WO2008126100A2

WO2008126100A2 - A method and a system for registering a user for value added services in a telecommunication network

Info

Publication number: WO2008126100A2
Application number: PCT/IN2007/000610
Authority: WO
Inventors: Babu Harish; Abdul Kareem Mohsin
Original assignee: Onmobile Global Limited
Priority date: 2007-04-16
Filing date: 2007-12-28
Publication date: 2008-10-23
Also published as: WO2008126100A3

Abstract

A method and a system for registration of a mobile phone user as a ring back tone (RBT) subscriber are disclosed. The invention enables the mobile phone user to access RBT services without being an RBT subscriber beforehand. In one embodiment of the invention, the mobile phone user is a caller initiating a call with callee. The system, on receiving a request from the caller for accessing a particular RBT service, verifies whether the caller is an RBT subscriber or not. If the caller is an RBT subscriber, the system extends the requested RBT service to the caller. If the caller is not an RBT subscriber, the system registers the caller as an RBT subscriber and extends the requested service to the caller.

Description

TITLE : "A METHOD AND A SYSTEM FOR REGISTERING A USER FOR VALUE ADDED SERVICES IN A TELECOMMUNICATION NETWORK"

FIELD OF THE INVENTION

The invention relates to ring back tones in telecommunication systems. More specifically, the invention relates to a method and a system for registration of a mobile phone user as a ring back tone subscriber.

DEFINITIONS

Caller: The mobile phone user who initiates a call is called a 'caller' Callee: The mobile phone user to whom the call is made is called a 'callee'

Ring back Tone (RBT): A tone which is played to the caller while she is waiting for the callee to respond to the call is called an RBT. The RBT is played till the callee responds to the call.

BACKGROUND

The number of mobile phone users has increased considerably during recent times. With the increase in number of mobile phone users, there has been an increase in the number of value added services that are offered to the mobile phone users. Stiff competition has compelled the providers of the value added services to provide innovative services and improve upon the existing services that are provided to the mobile phone users. Ring Back Tone (RBT) service is one such example of value added services provided to the mobile phone users. RBT service enables the callee to replace the monotonous call progress tone, which is played to a caller when a call is made to the callee, with other tones of choice. The other tones may, for example, be songs, advertisements, news and the likes. Various options are available to configure the RBT service. For example, some RBT services allow the caller to select the RBT played, instead of the callee. Other RBT services allow the caller to set the RBT of the callee as the RBT of the caller. Some RBT services enable the callee to play a customized message to the caller.

Typically, RBT services are provided to the mobile phone user by the mobile phone service provider. The RBT services are not extended automatically to every mobile phone user. Instead, the mobile phone users have to register themselves with an RBT system provided by the mobile phone service provider for accessing the RBT services. The RBT system provides the RBT services to the user. In a typical scenario, the user sends an SMS to a pre-specified number or calls a pre-specified number to register with the RBT system. After the mobile phone user is registered for the RBT services, the RBT system allows the mobile phone user to use the services provided by the RBT system. For example, a service provided by RBT system could be selecting an RBT to be played to any caller, who calls the mobile phone user. A mobile phone user who is registered for the RBT services is hereinafter referred to as an ¹RBT subscriber'. The RBT subscriber is charged a predefined amount by the mobile phone service provider for using the RBT services. Existing RBT systems do not allow the mobile phone users, who are not RBT subscribers, to access the RBT services. Typically, on receiving a request ^' from a mobile phone user for accessing RBT services, the RBT system checks whether or not the mobile phone user is an RBT subscriber. If the mobile phone user is not an RBT subscriber, the RBT system conveys to the mobile phone user that she cannot access the RBT services.

Typically, a caller is attracted towards RBT services after the caller is impressed by listening to the RBT played while the caller is calling a callee. The existing systems, however, do not allow the caller to access the RBT services if she is not an RBT subscriber. For example, some RBT systems provide an RBT service which facilitates the caller to set the RBT of the callee as the RBT of the caller. While listening to the RBT₁ a caller, who is not an RBT subscriber, will not be able to access this RBT service. At a later point of time, when the caller has separately registered for the RBT services, it is possible that the caller may not be able to copy the RBT of the callee. This may happen due to various reasons like, the callee may have changed the RBT or the caller may not recollect which callee had the particular RBT.

The above mentioned limitation result in a non RBT subscriber being unable to use the RBT services in a real time manner. This limitation also results in significant loss of the potential customers of the RBT system. The elimination of above limitation will make RBT services more users friendly. The elimination of above limitation is likely to make the mobile phone service provider more popular and provide the service provider an edge in the competitive market.

Therefore, there exists a need for a system which eliminates the abovementioned limitation and enables a user to access RBT services even when the user is not a registered subscriber of the RBT service.

SUMMARY OF THE INVENTION

A method and a system for registration of a mobile phone user as a ring back tone (RBT) subscriber are disclosed. Registration as an RBT subscriber is generally a precondition for any mobile phone user for accessing the RBT services extended by the mobile phone service provider. The invention enables the mobile phone user to access RBT services without being an RBT subscriber beforehand. According to an embodiment of the invention, the system, on receiving a request from the caller for accessing a particular RBT service, verifies whether the caller is an RBT subscriber or not. Further, certain subscription conditions regarding the subscriber are verified. If the caller is an RBT subscriber and the subscription conditions are satisfied, the system extends the requested RBT service to the caller. If the caller is not an RBT subscriber, the system registers the caller as an RBT subscriber and extends the requested service to the caller. BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic illustrating the environment of the invention;

FIG. 2 is a schematic illustrating a system for providing RBT services to a user in accordance with an embodiment of the invention;

FIG. 3 is a schematic illustrating an application server in accordance with an embodiment of the invention;

FIG. 4 is a flow diagram illustrating a method of providing RBT services to a caller in accordance with an embodiment of the invention; and

FIG. 5 is a flow diagram illustrating a method for the registering a caller as an RBT subscriber in accordance with an embodiment of the invention;

DETAILED DESCRIPTION OF INVENTION

In the following description, for the purposes of explanation, specific details are set forth in order to provide a thorough understanding of the invention. However, it will be apparent that the invention may be practiced without these specific details. Various aspects and features of example embodiments of the invention are described in more detail hereinafter.

FIG. 1 illustrates a telecommunication network environment. According to an embodiment of the invention, the telecommunication network is a GSM network. The call initiated by a caller 102 is received by a Gateway Mobile Switching Center (GMSC) 104. GMSC 104 is a Mobile Switching Center (MSC) through which, mobile phone to mobile phone calls and Public Switched Telephony Network (PSTN) to mobile phone calls are routed. GMSC 104 locates a Terminating Mobile Switching Center (TMSC) 106 which is responsible for handling calls directed towards callee 108. The call is forwarded by GMSC 104 to TMSC 106. The call is then forwarded to callee 108 by TMSC 106. After a connection is established with callee 108, i.e. the mobile phone of callee 108 starts ringing; a switch 110 at GMSC 104 forwards the call to an RBT system 105. The condition for transferring call to RBT system 105 and the process thereafter has been discussed in detail in conjunction with FIG. 4. RBT system 105 is responsible for registration of a mobile phone user as an RBT subscriber. RBT system 105 is also responsible for playing of RBT to caller 102. RBT system 105 is discussed in detail in conjunction with FIG. 2. GMSC 104 is associated with a Home location Register (HLR) 112. RBT system 105 is connected to Home Location register (HLR) 112 via GMSC 104. HLR112 further comprises a switch 114. Switch 114 enables the flow of information from HLR 112 to RBT system 105.

HLR 112 is a database that contains details of each mobile phone subscriber of the telecommunication network. More precisely, HLR 112 contains details of each SIM card issued by the mobile phone operator. For example, HLR 112 stores telephone numbers of the mobile phone user, current location of the mobile phone user, and details regarding the subscription of various services like the RBT services by the user.

RBT system 105 is connected with a mobile phone service provider module 116 which comprises a database. Mobile phone service provider module 116 is connected to RBT system 105 and subscription information is exchanged between RBT system 105 and mobile phone service provider module 116. Further, mobile phone service provider module 116 can upload information on HLR 112. Details regarding the subscription information have been discussed in conjunction with FIG. 3.

In another embodiment of the invention, caller 102 can directly call RBT system 105 at a pre-specified number. The call is routed from caller 102 to RBT system 105 through GMSC 104.

FIG. 2 illustrates RBT system 105 according to an embodiment of the invention. RBT system 105 has the subscription information regarding every RBT subscriber. Subscription information has been discussed in detail in conjunction with FIG. 3. Further, RBT system 105 is responsible for playing RBT to caller 102. RBT system 105 connects to GMSC 104 through signaling cards 202 and media cards 204. The number of signaling cards 202 and media cards 204 depends on the call flow rate, i.e., the number of calls handled by GMSC 104 per unit time. Signaling cards 202 are responsible for SS7/ISUP signal processing, for example, initiation of a call by caller 102, termination of a call by caller 102 etc. An example of signaling cards 202 is NMS TX-4000 cards. Each signaling card 202 is associated with a signaling controller 206. Signaling controller 206 is software, usually written in C/C++ computer language. Signaling controller 206 interfaces with signaling cards 202 and is responsible for SS7/ISUP signal handling.

Media cards 204 are responsible for media processing, for example, playback, recording, DTMF etc. An example of media card 204 is NMS AG-4040 cards. Each media card 204 is associated with a media controller 208. Media controller 208 is software, usually written in C/C++ language. Media controller 208 interfaces with the media cards 204 and are responsible for media processing. Media controller 208 contains multiple 'speech channels' which handle each individual call.

Signaling controller 206 and Media controller 208 corresponding to different signaling cards 202 and media cards 204 are connected via existing protocols like TCP/IP protocol.

Media controller 208 and signal controller 206 are connected with an application server 210 using existing protocols. Application server 210 comprises various Java computer language based applications. Different applications in application server 210 are invoked based on the input from media controller 206 and signaling controller 204. For example, when caller 102 calls callee 108 and callee 108 is an RBT subscriber, a tone player application for playing RBT to caller 102 is invoked. Further details regarding application server 210 have been discussed in conjunction with FIG. 3. FIG. 3 illustrates application server 210 in accordance with an embodiment of the invention. Application server 210 comprises various Java based applications and a database 302. FIG. 3 illustrates three applications viz. tone player 304, tone gatherer 306, and RBT daemon 308. All the three applications are discussed in detail in conjunction with FIG. 5. Although FIG. 3 illustrates only three applications, it will be apparent to a person skilled in the art that application server 210 may comprises several other applications without deviating from the scope of the invention.

All the applications are connected with signaling controller 206, media controller 208, and database 302. Application server 210 sends and receives inputs from the signaling controller 206 and media controller 208. Any transfer of media to and from the applications in the application server 210 is through media controller 208. For example, pressing of DTMF key by caller 102 is recognized by media controller 208 and is conveyed to tone player 304. Similarly, playing of RBT to caller 102 from tone player 304 is routed through the media controller 208.

Signaling controller 206 sends signaling information to application server 210, for example, when callee 108 is busy or declines the call, a signaling message indicating the status of callee 108 is sent to application server 210. Similarly, on receiving the signaling information that a connection is established between caller 102 and callee 108, tone player 304 starts playing RBT to caller 102. Further, on receiving signaling information callee 108 is busy or has declined the call; tone player 304 stops the playback of RBT to caller 102.

Database 302 is accessible by different applications in the application server 210. Database 302 contains subscription information regarding RBT subscribers. Subscription information may include phone number of the RBT subscribers, time of RBT subscription, RBT used by RBT subscriber etc. Subscription information also includes charges for registration, charges for accessing any particular RBT service and other related information. Database 302 also contains various RBTs which can be used by RBT subscribers as their RBT. Further, database 302 contains information stored by different applications from time to time.

According to an embodiment of the invention, when caller 102 initiates a call with callee 108, the call is routed through GMSC 104. Thereafter, GMSC 104 queries HLR 112 to identify if callee 108 is an RBT subscriber. HLR 112 responds back to GMSC 104 regarding the callee's RBT information. The RBT information includes information like status of RBT subscription for callee 108, and the nature of RBT service accessed by callee 108. GMSC 104 then forwards the call to callee 108 through TMSC 106. After the connection is established between caller 102 and callee 108, i.e., the phone of callee starts ringing, switch 110 at GMSC 104 forwards the call to RBT system 105. In one embodiment of the invention, call is transferred to RBT system 105 only if callee 108 is an RBT subscriber. Signaling controller 206 receives signal regarding the establishment of connection and forwards the signal to tone player 304. Tone player 304, then, starts playing the RBT of callee 108 to caller 102. RBT media is then transferred to caller 102 via media controller 208. RBT is played till callee 108 responds to the call or there is a call failure. In case callee 108 responds to the call or there is a call failure, a signal containing such information is received by signaling controller 206 from GMSC 104. Signaling controller 206 transfers the information to tone player 304. On receiving such information from signal controller 206, tone player 304 stops playing of RBT.

FIG. 4 is a flow diagram illustrating a method of providing RBT services to a caller in accordance with an embodiment of the invention. The method of FIG. 4 is executed when caller 102 calls callee 106, and RBT set by callee 106 is played to caller 102. At step 402, caller 102 sends a request to RBT system 105 for accessing the RBT being played, while still listening to the RBT. In one embodiment of the invention, the request can be send by caller 102 through pressing of DTMF keys. The pressing of DTMF key by caller 102 is recognized by media controller 208. The information regarding pressing of DTMF key by caller 102 is passed on to tone player 302. Tone player 302, on receiving the information, makes an entry into database 302. The entry comprises phone number of caller 102, phone number of callee 108, the information regarding RBT of callee 108, time of pressing of DTMF key etc. All the entries such made by tone player 304 are stored in database 302. The entries such made by tone player 302 are read by tone gatherer 306 one by one. In case callee 108 does not respond to the call, i.e., if the call fails, caller 102 can send a request to RBT system 105 for accessing an RBT service. The RBT service could be, for example, setting the RBT of the callee 108, which caller 102 was listening, as the RBT of the caller 102. In one embodiment of the invention, system 105 can send a voice message to caller 102 while RBT is being played, or after the call has failed, asking whether caller 102 would like to access a particular RBT service. Caller 102 can then use various means to send the request for the RBT service. The means for sending the request may include DTMF keys, voice request and the likes.

At step 404, tone gatherer 306 verifies whether caller 102 is an RBT subscriber or not. In order to verify, tone gatherer 306 reads the entries one by one. In any particular entry, tone gatherer 306 reads the caller's information, like phone number of caller 102, and searches for the information in the database 302. In case of caller 102 being an RBT subscriber, the subscription information regarding caller 102 is found by tone gatherer 306 in the database. If at step 404 tone gatherer 306 identifies that caller 102 is an RBT subscriber, step 408 is executed.

Tone gatherer 306 also performs a few other checks along with verifying whether or not caller 102 is an RBT subscriber. For example, caller 102 has pressed DTMF key for setting RBT of callee 108 as RBT of caller 102. Tone gatherer verifies whether setting of that particular RBT of callee 108 is allowed or not. For example, RBT of callee 108 could be a personalized message which callee 108 does not wants to be set by caller 102 as RBT of caller 102. In this case, caller 102 will not be able to access this particular RBT service.

If the caller is not a registered RBT subscriber then step 406 is executed. At step 406, RBT system 105 registers the caller as an RBT subscriber. The registering step has been discussed in detail in conjunction with FIG. 5.

At step 408, the requested RBT service is extended to the caller. If the user has requested for setting the RBT of the callee as the RBT of the caller, the RBT of the callee is set as RBT of the caller. Extending of the requested service is also a two way process similar to registration. Firstly, information regarding the caller 102 having accessed the RBT service is stored in database 302 by Tone gatherer 306. Thereafter, RBT daemon 308 sends the information to mobile phone service provider module 116 which is uploaded by mobile phone service provider module 116 on HLR 112. After RBT of callee 108 is set as RBT of caller 102, any person calling caller 102 will hear that particular RBT.

According to an embodiment of the invention, steps 404, 406, and 408 of the method are executed in a real-time manner, i.e., these steps follow each other automatically without any inputs from caller 102. The execution of these steps may be transparent to caller 102 and caller 102 may not be informed about the execution of these steps. In another embodiment of the invention, a message is sent to caller 102 informing caller 102 about the execution of these steps. A response may also be required from caller 102 before the next step is executed. FIG. 5 is a flow diagram illustrating the method for registration of caller 102 as RBT subscriber in accordance with an embodiment of the invention. Registering of caller 102 as RBT subscriber is a two step process. First, caller 102 is registered with RBT system 105. Secondly, Caller 102 is registered with HLR 112 via mobile phone service provider.

If the caller 102 is not an RBT subscriber, at step 502, caller 102 is registered with RBT system 105. For registration, tone gatherer 306 collects subscription information regarding the caller 102. Subscription information comprises phone number of the caller, time of sending of request for the RBT service to RBT system 105, mode of sending of request to RBT system 105 and other information. All the relevant information is then stored in database 302. The abovementioned procedure registers caller 102 with RBT system 105.

At step 504, RBT daemon 308 collects subscription information of caller 102 from database 302 and sends the subscription information to mobile phone service provider module 116. The subscription information also includes the charges for registration and the charges for the RBT service requested by caller 102. Various means can be used for sending the subscription information. For example, the subscription information can be send through File Transfer Protocol (FTP). Another method could be sending the subscription information to a mobile phone service provider's configured HTTP URL.

At step 506, mobile phone service provider module 116 reads the subscription information and checks whether the service conditions are satisfied or not. Service condition can include conditions such as; balance available with the caller 102 must be greater than the charges for registration and the RBT service accessed by caller 102.

In case the subscription conditions are not satisfied, mobile phone service provider module 116 sends the information to RBT daemon 308. This information can be send via FTP route. At step 508, subscription information of caller 102 is removed from database 302 i.e. caller is de-registered with system 105. Further, if the subscription conditions are not satisfied, step 408 of FIG. 4 is not executed.

In case the subscription conditions are satisfied, a pre specified amount is deducted from the account of caller 102, by mobile phone service provider, and thereafter step 510 is executed. At step 510, the subscription information is uploaded by the mobile phone service provider module 116 on HLR 112.

While example embodiments of the invention have been illustrated and described, it will be clear that the invention is not limited to these embodiments only. Numerous modifications, changes, variations, substitutions and equivalents will be apparent to those skilled in the art without departing from the spirit and scope of the invention as described in the claims.

Claims

CLAIMS :

1. A method for extending ring back tone service to a mobile phone user, the mobile phone user being a caller initiating a call with a cailee in a telecommunication network, a ring back tone of the cailee being played to the caller, the method comprising:

a. receiving a request from the caller for setting the ring back tone of the cailee as ring back tone of the caller;

b. verifying that the caller is not a ring back tone subscriber;

c. registering the caller as a ring back tone subscriber based on the verification; and

d. extending the requested ring back tone service to the caller in a real time manner.

2. The method as recited in claim 1 , wherein the step of receiving a request comprises the step of recognizing a DTMF key response by the caller.

3. The method as recited in claim 1 , wherein telecommunication network is GSM telecommunication network.

17

4. The method as recited in claim 1 , wherein the step of registering comprises the step of registering the caller as ring back tone subscriber in a home location register.

5. The method as recited in claim 1 further comprising the step of verifying subscription condition for the caller.

6. A system for extending ring back tone service to a mobile phone user, the mobile phone user being a caller initiating a call with a callee in a telecommunication network, a ring back tone of the callee being played to the caller, the system comprising:

a. means for receiving a request from the caller for setting the ring back tone of the callee as ring back tone of the caller;

b. means for verifying that the caller is not a ring back tone subscriber;

c. means for registering the caller as a ring back tone subscriber based on the verification; and

d. means for extending the requested ring back tone service to the caller in a real time manner.

7. The method as recited in claim 1 , wherein the step of receiving a request comprises the step of recognizing a DTMF key response by the caller.

8. The method as recited in claim 1 , wherein telecommunication network is GSM telecommunication network.

9. The method as recited in claim 1 , wherein the step of registering comprises the step of registering the caller as ring back tone subscriber in a home location register.

10. The method as recited in claim 1 further comprising the step of verifying subscription condition for the caller.