I 1111111111111111 11111 111111111111111 111111111111111 IIIII IIIIII IIII IIII IIII
`US009185227B2
`
`c12) United States Patent
`Mumick et al.
`
`(IO) Patent No.:
`(45) Date of Patent:
`
`US 9,185,227 B2
`Nov. 10, 2015
`
`(54) SENDER DRIVEN CALL COMPLETION
`SYSTEM
`
`(71) Applicant:
`
`Kirusa, Inc., New Providence, NJ (US)
`
`(72)
`
`Inventors:
`
`Inderpal Singh Mumick, Berkely
`Heights, NJ (US); Surinder Singh
`Anand, Highland Park, NJ (US); Raja
`N. Moorthy, Fairless Hills, PA (US)
`
`(73) Assignee:
`
`Kirusa, Inc., New Province, NJ (US)
`
`( *) Notice:
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by O days.
`
`(21) Appl. No.: 14/105,158
`
`(22) Filed:
`
`Dec. 12, 2013
`
`(65)
`
`Prior Publication Data
`
`US 2014/0169539 Al
`
`Jun. 19, 2014
`
`Related U.S. Application Data
`
`(60)
`
`Provisional application No. 61/737,274, filed on Dec.
`14, 2012.
`
`(51)
`
`(52)
`
`(58)
`
`(2006.01)
`(2006.01)
`(2009.01)
`
`Int. Cl.
`H04Ml/64
`H04M3/533
`H04W 4/00
`U.S. Cl.
`CPC ..................................... H04M 3/533 (2013.01)
`Field of Classification Search
`CPC .......... H04M 1/274575; H04W 28/04; H04W
`76/02; H04W 76/06; H04W 84/042
`USPC ..................... 379/88.01-88.23; 455/465, 466
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`............. 455/456
`379/201.01
`370/352
`
`5,627,875 A *
`5/1997 Kapsales ....................... 455/567
`6,064,874 A
`5/2000 Cox et al.
`6,577,881 Bl*
`6/2003 Ehara ............................ 455/563
`7,020,269 Bl*
`3/2006 Park et al.
`379/355.01
`8,880,120 Bl* 11/2014 Lavian et al.
`.............. 455/556.1
`2002/0101970 Al*
`8/2002 Contractor
`379/209.01
`2003/0112945 Al
`6/2003 Brown eta!.
`2003/0119520 Al*
`6/2003 Yoshioka et al.
`2004/0086100 Al *
`5/2004 Moore et al.
`2006/0013195 Al*
`1/2006 Son et al.
`2006/0104429 Al
`5/2006 Wouterse et al.
`2006/0242588 Al* 10/2006 Ybarra et al.
`715/748
`2007/0047695 Al*
`379/67.1
`3/2007 Tal et al.
`2009/0143085 Al *
`6/2009 Anderl et al. ................. 455/466
`2010/0296644 Al
`11/2010 Pisani et al.
`* cited by examiner
`Primary Examiner - Solomon Bezuayehu
`(74) Attorney, Agent, or Firm -Ash Tankha; Lipton,
`Weinberger & Husick
`ABSTRACT
`(57)
`A method and a system for completing an incomplete call
`made by a calling party to a called party, provide a call
`completion application on a calling party device. The call
`completion application detects an incomplete call, which is a
`call that is not connected to a called party device or a short
`duration call that does not enable an intended communication
`to occur between the calling party and the called party. The
`call completion application determines one or more call
`completion actions, for example, setting a reminder, trans(cid:173)
`mitting media data, etc., to be performed to complete the
`incomplete call, for example, based on user selections, a
`duration of the incomplete call, user configuration of the call
`completion application on the calling party device, etc. The
`call completion application triggers execution of the deter(cid:173)
`mined call completion actions based on one or more action
`execution criteria for completing the incomplete call.
`23 Claims, 8 Drawing Sheets
`
`PROVIDE A CALL COMPLETION APPLICATION ON A CALLING PARTY
`DEVICE
`
`DETECT AN INCOMPLETE CALL MADE BY THE CALLING PARTY TO THE
`CALLED PARTY
`
`101
`
`102
`
`PROVIDE A CAIL COMPLETION APPLICATION ON A CALLING PARTY
`DEVICE
`
`DETECT A CALL ATTEMPT UNANSWERED BY THE CALLED PARTY
`
`GENERATE A REQUEST DEFINING CALL COMPLETION ACTIO:KS FOR
`COMPLETING THE DETECTED UNANSWERED CALL ATTEMPT
`
`101
`
`105a
`
`106a
`
`DETERMINE ONE OR MORE OF MULTIPLE CALL COMPLETION ACTIONS TO BE 103
`PERFORMED TO COMPLETE THE DETECTED INCOMPLETE CALL
`
`RENDER THE GENERATED REQUEST ON A GRAPHICAL USER INTERFACE (GUD 107
`OF THE CALLING PARTY DEVICE
`
`TRIGGER EXECUTION OF THE DETERMINED CALL COMPLETION ACTIONS
`BASED ON ONE OR MORE ACTION EXECUTION CRITERIA FOR COMPLETING
`THE DETECTED INCOMPLETE CALL
`
`104
`
`RECEIVE A RESPONSE TO THE GENERATED REQUEST FROM THE CALLING
`PARTY VIA THE GUI
`
`108
`
`TRIGGER EXECUTION OF ONE OR MORE CALL COMPLETION ACTIONS
`DETERMINED FROM THE RECEIVED RESPONSE OF THE CALLING PARTY BASED
`ON ONE OR MORE ACTION EXECUTION CRITERIA FOR COMPLETING THE
`DETECTED UNANSWERED CALL ATTEMPT
`
`109
`
`Petitioner Exhibit 1001, Page 1 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 1 of 8
`
`US 9,185,227 B2
`
`PROVIDE A CALL COMPLETION APPLICATION ON A CALLING PARTY
`DEVICE
`
`l
`
`DETECT AN INCOMPLETE CALL MADE BY THE CALLING PARTY TO THE
`CALLED PARTY
`
`DETERMINE ONE OR MORE OF MULTIPLE CALL COMPLETION ACTIONS TO BE
`PERFORMED TO COMPLETE THE DETECTED INCOMPLETE CALL
`
`l
`
`l
`
`TRIGGER EXECUTION OF THE DETERMINED CALL COMPLETION ACTIONS
`BASED ON ONE OR MORE ACTION EXECUTION CRITERIA FOR COMPLETING
`THE DETECTED INCOMPLETE CALL
`
`101
`.,,/
`
`102
`.,,/
`
`103
`.,,/
`
`104
`_,/
`
`FIG. lA
`
`Petitioner Exhibit 1001, Page 2 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 2 of 8
`
`US 9,185,227 B2
`
`PROVIDE A CALL COMPLETION APPLICATION ON A CALLING PARTY
`DEVICE
`
`DETECT A CALL ATTEMPT UNANSWERED BY TIIE CALLED PARTY
`
`l
`
`l
`
`GENERATE A REQUEST DEFINING CALL COMPLETION ACTIONS FOR
`COMPLETI:--JG THE DETECTED UNANSWERED CALL ATTEMPT
`
`1
`
`RENDER THE GENERATED REQUEST ON A GRAPHICAL USER INTERFACE (GUI)
`OF THE CALLING PARTY DEVICE
`
`i
`
`RECEIVE A RESPONSE TO THE GENERATED REQUEST FROM THE CALLING
`PARTY VIA THE GUI
`
`101
`_,/
`
`105a
`_,/
`
`106a v
`
`107
`_,/
`
`108
`_,,/
`
`i
`
`TRIGGER EXECUTION OF ONE OR MORE CALL COMPLETION ACTIONS
`109
`DETERMINED FROM THE RECEIVED RESPONSE OF THE CALLING PARTY BASED
`../
`ON ONE OR MORE ACTION EXECUTION CRITERIA FOR COMPLETING TIIE
`DETECTED UNANSWERED CALL ATTEMPT
`
`FIG.1B
`
`Petitioner Exhibit 1001, Page 3 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 3 of 8
`
`US 9,185,227 B2
`
`PROVIDE A CALL COMPLETIOK APPLICATION ON A CALLING PARTY
`DEVICE
`
`DETECT A SHORT DURATION CALL MADE BY THE CALLING PARTY TO THE
`CALLED PARTY
`
`l
`
`l
`
`GENERATE A REQUEST DEFINING OPTIONS FOR PERFORMING CALL
`COMPLETION ACTIONS ASSOCIATED WITH THE DETECTED SHORT DURATION
`CALL
`
`l
`
`RENDER THE GENERATED REQUEST 0>1 A GRAPHICAL USER INTERFACE (GUI)
`OF THE CALLING PARTY DEVICE
`
`t
`
`RECEIVE A RESPONSE TO THE GENERATED REQUEST FROM THE CALLING
`PARTY VIA THE GUI
`
`101
`l../
`
`105b
`l../
`
`106b
`l--/
`
`107
`l../
`
`108
`_/
`
`l
`
`TRIGGER EXECUTION OP ONE OR MORE CALL COMPLETION ACTIONS
`109
`DETERMINED FROM THE RECEIVED RESPONSE OF THE CALLING PARTY BASED
`l--/
`ON ONE OR MORE ACTION EXECUTION CRITERIA FOR COMPLETING THE
`DETECTED SHORT DURATION CALL
`
`FIG. lC
`
`Petitioner Exhibit 1001, Page 4 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 4 of 8
`
`US 9,185,227 B2
`
`VOICESMS
`EXCHANGE
`SERVER
`
`210
`
`~200
`
`VOICESMS
`SERVER
`
`VOICESMS
`
`.~i
`-------------{. NETWORK
`\..._
`- - - - - - - - - -< (
`
`NETWORK
`COMPONENT
`
`CALLING PARTY DEVICE
`
`201a
`)
`
`GRAPHICAL USER I)JTERFACE
`
`CALL COMPLETION APPLICATION
`202
`a
`
`CALL DETECTION
`MODULE
`
`.---A-C-.T-IO-K-,----, 20Zb
`DDTERMI)JATION
`MODULE
`
`~-RE-Q-UE-ST-- 202c
`GENERATION
`MODULE
`
`202
`
`202d
`)
`
`REQUEST
`RENDERING
`MODUT,E
`
`202e
`)
`
`RESPONSE
`ACQUISITION
`MODULE
`
`202f
`.--A-C-'T_I_O_N_E_XE_C-'U_T_I_O_N_M_O_D_U_L_E_~
`
`FIG.2
`
`COMPONENT
`
`206
`
`CALLED PARTY DEVICE
`,--------------; 206a
`: MI:SSAGIKG L__)
`._ ______________ .
`I
`I
`: APPLICATION ,
`
`VOICE
`MESSAGING
`AND CALL
`COMPLETlON
`SERVER
`
`Petitioner Exhibit 1001, Page 5 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 5 of 8
`
`US 9,185,227 B2
`
`DETECTION OF AN UNANSWERED CALL ATTEMPT ON A CALLING PARTY
`DEVICE WITH AN ANDROID OPERA TING SYSTEM COMPRISES THE
`FOLLOWING STEPS:
`
`TM
`
`A. DETECT THE CHANGE OF STATE OF THE ANDROID CALLING PARTY
`DEVICE BETWEEN THE FOLLOWING: IDLE, OFF _HOOK, AND RINGING
`USING onCallStateChanged() TO REQUEST THE ANDROID™ OPERATING
`SYSTEM TO ISSUE A CALLBACK TO THE CALL COMPLETION
`APPLICATION ON THE ANDROID CALLING PARTY DEVICE.
`
`B. THE FOLLOWING CHANGE OF CALL STATES RELATE TO INCOMING
`CALLS (MISSED OR ANSWERED) THAT CAN BE IGNORED BY THE CALL
`COMPLETION APPLICATION:
`
`I. IDLE TO RINGING TO IDLE: AN INCOMING CALL THAT
`WAS NOT ANSWERED.
`
`II. IDLE TO RINGING TO OFF _HOOK TO IDLE: AN
`INCOMING CALL THAT WAS ANSWERED AND THEN
`ENDED.
`
`III. IDLE TO RINGING TO OFF _HOOK TO RINGING TO
`OFF _HOOK TO IDLE: AN INCOMING CALL THAT WAS
`ANSWERED FOLLOWED BY ANOTHER INCOMING CALL
`(WHICH MAY OR MAY NOT HA VE BEEN ANSWERED), AND
`FINALLY THE CALL ENDS.
`
`C. THE FOLLOWING CHANGE OF CALL STATES REPRESENTS AN
`OUTGOING CALL ATTEMPT THAT MAY OR MAY NOT HA VE BEEN
`ANSWERED.
`
`I. IDLE TO OFF _HOOK TO IDLE: AN OUTGOING CALL
`ATTEMPT.
`
`II. TO DIFFERENTIATE BETWEEN CALLS THAT ARE
`ANSWERED AND UNANSWERED, FETCH THE LAST ENTRY
`FOR OUTGOING CALLS FROM THE CALL LOG USING THE
`CallLog.getLastOutgoingCall. CHECK THE VALUE OF THE
`"DURATION" FIELD IN THE CALL LOG. IF THE VALUE OF
`DURATION IS 0, IT INDICATES THAT THE CALL WAS NOT
`ANSWERED.
`
`FIG.3
`
`Petitioner Exhibit 1001, Page 6 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 6 of 8
`
`US 9,185,227 B2
`
`DETECTION OF AN UNANSWERED CALL ATTEMPT ON A CALLING PARTY
`DEVICE WITH AN ios® MOBILE OPERATING SYSTEM COMPRISES THE
`FOLLOWING STEPS:
`
`A. REGISTER THE CALL COMPLETION APPLICATION WITH THE ios USING
`callEventHandler() TO BE NOTIFIED ABOUT ANY CHANGE IN THE CALL
`STATE.
`
`B. DETECT THE CHANGE OF STATE OF THE ios CALLING PARTY DEVICE
`BETWEEN THE FOLLOWING: CTCallStateDisconnected,
`CTCallStateDialing, CTCallStateConnected, AND CTCallStatelncoming.
`
`C. THE FOLLOWING CHANGE OF CALL STATES RELATE TO INCOMING
`CALLS (MISSED OR ANSWERED) THAT CAN BE IGNORED BY THE CALL
`COMPLETION APPLICATION:
`
`I. CTCallStateDisconnected TO CTCallStatelncoming TO
`CTCallStateDisconnected: AN INCOMING CALL THAT
`WAS NOT ANSWERED.
`
`II. CTCallStateDisconnected TO CTCallStatelncoming TO
`CTCallStateConnected TO CTCallStateDisconnected: AN
`INCOMING CALL THAT WAS ANSWERED AND THEN
`ENDED.
`
`III. CTCallStateDisconnected TO CTCallStatelncoming
`TO CTCallsStateConnected TO CTCallStatelncoming TO
`CTCallStateConnected TO CTCallStateDisconnected. AN
`INCOMING CALL THAT WAS ANSWERED, FOLLOWED BY
`ANOTHER INCOMING CALL (WHICH MAY OR MAY NOT
`HAVE BEEN ANSWERED), AND FINALLY THE CALL ENDS.
`
`D. THE FOLLOWING CHANGE OF CALL STATES REPRESENTS AN
`OUTGOING CALL ATTEMPT THAT HAS BEEN ANSWERED.
`
`I. CTCallStateDisconnected TO CTCallStateDialing TO
`CTCallStateConnected TO CTCallStateDisconnected: AN
`OUTGOING CALL THAT WAS ANSWERED.
`
`E. THE FOLLOWING CHANGE OF CALL STATES REPRESENTS AN
`OUTGOING CALL ATTEMPT THAT HAS NOT BEEN ANSWERED.
`
`I. CTCallStateDisconnected TO CTCallStateDialing TO
`CTCallStateDisconnected: AN OUTGOING CALL ATTEMPT
`THAT WAS NOT ANSWERED.
`
`FIG.4
`
`Petitioner Exhibit 1001, Page 7 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 7 of 8
`
`US 9,185,227 B2
`
`LIST OF CALL COMPLETION ACTIONS AVAILABLE TO THE
`
`CALLING PARTY:
`
`1. SEND A TEXT MESSAGE
`
`2. SEND A VOICE MESSAGE
`
`3. SEND A VIDEO MESSAGE
`
`4. SEND A PRE-RECORDED MESSAGE
`
`5. SEND A MISSED CALL ALERT
`
`6. BE ALERTED WHEN THE CALLED PARTY IS AVAILABLE
`
`7. ADD TO REMINDER
`
`8. ADD TO CALENDAR
`
`9. SEND A DIRECT MESSAGE ON TWITTER
`
`10. POST TO THE CALLED PARTY'S F ACEBOOK PAGE
`
`11. SEND A PRIVATE CHAT MESSAGE TO THE CALLED
`
`PARTY'S FACEBOOK IDENTITY
`
`FIG.5
`
`Petitioner Exhibit 1001, Page 8 of 23
`
`

`

`U.S. Patent
`
`Nov. 10, 2015
`
`Sheet 8 of 8
`
`US 9,185,227 B2
`
`606 v
`
`607
`_)
`
`608
`lJ
`
`609
`l)
`
`600
`
`605
`_)
`-
`
`l)°l
`
`DISPLAY
`UNIT
`
`PROCESSOR
`
`INPUT
`DEVICES
`
`-
`
`602
`_J
`
`MEMORY
`UNIT
`
`603 -
`_J
`
`604
`_J
`
`-
`
`-
`
`I/0
`CONTROLLER
`
`NETWORK
`INTERFACE
`
`FIXED
`MEDIA
`DRIVE
`
`REMOVABLE
`MEDIA
`DRIVE
`
`OUTPUT
`DEVICES
`
`FIG.6
`
`Petitioner Exhibit 1001, Page 9 of 23
`
`

`

`US 9,185,227 B2
`
`1
`SENDER DRIVEN CALL COMPLETION
`SYSTEM
`
`CROSS REFERENCE TO RELATED
`APPLICATIONS
`
`This application claims priority to and the benefit of pro(cid:173)
`visional patent application No. 61/737,274 titled "Sender
`Driven Call Completion System", filed in the United States
`Patent and Trademark Office on Dec. 14, 2012. The specifi(cid:173)
`cation of the above referenced patent application is incorpo(cid:173)
`rated herein by reference in its entirety.
`
`BACKGROUND
`
`Call completion systems such as voicemail are widely
`prevalent in Europe, the United States of America (USA),
`etc., both within a network and out of the network and have
`been used for a number of applications, for example, for
`sending voice messages and voice related information in the
`case of incomplete calls. A conventional call completion sys(cid:173)
`tem typically relies on a preconfigured establishment of a
`feature in the network of a called party to receive a message
`on behalf of the called party who is a recipient of a call.
`Consider an example where a calling party originates a voice
`call, or attempts to place a voice call to a called party. In a
`conventional call completion system, the phone number and
`the network of the called party is configured such that if a
`calling party attempts to establish a voice call with the called
`party and the called party does not accept the voice call, the
`calling party is offered an option to record and send a voice
`message, or alternatively, a short message service (SMS)
`message, etc., automatically to the called party indicating that
`the called party missed a call. However, this call completion
`service can operate only when the network is set up on behalf
`of the called party. The network needs to configure the call
`completion service on behalf of the called party to enable the
`calling party to send a message to the called party. The con(cid:173)
`figuration of the call completion service is typically triggered
`manually by the called party or performed automatically by
`the network for the called party. That is, the configuration of
`the call completion service involves a configuration of a set of
`parameters corresponding to a contact number of the called
`party before the calling party is offered an option to send a
`message.
`Such conventional call completion solutions, for example,
`voicemail, are often insufficient since the calling party does
`not get to decide on whether a voice message can be sent to the
`called party, that is, the calling party is dependent on the
`called party having enabled a voice message service for
`receipt of voice messages. Furthermore, all message transac(cid:173)
`tions need to be mandatorily performed via the network.
`Therefore, if the network fails to configure a message service
`for the called party, the called party is unable to receive a
`message from the calling party.
`Hence, there is a long felt but unresolved need for a method
`and a system that complete an incomplete call made by a
`calling party to a called party by executing a call completion
`action, for example, setting up a reminder, transmitting voice
`messages, text messages, missed call alerts, notifications of a
`call attempt, etc., to the called party, etc., independent of a
`preconfigured call completion service on the called party's
`network or a called party device, and that provide a sender,
`that is, the calling party the option to drive or trigger execution
`of the call completion action.
`
`SUMMARY OF THE INVENTION
`
`This summary is provided to introduce a selection of con(cid:173)
`cepts in a simplified form that are further disclosed in the
`
`5
`
`2
`detailed description of the invention. This summary is not
`intended to identify key or essential inventive concepts of the
`claimed subject matter, nor is it intended for determining the
`scope of the claimed subject matter.
`The method and the system disclosed herein address the
`above stated need for completing an incomplete call made by
`a calling party to a called party by executing a call completion
`action, for example, one that leads to setting up a reminder, or
`one that leads to transmitting a voice message, a text message,
`10 a missed call alert, a notification of a call attempt, other
`calling party driven messages, etc., to the called party, etc.,
`independent of a preconfigured call completion service on the
`called party's network or a called party device, and for pro-
`15 viding a sender, that is, the calling party the option to drive or
`trigger execution of the call completion action. As used
`herein, the term "sender" refers to a user, for example, a
`calling party who initiates a call to a recipient or a called party
`and wants to communicate with the recipient. Also, as used
`20 herein, the phrase "called party device" refers to a communi(cid:173)
`cation device of a called party who is a recipient or an
`intended recipient of a call made by the calling party. The
`method and the system disclosed herein therefore allow the
`calling party to perform an action, for example, communicate
`25 with the called party in lieu of the initial incomplete voice call
`attempt made by the calling party. The method and the system
`disclosed herein enable a seamless execution of an action by
`the calling party, for example, an action that leads to a seam(cid:173)
`less transmission of a message from the calling party to the
`30 called party when the call is not completed, where the calling
`party is prompted automatically to perform an action, for
`example, transmit a message, when the call is not completed.
`Furthermore, the method and the system disclosed herein
`35 implement a call completion service without any dependence
`on the underlying network to support call completion for the
`called party, with the calling party equipped with sufficient
`information and capability to trigger execution of the action.
`The method and the system disclosed herein, for example,
`40 enable transmission of a voice message by a calling party to a
`called party when a network component or a called party
`device is not configured to offer a call completion option to
`the calling party to leave a voice message. The method and the
`system disclosed herein provide a call completion application
`45 executable by at least one processor on a calling party device.
`As used herein, the phrase "calling party device" refers to a
`communication device of a calling party who originates a call
`or attempts to place a call to a called party. The calling party
`device and the called party device are, for example, mobile
`50 phones, smart phones, tablet computing devices, network
`enabled computing devices, etc. The call completion appli(cid:173)
`cation on the calling party device detects an incomplete call
`made by the calling party to the called party. As used herein,
`the phrase "incomplete call" refers to a call made by a calling
`55 party to a called party, that is not received or completed by the
`called party, or not connected to the called party device, for
`example, because the called party is busy, is in an out of
`coverage area, is unreachable, etc., or the called party device
`is switched off, or the call is not answered by the called party,
`60 or due to network congestion, etc. In an embodiment, the
`phrase "incomplete call" also refers to a call of a short dura(cid:173)
`tion, referred to as a "short duration call", made by a calling
`party to a called party, that is considered incomplete as the
`duration of the call is too short for an intended communica-
`65 tion to occur between the calling party and the called party. In
`an embodiment, the call completion application on the calling
`party device monitors the incomplete call as the incomplete
`
`Petitioner Exhibit 1001, Page 10 of 23
`
`

`

`US 9,185,227 B2
`
`3
`call progresses from the incomplete call being initiated, the
`incomplete call being answered or rejected, and the incom(cid:173)
`plete call being terminated.
`On detecting an incomplete call, the call completion appli(cid:173)
`cation on the calling party device determines one or more of 5
`multiple call completion actions to be performed to complete
`the detected incomplete call. The call completion actions
`comprise, for example, setting a reminder to call back the
`called party at a configurable time, recording media data on
`the calling party device, transmitting the media data to the 10
`called party device, transmitting a missed call alert to the
`called party device, transmitting a notification of the detected
`incomplete call to the called party device, transmitting a
`notification on availability of the called party, transmitting the
`media data to a social networking platform, transmitting an 15
`automated message requesting the called party to call back
`the calling party when available, etc., and any combination
`thereof. As used herein, the term "media data" refers to a
`stored form of media, for example, sounds, images, videos,
`text data, etc., produced and recorded for the purpose of 20
`audibly listening to a reproduction of those sounds or for the
`purpose of viewing a reproduction of the images, videos, text
`data, etc. The media data comprise, for example, one of text
`data, audio data, video data, audiovisual data, image data,
`multimedia data, message data, etc., and any combination 25
`thereof. In an embodiment, the call completion application
`determines the call completion actions based on a duration of
`the detected incomplete call. In another embodiment, the call
`completion application determines the call completion
`actions based on one or more of configurable criteria. The 30
`configurable criteria comprise, for example, user configura(cid:173)
`tion of the call completion application on the calling party
`device, call settings configured on the calling party device,
`network characteristics, device characteristics, etc.
`In another embodiment, the call completion application 35
`determines the call completion actions as follows: On detect-
`ing an incomplete call, the call completion application on the
`calling party device generates a request defining the call
`completion actions for completing the detected incomplete
`call. The call completion application renders the generated 40
`request on a graphical user interface ( GUI) of the calling party
`device and receives a response to the generated request from
`the calling party via the GUI. That is, the calling party's call
`completion application determines the intent of the calling
`party for performing an appropriate action for communicat- 45
`ing with the called party based on the received response. The
`response comprises, for example, a selection of one or more
`of the call completion actions to be executed for completing
`the detected incomplete call.
`The call completion application on the calling party device 50
`triggers execution of one or more call completion actions
`determined based on the duration of the detected incomplete
`call, or determined based on the configurable criteria, or
`determined from the received response of the calling party,
`based on one or more action execution criteria for completing 55
`the detected incomplete call. For example, the calling party's
`call completion application transmits a message of the calling
`party to the called party device via the network based on one
`or more action execution criteria. The action execution crite-
`ria comprise, for example, configuration of call completion 60
`actions on the calling party device, a presence or an absence
`of a message box and/or a messaging application for receiv-
`ing media data on a network account of the called party or on
`the called party device, a presence or an absence of a data
`connection from the calling party device to a network, a 65
`presence or an absence of a messaging service in a network
`component of the calling party, a presence or an absence of a
`
`4
`messaging service in a network component of the called
`party, reach of the messaging service to deliver the media data
`to the network component of the called party or to the called
`party device, network options provided to the calling party
`device and the called party device by the network to which the
`calling party device and the called party device are connected,
`call completion preferences configured by the call comple(cid:173)
`tion application on the calling party device, etc. In an embodi(cid:173)
`ment, the call completion application determines the call
`completion action to be executed, including a mode of trans(cid:173)
`mission of the media data, for example, a media message
`from the calling party device to the called party device via a
`network based on one or more of the action execution criteria.
`Disclosed herein is a method for completing a call attempt
`made by a calling party to a called party. The call attempt is
`made by the calling party to contact the called party and
`establish a communications link with the called party. The
`call completion application on the calling party device moni(cid:173)
`tors call attempts, manages multiple call completion actions
`selectable by the calling party, and manages completion of the
`call attempt for the calling party. The call completion appli(cid:173)
`cation on the calling party device detects a call attempt unan(cid:173)
`swered by the called party. The call completion application
`generates a request defining the call completion actions for
`completing the detected unanswered call attempt. The call
`completion application renders the generated request on the
`GUI of the calling party device and receives a response to the
`generated request from the calling party via the GUI. The call
`completion application triggers execution of one or more call
`completion actions determined from the received response of
`the calling party based on one or more of the action execution
`criteria for completing the detected unanswered call attempt.
`In an embodiment, the call completion application on the
`calling party device determines the call completion action to
`be executed, including a mode of transmission of media data,
`for example, a media message from the calling party device to
`the called party device via the network based on the received
`response and one or more of the action execution criteria.
`In an embodiment, the call completion application on the
`calling party device detects a call attempt answered by the
`called party and generates a request defining options for per(cid:173)
`forming the call completion actions associated with the
`detected answered call attempt for completing the detected
`answered call attempt. In this embodiment, the answered call
`attempt is a short duration call interpreted by the call comple(cid:173)
`tion application on the calling party device as an incomplete
`call. The options are, for example, based on the length or
`duration of the detected answered call attempt. The options
`comprise, for example, setting a reminder to call back the
`called party at a configurable time, recording media data on
`the calling party device, transmitting the media data to the
`called party device, transmitting a notification of the call
`attempt to the called party device, transmitting media data to
`a social networking platform, transmitting an automated mes(cid:173)
`sage requesting the called party to call back the calling party
`when available, etc., and any combination thereof. The call
`completion application renders the generated request on the
`GUI of the calling party device and receives a response to the
`generated request from the calling party via the GUI. The
`response comprises a selection of one or more of the defined
`options. The call completion application triggers execution of
`the selected call completion actions determined from the
`received response of the calling party based on one or more of
`the action execution criteria for completing the detected
`answered call attempt. In this embodiment, the call comple(cid:173)
`tion application addresses answered calls of duration, for
`example, less than about 2 seconds, where no intended com-
`
`Petitioner Exhibit 1001, Page 11 of 23
`
`

`

`US 9,185,227 B2
`
`5
`munication has occurred between the calling party and the
`called party. The call completion application considers these
`short duration answered calls as incomplete as the time of 2
`seconds is too short to have a conversation and therefore the
`call completion application provides the option of completing 5
`the call to the calling party.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`6
`calling party device and the called party device are a mobile
`phone, a smart phone, a tablet computing device, a portable
`computing device, a personal digital assistant, a touch centric
`device, a network enabled computing device, etc. The calling
`party device and the called party device may also be hybrid
`devices that combine the functionality of multiple devices.
`Examples of a hybrid device comprise a cellular telephone
`that includes a media player functionality, a gaming device
`that includes a wireless communications capability, a cellular
`10 telephone that includes game and electronic mail (email)
`functions, a portable device that receives email, supports
`mobile telephone calls, has music player functionality, and
`supports web browsing, etc.
`The method disclosed herein provides 101 a call comple-
`15 tion application executable by at least one processor on a
`calling party device. The method disclosed herein is imple(cid:173)
`mented using a computer system as disclosed in the detailed
`description of FIG. 6. The call completion application is a
`software application that can be downloaded and imple-
`20 mented on the calling party device. A sender, that is, the
`calling party initiates a call to a recipient, that is, the called
`party, when the sender wants to communicate with the recipi(cid:173)
`ent. A first network component receives a call attempt from
`the calling party to contact the called party. The call attempt is
`made by the calling party to contact the called party and
`establish a communications link between the calling party
`and the called party. The first network component routes the
`call attempt to a second network component for establishing
`a communications link between the calling party and the
`30 called party. As used herein, the terms "first network compo(cid:173)
`nent" and "second network component" refer, for example, to
`a mobile switching center (MSC), a base station subsystem
`(BSS), a radio access network (RAN), a telephone exchange,
`a telephone switch, etc., serving the calling party and the
`35 called party respectively. The first network component is, for
`example, an originating switch or an originating mobile
`switching center (MSC) associated with the calling party. The
`second network component is, for example, a terminating
`switch or a terminating mobile switching center (MSC) asso-
`40 ciated with the called party. The second network component
`is either the same as the first network component or one of
`multiple network components excluding the first network
`component.
`The call completion application on the calling party device
`detects 102 an incomplete call made by the calling party to the
`called party. In an embodiment, the incomplete call is a call
`made by a calling party to a called party, that is not received
`or completed by the called party, or not connected to the
`called party device due to the occurrence of one or more of
`50 multiple events comprising, for example, the called party
`being busy, the called party device being in an out of coverage
`area, the called party device being unreachable, the called
`party device being switched off, network congestion, the call
`not being answered by the called party, etc. In another
`55 embodiment, the incomplete call is a call of a short duration,
`also referred to as a "short duration call", made by a calling
`party to a called party, that is considered incomplete as the
`duration of the call is too short for an intended communica(cid:173)
`tion to occur between the calling party and the called party. In
`60 an embodiment, the call completion application on the calling
`party device monitors the incomplete call as the incomplete
`call progresses from the incomplete call being initiated, the
`incomplete call being answered or rejected, and the incom(cid:173)
`plete call being terminated. The call completion application
`65 checks the status of the call that terminates as well as the
`duration of the call to determine if the call was incomplete or
`not. Consider an example where a calling party A calls a
`
`The foregoing summary, as well as the following detailed
`description of the invention, is better understood when read in
`conjunction with the appended drawings. For the purpose of
`illustrating the invention, exemplary constructions of the
`invention are shown in t