- PTAB · Aug 11, 2025 · IPR2025-00560 · APJ Barry L Grossman · IPR · Institution
The Board instituted IPR on claims 1–29 and every asserted ground, finding a reasonable likelihood that claim 1 is unpatentable over Chang and Fang.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“partes review may not be instituted “unless . . . 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). The Board determines whether to institute a trial on behalf of the Director. 37 C.F.R. § 42.4(a).” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner asserts that a person of ordinary skill in the art would have had “bachelor’s degree in mechanical engineering or a similar field and at least two years of experience designing human breast pump equipment. More education could substitute for experience and vice versa.” Pet. 8 (citing Ex. 1003 ¶¶ 15–18). Mr. Bauer’s Declaration testimony states he considered some of the factors listed above. Ex. 1003 ¶ 17. Mr. Bauer testifies that based on his background and experience, in his opinion, the level of ordinary skill is as stated by Petitioner. Id. at 18. For purposes of this Decision, based on the prior art, the sophistication of the disclosed technology in the ’381 patent, and Mr. Bauer’s undisputed testimony, we adopt Petitioner’s definition of the level of ordinary skill.13” slip op. at 12
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“We do not perceive the need to construe any claim limitation. Claims must be construed “only to the extent necessary to resolve the controversy.” AstraZeneca AB v. Mylan Pharms. Inc., 19 F.4th 1325, 1345 (Fed. Cir. 2021) (quoting Vivid Techs., Inc. v. American Science & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999); see also Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (“Because binding. We wish to have the record developed before rendering any binding determination, finding, or conclusion. 14 The citation to Ex. 1005, 2290 appears to be an error. We do not find the cited claim construction at this location. we need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy,’ we need not construe the claim preambles here where the construction is not ‘material to the [obviousness] dispute.’” (citations omitted)).” slip op. at 13
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“Petitioner also asserts that “[m]ultiple reasons would have prompted a POSITA to implement a diaphragm pump in Chang’s breast pump device in accordance with Fang’s suggestions.” Id. at 21–24. Based on the record before us, we agree that Fang discloses a diaphragm, as recited in clause 1[a][1]. We also agree, based on the record before us, that a person of ordinary skill would have had multiple reasons to use Fang’s diaphragm pump in Chang’s device with a reasonable expectation of success.” slip op. at 21
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,813,381 - Fox Factory, Inc. v. Sram, LLCAll claims unpatentablePTAB · Aug 4, 2025 · IPR2024-00492 · APJ Hyun J Jung · IPR · Final written decision
Claims 1–3, 7, 8, and 10–12 are unpatentable over Yi, JP’279, and Nagai; the Board did not reach the Fox-based grounds.
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Based on the full record, we find that Patent Owner’s proposed level of ordinary skill in the art is consistent with the ’207 patent and the asserted prior art. PO Resp. 17 (citing Ex. 2016 ¶ 48). Our analysis below, however, would not change if we applied Petitioner’s proposed level of ordinary skill in the art, because it specifies experience in design work related to bicycle suspension technology, instead of the more general design of vehicle components or like technology.” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Petitioner’s declarant has a Ph.D. in Mechanical Engineering with “over 30 years of experience in teaching and directing research related to mechanical engineering and precision machine design.” Ex. 1003 ¶ 4. Based on the full record, we find that his experience “related to mechanical engineering and precision machine design” sufficiently meets or exceeds “experience in design of vehicle components or like technology,” as proposed by Patent Owner (PO Resp. 17). Petitioner’s declarant would, thus, be a person of ordinary skill in the art under either party’s proposed level of ordinary skill in the art. Therefore, we see no reason to give less weight to the opinions of Petitioner’s declarant. See also Tr. 39:21–40:22 (confirming that the argument is about how much weight to give to the testimony).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededOther
“Petitioner states that “[n]o terms need construction to resolve the controversy in this forum.” Pet. 8 (citing Ex. 1003 ¶ 32). “Patent Owner agrees that the ’207 Patent’s claim terms require no special claim construction.” PO Resp. 16. Based on the full record, we determine that express claim interpretation is not necessary to resolve the parties’ dispute. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms that . . . are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11
- Obviousness (§103) › Analogous artAnalogous artDecided for petitioner
“d) Petitioner’s Asserted Reason for Combining Petitioner argues that Yi, JP’279, and Nagai are in the same technical field. Pet. 70 (citing Ex. 1006, code (57), 1:7–8; Ex. 1007, 1; Ex. 1008, 1:10–13). We agree, and find, that Yi, JP’279, and Nagai are in the same field of endeavor. Ex. 1006, code (57), 1:7–8; Ex. 1007, 1; Ex. 1008, 1:10– 13. Patent Owner does not dispute that the references are analogous art. See PO Resp.” slip op. at 22
Patent outcomesUS 7,147,207 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 7,147,207 - Fox Factory, Inc. v. Sram, LLCAll claims unpatentablePTAB · Aug 4, 2025 · IPR2024-00491 · APJ Hyun J Jung · IPR · Final written decision
Claims 1–4, 6, 8, 10, 12, 14–18, 20, 22, 24, 26–29, 31, 33–38, 40, 42, 44, 46–49, 51, 53, and 56–64 are unpatentable as obvious over Denk and Moechnig, with Schroeder for claims 31, 51, …
RulingsFinal written decision- Skill levelSkill level patent owner adoptedDecided for patent owner
“Both parties’ proposals require a Bachelor’s degree or a Master’s degree in Mechanical Engineering but differ on the number of years of experience (“1–2 years of experience” versus “three years’ experience”) and from where the experience comes (“design work related to optimal mechanical and structural design” or “design of mechanical elements and structures” versus “vehicle component design and like technology” or “design of vehicle components or like technology”). Pet. 8; PO Resp. 14. Based on the full record, we find that Patent Owner’s proposed level of ordinary skill in the art is consistent with the ’993 patent and the asserted prior art. PO Resp. 17 (citing Ex. 2016 ¶ 48). Our analysis below, however, would not change if we applied Petitioner’s proposed level of ordinary skill in the art, because it specifies experience in “optimal mechanical and structural design,” which would be a part of the “design of vehicle components and like technology.”” slip op. at 9
- Expert testimonyPetitioner expert creditedDecided for petitioner
“Petitioner’s declarant has a Ph.D. in Mechanical Engineering with “over 30 years of experience in teaching and directing research related to mechanical engineering and precision machine design.” Ex. 1003 ¶ 4. Based on the full record, we find that his experience “related to mechanical engineering and precision machine design” sufficiently meets or exceeds “experience in design of vehicle components or like technology,” as proposed by Patent Owner (PO Resp. 14). Petitioner’s declarant would, thus, be a person of ordinary skill in the art under either party’s proposed level of ordinary skill in the art. Therefore, we see no reason to give less weight to the opinions of Petitioner’s declarant. See also Tr. 39:21–40:22 (confirming that the argument is about how much weight to give to the testimony).” slip op. at 10
- Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction needed
“Petitioner states that “[n]o terms need construction to resolve the controversy in this forum.” Pet. 9 (citing Ex. 1003 ¶ 30). We did not need to interpret expressly any claim term for institution. Inst. Dec. 14. “Patent Owner agrees that the ’993 Patent’s claim terms require no special claim construction for purposes of denying this Petition.” PO Resp. 13. Petitioner states that “a vertical plane of travel of the bicycle” and “a thickness of the wall at any point in the lower section of the body varying as a function of the cross-sectional angle of the point relative to the plane of travel” have been construed in related litigation. Pet. Reply 2–5 (citing Ex. 1001, 1:8–14, Fig. 1; Ex. 1024 ¶¶ 18, 20, 22, 24, 52–53; Ex. 1025, 8, 10; Ex. 2021 ¶ 43). Petitioner, however, contends that “the Board need not expressly construe these terms.” Id. at 2. Based on the full record, we determine that express claim interpretation is not necessary to determine whether Petitioner shows a reasonable likelihood of prevailing. Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms that . . . are in controversy, and only to the extent necessary to resolve the controversy.’”) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 11
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“(c) Petitioner Shows a Motivation to Combine Because Petitioner cites a portion of Denk that states, “for the same overall strength and rigidity, the weight may be reduced, or for the same weight, the strength and rigidity may be significantly increased in the load direction specified by the design,” we find that Denk provides a motivation to use its tubular component in the bicycle of Moechnig. Pet. 13–14; Ex. 1006, col. 2. We also credit Petitioner’s testimonial evidence regarding the motivation to combine because the record supports it. Ex. 1003 ¶ 57; Ex. 1006, cols. 1–2; Ex. 1007, 1:10–14; Ex. 1008 ¶¶ 1, 9, 49; Ex. 1010, 6:22–26. The record shows that lightweight components were desirable. See, e.g., Ex. 1006, col. 1; Ex. 1008 ¶ 1. We also agree with Petitioner that one of ordinary skill in the art would have reduced weight or improved strength relative to Moechnig, because Denk describes reducing weight or increasing strength as “specified by the design,” indicating that it is a matter of ordinary skill in the art to achieve less weight or more strength when applying Denk to Moechnig. Ex. 1006, col. 2. how Denk combined with Moechnig would have reduced weight or increased strength, because Denk itself indicates it would have done so. PO Resp. 24–25; Ex. 1006, col. 2 (“for the same overall strength and rigidity, the weight may be reduced”). We also do not agree with Patent Owner that “Denk provides no indication that it would be more lightweight than a standard steerer tube with equal wall thickness and circular profile,” because Denk provides an indication. PO Resp. 25; Ex. 1006, col. 2. Based on the full record, Petitioner persuades us, and we determine, that one of ordinary skill in the art would have been motivated to combine Denk and Moechnig.” slip op. at 26
Patent outcomesUS 10,328,993 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,328,993 - Yealink (USA) Network Technology Co. Ltd. / Yealink Network Technology Co., Ltd. v. Barco N.V.InstitutedPTAB · Jul 29, 2025 · IPR2025-00491 · APJ Frederick C Laney · IPR · Institution
The Board instituted IPR of claims 1–18 on all asserted grounds after finding a reasonable likelihood that claims 1, 9, and 15 are unpatentable over Ground 1.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device.” slip op. at 26
- Skill levelSkill level petitioner adoptedDecided for petitioner
“B. Level of Ordinary Skill in the Art Petitioners contend that a person having ordinary skill in the art would have had “Master of Science (M.S.) degree in electrical engineering or computer science, and five years of work experience in a related field. Additional educational experience could substitute for some of the work experience.” Pet. 9–10 (citing Ex. 1002 ¶¶ 36–37). Patent Owner does not dispute this position at this time. See generally Prelim. Resp. For purposes of this Decision, we adopt Petitioners’ proposed definition of a person of ordinary skill in the pertinent art, as it is consistent with the ’972 patent and the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 8
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionTerm construed board ownDecided for patent owner
“We do not agree with Patent Owner that “fixed” or “configurable” requires more than what is agreed to by the parties––i.e., the characteristics and operational parameters of the endpoint are either set prior to operation or can be set during operation. We disagree that the ’972 patent defines “fixed or a configurable endpoint” as “a number of descriptive fields of the endpoint.” Rather column 8, lines 5–6, of the ’972 patent states that “[a]n endpoint is defined by a number of descriptive fields,” which speaks more about the mechanism used to establish the characteristics and operational parameters of the endpoint than it does about how “fixed” or “configurable” would be understood by a skilled artisan. And the fact that an endpoint may be defined by descriptive fields does not inform a skilled artisan that “fixed” or “configurable” requires the endpoint to allow the processing device to correctly interpret and utilize the data from the endpoint. Correctly interpreting and utilizing data may be the goal, but that goal is not turned into a requirement of the claims because the recited endpoint is fixed or configurable. Similarly, there is no basis for making that goal a requirement simply because a fixed endpoint is described as providing basic functionality and a configurable endpoint is described as being configurable by the base unit either while pairing or via the processing device. As a result, we find little merit in Patent Owner’s contention that the language “fixed or a configurable” requires a process for setting up the characteristics and operational parameters of an endpoint within a device so that the processing device can correctly interpret and utilize the data of this endpoint. Patent Owner, however, will have an opportunity during trial to further develop this contention.” slip op. at 11
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableInstituted
“Having considered the arguments and evidence presented by both parties at this stage of the proceeding, we are persuaded that there is a reasonable likelihood Petitioners would prevail in showing that Beel discloses or suggests to a skilled artisan a base unit having a transmitter and a first peripheral device having a receiver and at least one fixed or a configurable endpoint, where the at least one fixed or a configurable endpoint is a data source or a data sink which is able to store or emit data, of the functional device exposed or made available on the first peripheral device. Petitioners’ offers evidence, supported by its expert declarant, that the endpoints disclosed in Beel are either fixed, such as a mass storage unit with predefined characteristics, or configurable, such as a virtual audio interface that may change configuration based on driver instructions or use context. Pet. 32–33. As Petitioners point out, the ’972 patent itself acknowledges that Beel’s Figure 11 illustrates a system comprising a combination of vendor-specific and standard endpoints, and further interprets these endpoints to correspond to drivers and host applications used for functionality like screen sharing and audio streaming, which demonstrates a direct conceptual and structural alignment between the ’972 patent and Beel. Id. Furthermore, Petitioner’s evidence demonstrates sufficiently that Beel describes a peripheral device acting as a virtual composite device capable of emulating different functions—such as a USB audio speaker—while rerouting the data stream (e.g., RTP audio stream) over the network. Id. For instance, Petitioners’ evidence demonstrates sufficiently Beel discloses or suggests that audio data can be captured by a virtual sound card interface implemented within the peripheral device, re-encoded, and transmitted to the base unit for playback or synchronization with video content. Id. In addition, Petitioners have demonstrated sufficiently that Beel’s architecture supports the requirement that the endpoint of the functional device—whether it is a camera, microphone, or speaker—is made available through or exposed on the peripheral device. Id. The functional device’s capabilities are effectively rendered accessible to the processing device by way of the peripheral device, which acts as an intermediary. Id. Petitioners’ evidence demonstrates sufficiently that this exposure can occur via logical interfaces, such as USB Audio Class (UAC) virtual drivers, that allow the processing device to recognize and interact with these endpoints using standard protocols. Id. Furthermore, Petitioners show sufficiently Beel discloses that the peripheral device may include software that facilitates communication with and presentation of media content on the processing device, further demonstrating that the endpoints are not only present but also actively used for data transmission. Id. Patent Owner’s arguments, at least at this stage of the proceeding, fail to undermine Petitioners’ showing because they are largely just that–– attorney arguments––without sufficient evidentiary backing and because they lack sufficient clarity regarding how the recited claim language distinguishes Beel’s disclosed system. First, Patent Owner makes several representations that Petitioners misplace its reliance on certain teachings or suggests found in Beel and that Beel does not support the contention Petitioners make, but Petitioners’ positions are backed the testimony of Dr. Almeroth and Patent Owner offers no contradictory evidence for why a skilled artisan would understand Beel differently. And, suffice it to say that, when the declaration of Dr. Almeroth is considered in juxtaposition with the cited evidence from Beel, we have found declarant Dr. Almeroth sufficiently persuasive to demonstrate Petitioner is reasonably likely to prevail on the point. For example, Patent Owner simply argues that “there is no indication in Beel of using any fixed or a configurable endpoint of the functional device exposed or made available on the first peripheral device” (Prelim. Resp. 31), but declarant Dr. Almeroth states that “Beel discloses that a peripheral device can act as a ‘virtual audio device’ using a USB Audio Class (UAC) interface,” which “indicates that endpoints of the functional device are ‘exposed or made available on the first peripheral device’” (Ex. 1002 ¶ 130 (emphasis added); see also id. ¶¶ 128–129). Patent Owner’s argument, without any evidentiary support, does little to undermine the opinion testimony from Dr. Almeroth about what Beel’s teachings would indicate to a skilled artisan. Second, although Patent Owner repeatedly states that Beel fails to” slip op. at 26
Claim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 10,684,972 - Dropbox, Inc. v. Motion Offense, LLCAll claims unpatentablePTAB · Jul 1, 2025 · IPR2024-00287 · APJ Norman H Beamer · IPR · Final written decision
Claims 9–12, 14–16, and 22–24 are unpatentable under § 103 over Riepling and Meisels, or Riepling, Manzano, and Meisels; claim 13 was disclaimed.
RulingsFinal written decision- Skill levelSkill level petitioner adoptedDecided for petitioner
“Petitioner’s proposal is consistent with the level of ordinary skill in the art as reflected by the asserted prior art. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); GPAC, 57 F.3d at 1579. We apply Petitioner’s articulation.” slip op. at 20
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“construction of “representation of the at least one file.” Petitioner is correct that a representation of a file is not the file itself, but (in keeping with the ordinary meaning of “representation”) is rather some sign or symbol that stands for the folder. Reply 2. This is confirmed by the explicit example of a representation of a folder in the ʼ906 application, illustrated in the portion of Figure 6B reproduced below (highlighted here for purposes of explanation). This portion of Figure 6B depicts representations of two files: “FamilyHistory.docx” and “XmasLetter-2012.pdf.” The ’906 application specifically states: [A] located data resources dialog UI element 630b . . . includes a presentation space 632b for presenting a user detectable representation of some or all of the data objects identified in the received data object identification response from . . . second node 504. Ex. 2004 ¶ 147 (emphasis added). The entries in the above figure are representations of the files, not the files themselves. The actual files are stored in the file system storage associated with the user’s node, and only retrieved if the user selects the “Access” or “Access All” elements. Id. ¶ 148. Patent Owner misconstrues the claim 22 language, “a first representation of the at least one file, in a location among one or more folders, that is stored at the at least one server” and “a second representation of the at least one file, in a location among one or more folders, that is stored at the first node.” Patent Owner infers from this language that the representation is itself a file that is “in a location among one or more folders” and is stored on a server or at a node. PO Resp. 17. Not so — the representation of a file, such as “FamilyHistory.docx” in the above figure, is not stored at a server or node, but rather is simply displayed on a screen. As the ’906 application states: A representation of a program entity may be stored and/or otherwise maintained in a presentation space. As used in this document, the term “presentation space” refers to a storage region allocated and/or otherwise provided for storing presentation information . . . . A screen of a display, for example, is a presentation space.” slip op. at 22
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundReasonable expectation foundDecided for petitioner
“because (i) Riepling and Meisels are from the same field of endeavor, directed to sharing files over a network; (ii) the combination would have yielded expected, predictable results, using known and routine computer programming principles, to modify Riepling’s system to generate an electronic message that includes a link pointing to an uploaded file; (iii) the combination would have been readily implemented given Meisels’ teachings of inserting, in an electronic message, a link to a shared location where a file is uploaded; and (iv) the combination was suggested because Meisels expressly disclosed a benefit of sending an email message with a link, to avoid multiple copies of a file from existing at multiple locations, and sending links to one file to multiple recipients and managing permissions on an individual recipient basis. Pet. 67–70 (citing Ex. 1107, Fig. 1, ¶¶ 2, 4, 19; Ex. 1108, Fig. 4, ¶¶ 1, 3, 41–45, 56; Mowry Decl. ¶¶ 194–198). In addition, for reasons similar to the motivation basis, Petitioner argues that a person of ordinary skill in the art would have had a reasonable expectation of success in making the combination. Id. at 70–71 (citing Mowry Decl. ¶¶ 199–200). Other than its arguments directed to ’520 claim requirement 9[l], discussed below in Section III.D.4.d), Patent Owner does not further address Petitioner’s arguments regarding the combination of Riepling and Meisels. As discussed in that section, we are persuaded by Petitioner’s expert’s testimony that one of ordinary skill would have applied the document link teachings of Meisels to modify Riepling. Accordingly, we determine that Petitioner has proved by a preponderance of the evidence that one of ordinary skill in the art would have been motivated to combine Riepling and Meisels in the manner argued by Petitioner.” slip op. at 32
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“We agree with Petitioner that set content field 325 of Riepling teaches or suggests claim requirement 9[b]. As Petitioner’s expert explains, the fact that field 325 has an appearance identical to that of fields 321–324 in Figure 3, which fields are specifically stated to be “text field[s],” strongly suggests that field 325 is also a text field. Mowry Decl. ¶ 70; see also Reply 10–11. Patent Owner’s suggestion that field 325 could be a dropdown list or other type of field is contradicted by the fact that it does not show the typical dropdown arrow associated with a dropdown box, or other typical non-textbox appearance such as the checkbox appearance of field 320. Moreover, in the example of Figure 3, the “Set Content” entry is “audio,” which is a file description. Reply 10. The fact that “JPEG” is checked in field 320 is not inconsistent with the “audio” entry in field 325, given that, as Riepling explains, “it may be possible for audio files such as MP3 files to contain non-MP3 data, such as JPEG data embedded within the MP3 files.” Id. at 11 (citing Ex. 1107 ¶ 32; Mowry 2nd Decl. ¶ ¶ 101–104). Also, there is no reason why the Figure 5 response that gives the uploader the ability to provide additional description of the file being uploaded is inconsistent with the ability of the requester first describing what type of file is being requested via field 325 in Figure 3. Id. at 11–12. Accordingly, for the reasons discussed above, we are persuaded that the record supports Petitioner’s arguments regarding claim requirement 9[b].” slip op. at 37
Patent outcomesUS 11,611,520 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,611,520 - Dropbox, Inc. v. Motion Offense, LLCAll claims unpatentablePTAB · Jun 30, 2025 · IPR2024-00286 · APJ Norman H Beamer · IPR · Final written decision
Claims 17–21 are unpatentable under § 103 over Houston and Garcia; the Board did not reach the alternative grounds.
RulingsFinal written decision- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed petitioner constructionDecided for petitioner
“We conclude that there is no basis for Patent Owner’s proposed construction of “representation of the at least one folder.” Petitioner is correct that a representation of a folder is not the folder itself, but (in keeping with the ordinary meaning of “representation”) is rather some sign or symbol that stands for the folder. Reply 2. This is confirmed by the explicit example of a representation of a folder in the ’635 application, illustrated in the portion of Figure 6D reproduced below (highlighted here for purposes of explanation). This portion of Figure 6D depicts representations of several folders, including the highlighted “Music” folder. The ’635 application specifically states: A folder content pane UI element 648d in navigation window UI element 646d is presented including representations of one or more data objects[11] at a location, identified in a path UI element 650d. A pointer UI element 652d illustrates a drag and drop operation of a “Music” folder represented in contents pane UI element 648d, dropped on edit window UI element 602d. Ex. 2004 ¶ 123 (emphasis added). The word “Music” in the above figure is a representation of a folder, not the folder itself. The actual folder is an entity in a file system that stores files (in the case of a “Music” folder, presumably MP3 or WAV files, or the like).” slip op. at 17
- Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation foundDecided for petitioner
“Patent Owner’s arguments are not pertinent to Petitioner’s proffered combination of Houston with Garcia as applied to the remaining challenged claims 17–21. As discussed further below, Petitioner relies on Garcia as supplementing Houston for details regarding the requirements of generating and sending an email with a link to a folder but without a file attachment, and for synchronizing folders and providing interfaces for display of shared folders. Pet. 26–27, 36–39, 57–60. For the challenged claims, Petitioner does not need to rely on the combination to modify Houston’s system such that, when an icon for a shared folder is created in Houston’s interface at an invited user’s client, the client does not store a file in the shared folder — 14 For this argument and others, Patent Owner cites for additional support portions of U.S. Provisional Patent Application No. 61/233,787. PO Resp. 18, 42, 46; Sur-Reply 9–12. This application is designated in Houston as a related application, and incorporated by reference therein. Ex. 1003, code (60), 1:6–10. We denied as untimely Patent Owner’s request to belatedly add this application to the record. Ex. 3002; Paper 39. Even accepting Patent Owner’s representations of the relied-on disclosures in that application, those disclosures are cumulative to Houston’s criticisms of systems that store documents remotely, and are irrelevant for the same reasons as discussed herein with respect to those Houston disclosures. that aspect of the Houston/Garcia combination is only relevant to claims 1–8, which have been disclaimed. Id. at 40–41; Ex. 2045.15 Thus, Patent Owner’s argument that Houston teaches away from combining with Garcia to delay storing a file when a folder is shared is not applicable to Petitioner’s challenges of claim 17–21, in light of our conclusion set forth above in Section III.C rejecting Patent Owner’s proposed construction of claim 17. The fact that the Houston system ensures the availability of synchronized local copies of files at each user’s local system and criticizes systems that store documents remotely, such as in Garcia, is irrelevant to those claims. On this record, there is nothing about that particular difference in the approaches of Houston and Garcia that would support a finding that one of ordinary skill in the art would have been discouraged from adopting Houston to take advantage of the teachings in Garcia regarding use of email and folder interfaces. In sum, Patent Owner focuses on a specific irrelevant detail of Houston regarding local storage of files, whereas Petitioner relies on other features of the combination of Houston and Garcia. In re Merck & Co., 800 F.2d 1091, 1097 (Fed. Cir. 1986); In re Keller, 642 F.2d 413, 425 (CCPA 1981). “The test for obviousness is not whether the features of a secondary reference may be bodily incorporated into the structure of the primary” slip op. at 41
- Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner
“To give substantial weight to objective indicia of nonobviousness such as commercial success, a proponent must establish a nexus between the evidence and the merits of the claimed invention. ClassCo, Inc. v. Apple, Inc., 838 F.3d 1214, 1220 (Fed. Cir. 2016). Nexus is a legally and factually sufficient connection between the objective evidence and the claimed invention, such that the objective evidence should be considered in determining nonobviousness. Demaco Corp. v. F. Von Langsdorff Licensing Ltd., 851 F.2d 1387, 1392 (Fed. Cir. 1988). “[T]here is no nexus unless the evidence presented is ‘reasonably commensurate with the scope of the claims.’” ClassCo, 838 F.3d at 1220 (quoting Rambus Inc. v. Rea, 731 F.3d 1248, 1257 (Fed. Cir. 2013)). A patentee is entitled to a presumption of nexus “when the patentee shows that the asserted objective evidence is tied to a specific product and that product ‘embodies the claimed features, and is coextensive with them.’” Fox Factory, Inc. v. SRAM, LLC, 944 F.3d 1366, 1373 (Fed. Cir. 2019) (quoting Polaris Indus., Inc. v. Arctic Cat, Inc., 882 F.3d 1056, 1072 (Fed. Cir. 2018)). “[T]he patentee retains the burden of proving the degree to which evidence of secondary considerations tied to a product is attributable to a particular claimed invention.” Fox Factory, 944 F.3d at 1378. The Federal Circuit has held that “if the marketed product embodies the claimed features, and is coextensive with them, then a nexus is presumed and the burden shifts to the party asserting obviousness to present evidence to rebut the presumed nexus.” Brown & Williamson Tobacco Corp. v. Philip Morris Inc., 229 F.3d 1120, 1130 (Fed. Cir. 2000). “A finding that a presumption of nexus is inappropriate does not end the inquiry into secondary considerations”; rather, “the patent owner is still afforded an opportunity to prove nexus by showing that the evidence of secondary considerations is the ‘direct result of the unique characteristics of the claimed invention.’” Fox Factory, 994 F.3d at 1373–74 (quoting In re Huang, 100 F.3d 125, 140 (Fed. Cir. 1996)). “Ultimately, the fact finder must weigh the [objective indicia] evidence presented in the context of whether the claimed invention as a whole would have been obvious to a skilled artisan.” See Lectrosonics, Inc. v. Zaxcom, Inc., IPR2018-01129, Paper 33, 33 (PTAB Jan. 24, 2020) (precedential) (citing WBIP, LLC v. Kohler Co., 829 F.3d 1317, 1331–32 (Fed. Cir. 2016)).” slip op. at 23
- Obviousness (§103) › Graham factors (scope of art, differences, level of skill)UnpatentableUnpatentable
“However, as Petitioner argues above, Houston discloses that a client can provide an email to the server to invite others to share a folder, and Houston explains that “attaching files [to emails is] cumbersome for many computer users.” Pet. 25–26 (citing Ex. 1003, Fig. 4, 1:41–42, 3:40–43, 7:50–51). From this, Petitioner argues that it would have been obvious for the email invitation to notify how to access the folder, rather than sending the folder contents itself. Id. Petitioner further argues that the claim 17[d] requirement would have been obvious over the combination of Houston and Garcia given the disclosure in Garcia of sharing a folder by sending an email with a link to the folder, instead of an attachment. Id. at 27, 57 (citing Ex. 1004, Figs. 9, 11–12, 10:32–34, 10:38–40, 11:39–43, cl. 3). We are persuaded that the record supports Petitioner’s arguments regarding this claim requirement. Both Houston alone, and the combination of Houston and Garcia, teach or suggest sending an email with a link to a folder to be shared, rather than the folder contents. Only if the recipient clicks on the link are the contents of the folder shared. Ex. 1004, 11:29–31. The act of clicking on the link in the email after the email is received is the required “initiation of the communication” that must occur separately from the email itself, as required by claim 17[d]: “causing generation of at least one email [that] does not include a file attachment, for permitting avoidance of at least one file from being communicated to and stored at the second node until an initiation of the communication of the at least one file by a user of the second node is detected and the communication commences via at least one server that stores the at least one file” (emphasis added). It does not matter if Houston or Garcia automatically downloads local copies of files when a recipient clicks on the email link, because that is a separate step following the step of claim 17[d].” slip op. at 46
Patent outcomesUS 11,611,520 unpatentableClaim construction§ 103 obviousnesscites Phillips · KSR · GrahamPatents in suitUS 11,611,520 - PTAB · Jun 23, 2025 · IPR2025-00260 · APJ Thomas L Giannetti · IPR · Institution
The Board instituted inter partes review of claims 1 and 11–14 on all asserted grounds and consolidated the proceeding with IPR2024-01357.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“In our Institution Decision in IPR2024-01357, we analyzed claim 1 of the ’678 patent in light of Basin-2007 and Basin-2005. ’1357 IPR, Paper 17, 23–28. We concluded, after reviewing the arguments presented there, that “Petitioner has demonstrated a reasonable likelihood of proving that the combined teachings of Basin-2005 and Basin-2007 render claim 1 unpatentable as obvious.” Id. at 28. In this proceeding, Petitioner has presented a challenge to claim 1 based on those same references that it represents is a “verbatim” copy of its previous challenge to claim 1 in the ’1357 IPR. Pet. 1–2, 28–35. Petitioner supports its challenge with expert testimony. Ex. 1002 ¶¶ 107–125.7 Patent Owner has not submitted a response on the merits of this challenge. For the purposes of this Decision, and for the reasons given in the Petition, we adopt the analysis in our Institution Decision in the ’1357 IPR (at pp. 23–28), where we determined that Petitioner has demonstrated a reasonable likelihood of prevailing on its obviousness challenge to claim 1 based on Basin-2005 and Basin-2007. Turning now to Petitioner’s challenge to claim 11, Petitioner relies on Basin-2007 and Stokes for the particle size limitations added to claim 1 by that dependent claim. Pet. 35–39. Thus, Petitioner asserts that “Basin-2007 discloses a light scattering material with an average TiO2 particle size that is ‘sub-micron’ (less than 1000 nm).” Id. at 37 (citing Ex. 1005 ¶ 5). 7 Exhibit 1002 appears to be a duplicate copy of Dr. Doolittle’s declaration from the ’1357 IPR. Petitioner concludes, “Basin-2007 renders obvious claim 11 by literally disclosing the selection of average particle sizes that preferentially scatter blue light.” Id. Further, “to the extent that the claim language ‘an average particle size that is selected such that [it preferentially scatters blue light]’ requires an average particle size selected for that reason (rather than an average particle size that leads to that outcome), this claim element is rendered obvious by Stokes.” Id. at 38 (citing Doolittle Decl. ¶ 45) (alterations in original). Petitioner explains that “Stokes explicitly discloses the selection of an average particle size ‘such that the particles preferentially scatter blue . . . LED light as compared to yellow . . . light from the luminescent material.’” Id. at 38 (citing Ex. 1008, 7:1–4) (alterations in original). Petitioner provides a motivation for combining Stokes with Basin- 2007 with a reasonable expectation of success. Pet. 38–39. Petitioner explains that “[t]o the extent that claim 11 is understood to also claim the basis for selecting a particular average particle size, a [person of ordinary skill] would have had reason to use such a basis for selecting average particle size as taught by Stokes.” Id. at 38 (citing Doolittle Decl. ¶¶ 46–48). Further, “a [person of ordinary skill] would have been motivated to apply this principle to Basin-2007, because it would increase the conversion of blue light to yellow light and improve the uniformity of the light source.” Id. at 39 (citing Doolittle Decl. ¶ 48). At this stage, Patent Owner does not provide an opposition to Petitioner’s evidence or arguments on the merits. For the reasons given by Petitioner, including those summarized above, we determine that Petitioner” slip op. at 6
- Director reviewOther
“On June 12, 2025, the Acting Director issued a decision denying the request and referring the Petition to the Board “to handle the case in the normal course, including by issuing a decision on institution addressing the merits and other nondiscretionary considerations, as appropriate.” Paper 16, 3. The Acting Director further instructed the Board, “[a]bsent extraordinary circumstances, the Board shall consolidate this proceeding with IPR2024-01357.” Id.” slip op. at 5
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“As noted supra, the Acting Director of the USPTO has instructed the Board, “[a]bsent extraordinary circumstances, the Board shall consolidate this proceeding with IPR2024-01357.” Paper 16, 3. Due to the similarity of the parties, counsel, subject matter, and asserted prior art between IPR2024- 01357 and this proceeding, and in view of the Acting Director’s guidance, we exercise our discretion to consolidate this proceeding with IPR2024- 01357. See 37 C.F.R. § 42.122(a).” slip op. at 8
NonePatents in suitUS 8,604,678 - PTAB · Jun 23, 2025 · PGR2025-00016 · APJ Eric C Jeschke · PGR · Institution
The Board instituted PGR on claims 4–14 on all asserted grounds, finding it more likely than not that at least one challenged claim is unpatentable.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 324 (2024); 37 C.F.R. § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Post-grant review may not be instituted “unless . . . the information presented in the petition . . . , if such information is not rebutted, would demonstrate that it is more likely than not that at least 1 of the claims challenged in the petition is unpatentable.” 35 U.S.C. § 324. Upon consideration of the evidence and arguments in the record, for the reasons below, we determine that the information presented shows that it is more likely than not that Petitioner would prevail with respect to at least one of the challenged claims. We thus institute a post-grant review on all challenged claims on all asserted grounds. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 362–63, 369–70 (2018); 37 C.F.R. § 42.208(a) (“When instituting post-grant review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner and “notes that it substantially tracks” Patent Owner’s definition. Prelim. Resp. 19–20; see also id. at 20 n.7 (defining one of ordinary skill in the art as having “at least a Bachelor of Science degree in Mechanical or Agricultural Engineering and two years of experience in the design of machines, or have had equivalent knowledge and experience”). Petitioner’s proposed definition of the level of ordinary skill in the art appears consistent with the record at this stage of the proceeding, including the prior art. See GPAC Inc., 57 F.3d at 1579. Patent Owner’s proposal is the same, except for use of the term “machines” instead of “vehicles.” Furthermore, Patent Owner does not argue at this stage of the proceeding that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would understand either the challenged patent or the prior art. For purposes of this Decision, we adopt the definition of the level of ordinary skill in the art proposed by Petitioner.” slip op. at 10
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther
“In contrast, we view the record at this stage as supporting an understanding of the “frame” in “mainframe” as a supporting structure. Patent Owner provides a dictionary defining “frame” as a “rigid supporting structure” (Prelim. Resp. 22 (citing Ex. 2009 at 3)), and Petitioner proposes “a supporting structure” based on that definition (see Pet. Reply CC Br. 3 (mistakenly citing Ex. 2007 rather than Ex. 2009)). Further, this dictionary definition does not contradict the “mainframe” described in the Specification or any other intrinsic evidence. See, e.g., Ex. 1001, Fig. 4, 2:44–45 (“FIG. 4 is a perspective view of a mainframe of a compact tool carrier.”); see also Phillips, 415 F.3d at 1322–23 (stating that judges may “rely on dictionary definitions when construing claim terms, so long as the dictionary definition does not contradict any definition found in or ascertained by a reading of the patent documents”).” slip op. at 15
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“Patent Owner’s argument does not identify a deficiency in the Petition, however, because we did not adopt any part of Patent Owner’s proposed construction of “mainframe,” including the phrase “the body,” which serves as the starting point of Patent Owner’s argument here. See § II.C.3. Instead, we preliminarily construe “mainframe” under its plain and ordinary meaning as a primary supporting structure. Id. Limitation 4.2 makes clear that the “mainframe” supports the “loader.” The current record supports that at least the structures shaded in green and blue in the annotated version of Figure 1 of KR996 immediately above are the primary supporting structure for the loader (i.e., a “mainframe”)—i.e., when in operation, those structures provide the primary “weight-bearing frame supporting the loader unit 40” in KR996. Pet. 24 (“KR996’s mainframe includes the frame components of KR996 vehicle for supporting the attached loader unit 40 by providing structural or weight-bearing support when the vehicle is in operation.” (citing Velinsky Decl. ¶¶ 65–67)); Pet. 26–27 (stating that the “mainframe” are the “portions [that] are part of a frame or body making up the KR996 vehicle when in operation providing structural and weight-bearing support for the loader unit 40, in addition to support for other features such as the control station and drive mechanism” (citing Velinsky Decl. ¶ 67)); see, e.g., Ex. 1005, Figs. 7–9 (showing the vehicle of KR996 in operation). The testimony of Dr. Velinsky supports these positions, explaining that one of ordinary skill in the art would have understood the green and blue structures above as part of a “mainframe.” See Velinsky Decl. ¶¶ 66– 67, cited at Pet. 24–27. At this stage of the proceeding, Patent Owner has not presented declaration testimony—but rather only attorney argument— supporting that one of ordinary skill in the art would have identified fixture 41 in KR996 as something other than a “mainframe.” See Elbit Sys. of Am., LLC v. Thales Visionix, Inc., 881 F.3d 1354, 1359 (Fed. Cir. 2018) (“‘[A]ttorney argument is not evidence’ and cannot rebut other admitted evidence.” (quoting Icon Health & Fitness, Inc. v. Strava, Inc., 849 F.3d 1034, 1043 (Fed. Cir. 2017))). On the current record, we determine that Petitioner has made a sufficient showing that KR996 discloses or suggests the mainframe limitations.” slip op. at 29
Claim construction§ 102 anticipation§ 103 obviousnesscites PhillipsPatents in suitUS 12,098,063 - PTAB · Jun 23, 2025 · IPR2025-00381 · APJ Eric C Jeschke · IPR · Institution
The Board instituted IPR on claims 1–10 on all asserted grounds, finding a reasonable likelihood that Kubota would prevail on at least one challenged claim.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“review. See 35 U.S.C. § 314 (2024); 37 C.F.R. § 42.4(a) (2024) (“The Board institutes the trial on behalf of the Director.”). Inter partes review may not be instituted “unless . . . the information presented in the petition . . . 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. Upon consideration of the evidence and arguments in the record, for the reasons below, we determine that the information presented shows a reasonable likelihood that Petitioner would prevail with respect to at least one of the challenged claims. We thus institute inter partes review on all challenged claims on all asserted grounds. See SAS Inst. Inc. v. Iancu, 584 U.S. 357, 362–63, 369–70 (2018); 37 C.F.R. § 42.108(a) (“When instituting inter partes review, the Board will authorize the review to proceed on all of the challenged claims and on all grounds of unpatentability asserted for each claim.”).” slip op. at 2
- Skill levelSkill level petitioner adoptedDecided for petitioner
“Patent Owner states that it “does not dispute” the definition of one of ordinary skill in the art proposed by Petitioner and “notes that it substantially tracks” Patent Owner’s definition. Prelim. Resp. 19–20; see also id. at 20 n.7 (defining one of ordinary skill in the art as having “at least a Bachelor of Science degree in Mechanical or Agricultural Engineering and two years of experience in the design of machines, or have had equivalent knowledge and experience”). Petitioner’s proposed definition of the level of ordinary skill in the art appears consistent with the record at this stage of the proceeding, including the prior art. See GPAC Inc., 57 F.3d at 1579. Patent Owner’s proposal is the same, except for use of the term “machines” instead of “vehicles.” Furthermore, Patent Owner does not argue at this stage of the proceeding that Petitioner’s proposal for the level of ordinary skill leads to an improper understanding of how a skilled artisan would understand either the challenged patent or the prior art. For purposes of this Decision, we adopt the definition of the level of ordinary skill in the art proposed by Petitioner.” slip op. at 9
- Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for petitioner
“But that the Specification may indicate that a “loader support” and a “mainframe” may have some similar functionality does not make the terms interchangeable from a claim construction perspective. See Bd. of Regents of the Univ. of Texas Sys. v. BENQ Am. Corp., 533 F.3d 1362, 1371 (Fed. Cir. 2008) (“Different claim terms are presumed to have different meanings.”) (citing CAE Screenplates Inc. v. Heinrich Fiedler GmbH & Co., 224 F.3d 1308, 1317 (Fed. Cir. 2000) (“In the absence of any evidence to the contrary, we must presume that the use of these different terms in the claims connotes different meanings.”)). For these reasons, we are not persuaded by Patent Owner’s view that intrinsic and extrinsic evidence regarding a different term—“mainframe”—supports a similar proposed construction for “loader support.” See, e.g., Prelim. Resp. 22–27 (discussing intrinsic and extrinsic evidence relating to “mainframe” and then proposing a definition of “loader support”). Instead, we apply the plain and ordinary meaning of “loader support,” which aligns with the view of the Iowa District Court. See Ex. 1020 at 5 (the Iowa District Court stating that “loader support” “will be given [its] plain and ordinary meaning”); 37 C.F.R. § 42.100(b) (“Any prior claim construction determination concerning a term of the claim in a civil action . . . that is timely made of record in the inter partes review proceeding will be considered.”). We need not construe explicitly any claim terms because doing so would not change the outcome of the analysis below. See Realtime Data, LLC v. Iancu, 912 F.3d 1368, 1375 (Fed. Cir. 2019) (“The Board is required to construe ‘only those terms . . . that are in controversy, and only to the extent necessary to resolve the controversy.’” (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)).” slip op. at 12
- Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)Instituted
“We have reviewed Petitioner’s contentions with respect to the claim, and for the reasons below, we determine that the Petition shows a reasonable likelihood that Petitioner would prevail in demonstrating that claim 1 is both anticipated and would have been obvious based on KR996.” slip op. at 15
Claim construction§ 102 anticipation§ 103 obviousnesscites PhillipsPatents in suitUS 11,465,891 - Microsoft Corporation v. Eyesmatch Ltd.InstitutedPTAB · Jun 11, 2025 · IPR2025-00297 · APJ Thomas L Giannetti · IPR · Institution
The Board instituted review of claims 1–18 on all petition grounds and granted Microsoft’s motion to join IPR2024-00856.
RulingsInstitution decision- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“III. DECISION ON INSTITUTION Petitioner represents that the challenges to the claims of the’109 patent in the Petition are “intentionally identical . . . in all substantive aspects” to the challenges in the ’856 IPR. See Joinder Motion 2; compare ’856 IPR, Paper 1, 2–4, with Pet. 2–3. Petitioner further represents that this proceeding and the ’856 IPR “rely upon the same analytical framework (e.g., same expert declarant and prior art) in addressing the Challenged Claims.” Joinder Motion 2. Additionally, Patent Owner does not present an opposition to the Petition on the merits and does not oppose joinder. See, e.g., Notice, 1. In view of the foregoing, for the reasons given above and in the ’856 Institution Decision, we determine that Petitioner has demonstrated a reasonable likelihood of prevailing on its challenge to at least one claim of the ’109 patent. We therefore institute inter partes review of all challenges in the Petition. See 35 U.S.C. § 314(a).” slip op. at 5
- PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted
“Joinder is a matter within the Board’s discretion based on the particular circumstances of each proceeding. For the reasons given above, we are persuaded that Petitioner has demonstrated that permitting Petitioner to join the ’856 IPR would avoid duplication and promote the efficient resolution of both proceedings and is therefore in the interests of justice.” slip op. at 6
- BurdenInstituted
“III. DECISION ON INSTITUTION Petitioner represents that the challenges to the claims of the’109 patent in the Petition are “intentionally identical . . . in all substantive aspects” to the challenges in the ’856 IPR. See Joinder Motion 2; compare ’856 IPR, Paper 1, 2–4, with Pet. 2–3. Petitioner further represents that this proceeding and the ’856 IPR “rely upon the same analytical framework (e.g., same expert declarant and prior art) in addressing the Challenged Claims.” Joinder Motion 2. Additionally, Patent Owner does not present an opposition to the Petition on the merits and does not oppose joinder. See, e.g., Notice, 1. In view of the foregoing, for the reasons given above and in the ’856 Institution Decision, we determine that Petitioner has demonstrated a reasonable likelihood of prevailing on its challenge to at least one claim of the ’109 patent. We therefore institute inter partes review of all challenges in the Petition. See 35 U.S.C. § 314(a).” slip op. at 5
NonePatents in suitUS 8,982,109
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.