• Amazon.Com, Inc. / Blizzard Entertainment, Inc. v. Ac Technologies S.A.Some claims unpatentable
  PTAB · Mar 6, 2017 · IPR2015-01802 · APJ Matthew R Clements · IPR · Final written decision

  Claims 1, 3, 5, and 7–15 are unpatentable as anticipated by Rabinovich; Petitioner did not prove claims 1–15 obvious over Rabinovich.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedPetitioner expert creditedDecided for petitioner

    “Electrical Engineering, and two to three years of experience working in the field, or an equivalent level of experience.” Ex. 1005 ¶ 17; Pet. 16. Patent Owner does not challenge this definition or present its own. Accordingly, we credit the testimony of Dr. Ratner regarding the level of ordinary skill in the art, and find that a person of ordinary skill in the art would have had an undergraduate degree in Computer Science or a related field, such as Electrical Engineering, and two to three years of experience working in the field, or an equivalent level of experience. This level of ordinary skill is reflected not only by the information presented by the parties, but also by the prior art of record. Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001) (the prior art itself can reflect the appropriate level of ordinary skill in the art).” slip op. at 9

  • Novelty / Anticipation (§102) › Prior-art status of a reference › Printed publication / public accessibilityPrinted publication establishedDecided for petitioner

    “We agree with and adopt Petitioner’s reasoning and determine Rabinovich to be a printed publication. We credit the unrebutted testimony of Dr. Rabinovich regarding the consistency of his professional practice in 1998 for republication of his AT&T technical memoranda on a webpage that he managed on AT&T’s publicly accessible website. Furthermore, we find the December 1998 IEEE article corroborates the public availability of Rabinovich on that website, and would have been a roadmap, for one of ordinary skill in the art of data management and optimized access to data, to be guided to Rabinovich. See Reply 19–22. As Petitioner points out, Patent Owner’s own declarant states that Rabinovich and the December 1988 IEEE article “are ‘similar[]’ in that they both address ‘problems in network connectivity caused by multiple clients accessing servers.’ (Ex. 2006 at 12).” Id. at 21. Additionally, the passage in the December 1998 IEEE article that cites to Rabinovich refers to an algorithm in Rabinovich for optimizing access to data in order to increase performance. Id. Accordingly, we find that footnote 16 of the IEEE article, which contains the URL to Rabinovich, would have guided one of ordinary skill directly to Rabinovich. We are, therefore, persuaded, that Rabinovich is a printed publication under 35 U.S.C. § 102.” slip op. at 12

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

    “object xs. Rabinovich defines cnt(s,xs) as the “total access count for xs,” which is equal to cnt(xs). Ex. 1006, 11. According to Dr. Ratner, “[t]he metric cnt(s,xs) measures the total number of times in that window that replica xs has been served to a client computer.” Ex. 1005 ¶ 253. As Patent Owner points out, Rabinovich teaches replicating object xs if the ratio of cnt(s,xs) over aff(xs) is greater than m, i.e., a non-zero value. PO Resp. 34; Ex. 1006, 12, Fig. 4. In view of this, we agree with Patent Owner that if cnt(s,xs) has a value of zero, meaning that object x has not been served to any client computer, then the ratio of cnt(s,xs) to aff(xs) will be zero, i.e., less than m, and Rabinovich will not carry out its replication step. This means that Rabinovich will not replicate object xs until xs has been accessed by a client computer at least once, such that the access count for xs is greater than zero. In this regard, we agree with Patent Owner that Rabinovich object xs is not “sen[t], from the at least one data storage device to the another data storage device . . . independently of an access of the at least one client computer” because Rabinovich teaches explicitly that object xs is not sent unless there has been at least one access from the client computer. We are not persuaded by Petitioner’s argument that Rabinovich” slip op. at 18

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

    “pieces” Claim 1 recites “each file including a plurality of individual pieces, the pieces containing parts of the files.” Ex. 1002, 25:67–26:1. The other independent claims recite limitations commensurate in scope. Neither party proposes explicitly a construction of the term “piece.” Petitioner argues that “files are inherently composed of pieces in the form of bits that make up bytes, the bytes themselves being pieces of the file.” Pet. 32. Patent Owner argues that construing “piece” to cover “bits and bytes” of a file “would read out the ‘pieces’ limitation from the claim entirely” (PO Resp. at 29–30) and that “one of ordinary skill in the art would not read the ‘pieces’ limitation of the claim to include bits and bytes” (id. at 30). The claims themselves define “piece” by requiring that a “file” have a “plurality of individual pieces,” but do not establish a lower bound—i.e., a minimum number of bits or bytes—to qualify as a “piece.” Patent Owner identifies no support in the ’680 patent for its contention that “piece” or “pieces” excludes a byte or bytes of a file, relying instead solely on the testimony of Dr. Paul S. Jacobs. Id. (citing Ex. 2006 ¶¶ 38, 39). We are not persuaded by Dr. Jacobs’s conclusory testimony. Because “piece” and “pieces” are limited by the claims only to being a subset of a file and because a byte or collection of bytes of a file is a subset of that file, we are persuaded that the broadest reasonable interpretation of “piece” and “pieces” in light of the Specification of the ’680 patent encompasses a byte or bytes. slip op. at 7

  Patent outcomesUS 7,904,680 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,904,680
• Infobionic, Inc. v. Braemar Manufacturing, LLCSome claims unpatentable
  PTAB · Dec 29, 2016 · IPR2015-01688 · APJ Scott C Moore · IPR · Final written decision

  Claims 1, 2, 4, 6, 7, 11–16, and 19–23 are anticipated by Sellers; claims 3, 5, 8, 9, 17, and 18 are obvious over Sellers and Stutman; claim 10 was not shown unpatentable.

  RulingsFinal written decision

  • Skill levelSkill level petitioner adoptedDecided for petitioner

    “On this record, we adopt Petitioner’s formulation concerning the level of ordinary skill in the art because this formulation more accurately describes the subject matter to which the ’403 Patent pertains. Patent Owner’s formulation is unduly narrow because subject matter of the ’403 Patent is not limited to “ECG telemetry devices” or other “remote monitoring and telemetry devices.” The parties do not dispute that Dr. Stone and Dr. Fernald are both qualified to testify about the perspective of one having ordinary skill in the art, regardless of which formulation we adopt. Tr. 24:22–25:3, 62:6–11. The parties also agree that the issues in this case do not turn on the differences between Petitioner’s and Patent Owner’s proposed formulations regarding the level of ordinary skill in the art. Id. at 24:13–19, 62:12–21. On this record, we find that both Dr. Stone and Dr. Fernald are qualified to offer expert opinions in this case. The factual findings and legal conclusions set forth below would not have differed had we adopted Patent Owner’s formulation regarding the level of ordinary skill in the art.” slip op. at 16

  • Claim Construction › Intrinsic evidence (Phillips canons) › Specification disavowal / 'present invention' languageTerm construed board ownDecided for petitioner

    “The parties agree that a central monitoring device/service is a device/service that “watch[es], keep[s] track of, or check[s]” on something “from a central location.” See PO Resp. 21; Reply 2. On this record, we determine that the claim term central monitoring device/service is not further limited to a device/service that performs monitoring “during a monitoring session” such that it is able to “respond to patient status . . . when it detects evidence of certain physiologic conditions as they occur.” See PO Resp. 20– 22. The Specification uses the term “central monitoring device” in an openended manner, and Patent Owner does not identify any lexicographic definition or disclaimer that would limit this claim term in the manner it proposes. See PO Resp. 19–22; Tr. 38:1–17. The term “central monitoring service” does not appear in the Specification. Though Patent Owner cites a dictionary that defines “monitoring” as “constant checking on a patient’s condition” (Ex. 2021, 930), this definition is overly narrow because the Specification makes clear monitoring may be performed on a periodic basis. See, e.g., Ex. 1001, 3:6–35, 8:63–9:2. Moreover, Patent Owner’s other dictionary definition (Ex. 2020, 752) does not reference a patient, or require detecting “physiologic conditions as they occur.” Dr. Fernald’s testimony regarding this claim term (Ex. 2003 ¶¶ 39– 41) is not persuasive because the portions of the Specification he cites do not limit the term central monitoring device/service in the manner Patent Owner proposes (see Ex. 2003 ¶ 39 (citing Ex. 1001, 3:14–20, 6:42–47, 7:17–25, 7:57–64, 8:28–42); Tr. 38:1–17), and because Dr. Fernald does not adequately account for the dictionary evidence indicating that the claim term “monitoring” does not require constantly observing a patient’s status (see Ex. 2020, 752). We find persuasive Dr. Stone’s testimony that one of ordinary skill would have understood the portions of the Specification cited by Patent Owner and Dr. Fernald to be non-limiting examples. Ex. 1011 ¶¶ 21–34. For the foregoing reasons, on this record, and under the applicable broadest reasonable interpretation standard, we construe central monitoring device/service as a device or service “that watches, keeps track of, or checks from a central location.” 2.” slip op. at 9

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

    “On this record, and under the applicable broadest reasonable interpretation standard, we determine that the claim term “in communication with” encompasses indirect communications (e.g., communication by way of an intermediate component). We further determine that a processor need not generate a message, or respond to a message, in order to be “in communication with” a separate component. The ’403 Patent Specification uses the term “in communication with” in a broad, open-ended manner. See, e.g., Ex. 1001, 2:17–27, 2:42–48. In addition, Patent Owner does not cite any persuasive intrinsic or extrinsic evidence that a person of ordinary skill in the art would have read the claim term “in communication with” to exclude embodiments in which a processor merely receives information. See PO Resp. 40–44. Nor does Patent Owner cite any persuasive intrinsic or extrinsic evidence that the claim term “in communication with” excludes communication between a processor and a component when the processor is acting as an intermediary between that component and some other component. See id. In addition, Dr. Fernald fails to sufficiently support his conclusion that the claim term “in communication with” excludes such forms of communication. See Ex. 2003 ¶¶ 99–103. 4.” slip op. at 12

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

    “Based on the arguments and evidence presented in the Petition and having considered the arguments and evidence presented by both parties during the trial, we are persuaded that Petitioner has established by a preponderance of the evidence that claims 1, 2, 4, 6, 7, 11–16, and 19–23 are anticipated by Sellers. 4.” slip op. at 26

  Patent outcomesUS 6,940,403 mixed
  Claim construction§ 102 anticipation§ 103 obviousnesscites Graham
  Patents in suitUS 6,940,403
• Sandisk Corp. v. Netlist, Inc.Some claims unpatentable
  PTAB · Sep 28, 2016 · IPR2015-01020 · APJ Peter P Chen · IPR · Final written decision

  Claims 17, 22, 24, 26, and 33 are unpatentable as obvious over Takeda, JEDEC, and Connolly; claims 15, 16, 31, and 32 were not shown unpatentable over Takeda and JEDEC.

  RulingsFinal written decision

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

    “We are unpersuaded by Patent Owner’s position. First, the claim language does not recite any physical or structural connection, rather, only “electrically coupling.” Pet. Reply 3, 8–9. In addition, the specification of the ’150 patent does not define explicitly the term “selectively electrically coupling.” Therefore, as in IPR2014-00882 and IPR2014-01011, we refer to its ordinary and customary meaning, as would be understood by one of ordinary skill in the art in the context of the entire disclosure. Translogic Tech., 504 F.3d at 1257. A technical dictionary, the IEEE Dictionary,4 defines “electrical coupling” as “[e]lectrical charges in conductors of a disturbed circuit formed by electrical induction.” Ex. 3001. The IEEE Dictionary explains that “[s]ince the ratio of a conductor’s electrostatic charge to the potential difference between conductors (required to maintain that charge) is the general definition of capacitance, electrical coupling is also called capacitive coupling.” Id. The IEEE Dictionary defines” slip op. at 9

  • Skill levelSkill level board ownOther

    “Based on our review of the ’150 patent and the types of problems and solutions described in the ’150 patent and cited prior art, we conclude a person of ordinary skill in the art at the time of the ’150 patent would have a Bachelor’s degree in electrical engineering, computer engineering, computer science, or related field, and at least one year of work experience, including familiarity with computer memory systems and related industry standards such as JEDEC standards for DRAM memories and memory modules. 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). D. Declarant Testimony” slip op. at 13

  • Expert testimonyPetitioner expert creditedDecided for petitioner

    “To testify as an expert under Federal Rule of Evidence 702, a person need not be a person of ordinary skill in the art, but rather must be “qualified in the pertinent art.” Sundance, Inc. v. DeMonte Fabricating Ltd., 550 F.3d 1356, 1363–64 (Fed. Cir. 2008); see SEB S.A. v. Montgomery Ward & Co., 594 F.3d 1360, 1372–73 (Fed. Cir. 2010) (upholding a district court’s ruling to allow an expert to provide testimony at trial because the expert “had sufficient relevant technical expertise” and the expert’s “knowledge, skill, experience, training [and] education . . . [wa]s likely to assist the trier of fact to understand the evidence”); Mytee Prods., Inc. v. Harris Research, Inc., 439 F. App’x 882, 886–87 (Fed. Cir. 2011) (non-precedential) (upholding admission of the testimony of an expert who “had experience relevant to the field of the invention,” despite admission that he was not a person of ordinary skill in the art). As noted above, Dr. Jagannathan has designed and implemented hardware virtual memory caches, and researched theoretical performance measures of various cache coherency protocols, and has experience in the design of memory systems. We find that, although Dr. Jagannathan may be less experienced than Dr. Sechen in the area of memory module design, he is nonetheless qualified sufficiently to testify about memory systems and memory modules. E. Asserted Obviousness of Claims 15, 16, 31, and 32 in view of Takeda” slip op. at 14

  • ExcludeMotion to exclude, deniedDenied

    “We have reviewed the parties’ contentions on this issue, and exercise our discretion to determine that Petitioner’s Reply and the Jagannathan Supplemental Declaration will not be excluded. We find that, although they may be “inartfully” drafted, the first Jagannathan declaration and Petition sufficiently outlined Petitioner’s position on the function of the chip select signal, namely, that the chip select signal was not itself the logic signal enabling operation of bit-switches. We further find that Petitioner’s Reply and the Supplemental Jagannathan Declaration did not present an entirely new rationale of unpatentability based on Takeda, JEDEC, and Connolly. Cf. Intelligent Bio-Sys., Inc. v. Illumina Cambridge Ltd., 821 F.3d 1359, 1369–70 (Fed. Cir. 2016) (affirming Board’s exclusion of reply brief and declaration that changed unpatentability theory to “an entirely new rationale”). Moreover, there is no dispute that Patent Owner was aware of Petitioner’s position by no later than the Jagannathan deposition, which preceded Patent Owner’s Response by ten days. Patent Owner could have addressed Petitioner’s chip select signal contention, procedurally or substantively, in its Response, but chose to raise the issue only after Petitioner filed its Reply and Supplemental Jagannathan Declaration. Accordingly, Patent Owner had notice of Petitioner’s position and an opportunity to refute that position in its Response.” slip op. at 24

  Patent outcomesUS 7,881,150 mixed
  Claim construction§ 103 obviousnesscites KSR · Graham
  Patents in suitUS 7,881,150
• Motivepower, Inc. v. Cutsforth, Inc.Some claims unpatentable
  PTAB · Sep 9, 2016 · IPR2013-00274 · APJ Trenton A Ward · IPR · Remand

  Claims 1–4, 6–7, and 9–24 are unpatentable as obvious over Bissett, Kartman, and Ohmstedt; claims 5 and 8 were not shown unpatentable.

  RulingsRemand decision

  • RemandFwd mixedOther

    “On January 22, 2016, the Federal Circuit issued a decision vacating and remanding the case to the Board. Cutsforth, Inc. v. MotivePower, Inc., 636 F. App’x 575, 578 (Fed. Cir. 2016) (unpublished) (nonprecedential) (entered herein as Paper 38). The Federal Circuit held “that the Board’s Final Written Decision does not provide enough explanation to support its finding of obviousness.” Id. “When the Board determines that modifications and combinations of the prior art render a claimed invention obvious, the Board must fully explain why a person of ordinary skill in the art would find such changes obvious.” Id. at 578–79. As a result, the Federal Circuit vacated the Board’s determinations that claims 1–24 of the ’018 patent were not patentable and remanded the case to the Board “for proceedings appropriate to the administrative process.” Id. at 579 (citing In re Sang-Su Lee, 277 F.3d 1338, 1346 (Fed. Cir. 2002)). On February 29, 2016, the Federal Circuit issued a formal mandate, returning the case to the Board. Paper 39.” slip op. at 3

  • Additional discoveryAdditional discovery, grantedGranted

    “Patent Owner’s request to submit additional briefing in light of the remand and to discuss the Petitioner’s opposition to such additional briefing. Paper 37, 2. During the conference, Patent Owner indicated that it was seeking additional briefing because the “record is without adequate briefing as to whether one of skill would have made the changes that are contemplated as they relate to a spring that was at issue and relating to claim 5.” Ex. 2064, Transcript of March 29, 2016 conference call, 6:15–18. Patent Owner stated that “a remand typically . . . deserves briefing on the point of the remand to make sure the record is full and there could be a fulsome review of the issues that are thought by the Appellate Court to . . . need[] further review.” Id. at 7:20–25. Patent Owner further argued that additional briefing was needed because the record was “devoid of arguments . . . from either side on this issue”; thus, Patent Owner requested “briefing without evidentiary submission by either party, a page limited briefing of simultaneous submission.” Id. at 8:9–11, 11:12–14.4 We granted Patent Owner’s request to file additional briefing. Paper 37, 3. More particularly, we authorized additional briefing limited to the issue raised by Patent Owner, namely, the design choice issue with respect to claim 5 of the ’018 patent. Id. In accordance with the Board’s Order, both Petitioner and Patent Owner filed their briefs on April 15, 2016. See Paper 40 (“Petitioner Remand Br.”) and Paper 41 (“PO Remand Br.”). Subsequently, Patent Owner requested authorization to file a Reply Brief to address arguments presented in Petitioner’s Remand Brief. The Board granted the request and authorized both parties to file a reply brief. Accordingly, the parties filed reply briefs on April 29, 2016. See Paper 42 (“PO Remand Reply”) and Paper 43 (“Pet. Remand Reply”).” slip op. at 3

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

    “the “specification’s requirement that the mounting block must be fixed to a location.” PO Resp. 8. In support of this argument, Patent Owner relies on Figure 15B of the ’018 patent as depicting that lower mounting block 16, i.e., the “mounting block,” is fixed in place to mount base 41 via bolts 43. Id. at 910. Patent Owner further points to descriptions of various embodiments of the attachment of the “mounting block” to a base or to a location. Id. We determine that neither Figure 15B nor the statements in the specification identified by Patent Owner require the non-moveable, or “fixed,” aspect. Figure 15B does not show that the attachment excludes any ability to adjust the block. Indeed, the bottom surface of the mount is not depicted, leaving us to speculate concerning the shape of mount holes 96, because a round hole would suggest there is no adjustability, while a slotted or elongated hole would suggest adjustability. But see Ex. 1001, Fig. 9 (not cited by Petitioner, but confirming that elongated holes 96 are contemplated). The lack of description and depiction of the shape of the holes compels us to reject Patent Owner’s characterization of Figure 15B as supporting a “fixed” or non-moveable attachment. Furthermore, as for the descriptions of how the mount is attached, the specification uses the word “secure” and describes various embodiments of the attachment, none of which requires non-movability of the mount after the brush holder component is installed. See Ex. 1001, 12:35–36 (bolts and washers “secure the lower mount block 16 to a mount base” (emphasis added)), 14:5658 (“mount holes 96 may include threading or other elements that allow for attachment to a mount base”), 16:2528 (“in other embodiments, a welded, keyed, pinned or other attachment scheme may be used to secure the lower mount block 16 to a mount base” (emphasis added)). In fact, the specification makes a point of not limiting the attachment of the mount to any particular method, fixed or not fixed. See id. at 12:37–41 (“or other attachment scheme may be used to secure the lower mount block 16 to a mount base near a moving conductive surface or in position to move relative to a conductive surface”). Nor does the language of the claim recite any method of attachment that limits the mounting block to something that cannot be adjusted, shifted, re-positioned, or otherwise moved, after attachment to the base.” slip op. at 9

  • Skill levelOther

    “The level of ordinary skill in the art is reflected by the prior art of record. See Okajima v. Bourdeau, 261 F.3d 1350, 1355 (Fed. Cir. 2001); In re GPAC Inc., 57 F.3d 1573, 1579 (Fed. Cir. 1995); In re Oelrich, 579 F.2d 86, 91 (CCPA 1978).” slip op. at 16

  Patent outcomesUS 7,990,018 mixed
  Claim construction§ 103 obviousnesscites Phillips · KSR · Graham
  Patents in suitUS 7,990,018
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01406 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable as obvious; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “Patent Owner’s argument is not persuasive. We agree with Petitioner that 35 U.S.C. § 315(b) applies only to civil actions for patent infringement, and not to an administrative proceeding, including an ITC investigation. See Amkor, Paper 98, slip op. at 6–18; Brinkman Corp. v. A&J Mfg., LLC, Case IPR2015-00056, slip op. at 7–8 (PTAB Mar. 23, 2015) (Paper 10). Although Amkor and Brinkman Corp. are not precedential, we find them instructive and directly on point. In Amkor, the Board determined that “had Congress intended for arbitration, ITC, or other non-judicial proceedings to trigger the time bar of section 315(b), it would have used more encompassing language than ‘Patent Owner’s Action’ and ‘served with a complaint,’ which are harmonious with a civil action.” Amkor, Paper 98, slip op. at 11 (determining that the time bar is limited to being triggered by the service of a complaint in a civil action). A similar decision by the Board in Brinkman Corp. reaches the same result and specifically is directed toward an ITC investigation. Accordingly, we are not persuaded by Patent Owner that Petitioner is barred under 35 U.S.C. § 315(b).” slip op. at 18

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

    “running instance of a computer program or application.” PO Resp. 26‒31. Petitioner accepts Patent Owner’s proposed construction. Pet. Reply 6; Tr. 20:1–4. Petitioner and Patent Owner, however, disagree as to whether a computer with an operating system is a computer program, and, therefore, a “process.” PO Resp. 26–36; Pet. Reply 7–10. In Ancora Technologies, the Federal Circuit explained that “[t]he ordinary meaning of the word ‘program’ in the computer context encompasses both operating systems and the applications that run on them (as well as other types of computer programs)” and “‘to a computer programmer’ a program is merely a ‘set of instructions’ for a computer.” Ancora Techs., Inc. v. Apple, Inc., 744 F.3d 732, 734 (Fed. Cir. 2014). Applying this guidance to the case before us, we agree with Petitioner and construe the term “process” to mean “a running instance of a computer program or application,” where a “computer program” is a set of instructions for a computer that encompasses both operating systems and the applications that run on them. We further note that the ʼ704, ʼ469, and ʼ121 patent specifications interchange the terms “process” and “processing unit.” For example, the specifications explain that a first “processing unit” is “established in the database [] as an active on-line party.” Ex. 1001, 5:29–34. The claims recite the term “process.” Accordingly, our construction is also consistent with the specifications, such that a “process” includes a “processing unit” that is running a program (operating system) or application.” slip op. at 15

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 23

  • ExcludeOther

    “Exhibits 2021, 2028, 2031, 2033, 2034, 2035, 2036, and 2039. Mot. 1. Petitioner specifically argues that Exhibits 2021, 2028, 2031, 2033, 2034, 2035, and 2036 should be excluded because these Exhibits are irrelevant under Federal Rule of Evidence 401. Id. at 1‒5. Petitioner also argues that Exhibits 2028 and 2033 have not been authenticated under Federal Rules of Evidence 901(b)(1). Id. at 1‒3. Petitioner additionally argues that Exhibits 2028, 2033, and 2039 should be excluded as hearsay under Federal Rules of Evidence 802. Id. Because our decision does not rely on any of the challenged Exhibits, we dismiss Petitioner’s Motion to Exclude as moot.” slip op. at 34

  Patent outcomesUS 6,108,704 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,108,704
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01400 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable under §103; the other challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “Patent Owner’s argument is not persuasive. We agree with Petitioner that 35 U.S.C. § 315(b) applies only to civil actions for patent infringement, and not to an administrative proceeding, including an ITC investigation. See Amkor, Paper 98, slip op. at 6–18; Brinkman Corp. v. A&J Mfg., LLC, Case IPR2015-00056, slip op. at 7–8 (PTAB Mar. 23, 2015) (Paper 10). Although Amkor and Brinkman Corp. are not precedential, we find them instructive and directly on point. In Amkor, the Board determined that “had Congress intended for arbitration, ITC, or other non-judicial proceedings to trigger the time bar of section 315(b), it would have used more encompassing language than ‘Patent Owner’s Action’ and ‘served with a complaint,’ which are harmonious with a civil action.” Amkor, Paper 98, slip op. at 11 (determining that the time bar is limited to being triggered by the service of a complaint in a civil action). A similar decision by the Board in Brinkman Corp. reaches the same result and specifically is directed toward an ITC investigation. Accordingly, we are not persuaded by Patent Owner that Petitioner is barred under 35 U.S.C. § 315(b).” slip op. at 18

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

    “Petitioner further contends that WINS discloses that NetBIOS is incorporated into the WINS system and expressly discloses that WINS should be combined with NetBIOS. Id. at 37–38 (citing 198 Ex. 1002 ¶ 81; Ex. 1003, 65). Accordingly, Petitioner concludes that one of ordinary skill in the art would have known about and been motivated to combine the references. Id. Petitioner further contends that a person with ordinary skill in the art would have been motivated similarly to combine WINS and NetBIOS with Pinard because Pinard discloses a telephony application with a graphical user interface that allows a user to establish and manage telephone calls. Id. at 38–39. Petitioner specifically argues that Pinard references Windows 3.1 and WINS references Windows 3.11 and Windows NT, and, therefore, a person with ordinary skill in the art would have known how to adapt the graphical user interfaces in Pinard to the system in WINS. Id. We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by WINS, and Pinard’s program is compatible with a Windows operating system, and, therefore, a person with ordinary skill in the art would have readily combined the disclosures of WINS, NetBIOS, and Pinard.” slip op. at 30

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.”” slip op. at 23

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

    “In Straight Path, the Federal Circuit held that the claim language “is connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 209 Pet. 35–36; 209 PO Resp. 36‒48; 198 Pet. 35–36; 198 PO Resp. 35‒46; 196 Pet. 29; 196 PO Resp. 38‒51. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and therefore must be claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter partes review.” Straight Path, 806 F.3d at 1363. We similarly do not determine whether this claim limitation is supported by the specifications of the ʼ704, ʼ469, and ʼ121 patents. determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 12

  Patent outcomesUS 6,009,469 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,009,469
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01397 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable as obvious; all other challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “2. Section 315(b) Under 35 U.S.C. § 315(b), “[a]n inter partes review may not be instituted if the petition requesting the proceedings is filed more than 1 year after the date on which the petitioner, real party in interest, or privy of the petitioner is served with a complaint alleging infringement of the patent.”” slip op. at 17

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “In Straight Path, the Federal Circuit held that the claim language “is connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 209 Pet. 35–36; 209 PO Resp. 36‒48; 198 Pet. 35–36; 198 PO Resp. 35‒46; 196 Pet. 29; 196 PO Resp. 38‒51. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and therefore must be claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter partes review.” Straight Path, 806 F.3d at 1363. We similarly do not determine whether this claim limitation is supported by the specifications of the ʼ704, ʼ469, and ʼ121 patents. determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 12

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.” Given that the combination of WINS and NetBIOS fails to teach or suggest the claims as construed, we need not reach the remaining arguments presented by Petitioner and Patent Owner.” slip op. at 23

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

    “unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Pinard, and claim 5 of the ’469 patent is unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Palmer. 198 Pet. 37–47, 54‒ 55, 58‒59. For claims 1, 2, and 5, Petitioner provides citations for where each claim limitation is disclosed by WINS and NetBIOS. Id. Petitioner also articulates reasoning with rational underpinnings why a person of ordinary skill in the art at the time of the invention would have combined the teachings of WINS and NetBIOS. Id. See KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We determine the record supports Petitioner’s contentions and adopt Petitioner’s contentions discussed below as our own. Furthermore, we have reviewed the Petition and supporting evidence and determine that Petitioner has shown by a preponderance of the evidence that claims 1, 2, and 5 of the ’469 patent would have been obvious over WINS and NetBIOS. See id.” slip op. at 25

  Patent outcomesUS 6,131,121 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,131,121
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01407 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable over prior art; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “Patent Owner’s argument is not persuasive. We agree with Petitioner that 35 U.S.C. § 315(b) applies only to civil actions for patent infringement, and not to an administrative proceeding, including an ITC investigation. See Amkor, Paper 98, slip op. at 6–18; Brinkman Corp. v. A&J Mfg., LLC, Case IPR2015-00056, slip op. at 7–8 (PTAB Mar. 23, 2015) (Paper 10). Although Amkor and Brinkman Corp. are not precedential, we find them instructive and directly on point. In Amkor, the Board determined that “had Congress intended for arbitration, ITC, or other non-judicial proceedings to trigger the time bar of section 315(b), it would have used more encompassing language than ‘Patent Owner’s Action’ and ‘served with a complaint,’ which are harmonious with a civil action.” Amkor, Paper 98, slip op. at 11 (determining that the time bar is limited to being triggered by the service of a complaint in a civil action). A similar decision by the Board in Brinkman Corp. reaches the same result and specifically is directed toward an ITC investigation. Accordingly, we are not persuaded by Patent Owner that Petitioner is barred under 35 U.S.C. § 315(b).” slip op. at 18

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

    “connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363.” slip op. at 12

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

    “Petitioner further contends that WINS discloses that NetBIOS is incorporated into the WINS system and expressly discloses that WINS should be combined with NetBIOS. Id. at 37–38 (citing 198 Ex. 1002 ¶ 81; Ex. 1003, 65). Accordingly, Petitioner concludes that one of ordinary skill in the art would have known about and been motivated to combine the references. Id. Petitioner further contends that a person with ordinary skill in the art would have been motivated similarly to combine WINS and NetBIOS with Pinard because Pinard discloses a telephony application with a graphical user interface that allows a user to establish and manage telephone calls. Id. at 38–39. Petitioner specifically argues that Pinard references Windows 3.1 and WINS references Windows 3.11 and Windows NT, and, therefore, a person with ordinary skill in the art would have known how to adapt the graphical user interfaces in Pinard to the system in WINS. Id. We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by WINS, and Pinard’s program is compatible with a Windows operating system, and, therefore, a person with ordinary skill in the art would have readily combined the disclosures of WINS, NetBIOS, and Pinard.” slip op. at 30

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.” Given that the combination of WINS and NetBIOS fails to teach or” slip op. at 23

  Patent outcomesUS 6,131,121 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,131,121
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-01398 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent are unpatentable as obvious; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “Patent Owner’s argument is not persuasive. We agree with Petitioner that 35 U.S.C. § 315(b) applies only to civil actions for patent infringement, and not to an administrative proceeding, including an ITC investigation. See Amkor, Paper 98, slip op. at 6–18; Brinkman Corp. v. A&J Mfg., LLC, Case IPR2015-00056, slip op. at 7–8 (PTAB Mar. 23, 2015) (Paper 10). Although Amkor and Brinkman Corp. are not precedential, we find them instructive and directly on point. In Amkor, the Board determined that “had Congress intended for arbitration, ITC, or other non-judicial proceedings to trigger the time bar of section 315(b), it would have used more encompassing language than ‘Patent Owner’s Action’ and ‘served with a complaint,’ which are harmonious with a civil action.” Amkor, Paper 98, slip op. at 11 (determining that the time bar is limited to being triggered by the service of a complaint in a civil action). A similar decision by the Board in Brinkman Corp. reaches the same result and specifically is directed toward an ITC investigation. Accordingly, we are not persuaded by Patent Owner that Petitioner is barred under 35 U.S.C. § 315(b).” slip op. at 18

  • Claim Construction › Intrinsic evidence (Phillips canons) › Plain and ordinary meaning to a POSITAPlain and ordinary meaningDecided for patent owner

    “connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query” slip op. at 12

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server.” slip op. at 23

  Patent outcomesUS 6,108,704 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,108,704
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-00196 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, and 5 of the ’469 patent and claim 3 of the ’121 patent were held unpatentable as obvious; the remaining challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • PTAB / AIA Trials › §315(b) time barNot time barredDecided for petitioner

    “2. Section 315(b) Under 35 U.S.C. § 315(b), “[a]n inter partes review may not be instituted if the petition requesting the proceedings is filed more than 1 year after the date on which the petitioner, real party in interest, or privy of the petitioner is served with a complaint alleging infringement of the patent.”” slip op. at 17

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

    “In Straight Path, the Federal Circuit held that the claim language “is connected to the computer network” has a facially clear meaning, that “the query transmitted to the server seeks to determine whether the second unit is connected at that time, i.e., connected at the time that the query is sent.” Straight Path, 806 F.3d at 1360.11 The Federal Circuit held that the query 11 Petitioner argues that the relevant specifications do not include an embodiment that “guarantee[s]” that an entry in its database is online, and, therefore, Patent Owner’s argument does not distinguish the ’704, ’469, and ’121 patents over the prior art. Addʼl Br. 6‒7. However, such an argument goes towards whether there is written description and enablement support for the claims. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate.” Id. The Federal Circuit further explained that “[i]t is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Id. The Federal Circuit explained, “[w]hen claim language has as plain a meaning on an issue as the language does here, leaving no genuine uncertainties on interpretive questions relevant to the case, it is particularly difficult to conclude that the specification reasonably supports a different meaning. The specification plays a more limited role than in the common situation where claim terms are uncertain in meaning in relevant respects.” Id. at 1361. Accordingly, the Federal Circuit construed the limitation “is connected to the computer network” as “is connected to the computer network at the time that the query is transmitted to the server.” Id. at 1363. Petitioner and Patent Owner argue that the limitations “on-line status” and “is accessible” have the same meaning as “is connected to the computer network.” See 209 Pet. 35–36; 209 PO Resp. 36‒48; 198 Pet. 35–36; 198 PO Resp. 35‒46; 196 Pet. 29; 196 PO Resp. 38‒51. Similar to “is connected to a computer network,” the “on-line status” and “is accessible” of the second process are recited in the present tense, and therefore must be claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter partes review.” Straight Path, 806 F.3d at 1363. We similarly do not determine whether this claim limitation is supported by the specifications of the ʼ704, ʼ469, and ʼ121 patents. determined at the time of the querying whether the second process “is accessible” or selecting of the process having an “on-line status.” Therefore, we construe “on-line status” and “is accessible” as having the same meaning as “is connected to the computer network.”” slip op. at 12

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

    “fail to determine whether a computer or process is connected to the computer network. PO Resp. 48–51. In view of our construction of this claim limitation, we agree with Patent Owner. WINS discloses that once a computer is registered with the WINS server (which is a NetBIOS Name Server (NBNS)) as active and on-line, the WINS server maintains a database of names and addresses as active and on-line by (1) releasing names once a computer is shut down properly, and (2) requiring a renewal time period in which a computer must reregister. Ex. 1003, 62–63, 68–69. WINS discloses that in response to User Datagram Protocol (UDP) name queries, “a mapping in the database does not ensure that the related device is currently running.” Id. at 68. WINS further explains that a “local WINS database should periodically be cleared of released entries and old entries that were registered at another WINS server but did not get removed from this WINS database for some reason.” Id. at 150. In other words, WINS discloses that the WINS database may include entries of computers that are not currently connected to the WINS network. Accordingly, a query to as to whether a second process “is connected to the computer network” in WINS will not determine whether the second process is connected to the WINS network at the time that the query is transmitted to the server. As discussed above in our claim construction analysis above (see Section I.E.1), a query as to whether a process “is connected to a computer network” or has an “on-line” status asks “whether the device ‘is’ connected, not whether it was connected or whether it is still registered as being connected even if that registration information is no longer accurate. It is not a reasonable interpretation of the claim language . . . to say that it is satisfied by a query that asks only for registration information, regardless of its current accuracy.” Straight Path, 806 F.3d at 1360. WINS discloses that the WINS server has information that a process “was” connected to the computer network, and that information may no longer be accurate. See Ex. 1003, 68, 150. As such, we determine that WINS does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein. Similarly, NetBIOS discloses a registration process for resources or nodes to receive a unique name by registering a name. Ex. 1004, 379. During a name query (discovery), a datagram is sent requesting the name and address of another resource. Id. at 396. The NBNS maintains a database of resource names through explicit name deletion, where the node specifies a deletion function and implicit name deletion, which occurs when a node ceases operation. Id. at 379. NetBIOS explains that implicit name deletion “is a frequent occurrence.” Id. Implicit name deletion is managed by assigning nodes a specified lifetime for registered names, where a name is silently released if a node fails to refresh the registered name before the lifetime expires. Id. NetBIOS further discloses a mechanism where the NBNS may correct the information stored after an incorrect response is provided to a requesting node. See id. at 409. However, similar to WINS, NetBIOS discloses that the information stored by the NBNS may be incorrect, and, therefore, will not determine whether a second process is connected to the computer network at the time that the query is transmitted to the server. Therefore, NetBIOS also does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible.” Given that the combination of WINS and NetBIOS fails to teach or suggest the claims as construed, we need not reach the remaining arguments presented by Petitioner and Patent Owner.” slip op. at 23

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

    “unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Pinard, and claim 5 of the ’469 patent is unpatentable under 35 U.S.C. § 103(a) as obvious over WINS, NetBIOS, and Palmer. 198 Pet. 37–47, 54‒ 55, 58‒59. For claims 1, 2, and 5, Petitioner provides citations for where each claim limitation is disclosed by WINS and NetBIOS. Id. Petitioner also articulates reasoning with rational underpinnings why a person of ordinary skill in the art at the time of the invention would have combined the teachings of WINS and NetBIOS. Id. See KSR Int’l Co. v. Teleflex Inc., 550 U.S. 398, 418 (2007) (citing In re Kahn, 441 F.3d 977, 988 (Fed. Cir. 2006)). We determine the record supports Petitioner’s contentions and adopt Petitioner’s contentions discussed below as our own. Furthermore, we have reviewed the Petition and supporting evidence and determine that Petitioner has shown by a preponderance of the evidence that claims 1, 2, and 5 of the ’469 patent would have been obvious over WINS and NetBIOS. See id. Petitioner also contends that claim 3 of the ʼ121 patent is unpatentable under 35 U.S.C. § 103(a) as obvious over WINS and NetBIOS. 196 Pet. 29–38. Petitioner provides citations for where each claim limitation is taught by WINS and NetBIOS. Id. Petitioner also articulates reasoning with rational underpinnings why a person of ordinary skill in the art at the time of the invention would have combined the teachings of WINS and NetBIOS. Id. See KSR, 550 U.S. at 418 (citing In re Kahn, 441 F.3d at 988). We determine the record supports Petitioner’s contentions and adopt Petitioner’s contentions discussed below as our own. Furthermore, we have reviewed the Petition and supporting evidence and determine that Petitioner has shown by a preponderance of the evidence that claim 3 of the ’121 patent would have been obvious over WINS and NetBIOS. See id.” slip op. at 25

  Patent outcomesUS 6,131,121 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,131,121

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.