- PTAB · Mar 8, 2016 · IPR2015-00481 · APJ Ken B Barrett · IPR · Adverse judgment
The Board granted Continental’s request for adverse judgment on claims 14, 17, 31, and 33 after Continental, as patent owner, conceded those claims were unpatentable.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). Pursuant to 37 C.F.R. § 42.73(b)(3), “[c]oncession of unpatentability” may be construed as a request for adverse judgment. 5 Continental also asserts that Netlatch should be dismissed as a party and that all papers filed by Netlatch expunged. Continental’s Ownership Statement 5. Continental does not persuade us that those steps are necessary. See 37 C.F.R. § 41.14 (“The record of a proceeding, including documents and things, shall be made available to the public, except as otherwise ordered.”); Office Patent Trial Practice Guide, 77 Fed. Reg. 48,756, 48,760 (Aug. 14, 2012) (referring to “the public’s interest in maintaining a complete and understandable file history”). We understand Continental to expressly request entry of adverse judgment against itself as the current patent owner. Continental’s Ownership Statement 5. Additionally, we treat Continental’s concession that the challenged claims are unpatentable (id. at 5; see Pet. 3–4) as a request for adverse judgment. 37 C.F.R. § 42.73(b)(3). Under these circumstances, entry of judgment adverse to Patent Owner Continental is appropriate.” slip op. at 6
NonePatents in suitUS 5,530,431 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 6,108,704 - Samsung Electronics Co., Ltd. / Samsung Electronics America, Inc. et al. v. Straight Path IP Group, Inc.Some claims unpatentablePTAB · 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 mixedClaim construction§ 103 obviousnesscites PhillipsPatents in suitUS 6,009,469 - Dr. Michael Farmwald / RPX Corporation v. Parkervision, Inc.Adverse judgmentPTAB · Oct 29, 2015 · IPR2014-00948 · APJ Jon B Tornquist · IPR · Adverse judgment
The Board granted Patent Owner’s adverse-judgment motion, entered judgment against Patent Owner, and cancelled claims 2, 22, 23, and 25.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request entry of adverse judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). “Judgment” is defined as “a final written decision by the Board, or a termination of a proceeding.” 37 C.F.R. § 42.2. Although Patent Owner uses the term “termination” in its Motion, it did not submit the Motion under 37 C.F.R. § 42.72 and it did not explain why termination is appropriate in this circumstance. See 37 C.F.R. § 42.72 (noting that the Board may terminate a trial without rendering a final written decision “where appropriate,” such as when the trial is consolidated with another proceeding or pursuant to a settlement under 35 U.S.C. § 317(a)). Under the circumstances presented here, we see no reason not to grant Patent Owner’s Motion. Additionally, for the reasons discussed above, this Decision is a Final Written Decision, not a termination of the proceeding.1” slip op. at 3
NonePatents in suitUS 6,370,371 - Dr. Michael Farmwald / RPX Corporation v. Parkervision, Inc.Adverse judgmentPTAB · Oct 29, 2015 · IPR2014-00947 · APJ Jon B Tornquist · IPR · Adverse judgment
The Board granted Patent Owner’s motion for adverse judgment and cancelled claims 1, 23, 25, 161, 193, and 202.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request entry of adverse judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). “Judgment” is defined as “a final written decision by the Board, or a termination of a proceeding.” 37 C.F.R. § 42.2. Although Patent Owner uses the term “termination” in its Motion, it did not submit the Motion under 37 C.F.R. § 42.72 and did not explain why termination is appropriate in this circumstance. See 37 C.F.R. § 42.72 (noting that the Board may terminate a trial without rendering a final written decision “where appropriate,” such as when the trial is consolidated with another proceeding or pursuant to a settlement under 35 U.S.C. § 317(a)). Under the circumstances presented here, we see no reason not to grant Patent Owner’s Motion. Additionally, for the reasons discussed above, this Decision is a Final Written Decision, not a termination of the proceeding.1” slip op. at 3
NonePatents in suitUS 6,061,551 - Dr. Michael Farmwald / RPX Corporation v. Parkervision, Inc.Adverse judgmentPTAB · Oct 29, 2015 · IPR2014-00946 · APJ Bart A Gerstenblith · IPR · Adverse judgment
The Board granted Patent Owner’s motion for adverse judgment and cancelled claims 1, 82, 90, and 91.
RulingsAdverse judgment- Adverse judgmentAdverse judgmentGranted
“A party may request entry of adverse judgment against itself at any time during a proceeding. 37 C.F.R. § 42.73(b). “Judgment” is defined as “a final written decision by the Board, or a termination of a proceeding.” 37 C.F.R. § 42.2. Although Patent Owner uses the term “termination” in its Motion, it did not submit the Motion under 37 C.F.R. § 42.72 and did not explain why termination is appropriate in this circumstance. See 37 C.F.R. § 42.72 (noting that the Board may terminate a trial without rendering a final written decision “where appropriate,” such as when the trial is consolidated with another proceeding or pursuant to a settlement under 35 U.S.C. § 317(a)). Under the circumstances presented here, we see no reason not to grant Patent Owner’s Motion. Additionally, for the reasons discussed above, this Decision is a Final Written Decision, not a termination of the proceeding.1” slip op. at 3
- PTAB / AIA Trials › Institution threshold (reasonable likelihood / more likely than not)InstitutedInstituted
“(collectively, “Petitioner”) filed a Petition for inter partes review of U.S. Patent No. 6,266,518 B1 (“the ’518 patent”). Paper 1. ParkerVision, Inc. (“Patent Owner”) filed a Preliminary Response on September 24, 2014. Paper 7. On December 18, 2014, we instituted this inter partes review of claims 1, 82, 90, and 91 of the ’518 patent. Paper 8.” slip op. at 2
NonePatents in suitUS 6,266,518
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.