SIST ETS 300 549 E1:2003

Digital cellular telecommunications system (Phase 2) (GSM); Unstructured Supplementary Service Data (USSD); Stage 2 (GSM 03.90)

...

Evropski digitalni celični telekomunikacijski sistem (faza 2) – Nestrukturirani podatki o dopolnilni storitvi (USSD) – Stopnja 2 (GSM 03.90)

General Information

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 33.070.50 - Global System for Mobile Communication (GSM)
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 549 ed.1 (1994-11) - Digital cellular telecommunications system (Phase 2) (GSM); Unstructured Supplementary Service Data (USSD); Stage 2 (GSM 03.90)

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ETS 300 549 E1:2003
01-december-2003
(YURSVNLGLJLWDOQLFHOLþQLWHOHNRPXQLNDFLMVNLVLVWHPID]D±1HVWUXNWXULUDQL
SRGDWNLRGRSROQLOQLVWRULWYL866'±6WRSQMD*60
Digital cellular telecommunications system (Phase 2) (GSM); Unstructured
Supplementary Service Data (USSD); Stage 2 (GSM 03.90)
Ta slovenski standard je istoveten z: ETS 300 549 Edition 1
ICS:
33.070.50 Globalni sistem za mobilno Global System for Mobile
telekomunikacijo (GSM) Communication (GSM)
SIST ETS 300 549 E1:2003 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

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

SIST ETS 300 549 E1:2003

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

SIST ETS 300 549 E1:2003
EUROPEAN ETS 300 549
TELECOMMUNICATION March 1995
STANDARD
Source: ETSI TC-SMG Reference: DE/SMG-030390P
ICS: 33.060.30
European digital cellular telecommunications system, Global System for Mobile communications
Key words:
(GSM)
European digital cellular telecommunications system (Phase 2);
Unstructured Supplementary Service Data (USSD) - Stage 2
(GSM 03.90)
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 549 E1:2003
Page 2
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
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 549 E1:2003
Page 3
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Contents
Foreword.5
1 Scope .7
2 Normative references .7
3 Definitions and abbreviations.8
4 Cross phase compatibility .8
5 Network initiated unstructured supplementary service.9
5.1 Handling of network initiated USSD.9
5.2 Functions and information flows.9
5.2.1 Invoking unstructured SS operation from the HLR .9
5.2.2 Invoking unstructured SS operation from the VLR .10
5.2.3 Invoking unstructured SS operation from the MSC .10
5.2.4 Forwarding USSD operations.10
5.2.5 Handling of unstructured SS operation at the MS .11
5.3 Information stored in the HLR.19
5.4 Information stored in the VLR.19
5.5 Handover.19
5.6 Cross-phase compatibility.19
6 Mobile initiated unstructured supplementary service data.20
6.1 Handling of mobile initiated USSD.20
6.2 Functions and information flows.20
6.2.1 Handling of USSD request at MS.20
6.2.2 Handling of USSD request at MSC.20
6.2.3 Handling of USSD request at VLR.21
6.2.4 Handling of USSD request at HLR.21
6.2.5 Processing the USSD request . 21
6.3 Information stored in the HLR.35
6.4 Information stored in the VLR.35
6.5 Handover.35
6.6 Cross-phase compatibility.35
History.36

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

SIST ETS 300 549 E1:2003
Page 4
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Blank page

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

SIST ETS 300 549 E1:2003
Page 5
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
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) and is
now submitted for the Voting phase of the ETSI standards approval procedure.
This ETS describes the unstructured supplementary service operation within the European digital cellular
telecommunications system (Phase 2).
This ETS corresponds to GSM Technical Specification (GSM-TS) GSM 03.90, version 4.0.3.
Reference is made within this ETS to GSM-TSs.
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.

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

SIST ETS 300 549 E1:2003
Page 6
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Blank page

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

SIST ETS 300 549 E1:2003
Page 7
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
1 Scope
This specification gives the stage 2 description of Unstructured Supplementary Service Data (USSD).
The unstructured supplementary service data (USSD) mechanism allows the MS user and a PLMN
operator defined application to communicate in a way which is transparent to the MS and to intermediate
network entities. The mechanism allows development of PLMN specific supplementary services. The
following diagram shows how handling of USSD is carried out, independently of the applications.
  USERUSER
   ‡
�˝˝˝˝˝�˝˝˝˝˝»  �˝˝˝˝˝˝˝˝˝˝˝»  �˝˝˝˝˝˝˝˝˝˝˝»  �˝˝˝˝˝˝˝˝˝˝˝»
”MS  ‡   ”  ”MSC    ”  ”VLR    ”  ”HLR    ”
” �˜˜˜`˜˜˜¿ ”  ” �˜˜˜˜˜˜˜¿ ”  ” �˜˜˜˜˜˜˜¿ ”  ” �˜˜˜˜˜˜˜¿ ”
” ‡ MMI ‡ ”  ” ‡Applica‡ ”  ” ‡Applica‡ ”  ” ‡Applica‡ ”
” ‡    ‡ ”  ” ‡ tions ‡ ”  ” ‡ tions ‡ ”  ” ‡ tions ‡ ”
” �˜˜˜´˜˜˜� ”  ” �˜˜˜´˜˜˜� ”  ” �˜˜˜´˜˜˜� ”  ” �˜˜˜´˜˜˜� ”
”   ‡   ”  ”   ‡   ”  ”   ‡   ”  ”   ‡   ”
” �˜˜˜`˜˜˜¿ ”  ” �˜˜˜`˜˜˜¿ ”  ” �˜˜˜`˜˜˜¿ ”  ” �˜˜˜`˜˜˜¿ ”
” ‡ USSD ‡ ”  ” ‡ USSD ‡ ”  ” ‡ USSD ‡ ”  ” ‡ USSD ‡ ”
” ‡Handlerˆ˜�˜˜˜�˜·Handlerˆ˜�˜˜˜�˜·Handlerˆ˜�˜˜˜�˜·Handler‡ ”
” �˜˜˜˜˜˜˜� ”  ” �˜˜˜˜˜˜˜� ”  ” �˜˜˜˜˜˜˜� ”  ” �˜˜˜˜˜˜˜� ”
¨˝˝˝˝˝˝˝˝˝˝˝…  ¨˝˝˝˝˝˝˝˝˝˝˝…  ¨˝˝˝˝˝˝˝˝˝˝˝…  ¨˝˝˝˝˝˝˝˝˝˝˝…
Figure 1.1: Handling of USSD
This specification defines the requirements for handling USSD at the MS and network entities. It does not
include specification of particular applications, nor does it specify how a particular application is selected.
Where more than one application exists at a network entity, routing of messages to the correct application
is carried out by the applications. The MMI for USSD is specified in TS GSM 02.30.
USSD may be initiated by the mobile station user, or by the network in the following ways:
- Network initiated USSD (section 1);
- Mobile initiated USSD (section 2).
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 telecommunication system
(Phase 2); Definitions, abbreviations and acronyms".
[2] GSM 02.04 (ETS 300 503): "European digital cellular telecommunication system
(Phase 2); General on supplementary services".
[3] GSM 02.30 (ETS 300 511): "European digital cellular telecommunication system
(Phase 2); Man-Machine Interface (MMI) of the Mobile Station (MS)".

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

SIST ETS 300 549 E1:2003
Page 8
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
3 Definitions and abbreviations
In addition to those below, abbreviations used in this specification are listed in GSM 01.04.
AI Application Initiated
MI Mobile Initiated
USSD Unstructured Supplementary Service Data
4 Cross phase compatibility
The phase 1 series of GSM specifications defined the signalling protocol which may be used, but they did
not specify the operation of USSD as a service.
The main body of this specification assumes that the mobile station and all network entities comply with
this phase of USSD. In order to minimize any possible problems between a phase 1 implementation of
USSD and this phase, sections 5.6 and 6.6 define the additional requirements for when one or more entity
complies with the phase 1 USSD specification for network initiated and mobile initiated USSD respectively.

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

SIST ETS 300 549 E1:2003
Page 9
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
5 Network initiated unstructured supplementary service
5.1 Handling of network initiated USSD
The network (MSC, VLR or HLR) can at any time send a USSD operation towards an MS. This operation
may be either a request (asking the MS to provide information) or a notification (requiring no information in
the response from the MS). No prior provision of USSD is required, although provision of services which
make use of USSD may be required. All USSD requests, notifications and responses (except responses to
notifications) contain the USSD string, an alphabet indicator and language indicator, as defined in TS GSM
02.04.
5.2 Functions and information flows
The following text describes the handling of network initiated USSD. Diagrammatic representations are as
follows:
figure 5.1 SDL for USSD invocation (HLR, VLR, MSC);
figure 5.2 SDL for forwarding of USSD operations (VLR, MSC);
figure 5.3 SDL for MS;
figure 5.4 Call flow for successful single USSD request;
figure 5.5 Call flow for successful single USSD notification;
figure 5.6 Call flow for successful multiple USSD requests;
figure 5.7 Call flow for failed USSD request.
5.2.1 Invoking unstructured SS operation from the HLR
When an application in the HLR is to send a USSD request or notification to an MS, it shall set up a
transaction to the VLR where the subscriber is currently registered and send the operation to the VLR. It
shall then await a response. The HLR is responsible for controlling the transaction, and shall therefore
normally release the transaction when it receives a response from the VLR. The HLR may also release the
transaction before receiving a response if necessary (eg if an application timer expires).
If an application in the HLR needs to send further operations to the same MS as part of the same
application, it may continue to use the same transaction until all operations are completed (see figure 5.6).
If a different transaction is to be used for a subsequent operation, the HLR shall release the first
transaction before starting the next.
If the VLR releases the transaction at any time (eg due to user clearing), the HLR shall inform the
application and terminate the USSD operation.
See section 5.2.4 for forwarding of an HLR invoked operation by the VLR and MSC.

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

SIST ETS 300 549 E1:2003
Page 10
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
5.2.2 Invoking unstructured SS operation from the VLR
When an application in the VLR is to send a USSD request or notification to an MS, it shall set up a
transaction to the MSC where the subscriber is currently registered and send the operation to the MSC. It
shall then await a response. The VLR is responsible for controlling the transaction, and shall therefore
normally release the transaction when it receives a response from the MSC. The VLR may also release
the transaction before receiving a response if necessary (eg if an application timer expires).
If an application in the VLR needs to send further operations to the same MS as part of the same
application, it may continue to use the same transaction until all operations are completed. If a different
transaction is to be used for a subsequent operation, the VLR shall release the first transaction before
starting the next.
See section 5.2.4 for forwarding of a VLR invoked operation by the MSC.
If the MSC releases the transaction at any time (eg due to the user clearing), the VLR shall inform the
application and terminate the USSD operation.
5.2.3 Invoking unstructured SS operation from the MSC
When an application in the MSC is to send a USSD request or notification to an MS, it shall set up a
transaction to the MS where the subscriber is currently registered and send the operation to the MS. It
shall then await a response. The MSC is responsible for controlling the transaction, and shall therefore
normally release the transaction when it receives a response from the MS. The MSC may also release the
transaction before receiving a response if necessary (eg if an application timer expires).
If an application in the MSC needs to send further operations to the same MS as part of the same
application, it may continue to use the same transaction until all operations are completed. If a different
transaction is to be used for a subsequent operation, the VLR shall release the first transaction before
starting the next.
If the MS releases the transaction at any time (eg due to the user clearing), the MSC shall inform the
application and terminate the USSD operation.
NOTE: MSC invoked USSD is only likely to be used for call related operations, where the
application is controlling a call to or from the MS.
5.2.4 Forwarding USSD operations
The VLR may any time receive a USSD operation fm the HLR. If the subscriber can be contacted, the VLR
shall set up a transaction to the MSC and forward the operation unchanged. Any further information
exchange between the HLR and MSC shall be transparent to the VLR. When one transaction is released,
the VLR shall release the other. If an error is received from the MSC, the VLR shall release the transaction
to the HLR.
The MSC may at any time receive an USSD operation from the VLR. If the subscriber can be contacted,
the MSC shall set up a transaction to the MS and forward the operation unchanged. Any further
information exchange between the VLR and MS shall be transparent to the MSC. When one transaction is
released, the MSC shall release the other. If an error is received from the MS, the MSC shall release the
transaction to the VLR.

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

SIST ETS 300 549 E1:2003
Page 11
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
5.2.5 Handling of unstructured SS operation at the MS
The MS may at any time receive a USSD operation (request or notification) from the MSC.
If the MS receives a USSD transaction while another USSD transaction (network or mobile initiated) or a
non-call related supplementary service transaction is in progress, the MS shall reject the new transaction.
If the MS receives a USSD operation when it is in a state where the MMI required is not possible (eg
during dialling) it shall reject the operation.
If the MS does not support the alphabet indicated in the USSD operation, it shall inform the network.
If the MS is in a state where it can handle the operation, it shall process the operation as follows:
- For a USSD request, the MS shall display the text provided and await user input. If the user enters a
response, the MS shall return the response to the MSC, maintaining the transaction. If the user
requests release of the transaction, the MS shall release the transaction. See TS GSM 02.30 for
details of the MMI.
- For a USSD notification, the MS shall display the text provided and send back a response.
After sending the response to a USSD operation, the MS shall wait for the network to release the
transaction. If, while awaiting this release, the MS receives any further USSD operations, it shall process
them in the normal way.

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

SIST ETS 300 549 E1:2003
Page 12
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Process USSD_NI1 390_51(1)
INPUTS AND OUTPUTS

Figure 5.1 idle
Source/destination of messages
shown to/from the right is
the application.

Source/destination of messages
shown to/from the left depends
  USSD USSD
on the entity being described,
  notify request
as follows:

  Entity  To/From

  HLR   VLR
no no
MS MS
  VLR   MSC
reachable reachable
  MSC   MS
yes yes
USSD USSD
  error  error
notify request
NW
idle wait user idle
response
  USSD
  release  release  error
  response
  USSD
  release  release  error
  response
wait
for idle
application
  USSD  USSD
  release  release
  notify  request
USSD USSD
  release release
notify request
NW
wait user idle
response
Figure 5.1: Network initiated USSD invoked at HLR, VLR or MSC

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

SIST ETS 300 549 E1:2003
Page 13
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Process USSD_NI2 390_52(1)
Figure 5.2 idle
INPUTS AND OUTPUTS

Source/destination of messages
depends on the entity being
described, as follows:
  USSD USSD
  notify request
  Entity  Left    Right

  VLR   MSC   HLR
  MSC   MS     VLR
no no
MS MS
reachable reachable
yes yes
USSD USSD
  error  error
notify request
forwarding
idle idle
wait user
  USSD
  release  release  error
  response
  USSD
  release  release  error
  response
forwarding
idle
wait application
  USSD  USSD
  release  release
  notify  request
USSD USSD
  release release
notify request
forwarding
idle
wait user
Figure 5.2: Network initiated USSD forwarding at VLR or MSC

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

SIST ETS 300 549 E1:2003
Page 14
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
Process USSD_NI3 390_53(1)
idle Figure 5.3
1 2
  USSD  USSD
  notify  request
INPUTS AND OUTPUTS

Source/destination of messages
shown to/from the left is
no no
the MS MMI.
alphabet alphabet
supported supported
Source/destination of messages
shown to/from the right is
yes yes
the network.
no no
valid valid
state state
yes yes
USSD USSD
  error  error
notify request
MS
  USSD
idle wait user idle
  response
response
  USSD
  release  release
  response
  USSD
  release  release
  response
wait
network idle
action
  USSD  USSD
  release  release
  notify  request
  release  release
1 2 idle
Figure 5.3: Network initiated USSD at MS

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

SIST ETS 300 549 E1:2003
Page 15
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
 MS         MSC         VLR         HLR
�˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡HLR initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡USSD request ‡   ‡
‡   ‡       ‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡
‡   ‡       ‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡  Release ‡   ‡
‡   ‡       ‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡VLR initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡USSD request ‡   ‡       ‡   ‡
‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡  Release ‡   ‡       ‡   ‡
‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡MSC initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD request ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡  Release ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
Figure 5.4: Information flow for USSD request (Single Operation)

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

SIST ETS 300 549 E1:2003
Page 16
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
 MS         MSC         VLR         HLR
�˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡HLR initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡USSD notify ‡   ‡
‡   ‡       ‡   ‡USSD notify ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡USSD notify ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡
‡   ‡       ‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡  Release ‡   ‡
‡   ‡       ‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡VLR initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡USSD notify ‡   ‡       ‡   ‡
‡   ‡USSD notify ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡  Release ‡   ‡       ‡   ‡
‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡MSC initiated   ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD notify ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡  Release ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
Figure 5.5: Information flow for USSD notification (Single Operation)

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

SIST ETS 300 549 E1:2003
Page 17
ETS 300 549: March 1995 (GSM 03.90 version 4.0.3)
 MS         MSC         VLR         HLR
�˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿       �˜˜˜˜˜¿
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡USSD request ‡   ‡
‡   ‡       ‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡
‡   ‡       ‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
:   :       :   :       :   :       :   :
:   :       :   :       :   :       :   :
:   :       :   :       :   :       :   :
‡   ‡       ‡   ‡       ‡   ‡USSD request ‡   ‡
‡   ‡       ‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡USSD request ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡
‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡USSD response‡   ‡       ‡   ‡       ‡   ‡
‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡       ‡   ‡
‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡USSD response‡   ‡
‡   ‡       ‡   ‡       ‡   ˆ˜˜˜˜˜˜˜˜˜˜˜˜>‡   ‡
‡   ‡       ‡   ‡       ‡   ‡       ‡   ‡
‡   ‡       ‡   ‡       ‡   ‡  Release ‡   ‡
‡   ‡       ‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
‡   ‡  Release ‡   ‡<˜˜˜˜˜˜˜˜˜˜˜˜·   ‡
...