3G TS 23.087 V3.0.

1 (1999-05)
Technical Specification

3rd Generation Partnership Project; Technical Specification Group Core Network; User-to-User Signalling (UUS) Supplementary Service - Stage 2 (Release 1999)

The present document has been developed within the 3rd Generation Partnership Project (3GPP TM) and may be further elaborated for the purposes of 3GPP. The present document has not been subject to any approval process by the 3GPP Organisational Partners and shall not be implemented. This Specification is provided for future development work within 3GPP only. The Organisational Partners accept no liability for any use of this Specification. Specifications and reports for implementation of the 3GPP TM system should be obtained via the 3GPP Organisational Partners' Publications Offices.

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

Keywords
3GPP, CN

3GPP Postal address

3GPP support office address

650 Route des Lucioles - Sophia Antipolis Valbonne - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16

Internet
http://www.3gpp.org

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.
2000, 3GPP Organizational Partners (ARIB, CWTS, ETSI, T1, TTA,TTC). All rights reserved.

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

Contents
Foreword ................................................................................................................................................5 1 2 3
3.1 3.2

Scope ............................................................................................................................................6 References ....................................................................................................................................6 Definitions and abbreviations ...........................................................................................................6

Definitions............................................................................................................................................................................. 6 Abbreviations....................................................................................................................................................................... 7

4
4.1 4.1.1 4.1.2 4.1.3

General..........................................................................................................................................7
Activation of UUS components ........................................................................................................................................ 7 Implicit request............................................................................................................................................................... 7 Explicit request............................................................................................................................................................... 8 UUS required option ..................................................................................................................................................... 8

Handling of User-to-user signalling ..................................................................................................8

Timers .................................................................................................................................................................................... 8 Information flows of UUS services ................................................................................................................................... 9 Service 1 (UUS1)............................................................................................................................................................ 9 Flow control............................................................................................................................................................. 9 Information flows .................................................................................................................................................. 10 Implicit activation............................................................................................................................................ 11 Explicit activation ............................................................................................................................................ 12 Service 2 (UUS2).......................................................................................................................................................... 13 Flow control........................................................................................................................................................... 13 Information flows .................................................................................................................................................. 13 Service 3 (UUS3).......................................................................................................................................................... 15 Flow control........................................................................................................................................................... 15 Information flows .................................................................................................................................................. 16 Messages and their contents ........................................................................................................................................... 19 Information elements used in the messages............................................................................................................ 19 Messages between MS and MSC............................................................................................................................. 19 Messages between MSC and VLR (B interface)..................................................................................................... 20 Messages between MSC MSC (E interface)........................................................................................................ 21 Call forwarding unconditional (CFU).............................................................................................................................. 21 Call forwarding on mobile subscriber busy (CFB)........................................................................................................ 21 Call forwarding on no reply (CFNRy)............................................................................................................................. 21 Call forwarding on mobile subscriber not reachable (CFNRc).................................................................................... 22 Call waiting (CW)............................................................................................................................................................... 22 Call hold (HOLD)................................................................................................................................................................ 22 Completion of calls to busy subscribers (CCBS).......................................................................................................... 22 Explicit call transfer (ECT)................................................................................................................................................. 22 Multi party service (MPTY) ............................................................................................................................................. 22 Advice of charge (AoC).................................................................................................................................................... 22 Barring of outgoing calls (BAOC)................................................................................................................................... 23 Barring of outgoing international calls (BOIC).............................................................................................................. 23 Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC)........... 23 Barring of incoming calls (BAIC)..................................................................................................................................... 23 Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam) ....................................... 23 Call deflection (CD)............................................................................................................................................................ 23

5.1 5.2 5.2.1 5.2.1.1 5.2.1.2 5.2.1.2.1 5.2.1.2.2 5.2.2 5.2.2.1 5.2.2.2 5.2.3 5.2.3.1 5.2.3.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4

6
6.1 6.2 6.3 6.4 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16

Interaction with other supplementary services ................................................................................21

7
7.1 7.2

Interaction with other network features..........................................................................................23

Customised Applications for Mobile network Enhanced Logic (CAMEL) .............................................................. 23 Support for Optimal Routeing(SOR) ............................................................................................................................... 23

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

8
8.1 8.2

Interworking with other networks ..................................................................................................24

Interworking with GSM PLMN/ISDN network supporting only a maximum User-user information element length of 35 octets ............................................................................................................................................................. 24 Interworking with non-ISDN network............................................................................................................................. 24

9
9.1 9.1.1 9.1.2 9.2 9.2.1 9.2.2 9.3 9.4 9.4.1 9.4.2 9.4.3

Network entity functions ...............................................................................................................24

Originating network processes ........................................................................................................................................ 24 Procedures in MSC...................................................................................................................................................... 24 Procedures in VLR....................................................................................................................................................... 28 Terminating network processes....................................................................................................................................... 29 Procedures in GMSC................................................................................................................................................... 29 Procedures in MSC...................................................................................................................................................... 31 Procedures common in serving and remote networks.................................................................................................. 37 Processes used during Active Call ................................................................................................................................. 47 Process and procedures in serving MSC................................................................................................................. 47 Process and procedures in serving VLR.................................................................................................................. 53 Process and procedures in remote MSC.................................................................................................................. 54

10
10.1 10.2 10.3

Information stored in the HLR and in the VLR...............................................................................59

Information stored in the HLR ......................................................................................................................................... 59 Transfer of information from HLR to VLR...................................................................................................................... 59 Information stored in the VLR.......................................................................................................................................... 59

11 12

State transition model....................................................................................................................59 Handover.....................................................................................................................................59 Change history...................................................................................... 60

Annex A (informative):

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

Foreword
This Technical Specification (TS) has been produced by the 3rd Generation Partnership Project (3GPP). The present document gives the stage 2 description of the User-to-User signalling supplementary services within the 3GPP system. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document.

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

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 Service 2 Service 3 (UUS1) (UUS2) (UUS3)

2
[1] [2] [3] [4] [5]

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. 3G TS 21.905: "3G Vocabulary". 3G TS 22.087: "User-to-user signalling (UUS); Stage 1". 3G TS 23.018: "Basic Call Handling Technical Realization". 3G TS 23.078: "CAMEL Stage 2". 3G TS 23.079: "Support for Optimal Routeing (SOR) Technical Realization".

3
3.1

Definitions and abbreviations

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: 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 Served subscriber: 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: network of the served subscriber User-to-User Information (UUI): information transferred by using the UUS supplementary service

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

UUS Service: 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
ACM ANM CON CPG IAM MS REL SIFOC SRI UUI UUS UUS1 UUS2 UUS3

Abbreviations
Address Complete Message ANswer Message CONnect Call ProGress Initial Address Message Mobile Station RELease Send Info For Outgoing Call Send Routing Info User-to-User Information User-to-User Signalling User-to-User Signalling Service 1 User-to-User Signalling Service 2 User-to-User Signalling Service 3

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

Further GSM related abbreviations are listed in GSM 01.04.

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 the present document.

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.

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.

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

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
5.1

Handling of User-to-user signalling

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.

3GPP

Release 1999

3G TS 23.087 V3.0.1 (1999-05)

Table 5.1: UUS Timers

Timer T1-UUS3 Name Remote network control Value 10s Run at MSC of the remote subscriber Started UUS3 service request sent to the remote subscriber Stopped Answer to UUS3 service request received from the remote subscriber Expiry Rejection of UUS3 service is sent toward the requesting network When UUS3 service is Flow control deactivated parameter is incremented. Timer is restarted. Note 1. Acceptance to UUS3 Consider UUS3 service received from service as not requesting network activated Acceptance to UUS3 Rejection of service received from UUS3 service is remote network sent toward the served subscriber

T2-UUS3

UUS3 flow control

10s

T3-UUS3

T4-UUS3

Served subscriber control Serving network control

10s

MSC of the served subscriber and MSC of the remote subscriber MS of the served subscriber

The MSC receives service acceptance

10s

UUS3 service request sent to the requesting network MSC of the served UUS3 service subscriber request sent to the remote network

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
5.2.1
5.2.1.1

Information flows of UUS services

Service 1 (UUS1)
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.

3GPP

Release 1999

10

3G TS 23.087 V3.0.1 (1999-05)

5.2.1.2

Information flows

Grafikname: Erstellt in: Erstellt am:

3GPP

Release 1999

11

3G TS 23.087 V3.0.1 (1999-05)

5.2.1.2.1
MSa Set-up UUI*

Implicit activation
MSCa VLRa GMSCb HLRb MSCb MSb

SIFOC Complete call IAM UUI* SRI SRI ack IAM UUI*

Set-up UUI* Alert UUI

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

Connect UUI CON CON Connect UUI UUI UUI

Disconnect UUI

REL UUI REL UUI Disconnect UUI

Note:

UUI* UUI

User-to-user information required for requesting the UUS service 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)

3GPP

Release 1999

12

3G TS 23.087 V3.0.1 (1999-05)

5.2.1.2.2
MSa Set-up S1=r,nr; UUI

Explicit activation
MSCa VLRa GMSCb HLRb MSCb MSb

SIFOC Complete call IAM S1=r,nr; UUI SRI SRI ack IAM S1=r,nr; UUI ACM/ANM/CPG

Set-up S1=r,nr; UUI Alert S1=p; UUI

Alert S1=p; UUI

ACM/ANM/CPG S1=p; UUI

S1=p; UUI

Connect UUI CON CON Connect UUI UUI UUI

Disconnect UUI

REL UUI REL UUI Disconnect UUI

Note:

S1 UUI r,nr p

UUS Service 1 User-to-user information can be sent optionally requested, not required provided

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

3GPP

Release 1999

13

3G TS 23.087 V3.0.1 (1999-05)

5.2.2
5.2.2.1

Service 2 (UUS2)
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

Grafikname: Erstellt in: Erstellt am:

3GPP

Release 1999

14

3G TS 23.087 V3.0.1 (1999-05)

MSa Set-up S2=r,nr

MSCa

VLRa

GMSCb

HLRb

MSCb

MSb

SIFOC Complete call IAM S2=r,nr

SRI SRI ack IAM S2=r,nr ACM/ANM/CPG S2=p

Set-up S2=r,nr Alert

Alert S2=p

ACM/ANM/CPG S2=p

S2=p

User info UUI

User info UUI

User info UUI

User info UUI

User info User info User info UUI UUI UUI

User info UUI

Connect CON CON

Connect

Note:

S2 UUI r,nr p

UUS Service 2 User-to-user information requested, not required provided

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

3GPP

Release 1999

15

3G TS 23.087 V3.0.1 (1999-05)

5.2.3
5.2.3.1

Service 3 (UUS3)
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 users 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.

3GPP

Release 1999

16

3G TS 23.087 V3.0.1 (1999-05)

5.2.3.2

Information flows

Grafikname: Erstellt in: Erstellt am:

3GPP

Release 1999

17

3G TS 23.087 V3.0.1 (1999-05)

MSa Set-up S3=r,nr

MSCa

VLRa

GMSCb

HLRb

MSCb

MSb

SIFOC Complete call IAM S3=r,nr

SRI SRI ack IAM S3=r,nr

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

Alert

ACM/ANM/CPG

Connect CON S3=p CON S3=p S3=p

Connect S3=p User info UUI

User info UUI

User info UUI

User info UUI User info UUI

User info User info User info UUI UUI UUI

Disconnect REL REL

Disconnect

Note:

S3 UUI r,nr p

UUS Service 3 User-to-user information requested, not required provided

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

3GPP

Release 1999

18

3G TS 23.087 V3.0.1 (1999-05)

MSa

MSCa

VLRa GMSCb Active call A-B

HLRb

MSCb

MSb

Facility S3=r

Uus act Uus act ack Facility S3=r

Facility S3=r

Facility S3=r

Facility Facility S3=p S3=p

Facility S3=p User info UUI

Facility S3=p

User info UUI

User info UUI

User info UUI User info UUI

User info User info User info UUI UUI UUI

Disconnect REL REL

Disconnect

Note:

S3 UUI r p

UUS Service 3 User-to-user information requested provided

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

3GPP

Release 1999

19

3G TS 23.087 V3.0.1 (1999-05)

5.3

Messages and their contents

This subclause contains the detailed description of the information flows used by UUS. 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 Element Element name UUS options UUS1 Information Information element description element Required 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 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 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 C If UUS1 services is requested and provisioned the information element is present, otherwise it shall be C absent. If UUS2 services is requested and provisioned the 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.

UUS2

UUS3

UUS provision

UUS1 UUS2 UUS3

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.

3GPP

Release 1999

20

3G TS 23.087 V3.0.1 (1999-05)

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 sender MSC Information element name Information Information element description element Required Refer to GSM 03.18. In addition: 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 Refer to GSM 03.18 In addition: The information element is present, if required UUS service was requested by MS A and service is not provided, otherwise it shall be absent. Refer to GSM 03.18 In addition: The information element is present if MS A requested UUS service(s); otherwise it shall be a bsent. 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. The information element is present if UUS3 service is provisioned; otherwise it shall be absent

Send Info For Outgoing Call

UUS options

Send Info For VLR Outgoing Call negative response

UUS reject

Complete Call

VLR

UUS provision

Send Info For UUS3 MSC

Send Info For UUS3 VLR Ack

UUS provision

3GPP

Release 1999

21

3G TS 23.087 V3.0.1 (1999-05)

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 conjunction of SOR, refer to GSM 03.79. Table 5.3.4.1: Messages between MSC MSC
Message Message sender MSCB Information element name Information Information element description element Required Refer to GSM 03.79. In addition: The information element is present if UUS1 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent. The information element is present if UUS2 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent The information element is present if UUS3 Service was requested in the original call and remote MSC supports UUS service; otherwise it shall be absent. 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. The information element is present if the remote subscriber has accepted UUS1 service request and call forwarding or call deflection has been activated after that; otherwise it shall be absent.

Resume Call Handling

UUS1 Service request

C UUS2 Service request C UUS3 Service request

UUS1 UUI

UUS CF interaction

6
6.1
No impact.

Interaction with other supplementary services

Call forwarding unconditional (CFU)

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

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,

3GPP

Release 1999

22

3G TS 23.087 V3.0.1 (1999-05)

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
No impact.

Call forwarding on mobile subscriber not reachable (CFNRc)

6.5
No impact.

Call waiting (CW)

6.6
No impact.

Call hold (HOLD)

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
No impact.

Multi party service (MPTY)

6.10
No impact.

Advice of charge (AoC)

3GPP

Release 1999

23

3G TS 23.087 V3.0.1 (1999-05)

6.11
No impact.

Barring of outgoing calls (BAOC)

6.12
No impact.

Barring of outgoing international calls (BOIC)

6.13
No impact.

Barring of outgoing international calls except those directed to the home PLMN country (BOIC-exHC)

6.14
No impact.

Barring of incoming calls (BAIC)

6.15
No impact.

Barring of incoming calls when roaming outside the home PLMN country (BIC-Roam)

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
7.1
No impact.

Interaction with other network features

Customised Applications for Mobile network Enhanced Logic (CAMEL)

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).

3GPP

Release 1999

24

3G TS 23.087 V3.0.1 (1999-05)

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
8.1

Interworking with other networks

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.

9
9.1
9.1.1

Network entity functions

Originating network processes
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.

3GPP

Release 1999

25

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_OCH_Check_Setup
This procedure is running in the MSC and sets the UUS specific parameters to SIFOC message

1(1)

No

UUS1 requested Yes No

Either implicit or explicit request

Requested as required Yes

Set UUS1 "required" to SIFOC

Set UUS1 "not required" to SIFOC

No

UUS2 requested Yes No

Requested as required Yes

Set UUS2 "required" to SIFOC

Set UUS2 "not required" to SIFOC

No

UUS3 requested Yes No

Requested as required Yes

Set UUS3 "required" to SIFOC

Set UUS3 "not required" to SIFOC

Figure 9.1.1.1: Procedure UUS_OCH_Check_Setup

3GPP

Release 1999

26

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_OCH_Set_Info_In_IAM
This procedure is running in the MSC and it sets UUS specific parameters to the IAM message

1(1)

S1 = UUS Service 1 S2 = UUS Service 2 S3 = UUS Service 3 r,nr = requested, not required r,r = requested, required No UUS1 requested Yes No UUS1 provisioned Yes No Implicit request

Yes

Requested as required Yes S1:=r,r

No

S1:=r,nr

UUS1 implicit active:=True

Copy S1 to IAM

No UUS1 data present Yes Copy UUS data to IAM Copy UUS data to IAM 1

No UUS2 requested Yes No UUS2 provisioned Yes Requested as required Yes S2:=r,r S2:=r,nr UUS3 requested Yes UUS3 provisioned Yes Requested as required Yes S3:=r,r S3:=r,nr

No

No

Copy S2 to IAM No 1

Copy S3 to IAM

Figure 9.1.1.2: Procedure UUS_OCH_Set_Info_In_IAM

3GPP

Release 1999

27

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_OCH_Set_Alert_And_Connect_Param
This procedure is running in the MSC and it sets the UUS parameters to the call control messages directed back to the initiating MS

1(1)

Yes UUS1 requested No UUS_MSC_ Check_UUS1

Pass UUS2 requested No UUS_MSC_ Check_UUS2 Yes

Fail UUS2 requested No UUS_MSC_ Check_UUS2 Yes

Pass Yes UUS3 requested No UUS_MSC_ Check_UUS3

Fail Yes UUS3 requested No UUS_MSC_ Check_UUS3

Pass UUS_MSC_ Check_UUS1_ UUI

Fail UUS_MSC_ Check_UUS1_ UUI

Result := Pass

Result := Fail

Figure 9.1.1.3: Procedure UUS_OCH_Set_Alert_And_Connect_Param

3GPP

Release 1999

28

3G TS 23.087 V3.0.1 (1999-05)

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
This procedure is running in the VLR and it does the UUS specific provisioning checks No UUS1 requested Yes No

1(1)

UUS1 provisioned Yes Set UUS1 "provisioned" to Complete Call

UUS1 required Yes No

No

UUS2 requested Yes No

UUS2 provisioned Yes Set UUS2 "provisioned" to Complete Call

UUS2 required Yes No

No

UUS3 requested Yes No

UUS3 provisioned Yes Set UUS3 "provisioned" to Complete Call

UUS3 required No

Yes Set negative response:= UUS Reject

Result := Pass Result := Fail

Figure 9.1.2.1: Procedure UUS_OCH_Check_Provision

3GPP

Release 1999

29

3G TS 23.087 V3.0.1 (1999-05)

9.2
9.2.1

Terminating network processes

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.

3GPP

Release 1999

30

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_GMSC_Check_Forwarding
This procedure is running in the GMSC and it check whether UUS specific data shall be forwarded in the optimal routeing case

1(1)

No UUS data received in RCH message? Yes No UUS CF interaction set in RCH message? Yes

UUS CF interaction := True

Add received UUS information to IAM

Figure 9.2.1.1: Procedure UUS_GMSC_Check_Forwarding

3GPP

Release 1999

31

3G TS 23.087 V3.0.1 (1999-05)

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.

3GPP

Release 1999

32

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_ICH_Check_Support
This procedure is running in the MSC and it checks UUS related parameters S1 = UUS Service 1 p = service is provided by the remote MS

1(1)

From the originating GMSC

UUS1 requested Yes No UUS_MSC_ Check_UUS1

Pass From the originating GMSC UUS2 requested Yes No UUS_MSC_ Check_UUS2 From the originating GMSC

Fail UUS2 requested Yes No UUS_MSC_ Check_UUS2

Pass From the originating GMSC UUS3 requested Yes No From the originating GMSC

Fail UUS3 requested Yes No

UUS_MSC_ Check_UUS3

UUS_MSC_ Check_UUS3

Pass Set UUS options to first backward message NOTE: UUS options is never set for implicit UUS1 service

Fail Set UUS options to first backward message

UUS_MSC_ Check_UUS1_ UUI

UUS_MSC_ Check_UUS1_ UUI

Result:= Pass

Result:= Fail

Figure 9.2.2.1: Procedure UUS_ICH_Check_Support

3GPP

Release 1999

33

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_ICH_Check_Forwarding
This procedure is running in the MSC and it checks whether UUS can be forwarded and if call forwarding is allowed. NOTE: UUS CF interaction flag is set if UUS1 service request response was sent to the serving nw and CF happens after that

1(1)

No UUS1 present

Yes No Explicit request Yes No

requested as required Yes

UUS1 explicit active? False

True

Clear stored UUS1 service request (and UUI)

UUS CF interaction := True

UUS2 present No Yes

requested as required No Yes Clear stored UUS2 service request

Result:= Fail

Result:= Fail

Result:= Pass

Result:= Pass

Figure 9.2.2.2: Procedure UUS_ICH_Check_Forwarding

3GPP

Release 1999

34

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_ICH_Handle_LCF
This procedure is running in the MSC and it checks whether UUS will be forwarde in the optimal routeing case

1(1)

No UUS data stored? Yes

Add UUS information to RCH message

UUS CF interaction = True? Yes

No

Add UUS CF interaction flag to RCH message

Figure 9.2.2.3: Procedure UUS_ICH_Handle_LCF

3GPP

Release 1999

35

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_ICH_Set_Info_In_IAM
This procedure is running in the MSC and it checks whether UUS will be added to the IAM message in the call forwarding case

1(1)

UUS information received, stored and not cleared Yes

No

Add UUS information to IAM

Figure 9.2.2.4: Procedure UUS_ICH_Set_Info_In_IAM

3GPP

Release 1999

36

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_ICH_UUS1_Implicit_Active
This procedure is running in the MSC and it sets the implicit UUS1 active when UUI is send

1(1)

UUS1 implicit request? Yes

No

UUS1 implicit active := True

Figure 9.2.2.5: Procedure UUS_ICH_UUS1_Implicit_Active

3GPP

Release 1999

37

3G TS 23.087 V3.0.1 (1999-05)

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.

3GPP

Release 1999

38

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS1_UUI
This procedure is running in the MSC and it checks whether UUI can be passed over Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.

1(1)

No

UUS1 implicit active = True? Yes

UUS1 explicit active = True? No

Yes

No UUI received? Yes

Pass UUI

Figure 9.3.1: Procedure UUS_MSC_Check_UUS1_UUI

3GPP

Release 1999

39

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS2_UUI_to_MS
This procedure is running in the MSC and it checks whether UUI can be passed over Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.

1(1)

UUS2 active= True? Yes

No

User To User

Figure 9.3.2: Procedure UUS_MSC_Check_UUS2_UUI_to_MS

3GPP

Release 1999

40

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS2_UUI_to_NW
This procedure is running in the MSC and it checks whether UUI can be passed over. In addition it handles UUS2 flow control Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.

1(1)

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

3GPP

Release 1999

41

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS3_UUI_to_MS
This procedure is running in the MSC and it checks whether UUI can be passed over. Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.

1(1)

No UUS3 active= True? Yes

User To User

Figure 9.3.4: Procedure UUS_MSC_Check_UUS3_UUI_to_MS

3GPP

Release 1999

42

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS3_UUI_to_NW
This procedure is running in the MSC and it checks whether UUI can be passed over. In addition it handles UUS3 flow control Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination exchange unless otherwise marked.

1(1)

No UUS3 active= True? Yes

N>0? No Yes True N:=N-1 Congestion control sent? False

User To User

Congestion Control

Inform the MS that it is not allowed to send any UUIs

Congestion control sent := True

Figure 9.3.5: Procedure UUS_MSC_Check_UUS3_UUI_to_NW

3GPP

Release 1999

43

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Clear_UUS
This procedure is running in the MSC and it handles CFNRy and UUS interaction when the MSC is receiving call control messages from forwarded-to NW. S1 = UUS1 Service response

1(1)

No UUS CF interaction = True Yes

Clear received (if any) S1

Yes Received msg was Answer or Connect? No

Clear received (if any) UUI

Figure 9.3.6: Procedure UUS_MSC_Clear_UUS

3GPP

Release 1999

44

3G TS 23.087 V3.0.1 (1999-05)

Macrodefinition UUS_MSC_Check_UUS1
np = service is not provided by network or remote end

1(1)

True

UUS1 result sent? False

Alert received? No Yes

explicit request Yes No S1 received No Yes

Connect received? Yes No explicit request No Yes

UUS1 result sent := True

UUS1 result sent := True

No S1 received Yes

Do not send S1

Pass received S1

Do not send S1

Pass received S1

S1:=np

No S1=np?

No S1=np?

Yes UUS1 explicit active:=True UUS1 Required? No Yes No UUS1 explicit active:=True

Yes

UUS1 Required? Yes

Pass

Fail

Pass

Fail

Figure 9.3.7: Macrodefinition UUS_MSC_Check_UUS1

3GPP

Release 1999

45

3G TS 23.087 V3.0.1 (1999-05)

Macrodefinition UUS_MSC_Check_UUS2

1(1)

np = service is not provided by network or remote end

Alert received? Yes

No

No S2 received Yes

Pass received S2

S2:=np

No S2 = np?

Yes UUS2 active :=True UUS2 Required? Yes No

Fail

Pass

Figure 9.3.8: Macrodefinition UUS_MSC_Check_UUS2

3GPP

Release 1999

46

3G TS 23.087 V3.0.1 (1999-05)

Macrodefinition UUS_MSC_Check_UUS3

1(1)

np = service is not provided by network or remote end

Connect received? Yes

No

No S3 received Yes S3 received No

Yes

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

3GPP

Release 1999

47

3G TS 23.087 V3.0.1 (1999-05)

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 originators 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.

3GPP

Release 1999

48

3G TS 23.087 V3.0.1 (1999-05)

Process Serving_MSC_Handle_UUS_In_Active_Call
This process is running in the serving MSC. It handles UUS3 during the active call

1(4)

Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

Congestion control sent := False

p = provided i.e. UUS3 service is provided np = not provided i.e. UUS3 service is not provided

IDLE

Facility

Connect

From GSM 03.18 processes

UUS_MSC_ Check_UUS3_ Activation

Connect

Result? Aborted Pass Fail No

UUS3 active= True? Yes

Start T4-UUS3

S3:=np

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

UUS3 flow control parameters

Facility

Facility

Start T2-UUS3

Wait_For_ Activation_ Response

IDLE

Active_Call

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 1)

3GPP

Release 1999

49

3G TS 23.087 V3.0.1 (1999-05)

Process Serving_MSC_Handle_UUS_In_Active_Call
This process is running in the serving MSC. It handles UUS3 during the active call Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

2(4)

Wait_For_ Activation_ Response

p = provided i.e. UUS3 service is provided np = not provided i.e. UUS3 service is not provided

Facility

T4-UUS3 expiry

Stop T4-UUS3

S3:=np

S3=p? No Yes

UUS3 active :=True

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

UUS3 flow control parameters

Facility

Facility

Start T2-UUS3

Active_Call

IDLE

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 2)

3GPP

Release 1999

50

3G TS 23.087 V3.0.1 (1999-05)

Process Serving_MSC_Handle_UUS_In_Active_Call
This process is running in the serving MSC. It handles UUS3 during the active call Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

3(4)

Release transaction

From GSM 03.18 processes

Release transaction

NOTIFY (ECT)

NOTIFY (ECT)

Release transaction

To GSM 03.18 processes

Release transaction

NOTIFY (ECT)

NOTIFY (ECT)

UUS1 implicit active := False UUS1 explicit active := False UUS2 active := False UUS3 active := False Stop T2-UUS3

IDLE

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 3)

3GPP

Release 1999

51

3G TS 23.087 V3.0.1 (1999-05)

Process Serving_MSC_Handle_UUS_In_Active_Call
This process is running in the serving MSC. It handles UUS3 during the active call Active_Call

4(4)

Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

User To User

User To User

T2-UUS3 expiry

UUS_MSC_ Check_UUS3_ UUI_to_MS

UUS_MSC_ Check_UUS3_ UUI_to_NW

N = 0? No Yes

N:=N+Y

N:=N+Y

Congestion control sent? True

False N > X? Yes No

Inform MS that it is allowed to send UUIs

Congestion Control

N := X

Congestion control sent := False

Start T2-UUS3

Start T2-UUS3

Active_Call

Figure 9.4.1.1: Process Serving_MSC_Handle_UUS_In_Active_Call (sheet 4)

3GPP

Release 1999

52

3G TS 23.087 V3.0.1 (1999-05)

Procedure UUS_MSC_Check_UUS3_Activation
This procedure is running in the MSC and it checks UUS3 activation during active call

1(1)

Signals to/from the right are to/from the VLR unless otherwise marked.

Send_Info_ For_UUS3

Wait_For_ Answer

From BSS

Release transaction

From GSM 03.18

Release transaction

Send_Info_ For_UUS3_ Ack

To GSM 03.18

Release transaction

To BSS

Release transaction

UUS3 provisioned? No Yes

Wait_For_Ack

Send_Info_ For_UUS3_ Ack

Result:= Aborted

Result:= Pass

Result:= Fail

Figure 9.4.1.2: Procedure UUS_MSC_Check_UUS3_Activation

3GPP

Release 1999

53

3G TS 23.087 V3.0.1 (1999-05)

9.4.2

Process and procedures in serving VLR

Figure 9.4.2.1 Process Serving_VLR_Handle_UUS_In_Active_Call 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
This process is running in the VLR and it checks the UUS3 provisioning status

1(1)

Signals to/from left are to/from MSC unless otherwise marked

IDLE

Send_Info_ For_UUS3

UUS3 provisioned? Yes

Set UUS provisioned

No Send_Info_ For_UUS3_Ack

IDLE

Figure 9.4.2.1: Process Serving_VLR_Handle_UUS_In_Active_Call

3GPP

Release 1999

54

3G TS 23.087 V3.0.1 (1999-05)

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 UUIs 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.

3GPP

Release 1999

55

3G TS 23.087 V3.0.1 (1999-05)

Process Remote_MSC_Handle_UUS_In_Active_Call
This process is running in the remote MSC and it handles UUS3 flow control

1(4)

Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

Congestion control sent := False

IDLE

Facility

Connect

Facility

Connect

To GSM 03.18 processes

UUS3 active= True? Yes

No

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

Start T1_UUS3

Start T2_UUS3

Wait_For_ Activation_ Response

Active_Call

IDLE

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 1)

3GPP

Release 1999

56

3G TS 23.087 V3.0.1 (1999-05)

Process Remote_MSC_Handle_UUS_In_Active_Call
This process is running in the remote MSC and it handles UUS3 flow control Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

2(4)

Wait_For_ Activation_ Response

Facility

T1-UUS3 expiry

p = provided i.e. UUS3 service is provided np = not rpovided i.e. UUS3 service is not provided

Stop T1-UUS3

S3 := np

S3=p? No Yes

UUS3 active:= True

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

Facility

Facility

Start T2-UUS3

Active_Call

IDLE

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 2)

3GPP

Release 1999

57

3G TS 23.087 V3.0.1 (1999-05)

Process Remote_MSC_Handle_UUS_In_Active_Call
This process is running in the remote MSC and it handles UUS3 flow control Active_Call Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

3(4)

User To User

User To User

T2-UUS3 expiry

UUS_MSC_ Check_UUS3_ UUI_to_MS

UUS_MSC_ Check_UUS3_ UUI_to_NW

N = 0? No Yes

N := N + Y

N := N + Y

Congestion control sent True

False N > X?

Yes

No

Inform MS that it is allowed to send UUIs

Congestion Control

N := X

Congestion control sent := False

Start T2-UUS3

Start T2-UUS3

Active_Call

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 3)

3GPP

Release 1999

58

3G TS 23.087 V3.0.1 (1999-05)

Process Remote_MSC_Handle_UUS_In_Active_Call
This process is running in the remote MSC and it handles UUS3 flow control

4(4)

Signals to/from the left are to/from the BSS; signals to/from the right are to/from the destination/originating exchange unless otherwise marked.

Wait_For_Activation_Response Active_Call

Release transaction

From GSM 03.18 processes

Release transaction

NOTIFY (ECT)

NOTIFY (ECT)

Release transaction

To GSM 03.18 processes

Release transaction

NOTIFY (ECT)

NOTIFY (ECT)

UUS1 implicit active := False UUS1 explicit active := False UUS2 active := False UUS3 active := False Stop T2-UUS3

IDLE

Figure 9.4.3.1: Process Remote_MSC_Handle_UUS_In_Active_Call (sheet 4)

3GPP

Release 1999

59

3G TS 23.087 V3.0.1 (1999-05)

10
10.1

Information stored in the HLR and in the VLR

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 (Not Provisioned, (Provisioned, Registration State Not Applicable, Not Applicable, Activation State Not Active, Active and operative, HLR Induction State Not Induced) 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, Not Registered, Not Active, Not Induced)

(Provisioned, Not Registered, Active and Operative, 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.

3GPP

Release 1999

60

3G TS 23.087 V3.0.1 (1999-05)

Annex A (informative): Change history

TSG CN# Spec Version Apr 1999 GSM 03.87 7.0.0 CN#03 23.087 3.0.0 CR Change history <Phase> New Version 3.0.0 3.0.1 Subject/Comment Transferred to 3GPP CN1 Approved at CN#03 References updated from 2G to 3G

R99

3GPP