Railware, Inc. v. Peninsula Corridor Joint Powers Board — Court construes patent terms for railway worker safety system, rejecting indefiniteness challenges and adopting middle-ground constructions

Background

Railware sued the Peninsula Corridor Joint Powers Board (Caltrain) for patent infringement, asserting three patents: U.S. Patent Nos. 9,517,782, RE47,835, and RE49,115. The patents cover systems, apparatuses, and methods designed to protect railway field workers during track maintenance by requiring dispatchers to receive a code from field workers before removing blocks on track sections.

The technology addresses a safety problem: conventionally, dispatchers remotely set blocks on track sections under maintenance, but human error sometimes led to premature block removal, causing injuries and fatalities. The patents teach partially delegating control over block removal to field workers by requiring them to provide a code to the dispatcher.

The parties filed claim construction briefs and the court held a technology tutorial and claim construction hearing on October 9, 2026, with additional discussion at a hearing on October 30, 2026. The court then issued this order construing the disputed terms.

The Court’s Holding

The court construed several groups of disputed terms. For the 'code' terms (release code, removal code, secret release code, secret removal code, and secret code), the court rejected both parties' proposals and adopted a middle-ground construction: 'A code for releasing a block on a track that is not available to the dispatcher to release the block, but the code may become available if a releasing event occurs (e.g., the dispatcher receives the code from a railway field worker).' This construction rejected Caltrain's argument that the code must be 'random' and 'not known' to the dispatcher in perpetuity, while also rejecting Railware's 'not readily available' language as potentially indefinite. The court found Caltrain's indefiniteness argument moot in light of this construction.

For 'second secret code,' the court adopted Railware's construction: 'A code relayed from the remote user terminal or the railway field worker,' rejecting Caltrain's indefiniteness challenge. The court explained that while the 'secret code' and 'second secret code' are separate claim elements, they can match, and the '115 patent clearly describes where the second code comes from and how it relates to the stored code.

The court construed 'user terminal' and 'remote user terminal' as 'User terminal of a railway field worker,' rejecting Caltrain's narrower 'mobile user device' limitation. For 'railway control apparatus' and 'railway traffic control apparatus,' the court adopted 'A collection of hardware and software components that controls a railway or railway traffic,' rejecting Caltrain's 'dispatcher terminal' construction. The court construed 'a/the processor' as 'One or more processors, at least one of which is configured to perform the recited functions,' applying Federal Circuit precedent on indefinite articles. Finally, the court construed 'responsive to' as 'As the but-for cause thereof,' rejecting Caltrain's 'exclusively upon' construction as improperly requiring the event to be the only but-for cause.

Key Takeaways

• The court rejected indefiniteness challenges to the 'code' terms and 'second secret code,' finding the patents provided sufficient clarity about the scope and relationships of the claimed elements.
• Claim differentiation principles played a key role in several constructions, including the court's rejection of a 'random' limitation for the code terms and its refusal to limit 'user terminal' to mobile devices.
• The court applied the Federal Circuit's Salazar framework to construe 'a/the processor' as permitting multiple processors while requiring at least one processor to perform all recited functions.
• The court distinguished between 'but-for cause' and 'exclusively upon,' holding that 'responsive to' requires but-for causation but does not preclude intervening events or multiple but-for causes.
• The court declined to resolve whether the claims include a failsafe mechanism, leaving that question for another day while crafting a construction that does not foreclose the possibility.

Why It Matters

This claim construction order demonstrates how courts navigate competing constructions by rejecting extreme positions on both sides and crafting middle-ground interpretations grounded in the intrinsic evidence. The court's analysis of the 'code' terms illustrates the tension between avoiding indefiniteness and giving effect to the full scope of the claims, including embodiments where the dispatcher eventually learns the code.

The order also provides useful guidance on several recurring claim construction issues: the application of claim differentiation, the distinction between exemplary embodiments and claim limitations, the Salazar framework for indefinite articles, and the meaning of 'responsive to' as requiring but-for causation without excluding causal chains. These constructions will shape the scope of Railware's patent claims as the case proceeds to summary judgment or trial.