ETSI EN 301 710 V7.0.

2 (1999-12)
European Standard (Telecommunications series)

Digital cellular telecommunications system (Phase 2+);

User-to-User Signalling (UUS) Supplementary Service;
Stage 2
(GSM 03.87 version 7.0.2 Release 1998)

GLOBAL SYSTEM FOR

MOBILE COMMUNICATIONS
(GSM 03.87 version 7.0.2 Release 1998) 2 ETSI EN 301 710 V7.0.2 (1999-12)

Reference
DEN/SMG-030387Q7

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

Important notice

This ETSI deliverable may be made available in more than one electronic version or in print. In any case of existing or
perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).
In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network
drive within ETSI Secretariat.

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
(GSM 03.87 version 7.0.2 Release 1998) 3 ETSI EN 301 710 V7.0.2 (1999-12)

Contents
Intellectual Property Rights................................................................................................................................5
Foreword.............................................................................................................................................................5
1 Scope ........................................................................................................................................................6
2 References ................................................................................................................................................6
3 Definitions and abbreviations ..................................................................................................................6
3.1 Definitions ..........................................................................................................................................................6
3.2 Abbreviations .....................................................................................................................................................7
4 General .....................................................................................................................................................7
4.1 Activation of UUS components..........................................................................................................................7
4.1.1 Implicit request .............................................................................................................................................8
4.1.2 Explicit request .............................................................................................................................................8
4.1.3 UUS required option.....................................................................................................................................8
5 Handling of User-to-user signalling.........................................................................................................8
5.1 Timers.................................................................................................................................................................8
5.2 Information flows of UUS services ....................................................................................................................9
5.2.1 Service 1 (UUS1)..........................................................................................................................................9
5.2.1.1 Flow control ............................................................................................................................................9
5.2.1.2 Information flows ..................................................................................................................................10
5.2.1.2.1 Implicit activation............................................................................................................................10
5.2.1.2.2 Explicit activation .................................................................................................................................11
5.2.2 Service 2 (UUS2)........................................................................................................................................12
5.2.2.1 Flow control ..........................................................................................................................................12
5.2.2.2 Information flows ..................................................................................................................................12
5.2.3 Service 3 (UUS3)........................................................................................................................................14
5.2.3.1 Flow control ..........................................................................................................................................14
5.2.3.2 Information flows ..................................................................................................................................14
5.3 Messages and their contents .............................................................................................................................16
5.3.1 Information elements used in the messages ................................................................................................17
5.3.2 Messages between MS and MSC................................................................................................................17
5.3.3 Messages between MSC and VLR (B interface).........................................................................................18
5.3.4 Messages between MSC – MSC (E interface) ............................................................................................18
6 Interaction with other supplementary services.......................................................................................19
6.1 Call forwarding unconditional (CFU)...............................................................................................................19
6.2 Call forwarding on mobile subscriber busy (CFB) ...........................................................................................19
6.3 Call forwarding on no reply (CFNRy)..............................................................................................................19
6.4 Call forwarding on mobile subscriber not reachable (CFNRc).........................................................................19
6.5 Call waiting (CW) ............................................................................................................................................19
6.6 Call hold (HOLD) ............................................................................................................................................20
6.7 Completion of calls to busy subscribers (CCBS)..............................................................................................20
6.8 Explicit call transfer (ECT) ..............................................................................................................................20
6.9 Multi party service (MPTY) .............................................................................................................................20
6.10 Advice of charge (AoC) ...................................................................................................................................20
6.11 Barring of outgoing calls (BAOC) ...................................................................................................................20
6.12 Barring of outgoing international calls (BOIC) ................................................................................................20
6.13 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC) ......20
6.14 Barring of incoming calls (BAIC) ....................................................................................................................20
6.15 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam)................................20
6.16 Call deflection (CD) .........................................................................................................................................21
7 Interaction with other network features .................................................................................................21
7.1 Customised Applications for Mobile network Enhanced Logic (CAMEL)......................................................21
7.2 Support for Optimal Routeing(SOR)................................................................................................................21

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 4 ETSI EN 301 710 V7.0.2 (1999-12)

8 Interworking with other networks ..........................................................................................................21

8.1 Interworking with GSM PLMN/ISDN network supporting only a maximum User-user information
element length of 35 octets ...............................................................................................................................21
8.2 Interworking with non-ISDN network ..............................................................................................................21
9 Network entity functions........................................................................................................................22
9.1 Originating network processes..........................................................................................................................22
9.1.1 Procedures in MSC .....................................................................................................................................22
9.1.2 Procedures in VLR......................................................................................................................................26
9.2 Terminating network processes ........................................................................................................................27
9.2.1 Procedures in GMSC ..................................................................................................................................27
9.2.2 Procedures in MSC .....................................................................................................................................29
9.3 Procedures common in serving and remote networks.......................................................................................35
9.4 Processes used during Active Call....................................................................................................................45
9.4.1 Process and procedures in serving MSC.....................................................................................................45
9.4.2 Process and procedures in serving VLR .....................................................................................................50
9.4.3 Process and procedures in remote MSC .....................................................................................................52
10 Information stored in the HLR and in the VLR .....................................................................................57
10.1 Information stored in the HLR .........................................................................................................................57
10.2 Transfer of information from HLR to VLR ......................................................................................................57
10.3 Information stored in the VLR .........................................................................................................................57
11 State transition model.............................................................................................................................57
12 Handover ................................................................................................................................................57

Annex A (informative): Status of Technical Specification GSM 03.87 .............................................58

History ..............................................................................................................................................................59

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 5 ETSI EN 301 710 V7.0.2 (1999-12)

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 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 European Standard (Telecommunications series) has been produced by Technical Committee Special Mobile
Group (SMG).

The present document gives the stage 2 description of the User-to-User signalling supplementary services within the
digital cellular telecommunications system.

The contents of the present document are subject to continuing work within SMG and may change following formal
SMG approval. Should SMG modify the contents of the present document it will then be republished by ETSI with an
identifying change of release date and an increase in version number as follows:

Version 7.x.y

where:

7 GSM Phase 2+ Release 1998;

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.

National transposition dates

Date of adoption of this EN: 3 December 1999
Date of latest announcement of this EN (doa): 31 March 2000
Date of latest publication of new National Standard
or endorsement of this EN (dop/e): 30 September 2000
Date of withdrawal of any conflicting National Standard (dow): 30 September 2000

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 6 ETSI EN 301 710 V7.0.2 (1999-12)

1 Scope
The present document gives the stage 2 description of the User-to-User signalling supplementary services.

The User-to-user supplementary service is divided into 3 different services:

- Service 1 (UUS1);

- Service 2 (UUS2);

- Service 3 (UUS3).

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.87: "Digital cellular telecommunications system (Phase 2+); User-to-User Signalling
(UUS); Service Description, Stage 1".

[3] GSM 03.18: "Digital cellular telecommunications system (Phase 2+); Basic Call Handling –
Technical Realization".

[4] GSM 03.78: "Digital cellular telecommunications system (Phase 2+); Customised Applications for
Mobile network Enhanced Logic (CAMEL) – Stage 2".

[5] GSM 03.79: "Digital cellular telecommunications system (Phase 2+); Support for Optimal
Routeing (SOR) – Technical Realization".

3 Definitions and abbreviations

3.1 Definitions
For the purposes of the present document, the following terms and definitions apply.

Burst parameter: Parameter indicating the absolute maximum number of UUS 3 service related user information
messages that can be sent at intervals indicated by the value of timer T2-UUS3.

Remote network: The network of the remote subscriber.

Remote subscriber: For service 1 and 2 the remote subscriber is the called party of a call to which the served subscriber
activates the UUS supplementary service. For service 3 the remote subscriber can be either the called or the calling party
of an established call to whom the use of the UUS supplementary service is requested by the served subscriber.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 7 ETSI EN 301 710 V7.0.2 (1999-12)

Served subscriber: The subscriber who has a provision of the UUS supplementary service and who activates the UUS
supplementary service. For service 1 and 2 the served subscriber is always the calling subscriber, for service 3 either the
calling or the called subscriber can be the served subscriber.

Serving network: The network of the served subscriber.

User-to-User Information (UUI): The information transferred by using the UUS supplementary service.

UUS Service: The UUS services (Service 1, 2 and 3) are components of the UUS supplementary service. If the UUS
supplementary service is provided to a subscriber, he can handle the UUS services independently within a call.

3.2 Abbreviations
For the purposes of the present document, the following abbreviations apply:

ACM Address Complete Message

ANM ANswer Message
CON CONnect
CPG Call ProGress
IAM Initial Address Message
MS Mobile Station
REL RELease
SIFOC Send Info For Outgoing Call
SRI Send Routing Info
UUI User-to-User Information
UUS User-to-User Signalling
UUS1 User-to-User Signalling Service 1
UUS2 User-to-User Signalling Service 2
UUS3 User-to-User Signalling Service 3

Further GSM related abbreviations are listed in GSM 01.04.

4 General
The UUS supplementary service allows the transfer of UUI to a remote subscriber over the signalling channel in
association with a call to this subscriber. The UUS supplementary service is divided in Service 1, Service 2 and
Service 3.

The UUS Service 1 allows the transfer of UUI embedded within Call Control messages.

The UUS Service 2 allows the transfer of UUI with a specific User-to-user message after the served subscriber has
received an address complete indication and prior to the answer indication from the B-side.

The UUS Service 3 allows the transfer of UUI with a specific User-to-user message during an active call.

For the use of the UUS supplementary service in GSM PLMNs the support of UUS capabilities within the
inter-exchange signalling system (e.g. ISUP) is necessary. However this is out of scope of this specification.

4.1 Activation of UUS components

If any of the UUS Services 1, 2 or 3 shall be used within a call, the UUS capabilities have to be activated by the served
subscriber either when initiating this outgoing call (Service 1, 2 and 3) or during an established call (Service 3).

The UUS capabilities for a call can be requested by means of an implicit request or an explicit request. UUS Service 1
can be requested either implicitly or explicitly. Service 2 and 3 can only be requested explicitly.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 8 ETSI EN 301 710 V7.0.2 (1999-12)

4.1.1 Implicit request

The UUS1 service is activated implicitly by the presence of UUI in the set-up request from the mobile station. The
network shall transfer the received UUI transparently to the B-side. For the purpose of UUS service 1 implicitly
requested, no explicit check for the availability of UUS capabilities at the destination network has to be performed by
the originating network.

If the calling subscriber has UUS 1 provisioned and implicitly requested, the network shall transfer all UUI contained in
call control messages.

If the calling subscriber has UUS1 not provisioned, the contained UUI shall be discarded by the serving MSC. The call
shall be established without further restrictions.

The served subscriber shall not be informed whether the implicit request was successful or not.

4.1.2 Explicit request

Any UUS Service can be explicitly activated by the served subscriber within the set-up request initiating a mobile
originated call. In addition UUS Service 3 can be activated during an established call with a Facility message. A UUS
Service 1 request can be accompanied by appropriate UUI.

The network shall check for the availability of UUS capabilities for the call by passing the UUS request and the
eventually accompanied UUI to the remote side. If a UUS Service is available for the call an appropriate "UUS
provided" indication for this UUS Service shall be sent within the first backward message from the remote side.

A UUS Service shall not be activated for the call if a "UUS not provided" indication or no indication about the
availability of this UUS Service is received from the remote side.

Service 3 can be explicitly activated during an active call by both parties. This may lead to a collision of activation
requests. The collision of activation requests occurs when there is an outstanding request for service 3 and a subsequent
request is received from the remote user. The entity (user or network) that observes the collision shall reject the second
request with Facility message. This leads to the rejection of both requests.

4.1.3 UUS required option

As an option at call set-up the served subscriber can specify whether the requested UUS Service is required or not
required for the call. If service 1 is implicitly requested or if service 3 is requested during the call, it cannot be requested
as required.

If the served subscriber has specified that one of the UUS services is required for the call and this UUS service can not
be activated by the network, the call attempt of the served subscriber shall be cleared.

If the served subscriber has specified that one of the UUS services is not required for the call and this UUS service can
not be activated by the network, the call establishment shall be continued.

5 Handling of User-to-user signalling

5.1 Timers
UUS related timers are needed only for UUS service 3. Timers T1-UUS3, T3-UUS3 and T4-UUS3 are used only when
UUS service 3 is requested during an active call.

ETSI
 (GSM 03.87 version 7.0.2 Release 1998) 9 ETSI EN 301 710 V7.0.2 (1999-12)

Table 5.1: UUS Timers

Timer Name Value Run at Started Stopped Expiry

T1-UUS3 Remote 10s MSC of the UUS3 service request Answer to UUS3 Rejection of UUS3
network remote subscriber sent to the remote service request service is sent
control subscriber received from the toward the
remote subscriber requesting
network
T2-UUS3 UUS3 flow 10s MSC of the served The MSC receives When UUS3 service is Flow control
control subscriber and service acceptance deactivated parameter is
MSC of the incremented.
remote subscriber Timer is restarted.
Note 1.
T3-UUS3 Served 10s MS of the served UUS3 service request Acceptance to UUS3 Consider UUS3
subscriber subscriber sent to the requesting service received from service as not
control network requesting network activated
T4-UUS3 Serving 10s MSC of the served UUS3 service request Acceptance to UUS3 Rejection of UUS3
network subscriber sent to the remote service received from service is sent
control network remote network toward the served
subscriber

NOTE: If a user information message has been discarded due to flow control, a congestion control message shall
be sent to the user.

5.2 Information flows of UUS services

5.2.1 Service 1 (UUS1)

5.2.1.1 Flow control

No specific flow control is needed to restrict the amount of messages sent for either implicit or explicit UUS service 1 as
the user-to-user information is transferred in call control messages.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 10 ETSI EN 301 710 V7.0.2 (1999-12)

5.2.1.2 Information flows

5.2.1.2.1 Implicit activation

MSa MSCa VLRa GMSCb HLRb MSCb MSb

Set-up
SIFOC
UUI*
Complete call

IAM
UUI* SRI

SRI ack

IAM Set-up
UUI*
UUI*

ACM/ANM/CPG Alert
ACM/ANM/CPG UUI
Alert UUI
UUI
UUI

Connect

UUI
CON

CON UUI
Connect UUI

UUI

Disconnect

UUI
REL
UUI REL
Disconnect
UUI
UUI

Note: UUI* User-to-user information required for requesting the UUS service
UUI User-to-user information can be sent optionally

Figure 5.2.1.2.1.1: Information flow for UUS1 implicit request (mobile to mobile call)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 11 ETSI EN 301 710 V7.0.2 (1999-12)

5.2.1.2.2 Explicit activation

MSa MSCa VLRa GMSCb HLRb MSCb MSb

Set-up
SIFOC
S1=r,nr;
UUI
Complete call

IAM
S1=r,nr; SRI
UUI
SRI ack

IAM Set-up
S1=r,nr;
UUI S1=r,nr;
UUI
ACM/ANM/CPG Alert
ACM/ANM/CPG S1=p;
Alert S1=p; UUI
S1=p; UUI
S1=p; UUI
UUI

Connect

UUI

CON UUI
Connect UUI

UUI

Disconnect

UUI
REL
UUI REL
Disconnect
UUI
UUI

Note: S1 UUS Service 1

UUI User-to-user information can be sent optionally
r,nr requested, not required
p provided

Figure 5.2.1.2.2.1: Information flow for UUS 1 explicit request (mobile to mobile call)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 12 ETSI EN 301 710 V7.0.2 (1999-12)

5.2.2 Service 2 (UUS2)

5.2.2.1 Flow control

Up to two UUI messages can be sent in each direction. If either party tries to send more than two UUI messages, they
are discarded.

5.2.2.2 Information flows

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 13 ETSI EN 301 710 V7.0.2 (1999-12)

MSa MSCa VLRa GMSCb HLRb MSCb MSb

Set-up
SIFOC
S2=r,nr
Complete call

IAM
SRI
S2=r,nr
SRI ack

IAM
Set-up
S2=r,nr S2=r,nr
Alert
ACM/ANM/CPG
ACM/ANM/CPG S2=p
Alert S2=p
S2=p
S2=p

User info
User info
User info
UUI User info
UUI
UUI
UUI

User info
User info
User info UUI
UUI
User info
UUI
UUI
Connect

CON
CON

Connect

Note: S2 UUS Service 2

UUI User-to-user information
r,nr requested, not required
p provided

Figure 5.2.2.2.1: Information flow for UUS2 explicit request (mobile to mobile call)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 14 ETSI EN 301 710 V7.0.2 (1999-12)

5.2.3 Service 3 (UUS3)

5.2.3.1 Flow control

Network flow control mechanisms shall exist after the connection has been established in order to restrict the amount of
UUI sent in each direction. A burst capability of sending N messages shall immediately be available to each user, where
N initially equals the value of the burst parameter X. The value of N shall be decremented by one for every message sent
by the user and incremented by Y at regular intervals of T2-UUS3 (see table 5.1). The value of N shall be limited to a
maximum of X.

The value of the burst parameter X shall be 16.

The value of the replenishment parameter Y shall be 8.

Network flow control shall be performed only by the sending user’s network.

If the MSC receives UUI messages from the MS at a rate which exceeds the flow control limit, it shall discard the UUI
messages that cannot be handled and respond to the first discarded UUI message with a congestion control message.

When the flow control restrictions are removed, an indication that further UUI messages can be accepted shall be given.
See the Processes Serving_MSC_Handle_UUS_In_Active_Call and Remote_ MSC_Handle_UUS_In_Active_Call.

5.2.3.2 Information flows

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 15 ETSI EN 301 710 V7.0.2 (1999-12)

MSa MSCa VLRa GMSCb HLRb MSCb MSb

Set-up
SIFOC
S3=r,nr
Complete call

IAM
SRI
S3=r,nr
SRI ack

IAM
Set-up
S3=r,nr
S3=r,nr
Alert
ACM/ANM/CPG
ACM/ANM/CPG
Alert

Connect
CON S3=p
CON
Connect S3=p
S3=p
S3=p
User info
User info
UUI User info
UUI User info
UUI
UUI

User info
User info
User info UUI
UUI
User info
UUI
UUI
Disconnect

REL
REL

Disconnect

Note: S3 UUS Service 3

UUI User-to-user information
r,nr requested, not required
p provided

Figure 5.2.3.2.1: Information flow for UUS3 explicit request during call establishment
(mobile to mobile call)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 16 ETSI EN 301 710 V7.0.2 (1999-12)

MSa MSCa VLRa GMSCb HLRb MSCb MSb

Active call A-B

Facility
Uus act
S3=r
Uus act ack

Facility
S3=r

Facility
Facility
S3=r
S3=r

Facility
S3=p
Facility
Facility
Facility S3=p
S3=p
S3=p

User info
User info
UUI User info
UUI User info
UUI
UUI

User info
User info
User info UUI
UUI
User info
UUI
UUI
Disconnect

REL
REL

Disconnect

Note: S3 UUS Service 3

UUI User-to-user information
r requested
p provided

Figure 5.2.3.2.2: Information flow for UUS3 explicit request during active call (mobile to mobile call)

5.3 Messages and their contents

This subclause contains the detailed description of the information flows used by UUS.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 17 ETSI EN 301 710 V7.0.2 (1999-12)

Each Information Element, IE is marked as (M) Mandatory, (C) Conditional, or (O) Optional. A mandatory information
element shall always be present. A conditional information element shall be present if certain conditions are fulfilled; if
those conditions are not fulfilled it shall be absent. An optional information element may be present or absent, at the
discretion of the application at the sending entity. This categorisation is a functional classification, i.e. stage 2
information and not a stage 3 classification to be used for the protocol.

The stage 2 and stage 3 message and information element names are not necessarily identical.

5.3.1 Information elements used in the messages

The following UUS specific constructed information elements are used in the messages.

Table 5.3.1.1: UUS specific information elements

Parent Information Child Information Information Information element description

Element Element name element
Required
UUS options UUS1 C The information element is present if UUS1 service is
requested; otherwise it shall be absent. It may contain the
following values:
- Required
- Not Required
UUS2 C The information element is present if UUS2 service
is requested; otherwise it shall be absent. It may
contain the following values:
- Required
- Not Required
UUS3 C The information element is present if UUS3 service
is requested; otherwise it shall be absent. It may
contain the following values:
- Required
- Not Required
UUS provision UUS1 C If UUS1 services is requested and provisioned the
information element is present, otherwise it shall be
UUS2 C absent.
If UUS2 services is requested and provisioned the
UUS3 C information element is present, otherwise it shall be
absent.
If UUS3 services is requested and provisioned the
information element is present, otherwise it shall be
absent.

5.3.2 Messages between MS and MSC

Call control messages (Setup, Alert, Connect, Disconnect, Release and Release Complete, refer to GSM 04.08) may
carry UUS service activation request and response. They can carry also UUI for UUS1.

Facility message, refer to GSM 04.08, can carry UUS service 3 activation request and response.

Dedicated User-To-User message, refer to GSM 04.08, carries UUI for UUS service 2 and 3.

These messages are used both in serving and remote networks.

ETSI
 (GSM 03.87 version 7.0.2 Release 1998) 18 ETSI EN 301 710 V7.0.2 (1999-12)

5.3.3 Messages between MSC and VLR (B interface)

These messages are used in the serving network.

Table 5.3.3.1: Messages between MSC and VLR

Message Message Information Information Information element description

sender element name element
Required
Send Info For MSC - - Refer to GSM 03.18.
Outgoing Call
In addition:
UUS options C The information element is present if MS A requested
UUS service; otherwise it shall be absent. The
structure of UUS options is defined in table 5.3.1.1
Send Info For VLR - - Refer to GSM 03.18
Outgoing Call
negative response In addition:
UUS reject C The information element is present, if required UUS
service was requested by MS A and service is not
provided, otherwise it shall be absent.
Complete Call VLR - - Refer to GSM 03.18

Send Info For UUS3 MSC
Send Info For UUS3 VLR
Ack
In addition:
UUS provision C The information element is present if MS A requested
UUS service(s); otherwise it shall be absent. The
structure of UUS Provision is defined in table 5.3.1.1
- - The message is sent when UUS3 service is requested
during active call. NOTE: This message is used in
serving and remote MSCs.
UUS provision C The information element is present if UUS3 service is
provisioned; otherwise it shall be absent

5.3.4 Messages between MSC – MSC (E interface)

These messages are used in the remote network when UUS is supported in remote MSC in conjuction of SOR, refer to
GSM 03.79.

Table 5.3.4.1: Messages between MSC - MSC

Message Message Information Information Information element description

sender element name element
Required
Resume Call MSCB - - Refer to GSM 03.79.
Handling
In addition:
UUS1 Service C The information element is present if UUS1 Service
request was requested in the original call and remote MSC
supports UUS service; otherwise it shall be absent.
C The information element is present if UUS2 Service
UUS2 Service was requested in the original call and remote MSC
request supports UUS service; otherwise it shall be absent
C The information element is present if UUS3 Service
was requested in the original call and remote MSC
UUS3 Service supports UUS service; otherwise it shall be absent.
request C The information element is present if UUS1 UUI was
present in the original call and remote MSC
supports UUS service; otherwise it shall be absent.
UUS1 UUI C The information element is present if the remote
subscriber has accepted UUS1 service request and
call forwarding or call deflection has been activated
UUS CF interaction after that; otherwise it shall be absent.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 19 ETSI EN 301 710 V7.0.2 (1999-12)

6 Interaction with other supplementary services

GSM 02.87 specifies interaction of UUS with other supplementary services. Additional details are provided in this
clause.

6.1 Call forwarding unconditional (CFU)

No impact.

6.2 Call forwarding on mobile subscriber busy (CFB)

No impact, if CFB is invoked due to a NDUB condition or due to UDUB before an alerting message was received from
the mobile station.

If CFB is invoked due to a UDUB indication from the B forwarding subscriber the same interaction as for CFNRy shall
apply.

6.3 Call forwarding on no reply (CFNRy)

If UUS Service 1 is implicitly requested for a call to a subscriber who has Call Forwarding on no reply active and
operative, the forwarding MSC shall store the UUI. If CFNRy is invoked, the stored UUI shall be forwarded with the
call.

If UUS Service 1 is explicitly requested as not required for a call to a subscriber who has Call Forwarding on no reply
active and operative, the forwarding MSC shall store UUS 1 service request and UUI, if any. If the forwarding user
accepts the UUS1 supplementary service request in the Alerting message, the CFNRy supplementary service can be
invoked and the stored UUS1 service request and UUI, if any, shall be forwarded with the call. If the forwarding user
rejects the UUS1 supplementary service request or does not include a response related to it in the Alerting message, then
the CFNRy supplementary service can be invoked but the UUS1 service request and UUI, if any, shall not be forwarded
with the call.

If UUS Service 1 is explicitly requested as required for a call to a subscriber who has Call Forwarding on no reply active
and operative and the no reply condition timer expires, the remote MSC shall release the call towards the calling
subscriber.

If Call Forwarding on no reply is invoked for a call for which UUS Service 2 was requested as not required, UUS
Service 2 shall not be requested for the forwarding leg, i.e. UUS 2 is no longer available for the call.

Call Forwarding on no reply shall not be invoked if UUS Service 2 was requested required for the initial mobile
terminated call.

If UUS Service 3 is requested for a call to a subscriber who has Call Forwarding on no reply active and operative, the
forwarding MSC shall store the UUS3 request. If CFNRy is invoked the UUS3 request shall be forwarded with the call.

For further details refer to procedures UUS_ICH_Check_Forwarding and UUS_MSC_Clear_UUS.

6.4 Call forwarding on mobile subscriber not reachable

(CFNRc)
No impact.

6.5 Call waiting (CW)

No impact.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 20 ETSI EN 301 710 V7.0.2 (1999-12)

6.6 Call hold (HOLD)

No impact.

6.7 Completion of calls to busy subscribers (CCBS)

Requests for the activation of the UUS supplementary service contained in the original call request shall be maintained
along with other call information used for the CCBS supplementary service.

The network shall also store any UUI containing in the original call request and use this stored UUI in the CCBS call.

6.8 Explicit call transfer (ECT)

When calls are transferred as a result of invocation of explicit call transfer supplementary service, the UUS
supplementary service activated on either of the calls prior to the invocation of the explicit call transfer supplementary
service shall be cancelled by the network.

No specific notification shall be sent to the users on the resulting call when the UUS supplementary service is no longer
activated.

The users on the resulting call can request service 3 again, if required.

6.9 Multi party service (MPTY)

No impact.

6.10 Advice of charge (AoC)

No impact.

6.11 Barring of outgoing calls (BAOC)

No impact.

6.12 Barring of outgoing international calls (BOIC)

No impact.

6.13 Barring of outgoing international calls except those directed

to the home PLMN country (BOIC-exHC)
No impact.

6.14 Barring of incoming calls (BAIC)

No impact.

6.15 Barring of incoming calls when roaming outside the home

PLMN country (BIC-Roam)
No impact.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 21 ETSI EN 301 710 V7.0.2 (1999-12)

6.16 Call deflection (CD)

If Call Deflection is invoked before alerting there is no impact.

If Call Deflection is invoked after alerting the same interactions as for Call forwarding on no reply shall apply.

7 Interaction with other network features

7.1 Customised Applications for Mobile network Enhanced

Logic (CAMEL)
No impact.

7.2 Support for Optimal Routeing(SOR)

The invocation of Optimal Routeing in case of late call forwarding shall have no impact on the interactions of UUS with
the call forwarding supplementary services as defined in clause 6.

The UUS request, UUI and UUS CF interaction indicator, if any, shall be added to the Resume Call Handling message
in remote MSC when SOR late call forwarding is applied. For details refer to the procedure UUS_ICH_Handle_LCF in
SDLs and the procedure Handle_ORLCF_VMSC (see GSM 03.79).

The UUS request and UUI, if any, shall be copied from the Resume Call Handling message to the IAM in GMSC when
SOR late call forwarding is applied. For details refer to the procedure UUS_GMSC_Check_Forwarding in SDLs and the
procedure OR_Handle_RCH (see GSM 03.79).

If UUS CF interaction indicator was present in Resume Call Handling message, the presence of UUS1 Service
acceptance and UUI, if any, shall be modified during call setup time. For further details refer to the procedure
MT_CF_MSC (see GSM 03.18) and UUS_MSC_Clear_UUS.

8 Interworking with other networks

8.1 Interworking with GSM PLMN/ISDN network supporting only

a maximum User-user information element length of 35
octets
If interworking occurs with a network supporting only a maximum of User-user information element length of 35 octets,
no notification shall be given to the calling user or called user sending the user information.

8.2 Interworking with non-ISDN network

In the case of interworking with non-ISDN network or with a non-ISDN called user, a progress indicator information
element indicating #1 "call is not end-to-end ISDN; further progress information may be available in-band" or #2
"destination address is non-ISDN", respectively, is sent to the calling user as part of basic call.

This progress information shall serve as indication that the requested service cannot be guaranteed.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 22 ETSI EN 301 710 V7.0.2 (1999-12)

9 Network entity functions

9.1 Originating network processes

9.1.1 Procedures in MSC
Figure 9.1.1.1 Procedure UUS_OCH_Check_Setup

This procedure is called when Setup is received from A-subscriber. It sets requested UUS service options into SIFOC
message.

Figure 9.1.1.2 Procedure UUS_OCH_Set_Info_In_IAM

Requested UUS service options and possible UUS1 data is copied in IAM. The procedure is controlled by the Complete
Call message parameters from the VLR.

Figure 9.1.1.3 Procedure UUS_OCH_Set_Alert_And_Connect_Param

In this procedure UUS related parameters are checked and set into the Alerting/Connect message that is sent to
A-subscriber. If any of the UUS services is requested as required and positive service acknowledgement is not received
from the remote end, the check will fail and the call will be cleared.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 23 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_OCH_Check_Setup 1(1)

This pro cedu re is running

in the MSC a nd sets the UU S
spec ific par amete rs to SIFOC
messa ge

No Ei ther imp li cit

UUS1
or expl icit
requ ested
request

Yes

No
R equ ested
a s required

Yes

Set U US1 Set U US1

"require d" to "no t req uired"
SIFOC to SIFOC

No
UUS2
requ ested

Yes

No
R equ ested
a s required

Yes

Set U US2 Set U US2

"require d" to "no t req uired"
SIFOC to SIFOC

No
UUS3
requ ested

Yes

No
R equ ested
a s required

Yes

Set U US3 Set U US3

"require d" to "no t req uired"
SIFOC to SIFOC

Figure 9.1.1.1: Procedure UUS_OCH_Check_Setup

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 24 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_OCH_Set_Info_In_IAM 1(1)

This pro cedu re is running

in the MSC a nd it sets UUS S1 = UU S Service 1
spec ific par amete rs to the S2 = UU S Service 2
IAM mes sage S3 = UU S Service 3
r,nr = req uested, n ot re qu ired
r,r = requ ested, require d
No
UUS1
requ ested

Yes
No
UUS1
provisio ned

Yes
No
Imp lici t
re qu est

Yes Requested No
as
req uire d

Ye s

S1:=r,r S1:=r,nr

U US1 Copy S1 to
i mpl ici t
IAM
a ctive:=True

No
UU S1 data
pre sent

Ye s
C opy UU S d ata Copy UUS data
to IAM to IAM 1

No
UUS2 UUS3
requ ested requested

Yes Yes
No
UUS2 UUS3
provisio ned provi sio ned

Yes Yes
R equ ested R equ ested
as as
re qu ired No required No
Yes Yes

S2 :=r,r S2:=r,nr S3:=r,r S3:=r,n r

C opy S2 to C opy S3 to
IAM IAM

No

Figure 9.1.1.2: Procedure UUS_OCH_Set_Info_In_IAM

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 25 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_OCH_Set_Alert_And_Connect_Param 1(1)

This pro cedu re is running in

th e MSC an d it se ts the U US
parameters to the ca ll con trol
messa ges directe d back to
th e in itiatin g MS

Yes
UU S1
reque ste d

No
UU S_MSC _
Check_ UU S1

Pass Fail
Yes Yes
UU S2 UUS2
reque ste d requ ested

No No
UU S_MSC _ UUS_MSC_
Check_ UU S2 Check_U US2

Pass Fail
Yes Yes
UU S3 UUS3
reque ste d requ ested

No No
UU S_MSC _ UUS_MSC_
Check_ UU S3 Check_U US3

Pass Fail
UU S_MSC_ U US_MSC _
Check_ UUS1_ C hec k_UU S1_
UU I U UI

Result := R esu lt :=
Pass Fai l

Figure 9.1.1.3: Procedure UUS_OCH_Set_Alert_And_Connect_Param

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 26 ETSI EN 301 710 V7.0.2 (1999-12)

9.1.2 Procedures in VLR

Figure 9.1.2.1 Procedure UUS_OCH_Check_Provision

This procedure is called in the VLR during subscription checks for an outgoing call. It sets requested UUS service
provision information in Complete call message. If any of the UUS services is requested as required and the service is
not provided to the subscription, the check will fail and the call will be cleared.

Procedure UUS_OCH_Check_Provision 1(1)

Th is pro cedu re is run ni ng in

th e VLR a nd it do es th e UU S
spec ific pro visio ni ng che cks

No
UUS1
requ ested

Yes

No
UUS1
provi sio ned

Yes

Se t UU S1 U US1
"p rovi sio ned " to re qu ired
C omp lete C all Ye s

No

No
UUS2
requ ested

Yes

No
UUS2
provi sio ned

Yes

Se t UU S2 U US2
"p rovi sio ned " to re qu ired
C omp lete C all Ye s

No

No
UUS3
requ ested

Yes

No
UUS3
provi sio ned

Yes

Se t UU S3 U US3
"p rovi sio ned " to re qu ired
C omp lete C all Ye s
Set neg ative
No resp ons e:=
UU S R eje ct

R esu lt :=
Pa ss
Re sult :=
Fail

Figure 9.1.2.1: Procedure UUS_OCH_Check_Provision

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 27 ETSI EN 301 710 V7.0.2 (1999-12)

9.2 Terminating network processes

9.2.1 Procedures in GMSC
Figure 9.2.1.1 Procedure UUS_GMSC_Check_Forwarding

This procedure is called when Resume Call Handling message is received from the remote MSC. If the message contains
UUS related information, that is copied to the subsequent IAM message.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 28 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_GMSC_Check_Forwarding 1(1)

This pro cedu re is running in

th e GMSC and it ch eck wh ether
UUS specific data shal l be
fo rward ed i n the optimal ro utei ng
case

No
UU S data
rece ived in
RC H messa ge?

Ye s

No
UU S CF i nterac ti on
se t in R CH me ssage?

Ye s

UU S C F
in te raction :=
True

Add recei ved

UU S inform ation
to IAM

Figure 9.2.1.1: Procedure UUS_GMSC_Check_Forwarding

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 29 ETSI EN 301 710 V7.0.2 (1999-12)

9.2.2 Procedures in MSC

Figure 9.2.2.1 Procedure UUS_ICH_Check_Support

This procedure is called after Alerting/Connect message is received from B-subscriber. It checks whether UUS service is
possible and if not whether the call setup can be continued.

Figure 9.2.2.2 Procedure UUS_ICH_Check_Forwarding

This procedure is called when no reply is received from B-subscriber. It checks whether call forwarding is allowed from
UUS service point of view.

Figure 9.2.2.3 Procedure UUS_ICH_Handle_LCF

This procedure is used to add UUS information to Resume Call Handling message when Optimal Routeing late call
forwarding is supported.

Figure 9.2.2.4 Procedure UUS_ICH_Set_Info_In_IAM

This procedure is used to add UUS specific information to forwarded call IAM message.

Figure 9.2.2.5 Procedure UUS_ICH_UUS1_Implicit_Active

This procedure is used to set UUS1 implicit service active at the remote MSC when only UUI for service 1 is received.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 30 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_ICH_Check_Support 1(1)

S1 = UUS Serv ice 1
This pro cedu re is running p = servi ce is
in the MSC a nd it che cks provi ded b y the
UUS rel ated param eters re mote MS

From the
UUS1
o rig ina ti ng
requested
GMSC Yes

No
UU S_MSC _
Ch eck_UU S1

Pass Fai l

From the From the

UUS2 UU S2
o rig ina ti ng ori gin atin g
requested re que sted
GMSC Yes GMS C Yes
No No
UU S_MSC _ UUS_MSC_
Ch eck_UU S2 Check_U US2

Pass Fai l

From the From the

UUS3 UU S3
o rig ina ti ng ori gin atin g
requested re que sted
GMSC Yes GMS C Yes

No No

UU S_MSC _ UUS_MSC_
Ch eck_UU S3 Check_U US3

Pass Fai l

Set UU S options N OTE: U US Set UUS op tion s

to first bac kward o ptions is ne ver to first b ackw ard
m essage set for im pli cit mes sage
U US1 se rvice

U US_MSC _ UU S_MSC_
C hec k_UU S1_ Ch eck_ UUS1 _
U UI UU I

Result:= Re sul t:=

Pass Fai l

Figure 9.2.2.1: Procedure UUS_ICH_Check_Support

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 31 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_ICH_Check_Forwarding 1(1)

This pro cedu re is running

in the MSC a nd it che cks
whe th er UU S ca n be
fo rward ed a nd i f cal l
fo rward in g is al low ed.
NOTE: UUS CF in te raction
fl ag i s set if UU S1 servi ce
request respo nse w as
sent to th e serving nw and
CF h ap pen s after that

No

U US1 p resen t

Yes

No

Exp lic it
re qu est

Yes

No
re qu ested
a s required

Yes
UUS1
explici t
active ? True

False

Cle ar stored UU S C F
UUS1 se rvice in te raction :=
requ est (and U UI) True

U US2 p resen t
No
Yes

re qu ested
a s requ ired
No

Yes
Cle ar stored
UUS2 service
request

Resu lt:= Resu lt:= Resu lt:= Resu lt:=

Fa il Fa il Pass Pass

Figure 9.2.2.2: Procedure UUS_ICH_Check_Forwarding

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 32 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_ICH_Handle_LCF 1(1)

This pro cedu re is running in

th e MSC an d it ch ecks w hethe r
UUS wi ll b e forward e in the
optim al rou teing case

No
UUS
data
sto red?

Yes

Add UU S
i nforma ti on to
R CH me ssage

U US CF No
i ntera cti on
= Tru e?

Yes

Add UU S C F
intera ction fl ag
to R CH me ssage

Figure 9.2.2.3: Procedure UUS_ICH_Handle_LCF

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 33 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_ICH_Set_Info_In_IAM 1(1)

This pro cedu re is running in

th e MSC an d it ch ecks w hethe r
UUS wi ll b e added to the IAM
messa ge i n the cal l fo rwardin g
case

U US information No
recei ved, stored
a nd n ot cl ea red

Yes

Add UU S
i nforma ti on
to IAM

Figure 9.2.2.4: Procedure UUS_ICH_Set_Info_In_IAM

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 34 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_ICH_UUS1_Implicit_Active 1(1)

This pro cedu re is running in

th e MSC an d it se ts the i mpl ici t
UUS1 active when U UI i s send

UUS1 No
imp licit
request?

Yes

UUS1 i mpl ici t

active :=
Tru e

Figure 9.2.2.5: Procedure UUS_ICH_UUS1_Implicit_Active

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 35 ETSI EN 301 710 V7.0.2 (1999-12)

9.3 Procedures common in serving and remote networks

Figure 9.3.1 Procedure UUS_MSC_Check_UUS1_UUI

This procedure is used to check whether it is allowed to pass UUI for UUS1 from MS to network or vice versa.

Figure 9.3.2 Procedure UUS_MSC_Check_UUS2_UUI_to_MS

This procedure is used to check whether it is allowed to pass User-To-User messages for UUS2 from network to MS.

Figure 9.3.3 Procedure UUS_MSC_Check_UUS2_UUI_to_NW

This procedure is used to check whether it is allowed to pass User-To-User messages for UUS2 from MS to network.

Figure 9.3.4 Procedure UUS_MSC_Check_UUS3_UUI_to_MS

This procedure is used to check whether it is allowed to pass User-To-User messages for UUS3 from network to MS.

Figure 9.3.5 Procedure UUS_MSC_Check_UUS3_UUI_to_NW

This procedure is used to check whether it is allowed to pass User-To-User messages for UUS3 from MS to network.

Figure 9.3.6 Procedure UUS_MSC_Clear_UUS

This procedure is used to handle the call forwarding interaction with UUS when call control messages are received from
the forwarded-to NW.

Figure 9.3.7 Macrodefinition UUS_MSC_Check_UUS1

Macro used in procedures UUS_OCH_Set_Alert_And_Connect_Param and UUS_ICH_Check_Support. It checks

whether UUS service 1 is supported.

Figure 9.3.8 Macrodefinition UUS_MSC_Check_UUS2

Macro used in procedures UUS_OCH_Set_Alert_And_Connect_Param and UUS_ICH_Check_Support. It checks

whether UUS service 2 is supported.

Figure 9.3.9 Macrodefinition UUS_MSC_Check_UUS3

Macro used in procedures UUS_OCH_Set_Alert_And_Connect_Param and UUS_ICH_Check_Support. It checks

whether UUS service 3 is supported.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 36 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS1_U UI 1(1)

Signals to/from the left are

This procedure is running in
the MSC and it checks whether to/f rom the BSS;
signals to/from the right are
UUI can be passed over to/f rom the destinat ion exchange
unless otherwise marked.

No
UUS1 implicit
active = True?

Yes

Yes
UUS1 explicit
active = True?

No

No
UUI
received?

Yes

Pass UUI

Figure 9.3.1: Procedure UUS_MSC_Check_UUS1_UUI

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 37 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS2_UUI_to_MS 1(1)

Si gn als to/from the le ft are
This pro cedu re is running in to/from the BSS;
th e MSC an d it ch ecks w hethe r si gnals to/from the rig ht are
UUI can be passe d ove r to/from the d estination e xchange
u nl ess othe rwise m arked.

UU S2 No
active =
True?

Yes

User To Us er

Figure 9.3.2: Procedure UUS_MSC_Check_UUS2_UUI_to_MS

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 38 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS2_U UI_to_NW 1(1)

This procedure is running in Signals to/from the left are

the MSC and it checks whether to/f rom the BSS;
UUI can be passed over. In addition signals to/from the right are
it handles UUS2 flow control to/f rom the destinat ion exchange
unless otherwise marked.

No
UUS2
active=
True?

Yes

UTU2Cnt
2
<2

UTU2Cnt:=
UTU2Cnt + 1

User To User

Figure 9.3.3: Procedure UUS_MSC_Check_UUS2_UUI_to_NW

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 39 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS3_U UI_to_MS 1(1)

Signals to/from the left are

This procedure is running in to/f rom the BSS;
the MSC and it checks whether signals to/from the right are
UUI can be passed over. to/f rom the destinat ion exchange
unless otherwise marked.

No
UUS3
active=
True?

Yes

User To User

Figure 9.3.4: Procedure UUS_MSC_Check_UUS3_UUI_to_MS

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 40 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS3_UUI_to_NW 1(1)

Si gn als to/from the le ft are
This pro cedu re is running in to/from the BSS;
th e MSC an d it ch ecks w hethe r si gnals to/from the rig ht are
UUI can be passe d ove r. In ad dition to/from the d estination e xchange
it h an dle s U US3 flow con tro l u nl ess othe rwise m arked.

No
U US3
a ctive=
True?

Yes

N >0 ?
No

Yes

True
Cong estio n
N:=N-1 co ntrol
se nt?

Fal se

Use r To Us er Co nge stion Inform the MS th at

Co ntrol it is no t al low ed to
send any UU Is

Cong estio n
co ntrol se nt
:= True

Figure 9.3.5: Procedure UUS_MSC_Check_UUS3_UUI_to_NW

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 41 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Clear_UUS 1(1)

This procedure is running in S1 = UUS1 Service response

the MSC and it handles CFNRy
and UUS int eraction when the
MSC is receiv ing call control
mes sages f rom f orwarded-t o NW.

No
UUS CF
interaction =
True

Yes

Clear received
(if any) S1

Yes
Received msg
was Answer or
Connec t?

No

Clear received
(if any) UUI

Figure 9.3.6: Procedure UUS_MSC_Clear_UUS

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 42 ETSI EN 301 710 V7.0.2 (1999-12)

Macrodefinition UUS_MSC_Check _UUS1 1(1)

np = service is not
provided by network
or remote end

True UUS1
result
sent?

False

Alert
received?
No
Yes

explicit Connect
request received?
Yes Yes
No No
S1 explicit
received request
No No
Yes Yes

UUS1 result UUS1 result

sent := True sent := True

No
S1
received

Yes

Do not send Pass received Do not send Pass received

S1 S1 S1 S1 S1:=np

No No
S1=np? S1=np?

Yes Yes
UUS1 explicit UUS1 explicit
active:=True active:=True

UUS1 UUS1
Required? Required?
No No
Yes Yes

Pass Fail Pass Fail

Figure 9.3.7: Macrodefinition UUS_MSC_Check_UUS1

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 43 ETSI EN 301 710 V7.0.2 (1999-12)

Macrodefinition UUS_MSC_Check _UUS2 1(1)

np = service is not
provided by network
or remote end

No
Alert
received?

Yes

No
S2
received

Yes

Pass received
S2 S2:=np

No
S2 = np?

Yes
UUS2 active
:=True
No
UUS2
Required?

Yes

Fail Pass

Figure 9.3.8: Macrodefinition UUS_MSC_Check_UUS2

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 44 ETSI EN 301 710 V7.0.2 (1999-12)

Macrodefinition UUS_MSC_Check _UUS3 1(1)

np = service is not
provided by network
or remote end

No
Connect
received?

Yes

No Yes
S3 S3
received received

Yes No

Pass received
S3 S3:=np

No
S3 = np?

Yes

UUS3 active
:=True

UUS3
Required?
No
Yes

Fail Pass Fail

Figure 9.3.9: Macrodefinition UUS_MSC_Check_UUS3

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 45 ETSI EN 301 710 V7.0.2 (1999-12)

9.4 Processes used during Active Call

There are different processes running for UUS3 during active call in serving and remote network. However, this
differentiation does not implicitly mean that call originator’s network is serving network. The differentiation is based on
which party initiates the UUS3 service. Thus, serving network process shall be used on initiator's side and remote
network process on the opposite end.

9.4.1 Process and procedures in serving MSC

Figure 9.4.1.1 Process Serving_MSC_Handle_UUS_In_Active_Call

This process is used to check UUS3 activation during active call, handle UUS3 flow control and interaction with ECT
supplementary service. The process starts during the call setup and checks the content of the Connect message in order
to start the UUS3 flow control correctly. If the UUS3 is not activated the process stays in the Idle state and waits UUS3
activation request from the MS.

Figure 9.4.1.2 Procedure UUS_MSC_Check_UUS3_Activation

This procedure is used to handle the dialogue towards the serving VLR when provisioning check is done.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 46 ETSI EN 301 710 V7.0.2 (1999-12)

Process Serving_MSC_Handle_UUS_In_Active_Call 1(4)

This process is running in

the serving MSC. It handles
UUS3 during the act ive call Signals to/from the left are
to/f rom the BSS; signals t o/from
the right are to/from the
destination/ originating exchange
unless otherwise marked.

p = provided i.e. UUS3

service is provided
Congestion np = not provided i.e.
control sent UUS3 service is not
:= False provided

IDLE

Facility Connec t From GSM 03.18 processes

UUS_MSC_
Check_UUS3_ Connec t
Activation

UUS3
Result? active=
Abort ed Fail No True?

Pass Yes

X:=16 UUS3 flow control

Start T4-UUS3 S3:=np N:=X parameters
Y:=8

Facility Facility Start T2-UUS3

Wait_For_
Activation_ IDLE Active_Call
Response

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 1)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 47 ETSI EN 301 710 V7.0.2 (1999-12)

Process Serving_MSC_Handle_UUS_In_Active_Call 2(4)

Si gn als to/from the le ft are
This pro cess is run ni ng in to/from the BSS; signal s to /from
th e servi ng MSC. It ha ndl es the righ t are to /from the
UUS3 duri ng the acti ve cal l d estination /orig inating excha nge
u nl ess othe rwise m arked.

Wai t_ Fo r_ p = provi ded i.e. UUS3

Activati on_ se rvice i s provided
Respon se n p = no t p rovided i .e .
U US3 se rvice is n ot
p rovi ded

Fac ili ty T4-UU S3

exp iry

Stop T4-UU S3 S3:=np

S3=p?
No
Ye s

UU S3 active
:=True

X:=16
N:=X UU S3 fl ow co ntrol
parame ters
Y:=8

Facil ity Fac ili ty

Start T2 -UUS3

Active _Ca ll ID LE

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 2)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 48 ETSI EN 301 710 V7.0.2 (1999-12)

Process Serving_MSC_Handle_UUS_In_Active_Call 3(4)

Sig nal s to/from the l eft a re
This pro cess is run ni ng in to/fro m th e BSS; si gna ls to/fro m
th e servi ng MSC. It ha ndl es the right are to/fr om the
UUS3 duri ng the acti ve cal l de sti na ti on/ori gi natin g exchange
un less o th erwi se ma rked.

Re lea se From GSM 03.18 processes Re lea se NOTIFY N OTIFY

transa ction transaction (ECT) (EC T)

R elease R ele ase N OTIFY NOTIFY

To GSM 03.18 processe s
tran saction tran sactio n (EC T) (ECT)

U US1 i mpli cit active := Fal se

U US1 e xpli cit active := Fals e
U US2 a ctive := Fa lse
U US3 a ctive := Fa lse
Stop T2 -UUS3

ID LE

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 3)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 49 ETSI EN 301 710 V7.0.2 (1999-12)

Process Serving_MSC_Handle_UUS_In_Active_Call 4(4)

This pro cess is run ni ng in

Si gn als to/from the le ft are
th e servi ng MSC. It ha ndl es
to/from the BSS; signal s to /from
UUS3 duri ng the acti ve cal l the righ t are to /from the
Acti ve_ Cal l d estination /orig inating excha nge
u nl ess othe rwise m arked.

U ser To User U ser To User T2-UU S3

expiry

UU S_MSC_ U US_MSC _
Ch eck_UUS3 _ C hec k_UU S3_ N = 0?
UU I_to_MS U UI_to_N W No

Yes

N :=N+Y N:=N +Y

Con ges tion Fa lse

control N > X?
sent? Ye s
True No

Inform MS that
i t i s a llo we d to C ong estio n N := X
C ontrol
se nd U UIs

Con ges tion

control sent
:= Fa lse

Sta rt T2-U US3 Start T2 -UUS3

Acti ve_ Cal l

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 4)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 50 ETSI EN 301 710 V7.0.2 (1999-12)

Procedure UUS_MSC_Check_UUS3_Activation 1(1)

This pro cedu re is running in

th e MSC an d it ch ecks U US3 Sig nal s to/from the ri gh t
activa tion durin g active ca ll are to/from the VL R
un less o th erwi se ma rked.

Se nd _Info_
For_ UU S3

Wai t_ For_
An swer

Sen d_Info_
From BSS Re lea se From GS M 0 3.18 R ele ase For_U US3_
transaction tran sactio n
Ack

To GSM 03 .1 8 R elease To BSS Re lease U US3

tran saction transa ction p rovi sioned?
No
Yes

Wai t_ Fo r_Ack

Se nd _Info_
For_ UU S3_
Ack

Re sul t:= Resu lt:= Re sult:=

Ab orted Pass Fail

Figure 9.4.1.2: Procedure UUS_MSC_Check_UUS3_Activation

9.4.2 Process and procedures in serving VLR

Figure 9.4.2.1 Process Serving_VLR_Handle_UUS_In_Active_Call

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 51 ETSI EN 301 710 V7.0.2 (1999-12)

This process is running in the serving VLR. If the UUS3 activation request comes during the active call, this process is
used to check whether the service is provisioned to the subscriber.

Process Serving_VLR_Handle_UUS_In_Active_Call 1(1)

This pro cess is run ni ng in

th e VLR a nd it checks th e Si gn als to/from le ft are
UUS3 provision in g sta tu s to/from MSC unle ss
otherw ise ma rked

ID LE

Se nd _Info_
For_ UU S3

U US3
p rovi sioned?

Yes

Set U US
provi sio ned

No
Se nd _Info_
For_ UU S3_Ack

ID LE

Figure 9.4.2.1: Process Serving_VLR_Handle_UUS_In_Active_Call

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 52 ETSI EN 301 710 V7.0.2 (1999-12)

9.4.3 Process and procedures in remote MSC

Figure 9.4.3.1 Process Remote_MSC_Handle_UUS_In_Active_Call

This process is running in the remote MSC. It is used for checking whether UUS3 UUI’s can be passed on and control
the flow control for UUS3. The process starts during the call setup and checks the content of the Connect message in
order to start the UUS3 flow control correctly. If the UUS3 is not activated the process stays in the Idle state and waits
UUS3 activation request from the NW.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 53 ETSI EN 301 710 V7.0.2 (1999-12)

Process Remote_MSC_Handle_UUS_In_Active_Call 1(4)

This pro cess is run ni ng in

th e remote MSC and i t h andles Sig nal s to/from the l eft a re
UUS3 flow contro l to/fro m th e BSS; si gna ls to/fro m
the right are to/fr om the
de sti na ti on/ori gi natin g exchange
un less o th erwi se ma rked.

Cong estio n
co ntrol se nt
:= Fals e

IDLE

Fac ili ty Co nne ct

Facil ity C onn ect To GSM 03.18 processe s

UU S3
active =
True? No

Ye s

X:=16
N:=X
Y:=8

Start T1_UU S3 Start T2_UU S3

Wai t_ Fo r_
Activation_ Active _Ca ll IDLE
Respon se

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 1)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 54 ETSI EN 301 710 V7.0.2 (1999-12)

Process Remote_MSC_Handle_UUS_In_Active_Call 2(4)

Si gn als to/from the le ft are
This pro cess is run ni ng in to/from the BSS; signal s to /from
th e remote MSC and i t h andles the righ t are to /from the
UUS3 flow contro l d estination /orig inating excha nge
Wa it_For_ u nl ess othe rwise m arked.
Acti vation_
R esponse

p = provi ded i.e. UUS3

se rvice i s provided
T1-UU S3 n p = no t rp ovided i .e .
Fac ili ty U US3 se rvice is n ot
exp iry
p rovi ded

Stop T1-UUS3 S3 := np

S3=p?
No

Yes

UUS3
active :=
True

X:=16
N:=X
Y:=8

Facil ity Facil ity

Start T2-U US3

Acti ve_ Cal l ID LE

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 2)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 55 ETSI EN 301 710 V7.0.2 (1999-12)

Process Remote_MSC_Handle_UUS_In_Active_Call 3(4)

Si gn als to/from the le ft are
This pro cess is run ni ng in to/from the BSS; signal s to /from
th e remote MSC and i t h andles the righ t are to /from the
UUS3 flow contro l d estination /orig inating excha nge
u nl ess othe rwise m arked.
Acti ve_Cal l

U ser To User U ser To User T2-UU S3

exp iry

UU S_MSC_ U US_MSC _
Check_ UUS3_ C hec k_UU S3_ N = 0?
UU I_ to _MS U UI_to_N W No

Yes

N := N + Y N := N + Y

Conges ti on False Ye s
contro l N > X?
sent

True No

Inform MS that
i t i s a llo we d to C ong estio n N := X
C ontro l
send U UIs

Conges ti on
contro l sent
:= Fa lse

Sta rt T2-U US3 Start T2 -UUS3

Acti ve_Cal l

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 3)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 56 ETSI EN 301 710 V7.0.2 (1999-12)

Process Remote_MSC_Handle_UUS_In_Active_Call 4(4)

This pro cess is run ni ng in

Si gn als to/from the le ft are
th e remote MSC and i t h andles
to/from the BSS; signal s to /from
UUS3 flow contro l the righ t are to /from the
d estination /orig inating excha nge
u nl ess othe rwise m arked.

Wai t_ Fo r_Activa tion_Re sponse

Active_ Ca ll

R elease R elease N OTIFY NOTIFY

From GSM 03.1 8 processe s
tran saction transactio n (EC T) (ECT)

Relea se Re lea se NOTIFY N OTIFY

To GSM 0 3.18 p roce sses
transa ction transaction (ECT) (EC T)

UU S1 implici t acti ve := Fa lse

UU S1 expl ici t activ e := Fa lse
UU S2 active := Fal se
UU S3 active := Fal se
Stop T2-UU S3

IDLE

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 4)

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 57 ETSI EN 301 710 V7.0.2 (1999-12)

10 Information stored in the HLR and in the VLR

10.1 Information stored in the HLR

The following logical states are applicable for each of the 3 Services of the User-to-user supplementary service (refer to
GSM 03.11 for an explanation of the notation):

Provisioning State Registration State Activation State HLR Induction State

(Not Provisioned, Not Applicable, Not Active, Not Induced)
(Provisioned, Not Applicable, Active and operative, Not Induced)

The HLR shall store:

- the logical state of each of the 3 services of the UUS supplementary service (which shall be one of the valid states
listed above) on a per subscriber basis.

10.2 Transfer of information from HLR to VLR

If the provisioning state for the UUS services is "Provisioned" then when the subscriber registers on a VLR the HLR
shall send that VLR information about the logical state of these UUS services.

If the logical state of the UUS services is changed while a subscriber is registered on a VLR then the HLR shall inform
the VLR of the new logical state of the UUS services.

10.3 Information stored in the VLR

For the supplementary service UUS the VLR shall store the service state information received from the HLR.

11 State transition model

Figure 11.1 shows the successful cases of transition between the applicable logical states of the service. The state
changes are caused by actions of the service provider.

Provision

(Not Provisioned, (Provisioned,

Not Registered, Not Registered,
Not Active, Active and Operative,
Not Induced) Not Induced)

Withdrawal

Figure 11.1: State transition model

12 Handover
Handover will have no impact on the control procedures and the operation of the service.

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 58 ETSI EN 301 710 V7.0.2 (1999-12)

Annex A (informative):
Status of Technical Specification GSM 03.87
Status
of
Technical Specification GSM 03.87: stage 2 of UUS
Date Version Comments
No Phase 1 version and no Phase 2 version

August 1998 0.3.0 Version 0.3.0 presented at the SMG3 WPB meeting in Stuttgart, 10-14 August
1998

September 1998 0.4.0 Version 0.4.0 delivered to SMG3 WPB delegates via e-mail.

November 1998 0.5.0 Version 0.5.0 presented at the SMG3 WPB meeting in Den Haag, 30 November – 4
December 1998

January 1999 0.6.0 Version 0.6.0 presented at SMG3 WPB ad hoc meeting in Sofia Antipolis, 11
January – 15 January 1999

January 1999 0.7.0 Version 0.7.0 was not presented at SMG3 WPB but a soft copy incorporating other
but call forwarding interaction comments was made available as Tdoc 3B99-036

January 1999 0.8.0 Version 0.8.0 presented at SMG3 WPB ad hoc meeting in Sofia Antipolis, 11
January – 15 January 1999. This version incorporated also comments for call
forwarding interaction.

January 1999 0.9.0 Version 0.9.0 presented at SMG3 WPB ad hoc meeting in Sofia Antipolis, 25
January – 27 January 1999
February 1999 2.0.0 specification to SMG#28 for information and approval

February 1999 7.0.0 TS approved by SMG#28 for Release 98

December 1999 7.0.2 Update to Version 7.0.2 for Publication

Text and figures: WinWord 6.0

Stylesheet: etsiw_70.dot

ETSI
(GSM 03.87 version 7.0.2 Release 1998) 59 ETSI EN 301 710 V7.0.2 (1999-12)

History
Document history
V7.0.1 July 1999 One-step Approval Procedure OAP 9952: 1999-07-28 to 1999-11-26

V7.0.2 December 1999 Publication

ETSI