OPEN INFORMATION

E DESCRIPTION 1 (22)
Uppgjord — Prepared Datum — Date Rev Dokumentnr — Document no
SG/ERA/FZ/BIFE Stefan Nilevi 2001-09-21 F 63/190 46-FAD 104 08 Uen
Godkänd — Approved Kontr — Checked Tillhör/referens — File/reference
ERA/FZ/BIFEC (Andreas Fredlund)

Unstructured Supplementary Services

Abstract

The purpose of this document is to describe the function "Unstructured Supplementary

Services Data", USSD from a Data Transcript point of view. USSD was introduced in GSM
900/1800 SS R6.0. This document describes USSD in general. Some services today using
USSD are “account codes in MSC/VLR and HLR” and "tariff area indication". The latter is
described in document: 69/190 46-FAD 104 08.

Contents Page

1 Revision Information 2

2 Description 2
2.1 Abbreviations 2
2.2 Concerned Nodes 3
2.3 General 3
2.4 Prerequisites on the Network 4
2.5 Technical Solution 4
2.6 Traffic Cases 11

3 Data Transcript Impacts 14

3.1 General 14
3.2 AXE Parameters 14
3.3 Subfile 10000 - APT Size Alterations 15
3.4 Subfile 13000 - Exchange Properties 17
3.5 Subfile 15900 - General Purpose Digit Analysis 18
3.6 Subfile 75400 - Node Address, Roaming Area Characteristics 19
3.7 Subfile 79000 - Initiation of USSD Text Strings 19
3.8 Subfile 81000 - Area Specific Feature Data / HLR Number Series
Analysis 19

4 Miscellaneous Information 20
4.1 Class 20
4.2 Printout Descriptions 20

SEIF v2.3,
 OPEN INFORMATION
E DESCRIPTION 2 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

1 Revision Information

Revision Impacts Prepared Date

A New document ERASNI 96-09-11
B Small updates not related to new ERASNI 97-05-26
or enhanced functionality.
PC1 Document updated to SS R7 with ERASNI 98-05-15
account code information
C Minor changes to document ERAPEOJ 98-09-21
structure
D Updated to SS R8.0. No changes. ERARDPN 00-02-24
E Some changes done to the ERASNI 00-07-07
alphabet used.
F Reviewed for CN 1.5, Minor ERATYDE 01-09-21
Changes

2 Description

2.1 Abbreviations

ACCT Account Codes

GSM Global System for Mobile communication

HEX HEXadecimal

HLR Home Location Register

HPLMN Home PLMN

ID IDentity

IE Information Element

IMSI International Mobile Subscriber Identity

MAP V1 MAP Version 1

MAP V2 MAP Version 2

MS Mobile Station

MSISDN Mobile Station ISDN number

NAI Nature of Address Indicator

NAPI Numbering Plan Indicator

 OPEN INFORMATION
E DESCRIPTION 3 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

NI Network Initiated

NOC Notification Case

Ph Phase

PLMN Public Land Mobile Network

SMS Short Message Services

SS Supplementary Service

TAI Tariff Area Indication

TT Toll Ticketing

USSD Unstructured Supplementary Services Data

VLR Visitor Location Register

2.2 Concerned Nodes

• MSC/VLR

• HLR

• EXTERNAL NODE

2.3 General

USSD enables a mobile subscriber to invoke and control supplementary

services which are:

• Not supported by the mobile users mobile equipment, i.e. the

required signalling isn’t implemented in the MS.

• Non GSM SS for which no functional signalling is defined.

Signalling for SS is normally done in a structured way, i.e. protocols provide

the necessary means (IE) in order to fulfil the functional requirements of the
SS. When for example a subscriber activates call forwarding, the signalling is
sent in a structured way, which the MS can recognise and respond to.

USSD is used when structured functional signalling isn’t available for a certain
SS. In this case the required signalling isn’t implemented in the MS, and a
proper IE isn’t sent. The protocol provides a container mechanism to transport
the USSD to a USSD application that is able to analyse and act upon the
requested service. Depending on the service invoked, the request is forwarded
to a USSD application located in the VLR, or to the HLR. In the latter case, the
invoked service is either sent to an external node or rejected by the HLR.

From the beginning only two features were using USSD. Today though, more
operator specific services has been developed. In some cases this is in
combination with SMS for further enhancement of the services provision. An
 OPEN INFORMATION
E DESCRIPTION 4 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

example of this is subscriber or system initiated cash balance notification

for prepaid via SMS.

By introducing USSD, the subscriber will benefit from services that are not
GSM specified. Also the mobile user can use these services independently of
mobile equipment. Both GSM Ph1 and Ph2 mobiles are supported. It has
to be said though, that in order to fully benefit from USSD, a Ph2 mobile
is needed.

2.4 Prerequisites on the Network

In order to fully benefit from USSD, MAP V3 signalling with Ericsson
proprietary extension is required (for account codes). TAI works with MAP V1
or later MAP versions (for MAP V1 only some TAI operations work).

2.5 Technical Solution

USSD may be initiated by the MS towards the network, or by the network
towards the MS. NI USSD is however only supported by the GSM Ph2
specifications, i.e. GSM Ph1 mobiles cant receive messages initiated by
the network.

This figure shows the data flow of USSD operations, independently of the
affected applications.

HLR EXT NODE

MSC/VLR

USSD APPL

USSD MAP
USSD
PLATFORM
PLATFORM
protocol
MAP
protocol
DTAP protocol CM LAYER

Figure 1 Data flow for USSD operations.

USSD Application
A USSD application performs a supplementary service operation.
USSD Platform
The USSD platform consists of the USSD service functions and the USSD
handler.
USSD Service Function
The USSD service functions perform services used by the USSD application.
 OPEN INFORMATION
E DESCRIPTION 5 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

USSD Handler in VLR

The USSD handler is the main component of the USSD platform. It analysis
the contents of the received USSD operation. Depending on the result, the
operation is:

• Forwarded to the HLR via the MAP interface

• Sent to a local application in VLR

• Sent to the CM layer, and from there to the MS

• Rejected

CM Layer
The CM layer in VLR controls the DTAP protocol which transports mobile and
NI operations between the VLR and MS.

USSD Handler in HLR

The USSD handler is the main component of the USSD platform. It analyses
the contents of the received USSD operation. Depending on the result, the
operation is:

• Forwarded to the external node, via TTEN

• Sent to the VLR

• Rejected

TTEN
Transparent Transfer to/from External Node. TTEN is a USSD application,
which allows the MS to operate services in other nodes than the ones
specified by GSM. The interconnection between PLMN and the external node,
for example a message centre, is performed in the HLR through TTEN.

2.5.1 USSD Block Structure in VLR

This figure shows the structure of the USSD blocks in the VLR.
 OPEN INFORMATION
E DESCRIPTION 6 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

1 MUDENY & MUATAI & MUAACCT

2 MUSTR MUSTRA

3 MUSSPAP MUSSH MUSSAN

MAP interface to HLR CM Layer

Figure 2 Block structure of USSD in VLR.

1. USSD application

2. USSD service functions

3. USSD handler

MUDENY
Mobile telephony USSD denial application. Standard USSD application
invoked in case a service or procedure code has to be denied. Service and
procedure codes are described later in this document.

MUATAI
Mobile telephony USSD application tariff area indication. This block is involved
when TAI is invoked.

MUAACCT
Mobile telephony USSD application account codes. This block handles the
processing of account information.

MUSTR
Mobile telephony USSD string. MUSTR is used to translate a received
notification case into a USSD text string, which will be sent to the MS.
Notification cases are described later in this document.

MUSTRA
Mobile telephony USSD string administration. MUSTRA syntax checks the
commands and parameters related to USSD.

MUSSPAP
Mobile telephony unstructured supplementary services procedure MAP
interface. MUSSPAP establishes and maintains the communication between
the VLR and HLR.
 OPEN INFORMATION
E DESCRIPTION 7 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

MUSSH
Mobile telephony USSD handler. MUSSH is the main block of the USSD
handler. It takes care of sending text strings to the CM layer block.

MUSSAN
Mobile telephony USSD analysis. MUSSAN identifies the USSD operation
invoked by the mobile subscriber. Based on the analysis result, the USSD
request is handled locally in the VLR, or forwarded to the HLR.

2.5.2 USSD Block Structure in HLR

This figure shows the main block structure of the USSD blocks in the HLR.

1 APP1 APP2 APPn

2
HSSUDAP HSUDAP2

HSSUDA

3 HUDEXAP HUEXAP2

HUDEXA
to ext.node to ext.node

Figure 3 Block structure of USSD in HLR.

1. Application blocks

2. USSD handler

3. TTEN

APP1....APPn
These blocks identify the different applications in the HLR using USSD.

HSSUDAP
Home supplementary service unstructured data MAP V1. HSSUDAP
establishes and maintains the communication between the VLR and the
USSD applications in HLR for MAP V1 mobile initiated USSD operations.
 OPEN INFORMATION
E DESCRIPTION 8 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

HSSUDA
Home supplementary service unstructured data. This is a command handling
block for administrations of text strings. Text strings are described in this
document.
HSUDAP2
Home supplementary service unstructured data MAP V2. HSUDAP2
establishes and maintains the communication between the VLR and the USSD
applications in HLR for MAP V2 mobile and network initiated USSD operations.
HUDEXAP
Home USSD external node application MAP V1. HUDEXAP establishes and
maintains the communication between the HLR and the external node for
MAP V1 operations.
HUDEXA
Home USSD external node application. Among other things, this block stores
the external node address.
HUEXAP2
Home USSD external node application MAP V2. HUEXAP2 establishes and
maintains the communication between the HLR and the external node for
MAP V2 operations.

2.5.3 USSD in Detail

As remarked earlier, USSD can be network or mobile initiated. A NI USSD
could be a TAI sent to the MS at call set up. A text string consisting of a
maximum of 80 or 172 (depending on the alphabet used) characters will then
appear on the MS display, informing the subscriber whether he for example is
in a cheap or expensive area. This is a NI USSD notification, and requires
MAP V2 signalling and a Ph2 mobile.

A NI USSD request could also be sent. The network then wants information
from the subscriber, for example a account code. After having received and
checked the code, another text string containing personal information could be
sent. This requires MAP V2 or MAP V3 and a Ph2 mobile.

A mobile initiated USSD request is invoked by the subscriber. Depending on

the code entered, different text strings can be sent to the MS. This operation
can be invoked from a Ph1 mobile to a system where MAP V1 signalling
is used.

The code entered by a subscriber at a mobile initiated USSD request is

defined as a service or procedure code.

A service code is intended to identify a call independent or a call related

USSD operation. A call independent operation is used when no call is
ongoing. The mobile user may want a TAI to be sent from the network.
Depending on the result (e.g. if he’s in a cheap or expensive area), he may or
may not initiate a call. A call related operation is done during the call. The
mobile user may want some information to be sent to his MS from the network.

A service code is built on the format dXc#, where

• d=1, 2, or 3 characters of the set *#. d is mandatory.

 OPEN INFORMATION
E DESCRIPTION 9 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

• X=2 or 3 decimal characters of the set 0-9. X is mandatory.

• c=* together with 1 to 10 characters of the set 0-9. c is optional.

Examples of service codes could be, *#41#, *#401# or *#41*8#. The service
codes associated with TAI are always preceded by *#.

A procedure code is intended to identify a call related operation. This code is

built on the format Y, where

• Y=1 or 2 decimal characters of the set 0-9.

Examples of procedure codes could be, 4 or 51. A procedure code shouldn’t

be used for a call independent operation since the MS may handle it as a
normal call set up. Both service and procedure codes can be used for call
related operations. It’s up to the operator to decide which codes to use.
2.5.3.1 USSD in Detail, VLR
The service or procedure codes entered by the mobile user at a mobile
initiated USSD request are analysed in the General purpose digit analysis in
the VLR. Five different trees, 6-9 and 22 are used.

• Tree 6, one digit procedure codes are analysed. For example

code 4.

• Tree 7, two digits procedure codes are analysed. For example

code 51.

• Tree 8, two digits service codes are analysed. For example

code 41.

• Tree 9, three digits service codes are analysed. For example

code 401.

• Tree 22, a 2-3 digit service code for “Account codes”.

The characters *# are removed in software, and not analysed in ANGSI.

The application identifier (APP) in the RES parameter in ANGSI states what to
do with the different codes. Four different possibilities exist.

• APP-0, transfer of the USSD operation towards the HLR.

• APP-1, denial application.

• APP-2, indication of tariff area (TAI) to the mobile subscriber.

• APP-3, handling of Account code information.

If the code entered by the subscriber is connected to APP-0, its forwarded to

the HLR. The HLR analyses it and forwards it to an external node, or sends
a rejection message back to the VLR. All service and procedure codes not
defined in the General purpose digit analysis have default APP-0, so theres no
real reason to connect them. No text string can be connected to APP-0.

If the code entered by the subscriber is connected to APP-1, a text string is

sent to the MS telling the subscriber that the requested service is unknown. By
connecting unused service and procedure to APP-1, unnecessary signalling
 OPEN INFORMATION
E DESCRIPTION 10 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

between VLR and HLR is prevented. There are however a lot of unused
codes, so this would be time consuming.

If the code entered by the subscriber is connected to APP-2, a text string is

sent to the MS telling the subscriber whether he’s in a cheap or an expensive
area. APP-2 is described in more detail in document: 69/190 46-FAD 104 08.

On the reference dump, text strings for application 1, 2 and 3 are already
defined. They can however be changed with the command MGUSC. In order
to print the text strings, command MGUSP is used. For application 2 and 3,
different notification cases (NOC) are defined. They are generated depending
on the service or procedure More information about NOCs can be found in
Application information for concerned block, MUATAI for Tarrif Area Indication
and block MUAACCT for Account Codes. For every NOC, two text strings are
defined, one for SMD and the other for IA5. SMD and IA5 are two different
alphabets used. SMD is generated for USSD operations initiated from Ph2 MS
when MAP V2 or MAP V3 is used, while IA5 is generated for Ph1 MS (MAP
V1 , MAP V2 or MAP V3).

When defining or changing a text string, the command MGUSC is used. If the
text string sent to the MS is to be shown only with upper case letters, this text
string is entered in the STRING parameter in MGUSC. If the text string sent to
the MS is to be shown with lower case letters, these letters have to be defined
in the STRING parameter with their HEX values preceded by an escape
code. Which escape code to use is defined with AXE paremeter USSESC
(% is default). An example of a text string where lower case letters are used
is, STRING=”C%68%65%61%70 %61%72%65%61. In this case, when the
string is printed with MGUSP, "Cheap area" will appear.

2.5.3.2 USSD in Detail, HLR

If the service or procedure code sent by the subscriber is forwarded to the
HLR, the General number series analysis is invoked. It’s an independent
analysis that can be called upon by different function blocks. Each function
has a specific USRF ID which acts as an input together with the number
to be analysed.

The General number series analysis consists of a pre analysis (HGPAI), and
a main analysis (HGNSI). Depending on USRF, NAPI and NAI in HGPAI,
branching is done to a certain origin in the main analysis where the NS is
analysed. The result is returned to the calling function block. At least two
different USRFs have to be defined with HGPAI.

Example 1 MML command definitions

HGPAI:USRF=USSDSC, NAPI=0, NAI=0, ONSA=6;

HGPAI:USRF=ENAP2SC, NAPI=0, NAI=0, ONSA=7;

The USSD service code (USSDSC) is forwarded to tree 6 in HGNSI for further
analysis. External node address profile 2 digits service code (ENAP2SC), is
forwarded to tree 7 in HGNSI for further analysis. NAPI and NAI are always
set to zero, which means "unspecified".

At least two different CHARs have to be defined with HGNSI.

 OPEN INFORMATION
E DESCRIPTION 11 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

Example 2 MML command definitions

HGNSI:ONSA=6, CHAR=USSDSC-1, NS=50;

HGNSI:ONSA=7, CHAR=ENAP2SC-4, NS=50 4670751;

In HLR, two different applications exist, namely "Default application" and

"Transparent transfer to external node" (APP-0 and 1). USSDSC-1 means that
the USSD service code 50 for example, is to be transferred to the external
node. ENAP2SC-4 states that NS 50 4670751, which is the service code plus
the MSISDN, is to be sent to external node address profile number 4 (used
as input to command HGXAI). The service and procedure codes not defined
in the analysis table are forwarded to the default application. A text string
predefined on the reference dump saying "UNKNOWN APPLICATION" is then
generated and sent to the MS. The text string can be changed with command
HGUSC, and printed with HGUSP.

Example 3 MML command definitions

HGXAI:ENAP=4, EADD=4-46707500000;

HGXAI specifies the external node address in international format for the
external node address profile 4 (input from HGNSI). The external node
address could then be defined in the SCCP analysis. Several different
external nodes can be defined if applicable. The service code 50 together with
the MSISDN number and the HLR address is sent to the external node for
analysis. If stated in HGXAI, the IMSI number is also sent. Depending on the
code sent, a text string is generated in the external node and sent to the MS.
As said earlier, no USSD services are available in the external node today.

2.5.4 Charging
For each local USSD application, application parameters decide whether
charging is to be performed or not. One TT record will be output for the entire
transaction. For all USSD operations, mobile and network initiated, charging
will be performed equally. The same charging principle will be used as already
exists for call independent SS procedures in block MSS. This way of charging
must, for USSD be copied to the traffic blocks MTA and MTB.

More charging information, can be obtained from the documents:

11746/FF-1/APT 210 15/6 and 1/1553-ANT 215 02/5.

2.6 Traffic Cases

2.6.1 General
With the following DT defined in the VLR and in the HLR, some traffic cases
for mobile initiated USSD requests are described. MAP V3 signalling is
used. Note that this isn’t a complete USSD DT. SAEs and some properties
are omitted. They are instead covered in section 3. NI USSD operations
arent described in this section, nor is TAI. They are instead described in the
document: 69/190 46-FAD 104 08.

Example 4 MML command definitions

ANGSI:DSO=6, S=6, RES=APP-1;

 OPEN INFORMATION
E DESCRIPTION 12 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

ANGSI:DSO=7, S=51, RES=APP-1;

ANGSI:DSO=7, S=60, RES=APP-1&AUG-1;
ANGSI:DSO=8, S=41, RES=APP-1&AUG-2;

MGUPI:APPL=1, NOC=0, ALPH=SMD;

MGUSC:STRING=R%65%71%75%65%73%74%65%64 S%65%72%76;
MGUSC:STRING=%69%63%65 U%6e%6b%6e%6f%77%6e;
MGUPE;
MGUAI;

MGUSC:APPL=1, NOC=0, ALPH=IA5,

STRING=REQUESTED SERVICE UNKNOWN;

HGEPC:PROP=USSDTEXTESCAPE-0;

HGNSI:ONSA=6, CHAR=USSDSC-1, NS=401;

HGNSI:ONSA=7, CHAR=ENAP3SC-4, NS=401 4670751;

HGPAI:ONSA=6, USRF=USSDSC, NAPI=0, NAI=0;

HGPAI:ONSA=7, USRF=ENAP3SC, NAPI=0, NAI=0;

HGXAI:ENAP=4, EADD=4-46707500000, IMSIND;

HGUPI:APPL=0, NOC=0, ALPH=SMD;

HGUSC:STRING=U%6e%6b%6e%6f%77%6e A%70%70;
HGUSC:STRING=%6c%69%63%61%74%69%6f%6e;
HGUPE;
HGUAI;

HGUSC:APPL=0,NOC=0,ALPH=IA5,
STRING=UNKNOWN APPLICATION;

2.6.2 Mobile Initiated USSD Requests

• During a call, a subscriber dials the combination *#41# followed
by the "send button". A check of AXE parameter USSDHA1 is
made, to see if Ph1 operations are to be analysed in VLR or
sent to the HLR. In these traffic cases they are to be analysed
in the VLR (USSDHA1-1). Different signals are generated in
the blocks concerned depending on if the mobile is a Ph1 or
a Ph2. The code is analysed in the General purpose digit
analysis. Since it’s a two digit service code, the analysis takes
place in tree 8. This service code is connected to the denial
application (APP-1) which means that it isn’t associated with a
service. By connecting unused codes to APP-1, unnecessary
signalling between VLR and HLR is prevented.

AUG-2 states that the code is to be analysed in ANGSI for

both HPLMN subscribers and for roamers. If the subscriber is
a roamer or not, is determined in the IMSI number analysis
(NATMS/OWNMS) during location updating. APP-1 is
connected to text strings already defined on the reference
dump. These text strings can however be changed as shown in
the DT above.

Depending on if the MS is a Ph1 or a Ph2 mobile, text strings

for different alphabets are generated. Alphabet SMD is always
 OPEN INFORMATION
E DESCRIPTION 13 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

used during Ph2 mobile operations, while alphabet IA5 is used

at Ph1 mobile operations. If *#41# is sent from a Ph2 mobile,
text string "Requested Service Unknown" will be sent to the
mobile. Note that this text string has to be defined with an
escape code since it contains lower case letters. If *#41# is
sent from a Ph1 mobile, text string "REQUESTED SERVICE
UNKNOWN" is sent. The same code could also be sent when
there’s no ongoing call. The scenario as described above
will then appear.

• If a subscriber during a call dials "51" followed by the "send

button", the two digit procedure code is analysed in tree 7 in the
General purpose digit analysis. The difference between this
traffic case and the previous is that roamers are sent to their
home HLR for further analysis. Procedure code 51 gets AUG-0
default, which means that this code is reserved for HPLMN use
only. If the HLR where the roamer is registered doesn’t support
USSD, then an error message is sent back to the VLR.

• If a roamer during a call dials "60" followed by the "send

button", the two digit procedure code is analysed in tree 7. If
the same code is sent from a HPLMN subscriber, it’s forwarded
to the HLR for further analysis (AUG-1).

• If a subscriber, either during a call or when there’s no ongoing

calls, dials *#401# followed by the "send button", then the three
digit service code is transferred to HLR (default APP-0). The
same thing would have occurred if the code in ANGSI was
connected to APP-0. In the HLR, a check is made to see if the
subscriber is barred from using SS. If this is not the case, the
service code is analysed in the number series analysis. The
characters *# are removed, and not analysed.

In HGPAI it’s determined whether the code is a USSD service

code (USSDSC). Also more in detail, its stated that the code
is associated with an external node address profile 3 digit
service code (ENAP3SC). NAPI and NAI are always set to 0
for service and procedure codes, which means unstructured.
The code 401 is now sent to the main Number series analysis.
In tree 6, digit "1" determines that the USSD service code
401 is to be sent to the external node (USSDSC-1). In tree
7, the value number for the ENAP (4) for the service code for
a specific number serie is determined. The number serie
consists of the service code plus an MSISDN. The ENAP value
number acts as an input to HGXAI. In HGXAI the external node
address is stated for a certain ENAP. The IMSI number for the
subscriber together with the service code and the HLR address
are sent to the external node. When the proper text string has
been generated in the external node, it’s forwarded to the MS
and shown on the display.

• If a subscriber during a call dials "70", the 2 digit procedure

code is forwarded to the HLR. In the Number series analysis
no data is defined for that procedure code, and the default
application (APP-0) is invoked. Depending on whether it is a
Ph1 or a Ph2 operation, a text string for alphabets IA5 or SMD
is generated in the HLR as for the denial application in the VLR.
 OPEN INFORMATION
E DESCRIPTION 14 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

Exchange property USSDTEXTESCAPE states what escape

code to use if needed. For alphabet IA5 (Ph1), text string
"UNKNOWN APPLICATION" is sent, while text string "Unknown
Application" is sent for a Ph2 operation (SMD).

3 Data Transcript Impacts

3.1 General

In order to enable USSD in the switch, new commands, SAEs and exchange
properties are introduced. In this document DT for the USSD based functions
“Account codes” and “TAI” are omitted. The latter function is covered in the
document: 69/190 46-FAD 104 08. A few things have to be said concerning
some commands.

When defining a text string for an application in VLR, the command MGUSC
on its own will sufficent as long as the text string contains less than 42
characters, space and escape codes included. If the text string to be defined
contains more than 41 characters, several MGUSC commands are needed.
Then a procedure starting with MGUPI and ended with MGUPE has to
be used. MGUAI is given in order to activate the text string when using
procedures. When MGUSC on its own is used, the text string is activated
automatically. The same rules as above apply for commands used when
defining strings in the HLR.

The Data Transcript commands are divided into different chapters depending
on where in the loading sequence they belong to.

All subfiles that are affected by the function USSD, excluding “TAI” and
“Account codes” are mentioned in this document.

3.2 AXE Parameters

Example 5 MML command definitions

!**********************!
!*** Definition of ***!
!*** AXE parameters ***!
!**********************!

DBTRI;
DBTSC:TAB=AXEPARS, SETNAME=GSMMSSC, NAME=USSDHA1, VALUE=0;
! 0-1 Handling of GSM Phase 1 USSD !
! requests. The parameter is optional. !
! 0 = GSM Phase 1 mobile originating !
! USSD requests will always be !
! forwarded to the HLR. !
! 1 = GSM Phase 1 mobile originating !
! USSD requests can be handled !
! locally by MSC/VLR. !
! Default value = 0 !
! The parameter is owned by the !
! block MUSSAN. !
 OPEN INFORMATION
E DESCRIPTION 15 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

DBTSC:TAB=AXEPARS, SETNAME=GSMMSSC, NAME=USSESC, VALUE=0;

! 0-4 Escape code used by USSD text !
! string commands. The parameter is optional. !
! 0 = Escape code = ’%’ . !
! 1 = Escape code = ’ ’. !
! 2 = Escape code = ’*’. !
! 3 = Escape code = ’:’. !
! 4 = Escape code = ’ ’. !
! Default value = 0 !
! The parameter is owned by block MUSTRA. !

DBTRE:COM;

3.3 Subfile 10000 - APT Size Alterations

Example 6 MML command definitions

!*** SIZE ALTERATIONS APT, VLR***!

SAAII:SAE=500, NI= 115, BLOCK=MCISS;

! MCISS handles call independent SS procedures between !

! the network and the mobile station. !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 113 W16 !
! Dimensioning: !
! An individual is seized for a mobile or network initiated !
! SS procedure. The individual remains connected until !
! the SS procedure is terminated. When the file is full, !
! any request for a call independent SS procedure will be !
! rejected. The file is supervised by the Software file !
! Congestion Supervision function. !

SAAII:SAE=500, NI= 21, BLOCK=MUSSPAP;

! MUSSPAP establishes and maintains the communication !

! between VLR and HLR for USSD MAP operations. !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 26 W16 !
! Dimensioning: !
! An individual is seized when a request is received from a !
! mobile to send a USSD operation in a new dialogue to !
! HLR. An individual is also seized when a network initiated!
! operation is received from HLR in a new dialogue. The !
! individual is released when the dialogue is ended. The !
! file is supervised by the Software file Congestion !
! Supervision function. !

SAAII:SAE=500, NI= 141, BLOCK=MUSSH;

! MUSSH handles the routing of USSD requests and !

! responses between CM layer blocks and USSD application !
! blocks. !
 OPEN INFORMATION
E DESCRIPTION 16 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

! Minimum step size: 1 !

! Maximum extension step: 500 !
! Record size: 21 W16 !
! Dimensioning: !
! An individual is seized when a mobile or network initiated!
! USSD operation is initiated. If the file is full, all new !
! USSD procedures will be fail. The file is supervised by !
! the Software file Congestion Supervision function. !

SAAII:SAE=708, NI= 68, BLOCK=MUSSH;

! MUSSH handles the routing of USSD requests and !

! responses between CM layer blocks and USSD application !
! blocks. SAE 708 is used for storage of dynamic buffer !
! references, which are used during the USSD procedure !
! Minimum step size: 1 !
! Maximum extension step: 400 !
! Record size: 1 W16 !
! Dimensioning: !
! An individual is seized when a USSD application requests !
! a dynamic buffer. This may occur several times during a !
! USSD procedure. The individual is released when !
! the dynamic buffer isnt used anymore during the USSD !
! procedure. The file is supervised by the !
! Software file Congestion Supervision function. !

SAAII:SAE=709, NI= 500, BLOCK=MUSTR;

! MUSTR is used to store the USSD text strings which are !
! defined for the USSD applications. !
! Minimum step size: 1 !
! Maximum extension step: 400 !
! Record size: 42 W16 !
! Dimensioning: !
! An individual is seized when a USSD text string with !
! max 64 octets is stored. One individual can store up to !
! 64 characters in the IA5 alphabet or up to 73 in alphabet !
! SMD. The file is supervised by the Software file !
! Congestion Supervision function. !

!*** SIZE ALTERATIONS APT, HLR***!

SAAII:SAE=500, NI= 16, BLOCK=HSSUDAP;

! HSSUDAP establishes and maintains the communication !

! between the VLR and the USSD applications in HLR for !
! MAP V1 mobile initiated USSD requests received from VLR !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 24 W16 !
! Dimensioning: !
! An individual is seized when a MS initiated USSD !
! operation is received from VLR, and is released when the !
! dialogue is ended. When the file becomes full, any request!
! received from VLR is denied. The file is supervised by the!
! Software file Congestion Supervision function. !

SAAII:SAE=500, NI= 190, BLOCK=HSUDAP2;

 OPEN INFORMATION
E DESCRIPTION 17 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

! HSUDAP2 establishes and maintains the communication !

! between the MS and the USSD applications in HLR for !
! MAP V2 mobile initiated USSD requests and for NI USSD !
! operations. !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 71 W16 !
! Dimensioning: !
! An individual is seized when a Ph2 MS initiated USSD !
! operation is received from VLR, and is released when the !
! dialogue is ended. Its also seized during NI USSD !
! operations. When the file becomes full, any USSD !
! MAP V2 operation is denied. The file is supervised by the !
! Software file Congestion Supervision function. !

SAAII:SAE=500, NI= 16, BLOCK=HUDEXAP;

! HUDEXAP establishes and maintains the communication !

! between the HLR and an external node for MAP V1 !
! mobile initiated USSD requests. !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 29 W16 !
! Dimensioning: !
! An individual is seized when a request is received from !
! from VLR through the USSD handler to send a USSD !
! operation to an external node. The individual is released !
! when a response received from the external node is sent !
! to the VLR. The file is supervised by the Software !
! file Congestion Supervision function. !

SAAII:SAE=500, NI= 190, BLOCK=HUEXAP2;

! HUEXAP2 establishes and maintains the communication !

! between the HLR and an external node for MAP V2 !
! mobile initiated USSD requests, and for NI USSD !
! operations. !
! Minimum step size: 1 !
! Maximum extension step: 500 !
! Record size: 47 W16 !
! Dimensioning: !
! An individual is seized when a Ph2 MS request is received !
! from VLR to send a USSD operation to an external node. !
! The individual is released when a response received from !
! the external node is sent to the VLR. Its also seized !
! during NI USSD operations. When the file is full, MAP V2 !
! operations towards HLR arent allowed. The file is !
! supervised by the Software file Congestion Supervision !
! function. !

3.4 Subfile 13000 - Exchange Properties

Example 7 MML command definitions

!*** EXCHANGE PROPERTIES, VLR ***!

 OPEN INFORMATION
E DESCRIPTION 18 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

MGEPC:PROP= SSEM2-0;

! 0-1 Supplementary service operations !

! in parallel to emergency call. The parameter !
! is optional. It specifies whether network !
! initiated supplementary service operations are !
! allowed in parallel to an emergency call. !
! 0 = Network initiated SS operations !
! are not allowed in parallel to an emergency call. !
! 1 = Network initiated SS operations !
! are allowed in parallel to an emergency call !
! Default value = 0 !
! The parameter is owned by the block MMM. !

MGEPC:PROP= SSLOC-0;

! 0-1 Allowance of network initiated !

! supplementary service operations outside !
! the local subscription area. The parameter !
! is mandatory with application dependent !
! values. The parameter is only valid for mobile !
! subscribers having a local subscription. It !
! specifies whether network initiated !
! supplementary service operations may be !
! forwarded to the MS in case the subscriber is !
! restricted due to local subscription. !
! 0 = Network initiated operations !
! are not allowed in case the MS is restricted !
! due to local subscription. !
! 1 = Network initiated operations are allowed !
! in case the MS is restricted due to local !
! subscription. The parameter is owned by the !
! block MZONE. !

!*** EXCHANGE PROPERTY, HLR ***!

HGEPC:PROP= USSDTEXTESCAPE-0;

! 0-4 Escape code used when entering a text !

! string by command. !
! 0 = Escape code ’%’ !
! 1 = Escape code ’#’ !
! 2 = Escape code ’*’ !
! 3 = Escape code ’:’ !
! 4 = Escape code ’!’ !
! Default value: 0 !
! Type: - Optional !
! Involved blocks: HSSUDA !

3.5 Subfile 15900 - General Purpose Digit Analysis

Example 8 MML command definitions

ANGSI:DSO=6, S=4, RES=APP-1;

ANGSI:DSO=7, S=51, RES=APP-1&AUG-0;
 OPEN INFORMATION
E DESCRIPTION 19 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

ANGSI:DSO=8, S=41, RES=APP-1&AUG-1;

ANGSI:DSO=9, S=401, RES=APP-1&AUG-2;

3.6 Subfile 75400 - Node Address, Roaming Area Characteristics

Example 9 MML command definitions

HGXAI:ENAP=4, EADD=4-46707500000;

3.7 Subfile 79000 - Initiation of USSD Text Strings

Example 10 MML command definitions

!*** USSD TEXT STRINGS, VLR ***!

MGUPI:APPL=1, NOC= , ALPH= ;

MGUSC:STRING= ;
MGUSC:STRING= ;
MGUPE;
MGUAI;

! Text strings are already defined on the !

! reference dump for APPL=1, 2 and 3, but can !
! be changed as stated above if the text string !
! contains more than 41 characters. If not, !
! MGUSC on its own will do. !

!*** USSD TEXT STRINGS, HLR ***!

HGUPI:APPL=0, NOC= , ALPH= ;

HGUSC:STRING= ;
HGUSC:STRING= ;
HGUPE;
HGUAI;

! Text strings are already defined on the !

! reference dump for APPL=0, but can be !
! changed as stated above if the text string !
! contains more than 41 characters. If not, !
! HGUSC on its own will do. !

3.8 Subfile 81000 - Area Specific Feature Data / HLR Number

Series Analysis

Example 11 MML command definitions

HGNSI:ONSA=6, CHAR=USSDSC-1, NS=401;

HGNSI:ONSA=7, CHAR=ENAP3SC-4, NS=401 4670751;

HGPAI:USRF=USSDSC, NAPI=0, NAI=0, ONSA=6;

HGPAI:USRF=ENAP3SC, NAPI=0, NAI=0, ONSA=7;
 OPEN INFORMATION
E DESCRIPTION 20 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

4 Miscellaneous Information

4.1 Class

Unstructured Supplementary Services Data is a standard optional function.

4.2 Printout Descriptions

Three new printouts are introduced for the following commands.

• MGUSP:APPL=ALL, NOC=ALL;

"MT USSD TEXT STRING DATA"

• HGUSP:APPL=ALL, NOC=ALL;

"HLR USSD TEXT STRING DATA"

• HGXAP:ENAP=ALL;

"HLR USSD EXTERNAL NODE ADDRESS PROFILE DATA"

 OPEN INFORMATION
E DESCRIPTION 21 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

References
11746/FF-1/APT 210 15/6 USSD traffic cases on access side
Uen A

11744/FF-1/APT 210 15/6 Indication of tariff area to mobile subscriber in MSC/VLR

Uen A

11749/FF-1/APT 210 15/6 USSD platform in MSC/VLR and HLR interface

Uen A

11638/FF-1/APT 210 15/6 Unstructured SS data operations in HLR

Uen A

11656/FF-1/APT 210 15/6 Unstructured SS data from HLR to an external node

Uen A

1/1553-ANT 215 02/5 Uen A User guide for charging, GSM

2/155 18-CNT 292 0061 Block MCISS

Uen PC3

2/155 18-CNT 292 0054 Block MUSSH

Uen A

2/155 18-CNT 292 0028 Block MUSTR

Uen A

2/155 18-CNT 238 0112 Block HSSUDAP

Uen B

2/155 18-CNT 238 0113 Block HSUDAP2

Uen B

2/155 18-CNT 238 0116 Block HUDEXAP

Uen B

2/155 18-CNT 238 0117 Block HUEXAP2

Uen B

2/155 18-1/APT 210 25 /2 Mobile telephony data. Changeable Exchange Adaptation

Uen PA5

2/155 18-ANT 238 01 Uen Home Location Register. Changeable Exchange Adaptation
PG8

2/155 18-CNT 292 0055 MUATAI

Uen B

2/155 18-CNT 292 0071 MUAACCT

Uen E

1/190 82-CNT 238 0095 HGNSI

Uen B1

4/190 82-CNT 238 0095 HGPAI

Uen B1
 OPEN INFORMATION
E DESCRIPTION 22 (22)
Datum — Date Rev Dokumentnr — Document no
2001-09-21 F 63/190 46-FAD 104 08 Uen

2/190 82-CNT 238 0114 HGUSC

Uen B

1/190 82-CNT 238 0118 HGXAI

Uen B

5/190 82-CNT 214 0010 ANGSI

Uen A

2/190 82-CNT 292 0029 MGUSC

Uen B