17.04.2015 Views

Inter MSC Handover Call Flow - EventHelix.com

Inter MSC Handover Call Flow - EventHelix.com

Inter MSC Handover Call Flow - EventHelix.com

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>MSC</strong>_VLR <strong>Inter</strong>faces (Intra <strong>MSC</strong> <strong>Handover</strong> <strong>Call</strong> <strong>Flow</strong>)<br />

Highway GSM Coverage GSM<br />

Equipment<br />

GSM Mobile Bethesda Rockville <strong>MSC</strong> VLRs<br />

Mobile Bethesda Cell Bethesda BSC Rockville Cell Rockville BSC Maryland <strong>MSC</strong><br />

VLR<br />

<strong>EventHelix</strong>.<strong>com</strong>/EventStudio 2.5<br />

31-Dec-04 08:05 (Page 1)<br />

This call flow was generated with EventStudio 2.5 (http://www.<strong>EventHelix</strong>.<strong>com</strong>/EventStudio).<br />

How does a GSM mobile phone maintain a call even when moving from one cell to another?<br />

The calls are maintained by handing over a call from one cell to another. This call flow covers a simple case of call handover in GSM. Here a<br />

user has an active call and is moving from the Rockville Cell to the Bethesda Cell. As the user moves, the call will be handed over by the<br />

Rockville Cell to the Bethesda Cell.<br />

Copyright © 2000-2004 <strong>EventHelix</strong>.<strong>com</strong> Inc. All Rights Reserved.<br />

The GSM Mobile has an active call in the Rockville Cell.<br />

The user reaches the boundary between the Rocville Cell and Bethesda cell.<br />

Release call resources in Rockville BSC.<br />

1:BSSMAP HANDOVER REQUIREDThe BSC decides to request a handover. A<br />

Target Cells, Origin Cell list of target cells is provided to the <strong>MSC</strong>.<br />

The Bethesda Cell is included in the list of<br />

target cells.<br />

2:BSSMAP HANDOVER REQUEST<br />

The <strong>MSC</strong> passes on the handover request to<br />

Target Cells, Origin Cell<br />

the Bethesda BSC. (The Rockville BSC<br />

identified this BSC as as a target cell for<br />

handover.)<br />

3:T101 The <strong>MSC</strong>-VLR starts a timer to await the<br />

response from the Bethesda BSC.<br />

4:BSSMAP HANDOVER REQUEST ACKNOWLEDGE The Bethesda BSC includes the RR<br />

RR HANDOVER COMMAND<br />

HANDOVER COMMAND message as a<br />

payload in the HANDOVER REQUEST ACK<br />

that is sent back to the <strong>MSC</strong>. The RR<br />

HANDOVER COMMAND will be delivered to<br />

the mobile via the Rockville BSC.<br />

5:T101 The <strong>MSC</strong> has heard back from the<br />

destination BSC, thus the T101 timer is<br />

stopped.<br />

6:BSSMAP HANDOVER COMMANDThe <strong>MSC</strong> delivers the handover <strong>com</strong>mand<br />

RR HANDOVER COMMAND to the Rockville BSC. This <strong>com</strong>mand<br />

encapsulates the RR HANDOVER<br />

COMMAND from the destination BSC.<br />

7:T102 T102 is started to track the <strong>com</strong>pletion of<br />

the handover.<br />

8:BSSMAP HANDOVER DETECTED<br />

The BSC informs the <strong>MSC</strong> that the<br />

handover has been detected. At this point<br />

the <strong>MSC</strong> can switch the voice path.<br />

Switch <strong>Call</strong> to new Path The <strong>MSC</strong> switches the voice path.<br />

9:BSSMAP HANDOVER COMPLETE<br />

The BSC forwards the handover <strong>com</strong>pletion<br />

event to the <strong>MSC</strong>.<br />

10:T102 <strong>Handover</strong> has been <strong>com</strong>pleted, so T102 is<br />

stopped.<br />

11:BSSMAP CLEAR COMMAND <strong>Call</strong> release has been <strong>com</strong>pleted, now the<br />

RR connection is released by the <strong>MSC</strong>.<br />

12:BSSMAP CLEAR COMPLETE The BSS informs the the <strong>MSC</strong> that the RR<br />

connection has been released.


<strong>MSC</strong>_VLR <strong>Inter</strong>faces (<strong>Inter</strong> <strong>MSC</strong> <strong>Handover</strong> <strong>Call</strong> <strong>Flow</strong>)<br />

Highway<br />

GSM Coverage<br />

<strong>EventHelix</strong>.<strong>com</strong>/EventStudio 2.5<br />

GSM Mobile Bethesda Rockville<br />

Mobile Bethesda Cell Bethesda BSC Bethesda Rockville<br />

<strong>MSC</strong> VLR <strong>MSC</strong> VLR Rockville BSC Rockville Cell 31-Dec-04 08:05 (Page 2)<br />

This call flow was generated with EventStudio 2.5 (http://www.<strong>EventHelix</strong>.<strong>com</strong>/EventStudio).<br />

How does a GSM mobile phone maintain a call even when moving from a cell controlled by one <strong>MSC</strong> to a cell controlled by a different <strong>MSC</strong>?<br />

The calls are maintained by handing over the call from the source <strong>MSC</strong> to the target <strong>MSC</strong>. The MAP/E protocol is used to manage the<br />

interactions between the source <strong>MSC</strong> and the target <strong>MSC</strong>.<br />

In this example, a user has an active call and is moving from the Rockville Cell to the Bethesda Cell. As the user moves, the call will be handed<br />

over by the Rockville Cell to the Bethesda Cell. The Bethesda cell and the Rockville cell are controlled by different <strong>MSC</strong>s, thus an <strong>Inter</strong>-<strong>MSC</strong><br />

hardover will be performed from the Rockville <strong>MSC</strong> to the Bethesda <strong>MSC</strong>.<br />

Copyright © 2000-2004 <strong>EventHelix</strong>.<strong>com</strong> Inc. All Rights Reserved.<br />

The GSM Mobile has an active call in the Rockville Cell.<br />

The user reaches the boundary between the Rocville Cell and Bethesda cell.<br />

1:BSSMAP HANDOVER REQUIRED<br />

Target Cells, Origin Cell<br />

The BSC decides to request a<br />

handover. A list of target cells is<br />

provided to the <strong>MSC</strong>. The Bethesda Cell<br />

is included in the list of target cells.<br />

2:MAP/E PERFORM HANDOVER<br />

This is an inter <strong>MSC</strong> handover, so pass<br />

Target Cells, Origin Cell<br />

the handover request to the target <strong>MSC</strong><br />

via a MAP/E message.<br />

3:T101 The <strong>MSC</strong>-VLR starts a timer to await<br />

the response from the Bethesda BSC.<br />

4:BSSMAP HANDOVER REQUEST<br />

Target Cells, Origin Cell<br />

5:BSSMAP HANDOVER REQUEST ACKNOWLEDGE<br />

RR HANDOVER COMMAND<br />

The <strong>MSC</strong> passes on the handover<br />

request to the Bethesda BSC. (The<br />

Rockville BSC identified this BSC as as<br />

a target cell for handover.)<br />

The Bethesda BSC includes the RR<br />

HANDOVER COMMAND message as a<br />

payload in the HANDOVER REQUEST<br />

ACK that is sent back to the <strong>MSC</strong>. The<br />

RR HANDOVER COMMAND will be<br />

delivered to the mobile via the Rockville<br />

BSC.<br />

6:MAP/E PERFORM HANDOVER ACK<br />

Pass the handover request<br />

RR HANDOVER COMMAND<br />

acknowledgement from the target <strong>MSC</strong><br />

to the source <strong>MSC</strong>.<br />

7:T101 The <strong>MSC</strong> has heard back from the<br />

destination <strong>MSC</strong>, thus the T101 timer<br />

is stopped.<br />

8:BSSMAP HANDOVER COMMAND<br />

RR HANDOVER COMMAND<br />

The <strong>MSC</strong> delivers the handover<br />

<strong>com</strong>mand to the Rockville BSC. This<br />

<strong>com</strong>mand encapsulates the RR<br />

HANDOVER COMMAND from the<br />

destination BSC.<br />

9:T102 T102 is started to track the <strong>com</strong>pletion<br />

of the handover.<br />

10:BSSMAP HANDOVER DETECTED<br />

The BSC informs the <strong>MSC</strong> that the<br />

handover has been detected. At this<br />

point the <strong>MSC</strong> can switch the voice<br />

path.<br />

Switch <strong>Call</strong> to new Path<br />

The <strong>MSC</strong> switches the voice path.<br />

11:BSSMAP HANDOVER COMPLETE<br />

12:MAP/E SEND END SIGNAL<br />

The BSC forwards the handover<br />

<strong>com</strong>pletion event to the <strong>MSC</strong>.<br />

Initiate call release at the source <strong>MSC</strong><br />

for the handover.


<strong>MSC</strong>_VLR <strong>Inter</strong>faces (<strong>Inter</strong> <strong>MSC</strong> <strong>Handover</strong> <strong>Call</strong> <strong>Flow</strong>)<br />

Highway<br />

GSM Coverage<br />

<strong>EventHelix</strong>.<strong>com</strong>/EventStudio 2.5<br />

GSM Mobile Bethesda Rockville<br />

Mobile Bethesda Cell Bethesda BSC Bethesda Rockville<br />

<strong>MSC</strong> VLR <strong>MSC</strong> VLR Rockville BSC Rockville Cell 31-Dec-04 08:05 (Page 3)<br />

Release call resources in Rockville BSC.<br />

13:T102 <strong>Handover</strong> has been <strong>com</strong>pleted, so T102<br />

is stopped.<br />

14:BSSMAP CLEAR COMMAND<br />

15:BSSMAP CLEAR COMPLETE<br />

16:MAP/E SEND END SIGNAL RESPONSE<br />

<strong>Call</strong> release has been <strong>com</strong>pleted, now<br />

the RR connection is released by the<br />

<strong>MSC</strong>.<br />

The BSS informs the the <strong>MSC</strong> that the<br />

RR connection has been released.<br />

Signal the end of the call.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!