Context-aware notification delivery
Through short-range communication and sensor analysis between the host device and accessories, the notification delivery method is selected based on the context, which solves the problem of duplicate processing of notifications on multiple devices and achieves unified management and efficient delivery.
Patent Information
- Application Number
- CN202080006039.8
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-05-07
- Publication Date
- 2025-09-26
- Estimated Expiration
- 2040-05-07
AI Technical Summary
Users repeatedly process notifications on multiple devices, making interactions cumbersome and prone to multiple interruptions. Existing technologies cannot effectively and collaboratively manage notification delivery.
The host device connects to the accessory through a short-range communication interface, uses sensor data to analyze user attention and accessory status, selects the appropriate notification delivery method, including audio, visual or tactile feedback, and selects the notification receiving device based on the context.
It achieves unified management of notifications in multi-device scenarios, reduces user interaction, improves the efficiency and consistency of notification delivery, and avoids repeated interruptions.
Smart Images

Figure CN113924555B_ABST
Abstract
Description
Background Art
[0001] Many devices provide a wireless connection to another device, such as an accessory. For example, a smartphone can be connected to a pair of earbuds or a smartwatch via short-range wireless pairing, so that the smartphone can output notifications to the earbuds and / or smartwatch. Each device can process notifications independently, so that the smartphone, earbuds, and smartwatch each receive notifications for the same content. The user may have to interact with the notification on each device to dismiss the notification. This is cumbersome for the user because the user may have dismissed or interacted with a notification on one accessory (e.g., a smartwatch), but still must interact with notifications on the smartphone and earbuds. In addition, the user may be interrupted separately by notifications on each device (e.g., by receiving an audio or tactile alert on each device). Summary of the Invention
[0002] The present disclosure provides a framework for delivering notifications to devices or accessories based on context. As used herein, an accessory can refer to any electronic device that is coupled to a host device and is capable of providing information to the user in some form (such as audio, visual, or tactile feedback). Examples of accessories include earbuds, smartwatches, headphones, and other wearable electronic devices. Accessories can also include other electronic devices accessed by the user of the host device, such as laptops, hubs, and tablets. For example, a host device can be wirelessly connected to one or more accessories so that these accessories can be used to receive notifications transmitted from the host device. To determine which accessory to transmit a notification to, the host device can obtain data from multiple sensors. Therefore, the host device can analyze the context of the accessory based on sensor data. For example, the host device can analyze user attention and accessory status. User attention can include, for example, whether the accessory is actively used by the user, whether the accessory detects the user's gaze, the accessory's posture, whether the accessory detects background vibrations, and the accessory's location. The accessory status can include, for example, whether the accessory is turned on and connected to the host device, and the accessory's mode, such as do not disturb, silent, or tactile. The host device can select one or more of the connected accessories to transmit notifications based on the context. The host device can select different types of notifications for each connected accessory based on the context. For example, the notification type can include audio, visual, tactile, etc. Once delivered, the notification can be dismissed by the user, so that dismissing the notification on one accessory will dismiss it on all devices and accessories.
[0003] One aspect of the present disclosure provides a host device comprising: a short-range communication interface adapted to transmit a notification to one or more accessories; a memory; and one or more processors in communication with the memory and the short-range communication interface. The one or more processors may be configured to: identify which of the one or more accessories are available for receiving notifications; analyze a context for transmitting the notification based on the one or more identified accessories; select at least one of the one or more identified accessories based on the context; and transmit the notification to the selected accessory.
[0004] The one or more processors may also be configured to request information from one or more sensors of each available device, the one or more sensors including at least one of: (i) an audio input sensor, (ii) an image sensor, (iii) a touch sensor, or (iv) a proximity sensor; receive information from the one or more sensors; and determine the context including at least one of user attention or an accessory state based on the received information. User attention may include at least one of: (i) active use of at least one of the one or more available accessories, (ii) gaze detection, (iii) gesture detection, (iv) conversation detection, or (v) the location of the one or more available accessories. The accessory state may include at least one of: (i) do not disturb mode, (ii) silent mode, or (iii) tactile mode.
[0005] The one or more processors may also be configured to determine a content type; determine a content classification based on the content type; and determine a notification type to be delivered to the selected attachment based on the content type, the content classification, and the one or more identified attachments. The content type may include at least one of: (i) a text message, (ii) an email, (iii) an application notification, (iv) a download, or (v) a news update. The content classification may include at least one of: (i) urgent, (ii) sensitive, (iii) normal, or (iv) a reminder. The notification type may include at least one of: (i) a visual notification, (ii) an audio notification, or (iii) a tactile notification.
[0006] The one or more processors may be configured to receive content in the form of an electronic message or a data set, wherein the one or more processors are configured to determine a type of content based on the received content. The one or more processors may also be configured to determine which of the one or more attachments are private attachments and public attachments. The private attachments may be accessible to a primary user of the device, and the public attachments may be accessible to the primary user and at least one other user of the device.
[0007] Another aspect of the present disclosure provides a method for delivering a notification to a selected accessory. The method includes: identifying, by one or more processors of a host device, which of one or more accessories are available for receiving notifications, analyzing, by the one or more processors, a context for delivering the notification based on the one or more identified accessories, selecting, by the one or more processors, at least one of the one or more identified accessories based on the context, and delivering, by the one or more processors, the notification to the selected accessory. BRIEF DESCRIPTION OF THE DRAWINGS
[0008] Figure 1 is a functional diagram of an example system according to aspects of the present disclosure.
[0009] Figure 2 is a functional block diagram of an example system according to aspects of the present disclosure.
[0010] Figure 3 is a schematic diagram of an example system according to aspects of the present disclosure.
[0011] Figure 4 is a schematic diagram of an example system according to aspects of the present disclosure.
[0012] Figure 5 is a schematic diagram according to various aspects of the present disclosure.
[0013] Figure 6 is a schematic diagram of an example system according to aspects of the present disclosure.
[0014] Figure 7 is a schematic diagram illustrating an example use of a system according to aspects of the present disclosure.
[0015] Figure 8 is a schematic diagram illustrating another example use of the system according to aspects of the present disclosure.
[0016] Figure 9 is a flow chart illustrating a method of selecting an attachment for receiving a notification based on context according to aspects of the present disclosure. DETAILED DESCRIPTION
[0017] The systems and methods described herein relate to a host device that can be coupled to one or more accessories simultaneously. As described above, an accessory can refer to any electronic device that is coupled to a host device and is capable of providing information to a user in some form (such as audio, visual, tactile feedback, etc.). Examples of accessories may include earbuds, smart watches, headphones, other wearable electronic devices, etc. Accessories may also include other electronic devices that can be accessed by the user of the host device, such as laptops, hubs, tablets, etc. Accessories can be coupled to the host device via short-range communication (e.g., Bluetooth, Bluetooth Low Energy (BLE), etc.). The host device and each connected accessory may include one or more sensors. As just some examples, the sensors may include image sensors, gaze detection sensors, audio detection inputs, touch sensors, and / or proximity sensors. According to some examples, Bluetooth signal strength analysis or ultra-wideband ("UWB") analysis can be used to detect when an accessory or electronic device is nearby. Sensor data can provide a context related to the user's attention. For example, user attention can be inferred through active use of the accessory, detection of the user's gaze, gesture data related to the orientation of the accessory, and detection of background chatter, thereby alerting the host device that the user may be nearby and the location of the accessory. Contextual data can also include information related to the state of the accessory. For example, the accessory state can include whether the accessory is open or closed and whether the accessory is set to a specific mode such as do not disturb, silent, haptic, etc. The host device can analyze the contextual data to determine which device or accessory to deliver the notification to.
[0018] Figure 1 An example system 100 is shown in which the features described herein may be implemented. This should not be considered to limit the scope of the present disclosure or the usefulness of the features described herein. In this example, system 100 may include multiple devices 110, 120, 130, 140, 150, a server computing device 170, and a network 180. The collection of devices may include, for example, a smartphone 110, a hub 120, a smartwatch 130, a laptop 140, and a headset 150. For convenience, the collection of devices 110, 120, 130, 140, 150 or a single device is referred to as device 110.
[0019] Each device 110 may be a personal computing device intended for use having all of the components typically used in connection with a personal computing device as described herein, including one or more processors (e.g., a central processing unit (CPU)), memory to store data and instructions (e.g., RAM and an internal hard drive), a display (e.g., a monitor with a screen, a touch screen, a projector, a television, or other device operable to display information, such as a smartwatch display), and a user input device (e.g., a mouse, keyboard, touch screen, or microphone).
[0020] Each of devices 110 can be a mobile computing device capable of wirelessly exchanging data with a server over a network such as the Internet, or a full-size personal computing device. By way of example only, devices may include mobile phones, wireless-enabled PDAs, tablet computers, netbooks capable of accessing information via the Internet or other networks, wearable computing devices (e.g., smart watches, headphones, smart glasses, virtual reality players, other head-mounted displays, etc.), wireless speakers, home assistants, game controllers, and the like. In some examples, one or more devices 110 may also be wirelessly coupled to accessories, such as earbuds, smart glasses, and the like. Furthermore, such accessories may be indirectly connected to network 180 through one or more devices 110.
[0021] Device 110 may be at various nodes of network 180 and may be capable of communicating directly and indirectly with other nodes of network 180. Figure 1 While four (4) devices are depicted in FIG, it should be understood that a typical system 100 may include one or more devices, with each computing device located at a different node of the network 180. Various protocols and systems may be used to interconnect the network 180 and intermediate nodes described herein, such that the network may be part of the Internet, the World Wide Web, a specialized intranet, a wide area network, or a local area network. The network 180 may utilize one or more company-proprietary standard communication protocols such as WiFi. While certain advantages are achieved in transmitting or receiving information as described above, other aspects of the subject matter described herein are not limited to any particular transmission method.
[0022] In one example, system 100 may include one or more server computing devices (e.g., a load balancing server farm) having multiple computing devices that exchange information with different nodes of a network for receiving data from other computing devices, processing data, and transmitting data to other computing devices. For example, one or more server computing devices 170 may be web servers capable of communicating with one or more devices 110 via network 180. In addition, server computing device 170 may use network 180 to transmit information to one of the other devices 110. Server computing device 170 may include one or more processors, memory, instructions, and data. These components operate in the same or similar manner as those described herein with respect to device 110. Server computing device 170 may receive sensor data from device 110. Server computing device 170 may determine a context for transmitting a notification by analyzing the sensor data.
[0023] Figure 2An example system 200 is shown in which the features described above and herein can be implemented. This should not be considered to limit the scope of the present disclosure or the usefulness of the features described herein. In this example, the system 200 can include a host device 210 and accessories 220, 230, 240, 250, 260. The host device 210 can include one or more processors 202, memory 204, instructions 206, data 208, a wireless communication interface or antenna 211, one or more sensors 217, a notification function 218, and a device state 219. The host device 210 can communicate with the accessories 220, 230, 240, 250, 260 via a short-range wireless communication interface.
[0024] The one or more processors 202 may be any conventional processor, such as a commercially available microprocessor. Alternatively, the one or more processors may be a dedicated device, such as an application specific integrated circuit (ASIC) or other hardware-based processor. Although Figure 2 The processor, memory, and other elements of host device 210 are functionally shown as being within the same box, but one of ordinary skill in the art will appreciate that the processor, computing device, or memory may actually include multiple processors, computing devices, or memories that may or may not be stored in the same physical housing. Similarly, the memory may be a hard drive or other storage medium located in a housing different from the housing of host device 210. Therefore, references to a processor or computing device will be understood to include references to a collection of processors, computing devices, or memories that may or may not operate in parallel.
[0025] The memory 204 can store information accessible by the processor, including instructions 206 and data 208 that can be executed by the processor 202. The memory 204 can be a type of memory operable to store information accessible by the processor 202, including a non-transitory computer-readable medium, or other medium that stores data that can be read by an electronic device, such as a hard drive, a memory card, a read-only memory ("ROM"), a random access memory ("RAM"), an optical disk, and other memory and read-only memory with write capabilities. The subject matter disclosed herein can include different combinations of the foregoing, whereby different portions of the instructions 206 and data 208 are stored on different types of media.
[0026] The data 208 can be retrieved, stored, or modified by the processor 202 according to the instructions 206. For example, although the present disclosure is not limited to a particular data structure, the data 208 can be stored in a computer register, in a relational database as a table with multiple different fields and records, an XML document, or a flat file. The data 208 can also be formatted in a computer-readable format (such as, but not limited to, binary values, ASCII, or Unicode). By way of example only, the data 208 can be stored as a bitmap composed of pixels stored in compressed or uncompressed or various image formats (e.g., JPEG), vector-based formats (e.g., SVG), or computer instructions for mapping. In addition, the data 208 can include information sufficient to identify the relevant information, such as numbers, descriptive text, proprietary codes, pointers, references to data stored in other memories (including other network locations), or information used by functions to calculate relevant data.
[0027] Instructions 206 may be any set of instructions to be executed directly by processor 202 (e.g., machine code) or indirectly (e.g., a script). In this regard, the terms "instructions," "application," "steps," and "program" are used interchangeably herein. Instructions may be stored in object code format for direct processing by the processor, or in any other computing device language, including scripts or collections of independent source code modules that are interpreted or pre-compiled as needed. The functions, methods, and routines of the instructions are described in more detail below.
[0028] Host device 210 may further include a wireless communication interface 211, such as an antenna, a transceiver, and any other equipment for wireless communication. The antenna may be, for example, a short-range wireless network antenna. Host device 210 may be capable of coupling with accessories 220, 230, 240, 250, and 260 via wireless connections 203, 205, 209, 207, and 201, respectively. For example, the antenna may be used to transmit and receive Bluetooth signals. There may be a maximum distance between host device 210 and accessories 220, 230, 240, 250, and 260 that allows host device 210 and accessories 220, 230, 240, 250, and 260 to be within range of each other.
[0029] Host device 210 can include one or more sensors 217. The sensors can include, for example, image sensors, gaze detection sensors, audio detection sensors, touch sensors, and / or proximity sensors. Data acquired by the sensors can be analyzed to determine context. Context can include user attention and / or accessory status. User attention can include, for example, detection of user proximity and / or user gaze, detection of background noise, positioning of host device 210 relative to a connected accessory, and the like.
[0030] The one or more image sensors can convert light signals into electrical signals to detect or capture features and / or objects around the host device 210. The one or more image sensors can be, for example, charge coupled device (“CCD”) sensors or complementary metal oxide semiconductor (“CMOS”) sensors. The one or more processors 302 can process the features and / or objects detected by the one or more image sensors to identify at least one detected feature and / or object. The one or more image sensors can be used to detect the gaze of the user, such that the image sensors also serve as gaze detection sensors. According to some examples, the image sensors can be used to determine the posture of the device.
[0031] The audio detection sensor may include, for example, one or more microphones configured to receive audio input signals. Audio input may include background noise, such as music, people talking, etc. The user can enable or disable receiving background noise as audio input, and if the user enables this feature, the device can only receive background noise as audio input. According to some examples, the user can adjust the settings on the device to limit sharing to a specific geographic area, time, or condition, such as when the device is within the Bluetooth range of a predetermined number of other user devices. In addition, the user can set one or more microphones to automatically disable in a specific location. According to some examples, the user can set the device to automatically disable receiving background noise as audio input in a specific location such as a familiar location. The user can further configure the device to receive audio input without further active input from the user. In some examples, the microphone used for audio detection input can also be used for user input.
[0032] A proximity sensor can detect the proximity of an accessory to other devices, for example, based on signal strength or other communication parameters.
[0033] The sensor data can be analyzed by host device 210 or another device on the network to determine user attention. Analyzing the sensor data can include, for example, determining whether the user is likely to see, hear, or feel the notification. Additionally or alternatively, analyzing the sensor data can include selecting an accessory to receive a notification. For example, based on the user's attention, host device 210 can transmit a notification to the connected accessory. In some examples, based on the user's attention, host device 210 can output a notification.
[0034] Host device 210 may include one or more notification features or settings 218. Notifications may, for example, be audio, tactile, visual, or a combination of audio, tactile, or visual. The audio notifications output by host device 210 may include noises or sounds that a user may hear. Thus, host device 210 may further include one or more outputs, such as speakers. Host device 210 may further include a control for determining the volume level of the audio notifications.
[0035] One or more device states 219 may include, for example, off, do not disturb, silent, tactile mode, etc. For example, when host device 210 is off, host device 210 may not be able to transmit or receive notifications. In some examples, when host device 210 is set to do not disturb, notifications received by host device 210 may not result in notifications being provided to the user. When in silent mode, host device 210 can receive content and notifications, but may only provide visual notifications. When in tactile mode, host device 210 can receive content and notifications, but may only provide tactile notifications. Host device 210 may have a default state that may, for example, allow any type of notification including audio, tactile, or visual.
[0036] Accessories 220, 230, 240, 250, 260 may each include one or more processors 222, 232, 242, 252, 262, memories 224, 234, 244, 254, 264, wireless communication interfaces 221, 231, 241, 251, 261, sensors 227, 237, 247, 257, 267, notification functions or settings 228, 238, 248, 258, 268 and device states 229, 239, 249, 259, 269, which are substantially the same as those described herein for the host device 210.
[0037] Host device 210 or another device on the network can analyze sensor data for each accessory to determine user attention. Accessories can be ranked based on user attention. High-ranking accessories may be accessories whose notifications the user is likely to hear, see, or feel, while low-ranking accessories may be accessories whose notifications the user is unlikely to hear, see, or feel, for example. For example, a high-ranking accessory may be an accessory that the user is actively using. A low-ranking accessory may be an accessory that is unable to detect the user's presence or gaze.
[0038] Analyzing the sensor data can include, for example, determining which accessory, if any, is being actively used. Analyzing the sensor data can also include determining the proximity of the accessory to the host device 210. For example, an accessory that is closer to the host device 210 can be ranked higher in terms of user attention than an accessory that is farther away. According to some examples, analyzing the sensor data can include detecting the presence of a user and / or detecting the user's gaze. An accessory that detects the presence of a user and / or the user's gaze using an image sensor can be ranked higher in terms of user attention than an accessory that does not detect the presence of a user and / or the user's gaze.
[0039] Additionally or alternatively, the host device or another device on the network can analyze the accessory status. Analyzing the accessory status can include determining which accessories are turned off or which are set to do not disturb, silent, haptic, morning, evening, etc. For example, the host device, the network computing device, or another device on the network can send a request to each accessory for the status of the accessory. The accessory can respond to the request with an indication of the accessory status. Additionally or alternatively, accessories that cannot be reached by the status request can be determined to be offline and / or turned off. Turned-off accessories may be excluded from the list of available accessories for receiving notifications. According to some examples, the accessory status can be set by the user. In some examples, an application on the host device can use specific notification settings for the connected accessory. In another example, a cloud management status system can be used to determine the accessory status. For example, each accessory can access a cloud management account that includes the accessory status of each accessory.
[0040] The accessory state can be used as a factor in determining which accessory to deliver a notification to. The accessory state (e.g., do not disturb, morning, evening, etc.) may cause each accessory to respond differently and, therefore, may affect the ranking of accessories to which notifications are delivered. For example, an accessory that is set to do not disturb may be ranked lowest when a notification is delivered to it. According to some examples, the host device may determine that an accessory that is set to silent may only receive visual notifications. In some examples, when an accessory is set to tactile mode, the host device may determine that the accessory may receive both visual and tactile notifications.
[0041] User attention and accessory status can determine the context in which the host device transmits a notification to one of the accessories. The context can, for example, determine the accessory from which the user is most likely to see, hear, or feel the notification. Based on user attention and / or accessory status, the host device 210 or another device on the network can determine which accessory receives the notification.
[0042] Figure 3 An example system 300 is shown, which shows a host device and multiple accessories connected via a short-range communication interface. The host device can store paired accessories by category. Once the host device identifies which accessories are connected, it can categorize the connected accessories based on whether they are private or public. For example, a private accessory may be one intended only for use by the user of the host device, while a public accessory may be one intended for use by the user of the host device as well as other individuals. In other examples, accessories can be further categorized based on user preferences, accessory type, and so on.
[0043] The host device can be, for example, a smartphone 310 or any of a variety of other host devices (e.g., a laptop, gaming system, tablet, etc.). Smartphone 310 can have a short-range wireless communication interface. The short-range communication interface can include, for example, a wireless network antenna, a transceiver, etc. The short-range communication interface can allow smartphone 310 to wirelessly connect to accessories. Accessories can include a home assistant hub 320, a smartwatch 330, a laptop 340, an augmented reality and / or virtual reality headset 350 and a pair of earbuds 360, or any of a variety of other accessories (e.g., a fitness tracker, wireless speakers, glasses, a head-mounted display, a tablet, a game controller, a motorcycle helmet, etc.). Each accessory can include a short-range communication interface that allows the accessory to couple to the host device. Wireless coupling can be established using any of a variety of technologies (e.g., Bluetooth, Bluetooth Low Energy (BLE), etc.). Accessories can be classified as private or public. According to some examples, accessories can be classified based on user input.
[0044] A host device can simultaneously connect wirelessly to one or more accessories. For example, smartphone 310 can connect to earbuds 360 via wireless connection 301, hub 320 via wireless connection 303, smartwatch 330 via wireless connection 305, laptop 340 via wireless connection 309, and headset 350 via wireless connection 307. According to some examples, smartphone 310 can simultaneously connect wirelessly to these accessories when hub 320, smartwatch 330, laptop 340, headset 350, and earbuds 360 are within range of a wireless network antenna. In some examples, smartphone 310 can only connect to earbuds 360 and smartwatch 330, for example, due to the range of smartphone 310's wireless network antenna. Thus, smartphone 310 can wirelessly couple to any number of accessories within range of its wireless network antenna.
[0045] The smartphone 310 can store a categorized list 390 of connected accessories. As just one example, the list 390 can identify devices as private devices 392 and public devices 394. A private accessory can be an accessory that generally outputs content only to the primary user. The primary user can be determined based on the user profile set up on the host device during the out-of-box experience. According to some examples, earbuds or smartwatches can be private accessories. For example, earbuds or smartwatches can be accessories that are used only by the primary user. Therefore, content or notifications transmitted to the earbuds or smartwatch can only be received by the primary user. A public or shared accessory can be an accessory that generally outputs content to anyone within the audio, visual, or other output range of the accessory. For example, wireless speakers or displays, short-range wireless stereos, etc. can be shared accessories.
[0046] In some examples, list 390 may include an identifier to indicate how each accessory is categorized. The identifier may be, for example, a color, an icon, text, placement of the accessory name in a specific section, a title, a sublist, etc. According to some examples, list 390 may be determined by user input. For example, a user may provide a name for each device or accessory after it is connected to the host device. List 390 may be user-modifiable, allowing the user to change the name of a device, add a device, or remove a device at any time.
[0047] As shown in system 300, smartphone 310 can categorize connected earbuds 360, hub 320, smartwatch 330, headset 350, and laptop computer 340. For example, smartphone 310 can categorize earbuds 360, smartwatch 330, and headset 350 as private accessories 392, and can categorize hub 320 and laptop computer 340 as public accessories 394.
[0048] Figure 4 A system is provided that can analyze the context of a host device and one or more accessories. The context can include user attention and accessory status. In some examples, the host device, a server computing device, or another device connected to a network can analyze the context data. Analyzing the context data can include, for example, analyzing sensor data collected by each accessory.
[0049] User attention can be inferred based on, for example, active users of the host device and / or accessory, detection of a user's gaze on the host device and / or accessory, gesture data associated with the device or accessory, whether the host device or accessory picks up background chatter, proximity of the accessory to the host device, etc. Data related to user attention can be determined based on data from one or more sensors of the host device or accessory. The data can be transmitted or shared over a network to the host device, a server computing device, or another device on the network for analysis.
[0050] The accessory state can be inferred by, for example, whether the accessory is open or closed, whether the accessory is set to do not disturb, silent, haptic mode, etc. Data related to the accessory state can be transmitted to a host device, a server computing device, or another device on the network for analysis.
[0051] Data can be collected from a host device and an accessory and shared over a network. The host device can analyze the contextual data to determine a context for delivering a notification to the host device and / or at least one accessory. According to some examples, the data can be analyzed by a server computing device or another device on the network.
[0052] The host device can rank available accessories based on the corresponding contextual data of each accessory. In some examples, the ranking can determine the accessories to which the host device will transmit notifications. For example, sensor data and accessory status can be analyzed to determine the ranking of each accessory. According to some examples, accessories that are closer to the host device can be ranked higher than accessories that are farther away. Accessories that are actively in use can be ranked higher than accessories that are turned off or set to do not disturb. Accessories that detect the user's presence and / or the user's line of sight can be ranked higher than accessories that do not detect the user's presence and / or the user's line of sight.
[0053] According to some examples, contextual data can also be analyzed to rank each accessory based on the type of notification determined to be delivered. For example, for receiving visual notifications, an accessory that detects the user's presence and / or the user's gaze may be ranked higher because the user may be more likely to see the visual notification if it were sent to the accessory. For receiving tactile notifications, an accessory that is on the user's body or worn by the user may be ranked higher than an accessory that is at a distance from the user because the user can easily feel the tactile notification.
[0054] Figure 4A system is shown in which a host device receives content and determines the type of content. The host device can receive content sent from another device, content sent from an application, content sent via a server computing device over a network, and the like. For example, the content can be received in the form of an electronic message or data set received by the host device. One or more processors of the host device can determine the type of content based on the received content. The content type can include, for example, a text message, an email, a calendar notification and / or reminder, a news update, an application update, a phone call, and the like. In some examples, determining the content type can include determining the application from which the content was received. For example, a text message can be received in a messaging application, an email can be received in an email application, calendar content can be received from a calendar application, news content can be received in a news application, application content can be received from an application or game store, and the like. Once the content is received, an indication can appear on the application. In some examples, a server computing device or another device connected to the network can determine the content type.
[0055] System 400 may include a host device, such as smartphone 310, connected to network 180. Smartphone 310 may include multiple applications, such as messaging 412, email 414, calendar 416, news 418, app store 422, phone 424, games, social media applications, and the like. These applications may receive content intended for output to the user. For example, messaging application 412 may receive text, picture, or video messages, email application 414 may receive emails with various content intended for the user, calendar application 416 may receive invitations or reminders, news application 418 may receive real-time content, app store 422 may receive updates to applications on smartphone 310, and phone 424 may receive video and / or voice calls.
[0056] Smartphone 310 can receive content, such as a text message, sent via network 180. One or more processors 402 of smartphone 310 can determine that the content is a text message and, therefore, should appear in messaging application 412. Smartphone 310 can provide an indication 426 that smartphone 310 has received the content. Indication 426 can be provided on messaging application 412, indicating that the content is a text message.
[0057] Figure 5A system is shown in which one or more processors of a host device determine the content classification of received content. Content classification may include designating content as urgent, sensitive, reminder, normal, etc. In some examples, a server computing device or another device connected to a network may determine the content classification of content received by the host device. Additionally or alternatively, the content type may be set by the user for each application. For example, content received by a text messaging application may be designated as urgent, while updates from a news application may be considered normal.
[0058] Urgent content may be content sent from specific people or applications that may be automatically selected or designated by a user of the host device. For example, the host device may determine a list of the top ten (10) people from a list of contacts that the user communicates with. Any content sent by those top ten people may be designated as urgent content. According to some examples, the list may be five (5) designated people, twelve (12) designated people, twenty (20) designated people, twenty-five (25) designated people, and so on. Thus, a list of ten people is merely an example and is not meant to be limiting. According to some examples, urgent content may be determined based on a semantic analysis of the content and the source of the content. For example, a message from a user's manager that reads "Can you talk now about project X?" may be classified as urgent.
[0059] Sensitive content may include content that requires privacy such that it should only be provided to the user of the host device and not other individuals in the user's company. According to some examples, sensitive content may be any content received by the host device through certain applications or profiles. For example, content received by the host device for a work profile may be automatically or selectively set to sensitive. According to some examples, sensitive content may, for example, be more or less sensitive based on context. For example, content from a particular user or contact may be considered sensitive when in a public place, but may be considered non-sensitive when at the user's home. In one example, a message from a primary contact about a grocery list may be public content when at the user's home, but may be classified as private when in a public location such as work.
[0060] Reminders can be content received by a host device based on a specific date or time. For example, a calendar application can provide reminder content about scheduling appointments, meetings, gatherings, etc. According to some examples, an email application can provide reminder content about following up on emails.
[0061] Normal content may be any content received by the host device that is not designated as urgent, sensitive, alerting, etc.
[0062] The one or more processors 402 may determine a content classification based on the received content. For example, the received content may be a text message, as indicated by an indicator 526a on the messaging application 412. The one or more processors 402 may determine whether the text message is urgent, sensitive, normal, or a reminder. For example, the content may be classified as urgent. The indicator 526a may include a symbol indicating that the content is urgent. For example, the indicator 526a may include an exclamation point (!) to indicate that the content is urgent.
[0063] Figure 6 A system is described in which a host device can determine a notification type using one or more processors. The notification type can be determined based on one or more of analyzed contextual data, a determined content type, and a determined content classification. The notification type can be, for example, any one or a combination of tactile, audio, or visual notifications. The host device can also use the one or more processors to determine to which accessory the notification should be sent.
[0064] According to some examples, a host device, a server computing device, or another device on the network can include an algorithm for determining which accessory receives the notification. The algorithm can be based on contextual data collected from multiple sensors, content type, content classification, and / or notification type. Additionally or alternatively, a mesh network hosting the host device and one or more accessories can include an algorithm for determining which accessory receives the notification. In some examples, the mesh network can be a local mesh network.
[0065] For example, a notification for urgent content can be transmitted to an accessory that has one or more notification type capabilities. Urgent content may cause the host device to transmit tactile, audio, and visual notifications to alert the user to the content. Additionally or alternatively, the host device can transmit notifications about urgent content to an accessory that is currently being used and / or viewed. For example, if the accessory detects the user's gaze, the host device can transmit a notification to the accessory because the user is likely to see the notification.
[0066] According to some examples, notifications for sensitive content can be transmitted to a private accessory in an attempt to ensure that only the user of the host device receives the sensitive content.
[0067] Notifications for reminder content can be delivered to an attachment with audio and visual notification capabilities. For example, an audio notification can attract the user's attention, while a visual notification can provide a reminder.
[0068] Notifications for general alerts can be sent to any attachment, regardless of whether the attachment has been classified as private or public. The notification type for general content may be based on the available attachments. In some examples, the notification type can be a combination of notification types.
[0069] Although not depicted, any number of combinations of notification types can be communicated from the host device to the accessory based on one or more of the analyzed contextual data, the determined content type, and the determined content classification. Thus, the examples provided herein are not intended to be limiting.
[0070] The one or more processors 402 of the smartphone 310 may determine the type of notification to be delivered. For example, the one or more processors 402 may determine whether to deliver a tactile, audio, visual, or combined notification. The notification type may be determined based on one or more of contextual data, content type, content classification, and available attachments.
[0071] As indicated by indication 526a, the messaging application 412 has received urgent content. Based on contextual data, content type, available attachments, and / or content classification, the one or more processors 402 can determine a notification type. For example, the processor 802 can determine to send a tactile and visual notification based on the content being a text message, the text message being urgent, and the notification capabilities of the available attachments.
[0072] Once the notification type is determined, smartphone 310 can determine which accessory to send the notification to. When smartwatch 330, earbuds 360, hub 320, headset 350, and laptop 340 are wirelessly connected to smartphone 310, smartphone 310 can send the notification to at least one of these accessories. When the content is determined to be urgent, smartphone 310 can deliver the notification to a private accessory such as smartwatch 330 or earbuds 360. In addition, when messaging app 412 receives the content, smartphone 310 can determine to deliver at least a visual notification. The visual notification can include a preview of the content. As shown, smartphone 310 can deliver notification 628 to smartwatch 330. Notification 628 can include tactile notification 628a and visual notification 628b.
[0073] Figure 7 An example is shown in which the host device determines which accessory to send a notification to based on one or more of analyzed contextual data, a determined content type, a determined content classification, a determined notification type, and available accessories.
[0074] like Figure 7 As shown, smartphone 310 may not be actively used by user 802. For example, smartphone 310 may be at the feet or in a bag or backpack behind user 702. Smartphone 310 may receive content 726.
[0075] Smartphone 310 can identify which accessories are available for receiving notifications. Thus, smartphone 310 can identify smartwatch 330, earbuds 360, and laptop computer 340 as available accessories because they can be wirelessly connected to smartphone 310. Smartphone 310 can classify accessories as public accessories or private accessories. Public accessories can be accessories where individuals other than the user of the smartphone can access notifications and content. Private accessories can be accessories where only the user of the smartphone can access notifications and content. For example, smartwatch 330 and earbuds 360 can be classified as private accessories because only user 702 can access content and / or notifications, while laptop computer 340 can be classified as public accessories because anyone other than user 702 can access, see, or hear the content and / or notifications.
[0076] The smartphone 310 can analyze the context for delivering notifications based on the available accessories. The context data can be analyzed by the smartphone 310, a server computing device, or another device on the network based on data from one or more sensors of each accessory. The context can provide a framework for determining relevant, available, or accessible accessories to which notifications are delivered. The context can include at least one of user attention or accessory status. User attention can include whether the accessory is being actively used, whether the accessory detects the user's gaze, the accessory's posture, whether the accessory detects background chatter, location. The accessory status can include whether the accessory is open or closed and / or whether the accessory is set to a specific mode, such as do not disturb, silent, haptic, etc.
[0077] For example, smartwatch 330 can detect that user 702 is wearing it. However, smartwatch 330 may be posed so that the display is not facing user 702. Earbuds 360 can detect that they are being worn by user 702. Laptop computer 340 may have an image sensor with field of view 704. The image sensor can detect the presence of user 702 within field of view 704. Additionally or alternatively, the image sensor can detect user 702's gaze when user 702 is looking at laptop computer 340.
[0078] Smartphone 310 may select at least one or more of smartwatch 330, earbuds 360, and laptop 340 based on context. For example, smartphone 310 may rank smartwatch 330, earbuds 360, and laptop 340 based on contextual data. Laptop 340 may be ranked highest when user 702 is actively engaging with it and is therefore looking at its display. Headphones 360 and smartwatch 330 may be ranked lower than laptop 340. For example, smartwatch 330 may be ranked lower than laptop 340 because its display is facing away from user 702. Therefore, user 702 may not be actively engaging with smartwatch 330, further resulting in a lower ranking. Earbuds 360 may be ranked lower than laptop 340 because user 702 may not be actively engaging with earbuds 360.
[0079] Smartphone 310 can select which accessory to deliver a notification to based on the content type. For example, a notification for a phone call can be delivered to earbuds 360, even though earbuds 360 may be ranked lower than laptop 340. Earbuds 360 may be best suited for user 702 to interact with the notification (e.g., by answering the call). A notification for a text message can be delivered to smartwatch 330, even though smartwatch 330 may be ranked lower than laptop 340. A notification for an email can be delivered from smartphone 310 to laptop 340. According to some examples, laptop 340 may be best suited for user 702 to interact with the notification (e.g., by replying to the email).
[0080] In some examples, smartphone 310 can select which accessory to send a notification to based on the content classification. For example, content can be classified as urgent, sensitive, normal, reminder, etc. Smartphone 310 can send notifications for urgent content to the accessory that user 702 is currently engaging with to ensure that user 702 receives the notification. For example, based on the image sensor detecting the user's gaze, a notification for urgent content can be sent to laptop 340. Therefore, user 702 is likely to see the notification on laptop 340. Smartphone 310 can send notifications for sensitive content to a private accessory that can only be accessed or viewed by user 702. For example, the notification can be sent to earbuds 360 or smartwatch 330. Smartphone 310 can send notifications for normal or reminder content to any accessory, regardless of whether the accessory is classified as private or public.
[0081] Smartphone 310 can select the type of notification to be delivered to the accessory. For example, earbuds 360 can be capable of receiving audio and / or tactile notifications, laptop 340 can be capable of receiving audio and / or visual notifications, and smartwatch 330 can be capable of receiving audio, visual, and / or tactile notifications.
[0082] After analyzing the contextual data, content type, content classification, and / or notification type, smartphone 310 may transmit a notification 728 for content 726 to laptop 340. Since laptop 340 can detect the user's gaze, notification 728 may be a visual notification 728b. Visual notification 728 may be a text box or pop-up window displayed on laptop 340.
[0083] Laptop computer 340 can receive user input in response to notifications 728, 728a. For example, laptop computer 340 can receive commands to ignore, dismiss, mute, respond, and the like. Input received by laptop computer 340 regarding notifications 728, 728a can be executed on laptop computer 340 as well as host device 310, smartwatch 330, earbuds 360, and the like, even if notifications 728, 728a were not sent to these devices. For example, laptop computer 340 can receive input to dismiss notifications 728, 728a, and content and / or notifications on smartphone 310 can also be dismissed. Additionally or alternatively, laptop computer 340 can receive input to dismiss notifications 728, 728a, thereby dismissing the content and / or notifications on smartwatch 330 even if the notifications were never presented to user 702 on smartwatch 330. Input received on the accessory that received the notification will be executed on all coupled devices and accessories.
[0084] Figure 8 Another example of a host device determining an accessory to which a notification is sent is shown. For example, there may be a host device such as smartphone 310 and a host device user 802. Host device user 802 may be wearing smartwatch 330 and earbuds 360. Host device user 802 may be viewing or interacting with hub 320. Smartphone 310 can be wirelessly connected to smartwatch 330, earbuds 360, and hub 320. Smartphone 310, smartwatch 330, earbuds 360, and hub 320 can also be connected to a network. Therefore, smartphone 310, smartwatch 330, earbuds 360, and hub 320 can send and receive content to each other via a wireless communication interface and / or via a network.
[0085] Additional user 801 may be near host device user 802. Additional user 801 may have their own host device, such as smartphone 811, smartwatch 831, and earbuds 861. Smartphone 811 may be wirelessly connected to smartwatch 831 and earbuds 861. According to some examples, smartphone 811, smartwatch 831, and earbuds 861 may not be wirelessly connected to hub 320. Additional user 801 may be able to view or interact with hub 320 even when their device is not connected to the hub.
[0086] Smartphone 310 may be located in a bag or backpack some distance away from user 802. Therefore, user 802 may not be currently interacting with, using, or viewing content on smartphone 811. However, smartphone 310 may receive content 826. Smartphone 310 may determine to transmit a notification to the accessory to notify user 802 of received content 826.
[0087] Smartphone 310 can identify which accessories are available for receiving notifications. For example, smartphone 310 can identify that it is wirelessly connected to earbuds 360, smartwatch 330, and hub 320, and therefore earbuds 360, smartwatch 330, and hub 320 are available accessories. Smartphone 310 can identify smartwatch 831, earbuds 861, and smartphone 811 as accessories that can couple to smartphone 310 but cannot wirelessly connect to smartphone 310, and therefore are not available accessories.
[0088] Smartphone 310 can analyze the context used to deliver the notification. The context can include user attention and / or accessory status. User attention and accessory status can be based on data collected by sensors on each accessory, for example. For example, the accessory can have an audio input sensor, an image sensor, a proximity sensor, etc. The sensors can, for example, detect user attention attributes (such as whether the accessory is actively in use), detect the gaze of a nearby user, detect the posture of the accessory, detect background vibrations, compare the location of the accessory with the location of the host device, etc. According to some examples, each accessory (hub 320, earbuds 360, and smartwatch 330) can be set to a certain state or mode, such as do not disturb, silent, haptic, etc. The sensor data and current status of the accessories can be analyzed by smartphone 310 or a server computer to determine user attention and / or accessory status for hub 320, earbuds 360, and smartwatch 330.
[0089] Hub 320 may have one or more image sensors that can detect objects within the image sensor's field of view 804. As shown, both host device user 802 and additional user 801 may be within the field of view 804 of hub 320's image sensor. Thus, hub 320 can detect the presence of users 802 and 801. Hub 320 may also include one or more audio input sensors, such as microphones. The microphones can detect pauses in background sounds, indicating the presence of users 802 and 801. Hub 320 may additionally or alternatively include a proximity sensor to determine its proximity to smartphone 310.
[0090] The earbuds 360 may include one or more audio input sensors (such as microphones) to pick up background noise. Background noise may include, for example, pauses in chatter, music playing, etc. Background noise may indicate that someone other than the user 802 is nearby.
[0091] Smart watch 330 may include a sensor for determining whether user 802 is wearing smart watch 330. Smart watch 330 may also include a proximity sensor that can determine the proximity of smart watch 330 to smartphone 310.
[0092] Smartphone 310 can determine the type of content. For example, smartphone 310 can determine whether it has received a text, email, news update, app update, phone call, etc. Once the content type is determined, smartphone 310 can determine the content classification, such as whether the content is urgent, sensitive, normal, a reminder, etc. Based on the type of content, the content classification, and / or the notification capabilities of the available attachments, smartphone 310 can determine the notification type. For example, hub 320 can have audio and / or video notification capabilities, smartwatch 330 can have audio, visual, and / or tactile notification capabilities, and earbuds 360 can have audio and / or tactile notification capabilities.
[0093] According to some examples, content 826 may be an incoming call intended for user 802. Smartphone 310 may analyze the context for delivering the notification regarding the phone call. For example, sensor data from hub 320 may indicate the presence of at least two users 802 and 801 based on the image sensor's field of view 804. Sensor data from smartwatch 330 may indicate that user 802 is not actively engaged with smartwatch 330 based on its gesture data. Additionally or alternatively, sensor data from smartwatch 330 may indicate the presence of at least one additional user 801 due to background noise picked up by a microphone. Earbuds 360 may recognize that user 802 is currently wearing them. Since content 826 is a phone call, earbuds 360 may allow user 802 to easily interact with the notification. For example, earbuds 360 may be used by user 802 to conduct a conversation after answering the call.
[0094] The smartphone 310 may transmit a notification 828 to the earbuds 360. The notification 828 may be an audio notification 828c that may be heard by the user 802 wearing the earbuds 360. The notifications 828, 828c may alert the user 802 that a phone call has been received by the smartphone 310.
[0095] Earbuds 360 can receive input from user 802 in response to the notification. For example, the user can provide touch input (such as a swipe) to answer the phone call or dismiss the phone call. The input provided by the user can be applied to any other device that may have received the content 826 and / or notification. Thus, user 802 answering the call on earbuds 360 will remove content 826 and / or notifications from smartphone 310. Additionally or alternatively, user 802 answering or dismissing the call on earbuds 360 will remove content 826 and / or notifications from smartwatch 330 and hub 320.
[0096] Figure 9 An example method for determining an accessory to deliver a notification based on context is shown. For example, in block 910, a host device can identify one or more accessories available for receiving notifications. The available accessories can be accessories wirelessly coupled to the host device via a short-range communication interface.
[0097] In block 920, the host device may analyze the context for delivering a notification based on the one or more identified accessories. For example, analyzing the context may include analyzing data from one or more sensors, including an audio input sensor, an image sensor, a proximity sensor, and the like. The context for delivering the notification may include at least one of user attention or accessory status. User attention may include, for example, at least one of active use of the accessory, gaze detection, gesture detection, conversation detection, the location of the device, and the like. User attention may be determined based on data collected from the sensors. Accessory status may include, for example, do not disturb, silent, haptic, and the like.
[0098] In block 930, the host device may determine a content type. The content type may include, for example, at least one of a text message, an email, an application notification, a download, a news update, and the like.
[0099] In block 940, the host device may determine a content classification. The content classification may be based on the type of content or a semantic analysis of the content. According to some examples, the content classification may be urgent, sensitive, normal, reminder, etc.
[0100] In block 950, the host device can determine a notification type to transmit to the selected attachment. The notification type can be based on the content type, content classification, and / or identified attachment. The notification type can be, for example, at least one of a visual, audio, or tactile notification.
[0101] In block 960, the host device may select at least one of the identified attachments based on the context. Additionally or alternatively, the host device may select one of the identified attachments based on content type, content classification, and / or notification type.
[0102] In block 970, the host device can transmit a notification to the selected accessory.
[0103] The method provided herein may include all or only some of the steps disclosed. Additionally or alternatively, the steps disclosed herein may be performed in an order different from that disclosed. Furthermore, although the method is described with reference to a host device, a server computing device may perform some or all of the method steps.
[0104] Unless otherwise stated, the foregoing alternative examples are not mutually exclusive, but may be implemented in various combinations to achieve unique advantages. Since these and other variations and combinations of the features discussed above can be utilized without departing from the subject matter defined by the claims, the foregoing description of the embodiments should be made by way of illustration rather than by limitation of the subject matter defined by the claims. In addition, the provision of examples described herein and the use of phrases such as, "such as," "including," and the like should not be construed as limiting the subject matter of the claims to specific examples; rather, these examples are intended to illustrate only one of many possible embodiments. Furthermore, the same reference numerals in different figures may identify the same or similar elements.
Claims
1. A host device, comprising: a short-range communication interface adapted to transmit the notification to one or more accessories; Memory; as well as one or more processors in communication with the memory and the short-range communication interface, the one or more processors configured to: generating a notification based on the received content; generating a ranking for each of the one or more attachments; identifying which of the one or more attachments are available to receive the notification; analyzing a context for delivering the notification based on the one or more identified attachments; selecting at least one of the one or more identified attachments to receive the notification based on the context and the generated ranking of the one or more identified attachments; as well as The notification is transmitted to at least one selected attachment.
2. The device according to claim 1, wherein The one or more processors are further configured to: requesting information from one or more sensors of each available device, the one or more sensors comprising at least one of: (i) an audio input sensor, (ii) an image sensor, (iii) a touch sensor, or (iv) a proximity sensor; receiving information from the one or more sensors; as well as The context including at least one of user attention or attachment status is determined based on the received information.
3. The device according to claim 2, wherein The user attention includes at least one of: (i) active use of at least one of the one or more available accessories, (ii) gaze detection, (iii) gesture detection, (iv) conversation detection, or (v) location of the one or more available accessories.
4. The device according to claim 2, wherein The accessory state includes at least one of: (i) a do not disturb mode, (ii) a silent mode, or (iii) a tactile mode.
5. The apparatus according to claim 1, wherein The one or more processors are further configured to: determining a content type of the received content; determining a content classification based on the content type; and A notification type to be transmitted to at least one selected attachment is determined based on the content type, the content classification, and the one or more identified attachments.
6. The device according to claim 5, wherein The content type includes at least one of: (i) a text message, (ii) an email, (iii) an application notification, (iv) a download, or (v) a news update.
7. The apparatus according to claim 5, wherein The content classification includes at least one of: (i) urgent, (ii) sensitive, (iii) normal, or (iv) reminder.
8. The apparatus according to claim 5, wherein The notification type includes at least one of: (i) a visual notification, (ii) an audio notification, or (iii) a tactile notification.
9. The apparatus according to claim 1, wherein The ranking of the one or more accessories is based at least in part on one or more of: (i) proximity of the one or more accessories to the device, (ii) a determination that the one or more accessories are being actively used, (iii) detection of the presence of a user by the one or more accessories, (iv) a wearing condition of the one or more accessories, or (v) detection of a gaze of the user by the one or more accessories.
10. The apparatus according to claim 1, wherein The one or more processors are further configured to determine which of the one or more attachments are private attachments and public attachments.
11. The apparatus according to claim 10, wherein The private attachment is accessible by a primary user of the device, and the public attachment is accessible by the primary user and at least one other user of the device.
12. A method for delivering a notification, comprising: generating, by one or more processors of the host device, a notification based on the received content; generating, by the one or more processors, a ranking for each of the one or more attachments; identifying, by the one or more processors, which of the one or more accessories are available to receive the notification; analyzing, by the one or more processors, a context for delivering the notification based on the one or more identified attachments; receiving the notification by selecting, by the one or more processors, at least one of the one or more identified attachments based on the context and the generated ranking of the one or more identified attachments; as well as The notification is communicated, by the one or more processors, to at least one selected accessory.
13. The method according to claim 12, further comprising: requesting information from one or more sensors of each available device, the one or more sensors comprising at least one of: (i) an audio input sensor, (ii) an image sensor, (iii) a touch sensor, or (iv) a proximity sensor; receiving information from the one or more sensors; as well as A context including at least one of user attention or an attachment status is determined based on the received information.
14. The method according to claim 13, wherein The user attention includes at least one of: (i) active use of at least one of the one or more available accessories, (ii) gaze detection, (iii) gesture detection, (iv) conversation detection, or (v) location of the one or more available accessories.
15. The method according to claim 13, wherein: The accessory state includes at least one of: (i) a do not disturb mode, (ii) a silent mode, or (iii) a tactile mode.
16. The method according to claim 12, further comprising: determining, by the one or more processors, a content type of the received content; determining, by the one or more processors, a content classification based on the content type; as well as A notification type is determined, by the one or more processors, to be transmitted to at least one selected attachment based on the content type, the content classification, and the one or more identified attachments.
17. The method according to claim 16, wherein The content type includes at least one of: (i) a text message, (ii) an email, (iii) an application notification, (iv) a download, or (v) a news update.
18. The method according to claim 16, wherein The content classification includes at least one of: (i) urgent, (ii) sensitive, (iii) normal, or (iv) reminder.
19. The method according to claim 16, wherein The notification type includes at least one of: (i) a visual notification, (ii) an audio notification, or (iii) a tactile notification.
20. The method according to claim 12, wherein The ranking of the one or more accessories by the one or more processors is based at least in part on one or more of: (i) proximity of the one or more accessories to the host device, (ii) a determination that the one or more accessories are being actively used, (iii) detection of the presence of a user by the one or more accessories, (iv) a wearing condition of the one or more accessories, or (v) detection of a gaze of the user by the one or more accessories.
21. The method of claim 12, further comprising determining, by the one or more processors based on the one or more identified attachments, which of the one or more identified attachments are private attachments and public attachments.
22. A non-transitory computer-readable medium storing instructions that, when executed by one or more processors, cause the one or more processors to: generating a notification based on the received content; generating a ranking for each of the one or more attachments; identifying which of the one or more attachments are available to receive the notification; analyzing a context for delivering the notification based on the one or more identified attachments; selecting at least one of the one or more identified attachments to receive the notification based on the context and the generated ranking of the one or more identified attachments; as well as The notification is transmitted to at least one selected attachment.
Citation Information
Patent Citations
Proxying for Communicating Messages With an Unregistered Accessory Device
US20160234366A1
Managing connections of a user device
US20170245047A1
Mobile notifications based upon notification content
US9813882B1