軟體發明常使用means plus function來撰寫每個step,可是功能手段用語需於說明書中揭露對應的結構,只是軟體發明的結構是什麼?滿有趣的,不是電腦,處理器等,而是流程圖。
Allvoice appealed after the Texas court found its means-plus-function claim elements indefinite under 35 U.S.C. § 112.
PHOSITA Creativity: A means plus function element is considered indefinite if a PHOSITA “would be unable to recognize the structure in the specification and associate it with the corresponding function in the claim.”
On appeal, the CAFC took a cue from KSR v. Teleflex — finding that a PHOSITA is creative and “not an automation.” For software cases, this means that the specification “need only disclose adequate defining structure to render the bounds of the claim understandable to one of ordinary skill in the art. Here, the CAFC found that the algorithm flowchart (see figure) was sufficient structure.
使用功能手段用語於說明書中應該對應的結構揭露,而於軟體發明中,計算流程圖作為軟體發明的結構,是足夠的結構揭露。
【更新】 【2016/09/21】
2181
Identifying and Interpreting a 35 U.S.C. 112(f) or Pre-AIA 35 U.S.C. 112, Sixth
Paragraph Limitation [R-07.2015]
對於該演算法的描述必須足夠,流程圖即是結構。
Applicant may express
the algorithm in any understandable terms including as a mathematical formula,
in prose, in a flow chart, or “in any other manner that provides sufficient structure.” Finisar, 523 F.3d at 1340, 86 USPQ2d at
1623; see also Intel Corp. v. VIA Techs., Inc., 319 F.3d 1357, 1366, 65 USPQ2d
1934, 1941 (Fed. Cir. 2003); In re Dossel, 115 F.3d 942, 946-47, 42 USPQ2d
1881, 1885 (Fed. Cir.1997); Typhoon Touch Inc. v. Dell Inc., 659 F.3d 1376,
1385, 100 USPQ2d 1690, 1697 (Fed. Cir. 2011); In re Aoyama, 656 F.3d at 1306,
99 USPQ2d at 1945.
沒有留言:
張貼留言