A CELL PHONE WITH SCHEDULED-BASED SUPPRESSION OF A NOTIFICATION OF AN INCOMING CALL
Technical Field This disclosure relates to cell phones, and more particularly, to a cell phone with a schedule-based suppression of a notification of an incoming call.
Description of the Related Art
A typical incoming call notification on a cell phone is an audible alert such as ringing. The user will often have to turn off the cell phone or disable the ringer during meetings, classes, and other time periods when the call notification or audible would be disturbing.
The user must manually disable the phone just before the period during which call notification, such as ringing, is to be disabled.
Therefore, a need exists for a cell phone that would remain on during periods when a notification of an incoming call suppressed.
SUMMARY OF THE INVENTION
A cell phone includes a radio frequency transceiver coupled to an antenna, a phone modem coupled to the transceiver; a phone interface coupled to the phone modem and transceiver; and a display, processor, read only memory ROM and random access memory RAM each coupled to the phone interface. The ROM and RAM memory is configured to permit scheduled suppression of a notification of a call received over the antenna.
Alternatively, a method for schedule based suppression on a cell phone of a notification of a call received includes the steps of entering on a cell phone interface a starting period for a scheduled suppression of a call notification, entering on the cell phone interface an ending period for the scheduled suppression, and entering a status enabling the cell phone to suppress notification of a call received by the cell phone for the duration from the starting period to the ending period. BRIEF DESCRIPTION OF DRAWINGS
This disclosure will present in detail the following description of preferred embodiments with reference to the following figures wherein:
FIG. 1 is a block diagram of a calendar interface display on a cell phone in accordance with the present invention;
FIG. 2 is a block diagram of a cell phone architecture for implementing the present invention;
FIG. 3 is a block diagram of an exemplary calendar data structure in accordance with the present invention; FIG.4 is a flow diagram of an exemplary calendar process in accordance with the present invention;
FIG. 5 is a flow diagram of an exemplary phone process in accordance with the present invention.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
A cell phone user will typically have to turn off his phone or disable his ringer during meetings, classes, and other time periods when he does not wish to be disturbed. This invention would allow the user to keep his phone on during these meetings and not be disturbed.
The present invention involves the use of a cell phone that has PDA capabilities such as a calendar. When the user enters an appointment in the calendar he will have an option to configure the appointment so the ringer on the phone is muted. If a phone call comes in during the scheduled time of a Do Not Disturb appointment, the phone will not ring and the call will be routed directly to voice mail. Other options include telling the phone to vibrate instead of not ringing during certain appointments. Referring now in specific detail to the drawings in which like reference numerals identify similar or identical elements throughout the several views, and initially to FIG. 1, a block diagram of a calendar interface display 10 on a cell phone.
Minimally, the display interface 10 would show and permit entry of a start date and time 11, an end date and time 12 and status 13. The exemplary busy status 13 shown can be for a condition when an incoming call is received the call notification or a ringing is suppressed during the start period to the end period.
An exemplary cell phone hardware architecture 20 is shown in block form in FIG. 2. The display 21, processor 22, ROM 23, RAM 24 and phone interface 25 can be interconnected over a bus 29. The phone interface 25 is coupled to the modem 27 and radio frequency RF receiver and transmitter 26 tied to the antenna 28.
Referring to an exemplary memory allocation structure for a calendar interface display, a pointer in memory 31 can point to a previous calendar entry (not shown), a current appointment 33, and the next entry 32 that would point or reference to its own current appointment description structure 34.
Referring now to FIG. 4, an exemplary flow diagram 40 illustrates a section of code which interprets appointments from the calendar data structure 20. When the operating system calls the calendar process, this section of code is executed. First the time of the next appointment entry in the calendar linked list is compared with the system clock 41. If it is time for an appointment, an appointment is added to an active appointment list 42. The active appointment list is a linked list similar to the calendar data structure lists 30, except that only active appointments are on the list. The active appointment list points to description structures 34 of only active appointments. Then the pointing is directed to the first active appointment on the active appointment list in block 43. Any operations necessary for that appointment are done 44. This would include setting up any phone related parameters as instructed in the appointment description structure. If the appointment indicates no calls, information is written in a shared area of memory for the phone process to read which will tell the phone process to not ring the phone.
Other parameters can be included in the appointment, enabling such features as follows: ring as normal operation, ring only if person calling is on priority list, ring only if a specific number calls, vibrate instead of ring, provide a special voice prompt and take a message locally on the phone, etc. Block 44 causes transfer of appointment related phone control to be transferred to the phone control process. A check is made to determine if the current appointment is over 45. If the current appointment is over, it is removed from the active appointment list, and phone control parameters in the shared memory are restored to defaults 46. The active appointment pointer is adjusted to the next active appointment 44. If all active appointments have been checked 48, then the routine returns to the operating system. If multiple concurrent appointments have different phone suppression levels, the strongest level is used, i.e.,
"Do Not Disturb" is stronger than vibrate on a priority list. This bit of code 40 is part of the calendar program, called when the operating system runs a calendar program thread. The flow diagram 50 of FIG. 5 illustrates the operation of the phone control process. First, the process decides whether appointment properties have been activated in the shared memory by the calendar program thread. If there are not appointment based changes in call handling, the process decision 51 allows the call to be processed as usual 52, based on whatever the default ring properties the user has established for the phone. If there are appointment based phone control features enabled, then the process parses the features in the following path of decisions starting with 53. If the appointment calls for no ring, then the ring feature on the phone is disabled 54, and the phone process is allowed to continue as usual. If no ring selection 53 was true, the voice mail service at the service provider's office would pick up the call.
When the appointment only allows calls from priority numbers or names to be allowed, the decision 55 passes control to decision 56, which waits for caller ID. If caller ID is available, the received caller LD number or name is checked against the priority list in decision 58. If the name or number is on the list, then the phone will ring and control will pass to continue processing the call in 60. Otherwise, if caller ID is not available in decision 56, or if the name or number is not available in decision 58, ring will be suppressed in 57 or 59, respectively, and the call control will continue as usual, allowing system voice mail to pick up the call.
When the appointment allows calls only from a special list, decision 61 passes control to decision 62, where caller ID is checked. If caller ID is available, the received caller ID name or number is checked with the special list of names or numbers in decision 66. If the name or number was on the special list, the phone is allowed to ring, and control is passed to continue processing the call in 68. If caller ID is not available, or if the incoming name or number is not on the special list, the phone will not ring, and the call process will continue from 63 or 67 respectively, allowing the system voice mail to answer the call. If the appointment calls for vibrate to announce calls, decision 64 will allow the phone to vibrate rather than ring, and pass the control to continue processing the call in 65. Finally, other options could be parsed based on appointment based phone control selections, by adding more options to the parsing tree, including things like auto-answer with a special message, answer the call using local memory for answering machine storage, or other functions. This bit of code 50 would be among the first functions executed when the phone received an incoming call, before the user was alerted to the incoming call.
Having described preferred embodiments for cell phone notification suppression (which are intended to be illustrative and not limiting), it is noted that modifications and variations can be made by persons skilled in the art in light of the above teachings. It is therefore to be understood that changes may be made in the particular embodiments of the invention disclosed which are within the scope and spirit of the invention as outlined by the appended claims. Having thus described the invention with the details and particularity required by the patents laws, what is claimed and desired protected by Letters Patent is set forth in the appended claims.