01-02 Procedures For Mobility Management

HUAWEI CSOFTX3000
Service Procedures
Contents
Contents
2 Procedures for Mobility Management...................................................................................2-1
2.1 Introduction to Mobility Management ..........................................................................................................2-2
2.2 Location Management...................................................................................................................................2-2
2.2.1 Common Messages for Location Management....................................................................................2-2
2.2.2 Location Management Procedures.......................................................................................................2-4
2.3 Handoff Management....................................................................................................................................2-6
2.3.1 Classification of Handoff .....................................................................................................................2-6
2.3.2 Intra-BSC Handoff...............................................................................................................................2-7
2.3.3 Inter-BSC Handoff Within the Same MSCe ........................................................................................2-8
2.3.4 Inter-MSCe Handoff ............................................................................................................................2-9
2.4 Roaming and Roaming Restriction .............................................................................................................2-17
2.4.1 Roaming and Basic Roaming Procedures ..........................................................................................2-17
2.4.2 Basic Roaming Restriction.................................................................................................................2-17
2.4.3 Enhanced Roaming Restriction..........................................................................................................2-18
2.4.4 Application of Roaming Restriction...................................................................................................2-18
Issue 03 (2007-06-18)
Huawei Technologies Proprietary
HUAWEI CSOFTX3000
Service Procedures
Figures
Figures
Figure 2-1 Location registration procedure ........................................................................................................2-4
Figure 2-2 Deregistration initiated by the MSCe ...............................................................................................2-5
Figure 2-3 Registered MS deactivation declared by the serving MSCe .............................................................2-6
Figure 2-4 Intra-BSC handoff.............................................................................................................................2-7
Figure 2-5 Inter-BSC handoff within the same MSCe .......................................................................................2-8
Figure 2-6 Relationship between the AMSCe, the SMSCe, and the TMSCe .....................................................2-9
Figure 2-7 Handoff-forward from AMSCe to SMSCe (TDM-based) ..............................................................2-10
Figure 2-8 Handoff-forward from the AMSCe to the SMSCe (IP-based)........................................................2-12
Figure 2-9 Handoff-back from the SMSCe to the AMSCe...............................................................................2-14
Figure 2-10 Handoff from serving MSCe to target MSCe through AMSCe ....................................................2-16
ii
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
2 Procedures for Mobility Management
Procedures for Mobility Management
About This Chapter

The following table lists the contents of this chapter.
Section
Describes
2.1 Introduction to Mobility

Management
The objective and classification of mobility management.
2.2 Location Management
The common messages and procedures for location

management.
2.3 Handoff Management
The classification of handoff and the procedure for

handoff.
2.4 Roaming and Roaming

Restriction
The classification and application of roaming restriction.
Issue 03 (2007-06-18)
2-1
HUAWEI CSOFTX3000
Service Procedures
2.1 Introduction to Mobility Management

The network is required to support and manage the mobility of an MS to:
z
Determine the current location of the MS.
Optimize the connection between the MS and the network.
According to different status of an MS, mobility management can be categorized into:

z
Location management
Handoff management
2.2 Location Management

It is necessary to confirm the current location of an idle MS. Location management helps the
MS to be connected to the calling party promptly.
Location management helps the network keep tracing and store the current location of an MS.
Location management guarantees the consistency of the location information stored in the
HLR, MSCe/VLR, and MS.
z
The HLR stores information on subscriber registration and location.
The VLR stores the information loaded from the HLR, including the subscriber
registration, location, and status.
The MSCe processes the flow of location registration and exchanges data with the VLR.
The MS stores information of its location area.
Location management flows in different cases adopt different protocols.

z
The location management between the HLR and the MSCe/VLR adopts the mobile
application part (MAP).
The location management between the MSCe/VLR and the MS adopts the base station
application part (BSAP) on the SCCP layer.
2.2.1 Common Messages for Location Management

Common messages involved in location management include:
2-2
Registration Notification
Qualification Request
Qualification Direction
MS Deactivation
Registration Cancellation
Bulk Deregistration
Unreliable Roaming Data Direction
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
Registration Notification
When an MS initiates a location registration, the MSCe/VLR sends an REGNOT message to
the HLR. This message serves to update the MS location information and private information
saved in the HLR.
Upon receiving the REGNOT message from the MSCe/VLR, the HLR returns a regnot
message.
Qualification Request
When an MS requests for a service, the necessary information (such as authentication data
and calling capabilities) may be absent. In this case, the MSCe/VLR sends the HLR a
QUALREQ message to apply for the absent information.
Upon receiving the QUALREQ message from the MSCe/VLR, the HLR returns a qualreq
message.
Qualification Direction
When MS private information (such as the name and activated/deactivated status of a
subscribed service) is changed in the HLR, the HLR sends the MSCe/VLR a QUALDIR
message to update the MS private information stored in the VLR.
Upon receiving the QUALDIR message from the HLR, the MSCe/VLR returns a qualdir
message.
MS Deactivation
The MSCe/VLR sets the MS to the deactivated state when:
z
The MS is powered off.
The MS is powered on but no activity (such as call origination/termination and periodic

location registration) is carried on.
In this case, the MSCe/VLR sends an MSINACT message to inform the HLR that the MS
changes to the deactivated state.
Upon receiving the MSINACT message from the MSCe/VLR, the HLR returns an msinact
message.
Registration Cancellation
The HLR sends a REGCANC message to instruct the previous serving MSCe/VLR to delete
information of an MS when the MS is roaming from the previous serving MSCe/VLR to a
new serving MSCe/VLR.
The HLR sends a REGCAN message to the current MSCe/VLR to instruct it delete the
subscriber data when the MS requests for deleting the subscriber data in the HLR.
Upon receiving the REGCANC message from the HLR, the MSCe/VLR returns a regcanc
message.
Bulk Deregistration
After the VLR is restarted, the subscriber information stored in the HLR can no longer
accurately indicate the MS location and status. In this case, the VLR sends a BULKDEREG
Issue 03 (2007-06-18)
2-3
HUAWEI CSOFTX3000
Service Procedures
message to instruct the HLR to delete the subscriber information relevant to this VLR. Thus,
the subscriber data in the VLR is consistent with that in the HLR.
Upon receiving the BULKDEREG message from the VLR, the HLR returns a bulkdereg
message.
Unreliable Roaming Data Direction

After the HLR is restarted, its related subscriber information stored in the VLRs is unreliable.
The HLR sends an NURELDIR message to instruct the VLR to delete the subscriber
information. Thus, the subscriber data in the HLR is consistent with that in the VLR.
Upon receiving the NURELDIR message from the HLR, the MSCe/VLR returns a nureldir
message.
2.2.2 Location Management Procedures

Location management procedures include:
z
Location Registration
Deregistration
MS Deactivation
Location Registration
Location registration takes place in the following cases:
z
An MS is powered on.
An MS moves beyond the paging coverage area of the previous location area.
The distance between the serving cell and the home cell reaches the threshold.
Some private parameters defined for successful call connections are changed.
An MS is powered off.
An MS timely initiates a periodic location registration.
The network side initiates a forced location registration.
Figure 2-1 shows the typical procedure for location registration.

Figure 2-1 Location registration procedure
BSC
MSCe2/VLR2
1.Location Updating
Request
HLR
MSCe1/VLR1
2.REGNOT
3.REGCANC
4.regcanc
6.Location Updating
Accept
2-4
5.regnot
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
1.
An MS initiates the location registration. The BSC sends a Location Updating Request
message to the MSCe (MSCe2).
2.
The MSCe (MSCe2) sends an REGNOT message to the HLR to which the MS belongs.
3.
The HLR sends a REGCANC message to instruct the previous visited MSCe/VLR
(MSCe1/VLR1) to remove all records of the MS.
4.
MSCe1/VLR1 sends a regcanc message to the HLR.
5.
The HLR sends a regnot message to MSCe2/VLR2.
6.
MSCe2/VLR2 sends a Location Updating Accept message to the BSC.
Deregistration
When an MS is powered off, or out of the network for long, the MSCe/VLR initiates the
deregistration flow.
Figure 2-2 shows the procedure for deregistration initiated by the MSCe.
Figure 2-2 Deregistration initiated by the MSCe
MSCe/VLR
HLR
1.MSINACT
2.msinact
1.
If an MS is powered off, deactivated, or out of the network for long, the MSCe/VLR
sends an MSINACT message to the HLR related to the MS, and removes all records of
the MS from the VLR.
2.
The HLR deactivates the location registration of the MS and returns an msinact message
to confirm the deregistration.
MS Deactivation
MS deactivation includes:
z
Registered MS deactivation declared by the serving MSCe
MS deactivation declared by the serving MSCe at location registration
MS deactivation reported by the HLR through an routreq message
Figure 2-3 shows the procedure for MS deactivation declared by the serving MSCe.
Issue 03 (2007-06-18)
2-5
HUAWEI CSOFTX3000
Service Procedures
Figure 2-3 Registered MS deactivation declared by the serving MSCe

MSCe/VLR
HLR
1.MSINACT
2.msinact
3.REGNOT
4.regnot
1.
After determining that a registered roaming MS is powered on but inactivated, the

serving MSCe/VLR marks this MS as deactivated and sends an MSINACT message to
the HLR.
2.
The HLR sets the MS to the deactivated state and returns an msinact message.
3.
When an activity from the MS is detected, the MSCe/VLR sends a REGNOT message to
the HLR.
The MSCe sending the message may not be the same MSCe that initially declared the
MS deactivation.
4.
The HLR sends a regnot message to the MSCe/VLR.
2.3 Handoff Management

With the help of handoff, an MS moving from one cell to another can maintain a conversation
or an access to the network.
During a conversation, the quality of service may deteriorate due to decreasing signal strength
or increasing interference. In this case, the connection is handed off to a cell with a stronger
signal.
Handoff takes place in the following cases:
z
An MS releases the air interface connection to the current serving base transceiver
station (BTS) and sets up a connection to the target BTS.
An MS is handed off to another traffic channel within the same BTS.
2.3.1 Classification of Handoff

In terms of frequency change or synchronization re-establishment, a handoff can be
categorized into the following types:
2-6
Hard handoff: An MS is required to change frequency or re-establish synchronization. It

applies to inter-BSC handoff and inter-MSCe handoff.
Soft handoff: An MS is not required to change frequency or re-establish synchronization.

It applies to inter-BTS handoff within a base station subsystem (BSS).
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
z
Softer handoff: It applies to inter-sector handoff within the same BTS. Softer handoff can
be carried out under BTS power control only.
According to different positions of an MS during the process, handoff can be categorized as

follows:
z
Intra-BTS handoff:
The handoff takes place in different sectors within the same BTS. It belongs to softer
handoff.
Intra-BSC handoff
The source cell and target cell in intra-BSC handoff are in the same BSC. It belongs to
soft handoff.
Inter-BSC handoff within the same MSCe

The source cell and target cell in this handoff are in the same MSCe but in different
BSCs. It belongs to hard handoff.
Inter-MSCe handoff
The source cell and target cell in this handoff are in different MSCes. It belongs to hard
handoff.
2.3.2 Intra-BSC Handoff

The BSC controls the intra-BSC handoff. The MSCe is not involved in the handoff process.
After the handoff is complete, the BSC sends a Handoff Performed message to inform the
MSCe of the successful handoff.
Intra-BTS handoff is carried out at the BSS side. It is not detailed in this section. The following
describes intra-BSC handoff, inter-BSC handoff within the same MSCe, and inter-MSCe handoff.
Figure 2-4 shows the procedure for intra-BSC handoff.

Figure 2-4 Intra-BSC handoff
MS
BSC
MSCe
1.Soft Handoff
2.Handoff Performed
1.
An MS and the BSC exchange a Soft Handoff message.
2.
The BSS informs the MSCe of a successful handoff through a Handoff Performed
message.
This message includes handoff causes and cells parameters.
Only when the soft handoff succeeds, the BSC sends the Handoff Performed message to the MSCe.
Issue 03 (2007-06-18)
2-7
HUAWEI CSOFTX3000
Service Procedures
2.3.3 Inter-BSC Handoff Within the Same MSCe

The source cell and target cell in this handoff are in the same MSCe but in different BSCs.
Figure 2-5 shows the procedure for inter-BSC handoff within the same MSCe.
Figure 2-5 Inter-BSC handoff within the same MSCe
BSC-O
MSCe
MGW
BSC-T
1.Handoff Required
2.Add Request
3.Add Reply
4.Handoff Request
5.Handoff Request Acknowledge
6.Handoff Command
7.Handoff Commenced
8.Handoff Complete
9.Modify Request
10.Modify Reply
11.Clear Command
12.Clear Complete
13.Subtract Request
14.Subtract Reply
1.
With the help of handoff, an MS moving from one cell to another can maintain a
conversation or an access to the network. In this case, after an MS reports that a stronger
signal is detected, the source BSC (BSC-O) sends a Handoff Required message to the
MSCe.
This message contains the codes of several recommended target cells in different BSCs
within the same MSCe.
2-8
2.
After the MSCe recognizes that the target cell is located in its BSC, it sends an Add
Request message to the media gateway (MGW) connecting to the target BSC (BSC-T).
3.
The MGW initiates bearer preparation and returns an Add Reply message.
4.
The MSCe sends BSC-T a Handoff Request message containing cell requirement.
5.
BSC-T sets up an access bearer with the MGW, assigns the radio resource and sends a
Handoff Request Acknowledge message to the MSCe.
6.
The MSCe constructs a Handoff Command message and sends it to BSC-O.
7.
BSC-O returns a Handoff Commenced message to inform the MSCe that the MS signals
attempt to migrate to a channel of BSC-T.
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
8.
BSC-T sends a Handoff Complete message to the MSCe. After that, the MS uses the
channel provided by the BSC-T to continue the service or the call.
9.
The MSCe sends the MGW a Modify Request message to require the MGW to change
the topology relationship between terminations in the context.
10. The MGW returns a Modify Reply message to the MSCe.

11. The MSCe sends a Clear Command message to instruct BSC-O to clear call resources
seized by the MS.
12. BSC-O returns a Clear Complete message.
13. The MSCe requests the MGW to release the bearer at the BSC-O side.
14. The MGW sends a Subtract Reply message to BSC-O to release the bearer resource at
the BSC-O.
The handoff is completed.
2.3.4 Inter-MSCe Handoff

z
Inter-MSCe handoff takes place when the source cell and target cell are in different
MSCes. Inter-MSCe handoff can be categorized into:
Handoff-Forward
Handoff-Back
Handoff-to-Third
The key terms are defined as follows:

z
AMSCe
During a call, the anchor MSCe (AMSCe) is the MSCe that first assigns a traffic channel
to a calling MS or a called MS. This MSCe keeps serving as the AMSCe in this call,
regardless of the number of handoffs that take place during the call.
SMSCe
During a call, the serving MSCe (SMSCe) is the MSCe that is providing a traffic channel
for an MS after each handoff. The SMSCe changes with each inter-MSCe handoff.
TMSCe
During a call, the tandem MSCe (TMSCe) is the MSCe that previously provided a traffic
channel for an MS after each handoff (except the first handoff). The TMSCe changes
with each inter-MSCe handoff during a call.
Figure 2-6 shows the relationship between the AMSCe, the SMSCe, and the TMSCe.
Figure 2-6 Relationship between the AMSCe, the SMSCe, and the TMSCe
AMSCe
First handoff-forward SMSCe
AMSC
TMSCe
SMSCe
Second handoff-forward
AMSCe
TMSCe
Issue 03 (2007-06-18)
TMSCe
SMSCe
Third handoff-forward
2-9
HUAWEI CSOFTX3000
Service Procedures
Handoff-Forward (TDM-Based)
Handoff-forward includes:
z
Handoff from the AMSCe to the SMSCe
Handoff from the TMSCe to the SMSCe
In a handoff-forward, the source MSCe and target MSCe are adjacent ones.
Figure 2-7 shows the procedure for the handoff-forward from the AMSCe to the SMSCe
(TDM-based).
Figure 2-7 Handoff-forward from AMSCe to SMSCe (TDM-based)
BSC-O
AMSCe
MGW-O
SMSCe
MGW-T
BSC-T
1.Handoff
Required
2.Add Request
3.Add Reply
4.FACDIR2
5.Add Request
6.Add Reply
7.Add Request
8.Add Reply
9.Handoff
Request
10.Handoff
Request
Acknowledge
11.facdir2
12.Handoff
Command
13.Handoff
Commenced
14.Handoff
Complete
15.MSONCH
16.Modify
Request
18.Clear
Command
19.Clear
Complete
17.Modify Reply
20.Subtract
Request
21.Subtract
Reply
1.
2-10
With the help of handoff, an MS moving from one cell controlled by the AMSCe to
another cell controlled by the SMSCe can maintain a conversation or an access to the
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
network. In this case, after an MS reports that a stronger signal is detected, the BSC-O
sends a Handoff Required message to the AMSCe.
2.
The AMSCe sends an Add Request message to the source MGW (MGW-O), and sets a
MAP circuit bearer connected to the target MGW (MGW-T).
3.
MGW-O sends an Add Reply message to the AMSCe.
4.
The AMSCe sends an FACDIR2 message to order the SMSCe to start a

handoff-forward.
5.
The SMSCe sends an Add Request message to instruct MGW-T to set up an MAP circuit
bearer connected to MGW-O.
6.
After the circuit bearer is set up, MGW-T sends an Add Reply message to the SMSCe.
7.
The SMSCe sends another Add Request message to instruct MGW-T to set up an A
interface circuit bearer connected to BSC-T.
8.
After the circuit bearer is set up, MGW-T sends an Add Reply message to the SMSCe.
9.
After the circuit is set up, the SMSCe sends a Handoff Request message to BSC-T.
10. BSC-T sends a reply message Handoff Request Acknowledge.

11. The SMSCe sends a facdir2 message to inform the AMSCe of the available traffic
channels for handoff.
12. The AMSCe sends a Handoff Command message to BSC-O.
13. BSC-O returns a Handoff Commenced message to inform the AMSCe that the MS
signals attempt to migrate to a channel of BSC-T.
14. After the MS signals migrate to a channel of BSC-T, BSC-T sends a Handoff Complete
message to the SMSCe. After that, the MS uses the channel provided by the BSC-T to
continue the service or the call.
15. The SMSCe sends an MSONCH message to inform the AMSCe of the successful
handoff.
16. The AMSCe sends a Modify Request message to request MGW-O to change topology
relationship between terminations in the context.
17. After modifying the bearer, MGW-O replies a Modify Reply message to the AMSCe.
18. The AMSCe sends a Clear Command message to BSC-O.
19. Upon receiving the Clear Command message, BSC-O clears call resources seized by the
MS and returns a Clear Complete message.
20. The AMSCe sends a Subtract Request message to request MGW-O to release the bearer
at the BSC-O side.
21. After releasing the bearer, MGW-O returns a Subtract Reply message to the AMSCe.
Handoff-Forward (IP-Based)
Figure 2-8 shows the procedure for the handoff-forward from the AMSCe to the SMSCe
(IP-based).
Issue 03 (2007-06-18)
2-11
HUAWEI CSOFTX3000
Service Procedures
Figure 2-8 Handoff-forward from the AMSCe to the SMSCe (IP-based)

BSC-O
AMSCe
MGW-O
SMSCe
MGW-T
BSC-T
1.Handoff
Required
2.Add Request
3.Add Reply
4.FACDIR2
5.INVITE
6.Handoff
Request
7.Handoff Request
Acknowledge
8.Add Request
9.Add Reply
10.Add Request
12.facdir2
11.Add Reply
13.200 OK
14.Modify
Request
15.Modify
Reply
16.200 OK
Acknowledge
17.Handoff
Command
18.Handoff
Commenced
19.Handoff
Compete
20.MSONCH
21.Subtract
Request
22.Subtract
Reply
23.Clear
Command
24.Clear
Complete
1.
2-12
With the help of handoff, an MS, moving from one cell controlled by the AMSCe to
another cell controlled by the SMSCe, can maintain a conversation or an access to the
network. In this case, after an MS reports that a stronger signal is detected, BSC-O sends
a Handoff Required message to the AMSCe.
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
This message contains the codes of several recommended target cells in different BSCs.
2.
After recognizing that the target cell is located in the BSC of the SMSCe, the AMSCe
sends an Add Request message to instruct MGW-O to assign a termination (T1) of the
RTP type connected to MGW-T.
3.
MGW-O returns an Add Reply message containing the SDP information of T1.
4.
The AMSCe sends an FACDIR2 message to order the target SMSCe to start a
handoff-forward.
5.
At the same time, the AMSCe sends an INVITE message to the SMSCe.
The message contains the IP address of T1 and the codec parameter. The messages
FACDIR2 and INVITE are associated through the vCIC parameter.
6.
Upon receiving the messages FACDIR2 and INVITE, the SMSCe sends a Handoff
Request message to BSC-T.
7.
BSC-T returns a Handoff Request Acknowledge message containing the IP address and
the codec capability of the termination at the BSC-T side (T2).
8.
The SMSCe sends an Add Request message to instruct MGW-T to assign a termination
connected to MGW-O (T3).
9.
MGW-T returns an Add Reply message containing the SDP information of T3.
10. The SMSCe sends an Add Request message to MGW-T to request a termination
connected to BSC-T (T4).
T3 and T4 are in the same Context (C1).
11. MGW-T returns an Add Reply message containing the SDP information of T4.
12. The SMSCe sends a facdir2 message to inform the AMSCe that traffic channels are
available and the handoff can be performed.
13. The SMSCe sends a 200 OK (INVITE) message to the AMSCe.
The message contains the IP address and the codec capability of T2.
14. Upon receiving the 200 OK message, the AMSCe sends a Modify Request message,
instructing MGW-O to update the bearer data to associate T1 and T2.
15. After the bearer is updated, MGW-O returns a Modify Reply message to the AMSCe.
16. The AMSCe sends the SMSCe an ACK message as the response to the 200 OK message.
17. Upon receiving the facdir2 message, the AMSCe sends a Handoff Command message to
BSC-O.
18. BSC-O sends a Handoff Commenced message to inform the AMSCe that the MS signals
19. After the traffic channel is set up between the MS and the SMSCe, BSC-T sends a
Handoff Complete message to the SMSCe. After that, the MS uses the channel provided
by the BSC-T to continue the service or the call.
20. The SMSCe sends an MSONCH message to inform the AMSCe of the successful
handoff.
21. The AMSCe sends a Subtract Request message to request MGW-O to release the bearer
at the BSC-O side.
22. After the bearer is released, MGW-O returns a Subtract Reply message to the AMSCe.
23. The AMSCe sends a Clear Command message to BSC-O.
MS and returns a Clear Complete message to the AMSCe.
Issue 03 (2007-06-18)
2-13
HUAWEI CSOFTX3000
Service Procedures
Handoff-Back
Handoff-back can be categorized into:
z
Handoff from the SMSCe to the AMSCe
Handoff from the SMSCe to the TMSCe
Figure 2-9 shows the procedure for the handoff-back from the SMSCe to the AMSCe. The
procedures for establishing, modifying, and releasing the bearer are not included.
Figure 2-9 Handoff-back from the SMSCe to the AMSCe
BSC-O
SMSCe
AMSCe
BSC-T
1.Handoff Required
2.HANDBACK2
3.Handoff Request
4.Handoff Request
Acknowledge
5.Handback2
6.Handoff Command
7.Handoff
Commenced
8.Handoff Complete
9.FACREL
10.Clear Command
11.Clear Complete
12.facrel
The procedure for inter-MSCe handoff-back over the A interface is the same as that for
inter-BSC handoff within the same MSCe. In addition, the handoff-back has four more
inter-MSCe messages.
1.
With the help of handoff, an MS moving from one cell controlled by the SMSCe to
another cell controlled by the AMSCe can maintain a conversation or an access to the
network. In this case, after an MS reports that a stronger signal is detected, BSC-O sends
a Handoff Required message to the SMSCe.
This message contains the codes of several recommended target cells in different BSCs.
2-14
2.
The SMSCe sends a HANDBACK2 message to order the AMSCe to start a

handoff-back.
3.
The AMSCe instructs the MGW to use available traffic channels to set up a bearer. After
the bearer is set up, the AMSCe sends a Handoff Request message to BSC-T.
4.
BSC-T sends a Handoff Request Acknowledge message to the AMSCe.
5.
The AMSCe sends the SMSCe a Handback2 message to start the handoff-back.
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
6.
The SMSCe sends a Handoff Command message to BSC-O.
7.
BSC-O sends a Handoff Commenced message to inform the SMSCe that the MS signals
8.
After the traffic channel is set up between the MS and the AMSCe, BSC-T sends a
Handoff Complete message to the AMSCe. After that, the MS uses the channel provided
by the BSC-T to continue the service or the call.
9.
Upon receiving a Handoff Complete message in the assigned traffic channel, the system
modify the bearer and change the flow direction between terminations in the context, and
sends the SMSCe an FACREL message to indicate success of the handoff.
10. The SMSCe sends a Clear Command message to BSC-O.

12. The SMSCe sends a facrel message to the AMSCe. The AMSCe then releases all trunk
circuits between MSCes.
Handoff-to-Third
Handoff-to-third can be categorized into:
z
Handoff from the serving MSCe (SMSCe-A) to the target MSCe (SMSCe-B) through the
AMSCe
Handoff from SMSCe-A to SMSCe-B through the TMSCe
Figure 2-10 shows the procedure for the handoff from SMSCe-A to SMSCe-B through the
AMSCe. The procedures for establishing, modifying, and releasing the bearer are not
included.
Issue 03 (2007-06-18)
2-15
HUAWEI CSOFTX3000
Service Procedures
Figure 2-10 Handoff from serving MSCe to target MSCe through AMSCe
BSC-O
SMSCe
SMSCe'
AMSCe
BSC-T
1.Handoff
Required
2.HANDTHIRD2
3.FACDIR2
6.facdir2
8.Handoff
Command
4.Handoff
Request
5.Handoff
Request
Acknowledge
7.handthird2
9.Handoff
Commenced
10.Handoff
Complete
11.MSONCH
13.Clear
Command
12.FACREL
14.Clear
Complete
15.facrel
The procedure for handoff-to-third over the A interface is the same as that for inter-BSC
handoff within the same MSCe. In addition, the handoff-to-third has seven more inter-MSCe
messages.
1.
After a basic inter-MSCe handoff, BSC-O sends a Handoff Required message to instruct
SMSCe-A to initiate a handoff.
2.
SMSCe-A recognizes that the target cell is located in the BSC of SMSCe-B and sends a
HANDTHIRD2 message to the AMSCe.
3.
After assigning a trunk circuit to SMSCe-B, the AMSCe sends an FACDIR2 message to
instruct SMSCe-B to start a handoff-to-third.
4.
SMSCe-B instructs the MGW to set up a bearer. After the bearer is set up, SMSCe-B
sends a Handoff Request message to BSC-T.
5.
BSC-T returns a Handoff Request Acknowledge message to SMSCe-B.
6.
SMSCe-B sends a facdir2 message to inform the AMSCe that traffic channels are
available and the handoff can be performed.
7.
The AMSCe sends a handthird2 message to SMSCe-A.
8.
SMSCe-A sends a Handoff Command message to BSC-O.
9.
BSC-O sends a Handoff Commenced message to inform the AMSCe that the MS signals
10. After the traffic channel is set up between the MS and the SMSCe-B, BSC-T sends a
Handoff Complete message to the SMSCe-B. After that, the MS uses the channel
provided by the BSC-T to continue the service or the call.
2-16
Issue 03 (2007-06-18)
HUAWEI CSOFTX3000
Service Procedures
11. Upon receiving signals from the MS in the assigned traffic channel, SMSCe-B sends an
MSONCH message to inform the AMSCe of the successful handoff.
12. The AMSCe sends an FACREL message to instruct SMSCe-A to release the trunk
circuit.
13. SMSCe-A sends a Clear Command message to BSC-O.
15. SMSCe-A returns and facrel message to require the AMSCe to release the trunk circuit.
2.4 Roaming and Roaming Restriction

Management on the area where a subscriber roams is called the roaming restriction. This
function is further classified into:
z
Basic Roaming Restriction
Enhanced Roaming Restriction
2.4.1 Roaming and Basic Roaming Procedures

From a subscriber point of view, roaming refers to the ability of the subscriber to enjoy
mobile service such as originating and terminating mobile calls and other mobile services
outside the home service area of the subscriber.
The system identification (SID) and network identification (NID) together provides evidence
to judge whether a roaming occurs. The SID is a global identification while the NID is
assigned by the network operator and configured on the BSC. The SID and NID are sent and
stored on the MS through the AIM interface.
Registration and deregistration of location are two key procedures in the roaming feature.
Registration of location allows the VLR of the serving MSCe to obtain the subscriber
information. When a location registration is initiated, it indicates that the MS is in the service
area of a certain MSCe and the HLR shall be informed. If the subscriber data does not exist in
the VLR of the serving MSCe, the HLR of the subscriber is required to provide the data and
conduct authentication.
Figure 2-1 and Figure 2-2 depict the location registration and deregistration procedures.
2.4.2 Basic Roaming Restriction

The HLR checks the roaming authority of a subscriber before location registration.
In basic roaming restriction, the serving MSCe sends the MSCeID to the HLR through the
location registration message when an MS enters a new MSCe area. The HLR then
determines whether the MS is allowed to roam in this MSCe.
This function restricts roaming of MSs in a relatively large area.
Issue 03 (2007-06-18)
2-17
HUAWEI CSOFTX3000
Service Procedures
2.4.3 Enhanced Roaming Restriction

Compared with basic roaming restriction, enhanced roaming restriction is more specific. With
this function, different subscriber groups are prohibited from roaming in different designated
local areas or cells.
According to their IMSI, MIN or MDN, subscribers with the same roaming attribute are
categorized into a Roaming-Restricted Subscriber Group. Besides, the system divides local
areas or cells into Roaming-Restricted Local Areas.
The procedure of enhanced roaming restriction is as follows:
1.
According to the MIN, IMSI, or MDN of a subscriber, the system determines the
Roaming-Restricted Subscriber Group to which the subscriber belongs.
2.
According to the local area or cell where the subscriber is located, the system determines
the corresponding Roaming-Restricted Local Area.
3.
The system determines whether this group is allowed to roam in this roaming-restricted
local area.
The service of enhanced roaming restriction helps operators to manage roaming areas of
mobile subscribers more flexibly.
2.4.4 Application of Roaming Restriction

Basic roaming restriction and enhanced roaming restriction are usually integrated in practical
operation.
When an MDN is required to determine the roaming authority, the system must determine
whether the whether the subscriber has the basic roaming authority. If not, the system call
origination and termination are rejected. If yes, the system determines whether the subscriber
has the roaming authority based on the advanced roaming procedure. If yes, the call
origination and termination are allowed.
2-18
Issue 03 (2007-06-18)

01-02 Procedures For Mobility Management

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

01-02 Procedures For Mobility Management

Caricato da

Copyright:

Formati disponibili

HUAWEI CSOFTX3000

Huawei Technologies Proprietary

Huawei Technologies Proprietary

2 Procedures for Mobility Management

Procedures for Mobility Management

About This Chapter

2.1 Introduction to Mobility

The objective and classification of mobility management.

2.2 Location Management

The common messages and procedures for location

2.3 Handoff Management

The classification of handoff and the procedure for

2.4 Roaming and Roaming

The classification and application of roaming restriction.

Huawei Technologies Proprietary

2 Procedures for Mobility Management

2.1 Introduction to Mobility Management

Determine the current location of the MS.

Optimize the connection between the MS and the network.

According to different status of an MS, mobility management can be categorized into:

2.2 Location Management

The HLR stores information on subscriber registration and location.

The MS stores information of its location area.

Location management flows in different cases adopt different protocols.

2.2.1 Common Messages for Location Management

Unreliable Roaming Data Direction

Huawei Technologies Proprietary

2 Procedures for Mobility Management

The MS is powered off.

The MS is powered on but no activity (such as call origination/termination and periodic

Huawei Technologies Proprietary

2 Procedures for Mobility Management

Unreliable Roaming Data Direction

2.2.2 Location Management Procedures

An MS timely initiates a periodic location registration.

The network side initiates a forced location registration.

Figure 2-1 shows the typical procedure for location registration.

Huawei Technologies Proprietary

2 Procedures for Mobility Management

MSCe1/VLR1 sends a regcanc message to the HLR.

The HLR sends a regnot message to MSCe2/VLR2.

MSCe2/VLR2 sends a Location Updating Accept message to the BSC.

Registered MS deactivation declared by the serving MSCe

MS deactivation declared by the serving MSCe at location registration

MS deactivation reported by the HLR through an routreq message

Huawei Technologies Proprietary

2 Procedures for Mobility Management

Figure 2-3 Registered MS deactivation declared by the serving MSCe

After determining that a registered roaming MS is powered on but inactivated, the

The HLR sends a regnot message to the MSCe/VLR.

2.3 Handoff Management

An MS is handed off to another traffic channel within the same BTS.

2.3.1 Classification of Handoff

Hard handoff: An MS is required to change frequency or re-establish synchronization. It

Soft handoff: An MS is not required to change frequency or re-establish synchronization.

Huawei Technologies Proprietary

2 Procedures for Mobility Management

According to different positions of an MS during the process, handoff can be categorized as

Inter-BSC handoff within the same MSCe

2.3.2 Intra-BSC Handoff

Figure 2-4 shows the procedure for intra-BSC handoff.

An MS and the BSC exchange a Soft Handoff message.

Huawei Technologies Proprietary