SGSN User Guide

Cloud Mobility Manager, Release
21.8, Operating Documentation, v.

1
SGSN User Guide
DN09131849
Issue 10-0
© 2021 Nokia. Nokia Condential Information
Use subject to agreed restrictions on disclosure and use.

SGSN User Guide
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.
This document includes Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia. This
document is intended for use by Nokia’s customers (“You”/”Your”) in connection with a
product purchased or licensed from any company within Nokia Group of Companies. Use this
document as agreed. You agree to notify Nokia of any errors you may nd in this document;
however, should you elect to use this document for any purpose(s) for which it is not
intended, You understand and warrant that any determinations You may make or actions
You may take will be based upon Your independent judgment and analysis of the content of
this document.
Nokia reserves the right to make changes to this document without notice. At all times, the
controlling version is the one available on Nokia’s site.
No part of this document may be modied.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

product names mentioned in this document may be trademarks of their respective owners.
© 2021 Nokia.
2 © 2021 Nokia. Nokia confidential 10-0

SGSN User Guide
Table of Contents
Summary of changes .................................................................................................................. 21
1 SGSN User Guide ......................................................................................................................... 24
2 Mobility and session management .......................................................................................... 25

2.1 GPRS mobility management (Features SG01011, SG01104, SG01184, SG01149,
SG01254, SG01070) ....................................................................................................... 25
2.1.1 GPRS mobility management (Features SG01011, SG01104, SG01184,
SG01149, SG01254, and SG01070): feature summary .................................... 26
2.1.2 IMEI transfer in SGSN change (Feature SG01184): feature summary .......... 28
2.1.3 Subscriber re-authentication (Feature SG01070): feature summary ......... 28
2.1.4 Selective routing area update (Feature SG01149): feature summary ........ 29
2.1.5 Dual transfer mode (Feature SG01104): feature summary .......................... 30
2.1.6 Configuring mobility management timers ....................................................... 31
2.1.7 Enhanced P-TMSI handling (Feature SG01254): feature summary .............. 33
2.1.8 Authentication and security parameters ......................................................... 34
2.2 GPRS session management (Features SG01012 and SG02157) ............................. 36
2.2.1 GPRS session management (Feature SG01012): feature summary ............. 37
2.2.2 Multiple PDP contexts for one subscriber (Feature SG02157): feature
summary ................................................................................................................... 40
2.2.2.1 Configuring multiple PDP contexts for one subscriber ...................... 40
2.3 Direct tunnel and smart device direct tunnel signaling optimization (Features
SG02017 and SG01221): feature summary ............................................................... 42
2.3.1 Configuring direct tunnel .................................................................................... 43
2.4 SRNC relocation (Feature SG01161): feature summary ............................................ 44
2.5 GPRS Subscriber data management (Features SG01031, SG01246, f60210-02,
f60210-03, f60210-04 and f60210-16): feature summary .................................... 45
2.5.1 Displaying and deleting subscriber data .......................................................... 46
2.6 IPv6 and dual stack PDP context support (Feature SG01000): feature summary
............................................................................................................................................ 48
2.6.1 Configuring IPv6/dual stack on user layer ........................................................ 48
2.7 RIM procedure support (Features SG01024 and SG01232): feature summary
............................................................................................................................................ 50
2.8 Quality of service (Feature SG01027): feature summary ......................................... 52
2.8.1 Configuring QoS ................................................................................................... 53
2.9 Conversational QoS (Feature SG01122): feature summary ..................................... 60
2.10 Streaming QoS (Feature SG01007): feature summary ........................................... 61
2.11 Streaming quality optimization (Feature SG02170): feature summary ............... 63
2.11.1 Configuring streaming quality optimization .................................................. 63
2.12 Release 8 to pre-Release 8 QoS mapping (Feature SG01262) .............................. 64
2.12.1 Configuring Release 8 to pre-Release 8 QoS mapping ................................ 65
2.12.2 Release 8 - pre-Release 8 QoS mapping (Feature SG01262): feature
10-0 © 2021 Nokia. Nokia confidential 3

SGSN User Guide
summary ................................................................................................................... 67
2.13 Operator defined QCI (Feature f52059-01): feature summary ............................ 68
2.13.1 Configuring operator defined QCI .................................................................. 69
2.14 2G ciphering GEA 1/2/3 (Features SG01009, SG01034, SG01175 and f60210-19):
feature summary ............................................................................................................ 71
2.14.1 Configuring 2G ciphering .................................................................................. 72
2.15 UMTS authentication (Feature SG01054): feature summary ................................ 74
2.16 Network identity and time zone support (Feature SG02206): feature summary
............................................................................................................................................ 75
2.17 IP multimedia support (Feature SG01043): feature summary .............................. 76
2.18 SGSN support for IPv6 and dual stack (Feature f12101-02): feature summary
............................................................................................................................................ 77
2.19 SGSN support for IPv4/IPv6 dual stack transport for Gb (Feature f12101-04):
feature summary ............................................................................................................ 78
2.20 SGSN support for IPv4/IPv6 dual stack transport for Iu-C (Feature f12101-05):
feature summary ............................................................................................................ 79
2.21 SGSN support for IPv4/IPv6 dual stack transport for Iu-U/Gn-U/Gn-C (Feature
f12101-06): feature summary ...................................................................................... 80
2.22 SGSN support for IPv4/IPv6 dual stack transport for Gr/Gf/Gs (Feature
2.23 CMM support for Gn dual stack (Feature f11810-01): feature summary ............ 82
2.24 Enhanced triple access scenarios - delivery (Feature f14605-03): feature summary
............................................................................................................................................ 83
2.24.1 Checking before handling RAU and reattach without DNS query ............... 84
2.24.2 Enabling SGSN handling RAU and reattach without DNS query .................. 86
2.24.3 Enabling T-ADS Data Retrieval bit in diameter ULR and IDA messages
.................................................................................................................................... 86
2.25 RAI group/RAI based UE handling support (Feature f52049-01): feature summary
............................................................................................................................................ 87
2.25.1 Configuring RAI group/RAI based UE handling support ............................... 88
2.25.2 Executing forced IP change in RA .................................................................... 90
2.26 Customer-specified GTP error indication handling towards RNC (Feature
2.26.1 Enabling special collision handling behavior during handover from 4G to 3G
.................................................................................................................................... 95
2.27 CMM support for ARD provisioned in HSS and pass it with service-based HO to
radio accordingly (Feature f11343-01): feature summary ....................................... 98
2.28 SGSN support for user plane frames that exceed 1500 bytes (Feature f52017-01):
feature summary ............................................................................................................ 98
2.29 SGSN support for configurable PDN type IPv4v6 (Feature f52061-01): feature
summary ........................................................................................................................ 100
2.29.1 Configuring SGSN support for PDN type IPv4v6 ........................................ 100
2.30 SGSN support for independent 2G PRAU and MSRT timers with 3G (Feature
f52088-01): feature summary ................................................................................... 101

SGSN User Guide
2.30.1 Configuring independent 2G PRAU and MSRT timers with 3G ................. 102
3 Radio and core network access support ............................................................................... 103

3.1 Gb over IP (Features SG01048, SG01102, SG01029, f60210-06 and f60210-31)
.......................................................................................................................................... 103
3.1.1 Configuring Gb over IP ...................................................................................... 104
3.1.2 Gb over IP (Features SG01048, SG01102, SG01029, f60210-06 and
f60210-31): feature summary ........................................................................... 110
3.2 EDGE support (Feature SG01033): feature summary ............................................. 111
3.3 3G access support (Features SG02001 and SG01119): feature summary .......... 112
3.3.1 Configuring the lu interface ............................................................................. 114
3.4 HSDPA, HSUPA support and HSPA+ (Features SG02104, SG01113 and SG02198)
.......................................................................................................................................... 116
3.4.1 HSDPA, HSUPA support and HSPA+ (Features SG02104, SG01113 and
SG02198): feature summary .............................................................................. 117
3.4.2 HSDPA, HSUPA, and HSPA+ parameters ........................................................ 118
3.4.3 Downlink bit rate in ISHO and GERAN PDP context activation .................... 119
3.4.4 RNC profile .......................................................................................................... 120
3.4.5 Iu-PS interworking scenarios ........................................................................... 121
3.4.5.1 Normal reference cases ........................................................................ 121
3.4.5.2 Interworking with non-3GPP R7 capable RAN .................................... 123
3.4.5.3 Non-supporting UE ................................................................................ 124
3.4.5.4 SRNS relocation cases ........................................................................... 125
3.4.5.5 Roaming support .................................................................................... 127
3.5 I-HSPA enhancement (Features SG01142 and f52050-01): feature summary
.......................................................................................................................................... 128
3.5.1 Configuring I-HSPA enhancement .................................................................. 130
3.6 SS7 over IP (Features SG01051, SG01105, SG01771 and f60210-29): feature
summary ........................................................................................................................ 131
4 End user management ............................................................................................................ 135

4.1 IMEI check with EIR (Features SG01106, SG01090, SG02156 and f60210-17):
feature summary .......................................................................................................... 135
4.1.1 Configuring IMEI check with EIR ....................................................................... 136
4.2 SGSN support for IMEISV in check IMEI EIR over Gf (Feature f52074-01): feature
summary ........................................................................................................................ 138
4.2.1 Configuring the use of the IMEISV for authentication to the EIR via the Gf
interface ................................................................................................................. 139
4.3 HLR-based 2G/3G access control (Feature SG02114): feature summary ........... 142
4.3.1 Configuring HLR-based 2G/3G access control .............................................. 143
4.3.2 Additional configuration for HLR-based 2G/3G access control ................. 145
4.3.2.1 Configuring access rights for a GSM subscriber to the GSM network
.......................................................................................................................... 145
4.3.2.2 Configuring access rights for a GSM subscriber to the UMTS network
.......................................................................................................................... 146

SGSN User Guide
4.3.2.3 Configuring access rights for a UMTS subscriber to the GSM network
.......................................................................................................................... 147
4.3.2.4 Configuring access rights for a UMTS subscriber to the UMTS network
.......................................................................................................................... 147
4.3.2.5 Configuring reject cause code for a GSM subscriber to the GSM
network .......................................................................................................... 148
4.3.2.6 Configuring reject cause code for a GSM subscriber to the UMTS
network .......................................................................................................... 149
4.3.2.7 Configuring reject cause code for a UMTS subscriber to the GSM
network .......................................................................................................... 149
4.3.2.8 Configuring reject cause code for a UMTS subscriber to the UMTS
network .......................................................................................................... 150
4.3.2.9 Configuring reject cause code for an R97/98 terminal to the UMTS
network .......................................................................................................... 151
4.3.2.10 Configuring reject cause code for subscriber count ...................... 151
4.4 GTP information sending (Feature SG01082): feature summary .......................... 152
4.5 Enable faulty IMEISV UE (Feature SG01171): feature summary ............................ 153
4.6 Terminal management support (Features SG02203, f52040-01): feature summary
.......................................................................................................................................... 154
4.6.1 Configuring terminal provisioning for GPRS subscribers using enhanced IMEI
query ....................................................................................................................... 156
4.7 MultiSIM (Feature SG01063): feature summary ....................................................... 157
5 Gateway selection and APN control ....................................................................................... 159

5.1 Intelligent GGSN selection (Features SG01116, SG01212, SG01218, SG01255,
SG01234, SG01260 and SG03067): feature summary .......................................... 159
5.1.1 Configuring intelligent GGSN selection .......................................................... 161
5.2 Override of requested APN in SGSN (Features SG01074 and f52032-01): feature
summary ........................................................................................................................ 169
5.2.1 Configuring override of requested APN ......................................................... 170
5.3 IMEI-based APN override (Feature SG02019): feature summary .......................... 173
5.3.1 Configuring IMEI-based APN override ............................................................. 174
5.4 APN conversion and correction (Feature SG02215): feature summary ............... 177
5.5 SGSN Gn local break out control (Feature SG01258): feature summary ............. 178
5.5.1 Configuring SGSN Gn local break out control ................................................ 179
5.6 SGSN support for local break out for S4-SGSN (Feature f51022-01): feature
summary ........................................................................................................................ 180
5.6.1 Configuring the S4-SGSN local break out control feature .......................... 181
5.6.2 Removing the S4-SGSN local break out control feature ............................. 183
5.7 R8 DNS query support for Gn-SGSN (Features SG02213, f52058-01): feature
summary ........................................................................................................................ 184
5.7.1 Enabling R8 DNS query support for Gn-SGSN ............................................... 185
5.8 Gn SGSN P-GW selection based on MSISDN range with rel8 DNS (Feature

SGSN User Guide
5.8.1 Configuring Gn SGSN P-GW selection based on MSISDN range with rel8 DNS
.................................................................................................................................. 187
5.9 SGSN support GGSN Load Balancing (Features f52037-01 and f12101-12): feature
summary ........................................................................................................................ 188
5.9.1 Configuring SGSN support GGSN load balancing .......................................... 189
5.10 MSISDN number based home GGSN/P-GW selection enhancement (Feature
5.10.1 Configuring MSISDN number based home GGSN/P-GW selection
enhancement for the SGSN ................................................................................ 192
5.11 PLMN level control of preferred gateway type (S-GW/P-GW or GGSN) (Feature
5.11.1 Configuring PLMN level control of preferred gateway .............................. 194
5.12 SGSN support for mobility enhancements when PLMN Level control of preferred
gateway type is enabled (Feature f52068-01): feature summary ........................ 195
5.13 P-GW selection based on charging characteristics for R8 DNS queries (Feature
5.13.1 Configuring P-GW selection based on charging characteristics for R8 DNS
queries .................................................................................................................... 198
5.14 PLMN level control of S6d/Gr selection (Feature f51026-01): feature summary
.......................................................................................................................................... 198
5.14.1 Configuring PLMN level control of S6d/Gr selection ................................. 199
5.15 SGSN support for NR UE capability based GW (Feature f51018-01): feature
summary ........................................................................................................................ 200
5.16 SGSN support for 512 direct tunnel APNs (Feature f51028-01): feature summary
.......................................................................................................................................... 202
5.17 CMM support for control the subscriber to make one PDP per subscriber per APN
(Feature f10189-01): feature summary ................................................................... 203
5.18 SGSN support for static GGSN/P-GW selection with IMSI and MSISDN range
5.18.1 Configuring static GGSN/P-GW selection with IMSI and MSISDN range
.................................................................................................................................. 204
6 Pooling and network sharing features .................................................................................. 206

6.1 Multipoint Gb (Features SG01023 and SG01153): feature summary ................... 206
6.1.1 Configuring multipoint Gb ................................................................................ 207
6.2 Multipoint Iu (Features SG02002, SG01153 and SG02210): feature summary
.......................................................................................................................................... 208
6.2.1 Configuring multipoint Iu ................................................................................. 209
6.2.1.1 Configuring the NRI in SGSN ................................................................. 210
6.2.1.2 Adding SGSN to the pool ....................................................................... 211
6.2.1.3 Adding RNC to the PS pool area ........................................................... 211
6.2.1.4 Rollback steps for SGSN ........................................................................ 212
6.3 Removing SGSN for maintenance for multipoint Gb/Iu .......................................... 213
6.4 Multipoint Iu/Gb DNS optimization ............................................................................ 214

SGSN User Guide
6.5 SGSN support for offloading functionality (Feature f50106-02): feature summary
.......................................................................................................................................... 215
6.5.1 Configuring SGSN support for offloading functionality ............................... 216
6.6 SGSN support for multipoint offloading with IMSI (Feature f52010-04): feature
summary ........................................................................................................................ 219
6.6.1 Configuring multipoint offloading with IMSI .................................................. 220
6.7 Network sharing (Features SG01040, SG01021, SG01129, SG01179, SG02212 and
f60210-29) .................................................................................................................... 223
6.7.1 Network selection services (Features SG01021, SG01129, SG01040): feature
summary ................................................................................................................ 223
6.7.1.1 Configuring network selection services .............................................. 224
6.7.1.2 Deactivating network selection services ............................................. 226
6.7.2 SS7 network sharing (Feature SG01083): feature summary ...................... 226
6.7.2.1 Activating SS7 network sharing ............................................................ 227
6.7.2.2 Configuring SS7 network sharing variant 1: Multiple GT addresses
based on analysis for Called-Party-Address (CdPA) ................................ 228
6.7.2.3 Deactivating SS7 network sharing variant 1 ...................................... 230
6.7.2.4 Configuring SS7 network sharing variant 2: SS7 network sharing
enhancement or equivalently Multiple GT addresses based on RAN (PLMN)
of the subscriber ........................................................................................... 231
6.7.3 Multi operator core network (MOCN) functionality (Features SG01179 and
SG02212): feature summary .............................................................................. 232
6.7.3.1 Configuring 2G MOCN ............................................................................ 233
6.7.3.2 Deactivating 2G MOCN .......................................................................... 235
6.7.3.3 Configuring 3G MOCN ............................................................................ 235
6.7.3.4 Deactivating 3G MOCN .......................................................................... 237
6.7.4 SGSN support for 2nd update PDP to PGW and S-CDR generation at RAU
after HO (Feature f50100-01): feature summary ........................................... 238
6.8 Gs interface and interworking with MOCN (Feature f50101-01): feature summary
.......................................................................................................................................... 238
6.9 SGSN support for multiple MSC/VLRs per LAC (Feature f52067-01): feature
summary ........................................................................................................................ 242
6.9.1 Configuring multiple MSC/VLRs per LAC ........................................................ 242
6.10 SGSN support for omitting least significant MSIN digit fields used in GT analysis
when supported length limit is exceeded (Feature f52077-01): feature summary ...
243
7 Operational control and optimization ................................................................................... 245

7.1 SGSN charging (Features SG01015, SG01189, SG02193, SG01118 and f60210-18)
.......................................................................................................................................... 245
7.1.1 Configuring SGSN charging .............................................................................. 247
7.1.1.1 Configuring charging parameters ........................................................ 248
7.1.1.2 Configuring CDRs ................................................................................... 260
7.1.1.3 Configuring CDR files ............................................................................. 264

SGSN User Guide
7.1.1.4 Configuring tariff functionality ............................................................ 266

7.1.1.5 Configuring charging characteristics ................................................... 269
7.1.1.6 Configuring IMEISV in CDR .................................................................... 269
7.1.1.7 Disabling SGSN charging ....................................................................... 270
7.1.2 SGSN charging (Features SG01015, SG01189, SG02193, SG01118, and
7.2 IMEISV in CDR (SG01088): feature summary ............................................................ 273
7.3 Configurable charging (Features SG01147, SG01132 and f60210-18): feature
summary ........................................................................................................................ 274
7.3.1 Provisioning configurable charging ................................................................. 275
7.3.2 Deactivating configurable charging ................................................................ 285
7.4 SGSN support for Ga interface (Features f52000-01 and f12101-15): feature
summary ........................................................................................................................ 286
7.4.1 Operational aspects of the Ga interface ........................................................ 288
7.4.2 Configuring the Ga interface ........................................................................... 289
7.4.3 Switching between Ga and Bp ......................................................................... 293
7.4.4 Deleting a charging gateway ............................................................................ 294
7.5 Controlled roaming (Feature SG01004): feature summary ................................... 295
7.5.1 Configuring controlled roaming for home subscribers ................................ 296
7.5.2 Configuring controlled roaming for visitor subscribers ............................... 299
7.6 QoS control for roaming subscribers (Feature SG01067): feature summary ..... 303
7.6.1 Configuring QoS control for roaming subscribers ........................................ 303
7.7 Operator determined barring (Feature SG02207): feature summary .................. 305
7.8 QoS upgrade above the HLR values (Feature SG01256): feature summary ....... 306
7.8.1 Configuring QoS upgrade above the HLR values .......................................... 308
7.9 SGSN support for roaming QoS control (Feature f51023-01): feature summary
.......................................................................................................................................... 308
7.9.1 Configuring SGSN support for roaming QoS control ................................... 309
7.10 HLR HSPA+QoS Override (Feature SG01231): feature summary ........................ 310
7.10.1 Configuring HLR HSPA+QoS Override .......................................................... 311
7.11 Detach timer optimization and control (Features SG01080, SG01089, SG01197
and SG02035): feature summary ............................................................................... 313
7.11.1 Configuring detach timer ............................................................................... 314
7.12 Signalling reduction for stationary devices (M2M) (Feature SG01257): feature
summary ........................................................................................................................ 316
7.13 SGSN abnormal signaling reduction (Feature SG01259): feature summary ..... 317
7.14 Paging optimization enhancement (Feature SG02204): feature summary ....... 318
7.14.1 Configuring paging optimization enhancement ......................................... 319
7.15 PDP context mass deactivation protection (Feature SG01096): feature summary
.......................................................................................................................................... 321
7.16 Cause code mapping (Feature SG01141) ............................................................... 322
7.16.1 Configuring cause code mapping ................................................................. 325
7.16.1.1 Configuring the cause code set for PLMN ........................................ 326
7.16.1.2 Configuring the IMEI analysis ............................................................. 327

SGSN User Guide
7.16.2 Cause code mapping (Feature SG01141): feature summary ................... 328
7.17 Provisionable reject cause when mobility event is rejected with GMM error codes
CC11..15 (Feature f52066-01): feature summary .................................................. 329
7.17.1 Configuring reject cause values for mobility event rejected with GMM error
codes 11, 12, 13, 14, and 15 .............................................................................. 330
7.18 P-GW node name delivery on SGSN (Feature SG01263): feature summary ...... 334
7.19 Configurable GTP timers in SGSN (Features SG01029 and SG01249): feature
summary ........................................................................................................................ 334
7.19.1 Configuring GTP timers .................................................................................. 335
7.19.2 GTP timers for home users (sgsnLocalEndPtCfg) ....................................... 340
7.19.3 GTP timers for roamers (gtpTimer) .............................................................. 344
7.20 SGSN support for IPSec on the X3 interface (Feature f52006-01): feature
summary ........................................................................................................................ 346
7.20.1 Configuring IPsec on X3 interface for the SGSN ........................................ 346
7.21 SGSN support for detach procedure for implicitly detached UEs in case of a PAPS
failure (Feature f51025-01): feature summary ....................................................... 352
8 S4-SGSN .................................................................................................................................... 354

8.1 Release 8 architecture (Feature SG01235): feature summary .............................. 354
8.2 S-GW/P-GW selection enhancements for S4-SGSN (Feature f51020-01): feature
summary ........................................................................................................................ 356
8.3 S13' IMEI checking (Feature SG02220): feature summary ..................................... 356
8.3.1 Configuring S13' IMEI checking ........................................................................ 359
8.4 S6d/Gr selection (Feature SG01236): feature summary ........................................ 361
8.4.1 Configuring S6d/Gr selection .......................................................................... 361
8.5 S3-based packet switch handover ( Feature SG01242): feature summary ......... 363
8.6 S4 SGSN roaming control (Features SG01250 and SG01251): feature summary
.......................................................................................................................................... 364
8.6.1 Configuring S4 SGSN roaming control ........................................................... 366
8.7 Cause code forwarding over S4 interface (Feature SG01237): feature summary
.......................................................................................................................................... 368
8.8 SGSN support for RFSP index (Feature f51024-01): feature summary ............... 369
9 Interface/Link management ................................................................................................... 371

9.1 GTP sequence number management enhancements (Feature f11506-01): feature
summary ........................................................................................................................ 371
10 Operability .............................................................................................................................. 372

10.1 Traffica support (Features SG01025, SG01087 and f60210-15): feature summary
.......................................................................................................................................... 372
10.1.1 Configuring Traffica ........................................................................................ 373
10.2 SGSN support for call trace (Features f60210-13 and f52071-01): feature
summary ........................................................................................................................ 373
10.2.1 Configuring call trace ...................................................................................... 375
10.2.2 Outputting call trace data (PCAP files) ......................................................... 380

SGSN User Guide
10.2.3 Working with PCAP output files (SGSN) ........................................................ 385

10.2.4 Displaying trace data in RedisDB .................................................................. 388
10.2.5 Configuring call trace for user plane data ................................................... 390
10.3 Internal load balancing and admission control (Features SG01060, f60110-05,
f60210-04 and f60210-05): feature summary ....................................................... 392
10.4 PAPS load balancing mechanism per access type (Feature f50110-01): feature
summary ........................................................................................................................ 393
10.4.1 Configuring PAPS load balancing mechanism per access type ................ 394
10.5 PAPS 2G/3G graceful shutdown (Features SG01086, f60210-27 and f62010-45):
feature summary .......................................................................................................... 395
10.5.1 Configuring 2G/3G graceful shutdown ........................................................ 396
10.5.2 Activating the links after scale out ............................................................... 398
10.5.3 Unblocking PAPS 2G/3G graceful shutdown ............................................... 399
10.6 IPPS graceful shutdown (Feature f70002-02 – 150): feature summary ............ 401
10.6.1 Configuring IPPS graceful shutdown ............................................................ 401
10.7 Overload control (Features SG01037, f60210-20 and f60210-21): feature
summary ........................................................................................................................ 402
10.8 SGSN safety net overload (Feature f10702-01): feature summary ................... 404
10.8.1 Configuring SGSN safety net overload ........................................................ 406
10.9 Performance management (Features SG01016, SG01085, SG01028, SG01131,
f60210-10, f13012-02, f13012-03): feature summary ........................................ 407
10.9.1 Counter categories in CMM ........................................................................... 409
10.9.2 Average, minimum, and maximum counter values .................................... 410
10.9.3 Displaying PM data .......................................................................................... 412
10.9.4 Close to real-time counters ........................................................................... 428
10.9.5 Configuring SGSN performance management ........................................... 429
10.9.6 Configuring performance measurement jobs ............................................ 431
10.9.7 Retrieving XML-format PM data from NECC ............................................... 441
10.10 CMM support for “measInfoId” field in performance management reports
10.10.1 Adding parameter measInfoId to the PM report ...................................... 443
10.11 MME/SGSN PM data transfer towards ONAP-DCAE and MME/AMF PCMD data
transfer towards CA4MN (Feature f14615-05): feature summary ....................... 443
10.12 DPDK-based M3UA (Feature f60110-05): feature summary ............................ 444
10.12.1 Configuring DPDK-based M3UA .................................................................. 445
10.13 Enhanced collision handling of attach storm with pseudo-random TLLI from non
3GPP compliant devices (Feature f52011-01): feature summary ........................ 446
10.13.1 Configuring enhanced collision handling of attach storm with pseudo-
random TLLI from non 3GPP compliant devices .............................................. 447
10.14 CMM support for OAM alignment (Feature f14516-01): feature summary .... 448
10.15 SGSN support for subscription cache - delivery (Feature f50104-02): feature
summary ........................................................................................................................ 449
10.15.1 Configuring subscription cache .................................................................. 449
10.16 Simplex DBS (Feature f14111-07): feature summary ........................................ 450

SGSN User Guide
10.17 SNMP interface ......................................................................................................... 451

10.17.1 SNMP architecture ........................................................................................ 453
10.17.2 SNMP security ................................................................................................ 453
10.17.3 Configuring SNMP ......................................................................................... 454
10.18 Backup and restore .................................................................................................. 458
10.18.1 Backing up software ..................................................................................... 458
10.18.2 Restoring software ....................................................................................... 458
10.18.3 Backup scheduling (Feature f14509-01): feature summary .................. 460
10.18.3.1 Configuring scheduled backups ...................................................... 460
10.18.4 Remote copy of backup files (Feature f12003-01): feature summary
.................................................................................................................................. 463
10.18.4.1 Configuring the operator remote machine ................................... 463
10.18.4.2 Configuring SSH keys between CMM and remote machine ........ 465
10.18.4.3 Configuring schedule for remote copy of backup ........................ 466
10.18.5 CMM support for secure backup and restore of CMM instance (Feature
10.18.5.1 Configuring secure backup and restore ......................................... 469
10.19 Syslog collection and streaming to remote server (Feature f13207-02): feature
summary ........................................................................................................................ 471
10.20 CMM support for sending log and alarm information to stdout in addition to
current destinations (Feature f14402-01): feature summary .............................. 472
10.20.1 Configuring the CMM CNF to send logs and alarms using stdout ......... 473
10.21 CMM support for authentication of NTP server (Feature f13213-05): feature
summary ........................................................................................................................ 479
10.22 SGSN support for internal trace tool enhancement (Feature f52075-01): feature
summary ........................................................................................................................ 480
10.22.1 Configuring the internal trace tool ............................................................ 480
10.22.2 Configuration examples of the internal trace tool .................................. 482
10.22.3 Opening and parsing the generated files of the internal trace tool ..... 483
10.23 SGSN support for deciphered Gb signaling for call trace (Feature f52078-01):
feature summary .......................................................................................................... 485
10.23.1 Configuring SGSN support for deciphered Gb signaling for call trace
.................................................................................................................................. 486

SGSN User Guide
List of Figures
Figure 1 Rotation of data file states ....................................................................................... 247
Figure 2 NECC architecture ...................................................................................................... 453
Figure 3 Using Fluentd with Elasticsearch .............................................................................. 477
Figure 4 sgsnmon folder .......................................................................................................... 484
Figure 5 7-Zip ZS ....................................................................................................................... 484
Figure 6 BIN file creation .......................................................................................................... 484

SGSN User Guide
List of Tables
Table 1 GPRS mobility management (Features SG01011, SG01104, SG01184, SG01149,
SG01254, and SG01070): feature summary .............................................................. 26
Table 2 IMEI transfer in SGSN change (Feature SG01184): feature summary .................... 28
Table 3 Subscriber re-authentication (Feature SG01070): feature summary ................... 29
Table 4 Selective routing area update (Feature SG01149): feature summary .................. 29
Table 5 Dual transfer mode ( Feature SG01104): feature summary ................................... 31
Table 6 MM context state timers (sgsnTimer) ......................................................................... 32
Table 7 Enhanced P-TMSI handling (Feature SG01254): feature summary ........................ 34
Table 8 Authentication and security parameters ................................................................... 34
Table 9 GPRS session management (Feature SG01012): feature summary ....................... 37
Table 10 Multiple PDP contexts for one subscriber (Feature SG02157): feature summary
........................................................................................................................................... 40
Table 11 Direct tunnel and smart device direct tunnel signaling optimization (Features
SG02017 and SG01221): feature summary ............................................................... 43
Table 12 SRNC relocation (Feature SG01161): feature summary ........................................ 45
Table 13 GPRS Subscriber data management (Features SG01031, SG01246, f60210-02,
f60210-03, f60210-04 and f60210-16): feature summary ................................... 46
Table 14 IPv6 and dual stack PDP context support (Feature SG01000): feature summary
........................................................................................................................................... 48
Table 15 RIM procedure support (Features SG01024 and SG01232): feature summary
........................................................................................................................................... 51
Table 16 Quality of service (Feature SG01027): feature summary ...................................... 52
Table 17 QoS features (prFile) ................................................................................................... 54
Table 18 QoS configuration parameters (qosConf) ............................................................... 54
Table 19 QoS roaming configuration parameters .................................................................. 58
Table 20 RNC QoS parameters (rnsParamSet) ........................................................................ 60
Table 21 Conversational QoS (SG01122): feature summary ................................................ 61
Table 22 Streaming QoS (Feature SG01007): feature summary .......................................... 62
Table 23 Streaming quality optimization (Feature SG02170): feature summary .............. 63
Table 24 Values of streamingOptAct ........................................................................................ 64
Table 25 QCI mapping (command plmnParam) ....................................................................... 66
Table 26 Release 8 - pre-Release 8 QoS mapping (Feature SG01262): feature name:
feature summary ............................................................................................................ 68
Table 27 Operator defined QCI: feature summary ................................................................. 68
Table 28 2G ciphering GEA 1/2/3 (Features SG01009, SG01034, SG01175 and f60210-19):
feature summary ............................................................................................................ 72
Table 29 Ciphering parameters ................................................................................................. 73
Table 30 UMTS authentication (Feature SG01054): feature summary ............................... 75
Table 31 Network identity and time zone support (Feature SG02206): feature summary
........................................................................................................................................... 76

SGSN User Guide
Table 32 IP multimedia support (Feature SG01043): feature summary ............................. 77

Table 33 SGSN support for IPv6 and dual stack (Feature f12101-02): feature summary
........................................................................................................................................... 78
Table 34 SGSN support for IPv4/IPv6 dual stack transport for Gb: feature summary
........................................................................................................................................... 79
Table 35 SGSN support for IPv4/IPv6 dual stack transport for Iu-C: feature summary
........................................................................................................................................... 80
Table 36 SGSN support for IPv4/IPv6 dual stack transport for Iu-U/Gn-U/Gn-C: feature
summary .......................................................................................................................... 81
Table 37 SGSN support for IPv4/IPv6 dual stack transport for Gr/Gf/Gs: feature summary
........................................................................................................................................... 82
Table 38 CMM support for Gb dual stack: feature summary ................................................ 83
Table 39 Enhanced triple access scenarios - delivery: feature summary ........................... 84
Table 40 RAI group/RAI based UE handling support: feature summary .............................. 88
Table 41 Customer-specified GTP error indication handling towards RNC: feature summary
........................................................................................................................................... 95
Table 42 CMM support for ARD provisioned in HSS and pass it with service-based HO to
radio accordingly: feature summary ........................................................................... 98
Table 43 SGSN support for user plane frames that exceed 1500 bytes: feature summary
........................................................................................................................................... 98
Table 44 SGSN support for configurable PDN type IPv4v6: feature summary ................ 100
Table 45 Values for the defaultIpv4ForPdnTypeIpv4OrIpv6 parameter ........................... 101
Table 46 SGSN support for independent 2G PRAU and MSRT timers with 3G: feature
summary ....................................................................................................................... 101
Table 47 Gb over IP (Feature SG01048): feature summary ................................................ 111
Table 48 EDGE support (Feature SG01033): feature summary ......................................... 112
Table 49 3G access support (Features SG02001 and SG01119): feature summary
......................................................................................................................................... 112
Table 50 HSDPA, HSUPA support and HSPA+ (Features SG02104, SG01113 and SG02198):
feature summary ......................................................................................................... 117
Table 51 HSDPA parameters ................................................................................................... 119
Table 52 HSUPA parameters .................................................................................................... 119
Table 53 I-HSPA enhancement (Features SG01142 and f52050-01): feature summary
......................................................................................................................................... 129
Table 54 SS7 over IP (Features SG01051, SG01105, SG01771 and f60210-29): feature
summary ....................................................................................................................... 131
Table 55 IMEI check with EIR (Features SG01106, SG01090, SG02156 and f60210-17):
feature summary ......................................................................................................... 135
Table 56 SGSN support for IMEISV in check IMEI EIR over Gf (Feature f52074-01): feature
summary ....................................................................................................................... 139
Table 57 checkImeiSv parameter values ................................................................................ 141
Table 58 HLR-based 2G/3G access control (Feature SG02114): feature summary

SGSN User Guide
......................................................................................................................................... 142
Table 59 Values of access rights for a GSM subscriber to the GSM network ................... 146
Table 60 Values of access rights for a GSM subscriber to the UMTS network ................. 146
Table 61 Values of access rights for a UMTS subscriber to the GSM network ................. 147
Table 62 Values of access rights for a UMTS subscriber to the UMTS network ............... 148
Table 63 Values of reject cause code for a GSM subscriber to the GSM network
......................................................................................................................................... 148
Table 64 Values of reject cause code for a GSM subscriber to the UMTS network
......................................................................................................................................... 149
Table 65 Values of reject cause code for a UMTS subscriber to the GSM network
......................................................................................................................................... 150
Table 66 Values of reject cause code for a UMTS subscriber to the UMTS network.
......................................................................................................................................... 150
Table 67 Values of reject cause code for an R97/98 terminal to the UMTS network
......................................................................................................................................... 151
Table 68 Values of reject cause code for subscriber count ................................................ 152
Table 69 GTP information sending (Feature SG01082): feature summary ...................... 153
Table 70 Enable faulty IMEISV UE (Feature SG01171): feature summary ......................... 154
Table 71 Terminal management support (Features SG02203, f52040-01): feature
summary ....................................................................................................................... 154
Table 72 MultiSIM (Feature SG01063): feature summary ................................................... 158
Table 73 Intelligent GGSN selection (Features SG01116, G01212, SG01218, SG01255,
SG01234, SG01260 and SG03067): feature summary .......................................... 159
Table 74 Intelligent GGSN selection activation parameters ............................................... 162
Table 75 Override of requested APN in SGSN (Features SG01074 and f52032-01): feature
summary ....................................................................................................................... 169
Table 76 IMEI-based APN override (Feature SG02019): feature summary ...................... 174
Table 77 APN conversion and correction (Feature SG02215): feature summary ............ 178
Table 78 SGSN Gn local break out control (Feature SG01258): feature summary
......................................................................................................................................... 179
Table 79 SGSN support for local break out for S4-SGSN: feature summary ................... 181
Table 80 R8 DNS query support for Gn-SGSN (Features SG02213, f52058-01): feature
summary ....................................................................................................................... 184
Table 81 Gn SGSN P-GW selection based on MSISDN range with rel8 DNS (Feature
Table 82 Values of msisdnPgwDnsFallback ........................................................................... 187
Table 83 SGSN support GGSN Load Balancing (Features f52037-01 and f12101-12):
feature summary ......................................................................................................... 189
Table 84 Values of ggsnLbMode ............................................................................................. 190
Table 85 MSISDN number based home GGSN/P-GW selection enhancement: feature
summary ....................................................................................................................... 192
Table 86 PLMN level control of preferred gateway type (S-GW/P-GW or GGSN): feature

SGSN User Guide
summary ....................................................................................................................... 194

Table 87 SGSN support for mobility enhancements when PLMN Level control of preferred
gateway type is enabled: feature summary ............................................................. 195
Table 88 P-GW selection based on charging characteristics for R8 DNS queries: feature
summary ....................................................................................................................... 197
Table 89 PLMN level control of S6d/Gr selection: feature summary ................................ 199
Table 90 SGSN support for NR UE capability based GW: feature summary ...................... 200
Table 91 SGSN support for 512 direct tunnel APNs: feature summary ............................ 202
Table 92 CMM support for control the subscriber to make one PDP per subscriber per APN:
feature summary ......................................................................................................... 203
Table 93 SGSN support for static GGSN/P-GW selection with IMSI and MSISDN range:
feature summary ......................................................................................................... 204
Table 94 Multipoint Gb (Features SG01023 and SG01153): feature summary ............... 206
Table 95 Multipoint Iu (Features SG02002, SG01153 and SG02210): feature summary
......................................................................................................................................... 209
Table 96 SGSN support for offloading functionality (Feature f50106-02): feature summary
......................................................................................................................................... 216
Table 97 SGSN support for multipoint offloading with IMSI (Feature f52010-04): feature
summary ....................................................................................................................... 220
Table 98 Network selection services (Features SG01021, SG01129, SG01040): feature
summary ....................................................................................................................... 224
Table 99 SS7 network sharing (Feature SG01083): feature summary .............................. 227
Table 100 Multi operator core network (MOCN) (Features SG01179, SG02212): feature
summary ....................................................................................................................... 233
Table 101 SGSN support for 2nd update PDP to P-GW and S-CDR generation at RAU after
HO: feature summary .................................................................................................. 238
Table 102 Gs interface and interworking with MOCN: feature summary .......................... 238
Table 103 SGSN support for multiple MSC/VLRs per LAC: feature summary .................. 242
Table 104 SGSN support for omitting least significant MSIN digit fields used in GT analysis
when supported length limit is exceeded: feature summary ................................ 244
Table 105 Charging-related prFile parameters .................................................................... 248
Table 106 Parameters of cdrFiles ........................................................................................... 265
Table 107 Parameters of chargingChangeGroup ................................................................. 267
Table 108 SGSN charging (Features SG01015, SG01189, SG02193, SG01118, and
Table 109 IMEISV in CDR (SG01088): feature summary ...................................................... 274
Table 110 Configurable charging (Features SG01147, SG01132 and f60210-18): feature
summary ....................................................................................................................... 275
Table 111 Values of ttcMode ................................................................................................... 278
Table 112 SGSN support for Ga interface: feature summary ............................................. 286
Table 113 Controlled roaming (Feature SG01004): feature summary ............................. 296
Table 114 QoS control for roaming subscribers (Feature SG01067): feature summary

SGSN User Guide
......................................................................................................................................... 303
Table 115 Operator determined barring (Feature SG02207): feature summary ............ 306
Table 116 QoS upgrade above the HLR values (Feature SG01256): feature summary
......................................................................................................................................... 307
Table 117 SGSN support for roaming QoS control (Feature f51023-01): feature summary
......................................................................................................................................... 309
Table 118 HLR HSPA+QoS Override (Feature SG01231): feature summary .................... 311
Table 119 Detach timer optimization and control (Feature SG01080, SG01089, SG01197
and SG02035): feature summary .............................................................................. 314
Table 120 Signalling reduction for stationary devices (M2M) (Feature SG01257): feature
summary ....................................................................................................................... 317
Table 121 SGSN abnormal signaling reduction (Feature SG01259): feature summary
......................................................................................................................................... 317
Table 122 Paging optimization enhancement (Feature SG02204): feature summary
......................................................................................................................................... 319
Table 123 PDP context mass deactivation protection (Feature SG01096): feature summary
......................................................................................................................................... 322
Table 124 PRFILE parameters affected by cause code mapping ....................................... 324
Table 125 UTPFIL parameters affected by cause code mapping ...................................... 324
Table 126 Cause code mapping (Feature SG01141): feature summary ........................... 328
Table 127 Provisionable reject cause when mobility event is rejected with GMM error codes
CC11..15: feature summary ....................................................................................... 330
Table 128 Values of rejectCcForGmmErrorCode11 ............................................................. 331
Table 133 P-GW node name delivery on SGSN (Feature SG01263): feature summary
......................................................................................................................................... 334
Table 134 Configurable GTP timers in SGSN (Features SG01029 and SG01249): feature
summary ....................................................................................................................... 335
Table 135 GTP timers for homers (sgsnLocalEndPtCfg) ..................................................... 340
Table 136 Configurable GTP timers for roamers (gtpTimer) .............................................. 344
Table 137 SGSN support for IPSec on the X3 interface (Feature f52006-01): feature
summary ....................................................................................................................... 346
Table 138 Values and description of command ipsecProfile .............................................. 347
Table 139 Values and description of command ipsecConn ................................................ 349
Table 140 SGSN support for detach procedure for implicitly detached UEs in case of a
PAPS failure (Feature f51025-01): feature summary ............................................ 353
Table 141 Release 8 architecture (Feature SG01235): feature summary ........................ 354
Table 142 S-GW/P-GW selection enhancements for S4-SGSN: feature summary
......................................................................................................................................... 356

SGSN User Guide
Table 143 S13' IMEI checking (Feature SG02220): feature summary ............................... 357
Table 144 Mobility management procedures for which ME Identity Check Request is used
......................................................................................................................................... 360
Table 145 S6d/Gr selection (Feature SG01236): feature summary .................................. 361
Table 146 S3-based packet switch handover ( Feature SG01242): feature summary
......................................................................................................................................... 364
Table 147 S4 SGSN roaming control (Features SG01250 and SG01251): feature summary
......................................................................................................................................... 364
Table 148 Cause code forwarding over S4 interface (Feature SG01237): feature summary
......................................................................................................................................... 369
Table 149 SGSN support for RFSP index: feature summary ............................................... 370
Table 150 GTP sequence number management enhancements: feature summary
......................................................................................................................................... 371
Table 151 Traffica support (Features SG01025, SG01087 and f60210-15): feature
summary ....................................................................................................................... 372
Table 152 SGSN support for call trace: feature summary .................................................. 374
Table 153 Reconstructed protocol stack ............................................................................... 386
Table 154 Interface IP addresses ............................................................................................ 387
Table 155 Wireshark packet analyzer settings example ...................................................... 388
Table 156 Internal load balancing and admission control (Features SG01060, f60110-05,
f60210-04 and f60210-05): feature summary ...................................................... 392
Table 157 PAPS load balancing mechanism per access type: feature summary ............. 394
Table 158 PAPS 2G/3G graceful shutdown (Features SG01086, f60210-27 and
Table 159 IPPS graceful shutdown (Feature f70002-02 – 150): feature summary
......................................................................................................................................... 401
Table 160 Overload control (Features SG01037, f60210-20 and f60210-21): feature
summary ....................................................................................................................... 402
Table 161 SGSN safety net overload (Feature f10702-01): feature summary ............... 404
Table 162 Attach and RAU rate limits (gParms) .................................................................... 407
Table 163 Performance management (Features SG01016, SG01085, SG01028, SG01131,
f60210-10, f13012-02, f13012-03): feature summary ....................................... 407
Table 164 CMM support for “measInfoId” field in performance management reports:
feature summary ......................................................................................................... 442
Table 165 MME/SGSN PM data transfer towards ONAP-DCAE and MME/AMF PCMD data
transfer towards CA4MN: feature summary ............................................................ 444
Table 166 DPDK-based M3UA (Feature f60110-05): feature summary ........................... 445
Table 167 Enhanced collision handling of attach storm with pseudo-random TLLI from non
3GPP compliant devices: feature summary ............................................................. 447
Table 168 CMM support for OAM alignment: feature summary ........................................ 448
Table 169 SGSN support for subscription cache - delivery: feature summary ................ 449
Table 170 Simplex DBS: feature summary ............................................................................ 451

SGSN User Guide
Table 171 User security levels ................................................................................................. 454

Table 172 Backup scheduling: feature summary .................................................................. 460
Table 173 Parameters of cmm schedule create and cmm schedule modify ................... 461
Table 174 Remote copy of backup files: feature summary ................................................ 463
Table 175 remoteCopySetup command parameters .......................................................... 464
Table 176 Parameters of cmm schedule create and cmm schedule modify ................... 467
Table 177 Cloud backup and restore improvements via NSP: feature summary ............ 468
Table 178 secureCopySetup command parameters ........................................................... 470
Table 179 Syslog collection and streaming to remote server: feature summary
......................................................................................................................................... 472
Table 180 CMM support for sending log and alarm information to stdout in addition to
current destinations: feature summary ................................................................... 473
Table 181 Fluentd and stdout configuration fields .............................................................. 476
Table 182 CMM support for authentication of NTP server: feature summary ................ 479
Table 183 SGSN support for internal trace tool enhancement: feature summary
......................................................................................................................................... 480
Table 184 SGSN support for deciphered Gb signaling for call trace: feature summary
......................................................................................................................................... 485

SGSN User Guide
Summary of changes
A list of changes between document issues. Click the links to view the updated sections.
Changes between issues 9-0 (CMM21.5) and 10-0 (CMM21.8)
New and updated features in CMM21.8

SGSN support for independent 2G PRAU and MSRT timers with 3G (Feature f52088-01):
feature summary
Configuring independent 2G PRAU and MSRT timers with 3G
SGSN support for call trace (Features f60210-13 and f52071-01): feature summary:
added a new restriction that the Create Session Request message retries are not
captured in the internal call trace PCAP files as these occur in the IPDS unit without
informing the PAPS unit
Working with PCAP output files (SGSN): clarified which information applies for hard-coded
values
CMM support for sending log and alarm information to stdout in addition to current
destinations (Feature f14402-01): feature summary
Configuring the CMM CNF to send logs and alarms using stdout
SNMP architecture: updated to add information for the ALMS pod
CMM support for authentication of NTP server (Feature f13213-05): feature summary
SGSN support for internal trace tool enhancement (Feature f52075-01): feature
summary
Configuring the internal trace tool
Configuration examples of the internal trace tool
Opening and parsing the generated files of the internal trace tool
SGSN support for deciphered Gb signaling for call trace (Feature f52078-01): feature
summary
Configuring SGSN support for deciphered Gb signaling for call trace
General changes
Configuring call trace: removed parameters collectorIP, s1mmeenb, uu, and x2 from
both the callTraceJob command and the callTraceSetting command
Syslog collection and streaming to remote server (Feature f13207-02): feature summary:
added but not new feature
Changed the references of SGSN Counters to CMM Counters in this document

SGSN User Guide
Changes between issues 8-2 (CMM21 M2) and 9-0 (CMM21.5)
New and updated features in CMM21.5

Configuring IPv6/dual stack on user layer: Updated. A note for feature dualStackPdp
and prFile dualStackPdpCtxt has been added.
SGSN support for local break out for S4-SGSN (Feature f51022-01): feature summary
Configuring the S4-SGSN local break out control feature
Removing the S4-SGSN local break out control feature
CMM support for control the subscriber to make one PDP per subscriber per APN
(Feature f10189-01): feature summary
SGSN support for static GGSN/P-GW selection with IMSI and MSISDN range (Feature
f52070-01): feature summary
Configuring static GGSN/P-GW selection with IMSI and MSISDN range
SGSN support for Ga interface (Features f52000-01 and f12101-15): feature summary:
Updated. Added a note for NECC related alarms.
Changes between issues 8-1 (CMM21) and 8-2 (CMM21 M2)
New and updated features in CMM21 M2

SGSN support for IMEISV in check IMEI EIR over Gf (Feature f52074-01): feature summary
Configuring use of IMEISV for authentication to the EIR via the Gf interface
Configuring intelligent GGSN selection: updated Example: UE capability based GW
selection for home subscribers and intelligent gateway selection for roaming subscribers,
Example: Nearest GGSN selection and Example: GGSN selection based on charging
characteristics.
SGSN support for NR UE capability based GW (Feature f51018-01): feature summary
SGSN support for 512 direct tunnel APNs (Feature f51028-01): feature summary
GTP sequence number management enhancements (Feature f11506-01): feature
summary
SGSN support for call trace (Features f60210-13 and f52071-01): feature summary:
Updated. SGSN support for user plane data in call trace (Feature f52071-01) feature added.
Working with PCAP output files (SGSN): Updated the Protocol stack section due to
SGSN support for user plane data in call trace (Feature f52071-01).
Configuring call trace for user plane data: Added due to SGSN support for user plane
data in call trace (Feature f52071-01).

SGSN User Guide
CMM support for “measInfoId” field in performance management reports (Feature

Adding parameter measInfoId to the PM report

SGSN User Guide
1. SGSN User Guide

SGSN User Guide provides instructions for the operation and administration of the
network element.
For the initial setup of the network element, see:

Cloud infrastructure operating documentation
Network Functions Manager - Packet operating documentation
Lifecycle Management and Software Upgrade documents, in CMM operating documentation
Integrating CMM, in CMM operating documentation
System architecture is described in Product Description and features in SGSN Feature

Overview.
For command descriptions as well as user account management and command execution
instructions, see CLI Reference Guide.
For features with only SGSN counters, see the updates in SGSN Feature Overview and CMM
Counters.

SGSN User Guide
2. Mobility and session management
2.1 GPRS mobility management (Features SG01011,

SG01104, SG01184, SG01149, SG01254, SG01070)
With this feature, end user is allowed to get registered and have access to the GPRS
services (attach, detach, update location, routing area update, authentication).
Mobility as well as session management is the core SGSN functionality. The functionality
provides subscriber authentication to the system, establishment of the data path, and
subscriber mobility within the general packet radio service (GPRS) network.
Mobility management (MM) handles the subscriber's requests for attaching to or detaching
from the general packet radio service (GPRS) network. MM updates the location of the
subscriber to the home location register (HLR/HSS) and to the visitor location register (VLR)
if the mobile station (MS) is also attached to the circuit-switched (CS) services. MM transfers
the necessary information from another SGSN when the subscriber moves from one routing
area to another. MM also handles the subscriber's authentication functions.
Mobility management Gb mode states:

IDLE (GPRS) state
STANDBY state
READY state
Mobility management Iu mode states:

PMM DETACHED state
PMM IDLE state
PMM CONNECTED state
Mobility management procedures:

Attach
Routing area update (RAU)
Periodic Routing Area Update
Detach
Tracking area update (TAU)
Relocation
Intra PAPS, where the source and the target RNC are located under the same
PAPS/PAPS group.

SGSN User Guide
Inter PAPS, where the source and the target RNC are located under different
PAPSs/PAPS group.
Inter SGSN, where the source and the target RNC are located under different SGSNs
Service request
MS-initiated service request
NW-initiated service request
Security mode command
Radio resource functionality
Cell selection
Discontinuous reception (DRX)
PS paging
Subscriber authentication
Subscriber re-authentication
2G-3G interworking
Intersystem change to 4G
Dual transfer mode
Enhanced P-TMSI handling
Selective Routing Area Update
2.1.1 GPRS mobility management (Features SG01011,

SG01104, SG01184, SG01149, SG01254, and SG01070):
feature summary
GPRS mobility management comprises a number of mobility management features.
Table 1: GPRS mobility management (Features SG01011, SG01104, SG01184, SG01149,

SG01254, and SG01070): feature summary
Function Impact
Compliance • GSM 23.060 General Packet Radio Service (GPRS) Service description;
Stage 2
• GSM 24.008 Mobile Radio Interface Layer 3 specication (CC/MM)
• 3GPP23.401 General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access,
Release 8
Capacity None
Required features None

SGSN User Guide
Function Impact
Interworking/dependent • Packet data transfer

features • GPRS subscriber data management (Feature SG01031)
• SGSN charging (Feature SG01015)
• Performance management (Feature SG01016)
• IPv6 and dual stack PDP context support (Feature SG01000)
• Detach Timer optimization and control (Features SG01080, SG01089,
SG01197, and SG02035)
• IMEI check with EIR (Features SG01090, SG01106 and SG02156)
• EDGE support (Feature SG01033)
• SRNC relocation (Feature SG01161)
• 3G access support (Feature SG02001)
• Network Sharing (Features SG01021, SG01040, SG01129, SG01179, and
SG02212)
• Signaling reduction for stationary devices (M2M) (Feature SG01257)
• Controlled roaming (Feature SG01004)
• HLR-based 2G/3G access control (Feature SG02114)
• UMTS authentication (Feature SG01054)
Restrictions None
Conguration Command securityParam, parameters

management authenticationMode,imeiCheckMode, cipheringMode,
umtsCipheringMode, ptmsiSignatureMode
Command sgsnTimer, parameters detachTimer,
perRaUpTimer, overwriteMsRdy, readyTimer,
msReachabTimer
Command system, parameter msStandbyForced
Command sgsnLocalEndPtCfg, parameter t3tunnel (GNSGSN,
with default value 20).
Command plmnParam, parameters for:
• PLMN
• handling of isolated/denylisted IMEIs
• Authentication Repetition Rate for mobility management procedures
• IMEI status check from EIR procedures
• IMEI check repetition rate for mobility management procedures
• PTMSI signature repetition rate for mobility management procedures
Counters Counters that are updated in terms of mobility management belong

to 001 measurement group which is relevant to GPRS Mobility
Management procedures. Counter range in this group is: M001C000 –
M001C411
Alarms 0126 PDP OVER DEFINED LIMIT

2012 ERROR IN FILE OPENING
2282 ACCESS SERVICE INITIALIZATION FAILED
Feature ID SG01011, SG01104, SG01184, SG01149, SG01254, and SG01070

SGSN User Guide
2.1.2 IMEI transfer in SGSN change (Feature SG01184):

feature summary
If the international mobile equipment identity (IMEI) or the international mobile
equipment identity and software version number (IMEISV) information is known by the
old SGSN, it is included into the SGSN Context Response message. When this occurs, it is
possible to omit the separate identification request and response messages and reduce
the time used in the inter-SGSN RAU procedure by one round-trip time. If the new SGSN
does not get the IMEI or IMEISV information from the old SGSN and the new SGSN is
configured to retrieve the IMEI or IMEISV, the new SGSN requests the IMEI/IMEISV
information with a separate identity procedure.
Table 2: IMEI transfer in SGSN change (Feature SG01184): feature summary
Function Impact
Compliance 3GPP TS 29.060 Rel. 5
Capacity None
Required features This feature is an enhancement to Feature SG01011: GPRS mobility

management.
Interworking/dependent None
features
Restrictions None
Conguration None
management
Counters None
Alarms None
Feature ID SG01184
2.1.3 Subscriber re-authentication (Feature SG01070):

feature summary
If the Mobile Station (MS) response to first authentication request is not valid, the
network can require a re-authentication. If the re-authentication fails, then the ongoing
service request is rejected with an information that authentication has been failed.

SGSN User Guide
Table 3: Subscriber re-authentication (Feature SG01070): feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions The feature is not supported if authentication is not activated in the

SGSN.
Conguration Command prFile, parameters reAuthActive and

management reAuthSupport
Command plmnParam, authentication repetition rate parameters for
MM procedures. For example, to provision re-authentication for a
GPRS attach, activate the re-authentication feature and dene the
number of re-authentication attempts for the attach procedure.
Counters None
Alarms None
Feature ID SG01070
2.1.4 Selective routing area update (Feature SG01149):

feature summary
This feature allows the operator to share the same routing area (RA) of one geographical
area with both 2G and 3G radio access. When a shared RA is in use, the RAU is not
required every time a mobile station moves between 2G and 3G cells because the mobile
station follows the selective RA update procedure.
Table 4: Selective routing area update (Feature SG01149): feature summary
Function Impact
Compliance 3GPP TS 23.060 General Packet Radio Service (GPRS); Service

description; Stage 2, Release 5
3GPP TS 24.008 Mobile radio interface Layer 3 specication; Core
network protocols; Stage 3, Release 5

SGSN User Guide
Function Impact
Capacity The feature decreases the network load caused by routing area
updates.
Interworking/dependent GPRS mobility management (Feature SG01011)

features GPRS session management (Feature SG01012)
3G access support (Feature SG02001)
Internal Load balancing and admission control (Feature SG01060)
Restrictions This feature is applicable only in a combined 2G and 3G environment.

• If the same routing area is used for both Iu and Gb interfaces,
congure them under the same PAPS or PAPS group.
• If the mobile has changed from 3G access to 2G access without
signaling the core network and performs the detach without RAU, the
SGSN maintains subscriber contexts until the mobile reachable timer
(MSRT) expires.
Conguration None
management
Counters Counters that are updated in terms of selective RA update belong to

026 and 024 measurement groups which are relevant to GPRS Gb
SGSN paging procedures and GPRS Iu SGSN paging procedures
respectively.
GPRS Gb SGSN Paging Measurement (026):
• M026C000 / NUMBER OF GB PAGING PROCEDURES
• M026C001 / NUMBER OF UNSUCCESSFUL GB PAGING PROCEDURES
• M026C002 / NUMBER OF GB SGSN LEVEL PAGINGS
• M026C003 / NUM OF GB PAGING PROCEDURES DUE TO DL DATA
NOTIF FROM S-GW
• M026C004 / NUM OF UNSUCCESSFUL GB PAGING PROCEDURES DUE
TO DL DATA NOTIF FROM S-GW
GPRS Iu SGSN Paging Measurement (024):
• M024C000 / NUMBER OF IU PAGING PROCEDURES
• M024C001 / NUMBER OF IU PAGING PROCEDURES FAILED
• M024C002 / NUMBER OF IU SGSN LEVEL PAGINGS
Alarms None
Feature ID SG01149
2.1.5 Dual transfer mode (Feature SG01104): feature

summary
Dual transfer mode (DTM) is a transfer mode in which an MS is in dedicated mode and

SGSN User Guide
packet transfer mode simultaneously. The end user can have two simultaneous ‘calls’:
one on the CS network (for example, a voice call) and one on the packet switched GPRS
network (for example, a data connection to the Internet).
Table 5: Dual transfer mode ( Feature SG01104): feature summary
Function Impact
Compliance 3GPP TS 43.055
Capacity None
features
Restrictions None
Conguration None
management
Counters None
Alarms None
Feature ID SG01104
2.1.6 Configuring mobility management timers

Use parameters of the sgsnTimer command to configure the timer controlling SGSN-
initiated detach and timers controlling mobility management Gb/Iu states.
Procedure
1 Display SGSN timers.
cmm sgsnTimer show
2 Configure detach timer.
The detachTimer parameter defines the time when an inactive subscriber is detached.
See Detach timer optimization and control (Feature SG01080, SG01089, SG01197,
SG02035).
To configure the timer: cmm sgsnTimer modify --detachTimer <integer

SGSN User Guide
0-1440 min>
3 Configure MM context state timers.
These timers control Mobility management Gb mode states and Mobility management Iu
mode states (see SGSN Feature Overview).
sgsnTimer parameters:
Table 6: MM context state timers (sgsnTimer)
Timer Values Description
readyTimer 0...10800 s The READY timer, T3314, is used in the MS and in

the network for each assigned P-TMSI to control
the cell update procedure. When the READY timer
is running or deactivated, the MS performs a cell
update each time a new cell is selected. If a routing
area is crossed, the MS performs a RAU procedure
instead of a cell update. The READY timer is
started in the following cases:
• in the MS when the GMM entity receives an
indication from the lower layers that an LLC frame
has been transmitted on the radio interface
• in the network when the GMM entity receives an
indication from the lower layers that an LLC frame
has been successfully received by the network
overwriteMsRdy true/false This parameter indicates whether the value of the

READY timer requested by the MS can be
overridden, by using the operator-congurable
parameter value for the READY timer. In cases of
maximum value of READY timer was requested by
MS in attach or RAU procedures, both READY and
periodic RA update timers are set to maximum
value even if the value of the overwriteMsRdy
parameter is true.
standbyTimer 0...11160 s STANDBY timer starts when the READY timer

expires and MS goes from Ready state to Standby.
The MM context state is changed from STANDBY
to IDLE when either SGSN receives a MAP Cancel
Location message from HLR and removes the MM
and PDP contexts or an implicit GPRS detach
procedure is performed. An implicit GPRS detach
procedure is initiated when the MS reachable timer
and the STANDBY timer have expired, or if a
network error has occurred. If the subscriber has
active PDP contexts, the contexts are deactivated.

SGSN User Guide
Timer Values Description
msReachabTimer 0...11160 s This parameter denes the timer for triggering an

implicit GPRS detach for the subscriber, if the
subscriber has made no interactions with the
network. The value must be slightly longer than the
value of the perRaUpTimer parameter used by
the UE.
system parameters:
msStandbyForced true/false
msStandbyForced is used (upon denition) when the network
orders the MS to go into STANDBY mode immediately after an
MM procedure by using the force to standby parameter. If the MS
requests the READY timer with maximum value in a GPRS attach
or RAU request, the parameter has no effect. Based on this,
msStandbyForced is useful in case of an MS with no maximum
value for READY timer dened.
2.1.7 Enhanced P-TMSI handling (Feature SG01254):

feature summary
When the enhanced P-TMSI handling feature is activated, SGSN will check whether two
different subscribers are using the same P-TMSI to identify themselves to the network or
not. In such cases, SGSN might send additional Identity Request to UE to find out UEs
IMSI. SGSN will be able to handle both cases: the same user or different users.

SGSN User Guide
Table 7: Enhanced P-TMSI handling (Feature SG01254): feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command prFile, parameter enhancedPtmsiHandling

management
Counters None
Alarms None
Feature ID SG01254
2.1.8 Authentication and security parameters

Configurable authentication and security parameters, defaults and purposes are listed in
the table.
Table 8: Authentication and security parameters
Parameter Default Purpose
authenticationMode whenNeeded Activates authentication functionality (value act) or

(securityParam) deactivates it (value deact).
imeiCheckMode false IMEI check is activated (true) or not (false)

(securityParam) IMEI check with EIR (Features SG01106, SG01090, SG02156
and f60210-17)
S13' IMEI checking (Feature SG02220)
imeiRequestMode false Terminal management support (Feature SG02203): the

(securityParam) SGSN is able to send the subscriber's identity (IMSI or
alternatively IMSI and MSISDN) in the MAP Check IMEI
request message to the terminal management system.
The terminal management system automatically delivers
operator settings to the subscriber’s mobile stations when
it detects the change of a mobile station.

SGSN User Guide
Parameter Default Purpose
ptmsiSignatureMode(securit false In addition to the PTMSI, a PTMSI signature can be

yParam) assigned to a subscriber. The PTMSI signature is an extra
information element used between the MS and the
network. The operator can decide whether or not to use
the PTMSI signature. If the PTMSI signature is used, the
network assigns a PTMSI signature for a subscriber during
the mobility management procedure. The PTMSI signature
is always sent encrypted between the network and the MS.
This way unauthorized users are not able to confuse the
network, even if they manage to nd out the PTMSI used
between the MS and the network. PTMSI signature is a 3-
byte random number calculated via software-based
random number generators.
cipheringMode false 2G ciphering GEA 1/2/3 (Features SG01009, SG01034,

(securityParam) SG01175 and f60210-19)
umtsCipheringMode false UMTS ciphering mode is in use (true) or not (false).

(securityParam)
attachRestriction false Attach restriction for non-ciphering 2G subscribers in use

(securityParam) (true) or not (false).
umtsAttachRestriction false Attach restriction for non-ciphering UMTS subscribers in

(securityParam) use (true) or not (false).
reAuthActive, false Subscriber re-authentication: reauthentication is used in

reAuthSupport (prFile) cases of failures during the rst authentication procedure
during, for example, an attach.
Authentication must be activated.
enhancedPtmsiHandling false Enhanced P-TMSI handling

(prFile)
forceAuthentication true When true, CMM forces authentication in all SGSN

(prFile) procedures for 1 hour after PAPS scale out/restart
ignoring the provisioning provided in cmm
securityParam and cmm plmnParam. 1 hour after
the PAPS scale out/restart, CMM performs authentication
according to cmm securityParam and cmm
plmnParam provisioning.
When false, CMM performs authentication according to
cmm securityParam and cmm plmnParam
provisioning.

SGSN User Guide
Note:
The securityParam --authenticationMode can have the following values:
whenNeeded Authentication is done when UE makes an attach or routing

area update.
act Authentication follows repetition rates congured under

plmnParam like iuPeriodicRaAuth.
deact Authentication is not done. When this value is selected, the

PTMSI signature mode ptmsiSignatureMode, the
ciphering mode cipheringMode and the UMTS ciphering
mode umtsCipheringMode are not effective even if the
value is set to true.
The IMEI request mode imeiRequestMode parameter cannot be set to true, if

the IMEI check mode imeiCheckMode parameter is set to false.
If the ciphering mode cipheringMode parameter is set to false, the changes of
the attach restriction attachRestriction parameter do not affect any attach or
routing area update procedures, because the ciphering is not in use.
If the UMTS ciphering mode umtsCipheringMode parameter is set to false, the
changes of the UMTS attach restriction umtsAttachRestriction parameter do
not affect any attach or routing area update procedures, because the UMTS
ciphering is not in use.
2.2 GPRS session management (Features SG01012 and

SG02157)
Session management (SM) handles the establishment and release of the connections to
the IP network outside the GPRS network. When a subscriber changes a routing area, SM
handles the re-establishment of these connections to the new SGSN. SM handles the
subscriber's authentication functions when the establishment or release of these
connections is requested.
Session management handles the following procedures:

Mobile-requested packet data protocol (PDP) context activation with which the MS can
create a connection to the IP network

SGSN User Guide
Mobile-requested PDP context deactivation with which the MS can remove a connection
to the IP network
Network-requested PDP context deactivation with which the network can remove the
connection of the MS to the IP network
Operator-initiated PDP context modification with which the operator can modify the
active PDP context parameters by changing the subscribed PDP context parameters
MS-initiated PDP context modification with which the MS can initiate PDP context
modification while the PDP context is active
Gateway GPRS support node (GGSN) initiated modification with which the GGSN can
modify the parameters (QoS, PDP address) while the PDP context is active
BSS packet flow context (PFC) procedures to describe the packet flow QoS characteristics
(ABQP) for data transmission in A/Gb
SGSN provides short message service (SMS)
The same procedures are also supported as S4-SGSN in Release 8 architecture.
This feature is a union of the following features: GPRS session management (SG01012) and
Multiple PDP contexts for one subscriber (SG02157).
2.2.1 GPRS session management (Feature SG01012):

feature summary
The session management (SM) establishes, modifies, and removes the connections of a
subscriber to the external IP network. This means that the SM handles PDP context
activation, modification, and deactivation. Support of session management allows the
end user to upload and download data via the GPRS network.
Table 9: GPRS session management (Feature SG01012): feature summary
Function Impact
Compliance This is a Nokia proprietary feature.
Capacity None

SGSN User Guide
Function Impact
Interworking/dependent Features related only to GPRS session management (SG01012):

features • Override of requested APN in SGSN (Feature SG01074)
• IP multimedia support (Feature SG01043)
• HSDPA, HSUPA Support and HSPA+ (Features SG02104, SG01113,
SG02198)
• Quality of service (Features SG01002, SG01007, SG01027, SG01122,
SG01245, SG01262, SG02170)
• QoS control for roaming subscribers (Feature SG01067)
• GTP information sending (Feature SG01082)
• PDP Context mass deactivation protection (Feature SG01096)
• Intelligent GGSN selection (Features SG01116, SG01212, SG01218,
SG01234, SG01255, SG01260, SG03067)
• APN dedicated prepaid (Feature SG01066)
• Direct tunnel and smart device direct tunnel signaling optimization
(Features SG01221, SG02017)
• IMEI-based APN override (Feature SG02019)
• APN conversion and correction (Feature SG02215)
Features related to GPRS session management (SG01012) and GPRS
mobility management (SG01011):
• Packet data transfer
• GPRS subscriber data management (Features SG01031, SG01246)
• SGSN charging (Features SG01015, SG01118, SG01189, SG02193)
• Performance management (Features SG01016, SG01028, SG01085,
SG01131)
• Quality of service (Features SG01002, SG01007, SG01027, SG01122,
SG01245, SG01262, SG02170)
• Lawful interception (Features SG01064, SG01152)
• Overload control (Feature SG01037)
Restrictions None

SGSN User Guide
Function Impact
Conguration Session management:

management Command securityParam, parameters attachRestriction,
umtsAttachRestriction. See Conguring 2G ciphering.
Command sgsnLocalEndPtCfg (GNSGSN), parameters gni,
gni6, goi. For step examples, see Conguring IMEI-based APN
override and Integrating CMM.
Command plmnParam (ETPLMN or ROAMINGPLMN), parameter
defaultApnOi (see Gateway and APN control features and an
example of APN conguration in Conguring IMEI-based APN override.)
Command plmnParam, parameters controlling authentication and
IMEI check procedures and repetition rates for PDP context activation
and deactivation:
• gbMoPdpActImei
• iuMoPdpActImei
• gbMoPdpDeaImei
• iuMoPdpDeaImei
• gbMoPdpActAuth
• iuMoPdpActAuth
• gbMoPdpDeaAuth
• iuMoPdpDeaAuth
• pdpActImeiChk
• pdpDeactImeiChk
Related to GPRS session management (SG01012) and GPRS mobility
management (SG01011):
Command securityParam, parameters authenticationMode,
imeiCheckMode
Command plmnParam (ETPLMN or ROAMINGPLMN), parameters
• homePlmn
• gbMncl
• iuMncl
• blacklistImeiEffect
• blackListEffect
Counters Counter group: GPRS Session Management (002)
Alarms 0126 PDP OVER DEFINED LIMIT

2012 ERROR IN FILE OPENING
2282 ACCESS SERVICE INITIALIZATION FAILED
2786 CALLS FAILING DUE TO OVERLOAD
Feature ID SG01012

SGSN User Guide
2.2.2 Multiple PDP contexts for one subscriber (Feature

SG02157): feature summary
With this feature it is possible for a subscriber to have more than one active PDP
contexts. Subscribers can use different kinds of services at the same time without service
breakouts, for example, browsing or e-mail usage is not interrupted due to an MMS. The
subscriber can activate up to eleven PDP contexts simultaneously.
Table 10: Multiple PDP contexts for one subscriber (Feature SG02157): feature summary
Function Impact
Capacity It is possible for the subscriber to activate one to four PDP contexts
simultaneously. The maximum allowed number of PDP contexts for
one subscriber is eleven.
Interworking/dependent GPRS mobility management (SG01011)

features
Restrictions If the maximum amount of PDP contexts is reached in the SGSN or

PAPS, it is not possible to activate the rst, second, third, or fourth
PDP context for the subscribers.
Conguration Command features, parameter multPdpCtxSubs

management Command prFile, parameter restrict11PdpCtx
Counters None
Alarms None
Feature ID SG02157
2.2.2.1 Configuring multiple PDP contexts for one

subscriber
The procedure includes steps for activating the Multiple PDP contexts for one subscriber
feature, configuring the maximum number of PDP contexts per subscriber, and
configuring a UTPFIL patch when needed.

SGSN User Guide
Procedure
1 Activate feature Multiple PDP contexts for one subscriber.
cmm features modify multPdpCtxSubs --status true
2 Configure the maximum number of PDP contexts per subscriber.
For maximum 4 PDPs per subscriber, set parameter restrict11PdpCtx to true

(default):
cmm prFile modify restrict11PdpCtx --status true
To increase the maximum allowed number of PDP contexts per subscriber (maximum 11
PDPs), set the parameter to false:
cmm prFile modify restrict11PdpCtx --status false
3 If restrict11PdpCtx is false, provision a UTPFIL patch.
If you increase the maximum allowed number of PDP contexts per subscriber to 11
PDPs, you need to increase the read bytes of messages from sockets by using a UTPFIL
file patch.
3.1 Look for the free records in UTPFIL file.
By giving the following command, you can find out how many records exist.
cmm patchParameter list
Step result
The following output will be shown. In this example, there is one record.
+----------------+
| patchParameter |
+----------------+
| 1 |
+----------------+
3.2 Create the UTPFIL patch record using the free record found in the previous
step.
Step example
In this example, this is the record no.2 (since record no.1 is already taken). The
record 2 will be provided last in the CLI. The value range is 1600-3500 (decimal)
and it should be given in hex. For example, if the new value is 2200 bytes (or 898

SGSN User Guide
in hex), then the patched value should be given as follows:
cmm patchParameter create --appId 69E --paramId 6 --value

898 2
Step result
The following output will be shown.
+----------------+-------+
| Field | Value |
+----------------+-------+
| patchParameter | 2 |
| appId | 69E |
| paramId | 6 |
| value | 898 |
+----------------+-------+
3.3 Restart the patched units.
2.3 Direct tunnel and smart device direct tunnel signaling

optimization (Features SG02017 and SG01221): feature
summary
The direct tunnel feature provides a direct user plane tunnel between the RAN and the
GGSN/S-GW when transporting user plane information. This means that the 3G access
user plane tunnel bypasses the SGSN. The user plane tunnel is created directly between
the RAN and the GGSN/SGW through the IP backbone.

SGSN User Guide
Table 11: Direct tunnel and smart device direct tunnel signaling optimization (Features
SG02017 and SG01221): feature summary
Function Impact
Compliance • 3GPP TS 23.060 General Packet Radio Service (GPRS); Service

description; Stage 2. Release 7, March 2007
• 3GPP TS 29.060 General Packet Radio Service (GPRS); GPRS
Tunneling Protocol (GTP) across the Gn and Gp interface.
Release 7, March 2007
Capacity Perform PDP context update in every RAB assignment. This

increases the number of PDP context updates. If the UE has
frequent RAB assignments and therefore, the number of PDP
context updates increases too much, the creation of the
direct tunnel can be restricted. For more information, see
Conguring direct tunnel. The load impact depends on the
traffic prole, mobile behavior and the type of services used.
Interworking/dependent features I-HSPA Enhancement (Feature SG01142)
Restrictions For the restrictions of this feature, see the SGSN Feature
Overview.
Conguration management Command feature, parameter directTunnelLicence

Command prFile, parameter dtRestrBasedOnTimer
Command apnList, rncParamSet and sgsnTimer
Charging None
Counters • M021C007 / PEAK ATTACH IU USERS

• M021C049 / PEAK IU PDP CONTEXTS
• M029C031 / GTP BYTES SENT DL PEAK
• M021C059 / DIRECT TUNNEL PDP CONTEXT PEAK
• M021C061 / DIRECT TUNNEL CHANGES TWO TUNNEL TO
DIRECT TUNNEL
• M017C006 / IU SUCCESSFUL PDP CONTEXT MODIFICATION
BY SGSN
Alarms None
Feature ID SG02017 and SG01221
2.3.1 Configuring direct tunnel

This procedure includes steps for activating the feature, configuring a selective APN and
RNC support for direct tunnel parameter in the SGSN, and restricting direct tunnel

SGSN User Guide
frequent establishments.
Procedure
1 Activate the feature.
cmm features modify directTunnelLicence --status true
2 Configure a selective APN.
Step example
cmm apnList create TTCN3.A.P.N.DT --oneGtpTunnel true
Step result
To delete the entry, use the command cmm apnList delete TTCN3.A.P.N.DT
3 Configure RNC support for direct tunnel parameter in the SGSN.
cmm rncParamSet modify 1 --rncSupportForDirectTunnel true

3.1 Show RNC 1.
cmm rnc show rnc1
3.2 Show RNC parameter set 1.
cmm rncParamSet show 1
4 Restrict direct tunnel frequent establishments.
4.1 Activate DT reset based on timer.
cmm prFile modify dtRestrBasedOnTimer --status true
4.2 Define the time period for monitoring direct tunnel establishments.
cmm sgsnTimer modify config --dtEstabTimer <timer in seconds>
2.4 SRNC relocation (Feature SG01161): feature summary

The SRNC relocation feature allows an operator to offer higher service quality, especially
with real-time service classes. With this feature, a mobile station can perform seamless
inter-RNC, inter-PAPS, and inter-SGSN changes, because the interruptions in the data
transfer are shorter and with no noticeable gaps in service continuity. Thus, the SRNC
relocation feature brings clear benefits to the operator by improving the end-user

SGSN User Guide
experience.
Table 12: SRNC relocation (Feature SG01161): feature summary
Function Impact

description; Stage 2
3GPP TS 25.413 UTRAN Iu interface Radio Access Network Application
Part (RANAP) signaling
3GPP TS 29.060 General Packet Radio Service (GPRS); GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface
3GPP TS 29.274 Evolved Packet System (EPS); Evolved General Packet
Radio Service (GPRS) Tunnelling Protocol for Control plane (GTPv2-C);
Stage 3
Capacity Not applicable
Interworking/dependent 3G Access Support (Feature SG02001)

features GPRS mobility management (Feature SG01011)
GPRS session management (Feature SG01012)
Restrictions The SNRS Relocation feature is always enabled in the SGSN; it cannot
be deactivated. The SRNC Relocation feature must be supported in all
the involved radio network controllers and SGSNs.
Conguration Not applicable

management
Counters None
Alarms None
Feature ID SG01161
2.5 GPRS Subscriber data management (Features

SG01031, SG01246, f60210-02, f60210-03, f60210-04
and f60210-16): feature summary
The purpose of this feature is to retrieve, store, maintain, delete and output subscriber
data in subscriber database.

SGSN User Guide
Table 13: GPRS Subscriber data management (Features SG01031, SG01246, f60210-02,
f60210-03, f60210-04 and f60210-16): feature summary
Function Impact
Compliance This is a Nokia proprietary feature
Interworking or dependent • GPRS mobility management (Feature SG01011)

features • GPRS session management (Feature SG01012)
• Quality of Service (Feature SG01027)
Restrictions Functionality of feature Subscriber information inquiry

(Feature SG01246) is not implemented.
Conguration management Command cmm prFile, parameter: grIfEnhancements

Command cmm system, parameter: subsDataKeepMode
Command cmm subscribers, parameter: imsi, imei,
msisdn
Counters None
Alarms None
Feature ID SG01031, SG01246, f60210-02, f60210-03, f60210-04,

f60210-16
2.5.1 Displaying and deleting subscriber data

You can filter subscribers according to various criteria, output part of the subscriber data
stored in the CMM's subscriber databases, and also delete subscriber data when
necessary.
Procedure
1 Filter subscriber data.
The cmm subscriber count command outputs the number of subscribers who
comply with the filtering criteria:

SGSN User Guide
--emmState {registered,deregistered}
--ecmState {connected,idle}
--filterType {attachedPerPaps,attachedPerPapsPerRat}
Parameters emmState and ecmState apply to UEs in E-UTRAN (MME subscriber data).
Filter types attachedPerPaps and attachedPerPapsPerRat apply to SGSN

subscriber data.
2 Display subscriber data.
The cmm subscriber show command outputs detailed UE context data.
cmm subscriber show
[--imsi <digits>]
[--imei <digits>]
[--msisdn <digits>]
Step example
cmm subscriber show --imsi 310012001001001
3 Delete subscriber data.
When needed, you can delete subscriber data manually from the database. For example,
in some fault cases a subscriber's data may remain in the database even though it
should have been removed, and the removal must be done manually using a command.
Deleting a subscriber manually from the database initiates a purge procedure towards
the HSS.
cmm subscriber delete
[--imsi <digits>]
[--imei <digits>]
Step example
cmm subscriber delete --imsi 310012001001002

SGSN User Guide
2.6 IPv6 and dual stack PDP context support (Feature

With this feature, the number of PDP context activations is reduced. In a single IPv4v6
PDP context, the UE gets two IP addresses (IPv4 and IPv6).This reduces the overhead on
the SGSN significantly and optimizes the utilization of the radio resources.
Table 14: IPv6 and dual stack PDP context support (Feature SG01000): feature summary
Function Impact
Compliance None
Capacity None
Restrictions None
Conguration Command features, parameters ipv6UserLayer,

management dualStackPdp
Command prFile, parameters dualStackPdpCtxt,
sgwDualStackSupport
Counters PAPS level:

• M021C117 / PAPS USER AVG DUAL STACK PDP CONT SUM
• M021C118 / PAPS USER AVG DUAL STACK PDP CONT DEN
• M021C119 / PAPS USER PEAK DUAL STACK PDP CONT
Charging In case of a Dual Stack PDP context activation, the CG will NOT receive
the dual stack PDP type (8D) and the two addresses IPv4 and IPv6.
Instead, it will receive single stack data, IPv4 PDP type (21) and IPv4
address. The new eld, Served PDP Address Ext, will not be visible in
this case and the IPv4 address will be stored in the existing Served PDP
Address eld.
Alarms None
Feature ID SG01000
2.6.1 Configuring IPv6/dual stack on user layer

The procedure includes steps for activating IPv6/dual stack on user layer and related
prFile parameters.

SGSN User Guide
Procedure
1 Activate IPv6/dual stack on user layer.
1.1 Activate IPv6 on user layer.
cmm features modify ipv6UserLayer --status true
1.2 Activate dual stack on user layer.
cmm features modify dualStackPdp --status true
2 Activate related prFile parameters.
As many nodes (S-GW/P-GW, GGSN, CGF, LIG) in the evolved packet core network are
affected by this feature, the control has been implemented with the help of the
following parameters of the prFile command:
dualStackPdpCtxt
This parameter should be turned on only if other S-GW/P-GW in the network is
capable of handling dual stack PDP context information.
sgwDualStackSupport
This parameter should be turned on only if other GGSNs in the network are capable
of handling dual stack PDP context information.
2.1 Activate S-GW dual stack support.
cmm prFile modify dualStackPdpCtxt --status true
2.2 Activate dual stack PDP context.
cmm prFile modify sgwDualStackSupport --status true
Note:
When only one of the feature dualStackPdp or the prFile

dualStackPdpCtxt is set to True, the dual stack PDP context functionality is
supported by the SGSN.
If both the feature dualStackPdp and the prFile dualStackPdpCtxt are

set to True, the dual stack PDP context functionality is not supported by the
SGSN.

SGSN User Guide
2.7 RIM procedure support (Features SG01024 and

The RAN Information Management (RIM) procedure support feature is used by the base
station controllers (BSCs) to exchange information with each other through the SGSN.
This feature can provide faster inter-access mobility for end users without the actual
handover feature. It can also provide shorter service breaks and reduced effects to
service delivery.

SGSN User Guide
Table 15: RIM procedure support (Features SG01024 and SG01232): feature summary
Function Impact
Capacity The capacity impact depends on the application using the RIM
procedures, that is, on the frequency at which the application
communicates through the core network and the size of the
application data to be relayed.
Interworking/dependent Multipoint Gb (Feature SG01023)

features
Restrictions None
Conguration management Command features, parameters

externalNaccSupport and r9RimFor2g3g
Command prFile, parameter rimRel8DnsAllowed
Counters GPRS Data Measurement (003):

• M003C098 / RELAYED RAN INFORMATION MESSAGES
• M003C099 / DESTINATION NOT FOUND FOR RAN
INFORMATION MESSAGE
• M003C100 / RELAYED RAN INFORMATION REQUEST
MESSAGES
• M003C101 / DESTINATION NOT FOUND FOR RELAYED RAN
INFORMATION REQUEST
Alarms None
External interfaces • BSC

• NetAct
• Gb
• Gn
• Iu-PS
• S3
Subscriber interfaces The RIM Procedure Support feature has an indirect effect on
the subscriber interface that depends on the BSC application
using RIM.

SGSN User Guide
2.8 Quality of service (Feature SG01027): feature

summary
This feature provides support for QoS administration on SGSN level, PLMN level and RNC
level. The Quality of service (QoS) feature ensures that a service or an application is
delivered to the end user in a satisfactory time frame and level of quality. It does not
create additional bandwidth but allows the existing bandwidth to be managed, so that
packets are transported efficiently through the network.
Table 16: Quality of service (Feature SG01027): feature summary
Function Impact
Compliance • 3GPP TS 23.060: General Packet Radio Service (GPRS) Service

description
• 3GPP TS 23.107: Quality of Service (QoS) concept and
architecture
• 3GPP TS 24.008: Mobile radio interface Layer 3 specication;
Core network protocols
• IETF RFCs 2475, 2597 and 2598
• 3GPP TS 23.203: Policy and charging control architecture
• 3GPP TS 23.401: General Packet Radio Service (GPRS)
enhancements for Evolved Universal Terrestrial Radio Access
Network (E-UTRAN) access
Capacity None
Required features For the 3G access: Iu over IP (Feature SG01119)
Interworking/dependent • Conversational QoS (Feature SG01122)

features • Streaming QoS (Feature SG01007)
• Streaming quality optimization (Feature SG02170)
• Release 8 - pre-Release 8 QoS mapping (Feature SG01262)
• Pre-emption support (S6d) (Feature SG01245)
Restrictions In 2G access, the conversational traffic class is not supported.

3GPP has not standardized the conversational class in 2G access
SGSN.
Parameter delayedIratMod (command prFile) needs to be
enabled for QoS negotiation based on HLR/HSS subscription on
relocation/handover scenarios.
Conguration management Command prFile, parameters qciMapR8ToR99,

delayedIratMod, preemptionSupR8

SGSN User Guide
Function Impact
Command features, parameters conversationalQoS,

streamingQoS, streamQualOpt
Parameters of the qosConf command
Command plmnParam, parameters
• qosRoamingAllowed
• plmnSpecQosRParInUse
• trafficClass
• traffHandlingPrio
• allocRetention
• maxBitRateForUl
• maxBitRateForDl
• guaranBitRateUl
• guaranBitRateDl
• plmnEArpHPriority
• plmnEArpMPriority
• plmnEArpPCap
• plmnEArpPVul
• earp
Command rncParamSet, parameters
• maxDlBitrateForRab
• maxQuaranteedDlBitRateForRab
• maxUlBitrateForRab
• maxGuaranteedUlBitrateForRab
• rel8RncSupported
• epsBearerPresSupported
• ueAmbrSupported
Counters See Counters
Alarms None
Feature ID SG01027
2.8.1 Configuring QoS

QoS provisioning involves feature activation (prFile), QoS parameter provisioning
(qosConf), PLMN QOS roaming configuration (plmnParam), and RNC-specific QoS
configuration (rncParamSet).
Procedure
1 Activate QoS features.
The following features are disabled by default (status false):

SGSN User Guide
Table 17: QoS features (prFile)
Parameter Description
qciMapR8ToR99 Enabling/Disabling feature capability for Release 8 and pre Release 8

QoS mapping (SG01262).
delayedIratMod This parameter determines whether SGSN will delay the sending of
IRAT RAU related Update PDP Context Request towards GGSN and will
send it only after PDP subscription is received from HLR during
update location procedure to prevent PDP context modication
related collisions (SGSN and PCRF initiated) and to optimize the
signaling.
preemptionSupR Enabling/Disabling feature capability for pre-emption support for rel 8

8 subscribers (SG01245).
Step example
cmm prFile modify qciMapR8ToR99 --status true
2 Configure QoS parameters.
Table 18: QoS configuration parameters (qosConf)
Parameter Description Type Default
gtpWredSwitch This parameter denes whether the inUse, inUse

Random Early Detection (RED) algorithm is notInUse
used in the GPRS Tunneling Protocol (GTP)
buffer.
gbWredSwitch This parameter denes whether the inUse, inUse

Enhanced Random Early Detection (ERED) notInUse
algorithm is used in the Gb buffer.
scheduleSwitch Scheduling in Gb buffer: this parameter inUse, inUse

denes whether the scheduling algorithm notInUse
is used.
weightPri1 This parameter denes the relative 25..90 (in 50

capacity of delay class 1 compared to the steps of 5)
other delay classes.



SGSN User Guide

dscpConversional Differentiated services codepoints The value 101110

mapping for conversational. of the
parameter
is non-
modiable.
dscpStreaming Differentiated services codepoints The value 100010

mapping for streaming. of the
parameter
is non-
modiable.
dscpLevel1 Differentiated services codepoints The value 011010

mapping for interactive priority level 1. of the
parameter
is non-
modiable.

parameter
is non-
modiable.

parameter
is non-
modiable.
dscpBackground Differentiated services codepoints The value 000000

mapping for background. of the
parameter
is non-
modiable.
hPriority EPS bearer ARP high priority. 1..13 5
mPriority EPS bearer ARP medium priority. 2..14 10
pcap Pre-emption capability. enable, disable

disable
pvul Pre-emption vulnerability. enable, enable

disable

SGSN User Guide
weightPri5 Weight for scheduling non-guaranteed 0..200 200

streaming. This parameter denes the
weight value for non-guaranteed
streaming traffic queue. The priority of
streaming queue is set to be guaranteed
by default. If other queues start to ll up,
the streaming queue weight is
downgraded to operator dened non-
guaranteed weight value until traffic is
balanced, and the streaming queue can
start to use higher priority again.
imbr This parameter denes the maximum bit 0..472 472

rate for UTRAN to GERAN in ISHO. The
values range from 0 to 63 kbit/s in steps
of 1 and from 64 to 472 kbit/s in steps of
8. IMBR has to be greater or same than
IGBR.
igbr This parameter denes the guaranteed 0..472 472

bit rate for UTRAN to GERAN in ISHO. The
values range from 0 to 63 kbit/s in steps
of 1 and from 64 to 472 kbit/s in steps of
8. IGBR has to be smaller or same than
IMBR.
trafClassRoam This parameter denes the traffic class Conversatio Interactive

which can be used by a roaming nal
subscriber at most. Streaming
Interactive
Background
trafHandPrioRoam This parameter denes the traffic 1..3 3

handling priority which can be used by a
roaming subscriber at most.
arpRoam This parameter denes the 1..3 3

allocation/retention priority which can be
used by a roaming subscriber at most.
downMaxRoam This parameter denes the maximum bit 0..168000 50

rate for downlink traffic for a roaming
subscriber.
upMaxRoam This parameter denes the maximum bit 0..46000 50

rate for uplink traffic for a roaming
subscriber.
upGbrRoam This parameter denes the guaranteed 0..46000 0

bit rate for uplink traffic for a roaming
subscriber.

SGSN User Guide
dwGbrRoam This parameter denes the guaranteed 0..168000 0

bit rate for downlink traffic for a roaming
subscriber.
epsHighPrioRoam EPS bearer ARP high prior for roaming 1...13 5

subscriber.
epsMedPrioRoam EPS bearer ARP medium prior for roaming 2..14 10

subscriber.
pcapRoam Pre-emption capability for roaming enable, disable

subscriber. disable
pvulRoam Pre-emption vulnerability for roaming enable, enable

subscriber. disable
earpRoam This parameter indicates the evolved ARP. 1..15 14
Note:
Operators can switch on or off both RED and WFQ algorithms and set WFQ
weights. The sum of weights has to be always exactly 100. The weight of a
lower priority can never be greater than the weight of a higher priority,
although they can be equal. When the weight is 0, the queue is served only
when there are no packets in other queues.
IETF RFCs (2475, 2597, and 2598) define the DSCP values used in IP networks.
Step example
cmm qosConf modify --pcap enable config
Step example
cmm qosConf modify --trafClassRoam Interactive config
Step example
cmm qosConf modify --trafClassRoam Interactive --pcap disable
config
3 Configure PLMN-specific QoS parameters.
Configure PLMN-specific QoS roaming configuration based on roaming agreement using

command plmnParam.

SGSN User Guide
Table 19: QoS roaming configuration parameters
qosRoamingAllowed With the QoS based roaming agreement you true, false true
can dene to allow QoS roaming.
• true - QoS roaming is allowed. Roaming
check is not performed, and QoS parameter
downgrade, according to QoS roaming list, is
not possible.
• false - QoS roaming is not allowed.
Roaming check must be performed
according to plmnSpecQosRParInUse
parameter value.
plmnSpecQosRParIn PLMN specic QoS roaming parameters in true, false false

Use use
• true -PLMN specic QoS roaming
parameters are in use. Roaming check is
performed according to PLMN specic
parameters.
• false - PLMN specic QoS roaming
parameters are not in use. Roaming check is
performed according to SGSN specic QoS
roaming subscribers parameters.
Note:
This parameter has impact only if the

parameter qosRoamingAllowed is set
to false
trafficClass This parameter denes the traffic class which • Interactive

can be used by roaming subscriber at most. Conversatio
nal
• Streaming
• Interactive
•
Background
traffHandlingPrio This parameter denes the traffic handling 1..3 3

priority which can be used by roaming
subscriber at most.
allocRetention This parameter denes the 1..3 3

allocation/retention priority which can be
used by roaming subscriber at most.
maxBitRateForUl This parameter denes the maximum bit 0..11500 50

rate for uplink for roaming subscribers.
maxBitRateForDl This parameter denes the maximum bit 0..28000 50

rate for downlink for roaming subscribers.
guaranBitRateUl This parameter denes the guaranteed bit 0..11500 0

rate for uplink for roaming subscribers.

SGSN User Guide
guaranBitRateDl This parameter denes the guaranteed bit 0..28000

rate for downlink for roaming subscribers.
plmnEArpHPriority ARP priority value for high priority. 1..13 5

plmnEArpHPriority should be less than
plmnEArpMPriority.
plmnEArpMPriority ARP priority value for medium priority. 2..14 10

plmnEArpMPriority should be less than
plmnEArpHPriority.
plmnEArpPCap Pre-emption capability. true, false false
plmnEArpPVul Pre-emption vulnerability. true, false true
earp Evolved allocation/retention priority. 1..15 14
Step example
cmm plmnParam modify ETPLMN --qosRoamingAllowed false
4 Configure RNC-specific QoS.
Create RNC-specific QoS configuration is using command rncParamSet.

SGSN User Guide
Table 20: RNC QoS parameters (rnsParamSet)
Parameter Description Default
maxDlBitrateForRab This parameter denes the maximum downlink 0

value for the RAB maximum bit rate (MBR)
supported in the RNC. The value is used by the
SGSN to downgrade the maximum bit rate value
according to the RNC capability.
maxQuaranteedDlBitRateF This parameter denes the maximum downlink 0

orRab value for the RAB guaranteed bit rate (GBR)
supported in the RNC. The value is used by the
SGSN to downgrade the guaranteed bit rate value
maxUlBitrateForRab This parameter denes the maximum uplink value 0

for the RAB guaranteed bit rate (GBR) supported
in the RNC. The value is used by the SGSN to
downgrade the guaranteed bit rate value
maxGuaranteedUlBitrateF This parameter denes the maximum uplink value 0

orRab for the RAB guaranteed bit rate (GBR) supported
in the RNC. The value is used by the SGSN to
downgrade the guaranteed bit rate value
rel8RncSupported RNC supports Rel 8. false
epsBearerPresSupported EPS bearer preservation is supported. true
ueAmbrSupported UE AMBR support in RNC parameter set. false
Step example
cmm rncParamSet modify 1 --maxDlBitrateForRab 42000
2.9 Conversational QoS (Feature SG01122): feature

summary
The Conversational QoS traffic class is valid only with 3G radio network (UTRAN), and
enables the network to transfer QoS information related to a flow of packets between
the SGSN and the RAN. Support for Conversational QoS traffic class in SGSN means
supporting the following QoS attributes: Guaranteed bit rate, Maximum bit rate, and
Transfer Delay. This feature supports services that require the highest QoS (transfer rate
and delay). Typical services mandating data stream to be carried with conversational
class: telephony and video telephony.

SGSN User Guide
Table 21: Conversational QoS (SG01122): feature summary
Function Impact
Compliance 3GPP TS 23.107
Capacity None
Required features Streaming QoS (Feature SG01007)
Interworking/dependent Quality of service (Feature SG01027)

features
Restrictions This feature requires that the Conversational QoS traffic class is
supported in the RNC, GW as well. The MS must also be able to
manage streaming applications.
The conversational QoS feature requires the streaming QoS
feature in order to function. In 2G access, the conversational traffic
class is not supported.
Conguration management Command features, parameter conversationalQoS

Command qosConf show to output QoS conguration
parameters.
Counters GPRS PAPS User Measurement (021):

• M021C040 / PAPS USER MIN CON PDP CONT
• M021C041 / PAPS USER PEAK CON PDP CONT
GPRS IPPS Throughput By Class Measurement (040):
• M040C004 / GTPU KBYTES DOWNLINK CONVERSATIONAL PER
BEARER CLASS
• M040C005 / GTPU PACKETS DOWNLINK CONVERSATIONAL PER
BEARER CLASS
• M040C006 / GTPU KBYTES UPLINK CONVERSATIONAL PER
BEARER CLASS
• M040C007 / GTPU PACKETS UPLINK CONVERSATIONAL PER
BEARER CLASS
• M040C026 / AVERAGE 3G PDP CONTEXTS CONVERSATIONAL PER
BEARER CLASS
• M040C027 MAXIMUM 3G PDP CONTEXTS CONVERSATIONAL PER
BEARER CLASS
Alarms None
Feature ID SG01122
2.10 Streaming QoS (Feature SG01007): feature summary

The Streaming QoS traffic class enables transferring QoS information related to a flow of
packets between the SGSN and the BSS/RAN in the Packet Flow Contexts. Support for

SGSN User Guide
Streaming QoS traffic class in SGSN means supporting the following QoS attributes:
Guaranteed bit rate, Maximum bit rate, and Transfer Delay. This feature supports a whole
new range of streaming services. Those services were originally targeted to be supported
by 3G networks, but they can now be offered in both 2G and 3G GPRS networks. Typical
services mandating data stream to be carried with Streaming class: tele-surveillance,
music clips, and audio email / recorded message.
Table 22: Streaming QoS (Feature SG01007): feature summary
Function Impact
Compliance Compliance with certain requirements of the 3GPP specications is

specically required: the BSS has to support the BSS packet ow
context (PFC) procedures
Capacity None
Interworking/dependent • Quality of Service (Feature SG01027)

features • Streaming Quality Optimization (Feature SG02170)
Restrictions This feature requires that the Streaming QoS traffic class is
supported in the BSS, GW as well. The MS must also be able to
manage streaming applications.
Conguration Command features, parameter streamingQoS

management Command qosConf show to output QoS conguration

• M021C036 / PAPS USER MIN STR PDP CONT
• M021C037 / PAPS USER PEAK STR PDP CONT
GPRS IPPS Throughput By Class Measurement (040):
• M040C020 / GTPU KBYTES DOWNLINK STREAMING PER BEARER
CLASS
• M040C021 / GTPU PACKETS DOWNLINK STREAMING PER BEARER
CLASS
• M040C022 / GTPU KBYTES UPLINK STREAMING PER BEARER CLASS
• M040C023 / GTPU PACKETS UPLINK STREAMING PER BEARER
CLASS
• M040C034 / AVERAGE 3G PDP CONTEXTS STREAMING PER BEARER
CLASS
• M040C035 / MAXIMUM 3G PDP CONTEXTS STREAMING PER BEARER
CLASS
Alarms None
Feature ID SG01007

SGSN User Guide
2.11 Streaming quality optimization (Feature SG02170):

feature summary
With this feature, the operator is able to override the MS requested MBR value with the
subscribed values on the HLR and the requested GBR value is applied an Operator defined
multiplier.
Table 23: Streaming quality optimization (Feature SG02170): feature summary
Function Impact
Compliance Compliance with certain requirements of the 3GPP specications is

specically required: the BSS has to support the BSS packet ow
context (PFC) procedures.
Capacity None
Interworking/dependent Quality of Service (Feature SG01027)

features
Restrictions This feature requires that the Streaming QoS traffic class is supported
in the BSS, GGSN, and the MS must also be able to manage streaming
applications.
Conguration Command prFile, parameter streamingOptAct

management Command features, parameter streamQualOpt
Counters None
Alarms None
Feature ID SG02170
2.11.1 Configuring streaming quality optimization

The SGSN has to change QoS negotiation so that the MS requested maximum bit rate
(MBR) value can be overridden according to the MBR value set in the HLR. The MS
requested guaranteed bit rate (GBR) value can also be overridden by the multiplied value
from the SGSN that the operator has configured. The feature requires activation and
provisioning.

SGSN User Guide
Procedure
1 Activate the Streaming quality optimization feature.
cmm features modify streamQualOpt --status true
2 Configure streaming quality optimization.
The prFile parameter streamingOptAct defines streaming quality optimization in

SGSN.
Table 24: Values of streamingOptAct
Value [0...10], 255 Impact
255 (default) no changes to the QoS negotiation
0 MBR uplink/downlink is overridden according to the HLR values
1…9 MBR uplink/downlink is overridden according to the HLR values, and

the GBR uplink/downlink values are multiplied by 1.1 - 1.9
10 (max.) MBR uplink/downlink is overridden according to the HLR values, and

the GBR uplink/downlink values are multiplied by 2.0
Step example
cmm prFile modify --streamingOptAct 7 streamingOptAct
To deactivate: cmm prFile modify --streamingOptAct 255

streamingOptAct
2.12 Release 8 to pre-Release 8 QoS mapping (Feature

SG01262)
With this feature, the operator is enabled to modify the fixed QoS mapping between
Release 8 and pre-Release 8 which is defined by 3GPP and gains more flexibility in order
to provide better service for selected subscribers in the network. This feature is
supported in 2G and 3G environments.
The operator has the flexibility to change the defined mapping using CMM CLI commands.
For example, QCI 8 could be mapped to Interactive traffic class THP2 instead of Interactive
traffic class THP3. The defined mapping will be applied for both Release 8 to pre Release 8

SGSN User Guide
QoS mapping and vice versa.
The default mapping is as follows:

QCI 1 ↔ CONV_Speech
QCI 2 ↔ CONV_TD150ms
QCI 3 ↔ CONV_TD80ms
QCI 4 ↔ STR
QCI 5 ↔ INT_THP1_SI
QCI 6 ↔ INT_THP1
QCI 7 ↔ INT_THP2
QCI 8 ↔ INT_THP3
QCI 9 ↔ BG
2.12.1 Configuring Release 8 to pre-Release 8 QoS

mapping
The feature requires activation as well as QoS mapping.
Procedure
1 Activate the Release 8 to pre Release 8 QoS mapping feature.
cmm prFile modify qciMapR8ToR99 --status true
2 Configure QoS mapping.

SGSN User Guide
Table 25: QCI mapping (command plmnParam)
Procedure / Parameter Description Type Default
Dene Traffic Class for Qci 1 Apply operator dened [1,2,3,4,10] 10

(tcForQci1) traffic class QCI 1
mapping.

mapping.

mapping.

mapping.
Dene Traffic Class for Qci 5 Apply operator dened [5,6,7,8,9,10] 10

mapping.

mapping.

mapping.

mapping.

mapping.
Note:
To avoid situations of inadvertently mapping a QCI to incorrect Release 99

parameters, SGSN considers GBR QCI (1 to 4) as one group and non-GBR QCI (5 to
9) as another group and allows mapping only within the same group. This way it is
ensured that it is not possible to map, for example, QCI 2 to INT_THP1 or QCI 6 to
CONV_TD150MS.

SGSN User Guide
Step example
cmm plmnParam modify --tcForQci9 10 ETPLMN
Step result
Verify the applied custom mapping: cmm plmnParam show ETPLMN
+------------------+--------------------+
| Field | Value |
+------------------+--------------------+
| plmnParam | ETPLMN |
| tcForQci9 | 6 |
+------------------+--------------------+
2.12.2 Release 8 - pre-Release 8 QoS mapping (Feature

The Release 8 - pre Release 8 QoS Mapping feature in S4-SGSN supports QoS mapping
between Release 8 QoS parameters and pre-Release 8 QoS parameters (standard) as well
as specific (non-standard) mapping based on operator's specific configuration.

SGSN User Guide
Table 26: Release 8 - pre-Release 8 QoS mapping (Feature SG01262): feature name: feature
summary
Function Impact
Compliance 3GPP TS 23.401 LTE; General Packet Radio Service (GPRS)

enhancements for Evolved Universal Terrestrial Radio Access Network
(E-UTRAN) access; Release 9 (Dec 2010)
Capacity None
Required features Release 8 architecture (Feature SG01235)

SGSN S4 Functionality
features
Restrictions None
Conguration Command prFile, parameter qciMapR8ToR99

management Command plmnParam, parameters tcForQci1 to tcForQci9
Counters None
Alarms None
Feature ID SG01262
2.13 Operator defined QCI (Feature f52059-01): feature

summary
The feature introduces SGSN support of operator defined QCIs for range 128-254 with
provisionable mapping to Rel 99 QoS.
Table 27: Operator defined QCI: feature summary
Function Impact
Compliance • 3GPP TS 23.401, General Packet Radio Service (GPRS)

Network (E-UTRAN) access
• 3GPP TS 23.107, Quality of Service (QoS) concept and architecture
Capacity Up to 32 operator specic QCIs are supported.

SGSN User Guide
Function Impact
Interworking/dependent • Streaming QoS (Feature SG01007)

features
Restrictions • The feature is only applicable for home subscribers.

• The feature applies only to default bearer procedures.
• In 2G access, the conversational traffic class is not supported.
• To support streaming class in GB, the streamWoPfcSupport
prFile parameter should be set to True.
Conguration Command gParms, parameter supportSgsnOperDefQci to

management enable the feature. Default value is No.
Command oprDefQciToRel99QosMapping, parameters
• qci
• trafficClass
• deliveryOrder
• maxSduSize
• deliveryOfErroneousSDUs
• residualBitErrorRatioNonRealTime
• residualBitErrorRatioRealTime
• sduErrorRatioNonRealTime
• sduErrorRatioStreaming
• sduErrorRatioConversational
• transferDelay
• trafficHandlingPriority
• sourceStatisticsDescriptorSpeech
• signalingIndication
• dscp
to dene the mapping between operator dened QCIs and Release
99 QoS parameter values.
Counters None
Alarms None
Feature ID f52059-02
2.13.1 Configuring operator defined QCI

Use the supportSgsnOperDefQci gParm to activate the feature and the
oprDefQciToRel99QosMapping command to map the operator defined QCIs and
Release 99 QoS parameter values.

SGSN User Guide
Procedure
1 Enable the feature.
Step example
cmm gParms modify --gParmName supportSgsnOperDefQci --gParmValue
Yes
2 Map operator specific QCI.
Step example
Configure operator specific QCI with interactive traffic class.
cmm oprDefQciToRel99QosMapping create --qci 210 --trafficClass

Interactive --deliveryOfErroneousSDUs accept --deliveryOrder Yes
--maxSduSize 1500 --residualBitErrorRatioNonRealTime 4*10^-3 --
sduErrorRatioNonRealTime 1*10^-3 --
sourceStatisticsDescriptorSpeech false --dscp 32 --
trafficHandlingPriority 3 --signalingIndication Yes
Step example
Configure operator specific QCI with conversational traffic class.
cmm oprDefQciToRel99QosMapping create --qci 230 --trafficClass

Conversational --deliveryOfErroneousSDUs accept --deliveryOrder
Yes --maxSduSize 1500 --residualBitErrorRatioRealTime 1*10^-1 --
sduErrorRatioConversational 1*10^-2 --
sourceStatisticsDescriptorSpeech true --dscp 32 --transferDelay
300
Step example
cmm oprDefQciToRel99QosMapping create --qci 200
Step result
In this example, all parameters have the default values.

SGSN User Guide
+----------------------------------+------------+
| Field | Value |
+----------------------------------+------------+
| oprDefQciToRel99QosMapping | 200 |
| qci* | 200 |
| deliveryOfErroneousSDUs | discard |
| deliveryOrder | No |
| dscp | 0 |
| maxSduSize | 1500 |
| residualBitErrorRatioRealTime | 1*10^-5 |
| residualBitErrorRatioNonRealTime | 1*10^-5 |
| sduErrorRatioConversational | 1*10^-3 |
| sduErrorRatioNonRealTime | 1*10^-4 |
| sduErrorRatioStreaming | 1*10^-4 |
| signalingIndication | No |
| sourceStatisticsDescriptorSpeech | false |
| trafficClass | Background |
| trafficHandlingPriority | 0 |
| transferDelay | 10 |
+----------------------------------+------------+
2.14 2G ciphering GEA 1/2/3 (Features SG01009,

SG01034, SG01175 and f60210-19): feature summary
Ciphering is required in order to support information confidentiality and integrity. This
feature makes it possible to enable ciphering of both user data and signaling between the
SGSN and the MS. SGSN supports 2G ciphering algorithms GEA1, GEA2, and GEA3. 2G
ciphering requires provisioning.

SGSN User Guide
Table 28: 2G ciphering GEA 1/2/3 (Features SG01009, SG01034, SG01175 and f60210-19):
feature summary
Function Impact
Compliance • 3GPP TS 43.020 Security related network functions

• 3GPP TS 33.102 3G Security
• 3GPP TS41.061 GPRS ciphering algorithm requirements
• 3GPP TS 55.216 Specication of the A5/3 encryption algorithms for GSM
and ECSD, and the GEA3 encryption algorithm for GPRS;
• 3GPP TS 44.064 Logical Link Control (LLC) layer specication
• ETSI condential specication Specication of the GPRS Encryption
Algorithm (GEA2)
Capacity Usage of SW based 2G ciphering impacts the system performance as it

consumes part of the computational resources that are shared with other
call processing functions in PAPS. See SGSN Feature Overview.
Interworking/depende • SGSN support for overload mechanism improvements for PAPS

nt features (f60210-21). The overload control (OLC) framework is based primarily on
CPU load monitoring of SGSN processes, that is when a CPU limit is
reached new 2G procedures (attaches, pdp activations and so on) can be
dropped. For ciphering, GIP process is monitored.
• Features SG01175, SG01034
Restrictions None
Conguration Command feature, parameter cipheringGea3

management Command plmnParam, parameter cipherMode
Command securityParam, parameters cipheringMode,
authenticationMode, attachRestriction (2G)
Charging None
Counters None
Alarms None
Feature ID SG01009, SG01034, SG01175 and f60210-19
2.14.1 Configuring 2G ciphering

All active connections can be ciphered. Ciphering can be turned ON or OFF for the whole
SGSN subscribers' access to the network can be restricted. Activate ciphering parameters
at any time other than that of the installation.

SGSN User Guide
Purpose
Parameters related to ciphering on SGSN and PLMN level:
Ciphering mode parameter (cipheringMode) defines the ciphering mode in the SGSN in
2G access mode. You can enable or disable ciphering for all 2G subscribers in the entire
SGSN. This procedure does not require the restart of the SGSN. Authentication must be
enabled using the authenticationMode parameter. Both parameters belong to the
cmm command group securityParam.
PLMN ciphering mode (cipherMode) parameter defines the ciphering mode in the PLMN
level. This parameter belongs to cmm command group plmnParam.
Attach restriction parameter (attachRestriction) can be used to prevent network
access for those subscribers whose profile does not support ciphering. The parameter
belongs to the cmm command group securityParam. Parameter
attachRestriction is used to restrict 2G access, while parameter
umtsAttachRestriction is used to restrict 3G access.
Table 29: Ciphering parameters
Parameter Values Description
cipheringMode true ciphering mode is in use (SGSN level)
false ciphering mode is not in use (SGSN level)
authenticationMode act, whenNeeded authentication mode is in use (SGSN level)
deact authentication mode is not in use (SGSN

level)
attachRestriction true attach restriction is in use (SGSN level)
false attach restriction is not in use (SGSN level)
cipherMode true ciphering mode is in use (PLMN level)
false ciphering mode is not in use (PLMN level)
SGSN functionality concerning the negotiation of GEA algorithm in PAPS is based on the
following decisions:
If ciphering mode or PLMN ciphering mode are false, an un-ciphered connection is
used, regardless which GEA algorithm the MS supports. (Access restriction parameter will
have no impact.)
If ciphering mode and PLMN ciphering mode are true and the MS and the SGSN have at
least one version of the GEA algorithm in common, the network selects one of the

SGSN User Guide
mutually acceptable versions of the GEA algorithms for use on that connection. (In case
of more than one mutually acceptable version, the strongest one should be used. Order
of priority: GEA3-GEA2-GEA1.)
If ciphering mode and PLMN ciphering mode are true and the MS and the SGSN have no
versions of the GEA algorithm in common:
If access restriction is false, an un-ciphered connection is used
If access restriction is true, the connection should be rejected with cause GPRS
services not allowed in this PLMN.
Procedure
1 Configure authentication mode.
cmm securityParam modify config –-authenticationMode whenNeeded
The values are act, deact (deactivates ciphering mode), and whenNeeded (default).
2 Configure ciphering mode.
cmm securityParam modify config --cipheringMode true
3 Configure PLMN level ciphering mode.
cmm plmnParam modify <PLMN> --cipherMode true
4 Configure attach restriction.
cmm securityParam modify config --attachRestriction true
5 If needed, enable GEA3 algorithm.
cmm features modify cipheringGea3 --status true
2.15 UMTS authentication (Feature SG01054): feature

summary
With this feature, SGSN provides universal mobile telecommunication system (UMTS)
authentication and key agreement in the serving GPRS support node (SGSN) for UMTS
users attached to a GSM BSS.

SGSN User Guide
Table 30: UMTS authentication (Feature SG01054): feature summary
Function Impact
Compliance 3GPP TS 33.102 3G Security; Security Architecture
Capacity The size of a UMTS quintuplet in a MAP message is slightly

over twice the size of a GSM triplet. Fetching authentication
vectors from the AuC increases the signaling load of the HLR.
Interworking or dependent None

features
Restrictions None
Conguration management None
Counters None
Alarms None
Feature ID SG01054
2.16 Network identity and time zone support (Feature

This feature supports the network identity and time zone (NITZ) functionality in SGSN
network supported areas of CMM i.e. the GERAN and UTRAN (2G and 3G. It provides the
means for serving PLMNs to transfer the full name of network, the short name of
network, universal time, local time zone (LTZ) and network daylight saving time (DST) to
mobile stations (MS).

SGSN User Guide
Table 31: Network identity and time zone support (Feature SG02206): feature summary
Function Impact
Compliance • 3GPP TS 22.042 V8.0.0: 3rd Generation Partnership Project,

Technical Specication Group Services and System Aspects,
Network Identity and Time Zone (NITZ), Service description,
Stage 1 (Release 8).
• 3GPP TS 23.038 V6.1.0: 3rd Generation Partnership Project,
Technical Specication Group Terminals, Alphabets and
language-specic information (Release 6).
Capacity None
features
Restrictions None
Conguration management Command features, parameter networkIdTimeZone.

Command system, parameter fullNetwName to dene
the full network name of the network operator.
Command system, parameter shortNetwName to dene
the short network name of the network operator.
Charging None
Counters None
Alarms None
Feature ID SG02206
2.17 IP multimedia support (Feature SG01043): feature

summary
The IP Multimedia Core Network (IM CN) subsystem allows PLMN operators to offer their
subscribers multimedia services based on and built upon internet applications, services,
and protocols.

SGSN User Guide
Table 32: IP multimedia support (Feature SG01043): feature summary
Function Impact
Compliance • 3GPP TS 24.008, Mobile Radio Interface Layer 3 Specication;

Core Network Protocols, Rel. 5
• 3GPP TS 29.060, General Packet Radio Service (GPRS); GPRS
Tunnelling Protocol (GTP) across the Gn and Gp Interface, Rel.
5
Capacity None
features
Restrictions None
Conguration management Command features, parameter

ipMultimediaSupport
Alarms None
Counters None
External interfaces • Interface between SGSN and MS

The transferring of PCO IE (Protocol Conguration Options
Information Element) is included in messages related to
secondary PDP context activation, PDP context modication,
and PDP context deactivation.
• Interface between SGSN and GGSN (Gn interface)
The transferring of PCO IE is included in messages related to
PDP context updating and PDP context deletion.
The GGSN must be able to transport data through the Gn
interface.
Feature ID SG01043
2.18 SGSN support for IPv6 and dual stack (Feature

This feature adds support for IPv6 and dual stack on SGSN interfaces S6d, S13', X1_1 and
Bp.

SGSN User Guide
Table 33: SGSN support for IPv6 and dual stack (Feature f12101-02): feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions • The only SGSN interfaces that support IPv6 and dual stack are S6d,
S13’, X1_1 and Bp.
• For intra-CMM inter-RAT scenarios in MME/SGSN, dual stack needs to
be congured to S3 (MME).
• As only one LIB IP address is received from LIC, and that address is
used also for X3 (which is IPv4 only), in MME/SGSN also X2 needs to be
congured IPv4 only.
Conguration See Integrating CMM and Lawful Interception.

management
Counters None
Alarms None
2.19 SGSN support for IPv4/IPv6 dual stack transport for

Gb (Feature f12101-04): feature summary
Apart from IPv4, the SGSN supports IPv6 at transport layer for both GB NS and GB Auto
CMM interfaces for both control and user plane traffic.

SGSN User Guide
Table 34: SGSN support for IPv4/IPv6 dual stack transport for Gb: feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent SGSN support for IPv4/IPv6 dual stack transport for Iu-U/Gn-U/Gn-C
features (f12101-06)
SGSN support for IPv4/IPv6 dual stack transport for Iu-C (f12101-05)
Restrictions None
Conguration Commands serviceIP and nsvc

management Command nse, parameter nseIpType
Counters None
Alarms None

Iu-C (Feature f12101-05): feature summary
Apart from IPv4 addresses, SGSN supports IPv6 addresses over control plane of the Iu
interface.

SGSN User Guide
Table 35: SGSN support for IPv4/IPv6 dual stack transport for Iu-C: feature summary
Function Impact
Compliance None
Capacity None
features (f12101-06)
Restrictions Dual stack (IPv4v6) is not supported on the same association. No mixed
IPv4 and IPv6 primary and secondary associations are supported.
Conguration Command muaAssociation

management Commands serviceIp and subnet
Counters None
Alarms None

Iu-U/Gn-U/Gn-C (Feature f12101-06): feature summary
Apart from IPv4 only, the CMM also supports IPv4v6 dual stack for the Iu-U, Gn-U and Gn-
C interfaces. But IPv6 only is not supported.

SGSN User Guide
Table 36: SGSN support for IPv4/IPv6 dual stack transport for Iu-U/Gn-U/Gn-C: feature
summary
Function Impact
Compliance 3GPP TS 29.060 Rel 15
Capacity None
Interworking/dependent SGSN support for IPv4/IPv6 dual stack transport for Gb (f12101-04)
features SGSN support for IPv4/IPv6 dual stack transport for Iu-C (f12101-05)
Restrictions IPv6 only is not supported for the Iu-U, Gn-U and Gn-C interfaces.
IPv6 is not supported in any interface in a S4-SGSN.
Conguration Command gParms, parameters prefGnToGGSNIpVer (default:

management IPv4) and ipv6SelectionAllowedOnGn (default: OFF)
Command rncParamSet, parameter ipv6AddressSupported
Counters None
Alarms None

Gr/Gf/Gs (Feature f12101-10): feature summary
Apart from IPv4 addresses, the SGSN also supports IPv6 addresses for the Gr/Gf/Gs
interfaces.

SGSN User Guide
Table 37: SGSN support for IPv4/IPv6 dual stack transport for Gr/Gf/Gs: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions Dual stack (IPv4v6) is not supported on the same association.

No mixed IPv4 and IPv6 primary and secondary associations are
supported.
Conguration Command muaAssociation

management
Counters None
Alarms None
2.23 CMM support for Gn dual stack (Feature f11810-01):

feature summary
This feature provides IPv6-only GN capability to CMM and enhances functionality
according to latest 3GPP TS 29.060 changes regarding to Alternative GGSN Address IE
handling.

SGSN User Guide
Table 38: CMM support for Gb dual stack: feature summary
Function Impact
Compliance 3GPP TS 29.060: GPRS Tunnelling Protocol (GTP) across the Gn and Gp
interface (Release 15), V15.5.0 (2019-06).
Capacity None
Required features MME support for IPv4/IPv6 dual stack transport for Gn (f12101-09)
SGSN support for IPv4/IPv6 dual stack transport for Iu-U/Gn-U/Gn-
C (f12101-06)
features
Restrictions None
Conguration None
management
Counters None
Alarms None
2.24 Enhanced triple access scenarios - delivery (Feature

With this feature, MME/SGSN (serving in 2G/3G/4G) enhancements are supported.

SGSN User Guide
Table 39: Enhanced triple access scenarios - delivery: feature summary
Function Impact
Compliance 3GPP TS 36.413: Evolved Universal Terrestrial Radio Access Network (E-
UTRAN); S1 Application Protocol (S1AP)
3GPP TS 23.003: Numbering, addressing and identication
Capacity None
features
Restrictions None
Conguration Command gParms, parameters includeMappedGummei,

management gnTargetIdFormat, nriLength, sgsnId, sgsnPoolId,
nullNri, s4Func, and s6dDiameter
Command prFile, parameters supportOfImsvops and
poolingCombiSgsnMme
Command plmn
Command mmeGrpNode
Command plmnParam, parameters gbNormRaAuthVisitor and
iuNormRaAuthVisitor
Counters None
Alarms None
2.24.1 Checking before handling RAU and reattach without

DNS query
In a combined MME/SGSN mode, the 2G/3G SGSN handles RAU from the local MME and
reattach inside the MME/SGSN without DNS query. Check the following parameters to
ensure that the MME and the SGSN are in the same MME/SGSN.
Procedure
1 View MCC and MNC.
cmm plmn show ETPLMN

Step result

SGSN User Guide
| Field | Value |
+--------------------------------+-----------------+
| plmn | ETPLMN |
| name* | ETPLMN |
| description | |
| mcc | 460 |
| mncDigits | 2Digits |
| mnc | 02 |
| plmnType | Home Network |
| obtainImeiSv | SMC |
| validateImeiEir | false |
...
2 View MME group ID and MME code.
Step example
cmm mmeGrpNode show ETPLMN~50002~51
Step result
+---------------+-----------------+
| Field | Value |
+---------------+-----------------+
| mmeGrpNode | ETPLMN~50002~51 |
| plmnName* | ETPLMN |
| mmeGi* | 50002 |
| mmeC* | 51 |
| localName | ESPATE133B |
| s10Ip | 0.0.0.0 |
| capacity | 5 |
| autoAdjustCap | true |
| nodeType | Home Network |
| numProtCPPS | 0 |
+---------------+-----------------+
3 View new visitor for authentication repetition rate for normal RA update (this is only
for RAU).
cmm plmnParam show ETPLMN

SGSN User Guide
Step result
+----------------------------+-------------+
| Field | Value |
+----------------------------+-------------+
| plmnParam | ETPLMN |
| plmnParamId* | ETPLMN |
| homePlmn | true |
| gtpTmrprId | 255 |
| gbMncl | 2 |
| gbGprsAttAuth | 1 |
| gbImsiAttAuth | 1 |
| gbCombAttAuth | 1 |
| gbNormRaAuthVisitor | 0 |
| gbNormRaAuth | 0 |
...
| iuMncl | 2 |
| iuNormRaAuthVisitor | 0 |
| iuNormRaAuth | 0 |
...
2.24.2 Enabling SGSN handling RAU and reattach without

DNS query
In the combined MME/SGSN, use the prFile parameter poolingCombiSgsnMme to enable
that the 2G/3G SGSN handles RAU from the local MME and the reattach procedure inside
the MME/SGSN without DNS query.
▪ Enable SGSN handling RAU and reattach without DNS query.
cmm prFile modify poolingCombiSgsnMme --status true
2.24.3 Enabling T-ADS Data Retrieval bit in diameter ULR

and IDA messages
The SGSN sets T-ADS Data Retrieval bit for Feature-List AVP in Supported-Features
grouped AVP in diameter ULR and IDA messages to the HSS.

SGSN User Guide
Procedure
1 Enable T-ADS Data Retrieval bit in diameter ULR and IDA messages.
cmm prFile modify supportOfImsvops --status true
2.25 RAI group/RAI based UE handling support (Feature

With this feature, the operator is enabled to define districts with their own dedicated IP
address pool. One district geographically covers a number of RAs. UE can be forced to
change its IP address by deactivating the PDP contexts with cause code #39: Reactivation
requested.

SGSN User Guide
Table 40: RAI group/RAI based UE handling support: feature summary
Function Impact

description; Stage 2 (Release 9, v9.7.0)
• 3GPP TS 29.060 General Packet Radio Service (GPRS); GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface (Release 9, v9.5.0)
Capacity None
Interworking/dependent GTP information sending (Feature SG01082)

features
Restrictions • This feature enables the operator to start massive PDP context
deactivation for a certain RA. The operation can be executed only for
one RA at a time.
• The UEs that are handled with initiate forced IP change operation will
be only those that were determined during the time when the
initiation command was given. Additional subscribers, whose PDP
context was activated after the forced IP change initiation command,
won't be handled separately.
• Not designed for roaming subscribers. Roaming subscribers use their
own GGSN.
• Not valid for S4 SGSN.
Conguration Commands district, districtRai and forceIpChange

management Command gParms, parameters raiBasedDeactPdpRate and
raiBasedUeHandlingEnabled
Counters None
Alarms None
2.25.1 Configuring RAI group/RAI based UE handling

support
Use global parameter raiBasedUeHandlingEnabled to activate the feature, CLI
command district to configure a new district and CLI command districtRai to add
RAIs under a selected district.
Before you start

SGSN User Guide
Feature GTP information sending (Feature SG01082) must be activated.

cmm features modify gtpInfoSending --status true
Procedure
cmm gParms modify --gParmName raiBasedUeHandlingEnabled --

gParmValue Yes
2 Set up a new district.
Step example
cmm district create --districtName DISTRICTA
Step result
+------------------+--------------------+
| Field | Value |
+------------------+--------------------+
| district | DISTRICTA |
| districtName* | DISTRICTA |
+-------------------+-------------------+
Unsuccessful outputs:
The maximum number of allowed districts (3000) is reached.

The same district name has already been defined.
3 Add RAIs under a selected district.
Step example
cmm districtRai create --mnc 232 --mcc 345 --lac 1 --rac 1 --
districtName DISTRICTA
Step result

SGSN User Guide
+--------------+----------------------+
| Field | Value |
+--------------+----------------------+
| districtRai | 345~232~1~1 |
| mcc* | 345 |
| mnc* | 232 |
| rac* | 1 |
| lac* | 1 |
| districtName | DISTRICTA
+--------------+----------------------+
Unsuccessful outputs:
District does not exist.ERROR: Create operation failed (msg=District DISTRICTB not
found in DISTRICT table. Create district first.)
The same RAI found under another district, the name of which is also
displayed.Create operation failed (msg=RA exists under district:DISTRICTA)
2.25.2 Executing forced IP change in RA

Purpose
Managing forced IP change operation in an RA (initiating/terminating forced IP change
operations and interrogating the number of subscribers in an RA). The rate of subscribers to
force IP change operation depends on raiBasedDeactPdpRate global parameter
(Maximum value: 25 subscribers per second.).
Procedure
1 Add the RAI for which forceIpChange will be initiated, under districtRai table.
Step example
cmm districtRai create --mnc 232 --mcc 345 --lac 1 --rac 1 --
districtName DISTRICTA
Step result

SGSN User Guide
+--------------+----------------------+
| Field | Value |
+--------------+----------------------+
| districtRai | 345~232~1~1 |
| mcc* | 345 |
| mnc* | 232 |
| rac* | 1 |
| lac* | 1 |
| districtName | DISTRICTA
+--------------+----------------------+
2 Modify the rate of the subscribers to force IP change, if needed.
Step example
cmm gParms modify --gParmName raiBasedDeactPdpRate --gParmValue
20
Step result
+------------+----------------------+
| Field | Value |
+------------+----------------------+
| gParms | raiBasedDeactPdpRate |
| gParmName* | raiBasedDeactPdpRate |
| gParmValue | 20 |
+------------+----------------------+
3 Initiate the forced IP change operation in RA for a specific district.
Step example
cmm forceIpChange create --mnc 232 --mcc 345 --lac 1 --rac 1
Step result
Successful output:

SGSN User Guide
+---------------+-------------+
| Field | Value |
+---------------+-------------+
| forceIpChange | 1~1~345~232 |
| rac* | 1 |
| lac* | 1 |
| mcc* | 345 |
| mnc* | 232 |
+---------------+-------------+
Unsuccessful output:
The given district name is not found.
ERROR: Create operation failed (msg=lac=1, rac=2, mcc='345', mnc='232' is not
provisioned in table districtRai.)
The forced IP change operation is in progress.
ERROR: Create operation failed (msg=An operation is already ongoing, can't create
new)
4 Interrogate RA to find out the number of subscribers in RA and also the possible
forced IP change operation status.
cmm forceIpChange list

Step result
Successful output:
The forced IP change operation has finished successfully.
+---------------+--------+------------+--------------+
| forceIpChange | papsId | statusCode | progressSubs |
+---------------+--------+------------+--------------+
| 2~1~345~232 | 0 | DONE | 5 |
| 2~1~345~232 | 1 | DONE | 10|
+---------------+--------+------------+--------------+
The forced IP change operation is in progress. If necessary, the forced IP change can
be terminated.

SGSN User Guide
+---------------+--------+------------+--------------+
+---------------+--------+------------+--------------+
| 2~1~345~232 | 0 | ONGOING | 5 |
| 2~1~345~232 | 1 | ONGOING | 10 |
+---------------+--------+------------+--------------+
The forced IP change operation is in progress for different RA.
ERROR: Create operation failed(msg=An operation is already ongoing,can't
create new)
Unsuccessful output:
The districtRai to trigger forceIpChange doesn’t exist.

ERROR: Create operation failed (msg=lac=1, rac=1, mcc='345', mnc='232' is not
provisioned in table districtRai.)
5 Terminate the forced IP change operation in RA under a specific district.
Step example
cmm forceIpChange modify --statusCode STOP --mnc 232 --mcc 345 --
lac 1 --rac 2
Step result

SGSN User Guide
+---------------+-------------------------+
| Field | Value |
+---------------+-------------------------+
| rac* | 2 |
| lac* | 1 |
| mcc* | 345 |
| mnc* | 232 |
+---------------+-------------------------+
+---------------+--------+------------+------------------+
+---------------+--------+------------+------------------+
| 2~1~345~232 | 0 | STOP | 5 |
| 2~1~345~232 | 1 | STOP | 5 |
+---------------+--------+------------+------------------+
6 Delete the forced IP change operation in RA under a specific district.
Step example
cmm forceIpChange delete 2~1~345~232
Step result
+---------------+-------------+
| Field | Value |
+---------------+-------------+
| rac* | 2 |
| lac* | 1 |
| mcc* | 345 |
| mnc* | 232 |
+---------------+-------------+

SGSN User Guide
2.26 Customer-specified GTP error indication handling

towards RNC (Feature f52062-01): feature summary
With this feature, an operator can change the existing collision handling behavior during
handover from 4G to 3G and a GW-initiated PDP deactivation to prevent the SGSN from
sending an error indication to the RNC during this scenario.
Table 41: Customer-specified GTP error indication handling towards RNC: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command rncParamSet, parameter

management specialCollisionHandlingDuringHo
Counters None
Alarms None
2.26.1 Enabling special collision handling behavior during

handover from 4G to 3G
Enabling this capability prevents the SGSN from sending an error indication to the RNC by
changing the existing collision handling behavior during a handover from 4G to 3G and a
GW-initiated PDP deactivation.
Procedure
1 Display the RNC parameter set list.
Step example
cmm rncParamSet list

SGSN User Guide
+-------------+----------+
| rncParamSet | pSetName |
+-------------+----------+
| 0 | default |
| 1 | 1 |
| 2 | DT |
| 3 | 1_v6 |
| 4 | DT_v6 |
+-------------+----------+
2 Enable special collision handling during handover.
cmm rncParamSet modify <rncParamSet> --

specialCollisionHandlingDuringHo true
Step example
cmm rncParamSet modify 0 --specialCollisionHandlingDuringHo true

SGSN User Guide
+----------------------------------+---------+
| Field | Value |
+----------------------------------+---------+
| rncParamSet | 0 |
| rncParamSetId* | 0 |
| pSetName | default |
| maxTimeForRelocResAlloc | 10 |
| maxTimeForRelocResCompl | 15 |
| maxTimeForRabAssignment | 20 |
| overloadShortTimerInSgsn | 10 |
| overloadLongTimerInSgsn | 30 |
| maxTimeForResetProcedure | 60 |
| guardPeriodBeforeResetAck | 5 |
| maxTimeUntilLocationReport | 10 |
| resetResourceRepeatInterval | 10 |
| guardPeriodAfteSubsProhib | 29 |
| maxTimeForIuRelease | 10 |
| maxTimeForIuReleaseCompl | 5 |
| maxTimeForSrnsContextResp | 8 |
| maxTimeForSecModeAck | 5 |
| maxRepeatCntOfRncGlobRst | 5 |
| maxRepeatForResourceReset | 1 |
| rabModifySupported | false |
| maxDlBitrateForRab | 0 |
| maxQuaranteedDlBitRateForRab | 0 |
| ipv6AddressSupported | false |
| maxUlBitrateForRab | 0 |
| maxGuaranteedUlBitrateForRab | 0 |
| rncSupportForDirectTunnel | false |
| cspsCoordinationSupported | true |
| epsBearerPresSupported | true |
| rel8RncSupported | false |
| ueAmbrSupported | false |
| specialCollisionHandlingDuringHo | true |
+----------------------------------+---------+

SGSN User Guide
2.27 CMM support for ARD provisioned in HSS and pass it

with service-based HO to radio accordingly (Feature
This feature supports HSS access restriction data (ARD) provisioning and passing with
service-based handover to radio accordingly in the CMM.
Table 42: CMM support for ARD provisioned in HSS and pass it with service-based HO to radio
accordingly: feature summary
Function Impact
Compliance 3GPP TS 25.413 (v10.10.0), UTRAN Iu interface Radio Access Network

Application Part (RANAP) signaling (Release 10)
Capacity None
features
Restrictions None
Conguration Command gParms, parameter accessRestrictionToLte

management
Counters None
Alarms None
2.28 SGSN support for user plane frames that exceed

1500 bytes (Feature f52017-01): feature summary
This feature adds support for user plane frames on SGSN with payload up to 1500 bytes.
With additional protocol stack headers, the packet size can become greater than 1500
without any fragmentation. The MTU size needs to be greater than 1500 bytes.
Table 43: SGSN support for user plane frames that exceed 1500 bytes: feature summary

SGSN User Guide
Function Impact
Compliance None
Capacity None
features
Restrictions • Only IPv4 network addressing is supported.

• Only Openstack based deployment is supported.
• Packets may contain only up to 1500 bytes of payload data. With
additional protocol stack headers, they may exceed the 1500 default
MTU size.
• Only certain maximum MTU sizes are supported per affected
interface.
• If the MTU sizes are set manually via Linux and CLI, and not via
deployment, the feature will not work properly.
• Each network element on the 2G/3G user plane data path must be
congured at least with the same MTU size in order to ensure that
fragmentation will not occur end-to-end.
Conguration Command gParms, parameters enable2GdataJumboFrame,

management enable3GdataJumboFrame
The default value is No. When the feature is disabled, the SGSN
fragments or even drops the large data packets.
Note:
When the gParm is activated, it must be done for all the interfaces
that participate in the packet processing in order to avoid
fragmentation. For example, in the case of 3G user plane
(enable3GdataJumboFrame set to Yes), the MTU size must
be changed for both lu-U and Gn/S4 interfaces.
Specic deployment with proper adaptations is needed on the

interface MTU parameter. Inside the network-related yaml le,
the mtu parameter needs to be changed for the following
networks: RAN2G, COREUP, RAN3GUP and LI external networks.
Note:
Besides the MTU size for the Gb interface (RAN2G network), the
actual maximum info length of 2G RAN data frame is determined
by the BSS side and the Ν201-U value as provided by the BSC at
the LLC layer (from 140 to 1520 bytes). This should be the
fragmentation limit for the 2G payload data.
Counters None

SGSN User Guide
Function Impact
Alarms None
2.29 SGSN support for configurable PDN type IPv4v6

This feature supports configurable global parameter
defaultIpv4ForPdnTypeIpv4OrIpv6 to allow operators to choose the PDN type
between IPv4 and IPv6, when the PDN type received from the HSS is IPv4_OR_IPv6 and
UE-requested IPv4v6 (dual stack).
Table 44: SGSN support for configurable PDN type IPv4v6: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command gParms, parameter

management defaultIpv4ForPdnTypeIpv4OrIpv6 (default: No) (This
parameter can also be used for the MME.)
Counters None
Alarms None
2.29.1 Configuring SGSN support for PDN type IPv4v6

Use the global parameter defaultIpv4ForPdnTypeIpv4OrIpv6 to choose the PDN
type between IPv4 and IPv6 upon receiving from the HSS.

SGSN User Guide
▪ Choose the PDN type between IPv4 and IPv6.
cmm gParms modify --gParmName defaultIpv4ForPdnTypeIpv4OrIpv6 --

gParmValue <value>
Table 45: Values for the defaultIpv4ForPdnTypeIpv4OrIpv6 parameter
Value Description
Yes The pdnType selection is IPv4.
No (default) The pdnType selection is IPv6.
2.30 SGSN support for independent 2G PRAU and MSRT

timers with 3G (Feature f52088-01): feature summary
With this feature, 2G PRAU timer can be configured independently from 3G PRAU timer
through patch parameters.
Table 46: SGSN support for independent 2G PRAU and MSRT timers with 3G: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command gParms, parameter pRau2g

management Command patchParameter, parameter paramId
Counters None
Alarms None

SGSN User Guide
2.30.1 Configuring independent 2G PRAU and MSRT timers

with 3G
Use the global parameter pRau2g to enable this feature, and the paramId 48 parameter
of the patchParameter command to define the value for 2G PRAU timer.
Procedure
1 Enable SGSN support for independent 2G PRAU and MSRT timers with 3G.
Step example
cmm gParm modify --gParmName pRau2g --gParmValue Yes
2 Define the new patch parameter for 2G PRAU timer.
Note:
Set the appId parameter to 40A, paramId parameter to 48 and value

parameter is in Hex.
Step example
cmm patchParameter create --appId 40A --paramId 48 --value B3 1

SGSN User Guide
3. Radio and core network access support
3.1 Gb over IP (Features SG01048, SG01102, SG01029,

f60210-06 and f60210-31)
The Gb interface transfers signaling and user data between the SGSN and the Base
Station Subsystem (BSS). The Gb interface covers both the transmission between the
SGSN and the Base Station Controller (BSC), and the logical radio interface between the
SGSN and the Mobile Station (MS).
The Gb interface uses communication paths, called Network Service Virtual Connections (NS-
VCs), to transmit the user data. NS-VCs are transported through paths offered by the
subnetwork of the Gb interface.
Gb over IP offers an alternative way to configure the Gb interface's subnetwork which is

based on IP and the physical layer is Ethernet. When the Gb interface is based on IP, an NS-
VC is a pair of User Datagram Protocol (UDP)/Internet Protocol (IP) endpoints: one UDP/IP
address in the BSS and one UDP/IP address in the SGSN.
Related features:
Multipoint Gb
The Multipoint Gb feature overcomes the strict hierarchy which restricts the connection
of a BSC to only one SGSN. This feature introduces the pool area concept. A pool area
consists of several RAN and CN nodes each having connections between each other. For
more information on this feature, see Multipoint Gb (Feature SG01023).
Large Routing Area Support (LRAS)
The Large Routing Area Support (LRAS) feature is also supported when Gb over IP is used.
For more information on this feature, see Large Routing Area Support (LRAS) (Feature
SG01060).
Note:
Only one PAPS group as default configuration. The LRAS feature is activated as
default and cannot be deactivated.
Support for Non-standard Gb over IP

The Support for Non-standard Gb over IP function enables better dynamic Gb over IP
configuration compatibility in multivendor environment by accepting oversized values in
the Number of IP4 Endpoints and Number of IP6 Endpoints parameters in the SNS-SIZE

SGSN User Guide
PDU. When this function is active, if the proposed number of IP endpoints in the SNS-SIZE
PDU exceeds the SGSN remote endpoint capacity, the received value is downsized to
match the current SGSN configuration. It means that the number of configured BSS IP
endpoints are not verified until the following CONFIG procedure. For detailed description
on the SIZE and CONFIG procedures, see Dynamic configuration in the Gb over IP feature
description in SGSN Feature Overview.
3.1.1 Configuring Gb over IP

The procedure includes steps and examples on how to configure Gb over IP for static or
dynamic configuration.
Procedure
1 Check that Gb-auto interface exists in IPDS, used for dynamic Gb.
Step example

SGSN User Guide
cmm serviceIp list --niType GBAUTO
+-----------------------------+
| serviceIp |
+-----------------------------+
| IPDS~0~0~GBAUTO~10.37.36.50 |
+-----------------------------+
cmm localEndPtCfg show GB
+---------------------+--------+
| Field | Value |
+---------------------+--------+
| localEndPtCfg | GB |
| interfaceName* | GB |
| dscpCode | AF41 |
| avRequested | 0 |
| sctpOutboundStreams | 1 |
| sctpInboundStreams | 1 |
| interfaceLabel | GBSGSN |
| description | |
| protocolProfileName | |
| interfacePort | 49999 |
| multiHomed | false |
| comboIndication | false |
| shutdown | false |
| immRspPref | No |
+---------------------+--------+
2 Check GB interface in each PAPS (GBNS), used for all dynamic and static Gb links.
Step example

SGSN User Guide
cmm serviceIp list --niType GBNS
+----------------------------+
| serviceIp |
+----------------------------+
| PAPS~0~0~GBNS~10.37.37.132 |
| PAPS~1~0~GBNS~10.37.37.133 | |
+----------------------------+
cmm sgsnLocalEndPtCfg show GBNS
+------------------------+-------+
| Field | Value |
+------------------------+-------+
| sgsnLocalEndPtCfg | GBNS |
| icp | 49999 |
| i6hcunack | |
| i6hcack | |
| llcRetransmTimer | 10 |
| llcRetransmCounter | 3 |
| nsTestTimer | 60 |
| nsAliveTimer | 3 |
| nsAliveRetries | 10 |
| bvcResetTimer | 3 |
| bvcResetRetries | 3 |
| snsProvTimer | 5 |
| snsAddRetries | 3 |
| snsConfigRetries | 3 |
| snsChangeWeightRetries | 3 |
| snsDeleteRetries | 3 |
+------------------------+-------+
3 Create dynamic Network Service Entity (NSE).
Step example
cmm nse create --nseId 8100 --nseName NSE8100 --localUdpPort
58000
4 Create static NSE and static IP NS-VC (example for 2 PAPS).

SGSN User Guide
Step example
cmm nse create --nseId 200 --nseName NSE200 --localUdpPort 52000
--connectionType STA
Step example
cmm nsvc create --nsvcName sta0 --remoteIpEndpoint 10.41.122.87 -
-remoteUdpPort 52000 --remoteDataWeight 1 --remoteSignWeight 1 --
nseId 200 --papsId 0 --nsvcId 200 --remoteIpEndpointVersion IPV4
Step example
cmm nsvc create --nsvcName sta1 --remoteIpEndpoint 10.41.122.87 -
-remoteUdpPort 52000 --remoteDataWeight 1 --remoteSignWeight 1 --
nseId 200 --papsId 1 --nsvcId 201 --remoteIpEndpointVersion IPV4
Note:
When creating more NS-VCs into one NSE, the local port number used by all NS-
VCs under the same NSE is common.
The sum of the NSE's remoteDataWeight and remoteSignWeight must not

be zero.
5 Unlock static NS-VCs only.
Step example
cmm nsvcAdmin modify --nseId 200 --state unlocked
OR
Step example
cmm nsvc modify --nsvcId 200 --nsvcStatus unlocked
Step example
cmm nsvc modify --nsvcId 201 --nsvcStatus unlocked
6 Interrogate Gb link state for dynamic and for static nsei.
Step example

SGSN User Guide
cmm gbLinkInfo list --nsei 8100
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
| papsId | nsei | nsvci | adminState | opState | remoteIp | remotePort | rdw | rsw |
ldw | lsw |
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
| 0 | 8100 | - | unlocked | working | 10.41.122.93 | 58000 | 1 | 1 | 1
| 1 |
| 1 | 8100 | - | unlocked | working | 10.41.122.93 | 58000 | 1 | 1 | 1
| 1 |
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
cmm gbLinkInfo list --nsei 200
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
| papsId | nsei | nsvci | adminState | opState | remoteIp | remotePort | rdw | rsw |
ldw | lsw |
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
| 0 | 200 | 200 | unlocked | working | 10.41.122.87 | 52000 | 1 | 1 | 0
| 0 |
| 1 | 200 | 201 | unlocked | working | 10.41.122.87 | 52000 | 1 | 1 | 0
| 0 |
+--------+------+-------+------------+---------+--------------+------------+-----+-----+---
--+-----+
7 Interrogate 2G cell status.
Step example

SGSN User Guide
cmm gbNetworkInfo list --nsei 8100
+--------+------+-------+-----+-----+------+-----+-----+----------+
| papsId | nsei | bvci | mcc | mnc | lac | rac | ci | bvcState |
+--------+------+-------+-----+-----+------+-----+-----+----------+
| 1 | 8100 | 10121 | 244 | 07 | 3424 | 5 | 436 | working |
+--------+------+-------+-----+-----+------+-----+-----+----------+
cmm gbNetworkInfo list --nsei 200
+--------+------+-------+-----+-----+------+-----+-----+----------+
| papsId | nsei | bvci | mcc | mnc | lac | rac | ci | bvcState |
+--------+------+-------+-----+-----+------+-----+-----+----------+
| 0 | 200 | 10093 | 244 | 09 | 2424 | 4 | 432 | working |
+--------+------+-------+-----+-----+------+-----+-----+----------+
8 Remove dynamic GB IP endpoints.
Step example
In case dynamic NSE must be removed with all dynamic IP endpoints:
cmm nse delete 8100
9 Remove static NS-VC.
In case static NS-VC must be removed in SGSN, the NS-VC configuration must be
removed also from BSC side. First, lock the static NS-VC to be removed and then delete
the locked NS-VC.
Step example
cmm nsvc modify --nsvcId 200 --nsvcStatus locked
Step example
cmm nsvc delete 200
Note:
In case that there are GPRS-enabled cells related to the static NSE, the locking of
the last NS-VC whose operational state is working will cause the deletion of the
cells under this NSE. It is recommended to execute the cmm gbLinkInfo and
cmm gbNetworkInfo commands before locking NS-VCs.

SGSN User Guide
3.1.2 Gb over IP (Features SG01048, SG01102, SG01029,

f60210-06 and f60210-31): feature summary
The NSE and its Sub-Network Service, which provides access to the intermediate network
is configured by auto-configuration procedures, that is, dynamic configuration. Static
configuration is an alternative Gb over IP interface configuration in which the parameters
are configured to both ends statically and not transferred over the Gb interface.

SGSN User Guide
Table 47: Gb over IP (Feature SG01048): feature summary
Function Impact
Compliance 3GPP TS 48.016 Base Station System (BSS) - Serving GPRS

Support Node (SGSN) interface; Network Service
Capacity None
Interworking/dependent • Multipoint Gb (Feature SG01023)

features • Internal Load balancing and admission control (Feature
SG01060)
See Gb over IP.
Restrictions If the local endpoints are added to the LRAS PAPS group after the
dynamic conguration (that is, SIZE and CONFIG procedures), the
endpoints are not effective until the next restart of the NSE.
Conguration management Command nse for GPRS NS layer handling

Commands nsvc and nsvcAdmin for static conguration
Command sgsnLocalEndPtCfg for GPRS network handling
Command gbLinkInfo for 2G network service virtual
connection data (link state output)
Command gbNetworkInfo for listing 2G network conguration
See Integrating CMM for detailed Gb interface conguration.
Counters M010C000 / DISCARDED DATA BY BSSGP

M010C001 / PASSED BSSGP DATA IN BYTES
M010C002 / NUMBER OF LLC FRAMES WAITING IN BSSGP QUEUE
SUM
DEN
PEAK
Alarms If the capacity of the measurement data structure is exceeded,

for example, because of the conguration changes or re-mapped
NS-VCs, alarm 3003 INCORRECT MEASUREMENT DATA is set and
the received data is discarded.
Feature ID SG01048
3.2 EDGE support (Feature SG01033): feature summary

This feature offers seamless support for enhanced data rates for GSM evolution (EDGE)
technology. In EDGE, a separate radio interface modulation technique is used that
increases the GSM data transfer rates per mobile.

SGSN User Guide
Table 48: EDGE support (Feature SG01033): feature summary
Function Impact
Compliance None
Capacity None
features
Conguration management Command features, parameter edgeSupport
Restrictions None
Counters None
Alarms None
Feature ID SG01033
3.3 3G access support (Features SG02001 and SG01119):

feature summary
With this feature, SGSN is connected to UMTS radio network so that it can be integrated
and used both in 2G GPRS and 3G UTRAN (WCDMA) environment.
3G access functionality is implemented with the Iu interface between SGSN and RNC, for
control and user planes. Iu interface traffic is transported over IP network.
Table 49: 3G access support (Features SG02001 and SG01119): feature summary

SGSN User Guide
Function Impact
Compliance • IETF RFC 2719: Framework Architecture for Signaling

Transport
• IETF RFC 2960: Stream Control Transmission Protocol
• IETF RFC 3309: Stream Control Transmission Protocol (SCTP)
Checksum Change
• IETF RFC 3332: Signaling System 7 (SS7) Message Transfer
Part 3 (MTP3) - User Adaptation Layer (M3UA)
• 3GPP TS 23.060 General Packet Radio Service (GPRS);Service
• 3GPP TS 25.410 UTRAN Iu interface: General aspects and
principles
• 3GPP TS 25.411 UTRAN Iu interface layer 1
• 3GPP TS 25.412 UTRAN Iu interface signalling transport
• 3GPP TS 25.413 UTRAN Iu interface RANAP signalling
• 3GPP TS 25.414 UTRAN Iu interface data transport and
transport signalling
• 3GPP TS 25.415 UTRAN Iu interface user plane protocols
Tunnelling Protocol (GTP) across the Gn and Gp interface
Capacity The 3G data traffic does not affect PAPS load since PAPS
handles only signaling traffic and data traffic is handled in the
IPPS.
When using the Multipoint Iu feature, the signaling load is
reduced between SGSNs and also between the SGSN and the
HLR. When the SGSN is used in dual mode (serving 2G and 3G),
the amount of statistical information grows
Interworking/dependent • Quality of Service ( Feature SG01027)

features • SS7 over IP (Feature SG01051)
• Multipoint Iu (Feature SG02002)
• Internal Load balancing and admission control (Feature
SG01060)
• HSDPA, HSUPA Support and HSPA+ (Feature SG02104)
• HLR-based 2G/3G access control (Feature SG02114)
• Overload control (Feature SG01037)
Restrictions The network needs to have an authentication center (AUC).

SGSN User Guide
Function Impact
Conguration management Commands:

• cmm rnc
• cmm rncParamSet
• cmm plmn
• cmm plmnParam
• cmm muaAssociationSet
• cmm muaAssociation
• cmm muaAssociationList
• cmm muaLink
• cmm muaSignallingRoute
• cmm muaRoute
• cmm muaSignallingRouteList
• cmm sccpSignallingPoint
• cmm sccpSubsystem
• cmm sccpSubsystemList
• cmm subscriber
Command serviceIp, parameters poolType {IPDS,
IPPS}, niType {M3UA7SH,M3UA7MHA,M3UA7MHB},
poolType IPPS, niType IU_DATA
Counters The statistics for the Iu interface are provided in the similar
accuracy level as for the Gb interface: while the statistics in
the Gb interface are collected in the cell level, the
corresponding statistics in the Iu Interface are collected in the
service area level. The characteristics of the Iu interface also
bring new types of counters, such as Relocation. For more
details and the counters involved, see Performance
Management (Feature SG01016).
Alarms • 1309 – RncOutOfServiceInSgsn

• 2064 – RouteSetUnavailable
• 2070 – LinkSetUnavailable
• 3159 – SctpAssociationLost
• 3333 – RncContinuouslyOutOfServiceInSgsn
• 3514 – RncUnavailable
3.3.1 Configuring the lu interface

The procedure includes steps for configuring related IPs and IP signalling SCCP and
subsystem, activating SS7 signaling, and configuring the Radio Network Controller in
SGSN.

SGSN User Guide
Procedure
1 Configure IP.
1.1 Define GTP-C and Iu-C subnets and addresses for IPDS.
cmm subnet create
1.2 Define GTP-U and Iu-U subnets and addresses for IPPS.
cmm serviceIp create
2 Configure IP signalling on SCTP level.
2.1 Create association set.
cmm muaAssociationSet create
2.2 Create associations.
cmm muaAssociation create
2.3 Add association to association set and activate.
cmm muaAssociationList create
3 Configure IP signalling Link.
3.1 Create the IP signaling linkset.
cmm muaLink create
4 Configure IP signalling routes.
4.1 Create IP signalling route.
cmm muaSignallingRoute create
4.2 Create M3UA route.
Create M3UA route
4.3 Assign and activate.
cmm muaSignallingRouteList create
5 Configure IP signalling SCCP and subsystem.
5.1 Create the remote signaling connection control part (SCCP) signaling point.

SGSN User Guide
cmm sccpSignallingPoint create
5.2 Create the following SCCP subsystem: radio access network application part
(RANAP).
cmm sccpSubsystem create
5.3 Assign subsystem to SCCP signaling point and activate.
cmm sccpSubsystemList create
6 Activate SS7 signaling.
6.1 Activate signaling link.
cmm muaLink modify --signallingLinkState ACT
7 Configure the Radio Network Controller in SGSN.
7.1 Create RAI and RNC and change state to unlocked.
cmm rait create
cmm rnc create --state unlocked
cmm raitOfRnc create
For more information on configuring the lu interface, see Integrating CMM.
3.4 HSDPA, HSUPA support and HSPA+ (Features

SG02104, SG01113 and SG02198)
HSDPA brings higher-speed data delivery to 3G terminals, HSUPA is Iu interface specific
3GPP Release 6 feature that provides enhanced uplink throughput, improved coverage
and reduced delay in the radio interface of UMTS terrestrial radio access network
(UTRAN), and HSPA+ for the packet switched core network offers a possibility to higher
bit rates and best possible QoS profile in different radio accesses.

SGSN User Guide
3.4.1 HSDPA, HSUPA support and HSPA+ (Features

SG02104, SG01113 and SG02198): feature summary
HSDPA, HSUPA and HSPA+ can be controlled through parameters of the features
command.
Table 50: HSDPA, HSUPA support and HSPA+ (Features SG02104, SG01113 and SG02198):
feature summary
Function Impact
Compliance Feature SG02104: HSDPA support

• 3GPP TS 24.008 Mobile radio interface Layer 3 specication; Core
network protocols, Release 7
• 3GPP TS 29.002 Mobile Application Part (MAP) specication, Release 7
• 3GPP TS 29.060 General Packet Radio Service (GPRS); GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface, Release 7
Features SG02104: HSDPA support and SG02198: HSPA+
• 3GPP TS 23.107 Quality of Service (QoS) concept and architecture,
Release 7
• 3GPP TS 23.203: Policy and charging control architecture, Release 8
• 3GPP TS 23.401: General Packet Radio Service (GPRS) enhancements
for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access,
Release 8
Features SG01113: HSUPA Support and SG02198: HSPA+
• 3GPP TS 24.008 Mobile radio interface Layer 3 specication
Capacity This feature affects PAPS throughput capacity. The number of

HSDPA/HSUPA contexts depends on the PAPS capacity.
Interworking or • GPRS session management (Feature SG01012)

dependent features • 3G access support (Feature SG02001)
(Feature SG02017)
• HLR HSPA+ QoS override (Feature SG01231)
Restrictions HSDPA:
• Supported for the Iu Interface. In GERAN, the maximum bit rate bps
value is 472 kbps or 2 Mbps depending on operator conguration.
HSUPA:
• Over 8 Mbps uplink MBR/GBR QoS values can be reported to the S-
CDR only when using the 3GPP ASN.1 CDR format.

SGSN User Guide
Function Impact
Conguration For HSDPA support, command features, parameters

management • hsdpaSupport
• hsdpaSupport4M
• hsdpaSupport12M
• hsdpaSupport16M
• hsdpa84m
For HSUPA support, command features, parameters
• hsupaSupport1500k
• hsupaSupport2M
• hsupaSupport6M
• hsupaSupport8M
• hsupa23m
For HSPA+ support, command features, parameters
• hsdpa21m
• hsdpa28m
• hsdpa42m
• hsdpa168m
• hsupa11m
• hsupa46m
Relevant to HSDPA feature, parameters of the prFile command:
• override2gDowngrade
• qosHandlingInIsho
- Command qosConf, parameters imbr and igbr (see Downlink
bit rate in ISHO and GERAN PDP context activation)
Charging The QoS prole is visible in the SGSN charging record (SCDR) with other
PDP context-related information.
Counters The HSDPA/HSUPA PDP context activation, modication and

deactivation procedures can be detected from the QoS throughput
parameters in Traffica.
Alarms None
Feature ID • HSDPA support (SG02104)

• HSUPA support (SG01113)
• HSPA+ (SG02198)
3.4.2 HSDPA, HSUPA, and HSPA+ parameters

HSDPA, HSUPA and HSPA+ features are by default activated (true).

SGSN User Guide
Table 51: HSDPA parameters
Parameter Functionality
hsdpa21m SGSN HSDPA+ support 16M - 21M
hsdpa168m SGSN HSDPA support 84 M - 168M (10 ksub)
hsdpaSupport SGSN HSDPA support
hsdpaSupport4m SGSN HSDPA support 4M
Table 52: HSUPA parameters
Parameter Functionality
hsupa11m SGSN HSUPA+ support 6M - 11.5M
hsupa23m SGSN HSUPA+ support 11.5M - 23M
hsupa46m SGSN HSUPA support 23M - 46M (10 ksub)
hsupaSupport2m SGSN HSUPA support 2M
hsupaSupport6m SGSN HSUPA support 6M
hsupaSuppor8m SGSN HSUPA support 8M
hsupaSupport1500k SGSN HSUPA support 11.5M
3.4.3 Downlink bit rate in ISHO and GERAN PDP context

activation
The handling of the quality of service downlink bit rate values in inter system handovers
and GERAN PDP context activation are configurable through prFile parameters
override2gDowngrade and qosHandlingInIsho.

SGSN User Guide
The handling of the quality of service downlink bit rate values in inter system handovers and
GERAN PDP context activation can be chosen with the two prFile parameters:
override2gDowngrade
qosHandlingInIsho
If both parameters have status true, the qosHandlingInIsho overrides the

override2gDowngrade.
If both parameters have status false:

In the inter-system handover to the GERAN, the downlink MBR and GBR values are 472
kbps. In the PDP context activation with the GERAN, the downlink MBR and GBR maximum
values are 472 kbps.
Downlink bit rates are not renegotiated in the inter system handover to UTRAN.
If the override2gDowngrade parameter is true and the qosHandlingInIsho

parameter is false:
In the inter-system handover to the GERAN or in the PDP context activation with the
GERAN, the downlink MBR and GBR values are 2048 kbps.
Downlink bit rates are not renegotiated in the inter system handover to UTRAN.
If the qosHandlingInIsho parameter is true:

In the inter-system handover to the GERAN or in the PDP context activation with the
GERAN, the operator-configurable parameters IMBR (maximum bit rate for UTRAN to
GERAN in ISHO) and IGBR (guaranteed bit rate for UTRAN to GERAN in ISHO) are taken into
account in negotiating the quality of service downlink bit rate parameter values.
IMBR and IGBR are configurable through the command qosConf, parameters imbr and
igbr.
3.4.4 RNC profile

The operator can define the RNC throughput capabilities by configuring maximum values
for MBR and GBR. Previously it has been possible to define only one MBR and one GBR
value per RNC, and the values have been applied both to uplink and to downlink. This has
prevented additional PDP context modifications in cases where SGSN has proposed an
MBR or a GBR value that RNC does not support.
However, with different HSUPA and HSDPA capabilities it is possible to divide the MBR or the
GBR parameters in RNC profile into uplink and downlink MBR/GBR. This is useful for
deployments in which the RNCs have different HSUPA and HSDPA capabilities. To prevent

SGSN User Guide
the unnecessary additional PDP context modifications between SGSN and GGSN, RNC's
uplink and downlink throughput capabilities can be taken into account in the QoS
negotiation. This, in turn, speeds up the PDP context activation.
3.4.5 Iu-PS interworking scenarios

Normal reference cases are handled, and problem scenarios and solutions are introduced.
3.4.5.1 Normal reference cases

Four scenarios: 3GPP R7 support, harmonized MBR across network; 3GPP R7 support,
non-harmonized MBR across network (MBR core exceeds MBR RAN); 3GPP R7 support,
non-harmonized MBR across network (MBR RAN exceeds MBR core), and 3GPP R7 NW with
harmonized MBR, R7 UE supporting lower MBR.
Scenario 1: 3GPP R7 support, harmonized MBR across network

After receiving the initial PDP Context Request, and corresponding GGSN response (Create
PDP Context Response), the following activities are performed:
1. SGSN initiates the RAB Assignment Request to the RNC, requesting certain MBR value (for
example, 21 Mb/s) as part of RAB parameters IE.
2. RNC then answers to the SGSN with RAB Assignment Response(s).
3. Optionally with Direct Tunnel, the SGSN initiates the Update PDP Context message
request to GGSN, including the Common Flags IE with the No QoS negotiation bit set to 1.
4. Optionally, the GGSN acknowledges the Update PDP Requests.
Finally, the SGSN sends the PDP acceptance to UE. The QoS/MBR value is mainly driven by
the limits that are set in HLR/HSS, HSPA+ core licenses or possible by policy restrictions.
Scenario 2: 3GPP R7 support, non-harmonized MBR across network (MBR

Core exceeds MBR RAN)
After receiving initial PDP Context Request and corresponding GGSN response, the following
activities are performed:
1. SGSN initiates RAB Assignment Request to the RNC, requesting certain MBR value (for
2. RNC then answers to the SGSN with RAB Assignment Response(s), including cause value
like req_mbr_dl_not_avail, RANAP cause 33.

SGSN User Guide
3. SGSN then sends a request for RAB assignment with lower QoS.
4. RNC answers to the renewed SGSN request with RAB Assignment Response.
5. SGSN initiates the Update PDP Context message request to GGSN with modified QoS
(Common Flags IE with the No QoS negotiation bit set to 1 only in case of Direct Tunnel
PDP Context).
6. GGSN acknowledges the Update PDP Request.
Finally, SGSN sends the PDP acceptance to UE. The QoS/MBR value is mainly driven by the
limits that are set in HLR/HSS, HSPA+ core licenses or possible by policy restrictions.
Scenario 3: 3GPP R7 support, non-harmonized MBR across network (MBR RAN

exceeds MBR core)
After receiving the initial PDP Context Request, SGSN already applies its limited MBR in PDP
request to GGSN. After the corresponding GGSN response, the following activities are
performed:
1. SGSN initiates RAB Assignment Request to the RNC, SGSN limits its MBR value to (for
example, 16 Mb/s) according to its feature/license support.
4. Optionally, GGSN acknowledges the Update PDP Request.
Finally, the SGSN sends the PDP acceptance to UE. So, in this case the QoS/MBR value is
mainly driven by limits that are set in HSPA+ Core.
Scenario 4: 3GPP R7 NW with harmonized MBR, R7 UE supporting lower MBR

1. SGSN initiates the RAB Assignment Request to the RNC, requesting certain MBR value (for
Note:
The UE is limited in air-interface by its own MBR.


SGSN User Guide
4. Optionally, the GGSN acknowledges the Update PDP Request.
Finally, SGSN sends the PDP acceptance to UE.
Note:
The user data can be exchanged at lower rate, determined by UE capabilities. Network
can set up higher RAB on Iu-side.
3.4.5.2 Interworking with non-3GPP R7 capable RAN

There are two workarounds in the case of partial RAN support for HSPA+ due to roll-out
status or multiple RAN vendors.
Scenario: Partial RAN support for HSPA+ due to roll-out status or multiple
RAN vendors
1. SGSN initiates RAB Assignment Request to the RNC, requesting certain MBR value (for
2. RNC then answers to the SGSN with RAB Assignment Response(s), including cause value
Abstract Syntax Error (Reject), RANAP cause 100.
3. In this case, SGSN rejects the PDP Context Request.
Workaround 1: SGSN defined MBR limit per affected RNC

After receiving the initial PDP Context Request (legacy UE, subscribes QoS), the SGSN sends
the PDP request to GGSN. After receiving the response, the following activities are
performed
1. SGSN initiates RAB Assignment Request to the RNC, now requesting limited MBR value
(for example, 16 Mbps) as defined in RNC parameter set in SGSN (actually earlier PDP
request to GGSN is already done with defined MBR limit).
3. Optionally with Direct Tunnel, SGSN initiates the Update PDP Context message request to
GGSN, including the Common Flags IE with the No QoS negotiation bit set to 1.
4. Optionally, the GGSN acknowledges the Update PDP Request.

SGSN User Guide
Workaround 2: Alternative RAB

After receiving the initial PDP Context Request and corresponding GGSN response, the
following activities are performed:
1. SGSN initiates RAB Assignment Request to the RNC, now requesting MBR value (for
example, 21 Mbps) and also alternative MBR of 16 Mbps in alternative RAB IE.
2. If the extended MBR exists in RAB assignment and RNC/UE is R6 or older and
if SGSN sends alternative RAB, the RNC answers to the SGSN with RAB Assignment
Response(s), setting assigned RAB to 16 Mbps.
If not, RNC sets Failed, cause=33 into RAB Assignment Response (because SGSN did
not provide 16Mbps DL alternative). Then, SGSN can repeat RAB assignment with lower
value.
3. SGSN initiates the Update PDP Context message request to GGSN with modified QoS
(Common Flags IE with the No QoS negotiation bit set to 1 only in case of Direct Tunnel
PDP Context).
3.4.5.3 Non-supporting UE
Workaround for UE not supporting the extended MBR rates (R99/R4 terminal,
R5/R6/Partial R7 terminal).
Problem description: R99/R4 terminal

After receiving the initial PDP Context Request (QoS IE length =11), SGSN applies R99 QoS
profile and limits the MBR to max 8.64 Mbps. The corresponding request is done to GGSN
response.
Later, the SGSN requests RAB setup as usual (MBR=8.64 Mbps) and RNC acknowledges this
request. SGSN then sends active PDP Context Accept to UE with negotiated QoS
(MBR=8.64).
Here, no extended octets are sent.
Problem description: R5/R6/Partial R7 terminal

After receiving the initial PDP Context Request (QoS IE Length =14), with extended octets,
SGSN negotiates the DL MBR according to the subscribed value (QoS profile from HLR/HSS)

SGSN User Guide
and request PDP context from GGSN including extended octets.
Then GGSN answers and RAB assignment from SGSN can be done, again with extended QoS
octets and RNC acknowledges this request. SGSN sends active PDP Context Accept to UE
with negotiated QoS.
Note:
Some UEs will reject the PDP Context Accept message with MBR exceeding 16 Mbps
and deactivate the PDP context.
Workaround
1. Limit MBR in HLR/HSS:
As a temporary solution, the MBR in the HLR/HSS subscriptions can be limited to 16
Mbps. It also impacts high-end subscribers.
2. RNC to change QoS/RAB based on UE release (alternative RAB):
If extended MBR exists in RAB assignment and UE is R6 or older, and if SGSN send
alternative RAB, then RNC answers to the SGSN with RAB assignment response(s),
setting the assigned RAB to 16 Mbps.
If not, the RNC sets "Failed, cause=33" into RAB Assignment Response and SGSN can
repeat RAB assignment with lower value.
3. RAB reconfiguration by RNC prior to SGSN sending PDP Accept.
4. UE (IMEI) specific policy to be applied.
3.4.5.4 SRNS relocation cases

Inter-SGSN and intra-SGSN SRNS relocation scenarios.
Inter-SGSN case
In the inter-SGSN SRNS relocation scenario, the new SGSN will request the target RNC to
establish same RABs as currently existing on source RNC. In case of any restrictions, SGSN
can apply similar handling as in the intra-SGSN case.
Intra-SGSN case
In the intra-SGSN SRNS relocation scenario, the existing SGSN will request the target RNC to

SGSN User Guide
establish same RABs as currently existing on source RNC. Challenges might occur when
target RAN does not support 3GPP R7 yet. In such case, SGSN can again apply the known
workaround of limiting the MBR on RNC basis. The values in the RNC parameter set are also
used by SGSN in these mobility cases.
Scenario 1: intra-SGSN, from R7 RAN to R6 RAN

PDP context and RAB have been set up, respecting possible MBR limits set by RAN or UE. The
UE is in the PMM-Connected state.
1. Source RNC initiates SRNS relocation (relocation required).
2. SGSN sends Relocation Request to target RNC (including RAB parameters). Since target
RAN is 3GPP R6 level, SGSN will need to limit the RAB to corresponding values (MBR=16
Mbps). This can be done by configuring the MBR on RNC level as part of RNC parameter
set in SGSN.
3. Target RNC acknowledges the Relocation Request.
4. SGSN sends Relocation Command to source RNC.
5. Optionally, SGSN initiates the Update PDP Context message request to GGSN (with
modified QoS).
Note:
The Common Flags IE with the No QoS negotiation bit is set to 1 only in case of
Direct Tunnel PDP Context.

7. Optionally, the modify PDP context procedure (with revised QoS) is executed (in case of
R7 capable UE)
Scenario 2: intra-SGSN, from R6 RAN to R7 RAN

PDP context and RAB have been set up, expecting possible MBR limits set by RAN or UE. The
UE here is in the PMM-Connected state.
1. Source RNC initiates the SRNS relocation (Relocation Required).
2. SGSN sends Relocation Request to target RNC (including RAB parameters). Since source
RAN is 3GPP R6 level, SGSN will request RAB according to these corresponding values (so
MBR remains 16 Mbps).
3. Target RNC acknowledges the Relocation Request.
4. SGSN sends Relocation Command to source RNC.
5. Optionally, SGSN initiates the Update PDP Context message request to GGSN (Common

SGSN User Guide
Flags IE with the No QoS negotiation bit set to 1 only in case of Direct Tunnel PDP
Context).
3.4.5.5 Roaming support

Roaming support scenarios and solutions.
Scenario 1: HPLMN has HSPA+ enabled with GGSN/HLR(HSS) being 3GPP R7

compliant. VPLMN has not enabled HSPA+, RNC/SGSN on 3GPP R6 level.
With SGSN on R6 level (SG6 release), the maximum bit rate SGSN requests to RNC in RAB
assignment request procedure is 16 Mbps.
Scenario 2: HPLMN has HSPA+ enabled with GGSN/HLR(HSS) being 3GPP R7

compliant. VPLMN has not enabled HSPA+, RNC on 3GPP R6 level and SGSN
on 3GPP R7.
With SGSN on SG7 release and HLR/HSS-limit on 21 Mbps, the maximum bit rate SGSN
requests to RNC in RAB assignment request procedure is 21 Mbps (SGSN negotiates MBR
according to HLR/HSS limit)
Scenario 3: SGSN has received a QoS profile from the HLR/HSS with MBR = 21
Mbps, and a UE connected to a 2G RAN has signaled Subscribed QoS.
SGSN sends a maximum of 2 Mbps depending on the values of prFile parameters
override2gDowngrade and qosHandlingInIsho.
QosHandlingInIsho is dominant parameter, so if it is true, override2gDowngrade

does not have any impact. When QosHandlingInIsho is true, bit rates are always
negotiated in inter-system handover (ISHO) case.
Scenario 4: SGSN – Qos Control per Roaming Partner

The existing feature QoS control for Roaming Subscriber (SG01067) is enhanced in such a
way that each roaming partner may have its own QoS parameter set. This enables QoS
control per roaming partner.

SGSN User Guide
3.5 I-HSPA enhancement (Features SG01142 and

The I-HSPA (internet high-speed packet access) enhancement feature provides operators
with a more streamlined flat UMTS terrestrial radio access network (UTRAN). This
simplifies network architecture by replacing separate RNCs with I-HSPA NodeBs (base
stations with PS RNC functionality).

SGSN User Guide
Table 53: I-HSPA enhancement (Features SG01142 and f52050-01): feature summary
Function Impact
Capacity • The introduction of I-HSPA NodeBs into the radio access network
creates more mobility events to the SGSN because it increases the
number of relocation procedures.
• The maximum number of congurable RNCs per CMM is 512.
• The total number of I-HSPA NodeBs for each CMM is limited to
8192.
• The number of normal RNCs affects the total capacity by
decreasing the maximum number of I-HSPA NodeBs. For example, if
there are 10 normal RNCs connected to the SGSN, only 8182 I-HSPA
NodeBs can be congured with this feature.
Required features • 3G access support (Feature SG01119)

• HSDPA, HSUPA Support and HSPA+ (Feature SG02104)
Interworking/dependent • HSDPA, HSUPA Support and HSPA+ (Feature SG01113)

features • Direct tunnel and smart device direct tunnel signaling optimization
(Feature SG02017)
Restrictions • Iu over ATM is not supported. This feature only supports Iu over IP.
• SCTP multi-homing conguration for the I-HSPA NodeBs should be
preferred over the single-homing one, since it already includes
redundancy on SCTP level. One multi-homed SCTP connection per I-
HSPAs is allowed.
Conguration Command features, parameter iHspaEnabler

management Command rnc to create I-HSPA NodeBs
Command gParm, parameter highCapacityIHspa to enable
the extended capacity of the RNCs/I-HSPAs.
Charging None
Counters None
Alarms None
Feature ID SG01142, f52050-01

SGSN User Guide
Note:
The high number of Iu links prolongates the recovery time for SGSN access services
after a CMM restart (planned, duplex failure or loss of all PAPS).
When CMM is deployed with 8K RNC/I-HSPA, it may require up to one hour until SGSN
services become fully operational again.
To avoid service outrage during this period, CMM should be deployed in a pooling
setup.
3.5.1 Configuring I-HSPA enhancement

Feature I-HSPA enhancement requires activation.
Procedure
cmm features modify iHspaEnabler --status true
2 Create an I-HSPA NodeB to the SGSN.
Use the rnc command to create, modify, or delete I-HSPA NodeBs (base station with
RNC functionality). The type of RNC is IHSPA:
cmm rnc create --rncId <integer> --rncName <string> --toA

<SPC,GT> --pSetId <integer> --type IHSPA --ni <IN0,IN1,NA0,NA1> -
-spc <integer> --mcc <digits> --mnc <digits>
rncId RNC identication
rncName name of RNC
toA type of RNC address (SPC, GT)
pSetId RNC parameter set
type type of RNC (RNC, IHSPA)
ni network indicator (IN0, IN1, NA0, NA1)

SGSN User Guide
spc signaling point code
mcc mobile country code
mnc mobile network code
Step result
When attach to the SGSN via the I-HSPA NodeB is successful, subscriber's access type I-
HSPA is shown with the following command:
cmm subscriber show -–imsi <>
3 Enable the extended capacity of the iHSPAs.
Set up a total sum of 8192 iHSPAs and RNCs (of which only up to 512 may be RNCs).
cmm gParms modify --gParmName highCapacityIHspa –-gParmValue Yes
or
Set up a total sum of 512 iHSPAs and RNCs.
cmm gParms modify --gParmName highCapacityIHspa –-gParmValue No
3.6 SS7 over IP (Features SG01051, SG01105, SG01771 and

SS7 over IP enables the SGSN to monitor the number of PDP context activation requests
coming from the UE, at a monitoring period configured by the operator.
Table 54: SS7 over IP (Features SG01051, SG01105, SG01771 and f60210-29): feature
summary
Function Impact
Compliance • IETF RFC 2960: Stream Control Transmission Protocol

• IETF RFC 3309: Stream Control Transmission Protocol (SCTP) Checksum Change
• IETF RFC 3332: Signaling System 7 (SS7) Message Transfer Part 3 (MTP3) - User Adaptation Layer (M3UA)
Capacity None
Interworking/dependent features None
Restrictions None

SGSN User Guide
Function Impact
Conguration management Commands:

• muaOwnSignallingPoint
• muaAssociationSet
• muaAssociation
• muaAssociationList
• muaLink
• muaRoute
• muaSignallingRoute
• muaSignallingRouteList
• muaService
• sccpSignallingPoint
• sccpSubsystem
• sccpSubsystemList
• routeParamSet
• subParamSet
• spcParamSet
• gtAnalysis
• gtCallingAnalysis
• gtLoadSharingNet
• gtAnalysisResult
• gtCallingAnalysisResult
• gtModificationData
• mapAddrAnalysis
• mapAddrAnalysisResAddr
• mapApplicationContextDefault
• mapDefaultParameter
• mapAddrAnalysisResult
• mapApplicationContextResult

SGSN User Guide
Function Impact
Counters SS7 supported counters:

• M042C000 / ROUTING_FAILURE_OF_GT_TYPE_1
• M042C004 / ROUTING_FAILURE_OF_UNKNOWN_GT
• M042C005 / ROUTING_FAILURE_OF_SPECIFIC_GT
• M042C006 / ROUTING_FAILURE_NET_FAILURE
• M042C007 / ROUTING_FAILURE_NET_CONGESTION
• M042C008 / ROUTING_FAILURE_SUBSYS_FAILURE
• M042C009 / ROUTING_FAILURE_SS_CONGESTION
• M042C010 / ROUTING_FAILURE_UNEQUIPPED_USR
• M042C011 / ROUTING_FAILURE_REASON_UNKNOWN
• M042C012 / SYNTAX_ERROR_DETECTED
• M042C013 / UDT_MESSAGES_SENT
• M042C014 / UDT_MESSAGES_RECEIVED
• M042C015 / UDTS_MESSAGES_SENT
• M042C016 / UDTS_MESSAGES_RECEIVED
• M042C017 / XUDT_MESSAGES_SENT
• M042C018 / XUDT_MESSAGES_RECEIVED
• M042C019 / XUDTS_MESSAGES_SENT
• M042C020 / XUDTS_MESSAGES_RECEIVED
• M042C021 / LUDT_MESSAGES_SENT
• M042C022 / LUDT_MESSAGES_RECEIVED
• M042C023 / LUDTS_MESSAGES_SENT
• M042C024 / LUDTS_MESSAGES_RECEIVED
• M042C025 / ROUTING_FAILURE_UNKN_DEST_ADDR
• M042C026 / CR_MESSAGES_SEND_TO_MTP
• M042C027 / CR_MESSAGES_RECEIVED_FROM_MTP
• M042C028 / CREF_MESSAGES_SENT_TO_MTP
• M042C029 / CREF_MESSAGES_RXED_FROM_MTP
• M042C030 / RSR_MESSAGES_SENT_TO_MTP
• M042C031 / RSR_MESSAGES_RECEIVED_FROM_MTP
• M042C032 / ERR_MESSAGES_SENT_TO_MTP
• M042C033 / ERR_MESSAGES_RECEIVED_FROM_MTP
• M042C034 / FAILURE_REL_COMPL_SUP_DPC_CL_2
• M042C035 / FAILURE_REL_COMPL_SUP_DPC_CL_3
• M042C036 / TIMER_TIAR_EXPIRY_FOR_DPC_CL_2
• M042C037 / TIMER_TIAR_EXPIRY_FOR_DPC_CL_3
• M042C038 / RESET_OF_CONNECTION_TO_DPC
• M042C039 / RELEASE_OF_CONNECTION_TO_DPC
• M043C000 / TOTAL_MSGS_TO_LOC_SS_NO_GT
• M043C001 / TOTAL_MSGS_TO_LOC_SS_WITH_GT
• M043C002 / TOTAL_MSGS_FROM_LOC_SS_NO_GT
• M043C003 / TOTAL_MSGS_FROM_LOC_SS_WITH_GT
• M043C004 / TOTAL_MESSAGES_FOR_LOCAL_SS
• M043C005 / MESSAGES_SENT_TO_BACKUP_SS
• M043C006 / TOTAL_MESSAGES_SENT_CLASS_0
• M043C007 / TOTAL_MESSAGES_SENT_CLASS_1
• M043C008 / TOTAL_MESSAGES_RXED_CLASS_0
• M043C009 / TOTAL_MESSAGES_RXED_CLASS_1
• M043C010 / DT1_MESSAGES_RECEIVED_FROM_MTP
• M043C011 / DT1_MESSAGES_SENT_TO_MTP
• M043C012 / DT2_MESSAGES_RECEIVED_FROM_MTP
• M043C013 / DT2_MESSAGES_SENT_TO_MTP
• M043C014 / ED_MESSAGES_RECEIVED_FROM_MTP
• M043C015 / ED_MESSAGES_SENT_TO_MTP
• M043C016 / MSGS_TOO_BIG_FOR_SEGMENTATION
• M044C000 / SCCP_MSGS_TO_LOCAL_SUBSYSTEM
• M044C001 / SCCP_MSGS_FROM_LOCAL_SUBSYSTEM
• M044C002 / SCCP_STP_MESSAGES_HANDLED
• M044C003 / USER_INDEPENDENT_MESSAGES
• M044C004 / TOTAL_SCCP_MESSAGES_HANDLED
• M044C005 / MSGS_REQ_GTT_TO_LOCAL_SUBSYS
• M044C006 / MSGS_REQ_GTT_FROM_LOCAL_SUBSYS
• M044C007 / SCCP_STP_MSGS_REQUIRING_GTT
• M044C008 / TOTAL_MESSAGES_REQUIRING_GTT
• M044C009 / REASS_ERRORS_TIMER_EXPIRES
• M044C010 / REASS_ERRORS_SEGM_OUT_OF_SEQ
• M044C011 / REASS_ERRORS_NO_REASS_SPACE
• M044C012 / REASS_ERRORS_REASSEMBLY_FAILED
• M044C013 / SEGM_ERRORS_SEGM_NOT_SUPPORTED
• M044C014 / SEGM_ERRORS_SEGMENTATION_FAIL
• M044C015 / HOP_COUNTER_VIOLATIONS
• M045C000 / ABORT_RXED_UNREC_MESSAGE_TYPE
• M045C001 / ABORT_SENT_UNREC_MESSAGE_TYPE
• M045C002 / ABORT_RXED_INCOR_TRANSACT_PORT
• M045C003 / ABORT_SENT_INCOR_TRANSACT_PORT
• M045C004 / ABORT_RXED_BADLY_FORMATTED_TAP
• M045C005 / ABORT_SENT_BADLY_FORMATTED_TAP
• M045C006 / ABORT_RXED_UNREC_TRANSACT_ID
• M045C007 / ABORT_SENT_UNREC_TRANSACT_ID
• M045C008 / ABORT_RXED_RESOURCE_LIMITATION
• M045C009 / ABORT_SENT_RESOURCE_LIMITATION
• M045C010 / REJECT_RXED_UNREC_COMPONENT
• M045C011 / REJECT_SENT_UNREC_COMPONENT
• M045C012 / REJECT_RXED_MISTYPED_COMPONENT
• M045C013 / REJECT_SENT_MISTYPED_COMPONENT
• M045C014 / REJECT_RXED_BADLY_STRUCT_COMP
• M045C015 / REJECT_SENT_BADLY_STRUCT_COMP
• M045C016 / REJECT_RXED_UNREC_LINKED_ID
• M045C017 / REJECT_SENT_UNREC_LINKED_ID
• M045C018 / REJECT_RXED_UNREC_INVOKE_ID_RR
• M045C019 / REJECT_SENT_UNREC_INVOKE_ID_RR
• M045C020 / REJECT_RXED_RETURN_RESULT_UNEX
• M045C021 / REJECT_SENT_RETURN_RESULT_UNEX
• M045C022 / REJECT_RXED_UNREC_INVOKE_ID_RE
• M045C023 / REJECT_SENT_UNREC_INVOKE_ID_RE
• M045C024 / REJECT_RXED_RETURN_ERROR_UNEXP
• M045C025 / REJECT_SENT_RETURN_ERROR_UNEXP
• M045C026 / REJECT_RXED_DUPLIC_INVOKE_ID
• M045C027 / REJECT_SENT_DUPLIC_INVOKE_ID
• M045C028 / REJECT_RXED_UNREC_OPERATION
• M045C029 / REJECT_SENT_UNREC_OPERATION
• M045C030 / REJECT_RXED_MISTYPED_PARAMETER
• M045C031 / REJECT_SENT_MISTYPED_PARAMETER
• M045C032 / REJECT_RXED_RESOURCE_LIMITAT
• M045C033 / REJECT_SENT_RESOURCE_LIMITAT
• M045C034 / REJECT_RXED_INITIATING_RELEASE
• M045C035 / REJECT_SENT_INITIATING_RELEASE
• M045C036 / REJECT_RXED_LINKED_RESP_UNEXP
• M045C037 / REJECT_SENT_LINKED_RESP_UNEXP
• M045C038 / REJECT_RXED_UNEXP_LINKED_OPER
• M045C039 / REJECT_SENT_UNEXP_LINKED_OPER
• M045C040 / REJECT_RXED_UNRECOGNIZED_ERROR
• M045C041 / REJECT_SENT_UNRECOGNIZED_ERROR
• M045C042 / REJECT_RXED_UNEXPECTED_ERROR
• M045C043 / REJECT_SENT_UNEXPECTED_ERROR
• M045C044 / REJECT_RXED_MISTYPED_PARAM_RR
• M045C045 / REJECT_SENT_MISTYPED_PARAM_RR
• M045C046 / REJECT_RXED_MISTYPED_PARAM_RE
• M045C047 / REJECT_SENT_MISTYPED_PARAM_RE
• M045C048 / TC_L_CANCEL_IND_FOR_CL_1_OPER
• M045C049 / MESSAGES_DISCARDED
• M045C050 / PROVIDER_ABORTS_RECEIVED
• M045C051 / REJECTS_RECEIVED
• M045C052 / ERRORS_IN_TRANSACTION_PORTION
• M045C053 / SENT_TC_UNIDIRECTIONAL_MSGS
• M045C054 / RXED_TC_UNIDIRECTIONAL_MSGS
• M045C055 / SENT_TC_BEGIN_MESSAGES
• M045C056 / RXED_TC_BEGIN_MESSAGES
• M045C057 / SENT_TC_CONTINUE_MESSAGES
• M045C058 / RXED_TC_CONTINUE_MESSAGES
• M045C059 / SENT_TC_END_MESSAGES
• M045C060 / RXED_TC_END_MESSAGES
• M045C061 / SENT_TC_ABORT_MESSAGES
• M045C062 / RXED_TC_ABORT_MESSAGES
• M045C063 / TOTAL_SENT_TC_MESSAGES
• M045C064 / TOTAL_RXED_TC_MESSAGES
• M045C065 / SENT_TC_COMPONENTS
• M045C066 / RXED_TC_COMPONENTS

SGSN User Guide
Function Impact
Alarms None
Feature ID SG01051, SG01105, SG01771 and f60210-29

SGSN User Guide
4. End user management
4.1 IMEI check with EIR (Features SG01106, SG01090,

SG02156 and f60210-17): feature summary
The IMEI check with EIR feature enables the identification of the mobile equipment (ME)
together with the equipment identity register (EIR).
Table 55: IMEI check with EIR (Features SG01106, SG01090, SG02156 and f60210-17):
feature summary
Function Impact
Compliance • GSM 23.060 General Packet Radio Service (GPRS) Service Description;
Stage 2
• GSM 24.008 Mobile Radio Interface Layer 3 specication
Capacity None
Interworking/dependent • GPRS mobility management (Feature SG01011)

• IMEISV in CDR (Feature SG01088)
• Detach timer optimization and control (Feature SG02035)
• S13' IMEI checking (Feature SG02220)
Restrictions The functionality of this feature is restricted by the interface

congured between the SGSN and the EIR. This feature requires the Gf
interface to be congured between the SGSN and the EIR.

SGSN User Guide
Function Impact
Conguration Command features, parameters impImeiChk, noCsDet

management Command plmnParam, parameter blackListEffect, and
parameters for procedure selections and IMEI check repetition rate
provisioning:
• gbGprsAttImei
• iuComRaLaImei
• gbImsiAttImei
• iuImsiAttImei
• gbMoPdpActImei
• iuMoPdpActImei
• gbMoPdpDeaImei
• iuMoPdpDeaImei
• gbNormRaImei
• iuNormRaImei
• gbNormRaImeiVisitor
• iuNormRaImeiVisitor
• gbPeriodicRaImei
• iuPeriodicRaImei
• iuServReqImei
• gbMoGprsDeaImei
• iuMoGprsDeaImei
• gprsAttImeiChk
• imsiAttImeiChk
• normalRauImeiChk
• normalRauImeiChkVisitor
• periodRauImeiCh
• detachImeiChk
• pdpActImeiChk
• pdpDeactImeiChk
• serviceReqImeiChk
Command securityParam, parameter imeiCheckMode
Counters None
Alarms None
Feature ID SG01106, SG01090, SG02156, f60210-17
4.1.1 Configuring IMEI check with EIR

This feature uses the Gf interface between the SGSN and the EIR. The feature requires
activation. You can set the IMEI check repetition rates for different mobility management
procedures.

SGSN User Guide
Procedure
1 Activate the IMEI checking mode.
cmm securityParam modify --imeiCheckMode true config

Step result
To check parameter status: cmm securityParam show
2 Configure IMEI check procedures
Step example
To enable IMEI status check from EIR for GPRS attach: cmm plmnParam modify
STPLMN --gprsAttImeiChk true
To enable IMEI status check from EIR for IMSI attach: cmm plmnParam modify
STPLMN --imsiAttImeiChk true
3 Configure IMEI check repetition rates.
Step example
To configure IMEI check repetition rate for Gb GPRS attach, Iu GPRS attach, Gb MO GPRS
detach, and Iu MO GPRS detach:
cmm plmnParam modify STPLMN --gbGprsAttImei 1 --iuGprsAttImei 1 -

-gbMoGprsDeaImei 1 --iuMoGprsDeaImei 1
4 Activate enhanced IMEI check control (SG01090).
With enhanced IMEI check control feature (SG01090), you can block or allow denylisted
mobile equipment. The default value of the blackListEffect parameter is block.
4.1 Activate the feature.
cmm features modify impImeiChk --status true
4.2 Configure denylisting.
Step example
cmm plmnParam modify --blackListEffect allow
Step result

SGSN User Guide
Note:
When feature S13 IMEI checking (SG02220) is activated, the blackListEffect

parameter is not visible.
Check that SGSN S4 functionality (Gr/S6d) is OFF: cmm gParms show --

gParmName s4Func
Check that S13' IMEI checking is false: cmm features show s13ImeiChecking
5 Activate CS service for denylisted IMEI (SG02156) (optional).
cmm features modify noCsDet --status true
When feature SG02156 is activated, a rejection cause code #7 'GPRS services not
allowed' is used instead of a cause code # 6 'Illegal ME'. The default value of the
noCsDet parameter is false.
4.2 SGSN support for IMEISV in check IMEI EIR over Gf

This feature adds SGSN support to use the IMEISV for the IMEI check procedure to the EIR
over the Gf interface.

SGSN User Guide
Table 56: SGSN support for IMEISV in check IMEI EIR over Gf (Feature f52074-01): feature
summary
Function Impact
Compliance 3GPP TS 29.002: Mobile Application Part (MAP) specication (Release

16), v16.0.0
Capacity None
Required features IMEI check must be congured; see IMEI check with EIR (Features
SG01106, SG01090, SG02156 and f60210-17)
Interworking/dependent When this feature is enabled, the IMEISV replaces the IMEI in the check
features IMEI procedure in all checkImeiMode instances:
• 0: the SGSN includes only the IMEI(SV) in the IMEI check.
• 1: the SGSN adds the IMSI in the MAP part of the IMEI check.
• 2: the SGSN adds the IMSI and MSISDN in the TCAP part of IMEI
check.
Restrictions None
Conguration Command securityParam, parameter imeiCheckMode

management Command plmnParam, parameter iuImsiAttImei
Command prFile, parameter checkImeiSv
Counters None
Alarms None
4.2.1 Configuring the use of the IMEISV for authentication

to the EIR via the Gf interface
After the IMEI authentication is enabled, the IMEISV can be configured using prFile for
authentication to the EIR via the Gf interface.
Procedure
1 Configure the CMM for the IMEI authentication.
cmm securityParam modify config --imeiCheckMode true
2 Verify that the IMEI authentication is active.

SGSN User Guide
cmm securityParam show
Step example
The following part of the command output indicates that the IMEI authentication is
enabled:
+-----------------------+------------+
| Field | Value |
+-----------------------+------------+
| securityParam | config |
| authenticationMode | whenNeeded |
| imeiCheckMode | true |
| imeiRequestMode | false |
| ptmsiSignatureMode | false |
| cipheringMode | false |
| umtsCipheringMode | true |
| attachRestriction | false |
| umtsAttachRestriction | false |
+-----------------------+------------+
3 For a specified PLMN, set the procedure for which authentication with the EIR will be
requested (for example, iu IMSI attach).
cmm plmnParam modify <plmnParamId> --iuImsiAttImei 1
4 Verify which procedures will request authentication with the EIR.
cmm plmnParam show
Step example
The following part of the command output indicates that the IMEI authentication is
enabled:

SGSN User Guide
+----------------------------+-------------+
| Field | Value |
+----------------------------+-------------+
| plmnParam | PLMN_ID |
| plmnParamId* | PLMN_ID |
… … … …
| iuImsiAttImei | 1 |
… … … …
+----------------------------+-------------+
5 Activate this feature to enable the authentication with IMEISV.
cmm prFile modify checkImeiSv --status true
Table 57: checkImeiSv parameter values
Value Purpose
true The IMEISV is used at authentication with the EIR
false The IMEI is used at authentication with the EIR
6 Verify that the feature is active.
cmm prFile show checkImeiSv
Step example
The following part of the command output indicates that the feature is enabled:
+-----------+-------------+
| Field | Value |
+-----------+-------------+
| prFile | checkImeiSv |
| status | true |
| parameter | CheckImeiSv |
+-----------+-------------+

SGSN User Guide
4.3 HLR-based 2G/3G access control (Feature SG02114):

feature summary
This feature enables the operator to handle subscribers' access to different radio
networks, even without the correct authentication methods. Therefore, the operator can
control 2G and 3G subscribers' access to 2G and 3G radio networks, and set 2G or 3G
access for each subscriber separately.
Table 58: HLR-based 2G/3G access control (Feature SG02114): feature summary
Function Impact
Compliance • 3GPP TS 29.002 Mobile Application Part (MAP)

• 3GPP TS 23.060 General Packet Radio Service (GPRS)
Capacity None
Interworking/dependent Controlled roaming (Feature SG01004)

features
Restrictions If the subscribers do not have any authentication vectors in the

subscriber database of the SGSN, the type of the subscribers (2G
or 3G) cannot be determined. Therefore, the SGSN local PLMN
specic access registration check cannot be performed.
Conguration management Command features, parameter hlr2g3gAccCtr

Command plmnParam, parameters (network access rights,
access reject cause codes)
• accRestrGtoG
• accRestrGtoU
• accRestrUtoG
• accRestrUtoU
• accRestrCauGtoG
• accRestrCauGtoU
• accRestrCauUtoG
• accRestrCauUtoU
• accRestrCauR97
• accRestrCauCnt
Command subscriber, parameter imsi
Command system, parameters ardMode,
subsDataKeepMode
Command securityParam, parameter
authenticationMode

SGSN User Guide
Function Impact
Counters M004C115 / SUBSCRIBER ACCESS TO GERAN REJECTED DUE TO

HLR BASED ACCESS RESTRICTION
M004C119 / SUBSCRIBER ACCESS TO UTRAN REJECTED DUE TO
HLR BASED ACCESS RESTRICTION
M004C116 / GSM SUBSCRIBER ACCESS TO GERAN REJECTED DUE
TO LOCAL ACCESS RESTRICTION
M004C117 / UMTS SUBSCRIBER ACCESS TO GERAN REJECTED DUE
M004C120 / GSM SUBSCRIBER ACCESS TO UTRAN REJECTED DUE
M004C121 / UMTS SUBSCRIBER ACCESS TO UTRAN REJECTED DUE
Alarms None
Feature ID SG02114
4.3.1 Configuring HLR-based 2G/3G access control

The procedure includes steps for activating and configuring the HLR-based 2G/3G access
control feature.
Purpose
The HLR based 2G/3G access control feature supports the following functionalities:
HLR Access Restriction Data parameter

SGSN local PLMN specific access restriction
Note:
The HLR access restriction data functionality is used to verify the feature activation.
Before you start
Set the GSM/EDGE Radio Access Network (GERAN) or the UMTS Terrestrial Radio Access
Network (UTRAN) to "restricted" in the HLR.
For the test environment, the following elements are required:
Serving GPRS Support Node (SGSN)

Home Location Register (HLR)

SGSN User Guide
Base Station Controller (BSC) or Radio Network Controller (RNC)

Mobile Station (MS)
Note:
Ensure that the QoS control for roaming subscribers (SG01067) feature, does not
prevent attaches while testing the HLR based 2G/3G access control, because the
SG01067 feature, can, also, set restrictions for subscribers' access to the radio
network (RNW).
Procedure
# cmm features modify hlr2g3gAccCtr --status true
2 Verify that the feature is active.
# cmm features show hlr2g3gAccCtr
Step example
The following part of the command output, indicates that the feature is enabled:
+-----------+---------------------------------------------------+
| Field | Value |
+-----------+---------------------------------------------------+
| features | hlr2g3gAccCtr |
| status | true |
| parameter | SGSN HLR Based 2G/3G access control |
+-----------+---------------------------------------------------+
3 In the SGSN, set the parameters below to the following values:
Set authenticationMode parameter to "act"
# cmm securityParam modify --authenticationMode act config
Set Access Restriction Data parameter to "true"

SGSN User Guide
# cmm system modify --ardMode true config
Set parameter Store Subscriber Data value to "true"
# cmm system modify --subsDataKeepMode true config
To ensure that the feature is activated and properly configured, follow the steps:
1. Delete the subscriber from the SGSN (if the subscriber data already exists in the SGSN)
# cmm subscriber delete --imsi xxx
where xxx is the subscribers' IMSI number.

2. Switch the 2G/3G MS on and try to attach to the 2G/3G network
3. Check the subscribers' information
# cmm subscriber show --imsi xxx
The subscriber is deleted from the SGSN, the attach is rejected, and the subscriber cannot
be found in the SGSN.
4.3.2 Additional configuration for HLR-based 2G/3G

access control
4.3.2.1 Configuring access rights for a GSM subscriber to

the GSM network
To configure access rights for a GSM subscriber to the GSM network, use the
accRestrGtoG parameter of the plmnParam command.
▪ Configure access rights for a GSM subscriber to the GSM network.
# cmm plmnParam modify ETPLMN --accRestrGtoG <value>

SGSN User Guide
Table 59: Values of access rights for a GSM subscriber to the GSM network
Value Purpose
notUsed Access rights are ignored
allowed Access rights are granted
notAllowed Access rights are denied
Note:
Before the user enters a value, the value-field is blank. For this case, notUsed is
considered to be the default value.
4.3.2.2 Configuring access rights for a GSM subscriber to

the UMTS network
To configure access rights for a GSM subscriber to the UMTS network, use the
accRestrGtoU parameter of the plmnParam command.
▪ Configure access rights for a GSM subscriber to the UMTS network.
# cmm plmnParam modify ETPLMN --accRestrGtoU <value>
Table 60: Values of access rights for a GSM subscriber to the UMTS network
Value Purpose
Note:

SGSN User Guide
4.3.2.3 Configuring access rights for a UMTS subscriber to

the GSM network
To configure access rights for a UMTS subscriber to the GSM network, use the
accRestrUtoG of the plmnParam command.
▪ Configure access rights for a UMTS subscriber to the GSM network.
# cmm plmnParam modify ETPLMN --accRestrUtoG <value>
Table 61: Values of access rights for a UMTS subscriber to the GSM network
Value Purpose
Note:
4.3.2.4 Configuring access rights for a UMTS subscriber to

the UMTS network
To configure access rights for a UMTS subscriber to the UMTS network, use the
accRestrUtoU parameter of the plmnParam command.
▪ Configure access rights for a UMTS subscriber to the UMTS network.
# cmm plmnParam modify ETPLMN --accRestrUtoU <value>

SGSN User Guide
Table 62: Values of access rights for a UMTS subscriber to the UMTS network
Value Purpose
Note:
4.3.2.5 Configuring reject cause code for a GSM subscriber

to the GSM network
To configure reject cause code for a GSM subscriber to the GSM network, use the
accRestrCauGtoG parameter of the plmnParam command.
▪ Configure reject cause code for a GSM subscriber to the GSM network.
# cmm plmnParam modify ETPLMN --accRestrCauGtoG <value>
Table 63: Values of reject cause code for a GSM subscriber to the GSM network
Value Purpose
la Location area not allowed
plmn PLMN not allowed
roamLa Roaming not allowed
gprsPlmn GPRS services not allowed in this PLMN
cellLa No suitable cells in LA
notUsed Not set

SGSN User Guide
4.3.2.6 Configuring reject cause code for a GSM subscriber

to the UMTS network
To configure reject cause code for a GSM subscriber to the UMTS network, use the
accRestrCauGtoU parameter of the plmnParam command.
▪ Configure reject cause code for a GSM subscriber to the UMTS network.
# cmm plmnParam modify ETPLMN --accRestrCauGtoU <value>
Table 64: Values of reject cause code for a GSM subscriber to the UMTS network
Value Purpose
notUsed Not set
4.3.2.7 Configuring reject cause code for a UMTS

subscriber to the GSM network
To configure reject cause code for a UMTS subscriber to the GSM network, use the
accRestrCauUtoG parameter of the plmnParam command.
▪ Configure reject cause code for a UMTS subscriber to the GSM network.
# cmm plmnParam modify ETPLMN --accRestrCauUtoG <value>

SGSN User Guide
Table 65: Values of reject cause code for a UMTS subscriber to the GSM network
Value Purpose
notUsed Not set
4.3.2.8 Configuring reject cause code for a UMTS

subscriber to the UMTS network
To configure reject cause code for a UMTS subscriber to the UMTS network, use the
accRestrCauUtoU parameter of the plmnParam command.
▪ Configure reject cause code for a UMTS subscriber to the UMTS network.
# cmm plmnParam modify ETPLMN --accRestrCauUtoU <value>
Table 66: Values of reject cause code for a UMTS subscriber to the UMTS network.
Value Purpose
notUsed Not set

SGSN User Guide
4.3.2.9 Configuring reject cause code for an R97/98

terminal to the UMTS network
To configure reject cause code for an R97/98 terminal to the UMTS network, use the
accRestrCauR97 parameter of the plmnParam command.
▪ Configure reject cause code for an R97/98 terminal to the UMTS network.
# cmm plmnParam modify ETPLMN --accRestrCauR97 <value>
Table 67: Values of reject cause code for an R97/98 terminal to the UMTS network
Value Purpose
notUsed Not set
4.3.2.10 Configuring reject cause code for subscriber

count
To configure reject cause code for subscriber count, use the accRestrCauCnt
parameter of the plmnParam command.
▪ Configure reject cause code for subscriber count.
# cmm plmnParam modify ETPLMN --accRestrCauCnt <value>

SGSN User Guide
Table 68: Values of reject cause code for subscriber count
Value Purpose
notUsed Not set
4.4 GTP information sending (Feature SG01082): feature

summary
With this feature, the SGSN provides the gateway GPRS support node (SGSN) with
additional information to allow more complex charging based on the location of the
mobile station (MS) and the time of the day.

SGSN User Guide
Table 69: GTP information sending (Feature SG01082): feature summary
Function Impact
Compliance 3GPP TS 29.060 General Packet Radio Service

(GPRS); GPRS Tunneling Protocol (GTP) across
the Gn and Gp interface
Capacity None
Interworking/dependent features IMEISV in CDR (Feature SG01088)
Restrictions None

gtpInfoSending
Command prFile, parameter
locChangeInfoUpd
Counters None
Alarms None
Feature ID SG01082
4.5 Enable faulty IMEISV UE (Feature SG01171): feature

summary
With this feature, the operator can control the faulty IMEISV UE in the SGSN.

SGSN User Guide
Table 70: Enable faulty IMEISV UE (Feature SG01171): feature summary
Function Impact
Capacity None
Interworking or dependent • GTP information sending (Feature SG01082)

features • IMEISV in CDR (Feature SG01088)
Restrictions None
Conguration management Command features, parameter faultyImeisv
Counters None
Alarms None
Feature ID SG01171
4.6 Terminal management support (Features SG02203,

This feature provides support for terminal provisioning for GPRS subscribers using
enhanced IMEI check query in the SGSN. With this feature, the SGSN can send the
subscriber's identity (IMSI or alternatively IMSI and MSISDN) in the MAP Check IMEI
request message to the terminal management system. The terminal management system
automatically delivers operator settings to the subscriber’s mobile stations when it
detects the change of a mobile station.
Table 71: Terminal management support (Features SG02203, f52040-01): feature summary
Function Impact

SGSN User Guide
Function Impact
Compliance This feature is not compliant with 3GPP 29.002: the IMSI and MSISDN in
the MAP Check IMEI request message is not standardized. Additionally,
the origin and destination reference elds are not allowed for a MAP
Check IMEI request message. Including IMSI or alternatively IMSI and
MSISDN parameters in a MAP Check IMEI message requires an EIR or a
terminal management system that supports this capability.
Implementation of extra parameters in a MAP Check IMEI request
message is EIR vendor specic and implementation of different EIR
vendors are usually incompatible. The Automatic Device Detection
functionality is compliant with the 3GPP specications.
Capacity None
Interworking/dependent • Enable faulty IMEISV UE (Feature SG01171)

features • IMEI check with EIR (Feature SG01106)
Restrictions If subscriber data does not exist in the SGSN subscriber database
when the IMEI check is done for the subscriber, the MSISDN is not yet
available in the SGSN and cannot be included in the MAP Check IMEI
request message. This occurs when new a subscriber arrives at an
SGSN, that is, makes an attach or makes an inter-SGSN routing area
update. In such cases, the MAP Check IMEI request message with the
subscriber’s identity (IMSI and MSISDN) is sent to the EIR after the
location update procedure receives the MSISDN from the HLR.
Conguration Command features, parameters: termManagSupp,

impImeiChk
Command prFile, parameter checkImeiMode
Command system, parameters: eir, npForEir, tonForEir
Command plmnParam, parameters: gbGprsAttImei,
gbImsiAttImei , gbNormRaImeiVisitor, gbNormRaImei,
gbPeriodicRaImei, gbMoPdpActImei , gbMoPdpDeaImei,
gbMoGprsDeaImei, iuGprsAttImei, iuImsiAttImei ,
iuNormRaImeiVisitor, iuNormRaImei,
iuPeriodicRaImei, iuMoPdpActImei, iuMoPdpDeaImei,
iuMoGprsDeaImei, iuServReqImei, gprsAttImeiChk,
normalRauImeiChk, normalRauImeiChkVisitor,
pdpActImeiChk, pdpDeactImeiChk, detachImeiChk,
serviceReqImeiChk
Command securityParam, parameter: imeiCheckMode,
imeiRequestMode
Counters None
Alarms 2562 NumberNotFoundFromHrnfilOrInvalidData

SGSN User Guide
4.6.1 Configuring terminal provisioning for GPRS

subscribers using enhanced IMEI query
This procedure includes steps to activate the terminal management support feature and
configure terminal provisioning for GPRS subscribers using enhance.
Procedure
cmm features modify termManagSupp --status true
2 Ensure that the feature is active.
cmm features list |grep termManagSupp

Step result
The following part of the output indicates that the feature is active:
cmm system modify --eir <> --npForEir E164 --tonForEir INT config
3 Choose the IMEI check mode.
SGSN will include IEs according to the setting of prFile parameter checkImeiMode:
0 SGSN includes only IMEI in IMEI Check (default)
1 SGSN adds IMSI in MAP part of IMEI Check
2 SGSN adds IMSI and MSISDN in TCAP part of IMEI Check
Step example
cmm prFile modify checkImeiMode --checkImeiMode 2
4 Create EIR address.
cmm system modify --eir <> --npForEir E164 --tonForEir INT config
5 Set IMEI check repetition rates.
5.1 Set IMEI check repetition rate to 1 for GPRS attach procedure for Gb

SGSN User Guide
connection.
cmm plmnParam modify PLMN -- gbGprsAttImei 1
5.2 If UTRAN is used, set IMEI check repetition rate to 1 for GPRS attach procedure
for Iu connection.
cmm plmnParam modify PLMN –iuGprsAttImei 1
6 Enable the IMEI status check from the EIR for GPRS attach.
cmm plmnParam modify PLMN –gprsAttImeiChk true
7 Enable the IMEI check.
8 Enable the Automatic Device Detection feature.
cmm features modify addSupport – status true
4.7 MultiSIM (Feature SG01063): feature summary

The MultiSIM feature allows one subscriber to use different mobile stations (MSs), each
one with its own SIM card, under the same subscriber international ISDN number
(MSISDN).

SGSN User Guide
Table 72: MultiSIM (Feature SG01063): feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent Lawful interception (Features SG01064, SG01152 and f60210-14).

features
Restrictions Lawful Interception functions for MultiSIM only if interception is

activated before users with same MSISDN attach.
Conguration management Command cmm features modify multiSim --status

true
Counters None
Alarms None
Feature ID SG01063

SGSN User Guide
5. Gateway selection and APN control
5.1 Intelligent GGSN selection (Features SG01116,

SG01212, SG01218, SG01255, SG01234, SG01260 and
This feature enables the operator to perform intelligent GGSN selection by defining an
APN list. For those APNs, the SGSN performs a dynamic GGSN selection which has
multiple triggers that can be activated simultaneously.
Table 73: Intelligent GGSN selection (Features SG01116, G01212, SG01218, SG01255,
SG01234, SG01260 and SG03067): feature summary
Function Impact
Compliance The feature is Nokia proprietary.
Capacity None
Interworking/dependent Direct tunnel (SG02017)

features Release 8 architecture (SG01235)
Restrictions See Intelligent GGSN selection main restrictions in SGSN

Feature Overview

SGSN User Guide
Function Impact
Conguration management Command features, parameters

• homeGgsnSolution
• imsiBasedHomeGgsnS
• nearestGgsn
• ccGgsn
• ggsnImei
• intGwSelRoamSubs
• ueCapBasedGwSel
Command prFile, parameters
• overrideWithModApn
• supportEpcCapability
• dnsFallbackEnabled
• pdpAddrTypeTag
Command system modify, parameters
• msisdnSubPos
• msisdnSubLen
• imsiStartDigit
• imsiEndDigit
• rncIdDigits
• pgwtag
• ipv4Tag
Command apnList create, parameter apn
Command apnList modify, parametershomeGgsn,
oneGtpTunnel
Command imeiAnalysis create, parameter ggsnTag
Counters None
Alarms None
Feature ID • Home GGSN selection and IMSI based home GGSN selection
(Feature SG01116)
• Nearest GGSN selection (Feature SG01212)
• GGSN selection based on charging characteristics (Feature
SG01218)
• UE capability based GW selection and intelligent gateway
selection for roaming subscribers (Feature SG01234)
• IMEI based GGSN selection (Feature SG03067)
• SGSN intelligent GGSN/P-GW selection based on requested PDP
type (Feature SG01260)
Related references

SGSN User Guide
5.1.1 Configuring intelligent GGSN selection

The Intelligent GGSN selection features can be activated separately or simultaneously.
Before you start
If all features are activated, the order of the entered values in the domain name server DNS
query is:
1. IMSI based home GGSN selection value
Note:
The home GGSN selection value will not be visible as the IMSI based home GGSN
selection value will override the MSISDN based home GGSN selection value.
2. Nearest GGSN selection value

3. GGSN selection based on charging characteristics value
4. IMEI based GGSN selection
5. UE capability based GW selection
6. Intelligent gateway selection for roaming subscribers
7. SGSN intelligent GGSN/P-GW selection based on requested PDP type
For example, “internet.MSISDN.RNC-ID.CCV.TAG.mnc.mcc.gprs“ where TAG is a text string

which identifies the mobile device type returned as a result of the IMEI analysis. If the IMEI
analysis does not return any TAG and SGSN enhanced GW selection feature is activated, the
TAG would contain “LTE”. SGSN selects GGSN/P-GW based on requested PDP type (IPv4,
IPv6, IPv4v6). This is achieved by inserting a PDP type tag (the strings used are configurable)
into the APN DNS query. The R7/R8 DNS APN FQDN is modified and the selected PDP/PDN
type corresponding to configurable strings is inserted in the APN DNS query. There are 3
configurable strings, one for each PDP type. For example, for R8 DNS APN query:
"apnx.ipv4.apn.epc.mncxxx.mccyyy.3gppnetwork.org" and for R7 DNS APN
query:"apnx.ipv4.mncxxx.mccyyy.gprs".
The same APNs that are used by the Intelligent GGSN selection feature have to be
configured to the DNS. To use these features, the operator defines an APN list, and for
those APNs the intelligent GGSN selection can be used. In the PDP context activation, the
SGSN can modify the APN if it was found from the list. The modified APN is used in the DNS
query where the DNS resolves a GGSN IP address (P-GW IP address if UE capability based GW
selection feature is active) for the subscriber. The APN can also be overridden with the
modified APN. The SGSN then creates the PDP context towards this GGSN and sends the

SGSN User Guide
modified APN in the creation command if the APN is overridden. The PDP type tag will be
applied as the last tag before the APN-OI field when there are other intelligent GGSN/P-GW
selection features used simultaneously.
Procedure
1 Activate intelligent GGSN selection features.
Table 74: Intelligent GGSN selection activation parameters
Feature Parameter
Home GGSN selection homeGgsnSolution
IMSI based home GGSN selection imsiBasedHomeGgsnS
Nearest GGSN selection nearestGgsn
GGSN selection based on charging ccGgsn

characteristics
IMEI based GGSN selection ggsnImei
UE capability based GW selection and intGwSelRoamSubs

intelligent gateway selection for roaming
subscribers
UE capability based GW selection ueCapBasedGwSel
Step example
cmm features modify homeGgsnSolution --status true
2 Configure the selective APN, by adding APN(s) to the selective APN list.
To create an APN list: cmm apnList create <apnList number> --apn <APN> -
-<use value> true, where allowed use values are:
homeGgsn (HGGSN; intelligent GGSN selection)
oneGtpTunnel (direct tunnel)
Note:
If APN conversion and correction (Feature SG02215) is activated, the converted

new APN must be entered in the APN list of the HGGSN.

SGSN User Guide
Step example
cmm apnList create 1 --apn exampleAPN --homeGgsn true
+---------------+------------+
| Field | Value |
+---------------+------------+
| apnList | 1 |
| prepaid | false |
| homeGgsn | true |
| oneGtpTunnel | false |
| arp | false |
| pgw | false |
| sgw | false |
| homePgw | false |
| allowedApn | false |
| apnConversion | false |
| lteVoice | false |
| lteData | false |
| capa | false |
| vulne | false |
| que | false |
| msisdnPgw | false |
| apn | exampleAPN |
+---------------+------------+
3 Activate APN override with the modified APN.
cmm prFile modify overrideWithModApn --overrideWithModApn

<parameter value>
The prFile parameter overrideWithModApn controls whether the APN is overridden

with the modified APN. The modified APN is the same APN as is used for dynamic GGSN
selection in the DNS query. In the GGSN selection based on charging characteristics
(SG01218) feature this parameter also controls whether subscribed charging
characteristics (CC) is required for dynamic GGSN selection (DNS query) and APN
override. Values are
0 = APN override is not used.
1 = APN override is used.
10 = APN override is not used. In feature SG01218 the dynamic GGSN selection is
allowed only if the subscribed CC exists.

SGSN User Guide
11 = APN override is used. In feature SG01218 the dynamic GGSN selection and the
APN override are allowed only if the subscribed CC exists.
4 Configure the IMEI analysis for the IMEI based GGSN selection.
Create an IMEI analysis (one per mobile device type) to specify devices to be directed to
dedicated GGSNs.
cmm imeiAnalysis create <IMEI number> --ggsnTag < TAG >
Note:
In case of the IMEI based GGSN selection feature, the possible value of the IMEI
parameter is a 14 digit IMEI number.
5 Activate SGSN intelligent GGSN/P-GW selection based on requested PDP type.
cmm prFile modify pdpAddrTypeTag --status true
The SGSN intelligent GGSN/P-GW selection based on requested PDP type feature
will be offered for home users during PDP context activation whenprFile
parameter pdpAddrTypeTag is enabled. This parameter controls the enabling
of the new IPv4tag, IPv6tag and IPv4v6tag attributes in the system cmm
command. Values are:
false = The tag is not included in the query.
Note:
If value is set to false, IPv4, IPv6 and IPv4v6 tag options are not
visible.
true = The tag is included in the query.
5.2 Configure any of the PDP type tags to specify devices to be directed to
dedicated GGSNs.

SGSN User Guide
cmm system modify config --ipv4Tag < TAG >
cmm system modify config –-ipv6Tag < TAG >
cmm system modify config --ipv4v6Tag < TAG >
Note:
PDP activations where UE requests dual stack PDP type and subscription is
with single PDP type (IPv4 and IPv6, no IPv4v6) will not utilize the IPv4v6
tagging.
Example: Home GGSN solution based on MSISDN

You need to define the MSISDN subrange (3 to 5 digits) and configure the APN to the DNS,
including the selected subrange.
Example values:
MSIDSN = 358507777001
APN = bssemu1.bb1.gtest.net.mnc005.mcc244.gprs
APN that is configured to DNS = bssemu1.bb1.gtest.net.85077.mnc005.mcc244.gprs
1. Activate the Home GGSN selection feature: cmm features modify

homeGgsnSolution --status true
2. Deactivate the IMSI based home GGSN selection feature: cmm features modify
imsiBasedHomeGgsnS --status false
3. Define the sub-range of MSISDN: cmm system modify config --msisdnSubPos 3
--msisdnSubLen 5 where
msisdnSubPos is <starting_position>
msisdnSubLen is <length>
4. Create an APN list and add a configured APN on the list: cmm apnList create <
apnList number > --apn < APN >
Example: IMSI based home GGSN selection

Example values:
IMSI = 234450123456789

SGSN User Guide
1. Activate the Home GGSN selection feature: cmm features modify

homeGgsnSolution --status true
2. Configure the IMSI range: cmm system modify config --imsiStartDigit 6 --
imsiEndDigit 10
3. Configure the APN to the DNS.
Example: Nearest GGSN selection

You need to configure the APN to the DNS. Include the same number of digits from the
RNCID number than configured with the RNCD parameter:
Example values:
RNCID = 9634
1. Add the APN to the selective APN list by adding APN to the DNS: cmm apnList create
<apnList number> --apn <APN> --<use value> true where the allowed use
values are homeGgsn and oneGtpTunnel.
2. Configure the number of RNCID digits used in the DNS query for the Nearest GGSN
selection feature: cmm system modify config --rncIdDigits <DIGITS> where
DIGITS defines the number of RNC ID digits used in the DNS query. Possible values are 1 -
5 and default value is 2.
3. Activate direct tunnel:
a. Configure direct tunnel for PLMN: cmm plmn modify ETPLMN --directTunnelOn
Yes
b. Configure RNC support for direct tunnel parameter in the SGSN: cmm rncParamSet
modify 1 --rncSupportForDirectTunnel true
c. Activate the feature: cmm features modify directTunnelLicence --status
true
Example: GGSN selection based on charging characteristics

You need to configure the APN to the DNS. Include the charging characteristics from the
subscriber's CC value.
Example values:
CC = <charging char>, for example:
1000 normal
0100 prepaid
0010 flat rate

SGSN User Guide
0001 hot billing

APN that is configured to DNS = bssemu1.bb1.gtest.net.<charging
char>.mnc005.mcc244.gprs
1. Add the APN to the selective APN list by adding APN to the DNS: cmm apnList create
<apnList number> --apn <APN> --<use value> true where the allowed use
value is homeGgsn.
2. If feature SG01255 is needed, set prFile parameter twoByteChargingChar to two
byte CC: cmm prFile modify twoByteChargingChar --status false --
twoByteChargingChar
Example: IMEI based GGSN selection

You need to add the MS IMEI to the IMEI analysis and configure the APN to the DNS including
the IMEI tag defined for the IMEI analysis result.
Example values:
TAG = NOKN97
APN that is configured to DNS =bssemu1.bb1.gtest.net.NOKN97.mnc005.mcc244.gprs
1. Activate the IMEI check for an GPRS attach:

cmm plmnParam modify EPLMN --gbGprsAttImei 1
2. Create an APN list and add a configured APN on the list: cmm apnList create <
apnList number > --apn <APN>
3. Add the MS IMEI to the IMEI analysis: cmm imeiAnalysis create <IMEI number> -
-ggsnTag <TAG>
Example: UE capability based GW selection for home subscribers and

intelligent gateway selection for roaming subscribers
You need to configure the APN to the DNS including the SGSN configured TAG (it should
consist of alphanumeric characters, either uppercase or lowercase and length should be up
to 10 characters) or the hardcoded value 'LTE' tag.
Example values:
APN that is configured to DNS =
bssemu1.bb1.gtest.net.TAG.mnc005.mcc244.gprsbssemu1.bb1.gtest.net.LTE.mnc005.m

SGSN User Guide
cc244.gprs
Note:
The feature UE capability based GW selection enables gateway selection for home
subscribers and the feature Intelligent gateway selection for roaming subscribers
enables UE gateway selection for EPC capable roamers. The feature Intelligent gateway
selection for roaming subscribers works independently, there is no inter-dependency
of this feature with any of the GGSN selection features.
Note:
If IMEI based GGSN selection and UE capability based GW selection for home
subscribers are true, the LTE tag is not triggered in DNS query.
1. Activate S-GW/P-GW connectivity for EPC capable mobiles: cmm prFile modify
upportEpcCapability --status true
2. Scenario 1:
a. Activate feature R8 architecture (SG01235): cmm gParms modify --gParmName
s4Func --gParmValue ON
b. S interfaces should not be configured.
c. Configure PGW TAG: cmm system modify config -–pgwtag <TAG>
Default value is 'LTE'.TAG should consist of alphanumeric characters, either uppercase
or lowercase and length should be up to 10 characters.
3. Scenario 2:
a. Deactivate feature R8 architecture (SG01235): cmm gParms modify --gParmName
s4Func --gParmValue OFF
4. Create an APN list and add a configured APN on the list: cmm apnList create
<apnList number> --apn <APN> --homeGgsn <true>
Example: SGSN intelligent GGSN/PGW selection based on requested PDP

type
You need to configure the APN to the DNS. Include the requested PDP type tag. The default
PDP type tag is 0.
Example values:
TAG = IPV4

SGSN User Guide
APN that is configured to DNS = bssemu1.bb1.gtest.net. IPV4.mnc005.mcc244.gprs
1. Enable the SGSN intelligent GGSN/PGW selection based on requested PDP type feature:
cmm prFile modify pdpAddrTypeTag --status true
2. Define, for example, the IPv4 PDP type tag: cmm system modify config --ipv4Tag
IPV4
5.2 Override of requested APN in SGSN (Features

SG01074 and f52032-01): feature summary
This feature increases the rate of successful packet data protocol (PDP) context
activations in SGSN, since a default APN can be used when activating a PDP context if the
requested APN is invalid or empty.
Table 75: Override of requested APN in SGSN (Features SG01074 and f52032-01): feature
summary
Function Impact
Capacity None
Interworking/dependent • IMEI based APN override (Feature SG02019)

features • APN conversion and correction (Feature SG02215)
Restrictions If both Override of requested APN in SGSN (Feature SG01074) and IMEI
based APN override (Feature SG02019) are enabled, the functionality of
the IMEI-based APN feature has priority.

SGSN User Guide
Function Impact
Conguration Command feature, parameter sg01074OverReqApn

management Command prfile, parameters
• overrideRoamingApn
• enforceSubscribedApn
• apnWithLowestPdpId
Command gParms, parameter overrideVaa
Command sgsnLocalEndPtCfg, parameter group GNSGSN,
parameters:
• gni
• gni6
• gniv4v6, visible only if dualStackPdpCtxt is set to true
• GOI
• secgni
• secgni6
• secgniv4v6, visible only if dualStackPdpCtxt is set to true
Command plmnParam, parameter defaultApnOi
Command imeiAnalysis
Counters None
Alarms None
5.2.1 Configuring override of requested APN

In addition to activating the feature, you must also specify the default and secondary
SGSN APNs. Optionally, you can enable the override for roaming subscribers,
enforcement of the subscribed APN, or APN selection for the lowest PDP ID.
Procedure
cmm features modify sg01074OverReqApn --status true

Step result
The following part of the command output indicates that the feature is enabled:

SGSN User Guide
+-----------+--------------------------------+
| Field | Value |
+-----------+--------------------------------+
| features | sg01074OverReqApn |
| status | true |
| parameter | SGSN Override of requested APN |
+-----------+--------------------------------+
2 Activate the override for roaming subscribers parameter, if needed.
cmm prFile modify overrideRoamingApn --status true

Step result
The following part of the command output indicates that the parameter is enabled:
+-----------+--------------------------------+
| Field | Value |
+-----------+--------------------------------+
| features | sg01074OverReqApn |
| status | true |
| parameter | SGSN Override of requested APN |
+-----------+--------------------------------+
3 Activate the enforce subscribed APN parameter, if needed.
cmm prFile modify enforceSubscribedApn --status true

Step result
+-----------+------------------------+
| Field | Value |
+-----------+------------------------+
| prFile | enforceSubscribedApn |
| status | true |
| parameter | ENFORCE_SUBSCRIBED_APN |
+-----------+------------------------+
4 Activate the override Vaa global parameter.
cmm gParms modify --gParmName overrideVaa --gParmValue ON

SGSN User Guide
Note:
This step is performed in order to dissociate the Override of requested APN

feature's functionality from the VAA parameter value and it is applicable for
roaming subscribers only.
5 Activate the enforcing subscribed APN parameter, if needed.
cmm prFile modify apnWithLowestPdpId --status true

Step result
+-----------+-----------------------------------------------------+
| Field | Value |
+-----------+-----------------------------------------------------+
| prFile | apnWithLowestPdpId |
| status | true |
| parameter | Select APN with lowest PDP id from HLR subscription |
+-----------+-----------------------------------------------------+
6 Define the default SGSN APN parameters.
cmm sgsnLocalEndPtCfg modify <parameter_group> --<parameter_name>

<parameter_value>
parameter_group Specify GNSGSN.
parameter_name • gni - GGSN IPv4 network identier

• gni6 - GGSN IPv6 network identier
• gniv4v6 - GGSN IPv4v6 network identier (is visible only when
dualStackPdpCtxt is set to True
• GOI - GGSN operator identier
Step example
The following example sets the GGSN IPv6 network identifier to ggsn1.ipv6.net.
cmm sgsnLocalEndPtCfg modify GNSGSN –-gni6 ggsn1.ipv6.net

SGSN User Guide
7 Define the secondary default SGSN APN parameters.

<parameter_value>
parameter_group Specify GNSGSN.
parameter_name • secgni - secondary GGSN IPv4 network identier

• secgni6 - secondary GGSN IPv6 network identier
• secgniv4v6 - secondary GGSN IPv4v6 network identier (visible
only when dualStackPdpCtxt is set to True).
Step example
The following example sets the secondary GGSN IPv6 network identifier to ggsn1.ipv6.
cmm sgsnLocalEndPtCfg modify GNSGSN –-secgni6 ggsn1.ipv6.net
8 Modify the PLMN-specific DEFAPN parameter.
cmm plmnParam modify <PLMN_name> --<PLMN_parameter> <PLMN_value>
PLMN_name name of the PLMN.
PLMN_parameter the default APN OI.
Step example
The following example sets the default APN parameter of the ETPLMN to
ggsn1.nokia.gprs.
cmm plmnParam modify ETPLMN --defaultApnOi ggsn1.nokia.gprs
5.3 IMEI-based APN override (Feature SG02019): feature

summary
This feature allows the operator to use a default SGSN APN in cases where the requested

SGSN User Guide
APN is not found from the HLR/HSS subscription record, instead of using the APN
according to the first HLR/HSS subscription record. This is useful when the PDP contexts
may exist in the HLR/HSS subscription in random order and the 'wild card' (*) cannot be
used in the HLR/HSS subscription.
Table 76: IMEI-based APN override (Feature SG02019): feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent features • Override of requested APN in SGSN (Feature SG01074)

• APN conversion and correction (Feature SG02215)
Restrictions There can be a maximum of 1000 different IMEIs dened in

the IMEI analysis.
Conguration management Command features, parameter sg02019OverReqApn

Command prfile, parameter overrideRoamingApn
Command sgsnLocalEndPtCfg, parameters GNSGSN,
gni, gni6, gniv4v6, GOI, secgni, secgni6, and
secgniv4v6
Note: gniv4v6 and secgniv4v6 are visible only when
dualStackPdpCtxt is True.
Command plmnParam, parameters defaultApnOi,
gbGprsAttImei, iuGprsAttImei, gbCombAttImei,
iuCombAttImei, gbNormRaImeiVisitor,
andiuNormRaImeiVisitor
Command imeiAnalysis
Counters None
Alarms None
Feature ID SG02019
5.3.1 Configuring IMEI-based APN override

This procedure includes steps for configuring IMEI-based APN override and examples of
SGSN APN configuration.

SGSN User Guide
Before you start
Configure the default APN. The default SGSN APN is used to override an incorrect APN when
the MS IMEI is not in the IMEI analysis.
If the subscriber does not have a wild card (*) subscription in the HLR, the Secondary GGSN
Network Identifier parameter (secgni) is used to define which QoS profile is used in the PDP
context activation, that is, if the secondary GNI is found from the HLR profile, the QoS
profile of that PDP context is used.
It is recommended that the following parameters are set to value 1 in the PLMN parameters
(if visible):
IMEI check repetition rate for GPRS attach gbGprsAttImei/iuGprsAttImei
IMEI check repetition rate for combined IMSI and GPRS attach
gbCombAttImei/iuCombAttImei
IMEI check repetition rate for normal RA update, new visitor
gbNormRaImeiVisitor/iuNormRaImeiVisitor
This ensures that the subscriber’s IMEI is available when the subscriber enters the SGSN and
the feature can be used for this IMEI.
Procedure
1 Activate the IMEI-based APN override feature.
cmm features modify sg02019OverReqApn --status true
2 Activate the override for roaming subscribers' parameter (optional).
cmm prFile modify overrideRoamingApn --status true
3 Define the default SGSN APN parameters.

<parameter_value>
The available parameter group is GNSGSN.
The available parameter values are listed:
gni GGSN IPv4 network identier
gni6 GGSN IPv6 network identier

SGSN User Guide
gniv4v6 GGSN IPv4v6 network identier
GOI GGSN operator identier
Step example
Modify the GGSN IPv6 network identifier to ggsn1.ipv6.net.
cmm sgsnLocalEndPtCfg modify GNSGSN –-gni6 ggsn1.ipv6.net
4 Define the secondary default SGSN APN parameters.

<parameter_value>
The available parameter group is GNSGSN.
The available parameter values are listed:
secgni secondary GGSN IPv4 network identier
secgni6 secondary GGSN IPv6 network identier
secgniv4v6 secondary GGSN IPv4v6 network identier
Step example
Modify the secondary GGSN IPv6 network identifier to ggsn1.ipv6.net.
cmm sgsnLocalEndPtCfg modify GNSGSN –-secgni6 ggsn1.ipv6.net
5 Modify the PLMN-specific DEFAPN parameter.
cmm plmnParam modify <PLMN_name> --<PLMN_parameter> <PLMN_value>

The available PLMN parameter value is defaultApnOi.

SGSN User Guide
Step example
Modify the DEFAPN parameter of the ETPLMN to ggsn1.nokia.gprs.
cmm plmnParam modify ETPLMN --defaultApnOi ggsn1.nokia.gprs
6 Create an IMEI analysis table, specifying devices that are not overridden by the IMEI
based APN override feature.
cmm imeiAnalysis create <IMEI_value> --apno true
Step example
cmm imeiAnalysis create 12345678 --apno true
5.4 APN conversion and correction (Feature SG02215):

feature summary
This feature enables the SGSN to implement more enhanced APN selection, by converting
the APN requested by the end user during a mobile originated PDP context activation
procedure to be the operator defined APN that is used in the network, before sending the
request to the DNS and GGSN.

SGSN User Guide
Table 77: APN conversion and correction (Feature SG02215): feature summary
Function Impact
Capacity None
Interworking/dependent • Override of requested APN in SGSN (Feature SG01074)

features • IMEI-based APN override (Feature SG02019)
• Subscriber authentication (Feature SG01011)
• GPRS session management (Features SG01012, SG01068 and
SG02157)
Restriction
Conguration management Command features, parameter apnConv

Command apnList, apnConversion and plmnParam
Charging None
Counters • M002C171 / MO PDP CONTEXT ACTIVATION WHERE APN

RECEIVED FROM UE
• M002C172 / SUCCESSFUL MO PDP CONTEXT ACTIVATION
WHERE APN REPLACED BY OPERATOR DEFINED APN
• M017C151 / IU MO PDP CONTEXT ACTIVATION WHERE APN
RECEIVED FROM UE
• M017C152 / IU SUCCESSFUL MO PDP CONTEXT ACTIVATION
WHERE APN REPLACED BY OPERATOR DEFINED APN
Alarms None
Feature ID SG02215
5.5 SGSN Gn local break out control (Feature SG01258):

feature summary
This feature introduces a local breakout (LBO) mechanism to roaming functionality
towards GGSN.

SGSN User Guide
Table 78: SGSN Gn local break out control (Feature SG01258): feature summary
Function Impact
Compliance • 3GPP TS 23.060 version 9.7.0 Release 9

• 3GPP TS 23.401 version 9.7.0 Release 9
• 3GPP TS 29.002 version 9.4.0 Release 9
Capacity None
features
Restrictions If both 3GPP R8 DNS query support for Gn SGSN and SGSN Gn LBO
control are enabled in the same GN SGSN, then the congured
roaming policy will not be applied.
Conguration Command plmnParam, parameter roamingControl

management Command prFile, parameter lboAllowedGnSgsn
Counters None
Alarms None
Feature ID SG01258
5.5.1 Configuring SGSN Gn local break out control

The procedure includes steps to active the SGSN Gn local break out control feature and
set related roaming control parameters for a particular VPLMN.
Procedure
1 Activate SGSN Gn local break out control.
cmm prFile modify lboAllowedGnSgsn --status true
2 Set a roaming control parameter for a particular VPLMN.
cmm plmnParam modify --plmnParamId VPLMN –roamingControl

{LBO,HRT,BOTH,NOT}
The parameter values for roaming control are listed here:
LBO Only local breakout is allowed and not home-routed traffic.

SGSN User Guide
HRT Only home-routed traffic is allowed. This is the default value.
BOTH Local breakout and home-routed traffic is allowed. In this case,

priority is given to local breakout. This means that Gn SGSN will
perform local breakout rst, and if it fails, then it will use home-
routed traffic.
NOT PDP creation is not allowed.
5.6 SGSN support for local break out for S4-SGSN

This feature introduces a local breakout (LBO) mechanism to roaming functionality
towards SGW/PGW. With this feature, the operator can apply local policy based on inter-
operator agreements for each roaming partner.

SGSN User Guide
Table 79: SGSN support for local break out for S4-SGSN: feature summary
Function Impact
Compliance • 3GPP TS 23.060 3rd Generation Partnership Project;Technical

Specication Group Services and System Aspects; General Packet Radio
Service (GPRS); Service description;Stage 2
• 3GPP TS 29.002 MAP – Mobile Application Part
• 3GPP TS 29.274 Tunnelling Protocol for Control plane (GTPv2-C)
Capacity • Up to 300 allowed APN lists are supported.

• Each allowed APN list consists of up to 10 APNs.
Required features SGSN Gn local break out control (Feature SG01258): Once the S4
LBO is enabled, the assumption is that the Gn LBO is also enabled for
fallback case.
Interworking/dependent • PLMN level control of S6d/Gr selection (Feature f51026-01)

features • PLMN level control of preferred gateway type (S-GW/P-GW or
GGSN) (Feature f51019-01)
Restrictions • S5 and S8 interfaces should be congured and this should be

depicted also in DNS conguration les. This action is needed to avoid
activation issues in case of a single UE attempting to establish multiple
PDNs where some are treated as LBO and some as HRT.
• Service eld format x-3gpp-sgw:x-s5-gtp:x-s4 or x-3gpp-sgw:x-s8-
gtp:x-s4 should be used in S-GW resolution for RAI queries.
Conguration Command gParms, parameter s4SgsnLbo

management Command plmnParam, parameters s4SgsnRoamingControl
and sgsnLboAllowedApnListName
Commands sgsnLboAllowedApn and
sgsnLboAllowedApnList
Counters None
Alarms None
5.6.1 Configuring the S4-SGSN local break out control

feature
The procedure includes steps to activate the S4-SGSN local break out control feature and
set the related roaming control parameters for a particular VPLMN.

SGSN User Guide
Procedure
1 Activate the S4-SGSN local break out control feature.
cmm gParms modify --gParmName s4SgsnLbo --gParmValue Yes
2 Set the S4 roaming control parameter for a particular VPLMN.
Step example
cmm plmnParam modify --plmnParamId ROAMINGPLMN --
s4SgsnRoamingControl LBO
The parameter values for roaming control are listed here:
LBO Only local breakout is allowed and not home-routed traffic.
HRT Only home-routed traffic is allowed. This is the default value.
BOTH Local breakout and home-routed traffic is allowed. In this case,

priority is given to local breakout. This means that Gn SGSN will
perform local breakout rst, and if it fails, then it will use home-
routed traffic.
NOT PDN creation is not allowed.
3 Create an LBO allowed APN list.
Step example
cmm sgsnLboAllowedApnList create --name lbolist
4 Create the allowed APNs under the LBO list.
Step example
cmm sgsnLboAllowedApn create --sgsnLboAllowedApnListName lbolist
--apnNi wap1.nokia.com
Step example
cmm sgsnLboAllowedApn create --sgsnLboAllowedApnListName lbolist
5 Connect an allowed APN list with the roaming PLMN.

SGSN User Guide
Step example
cmm plmnParam modify --sgsnLboAllowedApnListName lbolist
ROAMINGPLMN
5.6.2 Removing the S4-SGSN local break out control

feature
The procedure includes steps to remove the S4-SGSN local break out control feature and
unset the related roaming control parameters for a particular VPLMN.
Procedure
1 Remove an allowed APN list from the roaming PLMN.
Step example
cmm plmnParam modify ROAMINGPLMN --sgsnLboAllowedApnListName ""
2 Delete the allowed APNs from the LBO list.
Step example
cmm sgsnLboAllowedApn delete --sgsnLboAllowedApnListName lbolist
Step example
cmm sgsnLboAllowedApn delete --sgsnLboAllowedApnListName lbolist
3 Delete the LBO allowed APN list.
Step example
cmm sgsnLboAllowedApnList delete --name lbolist
4 Set the S4 roaming control parameter for a particular VPLMN to the default value.
Step example
cmm plmnParam modify --plmnParamId ROAMINGPLMN --
s4SgsnRoamingControl HRT
5 Deactivate the S4-SGSN local break out control feature.

SGSN User Guide
Step example
cmm gParms modify --gParmName s4SgsnLbo --gParmValue No
5.7 R8 DNS query support for Gn-SGSN (Features

SG02213, f52058-01): feature summary
This feature provides R8 NAPTR DNS query support on a Gn-SGSN configuration for
retrieving the Gn/Gp interface of the P-GW, during a PDP context activation of EPC-
capable home and roaming subscribers. Gn-SGSN R8 NAPTR DNS query functionality also
resolves IPv6 addresses.
Table 80: R8 DNS query support for Gn-SGSN (Features SG02213, f52058-01): feature
summary
Function Impact
Capacity None
Restrictions None

r8DnsForR7EpcSubs
Command prFile, parameters
• r8DnsR7EpcSubs
• dnsFallbackEnabled
Command gParms, parameters
• ipv6SelectionAllowedOnGn
• prefGnToGGSNIpVer
Counters None
Alarms None

SGSN User Guide
5.7.1 Enabling R8 DNS query support for Gn-SGSN

To enable the R8 DNS query support for Gn-SGSN feature, use the r8DnsForR7EpcSubs
parameter.
Before you start
Before enabling the feature, ensure that the UE is EPC-capable.
Procedure
cmm features modify r8DnsForR7EpcSubs --status true
2 Set a value for R8 DNS EPC subscriber.
The r8DnsR7EpcSubs parameter is common for IPv4 and IPv6.
1 roaming subscribers
2 home subscribers
3 both home and roaming subscribers
Step example
cmm prFile modify r8DnsR7EpcSubs --r8DnsR7EpcSubs 1
3 Check whether a DNS query gets fallback to Pre-release 8.
cmm prFile modify --status true dnsFallbackEnabled

To enable fallback:
cmm prFile modify dnsFallbackEnabled --status true
4 Allow IPv6 selection on Gn-C.
AAAA DNS queries are allowed only when ipv6SelectionAllowedOnGn is set to ON.
cmm gParms modify --gParmName ipv6SelectionAllowedOnGn --

gParmValue ON
5 Configure IP address version preference for transport layer.

SGSN User Guide
Step example
cmm gParms modify --gParmName prefGnToGGSNIpVer --gParmValue IPV6
5.8 Gn SGSN P-GW selection based on MSISDN range with

rel8 DNS (Feature f10110-03): feature summary
This feature provides R8 NAPTR DNS query support on a Gn-SGSN configuration for
retrieving the Gn/Gp interface of the P-GW: during a PDP context activation SGSN can
include additional digits from the home subscriber MSISDN number to the R8 Domain
Name Server (DNS) APN query so that DNS can return different P-GW IP addresses for
different subscribers.
Table 81: Gn SGSN P-GW selection based on MSISDN range with rel8 DNS (Feature
Function Impact
Capacity None
Interworking/dependent R8 DNS query support for Gn-SGSN (Feature SG02213)

features
Restrictions The following features should not have any affect when this feature is
activated:
• UE capability based GW selection and intelligent gateway selection for
roaming subscribers (Feature SG01234)
• Home GGSN selection (Feature SG01116)
Conguration Command system, parameters msisdnSubPos, msisdnSubLen

management Command features, parameter msisdnBasedPgwSel
Command prFile, parameter msisdnPgwDnsFallback
Command apnList, parameter msisdnPgw
Counters None
Alarms None

SGSN User Guide
Related references
5.8.1 Configuring Gn SGSN P-GW selection based on

MSISDN range with rel8 DNS
This feature requires activation, fallback functionality provisioning, MSISDN subrange
provisioning, and APN list provisioning.
Procedure
The default status is false. To activate the feature:
cmm features modify msisdnBasedPgwSel --status true
2 Configure fallback functionality of DNS query.
cmm prFile modify msisdnPgwDnsFallback –-msisdnPgwDnsFallback

<value>
Possible values are:
Table 82: Values of msisdnPgwDnsFallback
Value Description
0 (default) SGSN will abort the dialogue without performing any DNS fallback
procedure.
1 SGSN will perform DNS fallback by applying Release 8 DNS procedures

without MSISDN tag in the APN, for the APN lookup.
2 SGSN will perform DNS fallback by applying pre-Release 8 DNS

procedures for the APN lookup.
3 Configure system parameters.
System parameters related to this functionality are:
msisdnSubPos MSISDN subrange starting position for home P-GW selection, value
range 3...7, default 3.

SGSN User Guide
msisdnSubLen MSISDN subrange length for home P-GW selection, value range
3...7, default 7.
3.1 Verify system parameters.
Step example
cmm system show
+------------------------+--------------------+
| Field | Value |
+------------------------+--------------------+
| system | config |
...
| msisdnSubPos | 3 |
| msisdnSubLen | 7 |
+------------------------+--------------------+
3.2 Configure the values.
Step example
cmm system modify config --msisdnSubPos 4 --msisdnSubLen 5
4 Add APN in the APN allowed list for this feature.
Step example
cmm apnList create --msisdnPgw true --allowedApn true DUMMYAPN
This will add APN DUMMYAPN in the allowed APN list (list id 1) for SGSN support for Gn
SGSN P-GW selection based on MSISDN range with rel 8 DNS functionality.
5.9 SGSN support GGSN Load Balancing (Features

This feature allows the operator to configure SGSN network element taking into
consideration the different GGSN capacities in the same Access Point Name (APN) space.

SGSN User Guide
Table 83: SGSN support GGSN Load Balancing (Features f52037-01 and f12101-12): feature
summary
Function Impact
Compliance 3GPP TS 29.060: General Packet Radio Service (GPRS); GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface
Capacity SGSN supports the conguration of maximum 256 entries in host le
(each entry is per APN) and may contain up to 5 different GGSN IPs
with respective weights.
features (Feature f12101-06)
Restrictions None
Conguration Command gparms, parameter ggsnLbMode

management Command ggsnIpsWeight
Counters None
Alarms None
Feature ID f52037-01, f12101-12
5.9.1 Configuring SGSN support GGSN load balancing

The procedure includes steps for enabling GGSN load balancing mode.
Procedure
1 Enable GGSN load balancing mode.
Enable Round Robin GGSN Load Balancing mode
cmm gParms modify ggsnLbMode --gParmValue RRON

Enable DNS GGSN Load Balancing mode
cmm gParms modify ggsnLbMode --gParmValue DNS

Enable host file GGSN Load Balancing mode
cmm gParms modify ggsnLbMode --gParmValue HOST

Possible values of GGSN load balancing mode are:

SGSN User Guide
Table 84: Values of ggsnLbMode
Value Description
RROFF (Default) SGSN will not perform any GGSN load balancing functionality.
RRON SGSN will perform round robin GGSN selection to the IP list
received by DNS. In case, DNS cannot resolve the APN query
(DNS RCODE:3 Domain name does not exist), PDP rejection
(unknown APN case) will occur.
DNS SGSN will perform round robin GGSN selection to IP list received
by DNS. If DNS cannot resolve the APN query (DNS RCODE:3
Domain name does not exist), SGSN will check if this APN can be
found to internal host le. If this can be resolved by the host le,
SGSN will perform weighted GGSN load balancing. Otherwise, this
will lead to PDP rejection (unknown APN case).
HOST SGSN will rst check if APN can be found to internal host le. If
this can be resolved by the host le, SGSN will perform weighted
GGSN load balancing. If not, SGSN will check in internal DNS-
cache and then in actual DNS. In case the DNS query cannot be
resolved to valid GGSN IP (DNS RCODE:3 Domain name does not
exist ), PDP rejection (unknown APN case) will occur.
2 Configure the APN-GGSN list in Host file (not needed for RRON mode).
cmm ggsnIpsWeight create --apnNI <string> --mcc <digits> --mnc

<digits> --ggsnIpAddress <string> --weight <integer>
Configuring IPv4 GGSN IP in host file
Step example
cmm ggsnIpsWeight create --apnNI testapn --mnc 460 --mcc 020 --
ggsnIpAddress 12.36.10.1 --weight 5
Configuring IPv6 GGSN IP in host file
Step example
cmm ggsnIpsWeight create --apnNI apn --mnc 460 --mcc 020 --
ggsnIpAddress 2a00:8a00:6000:4000::a54:19ac --weight 3

SGSN User Guide
Note:
In case there is a need to perform GGSN Load Balancing in Host mode along with
one or more intelligent GGSN selection features, SGSN should be configured
accordingly, meaning that modified APNs should be present in the host file.
5.10 MSISDN number based home GGSN/P-GW selection

enhancement (Feature f10176-01): feature summary
This feature allows selection of home GGSN/P-GW based on MSISDN and introduces a
new list of APNs.

SGSN User Guide
Table 85: MSISDN number based home GGSN/P-GW selection enhancement: feature summary
Function Impact
Compliance None
Capacity None
Required features For the MME, MME support for APN NI Extension with Congurable
Length of MSISDN Digits (m10121-03).
For the SGSN, enable Home GGSN Solution and disable IMSI Based
Home GGSN Selection (SG01116).
features
Restrictions For the MME, this feature applies to Home Subscriber UEs, Local
Breakout (LBO) Roamer UEs and Roamer-Treated-As-Home-Subscriber
UEs. This feature does not apply to Roamer UEs.
For the SGSN, this feature is only relevant to Gn-SGSN and applies only
to Home Subscribers
Conguration For the MME:

management gParms msisdnHomeGwWithCc
Commands hpGwCcApnList, hpGwCcApn and plmn
For the SGSN:
Command features, parameter msisdnBasedGwCc
Commands apnList
Command prFile, parameter twoByteChargingChar
Counters None
Alarms None
Related references
5.10.1 Configuring MSISDN number based home GGSN/P-

GW selection enhancement for the SGSN
Use parameter msisdnBasedGwCc to enable and disable this feature, command apnList
parameter hpGwCc to modify P-GW selection based on charging characteristic and prfile
twoByteChargingChar to define the support for two-byte charging characteristics.

SGSN User Guide
Procedure
1 Activate feature Intelligent GGSN selection (SG01116).
Step example
cmm features modify homeGgsnSolution --status true
cmm features modify imsiBasedHomeGgsnS --status false
2 Define MSISDN range with system parameters.
Step example
cmm system modify config --msisdnSubPos 4 --msisdnSubLen 5
3 Enable MSISDN based GW selection with charging characteristic.
Step example
cmm features modify msisdnBasedGwCc --status true
4 Create home P-GW selection based on charging characteristic.
Step example
cmm apnList create test.apn.com --hpGwCc true
5 Define the support for two-byte charging characteristics value in SGSN received from
HLR.
Step example
cmm prFile modify twoByteChargingChar --status true --
twoByteChargingChar 2
5.11 PLMN level control of preferred gateway type (S-

GW/P-GW or GGSN) (Feature f51019-01): feature
summary
With this feature, the operator can control, at the on PLMN level, whether Rel-8 APN DNS
query for S/P-GW selection or Rel-7 query DNS for GGSN selection is preferred during
PDP context creation.

SGSN User Guide
Table 86: PLMN level control of preferred gateway type (S-GW/P-GW or GGSN): feature
summary
Function Impact
Compliance None
Capacity None
Interworking/dependent SGSN S4 functionality

features
Restrictions None
Conguration Command gParms, parameter plmnCtrlPreferGw. Default value

management is No; Yes is to enable the feature.
Command plmnParam (ETPLMN or ROAMINGPLMN), parameters
ctrlR7R8DnsQuery.
Counters None
Alarms None
5.11.1 Configuring PLMN level control of preferred

gateway
Enable this feature using global parameter plmnCtrlPreferGw. Configure the preferred
option for GGSN/GW selection during PDP context creation per PLMN using the
ctrlR7R8DnsQuery parameter with the plmnParam command.
Procedure
1 Enable PLMN level control of preferred gateway.
Step example
cmm gParms modify --gParmName plmnCtrlPreferGw --gParmValue Yes
2 Configure the prefered option for GGSN/GW selection during PDP context creation
per PLMN.

SGSN User Guide
Step example
cmm plmnParam modify ETPLMN --ctrlR7R8DnsQuery ExistFunc
cmm plmnParam modify ROAMINGPLMN --ctrlR7R8DnsQuery Gn
cmm plmnParam modify ETPLMN --ctrlR7R8DnsQuery S4
5.12 SGSN support for mobility enhancements when

PLMN Level control of preferred gateway type is enabled
This feature enhances the SGSN behavior provided with PLMN level control of preferred
gateway type (S-GW/P-GW or GGSN) (f51019-01) feature. With this feature, when the
IRAT changes take place (from the MME), or when the inter-system mobility takes place
(from the S4-SGSN), the SGSN keeps the same logical as the gateway configuration.
Table 87: SGSN support for mobility enhancements when PLMN Level control of preferred
gateway type is enabled: feature summary
Function Impact
Compliance None
Capacity None
Required features SGSN S4 functionality
Interworking/dependent PLMN level control of preferred gateway type (SGW/

features P-GW or GGSN) (f51019-01)
Restrictions None
Conguration Command gParms, parameter plmnCtrlPreferGw

management
Counters None
Alarms None

SGSN User Guide
5.13 P-GW selection based on charging characteristics for

R8 DNS queries (Feature f51021-01): feature summary
This feature can be used to assign dedicated P-GWs to support different kinds of traffic.
For example, postpaid and prepaid users can be served by different P-GWs. This feature
is enabled only for the home subscribers, and is applicable for both S4-SGSN and Gn-
SGSN that is provisioned to use R8 DNS query support for Gn-SGSN (Features SG02213,
f52058-01).

SGSN User Guide
Table 88: P-GW selection based on charging characteristics for R8 DNS queries: feature
summary
Function Impact
Compliance 3GPP TS 23.003 Maximum length of 63 octets for APN length should
be maintained
Capacity None
Required features R8 DNS query support for Gn-SGSN (Features SG02213,

f52058-01)
Interworking/dependent • Gn SGSN P-GW selection based on MSISDN range with Rel-8 DNS
features (Feature f10110-03)
• Intelligent GGSN selection (Features SG01116, SG01212,
SG01218, SG01255, SG01234, SG01260 and SG03067)
When Rel-8 DNS query is performed, the functionality of the intelligent
GGSN selection features are suppressed.
Restrictions This feature is enabled only for home subscribers and EPC-capable
UEs.
In Gn-SGSN that supports Rel-8 DNS queries, the requirement of UE is
EPC-capable is not taken into consideration when feature f10110-03 is
enabled, regardless the status of this feature.
When this feature is the only enabled feature, UE should be EPC-
capable in case of Gn-SGSN, otherwise Rel-7 DNS query is performed
and CC should apply or not based on the GGSN selection based on
Charging Characteristics feature (SG01218).
When prFile overrideWithModApn is true and handover to MME
takes place, the subscription in HSS will include either the wildcard " * "
APN or the subscription will include the tagged APN in order the PDP
not to be rejected.
Conguration Command gParms, parameter sgsnUseCcInApnForR8DnsPgw.

management Default value is No.
Command apnList, parameter ccPgw.
Command prFile, parameters twoByteChargingChar and
dnsFallbackEnabled.
Counters None
Alarms None
Related references

SGSN User Guide
5.13.1 Configuring P-GW selection based on charging

characteristics for R8 DNS queries
This feature requires activation, fallback functionality provisioning, charging
characteristics value provisioning, and APN list provisioning. Charging characteristics
should appear in subscription data.
Procedure
1 Enable the P-GW selection based on charging characteristics for Rel-8 DNS query
feature.
Step example
cmm gParms modify --gParmName sgsnUseCcInApnForR8DnsPgw
–gParmValue Yes
2 Configure the APN list.
Step example
cmm apnList create –-ccPgw true pgwCCwap1.nokia.com
3 Set the length of the charging characteristics added in the APN.
Step example
cmm prFile modify –-twoByteChargingChar 1 twoByteChargingChar
4 Enable DNS fallback.
Step example
cmm prFile modify --status true dnsFallbackEnabled
5.14 PLMN level control of S6d/Gr selection (Feature

With this feature, an operator can control, at the PLMN level, whether to use the HSS via
S6d interface or the HLR via Gr interface to acquire the UE subscription. This feature is
supported for both home users and roamers in 2G and 3G environments.

SGSN User Guide
Table 89: PLMN level control of S6d/Gr selection: feature summary
Function Impact
Compliance None
Capacity None
Required features SGSN S4 Functionality
Interworking/dependent S6d/Gr selection (Feature SG01236)

features When this feature is enabled, S6d/Gr selection (Feature SG01236) is
disabled.
Restrictions None
Conguration Command gParms, parameter plmnS6dSelection. Default value

management is No, value Yes is to enable the feature.
Command plmnParam, parameters s6dSelection and
fallbackGr.
Counters None
Alarms None
5.14.1 Configuring PLMN level control of S6d/Gr selection

Use global parameter plmnS6dSelection to enable and disable this feature, command
plmnParam parameter s6dSelection to select the HLR or the HSS, and parameter
fallbackGr to enable fallback to the Gr interface.
Procedure
1 Enable PLMN level control of S6d/Gr selection feature.
Step example
cmm gParms modify --gParmName plmnS6dSelection --gParmValue Yes
2 Enable Gr interface to HLR to acquire the UE subscription.
Step example
cmm plmnParam modify --s6dSelection false <plmnParamId>

SGSN User Guide
3 Enable S6d interface to HSS to acquire the UE subscription.
Step example
cmm plmnParam modify --s6dSelection true <plmnParamId>
4 Enable support to fallback to Gr interface.
Step example
cmm plmnParam modify --fallbackGr true <plmnParamId>
5.15 SGSN support for NR UE capability based GW

This feature supports selecting the GGSNs and GWs with 5G GW capabilities based on UE
capability for dual connectivity of the E-UTRAN with the new radio. With this feature, an
operator can deploy option-3/3a/3x/5G overlay networks with a dedicated pool of the
DCNR capable GW.
Table 90: SGSN support for NR UE capability based GW: feature summary
Function Impact
Compliance 3GPP TS 24.008, MS network capability

3GPP TS 29.272, Feature-List-ID 2 and Access-Restriction-Data
Capacity None

SGSN User Guide
Function Impact
Interworking/dependent • Home GGSN solution (Feature SG01116): GGSN selection based on

features the MSISDN
• IMSI-based home GGSN selection (Feature SG01116): GGSN
selection based on the IMSI range
• Nearest GGSN selection (Feature SG01212): GGSN selection based
on the RNC ID
• GGSN selection based on charging characteristics (Feature
SG01218, SG01255): GGSN selection based on charging
characteristic values
• UE capability-based GW selection (Feature SG01234): GGSN/ P-GW
(PDN gateway) selection based on EPC capability of UE
• IMEI based GGSN selection (Feature SG03067): GGSN selection
based on the mobile device type (IMEI)
• SGSN intelligent GGSN/P-GW selection based on requested PDP
type (Feature SG01260): GGSN/P-GW selection based on the
established PDP context activation’s PDP type (IPv4, IPv6 or IPv4v6) of
the home user
• SGSN support for P-GW Selection Based on Charging
Characteristics for R8 DNS queries (f51021-01)
• SGSN support for Gn SGSN PGW Selection Based on MSISDN
Range with rel8 DNS (f10110-03)
• CMM support for MSISDN number based Home GGSN/P-GW
Selection enhancement (f10176-01)
Restrictions This feature affects home subscribers only.

The CMM does not search for the DCNR capable GGSN/S-GW/P-GW
during the mobility scenarios of:
• incoming inter-SGSN RAU
• incoming inter-SGSN relocation
• incoming RAU or inter-SGSN HO from MME
- For the S4-SGSN, if a new PDP Activation Request message is
received for the new PDP after the RAU or inter-SGSN HO, the CMM
performs NAPTR query only for the DCNR capable P-GW. The S-GW is
preserved according to 3GPP TS 23.060.
Conguration Command gParms, parameter nrBasedGwSelectionSgsn

management
Counters None
Alarms None
Related descriptions
Intelligent GGSN selection (Features SG01116, SG01212, SG01218, SG01255, SG01234,
SG01260 and SG03067): feature summary

SGSN User Guide
P-GW selection based on charging characteristics for R8 DNS queries (Feature

Related references
Gn SGSN P-GW selection based on MSISDN range with rel8 DNS (Feature f10110-03):
feature summary
MSISDN number based home GGSN/P-GW selection enhancement (Feature f10176-01):
feature summary
5.16 SGSN support for 512 direct tunnel APNs (Feature

With this feature, the maximum number of APNs that can be provisioned as eligible for
direct tunnel increases from 254 to 512. The maximum count of APN list is extended from
254 (DT and non-DT) to 766 (512 DT and 254 non-DT).
Table 91: SGSN support for 512 direct tunnel APNs: feature summary
Function Impact
Compliance None
Capacity Up to 512 APNs eligible for direct tunnel.
features
Restrictions None
Conguration Command apnList

management
Counters None
Alarms None

SGSN User Guide
5.17 CMM support for control the subscriber to make one

PDP per subscriber per APN (Feature f10189-01): feature
summary
This feature enhances the CMM behavior to control the subscriber to activate one PDP
for the same APN.
Table 92: CMM support for control the subscriber to make one PDP per subscriber per APN:
feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent Override of requested APN in SGSN (Feature SG01074)

features Override of requested APN in SGSN (Features SG01074 and
f52032-01)
IMEI-ased APN override (Feature SG02019)
Restrictions None
Conguration Command gParms, parameter singlePdpPerApnSgsn

management
Counters None
Alarms None
5.18 SGSN support for static GGSN/P-GW selection with

IMSI and MSISDN range (Feature f52070-01): feature
summary
With this feature, a Gn-SGSN is able to select specific GGSNs for PDP context activation
based on static configuration for the IMSI or MSISDN, without using a DNS query.

SGSN User Guide
Table 93: SGSN support for static GGSN/P-GW selection with IMSI and MSISDN range: feature
summary
Function Impact

Capacity Maximum of 50 entries for static list conguration.
Interworking/dependent If a matching record is found, intelligent GGSN selection features and

features R8 DNS query support for Gn-SGSN (Features SG02213,
f52058-01) are overridden.
Restrictions None
Conguration Command gParms, parameter staticGwSelection. Default

management value is No
Command sgsnPgwSelectionRangeServices
Counters None
Alarms None
R8 DNS query support for Gn-SGSN (Features SG02213, f52058-01): feature summary
5.18.1 Configuring static GGSN/P-GW selection with IMSI

and MSISDN range
Activate the feature with the global parameter staticGwSelection. Modify the Gn-
SGSN configurations or records using command sgsnPgwSelectionRangeServices.
▪ Activate the feature.
cmm gParms modify --gParmName staticGwSelection --gParmValue Yes
▪ Add a Gn-SGSN configuration or record.
cmm sgsnPgwSelectionRangeServices create --entryId <integer> --

apnNi <string> --ggsnIpAddress <string> --maxMsin <digits> --
minMsin <digits> --rangeServiceType {imsi,msisdn}

SGSN User Guide
Step example
cmm sgsnPgwSelectionRangeServices create --entryId 1 --apnNi
example1.sample.com --ggsnIpAddress 2511:0:0:994::631 --maxMsin
358701 --minMsin 358700 --rangeServiceType msisdn
▪ Modify a Gn-SGSN configuration or record.
cmm sgsnPgwSelectionRangeServices modify entryId
Step example
cmm sgsnPgwSelectionRangeServices modify 1 --apnNi
example2.sample.com

SGSN User Guide
6. Pooling and network sharing features
6.1 Multipoint Gb (Features SG01023 and SG01153):

feature summary
The Multipoint Gb feature uses the standardized respective features as described in 3GPP
TS 23.236, Intra-domain connection of Radio access network (RAN) nodes to multiple
Core Network (CN) nodes, Release 5 and they are supported in 2G only. These features
enable the operator to add several SGSNs to serve the same routing area.
Table 94: Multipoint Gb (Features SG01023 and SG01153): feature summary
Function Impact
Compliance • 3GPP TS 23.003, Numbering, Addressing and Identication

• 3GPP TS 23.060, General Packet Radio Service (GPRS); Service
• 3GPP TS 23.236, Intra Domain Connection of RAN Nodes to Multiple
CN Nodes
• 3GPP TS 48.016; General Packet Radio Service (GPRS); Base Station
System (BSS) - Serving GPRS Support Node (SGSN) Interface; Network
Service
• 3GPP TS 48.018; General Packet Radio Service (GPRS); Base Station
System (BSS) - Serving GPRS Support Node (SGSN); BSS GPRS Protocol
Capacity Because of the increased radio network conguration information, that

is, more cells and NS-VCs in a PAPS, severe overload can occur due to
heavy MS ow control, BVC resets, and NS-VC blocks and unlocks.
However, subscribers do not move from one PAPS to another or
between SGSNs, which dramatically reduces the signaling load between
SGSNs and between an SGSN and the HLR/HSS.
Multipoint Gb may stress the SGSN and statistics because of the radio
network conguration increase. There are more cells and NS-VCs in a
PAPS.
If the size of the radio network becomes too large, the MS ow control,
the BVC reset, and the NS-VC block and unlock may burden the PAPS.
The offloading process increases traffic in the Gn and Iu interfaces due
to the detach with reattach requests and the RAU processes to another
SGSN.
Interworking/dependen • Multipoint Iu (Features SG02002, SG01153 and SG02210)

t features • PAPS 3G graceful shutdown ( Features SG01086 and f60210-27)

SGSN User Guide
Function Impact
Restrictions The NRI must be unique in each of the overlapping pool areas, and the
length of the NRIs has to be the same in these pool areas (5, 6 or 7
bits).
A PCU can be connected to one standalone PAPS or several PAPS only
in an SGSN. This restriction is needed to avoid the PCU creating the
same cells with the same RAs in several PAPSs. An SGSN must reject cell
creation if the specied RA, controlled by another PAPS, already exists
in the SGSN.
If a PCU is connected to several PAPSs with the same RAs then it is
possible that several PAPSs serve the same RAs in an SGSN.
A Nokia BSC supports eight NSEs per PCU, therefore, a PCU can be
connected to a maximum of eight SGSNs in a pool area.
Removing SGSN for Maintenance on Multipoint Iu/Gb and PAPS 3G
graceful shutdown features cannot be used simultaneously.
In 7 bits NRI length conguration, there can be only 16 individual PAPS
units.
In 6 bits NRI length conguration, there can be 20 PAPS units.
Conguration Command gParms, parameters nullNri, nriLength, sgsnId and

management sgsnPoolId.
Command features, parameters mpGb, multipGbNri and
multipointDns.
Command sgsnTimer, parameter offloadPrauTimer.
Command maintenance
Command pool (for DNS optimization)
Counters None
Alarms None
6.1.1 Configuring multipoint Gb

The procedure includes steps for configuring multipoint Gb and preparation before the
configuration.
Before you start
The parameters in the BSC are set:

The values to PS NRI list are set in every BSC.
The NRI length in every BSC is set to 7.
The DNS query entities are set to the DNS (NRI.RAC.LAC.MNC.MCC) for every SGSN.

SGSN User Guide
Procedure
cmm features modify mpGb --status true
Note:
In case NRI length is 6 or 7, then cmm features modify multipGbNri should

be set to status true in addition to activating the feature.
2 Add parameters related to Multipoint Gb.
2.1 Set the NRI length and the SGSN ID, if it does not exist.
Step example
cmm gParms modify --gParmName nriLength --gParmValue 7
Step example
cmm gParms modify --gParmName sgsnId --gParmValue 12
Step example
cmm gParms modify --gParmName sgsnPoolId --gParmValue 02
2.2 Interrogate that the SGSN ID is correct.
cmm gParms list
Note:
The usage of number 0 for SGSN ID is restricted for all SGSN nodes in
customer’s network and each SGSN must have a unique SGSN ID. The
reason is that SGSN ID 0 can cause unequal load balancing when LRAS
Feature is used in neighborhood SGSN.
6.2 Multipoint Iu (Features SG02002, SG01153 and

The Multipoint Iu feature enables radio access sharing in a 3G environment. With this
feature, one RNC can be connected to more than one SGSN as described in 3GPP TS

SGSN User Guide
23.236, Intra-domain connection of Radio Access Network (RAN) nodes to multiple Core
Network (CN) nodes.
Table 95: Multipoint Iu (Features SG02002, SG01153 and SG02210): feature summary
Function Impact
Compliance • 3GPP TS 23.003 Numbering, Addressing and Identication

• 3GPP TS 23.060 General Packet Radio Service (GPRS); Service
• 3GPP TS 23.236 Intra-domain connection of Radio Access
Network (RAN) nodes to multiple Core Network (CN) nodes
• 3GPP TS 25.413 UTRAN Iu interface Radio Access Network
Application Part (RANAP) signaling
Required features 3G access support (Features SG02001 and SG01119)
Interworking/dependent Multipoint Gb (Features SG01023 and SG01153)

features
Restrictions The NRI must be unique in each of the overlapping pool areas, and
the length of the NRIs has to be the same in these pool areas (5, 6
or 7 bits).
Removing SGSN for Maintenance on Multipoint Iu/Gb and PAPS 3G
graceful shutdown features cannot be used simultaneously.
In 7 bits NRI length conguration, there can be only 16 individual
PAPS units.
In 6 bits NRI length conguration, there can be 20 PAPS units.
Conguration management Command gParms, parameters nriLength, sgsnId,

nullNri and sgsnPoolId.
Command features, parameters mpIu, multipGbNri and
multipointDns.
Command sgsnTimer, parameter offloadPrauTimer.
Command maintenance
Command pool (for DNS optimization)
Counters None
Alarms None
Feature ID SG02002, SG01153 and SG02210
6.2.1 Configuring multipoint Iu

Multipoint Iu is a network wide feature which accordingly needs to be provisioned

SGSN User Guide
properly in all SGSNs, RNCs and DNS servers of the pool.
As a general rule, it is better to map all RNCs in all SGSNs in the pool. It is possible to have
certain RNCs connected only to specific SGSN but in that case the Multipoint Iu DNS
oprtimization should not be activated (the feature that bypasses NRI DNS queries and uses
local provisioning for old SGSN discovery).
6.2.1.1 Configuring the NRI in SGSN

The procedure includes steps for configuring multipoint Iu and preparation before the
configuration.
Before you start
The parameters in the RNC are set:

The values to PS NRI list are set in every RNC.
The NRI length in every RNC is set to 7.
The DNS query entities are set to the DNS (NRI.RAC.LAC.MNC.MCC) for every SGSN.
Procedure
cmm features modify mpIu --status true
Note:
In case NRI length is 6 or 7, then cmm features modify multipGbNri should

be set to status true in addition to activating the feature.
2 Set the NRI length, the SGSN ID and the pool ID (if relevant).
Step example
cmm gParms modify --gParmName nriLength --gParmValue 7
Step example
cmm gParms modify --gParmName sgsnId --gParmValue 12
Step example
cmm gParms modify --gParmName sgsnPoolId --gParmValue 02

SGSN User Guide
Note:
SgsnPoolId is only relevant if NRI length is 6 or 7.

The usage of number 0 for SGSN ID is restricted for all SGSN nodes in
customer’s network and each SGSN must have a unique SGSN ID. The reason is
that SGSN ID 0 can cause unequal load balancing when LRAS Feature is used in
neighborhood FNS SGSN.
6.2.1.2 Adding SGSN to the pool

Procedure
1 Activate the multipoint Iu feature in all the SGSNs that are in the pool.
For more information, see Configuring the NRI in SGSN.
2 Set the NRI length and SGSN ID.
3 Create connections (Iu over IP) between the new SGSN and the RNCs.
3.1 Configure all the SGSN-related parameters (SPC, NRI etc.) in all the RNCs in the
pool.
4 Configure routing areas in the SGSN (RNC-RAI configuration) by copying settings

from the default SGSN in the pool to the new SGSN.
5 Set DNS query keys to the DNS (NRI.RAC.LAC.MNC.MCC) for the SGSN.
6 Set NRI length in all RNCs. This activates the Multipoint Iu feature.
6.2.1.3 Adding RNC to the PS pool area

Procedure
1 Activate the multipoint Iu license in all the RNCs that are in the pool area.

SGSN User Guide
2 2 Set connections (Iu over IP) from the SGSNs to the RNC.
2.1 Define link parameters to one SGSN in the pool.
2.2 Copy settings to all of the SGSNs in the pool.
2.3 Configure all the SGSN-related parameters (SPC, NRI etc.) to the new RNC.
3 Set the global RNC ID in the SGSN (RNC configuration) by adding the RNC ID to every
SGSN in the pool.
4 Define the routing area of the RNC to every SGSN in the pool.
5 If a new RNC will be added to the pool area, set DNS query keys to the DNS
(NRI.RAC.LAC.MNC.MCC) for the SGSNs.
6 Set the NRI length in all RNCs. This activates the Multipoint Iu feature.
6.2.1.4 Rollback steps for SGSN

In case wrong NRI has been added to the SGSN, DNS and RNCs , feature activation must
be rolled back. The feature must be activated again with the correct NRI value.
Corrections are performed to the whole system level in a controlled way.
Procedure
1 In RNCs, switch the Iu interface to the SGSN off.
2 Wait until the periodic RAU timer has expired.
3 Configure the correct NRI value and/or NRI length to the SGSN.
4 Set the correct NRI values to DNS query keys (NRI.RAC.LAC.MNC.MCC) for the SGSN.
5 Set the correct NRI values in all the RNCs in the pool.
6 In RNCs, switch the Iu interface to the SGSN on.

SGSN User Guide
7 Verify that the new configuration works correctly.
6.3 Removing SGSN for maintenance for multipoint Gb/Iu

The procedure includes steps for removing SGSN for maintenance for multipoint Gb/Iu
and preparation before removing.
Before you start
Before the SGSN can be removed from the pool, the operator needs to configure the null-
NRI, non-broadcast routing area identity (RAI), and periodic routing area update timer for
the offloading procedure. The non-broadcast RAI has to be unique for each SGSN to enable
the target SGSN to retrieve data (such as IMSI, security contexts, mobility management and
packet data protocol contexts) from the source SGSN during offloading.
Procedure
1 Set the null-NRI in the SGSN.
Step example
cmm gParms modify --gParmName nullNri --gParmValue 31
2 Interrogate that null-NRI is correct.
cmm gParms show --gParmName nullNri
3 Create non-broadcasting RAI.
Step example
cmm system modify config --nbmcc 123 --nbmnc 01 --nblac 1 --nbrac
1
4 Interrogate that non-broadcasting RAI is correct.
cmm system show
5 Set offload PRAU timer.
Step example
cmm sgsnTimer modify config --offloadPrauTimer 4

SGSN User Guide
6 Interrogate that offload PRAU timer is correct.
cmm sgsnTimer show
7 Activate maintenance mode.
Step example
cmm maintenance create --rat GB SGSN or
Step example
cmm maintenance create --rat IU SGSN or
Step example
cmm maintenance create --rat ALL SGSN
6.4 Multipoint Iu/Gb DNS optimization

The Multipoint Iu/Gb DNS optimization feature simplifies the approach for identifying the
source SGSN in a multipoint Iu/Gb pool for inter-SGSN pool routing area update
scenarios.
Procedure
cmm features modify multipointDns --status true
2 Configure locally NRIs and IP addresses table for other SGSNs in the pool.
Step example
cmm pool create 1 --poolnri 11 --ipAddress 10.10.10.10 --
interface GN
Step result

SGSN User Guide
+-----------+-------------+
| Field | Value |
+-----------+-------------+
| pool | 1 |
| poolnri | 11 |
| ipAddress | 10.10.10.10 |
| interface | GN |
+-----------+-------------+
6.5 SGSN support for offloading functionality (Feature

This feature allows the operator to move/offload a subset of subscribers served by one
SGSN (source) to another SGSN (target) of the pool in a multipoint Iu/Gb pool
environment.

SGSN User Guide
Table 96: SGSN support for offloading functionality (Feature f50106-02): feature summary
Function Impact
Compliance 3GPP TS 23.236 Intra-domain connection of Radio Access Network

(RAN) nodes to multiple Core Network (CN) nodes
Capacity SGSN supports up to 16 Target CMM SGSN for offloading.
Required features Multipoint Iu (Features SG02002, SG01153 and SG02210)

and/or Multipoint Gb (Features SG01023 and SG01153)
features
Restrictions The target SGSN(s) for offloading functionality should be strictly

CMM SGSN(s) as specic IE private extensions are used.
Conguration management Commands cmm features mpGb, cmm features mplu,

cmm features 2gSubsOffloading, cmm features
subsOffloading, cmm subsOffloadTarget create,
cmm prFile modify enhOfflIdleSubsRate, cmm
maintenance create , cmm subsOffloadCount list
Charging None
Counters None
Alarms 14122 - SgsnOffloadProcedureInPaps
6.5.1 Configuring SGSN support for offloading

functionality
The procedure includes steps for activating and configuring SGSN support for offloading
functionality.
Before you start
Ensure that mpGb/mpIu, 2gSubsOffloading, and subsOffloading features are active.

(cmm features show mpGb, cmm features show mpIu, cmm features show
2gSubsOffloading, cmm features show subsOffloading).
Configure NRI for CMM SGSN by setting SGSN-id and NRI-length (if do not exist). This is
Multipoint related configuration and might already exist.
Example: cmm gParms modify --gParmName nriLength --gParmValue 5, cmm

SGSN User Guide
gParms modify --gParmName sgsnId --gParmValue 9

NRI parameters should be configured in RNC and BSC sides as well (not CMM related).
Create Non-Broadcasting RAI parameters nbmnc, nbmcc, nblac and nbrac. These
parameters should not be configured same as RAI, which is configured to any RNC / BSC
in the network.
Example: cmm system modify config --nbmcc 244 --nbmnc 08 --nblac
1111 --nbrac 11
Verify that null-NRI has been set in SGSN.
Example: cmm gParms modify --gParmName nullNri --gParmValue 31
Set or check the offload PRAU timer. Default value is 4 seconds.
Example: cmm sgsnTimer modify config --offloadPrauTimer 4 or cmm
sgsnTimer show)
Verify correct DNS query entries in DNS server for every SGSN in the pool
(NRI.RAC.LAC.MNC.MCC) and also for Non-broadcast RAIs for each SGSN
(NBRAC.NBLAC.MNC.MCC).
Procedure
1 Check if previous targets exist and set needed target(s) CMM SGSN parameters.
Step example
cmm subsOffloadTarget create --subsNri 05 --subsOffPercentage 50
--subsOffrate 150 1
Step result
+-------------------+-------+
| Field | Value |
+-------------------+-------+
| subsOffloadTarget | 1 |
| subsNri | 05 |
| subsOffPercentage | 50 |
| subsOffrate | 150 |
+-------------------+-------+

SGSN User Guide
Note:
The addition of all subsOffPercentage for all target SGSN’s should not be
greater than 100.
subsOffrate refers to phase 2 offloading rate per PAPS.
2 Set offload rate for offloading phase 1 subscribers to Target SGSN
Step example
cmm prFile modify enhOfflIdleSubsRate --enhOfflIdleSubsRate 30
Step result
+---------------------+----------------------------------+
| Field | Value |
+---------------------+----------------------------------+
| prFile | enhOfflIdleSubsRate |
| status | true |
| parameter | IDLE SUBSCRIBERS OFFLOADING RATE |
| enhOfflIdleSubsRate | 30 |
+---------------------+----------------------------------+
Note:
enhOfflIdleSubsRate refers to phase 1 offloading rate per PAPS.

the status of the enhOfflIdleSubsRate parameter does not control the
activation or deactivation of the feature.
3 Check if any offloading procedure is running and if not start the offloading
procedure. Multiple offloading cannot be activated simultaneously.
Step example
cmm maintenance create --offload AUTO --rat ALL --type OFFL SGSN
4 Check the already offloaded subscribers during offloading procedure running.
Step example
cmm subsOffloadCount list

SGSN User Guide
Step result
+----------+---------+--------------+------------+
| targetId | percent | currentCount | totalCount |
+----------+---------+--------------+------------+
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 0 | 0.0% | 0 | 0 |
| 1 | 91.5% | 2522387 | 2755279 |
| all | 91.5% | 2522387 | 2755279 |
+----------+---------+--------------+------------+
Note:
The percent value and currentCount parameters, may show less

subscribers than the real total number of subscribers that are offloaded towards
Target SGSN.
5 Stop/cancel the offloading procedure.
cmm maintenance delete SGSN
6.6 SGSN support for multipoint offloading with IMSI

This feature enables the operator to offload specific subscriber(s) to target CMM SGSN in

SGSN User Guide
the pool by specifying the IMSI number.
Table 97: SGSN support for multipoint offloading with IMSI (Feature f52010-04): feature
summary
Function Impact
Compliance None
Capacity SGSN supports up to 20 IMSI/NRI pairs congured at a time.
Required features Multipoint Iu (Features SG02002, SG01153 and SG02210) and /or
Multipoint Gb (Features SG01023 and SG01153).
SGSN support for offloading functionality (Feature f50106-02).
features
Restrictions The target SGSN(s) for offloading functionality should be strictly

CMM/SGSN(s) as specic IE private extensions are used.
Conguration management Command cmm features, parameters mpGb mplu,

2gSubsOffloading, subsOffloading,
imsiBasedOffload
Commands cmm subsImsiOffload create, cmm
maintenance create, cmm nriConfig list
Charging None
Counters None
Alarms None
Note:
IMSI offloading procedure has no impact on new subscribers handling.
6.6.1 Configuring multipoint offloading with IMSI

Activate and configure multipoint offloading with IMSI.
Before you start

SGSN User Guide
Ensure that mpGb/mpIu, 2gSubsOffloading, subsOffloading and imsiBasedOffload cmm

features are active.
(cmm features show mpGb, cmm features show mpIu, cmm features show
2gSubsOffloading, cmm features show subsOffloading and cmm features
show imsiBasedOffload).
Configure NRI for CMM SGSN by setting SGSN ID and NRI-length (if do not exist). This is
multipoint related configuration and might already exist.
Example: cmm gParms modify --gParmName nriLength --gParmValue 5
Example: cmm gParms modify --gParmName sgsnId --gParmValue 9
Check the configured NRI value: cmm nriConfig list
NRI parameters should be configured in RNC and BSC sides as well (not CMM related).
Create non-broadcast RAI parameters nbmnc, nbmcc, nblac and nbrac (if they don’t
already exist). These parameters should not be configured same as RAI, which is
configured to any RNC / BSC in the network.
Example: cmm system modify config --nbmcc 244 --nbmnc 08 --nblac
1111 --nbrac 11
Verify correct DNS query entries in DNS server for every SGSN in the pool
(NRI.RAC.LAC.MNC.MCC) and also for non-broadcast RAIs for each SGSN
(NBRAC.NBLAC.MNC.MCC).
Note:
The IMSI/NRI pairs should be (re)created each time before starting the IMSI offloading
process.
Procedure
1 Configure the required IMSI – target NRI pair(s) for existing subscriber(s) to be
offloaded.
Step example
cmm subsImsiOffload create –-subsNri 05 444092046000912
Step result

SGSN User Guide
+-------------------+-----------------+
| Field | Value |
+-------------------+-----------------+
| subsImsiOffload | 444092046000912 |
| subsNri | 05 |
+-------------------+-----------------+
2 Start the offloading procedure with IMSI.
Before starting the offloading procedure with IMSI, check if any offloading procedure is
running. Multiple offloading procedures cannot be activated simultaneously.
cmm maintenance create --type IOFFL SGSN
3 Check if specific subscribers are offloaded.
Step example
cmm subscriber show --imsi 444092046000912
Step result
+-------+-------+
| Field | Value |
+-------+-------+
| | |
+-------+-------+
4 Stop/cancel the offloading procedure.
cmm maintenance delete SGSN
5 Delete the configured IMSI/NRI pair(s).
Step example
cmm subsImsiOffload delete 444092046000912
Step result

SGSN User Guide
+-------------------+-----------------+
| Field | Value |
+-------------------+-----------------+
| subsImsiOffload | 444092046000912 |
| subsNri | 05 |
+-------------------+-----------------+
6.7 Network sharing (Features SG01040, SG01021,

SG01129, SG01179, SG02212 and f60210-29)
Network sharing comprises a number of features for network selection and sharing.
The features are:

Network selection services
Multiple PLMN support (SG01040)
Equivalent PLMN (SG01021)
LAC based EPLMN (SG01129)
Enhanced GW selection
SS7 network sharing (SG01083)
3G multi operator core network (3G MOCN) (SG01179)
2G multi operator core network (2G MOCN) (SG02212)
6.7.1 Network selection services (Features SG01021,

SG01129, SG01040): feature summary
Network selection services features proved support for a) several different mobile
country code (MCC) and mobile network code (MNC) combinations as home subscribers b)
several public land mobile networks (PLMNs) within its coverage area, meaning that there
can be radio network controllers (RNCs) in 3G and base station controllers (BSCs) in 2G, of
different PLMNs under the SGSN, c) equivalent PLMNs, meaning that a list of equivalent
PLMNs is sent to the user equipment (UE) or mobile station (MS), whereby the UE/MS
stores the list and treats the PLMNs equivalently in PLMN selection, and d) enhanced
GGSN selection.

SGSN User Guide
Table 98: Network selection services (Features SG01021, SG01129, SG01040): feature
summary
Function Impact
Compliance The equivalent PLMN list sent to the UE is based on 3GPP TS 24.008;
Mobile radio interface Layer 3 specication; Core network protocols;
Stage 3 (Release 5).
Capacity None
Required features Equivalent PLMN (Feature SG01021) is enhanced with LAC based
EPLMN (Feature SG01129), but is also a prerequisite for LAC based
EPLMN to work. If LAC based EPLMN is not switched on, Equivalent
PLMN works normally.
Interworking/dependent If network selection services is active, all subscribers considered as

features home subscribers by it are considered as home subscribers by the
controlled roaming (Feature SG01004) as well. Operators using
controlled roaming can restrict the use of equivalent PLMN lists.
Restrictions The maximum number of equivalent PLMN lists is 256 and each list can
have a maximum of 10 entries.
The UE/MS must support the same version of the GPRS mobility
management (GMM) protocol (specied in 3GPP TS 24.008) as the
shared SGSN.
For network selection services, equivalent PLMN list- specic
information elements must be supported in the UE/MS.
Conguration Command sgsnLai, parameter epind

management Command rait, parameter epind
Command eqPlmn
Command features, parameters equivalentPlmn,
lacBasedEplmn
Counters None
Alarms None
Feature ID Equivalent PLMN (SG01021), LAC based EPLMN (SG01129), Multiple

PLMN support (SG01040)
6.7.1.1 Configuring network selection services

The task consists of activating the feature, configuring LA parameters, and creating
equivalent PLMN.

SGSN User Guide
Procedure
cmm features modify lacBasedEplmn --status true
2 Configure LA parameters.
Congure LA parameters in GPRS Add Equivalent EPLMN list index (epind) to a LA:
network cmm sgsnLai modify <sgsnLai> --epind
<epind>
Congure LA parameters in Add equivalent EPLMN list index (epind) to a LA:

UMTS network cmm rait modify <rait> --epind <epind>
Possible epind values are 0...5 and 255 where:
0 The epind is set to value 'all'. All equivalent PLMNs dened for
network selection services (Feature SG01021) are used for the LA.
255 The epind is set to value 'not dened'. No equivalent PLMNs

dened for network selection services (Feature SG01021) are used
for the LA.
3 Create equivalent PLMN.
Create an equivalent PLMN and link it to a PLMN using the plmnParamId. PLMN must
have been already created using cmm plmnParam command.
cmm eqPlmn create --eqPlmnId <eqPlmnId> --plmnParamId

<plmnParamId> --mcc <mcc> --mnc <mnc> --eplmnIndex <eplmnIndex>
eqPlmnId This is the ID to be assigned to the new EPLMN.

SGSN User Guide
eplmnIndex The parameter denes the location areas in which the given
MCC+MNC combination is relevant. Possible values are all index
combinations from 1 to 5. Some examples:
• 00000 - no index in use
• 00001 - index 1 in use
• 00011 - index 1 and index 2 in use
• 01010 - index 2 and index 4 in use
• 01110 - index 2, index 3 and index 4 in use
• 11111 - all 5 indexes in use
6.7.1.2 Deactivating network selection services

To disable network selection services, clear the equivalent PLMN index configuration, set
equivalent PLMN index to value no index in use, and deactivate the feature.
Procedure
1 Clear equivalent PLMN list index (epind) from LA.
cmm sgsnLai modify <sgsnLai> --epind 0
2 Clear equivalent EPLMN list index (epind) from LA.
cmm rait modify <rait> --epind 0
3 Clear equivalent PLMN index (eplmnIndex) from the PLMN parameters.
cmm eqPlmn modify --eqPlmnId <eqPlmnId> --eplmnIndex 00000
4 Deactivate the feature.
cmm features modify lacBasedEplmn --status false
6.7.2 SS7 network sharing (Feature SG01083): feature

summary
SGSN normally has signalling connection control part (SCCP) global title (GT) addresses to
identify itself in the network. The GT address identifies the network making the
connection to the roaming partner PLMN. With the SS7 network sharing feature, it is
possible to define multiple GT addresses for the SGSN. This feature is useful especially in
network sharing cases where the core network is shared by partner operators at the edge

SGSN User Guide
of the radio access network.
Table 99: SS7 network sharing (Feature SG01083): feature summary
Function Impact
Compliance SS7 addresses used in network sharing (virtual SS7) are dened as GT
addresses as specied in ITU-T Recommendation Q.713: Signalling
connection control part formats and codes.
Capacity None
Required features SS7 network sharing enhances the functionality of network selection
services. Unless otherwise stated, these features are collectively
referred to as network sharing.
features
Restrictions There can be a maximum of 10 network element addresses of its own

in the SGSN.
SS7 network sharing is valid only for roaming subscribers.
Interworking of variants is not currently supported. Parallel
conguration is not recommended.
Conguration Commands:
management • virtualSgsnAddress
• mapAddrAnalysisResult
• mapAddrAnalysis
• gtAnalysis
Command features, parameter ss7NetworkSharing
Counters None
Alarms None
Feature ID SG01083
6.7.2.1 Activating SS7 network sharing

To use SS7 network sharing (variant 1 or variant 2), activate the feature using the
ss7NetworkSharing parameter.
▪ Activate the feature.
cmm features modify ss7NetworkSharing --status true
To deactivate the feature, set the parameter to value false.

SGSN User Guide
6.7.2.2 Configuring SS7 network sharing variant 1: Multiple

GT addresses based on analysis for Called-Party-Address
(CdPA)
With variant 1 of SS7 network sharing, operators sharing a core network can specify their
own SS7 Calling Party Address to 2G/3G-SGSN.
Before you start
Feature SS7 network services must be activated (parameter ss7NetworkSharing).
Procedure
1 Create network and network element specific number.
The maximum length of virtual SGSN address is 18 decimal digits. When the virtual
SGSN address (vsa) is given, both the numbering plan (np) and the type of number
(ton) must be set. Otherwise, default values are used (E212 and INT respectively).
cmm virtualSgsnAddress create <id> --vsa <vsa> --np <np> --ton

<ton>
Step example
cmm virtualSgsnAddress create 1 --vsa 358480666 --np E164 --ton
INT
2 Create network entity address analysis result.
cmm mapAddrAnalysisResult create --result <result> --name <name>
Step example
cmm mapAddrAnalysisResult create --result 1 --name TTCN
3 Create the result addresses for the network entity address analysis.
cmm mapAddrAnalysisResAddr create --resAddressIndex

<resAddressIndex> --resAddressName <resAddressName> --sgsn
<virtual SGSN address> --sgsnTon <SGSN ton>
Step example
cmm mapAddrAnalysisResAddr create --resAddressIndex 1 --

SGSN User Guide
resAddressName TTCN --sgsn 358480666 --sgsnTon INT
4 Create the network entity address analysis.
4.1 Create the network entity address analysis with global title (GT).
cmm mapAddrAnalysis create --toA <toA> --gtDigits <gtDigits>

--np <np> --toN <toN> --resNumber <resNumber> --
resAddressName <resAddressName> --resAddressIndex
<resAddressIndex> --spc <spc> --ni <ni>
Step example
cmm mapAddrAnalysis create --toA GT --gtDigits 35848056 --np
E214 --toN INT --resNumber 1 --resAddressName TTCN --
resAddressIndex 1 --spc 5081 --ni IN0
4.2 Create the network entity address analysis with destination point code (DPC).
cmm mapAddrAnalysis create --toA <toA> --gtDigits <gtDigits>

--np <np> --toN <toN> --resNumber <resNumber> --
resAddressName <resAddressName> --resAddressIndex
<resAddressIndex> --spc <spc> --ni <ni>
Step example
cmm mapAddrAnalysis create --toA DPC --gtDigits 35848056 --
np E214 --toN INT --resNumber 1 --resAddressName TTCN --
resAddressIndex 1 --spc 5081 --ni IN0
Step result
Make sure that the np number in mapAddrAnalysis command matches the np
number in IMSI analysis. Otherwise, SGSN will not send the virtual number.
Example of IMSI analysis output:

SGSN User Guide
#cmm imsiAnalysis show 2440720
+--------------+---------+
| Field | Value |
+--------------+---------+
| imsiAnalysis | 2440720 |
| plmnName | ETPLMN |
| toA | GT |
| ni | IN0 |
| spc | |
| ton | INT |
| np | E214 |
| srd | 1 |
| nrd | 8 |
| sad | 1 |
| dia | 3587021 |
+--------------+---------+
5 Create a GT analysis for the new virtual SGSN address in the SGSN.
cmm gtAnalysis create --gtaId <gtaId> --numberingPlan <

numberingPlan> --gtResultId <gtResultId>
Step example
cmm gtAnalysis create --gtaId 358480666 --numberingPlan 1 --
gtResultId 1
6.7.2.3 Deactivating SS7 network sharing variant 1

Steps for deleting SS7 network sharing variant 1, multiple GT addresses based on
analysis for Called-Party-Address (CdPA). In each step, the delete action requires ID as
attribute. Finally, deactivate the feature.
Procedure
1 Delete network and network element specific number.

SGSN User Guide
Step example
cmm virtualSgsnAddress delete 1
2 Delete the network entity address analysis.
Step example
cmm mapAddrAnalysis delete 35848056~5081~IN0
3 Delete the network entity address analysis result.
Step example
cmm mapAddrAnalysisResult delete 1
4 Delete the network entity address analysis result addresses.
Step example
cmm mapAddrAnalysisResAddr delete 1
cmm features modify ss7NetworkSharing --status false
6.7.2.4 Configuring SS7 network sharing variant 2: SS7

network sharing enhancement or equivalently Multiple GT
addresses based on RAN (PLMN) of the subscriber
With the SS7 network sharing enhancement, when the SGSN is connected to multiple RAN
with different PLMN, the SGSN is able to present different SGSN GT addresses to a
foreign HLR, depending on which RAN subscriber is attached to.
Before you start
Feature SS7 network services must be activated (parameter ss7NetworkSharing).
▪ Create network and network element specific number.
The maximum length of virtual SGSN address is 18 decimal digits. When the virtual
SGSN address (vsa) is given, both the numbering plan (np) and the type of number
(ton) must be set. Otherwise, default values are used (E212 and INT respectively).

SGSN User Guide
cmm virtualSgsnAddress create <id> --vsa <vsa> --np <np> --ton

<ton>
Step example
cmm virtualSgsnAddress create 1 --vsa 358480666 --np E164 --ton
INT
Result
If you wish to deactivate the feature,
clear the configuration: cmm virtualSgsnAddress delete 1
set the feature parameter to false: cmm features modify ss7NetworkSharing --
status false
6.7.3 Multi operator core network (MOCN) functionality

(Features SG01179 and SG02212): feature summary
In MOCN configuration, the multiple core network (CN) operators share the radio access
network for 2G (Feature SG02212) or 3G (Feature SG01179).

SGSN User Guide
Table 100: Multi operator core network (MOCN) (Features SG01179, SG02212): feature
summary
Function Impact
Compliance 3GPP 23.251 Network Sharing Architecture and functional description,

7.0.0 The standardisation baseline used is 3GGP Release 7, March 2007.
For GERAN: 3GPP 23.251 Release 10
Capacity None
Required features To enable the functionality of the 2G MOCN, the equivalent PLMN list
(Feature SG01021) of Network Selection Service must be used.
Interworking/dependent LAC based EPLMN (Feature SG01129), which is an enhancement of the

features equivalent PLMN list (Feature SG01021), can also be used.
With these features, a MOCN operator using the common 2G radio
network includes the broadcasted common PLMN ID in the EPLMN list
or in the LAC-based EPLMN list, respectively. This enables a non-
supporting MS to know it is roaming in the home network.
Restrictions 3G multi operator core network (SG01179):

• There can be only one SPC connection per RNC.
• The maximum number of PLMNs per RNC is 5.
Conguration Commands
management • rnc
• rait
• raitOfRnc
Command plmnParam, parameter csPsCoord
Command prFile, parameter rauCsPsCoordination
Command system, parameter csps2g
Command features, parameter mocn
Counters M020C055 / NUMBER OF CS/PS COORDINATIONS
Alarms None
Feature ID 3G multi operator core network (SG01179), 2G multi operator core

network (SG02212)
6.7.3.1 Configuring 2G MOCN

Configuring 2G MOCN (SG02212) requires feature activation, CS/PS coordination
activation, and PLMN configuration.

SGSN User Guide
Procedure
cmm features modify 2gMocn --status true
2 Activate CS/PS coordination for a non-supporting MS.
If needed, CS/PS coordination is requested for a non-supporting MS when the system

parameter csps2g is set:
cmm system modify config --csps2g true
3 Create a new PLMN parameter set.
You can create a PLMN level parameter set in the SGSN for new PLMN. It defines the
default parameters used for this PLMN.
Step example
Create visitor PLMN:
cmm plmnParam create --plmnParamId VISITOR_PLMN --homePlmn false
4 Create an IMSI analysis for mobiles using the new PLMN.
Create a new IMSI analysis for the new PLMN digits.
Step example
Create an IMSI analysis for digits 24018 by using the visitor PLMN:
cmm imsiAnalysis create 24018 --plmnName VISITOR_PLMN --toA SPC -

-ni NA0 --spc 4
5 Modify CS/PS coordination activation in the PLMN set.
CS/PS coordination is executed with MOCN non-supported UE when the SGSN does not
have Gs interface and the CS/PS coordination is active in the PLMN and in the shared
RNC.
Step example
Activate CS/PS coordination in visitor PLMN:
cmm plmnParam modify VISITOR_PLMN --csPsCoord true

SGSN User Guide
6 Enable CS/PS coordination for RAU.
Normally, CS/PS coordination is done in the SGSN for the attach procedure only, but if
you wish, you may also perform it for the RAU procedure as well, by using the
rauCsPsCoordination parameter:
cmm prFile modify rauCsPsCoordination --status true
6.7.3.2 Deactivating 2G MOCN

To deactivate 2G MOCN (SG02212), deactivate CS/PS coordination functions, and
deactivate the feature.
Procedure
1 Set CS/PS coordination for a non-supporting MS to false.
cmm system modify config --csps2g false
2 Set the CS/PS coordination parameter to value false in the PLMN parameter set.
cmm plmnParam modify VISITOR_PLMN --csPsCoord false
3 Disable CS/PS coordination for RAU.
If enabled, disable the rauCsPsCoordination parameter:
cmm prFile modify rauCsPsCoordination --status false
cmm features modify 2gMocn --status false
6.7.3.3 Configuring 3G MOCN

3G MOCN (SG01179) requires feature activation, RNC parameter configuration, PLMN and
IMSI configuration, and CS/PS coordination activation.
Procedure
cmm features modify mocn --status true

SGSN User Guide
2 Configure radio network controller (RNC) parameters in SGSN.
In MOCN configuration the CN operator of a shared radio network is identified by a

PLMN ID. Create a configuration of a radio network controller (RNC) supporting the
MOCN for the SGSN's own PLMN.
Step example
Create rnc1 for SGSN's own PLMN (mcc 240, mnc 08):
cmm rnc create --rncId 100 --rncName rnc1 --toA SPC --ni IN0 --
spc 1203 --mcc 240 --mnc 08
Create two routing areas with different PLMNs. One with own PLMN (mcc 240, mnc 08)
and one with different (mcc 240, mnc 18):
cmm rait create --raitId 1 --rac 61 --lac 1161 --mcc 240 --mnc 08
cmm rait create --raitId 2 --rac 61 --lac 1161 --mcc 240 --mnc 18
Link these two routing areas to the previously created RNC:
cmm raitOfRnc create --raitId 1 --rncName rnc1
cmm raitOfRnc create --raitId 2 --rncName rnc1
3 Create a new PLMN parameter set.
You can create a PLMN level parameter set in the SGSN for new PLMN. It defines the
default parameters used for this PLMN.
Step example
Create visitor PLMN:
cmm plmnParam create --plmnParamId VISITOR_PLMN --homePlmn false
4 Create an IMSI analysis for mobiles using the new PLMN.
Create a new IMSI analysis for the new PLMN digits.
Step example
Create an IMSI analysis for digits 24018 by using the visitor PLMN:
cmm imsiAnalysis create 24018 --plmnName VISITOR_PLMN --toA SPC -

-ni NA0 --spc 4

SGSN User Guide
5 Modify CS/PS coordination activation in the PLMN set.
CS/PS coordination is executed with MOCN non-supported UE when the SGSN does not
have Gs interface and the CS/PS coordination is active in the PLMN and in the shared
RNC.
Step example
Activate CS/PS coordination in visitor PLMN:
cmm plmnParam modify VISITOR_PLMN --csPsCoord true
6 Enable CS/PS coordination for RAU.
Normally, CS/PS coordination is done in the SGSN for the attach procedure only, but if
you wish, you may also perform it for the RAU procedurel, by using the
rauCsPsCoordination parameter:
cmm prFile modify rauCsPsCoordination --status true
6.7.3.4 Deactivating 3G MOCN

To deactivate 3G MOCN (SG01179), unlink the PLMN from the shared RNC, deactivate
CS/PS (and CS/PS RAU) coordination, and deactivate the feature.
Procedure
1 Unlink the PLMN created with different mcc/mnc combination from the shared RNC.
Step example
cmm raitOfRnc delete 2~rnc1
2 Set the CS/PS coordination parameter to value false in the PLMN parameter set.
cmm plmnParam modify VISITOR_PLMN --csPsCoord false
3 Disable CS/PS coordination for RAU.
cmm prFile modify rauCsPsCoordination --status false
cmm features modify mocn --status false

SGSN User Guide
6.7.4 SGSN support for 2nd update PDP to PGW and S-

CDR generation at RAU after HO (Feature f50100-01):
feature summary
With this feature, the 3G MOCN SGSN sends a second PDP update to P-GW with the new
MCC/MNC values and a S-CDR generation at RAU after HO (handover).
Table 101: SGSN support for 2nd update PDP to P-GW and S-CDR generation at RAU after HO:
feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent 3G multi operator core network (3G MOCN) (SG01179)

features
Restrictions None
Conguration Command gParm, parameter mocnAccurateLoc

management
Counters None
Alarms None
6.8 Gs interface and interworking with MOCN (Feature

This feature provides the Gs interface which connects the databases of the MSC/VLR and
the SGSN. The feature implements the procedures that are used to coordinate the
location information of mobile stations (MS) that are simultaneously international mobile
subscriber identity (IMSI) attached to both GPRS and non-GPRS services.
Table 102: Gs interface and interworking with MOCN: feature summary

SGSN User Guide
Function Impact
Compliance None
Capacity None
Interworking/dependent • GPRS subscriber data management (Features SG01031, SG01246,

features f60210-02, f60210-03, f60210-04 and f60210-16)
• GPRS mobility management (Features SG01011, SG01104, SG01184,
SG01149, SG01254, SG01070)
• GPRS session management (Features SG01012 and SG02157)
Restrictions CS paging for an unknown subscriber within a dened period after an

SGSN restart is not supported.

SGSN User Guide
Function Impact
Conguration For the Gs interface, command serviceIP

management Command system, parameter gsMode
Command features, parameter csServices
Command prFile, parameter gsUpdateLocationThres
For VLR conguration, commands
• vlr
• sgsnLai
• laiOfVlr
For M3UA conguration, commands
• muaAssociationSet
• muaAssociation
• muaAssociationList
• muaLink
• muaRoute
• muaSignallingRoute
• muaSignallingRouteList
• muaLink
For SCCP and GT analysis, commands
• sccpSignallingPoint
• sccpSubsystem
• sccpSubsystemList
• gtAnalysisResult
• gtAnalysis
For Release 14lr reject causes conguration, command prFile,
parameter rel14LrRejectCauses. This prFile controls SGSN’s
compliance with Annex N in 3GPP TS 24.008 (Rel14). Specically:
• If GMM cause network failure (#17) was caused by MAP causes
"system failure", "data missing" or "unexpected data value" from the
HLR during location registration, the SGSN encodes the Redirection
Indication IE.
• If GMM cause network failure (#17) was not caused by MAP causes
"system failure", "data missing" or "unexpected data value" from the
HLR during location registration, the SGSN encodes the Redirection
Completed IE.
See Integrating CMM for Gs interface conguration instructions.

SGSN User Guide
Function Impact
Counters • M046C000 / TOTAL RECEIVED GS SIGNALING MESSAGES

• M046C001 / TOTAL SENT GS SIGNALING MESSAGES
• M046C002 / NBR OF GS DOWNLINK TUNNEL REQ
• M046C003 / NBR OF SUCC GS DOWNLINK TUNNEL REQ
• M046C004 / NBR OF GS UPLINK TUNNEL REQ
• M046C005 / NBR OF SUCC GS UPLINK TUNNEL REQ
• M046C006 / NBR OF GS IMSI GPRS DETACH EXPLICIT
• M046C007 / NBR OF SUCC GS IMSI GPRS DETACH EXPLICIT
• M046C008 / NBR OF GS IMSI NON GPRS DETACH EXPLICIT
• M046C009 / NBR OF SUCC GS IMSI NON GPRS DETACH EXPLICIT
• M046C010 / NBR OF GS IMSI NON GPRS DETACH IMPLICIT
• M046C011 / NBR OF SUCC GS IMSI NON GPRS DETACH IMPLICIT
• M046C012 / NBR OF GS VLR RESET
• M046C013 / NBR OF GS SGSN RESET
• M046C014 / NBR OF GS UNKNOWN MSG TYPE
• M046C015 / NBR OF GS UNKNOWN IE
• M046C016 / NBR OF GS MISSING MANDATORY IE
• M046C017 / NBR OF GS MESSAGE TOO SHORT
• M046C018 / NBR OF GS MM INFO
• M046C019 / NBR OF SUCC GS MM INFO
• M046C020 / NBR OF GS MS INFO
• M046C021 / NBR OF SUCC GS MS INFO
• M046C022 / NBR OF GS ALERT PROCEDURES
• M046C023 / NBR OF GS MOBILE STATUS
• M046C024 / NBR OF GS LOCATION UPDATE ATTEMPTS
• M046C025 / NBR OF GS LOCATION UPDATE FAIL ON MSC
• M046C026 / NBR OF GS LOCATION UPDATE FAIL DUE TO SGSN
• M046C027 / NBR OF GS PAGING REQUESTS
• M046C028 / NBR OF SUCC GS PAGING
• M046C029 / NBR OF PAGING REJECTS DUE TO UNKNOWN IMSI
• M046C030 / NBR OF PAGING REJECTS DUE TO IMSI DETACHED GPRS
• M046C031 / NBR OF PAGING REJECTS DUE TO IMSI DETACHED NON-
GPRS
• M046C032 / NBR OF PAGING REJECTS DUE TO IMPL DETACHED NON-
GPRS
• M046C033 / NBR OF PAGING REJ DUE TO UE UNREACHABLE
• M046C034 / NBR OF PAGING REJ DUE TO OTHER
• M046C035 / NBR OF DL TOM MESSAGES
Alarms None

SGSN User Guide
6.9 SGSN support for multiple MSC/VLRs per LAC (Feature

This feature adds support for provisioning up to 32 different MSC/VLRs per location area
(LA).
Table 103: SGSN support for multiple MSC/VLRs per LAC: feature summary
Function Impact
Compliance 3GPP TS 23.236, Intra-domain connection of Radio Access Network

(RAN) nodes to multiple Core Network (CN) nodes, Release 5
Capacity Up to 32 different MSC/VLRs per LAI can be provisioned.
Required features Gs interface and interworking with MOCN (Feature f50101-01)
features
Restrictions None
Conguration Command cmm laiOfVlr

management See Integrating CMM for Gs interface conguration instructions.
Counters None
Alarms None
6.9.1 Configuring multiple MSC/VLRs per LAC

Use the laiOfVlr command to configure multiple MSC/VLRs per location area code
(LAC).
Before you start
Ensure that the Gs interface (Gs mode and Cs services) is configured. For more details, see
Integrating CMM.
Procedure
1 Create multiple MSC/VLR records per sgsnLAI

SGSN User Guide
cmm laiOfVlr create --mcc <digits> --mnc <digits> --lac <integer>

--vlrId <integer>
Note:
The SGSN LAI and VLR-related records must first be configured through sgsnLai
and vlr commands.
Step example
cmm laiOfVlr create --mcc 460 --mnc 02 --lac 4 --vlrId 1
Step example
Step example
Step example
6.10 SGSN support for omitting least significant MSIN

digit fields used in GT analysis when supported length
limit is exceeded (Feature f52077-01): feature summary
With this feature, the SGSN supports the manipulation of global title translations (GTT)
where the intermediate result may exceed the maximum length of the mobile global title
(MGT) allowed for the numbering plan.

SGSN User Guide
Table 104: SGSN support for omitting least significant MSIN digit fields used in GT analysis
when supported length limit is exceeded: feature summary
Function Impact
Compliance None
Capacity None
Required features CMM support for SS7 Stack for Cloud SGSN (Feature
f60210-29), which introduced global title (GT) analysis-related
functionality.
features
Restrictions None
Conguration management Command cmm imsiAnalysis
Charging None
Counters None
Alarms None

SGSN User Guide
7. Operational control and optimization
7.1 SGSN charging (Features SG01015, SG01189, SG02193,

SG01118 and f60210-18)
The SGSN charging feature (f60210-18) consists of legacy features SG01015, SG01189,
SG02193 and SG01118. With this feature, SGSN can generate charging data (S-CDRs) to
be used for end user billing.
SGSN charging supports S-CDRs with 3GPP ASN.1 format (known as charging release level 5
in SGSN ATCA), and Bp interface (SFTP) for transferring the S-CDRs to billing system.
The charging functionality can be divided to charging data collection (sgsnS4S program
block) and encoding (sgsnA4S program block) performed in PAPS VMs, and consuming CDR
batch and writing CDRs into disk files (sgsnCGF) on the NECC VM.
Charging data collection functionality in PAPS

Charging data collection functionality in PAPS VM is done by sgsnS4S program block.
Charging data for S-CDR generation is stored both in PAPS VM inside sgsnS4S program block
memory area and also in subscriber database. Charging data collection functionality consists
mainly of following areas:
normal S-CDR generation based on PDP context activation and deactivation
intermediate S-CDR generation based on triggers (volume, data, t24 trigger)
intermediate S-CDR generation based on container usage (container change due to QoS
modification, tariff change, tunnel type change)
intermediate S-CDR generation based on Inter system handovers between 2G (Gb) and
3G (Iu, I-HSPA)
S-CDR generation with management intervention (manual CDR generation, manual CDR
closure, direction -parameter modification, configurable charging parameter
modification, purge functionality)
abnormal S-CDR generation in case of PAPS VM restart
S-CDR statistics data generation
handling of tariff change so that it is visible via containers in S-CDRs

SGSN User Guide
Note:
All generated S-CDRs are sent to sgsnA4S in same PAPS VM for ASN.1 encoding. If own
PAPS VM's sgsnA4S is not responding to alive requests, a search is performed to be
able to send the S-CDRs to some other PAPS VM's sgsnA4S.
Charging data encoding functionality in PAPS

Charging data encoding functionality in PAPS VM is done by sgsnA4S program block.
S-CDR encoding to 3GPP ASN.1 format according to definitions
sending encoded S-CDR data over Kafka pipe to NECC
Note:
One PAPS VM's sgsnA4S can handle also S-CDRs sent by another PAPS VM's sgsnS4S if
needed.
CDR consuming and CDR file population functionality in NECC

The CDR files are stored in /data-charging/cdr folder. The file extension is .DAT, for
example, CF00001.DAT (or CF0001.DAT when number of digits in filename is set to 4).
Data files are controlled with control files TTSCOF and TTTCOF.
The TTSCOF contains information about the state, time stamp and save mode of the data
files. The TTTCOF contains a time stamp. The data files can be in four different states. The
states are explained below:
OPEN Data is being written into the le. Only one le at a time can be in
this state
FULL The le is full and ready to be transferred to a postprocessing system

outside the exchange.
TRANSFERRED The le has been transferred to a postprocessing system and can be
used again
UNUSABLE The le cannot be used, because there is not enough space on the
hard disk to create it.

SGSN User Guide
When CGF writes data into a data file, the state of the data file is OPEN.
When the data file becomes full, CGF changes the state to FULL. FULL means that the
contents in the data file can be transferred to the postprocessing system. When the
contents of the data file have been transferred to the postprocessing system, the CGF
process changes its state to TRANSFERRED. After this the file, can be used again.
CGF puts a data file to the UNUSABLE state when data file creation may fail or it is
corrupted. The rotation of the file states is presented in the figure.
Figure 1: Rotation of data file states
CGF updates TTSCOF and the postprocessing system, updates TTTCOF. At intervals, CGF
checks TTTCOF and updates TTSCOF.
Note:
Postprocessing system should not delete TTTCOF file or change the file's permissions.
Disk capacity
Disk space is provided to SGSN charging by the operator. The default value is 50 GB and may
be extended up to 100 GB through the HEAT/HOT template. 98% of this disk space is used
for the data. The remaining 2% is used to have a safety space.
7.1.1 Configuring SGSN charging

The following CLI commands are used for configuring and controlling SGSN charging
functionality: chargingParams, cdr, cdrFiles, chargingChangeGroup,
chargingSpecialday, and chargingWeekday.
Before you start
In addition, the following prFile parameters can be used to control charging:

SGSN User Guide
Table 105: Charging-related prFile parameters
Parameter Default Description
twoByteChargingChar 0 (4 bit Support for two-byte charging character value in

CC) SGSN
This parameter is used to dene the support for two-
byte charging characteristics value in SGSN, received
from HLR. It is congurable to use four-bit (0), one-
byte (1), or two-byte (2) charging characteristics in
SGSN.
See Conguring charging characteristics
forcefulCtxRem false Forceful removal of PDP contexts from the GGSN

With this parameter, the SGSN will in some abnormal
cases send a delete PDP context request to the GGSN
in order to remove hanging contexts.
originalCcInCdr false Original charging characteristics in CDR

(not in This parameter can be used for sending the original
use) charging characteristics received in mobility
management/session management/SMS messages in
the corresponding CDRs generated by the SGSN.
cgfDualStackSupport false SGSN dual stack PDP context support (3GPP rel 9,
Gn/Gp) for Charging Gateway
This parameter determines whether the Charging
Gateway is capable of supporting dual stack PDP
contexts or not. By default, it is not.
7.1.1.1 Configuring charging parameters

Charging parameters are held in a charging parameter set. The parameters are used to
activate and disable SGSN charging, configure charging triggers, and purge or discard S-
CDRs.
Purpose
Use the chargingParams command group to create, modify, delete or interrogate a
charging parameter set to be used by the charging data collection functionality in PAPS.
Note that there can be only one charging parameter set in use.
Procedure
1 Check if a charging parameter set exists.

SGSN User Guide
cmm chargingParams show --chargingParamsId 1
2 Output the current charging parameter values.
If a charging parameter set exists, use the chargingParams show command to

output current parameter values.
Step example
+-------------------+---------------+
| Field | Value |
+-------------------+---------------+
| chargingParams | 1 |
| chargingParamsId* | 1 |
| direction | bp |
| flatRate | on |
| time | 10-00 |
| vol2g | 18000 |
| minVol2g | 6000 |
| vol3g | 90000 |
| minVol3g | 30000 |
| t24h | on |
| purgeCDRs | 2day |
| ctmNorm | both |
| ttcMode | blockingOnCdr |
| ttcTso | on |
| cdrCreateGb | all |
| cdrCreateIu | all |
| cdrCreateIhspa | all |
| cdrCreateDt | on |
| sCdrDiscard | on |
+-------------------+---------------+
3 If there is no charging parameter set, create it.
cmm chargingParams create --chargingParamsId 1
4 Modify the charging parameter set.
Use the chargingParams modify command to modify charging data collection

SGSN User Guide
related charging parameters under this charging parameters set.
Note that the charging parameters related to the Configurable charging feature are
described in Provisioning configurable charging. The parameters are ttcMode, ttcTso,
cdrCreateGb, cdrCreateIu, cdrCreateIhspa, and cdrCreateDt .
Note:
S-CDRs for server based prepaid PDPs use the same triggers and CDR opening
rules as the normal users' S-CDRs. Triggers time, vol2G, minVol2G, vol3G and
minVol3G are common parameters for both normal and prepaid S-CDRs.
4.1 Start charging data collection (direction).
Modifying the value of parameter direction from off tobp will start charging
data collection and charging data encoding functionality in PAPS VM(s) and also
CDR file storing functionality in NECC.
You can modify the other necessary parameters, such as triggers, before
activating the charging so that they are in use immediately after the charging
functionality is activated.
The direction parameter controls if charging data collection is active or not.

Value off means charging data collection is not active, value bp means charging
data collection is active. When the parameter value is modified from off to bp,
charging data collection functionality wakes up and starts collecting charging
data and generating S-CDRs. When the parameter value is modified from bp to
off, all the current open S-CDRs are closed with closing cause management
intervention, and stored by default to CDR files existing on NECC disk. Note that
it is also possible to prevent the S-CDR storage in this case by using parameter
sCdrDiscard. When all the S-CDRs have been closed, charging data collection
functionality enters into sleep mode, and can be woken up again by changing the
direction parameter value from off to bp.
Notice 00260 ScdrUpdateTaskStatus is written in PAPS by the sgsnS4S

(073D) program block when S-CDR handling due to command execution starts,
and again when S-CDR handling due to command execution ends. This alarm
writing is PAPS-specific and may occur with different timestamps in different
PAPS VMs as every PAPS handles the S-CDR closure individually.
Step example
To start collecting charging data and generating S-CDRs, modify value of the

SGSN User Guide
direction parameter from off to bp:
cmm chargingParams modify --chargingParamsId 1 --direction

bp
To stop collecting charging data, modify value of the direction parameter

from bp to off:

off
When the direction parameter is set to off, the value of the sCdrDiscard
parameter determines whether the generated S-CDRs are stored on NECC disk
(off) or discarded (on).
4.2 Configure flat rate S-CDR generation (flatRate).
The flatRate parameter is used to define if flat rate S-CDRs are generated or
not. Values: on, off.
Step example
Enable flat rate S-CDR generation: cmm chargingParams modify --
chargingParamsId 1 --flatRate on
4.3 Set the S-CDR time trigger (time).
The time parameter is used for setting the S-CDR time trigger. The time trigger
runs individually for each open S-CDR, meaning that when a certain S-CDR has
been open for 4 hours (default value for time trigger as an example),
intermediate S-CDR with closing cause time limit will be generated if the
corresponding minVol trigger (minVol2g for 2G, minVol3g for 3G) trigger
value is also met, and no intermediate S-CDRs have been generated for this
same PDP context during the 4 hour period. If the minVol2g trigger is set to
3000 (default value as an example), there has to be that amount of data volume
in the 2G S-CDR for it to be generated. Note that the minVol trigger can be also
set to value 0, meaning intermediate S-CDR will be generated after 4 hours also
without any data volumes. This functionality takes place when the time trigger is
running in normal mode. See the description of parameter ctmNorm for the
continuous trigger mode.
Step example
Modify time trigger to 10-00: intermediate S-CDRs are generated with closing

SGSN User Guide
cause time limit with 10 hours interval, assuming there is minimum of 3000 kB of
data volume to be reported in the S-CDR.
cmm chargingParams modify --chargingParamsId 1 --time 10-00
Step example
With time trigger set to 10-00, and minVol2g set to 3000: intermediate S-
CDRs are generated with closing cause time limit with 10 hours interval,
assuming there is minimum of 3000 kB of data volume to be reported in the S-
CDR.
Step example
With time trigger set to 10-00, and minVol2g set to 0: intermediate S-CDRs
are generated with closing cause time limit with 10 hours interval.
4.4 Set the 2G S-CDR volume trigger (vol2G).
The vol2G parameter is used for setting the 2G S-CDR volume trigger. The
volume trigger runs individually for each open S-CDR, meaning when a certain S-
CDR has received the data volume amount corresponding to this parameter
value, an intermediate S-CDR will be created with closing cause volume limit,
assuming no intermediate S-CDRs have been generated during the same period.
This functionality takes place when vol2G trigger is running in normal mode.
See the description of parameter ctmNorm for the continuous trigger mode.
Note:
If minVol2g has been set to something else than 0, then the vol2G value
needs to be divisible with minVol2g value. An example (with default
values): minVol2G 3000 kB, vol2G 12000 kB.
When the vol2G value is modified, the change will take effect only for new
2G S-CDRs opened after the value modification.
Step example
Modify vol2G trigger to be 18000, with minVol2g set to 3000 (that is, 18000 is
divisible by 3000): intermediate 2G S-CDR is generated with closing cause
volume limit after 18000 kB of data transfer (including both UL and DL data).
cmm chargingParams modify --chargingParamsId 1 --vol2g 18000

SGSN User Guide
4.5 Set the minimum amount of data for triggering intermediate 2G S-CDR
generation (minVol2G).
The minVol2G parameter is an additional parameter related to the time trigger

functionality. With this parameter, you can define the minimum amount of data
for triggering intermediate 2G S-CDR generation with closing cause time limit.
The parameter can have value 0 which means intermediate S-CDRs without any
datavolume can be generated due to time trigger expiration. However, you are
recommended to use some other value than 0 to limit the S-CDR generation in
the system.
Note:
When minVol2G value is modified, the change will take effect only for new
Step example
Modify minVol2g to value 6000, with time trigger set to 10-00: an
intermediate S-CDR will be created after 10 hours if there has been 6000 kB of
data transfer (including both UL and DL data).
cmm chargingParams modify --chargingParamsId 1 --minVol2g

6000
4.6 Set the 3G S-CDR volume trigger (vol3G).
The vol3G parameter is used for setting the 3G S-CDR volume trigger. The
volume trigger runs individually for each open S-CDR, meaning when a certain S-
CDR has received the data volume amount corresponding to this parameter
value, an intermediate S-CDR will be created with closing cause volume limit,
assuming no intermediate S-CDRs have been generated during this same period.
This functionality takes place when the vol3G trigger is running in normal mode.
See the description of parameter ctmNorm for the continuous trigger mode.

SGSN User Guide
Note:
If minVol3g has been set to something else than 0, the vol3G value
needs to be divisible with minVol3g value. An example (with default
values): minVol3G 15000 kB, vol3G 60000 kB.
When the vol3G value is modified, the change will take effect only for new
Step example
Modify vol3G trigger to be 90000, with minVol3g set to 15000 (that is, 90000
is divisible by 15000): intermediate 3G S-CDR is generated with closing cause
volume limit after 90000 kB of data transfer (including both UL and DL data).
cmm chargingParams modify --chargingParamsId 1 --vol3g 90000
4.7 Set the minimum amount of data for triggering intermediate 3G S-CDR
generation (minVol3G).
The minVol3G parameter is an additional parameter related to time trigger

functionality. With this parameter, you can define the minimum amount of data
for triggering intermediate 3G S-CDR generation with closing cause time limit.
The parameter can have value 0, meaning intermediate S-CDRs without any
datavolume can be generated due to time trigger expiration. However, you are
recommended to use some other value than 0 to limit the S-CDR generation in
the system.
Note:
When the minVol3G value is modified, the change will take effect only for
new 3G S-CDRs opened after the value modification.
Step example
Modify minVol3g to value 30000, with time trigger set to 10-00: an
intermediate S-CDR will be created after 10 hours if there has been 30000 kB of
data transfer (including both UL and DL data).
cmm chargingParams modify --chargingParamsId 1 --minVol3g

30000

SGSN User Guide
4.8 Set the 24 hour trigger (t24h).
The t24h parameter is used for setting the 24 hour trigger functionality. When
this parameter is on, each S-CDR open for 24 hours without any intermediate S-
CDR generated will generate an intermediate S-CDR with closing cause time limit.
This functionality is off by default.
Step example
Set the t24h trigger on: intermediate S-CDR with closing cause time limit is
generated if no S-CDRs is generated for this specific PDP context since the last
24 hours.
cmm chargingParams modify --chargingParamsId 1 --t24h on
4.9 Configure purge (purgeCdrs).
The purgeCdrs parameter is used for closing and sending the S-CDRs that have
been open a long time without any updates or modifications, to release the
resources. This functionality is off by default. To enable purge, use values 1day
to 7day
Note:
If the t24h trigger is in use, it will basically disable the purge functionality,
as the S-CDRs without any other updates will be updated due to
intermediate S-CDR generation every 24 hours. So when using purgeCdrs
with value other than off it is recommended to set the t24h value to off
to allow the purge mechanism to do the final S-CDR closure in the system.
Step example
Set purgeCDRs to value 2day: S-CDR will be generated with closing cause
management intervention after 48 hours if there are no updates in the S-CDR
data during this period.
cmm chargingParams modify --chargingParamsId 1 --purgeCDRs

2day
4.10 Set the CDR trigger mode (ctmNorm).
The ctmNorm parameter is used for setting the CDR trigger mode, affecting
either the time trigger or the volume trigger or both. When the continuous

SGSN User Guide
trigger mode has been set, it will affect both 2G and 3G S-CDR generation.
Continuous trigger mode means that a trigger running in continuous mode does
not care about any other intermediate S-CDR generation but expires always as
defined.
For example, if the time trigger is running in continuous mode, an intermediate

S-CDR will be generated with closing cause time limit exactly within the interval
specified with the time parameter, no matter if any data volume is transferred
or not. If the volume trigger is running in continuous mode, an intermediate S-
CDR will always be generated with closing cause volume limit when the
corresponding data volume amount (including both UL and DL data) has been
met.
Note:
Using continuous trigger mode will noticeably increase the intermediate S-

CDR amount generated by the system.
Step example
Modify time trigger to be in continuous mode: cmm chargingParams modify
--chargingParamsId 1 --ctmNorm timeTr
With the values below, intermediate S-CDR is generated always when 10 hours
has passed, no matter how much data has been transferred or if any other
intermediate S-CDRs were generated during this 10 hour period.

SGSN User Guide
+-------------------+----------------+
| Field | Value |
+-------------------+----------------+
| direction | off |
| flatRate | on |
| time | 10-00 |
| vol2g | 18000 |
| minVol2g | 6000 |
| vol3g | 90000 |
| minVol3g | 30000 |
| t24h | on |
| ctmNorm | timeTr |
| ttcMode | blockingOnCont |
| ttcTso | off |
| cdrCreateDt | off |
+-------------------+----------------+
Step example
Modify volume trigger to be in continuous mode: cmm chargingParams
modify --chargingParamsId 1 --ctmNorm volumeTr
With the values below, an intermediate S-CDR with closing cause volume limit will
be always created when 18000 kB (2G) or 90000 kB (3G) of data has been
transferred (containing both UL and DL data), no matter if any other
intermediate S-CDRs have been generated for this PDP context during this
period.

SGSN User Guide
+-------------------+----------------+
| Field | Value |
+-------------------+----------------+
| direction | off |
| flatRate | on |
| time | 10-00 |
| vol2g | 18000 |
| minVol2g | 6000 |
| vol3g | 90000 |
| minVol3g | 30000 |
| t24h | on |
| ctmNorm | volumeTr |
| ttcTso | off |
+-------------------+----------------+
Step example
Modify both time and volume trigger to run in continuous mode: cmm
chargingParams modify --chargingParamsId 1 --ctmNorm both
With the values below, an intermediate S-CDR with closing cause time limit will be
always created when 10 hours has passed, and also with closing cause volume
limit after 18000 kB of data transfer for 2G and after 90000 kB of data transfer
for 3G (both UL and DL included), no matter if any other intermediate S-CDRs
have been generated during these periods.

SGSN User Guide
+-------------------+----------------+
| Field | Value |
+-------------------+----------------+
| direction | off |
| flatRate | on |
| time | 10-00 |
| vol2g | 18000 |
| minVol2g | 6000 |
| vol3g | 90000 |
| minVol3g | 30000 |
| t24h | on |
| ctmNorm | both |
| ttcTso | off |
+-------------------+----------------+
4.11 Enable or disable discarding S-CDRs without storing (sCdrDiscard).
The sCdrDiscard parameter is used to control if generated S-CDRs for certain

scenarios are to be stored on NECC disk or discarded without storing. The
parameter is used when modifying parameter direction from bp to off, and
also when modifying Configurable charging related parameters (cdrCreateGb,
cdrCreateIu, cdrCreateIhspa,cdrCreateDt) so that the corresponding S-
CDRs are closed.
Note:
This parameter value needs to be set before executing the actual

parameter modification command that will cause S-CDRs to be generated.

SGSN User Guide
Step example
Modify sCdrDiscard to on: S-CDRs will be closed and removed, but not stored
to disk files in NECC, when executing, for example, direction parameter
modification from bp to off.
cmm chargingParams modify --chargingParamsId 1 --sCdrDiscard

on
5 When needed, delete charging parameter set.
Use the chargingParams delete command to delete charging parameter set used
by the charging data collection functionality in PAPS. Note that using this command will
stop the possible charging data collection in PAPS, and all the open S-CDRs will be
closed and sent with closing cause management intervention.
Step example
cmm chargingParams delete --chargingParamsId 1
7.1.1.2 Configuring CDRs

Use the cdr command group to close and send open S-CDRs, output S-CDR amounts,
generate a subscriber's S-CDRs, and output S-CDRs of a subscriber.
Before you start
Alarms related to command cdr close:

Notice 00260 ScdrUpdateTaskStatus is written in PAPS by sgsnS4S program block
(073D) when S-CDR handling due to command execution starts, and again when S-CDR
handling due to command execution ends.
Alarm 014048 ChaOutOfUse is set when S-CDR handling due to command execution
has ended.
These alarm writings are PAPS-specific and may occur with different timestamps in different
PAPS as every PAPS handles the S-CDR closure individually.

SGSN User Guide
Procedure
1 Close and send open S-CDRs.
Use the cdr close command to close and send all the open S-CDRs in the system,
using closing cause management intervention. When all the S-CDRs have been closed
and sent, charging data collection functionality in PAPS enters offline state. This
command is used prior to SW upgrade to close the old S-CDRs in the system when still
on the old software level.
Step example
To generate all the S-CDRs in the system: cmm cdr close --transferType
offline
2 Close the current charging file.
Use the cdr close command to close the current open charging file in the system.
When all the S-CDRs have been closed and sent, the system will close the current
charging file that contains the S-CDRs and it will be marked as full. When S-CDRs start
again, a new charging file will be created and S-CDRs will be stored inside.
Step example
To generate all the S-CDRs in the system: cmm cdr close --transferType
currentFile
3 Output current S-CDR amounts.
Use the cdr count command to output the current S-CDR amounts. The command
can be used to
print all the S-CDR amounts by using access = ALL, sub = ALL
output only the requested S-CDR amounts by using access type (access =
GB/IU/IHSPA/DTIU/DTIHSPA) and/or sub type (sub = HOME/ROAM.
Step example
To output all the S-CDR amounts: cmm cdr count --access ALL --sub ALL

SGSN User Guide
+----------+-----------------------------+
| Field | Value |
+----------+-----------------------------+
| OPENCDRs | |
| | Access: ALL |
| | Home subscribers S-CDRs: |
| | - IU: 5 |
| | - GB: 9 |
| | - IHSPA: 4 |
| | - DTIU: 0 |
| | - DTIHSPA: 0 |
| | Roaming subscribers S-CDRs: |
| | - IU: 2 |
| | - GB: 1 |
| | - IHSPA: 0 |
| | - DTIU: 0 |
| | - DTIHSPA: 0 |
| | Total S-CDRs: 21 |
+----------+-----------------------------+
Step example
To output S-CDR amount of home Iu subscribers' PDPs only: cmm cdr count --
access IU --sub HOME
+----------+--------------------------+
| Field | Value |
+----------+--------------------------+
| OPENCDRs | |
| | Access: IU |
| | - IU: 5 |
+----------+--------------------------+
Use the cmm cdrPapsCount list command to output the current S-CDR amounts
per PAPS.

SGSN User Guide
Step example
cmm cdrPapsCount list
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
|papsId|homeIu|homeGb|homeIhspa|homeDtIu|homeDtIhspa|roamIu|roamGb|roamIhspa|roamDtIu|roamD
tIhspa|total|
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
| 0 | 4 | 7 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0
| 12 |
| 1 | 1 | 2 | 4 | 0 | 0 | 1 | 1 | 0 | 0 | 0
| 9 |
| All | 5 | 9 | 4 | 0 | 0 | 2 | 1 | 0 | 0 | 0
| 21 |
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
4 Generate one subscriber's S-CDRs.
Use the cdr generate command to generate a subscriber's S-CDRs. If the command
is given with only imsi as parameter, it will generate all open S-CDRs for that
subscriber. If the command is given with imsi and nsapi parameters, the specific S-
CDR will be generated. The S-CDR will be generated with closing cause management
intervention, and it is a final (not intermediate) S-CDR, that is, the last S-CDR in this
chain for this specific PDP context.
Step example
To generate all the S-CDRs for a subscriber: cmm cdr generate --imsi
123456789
Step example
To generate only this specific S-CDR for this subscriber: cmm cdr generate --imsi
123456789 --nsapi 5
5 Output S-CDRs for a specific subscriber.
Use the cdr show command to output the S-CDR data for specific subscriber.

SGSN User Guide
Step example
cmm cdr show --imsi 123456789
7.1.1.3 Configuring CDR files

Use the cdrFiles command group to create, modify, delete and interrogate CDR files.
Purpose
Note:
After SGSN charging is activated, the cdrFiles values should be changed only
with the sgsnCGF process disabled. Also empty the /data-charging/cdr folder.
The new values are in use after sgsnCGF is enabled again.
If the provided disk space is not adequate according to charging configuration, the
CDR file number will be internally adjusted to the appropriate value.

SGSN User Guide
Table 106: Parameters of cdrFiles
cdrFilesId Id for cdrFile entry: set it to 1
sizePerFile The size per CDR le (KB) to use. Default: 5120
amountOfFiles The total amount of CDR les/indexes to use (0...68000). The

resulting value when multiplied to the sizePerFile
parameter should be below 98% of the available charging disk
space. Default: 20000
compression Set this to true when CDR les should be compressed.

Default: false.
Note:
If compression is enabled,amountOfFiles and

sizePerFile are calculated from the process.
sizePerFile depends on the compress ratio and the
values used can be different from the value displayed in the
conguration.
noOfDigitsInFileName The parameter denes the number of digits in the lename of

CDR le to use (by default, 5).
Note:
If you change the value to 4, you must also change the

amount of CDR les where the CDRs are stored
(amountOfFiles).
• If noOfDigitsInFileName is 5, the maximum number
of les is 68000.
• If noOfDigitsInFileName is 4, the maximum number
of les is 9999.
overwrite When there is no available/free CDR le index to use, overwrite

could be an option. Default: false
useControlfiles Possibility to select whether the CDR les are transferred

towards the billing domain in a controlled way. Default: true
Procedure
1 Before changing the values, disable sgsnCGF.

SGSN User Guide
Step example
pcs resource disable sgsnCGF
2 Delete /data-charging/cdr folder or content.
3 Configure CDR files.
Step example
cmm cdrFiles modify 1 --amountOfFiles 9000 --sizePerFile 5120 --
noOfDigitsInFileName 4
Step result
+----------------------+--------+
| Field | Value |
+----------------------+--------+
| cdrFiles | 1 |
| cdrFilesId | 1 |
| sizePerFile | 5120 |
| amountOfFiles | 9000 |
| compression | false |
| overwrite | false |
| useControlFiles | true |
| noOfDigitsInFileName | 4 |
+----------------------+--------+
4 Enable sgsnCGF.
Step example
pcs resource enable sgsnCGF
7.1.1.4 Configuring tariff functionality

Tariff handling offers a way to manage the tariffs in the SGSN. Command groups for tariff
handling are chargingChangeGroup, chargingWeekday and chargingSpecialday.
Purpose
In the tariff configuration, every weekday has a charging change group and every charging

SGSN User Guide
change group has change times and change indexes. Then, for every day and time, the
charging gateway function (CGF) calculates charge indexes.
Special days can be configured to change the way CGF calculates tariff indexes. Special days
have their own charging change groups, and charge rate indexes are calculated from the
special day charging change group instead of weekdays.
Procedure
1 Configure charging change group.
Use the chargingChangeGroup command group to create, modify, delete and

interrogate charging change group.
Table 107: Parameters of chargingChangeGroup
chargingChangeGrou Index, values 1 to 50. Values are taken automatically with the
pId creation of a new change group.
changeTime The change time of the charge rate (hours-minutes) within a day.
The character & is permissible. A maximum of seven change times
may be dened. The change times must be given in a chronological
order.
This parameter is optional. The default value is that no change time
is given. The values 00:00 and 24:00 (at the beginning and at the
end of the change time string) are implied and should not be given.
Change times must have a difference between them at least one
hour.
chargeRateIndex Denes the charge rates that are used within a day. The character
& is permissible. This parameter is given as a decimal number with
values 1 to 4. A maximum of eight charge rate/tariff indices may be
dened (when change time contains 7 different times) and there
must be one extra index dened compared to the number of
charge rate change times (within the change time string). The
indices must be given in a chronological order in comparison to the
change time. This parameter is obligatory and at least one value
must be given (if no change time is given, this value is valid from
00:00 to 24:00).
2 Configure charging weekday.
Use the chargingWeekday command group to create, modify and interrogate

charging weekday configuration.
Parameters

SGSN User Guide
weekday All weekdays (MON, TUE, WED, THU, FRI, SAT, SUN congured with
changeGroupIndex 0.
changeGroupIndex Permitted values: 0 to 50. The default value is 0.

When this is has zero value, charging gateway function (CGF)
understands that this is not congured at all.
Note:
After the tariff configuration is given for the first time, the sgsnCGF process
needs a restart. After that, values can be modified on the fly.
Every changeGroupIndex used in weekday should be first configured in
charging change group parameters.
3 Configure charging special day.
Optionally, use the chargingSpecialday command group to create, modify, delete

and interrogate charging special day configuration.
Parameters
date Date of special day
changeGroupIndex changeGroupIndex of special day. Values 1 to 50.
Example: Configuring tariff functionality

1. Add entries using the chargingChangeGroup command:
cmm chargingChangeGroup create --chargingChangeGroupId 1 --
changeTime "16-00" --chargeRateIndex "4&1"
cmm chargingChangeGroup create --chargingChangeGroupId 2 --
changeTime "12-00&18-00" --chargeRateIndex "2&4&1"
2. Add special day:
cmm chargingSpecialday create --date "2017-12-25" --
changeGroupIndex 1
3. Change a changeGroupIndex of a day:

SGSN User Guide
cmm chargingWeekday modify --weekday WED --changeGroupIndex 2

4. When the first configuration is given, the sgsnCGF process needs a restart.
7.1.1.5 Configuring charging characteristics

Using the prFile parameter twoByteChargingChar, you can extend the Charging
Characteristics (CC) value to configure 4 bit, 1 byte or 2 byte CC. The masking of CC will
be performed accordingly to retrieve the CC.
▪ Configure the CC value.
Use the twoByteChargingChar parameter to define the support for two-byte

charging characteristics value in SGSN, received from HLR. It is configurable to use four-
bit, one-byte, or twobyte charging characteristics in SGSN. The following values can be
configured to interpret the CC type:
0 – Indicates existing 4 bit CC will be used (default).
1 – Indicates 1 byte CC will be used.
2 – Indicates 2 byte CC will be used.
Step example
cmm prFile modify twoByteChargingChar --twoByteChargingChar 2
Step result
+---------------------+-------------------------------------------------------+
| Field | Value |
+---------------------+-------------------------------------------------------+
| prFile | twoByteChargingChar |
| status | false |
| parameter | Support for two-byte charging character value in SGSN |
| twoByteChargingChar | 2 |
+---------------------+-------------------------------------------------------+
7.1.1.6 Configuring IMEISV in CDR

This feature (SG01088) enables the SGSN to request the MS to include the IMEI and SVN

SGSN User Guide
in the authentication and ciphering or identification response messages, and to add this
information to the CDR.
Purpose
The SGSN asks for the IMEISV from the mobile station when the GTP information sending
(feature SG01082) and/or the IMEISV in CDR (feature SG01088) is active.
▪ Activate IMEISV in CDR.
cmm features modify imeisvInCdr --status true
7.1.1.7 Disabling SGSN charging

To disable SGSN charging, use the direction parameter in the charging parameter set.
Procedure
1 Enable discarding of S-CDRs generated due to feature deactivation.
Modify parameter sCdrDiscard to on if S-CDRs generated due to feature

deactivation are not to be stored to NECC disk.
cmm chargingParams modify --chargingParamsId 1 --sCdrDiscard on
2 Disable SGSN charging.
Modify the direction parameter to off to deactivate the feature. This will cause all
the open S-CDRs to be closed.
cmm chargingParams modify --chargingParamsId 1 --direction off
7.1.2 SGSN charging (Features SG01015, SG01189,

SG02193, SG01118, and f60210-18): feature summary
The SGSN charging feature contains charging and pre-billing functions within the SGSN in
accordance with the 3GPP recommendations.
Table 108: SGSN charging (Features SG01015, SG01189, SG02193, SG01118, and

SGSN User Guide
Function Impact
Capacity See System capacity in Product Description.
Interworking/dependent • Direct tunnel and smart device direct tunnel signaling optimization
features (Features SG02017 and SG01221)
• Congurable charging (Features SG01147, SG01132 and f60210-18)
Restrictions Specic parameters not available for server-based prepaid PDPs S-

CDRs, S-CDRs for server- based prepaid PDPs are using the same
triggers and CDR opening rules as the normal users S-CDRs.
Supported CDR format is 3GPP ASN.1
Only supported CDR type is S-CDR.
Conguration Commands chargingParams, cdr, cdrFiles,

management chargingChangeGroup, chargingSpecialday,
chargingWeekday, cdrPapsCount
Command prFile, parameters twoByteChargingChar,
forcefulCtxRem, originalCcInCdr and
cgfDualStackSupport

SGSN User Guide
Function Impact
Counters M008C003 / GENERATED S-CDRS

M008C069 / AVG DUR OF SCDR NRT PDP CO SUM
M008C070 / AVG DUR OF SCDR NRT PDP CO DEN
M008C071 / AVG DUR OF SCDR RT PDP CO SUM
M008C072 / AVG DUR OF SCDR RT PDP CO DEN
M008C073 / AVG OPEN GB S-CDR SUM
M008C074 / AVG OPEN GB S-CDR DEN
M008C075 / MIN OPEN GB S-CDR
M008C076 / PEAK OPEN GB S-CDR
M008C077 / MIN OPEN S-CDR (GB+IU)
M008C078 / PEAK OPEN S-CDR (GB+IU)
M008C085 / AVG OPEN IPV4 S-CDR SUM
M008C086 / AVG OPEN IPV4 S-CDR DEN
M008C087 / MIN OPEN IPV4 S-CDR
M008C089 / AVG OPEN IPV6 S-CDR SUM
M008C090 / AVG OPEN IPV6 S-CDR DEN
M008C091 / MIN OPEN IPV6 S-CDR
M008C092 / PEAK OPEN IPV6 S-CDR
M008C109 / AVG OPEN S-CDR SEC PDP CON SUM
M008C110 / AVG OPEN S-CDR SEC PDP CON DEN
M008C111 / MIN OPEN S-CDR SEC PDP CON
M008C112 / PEAK OPEN S-CDR SEC PDP CON SUM
M008C113 / AVG OPEN S-CDR IU IF SUBS SUM
M008C114 / AVG OPEN S-CDR IU IF SUBS DEN
M008C115 / MIN OPEN S-CDR IU IF SUBS
M008C116 / PEAK OPEN S-CDR IU IF SUBS
M008C121 / GEN S-CDR OF IU IF SUBSCRIBER
M008C145 / SUM OF SAMPLES OF NUMBER OF S-CDRS BY ROAMING
GB-USER
M008C146 / NUMBER OF SAMPLES OF NUMBER OF SCDRS BY
ROAMING GB-USERS
M008C147 / PEAK VALUE OF NUMBER OF S-CDRS BY ROAMING GB-
USER
M008C148 / MIN VALUE OF NUMBER OF S-CDRS BY ROAMING GB-
USER
M008C153 / SUM OF SAMPLES OF NUMBER OF ROAMING S-CDRS BY
ROAMING IU-USERS
M008C154 / NUMBER OF SAMPLES OF NUMBER OF SCDRS BY
ROAMING IU-USERS
M008C155 / PEAK VALUE OF NUMBER OF S-CDRS BY ROAMING IU-
USERS
M008C156 / MIN VALUE OF NUMBER OF S-CDRS BY ROAMING IU-
USERS
M008C158 / PEAK TOTAL VALUE ROAMING S-CDRS
M008C159 / GEN OFFLINE POSTPAID SCDR IU
M008C160 / GEN OFFLINE POSTPAID SCDR GB
M008C189 / SCDRS TRANSFERRED OVER BP

SGSN User Guide
Function Impact
Alarms 0111 ResourceInformation

0260 ScdrUpdateTaskStatus
0262 IncomingCdrsAtCgfStopped
0263 ChaIncrNumOfUntransles
3584 AmountOfAvailableS-cdrsAchieved
14045 ChaInterfacePrbProblem
14046 ChaInterfaceDataProblem
14047 ChaInternalProblem
14048 ChaOutOfUse
14057 ChaOverwrtOfUntranslesOfUntransles
External interfaces Bp interface (SFTP) used for S-CDR le transferring from SGSN to
billing system.
Feature ID SG01015, SG01189, SG02193, SG01118, f60210-18
7.2 IMEISV in CDR (SG01088): feature summary

The purpose of the optional SGSN IMEISV in CDR feature is to include the IMEISV to
charging.

SGSN User Guide
Table 109: IMEISV in CDR (SG01088): feature summary
Function Impact
Compliance 3GPP TS 24.008; Mobile Radio interface Layer 3 specication; Core

Network protocols; Stage 3
Capacity None
Interworking/dependent GTP Information Sending (Feature SG01082)

features
Restrictions None
Conguration Command features, parameter imeisvInCdr

management
Counters None
Alarms None
External interfaces Bp interface between the 2G SGSN and the charging gateway
Feature ID SG01088
7.3 Configurable charging (Features SG01147, SG01132

The feature introduces S-CDR generation decision per S-CDR type configuration.
Configurable charging features add the possibility for user to choose if S-CDRs are to be
created only for limited subscriber types (home or roaming) and/or for limited radio
access types (Gb, Iu, or I-HSPA). These features can also be used for reducing the S-CDR
amount when direct tunnel is used.

SGSN User Guide
Table 110: Configurable charging (Features SG01147, SG01132 and f60210-18): feature
summary
Function Impact
Capacity None
Interworking/dependent • Direct tunnel and smart device direct tunnel signaling optimization
features (Feature SG02017)
• SGSN support for charging functionality for Open Linux-based Cloud
SGSN (Feature f60210-18)
Restrictions None
Conguration Commands cdr count, cdrPapsCount

management Command chargingParams, parameters ttcMode, ttcTso,
cdrCreateGb, cdrCreateIu, cdrCreateIhspa, and
cdrCreateDt
Counters None
Alarms None
Feature ID SG01147, SG01132, f60210-18
7.3.1 Provisioning configurable charging

You can set up S-CDR opening rules based on radio access type (Gb, Iu, or I-HSPA) and
roaming type (home or roamer), or configure the S-CDR handling for users' PDPs of direct
tunnel.
Procedure
1 Check whether charging parameter set exists.

Step result
If there is no charging parameter set, the following is displayed:

SGSN User Guide
+-------+-------+
| Field | Value |
+-------+-------+
| | |
+-------+-------+
2 If charging parameter set does not exist, create it.
Step example
cmm chargingParams create --chargingParamsId 1
Step result
The prinout example shows the default values:
+-------------------+----------------+
| Field | Value |
+-------------------+----------------+
| direction | off |
| flatRate | off |
| time | 04-00 |
| vol2g | 12000 |
| minVol2g | 3000 |
| vol3g | 60000 |
| minVol3g | 15000 |
| t24h | off |
| purgeCDRs | off |
| ctmNorm | off |
| ttcTso | off |
| cdrCreateDt | on |
| sCdrDiscard | off |
+-------------------+---------------+

SGSN User Guide
3 Modify charging parameters.
3.1 Activate charging data collection (direction).
Modify parameter direction from off to bp. This will start charging data
collection and charging data encoding functionality in PAPS VM(s) and also S-CDR
file storing functionality in NECC. Note that you can also modify the other
necessary parameters, such as triggers, before activating the charging so that all
parameters are in use immediately after the charging functionality is activated.
Step example
bp
3.2 Configure the tunnel type change mode (ttcMode)
Use the ttcMode parameter to set the tunnel type change mode for choosing
how the S-CDRs are handled for users' PDPs of direct tunnel. Note that direct
tunnel functionality will cause a huge amount of S-CDR updates/intermediate S-
CDR generation due to tunnel type changes, so the recommended values are
blockingOnCont and blockingOnCdr.
The cdrCreateDt parameter is used together with the ttcMode parameter

depending on the ttcMode parameter values.

SGSN User Guide
Table 111: Values of ttcMode
Value Description
blockingOnCont When tunnel type change between direct tunnel and

two tunnel happens, it is not reported in S-CDR as
container change. S-CDRs are generated for direct
tunnel users' PDP contexts.
blockingOffCont When tunnel type change between direct tunnel and

two tunnel happens, it is reported in S-CDR as container
change (dt establish or dt removal). S-CDRs are
generated for direct tunnel users' PDP contexts.
blockingOnCdr When tunnel type change between direct tunnel and

two tunnel happens, there is no intermediate S-CDR
generation. S-CDRs are not generated for direct tunnel
users' PDP contexts.
blockingOffCdr When tunnel type change between direct tunnel and

two tunnel happens, it will cause intermediate S-CDR
generation. S-CDRs are generated for direct tunnel
users' PDP contexts.
blockingOnCdrWoDatav When tunnel type change between direct tunnel and

ol two tunnel happens, only such S-CDRs that have some
data volumes reported will be generated. Final S-CDRs
(due to PDP context deactivation) are generated for
direct tunnel users' PDP contexts.
Step example
Modify ttcMode to be blockingOnCont (note that cdrCreateDt is set to off
as well):
cmm chargingParams modify --chargingParamsId 1 --ttcMode

blockingOnCont --cdrCreateDt off
Step example
Modify ttcMode to be blockingOffCont (note that cdrCreateDt is set to
off as well):

blockingOffCont --cdrCreateDt off
Step example
Modify ttcMode to be blockingOnCdr (note that cdrCreateDt is set to on
as well):

SGSN User Guide

blockingOnCdr --cdrCreateDt on
Step example
Modify ttcMode modified to be blockingOffCdr (note that cdrCreateDt is
set to on as well):

blockingOffCdr --cdrCreateDt on
Step example
Modify ttcMode to be blockingOnCdrWoDatavol (note that cdrCreateDt is
set to on as well):

blockingOnCdrWoDatavol --cdrCreateDt on
Step example
Modify ttcMode from blockingOnCont to blockingOnCdr and parameter
cdrCreateDt from off to on to block the S-CDR generation for direct tunnel
PDPs:

blockingOnCdr --cdrCreateDt on
3.3 Configure tunnel type change timestamp override (ttcTso).
Use the ttcTso parameter to set the tunnel type change timestamp override. It
activates the timestamp override mechanism to be active if direct tunnel related
S-CDR generation has been blocked with parameter ttcMode.
Step example
cmm chargingParams modify --chargingParamsId 1 --ttcTso on
3.4 Configure S-CDR opening for home and/or visitor Gb subscribers' PDPs
(cdrCreateGb).
Step example
Allow S-CDR opening for both home and roaming Gb subscribers' PDPs:
cmm chargingParams modify --chargingParamsId 1 --cdrCreateGb

SGSN User Guide
all
Step example
Allow S-CDR opening for home Gb subscribers' PDPs:

home
Note:
If parameter value was either all or roam before giving this command,
any possible S-CDR for roaming Gb users will be closed due to S-CDR
opening rule modification.
Step example
Allow S-CDR opening for roaming Gb subscribers' PDPs:

roam
Note:
If parameter value was either all or home before giving this command,
any possible S-CDR for home Gb users will be closed due to S-CDR opening
rule modification.
Step example
No S-CDR opening for Gb:

none
Note:
If parameter value was either all, home or roam before giving this
command, any possible S-CDR for both home and roaming Gb users will be
closed due to S-CDR opening rule modification.
Step result
If S-CDRs are closed due to S-CDR opening rule modification, alarm 0260

SGSN User Guide
ScdrUpdateTaskStatus is set to identify when corresponding S-CDR closure

task starts, and also when it ends.
Parameter sCdrDiscard can be used to define if the closed S-CDRs are

discarded or stored on NECC CDR disk file.
3.5 Configure S-CDR opening for home and/or visitor Iu subscriber's PDPs
(cdrCreateIu).
Step example
Allow S-CDR opening for both home and roaming Iu subscribers' PDPs:
cmm chargingParams modify --chargingParamsId 1 --cdrCreateIu

all
Step example
Allow S-CDR opening for home Iu subscribers' PDPs:

home
Note:
any possible S-CDR for roaming Iu users will be closed due to S-CDR
Step example
Allow S-CDR opening for roaming Iu subscribers' PDPs:

roam
Note:
any possible S-CDR for home Iu users will be closed due to S-CDR opening
rule modification.
Step example
No S-CDR opening for Iu:

SGSN User Guide

none
Note:
command, any possible S-CDR for both home and roaming Iu users will be
closed due to S-CDR opening rule modification.
Step result
task starts, and also when it ends.

3.6 Configure S-CDR opening for home and/or visitor I-HSPA subscribers' PDPs
(cdrCreateIhspa)
Step example
Allow S-CDR opening for both home and roaming I-HSPA subscribers' PDPs:
cmm chargingParams modify --chargingParamsId 1 --

cdrCreateIhspa all
Step example
Allow S-CDR opening for home I-HSPA subscribers' PDPs:

cdrCreateIhspa home
Note:
any possible S-CDR for roaming I-HSPA users will be closed due to S-CDR
Step example
Allow S-CDR opening for roaming I-HSPA subscribers' PDPs:

SGSN User Guide

cdrCreateIhspa roam
Note:
If parameter value was either all or home before giving this command,
any possible S-CDR for home I-HSPA users will be closed due to S-CDR
Step example
No S-CDR opening for I-HSPA:

cdrCreateIhspa none
Note:
command, any possible S-CDR for both home and roaming I-HSPA users
will be closed due to S-CDR opening rule modification.
Step result
task starts and when it ends.

4 Output the current S-CDR amounts.
Use the cdr count command to print all the S-CDR amounts (access=ALL, sub=ALL)
or also use access type (access=GB/IU/IHSPA/DTIU/DTIHSPA) and/or sub type
(sub=HOME/ROAM) to output only the requested S-CDR amounts.
Step example
Output all S-CDR amounts.
cmm cdr count --access ALL --sub ALL

SGSN User Guide
+----------+-----------------------------+
| Field | Value |
+----------+-----------------------------+
| OPENCDRs | |
| | Access: ALL |
| | - IU: 5 |
| | - GB: 9 |
| | - IHSPA: 4 |
| | - DTIU: 0 |
| | - DTIHSPA: 0 |
| | Roaming subscribers S-CDRs: |
| | - IU: 2 |
| | - GB: 1 |
| | - IHSPA: 0 |
| | - DTIU: 0 |
| | - DTIHSPA: 0 |
+----------+-----------------------------+
Step example
Output S-CDRs amount of home Iu subscribers' PDPs only.
cmm cdr count --access IU --sub HOME
+----------+--------------------------+
| Field | Value |
+----------+--------------------------+
| OPENCDRs | |
| | Access: IU |
| | - IU: 5 |
+----------+--------------------------+
Use the cmm cdrPapsCount list command to output the current S-CDR amounts
per PAPS.

SGSN User Guide
Step example
cmm cdrPapsCount list
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
|papsId|homeIu|homeGb|homeIhspa|homeDtIu|homeDtIhspa|roamIu|roamGb|roamIhspa|roamDtIu|roamD
tIhspa|total|
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
| 0 | 4 | 7 | 0 | 0 | 0 | 1 | 0 | 0 | 0 | 0
| 12 |
| 1 | 1 | 2 | 4 | 0 | 0 | 1 | 1 | 0 | 0 | 0
| 9 |
| All | 5 | 9 | 4 | 0 | 0 | 2 | 1 | 0 | 0 | 0
| 21 |
+------+------+------+---------+--------+-----------+------+------+---------+--------+-----
------+-----+
7.3.2 Deactivating configurable charging

You can deactivate the configurable charging feature by restoring the original values when
there are no restrictions in S-CDR generation.
Procedure
1 Modify parameter cdrCreateGb to all.
cmm chargingParams modify
2 Modify parameter cdrCreateIu to all.
3 Modify parameter cdrCreateIhspa to all.
4 Modify parameter ttcMode from blockingOnCdr to blockingOffCont and

parameter cdrCreateDt from on to off to change the S-CDR handling for direct
tunnel PDPs.

SGSN User Guide
7.4 SGSN support for Ga interface (Features f52000-01

With this feature, the SGSN supports the Ga charging interface, CDR backup on disk, and
configurable port number for primary and secondary CGs on the Ga interface.
Table 112: SGSN support for Ga interface: feature summary

Function Impact
Compliance 3GPP TS 29.060 Technical Specication Group Core Network and Terminals; General Packet Radio Service (GPRS); GPRS
Tunnelling Protocol (GTP).
3GPP TS 32.295 Telecommunication management; Charging management; Charging Data Record (CDR) transfer, Release
12 for the Ga interface
3GPP TS 32.240 Telecommunication management; Charging management; Charging architecture and principles, Release
12.
3GPP TS 32.251 Telecommunication management; Charging management; Packet Switched (PS) domain charging, Release
12
3GPP TS 32.298 Telecommunication management; Charging management; Charging Data Record (CDR) parameter
description, Release 12.
Capacity SGSN supports up to 10 charging gateways.

With the default values (gaTick = 1, gaTickVolume = 10) the SGSN sends up to 100*10 = 1000 GTP’ packets per
second, each carrying up to 3 S-CDRs, therefore the default rate is ~3000 sCDRs/sec on each CG. The maximum rate is
currently approximately 6000 sCDRs/sec on each CG.
The send buffer can store up to 9000 CDR super-packets. With the default conguration, each CDR super-packet
contains up to 30 S-CDRs, therefore with the default settings the send buffer can store up to 270 000 S-CDRs. By setting
the gaTickVolume to its maximum value 20, each super-packet can hold up to 60 CDRs. In this case, the send buffer’s
capacity becomes 540 000 S-CDRs.
The resend buffer capacity for each CG is 250 GTP’ packets and it is not congurable.
Required features SGSN support for Charging Functionality for Open Linux-based Cloud SGSN (f60210-18)
Interworking/dependent features This feature is based on the feature SGSN support for Charging Functionality for Open Linux-based Cloud SGSN
(f60210-18). The following mechanisms are common between f60210-18 and f52000-01:
• Charging data collection in PAPS
• CDR trigger mechanism
• CDR data storage and maintenance within PAPS
• CDR backup in DBS
• CDR transmission from PAPS to NECC over Kafka
Restrictions This feature does not support dual stack links to the same CG.
In case both IPv4 and IPv6 type addresses of the same CG are provisioned (due to misconguration) when the CG
requests redirection, then this action has effect only to the IP address from which the message was received.
In case the preferred CG is provisioned with two IP address types (due to misconguration), the one with the highest
value in cgOrder parameter will be used and the other will be ignored.
Conguration management • Commands subnet and serviceIp

• Ga parameter set: command gaParams
• Charging gateways: command cgw, parameters cgOrder, cgIp, adminState
• Firewall rules for CG traffic: command firewallRule
• Activation through command chargingParams, parameter direction, value ga
• Status of charging gateways: command cgInfo

SGSN User Guide
Function Impact
Counters Counters introduced with this feature:

• M008C032 / AVE MASTER QUEUE LENGTH SUM
• M008C033 / AVE MASTER QUEUE LENGTH DEN
• M008C034 / PEAK MASTER QUEUE LENGTH
• M008C035 / INOPERATIVE CG EXISTS
• M008C036 / NO OPERATIVE CG EXISTS
• M008C037 / NO OPERATIVE CG DURATION
• M008C039 / DISCARDED GTP PACKET DUE INOPERATIVE CG TIMER
• M008C040 / DISCARDED GTP PACKET DUE INVALID MESSAGE FORMAT
• M008C041 / DISCARDED GTP PACKET DUE VERSION NOT SUPPORTED
• M008C042 / DISCARDED GTP PACKET DUE SERVICE NOT SUPPORTED
• M008C043 / DISCARDED GTP PACKET DUE MANDATORY IE INCORRECT
• M008C044 / DISCARDED GTP PACKET DUE MANDATORY IE MISSING
• M008C045 / DISCARDED GTP PACKET DUE SYSTEM FAILURE
• M008C046 / DISCARDED GTP PACKET DUE INCORRECT SEQ NUM
• M008C047 / DISCARDED GTP PACKET DUE REQ NOT FULFILLED
• M008C048 / SENT DATA RECORD PACKETS
• M008C049 / RE-SENT DATA RECORD PACKETS
• M008C050 / SENT POSSIBLY DUPLICATED DATA RECORD PACKETS
• M008C051 / CANCELLED DATA RECORD PACKETS
• M008C052 / RELEASED DATA RECORD PACKETS
• M008C053 / SUCC DATA RECORD PACKET RESPONSES
• M008C054 / RECEIVED NODE ALIVE REQUESTS
• M008C055 / RECEIVED REDIRECTION REQUESTS DUE THIS NODE GO DOWN
• M008C056 / RECEIVED REDIRECTION REQUESTS DUE ANOTHER NODE GO DOWN
• M008C057 / RECEIVED REDIRECTION REQUESTS DUE SYSTEM FAILURE
• M008C058 / RECEIVED REDIRECTION REQUESTS DUE RECEIVE BUFFERS FULL
• M008C059 / RECEIVED REDIRECTION REQUESTS DUE SEND BUFFERS FULL
• M008C064 / AVE GTP PACKETS UNDER DCPM SUM
• M008C065 / AVE GTP PACKETS UNDER DCPM DEN
• M008C066 / PEAK GTP PACKETS UNDER DCPM
• M008C175 / S-CDR STORED ON DISK OVERFL
Also counters introduced in feature f60210-18 are valid when the direction is Ga:
• M008C003 / GENERATED S-CDRS
• M008C004 / DISCARDED S-CDRS DUE OVERFLOW
• M008C005 / DISCARDED S-CDRS DUE OTHER
• M008C028 / GENERATED PREPAID S-CDRS
• M008C069 / AVG DUR OF SCDR NRT PDP CO Sum
• M008C070 / AVG DUR OF SCDR NRT PDP CO DEN
• M008C071 / AVG DUR OF SCDR RT PDP CO Sum
• M008C072 / AVG DUR OF SCDR RT PDP CO DEN
• M008C073 / AVG OPEN GB S-CDR Sum
• M008C074 / AVG OPEN GB S-CDR DEN
• M008C075 / MIN OPEN GB S-CDR
• M008C076 / PEAK OPEN GB S-CDR
• M008C077 / MIN OPEN S-CDR (GB+IU)
• M008C078 / PEAK OPEN S-CDR (GB+IU)
• M008C085 / AVG OPEN IPV4 S-CDR Sum
• M008C086 / AVG OPEN IPV4 S-CDR DEN
• M008C087 / MIN OPEN IPV4 S-CDR
• M008C088 / PEAK OPEN IPV4 S-CDR
• M008C089 / AVG OPEN IPV6 S-CDR Sum
• M008C090 / AVG OPEN IPV6 S-CDR DEN
• M008C091 / MIN OPEN IPV6 S-CDR
• M008C092 / PEAK OPEN IPV6 S-CDR
• M008C105 / AVG OPEN PREPAID S-CDR Sum
• M008C106 / AVG OPEN PREPAID S-CDR DEN
• M008C107 / MIN OPEN PREPAID S-CDR
• M008C108 / PEAK OPEN PREPAID S-CDR
• M008C109 / AVG OPEN S-CDR SEC PDP CON Sum
• M008C110 / AVG OPEN S-CDR SEC PDP CON DEN
• M008C111 / MIN OPEN S-CDR SEC PDP CON
• M008C112 / PEAK OPEN S-CDR SEC PDP CON Sum
• M008C113 / AVG OPEN S-CDR IU IF SUBS Sum
• M008C114 / AVG OPEN S-CDR IU IF SUBS DEN
• M008C115 / MIN OPEN S-CDR IU IF SUBS
• M008C116 / PEAK OPEN S-CDR IU IF SUBS
• M008C121 / GEN S-CDR OF IU IF SUBSCRIBER
• M008C122 / DIS S-CDR OF IU IF DUE OVERF
• M008C123 / DIS S-CDR OF IU IF DUE OTHER
• M008C137 / GENER PREPAID S-CDR OF IU SUBS
• M008C145 / Sum OF SAMPLES OF NUMBER OF S-CDRS BY ROAMING GB-USER
• M008C146 / NUMBER OF SAMPLES OF NUMBER OF S-CDRS BY ROAMING GB-USERS
• M008C147 / PEAK VALUE OF NUMBER OF S-CDRS BY ROAMING GB-USER
• M008C148 / MIN VALUE OF NUMBER OF S-CDRS BY ROAMING GB-USER
• M008C153 / Sum OF SAMPLES OF NUMBER OF ROAMING S-CDRS BY ROAMING IU-USERS
• M008C154 / NUMBER OF SAMPLES OF NUMBER OF S-CDRSBY ROAMING IU-USERS
• M008C155 / PEAK VALUE OF NUMBER OF S-CDRS BY ROAMING IU-USERS
• M008C156 / MIN VALUE OF NUMBER OF S-CDRS BY ROAMING IU-USERS
• M008C158 / PEAK TOTAL VALUE ROAMING S-CDRS

SGSN User Guide
Function Impact
Alarms 160 ChgExceptionalHandling

3009 SgsnChargingResendBufferFull
3010 NoOperationalChargingGatewayNetworkElement
3056 AnInoperativeChargingGateway
3076 SgsnChargingResendBufferBecomingFull
3308 CdrSendBufferFullnessInfo
3323 CgDoesntAnswerToAliveReq
14131 S-cdrBackupOnDiskTookPlaceToAvoidOverflowOnGaInterface
Note:
In case the following NECC switchover alarms occur:

• 14131 S-cdrBackupOnDiskTookPlaceToAvoidOverflowOnGaInterface
• 3323 CgDoesntAnswerToAliveReq
• 3010 NoOperationalChargingGatewayNetworkElement
• 3056 AnInoperativeChargingGateway
• 3550 ApplicationIpAssociationMissing
The new NECC will not clear the alarms that the previous NECC raised.
The operator have to check if the alarms are raised by the new NECC.
In this case, it may be a connectivity issue between NECC and charging gateways.
Feature ID f52000-01, f12101-15
7.4.1 Operational aspects of the Ga interface

Checklist for the Ga interface parameters.
Before starting the CDR generation and transfer, check the following:
The CG IP addresses have been created and the CG administrative state is unlocked.
The system reads the provisioning and the currently known administrative and
operational states to find operational CG IP addresses. At least one should be found in
order to start CDR transfer.
If the CG does not respond to GTP’ Node Alive Request, the transfer cannot start and the
operational state will be Waiting for Node Alive response (10). The SGSN sends Node Alive
Requests to all CGs before the CDR transfer is started.
The node alive request procedure is used by the SGSN whenever a CG’s administrative
state is switched from locked to unlocked and whenever a CG has been created, if the
admin state provided in the cmm cgw create command is unlocked.
CDR generation trigger parameters have reasonable values. Values can be checked with
the command cmm chargingParams show 1.
Low-volume trigger and short-time trigger values cause high S-CDR generation.
CDR sending rate parameters have reasonable values. Default values are standard but if
the send buffer becomes full without any particular reason, the CDR sending rate can be
raised. However, the CDR generation rate must always be checked first before speeding
up CDR sending to the CG.
The Ga transmission rate is controlled through parameters gaTick and gaTickVolume in

the cmm gaParams configuration.

SGSN User Guide
The gaTick parameter (value is in 10 msec, range 1..100, means that gaTick can vary
from 10 msec to 1 sec, in steps of 10 msec) defines how frequently the transmission
queues will be polled for outgoing packets.
The gaTickVolume parameter (range from 8 to 20) defines up to how many GTP’ Data
Record Transfer Request messages are sent on each gaTick.
Each GTP’ Data Record Transfer Request message contains up to 3 S-CDRs (hard-coded
value). The S-CDRs in a GTP’ message may be less than 3 if, at the moment of transmission,
the available S-CDRs that could be packaged in the outgoing message were fewer.
The parameters have effect per charging gateway.
7.4.2 Configuring the Ga interface

Ga is the charging data collection interface between a CDR transmitting unit (CMM SGSN)
and a CDR receiving unit (CG).
Before you start
The Ga interface supports using the OAM subnet or a whole separate IP subnet.
The Ga interface terminates on the NECC cluster. The local Ga endpoint is defined as port
3386/UDP on the service IP address that is locally configured for the niType GA. The
service IP is configured with assignmentType set to floating. This means that the
external IP address of the NECC cluster for Ga interface is located to the NECC VM that
currently has the high availability IP address of the internal network. The IP address of the
Ga interface is transferred to another NECC VM in case of NECC failure.
IPv4 or IPv6 address is supported.
The Ga feature is activated when the direction parameter in chargingParams is set to

ga. The direction parameter defines if charging information (S-CDRs) are being produced
and where are they directed: either ga or bp (stored on disk). When direction is set to
off, no new S-CDRs are produced.
It is not required to switch the charging direction to Ga in order to provision the

configuration for Ga interface. Switching the charging direction to any value other than off
results in the SGSN producing CDRs. It is therefore recommended to provision the Ga details
before switching the direction to ga.

SGSN User Guide
Procedure
1 Create a subnet for Ga (optional, depending on the IP network planning).
Step example
cmm subnet create --subnetId 5 --ipv 4 --base z.z.z.z --
subnetMask 255.255.255.0
Step example
cmm subnet create --interfaceLabelL eth1 --ipv 6 --base x:x:x:x::
--prefixLen 64 --defaultGateway x:x:x:x::x --subnetId 10
where the x letters are the hexadecimal values of the eight 16-bit pieces of the IPv6
address.
2 Create local IP address for Ga.
Step example
cmm serviceIp create --niType GA --poolType NECC --poolId 0 --
poolMemberId 0 --svcIp x.x.x.x. --subnetLoc external --
assignmentType floating
Step example
cmm serviceIp create --niType GA --poolType NECC --poolId 0 --
poolMemberId 0 --svcIp x:x:x:x:x:x:x:x --subnetLoc external –-
assignmentType floating
where the x letters are the hexadecimal values of the eight 16-bit pieces of the IPv6
address.
3 Create Ga parameter set.

SGSN User Guide
cmm gaParams create
--gaParamsId <integer>
[--gaTick <integer>]
[--gaTickVolume <integer>]
[--cdrResendDelay <integer>]
[--cdrRetransmissions <integer>]
[--gaBackupOnDisk {true,false}]
[--dcpmException {cancel,release}]
[--gaEchoInt <integer>]
[--gaT3res <integer>]
gaParamsId Ga Parameters set ID. Only one Ga parameter set can be created.
gaTick Ga transmission period in steps of 0.01 seconds. Species how

frequently the send queue is polled for CDRs ready for
transmission to a CG.
Range: 1…100, default value: 1
gaTickVolume Transmitted CDR packets per tick, on Ga interface.

Default value: 10
cdrResendDelay Delay in seconds for the rst retransmission. The subsequent

retransmissions take place with increased delay.
Range: 2 - 180, default value: 5
cdrRetransmissions CDR retransmission count on Ga interface.

Default value: 5
gaBackupOnDisk Ga backup on disk in case of a risk to lose CDRs.
dcpmException CDR exception handling (default instruction to alternative CGs on

what to do in case of potentially duplicated CDR packets).
• cancel - DCPM on Ga sends CANCEL command in case of
permanent CG failure. Some of the CDR data may be lost if a CG
does not reply, or if a CG IP address is deleted before the CG has
acknowledged all the transfers.
• release - DCPM on Ga sends RELEASE command in case of
permanent CG failure (default). Duplicated CDR data may be
produced.
gaEchoInt Ga echo interval, in seconds.


SGSN User Guide
gaT3res Delay in seconds for echo retransmissions.

Step example
cmm gaParams create --gaParamsId 1
Creating the Ga parameter set without any other parameters means that all the
parameters take default values.
4 Create charging gateways.
cmm cgw create
--cgOrder <integer>
--cgIp <string>
[--remPort <integer>]
--adminState {locked,unlocked}
You can create up to 10 charging gateways.
The cgOrder indicates a CG preference significance for the S-CDRs for which there is
no recommended CG IP address provided by the GGSN. In all cases where a CG selection
needs to take place, the CG with the lowest cgOrder value is selected (regardless if it is
locked or unlocked).
Step example
cmm cgw create --cgOrder 1 --cgIp y.y.y.y --adminState locked
cmm cgw create --cgOrder 2 --cgIp y.y.y.y --adminState locked
Step example
cmm cgw create --cgOrder 1 --cgIp y:y:y:y:y:y:y:y --adminState
locked
5 Configure the firewall rules to allow Ga traffic.
Step example
cmm firewallRule create --ruleName allow_port1 --ruleResult allow
--dport 3386 --firewallProtocol udp

SGSN User Guide
Step result
If the charging gateway stays in operational status 10 WAITING THAT NODE
RESPONSE TO NODE ALIVE REQUEST, check that the correct firewall rules, which
allow the communication between CMM NECC’s Ga endpoint and the CG, are in place.
6 Change charging direction to Ga.
cmm chargingParams modify 1 --direction ga
7 Set the admin state of the CGs to unlocked.
Step example
cmm cgw modify --adminState unlocked 1
cmm cgw modify --adminState unlocked 2
Step result
When a CG is in the unlocked admin state, it is not possible to modify any parameters
(for example, IP address, port). The CG must be switched to locked first, and the
shutting down state must expire (30 minutes) so that the operational state switches to
unknown before any changes are allowed.
7.4.3 Switching between Ga and Bp

It is not supported to switch on the fly the direction from Ga to Bp (or vice versa). For this
reason, it is not allowed to make the transition of direction ga → bp or bp → ga. Every such
transition must go through the off state.
In case a transition from Bp to Ga (or Ga to Bp) is desired, it must be done in a maintenance

window, when the traffic and the produced CDRs are at the lowest possible rate. During the
transition some CDRs may be lost, for example, while the direction is set to off or due to the
direction change. Recommended main steps for a direction change are listed below.
Transition from Bp to Ga:

1. Switch direction to off (chargingParams)
2. Pull any existing charging files out of the SGSN (directory /data-charging/cdr)
3. Initialize the directory /data-charging/cdr by removing all its contents (this is
needed because these files may be used by Ga interface implementation to do fallback
on disk in the event of risk for data loss).
4. Provide the provisioning for Ga.

SGSN User Guide
5. Switch direction to ga (chargingParams).
Transition from Ga to Bp:

1. Switch direction to off (chargingParams)
2. Check using cmm cgInfo list that all buffers for all CGs have been emptied.
3. Change the adminState of every CG to locked(cgw).
4. Wait until the operational state of each CG goes to Unknown (check using cmm cgInfo
list).
5. Pull out any contents of /data-charging/cdr (in case any CDRs have been stored on
disk during the operation in Ga mode).
6. Initialize /data-charging/cdr by removing all its contents.
7. Switch direction to bp (chargingParams).
7.4.4 Deleting a charging gateway

In order to remove a CG, it is recommended to first switch it to locked admin state, then
wait until it reaches the 'unknown' status.
If a CG is deleted while it had queued packets (see output of cmm cgInfo list), it is
recommended to allow some minutes for the packets previously owned by the CG in that
slot to be sent and removed from the send buffer before adding another CG in the same
slot, as the co-existence in the send buffers of super-packets with the same CG order as
destination but targeted for different actual CG may temporarily reduce the effectiveness
of the high availability mechanism in case of NECC reset. However, the operation is allowed
as in all other operational conditions (that is, no NECC reset or Ga malfunctions) there is no
side effect.
When the last CG is being deleted, any existing CDRs in the send buffer are lost. Any new
CDRs are sent to the disk, if the gaBackupOnDisk parameter allows this.
By unlocking an existing CG, the SGSN triggers a Node Alive Request message. When the
admin state of the CG is unlocked, the operational state of the CG is set after the CG has
responded to the Node Alive Request and whether it has responded to the Echo Request or
not. The SGSN does not check the CG state, if the CG is marked as locked in the CG IP
address and status list in the SGSN.

SGSN User Guide
7.5 Controlled roaming (Feature SG01004): feature

summary
This feature allows the implementation of more flexible roaming agreements. It provides
tools to specify certain areas of the radio network that can be used only by defined
groups of subscribers. This feature can be enabled separately for home and visiting
subscribers.

SGSN User Guide
Table 113: Controlled roaming (Feature SG01004): feature summary
Function Impact
Capacity Minor effect on the capacity of the SGSN.
Interworking/dependent • GPRS mobility management (Feature SG01011)

• HLR based 2G/3G access control (Feature SG02114)
Restrictions The maximum capacity of access lists, LAs, and IMSIs is 1000, 2000,
and 5000, respectively.
Conguration Command system, parameter homeSubs, visitorSubs

management Command homeAccessList, parameter alName,
homeAccessListId
Command visitorAccessList, parameter alName,
visitorAccessListId
Command homeSubscriberGroup, parameter imsi,
accessRights, homeSubscriberGroupId,
homeAccessListId
Command iberGroup, parameter imsi, accessRights,
visitorSubscriberGroupId, visitorAccessListId
Command laiOfHomeAccessList, parameter mcc, mnc, lac,
homeAccessListId
Command laiOfVisitorAccessList, parameter mcc, mnc,
lac, visitorAccessListId
Command sgsnLai, parameter mnc, lac, mcc,
homeSubscriber, visitorSubscriber
Command features, parameter controlledRoaming
Counters Each rejection of a procedure that is caused by the Controlled

Roaming feature increments the corresponding counter.
Alarms None
Feature ID SG01004
7.5.1 Configuring controlled roaming for home subscribers

Controlled Roaming is activated in the SGSNs for location areas, separately for home and
visiting subscribers.

SGSN User Guide
Purpose
Use this procedure to configure controlled roaming for home subscribers.
Procedure
1 Create an access list for home subscribers.
cmm homeAccessList create --alName <access list name> --

homeAccessListId <access list number>
alName Access list name. Value: string from 1 to 15 characters.
homeAccessListId Home Access list identier
2 Define all totally allowed or partly allowed subscriber groups on the home access list.
cmm homeSubscriberGroup create --imsi <part of IMSI> --accessRights <access
rights> --homeSubscriberGroupId <subscriber group number> --homeAccessListId
<access list number>
homeSubscriberGroupId Home subscriber group identier. Value: integer [1...5000].
imsi IMSI number range. Value: [1...15]
accessRights Access rights of subscriber group.

Values:
• noRights - No rights
• 2gRoamGeranAndUtran - 2G roaming allowed with GERAN
and UTRAN
and UTRAN
2gAnd3gRoamGeranAndUtran - 2G and 3G roaming allowed
with GERAN and UTRAN
2gRoamGeran - 2G roaming allowed with GERAN
• 2gRoamUtran - 2G roaming allowed with UTRAN
• 2gAnd3gRoamGeran - 2G and 3G roaming allowed with
GERAN
• 2gAnd3gRoamUtran - 2G and 3G roaming allowed with
UTRAN

SGSN User Guide
homeAccessListId Home access list identier. The setting for this parameter should
match the value of homeAccessListId in the
homeAccessList table.
Step example
The following example creates a subscriber group for homers (IMSI digits:2440820) with
group ID of 1, assigns access rights to it and associates it with the access list created in
the previous step:
# cmm homeSubscriberGroup create --imsi 2440820 --accessRights
3gRoamGeranAndUtran --homeSubscriberGroupId 1 --homeAccessListId 1
3 Create SGSN location area identifiers and activate control at the LA level for home
and roaming subscribers.
cmm sgsnLai create –mcc <LA's mcc> --mnc <LA's mnc> --lac
<location area code> --homeSubscriber <true|false> --
visitorSubscriber <true|false>
mcc MCC digits of the broadcasted PLMN. Value: [3..3].
mnc MNC digits of the broadcasted PLMN. Value: [2 ....3].
lac Location area code. An integer, 1...6553.
homeSubscriber Control Roaming ag for a home subscriber at the LA level. Value:
true or false (the default).
visitorSubscriber Control Roaming ag for a visitor subscriber at the LA level. Value:
Step example
The following example creates an SGSN location area identifier for the LA in use
(MCC-244, MNC-07, LAC-1011), and specifies that roaming control is allowed for home
subscribers.
cmm sgsnLai create --mcc 244 --mnc 07 --lac 1011 --homeSubscriber true

SGSN User Guide
4 Activate controlled roaming for home subscribers at the location area (LA) level and
associate the home subscriber access list with the LA.
cmm laiOfHomeAccessList create --mcc <LA's mcc> --mnc <LA's mnc>

--lac <location area code> --homeAccessListId <access list
number>
lac Location area code. Value: integer, 1...6553.
homeAccessListId Home Access list identier. The setting for this parameter should
homeAccessListtable.
Step example
cmm laiOfHomeAccessList create –-mcc 244 --mnc 07 --lac 1011
--homeAccessListId 1
5 Activate controlled roaming for home subscribers on the SGSN level.
cmm system modify –homeSubs true config
7.5.2 Configuring controlled roaming for visitor

subscribers
Controlled Roaming is configured in the SGSNs for location areas, separately for home
and visiting subscribers.
Purpose
Use this procedure to configure controlled roaming for visiting subscribers.

SGSN User Guide
Procedure
1 Create an access list for visiting subscribers.
cmm visitorAccessList create --alName <access list name> --

visitorAccessListId <access list number>
alName Access list name. Value: string from 1 to 15 characters.
visitorAccessListId Visitor access list identier
Step example
The following example creates the visitor access list called, visitor_subs and assigns it
list ID 2:
# cmm visitorAccessList create --alName visitor_subs --

visitorAccessListId 2
2 Define all totally allowed or partly allowed subscriber groups on the visitor access
list.
cmm visitingSubscriberGroup create –-imsi <part of IMSI> --accessRights <access
right> --visitingSubscriberGroupId <subscriber group number> --
visitorAccessListId <access list number>
visitingSubscriberGroupId Visitor subscriber group identier. Value: integer [1...5000].
imsi IMSI number range. Value: [1...15]

SGSN User Guide
accessRights Access rights assigned to the subscriber group.

Values:
• noRights - No rights
and UTRAN
and UTRAN
2gAnd3gRoamGeranAndUtran - 2G and 3G roaming allowed
with GERAN and UTRAN
• 2gAnd3gRoamGeran - 2G and 3G roaming allowed with
GERAN
• 2gAnd3gRoamUtran - 2G and 3G roaming allowed with
UTRAN
visitorAccessListId Visitor access list identier. The setting for this parameter should
homeAccessList table.
Step example
The following example creates a subscriber group for visitor subscribers (IMSI digits:
2440920) with group ID of 2, assigns access rights to it and associates it with the
access list created in the previous step:
# cmm visitingSubscriberGroup create --imsi 2440920 --accessRights
3gRoamGeranAndUtran --visitingSubscriberGroupId 2 --visitorAccessListId 2
3 Create SGSN location area identifiers and activate controlled roaming.
cmm sgsnLai create –mcc <LA's mcc> --mnc <LA's mnc> --lac
<location area code> --homeSubscriber <true|false> --
visitorSubscriber <true|false>
lac Location area code. An integer, 1...6553.

SGSN User Guide
homeSubscriber Control Roaming ag for a home subscriber at the LA level. Value:
visitorSubscriber Control Roaming ag for a visitor subscriber at the LA level. Value:
Step example
The following example creates an SGSN location area identifier for the LA in use
(MCC-244, MNC-08, LAC-4424), and specifies that roaming control is allowed for visitor
subscribers.
# cmm sgsnLai create --mcc 244 --mnc 08 --lac 4424 --visitorSubscriber true
4 Activate controlled roaming for visitor subscribers at the location area (LA) level and
associate the home subscriber access list with the LA.
cmm laiOfVisitorAccessList create --mcc <LA's mcc> --mnc <LA's

mnc> --lac <location area code> --visitorAccessListId <access
list number>
lac Location area code. Value: integer, 1...6553.
visitorAccessListId Visitor access list identier. The setting for this parameter should
match the value of visitorAccessListId in the
visitorAccessListtable.
Step example
# cmm laiOfVisitorAccessList create –-mcc 244 --mnc 08 --lac 4424 –-
visitorAccessListId 2
5 Activate controlled roaming for visitor subscribers on the SGSN level.

SGSN User Guide
cmm system modify –visitorSubs true config
7.6 QoS control for roaming subscribers (Feature

With this feature, the HPLMN operator can control the served QoS per PLMN in the SGSN.
Table 114: QoS control for roaming subscribers (Feature SG01067): feature summary
Function Impact
Capacity None
Interworking/dependent features Quality of service (Feature SG01027)
Restrictions This QoS control per roaming partner

functionality enhances QoS control for roaming
subscribers feature by introducing the
possibility to dene its own QoS restrictions for
each PLMN.

qosCtrRoamSub
Command plmnParam, parameters
qosRoamingAllowed and
plmnSpecQosRParInUse
Counters None
Alarms None
Feature ID SG01067
7.6.1 Configuring QoS control for roaming subscribers

To allow roaming or PLMN specific roaming parameters, enable the QoS control for
roaming subscribers feature.

SGSN User Guide
Procedure
1 Enable the QoS control for roaming subscribers feature.
cmm features modify qosCtrRoamSub --status true
2 Allow QoS roaming.
cmm plmnParam modify <Roaming PLMN name> --qosRoamingAllowed true
true Allow QoS roaming.
false Deny QoS roaming.
3 Allow PLMN specific roaming parameters.
cmm plmnParam modify <Roaming PLMN name> --qosRoamingAllowed true

--plmnSpecQosRParInUse true
true PLMN specic roaming parameters in use
false PLMN specic roaming parameters not in use
In SGSN side, the QoS logic is displayed in the following table:

SGSN User Guide
CLI\Param --qosRoamingAllowed -- Applied QoS rule

plmnSpecQosParInUse
plmnParam false false SGSN level QoS values (for

example, QoS values set in
qosConf) are taken into
account.
false true PLMN specic QoS

parameters (for example,
QoS dened in plmnParam)
are taken into account.
true false UE requested/subscribed

QoS values are taken into
account.
true true UE requested/subscribed

QoS values are taken into
use (for example, QoS
settings in plmnParam are
ignored even though
plmnSpecQosParInUse
is true).
7.7 Operator determined barring (Feature SG02207):

feature summary
Operator determined barring (ODB) allows the network operator or service provider to
regulate the access by the subscribers to services (both Circuit and Packet Oriented), by
the barring of certain categories of outgoing or incoming calls/Packet Oriented Services
or of roaming. ODB takes effect immediately and terminates ongoing calls and bar future
calls/packet oriented services.

SGSN User Guide
Table 115: Operator determined barring (Feature SG02207): feature summary
Function Impact
Compliance 3GPP TS 23.015 “Technical realization of Operator Determined

Barring (ODB)” Rel-9
3GPP TS 22.041 “Operator Determined Barring (ODB) (Rel 9)”
Rel-9
3GPP TS 29.002 “Mobile Application Part (MAP)"
3GPP TS 23.060 “General Packet Radio Service (GPRS); Service
description; Stage 2"
Capacity None

features
Restrictions None
Conguration management None
Counters p
GPRS Session Management (002):
• M002C168 / FAIL MO PDP ACT FOR BAPS
• M002C169 / FAIL MO PDP ACT FOR BPSH
• M002C170 / FAIL MO PDP ACT FOR BPSV
GPRS Iu Session Management Measurement (017):
• M017C148 / IU FAIL MO PDP ACT FOR BAPS
• M017C149 / IU FAIL MO PDP ACT FOR BPSH
• M017C150 / IU FAIL MO PDP ACT FOR BPSV
Alarms None
Feature ID SG02207
7.8 QoS upgrade above the HLR values (Feature SG01256):

feature summary
This feature makes possible for GGSN-P-GW/PCRF to upgrade QoS attributes above HLR
limits. Normally, QoS values are limited to subscribed values as specified by HLR
subscription. With this feature it is possible for SGSN to accept temporarily upgraded
QoS values (turbo button' values) above the HLR limits from the GGSN/P-GW.

SGSN User Guide
Table 116: QoS upgrade above the HLR values (Feature SG01256): feature summary
Function Impact

• 3GPP TS 23.107 Quality of Service (QoS) concept and architecture
• 3GPP TS 23.203 Policy and charging control architecture
• 3GPP TS 23.401 General Packet Radio Service (GPRS) enhancements
for Evolved UniversalTerrestrial Radio Access Network (E-UTRAN)
access
• 3GPP TS 24.008 Mobile radio interface Layer 3 specication; Core
network protocols; Stage 3
• 3GPP TS 25.413 UTRAN Iu interface Radio Access Network
Application Part (RANAP) signalling
Tunneling Protocol (GTP) across the Gn and Gp interface
• 3GPP TS 29.212 Policy and Charging Control (PCC); Reference points
• 3GPP TS 29.213 Policy and charging control signaling ows and
Quality of Service (QoS) parameter mapping
Capacity The SGSN, radio network, and IP backbone are expected to be able to
handle the user data traffic ows which are expected to be caused
by the turbo button functionality, if these are not limited via the RNC
parameters, BSC conguration, or other means.
Required features GTP info sending (Feature SG01082) – optional

SGSN upgrade QoS Flag
Interworking/dependent If SGSN upgrade QoS Flag is enabled, the following feature will be
features able to limit the turbo QoS: QoS control for roaming subscribers
(Feature SG01067)
Restrictions Restrictions do apply on the below scenarios:

• Turbo button status on inter-PAPS, inter-SGSN and IRAT scenarios
• Overload handling
See QoS upgrade above the HLR values restrictions in SGSN
Feature Overview.
Conguration Command features, parameter updQosAboveHlr

management Command prFile, parameter updQosSuppFlg
Counters None
Alarms None
Feature ID SG01256

SGSN User Guide
7.8.1 Configuring QoS upgrade above the HLR values

You can enable/disable the QoS upgrade above the HLR value feature by using the
updQosAboveHlr parameter and the Upgrade QoS supported bit in Common Flag IE for
GTPv1 feature by using the updQosSuppFlg parameter.
Procedure
1 Activate feature QoS upgrade above the HLR value.
This feature makes possible for GGSN-P-GW/PCRF to upgrade QoS attributes above
HLR limits (turbo button). Normally, QoS values are limited to subscribed values as
specified by HLR subscription. With this feature, it is possible for SGSN to accept
temporarily upgraded QoS values (turbo button values) above the HLR limits from the
GGSN/P-GW.
cmm features modify updQosAboveHlr --status true
2 Enable sending of Upgrade QoS supported bit flag in Common Flag IE.
The Upgrade QoS supported bit field restricts the QoS values proposed by GGSN/P-GW
to the HLR limits in SGSN. This functionality is activated using the parameter
updQosSuppFlg. The parameter controls sending of the Upgrade QoS supported bit
flag in Common Flag IE from SGSN to GGSN-P-GW/PCRF. When this feature is enabled,
this restriction no longer exists and the HLR limits may be overridden.
cmm prFile modify updQosSuppFlg --status true
7.9 SGSN support for roaming QoS control (Feature

This feature allows an operator to control QoS values for inbound roaming subscribers.

SGSN User Guide
Table 117: SGSN support for roaming QoS control (Feature f51023-01): feature summary
Function Impact
Compliance • 3GPP TS 23.060: General Packet Radio Service (GPRS) Service

description
• 3GPP TS 23.107: Quality of Service (QoS) concept and architecture
• 3GPP TS 24.008: Mobile radio interface Layer 3 specication; Core
network protocols
• 3GPP TS 29.060, General Packet Radio Service (GPRS); GPRS
Tunnelling Protocol (GTP) across the Gn and Gp Interface
• GPP TS 29.274: Evolved General Packet Radio Service (GPRS)
Tunnelling Protocol for Control plane (GTPv2-C)
Capacity None

SGSN upgrade QoS Flag
features
Restrictions The feature should not be activated along with:

• QoS upgrade above the HLR values (Feature SG01256) (release 7
cases only)
• SGSN upgrade QoS Flag (release 7 cases only)
Parameter delayedIratMod ( prFile command) needs to be
enabled for retrieving subscribed QoS prole prior sending the
Update PDP Context Request message towards GGSN in mobility
management cases.
Conguration Command gParm, parameter ctrlRoamerQos. Default value is

management No.
Command prFile, parameter delayedIratMod
Command plmnParam (all QoS related parameters)
Counters None
Alarms None
7.9.1 Configuring SGSN support for roaming QoS control

Procedure

SGSN User Guide
Step example
cmm gParms modify --gParmName ctrlRoamerQos –-gParmValue Yes
2 Enable delayed IRAT modification (optional).
Step example
cmm prFile modify delayedIratMod --status true
3 Configure PLMN-specific QoS parameters.
Configure PLMN-specific QoS roaming configuration based on roaming agreement using

command plmnParam.
For more information, see Configuring QoS.
Step example
cmm rncParamSet modify 1 --maxDlBitrateForRab 42000
7.10 HLR HSPA+QoS Override (Feature SG01231): feature

summary
This feature allows the use of HSPA+ feature even though the HLR does not support high
bit rates.

SGSN User Guide
Table 118: HLR HSPA+QoS Override (Feature SG01231): feature summary
Function Impact
Compliance This feature is Nokia proprietary.
Capacity Not applicable.
Required features • HSDPA Support and HSPA+ (Features SG02104 and SG02198)
• HSUPA Support and HSPA+ (Features SG01113 and SG02198)
Interworking/dependent • Session Management (Feature SG01012)

features • 3G Access Support (Feature SG02001)
• Direct Tunnel (Feature SG02017)
Restrictions None
Conguration Command prFile, parameter hlrQosMbrDlValue,

management hlrQosMbrulValue, hlrQosMbrDlLimit, and
hlrQosMbrUlLimit
Counters None
Alarms None
Feature ID SG01231
7.10.1 Configuring HLR HSPA+QoS Override

If the HLR HSPA+QoS Override feature is configured, when the SGSN receives an MBR
value from the HLR that is equal to or greater than the configured ‘HSPA+ MBR limit
value’, the SGSN overrides the QoS parameters received from the HLR and uses the MBR
value set for the hlrQosMbrDlValue and hlrQosMbrUlValue parameters.
Purpose
Use this procedure to configure HLR HSPA+QoS Override.
Procedure
1 Display the current state of the feature for the DL and UL directions.
cmm prFile show hlrQosMbrDlValue

cmm prFile show hlrQosMbrUlValue
Step result
The feature is disabled in the downlink direction if hlrQosMbrDlValue is equal to 0.

SGSN User Guide
The feature is disabled in the uplink direction if hlrQosMbrUlValue is equal to 0.
cmm prFile modify hlrQosMbrDlValue --hlrQosMbrDlValue 1
cmm prFile modify hlrQosMbrUlValue --hlrQosMbrUlValue 1
hlrQosMbrDlValue The bit rate value that is used when the bit rate value received
from HLR is overridden. Values (in Mbps): 1D-168D, 0D. 0D
species that the feature is disabled in the downlink direction.
hlrQosMbrUlValue the bit rate value that is used when bit rate value received from
HLR is overridden. Values (in Mbps): 1D-46D, 0D. 0D species that
the feature is disabled in the uplink direction.
Step example
Suppose that in the HLR the MS subscription QoS profile, MAXIMUM BIT RATE FOR
DOWNLINK = 10 Mbps and in the SGSN hlrQosMbrDlLimit = 8 Mbps and
hlrQosMbrDlValue = 168 Mbps. Since the downlink MBR value received from HLR in
QoS parameter is greater than the value set for the hlrQosMbrDlLimit parameter,
the SGSN overrides the QoS parameter and sets the MBR downlink value to 168 Mbps
3 Set the HLR QoS maximum bit rate limit for uplink and downlink override limit.
In HLR and SGSN, two different bit rate values exist in the QoS parameter: one defines
maximum data transfer speed (in bps) for downlink direction and the other for uplink
direction. These parameters define the speed (bit rate) limit. If bit rate value received
from HLR is equal to or greater than this limit value, the feature overrides the bit rate
value received from HLR.
cmm prFile modify hlrQosMbrDlLimit --hlrQosMbrDlLimit 1
cmm prFile modify hlrQosMbrUlLimit --hlrQosMbrUlLimit 1

SGSN User Guide
hlrQosMbrDlLimit HLR QoS maximum bit rate for downlink override limit. If the DL
MBR value received from HLR in PDP context’s QoS parameter is
equal to or greater than value of this parameter, the maximum bit
rate for downlink value received from HLR is replaced with bit rate
value dened in parameter hlrQosMbrDlValue. Values: 0,
1D-8D. The 0 settings pecies that HLR’s bit rate value in all PDP
contexts is overridden, if the hlrQosMbrDlValue parameter
denes a bit rate value.
hlrQosMbrUlLimit HLR QoS maximum bit rate for uplink override limit. If the UL MBR
received from the HLR in PDP context’s QoS parameter is equal or
greater than value of this parameter, the maximum bit rate for
uplink value received from HLR is replaced with bit rate value
dened in parameter hlrQosMbrUlValue. Bit rate value is
given as megabits per second. The parameter value 0 means that
HLR’s bit rate value in all PDP contexts is overridden, if parameter
hlrQosMbrUlValue denes new bit rate value.
4 Verify that the feature is enabled.
cmm prFile show hlrQosMbrDlValue

cmm prFile show hlrQosMbrUlValue
Step result
The output should show that hlrQosMbrDlValue and hlrQosMbrUlValue
parameters are set to 1.
Note:
if the value displayed for Status is false, it does not mean that the feature is
enabled.
7.11 Detach timer optimization and control (Features

SG01080, SG01089, SG01197 and SG02035): feature
summary
The detach timer (Features SG01197 and SG02035) functionality optimizes the SGSN
resource utilization by removing loitering subscribers. The selective detach timer
(Feature SG01089) minimizes the unnecessary signaling thus increasing the system and
radio capacity. IMEI restricted detach timer (Feature SG01080) prevents the of accidental

SGSN User Guide
detach of MEs do not interwork properly with the detach timer.
Table 119: Detach timer optimization and control (Feature SG01080, SG01089, SG01197 and
Function Impact
Capacity None
Interworking/dependent • GPRS Mobility management (SG01011)

features • GPRS Session management (SG01012)
• IMEI check with EIR (SG01090)
Restrictions • The maximum IMEI/TAC values that can be stored in the

database is 100.
• This feature can handle only full 8-digit TAC values, which means
that variable length TAC values cannot be congured.
• The IMEI check functionality must be activated for attaches and
inter-SGSN routing area updates.
• In selective detach timer functionality a subscriber place is
reserved by inactive MS congured as "always-online" that re-
attach automatically after a network-initiated detach.
• Removing inactive subscribers with PDP context is not possible.
Conguration management Command tac

Command sgnsTimer, parameter detachTimer
Command features, parameters sgsnDetachTimer,
imeiRestrDetTimer, selDetachTimer
Counters GPRS Mobility Management (001):

• M001C186 / NUMBER OF INACTIVE RE-ATTACHED ALWAYS-
ONLINE SUBSCRIBER NOTICES
• M001C055 / MOBILE SUBSCRIBERS DETACHED BECAUSE OF
DETACH TIMER FOR INACTIVE USERS
Alarms None
Feature ID Detach timer (Features SG01197 and SG02035), IMEI restricted

detach timer (Feature SG01080), Selective detach timer (Feature
SG01089).
7.11.1 Configuring detach timer

With this feature, the SGSN resources are utilized in the optimal way by removing inactive

SGSN User Guide
subscribers via the detach procedure. When the detach timer expires, a network-initiated
detach is done. IMEI restricted detach timer and Selective detach timer are enhancements
to the Detach timer feature. To use these features, you need to activate the detach timer.
Procedure
1 Activate thedetach timer feature.
When the detach timer functionality is in use, SGSN starts a timer for each attached
subscriber. The detach timer is stopped if the subscriber activates a PDP context and it
is restarted when the subscriber deactivates the last PDP context. When the detach
timer expires, a network-initiated detach is done. In the network-initiated detach, the
MS is informed that re-attach is not required (detach type is 're-attach not required')
and only GPRS service is detached (no cause is included).
cmm features modify sgsnDetachTimer --status true
2 Configure detach timer value.
cmm sgsnTimer modify --detachTimer <integer>
The value range is 0 - 1440 minutes.
3 If needed, activate the feature IMEI restricted detach timer.
IMEI restricted detach timer enhances the detach timer for inactive subscribers as it
allows mobile stations (MS) with certain IMEI type allocation code (TAC) to be excluded
from the detach timer functionality.
It is done by configuring TAC parts of IMEIs to IMEI/TAC database. Up to 100 different

IMEI/TAC fields can be configured to the database. The configured IMEI/TAC fields are
8-digit long. When subscriber’s detach timer expires, mobility management checks if the
IMEI/TAC of the ME is found in the IMEI/TAC database. If a match is found, the
subscriber is not detached from the system. If a match is not found, the detach timer
functionality proceeds normally.
The use of IMEI restricted detach timer feature requires that the IMEI check
functionality is set on for all attaches and inter-SGSN routing area updates.
To activate IMEI restricted detach timer: cmm features modify

imeiRestrDetTimer --status true
Step example
Activate IMEI checking: cmm securityParam modify config --imeiCheckMode

SGSN User Guide
true
Set the IMEI check counter for GPRS attach to value ‘1’: cmm plmnParam modify
HOME --gbGprsAttImei 1
Enable IMEI check from EIR for GPRS attach: cmm plmnParam modify HOME --
gprsAttImeiChk true
Create the type allocation codes (TAC) of the subscriber to the database. This code
consists of the first eight digits of the mobile station’s IMEI code: cmm tac create
12345678
Activate detach timer and activate IMEI restricted detach timer (command features,
as above).
4 If needed, activate the feature selective detach timer.
Selective detach timer checks if the subscriber re-attaches within 20 seconds after a
network-initiated detach due to detach timer expiry. In that case, the MS is marked as
an inactive re-attached mobile station (MS) user. In every case when the detach timer is
supposed to be started, it is first checked whether the subscriber is marked as an
inactive re-attached mobile station (MS) user or not. If so, the detach timer is not
started (again) for these inactive MSs configured as mobile station (MS).
cmm features modify selDetachTimer --status true
7.12 Signalling reduction for stationary devices (M2M)

(Feature SG01257): feature summary
With this feature, the operator can reduce signalling for stationary, low mobility or low
priority machine-to-machine (M2M) devices.

SGSN User Guide
Table 120: Signalling reduction for stationary devices (M2M) (Feature SG01257): feature
summary
Function Impact
Capacity None
Interworking or dependent • Subscriber authentication (Feature SG01011)

features • GPRS session management (Features SG01012, SG01068
and SG02157)
Restrictions None
Conguration management Command features, parameter signalReductM2m
Counters None
Alarms None
Feature ID SG01257
7.13 SGSN abnormal signaling reduction (Feature

This feature enables the operator to monitor the number of PDP context activation
requests coming from the UE at a monitoring period. When the feature is enabled, then
all subscribers are monitored for abnormal signaling behavior.
Table 121: SGSN abnormal signaling reduction (Feature SG01259): feature summary
Function Impact
Capacity None

SGSN User Guide
Function Impact
Restrictions When the conguration values of the abnormal

signaling mechanism are strict, that is, too
small, then respective PDPs will be rejected.
Operator must carefully apply the abnormal
signaling conguration, otherwise this may lead
to PDP activation rejections from all users.
Default values are selected so that a 3GPP-
dened retransmission rate is not considered
abnormal. Abnormal signaling rate varies
among operators, therefore abnormal signaling
conguration must be carefully considered, in
order to address the operator's needs based
on radio conguration, network dimensioning,
smartphone penetration and other factors.
Daylight time changes are automatically
considered.
Conguration management Command cmm system modify,

parameters pdpActProcMonitoring,
procAttemptsInterval,
numbOfProcAttempsInInterval
Command cmm features modify,
parameter signalReductM2m

• M021C123 / PDP ACTIVATIONS DROPPED SUM
• M021C124 / PDP ACTIVATIONS DROPPED DEN
• M021C125 / MIN PDP ACTIVATIONS DROPPED
• M021C126 / PEAK PDP ACTIVATIONS
DROPPED
Alarms None
Feature ID SG01259
7.14 Paging optimization enhancement (Feature

The Paging optimization enhancement feature introduces I-BTS as a network element
which incorporates the functionalities of the RNC, and the concepts of Paging Master I-
BTS (PM IBTS) and Paging Standby I-BTS (PS I-BTS), which can be configured in the SGSN.
The SGSN sends the paging messages to the PM I-BTS. The PM I-BTS in the SGSN radio
network configuration is responsible for forwarding paging messages over the Iur
interface to other I-BTSs so that the entire routing area is covered for the search and

SGSN User Guide
paging operation. The benefits of paging optimization are reduced PAPS processor load,
reduced SGSN transactions, and reduced load on the RANAP signaling links. The feature
requires configuration.
Table 122: Paging optimization enhancement (Feature SG02204): feature summary
Function Impact
Compliance 3GPP TS 25.999 High Speed Packet Access (HSPA) evolution; Frequency
Division Duplex (FDD)
3GPP TS 25.413 UTRAN Iu interface Radio Access Network Application
Part (RANAP) signaling
3GPP TS 25.415 UTRAN Iu interface user plane protocols
Capacity A maximum of 512 I-BTSs can be congured in SGSN.
features
Restrictions I-BTSs in I-HSPA access should also be congured as groups so that

the master, stand-by and normal I-BTS nomenclature is understood by
the I-BTSs. This means that the I-HSPA RNC should also support
paging optimization, so that the SGSN’s paging group conguration
matches the RNC’s paging group conguration.
Conguration Command features, parameter pagingOpt

management Command sgsnPagingGroupList
Command sgsnPagingGroup
Counters None
Alarms None
Feature ID SG02204
7.14.1 Configuring paging optimization enhancement

The feature can be activated using the pagingOpt parameter. In addition, you need to
configure paging groups with I-HSPA RNCs having roles of master, standby, and group
member.
Procedure
1 Check feature status.

SGSN User Guide
cmm features show pagingOpt
Step example
+-----------+----------------------------------+
| Field | Value |
+-----------+----------------------------------+
| features | pagingOpt |
| status | false |
| parameter | Paging Optimization Enhancements |
+-----------+----------------------------------+
2 Activate paging optimization.
cmm features modify pagingOpt --status true
3 Create I-HSPA RNCs to be included in paging group.
4 Create a paging group.
Use the sgsnPagingGroupList command. Parameters
name Paging group name
groupId Paging group id
Step example
cmm sgsnPagingGroupList create --name PAG1 --groupId 1
5 Add one I-HSPA RNC into the paging group as Master.
Use the sgsnPagingGroup command. Parameters
groupId GroupId of RNC (1 - 4900)
rncRole RNC role in group: 1 Normal, 2 Master, 3 Standby
rncName RNC name. This parameter should match parameter rncName of

the rnc command.

SGSN User Guide
Step example
cmm sgsnPagingGroup create --groupId 1 --rncName RNC1 --rncRole 2
6 Add more I-HSPA RNCs into the paging group.
Step example
cmm sgsnPagingGroup create --groupId 1 --rncName RNC2
cmm sgsnPagingGroup create --groupId 1 --rncName RNC3
7 Add one I-HSPA RNC into the paging group as Standby.
Step example
cmm sgsnPagingGroup create --groupId 1 --rncName RNC4 --rncRole 3
8 Verify the configuration.
Output paging optimization configuration using commands:
cmm sgsnPagingGroupList list
cmm sgsnPagingGroup list
Result
When the provisioning task is completed, and paging request is triggered towards Master I-
HSPA RNC:
Master I-HSPA RNC forwards paging request to all the member of I-HSPA RNCs.
Serving I-HSPA RNC communicates with MS and responds back with service request
message with service type as ‘Paging response’ to SGSN.
7.15 PDP context mass deactivation protection (Feature

This feature allows configuring sending of PDP context deactivation messages towards
mobile stations. Thus, mobile stations receive PDP context deactivations in a controlled
way, and the radio network is not subjected to overload.

SGSN User Guide
Table 123: PDP context mass deactivation protection (Feature SG01096): feature summary
Function Impact
Capacity None

features
Restrictions Setting the mass deactivation speed too high can cause
overload in radio network.
CLI commands Feature activation command: cmm features modify,

parameter: pdpCtxMassDea
Prle conguration command: cmm prFile modify,
parameters: pdpCntxMassDeactAct,
pdpCntxMassDeactSpd
Counters None
Alarms None
Feature ID SG01096
7.16 Cause code mapping (Feature SG01141)

The feature Cause code mapping gives the operator the possibility to modify the cause
codes sent to mobile stations in situations when a different kind of cause code is needed
than the default SGSN implementation offers.
The operator can define several different cause code sets - a new set is created with default
mappings. In these cause code sets, the operator can change the existing cause code values
by giving new procedures and internal and external causes to be sent to mobile stations.
User defined cause code sets can be taken into use by defining it in the PLMN parameters.
Cause code sets can also be used according to the IMEI analysis. With this feature, a special
IMEI analysis can be created in the SGSN. If the IMEI with a user defined cause code set is
found from the analysis, IMEI specific cause codes are in use. If the IMEI with a user defined
cause code set is not found, the PLMN specific cause codes are used.
The default cause code set is used when:

there are no user-specific cause code sets defined for the PLMN nor in the IMEI analysis.

SGSN User Guide
user defined cause code set for the PLMN has not been modified after the cause code
set has been created, and the IMEI analysis does not exist for the mobile station.
user defined cause code set for the PLMN is given 0 as the cause code set name.
user defined cause code set in the IMEI analysis has not been modified after the cause
code set has been created.
user defined cause code set in the IMEI analysis is given 0 as the cause code set name.
It is recommended that also the values of the following SGSN parameters are set to true:
imeiCheckMode, command cmm securityParam modify --imeiCheckMode
true config
imeiRequestMode, command cmm securityParam modify --imeiRequestMode
true config
It is recommended that the values of the following PLMN parameters are set to 1:
IMEI check repetition rate for GPRS attach (gbGprsAttImei/iuGprsAttImei),
commands:cmm plmnParam modify <PLMN NAME> --gbGprsAttImei 1, cmm
plmnParam modify <PLMN NAME> --iuGprsAttImei 1
IMEI check repetition rate for normal RA update, new visitor

(gbNormRaImeiVisitor/iuNormRaImeiVisitor), commands: cmm plmnParam
modify <PLMN NAME> --gbNormRaImeiVisitor 1, cmm plmnParam modify
<PLMN NAME> --iuNormRaImeiVisitor 1
This ensures that the subscriber's IMEI is available when the subscriber enters the SGSN, and
thus the feature can be used for this IMEI.
The cause code mapping feature is optional. The feature parameter responsible for
activation/deactivation is ccMapping, command: cmm features modify ccMapping -
-status {true, false}.
Parameters
The following prFile parameters are affected. The value of parameter dnsFailureCause
has no effect because the same functionality can be achieved by modifying the mapping
settings. The table shows how to modify cause code mapping to get the same functionality
when this feature is active. The value of parameter cancelLocationCc affects cause code
mapping in detach request, but the cause code in attach reject request can be changed.

SGSN User Guide
Table 124: PRFILE parameters affected by cause code mapping
Parameter Description Required CC mapping
dnsFailureCause When a DNS error is detected in false: Default mapping

the internal SGSN RAU, and if true: Map Rau reject internal
the parameter indicates that the cause 92 to external cause 10
change is required, the cause When cause code mapping
code returned to the mobile feature is OFF, enabling this
station is changed from parameter maps the external
Protocol error, cause code as implicitly
unspecified to detached (10). In order to have
Implicitly detached. the similar behavior after
enabling this cause code
mapping feature, we need to
modify this internal cause 92
(0x5C-unknown_dns_c) to
external cause 10 (implicitly
detached) using cause code
mapping feature.
cancelLocationCc When the HLR sends a cancel false: Detach is sent with the
location message to SGSN, SGSN cause code 7.
shall send the detach message true: Detach is sent without the
without cause code value and cause code. Reject code in
reject the following attach attach reject can be changed by
attempt with the cause modifying cause code
code111. In the current mappings.
implementation, the SGSN uses When cause code mapping
cause code value 7 in detach feature is OFF, enabling this
reject. parameter maps the external
cause code as protocol error
(#111). In order to have the
similar behavior after enabling
this cause code mapping
feature, we need to modify this
internal cause 0x30
(no_gprs_subscr_c) to external
cause 0x6F(protocol error) using
cause code mapping feature.
Table 125: UTPFIL parameters affected by cause code mapping

Parameter Description Required CC mapping
0x04Controlled roaming cause to MS When this UTPFIL patch is used with value = 1, the external If the cause code mapping feature is activated, these internal
cause code to MS will be #14 ’GPRS services not causes
allowed in this PLMN’ for internal causes sg_err_t_contr_roaming_rej_c/sg_err_t_contr_roam_rl97_rej_c
sg_err_t_contr_roaming_rej_c/sg_err_t_contr_roam_rl97_rej_c. should be set to external cause 14(to have similar behavior
If this is used with value = 2, the external cause to MS will be as when the UTPFIL parameter is used with value = 1) for
#13 ’Roaming not allowed in this location attach and RAU reject procedures.
area’ for internal causes These internal causes
sg_err_t_contr_roaming_rej_c/sg_err_t_cont sg_err_t_contr_roaming_rej_c/sg_err_t_contr_roam_rl97_rej_c
r_roam_rl97_rej_c should be set to external cause 13 (to have similar behavior
as when the UTPFIL parameter is used with value = 2) for
attach and RAU reject procedures.

SGSN User Guide
7.16.1 Configuring cause code mapping

Activate the cause code mapping feature and define a cause code set.
Procedure
1 Activate the cause code mapping feature.
cmm features modify ccMapping --status true
2 Define the cause code set.
2.1 Create a cause code set.
cmm causeCodeSets create <NAME>

where:
NAME name of the cause code set. It is a string of length 1-8.
Step example
Create a cause code set with the name gb-set
cmm causeCodeSets create gb-set
2.2 Modify a cause code set value.
cmm causeCodeSets modify <NAME> --proc <PROC> --intCause

<INTCAUSE> --extCause <EXTCAUSE>
where:
NAME name for the cause code set
PROC procedure identier
INTCAUSE internal cause

SGSN User Guide
EXTCAUSE external cause
Step example
Modify the external cause value from the default value to 2 and the internal
cause code value to 1 in the procedure "attach accept causes" of the cause code
set gb-set.
cmm causeCodeSets modify gb-set --proc attAcc --intCause 1

--extCause 2
7.16.1.1 Configuring the cause code set for PLMN

To configure the cause code set for PLMN, use the plmnParam command.
Procedure
1 Modify the PLMN-specific cause code set parameters.
cmm plmnParam modify <PLMN> --gbCauseCodeRec <GBREC> --

iuCauseCodeRec <IUREC>
where:
PLMN name of the PLMN
GBREC The cause code set for Gb interface. Default value is 0.
IUREC the cause code set for iu interface. Default value is 0.
Step example
Modify the PLMN cause code set parameters of the OWN_PLMN
cmm plmnParam modify own_plmn --gbCauseCodeRec gb-set --

iuCauseCodeRec 0

SGSN User Guide
7.16.1.2 Configuring the IMEI analysis

To configure the cause code sets according to the IMEI analysis, use the imeiAnalysis
command.
Procedure
1 Create an IMEI analysis table to specify devices that will receive the user defined
cause code values by the cause code mapping feature.
cmm imeiAnalysis create =<IMEI value> --ccgb <ccgb feature value>

--cciu <cciu feature value> --gbset < GBREC> --iuset < IUREC>
where:
ccgb feature value True for IMEI-based cause code mapping for the Gb interface
cciu feature value True for IMEI-based cause code mapping for the Iu interface
GBREC cause code set name for Gb interface. Must also set –ccgb to true
IUREC cause code set name for iu interface. Must also set –cciu to true
Step example
cmm imeiAnalysis create 12345679 --cciu true --iuset iu-set
Step example
cmm imeiAnalysis create 12345678 --ccgb true --gbset gb-set

SGSN User Guide
7.16.2 Cause code mapping (Feature SG01141): feature

summary
This feature enables the operator to modify the cause codes sent to mobile stations in
situations when a different kind of cause code is needed than the default SGSN
implementation offers.
Table 126: Cause code mapping (Feature SG01141): feature summary
Function Impact
Capacity None

features
Restrictions There can be a maximum of 20 user dened cause code

mapping sets. Only the external cause code values dened in
3GPP specication 24.008 can be used. In the HLR/HSS-
initiated detach internal, the cause 41 (IMSI_U_IN_HLR) is
mapped to the external cause 2 (IMSI UNKOWN IN HLR) by
default. In the SGSN and GGSN-initiated detach internal, the
cause 41 is mapped to the external cause 8 (OPERATOR
DETERMINED BARRING). This is the only case where one
internal cause can be mapped to two different external
causes depending on the initial cause.
Conguration management Command plmnParam, parameters gbCauseCodeRec and

iuCauseCodeRec
Command causeCodeSets, parameters proc,
intCause, extCause
Command imeiAnalysis, parameters ccgb, cciu,
gbset, iuset

SGSN User Guide
Function Impact
Counters None
Note:
When Cause code mapping feature is ON, then all the

cause code based counters are updated on the old
external cause code only, not on the modied external
cause code. For example if internal cause 0xF3
(no_rsp_from_rnc_c) is modied to 0x0A
(implicitly_detached) using cause code mapping feature,
then external cause code counter will still be incremented
on 0x6F (protocol_err_c).
Alarms None
Feature ID SG01141
7.17 Provisionable reject cause when mobility event is

rejected with GMM error codes CC11..15 (Feature
With this feature, the SGSN is able to map the reject cause value when the CS/PS
coordination is used and mobility event is rejected with GMM error codes 11, 12, 13, 14
and 15.

SGSN User Guide
Table 127: Provisionable reject cause when mobility event is rejected with GMM error codes
CC11..15: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions Only for GMM error codes 11, 12, 13, 14 and 15.
Conguration Command gParms, parameters rejectCcForGmmErrorCode11,

management rejectCcForGmmErrorCode12,
rejectCcForGmmErrorCode13,
rejectCcForGmmErrorCode14 and
rejectCcForGmmErrorCode15
Counters None
Alarms None
7.17.1 Configuring reject cause values for mobility event

rejected with GMM error codes 11, 12, 13, 14, and 15
Use global parameters rejectCcForGmmErrorCode11,
rejectCcForGmmErrorCode12, rejectCcForGmmErrorCode13,
rejectCcForGmmErrorCode14, andrejectCcForGmmErrorCode15 to configure the
reject cause values.
Before you start
The possible values and descriptions of commands rejectCcForGmmErrorCode11,

rejectCcForGmmErrorCode12, rejectCcForGmmErrorCode13,
rejectCcForGmmErrorCode14, andrejectCcForGmmErrorCode15 are listed in the
following tables:

SGSN User Guide
Table 128: Values of rejectCcForGmmErrorCode11
Value Description
psCsCoordinationRequired This parameter denes that PS/CS registration coordination required

(default) reject cause value will be used for GMM error code 11.
plmnNotAllowed This parameter denes that PLMN not allowed reject cause value will be
used for GMM error code 11.
locationAreaNotAllowed This parameter denes that Location area not allowed reject cause value
will be used for GMM error code 11.
roamingNotAllowedInLocatio This parameter denes that Roaming not allowed in location area reject
nArea cause value will be used for GMM error code 11.
noSuitableCellInLocationArea This parameter denes that No suitable cell in location area reject cause
value will be used for GMM error code 11.
gprsServicesNotAllowed This parameter denes that GPRS services not allowed in this PLMN
reject cause value will be used for GMM error code 11.
Value Description

Reject Cause value will be used for GMM error code 12.
(default) will be used for GMM error code 12.

SGSN User Guide
Value Description

nArea (default) cause value will be used for GMM error code 13.
Value Description

(default) reject cause value will be used for GMM error code 14.

SGSN User Guide
Value Description

(default) value will be used for GMM error code 15.
Procedure
1 Set the reject cause value to PLMN not allowed for GMM error code 11.
Step example
cmm gParms modify --gParmValue plmnNotAllowed
2 Set the reject cause value to PS/CS registration coordination required for GMM error
code 12.
Step example
cmm gParms modify --gParmValue psCsCoordinationRequired
3 Set the reject cause value to No suitable cell in location area for GMM error code 13.
Step example
cmm gParms modify --gParmValue noSuitableCellInLocationArea

SGSN User Guide
7.18 P-GW node name delivery on SGSN (Feature

The feature prevents MME network element from performing reverse DNS lookup queries
for retrieving the P-GW FQDN during S-GW selection.
Table 133: P-GW node name delivery on SGSN (Feature SG01263): feature summary
Function Impact
Compliance 3GPP TS 29.060, General Packet Radio Service (GPRS), GPRS Tunnelling
Protocol (GTP) across the Gn and Gp interface V13.1.0 and CR719
Capacity None
Interworking/dependent R8 DNS query support for Gn-SGSN (Feature SG02213)

features
Restrictions Only for home subscribers.
Conguration Command cmm prFile modify, parameter:

management ggsnPgwFqdnIeCtrl
Counters None
Alarms None
Feature ID SG01263
7.19 Configurable GTP timers in SGSN (Features SG01029

and SG01249): feature summary
With the feature, it is possible to have separate N3/T3 timers for roaming subscribers
without any impact to the N3/T3 values of home users.

SGSN User Guide
Table 134: Configurable GTP timers in SGSN (Features SG01029 and SG01249): feature
summary
Function Impact
Capacity None

features
Restrictions None
Conguration management Commands sgsnLocalEndPtCfg, gtpTimer,

plmnParam.
Command features, parameter extdGtpTmrRoaming
Counters None
Alarms None
Feature ID SG01029, SG01249
7.19.1 Configuring GTP timers

Use command sgsnLocalEndPtCfg to provision GTP timers for home subscribers and
command gtpTimer to provision GTP timers for roamers. Use command plmnParam to
associate GTP profiles per PLMN.
Before you start
Note:
The sgsnLocalEndPtCfg command configures the default values for N3/T3 timers.
The values of GTP timers for roamers supersede the default N3/T3 values used when
the feature SG01249 (extdGtpTmrRoaming) is activated. If no modification is made
using thegtpProfile command, the GTP timer values for roamer are the default.
Procedure
1 Provision N3/T3 parameters for home subscribers.

SGSN User Guide
1.1 Show timer values.
Step example
Note:
This command is also used with identifier S4 and S3S16 (the settings in
each case are different).
# cmm sgsnLocalEndPtCfg show GNSGSN
+-------------------+--------------------+
| Field | Value |
+-------------------+--------------------+
| sgsnLocalEndPtCfg | GNSGSN |
| t3tunnel | 20 |
| gni | TTCN3.A.P.N |
| gni6 | |
| gniv4v6 | |
| goi | MNC002.MCC460.GPRS |
| secgni | |
| secgni6 | |
| secgniv4v6 | |
| n3CreatePdp | 5 |
| t3CreatePdp | 3 |
| n3UpdPdp | 5 |
| t3UpdPdp | 3 |
| n3DelPdp | 5 |
| t3DelPdp | 3 |
| n3Id | 5 |
| t3Id | 3 |
| n3SgsnCtxt | 5 |
| t3SgsnCtxt | 3 |
| n3ForwReloc | 5 |
| t3ForwReloc | 3 |
+-------------------+--------------------+
1.2 Modify N3/T3 timer values.

SGSN User Guide
Step example
cmm sgsnLocalEndPtCfg modify GNSGSN --n3CreSession 5 --
t3CreSession 3
2 Provision GTP timers for roaming subscribers.
Step example
#cmm gtpTimer create 1
+--------------------------+-------+
| Field | Value |
+--------------------------+-------+
| gtpTimer | 1 |
| gtptmrPrName | |
| gtptmrInUse | false |
| gtptmrN3PdpCreReqCounter | 5 |
| gtptmrT3PdpCreRespTimer | 3 |
| gtptmrN3PdpUpdReqCounter | 5 |
| gtptmrT3PdpUpdRespTimer | 3 |
| gtptmrN3CreSesReqCounter | 5 |
| gtptmrT3CreSesRespTimer | 3 |
| gtptmrN3ModBeaReqCounter | 5 |
| gtptmrT3ModBeaRespTimer | 3 |
+--------------------------+-------+
3 Associate GTP profile per PLMN.
Parameter gtpTmrprId is GTP timer profile id (0...255).
Step example

SGSN User Guide
#cmm plmnParam modify --gtpTmrprId 1 --plmnParamId ROAMINGPLMN
+----------------------------+-------------+
| Field | Value |
+----------------------------+-------------+
| plmnParam | ROAMINGPLMN |
| plmnParamId* | ROAMINGPLMN |
| homePlmn | false |
| gtpTmrprId | 1 |
| gbMncl | 2 |
| gbGprsAttAuth | 1 |
| gbImsiAttAuth | 1 |
| gbNormRaAuthVisitor | 0 |
| gbNormRaAuth | 0 |
| gbPeriodicRaAuth | 0 |
| gbMoPdpActAuth | 0 |
| gbMoPdpDeaAuth | 0 |
...
| tcForQci3 | 10 |
| tcForQci4 | 10 |
| tcForQci5 | 10 |
| tcForQci6 | 10 |
| tcForQci7 | 10 |
| tcForQci8 | 10 |
| tcForQci9 | 10 |
+----------------------------+-------------+
4 Check control plane Echo Request and Echo Response timer values.
For Echo Request and Echo Response timer values, IPDS uses local endpoint
configuration to identify the GTP profile and then the GTP profile to get the values.
Step example
Show local endpoint configuration:

SGSN User Guide
# cmm localEndPtCfg show GNSGSN
+---------------------+--------+
| Field | Value |
+---------------------+--------+
| localEndPtCfg | GNSGSN |
| interfaceName* | GN |
| dscpCode | AF11 |
| avRequested | 0 |
| sctpOutboundStreams | 1 |
| sctpInboundStreams | 1 |
| interfaceLabel | GN |
| description | |
| protocolProfileName | 2 |
| interfacePort | 0 |
| multiHomed | false |
| comboIndication | false |
| shutdown | false |
| immRspPref | No |
+---------------------+--------+
Display protocolProfileName = 2 to see the values for Echo Request and Echo
Response messages.
# cmm gtpProfile show 2
+--------------------------------+-------+
| Field | Value |
+--------------------------------+-------+
| gtpProfile | 2 |
| name* | 2 |
| description | |
| sendEchoTimerT3 | 60000 |
| waitEchoTimerT3 | 6000 |
| echoRequests | 9 |
| retransTimerT3 | 6000 |
| numTransmits | 3 |
...
sendEchoTimerT3 is the delay for Echo Request when Echo Response is received.
waitEchoTimerT3 is the delay for Echo Request when Echo Response is not

SGSN User Guide
received.
echoRequests is the number of failed Echo Requests before the alarm is
generated.
5 Activate S4/Gn interface SGSN extended GTP timers for roaming.
Parameter extdGtpTmrRoaming enables CMM to use different GTP N3/T3 values for
the GTP-C messages for roamer subscribers only.
cmm features modify --status true extdGtpTmrRoaming
Example of creating a GTP timer profile and associating it with a PLMN

1. Create new profile:
cmm gtpTimer create -–gtptmrPrName GTPTM 3
2. Modify profile:
cmm gtpTimer modify --gtptmrInUse true --gtptmrN3PdpCreReqCounter
3 --gtptmrT3PdpCreRespTimer 5 3
3. Configure the table index under the visitor PLMN (ROAMINGPLMN):
cmm plmnParam modify --plmnParamId ROAMINGPLMN --gtpTmrprId 3
7.19.2 GTP timers for home users (sgsnLocalEndPtCfg)

These GTP timers for home users are configurable through the sgsnLocalEndPtCfg
command.
Table 135: GTP timers for homers (sgsnLocalEndPtCfg)
Parameter Description Values
n3CreatePdp This parameter denes the value for the counter 1...7,
that holds the maximum number of attempts default 5
made by the GPRS tunnelling protocol (GTP) to
send a create PDP context request message. Valid
for GNSGSN.
t3CreatePdp This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a create PDP default 3 s
context response message to a create PDP context
request message. Valid for GNSGSN.

SGSN User Guide
n3UpdPdp This parameter denes the value for the counter 1...7,
send an update PDP context request message.
Valid for GNSGSN.
t3UpdPdp This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for an update default 3 s
PDP context response message to an update PDP
context request message. Valid for GNSGSN.
n3DelPdp This parameter denes the value for the counter 1...7,
send a delete PDP context request message. Valid
for GNSGSN.
t3DelPdp This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a delete PDP default 3 s
context response message to a delete PDP context
n3Id This parameter denes the value for the counter 1...7,
send an identication request message. Valid for
GNSGSN.
t3Id This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for an default 3 s
identication response message to an
identication request message. The values range
from 1 to 10 seconds in 1 second steps. Valid for
GNSGSN.
n3SgsnCtxt This parameter denes the value for the counter 1...7,
send an SGSN context request message. Valid for
GNSGSN.
t3SgsnCtxt This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for an SGSN default 3 s
context response message to an SGSN context
n3ForwReloc This parameter denes the value for the counter 1...7,
send a forward relocation request message. Valid
for GNSGSN.

SGSN User Guide
t3ForwReloc This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a forward default 3 s
relocation response message to a forward
relocation request message. Valid for GNSGSN.
n3EchoUP This parameter denes the value for the counter 1...7,
send an echo request message concerning user
plane. The values range from 1 to 7. Valid for
GNSGSN.
t3EchoUP This parameter denes the value for the timer that 3...15
holds the maximum waiting time for an echo s,default 3
response message to an echo request message s
concerning user plane. Valid for GNSGSN.
n3Ctxtv2 This parameter denes the value for the counter 1...7,
made by the GPRS tunneling protocol v2 (GTPv2) to
send a context request message. Valid for S3S16.
t3Cnxtv2 This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a context default 3 s
response message to a context request message
(GTPv2). Valid for S3S16.
n3Idv2 This parameter denes the value for the counter 1...7,
send a identication request message. Valid for
S3S16.
t3Idv2 This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a default 3 s
identication response message to a identication
request message (GTPv2). Valid for S3S16.
n3ForwRelocv2 This parameter denes the value for the counter 1...7,
send a forward relocation request message. Valid
for S3S16.
t3ForwRelocv2 This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a forward default 3 s
relocation request message to a forward relocation
response message (GTPv2). Valid for S3S16.

SGSN User Guide
n3RelocCancelv2 This parameter denes the value for the counter 1...7,
send a relocation cancel request message. Valid for
S3S16.
t3RelocCancelv2 This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a relocation default 3 s
cancel response message to a relocation cancel
request (GTPv2). Valid for S3S16.
n3CreSession This parameter denes the value for the counter 1...7,
made by the GPRS tunneling protocol V2 (GTPv2)
to send a create session request message. Valid
for S4.
t3CreSession This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a create default 3 s
session response message to a create session
request message. Valid for S4.
n3ModBearer This parameter denes the value for the counter 1...7,
send a modify bearer request message. Valid for
S4.
t3ModBearer This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a modify default 3 s
bearer response message to a modify bearer
n3DelSession This parameter denes the value for the counter 1...7,
send a delete session request message. Valid for
S4.
t3DelSession This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a delete default 3 s
session response message to a delete session
n3CreIndDataFwdTunne This parameter denes the value for the counter 1...7,
l that holds the maximum number of attempts default 5
send a create indirect data forwarding tunnel

SGSN User Guide
t3CreIndDataFwdTunne This parameter denes the value for the timer that 1...10 s,
l holds the maximum waiting time for a create default 3 s
indirect data forwarding tunnel response message
to a create indirect data forwarding tunnel request
message. Valid for S4.
n3DelIndDataFwdTunne This parameter denes the value for the counter 1...7,
l that holds the maximum number of attempts default 5
send a delete indirect data forwarding tunnel
t3DelIndDataFwdTunne This parameter denes the value for the timer that 1...10 s,
l holds the maximum waiting time for a delete default 3 s
indirect data forwarding tunnel response message
to a delete indirect data forwarding tunnel request
message. Valid for S4.
n3RelBearer This parameter denes the value for the counter 1...7,
send a release access bearer request message.
Valid for S4.
t3RelBearer This parameter denes the value for the timer that 1...10 s,
holds the maximum waiting time for a release default 3 s
access bearer response message to a release
access bearer request message. Valid for S4.
IndDataFwdTimer This timer is used to determine the duration for 1...10 s,

which Indirect Data Forwarding Tunnel will be default 3 s
established during a Handover Procedure. Valid for
S4.
7.19.3 GTP timers for roamers (gtpTimer)

These GTP timers for roamers are configurable through the gtpTimer command. These
timers are used for PLMNs that are mapped to one of the six available gtpTimer profiles.
Table 136: Configurable GTP timers for roamers (gtpTimer)

SGSN User Guide
gtptmrN3PdpCreReqCounter This parameter denes the value for the 1...7,

counter that holds the maximum number of default 5
attempts made by the GPRS tunnelling
protocol (GTP) to send a create PDP context
request message.
gtptmrT3PdpCreRespTimer This parameter denes the value for the 1...10 s,

timer that holds the maximum waiting time default 3 s
for a create PDP context response message
to a create PDP context request message.
gtptmrN3PdpUpdReqCounter This parameter denes the value for the 1...7,

attempts made by the GPRS tunnelling
protocol (GTP) to send an update PDP
context request message.
gtptmrT3PdpUpdRespTimer This parameter denes the value for the 1...10 s,

for an update PDP context response
message to an update PDP context request
message.
gtptmrN3CreSesReqCounter This parameter denes the value for the 1...7,

attempts made by the GPRS tunneling
protocol V2 (GTPv2) to send a create session
request message.
gtptmrT3CreSesRespTimer This parameter denes the value for the 1...10 s,

for a create session response message to a
create session request message.
gtptmrN3ModBeaReqCounter This parameter denes the value for the 1...7,

attempts made by the GPRS tunneling
protocol v2 (GTPv2) to send a modify bearer
request message.
gtptmrT3ModBeaRespTimer This parameter denes the value for the 1...10 s,

for a modify bearer response message to a
modify bearer request message.

SGSN User Guide
7.20 SGSN support for IPSec on the X3 interface (Feature

This feature provides SGSN support for IPSec on the X3 interface in PAPS and IPPS as it is
already used for X1_1 and X2 interface.
Table 137: SGSN support for IPSec on the X3 interface (Feature f52006-01): feature summary
Function Impact
Compliance None
Capacity Up to 10 IPsec prole entries can be

congured.
Up to 1500 IPsec connection entries can be
congured (100 IPDS + ((20 PAPS + 8 IPPS) x 50
LIBs) = 1500).
When IPSec is in use:
• up to 0.5% of the 2G user plane data can be
intercepted in the PAPS
• up to 30kpps 3G user plane data can be
intercepted per IPPS.
Interworking/dependent features f60210-14 SGSN support for Lawful

Interception (LIPv2) Functionality
f60110-13 FNS support for Lawful Intercept
Port
Restrictions This feature is only applicable with LIPv2

protocol.
Conguration management Commands ipsecProfile and

ipsecConn.
Counters None
Alarms 3152 LibConnectionFailure
7.20.1 Configuring IPsec on X3 interface for the SGSN

Use command ipsecProfile to create an IPsec profile, command ipsecConn to create
an IPsec connection using the created IPsec Profile and command ipsecConn to enable
IPsec connection.

SGSN User Guide
Before you start
Up to ten IPsec profile entries can be configured.
Up to 1500 IPsec connection entries can be configured.
In case that the connection in X3_2G /X3_3G interface cannot be established with alarm
3152 LibConnectionFailure, disable IPsec in both ends and check if the connection
can be established. If it can be established, check the IPsec configuration in both ends.
Procedure
1 Create an IPsec profile.
Table 138: Values and description of command ipsecProfile
Parameter name Description
ipsecProfileId Each IPsec prole entry needs a unique

ipsecProfileId value (from 1 to 10).
ikeAlg This parameter is set to a comma separated list of

<cipher>[-<hash>[;<pfsgroup>]] with the
following supported values:
• cipher values: aes128, aes256 and 3des
• hash values: sha1 and md5
• pfsgroup values: modp1024, modp1536, and
modp2048
ikeLifetime This parameter is set to an integer value (in minutes).

The default value is 60.
phase2Alg This parameter is set to a comma separated list of

<cipher>[-<hash>]. For the list of supported
cipher and hash values, see the ikeAlg parameter
description.
saLifetime This parameter is set to an integer value (in minutes).

ikeVersion This parameter is set to Permit, Never, Propose or

Insist. The default value is Permit.
keyingTries This parameter is set to an integer value. The default

value is 0, indicating unlimited.
dpdDelay This parameter is set to an integer value (in seconds).


SGSN User Guide
Parameter name Description
dpdTimeout This parameter is set to an integer value (in seconds).

dpdAction This parameter is set to Hold, Clear or Restart. The

default value is Hold.
failureHunt This parameter is set to None, PassThrough, Drop or

Reject. The default value is None.
rekeyMargin This parameter is set to an integer value. The default

value is 9.
rekeyFuzz This parameter is set to an integer value (as a

maximum %). The default value is 100.
force This parameter is set to true or false. The default

value is false.
Step example
cmm ipsecProfile create --ikeAlg '3des-sha1;modp1024' --
ikeLifetime 300 --phase2Alg '3des-sha1' --saLifetime 300 --
ipsecProfileId 1
Step result

SGSN User Guide
+-----------------+--------------------+
| Field | Value |
+-----------------+--------------------+
| ipsecProfile | 1 |
| ipsecProfileId* | 1 |
| ikeAlg | 3des-sha1;modp1024 |
| ikeLifetime | 300 |
| phase2Alg | 3des-sha1; |
| saLifetime | 300 |
| ikeVersion | Permit |
| keyingTries | 0 |
| dpdDelay | 30 |
| dpdTimeout | 120 |
| dpdAction | Hold |
| failureHunt | None |
| rekeyMargin | 9 |
| rekeyfuzz | 100 |
| force | false |
+-----------------+--------------------+
2 Create an IPsec connection using the created IPsec profile.
Note:
This command must be given separately for each IPPS and PAPS in order to
establish IPSec for X3 on 2G and 3G.
Table 139: Values and description of command ipsecConn
ipsecConnId Each IPsec Connection entry needs a unique

ipsecConnId value (from 1 to 1500).
connName This parameter is set to a character string up to 32

characters long.
connType This parameter is set to Tunnel or Transport. Default

is Tunnel.

SGSN User Guide
ipsecIntfType This parameter is set to X2 or X1_1 or X3_2G or

X3_3G.
X3_2G should be used when setting PAPS.
X3_3G should be used when setting IPPS
rightIp This parameter is set to the remote IP address for

the IPsec connection.
rightPort This parameter is set to the remote port for the

IPsec connection. Default is 0 (i.e., unspecied).
rightSubnet This parameter is set to the remote subnet for the

IPsec connection.
rightSubnetLen This parameter is set to an integer value indicating

the remote subnet length. Default is 0.
sharedKey This parameter is the shared key string used for

encryption on the IPsec connection.
ipsecProfileId This parameter is the IPsec prole ID to be used for

the IPsec connection.
connEnable This parameter is set to false or true. Default is false.

A dened IPsec connection can be enabled by
changing the connEnable parameter to true.
A dened IPsec connection can be disabled by
changing the connEnable parameter to false.
ipsecPoolType This parameter is set to IPDS or PAPS or IPPS. This

value is indicating the pool service type.
poolId This parameter is set to an integer value (from 0 to

31). This value is indicating the pool identication
number.
Step example
cmm ipsecConn create --ipsecPoolType PAPS --poolId 0 --
ipsecIntfType X3_2G --ipsecProfileId 1 --rightIp 21.100.0.44 --
ipsecConnId 1 --sharedKey "TEST"
Step result

SGSN User Guide
+----------------+--------------------+
| Field | Value |
+----------------+--------------------+
| ipsecConn | 1 |
| ipsecConnId* | 1 |
| connName | IPsec_connection_1 |
| connType | Tunnel |
| ipsecIntfType | X3_2G |
| rightIp | 21.100.0.44 |
| rightPort | 0 |
| rightSubnet | |
| rightSubnetLen | 0 |
| sharedKey | TEST |
| ipsecProfileId | 1 |
| connEnable | false |
| ipsecPoolType | PAPS |
| poolId | 0 |
+----------------+--------------------+
3 Enable IPsec connection.
Step example
cmm ipsecConn modify --connEnable true --ipsecConnId 1
Step result

SGSN User Guide
+----------------+--------------------+
| Field | Value |
+----------------+--------------------+
| ipsecConn | 1 |
| ipsecConnId* | 1 |
| connName | IPsec_connection_1 |
| connType | Tunnel |
| ipsecIntfType | X3_2G |
| rightIp | 21.100.0.44 |
| rightPort | 0 |
| rightSubnet | |
| rightSubnetLen | 0 |
| sharedKey | TEST |
| ipsecProfileId | 1 |
| connEnable | true |
| ipsecPoolType | PAPS |
| poolId | 0 |
+----------------+--------------------+
7.21 SGSN support for detach procedure for implicitly

detached UEs in case of a PAPS failure (Feature
This feature optimizes the service restoration of the 2G and 3G subscribers after a PAPS
reboot.

SGSN User Guide
Table 140: SGSN support for detach procedure for implicitly detached UEs in case of a PAPS
failure (Feature f51025-01): feature summary
Function Impact
Compliance 3GPP TS 44.064 Digital cellular telecommunications system (Phase 2+)

(GSM); Mobile Station - Serving GPRS Support Node (MS-SGSN); Logical
Link Control (LLC) Layer
Capacity None
features
Restrictions The feature is applicable for 2G and 3G subscribers.

management sgsnInformImplicitlyDetachedUEs. By default, the feature is
disabled (value No). The feature is enabled with value Yes.
Counters The feature has impact on the following counters:

• M025C000 / NUMBER OF IU RA LEVEL PAGINGS
• M025C001 / NUMBER OF IU RA LEVEL PAGING PROCEDURES
• M027C000 / NUMBER OF GB RA LEVEL PAGINGS
• M027C001 / NUMBER OF GB RA LEVEL PAGING PROCEDURES
Alarms None

SGSN User Guide
8. S4-SGSN
8.1 Release 8 architecture (Feature SG01235): feature

summary
This feature introduces 3GPP Release 8 architecture support in SGSN to align the network
architecture with LTE EPC (Evolved Packet Core).
Table 141: Release 8 architecture (Feature SG01235): feature summary

Function Impact
Compliance 3GPP TS 29.274 v8.7.0; Universal Mobile Telecommunications System (UMTS); LTE; 3GPP Evolved Packet System (EPS); Evolved General Packet Radio Service (GPRS) Tunneling Protocol
for Control plane (GTPv2-C); Stage 3.
3GPP TS 29.272 v8.8.0; Technical Specication Group Core Network and Terminals; Evolved Packet System (EPS); Mobility Management Entity (MME) and Serving GPRS Support Node
(SGSN) related interfaces based on Diameter protocol.
3GPP TS 23.060 v8.10.0; Technical Specication Group Services and System Aspects; General Packet Radio Service (GPRS); Service description; Stage 2.
3GPP TS 24.008 v8.11.0; 3rd Generation Partnership Project; Technical Specication Group Core Network and Terminals; Mobile radio interface Layer 3 specication; Core network
protocols; Stage 3.
3GPP TS 23.401 v8.11.0; 3rd Generation Partnership Project; Technical Specication Group Services and System Aspects; General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access.
Capacity None
Interworking/dependent features Intelligent GGSN Selection (Features SG01116, SG01212, SG01218, SG01255, SG01234, SG01260 and SG03067)
GPRS mobility management (Feature SG01011)
GPRS session management (Feature SG01012)
S6d/Gr Selection (Feature SG01236)
S13’ IMEI checking (Feature SG02220)
Restrictions Parameter qciTrafficClassMap in prFile section must be set to false when qciMapR8ToR99 is set to true.
When parameter s4Func is switched from OFF to ON, a restart of all the PAPS in the system is required.
Conguration management Command prFile, Parameters supportEpcCapability, dnsFallbackEnabled, epsCapability, sgwDualStackSupport, qciTrafficClassMap,
useNaptrAddField, qciMapR8ToR99, and supportOfImsvops
Command gParms, parameters s4Func and s6dDiameter

SGSN User Guide
Function Impact
Counters GPRS Mobility Management Measurement (001):

• M001C403 / SUCC INCOMING INTER SGSN RA UPDATE USING S-GW
• M001C404 / FAIL INCOMING INTER SGSN RA UPDATE USING S-GW
• M001C405 / SUCC OUTG INTER SGSN RA UPDATE USING S-GW
• M001C406 / FAIL OUTG INTER SGSN RA UPDATE USING S-GW
• M001C407 / NUM OF UE STATE CHANGE FROM READY TO STANDY AND USING S-GW
• M001C408 / SUCC OUTG TAU FROM 2G SGSN TO MME OVER S3
• M001C409 / FAIL OUTG TAU FROM 2G SGSN TO MME OVER S3
• M001C410 / SUCC INCOMING RAU FROM MME TO 2G SGSN OVER S3
• M001C411 / FAIL INCOMING RAU FROM MME TO 2G SGSN OVER S3
GPRS Session Management Measurement (002):
• M002C150 / SUCC MO PDP CONTEXT ACT TOWARDS S-GW
• M002C151 / FAIL MO PDP ACT DUE TO ACTIVATION REJECTED BY S-GW
• M002C152 / SUCC MO SECONDARY PDP ACT TOWARDS SGW
• M002C153 / FAIL MO SECONDARY PDP ACT DUE TO ACTIVATION REJECTED BY S-GW
• M002C154 / S-GW QOS UPGRADE REJECTED
• M002C155 / SUCC PDP CONT MODIFY SERVICES BY S-GW
• M002C156 / FAIL PDP CONT MODIFY SERVICES BY S-GW
• M002C157 / SUCC PDP CONT MODIFY SERVICES BY SGSN TOWARDS S-GW
• M002C158 / FAIL PDP CONT MODIFY SERVICES BY SGSN TOWARDS S-GW
• M002C159 / SUCC PDP CONT MODIFY SERVICES BY MS TOWARDS S-GW
• M002C160 / FAIL PDP CONT MODIFY SERVICES BY MS TOWARDS S-GW
• M002C161 / SUCC MO PDP CONTEXT DEACT TOWARDS S-GW
• M002C162 / FAIL MO PDP CONTEXT DEACT TOWARDS S-GW
• M002C163 / SUCC PDP CONTEXT DEACT BY S-GW
• M002C164 / FAIL PDP CONTEXT DEACT BY S-GW
• M002C165 / SUCC PDP CONTEXT DEACT BY SGSN TOWARDS S-GW
• M002C166 / FAIL PDP CONTEXT DEACT BY SGSN TOWARDS S-GW
• M002C167 / SUCC PDP DEACT SERVICE DUE S-GW RESET OR MISSING ECHO RESPONSE
GPRS Data Measurement Measurement (003):
• M003C156 / RECEIVED GTPV2 SIGNALING PACKETS
• M003C157 / BYTES IN RECEIVED GTPV2 SIGNALING
• M003C158 / SENT GTPV2 SIGNALINGPACKETS
• M003C159 / BYTES IN SENT GTPV2 SIGNALING
• M003C160 / RECEIVED ERRONEOUSGTPV2 SIGNALING PACKETS
• M003C161 / BYTES IN RECEIVED ERRONEOUS GTPV2 SIGNALING
GPRS User Measurement (004):
• M004C182 / DIRECT TUNNEL TO TWO TUNNEL DUE TO LICENCE LIMIT CONTROL
• M004C183 / USER SGW PDP ACTIVATION TOTAL NUMBER OF PROCEDURES
• M004C184 / USER SGW PDP ACTIVATION SUCC REQUEST ACCEPTED
• M004C185 / USER SGW PDP ACTIVATION FAIL CONTEXT NOT FOUND
• M004C186 / USER SGW PDP ACTIVATION FAIL NO RESOURCES AVAILABLE
• M004C187 / USER SGW PDP ACTIVATION FAIL ALL DYNAMIC PDP ADDRESSES ARE OCCUPIED
• M004C188 / USER SGW PDP ACTIVATION FAIL NO MEMORY IS AVAILABLE
• M004C189 / USER SGW PDP ACTIVATION FAIL MISSING OR UNKNOWN APN
• M004C190 / USER SGW PDP ACTIVATION FAIL USER AUTHENTICATION FAILED
• M004C191 / USER SGW PDP ACTIVATION FAIL SYSTEM FAILURE
• M004C192 / USER SGW PDP ACTIVATION FAIL SEMANTIC ERROR IN THE TFT OPERATION
• M004C193 / USER SGW PDP ACTIVATION FAIL SYNTACTIC ERROR IN THE TFT OPERATION
• M004C194 / USER SGW PDP ACTIVATION FAIL SEMANTIC ERRORS IN PACKET FILTER(S)
• M004C195 / USER SGW PDP ACTIVATION FAIL SYNTACTIC ERRORS IN PACKET FILTER(S)
• M004C196 / USER SGW PDP ACTIVATION FAIL MANDATORY IE INCORRECT
• M004C197 / USER SGW PDP ACTIVATION FAIL MANDATORY IE MISSING
• M004C198 / USER SGW PDP ACTIVATION FAIL CONDITIONAL IE MISSING
• M004C199 / USER SGW PDP ACTIVATION FAIL INVALID MESSAGE FORMAT
• M004C200 / USER SGW PDP ACTIVATION FAIL UE CONTEXT WITHOUT TFT ALREADY ACTIVATED
• M004C201 / USER SGW PDP ACTIVATION FAIL APN ACCESS DENIED - NO SUBSCRIPTION
• M004C202 / USER SGW PDP ACTIVATION FAIL REQUEST ACCEPTED PARTIALLY
• M004C203 / USER SGW PDP ACTIVATION FAIL NEW PDN DUE TO NETWORK PREFERENCE
• M004C204 / USER SGW PDP ACTIVATION FAIL NEW PDN DUE TO SINGLE ADDRESS BEARER
• M004C205 / USER SGW PDP ACTIVATION FAIL REQUEST REJECTED
• M004C206 / USER SGW PDP ACTIVATION FAIL GRE KEY NOT FOUND
• M004C207 / USER SGW PDP ACTIVATION FAIL PREFERRED PDN TYPE NOT SUPPORTED
• M004C208 / USER SGW PDP ACTIVATION FAIL PGW NOT RESPONDING
• M004C209 / USER SGW PDP ACTIVATION FAIL APN REST TYPE INCOMPATIBLE WITH ACT PDN
• M004C210 / USER SGW PDP ACTIVATION FAIL VERSION NOT SUPPORTED BY NEXT PEER
• M004C211 / USER SGW PDP ACTIVATION FAIL INVALID LENGTH
• M004C212 / USER SGW PDP ACTIVATION FAIL DENIED IN RAT
• M004C213 / USER SGW PDP ACTIVATION FAIL PROTOCOL NOT SUPPORTED
GPRS PAPS User Measurement (021)
• M021C119 / PAPS USER PEAK DUAL STACK PDP CONT
• M021C120 / PAPS USER AVG S4 DUAL STACK PDP CONTSUM
• M021C121 / PAPS USER AVG S4 DUAL STACK PDP CONTDEN
• M021C122 / PAPS USER PEAK S4 DUAL STACK PDP CONT
GPRS DNS Measurement (007):
• M007C015 / FAIL DNS INQUIRIES DUE SRV TARGET FORMAT ERROR
• M007C016 / FAIL DNS INQUIRIES DUE SRV TARGET FORMAT ERROR FOREIGN
GPRS Iu Mobility Management Measurement (016):
• M016C497 / IU SUCC INCOMING INTER SGSN RA UPDATE USING S-GW
• M016C498 / IU FAIL INCOMING INTER SGSN RA UPDATE USING S-GW
• M016C499 / IU SUCC OG INTER SGSN RA UPDATE USING S-GW
• M016C500 / IU FAIL OG INTER SGSN RA UPDATE USING SGW
• M016C501 / SUCC OUTG TAU FROM 3G SGSN TO MME OVER S3
• M016C502 / FAIL OUTG TAU FROM 3G SGSN TO MME OVER S3
• M016C503 / SUCC INCOMING RAU FROM MME TO 3G SGSN OVER S3
• M016C504 / FAIL INCOMING RAU FROM MME TO 3G SGSN OVER S3
GPRS Iu Session Management Measurement (017):
• M017C127 / IU SUCCESSFUL MO PDP CONTEXT ACTIVATION TOWARDS S-GW
• M017C128 / FAIL IU MO PDP CONTEXT ACTIVATION DUE ACTIVATION REJECTED BY S-GW
• M017C129 / IU SUCCESSFUL MO SECONDARY PDP CONTEXT ACTIVATION TOWARDS S-GW
• M017C130 / FAIL IU MO SECONDARY PDP CONTEXT ACTIVATION DUE ACTIVATION REJECTED BY S-GW
• M017C131 / IU SUCCESSFUL PDP CONTEXT MODIFICATION BY MS TOWARDS S-GW
• M017C132 / IU FAILED PDP CONTEXT MODIFICATION BY MS TOWARDS S-GW
• M017C133 / IU SUCCESSFUL PDP CONTEXT MODIFICATION BY SGSN TOWARDS S-GW
• M017C134 / IU FAILED PDP CONTEXT MODIFICATION BY SGSN TOWARDS S-GW
• M017C135 / IU SUCCESSFUL PDP CONTEXT MODIFICATION BY S-GW
• M017C136 / IU FAILED PDP CONTEXT MODIFICATION BY S-GW
• M017C137 / IU S-GW QOS UPGRADE REJECTED
• M017C138 / IU SUCCESSFUL PDP CONTEXT DEACTIVATION BY MS TOWARDS S-GW
• M017C139 / IU FAILED PDP CONTEXT DEACTIVATION BY MS TOWARDS S-GW
• M017C140 / IU SUCCESSFUL PDP CONTEXT DEACTIVATION BY SGSN TOWARDS S-GW
• M017C141 / IU FAILED PDP CONTEXT DEACTIVATION BY SGSN TOWARDS S-GW
• M017C142 / IU SUCCESSFUL PDP CONTEXT DEACTIVATION BY S-GW
• M017C143 / IU FAILED PDP CONTEXT DEACTIVATION BY S-GW
• M017C144 / IU SUCC NWR DEACT DUE REACTIVATION BECAUSE S-GW RESTART
• M017C145 / IU SUCC NWR DEACT DUE REACTIVATION BECAUSE S-GW FAILURE
• M017C146 / FAIL IU IMPL DEACT DUE S-GW NOT ANSWERING
• M017C147 / SUCC IU PDP DEACT SERVICE DUE S-GW RESET OR MISSING ECHO RESPONSE
GPRS Gb SGSN Paging Measurement (026)
• M026C003 / NUM OF GB PAGING PROCEDURES DUE TO DL DATA NOTIF FROM S-GW
• M026C004 / NUM OF UNSUCCESSFUL GB PAGING PROCEDURES DUE TO DL DATA NOTIF FROM S-GW

SGSN User Guide
Function Impact
Alarms 3717 SGW UNAVAILABLE
External interfaces S3: Interface between MME and SGSN, used for user and bearer information exchange for inter-3GPP access network mobility.
S4: Interface between S-GW and release 8 SGSN, used for U- plane tunneling and related mobility support as SGW is anchor point for 3GPP handover.
S16: Interface between two S4-SGSNs in order to manage the mobility of the MS (similar to Gn interface between two Gn / Gp - SGSNs).
S6d: Interface between SGSN and HSS to exchange subscriber related data.
S13': Interface between SGSN and EIR, used for IMEI identity check.
Feature ID SG01235
8.2 S-GW/P-GW selection enhancements for S4-SGSN

With this feature, the operator can provision the S-GW/P-GW selection on S4-SGSN
taking into account the P-GW priorities instead of the S-GW priorities for the collocation,
topological closeness mechanisms and lowest NAPTR pairs.
Table 142: S-GW/P-GW selection enhancements for S4-SGSN: feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent features SGSN S4 functionality
Restrictions This feature is applicable for homer subscribers in 2G and 3G

environments.
Conguration management Command gParms, parameter

gwSelectionModeForSgsn
Counters None
Alarms None
8.3 S13' IMEI checking (Feature SG02220): feature

summary
The 3GPP Release 8 SGSN supports also the diameter-based S13’ interface towards the
EIR, in addition to the MAP-based Gf interface already supported. This feature
implements a possibility for the operator to select between S13’ and Gf interfaces
between SGSN and Equipment Identity Register (EIR). SGSN selects between S13’ or Gf

SGSN User Guide
interface based on whether S13' IMEI checking feature is activated or not, respectively.
With this feature the functionality of SGSN is harmonized to the functionality of MME,
when SGSN uses the S13’ interface towards EIR.
Table 143: S13' IMEI checking (Feature SG02220): feature summary
Function Impact
Compliance 3GGP TS 29.272 Mobility Management Entity and Serving GPRS Support
Node related interfaces based on Diameter protocol, Rel-12
3GGP TS 23.060 General Packet Radio Service (GPRS); Service
Description; Stage 2, Rel-12
3GGP TS 23.401 General Packet Radio Service (GPRS) enhancements for
Evolved Universal Terrestrial Radio Access Network (E-UTRAN) access,
Rel-12
Capacity None
Interworking/dependent IMEI check with EIR (SG01106, SG01090, SG02156, f60210-17)

features
Restrictions • In case of S13' interface failure, for example, when EIR is not
responding, there is no fallback to Gf interface when
s13ImeiChecking is true
• The S13' IMEI checking functionality is not supported for inter SGSN
RAU and relocation procedures if the S13' interface is not congured in
the target SGSN.
• The functionality of this feature requires the securityParam
parameter imeiRequestMode set to false.
Conguration management Command prFile, parameter altImeiChkNasCause

Command features, parameters impImeiChk, imeisvInCdr,
s13ImeiChecking

SGSN User Guide
Function Impact
Counters In situations where a mobile management procedure fails as a result of

a ME being rejected due to IMEI check, the already existing IMEI illegality
related counters of the mobility management procedure are updated.
GPRS Mobility Management (001):
• M001C059 / FAIL GPRS ATTACH DUE TO ILLEGAL ME
• M001C080 / SUCC NWR GPRS DETACH DUE ILLEGAL ME
• M001C089 / FAIL INTRA PAPS RA UPDAT DUE ILLEGAL ME
• M001C101 / FAIL COMBINED INTRA PAPS RA&LA UPDAT IN PS SIDE DUE
ILLEGAL ME
• M001C113 / FAIL INTER PAPU RA UPDAT IN PS SIDE DUE ILLEGAL ME
• M001C125 / FAIL COMBINED INTER PAPU RA&LA UPDAT IN PS SIDE DUE
ILLEGAL ME
• M001C137 / FAIL INTER SGSN RA UPDAT DUE ILLEGAL ME
• M001C149 / FAIL COMBINED INTER SGSN RA&LA UPDAT IN PS SIDE
DUE ILLEGAL ME
• M001C161 / FAIL PERIODICAL RA UPDAT DUE ILLEGAL ME
• M001C173 / FAIL COMBINED PERIODIC RA&LA UPDAT IN PS SIDE DUE
ILLEGAL ME
• M001C264 / FAIL INCOMING INTRA PAPU 3G TO 2G SYSTEM HO DUE
TO ILLEGAL ME #6
• M001C277 / FAIL INCOMING INTER PAPU 3G TO 2G SYSTEM HO DUE TO
ILLEGAL ME #6
GPRS Iu Mobility Management Measurement (016):
• M016C084 / IU FAILED GPRS ATTACH DUE ILLEGAL ME #6
• M016C095 / IU FAIL COMBINED ATTACH IN PS SIDE DUE ILLEGAL ME #6
• M016C107 / SUCC IU NWR GPRS DETACH DUE ILLEGAL ME #6
• M016C117 / FAIL IU INTRA PAPU RAU DUE ILLEGAL ME #6
• M016C129 / FAIL IU INTER PAPU RAU DUE ILLEGAL ME #6
• M016C141 / FAIL IU INTER SGSN RAU DUE ILLEGAL ME #6
• M016C153 / FAIL IU PERIODICAL RAU DUE ILLEGAL ME #6
• M016C165 / FAIL IU COMBINED INTRA PAPU RA AND LA UPDATE DUE
ILLEGAL ME #6
• M016C178 / FAIL IU COMBINED INTER PAPU RA AND LA UPDATE DUE
ILLEGAL ME #6
• M016C191 / FAIL IU COMBINED INTER SGSN RA AND LA UPDATE DUE
ILLEGAL ME #6
• M016C204 / FAIL IU COMBINED PERIODICAL RA&LA UPDATE DUE
ILLEGAL ME #6
• M016C217 / FAIL INCOMING INTRA PAPU 2G TO 3G SYSTEM HO DUE
ILLEGAL ME #6
• M016C230 / FAIL INCOMING INTER PAPU 2G TO 3G SYSTEM HO DUE
ILLEGAL ME #6
• M016C243 / FAIL SERVICE REQUEST TYPE SIGNALLING DUE ILLEGAL ME
#6
• M016C256 / FAIL SERVICE REQUEST TYPE DATA DUE ILLEGAL ME #6
• M016C269 / FAIL SERVICE REQUEST TYPE PAGING RESPONSE DUE
ILLEGAL ME #6
GPRS PLMN Measurement (032):
• M032C002 / FAILED ATTACH DUE ILLEGAL ME #6 IN PLMN
• M032C014 / FAILED INTRA SGSN RAU DUE ILLEGAL ME #6 IN PLMN
• M032C028 / FAILED INTER SGSN RAU DUE ILLEGAL ME #6 IN PLMN
EPS CPPS Mobility Management (118):
• M118C273 / FAILED TAU ILLEGAL ME
Alarms None

SGSN User Guide
Function Impact
Feature ID SG02220
8.3.1 Configuring S13' IMEI checking

You need to activate the S13' IMEI checking feature and define the IMEI check mobility
management procedures. You can also enable enhanced IMEI check control (SG01090)
which enables SGSN to allow or block denylisted and unknown equipment. To enable
asking for IMEISV, you can activate feature IMEISV in CDR (SG01088).
Procedure
1 Activate IMEI check mode.
cmm securityparam modify –imeiCheckMode true config
2 Activate enhanced IMEI check control (SG01090).
cmm features modify impImeiChk --status true
2.2 Configure denylisting.
You can block or allow denylisted mobile equipment. The default value of the
blackListEffect parameter is block.
Step example
cmm plmnParam modify --blackListEffect allow
2.3 Configure handling of unknown IMEI.
You can block or allow unknown IMEIs. The default value of the
unknownImeiEffect parameter is block.
Step example
cmm plmnParam modify --unknownImeiEffect allow
3 Activate IMEISV in CDR (SG01088).

SGSN User Guide
The SGSN asks for the IMEISV from the mobile station when the GTP information
sending (feature SG01082) and/or the IMEISV in CDR (feature SG01088) is active.
cmm features modify imeisvInCdr --status true
4 Activate S13' IMEI checking.
cmm features modify s13ImeiChecking --status true
5 Activate IMEI check in mobility management procedures.
Table 144: Mobility management procedures for which ME Identity Check Request is used
Procedure Parameter name in IMEI status check from EIR parameters

(plmnParam)
GPRS attach gprsAttImeiChk
IMSI attach imsiAttImeiChk
Normal RA update SRA normalRauImeiChk
Normal RA update, new normalRauImeiChkVisitor

visitor
Periodic RA update periodRauImeiChk
MO PDP context pdpActImeiCh

activation
MO PDP context pdpDeactImeiChk

deactivation
MO GPRS detach detachImeiChk
service request serviceReqImeiChk
Step example
cmm plmnParam modify <PLMN> --gprsAttImeiChk true --detachImeiChk
true
6 Configure the IMEI validity timer.
SGSN decides if previously performed IMEI check is still valid or if it has to be checked
again, based on the value of the validity timer.
The IMEI check is executed only in the cases where the time stamp has expired or is
not use (validity time=0).

SGSN User Guide
The IMEI is considered still valid and the IMEI check is not executed during the validity
time set. When the IMEI check is executed, the validity time stamp is updated
(current time + validity time).
Step example
cmm plmnParam modify --imeiValidityTimer 1
8.4 S6d/Gr selection (Feature SG01236): feature summary

This feature allows the operator to control whether the EPS subscription via HSS or GPRS
subscription from the HLR should be used when serving home or roaming subscribers.
Table 145: S6d/Gr selection (Feature SG01236): feature summary
Function Impact
features
Restrictions None
Conguration management Command gParms, parameters s4Func and s6dDiameter

Command system, parameter s6dSelect
Counters Counters are available for the messages sent on the S6d and Gr
interface. For details, see Counters.
Alarms None
Feature ID SG01236
8.4.1 Configuring S6d/Gr selection

The procedure includes steps for activating the Rel-8 feature, activating/deactivating
S6d/Gr selection feature for homers and activating/deactivating s6dSelect parameter for

SGSN User Guide
roamers.
Procedure
1 Activate the Rel-8 feature.
cmm gParms modify --gParmName s4Func --gParmValue ON

Step result
+---------------------+
| Field | Value |
+------------+--------+
| gParms | s4Func |
| gParmName* | s4Func |
| gParmValue | ON |
+------------+--------+
2 Activate the S6d/Gr selection feature for homers.
cmm gParms modify --gParmName s6dDiameter --gParmValue ON

Step result
+--------------------------+
| Field | Value |
+------------+-------------+
| gParms | s6dDiameter |
| gParmName* | s6dDiameter |
| gParmValue | ON |
+------------+-------------+
3 Activate the s6dSelect parameter for roamers.
cmm system modify config --s6dSelect true

Step result
+-----------+---------------------------------------------------+
| Field | Value |
+-----------+---------------------------------------------------+
| s6dSelect | true |
+-----------+---------------------------------------------------+
4 Deactivate the S6d/Gr selection feature for homers.

SGSN User Guide
cmm gParms modify --gParmName s6dDiameter --gParmValue OFF

Step result
+------------+-------------+
| Field | Value |
+------------+-------------+
| gParms | s6dDiameter |
| gParmName* | s6dDiameter |
| gParmValue | OFF |
+------------+-------------+
5 Deactivate the s6dSelect parameter for roamers.
cmm system modify config --s6dSelect false

Step result
+-----------+---------------------------------------------------+
| Field | Value |
+-----------+---------------------------------------------------+
| s6dSelect | false |
+-----------+---------------------------------------------------+
8.5 S3-based packet switch handover ( Feature SG01242):

feature summary
Packet Switch Handover (SG01242) feature is an extension of relocation feature, which
enables Rel-8 UEs located in E-UTRAN to maintain connectivity to PS core access when
they move to UTRAN or vice versa. This allows the operator to seamlessly migrate the
users between inter-system radio access types.

SGSN User Guide
Table 146: S3-based packet switch handover ( Feature SG01242): feature summary
Function Impact
Compliance • 3GPP TS 25.413 UTRAN Iu interface Radio Access Network

Application Part (RANAP) signaling, Release 8.
• 3GPP TS 29.274 Evolved Packet System (EPS); Evolved
General Packet Radio Service (GPRS) Tunneling Protocol for
Control plane (GTPv2-C), Release 8.
• 3GPP TS 23.401 General Packet Radio Service (GPRS)
Network (E-UTRAN) access, Release 8.
Capacity None
Interworking or dependent • GPRS mobility management (Feature SG01011)

• EPS Bearer Mapping
Restrictions None
Conguration management Command cmm prFile modify, parameter

pshoBtwSgsnMme
Command cmm system modify, parameter eIddf
Counters None
Alarms None
Feature ID SG01242
8.6 S4 SGSN roaming control (Features SG01250 and

S4 SGSN roaming control feature is comprised of the following features: Configurable R8
QoS Enhancement and QoS Control for IMS APN (Feature SG01250) and APN DNS Domain
Handling and Control Based on IMSI Ranges (Feature SG01251).
Table 147: S4 SGSN roaming control (Features SG01250 and SG01251): feature summary

SGSN User Guide
Function Impact
Compliance This is a Nokia proprietary feature and also complies with:

• 3GPP TS 23.060 (v9.7.0): Digital cellular telecommunications
system (Phase 2+); Universal Mobile Telecommunications
System (UMTS); General Packet Radio Service (GPRS); Service
description; Stage 2.
• 3GPP TS 29.274 (v9.5.0): Universal Mobile
Telecommunications System (UMTS); LTE; 3GPP Evolved
Packet System (EPS); Evolved General Packet Radio Service
(GPRS) Tunneling Protocol for Control plane (GTPv2-C); Stage
3.
• 3GPP TS 23.401 (v9.7.0): LTE; General Packet Radio Service
(GPRS) enhancements for Evolved Universal Terrestrial Radio
Access Network (E-UTRAN) access.
• 3GPP TS 23.303 (v9.3.0): Policy and charging control
architecture.
Capacity None
features
Restrictions QoS policy set enforcement is applied even if the roamer is

routed to his/her home network. In other words, the visiting
operator may downgrade the QoS to the provisioned QoS
policy set values, even for a roamer utilizing home resources.
Conguration management Command features, parameter lteRoamQosControl

Command prFile, parameter ueAmbrSupportRanap
Command plmnParam, parameters lb, pon, dnsMcc,
dnsMnc, and imsApn
Command lteQosPolicySet, parameters gbrDl,
gbrUl, mbrUl, mbrDl, apnAmbrUl, apnAmbrDl,
arpGbr, arpNGbr, pciGbr, pciNgbr, pviGbr,
pviNgbr, ueAmbrUl, ueAmbrDl, qci1, qci2, qci3,
qci4, qci5qci6, qci7, qci8, and qci9
Counters None
Alarms None

SGSN User Guide
8.6.1 Configuring S4 SGSN roaming control

To configure the QoS policy set, enable the S4 SGSN roaming control feature and the UE
AMBR support RANNAP feature, and configure a default DNS in the IMSI NS table.
Before you start
When the default DNS domain is configured for an IMSI NS, it is applied for both R7 and R8
DNS queries. If R8 DNS query fails, fallback to R7 DNS query also uses this default DNS
domain.
The plmnParam command is used for configuring a default DNS domain in the IMSI NS
table.
Procedure
cmm features modify lteRoamQosControl --status true
2 Enable UE AMBR support RANNAP.
cmm prFile modify ueAmbrSupportRanap --status true
3 Configure a default DNS in the IMSI NS table.
cmm plmnParam modify <plmn> -- dnsMcc <mcc> --dnsMnc <mnc>
Lb enable or disable the local breakout functionality
Pon LTE Qos Policy set ID [value = 0...6]
dnsMcc Dene LTE inbound roaming subscribers default DNS domain

mobile country code [length = 3...3]
imsApn Species whether IMS APN is allowed in SGSN or not
4 Configure the QoS policy set.
lteQosPolicySet ID of LTE QoS policy set number.

SGSN User Guide
gbrDl This parameter denes the guaranteed bit rate for uplink in kbps.
The values range from 0 to 46000 with variable increment.
mbrUl This parameter denes the maximum bit rate for uplink in kbps.
The values range from 0 to 46000 with variable increment.
mbrDl This parameter denes the maximum bit rate for downlink in
kbps. The values range from 0 to 168000 with variable increment.
apnAmbrUl This parameter denes the aggregated maximum bit rate for
non-guaranteed bit rate for uplink per APN in kbps. The values
range from 0 to 46000 with variable increment.
apnAmbrDl This parameter denes the aggregated maximum bit rate for
non-guaranteed bit rate for downlink per APN in kbps. The values
range from 0 to 168000 with variable increment.
arpGbr This parameter denes allocation and retention priority for

guaranteed bit rate. The values range from 1 to 15.
arpNGbr This parameter denes allocation and retention priority for non-
guaranteed bit rate. The values range from 1 to 15.
pciGbr This parameter denes arp pre-emption capability information for

guaranteed bit rate.
pciNGbr This parameter denes arp pre-emption capability information for

non-guaranteed bit rate.
pviGbr This parameter denes arp pre-emption vulnerability information

for guaranteed bit rate
pviNGbr This parameter denes arp pre-emption vulnerability information

for non-guaranteed bit rate
apnAmbrUl This parameter denes the UE-aggregated maximum bit rate for
non-guaranteed bit rate for downlink. The values range from 0 to
168000 with variable increment.
qci1 This parameter denes the QOS class identier 1.

SGSN User Guide
Step example
cmm lteQosPolicySet create 1 --mbrUl 23000 --mbrDl 168000 --gbrDl
166000 --gbrUl 22000 --apnAmbrDl 168000 --apnAmbrUl 23000 --
arpNGbr 5 --arpGbr 4 --pciGbr true --pciNGbr false --pviGbr true
--pviNGbr false --ueAmbrDl 168000 --ueAmbrUl 23000 --qci1 true --
qci2 true --qci3 true --qci4 true --qci5 true --qci6 true --qci7
true --qci8 true --qci9 true
8.7 Cause code forwarding over S4 interface (Feature

This feature provides support for the SGSN to send F-Cause (that is, RANAP/BSSGP cause
codes) and diagnostics codes (that is, GMM/SM cause codes) to S-GW over S4 interface
via the Private-Extension IE (information element).

SGSN User Guide
Table 148: Cause code forwarding over S4 interface (Feature SG01237): feature summary
Function Impact
Compliance • 3GPP TS 29.274 Release 8: Tunneling Protocol for Control

plane (GTPv2-C); Stage 3
• 3GPP TS 24.301 Release 8: Non-Access-Stratum (NAS)
protocol for Evolved Packet System (EPS); Stage 3
• 3GPP TS 24.008 Release 8: Mobile radio interface Layer 3
specication; Core network protocols; Stage 3
• 3GPP TS 36.413 Release 8: S1 Application Protocol (S1AP)
• 3GPP TS 25.413 Release 7:UTRAN Iu interface RANAP signaling
Capacity None
Interworking or dependent Release 8 architecture (Feature SG01235)

features
Restrictions None
Conguration management Command cmm features modify, parameter

causeCodeFrwdS4
Congure the Enterprise id by using the command: cmm
prFile modify, parameter enterpriseId
Counters None
Alarms None
Feature ID SG01237
Note:
The enterpriseId parameter, that specifies the enterprise id, is encoded in the
Private Extension IE and it can be provided while activating the feature.
8.8 SGSN support for RFSP index (Feature f51024-01):

feature summary
This feature requests S4 SGSN to check s6d subscription data of a user with LTE-capable
UE (RFSP index or SPID) and passes the info to radio accordingly. This feature applies for
home subscriber only.

SGSN User Guide
Table 149: SGSN support for RFSP index: feature summary
Function Impact
Compliance None
Capacity None
Required features SGSN S4 Functionality (Gr/S6d)
features
Restrictions The SGSN does not implement per-PLMN policies to override the SPID
values.
For roamers, the SGSN does not send SPID to radio network.
Conguration gParm rfspInS4Sgsn

management
Counters None
Alarms None

SGSN User Guide
9. Interface/Link management
These features provide flexible configuration of external interfaces.
9.1 GTP sequence number management enhancements

This feature enhances the management of the GTP sequence number to improve the
behavior of the CMM and to avoid exhausting available GTP sequence numbers.
Table 150: GTP sequence number management enhancements: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration None
management
Counters None
Alarms None

SGSN User Guide
10. Operability
10.1 Traffica support (Features SG01025, SG01087 and

Traffica is a network-wide analytics tool that provides monitoring and troubleshooting
capabilities while giving insights into traffic, network, locations, devices, and subscribers.
With this feature, SGSN is able to generate RTT Traffica reports, acknowledge heartbeat
and respond back to Traffica servers, parsing our configuration in heartbeats and
generating Traffica generation processes, collect Traffica reports and deliver them to
Traffica servers instantly. SGSN supports several Traffica servers simultaneously. It can
take action in case of overload situation (if overload of PAPS is detected, SGSN starts
shedding reports and informs Traffica server by changing the HB response ID).
Table 151: Traffica support (Features SG01025, SG01087 and f60210-15): feature summary
Function Impact
Capacity OLC mechanism for shedding traffica reports based on process CPU
usage.
Interworking/dependent MME support for Traffica (f13101-01), Overload mechanism

features improvements for PAPS (f60210-21)
Restrictions None
Conguration Command features, parameter trafficaRealTime

management Commands trafReport and trafServer
Counters None
Alarms 173 SendingOfTrafficaReportsChangeAction

SGSN User Guide
10.1.1 Configuring Traffica

In SGSN, the Traffica feature requires activation. Configuring allowed Traffica servers is
optional.
Procedure
1 Activate the SGSN Traffica feature.
cmm features modify trafficaRealTime --status true
2 Optionally, configure allowed Traffica servers.
After this step, Traffica reports are only sent to allowed Traffica IP addresses. The
SGSN, when receiving a heartbeat message from a Traffica, verifies that the IP address
is included in the allowed Traffica addresses and sends the requested report to the
Traffica (unless some other Traffica has reserved the report earlier). If the IP address is
not allowed, the report request is discarded.
The IP address configuration is optional. If no allowed Traffica IP addresses are defined,

all Traffica addresses are allowed.
2.1 Interrogate Traffica servers.
cmm trafServer list
2.2 Add a Traffica server in the allowed IP addresses.
cmm trafServer create --serverId <integer> --ip <ip address>

where --serverId specifies the ID number of the Traffica server (1...10).
3 Interrogate active Traffica reports.
cmm trafReport list
cmm trafReport show <type of report>
10.2 SGSN support for call trace (Features f60210-13 and

The 3GPP subscriber and equipment trace allows tracing of a specific subscriber based on
IMSI or MSISDN. The trace can be activated from command line (management-based call

SGSN User Guide
trace). Subscriber and equipment trace can be enabled for the SGSN's interfaces and the
captured messages are stored as a PCAP file.
Table 152: SGSN support for call trace: feature summary
Function Impact
Compliance 3GPP TS 32.422: Telecommunication management; Subscriber and

equipment trace; Trace control and conguration management
Capacity • Total trace rate in IPPS side for protection from overload: 30 Mbps
• Total trace rate in PAPS side for protection from overload: 500 Kbps
• Maximum message rate for CTCS/REDIS in NECC: 15 000 msgs/sec
• Maximum number of simultaneous traces: 100 (including the MME
traces).
• Maximum duration of a call trace: 4 days.
• Max PDPs per PAPS: 10
• Max PDPs per IPPS: 10
Note:
To support the full capacity of the SGSN user plane data call trace
on an CNF environment, the large CTCS avor pod needs to be
used (CTCS container with 6 vCPU and Redis container with 4GB of
memory).
features
Restrictions • In case of MultiSim, if a specic MSIDSN is mapped to more than one

IMSI, only one IMSI will be selected from the application and the call
trace will start only for the specied IMSI. Call trace for the other IMSIs
is not be possible as long as the relevant call trace job is active.
• 2G and 3G data tracing is paused in case of overload and
automatically resumes after overload period is over.
• HLR/HSS-triggered call trace is not supported for SGSN.
• It is not possible to disable PAPS call trace overload control via CLI as
for CPPS (cmm gParms modify --gParmName
ocCallTraceContinue --true).
• The Create Session Request message retransmissions occur in the
IPDS unit without informing the PAPS unit. As a result, the Create
Session Request message retries are not captured in the internal call
trace PCAP les.

SGSN User Guide
Function Impact
Conguration Call trace management commands:

management callTraceJob
callTraceSetting
For enabling 2G and 3G call trace user plane data:
Command callTraceSetting, parameters s4gn2gu and
s4gn3gu
Trace data handling commands:
traceData
traceDataStatus
Counters None
Alarms 40548 LSS_mmeCallTraceStateChange
Feature ID f60210-13 and f52071-01
10.2.1 Configuring call trace

Use the callTraceJob command to create, list, show and delete call trace jobs.
Procedure
1 Create a call trace job.
cmm callTraceJob create
--userIdentity {imsi,msisdn}
--digits <digits>
[--mode {default,debug}]
userIdentity Call trace user identity, IMSI or MSISDN
digits IMSI or MSISDN digits
mode Call trace mode [default = default]
The call trace job uses existing interface values. If you want to change the interface
settings, use the callTraceSetting command.

SGSN User Guide
Step example
cmm callTraceJob create --userIdentity imsi --digits 26228000000001
2 List call trace jobs.
cmm callTraceJob list [ --userIdentity <list-item> ] [ --digits <digits> ]
[ --dns <list-item> ] [ --dnssgsn <list-item> ] [ --gb <list-item> ]
[ --gf <list-item> ] [ --gn <list-item> ] [ --gnsgsn <list-item> ]
[ --gr <list-item> ] [ --gs <list-item> ] [ --iucp <list-item> ]
[ --mode <list-item> ] [ --n11 <list-item> ] [ --n12 <list-item> ]
[ --n14 <list-item> ] [ --n15 <list-item> ] [ --n17 <list-item> ]
[ --n26 <list-item> ] [ --n26mme <list-item> ] [ --n8 <list-item> ]
[ --namfServer <list-item> ] [ --nlg <list-item> ] [ --nls <list-item> ]
[ --nnef <list-item> ] [ --nnrf <list-item> ]
[ --notificationService <list-item> ] [ --nr10 <list-item> ]
[ --rs10 <list-item> ] [ --s10 <list-item> ] [ --s102 <list-item> ]
[ --s11 <list-item> ] [ --s11u <list-item> ] [ --s13 <list-item> ]
[ --s13sgsn <list-item> ] [ --s16 <list-item> ] [ --s1mme <list-item> ]
[ --s3 <list-item> ] [ --s3sgsn <list-item> ] [ --s4 <list-item> ]
[ --s4gn2gu <list-item> ] [ --s4gn3gu <list-item> ]
[ --s6ad <list-item> ] [ --s6c <list-item> ] [ --s6d <list-item> ]
[ --sgd <list-item> ] [ --sgs <list-item> ] [ --sgslite <list-item> ]
[ --slg <list-item> ] [ --sls <list-item> ] [ --sv <list-item> ]
[ --t6a <list-item> ] [ --t6aU <list-item> ] [ --traceId <integer> ]
[ --traceSrc <list-item>
Step example
cmm callTraceJob list
+---------------------+
| callTraceJob |
+---------------------+
| imsi~26228000000001 |
+---------------------+
3 Show call trace job.

SGSN User Guide
cmm callTraceJob show
[--userIdentity {imsi,msisdn}]
[--digits <digits>]
Step example
cmm callTraceJob show --userIdentity imsi --digits 26228000000001
+---------------+---------------------+
| Field | Value |
+---------------+---------------------+
| callTraceJob | imsi~26228000000001 |
| userIdentity* | imsi |
| digits* | 26228000000001 |
| traceSrc | mgt |
| traceId | 1 |
| mode | default |
| dns | true |
| dnssgsn | true |
| gb | true |
| gf | true |
| gn | true |
| gnsgsn | true |
| gr | true |
| gs | true |
| iucp | true |
| rs10 | true |
| s10 | true |
| s102 | true |
| s11 | true |
| s11u | false |
| s13 | true |
...
4 Show call trace settings.

SGSN User Guide
cmm callTraceSetting show
Step example
+------------------+---------+
| Field | Value |
+------------------+---------+
| callTraceSetting | config |
| dns | true |
| dnssgsn | true |
| gb | true |
| gf | true |
| gn | true |
...
5 Modify call trace interface settings.

SGSN User Guide
cmm callTraceSetting modify [ --dns <list-item> ] [ --dnssgsn <list-item> ]
[ --gb <list-item> ] [ --gf <list-item> ] [ --gn <list-item> ]
[ --gnsgsn <list-item> ] [ --gr <list-item> ] [ --gs <list-item> ]
[ --iucp <list-item> ] [ --n11 <list-item> ] [ --n12 <list-item> ]
[ --n26 <list-item> ] [ --n26mme <list-item> ] [ --n8 <list-item> ]
[ --namfServer <list-item> ] [ --nlg <list-item> ] [ --nls <list-item> ]
[ --nnef <list-item> ] [ --nnrf <list-item> ]
[ --notificationService <list-item> ] [ --nr10 <list-item> ]
[ --rs10 <list-item> ] [ --s10 <list-item> ] [ --s102 <list-item> ]
[ --s11 <list-item> ] [ --s11u <list-item> ] [ --s13 <list-item> ]
[ --s13sgsn <list-item> ] [ --s16 <list-item> ] [ --s1mme <list-item> ]
[ --s3 <list-item> ] [ --s3sgsn <list-item> ] [ --s4 <list-item> ]
[ --s4gn2gu <list-item> ] [ --s4gn3gu <list-item> ]
[ --s6ad <list-item> ] [ --s6c <list-item> ] [ --s6d <list-item> ]
[ --sgd <list-item> ] [ --sgs <list-item> ] [ --sgslite <list-item> ]
[ --slg <list-item> ] [ --sls <list-item> ] [ --sv <list-item> ]
[ --t6a <list-item> ] [ --t6aU <list-item> ]
The cmm callTraceSetting modify command displays the current parameter

values.
Step example
cmm callTraceSetting modify --gb false
cmm callTraceSetting modify --gb true –-s6d false
cmm callTraceSetting modify --s11 true –-s10 false
6 Delete call trace job.
cmm callTraceJob delete
[--userIdentity {imsi,msisdn}]
[--digits <digits>]
Step example
cmm callTraceJob delete --userIdentity imsi --digits
26228000000001

SGSN User Guide
Step result
Deleting the call trace from the active trace table will generate a PCAP file in case the
user had any activity. If there was no activity, no file is generated.
The PCAP file name will include the userIdentity value (imsi or msisdn) given in the
cmm callTraceJob delete command.
10.2.2 Outputting call trace data (PCAP files)

Use the traceData command to create, search, and delete PCAP trace files.
Purpose
You will find the created PCAP files (.pcap) in the /shared/restfm/traces folder in
NECC.
Procedure
1 Create PCAP for a specific subscriber session.
cmm traceData create
[--imsi <digits>]
[--msisdn <digits>]
[--traceOrigin {hss,cli}]
[--traceID <integer>]
[--start <string>]
[--end <string>]
Mandatory parameters: imsi or msisdn and traceID.
Optional parameters: start [timestamp] and end [timestamp].

SGSN User Guide
Note:
If the cmm traceData create command is executed, only one PCAP file is
created each time.
If the cmm traceData create command is executed multiple times, a new

PCAP file is generated each time based on the current timestamp.
The created PCAP file name includes the userIdentity value (imsi or msisdn)
given in the cmm traceData create command.
Step example
cmm traceData create --msisdn 918003779684 --traceID 997
cmm traceData create --imsi 262280000000005 --traceID 997
Step example
cmm traceData create --imsi 262280000000001 --traceID 1
+--------------+--------------------------------------------------------------+
| Field | Value |
+--------------+--------------------------------------------------------------+
| fileFolder | /shared/restfm/traces/ |
| status | OK |
| fileLocation | active necc |
| packetCount | 6 |
| fileName | IMSI_262280000000001_TRACE-ID_1_2016-11-17-13-14-56-028.pcap |
+--------------+--------------------------------------------------------------+
2 List PCAP files.
The cmm traceData list command lists all PCAP files dedicated to subscribers or
sessions.

SGSN User Guide
cmm traceData list
[--quote {all,minimal,none,nonnumeric}]
[--imsi <digits>]
[--msisdn <digits>]
[--start <string>]
[--end <string>]
[--limit {db,all}]
[--file <string>]
[--status <string>]
[--fileName <string>]
[--fileFolder <string>]
[--packetCount <string>]
[--fileLocation <string>]
Step example
List all created files:
cmm traceData list
+--------------------------------------------------------------------------------
----+
| FILES
+--------------------------------------------------------------------------------
----+
| /shared/restfm/traces/IMSI_262280000000001_TRACE-
ID_1_2016-11-17-13-19-48-483.pcap |
ID_2_2016-11-17-13-19-51-168.pcap |
ID_3_2016-11-17-13-20-03-911.pcap |
+--------------------------------------------------------------------------------
----+

SGSN User Guide
Step example
List files dedicated to a subscriber ID:
cmm traceData list --imsi 262280000000001
+--------------------------------------------------------------------------------
----+
| FILES
+--------------------------------------------------------------------------------
----+
ID_1_2016-11-17-13-19-48-483.pcap |
ID_2_2016-11-17-13-19-51-168.pcap |
+--------------------------------------------------------------------------------
----+
Step example
List files dedicated to a subscriber session:
cmm traceData list --imsi 262280000000001 --traceID 1
+--------------------------------------------------------------------------------
----+
| FILES
+--------------------------------------------------------------------------------
----+
ID_1_2016-11-17-13-19-48-483.pcap |
+--------------------------------------------------------------------------------
----+
3 Delete PCAP files.

SGSN User Guide
cmm traceData delete
[--imsi <digits>]
[--msisdn <digits>]
[--limit {db,all}]
[--file <string>]
Values of the limit parameter:
limit Value db removes trace data from the RedisDB.

Value all removes trace data from the database as well as the
generated PCAP les from NECC.
Step example
Delete a file:
cmm traceData delete --file IMSI_262280000000001_TRACE-

ID_1_2016-11-17-13-14-56-028.pcap
+--------+----------------+
| Field | Value |
+--------+----------------+
| status | deleted 1 file |
+--------+----------------+
Step example
Delete all IMSI-dedicated files:
cmm traceData delete --file 262280000000001
+--------+----------------+
| Field | Value |
+--------+----------------+
| status | deleted 1 file |
+--------+----------------+
Step example
Delete data from RedisDB:

SGSN User Guide
cmm traceData delete --imsi 262280000000001 --limit db
+--------+--------------------+
| Field | Value |
+--------+--------------------+
| status | records deleted 21 |
+--------+--------------------+'
Step example
Delete files and data from RedisDB:
cmm traceData delete --imsi 262280000000002 --limit all
+--------+--------------------+
| Field | Value |
+--------+--------------------+
| status | records deleted 60 |
+--------+--------------------+
10.2.3 Working with PCAP output files (SGSN)

Traced UE call activity is written into a standardized PCAP format, which means that
traced UE call messages can be decoded with the off-the-shelf Wireshark™ packet
analyzer without requiring a proprietary plug-in.
Protocol stack
The CMM call trace software captures call related control plane message packets that
contain only application layer data of their respective protocol stacks. At the point of call
packet capture, all the lower protocol layers have been stripped off in the receiving direction
and have not been constructed on the send direction from CMM perspective. Therefore, all
the layers of protocol stack below the application layer must be reconstructed to the
accuracy that Wireshark dissectors can successfully traverse through each layer to reach the
application layer and decode captured call information.
SGSN supports tracing of 2G and 3G user plane data. Specifically, it is supported only for Gn-
U /S4-U interface stack.
The trace user plane data contains the real source and the target IPs and ports. It is

SGSN User Guide
supported for both IPv4 and IPv6.
Table 153: Reconstructed protocol stack
Libpcap_eth header
Linux Cooked capture (Layer 2)
IP layer
UDP, TCP or SCTP layer
Application data layer
Reconstruction of IP layer source, destination IP address and UDP layer port

for packets with hard-coded values
When IP address and port data are not available in SGSN, these values will be hard-coded.
For these cases, the reconstruction of IP layer source and destination IP addresses and UDP
layer port follow the conventions described below.

SGSN User Guide
Table 154: Interface IP addresses
Interface Source IP Destination IP
CMM network element (NE) is at either end of the GB 10.100.1.43 20.100.1.43

interface:
source IP address: 10.100.0.x, IU 10.100.1.51 20.100.1.51
destination IP address: 20.100.0.y
GR 10.100.1.49 20.100.1.49
GF 10.100.1.47 20.100.1.47
S4 10.100.1.4 20.100.1.4
SGSN_S3 10.100.0.4 20.100.0.4
S16 10.100.1.16 20.100.1.16
S6D 10.100.0.7 20.100.0.7
S13' 10.100.0.14 20.100.0.14
SGSN_DNS 10.100.1.58 20.100.1.58
SGSN_GN 10.100.1.57 20.100.1.57
GS 10.100.1.50 20.100.1.50
Example: IP address usage

The ‘internal’ IP addresses are used because the call-trace occurs within the internal
network.
The 10.100.0.x is sourced from the CMM
The 20.100.0.x is sourced from the remote element.
Direction of IP packet when hard-coded values exist

The direction of the packet is shown by the IP layer source and destination IP address
designation. If a given packet has IP layer source IP address 10.100.x.y and destination IP
address 20.100.x.y, the CMM sends the packet to its remote endpoint. On other hand, if a
packet has IP layer source IP address 20.100.x.y and destination IP address 10.100.x.y, the
CMM receives the packet from its remote endpoint.

SGSN User Guide
Wireshark packet analyzer settings

The below table provides an example on how to set the filters on Wireshark packet analyzer.
From the Wireshark menu, navigate to Edit ► Preferences ► Protocol settings
and set the appropriate filters.
Table 155: Wireshark packet analyzer settings example
Interface Filter Setting
GB gprs-ns || bssgp Edit--> Preferences --> Protocols -->

GPRS-NS --> UDP port(s) 49999 -
65000
10.2.4 Displaying trace data in RedisDB

Use the traceDataStatus command to display trace data in RedisDB.
Procedure
1 List all sessions and related data in RedisDB.
cmm traceDataStatus list
[--quote {all,minimal,none,nonnumeric}]
Step example

SGSN User Guide
cmm traceDataStatus list
+---------------+------------+-----+------+----+---------------+--------------+
|SUBSCRIBER |MSISDN |TRACE|TRACE |HITS| FIRST | LAST |
| | | ID |ORIGIN| | | |
+---------------+------------+-----+------+----+---------------+--------------+
|262280000000001|918003779680| 1|hss | 6|2016-11-17 |2016-11-17 |
| | | | | |T13:19:28.018 |T13:19:28.209 |
|262280000000001|918003779680| 2|hss | 15|2016-11-17 |2016-11-17 |
| | | | | |T13:19:28.304 |T13:19:29.101 |
|262280000000002|918003779681| 3|hss | 20|2016-11-17 |2016-11-17 |
| | | | | |T13:19:29.115 |T13:19:29.873 |
|262280000000002|918003779681| 4|hss | 20|2016-11-17 |2016-11-17 |
| | | | | |T13:19:29.924 |T13:19:30.535 |
|262280000000002|918003779681| 5|hss | 20|2016-11-17 |2016-11-17 |
| | | | | |T13:19:30.616 |T13:19:31.307 |
+---------------+------------+-----+------+----+---------------+--------------+
Note:
This command displays the first 100 trace jobs stored in RedisDB whether they
are active or not.
Use cmm callTraceJob list command to retrieve a list of active call trace
jobs.
2 Show subscriber session dedicated trace data in RedisDB.
cmm traceDataStatus show
[--imsi <digits>]
[--msisdn <digits>]
[--start <string>]
[--end <string>]
Step example

SGSN User Guide
cmm traceDataStatus show --imsi 262280000000001 --traceID 1
+-------------+-------------------------+
| Field | Value |
+-------------+-------------------------+
| hits | 6 |
| traceID | 1 |
| last | 2016-11-17T13:19:28.209 |
| msisdn | 918003779680 |
| traceOrigin | hss |
| imsi | 262280000000001 |
| first | 2016-11-17T13:19:28.018 |
+-------------+-------------------------+
10.2.5 Configuring call trace for user plane data

Use the callTraceSetting command to show, modify and list the call trace settings for
user plane data.
Procedure
1 Show call trace settings.
Step example

SGSN User Guide
+------------------+---------+
| Field | Value |
+------------------+---------+
| callTraceSetting | config |
| collectorIP | 0.0.0.0 |
| dns | true |
| dnssgsn | true |
| gb | true |
| gf | true |
| gn | true |
...
...
| s4gn2gu | false |
| s4gn3gu | false |
+------------------+---------+
2 Modify the call trace interface settings.
cmm callTraceSetting modify
--s4gn2gu {true,false}
The call trace collection for 2G Data( Gn-U and S4-U)[default = false].
--s4gn3gu {true,false}
The call trace collection for 3G Data (Gn-U and S4-U)[default = false].
Step example
cmm callTraceSetting modify --s4gn2gu true
Step example
cmm callTraceSetting modify --s4gn3gu true

SGSN User Guide
10.3 Internal load balancing and admission control

(Features SG01060, f60110-05, f60210-04 and
This feature ensures that the incoming traffic load is properly distributed over the
available resources in an optimal manner.
Table 156: Internal load balancing and admission control (Features SG01060, f60110-05,
Function Impact
Capacity None
Interworking/dependent features • SGSN support for Increased Gb i/f Capacity

for Open Linux-based Cloud SGSN (Feature
f60210-06)
• SGSN support for SS7 Stack Enhancements
(Feature f60210-29)
• SGSN support for Gr Interface to HLR for
Open Linux-based Cloud SGSN (Feature
f60210-16)
• SGSN support for Gf Interface to EIR for
Open Linux-based Cloud SGSN (Feature
f60210-17)
• SGSN support for New TCP Channel between
IPDS and PAPS (Feature f60210-07)
• SGSN support for Inter-PAPS Mobility
Scenarios (Feature f60210-23)
• Multipoint Gb (Features SG01023)
• QoS Control for Roaming Subscribers
(Feature SG01067)
Restrictions None

SGSN User Guide
Function Impact
Conguration management Command cmm prFile, parameter

lrasLoadBalancing
Note:
The Load balancing mechanism is enabled

by default and there is not any
conguration option to change the
behavior. The only congurable load
balancing functionality is the one that refers
to the Subscriber Load balancing
mechanism which is controlled via the
previous mentioned command.
Counters None
Alarms None
Feature ID SG01060, f60110-05, f60210-04, f60210-05
10.4 PAPS load balancing mechanism per access type

This feature enhances the load balancing mechanism of the SGSN in order to balance 2G
and 3G UEs separately.

SGSN User Guide
Table 157: PAPS load balancing mechanism per access type: feature summary
Function Impact
Compliance None
Capacity None
Required features Internal load balancing and admission control (Features

SG01060, f60110-05, f60210-04, f60210-05 and
f60210-06): the lrasLoadBalancing prFile parameter
must be enabled.
Restrictions None
Conguration management Command cmm prFile, parameter

lrasLoadBalancingPerRat
Counters None
Alarms None
10.4.1 Configuring PAPS load balancing mechanism per

access type
Use the prFile parameter lrasLoadBalancingPerRat to enable the load balancing
mechanism per radio access type (RAT).
Before you start
The Large Routing Area Support (SG01060) feature must be activated.

cmm prFile modify lrasLoadBalancing --status true --
lrasLoadBalancing <integer>
▪ Enable the PAPS load balancing mechanism per access type feature.
Step example
cmm prFile modify lrasLoadBalancingPerRat --status true

SGSN User Guide
10.5 PAPS 2G/3G graceful shutdown (Features SG01086,

PAPS 2G/3G graceful shutdown feature allows network operators to provide subscribers
with smoother service during maintenance, hardware changes, and network structure
modification. Specifically, it enables the operator to empty the PAPS of subscribers in a
controlled way before performing maintenance work by routing the subscribers to other
PAPS. Continuous operation for all subscribers is guaranteed, which leads to reduced
network traffic and increased revenue.

SGSN User Guide
Table 158: PAPS 2G/3G graceful shutdown (Features SG01086, f60210-27 and f60210-45):
feature summary
Function Impact
Compliance None
Capacity None
Interworking or dependent • SGSN support for Native Openstack (f70002-02)

features • SGSN support for Inter-PAPS Mobility Scenarios (f60210-23)
Restrictions • It is only possible to block one PAPS at a time.

• It is not possible to block the PAPS if it is the only PAPS.
• It is not possible to cancel the blocking of a single PAPS if
the mass detach has already been activated and not
completed. The mass detach procedure must be cancelled if
it is in progress before trying to unblock the PAPS.
Conguration management Command cmm maintForPaps, parameters

blockForMaint, rat, massDetach
Commands cmm outputPapsStatus show and cmm
outputPapsStatus list
Command cmm prFile,
parameterpapuBlMassDetachSpd
Command cmm subscriber count
Commands cmm nsvcAdmin modify, cmm nsvcEndps
remove and nsvcEndps add
Counters None
Alarms 142 MassDetachComplete
Feature ID SG01086, f60210-27 and f60210-45
10.5.1 Configuring 2G/3G graceful shutdown

To configure 2G/3G PAPS graceful shutdown, follow the steps given below.
Procedure
1 Block PAPS.
Step example
cmm maintForPaps create --blockForMaint ACT 0

SGSN User Guide
2 Check that the status of selected PAPS is blocked.
Step example
cmm outputPapsStatus show paps0
3 Configure the mass detach speed.
Step example
cmm prFile modify papuBlMassDetachSpd --papuBlMassDetachSpd 50
Note:
The value of the papuBlMassDetachSpd parameter is the value of the mass

detaches per second divided by 10. In the above example, the value 50 means
500 mass detaches per second.
4 Check the number of subscribers in selected PAPS.
cmm subscriber count --filterType attachedPerPaps
5 Start mass detach for 2G/3G users of a blocked PAPS.
Step example
cmm maintForPaps modify --massDetach START --rat ALL
6 Check the number of subscribers in selected PAPS after the completion of the mass
detach.
cmm subscriber count --filterType attachedPerPaps
Note:
142 MassDetachComplete alarm is raised when mass detach is completed.
7 Lock the static links of the affected PAPS (if it is needed).
Step example
cmm nsvcAdmin modify --papsId 0 --state locked

SGSN User Guide
Note:
In case of permanent scale in, delete the static links of PAPS that were previously
locked.
cmm nsvc delete --nsvcId <integer>
8 Delete dynamic links of the affected PAPS (if it is needed).
Step example
cmm nsvcEndps remove --papsId 0
10.5.2 Activating the links after scale out

Unlock the static links and recreate the dynamic links of the affected PAPS.
Procedure
1 Create the static links (if it is needed).
Step example
cmm nsvc create --nsvcName 1 --nsvcStatus locked --
remoteIpEndpoint x.x.x.x --remoteUdpPort 3000 --remoteSignWeight
1 --papsId 0 --re moteIpEndpointVersion IPV4 --nsvcId 1 --
remoteDataWeight 15 --nseId 2510
2 Unlock the static links of the affected PAPS.
Step example
cmm nsvcAdmin modify --papsId 0 --state unlocked
3 Recreate the dynamic links of the affected PAPS.
Step example
cmm nsvcEndps add --papsId 0

SGSN User Guide
10.5.3 Unblocking PAPS 2G/3G graceful shutdown

Use the maintForPaps command to cancel the mass detach procedure and unblock
PAPS.
Procedure
1 Cancel the active mass detach procedure for the PAPS.
Step example
cmm maintForPaps modify --massDetach CANCEL --rat ALL 0
Step result
+---------------+--------+
| Field | Value |
+---------------+--------+
| maintForPaps | 0 |
| blockForMaint | OFF |
| rat | ALL |
| massDetach | CANCEL |
+---------------+--------+
2 Unblock PAPS.
Step example
cmm maintForPaps modify --blockForMaint DACT 0
3 Check PAPS status.
Step example
cmm outputPapsStatus show paps0
Step result

SGSN User Guide
+-----------------------+---------------------+
| Field | Value |
+-----------------------+---------------------+
| outputPapsStatus | paps0 |
| active | false |
| blockForMaint | Unblocked |
| bfMRespCode | 0 |
| bfMRespCodeTimestamp | 2019-01-16 11:19:03 |
| massDetach | Idle |
| mDRespCode | 0 |
| mDRespCodeTimestamp | 2019-01-16 11:17:14 |
| offload | Idle |
| offlRespCode | |
| offlRespCodeTimestamp | 2019-01-16 08:41:41 |
+-----------------------+---------------------+
4 Delete PAPS record from maintForPaps list.
Step example
cmm maintForPaps delete 0
Step result
+--------------+-------+
| Field | Value |
+--------------+-------+
| maintForPaps | 0 |
+--------------+-------+
5 Check PAPS maintenance.
cmm maintForPaps list

Step result
+--------------+-------+
| NAME | VALUE |
+--------------+-------+
| | |
+--------------+-------+

SGSN User Guide
10.6 IPPS graceful shutdown (Feature f70002-02 - 150):

feature summary
This feature enables the emptying of the IPPS in a controlled way, minimizing the impact
to subscribers when an operator is doing maintenance work.
Table 159: IPPS graceful shutdown (Feature f70002-02 – 150): feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration management Command serviceState
Counters None
Alarms None
Feature ID f70002-02 – 150
10.6.1 Configuring IPPS graceful shutdown

The procedure includes steps for locking and showing an IPPS.
Procedure
1 Lock the IPPS.
cmm serviceState modify --svcState locked IPPS~0

When an IPPS is in the locked state, this IPPS is not selected for new PDPs from the
PAPS (apart of secondary PDPs which must be in the same IPPS as the Primary).

SGSN User Guide
Note:
The recommended draining period is ~30 minutes.
2 Show an IPPS.
Step example
cmm serviceState show IPPS~0
Note:
In case this procedure is followed by an IPPS scale-in, all the remaining active
bearers still served by this IPPS will be dropped but will be recreated in another
IPPS as soon as there is an UE initiated activity related to a dropped bearer.
10.7 Overload control (Features SG01037, f60210-20 and

The purpose of overload control is to ensure that as many packets are routed through as
possible and to ensure that the signaling is working without delay. The feature controls
both the signaling and data load so all units and processes function efficiently together in
a balanced way.
Table 160: Overload control (Features SG01037, f60210-20 and f60210-21): feature summary
Function Impact
Capacity None
Restrictions None
Conguration management Command prFile, parameter solc.

SGSN User Guide
Function Impact
Counters GPRS Overload Control Measurement (011)

• M011C019 / ATTACH IS REJECTED DUE TO OVERLOAD
• M011C020 / ATTACH IS DROPPED DUE TO OVERLOAD
• M011C021 / PDP ACTIVATION IS REJECTED DUE TO OVERLOAD
• M011C022 / PDP ACTIVATION IS DROPPED DUE TO OVERLOAD
• M011C023 / PDP MODIFICATION IS REJECTED DUE TO OVERLOAD
• M011C024 / PDP MODIFICATION IS DROPPED DUE TO OVERLOAD
• M011C025 / ROUTING AREA UPDATE IS REJECTED DUE TO OVERLOAD
• M011C026 / ROUTING AREA UPDATE IS DROPPED DUE TO OVERLOAD
• M011C027 / ATTACH IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C028 / PDP ACTIVATION IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C029 /PDP MODIFICATION IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C030 / ROUTING AREA UPDATE IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C031 / UPDATE PDP CONTEXT IS REJECTED DUE TO OVERLOAD
• M011C032 / VERSION 2 UPDATE BEARER REQUEST IS REJECTED DUE TO OVERLOAD
• M011C033 / VERSION 2 MODIFY BEARER REQUEST IS REJECTED DUE TO OVERLOAD
• M011C034 / VERSION 2 CREATE BEARER REQUEST IS REJECTED DUE TO OVERLOAD
• M011C035 / FORWARD RELOCATION REQUEST IS REJECTED DUE TO OVERLOAD
• M011C036 / VERSION 2 FORWARD RELOCATION REQUEST IS REJECTED DUE TO OVERLOAD
• M011C037 / VERSION 2 DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO OVERLOAD
• M011C038 / DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO OVERLOAD
• M011C039 / IDENTIFICATION REQUEST IS REJECTED DUE TO OVERLOAD
• M011C040 / VERSION 2 IDENTIFICATION REQUEST IS REJECTED DUE TO OVERLOAD
• M011C042 / VERSION 2 UPDATE BEARER REQUEST IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C043 / VERSION 2 MODIFY BEARER REQUEST IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C044 / VERSION 2 CREATE BEARER REQUEST IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C045 / FORWARD RELOCATION REQUEST IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C046 / VERSION 2 FORWARD RELOCATION REQUEST IS REJECTED DUE TO SUBSCRIBER DB
OVERLOAD
• M011C047 / VERSION 2 DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO SUBSCRIBER DB
OVERLOAD
• M011C048 / DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C049 / IDENTIFICATION IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C050 / VERSION 2 IDENTIFICATION IS REJECTED DUE TO SUBSCRIBER DB OVERLOAD
• M011C051 / UPDATE PDP CONTEXT IS DROPPED DUE TO OVERLOAD
• M011C052 / VERSION 2 UPDATE BEARER REQUEST IS DROPPED DUE TO OVERLOAD
• M011C053 / VERSION 2 MODIFY BEARER REQUEST IS DROPPED DUE TO OVERLOAD
• M011C054 / VERSION 2 CREATE BEARER REQUEST IS DROPPED DUE TO OVERLOAD
• M011C055 / FORWARD RELOCATION REQUEST IS DROPPED DUE TO OVERLOAD
• M011C056 / VERSION 2 FORWARD RELOCATION REQUEST IS DROPPED DUE TO OVERLOAD
• M011C057 / VERSION 2 DOWNLINK DATA NOTIFICATION IS DROPPED DUE TO OVERLOAD
• M011C058 / DOWNLINK DATA NOTIFICATION IS DROPPED DUE TO OVERLOAD
• M011C059 / IDENTIFICATION REQUEST IS DROPPED DUE TO OVERLOAD
• M011C060 / VERSION 2 IDENTIFICATION REQUEST IS DROPPED DUE TO OVERLOAD
• M011C061 / GB ATTACH IS DROPPED DUE TO STORM HANDLING
GPRS Iu OLC Measurement (028):
• M028C013 / IU ATTACH IS REJECTED DUE TO OVERLOAD
• M028C014 / IU ATTACH IS DROPPED DUE TO OVERLOAD
• M028C015 / IU PDP ACTIVATION IS REJECTED DUE TO OVERLOAD
• M028C016 / IU PDP ACTIVATION IS DROPPED DUE TO OVERLOAD
• M028C017 / IU PDP MODIFICATION IS REJECTED DUE TO OVERLOAD
• M028C018 / IU PDP MODIFICATION IS DROPPED DUE TO OVERLOAD
• M028C019 / IU ROUTING AREA UPDATE IS REJECTED DUE TO OVERLOAD
• M028C020 / IU ROUTING AREA UPDATE IS DROPPED DUE TO OVERLOAD
• M028C021 / IU SERVICE REQUEST IS REJECTED DUE TO OVERLOAD
• M028C022 / IU SERVICE REQUEST IS DROPPED DUE TO OVERLOAD
• M028C023 / IU ATTACH IS REJECTED DUE TO VOLTDB
• M028C024 / IU PDP ACTIVATION IS REJECTED DUE TO VOLTDB
• M028C025 / IU PDP MODIFICATION IS REJECTED DUE TO VOLTDB
• M028C026 / IU ROUTING AREA UPDATE IS REJECTED DUE TO VOLTDB
• M028C027 / IU SERVICE REQUEST IS REJECTED DUE TO VOLTDB
For more information, see Counters.
Alarms The following alarms are set by the OLC process indicating that one or more PAPS processes has
exhibited an overload in CPU resources by exceeding limits:
• 14097 PapsApplicationCpuMinorOverload
• 14098 PapsApplicationCpuMajorOverload
• 14099 PapsApplicationCpuCriticalOverload
PAPS will start shedding procedures partially in PapsApplicationCpuMajorOverload and fully in
PapsApplicationCpuCriticalOverload in order to reduce the overload. Alarms are cancelled once the
CPU consumption of the process falls below that limits.

SGSN User Guide
Function Impact
Feature ID SG01037, f60210-20, f60210-21
10.8 SGSN safety net overload (Feature f10702-01):

feature summary
This feature offers an additional level of protection that acts before CPU overload
protection. The feature ensures that the communicated capacity and performance is
achieved. Additionally, it provides protection for PAPS and IPDS against attach/RAU
storms.
Table 161: SGSN safety net overload (Feature f10702-01): feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent CPU overload control in PAPS (Feature f60210-21)

features
Restrictions None
Conguration Command gParms, parameters

management • enableCpuBasedControlOnly
• threegAttachRateLimitOverrideAtIpds
• threegIsauRateLimitOverrideAtIpds
• twogIsauRateLimitOverride
• threegIsauRateLimitOverride
• twogAttachRateLimitOverride
• threegAttachRateLimitOverride

SGSN User Guide
Function Impact
Counters GPRS Data Measurement (003):

• M003C162 / GEA0 CONTROL PLANE MESSAGES SENT IN UL
• M003C163 / GEA0 CONTROL PLANE MESSAGES SENT IN DL
• M003C164 / GEA0 USER PLANE PACKETS SENT IN UL
• M003C165 / GEA0 USER PLANE PACKETS SENT IN DL
• M003C178 / GEA0 DATA IN KBYTES SENT IN UL
• M003C179 / GEA0 DATA IN KBYTES SENT IN DL
GPRS Overload Control Measurement (011):
• M011C061 / GB ATTACH IS DROPPED DUE TO STORM HANDLING
• M011C062 / GB RAU IS DROPPED DUE TO STORM HANDLING
• M011C063 / ATTACH IS REJECTED DUE TO SAFETY NET
• M011C064 / PDP ACTIVATION IS REJECTED DUE TO SAFETY NET
• M011C065 / PDP MODIFICATION IS REJECTED DUE TO SAFETY NET
• M011C066 / RAU IS REJECTED DUE TO SAFETY NET
• M011C067 / PDP UPDATE IS REJECTED DUE TO SAFETY NET
• M011C068 / V2 UPDATE BEARER REQUEST IS REJECTED DUE TO SAFETY NET
• M011C069 / V2 MODIFICATION BEARER REQUEST IS REJECTED DUE TO
SAFETY NET
• M011C070 / V2 CREATE BEARER REQUEST IS REJECTED DUE TO SAFETY NET
• M011C071 / FORWARD RELOCATION REQUEST IS REJECTED DUE TO SAFETY
NET
• M011C072 / V2 FORWARD RELOCATION REQUEST IS REJECTED DUE TO
SAFETY NET
• M011C073 / V2 DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO
SAFETY NET
• M011C074 / DOWNLINK DATA NOTIFICATION IS REJECTED DUE TO SAFETY
NET
GPRS Iu OLC Measurement (028):
• M028C031 / IU ATTACH IS DROPPED DUE TO STORM HANDLING
• M028C032 / IU RAU IS DROPPED DUE TO STORM HANDLING
• M028C033 / IU ATTACH IS REJECTED DUE TO SAFETY NET
• M028C034 / IU PDP ACTIVATION IS REJECTED DUE TO SAFETY NET
• M028C035 / IU PDP MODIFICATION IS REJECTED DUE TO SAFETY NET
• M028C036 / IU RAU IS REJECTED DUE TO SAFETY NET
• M028C037 / IU SERVICE REQUEST IS REJECTED DUE TO SAFETY NET

SGSN User Guide
Function Impact
Alarms 14117 PapsApplicationPrbMessageQueueMinorOverload

14118 PapsApplicationPrbMessageQueueMajorOverload
14119 PapsApplicationPrbMessageQueueCriticalOverload
14120 PapsApplicationSafetyNetBreach
14121 PapsApplicationMessageStormDetected
The following alarm is relevant to IPDS and issued when IPDS storm has been
detected for SGSN attaches and/or RAUs:
40510 LSS_softwareAllocatedResourceOverload
10.8.1 Configuring SGSN safety net overload

The SGSN safety net overload feature is by default activated. The rate limits for attach
and RAU storm handling are configurable through global parameters.
Before you start
Note:
The safety net overload feature is controlled through the

enableCpuBasedControlOnly global parameter. The default value is No, meaning
that overload control is performed taking into account message rate and storm rate
(safety net feature is enabled). The safety net feature should not be disabled.
▪ Configure 2G/3G attach/RAU rate limits.
Modify the rate limits with the following command:
cmm gParms modify --gParmName <gparm> --gParmValue <value>

SGSN User Guide
Table 162: Attach and RAU rate limits (gParms)
gParm name Description Value range

and default
threegAttachRateLimitOverrideAt Number of 3G attaches allowed per 0-15000

Ipds second per IPDS, after which IPDS 10000
starts dropping attaches until the rate
is below the limit at IPDS.
threegIsauRateLimitOverrideAtIp Number of 3G ISRAUs allowed per 0-20000

ds second per IPDS, after which IPDS 15000
starts dropping 3G ISRAUs until the
rate is below the limit at IPDS.
twogIsauRateLimitOverride Number of 2G ISRAUs allowed per 0-5000

second per PAPS, after which PAPS 1800
rate is below the limit.
threegIsauRateLimitOverride Number of 3G ISRAUs allowed per 0-5000

rate is below the limit.
twogAttachRateLimitOverride Number of 2G attaches allowed per 0-5000

is below the limit.
threegAttachRateLimitOverride Number of 3G attaches allowed per 0-5000

is below the limit.
10.9 Performance management (Features SG01016,

SG01085, SG01028, SG01131, f60210-10, f13012-02,
With these features, you can collect statistical data about the general packet radio
service (GPRS) network and SGSN.
Table 163: Performance management (Features SG01016, SG01085, SG01028, SG01131,

f60210-10, f13012-02, f13012-03): feature summary
Function Impact

SGSN User Guide
Function Impact
Compliance Partially compliant with 3GPP TS 52.402 Telecommunication

Management; Performance Management (PM); Performance
Measurements - GSM, version 4.1.0.
Capacity None
Interworking/dependen • Quality of service (Feature SG01007)

t features • RIM procedure support (Features SG01024 and SG01232)
• Gb over IP (Feature SG01048)
• Internal load balancing and admission control (Feature SG01060)
• QoS control for roaming subscribers (Feature SG01067)
(Feature SG02017)
• Detach timer optimization and control (Feature SG02035)
• HLR based 2G/3G access control (Feature SG02114)
• HSDPA, HSUPA and HSPA+ support (Features SG02104, SG01113,
SG02198)
• CMM support for performance measurements (f60110-11)
Restrictions • In order to prevent complexity and capacity problems,only one

measurement of each measurement type can be running at a time, but
several measurement types can be running simultaneously. By default,
all measurement types are enabled
• The measurement period for producing counters from the application
is pre-dened to be 1 min for all measurement types. This
measurement period is not congurable.
• Measurement types M01, M02, M10 support reporting on routing area
level.
• Measurement types M16, M17 support reporting on routing area level.
• Performance management (Feature SG01028) are not supported.
• With PM evolution features f13012-02 and f13012-03, all the counter
data has been moved from InuxDB to PM Aggregation datastores in
NECC. As the result of this architectural change also Grafana tool
integration has been removed from CMM in CMM20.0 BR, as it uses
counter data stored in InuxDB as source data for visualization.
• From CMM20.0 BR onwards, the CMM supports sending of close to
real time counters (pre-dened counter set in the CMM) to external
Prometheus server via external Prometheus Pushgateway.
• VM statistics based formerly on data provided by Telegraf are
provided by a specic process running in every VM.

SGSN User Guide
Function Impact
Conguration Commands counter and counterGroup to display PM data. With

management f13012-03 PM evolution for component counters, most component
counters are aggregated on CMM level and cannot be queried per VM.
Also, parameters limit and interval do not apply.
Command plmnStatistic (to enable reporting of counters from
Measurement Group M032, PLMN Measurement).
Commands pmJob, pmJobMeas, pmJobSched,
pmMeasGroupName and pmMeasGroups to manage the
performance measurement job entry.
Commands prometheusGW and firewallRule
Command features, parameters (by default, true):
• advancedCdr
• advancedData
• advancedData2
• advancedMobilityMan
• advancedSessionMan
• advancedUser
• cellSaStat
• mobilityManCause
• mmCause2
• sessionManCause
• sessionManCause2
• ranapCause
• plmn
• hspaStatistics
• security
Command prFile, parameter sgsnSS7Statistics
For Prometheus gateway conguration: Command gParms, parameter
enablePrometheusGW (see IntegratingCMM)
Counters See CMM Counters
Alarms 3003 INCORRECT MEASUREMENT DATA

LSS_pmIntervalDataMissing
Feature ID SG01016, SG01085, SG01131, f60210-10, f13012-02, f13012-03
10.9.1 Counter categories in CMM

The counters collected by CMM can be divided in three different categories: static
counters, component counters, and VM counters.
All the counters are stored in NECC in PM aggregation datastores and kept for 15 minutes.

SGSN User Guide
Static counters
Static counters (service level counts) are reported per VM and are pushed to PM aggregation
datastores once per minute.
Note:
Measurement groups m044 and m045 are pushed to PM aggregation with 5 minutes
interval even if they contain static counters.
Component counters
Component counters (counts collected on a tracking area, routing area, and cell area) are
aggregated so that they are reported on CMM level instead of per VM and are pushed to PM
aggregation datastores once per 5 minutes.
Note:
The following measurement groups are handled differently as they are not
aggregated but reported with VM information:
m135 EPS IPDS Inter Service Communication
m137 IPDS Interface Per Interface Type
Measurement group m135 is pushed to PM aggregator in NECC with 1 minute interval

even it contains component counters.
VM counters
VM counters report HW usage. These counters are provided by specific a process running in
each VM, and the counters are pushed to PM aggregation datastores once per minute.
10.9.2 Average, minimum, and maximum counter values

CMM uses internal counters to track events and activities that are used for calculating
average, minimum, and maximum PM counter values.
Samples of the internal counters are taken every 10 seconds and each minute new average,
minimum, and maximum values are calculated using a sliding 5-minute window (that is, the
values from the current minute are aggregated with the calculated values from each of the

SGSN User Guide
4 previous 1-minute intervals). The new values are then pushed from the VM to PM
aggregator in the NECC, meaning that new values are stored in PM aggregation datastores
every 1 minute (static counters) or every 5 minutes (component counters), and kept in
datastores for 15 minutes.
The following examples describe how minimum, maximum, and average counters are
calculated and displayed in the CLI output using various query methods. The examples are
for static counters.
Example: Query with --sourceHost=’<VM>’

When queried with a version of the CLI command such as cmm counter show <PI ID> -
-sourceHost=’<VM>’ (where VM is a comma-separated VM list), counter values are
returned as follows:
Minimum:
The output displays one value for each of the specified VMs. In this case, the value is the
smallest value found across all samples observed on the VM during the requested
reporting period.
Maximum:
largest value found across all samples observed on the VM during the requested
reporting period.
Average:
average of all values found across all samples observed on the VM during the requested
reporting period.
Example: Query with --sourceHost=’*’

When queried with a version of the CLI command such as cmm counter show <PI ID> -
-sourceHost=’*’, counter values are returned as follows:
Minimum:
The output displays one value for each VM. In this case, the value is the smallest value
found across all samples observed on the VM during the requested reporting period.
Maximum:
The output displays one value for each VM. In this case, the value is the largest value
found across all samples observed on the VM during the requested reporting period.
Average:
The output displays one value for each VM. In this case, the value is the average of all
values found across all samples observed on the VM during the requested reporting
period.

SGSN User Guide
Example: Query without --sourceHost=’*’, --sourceIp=’*’ or --source=’*’

When queried without --sourceHost=’*’, --sourceIp=’*’ or --source=’*’ (for
example, cmm counter show <PI ID>), counter values are as like when making query
with sourceHost=’*’ as it is default.
10.9.3 Displaying PM data

PM data is continuously collected in the CMM. You can display counter group and counter
details as well as the run-time values.
Before you start
Each counter has a unique performance indicator ID (PID) which is a combination of the
counter group in which it belongs and the counter number. For example, PID M101C000
indicates counter number 000 of the 101 - EPS CPPS Authentication counter group (PID
m101).
Note:
Command cmm counter supports sourceHost parameter for static counters

and VM counters. From component counters, sourceHost parameter is
supported only for counters in groups m135 and m137.
AMF specific measurement groups start from M171.
Procedure
1 Display CMM counter groups.
cmm counterGroup definition list
Step example

SGSN User Guide
+-----------+-----------------------------------------------------+
| GROUP PID | NAME |
+-----------+-----------------------------------------------------+
| m001 | GPRS Mobility Management |
| m002 | GPRS Session Management |
| m003 | GPRS Data Measurement |
| m004 | GPRS User Measurement |
| m150 | EPS CPPS Dedicated Bearer Per TAI |
| m151 | EPS CPPS Mobility Management Per TAI |
| m152 | EPS CPPS Handover Per TAI |
| m153 | CPU Usage Per Core |
+-----------+-----------------------------------------------------+
2 Display details of a counter group.
cmm counterGroup definition show <groupId>
Step example

SGSN User Guide
cmm counterGroup definition show m101
+-------------+-----------------------------------------------------+
| NAME | VALUE |
+-------------+-----------------------------------------------------+
| PID | m101 |
| Name | EPS CPPS Authentication |
| Alias | cauth |
| Description | The EPS CPPS Authentication measurement provides |
| | information about attempted, successful, and failed |
| | HSS and UE authentication procedures. |
| | The counters are collected on the MME level. |
| Members | m101c000 |
| | m101c001 |
| | m101c002 |
| | m101c003 |
| | m101c004 |
...
3 Display counters.
cmm counter definition list
Step example
cmm counter definition list
...
|m118c395|FAILED EXTENDED SERVICE REQUESTS FOR MOBILE TERMINATING CSFB - NET FAIL |
| |VS.NbrFailedMobileTermCSFBextServiceReq_NetwkFailure |
|m118c396|FAILED EXTENDED SERVICE REQUESTS FOR MOBILE TERMINATING CSFB - CS NOT AV |
| |VS.NbrFailedMobileTermCSFBextServiceReq_CSnotAvailable |
|m118c397|FAILED EXTENDED SERVICE REQUESTS FOR MOBILE TERMINATING CSFB - CONG |
| |VS.NbrFailedMobileTermCSFBextServiceReq_Congestion |
|m118c398|FAILED EXTENDED SERVICE REQUESTS FOR MOBILE TERMINATING CSFB - SEV NET FAIL|
| |VS.NbrFailedMobileTermCSFBextServiceReq_SevereNetwkFailure |
|m118c399|S1-AP REQUESTS FAILED BY ENODEB FOR MOBILE TERMINATING CSFB - OTHER |
| |VS.NbrFailedMobileTermCSFBS1APreq_Other
...

SGSN User Guide
Step example
+-------------+----------------------------------------------------------------------------
---+
| COUNTER PID | NAME
+-------------+----------------------------------------------------------------------------
---+
| m001c000 | SUCC GPRS ATTACH
| | VS.SuccGprsAttach
| m001c004 | SUCC IMSI ATTACH
| | VS.SuccImsiAttach
| m001c005 | FAIL IMSI ATTACH
| | VS.FailImsiAttach
| m001c006 | FAIL GPRS ATTACH DUE MS ERROR
| m153c003 | AVERAGE PER CORE CPU USAGE
| | VS.avePerCoreCpuUsage
| m153c004 | PEAK PER CORE CPU USAGE
| | VS.peakPerCoreCpuUsage
| m153c005 | CPU STOLEN TIME
| | VS.CpuStolenTime
+-------------+----------------------------------------------------------------------------
---+

SGSN User Guide
Step example
You can limit output by group cmm counter definition list --group
<groupid>
cmm counter definition list --group m101
+----------+--------------------------------------------------------+
| PID | NAME |
+----------+--------------------------------------------------------+
| m101c000 | ATTEMPTED AUTHENTICATION REQUESTS HSS |
| | VS.AttAuthRequestsHSS |
| m101c001 | SUCCESSFUL HSS AUTHENTICATION PROCEDURES |
| | VS.NbrSuccessAuthRequestsHSS |
| m101c002 | FAILED AUTHENTICATION REQUESTS HSS - OTHER |
| | VS.NbrFailedAuthRequestsHSS_Other |
| m101c003 | FAILED AUTHENTICATION REQUESTS HSS - OTHER CC |
| | VS.NbrFailedAuthRequestsHSS_OtherCauseCode |
| m101c004 | FAILED AUTHENTICATION REQUESTS HSS - IMSI UNK HSS |
| | VS.NbrFailedAuthRequestsHSS_IMSIunknownInHSS |
...
Step example
A large group (like m118) still contains hundreds of counters. The query can be further
limited by changing group id to include the first digit of the counter so that it shows
only counters from group m118 that are yxx (y being given number), for example: cmm
counter definition list --group m118c0
4 Display detailed counter definitions.
cmm counter definition show <pid>
Step example

SGSN User Guide
[root@necc0 ~]# cmm counter definition show m118c399
+-------------+---------------------------------------------------------+
| NAME | VALUE |
+-------------+---------------------------------------------------------+
| PID | m118c399 |
| Name | S1-AP REQUESTS FAILED BY ENODEB FOR MOBILE TERMINATING |
| | CSFB - OTHER |
| 3GPP Name | VS.NbrFailedMobileTermCSFBS1APreq_Other |
| Source | cpps |
| Summary | Counts the number of times the MME receives an S1-AP |
| | failure message from the eNodeB during a Mobile |
| | Terminating CS Fallback due to Other reasons |
| Description | Pegged when the MME receives an INITIAL CONTEXT SETUP |
| | FAILURE or UE CONTEXT MODIFICATION FAILURE with cause |
| | Other reasons from the eNodeB during an extended |
| | service request procedure for Mobile Terminating CS |
| | Fallback. |
| Access | mme |
| Category | service |
+-------------+---------------------------------------------------------+
5 Display counter values.

SGSN User Guide
cmm counter list [ --endTime <string> ] [ --entity <string> ]
[ --entity_actc <string> ] [ --entity_bearerclass <string> ]
[ --entity_cellid <string> ] [ --entity_core <string> ]
[ --entity_disk <string> ] [ --entity_filesystem <string> ]
[ --entity_hss <string> ] [ --entity_interface <string> ]
[ --entity_interfacetype <string> ] [ --entity_iulac <string> ]
[ --entity_iuraplmn <string> ] [ --entity_iurarac <string> ]
[ --entity_iurarnc <string> ] [ --entity_iusalac <string> ]
[ --entity_iusaplmn <string> ] [ --entity_lac <string> ]
[ --entity_lip <string> ] [ --entity_liptp <string> ]
[ --entity_ludp <string> ] [ --entity_nsei <string> ]
[ --entity_nsvci <string> ] [ --entity_olac <string> ]
[ --entity_operdefqci <string> ] [ --entity_oplmn <string> ]
[ --entity_orac <string> ] [ --entity_ornc <string> ]
[ --entity_pagingtype <string> ] [ --entity_partner <string> ]
[ --entity_plmn <string> ] [ --entity_pltc <string> ]
[ --entity_rac <string> ] [ --entity_rautype <string> ]
[ --entity_reselection <string> ] [ --entity_rip <string> ]
[ --entity_riptp <string> ] [ --entity_rncid <string> ]
[ --entity_rudp <string> ] [ --entity_sac <string> ]
[ --entity_snet <string> ] [ --entity_spc <string> ]
[ --entity_ssname <string> ] [ --entity_ssnumber <string> ]
[ --entity_tac <string> ] [ --group <string> ] [ --mode <string> ]
[ --period <string> ] [ --pid <string> ] [ --source <string> ]
[ --sourceHost <string> ] [ --sourceIp <string> ]
[ --startTime <string> ]
Step example
[cmm@cpet60-ta-necc0 ~]$ cmm counter list --pid m128c003 --startTime '2019-09-16 16:00:15'
+----------+-------------------+----------------+-------------------------------+----------
--------------------+
| PID | NAME | 3GPP NAME | TIME | VALUE
+----------+-------------------+----------------+-------------------------------+----------
--------------------+
| m128c003 | AVERAGE CPU USAGE | VS.aveCpuUsage | 2019-09-16 16:25:00.000+03:00 | 7

SGSN User Guide
| | | | | source:
169.254.64.30:necc0 |
| | | | 2019-09-16 16:25:00.000+03:00 | 4
| | | | | source:
169.254.64.31:necc1 |
| | | | 2019-09-16 16:25:00.000+03:00 | 2
| | | | | source:
169.254.64.32:necc2 |
| | | | 2019-09-16 16:25:00.000+03:00 | 8
| | | | | source:
169.254.64.210:dbs0 |
| | | | 2019-09-16 16:25:00.000+03:00 | 3
| | | | | source:
169.254.64.211:dbs1 |
| | | | 2019-09-16 16:25:00.000+03:00 | 8
| | | | | source:
169.254.64.212:dbs2 |
| | | | 2019-09-16 16:25:00.000+03:00 | 3
| | | | | source:
169.254.64.213:dbs3 |
| | | | 2019-09-16 16:25:00.000+03:00 | 3
| | | | | source:
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:25:00.000+03:00 | 4
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:25:00.000+03:00 | 4
| | | | | source:
169.254.64.112:cpps2 |
| | | | 2019-09-16 16:25:00.000+03:00 | 4

SGSN User Guide
| | | | | source:
169.254.64.70:ipds0 |
| | | | 2019-09-16 16:25:00.000+03:00 | 11
| | | | | source:
169.254.64.71:ipds1 |
| | | | 2019-09-16 16:25:00.000+03:00 | 39
+----------+-------------------+----------------+-------------------------------+----------
--------------------+
Step example
[cmm@cpet60-ta-necc0 ~]$ cmm counter list --group m118c0
+----------+---------------------------------+-------------------------------+-------------------------------+-----------------
-------------+
+----------+---------------------------------+-------------------------------+-------------------------------+-----------------
-------------+
| m118c074 | AVERAGE DURATION OF ATTACH | VS.AveDurationAttach | 2019-09-16 16:34:00.000+03:00 | 17
| | PROCEDURES | | | source:
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:34:00.000+03:00 | 18
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:34:00.000+03:00 | 17
| | | | | source:
169.254.64.112:cpps2 |
| m118c075 | MAXIMUM DURATION OF ATTACH | VS.MaxDurationAttach | 2019-09-16
16:34:00.000+03:00 | 61 |
| | PROCEDURES | | | source:
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:34:00.000+03:00 | 40

SGSN User Guide
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:34:00.000+03:00 | 60
| | | | | source:
169.254.64.112:cpps2 |
| m118c080 | ATTEMPTED SGW RELOCATIONS FOR | VS.SgwRelocationServiceReqAtt | 2019-09-16 16:34:00.000+03:00 | 8282
| | SERVICE REQUESTS DUE TO SGW | | | source:
169.254.64.110:cpps0 |
| | FAILURE | | |
| | | | 2019-09-16 16:34:00.000+03:00 | 8105
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:34:00.000+03:00 | 8439
| | | | | source:
169.254.64.112:cpps2 |
| m118c094 | ATTEMPTED SGW RELOCATIONS DUE | VS.SgwRelocationAtt | 2019-09-16 16:34:00.000+03:00 | 8282
| | TO SGW FAILURE | | | source:
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:34:00.000+03:00 | 8105
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:34:00.000+03:00 | 8439
| | | | | source:
169.254.64.112:cpps2 |
+----------+---------------------------------+-------------------------------+-------------------------------+-----------------
-------------+
[cmm@cpet60-ta-necc0 ~]$

SGSN User Guide
Step example
[cmm@cpet60-ta-necc0 ~]$ cmm counter list --group m128 --startTime '2019-09-16 16:40:15'
+----------+------------------------+---------------------+-------------------------------+---------------
----------+
+----------+------------------------+---------------------+-------------------------------+---------------
----------+
| m128c003 | AVERAGE CPU USAGE | VS.aveCpuUsage | 2019-09-16 16:45:00.000+03:00 | 6
| | | | | source:
169.254.64.30:necc0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 3
| | | | | source:
169.254.64.31:necc1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 1
| | | | | source:
169.254.64.32:necc2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 8
| | | | | source:
169.254.64.210:dbs0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 3
| | | | | source:
169.254.64.211:dbs1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 8
| | | | | source:
169.254.64.212:dbs2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 3
| | | | | source:
169.254.64.213:dbs3 |
| | | | 2019-09-16 16:45:00.000+03:00 | 4
| | | | | source:

SGSN User Guide
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 4
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 4
| | | | | source:
169.254.64.112:cpps2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 48
| | | | | source:
169.254.64.70:ipds0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 11
| | | | | source:
169.254.64.71:ipds1 |
| m128c004 | PEAK CPU USAGE | VS.peakCpuUsage| 2019-09-16 16:45:00.000+03:00 | 16
| | | | | source:
169.254.64.30:necc0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 9
| | | | | source:
169.254.64.31:necc1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 7
| | | | | source:
169.254.64.32:necc2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 10
| | | | | source:
169.254.64.210:dbs0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 4
| | | | | source:
169.254.64.211:dbs1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 11

SGSN User Guide
| | | | | source:
169.254.64.212:dbs2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 4
| | | | | source:
169.254.64.213:dbs3 |
| | | | 2019-09-16 16:45:00.000+03:00 | 6
| | | | | source:
169.254.64.110:cpps0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 6
| | | | | source:
169.254.64.111:cpps1 |
| | | | 2019-09-16 16:45:00.000+03:00 | 7
| | | | | source:
169.254.64.112:cpps2 |
| | | | 2019-09-16 16:45:00.000+03:00 | 49
| | | | | source:
169.254.64.70:ipds0 |
| | | | 2019-09-16 16:45:00.000+03:00 | 13
| | | | | source:
169.254.64.71:ipds1 |
+----------+------------------------+----------------+-------------------------------+--------------------
----------+
6 Display the run-time values of a counter.

SGSN User Guide
cmm counter show [ --endTime <string> ] [ --entity <string> ]
[ --entity_actc <string> ] [ --entity_bearerclass <string> ]
[ --entity_cellid <string> ] [ --entity_core <string> ]
[ --entity_disk <string> ] [ --entity_filesystem <string> ]
[ --entity_hss <string> ] [ --entity_interface <string> ]
[ --entity_interfacetype <string> ] [ --entity_iulac <string> ]
[ --entity_iuraplmn <string> ] [ --entity_iurarac <string> ]
[ --entity_iurarnc <string> ] [ --entity_iusalac <string> ]
[ --entity_iusaplmn <string> ] [ --entity_lac <string> ]
[ --entity_lip <string> ] [ --entity_liptp <string> ]
[ --entity_ludp <string> ] [ --entity_nsei <string> ]
[ --entity_nsvci <string> ] [ --entity_olac <string> ]
[ --entity_operdefqci <string> ] [ --entity_oplmn <string> ]
[ --entity_orac <string> ] [ --entity_ornc <string> ]
[ --entity_pagingtype <string> ] [ --entity_partner <string> ]
[ --entity_plmn <string> ] [ --entity_pltc <string> ]
[ --entity_rac <string> ] [ --entity_rautype <string> ]
[ --entity_reselection <string> ] [ --entity_rip <string> ]
[ --entity_riptp <string> ] [ --entity_rncid <string> ]
[ --entity_rudp <string> ] [ --entity_sac <string> ]
[ --entity_snet <string> ] [ --entity_spc <string> ]
[ --entity_ssname <string> ] [ --entity_ssnumber <string> ]
[ --entity_tac <string> ] [ --group <string> ] [ --mode <string> ]
[ --period <string> ] [ --source <string> ] [ --sourceHost <string> ]
[ --sourceIp <string> ] [ --startTime <string> ]
Step example
[cmm@cpet60-ta-necc0 ~]$ cmm counter show m128c003
+-------------+--------------------------------------------------------------------------+
| NAME | VALUE |
+-------------+--------------------------------------------------------------------------+
| Value | 6 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.30:necc0 |
| ---------- | ------------------------------ |
| Value | 3 |
| Time | 2019-09-16 17:05:00.000+03:00 |

SGSN User Guide
| Source | 169.254.64.31:necc1 |
| ---------- | ------------------------------ |
| Value | 1 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.32:necc2 |
| ---------- | ------------------------------ |
| Value | 8 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.210:dbs0 |
| ---------- | ------------------------------ |
| Value | 3 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.211:dbs1 |
| ---------- | ------------------------------ |
| Value | 8 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.212:dbs2 |
| ---------- | ------------------------------ |
| Value | 4 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.110:cpps0 |
| ---------- | ------------------------------ |
| Value | 4 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.111:cpps1 |
| ---------- | ------------------------------ |
| Value | 4 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.112:cpps2 |
| ---------- | ------------------------------ |
| Value | 48 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.70:ipds0 |
| ---------- | ------------------------------ |
| Value | 11 |
| Time | 2019-09-16 17:05:00.000+03:00 |
| Source | 169.254.64.71:ipds1 |
| ---------- | ------------------------------ |
| PID | m128c003 |

SGSN User Guide
| Name | AVERAGE CPU USAGE |
| 3GPP Name | VS.aveCpuUsage |
| Summary | This counter indicates the average CPU utilization in the current |
| | interval. |
| Description | This counter is pegged every 10s over the reporting interval. |
| Logic | mean |
| Unit | percentage |
| Access | amf/mme/sgsn |
| Category | syscpuusage |
| Service | all |
+-------------+--------------------------------------------------------------------------+
Step example
[root@necc0 ~]# cmm counter show m129c000 --entity_disk '*'
+-------------+-----------------------------------------------------+
| NAME | VALUE |
+-------------+-----------------------------------------------------+
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| Source | host: cpps0.local |
| Entity | disk: sda1 |
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| Source | host: dbs0.local |
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| Source | host: dbs1.local |
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| Source | host: ipds0.local |

SGSN User Guide
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| Source | host: necc0.local |
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| ---------- | ------------------------------ |
| Value | 0 |
| Time | 2017-01-26 07:14:30.204-06:00 |
| ---------- | ------------------------------ |
| PID | m129c000 |
| Name | DISK INPUT/OUTPUT READ RATE |
| 3GPP Name | VS.diskIOReadRate |
| Summary | This counter indicates the disk I/O read rate in |
| Description | kB/sec. This counter is pegged whenever a disk Read |
| | is performed. This count reports the IO rate of all |
| | the disks |
| Logic | mean |
| Unit | kilobyte/second |
| Access | mme |
| Category | sysdiskio |
| Service | all |
+-------------+-----------------------------------------------------+
10.9.4 Close to real-time counters

CMM supports close to real-time counters by providing an interface towards external
Prometheus Pushgateway. The close to real-time counters are based on a pre-defined
counter set containing all VM counters and part of static counters. All the counters in this

SGSN User Guide
pre-defined set are pushed to external Prometheus Pushgateway (with 1 minute interval)
from where external Prometheus server scrapes the counter data for further analysis and
visualization. For example, use Grafana (that can be integrated in the Prometheus server).
The counters provided to external Prometheus are currently of two types: counters and
gauges.
A counter is a cumulative metric that represents a single monotonically increasing
counter whose value can only increase or be reset to zero on restart.
A gauge is a metric that represents a single numerical value that can arbitrarily go up and
down.
For a full list of counters supported as close to real time as well as definition as counter or
gauge towards Prometheus, see the Counters documents.
The CMM supports basic authentication towards Prometheus Pushgateway. Note that as
Prometheus does not currently support basic authentication, some 3rd party reverse proxy
software (for example nginx) should be used on the Prometheus side.
CMM provides job and instance with following values:

job:
cmm_mme
cmm_ta
cmm_qa
cmm_amf
instance: switch name, for example “cpet60-ta”
The CMM uses following labelling when providing close to real-time counter data to
Prometheus:
poolId
poolType
poolMember
Please refer to official Prometheus documentation for further information about labelling.
10.9.5 Configuring SGSN performance management

PM data is continuously collected in CMM. You can display counter group and counter
details as well as the run-time values. Feature configuration is also needed, for example,
to enable PLMN measurement and SS7 statistics counter collection.

SGSN User Guide
Before you start
All counters are numbered in the format myyycxxx, where myyy refers to the measurement
type and cxxx is the counter number of the measurement, for example, m001c002.
See SGSN Feature Overview for a list of SGSN measurements. All measurement and counter
descriptions can be found in CMM Counters.
Procedure
1 Check status of counter-related features.
The counter-related features listed below are by default enabled (true):

advancedCdr
advancedData
advancedData2
advancedMobilityMan
advancedSessionMan
advancedUser
cellSaStat
mobilityManCause
mmCause2
sessionManCause
sessionManCause2
ranapCause
plmn
hspaStatistics
security
You can check feature status using the cmm features show command and change
feature status using the cmm features modify command.
Step example
To change feature status: cmm features modify advancedData --status
true
2 Enable measurement group M032.
PLMN measurement (M032) provides information on attaches, routing area updates,

attached users and transferred 2G/3G data amounts over the Iu and Gb interfaces.
Events can be measured from ALL, HOME or ROAMING PLMNs and from specified PLMN.

SGSN User Guide
You can define a maximum of 24 PLMN types/ids that are collected. Counters are
collected on PLMN level.
To enable reporting of counters in measurement group M032:
cmm plmnStatistic create
--plmnType {ALL,HOME,ROAMING,PLMNID,INVALID}
--mcc <digits>
--mnc <digits>
plmnStatistic
Step example
cmm plmnStatistic create 1 –-plmnType ALL --mcc 234 --mnc 123
3 Enable SS7 statistics, if needed.
cmm prFile modify sgsnSS7Statistics --status true
10.9.6 Configuring performance measurement jobs

The procedure includes steps for creating, modifying, listing and deleting performance
measurement jobs.
Procedure
1 Create a performance measurement job entry.
cmm pmJob create
[--jobName <string> ]
[--granuPeriod {5,15}]
[--active {Suspended,Active}]
[--startDate <string>]
[--endDate <string>]
Step example

SGSN User Guide
cmm pmJob create --jobName testJob --granuPeriod 5
+-------------+-------------+
| Field | Value |
+-------------+-------------+
| pmJob | testJob |
| jobName* | testJob |
| granuPeriod | 5 |
| active | Suspended |
| longTerm | true |
| startDate | 17:09:11 |
| endDate | No_End_Date |
+-------------+-------------+
2 Show the detailed information of a performance measurement job entry.
Step example
cmm pmJob show defaultJob
+-------------+---------------+
| Field | Value |
+-------------+---------------+
| pmJob | defaultJob |
| jobName* | defaultJob |
| granuPeriod | 15 |
| active | Active |
| longTerm | true |
| startDate | No_Start_Date |
+-------------+---------------+
3 List all the performance measurement job entries.
Step example

SGSN User Guide
cmm pmJob list
+------------+-------------+--------+----------+---------------+-------------+
| pmJob | granuPeriod | active | longTerm | startDate | endDate |
+------------+-------------+--------+----------+---------------+-------------+
| defaultJob | 15 | Active | true | No_Start_Date | No_End_Date |
+------------+-------------+--------+----------+---------------+-------------+
4 Modify a performance measurement job entry.
Step example
cmm pmJob modify --jobName testJob --granuPeriod 15
+-------------+-------------+
| Field | Value |
+-------------+-------------+
| pmJob | testJob |
| longTerm | true |
| startDate | 17:09:20 |
+-------------+-------------+
5 Delete a performance measurement job entry.
Step example

SGSN User Guide
cmm pmJob delete --jobName testJob
+-------------+-------------+
| Field | Value |
+-------------+-------------+
| pmJob | testJob |
| longTerm | true |
| startDate | 17:09:20 |
+-------------+-------------+
6 Create PM job measurements.
cmm pmJobMeas create --jobName <string> --mts <string>
Step example
cmm pmJobMeas create --jobName testJob --mts cpuUsageCoreMts
+-----------+-------------------------+
| Field | Value |
+-----------+-------------------------+
| pmJobMeas | testJob~cpuUsageCoreMts |
| mts* | cpuUsageCoreMts |
+-----------+-------------------------+
7 Show the detailed information of PM job measurements.
cmm pmJobMeas show <pmJobMeas>
Step example

SGSN User Guide
cmm pmJobMeas show defaultJob~allMts
+-----------+-------------------+
| Field | Value |
+-----------+-------------------+
| pmJobMeas | defaultJob~allMts |
| jobName* | defaultJob |
| mts* | allMts |
+-----------+-------------------+
8 List all the PM job measurements.
Step example
cmm pmJobMeas list
+-------------------+
| pmJobMeas |
+-------------------+
| defaultJob~allMts |
+-------------------+
9 Delete PM job measurements.
cmm pmJobMeas delete <pmJobMeas>
Step example
cmm pmJobMeas delete testJob~cpuUsageCoreMts
+-----------+-------------------------+
| Field | Value |
+-----------+-------------------------+
| pmJobMeas | testJob~cpuUsageCoreMts |
| mts* | cpuUsageCoreMts |
+-----------+-------------------------+
10 Create PM job schedules.

SGSN User Guide
cmm pmJobSched create
--jobName <string>
--schedId <integer>
[--schedType {sun,mon,tue,wed,thu,fri,sat,dly,spd}]
[--colDate <string>]
[--startTime <string>]
[--endTime <string>]
Step example
cmm pmJobSched create --schedId 1 --jobName testJob --schedType dly --startTime
08:00 --endTime 14:00
+------------+-------------+
| Field | Value |
+------------+-------------+
| pmJobSched | testJob~1 |
| schedId* | 1 |
| schedType | dly |
| colDate | No_Spd_Date |
| startTime | 08:00 |
| endTime | 14:00 |
+------------+-------------+
11 Show PM job schedules.
Step example

SGSN User Guide
cmm pmJobSched show testJob~1
+------------+-------------+
| Field | Value |
+------------+-------------+
| schedId* | 1 |
| schedType | dly |
| endTime | 14:00 |
+------------+-------------+
12 List all the PM job schedules.
Step example
+--------------+-----------+-------------+-----------+---------+
| pmJobSched | schedType | colDate | startTime | endTime |
+--------------+-----------+-------------+-----------+---------+
| defaultJob~1 | dly | No_Spd_Date | 00:00 | 24:00 |
+--------------+-----------+-------------+-----------+---------+
13 Delete PM job schedules.
Step example

SGSN User Guide
cmm pmJobSched delete testJob~1
+------------+-------------+
| Field | Value |
+------------+-------------+
| schedId* | 1 |
| schedType | dly |
| endTime | 14:00 |
+------------+-------------+
14 List all the PM measurement group names.
cmm pmMeasGroupName list
Step example

SGSN User Guide
+------------------+-----------------+-----------------------------------------------------
--------------+
| pmMeasGroupName | groupLevel | measGroupDesc
+------------------+-----------------+-----------------------------------------------------
--------------+
| allMts | System_Non_Leaf | All Counts
| cAuthHssMts | System_Leaf | EPS CPPS Authentication Per HSS Group
| cAuthMts | System_Leaf | EPS CPPS Authentication Group
| cBsmMts | System_Leaf | EPS CPPS Bearer Session Management Group
| cBsmQciMts | System_Leaf | EPS CPPS Bearer Session Management Per Operator
Defined QCI Group |
| cBsmTaiMts | System_Leaf | EPS CPPS Bearer Session Management Per TAI Group
| pSgPaMts | System_Leaf | GPRS Gb SGSN Paging Measurement Group
| pTcapMts | System_Leaf | TCAP Performance and Utilization Measurement Group
| pUserMts | System_Leaf | GPRS User Measurement Group
| sysResUsageMts | System_Non_Leaf | System Resource Usage Count Group
| systemBaseMts | System_Non_Leaf | System Base Count Group
| systemServiceMts | System_Leaf | System Service Group
+------------------+-----------------+-----------------------------------------------------
--------------+
15 List all the PM measurement groups.

SGSN User Guide
cmm pmMeasGroups list
Step example
+------------------------------------------------------------------------------
-+
| pmMeasGroups
+------------------------------------------------------------------------------
-+
| allMts~cCompMts
|
| allMts~iCompMts
| allMts~pCompMts
| allMts~sysResUsageMts
|
| allMts~systemBaseMts
|
| cAuthHssMts~VS.AttAuthRequestsHSSPerHSS
|
.
.
| systemServiceMts~VS.asrtNonESCMinor
|
| systemServiceMts~VS.exceptionService
|
| systemServiceMts~VS.memAllocFail
|
| systemServiceMts~VS.reInitServiceManual
|
| systemServiceMts~VS.reInitServiceSelf
|
| systemServiceMts~VS.restartTask
|
+------------------------------------------------------------------------------
-+

SGSN User Guide
10.9.7 Retrieving XML-format PM data from NECC

Information on the collected PM data can be retrieved via the XML file generated from
PMCollector in NECC.
Purpose
You can use this procedure to verify that SGSN counters are reported as expected.
Procedure
1 Access NECC and navigate to folder cd /data-pm
Wait 15 minutes until the relevant XML file is generated.
2 Open the relevant XML file (check the timestamp) and search for the relevant entry.
Tip:
Each file is generated with the corresponding timestamp.
Tip:
Use a keyword to search the file. To find an appropriate keyword, display the
counter definition (cmm counter definition show).
Example: Verifying counter collection

1. Select one counter from a specific counter group (measurement).
Use command cmm counterGroup definition list to display available groups. For
example, select counter group m001.
2. Select one counter from a counter group.
Use command cmm counterGroup definition show m001 to display counters in
the group m001. For example, select counter m001c000.
3. Display counter details.
Use command cmm counter definition show m001c000 to display counter
m100c100 details. Pick a keyword from the counter data to help you search in the XML
file, for example in the case of counter m100c100, you can use succgprsattach as search
keyword.

SGSN User Guide
4. Execute a mobility management scenario in a test environment.

In the example case, execute a successful 2G attach. This should increase counter
m001c000 SUCC GPRS ATTACH of the GPRS mobility management measurement
(counter group).
5. Access NECC, locate the XML file and look for the counter entry in it.
10.10 CMM support for "measInfoId" field in performance

management reports (Feature f13032-01): feature
summary
This feature provides an additional field in performance management (PM) reports that
operators can use to group sets of PM counters similar to the capability that 3GPP
provides with the MeasInfoId architecture. These PM reports are XML files in /data-pm
in the NECC.
Table 164: CMM support for “measInfoId” field in performance management reports: feature
summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command gParms, parameter measInfoIdUsage

management
Counters None
Alarms None

SGSN User Guide
10.10.1 Adding parameter measInfoId to the PM report

After the global parameter measInfoIdUsage is set to serviceAndCategory, the
category names that are internally associated with each PM counter are added to the PM
XML file.
Procedure
1 Enable adding the measInfoId field as Service and Category in the PM file.
cmm gParms modify –-gParmName measInfoIdUsage –-gParmValue

serviceAndCategory
10.11 MME/SGSN PM data transfer towards ONAP-DCAE

and MME/AMF PCMD data transfer towards CA4MN
This feature adds initial PM data support for the Open Networking Automation Platform
(ONAP), Dublin version. Other functionalities for ONAP are not yet supported. This
feature also provides the capability for Cognitive Analytics for Mobile Networks (CA4MN)
tool to fetch PCMD files from the NECC.

SGSN User Guide
Table 165: MME/SGSN PM data transfer towards ONAP-DCAE and MME/AMF PCMD data
transfer towards CA4MN: feature summary
Function Impact
Compliance 3GPP TS 32.432 for PM le naming

3GPP TS 32.300 for measurement naming
Capacity None
features
Restrictions None
Conguration Command dcaeServer (see Integrating CMM)

management
Counters See the ONAP + Prometheus counter types column in CMM

Counters.
Alarms None
10.12 DPDK-based M3UA (Feature f60110-05): feature

summary
The PAPS selection modifications in the M3UA Load Balancer and the communication
modifications between the M3UA Load Balancer and PAPS improve the performance of
call processing and increase the capacity where more mobility procedures can be
accepted and performed.

SGSN User Guide
Table 166: DPDK-based M3UA (Feature f60110-05): feature summary
Function Impact
Compliance None
Capacity None
Interworking/dependent This feature is dependent on f60210-29 for the Multi-PAPS

features functionality.
Restrictions None
Conguration Command m3uaProfile

management
Alarms 40524 LSS_externalLinkDown
External interfaces Iu-PS

Gr
Gf
Counters GPRS IPDS Interface Measurement (037):

• M037C000 / TOTAL M3UA PACKETS RECEIVED
• M037C001 / TOTAL M3UA PACKETS SENT
IPDS Interface Per Interface Type (137):
• M137C002 / PACKETS SENT USING IPV4 PER INTERFACE TYPE
• M137C003 / KILOBYTES SENT USING IPV4 PER INTERFACE TYPE
• M137C004 / PACKETS RECEIVED USING IPV6 PER INTERFACE TYPE
• M137C005 / KILOBYTES RECEIVED USING IPV6 PER INTERFACE TYPE
• M137C006 / PACKETS SENT USING IPV6 PER INTERFACE TYPE
• M137C007 / KILOBYTES SENT USING IPV6 PER INTERFACE TYPE
10.12.1 Configuring DPDK-based M3UA

To configure DPDK-based M3UA, use the m3uaProfile command.
▪ Configure M3UA profile that is used for the M3UA association.
cmm m3uaProfile create --name SS7Profile
Step example

SGSN User Guide
+---------------------+--------------+
| Field | Value |
+---------------------+--------------+
| m3uaProfile | default |
| name* | default |
| description | |
| rtoMin | 50 |
| rtoMax | 400 |
| rtoInitValid | 300 |
| cookieLife | 60 |
| hbInterval | 30 |
| sackPeriod | 200 |
| sackFreq | 2 |
| mtuSize | 1500 |
| assoMaxRetrans | 10 |
| pathMaxRetrans | 5 |
| maxInitRetrans | 8 |
+---------------------+--------------+
10.13 Enhanced collision handling of attach storm with

pseudo-random TLLI from non 3GPP compliant devices
This feature improves the attach call completion rate of 2G subscribers while attempting
to attach at the same time with the same random TLLI.

SGSN User Guide
Table 167: Enhanced collision handling of attach storm with pseudo-random TLLI from non
3GPP compliant devices: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions During a re-attach storm with multiple UEs using the same random
TLLI, they will be served by the same PAPS which may lead to
temporarily unbalanced PAPS load.
It is also recommended that the feature is enabled before starting of
2G traffic, otherwise, ongoing processes may be impacted.

management pseudoRandomTlliCollisionHandling
Command prFile, parameter randomTlliRemTimer
Counters None
Alarms None
10.13.1 Configuring enhanced collision handling of attach

storm with pseudo-random TLLI from non 3GPP compliant
devices
Use global parameter pseudoRandomTlliCollisionHandling to enable and disable
this feature, and prFile randomTlliRemTimer to set the random format TLLIs stored in
the SGSN
Procedure
1 Enable this feature.
Step example
cmm gParms modify --gParmName pseudoRandomTlliCollisionHandling -
- gParmValue Yes

SGSN User Guide
2 Set the random format TLLIs stored in the SGSN to 5 seconds.
When feature enhanced collision handling of attach storm with pseudo-random TLLI
from non 3GPP compliant devices (f52011-01) is enabled, the value of prFile
randomTlliRemTimer is taken into account. The same subscriber can reattach after
the expiration of the attach accept retries only when this timer is set.
Step example
cmm prFile modify randomTlliRemTimer --status true --
randomTlliRemTimer 5
10.14 CMM support for OAM alignment (Feature

This feature provides OAM alignment across MME, SGSN, and AMF configurations.
Table 168: CMM support for OAM alignment: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Removed commands: logData, logDataStatus, logLiData,

management logLiDataStatus, and healthMon
Output of cmm help is organized by application (common, AMF,
MME, SGSN or any combination)
Commands counter, counterdefinition, and
counterGroupDefintion also display AMF counters
Counters None
Alarms None

SGSN User Guide
10.15 SGSN support for subscription cache - delivery

Previously, the internal cache kept the subscription only for the duration of the
transaction. With this feature, the PAPS subscription cache can maintain the UE
subscription as long as the subscriber is assigned to the specific PAPS.
Table 169: SGSN support for subscription cache - delivery: feature summary
Function Impact
Compliance None
Capacity The subscription cache can support entries for up to 500K subscribers
per PAPS.
The introduction of the subscription cache does not increase the PAPS
RAM requirements for more than 4GB.
The total PAPS RAM requirements are kept up to 24GB.
features
Restrictions None
Conguration Command gParms, parameter enableSgsnSubsCache. By

management default, this feature is disabled.
Counters VS.SubscriptionCacheHitsMax
VS.SubscriptionCacheHitsMean
VS.SubscriptionCacheMissMax
VS.SubscriptionCacheMissMean
Alarms None
10.15.1 Configuring subscription cache

Use global parameter enableSgsnSubsCache to enable the SGSN support for
subscription cache -delivery feature.

SGSN User Guide
Procedure
1 Enable subscription cache feature.
Step example
cmm gParms modify enableSgsnSubsCache --gParmValue Yes
2 Restart the SubHandler process at all PAPS.
Step example
sudo serfclient -t '*paps*' -c 'cmd.run.ssh' --payload 'sudo
systemctl restart fnsSubsHr.service'
Note:
This action should be performed with maintenance window.
10.16 Simplex DBS (Feature f14111-07): feature summary

This feature adds support for SGSN in simplex database service (DBS ) VM configuration.
The existing duplex DBS VM configuration continues to be supported. Simplex DBS
configuration, in conjunction with the Subscription Cache (f50104-02) feature, provides
significant reduction on the hardware resources since the DBS service no longer has to
keep standby VMs for redundancy.

SGSN User Guide
Table 170: Simplex DBS: feature summary
Function Impact
Compliance None
Capacity Capacity remains the same. CMM supports up to 16 DBS VMs in

simplex mode or 16 pairs (32 VMs) in duplex mode.
Required features f50104-02 - SGSN support for Subscription Cache – Delivery

Otherwise, DBS redundancy is severely compromised.
features
Restrictions None
Conguration Apart from deployment conguration, no additional conguration (via

management CLI) is needed.
Counters None
Alarms None
10.17 SNMP interface

Simple Network Management Protocol (SNMP) v3 is supported by the OAM framework to
enable remote management operations.
The SNMP is a standard management protocol for collecting and altering information from
devices. The SNMP works in agent-manager mode. The basic operations in the SNMP are:
GetRequest, SetRequest, GetNextRequest, GetBulkRequest, Response and Trap. SNMPTRAP
is used for asynchronous notification for alarms and events.
The CMM SNMP agent service listens on UDP port 161 and CMM SNMP manager (NSP) listens
on port 162.
Uses of SNMP
The SNMP is used between the application and the EMS (NFM-P) for following purposes:
Node discovery and management in the NFM-P
The NFM-P uses the SNMP to discover a CMM and stores the node properties in its
database. To discover one or more CMM in the network, a discovery rule is created
which contains the unique system IP address or a range of system IP address.

SGSN User Guide
The NFM-P also uses the SNMP for periodic heartbeats to check the availability of the
element.
Alarm get/set operations
The SNMP is used to query the active alarms and alarm history from the application
and cancel the active alarms when the alarm condition subsides. The cancel request
sent via the SNMP removes the alarm from the SNMP alarm table, and cancels the
alarm from the CMM.
The SNMP agent communicates with the MME REST API in the southbound interface to
query alarm data.
Notifications
The asynchronous notifications between the NFM-P and the MME use the SNMP traps.
Asynchronous notifications are sent to receivers registered in the CMM Notification
Forwarding Table (cmmNotificationForwardingTable). Entries in this table are used to
identify the registered SNMP managers to which the SNMP agent sends the
asynchronous notifications. The table can be accessed through the
cmmNotificationForwardingTable SNMP object. When a new alarm is raised, the SNMP
agent sends the alarm to the NFM-P as an SNMP trap.
MIB files
Management Information Base (MIB) files define the managed information base accessible
through the SNMP interface. They are
Nokia-CMM-TC-MIB
Nokia-CMM-MIB
SNMP objects
The values of instantiated objects may be requested by NFM-P/EMS. SNMP objects include:
cmmGeneral
cmmAggregateTable
cmmVNFCTable
cmmAlarmTable
cmmNotificationForwardingTable
notiLogTable
varbindLogTable

SGSN User Guide
Notifications
The following notifications are supported:
cmmAlarmNew
cmmAlarmChanged
cmmAlarmCleared
cmmAlarmListRebuiltNotification
cmmObjectCreateNotification
cmmMOAttrChangeNotification
cmmAgentColdStart
cmmNbiNotification
10.17.1 SNMP architecture

The SNMP agent runs as a service in the NECC VM or ALMS pod.
High availability is provided by the NECC cluster manager, which takes care of starting and
stopping, as well as relocating the service during failover. During failover, the SNMP agent is
started in the new active NECC and recovers configuration data and notification history
records.
In the container environment, the snmpagent runs at the ALMS pod (singleton). Kubernetes
manages this pod, recreating or restarting it as needed.
Figure 2: NECC architecture
10.17.2 SNMP security

SNMPv3 provides security (authentication, privacy, and access control) between the MME

SGSN User Guide
and northbound systems. The CMM SNMP agent supports security levels as defined in
user-based security model (USM), RFC 2574.
The SNMP agent running in the NECC supports the SNMPv3 listed in User security levels.
Table 171: User security levels
Default user Security level Authentication and privacy Authentication Privacy

algorithms password password
cmm_authUs authNoPriv authentication (SHA), no authUser -

er privacy
cmm_privUse authPriv authentication (MD5), privacy authUser privUser

r (DES)
cmm_privUse authPriv authentication (MD5), privacy authUser privUser

r1 (AES128)
<custom non noAuthNoPriv no authentication, no privacy - -

default
name>
10.17.3 Configuring SNMP

Use the emsTrapNotification command to configure the SNMPv3 connection to the
element management system (EMS), the NFM-P.
Procedure
1 Create the SNMP connection to the NFM-P.
cmm emsTrapNotification create
--emsHost <string>
--emsPort <integer>
[--userName <string>]
[--userSecLevel <integer>]
[--contextName <string>]
[--rowStatus <integer>]
[emsTrapNotification]
emsHost The IP address where the EMS listens for notications.

SGSN User Guide
emsPort The UDP port on which the EMS listens for notications.
userName The SNMP user name.
userSecLevel The SNMP user-based security level, a from value 1-3:

• 1- noAuthNoPriv (default)
• 2-authNoPriv
• 3-authPriv
contextName The SNMP context name. This context name is the same name
that is in the VacmAccessTable of VACM MIB RFC2575.
rowStatus The SNMP row status. This value is used to manage the insertion
and deletion of the SNMP conceptual row.
Step example
The following example is for a default SNMP user:
cmm emsTrapNotification create --emsHost 135.2.201.103 --emsPort

162 --userName cmm_privUser --userSecLevel 3 --contextName ' ' --
rowStatus 1
+---------------------+-------------------+
| Field | Value |
+---------------------+-------------------+
| emsTrapNotification | 135.2.201.103~162 |
| emsHost* | 135.2.201.103 |
| emsPort* | 162 |
| emsHostType | 1 |
| userName | cmm_privUser |
| userSecModel | 3 |
| userSecLevel | 3 |
| contextName | |
| rowStatus | 1 |
+---------------------+-------------------+
The following example is for a custom SNMP user:
cmm emsTrapNotification create --emsHost 1.1.1.1 --emsPort 162 -

SGSN User Guide
-userName non_DefaultUser --userSecLevel 1 --contextName

'noAuthNoPriv' --rowStatus 1
+---------------------+-----------------+
| Field | Value |
+---------------------+-----------------+
| emsHost* | 1.1.1.1 |
| emsPort* | 162 |
| emsHostType | 1 |
| userName | non_DefaultUser |
| contextName | noAuthNoPriv |
| rowStatus | 1 |
+---------------------+-----------------+
2 Check the SNMP configuration.
Step example
The following example is for a default SNMP user:
cmm emsTrapNotification show 135.2.201.103~162
+---------------------+-------------------+
| Field | Value |
+---------------------+-------------------+
| emsHost* | 135.2.201.103 |
| emsPort* | 162 |
| emsHostType | 1 |
| userName | cmm_privUser |
| contextName | |
| rowStatus | 1 |
+---------------------+-------------------+
The following example is for a custom SNMP user:
cmm emsTrapNotification show 1.1.1.1~162

SGSN User Guide
+---------------------+-----------------+
| Field | Value |
+---------------------+-----------------+
| emsHost* | 1.1.1.1 |
| emsPort* | 162 |
| emsHostType | 1 |
| userName | non_DefaultUser |
| contextName | noAuthNoPriv |
| rowStatus | 1 |
+---------------------+-----------------+
3 Check SNMP connectivity.
Use the snmpget command to retrieve data from a remote Linux host. The net-snmp
package (containing snmpget utility) must be installed on the remote host. Copy the
Nokia-CMM-MIB.txt and Nokia-CMM-TC-MIB.txt files from the
/usr/share/snmp/mibs directory on the NECC to the same directory on the host.
Execute the command on the remote Linux host:
snmpget -v3 -m +Nokia-CMM-MIB -u cmm_privUser -l authPriv -a MD5

-A authUser -x DES -X privUser <NECC_floating_IP>:161 Nokia-CMM-
MIB::cmmSystemName.0
The response should contain the system name:
Nokia-CMM-MIB::cmmSystemName.0 = STRING: adminnvcns4
Tip:
A simpler way to test SNMP service availability on NECC is to issue a similar

command as above on the NECC, replacing <NECC_floating_IP> with the
value of CLUSTER_IPV4 from the /etc/sysconfig/snmpagent-config file.

SGSN User Guide
10.18 Backup and restore

Perform regular backups to ensure that you have a functional copy in case of network
element problems.
Note:
Backup/restore operations should be executed with the cmm login wherever possible.
The cmm login has a REST authentication token so that execution of cmm
authenticate is not required.
10.18.1 Backing up software

Backup copying is to copy the fallback build and/or other files to a hard disk or other
mass memory device, such as USB.
Purpose
A backup contains the configuration data from MariaDB, Redis, RSP account and LDAP.
Backups are stored to a separate software upgrade volume that is mounted to NECC-0 as
/data-store. Even if the volume is external to the CMM application, it is not replicated, so
backup files should be backed up to some other location.
Procedure
1 Create a backup.
sudo cmm-upgrade backup create
2 Store the backup off-site.
10.18.2 Restoring software

You can restore configuration data (MariaDB, Redis and LDAP data) from the backup files.
Before you start

SGSN User Guide
Note:
Most virtual machines will be restarted during the restore operation and the CMM
operation will be impacted. In addition, the restore procedure will set the
administrative state of the CMM to locked, and the executor of the procedure will
need to manually unlock the CMM after the restore completes. Hence, restores should
be performed during a maintenance window.
LDAP restoration is a merge of the current LDAP data with the LDAP data contained in the
archive. For existing LDAP logins that already exist on the NECC, passwords will be copied
from the backup archive into the existing LDAP data. For data where there is no conflict, the
new logins and groups will be created and passwords restored to what was in the backup
archive.
Procedure
1 List available backups.
sudo cmm-upgrade backup show
2 Force NECC0 to be the active NECC.
Run the following commands to force NECC0 to be the active NECC. This is necessary to
force remotedb to be active on NECC0 (otherwise the MariaDB restore will fail).
sudo pcs cluster standby necc1.local
sudo pcs cluster unstandby necc1.local
3 Restore a backup.
sudo cmm-upgrade backup restore -f <backup name>
4 Unlock the CMM.
After the backup restore command is run, the CMM will be left in the locked
administrative state. To unlock the CMM, run the following commands.
4.1 Verify the administrative state is locked.
cmm aggregateService show
Step result
If the administrative state is locked (it should be), change it to unlocked.

SGSN User Guide
4.2 Change the administrative state to unlocked.
cmm aggregateService modify --adminState unlocked
10.18.3 Backup scheduling (Feature f14509-01): feature

summary
With the Backup scheduling feature, operators can schedule when the system triggers the
backup function automatically, for example, weekly.
Table 172: Backup scheduling: feature summary
Function Impact
Compliance This feature is proprietary.
Capacity None
Interworking/dependent MME support for Data Evolution (f17001-01)

features
Restrictions None
Conguration Command schedule

management
Counters None
Alarms 42007 ScheduledBackupFailure
Backup and restore
10.18.3.1 Configuring scheduled backups

Using the cmm schedule command, you can create, modify, list and delete a backup
schedule.

SGSN User Guide
Before you start
Table 173: Parameters of cmm schedule create and cmm schedule modify
Field Allowed values Allowed special characters
--minute 0 - 59 *,-/
--hour 0 - 23 *,-/
--dayOfMonth 1 - 31 *,-/
--month 1 - 12 *,-/
Jan - Dec
--dayOfWeek 0-6 *,-/

Sun - Sat
--schedJobName backup, rsp, remote-copy,

secure-copy
Usage of the special characters:
Asterisk ( * ) Asterisk means 'every'. For example, --hour '*' means every
hour. When asterisk is used alone without other values, it needs to be
included inside apostrophes, as in the example.
Comma ( , ) Commas are used to separate items of a list. For example, using --
dayOfWeek Mon,Wed,Fri means Mondays, Wednesdays and
Fridays.
Hyphen ( - ) Hyphens dene ranges. For example, --dayOfMonth 10-20

indicates every day of month between 10 and 20, inclusive.
Slash ( / ) Slashes specify step values. For example, --minute 15-45/5

indicates every 5 minutes starting at 15th minute and ending at 45th
minute of an hour, inclusive, and --minute */10 indicates 10
minutes interval.
▪ Create backup schedule.

SGSN User Guide
cmm schedule create
--schedJobName {backup,rsp,remote-copy,secure-copy}
--minute <string>
--hour <string>
--dayOfMonth <string>
--month <string>
--dayOfWeek <string>
All parameters are required to create a backup schedule.
Step example
cmm schedule create --schedJobName backup --minute 30 --hour 12 -
-dayOfMonth '*' --month Jan-Oct –dayOfWeek Sun,Sat
▪ List scheduled backups.
cmm schedule list
▪ Show backup schedule.
Step example
cmm schedule show --schedJobName backup
▪ Modify backup schedule.
Step example
cmm schedule modify --schedJobName backup --dayOfMonth */10 --
minute 0
▪ Delete backup schedule.
NOTICE:
If backup schedule is deleted, remote copy of backup will be not done since no
backup is being done on system.

SGSN User Guide
Step example
cmm schedule delete --schedJobName backup
10.18.4 Remote copy of backup files (Feature f12003-01):

feature summary
With this feature, an operator can schedule a job to automatically copy the backup files
from the CMM to a remote machine. It is recommended to use the remote copy of backup
files feature only when a scheduled CMM backup is in use.
Table 174: Remote copy of backup files: feature summary
Function Impact
Capacity None
Required features Backup scheduling (f14509-01)
Interworking/dependent This feature should not be used if Cloud backup and restore
features improvements via NSP (Feature f14008-01) is in use.
Restrictions None
Conguration Commands schedule and remoteCopySetup

management
Counters None
Alarms 42009 ScheduledRemoteCopyBackupFailure
10.18.4.1 Configuring the operator remote machine

Use the remoteCopySetup command to configure a remote machine for backup files.
Before you start
When an NSP backup operation in progress, data change using the remoteCopySetup
CLI command and NSP is not allowed.

SGSN User Guide
For NSP backup, have the have nsp user password ready before starting this procedure.
Table 175: remoteCopySetup command parameters
Field Allowed values
--remoteIP Valid IPv4 or IPv6 address
--secondaryRemoteIP Valid IPv4 or IPv6 address, optional
Note:
A secondary remote IP address is not

required for NSP backup.
--remoteLogin Standard characters used for a Linux user login
--remoteDir Standard characters used for a Linux Directory
▪ Configure the remote machine.
remoteDir must exist on the remote IP location.
Step example
cmm remoteCopySetup create --remoteId remote-config --remoteIp
135.11.121.130 --secondaryRemoteIP 135.11.121.132 --remoteLogin
cmm --remoteDir /var/remoteDir
▪ Display available configuration.
Step example
cmm remoteCopySetup show remote-config
▪ Modify the remote copy configuration.

SGSN User Guide
Step example
cmm remoteCopySetup modify --remoteId remote-config --remoteIp
<remoteIp> --remoteLogin <remoteLogin> --remoteDir <remoteDir>
▪ Delete the remote copy configuration.
Step example
cmm remoteCopySetup delete --remoteId remote-config
10.18.4.2 Configuring SSH keys between CMM and remote

machine
To support the automatic copy of backup files from the CMM to the remote machine, SSH
keys must be configured. SSH keys only need to be configured once during the lifetime of
the CMM, or at the appropriate time the operator wants to re-create the SSH keys.
Before you start
The CMM local account rsp is used to create the public SSH keys, which are copied to the
remote machine.
For NSP backup, set up the NSP SSH key with the nsp user account.
The login and IP of the remote machine is required to copy the files.
Procedure
1 Log in to the RSP account on NECC0. If the account does not exist, create a local login
on the CMM.
2 Check if the /home/rsp/.ssh/id_rsa.pub file exists. If the file exists, skip the
next step (SSH key generation).
3 Generate the SSH key.
3.1 Log in into the CMM using the root login.
3.2 Execute the SSH key generation command.

SGSN User Guide
/opt/app/sbin/ssh_key_gen -a generate
Note:
If the ssh keys already exist, the -f option is required to overwrite the
existing ssh keys. The tool copies the new ssh keys to every NECC host in
the CMM.
3.3 Exit the root login.
For the next step, use the rsp login.
4 Using the rsp account, copy the SSH public key to the operator remote machine.
The remote login and remote IP address used in the remote copy configuration are
used in Configuring schedule for remote copy of backup.
Step example
cat ~/.ssh/id_rsa.pub | ssh <remoteLogin>@<remoteIP> "cat >>
~/.ssh/authorized_keys"
For NSP backup, use the following command to set up ssh:
cat ~/.ssh/id_rsa.pub | ssh -l nsp <nsp server ip> "cat

>>~/.ssh/authorized_keys; chmod 644 ~/.ssh/authorized_keys"
10.18.4.3 Configuring schedule for remote copy of backup

Use the schedule command to set the schedule for remote copy of backup. The remote
machine and SSH keys must be configured before the schedule for remote copy of
backup feature can be configured.
Before you start
Note:
If NSP backup, check the CMM schedule list. If you have jobs configured for backup,
RSP, and remote copy, they should be removed. For NSP backup, CMM schedule
backup and remote copy are not needed.

SGSN User Guide
Table 176: Parameters of cmm schedule create and cmm schedule modify
Field Allowed values Allowed special characters
--minute 0 - 59 *,-/
--hour 0 - 23 *,-/
--dayOfMonth 1 - 31 *,-/
--month 1 - 12 *,-/
Jan - Dec
--dayOfWeek 0-6 *,-/

Sun - Sat
--schedJobName backup,rsp,remote-copy,secure-copy
Usage of the special characters:
Asterisk ( * ) Asterisk means 'every'. For example, --hour '*' means every
hour. When an asterisk is used alone without other values, it must be
inside apostrophes, as in the example.
Comma ( , ) Commas are used to separate items of a list. For example, using --
dayOfWeek Mon,Wed,Fri means Mondays, Wednesdays, and
Fridays.
Hyphen ( - ) Hyphens dene ranges. For example, --dayOfMonth 10-20

indicates every day of a month between 10 and 20, inclusive.
Slash ( / ) Slashes specify step values. For example, --minute 15-45/5

indicates every 5 minutes starting at the 15th minute and ending at
45th minute of an hour, inclusive, and --minute */10 indicates 10
minutes interval.
Procedure
1 List available configuration.
cmm schedule show –-schedJobName remote-copy
2 Configure the remote copy.
cmm schedule create --schedJobName remote-copy --minute <string>

--hour <string> --dayOfMonth <string> --month <string> --
dayOfWeek <string>

SGSN User Guide
Note:
It is recommended that the schedule used for the remote copy of backup is
aligned with the backup schedule and offset by an hour. For example, if the
backup is scheduled at 2:00 AM every day, the remote copy of backup should be
scheduled at 3:00 AM every day.
10.18.5 CMM support for secure backup and restore of

CMM instance (Feature f14008-02): feature summary
With this feature, an operator can create secure backup files, send them from the CMM to
a remote machine, get them from remote machine to the CMM, and restore them. If a
remote machine is not configured, backup files are only stored locally. Creating and
sending backup files can be scheduled with Backup scheduling (Feature f14509-01).
Table 177: Cloud backup and restore improvements via NSP: feature summary
Function Impact
Capacity None
Interworking/dependent Backup scheduling (feature f14509-01), optional.

features
Restrictions This feature cannot be used if Remote copy of backup files (feature
f12003-01) is in use.
Conguration Commands secureCopySetup and (optionally) schedule.

management
Counters None
Alarms 42016 SecureBackupFailure

SGSN User Guide
10.18.5.1 Configuring secure backup and restore

Use the secureCopySetup command to configure the location of the signed certificate
file for backup encryption, the location of private key file for backup decryption, and,
optionally, a remote machine for secure backup files.
Before you start
Note:
To configure secure backup, the user must:

have access to both the public and private key files and certificates for the keys
used to create the backup archive
be familiar with the configuration of secure backup, as this feature must be fully
configured during the software upgrade
To configure remote backup, the user must:
have the login credentials for the remote backup server

be familiar with the configuration of remote access, as this feature must be fully
configured during the software upgrade
WARNING!
When performing this procedure, ensure that the following keys and certificates are
secured and stored non-locally.
private key (secure backup)
certificate (secure backup)
RSP SSH keys (remote backup)
Failure to preserve the keys and certificate may result in an extended service outage
and complete loss of customer data. If the private-key is lost, CMM backups will be
unreadable and require the CMM to be re-provisioned manually.
Upload a self-signed certificate and private key files to a directory on NECC-0.
The following parameters are used in this procedure.

SGSN User Guide
Note:
Only users in the security group can use the secureCopySetup commands.
Table 178: secureCopySetup command parameters
Field Allowed values
secureId remote-cong
privateKeyFile Standard characters used for a Linux full lename
signedCertFile Standard characters used for a Linux full lename
remoteDir Standard characters used for a Linux full directory name
remoteIp Valid IPv4 or IPv6 address
remoteLogin Standard characters used for a Linux user login
secondaryRemoteIp Valid IPv4 or IPv6 address, optional
▪ Configure the locations for the private key files and self-signed certificate, and,
optionally, the remote machine.
The private key and signed certificate files must already exist on NECC-0 before the
cmm secureCopySetup create command is executed.
Nokia recommends storing the private key and signed certificate files in /data-
store to ensure they are preserved across software updates, healing, and VM image
replacements. If the files are not in /data-store, they will need to be restored
after performing these procedures.
The remoteDir, remoteIp, remoteLogin, and secondaryRemoteIp parameters
are optional. If the remote* parameters are omitted, the CMM does not try to
upload the secure backup file to the remote machine.
Step example
cmm secureCopySetup create --secureId remote-config --privateKeyFile /data-
store/private.key --signedCertFile /data-store/public.crt --remoteDir
/home/admin/backups --remoteIp 10.10.10.5 --remoteLogin admin --secondaryRemoteIp
10.10.10.6

SGSN User Guide
▪ Display the available configuration.
Step example
cmm secureCopySetup show --secureId remote-config
Before performing a procedure that would lead to the loss of any locally-preserved
private keys or certificate files, ensure you also verify the existence of these files in the
file system.
▪ Modify the secure copy configuration.
Step example
cmm secureCopySetup modify --secureId remote-config --privateKeyFile /data-
store/private.key --signedCertFile /data-store/public.crt --remoteDir /backups
▪ Delete the secure copy configuration.
Step example
cmm secureCopySetup delete --secureId remote-config
Related procedures
Configuring SSH keys between CMM and remote machine
Related references
Backup scheduling (Feature f14509-01): feature summary
10.19 Syslog collection and streaming to remote server

With this feature, the CMM supports the sending of message logs from NECCs to a
remote logging server. If configured, the CMM streams syslog data from all NECCs.

SGSN User Guide
Table 179: Syslog collection and streaming to remote server: feature summary
Function Impact
Compliance X.509 certicate
Capacity N/A
Required features N/A
Interworking/dependent N/A
features
Restrictions N/A
Conguration Command syslogAdmin, parameter create, delete, modify,

management list, show
See the Security document.
Counters N/A
Alarms N/A
10.20 CMM support for sending log and alarm information

to stdout in addition to current destinations (Feature
Cloud native applications typically use the infrastructure to forward information to NB
clients. With this feature, the CNF CMM configuration supports sending selected logs and
alarms to stdout in addition to all legacy handling.

SGSN User Guide
Table 180: CMM support for sending log and alarm information to stdout in addition to current
destinations: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None
Conguration Command gParms, parameters enableAlarmEventsStream

management and enableLogEventsStream
Counters None
Alarms None
10.20.1 Configuring the CMM CNF to send logs and alarms

using stdout
Use the gParms enableLogEventsStream and enableAlarmEventsStream to enable
sending logs and alarms to the Fluentd data collector via stdout.
Before you start
Note:
Before configuring the CMM CNF to send logs or alarms to Fluentd, estimate the
number of messages that may be produced and the impact on memory. Default
configurations may need to be adapted.
Procedure
1 Enable logs to be sent to Fluentd.

SGSN User Guide
Step example
cmm gParms modify enableLogEventsStream --gParmValue Yes
+------------+-----------------------+
| Field | Value |
+------------+-----------------------+
| gParms | enableLogEventsStream |
| gParmName* | enableLogEventsStream |
| gParmValue | Yes |
+------------+-----------------------+
2 Enable alarms to be sent to Fluentd.
Step example
cmm gParms modify enableAlarmEventsStream --gParmValue Yes
+------------+-------------------------+
| Field | Value |
+------------+-------------------------+
| gParms | enableAlarmEventsStream |
| gParmName* | enableAlarmEventsStream |
| gParmValue | Yes |
+------------+-------------------------+
3 Configure the external IP address.
The ALMS external IP address uses the same subnet as the OAM and requires a service
IP.

SGSN User Guide
cmm serviceIp create --poolType ALMS --poolId 0 --poolMemberId 0 --subnetLoc
external --assignmentType fixed --niType ALMS_ACCESS --svcIp 10.40.63.166
+-------------------+-----------------------------------+
| Field | Value |
+-------------------+-----------------------------------+
| serviceIp | ALMS~0~0~ALMS_ACCESS~10.40.63.166 |
| poolType* | ALMS |
| poolId* | 0 |
| poolMemberId* | 0 |
| niType* | ALMS_ACCESS |
| svcIp* | 10.40.63.166 |
| subnetLoc | external |
| assignmentType | fixed |
| subnetId | 1 |
| bfdReachableLeft | 0.0.0.0 |
| bfdGatewayLeft | 0.0.0.0 |
| bfdReachableRight | 0.0.0.0 |
| bfdGatewayRight | 0.0.0.0 |
| viaNexthop | 0.0.0.0 |
| viaReachable | 0.0.0.0 |
+-------------------+-----------------------------------+
4 Configure Fluentd per your deployment specifications.
Table Fluentd and stdout configuration fields described the fields used in configuration.

SGSN User Guide
Table 181: Fluentd and stdout configuration fields
Field Type Description
vnf_name string The name of the CNF that

sends the alarms.
vnf_type string The type of CNF.
vnfc_name string The NFC name for the CNF.
vnfc_type string The type of NFC for the CNF.
release string The release of the CNF.
alarm_id number The numeric ID of the alarm

as per the metadata of the
CNF.
alarm_time string The time the alarm was

generated, in ISO 8601
format.
severity string The severity of the alarm:

critical, major, minor,
warning, or clear.
alarm_short_text string Alarm text.
alarm_long_text string Additional alarm text.
event_id number The unique ID of the event.

All alarm events for this
alarm share this ID.
sequence_id number The sequence ID: 1 for raise;

otherwise, 2.
date string The date eld.
Step example
The following sample configuration demonstrates how logs can be handled. Figure
Using Fluentd with Elasticsearch shows this configuration, with EFK acting as the central
point for collecting logs from the Nokia NFs and maintaining an Elasticsearch cluster to
store a small amount of logs.

SGSN User Guide
Figure 3: Using Fluentd with Elasticsearch
<source>
@type tail
path /var/log/containers/*.log
pos_file /var/log/td-agent/cmm.log.pos
tag necclogs.start
<parse>
@type json
time_key time
time_format %iso8601
keep_time_key true
</parse>
</source>
<match necclogs.start>
@type rewrite_tag_filter
<rule>
key log

SGSN User Guide
pattern .+vnf_name.+alarm_id.+
tag necclog.alarm
</rule>
<rule>
key log
pattern .+vnf_name.+log_type.+
tag necclog.log
</rule>
</match>
<filter necclog.**>
@type parser
key_name log
reserve_data false
format json
</filter>
<match necclog.**>
@type copy
<store>
@type elasticsearch_dynamic
hosts 172.31.57.254
port 9201
resurrect_after 5s
type_name fluentd
time_key time
utc_index true
time_key_exclude_timestamp true
logstash_format true
logstash_prefix fluentd-cmmtest-${tag_parts[1]}
<buffer tag, time, namespace, type>
@type file
path /var/log/td-agent/elasticsearch-buffer/cmm_test
flush_mode interval
flush_interval 30s
timekey 3600
retry_forever true
retry_max_interval 5s

SGSN User Guide
overflow_action block
total_limit_size 1024m
</buffer>
</store>
</match>
10.21 CMM support for authentication of NTP server

The network time protocol (NTP) is a networking protocol for clock synchronization
between the computer systems over packet-switched and variable-latency data
networks. The authentication support allows the NTP client to verify that the NTP server
is trusted.
Table 182: CMM support for authentication of NTP server: feature summary
Function Impact
Compliance • RFC 1305

• RFC 8915
Capacity None
features
Restrictions None
Conguration Commands ntpAuthenticate and ntsTlsCAcert

management
Counters None
Alarms None

SGSN User Guide
10.22 SGSN support for internal trace tool enhancement

This feature enables the operators to retrieve the monitoring logs from the PAPS VMs.
Table 183: SGSN support for internal trace tool enhancement: feature summary
Function Impact
Compliance None
Capacity None
features
Restrictions None

management sgsnMonLogSheddingDuringOverload: to control the feature’s
behavior under CPU overload condition in PAPS. Default value: Yes.
Command sudo sgsnmonitorlogctrl: to activate the internal
trace tool.
Counters None
Alarms None
10.22.1 Configuring the internal trace tool

To start the internal trace tool, use the sudo sgsnmonitorlogctrl command.
▪ Start the internal trace tool.
Nokia recommends the user to delete the old files stored at /data-sgsnmon, if not
needed, prior to starting a new internal trace tool collection via the sudo
sgsnmonitorlogctrl command, to get full usage of the volume’s available space.
Step example
sudo sgsnmonitorlogctrl --paps all --profile 3G

SGSN User Guide
Step result
[cmm@espate181b-necc0 data-sgsnmon]$ sudo sgsnmonitorlogctrl --paps all --profile
3G
SGSN monitoring is starting...
Monitoring starting on paps1
Monitoring starting on paps0
▪ Retrieve the .tar file.
Step result
[cmm@espate181b-necc0 ~]$ ls -al /data-sgsnmon/2021-06-24_12-08-24.tar
-rw-r----- 1 root admin 61440 Jun 24 12:10 /data-sgsnmon/2021-06-24_12-08-24.tar
[cmm@espate181b-necc0 ~]$ cd /data-sgsnmon/
[cmm@espate181b-necc0 data-sgsnmon]$ ls -al
total 68
drwxrwxrwx 2 root root 4096 Jun 24 12:10 .
drwxr-xr-x 37 root root 4096 May 21 17:06 ..
-rw-r----- 1 root admin 61440 Jun 24 12:10 2021-06-24_12-08-24.tar
[cmm@espate181b-necc0 data-sgsnmon]$
▪ Bypass the overload mechanism.
Step example
cmm gParms modify --gParmName sgsnMonLogSheddingDuringOverload --
gParmValue No
Step result
+------------+----------------------------------+
| Field | Value |
+------------+----------------------------------+
| gParms | sgsnMonLogSheddingDuringOverload |
| gParmName* | sgsnMonLogSheddingDuringOverload |
| gParmValue | No |
+------------+----------------------------------+

SGSN User Guide
10.22.2 Configuration examples of the internal trace tool

Use the sudo sgsnmonitorlogctrl command to configure the related parameters for
the SGSN internal trace tool.
▪ Start the internal trace tool for 10 minutes in all the available PAPSs.
Step example
sudo sgsnmonitorlogctrl --profile 2G --paps all --time 10
▪ Start the internal trace tool in one PAPS for 2G and 3G profiles.
Step example
sudo sgsnmonitorlogctrl --profile 2G,3G --paps 0
▪ Start the internal trace tool for specific families (PRBs) in all PAPSs.
Step example
sudo sgsnmonitorlogctrl --profile 40A,404,408 --paps all
▪ Start the internal trace tool for a profile in all PAPSs until 1GB file logs are captured.
Step example
sudo sgsnmonitorlogctrl --profile 3G --size 1GB
▪ Start the internal trace tool for a profile in all PAPSs until 100MB file logs are
captured.
Step example
sudo sgsnmonitorlogctrl --profile 3G --size 100MB
▪ Start the internal trace tool for a specific profile and PRB.

SGSN User Guide
Step example
sudo sgsnmonitorlogctrl --profile 3G,7B
▪ Start the internal trace tool for a profile and specific PAPS until the alarm 1007 is
raised.
Step example
sudo sgsnmonitorlogctrl --profile 3G --alarm 1007 --paps 0
▪ Start the internal trace tool for a profile and specific PAPS until message
gtp_identification_res_s is received with cause imsi_not_known_c.
Step example
sudo sgsnmonitorlogctrl --profile 40A,408 --paps 0 --stop_msg
EB98 --stop_msg_offset 76 --stop_msg_values 08000000
▪ Start the internal trace tool and collect specific messages

gtp_create_pdp_context_req_s and gtp_create_pdp_context_res_s for specific PRBs.
Step example
sudo sgsnmonitorlogctrl --profile 40A,404,409,408 --paps all --
msg EBB0,EBAD
10.22.3 Opening and parsing the generated files of the

internal trace tool
Follow the steps to open and parse the generated files when the internal trace log
collection is completed.
Procedure
1 Install the 7Z ZS at Windows.
Install the 7Z ZS at Windows through the

https://github.com/mcmilk/7-Zip-zstd/releases/tag/19.00-v1.4.9-R2.

SGSN User Guide
2 Install the 64bit version of the Emil tool.
3 Retrieve the latest beta version of the Emil tool.
Retrieve the latest beta version through the Help menu / Check for Emil
updates. The latest version is: 3.64.212.21929.
4 Download the .tar file locally.
The files are separated per PAPS as shown in the Figure sgsnmon folder.
Figure 4: sgsnmon folder
5 Upzip the .tar file by selecting 7-zip ZS.
The generated files are in bin format and compressed using the fast compression
algorithm ZStandard.
Figure 5: 7-Zip ZS
Step result
After extracting the ZSTD file, the BIN file is created.
Figure 6: BIN file creation

SGSN User Guide
6 Drag and drop the BIN file to Emilx64.
Note:
Emilx32 is still possible to be used but conversion from BIN to ASCII format is
required.
10.23 SGSN support for deciphered Gb signaling for call

trace (Feature f52078-01): feature summary
This feature enhances the subscriber call trace functionality in case of 2G ciphering. SGSN
decrypts and displays the ciphered Gb signaling messages at call trace as properly
deciphered and readable Gb packets.
Table 184: SGSN support for deciphered Gb signaling for call trace: feature summary
Function Impact
Compliance None
Capacity None
Required features 2G ciphering GEA 1/2/3 (Features SG01009, SG01034, SG01175

and f60210-19)
Interworking/dependent SGSN support for call trace (Features f60210-13 and f52071-01)
features
Restrictions None
Conguration Command securityParam, parameter cipheringMode

management Command plmnParam, parameter cipherMode
Counters None
Alarms None

SGSN User Guide
10.23.1 Configuring SGSN support for deciphered Gb

signaling for call trace
Use cipheringMode parameter in securityParam command, and cipherMode
parameter in plmnParam command to configure the deciphered Gb signaling for the call
trace in the SGSN.
Procedure
1 Enable ciphering mode.
Step example
cmm securityParam modify config --cipheringMode true
2 Configure PLMN level ciphering mode.
Step example
cmm plmnParam modify <PLMN> --cipherMode true
The uplink messages are captured by the GIP after decryption and they are sent to the
GTE in order to be reported in call trace.
The downlink messages are captured by the GGB before encryption and they are sent to
the GTE in order to be reported in call trace.

SGSN User Guide

Uploaded by

SGSN User Guide

Uploaded by

Cloud Mobility Manager, Release

21.8, Operating Documentation, v.

SGSN User Guide

© 2021 Nokia. Nokia Condential Information

Use subject to agreed restrictions on disclosure and use.

No part of this document may be modied.

Copyright and trademark: Nokia is a registered trademark of Nokia Corporation. Other

2 © 2021 Nokia. Nokia confidential 10-0

Summary of changes .................................................................................................................. 21

1 SGSN User Guide ......................................................................................................................... 24

2 Mobility and session management .......................................................................................... 25

10-0 © 2021 Nokia. Nokia confidential 3

4 © 2021 Nokia. Nokia confidential 10-0

3 Radio and core network access support ............................................................................... 103

4 End user management ............................................................................................................ 135

10-0 © 2021 Nokia. Nokia confidential 5

5 Gateway selection and APN control ....................................................................................... 159

6 © 2021 Nokia. Nokia confidential 10-0

6 Pooling and network sharing features .................................................................................. 206

10-0 © 2021 Nokia. Nokia confidential 7

7 Operational control and optimization ................................................................................... 245

8 © 2021 Nokia. Nokia confidential 10-0

7.1.1.4 Configuring tariff functionality ............................................................ 266

10-0 © 2021 Nokia. Nokia confidential 9

8 S4-SGSN .................................................................................................................................... 354

9 Interface/Link management ................................................................................................... 371

10 Operability .............................................................................................................................. 372

10 © 2021 Nokia. Nokia confidential 10-0

10.2.3 Working with PCAP output files (SGSN) ........................................................ 385

10-0 © 2021 Nokia. Nokia confidential 11

10.17 SNMP interface ......................................................................................................... 451

12 © 2021 Nokia. Nokia confidential 10-0

10-0 © 2021 Nokia. Nokia confidential 13

14 © 2021 Nokia. Nokia confidential 10-0

Table 32 IP multimedia support (Feature SG01043): feature summary ............................. 77

10-0 © 2021 Nokia. Nokia confidential 15

16 © 2021 Nokia. Nokia confidential 10-0

summary ....................................................................................................................... 194

10-0 © 2021 Nokia. Nokia confidential 17

18 © 2021 Nokia. Nokia confidential 10-0

10-0 © 2021 Nokia. Nokia confidential 19

Table 171 User security levels ................................................................................................. 454

20 © 2021 Nokia. Nokia confidential 10-0

Changes between issues 9-0 (CMM21.5) and 10-0 (CMM21.8)

New and updated features in CMM21.8

10-0 © 2021 Nokia. Nokia confidential 21

Changes between issues 8-2 (CMM21 M2) and 9-0 (CMM21.5)

New and updated features in CMM21.5

Changes between issues 8-1 (CMM21) and 8-2 (CMM21 M2)

New and updated features in CMM21 M2

22 © 2021 Nokia. Nokia confidential 10-0

CMM support for “measInfoId” field in performance management reports (Feature

10-0 © 2021 Nokia. Nokia confidential 23

1. SGSN User Guide

For the initial setup of the network element, see:

System architecture is described in Product Description and features in SGSN Feature

24 © 2021 Nokia. Nokia confidential 10-0

2. Mobility and session management

2.1 GPRS mobility management (Features SG01011,

Mobility management Gb mode states:

Mobility management Iu mode states:

Mobility management procedures:

10-0 © 2021 Nokia. Nokia confidential 25

2.1.1 GPRS mobility management (Features SG01011,

Table 1: GPRS mobility management (Features SG01011, SG01104, SG01184, SG01149,

Required features None

26 © 2021 Nokia. Nokia confidential 10-0

Interworking/dependent • Packet data transfer

Conguration Command securityParam, parameters

Counters Counters that are updated in terms of mobility management belong

Alarms 0126 PDP OVER DEFINED LIMIT

Feature ID SG01011, SG01104, SG01184, SG01149, SG01254, and SG01070

10-0 © 2021 Nokia. Nokia confidential 27

2.1.2 IMEI transfer in SGSN change (Feature SG01184):

Table 2: IMEI transfer in SGSN change (Feature SG01184): feature summary

Compliance 3GPP TS 29.060 Rel. 5