• 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
• Smart Modular Technologies Inc. v. Netlist, Inc.No claims unpatentable
  PTAB · Mar 9, 2016 · IPR2014-01372 · APJ Linda M Gaudette · IPR · Final written decision

  The Board held claims 1–4, 14–20, 27, and 29 not unpatentable because Averbuj did not disclose a control module configured to generate the claimed address signals.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Based on a comparison of Dr. Bagherzadeh’s and Dr. Sechen’s declarations (Exs. 1009, 2019), we find Dr. Bagherzadeh has a broader range of educational and work experience, and, therefore, accord greater weight to his opinion as to the level of ordinary skill in the art. Dr. Bagherzadeh’s opinion is consistent with our finding as to the level of ordinary skill in the art in our Final Written Decision in IPR-970. We, therefore, adopt our finding in IPR-970 as to the level of ordinary skill in the art: [A] person of ordinary skill in the art at the time of the ’434 patent would have a Bachelor’s degree in electrical engineering, computer engineering, or in a related field and at least one year of work experience relating to memory systems, and would be familiar with the design of memory devices, memory modules, and BIST. IPR-970 FWD, 10–11 (noting that our finding was “based on our review of the ’434 patent and the types of problems and solutions described in the ’434 patent and cited prior art”).” slip op. at 10

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We are not persuaded by Dr. Bagherzadeh’s testimony because it is devoid of specific facts and analysis as to what led him to conclude that a person of ordinary skill in the art would interpret the claim term “generate” in the manner Petitioner proposes. See id. Dr. Bagherzadeh does not explain how the IEEE definition supports an interpretation of generate as “cause or initiate transmission,” terms that do not appear in the IEEE definition. See id. Nor does Dr. Bagherzadeh identify other extrinsic evidence which he believes to be consistent with an interpretation of “generate” as meaning “cause or initiate transmission.” See id. Likewise, Dr. Bagherzadeh has not explained why he believes the ’434 patent “describe[s] generating as initiating or transmitting” (Ex. 1009 ¶ 28), as these terms do not appear in the cited portions of the ’434 patent. See Ex. 1008, 6:3–5, 10:67–11:2, 6:14–17. Accordingly, Dr. Bagherzadeh’s testimony does not persuade us to accept Petitioner’s interpretation of “generate” as meaning “cause.”” slip op. at 15

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

    “supports a finding that a customary meaning of “generate” to one of ordinary skill in the art is “cause.”1 We, therefore, determine the broadest reasonable 1 Petitioner relies on Webster’s II, for a definition of “cause.” See Reply 4, 6–8 (citing Ex. 1032, 3). Having determined the broadest reasonable interpretation of “generate” does not encompass “cause,” we do not find this evidence relevant to our claim construction analysis. construction of “generate” is “produce” for the reasons stated above and in our Final Written Decision in IPR-970. We adopt and incorporate by reference our analysis and construction of the term “generate” in our Final Written Decision in IPR-970 (IPR-970 FWD, 24–33).” slip op. at 16

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

    “Moreover, the evidence in this proceeding fails to support a finding that Averbuj’s BIST controller 4 is configured to generate address signals for testing the memory devices in the manner claimed. In Averbuj, the algorithms (i.e., CMD_DATA containing OP CODE such as SET ADDRESS (see Ex. 1011, 4:4–12, 5:19–21, Table 1)) communicated to sequencers 8 are either received by user interface 22 via external input (id. at 5:41–43) or generated by another component (i.e., a component that is not part of BIST controller 4 circuitry) and stored in algorithm memory 20 (see Ex. 2012, 30:23–24, 41:1–4, 54:21–22, 55:6–25, 55:20–56:9 (wherein Dr. Bagherzadeh testifies that OP CODE residing in the algorithm memory of BIST controller 4 are generated by hand or by a tool, e.g., a compiler, and that “99 percent of the designs or chips do not have a compiler on-board”)). Multiplexer 24 selects one of the algorithms (i.e., CMD_DATA) and BIST controller 4 provides to sequencers 8 the same CMD_DATA (e.g., address signals) without transformation or modification. See Ex. 1011, 4:4–12, 5:16–21; Ex. 2012, 54:8–13 (“Averbuj Figure 2, without consideration of any other disclosure in Averbuj, illustrates that a multiplexer selects an input from the algorithm memory and the output [] reflect[s] what’s in the input, based on the selection.”). Based on our interpretation of the terms “configured to” and “generate,” as discussed above, the claim recitation “a control module configured to generate address . . . signals for testing the memory devices” (claims 1, 20, and 29) does not read on Averbuj’s BIST controller 4, because the SET ADDRESS signal output by BIST controller 4 is produced by a component external to BIST controller 4, and merely selected by multiplexer 24 and provided to sequencers 8 without transformation or modification by BIST controller 4. In sum, after considering the parties’ arguments and evidence, we determine Petitioner has not shown, by a preponderance of the evidence, that Averbuj discloses “a control module configured to generate address . . . signals for testing the memory devices” as recited in independent claims 1, 20, and 29. Petitioner does not correct this deficiency in its challenges as to dependent claims 2–4, 14–19, and 27. See Pet. 32–39; 35 U.S.C. § 112, ¶ 4 (“A claim in dependent form shall be construed to incorporate by reference all the limitations of the claim to which it refers.”). Because Petitioner has not identified in Averbuj a teaching of each and every limitation recited in claims 1–4, 14–20, 27, and 29, Petitioner has not met its burden to show these claims are unpatentable under 35 U.S.C. § 102(b) as anticipated by Averbuj.” slip op. at 30

  Patent outcomesUS 8,001,434 not shown unpatentable
  Claim construction§ 102 anticipation
  Patents in suitUS 8,001,434
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 19, 2015 · IPR2015-00976 · APJ Bryan F Moore · IPR · Institution

  The Board denied institution on all challenged claims because the patent did not disclose sufficient structure for certain means-plus-function limitations and Hendel did not show claim 63’s required access-control matching.

  RulingsInstitution decision

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

    “Petitioner has not shown that Hendel’s filtering decision is determined based on “matching one or more characteristics of said packet with one or more access control specifiers.” Petitioner simply states that the packet is “filtered.” Petitioner’s Declarant relies on the following text from Hendel: “In a preferred embodiment, the merge logic 66 directs the input port 50i to take one of the following actions on a packet: filter the packet; forward the packet at layer 2; forward the packet at layer 2; forward the packet as a layer 3 flow; process the packet as a layer 3 route; and forward the packet as multicast router.”) Ex. 1003 ¶ 132 (citing Ex. 1007, 13:4–8.) This citation does not specify, however, that a characteristic of the packet was matched to anything in order to make the filtering decision, only that the decision was the result of “merge logic.” Petitioner’s Declarant also relies on the following text from Hendel: “After the forwarding logic 52 has determined what to do with the packet, it passes that information to the input port 50i. If the input port 50i does not filter the packet, then it [takes actions to forward the packet].” Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25.) However, this statement does not even say that forwarding logic tells input port 50i to filter the packet, and certainly does not explain how forwarding logic 52 would make a filtering decision. Finally, Petitioner’s declarant relies on Hendel’s discussion of sending the packet to a firewall for further processing if no match occurs (Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25)), but the claim does not recite what happens if there is not a match. The specification confirms that a successful match is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by “determining all of the successful matches”). Neither Petitioner, nor Petitioner’s Declarant, has tied the matching in Hendel to a decision whether or not to forward a packet. For the reasons stated above, we determine Petitioner has not shown sufficiently that Hendel discloses all of the limitations of independent claim 63. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that claim 63 is anticipated by Hendel.” slip op. at 14

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Other

    “The corresponding structure need not be explicitly identified but must disclose to a person of ordinary skill in the art what structure is identified in the specification. See Atmel Corp. v. Info. Storage Devices, Inc., 198 F.3d 1374, 1380 (Fed. Cir. 1999). It is unclear from the Specification whether the CPU, shown in Figure 2 as part of access control element 120, is the “higher-level processor” which is described at Ex. 1001, 5:21–25, or some other processor running IOS described at Ex. 1001, 1:33–37. It is also unclear which part of the access control element 120 is composed of “circuits adapted to particular process steps and data structures” as described at 3:36–39. Here, the patent is at best unclear whether the claimed function is implemented in software executed on a general purpose CPU or in hardware as a collection of circuits. See Blackboard, Inc. v. Desire2Learn Inc., 574 F.3d 1371, 1385 (Fed. Cir. 2009) (“That ordinarily skilled artisans could carry out the recited function in a variety of ways is precisely why claims written in ‘means-plus-function’ form must disclose the particular structure that is used to perform the recited function.”). We also find that it is equally unclear whether the following means- plus-function limitations in claim 46, which appear to involve access control element 120, are implemented in hardware or in software structure (or some combination of both): means for matching matchable information, said matchable information being responsive to said packet label, with said set of access control patterns in parallel; means for making a routing decision in response to said access result; means for permitting or denying access for said packet; and means for receiving a packet label responsible to a packet, said packet label being sufficient to perform access control processing for said packet. Because the Specification of the challenged patent lacks sufficient disclosure of structure under 35 U.S.C. § 112, sixth paragraph, the scope of independent claim 46, and claims 47–52, 54, 56, and 59–62 that depend therefrom, cannot be determined without speculation and, consequently, the differences between the claimed invention and the prior art cannot be ascertained. Thus, we decline to institute an inter partes review as to any ground challenging claims 46–52, 54, 56, and 59–62.” slip op. at 11

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

    “Petitioner has not shown that Hendel’s filtering decision is determined based on “matching one or more characteristics of said packet with one or more access control specifiers.” Petitioner simply states that the packet is “filtered.” Petitioner’s Declarant relies on the following text from Hendel: “In a preferred embodiment, the merge logic 66 directs the input port 50i to take one of the following actions on a packet: filter the packet; forward the packet at layer 2; forward the packet at layer 2; forward the packet as a layer 3 flow; process the packet as a layer 3 route; and forward the packet as multicast router.”) Ex. 1003 ¶ 132 (citing Ex. 1007, 13:4–8.) This citation does not specify, however, that a characteristic of the packet was matched to anything in order to make the filtering decision, only that the decision was the result of “merge logic.” Petitioner’s Declarant also relies on the following text from Hendel: “After the forwarding logic 52 has determined what to do with the packet, it passes that information to the input port 50i. If the input port 50i does not filter the packet, then it [takes actions to forward the packet].” Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25.) However, this statement does not even say that forwarding logic tells input port 50i to filter the packet, and certainly does not explain how forwarding logic 52 would make a filtering decision. Finally, Petitioner’s declarant relies on Hendel’s discussion of sending the packet to a firewall for further processing if no match occurs (Ex. 1003 ¶ 132 (citing Ex. 1007, 9:21–25)), but the claim does not recite what happens if there is not a match. The specification confirms that a successful match is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by “determining all of the successful matches”). Neither Petitioner, nor Petitioner’s Declarant, has tied the matching in Hendel to a decision whether or not to forward a packet. For the reasons stated above, we determine Petitioner has not shown sufficiently that Hendel discloses all of the limitations of independent claim 63. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that claim 63 is anticipated by Hendel.” slip op. at 14

  Claim construction§ 102 anticipation
  Patents in suitUS 7,023,853
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 6, 2015 · IPR2015-00974 · APJ Matthew R Clements · IPR · Institution

  The Board denied institution on all challenged claims because Petitioner did not show a reasonable likelihood of proving unpatentability under the asserted anticipation and obviousness grounds.

  RulingsInstitution decision

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

    “Systems, Inc. (“Patent Owner”) filed a Preliminary Response. Paper 6 (“Prelim. Resp.”). We have jurisdiction under 35 U.S.C. § 314, which provides that an inter partes review may be authorized only if “the information presented in the petition . . . and any [preliminary] response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a); 37 C.F.R. § 42.4(a). Upon consideration of the Petition and the Preliminary Response, we determine that the information presented by Petitioner does not establish that there is a reasonable likelihood that Petitioner would prevail in showing the unpatentability of any of the challenged claims 1–10, 12, 13, 15–28, 30, 31, 33–43, 45–49, 51–64, 66, 67, and 69–72 of the ’668 patent. Accordingly, pursuant to 35 U.S.C. § 314, we do not institute an inter partes review of claims 1–10, 12, 13, 15–28, 30, 31, 33–43, 45–49, 51–64, 66, 67, and 69–72 of the ’668 patent.” slip op. at 2

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther

    “interpreted according to their “broadest reasonable construction in light of the specification of the patent” in which they appear. 37 C.F.R. § 42.100(b); see also In re Cuozzo Speed Techs., LLC, 793 F.3d 1268, 1278–79 (Fed. Cir. 2015). Applying that standard, we interpret the claim terms according to their ordinary and customary meaning in the context of the patent’s written description. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed. Cir. 2007). Petitioner proposes constructions for ten terms. Pet. 9–14. Patent Owner disputes some of those constructions and proposes an additional term for construction. Prelim. Resp. 9–19. For purposes of this Decision, we determine that we need not expressly construe any of the terms for which the parties have proposed constructions.” slip op. at 6

  • Skill levelOther

    “expressly disclose a limitation, may nevertheless anticipate if a person of ordinary skill in the art would understand the prior art to disclose the limitation and could combine the prior art description with his own knowledge to make the claimed invention. See Helifix Ltd. v. Blok-Lok, Ltd., 208 F.3d 1339, 1347 (Fed. Cir. 2000). After reviewing the arguments of the parties and the testimony of Dr. Lin, however, we are not persuaded that a person of ordinary skill in the art1 would understand the cited sentence in Amara as necessarily disclosing that the network interface ports of Amara’s internetworking device are configurable by its internal applications. Dr. Lin relies on pages 132 to 134 of Habraken, which is a textbook that describes, inter alia, configuring the interfaces of a Cisco router through a Setup dialog. While this passage describes configuring a port, it is not clear what aspect of the Cisco router is providing the Setup dialog. Nothing, for example, attributes the Setup dialog to “control plane processes” or “internal applications” or the like of the Cisco router. Even assuming that the Setup dialog is provided by an “internal application” of the Cisco router, 1 Petitioner asserts, and Patent Owner does not dispute, that a person of ordinary skill as of the critical date would have had a Master of Science Degree in an academic area emphasizing computer networking or, alternatively, a Bachelor Degree in an academic area emphasizing the design of electrical, computer, or software engineering and several years of experience in computer network engineering and the design of computer networks. Pet. 7. nothing in Habraken supports the determination that the network interface ports of all routers, such as the 3Com router described in Amara, are configurable by “internal applications” of that router. At best, Habraken establishes that a person of ordinary skill in the art at the time would have known that Cisco routers include a Setup dialog for configuring router interfaces. This is not sufficient, however, to persuade us that a person of ordinary skill in the art would have read Amara as necessarily disclosing that the network interface ports of the “device” are configurable by the internal applications.” slip op. at 11

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

    “We agree with Patent Owner that Amara’s express disclosure is not sufficient. Amara’s disclosure that internal applications control or configure the device only “typically” suggests that they do not necessarily serve that purpose and, therefore, that another component of device 100 may serve that purpose. Moreover, Amara’s disclosure that internal applications control or configure the “device” is not sufficiently specific as to whether the interface ports are an aspect of the device being controlled or configured by the internal applications. Our reviewing court has held that a prior art reference that does not expressly disclose a limitation, may nevertheless anticipate if a person of ordinary skill in the art would understand the prior art to disclose the limitation and could combine the prior art description with his own knowledge to make the claimed invention. See Helifix Ltd. v. Blok-Lok, Ltd., 208 F.3d 1339, 1347 (Fed. Cir. 2000). After reviewing the arguments of the parties and the testimony of Dr. Lin, however, we are not persuaded that a person of ordinary skill in the art1 would understand the cited sentence in Amara as necessarily disclosing that the network interface ports of Amara’s internetworking device are configurable by its internal applications. Dr. Lin relies on pages 132 to 134 of Habraken, which is a textbook that describes, inter alia, configuring the interfaces of a Cisco router through a Setup dialog. While this passage describes configuring a port, it is not clear what aspect of the Cisco router is providing the Setup dialog. Nothing, for example, attributes the Setup dialog to “control plane processes” or “internal applications” or the like of the Cisco router. Even assuming that the Setup dialog is provided by an “internal application” of the Cisco router, 1 Petitioner asserts, and Patent Owner does not dispute, that a person of ordinary skill as of the critical date would have had a Master of Science Degree in an academic area emphasizing computer networking or, alternatively, a Bachelor Degree in an academic area emphasizing the design of electrical, computer, or software engineering and several years of experience in computer network engineering and the design of computer networks. Pet. 7.” slip op. at 10

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 7,224,668
• Yamaha Corporation Of America v. Black Hills Media, LLCAll claims unpatentable
  PTAB · Mar 18, 2015 · IPR2013-00593 · APJ Stacey G White · IPR · Final written decision

  Claims 9, 10, and 14 are unpatentable as anticipated by Berman and Wolff; claim 13 is unpatentable as obvious over Berman.

  RulingsFinal written decision

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

    “from the Specification of the ’952 Patent, which defined “playlist 1528 . . . [as] a list of audio files and associated URL’s of where the audio files were retrieved from.” Ex. 1001, 21:6365. Petitioner persuasively argues that the Specification and the claims reflect that the playlist and associated URLs are separate items. Reply 5–6. For example, the Specification discusses a server having “a playlist for the Device 1110” and also “maintain[ing] a list of URL’s from which the device 1110 received audio files listed in the playlists.” Ex. 1001, 16:67–17:6; see also Reply 5–6 (citing Ex. 1001, 21:63–65, 21:45–46, 21:49, 21:51–52, Fig. 15) (pointing out examples in the Specification that discuss the playlist and URLs as separate items); Ex. 2012 ¶¶ 66–71, 75–76, 81–84 (explanation by Patent Owner’s declarant as to why a list of URLs is not a playlist). Thus, we are persuaded that URLs are not part of the playlist. Therefore, the broadest reasonable construction of playlist is “a list of audio files.”” slip op. at 8

  • Skill levelOther

    “a bachelor’s degree in computer science or electrical engineering, and at least one year of practical experience with networked multimedia.” Ex. 1002 ¶ 8. Patent Owner’s proposal is similar, requiring a person with “a bachelor’s degree in computer science or electrical engineering or its equivalent and 1–2 years of practical experience with media file sharing.” PO Resp. 9–10 (citing Ex. 2012 ¶¶ 26–29). We find this dispute between the parties to be of little value. An express definition of the level of ordinary skill is not required in all situations, as 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) (“the 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). Neither party has provided a sufficient explanation as to how their specific proposal regarding the level of ordinary skill (and in particular the importance of the inclusion or exclusion of “at least”) changes the analysis in this case. We find the level of ordinary skill in the art to be reflected in the cited references, and we determine that no express statement of the level of ordinary skill in the art is required.” slip op. at 11

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

    “Pet. 15–18. Specifically, Petitioner argues that Berman discloses a playback unit that receives a song list from the DUL server. Pet. 17 (citing Ex. 1012, Fig. 3 (step 308)); see also id. at 10:23–28 (describing song list packet sent to playback unit with a user ID “to confirm that the updated song list information was sent to and received by the correct playback unit”). Petitioner also asserts that the songs identified in the song list are stored on audio material server 104, and, thus, the songs are not stored on the playback unit. Id. at 18 (citing Ex. 1012, 4:5152). The playback unit receives URLs for songs on the song list from the audio material server. Id. (citing Ex. 1012, Fig. 3 (step 314), 7:22–54). Finally, Petitioner asserts that the playback unit obtains songs from the audio material server. Id. (citing Ex. 1012, Fig. 4 (step 412), 8:31–34). We agree with Petitioner’s arguments regarding the disclosures of Berman.” slip op. at 14

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

    “rendered obvious by the teachings of Berman. Pet. 34–35. Claim 13 depends from 9 and adds further limitations regarding the useage of web sites, which is not disclosed expressly by Berman. Petitioner asserts that it would have been obvious to one of ordinary skill in the art to use a web site as a remote source in place of Berman’s servers. Pet. 20–21. Dr. Bove supports Petitioner’s argument by testifying that “[i]t would have been well known to one of ordinary skill in the art in 2000 that music files could be provided by a Web server. As one example, the MP3.com music server site launched in 1997.” Ex. 1002 ¶ 19. We credit Dr. Bove’s testimony and find Petitioner’s arguments to be persuasive. Patent Owner does not proffer any additional arguments directed to the patentability of claim 13. PO Resp. 40. We determine that Petitioner has demonstrated by a preponderance of the evidence that dependent claim 13 would have been obvious over Berman.” slip op. at 16

  Patent outcomesUS 8,045,952 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,045,952
• Yamaha Corporation Of America v. Black Hills Media, LLCAll claims unpatentable
  PTAB · Mar 18, 2015 · IPR2013-00597 · APJ Peter P Chen · IPR · Final written decision

  Claims 2, 6, and 10–12 are unpatentable: Bi anticipates claims 2, 6, and 10–12; Gladwin anticipates claims 2, 6, 11, and 12; Berman renders claims 2, 6, 11, and 12 obvious.

  RulingsFinal written decision

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

    “[a] playlist is a list of a user’s favorite selections.” Ex. 1001, 1:33–34. Patent Owner quotes from the specification of the ’099 Patent: Playlists also facilitate the playing of a plurality of selections in a particular order. That is, the playlist may be compiled in an order in which the playing of selections therefrom is desired. The selections may then be automatically played sequentially from the playlist. Typically, selections may also be played randomly from a playlist. PO Resp. 10; Ex. 1001, 1:45–52 (emphasis added).2 As noted by Petitioner, this passage reflects that a playlist may have a particular order of selections (see Pet. Reply 6), but also expressly discloses that selections may be played randomly from a playlist. slip op. at 8

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

    “wireless handheld remote control which is associated with and separate from the media player device,” arguing that the term requires “a handheld remote control that can operate as an independent device relative to the media player that it control.” PO Resp. 14–16 (emphasis and grammatical error in original); see also Tr. 70:1–14 (“independent and separate would be synonyms.”). Petitioner argues that Patent Owner’s proposal is narrow and excludes “a standard remote control for a device,” Pet. Reply 8–9. We agree, as in addition to the Petitioner’s contentions, we note the terms “operate” and “independent” do not appear in the ’099 patent. 9 We decline to adopt Patent Owner’s proposed construction over the ordinary and customary meaning of the term.” slip op. at 9

  • Skill levelOther

    “year of practical experience with networked multimedia.” Ex. 1002 ¶ 8. Patent Owner’s proposal is similar, requiring “a person with a bachelor’s degree in computer science or electrical engineering and one year of practical experience with networked media.” PO Resp. 7. The parties dispute Petitioner’s use of the qualifying phrase “at least” in describing the level of education and work experience. While we disagree with Patent Owner’s argument that “at least” is “improper because it is open-ended” (PO Resp. 7–8),3 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) (“the 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). Here, neither party has provided a sufficient explanation as to how their specific proposal regarding the level of ordinary skill (and in particular the importance of the inclusion or exclusion of “at least”) affects the analysis in this case. Therefore, we find the level of ordinary skill in the art to” slip op. at 11

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend, grantedGranted

    “B. Motion to Amend In its Motion to Amend, Patent Owner moves to cancel independent claim 1 and dependent claim 9. Paper 25. Petitioner’s Reply does not oppose the motion. Pet. Reply 1. We grant the motion to amend, and proceed to analyze the remaining five claims.” slip op. at 10

  Patent outcomesUS 8,230,099 unpatentable
  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 8,230,099

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.