A method for porting a mobile directory number from one wireless service provider to another

This invention relates to methods for porting a mobile directory number associated with a wireless terminal from a donor wireless service provider to a recipient wireless service provider.

When a subscriber first obtains wireless communications service from a wireless service provider, the wireless service provider assigns a mobile station identification number (MSIN) and a mobile directory number (MDN) to the wireless terminal of the subscriber, wherein the MSIN is a number used by the wireless service provider to uniquely identify the subscriber and/or the wireless terminal, and the MDN is the telephone number of the wireless terminal. If the subscriber thereafter desires to switch to a new wireless service provider, the subscriber must surrender the MDN assigned to its wireless terminal by the old wireless service provider, and be assigned a new MDN by the new wireless service provider. Changing MDNs can be extremely inconvenient, especially if the MDN is used for business. Therefore, it would be convenient if a subscriber could take or "port" a MDN from one wireless service provider to another. In other words, it would be advantageous if a subscriber didnot have to change the MDN when he or she switches wireless service providers.

Provisions for porting a mobile directory number are expected to be specified in the well-known ANSI Standard 41. Porting a subscriber's MDN requires the occurrence of at least five distinct events which are not required when the subscriber switches wireless service providers without porting the MDN. First, the new or recipient wireless service provider must inform the old or donor wireless service provider and a Number Portability Administrative Center (NPAC) of the intent to port the subscriber's MDN from the donor wireless provider, wherein the NPAC includes a database for associating subscribers' MDNs to location routing numbers (LRN) identified with wireless service providers currently providing wireless communications service to the subscribers.

Second, Number Portability Databases (NPDB) belonging to wireless service providers (including the recipient and donor wireless service providers) must be updated using the NPAC such that the porting subscriber's MDN is associated with the LRN identifying the recipient wireless service provider. Third, a new Mobile Station Identification Number (MSIN) must be assigned to the subscriber's wireless terminal by the recipient wireless service provider, and a record or entry for the subscriber must be created in a Home Location Register (HLR) belonging to the recipient wireless service provider, wherein the HLR comprises information about subscribers of the wireless service provider to which the HLR belongs, including information associating the newly assigned MSIN to the MDN being ported. Thus, the porting subscriber is now recognized by the recipient wireless service provider as one of its subscribers.

Fourth, the subscriber's wireless terminal must be re-programmed with the new MSIN assigned by the recipient wireless service provider such that the wireless terminal will respond to pages to the new MSIN. And lastly, the subscriber's entry in the donor wireless service provider's HLR must be deleted such that the ported subscriber is no longer a subscriber of the donor wireless service provider.

If all five events do not occur simultaneously, the wireless communication service to the subscriber can be interrupted. For example, if the NPDB is updated before the subscriber's record is created in the recipient wireless service provider's HLR, then a call to the subscriber's wireless terminal may not be completed because the recipient wireless service provider would not recognize the wireless terminal as belonging to one of its subscribers. Likewise, if the NPDB is updated before the subscriber's wireless terminal is re-programmed with the new MSIN from the recipient wireless service provider, then a call to the subscriber's wireless terminal may not be completed because the wireless terminal would not recognize the new MSIN as its own and respond to a page to the new MSIN.

Furthermore, the coordination of these five events is complicated by the fact that the disparate elements are owned and operated by different entities. For example, the donor wireless service provider owns and operates its NPDB and HLR, the recipient wireless service provider owns and operates its NPDB and HLR, and the subscriber owns and operates the wireless terminal. Therefore, a need exists for a method that enables a subscriber's mobile directory number to be ported from a donor wireless service provider to a recipient wireless service provider with minimum interruption to the subscriber's wireless communication service.

WO-A-9747153 discloses a method for porting a mobile directory number from a donor mobile network to a donee mobile network. An operator responsible for maintaining a central database is notified that a mobile directory number is being ported, and updates a centralized database accordingly. An application module within the centralized database then transmits a signal to the donor mobile network, which updates a database at the HLR therein to route calls identifying the ported mobile directory number to the donee mobile network. Accordingly, changes to the donor mobile network's database are originated and controlled from the central database. According to one aspect of this invention there is provided a method as claimed in claim 1.

According to another aspect of this invention there is provided a method as claimed in claim 6.

The present invention is a method for porting a mobile directory number of a subscriber from a donor wireless service provider to a recipient wireless service provider with minimum interruption to the subscriber's wireless communication service. In one embodiment, the present invention is accomplished by creating an entry for the wireless terminal in the recipient wireless service provider's home location register and a temporary pointer in the donor wireless service provider's home location register, wherein such temporary pointer will cause the donor wireless communication system to route or forward any call intended for the wireless terminal being ported to the recipient wireless communications system for completion in well-known fashion. When the porting process is complete, the temporary pointer is removed or deactivated in the donor wireless service provider's home location register. Advantageously, coordination of the porting process is controlled by the recipient wireless service provider resulting in minimum interruption to the subscriber's wireless communications service.

Brief Description of the Drawings

The features, aspects, and advantages of the present invention will become better understood with regard to the following description, appended claims, and accompanying drawings where: <ul id="ul0001" list-style="none"><li>FIG. 1 depicts a schematic diagram of wireless communications systems belonging to two different wireless service providers in which the present invention may be used; and</li><li>FIG. 2 depicts a flowchart illustrating the present invention.</li></ul>

Detailed Description

FIG. 1 depicts a schematic diagram of a Number Portability Administrative Center (NPAC) 107,and a donor wireless communications system 101, and a recipient wireless communications system 102. The donor and recipient wireless communications systems 101, 102 belong to a donor and a recipient wireless service provider, respectively. The donor wireless communications system is the home wireless communications system of a wireless terminal 110, i.e., wireless communications systems currently providing wireless communications services to a subscriber associated with the wireless terminal 110, whereas the recipient wireless communications system is the wireless communications system that will replace the donor wireless communications system as the home wireless communications system with respect to the wireless terminal 110. It should be understood that the terms "wireless communications system" and "wireless service provider" (and "subscriber" and "wireless terminal") may be used interchangeably at varying points throughout this application and, thus, should not be construed to limit the present invention in any manner.

Both donor and recipient wireless communications systems 101, 102 comprise the switches, base stations and other equipment necessary to provide wireless communications service to the wireless terminal 110. The geographic region serviced by the donor wireless communications system 101 can be coextensive, overlapping or disjoint with the geographic region serviced by the recipient wireless communications system 102. For ease of discussion, only those wireless communications system elements necessary to an understanding of the illustrative embodiment are depicted in FIG. 1.

Each wireless communications system 101, 102 includes a Number Portability Database (NPDB) 103, 104 and a Home Location Register (HLR) 105, 106. Each of the NPDBs 103, 104 includes a database for associating or mapping mobile directory numbers (MDN) to location routing numbers (LRN) identified with home wireless communications systems. Table 1 depicts a portion of a typical Number Portability Database. <tables id="tabl0001" num="0001"><table frame="all"><title>Table 1 -</title><tgroup cols="2" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="78.75mm" /><colspec colnum="2" colname="col2" colwidth="78.75mm" /><thead valign="top"><row><entry namest="col1" nameend="col2" align="center"><b>A Portion of a Typical Number Portability Database</b></entry></row><row><entry namest="col1" nameend="col1" align="center"><b>Mobile Directory Number</b></entry><entry namest="col2" nameend="col2" align="center"><b>Location Routing Number</b></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="left">...</entry><entry namest="col2" nameend="col2" align="center">...</entry></row><row><entry namest="col1" nameend="col1" align="left">717-234-9393</entry><entry namest="col2" nameend="col2" align="center">717-555-9393</entry></row><row><entry namest="col1" nameend="col1" align="left">717-234-9394</entry><entry namest="col2" nameend="col2" align="center">717-555-9393</entry></row><row rowsep="1"><entry namest="col1" nameend="col1" align="left">...</entry><entry namest="col2" nameend="col2" align="center">...</entry></row></tbody></tgroup></table></tables>

Like the NPDBs 103, 104, the NPAC 107 also includes a database for mapping MDNs to LRNs identified with home wireless communications systems. The difference between the NPAC 107 and the NPDBs 103, 104 is that the database of the former is used to periodically or sporadically update the databases of the latter. Additionally, the NPDBs 103,104 are generally used by service providers to route a call for a wireless terminal through the PSTN to the appropriate home wireless communications system of the wireless terminal.

Each of the HLRs 105, 106 comprises entries or records for subscribers of the wireless communications system to which the HLR belongs. Each entry includes the following information pertaining to a subscriber of the wireless communications system to which the HLR is a part a MDN, a mobile station identification number (MSIN) assigned to the subscriber by the wireless communications system, a status, and a LRN, if applicable, as will be described herein. The status and LRN information are new information typically not included in prior art home location registers. The status field can be populated with one of two values: active or inactive. When the status field contains an active value, it indicates that the associated wireless terminal belongs to a subscriber of the wireless communications system to which the HLR is a part. Thus, call processing should proceed normally and the value in the LRN field is irrelevant or ignored. By contrast, when the status field contains an inactive value, it indicates that the associated wireless terminal no longer belongs to a subscriber of the wireless communication system to which the HLR is a part. Such inactive value further indicates that the wireless terminal is in the process of being ported to another wireless communication system as identified by the LRN (i.e., the recipient wireless communications system identified by the LRN is now the home wireless communications system of the associated wireless terminal). Table 2 depicts a portion of a home location register. <tables id="tabl0002" num="0002"><table frame="all"><title>Table 2 -</title><tgroup cols="4" colsep="1" rowsep="1"><colspec colnum="1" colname="col1" colwidth="39.37mm" /><colspec colnum="2" colname="col2" colwidth="39.37mm" /><colspec colnum="3" colname="col3" colwidth="39.37mm" /><colspec colnum="4" colname="col4" colwidth="39.37mm" /><thead valign="top"><row><entry namest="col1" nameend="col4" align="center"><b>Some of the Fields in a Portion of HLR 106.</b></entry></row><row><entry namest="col1" nameend="col1" align="center"><b>Mobile Directory Number</b></entry><entry namest="col2" nameend="col2" align="center"><b>Mobile Station Identification</b></entry><entry namest="col3" nameend="col3" align="center"><b>Status</b></entry><entry namest="col4" nameend="col4" align="center"><b>Location Routing Number</b></entry></row></thead><tbody valign="top"><row><entry namest="col1" nameend="col1" align="center">...</entry><entry namest="col2" nameend="col2" align="center">...</entry><entry namest="col3" nameend="col3" align="center">...</entry><entry namest="col4" nameend="col4" align="center">...</entry></row><row><entry namest="col1" nameend="col1" align="center">324-859-9494</entry><entry namest="col2" nameend="col2" align="center">324-859-9494</entry><entry namest="col3" nameend="col3" align="center">Active</entry><entry namest="col4" nameend="col4" /></row><row><entry namest="col1" nameend="col1" align="center">324-859-9499</entry><entry namest="col2" nameend="col2" align="center">324-859-9499</entry><entry namest="col3" nameend="col3" align="center">Inactive</entry><entry namest="col4" nameend="col4" align="center">293-545-8353</entry></row><row><entry namest="col1" nameend="col1" align="center">324-747-5410</entry><entry namest="col2" nameend="col2" align="center">324-859-9502</entry><entry namest="col3" nameend="col3" align="center">Active</entry><entry namest="col4" nameend="col4" /></row><row rowsep="1"><entry namest="col1" nameend="col1" align="center">...</entry><entry namest="col2" nameend="col2" align="center">...</entry><entry namest="col3" nameend="col3" align="center">...</entry><entry namest="col4" nameend="col4" align="center">...</entry></row></tbody></tgroup></table></tables>

In an illustrative embodiment, the donor wireless communication system 101 currently provides wireless communications service to a subscriber's wireless terminal 110 (i.e., donor wireless communications system is the home wireless communications system of the wireless terminal 110). An entry or record exists in the donor HLR 105 for the subscriber. Such entry including a MDN, a MSIN assigned to the wireless terminal 110 by the donor wireless communications system 101, an active status and an empty or irrelevant LRN. The NPAC 107 will have an entry for the wireless terminal 110 associating the wireless terminal's MDN with the LRN of the donor wireless communications system 101.

FIG. 2 depicts a flowchart of the steps performed by the recipient wireless service provider in the illustrative embodiment, which enables a mobile directory number to be ported from the donor wireless service provider to the recipient wireless service provider with minimal interruption in a subscriber's wireless communications service.

In step 210, the recipient wireless communications system 102 transmits a message to the NPAC 107 indicating the intent of the subscriber of wireless terminal 110 to port its current MDN (assigned by the donor wireless service provider) to the recipient wireless service provider and a service change event (wherein the service change event specifies a date and a time when porting shall be completed, including updating the NPDBs of the recipient, donor and other wireless communications systems). Alternately, the service change event for completing the porting process can be determined by the NPAC 107 (and transmitted to the recipient wireless service provider). Upon receiving such message, the NPAC 107 will store the contents of the message and update its database to associate the LRN of the recipient wireless communications system 102 with the MDN of the subscriber's wireless terminal 110 when the service change event occurs.

In step 215, the recipient wireless communications system 102 transmits a message to the donor wireless communications system 101 indicating that the porting process of the MDN for the wireless terminal 110 to the recipient wireless communications system 102 will be completed upon occurrence of the service change event. Upon receipt of such message, the donor wireless communications system 101 will perform the following actions indicated in steps 220, 225 and 230 (not necessarily in that order).

In steps 220, 225 and 230, the donor wireless communications system 101 receives the message transmitted in step 215 and updates its HLR 105 for the wireless terminal 110. Specifically, the entry in the donor HLR 105 for the wireless terminal 110 will be modified such that the status and LRN fields will contain an inactive value and a LRN identifying the recipient wireless communications system 102, respectively.

At approximately the same time, the recipient wireless service provider creates an entry in its HLR 106 for the subscriber of wireless terminal 110, in step 235, wherein such entry includes a new MSIN assigned to the wireless terminal 110 by the recipient wireless service provider, the MDN, an active status, and an empty or irrelevant LRN. In step 240, the wireless terminal is re-programmed at approximately the same time with the new MSIN.

At this time (i.e., completion of steps 220,225,230,235), a temporary pointer to the recipient wireless service provider in the donor HLR 105 has been created. Such temporary pointer will indicate to the donor wireless communications system 101, during the inchoate porting process, to forward or route any call for the wireless terminal 110 to the recipient wireless communications system 102, thereby permitting such call to be completed by the recipient wireless communications system 102 in well-known fashion.

This point can be illustrated using the following scenario involving a call being made to the wireless terminal 110 via the PSTN. Service providers on the PSTN will use their NPDB to route the call to the wireless terminal 110. If the service change event has not yet occurred then the PSTN will route the call to the donor wireless communication system 101 (since the database of the service provider's NPDB will still be associating the LRN of the donor wireless communications system 102 with the MDN of the wireless terminal 110). Upon being routed to the donor wireless communications system 101, the donor wireless service provider will check the wireless terminal's MDN against its HLR 105 to determine whether the wireless terminal 110 is one of its subscribers. Upon checking the MDN of wireless terminal 110 against its HLR 105, the wireless service provider will see that the wireless terminal 110 is currently inactive and route or forward the call to the recipient wireless communications system identified by the LRN (in the donor's HLR 105) where call processing may be completed by the recipient wireless communications system 102 in well-known fashion.

If the service change event has occurred, then the service provider's NPDB will have an updated database associating the LRN of the recipient wireless communications system 102 with the MDN of the wireless terminal 110. Thus, the PSTN will know to route the call to the recipient wireless communications system 102 where call processing may be completed by the recipient wireless communications system 102 in well-known fashion.

When the service change event occurs, a number of actions will be performed, as specified in step 245. Specifically, the NPAC 107 will cause the NPDBs of the donor, recipient and other wireless communications systems to be updated such that the MDN of wireless terminal 110 will be associated with the LRN for the recipient wireless communications system 102. Additionally, the donor wireless service provider will cause the temporary pointer to recipient wireless communications system 102 to be deactivated or removed (e.g., the entry for the wireless terminal 110 in the donor's HLR 105 will be erased) signifying the completion of the porting process.

In another embodiment, a service change event is not provided by the recipient wireless communications system to either the NPAC 107 or the donor wireless communications system 101. In this embodiment, the NPAC 107 will inform the recipient wireless service provider when it has updated the NPDBs. Upon being informed of such an event, the recipient wireless service provider transmits a message to the donor wireless communications system 101 to remove the entry for wireless terminal 110 from its HLR 105.

It is to be understood that the above-described embodiments are merely illustrative of the invention and that many variations may be devised by those skilled in the art without departing from the scope of the invention. For example, the sequence of steps specified in the above description may be varied to achieve the same objective.