The subject matter described herein relates to providing a messaging service in a communications network. More particularly, the subject matter described herein relates to methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network.
Presently, providers of goods and services must often rely on traditional methods for advertising and distributing coupons to potential customers. Television commercials, radio segments, Internet advertisements, and newspaper circulars are a few examples of the current methods in which businesses attempt to communicate with and attract prospective buyers. However, these manners of advertising may be considered inefficient due to being too dispersed and not targeted to a pertinent customer. Notably, these current methods for advertising fail to take advantage of recent technological features and capabilities afforded by mobile phones, personal digital assistants (PDAs), smart phones, and like devices. More specifically, these personal communication devices are capable of providing a seller the opportunity to immediately communicate with a potential buyer in a more direct and focused manner using messaging service messages or electronic mail (e-mail).
Current methods used to send targeted ads to mobile services include location-based services that send ads to a mobile phone when the mobile phone enters a geographic area. Such ads relate to businesses within the geographic are so that the mobile phone user will purchase a good or service from one of the businesses. However, one problem with location-based advertising to mobile devices is that such advertising does not take into account interests of the prospective buyer. Location-based ads may even be viewed as spam and may be deleted by the prospective buyer.
Accordingly, there exists a need for improved methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network.
The subject matter described herein comprises methods, systems, and computer program products for providing a call attempt triggered messaging service in a communications network is described. One method includes the intercepting of a call signaling message that includes a calling party subscriber identifier and a called party subscriber identifier. A call attempt triggered message generation (CATMG) database using the called party subscriber identifier is queried. In the event the called party subscriber identifier exists in the CATMG database, a messaging service message is generated. The messaging service message is then transmitted to a contact address.
The subject matter described herein for providing a call attempt triggered messaging service may be implemented using a computer program product comprising computer executable instructions embodied in a computer readable medium that are executed by a computer processor. Exemplary computer readable media suitable for implementing the subject matter described herein includes disk memory devices, programmable logic devices, and application specific integrated circuits. In one implementation, the computer readable medium may include a memory accessible by a processor. The memory may include instructions executable by the processor for implementing any of the methods for providing a call attempt triggered messaging service described herein. In addition, a computer readable medium that implements the subject matter described herein may be distributed across multiple physical devices and/or computing platforms.
Preferred embodiments of the subject matter described herein will now be explained with reference to the accompanying drawings of which:
The present subject matter relates to systems and methods for providing a call attempt triggered message generation (CATMG) service in a communications network. According to one aspect of the present subject matter, a CATMG service includes receiving or intercepting a call setup signaling message (e.g., SS7 ISUP IAM message, SIP Invite message, etc.) during transit through a communications network and subsequently generating a messaging service message (e.g., a short messaging service (SMS) message, an instant message, a multimedia messaging service message, an electronic mail message, etc.) in response to receiving or intercepting the call setup signaling message or any other similar attempt to establish a call.
Although the examples presented herein are associated with the reception (or interception) of SS7 ISUP call signaling messages and SS7 ISUP call signaling messages sent using SIGTRAN protocols, those skilled in the art realize the present subject matter is not limited to SS7 and SIGTRAN implementations. For instance, the present subject matter may be implemented in various signaling networks that employ non-SS7 signaling protocols, such as session initiation protocol (SIP).
Network routing element 104 also includes a CATMG rules database 116 that contains a listing of number identifiers of various persons, companies, and/or other entities that subscribe to the messaging service. For example, database 116 may contain a listing of identifier numbers that correspond to companies that desire advertisement content or a coupon to be sent to a calling party that attempts to call a predefined number (which is stored in database 116 and is unique to each company). An exemplary CATMG rules database 116 is depicted in
Network routing element 104 may also host a content database 117 that contains the companies' respective coupons, advertisement content, and other similar data. CATMG function 114 utilizes content database 117 as the source of the content that is ultimately incorporated into the generated response messages (e.g., SMS messages, email messages, etc.). In one embodiment, content database 117 may also co-exist with CATMG database 114 in a common database on network routing element 104. In an alternate embodiment, content database 117 can be stored on a separate computer as opposed to residing locally on network routing element 104. Similarly, in an alternate embodiment, network routing element 104 may contain, or be coupled to, permissions database 122. Permissions database 122 may contain a listing of calling party subscribers that have provided permission to receive messaging service messages (or other response messages) from network routing element 104.
In block 304, a called party subscriber database (i.e., CATMG rules database 116) is queried using the called party identifier. In one embodiment, screening function 113 may be adapted to utilize the called party identifier in the received call setup signaling message to query (or access) CATMG rules database 116 in order to determine if the CATMG service is to be performed. For example, after network routing element 104 receives a call setup message intended for 919-460-5500, screening function 113 queries CATMG rules database 116 to ascertain if 919-460-5500 is an entry that can “trigger” the CATMG service.
In block 306, a determination as to whether the identifier number is stored in CATMG rules database 116 is made. If the identifier number is not listed in CATMG rules database 116, then method 300 continues to block 308 where the call setup signaling message is routed in a conventional manner. If the identifier number is located in CATMG rules database 116, then the method 300 proceeds to block 310 where a copy of the call setup signaling message is made by screening function 113 and the original call setup signaling message is then routed in a conventional manner (i.e., the original call setup signaling message is not retained). In one embodiment, the determination process comprises a LIM-based screening process (e.g., screening function 113) that ascertains whether the call setup signaling message contains a “triggered” number. Triggered called party number information (e.g., an identifier number) may be maintained at CATMG rules database 116 within network routing element 104 and accessed by a LIM-based screening function.
In block 312, a response message (e.g., a messaging service message, email message, instant message, etc.) is generated. In one embodiment, CATMG function 114 generates an SMS message in response to the determination that the called party identifier is located in CATMG rules database 116. Notably, CATMG function 114 addresses the SMS message to the calling party subscriber identifier (e.g., the calling party number) that was located in the originally received call setup signaling message. During the generation process, CATMG function 114 may include a coupon, advertisement content, and/or any other type of data in the SMS message. The content data may be obtained from a local content database 120 (see
In block 314, the response message is transmitted to a contact address. In one embodiment, network routing element 104 transmits the SMS message (generated in block 312) to the contact address contained within the SMS message (i.e., the calling party identifier 919-380-3814). The method 300 then ends.
In one embodiment, the method 300 may only be performed if the calling party is a subscriber to the CATMG service as well. For example, network routing element 104 may be adapted to access permissions database 122 to determine if the calling party is a subscriber to the CATMG service prior to generating the messaging signal message. If the calling party's identifier number is stored in permissions database 122, then method 300 is executed normally. Conversely, if the subscriber's identifier number cannot be located in permissions database 122, then method 300 is not permitted to be performed.
Shown in
CATMG rules database 116 is adapted to maintain triggered called party numbers and associated data and actions. In one embodiment of the subject matter, CATMG rules database 116 may include, for each entry, a subscriber permission field that indicates whether a calling subscriber has provided permission to receive automatically generated message service messages in response to call attempts by the calling subscriber. If the subscriber permission field indicates that the calling party permits the generation and reception of a message service message, then a message may be generated and sent to the calling subscriber when the calling subscriber initiates a call to a targeted number. If the permission field indicates that the subscriber does not permit an automatic SMS generation, then such generation may not occur.
In an alternate implementation, a separate subscriber permission database 122 may be maintained to determine whether or not a calling subscriber permits or does not permit automatic SMS message generation in response to call attempts by the subscriber.
The present subject matter may also be implemented in a manner where the SMS message is transmitted to a device that is not associated to the subscriber identifier specified in the received call setup signaling message (e.g., the response message is not sent back to a calling party's cellular phone, which was used to make the initial call). In one embodiment, as illustrated in
In one exemplary implementation of the above embodiment, CATMG function 114 is adapted to maintain call attempted triggered messaging rules that may be specified by a parent or guardian with respect to their child. For example, CATMG function 114 may contain a call attempt triggered messaging rule which specifies that an SMS message is to be sent to a parent subscriber (or any designated third party) when his (or her) child attempts a call to a predetermined number (e.g., a 900 number, a number that a parent has placed on a restricted list or “blacklist” for that child, etc.). The SMS message may contain information that identifies the called party number as well as date/time stamp information. It is further appreciated that the same basic call attempt triggered message generation can be used to notify a parent or guardian when a “blacklisted” calling party is attempting to call their child. That is, CATMG function 114 may contain a call attempt triggered messaging rule which specifies that an SMS message is to be sent to a parent subscriber (or any designated third party) when a number/subscriber identifier (e.g., POTS number, SIP URI, etc.) that a parent has placed on a restricted list or “blacklist” for that child attempts to place a call to the child. It is appreciated that in various embodiments of the present subject matter, more complex CATMG rules may be specified. For example, rules may be specified in CATMG rules database 116 that dictate a predefined time period limitation, such as a day of week and/or time of day call attempt limitations. For example, a parent may wish to be notified of any call attempts made by their child during school hours, or any call attempts made by their child after 11 pm, etc.
With regard to these embodiments, it is appreciated that CATMG function 114 may, in addition to generating and transmitting a call attempt triggered messaging service message, enforce “blacklist” rules by blocking or terminating a call setup to a called party that is specified in the restricted list or “blacklist”. For example, CATMG function 114 may intercept an ISUP IAM message associated with call attempt to a “blacklisted” called party. CATMG function 114 may subsequently generate and transmit a messaging service message to a predetermined party (e.g., the parent subscriber) and additionally may discard the IAM message. In one embodiment, an associated ISUP release message may also be generated and transmitted by CATMG function 114. In this manner, not only is the parent notified of the child's attempt to call a “blacklisted” number, but the call attempt is ultimately denied.
In yet another embodiment, the present subject matter may be implemented with a toll free (e.g., 800 number service) database 602. As illustrated in
As an example of how a coupon can be provided to a calling party,
For example, by using an application on a mobile handset, mobile computing device, personal computer, etc., a parent of a child may register with CATMG function 114 to receive a notification each time the child attempts a call to a “900” number service. This registration may be accomplished using a SIP subscribe method message. The SIP subscribe method message may include the telephone number or URI associated with the child (e.g., the child's mobile phone number), the “blacklisted” number(s) (or a restricted number range) or URI(s) that the child is not allowed to call. The SIP subscribe method message may also include a contact address (e.g., MAILTO:URI, IM:URI, MMS:URI, etc.) to which the notification message is to be sent in the event the child attempts to call one of the “blacklisted” numbers or URIs. In one embodiment, CATMG function 114 maintains the subscription request and associated rule. In the event that a call attempt to one of the “blacklisted” numbers or URIs is made by the child, CATMG function 114 is adapted to notify the parent (at the specified contact address) using a SIP Notification method message. It is appreciated that methods and messages other than the exemplary SIP subscribe/notify methods may be used to accomplish the same function in a SIP/IMS network environment, and that the present subject matter is not limited to implementations that utilize SIP subscribe/notify methodologies.
It will be understood that various details of the subject matter described herein may be changed without departing from the scope of the subject matter described herein. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the subject matter described herein is defined by the claims as set forth hereinafter.
The present application claims the benefit of U.S. Provisional Patent Application Ser. No. 60/854,652, filed Oct. 26, 2006; the disclosure of which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
5684951 | Goldman et al. | Nov 1997 | A |
5768509 | Gunluk | Jun 1998 | A |
6047327 | Tso et al. | Apr 2000 | A |
6564055 | Hronek | May 2003 | B1 |
7072667 | Olrik et al. | Jul 2006 | B2 |
7072976 | Lee | Jul 2006 | B2 |
7095829 | Claudatos et al. | Aug 2006 | B2 |
7116972 | Zhang et al. | Oct 2006 | B1 |
7120455 | Chen et al. | Oct 2006 | B1 |
7136634 | Rissanen et al. | Nov 2006 | B1 |
7155243 | Baldwin et al. | Dec 2006 | B2 |
7248857 | Richardson et al. | Jul 2007 | B1 |
7299050 | Delaney et al. | Nov 2007 | B2 |
7321779 | Kang | Jan 2008 | B2 |
7394818 | Johnson et al. | Jul 2008 | B1 |
7403788 | Trioano et al. | Jul 2008 | B2 |
7454164 | Goss | Nov 2008 | B2 |
7463898 | Bayne | Dec 2008 | B2 |
7502335 | Lin | Mar 2009 | B2 |
7548756 | Velthuis et al. | Jun 2009 | B2 |
7817987 | Mian et al. | Oct 2010 | B2 |
7912908 | Cai et al. | Mar 2011 | B2 |
7917128 | Niekerk et al. | Mar 2011 | B2 |
20020010745 | Schneider | Jan 2002 | A1 |
20020013711 | Ahuja et al. | Jan 2002 | A1 |
20020023164 | Lahr | Feb 2002 | A1 |
20020095333 | Jokinen et al. | Jul 2002 | A1 |
20020120717 | Giotta | Aug 2002 | A1 |
20020126708 | Skog et al. | Sep 2002 | A1 |
20020147928 | Mahajan et al. | Oct 2002 | A1 |
20030003935 | Vesikivi et al. | Jan 2003 | A1 |
20030027591 | Wall | Feb 2003 | A1 |
20030032409 | Hutcheson et al. | Feb 2003 | A1 |
20030069991 | Brescia | Apr 2003 | A1 |
20030076941 | Tiliks et al. | Apr 2003 | A1 |
20030093314 | Leung et al. | May 2003 | A1 |
20030096625 | Lee et al. | May 2003 | A1 |
20030131263 | Keane et al. | Jul 2003 | A1 |
20040054576 | Kanerva et al. | Mar 2004 | A1 |
20040137922 | Kang | Jul 2004 | A1 |
20040203581 | Sharon et al. | Oct 2004 | A1 |
20040221011 | Smith et al. | Nov 2004 | A1 |
20040243719 | Roselinsky | Dec 2004 | A1 |
20050003838 | McCann et al. | Jan 2005 | A1 |
20050021666 | Dinnage et al. | Jan 2005 | A1 |
20050027867 | Mueller et al. | Feb 2005 | A1 |
20050068971 | Meisl et al. | Mar 2005 | A1 |
20050130685 | Jenkin | Jun 2005 | A1 |
20060047572 | Moore et al. | Mar 2006 | A1 |
20060120358 | Narasimhan et al. | Jun 2006 | A1 |
20060168003 | Vau et al. | Jul 2006 | A1 |
20060199597 | Wright | Sep 2006 | A1 |
20060218613 | Bushnell | Sep 2006 | A1 |
20060253453 | Chmaytelli et al. | Nov 2006 | A1 |
20070026878 | Midkiff et al. | Feb 2007 | A1 |
20070072591 | McGary et al. | Mar 2007 | A1 |
20070088851 | Levkovitz et al. | Apr 2007 | A1 |
20070206747 | Gruchala et al. | Sep 2007 | A1 |
20070271139 | Fiorini | Nov 2007 | A1 |
20070275738 | Hewes et al. | Nov 2007 | A1 |
20070282954 | Kim et al. | Dec 2007 | A1 |
20070287463 | Wilson | Dec 2007 | A1 |
20080004046 | Mumick et al. | Jan 2008 | A1 |
20080031196 | Marathe et al. | Feb 2008 | A1 |
20080051066 | Bandhole et al. | Feb 2008 | A1 |
20080101370 | Marsico et al. | May 2008 | A1 |
20080139170 | Kahn | Jun 2008 | A1 |
20080161028 | Fondë et al. | Jul 2008 | A1 |
20080287150 | Jiang et al. | Nov 2008 | A1 |
20090017794 | Wilson | Jan 2009 | A1 |
20090047980 | Wilson | Feb 2009 | A1 |
20090111489 | Wilson | Apr 2009 | A1 |
20100210292 | Nooren | Aug 2010 | A1 |
Number | Date | Country |
---|---|---|
1625146 | Jun 2005 | CN |
1 705 885 | Sep 2006 | EP |
10-0600335 | Jul 2006 | KR |
10-2008-0054737 | Jun 2008 | KR |
10-2008-0111175 | Dec 2008 | KR |
WO 9949686 | Sep 1999 | WO |
WO 0106679 | Jan 2001 | WO |
WO 0239765 | May 2002 | WO |
WO 02063849 | Aug 2002 | WO |
WO 02078381 | Oct 2002 | WO |
WO 03001770 | Jan 2003 | WO |
WO 03088690 | Oct 2003 | WO |
WO 2004100470 | Nov 2004 | WO |
WO 2004104735 | Dec 2004 | WO |
WO 2004105405 | Dec 2004 | WO |
WO 2007080570 | Jul 2007 | WO |
WO 2007141762 | Dec 2007 | WO |
WO 2008085830 | Jul 2008 | WO |
WO 2008130565 | Oct 2008 | WO |
WO 2010094038 | Aug 2010 | WO |
Number | Date | Country | |
---|---|---|---|
20080285735 A1 | Nov 2008 | US |
Number | Date | Country | |
---|---|---|---|
60854652 | Oct 2006 | US |