Patent Application
20110143754
The present invention generally relates to mobile communication. More specifically, the invention relates to proactive roaming tests for CAMEL voice roaming.
Roaming traffic contributes a significant percentage of an operator's revenue and even a better percentage of the operator's margin. With increasing competition and regulatory control, operators are being more pressured to increase their roaming revenue and reduce roaming margin losses. They need keep a check on roaming quality and fraud control at both, own networks to serve inbound roamers and roaming partner networks to serve outbound roamers, that can directly impact an operator's roaming revenue and margin.
Establishing roaming relationships is essential for operators to achieve roaming revenue in the first place. Such process involves both inbound and outbound roaming tests. These tests are usually only performed prior to the launch of these roaming relationships. However, roaming partners may constantly change network configuration, upgrade new software, add new number ranges, introduce new inter-connection routing or add new network elements. These changes or incomplete or incorrect execution of changes could affect roaming services. Constantly maintaining roaming quality of the services thus will help increase roaming revenue. Also, while roaming represents a substantial revenue source for the operators, it is also subjected to frauds like Subscriber identity module (SIM) box and interconnection frauds.
Camel roaming is essential for prepaid roaming these days. Camel roaming is also becoming more valuable for many advanced value services such as short code, fraud control, misdialed call correction, real-time billing, CLI delivery, home call routing etc for outbound roamers. However, establishing camel roaming is very difficult for operators. Although there does not exist a formal agreement per se, but there are extensive tests that are required to be carried out. This causes significant delays for many operators. Another alternative is where manual testing is done. However, this takes a lot of times although it's a cheaper alternative for some countries.
Automated testing is preferred but generally expensive and even more problematic for continued testing. Such a testing involves remote probes (real or virtual mobile stations) around the world. When a remote probe behaves like a virtual mobile station, a virtual SIM is dynamically slotted in from a central multiplexer of real SIMs to test different types of subscribers for different types of services under some kinds of schedules. However, there are several issues with the remote probes approach. First is coverage issue, as despite increasing coverage in multiple countries and major cities, this approach does not assure covering of home operator's roamer's services in the part that are not covered by these remote probes. The coverage problem also applies to a visiting operator for inbound roamers when the country's expanse is huge such as China, India etc.
Moreover, the operator often cannot afford to continuously test its inbound roaming service availability to accommodate constant changes of network infrastructures including network elements (e.g. VLR/VMSCs) and routing. Another drawback is cost as remote probe vendors need ways to recuperate the cost (e.g. remote probe hardware cost, data center collocation cost including bandwidth and maintenance etc.) for the vast amount of investment for extended coverage. Further, even testing any kind of subscriber (e.g. prepaid, postpaid, Virtual Private Network (VPN), machine-to-machine etc.) is done by providing the corresponding SIM card to the test vendor. It is unlikely that the number of test scenarios is multiplied by the number of profiles because of the costs of these tests, thus making it is hard for the operator to control the quality of service offered to any of the subscribers.
Further, due to its lack of network signaling, remote probe approach is also not quite effective in detecting various revenue affecting services like mentioned above. Further, in terms of providing revenue assurance, owing to the constant changes in IOT tariffs and constant upgrades of billing systems, constant regression tests can help reduce these revenue leaks. However, since remote probes are bottlenecked by their coverage area, unfortunately many countries that are out of the coverage cannot gain benefit of these tests. Further, remote probe approach cannot perform integrated camel testing with operator/network initiated services such as on-demand Operator Determined Barring (ODB), Cancel Location, InsertSusbcriberData (ISD), Immediate Service Termination (IST) and on-demand profile changes.
In accordance with the foregoing, there is a need in the art of a system, a method, and a computer product for creating a solution that gives an operator the ways to deal with above mentioned problems using automated testing mechanisms. The solution can be deployed for one single operator or in a central manner for multiple operators. When solution is used for multiple operators, the deployment can be hub based, where each of these operators can be considered as a club member.
The present invention is directed towards a method for facilitating roaming tests for a club network. The method includes simulating a roamer's profile by a signaling gateway and associating with either a club network or a roaming partner network of the club network. The club network and the roaming partner network correspond to a Home Public Mobile Network (HPMN) and a Visited PMN, respectively, in case the roamer is an outbound roamer. In case the roamer is an inbound roamer, the club network corresponds to the VPMN and roaming partner network corresponds to the HPMN. The method further includes performing by the signaling gateway, one or more CAMEL capability tests on the roamer. The roaming subscriber is associated with either the club network or the roaming partner network.
Another aspect of the invention presents a system for facilitating roaming tests for a club network. The system includes a gateway associated with the club network for simulating a roamer's profile by a signaling gateway and associating with either a club network or a roaming partner network of the club network. The club network and the roaming partner network correspond to a Home Public Mobile Network (HPMN) and a Visited PMN, respectively, in case the roamer is an outbound roamer. In case the roamer is an inbound roamer, the club network corresponds to the VPMN and roaming partner network corresponds to the HPMN. The signaling gateway further performs one or more CAMEL capability tests on the roamer. The roaming subscriber is associated with either the club network or the roaming partner network.
Yet another aspect of the present invention provides a computer program product including a computer usable program code for facilitating roaming tests for a club network. The computer program product includes a signaling gateway that simulates a roamer's profile and associates it with either a club network or a roaming partner network of the club network. The club network and the roaming partner network correspond to a Home Public Mobile Network (HPMN) and a Visited PMN, respectively, in case the roamer is an outbound roamer. In case the roamer is an inbound roamer, the club network corresponds to the VPMN and roaming partner network corresponds to the HPMN. The computer program product further performs by the signaling gateway, one or more CAMEL capability tests on the roamer. The roaming subscriber is associated with either the club network or the roaming partner network.
In the drawings, the same or similar reference numbers identify similar elements or acts.
In the following description, for purposes of explanation, specific numbers, materials and configurations are set forth in order to provide a thorough understanding of the present invention. It will be apparent, however, to one having ordinary skill in the art that the present invention may be practiced without these specific details. In some instances, well-known features may be omitted or simplified, so as not to obscure the present invention. Furthermore, reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure or characteristic, described in connection with the embodiment, is included in at least one embodiment of the present invention. The appearance of the phrase “in an embodiment”, in various places in the specification, does not necessarily refer to the same embodiment.
The present invention provides a system, a method, and a computer program product for facilitating CAMEL roaming tests for both outbound and inbound roamers of a club operator or a club/group of operators using SS7-based signaling and voice processing system at the network side. The method derives from earlier patent application titled “Predictive Intelligence”, by John Jiang, and the primary module (signaling gateway) of the present invention focuses on automated procedure for IREG 32 CAMEL testing on voice part, hence it is hereinafter, interchangeably referred to Predictive Intelligence based Camel Automated Testing module (PI-CAT or CAT) module. The method does not involve any mobile handset, physical SIMs or probes etc. The method also does not require dispatch of a real roamer at a roaming location. Instead, the method involves simulating a camel roamer via signaling at a roaming location in a roaming partner network, using the signaling gateway/CAT module.
A roaming partner network corresponds to a network that has at least one roaming agreement such as, but not limited to, Global System for Mobile communication (GSM), General Packet Radio Services (GPRS), Customized Application for Mobile Enhanced Logic (CAMEL) and Third Generation of mobile (3G) agreement with the club network. It will be apparent to a person skilled in the art that roaming services include standard call and non-call related activities such as, but not limited to, Mobile Originated (MO) call, Mobile Terminated (MT) call, Short Message Service (SMS), Packet Data Network (PDN), and other Value Added Services (VASs) such as call forwarding, call barring etc.
CAMEL is an Intelligent Network (IN) based standard that has a framework to help a network operator to provide the subscribers with the operator specific services even when roaming outside the home network. The primary use of CAMEL is prepaid (outbound) roaming. Unlike a USSD based prepaid roaming solution which is call-back based, CAMEL based prepaid roaming provides a seamless user experience just like normal mobile originated activities (calls, SMS etc). Since signaling control of an outbound roamer's call is passed by the VPMN gsmSSF to the HPMN gsmSCF, the gsmSCF is able to deduce the prepaid roamer's balance appropriately.
Another use of CAMEL is to enable Virtual Home Environment (VHE). Some implementation of VHE services can be like outbound roamers' calls based on home dialing experience (e.g. calls without country codes or home international access prefix, short code calls etc) can be correctly translated to the ones corresponding to the visitor network environment to complete the calls to provide a home-like user experience.
CAMEL is also useful for real-time billing. TAP records between roaming partners can come in as late as a month. Since it is just a wholesale Inter Operator Tariff (IOT) from the TAP exchange that doesn't affect retail IOT, the HPMN can produce retail billing in real-time. CAMEL can be used as well to implement fraud control measures. Operator Determined Barring (ODB) works well on all calls or international call barring while roaming at a VPMN but not well on premium numbers barring at the VPMN since these numbers can change dynamically. By using CAMEL control on an outbound roamer, all the roamer's calls can be restricted according to HPMN application logic.
Other services like selective home routing, least cost routing or CLI delivery or third party partner carrier routing from an outbound roamer can also be implemented using the CAMEL capabilities. In this case, an outbound roamer's call can be selectively routed back to the home network or a partner network based on the called number and the calling network. The selection logic employed by the HPMN gsmSCF can be based on least cost routing or just quality service control (e.g. roaming quality monitoring or for better delivery of caller ID via home or partner network) or lawful interception at home or just simply collect termination charges at home without incurring extra charges to the roamer.
In accordance with various embodiments of the present invention, the method further involves the signaling gateway to perform various CAMEL capability tests via signaling and determines the success or failure of these tests via signaling and intercepting voice circuits to hear “success” or “failure” announcements. Since, the roamer's profile is simulated it can also be changed through signaling. Moreover, all interactions with various components in the club network and the roaming partner network like VLR, HLR and SCP are also simulated.
The club network operator performs the proactive roaming tests by deploying the signaling gateway, either in the club network or outside the club network (at a centralized location, in a hub architecture) having a signaling connection to reach the club network for facilitating roaming tests for different club networks. In this manner, the signaling gateway is able to serve either one club network or multiple club networks (in multi-tenant support) for the CAMEL testing. Each of these different networks for which these tests can be conducted become a part of the club, and are hereinafter interchangeably referred to as club members. Each of these club members may appear as HPMN or VPMN to their respective roaming partners depending on whether the tests are done for outbound roamers or inbound roamers of the club network.
Club PMN 104 further includes a Mobile Switching Center (MSC)/Visiting Location Register (VLR) 106, a Serving GPRS Support Node (SGSN) 108, a Gateway GPRS Support Node (GGSN) 110, a Gateway MSC (GMSC) 112, a roaming Signal Control Point (SCP) 114, a Home Location Register (HLR) 116 and a Short Message Service Center (SMSC) 118. Since network elements MSC/VLR 106, SGSN 108, GGSN 110, GMSC 112, SCP 114, HLR 116 and SMSC 118 reside in Club PMN 104, they are hereinafter referred to as MSC-C/VLR-C 106, SGSN-C 108, GGSN-C 110, GMSC-C 112, SCP-C 114, HLR-C 116 and SMSC-C 118, respectively. These network elements communicate with each other over a Signaling System 7 (SS7) link (represented by dashed lines in
System 100 further includes a roaming partner PMN 120 (i.e., the roaming partner network) that is associated with club PMN 104. It will be apparent to a person skilled in the art that system 100 may include various other roaming partner networks. However, for the sake of convenience, this embodiment considers only one roaming partner network (i.e., roaming partner PMN 120). Roaming partner PMN 120 includes a MSC/VLR 122, a SGSN 124, a GGSN 126, a GMSC 128, an SCP 130, an HLR 132 and an SMSC 134. Since network elements MSC/VLR 122, SGSN 124, GGSN 126, GMSC 128, SCP 130, HLR 132 and SMSC 134 reside in roaming partner PMN 120, they are hereinafter referred to as MSC-R/VLR-R 122, SGSN-R 124, GGSN-R 126, GMSC-R 128, SCP-R 130, HLR-R 132 and SMSC-R 134, respectively. All these network elements of roaming partner PMN 120 communicate with each other over the SS7 link, except that SGSN-R 124 communicates with GGSN-R 126 via the IP link. Further, as shown in
Other network elements of roaming partner PMN 120 (e.g., MSC-R/VLR-R 122) communicate with various other network elements of club PMN 104 (e.g., HLR-C 116) via the SS7 link. It will also be apparent to a person skilled in the art that various components of club PMN 104 communicate with roaming partner PMN 120 using various signaling techniques including, but not limited to, SS7, SIP, IP, ISUP etc.
It will also be apparent to a person skilled in the art that club PMN 104 and roaming partner PMN 120 may also include various other network components (not shown in
The most important CAMEL architecture network elements consist of a GSM Service Control Function (gsmSCF) in club PMN and a GSM Service Switch Function (gsmSSF) in roaming partner PMN. The gsmSCF and gsmSSF communicates with each other using the CAMEL Application Part (CAP). When a CAMEL outbound roamer is registering at a CAMEL partner VPMN VLR, the HPMN HLR of the roamer provides CAMEL Subscription Information (CSI) to the VPMN VLR for the roamer via MAP Insert Subscriber Data (ISD) message.
GSM Association has defined a, IREG specification (IR.32) that defines end-to-end functional capability tests relating to the international roaming of a mobile subscriber to CAMEL services, belonging to an HPMN, to and within a roaming/visited PMN. The fundamental objective of these tests is to confirm the capability of CAMEL services which the subscribers should receive while roaming from their Home network to Visited networks. The overall objective of these tests is to confirm that the CAMEL features, which are known to operate correctly within each separate home network, will also operate correctly while inter-PMN roaming.
There are various types of tests that are defined as per IR.32 standard. Some of them are:
In accordance with various embodiments of the present invention, CAT module 102 addresses all the scenarios listed above from a VPMN-HPMN perspective (not based on mobile station and VPMN VLR perspective).
Furthermore, specific types of tests defined for CAMEL Phase 2 are defined as per the IR.32 standard:
In accordance with various embodiments of the present invention, CAT module 102 also addresses all the scenarios listed above from a VPMN-HPMN perspective (not based on mobile station and VPMN VLR perspective).
In order to test CAMEL roaming services for the inbound and outbound roamers, CAT module 102 simulates the roamer's profile at roaming partner PMN 120. CAT module 102 taps SS7 and IP roaming links between network elements of club PMN 104 and roaming partner PMN 120 in order to monitor roaming signaling traffic and packet data traffic at club PMN 104. Thereafter, CAT module 102 performs various CAMEL capability tests on the roamer. The roaming signaling traffic includes both Signaling Connection Control Part (SCCP) and ISUP traffic. In an embodiment of the present invention, the SCCP and ISUP traffic is transported over an IP interface such as, but not limited to, Signaling Transport (SIGTRAN) protocol, Voice over IP (VoIP) and Real-Time Transport Protocol (RTP). The SCCP traffic includes Mobile Application Part (MAP) traffic, CAMEL Application Part (CAP) traffic and Transaction Capabilities Application Part (TCAP) traffic. CAT module 102 further taps the SS7 link between SCP-C 114 and SCP-R 130 and the ISUP link between GMSC-C 112 and GMSC-R 128, in accordance with another embodiment of the present invention. In one embodiment of the present invention, CAT module 102 passively taps signaling path between the network elements of club PMN 104 and roaming partner PMN 120. In another embodiment of the present invention, CAT module 102 intercepts the signaling path with an address such as a Global Title (GT), a point code or an IP address.
Furthermore, in an embodiment of the present invention, CAT module 102 performs roaming signaling traffic and packet data traffic exchange between club PMN 104 and roaming partner PMN 120 for club PMN 104's outbound and inbound roamers. Additionally, in another embodiment of the present invention, CAT module 102 is connected with the network elements of club PMN 104 internally (e.g., communicates with GMSC-C 112 via the ISUP link and communicates with MSC-C/VLR-C 106 via the SS7 link).
Now, in order to facilitate various roaming tests for club PMN 104 operator, CAT module 102 needs to create test profile at a MSC/VLR location of the roaming subscriber and then conduct various CAMEL capability tests on the roaming subscriber.
CAT module 102, first creates fake roamer's (IMSI) location and validates the same with club PMN 104, using Location Update (LUP) and Insert Subscriber's Data (ISD) messages between steps 302 and 308. The LUP is done using the IMSI exchanged between the club networks and roaming partner network. CAT module 102 then validates if the roamer has the right camel profile to be tested by sending signaling messages such as a MAP Provide_Roaming_Number (PRN), a MAP Insert Subscriber Data (ISD) and a MAP_RESTORE_DATA (RSD)-ACK on the test IMSIs to any MSC/VLR of roaming partner PMN 120 (e.g., MSC-R/VLR-R 122). Hence, at step 310, CAT module 102 sends MAP Providing Roaming Number (PRN) message to the roaming partner PMN's VLR-R 122. Thereafter, at step 312, VLR-R 122 then triggers MAP RestoreData (RSD) to CAT module 102 which then relays the request to the HLR-C 116. CAT module 102 can modify profile messages as it relays from HLR-C 116 to VPMN VLR-R 122. Finally, at step 314, CAT module 102 also obtains the MSRN (Mobile Station Roaming Number) for subsequent call tests in response to the PRN message to VLR-R 122.
Similarly, to test the Connect operation, CAT module follows on from steps of
Similarly, in order to test interaction of MAP PSI subscriber state with CAMEL operation, CAT module 102, at step 1302, issues a MAP PSI on the outbound roamer's IMSI on state. If at step 1304, the PSI returns the same subscriber state (i.e. unreachable) as that of the IDP for the trigger reason, then CAT module 102 at step 1306, issues a CAP Continue message in response to the IDP message. Then at step 1308, CAT module 102 receives an ISUP (CAT#) with FTN as CAT#. Otherwise, at step 1310, CAT module 102 issues a CAP Release Call message in response to the IDP message; then CAT module 102 receives an ISUP REL message at step 1312.
In first embodiment, CAT module 102 tests interactions of MAP Barring All
Outgoing Calls messages (BAOC) with CAMEL operation. CAT module 102 follows on from the steps of
In second embodiment, CAT module 102 tests interactions of MAP Barring All International Calls messages (BAIC) with CAMEL operation. In this embodiment, steps 1402 and 1404 remain same as the first embodiment, where CAT module 102 receives the IDP message. Thereafter, at step 1406, CAT module 102 can either issue CAP Connect (local#) message, where local# is a local known answerable number in VPMN 120 country. In that case, CAT module 102 receives an ISUP ANM message at step 1408. In an alternative case, at step 1406, CAT module 102 issues a CAP Connect (CAT#) message, where CAT# is an international number from VPMN 120 country. In that case, at step 1408, CAT 102 receives and ISUP REL message.
In third embodiment, CAT module 102 tests interactions of MAP Barring All International Calls except home message (BAIC-Ex Home) with CAMEL operation. In this embodiment again, steps 1402 and 1404 remain same as the first and second embodiment, where CAT module 102 receives the IDP message. Thereafter, at step 1406, CAT module 102 can either issue a CAP Connect (home#) message, where home# is a home known answerable number in HPMN 104 country. In that case, CAT module 102 receives an ISUP ANM message. In an alternative case, at step 1406, CAT module 102 issues a CAP Connect (3rd Country#) message, where 3rd Country# is an answerable non-HPMN country international number from VPMN 120 country. In that case, at step 1408, CAT module 102 receives an ISUP REL message.
It will be apparent to a person skilled in the art that inbound testing with club member is same as outbound testing and in the present invention only inbound testing with roaming partners is considered. Since HPMN has the liability, HPMN can dictate the set of tests required. In case of inbound testing, HPMN is roaming partner PMN 120, while club member, i.e., club PMN 104 becomes the VPMN. This means roaming partners will control the service logic and acceptable results. However, CAT module 102 can still create the preconditions and actions of many IR. 32 test cases for roaming partner's service logics. CAT module 102 will additionally include a voice recognition capability to determine success or failure of the tests.
In various implementations of the inbound testing cases, the present invention does not require physical SIMs, or service logics from roaming partners. However it uses the various IMSI profiles from the roaming partners. The roaming partners are required to only do the IR. 21 configurations and routing.
Once the inbound roamer's profile is created and validated at club PMN 104, in order to test various CAMEL capability tests, service logics etc. of IR. 32 specification is followed. CAT module 102 automates the requirements laid out in IR. 32 specification on behalf of the club member networks.
In order to validate IDP parameters in CAMEL trigger of the simulated inbound roamer, following table provides the IDP test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test CAMEL CONNECT operations for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test CAMEL CONTINUE operation for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test CAMEL CONTINUE operation, CAT module 102 first simulates the effect of an inbound roamer ‘a’ making a test call to a local # (say b) or CAT#. Although CAT module 102 is not involved with CAP signaling as the service logic is defined by roaming partner network 120, CAT module 102 still examines whether tests are successful or not based on whether it hears “success” or “failure” of the test result, as CAT module 102 simulates a calling device and contains a voice recognition unit. Hence in this case, at step 1808, when the VLR-C 106 sends the IDP message with all parameters, then according to IR.32 CONTINUE service logic, CAT module 102 creates an effect that called party (i.e. b) answered the call and then CAT module 102 sends a RELEASE message to disconnect the call. Hence, the CAMEL CONNECT operation is validated.
In order to test CAMEL DCH-CONTINUE/RELEASE operations for the simulated inbound roamer, following tables provide the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
Likewise, in order to test CAMEL DCH RELEASE operation, CAT module 102 first simulates the effects of an inbound roamer making a test call to expected answer number AAC2. In this case, according to IR.32 service logic for DCH RELEASE operation, if CAT module 102 receives a RELEASE message without hearing “success” for Test Announcement 2, then DCH RELEASE operation is considered validated. Else if CAT module 102 receives an Answer, then the test operated is considered to be failed.
In order to test MAP PSI subscriber unreachable/busy operations for the simulated inbound roamer, following tables provide the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
Likewise, in order to test interaction of MAP PSI subscriber BUSY operation, CAT module 102 first simulates the effects of an inbound roamer ‘a’ making a test call to another inbound roamer ‘b’, such that the roamer ‘b’ is shown busy by creating the roamer's FTN point to the other number. As this other number is determined by roaming partner network 120, it can arrange to have the other number always busy. When SCP-R 130 is checking the subscriber state of the second number, the number comes as busy. SCP-R 130 is expected to answer the call based on the subscriber state. Although CAT module 102 is not involved with CAP signaling, CAT module 102 still examines whether it hears “success” or “failure” of the test result. Hence in this case, at step 2012, when the VLR-C 106 sends the IDP message with all parameters, then according to IR.32 MAP PSI Busy test logic, if the subscriber state in ATI result equals busy, then SCP-R 130 alters the destination address to Test Announcement 1. Thereafter, at step 2014, if CAT module 102 hears “success” in the Answer message, the CAMEL MAP PSI busy operation is validated.
In accordance with an embodiment of the present invention, if HPMN can change the PSI testing on busy to PSI testing on network unreachable, then this test or mobile usage can be eliminated. Just like call forwarding on busy is optional, the PSI testing on busy can be optional too and just PSI testing on network unreachable state should be sufficient. Otherwise, the usage of mobile can just be set up once for all club members' PSI busy test at any place while CAT module 102 can still test against all switches and VLRs of club members. If there is an automated tool such as “Sigos” or “Datamat” to set up such a busy call on roamer ‘b,’, then it is simpler.
In order to test Event ANSWER/DISCONNECT operation for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test Call Forwarding on Unreachable/No-answer operation for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test SS/ODB call barring operation for the simulated inbound roamer, following tables provide the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test IDP Phase 2 operation for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test FCI on No-Answer, Unreachable, Busy and Route-Select-Failure operation for the simulated inbound roamer, following tables provide the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
In order to test FCI on No-answer operation, CAT module 102 simulates the effects of an inbound roamer ‘a’ making a call to a local mobile that is not answering, through ISD and IAM messages as shown at steps 2502 to 2506. In the case, CAT module 102 faking the local mobile. Roaming partner network's 120 service logic is expected to request no-answer event and continue the call. At step 2508, CAT module 102 receives an IAM message. At step 2510, CAT module 102 release the call with a cause (NO-ANSWER) as it is faking the local mobile. HPMN service logic expects to connect the inbound roamer call to AAC1. Although CAT module 102 is not involved with CAP signaling, CAT module 102 still examines whether tests are successful or not based on whether it hears “success” or “failure” of the test result. The charging action can be used to verify TAP information.
Similarly, for testing FCI on Busy/Unreachable/Route-select-failure operation, CAT module 102 again simulates the effects of an inbound roamer ‘a’ making a call to a local mobile that is busy or not reachable or not routable in VPMN. In the case, CAT module 102 is faking the local mobile. HPMN service logic is expected to request busy/unreachable/route-selection-failure event and continue the call. In this case to, when CAT module 102 receives an IAM message, it releases it with a cause (busy/unreachable/not routable) as it is faking the local mobile. Although CAT module 102 is not involved with CAP signaling, it still examines whether tests are successful or not based on whether it hears “success” or “failure” of the test result.
In order to test reporting accuracy, credit balance accuracy and tariff switching for Call Information (CI) request and report, Send Charging Information (SCI) and Apply Charging request and report, operations for the simulated inbound roamer, following tables provide the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
Similarly, while determining tariff switching accuracy test, CAT module 102 examines whether tests are successful or not based on whether it hears “success” after about 30 secs or failure of the test result. Likewise, while determining credit balance accuracy, CAT module 102 examines whether tests are successful or not based on whether it hears “success” after about 10 secs and call is released after about 40 secs or failure of the test result.
In order to test interaction of ETC (Establish Temporary Connection), ARI (Assist Resource Instruction), CTR (ConnectToResource) and PA (Prompt Announcement) operations for the simulated inbound roamer, following table provides the test case as per IR. 32 with pre-condition, action, service logic and expected results and some comments.
It will be apparent to a person skilled in the art, that the present invention can also be applied to Code Division Multiple Access (CDMA)/American National Standards Institute #41 D (ANSI-41D), and various other technologies such as, but not limited to, VoIP, WiFi, 3GSM and inter-standard roaming. In one exemplary case, a CDMA outbound roamer travels with an HPMN CDMA handset. In another exemplary case, the CDMA outbound roamer travels with an HPMN GSM SIM and a GSM handset. In yet another exemplary case, GSM outbound roamer travels with an HPMN CDMA RUIM and a CDMA handset. To support these variations, CAT module 102 will have a separate SS7 and network interfaces, corresponding to both the HPMN and VPMN networks. It will also be apparent to a person skilled in the art that these two interfaces in different directions may not have to be the same technologies. Moreover, there could be multiple types of interface in both directions.
An exemplary list of the mapping between GSM MAP and ANSI-41D is described in the table below as a reference.
The present invention can take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment containing both hardware and software elements. In accordance with an embodiment of the present invention, software, including but not limited to, firmware, resident software, and microcode, implements the invention.
Furthermore, the invention can take the form of a computer program product, accessible from a computer-usable or computer-readable medium providing program code for use by, or in connection with, a computer or any instruction execution system. For the purposes of this description, a computer-usable or computer readable medium can be any apparatus that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
The medium can be an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system (or apparatus or device) or a propagation medium. Examples of a computer-readable medium include a semiconductor or solid state memory, magnetic tape, a removable computer diskette, a random access memory (RAM), a read-only memory (ROM), a rigid magnetic disk and an optical disk. Current examples of optical disks include compact disk-read only memory (CDROM), compact disk-read/write (CD-R/W) and Digital Versatile Disk (DVD).
The components of present system described above include any combination of computing components and devices operating together. The components of the present system can also be components or subsystems within a larger computer system or network. The present system components can also be coupled with any number of other components (not shown), such as other buses, controllers, memory devices, and data input/output devices, in any number of combinations. In addition, any number or combination of other processor-based components may be carrying out the functions of the present system.
It should be noted that the various components disclosed herein may be described using computer aided design tools and/or expressed (or represented), as data and/or instructions embodied in various computer-readable media, in terms of their behavioral, register transfer, logic component, transistor, layout geometries, and/or other characteristics. Computer-readable media in which such formatted data and/or instructions may be embodied include, but are not limited to, non-volatile storage media in various forms (e.g., optical, magnetic or semiconductor storage media) and carrier waves that may be used to transfer such formatted data and/or instructions through wireless, optical, or wired signaling media or any combination thereof.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense as opposed to an exclusive or exhaustive sense; that is to say, in a sense of “including, but may not be limited to.” Words using the singular or plural number also include the plural or singular number respectively. Additionally, the words “herein,” “hereunder,” “above,” “below,” and words of similar import refer to this application as a whole and not to any particular portions of this application. When the word “or” is used in reference to a list of two or more items, it covers all of the following interpretations: any of the items in the list, all of the items in the list and any combination of the items in the list.
The above description of illustrated embodiments of the present system is not intended to be exhaustive or to limit the present system to the precise form disclosed. While specific embodiments of, and examples for, the present system are described herein for illustrative purposes, various equivalent modifications are possible within the scope of the present system, as those skilled in the art will recognize. The teachings of the present system provided herein can be applied to other processing systems and methods. They may not be limited to the systems and methods described above.
The elements and acts of the various embodiments described above can be combined to provide further embodiments. These and other changes can be made in light of the above detailed description.
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 proactive roaming tests, discoveries of roaming partner services and discoveries of frauds in roaming using simulated roaming traffic. 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 been disclosed. For example, the present invention is implemented primarily from the point of view of GSM mobile networks as described in the embodiments. However, the present invention may also be effectively implemented on GPRS, 3G, CDMA, WCDMA, WiMax 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 networks, which may even be across international borders.
The examples under the system of present invention detailed in the illustrative examples contained herein are described using terms and constructs drawn largely from GSM mobile telephony infrastructure. However, use of these examples should not be interpreted as limiting the invention to those media. The system and method 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 the system under the present invention, this specification follows the path of a telecommunications call, from a calling party to a called party. For the avoidance of doubt, such a call can be 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.
In the foregoing specification, specific embodiments of the present invention have been described. However, one of ordinary skill in the art will appreciate that various modifications and changes can be made without departing from the scope of the present invention as set forth in the claims below. Accordingly, the specification and the figures are to be regarded in an illustrative rather than a restrictive sense, and all such modifications are intended to be included within the scope of present invention. The benefits, advantages, solutions to problems, and any element(s) that may cause any benefit, advantage, or solution to occur, or to become more pronounced, are not to be construed as a critical, required, or essential feature or element of any or all of the claims.
Technical references, each of which is incorporated by reference in its entirety herein:
This application claims the benefit of U.S. Provisional Patent Application No. 61/267,169 titled “Predictive Intelligence as the Basis of Automated CAMEL Testing for Voice Roaming” filed on Dec. 7, 2009, and the benefit of U.S. Provisional Patent Application No. 61/361,136 titled “Advanced Predictive Intelligence” filed on Sep. 30, 2010. This application is also a continuation in part of U.S. patent application Ser. No. 12/219,622 titled “Predictive Intelligence” filed on Jul. 24, 2008. Each of the preceding applications is incorporated by reference in its entirety herein.
| Number | Date | Country | |
|---|---|---|---|
| 61267169 | Dec 2009 | US | |
| 61361136 | Jul 2010 | US |
| Number | Date | Country | |
|---|---|---|---|
| Parent | 12219622 | Jul 2008 | US |
| Child | 12962317 | US |
