Method for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system
Summary by NHIP
Beacon Method for Voice Delivery
The method detects pauses in automated greetings to determine when to deliver a payload message. It sends a beep after every one-second pause to keep the line alive and prevent carrier disconnection.
Claim Score by NHIP
Abstract
A method to detect the pause in the personal or system message to determine when to leave the payload message, but since there is an issue of the carrier disconnecting the call while waiting to make a determination if the personal or system message has been completed and the recording phase started, the present invention teaches a solution of sending a beep during every second of the pause time, to keep the line alive and the carrier therefore does not hang up and the message is left in full.

Term
Projected expiry 11 March 2033.
- Priority
- Filed
- Granted
- Today
- Projected expiry
19 claims: 3 independent, 16 dependent
- 1A method for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system recorded on non-transitory computer-readable medium and capable of execution by a computer, said method comprising the steps of:providing a voice module running software capable of execution by a computer;calling a phone number of a target receiver by the voice module;establishing a successful call with the target receiver system by the voice module;receiving a first greeting from the target receiver;determining if the target receiver is an answering machine;sending a first beep after a pause of one second by the voice module to keep the call alive;sending the payload message to the target system by the voice module;terminating the call by the voice module.
- 10Broadest claimClaim Score 69, broad(NHIP)A system for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system recorded on non-transitory computer-readable medium and capable of execution by a computer, said system comprising the steps of:initiating a call to a receiver by the voice module;listening to a personal message or a system message;determining when to leave a payload message to the receiver by the voice module to keep the call alive;detecting a pause in the personal message or system;sending a beep during every second of the pause time by the voice module;and delivering the payload message for recording by the receiver by the voice module.
- 19A method for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system recorded on non-transitory computer-readable medium and capable of execution by a computer, said method comprising the steps of:providing a voice module running software capable of execution by a computer;calling a phone number of a target receiver by the voice module;establishing a successful call with the target receiver system by the voice module;receiving a first greeting from the target receiver;determining if the target receiver is an answering machine by the voice module;sending a first beep after a pause of one second by the voice module to keep the call alive;sending a second beep after a pause of one second by the voice module;sending a third beep after a pause of one second by the voice module;sending the payload message to the target system by the voice module;and terminating the call by the voice module.
Independent claims3
25 paragraphs in 8 sections, as filed
CROSS REFERENCE TO RELATED APPLICATIONS
This application claims priority from U.S. Patent Application Ser. No. 61/609,982, entitled “Method For Providing a Beacon to Ensure Delivery of Automated Messages Over a Telephone or Voice Messaging System”, filed on 13 Mar. 2012. The benefit under 35 USC §119(e) of the United States provisional application is hereby claimed, and the aforementioned application is hereby incorporated herein by reference.
FEDERALLY SPONSORED RESEARCH
Not Applicable
SEQUENCE LISTING OR PROGRAM
Not Applicable
TECHNICAL FIELD OF THE INVENTION
The present invention relates generally to telephone and voice mail/messaging systems. More specifically, the present invention relates to leaving an automated message or payload by a sending system over a telephone or voice mail system so the recorded message or payload is not cut off or failed to be recorded.
BACKGROUND OF THE INVENTION
Telephone call centers are typically used to distribute phone calls to a large number of people nationally, regionally, and/or locally. The number of phone lines and amount of machine systems can be very large and expensive. The use of pre-recorded messages has become more popular in recent years. Using a pre-recorded message from a sending system, an auto dialing phone calls a list of phone numbers for potential recipients and plays the message. While this system removes the necessity of using a physical person, the sending party still must purchase the expensive multiple phone lines in order to call multiple recipients.
When a system sends out an automated message and it is answered over a phone or voice messaging system, the sending system then waits to detect a pause or silence for which is at least as much as a pre-programmed number of seconds, for example, three seconds of pause. On detecting this it begins to leave its payload message. The pause between the personal and system greeting could be more than the three seconds or any pre-programmed amount. Sometimes as the payload message is being spoken/delivered the recorded personal greeting of the telephone line or voice messaging system starts playing and the recording of the message/payload is either cut off or not recorded at all as a results of being delivered over or during the personal greeting of the telephone line or messaging system.
Conversely, the solution of merely extending, the pause from connection to delivery of the message/payload cannot simply be extended in duration. If the pause between the personal and system greeting is long then the telephone carrier, detecting no sound hangs up the call. Most carriers have a three second silence allowance, before the call is disconnected. In this case, the payload message is not recorded because the line got disconnected. This can happen even when a human answers the phone and there is a long silence, but it is most likely to happen with answering systems. Additionally, if the call is not disconnected, there will be a long pause before the message is delivered or recorded for playback, which often times results in the telephone line owner simply deleting the message before playback or immediately upon the start of payback after the long period of silence, in addition to the delivery of such message with an extended period of silence being viewed as unprofessional or other negative connotations being associated with the message.
Therefore, what is needed is a method to detect the pause in the message to leave the payload, usurping an issue of the carrier disconnecting the call while a sending system is waiting to deliver the message/payload to keep the line alive so the carrier does not hang up and the message is left in full.
SUMMARY OF THE INVENTION
When automated telephone messages are sent and these messages are answered by an answering machine on a telephone system, voice mail or any other voice messaging system, many users experience receiving incomplete or no message at all. Commonly, a message is sent by an automated service to a receiver, with an associated phone number. This could be a cell phone, a landline, a user name, box number, or any other means of identification in a voice mail system. The call is picked up by an answering machine or voice mail system. The greeting has two parts. The personal greeting and system greeting.
The receiver may respond with a voice output or recording such as “I am unable to answer the phone please leave a message and I will get back to you” also referred to as a personal message. Next there is a pause. Then a system message responds with a voice output or recording such as “Please leave a message or Press 0 to reach an operator or press * to hang-up or leave a message after the tone”, also referred to as a system message.
The system that has placed this call starts to leave its message for the receiver also known as the payload message which can be something as simple as “Hi this message is to inform you that the Printers in building 7 are down arrange for to send the technician to fix it”. It has been found that on several occasions the message left is truncated or if the original message was short, it appears as if no message has been left after the recording beep.
The present invention teaches a method to detect the pause in the personal or system message to determine when to leave the payload message, but since there is an issue of the carrier disconnecting the call while waiting to make a determination if the personal or system message has been completed and the recording phase started, the present invention teaches a solution of sending a beep during every second of the pause time, to keep the line alive and the carrier therefore does not hang up and the message is left in full.
BRIEF DESCRIPTION OF THE DRAWINGS
The accompanying drawings, which are incorporated herein an form a part of the specification, illustrate the present invention and, together with the description, further serve to explain the principles of the invention and to enable a person skilled in the pertinent art to make and use the invention.
<figref idref="DRAWINGS">FIG. 1</figref> is a flow chart illustrating the known process of automatically calling a receiver to deliver a recorded voice message or payload; and
<figref idref="DRAWINGS">FIG. 2</figref> is a flow chart illustrating the method of the present invention for delivery of the recorded message or payload to ensure the message or payload is recorded in full by the receiver using the three beep beacon solution.
DETAILED DESCRIPTION OF THE INVENTION
In the following detailed description of the invention of exemplary embodiments of the invention, reference is made to the accompanying drawings (where like numbers represent like elements), which form a part hereof, and in which is shown by way of illustration specific exemplary embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, but other embodiments may be utilized and logical, mechanical, electrical, and other changes may be made without departing from the scope of the present invention. The following detailed description is, therefore, not to be taken in a limiting sense, and the scope of the present invention is defined only by the appended claims.
In the following description, numerous specific details are set forth to provide a thorough understanding of the invention. However, it is understood that the invention may be practiced without these specific details. In other instances, well-known structures and techniques known to one of ordinary skill in the art have not been shown in detail in order not to obscure the invention. Referring to the figures, it is possible to see the various major elements constituting the apparatus of the present invention.
Now referring to the Figures, the embodiment of the method for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system is shown. As shown in <figref idref="DRAWINGS">FIG. 1</figref>, the flow chart describes the workflow without using the three beep beacon solution. In this embodiment, the computerized system comprising hardware and software for executing the method, referred to as the “voice module” <b>101</b>, uses the hardware and software to initiate and establish a call <b>103</b> to the phone number of a target receiver machine <b>102</b>. After a successful call is established <b>103</b> the target system machine <b>102</b> starts sending the User Greetings <b>104</b>. The voice module <b>101</b> determines if the target receiver machine <b>102</b> is an answering machine. The detection <b>105</b> of whether the target system machine <b>102</b> is an answering machine is made by making calls to the API of the underlying systems, like CT_ADE, and Dialogic Voice cards, or Asterisk libraries (in the case of VoIP). The voice module <b>101</b> tries to wait for the end of the greeting <b>110</b>. The voice module <b>101</b> sends the payload <b>108</b> right away without any delay <b>106</b>. At this time the user greeting <b>104</b> would start playing and the user greeting <b>104</b> could still be playing when the payload message <b>108</b> is sent <b>114</b>. When this happens, the payload message <b>108</b> does not get recorded fully and only a partial message is actually recorded <b>115</b>. Hence the receiver does not receive the payload message <b>108</b> at all or receives only a part <b>116</b> of the payload message <b>108</b> since the payload message <b>108</b>, initiated without delay <b>106</b> has not been recorded by the target machine <b>102</b> until the target machine <b>102</b> finishes the user greeting <b>104</b> and/or system greeting <b>107</b> and finishes sending the user greeting and finishes sending the user greeting <b>113</b>. Depending on the length of the user greeting <b>104</b> and/or the system greeting <b>107</b>, the payload message <b>108</b> is either recorded partially or not at all upon completion of the message payload delivery <b>111</b> and the voice module <b>101</b> ending the call <b>112</b>.
Now referring to <figref idref="DRAWINGS">FIG. 2</figref>, the three beep solution of the present invention is taught. Here, the voice module <b>101</b> calls a phone number of a target receiver <b>102</b>. After a successful call is established <b>201</b> the target receiver system <b>102</b> starts sending the User Greetings <b>202</b>. The voice module <b>101</b> determines if this is answering machine. The detection <b>105</b> of whether it is an answering machine is made by making calls to the API of the underlying systems, like CT_ADE, and Dialogic Voice cards, or Asterisk libraries (in the case of VoIP). After a pause of 1 second <b>203</b> the voice module <b>101</b> sends a first beep <b>204</b>. The voice module <b>101</b> next sends a second beep <b>205</b> and a third beep <b>206</b> for a total of three sent beeps with a one second pauses <b>203</b> in-between each beep. This happens even while the User Greetings <b>104</b> followed by the System greetings <b>107</b> are playing <b>211</b>. After the three beeps are completed, the payload message <b>108</b> is started to be sent <b>207</b> and is delivered to the target system <b>102</b>, this is recorded <b>210</b> by the target machine <b>102</b>. After delivering the payload message <b>208</b> the voice module <b>101</b> ends the call <b>209</b>. After the machine detection <b>105</b>, which also consumes all/most-of-the first greetings run time, the method then gives 3 more seconds to the other party to finish up its current and following greeting, and after that the method playbacks the message payload <b>212</b>.
Through experimentation and trial and error, the inventor(s) have found that if they merely waited for three seconds, without the beeps, before sending the payload, the call gets disconnected by the carrier due to the silence and the payload is not recorded. Therefore, the inventor(s) came up with the solution of sending beeps to keep the line alive. With this the chance of successfully delivering the payload is substantially increased.
After the call is established, the voice module <b>101</b> immediately goes into the machine or human voice detection procedure <b>105</b> that does the detection of 1st greeting, and then followed by the three beep process. In the three beep process, the voice module <b>101</b> repeats “wait-for-1 second and beep” for three times. Then the voice module <b>101</b> plays the beep anyway whether we get silence or not. The voice module <b>101</b> does it three times. The voice module <b>101</b> will wait at most up to a total of three seconds with beeps in between. And after these three seconds, the voice module <b>101</b> starts the greetings and payload message anyway.
This enables the voice module <b>101</b> to at least give a total of three seconds to the other side to complete its greetings, and in the mean-time, while waiting, the voice module <b>101</b> also sends its beeps so that if the other party or carrier is also detecting silence, it can be assured that the voice module <b>101</b> is still there. Also if the other side is the human, it will let him know that an automated message delivery system is yet to deliver its payload message.
It the other side happens to start its second greeting after three seconds, say at a fourth second, then the voice module <b>101</b> will start our side of the message playback as per the pre-defined procedure, and in that way the voice module <b>101</b> will again get the issue of incomplete message recording. However its probability is quite rare given the current state of phone messaging systems.
Thus, it is appreciated that the optimum dimensional relationships for the parts of the invention, to include variation in size, materials, shape, form, function, and manner of operation, assembly and use, are deemed readily apparent and obvious to one of ordinary skill in the art, and all equivalent relationships to those illustrated in the drawings and described in the above description are intended to be encompassed by the present invention.
Furthermore, other areas of art may benefit from this method and adjustments to the design are anticipated. Thus, the scope of the invention should be determined by the appended claims and their legal equivalents, rather than by the examples given.
Contents8
4 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US10044710B2 | Cited by | United States of America | Applicant |
| US2010183128A1 | Cites | United States of America | Search report |
| US4069397A | Cites | United States of America | Search report |
| US4596901A | Cites | United States of America | Search report |
| US5430792A | Cites | United States of America | Search report |
| US5873032A | Cites | United States of America | Search report |
| US5909647A | Cites | United States of America | Search report |
| US6226360B1 | Cites | United States of America | Search report |
| US6324262B1 | Cites | United States of America | Search report |
| US20100183128A1 | Cites | United States of America | Search report |
4 members in 1 office
Priority claims6
| Document | Office | Kind | Date |
|---|---|---|---|
| 201261609982 | United States of America | P | |
| 201261609982 | United States of America | P | |
| 201313792802 | United States of America | A | |
| 61609982 | – | – | – |
| US201261609982P | – | – | – |
| US201313792802 | – | – | – |
Members4
| Document | Office | Kind | |
|---|---|---|---|
| US2013243170A1 | United States of America | A1 | |
| US2015100628A1 | United States of America | A1 | |
| US9014350B2This record | United States of America | B2 | |
| US9674123B2 | United States of America | B2 |
37 transactions on the USPTO file
Allowed after 1 non-final rejection.
- Non-final rejections
- 1
- Final rejections
- 0
- RCEs
- 0
- Appeals
- 0
Over time
Point at a mark for the transactionTransactions
| Event | Code | |
|---|---|---|
| Expire PatentEXP. | EXP. | |
| Maintenance Fee Reminder MailedREM. | REM. | |
| Payment of Maintenance Fee, 4th Yr, Small EntityM2551 | M2551 | |
| Recordation of Patent Grant MailedPGM/ | PGM/ | |
| Patent Issue Date Used in PTA CalculationAllowedPTAC | PTAC | |
| Issue Notification MailedAllowedWPIR | WPIR | |
| Dispatch to FDCD1935 | D1935 | |
| Application Is Considered Ready for IssuePILS | PILS | |
| Issue Fee Payment VerifiedN084 | N084 | |
| Issue Fee Payment ReceivedIFEE | IFEE | |
| Mail Notice of AllowanceAllowedMN/=. | MN/=. | |
| Notice of Allowance Data Verification CompletedAllowedN/=. | N/=. | |
| Reasons for AllowanceEX.R | EX.R | |
| Examiner's Amendment CommunicationEX.A | EX.A | |
| Interview Summary - Examiner Initiated - TelephonicEXET | EXET | |
| Interview Summary - Examiner InitiatedEXIE | EXIE | |
| Date Forwarded to ExaminerFWDX | FWDX | |
| New or Additional Drawing FiledC614 | C614 | |
| Response after Non-Final ActionA... | A... | |
| Request for Extension of Time - GrantedXT/G | XT/G | |
| Applicant Has Filed a Verified Statement of Micro Entity Status in Compliance with 37 CFR 1.29MICR | MICR | |
| Mail Non-Final RejectionNon-final rejectionMCTNF | MCTNF | |
| Non-Final RejectionNon-final rejectionCTNF | CTNF | |
| PG-Pub Issue NotificationPG-ISSUE | PG-ISSUE | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Case Docketed to Examiner in GAUDOCK | DOCK | |
| Application Dispatched from OIPEOIPE | OIPE | |
| Application Is Now CompleteCOMP | COMP | |
| Change in Power of Attorney (May Include Associate POA)PA.. | PA.. | |
| FITF set to NO - revise initial settingFTFI | FTFI | |
| Sent to Classification ContractorPGPC | PGPC | |
| Filing ReceiptFLRCPT.O | FLRCPT.O | |
| Applicant Has Filed a Verified Statement of Small Entity Status in Compliance with 37 CFR 1.27SMAL | SMAL | |
| Cleared by OIPE CSRL194 | L194 | |
| Applicants have given acceptable permission for participating foreignAPPERMS | APPERMS | |
| IFW Scan & PACR Auto Security ReviewSCAN | SCAN | |
| Initial Exam Team nnIEXX | IEXX |
7 legal events, as the office reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | |
|---|---|---|
| Lapsed due to failure to pay maintenance feeLapsedFP | FP | |
| Lapse for failure to pay maintenance feesLapsedPATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITYLAPS | LAPS | |
| Information on status: patent discontinuationPATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362STCH | STCH | |
| Fee payment procedureMAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITYFEPP | FEPP | |
| Maintenance fee paymentMAFP | MAFP | |
| Information on status: patent grantGrantedPATENTED CASESTCF | STCF | |
| AssignmentAS | AS |
Numbers
- Publication
- 09014350
- Publication, DOCDB
- 9014350
- Publication, EPODOC
- US9014350
- Application
- 13792802
- Application, DOCDB
- 201313792802
- Application, EPODOC
- US201313792802
Titles
- English
- Method for providing a beacon to ensure delivery of automated messages over a telephone or voice messaging system
Patent term adjustment
- Applicant delay
- −92 days
- Net adjustment
- 0 days
Classification
- CPC, 6
- H04M3/5158
- H04M3/53333
- H04M3/53366
- H04M7/129
- H04M2203/2011
- H04M2203/2027
- IPC, 4
- H04M1 64
- H04M3 51
- H04M3 533
- H04M7 12
- USPC, 2
- 379088180
- 379088220