- Inari Agriculture, Inc. v. Corteva Agriscience LLCNo claims unpatentablePTAB · Nov 18, 2025 · IPR2024-01014 · APJ Zhenyu Yang · IPR · Final written decision
Petitioner did not show claims 1–8 unpatentable because they are entitled to the 2004 priority date, making Barbour unavailable as prior art.
RulingsFinal written decision- Disclosure Requirements (§112) › Enablement (Wands, Amgen full scope)Entitled to earlier dateDecided for patent owner
“For a claim to a biological material, the enablement requirement of § 112, first paragraph, does not require such assured access to a microorganism deposit as of the filing date; what is required is assurance of access (to the microorganism culture by the public upon issuance of a patent on the application) prior to or during the pendency of the application, so that, upon issuance of a U. S. patent on the application, the public will, in fact, receive something in return for the patent grant. Feldman, 517 F.2d at 1355. Patent Owner has persuaded us that such exception not only applies to a deposit, but also extends to a biological material known and readily available. See 52 Fed. Reg. 34080, 34081. In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art.” slip op. at 15
- Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner
“In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art. Because all of Petitioner’s challenges rely on Barbour (Pet. 6), all those challenges fail.” slip op. at 15
- Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference not prior artNot shown unpatentable
“In this case, it is undisputed that TC1507 germplasm was known and readily available to the public by Barbour’s publication date in 2006 (Pet. 49–53), years before the 2014 issuance date of the ’378 patent (Ex. 1001, code 45). Thus, based on the record developed through trial, we agree with Patent Owner that the 2004 application satisfies the enablement requirement as of its application date in 2004. PO Resp. 16–18 (citing 52 Fed. Reg. 34080, 34081). As a result, the challenged claims are entitled to the 2004 priority date and, thus, Barbour does not qualify as prior art. Because all of Petitioner’s challenges rely on Barbour (Pet. 6), all those challenges fail.” slip op. at 15
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“would understand that the term “‘flanked by’ permits overlap between the expression cassette and the DNA sequence it is flanked by.” Pet. 24–26. Patent Owner does not propose any claim construction. PO Resp. 6–7. On this record and for purposes of this Decision, we see no need to expressly construe any claim term.” slip op. at 9
Patent outcomesUS 8,901,378 not shown unpatentableClaim construction§ 102 anticipation§ 112 disclosurecites PhillipsPatents in suitUS 8,901,378 - Adidas AG v. Nike, Inc.No claims unpatentablePTAB · Oct 19, 2017 · IPR2016-00922 · APJ James B Arpin · IPR · Final written decision
Petitioner failed to prove claims 1–9, 11–19, and 21 unpatentable as obvious over Reed and Nishida because it did not adequately explain why a skilled artisan would combine their teachings.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“appropriate factors identified by our reviewing court and utilized by other panels to assess the level of ordinary skill in the art. Id. at 17–18. We agree with Petitioner that it is not necessary to consider every factor or to weigh the factors equally in order to assess the level of ordinary skill in the art. Reply 2 (quoting In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995)). Here, we may rely on Petitioner’s declarant’s testimony (Ex. 1003 ¶ 34) and the teachings of the prior art to evaluate Petitioner’s assessment of the level of ordinary skill in the art. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). In particular, Reed and Nishida identify the types of problems encountered in the art prior art solutions to these problems, and the sophistication of the technology. E.g., Ex. 1006, 1:13–55; Ex. 1009, 1:10– 36; see, e.g., Ex. 1007, 1:8–32, 2:12–64; Ex. 1008, 1:11–54; Ex. 1010, 145– 160; see also Ex. 1010, Preface (“The aim of this book is to combine in a single volume the fundamental principles of weft and warp knitting in such a manner that its contents are useful to readers in education, industry or commerce. It thus [fulfills] the long felt need for a comprehensive up-to-date textbook explaining this important sector of textile technology.”).” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“unitary construction” means “a textile element having a unitary construction and having a first area and a second area.” Pet. 6. As Petitioner notes, this is the construction that this panel gave to the same term appearing in the substitute claims of the ’011 patent. adidas AG v. Nike, Inc., Case IPR2013- 00067, slip op. at 16–17 (PTAB Apr. 28, 2014) (Paper 60). We further note that the ’749 patent’s Specification provides that “[a]s defined for purposes of the present invention, unitary construction is intended to express a configuration wherein portions of a textile element are not joined together by seams or other connections, as depicted with textile element 40 in FIG. 8.” Ex. 1001, 6:42–46 (emphasis added); see IPR2013-00067, Ex. 1002, 6:41–46 (identical disclosure). The ’011 patent and the ’749 patent share the same Specification (apart from their claims), neither party contested our construction of this term in the appeal of our decision in the inter partes review of the claims of the ’011 patent, and Patent Owner does not contest Petitioner’s proposed construction of this term in this proceeding. Therefore, in view of the express definition of the phrase “unitary construction” in the Specification of the ’749 patent, we adopt Petitioner’s proposed construction as the broadest reasonable interpretation for this term. See Tr. 20:5–13, 37:11–17.” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for petitioner
“2. “wide-tube circular knitting machine” (Claims 9 and 19) We determine that the broadest reasonable interpretation of the term “wide-tube circular knitting machine” is “a circular knitting machine forming body garment sized, tubular textile structures, including those having a diameter that ranges from 10 inches to 20 inches.” See Inst. Dec. 9–11. Neither party contests this construction. See Tr. 20:5–13, 37:11–17.” slip op. at 13
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“8 Patent Owner contends that Reed is not analogous art. PO Resp. 34–36. In particular, Patent Owner contends that Reed is not from the same field of endeavor as the challenged claims and that Reed’s teachings are not reasonably pertinent to the particular problem with which the recited methods are involved. Id. at 34–35. Because Reed is directed to the manufacture of all types of garments, including footwear (Reply 12–13; see Ex. 1006, 1:33–44), and Reed is related directly to preparation of garments layouts from a knitted textile structure (Reply 14–15; see Ex. 1006, 2:29– 35), we are persuaded that Reed is analogous art to the challenged claims.” slip op. at 18
Patent outcomesUS 8,266,749 not shown unpatentableClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,266,749 - Corelogic, Inc. v. Boundary Solutions, Inc.No claims unpatentablePTAB · May 19, 2016 · IPR2015-00219 · APJ Lynne E Pettigrew · IPR · Final written decision
Claims 12–15 and 17–21 were not shown unpatentable because Oosterom did not disclose searching the database using a jurisdictional identifier.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for patent owner
“In the Institution Decision, we construed “jurisdictional identifier” to mean “a number or other name, code, or description that identifies a jurisdiction.” Dec. 6. We based our construction on the only appearance of “jurisdictional identifier” in the written description of the ’352 patent, which states: FIG. 3 illustrates a USA County Boundary Map (USACM). This is a public domain boundary file of each and every of the 3140 counties within the United States. Each of these polygons is geocoded with its county name and FIPS number, a numerical jurisdictional identifier, as illustrated in the figure. Ex. 1001, 8:48–53 (emphasis added).3 BSI does not challenge our construction of “jurisdictional identifier” in its Patent Owner Response, see PO Resp. 6, nor does CoreLogic challenge the construction in its Reply, see Reply 10. For this Final Written Decision, after considering the complete record, we maintain our construction of “jurisdictional identifier” as “a number or other name, code, or description that identifies a jurisdiction.”” slip op. at 5
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Having reviewed the arguments and evidence, we are not persuaded CoreLogic has demonstrated that Oosterom discloses searching the parcel map database “using a jurisdictional identifier” as recited in claim 12. Among the attributes in Oosterom’s parcel and boundary tables identified by CoreLogic in its analysis, only the municipality codes (i.e., “municip” in the parcel table and “L_municip” and “R_municip” in the boundary table) qualify as “jurisdictional identifiers.” See Ex. 1010, 513–14 (Tables 1, 2). The “object_id” of an object, e.g., a parcel or a boundary, is a nationwide unique identifier, but there is no indication in Oosterom that the object_id of a parcel or boundary identifies a jurisdiction. See id. at 512; see also id. at 513–14 (showing object_id attribute in parcel and boundary tables). As for the “ogroup” attribute in the parcel and boundary tables, Oosterom states only that it “indicates to which group the record belongs.” Id. at 519. Nothing in Oosterom describes the ogroup as identifying a jurisdiction. Although the municipality code attributes in the parcel and boundary tables identify jurisdiction, CoreLogic does not cite any portion of Oosterom that illustrates the use of municipality codes in searching the database for selected parcels as required by claim 12. See Pet. 45. Dr. Goodchild opines that the “municipality code . . . would allow us to search [the] parcel table by that jurisdiction and to identify all the parcels in that jurisdiction.” Ex. 2010, 19:22–24. He further testifies that in his analysis, he “was concerned with the specific kind of query identified in the claim, which is much narrower than Oosterom’s discussion [and] much more specific than the broad range of queries discussed by Oosterom.” Id. at 21:14–25. Ultimately, he states that the “question [he] analyzed is whether [Oosterom’s] database is capable of supporting the type of query identified in the claim.” Id. at 22:14–16 (emphasis added). Dr. Goodchild’s testimony that municipality codes could be used in searching Oosterom’s database, however, is insufficient to establish for anticipation purposes that Oosterom discloses the step of searching a multi-jurisdictional digital parcel map database for a selected parcel boundary polygon “using a jurisdictional identifier.”” slip op. at 10
- ExcludeOther
“C. CoreLogic’s Motion to Exclude Evidence CoreLogic moves to exclude the redirect testimony of BSI’s expert, Mr. William Huxhold, on the ground that it was provided in response to leading questions. Mot. Excl. 1 (citing Ex. 1034, 150:6–153:8). The redirect testimony relates to a portion of Mr. Huxhold’s cross-examination testimony. Id. at 1–2 (citing Ex. 1034, 72:5–22). Because we do not rely on Mr. Huxhold’s testimony, CoreLogic’s motion is dismissed as moot.” slip op. at 12
Patent outcomesUS 8,065,352 not shown unpatentableClaim construction§ 102 anticipationPatents in suitUS 8,065,352 - Smart Modular Technologies Inc. v. Netlist, Inc.No claims unpatentablePTAB · Mar 9, 2016 · IPR2014-01372 · APJ Linda M Gaudette · IPR · Final written decision
The Board held claims 1–4, 14–20, 27, and 29 not unpatentable because Averbuj did not disclose a control module configured to generate the claimed address signals.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Based on a comparison of Dr. Bagherzadeh’s and Dr. Sechen’s declarations (Exs. 1009, 2019), we find Dr. Bagherzadeh has a broader range of educational and work experience, and, therefore, accord greater weight to his opinion as to the level of ordinary skill in the art. Dr. Bagherzadeh’s opinion is consistent with our finding as to the level of ordinary skill in the art in our Final Written Decision in IPR-970. We, therefore, adopt our finding in IPR-970 as to the level of ordinary skill in the art: [A] person of ordinary skill in the art at the time of the ’434 patent would have a Bachelor’s degree in electrical engineering, computer engineering, or in a related field and at least one year of work experience relating to memory systems, and would be familiar with the design of memory devices, memory modules, and BIST. IPR-970 FWD, 10–11 (noting that our finding was “based on our review of the ’434 patent and the types of problems and solutions described in the ’434 patent and cited prior art”).” slip op. at 10
- Expert testimonyPetitioner expert discountedDecided for patent owner
“We are not persuaded by Dr. Bagherzadeh’s testimony because it is devoid of specific facts and analysis as to what led him to conclude that a person of ordinary skill in the art would interpret the claim term “generate” in the manner Petitioner proposes. See id. Dr. Bagherzadeh does not explain how the IEEE definition supports an interpretation of generate as “cause or initiate transmission,” terms that do not appear in the IEEE definition. See id. Nor does Dr. Bagherzadeh identify other extrinsic evidence which he believes to be consistent with an interpretation of “generate” as meaning “cause or initiate transmission.” See id. Likewise, Dr. Bagherzadeh has not explained why he believes the ’434 patent “describe[s] generating as initiating or transmitting” (Ex. 1009 ¶ 28), as these terms do not appear in the cited portions of the ’434 patent. See Ex. 1008, 6:3–5, 10:67–11:2, 6:14–17. Accordingly, Dr. Bagherzadeh’s testimony does not persuade us to accept Petitioner’s interpretation of “generate” as meaning “cause.”” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“supports a finding that a customary meaning of “generate” to one of ordinary skill in the art is “cause.”1 We, therefore, determine the broadest reasonable 1 Petitioner relies on Webster’s II, for a definition of “cause.” See Reply 4, 6–8 (citing Ex. 1032, 3). Having determined the broadest reasonable interpretation of “generate” does not encompass “cause,” we do not find this evidence relevant to our claim construction analysis. construction of “generate” is “produce” for the reasons stated above and in our Final Written Decision in IPR-970. We adopt and incorporate by reference our analysis and construction of the term “generate” in our Final Written Decision in IPR-970 (IPR-970 FWD, 24–33).” slip op. at 16
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Moreover, the evidence in this proceeding fails to support a finding that Averbuj’s BIST controller 4 is configured to generate address signals for testing the memory devices in the manner claimed. In Averbuj, the algorithms (i.e., CMD_DATA containing OP CODE such as SET ADDRESS (see Ex. 1011, 4:4–12, 5:19–21, Table 1)) communicated to sequencers 8 are either received by user interface 22 via external input (id. at 5:41–43) or generated by another component (i.e., a component that is not part of BIST controller 4 circuitry) and stored in algorithm memory 20 (see Ex. 2012, 30:23–24, 41:1–4, 54:21–22, 55:6–25, 55:20–56:9 (wherein Dr. Bagherzadeh testifies that OP CODE residing in the algorithm memory of BIST controller 4 are generated by hand or by a tool, e.g., a compiler, and that “99 percent of the designs or chips do not have a compiler on-board”)). Multiplexer 24 selects one of the algorithms (i.e., CMD_DATA) and BIST controller 4 provides to sequencers 8 the same CMD_DATA (e.g., address signals) without transformation or modification. See Ex. 1011, 4:4–12, 5:16–21; Ex. 2012, 54:8–13 (“Averbuj Figure 2, without consideration of any other disclosure in Averbuj, illustrates that a multiplexer selects an input from the algorithm memory and the output [] reflect[s] what’s in the input, based on the selection.”). Based on our interpretation of the terms “configured to” and “generate,” as discussed above, the claim recitation “a control module configured to generate address . . . signals for testing the memory devices” (claims 1, 20, and 29) does not read on Averbuj’s BIST controller 4, because the SET ADDRESS signal output by BIST controller 4 is produced by a component external to BIST controller 4, and merely selected by multiplexer 24 and provided to sequencers 8 without transformation or modification by BIST controller 4. In sum, after considering the parties’ arguments and evidence, we determine Petitioner has not shown, by a preponderance of the evidence, that Averbuj discloses “a control module configured to generate address . . . signals for testing the memory devices” as recited in independent claims 1, 20, and 29. Petitioner does not correct this deficiency in its challenges as to dependent claims 2–4, 14–19, and 27. See Pet. 32–39; 35 U.S.C. § 112, ¶ 4 (“A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.”). Because Petitioner has not identified in Averbuj a teaching of each and every limitation recited in claims 1–4, 14–20, 27, and 29, Petitioner has not met its burden to show these claims are unpatentable under 35 U.S.C. § 102(b) as anticipated by Averbuj.” slip op. at 30
Patent outcomesUS 8,001,434 not shown unpatentableClaim construction§ 102 anticipationPatents in suitUS 8,001,434 - EMC Corporation v. Acqis LLCNo claims unpatentablePTAB · Mar 8, 2016 · IPR2014-01462 · APJ Robert J Weinschenk · IPR · Final written decision
Claims 54 and 56–61 were not shown unpatentable because the evidence did not establish that the cited references rendered the claimed PCI transaction communication obvious.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“construction in the Decision on Institution. The evidence indicates that the term “Peripheral Component Interconnect (PCI) bus transaction” refers to a particular industry standard, not just any communication with an interconnected peripheral component. Industry literature and dictionaries use the proper noun “Peripheral Component Interconnect” and the abbreviation “PCI” to refer to a particular industry specification for a local bus. See, e.g., Ex. 2001, 1; Ex. 2002, 6–7; Ex. 2003, 7–8. The challenged claims recite “Peripheral Component Interconnect” as a proper noun and abbreviate it as “PCI,” indicating that the challenged claims use those terms consistent with the understood industry meaning. Ex. 1001, col. 43, ll. 48–49, col. 44, l. 6; see Azure Networks, LLC v. CSR PLC, 771 F.3d 1336, 1348 (Fed. Cir. 2014). The written description similarly uses the abbreviation “PCI” to refer to a particular industry standard, and uses the common noun “peripheral bus” to refer to a generic peripheral bus. Compare Ex. 1001, col. 5, ll. 31–33 (“The present invention . . . interface[s] two PCI or PCI-like buses”), with id. at col. 10, ll. 53–55 (“Additionally, the peripheral controller is coupled to a clock control logic, a configuration signal, and a peripheral bus.”) (emphasis added).” slip op. at 6
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“obvious over Horst and LVDS Owner’s Manual; claims 56 and 59 would have been obvious over Horst, LVDS Owner’s Manual, and Pocrass; and claim 58 would have been obvious over Horst, LVDS Owner’s Manual, and Deters. Pet. 58–59. A claim is unpatentable as obvious under 35 U.S.C. § 103(a) if the differences between the claimed subject matter and the prior art are such that the subject matter as a whole would have been obvious at the time the invention was made to a person having ordinary skill in the art to which the subject matter pertains. KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 406 (2007). The question of obviousness is resolved on the basis of underlying factual determinations, including: (1) the scope and content of the prior art; (2) any differences between the claimed subject matter and the prior art; (3) the level of ordinary skill in the art; and (4) any objective indicia of non-obviousness. Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966). We have considered the parties’ arguments and supporting evidence, and we determine that Petitioner has not shown by a preponderance of the evidence that claims 54 and 56–61 would have been obvious over the cited references.” slip op. at 7
- ExcludeMotion to exclude, deniedMixed
“Owner argues that paragraphs 10–24 and 31–37 of Exhibit 1031 should be excluded as irrelevant and prejudicial because Petitioner relies on those paragraphs to support improper arguments in the Reply. PO Mot. 8. Petitioner argues in the Reply that the TNet transaction in Horst includes PCI address bits, and that claim 54 only requires communicating two bits of a PCI bus transaction. PO Mot. 1. Patent Owner contends that both arguments exceed the scope of a proper reply, as set forth in 37 C.F.R. § 42.23(b), and that the portions of Exhibit 1031 that Petitioner relies upon to support those arguments should be excluded as irrelevant and prejudicial. PO Mot. 2–4, 6, 7. Patent Owner’s argument is not persuasive. Patent Owner argues in the Response that the TNet transaction in Horst does not include PCI address bits. PO Resp. 27–29. As such, Petitioner’s argument in the Reply that the TNet transaction includes PCI address bits is responsive to an argument raised in the Response. See 37 C.F.R. § 42.23(b) (generally permitting a reply to respond to arguments raised in a response). Patent Owner also argues in the Response that claim 54 requires communicating a 32-bit PCI address. PO Resp. 8–11. As such, Petitioner’s argument in the Reply that claim 54 only requires communicating two bits of a PCI bus transaction is responsive to an argument raised in the Response. Because we are not persuaded that the identified arguments in the Reply are improper, the premise of Patent Owner’s Motion to Exclude Exhibit 1031 fails. Therefore, Patent Owner’s Motion to Exclude paragraphs 10–24 and 31–37 of Exhibit 1031 is denied.” slip op. at 16
Patent outcomesUS 8,041,873 not shown unpatentableClaim construction§ 103 obviousnesscites GrahamPatents in suitUS 8,041,873 - EMC Corporation v. Acqis LLCNo claims unpatentablePTAB · Mar 8, 2016 · IPR2014-01469 · APJ Robert J Weinschenk · IPR · Final written decision
Claims 24 and 31–33 were not shown unpatentable because Petitioner failed to prove obviousness over either asserted reference combination, including failure to establish Bogaerts as prior art.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner
“Interconnect (PCI) bus transaction” to mean “a data signal communication with an interconnected peripheral component.” Pet. 13. Patent Owner agrees with the construction in the Decision on Institution that the claim term “Peripheral Component Interconnect (PCI) bus transaction” means “Peripheral Component Interconnect (PCI) industry standard bus transaction.” PO Resp. 21–22. We see no reason now to deviate from the construction in the Decision on Institution. The evidence indicates that the term “Peripheral Component Interconnect (PCI) bus transaction” refers to a particular industry standard, not just any communication with an interconnected peripheral component. Industry literature and dictionaries use the proper noun “Peripheral Component Interconnect” and the abbreviation “PCI” to refer to a particular industry specification for a local bus. See, e.g., Ex. 2001, 1; Ex. 2002, 6–7; Ex. 2003, 7–8. The challenged claims recite “Peripheral Component Interconnect” as a proper noun and abbreviate it as “PCI,” indicating that the challenged claims use those terms consistent with the understood industry meaning. Ex. 1001, col. 27, ll. 24–25, col. 28, ll. 35–36; see Azure Networks, LLC v. CSR PLC, 771 F.3d 1336, 1348 (Fed. Cir. 2014). The written description similarly uses the abbreviation “PCI” to refer to a particular industry standard, and uses the common noun “peripheral bus” to refer to a generic peripheral bus. Compare Ex. 1001, col. 19, ll. 31–33 (“the present invention may interface two PCI or PCI-like buses”), with id. at col. 7, ll. 4–6 (“Additionally, the host controller is coupled to a clock control logic, a configuration signal, and a peripheral bus.”) (emphasis added). Petitioner and Petitioner’s declarant, Mr. Bruce Young, acknowledge that the term “Peripheral Component Interconnect (PCI)” refers to an industry standard. Ex. 1003 ¶ 58; Ex. 2006, 1, 3; Ex. 2031, 16:8–12. The evidence Petitioner identifies in support of its proposed construction is the claim construction order issued in ACQIS LLC v. Appro International, Inc., No. 6:09-cv-00148 (E.D. Tex. Feb. 3, 2011). Pet. 12–13 (citing Ex. 1013). In that case, though, the parties did not appear to dispute that the term “Peripheral Component Interconnect (PCI)” refers to an industry standard. See Ex. 1013, 7 (“The parties’ primary dispute is whether the term is limited to the conventional, parallel PCI Local Bus, and, therefore excludes PCI Express bus architecture and bus transaction protocol.”). Moreover, the district court subsequently reconsidered its construction and clarified that the term “PCI bus transaction” refers to a PCI industry standard bus transaction. Ex. 1030, 8–10. Therefore, we construe the claim term “Peripheral Component Interconnect (PCI) bus transaction” to mean “Peripheral Component Interconnect (PCI) industry standard bus transaction,” and we construe the claim term “PCI bus transaction” to mean “PCI industry standard bus transaction.”” slip op. at 6
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“Horst outputs address and data bits of a PCI bus transaction in serial form over the TNet links. Pet. 31–34. Petitioner’s argument is not persuasive. The TNet processor interface in Horst translates a CPU transaction into a TNet transaction. Ex. 1009, 5 (“The interface to the destination CPU or I/O device provides mapping and validation hardware translating this virtual TNet address to the appropriate physical memory address.”), Figs. 5, 7; Ex. 2021 ¶ 94 (“The TNet Processor Interface generates TNet transactions from CPU front-side bus transactions.”). The TNet processor interface then encodes the TNet transaction using an 8B/9B encoder so that it can be output over the 9-bit serial TNet links. Ex. 1003 ¶¶ 48, 146; Ex. 1009, 3, Figs. 3, 4 (showing “8B/9B encoder”), Table 1; Ex. 2021 ¶ 105. Petitioner does not identify persuasive evidence indicating that either the CPU transaction or the TNet transaction is a PCI industry standard bus transaction. Pet. 31–34 (citing Ex. 1009, 3–8, Figs. 2, 3, 5, 7–9, Table 1; Ex. 1003 ¶¶ 159[24C(i)], 159[24C(iv)], 159[24C(v)], 159[31B(i)], 159[31B(iii)]); Ex. 2021 ¶ 129. Thus, the evidence identified in the Petition does not indicate that the information output by the TNet processor interface over the TNet links includes address and data bits of a PCI industry standard bus transaction in serial form. Petitioner points out that, after a TNet transaction is communicated over the TNet links, a TNet bus interface in the console may use information in the TNet transaction to create a PCI industry standard bus transaction if a particular I/O device is connected to a PCI bus. Pet. 31–32 (citing Ex. 1009, 7, Fig. 8). But claims 24 and 31 require more than just communicating information over serial channels that subsequently might be used in the console to create a PCI industry standard bus transaction. Claims 24 and 31, when read in light of the specification, require that the information actually communicated over the serial channels includes address and data bits of a PCI industry standard bus transaction in serial form. Ex. 1001, col. 20, ll. 60–65, col. 21, ll. 15–21, col. 27, ll. 34–38, col. 28, ll. 34–39; Ex. 2022, 15:12–16:2, 22:11–16. As discussed above, the evidence identified in the Petition does not indicate that the information output by the TNet processor interface over the TNet links includes address and data bits of a PCI industry standard bus transaction in serial form.” slip op. at 11
- Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication not establishedDecided for patent owner
“The evidence identified by Patent Owner indicates that the date “2 October 1996” on Bogaerts is when it was submitted to the CERN/LHCC committee. Ex. 2021 ¶¶ 170, 171, 173; Ex. 2026, 12. Although it is possible that Bogaerts was available in the CERN Library at or around the same time, Petitioner has not shown that by a preponderance of the evidence. For example, Petitioner does not cite persuasive evidence indicating that the “Submitted by 2 Oct 1996” entry in the CERN Document Server record means that Bogaerts was available in the CERN Library on that date. Tr. 23:1–12, 25:5–25; Pet. Reply 21–25. In addition, Petitioner acknowledges that the CERN Document Server record itself was not created until December 18, 2014. Tr. 25:5–25; Ex. 2011, 439. Therefore, Petitioner has not shown sufficiently that Bogaerts is a prior art printed publication based on its availability in the CERN Library.” slip op. at 17
- ExcludeMotion to exclude, deniedDenied
“should be excluded for lack of authentication under Fed. R. Evid. 901. PO Mot. 2–6. Federal Rule of Evidence 901 requires that the proponent produce evidence sufficient to support a finding that an item is what the proponent claims it is. Here, Patent Owner does not dispute that Exhibit 1011 is what Petitioner claims it is, namely a reference entitled “RD24 Status Report: Application of the Scalable Coherent Interface to Data Acquisition at LHC.” Id. What Patent Owner disputes is whether Petitioner has shown by a preponderance of the evidence that Bogaerts is prior art with respect to the ’814 patent. Id. Patent Owner attempts to characterize this dispute as a question of authentication, arguing that Petitioner has not produced “evidence that [Exhibit 1011] is a true and correct copy of a publication that was publicly available as of the date asserted by Petitioner.” Id. at 3. But this is a question of sufficiency of proof, not admissibility. Therefore, Patent Owner’s Motion to Exclude Exhibit 1011 is denied.” slip op. at 20
Patent outcomesUS RE42,814 not shown unpatentableClaim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
Holdings, summaries, rulings, issues, outcomes, winners and claim constructions shown for a decision were generated by a large language model reading the opinion. They are a guide to the decision, not the decision. Confirm every one against the court's own text before relying on it. Outcomes read from the patent owner’s side. Party names are extracted from the decision and are missing on about 900 short Director denials and scans, which carry the trial number instead.