L4T Innovations LLC v. Reolink Innovation, Ltd. and Reolink Digital Technology Co., Ltd., No. 2:26-cv-00981 (E.D. Tex., Marshall Division), is a 12-page complaint for patent infringement filed October 30, 2026, with one count and a jury demand. The complaint says L4T Innovations LLC is a Michigan limited liability company with an office in Saint Joseph, Michigan, and that it is the assignee of all rights, title, and interest in U.S. Patent 11,189,321. It alleges, on information and belief, that Reolink Innovation, Ltd. is a corporation organized and existing under the laws of Hong Kong, with a principal place of business in Kowloon, Hong Kong, and that Reolink Digital Technology Co., Ltd. is a corporation organized and existing under the laws of China, with a principal place of business in Shenzhen, China. It further alleges, on information and belief, that those entities research, develop, manufacture, and sell Reolink-branded cameras, doorbells, accessories, and software worldwide, including in the United States, and that, directly and/or indirectly through subsidiaries, affiliates, distributors, and agents, they develop, design, manufacture, import, distribute, market, offer to sell, and/or sell infringing products and services in the United States and in Texas, including in the Eastern District of Texas.
The patent and the asserted claims
The complaint asserts U.S. Patent 11,189,321, titled Retrospective Capture Trigger, which issued November 30, 2021, from Application No. 16/821,423, filed March 17, 2020. It says that application was a continuation of international applications PCT/US2018/053805 and PCT/US2018/053807, both filed October 1, 2018, and that those applications arose from provisional applications filed October 2, 2017, and October 13, 2017. The complaint asserts at least claims 1, 6, 8, 9, 14, 15, and 16, as detailed in an evidence-of-use exhibit attached to the complaint.
Claim 1 covers an event marking device with a housing, a microcontroller, a memory, a real-time clock, a communication interface, and a trigger circuit arranged to be enabled by a user to identify an event for recording. The microcontroller is configured to read the real-time clock and write a corresponding real-time datum in the memory upon receiving enablement of the trigger circuit by the user, and to read the real-time data from the memory and output the real-time datum via the communication interface when that interface is operatively coupled to an external device, whereby the real-time datum causes the external device to preserve a recording captured at the time of the enablement of the trigger circuit. Claim 6 covers the event marking device of claim 1, further comprising a visible indicator capable of being energized to indicate readiness to accept trigger circuit enablement.
Claim 8 covers a method of generating real-time clock data with a real-time clock of an event marking device; generating a trigger signal with a trigger circuit of the device; identifying, from the real-time clock data with a microcontroller of the device, a real time corresponding to receipt of the trigger signal; writing, with the microcontroller, trigger signal data to a memory of the device indicating that real time; and outputting, with a communication interface of the device, trigger event data including the time of generating the trigger signal to an external device, whereby outputting the trigger event data causes the external device to preserve a recording captured at the time of the enablement of the trigger circuit. Claim 9 covers the method of claim 8, in which generating the trigger signal includes generating it based on input received from a user. Claim 14 covers the method of claim 8, further comprising generating the trigger signal in response to manipulation of a switch by a user.
Claim 15 covers a device with a trigger circuit disposed in a housing and configured to generate a trigger signal, a real-time clock disposed in the housing and configured to generate real-time clock data corresponding to a real time, a memory disposed in the housing and configured to store data in a computer readable media, a microcontroller coupled to the trigger circuit, the real-time clock, and the memory and configured to receive the trigger signal, reference the real-time clock data upon receiving the trigger signal, and write trigger event data to the memory indicating a real time at which the trigger signal was generated, and a communication interface configured to output the trigger event data to an external device, whereby the external device is made to store or transmit recorded content corresponding to the real time of the trigger event. Claim 16 covers the device of claim 15, in which the trigger circuit includes a switch configured to be operated by the user.
The accused products
The complaint defines the accused products as a system comprising Reolink Video Doorbell PoE products, including at least model D340P, and Reolink Video Doorbell WiFi products, including at least model D340W (together, the Reolink Doorbells); separate Reolink Network Video Recorders, including without limitation the Reolink Network Video Recorder RLN12W, Reolink Home Hub, Home Hub Pro, Home Hub Mini, and other models identified as compatible with the Reolink Doorbells (the Reolink NVRs); and associated firmware, mobile applications (including the Reolink App), and desktop software (the Reolink Software Products).
It alleges that the doorbells contain embedded microprocessors performing on-device AI-based person, vehicle, and package detection, real-time H.264/H.265 video encoding at 5 megapixels, event time-stamping, and network communication, and that they incorporate a 6-second pre-recording buffer. It alleges that when a user presses the doorbell button, the doorbell records the event with a timestamp and transmits the event data, including the timestamp and an associated video clip with the pre-buffered footage, over a PoE Ethernet or WiFi interface to an external Reolink NVR, which preserves the recording. Based upon public information, it says the defendants own, operate, advertise, and/or control the websites reolink.com and support.reolink.com.
The count, knowledge, and prayer
Count I alleges that the defendants have directly infringed and continue to directly infringe one or more claims of the '321 Patent, either literally or under the doctrine of equivalents, including at least claims 1, 6, 8, 9, 14, 15, and 16, by making, using, selling, offering to sell, importing, providing, supplying, and/or distributing the accused products. It alleges that, since at least the time of receiving the complaint, the defendants have induced end users, including customers and retail purchasers, to infringe, including claims 1 and 8, through advertising, manuals, tutorials, and technical support that instruct users how to use the Reolink Doorbell with the Reolink NVRs, and that they have done so with knowledge of the patent and with knowledge that the induced acts constitute infringement. It also alleges that, since at least the time of receiving the complaint, the defendants have contributed to infringement, that the accused products have features specially designed to be used in an infringing way, and, upon information and belief, that those products have no substantial non-infringing uses.
The complaint alleges that the defendants had knowledge of the '321 Patent at least as of the date they were notified of the filing of this action, and that their actions are at least objectively reckless as to the risk of infringing a valid patent. The prayer asks for a judgment that one or more claims of the '321 Patent have been infringed, either literally or under the doctrine of equivalents, by the defendants or others acting in concert with them; damages (past, present, and future, including treble damages for alleged willful infringement), costs, expenses, and pre-judgment and post-judgment interest; compulsory ongoing licensing fees; a declaration that the case is exceptional and an award of reasonable attorneys' fees and costs under 35 U.S.C. § 285; and all other and further relief as the court may deem just and proper.
The complaint pleads subject matter jurisdiction under 28 U.S.C. §§ 1331 and 1338(a), and venue under 28 U.S.C. §§ 1391 and 1400(b), including because, it says, the defendants are foreign corporations and may be sued in any judicial district under 28 U.S.C. § 1391(c)(3). It also alleges acts of infringement in the district and, upon information and belief, that the defendants have placed the accused products into the stream of commerce through their websites, online marketplaces, and brick-and-mortar retailers, including a retail store in Longview, Texas. It pleads personal jurisdiction based in part on what it calls the defendants' "substantial and pervasive business" in Texas and the district, from which, it says, they derive substantial revenue.
Other suits on the patent
L4T Innovations has also asserted the '321 Patent in other suits in the Eastern District of Texas. The complaints in Nos. 2:25-cv-00394 (filed April 16, 2025), 2:26-cv-00014 (filed January 8, 2026), 2:26-cv-00091 (filed February 4, 2026), 2:26-cv-00187 (filed March 9, 2026), and 2:26-cv-00582 (filed July 15, 2026) each assert the '321 Patent. The dockets in Nos. 2:25-cv-00394, 2:26-cv-00014, 2:26-cv-00091, and 2:26-cv-00187 show an order dismissing the case.
What to watch next
Watch for an answer or a Rule 12 motion. The case can end at any time, including by settlement or voluntary dismissal.