• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00710 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1–7, 9, 13, and 16–20 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 8 was not shown unpatentable under either ground.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’294 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7

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

    “Petitioner indicates that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction. Thus, no express construction is required.” Pet. 13 (citing Ex. 1003 ¶ 86). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

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

    “rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 17

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “and reliance on Figure 19 do not in any way explain how updating game costs by meter 502 with a new Cost_Table is relevant to a credit multiplier or even a multiplier being varied over time. Ex. 1003 ¶ 155. Considering this evidence, we determine that Petitioner and Mr. Crevelt’s reliance mainly on snippets from Schneier’s “Updating Cost Information protocol” embodiment does not sufficiently explain why or how a person of ordinary skill in the art would have understood updating game cost to encompass varying a multiplier of credits over time. We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004:158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to persuasive evidence in Schneier as to how or why a person of ordinary skill in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 8.” slip op. at 20

  Patent outcomesUS 10,825,294 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,825,294
• Activision Blizzard, Inc. v. Milestone Entertainment, LLCSome claims unpatentable
  PTAB · Oct 13, 2026 · IPR2025-00709 · APJ Scott A Daniels · IPR · Final written decision

  Claims 1, 2, 4, 6, 8, 10, 14–18, 21–23, 25, 27, and 29 are unpatentable as obvious over Schneier and over Schneier with Okita; claim 9 was not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Patent Owner states it “does not dispute Petitioners’ proposed level of skill, and under any level of skill a POSITA would not understand the asserted Grounds to raise any unpatentability issue.” PO Resp. 4. Patent Owner states further that “this [Patent Owner Response] and supporting declarations apply Petitioner’s proposed level of skill.” Id. On this record, Petitioner’s proposed level of ordinary skill in the art is not contradicted and is consistent with the technology and descriptions in the ’635 patent and the asserted prior art references. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001). For purposes of this Decision, we rely on Petitioner’s proposed level of ordinary skill in the art.” slip op. at 7

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

    “Petitioner indicated in the Petition that “[t]his Petition establishes that the prior art meets each of the claim limitations under any reasonable construction.[] Thus, no express construction is required.” Pet. 12–13 (citing Ex. 1003 ¶ 85). In its Response, Patent Owner indicates that no constructions are necessary “because under any reasonable construction of the claim terms, the prior art fails to disclose or suggest the claimed features.” PO Resp. 4–5. Because there is no dispute between the parties as to any particular claim term and because the claims, as a whole, are reasonably clear on their face, no specific claim construction is necessary in this proceeding.” slip op. at 8

  • Expert testimonyPetitioner expert discountedDecided for patent owner

    “We also note that during his deposition, Mr. Crevelt was given opportunity to clarify his testimony as to Figure 19 and explain the cost updating embodiment in Schneier, and mostly demurred. See Ex. 2004, 158:4–182:6. Explaining his reliance on Figure 19, Mr. Crevelt stated: A: And whatever latest price from that updated cost information coming from the central site is -- is variable, it’s variable as time proceed[s]. It’s a – it’s a, much of a complicated section, and -- but the information is in the Schneier patent and shows that it could have -- it should change over time. Id. at 158:23–159:5. Mr. Crevelt further stated that: A: . . . for a metered play where you’re buying so much time or so many credits or so many games on a specific game and when it runs out, then have you to buy more, and that variable can change over time. Id. at 161:2–6. These explanations are unpersuasive because the testimony relates Schneier’s “updated cost,” with the claimed “multiplier” and “variable,” and does not adequately explain how they are equivalent or interconnected. See, e.g., id. at 160:16–23 (Mr. Crevelt testifying that “we can go from the description of figure 19, which starts at basically the top of column 56 in the Schneier patent, and . . . describes this process in detail of how the information is transferred from one place to the other and updated.”). Mr. Crevelt concludes that Schneier’s description is “complicated,” and from Figure 19 asserts the cost somehow includes a credit multiplier that “could” or “should” change over time. Id. at 158:23– 159:5. Overall, this testimony fails to sufficiently explain or point to in the art would have understood that the Figure 19 cost updating embodiment discloses a time-variable multiplier as required in claim 9.” slip op. at 21

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

    “Discount Credit Pricing Structure The $0.20 discount described by Schneier for purchasing 20 credits, rather than 10 credits, does not have a temporal component. Ex. 1008, 63:31–34. Rather, it describes an option for the user or player to obtain a discount at a particular point in time if the player is willing to purchase 20 rather than 10 credits. Id. Petitioner’s citations to this embodiment do not address the idea of a time component, i.e., “over time,” as required by claim 9. Pet. 31; Pet. Reply 3–7 (citing Ex. 1008, 63:31–34). In this embodiment the $0.30 and $0.50 multipliers are constant, and the user is simply choosing between two existing options at a particular time to potentially take advantage of a $0.20 discount on credits. Comparatively, the $0.30 and $0.50 multipliers are different, but they are not “variable over time,” as required by claim 9. Ex. 1001, 47:38–40.” slip op. at 18

  Patent outcomesUS 10,650,635 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,650,635
• Axon Enterprise, Inc. / Dedrone Holdings, Inc. et al. v. Airspace Defense, Inc.Some claims unpatentable
  PTAB · Oct 6, 2026 · IPR2025-00629 · APJ Scott C Moore · IPR · Final written decision

  Original claim 12 is not unpatentable; substitute claim 37 is added, while substitute claims 21–28 and 30–36 are denied as obvious.

  RulingsFinal written decision

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

    “F.3d at 1279–80, we begin our analysis with the Specification of the ’711 Patent. The Specification indicates when a UAV (such as the recited “reference aerial vehicle”) navigates autonomously, it flies without manual control, and can, for example, track and fly to a target using information captured onboard the vehicle itself. See Ex. 1001, 3:24–28 (“[I]t may not be desirable to manually control the interceptor aerial vehicle to follow the target UAV. In some embodiments, the interceptor aerial vehicle is able to autonomously track and fly to the target UAV using machine vision based on images captured by a camera of the interceptor aerial vehicle.”). The Specification also indicates that “autonomous” means more than just “automatic flight,” and clarifies that autonomous navigation occurs when a UAV that previously received a target location from an external source subsequently turns and flies itself towards the received location. See, e.g., id. at 4:15–17 (disclosing that the detected location of a target may be provided to an interceptor “to allow it to automatically and autonomously fly toward the direction of the detected location”); 15:64–16:3 (automatic and autonomous navigation occurs when an interceptor’s navigation component and/or flight controller receive the location of a target, and adjust the interceptor “to turn and fly towards the received location . . . based on the received location”); 16:49–60 (“For example, a flight direction and/or speed of an interceptor aerial vehicle are automatically and autonomously adjusted based on a location and size of the target within the captured image. . . . This allows the flight path of the interceptor aerial vehicle to be dynamically adjusted to track and follow a moving target.”).” slip op. at 11

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

    “have had reason to combine Beard and Laufer in the manner proposed by Petitioner, the combination would not satisfy the Autonomous Navigation limitation required by claim 12 because Laufer’s autopilot commands are generated by and transmitted from a remote command center (i.e., Laufer’s central controller 115). PO Resp. 15–16. In its Reply, Petitioner does not dispute that Laufer’s autopilot commands are generated by Laufer’s central controller 115, which is remote from the aircraft being controlled. See Reply 13–17. Petitioner asserts, however, that the combination still satisfies the Autonomous Navigation limitation because these autopilot commands are generated without human input. See id. Based on the complete trial record, Patent Owner’s arguments are persuasive. See PO Resp. 15–16; PO Sur-reply 42, 1–6; Ex. 2025 ¶¶ 84–87. The flight of Beard’s UAV 100 under the control of Laufer’s autopilot commands does not satisfy the Autonomous Navigation limitation of claim 12, as we have construed that limitation, because Laufer’s autopilot commands are generated at a location that is remote from UAV 100 (Laufer’s central controller 115.) See, e.g., Ex. 1010 ¶ 40 (“Central controller 115 uses autopilot command module 440 to generate autopilot aircraft commands”), ¶¶ 26, 30 (clarifying that central controller 115 and the controlled interceptor aircraft are separate devices that may communicate through a “wireless connection”), Fig. 4 (depicting “aircraft control commands 475” being generated externally from the depicted “Interceptor Aircraft”); see also Ex. 2025 ¶¶ 95–95. Petitioner never disputes that, in the proposed combination, Laufer’s central controller 115 would remain external to Beard’s UAV 100. See Reply 13–17. Instead, Petitioner relies on its proposed construction of the Autonomous Navigation limitation, which would have encompassed such an arrangement. See id. Our construction of the Autonomous Navigation limitation, which did not adopt Petitioner’s claim construction position, is dispositive of Petitioner’s argument. We thus determine that Petitioner has not shown by a preponderance of the evidence that claim 12 would have been obvious over Beard and Laufer.” slip op. at 15

  • PTAB / AIA Trials › Motions to amend / substitute claimsMotion to amend granted in partGranted in part

    “the legal requirements set forth in 35 U.S.C. § 316(d) and 37 C.F.R. § 42.121. Lectrosonics, Paper 15 at 4, 7–8. For the reasons that follow, we determine that Patent Owner has satisfied this burden. 1. Proposal of a Reasonable Number of Substitute Claims A motion to amend must “propose a reasonable number of substitute claims.” 35 U.S.C. § 316(d)(1)(B); see also 37 C.F.R. § 42.121(a)(3) (“A motion to amend may cancel a challenged claim or propose a reasonable number of substitute claims.”). “There is a rebuttable presumption that a reasonable number of substitute claims per challenged claim is one (1) substitute claim.” Lectrosonics, IPR2018-01129, Paper 15 at 4; see also 37 C.F.R. § 42.121(a)(3). Patent Owner has shown it proposes a reasonable number of substitute claims by proposing a single substitute claim for each of challenged claims 1–4, 8–11, and 13–20. MTA 1–2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 2. Amendments Respond to a Ground of Unpatentability “A motion to amend may be denied where … [t]he amendment does not respond to a ground of unpatentability involved in the trial.” 37 C.F.R. § 42.121(a)(2)(i). Patent Owner has responded to the grounds of unpatentability involved in this proceeding by amending the claims in response to the Petition’s asserted prior art. See MTA 2, 25, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 3. No Enlargement of the Scope of the Claims An amendment may not seek to enlarge the scope of the claims of the patent. 35 U.S.C. § 316(d)(3); 37 C.F.R. §§ 42.121(b)(1)–(b)(2). Patent Owner asserts that the amendments in the Motion do not enlarge the scope of the claims of the patent because each proposed substitute claim “retains all of the limitations of the corresponding challenged claim, and each proposed independent substitute claim adds further limitations.” See MTA 2, Claims App. Petitioner does not argue otherwise. See generally MTA Opp. We determine that Patent Owner meets this requirement. 4. No Introduction of New Matter An amendment may not introduce new matter. 35 U.S.C. § 316(d)(3);” slip op. at 22

  • 112 supportDecided for patent owner

    “Having considered the evidence and argument cited by both parties, we determine there is sufficient written description support for the disputed portions of limitations [37.e1], [37.e3,] and [37.e4]. The ’452 application discloses selecting between groups of processing schemes (e.g., algorithms) depending on a confidence level, where the groups are, for example: high cost, high robustness algorithms; medium cost, medium robustness algorithms; and low cost, low robustness algorithms. See Ex. 2019 ¶¶ 146–147. These schemes or algorithms may be neural networks. See, e.g., id. ¶ 50 (including neural network as a type of algorithm); see also id. ¶¶ 109–110); see generally MTA Opp 1 (not disputing that schemes may be neural networks). Specifically, the ’452 application describes “algorithms that process video frames of one or more video data streams,” and “produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Id. ¶ 141. The ’452 application also discloses the concept of switching between neural networks based on confidence levels. In particular, the ’452 application discloses that a “process cycles through the processing schemes to produce a detection of an object,” for example, where “if the confidence number is higher than an activation number, an action is performed to stop or change a running group (i) and select or switch to group (ii).” Id. ¶ 146. More particularly, “a processing scheme from the group of (i) High cost (low refresh rate), high robustness algorithm[s] can select a cheaper processing scheme from the group of (ii) Medium cost, medium robustness algorithms.” Id. The ’452 application additionally discloses that schemes or algorithms (e.g., neural networks) are applied to individual video frames, and that the confidence levels that determine which neural network will be applied in the future are also derived from individual video frames. For example, as discussed above, the ’452 application describes that “[t]he processing schemes produce a prediction of objects within the video f[r]ame, as well as a confidence number that is a measure of quality for that prediction.” Ex. 2019 ¶ 141 (emphases added). The ’452 application also describes selecting and applying an individual neural network, rather than only selecting and applying a group of processing schemes. For example, as highlighted above, the ’452 application describes that “a processing scheme from the” “High” group “can select a cheaper processing scheme from the” “Medium” group. Id. ¶ 146 (emphases added). In our view, these disclosures, read together, would reasonably convey to one skilled in the art that the inventor had possession of the disputed subject matter described above. See Ariad, 598 F.3d at 1351.” slip op. at 24

  Patent outcomesUS 10,514,711 mixed
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · Graham · Nautilus
  Patents in suitUS 10,514,711
• Sierra Wireless, Inc. / Thales Dis Ais Deutschland GmbH v. Sisvel International S.A.Some claims unpatentable
  PTAB · May 28, 2024 · IPR2020-01099 · APJ Monica S Ullagaddi · IPR · Remand

  On remand, claims 5–7 and 10 are unpatentable as obvious over Chen; claim 8 was not shown unpatentable over the asserted grounds.

  RulingsRemand decision

  • RemandOther

    “with the Federal Circuit. Paper 53. Petitioner subsequently filed a Notice of Cross-Appeal. Paper 54. The Federal Circuit rendered its Decision on October 6, 2023 (Paper 58) and entered its mandate on November 29, 2023 (Paper 57). In its Decision, the Federal Circuit vacated our conclusion regarding the “means for detecting” limitation recited in claims 5 and 10. Sisvel, 82 F.4th at 1364, 1370. The Court ordered that, on remand, we “must conduct the analysis appropriate for Noah group two, including whether any of the protocols are clearly linked or associated with ‘the function recited in the claim,’[ ] and whether they are ‘adequate structure for performing this function.’” Id. at 1370 (citing Noah Systems, Inc. v. Intuit Inc., 675 F.3d 1302, 1313 (Fed. Cir. 2012)). The Court further held that “the Board should have considered the knowledge of a skilled artisan,” and specifically, Dr. Kakaes’s expert testimony, “to assess whether the protocol name sufficiently discloses an understood algorithm corresponding to the means-plus-function limitation.” Id. at 1369. The Court also held that we “must either (1) determine whether the claim[s] [are] indefinite and then whether such indefiniteness renders it impossible to adjudicate a prior-art challenge on the merits, or (2) resolve the prior art challenge to the patentability of the claims despite the potential indefiniteness of the means-plus-function term.” Id. at 1370. After the Federal Circuit issued its mandate, we ordered the parties to brief these issues including “the supported construction of the ‘means for detecting’ claim term, as well as the attendant patentability issues of indefiniteness and impossibility as relevant to this claim term.” Paper 59, 3. Petitioner filed an Opening Brief on Remand (Paper 63, “Rem. Pet. Br.”). Patent Owner thereafter filed a Response to Petition (Paper 64, “Rem. PO” slip op. at 4

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “In its Patent Owner’s Response, Patent Owner states: [A] person having ordinary skill at the time of invention— September 10, 1999—in the relevant art would be one with a bachelor’s degree in electrical engineering or computer sciences and telecommunications networks, along with at least three or more years of practical experience in the field. A combination of more experience in the field and less education or more education and less experience in the field would also suffice. PO Resp. 7 (citing Inst. Dec. 9; Ex. 2001 ¶ 27). In our original Final Written Decision, we determined that: Although there are differences between the contentions of the parties as to the level of ordinary skill in the art, the parties have not informed us of a dispute that needs to be resolved. We do not find it necessary to resolve the differences between the contentions of the parties as to the appropriate level of ordinary skill in the art because the findings and conclusions rendered in this Decision do not turn on either proposed definition. We determine, on this record, that the level of ordinary skill proposed by Patent Owner is consistent with the ’561 patent and the asserted prior art. As such, we adopt Patent Owner’s proposed definition for a person of ordinary skill in the art. Final Dec. 10. Based on our review of the entire record, we are not apprised of nor can we ascertain any reason to deviate from this determination. As such, in this Final Written Decision on remand, we maintain the definition of level of ordinary skill in the art from the original Final Written Decision.” slip op. at 12

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Whether §112(f) applies (Williamson, nonce words)§112(f) appliesDecided for petitioner

    “Claim limitations that include the terms “means” or “means for” are presumed to invoke 35 U.S.C. § 112 ¶ 6. See Williamson v. Citrix Online, LLC, 792 F.3d 1339, 1348 (Fed. Cir. 2015) (en banc in relevant part). Claims subject to 35 U.S.C. § 112 ¶ 6 are construed in a “two-step process,” whereby we “first identify the claimed function,” and then “determine what structure, if any, disclosed in the specification corresponds to the claimed function.” Id. at 1351. Accordingly, the rules governing this inter partes review require that Petitioner “identify the specific portions of the specification that describe the structure, material, or acts corresponding to each claimed function.” 37 C.F.R. § 42.104(b)(3). It is well established that “the corresponding structure for a § 112 ¶ 6 claim for a computer-implemented function is the algorithm disclosed in the specification.” Aristocrat Techs. Austl. Pty Ltd. vs. Int’l Game Tech., 521 F.3d 1328, 1333 (Fed. Cir. 2008) (quoting Harris Corp. v. Ericsson Inc., 417 F.3d 1241, 1249 (Fed. Cir. 2005)); see also EON Corp. IP Holdings, LLC v. AT&T Mobility LLC, 785 F.3d 616, 623 (Fed. Cir. 2015) (“A microprocessor or general purpose computer lends sufficient structure only to basic functions of a microprocessor. All other computer-implemented functions require disclosure of an algorithm.”). The Federal Circuit has held that “[t]he specification can express the algorithm ‘in any understandable terms including as a mathematical formula, in prose, or as a flow chart, or in any other manner that provides sufficient structure.’” Noah, 675 F.3d at 1312 (citing Finisar Corp. v. DirecTV Grp., Inc., 523 F.3d 1323, 1340 (Fed. Cir. 2008) (internal citation omitted)).” slip op. at 13

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “For example, with respect to the CRC protocol, Dr. Kakaes testifies that “CRCs are often referred to as ‘error detecting codes’ as they are typically used[] to detect whether a received data message is or is not erroneous.” Ex. 1002 ¶ 88. Dr. Kakaes further testifies that [t]o use a CRC, the transmitter runs a polynomial division of the data block (before forward error correcting code has been applied, if any) to calculate a “remainder” consisting of a predetermined number of bits, for example 16, which are also called “parity bits,” or “check bits,” or “checksum bits,” or “CRC bits” that are attached to the block to be encoded and then transmitted, in whichever way it may or may not be encoded, punctured, etc. After reception and channel decoding (recall that means determining the “maximum likelihood” message), the receiver then runs the same polynomial division of the received decoded data block (which includes the parity bits) and, if the result does not match the “remainder,” i.e., the “parity bits” are not consistent with the determined message, the decoded data block “fails” the “check,” i.e., is declared as being erroneous. As it turns out such a determination is never wrong. In other words, the “false negative” rate is 0. Id. (emphasis added). With regard to the ARQ protocol, Dr. Kakaes testifies that “[i]n an ARQ scheme, the receiver automatically requests retransmission of a data packet if it is detected to be erroneous, such as through the use of CRC, as discussed above.” Id. ¶ 91.” slip op. at 20

  Patent outcomesUS 6,529,561 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,529,561
• Netflix, Inc. v. Divx, LLCSome claims unpatentable
  PTAB · Feb 3, 2023 · IPR2020-00052 · APJ Iftikhar Ahmed · IPR · Remand

  On remand, claims 1 and 17–19 are unpatentable as obvious over Vehviläinen; the Board did not reach anticipation.

  RulingsRemand decision

  • RemandOther

    “Federal Circuit. Netflix, 2022 WL 2298983 at *1. The Federal Circuit vacated our Decision as to claims 1 and 17–19 and remanded for further consideration of whether claims 1 and 17–19 are unpatentable in light of the court’s construction of a disputed limitation recited in claim 1. Id. at *7. The Federal Circuit affirmed our Decision as to claims 2 and 4, and thus, those claims are not before us on remand. Id. The parties proposed filing a joint brief, with six pages per side, limited to identifying the issues that remain on remand and identifying relevant portions of the existing record, without submitting any new evidence or arguments, and we authorized the joint brief. Paper 87; Ex. 1028. Accordingly, the parties filed a joint brief. Paper 88 (“Joint Brief”). For the reasons discussed below, we conclude, in view of the Federal Circuit’s claim construction and the complete record before us, that Petitioner has shown, by a preponderance of the evidence, that claims 1 and 17–19 are unpatentable.” slip op. at 3

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

    “[t]he words of a claim are generally given their ordinary and customary meaning as understood by a person of ordinary skill in the art when read in the context of the specification and prosecution history.” Thorner v. Sony Comput. Entm’t Am. LLC, 669 F.3d 1362, 1365 (Fed. Cir. 2012) (citing Phillips, 415 F.3d at 1313). “There are only two exceptions to this general rule: 1) when a patentee sets out a definition and acts as his own lexicographer, or 2) when the patentee disavows the full scope of a claim term either in the specification or during prosecution.” Id. (citing Vitronics Corp. v. Conceptronic, Inc., 90 F.3d 1576, 1580 (Fed. Cir. 1996)). Neither of those exceptions apply here, and for the reasons below, we disagree with Patent Owner that the plain and ordinary meaning of “selecting a filter to apply” excludes determining whether or not to apply a given filter. We begin with the claim language at issue. TQ Delta, LLC v. DISH Network LLC, 929 F.3d 1350, 1357 (Fed. Cir. 2019). When considering the language of the claim overall, the usage of “selecting a filter” in the claims does not in any way indicate whether the filter has to be selected from among multiple filters. Claim 1 recites “selecting a filter to apply to determined level of detail.” Ex. 1001, 13:20–22 (emphasis added). Patent Owner argues that “the claim language confirms that ‘selecting a filter’ means choosing from a number of alternative filters, not merely deciding whether or not to apply a filter,” (PO Resp. 34), but we see nothing in the claim language that suggests such a requirement. Patent Owner also points us to claim 19, arguing that selecting is not merely deciding whether to apply a filter, “since that determination is already made in [c]laim 19 by virtue of the initial sub-step of ‘exceed[ing] the threshold.’” Id. Again, we see nothing in claim 19 that suggests the determination of the threshold being exceeded requires a specific manner of filter selection. Instead, similar to claim 1, claim 19 recites: “when the level of detail exceeds the threshold, selecting a filter to apply to predetermined pixels.” Ex. 1001, 16:8–9. Thus, we are not persuaded that the claim language necessarily requires selecting a filter from among multiple filters. slip op. at 14

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

    “because Vehviläinen performs additional analysis before selecting a moderate or high activity filter, it does not teach selecting from among multiple filters. As discussed above, we do not agree with Patent Owner’s claim interpretation, and even if we did, we are persuaded that a person of ordinary skill in the art would have easily modified Vehviläinen’s filter selection to use a single area, e.g., the smooth area of Figure 5A, and a decision branch based on the level of detail for that single area. Vehviläinen discloses that “increasing the amount of selection branches makes the system more adaptive to the nature of the blocking effect but also increases control logic.” Ex. 1004, 8:15–27. Vehviläinen states that “[a] good embodiment,” but of course, “the invention can be utilized with less than three branches.” Id. at 8:18–21. Dr. Bove testifies that a person of ordinary skill in the art “would have been motivated to reduce complexity and the required control logic by using fewer branches, as taught by Vehviläinen, including for example just one branch, particularly for applications running on performance-constrained platforms such as low-end computer processors or mobile platforms, which often had constraints on thermal dissipation, power consumption, and cost.” Ex. 1003 ¶ 120 (citing Ex. 1004, 11:7–22). He further testifies that a person of ordinary skill in the art “would have been motivated to determine the level of detail for just the ‘smooth’ area and then select the smooth filter, if the area is smooth, or the high-activity filter otherwise.” Id. Dr. Bove illustrates that modification with the following pseudocode: if ( IsSmooth (Figure_5A) == TRUE) { Select (SmoothFilter); } else { Select (HighActivityFilter); } Id. He further testifies that such a modification would have been obvious and well within [a person of ordinary skill in the art’s] level of skill, and [such a person] would have had a reasonable expectation of success given that [the] modification involves a simple reordering of elements taught by Vehviläinen, the fact that Vehviläinen expressly teaches the have had with these basic filtering and thresholding techniques. Id. On this aspect, we credit Dr. Bove’s testimony because it is based on the express teachings of Vehviläinen and addresses a straightforward modification in view of those teachings.” slip op. at 33

  • Obviousness (§103) › Objective indicia / secondary considerations › NexusObjective indicia no nexusDecided for petitioner

    “a) Patent Owner Has Not Established that It is Entitled to a Presumption of Nexus We determine that Patent Owner has not demonstrated a nexus between the evidence presented and claims 1 and 17–19. Patent Owner’s arguments and evidence are directed broadly to the DivX6 codec’s deblocking scheme and not specifically to the deblocking aspects covered by the challenged claims. We agree with Petitioner that the claimed features constitute only a small part of the commercial product and the two are far from being coextensive. See Pet. Reply 31 (citing Ex. 1017, 133:10–24; Ex. 1018, 34:4–35:1). As Dr. Bajaj explained, the “DivX [codec] included a lot of things” other than deblocking, and the DivX documentation details “only a fraction of the things that were there in the codec.” Ex. 1017, 133:10–24.” slip op. at 48

  Patent outcomesUS 8,139,651 mixed
  Claim construction§ 103 obviousnesscites Phillips · Graham
  Patents in suitUS 8,139,651
• Siemens Industry Software Inc. v. Synopsys, Inc.Some claims unpatentable
  PTAB · Jan 11, 2023 · IPR2021-01215 · APJ Michael T Cygan · IPR · Final written decision

  Claims 1–5, 7, 8, 11–15, 17, 18, and 21–24 are unpatentable over Yoshimura-based grounds; claims 6, 9, 10, 16, 19, and 20 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level board ownOther

    “B. Level of Skill in the Art Petitioner offers an assessment as to the level of skill in the art as of the time the ’655 patent was filed. Pet. 9. For purposes of this proceeding, Petitioner and Petitioner’s declarant “adopt the [following] definition for the person of ordinary skill in the art”: “a Bachelor of Science degree in Electrical Engineering or Computer Engineering, and has either received academic credits for an ASIC design course or completed at least one year of work experience in the VLSI design, electronic design automation for VLSI, or ASIC design fields.” Id. at 9–10; Ex. 1003 ¶ 78 (Robins Declaration). Patent Owner applies the same definition. Resp. 5. To the extent necessary, we accept this definition because it is supported by the Robins Declaration and consistent with the ’655 patent and the asserted prior art.” slip op. at 7

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

    “Although the phrase “separate from,” is not found in the claims, we look to the language of the claims, the description in the patent disclosure, and the prosecution history to determine what type of separateness is required by the claims. We start with the relied-upon Figure 4 of the ’655 patent, which illustrates a box labeled “Multi-Scenario ECO Database 426” that is near, but not overlapping with or surrounding, boxes labeled “Image 424” through “Image 422” and “Image 420.” Ex. 1001, Fig. 4. The ’655 patent also describes a storage device 408 as “storing scenario images 420– 424 that correspond to different scenarios,” and “can additionally store multi-scenario ECO database 426,” which “can include circuit information for multiple scenarios that can be used to estimate the impact of ECOs in multiple scenarios.” Ex. 1001, 5:9–11, 5:18–21.” slip op. at 9

  • Prior constructionPrior construction adoptedDecided for patent owner

    “determin[e/ing . . . ] an ECO to fix one or more design requirement violations, wherein said determining includes identifying an ECO to fix a design requirement violation in the scenario and checking that ECO against at least some of the multiple scenarios by estimating parameter values based on parameter values stored in the scenario image and the multi-scenario ECO database. Resp. 10 (citing Ex. 2001, 21-24). In reviewing the term, the District Court explained that the multi- scenario ECO database “stores parameters and allows for a quick estimation of an ECO’s impact across multiple scenarios.” Ex. 2001, 19. The District Court further summarized the ’655 patent as describing that a scenario image is “[f]irst” loaded, and if there is a design requirement violation, an ECO is determined for that scenario, and then subsequent scenarios are loaded to check whether the ECO from the first scenario will create new, or exacerbate existing, design violations. Id. (citing Ex. 1001, 4:21–33). However, as recognized by the Court, the process at the cited section is described in the ’655 patent as an “approach [that] may take an impracticably long time to fix design requirement violations in multiple scenarios” due to the long time that is required to load a scenario image. Id. at 24; Ex. 1001, 4:43–47. The Court reasoned that in order to determine an ECO to fix a violation, “determine” must involve “identifying” a possible fix and “checking” whether that fix is suitable. Id. at 23. Thus, the District Court’s construction requires both identifying and checking as part of the claimed determining step. Id. at 23–24. We agree with the District Court’s reasoning, and apply their construction in this proceeding.” slip op. at 11

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

    “Petitioner assertion that Yoshimura’s estimation in step S5 is performed to check an identified ECO is supported by the record. In determining the change to be made (the ECO), Yoshimura uses estimated parameters for the third and fourth corner conditions, calculated in step S5 through the “Hold Margin” equation. Ex. 1007, 6:63–67. Those third and fourth corner conditions are then used to check potential layouts identified in step S6. Id. at 7:18–20 (“In step S6, the automatic EC device 16 searches for a layout that does not cause a timing error under any one of the first to fourth comer conditions from the analysis results of step S4 and step S5.”). In this manner, step S5 sets an initial third corner condition having estimated parameter values that is included, as the initial step, in checking an identified ECO at steps S6–S8. Thus, Yoshimura’s determination of a change to satisfy the corner conditions is, to use Dr. Edward’s phrase, “based on” its third and fourth corner conditions having parameters estimated in step S5. For this reason, we determine that Petitioner has sufficiently shown that Yoshimura discloses the claimed limitation.” slip op. at 20

  Patent outcomesUS 8,407,655 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 8,407,655
• Cradlepoint, Inc. / Honeywell International, Inc. et al. v. Sisvel S.P.A.Some claims unpatentable
  PTAB · Sep 12, 2022 · IPR2021-00580 · APJ Monica S Ullagaddi · IPR · Final written decision

  Claims 1, 2, 6, 7, and 8 are unpatentable as anticipated by and obvious over Sachs; claims 3–5, 9, and 10 were not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “B. Level Of Ordinary Skill In The Art Petitioner contends that: A POSITA at or about the time of the alleged invention (January 5, 2006) would have had a degree in electrical engineering or a similar discipline, with at least three years of relevant industry or research experience, including experience designing or implementing wireless radio systems for data transmission and retransmission. Pet. 35 (citing Ex. 1002 ¶¶ 40–53). Patent Owner contends that a person having ordinary skill at the time of invention—January 5, 2006—in the relevant art would be one a bachelor’s degree in electrical engineering, computer sciences, or telecommunications, along with three to five or more years of practical experience in the field. A combination of more experience in the field and less education or more education and less experience in the field would also suffice. PO Resp. 9 (citing Ex. 2001 ¶ 27). According to Patent Owner, “[a]lthough Patent Owner’s proposed level of skill in the art is similar to Petitioners’ proposal, Patent Owner includes the qualification that a combination of more experience in the field and less education, or more education and less experience in the field would also suffice.” Id. The parties’ contentions as to the level of ordinary skill in the art are similar, and there does not appear to be a dispute that needs to be resolved. We adopt Petitioner’s definition as it appears to be consistent with the specification of the ’396 patent and the cited references. The findings and conclusions rendered in this Decision would not change had we adopted Patent Owner’s definition.” slip op. at 8

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

    “Petitioner proposes “that all claim terms should be accorded their plain and ordinary meaning, as understood by a POSITA and consistent with the specification and file history of the ’396 patent.” Pet. 34–35. Patent Owner “agrees that the claim[] terms should be given their plain and ordinary meaning” and “reserves the right to provide alternate constructions if any of the terms become material to the Board’s decision.” PO Resp. 10. We need not expressly define any claim term in our Decision in order to resolve the issues before us. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (explaining that construction is needed only for terms that are in dispute, and only as necessary to resolve the controversy). We note that the parties both implicitly construe claim limitation 1[c], “stopping the timer when the at least one data block is received from the transmitter while the timer is running, in order to prevent a triggering of a status report before the timer expires” similarly. See e.g., infra § III.D.2.” slip op. at 9

  • Expert testimonyPatent owner expert discountedDecided for petitioner

    “separate ‘reordering procedure,’ to which the timer is tied.” Id. (emphasis added). We agree that the cited evidence in Sachs more closely supports Petitioner’s position that the “timer is stopped when and because the missing PDUs are received,” and not after the occurrence of some additional step in which PDUs in the RLC buffer are shuffled into sequential order. Petitioner persuasively supports its position with, for example, its annotated version of Figure 5, reproduced above, which depicts that the T_reorder timer is stopped when out-of-order PDUs 3 and 4 are received––Sachs does not depict or describe an additional step of reshuffling occurring before the timer is stopped. Pet. 41. Patent Owner’s argument that Sachs teaches “a reordering procedure is performed before any other actions are taken” is unavailing because it is not supported by the cited evidence. In support of this argument, Patent Owner’s Declarant, Mr. Regis J. Bates, Jr., offers similar testimony that “the expiry of the timer in Sachs does not trigger a status report as in the ’396 patent, instead a reordering procedure is performed before any other actions are taken,” but does not explain why the reordering procedure takes place before “any other actions.” Ex. 2001 ¶ 53 (citing Ex. 1003, Figs. 4, 5, Abstract, 8:25–31, 9:11–15) (emphasis added). In his Second Declaration, Mr. Bates adds no further detail or explanation and cites the same portions of Sachs. Ex. 2006 ¶ 29. None of the cited portions of Sachs sufficiently supports a finding that Sachs teaches or suggests that “a reordering procedure is performed before any other actions are taken,” as Patent Owner contends and as Patent Owner’s Declarant testifies. Id.” slip op. at 18

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

    “We clarify that limitations 1[c] and 1[d] cannot both occur in response to the same set of stimuli. Limitation 1[c] can be triggered in response to one set of stimuli and limitation [d] can be triggered in response to a different set of stimuli as is shown in Sachs’s figures. In order for Petitioner to prevail, it need only show one of these mutually-exclusive claim limitations to satisfy the claim, as it contends. Petitioner persuasively shows that, under a first theory, with a first set of stimuli, the timer is stopped before it expires and limitations 1[a], 1[b], and 1[c] are performed as shown in Figure 5 of Sachs. Ex. 1003, Fig. 5. Under a second theory, with a different, second set of stimuli, the timer is allowed to expire and limitations 1[a], 1[b], and 1[d] are performed as shown in Figure 4 of Sachs. Id. at Fig. 4. In Petitioner’s annotated version of Figure 4, PDUs 3 and 4 are not received within the time period set by the T_reorder timer––as such, the T_reorder timer expires and a status report acknowledging PDUs up to 14 and negatively acknowledging PDUs 3 and 4 (i.e., indicating that PDUs 3 and 4 are missing) is sent. Pet. 41. In Petitioner’s annotated version of Figure 5, the T_reorder timer is stopped when out-of-order PDUs 3 and 4 are received within the time period set by the T_reorder timer and as such, the T_reorder timer is stopped before it can expire. Id.” slip op. at 16

  Patent outcomesUS 7,869,396 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,869,396
• Cradlepoint, Inc. / Sierra Wireless, Inc. et al. v. Sisvel International S.A.Some claims unpatentable
  PTAB · Jan 18, 2022 · IPR2020-01099 · APJ Monica S Ullagaddi · IPR · Final written decision

  Claims 1–3 and 9 are unpatentable as obvious over Chen; claims 4–8 and 10 were not shown unpatentable on the instituted grounds.

  RulingsFinal written decision

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

    “Response. Paper 10 (“Prelim. Resp.”). We instituted an inter partes review on all challenged claims on all grounds set forth in the Petition. Paper 11 (“Institution Decision” or “Inst. Dec.”).” slip op. at 2

  • Skill levelSkill level patent owner adoptedDecided for patent owner

    “Although there are differences between the contentions of the parties as to the level of ordinary skill in the art, the parties have not informed us of a dispute that needs to be resolved. We do not find it necessary to resolve the differences between the contentions of the parties as to the appropriate level of ordinary skill in the art because the findings and conclusions rendered in this Decision do not turn on either proposed definition. We determine, on this record, that the level of ordinary skill proposed by Patent Owner is consistent with the ’561 patent and the asserted prior art. As such, we adopt Patent Owner’s proposed definition for a person of ordinary skill in the art.” slip op. at 10

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

    “Petitioner proposes a construction for the term “code rate.” Separately, with regard to means-plus-function limitations recited in claims 5, 9, and 10, Petitioner provides claim construction contentions that identify the specific portions of the specification that describe the structure, material, or acts corresponding to each claimed function, as required by 37 C.F.R. § 42.104(b)(3). Pet. 33–37. Patent Owner does not propose a definition for any claim term nor does it contest any of Petitioner’s proposed constructions. PO Resp. 7–9. In the Institution Decision, we preliminarily construed the means- plus-function claim limitations as set forth in the table below, but determined that it was not necessary for us to construe the claim term “code rate.” Inst. Dec. 11–20 (citing Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017)).5 Based on the 5 Petitioner notes that “construction may be helpful to establishing the inverse and counterintuitive relationship between code rate and redundancy in which an increased code rate (e.g., 1/2) means that fewer redundant bits are transmitted whereas a decreased code rate (e.g., 1/4) means that more determination that we need not expressly construe “code rate” and our preliminary determinations for the means-plus-functions terms for the reasons set forth in our Institution Decision, which we adopt and do not repeat herein, and which are reflected in the table below. Id. at 11–19. Because Petitioner presents further argument for its construction of “means for detecting” in its Petitioner’s Reply––we address that argument below for completeness.” slip op. at 11

  • Claim Construction › Functional claiming / §112(f) means-plus-function › Corresponding structure / algorithm (indefinite if none)Term construed board ownDecided for patent owner

    “We recognize, however, “the testimony of one of ordinary skill in the art cannot supplant the total absence of structure from the specification.” Default Proof Credit Card Sys., Inc. v. Home Depot U.S.A., Inc., 412 F.3d 1291, 1302 (Fed. Cir. 2005); see also Biomedino, LLC v. Waters Techs. Corp., 490 F.3d 946, 950–53 (Fed. Cir. 2007). “The prohibition against using expert testimony in this manner is a direct consequence of the requirement that the specification itself adequately disclose the corresponding structure.” Noah Sys., Inc. v. Intuit Inc., 675 F.3d 1302, 1312 (Fed. Cir. 2012) (citing AllVoice Computing PLC v. Nuance Commc'ns., required that the structure disclosed in the specification be more than simply a general purpose computer or microprocessor.” Aristocrat Techs. Austl. Pty Ltd. v. Int'l Game Tech., 521 F.3d 1328, 1333 (Fed. Cir. 2008). The specification must “disclose an algorithm for performing the claimed function.” Net MoneyIN, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1367 (Fed. Cir. 2008); Aristocrat, 521 F.3d at 1333. The Federal Circuit has held that “[t]he specification can express the algorithm ‘in any understandable terms including as a mathematical formula, in prose, or as a flow chart, or in any other manner that provides sufficient structure.’” Noah, 675 F.3d at 1312 (citing Finisar Corp. v. DirecTV Grp., Inc., 523 F.3d 1323, 1340 (Fed.Cir.2008) (internal citation omitted)). “Simply disclosing software, however, ‘without providing some detail about the means to accomplish the function[,] is not enough.’” Id. (citing Finisar, 523 F.3d at 1340–41 (citation omitted)). In the present proceeding, even assuming, arguendo, that the record sufficiently supports a finding that a POSITA would have known of FEC, CRC, ARQ, and hybrid ARQ protocols, Petitioner has not shown that the specification of the ’561 patent discloses a sufficient algorithm, whether “as a mathematical formula, in prose, or as a flow chart, or any other manner that provides sufficient structure” for the “means for detecting,” including an algorithm for performing any one or more of these protocols. Noah, 675 F.3d at 1312. The ’561 patent discloses “means (224) for detecting a need for retransmission of the received coded data block,” “CCU [Channel Coding Unit] [that] is responsible for channel coding, including forward error coding FEC” as well as detecting the “[t]he need for retransmission . . . by an error errors occurring on the channel with sufficient certainty.” Ex. 1001, code (57), 2:25, 6:64–65, 7:54–59; see id. at Fig. 5, Step 508, 10:41–44. Petitioner has not shown that the ’561 patent presents an algorithm for how the error detection code detects an error, nor explained the circumstances under which the error correcting code cannot correct errors and what constitutes “sufficient certainty.” Id. at 7:54–59. Although the ’561 patent discloses examples of incremental redundancy protocols such as “hybrid FEC/ARQ (Forward Error Correction/Automatic Repeat Request), which uses error correction coding in order to decrease the number of retransmissions,” it does not present an algorithm for implementing the same. Id. at 2:33–37. For the foregoing reasons and based on the entirety of the record developed during trial, we conclude that Petitioner fails to identify sufficient algorithmic structure corresponding to the “means for detecting” recited in independent claims 5 and 10.” slip op. at 15

  Patent outcomesUS 6,529,561 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,529,561
• Cradlepoint, Inc. / Sierra Wireless, Inc. et al. v. Sisvel International S.A.Some claims unpatentable
  PTAB · Jan 18, 2022 · IPR2020-01102 · APJ Aaron W Moore · IPR · Final written decision

  Claims 1–5, 15–20, 30, and 31 are unpatentable as obvious over Qualcomm and TS25.322; claims 6–14 and 21–29 were not shown unpatentable. Substitute claims 32–35, 45–49, 59, and 60 were denied.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner asserts that a person of ordinary skill in the art at the time of the invention “would have a degree in electrical engineering or similar discipline, with at least three years of relevant industry or research experience in telecommunication, including familiarity with cellular communications technologies,” that this person “would also have familiarity with WCDMA,” and that “[t]his definition is approximate,” as “more education may substitute for industry experience or vice versa.” Pet. 12–13 (citing Ex. 1007 ¶¶ 30–34). We adopted Petitioner’s proposal at institution. See Decision 7–8. In its Response, Patent Owner “proposes that a person having ordinary skill at the time of invention—August 23, 2005—in the relevant art would be one with a bachelor’s degree in electrical engineering, computer sciences, or telecommunications, along with three to five or more years of practical experience in the field” and that “[a] combination of more experience in the field and less education or more education and less experience in the field would also suffice.” PO Resp. 8 (citing Ex. 2001 ¶ 27). Patent Owner asserts that “[a]lthough [its] proposed level of skill in the art is similar to Petitioners’ proposal, Patent Owner includes the qualification that a combination of more experience in the field and less education, or more education and less experience in the field would also suffice.” Id. The parties do not argue that the formulation of the level of skill in the art affects any issue in this case, and we maintain our adoption of Petitioner’s formulation, which we find to be generally consistent with the disclosures of the ’443 patent and the prior art, and which includes that “more education may substitute for industry experience or vice versa.”” slip op. at 9

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

    “length indicator” to mean “a single length indicator that provides two pieces of information: (1) that a first data octet of the protocol data unit is a first octet of a first service data unit; and (2) that at least one other octet of the protocol data unit is the last octet of another service data unit.” See Prelim. Resp. 9–10. We agreed with Patent Owner that the specification’s description of a single length indicator that conveys both types of information and the arguments made during prosecution that the claims required a “single LI” or “the same length indicator” to include both types of information were sufficient to support a construction that required a single length indicator to include both pieces of information. See Decision 9. Although it did not propose a construction in the Petition, Petitioner now argues that “the claim language uses the indefinite article ‘a’ to modify ‘length indicator’” and that “[p]recedent is well settled that ‘an indefinite article ‘a’ or ‘an’ in patent parlance carries the meaning of ‘one or more’ in open-ended claims containing the transitional phrase ‘comprising.’” Pet. Reply 5 (citing KCJ Corp. v. Kinetic Concepts, Inc., 223 F.3d 1351, 1356 (Fed. Cir. 2000)). While we agree with Petitioner that “a” may mean “one or more,” that simply means that the addition of more length indicators would not be excluded from the scope of the claim. Petitioner does not explain, and we do not see, how that affects the meaning of “length indicator” itself and, for the reasons argued by Patent Owner and adopted at institution, we maintain the earlier construction of “length indicator” as “a single length indicator that provides two pieces of information: (1) that a first data octet of the protocol data unit is a first octet of a first service data unit; and (2) that at least one other octet of the protocol data unit is the last octet of another service data unit.” See Decision 8; Prelim. Resp. 9–12; PO Resp. 10–13. slip op. at 11

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

    “We also observe that, although Patent Owner characterizes this issue as one based on “teaching away” (see, e.g., PO Resp. 3; PO Sur-Reply 15– 16), the argument is not about teaching away because Patent Owner is not pointing us to any specific teaching in the prior art, or elsewhere, that would counsel against the proposed modification. Patent Owner is not arguing that something in the prior art disparages or discourages the use of one bit of an LI as a flag. Instead, Patent Owner is arguing that one of skill in the art would not pursue the Qualcomm approach because to do so would mean accepting other drawbacks that would flow from the use of the flag. In any event, we credit Patent Owner’s evidence that dedicating a bit of the LI for use as a flag would reduce the length that could be represented by the remaining bits of the LI and cause SDUs to be divided into more PDUs. See, e.g., Ex. 2005 ¶¶ 30, 32. However, the record also shows that use of the flag would provide a specific advantage, as described in Qualcomm. See Ex. 1006, 3; Ex. 1007 ¶ 253. This is the motivation advanced by Petitioner which, notably, Patent Owner does not dispute. We conclude that, even if Patent Owner is correct that the proposal in Qualcomm would reduce the permitted PDU size from 128 octets to 64, the change would merely be something a skilled artisan would need to weigh against the advantages that the Qualcomm technique would provide. Patent Owner may be correct that the reduced lengths would, in the end, render the modified system unsuitable for certain applications or for adoption in a standard. That would not, however, make the modification nonobvious, particularly where the exact change proposed in the combination was suggested by individuals working in the field, as evidenced by Qualcomm itself.7 The record shows that at least some of those working in the field, at the time of the invention, believed that the advantages of Qualcomm’s approach would outweigh the reduced lengths.” slip op. at 20

  • BurdenMixed

    “In TS25.322, the value “0000000” is a predefined, special value used to indicate that “[t]he previous RLC PDU was exactly filled with the last segment of an RLC SDU and there is no ‘Length Indicator’ that indicates the end of the RLC SDU in the previous RLC PDU.” See Ex. 1005, 36–37. However, although Qualcomm specifically contemplates implementing its flag scheme by “[r]e-arrang[ing] special LI values as they are now coded on less number of bits” (Ex. 1006, 4), the Petition did not argue a combination that includes modification of the special LIs for the independent claims. Instead, Petitioner relied on Qualcomm’s proposal to modify ordinary LIs that indicate the end of SDUs. See, e.g., Pet. 71–72 (describing and illustrating modification of the LI that identified the end of SDU 1: “[t]he green modified LI indicates that a first data octet of PDU is a first octet of SDU1 and another octet of the PDU is the last octet of SDU1”); Ex. 1007 ¶¶ 261–262. Petitioner’s argument with respect to these claims is thus not consistent with the argument it advanced for the independent claims from which these claims depend. Petitioner cannot reasonably rely on one type of prior art LI as the “length indicator” of claim 1, but then shift to a different type of prior art LI when addressing the very same “length indicator” recited in a dependent claim. Moreover, Petitioner fails to explain how or why the special LI “0000000” that is used to indicate the layout of the previous PDU could reasonably be used to also indicate the layout of the current PDU in which the LI appears. For example, if the previous PDU did not meet the condition identified by the “0000000” special value, then the LI would not appear in the next PDU even if that next PDU had a first SDU that ended in that PDU. For these reasons, Petitioner has not provided sufficient explanation or argument to establish obviousness of claims 6 and 21.9” slip op. at 28

  Patent outcomesUS 7,894,443 mixed
  Claim construction§ 103 obviousness§ 112 disclosurecites Phillips · KSR · Graham
  Patents in suitUS 7,894,443
• Apple Inc. v. Corephotonics, Ltd.Some claims unpatentable
  PTAB · Nov 2, 2021 · IPR2020-00878 · APJ Bryan F Moore · IPR · Final written decision

  Claims 1, 2, 4–6, 9–15, 17, 18, 20–23, and 25–29 are unpatentable; claims 3, 8, 16, 19, 24, and 30 were not shown unpatentable.

  RulingsFinal written decision

  • BurdenMixed

    “35 U.S.C. § 6. This Final Written Decision is issued pursuant to 35 U.S.C. § 318(a) and 37 C.F.R. § 42.73. For the reasons discussed herein, we determine that Petitioner has shown, by a preponderance of the evidence, that claims 1, 2, 4–6, 9–15, 17, 18, 20–23, and 25–29 of the ’897 patent are unpatentable and that Petitioner has not shown, by a preponderance of the evidence, that claims 3, 8, 16, 19, 24, and 30 of the ’897 patent are unpatentable.” slip op. at 2

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “would include someone who had, at the priority date of the ’897 Patent, (i) a Bachelor’s degree in Physics, Optical Sciences, or equivalent training, as well as (ii) approximately three years of experience in designing multi-lens optical systems. Such a person would have had experience in analyzing, tolerancing, adjusting, and optimizing multi-lens systems for manufacturing, and would have been familiar with the specifications of lens systems and their fabrication. In addition, a POSITA [person of ordinary skill in the art] would have known how to use lens design software such as Code V, Oslo, or Zemax, and would have taken a lens design course. Pet. 6–7 (citing Ex. 1003 ¶¶ 19–20). Patent Owner applied the same level of skill for the purposes of this IPR. PO Resp. 14–15 (citing Ex. 2001 ¶ 19). We regard Petitioner’s formulation of the level of skill as consistent with the prior art before us. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (prior art itself may reflect an appropriate level of skill). Therefore, for purposes of this Final Written Decision, we adopt Petitioner’s assessment of the level of skill in the art because it is consistent with the ’897 patent and the asserted prior art, and we apply it in our analysis below.” slip op. at 11

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

    “Patent Owner argues that no “dispute between the parties in this IPR depends on the construction of EFL, TTL, or of any other claim term [and] submits that the Board should refrain from construing any terms in the patent for the purposes of this proceeding.” PO Resp. 17. Petitioner does not respond to this argument. See generally Pet. Reply. We agree with Patent Owner. If we were to adopt either construction, it would not change the determination made in this Decision. Thus, we decline to construe any claim terms for purposes of this Final Written Decision. See Nidec Motor Corp. v. Zhongshan Broad Ocean Motor Co., 868 F.3d 1013, 1017 (Fed. Cir. 2017) (quoting Vivid Techs., Inc. v. Am. Sci. & Eng’g, Inc., 200 F.3d 795, 803 (Fed. Cir. 1999)) (“[W]e need only construe terms ‘that are in controversy, and only to the extent necessary to resolve the controversy.’”).” slip op. at 10

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

    “unpatentable under 35 U.S.C. § 102 as anticipated by Ogino. Pet. 10–40. Patent Owner does not present arguments related to this ground. See generally PO Resp. For the reasons that follow, we are persuaded that the evidence supports Petitioner’s arguments and thus, Petitioner establishes by a preponderance of the evidence that claims 1, 4, 9–15, 17, 20, and 25–29 are unpatentable under 35 U.S.C. § 102 as anticipated by Ogino.” slip op. at 17

  Patent outcomesUS 10,330,897 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 10,330,897

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.