Dismiss
InnovationQ will be updated on Sunday, Oct. 22, from 10am ET - noon. You may experience brief service interruptions during that time.
Browse Prior Art Database

METHOD TO MAINTAIN MOBILITY MANAGEMENT DATA WHILE MIGRATING MOBILE SUBSCRIBER INFORMATION BETWEEN DISPATCH CONTROLLERS

IP.com Disclosure Number: IPCOM000009873D
Original Publication Date: 2000-May-01
Included in the Prior Art Database: 2002-Sep-25
Document File: 2 page(s) / 87K

Publishing Venue

Motorola

Related People

Patrick Baumann: AUTHOR [+3]

Abstract

In a large-scale dispatch system, it is common for a dispatch controller to become fully loaded with subscribers. At this point, a new controller can be added to the system. When the new controller is added, subscribers are moved from the existing controller(s) to the new controller to allow for additional expansion of fleets and groups on the existing machines. However, when this subscriber migration is performed, the new controller is not provided with the associated dynamic mobility management data.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 50% of the total text.

MOTOROLA

Technical Developments

METHOD TO MAINTAIN MOBILITY MANAGEMENT DATA WHILE MIGRATING MOBILE SUBSCRIBER INFORMATION BETWEEN DISPATCH CONTROLLERS

Patrick Baumann, Kirk Ingemunson, and Margaret Ng.

In a large-scale dispatch system, it is common for a dispatch controller to become fully loaded with subscribers. At this point, a new controller can be added to the system. When the new controller is added, subscribers are moved from the existing controller(s) to the new controller to allow for additional expansion of fleets and groups on the existing machines. However, when this subscriber migration is performed, the new controller is not provided with the associated dynamic mobility management data.

Due to the lack of dynamic information transfer, the system is no longer able to locate the Mobile Subscriber (MS). This causes a dispatch outage from an MS perspective until it reregisters.

In iDEN, the current fleet migration procedure moves subscribers' static provisioning information.

It is unable to transfer and dynamic information, such as location area, because the new controller (DAP) assigns a new temporary 'paging' m to the MS. Because the MS still has the original 'paging' ID, it cannot recognize the new m when the new controller attempts to page the MS. We would like

Motorola. Inc. 2000

to provide a way to establish communication between the new controller and the migrated MS without requiring user intervention. This article describes an implementation providing an automatic MS re~registration in order to synchronize the new controller and the migrated MS without requiring a system wide broadcast.

In the migration situation described above, the synchronization of the MS with respect to the Fi...