DCT

2:26-cv-12780

Railware Inc v. New Jersey Transit Corp

Log In
Key Events
Amended Complaint
complaint Intelligence

I. Executive Summary and Procedural Information

  • Parties & Counsel:
  • Case Identification: 1:24-cv-05537, S.D.N.Y., 08/06/2024
  • Venue Allegations: Plaintiff alleges venue is proper in the Southern District of New York because Defendant NJ Transit maintains a regular and established place of business at New York Penn Station and has committed acts of infringement within the district.
  • Core Dispute: Plaintiff alleges that Defendant’s centralized train control and dispatch systems infringe three patents related to technology for ensuring the safety of railway field workers.
  • Technical Context: The technology at issue involves a cooperative system between a central dispatcher and a field worker to prevent the accidental removal of a "block" that protects a section of track where maintenance is being performed.
  • Key Procedural History: The complaint alleges that Plaintiff provided Defendant with actual notice of the parent patent to the portfolio as early as November 2016. The complaint also references a prior lawsuit filed by Plaintiff against Amtrak in June 2022 for infringement of the same patents, alleging this event provided further notice to NJ Transit. Additionally, the complaint notes that the Federal Railroad Administration (FRA) has issued safety advisories and rules encouraging railroads to adopt "redundant signal protections," such as the technology allegedly covered by the patents-in-suit.

Case Timeline

Date Event
2013-10-21 Priority Date for '782, '835, and '115 Patents
2013-11-01 Alleged first use of "EEPS" mark in commerce by Railware
2014-11-25 FRA issues Safety Advisory 2014-02 recommending electronic safety technologies
2016-06-10 FRA issues Final Rule requiring redundant signal protections for roadway workers
2016-08-05 Notice of Allowance for application that would become the '782 Patent
2016-11-22 Railware allegedly provides actual notice of U.S. Patent No. 9,403,545 to NJ Transit
2016-12-13 U.S. Patent No. 9,517,782 ('782 Patent) issues
2017-07-01 FRA deadline for railroads to evaluate and identify redundant signal protections
2018-01-01 FRA deadline for railroads to implement redundant signal protections
2020-02-04 U.S. Reissue Patent No. RE47,835 ('835 Patent) issues
2020-10-21 Railware allegedly begins marking its products and website with patent numbers
2022-06-15 Railware files suit against Amtrak for infringement of the Asserted Patents
2022-06-28 U.S. Reissue Patent No. RE49,115 ('115 Patent) issues
2024-08-06 Complaint filed

II. Technology and Patent(s)-in-Suit Analysis

U.S. Patent No. 9,517,782 - “Tools for Railway Traffic Control”

  • Patent Identification: U.S. Patent No. 9,517,782, “Tools for Railway Traffic Control,” issued December 13, 2016 (the ’782 Patent).

The Invention Explained

  • Problem Addressed: The patent's background describes the danger that arises when a remote train dispatcher makes a human error and prematurely removes a "block" from a section of track, which is intended to prevent trains from entering an area where railway workers are performing maintenance. This can lead to serious injury or death '782 Patent, col. 2:25-34 Compl. ¶¶18-20
  • The Patented Solution: The invention introduces a system where safety authority is shared between the central dispatcher and the field worker. A central "railway control apparatus" generates a unique "release code" when a block is placed and transmits it to the field worker's mobile device. The block cannot be removed until the field worker provides that same release code back to the central system, thus requiring the worker's active participation to clear the track '782 Patent, abstract '782 Patent, col. 2:47-65
  • Technical Importance: This approach fundamentally altered the safety protocol by converting a single-user (dispatcher-only) process into a cooperative, multi-device process, adding a technological failsafe controlled by the person physically present on the track Compl. ¶22

Key Claims at a Glance

  • The complaint asserts independent method claim 5 Compl. ¶61
  • The essential elements of claim 5 are:
    • Configuring a mobile user device of a railway field worker to display information from a railway control apparatus and permit the worker to respond to prompts.
    • Providing a terminal user interface for a terminal user (e.g., a dispatcher) to request the railway control apparatus to place a block on specified track sections.
    • Generating, by the railway control apparatus, a release code and transmitting it to an electronic contact address accessible by the field worker.
    • Permitting the block to be removed by the railway control apparatus only upon receiving the release code from the user terminal in return.
  • The complaint reserves the right to assert other claims Compl. ¶62, n.42

U.S. Reissue Patent No. RE47,835 - “Tools for Railway Traffic Control”

  • Patent Identification: U.S. Reissue Patent No. RE47,835, “Tools for Railway Traffic Control,” issued February 4, 2020 the ’835 Patent This is a reissue of U.S. Patent No. 9,403,545.

The Invention Explained

  • Problem Addressed: Similar to the ’782 Patent, the invention addresses the life-threatening risks to railway workers from the premature or mistaken removal of track blocks by remote dispatchers ’835 Patent, col. 2:23-34
  • The Patented Solution: The patent describes a method for controlling railway access where a central apparatus places a block on a track. A "removal code" is generated and sent to a field worker after the system determines the worker's electronic contact address by accessing a "rail personnel contact database." The block can only be removed upon entry of this code at the central control apparatus, ensuring the worker is involved in the release process ’835 Patent, abstract ’835 Patent, col. 15, ll. 5-38
  • Technical Importance: The technology established a formal, database-driven communication link for delivering a security code to a specific field worker, creating an auditable and technologically enforced safety check.

Key Claims at a Glance

  • The complaint asserts independent method claim 19 Compl. ¶117
  • The essential elements of claim 19 are:
    • Providing a user interface of the railway traffic control apparatus with a "block placing part" to place a block on track sections.
    • Generating a removal code, determining a field worker's electronic contact address by accessing a "rail personnel contact database," and transmitting the code to that address.
    • Permitting the block to be removed only upon entry of the removal code by the centralized control operation.
  • The complaint reserves the right to assert other claims Compl. ¶118, n.81

U.S. Reissue Patent No. RE49,115 - “Tools for Railway Traffic Control”

  • Patent Identification: U.S. Reissue Patent No. RE49,115, “Tools for Railway Traffic Control,” issued June 28, 2022 the ’115 Patent This is also a reissue of U.S. Patent No. 9,403,545.
  • Technology Synopsis: The ’115 Patent claims a railway control apparatus (a system claim) rather than a method. The apparatus comprises a processor and memory and is configured for centralized control of a railway network. When a track section is selected for blocking, the apparatus generates a "secret code" associated with that section and transmits the code to a "remote user terminal" Compl. ¶¶27, 178
  • Asserted Claims: The complaint asserts independent apparatus claim 20 Compl. ¶178
  • Accused Features: The complaint alleges that NJ Transit's RailwayNet/AIM system, as a whole, constitutes the infringing "railway control apparatus" Compl. ¶¶180-181

III. The Accused Instrumentality

Product Identification

The accused instrumentality is NJ Transit's implementation and operation of a centralized train control system, identified as "Wabtec's RailwayNetSM or Advanced Information Management ('AIM') platform" Compl. ¶14

Functionality and Market Context

  • The system is used by NJ Transit for train dispatching and traffic control across its rail network, including at its Penn Station Central Control ("PSCC") and Rail Operations Center ("ROC") Compl. ¶¶47, 66 The complaint alleges the system includes an "enhanced employee protection" functionality, which NJ Transit internally refers to as the "Enhanced Employee Protection System (EEPS)" Compl. ¶57
  • The EEPS functionality requires a railway worker to possess a "company issued cell phone." To remove a track block, the worker must provide a "four digit PIN (EEPS code)" to the dispatcher. The complaint alleges this PIN is given to the employee "through their company cell phone" after a block is placed Compl. ¶57 Compl. ¶72 A screenshot from an "NJT EEPS Guidance Sheet" included in the complaint describes this process. Compl. ¶57

IV. Analysis of Infringement Allegations

'782 Patent Infringement Allegations

Claim Element (from Independent Claim 5) Alleged Infringing Functionality Complaint Citation Patent Citation
configuring a mobile user device of a railway field worker to provide a device user interface to display information received via a network from a railway control apparatus and to permit the railway field worker to respond to prompts displayed thereon; NJ Transit provides "company issued cell phone[s]" to workers for the EEPS system. These phones are configured to receive an "EEPS code" and allow the worker to provide it to the dispatcher. ¶72; ¶75 col. 12:15-23
providing a terminal user interface on a terminal to permit a terminal user of the terminal request the railway control apparatus to place a block on one or more specified track sections... NJ Transit dispatchers use terminals at control centers (PSCC and ROC) to place blocks on track sections (e.g., place tracks in "foul time"). The complaint includes photographs of these control centers. ¶80; ¶82; ¶88 col. 12:24-31
generating by the railway control apparatus a release code and transmitting the release code to an electronic contact address accessible by the railway field worker via operation of the user interface of the user terminal; and The "back office" of the accused system allegedly generates a "four digit PIN (EEPS code)" which is then "given" to the employee "through their company cell phone." ¶94; ¶96; ¶100 col. 12:32-38
permitting the block to said one or more track sections to be removed by the railway control apparatus only upon receiving the release code from the user terminal in return. The dispatcher is only able to remove the block after the worker provides the EEPS code. The complaint includes a screenshot from a guidance document stating this rule. ¶101; ¶102; ¶104 col. 12:39-44

'835 Patent Infringement Allegations

Claim Element (from Independent Claim 19) Alleged Infringing Functionality Complaint Citation Patent Citation
providing a user interface of the railway traffic control apparatus, including a block placing part to place a block on one or more specified track sections... Dispatchers at NJ Transit's control centers use a terminal user interface to place blocks on track sections, which the complaint alleges constitutes the "block placing part." ¶136; ¶141; ¶142 col. 15:15-28
generating a removal code, determining an electronic contact address of the railway field worker by accessing a rail personnel contact database...and transmitting the removal code to the electronic contact address...; and The complaint alleges the system's "back office" generates the EEPS code and that NJ Transit maintains a "rail personnel contact database" to manage employee communications and authentication. ¶148; ¶150; ¶153 col. 15:29-35
permitting the block to said one or more track sections to be removed only upon entry of the removal code by said centralized control operation from the railway traffic control apparatus. The system allegedly permits block removal only after the dispatcher receives and enters the EEPS code provided by the field worker. ¶162; ¶163; ¶165 col. 15:36-43
  • Identified Points of Contention:
    • Scope Questions: The case may turn on whether the accused RailwayNet/AIM system, a commercial product integrated into NJ Transit's operations, maps onto the claimed "railway control apparatus." A question for the court will be whether the distributed components of the accused system (e.g., "back office," dispatcher terminals, worker cell phones) collectively meet the limitations of the claimed single "apparatus."
    • Technical Questions: A key technical question is how the "EEPS code" is conveyed to the worker. The claims require "transmitting the release code to an electronic contact address." The complaint states the code is "given" to the employee "through their company cell phone" Compl. ¶72, which is ambiguous. The analysis may focus on whether this is a data transmission (e.g., SMS) versus a verbal communication, and whether the latter falls within the claim scope. The complaint's system diagram, showing voice and data flows to the "Roadway Worker," suggests this will be a point of dispute Compl. p. 27, Figure 4

V. Key Claim Terms for Construction

  • The Term: "release code" / "removal code" / "secret code"

    • Context and Importance: The infringement theory equates NJ Transit's "four digit PIN (EEPS code)" with this claim term. The term's construction is critical because it defines the security token at the heart of the invention. Practitioners may focus on whether a reusable or semi-static PIN satisfies the requirements of a "release code" or "secret code," which could imply a one-time, dynamically generated value.
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The specification refers to the code simply as a "cipher which is random, pseudo-random, secret, etc." '782 Patent, col. 6:58-60, suggesting the exact nature is not limiting.
      • Evidence for a Narrower Interpretation: The specification states, "A new random cipher may be generated for each instance of traffic blocking" '782 Patent, col. 6:60-62, which could support an argument that the code must be unique for each blocking event, potentially distinguishing it from a more static PIN.

  • The Term: "transmitting the release code to an electronic contact address"

    • Context and Importance: This limitation defines the delivery mechanism for the security code. The infringement case depends on showing that the way NJ Transit's workers receive their "EEPS code" meets this requirement. The dispute will likely center on the specific method of delivery (e.g., data message vs. voice call).
    • Intrinsic Evidence for Interpretation:
      • Evidence for a Broader Interpretation: The claim language is general. The term "electronic contact address" is not explicitly defined, and could arguably include a phone number for any form of electronic communication.
      • Evidence for a Narrower Interpretation: The specification provides examples such as transmitting a message via "email or messaging" '782 Patent, col. 3:20-22 and shows a text-based message in Figure 10. This may support an interpretation requiring a data-based message rather than a voice communication.

VI. Other Allegations

  • Indirect Infringement: The complaint alleges inducement of infringement under 35 U.S.C. § 271(b). The factual basis is that NJ Transit provides instructions and directions to its own dispatchers and users on how to operate the accused RailwayNet/AIM system and its EEPS functionality, which allegedly causes them to perform the steps of the patented methods Compl. ¶108 Compl. ¶169 Compl. ¶253
  • Willful Infringement: The complaint alleges willful infringement based on both pre-suit and post-suit knowledge. The allegations assert that NJ Transit had actual knowledge of the patent portfolio since at least November 22, 2016, from direct correspondence with Railware Compl. ¶37 It further alleges knowledge based on industry awareness, Railware's patent marking since October 2020, and knowledge of a similar lawsuit Railware filed against Amtrak in 2022 Compl. ¶¶43-46

VII. Analyst’s Conclusion: Key Questions for the Case

  • A core issue will be one of definitional scope: can the claim term "transmitting... to an electronic contact address," which the patent specification exemplifies with email and messaging, be construed to cover the process where a worker is "given" a PIN "through their company cell phone," particularly if that process involves voice communication?
  • A key evidentiary question will be one of technical operation: does the accused EEPS functionality, which uses a "four digit PIN," meet the claim requirements for a "release code" or "secret code," particularly in light of specification language suggesting a new random code is generated for each blocking event?
  • A central question for damages will be one of willfulness: given the complaint's detailed allegations of pre-suit notice dating back to 2016, including licensing discussions and explicit identification of the parent patent, the court will need to determine whether NJ Transit’s continued use of the accused system was objectively reckless, potentially exposing it to enhanced damages.