You are on page 1of 44

ETSI TS 123 172 V5.6.

0 (2005-06)
Technical Specification

Universal Mobile Telecommunications System (UMTS); Technical realization of Circuit Switched (CS) multimedia service; UDI/RDI fallback and service modification; Stage 2 (3GPP TS 23.172 version 5.6.0 Release 5)

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

Reference
RTS/TSGC-0323172v560

Keywords
UMTS

ETSI
650 Route des Lucioles F-06921 Sophia Antipolis Cedex - 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88

Important notice
Individual copies of the present document can be downloaded from: http://www.etsi.org The present document 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. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at http://portal.etsi.org/tb/status/status.asp If you find errors in the present document, please send your comment to one of the following services: http://portal.etsi.org/chaircor/ETSI_support.asp

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 2005. All rights reserved. DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members. TM TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. TM 3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
TM TM TM

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

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 ETSI 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://webapp.etsi.org/IPR/home.asp). 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 ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document.

Foreword
This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http://webapp.etsi.org/key/queryform.asp .

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

Contents
Intellectual Property Rights ................................................................................................................................2 Foreword.............................................................................................................................................................2 Foreword.............................................................................................................................................................4 1 2 3
3.1 3.2

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


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

Service change and fallback for UDI/RDI multimedia ............................................................................6

4.1 General Requirements ........................................................................................................................................6 4.2 Access Call Control Signalling ..........................................................................................................................7 4.2.1 Mobile originating side - initiation of call setup ...........................................................................................7 4.2.1.1 Subscription checking .............................................................................................................................8 4.2.1.1.1 Send Info For Outgoing Call .............................................................................................................8 4.2.1.1.2 Complete Call....................................................................................................................................8 4.2.2 Mobile terminating side ................................................................................................................................9 4.2.2.1 Subscription checking ...........................................................................................................................10 4.2.2.1.1 Send Info For Incoming Call ...........................................................................................................10 4.2.2.1.2 Complete Call..................................................................................................................................10 4.2.3 Mobile originating side - completion of call setup .....................................................................................10 4.2.4 Service change in the active state ...............................................................................................................12 4.3 Core Network procedures.................................................................................................................................13 4.3.1 Multimedia codec .......................................................................................................................................13 4.3.2 Originating side - initiation of call setup ....................................................................................................13 4.3.3 Terminating side .........................................................................................................................................14 4.3.3.1 HLR Interrogation.................................................................................................................................14 4.3.3.1.1 Send Routing Info............................................................................................................................14 4.3.3.1.2 Send Routing Info Ack ....................................................................................................................14 4.3.3.1.3 Handling of mobile terminating calls in the HLR ...........................................................................15 4.3.3.1.4 Handling of mobile terminating calls in the GMSC ........................................................................23 4.3.3.2 Terminating MSC Handling..................................................................................................................26 4.3.4 Originating side - completion of call setup .................................................................................................28 4.3.5 Service change during the active state ........................................................................................................30 4.3.5.1 Mid-Call Codec Modification Procedure For Service Change .............................................................30 4.3.5.2 Unsuccessful Service Change ...............................................................................................................36 4.3.6 Interaction with supplementary services.....................................................................................................39 4.3.6.1 Call forwarding and Call deflection ......................................................................................................39 4.3.6.2 Closed User Group (CUG)....................................................................................................................39 4.3.6.3 Call barring ...........................................................................................................................................39 4.3.7 Interactions with CAMEL ..........................................................................................................................39 4.3.7.1 Interaction at call setup .........................................................................................................................39 4.3.7.2 Interaction at call answer ......................................................................................................................40 4.3.7.3 Interaction with Call Party Handling.....................................................................................................40 4.3.7.4 Interaction with CAMEL in-band information and user interaction .....................................................40 4.3.8 Interworking with external networks ..........................................................................................................40 4.3.9 User interaction and in-band information ...................................................................................................40

Lawful Interception ................................................................................................................................41 Change history ...............................................................................................42

Annex A (informative):

History ..............................................................................................................................................................43

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

Foreword
This Technical Specification has been produced by the 3rd Generation Partnership Project (3GPP). 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.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

Scope

The present document describes the Service Change and UDI Fallback (SCUDIF) feature. This service is available to UDI/RDI multimedia calls and allows users to achieve successful call establishment when end to end circuit-switched (CS) multimedia is not possible (fallback to speech) or when signalling of the feature is not possible in the network (fallback to preferred service or speech). Furthermore, it allows the users to swap between a multimedia service and basic speech during an established call. NOTE: In the present document, the term "multimedia" refers to UDI/RDI multimedia unless specifically stated.

References
References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. [1] [2] [3] [4] [5] [6] 3GPP TR 21.905: "Vocabulary for 3GPP Specifications". 3GPP TS 23.153: "Out of Band Transcoder Control; Stage 2". 3GPP TS 24.008: "Mobile Radio Interface Layer 3 specification; Core network protocols; Stage 3". 3GPP TS 26.103: "Speech Codec List for GSM and UMTS". 3GPP TS 27.001: "General on Terminal Adaptation Functions (TAF) for Mobile Stations (MS)". 3GPP TS 29.007: "General requirements on interworking between the Public Land Mobile Network (PLMN) and the Integrated Services Digital Network (ISDN) or Public Switched Telephone Network (PSTN)". 3GPP TS 29.205: "Application of Q.1900 series to bearer-independent circuit-switched core network architecture; Stage 3". 3GPP TS 22.101: "Service aspects; Service principles". 3GPP TS 33.106: "3GPP Security; Lawful Interception Requirements". 3GPP TS 23.018: "Basic Call Handling; Technical realization". 3GPP TS 23.003: "Numbering, adressing and identification". 3GPP TS 29.232: "Media Gateway Controller (MGC) Media Gateway (MGW) Interface; Stage 3". 3GPP TS 26.102: "Mandatory Speech Codec; AMR Speech Codec; Interface to Iu, Uu, Nb". 3GPP TS 23.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL) ; Stage 2". 3GPP TS 23.082: "Call Forwarding (CF) supplementary services, Stage 2".

The following documents contain provisions, which, through reference in this text, constitute provisions of the present document.

[7] [8] [9] [10] [11] [12] [13] [14] [15]

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

[16]

3GPP TS 22.078: "Customised Applications for Mobile network Enhanced Logic (CAMEL); Service description, Stage 1".

3
3.1

Definitions and abbreviations


Definitions

For the purposes of the present document, the terms and definitions given in 3GPP TR 21.905 [1] and the following apply: Editor's note: To be completed. fallback: when two services (multimedia and speech) are proposed but only one of them is available or wanted, only the service available (preferred or less preferred) is selected, and the other one is discarded service change: when two services (multimedia and speech) are available during the active state of a call, users may request a service change to switch between the two services

3.2
BC BC1 BC2 BCa BCb BCmm BCSM BCsp CAMEL DP IE MMI O-MSC OoBTC O-UE RI SCUDIF T-MSC T-UE

Abbreviations
Bearer Capability First Bearer Capability in a message (preferred service) Second Bearer Capability in a message (less preferred service) Bearer Capability of the currently selected service Bearer Capability of the service to switch to Bearer Capability multimedia Basic Call State Model Bearer Capability speech Customised Applications for Mobile network Enhanced Logic Detection Point Information Element Man-Machine Interface Originating MSC Out-of-Band Transcoder Control Originating UE Repeat Indicator Service Change and UDI/RDI Fallback Terminating MSC Terminating UE

For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 [1] and the following apply:

4
4.1

Service change and fallback for UDI/RDI multimedia


General Requirements

The Service Change and UDI Fallback (SCUDIF) is a function which applies to UDI/RDI multimedia calls (see 3GPP TS 22.101 [8], clause 7.2.1), and shall support the following: a) Fallback to speech during call setup: allow a user to attempt to set up a multimedia call, and try a speech connection if the former doesn't succeed; b) Fallback to the less preferred service (speech or multimedia) during call setup: allow the terminating side via specific settings for this service in the terminal to accept or reject a multimedia call, without interrupting the call setup;

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

c) Fallback to the preferred service (speech or multimedia) or speech during call setup: allow the call setup to proceed with a single service if the transit network does not support the signalling of this functionality; d) BC negotiation at the terminating side: allow the terminating side via specific settings for this service in the terminal to turn a speech call (with service change) into a multimedia call and vice-versa; e) Service change: allow a speech call to be turned to multimedia by either of parties, and back to speech, through a successful in call modification procedure; f) Allow any of the users to reject a multimedia request from the other party while in speech mode. To fulfil: service request signalling between the UE and the MSC; service request signalling across the Core Network.

This functionality is not supported for multimedia with Fixed Network User Rate set to 32 kbit/s. In this case, the MSC shall revert to a multimedia only call.

4.2

Access Call Control Signalling

Using the repeat indicator value "support of service change and fallback", as described in 3GPP TS 24.008 [3], clause 5.3.6, together with two BC-IEs, a multimedia and a speech, it is possible to request a service change and fallback functionality, while still maintaining the backwards compatibility with non-supporting terminals.

4.2.1

Mobile originating side - initiation of call setup

By sending a SETUP message with a Repeat Indicator set to "support of service change and fallback", a multimedia BC-IE, and a speech BC-IE (see figure 4.1), a terminal may request a call to be set with the capability to fallback to either a speech only, a multimedia only call or to use service change later during the active state of the call (the first BC-IE indicates the preferred service). After checking the provisioning (see subclause 4.2.1.1), and verifying that the functionality is supported, the MSC replies in the CALL PROCEEDING message with either the two BCs in the same order (to indicate that it accepts the proposed settings - see figure 4.2), or with a single BC (multimedia or speech - see figure 4.3) unless the CALL PROCEEDING is delayed until the response from the terminating user and then it may also be sent with the BCs in reverse order (see clause 4.2.3). In the case the MSC ignores the SETUP message if the presence of a reserved value for the Repeat Indicator is set, it sends a STATUS message back to the UE (see figure 4.4), with the Cause Value set to #100, "Conditional IE error" (see 3GPP TS 24.008 [3], clause 8.7.2). The UE then reacts as described in 3GPP TS 24.008 [3], clause 5.5.3.2.2, and may resend a new SETUP message with a single BC, or perform any appropriate action according to its implementation. This also applies in case the MSC returns instead a RELEASE COMPLETE message.
O-UE SETUP (RI, BC1, BC2) O-MSC

Figure 4.1: SETUP message towards the originating MSC

O-UE CALL PROCEEDING (RI, BC1, BC2)

O-MSC

Figure 4.2: Normal case

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

O-UE CALL PROCEEDING (BC1 or BC2)

O-MSC

Figure 4.3: Fallback case

O-UE STATUS (Cause:#100)

O-MSC NOTE

SETUP (BC1 or BC2)

NOTE

CALL PROCEEDING (BC)

NOTE:

The sending of the STATUS message from the MSC and the second SETUP message from the UE are implementation dependent.

Figure 4.4: MSC not supporting the RI value

4.2.1.1

Subscription checking

The functional behaviour of the originating MSC and VLR is specified in 3GPP TS 23.018 [10]. The procedure specific to SCUDIF is specified in this subclause: For mobile originated SCUDIF calls, the MSC shall convert both PLMN bearer capability 1 and PLMN bearer capability 2 to two individual Basic Service codes and send them in Send Info For Outgoing Call. The VLR shall check the subscription for those basic services, then indicates the availability of each basic service to the MSC by Complete Call. If both services are not provisioned, the VLR shall send Send Info For Outgoing Call negative response to the MSC. The MSC shall fall back to the allowed service if the availability of only one service is indicated. The MSC shall continue as a SCUDIF call if the availability of both services is indicated.

4.2.1.1.1

Send Info For Outgoing Call

Send Info For Outgoing Call contains the following SCUDIF specific information elements:
Information element name Bearer service2 Status C Description Bearer service 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present. Teleservice 2 required for the MO call, derived from the PLMN bearer capability 2 information received in the set-up request from the MS. For a SCUDIF call, one of bearer service 2 or teleservice 2 shall be present.

Teleservice2

4.2.1.1.2

Complete Call

Complete Call contains the following SCUDIF specific information elements:


Information element name First service availability Second service availability Status C C Description Shall be present for a MO SCUDIF call if the Bearer service or Teleservice is allowed; otherwise shall be absent. Shall be present for a MO SCUDIF call if the Bearer service 2 or Teleservice 2 is allowed; otherwise shall be absent.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

ETSI TS 123 172 V5.6.0 (2005-06)

4.2.2

Mobile terminating side

When the terminating MSC receives a request for a multimedia call, it shall check if the called user is provisioned for the service (see subclause 4.2.2.1). The terminating MSC shall include in the SETUP message towards the UE both BC-IEs in the same order as indicated by the incoming request together with the Repeat Indicator set to "service change and fallback in order to invoke the SCUDIF functionality in the called terminal (see figure 4.5). The terminating UE, based on its capabilities and internal settings, may return the two BC-IEs in the same order (to indicate that it accepts the proposed settings - see figure 4.6), reversed order (see figure 4.7), or just one BC-IE (either speech or multimedia - see figure 4.8) to the terminating MSC in the CALL CONFIRMED message. In the case the UE ignores the SETUP message due to the presence of a reserved value for the Repeat Indicator, it sends a STATUS message back to the terminating MSC (see figure 4.9), with the Cause Value set to #100, "Conditional IE error" (see 3GPP TS 24.008 [3], clause 8.7.2). The terminating MSC shall then react according to 3GPP TS 24.008 [3], clause 5.5.3.2.2 and it shall send a new SETUP message with a single BC, either the preferred service BC-IE or the speech BC-IE (fallback to speech), depending on configuration. The call setup then proceeds accordingly.
T-MSC SETUP (RI, BC1, BC2) T-UE

Figure 4.5: SETUP message towards the terminating UE

T-MSC CALL CONFIRMED (RI, BC1, BC2)

T-UE

Figure 4.6: Normal case

T-MSC CALL CONFIRMED (RI, BC2, BC1)

T-UE

Figure 4.7: Reversed call setup

T-MSC CALL CONFIRMED (BC1 or BC2)

T-UE

Figure 4.8: Fallback case

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

10

ETSI TS 123 172 V5.6.0 (2005-06)

T-MSC STATUS (Cause: #100)

T-UE

SETUP (BC1 or BC2)

CALL CONFIRMED (BC )

Figure 4.9: UE not supporting the RI value

4.2.2.1

Subscription checking

The functional behaviour of the terminating MSC and VLR is specified in 3GPP TS 23.018 [10]. The procedure specific to SCUDIF calls is specified in this subclause. For mobile terminating SCUDIF calls, the MSC shall convert the services received in the incoming request to two individual Basic Service codes, and include them in Send Info For Incoming Call. The VLR shall check the subscription for those basic services, then indicate the availability of each basic service to the MSC by Complete Call. If both services are not provisioned, the VLR shall send Send Info for Incoming Call negative response to the MSC. The MSC shall fall back to the allowed service if the availability of only one service is indicated. The MSC shall continue as a SCUDIF call if the availability of both services is indicated.

4.2.2.1.1

Send Info For Incoming Call

Send Info For Incoming Call contains the following SCUDIF specific information elements:
Information element name Bearer Service 2 Required C Description Bearer Service 2 required for the MT call, derived from the less preferred service indicated in the incoming IAM of a SCUDIF call. For a SCUDIF call, one of Bearer service 2 or Teleservice 2 shall be present. Teleservice 2 required for the MT call, derived from the less preferred service indicated in the incoming IAM of a SCUDIF call. For a SCUDIF call, one of Bearer service 2 or Teleservice 2 shall be present.

Teleservice 2

4.2.2.1.2

Complete Call

The parameters described in subclause 4.2.1.1.2 "Complete Call" for the mobile originating MSC are also applicable to the mobile terminating MSC.

4.2.3

Mobile originating side - completion of call setup

If the preferred mode, that is the first BC-IE indicated by the originating UE, was selected as the result of negotiations, the call shall be set up normally towards the originating UE. If the negotiation resulted in a change of the selected mode, i.e. the call was set up as "multimedia first" and changed during the negotiation to a speech call, or vice-versa, because of either fallback or change of selected mode and the Call Proceeding message has been sent then an In-Call Modification procedure (see 3GPP TS 24.008 [3], clause 5.3.4.3) shall be initiated towards the originating UE after the call control entity has entered the active state, i.e. the CONNECT message has been sent.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

11

ETSI TS 123 172 V5.6.0 (2005-06)

O-UE CONNECT

O-MSC

CONNECT ACKNOWLEDGE

Figure 4.10: Preferred mode selected

O-UE CONNECT

O-MSC

CONNECT ACKNOWLEDGE

MODIFY (BC2)

MODIFY COMPLETE (BC2)

Figure 4.11: Less preferred mode selected, accepted

O-UE CONNECT

O-MSC

CONNECT ACKNOWLEDGE

MODIFY (BC2)

MODIFY REJECT (BC1)

RELEASE COMPLETE

Figure 4.12: Less preferred mode selected, rejected If the Call Proceeding message is delayed until response from the terminating side then it may include one or both BCs either in the order requested from the Originating UE or the order of the BCs may be reversed, depending on the result from the negotiation or (single BC) due to fallback. See Figure 4.12a.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

12

ETSI TS 123 172 V5.6.0 (2005-06)

O-UE

O-MSC

(select = x, avail = x, y, z, mm) CALL PROCEEDING (RI, BC2, BC1) CONNECT CONNECT ACKNOWLEDGE

Figure 4.12a: Call Proceeding Delayed

4.2.4

Service change in the active state

At any given time, if either of call parties wants to change from the current active mode to the other mode via MMI, the terminal shall activate an In-Call Modification procedure. Using this procedure, described in 3GPP TS 24.008 [3], clause 5.3.4.3, the UE shall send a MODIFY message containing the BC-IE to change to. This BC-IE shall be one of those already negotiated at call setup. As a result, the MSC shall then invoke the service change procedure (see clause 4.3.5). If the request is accepted, the originating MSC sends a MODIFY COMPLETE message to the UE including the BC-IE of the mode to switch to (see figure 4.13). If the request is rejected, the MSC sends a MODIFY REJECT message to the UE including the BC-IE from the current active mode (see figure 4.14). In the case the MSC has determined that the other mode is unavailable (e.g. a fallback to either mode has occurred), it shall reject the MODIFY request at once by replying with a MODIFY REJECT message. On the remote side, the MSC shall initiate an In-Call Modification procedure towards the terminal using the MODIFY message. The terminal shall request confirmation from the user unless configured differently. If the change is accepted, the UE shall reply to the MSC with a MODIFY COMPLETE message, whereas a MODIFY REJECT message shall be sent if the change is rejected. NOTE: Privacy concerns strongly advise that any change to multimedia mode, unless explicitly allowed by the user in the terminal configuration settings, triggers a question to the user in order to confirm or decline the change. The details on how to provide the user interaction are left for implementation.
UE A MODIFY (BCb) Core Network Procedure MODIFY (BCb) MSC A MSC B UE B

MODIFY COMPLETE (BCb) Core Network Procedure MODIFY COMPLETE (BCb)

Figure 4.13: Service change requested, accepted

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

13

ETSI TS 123 172 V5.6.0 (2005-06)

UE A MODIFY (BCb)

MSC A

MSC B

UE B

Core Network Procedure MODIFY (BCb)

MODIFY REJECT (BCa) Core Network Procedure MODIFY REJECT (BCa)

Figure 4.14: Service change requested, rejected

4.3

Core Network procedures

In order to provide the capability in the network to transmit the request for service change and fallback both at call setup and during the active state of a call, the normal Out-of-Band Transcoder Control procedures, described in 3GPP TS 23.153 [2] shall be used. The following text describes the codec to be used, the mapping between the terminal interface described above, and the different IEs to be used for the codec negotiation procedures at both the originating and the terminating MSC.

4.3.1

Multimedia codec

The codec negotiation procedures transmit an ordered list of preferred codecs from the originating to the terminating MSC. A node that requires interaction with the user plane will remove the codecs it does not support. The terminating MSC shall select the codec to use ("selected codec") from the list of available codecs for the call. This selection shall be based on the received list of codecs and on the information given by the terminating UE in the CALL CONFIRMED message. A dummy codec (defined in 3GPP TS 26.103 [4]) is included in the codec list to indicate that a multimedia call is requested. This codec is in the present document referred to as the 3G-324.M codec. This codec is only used by the Core Network and shall not be sent from the terminal in the Supported Codec List IE. The 3G-324.M codec shall be indicated to the MGW as codec media stream property in accordance with the3GPP TS 29.232[12]. The MGW shall treat the User Plane configuration (SDU Format) of the 3G-324.M codec as for PCM, as defined in 3GPP TS 26.102 [13].

4.3.2

Originating side - initiation of call setup

The originating MSC has a list of supported codec types, listed in order of preference. If the SETUP message received from the UE contains a Repeat Indicator with a value of "service change and fallback", in addition to a multimedia BC-IE and a speech BC-IE, the MSC shall include a 3G-324.M codec in the list of supported codec types according to the following rule: if the multimedia BC-IE is listed first, then the 3G-324.M codec shall be the first codec in the list (see figure 4.15); if the speech BC-IE is listed first, then the 3G-324.M codec shall be the last codec in the list (see figure 4.16). In the case that the maximum number of codecs is already reached before insertion of the 3G-324M codec, the optional speech codec with the least preference shall be replaced by the 3G-324.M codec.

The list shall then be sent according to the Out-of-Band Transcoder Control codec negotiation procedures. The TMR field, although mandatory BICC/ISUP parameter, has no meaning when using OoBTC/BICC codec negotiation (the link characteristics and QoS are determined from the codec type and signalled to any intermediate switches via the bearer control protocol) and thus shall be set arbitrarily to "speech". A transit node that requires interaction with the user

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

14

ETSI TS 123 172 V5.6.0 (2005-06)

plane will remove from the list the codecs it does not support. If the 3G-324.M codec is not supported, and thus removed, the call shall be turned into a normal speech call (fallback to speech) and follow the normal call setup procedures.
O-UE SETUP (RI, BCmm, BCsp) (List of Codecs = mm, x, y, z) O-MSC T-MSC

x, y, z: mm:

speech codecs. dummy multimedia codec.

Figure 4.15: Multimedia BC as first BC

O-UE SETUP (RI, BCsp, BCmm)

O-MSC

T-MSC

(List of Codecs = x, y, z, mm)

Figure 4.16: Speech BC as first BC

4.3.3
4.3.3.1

Terminating side
HLR Interrogation

The GMSC sends the Send Routing Information request with both the Network Signal Information and Network Signal Information 2 parameters. The Network Signal Information shall include the ISDN BC IE for the preferred service, and the Network Signal Information 2 includes the ISDN BC IE for the less preferred service. The functional behaviour of the HLR is described in 3GPP TS 23.018 [10]. The procedures specific to SCUDIF calls are specified in the subclause 4.3.3.1.3 for the HLR and 4.3.3.1.4 for the GMSC. The information elements specific to SCUDIF between the GMSC and the HLR are specified in subclauses 4.3.3.1.1 and 4.3.3.1.2.

4.3.3.1.1

Send Routing Info

The following element specific to SCUDIF calls is defined for Send Routing Info:
Information element name ISDN BC 2 ISDN LLC 2 Required C C Description ISDN bearer capability 2. Shall be present for a SCUDIF call to indicate the less preferred service. ISDN lower layer compatibility 2. Shall be present for a SCUDIF call if necessary for the less preferred service, otherwise shall be absent. ISDN higher layer compatibility 2. Shall be present for a SCUDIF call if necessary for the less preferred service, otherwise shall be absent.

ISDN HLC 2

4.3.3.1.2

Send Routing Info Ack

The following elements specific to SCUDIF calls are defined for Send Routing Info Ack:

ETSI

3GPP TS 23.172 version 5.6.0 Release 5 Information element name Roaming number 2 Required C

15

ETSI TS 123 172 V5.6.0 (2005-06)

Forwarded-to number 2

Long forwarded-to number 2

Forwarded-to subaddress 2

Notification to calling party 2

Forwarding reason 2

SS-List 2

Basic Service Code 2 Allowed Services Unavailability Cause

C C C

Description E.164 number required to route the call to VMSCB (see 3GPP TS 23.003 [11]) for the less preferred service of a SCUDIF call. Shall be present for a SCUDIF call if the preferred service is not forwarded (i.e. either Roaming Number is present or the preferred service is not allowed) and the less preferred service is allowed and not forwarded, otherwise shall be absent. E.164 number of the C subscriber for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. Number of the C subscriber (see 3GPP TS 23.082 [15]) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, and GMSC and HLR support Long Forwarded-to Numbers, otherwise shall be absent. Subaddress of the C subscriber (see 3GPP TS 23.003 [11]) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded and a forwarded-to subaddress is stored in the HLR in association with the forwarded-to number 2, otherwise shall be absent. Indication of whether the calling party is to be notified that the call has been forwarded if the less preferred service of a SCUDIF call is kept. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. Indication of why the call has been forwarded (unconditionally or on mobile subscriber not reachable) for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is to be forwarded, otherwise shall be absent. List of SS-codes for the less preferred service of a SCUDIF call. Shall be present if the HLR has determined that the less preferred service of a SCUDIF call is allowed, otherwise shall be absent. Indicates the type of the basic service for the less preferred service, i.e. teleservice or bearer service. Shall be present for SCUDIF calls. Indicates which services are available for that call. Indicates the reason for which one of the services of a SCUDIF call is not available. Shall be present for SCUDIF calls if one service is not available.

4.3.3.1.3

Handling of mobile terminating calls in the HLR

The procedures specific to SCUDIF calls in the HLR are specified within this subclause: Procedure SCUDIF_Subscription_Check_HLR Procedure SCUDIF_CAMEL_CSI_Check_HLR Procedure SCUDIF_Set_Second_Service_when_Forwarded Procedure SCUDIF_Set_Correct_PLMN_BC Procedure SCUDIF_Check_Second_Service_before_Negative_Response Procedure SCUDIF_Check_Second_Service_after_PRN Procedure SCUDIF_Check_Second_Service_when_Forwarded

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

16

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Subscription_Check_HLR
Procedure in the HLR to check the subscription f or the second service and store the unavailability cause if one of the services is not available

SCSC_HLR1(2)

Second Network Signal Info Present? Yes Store Result for first service

no

result=fail? no yes service related negative response? yes Unavailability Cause:= negative response no

Allowed Services := both

Allowed Services := second Service

requested service := Network Signal Info 2

Figure 4.16A: Procedure SCUDIF_Subscription_Check_HLR (sheet 1)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

17

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Subscription_Check_HLR
Procedure in the HLR to check the subscription f or the second service and store the unavailability cause if one of the services is not available

SCSC_HLR2(2)

Subscription_Check_ HLR

for second service

result=fail? yes no result for first service =fail? no Unavailability Cause:= negative response negative response := negative response for first service

yes

Allowed Services := first Service

result := pass

Figure 4.16B: Procedure SCUDIF_Subscription_Check_HLR (sheet 2)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

18

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_CAMEL_CSI_Check_HLR
Procedure in the HLR to check the CAMEL data for the second service to know if CAMEL is active for that call

1(1)

Network Signal Info 2 present? yes

no

interrogation on second service? no

yes

result = CSI active? yes no

CAMEL_CSI_ Subscription_Check

for second service

Figure 4.16C: Procedure SCUDIF_CAMEL_CSI_Check_HLR

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

19

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Set_Second_Service_when_forwarded
Procedure in the HLR to set the forwarding information to the correct service for SCUDIF

1(1)

Network Signal Info 2 present? yes interrogation on second service? yes Store Forwarding Information for second Service Store Forwarding Information for first Service

no

no

first service allowed?

no

yes

result := SRI_Ack

result := continue

Figure 4.16D: Procedure SCUDIF_Set_Second_Service_when_Forwarded

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

20

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Set_Correct_PLMN_BC
Procedure in the HLR to set the speech PLMN BC SCUDIF calls

1(1)

Network Signal Info 2 present? yes both services allowed ? yes interrogation on the first service? no routing address no of first service is MSRN? yes Copy MSRN for service to MSRN second service

no

no

yes

PLMN BC := BC for speech service

PLMN BC := BC for allowed service result := set_PLMN_BC

result := SRI_Ack

result := continue

Figure 4.16E: Procedure SCUDIF_Set_Correct_PLMN_BC

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

21

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Check_second_service_before_Negative_response
Procedure in the HLR to check the second service before sending a SRI negative response back to the GMSC

1(1)

no

Second Network Signal info present? yes interrogation on second service? yes

no service related negative response? no

no

interrogation on first service failed? yes

yes requested service := second signal network info

restore routeing information for first service

negative response := negative response for first service

unavailability cause := negative response

unavailability cause := negative response allowed services := second service

allowed services := first service

result := fail

result := pass

result := fail

result := second interrogation

result := fail

Figure 4.16F: Procedure SCUDIF_Check_Second_Service_before_Negative_Response

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

22

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Check_Second_Service_after_PRN
Procedure in the HLR to check the second service after PRN response has been received

1(1)

Network Signal Info 2 present? yes

no

interrogation on second service? no

yes

Store routeing information for the first service

Store routeing information for the second service

requested service := second network signal info

result := second interrogation

result := continue

Figure 4.16G: Procedure SCUDIF_Check_Second_Service_after_PRN

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

23

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Check_Second_Service_when_forwarded
Procedure in the HLR to check the second service when a service is forwarded

1(1)

Network Signal Info 2 present? yes

no

CSI active?

yes

no

interrogation on second service? no

yes

Store routeing information for the first service

Store routeing information for the second service

requested service := Network Signal Info 2

result := second interrogation

result := continue

Figure 4.16H: Procedure SCUDIF_Check_Second_Service_when_Forwarded

4.3.3.1.4

Handling of mobile terminating calls in the GMSC

The procedures specific to SCUDIF calls in the GMSC are specified within this subclause: Procedure SCUDIF_Negative_SRI_Response_Handling Procedure SCUDIF_Check_Service_Availability Procedure SCUDIF_Check_Service_Compatibility

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

24

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Negative_SRI_Response_Handling
Procedure in the GMSC to handle a second interrogation for SCUDIF call when a negative response is received

SC_SRI1(1)

SCUDIF call? no yes

second interrogation? no yes

service related error? no yes no

first interrogation successful? yes

Fallback to the less preferred service

retrieve SRI result from first interrogation

result := fail

result := retry

result := fail

result := pass

Figure 4.16I: Procedure SCUDIF_Negative_SRI_Response_Handling

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

25

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Check_Service_Availability
Procedure in the GMSC to fallback to a single service if one of the services of a SCUDIF call is unavailable

SC_S_A1(1)

SCUDIF call? yes Allowed services indicator present? yes Value of Allowed services indicator ? both

No

no second interrogation? no

yes

first service Second Service Fallback to the Fallback to the less preferred service preferred service

yes included? MSRN no Store SRI for preferred service

Result is for the less preferred service

result := continue

result := second_SRI

result := continue

Figure 4.16J: Procedure SCUDIF_Check_Service_Availability

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

26

ETSI TS 123 172 V5.6.0 (2005-06)

procedure SCUDIF_Check_Service_Compatibility
Procedure in the GMSC to fallback to a single service if the services of a SCUDIF call have different destination

SC_S_C1(1)

SCUDIF call?

no

yes

MSRN provided for preferred service?

yes Forwarding data no provided for less preferred service? no yes

no

Forwarding data provided for less preferred service? yes

Forwarded-to number identical for both services? yes

no

Fallback to the preferred service

Figure 4.16K: Procedure SCUDIF_Check_Service_Compatibility

4.3.3.2

Terminating MSC Handling

The terminating MSC receives the list of supported codec types, including the 3G-324.M codec. It shall then send a SETUP message towards the terminating UE including a Repeat Indicator with the value "service change and fallback" and two BC-IEs, according to the following rule: if the 3G-324.M codec is the first (preferred) codec in the list of supported codecs, then the first BC-IE in the SETUP message is the multimedia BC-IE, and the second BC-IE is the speech BC-IE (see figure 4.17); if the 3G-324.M codec is in the list of supported codec types, but not in the first position, then the first BC-IE in the SETUP message is the speech BC-IE, and the second BC-IE is the multimedia BC-IE (see figure 4.18).

The terminating UE answers according to its capabilities in the CALL CONFIRMED message. The terminating MSC shall determine the Selected Codec and construct the list of available codecs according to the following rules:

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

27

ETSI TS 123 172 V5.6.0 (2005-06)

if no Repeat Indicator is included, and only a speech BC-IE is received, the MSC shall choose a speech codec as the Selected Codec according to the normal mechanism, and no 3G-324.M codec shall be inserted in the list of available codecs (see figure 4.19); if no Repeat Indicator is included, and only a multimedia BC-IE is received, the MSC shall choose the 3G-324.M codec as the Selected Codec, and only the 3G-324.M codec shall be inserted in the list of available codecs (see figure 4.20); if the Repeat Indicator is included, and the speech BC_IE is the first BC-IE and the multimedia BC-IE is the second BC-IE, the MSC shall choose a speech codec as the Selected Codec according to the normal mechanism, and both the 3G-324.M codec and speech codecs shall be inserted in the list of available codecs (see figure 4.21); if the Repeat Indicator is included, and the multimedia BC-IE is the first BC-IE and the speech BC-IE is the second BC-IE, the Selected Codec shall be the 3G-324.M codec, and both the 3G-324.M codec and speech codecs shall be inserted in the list of available codecs (see figure 4.22).

The Selected Codec and the list of available codecs shall be sent back to the originating MSC according to the normal codec negotiation procedure.
O-MSC (List of Codecs = mm, x, y, z) SETUP (RI, BCmm, BCsp) T-MSC T-UE

Figure 4.17: 3G-324M codec first

O-MSC (List of Codecs = x, y, z, mm)

T-MSC

T-UE

SETUP (RI, BCsp, BCmm)

Figure 4.18: Speech codec first

O-MSC

T-MSC CALL CONFIRMED (BCsp)

T-UE

(select = x, avail = x, y, z)

NOTE

NOTE:

The actual speech codec is selected according to OoBTC procedures.

Figure 4.19: Speech only

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

28

ETSI TS 123 172 V5.6.0 (2005-06)

O-MSC

T-MSC

T-UE

CALL CONFIRMED (BCmm)

(select = mm, avail = mm)

Figure 4.20: Multimedia only

O-MSC

T-MSC

T-UE

CALL CONFIRMED (RI, BCsp, BCmm)

(select = x, avail = x, y, z, mm)

NOTE

NOTE:

The actual speech codec is selected according to OoBTC procedures.

Figure 4.21: Speech preferred

O-MSC

T-MSC

T-UE

CALL CONFIRMED (RI, BCmm, BCsp)

(select = mm, avail = mm, x, y, z) NOTE

NOTE:

The actual list of speech codecs is built according to OoBTC procedures.

Figure 4.22: Multimedia preferred

4.3.4

Originating side - completion of call setup

The originating MSC receives the Selected Codec and the list of available codecs, and, depending on the active mode, shall do the following: The call was set up with a multimedia BC-IE first: if the Selected Codec is the 3G-324.M codec, no In-Call Modification procedure is necessary (see figure 4.23). If no speech codecs are included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the speech BC-IE shall be rejected with a MODIFY REJECT message; if the Selected Codec is a speech codec, an In-Call Modification procedure to change to speech mode shall take place (see figure 4.24). If the 3G-324.M codec is not included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the multimedia BC-IE shall be rejected with a MODIFY REJECT message.

The call was set up with a speech BC-IE first: if the Selected Codec is the 3G-324.M codec, an In-Call Modification procedure to change to multimedia mode shall take place (see figure 4.25). If no speech codecs are included in the list of available codecs, all In-Call

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

29

ETSI TS 123 172 V5.6.0 (2005-06)

Modification procedures initiated by the UE using the speech BC-IE shall be rejected with a MODIFY REJECT message; if the Selected Codec is a speech codec, no In-Call Modification procedure is necessary (see figure 4.26). If the 3G-324.M codec is not included in the list of available codecs, all In-Call Modification procedures initiated by the UE using the multimedia BC-IE shall be rejected with a MODIFY REJECT message.
O-UE O-MSC (select = mm, avail = mm, x, y, z) CONNECT T-MSC

NOTE

NOTE:

Speech codecs (x, y, z) may or may not be present. If they are not present, subsequent MODIFY requests from the UE are rejected.

Figure 4.23: Multimedia preferred, selected

O-UE

O-MSC (select = x, avail = x, y, z, mm) CONNECT MODIFY (BCsp)

T-MSC NOTE 1

NOTE 2

NOTE 1: The multimedia codec (mm) may or may not be present. If it is not present, subsequent MODIFY requests from the UE are rejected. NOTE 2: see clause 4.2.3 for the In-Call Modification signalling.

Figure 4.24: Multimedia preferred, speech selected

O-UE

O-MSC

T-MSC (select = mm, avail = mm, x, y, z) NOTE 1

CONNECT MODIFY (BCmm) NOTE 2

NOTE 1: Speech codecs (x, y, z) may or may not be present. If they are not present, subsequent MODIFY requests from the UE are rejected. NOTE 2: see clause 4.2.3 for the In-Call Modification signalling.

Figure 4.25: Speech preferred, multimedia selected

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

30

ETSI TS 123 172 V5.6.0 (2005-06)

O-UE

O-MSC (select = x, avail = x, y, z, mm)

T-MSC NOTE

CONNECT

NOTE:

The multimedia codec (mm) may or may not be present. If it is not present, subsequent MODIFY requests from the UE are rejected.

Figure 4.26: Speech preferred, selected

4.3.5

Service change during the active state

Whenever an In-Call Modification procedure is invoked by a terminal, unless it is not allowed as determined at call setup, the following shall take place: if the current mode is the speech mode and the MODIFY message contains a multimedia BC-IE, the normal Out-of-Band Transcoder Control procedures shall be invoked in order to change the Selected Codec to the 3G-324.M codec; if the current mode is the multimedia mode and the MODIFY message contains a speech BC-IE, the normal Out-of-Band Transcoder Control procedures shall be invoked in order to change the Selected Codec to the preferred speech codec.

The Codec Modification procedure shall be supported for service change. The use of mid-call codec negotiation procedure is optional for service change. When a MSC detects through an Out-of-Band Transcoder Control procedure that the selected codec has changed from a speech codec to the 3G-324.M codec, or vice-versa, it shall initiate an In-Call Modification procedure towards the UE with a MODIFY message containing the multimedia BC-IE (or the speech BC-IE), unless the new mode has been denied at call setup (see clause 4.2.4).

4.3.5.1

Mid-Call Codec Modification Procedure For Service Change

The Codec Modification procedures as defined in 3GPP TS 23.153 [2] shall be applied with the following specific additional rules for the Service Change procedure. In order to prevent the MGW generating an error or seizing resources during the interim period when its terminations are being altered and it may have a speech codec on one side of the context and the 3G-324M codec on the other side the Server shall modify the Streammode of the affected terminations to inactive during the Service change and shall restore the stream mode to active (send/receive bothway) on completion of the service change procedure. In order to restore the stream mode to active, the MSC servers shall use the 'Modify Bearer Characteristics' procedure for Iu terminations and for Nb terminations towards the succeeding node with respect to the 'Modify Codec' message. The MSC servers shall use the 'Confirm Bearer Characteristics' procedure for Nb terminations towards the preceding node with respect to the 'Modify Codec' message. If the affected termination"s stream mode is inactive a MGW shall not reject a 'Modify Bearer Characteristics' or a 'Reserve Bearer Characteristics' procedure because the multimedia codec and a speech codec are interconnected simultaneously in the same context. For a service change where the CN shall initiate the IuUP on the Nb interface, the MSC server terminating the service change shall trigger the IuUP initialisation towards the core network by setting the IuUP initialisation direction to 'out' in the 'Confirm Bearer Characteristics' procedure for the corresponding termination towards the core network. Example call flows are shown in Figure 4.3.5.1/1 to 4.3.5.1/6.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

31

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

M SC- A MGW-A

Server B MGW-B

M SC- C MGW-C

RNC C

Direct Transfer [M odify (MuM e) M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec = M uM e 3GUP mode=transparent ) RAB Assign M odify (M uM e RAB parameters) M odify Bearer Request M odify Bearer Ack RAB Assign M odify Rsp M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec = M uM e, Dir=IN) M odify Codec (Selected Codec = M uM e) Reserve Bearer Characteristics (Stream M ode=INACTIVE, New Codec = M uM e, Dir=IN) M odify Bearer Request M odify Bearer Ack BNC M odified M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec = M uM e, Dir=IN)

Optionally to increase bandwidth

Optionally to increase bandwidth

M odify Codec (Selected Codec= M uM e) Reserve Bearer Char (Stream M ode=INACTIVE, New Codec = M uM e)

M odify Bearer Request M odify Bearer Ack BNC M odified

Optionally to increase bandwidth

Direct Transfer [M odify (MuM e)] Direct Transfer [M odify Complete(M uM e)] M odify Bearer Characteristics (Stream M ode=INACTIVE, codec = M uM e, mode=transparent ) RAB Assign M odify (M uM e RAB parameters)

Optionally to increase bandwidth

M odify Bearer request M odify BearerAck RAB Assign M odify Rsp

Figure 4.3.5.1/1: Service change speech to MuMe

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

32

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

M SC- A MGW-A

Server B MGW-B

M SC- C MGW-C

RNC C

M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = M uM e)

Confirm Bearer Char (Stream M ode=ACTIVE, Codec = M uM e, Dir=OUT ) Iu FP Init Iu FP Init Iu FP Init Ack Iu FP Init Ack Successful Codec M odification M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = M uM e,)

Confirm Bearer Char (Stream M ode=ACTIVE, Codec = M uM e)

Successful Codec M odification M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = M uM e )

M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = M uM e )

Direct Transfer [M odify_Complete (M uM e)

Figure 4.3.5.1/2: Service change speech to MuMe (continued)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

33

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

M SC- A MGW-A

Server B MGW-B

M SC- C MGW-C

RNC C

Direct Transfer [M odify (speech) M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec = AM R, Dir=OUT, )

RAB Assign M odify (AMR RAB parameters) Iu FP Init Iu FP Init Ack M odify Bearer Request M odify Bearer Ack RAB Assign M odify Rsp M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec = AM R)

Optionally to decrease bandwidth

M odify Codec (Selected Codec = AM R) Reserve Bearer Characteristics (Stream M ode=INACTIVE, New Codec = AM R 3GUP Dir=IN ) BNC M odified M odify Bearer Characteristics (Stream M ode=INACTIVE, New Codec =AM R 3GUP Dir=IN,) M odify Codec (Selected Codec= AM R) Reserve Bearer Char (Stream M ode=INACTIVE, New Codec = AM R, 3GUP Dir=IN,) BNC M odified M odify Bearer Characteristics (Stream M ode=INACTIVE, codec = AM R, 3GUP Dir=IN )

Direct Transfer [M odify (AM R)] Direct Transfer [M odify Complete(AM R)] RAB Assign M odify (AMR RAB parameters) Iu FP Init Iu FP Init Iu FP Init Ack Iu FP Init Ack Iu FP Init Iu FP Init Ack Iu FP Init Iu FP Init Ack

Optionally for RFCI value correction

Optionally to decrease bandwidth

M odify Bearer request M odify BearerAck

RAB Assign M odify Rsp

Figure 4.3.5.1/3: Service change MuMe to AMR

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

34

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

MSC- A MGW-A

Server B MGW-B

MSC- C MGW-C

RNC C

Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR)

Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = AMR ) Modify Bearer Request

Optionally to decrease bandwidth

Modify Bearer Ack Successful Codec Modification

Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR)

Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = AMR)

Modify Bearer Request Modify Bearer Ack Successful Codec Modification Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR)

Optionally to decrease bandwidth

Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR)

Direct Transfer (Modify_Complete (speech)

Figure 4.3.5.1/4: Service change MuMe to AMR (continued)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

35

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

MSC- A MGW-A

Server B MGW-B

MSC- C MGW-C

RNC C

Direct Transfer [Modify (speech) Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = AMR, Dir=OUT, )

RAB Assign Modify (AMR RAB parameters) Iu FP Init Iu FP Init Ack Modify Bearer Request Modify Bearer Ack RAB Assign Modify Rsp Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = G.711)

Optionally to decrease bandwidth

Modify Codec (Selected Codec = G.711) Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = G.711 3GUP Dir=IN ) BNC Modified Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec =G.711 3GUP Dir=IN,) Modify Codec (Selected Codec= G.711) Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = G.711,) BNC Modified Modify Bearer Characteristics (Stream Mode=INACTIVE, codec = AMR, 3GUP Dir=IN )

Direct Transfer [Modify (AMR)] Direct Transfer [Modify Complete(AMR)] RAB Assign Modify (AMR RAB parameters) Iu FP Init Iu FP Init Ack

Optionally to decrease bandwidth

Modify Bearer request Modify BearerAck RAB Assign Modify Rsp

Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = AMR)

Figure 4.3.5.1/5: Service change MuMe to PCM(G.711)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

36

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

M SC- A MGW-A

Server B MGW-B

M SC- C MGW-C

RNC C

Confirm Bearer Char (Stream M ode=ACTIVE, New Codec = G.711, 3GUP Dir=Out) Iu FP Init Iu FP Init Iu FP Init Ack Iu FP Init Ack

Successful Codec M odification

M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = G.711)

Confirm Bearer Char (Stream M ode=ACTIVE, New Codec = G.711)

Successful Codec M odification M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = G.711)

M odify Bearer Characteristics (Stream M ode=ACTIVE, codec = AM R)

Direct Transfer (M odify_Complete (speech)

Figure 4.3.5.1/6: Service change MuMe to PCM(G.711) (continued)

4.3.5.2

Unsuccessful Service Change

In the case the service change is denied by the UE at the terminating side, the procedures for the unsuccessful Codec Modification as defined in [2] shall be applied to revert to the old medium (speech or multimedia). The through-connection of terminations shall be performed as described in Subclause 4.3.5.1. The "Codec Modification Failure" message shall interact with the "Modify Bearer Characteristics" procedure and the "Confirm Bearer Characteristics" procedure in the same way as the 'Successful Codec Modification' message. An example sequence is shown in Figure 4.3.5.2/1 to 4.3.5.2/2.

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

37

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

MSC- A MGW-A

Server B MGW-B

MSC- C MGW-C

RNC C

Direct Transfer [Modify (MuMe) Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe mode=transparent ) RAB Assign Modify (MuMe RAB parameters) Modify Bearer Request Modify Bearer Ack RAB Assign Modify Rsp Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) Modify Codec (Selected Codec = MuMe) Reserve Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) Modify Bearer Request Modify Bearer Ack BNC Modified

Optionally to increase bandwidth

Optionally to increase bandwidth Note: note needed if changing from PCM

Modify Bearer Characteristics (Stream Mode=INACTIVE, New Codec = MuMe Dir=IN, ) Modify Codec (Selected Codec= MuMe) Reserve Bearer Char (Stream Mode=INACTIVE, New Codec = MuMe, Dir=IN,) Modify Bearer Request Modify Bearer Ack BNC Modified

Optionally to increase bandwidth Note: note needed if changing from PCM

Direct Transfer [Modify (MuMe)] Direct Transfer [Modify Reject (Speech)]

Figure 4.3.5.2/1:Service Change Rejected

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

38

ETSI TS 123 172 V5.6.0 (2005-06)

RNC-A

MSC- A MGW-A

Server B MGW-B

MSC- C MGW-C

RNC C

Confirm Bearer Char (Stream Mode=ACTIVE, New Codec = Old Codec (G711 or AMR) ) Modify Bearer Request

Optionally to decrease bandwidth Note: Not need if change from PCM

Modify Bearer Ack BNC Modified Codec Modification Failure

Modify Bearer Characteristics (Stream Mode=ACTIVE, codec = Old Codec (G711 or AMR) Confirm Bearer Char (Stream Mode=ACTIVE, Codec = Old Codec (G711 or AMR) Modify Bearer Request Modify Bearer Ack BNC modified Codec Modification Failure Modify Bearer Characteristics (Stream Mode=ACTIVE, codec =Old Codec(G711 or AMR) )

Optionally to decrease bandwidth Note: not needed if change from PCM

Modify Bearer Characteristics (Stream Mode=ACTIVE, Codec = AMR 3GUP Dir=OUT, mode=support ) RAB Assign Modify (AMR RAB parameters) Iu FP Init Iu FP Init Ack Modify Bearer Request Modify Bearer Ack Iu FP Init Iu FP Init Ack RAB Assign Modify Rsp

Optionally to decrease bandwidth Optionally for RFCI value correction Note Not performed if PCM in Core

Direct Transfer (Modify_Reject (speech)

Figure 4.3.5.2/2:Service Change Rejected (Continued)

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

39

ETSI TS 123 172 V5.6.0 (2005-06)

4.3.6
4.3.6.1

Interaction with supplementary services


Call forwarding and Call deflection

If CFB(UDUB), CFNRy, or Call Deflection is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the handling of the call should continue with the active service negotiated between the called UE and the network. If call forwarding except CFB(UDUB) and CFNRy is invoked in a SCUDIF call, and both basic services are provisioned, the HLR (for early call forwarding) or VLR (for late call forwarding) shall check the service for both the preferred service and the less preferred service. Then, the SCUDIF call interacting with call forwarding shall be handled according to the following rules: If the call forwarding is active only for the less preferred service, the preferred service shall be selected and the call setup shall continue with a single service without invoking call forwarding. If the call forwarding is active only for the preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number. If the call forwarding is active for both services and the forwarded to number for the preferred service is same as for the less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number. If the call forwarding is active for both services and the forwarded to number for the preferred service is different from that for the less preferred service, the preferred service shall be selected and call forwarding shall continue with a single service to the destination indicated by the forwarded to number for the preferred service. If the call forwarding is active for both services and CF type for the preferred service is different from that of less preferred service, the call shall continue as a SCUDIF call to the destination indicated by the forwarded to number, and the forwarding reason for the preferred service shall be indicated. For Late call forwarding or Call Deflection with Optimal Routing, the second basic service group code shall be generated in VMSC and sent in Resume Call Handling and may be sent in the following Send Routing Information. The preferred service is set as basic service group IE, and the less preferred service is set as basic service group 2 IE.

NOTE:

4.3.6.2

Closed User Group (CUG)

If a SCUDIF call interacts with CUG and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is not allowed, then the call shall fall back to the allowed service.

4.3.6.3

Call barring

If a SCUDIF call interacts with call barring and both basic services are provisioned, the service state shall be checked for both the preferred service and the less preferred service. If one service is barred, then the call shall fall back to the allowed service.

4.3.7
4.3.7.1

Interactions with CAMEL


Interaction at call setup

When a SCUDIF call activates a CAMEL dialogue for the originating or the terminating subscriber, both basic services shall be indicated to the gsmSCF in the InitialDP message (see 3GPP TS 23.078 [14]) : the bearer capability IE and the ext-basic service code IE shall indicate the preferred service (i.e. 3G-324.M if the 3G-324.M codec is the first codec in the list of supported codecs ; speech otherwise),

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

40

ETSI TS 123 172 V5.6.0 (2005-06)

the bearer capability 2 IE and the ext-basic service code 2 IE shall indicate the other, less preferred service (i.e. resp. speech or 3G-324.M).

4.3.7.2

Interaction at call answer

When the Answer DP is triggered according to the BCSM (see 3GPP TS 23.078 [14]), the event report sent to the gsmSCF shall indicate the result from the OoBTC codec negotiation procedure according to the following : the ext-basic service code IE is included, and represents the selected service (indicated by the selected codec) ; the ext-basic service code 2 IE is included if the list of available codecs contains codecs both for speech and 3G324.M, and represents the other service (i.e. speech if the selected service is 3G-324.M, and vice-versa).

4.3.7.3

Interaction with Call Party Handling

Interaction with Call Party Handling is allowed, when the call is a speech call and it cannot become a multimedia call. See 3GPP TS 22.078 [16] clause 21.

4.3.7.4

Interaction with CAMEL in-band information and user interaction

Interaction with Camel in-band information and user interaction is allowed, when the call is a speech call and it cannot become a multimedia call. See 3GPP TS 22.078 [16] clause 21.

4.3.8

Interworking with external networks

If the 3G-324.M codec is included in the list of supported codec types received by a Gateway MSC, and the external network does not support BICC or does not support Codec Negotiation, the Gateway MSC shall terminate the codec negotiation and fallback to a single service. NOTE 1: If the route is known not to support the SCUDIF functionality, the Gateway MSC may decide by configuration to terminate the codec negotiation and follow the procedure described in this clause. In the case where the 3G-324.M codec is the first in the list, the network decides by configuration to fallback either to a UDI multimedia-only call or to speech. In the case where the 3G-324.M codec is not the first on the list, the call shall fallback to speech only. If fallback to multimedia occurs, the call control parameters sent towards the external network shall be set according to the setting for multimedia calls, and TMR is set to "64 kbit/s unrestricted". The 3G-324.M codec shall be returned to the originating MSC server as the selected codec and be the only member of the available codec list. NOTE 2: For multimedia calls, 3GPP TS 27.001 [5], annex B, and 3GPP TS 29.007 [6], table 7A, describe the setting and validity of the PLMN BC-IE as well as the comparable settings of parameters in the PLMN and ISDN BC-IEs. As the ISDN BC-IE parameter values used for UDI/RDI multimedia calls are identical to the BICC USI IE parameter values (see 3GPP TS 29.205 [7]), the setting of call control parameters sent towards the external network in case of fallback to multimedia can be derived straightforward. If fallback to speech occurs, the call control parameters shall be set according to the setting for speech calls, and TMR is set to "speech". The 3G-324.M codec shall be removed from the available codec list. Speech codec selection shall be made according to normal OoBTC procedures for interworking to external networks, and the selected codec and available codec list returned to the originating MSC server.

4.3.9

User interaction and in-band information

The MSC provided announcements and tones do not work, if the negotiated BC is a multimedia BC. Most often the inband information is connected to the originating UE but the same rules apply for the terminating UE. The following rules apply:

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

41

ETSI TS 123 172 V5.6.0 (2005-06)

1) Before sending the CONNECT message the originating MSC may insert in-band information if CALL PROCEEDING message indicates speech as the selected or preferred service. When fallback to multimedia occurs after CALL PROCEEDING but before CONNECT, the MSC may insert in-band information. 2) Before sending the CONNECT message the originating MSC shall not insert in-band information, if CALL PROCEEDING message indicates multimedia as the selected or preferred service. When fallback to speech occurs after CALL PROCEEDING but before CONNECT, the MSC shall not insert in-band information. 3) After the CONNECT message to/from the UE the originating/terminating MSC may insert in-band information, if the selected service is speech. Otherwise, the MSC shall not insert any in-band information. As an option, if the call is to be cleared, the MSC may perform an in-call modification to speech prior to the insertion of the inband information. 4) During the call setup phase the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected/preferred service received from the originating switch is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any in-band information during the call setup phase. 5) In the active phase of the call the terminating MSC, transit MSC and GMSC may insert in-band information, if the selected service is speech. Otherwise the terminating MSC, transit MSC and GMSC shall not insert any inband information. As an option, if the call is to be cleared, the terminating MSC, transit MSC or GMSC may perform an in-call modification to speech prior to insertion of the in-band information.

Lawful Interception

SCUDIF calls shall be monitored as for normal Circuit Switched data calls, for detailed requirements see 3GPP TS 33.106 [9].

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

42

ETSI TS 123 172 V5.6.0 (2005-06)

Annex A (informative): Change history


Change history
Date TSG # TSG Doc. CR Rev Subject/Comment Old New

2002-04 2002-06 NP#16


2002-12 2002-12 2002-12 2003-09 2003-09 2003-09 2003-09 2003-09 2003-12 2003-12 2004-03 2004-03 2004-03 2005-03 2005-06 NP#18 NP#18 NP#18 NP#21 NP#21 NP#21 NP#21 NP#21 NP#22 NP#22 NP#23 NP#23 NP#23 NP#27 CP#28

NP-020168
NP-020618 NP-020619 NP-020619 NP-030330 NP-030330 NP-030330 NP-030331 NP-030328 NP-030564 NP-030564 NP-040081 NP-040081 NP-040081 NP-050100 CP-050033

001 003 004 014 015 016 017 018 019 021 022 023 024 030 035

3 2 3 4 2 1 1 1 1 2 2 2 1

First draft of specification presented Approved at NP#16 and placed under change control
Lawful Interception For SCUDIF Mobile originating BC handling for SCUDIF calls Service Change Procedure Interaction with supplementary services in case of SCUDIF calls Repeat subscription checking in MO SCUDIF call HLR Interrogation for SCUDIF calls Callflows for Service change during the active state Interpretation of 'no BC-IE in CALL PROC/CONF messages' Corrections on HLR interrogation for SCUDIF calls CAMEL interactions with SCUDIF calls SCUDIF corrections for CAMEL interworking SCUDIF corrections for user interaction SCUDIF corrections for ISUP/BICC interworking Inclusion of Missing HLR Interrogation Parameter for SCUDIF Correction to figure 4.3.5.2/1, wrong Bearer Capability in MODIFY REJECT-message

1.0.0 1.0.0 2.0.0 5.0.0


5.0.0 5.0.0 5.0.0 5.1.0 5.1.0 5.1.0 5.1.0 5.1.0 5.2.0 5.2.0 5.3.0 5.3.0 5.3.0 5.4.0 5.5.0 5.1.0 5.1.0 5.1.0 5.2.0 5.2.0 5.2.0 5.2.0 5.2.0 5.3.0 5.3.0 5.4.0 5.4.0 5.4.0 5.5.0 5.6.0

ETSI

3GPP TS 23.172 version 5.6.0 Release 5

43

ETSI TS 123 172 V5.6.0 (2005-06)

History
Document history
V5.0.0 V5.1.0 V5.2.0 V5.3.0 V5.4.0 V5.5.0 V5.6.0 June 2002 December 2002 September 2003 December 2003 March 2004 March 2005 June 2005 Publication Publication Publication Publication Publication Publication Publication

ETSI