[go: up one dir, main page]

WO2006099389A2 - Procede, systeme et produit de programme informatique permettant de contrecarrer une redirection anti-trafic - Google Patents

Procede, systeme et produit de programme informatique permettant de contrecarrer une redirection anti-trafic Download PDF

Info

Publication number
WO2006099389A2
WO2006099389A2 PCT/US2006/009064 US2006009064W WO2006099389A2 WO 2006099389 A2 WO2006099389 A2 WO 2006099389A2 US 2006009064 W US2006009064 W US 2006009064W WO 2006099389 A2 WO2006099389 A2 WO 2006099389A2
Authority
WO
WIPO (PCT)
Prior art keywords
vpmn
hpmn
time interval
configurable
lup
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2006/009064
Other languages
English (en)
Other versions
WO2006099389A3 (fr
Inventor
Yeu Jun Jiang
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Roamware Inc
Original Assignee
Roamware Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Roamware Inc filed Critical Roamware Inc
Publication of WO2006099389A2 publication Critical patent/WO2006099389A2/fr
Anticipated expiration legal-status Critical
Publication of WO2006099389A3 publication Critical patent/WO2006099389A3/fr
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
    • H04W8/08—Mobility data transfer
    • H04W8/12—Mobility data transfer between location registers or mobility servers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections

Definitions

  • the present invention relates to traffic redirection in a wireless network. More particularly the invention discloses a method, system and program product to counter anti-traffic redirection mechanisms.
  • a network operator may be providing one or more of voice/data service using one or a combination of the aforementioned technologies.
  • various geographical zones are allotted to one or more network operators. These operators usually provide competitive services in their zone. A particular network operator may be present in more than one geographical zone.
  • the network operators In order to provide seamless service to a subscriber, the network operators not only cater to the subscribers directly registered with them but also to their subscribers from other zones and/or the subscribers of other network operators with whom they have a "roaming" agreement. Often, those roaming arrangements are bilateral, such that the subscribers of each geographically diverse operator are enabled to receive roaming service within the zone of the other operator.
  • the network with which the subscriber has a direct relationship is called the subscriber's Home Network. Any other network in which the user may roam is called the Visiting Network.
  • the subscriber is referred to as an outbound roamer from the perspective of the Home Network and an inbound roamer from the perspective of the Visited Network.
  • the home network of the roaming user may prefer one visited network over another, or may want to allocate varying percentages of their outbound roamers' traffic to different operators.
  • Various factors such as commercial terms, quality of service, range of service and the like would dictate such a preference or roaming distribution. Under ideal scenario the home network would make all possible efforts to ensure that its outbound roamers register to the visited network operator that it prefers in that case.
  • TR Traffic Redirection
  • SoR Steering of Roaming
  • MAP Mobile Application Part
  • preferred network is used herein, to refer either static preferences of one network over another or dynamic preference of one network over another based on some logics or distribution (e.g. subscriber profiles, the visiting country, current distribution of outbound roamers in the country).
  • FIGURE 1 is a block diagram of an embodiment of the anti-anti-Traffic
  • FIGURE 2 is a flowchart illustrating the method for countering an anti-TR approach, as per some embodiments of the invention.
  • FIGURE 3 shows the signal flow for countering an anti-TR approach that fakes manual mode of the handset or fakes the scenario of being the only network available.
  • FIG. 4 shows the signal flow for countering an anti-TR approach that fakes the presence of a special handset.
  • FIG. 5 shows the signal flow for countering a GLR based anti-TR.
  • a method for detecting the anti-TR mechanism and redirecting the roamer to a preferred network detects the presence of an anti-TR solution by observing one or more registration messages exchanged by a visiting network and a home network. The method includes steps to steer the roamer to reattempt connection with the preferred networks by sending appropriate registration response messages in response to the observed registration messages.
  • the invention also discloses a system for detecting the anti-TR mechanism and redirecting the roamer to a preferred network.
  • the system includes a probing block to observe the registration messages exchanged between the Home Network and the Visiting Network.
  • the system further includes a detection block to detect the presence of an anti-TR mechanism deployed at the visiting network, based on the registration messages as observed by the probing block.
  • the invention also provides for a redirection module that attempts to redirect the roamer to attempt reconnection with a preferred visiting network.
  • the invention is being described with GSM as the underlying technology and focus, the inventive concept is equally applicable in other wireless technologies such as CDMA, WCDMA, WiFi, WiFiMax, VoIP etc.
  • the home network has been referred to as Home Public Mobile Network (HPMN) and the visiting network has been referred to as Visiting Public Mobile Network (VPMN).
  • the HPMN and VPMN may both have more than one network operators wherein the HPMN may prefer certain VPMN network operators to the others.
  • HPMN/ HPMN network / HPMN network operator and VPMN / VPMN network / VPMN network operator have been used interchangeably throughout this specification and their intended meaning is driven by the context in which they have been used.
  • the term subscriber is used herein to indicate a user that registers with a network.
  • the subscriber that registers with a network can be any combination of hardware and software capable of registering on a wireless network, e.g., a personal digital assistant (PDA) or a personal computer (PC).
  • PDA personal digital assistant
  • PC personal computer
  • the methods and system disclosed herein use the Mobile Application Part (MAP)-signaling messages exchanged between the VPMN and the HPMN to detect any anti-TR solutions deployed by the visiting network and thereafter steer the roamer to attempt reconnection with the preferred network.
  • MAP Mobile Application Part
  • FIG. 1 illustrates a block diagram of a system in accordance with an embodiment of the present invention.
  • System comprises a HPMN 102 communicating with VPMNs 104 and 106 via a SS7 interface 108.
  • VPMN 106 is the preferred VPMN and VPMN 104 is the non-preferred VPMN that has deployed an anti-TR solution.
  • HPMN 102 comprises an anti-anti-TR block 110, an HPMN Roaming Signal Transfer Point (STP) 112, and an HPMN HLR 114.
  • Anti-anti-TR block 110 and HPMN HLR 114 are coupled to HPMN Roaming STP 112.
  • Anti-anti-TR block comprises of three modules, a probing block 110a, a detecting block 110b and a redirecting block 110c. The functions of these blocks has been discussed in detail below. These blocks are logical blocks and may be present as one single entity or may be formed by one or more logical/physical entities.
  • System further comprises an international STP 116, corresponding with HPMN 102, to route the signals to another international STP 118 that corresponds with VPMNs 104 and 106.
  • VPMN 104 comprises a VPMN STP 120 coupled to a VPMN VLR ⁇ /MSC 122.
  • VPMN 106 and other VPMNs would also have a similar structure (not shown in this diagram).
  • HPMN Roaming STP 112 communicates with VPMN STP 120 and VPMN STP 124 via international STP 116, SS7 interface 106 and international STP 118.
  • the aforesaid embodiment is described using the blocks pertinent to the invention, however various other blocks may be present in HPMN and VPMNs.
  • the HPMN 102 may deploy a TR solution so as to steer its outbound roamers to its preferred VPMNs 106.
  • the non-preferred VPMNs 104 may deploy anti-TR solutions that would try to pull the inbound roamers on to their networks.
  • the anti-TR solution is deployed in the VPMN 104 network either by monitoring the roaming MAP transactions and injecting spurious messages or by intercepting the roaming MAP transactions and faking interactions as if from the roaming handset or the real VPMN
  • the invention discloses two possible modes of operation of the anti-anti-TR solution i.e. the monitoring approach and the in-signaling approach.
  • anti-anti-TR module 110 detects the anti- TR attempt by monitoring passively the exchange of at least one registration message between HPMN 102 and VPMN 104.
  • probing block 110a observes the registration messages exchanged between HPMN 102 and VPMN 104.
  • the detecting block 110b detects an anti-TR attempt, by observing the type and frequency (explained in detail below) of messages exchanged between HPMN 102 and VPMN 104.
  • at least one registration message is a Location Update (LL ) P) message.
  • anti-anti-TR module 110 detects an anti-TR attempt by actively monitoring the signaling between HPMN 102 and VPMN 104.
  • the anti-anti-TR block actively monitors the exchange of at least one registration message between HPMN 102 and VPMN 104.
  • Active monitoring is hereinafter referred interchangeably as in-signaling mode.
  • the anti-anti-TR block 110 is deployed on roaming SS7 path by configuring HPMN's 102 roaming STP 112 to route roaming SCCP traffic through anti-anti-TR module 110.
  • FIGURE 1 depicts both the monitoring based and in-signaling path based anti- anti-TR architecture.
  • monitoring-based anti-anti-TR solution there will be an additional tapping of international roaming links between HPMN and international signal carriers.
  • in-signaling path based anti-anti-TR solution roaming SS7 messages from any VPMN are redirected thru the anti-anti-TR block 110 by the HPMN Roaming STP 112.
  • the anti-anti-TR detection mechanism will receive an outbound roamer's Location update transaction between VPMN 104, 106 and HPMN 102. In both cases however, the anti-anti-TR block 110 will inject or modify MAP transactions on outbound roamers.
  • HPMN TR/anti-anti-TR solution and the success of the VPMN anti-TR solution. If the roamer failed to register on the VPMN network 104 after the anti-anti-TR solution, then HPMN 102 can deduce the success of the HPMN TR/anti-anti-TR solution and the failure of the VPMN anti-TR solution.
  • TR/anti-anti-TR HPMN 102 can produce all kinds of reports such as signaling load overhead, TR/anti-anti-TR success/failure, percentage of redirected outbound roaming traffic etc.
  • the anti-TR solution deployed by VPMN 104 may take one or more approaches. We now explain each of these approaches and how the instant invention's anti-anti-TR solution counters each of these approaches.
  • a basic idea for implementing an anti-TR solution at a VPMN is to fool the HPMN TR to think that the handset is operating in manual mode or the VPMN is the only network in coverage. This is achieved by repeatedly sending a location update on the same network location despite more than 4 location update rejections from the HPMN TR already.
  • inter-location update intervals are very unpredictable. These intervals not only vary among different handset types, but also can have a small range even for the same handset type. It is also possible that inter network location update intervals can vary between different operators/networks. Furthermore, inter network location update intervals might also vary among different handset types but also can have a small range even for the same handset type.
  • the most likely scenario for an anti-TR solution to do by a VPMN, after suspecting the response to the first location update from the device is a TR attempt, is to fairly rapidly fire one or more location update in succession, on the same VMSC/VLR on behalf of the inbound roaming device at the VPMN.
  • the anti-TR solution fires 3 more location updates after the first TR reject, then the total TR rejects will be 4.
  • the handset will then try another location update on the same location; the HPMN TR solution will allow the location update.
  • the anti-TR solution fires one more location update after the first reject, then the total TR rejects will be 2 at the moment.
  • the handset will then try 3 more location updates on the same location.
  • the HPMN TR solution will allow the last location update normally.
  • FIG. 1 illustrates some countering approaches for an anti-TR solution deployed by non-preferred VPMN 104.
  • Figure 2 shows these approaches in conjunction with each other. However these individual approaches may be implemented in isolation or in any combination alongwith other approaches for anti- anti-TR.
  • the anti-anti-TR block 110 receives LUP messages by either monitoring the SS7 link between the Roaming STP 112 and International STP 116 or by the redirected messages from roaming STP 112.
  • the LUP messages from a particular IMSI are received at step 201.
  • LUP reject counter 204 but sends a LUP reject 205. If the LUP is received after the threshold time either HPMN 102 may acknowledge the same or may opt to check for other anti-TR approaches 206.
  • the anti-anti-TR block 110 can detect if the interval between location updates of the same outbound IMSI is shorter than the configurable threshold time interval. When a new location update comes within such a configurable threshold time interval, the TR rejection to the location update is not counted in the rejection counter. In this way, even though the anti-anti-TR enhanced HPMN TR might have received 5 consecutive Location Update attempts from the same IMSI on the same VMSC/VLR 122, it will not treat the roaming device in manual mode and will continue to reject the LUP when some of the inter-LUP attempts come within the configurable threshold time interval.
  • the configurable threshold time interval may be changed periodically.
  • anti-anti-TR block 110 may statistically change the configurable threshold time interval over a period of time. This statistical calculation may be based on the frequency of LUPs received from various VMSC/VLR. Such a solution provides robustness against anti-TR solution detecting the configurable threshold time interval.
  • FIG. 3 shows the exchange of signals for the aforementioned scenario.
  • a mobile station / handset initiates registration with a non-preferred VPMN 104.
  • VPMN 104 sends a LUP 302 to HPMN 102.
  • HPMN Since HPMN has deployed a TR solution, it refuses the update and sends a LUP reject message 303.
  • the anti-TR solution of VPMN 104 detects the TR 304 and sends 3 more LUP messages 305 from same IMSI/VLR or may set the Calling Party Address (CgPA) as VLR.
  • CgPA Calling Party Address
  • VPMN 104 since VPMN 104 cannot hold on to the mobile station for long as the roamer may initiate a new location LUP manually in the mean time, therefore VPMN 104 sends further LUP messages in quick succession.
  • anti-anti-TR block 110 Upon receipt of a consecutive LUP message from same VMSC/VLR, anti-anti-TR block 110 would check if it has come within the configurable threshold time interval. If it has, then anti-TR would be detected 306 and LUP rejection error would be sent 307, without incrementing the LUP rejection counter. This way the mobile station would effectively be reinitiating the registration process in a normal manner 308 despite of anti-TR solution intercepting in between. [0044]This anti-anti-TR solution works in both the in-signaling path mode of TR and the monitoring mode of TR.
  • the HPMN 102 anti-anti-TR block 110 on receipt of an LUP from an IMSI/VLR 201 , would check if it is received after a threshold time period after the last LUP 207.
  • This threshold time period is a configurable extended time period up to which HPMN 102 would wait without assuming the mobile station to be a special handset and therefore issue an LUP ack.
  • this configurable extended time period may be about 2 (or more) times of the normal interval (e.g. 30secs, configured by the anti-anti-TR solution) between location updates. If the LUP is received within the extended time period, anti-anti-TR 110 would still reject the LUP.
  • HPMN 102 will only wait for this extended interval for a configurable number (e.g. 1) of times, in general, less than 2 times. Therefore once it is determined 208 that the LUP is received within the configurable extended time interval, it is checked if the extended time interval has been exercised more than the configurable number of times 209. If yes 211, then a LUP ack is sent 212 to VPMN 104. If no 210, then a LUP reject is sent 205 and the extended time interval counter is incremented by one (not shown in figure).
  • a configurable number e.g. 1
  • FIG. 4 shows the exchange of signals for the aforementioned scenario.
  • the mobile station initiates registration with VPMN 104 and VPMN 104 sends LUP (with IMSI and VLR information) message 402 to HPMN 102. Since HPMN 102 deploys TR, it rejects the LUP received 403 from a non-preferred VPMN 104. This way VPMN 104 detects the presence of a TR solution 404. Thereafter anti-TR block of VPMN 104 drops LUP messages from same IMSI for 'n 1 number of times 405 and follows it up by sending a LUP message 406 thereby extending the period between two consecutive LUPs so as to fool HPMN 102 to treat the mobile station as special handset.
  • LUP with IMSI and VLR information
  • HPMN 102 still sends a reject message 408 to VPMN 104. . This way the mobile station would effectively be reinitiating the registration process in a normal manner 409 despite of anti-TR solution intercepting in between.
  • HPMN's 102 anti-anti- TR solution 110 would check if a first successful location update of an outbound roamer on VPMN 104 is followed by a subsequent location update for the same IMSI on same VPMN 104 or any other VPMN, within a configurable time interval 213, for example 10 minutes.
  • HPMN 102 also checks if similar non-receipt of LUPs has been happening for many subscribers 216 on a particular VPMN 104. The number of subscribers for checking this condition may either be a fixed number, which in a very watchful mode maybe 1 i.e.
  • the number of subscribers to be checked maybe a ratio of the total number of subscribers registered with the particular VPMN 104. If the above two conditions are not satisfied i.e. subsequent LUPs have been received 214 and even if they have not been received from few IMSI 217, then HPMN 102 assumes no GLR based anti-TR solution deployed. However, if it is found that subsequent LUPs have not been received within the configurable time 215 and the same has been happening for a number of subscribers 219 then HPMN 102 would send a Cancel Location message 219 to IMSI.
  • the anti-anti-TR solution will wait for a configurable interval (for example 10 minutes) to issue a MAP Cancel- Location each time a location update at the VPMN (found out to be deploying GLR based anti-TR) from an outbound roaming device is successful.
  • a configurable interval for example 10 minutes
  • the Home Location Register (HLR) of the roaming device still has the real VPMN VLR/VMSC entry. In this way, for any Mobile Originated (MO)-activity with the VPMN 1 the handset will be forced to make a new location update on the VPMN.
  • MO Mobile Originated
  • the HPMN HLR will issue MAP PRN to the outbound roamer's real VLR, which returns the MSRN. If the VPMN VLR entry of the roamer is empty, the VPMN VLR will issue a MAP RestoreData to HPMN HLR. The anti-anti-TR solution will wait for a configurable interval to issue another MAP Cancel-Location on the outbound roamer to the VPMN VLR after the RestoreData.
  • the HPMN HLR will return the outbound roamer's real VPMN VMSC to the originating SMSC. The originating SMSC will then send the message to the real VPMN VMSC. If the VPMN VLR entry is empty, the SMSC will receive an error ack and can then report the delivery status to the roamer's HPMN HLR for future delivery.
  • FIG. 5 shows the exchange of signals for the aforementioned scenario.
  • a roaming mobile station registers with VPMN 104.
  • VPMN 104 sends a LUP message 501 to HPMN 102.
  • the location Update profile of the roamer sent by HPMN 102 is stored by VPMN at GLR 503. Thereafter for very subsequent LUP from IMSI, VPMN 104 would use the stored profile to acknowledge.
  • HPMN 102 Upon discovering that no subsequent LUPs have been received from an IMSI after a successful LUP and a similar occurrence for a number of IMSIs on same VPMN 104, HPMN 102 deduces that a GLR based anti-TR solution has been deployed 504. It then sends a Cancel Location message 505, 506 to the IMSI who have not been updated for a long period of time on VPMN 104 having GLR based anti-TR solution.
  • a Roaming Restricted error code can also be used is response to a LUP message. Although this temporarily, puts the network location area as forbidden in the handset, it results in a faster network reselection.
  • the anti-TR solution can perform just TCAP abort or just TCAP reject the Roaming Restricted in the MAP ISD message with unexpected data value or unsupported service etc in ISD ACK.
  • a Roaming Not Allowed error code can also be used in response to a LUP message. Although this puts the network as forbidden in the SIM of a handset, it results in a faster network reselection.
  • the anti-TR solution can just drop the LUP ack/error message and immediately issues another LUP message on the same transaction of the first LUP message that got the LUP error of Roaming Not Allowed. In this way, the HPMN TR may deduce that the handset has manually selected the same not allowed network again and could have allowed the registration to be successful.
  • the in-signal-path anti-anti-TR solution will continue to issue RNA to a location update if it comes back within a configurable interval (for example 20 seconds) of the previous location update that got rejected with the RNA error.
  • a VPMN 104 simplistically blocks all the OTA messages from HPMN 102 to its outbound roamers.
  • HPMN 102 would respond by sending RNA error code in the LUP response to a LUP request from an outbound roamer registered/attempting registration with VPMN 104 deploying anti-TR solution to OTA/SIM approach. Once the roamer registers with an alternate network, HPMN 102 can then send OTA messages, steering it to the preferred VPMN 106.
  • a computer usable medium claimed herein includes computer usable program code, which when executed counters the anti-TR solution as deployed by the VPMN.
  • the anti-TR attempt is detected by observing exchange of at least one registration message between the VPMN and the HPMN.
  • the computer usable medium further includes computer usable program code for redirecting the roamer to attempt reconnection with a preferred network.
  • the components of Anti-Traffic Redirection Countering System include any combination of computing components and devices operating together.
  • the components of the ATRCS can also be components or subsystems within a larger computer system or network.
  • the ATRCS components can also be coupled with any number of other components (not shown), for example other buses, controllers, memory devices, and data input/output devices, in any number of combinations.
  • any number or combination of other processor- based components may be carrying out the functions of the ATRCS.
  • 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.
  • the present invention may also be effectively implemented on CDMA, 3G, WCDMA, GPRS, WiFi, WiMAX, VOIP 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.
  • ATCS Anti-Traffic Redirection Countering System
  • Anti-Traffic Redirection Countering System a method for countering anti-TR between VPMN and HPMN of the roaming mobile station in a manner that is agnostic to 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
  • GSM 902 on MAP specification Digital cellular telecommunications system (Phase 2+) Mobile Application Part (MAP) Specification (3GPP TS 09.02 version 7.9.0 Release 1998)
  • GSM 1111 SIM and Mobile Interface
  • GSM 23119 Gateway Location Register
  • GSM 408 Mobile Radio Interface Network Layer

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système permettant de contrecarrer une redirection anti-trafic d'une station mobile d'itinérance. L'observation de messages d'enregistrement échangés entre le réseau en visite et le réseau de rattachement permet de détecter si le réseau en visite a déployé un mécanisme de redirection anti-trafic dont le but est de tromper le réseau de rattachement quant à la permission d'établir une connexion avec un réseau non préféré. L'invention concerne également une manière permettant de diriger l'abonné itinérant dans sa nouvelle tentation de connexion avec un réseau préféré.
PCT/US2006/009064 2005-03-14 2006-03-14 Procede, systeme et produit de programme informatique permettant de contrecarrer une redirection anti-trafic Ceased WO2006099389A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US66203105P 2005-03-14 2005-03-14
US60/662,031 2005-03-14

Publications (2)

Publication Number Publication Date
WO2006099389A2 true WO2006099389A2 (fr) 2006-09-21
WO2006099389A3 WO2006099389A3 (fr) 2007-12-13

Family

ID=36992361

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2006/009064 Ceased WO2006099389A2 (fr) 2005-03-14 2006-03-14 Procede, systeme et produit de programme informatique permettant de contrecarrer une redirection anti-trafic

Country Status (2)

Country Link
CN (1) CN101180897A (fr)
WO (1) WO2006099389A2 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8744436B2 (en) 2006-09-01 2014-06-03 At&T Mobility Ii Llc Roaming selection services

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101808295B (zh) * 2009-02-16 2013-01-02 中国移动通信集团江西有限公司 多vpmn呼叫控制方法、业务控制点及系统
US8364143B2 (en) * 2010-12-21 2013-01-29 Tektronix, Inc. Detection of anti-steering of roaming activity on visited networks

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6058309A (en) * 1996-08-09 2000-05-02 Nortel Networks Corporation Network directed system selection for cellular and PCS enhanced roaming
US7222192B2 (en) * 2002-01-10 2007-05-22 Tekelec Methods and systems for providing mobile location management services in a network routing node

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8744436B2 (en) 2006-09-01 2014-06-03 At&T Mobility Ii Llc Roaming selection services

Also Published As

Publication number Publication date
WO2006099389A3 (fr) 2007-12-13
CN101180897A (zh) 2008-05-14

Similar Documents

Publication Publication Date Title
US7873358B2 (en) Method and system for providing inbound traffic redirection solution
US8121594B2 (en) Method and system for providing roaming services to inbound roamers using visited network Gateway Location Register
US10327137B2 (en) System and method for detecting malicious attacks in a telecommunication network
US7917139B2 (en) Inbound roamer call control system
EP1763963B1 (fr) Passerelle frontière d'itinérance
US7590417B2 (en) Method, system and computer program product for countering anti-traffic redirection
US20100240361A1 (en) Anti-inbound traffic redirection system
EP2730107A1 (fr) Module à valeur ajoutée dans intelligence prédictive
JP2005237008A (ja) Ｓｍｓメッセージのフィルタリングのためのシステム及び方法
US8254916B2 (en) Method for blocking roaming-steering mechanisms
US7684793B2 (en) Anti-traffic redirection system
WO2008057475A1 (fr) Procédé et système de fourniture de services d'itinérance à des abonnés itinérants entrants au moyen d'un enregistreur de localisation passerelle de réseau visité
WO2006099389A2 (fr) Procede, systeme et produit de programme informatique permettant de contrecarrer une redirection anti-trafic
CN101185352B (zh) 阻止通信重定向的系统
EP1938628B1 (fr) Systeme d'opposition au reacheminement du trafic entrant
EP1974555A2 (fr) Systeme permettant de rediriger le trafic entrant
WO2008027106A1 (fr) Procédé et système offrant une solution de réacheminement du trafic entrant
WO2006099476A2 (fr) Methode et appareil au moyen desquels un reseau domestique peut detecter et peut reagir contre un reacheminement de trafic de reseau d'arrivee de reseau visite
CN103716819A (zh) 拜访位置寄存器故障处理方法和移动管理网元
EP2727327A1 (fr) Numéro de téléphone local prépayé sans numéro de téléphone local
HK1179089B (en) Method and apparatuses for receiving a mobility management entity name

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 200680016431.0

Country of ref document: CN

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

WWE Wipo information: entry into national phase

Ref document number: 1689/MUMNP/2007

Country of ref document: IN

122 Ep: pct application non-entry in european phase

Ref document number: 06738154

Country of ref document: EP

Kind code of ref document: A2