Handoff Hequest over SCCP

TSG-A
TITLE:
The Handoff Request message transfer over an SCCP connection

SOURCE: CWTS Dong Xiaolu CWTS, China +86 10 68094329 dongxiaolu@mail.ritt.com.cn

ABSTRACT: This contribution addresses the issues that in some cases the number of octets of the data fields in SCCP CR message is smaller than that of the Handoff Request message. RECOMMENDATION:

Review, discuss and adopt.

Notice
2002 CWTS. All rights reserved. The information contained in this contribution is provided for the sole purpose of promoting discussion within the 3GPP2 and its Organization Partners and is not binding on the contributor. The contributor reserves the right to add to, amend, or withdraw the statements contained herein. CWTS grants a free, irrevocable license to 3GPP2 and its Organization Partners to incorporate text or other copyrightable material contained in the contribution and any modifications thereof in the creation of 3GPP2 publications; to copyright and sell in Organizational Partners name any Organizational Partners standards publication even though it may include portions of the contribution; and at the Organization Partners sole discretion to permit others to reproduce in whole or in part such contributions or the resulting Organizational Partner s standards publication.

Introduction
According to the description in IOS4.x, the Handoff Request message shall be contained in the user data field of the SCCP Connection Request. The length of the user data field of the SCCP CR is limited and the message segmenting/re-assembling mechanism for this message is not available. But the size of the Handoff Request message is increasing. That results in a failure of the inter-BSC hard handoff procedure when the number of octets of the data fields in SCCP CR message is smaller than the number of octets of the Handoff Request message. So it is necessary to find a solution to solve this problem.

Proposed solution on IOS4.x

1 SCCP Connection Establishment During inter-BSC Handoff When the MSC decides to perform an inter-BS Handoff. MSC shall check whether the SCCP Connection Request message can transport the Handoff Request message. If the number of octets of the data fields in SCCP CR message is smaller than the number of octets of the Handoff Request message, MSC shall sent an SCCP Connection Request message without data field to establish a SCCP connection. Upon receipt of the SCCP Connection Request message without data field, The BS shall return an empty SCCP Connection Confirm message to the MSC. After the SCCP connection is established, The MSC shall send the SCCP DT1 message containing the BSMAP Handoff Request message (segmented if needed) to the BS. The diagram shows a successful SCCP connection establishment procedure during handoff when the SCCP DT1 message contains the BSMAP Handoff Request message.

BS SCCP Connection Request (without data field) SCCP Connection Confirm (without data field)

MSC

SCCP DT1 (Handoff Request) SCCP DT1 (segmented Handoff Request message if needed)

SCCP DT1 (Handoff Request Ack)

2 SCCP connection refusal during inter -BSC handoff The diagram shows an SCCP connection refusal during handoff when the SCCP DT1 message contains the BSMAP Handoff Request message.

BS SCCP Connection Request (without data field) SCCP Connection Confirm (without data field)

MSC

SCCP DT1 (Handoff Request) SCCP DT1 (segmented Handoff Request message if needed)

SCCP DT1 (Handoff failure)

SCCP DT1 (Clear Command)

Upon receipt of the SCCP DT1 message with Handoff failure, MSC shall initiate a normal connection clear procedure by sending a Clear Command message. 3 SCCP transfer of Handoff Messages Message Application Message Handoff Messages Handoff Request Handoff Request Acknowledge Handoff Failure f. May be used after an SCCP connection has been established Discriminator

SCCP Message CR , DT1 CCd, D T 1f DT1 , CREF

f e d f

BSMAP BSMAP BSMAP