# US 9,521,261 B2 · Communication reminders > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 9,521,261 B2 - Document ID: US9521261B2 - Status: Granted - Kind: B2 - Application number: 14/450,902 - Filed: 2014-08-04 - Published: 2014-11-20 - Granted: 2016-12-13 - Earliest claimed: 2008-05-20 - Assignees: Microsoft Technology Licensing, LLC - Applicants: Microsoft Technology Licensing, LLC - Inventors: Giridhar Kalpathy Narayanan - Web page: https://patentgrep.com/patent/US9521261B2 ## CPC - H04M 3/565: {relating to time schedule aspects} - H04M 1/2473: {Telephone terminals interfacing a personal computer, e.g. using an API (Application Programming Interface) (details of API H04M7/0021)} - H04M 1/2749: Automatic dialling or redialling systems, e.g. on off-hook or redial on busy - H04M 1/575: {Means for retrieving and displaying personal data about calling party} - H04M 1/72451: according to schedules, e.g. using calendar applications - H04M 1/72484: wherein functions are triggered by incoming communication events - H04M 3/42: Systems providing special services or facilities to subscribers (specially adapted for wireless communication networks H04W4/00) - H04M 3/432: Arrangements for calling a subscriber at a specific time, e.g. morning call service - H04W 4/16: Communication-related supplementary services, e.g. call-transfer or call-hold - H04M 1/2535: {adapted for voice communication over an Internet Protocol [IP] network (Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16)} - H04M 1/27475: using interactive graphical means or pictorial representations - H04M 1/663: Preventing unauthorised calls to a telephone set - H04M 2201/38: Displays - H04M 2203/2072: Schedules, e.g. personal calendars - H04M 2250/60: logging of communication history, e.g. outgoing or incoming calls, missed calls, messages or URLs - H04M: TELEPHONIC COMMUNICATION (circuits for controlling other apparatus via a telephone cable and not involving telephone switching apparatus G08) - H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72) ## Abstract Embodiments are configured to provide reminders associated with communications and other events. In an embodiment, components of a communication system can operate to generate, maintain, and implement reminders associated with communications and other events. A reminder can be automatically generated and scheduled for one or more users of the communication system when a user is unavailable or unable to take a call. Reminders can be generated to include information which can be used to establish a communication event for a subsequent communication associated with each reminder. ## Claims ### Claim 1 A computer-implemented method for communicating between two or more devices comprising: receiving an incoming call at a first device associated with a called party from a caller using a second device, wherein the incoming call includes an identifier comprising one or more of: an identifier for the caller and an identifier for the second device; determining a status of the incoming call, wherein the status is one of: complete and uncomplete; when the status of the incoming call is uncomplete, automatically creating a call reminder for the incoming call having a two-way reminder type; and, using the call reminder to schedule a subsequent call between the caller and the called party. ### Claim 2 (depends on 1) The computer-implemented method of claim 1, further comprising determining the incoming call is uncomplete when one or more of the following conditions are met: the first device is unavailable; the first device is powered off; the called party does not answer the incoming call; and the incoming call is transferred to a voicemail system for the called party. ### Claim 3 (depends on 1) The computer-implemented method of claim 1, further comprising using end-point details to create the call reminder including identifying the first device to receive the subsequent call at one time and a third device to receive the subsequent call at another time. ### Claim 4 (depends on 1) The computer-implemented method of claim 1, further comprising using contact details of one or more of the caller and the called party to create the call reminder. ### Claim 5 (depends on 1) The computer-implemented method of claim 1, wherein the call reminder further comprises recurring reminder settings, snooze option settings, and a reminder time. ### Claim 6 (depends on 1) The computer-implemented method of claim 1, further comprising using touch inputs to interact with the call reminder. ### Claim 7 (depends on 1) The computer-implemented method of claim 1, further comprising using a declining action to generate a reschedule request for the call reminder including a reschedule time. ### Claim 8 (depends on 1) The computer-implemented method of claim 1, further comprising providing the call reminder to the caller according to one or more preferred end-point details of the caller. ### Claim 9 (depends on 1) The computer-implemented method of claim 1, further comprising creating the call reminder including creating one or more of a reminder subject, an importance level, and an endpoint. ### Claim 10 (depends on 1) The computer-implemented method of claim 1, wherein automatically creating a call reminder for the incoming call having the two-way reminder type further comprises creating a call reminder for the caller at the second device and a call reminder for the called party at the first device. ### Claim 11 (depends on 10) The computer-implemented method of claim 10, further comprising using visual, audible, tactile, or other cues to alert or inform the caller and the called party of the subsequent call associated with the call reminder. ### Claim 12 (depends on 1) The computer-implemented method of claim 1, wherein the call reminder comprises an invitation for a calendar application. ### Claim 13 A mobile communication device comprising: a processor; and a memory communicatively coupled to the processor, the memory storing computer-readable instructions that when executed by the processor cause the mobile communication device to: initiate an outgoing call from a caller at the mobile communication device to a called party at a remote device; automatically create a call reminder for the caller when a status of the outgoing call is uncomplete; and use the call reminder to schedule a subsequent call between the caller and the called party. ### Claim 14 (depends on 13) The mobile communication device of claim 13, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to determine the status of the outgoing call is uncomplete when the mobile device receives an indication of one or more of the following: the remote device is unavailable; the remote device is powered off; the called party did not answer the outgoing call; and the outgoing call was transferred to a voicemail system for the called party. ### Claim 15 (depends on 13) The mobile communication device of claim 13, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to include end-point details for the remote device to receive the subsequent call at a first time and a second remote-device to receive the subsequent call at a second time. ### Claim 16 (depends on 13) The mobile communication device of claim 13, wherein the call reminder further comprises one or more of recurring reminder settings, snooze option settings, and preferred end-point details. ### Claim 17 (depends on 13) The mobile communication device of claim 13, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to receive touch inputs as part of interacting with the call reminder. ### Claim 18 (depends on 13) The mobile communication device of claim 13, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to automatically create the call reminder for the caller and the called party when the call reminder is a two-way type reminder. ### Claim 19 (depends on 13) The mobile communication device of claim 13, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to automatically send the call reminder to the called party at the remote device when the call reminder is a two-way type reminder. ### Claim 20 (depends on 19) The mobile communication device of claim 19, further comprising computer-readable instructions that when executed by the processor cause the mobile communication device to include preferred end-point details for the caller in the call reminder sent to the called party.