WO2012177911A1

WO2012177911A1 - Anti-call forwarding spam control

Info

Publication number: WO2012177911A1
Application number: PCT/US2012/043591
Authority: WO
Inventors: John Yue Jun Jiang
Original assignee: Roamware, Inc.
Priority date: 2011-06-21
Filing date: 2012-06-21
Publication date: 2012-12-27

Abstract

A method and system for managing mobile communication of a subscriber are provided. The method includes establishing observing a data modification request regarding the subscriber. The method further includes matching one or more parameters in the data modification request with data in a database. Thereafter, depending on outcome of the match with the data in the database, either implementing the data modification request or cancelling the data modification request.

Description

ANTI-CALL FORWARDING SPAM CONTROL

Related Applications

This application claims the benefit of U.S. Provisional Patent Application No. 61/499,462, filed on June 21 , 201 1 , titled "Anti-Call Forwarding Spam Control," which is incorporated by reference in its entirety herein.

BACKGROUND OF THE INVENTION

Field of the Invention

The present invention generally relates to mobile communication. More specifically, the invention relates to handling call forwarding service for a subscriber.

Background

Mobile communication during roaming contributes a major percentage of a network operator's revenue and specifically, voice traffic and SMS traffic contributes even better percentage of the network operator's margin. With increasing competition and regulatory control, network operators look for solutions to enhance both local and roaming revenues.

Mobile subscribers generally tend to use call forwarding service so that callers can reach them at an alternate number, in case where subscribers' original number is not reachable. This alternate number, i.e., the call Forward-To- Number (FTN) can also be a number mapped to a different subscriber. For example, a subscriber may set call forwarding to his friend's mobile number. However, this call forwarding does not require consent from the owner of FTN for forwarding. This is due to the fact that the subscriber setting call forwarding pays for the forwarded leg and the FTN owner does not have to pay.

The FTN owner may be a postpaid or prepaid subscriber and may even be roaming when call forwarding is set to his number. In that case, the FTN owner will have to pay the roaming airtime charges for receiving the MT call. In such situation, there may be a possibility that the subscriber may erroneously mis-set the call forwarding to a FTN owner who is outbound roaming. Moreover, there may be

I situation where the subscriber can use this call forwarding to fool the calling party, thereby spamming the FTN subscriber.

In other situation, the subscriber can intentionally set the FTN to another subscriber as a result the FTN subscriber gets annoying calls. The subscriber setting the call forwarding may do so to avoid debt chasing calls, or sales calls, or even play a prank to deliberately spam FTN subscriber. No solution exists to deal with the above mentioned problem. In accordance with the foregoing, there is a need in the art of a system and method for a solution that allows the subscriber to manage call forwarding set to his number.

SUMMARY

The present invention is directed towards a method for managing mobile communication for a subscriber. The method includes establishing observing a data modification request for the subscriber. The method further includes matching one or more parameters in the data modification request with a database. Thereafter, depending on outcome of the match with the database, either implementing the data modification request or cancelling the data modification request.

The present invention also presents a system for managing mobile communication for a subscriber. The system includes a service node that observes a data modification request for the subscriber. The service node further matches one or more parameters in the data modification request with a database. Thereafter, depending on the outcome of the match, the service node either implements the data modification request or cancels the data modification request.

BRIEF DESCRIPTION OF DRAWINGS

In the drawings, the same or similar reference numbers identify similar elements or acts. FIG. 1 illustrates a system for implementing Anti Forwarding Spam Control (AFSC) service for managing call forwarding for a subscriber, in accordance with an aspect of the present invention;

FIG. 2 illustrates a flowchart depicting the AFSC service, in accordance with an aspect of the present invention;

FIG. 3 illustrates a flow diagram for implementing the AFSC service in a monitoring based mode, in accordance with an aspect of the present invention; arid

FIG. 4 illustrates a How diagram for implementing the AFSC service in a trigger based mode, in accordance with an aspect of the present invention.

DETAILED DESCRIPTION

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 aspect" or "an aspect" means that a particular feature, structure or characteristic, described in connection with the aspect, is included in at least one aspect of the present invention. The appearance of the phrase "in an aspect," in various places in the specification, does not necessarily refer to the same aspect.

The present invention provides a system and a method where home network facilities for its outbound roamer, Anti Forwarding Spam Control (AFSC) service that allows the outbound roamer to manage its call forwarding. This AFSC service deals with problem of outbound roamers who do not want any other subscriber to set call forwarding to his number. FIG. 1 illustrates a system 100 for implementing the AFSC service for a subscriber of Home Public Mobile Network (HPMN) 102, in accordance with an aspect of the present invention. HPMN 102 includes a service node 104 that observes facilitates the AFSC service for an outbound roamer 106. The service node 104 facilitates that a subscriber 108 (from HPMN or other operator) is not able to set his call forwarding to HPMN's outbound roamer 106. The HPMN 102 further includes a Gateway Mobile Switching Center (GMSC)/ Service Switching Function (SSF) 1 10 to facilitate call to subscriber 106. HPMN 102 further includes a Home Location Register (HLR) 1 12, and an Unstructured Supplementary Services Data (USSD) gateway 1 14 to send and receive USSD commands from subscriber 106. A prepaid Signaling Control Point (SCP) 1 16 to handling charging of subscriber 106.

In an aspect of the present invention, service node 104 communicates with GMSC/SSF 1 10 over ISUP and MAP protocols. Service node 104 further sends SMS to SMSC 1 12 over a Transmission Control Protocol (TCP) / Internet Protocol (IP). Additionally, service node 104 communicates with USSD gateway 1 14 over an XML and a Short Message Peer-to-Peer (SMPP) protocol. Service node 104 communicates with prepaid SCP 1 16 over CAP and Intelligent Network Application Part (1NAP) protocols.

In an aspect of the present invention, the outbound roaming subscriber 106 of HPMN 102 first needs to register for the AFSC service in order to manage its call forwarding. Subscriber 106 can use SMS or USSD or Web interface to turn on the AFSC service. Further, subscriber 106 can set following conditions while using the AFSC service:

• Default setting- disallow everyone to set FTN to subscriber 106's number

• Request permission to set subscriber 106's number as call FTN

• White-list subscribers can also set subscriber 106's number as call FTN

• Turn on AFSC only when subscriber 106 is outbound roaming

The service node 104 notifies subscriber 106 in case request permission or a non-whitelist^' caller sets call forwarding to subscriber 106. The service node 104 also allows subscriber 106 to opt-in or opt-out from AFSC service. In case of opt-in, unless subscriber 106 has explicitly approved the call forwarding, the call forwarding will be cancelled. In case of opt-out, unless the subscriber explicitly disapproves within a certain interval, the call forwarding even is not selected. In one aspect of the present invention, the AFSC is offered as a free service to all outbound roamers of HPMN 102, due to regulations. In another aspect of the present invention, the subscriber does not register for the AFSC service but avails the AFSC service on need basis. In yet another aspect of the present invention, the AFSC service can be deployed at operator level or at a national level for a group of operators. In case, it is deployed at national level, the HPMN 102 maintains a national subscription database 1 18, which an individual operator can subscribe to for using the AFSC service. Individual operator can create a local database that synchronizes with the national subscription database 1 18 to improve efficiency and reduce cost. This deployment is like national Do Not Disturb (DND) service.

FIG. 2 illustrates a flowchart depicting the AFSC service, in accordance with an aspect of the present invention. At step 202, service node 104 observes a data modification request for the subscriber. The data modification request may be any request like, but not limited to, call forwarding, call baring etc. In accordance with various aspects of the present invention, service node 104 may observe the data modification request either as an active node (trigger based mode) or as a passive node (monitoring based mode). As an active node, the service node 104 has its own point codes and Global Titles (GTs). At a passive node, service node 104 tracks the MAP messages exchanged between HLR 1 12 and subscriber 106. The monitoring can be Sigtran, HSL or LSL.

At step 204, the service node 104 matches one or ^"more parameters in the data modification request with the database 1 18. In one aspect of the present invention, the one or more parameters is the call forward-to-number (FTN) in the data modification request, i.e., call forwarding request. In order to match the parameters, service node 104 checks in the database 1 18 whether the FTN allows call forwarding by a calling party (say subscriber 108).

Thereafter, at step 206, depending on the outcome of match, i.e., whether the FTN allows call forwarding, either of following two actions is performed.

• Implement the data modification request. In other words, allow the call forwarding message to be implemented. • Cancel the call forwarding in the data modification request. In other words, cancel the calling forwarding message if the FT does not allow call forwarding in the database 1 18. In an aspect of the present invention, database 1 18 also stores a list of valid subscribers (e.g., subscriber 106) that have registered for the AFSC service. In an aspect of the present invention, database 1 18 maintains a blacklist of VPMNs whose subscribers are not able to set ΡΓΝ as subscriber 106's number.

FIG. 3 illustrates a flow diagram for implementing the AFSC service in a monitoring based mode, in accordance with an aspect of the present invention. As service node 104 is in monitoring mode, then it observes a call forwarding request from subscriber 106 to its HLR 1 12. This call forwarding request is one type of the data modification message. Thereafter, HLR 1 12 sends an Inform (IMSI-A, A, B) to service node 1 14. The service node 104 then checks within the database 1 18, whether party B has allowed call forwarding in the database 1 18. If call forwarding is not allowed, then service node cancels the call forwarding request and informs the calling party.

FIG. 4 illustrates a flow diagram for implementing the AFSC service in a trigger based mode, in accordance with an aspect of the present invention. In this case, service node 104 is in trigger based mode. The call forwarding request reaches HLR 1 12, which then forwards it to service node 104 as NotifySubscriber Data Change message (IMSI-A, A, B). If FTN is allowed (Allow (A,B)) in database 1 18, then service node 104 does not need to do anything else but reporting it to HLR 1 12. In case the FTN is not allowing call forwarding in database 1 18, then service node 104 cancels the call forwarding request and informs the calling party, i.e., subscriber 108. 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 # 4 I D (ANSI-41D), and various other technologies such as, but not limited to, VoIP, WiFi, 3GSM and inter-standard roaming. In one exemplaiy case, a CDMA outbound roamer travels with an ITPMN 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, gateway 104 and client 106 will have a separate SS7 and network interfaces, corresponding to both the HPMN and FPMN 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 ANS1-41 D is described in Table 1 below as a reference.

TABLE 1

The present invention provides a Anti Forwarding Spam Control (AFSC) is helpful for outbound roaming subscribers of an operator who want to keep a control on call forwarding done on their numbers. With the help of AFSC service, the outbound roaming can control who can use his number as a forward-to-number.

The present invention can take the form of an entirely hardware variation, an entirely software variation, or a variation containing both hardware and software elements. In accordance with an aspect 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).

A computer usable medium provided herein includes a computer usable program code, which when executed, facilitates mobile communication between a calling party and a called party, by establishing the mobile communication, by a service node, upon receiving a response from the called party for a mobile communication request made by the calling party to the service node. Further, the computer program product facilitates by the service node, charging of the called party for the established mobile communication. 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 aspects of the present system is not intended to be exhaustive or to limit the present system to the precise form disclosed. While specific aspects 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 aspects described above can be combined to provide further variations. These and other changes can be made in light of the above detailed description. 1

Other Variations

Provided above for the edification of those of ordinary skill in the art, and not as a limitation on the scope of the invention, are detailed illustrations of a scheme for charging a called party for the mobile communication initiated by a calling party. . 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 variations 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 aspects. 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 Wi Fi 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 aspects 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 aspects 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 elemenl(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.

APPENDIX

I I HTTP Hypertext Transfer Protocol

1AM Initial Address Message

IDP Initial Destination Point

IN Intelligent Network

1NAP Intelligent Network Application Part

IP Internet Protocol

ISD MAP Insert Subscriber Data

ISUP ISDN User Part

IVR Interactive Voice Response

LCF Late Call Forwarding

LUP Location Update

MAP Mobile Application Part

MO Mobile Originated

MSC Mobile Switching Center

MSISDN Mobile Station International Subscriber Directory

Number

MSRN Mobile Station Roaming Number

MT Mobile Terminated

O&M Operation and Maintenance

PC Point Code

RRB Request Report Basic call state model event

SC Short Code

SCP Signaling Control Point

SCCP Signal Connection Control part

SME Short Message Entity

SMPP Short Message Peer-to-Peer

SMS Short Message Service

SMSC Short Message Service Center

SNMP Simple Network Management Protocol

SRI MAP Send Routing Information

SRI-SM MAP Send Routing Information For Short Message

SS7 Signaling System #7

SSF Service Switching Function

STP Signal Transfer Point

TAP Transfer Account Procedure

T-CSI Terminating CAMEL Subscription Information

TCAP Transaction Capabilities Application Part

TCP Transmission Control Protocol

USSD Unstructured Supplementary Services Data

VLR Visitor Location Register

VPMN Visited Public Mobile Network

VT-CSI Visited Terminated CAMEL Service Information

XML extensible Markup Language

Technical References, the entirety of each of which is incorporated by reference herein:

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 378 CAMEL Architecture, Release 1998

GSM 978 CAMEL Application Protocol, Release 1 98

GSM 340 on SMS

Digital cellular telecommunications system (Phase 2+);

Technical realization of the Short Message Service (SMS);

(GSM 03.40 version 7.4.0 Release 1998)

Q 1 214-Q 121 8 on Intelligent Networks

Q701 -704 on SS7 MTP

Q71 1 -Q714 on SS7 SCCP TD.35 NRTRDE Format for Fraud information

FF. 18 NRTRDE Business Requirements

ETS I CS domain charging documents: TS 12.05, TS 32.005, TS 32.205, TS 32.298 ETSI PS domain charging documents: TS 12.15, TS 32.015, TS 32.215, TS 32.298

ETS 300 374-1 Intelligent Network (IN); Intelligent Network Capability Set 1 (CS l ); Core Intelligent Network Application Protocol (INAP); Part 1 : Protocol specification

EN 301 140- 1 Intelligent Network (IN); Intelligent Network Application Protocol (INAP); Capability Set 2 (CS2); Pail 1 : Protocol specification Jiang DCG 2005 Dynamic originating CAMEL approach for Implementing Call Control Services for Inbound Roamers, United States Provisional Patent Application Serial No. 60/679,444; Jiang et al 2003 Traffic Redirection

GSM 379 on CAMEL Support of Optimal Routing (SOR)

GSM 318 on CAMEL Basic Call Handling

ITU-T Recommendation Q.1214 (1995), Distributed functional plane for intelligent network CS- 1 ;

ITU-T Recommendation Q.1218 ( 1995), Interface Recommendation for intelligent network CS- 1 ;

ITU-T Recommendation Q.762 ( 1999), Signaling system No. 7 - ISDN user part general functions of messages and signals; ITU-T Recommendation Q.763 (1999), Signaling system No. 7 - ISDN user part formats and codes;

ITU-T Recommendation Q.764 (1999), Signaling system No. 7 - ISDN user part signaling procedures;

ITU-T Recommendation Q.766 (1993), Performance objectives in the integrated services digital network application;

ITU-T Recommendation Q.765 ( 1998), Signaling system No. 7 - Application transport mechanism;

ITU-T Recommendation Q.769.1 (1999), Signaling system No. 7 - ISDN user part enhancements for the support of Number Portability

Claims

1. A method of managing mobile communications of a subscriber, the method comprising: observing a data modification request regarding the subscriber; .

matching one or more parameters in the data modification request with data in a database;

depending on an outcome of the match with the data in the database, performing one of:

implementing the data modification request; and cancelling the data modification request.

2. The method of claim 1 , wherein the data modification request is observed by one selected from a group consisting of active monitoring, passive monitoring and an event trigger.

3. The method of claim 1 , wherein the data modification request is one selected from a group consisting of a call forwarding request and a call barring request.

4. The method of claim 1 , wherein the one or more parameters is a call forward-to-number.

5. The method of claim 1. wherein matching comprises checking the data in the database to determine whether a call forward-to-number allows call forwarding by a calling party.

6. The method of claim 5, wherein implementing the data modification request comprises allowing call forwarding if the call forward-to- number allows call forwarding by the calling party in the database.

7. The method of claim 5, wherein cancelling the data modification request comprises cancelling call forwarding if the call forward- to-number does not allow call forwarding by the calling party.

8. The method of claim 1 , wherein the subscriber controls call forwarding to a number of the subscriber by initiating Anti-Call Forwarding Spam Control (AFSC).

9. The method of claim 8, wherein the subscriber initiates AFSC by one or more of a Short Message Service (SMS), Unstructured

Supplementary Services Data (USSD) or a web-interface.

10. The method of claim 8, wherein the subscriber sets one or more of the following options while initiating AFSC:

a default setting option that disallows anyone to set the number of the subscriber as the call forward-to-number; and

a request permission option that requests permission to set the number of the subscriber as the call forward-to-number.

1 1. A system for managing mobile communications of a subscriber, the system comprising:

a service node that observes a data modification request regarding the subscriber,

the service node further matches one or more parameters in the data modification request with data in a database, the service node further, depending on the outcome of the match, performs one of the following:

implements the data modification request; and cancels the data modification request.

12. The system of claim 12, wherein the service node observes the data modification request by one selected from a group consisting of a probe and a trigger.

13. The system of claim 12, wherein the data modification request is one selected from a group consisting of a call forwarding request and a call barring request.

14. The system of claim 12, wherein the service node checks the data in the database to determine whether a call forward-to-number allows call forwarding by a calling party.

15. The system of claim 12, wherein the one or more parameters is a call forward-to-number.

16. The system of claim 12, wherein the service node allows call forwarding if the call forward-to-number allows call forwarding by the calling party in the database.

17. The system of claim 12, wherein the service node cancels call forwarding if the call forward-to-number does not allow call forwarding by the calling party.

18. The system of claim 1 , wherein the subscriber controls call forwarding to its number by initiating Anti-Call Forwarding Spam Control (AFSC).

19. The system of claim 19, wherein the subscriber initiates AFSC by one or more of a Short Message Service (SMS), Unstructured

Supplementary Services Data (USSD) or a web-interface.

20. The system of claim 19, wherein the subscriber sets one or more of the following options while initiating AFSC:

21 . A computer program product comprising a computer usable medium having control logic stored thereon for causing a computer to manage mobile communications of a subscriber, the control logic comprising:

computer readable program code means for observing a data modification request regarding the subscriber;

computer readable program code means for matching one or more parameters in the data modification request with data in a database;

depending on an outcome of the match with the data in the database, computer readable program code means for performing one of: