- Corelogic, Inc. v. Boundary Solutions, Inc.Institution deniedPTAB · May 24, 2016 · CBM2016-00016 · APJ Peter P Chen · CBM · Institution
The Board denied institution for claims 1–19 because the petition did not establish that the ’957 patent qualifies as a covered business method patent.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“method patent,” as defined by the AIA. CoreLogic bears the burden of persuasion that the ’957 patent is a covered business method patent. See 37 C.F.R. § 42.304(a). For the reasons discussed below, we determine CoreLogic has made an insufficient showing that the ’957 patent is a “covered business method patent.” The AIA defines “covered business method patent” as “a patent that claims a method or corresponding apparatus for performing data processing or other operations used in the practice, administration, or management of a financial product or service, except that the term does not include patents for technological inventions.” AIA § 18(d)(1); see also 37 C.F.R. § 42.301(a). The legislative history of the AIA “explains that the definition of covered business method patent was drafted to encompass patents ‘claiming activities that are financial in nature, incidental to a financial activity or complementary to a financial activity.’” Transitional Program for Covered Business Method Patents—Definitions of Covered Business Method Patent and Technological Invention; Final Rule, 77 Fed. Reg. 48,374, 48,735 (Aug. 14, 2012) (“CBM Final Rules”) (quoting 157 Cong. Rec. S5432 (daily ed. Sept. 8, 2011)); see also Blue Calypso, LLC v. Groupon, Inc., 815 F.3d 1331, 1338 (Fed. Cir. 2016). To determine whether a patent is eligible for a covered business method patent review, the focus is on the claims. AIA § 18(d)(1) (“a patent that claims . . .” (emphasis added)); 37 C.F.R. § 42.301(a) (same); CBM Final Rules, 77 Fed. Reg. at 48,736 (comment 4) (“[T]he definition set forth in § 42.301(a) . . . is based on what the patent claims.”). A patent need have only one claim directed to a covered business method to be eligible for review. CBM Final Rules, 77 Fed. Reg. at 48,736 (comment 8) (“A patent having one or more claims directed to a covered business method is a covered business method patent for purposes of the review, even if the patent includes additional claims.”).” slip op. at 5
- Adverse judgmentAdverse judgmentOther
“patent because “[a]t least claim 1 of the ’957 patent claims data processing or other operations that are financial in nature or, at a minimum, incidental or complementary to a financial activity.” Pet. 7. CoreLogic also relies on dependent claims 13 and 16–18, and argues that those claims “explicitly limit the claims to financial applications.” Id. at 9; see also id. at 11 (alleging that claims 16–18 cover “subject matter incidental or complementary to a financial activity”). As noted above, however, BSI disclaimed claims 13 and 16–18 at the same time it filed its Preliminary Response. See Ex. 2003. “A statutory disclaimer under 35 U.S.C. § 253 has the effect of canceling the claims from the patent and the patent is viewed as though the disclaimed claims had never existed in the patent.” Guinn v. Kopf, 96 F.3d 1419, 1422 (Fed. Cir. 1996). We agree with other panels that have considered this issue under similar facts and concluded that the disclaimed claims should not be consulted when determining whether the patent is a covered business method patent under AIA §18(d)(1).1 We are mindful that other Board decisions have evaluated compliance with CBM standing requirements at the time of filing, but those cases are distinguishable2 and not binding here. Any suggestion in those cases that a decision on institution should address the disclaimed claims because they existed at the time the petition was filed is inconsistent with Federal Circuit precedent instructing us to treat the claims as if they never existed, and our Rules forbidding institution “based on disclaimed claims.” Guinn, 96 F.3d at 1422; 37 CFR § 42.207(e) (“No post-grant review will be instituted based on disclaimed claims.”); see also Google Inc. v. SimpleAir, Inc., CBM2015- 00019, slip op. at 5–6 (PTAB Aug. 19, 2015) (Paper 15) (Order Denying Request for Rehearing) (rejecting petitioner’s argument that disclaimed claim should be considered because it existed at the time the petition was 1 See, e.g., AT&T Mobility LLC v. Intellectual Ventures II LLC, CBM2015- 00185, slip op. at 9–10 (PTAB May 4, 2016) (Paper 10); Great West Casualty Co. v. Intellectual Ventures II LLC, CBM2015-00171, slip op. at 7–9 (PTAB Feb. 9, 2016) (Paper 10); Google Inc. v. SimpleAir, Inc., CBM2015-00019, slip op. at 14–15 (PTAB May 19, 2014) (Paper 11). 2 In Travelers Lloyds of Texas Ins. Co. v. Integrated Claims Sys., LLC, CBM2014-00187, slip op. at 7, 8 n.1 (PTAB Mar. 30, 2016) (Paper 31), the Patent Owner attempted to cancel a claim after institution, not disclaim a claim prior to institution. In J.P. Morgan Chase & Co. v. Intellectual Ventures II LLC, CBM2014-00157, slip op. at 9 (PTAB Jan. 12, 2016) (Paper 40), the Patent Owner’s disclaimer occurred after institution, not prior to institution. filed). We therefore do not consider disclaimed claims 13 and 16–18 in our analysis.” slip op. at 6
- BurdenDecided for patent owner
“We agree with BSI. CoreLogic does not explain adequately how any of the claims of the ’957 patent recite a method or apparatus “for performing data processing or other operations used in the practice, administration, or management of a financial product or service.” AIA § 18(d)(1); see also 37 C.F.R. § 42.301(a). CoreLogic focuses on claim 1, but fails to identify any limitation in claim 1 or any other claim that relates to a financial activity in any way. Claim 1 claims a “method for retrieving geographic parcel boundary polygon maps and associated parcel attribute data,” which has applicability to retrieving and displaying map data, not financial products and services. CoreLogic suggests that the “transmitting” step of claim 1 “can be used” by various entities in a business context, but does not argue, let alone establish, that the claim terms on their face are financial in nature. See Pet. 1. CoreLogic asserts that the Specification of the ’957 patent describes several methods of generating revenue using the claimed methods, and that numerous businesses may pay for access to map data generated using the claimed method. Pet. 10–16. CoreLogic’s reliance on these portions of the Specification is unavailing. First, CoreLogic fails to address how these disclosures relate directly to, or meaningfully informs our analysis of, the language of the claims. For example, CoreLogic does not direct us to any claims or claim limitations that require users to pay for access to the map database or use of the claimed methods. Second, CoreLogic fails to address portions of the Specification that indicate the claimed invention can be used “for free,” i.e., without any generation of revenue or financial aspect at all. See Ex. 1001, 2:58 (“These end users may access for free . . . .”), 14:11–15 (“Another public-private alliance option is to offer the free use of the NPDP server to such data sponsors in addition to or in lieu of their revenue share.”), 14:41–45 (“[C]ommodity service subscriber end users (customers) can have access to the NPDP at no charge.”), 16:8–12 (“It is also contemplated that other independent public and private data sponsors could be provided with links as part of the NPDP display which end users could access on a free or fee basis.”). Given that the Specification contemplates use of the claimed inventions for free, it is not apparent that the “purpose of the claimed method is to provide data in exchange for money,” as CoreLogic suggests. Pet. 10. At most, CoreLogic has established that the claimed methods could be used to generate revenue in a number of ways, even though the language of the claims does not require any exchange of money or other financially related step. Under these circumstances, we conclude that the “financial prong” has not been met. Numerous Board decisions have taken a similar approach in situations where the Specification refers to potential financial applications for the claimed inventions but the claim language does not expressly indicate a financial context.3 In Qualtrics, LLC v. OpinionLab,” slip op. at 10
NonePatents in suitUS 7,092,957 - Arista Networks, Inc. v. Cisco Systems, Inc.Rehearing deniedPTAB · Feb 29, 2016 · IPR2015-00973 · APJ Bryan F Moore · IPR · Rehearing
The Board denied rehearing and again denied institution on all challenged claims because the petition did not show a reasonable likelihood that Hendel disclosed the claimed access result.
RulingsRehearing decision- RehearingRehearing, deniedDenied
“the Board reviews the decision for an abuse of discretion. 37 C.F.R. § 42.71(c). An abuse of discretion may arise if a decision is based on an erroneous interpretation of law, if a factual finding is not supported by substantial evidence, or if an unreasonable judgment is made in weighing relevant factors. Star Fruits S.N.C. v. U.S., 393 F.3d 1277, 1281 (Fed. Cir. 2005); Arnold P’ship v. Dudas, 362 F.3d 1338, 1340 (Fed. Cir. 2004); In re Gartside, 203 F.3d 1305, 1315–16 (Fed. Cir. 2000). The party requesting rehearing has the burden of showing that the decision should be modified, and “[t]he request must specifically identify all matters the party believes the Board misapprehended or overlooked.” 37 C.F.R. § 42.71(d).” slip op. at 2
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“being forwarded (restriction) or that an output port is selected and altered. Rather, these citations generally state that priority can be given to certain packets and quality of service can be applied to layer 2 routing. Thus, we are not persuaded that Petitioner’s citation to quality of service in general discloses “generating an access result in response to said at least one selected match.”” slip op. at 7
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“rehearing, we determine that the phrase “modifications on the intended destination address to which a packet is to be transmitted” introduces uncertainly into the construction.4 The construction in the Decision appears to conflate the “destination” of a packet with the output interface to which a packet is directed. The Specification does not describe, however, modifying the “destination” of the packet; the only “modification” on how the packet is routed specifically described in the Specification is when “the access control element 120 . . . [alters] the output interface, which was selected by the routing element 110, to another selected output interface.” Ex. 1001, 6:13– 4 Petitioner does not seek rehearing of the claim construction (Reh’g Req. 4, n. 1) but our analysis requires that we revisit the claim construction determination from the Decision. 16; Reh’g Req. 4–5. Thus, we modify our construction of “access control” to mean only restrictions on the transmission of a packet or alteration of a selected output interface for the packet.” slip op. at 4
- Expert testimonyPetitioner expert discountedDecided for patent owner
“Additionally, Petitioner cites to its Declarant Dr. Chao. Reh’g Req. 6 (citing Ex. 1003 ¶ 31). Petitioner’s Declarant states without citation that “a switch may modify the forwarding decision to account for network policies such as quality of service determinations. That is, a packet may be destined for a certain MAC address and port on the switch, but the switch may determine that the packet can be transmitted more reliably through another port, and so it will change the destination port for that packet.” Ex. 1003 ¶ 31. Petitioner’s Declarant’s testimony is conclusory and unsupported by evidence, and, therefore, we give that testimony no weight.” slip op. at 7
Claim constructionPatents in suitUS 6,377,577 - Arista Networks, Inc. v. Cisco Systems, Inc.Institution deniedPTAB · Oct 19, 2015 · IPR2015-00976 · APJ Bryan F Moore · IPR · Institution
The Board denied institution on all challenged claims because the patent did not disclose sufficient structure for certain means-plus-function limitations and Hendel did not show claim 63’s required access-control matching.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“Petitioner has not shown that Hendel’s filtering decision is determined based on “matching one or more characteristics of said packet with one or more access control specifiers.” Petitioner simply states that the packet is “filtered.” Petitioner’s Declarant relies on the following text from Hendel: “In a preferred embodiment, the merge logic 66 directs the input port 50i to take one of the following actions on a packet: filter the packet; forward the packet at layer 2; forward the packet at layer 2; forward the packet as a layer 3 flow; process the packet as a layer 3 route; and forward the packet as multicast router.”) Ex. 1003 ¶ 132 (citing Ex. 1007, 13:4–8.) This citation does not specify, however, that a characteristic of the packet was matched to anything in order to make the filtering decision, only that the decision was the result of “merge logic.” Petitioner’s Declarant also relies on the following text from Hendel: “After the forwarding logic 52 has determined what to do with the packet, it passes that information to the input port 50i. If the input port 50i does not filter the packet, then it [takes actions to forward the packet].” Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25.) However, this statement does not even say that forwarding logic tells input port 50i to filter the packet, and certainly does not explain how forwarding logic 52 would make a filtering decision. Finally, Petitioner’s declarant relies on Hendel’s discussion of sending the packet to a firewall for further processing if no match occurs (Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25)), but the claim does not recite what happens if there is not a match. The specification confirms that a successful match is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by “determining all of the successful matches”). Neither Petitioner, nor Petitioner’s Declarant, has tied the matching in Hendel to a decision whether or not to forward a packet. For the reasons stated above, we determine Petitioner has not shown sufficiently that Hendel discloses all of the limitations of independent claim 63. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that claim 63 is anticipated by Hendel.” slip op. at 14
- Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Other
“The corresponding structure need not be explicitly identified but must disclose to a person of ordinary skill in the art what structure is identified in the specification. See Atmel Corp. v. Info. Storage Devices, Inc., 198 F.3d 1374, 1380 (Fed. Cir. 1999). It is unclear from the Specification whether the CPU, shown in Figure 2 as part of access control element 120, is the “higher-level processor” which is described at Ex. 1001, 5:21–25, or some other processor running IOS described at Ex. 1001, 1:33–37. It is also unclear which part of the access control element 120 is composed of “circuits adapted to particular process steps and data structures” as described at 3:36–39. Here, the patent is at best unclear whether the claimed function is implemented in software executed on a general purpose CPU or in hardware as a collection of circuits. See Blackboard, Inc. v. Desire2Learn Inc., 574 F.3d 1371, 1385 (Fed. Cir. 2009) (“That ordinarily skilled artisans could carry out the recited function in a variety of ways is precisely why claims written in ‘means-plus-function’ form must disclose the particular structure that is used to perform the recited function.”). We also find that it is equally unclear whether the following means- plus-function limitations in claim 46, which appear to involve access control element 120, are implemented in hardware or in software structure (or some combination of both): means for matching matchable information, said matchable information being responsive to said packet label, with said set of access control patterns in parallel; means for making a routing decision in response to said access result; means for permitting or denying access for said packet; and means for receiving a packet label responsible to a packet, said packet label being sufficient to perform access control processing for said packet. Because the Specification of the challenged patent lacks sufficient disclosure of structure under 35 U.S.C. § 112, sixth paragraph, the scope of independent claim 46, and claims 47–52, 54, 56, and 59–62 that depend therefrom, cannot be determined without speculation and, consequently, the differences between the claimed invention and the prior art cannot be ascertained. Thus, we decline to institute an inter partes review as to any ground challenging claims 46–52, 54, 56, and 59–62.” slip op. at 11
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“Petitioner has not shown that Hendel’s filtering decision is determined based on “matching one or more characteristics of said packet with one or more access control specifiers.” Petitioner simply states that the packet is “filtered.” Petitioner’s Declarant relies on the following text from Hendel: “In a preferred embodiment, the merge logic 66 directs the input port 50i to take one of the following actions on a packet: filter the packet; forward the packet at layer 2; forward the packet at layer 2; forward the packet as a layer 3 flow; process the packet as a layer 3 route; and forward the packet as multicast router.”) Ex. 1003 ¶ 132 (citing Ex. 1007, 13:4–8.) This citation does not specify, however, that a characteristic of the packet was matched to anything in order to make the filtering decision, only that the decision was the result of “merge logic.” Petitioner’s Declarant also relies on the following text from Hendel: “After the forwarding logic 52 has determined what to do with the packet, it passes that information to the input port 50i. If the input port 50i does not filter the packet, then it [takes actions to forward the packet].” Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25.) However, this statement does not even say that forwarding logic tells input port 50i to filter the packet, and certainly does not explain how forwarding logic 52 would make a filtering decision. Finally, Petitioner’s declarant relies on Hendel’s discussion of sending the packet to a firewall for further processing if no match occurs (Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25)), but the claim does not recite what happens if there is not a match. The specification confirms that a successful match is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by “determining all of the successful matches”). Neither Petitioner, nor Petitioner’s Declarant, has tied the matching in Hendel to a decision whether or not to forward a packet. For the reasons stated above, we determine Petitioner has not shown sufficiently that Hendel discloses all of the limitations of independent claim 63. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that claim 63 is anticipated by Hendel.” slip op. at 14
Claim construction§ 102 anticipationPatents in suitUS 7,023,853 - Arista Networks, Inc. v. Cisco Systems, Inc.Institution deniedPTAB · Oct 6, 2015 · IPR2015-00974 · APJ Matthew R Clements · IPR · Institution
The Board denied institution on all challenged claims because Petitioner did not show a reasonable likelihood of proving unpatentability under the asserted anticipation and obviousness grounds.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied
“Systems, Inc. (“Patent Owner”) filed a Preliminary Response. Paper 6 (“Prelim. Resp.”). We have jurisdiction under 35 U.S.C. § 314, which provides that an inter partes review may be authorized only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a); 37 C.F.R. § 42.4(a). Upon consideration of the Petition and the Preliminary Response, we determine that the information presented by Petitioner does not establish that there is a reasonable likelihood that Petitioner would prevail in showing the unpatentability of any of the challenged claims 1–10, 12, 13, 15–28, 30, 31, 33–43, 45–49, 51–64, 66, 67, and 69–72 of the ’668 patent. Accordingly, pursuant to 35 U.S.C. § 314, we do not institute an inter partes review of claims 1–10, 12, 13, 15–28, 30, 31, 33–43, 45–49, 51–64, 66, 67, and 69–72 of the ’668 patent.” slip op. at 2
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“interpreted according to their “broadest reasonable construction in light of the specification of the patent” in which they appear. 37 C.F.R. § 42.100(b); see also In re Cuozzo Speed Techs., LLC, 793 F.3d 1268, 1278–79 (Fed. Cir. 2015). Applying that standard, we interpret the claim terms according to their ordinary and customary meaning in the context of the patent’s written description. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed. Cir. 2007). Petitioner proposes constructions for ten terms. Pet. 9–14. Patent Owner disputes some of those constructions and proposes an additional term for construction. Prelim. Resp. 9–19. For purposes of this Decision, we determine that we need not expressly construe any of the terms for which the parties have proposed constructions.” slip op. at 6
- Skill levelOther
“expressly disclose a limitation, may nevertheless anticipate if a person of ordinary skill in the art would understand the prior art to disclose the limitation and could combine the prior art description with his own knowledge to make the claimed invention. See Helifix Ltd. v. Blok-Lok, Ltd., 208 F.3d 1339, 1347 (Fed. Cir. 2000). After reviewing the arguments of the parties and the testimony of Dr. Lin, however, we are not persuaded that a person of ordinary skill in the art1 would understand the cited sentence in Amara as necessarily disclosing that the network interface ports of Amara’s internetworking device are configurable by its internal applications. Dr. Lin relies on pages 132 to 134 of Habraken, which is a textbook that describes, inter alia, configuring the interfaces of a Cisco router through a Setup dialog. While this passage describes configuring a port, it is not clear what aspect of the Cisco router is providing the Setup dialog. Nothing, for example, attributes the Setup dialog to “control plane processes” or “internal applications” or the like of the Cisco router. Even assuming that the Setup dialog is provided by an “internal application” of the Cisco router, 1 Petitioner asserts, and Patent Owner does not dispute, that a person of ordinary skill as of the critical date would have had a Master of Science Degree in an academic area emphasizing computer networking or, alternatively, a Bachelor Degree in an academic area emphasizing the design of electrical, computer, or software engineering and several years of experience in computer network engineering and the design of computer networks. Pet. 7. nothing in Habraken supports the determination that the network interface ports of all routers, such as the 3Com router described in Amara, are configurable by “internal applications” of that router. At best, Habraken establishes that a person of ordinary skill in the art at the time would have known that Cisco routers include a Setup dialog for configuring router interfaces. This is not sufficient, however, to persuade us that a person of ordinary skill in the art would have read Amara as necessarily disclosing that the network interface ports of the “device” are configurable by the internal applications.” slip op. at 11
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable
“We agree with Patent Owner that Amara’s express disclosure is not sufficient. Amara’s disclosure that internal applications control or configure the device only “typically” suggests that they do not necessarily serve that purpose and, therefore, that another component of device 100 may serve that purpose. Moreover, Amara’s disclosure that internal applications control or configure the “device” is not sufficiently specific as to whether the interface ports are an aspect of the device being controlled or configured by the internal applications. Our reviewing court has held that a prior art reference that does not expressly disclose a limitation, may nevertheless anticipate if a person of ordinary skill in the art would understand the prior art to disclose the limitation and could combine the prior art description with his own knowledge to make the claimed invention. See Helifix Ltd. v. Blok-Lok, Ltd., 208 F.3d 1339, 1347 (Fed. Cir. 2000). After reviewing the arguments of the parties and the testimony of Dr. Lin, however, we are not persuaded that a person of ordinary skill in the art1 would understand the cited sentence in Amara as necessarily disclosing that the network interface ports of Amara’s internetworking device are configurable by its internal applications. Dr. Lin relies on pages 132 to 134 of Habraken, which is a textbook that describes, inter alia, configuring the interfaces of a Cisco router through a Setup dialog. While this passage describes configuring a port, it is not clear what aspect of the Cisco router is providing the Setup dialog. Nothing, for example, attributes the Setup dialog to “control plane processes” or “internal applications” or the like of the Cisco router. Even assuming that the Setup dialog is provided by an “internal application” of the Cisco router, 1 Petitioner asserts, and Patent Owner does not dispute, that a person of ordinary skill as of the critical date would have had a Master of Science Degree in an academic area emphasizing computer networking or, alternatively, a Bachelor Degree in an academic area emphasizing the design of electrical, computer, or software engineering and several years of experience in computer network engineering and the design of computer networks. Pet. 7.” slip op. at 10
Claim construction§ 102 anticipation§ 103 obviousnessPatents in suitUS 7,224,668 - Sure-Fire Electrical Corporation v. Yongjiang Yin And Shenzhen El Lighting Co. Ltd.Rehearing grantedPTAB · Jun 1, 2015 · IPR2014-01448 · APJ Debra K Stephens · IPR · Rehearing
Rehearing was granted for claims 1 and 7 under § 103 over He and Korodi, and denied for the He and Currie ground.
RulingsRehearing decision- RehearingRehearing, grantedRehearing, deniedGranted in part
“Therefore, we conclude that we did not abuse our discretion in declining to institute an inter partes review based the combination of He and Currie. Accordingly, we do not institute an inter partes review based on this ground. III. CONCLUSION For the foregoing reasons, on rehearing, based on our review of the record before us, we determine Petitioner has demonstrated a reasonable likelihood of prevailing on its assertion that the challenged claims are unpatentable based on the combination of He and Korodi. Therefore, we modify our Decision to institute an inter partes review of claims 1 and 7 for obviousness over He and Korodi. We determine, however, that we did not abuse our discretion in declining to institute review on the asserted ground based on He and Currie, and rehearing is denied as to that ground. At this stage in the proceeding, we have not made a final determination with respect to the patentability of the challenged claims, including the claim construction.” slip op. at 12
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“a reasonable likelihood that an ordinarily skilled artisan would have been motivated to combine the teachings of He and Korodi. Specifically, we determine, based on the current record, Petitioner has articulated reasoning with a rational underpinning as to why an ordinarily skilled artisan would have been motivated to combine the teachings. “‘[T]here must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness’ . . . [H]owever, the analysis need not seek out precise teachings directed to the specific subject matter of the challenged claim, for a court can take account of the inferences and creative steps that a person of ordinary skill in the art would employ.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We credit Dr. Horenstein’s testimony that an ordinarily skilled artisan would have found it obvious simply to replace the aluminum core wire in He with a power cord as taught by Korodi. Ex. 1008 ¶¶ 99, 102. We additionally are persuaded, on the record before us, that the combination of He and Korodi unites old elements with no change in their respective functions. See KSR, 550 U.S. at 415–16. To be nonobvious, an improvement must be “more than the predictable use of prior art elements according to their established functions.” Id. at 417. Indeed, we credit Dr. Horenstein’s testimony that replacing the aluminum core wire in He for the power cord in Korodi would have been a merger of familiar elements according to their established functions, known methods, and predictable results. Ex. 1008 ¶ 103.” slip op. at 10
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundOther
“Based on the record before us, we are persuaded Petitioner has shown a reasonable likelihood that an ordinarily skilled artisan would have been motivated to combine the teachings of He and Korodi. Specifically, we determine, based on the current record, Petitioner has articulated reasoning with a rational underpinning as to why an ordinarily skilled artisan would have been motivated to combine the teachings. “‘[T]here must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness’ . . . [H]owever, the analysis need not seek out precise teachings directed to the specific subject matter of the challenged claim, for a court can take account of the inferences and creative steps that a person of ordinary skill in the art would employ.” KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We credit Dr. Horenstein’s testimony that an ordinarily skilled artisan would have found it obvious simply to replace the aluminum core wire in He with a power cord as taught by Korodi. Ex. 1008 ¶¶ 99, 102. We additionally are persuaded, on the record before us, that the combination of He and Korodi unites old elements with no change in their respective functions. See KSR, 550 U.S. at 415–16. To be nonobvious, an improvement must be “more than the predictable use of prior art elements according to their established functions.” Id. at 417. Indeed, we credit Dr. Horenstein’s testimony that replacing the aluminum core wire in He for the power cord in Korodi would have been a merger of familiar elements according to their established functions, known methods, and predictable results. Ex. 1008 ¶ 103. Accordingly, based on the record before us, we are persuaded the combination of He and Korodi is a proper combination.” slip op. at 10
- Burden
“With regard to the asserted ground of unpatentability of claims 1 and 7 for obviousness over He and Currie, Petitioner does not explain adequately the relative strengths or weaknesses of this ground and the grounds on which we have instituted. See Cisco Systems, Inc. v. Constellation Tech. LLC, Case IPR2014-01180, slip op. at 29–30 (PTAB Feb. 8, 2015) (Paper 8). The Currie reference has a filing date of September 24, 2004 and an issuance date of October 17, 2006. Thus, the Currie reference would not be prior art if Patent Owner were successful in establishing a conception date “at least as early as April 2004” and diligence from conception to reduction to practice. See Prelim. Resp. 11. Accordingly, the arguments presented in Petitioner’s Request for Rehearing do not apply to the combination of He and Currie. Therefore, we conclude that we did not abuse our discretion in declining to institute an inter partes review based the combination of He and Currie. Accordingly, we do not institute an inter partes review based on this ground.” slip op. at 11
§ 103 obviousnesscites KSRPatents in suitUS 7,671,279
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.