Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04W—WIRELESS COMMUNICATION NETWORKS
  • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
  • H04W12/12—Detection or prevention of fraud
  • H04W12/126—Anti-theft arrangements, e.g. protection against subscriber identity module [SIM] cloning

Definitions

• This invention relates to radio telecommunications networks in general and, more particularly, to a method and apparatus for detecting fraudulent telephone usage within such a system.
• Fraud has been identified as one of the cellular telephone industry's biggest problems. Because of fraud, the annual global loss in revenue now exceeds $1 billion. This amount does not account for indirect fraud costs, which include anti-fraud in-house personnel teams, the cost of anti-fraud equipment, and the negative impact such fraud has on wary potential subscribers.
• Fraud appears in many forms, and new methods of committing fraud are conceived on almost a daily basis.
• criminals who steal cellular phone services enjoy anonymity and other benefits, such as the ability to make an unlimited number of free calls, income from selling long-distance services at reduced rates, and the ability to bypass regulations that prohibit communications between certain countries.
• cloning One of the most popular, and difficult to detect, methods of fraud is cloning, which can be described as the complete duplication of a legitimate mobile terminal, including the mobile identification number (MUST), the electronic serial number (ESN) and, in some cases, the subscriber's personal identification number (PLN).
• MUST mobile identification number
• ESN electronic serial number
• PPN subscriber's personal identification number
• cloned telephones successfully pass pre-call validation checks, allowing fraudulent use that is billed to legitimate subscribers. In many cases, fraudulent calling activity is not detected until after thousands of dollars of non-recoverable calling charges have accrued.
• the MLN-ESN represents a unique combination that may be used to validate a legitimate subscription.
• the MLN-ESN are stored in the operator's database, or home location register (HLR).
• HLR home location register
• each access request to the MSC by the mobile terminal triggers a matching check by the MSC with the numbers received from the HLR. If the MLN-ESN transmitted by the phone matches the HLR data, then the MSC processes the access request.
• the most common way of obtaining MLN-ESN combinations for use in cloning cellular phones is the theft of subscriber data from the operator, via interception, using a frequency scanner over the air interface. Since the MLN-ESN combination is transmitted on the air interface control channel whenever a mobile terminal registers with a Mobile Switching Center (MSC) or initiates/receives a call, the MLN-ESN combination is fairly easy to retrieve. One, if not many, cellular phones can easily be reprogrammed to use new MLN-ESN combinations.
• MSC Mobile Switching Center
• a method and apparatus capable of defeating cloned cellular telephone operations which make use of stolen MLN-ESN combinations is desirable. Further, it is also desirable to have a method and apparatus of defeating fraudulent cellular telephone operations which make use of stolen PINs.
• an apparatus for detecting fraud in a radio network includes a Mobile Station (MS) having a nonvolatile memory to store an electronic identification number and a first calling event table.
• the nonvolatile memory may be battery-backed random access memory, electrically-erasable programmable read-only memory, or other types well known in the art.
• the apparatus also includes a MSC or HLR having a second calling event table that contains a mirror image of the first calling event table, as long as no fraud has occurred.
• the first and second calling event tables contain identifying information for MS calling activity, such as outgoing call information, which may comprise a called number, a call time, a call duration, and/or a call date.
• the first and second calling event tables are updated with each outgoing call, and authorization to make future calls is based on conditioned correspondence between the information contained in each calling event table.
• a mismatch in table information (between the first and second calling event tables) is determined during an interrogation process that begins when the clone attempts to initiate a call, and, upon detection of the mismatch by the MSC or HLR, the fraudulent call connection is prevented.
• the method for detecting fraud within a radio network begins when the MS initiates a call through the MSC.
• calling event data within the MSC or HLR is retrieved for the calling MS (from the second calling event table).
• one or more queries based on the retrieved calling event data are sent to the MS to determine whether the first calling event table in the MS contains data that matches the contents of the second calling event table.
• a response message containing the MS calling event data is sent from the MS to the MSC/HLR, and compared with the MSC HLR query calling event data. If the data are equal, then the call can be completed.
• Call data, queries, and comparisons can be maintained and conducted within a MSC, a HLR, or by using some combination of a MSC and a HLR.
• any mismatch between data in the first and second calling event tables results in preventing the MS from being used to make calls in conjunction with the MSC.
• Such a mismatch indicates fraudulent cloning of a MS with a stolen MLN-ESN combination.
• the MSC or HLR query may include data for several events within the tables, selected in sequence, or randomly, such that only a complete copy of the table contents will enable a successful cloning operation.
• FIG. 1 is a schematic block diagram of the apparatus of the present invention
• FIGS. 2A and 2B are tables which illustrate exemplary contents of the first and second calling event tables, respectively, when no fraud has occurred;
• FIG. 3 is a flow chart illustrating the steps of subscriber fraud detection embodied in the present invention.
• FIG. 4 is a flow chart illustrating the steps of subscriber fraud detection and data updating embodied in the present invention.
• FIGS. 5 A and 5B are tables which illustrate exemplary contents of the first and second calling event tables, respectively, when fraud has occurred.
• the present invention includes an apparatus and method for limiting fraudulent telephone calls in a radio network which involves collection of historical data by the network and by individual cellular telephones operating within the network.
• the data collected by the apparatus illustrated in the schematic block diagram of Fig. 1 may be similar to, or identical to, that shown in Figs. 2A and 2B, which depict a series of events directly related to outgoing calls made by an individual cellular phone, or MS operator.
• the apparatus of the present invention comprises a radio network 8, including a MS 20 having a nonvolatile memory 25.
• the first calling event table which may be identical to, or similar to, the table of Fig. 2A, is stored in the memory 25.
• the MS 20 is in electronic communication with the MSC 30, via radio waves 26 and the base station 27, as part of the radio network 8.
• the MSC 30 has a non-volatile memory 35, containing a second calling event table for the MS 20, which in turn contains a mirror image (normally) of the first calling event table.
• the contents of the second calling event table may be identical to, or similar to, the table shown in Fig. 2B.
• a HLR 180, linked to the MSC 30, may alternatively have a non-volatile memory 185 that is used to contain the second calling event table.
• the second calling event table may be resident in either the MSC 30 or the HLR 180, or both.
• an index number 31 is assigned to each outgoing call made by the cellular phone, up to some maximum number of calling events (e.g. fifty) 32.
• Each outgoing call, or event is characterized by the number dialed 33, the date on which the call was made 34, the time of the call 36, the duration of the call 37, and/or other identifying information 38, such as the user PLN, and the like.
• Fig. 2B depicts the information collected by the memory 35 in the network MSC 30 (or the memory 185 in the HLR 180, or both) which corresponds to the MS 20 memory 25 data shown in Fig.2A. As illustrated, all of the data shown in Fig.
• Non-volatile memories 25, 35, and 185 may exist in the form of battery-backed random access memory, electrically-erasable programmable read-only memory, subscriber identification module cards, disk or tape drives, or similar devices.
• Fig. 3 depicts an operational flow chart illustrating the method of the present invention.
• a mobile station (MS) 20 originates a call by sending a call set-up request 40, which includes the ESN of the MS 20, to the MSC 30.
• the MSC 30 may access one or more events, in sequence or at random, from the historical data stored in the second calling event table (illustrated in Fig. 2B) corresponding to the ESN 42 that matches the ESN sent by the MS 20.
• the accessed event data is fetched and formatted into a query 50
• a formatted calling event query 60 is sent to the MS 20.
• the MS 20 fetches data which corresponds to the calling event query 60, formats it at step 70, and a calling event response message 80 is sent to the MSC 30.
• the MSC 30 compares at step 90 the calling event query 60 and the calling event response message 80. If the query 60 and response message 80 do not match, then the call is rejected 100 and the signaling channel is reallocated. If the query 60 matches the response message 80, then the call is allowed to complete.
• the calling event query 60 may consist of asking the MS 20 "What was the number that you dialed on December 13, 1997 at 11 : 17?" (refer to Fig. 2B, event 43).
• the MS 20 must respond to the MSC 30 by way of the calling event response message 80 that the number was "2340999," (refer to Fig. 2A, event 44) or the call is rejected. Otherwise, if the calling event data from the first calling event table (tabular data in Fig. 2A) and the second calling event table (tabular data in Fig. 2B) match, call setup, including any other authentication procedures and equipment identification, is completed in step 110.
• a second example may be that the MSC 30 interrogates the MS 20 by way of the calling event query 60 as to "What was the number dialed at your recorded index number position of fifty?" (refer to Fig. 2B, event 46)
• the MS 20 must answer to the MSC 30 by way of the calling event response message 80 that the number was "2345234" (refer to Fig. 2A, event 47). Again, if the proper answer is not elicited (i.e., no match), the call is rejected 100.
• Fig. 4 a flow chart of the call completion sequence, along with database or memory updating, is shown.
• the call setup is completed 110, then the complete connection is established after the traffic channel is allocated. At this time the actual call 120 occurs.
• the call is terminated and the MSC 30 acts to send updated historical calling event data 130 to the MS 20.
• the MS 20 acknowledges data receipt 140 from the MSC 30, and the MS 20 updates the MS 20 calling event table 150 (i.e. the first calling event table). The receipt of the acknowledge data message
• the MSC 30 causes the MSC 30 to update the MSC calling event table 160 (i.e. the second calling event table).
• the calling event query 60 and calling event response message 80 may be repeated for several events, as in a query and response loop 170, so that the probability of legitimate subscriber use is greatly increased. That is, a cloned phone which possesses the MLN-ESN number, and even the PIN of a particular subscriber will, most likely, not have a record of any more than the most recent calling event/outgoing call made by the cloned phone.
• FIGs. 5 A and 5B An idea of the problems a fraudster faces when attempting to defeat the protection provided by the present invention can be seen by referring to Figs. 5 A and 5B, wherein the first and second calling event tables are shown after the MS 20 has been cloned by cloned MS 61 (see Fig. 1).
• Fig. 5 A details the cloned MS 61 memory
• Fig. 5B details the MSC 30 memory 35 content.
• the fraudster has successfully captured the last two calling event transactions for the cloned MS 61 (see events 48 and 49 in Fig. 5B), and coded them into the nonvolatile memory 62 of the cloned MS 61 (see events 48 and 49 in Fig. 5A).
• the fraudster since the information was not sent out over the air until several hours (or days) earlier, the fraudster was not able to recover the calling event information for transaction events three through fifty (see events 51 in Figs. 5A and 5B).
• the table shown in Fig. 5A clearly indicates that the MS used to clone the MS 20 is a different phone. That is, even though the MS clone makes use of the present invention, it can not be operated by a fraudulent subscriber.
• a corresponding calling event table contained in the memory 185 within the HLR 180 is updated 190 after the acknowledge data message 140 is received by the MSC 30.
• Information from the second calling event table may also be downloaded, upon request, from the HLR 180 memory 185 to the MSC 30 memory 35 as required. For example, single events, multiple events, or even an entire calling event table may be sent by the HLR 180 to the MSC 30 to support various calling event queries 60 posed by the MSC 30 to the MS 20.
• the MSC 30 In the case of a remotely located HLR 180, several aspects in the implementation of the method of the invention are changed. First, the MSC 30 must request data from the calling event table maintained in the HLR 180 for use in formulating a calling event query 60 to the MS 20. One or more events, chosen in sequence or at random, are requested from the HLR 180 by the MSC 30 for use in formulating one or more calling event queries 60. Once the event data has been retrieved from the HLR 180, the method proceeds as described above until the call termination is acknowledged 140 by the MS 20. At that time, the MS 20 updates the
• MS calling event table 150 in the normal fashion, but the MSC 30 sends a message and current calling event data to the HLR 180 for updating 190 the HLR outgoing calling event table for the MS 20 (instead of updating the memory 35 content within the MSC 30).
• a default calling event table may be predetermined by the service provider and downloaded to the phone, or the first call from an inactive phone may be placed with a service provider for verification of basic phone operation and uploading of the calling event table maintained within the telephone. Roaming telephone users can always be verified against the calling event data held by the HLR 180. However, roamers operating out of the country may not have HLR data available for verification.

Landscapes

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

Priority Applications (4)

Applications Claiming Priority (2)

Publications (1)

Family

ID=22637164

Family Applications (1)

Country Status (7)

Cited By (3)

Families Citing this family (15)

Citations (4)

Family Cites Families (6)

• 1998
  • 1998-10-19 US US09/174,701 patent/US6295446B1/en not_active Expired - Fee Related
• 1999
  • 1999-10-08 CN CN99812178A patent/CN1323501A/zh active Pending
  • 1999-10-08 CA CA002344596A patent/CA2344596A1/en not_active Abandoned
  • 1999-10-08 BR BR9914630-4A patent/BR9914630A/pt not_active IP Right Cessation
  • 1999-10-08 AU AU14237/00A patent/AU1423700A/en not_active Abandoned
  • 1999-10-08 WO PCT/SE1999/001824 patent/WO2000024219A1/en active Application Filing
  • 1999-10-08 GB GB0107241A patent/GB2358113A/en not_active Withdrawn

Patent Citations (4)

Also Published As

Similar Documents

Legal Events