System and method for controlling and monitoring a wireless roaming call.

(54) Title: SYSTEM AND METHOD FOR CONTROLLING AND VERIFYING A CALL FOR WIRELESS TELEPHONY OUTSIDE THE SERVICE AREA.

(54) Title: SYSTEM AND METHOD FOR CONTROLLING AND MONITORING A WIRELESS ROAMING CALL.

(57) Summary

The present invention refers to a network solution system for communication outside the service area (100), the system includes a server for communication outside the service area (116), a national location register (112) and a unit remote switching number 800 (8130). The system is integrated with a standard SS7 telecommunications network and is also coupled to a meter based on a call and billing control platform that allows limited registered wireless credit subscribers to place and receive calls, to locate and receive calls when communication outside the area. service is far from the Home provider's network. The invention verifies that the wireless subscriber's accounting balance is sufficient to place or receive the call, translates the accounting balance in minutes to speak, and verifies the call for the duration of the conversation. The network solution system for communication outside the service area is also operable such that if the wireless telephone subscriber exceeds the accounting balance, the system drops the call in the first negative minute and immediately decreases the wireless telephone subscriber's account. If the call is disconnected before the balance sheet is exhausted, the invention immediately decrements the wireless telephone subscriber's account and releases the link. The out-of-service network communication solution system is designed to mitigate a home provider's exposure to credit risk when providing out-of-service communication services to credit limited subscribers.

(57) Abstract

The invention is a Roaming Solution network system (100), the system including a Roaming Server (116), a National Location Register (112), and an 800 number Remóte Switching Unit (130). The system is integrated with a standard SS7 type telecommunications network and further coupled to an account based billing and cali control platform that allows registered wireless credit limited subscribers to place and receive calis when roaming outside of their Home Provider s network. The invention verifies that the wireless subscriber s account balance is sufficient to place or receive the cali, translates the account balance into talk minutes, and monitors the cali for talk duration. The Roaming Solution network system is further operable such that if the wireless subscriber exceeds the available account balance, the system tears down the cali in the first negative minute and immediately decrements the wireless subscriber s account. If the cali is disconnected prior to the account balance being depleted, the invention immediately decrements the wireless subscriber s account and releases the trunks. This Roaming Solution network system is designed to mitígate a Home

Provider s exposure to credit risk when providing roaming Services to credit limited subscribers.

(12) INTERNATIONAL APPLICATION PUBLISHED VNDERTHE PATENT C00PERAT10N TREATY (PCT) (19) World Intellectual Property Organized by International Bureau (43) International Publication Date 7 September 2001 (07.09.2001)

<img file="MXPA02008463A_D0001.tif" />

PCT (10) International Publication Number

WO 01/65872 Al (51) International Patcut Ciassificatiou '': H04Q 7/20,

H04M 11/00, 03/15 (21) International Application Number: PCT / US01 / 06285 (22) International Filing Date: 27 February 2001 (27.02.2001) (81) Designated States (national): AE, AQ, AL, AM, AT, AU, ΛΖ, BA, BB, BG, BR, BY, BZ, CA, CH, CN, CR, CU, CZ, DE, DK, DM, DZ, EE, ES, Fl, ÜB, ÜD, GE, Gil, GM, HR, HU, ID, IL, IN, IS, JP, KE, KG, KP, KR, KZ, LC, LK, LR, LS, LT, LU, LV, MA, MD, MG, MK, MN, MW, MX, MZ, NO, NZ, PL, PT, RO, RU, SD, SE, SG, SI, SK, SL, TJ, TM, TR, TT, TZ, UA, UG, UZ, VN, Y1J, ZA, ZW.

(25) Filing Language:

(26) Publication Langunge:

English

F.nglish (30) Priority Data:

60 / 186,067 29 February 2000 (29.02.2000) US (84) Designate *) States (regional): ARIPO patent (GH, GM, KE, LS, MW, MZ, SD, SL, SZ, TZ, UG, ZW) , Eurasian patent (AM, ΑΖ, BY, KG, KZ, MD, RU, TJ, TM), European patent (AT, BE, CH, CY, DE, DK, ES, Fl, FR, GB, GR, IE, TT, LU, MC, NI., PT, SE, TR), OAPT patent (BF, Bl, CF, CG, □, CM, GA, GN, GW, ML, MR, NE, SN, TD, TG).

(71) Applicant: NATIONAL TELEMANAGEMENT CORPORATION fUS / US]; Suite 212, 8828 Stemmons Freeway, Dallas, TX 75247 (US).

(72) Inventor: HANSON, Daniel, A .; 6504 Bob-O-Link, Dal = las, TX 75214 (US).

Publis hed:

- with internalional search report

For two-leiier codes and oíher abbreviations, refer lo Ihe Cuidance Notes on Codes andAbbreviationsappearing at the beginning of each regular issue of the PCI 'Cazetle.

(74) Agent: STALLION, Mark, E .; Blackwell Sanders Peper Martin LLP, Suite 2400, 720 Olive Street, St. Louis, MO 63101 (US).

= (54) Title: SYSTEM AND MET1IOD FOR CONTROLLING AND MONITOR1NG A WIRELESS ROAMING CALL

<img file="MXPA02008463A_D0002.tif" />

WO 01/65872 Al (57) Abstract: The invention is a Roaming Solution network system (100), the system including a Roaming Server (116), a National Location Register (112), and an 800 number Remóte Switching Unit (130) . The system is integrated with a standard SS7 type telecommunications network and further coupled to an account based billing and cali control platform that allows registered wireless credit limited subscriben to place and receivc calis when roaming outside of their Home Provider's network. The invention veriftes that the wireless subscriber's account balance is sufficient to place orreceive the cali, translates the account balance into talk minutes, and monitors the cali for talk duration. The Roaming Solution network system is further operable such that if the wireless subscriber exceeds the available account balance, the system tears down the cali in the firsl negative minute and immedialely decremenis the wireless subscriber's account. íf the cali is disconnectcd prior to the account balance being dcplctcd, the invention immediately decrements the wireless subscriber's account and releases tile trunks. This Roaming Solution network system is designed mitígate a Home Provider's expostre to crcdit risk when providing roaming Services to credit limited subscribers.

SYSTEM AND METHOD FOR CONTROLLING AND MONITORING A CALL FOR

WIRELESS TELEPHONY OUTSIDE THE SERVICE AREA (1) Field of the Invention

This invention relates generally to the field of telecommunications, and more particularly to a telecommunication system for controlling and monitoring roaming wireless calls for real-time billing, especially roaming wireless calls that have credit restrictions.

(2) Background of the Art

The telecommunications industry has been transformed into a wireless telecommunications environment with the introduction of wireless telecommunications services (referred to as wireless or simply wireless services). This transition has resulted in an increase in the large number of wireless service providers who seek to provide the service to the increasing number of service subscribers nationally, as well as globally. Providing wireless service subscribers with the ability to make and receive wireless communications regardless of geographic location is not only a technical challenge, but REF: 141748 also requires a complex network and infrastructure. A subscriber to the wireless service may wish to perform or receive wireless telecommunications when geographically outside the subscriber's home network. The home network is the network or region served by the wireless service provider's network with which the subscriber has entered into a contract. However, the wireless service provider also wishes to provide telecommunication services to the subscriber even when the subscriber is geographically outside the home network, usually referred to as roaming outside the home network or simply roaming. The subscriber must be able to communicate outside the home network in order for the roaming solution to occur.

However, providing this service creates a credit risk for the provider because calls that originate or are provided to the roaming subscriber while roaming on a local roaming provider network cannot be controlled or monitored in time. actual for a billing-based account. Due to this potential network or credit exposure, wireless service providers in many cases refuse to provide roaming services to many subscribers in order to mitigate exposure to credit risk. Other solutions to mitigate exposure to credit risk include credit card billing, various pre-payment systems including the applicant-patented system that provides roaming services for roaming subscribers' not registered via pre-pay only to transmit calls.

When the subscriber is outside the home network, the subscriber's computer searches the local provider's network (local relative to a roaming subscriber, the local provider may be referred to as the roaming provider or provider supplying a service) through which you can communicate. This is called roaming. The subscriber's computer roams until a network provider for which communications can be established is found. The large number of providers and the growing number of subscribers combined with the complex infrastructure make network roaming a key part of successfully providing wireless services nationally or globally.

Wireless communication networks and services should provide a roaming solution for Roaming Registration Notification (Regnot) as well as roaming solutions for wireless communications originating from the wireless roaming subscriber and for incoming communications directed to the wireless roaming subscriber. There are several wireless telecommunication interconnection strategies that are designed to provide the service to a wireless roaming subscriber. A given wireless provider will supply the service to both locally based subscriber traffic, especially its own subscribers, however it will also provide roaming service to subscribers who are not their own and who are roaming within the local provider's network ( that is, a wireless roaming subscriber).

As stated above, wireless subscribers want to be able to use their mobile phones regardless of their position and this subscriber wants to have induced wireless providers to negotiate contracts with each other to provide roaming services with their subscribers when they are outside the provider's network wireless base. A roaming subscriber is considered when the subscriber's mobile station or mobile phone requires service on a local network which is operated by a different wireless provider than the one the subscriber has contracted with. When the subscriber's mobile station is in roaming mode, the subscriber is provided with a signal indicative of the roaming condition and is typically displayed on the mobile phone screen as a result of a system identification comparison (SID, Subscribed system which is stored in the mobile station (mobile phone) with the SID of the local wireless provider's system which provides a broadcast service from the local base station. This warns the subscriber of the mobile station that the service being provided is generating roaming charges. However, the subscriber typically has no visibility into the actual roaming costs since contact between various wireless providers may vary. Therefore, a subscriber may accumulate roaming costs that are higher than he anticipates.

A typical scheme is when a wireless subscriber's mobile station or mobile phone enters a geographic area outside of its base network that prevents it from obtaining service from the base provider's communications network. The mobile station or mobile phone registers with the local provider's wireless communication system (roaming provider) by providing identification information to the local provider's mobile switching center (MSC). This identification was called Regnot. The visitor location record (VLR) that joins the local provider's MSC has a database of information that identifies other providers with whom it has billing arrangements so that the local provider has agreed to provide roaming services to roaming subscribers of the other provider (roaming subscriber base provider). The VLR maintains records of all services that are provided to wireless roaming subscribers. If the other provider or the roaming subscriber's base provider registers with the VLR of the local provider, then the VLR will contact the base location record (HLR) of the subscriber's base provider Roaming to obtain the profile information of the calling party for the roaming subscriber who has roaming in the local or roaming provider's network. The wireless communication system of the local wireless provider will then seek authorization to provide the service to the roaming subscriber who has performed the roaming process within the local wireless provider's network. The HLR of the base provider will tell the VLR of the local provider if whether or not you provide roaming services. Once roaming services are allowed to be provided, all calls originating from the roaming subscriber are completed by the MSC and RSU of the local provider. The problem is that the base provider has no control over the call originating from the roaming calling party. This situation generates a credit risk with the base provider. For this, the base providers have chosen not to allow the provision of roaming services for some subscribers who are not registered with the roaming provider's VLR. Please note that in the telecommunications industry, when one refers to a provider's mobile switching center or a switching center or a mobile switch or simply a switch, it usually implies that an HLR and VLR are included, as well as other elements typical needed. For the purpose of this document, when these terms are used, ~ is implied to be included in HLR and VLR.

Provision of a call to the roaming subscriber, when roaming on a local provider or roaming network, may be carried out by current wireless telecommunication infrastructure, however, once the call is ended at the local provider's MSC , the base provider has no means to control and monitor the call. Again, base providers have chosen not to allow roaming services for some subscribers and have not yet registered with the roaming provider's VLR.

If the roaming subscriber is identified in the VLR of the local provider, the local wireless provider's system will send a request to provide service to the base wireless provider's system controller which contains a database called HLR. The HLR contains user profile information comprising an authorization to allow roaming, user characteristics and information about anticipated roaming costs based on the various contractual agreements that are carried out. The base wireless provider system will then provide information back to the local wireless provider system, including authorization to allow roaming, as well as other features.

The Applicant has reduced the practice and implemented proprietary technology that provides real-time call management 'of a call originating from an unregistered prepaid roaming subscriber which solves part of the problem discussed above, specifically the origin a call from a pre-paid roaming calling party, not registered. This is an option for those subscribers where the base provider has chosen not to register with the local provider for the provision of roaming services. With this technology, any roaming subscriber with unregistered prepayment (a subscriber that the base provider has chosen not to register with the VLR of the local provider but who is a prepaid subscriber) can originate a prepaid call. For example, the US patent No. 6,029,026, issued February 22, 2000, to the present applicant, describes a network that provides such a service. This patent describes and claims a telecommunication system that includes a prepaid call management platform which is coupled and located in conjunction with a telecommunication MSC of the local roaming provider. The system also includes a customer database coupled to the pre-paid call management platform to store customer data for a pre-payment. The system provides a method for constant call management of all prepaid calls with unregistered roaming call processing capabilities. The method includes the steps of recognizing an unregistered roaming call at the roaming provider's telecommunications MSC and rotating the unregistered roaming call to a prepaid call management platform coupled to the telecommunications MSC. The system allows unregistered roaming calls to be processed locally. This system provides a pre-paid call management account, however this technology requires the roaming or local provider to have additional communicable hardware (hardware) infrastructure and to be located in conjunction with the roaming provider's MSC . Additional infrastructure required includes a remote switching unit (RSU) to end pre-paid roaming calls. Additionally, this proprietary system provides call origination services and not call provisioning services (calls that are routed to the subscriber while roaming while on a local network).

The Regnot of the roaming subscriber that is presented is registered with the base wireless provider system as well, which allows the base wireless providers to be aware of the subscriber's location so that the base wireless provider is able to re-route all calls entering the local provider's MSC for final termination of the subscriber's mobile expression. If the subscriber's mobile station moves from an MSC in a previously visited provider network to a first visited MSC, or back to the base provider network MSC, the base MSC notifies the previously visited MSC to delete any data regarding the mobile station from your system. This process of tracking the provision of a call to the roaming caller and the actual provision of call completion on the local provider's switch is not resolved by the applicants' proprietary system for billing on an account.

In summary, there are several drawbacks to standard or conventional wireless communication networks.

For example, a drawback to the standard or conventional network is that the calls supplied to the roaming subscriber cannot be controlled or monitored. Another drawback of the standard network is that calls originating from the roaming subscriber cannot be fully supervised and controlled or if supervision and control is provided, additional infrastructure is required at the roaming provider's site. There is a need in wireless systems to resolve the credit risks of some roaming subscribers and provide a system so that wireless service providers can provide wireless roaming services to subscribers with credit risk and thus decrease the risk of credit.

SUMMARY OF THE INVENTION

The invention is a wireless telecommunication roaming solution that includes the Regnot function, a roaming call originating function and a roaming call provisioning function. The roaming solution integrates with a real-time account billing system that equips the base provider with the ability to monitor, control and set the real-time price of calls originated or supplied to roaming subscribers with credit risk, for example, pre-paid roaming subscribers. The roaming solution defines a network architecture comprising multiple network components including a roaming server which acts as a gateway between the National Location Register (NLR), which is also part of the roaming solution and a remote call origin switching unit. The remote call source switching unit with the 800 number remote switching unit (800 # RSU) at the location where wireless roaming call origins will be processed through central control, which can generally be referred to as a central RSU control or RSU call origin. The roaming server also acts as a gateway between the NLR and an account based on a billing system to which the roaming solution is coupled. The NLR acts as a VLR, as observed by the HLR of the base provider, and acts as an HLR, as observed by the VLR of the local roaming provider. This is accomplished by an intermediate NLR connection within or by inserting itself into the communication link between the HLR of the base mobile switch and the VLR of the mobile switch supplying the roaming. The NLR is placed communicably to intercept messages from the VLR and HLR. The NLR tracks the location information for wireless roaming subscribers and contains the HLR information, which provides the subscriber profile information. The NLR and the roaming server are adapted to communicate communicatively with a conventional and unmodified wireless communication network having a base MSC which provides transport and translation support for calls originating from the wireless roaming subscriber, and several roaming tenderer MSCs, which provide transport and translation support to complete calls to the wireless roaming subscriber. The NLR and roaming server are further adapted to integrate and communicate with a real-time billing system so that all roaming calls can be monitored, controlled and a price and account can be set in real time . Therefore, the roaming solution network system comprises three components and these are the roaming server, the NLR, and the RSU call origin (800 # RSU). Each of these components is tailored so that it can be located at a central location away from either the base provider or the provider providing the service.

One aspect of the present invention is that the initiations or origins of all calls from roaming subscribers with wireless credit risk can be supported and monitoring and control of t will be provided.

calls. Real-time call monitoring and control provided by the roaming server, and the NLR, integrated with a real-time account billing system mitigates the exposure of base providers to credit risk. During the Regnot process, the NLR scheduling elements retain the roaming service provision MSCID and provide it with the roaming server for use in subsequent rate setting of calls originating. In addition, during call origination, NLR programming elements retain the MIN of subscribers making the call and dial the digits. These are provided to the roaming server for subsequent use by the centralized 800 # RSU when setting up the call for the called party. In response, NLR programming elements receive a DN from a dialed number or unique for use by the roaming MSC to extend the call originating to 800 # RSU. During this aspect of the invention, completing the call to the wireless roaming subscriber can be disabled. Centralized localization of roaming solution components specifically in NLR, roaming server, and call originating RSU eliminates the need for specialized roaming platforms that must be co-located on the switch supplying the service to provide the service to unregistered pre-paid roaming subscribers, because they can now be registered.

Another aspect of the present invention is the support of supplying a call to roaming subscribers with wireless credit risk. Again, due to the roaming solution of the present invention, the exposure to credit risk of the base provider is reduced. When an incoming call directed to a roaming subscriber at wireless credit risk arrives at the home MSC, the MSC routes the call to the RSU of the billing system, which may be referred to as the RSU of the account billing system. The billing system account billing system MSW requests the sales server, requests a call validation, and then requests a temporary local directory number (TLDN) from the roaming server. to the roaming server MSC. The roaming server routes the request to the NLR. Subsequently, at the request of the server]? roaming, the NLR scheduling elements will obtain a TLDN from the MSC that provides the roaming service using a message and a routing request response (ROUTEREQ). The RSU integrated with the billing system interacts with the roaming server and uses the TLDN to originate a call to the MSC that provides the roaming service for the wireless roaming subscriber. Upon completion of the call, the calling segments of the calling party to the RSU and from the RSU to the carried wireless roaming subscriber will be merged into the RSU integrated with the billing system. As noted above, NLR scheduling elements may disable completing the call to a wireless roaming subscriber during Regnot. However, when a call is received to a wireless roaming subscriber, the NLR scheduling elements send a QUALDIR message to the MSC that provides the roaming service to allow the call to the wireless roaming subscriber to complete. Upon disconnection of the call, the roaming server will inform the NLR programming element which then inactivates the call completions to the wireless roaming subscriber. Please note that the NLR does not take into account the fact that the wireless roaming subscriber has hung up from its home MSC to the MSC that provides the roaming service or from the MSC that provides the service to its home MSC during the instance one call.

The invention includes the ability to communicate with an account-based call and billing control platform that enables registered wireless prepaid subscribers to make and receive calls when roaming outside of the provider's home networks. . The invention verifies that the balance of the prepaid wireless subscriber's account is sufficient to establish or receive the call, translates the account balance into conversation minutes, and monitors the call for the duration of the conversation. If the prepaid wireless subscriber exceeds the available account balance, the invention suspends the call in the first negative minute and immediately decreases the prepaid wireless subscriber's account. If the call is disconnected before the account balance decreases, the invention immediately decreases the prepaid wireless subscriber's account and frees the exchange exchanges.

The present invention, as described above, corrects the drawbacks of wireless networks that are unable to provide service to roaming subscribers with high credit risk without exposing the base provider to unacceptable credit risk. The previously unregistered prepaid wireless roaming subscriber previously requires an unregistered prepaid roaming solution which can now transition to a registered account based on wireless roaming subscribers. Additionally, these account-based subscribers may be pre-paid or optionally limited credit subscribers. These and other advantageous features of the present invention will be in part apparent and in part highlighted below.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the present invention, reference may be made to the accompanying drawings in which:

Figure 1 is a general diagram of the roaming network architecture integrated with the standard SS7 communication network and an account based billing system;

FIG. 2 is a call flow diagram of the Regnot process;

Figure 3 is a call flow diagram of a call source from a wireless roaming provider (stage 2 dialing);

Figure 4 is a call flow diagram of a call originating from a wireless roaming provider (single stage dialing);

Figure 5 is a call flow diagram of the call provision in the MSC that provides the roaming service to the roaming subscriber;

Figure 6 is a sequence of sending interface messages between a roaming rate and service MSC, an NLR and an HLR of a Regnot of the roaming subscriber at the time of activation;

Figure 7 is a sequence of establishing interface messages between an MSC that provides the roaming service, an 800 # RSU and a market server for the origin of a roaming call which includes a second 800 # dial tone. RSU;

Figure 8 is a sequence of sending interface message between an MSC supplying the roaming service, an LLR, a roaming server, a market server and an 800 # RSU for dialing a single call origination stage. wireless roaming;

Fig. 9 is a sequence of sending interface message between a base MSC, an HLR, an LLR, a local RSU, a market server, a roaming server and an MSC supplying the roaming service for the provision of a call to the MSC supplying the roaming service, for a wireless roaming subscriber.

Fig. 10 is a sequence of sending interface messages when the mobile station becomes inactive.

FIG. 11 is a sequence of sending interface messages for volume log deletion of actively registered roaming subscribers.

FIG. 12 is a sequence of sending interface messages for registration again, when a roaming subscriber enters the network of a new MSC supplying the service.

Figure 13 is a sequence of sending interface message for registration again when the roaming subscriber re-enters the home network.

DETAILED DESCRIPTION OF THE INVENTION

In accordance with one or more embodiments of the present invention, the various views are illustrated in Figures 1 to 13, and similar reference numerals are used consistently throughout them to refer to similar and corresponding parts of the invention to the whole various views and figures of the drawings. In addition, note that the first digit or digits of the reference number for a given article or some part of the invention correspond to the number of the figure in which the article or part is identified for the first time.

An embodiment of the present invention comprises a roaming solution system further comprising a roaming server and an NLR, and an 800 # RSU where the system is adapted to communicably connect to a standard or conventional telecommunications network that has a typical base provider infrastructure and a plurality of roaming provider infrastructures and where the solution solution system Roaming are also adapted to communicateably connect to a real-time account billing system that has a market server and a MSW. The roaming solution describes a novel system and method of providing credit-limited wireless roaming services to roaming subscribers with high credit risk while reducing the exposure of the base provider to credit risk. The roaming solution further allows the base provider to make the decision to register the roaming subscriber with high credit risk, with a plurality of roaming provider partners without fear of substantial credit risk.

The details of the invention and the various embodiments can be better understood with reference to the figures of the drawings. Referring to Figure 1, a total network architecture 100 for a wireless roaming solution is shown. The network architecture is designed to provide a continuous roaming solution. The communication links or paths are demonstrated between the various components of the network. Voice communication paths are indicated as such, for example, voice link 102 between mobile station or mobile phone 104 and MSC 106 supplying the roaming service. SS7 communication links are also shown, for example SS7 communication link 108 between VLR 110 and NLR 112. TCP / IP communication links are also shown, for example, TCP / IP communication link 114 between NLR 112 and roaming server 116. A typical SS7 telecommunication network architecture comprises an MSC 106 that provides roaming service which is coupled to a

VLR by means of an SS7 link and this is located in the roaming position and the network architecture further comprises a base MSC 118 that is coupled to an HLR by an SS7 link and is located in the subscriber base position wireless roaming. The network architecture may also include a RSU 120 local billing system that is local to the base location of the wireless roaming subscriber and the local RSU acts as an auxiliary switch that controls the wireless roaming call for time account billing. real. The network also includes a market server 122 where the rate setting engine for real-time account billing is located and where the database of subscribers with high credit risk is located. The market server and the local billing RSU can be linked by communicating through a conventional or standard TCP / IP link. The RSU can further communicate with the base MSC via voice links 126 and 128.

The network can be equipped with a novel roaming solution network system comprising a roaming server 116, an NLR 112 and an 800 # RSU 130 (call origin RSU). The roaming solution system can be linked by communicating through the roaming server 116 to the RSU 120 of the local billing system through the conventional or standard TCP / IP link 132, which provides a communicable link to the monitoring and control system of Real-time calls for billing to a real-time account. The components of the roaming solution are interconnected by conventional or standard TCP / IP links 114 and 134. The 800 # RSU has a voice link 136 with the MSC 106 which provides a roaming service from the roaming provider. 800 # RSU 130 is the component of the roaming solution network with which calls originating from the roaming wireless subscriber will be processed for control. The roaming server 116 of the roaming solution network acts as a gateway between the NLR 112 and the market server 122. Market server 122 is the account based billing network component where the rate setting system and equipment is located and where the subscriber database is located.

The NLR 112 is adapted to be communicably inserted into the SS7 link between the VLR 110 of the roaming provider and the HLR 138 of the base provider. NLR 112 communicates with VLR 110 via link 108 SS7 and communicates with HLR 138 via link 140 SS7. The NLR is adapted to perform the function of an HLR (subscriber profile information processor) and the function of a VLR (roaming processing of a registered visitor). Therefore, the NLR is adapted to have an appearance of HLR relative to the VLR and to present an appearance like a VLR relative to the HLR. The NLR is communicatively adapted to intercept HLR and VLR messages. The

Network NLR 112 tracks the location information for a wireless roaming subscriber and reflects the HLR that provides the profile information of the wireless roaming subscriber.

When the wireless mobile station or wireless mobile phone 104 of a wireless roaming subscriber enters the roaming MSC 106 area, a Regnot occurs. During the Regnot process, the programming elements (software) of NLR 110 are used to provide the DN and the Regnot response message to the MSC 106 supplying the roaming service. The DN is assigned to a centralized 800 # RSU 130 in which all call origins will be processed for control. Once the wireless roaming subscriber's mobile station 104 has completed the Regnot process, the NLR scheduling elements (software) may prevent the completion of the entire call to the wireless roaming subscriber by setting a completion restriction code and the NLR sends a Regnot response message to the MSC 106 that provides the roaming service. At this point, all calls originating from the subscriber and wireless roaming can be supported.

In addition, please note that during the Regnot process, the NLR programming elements retain the MSCID that provides the roaming service and provide the MSCID to the roaming server 116 for use in subsequent rate setting of calls that are originate. During the initiation of a call from the wireless roaming subscriber, the NLR Programming Elements (software) retain the 'MIN of the calling subscribers and the dialed digits (i.e. the called party number). The MIN and the dialed numbers are provided to the roaming server for subsequent use by the centralized 800 # RSU 130 in establishing the call to the called party. In response to the call request, the NLR programming elements (software) receive a unique DN for use by the MSC 10 6 which provides the roaming service to extend the call originating to the 800 # RSU.

The network architecture also depends on supplying the support call or terminating the call to the wireless roaming subscriber. When the wireless roaming subscriber enters the MSC 106 area supplying the roaming service, the server

116 Roaming is aware of the location of the wireless roaming subscriber. Therefore, when a call comes in to a wireless roaming subscriber that reaches the base MSC 118, the base MSC sends the call to the

RSU 120 of the local account billing system. The local account billing system RSU then requests the account billing system market server 122 which in turn requests a TLDN from the roaming server 116. Roaming server 116 sends the request for a TLDN to NLR 112. Subsequently, upon request from the roaming server, the NLR programming elements (software) will obtain a TLDN from the MSC 106 that provides roaming service using a ROUTEREQ message and a response. Once the TLDN is provided, the local RSU 120 interacts with the roaming server 116, uses this TLDN to originate a call to the

MSC 106 that provides the roaming service for the wireless roaming subscriber. When the wireless roaming subscriber answers the call, the calling segments of the calling party to the local RSU 120 and the local RSU to the called roaming subscriber will be connected to the local RSU.

As indicated above, the NLR programming elements are adapted to be able to disable completing a call to a wireless roaming subscriber during the Regnot process. However, when a call is received for the wireless roaming subscriber at the base MSC, the NLR programming elements are adapted to send a message to the MSC 106 supplying the roaming service to allow completion of the call for the subscriber wireless roaming. Upon disconnection of the call, can roaming server 116 informal? to the NLR programming elements (software) which can then inactivate call terminations to the wireless roaming subscriber.

It should be noted that the wireless roaming subscriber on this network is identified by its Mobile Identification Number (MIN). The wireless roaming subscriber MIN is retained during the Regnot process, at which time the NLR programming element (software) can search within an internal subscriber lookup table to see if the roaming service supplying MSC supports originating. call using a source trigger. If not found in MSCID supplying roaming service in lookup table, NLR scheduling items (software) can load source trigger based solely on transmission capacity parameter (TansCap) found in the Regnot message. It is further noted that the NLR does not take into account when a wireless roaming subscriber has hung up from its home MSC to a MSC that provides service (from a non-roaming environment to a roaming environment), OR from an MSC that supplies the roaming service to your home MSC (from roaming to non-roaming environment) during the instance of a single call. The location of the wireless roaming subscriber is established at the time of Regnot. There is no additional action taken by the NLR to take into account roaming disconnection that can result in a change to a wireless roaming subscriber location when moving between base MSC areas and MSC areas supplying roaming service. during a single call. The disconnects are transparent to the programming elements (software) so that the roaming location of the wireless roaming subscriber is continuous and is established only at the time of Regnot.

All messages that come from MSC 106 that the roaming service provides can be routed to the

NLR 112 via SS7 network link 108. The NLR 112 can extract the location information from the wireless roaming subscriber (ie MSCID, location area ID, etc.), and store it in the internal database. Furthermore, the NLR may also change part of the profile parameters in the Regnot return result message to allow the wireless roaming subscriber to make and receive calls from the MSC providing the roaming service. The NLR may also pass the location information of the wireless roaming subscriber to the roaming server 116 via the TCP / IP network link 114.

The advantages of this roaming solution network system are clear. The integration of the novel system in the SS7 standard or another standard of a similarly configured telecommunication network is transparent. The base MSC

0 and the related HLR as well as the MSC supplying the service and the related VLR are not altered and will operate normally. The call account billing and monitoring supervision system includes the market server 122 and the RSU 120 of the local account billing system and are unaltered and will function as usual. Calls entering the base provider's switch can be delivered to roaming subscribers with previously unregistered but now limited credit. Calls can be originated by these roaming subscribers with limited credit who are now registered without the need for roaming platforms that support each site of the roaming providers. All this is provided at the same time that the exposure time to a credit risk for the base provider is reduced.

Referring to Figure 2, a call flow diagram for a call Regnot process is provided when the wireless roaming subscriber turns on the mobile phone while it is in the MSC area supplying roaming service or when the roaming subscriber Wireless moves to a roaming area. When the wireless roaming subscriber 202 is activated, the mobile phone 104, and the mobile phone transmits a MIN to the MSC 106 which supplies the roaming service which sends a 204 Regnot message via the SS7 network link to a VLR 110. The VLR of the MSC supplying the roaming service is configured to identify the NLR point codes as the HLR of a previously reserved block of the wireless roaming subscriber's MIN. Therefore, the MSC supplying the roaming sends the Regnot to the NLR. Upon receipt of the Regnot message, the NLR may search the MIN in the NLR's internal database to see if the wireless roaming subscriber is listed. If the wireless roaming subscriber is in the list, the NLR can replace the MSCID that is roaming with the MSCID of the NLR and send the 206 Regnot message to the HLR using the HLR direct point code. If the wireless roaming subscriber is not on the list, then in NLR you can pass the message directly to the HLR without any modification (i.e. the MSCID is not replaced with the NLR ID). The HLR can then respond with a Regnot return result message 208 to the NLR via the SS7 network link. The NLR may modify the Regnot return result message before sending it to the MSC supplying the roaming service. The NLR can replace the MSCID of the HLR with the MSCID of the NLR. The NLR can set the originating indicator for 8 of the origins of all calls on the MSC that provides the roaming service. The NLR can also set destination digits equal to an 1800 DN Identification Service (DNIS) number. In addition, the NLR can set the restriction code to 1 to restrict the establishment on the MSC that provides roaming. Setting the originating flag to 8 indicates that the origins of all calls must be routed to a single NPANXX-XXXX. The active line number (1-800 DNIS number) is configurable for each pre-reserved block of wireless roaming subscriber MINs. The active line number can be used to route all call sources to the centralized 800 # RSU. If the termination restriction code is set to 1, or to another appropriate code number (denial of completion), no calls will be delivered to the wireless roaming subscriber.

The NLR can then send location information for wireless roaming subscriber 210 to roaming server 116 over the TCP / IP link. The roaming server can then update the location information for the wireless roaming subscriber and in turn send the location information for the subscriber 212 to the market server 122. The roaming server then confirms the location message to the NLR. Again, please note that the NLR may modify the Regnot return result message before sending it back 214 to the MSC supplying the roaming service. The NLR can replace the MSCID of the HLR with the MSCID of the NLR. The NLR may also set the originating trigger field for all call attempts which request the originating request message from the NLR when the wireless roaming subscriber establishes a call. The NLR may also set the termination restriction code to, or another appropriate code number, to prevent any termination so that no calls are entered to the wireless roaming subscriber.

Once the Regnot process is performed according to the flowchart in Figure 2, an attempt can be made to initiate a call from the wireless roaming subscriber. Referring to Figure 3, which shows the call flow diagram for the initiation of a call by the wireless roaming subscriber. Figure 3 is representative of call initiation in a telecommunication network where two-stage dialing is supported only. This is because the version of the SS7 network or similar network where originating request messages are not fully supported. Wireless roaming subscriber initiates a 302 call by entering the party number and sending the requested number from the station

104 mobile. This call initiation attempt by the wireless roaming subscriber is routed to the MSC 106 supplying the roaming service and the MSC supplying the roaming service routes the call attempt 304 to the centralized # 800 RSU (call origin RSU) 130 by dialing the 1-800 DNIS (active line number) received during registration. Once the 800 # RSU receives the call attempt, it can collect the DNs of the requested party and the MIN 306 of the wireless roaming subscriber (which can be obtained by dialing the second stage) and the request 306 from the server 122 of market for call validation. If the call validation is positive 308, the market server sends the maximum call duration to the centralized 800 # RSU 130. The centralized 800 # RSU then connects call 310 to the destination DN of the requested party. The centralized 800 # RSU can monitor the call to indicate that the call has been established and begin call time determination for the time the call was first routed to the 800 # RSU. The call can be suspended and disconnected when the call is disconnected at the originating MSC or when a completion instrument has been reached or when the maximum call duration has been reached.

The call record is communicated to 312 market server. The advantages of using Market Server 122 in combination with 800 # RSU 130 as described above is that the call can be supervised and controlled by an 800 # RSU exchange for account billing in real time without the need for local roaming platforms. to the MSC supplying the roaming provider service.

Referring to Figure 4, a call flow diaphragm is shown for call origin after Regnot has occurred according to the call flow diagram shown in Figure 2. The call origin after registration Calling according to the call flow diagram in Figure 2 does not require second stage dialing for systems that fully support the originating request message. The wireless roaming subscriber originates a call 402 at MSC 106 supplying the roaming service and MSC supplying the roaming service sends an originating request message 404 to NLR 112 via VLR 110. The NLR sends a message 406 which it contains the digits of the requested party and the MIN of the wireless roaming subscriber to the roaming server 116 over the TCP / IP network link. In turn, this information is stored on the roaming server. A new unique 1-800 DNIS number can be assigned by the roaming server for this call originating from the wireless roaming subscriber. The roaming server then returns the number 1-800, 408, to the NLR. The NLR sends 1-800 DNIS 410 to the MSC supplying the roaming service in the originating result return result message. The MSC that provides the roaming service can direct the 412 call to 800 # RSU 130 through the 1-800 DNIS. The 1-800 # RSU requests 414 from the roaming server to validate the 1-800 DNIS number received. The roaming server searches the 1-800 DNIS in the internal database to obtain the dialed digits of the requested party and the MIN of the roaming subscriber, and sends request 416 to 800 # RSU to validate the call. The 800 # RSU validates the 418 call with the market server 122. If the validation is positive, the market server provides the maximum call duration to 800 # RSU. The 800 # RSU then connects the 422 call to the dialed destination digits of the requested party. The 800 # RSU can monitor the call to indicate that the call has been connected and start timing the call from the moment the call is first routed to the 800 # RSU. The call can be interrupted and disconnected when the caller disconnects at the originating MSC or when a completion instrument has been reached or when the maximum call duration has been reached. The call log is sent 424 to the market server.

The advantages of using NLR 112 and roaming server 116 for holding and channel information as well as for validating and routing the call to 800 # RSU is accomplished in one-step dialing.

Referring to FIG. 5, a call flow diagram for call completion or call provisioning is shown in an MSC 106 that provides roaming service for calls 502 entering a wireless roaming subscriber. The call flow is initialized by the base MSC 118 and the roaming subscriber receives an incoming call designed for the roaming subscriber. Base MSC 118 sends a location request message to HLR 138 in an attempt to locate the wireless roaming subscriber and MSC 106 that provides the roaming service for which the subscriber is served. The HLR returns the DN in the location request return result message. The base MSC 118 sends the call 504 to the local RSU 120 of the real account billing system by means of the DN. The local RSU then requests 506 from the market server 122 for call validation 508 and requests a TLDN 510 from the roaming server. The roaming server sends the request for a TLDN 512 to the NLR 112. The NLR then sends a qualifying directive message (QUALDIR) to the MSC 106 supplying the roaming service, to allow 514 provision of a call. The NLR then sends a route request message to the MSC supplying the roaming service (VLR) via the SS7 network link requesting a TLDN 514. The MSC supplying the roaming service in this way corresponds to a message ROUTEREQ return result that contains the TLDN 516 to the NLR. The NLR then sends TLDN 518 to the roaming server, which in turn sends TLDN 520 to the local RSU 12 0. The market server has previously provided the maximum call duration to the local RSU. The local RSU then dials TLDN 522, which then routes call 524 that enters MSC 106 that provides the roaming service. The MSC supplying the roaming service then ends and completes the 526 call to the roaming subscriber. The RSU 520 monitors the call to indicate that the call has been connected and begins determining the time of the call from the moment the call is first routed to the RSU. The call can be suspended and disconnected when the incoming call is disconnected at the origin or when a completion instrument has been reached or the maximum call duration has been reached. Upon disconnection of the call, the RSU updates 528 to the roaming server which in turn sends disconnection information 530 to the NLR. NLR Inactivates Call Termination

532 .

The advantage is that during Regnot the NLR is identified by the VLR as the HLR, and thus the MSC supplying the roaming service is supplied with the NLR as if it were the HLR. The NLR is capable of identifying the actual HLR based on the roaming MIN's search. The NLR can then contact the real HLR and will identify itself (the NLR) as the VLR that provides service to the roader by providing the real HLR with the MSCID of the NLR in view of the MSCID that provides the roaming service. Therefore, the HLR views the NLR as the VLR that supplies the service to the rover. The NLR also during Regnot contacts the roaming server and the market server to identify the position of the roader. The NLR is now the focal point regarding communication of the driving itinerary. This makes roaming continuous as the roaming subscriber moves from one MSC to the next.

Referring to FIG. 6, roaming service 600 of the interface message sequence is shown. It should be noted first before discussing the interface message sequence as indicated in Figure 6 that all messages from wireless roaming subscribers that are not included in the NLR database are passed directly to the HLR without any modification to the message Regnot. The location of the subscriber that is not in the list is now as reflected by the interface message sequence of Figure 6. Figure 6 reflects an interface message sequence where the wireless roaming subscriber is included in the NLR.

The first interface message in the sequence occurs when the wireless roaming subscriber turns on the phone 614, at which time the subscriber's mobile station provides the subscriber's MIN to the MSC 602 supplying the service. The MSC 602 supplying the service sends a Regnot message via the SS7 network to the NLR which includes the subscriber's MIN and the MSCID supplying the roaming service. Upon receipt of the Regnot message, the NLR searches the MIN in the internal database to see if the subscriber is a subscriber on the list. For a wireless subscriber listed, the NLR will replace the MSCID providing service and the point code with the MSCID of the NLR and the point code and send the 617 Regnot message to the HLR 606. Please note that if the subscriber is not a wireless subscriber in the list, the NLR will go through the message directly to the HLR without any modification. The HLR will thus respond with a Regnot return result message 618 to the NLR. The NLR will then send the location information to the NTC roaming server 608 over the TCP / IP interface in a location notification message. The roaming service 608 will then return the location notification confirmation message 622 to the NLR 604. The roaming service 608 updates the location information and sends the location information to the market server by transmitting the MSCID 624 to the RSU 610 which in turn transmits the MSCID to the market server 612. In networks where Stage 2 dialing is required, the NLR will modify the Regnot return result message in the following ways before sending it to the MSC supplying the service. First, the NLR will replace the MSCID of the HLR with the MSCID of the NLR. Second, the NLR will set the originating indicator for an indication of origin of all calls. Third, the NLR will set the destination digits equal to the 1-800 DNIS number. Fourth, the NLR will set the termination restriction code as an indication that the call is not allowed. In single-stage dialing, the NLR will modify the Regnot return result message as follows, before sending it to the MSC supplying the service. Again, the HLR MSCID is replaced with the NLR MSCID. The NLR will set the originating field for all call attempts. The NLR will also establish the code that prevents answering the call

<td>for one</td><td>indication</td><td>what not</td><td>I know</td><td>It allows</td><td>to complete</td><td>the</td>

<td colspan="2">call. Please,</td><td>note that</td><td>the</td><td colspan="2">establishment of</td><td>the</td>

<td>activation</td><td>originally</td><td>for all</td><td>the</td><td>call</td><td>will request</td><td>a</td>

<td>Message from</td><td>request</td><td>of origin to</td><td colspan="2">NLR when</td><td colspan="2">the subscriber</td>

<td>itinerant</td><td>wireless</td><td>make a</td><td colspan="2">call. The</td><td colspan="2">NLR will keep</td>

an internal staging table to identify MSCs that can support source activations.

Once the sequence of the interface method of Figure 6 is performed for the roaming Regnot, the origin of the roaming call can be provided for the wireless roaming subscriber. Referring to Figure 7, the interface message sequence for roaming an originating call 700 that requires two-stage dialing is shown, after the Regnot sequence of Figure 6 has been performed. The interface message sending sequence begins when the wireless roaming subscriber originates a call 702 on the MSC 704 that provides roaming service. The MSC that provides roaming service will process the origin of the roaming call through 800 # RSU 706 through 1-800

DNIS 708 that is inserted during the Regnot process, as shown in Figure 6. Centralized 800 # RSU (the call origin RSU) 706 will provide a second dial tone 710 in order to collect the destination 712 digits for make the call connection with the called party. The

800 # RSU will then ask the market server 714 for a rate setting request message 716 for call validation. The rate setting request message will provide the MIN for a wireless roaming subscriber and the digits of the destination number. If the market server finds the call validation to be positive, the market server will send a rate setting request response message 718 back to the 800 # RSU containing the maximum call duration. The centralized 800 # RSU then connects the 720 call to the destination DN of the called party. The 800 # RSU will monitor the call for setting the 722 price.

Please note that the connection between the NLR and the roaming server must be monitored to ensure that an active connection is maintained. Therefore, there is an interface protocol between the roaming server and the NLR over the TCP / IP network link that is designed to monitor the active connection between the roaming server and the NLR. The interface monitoring interface protocol is started by an NLR. The NLR opens the TCP / IP network link. by sending an active connection status check to the roaming server. The NLR will be responsible for sending the active connection status check message at a specified interval. The NLR active connection status check message, the NLR will report the status of the SS7 link, the database and the roaming server application. The roaming server can be adapted to respond to the active connection status check message with a response message indicating an active connection. The roaming server can reply back with a reply message within a fixed interval. If the NLR does not observe any reply messages from the roaming server within a fixed interval, the NLR will close the active connection and try to reconnect the roaming server. If the reconnect attempt fails, the NLR can retry an attempt at fixed intervals. The response time interval and the retry time interval are parameters that can be configured and are set by the NLR.

Referring to Figure 8, the interface message sending sequence for a wireless roaming call source network environment 800 is shown. For the roaming call origin to occur, the VLR for this wireless roaming subscriber is set as all calls to the originating trigger during the Regnot procedure. The call originating occurs when the wireless roaming subscriber dials the digits of the desired party and sends the call originating message 802 with the dialed digits to the MSC 804 supplying the roaming service. The MSC supplying the roaming service then transmits an originating request message 806 to NLR 808 which includes the dialed digits of the called party. The NLR will then send the routing information message 810 along with the dialed digits of the called party to the roaming server 812. The roaming server then assigns a temporary 1-800 DNIS for the wireless roaming subscriber and will store the 1800 DNIS along with the dialed digits of the called party as received in the originating request message. The roaming server will then reply to the NLR with the routing information reply message 814 containing the 1-800 DNIS along with the dialed digits of the desired call. The NLR will then reply to the MSC 804 supplying the roaming service with a source request return result message 816 including the 142

800 DNIS as the destination digits. The MSC 804 that provides the roaming service then 'connects 818 to an 800 # RSU (call origin RSU) 824 via 1-800 DNIS as assigned by the roaming server. If the NLR does not receive the routing information response message 820 from the roaming server within the defined time interval, the NLR will retry the routing information message again and place the 1-800 DNIS in the digits of routing of the originating request return result. The roaming server transmits the MIN, dials the digits and the MSCID 822 to 800 # RSU 824. The 800 # RSU 824 sends a rate setting request message 826 from the 800 # RSU to the marketplace 824 server that includes the MIN of the wireless roaming subscriber and the dialed digits. The market server performs a call validation, and if the call validation is positive, the market server will reply back with a rate setting request response 830, which includes the maximum call duration as well as the dialed digits of the part that is called. The 800 # RSU then connects the calling party to the called party 832. The 800 # RSU monitors the call for setting the 834 price and transmits it to the market server.

Referring to FIG. 9, an interface message sequence for supplying a call entering the home MSC to a wireless roaming subscriber in the MSC supplying the roaming service is shown. The call provisioning interface message sequence 900 is initiated by a call 902 entering the base MSC 904. The base MSC attempts to locate the wireless roaming subscriber. The HLR responds back 5 to the base MSC with a location request response message that provides the connection information to the local RSU. The base MSC then connect 906 to the RSU system

908 of billing of local account by means of the DN and in turn the RSU of local billing sends a message 910 of request of establishment of rates to the server 912 of market which includes the MIN and the dialed digits for call validation. If the validation is positive, the market server returns the MSCID to the local RSU 908. A routing request message 916 is sent to the roaming server 918 requesting TLDNs, which in turn requests TLDN 920 from the NLR with a routing request message. The NLR 922 will send a 926 QUALDIR message to the MSC 926 that provides the roaming service to allow call termination for the wireless roaming subscriber. A return QUALDIR message 928 is transmitted back from the MSC supplying the roaming service to the NLR. The NLR will then obtain a TLDN from the MSC supplying the roaming service using the 930 ROUTEREQ message. Upon receipt of ROUTEREQ return result message 932 from the MSC supplying the roaming service, the NLR will send a routing request response message 934 to the roaming server. The roaming server will then send a routing request response message 936 to RSU 908, which includes a TLDN, which in turn is transmitted 938 to the base MSC 904. The local RSU then connects 940 to the wireless roaming subscriber upon termination of the MSC supplying the roaming service thereby completing the call.

The call can be suspended and disconnected 942 by call disconnect on the base MSC or disconnection 944 on the roaming server. The call is priced 946 for the local billing RSU.

Referring to FIG. 10, a sequence of signals 1000 is shown that occur when the mobile station is deactivated or becomes inactive. A power suspend signal 1002 is transmitted to the MSC 1004 supplying the service. The MSC supplying the service sends an idle mobile station signal 1006 to the NLR 1008. The NLR then transmits a location notification signal 1010 to the roaming server 1012. Roaming server 1012 then responds back with a message

0 Location notification confirmation 1014. The NLR

1008 it then notifies the HLR 1016 with a mobile station idle 1018 signal. A mobile station idle return signal 1020 is transmitted back from the HLR to the NLR, and the NLR sends a mobile station idle return signal 1020 to the MSC supplying the service.

Referring to FIG. 11, a sequence for a 1100 volume log deletion is shown.

Volume log deletion is initiated by MSC 1102 supplying the service, which then sends a volume log delete signal 1104 to NLR 1106. The NLR responds back with a log delete return signal 1108 on volume. The NLR then sends a location notification signal 1110 for each subscriber included in the volume log deletion to the roaming server 1112. The roaming server sends a location notification confirmation signal 1114 of

<td> 10</td><td>Return</td><td>to the NLR. The NLR then sends</td><td>an inactive signal</td><td>of</td>

<td></td><td>station</td><td>mobile for each subscriber</td><td>in elimination</td><td>of</td>

<td></td><td>registry</td><td>in volume 1116 back</td><td>to HLR 1118. The</td><td>HLR</td>

<td></td><td>then</td><td>transmits a 1120 signal from</td><td>idle return</td><td>of</td>

<td></td><td>station</td><td>mobile to the NLR.</td><td></td><td></td>

<td> 15</td><td></td><td>With reference to the figure</td><td>12, shown</td><td>a</td>

message stream for the new 1200 record of a new supplying MSC. The sequence is initiated by the new service providing MSC 1201, which transmits a registration notification 1204 to the NLR 1202. The

NLR modifies the Regnot and then sends the registration notification message 1205 to the HLR 1206. The HLR then transmits a registration notification return message 1208 to the NLR which then sends the message back to the MSC supplying the service, again . The NLR 1202 then transmits a location notification message 1209 to the roaming server 1210. The roaming server then transmits a location notification confirmation message 1212 back to NLR 1202. The roaming server 1210 also sends the location notification message to the market server 1214 and the market server responds back with a 1216 location notification confirmation message. The NLR then transmits a deregistration message 1218 to the MSC

1220 which provides old service, which in turn responds back with a 1222 registration cancellation return message.

Referring to Figure 13, the message sequence for registration back to the base 1300 market is shown. The message sequence is initiated by the base MSC 1302 which transmits a registration notification message 1304 to the HLR 1306. The HLR then transmits a deregistration message 1308 to NLR 1310, the deregistration message is then sent to MSC 1311 which supplies the service which in turn transmits a deregistration return message 1312, back to the NLR . The NLR then sends the return registration cancel return message to the HLR 1306. The HLR then transmits a return registration notification return message 1314 to the base MSC 1302.

The various call flow examples shown above illustrate many of the novel aspects of the roaming solution. A user of the present invention can choose any of the above call flows, or an equivalent thereof, depending on the

4th application you want. In this regard, it is recognized that various forms of the "present roaming" solution can be used without departing from the spirit and scope of the present invention.

As is evident from the foregoing description, some aspects of the present invention are not limited by the particular details of the examples illustrated herein, and therefore it is contemplated that other modifications and modifications will occur to those skilled in the art.

1Ό applications or equivalents thereof. Accordingly, the claims are intended to encompass all such modifications and applications that do not depart from the spirit and scope of the present invention.

Other aspects, objectives and advantages of the present invention can be obtained from the study of the drawings, the description and the appended claims.

It is noted that in relation to this date, the best method known by the applicant to put the aforementioned invention into practice is the one that is clear from the present description of the invention.