Unreported / Non-Citable
Background
Railware sued the Peninsula Corridor Joint Powers Board, doing business as Caltrain, for patent infringement in the Northern District of California. The asserted patents—U.S. Patent Nos. 9,517,782, RE47,835, and RE49,115—cover systems, apparatuses, and methods designed to protect railway field workers during track maintenance. The technology addresses a safety problem: conventionally, dispatchers remotely set blocks on track sections under maintenance and reroute trains, but human error sometimes led to blocks being removed prematurely, causing injuries and fatalities. The patents teach providing field workers with a code that the dispatcher must receive before removing a block, effectively delegating partial control over block removal to the workers on the ground.
The parties filed claim construction briefs and the court held a technology tutorial and claim construction hearing on October 9, 2026, followed by additional discussion at a hearing on October 30, 2026. The parties agreed on the level of ordinary skill in the art: a person with at least a bachelor's degree in electrical, mechanical, industrial, or related engineering, plus at least two years of experience in railway safety, railway operations, or railway control systems, with education and experience potentially substituting for one another. The court adopted this undisputed standard for purposes of the claim construction order.
The Court’s Holding
The court construed six groups of disputed terms. For the 'code' terms (release code, removal code, secret release code, secret removal code, and secret code), the court rejected Caltrain's arguments that the codes must be 'random' and 'not known' to the dispatcher, and also rejected Railware's 'not readily available' proposal. Instead, it adopted the construction Railware offered at the October 30 hearing: '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).' The word 'random' appears only in a dependent claim, the specifications describe random codes only as examples, and Caltrain's 'not known' construction was untenable because the claims contemplate the dispatcher receiving the code; Caltrain's indefiniteness argument was moot once 'readily' was excluded.
For 'second secret code,' the court adopted 'A code relayed from the remote user terminal or the railway field worker,' rejecting Caltrain's indefiniteness argument as 'not a close call.' For 'user terminal' and 'remote user terminal,' it adopted 'User terminal of a railway field worker,' rejecting Caltrain's 'mobile user device' limit under claim differentiation principles. For 'railway control apparatus' and 'railway traffic control apparatus,' it adopted 'A collection of hardware and software components that controls a railway or railway traffic.' For 'a/the processor,' it construed the term as 'One or more processors, at least one of which is configured to perform the recited functions' under Federal Circuit precedent. Finally, for 'responsive to,' it adopted 'As the but-for cause thereof,' rejecting Caltrain's 'exclusively upon' reading because an event can have multiple but-for causes and the claims do not preclude intervening steps.
Key Takeaways
- The court rejected both parties' more extreme claim construction proposals and instead adopted middle-ground constructions, including one proposed by Railware at a post-briefing hearing to address the court's concerns about indefiniteness and clarity.
- The court found that Caltrain's indefiniteness arguments were either moot or clearly without merit, particularly as to the 'second secret code' term, which the court said was 'not a close call' given the claims' express teaching of comparing the second code to the stored code.
- Claim differentiation principles played a significant role in two rulings: the court declined to read 'random' into the code terms because a dependent claim expressly recited random generation, and declined to equate 'user terminal' with 'mobile user device' because other claims used the latter term.
- The court applied recent Federal Circuit precedent, including Salazar v. AT&T Mobility, to construe 'a/the processor' as permitting multiple processors while requiring that at least one processor perform all recited functions, rejecting Railware's pre-Salazar authorities.
- The court construed 'responsive to' as requiring but-for causation rather than exclusive causation, reasoning that an event can have multiple but-for causes and that the claims do not preclude intervening steps between the triggering event and the block release.
Why It Matters
This claim construction order resolves the meaning of key disputed terms in a patent infringement case involving railway worker safety technology, setting the framework for the parties' infringement and invalidity contentions going forward. The court's rejection of Caltrain's indefiniteness arguments preserves the asserted claims for trial, and its adoption of constructions that neither party fully endorsed shows the court crafting its own interpretations grounded in the intrinsic record. The order illustrates the primacy of intrinsic evidence over extrinsic testimony from other proceedings, the role of claim differentiation, and the Federal Circuit's evolving guidance on 'a/the' terms and causal language like 'responsive to,' with the 'processor' analysis reflecting the continuing influence of Salazar.