[go: up one dir, main page]

WO2015009273A1 - Method and apparatus for filtering of a notification - Google Patents

Method and apparatus for filtering of a notification Download PDF

Info

Publication number
WO2015009273A1
WO2015009273A1 PCT/US2013/050473 US2013050473W WO2015009273A1 WO 2015009273 A1 WO2015009273 A1 WO 2015009273A1 US 2013050473 W US2013050473 W US 2013050473W WO 2015009273 A1 WO2015009273 A1 WO 2015009273A1
Authority
WO
WIPO (PCT)
Prior art keywords
notification
event notification
event
rendering
filter
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/US2013/050473
Other languages
French (fr)
Inventor
Sean White
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Nokia Inc
Original Assignee
Nokia Inc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Inc filed Critical Nokia Inc
Priority to PCT/US2013/050473 priority Critical patent/WO2015009273A1/en
Publication of WO2015009273A1 publication Critical patent/WO2015009273A1/en
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • GPHYSICS
    • G06COMPUTING OR CALCULATING; COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F1/00Details not covered by groups G06F3/00 - G06F13/00 and G06F21/00
    • G06F1/16Constructional details or arrangements
    • G06F1/1613Constructional details or arrangements for portable computers
    • G06F1/163Wearable computers, e.g. on a belt
    • GPHYSICS
    • G02OPTICS
    • G02BOPTICAL ELEMENTS, SYSTEMS OR APPARATUS
    • G02B27/00Optical systems or apparatus not provided for by any of the groups G02B1/00 - G02B26/00, G02B30/00
    • G02B27/01Head-up displays
    • G02B27/017Head mounted
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72403User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality
    • H04M1/72409User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories
    • H04M1/72412User interfaces specially adapted for cordless or mobile telephones with means for local support of applications that increase the functionality by interfacing with external accessories using two-way short-range wireless interfaces
    • GPHYSICS
    • G02OPTICS
    • G02BOPTICAL ELEMENTS, SYSTEMS OR APPARATUS
    • G02B27/00Optical systems or apparatus not provided for by any of the groups G02B1/00 - G02B26/00, G02B30/00
    • G02B27/01Head-up displays
    • G02B27/0101Head-up displays characterised by optical features
    • G02B2027/014Head-up displays characterised by optical features comprising information/image processing systems
    • GPHYSICS
    • G02OPTICS
    • G02BOPTICAL ELEMENTS, SYSTEMS OR APPARATUS
    • G02B27/00Optical systems or apparatus not provided for by any of the groups G02B1/00 - G02B26/00, G02B30/00
    • G02B27/01Head-up displays
    • G02B27/017Head mounted
    • G02B2027/0178Eyeglass type
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00Network arrangements or protocols for supporting network services or applications
    • H04L67/50Network services
    • H04L67/55Push-based network services
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04MTELEPHONIC COMMUNICATION
    • H04M1/00Substation equipment, e.g. for use by subscribers
    • H04M1/72Mobile telephones; Cordless telephones, i.e. devices for establishing wireless links to base stations without route selection
    • H04M1/724User interfaces specially adapted for cordless or mobile telephones
    • H04M1/72448User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions
    • H04M1/72454User interfaces specially adapted for cordless or mobile telephones with means for adapting the functionality of the device according to specific conditions according to context-related or environment-related conditions

Definitions

  • the present application relates generally to filtering of a notification.
  • One or more embodiments may provide an apparatus, a computer readable medium, a non-transitory computer readable medium, a computer program product, and a method for determining an event notification associated with an event, causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, receiving a usefulness indication associated with the event notification, and causing modification of the notification filter based, at least in part, on the usefulness indication.
  • One or more embodiments may provide an apparatus, a computer readable medium, a computer program product, and a non-transitory computer readable medium having means for determining an event notification associated with an event, means for causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, means for receiving a usefulness indication associated with the event notification, and means for causing modification of the notification filter based, at least in part, on the usefulness indication.
  • One or more example embodiments further perform determining that a notification filter indicates approval of rendering of the event notification.
  • One or more example embodiments further perform sending information indicative of the event notification and receiving information indicative of the determination that a notification filter indicates approval of rendering of the event notification.
  • the notification filter comprises at least one criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria.
  • the notification filter comprises at least one criteria indicative of the event notification source, and the indication of approval is based, at least in part, on the criteria.
  • the indication of approval comprises at least one of event notification content or event notification context.
  • the event notification is associated with a message and the event notification content is associated with at least one of a message sender, a message title, a message body, or a message header.
  • the event notification context indicates at least one of weather condition, date, time of day, temperature, light conditions, environmental condition, or location of the apparatus.
  • the event notification is associated with a call and the event notification content is associated with at least one of a caller or a call type.
  • the call type relates to at least one of a voice call, video call, packet call, conference call, or telephony call.
  • the event relates to at least one of a call, message, alarm indication, calendar indication, power indication, signal strength indication, or location indication.
  • the notification filter relates to at least one of heuristics or statistical methods.
  • the usefulness indication relates to an indication that a user found the event notification useful.
  • the usefulness indication relates to input that identifies that the event notification was useful to a user.
  • the usefulness indication relates to an action by a user that implies that the event notification was useful to the user.
  • the action by a user relates to at least one of reading the event notification, acknowledging the event notification, or requesting additional information associated with the event notification.
  • the action by a user relates to at least one of ignoring the event notification or dismissing the event notification.
  • the modification of the notification filter causes the notification filter to be more likely to indicate approval of rendering of the event notification. In at least one example embodiment, the modification of the notification filter causes the notification filter to be less likely to indicate approval of rendering of the event notification.
  • One or more example embodiments further perform determining another event notification associated with another event, the other event notification correlating with the event notification and precluding rendering of the other event notification to a user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
  • the peripheral apparatus relates to a wearable apparatus.
  • One or more example embodiments further perform causing modification of a different notification filter based, at least in part, on the usefulness indication, the different notification filter being associated with a different apparatus.
  • causing modification of the different notification filter comprises causing modification of a multiple apparatus notification filter.
  • notification filter and the different notification filter are based, at least in part, on the multiple apparatus notification filter.
  • FIGURE 1 is a block diagram showing an apparatus according to an example embodiment
  • FIGURES 2A-2C are block diagrams illustrating apparatus communication according to at least one example embodiment.
  • FIGURES 3A-3B are block diagrams illustrating filter association according to at least one example embodiment.
  • FIGURES 4A-4C are illustrations showing peripheral apparatuses according to at least one example embodiment.
  • FIGURE 5 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • FIGURE 6 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • FIGURE 7 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • FIGURE 8 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • FIGURES 1 through 8 of the drawings An embodiment of the invention and its potential advantages are understood by referring to FIGURES 1 through 8 of the drawings.
  • circuitry refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present.
  • This definition of 'circuitry' applies to all uses of this term herein, including in any claims.
  • the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware.
  • the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network apparatus, other network apparatus, and/or other computing apparatus.
  • non-transitory computer-readable medium which refers to a physical medium (e.g., volatile or non-volatile memory device), can be differentiated from a “transitory computer-readable medium,” which refers to an electromagnetic signal.
  • FIGURE 1 is a block diagram showing an apparatus, such as an electronic apparatus 10, according to at least one example embodiment. It should be understood, however, that an electronic apparatus as illustrated and hereinafter described is merely illustrative of an electronic apparatus that could benefit from embodiments of the invention and, therefore, should not be taken to limit the scope of the invention. While electronic apparatus 10 is illustrated and will be hereinafter described for purposes of example, other types of electronic apparatuses may readily employ embodiments of the invention.
  • Electronic apparatus 10 may be a personal digital assistant (PDAs), a pager, a mobile computer, a desktop computer, a television, a gaming apparatus, a laptop computer, a media player, a camera, a video recorder, a mobile phone, a global positioning system (GPS) apparatus, and/or any other types of electronic systems.
  • PDAs personal digital assistant
  • the apparatus of at least one example embodiment need not be the entire electronic apparatus, but may be a component or group of components of the electronic apparatus in other example embodiments.
  • apparatuses may readily employ embodiments of the invention regardless of their intent to provide mobility.
  • embodiments of the invention may be described in conjunction with mobile applications, it should be understood that embodiments of the invention may be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries.
  • electronic apparatus 10 comprises processor 11 and memory 12.
  • Processor 11 may be any type of processor, controller, embedded controller, processor core, and/or the like.
  • processor 11 utilizes computer program code to cause an apparatus to perform one or more actions.
  • Memory 12 may comprise volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data and/or other memory, for example, non- volatile memory, which may be embedded and/or may be removable.
  • RAM volatile Random Access Memory
  • non- volatile memory may comprise an EEPROM, flash memory and/or the like.
  • Memory 12 may store any of a number of pieces of information, and data. The information and data may be used by the electronic apparatus 10 to implement one or more functions of the electronic apparatus 10, such as the functions described herein.
  • memory 12 includes computer program code such that the memory and the computer program code are configured to, working with the processor, cause the apparatus to perform one or more actions described herein.
  • the electronic apparatus 10 may further comprise a communication device 15.
  • communication device 15 comprises an antenna, (or multiple antennae), a wired connector, and/or the like in operable communication with a transmitter and/or a receiver.
  • processor 11 provides signals to a transmitter and/or receives signals from a receiver.
  • the signals may comprise signaling information in accordance with a communications interface standard, user speech, received data, user generated data, and/or the like.
  • Communication device 15 may operate with one or more air interface standards, communication protocols, modulation types, and access types.
  • the electronic communication device 15 may operate in accordance with second- generation (2G) wireless communication protocols IS -136 (time division multiple access (TDMA)), Global System for Mobile communications (GSM), and IS-95 (code division multiple access (CDMA)), with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), and/or with fourth-generation (4G) wireless communication protocols, wireless networking protocols, such as 802.11, short- range wireless protocols, such as Bluetooth, and/or the like.
  • Communication device 15 may operate in accordance with wireline protocols, such as Ethernet, digital subscriber line (DSL), asynchronous transfer mode (ATM), and/or the like.
  • Processor 11 may comprise means, such as circuitry, for implementing audio, video, communication, navigation, logic functions, and/or the like, as well as for implementing embodiments of the invention including, for example, one or more of the functions described herein.
  • processor 11 may comprise means, such as a digital signal processor device, a microprocessor device, various analog to digital converters, digital to analog converters, processing circuitry and other support circuits, for performing various functions including, for example, one or more of the functions described herein.
  • the apparatus may perform control and signal processing functions of the electronic apparatus 10 among these devices according to their respective capabilities.
  • the processor 11 thus may comprise the functionality to encode and interleave message and data prior to modulation and transmission.
  • the processor 1 may additionally comprise an internal voice coder, and may comprise an internal data modem.
  • the processor 11 may comprise functionality to operate one or more software programs, which may be stored in memory and which may, among other things, cause the processor 11 to implement at least one embodiment including, for example, one or more of the functions described herein.
  • the processor 11 may operate a connectivity program, such as a conventional internet browser.
  • the connectivity program may allow the electronic apparatus 10 to transmit and receive internet content, such as location-based content and/or other web page content, according to a Transmission Control Protocol (TCP), Internet Protocol (IP), User Datagram Protocol (UDP), Internet Message Access Protocol (IMAP), Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like, for example.
  • TCP Transmission Control Protocol
  • IP Internet Protocol
  • UDP User Datagram Protocol
  • IMAP Internet Message Access Protocol
  • POP Post Office Protocol
  • WAP Wireless Application Protocol
  • HTTP Hypertext Transfer Protocol
  • the electronic apparatus 10 may comprise a user interface for providing output and/or receiving input.
  • the electronic apparatus 10 may comprise an output device 14.
  • Output device 14 may comprise an audio output device, such as a ringer, an earphone, a speaker, and/or the like.
  • Output device 14 may comprise a tactile output device, such as a vibration transducer, an electronically deformable surface, an electronically deformable structure, and/or the like.
  • Output device 14 may comprise a visual output device, such as a display, a light, and/or the like.
  • the apparatus causes display of information, the causation of display may comprise displaying the information on a display comprised by the apparatus, sending the information to a separate apparatus that comprises a display, and/or the like.
  • the electronic apparatus may comprise an input device 13.
  • Input device 13 may comprise a light sensor, a proximity sensor, a microphone, a touch sensor, a force sensor, a button, a keypad, a motion sensor, a magnetic field sensor, a camera, and/or the like.
  • a touch sensor and a display may be characterized as a touch display.
  • the touch display may be configured to receive input from a single point of contact, multiple points of contact, and/or the like.
  • the touch display and/or the processor may determine input based, at least in part, on position, motion, speed, contact area, and/or the like.
  • the apparatus receives an indication of an input.
  • the apparatus may receive the indication from a sensor, a driver, a separate apparatus, and/or the like.
  • the information indicative of the input may relate to information that conveys information indicative of the input, indicative of an aspect of the input indicative of occurrence of the input, and/or the like.
  • the electronic apparatus 10 may include any of a variety of touch displays including those that are configured to enable touch recognition by any of resistive, capacitive, infrared, strain gauge, surface wave, optical imaging, dispersive signal technology, acoustic pulse recognition or other techniques, and to then provide signals indicative of the location and other parameters associated with the touch. Additionally, the touch display may be configured to receive an indication of an input in the form of a touch event which may be defined as an actual physical contact between a selection object (e.g., a finger, stylus, pen, pencil, or other pointing device) and the touch display.
  • a selection object e.g., a finger, stylus, pen, pencil, or other pointing device
  • a touch event may be defined as bringing the selection object in proximity to the touch display, hovering over a displayed object or approaching an object within a predefined distance, even though physical contact is not made with the touch display.
  • a touch input may comprise any input that is detected by a touch display including touch events that involve actual physical contact and touch events that do not involve physical contact but that are otherwise detected by the touch display, such as a result of the proximity of the selection object to the touch display.
  • a touch display may be capable of receiving information associated with force applied to the touch screen in relation to the touch input.
  • the touch screen may differentiate between a heavy press touch input and a light press touch input.
  • a display may display two- dimensional information, three-dimensional information and/or the like.
  • the keypad may comprise numeric (for example, 0-9) keys, symbol keys (for example, #, *), alphabetic keys, and/or the like for operating the electronic apparatus 10.
  • the keypad may comprise a conventional QWERTY keypad arrangement.
  • the keypad may also comprise various soft keys with associated functions.
  • the electronic apparatus 10 may comprise an interface device such as a joystick or other user input interface.
  • Input device 13 may comprise a media capturing element.
  • the media capturing element may be any means for capturing an image, video, and/or audio for storage, display or transmission.
  • the camera module may comprise a digital camera which may form a digital image file from a captured image.
  • the camera module may comprise hardware, such as a lens or other optical component(s), and/or software necessary for creating a digital image file from a captured image.
  • the camera module may comprise only the hardware for viewing an image, while a memory device of the electronic apparatus 10 stores instructions for execution by the processor 11 in the form of software for creating a digital image file from a captured image.
  • the camera module may further comprise a processing element such as a co-processor that assists the processor 11 in processing image data and an encoder and/or decoder for compressing and/or decompressing image data.
  • the encoder and/or decoder may encode and/or decode according to a standard format, for example, a Joint Photographic Experts Group (JPEG) standard format.
  • JPEG Joint Photographic Experts Group
  • FIGURES 2A-2C are block diagrams illustrating apparatus communication according to at least one example embodiment.
  • the examples of FIGURES 2A-2C are merely examples and do not limit the scope of the claims.
  • the number of apparatuses may vary
  • the number of peripheral apparatuses may vary
  • the type of communication between and among apparatuses and peripheral apparatuses may vary
  • the routing of communication between and among apparatuses and peripheral apparatuses may vary, and/or the like.
  • a user may have an apparatus that is viewed as a primary apparatus.
  • Such an apparatus may relate to, for example, a personal digital assistant (PDAs), a pager, a mobile computer, a desktop computer, a television, a gaming apparatus, a laptop computer, a media player, a camera, a video recorder, a mobile phone, a global positioning system (GPS) apparatus, and/or any other types of electronic apparatuses.
  • PDAs personal digital assistant
  • a pager a mobile computer
  • desktop computer a television
  • gaming apparatus a laptop computer
  • media player a media player
  • a camera a media player
  • a camera a media player
  • video recorder a mobile phone
  • GPS global positioning system
  • a user may have one or more peripheral apparatuses that operate in conjunction with and in communication with the user's apparatus.
  • Such a peripheral apparatus may relate to, for example, a watch, a ring, a bracelet, a headset, a pair of glasses, a second electronic apparatus, a global positioning system apparatus, an entertainment apparatus, and/or similar peripheral apparatuses.
  • a peripheral apparatus may be similar as described regarding FIGURES 4A-4C.
  • an event relates to a call, message, notification, update, alarm, calendar occurrence, power, signal strength, location, and/or the like.
  • receipt of an incoming phone call on an apparatus may relate to a call event.
  • Receipt of a social network message for example, may relate to a message event.
  • reaching twenty-percent battery capacity may relate to a power event.
  • an apparatus determines an event notification associated with an event.
  • An event notification may, for example, relate to a notification dialog, a message dialog, a data feed entry, an auditory alert, a visual alert, and/or the like.
  • an event notification is associated with an event and/or various attributes associated with the event.
  • an event notification may be associated with pushed data, streamed data, pulled data, and/or the like.
  • the event notification may be associated with receipt of data pushed to the apparatus in a publish-subscribe model.
  • an event notification may be associated with receipt of streamed data from a data feed.
  • the streamed data may relate to a single data entry of a stream of data entries.
  • an event notification may be associated with receipt of data requested in a pull-based data system.
  • an event notification associated with an event comprises event notification content, event notification context, and/or the like.
  • an event notification may be associated with a message and event notification content may relate to a message sender, a message title, a message body, a message header, and/or the like.
  • the message may relate to a text message, an instant message, a Twitter message, a Facebook message, and/or the like.
  • an event notification may be associated with a call and event notification content may relate to a caller, a call source, a call type, and/or the like.
  • an event notification may be associated with a sensor event and event notification content may relate to a sensor reading.
  • a sensor may relate to a temperature sensor, an occupancy sensor, a motion sensor, a light sensor, and/or the like.
  • a sensor event for example, may relate to temperature conditions meeting some predetermined criteria, occupancy of a room, motion at an entrance door, lighting conditions meeting some predetermined criteria, and/or the like.
  • the call type may relate to a voice call, a video call, a packet call, a conference call, a telephonic call, and/or the like.
  • an event notification context relates to weather condition, date, time of day, temperature, light conditions, environmental condition, location of the peripheral apparatus, and/or the like.
  • event notification context may relate to the context surrounding the occurrence of an event. In certain circumstances, more than one event may occur. In such circumstances, it may be desirable to associate each event with an event notification.
  • the two events may be associated with two event notifications. For example, two similar events may be associated with two correlating event notifications.
  • an apparatus determines another event notification associated with another event in circumstances where the other event notification correlates with an event notification.
  • a user may find it desirable to be alerted of the occurrence of an event associated with an apparatus via an event notification.
  • the user may find it desirable to receive the event notification by way of the user' s apparatus.
  • information indicative of the event notification may be displayed.
  • the user may find it desirable to receive the event notification by way of a peripheral apparatus.
  • it may be desirable to alert a user of an incoming call on an apparatus via a peripheral apparatus.
  • an apparatus may cause rendering of an event notification.
  • a communication channel may relate to communication via near field communication, inductive communication, electric field communication, Bluetooth communication, infrared communication, local area network communication, wireless local area network communication, wired connection communication, any wireless communication protocol, any wired communication protocol, and/or the like.
  • Information caused to be communicated from the peripheral apparatus may relate to any information, data, input, and/or the like that originates from or is inputted via the peripheral apparatus.
  • a user may press a button on a peripheral apparatus, avoid a button press, manipulate or move the peripheral apparatus, and/or the like. Under such circumstances, it may be desirable to receive a communication of information indicative of the button press, lack of the button press, manipulation of the peripheral apparatus, and/or the like.
  • an apparatus receives communication of information indicative of a keystroke, button press, light condition, environmental condition, user action, and/or the like associated with a peripheral apparatus and caused to be communicated to the apparatus from the peripheral apparatus.
  • FIGURE 2A is a block diagram illustrating apparatus communication according to at least one example embodiment.
  • peripheral apparatus 202 and apparatus 206 communicate directly with one another via communication channel 204.
  • Peripheral 202 may relate to a peripheral apparatus.
  • Apparatus 206 may relate to an electronic apparatus, similarly as described regarding FIGURE 1.
  • apparatus 206 may cause communication with peripheral 202 by way of communication channel 204.
  • Peripheral 202 may receive communication caused by apparatus 206.
  • peripheral 202 may cause communication with apparatus 206 by way of communication channel 204.
  • Apparatus 206 may receive communication cause by peripheral 202.
  • apparatus 206 may cause peripheral 202 to perform an action via causing communication with peripheral 202 via communication channel 204
  • peripheral 202 may cause apparatus 206 to perform an action via causing communication with apparatus 206 via communication channel 204, and/or the like.
  • peripheral 202 may not be present.
  • apparatus 206 may send information indicative of an event notification associated with an event to peripheral 202 via communication channel 204.
  • Peripheral 202 may receive said information from apparatus 206.
  • Peripheral 202 may send information indicative of user action to apparatus 206 via communication channel 204.
  • Apparatus 206 may receive said information from peripheral 202.
  • apparatus 206 may cause rendering of an event notification on peripheral 202 by way of causing communication with peripheral 202 via communication channel 204.
  • FIGURE 2B is a block diagram illustrating apparatus communication according to at least one example embodiment.
  • a user may desire to manage communication and/or rendering of event notifications from a different apparatus. For instance, the user may desire to offload the management of communication and/or rendering, to manage the communication and/or rendering from a remotely accessible different apparatus, to manage the communication and/or rendering to more than one peripheral apparatus, and/or the like.
  • an event notification associated with an event may be communicated to the different apparatus and then communicated from the different apparatus to the apparatus, to the peripheral apparatus, and/or the like, for rendering.
  • peripheral 232 and apparatus 240 communicate with one another by way of apparatus 236 and via communication channel 234 and communication channel 238.
  • Peripheral 232 may relate to a peripheral apparatus.
  • Apparatus 236 may relate to an electronic apparatus, similarly as described regarding FIGURE 1.
  • Apparatus 240 may relate to a server, router, switch, cloud platform, and/or the like.
  • apparatus 240 may cause communication with peripheral 232 by way of apparatus 236.
  • apparatus 240 may cause communication with peripheral 232 indirectly by causing communication with apparatus 236, which in turn causes communication with peripheral 232.
  • Peripheral 232 may receive communication caused by apparatus 240 by way of apparatus 236.
  • peripheral 232 may cause communication with apparatus 240 by way of apparatus 236.
  • Apparatus 240 may receive communication cause by peripheral 232.
  • peripheral 232 may cause communication with apparatus 240 indirectly by causing
  • apparatus 240 may receive communication caused by peripheral 232 by way of apparatus 236.
  • apparatus 240 manage communication between apparatus 236 and peripheral 232.
  • apparatus 236 may request information from apparatus 240 regarding communication with peripheral 232.
  • peripheral 232 may communicate information regarding communication with apparatus 236 to apparatus 240, by way of apparatus 236.
  • apparatus 236 may cause peripheral 232 to perform an action by way of apparatus 240
  • peripheral 232 may cause apparatus 236 to perform an action by way of apparatus 240, and/or the like.
  • peripheral 232 and/or apparatus 240 may not be present.
  • apparatus 236 may send information indicative of an event notification to apparatus 240.
  • Apparatus 236 may send information indicative of peripheral 232 to apparatus 240.
  • apparatus 236 may receive information sent from apparatus 240.
  • Communication between peripheral 232 and apparatus 236 may be similar as described regarding FIGURE 2A.
  • apparatus 236 may cause rendering of an event notification on peripheral 232 by way of causing communication with apparatus 240 via communication channel 238 and/or communication channel 234.
  • FIGURE 2C is a block diagram illustrating apparatus communication according to at least one example embodiment.
  • peripheral 262 In the example of FIGURE 2C, peripheral 262
  • Peripheral 262 and peripheral 263 may communicate with each other either directly or via apparatus 266.
  • the number of peripheral apparatuses may vary. The number of apparatuses may vary. Although only peripheral 262 and peripheral 263 are illustrated, there may be greater or fewer peripheral apparatuses. Similarly, although only apparatus 266 is illustrated, there may be additional apparatuses in communication with the peripheral apparatuses.
  • apparatus 266 communicates information by way of communication channel 264 that differs from information communicated by way of communication channel 265. For example, apparatus 266 may communicate with peripheral apparatus 262 independently of any communication with peripheral apparatus 263.
  • apparatus 266 may cause rendering of an event notification on peripheral 262 and/or peripheral 263 by way of causing communication with peripheral 262 via communication channel 264 and/or causing communication with peripheral 263 via communication channel 265.
  • peripheral 262 and/or peripheral 263 may not be present.
  • FIGURES 3A-3B are block diagrams illustrating filter association according to at least one example embodiment.
  • the examples of FIGURES 3A-3B are merely examples and do not limit the scope of the claims.
  • the number of filters may vary, the number of filter levels may vary, the number of apparatuses per filter may vary, the number of filters per apparatus may vary, filter association may vary, and/or the like.
  • a user may be inundated with event notifications alerting the user, via an apparatus or a peripheral apparatus, to occurrences of a variety of events.
  • filtering of event notifications caused to be rendered is based, at least in part, on a notification filter. For example, it may be desirable to render some event notifications while precluding rendering of other event notifications based, at least in part, on the notification filter.
  • rendering and preclusion of rendering of an event notification to a peripheral apparatus is based, at least in part, on feedback from the apparatus and/or feedback communicated from the peripheral apparatus. For example, it may be desirable to associate information indicative of a user action with an event notification. For example, after an event notification is caused to be rendered, it may be desirable to associate subsequent user actions with the event notification. For example, user actions associated with an event notification may relate to reading event notification content associated with the event notification, acknowledging the event notification, requesting additional information associated with the event notification, accepting the event notification, saving the event notification, opening the event notification, and/or the like. In at least one example embodiment, information indicative of user action associated with the reading of textual event notification content associated with a message event is received by an apparatus.
  • the apparatus may receive information indicative of user action based, at least in part, on user action associated with the apparatus, user action associated with a peripheral apparatus, and/or the like.
  • information indicative of a user requesting the full textual content of a truncated message event notification is received by an apparatus.
  • a user may receive, on an apparatus and/or a peripheral apparatus, a message event notification associated with a truncated version of the original message content.
  • the user may, for example, desire to view the full version of the original message content. In such a situation, it may be desirable to receive information indicative of such user input.
  • action by a user relates to ignoring an event notification, dismissing an event notification, closing the event notification, and/or the like.
  • ignoring an event notification may relate to the user receiving the event notification and not taking any action associated with the event notification, not pressing any buttons in response to the event notification, and/or the like.
  • Dismissing an event notification may relate to the user receiving the event notification and taking action to dismiss the event notification, hide the event notification, cancel the event notification, delete the event notification, reject the event notification, and/or the like.
  • user action associated with an event notification relates to a usefulness indication.
  • the usefulness indication relates to an indication that a user found the event notification useful.
  • the usefulness indication relates to an action by a user that implies that the event notification was useful to the user.
  • information indicative of a usefulness indication associated with an event notification is received from a peripheral apparatus.
  • the usefulness indication may relate to input that identifies that the event notification was useful to the user.
  • the usefulness indication may relate to user action stemming from the event notification, user action caused by the event notification, any action that implies that the event notification was useful to the user, and/or the like.
  • a positive usefulness indication associated with an event notification may indicate that a user found the event notification to be useful.
  • the positive usefulness indication may relate to input associated with reading event notification content associated with the event notification, acknowledging the event notification, requesting additional information associated with the event notification, accepting the event notification, saving the event notification, opening the event notification, and/or the like.
  • a negative usefulness indication associated with the event notification may indicate that the user found the event notification to be not useful.
  • a negative usefulness indication may relate to the user ignoring the event notification, closing the event notification, dismissing the event notification, and/or the like.
  • the apparatus may modify the notification filter based, at least in part, on a positive usefulness indication associated with the event notification. For example, such modification may influence the approval of rendering of the event notification and make such a determination of approval more likely.
  • An indication of approval for example, may relate to information indicating that an event notification should be caused to be rendered.
  • a notification filter comprises at least one criteria indicative of the event notification source, and the indication of approval is based, at least in part, on the criteria.
  • the indication of approval may be based, at least in part, on an indication of an event notification source application associated with the event notification.
  • the indication of approval may be based, at least in part, on the event notification being associated with a particular messaging application.
  • a notification filter may, for example, favor rendering of event notifications associated with the particular messaging application. Event notifications associated with a different event notification source may be less likely to receive approval of rendering.
  • a notification filter may be based, at least in part, on a criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria.
  • the indication of approval may be based, at least in part, on event notification content, event notification context, and/or the like.
  • the indication of approval may be based, at least in part, on the event notification being associated with a particular message sender, message tags, type of message content, and/or the like.
  • a notification filter may, for example, favor rendering of event notifications associated with a particular person. Event notifications associated with a different person may be less likely to receive approval of rendering.
  • Event notification content and event notification context may be similar as described regarding FIGURES 2A-2C.
  • the apparatus may modify the notification filter based, at least in part, on a negative usefulness indication associated with the event notification. For example, such modification may influence the approval of rendering of the event notification to a user and make such a determination of approval less likely.
  • a user may desire to filter the rendering of event notifications to the user's apparatus and/or peripheral apparatus.
  • the user may desire that event notifications are passed through a notification filter before such rendering.
  • an event notification that is passed through a notification filter may be approved for rendering, disapproved for rendering, and/or the like.
  • the user may desire the rendering of event notifications approved for rendering.
  • an apparatus may cause rendering of the event notification based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification.
  • an apparatus may cause rendering of the event notification at a peripheral apparatus based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification at the peripheral apparatus.
  • an apparatus may cause rendering of another event based, at least in part, on a determination that a notification filter indicates approval of rendering of the other event notification.
  • an event notification may be associated with a positive usefulness indication.
  • the filter may be likely to indicate approval of rendering of the other event notification.
  • an apparatus may preclude rendering of the other event notification based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
  • an event notification may be associated with a negative usefulness indication.
  • the filter may be likely to indicate disapproval of rendering of the other event notification.
  • a notification filter indicates approval of rendering of the event notification at a different apparatus.
  • the apparatus may receive from the different apparatus information indicative of the determination that a notification filter indicates approval of rendering of the event notification.
  • a different apparatus may relate to a server, a database, a router, a switch, a cloud platform, and/or the like.
  • a modification of the notification filter causes the notification filter to be more likely to indicate approval of rendering of an event notification to a user.
  • modification of the notification filter may cause the notification filter to be more likely to indicate approval of rendering of other event notifications correlating to the event notification.
  • a modification of a notification filter causes the notification filter to be less likely to indicate approval of rendering of an event notification to a user.
  • modification of the notification filter may cause the notification filter to be less likely to indicate approval of rendering of other event notifications correlating to the event notification.
  • filtering may be based, at least in part, on additional criteria, such as event notification content, event notification context, and/or the like.
  • additional criteria such as event notification content, event notification context, and/or the like.
  • a notification filter be modified by usefulness indications and associated event notifications.
  • an event notification that becomes associated with a usefulness indication may cause modification of the associated notification filter.
  • the notification filter may relate to probabilistic methods, weighted averaging, heuristics, statistical methods, support vector machine (SVM) classifiers, and/or the like.
  • SVM support vector machine
  • Q relates to event notification determination criteria, such as event notification content, event notification context, and/or the like
  • Wj relates to a weight factor associated with the given criteria.
  • Modification of the notification filter based, at least in part, on a usefulness indication associated with the event notification may cause modification to the weight factors associated with the notification filter and criteria. For example, a positive usefulness associated with the event notification may cause an increase in the associated weight factor for the given criteria.
  • approval to render the event notification may be based, at least in part, on the event notification weighted summation exceeding a predetermined threshold.
  • preclusion of rendering the event notification may be based, at least in part, on the event notification weighted average failing to exceeding some predetermined threshold.
  • FIGURE 3A is a block diagram illustrating filter association according to at least one example embodiment.
  • filter 302 and filter 306 may each relate to a notification filter, a multiple apparatus notification filter, and/or the like.
  • Filter 302 is associated with at least apparatus 304 and filter 306 is associated with at least peripheral 308.
  • event notifications intended for rendering at apparatus 304 may be approved for rendering or precluded from rendering at apparatus 304 by way of associated filter 302.
  • event notifications intended for rendering at peripheral 308 may be approved for rendering or precluded from rendering at peripheral 308 by way of associated filter 306.
  • Apparatus 304 may be associated with one or more filters in addition to filter 302.
  • Peripheral 308 may be associated with one or more filters in addition to filter 306.
  • Filter 302 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like, in addition to apparatus 304.
  • Filter 306 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like, in addition to peripheral 308.
  • FIGURE 3B is a block diagram illustrating filter association according to at least one example embodiment.
  • a user may desire the ability to influence which event notifications are caused to be rendered. For example, the user may desire to render more event notifications associated with family members and render less event notifications associated with co-workers. In such an example, the user may influence the notification filter by way of event notification usefulness indications. In certain circumstances, a user may desire usefulness indications to influence multiple notification filters. For example, a user with one or more apparatuses and/or one or more peripheral apparatuses may find it desirable to avoid indicating event notification usefulness on a per apparatus and/or per peripheral apparatus basis.
  • a user may cause modification of a different notification filter based, at least in part, on a usefulness indication.
  • the different notification filter may be associated with a different apparatus, different peripheral apparatus, and/or the like.
  • a user may desire to have a notification filter correlate to a different notification filter.
  • the different notification filter for example, may be associated with a different apparatus and/or a different peripheral apparatus.
  • usefulness indications may cause modification of the notification filter, the different notification filter, both the notification filter and the different notification filter, and/or the like.
  • a notification filter is associated with a single apparatus, a single peripheral apparatus, and/or the like.
  • a notification filter may be associated with one or more apparatus and/or peripheral apparatus.
  • causing modification of a different notification filter may relate to causing modification of a multiple apparatus notification filter.
  • modification of the multiple apparatus notification filter may be based, at least in part, on one or more associated event notification usefulness indications.
  • a notification filter and a different notification filter are based, at least in part, on a multiple apparatus notification filter.
  • the notification filter and the different notification filter may be modified based, at least in part, on the multiple apparatus notification filter via inheritance, propagated modification, and/or the like.
  • filter 352 and filter 356 may each relate to a notification filter, a multiple apparatus notification filter, and/or the like.
  • Filter 360 may relate to a multiple apparatus notification filter.
  • Filter 352 is associated with at least apparatus 354 and filter 356 is associated with at least peripheral 358.
  • event notifications intended for rendering at apparatus 354 may be approved for rendering or precluded from rendering at apparatus 354 by way of associated filter 352.
  • event notifications intended for rendering at peripheral 358 may be approved for rendering or precluded from rendering at peripheral 358 by way of associated filter 356.
  • filter 360 is associated with at least filter 352 and filter 356.
  • Filter 360 may cause modification of filter 352 and/or filter 356 by way of inheritance, propagated modification, and/or the like.
  • Apparatus 354 may be associated with one or more filters in addition to filter 352 and filter 360.
  • Filter 352 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like in addition to apparatus 354.
  • Peripheral 358 may be associated with one or more filters in addition to filter 356 and filter 360.
  • Filter 356 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like in addition to peripheral 358.
  • Filter 360 may be associated with one or more filters in addition to filter 352 and filter 356.
  • FIGURES 4A-4C are illustrations showing peripheral apparatuses according to at least one example embodiment.
  • the examples of FIGURES 4A-4C are merely examples and do not limit the scope of the claims.
  • peripheral apparatus design may vary, type and number of peripheral apparatus output may vary, type and number of peripheral apparatus input may vary, and/or the like.
  • a peripheral apparatus may, for example, relate to a wearable apparatus, an entertainment apparatus, a global positioning system apparatus, a vehicular apparatus, and/or the like.
  • a peripheral apparatus relates to a wearable apparatus.
  • a wearable apparatus may be an apparatus that is easily mountable, carryable, holdable, and/or transportable on one' s person.
  • a wearable apparatus may relate to a ring, a watch, a necklace, a bracelet, an anklet, an armband, a pair of glasses, a pair of sunglasses, a headset, and/or the like.
  • a wearable apparatus may be desirable due to its placement on the body. For example, whereas an electronic apparatus may be hidden in a user's pant pocket, a wearable apparatus may be easily accessible, viewable, noticeable, reachable, and/or the like.
  • FIGURE 4A is an illustration showing a peripheral apparatus according to at least one example embodiment.
  • ring 400 comprises body 402, output 406, and input 408, input 410, and input 412.
  • Output 406 may relate to any output, including a display output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like.
  • Each of input 408, input 410, and input 412 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like.
  • ring 400 may indicate an event notification on display 406.
  • a user may desire that ring 400 only receives specific types of event notifications based upon a particular set of criteria, including time, location, light conditions, event notification content, event notification context, and/or the like. In such situations, the user may indicate positive usefulness indications to the event notifications the user desires to be communicated to the ring 400 and indicate negative usefulness indications to event notifications the user desires to be precluded from communication to the ring 400.
  • FIGURE 4B is an illustration showing a peripheral apparatus according to at least one example embodiment.
  • glasses 430 comprises frame 432, output 436, and input 438, input 440, and input 442.
  • Output 436 may relate to any output, including a display output, a laser output, a projector output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like.
  • either individual lens or both lenses may include display functionality.
  • Each of input 438, input 440, and input 442 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like.
  • FIGURE 4C is an illustration showing a peripheral apparatus according to at least one example embodiment.
  • watch 460 comprises body 462, strap 464, output 466, and input 468, input 470, and input 472.
  • Output 466 may relate to any output, including a display output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like.
  • Each of input 468, input 470, and input 472 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like.
  • FIGURE 5 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • there is a set of operations that corresponds with the activities of FIGURE 5.
  • An apparatus for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations.
  • the apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations.
  • an apparatus, for example electronic apparatus 10 of FIGURE 1 is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 5.
  • the apparatus determines an event notification associated with an event.
  • the determination, the event notification, and the event may be similar as described regarding FIGURES 2A-2C.
  • the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification.
  • the causation, the rendering, the event notification, the determination, the notification filter, the indication, and the approval of rendering may be similar as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
  • the apparatus receives a usefulness indication associated with the event notification.
  • the receipt and the usefulness indication may be similar as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
  • the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication. The causation and the modification may be similar as described regarding FIGURES 3A-3B.
  • FIGURE 6 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • An apparatus, for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations.
  • the apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations.
  • an apparatus, for example electronic apparatus 10 of FIGURE 1 is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 6.
  • an apparatus is in communication with a different apparatus, which may relate to a server. For example, after determining an event notification associated with an event, the apparatus may communicate with the different apparatus information necessary to determine an approval of rendering, and receive from the different apparatus information indicating approval of rendering.
  • the apparatus determines an event notification associated with an event, similarly as described regarding block 502 of FIGURE 5.
  • the apparatus sends information indicative of the event notification, similarly as described regarding FIGURES 2A-2C.
  • the apparatus receives information indicative of the
  • the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
  • the apparatus receives a usefulness indication associated with the event notification, similarly as described regarding block 506 of FIGURE 5.
  • the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication, similarly as described regarding block 508 of FIGURE 5.
  • FIGURE 7 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • there is a set of operations that corresponds with the activities of FIGURE 7.
  • An apparatus for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations.
  • the apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations.
  • an apparatus, for example electronic apparatus 10 of FIGURE 1 is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 7.
  • the apparatus determines an event notification associated with an event, similarly as described regarding block 502 of FIGURE 5.
  • the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
  • the apparatus receives a usefulness indication associated with the event notification, similarly as described regarding block 506 of FIGURE 5.
  • the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication, similarly as described regarding block 508 of FIGURE 5.
  • the apparatus determines another event notification associated with another event, the other event notification correlating with the event notification, similarly as described regarding FIGURES 2A-2C.
  • the apparatus precludes rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification, similarly as described regarding FIGURES 3A-3B.
  • FIGURE 8 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
  • An apparatus for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations.
  • the apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations.
  • an apparatus, for example electronic apparatus 10 of FIGURE 1 is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 8.
  • the apparatus determines an event notification associated with an event and an application, similarly as described regarding FIGURES 2A-2C and FIGURES 3A- 3B.
  • the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
  • the apparatus receives a negative usefulness indication associated with the event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A- 3B.
  • the apparatus cause modification of the notification filter based, at least in part, on the negative usefulness indication, similarly as described regarding FIGURES 3A-3B.
  • the apparatus determines another event notification associated with another event and the application, the other event notification correlating with the event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
  • the apparatus precludes rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification, similarly as described regarding FIGURES 3A-3B.
  • the apparatus determines a different event notification associated with a different event and the application, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
  • the apparatus causes rendering of the different event notification to the user based, at least in part, on a determination that a notification filter indicates approval of rendering of the different event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
  • Embodiments of the invention may be implemented in software, hardware, application logic or a combination of software, hardware, and application logic.
  • the software, application logic and/or hardware may reside on the apparatus, a separate device, or a plurality of separate devices. If desired, part of the software, application logic and/or hardware may reside on the apparatus, part of the software, application logic and/or hardware may reside on a separate device, and part of the software, application logic and/or hardware may reside on a plurality of separate devices.
  • the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
  • block 708 of FIGURE 7 may be performed after block 710 of FIGURE 7.
  • one or more of the above - described functions may be optional or may be combined.
  • block 604 and 606 of FIGURE 6 may be optional and/or combined with block 608 of FIGURE 6.

Landscapes

  • Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Human Computer Interaction (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • General Physics & Mathematics (AREA)
  • Signal Processing (AREA)
  • Computer Hardware Design (AREA)
  • Theoretical Computer Science (AREA)
  • Optics & Photonics (AREA)
  • General Engineering & Computer Science (AREA)
  • Telephone Function (AREA)
  • User Interface Of Digital Computer (AREA)

Abstract

A method comprising determining an event notification associated with an event, causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification to the user, receiving a usefulness indication associated with the event notification, and causing modification of the notification filter based, at least in part, on the usefulness indication is disclosed.

Description

METHOD AND APPARATUS FOR FILTERING OF A NOTIFICATION
TECHNICAL FIELD
The present application relates generally to filtering of a notification.
BACKGROUND
Many users have become dependent on electronic apparatuses to manage various aspects of their lives. For example, many users keep track of many of their appointments, meetings and other events in a calendar program on their electronic apparatus. In addition, many users utilize electronic apparatuses for communication and messaging. Furthermore, many users have a peripheral apparatus or multiple peripheral apparatuses that interact with the electronic apparatus. Such electronic apparatuses and/or peripheral apparatuses may, for example, display notifications.
SUMMARY
Various aspects of examples of the invention are set out in the claims.
One or more embodiments may provide an apparatus, a computer readable medium, a non-transitory computer readable medium, a computer program product, and a method for determining an event notification associated with an event, causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, receiving a usefulness indication associated with the event notification, and causing modification of the notification filter based, at least in part, on the usefulness indication.
One or more embodiments may provide an apparatus, a computer readable medium, a computer program product, and a non-transitory computer readable medium having means for determining an event notification associated with an event, means for causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, means for receiving a usefulness indication associated with the event notification, and means for causing modification of the notification filter based, at least in part, on the usefulness indication.
One or more example embodiments further perform determining that a notification filter indicates approval of rendering of the event notification.
One or more example embodiments further perform sending information indicative of the event notification and receiving information indicative of the determination that a notification filter indicates approval of rendering of the event notification. In at least one example embodiment, the notification filter comprises at least one criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria.
In at least one example embodiment, the notification filter comprises at least one criteria indicative of the event notification source, and the indication of approval is based, at least in part, on the criteria.
In at least one example embodiment, the indication of approval comprises at least one of event notification content or event notification context.
In at least one example embodiment, the event notification is associated with a message and the event notification content is associated with at least one of a message sender, a message title, a message body, or a message header.
In at least one example embodiment, the event notification context indicates at least one of weather condition, date, time of day, temperature, light conditions, environmental condition, or location of the apparatus.
In at least one example embodiment, the event notification is associated with a call and the event notification content is associated with at least one of a caller or a call type.
In at least one example embodiment, the call type relates to at least one of a voice call, video call, packet call, conference call, or telephony call.
In at least one example embodiment, the event relates to at least one of a call, message, alarm indication, calendar indication, power indication, signal strength indication, or location indication.
In at least one example embodiment, the notification filter relates to at least one of heuristics or statistical methods.
In at least one example embodiment, the usefulness indication relates to an indication that a user found the event notification useful.
In at least one example embodiment, the usefulness indication relates to input that identifies that the event notification was useful to a user.
In at least one example embodiment, the usefulness indication relates to an action by a user that implies that the event notification was useful to the user.
In at least one example embodiment, the action by a user relates to at least one of reading the event notification, acknowledging the event notification, or requesting additional information associated with the event notification.
In at least one example embodiment, the action by a user relates to at least one of ignoring the event notification or dismissing the event notification.
In at least one example embodiment, the modification of the notification filter causes the notification filter to be more likely to indicate approval of rendering of the event notification. In at least one example embodiment, the modification of the notification filter causes the notification filter to be less likely to indicate approval of rendering of the event notification.
One or more example embodiments further perform determining another event notification associated with another event, the other event notification correlating with the event notification and precluding rendering of the other event notification to a user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
In at least one example embodiment, the peripheral apparatus relates to a wearable apparatus.
One or more example embodiments further perform causing modification of a different notification filter based, at least in part, on the usefulness indication, the different notification filter being associated with a different apparatus.
In at least one example embodiment, wherein causing modification of the different notification filter comprises causing modification of a multiple apparatus notification filter.
In at least one example embodiment, wherein the notification filter and the different notification filter are based, at least in part, on the multiple apparatus notification filter. BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of embodiments of the invention, reference is now made to the following descriptions taken in connection with the accompanying drawings in which:
FIGURE 1 is a block diagram showing an apparatus according to an example embodiment;
FIGURES 2A-2C are block diagrams illustrating apparatus communication according to at least one example embodiment.
FIGURES 3A-3B are block diagrams illustrating filter association according to at least one example embodiment.
FIGURES 4A-4C are illustrations showing peripheral apparatuses according to at least one example embodiment.
FIGURE 5 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
FIGURE 6 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
FIGURE 7 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment. FIGURE 8 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment.
DETAILED DESCRIPTION OF THE DRAWINGS
An embodiment of the invention and its potential advantages are understood by referring to FIGURES 1 through 8 of the drawings.
Some embodiments will now be described more fully hereinafter with reference to the accompanying drawings, in which some, but not all, embodiments are shown. Various embodiments of the invention may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein; rather, these embodiments are provided so that this disclosure will satisfy applicable legal requirements. Like reference numerals refer to like elements throughout. As used herein, the terms "data," "content," "information," and similar terms may be used interchangeably to refer to data capable of being transmitted, received and/or stored in accordance with embodiments of the present invention. Thus, use of any such terms should not be taken to limit the spirit and scope of embodiments of the present invention.
Additionally, as used herein, the term 'circuitry' refers to (a) hardware-only circuit implementations (e.g., implementations in analog circuitry and/or digital circuitry); (b) combinations of circuits and computer program product(s) comprising software and/or firmware instructions stored on one or more computer readable memories that work together to cause an apparatus to perform one or more functions described herein; and (c) circuits, such as, for example, a microprocessor s) or a portion of a microprocessor(s), that require software or firmware for operation even if the software or firmware is not physically present. This definition of 'circuitry' applies to all uses of this term herein, including in any claims. As a further example, as used herein, the term 'circuitry' also includes an implementation comprising one or more processors and/or portion(s) thereof and accompanying software and/or firmware. As another example, the term 'circuitry' as used herein also includes, for example, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network apparatus, other network apparatus, and/or other computing apparatus.
As defined herein, a "non-transitory computer-readable medium," which refers to a physical medium (e.g., volatile or non-volatile memory device), can be differentiated from a "transitory computer-readable medium," which refers to an electromagnetic signal.
FIGURE 1 is a block diagram showing an apparatus, such as an electronic apparatus 10, according to at least one example embodiment. It should be understood, however, that an electronic apparatus as illustrated and hereinafter described is merely illustrative of an electronic apparatus that could benefit from embodiments of the invention and, therefore, should not be taken to limit the scope of the invention. While electronic apparatus 10 is illustrated and will be hereinafter described for purposes of example, other types of electronic apparatuses may readily employ embodiments of the invention. Electronic apparatus 10 may be a personal digital assistant (PDAs), a pager, a mobile computer, a desktop computer, a television, a gaming apparatus, a laptop computer, a media player, a camera, a video recorder, a mobile phone, a global positioning system (GPS) apparatus, and/or any other types of electronic systems. Moreover, the apparatus of at least one example embodiment need not be the entire electronic apparatus, but may be a component or group of components of the electronic apparatus in other example embodiments.
Furthermore, apparatuses may readily employ embodiments of the invention regardless of their intent to provide mobility. In this regard, even though embodiments of the invention may be described in conjunction with mobile applications, it should be understood that embodiments of the invention may be utilized in conjunction with a variety of other applications, both in the mobile communications industries and outside of the mobile communications industries.
In at least one example embodiment, electronic apparatus 10 comprises processor 11 and memory 12. Processor 11 may be any type of processor, controller, embedded controller, processor core, and/or the like. In at least one example embodiment, processor 11 utilizes computer program code to cause an apparatus to perform one or more actions. Memory 12 may comprise volatile memory, such as volatile Random Access Memory (RAM) including a cache area for the temporary storage of data and/or other memory, for example, non- volatile memory, which may be embedded and/or may be removable. The non- volatile memory may comprise an EEPROM, flash memory and/or the like. Memory 12 may store any of a number of pieces of information, and data. The information and data may be used by the electronic apparatus 10 to implement one or more functions of the electronic apparatus 10, such as the functions described herein. In at least one example embodiment, memory 12 includes computer program code such that the memory and the computer program code are configured to, working with the processor, cause the apparatus to perform one or more actions described herein.
The electronic apparatus 10 may further comprise a communication device 15. In at least one example embodiment, communication device 15 comprises an antenna, (or multiple antennae), a wired connector, and/or the like in operable communication with a transmitter and/or a receiver. In at least one example embodiment, processor 11 provides signals to a transmitter and/or receives signals from a receiver. The signals may comprise signaling information in accordance with a communications interface standard, user speech, received data, user generated data, and/or the like. Communication device 15 may operate with one or more air interface standards, communication protocols, modulation types, and access types. By way of illustration, the electronic communication device 15 may operate in accordance with second- generation (2G) wireless communication protocols IS -136 (time division multiple access (TDMA)), Global System for Mobile communications (GSM), and IS-95 (code division multiple access (CDMA)), with third-generation (3G) wireless communication protocols, such as Universal Mobile Telecommunications System (UMTS), CDMA2000, wideband CDMA (WCDMA) and time division-synchronous CDMA (TD-SCDMA), and/or with fourth-generation (4G) wireless communication protocols, wireless networking protocols, such as 802.11, short- range wireless protocols, such as Bluetooth, and/or the like. Communication device 15 may operate in accordance with wireline protocols, such as Ethernet, digital subscriber line (DSL), asynchronous transfer mode (ATM), and/or the like.
Processor 11 may comprise means, such as circuitry, for implementing audio, video, communication, navigation, logic functions, and/or the like, as well as for implementing embodiments of the invention including, for example, one or more of the functions described herein. For example, processor 11 may comprise means, such as a digital signal processor device, a microprocessor device, various analog to digital converters, digital to analog converters, processing circuitry and other support circuits, for performing various functions including, for example, one or more of the functions described herein. The apparatus may perform control and signal processing functions of the electronic apparatus 10 among these devices according to their respective capabilities. The processor 11 thus may comprise the functionality to encode and interleave message and data prior to modulation and transmission. The processor 1 may additionally comprise an internal voice coder, and may comprise an internal data modem.
Further, the processor 11 may comprise functionality to operate one or more software programs, which may be stored in memory and which may, among other things, cause the processor 11 to implement at least one embodiment including, for example, one or more of the functions described herein. For example, the processor 11 may operate a connectivity program, such as a conventional internet browser. The connectivity program may allow the electronic apparatus 10 to transmit and receive internet content, such as location-based content and/or other web page content, according to a Transmission Control Protocol (TCP), Internet Protocol (IP), User Datagram Protocol (UDP), Internet Message Access Protocol (IMAP), Post Office Protocol (POP), Simple Mail Transfer Protocol (SMTP), Wireless Application Protocol (WAP), Hypertext Transfer Protocol (HTTP), and/or the like, for example.
The electronic apparatus 10 may comprise a user interface for providing output and/or receiving input. The electronic apparatus 10 may comprise an output device 14. Output device 14 may comprise an audio output device, such as a ringer, an earphone, a speaker, and/or the like. Output device 14 may comprise a tactile output device, such as a vibration transducer, an electronically deformable surface, an electronically deformable structure, and/or the like. Output device 14 may comprise a visual output device, such as a display, a light, and/or the like. In at least one example embodiment, the apparatus causes display of information, the causation of display may comprise displaying the information on a display comprised by the apparatus, sending the information to a separate apparatus that comprises a display, and/or the like. The electronic apparatus may comprise an input device 13. Input device 13 may comprise a light sensor, a proximity sensor, a microphone, a touch sensor, a force sensor, a button, a keypad, a motion sensor, a magnetic field sensor, a camera, and/or the like. A touch sensor and a display may be characterized as a touch display. In an embodiment comprising a touch display, the touch display may be configured to receive input from a single point of contact, multiple points of contact, and/or the like. In such an embodiment, the touch display and/or the processor may determine input based, at least in part, on position, motion, speed, contact area, and/or the like. In at least one example embodiment, the apparatus receives an indication of an input. The apparatus may receive the indication from a sensor, a driver, a separate apparatus, and/or the like. The information indicative of the input may relate to information that conveys information indicative of the input, indicative of an aspect of the input indicative of occurrence of the input, and/or the like.
The electronic apparatus 10 may include any of a variety of touch displays including those that are configured to enable touch recognition by any of resistive, capacitive, infrared, strain gauge, surface wave, optical imaging, dispersive signal technology, acoustic pulse recognition or other techniques, and to then provide signals indicative of the location and other parameters associated with the touch. Additionally, the touch display may be configured to receive an indication of an input in the form of a touch event which may be defined as an actual physical contact between a selection object (e.g., a finger, stylus, pen, pencil, or other pointing device) and the touch display. Alternatively, a touch event may be defined as bringing the selection object in proximity to the touch display, hovering over a displayed object or approaching an object within a predefined distance, even though physical contact is not made with the touch display. As such, a touch input may comprise any input that is detected by a touch display including touch events that involve actual physical contact and touch events that do not involve physical contact but that are otherwise detected by the touch display, such as a result of the proximity of the selection object to the touch display. A touch display may be capable of receiving information associated with force applied to the touch screen in relation to the touch input. For example, the touch screen may differentiate between a heavy press touch input and a light press touch input. In at least one example embodiment, a display may display two- dimensional information, three-dimensional information and/or the like.
In embodiments including a keypad, the keypad may comprise numeric (for example, 0-9) keys, symbol keys (for example, #, *), alphabetic keys, and/or the like for operating the electronic apparatus 10. For example, the keypad may comprise a conventional QWERTY keypad arrangement. The keypad may also comprise various soft keys with associated functions. In addition, or alternatively, the electronic apparatus 10 may comprise an interface device such as a joystick or other user input interface. Input device 13 may comprise a media capturing element. The media capturing element may be any means for capturing an image, video, and/or audio for storage, display or transmission. For example, in at least one example embodiment in which the media capturing element is a camera module, the camera module may comprise a digital camera which may form a digital image file from a captured image. As such, the camera module may comprise hardware, such as a lens or other optical component(s), and/or software necessary for creating a digital image file from a captured image. Alternatively, the camera module may comprise only the hardware for viewing an image, while a memory device of the electronic apparatus 10 stores instructions for execution by the processor 11 in the form of software for creating a digital image file from a captured image. In at least one example embodiment, the camera module may further comprise a processing element such as a co-processor that assists the processor 11 in processing image data and an encoder and/or decoder for compressing and/or decompressing image data. The encoder and/or decoder may encode and/or decode according to a standard format, for example, a Joint Photographic Experts Group (JPEG) standard format.
FIGURES 2A-2C are block diagrams illustrating apparatus communication according to at least one example embodiment. The examples of FIGURES 2A-2C are merely examples and do not limit the scope of the claims. For example, the number of apparatuses may vary, the number of peripheral apparatuses may vary, the type of communication between and among apparatuses and peripheral apparatuses may vary, the routing of communication between and among apparatuses and peripheral apparatuses may vary, and/or the like.
As electronic apparatuses have become more prolific, there has been an increasing desire for users to utilize multiple electronic apparatuses collaboratively. For example, a user may have an apparatus that is viewed as a primary apparatus. Such an apparatus may relate to, for example, a personal digital assistant (PDAs), a pager, a mobile computer, a desktop computer, a television, a gaming apparatus, a laptop computer, a media player, a camera, a video recorder, a mobile phone, a global positioning system (GPS) apparatus, and/or any other types of electronic apparatuses. Additionally, for example, a user may have one or more peripheral apparatuses that operate in conjunction with and in communication with the user's apparatus. Such a peripheral apparatus may relate to, for example, a watch, a ring, a bracelet, a headset, a pair of glasses, a second electronic apparatus, a global positioning system apparatus, an entertainment apparatus, and/or similar peripheral apparatuses. A peripheral apparatus may be similar as described regarding FIGURES 4A-4C.
From time to time, miscellaneous events may occur. In some circumstances, the user may find it desirable to be alerted of the occurrence of an event via one or more apparatuses and/or peripheral apparatuses. In at least one example embodiment, an event relates to a call, message, notification, update, alarm, calendar occurrence, power, signal strength, location, and/or the like. For example, receipt of an incoming phone call on an apparatus may relate to a call event. Receipt of a social network message, for example, may relate to a message event. In at least one example embodiment, reaching twenty-percent battery capacity may relate to a power event.
In certain circumstances, it may be desirable to associate an event with an event notification. For example, a user may be alerted as to an occurrence of an event by way of an associated event notification. In at least one example embodiment, an apparatus determines an event notification associated with an event. An event notification may, for example, relate to a notification dialog, a message dialog, a data feed entry, an auditory alert, a visual alert, and/or the like. In at one or more example embodiments, an event notification is associated with an event and/or various attributes associated with the event. In one or more example embodiments, an event notification may be associated with pushed data, streamed data, pulled data, and/or the like. The event notification, for example, may be associated with receipt of data pushed to the apparatus in a publish-subscribe model. In another example, an event notification may be associated with receipt of streamed data from a data feed. In such an example, the streamed data may relate to a single data entry of a stream of data entries. In another example, an event notification may be associated with receipt of data requested in a pull-based data system. In at least one example embodiment, an event notification associated with an event comprises event notification content, event notification context, and/or the like. For example, an event notification may be associated with a message and event notification content may relate to a message sender, a message title, a message body, a message header, and/or the like. In one or more example embodiments, the message may relate to a text message, an instant message, a Twitter message, a Facebook message, and/or the like. In at least one example embodiment, an event notification may be associated with a call and event notification content may relate to a caller, a call source, a call type, and/or the like. In at least one example embodiment, an event notification may be associated with a sensor event and event notification content may relate to a sensor reading. For example, a sensor may relate to a temperature sensor, an occupancy sensor, a motion sensor, a light sensor, and/or the like. A sensor event, for example, may relate to temperature conditions meeting some predetermined criteria, occupancy of a room, motion at an entrance door, lighting conditions meeting some predetermined criteria, and/or the like. In one or more example embodiments, the call type may relate to a voice call, a video call, a packet call, a conference call, a telephonic call, and/or the like. In at least one example embodiment, an event notification context relates to weather condition, date, time of day, temperature, light conditions, environmental condition, location of the peripheral apparatus, and/or the like. For example, event notification context may relate to the context surrounding the occurrence of an event. In certain circumstances, more than one event may occur. In such circumstances, it may be desirable to associate each event with an event notification. In some circumstances, the two events may be associated with two event notifications. For example, two similar events may be associated with two correlating event notifications. In one or more example embodiments, an apparatus determines another event notification associated with another event in circumstances where the other event notification correlates with an event notification.
In certain circumstances, a user may find it desirable to be alerted of the occurrence of an event associated with an apparatus via an event notification. For example, the user may find it desirable to receive the event notification by way of the user' s apparatus. For example, information indicative of the event notification may be displayed. Alternatively and/or additionally, the user may find it desirable to receive the event notification by way of a peripheral apparatus. For example, in certain circumstances, it may be desirable to alert a user of an incoming call on an apparatus via a peripheral apparatus. In at least one example embodiment, an apparatus may cause rendering of an event notification. In at least one example embodiment, an apparatus may cause rendering of an event notification on a peripheral apparatus. Causing rendering of an event notification on a peripheral apparatus may relate to directly communicating the event notification to the peripheral apparatus for rendering on the peripheral apparatus, directing another apparatus to communicate the event notification to the peripheral apparatus for rendering on the peripheral apparatus, directing the peripheral apparatus to receive
communication of the event notification for rendering on the peripheral apparatus, and/or the like. In one or more example embodiments, the apparatus and the peripheral apparatus communicate via a communication channel. A communication channel, for example, may relate to communication via near field communication, inductive communication, electric field communication, Bluetooth communication, infrared communication, local area network communication, wireless local area network communication, wired connection communication, any wireless communication protocol, any wired communication protocol, and/or the like.
In certain circumstances, it may be desirable to receive communication sent from a peripheral apparatus. For example, it may be desirable to receive communication of information caused to be communicated from the peripheral apparatus. Information caused to be communicated from the peripheral apparatus may relate to any information, data, input, and/or the like that originates from or is inputted via the peripheral apparatus. In one or more example embodiments, a user may press a button on a peripheral apparatus, avoid a button press, manipulate or move the peripheral apparatus, and/or the like. Under such circumstances, it may be desirable to receive a communication of information indicative of the button press, lack of the button press, manipulation of the peripheral apparatus, and/or the like. In one or more example embodiments, an apparatus receives communication of information indicative of a keystroke, button press, light condition, environmental condition, user action, and/or the like associated with a peripheral apparatus and caused to be communicated to the apparatus from the peripheral apparatus. FIGURE 2A is a block diagram illustrating apparatus communication according to at least one example embodiment. In the example of FIGURE 2A, peripheral apparatus 202 and apparatus 206 communicate directly with one another via communication channel 204. Peripheral 202 may relate to a peripheral apparatus. Apparatus 206 may relate to an electronic apparatus, similarly as described regarding FIGURE 1. In the example of FIGURE 2 A, apparatus 206 may cause communication with peripheral 202 by way of communication channel 204. Peripheral 202 may receive communication caused by apparatus 206. In the example of FIGURE 2A, peripheral 202 may cause communication with apparatus 206 by way of communication channel 204. Apparatus 206 may receive communication cause by peripheral 202. In the example of FIGURE 2A, apparatus 206 may cause peripheral 202 to perform an action via causing communication with peripheral 202 via communication channel 204, peripheral 202 may cause apparatus 206 to perform an action via causing communication with apparatus 206 via communication channel 204, and/or the like. In the example of FIGURE 2A, peripheral 202 may not be present.
In the example of FIGURE 2A, apparatus 206 may send information indicative of an event notification associated with an event to peripheral 202 via communication channel 204. Peripheral 202 may receive said information from apparatus 206. Peripheral 202 may send information indicative of user action to apparatus 206 via communication channel 204. Apparatus 206 may receive said information from peripheral 202. In the example of FIGURE 2A, apparatus 206 may cause rendering of an event notification on peripheral 202 by way of causing communication with peripheral 202 via communication channel 204.
FIGURE 2B is a block diagram illustrating apparatus communication according to at least one example embodiment. In certain circumstances, a user may desire to manage communication and/or rendering of event notifications from a different apparatus. For instance, the user may desire to offload the management of communication and/or rendering, to manage the communication and/or rendering from a remotely accessible different apparatus, to manage the communication and/or rendering to more than one peripheral apparatus, and/or the like. In such an example, an event notification associated with an event may be communicated to the different apparatus and then communicated from the different apparatus to the apparatus, to the peripheral apparatus, and/or the like, for rendering. In certain circumstances, it may be desirable to manage communication between apparatus 236 and peripheral 232 from a different apparatus. In the example of FIGURE 2B, peripheral 232 and apparatus 240 communicate with one another by way of apparatus 236 and via communication channel 234 and communication channel 238. Peripheral 232 may relate to a peripheral apparatus. Apparatus 236 may relate to an electronic apparatus, similarly as described regarding FIGURE 1. Apparatus 240 may relate to a server, router, switch, cloud platform, and/or the like. In the example of FIGURE 2B, apparatus 240 may cause communication with peripheral 232 by way of apparatus 236. For example, apparatus 240 may cause communication with peripheral 232 indirectly by causing communication with apparatus 236, which in turn causes communication with peripheral 232. Peripheral 232 may receive communication caused by apparatus 240 by way of apparatus 236. In the example of FIGURE 2B, peripheral 232 may cause communication with apparatus 240 by way of apparatus 236. Apparatus 240 may receive communication cause by peripheral 232. For example, peripheral 232 may cause communication with apparatus 240 indirectly by causing
communication with apparatus 236, which in turn causes communication with apparatus 240. Apparatus 240 may receive communication caused by peripheral 232 by way of apparatus 236. In the example of FIGURE 2B, apparatus 240 manage communication between apparatus 236 and peripheral 232. For example, apparatus 236 may request information from apparatus 240 regarding communication with peripheral 232. Similarly, peripheral 232 may communicate information regarding communication with apparatus 236 to apparatus 240, by way of apparatus 236. In the example of FIGURE 2B, apparatus 236 may cause peripheral 232 to perform an action by way of apparatus 240, peripheral 232 may cause apparatus 236 to perform an action by way of apparatus 240, and/or the like. In the example of FIGURE 2B, peripheral 232 and/or apparatus 240 may not be present.
In the example of FIGURE 2B, apparatus 236 may send information indicative of an event notification to apparatus 240. Apparatus 236 may send information indicative of peripheral 232 to apparatus 240. In the example of FIGURE 2B, apparatus 236 may receive information sent from apparatus 240. Communication between peripheral 232 and apparatus 236 may be similar as described regarding FIGURE 2A. In the example of FIGURE 2B, apparatus 236 may cause rendering of an event notification on peripheral 232 by way of causing communication with apparatus 240 via communication channel 238 and/or communication channel 234.
FIGURE 2C is a block diagram illustrating apparatus communication according to at least one example embodiment. In the example of FIGURE 2C, peripheral 262
communicates directly with apparatus 266 via communication channel 264 and peripheral 263 communicates directly with apparatus 266 via communication channel 265. Peripheral 262 and peripheral 263 may communicate with each other either directly or via apparatus 266. In the example of FIGURE 2C, the number of peripheral apparatuses may vary. The number of apparatuses may vary. Although only peripheral 262 and peripheral 263 are illustrated, there may be greater or fewer peripheral apparatuses. Similarly, although only apparatus 266 is illustrated, there may be additional apparatuses in communication with the peripheral apparatuses. In at least one example embodiment, apparatus 266 communicates information by way of communication channel 264 that differs from information communicated by way of communication channel 265. For example, apparatus 266 may communicate with peripheral apparatus 262 independently of any communication with peripheral apparatus 263. In the example of FIGURE 2C, apparatus 266 may cause rendering of an event notification on peripheral 262 and/or peripheral 263 by way of causing communication with peripheral 262 via communication channel 264 and/or causing communication with peripheral 263 via communication channel 265. In the example of FIGURE 2C, peripheral 262 and/or peripheral 263 may not be present.
FIGURES 3A-3B are block diagrams illustrating filter association according to at least one example embodiment. The examples of FIGURES 3A-3B are merely examples and do not limit the scope of the claims. For example, the number of filters may vary, the number of filter levels may vary, the number of apparatuses per filter may vary, the number of filters per apparatus may vary, filter association may vary, and/or the like.
From time to time, a user may be inundated with event notifications alerting the user, via an apparatus or a peripheral apparatus, to occurrences of a variety of events. In some circumstances, it may be desirable to allow filtering of event notifications. In at least one example embodiment, filtering of event notifications caused to be rendered is based, at least in part, on a notification filter. For example, it may be desirable to render some event notifications while precluding rendering of other event notifications based, at least in part, on the notification filter.
In one or more example embodiments, rendering and preclusion of rendering of an event notification to a peripheral apparatus is based, at least in part, on feedback from the apparatus and/or feedback communicated from the peripheral apparatus. For example, it may be desirable to associate information indicative of a user action with an event notification. For example, after an event notification is caused to be rendered, it may be desirable to associate subsequent user actions with the event notification. For example, user actions associated with an event notification may relate to reading event notification content associated with the event notification, acknowledging the event notification, requesting additional information associated with the event notification, accepting the event notification, saving the event notification, opening the event notification, and/or the like. In at least one example embodiment, information indicative of user action associated with the reading of textual event notification content associated with a message event is received by an apparatus. For example, the apparatus may receive information indicative of user action based, at least in part, on user action associated with the apparatus, user action associated with a peripheral apparatus, and/or the like. In one or more example embodiments, information indicative of a user requesting the full textual content of a truncated message event notification is received by an apparatus. For example, a user may receive, on an apparatus and/or a peripheral apparatus, a message event notification associated with a truncated version of the original message content. The user may, for example, desire to view the full version of the original message content. In such a situation, it may be desirable to receive information indicative of such user input. In one or more example embodiments, action by a user relates to ignoring an event notification, dismissing an event notification, closing the event notification, and/or the like. For example, ignoring an event notification may relate to the user receiving the event notification and not taking any action associated with the event notification, not pressing any buttons in response to the event notification, and/or the like.
Dismissing an event notification may relate to the user receiving the event notification and taking action to dismiss the event notification, hide the event notification, cancel the event notification, delete the event notification, reject the event notification, and/or the like.
In at least one example embodiment, user action associated with an event notification relates to a usefulness indication. In one or more example embodiments, the usefulness indication relates to an indication that a user found the event notification useful. In one or more example embodiments, the usefulness indication relates to an action by a user that implies that the event notification was useful to the user. In at least one example embodiment, information indicative of a usefulness indication associated with an event notification is received from a peripheral apparatus. For example, the usefulness indication may relate to input that identifies that the event notification was useful to the user. In another example, the usefulness indication may relate to user action stemming from the event notification, user action caused by the event notification, any action that implies that the event notification was useful to the user, and/or the like.
In at least one example embodiment, a positive usefulness indication associated with an event notification may indicate that a user found the event notification to be useful. For example, the positive usefulness indication may relate to input associated with reading event notification content associated with the event notification, acknowledging the event notification, requesting additional information associated with the event notification, accepting the event notification, saving the event notification, opening the event notification, and/or the like. A negative usefulness indication associated with the event notification, on the other hand, may indicate that the user found the event notification to be not useful. A negative usefulness indication may relate to the user ignoring the event notification, closing the event notification, dismissing the event notification, and/or the like.
In certain circumstances, it may be desirable to associate event notification usefulness indications with a notification filter. For example, it may be desirable to cause rendering of an event notification associated with an event based, and least in part, on an indication of approval of rendering of the event notification to a user. In certain circumstances, the apparatus may modify the notification filter based, at least in part, on a positive usefulness indication associated with the event notification. For example, such modification may influence the approval of rendering of the event notification and make such a determination of approval more likely. In one or more example embodiments, it may be desirable to determine that a notification filter indicates approval of rendering of an event notification. An indication of approval, for example, may relate to information indicating that an event notification should be caused to be rendered. In at least one example embodiment, a notification filter comprises at least one criteria indicative of the event notification source, and the indication of approval is based, at least in part, on the criteria. For example, the indication of approval may be based, at least in part, on an indication of an event notification source application associated with the event notification. In such an example, the indication of approval may be based, at least in part, on the event notification being associated with a particular messaging application. A notification filter may, for example, favor rendering of event notifications associated with the particular messaging application. Event notifications associated with a different event notification source may be less likely to receive approval of rendering. In at least one example embodiment, a notification filter may be based, at least in part, on a criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria. For example, the indication of approval may be based, at least in part, on event notification content, event notification context, and/or the like. In such an example, the indication of approval may be based, at least in part, on the event notification being associated with a particular message sender, message tags, type of message content, and/or the like. A notification filter may, for example, favor rendering of event notifications associated with a particular person. Event notifications associated with a different person may be less likely to receive approval of rendering. Event notification content and event notification context may be similar as described regarding FIGURES 2A-2C.
Similarly, for example, it may be desirable to preclude rendering of an event notification associated with an event based, and least in part, on a disapproval of rendering of the event notification to a user. In certain circumstances, the apparatus may modify the notification filter based, at least in part, on a negative usefulness indication associated with the event notification. For example, such modification may influence the approval of rendering of the event notification to a user and make such a determination of approval less likely.
In certain circumstances, a user may desire to filter the rendering of event notifications to the user's apparatus and/or peripheral apparatus. In such circumstances, the user may desire that event notifications are passed through a notification filter before such rendering. For example, an event notification that is passed through a notification filter may be approved for rendering, disapproved for rendering, and/or the like. In such an example, the user may desire the rendering of event notifications approved for rendering. In at least one example embodiment, an apparatus may cause rendering of the event notification based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification. In at least one example embodiment, an apparatus may cause rendering of the event notification at a peripheral apparatus based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification at the peripheral apparatus. Similarly, in at least one example embodiment, an apparatus may cause rendering of another event based, at least in part, on a determination that a notification filter indicates approval of rendering of the other event notification. For example, an event notification may be associated with a positive usefulness indication. In this example, if another event notification correlating with the event notification is passed through a notification filter, the filter may be likely to indicate approval of rendering of the other event notification. Conversely, an apparatus may preclude rendering of the other event notification based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification. For example, an event notification may be associated with a negative usefulness indication. In this example, if another event notification correlating with the event notification is passed through a notification filter, the filter may be likely to indicate disapproval of rendering of the other event notification. In certain
circumstances, it may be desirable to determine at the apparatus that a notification filter indicates approval of rendering of the event notification at a different apparatus. Under such
circumstances, the apparatus may receive from the different apparatus information indicative of the determination that a notification filter indicates approval of rendering of the event notification. For example, a different apparatus may relate to a server, a database, a router, a switch, a cloud platform, and/or the like.
In certain circumstances, it may be desirable to modify a notification filter based, at least in part, on an associated usefulness indication. For example, based upon the usefulness indication associated with an event notification, the apparatus may cause modification of the notification filter. In at least one example embodiment, a modification of the notification filter causes the notification filter to be more likely to indicate approval of rendering of an event notification to a user. For example, based, at least in part, on a positive usefulness indication associated with the event notification, modification of the notification filter may cause the notification filter to be more likely to indicate approval of rendering of other event notifications correlating to the event notification. Conversely, in at least one example embodiment, a modification of a notification filter causes the notification filter to be less likely to indicate approval of rendering of an event notification to a user. For example, based, at least in part, on a negative usefulness indication associated with the event notification, modification of the notification filter may cause the notification filter to be less likely to indicate approval of rendering of other event notifications correlating to the event notification.
In certain circumstances, it may be desirable to filter event notifications based on a variety of criteria. For example, rather than filtering event notifications based purely on the source of the event notification, filtering may be based, at least in part, on additional criteria, such as event notification content, event notification context, and/or the like. For example, over time, a notification filter be modified by usefulness indications and associated event notifications. In this example, an event notification that becomes associated with a usefulness indication may cause modification of the associated notification filter. In determining whether a subsequent event notification should be approved for rendering to a user or disapproved for rendering to a user, the notification filter may relate to probabilistic methods, weighted averaging, heuristics, statistical methods, support vector machine (SVM) classifiers, and/or the like. For example, approval of rendering of an event notification to a user may be based, at least in part, on the following:
Approval = [∑f=0 Wj Q] ≥ Threshold, where the notification filter =
Figure imgf000018_0001
In the example equation above, Q relates to event notification determination criteria, such as event notification content, event notification context, and/or the like, and Wj relates to a weight factor associated with the given criteria. Modification of the notification filter based, at least in part, on a usefulness indication associated with the event notification may cause modification to the weight factors associated with the notification filter and criteria. For example, a positive usefulness associated with the event notification may cause an increase in the associated weight factor for the given criteria. In at least one example embodiment, approval to render the event notification may be based, at least in part, on the event notification weighted summation exceeding a predetermined threshold. In at least one example embodiment, preclusion of rendering the event notification may be based, at least in part, on the event notification weighted average failing to exceeding some predetermined threshold.
FIGURE 3A is a block diagram illustrating filter association according to at least one example embodiment. In the example of FIGURE 3A, filter 302 and filter 306 may each relate to a notification filter, a multiple apparatus notification filter, and/or the like. Filter 302 is associated with at least apparatus 304 and filter 306 is associated with at least peripheral 308. In the example of FIGURE 3A, event notifications intended for rendering at apparatus 304 may be approved for rendering or precluded from rendering at apparatus 304 by way of associated filter 302. Similarly, event notifications intended for rendering at peripheral 308 may be approved for rendering or precluded from rendering at peripheral 308 by way of associated filter 306. Apparatus 304 may be associated with one or more filters in addition to filter 302.
Peripheral 308 may be associated with one or more filters in addition to filter 306. Filter 302 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like, in addition to apparatus 304. Filter 306 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like, in addition to peripheral 308.
FIGURE 3B is a block diagram illustrating filter association according to at least one example embodiment. In certain circumstances, a user may desire the ability to influence which event notifications are caused to be rendered. For example, the user may desire to render more event notifications associated with family members and render less event notifications associated with co-workers. In such an example, the user may influence the notification filter by way of event notification usefulness indications. In certain circumstances, a user may desire usefulness indications to influence multiple notification filters. For example, a user with one or more apparatuses and/or one or more peripheral apparatuses may find it desirable to avoid indicating event notification usefulness on a per apparatus and/or per peripheral apparatus basis. In at least one example embodiment, a user may cause modification of a different notification filter based, at least in part, on a usefulness indication. In such an example, the different notification filter may be associated with a different apparatus, different peripheral apparatus, and/or the like. For example, a user may desire to have a notification filter correlate to a different notification filter. The different notification filter, for example, may be associated with a different apparatus and/or a different peripheral apparatus. In such an example, usefulness indications may cause modification of the notification filter, the different notification filter, both the notification filter and the different notification filter, and/or the like. In one or more example embodiments, a notification filter is associated with a single apparatus, a single peripheral apparatus, and/or the like. In certain circumstances, it may be desirable to associate a notification filter with more than one apparatus and/or peripheral apparatus. For example, a multiple apparatus notification filter may be associated with one or more apparatus and/or peripheral apparatus. In at least one example embodiment, causing modification of a different notification filter may relate to causing modification of a multiple apparatus notification filter. For example, modification of the multiple apparatus notification filter may be based, at least in part, on one or more associated event notification usefulness indications. In at least one example embodiment, a notification filter and a different notification filter are based, at least in part, on a multiple apparatus notification filter. For example, the notification filter and the different notification filter may be modified based, at least in part, on the multiple apparatus notification filter via inheritance, propagated modification, and/or the like.
In the example of FIGURE 3B, filter 352 and filter 356 may each relate to a notification filter, a multiple apparatus notification filter, and/or the like. Filter 360 may relate to a multiple apparatus notification filter. Filter 352 is associated with at least apparatus 354 and filter 356 is associated with at least peripheral 358. In the example of FIGURE 3B, event notifications intended for rendering at apparatus 354 may be approved for rendering or precluded from rendering at apparatus 354 by way of associated filter 352. Similarly, event notifications intended for rendering at peripheral 358 may be approved for rendering or precluded from rendering at peripheral 358 by way of associated filter 356. In the example of FIGURE 3B, filter 360 is associated with at least filter 352 and filter 356. Filter 360 may cause modification of filter 352 and/or filter 356 by way of inheritance, propagated modification, and/or the like. Apparatus 354 may be associated with one or more filters in addition to filter 352 and filter 360. Filter 352 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like in addition to apparatus 354. Peripheral 358 may be associated with one or more filters in addition to filter 356 and filter 360. Filter 356 may be associated with one or more apparatuses, peripheral apparatuses, and/or the like in addition to peripheral 358. Filter 360 may be associated with one or more filters in addition to filter 352 and filter 356.
FIGURES 4A-4C are illustrations showing peripheral apparatuses according to at least one example embodiment. The examples of FIGURES 4A-4C are merely examples and do not limit the scope of the claims. For example, peripheral apparatus design may vary, type and number of peripheral apparatus output may vary, type and number of peripheral apparatus input may vary, and/or the like.
A peripheral apparatus may, for example, relate to a wearable apparatus, an entertainment apparatus, a global positioning system apparatus, a vehicular apparatus, and/or the like. In at least one example embodiment, a peripheral apparatus relates to a wearable apparatus.
A wearable apparatus may be an apparatus that is easily mountable, carryable, holdable, and/or transportable on one' s person. For example, a wearable apparatus may relate to a ring, a watch, a necklace, a bracelet, an anklet, an armband, a pair of glasses, a pair of sunglasses, a headset, and/or the like. In certain circumstances, a wearable apparatus may be desirable due to its placement on the body. For example, whereas an electronic apparatus may be hidden in a user's pant pocket, a wearable apparatus may be easily accessible, viewable, noticeable, reachable, and/or the like.
FIGURE 4A is an illustration showing a peripheral apparatus according to at least one example embodiment. In the example of FIGURE 4A, ring 400 comprises body 402, output 406, and input 408, input 410, and input 412. Output 406 may relate to any output, including a display output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like. Each of input 408, input 410, and input 412 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like. In the example of FIGURE 4A, ring 400 may indicate an event notification on display 406. In certain situations, a user may desire that ring 400 only receives specific types of event notifications based upon a particular set of criteria, including time, location, light conditions, event notification content, event notification context, and/or the like. In such situations, the user may indicate positive usefulness indications to the event notifications the user desires to be communicated to the ring 400 and indicate negative usefulness indications to event notifications the user desires to be precluded from communication to the ring 400.
FIGURE 4B is an illustration showing a peripheral apparatus according to at least one example embodiment. In the example of FIGURE 4B, glasses 430 comprises frame 432, output 436, and input 438, input 440, and input 442. Output 436 may relate to any output, including a display output, a laser output, a projector output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like. In the example of FIGURE 4B, either individual lens or both lenses may include display functionality. Each of input 438, input 440, and input 442 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like.
FIGURE 4C is an illustration showing a peripheral apparatus according to at least one example embodiment. In the example of FIGURE 4C, watch 460 comprises body 462, strap 464, output 466, and input 468, input 470, and input 472. Output 466 may relate to any output, including a display output, an electronic ink display output, a light output, an audio output, a haptic output, vibration output, and/or the like. Each of input 468, input 470, and input 472 may relate to any input, including a button input, key input, slider input, roller input, knob input, audio input, microphone input, camera input, light input, temperature input, touch input, direction input, location input via camera, global positioning system, and/or the like, motion input via accelerometer and/or gyroscope, and/or the like.
FIGURE 5 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment. In at least one example embodiment, there is a set of operations that corresponds with the activities of FIGURE 5. An apparatus, for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations. The apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations. In an example embodiment, an apparatus, for example electronic apparatus 10 of FIGURE 1, is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 5.
At block 502, the apparatus determines an event notification associated with an event. The determination, the event notification, and the event may be similar as described regarding FIGURES 2A-2C.
At block 504, the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification. The causation, the rendering, the event notification, the determination, the notification filter, the indication, and the approval of rendering may be similar as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
At block 506, the apparatus receives a usefulness indication associated with the event notification. The receipt and the usefulness indication may be similar as described regarding FIGURES 2A-2C and FIGURES 3A-3B. At block 508, the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication. The causation and the modification may be similar as described regarding FIGURES 3A-3B.
FIGURE 6 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment. In at least one example embodiment, there is a set of operations that corresponds with the activities of FIGURE 6. An apparatus, for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations. The apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations. In an example embodiment, an apparatus, for example electronic apparatus 10 of FIGURE 1, is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 6.
In certain circumstances, it may be desirable to manage a notification filter and/or a multiple apparatus notification filter at a different apparatus, similarly as described regarding FIGURE 2B. In such circumstances, an apparatus is in communication with a different apparatus, which may relate to a server. For example, after determining an event notification associated with an event, the apparatus may communicate with the different apparatus information necessary to determine an approval of rendering, and receive from the different apparatus information indicating approval of rendering.
At block 602, the apparatus determines an event notification associated with an event, similarly as described regarding block 502 of FIGURE 5.
At block 604, the apparatus sends information indicative of the event notification, similarly as described regarding FIGURES 2A-2C.
At block 606, the apparatus receives information indicative of the
determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
At block 608, the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
At block 610, the apparatus receives a usefulness indication associated with the event notification, similarly as described regarding block 506 of FIGURE 5.
At block 612, the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication, similarly as described regarding block 508 of FIGURE 5.
FIGURE 7 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment. In at least one example embodiment, there is a set of operations that corresponds with the activities of FIGURE 7. An apparatus, for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations. The apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations. In an example embodiment, an apparatus, for example electronic apparatus 10 of FIGURE 1, is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 7.
At block 702, the apparatus determines an event notification associated with an event, similarly as described regarding block 502 of FIGURE 5.
At block 704, the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
At block 706, the apparatus receives a usefulness indication associated with the event notification, similarly as described regarding block 506 of FIGURE 5.
At block 708, the apparatus causes modification of the notification filter based, at least in part, on the usefulness indication, similarly as described regarding block 508 of FIGURE 5.
At block 710, the apparatus determines another event notification associated with another event, the other event notification correlating with the event notification, similarly as described regarding FIGURES 2A-2C.
At block 712, the apparatus precludes rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification, similarly as described regarding FIGURES 3A-3B.
FIGURE 8 is a flow diagram illustrating activities associated with filtering of a notification according to at least one example embodiment. In at least one example embodiment, there is a set of operations that corresponds with the activities of FIGURE 8. An apparatus, for example electronic apparatus 10 of FIGURE 1, or a portion thereof, may utilize the set of operations. The apparatus may comprise means, including, for example processor 11 of FIGURE 1, for performance of such operations. In an example embodiment, an apparatus, for example electronic apparatus 10 of FIGURE 1, is transformed by having memory, for example memory 12 of FIGURE 1, comprising computer code configured to, working with a processor, for example processor 11 of FIGURE 1, cause the apparatus to perform set of operations of FIGURE 8.
In certain circumstances, it may be desirable for a notification filter to consider criteria other than event notification source. For example, the event notification source may relate to an application. In such an example, the application may be one of several criteria considered by the notification filter and may not be outcome determinative. At block 802, the apparatus determines an event notification associated with an event and an application, similarly as described regarding FIGURES 2A-2C and FIGURES 3A- 3B.
At block 804, the apparatus causes rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification, similarly as described regarding block 504 of FIGURE 5.
At block 806, the apparatus receives a negative usefulness indication associated with the event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A- 3B.
At block 808, the apparatus cause modification of the notification filter based, at least in part, on the negative usefulness indication, similarly as described regarding FIGURES 3A-3B.
At block 810, the apparatus determines another event notification associated with another event and the application, the other event notification correlating with the event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
At block 812, the apparatus precludes rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification, similarly as described regarding FIGURES 3A-3B.
At block 814, the apparatus determines a different event notification associated with a different event and the application, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
At block 816, the apparatus causes rendering of the different event notification to the user based, at least in part, on a determination that a notification filter indicates approval of rendering of the different event notification, similarly as described regarding FIGURES 2A-2C and FIGURES 3A-3B.
Embodiments of the invention may be implemented in software, hardware, application logic or a combination of software, hardware, and application logic. The software, application logic and/or hardware may reside on the apparatus, a separate device, or a plurality of separate devices. If desired, part of the software, application logic and/or hardware may reside on the apparatus, part of the software, application logic and/or hardware may reside on a separate device, and part of the software, application logic and/or hardware may reside on a plurality of separate devices. In an example embodiment, the application logic, software or an instruction set is maintained on any one of various conventional computer-readable media.
If desired, the different functions discussed herein may be performed in a different order and/or concurrently with each other. For example, block 708 of FIGURE 7 may be performed after block 710 of FIGURE 7. Furthermore, if desired, one or more of the above - described functions may be optional or may be combined. For example, block 604 and 606 of FIGURE 6 may be optional and/or combined with block 608 of FIGURE 6.
Although various aspects of the invention are set out in the independent claims, other aspects of the invention comprise other combinations of features from the described embodiments and/or the dependent claims with the features of the independent claims, and not solely the combinations explicitly set out in the claims.
It is also noted herein that while the above describes example embodiments of the invention, these descriptions should not be viewed in a limiting sense. Rather, there are variations and modifications which may be made without departing from the scope of the present invention as defined in the appended claims.

Claims

WHAT IS CLAIMED IS
1. An apparatus, comprising:
at least one processor;
at least one memory including computer program code, the memory and the computer program code configured to, working with the processor, cause the apparatus to perform at least the following:
determine an event notification associated with an event;
cause rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification;
receive a usefulness indication associated with the event notification; and cause modification of the notification filter based, at least in part, on the usefulness indication.
2. The apparatus of Claim 1, wherein:
causation of rendering of the event notification to the user comprises causing communication of the event notification to a peripheral apparatus; and
receipt of the usefulness indication associated with the event notification comprises receiving the usefulness indication from the peripheral apparatus.
3. The apparatus of Claim 2, wherein the peripheral apparatus relates to a wearable apparatus.
4. The apparatus of Claim 1, wherein the memory includes computer program code configured to, working with the processor, cause the apparatus to:
send information indicative of the event notification; and
receive information indicative of the determination that the notification filter indicates approval of rendering of the event notification.
5. The apparatus of Claim 1, wherein the notification filter comprises at least one criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria.
6. The apparatus of Claim 1, wherein the notification filter relates to at least one of heuristics or statistical methods.
7. The apparatus of Claim 1, wherein the memory includes computer program code configured to, working with the processor, cause the apparatus to: determine another event notification associated with another event, the other event notification correlating with the event notification; and
preclude rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
8. The apparatus of Claim 1, wherein the memory includes computer program code configured to, working with the processor, cause the apparatus to perform causing modification of a different notification filter based, at least in part, on the usefulness indication, the different notification filter being associated with a different apparatus.
The apparatus of Claim 1, wherein the apparatus comprises at least one output
A method comprising:
determining an event notification associated with an event;
causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification;
receiving a usefulness indication associated with the event notification; and
causing modification of the notification filter based, at least in part, on the usefulness indication.
The method of Claim 10, wherein:
causation of rendering of the event notification to the user comprises causing communication of the event notification to a peripheral apparatus; and
receipt of the usefulness indication associated with the event notification comprises receiving the usefulness indication from the peripheral apparatus.
12. The method of Claim 11, wherein the peripheral apparatus relates to a wearable apparatus.
The method of Claim 10, further comprising:
sending information indicative of the event; and
receiving information indicative of the determination that the notification filter indicates approval of rendering of the event notification.
14. The method of Claim 10, wherein the notification filter comprises at least one criteria that is independent of an event notification source, and the indication of approval is based, at least in part, on the criteria.
15. The method of Claim 10, wherein the notification filter relates to at least one of heuristics or statistical methods.
The method of Claim 10, further comprising:
determining another event notification associated with another event, the other event notification correlating with the event notification; and
precluding rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
17. At least one computer-readable medium encoded with instructions that, when executed by a processor:
determine an event notification associated with an event;
cause rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification;
receive a usefulness indication associated with the event notification; and cause modification of the notification filter based, at least in part, on the usefulness indication.
The medium of Claim 17, wherein:
causation of rendering of the event notification to the user comprises causing communication of the event notification to a peripheral apparatus; and receipt of the usefulness indication associated with the event notification comprises receiving the usefulness indication from the peripheral apparatus.
19. The medium of claim 17, wherein the notification filter relates to at least one of heuristics or statistical methods.
20. The medium of claim 17, wherein the instructions that, when executed by a processor, further:
determine another event notification associated with another event, the other event notification correlating with the event notification; and
preclude rendering of the other event notification to the user based, at least in part, on a determination that the notification filter indicates disapproval of rendering of the other event notification.
An apparatus comprising:
means for determining an event notification associated with an event; means for causing rendering of the event notification to a user based, at least in part, on a determination that a notification filter indicates approval of rendering of the event notification;
means for receiving a usefulness indication associated with the event notification; and
means for causing modification of the notification filter based, at least in part, on the usefulness indication.
PCT/US2013/050473 2013-07-15 2013-07-15 Method and apparatus for filtering of a notification Ceased WO2015009273A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/US2013/050473 WO2015009273A1 (en) 2013-07-15 2013-07-15 Method and apparatus for filtering of a notification

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/US2013/050473 WO2015009273A1 (en) 2013-07-15 2013-07-15 Method and apparatus for filtering of a notification

Publications (1)

Publication Number Publication Date
WO2015009273A1 true WO2015009273A1 (en) 2015-01-22

Family

ID=52346572

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2013/050473 Ceased WO2015009273A1 (en) 2013-07-15 2013-07-15 Method and apparatus for filtering of a notification

Country Status (1)

Country Link
WO (1) WO2015009273A1 (en)

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030131143A1 (en) * 2002-01-10 2003-07-10 Andrew Myers Notification services within a unified communications service
US20030188041A1 (en) * 2002-04-01 2003-10-02 Fillmore James A. Distributed event notification system and method
US20040196858A1 (en) * 2003-02-07 2004-10-07 Kirk Tsai Intermediary network system and method for facilitating message exchange between wireless networks
US20060092861A1 (en) * 2004-07-07 2006-05-04 Christopher Corday Self configuring network management system
US20070027808A1 (en) * 2005-07-29 2007-02-01 Microsoft Corporation Strategies for queuing events for subsequent processing
US20090013052A1 (en) * 1998-12-18 2009-01-08 Microsoft Corporation Automated selection of appropriate information based on a computer user's context
US20100095377A1 (en) * 2008-01-11 2010-04-15 Fortinet, Inc. Detection of suspicious traffic patterns in electronic communications
US20100255817A1 (en) * 2009-04-06 2010-10-07 Ying-Ju Chen Method and system for filtering incoming messages to a mobile device
US20120066498A1 (en) * 2010-09-09 2012-03-15 Kai Wolfgang Engert Verifying authenticity of a sender of an electronic message sent to a recipient using message salt
US8180883B1 (en) * 2004-08-02 2012-05-15 Cisco Technology, Inc. Method and system for processing directives included in management events

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090013052A1 (en) * 1998-12-18 2009-01-08 Microsoft Corporation Automated selection of appropriate information based on a computer user's context
US20030131143A1 (en) * 2002-01-10 2003-07-10 Andrew Myers Notification services within a unified communications service
US20030188041A1 (en) * 2002-04-01 2003-10-02 Fillmore James A. Distributed event notification system and method
US20040196858A1 (en) * 2003-02-07 2004-10-07 Kirk Tsai Intermediary network system and method for facilitating message exchange between wireless networks
US20060092861A1 (en) * 2004-07-07 2006-05-04 Christopher Corday Self configuring network management system
US8180883B1 (en) * 2004-08-02 2012-05-15 Cisco Technology, Inc. Method and system for processing directives included in management events
US20070027808A1 (en) * 2005-07-29 2007-02-01 Microsoft Corporation Strategies for queuing events for subsequent processing
US20100095377A1 (en) * 2008-01-11 2010-04-15 Fortinet, Inc. Detection of suspicious traffic patterns in electronic communications
US20100255817A1 (en) * 2009-04-06 2010-10-07 Ying-Ju Chen Method and system for filtering incoming messages to a mobile device
US20120066498A1 (en) * 2010-09-09 2012-03-15 Kai Wolfgang Engert Verifying authenticity of a sender of an electronic message sent to a recipient using message salt

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
CARZANIGA, A. ET AL.: "Design and Evaluation of Wide-Area Event Notification Service", ACM TRANSACTIONS ON COMPUTER SYSTEMS, vol. 19, no. 3, August 2001 (2001-08-01), pages 332 - 383, Retrieved from the Internet <URL:ftp://ftp.cs.utoronto.ca/pub/hfliu/papers/siena_tocs01.pdf> [retrieved on 20131208] *

Similar Documents

Publication Publication Date Title
US20230319413A1 (en) User interfaces for camera sharing
CN105556457B (en) Wearable electronic device, method for processing information, and computer-readable medium
CN110622120B (en) voice communication method
US10324580B2 (en) Causing display of a notification
US11765114B2 (en) Voice communication method
US9189873B2 (en) Method and apparatus for indicating historical analysis chronicle information
KR101959609B1 (en) Performance of an operation based at least in part on tilt of a wrist worn apparatus
CN111343081A (en) Information display method and electronic equipment
TW201610810A (en) Electronic message user interface
US10432567B2 (en) Display of a notification that identifies a keyword
US9143875B2 (en) Determination of ambient sound processed audio information
US9910519B2 (en) Method and apparatus for operation designation
CN107682544A (en) A kind of backlog reminding method, terminal and computer-readable recording medium
US8996451B2 (en) Method and apparatus for determining an analysis chronicle
KR101626307B1 (en) Mobile terminal and operation control method thereof
WO2015009273A1 (en) Method and apparatus for filtering of a notification
US20180356973A1 (en) Method And System For Enhanced Touchscreen Input And Emotional Expressiveness
US8406458B2 (en) Method and apparatus for indicating an analysis criteria
US9646084B2 (en) Causation of storage of handshake greeting audio information
KR20110033697A (en) Mobile terminal and its control method
US9955000B2 (en) Method and apparatus for preclusion of causation of rendering of a notification at a notification time
US20150268820A1 (en) Causation of a rendering apparatus to render a rendering media item

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13889654

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13889654

Country of ref document: EP

Kind code of ref document: A1