TENSTREET, LLC v. DRIVERREACH, LLC

District Court, S.D. Indiana·Decided September 30, 2019·No. 1:18-cv-03633·Unknown

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF INDIANA INDIANAPOLIS DIVISION

TENSTREET, LLC, an Oklahoma limited ) liability company, ) ) Plaintiff, ) ) v. ) No. 1:18-cv-03633-JRS-TAB ) DRIVERREACH, LLC, an Indiana limited ) liability company, ) ) Defendant. )

Order on Motion to Dismiss (ECF No. 14)

Defendant DriverReach, LLC moves to dismiss Plaintiff Tenstreet, LLC’s com- plaint for failure to state a claim upon which relief can be granted. (ECF No. 14.) The motion, now fully briefed and ripe for decision is granted for the following rea- sons. I. Background1

Plaintiff Tenstreet, LLC (“Tenstreet”) develops and sells software products and services for the transportation industry. (Compl. ¶ 7, ECF No. 1.) One such product, XchangeTM, is a network that facilitates the sharing of job applicant verification data between past and prospective employers of commercial truck drivers. (Id.) Tenstreet acquired a patent for XchangeTM on March 27, 2012, U.S. Patent No. 8,145,575 (the

1 Consistent with the Rule 12(b)(6) standard, Plaintiff’s non-conclusory allegations are taken as true for purposes of Tenstreet’s motion to dismiss. “’575 patent”), entitled “Peer to Peer Sharing of Job Applicant Information.” (Compl. ¶ 8, ECF No. 1.) The ‘575 patent explains that federal regulations require employers of commercial

truck drivers to complete a verification process before hiring a driver. (‘575 Patent, ECF No. 1-1 at 1:18-20.) Part of this process involves verifying the driver’s employ- ment history from the preceding three years. (Id. at 1:20-21.) Before Tenstreet’s product, XchangeTM, was created, employers would verify this data by contacting the driver’s previous employer via fax, phone, or through a commercial employment his- tory database. (Id. at 1:21-24.) The ‘575 patent alleges that this method was “time

consuming” and “expensive” for the employers and often resulted in errors that driv- ers were unable to correct. (Id. at 1:25-29.) XchangeTM sought to streamline this process by creating a “method for peer-to- peer sharing of job applicant data over a network.” (Id. at 5:42-43.) Claim 1 of the ‘575 patent is representative and dispositive of the asserted claims.2 It describes the

2 Tenstreet asserts “at least Claim 1” of the ‘575 patent. (Pl.’s Br. ¶ 16. ECF No. 1.) Claim 1 is independent and claims 2-30 are dependent. (‘575 Patent, ECF No. 1-1 at 5:42-8:18.) The added limitations of the dependent claims do not affect the result of the patentability of the ‘575 patent. McRO, Inc. v. Bandai Namco Games Am. Inc., 837 F.3d 1299, 1307 n.3 (Fed. Cir. 2016). The Federal Circuit has held that addressing each claim is unnecessary when “all the claims are substantially similar and linked to the same abstract idea,” Con- tent Extraction & Transmission, LLC v. Wells Fargo Bank, Nat’l. Ass’n, 776 F.3d 1343, 1348 (Fed. Cir. 2014), despite Supreme Court language suggesting otherwise, Alice Corp. Pty. Ltd. v. CLS Bank Int’l., 573 U.S. 208, 217 (2014) (“[We] consider the elements of each claim both individually and as an ordered combination to determine whether the additional ele- ment transform the nature of the claim into a patent-eligible application.”) (internal quota- tions and citations omitted). Nonetheless, Tenstreet does not present any meaningful argu- ment for the distinctive significance of the dependent claims. (Pl.’s Br., ECF No. 24 at 24.); Electric Power Grp., LLC v. Alstom S.A., 830 F.3d 1350, 1352 (Fed. Cir. 2016). network as a “computerized central exchange that interfaces with requesters, provid- ers, and job applicants.” (Id. at 1:40-42.) Requesters are prospective employers who seek verification data about a job applicant. (Id. at 1:42-44.) Providers are former

employers who possess the verification data of a job applicant. (Id. at 1:44-46.) The exchange manages the interactions of each participant by providing access to a com- munication channel depending on the classification of the requester, provider, or job applicant seeking access to the exchange. (Id. at 1:48-51.) The communication chan- nel may be an online interface, a facsimile interface, or an electronically stored data interface. (Id. at 1:52-54.)

Typically, the exchange will receive a request from a prospective employer, a re- quester, to verify the employment data of a job applicant. (Id. at 1:58-60.) The job applicant must then authorize this verification. (Id. at 1:60-61.) Next, the request is routed to the past employer, the provider, through the communication channel of that provider. (Id. at 1:63-65.) The provider then submits the verification data to the exchange, which then routes the completed verification data to the requester. (Id. at 1:66-67; 2:1.)

Additionally, job applicants and providers can store the verification data in a cen- tralized database to complete subsequent requests. (Id. at 2:11-13.) Requesters, pro- viders, and job applicants may check the status of a verification transaction with the exchange. (Id. at 2:16-18.) The ‘575 patent alleges that this network improves upon the previous verification process by managing “the complexity associated with different parties participating in different ways with the network so that individual partners do not have to manage it for themselves.” (Id. at 2:64-67.) Moreover, the patent claims that the software provides additional protections for drivers against inaccurate data being shared with

prospective employers, beyond what the regulations provide. (Id. at 3:56-63.) By using XchangeTM, drivers can review and correct information before it is sent to the prospective employer. (Id. at 2:7-10.) Tenstreet alleges that Defendant DriverReach, LLC (“DriverReach”) has infringed the ‘575 patent by selling its own employment verification product, VOE Plus Solu- tions. (Compl. ¶ 2, ECF No. 1.) DriverReach has moved to dismiss on the ground

that the ‘575 patent is patent-ineligible subject matter under 35 U.S.C. § 101. (Def.’s Motion to Dismiss, ECF No. 14.) II. Legal Standard

To survive a motion to dismiss for failure to state a claim, a plaintiff must allege “enough facts to state a claim to relief that is plausible on its face.” Bell Atl. Corp. v. Twombly, 550 U.S. 544, 570 (2007). In considering a Rule 12(b)(6) motion to dismiss, the court takes the complaint’s factual allegations as true and draws all reasonable inferences in the plaintiff’s favor. Orgone Capital III, LLC v. Daubenspeck, 912 F.3d 1039, 1044 (7th Cir. 2019). The court need not “accept as true a legal conclusion couched as a factual allegation.” Papasan v. Allain, 478 U.S. 265, 286 (1986). In addition to the allegations in the complaint, on a motion to dismiss, the court may consider “documents that are attached to the complaint, documents that are cen- tral to the complaint and are referred to in it, and information that is properly subject to judicial notice.” Williamson v. Curran, 714 F.3d 432, 436 (7th Cir. 2013). “[D]oc- uments attached to a motion to dismiss are considered part of the pleadings if they are referred to in the plaintiff’s complaint and are central to his claim.’” McCready v.

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

TENSTREET, LLC v. DRIVERREACH, LLC, (S.D. Ind. 2019).

TENSTREET, LLC v. DRIVERREACH, LLC (TENSTREET, LLC v. DRIVERREACH, LLC) — published by Counsel Stack Legal Research, free access to 12M+ legal documents.

Related

Foman v. Davis
371 U.S. 178 (Supreme Court, 1962)
Papasan v. Allain
478 U.S. 265 (Supreme Court, 1986)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
188 LLC v. Trinity Industries, Incorporated
300 F.3d 730 (Seventh Circuit, 2002)
Ann Bogie v. Joan AlexandraSanger
705 F.3d 603 (Seventh Circuit, 2013)
Lisa Williamson v. Mark Curran, Jr.
714 F.3d 432 (Seventh Circuit, 2013)
Genetic Technologies Limited v. Merial L.L.C.
818 F.3d 1369 (Federal Circuit, 2016)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Tli Communications LLC v. Av Automotive, L.L.C.
823 F.3d 607 (Federal Circuit, 2016)
Electric Power Group, LLC v. Alstom S.A.
830 F.3d 1350 (Federal Circuit, 2016)
McRO, Inc. v. Bandai Namco Games America Inc.
837 F.3d 1299 (Federal Circuit, 2016)
Fairwarning Ip, LLC v. Iatric Systems, Inc.
839 F.3d 1089 (Federal Circuit, 2016)
Orgone Capital III, LLC v. Keith Daubenspeck
912 F.3d 1039 (Seventh Circuit, 2019)