Method for restricting the transmission of short messages
Technical field of the invention
The invention relates to a method for restricting the transmission of short messages in a core network node.
Description of related art
Short message service is well known and increasing in number of participants and traffic. It enables to send a short text from a sender to a receiver via a cellular telecommunication network like a GSM (Global System for Mobile telecommunications) or UMTS (Universal Mobile Telecommunications System). A further development is the multimedia messaging service that enables the sending of pictures, text and audio messages. However, an increasing number of short messages and multimedia messages is used for advertisements or the distribution of so called short message viruses. A further problem is the reception of fraudulent "call me back" messages sent by operators of telephone service providers like 0190-services in Germany. Although call barring even for incoming calls is a well-established feature within cellular telecommunications networks, there is currently no means to avoid the reception of short messages available. It is therefore object of the invention to provide means for restricting the transmission of short messages and multimedia messages.
Summary In the following the term short messages is used as a synonym for messages transmitted by using a short message service or a multi media message service. The invention introduces a method for handling short messages in a core network node of a communication network supporting a short message service and a mobile services switching centre for said communication network executing said method.
The method for handling short messages in a core network node of a communication network supporting a short message service, comprises the steps of receiving a short message, identifying the receiver of the short message, retrieving information about a restriction for the transmission of short messages for the user, comparing information
about the short message with retrieved information, and deciding based on the result of the comparison whether to forward the short message to the receiver or to reject the short message. The execution of the invented method in a core network node saves resource on the air interface. If the handling of restrictions would be executed in a user equipment for mobile telecommunication, signalling and data transmission resources would be required.
The core network node may be for instance a mobile services switching centre. This has the advantage that no new node has to be introduced for the handling.
Information about a restriction is retrieved from a visited location register, or a service control function for example. As restriction information in most cases is related to an end user and visited location register are already used for storing a user profile, the invention can be implemented with minor effort. Furthermore interfaces between a mobile services switching centre and a visited location register and respectively a service control function are already defined. By this, existing interfaces can be used for the implementation of the invention. This solution consists in following main steps, restriction data is stored in an home location register in the subscriber profile by the operator, the subscriber profile (together with Restriction data) is downloaded in visited location register during Update Location, Restoration Data procedure or whenever the subscriber profile change. A check on originating address is done in mobile services switching centre /visited location register, if a restriction is found, the SMS is not sent to the MS. The downloading from home location register to visited location register of restriction information can be implemented either as proprietary solution using the extension container of Insert Subscriber Data MAP (Mobile Application Part) message or as standard solution adding new parameters in ISD MAP message.
A mobile services switching centre according to the invention comprises a short message restriction module for retrieving restriction information, for comparing information available about the short message with restriction information and for deciding whether to forward a short message to a receiver or to reject the short message.
Brief description of the figures
Figure 1 depicts a first embodiment of the invention.
Figure 2 depicts a further embodiment of the invention.
Detailed description of the invention
In the following the invention will be described by means of figures and embodiments.
Figure 1 depicts a first embodiment of the invention. A simplified core network supporting a short message service is depicted, comprising a home location register HLR1, a mobile services switching centre MSCl, a visited location register VLR1, a base station controller BSC1, a user equipment UE1 and a short message service centre SMSC1. The home location register HLR1 is connected to the visited location register VLR1 and transmits in a first step 100 restriction information to the visited location register VLR1. The visited location register VLR1 stores said restriction information for example in the subscriber profile. Restriction information can comprise for example the following parameters describing an short message, a subject or title of a message, a type of message, a size, an origin, a service, an identification of art least one of the following: a subscriber, a group of senders, or a server. If at least one of the parameters of a short message matches with at least one of the stored parameters, it will not be forwarded.
The short message service centre SMSC1 requests the mobile services switching centre MSCl in a next step 101 to forward a short message to a subscriber, for example by sending a mobile application part MtForwardSM message.
In a following step 102 the mobile services switching centre MSCl demands restriction data for the addressed subscriber from the visited location register NLR1. The visited location register VLR1 returns the demanded restriction information in a next step 103. The mobile services switching centre MSCl checks, whether there is a match between a parameter describing the short message and a parameter of the restriction information in a next step 104. If there is a match, the mobile services switching centre MSCl rejects the short message and informs the short message service centre SMSC1 in a next step 105 about the rejection, for example by sending a MtForwardResult message. If there is no match, the mobile services switching centre MSCl forwards the short message to the
addressed subscriber and informs the short message centre SMSC1 about it. This can be executed for example by sending a MtForwardResult message.
Figure 2 depicts an alternative embodiment of the invention. A simplified core network supporting a short message service is depicted, comprising a mobile services switching centre MSC2, a service switching function gsmSSF, a service control function gsmSCF, a visited location register VLR2, a base station controller BSC2, a user equipment UE2 and a short message service centre SMSC2. In the depicted embodiment of the invention, it is necessary that the user equipment UE2 comprises a Mobile originating/ mobile terminating-short message service-CSI (Customised application mobile for enhanced logic Service Indication), and that the feature SMS (Short Message Service) Camel
(Customised Application Mobile for Enhanced Logic) Phase 4 or another IN (Intelligent Network) triggering solution for SMS is supported in the mobile services switching centre/visited location register MSC2/VLR2 serving the area, where the user equipment UE2 is currently roaming. In a first step 201 , the short message service centre SMSC2 requests, for example by sending a MAP (Mobile Application Part) message MtForwardSM, the mobile services switching centre MSC2 to forward a short message. In a next step 202, the mobile services switching centre MSC2 requests an intelligent network node, the GSM (Global System for Mobile telecommunications) service control function gsmSCF, through the GSM service switching function gsmSSF, to check, whether restriction information is stored related to the user equipment or its user. The request can be perfomed for example by sending a CAP (CAMEL Application Part) message InitialDPSMS. If the GSM service control function gsmSCF finds matching restriction information, it indicates that the short message shall not be sent to the mobile services switching centre MSC2, for example by sending a CAP ReleaseSMS message. If the GSM service control function gsmSCF does not find any matching restriction information, it indicates this to the mobile services switching centre MSC2 for instance by sending a CAP
ContinueSMS/ConnectSMS message. The mobile services switching centre MSC2 then forwards the short message towards the user equipment UE2. In both cases, forwarding and rejection of the short message, the respective result is sent in a step 204 to the short
message service centre SMSC2. This can be perfomed by sending a MAP MtForwardSMResult message.
The features of the embodiment as described by means of figure 2 can be implemented as a proprietary solution or as a standard solution. In the case that a proprietary solution chosen, it is possible to reuse a generic rpCause in the Release message sent on the CAP interface as showed in the Fig. 2. In the case that a standardised solution is chosen, the 3GPP (3rd Generation Partnership Project) technical specifications TS 23.040 Technical realization of the Short Message Service (SMS), TS 29.078 CAMEL Application Part (CAP) specification, and TS 23.078 Customized Applications Mobile Enhanced Logic - Stage 2 have to be adapted. It is for example necessary to add an rpCause in the above mentioned release message.