Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
8650 Subscriber
Data Manager
SDM SUPPLEMENTARY SERVICES
MANAGEMENT
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.
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
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
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
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.
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.
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.
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.
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).
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).
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.
Table 2 lists the supplementary services that you can offer to mobile subscribers
in a GSM or UMTS network.
Group Services
Charging Services
Operator Services
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.
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.
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).
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.
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
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.
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 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.
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.
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 VMSC B:
routes the call to the PSTN if the FTN is the number of a fixed subscriber,
or,
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.
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
a list of allowed destinations,
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,
rejection of subaddresses for call forwarding,
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.
Service description Depending on the non-reachability conditions, call forwarding is performed either
by the GMSC or the VMSC.
The GMSC:
routes the call to the PSTN if the FTN is the number of a fixed subscriber,
or,
triggers 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.
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 forwarded-to subaddress, if there is one,
the call forwarding options for the CFNREACH service.
The VMSC B:
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 VMSC B so that subscriber B is charged for the for-
warded portion of the call.
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),
call forwarding allowed on call forwarding violation, when the FTN belongs to
a list of allowed destinations,
in the case of a call forwarding violation, call offered to the initially called UE
or call rejected,
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,
rejection of subaddresses for call forwarding,
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.
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
routing information.
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 VMSC B:
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 VMSC B so that subscriber B is charged for the for-
warded portion of the call.
Depending on the Public Land Mobile Network (PLMN) options, the network can
reject call forwarding on busy for a given category of calling subscribers.
CFBUSY options:
The CFBUSY options are:
call forwarding allowed on call forwarding violation, when the FTN belongs to
a list of allowed destinations,
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 identity to C,
rejection of subaddresses for call forwarding,
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 the call is forwarded by the CFBUSY service on a busy
condition determined by the network.
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.
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.
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.
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.
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.
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).
BOIC-exHC BOIC
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.
Note: The line identity display services (COLP and CLIP) are linked to a corresponding
line identification restriction service (COLR and CLIR).
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 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.
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.
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.
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.
Figure 16: COLR service between two mobile subscribers in the same network
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.
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.
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
PI = presentation allowed PI = presentation allowed
NDS not received or not CLI = LI with or without sub- CLI = LI with or without
applicable address subaddress
PI = presentation allowed
PI = presentation allowed
SI transmitted unchanged
SI transmitted unchanged
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
PI = presentation restricted
SI transmitted unchanged
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)
SI transmitted unchanged
(if CLI = LI)
NDS not received or not CLI not transmitted CLI = LI with or without
applicable subaddress
PI = presentation restricted
PI = presentation restricted
SI transmitted unchanged
SI transmitted unchanged
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.
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:
Figure 19: CLIR service between two mobile subscribers in the same network
PI = presentation allowed
PI = presentation restricted
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.
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
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
Basic operations :
Figure 26 illustrates some of the basic operations that the controlling subscriber
can perform:
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,
disconnect one party or terminate the conference call by disconnecting all the
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,
disconnect one party or terminate the conference call by disconnecting all the
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.).
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.
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.
The MSC stores information on resource pre-emption actions for any given levels
for incoming and on-going call priority.
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.
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),
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,
barOutInterCallProv
Description
barOutIntCallExceptToH-
plmnProv Description
Barring of outgoing international calls except those directed to the HPLMN coun-
try
barIncCallProvisioned
Description
barIncCallRoamFCoun-
tryProv Description
Barring of incoming calls when roaming outside the HPLMN country is provi-
sioned
BSGofBAOClist
Description
BSGofBOIClist
Description
BSGofBOICEXHClist
Description
List of BSGs activated for BAOC except those directed to the HPLMN Country
BSGofBAIClist
Description
BSGofBICROAMlist
Description
List of BSGs activated for BAIC when Roaming outside the HPLMN country
MsCbAbility
Description
callBarringPassword
Description
msCfNoAbility
Description
destinationProfile
Description
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
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
Call Forwarded Number list, one per BSG for Call Forwarding, by default, on
subscriber Not Reachable
cfdcfnreplyCallForward-
ingNumberlist Description
Call Forwarded Number list, one per BSG for Call Forwarding, by default, on
No Reply
cfuNotifToFwdPartyFlag
Description
cfbusyNotifToFwdPartyFlag
Description
cfnreplyNotifToFwdPar-
tyFlag Description
cfnreachNotifToFwdPar-
tyFlag Description
allNotifToFwdPartyFlag
Description
cfuNotifToCallingPartyFlag
Description
cfbusyNotifToCalling-
PartyFlag Description
cfnreplyNotifToCalling-
PartFlag Description
cfnreachNotifToCalling-
PartFlag Description
allNotifToCallingPartyFlag
Description
colpOverrideCategoryState
Description
clipProvisionedFlag
Description
clipOverrideCategoryState
Description
clirProvisionedFlag
Description
presentationMode
Description
Presentation mode
callHoldProvisionedFlag
Description
CH provisioned flag
mptyProvisionedFlag
Description
callTransferProvisionedFlag
Description
aoccProvisionedFlag
Description
aociProvisionedFlag
Description
maliciousCallProvisioned-
Flag Description
colrProvisionedFlag
Description
osss1ProvisionedFlag to
osss15ProvisionedFlag Description
osss1ActivationFlag to
osss15ActivationFlag Description
callWaitingProvisionedFlag
Description
cwTSSpeechActivationFlag
Description
cwTSFaxActivationFlag
Description
cwBSG20ActivationFlag
Description
cwBSG30ActivationFlag
Description
cnapProvisionedFlag
Description
cnapOverrideCategoryState
Description
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
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
Preferential CUG index number with a CUG interlock code associated to the
BSG Fax, which is the nominated default CUG to be used when no explicit
CUG index is received by the network
prefCugIndexForBsg20
Description
Preferential CUG index number with a CUG interlock code associated to the
BSG Data Cda, which is the nominated default CUG to be used when no explicit
CUG index is received by the network
prefCugIndexForBsg30
Description
Preferential CUG index number with a CUG interlock code associated to the
BSG Data Cds, which is the nominated default CUG to be used when no explicit
CUG index is received by the network
interCugRestForSpeech
Description
Inter CUG restriction which allows receiving calls from or placing calls outside
the CUG associated to the BSG Speech
interCugRestForFax
Description
Inter CUG restriction which allows receiving calls from or placing calls outside
the CUG associated to the BSG Fax
interCugRestForBsg20
Description
Inter CUG restriction which allows receiving calls from or placing calls outside
the CUG associated to the BSG Data Cda
interCugRestForBsg30
Description
Inter CUG restriction which allows receiving calls from or placing calls outside
the CUG associated to the BSG Data Cds
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
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).
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
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
Set parameter(s)...
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
BarOutIntercallExceptToHplmnProv
BarIncCallProvisioned
BarIncCallRoamFCountryProv
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
6. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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):
Using subscriber profile:
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
After a subscription (or several subscriptions) has (have) been copied, you can
then modify the new subscription(s) to match your operation requirements.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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.
You use the subscriber identity (DN-subscriber profile) to select the subscriber(s)
for which you want to perform the operation.
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
BarOutIntercallExceptToHplmnProv
BarIncCallProvisioned
BarIncCallRoamFCountryProv
callBarringPassword
msCBAbility
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
3. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
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
Set parameter(s)...
Set parameter(s)...
BarOutCallProv
BarOutInterCallProv
BarOutIntercallExceptToHplmnProv
BarIncCallProvisioned
BarIncCallRoamFCountryProv
BSGofBAOClist
BSGofBOIClist
BSGofBAOCEXHClist
BSGofBAIClist
BSGofBICROAMlist
6. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
This chapter describes the following procedures and their parameters to manage
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).
Note: Before managing basic subscription data, you need to be familiar with
Subscription management basics (see chapter 1).
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
3. Set the mandatory parameter for call forwarding ty p eOf C allForw ard -
i ng Li st
Set parameter(s)...
Set parameter(s)...
destinationProfile
msCFNoAbility
cfuCallForwardingNumberList
cfbusyCallForwardingNumberList
cfnreplyCallForwardingNumberList
cfnreachCallForwardingNumberList
cfdCallForwardingNumberList
allCallForwardingNumberList
cfdcfbusyCallForwardingNumberlist
cfdcfnreachCallForwardingNumberlist
cfdcfnreplyCallForwardingNumberlist
cfuNotifToFwdPartyFlag
cfbusyNotifToFwdPartyFlag
cfnreplyNotifToFwdPartyFlag
cfnreachNotifToFwdPartyFlag
allNotifToFwdPartyFlag
cfuNotifToCallingPartyFlag
cfbusyNotifToCallingPartyFlag
cfnreplyNotifToCallingPartFlag
cfnreachNotifToCallingPartFlag
allNotifToCallingPartyFlag
5. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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 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.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
After one or more subscriptions have been copied, you can then modify the new
subscription(s) to match your operation requirements.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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.
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.
You use the subscriber identity (DN-subscriber profile) to select the subscriber(s)
for which you want to perform the operation.
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
destinationProfile
cfuCallForwardingNumberList
cfbusyCallForwardingNumberList
cfnreplyCallForwardingNumberList
cfnreachCallForwardingNumberList
cfdCallForwardingNumberList
allCallForwardingNumberList
cfdcfbusyCallForwardingNumberlist
cfdcfnreachCallForwardingNumberlist
cfdcfnreplyCallForwardingNumberlist
cfuNotifToFwdPartyFlag
cfbusyNotifToFwdPartyFlag
cfnreplyNotifToFwdPartyFlag
cfnreachNotifToFwdPartyFlag
allNotifToFwdPartyFlag
cfuNotifToCallingPartyFlag
cfbusyNotifToCallingPartyFlag
cfnreplyNotifToCallingPartFlag
cfnreachNotifToCallingPartFlag
allNotifToCallingPartyFlag
notif flags
destinationProfile
msCfNoAbility
3. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
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
cfuCallForwardingNumberList
cfbusyCallForwardingNumberList
cfnreplyCallForwardingNumberList
cfnreachCallForwardingNumberList
cfdCallForwardingNumberList
allCallForwardingNumberList
cfdcfbusyCallForwardingNumberlist
cfdcfnreachCallForwardingNumberlist
cfdcfnreplyCallForwardingNumberlist
cfuNotifToFwdPartyFlag
cfbusyNotifToFwdPartyFlag
cfnreplyNotifToFwdPartyFlag
cfnreachNotifToFwdPartyFlag
allNotifToFwdPartyFlag
cfuNotifToCallingPartyFlag
cfbusyNotifToCallingPartyFlag
cfnreplyNotifToCallingPartFlag
cfnreachNotifToCallingPartFlag
allNotifToCallingPartyFlag
5. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
This chapter describes the following procedures and their parameters to manage
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).
Note: Before managing basic subscription data, you need to be familiar with
Subscription management basics (see chapter 1).
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
colpProvisionedFlag
colpOverrideCategoryState
clipProvisionedFlag
clipOverrideCategoryState
clirProvisionedFlag
presentationMode
callHoldProvisionedFlag
mptyProvisionedFlag
callTransferProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
maliciousCallProvisionedFlag
callWaitingProvisionedFlag
cwTSSpeechActivationFlag
cwTSFaxActivationFlag
cwBSG20ActivationFlag
cwBSG30ActivationFlag
osss1ProvisionedFlag
osss1ActivationFlag
osss2ProvisionedFlag
osss2ActivationFlag
osss3ProvisionedFlag
osss3ActivationFlag
osss4ProvisionedFlag
osss4ActivationFlag
osss5ProvisionedFlag
osss5ActivationFlag
osss6ProvisionedFlag
osss6ActivationFlag
osss7ProvisionedFlag
osss7ActivationFlag
osss8ProvisionedFlag
osss8ActivationFlag
osss9ProvisionedFlag
osss9ActivationFlag
Set parameter(s)...
osss10ProvisionedFlag
osss10ActivationFlag
osss11ProvisionedFlag
osss11ActivationFlag
osss12ProvisionedFlag
osss12ActivationFlag
osss13ProvisionedFlag
osss13ActivationFlag
osss14ProvisionedFlag
osss14ActivationFlag
osss15ProvisionedFlag
osss15ActivationFlag
cnapProvisionedFlag
cnapOverrideCategoryState
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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 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.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
After one or more subscriptions have been copied, you can then modify the new
subscription(s) to match your operation requirements.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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.
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.
You use the subscriber identity (DN-subscriber profile) to select the subscriber(s)
for which you want to perform the operation.
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
colpProvisionedFlag
colpOverrideCategoryState
clipProvisionedFlag
clipOverrideCategoryState
clirProvisionedFlag
presentationMode
callHoldProvisionedFlag
mptyProvisionedFlag
callTransferProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
maliciousCallProvisionedFlag
callWaitingProvisionedFlag
cwTSSpeechActivationFlag
cwTSFaxActivationFlag
cwBSG20ActivationFlag
cwBSG30ActivationFlag
cwBSG40ActivationFlag
osss1ProvisionedFlag
osss1ActivationFlag
osss2ProvisionedFlag
osss2ActivationFlag
osss3ProvisionedFlag
osss3ActivationFlag
osss4ProvisionedFlag
osss4ActivationFlag
osss5ProvisionedFlag
osss5ActivationFlag
osss6ProvisionedFlag
osss6ActivationFlag
osss7ProvisionedFlag
osss7ActivationFlag
osss8ProvisionedFlag
osss8ActivationFlag
osss9ProvisionedFlag
osss9ActivationFlag
Set parameter(s)...
osss10ProvisionedFlag
osss10ActivationFlag
osss11ProvisionedFlag
osss11ActivationFlag
osss12ProvisionedFlag
osss12ActivationFlag
osss13ProvisionedFlag
osss13ActivationFlag
osss14ProvisionedFlag
osss14ActivationFlag
osss15ProvisionedFlag
osss15ActivationFlag
cnapProvisionedFlag
cnapOverrideCategoryState
3. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
colpProvisionedFlag
colpOverrideCategoryState
clipProvisionedFlag
clipOverrideCategoryState
clirProvisionedFlag
presentationMode
callHoldProvisionedFlag
mptyProvisionedFlag
callTransferProvisionedFlag
aoccProvisionedFlag
aociProvisionedFlag
maliciousCallProvisionedFlag
callWaitingProvisionedFlag
cwTSSpeechActivationFlag
cwTSFaxActivationFlag
cwBSG20ActivationFlag
cwBSG30ActivationFlag
cwBSG40ActivationFlag
osss1ProvisionedFlag
osss1ActivationFlag
osss2ProvisionedFlag
osss2ActivationFlag
osss3ProvisionedFlag
osss3ActivationFlag
osss4ProvisionedFlag
osss4ActivationFlag
osss5ProvisionedFlag
osss5ActivationFlag
osss6ProvisionedFlag
osss6ActivationFlag
osss7ProvisionedFlag
osss7ActivationFlag
osss8ProvisionedFlag
osss8ActivationFlag
osss9ProvisionedFlag
osss9ActivationFlag
Parameters to set up
osss10ProvisionedFlag
osss10ActivationFlag
osss11ProvisionedFlag
osss11ActivationFlag
osss12ProvisionedFlag
osss12ActivationFlag
osss13ProvisionedFlag
osss13ActivationFlag
osss14ProvisionedFlag
osss14ActivationFlag
osss15ProvisionedFlag
osss15ActivationFlag
cnapProvisionedFlag
cnapOverrideCategoryState
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
This chapter describes the following procedures and their parameters to manage
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).
Note: Before managing basic subscription data, you need to be familiar with
Subscription management basics (see chapter 1).
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
cugInterlockCodeInd1
cugInterlockCodeInd2
cugInterlockCodeInd3
cugInterlockCodeInd4
cugInterlockCodeInd5
cugInterlockCodeInd6
cugInterlockCodeInd7
cugInterlockCodeInd8
cugInterlockCodeInd9
cugInterlockCodeInd10
intraCugOptionInd1
intraCugOptionInd2
intraCugOptionInd3
intraCugOptionInd4
intraCugOptionInd5
intraCugOptionInd6
intraCugOptionInd7
intraCugOptionInd8
intraCugOptionInd9
intraCugOptionInd10
AllassociatedBsgString1
AllassociatedBsgString2
AllassociatedBsgString3
AllassociatedBsgString4
AllassociatedBsgString5
AllassociatedBsgString6
AllassociatedBsgString7
AllassociatedBsgString8
AllassociatedBsgString9
AllassociatedBsgString10
prefCugIndexForSpeech
prefCugIndexForFax
prefCugIndexForBsg20
prefCugIndexForBsg30
interCugRestForSpeech
interCugRestForFax
interCugRestForBsg20
interCugRestForBsg30
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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 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.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
After one or more subscriptions have been copied, you can then modify the new
subscription(s) to match your operation requirements.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
From the tools listed in section 3.1, you can list CUG 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.
You use the subscriber identity (DN-subscriber profile) to select the subscriber(s)
for which you want to perform the operation.
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
cugInterlockCodeInd1
cugInterlockCodeInd2
cugInterlockCodeInd3
cugInterlockCodeInd4
cugInterlockCodeInd5
cugInterlockCodeInd6
cugInterlockCodeInd7
cugInterlockCodeInd8
cugInterlockCodeInd9
cugInterlockCodeInd10
prefCugIndexForSpeech
prefCugIndexForFax
prefCugIndexForBsg20
prefCugIndexForBsg30
3. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
cugInterlockCodeInd1
cugInterlockCodeInd2
cugInterlockCodeInd3
cugInterlockCodeInd4
cugInterlockCodeInd5
cugInterlockCodeInd6
cugInterlockCodeInd7
cugInterlockCodeInd8
cugInterlockCodeInd9
cugInterlockCodeInd10
intraCugOptionInd1
intraCugOptionInd2
intraCugOptionInd3
intraCugOptionInd4
intraCugOptionInd5
intraCugOptionInd6
intraCugOptionInd7
intraCugOptionInd8
intraCugOptionInd9
intraCugOptionInd10
AllassociatedBsgString1
AllassociatedBsgString2
AllassociatedBsgString3
AllassociatedBsgString4
AllassociatedBsgString5
AllassociatedBsgString6
AllassociatedBsgString7
AllassociatedBsgString8
AllassociatedBsgString9
AllassociatedBsgString10
prefCugIndexForSpeech
prefCugIndexForFax
prefCugIndexForBsg20
prefCugIndexForBsg30
interCugRestForSpeech
interCugRestForFax
interCugRestForBsg20
interCugRestForBsg30
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
This chapter describes the following procedures and their parameters to manage
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).
Note: Before managing basic subscription data, you need to be familiar with
Subscription management basics (see chapter 1).
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
emlppMaximumEntitledPriority
emlppDefaultPriority
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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.
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.
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
To select the subscriber for which you want to perform the operation, 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)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
From the tools listed in section 3.1, you can list eMLPP 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: match on no 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.
Use the subscriber identity (DN-subscriber profile) to select the subscriber(s) for
which you want to perform the operation.
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
emlppProvisionedFlag
3. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
Set parameter(s)...
suMSubscriberProfileId
Using IMSI:
Set parameter(s)...
MobileCountryCodeId (MCC)
MobileNetworkCodeId (MNC)
MSubIdentificationNumberId (MSIN)
Set parameter(s)...
CountryCodeId (CC)
NationalDestinationCodeId (NDC)
SubscriberNumberId (SN)
Set parameter(s)...
emlppMaximumEntitledPriority
emlppDefaultPriority
4. End.
the On Line
Help (OLH)
possible values for parameters
available on
8650 SDM GUI
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.
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)
COLP
COLR
CLIP
CLIR
MCI
HOLD (1)
CW (1)
ECT (1)
MPTY (1)
AOCI (1)
AOCC (1)
Supplemen- BSG
tary service
Speech call SMS FAX Asynchronous Synchronous
Data Data
Transmission Transmission
(BSG20 ) (BSG30)
CUG (1)
eMLPP
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.
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:
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.
CFU
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.
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
BAOC
BAIC
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.
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
International
FTN
Foreign FTN
International
FTN:
UE outside
HPLMN
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.
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.
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,
for the forwarded section of the call, the number of the forwarding subscriber
is transmitted as the number of the calling subscriber.
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.
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.
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.
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 CUG Subscribers involved in the ECT service must belong to the same CUG.
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.
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 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.
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.
Note: Interactions exist between CAMEL phase 3 services and supplementary services if
the CAMEL phase 3 services are supported by the RCP.
Abbreviations
2G Second Generation
3GPP Third Generation Partnership Project
DN Distinguished Name
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
OA Outgoing Access
ODB Operator Determined Barring
OMC Operation and Maintenance Center
UE User Equipment
UMTS Universal Mobile Telecommunications System
USSD Unstructured Supplementary Service Data
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.
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.
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.
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.
Index
A C
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
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
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
Telecommunications
definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
USSD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19