Desktop Alert Inc. v. Alertus Technologies, LLC

CourtDistrict Court, D. Maryland
DecidedAugust 14, 2024
Docket8:22-cv-03337
StatusUnknown

This text of Desktop Alert Inc. v. Alertus Technologies, LLC (Desktop Alert Inc. v. Alertus Technologies, LLC) is published on Counsel Stack Legal Research, covering District Court, D. Maryland primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Desktop Alert Inc. v. Alertus Technologies, LLC, (D. Md. 2024).

Opinion

IN THE UNITED STATES DISTRICT COURT FOR THE DISTRICT OF MARYLAND

* DESKTOP ALERT, INC., * * Plaintiff * * Civ. No. MJM-22-3337 v. * * ALERTUS TECHNOLOGIES, LLC, * * Defendant. * * * * * * * * * * * *

MEMORANDUM OPINION Desktop Alert, Inc. (“Desktop” or “Plaintiff”) filed this civil action against Alertus Technologies, LLC (“Alertus” or “Defendant”) for patent infringement. ECF 1 & 26. This matter is before the Court on Defendant’s Motion to Dismiss (ECF 27), Plaintiff’s Motion for Partial Summary Judgment (ECF 32),1 and Plaintiff’s Motion for Leave to File a Surreply (ECF 34). The motions are ripe for disposition, and no hearing is necessary. See Local Rule 105.6 (D. Md. 2023). For the reasons set forth below, the Court shall deny each of the pending motions. I. BACKGROUND2 Plaintiff is incorporated in the state of New York, with its principal place of business in Chatham, New Jersey. Am. Compl., ECF 26, ¶ 1. Defendant is a limited liability company organized in Maryland, with its principal place of business in Baltimore, Maryland. Id. ¶ 2. Plaintiff is the creator of Desktop Alert, “a network-based mass notification platform for sending

1 Plaintiff’s Motion for Partial Summary Judgment is styled in the alternative to its opposition to Defendant’s Motion to Dismiss. ECF 32. 2 The facts described herein are drawn from allegations in the Amended Complaint (ECF 26) and documents attached to the original Complaint (ECF 1). messages to individual computers over a virtual, public, or private network,” which was first released to the public in August 2003. Id. ¶¶ 5–6. Sometime thereafter, Defendant began offering its own program, entitled “Alertus Desktop.” Id. ¶ 12. Later, Defendant renamed its program “Alertus Desktop Alert.” Id. ¶ 13.

In or around 2009, Plaintiff developed a technique using the Desktop Alert program that “enabled it to receive time sensitive and critical ‘pull’ or ‘polling’ requests from one or more of the clients seeking the status of alert messages being sent to and received by the central server connected to the client via a network.” Id. ¶ 8. This technique “overcame a critical shortcoming” in the prior art. Id. ¶ 9. Plaintiff filed a provisional patent application for this method on July 1, 2010. Id. ¶ 16. The United States Patent and Trademark Office granted the application and issued Patent No. 9,172,765 (“the ‘765 Patent”) on October 27, 2015, of which Plaintiff is the present owner. Id. ¶¶ 9–11. Plaintiff provided notice of its patent application through two press releases, dated February 21, 2014, and January 22, 2016. Id. ¶ 38; ECF 1-5 (press releases). The ‘765 Patent contains two Independent Claims: Claims 1 and 10. ECF 1-1 (‘765 Patent)

at 12–14. Independent Claim 1 recites the following: An improved method for the dissemination of an alert message to a plurality of personal computers using a network communications protocol, said computers comprising clients, each said clients subscribing to a central server, said server comprising an alert message cache, said server adapted to receive and store alert messages, and said server adapted to generate and store alert ID numbers, said method comprising, a first triggering step comprises the use of a HTTP packet comprising a request for a Boolean value relating to whether there are new alert messages and said packet comprises approximately 20 bytes, a second step wherein said client contacts the central server and requests the value of said alert ID number in said memory, said value reflecting the number of alert messages received by said central server, a third step wherein said server transmits said value to said client, a fourth step wherein said client compares a stored value at the client with the value of the transmitted alert ID number, and if said transmitted value exceeds said stored value, a fifth step wherein said client transmits a second message to said server and requests for the server to transmit all unread alert messages in a GetUnread Alerts request from said server that are specific to said client, and if there are unread alert messages specific to said client in said server, a sixth step wherein said server sends to client all unread alert messages specific to the client, and, a further step wherein said client updates the stored value in its memory to reflect the number of additional unread alert messaged transmitted from said server to said client in response to said second message, and wherein, upon the reception of said unread alert messages in said sixth step, said alert messages are in instant message format and said client opens a window on a display panel to display said alert messages, wherein said communications protocol comprises protocols for the transmission of messages over the internet. Id. at 12:37–13:8. Independent Claim 10 similarly recites the following: A system for providing alert messages to a plurality of clients using a polling-based network, said system comprising a plurality of clients, at least one server in communication with said clients using a network connection, said central server provided with input devices to receive alert messages, and a database, said database for storing said alert messages, and said processor having programming instructions to create and store an alert ID value corresponding to alert messages Stored in said database, and said clients adapted to communicate with said server using an RPC communications protocol wherein said protocol further comprises a first triggering step comprises the use of a HTTP packet comprising a request for a Boolean value relating to whether there are new alert messages and said packet comprises approximately 20 bytes, and further communication from said client to said server requesting a GetAlert Messages using a SOAP communications protocol and wherein said client is transmitted an Alert ID message value from said server to said client, and if said Alert ID message value matches a stored message value, the client will further request from said server any alert messages to which it subscribes, and in response to said requests, said server transmits any unread alert messages and said unread alert message are in instant message format and upon the client’s reception of said unread alert messages said client opens a window on a display panel at said client, and wherein said communications protocol comprises protocols for the transmission of messages over the internet. Id. at 13:34–14:24. According to Defendant’s co-founder Blake Robertson, up until December 2014 (when he left the company), Defendant’s program suffered from server overuse during client requests, which would have been remedied by Plaintiff’s patented technique. Am. Compl. ¶ 14 (citing ECF 1-3). Around May 2020, Plaintiff’s CEO collaborated with employees of Defendant, during which Plaintiff’s “code and know-how for methods” were disclosed to Defendant. Id. ¶¶ 15–16. At the time Robertson left Defendant in December 2014, its program’s polling intervals were between ten and thirty seconds. Id. ¶ 23 (citing ECF 1-3). However, in a 2022 webinar, Defendant claimed to have polling intervals of as little as one second, id., and in advertisements, it described its program as able to “dynamically adjust polling intervals to optimize notification speed while maintaining critical stability,” id. ¶ 21 (citing ECF 1-2) (brackets removed). Plaintiff claims, upon information and belief, that Defendant uses a Boolean value polling method similar to that described in Claim 1 of the ‘765 Patent, and that it was able to reduce its polling interval to one second by following the steps and methods found within the ‘765 Patent. Id. ¶¶ 22, 24–25, 30–33. Plaintiff filed an initial Complaint for patent infringement against Defendant on December 13, 2022, ECF 1, and was granted leave to file an Amended Complaint on June 2, 2023. ECF 25 & 26. Defendant filed a Motion to Dismiss the Amended Complaint.

Free access — add to your briefcase to read the full text and ask questions with AI

Related

Le Roy v. Tatham
55 U.S. 156 (Supreme Court, 1853)
Diamond v. Diehr
450 U.S. 175 (Supreme Court, 1981)
Anderson v. Liberty Lobby, Inc.
477 U.S. 242 (Supreme Court, 1986)
Papasan v. Allain
478 U.S. 265 (Supreme Court, 1986)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Taltech Ltd. v. Esquel Apparel, Inc.
279 F. App'x 974 (Federal Circuit, 2008)
Harrods Limited v. Sixty Internet Domain Names
302 F.3d 214 (Fourth Circuit, 2002)
Bosiger v. US Airways, Inc.
510 F.3d 442 (Fourth Circuit, 2007)
Khoury v. Meserve
268 F. Supp. 2d 600 (D. Maryland, 2003)

Cite This Page — Counsel Stack

Bluebook (online)
Desktop Alert Inc. v. Alertus Technologies, LLC, Counsel Stack Legal Research, https://law.counselstack.com/opinion/desktop-alert-inc-v-alertus-technologies-llc-mdd-2024.