IP Library › Granted Patent US 12,244,484
Granted Patent B2
US 12,244,484 · App. 18/051,411 · Granted Mar 4, 2025

Interspersed message batching in a database system

Inventors: Michael Aurelio (San Francisco, CA); Eric Paul Wittke (San Francisco, CA); Laurel Knell (San Francisco, CA); Bradly Zavakos (Indianapolis, IN); Abigail Kutruff (San Francisco, CA); Jon Belkowitz (San Francisco, CA)
Assignee: Salesforce, Inc.
H04L43/16G06F16/9017H04L65/612H04L67/10H04L47/50
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,244,484
App. No.
18/051,411
Granted
Mar 4, 2025
Kind
B2
Abstract

A message batching configuration may be determined for transmitting a message to recipients. The message batching configuration may include two or more message batches, a respective recipient count for each message batch, a respective time delay between each message batch, and a performance metric for evaluating the message. The message is transmitted in accordance with the message batching configuration. The transmission of subsequent message batches is halted when it is determined that the designated performance metric fails to meet a designated performance metric threshold.

Claims (37)

1. A computer-implemented method comprising:

receiving via a communication interface a message for transmission to a plurality of recipients;

determining via a processor a message batching configuration for the message, the message batching configuration including a plurality of message batches for transmitting the message, the message batching configuration including a respective recipient count for each of the message batches, the message batching configuration including a designated performance metric for evaluating the message;

transmitting the message to a respective subset of the recipients via a network in accordance with the respective recipient count;

in response to the designated performance metric being less than a designated performance metric threshold, reducing the respective recipient count for a subsequent message batch; and

transmitting the message to the reduced number of respective recipients the subsequent message batch via the network.

2. The method recited in claim 1 , wherein each subset of the recipients is determined by randomly selecting recipients from a database table.

3. The method recited in claim 2 , wherein the message batching configuration includes one or more criteria for selecting the recipients from the database table.

4. The method recited in claim 2 , wherein the database table is stored in a multitenant database system within an on-demand computing services environment configured to provide computing services to a plurality of organizations.

5. The method recited in claim 1 , wherein the designated performance metric is a click through rate.

6. The method recited in claim 1 , wherein the determining the message batching configuration comprises providing for increasing respective recipient count for each successive message batch.

7. The method recited in claim 1 , further comprising applying a function over a plurality of performance metrics, the plurality of performance metrics including the designated performance metric.

8. A system configured to perform a method, the system comprising:

a processor; and

memory, the memory storing instructions to cause the processor to execute a method, the method comprising:

receiving via a communication interface a message for transmission to a plurality of recipients;

determining via a processor a message batching configuration for the message, the message batching configuration including a plurality of message batches for transmitting the message, the message batching configuration including a respective recipient count for each of the message batches, the message batching configuration including a designated performance metric for evaluating the message;

transmitting the message to a respective subset of the recipients via a network in accordance with the respective recipient count;

in response to the designated performance metric being less than a designated performance metric threshold, reducing the respective recipient count for a subsequent message batch; and

transmitting the message to the reduced number of respective recipients the subsequent message batch via the network.

9. The system recited in claim 8 , wherein each subset of the recipients is determined by randomly selecting recipients from a database table.

10. The system recited in claim 9 , wherein the message batching configuration includes one or more criteria for selecting the recipients from the database table.

11. The system recited in claim 9 , wherein the database table is stored in a multitenant database system within an on-demand computing services environment configured to provide computing services to a plurality of organizations.

12. The system recited in claim 8 , wherein the designated performance metric is a click through rate.

13. The system recited in claim 8 , wherein the determining the message batching configuration comprises providing for increasing respective recipient count for each successive message batch.

14. The system recited in claim 8 , further comprising applying a function over a plurality of performance metrics, the plurality of performance metrics including the designated performance metric.

15. A non-transitory computer readable medium configured to cause a processor to perform a method, the method comprising:

receiving via a communication interface a message for transmission to a plurality of recipients;

determining via a processor a message batching configuration for the message, the message batching configuration including a plurality of message batches for transmitting the message, the message batching configuration including a respective recipient count for each of the message batches, the message batching configuration including a designated performance metric for evaluating the message;

transmitting the message to a respective subset of the recipients via a network in accordance with the respective recipient count;

in response to the designated performance metric being less than a designated performance metric threshold, reducing the respective recipient count for a subsequent message batch; and

transmitting the message to the reduced number of respective recipients the subsequent message batch via the network.

16. The non-transitory computer readable medium recited in claim 15 , wherein each subset of the recipients is determined by randomly selecting recipients from a database table.

17. The non-transitory computer readable medium recited in claim 16 , wherein the message batching configuration includes one or more criteria for selecting the recipients from the database table.

18. The non-transitory computer readable medium recited in claim 16 , wherein the database table is stored in a multitenant database system within an on-demand computing services environment configured to provide computing services to a plurality of organizations.

19. The non-transitory computer readable medium recited in claim 15 , wherein the designated performance metric is a click through rate.

20. The non-transitory computer readable medium recited in claim 15 , wherein the determining the message batching configuration comprises providing for increasing respective recipient count for each successive message batch.

Assignments (2)
CHANGE OF NAME Recorded Aug 4, 2026
From: SALESFORCE.COM, INC.
To: SALESFORCE, INC.
Reel/Frame 076118/0548 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 21, 2022
From: AURELIO, MICHAEL; WITTKE, ERIC PAUL; KNELL, LAUREL; ZAVAKOS, BRADLY; KUTRUFF, ABIGAIL; BELKOWITZ, JON
To: SALESFORCE.COM, INC.
Reel/Frame 062176/0359 →
Continuity (2)
Continuation 16882183 · May 22, 2020
Related Publication 20230077698A1 · Mar 16, 2023
References Cited (50)
US D403674S · Arora · 1999 [cited by applicant]
US D473566S · Platz · 2003 [cited by applicant]
US D652427S · Willekes · 2012 [cited by applicant]
US D736822S · Tursi · 2015 [cited by applicant]
US D754194S · Su · 2016 [cited by applicant]
US D766293S · Rubio · 2016 [cited by applicant]
US D773483S · Leventhal · 2016 [cited by applicant]
US D774522S · Joukov · 2016 [cited by applicant]
US D775141S · Chaplin · 2016 [cited by applicant]
US D776675S · Ohta · 2017 [cited by applicant]
US D816686S · Rapp · 2018 [cited by applicant]
US D828391S · Cabot · 2018 [cited by applicant]
US D834616S · Hu · 2018 [cited by applicant]
US D845966S · Shivaji-Rao · 2019 [cited by applicant]
US D847144S · Einspahr · 2019 [cited by applicant]
US D851657S · Franklin · 2019 [cited by applicant]
US D852815S · Gavenman · 2019 [cited by applicant]
US D859433S · Kim · 2019 [cited by applicant]
US 10404923B1 · Pena · 2019 [cited by applicant]
US D870770S · Montgomery · 2019 [cited by applicant]
US D876445S · Ting · 2020 [cited by applicant]
US 10609185B2 · Bliss · 2020 [cited by applicant]
US D883997S · Einspahr · 2020 [cited by applicant]
US D886834S · Chitalia · 2020 [cited by applicant]
US 20050015492A1 · Kumbalimutt · 2005 [cited by examiner]
US 20080126516A1 · Holt · 2008 [cited by examiner]
US 20110107374A1 · Roberts · 2011 [cited by examiner]
US 20110274261A1 · Casalaina · 2011 [cited by examiner]
US 20140122726A1 · Jafry · 2014 [cited by examiner]
US 20140380177A1 · Gutermuth · 2014 [cited by applicant]
US 20160019597A1 · Smith · 2016 [cited by examiner]
US 20160280040A1 · Connell · 2016 [cited by examiner]
US 20160300425A1 · Devaraj · 2016 [cited by applicant]
US 20180219830A1 · O'Brien · 2018 [cited by examiner]
US 20200099771A1 · Hsu · 2020 [cited by applicant]
US 20210264921A1 · Reece · 2021 [cited by examiner]
U.S. Appl. No. 29/740,040, Restriction Requirement mailed Aug. 31, 2021, 7 pgs. [cited by applicant]
U.S. Appl. No. 29/740,041, Restriction Requirement mailed Aug. 30, 2021, 7 pgs. [cited by applicant]
5 Keys to Successful Pipeline Management—Buckley, https://www.newbreedrevenue.com/blog/pipeline-management-success ( Year: 2015). [cited by applicant]
Bioinformatics pipeline for high-throughput analysis of KeyPoint—researchgate, https://www.researchgate.net/figure/Bioinformatics-pipeline-for-high-throughput-analysis-of-KeyPoint-sequence-runs_fig8_241978 (Year: 2009). [cited by applicant]
Flow chart explaining the data processing pipeline—Researchgate, https://www.researchgate.net/figure/ Flow-chart-explaining-the-data-processing-pipeline_fig1_304536244 (Year: 2016). [cited by applicant]
Introducing AWS Icons for AWS Architecture Diagrams—Creately, https://creately.com/blog/announcements/ aws-architecture-diagrams-icons/amp/ (Year: 2013). [cited by applicant]
U.S. Appl. No. 29/740,039, Restriction Requirement mailed Aug. 27, 2021, 7 pgs. [cited by applicant]
Office Action dated Apr. 8, 2022 for U.S. Appl. No. 29/740,039 (pp. 1-5). [cited by applicant]
Office Action dated Apr. 8, 2022 for U.S. Appl. No. 29/740,040 (pp. 1-5). [cited by applicant]
Office Action dated Apr. 11, 2022 for U.S. Appl. No. 29/740,041 (pp. 1-6). [cited by applicant]
Notice of Allowance dated Jul. 21, 2022 for U.S. Appl. No. 29/740,039 (pp. 1-7). [cited by applicant]
Notice of Allowance dated Jul. 21, 2022 for U.S. Appl. No. 29/740,040 (pp. 1-7). [cited by applicant]
Notice of Allowance dated Jul. 21, 2022 for U.S. Appl. No. 29/740,041(pp. 1-7). [cited by applicant]
Office Action (Notice of Allowance and Fees Due (PTOL-85)) dated Aug. 5, 2022 for U.S. Appl. No. 16/882,183 (pp. 1-7). [cited by applicant]