• Captioncall, LLC v. Ultratec, Inc.Rehearing denied
  PTAB · Dec 1, 2015 · IPR2013-00540 · APJ Barbara A Benoit · IPR · Rehearing

  Denied Patent Owner’s request for rehearing of the Final Written Decision, which held claims 1 and 2 unpatentable, and denied its request for an expanded panel.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “ANALYSIS A request for rehearing must identify specifically all matters the party believes we misapprehended or overlooked, and the place where each matter was addressed previously in a motion, an opposition, or a reply. 37 C.F.R. § 42.71(d). Additionally, Patent Owner, as the party challenging the Final Decision, has the burden of showing the decision should be modified. Id.” slip op. at 2

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Patents / published applications (effective date, provisional support)Reference is prior artDecided for petitioner

    “Ryan1 did not qualify as prior art because it was not enabled (Paper 30, 15– 24 (“PO Resp.”)), we determined that Ryan was enabled prior to the date of invention of the challenged patent in 1997 and, therefore, qualified as prior art to the challenged claims. Final Dec. 18–23.” slip op. at 3

  • ExcludeDecided for petitioner

    “transcript is inadmissible because it does not satisfy the requirements that all testimony, other than uncompelled direct testimony, must be in the form of a deposition transcript, 37 C.F.R. § 42.53(a), and that the witness shall be sworn, 37 C.F.R. § 42.53(f)(1). Req. 7. Therefore, according to Patent Owner, the Yamamoto transcript was “not taken, sought, or filed in accordance with these regulations [and] is not admissible.” Id. (citing 37 C.F.R. § 42.61(a)). Rule 42.53, however, is titled “Taking Testimony” and applies only to testimony taken “during a testimony period set by the Board” for purposes of a particular review proceeding. 37 C.F.R. § 42.53(b); see also 37 C.F.R. § 42.53(c) (providing time limits set by the Board); id. § 42.53(d) (providing notice requirements). As stated in our Final Decision, Petitioner sought to admit the Yamamoto transcript as supplemental information, not as deposition testimony taken in this inter partes proceeding. Final Dec. 31. And based on the parties’ stipulation in district court, we treated the Yamamoto transcript as sworn deposition testimony taken in the district court. Id. at 33–35 (citing Ex. 1062 ¶ 5). Petitioner filed the Yamamoto transcript as supplemental information under 37 C.F.R. § 42.123(b), establishing that the Yamamoto transcript reasonably could not have been obtained earlier and that its consideration was in the interests of justice. Paper 63, 7–8. Therefore, Petitioner’s filing of the Yamamoto transcript complied with Board rules, and we properly relied on it in determining the public accessibility of Yamamoto. See Final Dec. 30– 35.” slip op. at 6

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

    “Specification’s disclosure of “voice pattern.” Req. 10–11. We disagree that our reliance on the Specification’s “Brief Summary of the Invention,” which indicates “a speech recognition computer program which has been trained to the voice pattern of the call assistant,” was improper. See Final Dec. 7 (quoting Ex. 1021, 2:45-48 (emphasis added)). Rather, in our Final Decision, we contrasted the Specification’s use of “voice pattern of the call assistant” in its “Brief Summary of the Invention” with its use of “a voice recognition software package which is specifically trained to the voice of that particular call assistant” in the context of a particular embodiment of the invention shown in Figure 1. Final Dec. 7 (quoting Ex. 1021, 2:45–48, 5:45–48). Based on the evidence in the Specification (including the Specification’s disclosure of “a voice pattern”), we determined that the Specification did not indicate expressly that the voice recognition software is trained to the voice of only that particular call assistant or otherwise indicate that the voice recognition software is trained for the voice of only one call assistant. Final Dec. 7. We concluded that “we will not limit ‘trained to the voice of the call assistant’ to require training to the voice of only one particular call assistant, because the claim language encompasses the invention as disclosed in the Specification—software trained to a voice pattern of a call assistant.” Id. at 8 (citing Ex. 1021, 2:41–49 (“Summary of the Invention”)).” slip op. at 8

  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 6,233,314
• Captioncall, LLC v. Ultratec, Inc.Rehearing denied
  PTAB · Dec 1, 2015 · IPR2013-00550 · APJ William V Saindon · IPR · Rehearing

  The Board denied Patent Owner’s rehearing request, leaving the finding that claim 1 was anticipated by McLaughlin unchanged.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “unpatentability by a preponderance of the evidence. 35 U.S.C. § 316(e). The standard of review for rehearing requests is set forth in 37 C.F.R. § 42.71(d), which states: The burden of showing a decision should be modified lies with the party challenging the decision. The request must specifically identify all matters the party believes the Board misapprehended or overlooked, and the place where each matter was previously addressed in a motion, an opposition, or a reply.” slip op. at 2

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableDecided for petitioner

    “MoneyIn, Inc. v. VeriSign, Inc., 545 F.3d 1359, 1369 n.5 (Fed. Cir. 2008), “for the proposition that anticipation can be based on combining characteristics of various distinct embodiments in a prior art reference.” Req. Reh’g 1 (citing to Final Dec. 20). Patent Owner’s argument mischaracterizes our Final Decision. We pointed to Net MoneyIn in support of our finding that McLaughlin “is describing options for a single system, not separate embodiments.” Final Dec. 20 (emphasis added). Further, Patent Owner overstates the importance of the word “embodiment”; the anticipation inquiry is whether there is “a single prior art disclosure of all elements of a claimed invention arranged as in the claim,” i.e., the word “embodiment” is not itself governing. Net MoneyIn, 545 F.3d at 1359. In this case, Patent Owner has attempted repeatedly to get around McLaughlin’s anticipating disclosure by arguing that the various features are in different “embodiments,” essentially because they are under separate headings. But Patent Owner fails to address convincingly Petitioner’s assertions, backed by convincing testimony, that these features are all part of the same single prior art disclosure and arranged as claimed. In our Final Decision, we reviewed the facts and found that Petitioner had established that all of the elements of the claim were found in a single system in McLaughlin. See generally Final Dec. 15–24.” slip op. at 3

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

    “Patent Owner next alleges that we “explained that a captioned telephone device is a single device that has the features in the body of the claim.” Req. Reh’g 2. Patent Owner mischaracterizes our Final Decision; we made no such statement or implication regarding a “single device.” Our Final Decision already explains why a construction including the phrase “single device” is not commensurate with the broadest reasonable interpretation. See Final Dec. 7–9 (setting forth our construction of the “captioned telephone device”). Specifically, we pointed out that the specification of the ’082 patent instructed one of ordinary skill in the art that “the captured telephone device displays text but need not output any audio signals,” or, in other words, there was no requirement for all features of the claims to be found in one housing or a “single device.” Final Dec. 9 (citing, e.g., an example in the ’082 specification where the speaker/microphone portion (telephone) was depicted as a separate device from the text display portion); Ex. 1021, 9:20–32, Figs. 4–6.” slip op. at 4

  • PTAB / AIA Trials › Constitutional / APA (Arthrex, Oil States, due process)Decided for petitioner

    “Written Decision “with less than a full panel.” Req. 11–13. Panel composition for an inter partes review is specified in 35 U.S.C. § 6(c), which states “[e]ach . . . inter partes review shall be heard by at least 3 members of the Patent Trial and Appeal Board, who shall be designated by the Director.” The Director’s authority under 35 U.S.C. § 6 to designate panels has been delegated to the Chief Judge. See Patent Trial and Appeal Board Standard Operating Procedure 1 (Rev. 14) (May 8, 2015) (“PTAB SOP 1”). As acknowledged by Patent Owner (Req. 11–12), the Final Decision was decided by three administrative patent judges, who are members of the Board. See 35 U.S.C. § 6(a) (indicating that administrative patent judges, along with various members of the United States Patent and Trademark Office, constitute the Patent Trial and Appeal Board). The three administrative patent judges were designated by the Chief Judge according to PTAB SOP 1, titled “Assignment of Judges to Merits Panels, Interlocutory Panels, and Expanded Panels.” The Board, therefore, complied with the statutory requirements for panel composition. Accordingly, we did not issue the Final Decision with less than a “full panel,” as Patent Owner contends.” slip op. at 5

  Claim construction§ 102 anticipation
  Patents in suitUS 7,003,082
• Captioncall, LLC v. Ultratec, Inc.Rehearing denied
  PTAB · Dec 1, 2015 · IPR2013-00541 · APJ Barbara A Benoit · IPR · Rehearing

  The Board denied the Patent Owner’s rehearing request, leaving claims 1–15 unpatentable based on the prior final written decision.

  RulingsRehearing decision

  • RehearingRehearing, deniedDenied

    “ANALYSIS A request for rehearing must identify specifically all matters the party believes we misapprehended or overlooked, and the place where each matter was addressed previously in a motion, an opposition, or a reply. 37 C.F.R. § 42.71(d). Additionally, Patent Owner, as the party challenging the Final Decision, has the burden of showing the decision should be modified. Id.” slip op. at 2

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityReference is prior artDecided for petitioner

    “Ryan1 did not qualify as prior art because it was not enabled (Paper 28, 16– 25 (“PO Resp.”)), we determined that Ryan was enabled prior to the date of invention of the challenged patent in 1997 and, therefore, qualified as prior art to the challenged claims. Final Dec. 23–28.” slip op. at 3

  • ExcludeDecided for petitioner

    “record will be treated as a sworn deposition taken in [the district court proceeding] at which both parties appeared and had the opportunity to question the witness.” Ex. 1062 ¶ 5 (Stipulation Regarding Seiichi Yamamoto). As explained in our Final Decision, we granted Petitioner’s motion to submit the Yamamoto transcript as supplemental information under 37 C.F.R. § 42.123(b) relating to the prior art status of Yamamoto and, after supplemental briefing by the parties, determined the Yamamoto transcript was admissible. Final Dec. 36–41.” slip op. at 6

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

    “Specification’s disclosure of “voice pattern.” Req. 10–12. We disagree that our reliance on the Specification’s “Brief Summary of the Invention,” which indicates “a speech recognition computer program which has been trained to the voice pattern of the call assistant,” was improper. See Final Dec. 8–9 (quoting Ex. 1001, 2:46–48 (emphasis added)). Rather, in our Final Decision, we contrasted the Specification’s use of “voice pattern of the call assistant” in its “Brief Summary of the Invention” with its use of “a voice recognition software package which is specifically trained to the voice of that particular call assistant” in the context of a particular embodiment of the invention shown in Figure 1. Final Dec. 8–9 (quoting Ex. 1001, 2:46– 48, 5:44–47). Based on the evidence in the Specification (including the Specification’s disclosure of “a voice pattern”), we determined that the Specification did not indicate expressly that the voice recognition software is trained to the voice of only that particular call assistant or otherwise indicate that the voice recognition software is trained for the voice of only one call assistant. Final Dec. 9. We concluded that “we will not limit ‘trained to the voice of the call assistant’ to require training to the voice of only one particular call assistant, because the claim language encompasses the invention as disclosed in the Specification—software trained to a voice pattern of a call assistant.” Id. at 10 (citing Ex. 1001, 2:41–49 (“Summary of the Invention”)).” slip op. at 8

  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 5,909,482
• Global Tel*link Corporation v. Securus Technologies, Inc.Some claims unpatentable
  PTAB · Nov 2, 2015 · IPR2014-00810 · APJ Georgianna W Braden · IPR · Final written decision

  Claims 1–3 and 5–7 are unpatentable as anticipated by Silberschatz; Petitioner did not show claims 4 and 8 unpatentable because Silberschatz does not disclose allocating or de-allocating a specific telecommunications resource.

  RulingsFinal written decision

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

    “In this case, the ’637 patent discloses multiple embodiments of telephony and telecommunication resources being allocated and de-allocated, but during prosecution, the applicant removed the modifying limitation of “telecommunication”3 leaving only the term “resource” in the issued claims. Compare Ex. 1004, 60–69 (Application No. 09/072,436) with Ex. 1002, 44–47. The claims, thus, recite “resource” and do not recite “telecommunications resource” nor do they recite “computer resource.” The lack of a limiting term modifying “resource” indicates a scope broader than the scope encompassed by a “resource” that is limited to only a “telecommunications resource” or “computer resource.” Moreover, the Examiner characterized the claims of the application that issued as the ’637 patent as “broader in scope than the claims [in] the parent patent.” Ex. 1002, 95. The Applicant did not dispute the Examiner’s characterization of the claims. Id. at 107. Although the ’637 patent discloses embodiments using “resources,” the ’637 patent does not define explicitly the term “resource.” Therefore, we look to the ordinary meaning of the term as would be understood by one of 3 The term “telecommunication” was recited in the proposed claims of earlier-filed parent Application No. 09/072,436. The ’637 patent claims priority to patent Application No. 09/072,436. See Ex. 1002, 1. ordinary skill in the art. A technical dictionary, IEEE Dictionary4, defines “resource” as “[a]ny capability that must be scheduled, assigned, or controlled by the underlying implementation to assure non[-]conflicting usage by processes.” Id. at 976. As shown by the dictionary definition, one of ordinary skill in the art would understand “resource” is not limited to a telecommunications resource or a computer resource.5 Thus, the ordinary meaning of “resource” is consistent with the term’s use in the ’637 patent, which readily interchanges the term “resources” with “components” and “capability” in the context of computer telephony resources. Ex. 1001, 1:27–29. For example, in one embodiment in the ’637 patent, the telecommunication “resource” is a telephony line card that is coupled to a telephone. Id. at 9:12–15. In other embodiments, the telecommunication “resources” are components or ports coupled via a data bus to a central processing unit system, a data port system, a video system, a network system, a storage controller, and a high speed communication system. Id. at 8:1–27, 10:64–11:10, 11:14–22. In every embodiment in the ’637 patent, 4 IEEE 100: The Authoritative Dictionary of IEEE Standards Terms: Seventh Edition (Standards Information Network, IEEE Press ©2000) (Ex. 3001) (hereinafter “IEEE Dictionary”). 5 Petitioner’s Declarant, Dr. Forys, testified on cross-examination that a person of ordinary skill in the art would have telecommunications experience because all of the embodiments in the ’637 patent are directed to telecommunications. Ex. 2002, 47:2–14. Based on this testimony, Patent Owner argues that the ’637 patent would be understood by a person of ordinary skill in the art in the context of a telecommunications systems. PO Resp. 8–9. We agree the ’637 patent may have been understood in the context of a telecommunications system, however, that does not indicate that a skilled artisan would have understood “resource” to have been limited to only a telecommunications resource. resources are a component or capability of a system that is managed (i.e., identified, allocated, de-allocated) by some module in the service kernel. Id. at 9:27–39, 10:10–14, 10:64–11:10, 11:14–22. Accordingly, we do not agree with Patent Owner’s position, because” slip op. at 11

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “Petitioner’s Declarant, Dr. Forys, opines that a person of ordinary skill in the art relevant to the ’637 patent “would have a B.S. degree in Electrical Engineering, Computer Science, or an equivalent field and one year to two years of industry experience in telecommunications.” Ex. 1003 ¶ 32. Patent Owner does not disagree with Petitioner’s assertions regarding the level of skill in the art, nor does Patent Owner’s Declarant, Dr. Akl, offer any contrary explanation regarding who would qualify as a person of ordinary skill in the art relevant to the ’637 patent. PO Resp. 9–10; Ex. 2003 ¶ 42. Based on our review of the ’637 patent, the types of problems and solutions described in the ’637 patent and cited prior art, and the testimony of Petitioner’s Declarant, we conclude that a person of ordinary skill in the art at the time of the claimed invention would have had at least a Bachelor’s degree in Electrical Engineering, Computer Science, or a similar discipline, and at least one year of work experience in telecommunications technologies. We further note that the applied prior art reflects the appropriate level of skill at the time of the claimed invention. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001).” slip op. at 16

  • Novelty / Anticipation (§102) › Anticipation standard (single reference, every element)UnpatentableNot shown unpatentableMixed

    “We do agree with Patent Owner’s argument, however, with regards to dependent claims 4 and 8, which require the return of “the allocated telecommunications resources to control of the management module.” Ex. 1001, 21:52–22:6, 22:44–52; see supra, Section II.A.3. Petitioner has not indicated a disclosure in Silberschatz that demonstrates the allocation or de-allocation of a specific telecommunications resource. Therefore, we determine that Petitioner has failed to meet its burden to show Silberschatz anticipates dependent claims 4 and 8.” slip op. at 21

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “We do not agree with Patent Owner’s position, because Petitioner identifies CPU time as a specific resource that is requested (Pet. 23–24), allocated (id. at 25), used (id. at 25), and de-allocated (id. at 26). We credit the testimony of Dr. Forys, who explains how and where Silberschatz discloses each element of the challenged claims. See Ex. 1003 ¶¶ 64–80. Specifically, Dr. Forys testifies regarding the request, allocation, use, and de-allocation of a single type of resource (e.g., CPU time), thereby meeting the limitations of the challenged claims. Id. ¶¶ 74–80. Although Patent Owner correctly points out that Petitioner discusses multiple types of resources, we do not agree that Petitioner discusses or applies the disclosure of Silberschatz inconsistently, because Petitioner at least consistently identifies CPU time as a resource requested, allocated, used, and de-allocated.” slip op. at 21

  Patent outcomesUS 7,324,637 mixed
  Claim construction§ 102 anticipationcites Graham
  Patents in suitUS 7,324,637
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 22, 2015 · IPR2015-01050 · APJ Bryan F Moore · IPR · Institution

  The Board denied institution on all challenged claims because the means-plus-function claims lacked sufficient structural disclosure and Feldmeier did not establish claim 63’s forwarding-permission limitation.

  RulingsInstitution decision

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

    “Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a); see 37 C.F.R. § 42.108. Upon consideration of the Petition and the Preliminary Response, we conclude the information presented does not show a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of any of the challenged claims of the ’853 patent.” slip op. at 2

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

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

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

    “Patent Owner argues, “Feldmeier’s packet forwarding is not the same as determining forwarding permissions (e.g., whether a packet is restricted from being transmitted from a selected source device to a selected destination device.)” Prelim. Resp. 31–32. Patent Owner further argues Feldmeier does not process a packet based on a forwarding permission. Id. We agree. Petitioner purports to show that “matching one or more characteristics of said packet with one or more access control specifiers,” recited in claim 63, results in “permission” to forward a packet. Petitioner states that “the information obtained from the CAM lookup governs the decision of whether to route or discard the packet.” Pet. 40 citing (Ex. 1003 ¶ 106). We note that Feldmeier discloses that “[a]ddress filtering is a process similar to address translation, except that rather than retrieving the data associated with an address, the process simply determines whether the address exists in a table of addresses.” Ex. 1005, 1:19–22. Feldmeier further discloses that “[t]he term address translation, as used herein, includes both address translation and address filtering operations.” Id. at 1:22–24. Also, as cited by Petitioner (Pet. 40), “Demultiplexer 1430 routes the packet . . . to either output packet queue 1450 or to discard line 1460 depending on the signal received from network address lookup 1440.” Ex. 1005, 13:24– 27. Finally, “[n]etwork address lookup 1440 is an apparatus for performing hierarchical address translations according to an embodiment of the invention.” Id. at 13:19–22. These passages suggest that a translation that yields no match (filtering) results in the packet being sent to the discard line. In contrast, the Specification supports that a successful match leading to a forwarding permission is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input or output permission by, among other things, “determining all of the successful matches”). Based on the above passages, Petitioner has not shown evidence that an affirmative match in Feldmeier results in a permission of packet forwarding, as required by claim 63. For the reasons stated above, we determine Petitioner has not shown sufficiently that Feldmeier discloses all of the limitations of independent claim 63. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that claim 63 is anticipated by Feldmeier.” slip op. at 14

  Claim construction§ 102 anticipationcites Phillips
  Patents in suitUS 7,023,853
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 22, 2015 · IPR2015-01049 · APJ Bryan F Moore · IPR · Institution

  The Board denied institution on all challenged claims because Petitioner did not show a reasonable likelihood of prevailing on any asserted ground.

  RulingsInstitution decision

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

    “(“Prelim. Resp.”). Institution of an inter partes review is authorized by statute when “the information presented in the petition . . . and any response . . . shows that there is a reasonable likelihood that the petitioner would prevail with respect to at least 1 of the claims challenged in the petition.” 35 U.S.C. § 314(a); see 37 C.F.R. § 42.108. Upon consideration of the Petition and the Preliminary Response, we conclude the information presented does not show there is a reasonable likelihood that Petitioner would prevail in establishing the unpatentability of any of claims 1, 2, 5, 7– 10, 12–16, 18–22, 25, and 28–31 of the ’577 patent and, therefore, deny the Petition for inter partes review..” slip op. at 2

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

    “We note that Feldmeier discloses that “[a]ddress filtering is a process similar to address translation, except that rather than retrieving the data associated with an address, the process simply determines whether the address exists in a table of addresses.” Ex. 1005, 1:19–22. Feldmeier further discloses that “[t]he term address translation, as used herein, includes both address translation and address filtering operations.” Id. at 1:22–24. Also, as cited by Petitioner, “Demultiplexer 1430 routes the packet . . . to either output packet queue 1450 or to discard line 1460 depending on the signal received from network address lookup 1440.” Id. at 13:24–27. Finally, “[n]etwork address lookup 1440 is an apparatus for performing hierarchical address translation[s] according to an embodiment of the invention.” Id. at 13:19–22. These passages suggest that a translation that yields no match (filtering) results in the packet being sent to the discard line. In contrast, the Specification supports that a successful match leading to a forwarding permission is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by, among other things, “determining all of the successful matches”); see also Prelim. Resp. 24 (“Feldmeier never discloses that its firewall device makes a decision to permit or deny a packet based on a matching entry in the network address lookup.”). Based on the above passages, Petitioner has not shown that, even under our broad construction of access control, an affirmative match in Feldmeier can result in a modification or a denial of packet forwarding, as required by claim 1.” slip op. at 11

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

    “to a forwarding permission is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by, among other things, “determining all of the successful matches”); see also Prelim. Resp. 24 (“Feldmeier never discloses that its firewall device makes a decision to permit or deny a packet based on a matching entry in the network address lookup.”). Based on the above passages, Petitioner has not shown that, even under our broad construction of access control, an affirmative match in Feldmeier can result in a modification or a denial of packet forwarding, as required by claim 1.” slip op. at 11

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

    “In a computer network for transmitting information, messages can be restricted from being transmitted from selected source devices to selected destination devices. In known computer networks, this form of restriction is known as “access control” and is performed by routers, which route messages (in the form of individual packets of information) from source devices to destination devices. Ex. 1001, 1:4–10. Patent Owner also cites certain dictionary definitions. Id. at 10–11. Patent Owner states that “modifying” transmission is “nowhere in the record.” Id. Nonetheless, Patent Owner does not explain why the embodiment cited by the Petitioner above is not relevant to construing the claims. Because the embodiment cited by Petitioner suggests that access control may be used to change the destination address of a packet, we apply a broader definition than proposed by Patent Owner. We find the broadest reasonable construction of “access control” to include restrictions or modifications on the intended destination address to which a packet is to be transmitted.” slip op. at 8

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 6,377,577
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 19, 2015 · IPR2015-00973 · APJ Bryan F Moore · IPR · Institution

  The Board denied institution on all challenged claims because the petition did not show a reasonable likelihood of prevailing on any asserted ground.

  RulingsInstitution decision

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

    “For the reasons stated above, we determine Petitioner has not shown sufficiently that Hendel discloses all of the limitations of independent claim 1. Accordingly, the information presented does not show a reasonable likelihood that Petitioner would prevail in showing that independent claim 1, or claims 2, 5, 7–10, 12–16, 18–22, 25, 28, 29, and 31 that depend therefrom, are anticipated by Hendel.” slip op. at 11

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

    “patent according to their broadest reasonable construction in light of the specification of the patent in which they appear. 37 C.F.R. § 42.100(b); see also In re Cuozzo Speed Techs., LLC, 793 F.3d 1268, 1278–79 (Fed. Cir. 2015). Consistent with the broadest reasonable construction, claim terms are presumed to have their ordinary and customary meaning as understood by a person of ordinary skill in the art in the context of the entire patent disclosure. In re Translogic Tech., Inc., 504 F.3d 1249, 1257 (Fed. Cir. 1 U.S. Patent No. 6,081,522, filed June 30, 1997, issued June 27, 2000 (Ex. 1007, “Hendel”). 2 U.S. Patent No. 5,938,736, filed June 30, 1997, issued Aug. 17, 1999 (Ex. 1008, “Muller”). 3 U.S. Patent No. 5,867,495, filed Nov. 18, 1996, issued Feb. 2, 1999 (Ex. 1019, “Elliot”). 2007). An inventor may provide a meaning for a term that is different from its ordinary meaning by defining the term in the specification with reasonable clarity, deliberateness, and precision. In re Paulsen, 30 F.3d 1475, 1480 (Fed. Cir. 1994). Petitioner proposes constructions for the terms “access control,” “associative memory,” “packet label,” “responsive,” and “megapacket.” Pet. 5–9. We determine that the terms “associative memory,” “packet label,” “responsive,” and “megapacket” do not require express construction for purposes of our Decision.” slip op. at 6

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

    “As to the term “access control,” Petitioner asserts that “[a] person of skill in the art would have understood ‘access control’ to encompass restrictions or modifications of the transmission of a packet.” Pet. 5. Petitioner relies on the following passage from the Specification: [T]he invention can be used to augment or override routing decisions otherwise made by the router, using the access control element 120. In addition to specifying the packet 130 is to be dropped or forwarded to the higher-level processor, the access control element 120 can alter the output interface, which was selected by the routing element 110, to another selected output interface. The invention can thus be used to implement QOS (quality of service), and other administrative policies. Ex. 1001, 6:9–18. Patent Owner asserts “the plain and ordinary meaning of ‘access control’ is ‘restriction of packets from being transmitted from selected source devices to selected destination devices.’” Prelim. Resp. 10. Patent Owner relies on the following passage from the Specification (id.): In a computer network for transmitting information, messages can be restricted from being transmitted from selected source devices to selected destination devices. In known computer networks, this form of restriction is known as “access control” and is performed by routers, which route messages (in the form of individual packets of information) from source devices to destination devices.” slip op. at 7

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

    “‘discarding’ packets does not concern access control,” that Hendel’s “packets are only filtered or discarded as part of the packet forwarding process when there is a problem with the packet,” and thus, “Hendel refers to such filtering or discarding occurring when packets are ‘ill-formed’ or have ‘no appropriate destination[s]’ or ‘unsupported’ headers.” Prelim Resp. 21–22 (citing Ex. 1007, 8:39–40, 10:51–52, 13:9–11). We agree. Although we did not adopt Patent Owner’s proposed construction of the claim term “access result,” Patent Owner nevertheless makes a salient argument. We find Petitioner has not shown that the filtering decision is done “in response to [] at least one selected match” as required by claim 1. The Specification supports that a successful match leading to an access result is contemplated by the claims. Ex. 1001, 7:1–12, 27–39 (determining an input [or output] permission by, among other things, “determining all of the successful matches”); see also Prelim. Resp. 21 (“the ‘matching entry,’ at most, provides a destination for Hendel’s system to forward the packet . . . [but,] where a destination is found, the packet is forwarded; there is no disclosure to generate any access result to possibly restrict access to the destination.”). Neither Petitioner, nor Petitioner’s Declarant, has tied an actual match in Hendel to a decision whether to forward the packet or make some modification to the intended transmission of the packet.” slip op. at 11

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 6,377,577
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 19, 2015 · IPR2015-00976 · APJ Bryan F Moore · IPR · Institution

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

  RulingsInstitution decision

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

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

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

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

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

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

  Claim construction§ 102 anticipation
  Patents in suitUS 7,023,853
• The United States Postal Service (Usps) / The United States Of America, As Represented By The Postmaster General v. Return Mail, Inc.All claims unpatentable
  PTAB · Oct 15, 2015 · CBM2014-00116 · APJ Kevin F Turner · CBM · Final written decision

  Claims 39–44 are unpatentable under § 101 because they claim the abstract idea of relaying mailing address data without significantly more; anticipation by 1997 ACS was not shown.

  RulingsFinal written decision

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

    “II. ANALYSIS A. Claim Construction We construe all terms, whether or not expressly discussed here, using the broadest reasonable construction in light of the ’548 Patent specification. See 37 C.F.R. § 42.300(b); see also In re Cuozzo Speed Techs., LLC, 93 F.3d 1268, 1278–80 (Fed. Cir. 2015) (“Congress implicitly approved the broadest reasonable interpretation standard in enacting the AIA,” and “the standard was properly adopted by PTO regulation.”). During the pre-trial stage of this proceeding, the parties submitted their constructions for specific claim terms and we adopted constructions consistent with the constructions adopted by the U.S. Court of Federal Claims (Ex. 1011). Dec. 8–10. Return Mail does not dispute the constructions adopted. PO Resp. 16–27. Upon review of the parties’ explanations and supporting evidence before us, we discern no reason to modify our claim constructions set forth in the Decision on Institution with respect to these claim terms. Dec. 8–10. For convenience, our claim constructions are reproduced in the table below:” slip op. at 6

  • Patent Eligibility (§101) › Alice/Mayo step one — 'directed to'Step1 directed to exceptionIneligibleUnpatentable

    “USPS has shown, by a preponderance of the evidence, that claim 39, as a whole, is directed to the processing of returned mail items, involving decoding information, obtaining an updated address, and electronically transmitting that updated address to a transferee. USPS has shown that the steps are directed to the abstract idea of relaying mailing address data, with the inclusion of an electrical transmission step. Regarding whether claim 39 includes limitations that amount to significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14

  • Patent Eligibility (§101) › Alice/Mayo step two — inventive conceptStep2 no inventive conceptIneligibleUnpatentable

    “significantly more than the abstract idea of relaying mailing address data, per our claim construction, USPS has shown that the “decoding” step is “deciphering information into useable form,” but that does not necessarily bring it out of the realm of processes performed in the past by human beings. In fact, all of the claimed steps could be performed in the human mind, with the exception of the transmitting step. Additionally, USPS has shown that what the data might be deemed to represent to the human mind — e.g., “information indicating whether the sender wants a corrected address to be provided for the intended recipient” — does not substantially affect the underlying structure or function of the claim or any machine on which it is carried out. Consistent with USPS’s position, the ’548 Patent disclosure does not describe any particular hardware to perform the steps recited in claim 39, but refers merely in broad terms to generic computer hardware and software.” slip op. at 14

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

    “deciding between the proffered constructions of “[d]ecipher information into useable form” and “[c]onvert information into useable form,” the court concluded that “using the terms ‘decipher’ and ‘deciphered’ more closely follow the customary meaning of the terms and reflects the claim language. This is because decoding must operate on encoded data,” which is recognized in the term “decipher” but not in “convert.” Ex. 1011, 22–23. USPS contends that “the carrier converts into intelligible form the participant code and endorsement thereby performing the claimed ‘decoding.’” Pet. 45. However, we find no support within 1997 ACS that the carrier decodes or deciphers the participant code or endorsement because the carrier (a person) is merely reading those indicators. The indicator “ADRESS SERVICE REQUESTED” is merely read and there is no disclosure that the carrier decodes the participant code or the keyline. We disagree with Dr. Lubenow that the plain-English endorsements “meet the plain and ordinary meaning of the term ‘code.’” Ex. 1028 ¶ 18. As such, we are not persuaded that the carrier in 1997 ACS acts to decode encoded data on the returned mail items.” slip op. at 24

  Patent outcomesUS 6,826,548 unpatentable
  Claim construction§ 101 eligibility§ 102 anticipationcites Alice · Mayo
  Patents in suitUS 6,826,548
• Arista Networks, Inc. v. Cisco Systems, Inc.Institution denied
  PTAB · Oct 6, 2015 · IPR2015-00974 · APJ Matthew R Clements · IPR · Institution

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

  RulingsInstitution decision

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

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

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

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

  • Skill levelOther

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

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

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

  Claim construction§ 102 anticipation§ 103 obviousness
  Patents in suitUS 7,224,668

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.