Etsi TS 100 549

ETSI TS 100 549 V7.0.
0 (1999-08)
Technical Specification
Digital cellular telecommunications system (Phase 2+);

Unstructured Supplementary Service Data (USSD) - Stage 2
(GSM 03.90 version 7.0.0 Release 1998)
GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS
(GSM 03.90 version 7.0.0 Release 1998) 2 ETSI TS 100 549 V7.0.0 (1999-08)
Reference
RTS/SMG-030390Q7 (53003i03.PDF)
Keywords
Digital cellular telecommunications system,
Global System for Mobile communications (GSM)
ETSI
Postal address
F-06921 Sophia Antipolis Cedex - FRANCE
Office address
650 Route des Lucioles - Sophia Antipolis
Valbonne - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Internet
secretariat@etsi.fr
Individual copies of this ETSI deliverable
can be downloaded from
http://www.etsi.org
If you find errors in the present document, send your
comment to: editor@etsi.fr
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 1999.

All rights reserved.
ETSI
Contents
Intellectual Property Rights ............................................................................................................................... 4
Foreword ............................................................................................................................................................ 4
1 Scope........................................................................................................................................................ 5
2 References................................................................................................................................................ 5
3 Abbreviations........................................................................................................................................... 6
4 Cross phase compatibility........................................................................................................................ 6
5 Network initiated unstructured supplementary service ........................................................................... 6
5.1 Handling of network initiated USSD ................................................................................................................. 6
5.2 Functions and information flows........................................................................................................................ 6
5.2.1 Invoking unstructured SS operation from the HLR...................................................................................... 6
5.2.2 Invoking unstructured SS operation from the VLR...................................................................................... 7
5.2.3 Invoking unstructured SS operation from the MSC ..................................................................................... 7
5.2.4 Forwarding USSD operations ...................................................................................................................... 7
5.2.5 Handling of unstructured SS operation at the MS ........................................................................................ 8
5.3 Information stored in the HLR......................................................................................................................... 15
5.4 Information stored in the VLR......................................................................................................................... 15
5.5 Handover ......................................................................................................................................................... 15
5.6 Cross-phase compatibility................................................................................................................................ 16
6 Mobile initiated unstructured supplementary service data.................................................................... 16
6.1 Handling of mobile initiated USSD ................................................................................................................. 16
6.2 Functions and information flows...................................................................................................................... 16
6.2.1 Handling of USSD request at MS .............................................................................................................. 16
6.2.2 Handling of USSD request at MSC............................................................................................................ 17
6.2.3 Handling of USSD request at VLR ............................................................................................................ 17
6.2.4 Handling of USSD request at HLR ............................................................................................................ 17
6.2.5 Processing the USSD request ..................................................................................................................... 17
6.3 Information stored in the HLR......................................................................................................................... 30
6.4 Information stored in the VLR......................................................................................................................... 30
6.5 Handover ......................................................................................................................................................... 31
6.6 Cross-phase compatibility................................................................................................................................ 31
Annex A (informative): Change Request History ............................................................................... 32

History.............................................................................................................................................................. 33
ETSI
Intellectual Property Rights

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information
pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found
in SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect
of ETSI standards", which is available free of charge from the ETSI Secretariat. Latest updates are available on the
ETSI Web server (http://www.etsi.org/ipr).
Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee
can be given as to the existence of other IPRs not referenced in SR 000 314 (or the updates on the ETSI Web server)
which are, or may be, or may become, essential to the present document.
Foreword
This Technical Specification (TS) has been produced by the Special Mobile Group (SMG).
The present document defines the stage 2 description of Unstructured Supplementary Service Data (USSD) within the
digital cellular telecommunications system.
The contents of the present document is subject to continuing work within SMG and may change following formal SMG
approval. Should SMG modify the contents of the present document it will be re-released with an identifying change of
release date and an increase in version number as follows:
Version 7.x.y
where:
7 indicates Release 1998 of GSM Phase 2+
x the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates,
etc.
y the third digit is incremented when editorial only changes have been incorporated in the specification.
ETSI
1 Scope
The present document gives the stage 2 description of Unstructured Supplementary Service Data (USSD).
The unstructured supplementary service data (USSD) mechanism allows the Mobile Station (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.
86(5
·
ÅÁÁÁÁÁÛÁÁÁÁÁÈ ÅÁÁÁÁÁÁÁÁÁÁÁÈ ÅÁÁÁÁÁÁÁÁÁÁÁÈ ÅÁÁÁÁÁÁÁÁÁÁÁÈ
Â06 · Â Â06& Â Â9/5 Â Â+/5 Â
Â ¸¶¶¶¿¶¶¶¹ Â Â ¸¶¶¶¶¶¶¶¹ Â Â ¸¶¶¶¶¶¶¶¹ Â Â ¸¶¶¶¶¶¶¶¹ Â
Â · 00, · Â Â ·$SSOLFD· Â Â ·$SSOLFD· Â Â ·$SSOLFD· Â
Â · · Â Â · WLRQV · Â Â · WLRQV · Â Â · WLRQV · Â
Â º¶¶¶¾¶¶¶» Â Â º¶¶¶¾¶¶¶» Â Â º¶¶¶¾¶¶¶» Â Â º¶¶¶¾¶¶¶» Â
Â · Â Â · Â Â · Â Â · Â
Â ¸¶¶¶¿¶¶¶¹ Â Â ¸¶¶¶¿¶¶¶¹ Â Â ¸¶¶¶¿¶¶¶¹ Â Â ¸¶¶¶¿¶¶¶¹ Â
Â · 866' · Â Â · 866' · Â Â · 866' · Â Â · 866' · Â
Â ·+DQGOHU¼¶Ü¶¶¶Ü¶½+DQGOHU¼¶Ü¶¶¶Ü¶½+DQGOHU¼¶Ü¶¶¶Ü¶½+DQGOHU· Â
Â º¶¶¶¶¶¶¶» Â Â º¶¶¶¶¶¶¶» Â Â º¶¶¶¶¶¶¶» Â Â º¶¶¶¶¶¶¶» Â
ËÁÁÁÁÁÁÁÁÁÁÁÎ ËÁÁÁÁÁÁÁÁÁÁÁÎ ËÁÁÁÁÁÁÁÁÁÁÁÎ ËÁÁÁÁÁÁÁÁÁÁÁÎ
Figure 1.1: Handling of USSD
The present document 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 USSD handler.
The MMI for USSD is specified in GSM 02.30 and GSM 02.90. The alphabet indicator and the data coding scheme are
defined in GSM 03.38.
USSD may be initiated by the MS user, or by the network in the following ways:
- Network initiated USSD (clause 1);
- Mobile initiated USSD (clause 2).
2 References
The following documents contain provisions which, through reference in this text, constitute provisions of the present
document.
• References are either specific (identified by date of publication, edition number, version number, etc.) or
non-specific.
• For a specific reference, subsequent revisions do not apply.
• For a non-specific reference, the latest version applies.
• A non-specific reference to an ETS shall also be taken to refer to later versions published as an EN with the same
number.
• For this Release 1998 document, references to GSM documents are for Release 1998 versions (version 7.x.y).
[1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and
acronyms".
[2] GSM 02.30: "Digital cellular telecommunications system (Phase 2+); Man-Machine Interface
(MMI) of the Mobile Station (MS)".
[3] GSM 02.90: "Digital cellular telecommunications system (Phase 2+); Unstructured Supplementary
Service Data (USSD) - Stage 1".
ETSI
[4] GSM 03.38: "Digital cellular telecommunications system (Phase 2+); Alphabets and
language-specific information".
3 Abbreviations
In addition to those below, abbreviations used in the present document are listed in GSM 01.04 [1].
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 the present document assumes that the MS 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, subclauses 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.
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.
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 Information flow for successful single USSD request;
Figure 5.5 Information flow for successful single USSD notification;
Figure 5.6 Information flow for successful multiple USSD requests;
Figure 5.7 Information 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
ETSI
response from the VLR. The HLR may also release the transaction before receiving a response if necessary (e.g. 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 (e.g. due to user clearing), the HLR shall inform the application and
terminate the USSD operation.
See subclause 5.2.4 for forwarding of an HLR invoked operation by the VLR and MSC.
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 (e.g. if an
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 subclause 5.2.4 for forwarding of a VLR invoked operation by the MSC.
If the MSC releases the transaction at any time (e.g. due to the user clearing), the VLR shall inform the application and
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 (e.g. if an
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 (e.g. due to the user clearing), the MSC shall inform the application and
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 from 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.
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.
ETSI
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 (e.g. 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 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.
ETSI
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
USSD USSD shown to/from the left depends
notify request on the entity being described,
as follows:
Entity To/From
no no HLR VLR
MS MS VLR MSC
reachable reachable MSC MS
yes yes
RELEASE USSD USSD RELEASE

(error) notify request (error)
NW
idle wait user idle
response
error USSD release release

response

response
wait
for idle
application
USSD USSD release release

notify request

notify request
NW
wait user idle
response
Figure 5.1: Network initiated USSD invoked at HLR, VLR or MSC
ETSI
Figure 5.2 idle

INPUTS AND OUTPUTS
depends on the entity being
USSD USSD described, as follows:
notify request
Entity Left Right
VLR MSC HLR

MSC MS VLR
no MS MS no
reachable reachable
yes yes
RELEASE USSD USSD RELEASE

(error) notify request (error)
idle forwarding idle

wait user

response

response
forwarding idle
wait application

notify request

notify request
forwarding idle
wait user
Figure 5.2: Network initiated USSD forwarding at VLR or MSC
ETSI
idle Figure 5.3
1 2
USSD USSD
notify request
INPUTS AND OUTPUTS
shown to/from the left is
no alphabet alphabet no the MS MMI.
supported supported
yes yes the network.
no valid valid no
state state
yes yes
error USSD USSD error

notify request
wait MS wait
network USSD wait user network
action response response action
USSD release release

response
USSD release release

response
wait
network idle
action

notify request
release release
1 2 idle
Figure 5.3: Network initiated USSD at MS
ETSI
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| | | |
| | | +------------>| | | |
| | | | | | | |
| | | | Release | | | |
| | Release | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|MSC initiated | | | | | |
| | | | | | | |
| |USSD request | | | | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | | | | | |
| | Release | | | | | |
| |<------------| | | | | |
| | | | | | | |
Figure 5.4: Information flow for USSD request (Single Operation)
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
|HLR initiated | | | | | |
| | | | | | | |
| | | | | |USSD notify | |
| | | |USSD notify | |<------------| |
| |USSD notify | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| |USSD response| | | |
| | | +------------>| |USSD response| |
| | | | | +------------>| |
| | | | | | | |
| | | | | | Release | |
| | | | Release | |<------------| |
| | Release | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|VLR initiated | | | | | |
| | | | | | | |
| | | |USSD notify | | | |
| |USSD notify | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| |USSD response| | | |
| | | +------------>| | | |
| | | | | | | |
| | | | Release | | | |
| | Release | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|MSC initiated | | | | | |
| | | | | | | |
| |USSD notify | | | | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | | | | | |
| | Release | | | | | |
| |<------------| | | | | |
| | | | | | | |
Figure 5.5: Information flow for USSD notification (Single Operation)
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| |USSD response| | | |
| | | +------------>| |USSD response| |
| | | | | +------------>| |
| | | | | | | |
: : : : : : : :
: : : : : : : :
: : : : : : : :
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| |USSD response| | | |
| | | +------------>| |USSD response| |
| | | | | +------------>| |
| | | | | | | |
| | | | | | Release | |
| | | | Release | |<------------| |
| | Release | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
Figure 5.6: Information flow for HLR initiated USSD request (Multiple Operation On Same
Transaction)
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
|VLR cannot contact subscriber | | | |
| | | | | | | |
| | | | | |<------------| |
| | | | | | | |
| | | | | | Error | |
| | | | | +------------>| |
| | | | | | | |
| | | | | | | |
|MSC cannot contact subscriber | | | |
| | | | | | | |
| | | |USSD request | |<------------| |
| | | |<------------| | | |
| | | | | | | |
| | | | Error | | | |
| | | +------------>| | Error | |
| | | | | +------------>| |
| | | | | | | |
| | | | | | | |
|Error detected at MS | | | | |
| | | | | | | |
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | Error | | | | | |
| +------------>| | Error | | | |
| | | +------------>| | Error | |
| | | | | +------------>| |
| | | | | | | |
| | | | | | | |
|MS clears transaction | | | | |
| | | | | | | |
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | Release | | | | | |
| +------------>| | Release | | | |
| | | +------------>| | Release | |
| | | | | +------------>| |
| | | | | | | |
Figure 5.7: Information flow for failed USSD request
5.3 Information stored in the HLR

The HLR shall not store any information specific to the use of USSD, although information may be stored for services
which are offered by USSD applications.
5.4 Information stored in the VLR

The VLR shall not store any information specific to the use of USSD, although information may be stored for services
5.5 Handover
Handover will have no impact on the operation of this service.
ETSI
5.6 Cross-phase compatibility

Network initiated USSD shall not be permitted if the MS or any network entity involved in the operation is of Phase 1.
If, when setting up a transaction, a network entity discovers that the other end is of Phase 1, it shall reject the request and
release the transaction being set up.
6 Mobile initiated unstructured supplementary service

data
6.1 Handling of mobile initiated USSD

A MS can at any time initiate a USSD request to the network. No prior provision of the service is required, although
provisioning of services which make use of USSD may be required. All USSD messages (requests and responses),
contain the USSD string, an alphabet indicator and language indicator.
6.2 Functions and information flows

The following text describes the handling of mobile network initiated USSD. Diagrammatic representations are as
follows:
Figure 6.1 SDL, request from user at MS;
Figure 6.2 SDL, request from MS at MSC;
Figure 6.3 SDL, request from application at MSC;
Figure 6.4 SDL, request from MSC at VLR;
Figure 6.5 SDL, request from application at VLR;
Figure 6.6 SDL, request from VLR at HLR;
Figure 6.7 Information flow, no further information required;
Figure 6.8 Information flow, further information required;
Figure 6.9 Information flow for failed USSD request.
6.2.1 Handling of USSD request at MS

When the user makes a request which the MS determines is to make use of USSD, the MS shall set up a transaction to
the network, send the request to the MSC and await a response. When the MS receives the response, it shall display the
information contained to the user.
While awaiting the response, the MS may receive a network initiated USSD request or notification on the same
transaction. If this occurs, the MS shall process that operation (see section 1) and continue to await the response to the
mobile initiated request.
If, when the MS determines that a user request is to make use of USSD, the MS is already involved in a USSD or a non-
call related supplementary service transaction, the MS shall reject the request.
ETSI
6.2.2 Handling of USSD request at MSC

When an MSC receives a USSD request containing an HPLMN service code, it shall set up a transaction to the VLR and
forward the request unchanged. If this forwarding fails, an error shall be returned to the MS. The MSC shall be
transparent to any further requests or responses (in either direction) for that transaction, passing them between the MS
and VLR without taking any action. When one transaction is released (MS-MSC or MSC-VLR), the MSC shall release
the other.
If an HPLMN service code is not included, the MSC shall process the request locally (see section 6.2.5).
If the MSC does not support the alphabet used in a USSD request, it shall set up a transaction to the VLR and forward
the request unchanged, in the same way as when a HPLMN service code is received.
6.2.3 Handling of USSD request at VLR

When a VLR receives a USSD request containing an HPLMN service code and the user is not in the HPLMN, it shall
set up a transaction to the HLR and forward the request unchanged. If this forwarding fails, an error shall be returned to
the MS. The VLR shall be transparent to any further requests or responses (in either direction) for that transaction,
passing them between the MSC and HLR without taking any action. When one transaction is released (MSC-VLR or
VLR-HLR), the VLR shall release the other.
If an HPLMN service code is not included, or the user is in the HPLMN, the VLR shall process the request locally (see
subclause 6.2.5).
If the VLR does not support the alphabet used in a USSD request, it shall set up a transaction to the HLR and forward
the request unchanged, in the same way as when a HPLMN service code is received and the user is not in the HPLMN.
6.2.4 Handling of USSD request at HLR

An HLR shall always process a USSD request locally (see subclause 6.2.5).
If the HLR does not support the alphabet used in a USSD request, it shall inform the MS and release the transaction.
6.2.5 Processing the USSD request

When a network entity is to process a USSD request locally, the request shall be handled by an appropriate application.
The location, nature and contents of USSD applications is, by definition, service provider and network operator
dependent, but may include:
- Setting up or releasing signalling and/or speech channels;
- Passing the request to another network entity (unchanged or changed);
- Passing a different USSD request to another network entity;
and/or
- Requesting further information from the MS (one or more times).
Upon completion of handling the request, the network entity shall respond to the request and release the transaction.
ETSI
Process USSD_MI1 390_61(1)
Figure 6.1 idle
INPUTS AND OUTPUTS

USSD
request Source/destination of messages
shown to/from the left is
the MS MMI.
USSD the MSC.
request
wait
network
response
USSD USSD USSD release release error

response notify request

response notify request
idle USSD idle

response
wait MI
network wait user
response response
USSD release release error

response

response
wait
network idle
response
Figure 6.1: Mobile initiated USSD at MS
ETSI
Figure 6.2 (sheet 1 of 3)

INPUTS AND OUTPUTS
idle Source/destination of messages
shown to/from the left is the MS.
shown to/from the right is either
USSD the VLR or the application
request (as indicated).
no alphabet
supported
yes
HPLMN no
service
code
yes
USSD USSD
request request
(VLR) (appl)
MI MSC
wait VLR application
response processing
Figure 6.2 (sheet 1 of 3): Mobile initiated USSD at MSC
ETSI
MI
Figure 6.2 (sheet 2 of 3) wait VLR
response
USSD USSD
response request release release error
(VLR) (VLR) (VLR) (VLR)
USSD USSD release release error

response request (VLR)
USSD
notify
(VLR)
idle idle
USSD
notify
MI
wait user
response
(for VLR)

response (VLR)
USSD release error

response release
(VLR) (VLR)
(VLR)
MI MI
wait VLR idle wait VLR
response response
ETSI
MSC
Figure 6.2 (sheet 3 of 3) application
processing
USSD USSD
(application) (applIcation) (application) (application)

response request (application)
USSD
notify
(application)
idle idle
USSD
notify
MSC
wait user
response
(for application)

response (application)
USSD release error

response release
(application) (application)
(application)
MSC MSC
application idle application
processing processing
ETSI
Process USSD_AI1 390_63(1)
Figure 6.3 idle

INPUTS AND OUTPUTS
For consistency with other SDL
diagrams, all messages are
USSD shown to/from the right, for
request either the VLR or the
(application) application (as indicated).
USSD request from application

USSD is used when an application
request receives a request from a MS and
(VLR) passes on the request (changed or
unchanged) or generates a new
request.
AI
wait VLR
response
USSD USSD USSD

response request notify release release error
(VLR) (VLR) (VLR) (application) (VLR) (VLR)
USSD USSD USSD

(application) (application) (application) (VLR) (application) (application)
idle idle
AI
wait application
response
(for VLR)
USSD
response release release error
(application) (application) (VLR) (application)

response (VLR) (application) (VLR)
(VLR)
AI AI
wait VLR idle wait VLR
response response
Figure 6.3: Application initiated USSD at MSC
ETSI
Figure 6.4 (sheet 1 of 3)

INPUTS AND OUTPUTS
idle Source/destination of messages
shown to/from the left is the MSC.
shown to/from the right is either
USSD the HLR or the application
request (as indicated).
no alphabet
supported
yes
HPLMN no
service
code
yes
USSD USSD
request request
(HLR) (application)
MI VLR
wait HLR application
response processing
Figure 6.4 (sheet 1 of 3): Mobile initiated USSD at VLR
ETSI
MI
Figure 6.4 (sheet 2 of 3) wait HLR
response
USSD USSD
(HLR) (HLR) (HLR) (HLR)

response request (HLR)
USSD
notify
(HLR)
idle idle
USSD
notify
MI
wait user
response
(for HLR)

response (HLR)
USSD release error

response release
(HLR) (HLR)
(HLR)
MI MI
wait HLR idle wait HLR
response response
ETSI
VLR
Figure 6.4 (sheet 3 of 3) application
processing
USSD USSD
(application) (application) (application) (application)

response request (application)
USSD
notify
(application)
idle idle
USSD
notify
VLR
wait user
response
(for application)

response (application)
USSD release error

response release
(application) (application)
(application)
VLR VLR
aplication idle application
ETSI
Process USSD_AI2 390_65(1)
Figure 6.5 idle

INPUTS AND OUTPUTS
For consistency with other SDL
diagrams, all messages are
USSD shown to/from the right, for
request either the HLR or the
(application) application (as indicated).
USSD request from application

USSD is used when an application
request receives a request from a MS and
(HLR) passes on the request (changed or
unchanged) or generates a new
request.
AI
wait HLR
response
USSD USSD USSD

(HLR) (HLR) (HLR) (application) (HLR) (HLR)
USSD USSD USSD

(application) (application) (application) (HLR) (application) (application)
idle idle
AI
wait application
response
(for HLR)
USSD
response release release error
(application) (application) (HLR) (application)

response (HLR) (application) (HLR)
(HLR)
AI AI
wait HLR idle wait HLR
response response
Figure 6.5: Application initiated USSD at VLR
ETSI

INPUTS AND OUTPUTS
Figure 6.6 idle Source/destination of messages
shown to/from the left is the VLR.
shown to/from the right is the
USSD application.
request
no alphabet
supported
yes
error USSD
request
HLR
idle application
processing

response request notify

response request notify
HLR
idle wait user idle
response

response

response
HLR HLR
application idle application
Figure 6.6: Mobile initiated USSD at HLR
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
|Request handled by MSC | | | | |
| | | | | | | |
| +------------>| | | | | |
| | |OR1:N| | | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|Request handled by VLR | | | | |
| | | | | | | |
| +------------>|OR1:Y| | | | |
| | | +------------>| | | |
| | | | |OR2:N| | |
| | | |USSD response| | | |
| |USSD response| |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|Request handled by HLR | | | | |
| | | | | | | |
| +------------>|OR1:Y| | | | |
| | | +------------>|OR2:Y| | |
| | | | | +------------>| |
| | | | | | | |
| | | | | |USSD response| |
| | | |USSD response| |<------------| |
| |USSD response| |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
NOTE: OR1: HPLMN service code Y: Yes

OR2: HPLMN service code and user not in HPLMN N: No
Note that the application at the MSC/VLR may pass the request on to another network entity. This is not
shown here.
Figure 6.7: Information flow for mobile initiated USSD Request (No further information requested)
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | +------------>| |
| | | | | | | |
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | +------------>| |
| | | | | | | |
: : : : : : : :
: : : : : : : :
: : : : : : : :
| | | |USSD request | |<------------| |
| |USSD request | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | +------------>| |
| | | | | | | |
| | | |USSD response| |<------------| |
| |USSD response| |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
NOTE: Note that this call flow only shows one example to illustrate the possible scenarios. See the SDL diagrams
for a complete description.
Figure 6.8: Information flow for mobile initiated USSD Request Handled by HLR, further information
requested
ETSI
MS MSC VLR HLR

+-----+ +-----+ +-----+ +-----+
| | | | | | | |
|Error detected at MSC | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | | | | | |
| | Error | | | | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|Error detected at VLR | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | | | |
| | | | Error | | | |
| | Error | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|Error detected at HLR | | | | |
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | +------------>| |
| | | | | | | |
| | | | | | Error | |
| | | | Error | |<------------| |
| | Error | |<------------| | | |
| |<------------| | | | | |
| | | | | | | |
| | | | | | | |
|MS clears transaction before response received | |
| | | | | | | |
| +------------>| | | | | |
| | | +------------>| | | |
| | | | | +------------>| |
| | Release | | | | | |
| +------------>| | | | | |
| | | | Release | | | |
| | | +------------>| | | |
| | | | | | Release | |
| | | | | +------------>| |
| | | | | | | |
NOTE: This call flow only shows a limited number of examples to illustrate the possible scenarios. See the SDL
diagrams for a complete description.
Figure 6.9: Information flow for mobile initiated failed USSD Request
6.3 Information stored in the HLR

The HLR shall not store any information specific to the use of USSD, although information may be stored for services
6.4 Information stored in the VLR

The VLR shall not store any information specific to the use of USSD, although information may be stored for services
ETSI
6.5 Handover
Handover will have no impact on the operation of this service.
6.6 Cross-phase compatibility

If, when a Phase 2 MS sends a mobile initiated USSD request, any network entity is of Phase 1, the request will be
rejected. If it is possible to encode the content of the USSD request using the Phase 1 protocol, the MS shall repeat the
request, using the Phase 1 protocol.
A Mobile initiated USSD request from a Phase 1 MS uses the Phase 1 protocol. On receipt of such a request, the
application shall also use the Phase 1 protocol when sending the response.
A Phase 2 network shall not send network initiated requests or notifications during a mobile initiated USSD request if
the MS or any network entity involved in the operation is of Phase 1.
ETSI
Annex A (informative):
Change Request History
Status
of
Technical Specification GSM 03.90
Date Version Remarks
No Phase 1 version
October 1993 version 4.0.0 TS approved by SMG#08
January 1994 version 4.0.1 TS frozen for Phase 2 by SMG#09
TS changed to draft prETS 300 549
October 1994 version 4.0.2 TS changed to final draft prETS 300 549
January 1995 version 4.0.3 TS changed to ETS 300 549 First edition
July 1995 version 4.1.0 CR 03.90-A002 (category 2) approved by SMG#15
August 1996 version 4.1.1 TS changed to ETS 300 549 Second edition
December 1996 version 5.0.0 ETS changed to GTS for release '96
SMG#27 version 6.0.0 Release 1997 version
SMG#29 version 7.0.0 Release 1998 version
Text and flows: WinWord6
Stylesheet: etsiw_70.dot
ETSI
History
Document history
V7.0.0 August 1999 Publication
ISBN 2-7437-3330-6
Dépôt légal : Août 1999
ETSI

Etsi TS 100 549

Caricato da

Informazioni sul documento

Descrizione originale:

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Etsi TS 100 549

Caricato da

Copyright:

Formati disponibili

ETSI TS 100 549 V7.0.

Digital cellular telecommunications system (Phase 2+);

GLOBAL SYSTEM FOR

No part may be reproduced except as authorized by written permission.

© European Telecommunications Standards Institute 1999.

Annex A (informative): Change Request History ............................................................................... 32

Intellectual Property Rights

7 indicates Release 1998 of GSM Phase 2+

Figure 1.1: Handling of USSD

- Network initiated USSD (clause 1);

- Mobile initiated USSD (clause 2).

• For a specific reference, subsequent revisions do not apply.

• For a non-specific reference, the latest version applies.

4 Cross phase compatibility

5 Network initiated unstructured supplementary service

5.1 Handling of network initiated USSD

5.2 Functions and information flows

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 Information flow for successful single USSD request;

Figure 5.5 Information flow for successful single USSD notification;

Figure 5.6 Information flow for successful multiple USSD requests;

Figure 5.7 Information flow for failed USSD request.

5.2.1 Invoking unstructured SS operation from the HLR

5.2.2 Invoking unstructured SS operation from the VLR

5.2.3 Invoking unstructured SS operation from the MSC

5.2.4 Forwarding USSD operations

5.2.5 Handling of unstructured SS operation at the MS

Process USSD_NI1 390_51(1)

RELEASE USSD USSD RELEASE

error USSD release release

error USSD release release

USSD USSD release release

USSD USSD release release

Figure 5.1: Network initiated USSD invoked at HLR, VLR or MSC

Process USSD_NI2 390_52(1)

Figure 5.2 idle

VLR MSC HLR

RELEASE USSD USSD RELEASE

idle forwarding idle

error USSD release release

error USSD release release

USSD USSD release release

USSD USSD release release

Figure 5.2: Network initiated USSD forwarding at VLR or MSC

Process USSD_NI3 390_53(1)

idle Figure 5.3

error USSD USSD error

USSD release release

USSD release release

USSD USSD release release

Figure 5.3: Network initiated USSD at MS

MS MSC VLR HLR

Figure 5.4: Information flow for USSD request (Single Operation)

MS MSC VLR HLR

Figure 5.5: Information flow for USSD notification (Single Operation)

MS MSC VLR HLR

MS MSC VLR HLR

Figure 5.7: Information flow for failed USSD request

5.3 Information stored in the HLR

5.4 Information stored in the VLR