Opposite-MSC Anchor-MSC Target-MSC

Tr Tr
Inter-MSC HO

RNC RNC

DHT DHT

Inter-MSC HO

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.A.1
Opposite-MSC Anchor-MSC Target-MSC
Tr Tr

Tr
Inter-MSC HO

RNC RNC

DHT DHT

Inter-MSC HO

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.A.2
 Opposite-MSC Anchor-MSC Target-MSC

Tr Tr

Inter-MSC HO

RNC RNC

DHT DHT

In this case target MSC and anchor MSC need set transcoder, so an Inter-MSC HO
chor-MSC need inform-target MSC of the codec list supported by
UE

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.A.3
Opposite-MSC Anchor-MSC Target-MSC

Tr
Tr Tr
Inter-MSC HO

RNC RNC

DHT DHT

Inter-MSC HO

: AAL2 link

: Radio Link

ME : STM or AAL1 link

Tr : Transcoder

Figure 3.A.4
 OoBTC is successful

Opposite-MSC Anchor-MSC Target-MSC

or
Tr Tr

OoBTC is unsuccessful
RNC RNC

DHT DHT

Inter-MSC HO
In this case OoBTC is applied by anchor-MSC.
If OoBTC is successful, anchor-MSC dose not set transcoder.
If OoBTC is unsuccessful, anchor-MSC sets transcoder. Target-MS
C dose not set transcoder.

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.B.1
 Opposite-MSC Anchor-MSC Target-MSC
Tr Tr

Tr

RNC RNC

DHT DHT

In this case TrFO is not applied because Anchor MSC must set tran Inter-MSC HO
scoder whether TrFO is successful or not.

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.B.3
 Opposite-MSC Anchor-MSC Target-MSC

Tr Tr

RNC RNC

DHT DHT

Inter-MSC HO
In this case OoBTC is not applied by anchor-MSC because target
MSC must set transcoder whether TrFO is successful or not.

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.B.2
 Opposite-MSC Anchor-MSC Target-MSC

Tr Tr

RNC RNC

DHT DHT

Inter-MSC HO
In this case OoBTC is not applied by anchor-MSC because target
MSC must set transcoder whether TrFO is successful or not.

ME : AAL2 link

: Radio Link

: STM or AAL1 link

Tr : Transcoder

Figure 3.B.4
 Target RNC/BSS
ME Anchor RNC/BSS Anchor MSC Target MSC

RELOCATION REQUIRED - RANAP

PREPARE HANDOVER REQUEST - MAP(supported codec list)

Selection of codec

UMTS: RELOCATION REQUEST - RANAP

UMTS: RELOCATION REQUEST ACKNOWLEDGE- RANAP

PREPARE HANDOVER REQUEST ack- MAP(selected codec type)

Figure ４ .1 Target MSC selects transcoder used in target MSC

 Target BSS
ME Anchor BSS Anchor MSC Target MSC

GSM: HANDOVER REQUIRED - BSSMAP

UMTS: RELOCATION REQUIRED - RANAP

Additional new operation

Transcoder list request - MAP

Transcoder list request ack -MAP(supported transcoder list)

UMTS: Selection of codec

PREPARE HANDOVER REQUEST - MAP(Selected codec type)

UMTS: RELOCATION REQUEST - RANAP

RELOCATION REQUEST ACKNOWLEDGE- RANAP

PREPARE HANDOVER REQUEST ack- MAP

Figure ４ .2 Target MSC selects transcoder used in target MSC

 ME Anchor RNC Anchor MSC Target MSC Target RNC Target VLR

RELOCATION REQUIRED - RANAP

PREPARE HANDOVER REQUEST - MAP(supported codec list, note 1)

UMTS: Selection of codec

RELOCATION REQUEST - RANAP
Note1: supported codec list information should not be contained in the ca
se where AAL2 is used between anchor MSC and target MSC. MAP-Allocate-Handover-Number req
Note2: supported codec list information is not contained in the case where
AAL2 is used between anchor MSC and target MSC.
MAP-Allocate-Handover-Number resp.

RELOCATION REQUEST ACKNOWLEDGE- RANAP

PREPARE HANDOVER REQUEST ack- MAP(selected codec list, note 2)

IAM, note 4

ERQ
ECF Note 5

ACM
selected codec information, note 3

UMTS: RELOCATION COMPLETE - RANAP

HANDOVER COMMAND- UMTS RRC

Note 3: selected codec information is sent by the same message as the others(RRC/RANAP) or the message ind
ependent of the others (CC)
Note 4: Supported codec list may not be contained in IAM(BICC)
Note 5: This procedure is performed in the case where AAL2 is used between anchor MSC and target MSC

Fig 5.1 Codec negotiation procedure at inter MSC HO

 ME Anchor RNC Anchor MSC Target MSC Target RNC Anchor VLR
SETUP
MAP-Allocate-additional-call-Number req
MAP-Allocate-additional-call-Number resp
Selection of codec, note 2
odec list information should not be containe
ADDITIONAL CALL SETUP req. - MAP(supported codec list or selected codec information, note 1)
ec information should be contained in the cas
sed between anchor MSC and target MSC.
Selection of codec, note 3
SC selects codec where AAL2 is used betwe
d target MSC. RAB ASSIGNMENT REQUEST -RANAP
C selects codec where AAL2 is used betwee
target MSC. ERQ
dec information is not contained in the case ERQ or IAM (additional call number)
ed between anchor MSC and target MSC. ECF
are used in AAL2 environment and IAM/A
Note 5 ECF or ANM
M environment

RADIO BEARER SETUP

RADIO BEARER SETUP COMPLETE

RAB ASSIGNMENT RESPONCE-RANAP

ADDITIONAL CALL SETUP resp- MAP(selected codec type, note 4)

selected codec information, note 6

IAM toward opposite MSC

ACM from opposite MSC

ACM

Note 6: selected codec information is sent by the same message as the others(RRC/RANAP) or the message independent of the others (CC)

Fig 5.2 Codec negotiation procedure after inter MSC HO