3bl95517abaapczza 01 en PDF

Alcatel-Lucent
8650 Subscriber
Data Manager
SDM SUPPLEMENTARY SERVICES
MANAGEMENT
3BL 95517 ABAA PCZZA Ed.01

OPERATOR GUIDE
Status RELEASED 24/09/2008
Mnemonic SDMSSOPG
All rights reserved. Passing on and copying of this document, use and
communication of its contents not permitted without written authorization
from Alcatel-Lucent.
2 / 204 3BL 95517 ABAA PCZZA Ed.01

Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1 Introduction to supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
1.1 Telecommunication services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.2 Basic services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
1.3 Supplementary services in a GSM or UMTS network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
1.3.1 Supplementary service type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.2 Unstructured Supplementary Service Data (USSD) . . . . . . . . . . . . . . . . . . . . . . . . . 19
1.3.3 Supplementary service groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2 Description of supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.1 Call forwarding services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.1.1 Call Forwarding Unconditional (CFU) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
2.1.2 Call Forwarding on No Reply from mobile subscriber (CFNREPLY) . . . . . . . . . . . 30
2.1.3 Call Forwarding on mobile subscriber Not Reachable (CFNREACH) . . . . . . . . . . 32
2.1.4 Call Forwarding on Busy mobile subscriber (CFBUSY) . . . . . . . . . . . . . . . . . . . . . . 35
2.1.5 Default Call Forwarding (CFD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
2.2 Call barring services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2.2.1 Barring of outgoing calls (BAOC, BOIC, BOIC-exHC) . . . . . . . . . . . . . . . . . . . . . . 39
2.2.2 Barring of all incoming calls (BAIC, BIC-Roam) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
2.3 Call identification services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
2.3.1 COnnected Line identification Presentation (COLP) . . . . . . . . . . . . . . . . . . . . . . . . 44
2.3.2 COnnected Line identification Restriction (COLR) . . . . . . . . . . . . . . . . . . . . . . . . . . 47
2.3.3 Calling Line Identification Presentation (CLIP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
2.3.4 Calling Line Identification Restriction (CLIR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
2.3.5 Malicious Call Identification (MCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
2.3.6 Calling Name Presentation (CNAP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
2.4 Call completion services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.4.1 Call Hold (HOLD) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
2.4.2 Call Waiting (CW) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
2.4.3 Explicit Call Transfer (ECT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
2.5 Group services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.5.1 MultiParTY (MPTY) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
2.5.2 Closed User Group (CUG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
2.6 Charging services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.6.1 Advice Of Charge-Information (AOCI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.6.2 Advice Of Charge-Charging (AOCC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
2.7 Priority call services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
2.7.1 enhanced Multi-Level Precedence and Pre-emption (eMLPP) . . . . . . . . . . . . . . . . . 72
2.8 Operator services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
2.8.1 Operator Specific Supplementary Service (OSSS) . . . . . . . . . . . . . . . . . . . . . . . . . . 74
3 Supplementary Services management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
3.1 Supplementary Services management overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
3.1.1 Tools used to manage Supplementary Services in the 8650 SDM . . . . . . . . . . . . . 76
3.1.2 Documentation to use to manage supplementary services . . . . . . . . . . . . . . . . . . 76
3.1.3 Supplementary Services management operations and subdomains . . . . . . . . . . . 76
3.2 Call Barring parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
3.3 Call Forwarding parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
3.4 GCS parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
3.5 CUG parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
3.6 eMLPP parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4 Call Barring key procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
4.1 Provisioning call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
4.2 Deleting call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
3BL 95517 ABAA PCZZA Ed.01 3 / 204

Contents
4.3 Copying call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

4.4 Displaying call barring information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
4.5 Listing call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
4.6 Modifying call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
5 Call Forwarding key procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
5.1 Provisioning call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
5.2 Deleting call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
5.3 Copying call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
5.4 Displaying call forwarding information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
5.5 Listing call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
5.6 Modifying call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
6 GCS key procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
6.1 Provisioning GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
6.2 Deleting GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
6.3 Copying GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
6.4 Displaying GCS information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
6.5 Listing GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
6.6 Modifying GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
7 CUG key procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
7.1 Provisioning CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
7.2 Deleting CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
7.3 Copying CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
7.4 Displaying CUG information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
7.5 Listing CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151
7.6 Modifying CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
8 eMLPP key procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159
8.1 Provisioning eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
8.2 Deleting eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
8.3 Copying eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164
8.4 Displaying eMLPP information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165
8.5 Listing eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167
8.6 Modifying eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
9 Interactions between supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
9.1 Supplementary services and BSG applicability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
9.2 Interactions between system functions and supplementary services . . . . . . . . . . . . . . . . . . . . . 174
9.2.1 ODB and supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
9.2.2 HB and CFU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176
9.3 Interactions between supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
9.3.1 Interactions between call forwarding services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
9.3.2 Interactions between call barring services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
9.3.3 Interactions between call forwarding and call barring services . . . . . . . . . . . . . . 178
9.3.4 Interactions between COLP and other supplementary services . . . . . . . . . . . . . . 181
9.3.5 Interactions between CLIP and other supplementary services . . . . . . . . . . . . . . . 182
9.3.6 Interactions between CLIR and other supplementary services . . . . . . . . . . . . . . . 182
9.3.7 Interactions between HOLD and other supplementary services . . . . . . . . . . . . . . 183
9.3.8 Interactions between CW and other supplementary services . . . . . . . . . . . . . . . . 183
9.3.9 Interactions between ECT and other supplementary services . . . . . . . . . . . . . . . . 184
9.3.10 Interactions between MPTY and other supplementary services . . . . . . . . . . . . . . 185
9.3.11 Interactions between CNAP and other supplementary services . . . . . . . . . . . . . . 185
9.3.12 Interactions between CUG and other supplementary services . . . . . . . . . . . . . . . 186
9.3.13 Interactions between AOCC and AOCI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
9.4 Interactions with IN services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
9.4.1 Interactions between IN services and call forwarding services . . . . . . . . . . . . . . . 189
9.4.2 Interactions between IN services and call barring services . . . . . . . . . . . . . . . . . . 189
9.4.3 Interaction between IN services and CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
4 / 204 3BL 95517 ABAA PCZZA Ed.01

Contents
9.5 Interactions with CAMEL services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

9.5.1 Interactions between CAMEL and call forwarding services . . . . . . . . . . . . . . . . . 190
9.5.2 Interactions between CAMEL and call barring services . . . . . . . . . . . . . . . . . . . . . 190
9.5.3 Interaction between CAMEL and CLIP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
9.5.4 Interaction between CAMEL and CLIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
9.5.5 Interactions between CAMEL phase 2 service and ECT . . . . . . . . . . . . . . . . . . . . 190
9.5.6 Interactions between CAMEL phase 2 service and MPTY . . . . . . . . . . . . . . . . . . . 190
9.5.7 Interactions between CAMEL and AOC services . . . . . . . . . . . . . . . . . . . . . . . . . . 190
9.5.8 Interactions between CAMEL and the CUG service . . . . . . . . . . . . . . . . . . . . . . . . 191
Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193
Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
3BL 95517 ABAA PCZZA Ed.01 5 / 204

Figures
Figures
Figure 1: Basic subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Figure 2: GSM/UMTS network architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Figure 3: Supplementary services data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Figure 4: Call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Figure 5: Registering an unconditional FTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Figure 6: Registering a conditional FTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Figure 7: CFU service for an HPLMN subscriber . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 8: CFNREPLY service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 9: CFNREACH service (call forwarding by the GMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 10: CFNREACH service (call forwarding by the VMSC) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 11: CFBUSY service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Figure 12: CFD service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Figure 13: BAOC service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Figure 14: BAIC service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Figure 15: COLP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Figure 16: COLR service between two mobile subscribers in the same network . . . . . . . . . . . . . . . . . . . . . . . . . 48
Figure 17: CLIP service CLI transmitted via ISUP signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Figure 18: CLIP service CLI transmitted via MAP message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Figure 19: CLIR service between two mobile subscribers in the same network . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Figure 20: MCI service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Figure 21: CNAP service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Figure 22: HOLD service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
Figure 23: CW service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Figure 24: ECT service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
Figure 25: MPTY service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Figure 26: Conference call basic operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Figure 27: An originating call request: successful CUG authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
Figure 28: An originating call request: unsuccessful CUG authorization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
6 / 204 3BL 95517 ABAA PCZZA Ed.01

Tables
Tables
Table 1: Basic services (BS/TS) offered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 2: Supplementary services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Table 3: Operating restrictions if outgoing call barring not supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Table 4: Called subscriber identification according to data received by VMSC . . . . . . . . . . . . . . . . . . . . . . . . . 46
Table 5: Calling subscriber identification according to data received by VMSC . . . . . . . . . . . . . . . . . . . . . . . . . 52
Table 6: Calling line identification according to CLIR service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Table 7: Applicability of supplementary services to BSGs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Table 8: Quiescent rules between ODB and CF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175
Table 9: Call forwarding service activation compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177
Table 10: Activation of call forwarding services according to call barring services activated . . . . . . . . . . . . . 178
Table 11: Activation of call barring according to call forwarding service activated . . . . . . . . . . . . . . . . . . . . . 179
3BL 95517 ABAA PCZZA Ed.01 7 / 204

Tables
8 / 204 3BL 95517 ABAA PCZZA Ed.01

Preface
Preface
Purpose This operator guide explains how to manage Supplementary Services from the
Alcatel-Lucent 8650 Subscriber Data Manager (SDM). The information presented
in this document applies to both Global System for Mobile communications (GSM)
and Universal Mobile Telecommunications System (UMTS) networks.
Information presented in this document applies to Alcatel-Lucent 8650 SDM re-
leases beginning with R1.1.
Audience This guide is for operators in charge of managing Supplementary Services from
the 8650 SDM Graphical User Interface (GUI) and from the Interface Description
Language (IDL) Common Object Request Broker Architecture (CORBA) using the
CCBS application or the Mass management.
Contents Chapter1 gives a general description of Supplementary Services

(SSs) and key concepts.
Chapter2 defines and describes the supplementary services.
Chapter3 describes the procedures that you perform to open
and manage supplementary services. It provides also
a short functional description of each parameter re-
quired for Supplementary Services management.
Chapter 4 describes management procedures for call barring.
Chapter 5 describes management procedures for call forward-
ing.
Chapter 6 describes management procedures for GCS.
Chapter 7 describes management procedures for CUG.
Chapter 8 describes management procedures for eMLPP.
Chapter 9 describes the conditions governing the use of supple-
mentary services.
Abbreviations gives the extended form of all the abbreviations used
in this guide.
Index lists the main topics and locates them in this guide.
Related documents Documents related to this guide include:
3BL 95517 ABAA PCZZA Ed.01 9 / 204

Preface
Alcatel-Lucent 8650 SDM, CORBA Interface Description for SDM Provisioning

Management Programmer guide, SDMCORPRG,
Alcatel-Lucent 8650 SDM, SDM Mass Management Operator guide, SDMMA-
SOPG.
Alcatel-Lucent 8650 SDM, SDM Subscription Management Operator guide,
SDMSUBOPG.
Typographical conventions This guide uses the following typographical conventions:

text in italics: document titles,
text in bold: important information,
text in courier: text typed by an operator and messages displayed by the
system,
text in bol d i tal i cs : dialog box buttons and fields, keyboard keys, menus,
menu options, tab names, parameters,
text in [ bo ld i tali cs i n square brack ets] : window titles and dialog
box names,
the symbol indicates an example,
Information links indicate relevant information links related to the preceding
section or sub-section.
Terminological conventions The following terminological conventions are used in this document:
The terminology used is that specified by the International Telecommunica-
tion Union Telecommunication standardization sector (ITU-T) and European
Telecommunications Standards Institute (ETSI) standards.
This document uses abbreviations developed from the English extended form
when available. Certain abbreviations may be French-based when no English
extended form exists.
This guide applies standard Global System for Mobile communications (GSM)
and Universal Mobile Telecommunications System (UMTS) terminology.
This guide uses:

CS (Circuit-Switched) to indicate the circuit domain in Alcatel-Lucent GSM and
UMTS networks.
PS (Packet-Switched) to indicate the packet domain in Alcatel-Lucent GSM and
UMTS networks.
UE (User Equipment) to indicate the subscriber terminal whether the subscriber
is in a GSM or UMTS network.
The guide also uses the following terminological conventions:

For the call forwarding services:
subscriber A is the calling subscriber,
subscriber B is the subscriber with the call forwarding service,
subscriber C is the subscriber receiving the forwarded calls.
For all other supplementary services:

subscriber A is the calling subscriber,
subscriber B is the called subscriber.
10 / 204 3BL 95517 ABAA PCZZA Ed.01

Preface
Alcatel-Lucent acknowledges the following trademark for company names or

products mentioned within Alcatel-Lucent documents:
CORBA is a registered trademark of Object Management group.
3BL 95517 ABAA PCZZA Ed.01 11 / 204

Preface
12 / 204 3BL 95517 ABAA PCZZA Ed.01

1 Introduction to supplementary services
This chapter provides a general description of Supplementary Services (SSs) and

key concepts. The chapter describes:
basic services and a basic service subscription,
supplementary services and supplementary service types.
3BL 95517 ABAA PCZZA Ed.01 13 / 204

1.1 Telecommunication services

Telecommunication services are the communication capabilities made available
to subscribers by network operators. GSM/UMTS standards divide telecommuni-
cation services into two categories:
basic services, see section 1.2
supplementary services, see section 1.3.
Note: For more detailed information about basic, CS and PS subscription manage-
ment, see the Alcatel-Lucent 8650 SDM, SDM Subscription Management Operator
guide, SDMSUBOPG.
1.2 Basic services

Basic services are telecommunication services that enable subscribers to commu-
nicate over a network. GSM/UMTS standards divide telecommunication services
into two broad categories:
Bearer Services (BS),
Bearer Services provide the capacity to transmit signals between two or more
access points.
TeleServices (TS),
TeleServices provide complete connection capabilities, including terminal
equipment functions, for communications between two or more users.
Basic services are divided into Basic Service Groups (BSGs). Table 1 lists the basic
services.
Note: In GSM specifications, Basic Service Groups (BSGs) are identified as BS2x and
BS3x. In the Alcatel-Lucent solution, BSGs are identified as BS20 and BS30.
In UMTS specifications, General Bearer Services (GBSs) are identified as BS20 and
BS30. In the Alcatel-Lucent solution, GBSs are identified as GBS20 and GBS30.
14 / 204 3BL 95517 ABAA PCZZA Ed.01

Table 1: Basic services (BS/TS) offered
BSG Basic service Definition Network applicability

(Basic
GSM UMTS
Service
Groups in
GSM and/or
UMTS)
BSG20 BS21, BS22, Asynchronous duplex circuit data ser-

BS24, BS25, vices
BS26
GBS 20 Asynchronous duplex circuit data ser-

vices
BSG30 BS31, BS32, Synchronous duplex circuit data services

BS33, BS34
GBS 30 Synchronous duplex circuit data services
Speech TS11 Telephony
TS12 Emergency call
SMS TS21 Short Message Service-Mobile Termi-

nated/Point-to-Point (SMS-MT/PP)
TS22 Short Message Service-Mobile Origi-

nated/Point-to-Point (SMS-MO/PP)
Fax TS61 Alternate speech and facsimile group 3
TS62 Automatic facsimile group 3
3BL 95517 ABAA PCZZA Ed.01 15 / 204

Each subscriber has a basic subscription (see Figure 1). You attribute basic services
to a subscriber when creating a subscription for that subscriber. The HLR/AuC of
the Home PLMN (HPLMN) stores subscription data, then transmits this information
to the Visitor Location Registers (VLRs) in areas visited by the subscriber. Areas
visited by the subscriber must be authorized areas, that is, HPLMNs or cooperating
Public Land Mobile Networks (PLMNs).
Figure 1: Basic subscription
A basic subscription includes the following subscriber data:

identity,
mainMSISDN with BS,
MSISDN with BS,
Network Access Mode (NAM),
BS without SN,
ServiceMode-Notification.
16 / 204 3BL 95517 ABAA PCZZA Ed.01

1.3 Supplementary services in a GSM or UMTS network

A supplementary service is a telecommunication service that modifies or enhances
a basic service. For a list of the basic services, see Table 1.
A network operator offers a supplementary service to a customer in association
with a basic service. Supplementary services are not offered on a standalone
basis. A supplementary service affects one or more Basic Service Groups (BSGs).
For a list of BSGs, see Table 1.
A network operator can offer certain supplementary services to subscribers on a
general basis (without a subscription), or on request (on a subscription basis).
A subscriber can access a supplementary service on demand. Subscribers can
control the use of certain supplementary services with a password.
With the Alcatel-Lucent Circuit-Switched Core Network (CSCN), you can offer sup-
plementary services to mobile subscribers in a GSM or UMTS network. Figure 2
describes the architecture of a mobile network supporting both GSM and UMTS
services. Under the 3GPP UMTS Release 3 standards, the management of sup-
plementary services is the same whether you provide these services to mobile
subscribers in a GSM or UMTS network.
Figure 2: GSM/UMTS network architecture
3BL 95517 ABAA PCZZA Ed.01 17 / 204

Supplementary services data for a subscriber is stored in the HLR/AuC of their

HPLMN. On User Equipment (UE) location updates, the HLR/AuC sends the data
to the VLR where the UE for the subscriber is currently attached (see Figure 3).
Figure 3: Supplementary services data
The HLR/AuC of the 8650 SDM:

stores the supplementary services assigned to its PLMN subscribers,
manages subscriber data about the supplementary services (for example, For-
warded-To Number (FTN), activation state, etc.),
checks the compatibility of the supplementary services requested by a sub-
scriber,
sends, to the VLR, data required to provide supplementary services to a visiting
subscriber.
The VLR:
stores, temporarily, data about subscribers passing in the coverage area of
the Visited Mobile services Switching Center (VMSC),
supplies the VMSC with subscriber data, such as an FTN, in order to provide
supplementary services to a visiting subscriber,
checks the rights of the subscriber to the supplementary services requested.
Supplementary services Activation of a functional option enables you to inhibit or offer supplementary ser-
offered to foreign vices to certain foreign subscribers roaming in their network. You can inhibit or
subscribers offer supplementary services to foreign subscribers based on the HPLMN of the
subscriber. You can offer the following supplementary services to foreign sub-
scribers:
MultiParTY (MPTY),
COnnected Line identification Presentation (COLP),
COnnected Line identification presentation Restriction (COLR).
18 / 204 3BL 95517 ABAA PCZZA Ed.01

1.3.1 Supplementary service type

Supplementary services can be one of two service types:
standardized service, defined by a GSM or UMTS standard.
A standardized supplementary service is available to subscribers regardless
of where they are located (that is, whether they are in their HPLMN or in a
cooperating PLMN).
or
proprietary service, defined by a network operator.
A proprietary supplementary service is available to subscribers only when they
are located in their HPLMN.
1.3.2 Unstructured Supplementary Service Data (USSD)

Subscribers can use Unstructured Supplementary Service Data (USSD) to access
or modify their supplementary services if they do not have a UE that enables them
to have direct access to supplementary services. Subscribers can also use USSD to
access operations that are not standardized or to initiate USSD messages between
the HLR/AuC in the 8650 SDM and the Service Control Point (SCP).
Subscribers use USSD procedures to transmit instructions or information over a
GSM network. USSD mechanisms allow an interchange of character strings in
a message between a UE and the SCP. Subscribers can enter USSD commands
directly from their UE.
Note: You can inhibit the USSD function for foreign roaming subscribers belonging to
any Foreign PLMN (FPLMN) or belonging to a list of prohibited FPLMNs.
1.3.3 Supplementary service groups

This guide divides supplementary services into the following groups:
Call Forwarding services,
Call Barring services,
General Call Services (GCS) which includes:
call identification services,
call completion services,
group services,
charging services,
priority call services,
operator services.
Table 2 lists the supplementary services that you can offer to mobile subscribers
in a GSM or UMTS network.
3BL 95517 ABAA PCZZA Ed.01 19 / 204

Table 2: Supplementary services
Supplementary Service GSM/UMTS Acronym Service Type
Call Forwarding Services
Call Forwarding Unconditional CFU standardized
Call Forwarding on No Reply from mobile sub- CFNREPLY standardized

scriber
Call Forwarding on mobile subscriber Not Reach- CFNREACH standardized

able
Call Forwarding on Busy mobile subscriber CFBUSY standardized
Default Call Forwarding CFD proprietary
Pre-Call Deflection PCD proprietary
Call Barring Services
Barring of All Outgoing Calls (except to emergency BAOC standardized

numbers)
Barring of Outgoing International Calls BOIC standardized
Barring of Outgoing International calls except those BOIC-exHC standardized

directed to the HPLMN country
Barring of All Incoming Calls BAIC standardized
Barring of all Incoming Calls when Roaming outside BIC-Roam standardized

the HPLMN country
Call Identification Services
COnnected Line identification Presentation COLP standardized
COnnected Line identification Restriction COLR standardized
Calling Line Identification Presentation CLIP standardized
Calling Line Identification Restriction CLIR standardized
Malicious Call Identification MCI proprietary
Calling Name Presentation CNAP standardized
Call Completion Services
call HOLD HOLD standardized
Call Waiting CW standardized
Explicit Call Transfer ECT standardized
Group Services
20 / 204 3BL 95517 ABAA PCZZA Ed.01

Supplementary Service GSM/UMTS Acronym Service Type
MultiParTY conference call MPTY standardized
Closed User Group CUG standardized
Charging Services
Advice Of Charge-Information AOCI standardized
Advice of Charge-Charging AOCC standardized
Priority Call Services
enhanced Multi-Level Precedence and Pre-emption EMLPP standardized
Operator Services
Operator Specific Supplementary Services OSSS proprietary
3BL 95517 ABAA PCZZA Ed.01 21 / 204

22 / 204 3BL 95517 ABAA PCZZA Ed.01

2 Description of supplementary services
This chapter defines and describes the following supplementary services:

call forwarding services,
call barring services,
call identification services,
call completion services,
group services,
charging services,
priority call services,
operator services.
3BL 95517 ABAA PCZZA Ed.01 23 / 204

2.1 Call forwarding services

Call Forwarding services enable mobile subscribers to re-route incoming calls to
a predetermined number (see Figure 4). The following call forwarding services
are supported in a GSM or UMTS network:
Call Forwarding Unconditional (CFU),
Call Forwarding Conditional (CFC):
Call Forwarding on No Reply from mobile subscriber (CFNREPLY),
Call Forwarding on mobile subscriber Not Reachable (CFNREACH),
Call Forwarding on Busy mobile subscriber (CFBUSY),
default call forwarding (CFD).
Call forwarding is applicable to all basic services except the emergency call (TS12)
and Short Message Service (SMS).
Note: You need to subscribe to BSGs to be able to set these BSGs for the call forwarding.
A mobile subscriber can forward calls to:
another UE in the HPLMN,
a UE of a cooperating PLMN,
a fixed number in the PSTN/ISDN.
Figure 4: Call forwarding
After you have provisioned a call forwarding service, call forwarding is activated
and the FTN is registered either by the subscriber or by you depending on the
PLMN options.
The 8650 SDM can inhibit call forwarding for roaming HPLMN subscribers in all
FPLMNs or in designated FPLMNs. Depending on particular functional options
set in the network, the HLR/AuC in the 8650 SDM does not transmit the FTNs to
the VLR registered for:
the CFD service, or
the CFC or CFD service for call forwarding towards a voice mail box, or,
all CFC services.
Subscriber-controlled Call Forwarding (CF) enables the subscriber to activate or

deactivate a call forwarding service, and register or erase an FTN.
Operator-determined call forwarding (CFOP) enables you to reroute uncompleted
calls to another number (for example, to a voice messaging service) for subscribers
who do not subscribe to any of the subscriber-controlled call forwarding services.
24 / 204 3BL 95517 ABAA PCZZA Ed.01

You can activate or deactivate the CFOP service, or register or erase the associated
FTNs. The subscriber can modify this data but needs to obtain authorization from
you.
Call forwarding is activated:
by the subscriber or you for both CFU and CFC,
only by you for CFD,
only by the subscriber for PCD.
Forwarded-To Number An FTN is the number that a call is being re-routed to. FTNs are stored in the
(FTNs) HLR/AuC of the 8650 SDM. You or the subscriber can register an FTN.
For CFU, you or the subscriber can register FTNs (see Figure 5):
individually for each Basic Service Group (BSG),
for all applicable Bearer Services (BS),
for all applicable TeleServices (TS),
for a set of BSGs (Mobile Application Part (MAP) phase 2 and later versions
only).
Figure 5: Registering an unconditional FTN
3BL 95517 ABAA PCZZA Ed.01 25 / 204

For CFC, you or the subscriber can register FTNs (see Figure 6):
collectively for the three conditional call forwarding conditions,
individually for each conditional call forwarding condition.
Figure 6: Registering a conditional FTN
To select a terminal in the installation of the subscriber (MAP phase 2 and later
versions), you can include a forwarding subaddress in the FTN.
Short FTNs Frequently used FTNs may be available in an abbreviated format known as short
FTNs. These numbers apply mainly to voice messaging services which subscribers
often use for call forwarding.
Number barred to call You can prevent UEs located in the HPLMN from forwarding calls to certain num-
forwarding bers (for example, forwarding calls to emergency services).
Barring is implemented by the translation function in the 8650 SDM, for the sub-
scribers of the HPLMN, when registering the FTNs.
Destination profile By default, the subscriber is entitled to forward calls to all destinations, however,
you can limit FTNs to certain destinations. Destination profiles correspond to num-
bers that are allowed to have calls forwarded to them. You can define up to 16
destination profiles. You can assign a destination profile to a subscriber who has
a call forwarding service.
Announcements Depending on a functional option, and provided the called subscriber (B) has
subscribed to notification to calling party, a tone or recorded announcement is
broadcast to the calling subscriber (A) to indicate that the called subscriber will
forward the call. If the calling subscriber wants the call forwarded, the call is
26 / 204 3BL 95517 ABAA PCZZA Ed.01

forwarded to the forwarded-to party (subscriber C). If the calling party does want
the call forwarded, he can release the call to prevent call forwarding.
Note: In the case of re-routing by the Customized Applications for Mobile network En-
hanced Logic (CAMEL) server, the tone/announcement is not broadcast if the
Connect Message with a new destination routing address is received from the
CAMEL server.
3BL 95517 ABAA PCZZA Ed.01 27 / 204

2.1.1 Call Forwarding Unconditional (CFU)

Definition of the service The Call Forwarding Unconditional (CFU) service enables a mobile subscriber to
re-route all calls to another number.
This service is applied to one or more BSGs.
Service type Standardized service.
Subscriber A calls a mobile subscriber B who has the CFU service (see Figure 7):
On receiving the call setup message, the Gateway Mobile services Switching
Center (GMSC) asks the HLR/AuC for call routing information.
The HLR/AuC checks that:
the call is not prohibited by a call barring service,
the CFU service is operational for the basic service concerned,
there is no call forwarding violation, that is, the number of successive for-
warded calls is below the maximum limit allowed.
The HLR/AuC then sends to the GMSC:

the FTN,
the forwarding subaddress, if there is one,
the call forwarding options for the CFU service.
The GMSC analyzes the FTN as the new called number.

The GMSC:
routes the call to the PSTN if the FTN is the number of a fixed subscriber,
or,
initiates a terminating call procedure if the FTN is the number of a mobile
subscriber.
The call is registered in the GMSC so that subscriber B is charged for the forwarded
portion of the call.
Depending on the PLMN options, the GMSC may reject unconditional call for-
warding for a given category of calling subscribers.
28 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 7: CFU service for an HPLMN subscriber
CFU options:
CFU options are:
call released or call forwarding disabled on call forwarding violation,
call forwarding allowed on call forwarding violation when the FTN belongs to
a list of allowed destinations,
on call forwarding violation, call offered to the initially called UE or call re-
jected,
no indication to A and B of call forwarding,
presentation of the identity of B to C (subscriber receiving the forwarded calls),
or presentation of the identity of A to C,
rejection of subaddresses for call forwarding,
notification to B of the active state of the CFU service for each originating call,
notification to A that the call is forwarded.
3BL 95517 ABAA PCZZA Ed.01 29 / 204

2.1.2 Call Forwarding on No Reply from mobile subscriber

(CFNREPLY)
Service definition The Call Forwarding on No Reply from mobile subscriber (CFNREPLY) service en-
ables a mobile subscriber to re-route calls to another number when the mobile
subscriber fails to answer the call.
This service is applied to one or more BSGs.
Service description A subscriber A calls a mobile subscriber B who has the CFNREPLY service (see
Figure 8):
On receiving the call setup message, the GMSC asks the HLR/AuC for call
routing information.
The HLR/AuC checks that the call is not prohibited by a call barring service,
then sends the GMSC call routing information.
The GMSC routes the call to the VMSC B (MSC visited by subscriber B).
The VMSC B makes the call to subscriber B.
When a no-reply timer times out, the Visitor Location Register (VLR) checks that:
the CFNREPLY service is operational for the basic service concerned,
there is no call forwarding violation, that is, the number of successive for-
warded calls is below the maximum limit allowed.
The noreply timer has a value between 5 and 30 seconds, incremented in

multiples of 5. This value is stored in the HLR/AuC of the 8650 SDM and the
VLR for each BSG applicable to the CFNREPLY service.
The VLR sends to VMSC B:
the FTN for the no-reply condition,
the forwarded-to subaddress, if there is one,
the call forwarding options for the CFNREPLY service.
The VMSC B:
or,

subscriber.
The call is registered in the VMSC B so that subscriber B is charged for the for-
warded portion of the call.
Depending on the PLMN options, the GMSC can reject calls forwarded on no
reply for a given category of calling subscribers.
30 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 8: CFNREPLY service
CFNREPLY options:
The CFNREPLY options are:
modification of the no-reply timer when calls are forwarded for subscriber B,
use of the default no-reply timer value (20 seconds) when no default value is
set at the interface level,
call forwarding allowed on call forwarding violation, when the FTN belongs to
no indication of call forwarding to A and B,
presentation of the identity of B to C (the subscriber receiving the forwarded
calls), or presentation of the identity of A to C,
notification to B of the active state of at least one conditional call forwarding
service on each originating call,
notification to A that the call is forwarded,
notification to B that a call is forwarded by the CFNREPLY service.
3BL 95517 ABAA PCZZA Ed.01 31 / 204

2.1.3 Call Forwarding on mobile subscriber Not Reachable

(CFNREACH)
Service definition The CFNREACH service enables a mobile subscriber to re-route all calls to another
number when the mobile subscriber is not reachable.
The non-reachability conditions that trigger this service are:
absence in the HLR/AuC of the HPLMN of the address of local VLR of the called
party,
subscriber roaming in an unauthorized area,
paging failure,
radio congestion,
UE detachment.
The service is applied to one or more BSGs.
Service description Depending on the non-reachability conditions, call forwarding is performed either
by the GMSC or the VMSC.
Call forwarding by the GMSC:

When a subscriber A calls a mobile subscriber B who has the CFNREACH service
(see Figure 9):
On receiving the call set-up message, the GMSC asks the HLR/AuC for call
The HLR/AuC first checks that the call is not prohibited by a call barring service.
The HLR/AuC then checks that:
UE B is registered,
UE B is active,
roaming is allowed.
If any one of these conditions is not satisfied, subscriber B is not reachable. If

the CFNREACH service is operational and there is no call forwarding violation,
the HLR/AuC sends the GMSC (see Figure 9):
the FTN for the not reachable condition,
the call forwarding options.
The GMSC:
or,
triggers a terminating call procedure if the FTN is the number of a mobile
subscriber.
32 / 204 3BL 95517 ABAA PCZZA Ed.01

The call is registered in the GMSC so that subscriber B is charged for the forwarded
portion of the call.
Figure 9: CFNREACH service (call forwarding by the GMSC)
Call forwarding by the VMSC:

When a subscriber A calls a mobile subscriber B who has the CFNREACH service
(see Figure 10):
On receiving the call setup message, the GMSC asks the HLR/AuC for call
The HLR/AuC first checks that the call is not prohibited by a call barring service.
The HLR/AuC then checks that:
UE B is registered,
UE B is active,
roaming is allowed.
If the above conditions are satisfied:

The HLR/AuC sends the GMSC the call routing information,
The GMSC routes the call to the VMSC B (MSC visited by subscriber B),
The VMSC B initiates a paging procedure for UE B.
3BL 95517 ABAA PCZZA Ed.01 33 / 204

If the paging procedure fails or the radio network is congested, the subscriber is
not reachable. Having checked that the CFNREACH service is operational and
that there is no call forwarding violation, the VLR sends the VMSC B:
the FTN for the not reachable condition,
the call forwarding options for the CFNREACH service.
The VMSC B:
or,
subscriber.
Figure 10: CFNREACH service (call forwarding by the VMSC)
34 / 204 3BL 95517 ABAA PCZZA Ed.01

CFNREACH options:
The CFNREACH options are:
call released or call forwarding inactive on call forwarding violation (for call
forwarding on not reachable at the HLR/AuC),
in the case of a call forwarding violation, call offered to the initially called UE
or call rejected,
calls), or presentation of the identity of A to C,
notification to A that the call is forwarded.
2.1.4 Call Forwarding on Busy mobile subscriber (CFBUSY)

Definition of the service The Call Forwarding on Busy (CFBUSY) service enables a mobile subscriber to
re-route all new incoming calls to another number when the subscriber is busy
with a call.
Service description A subscriber A calls a mobile subscriber B who has the CFBUSY service (see
Figure 11):
On receipt of the call setup message, the GMSC asks the HLR/AuC for call
The HLR/AuC checks that the call is not prohibited by a call barring service.
The HLR/AuC then sends the call routing information to the GMSC.
The GMSC routes the call to the VMSC B (MSC visited by B).
The VMSC B initiates a paging procedure for UE B. The network cannot com-
plete the call because of a busy condition if during the paging procedure a
traffic channel (TCH) is already allocated to UE B and if any of the following
conditions apply:
the Call Waiting (CW) service is not activated,
the CW service is activated with a call already waiting,
the CW service is activated with no call waiting, but the call is released by
the UE because of the user busy condition.
The VLR checks:

that the CFBUSY service is operational,
that there is no call forwarding violation, that is, the number of successive
forwarded calls is less than the maximum limit allowed.
3BL 95517 ABAA PCZZA Ed.01 35 / 204

The VLR sends the VMSC B:

the FTN for the busy condition,
the call forwarding options for CFBUSY.
The VMSC B:
or,
subscriber.
Depending on the Public Land Mobile Network (PLMN) options, the network can
reject call forwarding on busy for a given category of calling subscribers.
Figure 11: CFBUSY service
36 / 204 3BL 95517 ABAA PCZZA Ed.01

CFBUSY options:
The CFBUSY options are:
calls), or presentation of the identity of A identity to C,
notification to A that the call is forwarded,
notification to B that the call is forwarded by the CFBUSY service on a busy
condition determined by the network.
2.1.5 Default Call Forwarding (CFD)

Service definition The Default Call Forwarding service (CFD) service is a call forwarding service, set
up by you, for calls to a mobile subscriber when the calls satisfy the conditions of
the CFNREPLY and CFNREACH and/or CFBUSY services but when these services
are not activated.
A mobile subscriber can use a CFD service to forward calls to a voice messaging
system.
Service description Subscribers can use the CFD service only if they have subscribed to one or more
CFC services. If the CFC services are provisioned but not activated, the network
triggers the CFD service if one of the following situations applies:
the UE fails to reply,
the UE is unreachable,
the UE is busy with a call.
The network forwards the call to an FTN that you register. The network transfers the
FTN to the VLR to which the UE is attached. This FTN replaces the FTN previously
registered by the subscriber for CFC (see Figure 12).
For one BSG, the FTN may be the same for various conditional call forwarding
(CFNREACH+CFNREPLY and eventually CFBUSY) or defined per conditional call
forwarding.
The CFD service follows the same principles as the conditional call forwarding
services.
When the subscriber activates a conditional call forwarding service, the network
automatically deactivates the CFD service. Conversely, when the subscriber deac-
tivates one or more conditional call forwarding services, the network automatically
reactivates the FTN for the CFD service.
The CFD service call is registered in the VMSC B so that subscriber B is charged
for the forwarded portion of the call.
3BL 95517 ABAA PCZZA Ed.01 37 / 204

Figure 12: CFD service
In a CFD service, there can be either an FTNd or FTNdb (default for Call Forward-
ing busy), FTNdc (default for not reachable), FTNdy (default for Call Forwarding
no reply). The FTN numbers are actually a list of FTN numbers: one FTN per BSG
(Call Forwarding number list). In Figure 12, CFD can also be associated with an
FTNdb or an FTNdc.
38 / 204 3BL 95517 ABAA PCZZA Ed.01

2.2 Call barring services

Call barring services enable mobile subscribers to eliminate calls. The two cate-
gories of call barring services are:
outgoing call barring services: Outgoing call barring services enable mo-
bile subscribers to eliminate all or some originating calls likely to be set up from
their UE.
incoming call barring services: Incoming call barring services enable mo-
bile subscribers to eliminate all or some terminating calls likely to be made to
their UE.
A mobile subscriber can have one or more call barring services for the same BSG.
However, only one incoming and one outgoing call barring service can be active
at the same time for a particular BSG.
Note: You need to subscribe to BSGs to be able to set these BSGs for the call barring
service.
Barring of outgoing calls has no effect on the capability of the UE to receive calls
(mobile terminated calls) or to make emergency calls. Similarly, barring of incom-
ing calls has no effect on the capability of the UE to make calls (mobile-originated
calls).
Note: You can restrict the ability of a subscriber to make or receive calls or use supple-
mentary services by using the Operator Determined Barring (ODB) function.
For information about ODB, see the Alcatel-Lucent 8650 SDM, SDM ODB Sub-
scription Management Operator guide, SDMODBOPG.
2.2.1 Barring of outgoing calls (BAOC, BOIC, BOIC-exHC)

Service definition The outgoing call barring services are:
Barring of All Outgoing Calls (except calls to emergency numbers) (BAOC),
Barring of Outgoing International Calls (BOIC),
Barring of Outgoing International Calls except those directed to the HPLMN
Country (BOIC-exHC).
An outgoing international call is a call to a mobile or fixed subscriber located

outside the country that the caller is visiting.
Service type Standardized services.
Service description When an originating call is set up, the VLR checks the settings of the calling sub-
scriber. If the called party is not linked to an emergency service, the VLR checks
the outgoing call barring services for the calling subscriber for the BSG involved
in the call. This check is performed by the VLR in the following order:
BAOC service,
BOIC service,
BOIC-exHC service.
3BL 95517 ABAA PCZZA Ed.01 39 / 204

The check performed by the VLR on the BAOC service results in one of the following
outcomes:
If the BAOC service is operational or induced by CAMEL, the call is barred.
The VLR sends the UE a notification that the call is barred. The VMSC A (MSC
visited by subscriber A) releases the call (see Figure 13).
If the BAOC service is not operational:
the originating call setup procedure continues when the call is not interna-
tional (from the point of view of the Visited PLMN (VPLMN),
the status of the BOIC service is checked when the call is an international
call (from the point of view of the VPLMN).
The check performed by the VLR on the BOIC service results in one of the following
outcomes:
If the BOIC service is operational or induced by CAMEL, the call is barred. The
VLR sends the UE a notification that the call is barred. The VMSC A releases
the call.
If the BOIC service is not operational:
the originating call setup procedure continues when the call is to the HPLMN
country of the subscriber,
the status of the BOIC-exHC service is checked when the call is not directed
to the HPLMN country.
The check performed by the VLR on the BOIC-exHC service results in one of the
following outcomes:
If the BOIC-exHC is operational or induced by CAMEL, the call is barred. The
VLR sends the UE a message indicating that the call is barred. The VMSC A
releases the call.
If the BOIC-exHC service is not operational, the originating call setup proce-
dure continues.
40 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 13: BAOC service
Operating restrictions:
When one or more outgoing call barring services are not supported by the VLR and
when the VLRHLR/AuC interface uses a MAP phase 2 protocol or later version,
the HLR/AuC of the 8650 SDM imposes operating restrictions (see Table 3).
Table 3: Operating restrictions if outgoing call barring not supported
Service not supported Resulting restriction
BAOC Roaming forbidden
BOIC Roaming forbidden
BOIC-exHC BOIC
3BL 95517 ABAA PCZZA Ed.01 41 / 204

2.2.2 Barring of all incoming calls (BAIC, BIC-Roam)

Service definition The incoming call barring services are:
barring of all incoming calls (BAIC),
barring of all incoming calls when roaming outside the HPLMN country (BIC-
Roam).
Service type Standardized services.
Service description On a terminating call setup, the GMSC asks the HLR/AuC for call routing infor-
mation. The HLR/AuC checks the subscription of the called party to ensure that
no geographic restrictions apply.
The HLR/AuC then checks the status of the BAIC service for the BSG involved in
the call:
If the BAIC service is active and operational or induced by CAMEL, the call
is barred. The HLR/AuC sends the GMSC an error message and the GMSC
releases the call (see Figure 14).
If the BAIC service is not operational, the terminating call setup procedure
continues with a check on the status of the BIC-Roam service.
The check on the BIC-Roam service results in one of the following outcomes:
If the BAIC service is active and operational or induced by CAMEL, the call is
barred when the subscriber having this service:
is roaming outside the country of the HPLMN,
does not have the CFU service for the same BSG.
The HLR/AuC sends the GMSC an error message and the GMSC releases the
call.
If the BIC-Roam service is not operational, the terminating call setup procedure
continues.
42 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 14: BAIC service
3BL 95517 ABAA PCZZA Ed.01 43 / 204

2.3 Call identification services

The call identification services are:
COnnected Line identification Presentation (COLP),
COnnected Line identification Restriction (COLR),
Calling Line Identification Presentation (CLIP),
Calling Line Identification Restriction (CLIR),
Malicious Call Identification (MCI).
Calling Name Presentation (CNAP).
Note: The line identity display services (COLP and CLIP) are linked to a corresponding
line identification restriction service (COLR and CLIR).
2.3.1 COnnected Line identification Presentation (COLP)

Service definition The COnnected Line identification Presentation (COLP) service is used to display
the identity of the connected line (the called party) on the UE of the calling sub-
scriber.
Service description The UE of the calling subscriber displays the connected line identity if:
the calling subscriber has the COLP service,
the final called party has not activated the COLR service,
the subscriber with call forwarding selects the option that the calling user is
notified of call forwarding.
On each originating call made by subscriber A, the VMSC A contacts the VLR to
check the rights of the calling subscriber to the COLP service. If subscriber A has
this service, the VMSC A asks the network to provide the connected Line Identity
(LI).
In response to the request, the network sends the VMSC A the called party identi-
fication data (see Figure 15). This data includes:
the Presentation Indicator (PI) of the LI, which has one of the following values:
presentation allowed,
presentation restricted,
presentation not available.
the LI (if available and if disclosure is allowed) accompanied, where appropri-

ate, by a supplementary designation number (NDS) and a subaddress.
the Screening Indicator (SI) which indicates whether the line identity was sup-
plied by:
the network,
the called subscriber, checked by the network,
44 / 204 3BL 95517 ABAA PCZZA Ed.01

the called subscriber, unchecked by the network.
The local VLR checks:

that the VLR supports the COLP service,
for the presence of the called line identification data (LI, PI, SI),
the PI value,
the presence of the called line identification restriction override option.
The called line identification restriction override option, together with the COLP
service, enables the calling subscriber to force presentation of the connected line
identity when the called subscriber has the COLR service. The calling subscriber
can use this option only when located in the HPLMN.
The display of the connected line identity depends on the checks made by the VLR
(see Table 4). UE A displays the connected line identity in the form of a value
received from the network after it has been processed by the translation function
in the Radio Control Point (RCP).
The connected line identity is not requested from the network in the case of an
emergency call.
Figure 15: COLP service
3BL 95517 ABAA PCZZA Ed.01 45 / 204

Table 4: Called subscriber identification according to data received by VMSC
Data received by the VMSC Data sent to the calling subscriber

COLP service COLP service with COLR
override
LI avail- PI NDS received LI = LI or NDS with or LI = LI or NDS with or with-

able without subaddress (1) out subaddress (1)
= presen-
tation al-
PI = presentation allowed PI = presentation allowed
lowed
SI transmitted unchanged SI transmitted unchanged
NDS not received LI = LI with or without sub- LI = LI with or without sub-

address address
PI NDS received LI and NDS not transmitted LI = LI or NDS with or with-

out subaddress (1)
= presen-
PI = presentation restricted
tation re-
stricted
SI transmitted unchanged
NDS not received LI not transmitted LI = LI with or without sub-

address
LI not PI LI not transmitted LI not transmitted

available
= presen- PI = presentation not avail-
PI = presentation not avail-
tation not able
able
available
Note: (1): Depending on the options selected on provision of the COLP service, the
identity presented to the calling subscriber corresponds to the LI or the NDS of the
called subscriber.
46 / 204 3BL 95517 ABAA PCZZA Ed.01

2.3.2 COnnected Line identification Restriction (COLR)

Service definition The COnnected Line identification Restriction (COLR) service is used by a called
subscriber to prevent the line identity from being presented to the calling sub-
scriber when the calling subscriber has the COLP service.
Service description The principle of the COLR service is described in Figure 16.
The COLR service is implemented when the network requests the identity of the
called subscriber.
On receipt of the request, the local VLR of the called subscriber checks that the
called subscriber has the COLR service.
Depending on the characteristics of the call, different called subscriber identifica-
tion data is affected:
if the call is not an Integrated Services Digital Network (ISDN) call from end-
to-end:
the PI is set to presentation restricted,
transmission to the calling subscriber of the LI accompanied, where appro-
priate, by an NDS and a subaddress, depends on a COLR service functional
option.
if the call is an ISDN call from end-to-end:

the LI is transmitted to the calling subscriber accompanied, where appro-
priate, by an NDS and a subaddress,
the PI is set to presentation restricted,
the SI is set to the identity supplied by the network value.
Presentation to the calling subscriber of the connected line identity of the called
subscriber depends on whether the COLR override option is associated with the
COLP service of the calling subscriber. The COLR override option is operational
only when calling parties are located in their HPLMNs.
3BL 95517 ABAA PCZZA Ed.01 47 / 204

Figure 16: COLR service between two mobile subscribers in the same network
48 / 204 3BL 95517 ABAA PCZZA Ed.01

2.3.3 Calling Line Identification Presentation (CLIP)

Service definition The Calling Line Identification Presentation (CLIP) service is used to display the
line identity of the calling subscriber on the UE of the called subscriber.
Service description The Calling Line Identity (CLI) is displayed on the UE of the called subscriber if:
the called subscriber has the CLIP service,
the calling subscriber has not activated the CLIR service.
The CLI is normally transmitted between the GMSC and the VMSC via signaling
links (Integrated Services Digital Network User Part (ISUP) signaling in the Initial
Address Message (IAM). Depending on a functional option, however, the CLI can
also be transmitted in MAP messages regardless of the type of network through
which the call is routed. The GMSC supplies the HLR/AuC in the 8650 SDM with
the CLI in the Send Routing Information (SRI) message. The HLR/AuC then trans-
mits the CLI to the visited VLR in the Provide Routing Number (PRN) message.
Note: Depending on a functional option, the HLR/AuC of the 8650 SDM sends the CLI
in MAP messages to the VLR only if the UE is roaming outside the country of its
HPLMN.
By setting PLMN data in the MSC, you can select CLI received via MAP to take
precedence over CLI received via ISUP signaling:
always,
only when the subscriber belongs to the RCP country, or,
only when the subscriber does not belong to the RCP country.
The network automatically implements the CLIP service when the VMSC receives
the call setup message. See Figure 17 for an illustration of CLI sent via ISUP
signaling. See Figure 18 for an illustration of CLI sent via MAP messages. The
call setup message includes the following calling line identification data:
The CLI consisting of:
the calling LI that indicates the number of the calling subscriber. The LI may
be associated with a subaddress,
where appropriate, a supplementary designation number (NDS) which may
also be associated with a subaddress.
The PI that indicates whether presentation of the CLI is:

allowed,
restricted,
not available.
The SI gives the origin of the CLI:

the network,
the calling subscriber with network verification,
the calling subscriber with no network verification.
3BL 95517 ABAA PCZZA Ed.01 49 / 204

When requested by the VMSC, the destination VLR checks:

whether it supports the CLIP service,
the entitlement of the called subscriber to the CLIP service,
availability of the LI,
the presence of an NDS,
the PI value,
the presence of the calling line identification restriction override option.
This override option, together with the CLIP service, enables the called subscriber
to force presentation of the CLI if the calling subscriber has the CLIR service and
if the called subscriber is located in the HPLMN.
When the destination VLR does not support the CLIP service, the CLI is not included
in the call setup message sent to the called subscriber.
When the CLIP service is supported by the destination VLR, the called subscriber
receives the identification data of the calling subscriber in the call setup message,
as indicated in Table 5.
The translation function in the RCP process the CLI before it is presented to the
called subscriber to ensure that the CLI is presented in the appropriate format.
Figure 17: CLIP service CLI transmitted via ISUP signaling
50 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 18: CLIP service CLI transmitted via MAP message
3BL 95517 ABAA PCZZA Ed.01 51 / 204

Table 5: Calling subscriber identification according to data received by VMSC
Data received by the VMSC Data sent to the called subscriber

CLIP service CLIP service with CLIR
override
LI avail- PI = pre- NDS received and ap- CLI = NDS with or without CLI = NDS with or without
able sentation plicable (1) subaddress a subaddress
allowed
SI = identity supplied by the SI = identity supplied by the

calling party with verification calling party with verifica-
of the network tion of the network,
or or
identity supplied by the call- identity supplied by the call-
ing party without network ver- ing party without network
ification verification
NDS not received or not CLI = LI with or without sub- CLI = LI with or without
applicable address subaddress
PI = presentation allowed
PI = pre- NDS received and ap- CLI not transmitted CLI = LI or NDS with or
sentation plicable (1) without subaddress (2)
restricted PI = presentation restricted
SI = identification supplied
by the calling party with
verification of the network
or
identification supplied by
the calling party with no
network verification
(if CLI = NDS)
(if CLI = LI)
NDS not received or not CLI not transmitted CLI = LI with or without
applicable subaddress
LI not CLI not transmitted CLI not transmitted

available
(3) or PI = presentation not avail- PI = presentation not avail-
truncated able able
52 / 204 3BL 95517 ABAA PCZZA Ed.01

Note: (1): The applicability of the NDS depends on the following CLIP service provision-
ing options:
authorization to replace the LI with the NDS if the NDS received from the net-
work is:
a national or international E.164 number,
an E.164 number of the same type as the LI (national or international),
a private number.
(2): The identity presented depends on a CLIP service functional option.

(3): If the calling subscriber is not an ISDN subscriber, the LI received by the VMSC
may be considered unavailable depending on the CLIP service option.
2.3.4 Calling Line Identification Restriction (CLIR)

Service definition The Calling Line Identification Restriction (CLIR) service enables a calling sub-
scriber to temporarily or permanently prevent presentation of their line identity to
the called subscriber when the called subscriber has the CLIP service.
Service description The CLIR service is offered in two operating modes:

permanent mode: presentation of the CLI is never allowed,
temporary mode:
with presentation restricted by default: presentation of the CLI is allowed
only on explicit authorization from the calling subscriber,
with presentation allowed by default: presentation of the CLI is restricted
only on explicit authorization from the calling subscriber.
Presentation or restriction of CLI is authorized by the calling subscriber at the time

of call setup.
The CLIR service is implemented automatically by the network when the MSC vis-
ited by the calling subscriber receives the call setup message (see Figure 19).
The VLR first confirms that the call is not barred. The VLR then checks:
whether it supports the CLIR service,
the rights of the calling subscriber to the service,
the operating mode chosen by the subscriber.
If the CLIR service is not supported by the originating VLR, the call is rejected when
the calling subscriber requests CLIR at the time of call setup (see Table 6).
When the CLIR service is supported by the originating VLR, presentation of the CLI
to the called subscriber (mobile or fixed subscriber) depends on:
the operating mode of the CLIR service,
the request made by the calling subscriber at the time of call setup.
When the VLR does not receive the assignment state of the CLIR service from the
HLR/AuC, one of the following default status values is used:
3BL 95517 ABAA PCZZA Ed.01 53 / 204

service not assigned,

or,
service assigned and temporary mode CLIR with presentation restricted by de-
fault.
This default value is defined by a functional option during network configuration.
Figure 19: CLIR service between two mobile subscribers in the same network
54 / 204 3BL 95517 ABAA PCZZA Ed.01

Table 6: Calling line identification according to CLIR service
Operating Action by the Data sent to the called party

mode calling party on
call setup
Permanent mode None or CLI sent but not presented (2)

erasure of CLIR (1)
SI = identity supplied by the network
Temporary mode None CLI sent but not presented (2)

with presentation
restricted by de- PI = presentation restricted
fault
Erasure of CLIR CLI presented
Temporary mode None CLI presented

with presentation
allowed by default PI = presentation allowed
Erasure of CLIR CLI sent but not presented (2)
Note: (1): In permanent mode, the request to erase the CLIR service by the calling party
is rejected. A rejection notification is sent but call setup is not interrupted.
(2): Presentation of the calling line identity is forced when the called subscriber
has the CLIP service with the calling line identification restriction override option.
This option can only be used when the called subscriber is located in the HPLMN.
2.3.5 Malicious Call Identification (MCI)

Service definition The Malicious Call Identification (MCI) service enables a mobile subscriber to ob-
tain information, from the operator, about the origin of a call (for example, a
nuisance call).
Service type Proprietary service.
Service description Since MCI is a proprietary service, the data associated with the service is transmit-
ted by the HLR/AuC to the local VLR of the called subscriber only when the called
3BL 95517 ABAA PCZZA Ed.01 55 / 204

subscriber is located in the HPLMN. The data is transmitted to the VLR (see
Figure 20):
immediately if the UE is registered in the VLR,
during the next location update if the UE is not registered in the VLR.
When the VLR HLR/AuC uses a MAP phase 2 protocol or later version, and when
the MCI service is not supported by the VLR, a message is sent to the HLR/AuC.
In this case, no MCI service data is transmitted to the VLR.
Each time a terminating call is set up in the MSC visited by the called subscriber,
the VLR sends the Radio Control Function (RCF) the assignment state of the MCI
service. If the MCI service is assigned to the called subscriber, when the call is
released the MSC generates an unsolicited message (MCI message) containing
the Call Detail Record (CDR) of the called subscriber.
This message is never printed locally in the VMSC. It is sent to the Operation and
Maintenance Center (OMC). If a network has an external center that is dedicated
to the collection of unsolicited messages, the OMC sends the message to the
external center, otherwise, the message is stored in the OMC in a general records
file where it is retained for 24 hours.
You can retrieve the message corresponding to this call at the request of the mobile
subscriber. The message contains details about the malicious call.
No MCI message is generated for forwarded calls.
Figure 20: MCI service
56 / 204 3BL 95517 ABAA PCZZA Ed.01

2.3.6 Calling Name Presentation (CNAP)

Service definition The Calling Name Presentation (CNAP) service provides the ability to indicate the
name of the calling party to the called party at call setup time for all incoming
calls. The calling party takes no action to activate, initiate, or provide the CNAP
in any way.
The delivery of the calling name to the called party may be affected by other
services that the calling party has subscribed to. For example, if the calling party
has subscribed to Calling Line Identification Restriction (CLIR), then the calling line
identity and the calling name identity is not presented to the called party.
The calling party may request not to present the name. The presentation may be
allowed if CLIR overriding is allowed for some called numbers.
Service description When a subscribers has subscribed to the CNAP service, at call setup, the HLR
requests the VMSC to provide the name of the calling party (see Figure 21).
The VMSC then interrogates an external Line Information DataBase (LIDB) for the
name. If the calling party has allowed presentation of its name, the LIDB sends
the name to the VMSC and the VMSC then sends it to the called party. The name
is displayed on the handset of the called party.
Figure 21: CNAP service
3BL 95517 ABAA PCZZA Ed.01 57 / 204

2.4 Call completion services

The call completion services are:
call HOLD (HOLD),
Call Waiting (CW),
Explicit Call Transfer (ECT),
2.4.1 Call Hold (HOLD)

Service definition The HOLD service enables a subscriber to interrupt a conversation temporarily to
take or make another call and then, if necessary, return to the first call.
This service applies only to speech calls, excluding emergency calls (TS12).
Service description A call can be placed on hold:

by the calling subscriber, if the calling subscriber has the HOLD service, after
the called subscriber has accepted the call and before the call is released,
by the called subscriber, if the called subscriber has the HOLD service, after
accepting the call and before the call is released.
The call service is initiated when the calling subscriber, using the UE, asks the
network to temporarily interrupt a call (see Figure 22). On receipt of the request,
the VMSC checks with the local VLR to confirm that the subscriber is entitled to the
HOLD service.
If the call hold request is accepted, the call is interrupted. The VMSC transmits an
acknowledgement to the subscriber who requested call hold.
The currently active call switches to the hold state. The Traffic CHannel (TCH)
assigned to the calling subscriber or the called party concerned is released from
the call on hold, but the traffic channel remains assigned to the mobile subscriber
concerned. The traffic channel is then available to make another call or to accept
a waiting call.
Depending on the hold service configuration options, a notification may be sent
to the subscriber placed on hold.
58 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 22: HOLD service
Operations on a call on hold:

A subscriber with the HOLD service can:
when the subscriber has a call on hold and no active call:
retrieve the call on hold,
make another call,
release the call on hold,
receive an incoming call if the CW service is activated.
when the subscriber has a call on hold and an active call:

switch from one call to the other (place the active call on hold and continue
with the original call on hold),
release the active call,
release the call on hold,
release both calls.
when the other party also has the HOLD service:

the HOLD service is initiated by just one party (calling or called subscriber),
or,
each party places the other on hold.
When the mobile subscriber makes a new call or accepts a waiting call:
in a UMTS network, the call is rejected if the type of traffic channel needed
is different from that already assigned to the call on hold.
3BL 95517 ABAA PCZZA Ed.01 59 / 204

in a GSM network, under a functional option, it is possible for a mobile

subscriber to make a new call or accept a waiting call with a different traffic
channel (for example, place a speech call on hold to accept a fax or data call).
To return to the call on hold, the subscriber executes a procedure using the UE
to ask the network to retrieve the call on hold. If the request is accepted, the call
previously placed on hold becomes the new active call and the traffic channel is
reassigned for the call.
The calling or called subscriber can place only one call on hold at a time, except
during transitional periods associated with the double call procedure. This tran-
sitional period is limited by a timer (T = 5 seconds).
The called subscriber or the calling subscriber can release the call on hold at any
time.
2.4.2 Call Waiting (CW)

Service definition The CW service enables a mobile subscriber to receive notification of the presence
of a call when already engaged in a call.
This service does not apply to the emergency call (TS12) or to the Short Message
Service (SMS).
Service description The principle of the CW service is described in Figure 23.

On receipt of an incoming call, and before initiating the paging procedure, the
MSC visited by the called subscriber checks that:
the called mobile subscriber is already engaged in a call with another sub-
scriber,
a traffic channel is already assigned to that call,
the CW service is activated for the basic service associated with the call,
there are no other calls waiting.
If these conditions are true, the MSC sends the called subscriber a new incoming
call setup message that includes a CW indicator.
The VMSC waits for the UE to return a call setup message acknowledgement. The
CW service is then suspended for any other incoming call. After receipt of the
acknowledgement, the following timers are started:
CW service timer,
no-reply timer (if the subscriber has activated the CFNREPLY service).
The calling subscriber receives a call waiting indication depending on the CW

service provision options.
To pick up a waiting call, the subscriber needs to release the current call or place
the call on hold. When the subscriber accepts the waiting call, the timers stop and
the call waiting service becomes available again for incoming calls.
If the VMSC does not receive a call waiting acceptance before the no-reply timer
times out, the call is subject to the call forwarding on no reply process (CFNREPLY)
if this service is activated. Otherwise, the CW service timer continues until it times
60 / 204 3BL 95517 ABAA PCZZA Ed.01

out. The waiting call is then released and the CW service becomes available again
for other incoming calls.
The VMSC generates a CDR if the subscriber accepts the waiting call.
Figure 23: CW service
3BL 95517 ABAA PCZZA Ed.01 61 / 204

2.4.3 Explicit Call Transfer (ECT)

Service definition The ECT service enables a mobile subscriber to create a double call after placing
the first call on hold, connecting the two parties, and then withdrawing completely
from the call.
This service applies only to speech calls, and does not include emergency calls
(TS12).
The ECT service can be the subject of a CAMEL supplementary service notification.
Service description The principle of the ECT service is described in Figure 24.
Calls involved in this service may be incoming or outgoing calls:
the subscriber with the ECT service must place one of the calls on hold,
the other call can be in the conversation or ringing phase depending on the
option selected on provisioning the ECT service.
The ECT service is executed as follows:

a mobile subscriber makes an ECT service request,
the two remote subscribers are interconnected,
the subscriber requesting the ECT service is disconnected.
Depending on the capabilities of the UE, the ECT service request will be made:
directly by the subscriber from the UE of the subscriber using one of the two
current calls,
using an Unstructured Supplementary Service Data (USSD) procedure when
the UE is not able to make the request directly and if the associated functional
option for the ECT service is active.
On receipt of the request, the MSC visited by the calling subscriber checks with
the local VLR to ensure that the subscriber is entitled to the ECT service. If the
subscriber is entitled to the service, the VMSC sets up the call between the two
remote subscribers (subscribers B and C). If an associated functional option is
active, a notification may be sent to the remote subscribers.
The notification sent to the first remote subscriber includes the identity of the sec-
ond subscriber. The notification sent to the second remote subscriber includes the
identity of the first subscriber.
The VMSC then disconnects the calling subscriber from the call transfer. When the
call transfer is established, the calling subscriber can initiate another call transfer
without waiting for the completion of the first call transfer.
62 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 24: ECT service
To avoid loops in the network, the identities of the subscribers involved in the
call are checked, depending on an ECT service provisioning option. The network
rejects the call transfer if the identities of the two remote parties are the same, or if
one of the two identities matches the identity of the mobile subscriber requesting
the call transfer.
The maximum number of call transfers executed in parallel for a subscriber is
seven. When the number reaches the maximum allowed, further call transfer
requests from that subscriber in the same MSC are rejected.
At the end of the call between the two remote subscribers (B and C), the VMSC A
sends two CDRs: one for the call between A and B, and one for the call between
A and C. If subscriber A requested both calls, both calls are charged to subscriber
A for their total duration, including the duration of the call between subscribers B
and C.
The ECT service requires a VLR that supports the MAP phase 2 protocol or later
versions.
3BL 95517 ABAA PCZZA Ed.01 63 / 204

2.5 Group services

The group services are:
MultiParTY (MPTY),
Closed User Group (CUG).
2.5.1 MultiParTY (MPTY)

Service definition The multiparty (MPTY) call service is used to set up a conference call between up
to six subscribers.
This service applies only to speech calls, excluding emergency calls (TS12).
The MPTY service can be the subject of a CAMEL supplementary service notifica-
tion.
Service description The principle of the MPTY service is described in Figure 25.
The MPTY service requires the activation of the HOLD supplementary service.
The calls involved in a conference call can be incoming or outgoing calls. To set
up a conference call, the subscriber initiating the conference call (also called the
controlling subscriber) must have:
an active call,
a call on hold.
The MPTY service is initiated when the controlling subscriber sends a request from
the UE to the network for a multiparty call with the two calls.
The conference call request is accepted if the following conditions are met:
The controlling subscriber is entitled to the MPTY service.
The MSC visited by the controlling subscriber checks with the local VLR to en-
sure that the controlling subscriber is entitled to the MPTY service.
The basic service involved is speech (excluding emergency calls).
If the above conditions are satisfied, the VMSC sets up the conference call between
the controlling subscriber and the two remote subscribers. If the conditions are
not satisfied, the request is rejected.
At the request of the controlling subscriber, a party can be added to (under the
same conditions) or removed from the conference call. A conference call is limited
to six parties (including the controlling subscriber).
Depending on MPTY service provisioning options, the network can send notifica-
tions to the parties of the conference call.
64 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 25: MPTY service
3BL 95517 ABAA PCZZA Ed.01 65 / 204

Basic operations :
Figure 26 illustrates some of the basic operations that the controlling subscriber
can perform:
Figure 26: Conference call basic operations
66 / 204 3BL 95517 ABAA PCZZA Ed.01

Operations:
The controlling subscriber is the only party permitted to manage the conference
call. The controlling subscriber can set up only one conference call at a time.
After setting up the conference call, the controlling subscriber can:
place the conference call on hold (the parties on hold can continue to com-
municate with each other),
make a private call with a party involved in the conference call. The other
parties remain connected to the conference call which is on hold,
disconnect one party or terminate the conference call by disconnecting all the
parties in the conference.
The controlling subscriber can place the entire conference call on hold (see Figure
26) but cannot place an individual call on hold unless there is only one party
remaining in the conference call.
After placing the conference call on hold, the controlling subscriber can:
make a new call (if this call does not belong to the basic service TS11 it cannot
be included in the conference),
answer a waiting call (if this call does not belong to the basic service TS11 it
cannot be included in the conference call),
retrieve the conference call,
parties in the conference.
The controlling subscriber can retrieve the entire conference call that was placed
on hold, but cannot retrieve individually a single call from the conference on hold
unless there remains only one party to the conference call.
The controlling subscriber involved in a basic service TS11 single call and a con-
ference call can:
add the single call to the conference call,
alternate between the conference call and the single call, by placing the active
call on hold and retrieving the conference call,
parties in the conference,
disconnect the single call.
A CDR is issued for each call involved in the conference call with an indication
that the call was included in a conference call. In addition, the CDR of the call
which terminates the conference calls contains various information about the con-
ference call (for example, duration of the call, number of operations invoked by
the controlling subscriber, etc.).
3BL 95517 ABAA PCZZA Ed.01 67 / 204

2.5.2 Closed User Group (CUG)

Service definition The Closed User Group (CUG) service enables subscribers, connected to a PLMN
and possibly to other networks, to form closed user groups (CUGs) to and from
which access is restricted.
A specific subscriber can be a member of one or more CUGs (maximum of 10
CUGs). Members of a specific CUG can communicate among each other but not
with subscribers outside the group.
The CUG service is applicable to the following communication services:
BSG20,
BSG30,
SPEECH,
FAX.
Service description The aim of the CUG service is to guarantee the integrity of any CUG call handled
by the PLMN.
CUG handling in originating calls:
The principle of CUG handling in originating calls is described in Figure 27 and
Figure 28.
The UE sends an originating call request with CUG information (any combi-
nation of CI, SPC, and SOA) to the RCF.
The RCF sends a message to the Basic Call Handling (BCH) in the VLR to
check the basic service requested for the call and the supplementary services
applicable to that basic service.
The BCH performs an IN invocation and a Call Barring check in the VLR.
The BCH then sends an internal message to the CUG to check:
the provisioning of CUG for the requested basic service,
whether outgoing calls are barred within the CUG,
the preferential CUG and Outgoing Access (OA) subscription information.
The CUG responds to the BCH in the VLR either authorizing or not authorizing
the calling UE to the CUG services.
On successful authorization:
the BCH sends conditional CUG information to the RCF,
the RCF sends the conditional CUG information with the CUG index to the
UE,
the RCF sends the conditional CUG information to the Service Switching
Point (SSP) to establish the CUG service.
On unsuccessful authorization:
the BCH sends information of a CUG error to the RCF,
the RCF sends the information of the CUG error to the UE.
68 / 204 3BL 95517 ABAA PCZZA Ed.01

Figure 27: An originating call request: successful CUG authorization
Figure 28: An originating call request: unsuccessful CUG authorization
3BL 95517 ABAA PCZZA Ed.01 69 / 204

CUG handling in terminating call:

For terminating calls, the scenario applied is very similar to that of originating
calls.
On receiving a terminating call request, the SSP in the GMSC sends CUG
information to the RCF in the GMSC.
The RCF transfers the CUG information to the Basic Call Handling (BCH) in
the HLR/AuC to check the basic service requested for the call and the supple-
mentary services applicable to that basic service.
The BCH checks that the call is not prohibited by a call barring service and
then sends an internal message to the CUG in the HLR/AuC to check:
the provisioning of CUG for the requested basic service,
whether incoming calls are barred within the CUG,
the preferential CUG and Incoming Access (IA) subscription information.
The CUG responds to the BCH in the HLR/AuC either authorizing or not au-
thorizing the called UE to the CUG services.
On successful authorization:
the BCH checks that the CFU service is operational for the basic service
concerned,
the BCH sends conditional CUG information to the RCF,
the RCF sends the conditional CUG information with the CUG index to the
SSP in the GMSC,
the SSP in the GMSC sends the conditional CUG information to the SSP in
the VMSC to establish the CUG service.
On unsuccessful authorization:
the BCH sends information of a CUG error to the RCF,
the RCF transfers the information of the CUG error to the originating net-
work.
70 / 204 3BL 95517 ABAA PCZZA Ed.01

2.6 Charging services

The charging supplementary services are:
Advice Of Charge-Information (AOCI),
Advice of Charge-Charging (AOCC).
2.6.1 Advice Of Charge-Information (AOCI)

Service definition The AOCI service enables a mobile subscriber to estimate the cost of a call (no
contractual value), based on information displayed in real time on the UE.
2.6.2 Advice Of Charge-Charging (AOCC)

Service definition The AOCC service displays the cost of a call on the UE of the subscriber at the
end of a call.
3BL 95517 ABAA PCZZA Ed.01 71 / 204

2.7 Priority call services

The priority call services are represented by the enhanced Multi-Level Precedence
and Pre-emption (eMLPP) service.
2.7.1 enhanced Multi-Level Precedence and Pre-emption (eMLPP)

Service definition The eMLPP service enables subscribers to prioritize calls according to the following
rules:
Precedence: a priority level is assigned to a call during call set-up,
Pre-emption: resources for a call of lower precedence are allocated to a call
of higher precedence.
An on-going call of lower precedence can be disconnected to accept an in-
coming call of higher precedence.
The eMLPP service is applicable to the following communication services:

BSG20,
BSG30,
SPEECH,
FAX.
Service description Precedence levels:

The eMLPP service provides different levels of precedence for call set-up and call
continuity. Subscribers can select authorized precedence levels on per-call basis
at call set-up. If they do not, the network applies subscribers specific default
precedence levels.
Once set for a call, precedence levels can not be changed.
Priority levels:
Several priority levels are allowed for subscribers in a network. A network operator
allocates call set-up classes and pre-emption capabilities to each priority level.
According to call priority, the network decides the respective actions to be taken
(for example, queuing priority, fast call set-up procedures or possibly pre-emption
in case of congestion of network resources).
In case of pre-emption, the network allocates resources of an on-going call of
lower precedence to an incoming call of higher precedence. Pre-emption is only
performed to provide precedence for those priority levels which have a pre-emp-
tive capability allocated by the network operator. Priority levels with no allocated
pre-emption capability only have queuing priority.
Note: Pre-emption is not possible if the on-going call is an emergency call.

The VLR stores:
service state information,
maximum priority levels a subscriber is entitled to use,
a default priority level received from the Home Location Register (HLR).
72 / 204 3BL 95517 ABAA PCZZA Ed.01

The MSC stores information on resource pre-emption actions for any given levels
for incoming and on-going call priority.
3BL 95517 ABAA PCZZA Ed.01 73 / 204

2.8 Operator services

The operator services are Operator Specific Supplementary Services (OSSS).
2.8.1 Operator Specific Supplementary Service (OSSS)

Service definition Operator Specific Supplementary Service (OSSS) is a supplementary service that
is specific to an operator.
Service type Proprietary service.
Service description OSSSs require the MAP phase 2 protocol or later versions. This protocol includes
16 codes for OSSSs. You can use 15 of these codes to define operator specific
services (OS1 to OS15). One of the 16 codes is a reserved code and cannot be
used to define an OSSS.
74 / 204 3BL 95517 ABAA PCZZA Ed.01

3 Supplementary Services management overview
This chapter mainly describes the key procedures that you perform to open and
manage supplementary services. It provides also a short functional description of
each parameter required for SS management.
This chapter includes sections about:
Supplementary Services management overview (see section 3.1),
Call Barring parameters (see section 3.2),
Call Forwarding parameters (see section 3.3),
GCS parameters (see section 3.4),
CUG parameters (see section 3.5),
eMLPP parameters (see section 3.6),
3BL 95517 ABAA PCZZA Ed.01 75 / 204

3.1 Supplementary Services management overview

You manage supplementary services at the 8650 SDM to provision an existing
subscriber with characteristics, for a basic, a CS and/or a PS subscription.
3.1.1 Tools used to manage Supplementary Services in the 8650 SDM

You can manage SS in the 8650 SDM:
using the 8650 SDM Graphical User Interface (GUI), or
using a standard Common Object Request Broker Architecture (CORBA) in-
terface, between the HLR/AuC in the 8650 SDM and a proprietary external
management application, for example a Customer Care and Billing System
(CCBS), or
using mass management files (except for copy operations).
For more information about:

management using the 8650 SDM GUI, see the Alcatel-Lucent 8650 SDM,
SDM Application Management Operator guide, SDMOPG,
management using a standard CORBA interface, see the Alcatel-Lucent 8650
SDM, CORBA Interface Description for SDM Provisioning Management Pro-
grammer guide, SDMCORPRG,
mass management, see the Alcatel-Lucent 8650 SDM, SDM Mass Manage-
ment Operator guide, SDMMASOPG.
3.1.2 Documentation to use to manage supplementary services

Documentation to use to manage supplementary services at the 8650 SDM, in-
cludes:
this operator guide,
the On Line Help (OLH) of the 8650 SDM GUI.
The On Line Help (OLH) of the 8650 SDM GUI:

provides you with possible supplementary services parameter values and a
description for each value.
is available in the 8650 SDM documentation set,
is used as On Line Help when using the 8650 SDM GUI.
3.1.3 Supplementary Services management operations and

subdomains
This section describes basic management operations you perform to create and
enable Supplementary Services in your network.
Management operations You manage Supplementary Services at the 8650 SDM by using the tools de-
scribed in section 7.1.2. These tools enable you to:
provision a supplementary service(s),
list supplementary services,
76 / 204 3BL 95517 ABAA PCZZA Ed.01

modify supplementary services,

copy supplementary services,
delete supplementary services.
Management subdomains You can manage Supplementary Services from:

the S UB / S ubscri p ti on/ S UB _OAM_B asi cS ubscri p ti on subdo-
main,
For general information about subscriptions, see Alcatel-Lucent 8650 SDM,
SDM Subscription management Operator guide, SDMSUBOPG.
the S UB / S up p l ementary S ervi ce subdomain divided into the following
subdomains:
S UB_OAM_S up p l ementary S ervi ce_C allBarri ng ,
S UB _OAM_S up p l ementary S ervi ce_C al l Forw ard i ng ,
MS _OAM_S UP_GC S ,
S UB _OAM_S up p l ementary S ervi ce_C ug ,
S UB _OAM_S up p l ementary S ervi ce_eMLPP .
Whatever the subdomain is, the parameters to set up are identical.
3BL 95517 ABAA PCZZA Ed.01 77 / 204

3.2 Call Barring parameters

barOutCallProv
Description
Barring of outgoing calls
barOutInterCallProv
Description
Barring of outgoing international calls
barOutIntCallExceptToH-
plmnProv Description
Barring of outgoing international calls except those directed to the HPLMN coun-
try
barIncCallProvisioned
Description
Barring of incoming calls
barIncCallRoamFCoun-
tryProv Description
Barring of incoming calls when roaming outside the HPLMN country is provi-
sioned
BSGofBAOClist
Description
List of BSGs activated for BAOC
BSGofBOIClist
Description
List of BSGs activated for BOIC
78 / 204 3BL 95517 ABAA PCZZA Ed.01

BSGofBOICEXHClist
Description
List of BSGs activated for BAOC except those directed to the HPLMN Country
BSGofBAIClist
Description
List of BSGs activated for BAIC
BSGofBICROAMlist
Description
List of BSGs activated for BAIC when Roaming outside the HPLMN country
MsCbAbility
Description
Ability of the UE to modify call barring data
callBarringPassword
Description
Value of the call barring password
3BL 95517 ABAA PCZZA Ed.01 79 / 204

3.3 Call Forwarding parameters

typeOfCallForwardingList
Description
Type of call forwarding
msCfNoAbility
Description
Ability of the UE to modify call forwarding data
destinationProfile
Description
Destination profile for forwarded to number translation
cfuCallForwardingNum-
berList Description
Call Forwarded Number list, one per BSG for Unconditional Call Forwarding
(one number for each BSG activated)
cfbusyCallForwardingNum-
berList Description
Call Forwarded Number list, one per BSG for Call Forwarding on Busy sub-
scriber
cfnreplyCallForward-
ingNumberList Description
Call Forwarded Number list, one per BSG for Call Forwarding on No Reply
80 / 204 3BL 95517 ABAA PCZZA Ed.01

cfnreachCallForward-
ingNumberList Description
Call Forwarded Number list, one per BSG for Call Forwarding on No Reachable
subscriber
cfdCallForwardingNum-
berList Description
Call Forwarded Number list, one per BSG for Call Forwarding by default
cfdcfbusyCallForward-
ingNumberlist Description
Call Forwarded Number list, one per BSG for Call Forwarding, by default, on
Busy subscriber
cfdcfnreachCallForward-
ingNumberlis Description
subscriber Not Reachable
cfdcfnreplyCallForward-
ingNumberlist Description
No Reply
cfuNotifToFwdPartyFlag
Description
Enables notification to forwarded party for Unconditional Call Forwarding
3BL 95517 ABAA PCZZA Ed.01 81 / 204

cfbusyNotifToFwdPartyFlag
Description
Notification to forwarded party for Call Forwarding on busy subscriber
cfnreplyNotifToFwdPar-
tyFlag Description
Notification to forwarded party for Call Forwarding on no reply subscriber
cfnreachNotifToFwdPar-
tyFlag Description
Notification to forwarded party for Call Forwarding on no reachable subscriber
allNotifToFwdPartyFlag
Description
Notification to forwarding party for all types of Call Forwarding
cfuNotifToCallingPartyFlag
Description
Notification to calling party for unconditional Call Forwarding
cfbusyNotifToCalling-
PartyFlag Description
Notification to calling party for Call Forwarding on busy subscriber
cfnreplyNotifToCalling-
PartFlag Description
Notification to calling party for Call Forwarding on no reply subscriber
82 / 204 3BL 95517 ABAA PCZZA Ed.01

cfnreachNotifToCalling-
PartFlag Description
Enables notification to calling party for Call Forwarding on no reachable sub-

scriber
allNotifToCallingPartyFlag
Description
Notification to calling party for all types of Call Forwarding
3BL 95517 ABAA PCZZA Ed.01 83 / 204

3.4 GCS parameters

colpProvisionedFlag
Description
COLP provisioned flag
colpOverrideCategoryState
Description
COLP override category
clipProvisionedFlag
Description
CLIP provisioned flag
clipOverrideCategoryState
Description
CLIP override category state
clirProvisionedFlag
Description
CLIR provisioned flag
presentationMode
Description
Presentation mode
callHoldProvisionedFlag
Description
CH provisioned flag
84 / 204 3BL 95517 ABAA PCZZA Ed.01

mptyProvisionedFlag
Description
MPTY service provisioned flag
callTransferProvisionedFlag
Description
CT service provisioned flag
aoccProvisionedFlag
Description
AOCC service provisioned flag
aociProvisionedFlag
Description
AOCI service provisioned flag
maliciousCallProvisioned-
Flag Description
MCI service provisioned flag
colrProvisionedFlag
Description
COLR service provisioned flag
osss1ProvisionedFlag to
osss15ProvisionedFlag Description
OSSS 1 to 15 provisioned flags
3BL 95517 ABAA PCZZA Ed.01 85 / 204

osss1ActivationFlag to
osss15ActivationFlag Description
OSSS 1 to 15 activated flags
callWaitingProvisionedFlag
Description
CW service provisioned flag
cwTSSpeechActivationFlag
Description
Call waiting teleservice (speech) provisioned flag
cwTSFaxActivationFlag
Description
Call waiting teleservice (FAX) provisioned flag
cwBSG20ActivationFlag
Description
Call waiting asynchronous duplex circuit data service provisioned flag
Description
Call waiting synchronous duplex circuit data service provisioned flag
cnapProvisionedFlag
Description
CNAP service provisioned flag
86 / 204 3BL 95517 ABAA PCZZA Ed.01

cnapOverrideCategoryState
Description
CNAP override category state
3BL 95517 ABAA PCZZA Ed.01 87 / 204

3.5 CUG parameters

For more information about possible values for parameters, see the On Line Help
(OLH) of the 8650 SDM GUI.
cugInterlockCodeInd1 to
cugInterlockCodeInd10 Description
Identification code which uniquely identifies a CUG within the network
intraCugOptionInd1 to
intraCugOptionInd10 Description
Access restriction with other members of that CUG which indicates the UE ability
to originate or receive calls from within the CUG
AllassociatedBsgString1 to
AllassociatedBsgString10 Description
A string of BSGs where each is separated by a dash
prefCugIndexForSpeech
Description
Preferential CUG index number with a CUG interlock code associated to the
BSG Speech, which is the nominated default CUG to be used when no explicit
CUG index is received by the network
prefCugIndexForFax
Description
BSG Fax, which is the nominated default CUG to be used when no explicit
prefCugIndexForBsg20
Description
BSG Data Cda, which is the nominated default CUG to be used when no explicit
88 / 204 3BL 95517 ABAA PCZZA Ed.01

Description
BSG Data Cds, which is the nominated default CUG to be used when no explicit
interCugRestForSpeech
Description
Inter CUG restriction which allows receiving calls from or placing calls outside
the CUG associated to the BSG Speech
interCugRestForFax
Description
the CUG associated to the BSG Fax
interCugRestForBsg20
Description
the CUG associated to the BSG Data Cda
Description
the CUG associated to the BSG Data Cds
3BL 95517 ABAA PCZZA Ed.01 89 / 204

3.6 eMLPP parameters

For more information about possible values for parameters, see the On Line Help
(OLH) available on 8650 SDM GUI.
emlppMaximumEntitled-
Priority Description
Highest priority level that a subscriber can apply to an outgoing call during
set-up
emlppDefaultPriority
Description
Priority level which shall be assigned to a call when no explicit priority is fixed
during call set-up
emlppProvisionedFlag
Description
eMLPP service provisioned Flag
90 / 204 3BL 95517 ABAA PCZZA Ed.01

4 Call Barring key procedures
This chapter describes the following procedures and their parameters to manage
Call Barring (CB):
Provisioning call barring (see section 4.1),
Deleting call barring (see section 4.2),
Copying call barring (see section 4.3),
Displaying call barring information (see section 4.4),
Listing call barring (see section 4.5),
Modifying call barring (see section 4.6).
Note: Before managing basic subscription data, you need to be familiar with
Subscription management basics (see chapter 1).
3BL 95517 ABAA PCZZA Ed.01 91 / 204

4.1 Provisioning call barring

To provision call barring to a subscription you use the create operation. The pro-
vision call baring procedure enables you to:
provide call barring services for a mobile subscriber,
activate call barring services,
initialize call barring options.
Prerequisite(s) If you manage a subscription from the S UB _OAM_S up p l ementary S er-

vi ce subdomain, for a given subscriber, a CS and/or PS subscription has been
created.
To create a CS or a PS subscription, see the Alcatel-Lucent 8650 SDM, SDM
Subscription management Operator guide, SDMSUBOPG.
You can provision call barring services from the S UB _OAM_S up p lemen-
tary S ervi ce_C al l B arri ng _create subdomain.
You know the subscriber identity: Distinguished Name (DN)-subscriber profile.
Key procedure To provision call barring:

1. Enter the subscriber identity (subscriber profile, IMSI or MSISDN):
Using subscriber profile:
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
2. Select the operation:
92 / 204 3BL 95517 ABAA PCZZA Ed.01

If call barring SS... then...
does not exist create call barring
exists modify call barring
3. Set the msC B Abi l i ty that enables the UE to modify call barring services.
Set parameter(s)...
msC B Abi l i ty
4. Set the cal l B arri ng Passw o rd to enable creation by copy.
Set parameter(s)...
cal lB arri ng Passw ord
5. Set optional parameters related to call barring SS:
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
BarOutIntercallExceptToHplmnProv
BarIncCallProvisioned
BarIncCallRoamFCountryProv
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
6. End.
Information links The following table provides references to related information.
For more information about... see...
tools used to manage supplementary services section 3.1
3BL 95517 ABAA PCZZA Ed.01 93 / 204

the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
parameters for call barring services section 3.2
interactions between supplementary services chapter 9
94 / 204 3BL 95517 ABAA PCZZA Ed.01

4.2 Deleting call barring

From the tools listed in section 3.1, you can delete:
a single existing subscription if it is no longer needed, using the 8650 SDM
GUI or CORBA methods.
several existing subscriptions if they are no longer needed, using mass man-
agement.
If you delete:
a Basic subscription (at S UB _OAM_B asi cS ubscri p ti on subdomain
management level), all attached supplementary services are deleted,
a call barring supplementary service (at S UB _OAM_S up p l ementary -
S er vi ce_C al l B ar r i ng _d el ete subdomain management level), all
attached characteristics are deleted.
To select the subscriber for which you want to perform the operation, enter the
subscriber identity (subscriber profile, IMSI or MSISDN):
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 95 / 204

For more information about... see ...
supplementary services management operations and subdo-

section 3.1.3
mains
tools used to manage supplementary services at the 8650

section 3.1
SDM
96 / 204 3BL 95517 ABAA PCZZA Ed.01

4.3 Copying call barring

From the tools listed in section 3.1, you can copy:
an existing subscription to create a new one with the same characteristics, using
the 8650 SDM GUI or CORBA methods.
After a subscription (or several subscriptions) has (have) been copied, you can
then modify the new subscription(s) to match your operation requirements.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)

section 3.1.3
mains

section 3.1
SDM
modifying call barring section 4.6
3BL 95517 ABAA PCZZA Ed.01 97 / 204

4.4 Displaying call barring information

From the tools listed in section 3.1, you can display parameters and values related
to:
a single existing subscription, using the 8650 SDM GUI or CORBA methods.
several existing subscriptions, using mass management.
Then you can analyze displayed parameters and values, using:

the description of the call barring parameters (see section 3.2),
the On Line Help (OLH) available on 8650 SDM GUI that describes the pos-
sible values.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
98 / 204 3BL 95517 ABAA PCZZA Ed.01

the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 99 / 204

4.5 Listing call barring

The list call barring procedure enables you to list call barring subscriptions with:
all call barring parameters,
only requested call barring parameters.
From the tools listed in section 3.1, you can list call barring subscriptions using a
search based on criteria you define according to your requirements.
These criteria can include:
parameter(s),
parameter value(s),
logic operators:
AND: match on all criteria,
OR: match on only one criteria,
NOT: no match on criteria,
Present: match on the criterion occurrence,
Equal: match on the criterion value,
Greater than: match on value(s) greater than the criterion value,
Less than: match on value(s) less than the criterion value.
You can also combine these criteria for a more accurate search.
a description of each call barring subscription parame-

section 3.2
ter
the On Line Help

possible values for parameters (OLH) available on
8650 SDM GUI
Prerequisite(s) If you list:

a Basic subscription (at S UB _OAM_B asi cS ubscri p ti on_query subdo-
main management level), all attached supplementary services are listed,
a call barring supplementary service (at S UB _OAM_S up p l ementary -
S ervi ce_C allBarri ng _query subdomain management level), all
attached call barring characteristics are listed.
You use the subscriber identity (DN-subscriber profile) to select the subscriber(s)
for which you want to perform the operation.
Key procedure To list call barring:

100 / 204 3BL 95517 ABAA PCZZA Ed.01

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
2. Set parameters to be used as selection criteria:
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
callBarringPassword
msCBAbility
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
3. End.
3BL 95517 ABAA PCZZA Ed.01 101 / 204

the On Line
Help (OLH)
available on
8650 SDM GUI
102 / 204 3BL 95517 ABAA PCZZA Ed.01

4.6 Modifying call barring

The modify call barring procedure enables you to:
provision or withdraw call barring services to a subscriber,
activate new outgoing/incoming call barring services,
modify call barring options,
deactivate a call barring service for a mobile subscriber.

created.
You can modify call barring services from the S UB _OAM_S up p lemen-
tary S ervi ce_C al l B arri ng _mod i f y subdomain.
Key procedure To modify call barring:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 103 / 204

If call barring SS... then...
does not exist create call barring
exists modify call barring
3. Set the msC B Abi l i ty that enables the UE to modify call barring services.
Set parameter(s)...
msC B Abi l i ty
4. Set the cal l B ar r i ng P assw or d to enable modification.
Set parameter(s)...
cal lB arri ng Passw ord
5. Set optional parameters related to call barring SS:
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
6. End.
104 / 204 3BL 95517 ABAA PCZZA Ed.01

the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 105 / 204

106 / 204 3BL 95517 ABAA PCZZA Ed.01

5 Call Forwarding key procedures
Call Forwarding (CF):
Provisioning call forwarding (see section 5.1),
Deleting call forwarding (see section 5.2),
Copying call forwarding (see section 5.3),
Displaying call forwarding information (see section 5.4),
Listing call forwarding (see section 5.5),
Modifying call forwarding (see section 5.6).
3BL 95517 ABAA PCZZA Ed.01 107 / 204

5.1 Provisioning call forwarding

To provision call forwarding to a subscription you use the create operation. The
provision call forwarding procedure enables you to:
provide call forwarding services for a mobile CS subscriber,
activate call forwarding services,
initialize call forwarding options.

vi ce subdomain, for a given subscriber, a CS subscription has been created.
To create a CS subscription, see the Alcatel-Lucent 8650 SDM, SDM Subscrip-
tion Management Operator guide, SDMSUBOPG.
You can provision call forwarding services from the S UB _OAM_S up p l e-
mentary S ervi ce_C al l Forw ard i ng _create subdomain.
Key procedure To provision call-forwarding:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
108 / 204 3BL 95517 ABAA PCZZA Ed.01

If call forwarding SS... then...
does not exist create call forwarding
exists modify call forwarding
3. Set the mandatory parameter for call forwarding ty p eOf C allForw ard -
i ng Li st
Set parameter(s)...
ty p eOf C al l Forw ard i ng Li st
4. Set optional parameters related to call forwarding SS:
Set parameter(s)...
destinationProfile
msCFNoAbility
cfuCallForwardingNumberList
cfbusyCallForwardingNumberList
cfnreplyCallForwardingNumberList
cfnreachCallForwardingNumberList
cfdCallForwardingNumberList
allCallForwardingNumberList
cfdcfbusyCallForwardingNumberlist
cfdcfnreachCallForwardingNumberlist
cfdcfnreplyCallForwardingNumberlist
cfnreplyNotifToFwdPartyFlag
cfnreachNotifToFwdPartyFlag
cfbusyNotifToCallingPartyFlag
cfnreplyNotifToCallingPartFlag
cfnreachNotifToCallingPartFlag
5. End.
3BL 95517 ABAA PCZZA Ed.01 109 / 204

the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for call forwarding services section 3.3
110 / 204 3BL 95517 ABAA PCZZA Ed.01

5.2 Deleting call forwarding

agement.
If you delete:
a call forwarding supplementary service (at S UB _OAM_S up p l ementary -
S ervi ce_C allForw ard i ng _d elete subdomain management level), all
attached characteristics are deleted.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 111 / 204


section 3.1.3
mains

section 3.1
SDM
112 / 204 3BL 95517 ABAA PCZZA Ed.01

5.3 Copying call forwarding

After one or more subscriptions have been copied, you can then modify the new
subscription(s) to match your operation requirements.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)

section 3.1.3
mains

section 3.1
SDM
3BL 95517 ABAA PCZZA Ed.01 113 / 204

5.4 Displaying call forwarding information

to:

the description of the call forwarding parameters (see section 3.3),
sible values.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
114 / 204 3BL 95517 ABAA PCZZA Ed.01

the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 115 / 204

5.5 Listing call forwarding

The list call forwarding procedure enables you to list call forwarding subscriptions
with:
all call forwarding parameters,
only requested call forwarding parameters.
From the tools listed in section 3.1, you can list call forwarding subscriptions using
a search based on criteria you define according to your requirements.
parameter(s),
parameter value(s),
logic operators:
a description of each call forwarding subscription pa-

section 3.3
rameter
the On Line Help

8650 SDM GUI

a call forwarding supplementary service (at S UB _OAM_S up p l ementary -
S ervi ce_C al l Forw ard i ng _query subdomain management level), all
attached call forwarding characteristics are listed.
116 / 204 3BL 95517 ABAA PCZZA Ed.01

Key procedure To list call-forwarding:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 117 / 204

Set parameter(s)...
destinationProfile
notif flags
destinationProfile
msCfNoAbility
3. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
118 / 204 3BL 95517 ABAA PCZZA Ed.01

5.6 Modifying call forwarding

The modify call forwarding procedure enables you to:
provision or withdraw call forwarding services to a subscriber,
activate new call forwarding services,
modify call forwarding options.
deactivate a call forwarding service for a mobile subscriber.

created.
You can modify call forwarding services from the S UB _OAM_S up p lemen-
tary S ervi ce_C allForw ard i ng _mod i f y subdomain.
Key procedure To modify call-forwarding:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 119 / 204

If call forwarding SS... then...
does not exist create call forwarding
exists modify call forwarding
3. Set the msC f NoAbi l i ty that enables the UE to modify call forwarding
services.
Set parameter(s)...
msC f NoAbi l i ty
Set parameter(s)...
destinationProfile
typeOfCallForwardingList
5. End.
120 / 204 3BL 95517 ABAA PCZZA Ed.01

the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 121 / 204

122 / 204 3BL 95517 ABAA PCZZA Ed.01

6 GCS key procedures
General Call Services (GCS):
Provisioning GCS (see section 6.1),
Deleting GCS (see section 6.2),
Copying GCS (see section 6.3),
Displaying GCS information (see section 6.4),
Listing GCS (see section 6.5),
Modifying GCS (see section 6.6).
3BL 95517 ABAA PCZZA Ed.01 123 / 204

6.1 Provisioning GCS

To provision GCS to a subscription you use the create operation. The provision
GCS procedure enables you to:
provide GCS for a mobile subscriber,
activate GCS services,
initialize GCS options.

created.
Subscription Management Operator guide, SDMSUBOPG.
You can provision general call services from the S UB _OAM_S up p lemen-
tary S ervi ce_GC S _create subdomain.
Key procedure To provision GCS:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
124 / 204 3BL 95517 ABAA PCZZA Ed.01

If GCS SS... then...
does not exist create GCS
exists modify GCS
3. Set optional parameters related to GCS supplementary services:
3BL 95517 ABAA PCZZA Ed.01 125 / 204

Set parameter(s)...
colpProvisionedFlag
clipProvisionedFlag
clirProvisionedFlag
presentationMode
mptyProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
maliciousCallProvisionedFlag
osss1ProvisionedFlag
osss1ActivationFlag
osss2ActivationFlag
osss3ActivationFlag
osss4ActivationFlag
osss5ActivationFlag
osss6ActivationFlag
osss7ActivationFlag
osss8ActivationFlag
osss9ActivationFlag
Optional parameters related to GCS supplementary services (continued):
126 / 204 3BL 95517 ABAA PCZZA Ed.01

Set parameter(s)...
osss10ActivationFlag
cnapProvisionedFlag
4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for GCS section 3.4
3BL 95517 ABAA PCZZA Ed.01 127 / 204

6.2 Deleting GCS

agement.
If you delete:
a GCS supplementary service (at S UB _OAM_S up p l ementary -
S ervi ce_GC S _d el ete subdomain management level), all attached
characteristics are deleted.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
128 / 204 3BL 95517 ABAA PCZZA Ed.01


section 3.1.3
mains

section 3.1
SDM
3BL 95517 ABAA PCZZA Ed.01 129 / 204

6.3 Copying GCS

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)

section 3.1.3
mains

section 3.1
SDM
130 / 204 3BL 95517 ABAA PCZZA Ed.01

6.4 Displaying GCS information

to:

the description of the GCS parameters (see section 3.4),
sible values.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 131 / 204

the On Line
Help (OLH)
available on
8650 SDM GUI
132 / 204 3BL 95517 ABAA PCZZA Ed.01

6.5 Listing GCS

The list GCS procedure enables you to list GCS subscriptions with:
all GCS parameters,
only requested GCS parameters.
From the tools listed in section 3.1, you can list GCS subscriptions using a search
based on criteria you define according to your requirements.
parameter(s),
parameter value(s),
logic operators:
a description of each GCS subscription parameter section 3.4
the On Line Help

8650 SDM GUI

a GCS supplementary service (at S UB _OAM_S up p l ementary S er-
vi ce_GC S _query subdomain management level), all attached GCS
characteristics are listed.
3BL 95517 ABAA PCZZA Ed.01 133 / 204

Key procedure To list GCS:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
134 / 204 3BL 95517 ABAA PCZZA Ed.01

Set parameter(s)...
colpProvisionedFlag
clipProvisionedFlag
clirProvisionedFlag
presentationMode
mptyProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
osss1ActivationFlag
osss2ActivationFlag
osss3ActivationFlag
osss4ActivationFlag
osss5ActivationFlag
osss6ActivationFlag
osss7ActivationFlag
osss8ActivationFlag
osss9ActivationFlag
3BL 95517 ABAA PCZZA Ed.01 135 / 204

Set parameter(s)...
cnapProvisionedFlag
3. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
136 / 204 3BL 95517 ABAA PCZZA Ed.01

6.6 Modifying GCS

The modify GCS procedure enables you to:
provision or withdraw GCS to/from a subscriber,
activate new GCS services,
modify GCS options,
deactivate a GCS service for a mobile subscriber.

created.
You can modify GCS services from the S UB _OAM_S up p l ementary S er-
vi ce_GC S _mod i f y subdomain.
Key procedure To modify GCS:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 137 / 204

If GCS SS... then...
does not exist create GCS
exists modify GCS
138 / 204 3BL 95517 ABAA PCZZA Ed.01

Set parameter(s)...
colpProvisionedFlag
clipProvisionedFlag
clirProvisionedFlag
presentationMode
mptyProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
osss1ActivationFlag
osss2ActivationFlag
osss3ActivationFlag
osss4ActivationFlag
osss5ActivationFlag
osss6ActivationFlag
osss7ActivationFlag
osss8ActivationFlag
osss9ActivationFlag
3BL 95517 ABAA PCZZA Ed.01 139 / 204

Parameters to set up
cnapProvisionedFlag
4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
140 / 204 3BL 95517 ABAA PCZZA Ed.01

7 CUG key procedures
Closed User Group (CUG):
Provisioning CUG (see section 7.1),
Deleting CUG (see section 7.2),
Copying CUG (see section 7.3),
Displaying CUG information (see section 7.4),
Listing CUG (see section 7.5),
Modifying CUG (see section 7.6).
3BL 95517 ABAA PCZZA Ed.01 141 / 204

7.1 Provisioning CUG

To provision CUG to a subscription you use the create operation. The provision
CUG procedure enables you to:
provide CUG services for a mobile subscriber,
activate CUG services,
initialize CUG options.

tion management Operator guide, SDMSUBOPG.
You can provision CUG services from the S UB _OAM_S up p l ementary -
S ervi ce_C ug _create subdomain.
Key procedure To provision CUG:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
142 / 204 3BL 95517 ABAA PCZZA Ed.01

If CUG SS... then...
does not exist create CUG
exists modify CUG
3. Set optional parameters related to CUG:
3BL 95517 ABAA PCZZA Ed.01 143 / 204

Set parameter(s)...
cugInterlockCodeInd1
intraCugOptionInd1
intraCugOptionInd2
intraCugOptionInd3
intraCugOptionInd4
intraCugOptionInd5
intraCugOptionInd6
intraCugOptionInd7
intraCugOptionInd8
intraCugOptionInd9
intraCugOptionInd10
AllassociatedBsgString1
prefCugIndexForFax
interCugRestForFax
144 / 204 3BL 95517 ABAA PCZZA Ed.01

4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for CUG services section 3.5
3BL 95517 ABAA PCZZA Ed.01 145 / 204

7.2 Deleting CUG

agement.
If you delete:
a CUG supplementary service (at S UB _OAM_S up p l ementary -
S ervi ce_C ug _d el ete subdomain management level), all attached
characteristics are deleted.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
146 / 204 3BL 95517 ABAA PCZZA Ed.01


section 3.1.3
mains

section 3.1
SDM
3BL 95517 ABAA PCZZA Ed.01 147 / 204

7.3 Copying CUG

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)

section 3.1.3
mains

section 3.1
SDM
148 / 204 3BL 95517 ABAA PCZZA Ed.01

7.4 Displaying CUG information

to:

the description of the CUG parameters (see section 3.5),
sible values.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 149 / 204

the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for CUG section 3.5
150 / 204 3BL 95517 ABAA PCZZA Ed.01

7.5 Listing CUG

The list CUG procedure enables you to list CUG subscriptions with:
all CUG parameters,
only requested CUG parameters.
From the tools listed in section 3.1, you can list CUG subscriptions using a search
parameter(s),
parameter value(s),
logic operators:
a description of each CUG subscription parameter section 3.5
the On Line Help

8650 SDM GUI

a CUG supplementary service (at S UB _OAM_S up p l ementary S er-
vi ce_C ug _query subdomain management level), all attached GCS
3BL 95517 ABAA PCZZA Ed.01 151 / 204

Key procedure To list CUG:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
2. Set optional parameters related to CUG supplementary services:
152 / 204 3BL 95517 ABAA PCZZA Ed.01

Set parameter(s)...
prefCugIndexForFax
3. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 153 / 204

7.6 Modifying CUG

The modify CUG procedure enables you to:
provision or withdraw CUG to/from a subscriber,
activate new CUG services,
modify CUG options,
deactivate a CUG service for a mobile subscriber.

created.
You can modify CUG services from the S UB _OAM_S up p l ementary S er-
vi ce_C ug _mod i f y subdomain.
Key procedure To modify CUG:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
154 / 204 3BL 95517 ABAA PCZZA Ed.01

If CUG SS... then...
does not exist create CUG
exists modify CUG
3. Set optional parameters related to CUG supplementary services:
3BL 95517 ABAA PCZZA Ed.01 155 / 204

Set parameter(s)...
intraCugOptionInd1
intraCugOptionInd2
intraCugOptionInd3
intraCugOptionInd4
intraCugOptionInd5
intraCugOptionInd6
intraCugOptionInd7
intraCugOptionInd8
intraCugOptionInd9
intraCugOptionInd10
prefCugIndexForFax
interCugRestForFax
156 / 204 3BL 95517 ABAA PCZZA Ed.01

4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
3BL 95517 ABAA PCZZA Ed.01 157 / 204

158 / 204 3BL 95517 ABAA PCZZA Ed.01

8 eMLPP key procedures
the enhanced Multi-Level Precedence and Pre-emption (eMLPP) service:
Provisioning eMLPP (see section 8.1),
Deleting eMLPP (see section 8.2),
Copying eMLPP (see section 8.3),
Displaying eMLPP information (see section 8.4),
Listing eMLPP (see section 8.5),
Modifying eMLPP (see section 8.6).
3BL 95517 ABAA PCZZA Ed.01 159 / 204

8.1 Provisioning eMLPP

Use the create operation to provide a subscriber with eMLPP service. The eMLPP
provisioning procedure enables you to activate and initialize the eMLPP service.
tion management Operator guide, SDMSUBOPG.
You can provide a subscriber with the eMLPP service from the
S UB _OAM_S up p l ementary S ervi ce_eMLPP_C reate subdomain.
An eMLPP management session is open.
Key procedure To provide a subscriber with eMLPP:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN
Set parameter(s)...
CountryCodeId (CC)
160 / 204 3BL 95517 ABAA PCZZA Ed.01

If eMLPP SS... then...
does not exist create eMLPP
exists modify eMLPP
3. Set optional parameters related to eMLPP:
Set parameter(s)...
emlppMaximumEntitledPriority
4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for eMLPP services section 3.6
3BL 95517 ABAA PCZZA Ed.01 161 / 204

8.2 Deleting eMLPP

a single existing subscription, if it is no longer needed, using the 8650 SDM
several existing subscriptions, if they are no longer needed, using mass man-
agement.
If you delete:
management level), all attached supplementary services are deleted.
an eMLPP supplementary service (at S UB _OAM_S up p l ementary S er-
vi ce_eMLP P_Del ete subdomain management level), all attached charac-
teristics are deleted.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN:
Set parameter(s)...
CountryCodeId (CC)
162 / 204 3BL 95517 ABAA PCZZA Ed.01


section 3.1.3
mains

section 3.1
SDM
3BL 95517 ABAA PCZZA Ed.01 163 / 204

8.3 Copying eMLPP

From the tools listed in section 3.1, you can copy an existing subscription to create
a new one with the same characteristics, using the 8650 SDM GUI or CORBA
methods.
After a subscription (or several subscriptions) has (have) been copied, you can
then modify the new subscription(s) to match your operation requirements.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN:
Set parameter(s)...
CountryCodeId (CC)

section 3.1.3
mains

section 3.1
SDM
modifying eMLPP section 8.6
164 / 204 3BL 95517 ABAA PCZZA Ed.01

8.4 Displaying eMLPP information

to:

the description of the eMLPP parameters (see section 3.6),
sible values.
Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN:
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 165 / 204

the On Line
Help (OLH)
available on
8650 SDM GUI
166 / 204 3BL 95517 ABAA PCZZA Ed.01

8.5 Listing eMLPP

The eMLPP list procedure enables you to list eMLPP subscriptions with:
all eMLPP parameters,
requested eMLPP parameters only.
From the tools listed in section 3.1, you can list eMLPP subscriptions using a search
parameter(s),
parameter value(s),
logic operators:
NOT: match on no criteria,
a description of each eMLPP subscription parameter section 3.6
the On Line Help

8650 SDM GUI

an eMLPP supplementary service (at S UB _OAM_S up p l ementary S er-
vi ce_eMLP P_Query subdomain management level), all attached eMLPP
Use the subscriber identity (DN-subscriber profile) to select the subscriber(s) for
which you want to perform the operation.
Key procedure To list eMLPP:

3BL 95517 ABAA PCZZA Ed.01 167 / 204

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN:
Set parameter(s)...
CountryCodeId (CC)
2. Set parameters to be used as selection criteria:
Set parameter(s)...
emlppProvisionedFlag
3. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
168 / 204 3BL 95517 ABAA PCZZA Ed.01

8.6 Modifying eMLPP

The eMLPP modify procedure enables you to modify eMLPP options.
created.
You can modify an eMLPP service from the S UB _OAM_S up p l ementary -
S ervi ce_eMLPP _Mod i f y subdomain.
An eMLPP management session is open.
Key procedure To modify eMLPP:

Set parameter(s)...
Using IMSI:
Set parameter(s)...
Using Main MSISDN:
Set parameter(s)...
CountryCodeId (CC)
3BL 95517 ABAA PCZZA Ed.01 169 / 204

If eMLPP SS... then...
does not exist create eMLPP
exists modify eMLPP
3. Set optional parameters related to eMLPP SS:
Set parameter(s)...
emlppMaximumEntitledPriority
4. End.
the On Line
Help (OLH)
available on
8650 SDM GUI
parameters for eMLPP service section 3.6
170 / 204 3BL 95517 ABAA PCZZA Ed.01

9 Interactions between supplementary services
This section describes the conditions governing the use of supplementary services.
Use of supplementary services are dependent on:
the compatibility of the supplementary service with the BSGs subscribed to by
the subscriber,
the compatibility of a supplementary service with:
system functions,
other supplementary services already subscribed to by the subscriber,
IN services,
CAMEL services.
Note: Supplementary services could be:

active and operative when there is no reason of quiescence,
active and quiescent when there is one or more reasons of quiescence.
3BL 95517 ABAA PCZZA Ed.01 171 / 204

9.1 Supplementary services and BSG applicability

Table 7 describes the applicability of the supplementary services according to the
BSGs subscribed to by the subscriber.
Note: No supplementary service is applicable to services.
Table 7: Applicability of supplementary services to BSGs
Supplemen- BSG
tary service
Speech call SMS FAX Asynchronous Synchronous
Data Data
Transmission Transmission
(BSG20 ) (BSG30)
CFU (1)
CFB (1)
CFNRy (1)
CFNRc (1)
PCD (1)
CFD (1)
BAOC (1) (2)
BOIC (1) (2)
BOIC-exHC (1) (2)
BAIC (1) (3)
BIC-Roam (1) (3)
COLP
COLR
CLIP
CLIR
MCI
HOLD (1)
CW (1)
ECT (1)
MPTY (1)
AOCI (1)
AOCC (1)
172 / 204 3BL 95517 ABAA PCZZA Ed.01

Supplemen- BSG
tary service
Speech call SMS FAX Asynchronous Synchronous
Data Data
Transmission Transmission
(BSG20 ) (BSG30)
CUG (1)
eMLPP
OSSS (4) (4) (4) (4) (4)
Note: (1): Not applicable to emergency calls (TS12).

(2): Applicable to the Short Message Service-Mobile Originated (SMS-MO).
(3): Applicable to the Short Message Service-Mobile Terminated (SMS-MT).
(4): Applicable according to the operator.
3BL 95517 ABAA PCZZA Ed.01 173 / 204

9.2 Interactions between system functions and supple-

mentary services
The system functions that affect supplementary services are:
Operator Determined Barring (ODB),
Hot Billing (HB).
9.2.1 ODB and supplementary services

ODB is an optional function available to you. ODB enables you to restrict the
capabilities of a subscriber to:
make and receive calls,
roam,
register FTNs,
etc.
ODB involves interactions with the following supplementary services:

call forwarding,
call barring,
call hold,
explicit call transfer,
closed user group.
ODB and call forwarding The interactions between ODB and call forwarding services, applicable to a sub-
services scriber, are:
An ODB restriction entered by you that conflicts with a call forwarding service
already registered causes the service to switch to quiescent mode,
A request from the subscriber concerning a call forwarding service that conflicts
with an ODB restriction will result in a reject of the call forwarding request,
Deletion of an ODB restriction will make call forwarding services, previously
set to the quiescent mode by ODB, active and operative again provided no
interaction with other supplementary services prevents this from occurring,
Provided that there is no ODB restriction or interaction restriction with other
supplementary services, a subscriber can:
activate a CF service,
deactivate a CF service,
withdraw a CF service,
register an FTN.
If there is an existing call forwarding program which is in contravention with a

given ODB category, the setting of ODB will result most of the time in making CF
quiescent.
Table 8 lists quiescent rules between ODB and CF.
174 / 204 3BL 95517 ABAA PCZZA Ed.01

Table 8: Quiescent rules between ODB and CF
ODB category CFU or CFC quiescent state
ODBOC / CFU and CFC None.

ODBFN / ODBIC
In all cases CFU and CFC are put in
quiescent state
ODBOIC / CFU MCC of FTN != MCC of HPLMN

ODBFNI
CFC MCC of FTN != MCC of VPLMN
ODBOIEH / CFU MCC of FTN != MCC of HPLMN

ODBFNIEH
CFC MCC of FTN != MCC of VPLMN or
HPLMN
ODBOROH CFU and CFC MCC of VPLMN != MCC of HPLMN
ODBIRO CFU and CFC MCC of VPLMN != MCC of HPLMN
ODBIRZ CFU and CFC WZN!= Zone of HPLMN
ODBOIZ / CFU WZN != Zone of HPLMN

ODBFNZ
CFC WZN != Zone of VPLMN
ODBOZEH / CFU WZN != Zone of HPLMN

ODBFNZEH
CFC WZN = Zone of VPLMN or MCC of
FTN = MCC of HPLMN
ODBOIHZ CFU MCC of FTN != MCC of HPLMN
CFC WZN != Zone of VPLMN or MCC of

FTN = MCC of HPLMN and VPLMN
ODB and call barring The network always performs a check on ODB restrictions first before performing
services the check on subscriber-determined call barring services.
The network accepts the activation (or deactivation) by the subscriber of a call bar-
ring service, provided no ODB restriction or interaction with other supplementary
services is applied to the subscriber.
ODB and HOLD The network rejects a request from the subscriber to place a call on hold if an
ODB restriction on the HOLD service is applied to the subscriber.
ODB and ECT The network rejects an ECT request from a subscriber if an ODB restriction on the
ECT service is applied to the subscriber.
Depending on a functional option, when ODB of ECT is applied to a subscriber
with the ECT service provisioned, if the subscriber is roaming in an FPLMN that
supports ECT but not ODB of ECT, either:
3BL 95517 ABAA PCZZA Ed.01 175 / 204

the HLR/AuC applies a Roaming Restriction Due to Unsupported Feature, or,

the HLR/AuC accepts the location update procedure without the possibility of
invoking the ECT service.
When an ECT call is in progress between two parties, new ODB restrictions can
affect the ECT call. The network can release the call between these two parties if
the UE with the ECT service has not changed MSCs.
ODB and CUG The network always performs a check on ODB restrictions first before performing
the check on CUG restrictions.
9.2.2 HB and CFU

The HB category can only be used with the CFU service if the HB CDR at GMSC
option is active.
176 / 204 3BL 95517 ABAA PCZZA Ed.01

9.3 Interactions between supplementary services

This section describes the restrictions on the use of supplementary services accord-
ing to the supplementary services already activated. Depending on the systems
checks on the interactions between supplementary services, the outcome of these
checks may result in the acceptance or rejection of the service activation.
9.3.1 Interactions between call forwarding services

Table 9 gives the options for activation of a call forwarding service according to
the activation of another call forwarding service assigned to a subscriber for a
given BSG.
Table 9: Call forwarding service activation compatibility
Active Service to be activated

service
CFU CFNRE- CFN- CFBUSY CFD

PLY REACH
CFU
CFNRE- (1) (2) (2) (3)

PLY
CFN- (1) (2) (2) (3)

REACH
CFBUSY (1) (2) (2) (3)
CFD (4)
Note: (1): Following activation of the CFU service, the conditional call forwarding service
that was previously activated switches to quiescent mode. Deactivation of the CFU
service changes the conditional call forwarding service back to active status.
(2): Service can be active if the CFU service is inactive.
(3): The CFD service can be activated if the conditional call forwarding service is
inactive.
(4): Activation of the CFU service replaces the CFC service in quiescent mode.
Deactivation of the CFU service returns the CFC service to the active state.
9.3.2 Interactions between call barring services

For a given BSG, only one outgoing call barring service (BAOC, BOIC or BOIC-
exHC) can be active at the same time.
Similarly, for a given BSG, only one incoming call barring service (BAIC or BIC-
Roam) can be active at the same time.
When an outgoing call barring service is active for a subscriber, the activation of
a second outgoing call barring service will cause deactivation of the outgoing call
barring service currently activated.
Similarly, any active incoming call barring service will be deactivated when a sec-
ond incoming call barring service is activated for the same subscriber.
3BL 95517 ABAA PCZZA Ed.01 177 / 204

9.3.3 Interactions between call forwarding and call barring services

Table 10 lists the call forwarding services that you can activate when a call barring
service is already activated.
Call forwarding activation An FTN is national:

for the CFU service, when the country of the FTN is the HPLMN country of the
subscriber having calls forwarded,
for the CFBUSY, CFNREPLY and CFNREACH services, when the country of the
FTN is the VPLMN country of the subscriber having calls forwarded.
An FTN is international:
for the CFU service, when the country of the FTN is different from the HPLMN
country of the subscriber having calls forwarded,
for the CFBUSY, CFNREPLY and CFNREACH services, when the country of the
FTN is different from the VPLMN country of the subscriber having calls for-
warded.
Table 10: Activation of call forwarding services according to call barring services activated
Service Service that can be activated

activated
CFU CFBUSY, CFNREPLY, CFNREACH
national FTN international FTN national FTN international
FTN
UE in HPLMN UE outside UE in HPLMN UE outside
HPLMN HPLMN
BAOC
BOIC (4) (2) (2)
BOIC-exHC (2) (2) (3)

(4)
BAIC
BIC-Roam (1) (1)
Note: (1): Activation of the CFU service places the BIC-Roam service in quiescent mode.
(2): If the subscriber roams and the call forwarding service becomes international,
the call forwarding service switches to quiescent mode.
(3): Activation is allowed only where the FTN forwards the calls to the HPLMN
country.
(4): Activation of the CF (CFNREACH,CFBUSY,CFBREPLY) services is allowed only
if BICROAM is in quiescent mode.
(5): If the subscriber is a CAMEL phase 2 subscriber, the interaction checks are
not implemented and activation is allowed.
178 / 204 3BL 95517 ABAA PCZZA Ed.01

Call barring activation Table 11 lists the call barring services that can be activated when a call forwarding
service is already activated.
Table 11: Activation of call barring according to call forwarding service activated
Service activated Service that can be activated

BAOC BOIC BOIC-exHC BAIC (4) BIC-Roam
(4)
CFU
National FTN
International
FTN
Foreign FTN
3BL 95517 ABAA PCZZA Ed.01 179 / 204

Service activated Service that can be activated

BAOC BOIC BOIC-exHC BAIC (4) BIC-Roam
(4)
CFBUSY
National FTN:
CFNREPLY
CFNREACH (1) (2) (3)
UE in HPLMN
UE outside (1) (2)

HPLMN
International
FTN:
UE in HPLMN (2) (3)
UE outside
HPLMN
Foreign FTN: (2)
UE in HPLMN
UE outside
HPLMN
Note: (1): If subsequently the subscriber roams so that the call forwarding service be-
comes international, the call forwarding service switches to quiescent mode.
(2): CB request is allowed. If subsequently the subscriber roams so that the call
forwarding service becomes "International or UE outside HPLMN", the call for-
warding service switches to the active standby state and CB becomes quiescent
due to Roaming.
(3): CB request is allowed. If subsequently the subscriber roams outside the
HPLMN, the call forwarding service switches back to the active state and CB be-
comes quiescent due to Roaming.
(4): If the subscriber is a CAMEL phase 2 subscriber, the interaction checks are
not implemented and activation is allowed.
CAMEL subscribers When a CAMEL subscriber located in a VLR that does not support CAMEL services,
and the subscriber is subject to an outgoing call barring service (BAOC, BOIC or
BOIC-exHC), conditional call forwarding (CFNREPLY, CFNREACH, CFBUSY) is not
allowed.
180 / 204 3BL 95517 ABAA PCZZA Ed.01

9.3.4 Interactions between COLP and other supplementary services

The COLP service affects all call forwarding services.
When a call is forwarded:
the identity of the called party is not displayed if the calling party (the subscriber
with the COLP service) has not selected the call forwarding notification option,
if the calling party has selected the call forwarding notification option, the iden-
tity of the called party is different from the number dialed by the calling party.
3BL 95517 ABAA PCZZA Ed.01 181 / 204

9.3.5 Interactions between CLIP and other supplementary services

The CLIP service affects the following supplementary services:
CLIR,
CW.
CLIP and call forwarding If the subscriber receiving a forwarded call has subscribed to the CLIP service,
depending on the option selected on assignment of the call forwarding service,
the identity displayed is:
the identity of the calling subscriber, if this subscriber has not subscribed to the
CLIR service,
or,
the identity of the forwarding subscriber.
When the calling party has subscribed to the CLIR service, calling party identity
is presented to the call forwarding recipient if this subscriber has the CLIP service
with the calling line identification restriction override option.
CLIP and CLIR In normal operation, CLIR takes priority over CLIP.
CLIP can take priority over CLIR when the subscriber with the CLIP service also has
the calling line identification restriction override option. This option is reserved for
certain subscribers (police service, fire service, etc.).
CLIP and CW A subscriber who subscribes to CLIP and CW receives the identification of the
calling line in the call waiting indication message if:
the calling subscriber has not subscribed to the CLIR service,
the calling subscriber has subscribed to the CLIR service and the called sub-
scriber has the CLIR override option.
9.3.6 Interactions between CLIR and other supplementary services

The CLIR service affects the following supplementary services:
call forwarding,
CLIP.
CLIR and call forwarding When the calling party has subscribed to the CLIR service, calling party identity
is presented to the call forwarding recipient if this subscriber has the CLIP service
with the CLIR override option.
When the subscriber forwarding the calls has the CLIP service, the identity of the
forwarding subscriber is presented in a restricted way to the call forwarding re-
cipient if:
the subscriber receiving the forwarded calls has the CLIP service,
182 / 204 3BL 95517 ABAA PCZZA Ed.01

for the forwarded section of the call, the number of the forwarding subscriber
is transmitted as the number of the calling subscriber.
CLIR and CLIP See section 9.3.5.
CLIR and CNAP See section 9.3.11.
9.3.7 Interactions between HOLD and other supplementary services

The HOLD service affects the CW supplementary service.
If a subscriber has a call on hold and an active call, a new incoming call is pre-
sented as a waiting call, provided that no other call is waiting.
When a subscriber has a call on hold and no active call, a new incoming call is
presented as a waiting call, provided that no other call is waiting.
9.3.8 Interactions between CW and other supplementary services

The CW service affects the following supplementary services:
call forwarding: CFU, CFBUSY, CFNREPLY,
call barring: BAIC, BIC-Roam,
CLIP,
HOLD.
CW and CFU The CFU service, if activated, has priority over the CW service.
Activation of the CFU service when a call is waiting does not change the state of
the waiting call.
CW and CFBUSY On receipt of an incoming call, if the called subscriber is busy (traffic channel
assigned) and no call is waiting, the CFBUSY service is implemented if it is active
and applicable. The new incoming call is not presented to the called subscriber.
CW and CFNREPLY When an incoming call is presented to a subscriber as a call waiting, the CFNRE-
PLY service is implemented if the subscriber does not accept the waiting call before
the no-reply timer times out.
CW and BAIC The BAIC service, when activated, has priority over the CW service. The CW ser-
vice cannot be invoked when the BAIC service is active.
Activation of the BAIC service when a call is waiting does not change the state of
the waiting call.
3BL 95517 ABAA PCZZA Ed.01 183 / 204

CW and BIC-Roam The BIC-Roam service, when activated, has priority over the CW service. The CW
service cannot be invoked when the BIC-Roam service is activated.
Activation of the BIC-Roam service when a call is waiting does not change the
state of that call.
CW and CLIP See section 9.3.5.
CW and HOLD See section 9.3.7
CLIR and CNAP See section 9.3.11.
9.3.9 Interactions between ECT and other supplementary services

The ECT service affects the following supplementary services:
call forwarding services: CFBUSY, CFNREPLY.
general supplementary services: COLP, COLR, CLIP, CLIR, HOLD, AOCI,
AOCC and MPTY.
the CUG service.
ECT and call forwarding In an ECT request, when one of the parties forwards the transferred call (using the
CFBUSY or CFNREPLY service), the identity of the second party received in the ECT
notification is presented to the call forwarding recipient as the calling line identity.
ECT and COLP A party involved in the ECT service who subscribes to the COLP service is presented
with the identity of the second party if the second party does not subscribe to the
COLR service.
ECT and COLR The identity of a party involved in the ECT service who subscribes to the COLR
service is presented to the second party if the second party has the COLP service
with the COLR override option.
ECT and CLIP A party involved in the ECT service who subscribes to the CLIP service is presented
with the identity of the second party if the second party does not subscribe to the
CLIR service.
ECT and CLIR The identity of a party involved in the ECT service who subscribes to the CLIR
service is presented to the second party if the second party has the CLIP service
with the calling line identification restriction override option.
184 / 204 3BL 95517 ABAA PCZZA Ed.01

ECT and HOLD You cannot withdraw the HOLD service from a subscriber who is assigned the ECT
service.
ECT and AOCI The simultaneous assignment of the ECT and AOCI service is possible only if al-
lowed by the associated ECT functional option.
ECT and AOCC The simultaneous assignment of the ECT and AOCC service is possible only if
allowed by the associated ECT functional option.
ECT and MPTY A subscriber cannot transfer a conference call.
ECT and CUG Subscribers involved in the ECT service must belong to the same CUG.
9.3.10 Interactions between MPTY and other supplementary services

The MPTY service affects the following general supplementary services:
CLIP,
HOLD,
ECT.
MPTY and CLIP When the subscriber controlling the conference call adds an additional subscriber
to the call, the identity of that subscriber is not presented to the other parties, even
if the other parties have subscribed to the CLIP service.
MPTY and HOLD Any subscriber who participates in a conference call can place a call on hold.
The HOLD service cannot be withdrawn from a subscriber who is assigned the
MPTY service.
MPTY and ECT See section 9.3.9.
9.3.11 Interactions between CNAP and other supplementary services

The CNAP service affects the following general supplementary services:
CLIR,
CFU,
CFB,
CFNRy,
CFNRc,
3BL 95517 ABAA PCZZA Ed.01 185 / 204

CW.
CNAP and CLIR The CLIR supplementary service takes precedence over the CNAP supplementary
service, unless the called user has an override category. In case of the latter, it is
assumed that the override category for name information has been set so that the
name information is presented to the called user. The Calling Line Identification
Restriction (CLIR) information is used to restrict the delivery of the calling name to
the called subscriber. That is, if the calling party has activated CLIR, then, instead
of the calling name, a privacy indication is provided to the called subscriber, which
may be a visual display indicating private (or Restricted) name. This method
of restricting calling name must not restrict the use or implementation of other
calling name restriction methods when the calling party is a fixed subscriber. These
methods used by fixed subscribers are outside the scope of this specification.
CNAP and CFU For an incoming call to a subscriber with both CNAP and Call Forwarding Un-
conditional (CFU) activated, the calling party name information is not displayed
at the forwarding subscribers terminal. When a call has been forwarded and
the forwarded-to user has been provided with the CNAP supplementary service,
the forwarded-to user receives the name of the original calling party, if the calling
party has not subscribed to or invoked the CLIR supplementary service.
CNAP and CFB Network Determined User Busy (NDUB)

Same as the interaction with Call Forwarding Unconditional.
User Determined User Busy (UDUB)

Same as the interaction with Call Forwarding No Reply.
CNAP and CFNRy For an incoming call to a subscriber with both CNAP and Call Forwarding on No
Reply (CFNRy) activated, the calling party name information is displayed by the
predefined time while the call is alerting.
CNAP and CFNRc Same as the interaction with Call Forwarding Unconditional (CFU).
CNAP and CW If the served mobile subscriber is provisioned with the CNAP service, the calling
party name information is displayed to the subscriber in the notification of an
incoming (waiting) call similar to a normal incoming call.
9.3.12 Interactions between CUG and other supplementary services

The CUG service affects the following supplementary services:
general supplementary services: CW, ECT, and MPTY.
186 / 204 3BL 95517 ABAA PCZZA Ed.01

CUG and call forwarding The calling party is a CUG subscriber not allowed to make calls outside the
services CUG (CUG call with no outgoing access (OA) indication), and the called party
(with the call forwarding service) is:
a CUG subscriber allowed to make outgoing calls within the CUG: after
checking that the CUG interlock code matches for each of the subscribers,
call forwarding is allowed.
a CUG subscriber not allowed to make outgoing calls within the CUG: call
forwarding is rejected.
The calling party is a CUG subscriber allowed to make calls outside the CUG
(CUG call with outgoing access (OA) indication), and the called party (with the
call forwarding service) is:
a CUG subscriber allowed only to make outgoing calls within the CUG:
after checking that the CUG interlock code matches for each of the sub-
scribers, call forwarding is allowed.
a CUG subscriber not allowed to make outgoing calls within and outside
the CUG: call forwarding is rejected.
a CUG subscriber allowed to make outgoing calls within and outside the
CUG: after checking that the CUG interlock code matches for each of the
subscribers, call forwarding is allowed.
a CUG subscriber allowed only to make outgoing calls outside the CUG:
after checking that the CUG interlock code matches for each of the sub-
scribers, call forwarding is allowed.
a CUG subscriber allowed to make calls outside the CUG: call forwarding
service is allowed if the CUG interlock code for the calling party is different
from that of the called party.
a CUG subscriber not allowed to make calls outside the CUG: call forward-
ing is rejected if the CUG interlock code for the calling party is different from
that of the called party.
a subscriber not a member of the CUG: call forwarding is allowed.
The calling party is a CUG subscriber, the call forwarding service is:
rejected, when the called party is a CUG subscriber not allowed to make
calls outside the CUG.
allowed, when the called party is a CUG subscriber allowed to make calls
outside the CUG.
CUG and call barring Active call barring services take priority over CUG restrictions.
CUG and CW A CUG call waiting is presented to the subscriber as a CUG call.
CUG and ECT The subscribers involved in an ECT must belong to the same CUG.
CUG and MPTY Multiparty calls must be set up taking into account the CUGs of each of the parties.
3BL 95517 ABAA PCZZA Ed.01 187 / 204

9.3.13 Interactions between AOCC and AOCI

The provisioning of both the AOCC and AOCI services for the same subscriber is
rejected.
188 / 204 3BL 95517 ABAA PCZZA Ed.01

9.4 Interactions with IN services

The Intelligent Network (IN) services affect the following supplementary services:
call forwarding,
call barring
CUG.
9.4.1 Interactions between IN services and call forwarding services

IN services are invoked either before or after a call forwarding service depending
on the IN access mode.
9.4.2 Interactions between IN services and call barring services

For outgoing calls, the IN services are invoked either before or after a call barring
service according to an IN service table.
For incoming calls, the call barring services take priority over the invocation of the
IN services.
9.4.3 Interaction between IN services and CUG

The first IN invocation takes priority over CUG restrictions.
3BL 95517 ABAA PCZZA Ed.01 189 / 204

9.5 Interactions with CAMEL services

CAMEL services affect the following supplementary services:
general supplementary services: CLIP, CLIR, ECT, MPTY, AOCI and AOCC,
the CUG service.
Note: Interactions exist between CAMEL phase 3 services and supplementary services if
the CAMEL phase 3 services are supported by the RCP.
9.5.1 Interactions between CAMEL and call forwarding services

You can apply CAMEL services to any terminating call forwarded by any of the
call forwarding supplementary services. With call forwarding by the GMSC on a
terminating call, call forwarding is triggered after invocation of the terminating
call CAMEL service.
9.5.2 Interactions between CAMEL and call barring services

When the BAOC service is activated, the originating call CAMEL services are not
applicable.
Originating call CAMEL services are invoked before the BOIC and BOIC-exHC
services.
Terminating call CAMEL services are not applicable when the BAIC or BIC-Roam
service is activated.
9.5.3 Interaction between CAMEL and CLIP

A CAMEL service can modify the supplementary designation number (NDS) pre-
sented to the called subscriber as the calling line identity (CLI).
9.5.4 Interaction between CAMEL and CLIR

A CAMEL service can modify the NDS and presentation indicator (PI) of the calling
subscriber without violating the CLIR service of the calling subscriber.
9.5.5 Interactions between CAMEL phase 2 service and ECT

Depending on the subscriber data and the activation of a functional option, a
notification is sent to the Service Control Function (SCF) at the invocation of the
ECT service by the UE.
9.5.6 Interactions between CAMEL phase 2 service and MPTY

Depending on the subscriber data and the activation of a functional option, a
notification is sent to the SCF at the start of the conference call at the invocation
of the ECT service by the UE.
9.5.7 Interactions between CAMEL and AOC services

The AOCI and AOCC services are not applicable to calls subject to a CAMEL
service.
190 / 204 3BL 95517 ABAA PCZZA Ed.01

9.5.8 Interactions between CAMEL and the CUG service

The CUG service is initiated before any originating or terminating call CAMEL
services.
When a CAMEL subscriber receives an incoming call with CUG information, if the
called party number was modified after CAMEL invocation, the call is:
released if the new called subscriber subscribes to the CUG service,
routed to the modified number if the new called subscriber is not a subscriber
to a CUG service.
3BL 95517 ABAA PCZZA Ed.01 191 / 204

192 / 204 3BL 95517 ABAA PCZZA Ed.01

Abbreviations
Abbreviations
2G Second Generation
3GPP Third Generation Partnership Project
AOCC Advice Of Charge-Charging

AOCI Advice Of Charge-Information
AuC Authentication Center
BAIC Barring of All Incoming Calls

BAOC Barring of All Outgoing Calls
BCH Basic Call Handling
BIC-Roam BAIC when Roaming outside the HPLMN country
BOIC Barring of Outgoing International Calls
BOIC-exHC BOIC except those directed to the HPLMN Country
BS Bearer Service
BSG Basic Service Group
CAMEL Customized Applications for Mobile network Enhanced Logic

CB Call Barring
CF Call Forwarding
CFB Call Forwarding on Busy mobile subscriber
CFC Call Forwarding Conditional
CFD default call forwarding
CFNRc Call Forwarding on mobile subscriber Not Reachable
CFNRy Call Forwarding on No Reply from mobile subscriber
CFU Call Forwarding Unconditional
CH Call Hold
CLI Calling Line Identity
CLIP Calling Line Identification Presentation
CLIR Calling Line Identification Restriction
CN Core Network
CNAP Calling Name Presentation
COLP COnnected Line identification Presentation
COLR COnnected Line identification Restriction
CORBA Common Object Request Broker Architecture
CSD Circuit Switched Data
CT Call Transfer
CUG Closed User Group
CW Call Waiting
DN Distinguished Name
ECT Explicit Call Transfer

eMLPP enhanced Multi-Level Precedence and Pre-emption
3BL 95517 ABAA PCZZA Ed.01 193 / 204

Abbreviations
ETSI European Telecommunications Standards Institute
FPLMN Foreign PLMN

FTN Forwarded-To Number
GBS General Bearer Service

GCS General Call Services
GSM Global System for Mobile communications
GUI Graphical User Interface
HB Hot Billing
HLR Home Location Register
HOLD call HOLD
HPLMN Home PLMN
IA Incoming Access
IAM Initial Address Message
IDL Interface Description Language
IMSI International Mobile Subscriber Identity
IN Intelligent Network
ISDN Integrated Services Digital Network
ISUP Integrated Services Digital Network User Part
ITU-T International Telecommunication Union - Telecommunication standardization sector
LI Line Identity
LIDB Line Information DataBase
MAP Mobile Application Part

MCI Malicious Call Identification
MPTY MultiParTY
MSC Mobile services Switching Center
NAM Network Access Mode

NDS supplementary designation number
OA Outgoing Access
ODB Operator Determined Barring
OMC Operation and Maintenance Center
194 / 204 3BL 95517 ABAA PCZZA Ed.01

Abbreviations
OSSS Operator Specific Supplementary Service
PCD Pre-Call Deflection

PI Presentation Indicator
PLMN Public Land Mobile Network
PRN Provide Routing Number
RCF Radio Control Function
SCF Service Control Function

SCP Service Control Point
SDM Subscriber Data Manager
SI Screening Indicator
SMS Short Message Service
SMS-MO Short Message Service-Mobile Originated
SMS-MO/PP Short Message Service-Mobile Originated/Point-to-Point
SMS-MT Short Message Service-Mobile Terminated
SMS-MT/PP Short Message Service-Mobile Terminated/Point-to-Point
SS Supplementary Services
SSP Service Switching Point
TCH Traffic CHannel

TS TeleService
UE User Equipment
UMTS Universal Mobile Telecommunications System
USSD Unstructured Supplementary Service Data
VLR Visitor Location Register

VMSC Visited Mobile services Switching Center
VPLMN Visited PLMN
WZN World Numbering Zone
3BL 95517 ABAA PCZZA Ed.01 195 / 204

Abbreviations
196 / 204 3BL 95517 ABAA PCZZA Ed.01

Glossary
Glossary
basic services The standardized telecommunications services that enable mobile subscribers to
communicate over the mobile network. GSM/UMTS standards define 2 categories
of basic services: Bearer Services (BS) and TeleServices (TS).
Bearer Service (BS) A type of telecommunication service that provides the capability of transmission
of information between access points. GSM/UMTS standards define various BSs
in terms of specific capacities, delay and bit error rates.
Customized A set of mobile network standards that defines an architecture for Intelligent Net-
Applications for Mobile work (IN) services. CAMEL enables subscribers to use the services to which they
network Enhanced have rights even when roaming outside their Home PLMN (HPLMN).
Logic (CAMEL)
Circuit-Switched Core The domain of the UMTS Core Network (CN) that provides mobility management
Network (CSCN) and switching services for voice and Circuit Switched Data (CSD).
circuit switching A telecommunications connection mode in which the network allocates a specific
set of resources for the duration of the call.
Core Network (CN) An architectural term relating to the part of the GSM/UMTS network that is inde-
pendent of the radio-connection technology of the User Equipment (UE).
destination profile The value assigned to a subscriber that represents the destinations allowed for
call forwarding.
Foreign PLMN (FPLMN) A Public Land Mobile Network (PLMN) other than the Home PLMN (HPLMN).
Gateway MSC (GMSC) A Mobile services Switching Center (MSC) that provides the interface between the
local mobile network and other networks (for example, the fixed network) for calls
to a mobile subscriber handled in the local network.
Global System for Mobile A set of ETSI standards for digital mobile communication via networks operating
communications (GSM) in the 900/1800/1900 MHz band over the radio interface. GSM is Second Gen-
eration (2G) mobile technology.
Home Location Register A permanent database that contains information (identification, directory number,
(HLR) services subscribed to) relating to the mobile subscribers of a Public Land Mobile
Network (PLMN) and the reference of the VLR corresponding to the last recorded
location of the subscribers.
3BL 95517 ABAA PCZZA Ed.01 197 / 204

Glossary
Home PLMN (HPLMN) The Public Land Mobile Network (PLMN) to which a mobile subscriber is admin-
istratively attached. The identity of the HPLMN is included in the International
Mobile Subscriber Identity (IMSI) of each subscriber.
Intelligent Network (IN) A telecommunications architecture that separates service logic from network
switching functions to enable operators to flexibly introduce new network
functions and services.
Mobile services Switching The element of the CSCN that provides the switching functions necessary to set
Center (MSC) up and to manage calls between two mobile subscribers, or between a mobile
subscriber and a fixed subscriber.
Node B A logical node in the radio access part of UMTS networks, responsible for radio
transmission and reception for one or more cells.
notification A message sent by the Radio Control Point (RCP) to the Service Switching Point (SSP)
to indicate information concerning a call, for example, a request for a service.
paging A procedure initiated by the Radio Control Point (RCP) on each incoming call in
order to find the destination User Equipment (UE) within the location area.
Public Land Mobile A telecommunications network set up and operated by an administration to offer
Network (PLMN) mobile cellular services.
Radio Access Network An architectural term relating to the part of the mobile network that provides ter-
(RAN) minal radio connection technology. In GSM networks, the RAN is the Base Station
Subsystem (BSS). In UMTS networks, the RAN is the Universal Terrestrial Radio Ac-
cess Network (UTRAN).
Radio Control Function The function of the Radio Control Point (RCP) that handles interworking of the
(RCF) CSCN with the Radio Access Network (RAN) and all the functions associated with
mobility management.
Radio Control Point (RCP) The element of the Mobile services Switching Center (MSC) that contains all the
specific call handling functions and provides interworking with the Service Switch-
ing Point (SSP) to manage the physical resources associated with call routing. The
Radio Control Point (RCP) hosts the Radio Control Function (RCF) and the Visitor
Location Register (VLR).
Radio Network Controller The Universal Terrestrial Radio Access Network (UTRAN) equipment that controls
(RNC) the use and integrity of the radio resources. The RNC is the UMTS equivalent of
the BSC from GSM networks.
roaming The capability of a subscriber to roam and use its UE in an area other than its
home network.
198 / 204 3BL 95517 ABAA PCZZA Ed.01

Glossary
Service Control Point (SCP) The physical entity of the Intelligent Network (IN) that hosts the Service Control
Function (SCF).
Service Switching Point The physical entity of the Mobile services Switching Center (MSC) that handles the
(SSP) Service Switching Function (SSF).
Subscriber Identity Module A smartcard for GSM user terminals that stores the subscriber identity, subscription
(SIM) data, authentication and ciphering keys, and authentication algorithms.
Supplementary Service (SS) A service that modifies or enhances a basic telecommunications service.
TeleService (TS) A type of telecommunications service that provides complete communication ca-
pability between users, including the terminal equipment functions, in compliance
with protocols established by agreement between administrations.
Universal Mobile The 3GPP-defined mobile telecommunications network that enables high-speed
Telecommunications voice and multimedia transmission.
System (UMTS)
Universal Subscriber A smartcard for UMTS user terminals that stores the subscriber identity, subscrip-
Identity Module (USIM) tion data, authentication and ciphering keys, and authentication algorithms.
Universal Terrestrial Radio The UMTS network subsystem that links the User Equipment (UE) with the core
Access Network (UTRAN) network. A UTRAN consists of one or more Radio Network Controllers (RNCs)
and Node Bs.
Unsolicited message An error message generated by the Real Time Operating System (RTOS) software
of Alcatel-Lucent 83xx platforms.
User Equipment (UE) UMTS and GSM subscriber terminals.
Visited MSC (VMSC) Mobile services Switching Center (MSC) to which a roaming mobile subscriber is
attached at a given time.
Visitor Location Register A database, associated with a Mobile services Switching Center (MSC), that con-
(VLR) tains information concerning the mobile subscribers temporarily present in the
coverage area of the MSC.
3BL 95517 ABAA PCZZA Ed.01 199 / 204

Glossary
200 / 204 3BL 95517 ABAA PCZZA Ed.01

Index
Index
A C
Acronyms Call barring

GSM/UMTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 definition
Advice Of Charge-Charging, See AOCC incoming calls . . . . . . . . . . . . . . . . . . . . . . . . . 42
Advice Of Charge-Information, See AOCI outgoing calls . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Announcements . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 general definition . . . . . . . . . . . . . . . . . . . . . . . . 39
AOCC modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
AOCI services, See BAOC, BOIC, BOIC-exHC, BAIC,
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 BIC-Roam
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71 Call completion
Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 services, See HOLD, CW, ECT, CCBS
Call forwarding
B announcements . . . . . . . . . . . . . . . . . . . . . . . . . . 26
barred numbers . . . . . . . . . . . . . . . . . . . . . . . . . . 26
BAIC destination profile . . . . . . . . . . . . . . . . . . . . . . . . 26
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 Forwarded-To Number . . . . . . . . . . . . . . . . . . . . 25
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 general definition . . . . . . . . . . . . . . . . . . . . . . . . 24
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
BAOC provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 services, See CFU, CFNRy, CFNRc, CFB, CFD, PCD
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 short FTN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 Call Forwarding on Busy, See CFB
Barring of All Incoming Calls, See BAIC Call Forwarding on No Reply, See CFNRy
Barring of All Incoming Calls when Roaming outside Call Forwarding on Not Reachable, See CFNRc
the HPLMN country, See BIC-Roam Call Forwarding Unconditional, See CFU
Barring of All Outgoing Calls except to emergency Call hold, See HOLD
numbers, See BAOC Call identification
Barring of Outgoing International Calls, See BOIC services, See COLP, COLR, CLIP, CLIR, MCI, CNAP
Barring of Outgoing International Calls except those Call waiting, See CW
directed to the HPLMN Country, See BOIC-exHC Calling Line Identification Presentation, See CLIP
Basic services Calling Line Identification Restriction, See CLIR
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Calling Name Presentation, See CNAP
Basic subscription CFB
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
BIC-Roam description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 CFD
BOIC definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 CFNRc
BOIC-exHC definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
BSG CFNRy
applicability to supplementary services . . . . . 172 definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3BL 95517 ABAA PCZZA Ed.01 201 / 204

Index
CFOP D
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
CFU Default call forwarding, See CFD
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Delete
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29 call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 111
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Charging eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162
services, See AOCI, AOCC GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
CLIP Destination profile . . . . . . . . . . . . . . . . . . . . . . . . . . 26
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 Display
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 call barring information . . . . . . . . . . . . . . . . . . . 98
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 call forwarding information . . . . . . . . . . . . . . . 114
CLIR CUG information . . . . . . . . . . . . . . . . . . . . . . . . 149
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 eMLPP information . . . . . . . . . . . . . . . . . . . . . . 165
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 GCS information . . . . . . . . . . . . . . . . . . . . . . . . 131
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53 Documentation
Closed User Group, See CUG for supplementary services management . . . . 76
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68 E
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
CNAP
ECT
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
COLP
eMLPP
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
COLR
provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
enhanced Multi-Level Precedence and Pre-emption,
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
See eMLPP
COnnected Line identification Presentation, See
Explicit Call Transfer, See ECT
COLP
COnnected Line identification Restriction, See COLR
Conventions G
terminological . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Copy GCS
call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97 modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 113 provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148 Group
eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164 services, See MPTY, CUG
GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
CUG H
copying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
deleting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146 HB
displaying information . . . . . . . . . . . . . . . . . . . 149 interactions with the CFU service . . . . . . . . . . 176
listing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151 HOLD
modifying . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154 definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142 description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
CW type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Hot Billing, See HB
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
202 / 204 3BL 95517 ABAA PCZZA Ed.01

Index
I listing CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

listing eMLPP subscription(s) . . . . . . . . . . . . . . 167
IN listing GCS subscription(s) . . . . . . . . . . . . . . . . 133
interactions with supplementary services . . . . 189 modifying CUG . . . . . . . . . . . . . . . . . . . . . . . . . 154
Intelligent Networks, See IN provisioning CUG . . . . . . . . . . . . . . . . . . . . . . . 142
Interactions provisioning eMLPP . . . . . . . . . . . . . . . . . . . . . . 160
between AOCC and AOCI . . . . . . . . . . . . . . . 188
between call barring services . . . . . . . . . . . . . . 177 L
between call forwarding and call barring
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178 List
between call forwarding services . . . . . . . . . . 177 call barring subscription(s) . . . . . . . . . . . . . . . . 100
between CLIP and other supplementary call forwarding subscription(s) . . . . . . . . . . . . . 116
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 CUG subscription(s) . . . . . . . . . . . . . . . . . . . . . 151
between CLIR and other supplementary eMLPP subscription(s) . . . . . . . . . . . . . . . . . . . . 167
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 GCS subscription(s) . . . . . . . . . . . . . . . . . . . . . . 133
between CNAP and other supplementary
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185 M
between COLP and other supplementary
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Malicious Call Identification, See MCI
between CUG and other supplementary
Management
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
Supplementary services
between CW and other supplementary
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
MCI
between ECT and other supplementary
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
between HOLD and other supplementary
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Modifying
between MPTY and other supplementary
call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . 119
between supplementary services . . . . . . . . . . . 177
CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154
system functions and supplementary services 174
eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
with CAMEL services . . . . . . . . . . . . . . . . . . . . . 190
GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
with hot billing . . . . . . . . . . . . . . . . . . . . . . . . . . 176
MPTY
with IN services . . . . . . . . . . . . . . . . . . . . . . . . . 189
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
with ODB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
K MultiParTY call, See MPTY
Key procedure O
copying call barring . . . . . . . . . . . . . . . . . . . . . . 97
copying call forwarding . . . . . . . . . . . . . . . . . . 113
ODB
copying CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174
copying eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . 164
interactions with supplementary services . . . . 174
copying GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
On Line Help (OLH) . . . . . . . . . . . . . . . . . . . . . . . . 76
deleting call barring . . . . . . . . . . . . . . . . . . . . . . 95
Operator
deleting call forwarding . . . . . . . . . . . . . . . . . . 111
services, See OSSS
deleting CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Operator Specific Supplementary Services, See OSSS
deleting eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . 162
OSSS
deleting GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
displaying call barring information . . . . . . . . . 98
description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
displaying call forwarding information . . . . . 114
type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
displaying CUG . . . . . . . . . . . . . . . . . . . . . . . . . 149
displaying eMLPP information . . . . . . . . . . . . . 165
displaying GCS information . . . . . . . . . . . . . . 131 P
listing call barring subscription(s) . . . . . . . . . . 100
listing call forwarding subscription(s) . . . . . . . 116 Pre-Call Deflection, See PCD
3BL 95517 ABAA PCZZA Ed.01 203 / 204

Index
Priority call
services, See eMLPP
Proprietary supplementary service
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Provisioning
Call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Call forwarding . . . . . . . . . . . . . . . . . . . . . . . . . 108
CUG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
eMLPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160
GCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Standardized supplementary service

definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Supplementary service
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 17, 199
foreign subscribers . . . . . . . . . . . . . . . . . . . . . . . 18
groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
list by service type . . . . . . . . . . . . . . . . . . . . . . . . 19
management
documentation . . . . . . . . . . . . . . . . . . . . . . . . . 76
types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Supplementary services
management
overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Telecommunications
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
USSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
204 / 204 3BL 95517 ABAA PCZZA Ed.01

3bl95517abaapczza 01 en PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

3bl95517abaapczza 01 en PDF

Загружено:

Авторское право:

Доступные форматы

Alcatel-Lucent

3BL 95517 ABAA PCZZA Ed.01

Status RELEASED 24/09/2008

2 / 204 3BL 95517 ABAA PCZZA Ed.01

3BL 95517 ABAA PCZZA Ed.01 3 / 204

4.3 Copying call barring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

4 / 204 3BL 95517 ABAA PCZZA Ed.01

9.5 Interactions with CAMEL services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

3BL 95517 ABAA PCZZA Ed.01 5 / 204

6 / 204 3BL 95517 ABAA PCZZA Ed.01

3BL 95517 ABAA PCZZA Ed.01 7 / 204

8 / 204 3BL 95517 ABAA PCZZA Ed.01

Contents Chapter1 gives a general description of Supplementary Services

Related documents Documents related to this guide include:

3BL 95517 ABAA PCZZA Ed.01 9 / 204

Alcatel-Lucent 8650 SDM, CORBA Interface Description for SDM Provisioning

Typographical conventions This guide uses the following typographical conventions:

This guide uses:

The guide also uses the following terminological conventions:

For all other supplementary services:

10 / 204 3BL 95517 ABAA PCZZA Ed.01

Alcatel-Lucent acknowledges the following trademark for company names or

3BL 95517 ABAA PCZZA Ed.01 11 / 204

12 / 204 3BL 95517 ABAA PCZZA Ed.01

1 Introduction to supplementary services

This chapter provides a general description of Supplementary Services (SSs) and

3BL 95517 ABAA PCZZA Ed.01 13 / 204

1.1 Telecommunication services

1.2 Basic services

14 / 204 3BL 95517 ABAA PCZZA Ed.01

Table 1: Basic services (BS/TS) offered

BSG Basic service Definition Network applicability

BSG20 BS21, BS22, Asynchronous duplex circuit data ser-

GBS 20 Asynchronous duplex circuit data ser-

BSG30 BS31, BS32, Synchronous duplex circuit data services

GBS 30 Synchronous duplex circuit data services

Speech TS11 Telephony

TS12 Emergency call

SMS TS21 Short Message Service-Mobile Termi-

TS22 Short Message Service-Mobile Origi-

Fax TS61 Alternate speech and facsimile group 3

TS62 Automatic facsimile group 3

3BL 95517 ABAA PCZZA Ed.01 15 / 204

Figure 1: Basic subscription

A basic subscription includes the following subscriber data:

16 / 204 3BL 95517 ABAA PCZZA Ed.01

1.3 Supplementary services in a GSM or UMTS network

Figure 2: GSM/UMTS network architecture

3BL 95517 ABAA PCZZA Ed.01 17 / 204

Supplementary services data for a subscriber is stored in the HLR/AuC of their

Figure 3: Supplementary services data

The HLR/AuC of the 8650 SDM:

18 / 204 3BL 95517 ABAA PCZZA Ed.01

1.3.1 Supplementary service type

1.3.2 Unstructured Supplementary Service Data (USSD)

1.3.3 Supplementary service groups

3BL 95517 ABAA PCZZA Ed.01 19 / 204

Table 2: Supplementary services

Supplementary Service GSM/UMTS Acronym Service Type

Call Forwarding Services

Call Forwarding Unconditional CFU standardized

Call Forwarding on No Reply from mobile sub- CFNREPLY standardized