FORM 2
The Patent Act 1970
(39 of 1970)
&
The Patent Rules, 2005

COMPLETE SPECIFICATION
(SEE SECTION 10 AND RULE 13)

TITLE OF THE INVENTION

“MO-SMS Spam Controller”

APPLICANTS:
Name : TeleDNA Communications Pvt. Ltd.
Address : No 23 & 24, 2nd Floor, AMR Tech Park, Hosur Road
Bangalore. PIN 560068

The following specification particularly describes and ascertains the nature of this invention and the manner in which it is to be performed:-

FIELD OF INVENTION
[001]This invention relates to mobile communications, and more particularly to short message service in mobile communications.

BACKGROUND OF INVENTION
[002]Short Message Service (SMS) is a popular way of communicating with network users. A virus affected Mobile handset generates huge amount of spam SMS messages without the intervention of the Mobile User. The Mobile user is unaware of these spam SMS message being submitted to the network. As the volume of spam messages is very large, these unsolicited SMS messages can congest the network resource (Access, Core, VAS infrastructure). This results in poor efficiency of mobile network in delivering SMS messages. The regular SMS traffic is also affected leading to delayed SMS message delivery and dissatisfied subscribers.
[003]MT text messaging spam controllers are available which detects spam based on number of messages received within specified time to a fixed mobile number. However such controllers only detect the spam based on destination mobile number.

OBJECT OF INVENTION
[004]The principal object of this invention is to detect spam messages generated from mobile user and controlling the spam messages from mobile user.
[005]Another object of the invention is to control the spam message in mobile network and SMSC. By controlling spam messages, mobile network resources and SMSC can be utilized for handling high volume of regular SMS message traffic.
[006]The objective of this invention is also for allowing a mobile network operator / service provider to identify if there is any MO-SMS based Spam hampering their network resources at any given point of time and identify all the mobile numbers from which these Spam SMS messages are generated.
[007]A further object of the invention is to notify the mobile users about the spam messages generated from the mobile user.
[008]A further object of the invention is to block the SMS service for a particular mobile user on SMSC.
[009]A further object of the invention is to block the spam message not to reach the SMSC. The OTA Setting is sent to mobile user having an updated service center address.
[0010]A further object of the invention is to block the SMS Service on HLR for a particular mobile user.
STATEMENT OF INVENTION
[0011]Accordingly the invention provides a system comprising of a MO-SMS Spam Controller module which is notified of MO-SMS messages by the SMSC (Short Message Service Center), characterized of detecting the spam messages generated from particular mobile user, notifying the mobile user about the spam messages generated. The mobile users who is generating the spam messages, the SMS Service is controlled by blocking the mobile user’s SMS service on HLR or on SMSC or by updating the service center address through an OTA setting.
[0012] The spam detection module detects the spam messages based on the filters (From Address, To Address, MSC Address, Submission Time, Duration between subsequent MO-SMS short message). The spam detection module will apply the filters to detect if the mobile user is generating the spam short messages. This module will notify configured notification message to mobile user about the spam messages generated from mobile device.
[0013]The Spam Controller module controls the SMS service of spam originated mobile user. Based on the configuration the Spam Controller module will block the SMS Service on HLR or SMS Service block message is sent to SMSC (Short Message Service Center) or mobile users SMS Service Center Address is modified using OTA Setting. The spam mobile user details are pushed to operator’s CRM / Provisioning System.
[0014]These and other aspects of the embodiments herein will be better appreciated and understood when considered in conjunction with the following description and the accompanying drawings. It should be understood, however, that the following descriptions, while indicating preferred embodiments and numerous specific details thereof, are given by way of illustration and not of limitation. Many changes and modifications may be made within the scope of the embodiments herein without departing from the spirit thereof, and the embodiments herein include all such modifications.

BRIEF DESCRIPTION OF FIGURES
[0015]This invention is illustrated in the accompanying drawings, through out which like reference letters indicate corresponding parts in the various figures. The embodiments herein will be better understood from the following description with reference to the drawings, in which:
[0016]FIG. 1 illustrates network integration of MO-SMS Spam Controller system, according to embodiments as disclosed herein;
[0017]FIG. 2 illustrates a MO-SMS Spam Controller module, integration of the modules with operator’s SMSC and CRM / Provisioning System, according to embodiments as disclosed herein;
[0018]FIG. 3 illustrates a MO-SMS Spam Controller module provided with SMSC and communication network components, according to embodiments as disclosed herein; and
[0019]FIG. 5 and 6 are flow charts depicting sequence of steps in detecting and controlling the spam messages, according to embodiments as disclosed herein;

DETAILED DESCRIPTION OF INVENTION
[0020]The embodiments herein and the various features and advantageous details thereof are explained more fully with reference to the non-limiting embodiments that are illustrated in the accompanying drawings and detailed in the following description. Descriptions of well-known components and processing techniques are omitted so as to not unnecessarily obscure the embodiments herein. The examples used herein are intended merely to facilitate an understanding of ways in which the embodiments herein may be practiced and to further enable those of skill in the art to practice the embodiments herein. Accordingly, the examples should not be construed as limiting the scope of the embodiments herein.
[0021]The embodiments herein achieve detecting and controlling spam messages for mobile user by incorporating systems and methods thereof. Referring now to the drawings, and more particularly to FIGS. 1 through 5, where similar reference characters denote corresponding features consistently throughout the figures, there are shown preferred embodiments.
[0022]The embodiments herein disclose a method for detecting and controlling the spam messages from a mobile user.
[0023]FIG. 1 illustrates system components of Mobile Originated SMS (MO-SMS) Spam Controller, according to embodiments as disclosed herein. The system comprises of a MO-SMS Spam Controller module 101, HLR (Home Location Register) 102, mobile operator’s Short Message Service Center (SMSC) 103, mobile operator’s CRM/Provisioning System 104, mobile network 105 and a plurality of mobile users i.e., user 106 and user 107.
[0024]The MO-SMS Spam Controller module 101 is responsible for detecting and controlling the spam messages from mobile user 106, 107. The MO-SMS Spam Controller module 101 detects the spam messages based on configured filters. The configuration of filters in the MO-SMS Spam Controller module 101 may be modified by the network operator. The MO-SMS Spam Controller module 101 notifies spam mobile users about the spam messages generated from the mobile devices. The notification message for alerting mobile users about spam messages may be modified by the network operator. The SMS service control interface is a configuration, which can be modified by the network operator.
[0025]On detecting a spam message from a mobile user, the MO-SMS Spam Controller module 101 blocks access to the SMS service for the mobile user.
[0026]The HLR (Home Location Register) 102 is a network server that is responsible for maintaining the mobile user services user 106, 107. On receiving the request to block the SMS Service for a particular mobile user, the HLR 102 checks the account details of the user 106, updates the relevant information for the mobile user 106.
[0027]The SMSC 103 interfaces with sub modules of MO-SMS Spam Controller module 101 (i.e., Spam detection module and Spam Controller module). SMSC 103 works on the principle of store and forward mechanism i.e., SMSC 103 stores the SMS message received from the user 107 of mobile device sent through the network 105 and notifies processed MO-SMS message, to MO-SMS Spam Controller module 101 in the present case. In an embodiment, the SMSC 103 may employ Short Message Peer-to-Peer (SMPP) V3.4 protocol and XML to interface the SMSC 103 to the MO-SMS Spam Controller module 101. In an embodiment, SMSC 103 receives spam message notification message for a particular mobile user 106 from MO-SMS Spam Controller module 101.
[0028]The operator’s CRM / Provisioning System 104 interfaces with the MO-SMS spam controller module 101. In an embodiment, the MO-SMS spam controller module 101 pushes the spam message mobile user 106 details to CRM / Provisioning System 104. The MO-SMS spam controller module 101 interfaces with operator’s CRM / Provisioning System 104 on FTP interface / FormlessHTTP interface.
[0029]The network 105 acts as a medium for the transmission of the SMS messages to the MO-SMS Spam Controller module 101 and receiving the spam message notification messages and further sending the spam notification messages to mobile users.
[0030]FIG. 2 illustrates a MO-SMS Spam Controller module, network operator SMSC, CRM / Provisioning system and communication network components, according to embodiments as disclosed herein. The MO-SMS Spam Controller module 101 comprises of two sub modules: a Spam Detection module 301 and a Spam Controller module 302. The Spam Detection module 301 integrates with the operators SMSC for getting MO-SMS messages from mobile user 105. Spam Detection module 301 detects that a MO-SMS generated from a particular mobile user is spam, based on the filters.
[0031]The spam controller module 302 integrates with the operator’s SMSC 103, HLR 102 and CRM / Provisioning System 104. The spam controller module gets the trigger from spam detection module 101 about the spam message generated from mobile user 106. Furthermore, spam controller module 302 is responsible for blocking the mobile user who is generating the spam message from the SMS services.
[0032]The HLR (Home Location Register) 102 is a network server that is responsible for maintaining the mobile user services user 106, 107. On receiving the request to block the SMS Service for a particular mobile user, the HLR 102 checks the account details of the user 106, updates the relevant information for the mobile user 106.
[0033]The SMSC 103 works on the principle of store and forward mechanism i.e., SMSC 103 stores the SMS message received from the user 106 of mobile device sent through the network 105 and notifies the processed MO-SMS, to MO-SMS spam controller module 101.
[0034]FIG. 3 illustrates a MO-SMS spam controller module provided with SMSC module and communication network components, according to embodiments as disclosed herein. The MO-SMS spam controller module 101 may employ a SMSC 103 of its own as shown in FIG. 3. The MO-SMS spam controller 101 comprises of sub modules: spam detection module 301, spam controller module 302 and SMSC 401. The spam detection module 301 integrates with the SMSC 401. The spam detection module 301 detects spam messages generated from mobile user 106 based on the filters. The spam detection module 301 sends spam message notification trigger to spam controller module 302.
[0035]Spam controller module 302 sits in the MO-SMS spam controller module 101. The spam controller module 302 integrates with the SMSC 401. The spam controller module 302 gets the spam message notification trigger from spam detection module 301. Spam controller module 302 integrates with HLR 102 to block the SMS Service for the mobile user who is generating the spam. The spam controller module 302 integrates with SMSC 401 to block the SMS service. The spam controller module 302 integrates with operator’s CRM / Provisioning system 104 for notifying mobile user details that is generating spam messages. Furthermore, the mobile user is notified about the spam message generated from mobile user.
[0036]The HLR (Home Location Register) 102 is a network server that is responsible for maintaining the mobile user services user 106, 107. On receiving the request to block the SMS Service for a particular mobile user, the HLR 102 checks the account details of the user 106, updates the relevant information for the mobile user 106.
[0037]The SMSC 401 works on the principle of store and forward mechanism i.e., SMSC 401 processes the MO-SMS message notifies the MO-SMS originated from user 106 of mobile device sent through the mobile network 105 to MO-SMS spam controller module 101.
[0038]FIG. 4 is a flowchart depicting sequence of detecting and controlling spam messages, according to embodiments as disclosed herein. The mobile user submits (501) the MO-SMS message to SMSC. The MO-SMS message is sent via the mobile network. SMSC processes the message and notifies (502) the MO-SMS message to MO-SMS spam controller module. Spam Detection module checks (503) if the MO-SMS generated from mobile user is spam based on the filters. If the MO-SMS is a spam, the spam detection module sends (504) trigger to spam controller module, logs are generated and the mobile user is notified (505) about the spam message.
[0039]FIG. 5 is a flowchart depicting sequence of controlling the SMS service for mobile user who is generating the spam messages, according to embodiments as disclosed herein. Spam detection module 301 notifies the spam controller module about the spam message generated from mobile user 106. If the SMS service block is to be configured (601) on SMSC then the SMS service block is sent (602) to SMSC. If the SMS service block is to be configured (603) using OTA Setting via on SMSC, then SMS service is blocked by sending (604) OTA Setting to mobile user 106 having modified service center address. If the SMS service block is to be configured (605) on HLR, then the SMS service is blocked by sending (606) SMS service block message to HLR. The spam mobile user detail is pushed (607) to operator’s CRM / Provisioning System.
[0040]In an embodiment, the MO-SMS spam controller module may be implemented to enhance the utilization of mobile network resource and SMSC for handling regular SMS service. In an example, network operators providing Global System for Mobile communication (GSM), Code Division Multiple Access (CDMA) services can detect and control the spam messages
[0041]The embodiments disclosed herein can be implemented through at least one software program running on at least one hardware device and performing network management functions to control the network elements. The network elements shown in Fig. 1, 2, and 3 include blocks which can be at least one of a hardware device, or a combination of hardware device and software module. The embodiment disclosed herein describes a method for group chat in mobile device. Therefore, it is understood that the scope of the protection is extended to such a program and in addition to a computer readable means having a message therein, such computer readable storage means contain program code means for implementation of one or more steps of the method, when the program runs on a server or mobile device or any suitable programmable device. The hardware device can be any kind of portable device that can be programmed. The device may also include means which could be e.g. hardware means like e.g. an ASIC, or a combination of hardware and software means, e.g. an ASIC and an FPGA, or at least one microprocessor and at least one memory with software modules located therein. The method embodiments described herein could be implemented partly in hardware and partly in software. Alternatively, the invention may be implemented on different hardware devices, e.g. using a plurality of CPUs.
[0042]The foregoing description of the specific embodiments will so fully reveal the general nature of the embodiments herein that others can, by applying current knowledge, readily modify and/or adapt for various applications such specific embodiments without departing from the generic concept, and, therefore, such adaptations and modifications should and are intended to be comprehended within the meaning and range of equivalents of the disclosed embodiments. It is to be understood that the phraseology or terminology employed herein is for the purpose of description and not of limitation. Therefore, while the embodiments herein have been described in terms of preferred embodiments, those skilled in the art will recognize that the embodiments herein can be practiced with modification within the spirit and scope of the embodiments as described herein.

STATEMENT OF CLAIMS
What is claimed is:
1. A system for detecting and controlling MO-SMS Spam in a mobile network, said system comprising of at least one means configured for:
checking if MO-SMS received from mobile user is a spam based on set of filters; and
blocking the SMS service for said mobile user if said MO-SMS is spam.

2. The system as in claim 1, wherein said set of filters are defined on the basis of atleast one of
From Address;
To Address;
MSC Address; and
Duration between subsequent MO-SMS short message.

3. The system as in claim 1, wherein said system is configured to store filters.

4. The system as in claim 1, wherein said system is configured to interface with an HLR (Home Location Register) to block said SMS Service.

5. The system as claimed in claim 1, wherein said system is configured to interface with an SMSC.

6. The system as in claim 1, wherein said system is configured to notify said mobile user about said MO-SMS spam.

7. The system as in claim 1, wherein said system is configured to block said SMS service by sending modified service center address to said mobile user.

8. The system as in claim 1, wherein said system is configured to block said SMS service on SMSC.

9. The system as in claim 1, wherein said system is configured to push details of said mobile user to CRM / Provisioning system of operator to which said mobile user belongs

10. A method for detecting and controlling MO-SMS spam in a mobile network, said method comprising steps of:
checking if MO-SMS received from mobile user is a spam based on set of filters; and
blocking the SMS service for said mobile user if said MO-SMS is spam.

11. The method as in claim 10, wherein said set of filters are defined on the basis of atleast one of
From Address;
To Address;
MSC Address; and
Duration between subsequent MO-SMS short message.

12. The method as in claim 10, wherein an HLR is used to block said SMS service for said mobile user.

13. The method as in claim 10, wherein said mobile user is notified about said MO-SMS spam.

14. The method as in claim 10, wherein said SMS service is blocked by sending modified service center address to said mobile user.

15. The method as in claim 10, wherein said SMS service is blocked on SMSC.

16. The method as in claim 10, wherein details of said mobile user are pushed to CRM / Provisioning system of operator to which said mobile user belongs

Dated this 1st December 2009

Mr. Nishant Kewalramani
Patent Agent