IP Library Granted Patent US 12,401,728
Granted Patent B2
US 12,401,728 · App. 18/525,658 · Granted Aug 26, 2025

Push notification management

Inventors: Alex Joseph Castro (Cypress, CA); Michael Brian Murray (Marina del Rey, CA); William Wu (Marina del Rey, CA)
Assignee: Snap Inc.
H04L67/55H04L51/04H04L51/224H04L51/52
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 12,401,728
App. No.
18/525,658
Granted
Aug 26, 2025
Kind
B2
Abstract

A push notification mechanism at a mobile user device provides for automated limiting of the rate of production of push notification alerts (such as an audible alert or a vibratory alert) and/or push notifications responsive to the occurrence of chat events relevant to a chat application hosted by the user device. Some chat events automatically trigger suppression periods during which push notification alerts are prevented for subsequent chat events that satisfy predefined suppression criteria. Such push notification and/or alert limiting can be performed separately for separate users, chat groups, and/or chat event types.

Claims (39)

1. A method comprising:

providing a push notification service with respect to an application that is hosted by a user device and that provides messaging functionality with a plurality of users via a messaging platform associated with said application, the push notification service being configured to automatically generate respective push notification alerts in response to receiving, while the user device is in an inactive mode, notification of predefined alert-triggering events, each push notification alert comprising an audible and/or a tactile indication generated by the user device; and

in an automated operation performed using one or more computer processor devices configured therefor, dynamically limiting push notification alerts based on predefined alert suppression criteria, such that respective push notification alerts are suppressed for at least some of the events, wherein the alert suppression criteria define a respective type-specific suppression period for each event type in a predefined set of message event types, such that the respective type-specific suppression period for two or more of the predefined set of event types differ in length,

wherein said two or more message event types with different respective suppression periods are selected from the group consisting of: text messages, non-text messages, typing events, status messages, screenshots, and calling events, and

wherein the limiting of push notification alerts comprises:

identifying a particular message event as a suppression trigger event for a particular one of the set of message event types; and

generating a push notification alert for the suppression trigger event; and responsive to identifying the suppression trigger event, performing type-specific alert suppression for a suppression interval that extends for respective predefined type-specific suppression period subsequent to the suppression trigger event, such that push notification alerts are universally suppressed for any message event that is of said particular type and that occurs during the suppression interval.

2. The method of claim 1 , wherein a shorter type-specific suppression period applies to non-text messages in the form of media message events than text message events.

3. The method of claim 1 , wherein no suppression period applies to calling events.

4. The method of claim 1 , wherein the respective type-specific suppression periods for different message event types are customizable via a user interface.

5. The method of claim 1 , wherein events of an exempt event type do not trigger suppression periods.

6. The method of claim 1 , wherein the type-specific alert suppression is performed regardless of sender identity.

7. The method of claim 1 , wherein the type-specific alert suppression is performed regardless of chat group.

8. The method of claim 1 , further comprising detecting the message event type based on message content analysis.

9. The method of claim 1 , further comprising allowing user customization of the predefined alert suppression criteria per contact.

10. A system comprising:

one or more computer processor devices; and

memory storing instructions to configure the one or more computer processor devices, when executing the instructions, to perform operations comprising:

providing a push notification service on a user device hosting an application that provides messaging functionality with a plurality of users via a messaging platform associated with said application, the push notification service being configured to automatically generate respective push notification alerts in response to receiving, while the user device is in an inactive mode, notification of predefined alert-triggering events, each push notification alert comprising an audible and/or a tactile indication generated by the user device; and

in an automated operation, dynamically limiting push notification alerts based on predefined alert suppression criteria, such that respective push notification alerts are suppressed for at least some of the events, wherein the alert suppression criteria define a respective type-specific suppression period for each event type in a predefined set of message event types, such that the respective type-specific suppression period for two or more of the predefined set of event types differ in length,

wherein said two or more message event types with different respective suppression periods are selected from the group consisting of: text messages, non-text messages, typing events, status messages, screenshots, and calling events, and

wherein the limiting of push notification alerts comprises:

identifying a particular message event as a suppression trigger event for a particular one of the set of message event types; and

generating a push notification alert for the suppression trigger event; and responsive to identifying the suppression trigger event, performing type-specific alert suppression for a suppression interval that extends for respective predefined type-specific suppression period subsequent to the suppression trigger event, such that push notification alerts are universally suppressed for any message event that is of said particular type and that occurs during the suppression interval.

11. The system of claim 10 , wherein a shorter type-specific suppression period applies to non-text messages in the form of media message events than text message events.

12. The system of claim 10 , wherein no suppression period applies to calling events.

13. The system of claim 10 , wherein the respective type-specific suppression periods for different message event types are customizable via a user interface.

14. The system of claim 10 , wherein events of an exempt event type do not trigger suppression periods.

15. The system of claim 10 , wherein the type-specific alert suppression is performed regardless of sender identity.

16. The system of claim 10 , wherein the type-specific alert suppression is performed regardless of chat group.

17. The system of claim 10 , further comprising detecting the message event type based on message content analysis.

18. The system of claim 10 , wherein the instructions further configure the one or more computer processor devices to allow user customization of rules the predefined alert suppression criteria per contact.

19. A non-transitory computer readable storage medium storing instructions for causing a machine, when executing the instructions, to perform operations comprising:

at a user device, providing a push notification service with respect to an application that is hosted by the user device and that provides messaging functionality with a plurality of users via a messaging platform associated with said application, the push notification service being configured to automatically generate respective push notification alerts in response to receiving, while the user device is in an inactive mode, notification of predefined alert-triggering events, each push notification alert comprising an audible and/or a tactile indication generated by the user device; and

in an automated operation, dynamically limiting push notification alerts based on predefined alert suppression criteria, such that respective push notification alerts are suppressed for at least some of the events, wherein the alert suppression criteria define a respective type-specific suppression period for each event type in a predefined set of message event types, such that the respective type-specific suppression period for two or more of the predefined set of event types differ in length,

wherein said two or more message event types with different respective suppression periods are selected from the group consisting of: text messages, non-text messages, typing events, status messages, screenshots, and calling events, and

wherein the limiting of push notification alerts comprises:

identifying a particular message event as a suppression trigger event for a particular one of the set of message event types; and

generating a push notification alert for the suppression trigger event; and responsive to identifying the suppression trigger event, performing type-specific alert suppression for a suppression interval that extends for respective predefined type-specific suppression period subsequent to the suppression trigger event, such that push notification alerts are universally suppressed for any message event that is of said particular type and that occurs during the suppression interval.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 11, 2025
From: CASTRO, ALEX JOSEPH; MURRAY, MICHAEL BRIAN; WU, WILLIAM
To: SNAP INC.
Reel/Frame 071383/0006 →
Continuity (4)
Continuation 18104628 · Feb 1, 2023
Continuation 15837946 · Dec 11, 2017
Provisional Application 62432679 · Dec 11, 2016
Related Publication 20240098158A1 · Mar 21, 2024
References Cited (71)
US 6038295A · Mattes · 2000 [cited by applicant]
US 6980909B2 · Root et al. · 2005 [cited by applicant]
US 7173651B1 · Knowles · 2007 [cited by applicant]
US 7411493B2 · Smith · 2008 [cited by applicant]
US 7535890B2 · Rojas · 2009 [cited by applicant]
US 8131597B2 · Hudetz · 2012 [cited by applicant]
US 8199747B2 · Rojas et al. · 2012 [cited by applicant]
US 8332475B2 · Rosen et al. · 2012 [cited by applicant]
US 8718333B2 · Wolf et al. · 2014 [cited by applicant]
US 8724622B2 · Rojas · 2014 [cited by applicant]
US 8862676B1 · Bilinski · 2014 [cited by examiner]
US 8874677B2 · Rosen et al. · 2014 [cited by applicant]
US 8909679B2 · Root et al. · 2014 [cited by applicant]
US 8995433B2 · Rojas · 2015 [cited by applicant]
US 9040574B2 · Wang et al. · 2015 [cited by applicant]
US 9055416B2 · Rosen et al. · 2015 [cited by applicant]
US 9100806B2 · Rosen et al. · 2015 [cited by applicant]
US 9100807B2 · Rosen et al. · 2015 [cited by applicant]
US 9137049B2 · Varoglu · 2015 [cited by examiner]
US 9191776B2 · Root et al. · 2015 [cited by applicant]
US 9204252B2 · Root · 2015 [cited by applicant]
US 9443227B2 · Evans et al. · 2016 [cited by applicant]
US 9473428B1 · Koum · 2016 [cited by examiner]
US 9489661B2 · Evans et al. · 2016 [cited by applicant]
US 9491134B2 · Rosen et al. · 2016 [cited by applicant]
US 9503409B2 · Heiby · 2016 [cited by examiner]
US 10033673B1 · Phanshikar · 2018 [cited by examiner]
US 10135768B2 · Shin · 2018 [cited by examiner]
US 10135941B2 · DeLuca · 2018 [cited by examiner]
US 10587749B2 · Drake · 2020 [cited by examiner]
US 11588913B1 · Castro et al. · 2023 [cited by applicant]
US 20080096597A1 · Vempati et al. · 2008 [cited by applicant]
US 20090002127A1 · Kraft · 2009 [cited by examiner]
US 20110202598A1 · Evans et al. · 2011 [cited by applicant]
US 20110298614A1 · Bells · 2011 [cited by applicant]
US 20120072844A1 · Lefrancois des Courtis · 2012 [cited by examiner]
US 20120209924A1 · Evans et al. · 2012 [cited by applicant]
US 20140082093A1 · Savage · 2014 [cited by applicant]
US 20140173430A1 · Clavel et al. · 2014 [cited by applicant]
US 20140241517A1 · Varoglu et al. · 2014 [cited by applicant]
US 20140244714A1 · Heiby · 2014 [cited by applicant]
US 20140289644A1 · Clarke et al. · 2014 [cited by applicant]
US 20140370857A1 · Bovis · 2014 [cited by examiner]
US 20150121412A1 · McRae · 2015 [cited by examiner]
US 20150379224A1 · Rosen · 2015 [cited by examiner]
US 20160112358A1 · Ghafourifar · 2016 [cited by examiner]
US 20160164810A1 · Wolz · 2016 [cited by examiner]
US 20160315902A1 · Silva et al. · 2016 [cited by applicant]
US 20170272568A1 · Bovis · 2017 [cited by examiner]
US 20170374075A1 · Boval · 2017 [cited by examiner]
US 20180081514A1 · Bostick · 2018 [cited by examiner]
US 20190104097A1 · Lalka · 2019 [cited by examiner]
US 20200327559A1 · Sharma · 2020 [cited by examiner]
US 20230179677A1 · Castro et al. · 2023 [cited by applicant]
CA 2887596A1 · 2015 [cited by applicant]
“U.S. Appl. No. 15/837,946, 312 Amendment filed Jan. 10, 2023”, 7 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Final Office Action mailed Mar. 25, 2021”, 22 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Final Office Action mailed Apr. 6, 2022”, 24 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Non Final Office Action mailed Aug. 6, 2021”, 24 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Non Final Office Action mailed Aug. 27, 2020”, 22 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Non Final Office Action mailed Dec. 30, 2019”, 27 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Notice of Allowance mailed Oct. 13, 2022”, 6 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, PTO Response to Rule 312 Communication mailed Jan. 24, 2023”. [cited by applicant]
“U.S. Appl. No. 15/837,946, Response filed Jan. 6, 2022 to Non Final Office Action mailed Aug. 6, 2021”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Response filed Apr. 30, 2020 to Non Final Office Action mailed Dec. 30, 2019”, 11 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Response filed Jun. 25, 2021 to Final Office Action mailed Mar. 25, 2021”, 11 pages. [cited by applicant]
“U.S. Appl. No. 15/837,946, Response filed Aug. 8, 2022 to Final Office Action mailed Apr. 6, 2022”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 15/837,946, Response filed Dec. 28, 2020 to Non Final Office Action mailed Aug. 27, 2020”, 12 pgs. [cited by applicant]
“U.S. Appl. No. 18/104,628, Corrected Notice of Allowability mailed Nov. 6, 2023”, 9 pgs. [cited by applicant]
“U.S. Appl. No. 18/104,628, Notice of Allowance mailed Jul. 26, 2023”, 12 pgs. [cited by applicant]
Leyden, John, “This SMS will self-destruct in 40 seconds”, [Online] Retrieved from the Internet: <URL: http://www.theregister.co.uk/2005/12/12/stealthtext/>, (Dec. 12, 2005), 1 pg. [cited by applicant]