- Intel Corporation v. VLSI Technology LLCSome claims unpatentablePTAB · Feb 6, 2020 · IPR2018-01033 · APJ Bart A Gerstenblith · IPR · Final written decision
Claims 17 is anticipated by Bednar, and claims 1 and 17 are obvious over Bednar and Gunther; the remaining challenged claims were not shown unpatentable.
RulingsFinal written decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“requesting institution of inter partes review of claims 1, 4–6, and 17–19 of U.S. Patent No. 8,004,922 B2 (Ex. 1001, “the ’922 patent”). VLSI Technology LLC (“Patent Owner”) filed a Preliminary Response (Paper 12). Applying the standard set forth in 35 U.S.C. § 314(a), we instituted an inter partes review of all challenged claims. Paper 17 (“Inst. Dec.”).” slip op. at 2
- Skill levelSkill level board ownDecided for petitioner
“to the level of ordinary skill in the art was incorrect. Accordingly, because our preliminary finding is consistent with the level of ordinary skill in the art reflected by the prior art of record, we maintain and reaffirm that one of ordinary skill in the art at the time of the invention would have had “at least (1) an undergraduate degree in electrical engineering (or an equivalent subject), together with three years of post-graduate experience designing power management circuits; or (2) a master’s degree in electrical engineering (or equivalent subject) together with two years of post-graduate experience designing power management circuits.” Inst. Dec. 8–9; see Pet. 36 (citing Ex. 1002 ¶¶ 26–27).” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“construction of “memory device,” specifically whether it encompasses a latch. Neither party argues that “memory device” is expressly defined in the ’922 patent. Accordingly, the plain and ordinary meaning of the term controls. And, the standard under which we construe the term is the broadest reasonable construction in light of the specification.” slip op. at 45
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed
“preponderance of the evidence, that (1) claim 17 is anticipated by Bednar, and (2) claims 1 and 17 would have been obvious over the combination of Bednar and Gunther. For the reasons discussed above, Petitioner has not demonstrated, by a preponderance of the evidence, that (1) claim 1 is anticipated by Bednar or (2) claims 4–6, 18, and 19 would have been obvious over the combination of Bednar, Gunther, and Willingham. The chart below summarizes our conclusions.” slip op. at 91
Patent outcomesUS 8,004,922 mixedClaim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 8,004,922 - Old Republic General Insurance Group, Inc. / Old Republic Insurance Company et al. v. Intellectual Ventures II LLCSome claims unpatentablePTAB · Apr 12, 2017 · IPR2015-01992 · APJ Jon B Tornquist · IPR · Final written decision
Claims 1, 2, 4–12, 14–24, and 34–48 are unpatentable over the stated grounds; claims 3 and 13 were not shown unpatentable, and claims 25–33 and 49 were disclaimed.
RulingsFinal written decision- Adverse judgmentAdverse judgmentOther
“On February 8, 2017, Patent Owner informed the Board that it had “disclaimed claims 25–33 and 49” of the ’002 patent, thereby “rendering the institution of claims 25–33 and 49 in the subject inter partes review proceeding moot.” Paper 18, 1; Ex. 2005 (disclaimer of claims 25–33 and 49 pursuant to 37 C.F.R. § 1.321(a)).” slip op. at 2
- BurdenMixed
“2. Analysis To anticipate a claim a “prior art reference must disclose each and every feature of the claimed invention, either explicitly or inherently.” Eli Lilly & Co. v. Zenith Goldline Pharm., 471 F.3d 1369, 1375–76 (Fed. Cir. 2006). An inherent disclosure may be found when an asserted prior art reference “necessarily” includes the unstated limitation. Transclean Corp. v. Bridgewood Servs., Inc., 290 F.3d 1364, 1373 (Fed. Cir. 2002).” slip op. at 13
- ExcludeMotion to exclude, deniedDenied
“Upon review of Petitioner’s arguments and supporting evidence, we are persuaded that Petitioner has identified where each limitation of independent claim 1 is disclosed in Huang. Claims 11, 34, and 40 contain limitations similar to claim 1, Petitioner provides detailed arguments as to where each limitation of these claims is disclosed in Huang, and Patent Owner does not present any arguments for these claims separate from those 7 At oral argument, Patent Owner asserted that we should not consider Petitioner’s argument that the icons of Huang contain URL information because this argument was presented for the first time in Petitioner’s Reply. Tr. 32:19–35:5. Patent Owner did not file a motion to exclude this evidence, however, or request a sur-reply to address any allegedly new issues raised for the first time in Petitioner’s Reply. Id. at 34:18–23. Nor is it evident why Petitioner’s arguments are not appropriate rebuttal arguments addressing Patent Owner’s proposed construction of “pointer.” Accordingly, we decline to exclude Petitioner’s URL arguments and evidence.” slip op. at 15
- Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner
“be used in conjunction with the mobile interface agent, including “a computer, cable set top box, cellular phone, or other device.” Ex. 1001, 4:44–45. Patent Owner does not explain why the description of a “pointer” in one “context,” i.e., on a computer or PDA, represents a clear and deliberate attempt to define the term in all contexts, such that all pointers must be a “reference” to “a type of menu item” and be “accessible on a computer, PDA, or server.” See In re Paulsen, 30 F.3d at 1480 (noting that an inventor is “free to define the specific terms used to describe his or her invention,” but “this must be done with reasonable clarity, deliberateness, and precision”). The broadest definition of the term “pointer” in the ’002 patent is “a link/shortcut to an item.” Ex. 1001, 10:8–10 (“As discussed above, a pointer is a link/shortcut to an item such as . . . .”); Dec. on Inst. 10. This definition is consistent with the description of “pointers” in the ’002 patent written description and claims. Ex. 1001, 20:4–6 (“wherein the pointers provide links to access the corresponding user specific resources and information.”). Accordingly, we construe “pointer” to mean “a link or shortcut to an item.”” slip op. at 9
Patent outcomesUS 6,546,002 mixedClaim construction§ 102 anticipation§ 103 obviousnessPatents in suitUS 6,546,002 - Mexichem Amanco Holdings S.A De C.V. v. Honeywell International, Inc.Some claims unpatentablePTAB · Dec 9, 2016 · IPR2015-01309 · APJ Jon B Tornquist · IPR · Final written decision
Claims 1, 3, 5, 6, 10–13, 16, and 19 are unpatentable as obvious; claims 7–9, 14, and 15 were not shown unpatentable.
RulingsFinal written decision- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededNot reached
“Petitioner and Patent Owner propose constructions for all, or a portion of, the term “Formula I, XCF3(I), where X is a C2 unsaturated, substituted, alkyl radical.” Pet. 17–19 (proposing a construction for the term “C2 unsaturated, substituted, alkyl radical”); PO Resp. 12–15. Neither party contends, however, that express construction of this claim term, or any other term in the ’808 patent, would impact any of Petitioner’s or Patent Owner’s arguments in this proceeding. Accordingly, we determine that no claim terms require construction for purposes of this Final Written Decision. See Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999) (“[O]nly those terms need be construed that are in controversy, and only to the extent necessary to resolve the controversy.”).” slip op. at 7
- Skill levelSkill level patent owner adoptedDecided for patent owner
“art. Patent Owner, relying upon the testimony of Dr. Bivens, asserts that one of ordinary skill in the art would have had either: “(1) a bachelor of science degree in a specialty area (such as chemical engineering or chemistry) and five years of work experience in developing/testing refrigerants, blowing agents, and propellants, or (2) a Ph.D. or masters of science degree and 2-3 years of work experience.” PO Resp. 12 (citing Ex. 2034 ¶¶ 21–24). Patent Owner’s identification of a person of ordinary skill in the art is uncontroverted and is consistent with the prior art of record. Accordingly, we adopt Patent Owner’s identification for purposes of this Final Written Decision. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (noting that the prior art itself may reflect the level of ordinary skill in the art).” slip op. at 8
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundMixed
“Accordingly, we are persuaded that: (1) Petitioner has identified where every limitation of claim 1 is disclosed or suggested in the combination of Kruse, Inagaki, and Butler; (2) Petitioner has set forth reasoned explanations supported by factual underpinnings to explain why one of ordinary skill in the art, prior to the earliest filing date of the ’808 patent, would have sought to combine Kruse, Inagaki, and Butler to achieve the invention set forth in claim 1 of the ’808 patent; and (3) Petitioner has set forth reasoned arguments, supported by record evidence, to show why a person of ordinary skill in the art would have had a reasonable expectation of success in combining Kruse, Inagaki, and Butler to achieve the composition of claim 1.” slip op. at 17
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“patent met a long-felt but unresolved need or were commercially successful, we have been directed to no persuasive evidence to demonstrate these propositions. See Graham, 383 U.S. at 17–18 (noting that “long felt but unsolved needs” and commercial success may be utilized as indicia of nonobviousness). Indeed, we have been directed to no persuasive evidence that a mixture of CO2 and a fluoroalkene of claim 1 has ever been used commercially, or that such a mixture was considered by those of ordinary skill in the art to have met a long felt but previously unresolved need.9, 10 See Tr. 51:24–52:7; Pet. Reply 9 (asserting that Patent Owner “has provided no evidence, post- or pre- issuance of the ’808 patent, of the commercial advantages or uses of the claimed compositions”). With respect to Petitioner’s prior patent applications, although Patent Owner initially characterizes these applications as relating to CO2 and partially fluorinated hydrocarbons, Patent Owner later notes that these patents are directed to blends of HFO-1234yf, CO2, and R-134a. PO Resp. 44; Ex. 2024, 12 (arguing in support of patentability that “[t]he specific 9 To be relevant, Patent Owner must show that the asserted secondary considerations are attributable to “the merits of the claimed invention beyond what was readily available in the prior art.” Asyst Techs. v. Emtrak, Inc., 544 F.3d 1310, 1316 (Fed. Cir. 2008). Here, Inagaki discloses using compounds within the scope of claim 1 of the ’808 patent as refrigerants. Patent Owner presents no persuasive evidence that the addition of CO2 to the compounds of Inagaki, or the particular ranges recited in claim 1, resulted in a product that met a long felt but unresolved need or resulted in a commercially successful product beyond what was provided in Inagaki. Thus, we are also not persuaded that there is any nexus between the asserted secondary considerations and the features of claim 1 that are not disclosed in Inagaki. 10 As Patent Owner has not demonstrated any commercial use of the claim 1 compounds for any purpose, or provided evidence that those of skill in the art considered the claimed compounds to have met an unresolved need in the art, this analysis applies equally to the dependent claims of the ’808 patent, which each depend, directly or indirectly, from claim 1. combination of trans-R1234ze and R134a and CO2 simply is not suggested in Singh, let alone in the amounts defined in claim 1”). Patent Owner does not explain sufficiently why Petitioner’s arguments directed to the patentability of a blend of three compounds, utilized in specific proportions, are necessarily applicable to the combination of Kruse, Inagaki, and Butler proposed by Petitioner, or why these arguments are otherwise strong evidence of the nonobviousness of claim 1 of the ’808 patent. Based on the foregoing, and upon review of Patent Owner’s arguments as a whole, we are not persuaded that Patent Owner’s proffered objective evidence of nonobviousness is strong or tends to refute Petitioner’s arguments and evidence with respect to the obviousness of claim 1 of the ’808 patent.” slip op. at 25
Patent outcomesUS 8,623,808 mixedClaim construction§ 103 obviousnesscites KSR · GrahamPatents in suitUS 8,623,808 - Qualcomm Inc. v. Bandspeed, Inc.Some claims unpatentablePTAB · Sep 7, 2016 · IPR2015-01580 · APJ Patrick M Boucher · IPR · Final written decision
Claims 5, 6, 8, 17, 18, and 20 are unpatentable; claims 7 and 19 were not shown unpatentable because Cuffaro does not disclose a specified number of votes and the obviousness testimony was insufficient.
RulingsFinal written decision- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“After institution, Qualcomm Inc. filed substantially the same petition in IPR2015-01580 (IPR2015-01580, Paper 1), together with a Motion for Joinder of IPR2015-01580 with the instant proceeding (IPR2015-01580, Paper 2). On September 17, 2015, we granted a motion to terminate this proceeding with respect to MediaTek Inc. and MediaTek USA, Inc., but not as to Patent Owner, leaving only Patent Owner as a party to the proceeding. Paper 22. On November 16, 2015, we granted Qualcomm Inc.’s Motion for Joinder, joining Qualcomm Inc. to the instant proceeding. Paper 23. Qualcomm Inc. (“Petitioner”) is now the sole petitioner.” slip op. at 2
- Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesTerm construed petitioner constructionDecided for petitioner
“phrase “means for . . . .” Petitioner construes these terms in accordance with 35 U.S.C. § 112 ¶ 6, identifying an algorithm described in the specification corresponding to each “means” limitation. Pet. 7–9 (citing Ex. 1001, col. 8, l. 8–38, col. 8, ll. 49–col. 9, l. 16, col. 19, l. 25–col. 20, l. 67). Petitioner identifies a general purpose computer, processor 704 in Figure 7, as structure for “executing the instructions associated with the corresponding function” recited in each “means limitation,” except for the “means fro [sic] the first participant to communicate . . .” recited in claims 5 and 20. Pet. 7–9 (citing Ex. 1001, Fig. 7, col. 25, ll. 13–18). For the “means fro [sic] the first participant to communicate” limitation, Petitioner identifies transceiver 216, shown in Figure 2, reproduced supra. Pet. 9 (citing Ex. 1001, Fig. 2, col. 9, ll. 54–59). Patent Owner does not contest these identifications. We agree with Petitioner’s identifications and adopt them as our constructions of the means-plus-function limitations. Specifically, as to those means-plus-function limitations that correspond to processor 704 in Figure 7, Petitioner identifies in its claim chart the algorithm described in the specification for performing each function of these means. Pet. 8–9; See also Function Media, L.L.C. v. Google, Inc., 708 F.3d 1310, 1318 (Fed. Cir. 2013) (“When dealing with a ‘special purpose computer-implemented means-plus-function limitation,’ [the Federal Circuit] require[s] the specification to disclose the algorithm for performing the function.”); Blackboard, Inc. v. Desire2Learn, Inc., 574 F.3d 1371, 1384 (Fed. Cir. 2009) (“[W]hen a computer is referenced as support for a function in a means-plus-function claim, there must be some explanation of how the computer performs the claimed function.”).” slip op. at 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We are not persuaded by this reasoning. As Petitioner observes, the embodiments of the ’624 patent identified by Patent Owner are characterized as “examples,” and a person of ordinary skill “would understand that the example scenarios of the specification are not necessarily limiting on the claims.” Reply 3 (citing Ding Supp. Decl. ¶ 6). In addition, Petitioner notes that claim language in related patents owned by Patent Owner explicitly refers to participants, evidencing Patent Owner’s understanding “how to expressly create participant-specific voting requirements in claims.” Id. at 3. At the oral hearing, Patent Owner suggested that explicit reference to participants in such other claim language “was because it wanted to clarify that each participant got a single vote,” and explained its position that, in the claims at issue in this proceeding, “participant is implicit in the claim language as it is.” Tr. 78:16–25. But the claims are directed to a “communications apparatus,” and recite “votes” in the context of what the “particular communications channel” “receives.” Nothing within the structure of the claims requires resolving the origin of such votes. Furthermore, Patent Owner’s proposed construction is inconsistent with the construction it agreed to before the district court in the Qualcomm Litigation. In that litigation, the parties agreed that the term “vote” should be construed as “a binary expression (to use or not to use),” a construction that makes no reference to the origin of the “vote” as from a participant or otherwise. Ex. 1014, 6. We see no compelling reason to excuse the inconsistency by adopting a narrower construction when the Board applies a claim-construction standard (broadest reasonable interpretation) that could only result in the same or a broader construction. See Amazon.com, Inc. v. Barnesandnoble.com, Inc., 239 F.3d 1343, 1351 (Fed. Cir. 2001) (“A patent may not, like a ‘nose of wax,’ be twisted one way to avoid anticipation and another to find infringement.” (quoting Sterner Lighting, Inc. v. Allied Elec. Supply, Inc., 431 F.2d 539, 544 (5th Cir. 1970))). Accordingly, we construe “votes to use a particular communications channel” as “expressions of preference for using the particular communications channel.”” slip op. at 10
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable
“Patent Owner responds that “the Gerten device is not capable of and expressly teaches away from performing this functionality.” PO Resp. 15 (citing Melendez Decl. ¶ 33). Patent Owner contends that “Gerten’s disclosure is directed toward eliminating channels for use in an entire piconet as opposed to eliminating channels for use by certain participants within a piconet.” Id. at 16 (emphasis added). Patent Owner argues that Gerten does not disclose a selection kernel capable of maintaining synchronization between a master and more than one slave in a piconet, with the master and one slave using a default set of channels while the same master and a different slave use a different set of channels. Id. We are not persuaded that the absence of a specific teaching of such a selection kernel supports the conclusion that one of skill in the art would understand Gerten to function in the manner Patent Owner suggests. In this instance, Petitioner refers to two embodiments of Gerten “in which a first participant communicates with a second participant via a normal sequence and with another participant via an adaptive hopping sequence.” Reply 5. First, Figure 3 of Gerten is reproduced below. Figure 3 illustrates “methodology for determining and communicating channels to be avoided to a remote device.” Ex. 1003, col. 2, ll. 4–6. As illustrated in the drawing, a master unit performs a discovery process (block 110) upon connecting with a new slave unit. Ding Decl. ¶¶ 60, 64. If the slave unit is capable of using interference avoidance, the master unit begins the process of determining a modified set of channels for use (block 120). Id. ¶ 45. If a second slave unable to use interference avoidance enters the piconet, standard frequency hopping is used. Supp. Ding Decl. ¶ 9. Under Patent Owner’s characterization of Gerten, entry of the second slave into the network would require the first slave necessarily to revert back to the default hopping sequence. Id. ¶ 10. But this would undermine the stated benefits of Gerten, which explicitly discloses: The above process can be applied to a Bluetooth example and includes identification of a Bluetooth device’s ability to support interference avoidance, the measurements of signal strength on all channels and identification of which channel should not be used without violating the FCC rules, a method of modifying the Bluetooth hop sequence so that it will avoid channels containing strong or fixed interferers while still supporting standard Bluetooth hopping with other non-enabled members of the piconet and a method of relating necessary interference avoidance information to the remote Bluetooth devices. Ex. 1003, col. 4, l. 66–col. 5, l. 9 (emphasis added).” slip op. at 17
Patent outcomesUS 7,477,624 mixedClaim construction§ 102 anticipation§ 103 obviousnessPatents in suitUS 7,477,624 - Kingston Technology Company, Inc. v. Catr Co. Ltd.Some claims unpatentablePTAB · May 10, 2016 · IPR2015-00559 · APJ Bart A Gerstenblith · IPR · Final written decision
Claims 9, 14, 17, 19, and 21–23 are unpatentable as obvious over Matsumiya and Deng and over Wu and Hoogesteger; the remaining challenged claims were not shown unpatentable.
RulingsFinal written decision- Skill levelSkill level board ownDecided for petitioner
“1. Level of Ordinary Skill in the Art In our Final Written Decision in IPR 149, we found “that one of ordinary skill in the art would have had a degree in mechanical engineering or industrial design, but also a general understanding of the use of electrical components, which may be incorporated in mechanical designs.” IPR 149 Decision 23. The parties present the same arguments here, with respect to their views of the level of ordinary skill in the art, as they did in IPR 149. Accordingly, for the reasons discussed in our Final Written Decision in IPR 149 we adopt the same level of skill here. Id. at 22–23.” slip op. at 17
- Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner
“Second, Dr. Wolfe testified that Matsumiya discloses “a shaft” that protrudes from each side of the case. Ex. 1016 ¶ 97. On cross-examination, however, Dr. Wolfe admitted that while Matsumiya could disclose a “split axle,” “normally, you’d presume that it’s a through axle.” Ex. 2012, 85:9– 18. Dr. Wolfe did not explain in his direct testimony how either an axle or split axle would be integrated with or attached to at least one side of the case. Third, Petitioner relied on the express disclosure of Matsumiya, not a modification of Matsumiya, as teaching this element of the claims. See Pet. 16 (relying only on Matsumiya’s disclosure). In its Reply, Petitioner asserts, for the first time, that Matsumiya “could also use a snap hinge,” pointing to Professor Visser’s cross-examination testimony. Reply 13 (citing Ex. 1050, 127:9–11). Professor Visser’s testimony, however, does not support Petitioner’s argument. Professor Visser testified that Matsumiya does not show a snap-on hinge, and that a snap-on hinge would not have the same functionality as an axle. Ex. 1050, 127:18–21. He also testified that the two concentric rings on the arms of Matsumiya are inconsistent with a snap-on hinge. Id. at 128:17–20. Thus, the issue before us is not whether it would have been obvious to modify Matsumiya to include a snap-on hinge or hinge protuberance on the side of the case because that was not the basis set forth in the Petition and upon which we instituted review; rather, the issue is whether Petitioner has shown that Matsumiya discloses a hinge element or hinge protuberance integrated with or attached to at least one side of the case. In light of the record before us, and as detailed in the discussion above, we conclude that Petitioner has not shown that Matsumiya discloses a hinge element or a hinge protuberance “formed on at least one side of the case.” We find that Petitioner has failed to present sufficient evidence to show that Matsumiya discloses this element of the claims, and we find Patent Owner’s evidence in the form of Dr. Wolfe’s cross-examination testimony and Professor Visser’s testimony more persuasive.” slip op. at 22
- Obviousness (§103) › Analogous artNon analogous artDecided for patent owner
“Id. at 1:14–23. Accordingly, we find that Kindig’s field of endeavor is hinged enclosures to house appliances that make noise when operated. The ’544 patent states that “[t]he present invention relates to a flash memory apparatus, and more particularly to a flash memory apparatus, wherein a cover is not completely separated from the main body upon being in use so that lost [sic] of the cover is prevented.” Ex. 1001, 1:8–11. The ’544 patent is largely directed to a cover that rotates with respect to a case (as is evident from the parties’, and consequently our, extensive discussion of the hinged connection (i.e., hinge protuberances and hinge holes)), but is not readily disconnected. In fact, the ’544 patent discloses the recited “hooking groove” and “hooking threshold” specifically to prevent the hinge hole from being easily detached from the hinge protuberance. Id. at 3:36–43 (“Furthermore, a hooking groove 34 is preferably formed on the lower periphery of the hinge protuberance 33. A hooking threshold 45 is hooked on the hooking groove 34 and is preferably formed on a rim confining the hinge hole 41 in order to prevent the hinge hole 41 from being easily detached from the hinge protuberance 33 after joining of the hinge hole 41 and the hinge protuberance 33.”). Thus, we find that the ’544 patent’s field of endeavor is hinge assemblies for a flash memory apparatus.” slip op. at 32
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentable
“Second, Petitioner asserts that Kindig’s hinge connection “would advantageously help to retain connection between the cover of Matsumiya and the memory card,” id. at 25, but Petitioner has not shown that Matsumiya fails to retain the connection between case and cover or has difficulty doing so. Rather, from our review the record supports that Matsumiya’s cover is securely attached to the case. Additionally, we are unaware of any teaching in Matsumiya of disconnecting the cover from the case. Similarly, the ’544 patent aims to avoid disconnecting the cover from the case, as discussed above. Kindig, however, is directed to an easily detachable cover. Accordingly, Petitioner’s reason—as to why one of ordinary skill in the art would have been prompted to modify Matsumiya by adding the elements of claim 13 from Kindig—lacks a rational underpinning. 3. Conclusion of Obviousness For the foregoing reasons, after consideration of the entire record, we” slip op. at 35
Patent outcomesUS 6,926,544 mixed§ 103 obviousnesscites KSR · GrahamPatents in suitUS 6,926,544 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentablePTAB · Mar 4, 2016 · IPR2015-01011 · APJ Kalyan K Deshpande · IPR · Final written decision
Claims 1, 2, 5, and 10 of the ’469 patent are unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownDecided for patent owner
“connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time the query is transmitted to the server.” Id. at 1363. 11 Petitioner argues that the relevant specifications do not include an embodiment that “‘guarantees’ or ‘ensures’ the availability of the second process at any given point in time” and the file histories of the challenged patents “expressly reject[] the notion that the claims contain any guarantee of perfect accuracy.” Addʼl Br. 6. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter parties review.” Straight Path, 806 F.3d at 1363. We similarly do not offer any determination as to whether this claim construction is supported by the specifications of the ʼ704 patent, ʼ469 patent, and the ʼ121 patent. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 66 Pet. 24–30; 66 PO Resp. 32‒35; 67 Pet. 25–31; 67 PO Resp. 30‒34; 68 Pet. 24–29; 68 PO Resp. 36‒42. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and, therefore must be determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 11
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly and (2) requiring a renewal time period in which a computer must reregister. Ex. 1012, 62– 63, 68–69. Microsoft Manual discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. Microsoft Manual further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, Microsoft Manual discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in Microsoft Manual will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. Microsoft Manual discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“and AVAYA, Inc. (“AVAYA”) filed three Petitions and Motions to Join the IPR2014-01366, IPR2014-01367, and IPR2014-01368 proceedings. IPR2015-01011, Papers 2, 4; IPR2015-01007, Papers 3, 4; IPR2015-01006, Papers 2, 4. We granted these motions and joined Samsung, Cisco, and AVAYA (collectively, “Petitioner”) to these inter partes reviews. 66 Paper 26; 67 Paper 23; 68 Paper 25.” slip op. at 3
Patent outcomesUS 6,108,704 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 6,108,704 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentablePTAB · Mar 4, 2016 · IPR2015-01007 · APJ Kalyan K Deshpande · IPR · Final written decision
Claims 1, 2, 5, and 10 of the ’469 patent were held unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.
RulingsFinal written decision- BurdenFwd mixedMixed
“and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly and (2) requiring a renewal time period in which a computer must reregister. Ex. 1012, 62– 63, 68–69. Microsoft Manual discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. Microsoft Manual further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, Microsoft Manual discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in Microsoft Manual will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. Microsoft Manual discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“In Ancora Techs., the Federal Circuit explained that “[t]he ordinary meaning of the word ‘program’ in the computer context encompasses both operating systems and the applications that run on them (as well as other types of computer programs)” and “‘to a computer programmer’ a program is merely a ‘set of instructions’ for a computer.” Ancora Techs., Inc. v. Apple, Inc., 744 F.3d 732, 734 (Fed. Cir. 2014). Applying this guidance to the case before us, we agree with Petitioner and construe the term “process” to mean “a running instance of a computer program or application,” where a “computer program” is a set of instructions for a computer that encompasses both operating systems and the applications that run on them. We further note that the ʼ704, ʼ469, and ʼ121 patent specifications interchange the terms “process” and “processing unit.” For example, the specifications explain that a first “processing unit” is “established in the database [] as an active on-line party.” Ex. 1001, 5:29–34. The claims recite the term “process.” Accordingly, our construction is also consistent with the specifications, such that a “process” includes a “processing unit” that is running a program (operating system) or application.” slip op. at 14
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundUnpatentable
“Petitioner contends that “WINS is an implementation of NetBIOS” and, therefore, Petitioner contends that “one having skill in the art would have known about and been motivated to combine Microsoft Manual with NetBIOS.” Id. at 34 (citing 67 Ex. 1004 ¶¶ 88–89). We are persuaded by Petitioner that the combination is reasonable because Microsoft Manual demonstrates that Microsoft TCP/IP has combined the elements of NetBIOS and Microsoft Manual in the same manner in which Petitioner proposes to combine NetBIOS and Microsoft Manual. See 67 Ex. 1012, 3, 11. Microsoft Manual discloses that Microsoft TCP/IP for Windows NT provides support for application interfaces, including NetBIOS for establishing logical names and sessions on the network. Id. at 11. Microsoft Manual describes that “[w]hen WINS servers are in place on the network, NetBIOS over TCP/IP resolves names on a client computer by communication with the WINS server.” 67 Pet. 34 (quoting 67 Ex. 1012, 62). We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by Microsoft Manual, and a person with ordinary skill in the art would have readily combined the disclosures of Microsoft Manual and Microsoft Manual.” slip op. at 25
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable
“and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly and (2) requiring a renewal time period in which a computer must reregister. Ex. 1012, 62– 63, 68–69. Microsoft Manual discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. Microsoft Manual further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, Microsoft Manual discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in Microsoft Manual will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. Microsoft Manual discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1014, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to Microsoft Manual, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.” Given that the combination of Microsoft Manual and NetBIOS fails to teach or suggest the claims as construed, we need not reach the remaining arguments presented by Petitioner and Patent Owner.” slip op. at 19
Patent outcomesUS 6,009,469 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 6,009,469
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.