Railware, Inc. v. National Railroad Passenger Corporation

CourtDistrict Court, S.D. New York
DecidedAugust 23, 2023
Docket1:22-cv-05013
StatusUnknown

This text of Railware, Inc. v. National Railroad Passenger Corporation (Railware, Inc. v. National Railroad Passenger Corporation) is published on Counsel Stack Legal Research, covering District Court, S.D. New York primary law. Counsel Stack provides free access to over 12 million legal documents including statutes, case law, regulations, and constitutions.

Bluebook
Railware, Inc. v. National Railroad Passenger Corporation, (S.D.N.Y. 2023).

Opinion

UNITED STATES DISTRICT COURT SOUTHERN DISTRICT OF NEW YORK RAILWARE, INC., Plaintiff, 22 Civ. 5013 (KPF) -v.- OPINION AND ORDER NATIONAL RAILROAD PASSENGER CORPORATION, doing business as AMTRAK, Defendant. KATHERINE POLK FAILLA, District Judge: Plaintiff Railware, Inc. contends that Defendant Amtrak infringed Railware’s patented train traffic control system, which was designed to ensure that railway workers are out of the path of incoming train traffic by permitting a dispatcher to unblock track sections only after workers verify that it is safe to do so. According to Plaintiff, Defendant’s own railway control systems infringe its patents by replicating this safety feature without authorization or license. Defendant now moves to dismiss this action on the ground that the relevant patents are directed to an abstract idea and therefore are ineligible for patent protection. Ultimately, the Court cannot agree with Defendant’s arguments at this stage of the litigation and on this record, and accordingly it denies Defendant’s motion. BACKGROUND1 A. Factual Background 1. Plaintiff’s Patented Train Traffic Control System Certain railroad maintenance tasks require workers to physically enter the track area and thereby put themselves directly in the path of potential train

traffic. (AC ¶ 13). A worker’s failure to timely vacate a track can have devastating — even deadly — consequences. Prior to the advent of centralized train control systems, railroads employed various safety systems, including alarms, to warn workers of approaching trains. (Id.). Centralized control systems made this work safer by consolidating control of railroad tracks in the hands of remote dispatchers. (AC ¶ 14). Such dispatchers can temporarily divert train traffic away from sections of track that are undergoing maintenance by blocking and unblocking track sections. (Id.).

This system is imperfect, however, inasmuch as “[h]uman error could and did lead to blocks being removed prematurely by the dispatcher, either because the dispatcher falsely believed that the railway work was complete, or because the dispatcher intended to remove a different block and mistakenly removed a block on a track section that was still undergoing work.” (Id.).

1 This Opinion draws its facts from the Amended Complaint (the “AC” (Dkt. #11)), the well-pleaded allegations of which are taken as true for the purposes of this Opinion, and the exhibits attached thereto, including U.S. Patent No. 9,517,782 (the “’782 Patent” (Dkt. #11-1)), U.S. Patent No. RE47,835 (the “’835 Patent” (Dkt. #11-2)), and U.S. Patent No. RE49,115 (the “’115 Patent” (Dkt. #11-3)). For ease of reference, the Court refers to Defendant’s memorandum of law in support of its motion to dismiss as “Def. Br.” (Dkt. #29); to Plaintiff’s memorandum of law in opposition as “Pl. Opp.” (Dkt. #31); and to Defendant’s reply memorandum as “Def. Reply” (Dkt. #34). Plaintiff, a New York company, purveys Dispatch X, “one of the premier train traffic control systems in the world.” (AC ¶¶ 11, 46). A notable feature of Dispatch X is a patented safety technology known as the Enhanced Employee

Protection System (“EEPS”). (Id. ¶ 2 & ¶ 10 n.6). EEPS was created by Railware principal Ross Pirtle to mitigate safety risks to railroad maintenance workers. (Id. ¶ 12). EEPS differentiates Dispatch X from other centralized railroad control systems in at least one key respect: rather than localizing control over railroad tracks in a single dispatcher, it “requir[es] railway traffic controllers and employees on the ground to cooperate to lift a block.” (Id. ¶ 15). Generally speaking, EEPS functions as follows: each time a dispatcher places a block over a section of railroad track, an electronic system generates a

unique code and sends that code to a worker in the field. (Id.). The block cannot be removed until the roadway worker sends the code back to the dispatcher. (Id.). In theory, this process reduces mistakes and miscommunications in railway control by dividing the power to unblock railroad track sections between workers on the tracks and remote dispatchers. Plaintiff became the sole owner of two patents related to EEPS through assignment from Pirtle: U.S. Patent Number 9,517,782 (the “’782 Patent”) and U.S. Patent Number 9,403,545 (the “’545 Patent”). (AC ¶ 4). Subsequently,

Plaintiffs obtained U.S. Reissue Patents RE47,835 (the “’835 Patent”) and RE49,115 (the “’115 Patent,” and collectively with the other named patents, the “Asserted Patents”), both of which are reissues of the ’545 Patent. (Id. ¶¶ 4, 17). Since at least October 21, 2020, Railware has published the patent numbers of the Asserted Patents in the header bar of its Dispatch X system and on its website. (Id. ¶ 30). Each of the Asserted Patents is “directed to methods and systems for

centralized railway control.” (AC ¶¶ 18-20). More specifically, claim 5 of the ’782 Patent teaches a system whereby (i) a roadway worker possesses a device with an interactive user interface that displays information received from a railway control apparatus; (ii) through an interactive terminal, a user can request that the railway control apparatus place a block on one or more specified track sections; (iii) also through that terminal, the railway control apparatus generates a release code and transmits it to an electronic contact address accessible by the roadway worker; and (iv) the railway control

apparatus can only remove the block upon receiving the release code from the roadway worker via the terminal. (Id. ¶ 19). Similarly, claim 19 of the ’835 Patent teaches “a railway traffic control apparatus of a centralized railway control system configured for centralized control of traffic of a centrally controllable railway network including plural railways and a plurality of railway traffic interlocks.” (AC ¶ 19). That apparatus is comprised of three components: (i) a user interface of a centralized railway traffic control apparatus that places blocks on one or more

specified track sections across the plural railways; (ii) generation of a block removal code and transmission of that code to a unique contact for the relevant railway worker; and (iii) removal of the block only upon entry of the removal code. (Id.). Claim 20 of the ’115 Patent is familiar, as it largely tracks the relevant claims of the ’782 and ’835 Patents. It teaches a centralized control of plural railways, this time through the use of:

[i] a processor for controlling a plurality of track sections in the railway network, wherein each track section is associated with a corresponding interlock and is disposed in any of said plural railways of said railway network that is managed by centralized control operation from the railway control apparatus, the processor controlling, by said centralized control operation, one or more interlocks amongst the plurality of railway interlocks dispersed in said plural railways of said railway network, to block railway traffic to one or more specified track sections; and [ii] a memory device storing computer-executable instructions, wherein execution of the computer-executable instructions by the processor causes the railway control apparatus to: (a) receive a selection of at least one track section amongst the plurality of track sections; (b) transmit a block signal to the corresponding interlock associated with the at least one selected track section, to place a block on the selected track section by said centralized control operation from the railway control apparatus; (c) generate a secret code associated with the at least one selected track section; and (d) transmit the secret code to a remote user terminal.

(AC ¶ 20).

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

Related

Gottschalk v. Benson
409 U.S. 63 (Supreme Court, 1972)
Bell Atlantic Corp. v. Twombly
550 U.S. 544 (Supreme Court, 2007)
Ashcroft v. Iqbal
556 U.S. 662 (Supreme Court, 2009)
Ddr Holdings, LLC v. hotels.com, L.P.
773 F.3d 1245 (Federal Circuit, 2014)
In re Cipro Cases I & II
348 P.3d 845 (California Supreme Court, 2015)
Internet Patents Corporation v. Active Network, Inc.
790 F.3d 1343 (Federal Circuit, 2015)
Enfish, LLC v. Microsoft Corporation
822 F.3d 1327 (Federal Circuit, 2016)
Rapid Litigation Management Ltd. v. CellzDirect, Inc.
827 F.3d 1042 (Federal Circuit, 2016)
Wbip, LLC v. Kohler Co.
829 F.3d 1317 (Federal Circuit, 2016)
Electric Power Group, LLC v. Alstom S.A.
830 F.3d 1350 (Federal Circuit, 2016)
Affinity Labs of Texas, LLC v. Directv, LLC
838 F.3d 1253 (Federal Circuit, 2016)
Intellectual Ventures I LLC v. Symantec Corp.
838 F.3d 1307 (Federal Circuit, 2016)
Fairwarning Ip, LLC v. Iatric Systems, Inc.
839 F.3d 1089 (Federal Circuit, 2016)
Smartflash LLC v. Apple Inc.
680 F. App'x 977 (Federal Circuit, 2017)

Cite This Page — Counsel Stack

Bluebook (online)
Railware, Inc. v. National Railroad Passenger Corporation, Counsel Stack Legal Research, https://law.counselstack.com/opinion/railware-inc-v-national-railroad-passenger-corporation-nysd-2023.