• 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
• LG Electronics, Inc. / Toshiba Corp. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · May 9, 2016 · IPR2015-00209 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 11, 12, 14, 16, 19, 22, 23, 27, 30, and 31 of the ’704 patent; claims 3, 6, 9, 10, 14, 17, and 18 of the ’469 patent; and claims 4, 6–14 of …

  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 petitioner

    “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) › 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” slip op. at 23

  • Obviousness (§103) › Motivation to combine / reasonable expectation of successMotivation 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

  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-00198 · 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 WINS and NetBIOS; the other challenged claims were not shown unpatentable.

  RulingsFinal written decision

  • 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

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

    “year after Petitioner was served a complaint filed with the United States International Trade Commission (“ITC”). PO Resp. 4‒6. Petitioner responds that § 315(b) only applies to service of a complaint in a civil action and not to administrative proceedings such as an ITC investigation. Pet. Reply 5‒6 (citing Alcon Research, Ltd. v. Dr. Joseph Neev, Case IPR2014-00217, Paper 21, 9 (PTAB May 9, 2014); Amkor Tech., Inc. v. Tessera, Inc., Case IPR2013-00242, Paper 98, slip op. at 10–12 (PTAB Jan. 31, 2014)). Petitioner specifically argues that the Board has rejected similar arguments as those raised by Patent Owner and held that § 315(b) only covers civil actions brought in federal district court. Paper 17, 3‒5 (citing Amkor, Paper 98, 7–8). Patent Owner argues that Amkor is directed to administrative proceedings such as arbitration, and any discussion in Amkor regarding an ITC investigation is not relevant. Prelim. Resp. 13, n. 1. 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) › 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.”” 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,009,469 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,009,469
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · Mar 4, 2016 · IPR2015-01006 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, 5, and 10 of the ’469 patent are unpatentable; the remaining challenged claims of the ’704, ’469, and ’121 patents were not shown unpatentable.

  RulingsFinal written decision

  • 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 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 the query is transmitted to the server.” Id. at 1363.” slip op. at 11

  • BurdenNot shown unpatentable

    “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual 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. 1014, 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 Microsoft Manual, 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 Microsoft Manual 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 19

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

    “Petitioner contends that “WINS is an implementation of NetBIOS” and, therefore, Petitioner contends that “one having skill in the art would have known about and been motivated to combine Microsoft Manual with NetBIOS.” Id. at 34 (citing 67 Ex. 1004 ¶¶ 88–89). We are persuaded by Petitioner that the combination is reasonable because Microsoft Manual demonstrates that Microsoft TCP/IP has combined the elements of NetBIOS and Microsoft Manual in the same manner in which Petitioner proposes to combine NetBIOS and Microsoft Manual. See 67 Ex. 1012, 3, 11. Microsoft Manual discloses that Microsoft TCP/IP for Windows NT provides support for application interfaces, including NetBIOS for establishing logical names and sessions on the network. Id. at 11. Microsoft Manual describes that “[w]hen WINS servers are in place on the network, NetBIOS over TCP/IP resolves names on a client computer by communication with the WINS server.” 67 Pet. 34 (quoting 67 Ex. 1012, 62). We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by Microsoft Manual, and a person with ordinary skill in the art would have readily combined the disclosures of Microsoft Manual and Microsoft Manual.” slip op. at 25

  Patent outcomesUS 6,131,121 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,131,121
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · Mar 4, 2016 · IPR2015-01011 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, 5, and 10 of the ’469 patent are unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.

  RulingsFinal written decision

  • 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 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 the query is transmitted to the server.” Id. at 1363. 11 Petitioner argues that the relevant specifications do not include an embodiment that “‘guarantees’ or ‘ensures’ the availability of the second process at any given point in time” and the file histories of the challenged patents “expressly reject[] the notion that the claims contain any guarantee of perfect accuracy.” Addʼl Br. 6. In Straight Path, the Federal Circuit did not offer a view as to the sufficiency of the written description or enablement based on the claim construction provided by the Federal Circuit because “written-description and enablement challenges were not, and could not have been, part of the inter parties review.” Straight Path, 806 F.3d at 1363. We similarly do not offer any determination as to whether this claim construction is supported by the specifications of the ʼ704 patent, ʼ469 patent, and the ʼ121 patent. 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 66 Pet. 24–30; 66 PO Resp. 32‒35; 67 Pet. 25–31; 67 PO Resp. 30‒34; 68 Pet. 24–29; 68 PO Resp. 36‒42. 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 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 11

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

    “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19

  • PTAB / AIA Trials › Joinder §315(c) / SAS all-or-nothingJoinder, grantedGranted

    “and AVAYA, Inc. (“AVAYA”) filed three Petitions and Motions to Join the IPR2014-01366, IPR2014-01367, and IPR2014-01368 proceedings. IPR2015-01011, Papers 2, 4; IPR2015-01007, Papers 3, 4; IPR2015-01006, Papers 2, 4. We granted these motions and joined Samsung, Cisco, and AVAYA (collectively, “Petitioner”) to these inter partes reviews. 66 Paper 26; 67 Paper 23; 68 Paper 25.” slip op. at 3

  Patent outcomesUS 6,108,704 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,108,704
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · Mar 4, 2016 · IPR2014-01366 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, 5, and 10 of the ’469 patent are unpatentable; the remaining challenged claims of the ’704, ’469, and ’121 patents were not shown unpatentable.

  RulingsFinal written decision

  • 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 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 the query is transmitted to the server.” Id. at 1363.” slip op. at 11

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

    “Petitioner contends that “WINS is an implementation of NetBIOS” and, therefore, Petitioner contends that “one having skill in the art would have known about and been motivated to combine Microsoft Manual with NetBIOS.” Id. at 34 (citing 67 Ex. 1004 ¶¶ 88–89). We are persuaded by Petitioner that the combination is reasonable because Microsoft Manual demonstrates that Microsoft TCP/IP has combined the elements of NetBIOS and Microsoft Manual in the same manner in which Petitioner proposes to combine NetBIOS and Microsoft Manual. See 67 Ex. 1012, 3, 11. Microsoft Manual discloses that Microsoft TCP/IP for Windows NT provides support for application interfaces, including NetBIOS for establishing logical names and sessions on the network. Id. at 11. Microsoft Manual describes that “[w]hen WINS servers are in place on the network, NetBIOS over TCP/IP resolves names on a client computer by communication with the WINS server.” 67 Pet. 34 (quoting 67 Ex. 1012, 62). We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by Microsoft Manual, and a person with ordinary skill in the art would have readily combined the disclosures of Microsoft Manual and Microsoft Manual.” slip op. at 25

  • BurdenNot shown unpatentable

    “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual 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. 1014, 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 Microsoft Manual, 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 Microsoft Manual 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 19

  Patent outcomesUS 6,108,704 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,108,704
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · Mar 4, 2016 · IPR2014-01367 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, 5, and 10 of the ’469 patent were held unpatentable; the remaining challenged claims of the ’704, ’469, and ’121 patents were not shown unpatentable because the cited art did not establish …

  RulingsFinal written decision

  • 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 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 the query is transmitted to the server.” Id. at 1363.” slip op. at 11

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

    “Patent Owner argues that these descriptions from Microsoft Manual and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual 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. 1014, 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 Microsoft Manual, 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 Microsoft Manual 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 19

  • BurdenFwd mixedUnpatentable

    “7. Analysis - Claim 10 Claim 10, as written, depends from claim 8. 67 Ex. 1001, 43:1‒3. Claim 8 was cancelled during the Reexamination proceeding. 67 Ex. 1001, 67 (1:18). During Reexamination, claims 14 and 17 were amended to depend from independent claim 9. Id. at 67 (2:15‒26, 2:59‒60). Claim 10 was not amended and still depends from canceled claim 8. Accordingly, we determine claim 10 to be unpatentable because it depends from a cancelled claim. 8. Conclusion We have reviewed the Petition and supporting evidence and find that Petitioner has shown by a preponderance of the evidence that claims 1, 2, and 5 of the ʼ469 patent are obvious over Microsoft Manual and NetBIOS, and claim 10 is unpatentable because it depends from a cancelled claim. Accordingly, we determine that Petitioner has demonstrated by a preponderance of the evidence that claims 1, 2, 5, and 10 of the ʼ469 patent are unpatentable.” slip op. at 28

  Patent outcomesUS 6,009,469 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,009,469
• Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentable
  PTAB · Mar 4, 2016 · IPR2015-01007 · APJ Kalyan K Deshpande · IPR · Final written decision

  Claims 1, 2, 5, and 10 of the ’469 patent were held unpatentable; the remaining challenged claims were not shown unpatentable because the cited art did not establish current network connection status.

  RulingsFinal written decision

  • BurdenFwd mixedMixed

    “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual does not disclose the claimed “is connected to the computer network,” “on-line status,” or “is accessible,” as construed herein.” slip op. at 19

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

    “In Ancora Techs., 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 14

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

    “Petitioner contends that “WINS is an implementation of NetBIOS” and, therefore, Petitioner contends that “one having skill in the art would have known about and been motivated to combine Microsoft Manual with NetBIOS.” Id. at 34 (citing 67 Ex. 1004 ¶¶ 88–89). We are persuaded by Petitioner that the combination is reasonable because Microsoft Manual demonstrates that Microsoft TCP/IP has combined the elements of NetBIOS and Microsoft Manual in the same manner in which Petitioner proposes to combine NetBIOS and Microsoft Manual. See 67 Ex. 1012, 3, 11. Microsoft Manual discloses that Microsoft TCP/IP for Windows NT provides support for application interfaces, including NetBIOS for establishing logical names and sessions on the network. Id. at 11. Microsoft Manual describes that “[w]hen WINS servers are in place on the network, NetBIOS over TCP/IP resolves names on a client computer by communication with the WINS server.” 67 Pet. 34 (quoting 67 Ex. 1012, 62). We are persuaded that Microsoft TCP/IP for Windows NT utilizes NetBIOS features for name resolution, as disclosed by Microsoft Manual, and a person with ordinary skill in the art would have readily combined the disclosures of Microsoft Manual and Microsoft Manual.” slip op. at 25

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

    “and NetBIOS fail to determine whether a computer or process is connected to the computer network. PO Resp. 35, 49–51. In view of our construction of this claim limitation, we agree with Patent Owner. Microsoft Manual 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. 1012, 62– 63, 68–69. Microsoft Manual 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. Microsoft Manual 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, Microsoft Manual 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 Microsoft Manual 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. Microsoft Manual 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. 1012, 68, 150. As such, we determine that Microsoft Manual 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. 1014, 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 Microsoft Manual, 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 Microsoft Manual 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 19

  Patent outcomesUS 6,009,469 mixed
  Claim construction§ 103 obviousnesscites Phillips
  Patents in suitUS 6,009,469

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.