Patent Application
20080075249
The invention is herein described, by way of example only, with reference to the accompanying drawings. With specific reference now to the drawings in detail, it is stressed that the particulars shown are by way of example and for purposes of illustrative discussion of exemplary embodiments of the present invention only, and are presented in order to provide what is believed to be the most useful and readily understood description of the principles and conceptual aspects of the invention. In this regard, no attempt is made to show structural details of the invention in more detail than is necessary for a fundamental understanding of the invention, the description taken with the drawings making apparent to those skilled in the art how the several forms of the invention may be embodied in practice.
A brief description of each of the drawings is set forth below:
The present embodiments comprise an apparatus and a method for notification of a failed prepaid call, initiated in a telephony network by a calling party to a called party.
Currently, a user of a telephony network, such as a cellular telephony network, may subscribe to a prepaid calling service in the telephony network. The subscribed user pre-pays for call credit, assigned to the user by the telephony network operator.
According to exemplary embodiments of the present invention, when a call initiated by the subscribed user is blocked due to insufficient prepaid call credit left for the subscribed user, the air time and revenue lost as a result of the blocking of the call may be recovered.
According to the exemplary embodiments, when the prepaid call fails, the called party may be automatically notified of the failed attempt of the calling party, who is the prepaid calling service subscriber, to call the called party.
Once the called party receives the notification regarding the failed attempt to call him, the called party may initiate a call to the calling party of the prepaid call. Consequently, the revenues and air time potentially lost as result of the failure of the prepaid call may be recovered.
Optionally, the called party may also be automatically connected to the calling party in a callback call, provided that the called party agrees to be connected in the callback call (and to pay for the callback call).
Thus, according to the exemplary embodiments, the calling party does not have to take an active role in the effort to recover the lost prepaid call (for example—by initiating an SMS message). Furthermore, the exemplary embodiments may provide an apparatus and a method which may prove significantly less prone for abuse by users.
The principles and operation of an apparatus and a method according to the exemplary embodiments of the present invention may be better understood with reference to the drawings and accompanying description.
Before explaining at least one embodiment of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the following description or illustrated in the drawings.
The invention is capable of other embodiments or of being practiced or carried out in various ways. Also, it is to be understood that the phraseology and terminology employed herein is for the purpose of description and should not be regarded as limiting.
Reference is now made to
Apparatus 1000 includes a failed prepaid call data capturer 110.
The failed prepaid call data capturer 110 is deployed in the telephony network, and configured to capture data pertaining to the failed prepaid call from the telephony network. The failed prepaid call is initiated by a calling party 101 to a called party 102 in the telephony network.
Optionally, the failed prepaid call data capturer 110 captures the data pertaining to the failed prepaid call from the telephony network, as the prepaid call fails, or immediately after the failure of the call.
Optionally, the failed prepaid call data capturer 110 uses a predefined capturing policy when capturing the data pertaining to the failed prepaid call. For example, the predefined capturing policy may define rules for recognizing a failed prepaid call, rules for distinguishing between relevant and non-relevant failed calls (the latter calls being ignored by the failed prepaid call capturer 110), etc.
The apparatus further includes a notifier 120, connected to the prepaid call data capturer 110.
The notifier 120 automatically notifies the called party 102 about the failed prepaid call, using the data captured by the failed prepaid call data capturer 110.
Optionally, the notifier 120 may notify the called party 102 about the failed prepaid call utilizing Short Message Service (SMS).
SMS is a service available on most digital mobile phones. SMS permits the sending of short messages between mobile phones, other handheld devices, and even landline phones which are preconfigured for receiving SMS messages.
Optionally, the notifier 120 may notify the called party 102 about the failed prepaid call utilizing Unstructured Supplementary Services Data (USSD).
USSD is a method of transmitting information or instructions over a GSM network (GSM—Global System for Mobile communication is European digital standard for mobile or cellular telephony). USSD has some similarities with SMS since both use the signaling path of a cellular GSM network.
However, unlike SMS, USSD is not a store and forward service and is session-oriented, such that when a user accesses a USSD service, a session is established and the radio connection stays open until the user, an application, or a time out releases it.
Optionally, the notifier 120 may notify the called party 102 about the failed prepaid call utilizing email, WAP (Wireless Application Protocol), MMS (Multimedia Message Service), or any other method for transmitting information over a cellular network.
Optionally, the notifier 120 automatically establishes a callback call connection between the called party 102 and the calling party 101 of the failed prepaid call. As known in the art, the called party 102 must first agree to accept the callback call before the callback connection is actually opened for both the called party 102 and the calling party 101, as the called party 102 may have to pay for the callback call.
Reference is now made to
A system according to an exemplary embodiment is implemented as a part of a central infrastructure of a cellular telephony network. The cellular telephony network connects a handset 10 used by a calling party of a prepaid call and a handset 90 used by a called party of the prepaid call.
The cellular telephony network includes one or more Mobile Switching Center(s) (MSC) 20. A Mobile Switching Center (MSC) is a computer that places the calls, and takes and receives data from the subscriber(s) of the network or from a PSTN (Public switched Telephone Network).
The cellular telephony network further includes a Real Time Billing (RTB) system 30. The Real Time Billing (RTB) handles the financial aspects of cellular phone calls, including, but not limited to: billing prepaid calls, managing credit assigned to the calling party for prepaid calls, rejecting prepaid call attempts when the calling party runs out of credit, etc.
The cellular telephony network further includes a Short Message Service Center (SMSC) 80 which provides a Short Message Service (SMS), for routing SMS or other short messages between subscribers of the telephony network, as well as users of other telephony networks. As discussed above, the cellular telephony network may optionally include a Multi-Media Message Service (MMS) or other services for communicating to the called phone 90.
System 40, for notification of a failed prepaid call, includes a failed prepaid call capturer 70.
The failed prepaid call capturer 70 is implemented as a server mediating between the cellular network and the system 40. The failed prepaid call data capturer 70 captures data pertaining to a failed prepaid call, blocked by the RTB system 30, described hereinabove.
System 40 further includes a notifier 60 implemented as a Notification Delivery Unit (NDU) on a dedicated server. The notifier 60 is functionally associated with to the failed prepaid call capturer 70.
The notifier 60 automatically notifies the called party 90 about the failed prepaid call, using the data captured by the failed prepaid call data capturer 70.
The notifier 60 may notify the called party 90 about the failed prepaid call from the calling party 10, utilizing, for example, Short Message Service (SMS), utilizing Unstructured Supplementary Services Data (USSD), or using any other messaging service available in the telephony network.
Optionally, the notifier 60 automatically establishes a callback call connection between the called party 90 and the calling party 10 of the failed prepaid call. As known in the art, the called party 90 must first agree to accept the callback call before the callback connection is actually opened for both the called party 90 and the calling party 10, as the called party may have to pay for the callback call.
Optionally, system 40 further includes a database 50 for recording information pertaining to captured failed prepaid call, the notification of the called party of the failed prepaid call, the callback call connection established between the called party 90 and the calling party 10, etc.
Reference is now made to
Method 3000 includes capturing 310 data pertaining to the failed prepaid call from the telephony network (such as a cellular telephony network). The capturing 310 may be carried out using a failed prepaid call capturer 110, as described in further detail hereinabove.
Next, the called party is automatically notified 320 of the failure of the prepaid call, using the data pertaining to the failed prepaid call captured 310 from the telephony network.
Optionally, the capturing 310 of the data pertaining to the failed prepaid call is carried out immediately as the prepaid call fails, or soon thereafter. For example, when the prepaid call is blocked due to the exhaustion of the credit assigned to the calling party for prepaid calls, as described in greater detail hereinabove.
Optionally, the capturing 310 of the filed prepaid call is carried out using a predefined capturing policy. The capturing policy may define, but is not limited to: rules for recognizing a failed prepaid call, rules for distinguishing between relevant and non-relevant failed calls (the latter calls being ignored during the capturing 310), etc.
Optionally, method 3000 further includes establishing a callback call connection between the called party 102 and the calling party 101 of the failed prepaid call. As known in the art and discussed hereinabove, the called party 102 has to agree to accept the callback call before the callback connection is actually opened for both the called party 102 and the calling party 101, as the called party 102 may have to pay for the callback call.
Optionally, the capturing of the failed prepaid call also includes monitoring of data traffic between one or more mobile switching center(s) and a billing system, in a cellular network, as described in further detail hereinabove.
Optionally, the capturing of the failed prepaid call also includes analyzing data generated by a real time billing system used for billing the calling party 101 for prepaid calling.
Optionally, the capturing of the failed prepaid call also includes analyzing Parlay event data generated in the telephony network.
Parlay is a family of application programming interfaces (APIs) defined by a telecomm industry consortium seeking to standardize a set of abstract high-level interfaces for use by third-party programmers. The set of abstract high-level interfaces is used by the third-party programmers in building applications that leverage the services and functionality exposed by telecommunication network elements.
Optionally, the capturing of the failed prepaid call also includes analyzing Open Scripting Architecture (OSA) event data generated in the computer infrastructure of the telephony network, as known in art.
Optionally, the capturing of the failed prepaid call also includes analyzing Intelligent Network Application Part (INAP) event data generated in the telephony network.
INAP is an intelligent network protocol used in European SS7 (a cellular protocol) cellular networks to query their databases for a variety of functions not related to call setup and tear down. INAP uses the ASN.1 standard for defining message content. ASN.1 is an international standard used for specification of data in communication protocols.
Optionally, the capturing of the failed prepaid call includes analyzing information generated by Customized Applications for Mobile networks Enhanced Logic (CAMEL). CAMEL is a set of GSM standards designed to work on a GSM core network. The standards allow an operator to define services over and above standard GSM services. The CAMEL architecture is based on the Intelligent Network (IN) standards, and uses the CAP (CAMEL Application Part) protocol. The CAP protocol is used for implementing enhancements specific to mobile domains an Intelligent Network (IN) based on the CAMEL architecture.
Optionally, the notification 310 of the called party is carried out utilizing Short Message Service (SMS).
SMS is a service available on most digital mobile phones that permits the sending of short messages between mobile phones, other handheld devices, and even landline phones, as explained hereinabove.
Optionally, the notification 310 of the called party is carried out utilizing call utilizing Unstructured Supplementary Services Data (USSD).
Optionally, the notification 320 of the called party is carried out using a message which is formatted according to a predefined policy. The predefined policy may relate to a variety of aspects, including but not limited to: the language of the message, a predefined message template, etc.
Reference is now made to
In the exemplary scenario, a calling party 10 initiates a prepaid call 400 to a called party 90.
The Mobile Service Center (MSC) 20 checks 410 against the Real Time Billing (RTB) system if the calling party 10 has sufficient credit for the call.
When the calling party 10 runs out of prepaid call credit, the RTB system 30 rejects the call attempt due to the lack of credit 420 left for the calling party 10.
Next, the MSC (or an Intelligent Network's Network Peripheral Service, as known in the art) 20 informs 430 the calling party 10 that the call fails due to the lack of credit, and hangs up the call.
Then, the failed prepaid call capturer 70 captures 440 the details of the failed prepaid call. The details of the failed prepaid call may include, but are not limited to: The Caller Line Identification (CLI) of the calling party, The Mobile Station Integrated Services Digital Network (MSISDN) uniquely identifying the cellular handset used by the calling party, the time of call, pre-selected attributes pertaining to the calling party, pre-selected attributes pertaining to the called party, etc.
The call capturer 70 may be implemented using one or more of possible methods, including but not limited to: using one or more passive probe(s) for monitoring the data traffic between the Mobile Service center (MSC) 20 and the Real Time Billing (RTB) system 30, analyzing data generated by the Real Time Billing (RTB) 30, analyzing Open Scripting Architecture (OSA) events, analyzing Parlay events, and analyzing Intelligent Network Application Part (INAP) events, as described in further detail hereinabove.
Next, the call capturer 70 forwards 450 the captured details of the failed prepaid call to the notifier 60.
Finally, the notifier 60 formats a notification message according to a predefined policy including but not limited to rules relating to the language of the notification, a message template to be used for notification, etc.
The notifier 60 sends 460 the notification to the called party 90, via, for example, an SMSC/USSD gateway 80. The SMSC/USSD gateway 80 sends 470 the failed prepaid call notification to the called party 90.
It is expected that during the life of this patent many relevant devices and systems will be developed and the scope of the terms herein, particularly of the terms “Call”. “Cellular”, “Telephony”, “SMS”, “GSM”, “CAMEL”, “WAP”, “MMS”, “MSC”. “SMSC”, “USSD”, “OSA”, “INAP”, “GSM”, “MSISDN”, “CLI”, and “SS7”, is intended to include all such new technologies apriori.
Additional objects, advantages, and novel features of the present invention will become apparent to one ordinarily skilled in the art upon examination of the following examples, which are not intended to be limiting. Additionally, each of the various embodiments and aspects of the present invention as delineated hereinabove and as claimed in the claims section below finds experimental support in the following examples.
It is appreciated that certain features of the invention, which are, for clarity, described in the context of separate embodiments, may also be provided in combination in a single embodiment. Conversely, various features of the invention, which are, for brevity, described in the context of a single embodiment, may also be provided separately or in any suitable subcombination.
Although the invention has been described in conjunction with specific embodiments thereof, it is evident that many alternatives, modifications and variations will be apparent to those skilled in the art. Accordingly, it is intended to embrace all such alternatives, modifications and variations that fall within the spirit and broad scope of the appended claims.
All publications, patents and patent applications mentioned in this specification are herein incorporated in their entirety by reference into the specification, to the same extent as if each individual publication, patent or patent application was specifically and individually indicated to be incorporated herein by reference.
In addition, citation or identification of any reference in this application shall not be construed as an admission that such reference is available as prior art to the present invention.
