• Commscope Technologies, LLC v. Communications Components Antenna Inc.Institution denied
  PTAB · Nov 3, 2016 · IPR2016-00999 · APJ Jeffrey S Smith · IPR · Institution

  The Board denied institution because the petition did not show a reasonable likelihood of proving claims 1–28 unpatentable, principally because Yea did not establish the claimed asymmetrical coverage areas.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “partes review of claims 1–28 of U.S. Patent No. 8,311,582 B2 (Ex. 1001, “the ’582 patent”). Paper 1 (“Pet.”). Patent Owner, Communications Components Antenna Inc., filed a Preliminary Response. Paper 7 (“Prelim. Resp.”). Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any 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); see 37 C.F.R. § 42.108. Upon consideration of the Petition and the Preliminary Response, we are not persuaded Petitioner has demonstrated a reasonable likelihood that it would prevail in establishing the unpatentability of claims 1–28 of the ’582 patent. Accordingly, we do not institute an inter partes review.” slip op. at 2

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed petitioner constructionDecided for petitioner

    “Petitioner’s proposed construction of this limitation is supported by the specification of the ’582 patent. The ’582 patent discloses replacing a single sector coverage area with sub-sector coverage areas, at least one of which is an asymmetrical coverage area. Ex. 1001, 3:16–18. The ’582 patent discloses that the use of asymmetrical coverage areas permits the total coverage area to closely approximate the symmetrical sector coverage area being replaced, without creating excessively large sub-sector handover zones or introducing sever degradation in network performance. Id. at 3:18–24. The ’582 patent discloses creating the asymmetrical coverage areas by replacing an existing antenna with an antenna that has substantially the same coverage area, but divides the coverage area into a plurality of separate asymmetrical beams or sub-sectors. Id. at 4:32–38. As disclosed by the ’582 patent, the replacement antenna produces a plurality of separate beams, each defining a new sub-sector with only a small overlapping area between them and which together provide substantially identical coverage to the sector supported by the original antenna, to upgrade the single sector to a plurality of sub-sectors without significantly affecting neighboring sites. Id. at 4:51–57. The replacement antenna introduces asymmetry into the generated beam pattern. Id. at 4:58–60. The introduction of asymmetrical beams by the replacement antenna allows close approximation of the coverage area of the conventional sector antenna being replaced. Id. at 5:61–64. For purposes of this Decision, we adopt Petitioner’s proposed construction of “a plurality of sub-sector coverage areas extending therefrom, at least one of which is asymmetrical,” as a plurality of replacement sub-sector beams, at least one of which has an asymmetrical shape, where asymmetry includes deliberate or inherent asymmetry as the broadest reasonable construction consistent with the specification.” slip op. at 8

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “49 (Fed. Cir. 2005). There, the district court invalidated claims of the patent in suit on summary judgment based on the measured dimensions of a prior art patent figure. Id. at 1148. The Federal Circuit reversed, warning “that arguments based on drawings not explicitly made to scale in issued patents are unavailing.” Id. at 1149. Petitioner here does not identify any portion of Yea disclosing that Figures 4 and 8 are drawn accurately enough to determine an asymmetrical nature of the radiation patterns. Petitioner also fails to cite to any disclosure in Yea that identifies or describes an asymmetrical nature of the radiation patterns. Furthermore, Petitioner also has not explained why the shapes shown in the linear scale drawings of Figure 4 would show similar shapes when converted to a logarithmic scale. Additionally, Petitioner does not explain why the carrier to interference ratio shown in Figure 8 can be used to accurately measure antenna radiation beam patterns. We find Petitioner does not sufficiently establish that the plots shown in Figures 4 and 8 of Yea can be used to determine whether the antenna radiation beam pattern is asymmetrical. On the record before us, we determine the Petition and supporting evidence does not adequately establish a reasonable likelihood that Petitioner would prevail in showing that Yea anticipates independent claims 1, 13, and 20. b. Dependent Claims 2, 6, 7, 9, 11, 12, 14, 15, 18, 19, 21, 22, 24, and 27 Petitioner argues that Yea anticipates dependent claims 2, 6, 7, 9, 11, 12, 14, 15, 18, 19, 21, 22, 24, and 27. Pet. 47–53. In so arguing, Petitioner relies on Yea as disclosing the claimed asymmetrical coverage area. Id. Because we are not persuaded that Yea discloses this limitation, we are not persuaded that Petitioner establishes a reasonable likelihood of prevailing in showing that Yea anticipates dependent claims 2, 6, 7, 9, 11, 12, 14, 15, 18, 19, 21, 22, 24, and 27.” slip op. at 14

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation not foundNot shown unpatentableNot shown unpatentable

    “as well as testimony of both Mr. Collins and Mr. Cosgrove. Under Rule 37 C.F.R. § 42.108, any genuine issues of material fact created by the testimonial evidence should be viewed in light most favorable to the petitioner solely for purposes of deciding whether to institute an inter partes review. Even reviewing the testimony of Mr. Collins in the light most favorable to Petitioner, we determine Petitioner has established only that asymmetrical beams may be used in a planar array antenna, but not that a person of ordinary skill in the art would have understood steered beams of a planar array antenna are necessarily asymmetrical. Mr. Collins cites to Litva (Ex. 1009) and Wästberg (Ex. 1018) in stating that prior art steered beams of a planar array antenna can be asymmetrical beams. Ex. 1024 ¶ 179. We credit Patent Owner’s arguments and the testimony of Mr. Cosgrove to determine Petitioner does not sufficiently establish the likelihood that a person of ordinary skill in the art would have understood that steered beams of a planar array antenna are necessarily asymmetrical. Further, Petitioner fails to set forth a sufficient rationale for why a person of ordinary skill in the art would use the asymmetrical beams of the prior art with the disclosure of Yea. Pet. 39–40. On the record before us, we determine the Petition and supporting evidence does not adequately establish a reasonable likelihood that using asymmetrical beams in Yea would have been obvious. We therefore conclude that the information presented does not show a reasonable likelihood that Petitioner would prevail in showing the subject matter of claims 1, 2, 6, 7, 9, 11–15, 18–22, 24, and 27 would have been obvious over Yea, Metawave Website, Litva, and Wästberg.” slip op. at 22

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,311,582
• Mastercard International Inc. v. Leon StamblerAll claims unpatentable
  PTAB · Jul 6, 2016 · CBM2015-00044 · APJ Peter P Chen · CBM · Final written decision

  Claims 51 and 53 are unpatentable as anticipated by Davies; claims 51, 53, 55, and 56 are unpatentable as obvious over Davies and Meyer; claim 55 over Davies and Nechvatal; and claim 56 over Davies, …

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “F. Level of Ordinary Skill in the Art Petitioner’s proposal for the level of ordinary skill in the art is “at least a bachelors degree in computer programming and two years’ experience as a programmer or developer in the field of computer science, with a working understanding of cryptographic operations for transforming original input into a coded output using a known algorithm.” Pet. 14–15. Patent Owner has proposed similarly, that one of ordinary skill in the art would possess “(1) undergraduate education in mathematics, physics, computer science, electrical engineering or similar technical subject; and (2) either postgraduate education in networking, cryptography, or other discipline encompassing information theory, or equivalent experience with applications involving communication of financial, military, medical or similarly sensitive data over secure and non-secure networks.” Prelim. Resp. 30–31. We determine that an express definition of the level of ordinary skill is not required. The level of ordinary skill in the art can be reflected in the cited prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (“[T]he absence of specific findings on the level of skill in the art does not give rise to reversible error ‘where the prior art itself reflects an appropriate level and a need for testimony is not shown.’”) (internal quotations omitted); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995). Therefore, we find the level of ordinary skill in the art to be reflected in the cited references.” slip op. at 16

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)Term construed board ownDecided for petitioner

    “1. “variable authentication number (VAN)” In the Decision to Institute, we construed the term “variable authentication number” or “VAN” as “a variable number resulting from a coding operation that can be used in verifying the identity of a party or the integrity of information or both.” Dec. to Inst. 8. See also Case IPR2014-00694, slip op. at 8–9 (PTAB Oct. 31, 2014) (Paper 10). Patent Owner “does not challenge this construction.” PO Resp. 16–17. Patent Owner asserts additional construction of the term is necessary for CBM standing issues, but does not elaborate further. PO Resp. 1. Patent Owner also argues we incorrectly applied the broadest reasonable interpretation to the term in the Decision to Institute. PO Resp. 9. The Decision to Institute noted that our review of the claims of the expired ’302 patent is similar to that of a district court’s review, In re Rambus, Inc., 694 F.3d 42, 46 (Fed. Cir. 2012); Phillips v. AWH Corp., 415 F.3d 1303, 1327 (Fed. Cir. 2005), but inadvertently mentioned the broadest reasonable interpretation standard in construing this term. Dec. to Inst. 7–8. We reaffirm our agreement with Patent Owner that the Phillips framework is applied to the expired ’302 patent. Our construction of “VAN” is the same under either claim construction standard. We reject Patent Owner’s undeveloped argument regarding standing, and maintain the construction of VAN from the Decision to Institute, as the ordinary and customary meaning of the term: “a variable number resulting from a coding operation that can be used in verifying the identity of a party or the integrity of information or both.”” slip op. at 10

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed patent owner constructionDecided for patent owner

    “2. Sequence of method steps: receiving, generating In the Decision to Institute, we agreed with Patent Owner and construed the sequence of method steps in independent claim 51 to mean that at least a portion of the receiving step must precede the generating step. Dec. to Inst. 8. See also Case IPR2014-00694, slip op. at 11–14 (PTAB Oct. 31, 2014) (Paper 10). We maintain that construction as the ordinary and customary meaning of the sequence of the receiving and generating method steps.” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Preamble limiting or notPreamble limitingDecided for patent owner

    “intended use of an invention is generally not treated as limiting the scope of the claim. Boehringer Ingelheim Vetmedica, Inc. v. Schering-Plough Corp., 320 F.3d 1339, 1345 (Fed. Cir. 2003). However, “a preamble limits the invention if it recites essential structure or steps, or if it is ‘necessary to give life, meaning, and vitality’ to the claim.” Catalina Mktg. Int'l, Inc. v. Coolsavings.com, Inc., 289 F.3d 801, 808 (Fed. Cir. 2002) (citing Pitney Bowes Inc. v. Hewlett-Packard Co., 182 F.3d 1298, 1305 (Fed. Cir. 1999). “The effect preamble language should be given can be resolved only on review of the entirety of the patent to gain an understanding of what the inventors actually invented and intended to encompass by the claim.” Corning Glass Works v. Sumitomo Elec. U.S.A., Inc., 868 F.2d 1251, 1257 (Fed. Cir. 1989). When the limitations in the body of the claim rely upon or derive essential structure from the preamble elements, e.g., the preamble serves as an antecedent basis for limitations in the claim, then the preamble acts as a necessary component of the claimed invention and is limiting. See Eaton Corp. v. Rockwell Int’l Corp., 323 F.3d 1332, 1339 (Fed. Cir. 2003). In this case, the preamble of independent claim 51 recites “a credential being previously issued,” and the limitations of the claim include “determining whether the at least a portion of the received funds transfer information is authentic by using the VAN and the credential information.” Ex. 1001, 33:18–19, 33:29–31. Thus, the preamble’s recitation of “a credential” is an antecedent basis for the recited “the credential information” in the “determining” step, and we determine that the preamble limits the scope of the challenged independent claim 51 and dependent claims 53, 55, and 56.” slip op. at 11

  Patent outcomesUS 5,793,302 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 5,793,302
• Corelogic, Inc. v. Boundary Solutions, Inc.No claims unpatentable
  PTAB · 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 unpatentable
  Claim construction§ 102 anticipation
  Patents in suitUS 8,065,352
• Actifio, Inc. v. Delphix Corp.All claims unpatentable
  PTAB · May 11, 2016 · IPR2015-00100 · APJ Patrick R Scanlon · IPR · Final written decision

  Claims 1–6, 8, 14, 16–19, 24, and 25 are unpatentable as obvious over Sanders, Edwards, and Chapman.

  RulingsFinal written decision

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedOther

    “and Petitioner’s Response (Paper 45), insofar as they relate to public accessibility of Sanders and Chapman. We acknowledge the potential for bias in Mr. Hernandez’s testimony as a present employee of Petitioner. We find, however, the testimony in Mr. Hernandez’s Declarations as to public accessibility of Sanders and Chapman to be credible. As an earlier panel of the Board has found, in a proceeding involving a different patent and different parties, documents such as Sanders and Chapman are dated technical documents or whitepapers, having no indication of being mere drafts or internal papers, each of which is “a type of document whose very purpose is public disclosure.” Veeam Software Corp. v. Symantec Corp., Case IPR2014- 00089, slip op. at 14 (PTAB Apr. 25, 2014) (Paper 9).” slip op. at 10

  • ExcludeMotion to exclude, grantedMotion to exclude, deniedGranted in part

    “1032, 1034–1037, 1040–1044, 1046, 1047, 1049, 1053, 1054, 1056, 1058, 1059, 1063, 1065, 1066, and 1069. Paper 37 (“Mot. to Exclude”), 1. In inter partes reviews, documents are admitted into evidence subject to an opposing party asserting objections to the evidence and moving to exclude the evidence. 37 C.F.R. § 42.64. As movant, Patent Owner has the burden of showing that an Exhibit is not admissible. 37 C.F.R. § 42.20(c).” slip op. at 54

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “We begin our analysis by considering the language of the claims themselves. Phillips v. AWH Corp., 415 F.3d 1303, 1314, 1315 (Fed. Cir. 2005) (en banc). The term “metadata” is not recited in any of the claims of” slip op. at 12

  • Claim Construction › Intrinsic evidence (Phillips canons) › Lexicography (patentee as own lexicographer)Term construed petitioner constructionDecided for petitioner

    “A database block is a unit of data used by a database and comprises a specific number of bytes stored in the storage. A database block can also be referred to as a page. A portion of the database block stores metadata associated with the database block. PO Resp. 18 (quoting Ex. 2002, 2:7–12). The first phrase in the cited passage above explicitly defines the term, by stating “[a] database block is a unit of data used by a database.”4 Ex. 2002, 2:7–8. Although the sentence following shortly thereafter states that a database block “stores metadata,” that sentence by itself is insufficient to limit the disputed term by requiring the unclaimed “metadata” feature because it 3 Patent Owner describes the ’808 patent as being related to the ’361 patent. Prelim. Resp. 28. 4 The first sentence also states a database block comprises “a specific number of bytes stored in the storage.” For the reasons discussed below, we find this addition is not part of the explicit definition but, rather, represents embodiments within the defined term. Patent Owner also fails to explain how to interpret this particular phrase or how it presents a material issue related to the prior art. does not state unambiguously that all “database blocks” must include metadata. See Liebel-Flarsheim Co. v. Medrad, Inc., 358 F.3d 898, 906 (Fed. Cir. 2004) (construing a claim term broadly because “[n]o statement in the written description [ ] constitute[d] a limitation on the scope of the invention”) (alterations in original) (quoting Brookhill-Wilk 1, LLC. v. Intuitive Surgical, Inc., 334 F.3d 1294, 1301 (Fed. Cir. 2003)). Further, the cited passage also does not exclude the possibility of some database blocks not having any metadata. See id. at 908 (passages in the Summary of the Invention section of a patent did not limit the scope of the invention because the passages, “although focusing on the use of the invention in conjunction with pressure jackets, do not disclaim the use of the invention in the absence of a pressure jacket”). More importantly, the rest of the ’361 patent is consistent with a definition of database blocks that does not require metadata in all database blocks.” slip op. at 13

  Patent outcomesUS 8,566,361 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,566,361
• Actifio, Inc. v. Delphix Corp.All claims unpatentable
  PTAB · Apr 29, 2016 · IPR2015-00108 · APJ Patrick R Scanlon · IPR · Final written decision

  Claims 9–13 and 21–23 are unpatentable as obvious under § 103 over Sanders, Edwards, and Patel; claims 13 and 23 also rely on Chapman.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artPrinted publication establishedDecided for petitioner

    “printed publications” in accordance with 35 U.S.C. §§ 102 and 311(b). PO Resp. 1‒5. We look to the underlying facts to make a legal determination as to whether a document is a printed publication. Suffolk Techs., LLC v. AOL Inc., 752 F.3d 1358, 1364 (Fed. Cir. 2014). The determination of whether a document is a “printed publication” under 35 U.S.C. § 102(b) involves a caseby-case inquiry into the facts and circumstances surrounding its disclosure to members of the public. In re Klopfenstein, 380 F.3d 1345, 1350 (Fed. Cir. 2004). Public accessibility is a key question in determining whether a document is a printed publication and is determined on a case-by-case basis. Suffolk Techs., 752 F.3d at 1364. To qualify as a printed publication, a document “must have been sufficiently accessible to the public interested in the art.” In re Lister, 583 F.3d 1307, 1311 (Fed. Cir. 2009). slip op. at 6

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “The first phrase in the cited passage above explicitly defines the term, by stating “[a] database block is a unit of data used by a database.”4 Ex. 2102, 2:7–8. Although the sentence following shortly thereafter states that a database block “stores metadata,” that sentence by itself is insufficient to limit the disputed term by requiring the unclaimed “metadata” feature because it does not state unambiguously that all “database blocks” must include metadata. See Liebel-Flarsheim Co. v. Medrad, Inc., 358 F.3d 898, 906 (Fed. Cir. 2004) (construing a claim term broadly because “[n]o statement in the written description [ ] constitute[d] a limitation on the scope of the invention”) (quoting Brookhill-Wilk 1, LLC. v. Intuitive Surgical, Inc., 334 F.3d 1294, 1301 (Fed. Cir. 2003)). Further, the cited passage also does not exclude the possibility of some database blocks not having any metadata. See id. at 908 (passages in the Summary of the Invention section of a patent did not limit the scope of the invention because the passages, “although focusing on the use of the invention in conjunction with pressure jackets, do not disclaim the use of the invention in the absence of a pressure jacket”). More importantly, the rest of the ’361 patent is consistent with a definition of database blocks that does not require metadata in all database blocks.” slip op. at 14

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “We are not persuaded by Patent Owner’s arguments. The crux of these arguments appears to be that, because a Snapshot copy allegedly is an exact copy of the current state of the volume, SnapMirror does not utilize database blocks from different points in time to create a Snapshot copy. The claim language, however, does not require database blocks for different point-in-time copies to be utilized in this manner. Rather, the claim language merely requires receiving and storing database blocks for different point-in-time copies. We agree with Petitioner that the combined teachings of Sanders and Edwards disclose receiving and storing database blocks for different point-intime copies. Sanders discloses that “[t]he SnapMirror initialize command creates a Snapshot copy of the source volume and transfers data from the source to the destination volume,” such that the transferred data is received and stored at the destination volume. Ex. 1104, 22. We also credit Dr. Zadok’s testimony that a Snapshot copy is a point-in-time copy. Ex. 1117 ¶¶ 44, 123. Thus, each Snapshot copy would result in transferred data (i.e., database block) for different point-in-time copies being received and stored. Lastly, even if Patent Owner is correct that a given Snapshot copy uses only database blocks from the same point in time, we agree with Petitioner that this does not mean that database blocks for different point-in-time copies are not received and stored. We conclude that a preponderance of the evidence demonstrates that a person of ordinary skill would have found the limitation of loading the first database at multiple points in time, including receiving and storing database blocks for different point-in-time copies, obvious.” slip op. at 47

  • ExcludeMotion to exclude, grantedMotion to exclude, deniedMixed

    “1132, 1133, 1135, 1136, 1138, 1141–1145, 1147, 1148, 1150, 1154, 1155, 1157, 1159, 1160, 1164, 1166, and 1167. Paper 36 (“Mot. to Exclude”), 1. In inter partes reviews, documents are admitted into evidence subject to an opposing party asserting objections to the evidence and moving to exclude the evidence. 37 C.F.R. § 42.64. As movant, Patent Owner has the burden of showing that an Exhibit is not admissible. 37 C.F.R. § 42.20(c). Patent Owner contends that Petitioner does not rely on Exhibits 1132, 1133, 1135, 1138, 1144, 1148, 1150, 1154, 1157, 1159, 1164, 1166, and 1167. Mot. To Exclude 1 n.1. Petitioner does not dispute this contention. See Paper 46 (“Opp. Mot. to Exclude”). We, therefore, grant Patent Owner’s motion as it pertains to Exhibits 1132, 1133, 1135, 1138, 1144, 1150, 1154, 1157, 1159, 1164, 1166, and 1167. We note, however, that Petitioner does rely on Exhibit 1148. See Reply 11. For reasons discussed below, we deny Patent Owner’s motion as it pertains to Exhibit 1148. Further, Petitioner has moved, unopposed, to expunge Exhibit 1128 (see Paper 34), which motion we hereby grant. Of the remaining objected-to Exhibits, our Final Written Decision discusses and relies on only Exhibits 1106, 1120, 1147, and 1148. We determine, for reasons set forth above, that Petitioner has demonstrated by a preponderance of the evidence that the challenged claims are unpatentable, without need for Petitioner’s additional arguments or evidence in relation to the remaining additional Exhibits. Accordingly, Patent Owner’s motion to exclude Exhibits 1136, 1141–1143, 1145, 1155, and 1160 is dismissed as moot.” slip op. at 57

  Patent outcomesUS 8,566,361 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,566,361
• Sandisk Corporation v. Netlist, Inc.Rehearing denied
  PTAB · Apr 27, 2016 · IPR2014-00970 · APJ Linda M Gaudette · IPR · Rehearing

  Denied SanDisk’s rehearing request; the Board maintained its findings that claims 2, 5, and 6 were not shown obvious over Huang and claims 17–19 and 35 were not shown anticipated by Averbuj.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “II. STANDARD OF REVIEW The party requesting rehearing has the burden of showing the decision should be modified, and “[t]he request must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, or a reply.” 37 C.F.R. § 42.71(d).” slip op. at 3

  • BurdenNot shown unpatentable

    “20–21 (“Averbuj discloses that in BIST mode, the multiplexer 46 shown in Fig. 6 selectively inputs signals BIST_ADDR/CTRL (i.e., address and control signals from the control module) to the address and control port of the corresponding memory device 12.” (emphasis added)). In other words, the Petition is devoid of any discussion of BIST_EN in connection with the limitations of claims 17–19 and 35. See Pet. 19–21. Likewise, the Reply fails to contain any discussion of how the claim limitations are met by Averbuj’s use of the BIST_EN signal. See Reply 17. 37 C.F.R. § 42.22(a)(2) requires each petition to include “[a] full statement of the reasons for the relief requested, including a detailed explanation of the significance of the evidence including material facts, and the governing law, rules, and precedent.” Our discussion in the Final Decision of the patentability challenge as to claims 17–19 and 35 based on anticipation by Averbuj addresses Petitioner’s arguments in the Petition and Reply, which are limited to a contention that Averbuj’s multiplexer 46 is required to meet the “configured to selectively input” and “selectively inputs” limitations recited in claims 17–19 and 35. See Final Dec. 44–46 (citing Pet. 19–21; Reply 17). In arguing that we should have considered Dr. Alpert’s testimony that Averbuj’s sequencer, by generating a BIST_EN signal, is “configured to selectively input”/“selectively inputs” address and control signals to the memory modules, Petitioner attempts to improperly incorporate arguments into its Petition and Reply by reference to Dr. Alpert’s declaration testimony. See 37 C.F.R. § 42.6(a)(3) (“Arguments must not be incorporated by reference from one document into another document.”). In any event, we find the declaration testimony relied on by Petitioner in support of this Request (see Req. Reh’g 13) supports our determination that Petitioner failed to show, by a preponderance of the evidence, that Averbuj anticipates claims 17–19 and 35. Dr. Alpert testified that if the “configuration [to selectively input to the address and control ports] is determined to require the structure that performs the selection itself, then the disclosed control module also includes multiplexer 46 of memory interface 41.” Ex. 1007 ¶ 78 (emphasis added); see also id. ¶ 81 (identifying multiplexer 46 as the “DRAM controller which performs the selective inputting” as recited in claim 18). Petitioner did not explain (see Pet. 19–21; Reply 17) how Averbuj describes multiplexer 46 as being part of sequencer 8 (the alleged control module). See Final Dec. 45–46 (explaining that Petitioner has not addressed Patent Owner’s argument that the device that selectively inputs address and control signals to memory modules 12 is multiplexer 46 of memory interface 41 (the alleged data handler), not sequencer 8 (the alleged control module)). In sum, for the above reasons, we are not persuaded of error in our determination that Petitioner did not meet its burden to establish unpatentability of claims 17–19 and 35 under 35 U.S.C. § 102(b) based on Averbuj.” slip op. at 11

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successNot shown unpatentableMotivation not foundNot shown unpatentable

    “Huang and Tsern, Petitioner relied on the declaration testimony of its expert, Dr. Donald Alpert (Ex. 1007). See, e.g., id. at 44 (citing Ex. 1007 ¶ 222 in support of its challenge as to claim 2). In concluding Petitioner had not demonstrated a reasonable likelihood it would prevail in showing that claims 2, 5, and 6 would have been obvious over Huang in view of Tsern, we said the following: Dr. Alpert’s opinion that a person of ordinary skill in the art would have been motivated to combine Huang and Tsern . . . is either unsupported or relies on disclosure in the ’434 patent Detailed Description. See, e.g., Ex. 1007 ¶¶ 193, 199, and 206. . . . [T]here is no evidence on this record that the cited portions of the ’434 patent are a description of prior art. Moreover, Dr. Alpert’s statements lack sufficient articulated reasoning with rational underpinning as to why an ordinary artisan at the time of the invention would have had a reason to combine the prior art elements in the manner required by the challenged claims.” slip op. at 4

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “statement of the reasons for the relief requested, including a detailed explanation of the significance of the evidence including material facts, and the governing law, rules, and precedent.” Our discussion in the Final Decision of the patentability challenge as to claims 17–19 and 35 based on anticipation by Averbuj addresses Petitioner’s arguments in the Petition and Reply, which are limited to a contention that Averbuj’s multiplexer 46 is required to meet the “configured to selectively input” and “selectively inputs” limitations recited in claims 17–19 and 35. See Final Dec. 44–46 (citing Pet. 19–21; Reply 17). In arguing that we should have considered Dr. Alpert’s testimony that Averbuj’s sequencer, by generating a BIST_EN signal, is “configured to selectively input”/“selectively inputs” address and control signals to the memory modules, Petitioner attempts to improperly incorporate arguments into its Petition and Reply by reference to Dr. Alpert’s declaration testimony. See 37 C.F.R. § 42.6(a)(3) (“Arguments must not be incorporated by reference from one document into another document.”). In any event, we find the declaration testimony relied on by Petitioner in support of this Request (see Req. Reh’g 13) supports our determination that Petitioner failed to show, by a preponderance of the evidence, that Averbuj anticipates claims 17–19 and 35. Dr. Alpert testified that if the “configuration [to selectively input to the address and control ports] is determined to require the structure that performs the selection itself, then the disclosed control module also includes multiplexer 46 of memory interface 41.” Ex. 1007 ¶ 78 (emphasis added); see also id. ¶ 81 (identifying multiplexer 46 as the “DRAM controller which performs the selective inputting” as recited in claim 18). Petitioner did not explain (see Pet. 19–21; Reply 17) how Averbuj describes multiplexer 46 as being part of sequencer 8 (the alleged control module). See Final Dec. 45–46 (explaining that Petitioner has not addressed Patent Owner’s argument that the device that selectively inputs address and control signals to memory modules 12 is multiplexer 46 of memory interface 41 (the alleged data handler), not sequencer 8 (the alleged control module)). In sum, for the above reasons, we are not persuaded of error in our determination that Petitioner did not meet its burden to establish unpatentability of claims 17–19 and 35 under 35 U.S.C. § 102(b) based on Averbuj.” slip op. at 11

  § 102 anticipation§ 103 obviousness
  Patents in suitUS 8,001,434
• Actifio, Inc. v. Delphix Corp.All claims unpatentable
  PTAB · Apr 27, 2016 · IPR2015-00136 · APJ Jennifer S Bisk · IPR · Final written decision

  Claims 1, 4, 5, 27–29, and 34 are unpatentable under § 103 over the NetApp references, with Hart added for claims 4, 5, 29, and 34.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “A given reference is ‘publicly accessible’ upon a satisfactory showing that such document has been disseminated or otherwise made available to the extent that persons interested and ordinarily skilled in the subject matter or art exercising reasonable diligence, can locate it.” SRI Int’l, Inc. v. Internet Sec. Sys., Inc. 511 F.3d 1186, 1194 (Fed. Cir. 2008) (quoting Bruckelmyer v. Ground Heaters, Inc., 445 F.3d 1374, 1378 (Fed. Cir. 2006)). Petitioner asserts that the level of ordinary skill is not disputed in this case and that “[t]here is no difference between customers and potential customers of NetApp and a [person of ordinary skill in the art].” Reply 6–7. Mr. Hernandez testifies that NetApp’s customers and potential customers were entities or individuals who were “interested in data storage technology, data management technology, database storage and management technology, and related technologies.” Ex. 1048 ¶ 3. As discussed above, Mr. Hernandez also testifies NetApp had more than two hundred Systems Engineers and other sales personnel during the period of 2004–2009 who distributed NetApp’s technical documents (including Neto) to “thousands” of customers and potential customers. Id. ¶ 4. Hence, the record supports Petitioner’s contention that Neto was distributed to persons interested and ordinarily skilled in the subject matter of database technology at the time of its publication. See Reply 6–7. In view of the foregoing considerations, we find that Petitioner has established, by a preponderance of the evidence, that Neto (dated April 2009) was sufficiently disseminated to persons of ordinary skill interested in database technology to be deemed “publicly accessible” at least more than one year before November 30, 2010, the earliest possible priority date of the ʼ174 patent. See Ex. 1001, (60). Petitioner has also established, by a preponderance of the evidence, that Klivansky (dated October 2004) was available to the interested public at least more than one year before the critical date. Therefore, on this record, we determine Neto and Klivansky qualify as prior art printed publications under 35 U.S.C. § 102(b). slip op. at 18

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “PO Resp. 18–19 (quoting Ex. 2002, 2:7–12). The first phrase in the cited passage above explicitly defines the term, by stating “[a] database block is a unit of data used by a database.”12 Ex. 2002, 2:7–9. Although the sentence following shortly thereafter states that a database block “stores metadata,” that sentence by itself is insufficient to limit the disputed term by requiring the unclaimed “metadata” feature because it does not state unambiguously that all “database blocks” must include metadata. See Liebel-Flarsheim Co. v. Medrad, Inc., 358 F.3d 898, 906 (Fed. Cir. 2004) (construing a claim term broadly because “[n]o statement in the written description [ ] constitute[d] a limitation on the scope of the invention”) (quoting Brookhill-Wilk 1, LLC. v. Intuitive Surgical, Inc., 334 F.3d 1294, 1301 (Fed. Cir. 2003)). Further, the cited passage also does 12 The first sentence also states a database block comprises “a specific number of bytes stored in the storage.” For the reasons discussed below, we find this addition is not part of the explicit definition but, rather, represents embodiments within the defined term. Patent Owner also fails to explain how to interpret this particular phrase or how it presents a material issue related to the prior art. not exclude the possibility of some database blocks not having any metadata. See id. at 908 (passages in the Summary of the Invention section of a patent did not limit the scope of the invention because the passages, “although focusing on the use of the invention in conjunction with pressure jackets, do not disclaim the use of the invention in the absence of a pressure jacket”). More importantly, the rest of the ’174 patent is consistent with a definition of database blocks that does not require metadata in all database blocks.” slip op. at 21

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “We are persuaded that a preponderance of evidence demonstrates that the four NetApp References are sufficiently related for purposes of this obviousness analysis. Patent Owner does not dispute that all four documents refer to NetApp products and technologies that include FlexVol, FlexClone, Snapshots, and the ONTAP operating system. See Ex. 1018 ¶¶ 35–43; PO Resp. 35–39. Even if the documents refer to various versions of those products and technologies, we are persuaded that a person of ordinary skill in the art would have been motivated to look to the teachings of the four references based on express disclosures in the references themselves. For example, the basics of NetApp storage and cloning are described by Edwards and Edwards II. Pet. 30–31 (citing Ex. 1018 ¶¶ 102–103). Although the patent discussing this cloning technology (Ex. 1005, filed April 30, 2004) was filed prior to the publication of an article (Ex. 1003, dated June 22–27, 2008) on the same topic, we are not persuaded that this time difference would deter a person of ordinary skill from combining the teachings of the two references. This is true even if the Edwards article describes updates to the cloning technology not discussed by Edwards II. And Edwards explicitly discusses the use of writable Snapshot copies in database environments to make “copies of a production database for development or test purposes.” Ex. 1003, 14. A person of ordinary skill in the art looking to implement such a solution would have looked to other NetApp publications such as Neto, which explicitly states that it “is intended for use by ‘Oracle database administrators, storage administrators, and architects implementing a backup, recovery, and cloning solution for Oracle databases running on NetApp storage’” (Pet. 30 (quoting Ex. 1004, 4)) and Klivansky, which describes its contents as being useful as “a way of understanding the full landscape of FlexClone benefits, as a refresher of specific FlexClone operations, or as a guided tutorial that filer administrators can try” (Pet. 31 (quoting Ex. 1006, 25)). Given these explicit statements, we are persuaded that a person of ordinary skill would look to combine the teachings of Klivansky with the teachings of the other references even if Klivansky, published in 2004 (Ex. 1006), discussed an older version of the cloning technology.” slip op. at 48

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundUnpatentable

    “The Petition further explains that a person of ordinary skill would have found it obvious to modify NetApp’s existing SnapManager GUI (as disclosed in Neto) for Hart’s timeline GUI because they provide similar functionality of managing multiple point-in-time databases and both allow restoring files to their prior stated based on a selected point-in-time. Pet. 34–35 (citing Ex. 1018 ¶ 117–120). We find a preponderance of the evidence supports this assertion. We find persuasive Dr. Zadok’s testimony that the difference between the two references is that “Hart’s GUI used a timeline structure to display stored snapshots, whereas Neto used a list structure to display backups (snapshots), one of which could be selected for restoration by right-clicking it.” Ex. 1018 ¶ 120. And we agree that “[s]ubstituting Hart’s timeline-based GUI for selecting (typically by clicking a mouse) a point-in-time copy for Neto’s right-click based method of selection was nothing more than a simple substitution of one known method of selection with another.” Pet. at 35; see also Ex. 1007 ¶ 25 (“[I]t should be apparent that the disclosed implementations can be incorporated in, or integrated with, any electronic device that has a user interface.”). Moreover, we credit Dr. Zadok’s testimony that “Neto’s examples name the point-in-time copies based on the time they were taken and can list them alphabetically; thus, they were typically arranged in a timeline” and concludes that “[g]iven the similarities . . . it would have been obvious for a POSITA to substitute Neto’s GUI with Hart’s GUI to perform the snapshot backup, restore, and clone functions described in Neto, Edwards, Edwards II, and Klivansky.” Ex. 1018 ¶ 120. We, therefore, find a preponderance of the evidence demonstrates that a person of ordinary skill would have had reason to combine the teachings of the Edwards, Edwards II, Neto, and Klivansky with Hart. In sum, as with the independent claims, we have reviewed both parties’ arguments and supporting evidence, including the disclosure of all four references and the testimony of both Dr. Zadok and Dr. Shenoy. Despite the counter-arguments in Patent Owner’s Response, and the evidence cited therein, for the reasons discussed above, Petitioner has shown, by a preponderance of the evidence, that each of claims 4, 5, 29, and 34 is unpatentable under 35 U.S.C. § 103 as directed to subject matter obvious over the combination of Edwards, Edwards II, Neto, Klivansky, and Hart.” slip op. at 69

  Patent outcomesUS 8,468,174 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,468,174
• Actifio, Inc. v. Delphix Corp.All claims unpatentable
  PTAB · Apr 27, 2016 · IPR2015-00128 · APJ Jennifer S Bisk · IPR · Final written decision

  Claims 1, 4, 5, 27–29, and 34 are unpatentable as obvious over the NetApp references, with Hart added for claims 4, 5, 29, and 34.

  RulingsFinal written decision

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedReference is prior artDecided for petitioner

    “A given reference is ‘publicly accessible’ upon a satisfactory showing that such document has been disseminated or otherwise made available to the extent that persons interested and ordinarily skilled in the subject matter or art exercising reasonable diligence, can locate it.” SRI Int’l, Inc. v. Internet Sec. Sys., Inc. 511 F.3d 1186, 1194 (Fed. Cir. 2008) (quoting Bruckelmyer v. Ground Heaters, Inc., 445 F.3d 1374, 1378 (Fed. Cir. 2006)). Petitioner asserts that the level of ordinary skill is not disputed in this case and that “[t]here is no difference between customers and potential customers of NetApp and a [person of ordinary skill in the art].” Reply 6–7. Mr. Hernandez testifies that NetApp’s customers and potential customers were entities or individuals who were “interested in data storage technology, data management technology, database storage and management technology, and related technologies.” Ex. 1048 ¶ 3. As discussed above, Mr. Hernandez also testifies NetApp had more than two hundred Systems Engineers and other sales personnel during the period of 2004–2009 who distributed NetApp’s technical documents (including Neto) to “thousands” of customers and potential customers. Id. ¶ 4. Hence, the record supports Petitioner’s contention that Neto was distributed to persons interested and ordinarily skilled in the subject matter of database technology at the time of its publication. See Reply 6–7. In view of the foregoing considerations, we find that Petitioner has established, by a preponderance of the evidence, that Neto (dated April 2009) was sufficiently disseminated to persons of ordinary skill interested in database technology to be deemed “publicly accessible” at least more than one year before November 30, 2010, the earliest possible priority date of the ʼ174 patent. See Ex. 1001, (60). Petitioner has also established, by a preponderance of the evidence, that Klivansky (dated October 2004) was available to the interested public at least more than one year before the critical date. Therefore, on this record, we determine Neto and Klivansky qualify as prior art printed publications under 35 U.S.C. § 102(b). slip op. at 18

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner

    “Therefore, in view of the entire disclosure of the ’174 patent and the plain language of the claims, we find that the intrinsic record before us does not justify limiting the term “database block” by reading in the “metadata” limitation not found in the claims. See Liebel-Flarsheim Co., 358 F.3d at 908.” slip op. at 25

  • Obviousness (§103) › Analogous artAnalogous artDecided for petitioner

    “For example, the basics of NetApp storage and cloning are described by Edwards and Edwards II. Pet. 30–31 (citing Ex. 1018 ¶¶ 102–103). Although the patent discussing this cloning technology (Ex. 1005, filed April 30, 2004) was filed prior to the publication of an article (Ex. 1003, dated June 22–27, 2008) on the same topic, we are not persuaded that this time difference would deter a person of ordinary skill from combining the teachings of the two references. This is true even if the Edwards article describes updates to the cloning technology not discussed by Edwards II. And Edwards explicitly discusses the use of writable Snapshot copies in database environments to make “copies of a production database for development or test purposes.” Ex. 1003, 14. A person of ordinary skill in the art looking to implement such a solution would have looked to other NetApp publications such as Neto, which explicitly states that it “is intended for use by ‘Oracle database administrators, storage administrators, and architects implementing a backup, recovery, and cloning solution for Oracle databases running on NetApp storage’” (Pet. 30 (quoting Ex. 1004, 4)) and Klivansky, which describes its contents as being useful as “a way of understanding the full landscape of FlexClone benefits, as a refresher of specific FlexClone operations, or as a guided tutorial that filer administrators can try” (Pet. 31 (quoting Ex. 1006, 25)). Given these explicit statements, we are persuaded that a person of ordinary skill would look to combine the teachings of Klivansky with the teachings of the other references even if Klivansky, published in 2004 (Ex. 1006), discussed an older version of the cloning technology.” slip op. at 48

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable

    “g. Conclusion In the Decision to Institute, we determined that Petitioner had shown a reasonable likelihood of prevailing on this proposed ground of unpatentability. Inst. Dec. 25–28. We have reviewed both parties’ arguments and supporting evidence, including the disclosure of all four references and the testimony of both Dr. Zadok and Dr. Shenoy. Despite the counter-arguments in Patent Owner’s Response, and the evidence cited therein, for the reasons discussed above, Petitioner has shown, by a preponderance of the evidence, that each of claims 1, 27, and 28 is unpatentable under 35 U.S.C. § 103 as directed to subject matter obvious over the combination of Edwards, Edwards II, Neto, and Klivansky.” slip op. at 68

  Patent outcomesUS 8,468,174 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips
  Patents in suitUS 8,468,174
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Apr 12, 2016 · IPR2016-00018 · APJ Peter P Chen · IPR · Institution

  The Board denied institution because Arista did not show a reasonable likelihood that claims 1, 2, 6–9, 12, 13, and 17–20 were unpatentable over Chau or Chau and Wils.

  RulingsInstitution decision

  • PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)Institution denied meritsInstitution denied

    “review of claims 1, 2, 6–9, 12, 13, and 17–20 of U.S. Patent No. 8,051,211 B2 (Ex. 1001, “the ’211 patent”). Paper 2 (“Pet.”). Patent Owner, Cisco Systems, Inc., filed a Preliminary Response. Paper 7 (“Prelim. Resp.”). Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any 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); see 37 C.F.R. § 42.108. Upon consideration of the Petition and the Preliminary Response, we are not persuaded Petitioner has demonstrated a reasonable likelihood that it would prevail in establishing the unpatentability of claims 1, 2, 6–9, 12, 13, and 17–20 of the ’211 patent. Accordingly, we do not institute an inter partes review.” slip op. at 2

  • BurdenNot shown unpatentable

    “Petitioner’s only apparent contention for Chau’s disclosure that the first and second LANs are both usable for simultaneous transmission “subsequent to” the aggregation of LANs, is that “the simultaneous transmission occurs as a result of the grouping of the first LAN (channel C2) and second LAN (channel C1).” Pet. 19–20, citing Ex. 1014 ¶ 54. The Lin declaration is similarly worded, and like the Petition, is silent as to whether Chau’s alleged simultaneous transmission occurs “subsequent to,” i.e., after the aggregation of LANs. Petitioner’s argument of simultaneous transmission occurring “as a result of” alleged aggregation of LANs is unavailing, because “subsequent to” means, “after,” not “as a result of.” In fact, in the related ’975 IPR, we expressly rejected the Patent Owner’s proposed construction of “as a result of” for “subsequent to.” See Section II.A. Neither the Petition nor the Lin declaration (Ex. 1014) cite any evidence of simultaneous transmission occurring “after” aggregation of LANs in Chau. Accordingly, we are not persuaded that Petitioner’s showing demonstrates a reasonable likelihood that it would prevail as to claim 1 being anticipated by Chau.” slip op. at 11

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “In addition, as we determined in the ’975 IPR, for purposes of this decision, we determine that the broadest reasonable construction of “subsequent to” is its ordinary and customary meaning, namely, “after.” See Case IPR2015-00975, slip op. at 7–8 (PTAB Oct. 6, 2015) (declining to adopt Patent Owner’s proposed construction of “as a result of” for “subsequent to”).” slip op. at 7

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Not shown unpatentableNot shown unpatentable

    “Petitioner’s only apparent contention for Chau’s disclosure that the first and second LANs are both usable for simultaneous transmission “subsequent to” the aggregation of LANs, is that “the simultaneous transmission occurs as a result of the grouping of the first LAN (channel C2) and second LAN (channel C1).” Pet. 19–20, citing Ex. 1014 ¶ 54. The Lin declaration is similarly worded, and like the Petition, is silent as to whether Chau’s alleged simultaneous transmission occurs “subsequent to,” i.e., after the aggregation of LANs. Petitioner’s argument of simultaneous transmission occurring “as a result of” alleged aggregation of LANs is unavailing, because “subsequent to” means, “after,” not “as a result of.” In fact, in the related ’975 IPR, we expressly rejected the Patent Owner’s proposed construction of “as a result of” for “subsequent to.” See Section II.A. Neither the Petition nor the Lin declaration (Ex. 1014) cite any evidence of simultaneous transmission occurring “after” aggregation of LANs in Chau. Accordingly, we are not persuaded that Petitioner’s showing demonstrates a reasonable likelihood that it would prevail as to claim 1 being anticipated by Chau.” slip op. at 11

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,051,211
• Sega Of America, Inc. / Ubisoft, Inc. et al. v. Uniloc USA, Inc. And Uniloc Luxembourg S.A.All claims unpatentable
  PTAB · Mar 10, 2016 · IPR2014-01453 · APJ Donna M Praiss · IPR · Final written decision

  Claims 1–20 are unpatentable: claims 1–11 and 17–20 as anticipated by Schull; claims 10–11 also as obvious over Schull; claims 12–14 as anticipated by Logan or obvious over Haines and Manduley; claims 15–16 as obvious …

  RulingsFinal written decision

  • Skill levelOther

    “between the subject matter sought to be patented 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 said 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) objective evidence of nonobviousness. Graham v. John Deere Co., 383 U.S. 1, 17–18 (1966). An invention “composed of several elements is not proved obvious merely by demonstrating that each of its elements was, independently, known in the prior art.” KSR, 550 U.S. at 418. Moreover, a determination of unpatentability on the ground of obviousness must include “articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006). The obviousness analysis “should be made explicit” and it “can be important to identify a reason that would have prompted a person of ordinary skill in the relevant field to combine the elements in the way the claimed new invention does.” KSR, 550 U.S. at 418.” slip op. at 24

  • Expert testimonyPetitioner expert creditedPatent owner expert discountedDecided for petitioner

    “In addition, we do not find credible Dr. DiEuliis’s testimony that the text in Figure 2B, which states “registration no. generated from user details added to serial no. is encrypted and re-arranged,” describes the addition of two numbers (registration no. and serial no.). There is no previous step in the flowchart depicted in Figure 2B that describes the step of generating the registration number to indicate that the registration number is an input, rather than an output. Ex. 1025, Fig. 2B; see Ex. 1026, Fig. 2. Further, as explained next, the “user details” encompass text, which further explains why the flowchart is not discussing the addition of numbers.” slip op. at 17

  • Disclosure Requirements (§112) › Written description (Ariad)Not reached

    “Regarding Petitioner’s assertion that certain claim terms lack definiteness or written description support, because those issues are neither appropriate for an inter partes review proceeding nor briefed by the parties, we do not address them in this decision. See 35 U.S.C. § 311(b). For purposes of this decision and for the reasons expressed by the District Court, we adopt and apply the constructions provided in the table above. See Ex. 1008, 53–54, 58–61.” slip op. at 12

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableUnpatentable

    “We are persuaded by Petitioner’s argument that Schull discloses a summation algorithm for generating its Passwordable ID. As explained by Petitioner, Schull’s algorithm combines three ID numbers: Program ID, Feature ID, and Target ID, which Petitioner refers to as X, Y, and Z in its explanation. Pet. 21. The X number has “N” digits, the Y number has “M” digits, and the Z number has “T” digits. Id. The algorithm combines the numbers X, Y, and Z “(e.g., by concatenating them to produce a number” slip op. at 28

  Patent outcomesUS 5,490,216 unpatentable
  § 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 5,490,216

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.