ETSI ETS 300 529 ed.2 (1995-10)

European digital cellular telecommunications system (Phase 2); Technical realization of supplementary services (GSM 03.11)

RE/SMG-030311P

Evropski digitalni celični telekomunikacijski sistem (faza 2) – Tehnična realizacija dopolnilnih storitev (GSM 03.11)

General Information

• Status: Published
• Publication Date: 11-Oct-1995
• Technical Committee: SMG 3 - Network Aspects
• Current Stage: 12 - Completion
• Due Date: 13-Oct-1995
• Completion Date: 12-Oct-1995
• Ref Project: SIST ETS 300 529 E2:2003 - European digital cellular telecommunications system (Phase 2); Technical realization of supplementary services (GSM 03.11)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 529 E2:2003
01-december-2003
(YURSVNLGLJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHPID]D±7HKQLþQDUHDOL]DFLMD
GRSROQLOQLKVWRULWHY*60
European digital cellular telecommunications system (Phase 2); Technical realization of
supplementary services (GSM 03.11)
Ta slovenski standard je istoveten z: ETS 300 529 Edition 2
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
SIST ETS 300 529 E2:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ETS 300 529 E2:2003

---------------------- Page: 2 ----------------------

SIST ETS 300 529 E2:2003
EUROPEAN ETS 300 529
TELECOMMUNICATION October 1995
STANDARD Second Edition
Source: ETSI TC-SMG Reference: RE/SMG-030311P
ICS: 33.060.50
European digital cellular telecommunications system, Global System for Mobile communications
Key words:
(GSM)
European digital cellular telecommunications system (Phase 2);
Technical realization of supplementary services
(GSM 03.11)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
Copyright Notification: No part may be reproduced except as authorized by written permission. The copyright and the
foregoing restriction extend to reproduction in all media.
© European Telecommunications Standards Institute 1995. All rights reserved.
New presentation - see History box

---------------------- Page: 3 ----------------------

SIST ETS 300 529 E2:2003
Page 2
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

---------------------- Page: 4 ----------------------

SIST ETS 300 529 E2:2003
Page 3
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Contents
Foreword.5
1 General .7
1.1 Scope .7
1.2 Normative references .7
1.3 Definitions and abbreviations.8
2 Activation, deactivation, registration, erasure, interrogation and invocation .9
2.1 General.9
2.1.1 Definition of "state vectors" .9
2.1.2 Handling of service states at the HLR.10
2.1.2.1 Encoding of SS-Status.11
2.1.2.2 Invocation of services at the HLR.11
2.1.3 Handling of SS-Status at the VLR .11
2.1.3.1 Invocation of services at the VLR.12
2.1.3.2 Interrogation of the service at the VLR and notifications
from VLR.12
2.1.4 Handling of SS-Status at the MS .12
2.2 Handling of call independent SS procedures with respect to basic service groups .12
2.3 Exceptional handling of basic service codes .13
3 Password handling .18
3.1 General.18
3.2 Registration of password.23
3.3 Use of password.23
3.4 Deactivation.26
4 Supplementary service data management .27
5 Format of description.27
History.28

---------------------- Page: 5 ----------------------

SIST ETS 300 529 E2:2003
Page 4
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Blank page

---------------------- Page: 6 ----------------------

SIST ETS 300 529 E2:2003
Page 5
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Foreword
This European Telecommunication Standard (ETS) has been produced by the Special Mobile Group
(SMG) Technical Committee (TC) of the European Telecommunications Standards Institute (ETSI).
This ETS defines the technical realization of supplementary services for the European digital cellular
telecommunications system (Phase 2).
This ETS corresponds to GSM Technical Specification (GSM-TS) GSM 03.11 version 4.9.1.
The specification from which this ETS has been derived was originally based on CEPT documentation,
hence the presentation of this ETS may not be entirely in accordance with the ETSI/PNE rules.
Reference is made within this ETS to GSM-TSs (NOTE).
Reference is also made within this ETS to GSM xx.xx series. The specifications in the series can be
identified, with their full title, within the normative reference Clause of this ETS by the first two digits of
their GSM reference number e.g. GSM 09.xx series, refers to GSM 09.01, GSM 09.02, etc.
NOTE: TC-SMG has produced documents which give the technical specifications for the
implementation of the European digital cellular telecommunications system. Historically,
these documents have been identified as GSM Technical Specifications (GSM-TSs).
These TSs may have subsequently become I-ETSs (Phase 1), or ETSs (Phase 2),
whilst others may become ETSI Technical Reports (ETRs). GSM-TSs are, for editorial
reasons, still referred to in current GSM ETSs.
Proposed transposition dates
Date of adoption of this ETS: 31 October 1995
Date of latest announcement of this ETS (doa): 31 January 1996
Date of latest publication of new National Standard 31 July 1996
or endorsement of this ETS (dop/e):
31 July 1996
Date of withdrawal of any conflicting National Standard (dow):

---------------------- Page: 7 ----------------------

SIST ETS 300 529 E2:2003
Page 6
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Blank page

---------------------- Page: 8 ----------------------

SIST ETS 300 529 E2:2003
Page 7
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
1 General
1.1 Scope
This ETS describes the general aspects on how supplementary services in the GSM system are realized
from a technical point of view.
Description of technical realization for specific supplementary services can be found in GSM 03.8x and
03.9x-series technical specifications.
All supplementary services may require signalling on the radio path. Signalling procedures and messages
used are defined in the GSM 04.8x and 04.9x-series of technical specifications.
For some supplementary services information needs to be transferred between the home location register
(HLR), the visitor location register (VLR) and the mobile services switching centre (MSC). Signalling
procedures for such information transfer are defined in technical specification GSM 09.02.
Definitions and descriptions of supplementary services are given in the GSM 02.8x and 02.9x-series of
technical specifications.
Definitions are given in technical specification GSM 02.04.
NOTE 1: The technical specifications on the technical realization of supplementary services do
not distinguish between subscriber, user and customer, since all three do not fully cover
the textual needs. Generally the term "subscriber" is used, even if this person is not
having the subscription.
NOTE 2: The terms "he", "his" and "him" are used as abbreviation of "he/she", "his/her" and
"him/her" respectively.
1.2 Normative references
This ETS incorporates by dated and undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications are listed
hereafter. For dated references, subsequent amendments to or revisions of any of these publications apply
to this ETS only when incorporated in it by amendment or revision. For undated references, the latest
edition of the publication referred to applies.
[1] GSM 01.04 (ETR 100): "European digital cellular telecommunications system
(Phase 2); "Abbreviations and acronyms".
[2] GSM 02.04 (ETS 300 503): "European digital cellular telecommunications
system (Phase 2); General on supplementary services".
[3] GSM 02.30 (ETS 300 511): "European digital cellular telecommunications
system (Phase 2); Man-Machine Interface (MMI) of the Mobile Station (MS)".
[4] GSM 03.81 (ETS 300 542): "European digital cellular telecommunications
system (Phase 2); Line identification supplementary services - Stage 2".
[5] GSM 03.82 (ETS 300 543): "European digital cellular telecommunications
system (Phase 2); Call Forwarding (CF) supplementary services - Stage 2".
[6] GSM 03.83 (ETS 300 544): "European digital cellular telecommunications
system (Phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary
services - Stage 2".
[7] GSM 03.84 (ETS 300 545): "European digital cellular telecommunications
system (Phase 2); Multi Party (MPTY) supplementary services - Stage 2".

---------------------- Page: 9 ----------------------

SIST ETS 300 529 E2:2003
Page 8
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
[8] GSM 03.85 (ETS 300 546): "European digital cellular telecommunications
system (Phase 2); Closed User Group (CUG) supplementary services -
Stage 2".
[9] GSM 03.86 (ETS 300 547): "European digital cellular telecommunications
system (Phase 2); Advice of Charge (AoC) supplementary services - Stage 2".
[10] GSM 03.88 (ETS 300 548): "European digital cellular telecommunications
system (Phase 2); Call Barring (CB) supplementary services - Stage 2".
[11] GSM 03.90 (ETS 300 549): "European digital cellular telecommunications
system (Phase 2); Unstructured supplementary services operation - Stage 2".
[12] GSM 04.80 (ETS 300 564): "European digital cellular telecommunications
system (Phase 2); Mobile radio interface layer 3 supplementary services
specification Formats and coding".
[13] GSM 04.81 (ETS 300 565): "European digital cellular telecommunications
system (Phase 2); Line identification supplementary services - Stage 3".
[14] GSM 04.82 (ETS 300 566): "European digital cellular telecommunications
system (Phase 2); Call Forwarding (CF) supplementary services - Stage 3".
[15] GSM 04.83 (ETS 300 567): "European digital cellular telecommunications
system (Phase 2); Call Waiting (CW) and Call Hold (HOLD) supplementary
services - Stage 3".
[16] GSM 04.84 (ETS 300 568): "European digital cellular telecommunications
system (Phase 2); Multi Party (MPTY) supplementary services - Stage 3".
[17] GSM 04.85 (ETS 300 569): "European digital cellular telecommunications
system (Phase 2); Closed User Group (CUG) supplementary services -
Stage 3".
[18] GSM 04.86 (ETS 300 570): "European digital cellular telecommunications
system (Phase 2); Advice of Charge (AoC) supplementary services - Stage 3".
[19] GSM 04.88 (ETS 300 571): "European digital cellular telecommunications
system (Phase 2); Call Barring (CB) supplementary services - Stage 3".
[20] GSM 04.90 (ETS 300 572): "European digital cellular telecommunications
system (Phase 2); Unstructured supplementary services operation - Stage 3".
[21] GSM 09.02 (ETS 300 599): "European digital cellular telecommunications
system (Phase 2); Mobile Application Part (MAP) specification".
1.3 Definitions and abbreviations
Abbreviations used in this ETS are listed in GSM 01.04.

---------------------- Page: 10 ----------------------

SIST ETS 300 529 E2:2003
Page 9
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
2 Activation, deactivation, registration, erasure, interrogation and invocation
2.1 General
Activation, deactivation, registration, erasure, interrogation and invocation are defined independently from a
particular supplementary service. Whether they are applicable to a particular supplementary service or not
is defined in the corresponding TS GSM 03.8x and 03.9x-series.
The invocation of a supplementary service is executed as described in the corresponding stage 2
description and always includes a MSC and a location register.
When a MSC receives a request for either activation/deactivation or registration/erasure or an
interrogation, it invokes one of the following procedures.
The MSC then can:
- contact only the current VLR (e.g. interrogation of a call forwarding conditional supplementary
service);
- contact only the HLR (e.g. interrogation of the supplementary service call forwarding unconditional);
- contact the HLR, after which the HLR updates the VLR (e.g. registration of a forwarding number for
a conditional call forwarding supplementary service).
Which of the above listed procedures is applied for a call independent supplementary service operation is
described in the corresponding TS GSM 03.8x and 03.9x-series.
Successful activation, deactivation, registration and erasure change the service state at the HLR. These
transitions (if applicable to a particular service) are defined in the GSM 03.8x and 03.9x-series. Note that
the HLR may also change the service state due to "HLR Induction" (see subclause 2.1.1).
In connection with supplementary service operations the served subscriber or remote subscribers may get
notifications from the network.
2.1.1 Definition of "state vectors"
In order to provide a tool to define service states the concept of a "state vector" is introduced. The state
vector is used to represent the state of the service in terms of four variables:
1) Provisioning State,
possible values are "Provisioned" or "Not Provisioned";
2) Registration State,
possible values are "Registered", "Erased", or "Not Applicable";
3) Activation State,
possible values are "Not Active", "Active and Operative" or "Active and Quiescent";
4) HLR Induction State,
possible values are "Induced" or "Not Induced".
The state vector represents the state of the service by using all four variables together. The state vector is
represented using the notation:
(Provisioning State, Registration State, Activation State, HLR Induction State)
e.g.: (Provisioned, Registered, Not Active, Not Induced).

---------------------- Page: 11 ----------------------

SIST ETS 300 529 E2:2003
Page 10
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Note that the state vector is a logical (not a physical) representation of the service state. Note also that
though some parts of the state vector are similar to elements of SS-Status the mapping between the state
vector and SS-Status is not one to one. The use of state vectors is not intended to specify any particular
implementation internally in a node. There is a relationship specified between the state vector and parts of
the transfer syntax. This relationship is not a direct one-to-one mapping.
The following text specifies the semantics of each variable in the state vector.
The three variables "Provisioning State", "Registration State" and "Activation State" are used to represent
the state of the service according to the normal behaviour based on service provider and user actions.
The "HLR Induction State" records whether or not the HLR has temporarily induced the service (e.g. if the
VLR does not support CUG, the HLR may induce an outgoing barring service). The Provisioning State,
Registration State and Activation State are not affected by HLR induction of a service.
Provisioning State
- has value "provisioned", if the subscriber has a subscription to the service;
- has value "Not Provisioned" otherwise.
Registration State
- has value "Not Applicable", if registration is not applicable to the service;
- has value "Registered", if registration is applicable, and there is registration data available;
- has value "Erased" otherwise.
Activation State
- has value "Active and Operative", if the service is in a state where it can be invoked (and this is not
due to HLR induction);
- has value "Active and Quiescent", if the service is in a state where it cannot be invoked, but where it
will automatically move to the "Active and Operative" state when conflicting conditions are removed;
- has value "Not Active" otherwise.
HLR Induction State
- has the value "Induced" if the HLR has induced the service (e.g. if the VLR does not support CUG,
the HLR may induce an outgoing barring service);
- has the value "Not Induced" otherwise.
For further information about how HLR induction applies to particular services refer to the GSM
03.8x and 03.9x-series.
2.1.2 Handling of service states at the HLR
Valid states (represented by state vectors) are defined on a service-by-service basis in the GSM 03.8x
and 03.9x-series. For each service the set of valid states represents the logical states that can exist in the
HLR. The HLR contains the master copy of service state information.

---------------------- Page: 12 ----------------------

SIST ETS 300 529 E2:2003
Page 11
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
2.1.2.1 Encoding of SS-Status
To send service state information to the VLR or the MS, the HLR often uses the SS-Status parameter.
This parameter contains four bits (referred to here as the "P bit", "R bit", "A bit" and "Q bit"). In a phase 2
context the HLR shall encode the SS-Status using the mapping defined in this subclause from the service
states to SS-Status.
If the HLR Induction State is "Not Induced" then:
- If the Provisioning State is "Provisioned", then the P bit shall be 1, otherwise the P bit shall be 0.
- If the Registration State is "Registered", the R bit shall be 1. If the Registration State is "Not
Registered" the R bit shall be 0. If the Registration State is "Not Applicable" the R bit shall be either
0 or 1.
- If the Activation State is "Active and Operative" the A bit shall be 1 and the Q bit shall be 0. If the
Activation State is "Active and Quiescent" the A bit shall be 1 and the Q bit shall be 1. If the
Activation State is "Not Active" the A bit shall be 0 and the Q bit shall be either 0 or 1.
If the HLR Induction State is "Induced" then the P bit shall be 1, the R bit shall be 0 or 1, the A bit shall be
1 and the Q bit shall be 0.
HLR Induction State "Not Induced" P bit R bit A bit Q bit
Provisioning State "Provisioned" 1
"Not Provisioned" 0
Registration State "Registered" 1
"Not Registered" 0
"Not Applicable" 0/1
Activation State "Active and Operative" 1 0
"Active and Quiescent" 1 1
"Not Active" 0 0/1
P bit R bit A bit Q bit
HLR Induction State "Induced" 1 0/1 1 0
Table 2.1: Encoding of the P, R, A and Q bits in the SS-Status parameter
2.1.2.2 Invocation of services at the HLR
If the service can be invoked at the HLR (e.g. to bar an incoming call) then invocation is possible only if the
Activation State is "Active and Operative". Note that the concept of HLR induction does not apply to
services invoked at the HLR as the HLR can invoke the effect of these services without needing to induce
them first.
2.1.3 Handling of SS-Status at the VLR
The VLR shall store sufficient information to support VLR based invocation, interrogation and notifications
from the VLR to the MS.
The VLR shall not check the internal consistency of SS-Status values received from the HLR (i.e. it shall
not impose any rules relating values of some bits in SS-Status to other bits). The VLR shall not check that
the SS-Status received from the HLR is valid according to the VLR's definition of the relevant service.

---------------------- Page: 13 ----------------------

SIST ETS 300 529 E2:2003
Page 12
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
2.1.3.1 Invocation of services at the VLR
The ability to invoke the service at the VLR (e.g. to forward a call, or create an MPTY call) is based on the
A and Q bits of SS-Status. The service can only be invoked if A=1 and Q=0. Other bits in SS-Status are
not relevant to invocation at the VLR.
2.1.3.2 Interrogation of the service at the VLR and notifications from VLR
If the VLR sends a notification or an interrogation result that includes an SS-Status parameter the VLR
shall set the P, R, A and Q bits to the same values received from the HLR. Unless stated otherwise in
individual service specifications, it the service is not provisioned and the VLR has not received a value for
SS-Status from the HLR then if the VLR has to send SS-Status for that service it shall set the P, R, A, and
Q bits to 0.
2.1.4 Handling of SS-Status at the MS
The MS has to interpret SS-Status values received from the network. The following information is provided
as guidance as to how to treat the SS-Status information:
- The P, A and Q bits are relevant for all phase 2 supplementary services for which the MS may
receive SS-Status information from the network.
- The value of the R bit is only relevant if registration is applicable to the supplementary service the
SS-Status relates to.
- The A and Q bits shall be treated as a pair with the following meanings assumed:
If A=1 and Q=0, then the service is "Active and Operative";
If A=1 and Q=1, then the service is "Active and Quiescent";
If A=0 and Q=0 or 1, then the service is deactivated.
- The MS may assume that if P=0 then the service is also deactivated (and if registration is applicable
erased).
- If registration is applicable to the service then the MS may assume that if R=0 then the service is
also deactivated.
2.2 Handling of call independent SS procedures with respect to basic service groups
A request for registration, erasure, activation, deactivation or interrogation of a supplementary service
always refers to a basic service group.
The basic service group may be either an elementary basic service group (defined in TS GSM 02.04) or a
collective basic service group (defined in TS GSM 02.30).
The following text and figure 2.1 describe the general handling of call independent SS procedures in the
destination entity with respect to basic service groups.
- The VLR or HLR (i.e. the destination entity) shall check the received request for general problems
(see figure 2.1 sheet 2 and sheet 3).
- In case of general error the procedure shall be terminated by sending an error towards the MS (see
figure 2.1 sheet 1).
- If there is no general problem, the HLR or VLR shall split the received basic service group (BSG)
into elementary basic service groups (EBSG) and continue with separate handling of each
elementary basic service group (see figure 2.1 sheet 1).
Note that the received basic service group may be an elementary basic service group. In this case
splitting is not required.

---------------------- Page: 14 ----------------------

SIST ETS 300 529 E2:2003
Page 13
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
- Elementary basic service groups shall be ignored if:
- there is no basic service provisioned in the group; or
- the supplementary service is not applicable for any basic service within this elementary basic
service group;
(see figure 2.1 sheet 4).
Note that in case the SS is either not provisioned or all the elementary basic service groups were
ignored a general error will be returned (see above).
For interrogation the following handling continues (see figure 2.1 sheet 4):
- For all other elementary basic service groups the information requested will be returned to the MS
and the procedure is terminated.
For registration/erasure and activation/deactivation the following handling continues (see figure 2.1
sheet 4):
- For all other elementary basic service groups the requested procedure will either be executed or
rejected due to interaction with other supplementary services.
- If the request cannot be accepted for any of these elementary basic service groups due to
interaction, the corresponding error will be returned and the procedure is terminated.
- If the request was executed for all of these elementary basic service groups an acknowledgement is
returned towards the MS and the procedure is terminated.
Note that this acknowledgement will include the same basic service group as received in the
request.
- In case the request is accepted for some but not for all of these elementary basic service groups,
partial acceptance will be signalled towards the MS and the procedure will be terminated.
The return errors for supplementary service operations and applicability of these errors are defined in
TS GSM 04.80. Detailed description of call independent handling for a specific supplementary service is
described in GSM 03.8x and 03.9x-series of technical specifications.
2.3 Exceptional handling of basic service codes
When an individual teleservice code or bearer service code is sent by an MS instead of an elementary
basic service group the network shall treat such a request as a request for the corresponding elementary
basic service group.
The response to such a request shall include the elementary basic service group code of this basic service
code if this is required by the protocol or application.

---------------------- Page: 15 ----------------------

SIST ETS 300 529 E2:2003
Page 14
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Process SS_REQUEST_WITH_BS_GROUP 311_211(1)
Figure 2.1 (sheet 1 of 4) idle Handling in HLR and VLR
   SS
idle
  request
  see sheets 2 BS:    Basic Service.
general
  and 3 BSG:  Basic Service group.
SS_request_
 EBSG: Elementary Basic Service group.
handling
 SS:    Supplementary Service.

  NOTE:   Only BS and SS included in
           the request are relevant.
yes
error
no
split
request to
EBSG
take
1 request of
first EBSG
 see sheet 4
specific
SS_request_
handling
yes
last
EBSG
no
error
no
yes
take successful
no
request of for any
next EBSG EBSG
yes
partial
acknowledge error
acceptance
1 idle
Figure 2.1 (sheet 1 of 4): Handling of call independent SS procedures with respect to basic service
groups

---------------------- Page: 16 ----------------------

SIST ETS 300 529 E2:2003
Page 15
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Procedure general_SS_request_handling 311_212(2)
 BS:   Basic Service.
Handling of the
Figure 2.1 (sheet 2 of 4)  BSG:  Basic Service Group.
entire request
 SS:   Supplementary Service.
no
SS supported
by this
entity
set error
yes
unexpected
data value
required
yes
parameter
missing
no
set error
data missing
irrelevant
yes
parameter
value
no
set error
unexpected
data value
no
request
applicable
for this SS
yes
set error
illegal SS
operation
yes
interrogation
no
no
SS
provisioned
set error
SS error
yes
status
1 2
Figure 2.1 (sheet 2 of 4): Handling of call independent SS procedures with respect to basic service
groups

---------------------- Page: 17 ----------------------

SIST ETS 300 529 E2:2003
Page 16
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Procedure general_SS_request_handling 311_213(2)
1 2
Figure 2.1 (sheet 3 of 4)
any BS
no
provisioned and
applicable within
the BSG
set error
yes BS Not
Provisioned
SS requiring
no
password or
password
registration
yes
To process PW1
as specified in TS GSM 03.11
SS_request
Waiting for indications from
process PW1, PW2, PW3 or PW4
Wait_for_PW
as specified in TS GSM 03.11.
SS Get New_ SS
SS Get SS Get_ SS User_
Password_ Password_
Password New Password Errors
Again Changed
SS Get SS
Set ERROR
Password Acknowledge
Wait for
password
SS Get
Password_
Ack
To processes
PW1, PW2, PW3 or PW4
SS Receive_
specified in TS GSM 03.11.
Password
Wait_for_PW
Figure 2.1 (sheet 3 of 4): Handling of call independent SS procedures with respect to basic service
groups

---------------------- Page: 18 ----------------------

SIST ETS 300 529 E2:2003
Page 17
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
Procedure specific_SS_request_handling 311_214(1)
Figure 2.1 (sheet 4 of 4) Handling of elementary BS groups
 BS:    Basic Service
 EBSG:  Elementary Basic Service Group
 SS:    Supplementary Service
any BS
no
provisioned within
the EBSG
yes
SS applicable no
for any BS within
this EBSG
yes
yes
interrogation
no
incompatible
yes
with other SS
for this EBSG
no
execute set
set error
requested SS info
SS incompatibility
procedure for EBSG
NOTE: Execution of the procedure and setting of SS info for EBSGs is
      described in the GSM 03.8x and 03.9x series of technical specifications.
Figure 2.1 (sheet 4 of 4): Handling of call independent SS procedures with respect to basic service
groups

---------------------- Page: 19 ----------------------

SIST ETS 300 529 E2:2003
Page 18
ETS 300 529: October 1995 (GSM 03.11 version 4.9.1)
3 Password handling
3.1 General
Some suppleme
...