• Cisco Systems, Inc. v. Umbra Technologies Ltd.No claims unpatentable
  PTAB · Aug 28, 2025 · IPR2024-00270 · APJ Gregg I Anderson · IPR · Final written decision

  Claims 15–20 were not shown unpatentable because Hankins did not teach limitation 15.3; claims 1–14 were disclaimed.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner does not dispute Petitioner’s proposal of the level of ordinary skill in the art. PO Resp. 6. Petitioner’s proposal is supported by the Reddy Declaration and is consistent with the ’595 patent and the asserted prior art. Accordingly, we apply Petitioner’s articulation in our obviousness evaluation below.” slip op. at 14

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

    “B. Claim Construction Beyond plain and ordinary meaning, Petitioner does not propose any term for claim construction. Pet. 13. Patent Owner does not argue any claim construction issue. See generally PO Resp. The argument and evidence provided by the parties regarding limitation 15.3 is dispositive. See Section II.E. below. Our analysis of limitation 15.3 does not turn on any claim construction question. Id. Accordingly, we do not need to construe any claim term. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (noting that “we need only construe 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))). We apply the plain and ordinary meaning of all claim terms, as would have been understood by a person of ordinary skill in the art, in the context of the ’595 patent.” slip op. at 14

  • Adverse judgmentAdverse judgmentOther

    “D. Claims 1–14 as Obvious Over Kommula As already noted, Patent Owner has disclaimed claims 1–14. Ex. 3001. We do not analyze claims 1–14 as the challenge is mooted by the filing of the Statutory Disclaimer.” slip op. at 15

  • BurdenNot shown unpatentable

    “350 receiving a request for a listing of “services” from a gateway device and provisioning one or more tunnel servers has not been shown to teach generating “a list of available servers.” There is no persuasive evidence to support Petitioner’s assertion. Petitioner relies on unsupported argument because, at best, Hankins discloses gateway devices 311 and 321, each of which is located in different logical broadcast domains, requesting services from one another. Ex. 1005, 12:9–16. This particular disclosure, however, does not appear to implicate the functionality of Hankins’s controller 350, much less result in controller 350 generating a list of available tunnel servers that would allow gateway devices 311 and 312 to exchange a listing of “services” therebetween. Petitioner’s reliance on Hankins’s controller 350 provisioning additional tunnel servers both to improve performance and without human intervention fares no better. Ex. 1005, 25:45–55. There is no indication in Hankins that this provisioning performed by controller 350 is done in response to receiving a request for a list of available tunnel servers from either gateway device 311 or 312.” slip op. at 20

  Patent outcomesUS 11,108,595 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 11,108,595
• Interactive Communications International, Inc. v. Blackhawk Network Inc.No claims unpatentable
  PTAB · Feb 6, 2025 · IPR2023-01235 · APJ Bart A Gerstenblith · IPR · Final written decision

  Claims 1–6 were not shown unpatentable under either obviousness ground because Szrek did not disclose a pre-printed lottery ticket without lottery numbers associated at customer purchase.

  RulingsFinal written decision

  • PTAB / AIA Trials › Real party in interest / privityRpi dispute resolved for petitionerDecided for petitioner

    “real party in interest. Prelim. Resp. 1–2, 32–34. In the Institution Decision, we stated: To the extent Patent Owner seeks to pursue its argument that Linq3 is a real party of interest to Petitioner, even though no time bar under 35 U.S.C. § 315(b) has been asserted, Patent Owner may raise the issue of real party in interest again in its Patent Owner Response and the parties may brief and argue the issue during trial. Inst. Dec. 11. In its Patent Owner Response, Patent Owner did not raise the issue of challenging Petitioner’s identified real party in interest. See generally PO Resp. Thus, we need not address this issue further because we find that Patent Owner has waived any challenge to Petitioner’s identification of the real parties in interest in this proceeding. See Paper 12 (Scheduling Order), 9 (“Patent Owner is cautioned that any arguments not raised in the response may be deemed waived.”).” slip op. at 5

  • Skill levelSkill level petitioner adoptedDecided for patent owner

    “B. Level of Ordinary Skill in the Art Petitioner proposes that the level of ordinary skill in the art is an artisan with a working knowledge of POS activation systems and lottery systems that was gained through a mixture of training and work experience in the relevant field such as (i) having a Bachelor’s degree in computer science, computer communications, electrical engineering, or equivalent degree, coupled with at least three years of work experience; (ii) having a Master’s degree in computer science, computer communications, or electrical engineering, but having less work experience; or (iii) having no formal degree, but having experience in the relevant field of at least six years of work experience. Pet. 2–3 (citing Ex. 1003 ¶ 13).5 Patent Owner states that, “[f]or the purpose of this proceeding, Patent Owner adopts the Petition’s proposed definition of the level of ordinary skill in the art.” PO Resp. 19. 5 Petitioner proposes the same level of ordinary skill in the art that the Board adopted in PGR2020-00084. Pet. 2–3 (citing Ex. 1008, 11). We find that the parties’ agreed-upon level of ordinary skill in the art is consistent with the level of ordinary skill in the art reflected by the ’135 patent and the prior art of record. See Inst. Dec. 14; see Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978). Therefore, we adopt the parties’ agreed-upon level of ordinary skill in the art, as articulated above, in our consideration of the issues presently before us.” slip op. at 12

  • Claim Construction › Intrinsic evidence (Phillips canons) › Prosecution history disclaimer / disavowalTerm construed patent owner constructionDisclaimer foundDecided for patent owner

    “Following the block quote from Yacenda, the applicant then stated, “[b]ased on the foregoing, Yacenda’s system is directly opposite of the instant claims, as the instant claims require a ‘pre-printed lottery ticket’ which has no lottery numbers associated with it at the time of customer purchase.’” Ex. 1002, 76. This statement is clear and unmistakable. It (1) specifically states that “the instant claims require” and (2) then states what the claims require—a “‘pre-printed lottery ticket’ which has no lottery numbers associated with it at the time of customer purchase.” We fail to see how the applicant could have been more clear in stating a requirement of the Challenged Claims. And, by doing so, the applicant narrowed the scope of what would otherwise be encompassed in the meaning of “pre-printed lottery ticket” and therefore what would otherwise be encompassed in the scope of the Challenged Claims—a lottery ticket which has lottery numbers associated with it at the time of customer purchase.” slip op. at 27

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We do not find Mr. Hutton’s testimony particularly helpful. First, we have addressed the points raised by his testimony in our discussion above because they are largely the same as the arguments raised in Petitioner’s Reply. Second, we find his testimony entitled to very little weight because he applies an incorrect understanding of the caselaw, which mirrors Petitioner’s incorrect and arguably misleading quotations of the Federal Circuit’s decision in Quest. In particular, in paragraph 5, Mr. Hutton states the following as his understanding of the law as it applies to prosecution disclaimer: “I also understand that in order to disclaim embodiments within the specification, the statements should have some indication that the applicant intended to surrender embodiments from the specification.” Ex. 1038 ¶ 5 (emphasis added). This then leads Mr. Hutton to state: “[t]hus, in my opinion, a [person of ordinary skill in the art] would not view applicant’s statements as a disclaimer, because the applicant never stated that they intended to surrender multiple embodiments described in the specification.” Id. ¶ 13 (emphasis added). As we explained above in responding to a similar argument by Petitioner, the caselaw does not require an applicant to expressly state whether a disclaimer excludes particular embodiments of the subject specification when disclaiming claim scope during prosecution. See Quest, 924 F.3d at 1229. And, as noted above, counsel for Petitioner agreed that such a statement explicitly disclaiming particular embodiments is not required. Tr. 12:18–13:17. Third, although we have considered Mr. Hutton’s testimony, we find it “less significant than the intrinsic record in determining the legally operative meaning of” “pre-printed lottery ticket.” Phillips, 415 F.3d at 1317. In particular, we are cognizant of the Federal Circuit’s guidance that we “should discount any expert testimony that is clearly at odds with the claim construction mandated by . . . the prosecution history.” Id. at 1318 (internal quotation omitted). In this instance, for the reasons explained above, we find that Mr. Hutton’s testimony is clearly at odds with the applicant’s arguments during prosecution and that his testimony is based on a misunderstanding of what is required by the governing caselaw for prosecution history disclaimer.” slip op. at 43

  Patent outcomesUS 9,865,135 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,865,135
• Apple Inc. v. Smart Mobile Technologies LLCNo claims unpatentable
  PTAB · Sep 25, 2024 · IPR2022-01223 · APJ Hyun J Jung · IPR · Final written decision

  Claims 1–3 and 5 were not shown unpatentable over Yegoshin, Bernard, Johnston, and Preiss under § 103 because the evidence did not establish multiplexing signals.

  RulingsFinal written decision

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

    “communication device for multiplexing signals.” Ex. 1001, 12:2–3 (emphasis added). The language in the preamble does not support adopting Petitioner’s proposed interpretation of “multiplexing” to mean that “the connections may be used simultaneously or sequentially for combining multiple data paths into a single path,” because signals are being multiplexed, not connections or data paths. Pet. Reply 10. No connection is recited in the preamble with regard to multiplexing.” slip op. at 13

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

    “Resp. 9–10 (citing Ex. 1002 (file history of the ’075 patent), 12; Ex. 2003 (Defendants’ Opening Claim Construction Brief from related litigation), 40–41; Ex. 2023 (Claim Construction Order from related litigation), 7). “Petitioner does not dispute that the preamble of claim 1 is limiting.” Pet. Reply 9 (citing PO Resp. 9–10; Ex. 2003, 45–46). Based on the full record, we adopt the parties’ agreement that the preamble is limiting. See also Ex. 2003, 45–46; Ex. 2023, 7.” slip op. at 9

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

    “show by a preponderance of the evidence that Yegoshin teaches or would have been understood to reasonably suggest “multiplexing signals” and that Bernard “includes or operates as a multiplexer for combining the data packets.” See Pet. 32–40. Because Petitioner does not show multiplexing signals in any of the asserted references, Petitioner does not show by a preponderance of the evidence that its proposed combination of Yegoshin, Bernard, Johnston, and Preiss would have rendered obvious “[a]n IP-enabled communication device for multiplexing signals,” as recited by claim 1. Also, because Petitioner fails to show Yegoshin teaches or would have been understood to reasonably suggest multiplexed signals and fails to show that Bernard “includes or operates as a multiplexer for combining the data packets,” Petitioner’s asserted motivation to modify Yegoshin in view of Bernard for “multiplexing signals” lacks rational underpinning. Weighing the underlying factual determinations, a preponderance of the evidence does not persuade us that claim 1 of the ’075 patent is unpatentable over Yegoshin, Bernard, Johnston, and Preiss. Arctic Cat, 876 F.3d at 1361.” slip op. at 44

  • Expert testimonyPetitioner expert discountedPatent owner expert creditedDecided for patent owner

    “We do not credit Petitioner’s cited testimonial evidence because, for the reasons above, Yegoshin and the full record do not support it. Ex. 1003 ¶¶ 79, 80. We, instead, credit Patent Owner’s cited testimonial evidence because Yegoshin and the full record better support it. Ex. 2018 ¶¶ 50, 51, 55–56, 58–61; see also Ex. 2025, 65:19–66:4.” slip op. at 26

  Patent outcomesUS 9,319,075 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,319,075
• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationNo claims unpatentable
  PTAB · Sep 17, 2024 · IPR2024-00037 · APJ Brent M Dougal · IPR · Final written decision

  Claims 1–9, 12–24, and 27–31 were not shown unpatentable because Petitioner did not prove either asserted obviousness combination taught the claimed controller or packet-applicable criterion.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time of the invention. Id. at 13, 17. Petitioner asserts that a person of ordinary skill in the art (POSA): would have had a bachelor’s degree in computer science, computer engineering, or an equivalent, and two years of professional experience, and a POSA would have had a working knowledge of hardware and software for packet-switched networking. EX1004, ¶¶48-49. Lack of work experience can be remedied by additional education and vice versa. Id., ¶48. Pet. 5. “Patent Owner does not dispute Petitioner’s level of ordinary skill.” PO Resp. 16. We are persuaded that Petitioner’s proposal is consistent with the problems and solutions in the ’111 patent and prior art of record. We adopt Petitioner’s definition of the level of skill for the purposes of this Decision.” slip op. at 6

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

    “Both parties agree that the ultimate analysis “remains the same” under either construction. Id. at 2; PO Sur-reply 2. We likewise agree that we do not need to decide between the two constructions. At the same time, consistent with parties’ positions, we construe “controller” to mean an entity that is either 1) configured to 2 Though Patent Owner does not provide a citation in support, Petitioner does not disagree that this is consistent with what occurred in the parallel district court proceeding. See Reply 1. perform deep packet inspection on packets, or 2) that is capable of controlling deep packet inspection. We determine that no other terms need to be construed. 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 7

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

    “Though Petitioner asserts that there are a “limited number of design options” and that it would have been obvious to combine the different components of Lin, Petitioner does not establish that a controller configured to perform DPI analysis on packets was a known solution, and thus one of the limited design options. As discussed in KSR: When there is a design need or market pressure to solve a problem and there are a finite number of identified, predictable solutions, a person of ordinary skill has good reason to pursue the known options within his or her technical grasp. If this leads to the anticipated success, it is likely the product not of innovation but of ordinary skill and common sense. In that instance the fact that a combination was obvious to try might show that is was obvious under § 103. KSR, 550 U.S. at 421. Besides asserting the combination would have been “obvious to try,” Petitioner provides no other analysis or reason why one of skill in the art would have modified the teachings of Lin to obtain the claimed controller. Thus, Petitioner has not established by a preponderance of the evidence that the teachings of Lin render obvious all of the features of claim 1.” slip op. at 18

  • Expert testimonyPatent owner expert creditedPetitioner expert discountedDecided for patent owner

    “Further, we find the testimony of Patent Owner’s declarant more persuasive based at least on his consideration of Swenson as a whole and his more detailed analysis and explanations. For example, Patent Owner’s declarant explains in detail why, “[i]n the context of a HTTP GET request and response, as disclosed in Swenson, the message does not constitute a single packet but a flow of packets:” Furthermore, Swenson discloses that the steering device 130 “sends an ICAP request message 516 comprising [a] HTTP GET request header and a portion of the [HTTP] response payload to the network controller 140, which inspects the message to determine whether to monitor the flow or optimize the video.” Ex. 1007 [0065]. In the context of a HTTP GET request and response, as disclosed in Swenson, the message does not constitute a single packet but a flow of packets. The reference to a HTTP request and response “header” and “payload” are thus not references to the header and payload of a packet. A POSA would know that despite common parlance references to “HTTP packets,” HTTP does not pertain to individual packets, whereas packet transmission is governed by the TCP protocol. HTTP utilizes TCP to exchange data such that information may be used by an end user (e.g., a video or audio stream). Even assuming that Swenson’s controller were analyzing the header and payload of an HTTP request/response, a POSA would understand that this analysis is not at the packet but at the flow level and thus does not constitute deep packet inspection. Ex. 2025 ¶ 69. Petitioner’s declarant merely responds by reiterating what was previously stated: Swenson is explicit in stating that its inspection techniques include inspection of “a portion of the [HTTP] response payload.” . . . A POSA would have understood the analysis of the “response payload” to be DPI by a DPI-capable controller, as DPI refers to monitoring the payload of a packet.” slip op. at 15

  Patent outcomesUS 10,652,111 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,652,111
• Cisco Systems, Inc. / Juniper Networks, Inc. v. Orckit CorporationNo claims unpatentable
  PTAB · Sep 17, 2024 · IPR2023-00554 · APJ Brent M Dougal · IPR · Final written decision

  Claims 1–9, 12–24, and 27–31 were not shown unpatentable because neither asserted obviousness combination established all limitations of claim 1.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “understanding of a person of ordinary skill in the art at the time of the invention. Id. at 13, 17. Petitioner asserts that a person of ordinary skill in the art (POSA): would have had a bachelor’s degree in computer science, computer engineering, or an equivalent, and two years of professional experience, and a POSA would have had a working knowledge of hardware and software for packet-switched networking. EX1004, ¶¶48-49. Lack of work experience can be remedied by additional education and vice versa. Id., ¶48. Pet. 5. “Patent Owner does not dispute Petitioner’s level of ordinary skill.” PO Resp. 16. We are persuaded that Petitioner’s proposal is consistent with the problems and solutions in the ’111 patent and prior art of record. We adopt Petitioner’s definition of the level of skill for the purposes of this Decision.” slip op. at 6

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITATerm construed board ownOther

    “We likewise agree that we do not need to decide between the two constructions. At the same time, consistent with parties’ positions, we construe “controller” to mean an entity that is either 1) configured to 2 Though Patent Owner does not provide a citation in support, Petitioner does not disagree that this is consistent with what occurred in the parallel district court proceeding. See Reply 1. perform deep packet inspection on packets, or 2) that is capable of controlling deep packet inspection. We determine that no other terms need to be construed. 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 7

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “We agree with Patent Owner that DPI and DFI would have been understood to be different processes – That DPI inspects the detailed contents of individual packets in a granular, thorough manner; and, in contrast, DFI focuses on the broader patterns of network traffic flows by looking at aggregate data flow characteristics. As discussed above, the testimony of Patent Owner’s declarant as to the understanding of DPI is largely uncontested. Further, the testimony of Patent Owner’s declarant as to the understanding of DFI is supported by Swenson when considered as a whole as well as supported by Exhibit 2027.” slip op. at 13

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

    “a POSA would have understood that one of the limited number of design options would have been to implement the security service as part of a controller configured to perform DPI analysis on packets, and a POSA would have had a reasonable expectation that the controller would have been successful in performing DPI analysis. Id. at 18–19 (citing Ex. 1004 ¶ 79 (making an identical statement)). No additional discussion, explanation, or evidence on these points were provided at the Petition stage. Patent Owner argues that: The mere fact that the security service may share certain common technical characteristics with the controller (i.e., its connection to the network switch and the hardware in which these two separate entities are implemented) cannot in and of itself suggest to a POSA that the function carried out by the security service should also be performed by the controller or that the controller should be configured to perform that function (i.e., deep packet inspection). PO Resp. 21–22 (citing Ex. 2025 ¶¶ 54–55). We agree. Though Petitioner asserts that there are a “limited number of design options” and that it would have been obvious to combine the different components of Lin, Petitioner does not establish that a controller configured to perform DPI analysis on packets was a known solution, and thus one of the limited design options. As discussed in KSR: When there is a design need or market pressure to solve a problem and there are a finite number of identified, predictable solutions, a person of ordinary skill has good reason to pursue the known options within his or her technical grasp. If this leads to the anticipated success, it is likely the product not of innovation but of ordinary skill and common sense. In that instance the fact that a combination was obvious to try might show that is was obvious under § 103. KSR, 550 U.S. at 421. Besides asserting the combination would have been “obvious to try,” Petitioner provides no other analysis or reason why one of skill in the art would have modified the teachings of Lin to obtain the claimed controller. Thus, Petitioner has not established by a preponderance of the evidence that the teachings of Lin render obvious all of the features of claim 1.” slip op. at 17

  Patent outcomesUS 10,652,111 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,652,111
• Cisco Systems, Inc. v. Corrigent CorporationNo claims unpatentable
  PTAB · Aug 6, 2024 · IPR2023-00447 · APJ Nathan A Engels · IPR · Final written decision

  Claims 1–26 were not shown unpatentable because the Petition did not establish the claimed port assignment and packet labeling under Raz or adequately explain the Raz–Ferguson combination.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “packet-switched networking, MPLS and LAG.” Pet. 6 (citing Ex. 1004 ¶¶ 57–58). Petitioner also states that a lack of work experience can be remedied by additional education, and vice versa. Pet. 6 (citing Ex. 1004 ¶ 57). Patent Owner “uses the same definition.” PO Resp. 4. We apply Petitioner’s level of ordinary skill, which is undisputed and is consistent with the level reflected by the ’602 patent and the asserted prior art.” slip op. at 6

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

    “We construe claims using the principles set forth in Phillips v. AWH Corp., 415 F.3d 1303, 1312–17 (Fed. Cir. 2005) (en banc) and related cases. See 37 C.F.R. § 42.100(b) (2022). Under that precedent, the words of a claim are generally given their “ordinary and customary meaning,” which is the meaning the term would have to a person of ordinary skill at the time of the invention, in the context of the entire patent including the specification. Phillips, 415 F.3d at 1312–13. Neither party proposes any express claim constructions. Pet. 6–7; see PO Resp. 4. To the extent that the parties dispute the meaning of certain claim terms, we address those issues below, but we determine it is unnecessary to expressly construe any terms. 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 6

  • BurdenNot shown unpatentable

    “Patent Owner argues, and we agree, that the cited portions of Raz do not disclose a LAG between two switches. PO Resp. 8–9. Petitioner acknowledges this; as stated in Petitioner’s Reply, “Petitioner has always acknowledged that Raz addresses the use of subports within an LSR, but a [person of ordinary skill in the art] would have found it obvious from Raz to use Ethernet physical data ports of a router or switch in an Ethernet LAG to communicate high-speed packet streams in [an] MPLS network.” Pet. Reply 2 (citing Pet. 15, 19, 22–25; Ex. 1021 ¶ 13; Ex. 1006, 1:16–19, 2:23– 31, 7:7–29, 11:3–12, 13:16–19, 14:42–44, 15:56–58, 17:7–9). Petitioner argues that LAGs were well known and, “[w]hile PO argues that Raz teaches the use of a single high-speed link to communicate between LSRs, that is merely a design choice.” Pet. Reply 3 (citing Ex. 1021 ¶¶ 15–17; PO Resp. 8–9). Further, Petitioner argues “[i]t would have been obvious to a [person of ordinary skill in the art] that high-speed packet streams could be communicated between switches or routers through a physical tunnel port of a LAG.” Pet. Resp. 3 (citing Ex. 1021 ¶¶ 15–17) (emphasis added). Among other problems, though, those arguments were not in the Petition; the Petition does not describe modifications of Raz’s teachings, much less establish those modifications as a “design choice.” See Pet. 25; see also PO Sur-reply 3. Further, we agree with Patent Owner that Raz is fundamentally different with its teachings of multiplexing the outputs of multiple slow- speed subports/processors into a single stream for transmission across a single high-speed link. PO Resp. 7–9, 12–13, 15–16; PO Sur-reply 4–5. As stated in Raz, “[t]he present invention provides a subport forwarding and provisioning mechanism whereby a plurality of subports comprising slower speed processors are used to perform the packet processing for a higher speed packet stream.” Ex. 1006, 6:24–27. Additionally, where Raz describes communication between two LSRs, Petitioner acknowledges that Raz teaches that its cited second LSR assigns the port on which it will receive a data packet. Pet. Reply 4; Ex. 1021 ¶ 20 (“in Raz, the second LSR chooses the subport that will be used to transmit the data packet from the first LSR and receive the data packet at the second LSR”). According to Petitioner, Raz teaches that “a first LSR generates a data packet label in which a port serial number is encoded and sends the label to a preceding LSR. Subsequently, the preceding LSR sends a data packet to the proper subport for processing. The process is then repeated in sending the data packet from the first LSR to a second LSR.” Pet. Reply 4 (citations omitted). “This technique just as easily could have been implemented to identify a single physical tunnel port through which a data packet in a first router or switch would be communicated to a second router or switch via a LAG.” Pet. Reply 4 (emphasis added) (citing Ex. 1006, 2:23–25, 7:7–16, 7:22–26, 11:3–29, Fig. 5; Ex. 1021 ¶ 18). Again, these arguments were not made in the Petition (see Pet. 22–25), and Petitioner’s assertions that Raz’s teachings “just as easily could have been implemented” in the manner claimed is improper hindsight and inconsistent with the fundamental differences between Raz’s multiplexing within an LSR and the claimed link aggregation and port assignment between MPLS/LAG switches.” slip op. at 8

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

    “[c]laims 1–13, 15–24 and 26 set forth above in Ground 1.” Pet. 52. Further, Petitioner states that “[f]or independent [c]laims 1, 15, and 26, Ferguson builds on the previous analysis of Raz by disclosing a system for communicating packets between switches and routers in an MPLS network.” Pet. 52; see Pet. 52–55. Critically, though, Petitioner does not specifically explain how the combined teachings of Raz and Ferguson would satisfy individual claim elements. Among other problems with Petitioner’s proposed combination, Petitioner does not adequately explain how or why a person of ordinary skill would have combined the references to include the claimed port assignment and packet labeling for transmission of a packet from a preceding node and then between a first and second MPLS switch. See Pet. 56–59. Instead, Petitioner generally advocates for the combination of Raz and Ferguson, arguing for example that “both Raz and Ferguson are directed to solving the problem of ensuring enough bandwidth is available to communicate high-speed packet streams through an MPLS network.” Pet. 57 (citing Ex. 1006, 10:60–11:12, 14:33–41, 15:47–55, 17:1–9, Fig. 5; Ex. 1007, 1:28–42, 2:54–57, 4:55–60; Ex. 1004 ¶¶ 247–249). Further, Petitioner contends a person of ordinary skill “would have understood from the disclosures in Ferguson that techniques for utilizing an Ethernet physical data port in a LAG to communication data packets between routers or switches in an MPLS network are also applicable to the use of subports transmitting the data packets within the routers or switches, and vice versa.” Pet. 59 (citing Ex. 1004 ¶ 250; Ex. 1007, 5:61–6:6); see Pet. 56–59; Pet. Reply 20. But Petitioner does not adequately explain how the proposed combination of Raz and Ferguson would cure the deficiencies addressed above in Petitioner’s analysis of Raz for Ground 1. Among other problems, none of Petitioner’s arguments adequately address port assignment and labeling in the proposed combination, much less adequately explain why the proposed combination would satisfy the challenged claims. See Pet. 55–56. As Petitioner does not adequately explain how the teachings of Raz and Ferguson might be combined to cure the deficiencies addressed above, we additionally determine Petitioner’s arguments and evidence advanced for the combination of Raz and Ferguson do not establish obviousness by a preponderance of the evidence for any of claims 1–26.” slip op. at 11

  Patent outcomesUS 9,118,602 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 9,118,602
• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00398 · APJ George R Hoskins · IPR · Final written decision

  Claims 1–22 were not shown unpatentable as obvious over Dill, Vadhri, and Akashika because Dill was not shown to disclose the claimed Integration Tier Limitation.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “We adopt Petitioner’s undisputed formulation of ordinary skill in the art as set forth above, because we are satisfied this formulation generally comports with the level of skill necessary to understand and implement the teachings of the ’196 patent and the asserted prior art. We do not adopt Patent Owner’s annotation to Petitioner’s formulation as requiring knowledge of “mobile wallets” specifically, because we determine knowledge of “mobile payment systems and techniques” per Petitioner’s formulation is tied sufficiently to the claims of the ’196 patent to reflect the level of ordinary skill in the pertinent art. At the same time, even if we were to include knowledge of “mobile wallets” in our formulation, it would not materially change our Decision as set forth below. That is, we would still determine Petitioner has not shown by a preponderance of the evidence that Dill discloses the Integration Tier Limitation.” slip op. at 10

  • Expert testimonyNot reached

    “We need not resolve the parties’ dispute as to whether Dr. Houh qualifies as an ordinarily skilled artisan. Even assuming that Dr. Houh possesses, at a minimum, ordinary skill in the art—as we have done in this Decision—we determine Petitioner still fails to show that any of the challenged claims are unpatentable.” slip op. at 12

  • Claim Construction › Threshold & procedure › Whether a term needs construction (O2 Micro)No construction neededDecided for patent owner

    “The Integration Tier Limitation requires no further construction for purposes of this proceeding. See Pet. Reply 7 (“[N]o specific construction is required.”). The claim clearly specifies that the claimed “web services communication mechanisms” must serve as an interface between the integration tier and (1) the claimed mobile wallet application and, separately, (2) “a plurality of different device types over a plurality of different communication channels.” For purposes of this Decision, we assume that this interface may be direct or indirect. See id. at 6 (asserting that “communication channels that interface, even indirectly, with the ‘web services communication mechanisms’ still interface with the ‘web services communication mechanisms’”).” slip op. at 28

  • Obviousness (§103) › Graham factors (scope of art, differences, level of skill)Not shown unpatentableNot shown unpatentable

    “However, we find that of those four channels (1)–(4), only the first channel (1) is associated with web interface 137 such that it qualifies as a “communication channel,” as required by claim 1. There is no indication in the Dill disclosures cited by Petitioner that any of the other three channels (2)–(4) are associated with web interface 137. For example, Figure 9 of Dill includes a double-headed arrow to illustrate communication between web interface 137 and transfer options module 145, but Figure 9 does not include any arrows to illustrate communication between web interface 137 and any one or more of IVR interface 136, other interfaces 138, agent system 135, or mobile network 115. See Ex. 1005, Fig. 9. In other words, Petitioner fails to show Dill teaches web interface 137 interfaces with any devices over any of channels (2)–(4), as would be required by Petitioner’s mapping. In the Petition, Petitioner never clearly (or persuasively) addresses this requirement of the claim. Petitioner does contend that transfer options module 145 is coupled to various devices via interfaces 136–138 and exchanges transaction information (see Pet. 25–26; see also Pet. Reply 10– 11), but that contention misses the mark. The salient question is whether Dill’s web interface 137 (i.e., the claimed “web services communication mechanisms”) interfaces with the different device types over the channels, not whether transfer options module 145 (i.e., the claimed “integration tier”) does so.” slip op. at 30

  Patent outcomesUS 10,438,196 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,438,196
• Apple Inc. v. Fintiv, Inc.No claims unpatentable
  PTAB · May 23, 2024 · IPR2023-00399 · APJ Juliet Mitchell Dirba · IPR · Final written decision

  Claims 1–22 were not shown unpatentable under § 103 over Dill, Vadhri, and Akashika because Dill did not teach or render obvious the hardware SIM card and integration tier limitations.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “In the Institution Decision, we determined that a person of ordinary skill in the art would have had “a bachelor’s degree in electrical engineering, computer science, or equivalent training, and approximately two years of work experience in software development with a basic knowledge of accounting” and “working knowledge of mobile payment systems and techniques,” as Petitioner proposes. Inst. Dec. 9 (quoting Pet. 3–4). We stated that “this definition generally comports with the level of skill necessary to understand and implement the teachings of the ’488 patent and the asserted prior art.” Id. (citing Ex. 1003 ¶ 22; Ex. 2001 ¶ 35).” slip op. at 10

  • Expert testimonyPetitioner expert discountedMixed

    “In addition, Petitioner’s reliance on Dr. Houh’s testimony (see Pet. 23–24) is unavailing. Although Dr. Houh agrees with the arguments in the Petition and includes quotes from the cited portions of Dill and Bykov (see Ex. 1002 ¶¶ 95–97), he provides no additional analysis or explanation beyond what was provided in the Petition. As a result, his testimony suffers the same deficiencies as the Petition. Also, we do not credit his conclusion that Dill includes the requisite disclosure (see id. ¶ 97) because he fails to provide sufficient supporting explanation or evidence (see 37 C.F.R. § 42.65(a)). Finally, we note that Petitioner misrepresents Dr. Shamos’s testimony by stating that Dr. Shamos “agrees that if a mobile device executes a mobile wallet over a cellular network, the mobile device has a SIM card for the mobile wallet.” Pet. Reply 22 (emphasis added) (citing Ex. 1022, 29:4–7, 40:9–10). In the cited testimony, Dr. Shamos agrees that mobile devices have SIM cards, but he does not address where a mobile wallet application would be installed. Ex. 1022, 29:4–7, 40:9–10. Thus, contrary to Petitioner’s argument, we determine that Dr. Shamos’s testimony does not support Petitioner’s position.” slip op. at 27

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

    “for the term “hardware SIM card” because the important points are undisputed. In particular, the parties agree that a “hardware SIM card” is a SIM card implemented in hardware rather than software. See Pet. Reply 9 (citing Ex. 1021 ¶ 36); Tr. 40:25–41:2 (Patent Owner’s counsel explaining that the language in its proposed construction was “to differentiate it from a software SIM card”); see also PO Resp. 16, 19 (asserting that the term refers to a specific type of hardware, namely a “chip” or a “smart card”) (citing Ex. 2003 ¶¶ 32–33). The parties also agree that an ordinarily skilled artisan would have known that a “SIM card” is a component in a mobile device involved in identifying and authenticating a user to a mobile network. See Tr. 30:23–31:3 (Petitioner’s counsel stating “a SIM card, just as known in the art . . . would allow the user to be able to access the mobile network” 10 Each page in Exhibit 2021 includes at least two page numbers. For clarity, we refer to the page number of the exhibit (shown in the bottom right corner), and we have adjusted Patent Owner’s citation accordingly. given “the user’s identification information on it”), 39:24–40:2 (Patent Owner’s counsel stating that “I think everyone is in agreement that the critical aspect of what makes a SIM card a SIM card is that it can authenticate a mobile device to a wireless network”). The evidence supports the parties’ understanding. The word “SIM” is an acronym for “subscriber identity module” (see, e.g., Ex. 1001, 6:58–67; Ex. 2021, 5), and the record shows that a SIM is a specific component in a mobile device that is involved in identifying and authenticating a user to a mobile network (see Ex. 2003 ¶¶ 30–31; see also e.g., Ex. 2021, 7 (stating that a SIM’s “primary function” is “to authenticate the subscriber to the network”); Ex. 2025, 3 (describing the SIM)).11 Consequently, we determine that an ordinarily skilled artisan would have understood a “hardware SIM card” to be a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. We do not need to further construe the term, or determine whether the additional requirements proposed by Patent Owner are appropriate, because Petitioner fails to show that the prior art teaches or suggests the claimed “hardware SIM card,” as explained below. See infra § II.D.2.a (analyzing the parties’ substantive contentions).” slip op. at 13

  • BurdenNot shown unpatentable

    “Petitioner has not shown, by a preponderance of the evidence, that Dill discloses “a mobile wallet application installed on a hardware SIM card,” as required by element 1.3B. See Pet. 23–24. In particular, even assuming that Dill teaches installing a mobile wallet application somewhere on a mobile device (see Pet. 23),14 Dill does not teach installing it on a hardware SIM card,15 as specifically required by the claim. Petitioner relies upon paragraph 106 of Dill (see Pet. 23), but that paragraph does not disclose this claim limitation (see Ex. 1005 ¶ 106). In relevant part, that paragraph of Dill simply states: 14 Patent Owner disagrees with this premise, arguing that Dill does not disclose a mobile device that includes a mobile wallet application. See PO Resp. 52–56. We need not resolve that dispute because, even assuming Petitioner’s premise (as we have done in this Decision), Petitioner still fails to show that the claims are unpatentable. 15 As noted above, a “hardware SIM card” is a hardware component in a mobile device that is involved in identifying and authenticating a user to a mobile network. See supra § II.C.1 (addressing meaning of term). It should also be appreciated that the methods described above may be performed by hardware components or may be embodied in sequences of machine-executable instructions, which may be used to cause a machine such as a general-purpose or special-purpose processor or logic circuits programmed with the instructions to perform the methods. These machine-executable instructions may be stored on one or more machine readable mediums, such as CD-ROMs or other type of optical disks, floppy diskettes, ROMs, RAMs, EPROMs, EEPROMs, magnetic or optical cards, flash memory, or other types of machine-readable mediums suitable for storing electronic instructions. Alternatively, the methods may be performed by a combination of hardware and software. Ex. 1005 ¶ 106 (emphases added). This teaches storing instructions on “other types of machine-readable mediums,” but it fails to teach storing instructions on a hardware SIM card, much less storing Dill’s mobile wallet application there. In short, Dill is silent with respect to this issue, and silence is not disclosure. Notably, Petitioner does not contend (or show) that a mobile wallet application installed on a mobile device would necessarily be installed on a hardware SIM card. See Pet. 23–24; Ex. 1003 ¶¶ 95–97. Indeed, the record indicates that a mobile wallet application installed on a mobile device could instead be installed on a different component. See, e.g., Ex. 1001, 7:1–3, 9:33–35 (identifying device memory as alternate component); Ex. 2021, 5 (describing SIM as the “smaller of two computer chips inside a GSM mobile handset”); cf. Pet. Reply 9 (distinguishing between hardware SIM cards and software ones). Thus, Petitioner fails to show that this claim limitation is inherent in Dill. See PAR Pharm., Inc. v. TWI Pharms., Inc., 773 F.3d 1186, 1196 (Fed. Cir. 2014) (explaining that inherency requires a showing that “the limitation at issue necessarily must be present”).” slip op. at 22

  Patent outcomesUS 9,208,488 not shown unpatentable
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 9,208,488
• Medivis, Inc. v. Novarad Corp.No claims unpatentable
  PTAB · Mar 6, 2024 · IPR2023-00042 · APJ Scott Raevsky · IPR · Final written decision

  Claims 1–6 and 11–20 were not shown unpatentable: Doo did not disclose the claimed volume, the Doo-Amira combination lacked a persuasive rationale, and the other references were not shown publicly accessible.

  RulingsFinal written decision

  • Skill levelSkill level board ownDecided for petitioner

    “We adopt Petitioner’s proposed level of skill, except that we excise part of Petitioner’s definition to produce the following modified version: a bachelor’s degree in computer science, electrical engineering, or a related field with several years of experience in the design, development, and study of augmented reality devices and . . . familiarity with conventional medical imaging data and visualization of data for medical procedures . . . . Our edit removes the alternative of “working with a team including someone with such familiarity” because one’s role in a team may be tangential to their personal experience with medical imaging. Regardless, had we adopted Petitioner’s original definition, our decision would not have changed.” slip op. at 7

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

    “The parties propose constructions for the claim terms “three- dimensional (3D) data,” “inner layer(s) of the patient,” “confined within a virtual 3D shape,” and “being having.” Pet. 11–14; PO Resp. 11–18. We do not need to construe any of these claim terms in order to resolve the issues presented in this proceeding. See Realtime Data, LLC v. Iancu, 912 F.3d 1368 (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 8

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

    “First, neither the Petition nor Dr. Kazanzides explains how Doo’s curved plane teaches the claimed “volume.” See Pet. 36–37; Ex. 1012 ¶¶ 74–75 (essentially repeating the Petition). The Petition merely asserts that Doo’s image in Figure 7 “is confined within the volume of the virtual 3D shape illustrated in Figure 9,” without explaining how the shape of Figure 9 has a “volume.” Pet. 37. The Reply does no better, asserting that “Doo’s shape 532 in Figure 9 and shape 432 in Figure 7 are virtual 3D shapes.” Reply 18. This statement is conclusory and does not explain how Doo’s “false 3D” shapes have volume. Petitioner further attempts to establish that Doo’s disclosure of Figure 9’s shape 532 as “mimic[ing] the surface curvature of the patient’s body” is evidence that Doo discloses a 3D shape. Id. (citing Ex. 1008 ¶ 76). This argument, however, is unpersuasive because it takes Doo’s statement out of context. Doo explains that Figure 9’s warped “two-dimensional image 532 . . . mimic[s] the surface curvature of the patient’s body,” not that it has volume. See Ex. 1008 ¶ 76 (emphasis added). In other words, even though Doo’s shape 532 of Figure 9, when projected on a patient’s body (as in Figure 7) may appear to a surgeon like a 9 Our Institution Decision did not rely on Petitioner’s theory based on Doo Figures 7–9. We discuss our Institution Decision’s reasoning below under Petitioner’s second theory based on Doo Figures 6 and 11. half-cylinder shape having a volume, Doo’s technique avoids rendering a 3D shape like a half-cylinder (hence calling these “false 3D shapes”) because it instead simulates the body’s curvature with a mere curved two-dimensional plane. Second, we find that Doo’s curved plane does not, in fact, have a volume.10 Instead, Doo’s curved plane is a 2D plane merely “wrapped around an axis.” See Ex. 1008 ¶¶ 75–76. As Patent Owner persuasively argued at the hearing, Doo’s curved plane is not “half of a cylinder. It’s just a wrapped piece of paper.” Tr. 33:14–15. Just as curving a piece of paper would not give the curved paper a half cylinder’s volume, neither does curving Doo’s flat 2D plane create a half cylinder with volume. Viewed another way, curving a 2D plane does not impart volume to the plane any more than curving a 1D line into a parabola would impart area to the 1D line.” slip op. at 12

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

    “The U.S. Supreme Court has emphasized that “rejections on obviousness grounds cannot be sustained by mere conclusory statements; instead, there must be some articulated reasoning with some rational underpinning to support the legal conclusion of obviousness.” KSR, 550 U.S. at 418 (quoting In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). Petitioner’s argument fails this standard. Petitioner asserts a generic rationale that one of ordinary skill in the art would have applied Amira to Doo “to take advantage of the visualization technology disclosed in Amira (or any similar visualization software).” Pet. 41. But Petitioner’s assertion contains no explanation why one of ordinary skill would have taken advantage of Amira’s technology in the context of Doo. Petitioner’s rationale is so vague and broad that it could be applied to combine any two references because it merely asserts that one reference would “take advantage of the . . . technology disclosed in” another. See, e.g., In re Van Os, 844 F.3d 1359, 1361 (Fed. Cir. 2017) (explaining that “a finding that a combination of prior art would have been . . . ‘intuitive’ is no different than merely stating the combination ‘would have been obvious’”). This approach wholly misses KSR’s “articulated reasoning” standard. See KSR, 550 U.S. at 418. The Reply’s assertion that reducing a surgeon’s cognitive load in Doo “suggests an improvement on conventional medical imaging displays, such as disclosed in Amira,” fares no better. Reply 20. This assertion again fails to explain why one of ordinary skill in the art would have combined Amira with Doo. For instance, Petitioner provides no explanation as to how Amira’s display would further reduce cognitive load. See Reply 19–20 (only vaguely referring to Amira’s “[t]racking capabilities [that] allow for . . . interaction with the visualization” (Ex. 1005, 14, 26)). Not only that, but Doo itself presents a solution for the cognitive load problem. See Ex. 1008 ¶ 14 (“The present invention is particularly adapted to manage the multitude of medical images needed to be viewed by a surgeon during an operation so that a surgeon is not required to look away from the patient, so that the surgeon does not have to sustain heavy cognitive loading.”). Petitioner does not persuasively explain why one of ordinary skill in the art would turn to yet another reference (like Amira) for an additional solution, or even what that solution would be.” slip op. at 23

  Patent outcomesUS 11,004,271 not shown unpatentable
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR
  Patents in suitUS 11,004,271
• Netflix, Inc. v. Divx, LLCNo claims unpatentable
  PTAB · Feb 22, 2024 · IPR2020-00558 · APJ Iftikhar Ahmed · IPR · Remand

  The majority determined claims 1–24 were not shown unpatentable over Chen, Lindahl, and Hurst; the dissent would have found them obvious.

  RulingsRemand decision

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

    “We determine Patent Owner’s reading of the claim limitation is the better one. The limitation begins with the verb “locating,” and it therefore makes sense that the clause would recite what is located (i.e., encryption information) and where it is located (i.e., within the requested portions of the selected stream of protected video). In other words, it is reasonable that the second and third clauses of the limitation both modify the first clause (for example, as could perhaps be expressed through the use of commas as “locating encryption information, that identifies encrypted portions of frames of video, within the requested portions of the selected stream of protected video”).10 On the other hand, Petitioner’s reading of the limitation, 10 In general, we recognize that the use of commas to set off phrases in claim drafting is not consistent. We included commas above to illustrate Patent Owner’s understanding of the claim limitation. allowing only the second clause to modify the first, while not unreasonable, makes less sense. That is, the encrypted information identifies the encrypted portions of frames, which in turn are within the requested portions of the selected stream of protected video. Reading the claim in its entirety, the encrypted portions of frames would be understood to be located within the requested portions of the stream; it does not seem necessary for the claim to expressly recite that aspect. For example, the very next limitation— limitation [m] of claim 1—refers to “each encrypted portion of the frames of video” but does not expressly recite “within the requested portions of the selected stream.” Ex. 1001, 27:58–60. Thus, when limitation [l] recites “within the requested portions of the selected stream,” it seems more likely that the clause refers to where that encrypted information is located rather than simply to indicate the obvious location of the encrypted portion of the frames of video. We therefore view Patent Owner’s reading of the claim language as the better one.” slip op. at 13

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

    “I am persuaded that the Petition demonstrates that one of ordinary skill in the art would have had a motivation to combine Chen, Lindahl, and Hurst, as asserted by Petitioner. As the Federal Circuit found, the Petition pointed to and relied upon the portions in Chen describing pre-Chen art, without scalability or FEC features that were part of what Chen describes as aspects of its own inventive system. Netflix, slip op. at 9–10 (citing Pet. 17– 19, 69–70). I agree with Petitioner that “Chen-924 teaches several embodiments that adaptively stream alternative representations of a video using partially encrypted container files.” Pet. 20 (citing Ex. 1010, 14:41– 15:60). I determine that Chen-924 provides support for the rationale provided in the Petition, and that one of ordinary skill in the art would have been motivated to combine Chen and Lindahl in view of the disclosure of Chen-924. As discussed above, the Petition does not rely solely on privacy concerns and improvements to efficiency as its motivation to combine the references. See Pet. 18–19 (specifying piracy concerns, improvements to the efficiency of adaptive streaming, optimization of the balance between bitrate and bandwidth, and improvements to the end-user experience with fast startup and seek). With respect to whether one of ordinary skill in the art would have” slip op. at 52

  • Strike new argumentNew argument disregardedDecided for petitioner

    “I agree with Petitioner that Patent Owner’s Remand Brief, specifically pages 1–7, attempt to address aspects of claim 1 for the first time on remand. I also agree that Patent Owner’s arguments attempt to recharacterize limitations [j] and [k] to raise issues that Patent Owner did not raise previously, in contravention of our Order that issues raised needed support from “where those issues were raised in previous briefings by the parties.” Paper 56, 2. I have addressed whether scalability and FEC are integral to how Chen operates above, as well as whether the Petition relies on those aspects, supra. The questions about how Chen operates and what portions of Chen are asserted in the ground of unpatentability were previously raised, but now are being considered or reconsidered, based on the Federal Circuit’s decision. In Patent Owner’s Remand Brief, pages 1–7, the citations to argument previously raised do not support the arguments now presented by Patent Owner on remand. As such, I determine Patent Owner’s new arguments fall outside the scope of remand, and I dismiss these arguments seeking to distinguish limitations [j] and [k] from the cited prior art combination.24” slip op. at 62

  • ExcludeMotion to exclude, grantedMixed

    “7 Patent Owner’s Brief on Remand recognizes that there are two arguments Patent Owner raised in its Patent Owner Response that were not addressed in the Final Written Decision. See PO Remand Br. 1 (citing PO Resp. 24–37 (the construction of “locating encrypted information . . . within requested portions”), 38–58 (referring to Patent Owner’s “common keys” argument)). 8 The Final Decision also addressed Petitioner’s Motion to Exclude (Paper 42). See Final Dec. 28–37 (granting-in-part, denying-in-part, and dismissing-in-part Petitioner’s Motion). Our determinations on that Motion were part of Petitioner’s appeal to the Federal Circuit. See Paper 52. Because the Federal Circuit did not address this aspect of the Final Written Decision and the Federal Circuit’s decision does not impact our previous rulings on the Motion, we maintain those rulings here. Additionally, on remand, Petitioner requested authorization to file a motion for sanctions, which we held in abeyance until the parties’ briefing on remand was complete. See Ex. 3003, 1. Petitioner requests sanctions because of the impropriety of Patent Owner’s remand brief, including new claim construction arguments for limitations [1j] and [1k], and prejudice to Petitioner. Id. at 3, 5. Although we reserved further consideration of Petitioner’s request, we expanded both the time and pages allowed for Petitioner’s responsive brief, and also allowed Petitioner to address any related issues in its responsive brief. Id. at 1. Having considered the parties’ briefing on remand, and given that we do not reach the claim construction arguments that Petitioner objected to in its request for authorization to file a motion for sanctions, we deny Petitioner’s request.” slip op. at 5

  Patent outcomesUS 10,225,588 not shown unpatentable
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 10,225,588

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.