Method of supporting functionality for roamer port calls in...

Telecommunications – Radiotelephone system – Zoned or cellular telephone system

Reexamination Certificate

Rate now

  [ 0.00 ] – not rated yet Voters 0   Comments 0

Details

C455S422100, C455S433000, C455S560000, C455S445000

Reexamination Certificate

active

06424832

ABSTRACT:

BACKGROUND OF THE INVENTION
1. Technical Field of the Invention
This invention relates to telecommunication systems and, more particularly, to a method of supporting functionality for roamer port calls in a radio telecommunications network in which Number Portability (NP) is implemented.
2. Description of Related Art
The term Number Portability (NP) is utilized in connection with several types of subscriber service changes in which a subscriber may keep his original telephone number. For example, NP may refer to location portability which involves the capability to physically move (port) a subscriber's line connection from one switch to another while retaining the subscriber's original telephone number. NP may also refer to service provider portability which involves changing a subscriber's service from one service provider to another while retaining the subscriber's original telephone number. Or NP may refer to service type portability which involves changing the type of service (for example from POTS to ISDN) while retaining the subscriber's original telephone number. The present invention relates to service provider portability, but is applicable to location portability as well.
FIG. 1
is a simplified block diagram of an existing NP network configuration. All information about ported numbers is loaded from a central database system consisting of several Number Portability Administration Centers (NPACs)
11
distributed throughout the country. In each area, the NP data is downloaded from the NPAC
11
to a Local Service Management System (LSMS)
12
in order to populate network elements
13
-
15
deployed in the NP network with the ported subscriber data. The network elements
13
-
15
may comprise service control points (SCPs) and/or service transfer points (STPs). Each service provider may implement its own LSMS, and each LSMS is notified by the NPAC which numbers are ported. In this way, callers in different networks continue to dial the subscriber's original number, and each network is aware of the fact that the dialed number has been ported, and routes the call accordingly.
Each portable number is identified by its Numbering Plan Area Office Code (NPA-NXX), where the NPA relates to the area code, and the NXX relates to the exchange code. For example, in the telephone number 214-997-1234, the NPA is 214 and the NXX is 997.
The ported subscriber data downloaded from the NPAC
11
and LSMS
12
for a single subscriber is grouped into a single record called an NP subscription. The information contained within the NP subscription is the routing data necessary to route a call to the subscriber's new location or new service provider's switch. The information is categorized as Location Routing Number (LRN) data and Global Title Translation (GTT) data. GTT data is necessary for the routing of services such as Line Information Database service (LIDB), Custom Local Area Signaling Services (CLASS), Caller ID With Name (CNAM), and Interswitch Voice Messaging (ISVM). Upon reception of this information from the NPAC
11
, the LSMS
12
populates the LRN and GTT functions deployed in the network elements
13
-
15
with the relevant data elements.
NP has been implemented in wireline telecommunications networks, and
FIG. 2
is an illustrative drawing illustrating the steps involved when retrieving a Location Routing Number (LRN) in an existing wireline telecommunications network having NP service provisioning. At
21
, a calling subscriber dials the telephone number of a called subscriber
26
, for example 214-997-1234. The call is routed to an originating switch
22
. There are mechanisms set up within the originating switch to recognize that the NPA-NXX (214-997) has been made open for portability. Therefore, a lookup is performed in the NP database
23
of a SCP associated with the originating switch to retrieve a LRN corresponding to the dialed telephone number. If the NP database indicates that the dialed number is not ported, then the dialed number (or an empty response) is returned to the originating switch. If the dialed number has been ported, the LRN of a recipient destination switch
25
is returned. The originating switch then routes the call on the LRN at
24
to the destination switch
25
which handles the NXX in the retrieved number (e.g., 881). The dialed telephone number is also carried in signaling, for example in the Generic Address Parameter (GAP) of ISUP common channel signaling. The destination switch replaces the LRN with the dialed telephone number since the called subscriber
26
is still using the dialed telephone number. The call completely bypasses the 997 NXX switch
27
.
The Federal Communications Commission (FCC) has directed that NP be implemented in wireless radio telecommunications networks as well. Additional complexities are encountered in wireless networks due to the mobility of the subscribers. In wireless ANSI-41 networks today, a subscriber's Mobile Directory Number (MDN) and his mobile station's Mobile Identification Number (MIN) are generally identical. Several wireless features are built on the assumption of MIN-MDN equivalence. After the introduction of NP in wireless networks, a subscriber can keep his directory number as he changes from one service provider to another. However, when porting to an ANSI-41 network, the subscriber' mobile station is assigned a MIN that is generally different from his MDN. MINs are not portable in ANSI-41 networks, and each MIN series is tied to a particular home location register (HLR). Hence, features that assume MIN-MDN equivalence are impacted.
In particular, the implementation of NP impacts features such as functionality for roamer port calls delivered locally or after a location query to an HLR. Many operators support at least one roamer port in their networks. Roamer port numbers utilize two-stage dialing procedures to enable subscribers operating in the same local network to call each other without incurring long distance charges even though they are from different home networks. For example, if a subscriber from Montreal travels to Dallas and registers there, a calling party in Dallas can utilize the roamer port in Dallas to call the Montreal subscriber without incurring long distance charges. The calling party may be a mobile subscriber or someone calling from the PSTN. The roamer port belongs to the MSC of the Dallas service provider, with whom the Montreal subscriber's service provider has an agreement. The Dallas calling party dials the roamer port number for the roamer port mobile switching center (MSC) which is a local number. He then gets a second dial tone, and “over-dials” the Montreal subscriber's MDN. The roamer port number is defined in the Dallas MSC in which the Montreal subscriber is operating, and may serve the entire service area of the Dallas MSC or some sub-area thereof The roamer port number tells the Dallas MSC to page for the roaming mobile subscriber in the roamer port service area. In this manner, the Dallas calling party is able to call the Montreal subscriber who is roaming in the Dallas network without using long distance trunks or incurring long distance charges.
Paging in wireless networks is performed utilizing the MIN of the mobile station rather than the subscriber's dialed MDN. Before the implementation of NP, the MDN and MIN were equivalent, so the MSC owning the roamer port could page the called mobile station using the dialed MDN. With NP, however, the MDN and MIN become distinct and separate numbers if a number is ported, and the MSC that has the roamer port must translate the over-dialed MDN to a MIN in order to page the subscriber and deliver the call.
Additional complexity is added by the fact that in metropolitan areas, a single roamer port can be shared by several MSCs. In this case, the current functionality is such that the MSC having the roamer port first checks in its own records to see if the MIN (equivalent to the dialed MDN) is being served. If so, the called mobile station is paged

LandOfFree

Say what you really think

Search LandOfFree.com for the USA inventors and patents. Rate them and share your experience with other people.

Rating

Method of supporting functionality for roamer port calls in... does not yet have a rating. At this time, there are no reviews or comments for this patent.

If you have personal experience with Method of supporting functionality for roamer port calls in..., we encourage you to share that experience with our LandOfFree.com community. Your opinion is very important and Method of supporting functionality for roamer port calls in... will most certainly appreciate the feedback.

Rate now

     

Profile ID: LFUS-PAI-O-2887858

  Search
All data on this website is collected from public sources. Our data reflects the most accurate information available at the time of publication.