Patent classifications
H04M19/045
Quiet hours for notifications
In some implementations, a computing device can be configured to automatically turn off notifications when generating a notification would cause a disturbance or be unwanted by a user. The device can be configured with quiet hours during which notifications that would otherwise be generated by the computing device can be suppressed. In some implementations, quiet hours can be configured as a time period with a start time and an end time. In some implementations, quiet hours can be derived from application data. For example, calendar data, alarm clock data, map data, etc. can be used to determine when quiet hours should be enforced. In some implementations, the device can be configured with exceptions to quiet hour notification suppression. In some implementations, the user can identify contacts to which the quiet hours notification suppression should not be applied.
User interface for limiting notifications and alerts
The present disclosure relates to systems and processes for limiting notifications on an electronic device. In one example process, data representing a user input can be received by an electronic device. The data representing the user input can include touch data from the touch-sensitive device, ambient light data from an ambient light sensor, intensity data from a contact intensity sensor, and/or motion data from one or more motion sensors. Based on the data, it can be determined whether the user input is a cover gesture over a touch-sensitive display of the electronic device. In response to determining that the user input is a cover gesture over the touch-sensitive display, the electronic device can be put into a DND mode for a predetermined amount of time. While in the DND mode, the electronic device can cease to output some or all notifications.
QUIET HOURS FOR NOTIFICATIONS
In some implementations, a computing device can be configured to automatically tum off notifications when generating a notification would cause a disturbance or be unwanted by a user. The device can be configured with quiet hours during which notifications that would otherwise be generated by the computing device can be suppressed. In some implementations, quiet hours can be configured as a time period with a start time and an end time. In some implementations, quiet hours can be derived from application data. For example, calendar data, alarm clock data, map data, etc. can be used to determine when quiet hours should be enforced. In some implementations, the device can be configured with exceptions to quiet hour notification suppression. In some implementations, the user can identify contacts to which the quiet hours notification suppression should not be applied.
METHOD FOR NOTIFICATION REMINDER, TERMINAL, AND STORAGE MEDIUM
A method for notification reminder is provided. A notification is received in a do not disturb (DND) mode. A contact corresponding to the notification is identified. A notification interface corresponding to the notification is displayed when the contact belongs to a preset contact group. A mode type of the DND mode is acquired. When the mode type belongs to a first mode type including a sleep mode and/or a mute mode, perform the notification reminder through sound according to a first prompt tone parameter and/or vibration according to a first vibration parameter. When the mode type belongs to a second mode type including a game mode and/or a meeting mode, perform the notification reminder through sound according to a second prompt tone parameter and/or vibration according to a second vibration parameter. The notification reminder is skipped when the contact does not belong to the preset contact group.
Quiet hours for notifications
In some implementations, a computing device can be configured to automatically turn off notifications when generating a notification would cause a disturbance or be unwanted by a user. The device can be configured with quiet hours during which notifications that would otherwise be generated by the computing device can be suppressed. In some implementations, quiet hours can be configured as a time period with a start time and an end time. In some implementations, quiet hours can be derived from application data. For example, calendar data, alarm clock data, map data, etc. can be used to determine when quiet hours should be enforced. In some implementations, the device can be configured with exceptions to quiet hour notification suppression. In some implementations, the user can identify contacts to which the quiet hours notification suppression should not be applied.
USER INTERFACE FOR LIMITING NOTIFICATIONS AND ALERTS
The present disclosure relates to systems and processes for limiting notifications on an electronic device. In one example process, data representing a user input can be received by an electronic device. The data representing the user input can include touch data from the touch-sensitive device, ambient light data from an ambient light sensor, intensity data from a contact intensity sensor, and/or motion data from one or more motion sensors. Based on the data, it can be determined whether the user input is a cover gesture over a touch-sensitive display of the electronic device. In response to determining that the user input is a cover gesture over the touch-sensitive display, the electronic device can be put into a DND mode for a predetermined amount of time. While in the DND mode, the electronic device can cease to output some or all notifications.
QUIET HOURS FOR NOTIFICATIONS
In some implementations, a computing device can be configured to automatically tum off notifications when generating a notification would cause a disturbance or be unwanted by a user. The device can be configured with quiet hours during which notifications that would otherwise be generated by the computing device can be suppressed. In some implementations, quiet hours can be configured as a time period with a start time and an end time. In some implementations, quiet hours can be derived from application data. For example, calendar data, alarm clock data, map data, etc. can be used to determine when quiet hours should be enforced. In some implementations, the device can be configured with exceptions to quiet hour notification suppression. In some implementations, the user can identify contacts to which the quiet hours notification suppression should not be applied.
Method for notification reminder, terminal, and storage medium
A method for notification reminder, a terminal, and a storage medium are provided, relating to the technical field of notification reminder. The method includes the following. A notification is received in a do not disturb (DND) mode, where the notification is at least one of: an incoming call notification, a short message notification, or an application notification. A contact corresponding to the notification is identified. Notification reminder is performed in a predetermined manner when the contact belongs to a preset contact group. Notification reminder is skipped when the contact does not belong to the preset contact group. The preset contact group is a group that allows notification reminder in the DND mode by default.
Venue owner-controllable per-venue service configuration
There are provided measures for venue owner-controllable per-venue service configuration. Such measures could comprise configuring a per-venue service model of services of a network operator for terminal devices of subscribers of the network operator on the basis of an input by a venue owner of a venue, the per-venue service model including at least one configurable parameter for defining a venue-based service for terminal devices of subscribers residing in a specified venue area of the venue, and controlling provision of services of the network operator to terminal devices or subscribers of terminal devices in accordance with the per-venue service model depending on applicability thereof for the service provision.
Managing connections of a user device
Systems, methods, and computer-readable medium are provided for managing connections of user devices. For example, two source devices may be configured to maintain a data stream with one another. The data stream may enable the two source devices to identify one or more connections between each other and at least a third device. In response to receiving an event that indicates content to be provided to the third device, the data stream may be used by the source devices to configure their network connections with the third device.