2026-03-16 - LD Munich - Qualcomm v. Network System Technologies - UPC_CFI_449/2024
- Aktenzeichen:
- UPC_CFI_449/2024
- Datum:
- Spruchkörper:
- Court of First Instance - Munich (DE) Local Division
- Art:
- Final Decision
- Parteien:
- Qualcomm Incorporated, Qualcomm Technologies, Inc., Qualcomm Germany GmbH v. Network System Technologies LLC
Kernaussage: The Munich LD revoked EP 1 552 669 (NoC address translation) for added matter and dismissed the infringement action in this third companion case to UPC_CFI_65/2024 and UPC_CFI_64/2024.
2026-03-16 - LD Munich - Qualcomm
v.
Network System Technologies - UPC_CFI_449/2024
notable
The Munich LD revoked EP 1 552 669 (NoC address translation) for added matter and dismissed the infringement action in this third companion case to UPC_CFI_65/2024 and UPC_CFI_64/2024. The court found two added matter defects: (1) 'network interface means coupled between one of the modules and the network' implied a structural distinction not derivable from the application, which only used 'associated to' (a functional description); (2) attributing the determination of the addressed module's selected location to the 'network interface' was not supported — only the 'address translation means' (a subcomponent of the network interface) was disclosed for this function. All four auxiliary requests failed for containing the same problematic features. Infringement was independently denied because the attacked embodiment's route/path information was not a 'single address' within claim feature 4.2, and no subsequent determination steps (features 5 and 6) were performed. Evidence production was denied on the same fishing expedition grounds as the companion cases.
Nichtigkeitsgründe
Art. 138 EPCAdded Matter
Patent invalid (this ground)Art. 123(2) EPC · Art. 138(1)(c) EPC
“The patent was revoked for added matter under Art. 138(1)(c)/123(2) EPC on two grounds: (1) 'coupled between' implied structural separation not derivable from the application's 'associated to' language, which was merely functional; (2) attributing the determination of the addressed module's location to the 'network interface' was not supported — only the address translation means (a subcomponent) was disclosed for this function. All auxiliary requests failed for containing the same features. [161]-[179]”