Information

Services

PLMN-Wide Short Codes for Subscriber

related routing of Service Numbers
A50016-D1110-C419-2-7629
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their
own purposes could violate the rights of their owners.

Copyright (C) Siemens AG 1998-2004.

Issued by Information and Communication Mobile

Hofmannstraße 51
D-81359 München

Technical modifications possible.

Technical specifications and features are binding only insofar as
they are specifically and expressly agreed upon in a written contract.

2 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

Reason for Update

Summary:
Formal corrections

Issue History
Issue Date of issue Reason for Update

1 11/2002 New software version

2 05/2004 Formal corrections

A50016-D1110-C419-2-7629 3
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

4 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

This document consists of a total of 16 pages. All pages are issue 2.

Contents
1 Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2 Mode of Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

3 Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

4 Call Charge Registration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

5 Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.1 Administration Functions at the MSC/VLR . . . . . . . . . . . . . . . . . . . . . . . . . 13
5.2 Administration Functions at the HLR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

6 Compatibility with other Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

A50016-D1110-C419-2-7629 5
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

6 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

1 Definition
Within a Public Land Mobile Network (PLMN), service providers can offer specific ser-
vices to mobile subscribers. These services are located in service centers that are dis-
tributed throughout the whole PLMN area. This also means that a specific service can
be supported in different service centers.
If the mobile subscriber has subscription to such a service, it is possible that only one
service center can handle the service requests of a specific mobile subscriber. The mail-
box, for instance, is such a service. Mailboxes are then distributed throughout the whole
PLMN area, but the mailbox of one specific subscriber has a fixed location in one spe-
cific service center.
The mobile subscriber dials a universal service number or a PLMN-wide short code to
access the service (e.g. to retrieve messages from his mailbox, directory assistance).
The network then guarantees that the mobile subscriber will always be connected to his
service center, irrespectively of the location at which he dialed the service number or
short code. This feature is called ”subscriber related routing”.
Service access via a PLMN-wide short code can also be realized by means of subscrib-
er dependent digit processing and feature control (SDDPFC) application. Such applica-
tion is more flexible, especially if the short code should be used in a larger context than
just for routing of service numbers.

A50016-D1110-C419-2-7629 7
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

2 Mode of Operation
A brief description of the procedure is given in Fig. 2.1:
1. The mobile subscriber dials the service number or a short code to access a specific
service. This number/code is sent to the servicing mobile-services switching cen-
ter/visitor location register (MSC/VLR).
2. If the subscriber dialed a short code, the MSC/VLR itself has to determine the ser-
vice number. Using the service number, the MSC/VLR interrogates the home loca-
tion register/authentication center (HLR/AC) of the calling mobile subscriber to
obtain information for routing towards the service center.
3. In the subscriber database the HLR/AC searches for the subscriber service address,
which can be either a fixed or subscriber dependent address, or it can be a service
center address. In the first two cases (fixed or subscriber dependent), the HLR/AC
returns the available information to the MSC/VLR.
4. If the subscriber service address is a service center address, the HLR/AC requests
routing information from this service center. The latter provides this information
which is sent to the MSC/VLR via the HLR/AC.
5. Finally, the routing information enables the MSC/VLR to connect the mobile sub-
scriber to his service center.

(2)
MSC/VLR interrogation HLR/AC
(1)
(3)
(5)
service number

n
atio
or short code

rm
info
t
ues

ting
req

rou
Access
(4)

(4)

Network

Service
Center
A-subscriber

Fig. 2.1 The principle of subscriber related routing

Because of the feature “subscriber related routing”, a mobile subscriber will always be
connected to his service center when he dials the service number or a PLMN-wide short
code.

Service number
The service number consists of the following parts (Fig. 2.2):
• the country code (CC) defining the country;
• the network destination code (NDC) defining the operator;
• the service indicator (SI) defining the service requested by the subscriber:
– X is a digit between 0 and 9 or between A and F (to be set via MPRDDAT);
– Y is a digit between 0 and 9 (to be set via SUBRSERV)
• the mobile subscriber number (SN) of the calling subscriber’s (basic) MSISDN.

8 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

CC NDC SI SN

X Y

Fig. 2.2 Service number structure

Service provider name table

If the subscriber uses a PLMN-wide short code, the servicing MSC/VLR first has to de-
termine the SI by means of the service provider name table (SPINAT). The SPINAT has
200 entries of which 100 entries are used for subscriber related routing. The other en-
tries are used for cell oriented routing.
Each entry of the SPINAT contains the following elements (Fig. 2.3):
– a service provider name which is a symbolic name identifying the service provider
– the service provider name type specifying whether it is used for subscriber related
routing or cell oriented routing
– the service indicator (only in the case of subscriber related routing)
– the call type (only in the case of cell oriented routing) to differentiate ordinary calls
from emergency calls

Entry n
Service provider name

Service provider type

(=subscriber related routing)

Service indicator

Entry n+1
Service provider name

Service provider name type

(=cell oriented routing)

Call type

Fig. 2.3 Structure of the SPINAT

The relationship between a short code and the corresponding service provider name
and SI is installed via code points. However, this is a matter of code point administration.
When the servicing MSC/VLR has the complete service number, which it has either re-
ceived from the mobile subscriber or determined via short code analysis, the MSC/VLR
interrogates the HLR to obtain the subscriber service address. The latter is useful rout-
ing information enabling the MSC/VLR to connect the mobile subscriber to his service
center.

A50016-D1110-C419-2-7629 9
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

HLR service table

In order to determine the subscriber service address, the HLR accesses the HLR ser-
vice table using the SI and the MSISDN. Each entry in this table contains the following
parameters (Fig. 2.4):
– the service name which is a symbolic name to identify the service
– the service indicator
– the subscriber service address itself
– the subscriber service address type specifying the format/type of the subscriber ser-
vice number
– a provision counter to count the number of subscribers using this particular service

HLR Service Table

Entry n
Service name

Service indicator

Subscriber service address

Subscriber service ad-

dress type

Provision counter

Fig. 2.4 Structure of the HLR service table

The provision counter protects from cancellation of a service used by at least one mobile
subscriber. Only if the associated counter’s value is 0 is the PLMN operator able to de-
lete the service via MML commands.

Subscriber service address

As the network supports three types of subscriber service addresses, the subscriber
service address type parameter is defined. The subscriber service address can be:
– fixed, i.e. it is a fixed number
– subscriber dependent, i.e. it is composed of parts of the MSISDN, or
– a service center address.
For one specific mobile subscriber, only one subscriber service address can be installed
per service subscribed to. Tab. 2.1 shows how the subscriber service address is stored
in the HLR service table for each type (F1 to F16 are decimal digits).

Subscriber service address Subscriber service address type

<F1 . . . F16> Fixed

<CC><NDC><F1 F2 F3> Subscriber dependent
<F1 . . . F16> Service center address

Tab. 2.1 The subscriber service address types

10 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

• Fixed
If the subscriber service address is a fixed (ISDN) number (according to numbering
plan E.164), the HLR returns it to the MSC/VLR as routing information.
• Subscriber dependent
The HLR does the same for the second type, i.e. when the address is subscriber de-
pendent. But, in this case, the HLR first has to construct the complete subscriber
service address by taking that part out of the HLR service table and adding the sub-
scriber number (i.e. (basic) MSISDN without CC and NDC) received from the
MSC/VLR.
• Service center address
However, if the subscriber service address is a service center address, it cannot be
used as routing information. In this case, the HLR requests a ”mobile subscriber
roaming number” from the service center. Therefore, the HLR uses the service cen-
ter address as a global title (i.e. address information) for the signaling connection
control part (SCCP) routing to the service center.
Afterwards, the HLR forwards the roaming number received from the service center to
the MSC/VLR. The latter uses the roaming number as routing information to connect the
calling subscriber to his service center.

Authorization
The HLR checks the subscriber’s subscription to the service, but neither the MSC/VLR
nor the HLR can verify whether the calling subscriber is authorized to use a specific ser-
vice number.
This means that any mobile subscriber can dial a service number containing an SI and
an MSISDN of another subscriber. If the other subscriber has subscription to the service
indicated by the SI (checked in the HLR), the calling subscriber is connected to the other
subscriber’s service center. This must be possible, for instance, to leave a message in
another mobile subscriber’s mailbox.
However, access to certain services or actions (e.g. to retrieve messages) should be
regulated. Therefore, it is up to the service center to perform authorization checks, e.g.
by means of a password, to prevent unauthorized subscribers from accessing a certain
service or to perform a certain action.

Subaddressing of the short code

Since the MSC/VLR knows the number of short code digits (code point administration),
the subscriber may append further digits to the short code. These further digits are treat-
ed as a subaddress. This subaddress can be used for controlling and triggering other
functions within the service center.
The complete dialed number, short code followed by subaddress, is sent to the
MSC/VLR where it is split.
The short code is treated as described, i.e. the MSC/VLR derives the service number,
which is used to interrogate the HLR. The additionally dialed digits are stored in the
MSC/VLR until the latter has received the result of the interrogation procedure. The su-
baddress is not checked. Then, the subaddress is also sent to the service center within
the initial address message.

A50016-D1110-C419-2-7629 11
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

Call forwarding registration with a service number or a short code

If a mobile subscriber has a subscription to the supplementary service call forwarding,
the subscriber is able to enter a forwarded-to number by means of subscriber controlled
input procedures.
It is possible for a subscriber to enter his service number as the forwarded-to number.
Then, a call to the subscriber is diverted to the subscriber’s service center (e.g. his mail-
box) when a certain condition is met (e.g. on no reply). Also for unconditional call for-
warding can the service number be entered as the forwarded-to number.
The MSC also allows a subscriber to enter a short code as the forwarded-to number,
provided that the short code is entered in the national format (i.e. without prefix), be-
cause only then is the HLR able to recognize the number as a short code. For this pur-
pose, the translation table is created in the HLR database. This table is administrable by
means of MML commands and stores a number of short codes with their corresponding
service indicators.
During the registration procedure, the short code is sent to the HLR. If the HLR receives
such a forwarded-to number, it looks for the corresponding service indicator in the trans-
lation table. This way, the HLR completes the service number, checks whether the sub-
scriber has subscription to the service and stores the service number in the international
format in the subscriber database. If the HLR cannot find the short code in the translation
table, the HLR will handle the short code as any other forwarded-to number. However,
during the invocation of call forwarding, the call will be rejected, because the forwarded-
to number is wrong.

3 Implementation
The feature ”subscriber related routing” is implemented as software functions in the
line/trunk group (LTG) of the MSC/VLR, and the coordination processor (CP) of the
MSC/VLR and the HLR.
The call processing functions in the MSC/VLR and the HLR carry out all the necessary
procedures for subscriber related routing.

4 Call Charge Registration

For each (speech) call originated from or terminated on a certain mobile station, the ser-
vicing MSC/VLR generates a charging record.
In the case of subscriber related routing, the MSC/VLR can generate an administrable
interrogation record because routing information is requested from the HLR, and gener-
ates at least one mobile originated call (MOC) record for the connection to the service
center. The charging records are used for post-processing purposes.

12 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

5 Administration
The administration of the core network nodes is performed either on the remote switch
commander (SC) with integrated or connected client terminals (CTs) or on the local craft
terminal (LCT). The switch commander supports Q3, MML and SNMP and offers a
graphical user interface and also allows a comfortable way of entering tasks and com-
mands.
An overview of the tasks being relevant in the context of this document is given below.
Detailed operation instructions can be found in the operation manuals (OMN) and in the
task manual (TML).
The administration of the feature at the MSC/VLR and the HLR contains the following
topics:
– administration of the services, i.e. defining services and managing the HLR service
table and the SPINAT
– subscriber administration at the HLR, i.e. to provide or to withdraw the subscription
to certain services
– code point administration at the MSC/VLR allowing the mobile subscriber to use
PLMN-wide short codes

5.1 Administration Functions at the MSC/VLR

Administration of service provider names
In the MSC/VLR, the PLMN operator can maintain service provider names and their cor-
responding service indicators for subscriber related routing. This information is stored in
the service provider name table which can be administrated by the operator via the fol-
lowing commands:
– CR PROVNAM, DISP PROVNAM, CAN PROVNAM (create, display, cancel provider
name)

Administration of code points

Code points are references for the digit translator enabling the latter to trigger an appro-
priate procedure or to select an appropriate destination depending on the dialed digits
and on the origin of the call.
The link between a PLMN-wide short code and a service provider name is managed with
code point administration especially for subscriber related routing. If the digit translator
detects a short code, the procedure triggered by the translator is to consult the service
provider name table in order to find the corresponding service indicator. And the asso-
ciated code point defines the destination number corresponding with the appropriate
service indicator. The operator can administrate this link with the following commands:
– CR CPT, DISP CPT, MOD CPT, SPLIT CPT, MERGE CPT, CAN CPT (create, dis-
play, modify, split, merge, cancel code point)

A50016-D1110-C419-2-7629 13
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

5.2 Administration Functions at the HLR

Administration of the service/translation table in HLR
With respect to service numbers, the mobile project dependent data must define a hexa-
decimal value for the service indicator (X digit only); the latter has to be used by all sub-
scribers. The PLMN operator can check this value using the command:
– DISP MPRDDAT (display mobile project description data)
The administration of subscriber related service data also includes data from both the
service table and the translation table in the HLR:
– The service table contains the service addresses with their corresponding service
indicators and service address types. The combination of one service indicator (Y
digit only) with a subscriber service address is indicated by a proper symbolic name.
– The administration of the translation table allows the operator to define a short code
for the appropriate service indicator (the same Y digit). This table enables the trans-
lation of a short code entered into the service number as the forwarded-to number.
The latter is then stored as the current forwarded-to number.
These tables are administered with the following commands:
– CR SUBRSERV, DISP SUBRSERV, MOD SUBRSERV, CAN SUBRSERV (create,
display, modify, cancel subscriber related service data)

Subscriber administration
Subscriber administration enables the PLMN operator to manage (providing and with-
drawing) the subscriber’s subscription to the operator service ”subscriber related rout-
ing”. The operator then assigns or deletes the proper symbolic name to the subscriber’s
identification number by means of the following commands:
– ENTR OPRSERV, CAN OPRSERV (enter, cancel operator service data)
The operator can display the assignment using the command:
– DISP MSUB (display mobile subscriber)

14 A50016-D1110-C419-2-7629
Information PLMN-Wide Short Codes for Subscriber related
Services routing of Service Numbers

6 Compatibility with other Features

Roaming
The PLMN operator allows mobile subscribers to use PLMN-wide short codes instead
of full service numbers for subscriber related routing. However, the use of short codes
is restricted according to the following roaming conditions:
– The subscriber is allowed to use short codes for subscriber related routing only
when he is roaming in his home PLMN. If not, the servicing MSC/VLR (of the foreign
PLMN) rejects the call setup.
– If a PLMN supports the short code facility, it is offered only to subscribers who are
registered in an HLR of this PLMN.
To verify that these conditions are met, the MSC/VLR takes the following action: the
MSC/VLR takes the international mobile subscriber identity (IMSI) of the calling party
and filters out the mobile country code (MCC) and the mobile network code (MNC).
Then, the MSC/VLR compares the MCC and the MNC from the IMSI with the MCC and
the MNC stored in the office database of the MSC/VLR. If both codes are the same, the
mobile subscriber is roaming in his home PLMN and the call setup proceeds.

Subscriber dependent digit processing and feature control

In countries where short codes are the same as the initial digits of ISDN numbers, they
can still be used if subscriber dependent digit processing and feature control (SDDPFC)
is implemented. The latter makes it possible to set limits to the number of digits to be
evaluated. This way a short code can be distinguished from an overlapping ISDN num-
ber.
The service indicator mentioned in this feature may also be used in SDDPFC applica-
tions where routing is related to the subscriber’s grouping index. It is possible for a ser-
vice indicator to be used to mark the group. In such a case the indicator must be
assigned to one item only.

A50016-D1110-C419-2-7629 15
PLMN-Wide Short Codes for Subscriber related Information
routing of Service Numbers Services

16 A50016-D1110-C419-2-7629