1. Field of the Invention
The present invention generally relates to outbound roamers. More specifically, the invention relates to dynamic provisioning of Customized Applications for Mobile network Enhanced Logic (CAMEL) Subscription Information (CSI) of the outbound roamers.
2. Background of the Technology
Various operators offer international roaming to their users utilizing mobile communication systems employed worldwide. One of the most lucrative aspects of international roaming for an operator is the revenue generated by outbound roaming. The operator generates revenue from outbound roaming when a subscriber of the operator's own home network, visits another network and makes calls. To increase outbound roaming revenue, many operators offer various value-added call control services to the outbound roamers.
These value added services may be provided both for Mobile Originated (MO) and Mobile Terminated (MT) outbound roamer calls. Some of these value added services for the MO calls include, but are not limited to, roaming home short-code, optimal routing, misdialed digit correction, prepaid roaming, Calling Line Identification (CLI) guarantee, and roaming fraud control. Value added services for the MT call for an outbound roamer include, but are not limited to; optimal routing for late call forwarding, incoming call screening and MT prepaid roaming. Roaming home short-code for a MO call from the outbound roamer allows the outbound roamer to dial a home network short-code, such as, customer care, or emergency at the visited network. This service then translates the short-code into the home or visited network long number. In case of an MT call for an outbound roamer, the incoming call screening service allows the outbound roamer to screen only selected callers to get through to the outbound roamer. Further, in case the outbound roamer misdials a number, i.e., a MO call, due to a wrong or missing international dialing prefix, the call may be intelligently corrected using the misdialed digits correction service.
Generally, implementing one or more of the above-mentioned value added services can include Customized Application for Mobile network Enhanced Logic (CAMEL). In that case, when the outbound roamer registers at the visiting network and initiates a call, an Originating CAMEL Subscription Information (O-CSI) is sent from a Home Location Register (HLR) of the home network of the roamer to a Visited Location Register (VLR) of the visiting network. The O-CSI enables the call control for the MO call from a VPMN VMSC to pass to a HPMN GSM Service Control Function (SCF). Similarly, for a MT call, the HLR sends a T-CSI to a HPMN GMSC, which in turn passes the call control to the HPMN gsmSCF. Therefore, for the MO call, the O-CSI is provisioned at the VLR, while for the MT call the T-CSI is provisioned at the HLR.
HLR is provisioned with the O-CSI and the T-CSI for the MO-call and the MT-call irrespective of whether the subscriber is outbound roaming or not. Further, the HLR is provisioned irrespective of whether the subscriber is currently outbound roaming on the CAMEL network or not. Moreover, the license cost of CAMEL subscription for the CSI by an HLR vendor is usually linked to the number of O-CSI or T-CSI or the number of subscribers defined with a CSI that are statically provisioned at the HLR. This static provisioning is irrespective of the number of O-CSI or T-CSI subscribers outbound roaming at any given time. Thus, subscriber-based charging by the HLR vendor often proves to be expensive for the operator.
On the other hand, certain HLR vendors have an upper-limit on the number of T-CSI and O-CSI to be provisioned at the HLR. In this case, the limit for storing the CSI in the HLR becomes a bottleneck for the operator.
One or more of the above-mentioned approaches suffer from the problem of static provisioning of the CSI at the HLR irrespective of the number of outbound roaming subscribers at a given time. This increases the cost for supporting the CAMEL subscribers. Thus, there is a need for an alternative approach that is cost-effective by keeping the number of CSI provisioned at the HLR low at any time.
Brief Description of the Drawings
The present invention provides a system for providing Customized Applications for Mobile network Enhanced Logic (CAMEL) Subscription Information (CSI) of an outbound roamer of a Home Public Mobile Network (HPMN) to at least one CSI storing node when the outbound roamer is roaming in a Visited Public Mobile Network (VPMN). The system comprises a roamers database storing an outbound roamer record of at least one outbound roamer, wherein the outbound roamer record comprises at least the International Mobile Subscriber Identity (IMSI) of the outbound roamer. The system further comprises a detection block to detect whether provisioning of the CSI is required for the outbound roamer and whether a CSI generation block to generate the CSI of the outbound roamer based on at least the IMSI of the outbound roamer, if the provisioning of the CSI is required. The system further comprises a provisioning block to provision the generated CSI of the outbound roamer to at least one CSI storing node. The CSI comprises a service key and an address of a Global System for Mobile communication (GSM) Service Control Function (SCF). Further, the CSI comprises at least one of a Mobile Originated (MO)-CSI and a Mobile Terminated (MT)-CSI.
In the foregoing description, the HPMN is a network where an outbound roamer is originally subscribed, while the VPMN is a network in which the outbound roamer is roaming.
The interface between monitoring block 108 and dynamic CAMEL gateway 110 is either specially prepared using known techniques or standards, or the two elements can be from the same vendor using a vendor specific interface, or they may be available in a single device. In an embodiment of the present invention, that interface may be a TCP/IP based interface. Monitoring block 108 and dynamic CAMEL gateway 110 may belong to different vendors. A person skilled in the art will appreciate that monitoring block 108 and dynamic CAMEL gateway 110 may belong to the same vendor.
In accordance with an embodiment of the present invention, monitoring block 108, and dynamic CAMEL gateway 110 may be physically integrated in the same physical device. In accordance with another embodiment of the present invention, monitoring block 108, and dynamic CAMEL gateway 110 may be installed separately.
VPMN VLR/VMSC 118 sends a MAP transaction message 120 when the outbound roamer registers at VPMN VLR/VMSC 118. MAP transaction message 120 includes a MAP Location Update transaction. MAP transaction message 120 is forwarded to HPMN GMSC/STP 112. Monitoring block 108 taps international roaming links between SS7 interface 106 and HPMN GMSC/STP 112 via which MAP transaction message 120 is sent. Monitoring block 108 monitors MAP transaction message and informs dynamic CAMEL gateway 110 when it detects a successful MAP Location Update. Further, monitoring block 108 provides details of the outbound roamer to dynamic CAMEL gateway 110. The details provided by monitoring block 108 include at least an International Mobile Subscriber Identity (IMSI), the HPMN HLR, VLR/VMSC, a Mobile Station International ISDN Number (MSISDN), a supported CAMEL phase, and combination thereof.
Dynamic CAMEL gateway 110 generates CSI of the outbound roamer. In accordance with an embodiment of the present invention, the CSI comprises a service key and an address of a Global System for Mobile communication (GSM) Service Control Function (SCF). Further, the CSI comprises at least one of a Mobile Originated (MO)-CSI and a Mobile Terminated (MT)-CSI. Dynamic CAMEL gateway 110 provides the generated CSI to HPMN HLR 114 or VPMN VLR/VMSC 118 depending upon whether the generated CSI is a MT-CSI or a MO-CSI respectively. Dynamic CAMEL gateway 110 maintains records relating to at least one VPMN, CAMEL phases supported by the VPMN and at least one subscriber details. Dynamic CAMEL gateway 110 forwards the generated CSI 122 to HPMN GMSC/STP 112.
Detection block 202 detects whether provisioning of the CSI is required for the outbound roamer, if monitoring block 108 communicates a successful MAP Location Update (LUP). Monitoring block 108 also provides details of the outbound roamer to roamers database 208 that stores an outbound roamer record of at least one outbound roamer, such the outbound roamer record comprises at least the International Mobile Subscriber Identity (IMSI) of the outbound roamer. Additionally, the outbound roamer record includes the HPMN HLR, VLR/VMSC, a Mobile Station International ISDN Number (MSISDN), a supported CAMEL phase, and combination thereof. Additionally, detection block 202 identifies whether the CSI for the outbound roamer is defined at CSI storing node 210 in response to the successful MAP Location Update (LUP) from the outbound roamer. Detection block 202 also detects whether the CSI defined at CSI storing node 210 conforms to the CAMEL phase supported by CSI storing node 210. For example, it checks whether HPMN HLR 114 has sent the required MO-CSI to VPMN VLR/VMSC 118 or whether HPMN HLR 114 has the required MT-CSI.
CSI generation block 204 generates the CSI of the outbound roamer based on at least the IMSI of the outbound roamer, if the provisioning of the CSI is required as communicated by detection block 202. CSI generation block 204 retrieves IMSI of the outbound roamer stored in the outbound roamer record of roamers database 208.
Provisioning block 206 provides the generated CSI of the outbound roamer to at least one CSI storing node 210. CSI storing node 210 comprises at least one of HPMN HLR 114 and VPMN VLR/VMSC 118. Provisioning block 206 provisions MO-CSI to VPMN VLR/VMSC 118 while it provisions MT-CSI to HPMN HLR 114.
Before CSI generation block 204 generates the MO-CSI, CAMEL support identification block 302 checks whether CAMEL is supported by VPMN 104 of the outbound roamer and identifies the phase of CAMEL supported by VPMN 104 by using the information of the CAMEL phases stored in CAMEL support database 304. CSI generation block 204 generates the MO-CSI using the information of the CAMEL phases stored in CAMEL Support Database (CSD) 304. It will be apparent to one skilled in the art that CAMEL support identification block 302 may employ various techniques to identify the phase of CAMEL supported by VPMN 104, without deviating from the spirit and scope of the present invention. For example, monitoring block 108 may check CAMEL phases supported by the VPMN in addition to monitoring successful location update transaction of the outbound roamer with the VPMN.
The MO-CSI contains only O-CSI, if CAMEL support identification block 302 identifies VPMN 104 to support CAMEL phase 1.
The MO-CSI contains at least one of O-CSI, SS-CSI and TIF-CSI, if CAMEL support identification block 302 identifies VPMN 104 to support CAMEL phase 2. In CAMEL phase 2, TDP-Criteria for the O-CSI may be associated with the O-CSI.
The MO-CSI contains at least one of O-CSI, D-CSI, SS-CSI, VT-CSI, SMS-CSI, M-CSI, GPRS-CSI, and TIF-CSI, if CAMEL support identification block 302 identifies VPMN 104 to support CAMEL phase 3. In CAMEL Phase 3, additionally, TDP-Criteria for the VT-CSI may be associated with the VT-CSI. Although the present invention is described using GSM network, it is applicable to other wireless networks including GPRS and WIN-based CDMA. First two phases of CAMEL are supported by GSM only while phase 3 and plus are supported by GSM and GPRS. The MO-CSI for phase 3 of CAMEL includes GPRS-CSI and TDP-Criteria for the GPRS-CSI. The VLR (or GPRS SGSN) bound MO-CSI is sent after MAP location update or when any information in the applicable MO-CSI in HPMN HLR 114 has been changed.
For provisioning MO-CSI, the record of MO-CSI (VLR or SGSN) is sent in one dialogue after a successful location update (including GPRS). In accordance with an embodiment of the present invention, the MO-CSI generated by CSI generation block 204 is provisioned at CSI storing node 210. CSI storing node 210 comprises VPMN VLR/VMSC 118. To provision MO-CSI at VPMN VLR/VMSC 118, provisioning block 206 sends a stand-alone MAP Insert Subscriber Data (ISD) to VPMN VLR/VMSC 118 containing a record of MO-CSI of the outbound roamer. In accordance with an embodiment of the present invention, the record of MO-CSI includes an IMSI and the MO-CSI or a set of MO-CSIs corresponding to the phase supported by VPMN 104 of the outbound roamer.
The GT of dynamic CAMEL gateway 110 has the same prefix as the GT of HPMN HLR 114 when it sends the MAP ISD. Dynamic CAMEL gateway 110 selects the HLR GT with the same prefixes as the HPMN HLR GT corresponding to the IMSI of the outbound roamer to avoid discrepancy if VPMN VLR/VMSC 118 checks the prefix of the stored HPMN HLR GT against the HLR GT of dynamic CAMEL gateway 110.
It may be seen that in this embodiment, no change need be made to HPMN HLR 114 as provisioning of MO-CSI at HPMN HLR 114 is not required and therefore no license cost is incurred by the operator. Further, if monitoring block 108 or dynamic CAMEL gateway 110 is not functional, HPMN HLR 114 is not affected. Hence, when the outbound roamer returns to HPMN HLR 114, it is not required to remove the roaming MO-CSI of the outbound roamer at HPMN HLR 114.
Further, in any CAMEL phase, if HPMN HLR 114 has already sent a MO-CSI (e.g. O-CSI, SS-CSI, VT-CSI), dynamic CAMEL gateway 110 does not send additional MO-CSI of the same type since the VLR CAMEL interaction with the HPMN SCP via the same type of MO-CSI can be relayed through dynamic CAMEL gateway 110 to the HPMN SCP.
If the VLR/SGSN MO-CSI is omitted in the MAP ISD operation, VPMN VLR/VMSC 118 shall keep the previously stored VLR/SGSN MO-CSI. Within one dialogue, subsequent received data is interpreted as add-on data. If VPMN VLR/VMSC 118 detects overlapping in the information received within a dialogue, it sends an error for example, Unexpected Data Value.
It will be apparent to a person skilled in the art that various blocks disclosed in conjunction with the disclosed embodiments of the present invention are logically unique entities. One or more of these blocks may be implemented on a single network node, without deviating from the spirit and scope of the present invention. Further, the functions performed by two or more of these blocks may be merged in to a single program code for implementation on a network node. Various implementations imbibing the teachings of the present invention will be apparent to one skilled in the art. All these implementation are deemed to lie within the spirit and scope of the present invention.
Provisioning block 206 provisions both MO-CSI and MT-CSI generated by CSI generation block 204. Various embodiments for provisioning MO-CSI and MT-CSI via HLR provisioning block 402 are described in the following description.
In accordance with an embodiment of the present invention, to provision MO-CSI at VPMN VLR/VMSC 118, provisioning block 206 instructs HLR provisioning block 402 to provision a record of MO-CSI of the outbound roamer to HPMN HLR 114. In accordance with an embodiment of the present invention, the record of MO-CSI includes the IMSI and the MO-CSI or a set of MO-CSIs of the outbound roamer in accordance with the phase supported by VPMN 104. HPMN HLR 114 in turn sends a stand-alone MAP ISD to VPMN VLR/VMSC 118 containing the MO-CSI. The record of MO-CSI provisioned HLR provisioning block 402 at HPMN HLR 114 is subsequently de-provisioned once the outbound roamer returns to HPMN 102, or upon timeout of the record of MO-CSI, or upon purging by VPMN VLR/VMSC 118.
In this embodiment, there is no restriction on the GT of dynamic CAMEL gateway 110. This embodiment is advantageous if VPMN VLR/VMSC 118 checks GT of the issuer of MAP ISD against the full HPMN HLR 114. In this case, a MAP ISD issued by dynamic CAMEL gateway 110 may not be accepted by VPMN VLR/VMSC 118. However, since HPMN HLR 114 issues the MAP ISD, it can be employed even when VPMN VLRNMSC 118 checks the full GT of the issuer of the MAP ISD. Dynamic CAMEL gateway 110 does not send subsequent stand-alone MAP ISD each time a new location update if the outbound roamer is received as the CSI record of the outbound roamer is modified when the successful location update is received for the first time. However, HPMN HLR 114 has to send the stand-alone MAP ISD with the CSI parameter as part of the location update transaction. In addition, if a new location update indicates a different CAMEL phase support, depending on application requirements, dynamic CAMEL gateway 110 may update the HLR CSI provisioning by interfacing HLR provisioning block 402. Further, dynamic CAMEL gateway 110 does not send the complete record of the stand-alone MAP ISD messages in CAMEL Phase 1 and 2.
In an embodiment of the present invention, the complete record of VLR MO-CSI for CAMEL phase 1 and CAMEL phase 2, is sent in one dialogue with MAP ISD command while for CAMEL phase 3, one or more specific elements of VLR/SGSN MO-CSI are sent in one dialogue. When the VLR/SGSN receives a specific element of VLR/SGSN MO-CSI, it overwrites the corresponding specific element of VLR/SGSN MO-CSI (if any) stored in its database for a particular subscriber.
In the stand-alone MAP ISD, provisioning block 206 sends the record of the first group of MO-CSI in one dialogue for CAMEL phase 1 and CAMEL phase 2. The record consists of one or more of O-CSI (irrespective of the value of the “CAMEL Capability Handling” inside O-CSI), TDP-Criteria for O-CSI, SS-CSI and TIF-CSI. VPMN VLRNMSC 118 deletes any old record present in its database and stores the MO-CSI received with MAP ISD command. However, if any element (e.g. SS-CSI) in the record of MO-CSI changes, provisioning block 206 sends the record of MO-CSI again.
For example, if HPMN HLR 114 has already sent the MO-CSI (e.g. O-CSI) while the dynamic CAMEL gateway 110 has to send other MO-CSI (e.g. SS-CSI), dynamic CAMEL gateway 110 will record the MO-CSI sent by HPMN HLR 114 during monitoring and resend the MO-CSI sent by HPMN HLR 114 together with the MO-CSI created by CSI generation block 204. VPMN VLRNMSC 118 deletes the omitted elements of above list on receipt of MO-CSI with the MAP ISD.
In the stand-alone MAP ISD, provisioning block 206 sends the record of the first group of MO-CSI in one dialogue for CAMEL phase 3 and plus. The record consists of one or more of O-CSI (irrespective of the value of the “CAMEL Capability Handling” inside O-CSI), TDP-Criteria for O-CSI, SS-CSI and TIF-CSI for the first group. VPMN VLR/VMSC 118 deletes any old record present in its database and stores the MO-CSI received with MAP ISD command. However, if any element (e.g. SS-CSI) in the record of MO-CSI changes, provisioning block 206 sends the record of MO-CSI again. For CAMEL phase 3 and plus, the record of the second group of MO-CSI additionally contains D-CSI, VT-CSI, TDP-Criteria for VT-CSI, SMS-CSI, and a M-CSI.
Thus, for the first group of MO-CSI of CAMEL phase 3, the dynamic CAMEL gateway 110 records HPMN HLR 114 sent MO-CSI information and resends it together with MO-CSI. However, for other MO-CSI elements, dynamic CAMEL gateway 110 can send them independently.
From CAMEL phase 3 onwards, the record of GPRS MO-CSI to be sent include GPRS-CSI, and TDP Criteria for GPRS-CSI. A complete record of the GPRS MO-CSI is sent if only one GPRS-CSI is changed. The omitted elements of above record are deleted from the SGSN.
In either embodiment, the default phase of CAMEL support at VPMN 104 is one. The actual MO-CSI sent to VPMN VLRNMSC 118 or requested to HLR provisioning block 402 depends on the HPMN application requirements.
A person skilled in the art will appreciate that dynamic CAMEL gateway 110 for MO-CSI is useful to operators with or without CAMEL support for MO calls, since it is required that VPMN 104 should support while HPMN 102 may or may not support CAMEL.
Further, in various embodiments, dynamic CAMEL gateway 110 provisions MT-CSI for the outbound roamer.
In accordance with an embodiment of the present invention, CAMEL gateway 110 provisions MT-CSI at HPMN HLR 114 via HLR provisioning block 402. After a successful location update of the outbound roamer, provisioning block 206 instructs HLR provisioning block 402 to provision a record of MT-CSI at HPMN HLR 114. The record of MT-CSI includes the IMSI, and the MT-CSI. HLR provisioning block 402 de-provisions the earlier provisioned MT-CSI at HPMN HLR 114 if the outbound roamer registers at the HPMN or is timeout by the HPMN or is purged by the current VPMN VLRNMSC 118. Thus, GT translation at the SCCP layer of HPMN GMSC/STP 112 on HPMN MSISDN E164 routing is not required. However, it requires the support of MT-CSI by HPMN HLR 114 and HLR provisioning block 402.
It may be seen that in this embodiment, no change is done to HPMN HLR 114 as HPMN HLR 114 provisioning of MT-CSI is not required and therefore no license cost is incurred. Further, if monitoring block 108 or dynamic CAMEL gateway 110 is not functional, HPMN HLR 114 is not affected. Hence, when the outbound roamer re-registers to HPMN 102, the outbound roamer does not need to remove the roaming MT-CSI at HPMN HLR 114. However, dynamic CAMEL gateway 110 redirects all SCCP messages on HPMN MSISDN E164.
At step 604, it is detected whether provisioning of the CSI is required for the outbound roamer in response to the successful MAP location update. Also, a check is done to identify whether the CSI for the outbound roamer is defined at the CSI storing node. The check determines whether the HPMN HLR has sent the required MO-CSI to the VPMN VLR/VMSC or whether the HPMN HLR has the required MT-CSI. At step 606, the CSI of the outbound roamer is generated based on the outbound roamer record, if the provisioning of the CSI is required. At step 608, the generated CSI of the outbound roamer is provided to at least one CSI storing node. The generated CSI include MO-CSI and MT-CSI.
Next, it is determined whether the location update is successful and whether provisioning of the MO-CSI is required for the outbound roamer at the VPMN VLR/VMSC at step 706. Further, it is determined whether the VPMN supports CAMEL and whether the MO-CSI defined at the VPMN VLR/VMSC conforms to the CAMEL phase supported by the VPMN VLR/VMSC. The CAMEL phase supported by the VPMN is determined at step 708. If the conditions in step 706 are true, the MO-CSI is generated according to the CAMEL phase supported by the VPMN at step 710. The generation of MO-CSI is described in
Next, it is determined whether the location update is successful and whether provisioning of the MT-CSI is required for the outbound roamer at the HPMN HLR at step 906. If the conditions in step 906 are true, the MT-CSI is generated based on the IMSI of the outbound roamer at step 908. The generation of MT-CSI is described in
The foregoing description describes some of the applications for controlling MO-calls of the outbound roamers using the present invention.
The O-CSI for VPMN CAMEL phase 1 is empty. The O-CSI for VPMN CAMEL phase 2 and above contains the following TDP criteria
“The length of the dialed digits is less or equal than X (e.g. 6)”
When the outbound roamer makes a short-code call, a VPMN gsmSSF transfers the call control via a CAP IDP containing the IMSI and the short-code to the HPMN gsmSCF at step 1210. The HPMN gsmSCF checks a database containing translated long numbers corresponding to the short-code and returns the translated long number via a CAP Connect command at step 1212.
However, if the outbound roamer is already equipped with an O-CSI, it can be handled via CAP relay through a CAP relay proxy back to the HPMN gsmSCF.
The O-CSI for the VPMN CAMEL phase 1 is empty. The O-CSI for the VPMN CAMEL phase 2 and above contains the following TDP criteria
When the outbound roamer makes a misdialed digit call, the VPMN gsmSSF transfers the call control via a CAP IDP containing the IMSI and misdialed digits to the HPMN gsmSCF at step 1310. The HPMN gsmSCF returns a CAP Connect command containing the corrected number to the VPMN gsmSSF at step 1312.
The O-CSI for the VPMN CAMEL phase 1 is empty. The O-CSI for the VPMN CAMEL phase 2 and above contains the following TDP criteria
When the outbound roamer makes a HPMN international call, the VPMN gsmSSF transfers the call control via a CAP IDP containing the calling party number, the IMSI and a home number to the HPMN gsmSCF at step 1410. The HPMN gsmSCF obtains caller ID and returns a routing number via a CAP Connect command at step 1412. The call made by the outbound roamer is routed via the routing number to the HPMN and the HPMN gsmSCF substitutes the original IN called party and the original calling party.
However, if the outbound roamer is already equipped with an O-CSI, it may be handled via a CAP relay through the value added local service node back to the HPMN gsmSCF.
After detecting a successful location update at the CAMEL supporting VPMN of the outbound roamer of certain class (e.g. prepaid) at step 1502, the monitoring block provides the IMSI of the outbound roamer to the Dynamic CAMEL gateway at step 1504. The Dynamic CAMEL gateway provides the MO-CSI to the VLR of the outbound roamer either by sending a stand-alone MAP ISD containing the MO-CSI and IMSI with disabled outbound call ODB/CB restriction to the VLR at step 1506 or by triggering the HPMN HLR to send a stand-alone MAP ISD via the HLR provisioning block at step 1508. The O-CSI for any VPMN CAMEL phase is empty.
When the outbound roamer makes a HPMN international call, the VPMN gsmSSF transfers the call control via a CAP IDP containing calling party number, the IMSI and a called party number to the HPMN gsmSCF at step 1510. The HPMN gsmSCF returns a routing number. The HPMN gsmSCF sends Request Report Basic call state monitoring (RRB) including answer/interrupt event and disconnect/interrupt event at step 1512. When the call is routed via the routing number to the HPMN, the HPMN gsmSCF may use ERB answer/interrupt command to monitor and start accounting the call or interrupt the call if balance is reached at step 1514. The HPMN gsmSCF may use ERB disconnect/interrupt command to disconnect and end accounting or interrupt the call if balance is reached or exhausted at step 1516. The HPMN gsmSCF releases the call at step 1518.
When the outbound roamer makes a HPMN international call, the VPMN gsmSSF transfers the call control via a CAP IDP containing the calling party number, the IMSI and the called party number to the HPMN gsmSCF at step 1610. The HPMN gsmSCF returns a routing number. The HPMN gsmSCF sends Request Report Basic call state machine (RRB) including answer/interrupt event and disconnect/interrupt event at step 1612. When the call is routed via the routing number to the HPMN, the HPMN gsmSCF may use ERB answer/interrupt to monitor and start statistical analysis (for example, duration or frequency or suspect location) of the call or interrupt the call at step 1614. The HPMN gsmSCF may use ERB disconnect/interrupt to disconnect and end the statistical analysis or interrupt the call at step 1616. The HPMN gsmSCF releases the call at step 1618.
To solve the aforesaid problem, the optimal routing can be controlled by the HPMN operator by using the MO-CSI. The optimal routing can be applied when the calling outbound roamer and the receiving call outbound roamer are both on the network of the same group of operators. Therefore, the HPMN (of both roamers) and the HPMN dynamic CAMEL Gateway know the receiving call outbound roamer is not affected by the optimal routed call. If there is a dynamic CAMEL Gateway (maybe centrally) deployed for each operator of the same group, the optimal routed call can also be defined between a local and an outbound roamer of the same group and between an outbound roamer of one operator and an outbound roamer of another operator, all within the same group. The communication between the individual operator dynamic CAMEL gateway can be via a private TCP/IP secure network.
The dynamic CAMEL gateway for optimal routing can control the routing of the call to a special route (using #MSRN) where termination interconnection loss for the VPMN (eg. when the group network or leased-line direct connect is used for interconnection) is not present between the VPMN and the HPMN. It can even be effectively routed to the HPMN via VoIP and routed back to the VPMN via VoIP. Therefore, the total cost for both operators is maintained without losing any service (e.g. ringback tone) for the receiving-call outbound roamers.
After detecting a successful location update at the CAMEL supporting the VPMN of the outbound roamer of certain class (e.g. postpaid or prepaid) at step 1702, the monitoring block provides the IMSI of the outbound roamer to the Dynamic CAMEL gateway at step 1704. The Dynamic CAMEL gateway provides the MO-CSI to the VLR of the outbound roamer either by sending a stand-alone MAP ISD containing the MO-CSI and IMSI to the VLR at step 1706 or by triggering the HPMN HLR to send a stand-alone MAP ISD via the HLR provisioning block at step 1708. The O-CSI for any CAMEL phase will be empty.
When the outbound roamer makes a HPMN international call, the VPMN gsmSSF transfers the call control via a CAP IDP containing the calling party number, the IMSI and the called party number to the HPMN gsmSCF at step 1710. The HPMN gsmSCF interrogates the HLR about the routing number of the called party at step 1712. The HLR provides the routing number (MSRN) to the HPMN gsmSCF at step 1714. The HPMN gsmSCF in turn returns a routing number (#MSRN) dynamically selected from a pool that maps to the real MSRN to the VPMN gsmSSF at step 1716.
The foregoing description describes some of the applications for controlling MT-calls of the outbound roamers using the present invention.
The Dynamic CAMEL gateway provides the MT-CSI to the HPMN HLR of the outbound roamer via the HLR provisioning block at step 1808. To direct a MT call to the outbound roamer, the HPMN GMSC/STP issues a MAP SRI command to the HPMN HLR at step 1810 and gets the MT-CSI from the HPMN HLR at step 1812. The HPMN GMSC/STP issues a CAP IDP containing the calling party number and the called party number to the HPMN gsmSCF at step 1814. When the HPMN gsmSCF receives the MAP ISD, it may send the MAP ISD to the VLR to erase the late call forwarding entry if it was not done while the location update was monitored. The HPMN gsmSCF can dynamically determine late call forwarding numbers from the HPMN HLR using MAP InterrogateSS or SendParameters.
If the outbound roamer is busy, the HPMN gsmSCF returns a RRB (busy/no answer) to the HPMN GMSC/STP at step 1816. The HPMN GMSC/STP issues the MAP SRI to the HPMN HLR again after sometime at step 1818. The HPMN HLR returns a MSRN at step 1820 to which the MT call is routed at step 1822. If the outbound roamer is busy, the VPMN VLR/VMSC issues REL (busy) to the HPMN GMSC/STP at step 1824. The HPMN GMSC/STP issues ERB (busy) to the HPMN gsmSCF to update the availability of the outbound roamer at step 1826. The gsmSCF may then issue Connect (calling party number, FTN of the called party) at step 1828. It may thus be seen from the description of
However, if the outbound roamer is already equipped with a T-CSI, it can be handled via CAP relay through a CAP relay proxy to the HPMN gsmSCF.
When the MT call is to be forwarded to the outbound roamer, it is directed to the HPMN GMSC/STP at step 1908. The HPMN GMSC/STP issues a MAP SRI command to the HPMN HLR at step 1910 and obtains the MT-CSI from the HPMN HLR at step 1912. The HPMN GMSC/STP issues a CAP IDP for the HPMN gsmSCF at step 1914. When the HPMN gsmSCF receives CAP IDP, it checks the blacklist and whitelist to ascertain whether the call is allowed or not. If the call is allowed, it continues the MT call, otherwise it connects to a Voicemail or drops the call at step 1916.
However, if the outbound roamer is already equipped with the T-CSI, it can be handled via CAP relay through a CAP relay proxy to the HPMN gsmSCF.
The HPMN GMSC/STP issues the MAP SRI to the HPMN HLR again at step 2018. The HPMN HLR returns the routing number (MSRN) at step 2020. The HPMN GMSC/STP directs the MT call containing the calling party number and the MSRN to the VPMN VLR/VMSC at step 2022. If the outbound roamer replies, the VPMN VLR/VMSC issues ANM to the HPMN GMSC/STP at step 2024. The HPMN GMSC/STP issues ERB (answer) to the HPMN gsmSCF to start accounting at step 2026. If the call duration exceeds the balance of the outbound roamer, the VPMN VLR/VMSC issues a release command (REL) to the HPMN GMSC/STP at step 2028. The HPMN GMSC/STP issues ERB (answer) to the HPMN gsmSCF to end accounting at step 2030.
However, if the outbound roamer is already equipped with a T-CSI, it can be handled via CAP relay through a CAP relay proxy to the HPMN gsmSCF.
Other Variations
Provided above for the edification of those of ordinary skill in the art, and not as a limitation on the scope of the invention, are detailed illustrations of a scheme for generating and provisioning the CSI of the outbound roamer in a wireless communication network, who has moved onto a VPMN and is detected as being registering with the VPMN. Numerous variations and modifications within the spirit of the present invention will of course occur to those of ordinary skill in the art in view of the embodiments that have now been disclosed. For example, while in the described embodiments, the present invention is implemented primarily from the point of view of GSM mobile networks, the present invention may also be effectively implemented on CDMA, 3G, WCDMA, GPRS, etc., or any other network of common carrier telecommunications in which end users are normally configured to operate within a “home” network to which they normally subscribe, but have the capability of also operating on other neighboring or remote visited networks.
The examples under the present invention, detailed in the illustrative examples contained here, are described using terms and constructs drawn largely from GSM mobile telephony infrastructure. However, use of these examples should not be interpreted to limiting the invention to those media. The capabilities of the visited or non-accustomed network can be of use and provided through any type of telecommunications medium, including without limitation: (i) any mobile telephony network including, without limitation, GSM, 3GSM, 3G, CDMA, WCDMA or GPRS, satellite phones or other mobile telephone networks or systems; (ii) any so-called WiFi apparatus normally used in a home or subscribed network, but also configured for use on a visited or non-home or non-accustomed network, including apparatus not dedicated to telecommunications such as personal computers, Palm-type or Windows Mobile devices; (iii) an entertainment console platform such as Sony Playstation, PSP or other apparatus that are capable of sending and receiving telecommunications over home or non-home networks, or even (iv) fixed-line devices made for receiving communications, but capable of deployment in numerous locations while preserving a persistent subscriber id such as the eye2eye devices from Dlink; or telecommunications equipment meant for voice over IP communications such as those provided by Vonage or Packet8.
In describing certain embodiments of dynamic CSI generation under the present invention, this specification follows the path of a telecommunications call from a calling party to a subscriber or calling party. For the avoidance of doubt, that call can be for a normal voice call, in which the subscriber telecommunications equipment is also capable of visual, audiovisual or motion-picture display. Alternatively, those devices or calls can be for text, video, pictures or other communicated data.
This application claims priority from U.S. Provisional Patent Application Ser. No. 60/657,798 entitled Dynamic CAMEL Approach for Implementing Call Services for Outbound Roamers, filed Mar. 2, 2005, the entirety of which is incorporated herein by reference.
Number | Name | Date | Kind |
---|---|---|---|
5353328 | Jokimies | Oct 1994 | A |
5586166 | Turban | Dec 1996 | A |
5742910 | Gallant et al. | Apr 1998 | A |
5764730 | Rabe et al. | Jun 1998 | A |
5818824 | Lu et al. | Oct 1998 | A |
5854982 | Chambers et al. | Dec 1998 | A |
5901359 | Malmstrom | May 1999 | A |
5903832 | Seppanen et al. | May 1999 | A |
5930701 | Skog | Jul 1999 | A |
5940490 | Foster et al. | Aug 1999 | A |
5943620 | Boltz et al. | Aug 1999 | A |
5953653 | Josenhans et al. | Sep 1999 | A |
5987318 | Alperovich et al. | Nov 1999 | A |
5987323 | Huotari | Nov 1999 | A |
5987325 | Tayloe | Nov 1999 | A |
6014561 | Mölne | Jan 2000 | A |
6052604 | Bishop et al. | Apr 2000 | A |
6058309 | Huang et al. | May 2000 | A |
6075855 | Christiansen et al. | Jun 2000 | A |
6085084 | Christmas | Jul 2000 | A |
6138005 | Park | Oct 2000 | A |
6138009 | Birgerson | Oct 2000 | A |
6148197 | Bridges et al. | Nov 2000 | A |
6163701 | Saleh et al. | Dec 2000 | A |
6185295 | Frederiksen et al. | Feb 2001 | B1 |
6185436 | Vu | Feb 2001 | B1 |
6192255 | Lewis et al. | Feb 2001 | B1 |
6195532 | Bamburak et al. | Feb 2001 | B1 |
6208864 | Agrawal et al. | Mar 2001 | B1 |
6212372 | Julin | Apr 2001 | B1 |
6353740 | Granberg | Mar 2002 | B1 |
6356755 | Valentine et al. | Mar 2002 | B1 |
6356756 | Koster | Mar 2002 | B1 |
6456845 | Drum et al. | Sep 2002 | B1 |
6456859 | Desblancs et al. | Sep 2002 | B1 |
6463298 | Sorenson et al. | Oct 2002 | B1 |
6466786 | Wallenius | Oct 2002 | B1 |
6505050 | Brudos et al. | Jan 2003 | B1 |
6515974 | Inoue et al. | Feb 2003 | B1 |
6574481 | Rathnasabapathy et al. | Jun 2003 | B1 |
6603761 | Wang et al. | Aug 2003 | B1 |
6603968 | Anvekar et al. | Aug 2003 | B2 |
6611516 | Pirkola et al. | Aug 2003 | B1 |
6628934 | Rosenberg et al. | Sep 2003 | B2 |
6636502 | Lager et al. | Oct 2003 | B1 |
6671523 | Niepel et al. | Dec 2003 | B1 |
6684073 | Joss et al. | Jan 2004 | B1 |
6687243 | Sayers et al. | Feb 2004 | B1 |
6693586 | Walters et al. | Feb 2004 | B1 |
6738622 | Stadelmann et al. | May 2004 | B1 |
6738636 | Lielbriedis | May 2004 | B2 |
6764003 | Martshitsch et al. | Jul 2004 | B1 |
6782264 | Anderson | Aug 2004 | B2 |
6795444 | Vo et al. | Sep 2004 | B1 |
6856818 | Ford | Feb 2005 | B1 |
6876860 | Berg et al. | Apr 2005 | B1 |
6920487 | Sofer et al. | Jul 2005 | B2 |
6925299 | Sofer et al. | Aug 2005 | B1 |
6961559 | Chow et al. | Nov 2005 | B1 |
6963543 | Diep et al. | Nov 2005 | B2 |
6968383 | Heutschi et al. | Nov 2005 | B1 |
6975852 | Sofer et al. | Dec 2005 | B1 |
6978156 | Papadopoulos et al. | Dec 2005 | B1 |
7020479 | Martschitsch | Mar 2006 | B2 |
7139570 | Elkarat et al. | Nov 2006 | B2 |
7184764 | Raviv et al. | Feb 2007 | B2 |
7231431 | Sofer et al. | Jun 2007 | B2 |
20020009199 | Ala-Laurila et al. | Jan 2002 | A1 |
20020012351 | Sofer et al. | Jan 2002 | A1 |
20020037708 | McCann et al. | Mar 2002 | A1 |
20020087631 | Sharma | Jul 2002 | A1 |
20020101858 | Stuart et al. | Aug 2002 | A1 |
20020101859 | Maclean | Aug 2002 | A1 |
20020160763 | Mittal et al. | Oct 2002 | A1 |
20020187780 | Souissi | Dec 2002 | A1 |
20020191575 | Kalavade et al. | Dec 2002 | A1 |
20020196775 | Huotori | Dec 2002 | A1 |
20030008643 | Hestir | Jan 2003 | A1 |
20030017843 | Noblins | Jan 2003 | A1 |
20030050047 | Ala-Luukko | Mar 2003 | A1 |
20030051041 | Kalavade et al. | Mar 2003 | A1 |
20030064723 | Thakker | Apr 2003 | A1 |
20030069922 | Arunachalam | Apr 2003 | A1 |
20030087647 | Hurst | May 2003 | A1 |
20030129991 | Allison et al. | Jul 2003 | A1 |
20030133421 | Sundar et al. | Jul 2003 | A1 |
20030139180 | McIntosh et al. | Jul 2003 | A1 |
20030208560 | Inoue | Nov 2003 | A1 |
20030224795 | Wilhoite et al. | Dec 2003 | A1 |
20030227899 | McCann | Dec 2003 | A1 |
20030229791 | De Jong | Dec 2003 | A1 |
20040019539 | Raman et al. | Jan 2004 | A1 |
20040053610 | Kim | Mar 2004 | A1 |
20040082346 | Skytt et al. | Apr 2004 | A1 |
20040087305 | Jiang et al. | May 2004 | A1 |
20040120552 | Borngraber et al. | Jun 2004 | A1 |
20040131023 | Auterinen | Jul 2004 | A1 |
20040132449 | Kowarch | Jul 2004 | A1 |
20040148400 | Mostafa | Jul 2004 | A1 |
20040196858 | Tsai et al. | Oct 2004 | A1 |
20040224680 | Jiang | Nov 2004 | A1 |
20040229601 | Zabawskyj et al. | Nov 2004 | A1 |
20040236836 | Appelman | Nov 2004 | A1 |
20050021834 | Coulombe | Jan 2005 | A1 |
20050047378 | Wuschke et al. | Mar 2005 | A1 |
20050064883 | Heck et al. | Mar 2005 | A1 |
20050070278 | Jiang | Mar 2005 | A1 |
20050186939 | Barnea et al. | Aug 2005 | A1 |
20050186960 | Jiang | Aug 2005 | A1 |
20050186979 | McCann et al. | Aug 2005 | A1 |
20050192007 | Kumar et al. | Sep 2005 | A1 |
20050192035 | Jiang | Sep 2005 | A1 |
20050215250 | Chava et al. | Sep 2005 | A1 |
20050232282 | Silver et al. | Oct 2005 | A1 |
20050250493 | Elkarat et al. | Nov 2005 | A1 |
20060003775 | Bull et al. | Jan 2006 | A1 |
20060009204 | Ophir | Jan 2006 | A1 |
20060025129 | Wolfman et al. | Feb 2006 | A1 |
20060046721 | Sernan-Dez Arppe et al. | Mar 2006 | A1 |
20060052113 | Ophir et al. | Mar 2006 | A1 |
20060068778 | Della-Torre | Mar 2006 | A1 |
20060068786 | Florence | Mar 2006 | A1 |
20060079225 | Wolfman et al. | Apr 2006 | A1 |
20060079236 | Del Pino et al. | Apr 2006 | A1 |
20060148459 | Wolfman et al. | Jul 2006 | A1 |
20060149658 | Smith | Jul 2006 | A1 |
20060205404 | Gonen et al. | Sep 2006 | A1 |
20060211420 | Ophir et al. | Sep 2006 | A1 |
20070021118 | Ophir et al. | Jan 2007 | A1 |
20070049269 | Ophir et al. | Mar 2007 | A1 |
20070054665 | Elkarat et al. | Mar 2007 | A1 |
20070072587 | Della-Torre et al. | Mar 2007 | A1 |
20070178885 | Lev et al. | Aug 2007 | A1 |
20070232300 | Wolfman | Oct 2007 | A1 |
20070259663 | Weintraub et al. | Nov 2007 | A1 |
20080020760 | Elkarat et al. | Jan 2008 | A1 |
Number | Date | Country |
---|---|---|
2281041 | Feb 2001 | CA |
0899 974 | Mar 1999 | EP |
1389024 | Feb 2004 | EP |
2322998 | Sep 1998 | GB |
WO 9826621 | Jun 1998 | WO |
WO 9826626 | Jun 1998 | WO |
WO 0018156 | Mar 2000 | WO |
WO 0051375 | Aug 2000 | WO |
WO 0079761 | Dec 2000 | WO |
WO 0079825 | Dec 2000 | WO |
WO 0122750 | Mar 2001 | WO |
WO 0165884 | Sep 2001 | WO |
WO 0241641 | May 2002 | WO |
WO 02019667 | Jul 2002 | WO |
WO 03019960 | Mar 2003 | WO |
WO 03043367 | May 2003 | WO |
WO 03065660 | Aug 2003 | WO |
WO2004023773 | Mar 2004 | WO |
WO 2004081802 | Sep 2004 | WO |
WO2004075598 | Sep 2005 | WO |
WO2005101857 | Oct 2005 | WO |
WO2008012815 | Jan 2008 | WO |
Number | Date | Country | |
---|---|---|---|
20060240822 A1 | Oct 2006 | US |
Number | Date | Country | |
---|---|---|---|
60657798 | Mar 2005 | US |