Patent Application
20110034154
When a call is received at a user's mobile communications device, such as a mobile phone or personal digital assistant (“PDA”), the user may ignore the call by selecting an “ignore call” option on the mobile communications device. Ignoring the call may be a convenient way to keep the mobile communications device from continuously ringing/vibrating, especially if the user cannot immediately answer the call and speak with the caller. For example, the user may be in the middle of a work-related meeting and cannot readily answer a personal call. However, current mobile communications devices do not provide the caller with a reason as to why his or her call is being ignored. As a result, the caller may continue to call the user's mobile communications device, which may be bothersome to both the caller and the user. Therefore, as mobile communications become increasingly popular, it may be important to have a system and method for providing a comprehensive and efficient way for letting a caller know why his or her call is being ignored.
In order to facilitate a fuller understanding of the exemplary embodiments, reference is now made to the appended drawings. These drawings should not be construed as limiting, but are intended to be exemplary only.
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. It should be appreciated that the same reference numbers will be used throughout the drawings to refer to the same or like parts. It should be appreciated that the following detailed description are exemplary and explanatory only and are not restrictive.
Exemplary embodiments may provide a system and method for providing a reason for ignoring a call. That is, exemplary embodiments may, among other things, expand and optimize communications by comprehensively and effectively providing one or more reasons to a caller as to why his or her incoming call is being ignored. In addition, some embodiments may also provide custom alerts so that a called party may preview an incoming call and/or to see the importance/priority of that incoming call.
Most mobile communications devices (e.g., wireless devices) are typically equipped with a caller identification feature that allows a user of the mobile communications device to preview who is calling. As discussed above, if a user of the mobile communications device is unable to answer a call, the user may initially check to see who is calling, and if the call does not seem important enough to answer, the user may select an ignore option on the mobile communications device. For example, if the user is in the middle of a work-related meeting and his or her spouse calls, the user may recognize that the caller is his or her spouse and assume that the call is not important enough to take at that time. The user may ignore the call and call back later at a more convenient time. By selecting the ignore option, the mobile communications device may stop any further ringing/vibrating at the mobile communications device and the user may continue participating his work-related meeting without further disturbance by that call attempt. The caller, however, may be unaware as to why the call was ignored and may assume, for example, that reception was poor among many other speculative reasons. As a result, the caller may call the user again. In this example, the user may receive one or more additional calls from his or her spouse, which may cause repeated disturbance/distraction, especially if the user is still in his or her work-related meeting. Furthermore, if the caller is calling because of emergency, there may be no way the caller can let the user or called party know that it is an emergency other than calling repeatedly.
In one or more exemplary embodiments, a system and method may be provided so that a user of a wireless device may let the caller know why an incoming call is being ignored. Referring the example described above, the called party who receives a call may select an ignore option and may provide one or more reasons to the caller as to why the call is being ignored. For example, the user may select a reason from a list of reasons provided at the mobile communications device. These may include “In a meeting” or “Busy right now.” Such reasons may then be conveyed to the caller. This way, if the call is unimportant, the caller may simply wait for the user to call back after the meeting or when the user is available. In some embodiments, if the user selects a reason while the call is still being attempted, the reason may be incorporated to a voicemail prompt and may notify the caller during a playback message. This way, when the caller gets transferred to voicemail, he or she can immediately be notified of the reason the user is ignoring the call. In other embodiments, the reason the call has been ignored may be sent to the caller's telephonic device via text message or other similar message (e.g., SMS). A text message may ensure that the caller is notified of the reason, which may be particularly useful if the caller decides not to listen to the voicemail prompt. Other various embodiments may also be provided.
In the event a caller is calling because of an emergency, embodiments of the present invention may also provide a way for the caller to let the called party know that that the call is an emergency. This may prevent repeated calls, which may be inconvenient to both the caller and the called party.
Network 102 may be a wireless network, a wired network or any combination of wireless network and wired network. For example, network 102 may include one or more of a fiber optics network, a passive optical network, a cable network, an Internet network, a satellite network (e.g., operating in Band C, Band Ku or Band Ka), a wireless LAN, a Global System for Mobile Communication (“GSM”), a Personal Communication Service (“PCS”), a Personal Area Network (“PAN”), D-AMPS, Wi-Fi, Fixed Wireless Data, EE 802.11a, 802.11b, 802.15.1, 802.11n and 802.11g or any other wired or wireless network for transmitting and/or receiving a data signal. In addition, network 102 may include, without limitation, telephone line, fiber optics, IEEE Ethernet 802.3, a wide area network (“WAN”), a local area network (“LAN”), or a global network such as the Internet. Also, network 102 may support, an Internet network, a wireless communication network, a cellular network, or the like, or any combination thereof. Network 102 may further include one, or any number of the exemplary types of networks mentioned above operating as a stand-alone network or in cooperation with each other. Network 102 may utilize one or more protocols of one or more network elements to which it is communicatively coupled. Network 102 may translate to or from other protocols to one or more protocols of network devices. Although network 102 is depicted as one network, it should be appreciated that according to one or more embodiments, network 102 may comprise a plurality of interconnected networks, such as, for example, a service provider network, the Internet, a broadcaster's network, a cable television network, corporate networks, and/or home networks.
Network elements 104, 106, 110, and data storage 108 may transmit and receive data to and from network 102 representing broadcast content, user request content, mobile communications data, and/or other data. The data may be transmitted and received utilizing a standard telecommunications protocol or a standard networking protocol. For example, one embodiment may utilize Session Initiation Protocol (“SIP”). In other embodiments, the data may be transmitted and/or received utilizing other Voice Over IP (“VOIP”) or messaging protocols. For example, data may also be transmitted and/or received using Wireless Application Protocol (“WAP”), Multimedia Messaging Service (“MMS”), Enhanced Messaging Service (“EMS”), Short Message Service (“SMS”), Global System for Mobile Communications (“GSM”) based systems, Code Division Multiple Access (“CDMA”) based systems, Transmission Control Protocol/Internet (“TCP/IP”) Protocols, or other protocols and systems suitable for transmitting and receiving data. Data may be transmitted and received wirelessly or may utilize cabled network or telecom connections such as an Ethernet RJ45/Category 5 Ethernet connection, a fiber connection, a traditional phone wireline connection, a cable connection or other wired network connection. Network 102 may use standard wireless protocols including IEEE 802.11a, 802.11b and 802.11g. Network 102 may also use protocols for a wired connection, such as an IEEE Ethernet 802.3.
Transmitter/receiver 118 may be a repeater, a microwave antenna, a cellular tower, or another network access device capable of providing connectivity between to different network mediums. Transmitter/receiver 118 may be capable of sending or receiving signals via a mobile network, a paging network, a cellular network, a satellite network or a radio network. Transmitter/receiver 1318 may provide connectivity to one or more wired networks and may be capable of receiving signals on one medium such as a wired network and transmitting the received signals on a second medium, such as a wireless network.
Wireless device 120 may be a mobile communications device, wireline phone, a cellular phone, a mobile phone, a satellite phone, a personal digital assistant (“PDA”), a computer, a handheld MP3 player, a handheld multimedia device, a personal media player, a gaming device, and/or other devices capable of communicating with network 102 via transmitter/receiver 118.
Network elements, transmitter/receiver 118, data storage 108, and set-top box 114 may include one or more processors (not shown) for recording, transmitting, receiving, and/or storing data. Although network elements, transmitter/receiver 118 and data storage 108 are depicted as individual elements, it should be appreciated that the contents of one or more of a network element, transmitter/receiver 118, and data storage 108 may be combined into fewer or greater numbers of devices and may be connected to additional devices not depicted in
Data storage 108 may be network accessible storage and may be local, remote, or a combination thereof to network elements 104, 106, and 110. Data storage 108 may utilize a redundant array of inexpensive disks (“RAID”), tape, disk, a storage area network (“SAN”), an internet small computer systems interface (“iSCSI”) SAN, a Fibre Channel SAN, a common Internet File System (“CIFS”), network attached storage (“NAS”), a network file system (“NFS”), or other computer accessible storage. In one or more embodiments, Data storage 108 may be a database, such as an Oracle database, a Microsoft SQL Server database, a DB2 database, a MySQL database, a Sybase database, an object oriented database, a hierarchical database, or other database. Data storage 108 may utilize flat file structures for storage of data.
Network elements 104, 106, and 110 may be one or more servers (or server-like devices), such as a Session Initiation Protocol (“SIP”) server. Network elements 104, 106, and 110 may include one or more processors (not shown) for recording, transmitting, receiving, and/or storing data. According to one or more embodiments, network elements 104, 106, and 110 may be servers providing media content to one or more users. In other embodiments, network elements 104, 106, and 110 may be servers that provide network connection between two or more wireless devices 118. Network elements 104, 106, and 110 may also be servers of a service provider, the Internet, a broadcaster, a cable television network, and/or another media provider.
Network element 110 may be a residential gateway, such as a router, an optical network terminal or another piece of Customer Premises Equipment (“CPE”) providing access to one or more pieces of equipment. For example, network element 110 may provide audio/video programming content feeds to a set-top box, such as set-top box 116. Network element 110 may also provide network connectivity for other clients, such as a Voice Over IP (“VOIP”) phone (not shown) and a network client, e.g., network client 112.
Network client 112 may be a desktop computer, a laptop computer, a server, a personal digital assistant, or other computer capable of sending and/or receiving network signals. Network client 112 may use a wired or wireless connection. Although depicted as connected via a residential gateway in
According to one or more embodiments, set-top box 114 may receive a media selection, such as a channel selection from a user (e.g., via wireless remote (not shown)). Set-top box 114 may provide the programming feed corresponding to the selected media channel. According to some embodiments, set-top box 114 may analyze metadata to identify search criteria related to the media selection. The metadata may be local to set-top box 114 or remote from set-top box 114. For example, set-top box 114 may analyze closed captioning data associated with the selected programming feed, electronic program guide information associated with the programming feed, or other metadata. Set-top box 114 may request, query, or otherwise interface with remote sources of data. According to some embodiments, set-top box 114 may forward selection data to one or more network components, such as one or more of network elements 104, 106, and 110. Set-top box 114 may also forward metadata associated with a media selection to one or more network elements, such as network elements 104, 106, and 110. According to some embodiments, set-top box 114 may forward only a channel selection and one or more network elements may separately obtain metadata.
System 100 may be used for mobile telecommunications between two or more components of the system 100, e.g., two or more wireless devices, wireless device with network client, set top box with wireless device, landline phone, VoIP, etc. System 100 may also be used for transmitting and/or receiving multimedia content. The various components of system 100 as shown in
Storage module 202 may manage or access electronic storage including databases and other organized electronic storage. Storage module 202 may provide one or more interfaces for custom module 204, the search module 206, and/or presentation module 208. Storage module 202 may store reasons for ignoring a call or other similar data. These may include reasons, such as “In a meeting,” “Busy,” “Currently unavailable,” “Traveling,” “Hiking,” “Sleeping,” “All tied up,” “Don't want to talk to you,” “Call me later,” etc.
Custom module 204 may receive input from a user to customize one or more reasons for ignoring a call. For example, custom module 204 may provide an interface for the user to input his or her own reasons for ignoring call. A user may enter his or reasons via the interface. It should be appreciated that the customized reason may also be stored in the storage module 202, e.g., for future selection and use.
Search module 206 may receive input or other search criteria from one or more user queries/searches. Search module 206 may interface with the storage module 202 and with a user at a wireless device (e.g., mobile communications device) and/or a multimedia display device (e.g., a television set via a set top box) to receive reasons for ignoring a call or other data. In this example, the user may select a reason for ignoring a call from a plurality of reasons stored in storage module 202. The search module 206 may provide various searching methods and processes for a user to find a reason to ignore a call.
Formatting may be included in the search module 206 so that the search results may be transmitted/received in format compatible with one or more user devices. For example, search results may be formatted as extensible Markup Language (“XML”) and provided to a user as a Really Simple Syndication (“RSS”) feed. Search results may also be optically packaged for speedy delivery over network 102 or may be packaged according to specified preferences. Other formatting parameters may also be provided.
Presentation module 208 may interface with a user at a wireless device (e.g., mobile communications device) and/or a multimedia display device (e.g., a television set via a set top box). Presentation module 208 may present the user a graphical interface with which the user may select one or more reasons to ignore a call. Therefore, the presentation module 208 may interface with the storage module 202, the custom module 204, and/or the search module 206 so that the user may send a caller his or her reason for ignoring an incoming call.
The ignore/priority module 200 may provide a way for a user to let a caller know why his or her call is being ignored. In some embodiments, the ignore/priority module 200 may be implemented server-side, e.g., with network elements 104 and/or 106. In other embodiments, the ignore/priority module 200 may be implemented client-side, e.g., with network element 110, network client 112, set top box 114, and/or wireless device 120.
In the event the user selects the “Ignore” option, another illustrative screen 300B may be presented, as depicted in
A “Cancel” option may be another selection option and be provided in the event the user mistakenly selected the “Ignore” option from screen 300A. If the call is attempting to connect, the “Cancel” option may allow the user to go back to screen 300A and select the “Accept” option to answer the call.
It should be appreciated that an “Other” option may also be provided at screen 300B for other various functionalities and features.
It should also be appreciated that ignore/priority module 200 may also be used by a caller to indicate priority of a call to the called party.
Referring to
While this may be useful in situations where a caller need to notify the called party of the priority of a call in a personal and/or work-related situation, providing custom alerts indicating call priority may also be useful in emergency situations. For example, the Federal Emergency Management Agency (FEMA) may send an emergency custom alert to all home phones in a particular area code and/or zip code to warn of an emergency. In other embodiments, for example, an emergency custom alert may be sent to cell phones off of a communications tower (e.g., mobile transceiver/receiver 118). Here, the emergency custom alert may let the called party know that a call is high priority and from FEMA to warn of a dam collapse sending flood waters rushing down to a nearby town or city. In particular, the custom alert may instruct residents and drivers to seek higher ground immediately and avoid driving on roads.
Although a reason to ignore call and/or priority level has been primarily directed to a visible message on a device, it should be appreciated that other various modes of presentation may also be provided. For example, the reason and/or priority level may be stored, searched, and/or presented in an audio format (e.g., a custom ringtone).
In other embodiments, the user may indicate on his or her device one or more reasons to ignore a call before an incoming call is received. For instance, a user may preset his or her device with his current status, e.g., “Busy,” “In a meeting,” “Unavailable,” “Call you later,” and/or other status indicators. In this example, when an incoming call is registered at the user's wireless device, the ignore/priority module 200 may automatically inform the caller at his or her calling device know of the user's preset status.
It should be appreciated that while embodiments are primarily directed to handling incoming calls via a mobile communications device, other variations and/or various implementations may also be provided.
By linking received calls with one or more other devices, such as a set top box or TV, a user/viewer may be able to maximize his or her entertainment pleasure without undue burden or inconvenience, much like when in a work-related meeting. Although described primarily with respect to a television display, it should be appreciated that a variety of device interconnectivity may also be implemented.
At block 510, an incoming call from a caller may be identified by the ignore/priority module 200, which may be incorporated in a network element comprising one or more computer processors and data storage units. The network element may be at least one of network element 110, network client 112, set top box 114, and a wireless device 120.
At block 520, information associated to the incoming call may be transmitted to a user at a first communications device (e.g., a mobile phone). In this example, the information may include caller identifier information, such as name, phone number, image, etc., and/or other information.
At block 530, a reason for ignoring the incoming call may be received at the network element. For example, in some embodiments, an instruction to ignore the incoming call may first be received at the network element. For example, the user may select an option to ignore the incoming call at the first communications device. In some embodiments, a selectable option to ignore the incoming call may be transmitted to the first communications device as an option for the user to select.
In other embodiments, one or more selectable reasons from which a user selects a reason for ignoring the incoming call may be provided to the first communications device. In some embodiments, the one or more selectable reasons may comprise at least one of the following reasons: “busy,” “in a meeting,” “unavailable,” and “custom.” The custom reason may allow the user of the first communications device to generate a customized reason for ignoring the incoming call, as described above.
It should be appreciated that the one or more selectable reasons may be stored in the storage module 202. Also, it should be appreciated that the search module 206 may provide a user interface to search for the one or more reasons for ignoring the incoming call.
At block 540, the reason for ignoring the incoming call may be transmitted to the caller at a second communications device (e.g., a mobile phone). In some embodiments, the reason for ignoring the incoming call may be in at least one of the following formats: voicemail, text message, image, and multimedia.
At block 610, instructions to initiate a call to a called party may be received by the ignore/priority module 200, which may be incorporated in a network element comprising one or more computer processors and data storage units. The network element may be at least one of network element 110, network client 112, set top box 114, and a wireless device 120. In some embodiments, a selectable option to provide a priority level for the call may be provided.
At block 620, a priority level may be received by the network element to be included with the call. In some embodiments, one or more selectable priority levels from which a user selects a priority level for the call may be provided. In this example, the one or more selectable priority levels may comprise at least one of the following priority levels: “emergency,” “important,” “not important,” and “custom.” The custom priority level may allow the user to generate a customized priority level of the call, as discussed above,
It should be appreciated that the one or more selectable priority levels may be stored in the storage module 202. It should also be appreciated that the search module 206 may allow a user the ability to search for the one or more priority levels for the call.
At block 630, the priority level may be transmitted with the call for display at a communications device associated with the called party. In some embodiments, the priority level for the call may be in at least one of the following formats: voicemail, text message, image, and multimedia.
In summary, embodiments may provide a system and method for comprehensively and effectively providing a reason for ignoring a call and/or a priority level of a call. It should be appreciated that although embodiments are described primarily with incoming phone calls, the systems and methods discussed above are provided as merely exemplary and may have other applications. These may include emergency alerts, voicemail previews, dissemination of various news/information, etc.
While depicted as various servers and/or devices, it should be appreciated that embodiments may be constructed in software and/or hardware, as a separate and/or stand-alone device, physical and/or virtual, or as pan of an integrated transmission and/or switching device.
Additionally, it should also be appreciated that system support and updating the various components of the system may be easily achieved. For example, a system administrator may have access to one or more of the components of the system, network, and/or device. It should also be appreciated that the one or more system components, servers, and/or devices of the system may not be limited to physical components. These components may be software based, virtual, etc. Moreover, the various components, servers, and/or devices may be customized to perform one or more additional features and functionalities. Such features and functionalities may be provided via deployment, transmitting and/or installing software/hardware.
It should also be appreciated that each of the communications devices, servers, and/or network elements may include one or more processors (not shown) for providing a reason for ignoring a call and/or priority level of a call. It should be appreciated that one or more data storage systems (e.g., databases) (not shown) may also be coupled to each of the devices or servers of the system. In one embodiment, the one or more data storage systems may store relevant information for each of the servers and system components.
It should be appreciated that the contents of any of these one or more data storage systems may be combined into fewer or greater numbers of data storage systems and may be stored on one or more data storage systems and/or servers. Furthermore, the data storage systems may be local, remote, or a combination thereof to clients systems, servers, and/or other system components. In another embodiment, information stored in the databases may be useful in providing additional personalizations and customizations.
In the preceding specification, various embodiments have been described with reference to the accompanying drawings. It will, however, be evident that various modifications and changes may be made thereto, and additional embodiments may be implemented, without departing from the broader scope of the disclosure as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative rather than restrictive sense.
