PTAB
Advanced fields
1 decision · 545msnewest first
  • PTAB · May 16, 2022 · IPR2022-00181 · APJ Juliet Mitchell Dirba · IPR · Institution

    The Board denied institution because Petitioner did not show a reasonable likelihood of proving claims 1, 19, 23, 24, or 28 unpatentable on any asserted ground.

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

      “An inter partes review may not be instituted unless “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). Having reviewed the parties’ papers and the evidence of record, we determine that Petitioner has not shown a reasonable likelihood it will prevail in establishing the unpatentability of any of the challenged claims. Accordingly, we do not institute an inter partes review.” slip op. at 2

    • Disclosure Requirements (§112) › Written description (Ariad)Entitled to earlier dateDecided for patent owner

      “Petitioner contends that the PCT application does not include “anything that could reasonably be characterized” as disclosing the metadata limitation. Pet. 12–13 (citing Ex. 1025 ¶ 81). Petitioner, however, does not elaborate or address any aspect of the PCT application’s disclosure. See id. Patent Owner argues that the PCT application discloses the metadata limitation. Prelim. Resp. 6–12. According to Patent Owner, the PCT application describes a mobile device receiving and displaying “descriptive information” about a track (such as the song title, artist, and duration) without downloading the track itself, and this “descriptive information” discloses the “track meta-data” recited in the claim. Id. at 8–11 (citing Ex. 1008, 4:27–5:9, 11:6–16, 13:14–21, 51:7–13, 91:7–10, 105:16–18, 116:1–10, 133:2–3, 134:10–15, 149:21–23, 149:25–150:3, 150:12–26, 152:1–9, 153, 156). In support, Patent Owner notes that the PCT application describes “[m]etadata” as “[i]ndividual items of data or collections of data, of,” among other things, mobile content such as “full music downloads.” Id. at 7 (citing Ex. 1008, 13:14–21) (emphasis omitted). Patent Owner further explains by asserting that “[t]he fact that the track metadata is provided as a search result, but not the music file itself, demonstrates” disclosure of the metadata limitation. Id. at 9. In addition, Patent Owner submits that the PCT application discloses “sharing” track information because users can send their playlists and recommendations to other users. Id. at 11–12 (citing Ex. 1008, 5:21–22, 7:2–4, 59:10–14, 61:15–28, 65:1–17, 66:18–9, 67:7–9, 101:17–102:13, 130:8–17, Figs. 84, 97, 106). On this record, we are persuaded that the PCT application discloses the metadata limitation, which (for purposes of this Decision) requires a software application that uses “track meta-data” that (1) exists separately from the music track, (2) exists separately in any way from other forms of metadata, and/or (3) is stored in a separate database. See supra § II.B (claim construction). In particular, Patent Owner persuasively shows that the PCT application discloses a mobile device application that uses “track meta-data” (e.g., attributes of music tracks, such as the song’s title, artist, and duration) stored on the mobile device while the corresponding track and its metadata remain separately stored on a remote server.” slip op. at 13

    • Novelty / Anticipation (§102) › Priority / effective filing date / continuation supportPriority date awardedDecided for patent owner

      “2. Law on Written Description Support “It is elementary patent law that a patent application is entitled to the benefit of the filing date of an earlier filed application only if the disclosure of the earlier application provides support for the claims of the later application, as required by 35 U.S.C. § 112.” PowerOasis, Inc. v. T-Mobile USA, Inc., 522 F.3d 1299, 1306 (Fed. Cir. 2008) (quoting In re Chu, 66 F.3d 292, 297 (Fed. Cir. 1995)). “To satisfy the written description requirement [in § 112,] the disclosure of the prior application must ‘convey with reasonable clarity to those skilled in the art that, as of the filing date sought, [the inventor] was in possession of the invention.’” Id. (second alteration in original) (quoting Vas-Cath Inc. v. Mahurkar, 935 F.2d 1555, 1563–64 (Fed. Cir. 1991)). “[T]he hallmark of written description is disclosure.” Ariad Pharm., Inc. v. Eli Lilly & Co., 598 F.3d 1336, 1351 (Fed. Cir. 2010) (en banc). The sufficiency of written description support is based on “an objective inquiry into the four corners of the specification from the perspective of a person of ordinary skill in the art.” Id. “Based on that inquiry, the specification must describe an invention understandable to that skilled artisan and show that the inventor actually invented the invention claimed.” Id. “The level of detail required to satisfy the written description requirement” necessarily “varies predictability of the relevant technology.” Id. The invention need not be described in haec verba, but a disclosure that merely renders obvious the claims does not provide adequate written description support. Id. at 1352.” slip op. at 12

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

      “connect these dots. For example, it is unclear whether Petitioner proposes a combination of Abrams’s web browser and Khedouri’s music application, or whether it instead proposes that one be replaced with the other. See id. at 53–54. Petitioner also does not address whether a person of ordinary skill in the art would have had a reasonable expectation of success in combining a web browser and a music application. See id. Rather, Petitioner simply refers to combining “Khedouri’s music sharing functions” with “Abrams’ social networking functions” (id. at 54), which does not address the requirement that “a software application” meet these limitations. Moreover, Petitioner does not sufficiently explain why a person of ordinary skill in the art would have combined the functionality of Abrams and Khedouri. See KSR, 550 U.S. at 418 (obviousness requires analysis of “whether there was an apparent reason to combine the known elements in the fashion claimed by the patent at issue”); Belden Inc. v. Berk-Tek LLC, 805 F.3d 1064, 1073 (Fed. Cir. 2015) (“[O]bviousness concerns whether a skilled artisan not only could have made but would have been motivated to make the combinations or modifications of prior art to arrive at the claimed invention.”). Liberally interpreting the relevant portion of the Petition, Petitioner contends that a motivation to combine is established because: (1) the references themselves provide the motivation to combine, (2) the proposed combination was desirable and predictable, (3) an ordinary artisan would have been motivated to add music to Abrams, and/or (4) an ordinary artisan would have been motivated to add Abrams’s social networking functions to Khedouri. See Pet. 53–54; see also supra § II.E.1 (reproducing relevant portion of Petition with corresponding reference numbers). We are not persuaded. themselves provide the requisite motivation. See Pet. 53. Abrams is directed to “connecting users in an online computer system based on their relationships within social networks.” Ex. 1009 ¶ 1; see also id. ¶ 36 (“What is needed is a system that allows individuals to replicate the process of developing personal relationships through social networks, using a computer system and database.”). Khedouri, on the other hand, is directed to “selecting, requesting, downloading, and playing audio” files on a user’s portable audio player device from a content delivery service. Ex. 1011, Abst., ¶ 3. Petitioner identifies (and we perceive) no disclosure in either reference that suggests their combination. See Pet. 53–54. Petitioner incorrectly implies that Khedouri “expands on [Abrams’s] ‘music theme.’” Id. at 53. Abrams states that a user can identify the user’s interests as well as favorite music, books, tv, and movies (Ex. 1009 ¶ 91, Fig. 2), and each of these are stored as a text field in Abrams’s database (id. ¶¶ 89, 91, Fig. 2). This is a passing reference to music, not a music theme. Petitioner also contends that both Abrams and Khedouri teach most limitations of the claim (Pet. 53 (citing Ex. 1025, 120–123)), but even if that were true, it does not explain why a person of ordinary skill in the art would have combined them. Second, Petitioner’s assertions that the proposed combination would have been “desirable” and “predictable” are conclusory and entitled to little weight. See Pet. 54. Petitioner relies on Dr. Shamos’s testimony in support, but it similarly fails to provide analysis or evidence to support his conclusions. See Ex. 1025 ¶ 170. Accordingly, we assign little weight to that testimony. See 37 C.F.R. § 42.65(a) (“Expert testimony that does not disclose the underlying facts or data on which the opinion is based is entitled to little or no weight.”); see also TQ Delta, 942 F.3d at 1358. a desirable feature” and the combination would provide users “the ability to not only identify and publicize information about their favorite music on their profiles (and learn about others’ favorite music from others’ profiles) but to actually search for that music and be able to listen to it.” Pet. 54 (citing Ex. 1025 ¶ 170). Although this identifies vague benefits of a combination (i.e., sharing information and facilitating access to music), it fails to explain why an ordinary artisan would have been motivated to incorporate these benefits in Abrams’s social network. Petitioner also provides no evidence that an ordinary artisan would have had reasonable expectation of success in making this proposed combination. See id. at 53– 54. Given the specific facts and circumstances of this case, we are concerned that this rationale suffers from improper hindsight bias. See KSR, 550 U.S. at 421 (“A factfinder should be aware, of course, of the distortion caused by hindsight bias and must be cautious of arguments reliant upon ex post reasoning.”); Polaris Indus., Inc. v. Arctic Cat, Inc., 882 F.3d 1056, 1068 (Fed. Cir. 2018) (“We have observed that the prejudice of hindsight bias often overlooks that the genius of invention is often a combination of known elements which in hindsight seems preordained.” (internal quotation marks omitted)).” slip op. at 24

    § 102 anticipation§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
    Patents in suitUS 9,294,430

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.