throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`DELL INC.,
`Petitioner
`
`v.
`
`NETWORK-1 SECURITY SOLUTIONS, INC.,
`Patent Owner
`
`
`CASE IPR: IPR2013-00385
`
`
`
`MOTION FOR JOINDER UNDER 35 U.S.C. § 315(c),
`37 C.F.R. §§ 42.22, AND 42.122(b)
`
`Mail Stop Patent Board
`Patent Trial and Appeal Board
`U.S. Patent and Trademark Office
`P.O. Box 1450
`Alexandria, VA 22313-1450
`
`

`

`
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`Dell Inc. (“Dell”) submits concurrently herewith a Petition for Inter Partes
`
`Review of U.S. Patent No. 6,218,930 (the “’930 Patent”) (“Petition”). Dell
`
`respectfully requests that its Petition be granted and moves that the proceedings be
`
`joined pursuant to 35 U.S.C. § 315(c), 37 C.F.R. §§ 42.22, and 37 C.F.R.
`
`§ 42.122(b) with the pending inter partes review initiated by Avaya Inc. (“Avaya”)
`
`concerning the same patent: Avaya Inc. v. Network-1 Security Solutions, Inc., Case
`
`No. IPR2013-00071 (the “Avaya IPR”).
`
`In accordance with the Board’s Representative Order identifying matters to
`
`be addressed in a motion for joinder (Paper No. 15, IPR2013-00004, April 24,
`
`2013), Dell submits that: (1) joinder is appropriate because it will promote efficient
`
`determination of the validity of the ’930 Patent without prejudice to Avaya or
`
`Network-1 (See, e.g., Paper No. 10, IPR2013-00256, June 20, 2013 (granting
`
`motion for joinder under similar circumstances)); (2) Dell’s petition raises the
`
`same grounds of unpatentability as Avaya; (3) joinder would not affect the pending
`
`schedule in the Avaya IPR nor increase the complexity of that proceeding,
`
`minimizing costs; and (4) Dell is willing to agree to consolidated filings with
`
`Avaya to minimize burden and schedule impact. Absent joinder, Dell could be
`
`prejudiced if the Avaya IPR is terminated before a final written decision is issued
`
`as it would have to litigate the same positions at the District Court under a higher
`
`burden of proof. Accordingly, joinder should be granted.
`
`
`
`1
`
`

`

`Dell’s Motion for Joinder (IPR2013-00385)
`
`Background and Related Proceedings
`
`
`I.
`
`Network-1 Security Solutions, Inc., is the owner of the ’930 Patent. In 2011,
`
`Network-1 sued twenty-six (26) different companies, including Dell and Avaya,
`
`for allegedly infringing the ’930 Patent by selling devices that are compliant with
`
`the IEEE 802.3af and 802.3at Power over Ethernet (“PoE”) standards (the
`
`“Underlying Litigation”).
`
`In addition to the Underlying Litigation, the ’930 Patent is the subject of a
`
`pending ex parte reexamination proceeding (Control No. 90/012,401) in which
`
`claims 6, 8, and 9 have been non-finally rejected on multiple anticipation and
`
`obviousness grounds. Neither Dell nor Avaya are the real party-in-interest in that
`
`proceeding, which has been stayed by the Board pending outcome of the Avaya
`
`IPR and another petition for inter partes review of the ’930 Patent, IPR2013-00092
`
`(See Paper No. 9, IPR2013-00071).1
`
`Avaya Corporation filed its petition for inter partes review of the ‘930
`
`Patent on December 5, 2012. On March 5, 2013, the Underlying Litigation was
`
`stayed pending the outcome of both the Avaya IPR and IPR2013-00092. The
`
`Board instituted trial in the Avaya IPR on May 24, 2013 (Paper No. 18, IPR 2013-
`
`1 That petition was submitted by Sony Corporation of America and has been
`
`denied (Paper No. 21, IPR2013-00092). Sony has requested rehearing (Paper No.
`
`22, IPR2013-00092).
`
`
`
`2
`
`

`

`
`00071) on Grounds 1 and 3 in Avaya’s petition and set July 24, 2013, as the date
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`for Network-1’s response to the petition (Paper No. 19). On June 7, 2013, Avaya
`
`requested a limited rehearing on the subject of its Ground 5 (Paper No. 20). The
`
`Board has not yet acted on this request. Oral argument is currently set for
`
`December 17, 2013.
`
`II. Dell’s petition and motion for joinder are timely
`Dell’s Petition and the instant motion for joinder are timely under 35 U.S.C.
`
`315(c), 37 C.F.R. §§ 42.22, and 42.122(b), as they are being submitted within one
`
`month of May 24, 2013, the date that the Avaya IPR was instituted.2 Dell’s filings
`
`are within the time period prescribed by the statute and the regulations for filing
`
`such a petition and motion for joinder.
`
`Network-1’s counsel stated on the June 24, 2013 conference call that it
`
`believes Dell’s petition is untimely and referred the Board to an Opposition to a
`
`Petitioner’s Motion for Joinder filed in IPR2013-00319. (See Paper No. 16,
`
`IPR2013-00319, June 11, 2013) (the “Opposition”). The Opposition takes a
`
`number of rather radical positions including that the USPTO has misinterpreted 35
`
`2 On June 24, 2013, at the Board’s request, counsel for Petitioner Dell conducted a
`
`conference call with the Board, counsel for Petitioner Avaya in IPR2013-00071,
`
`and counsel for Patent Owner Network-1. During the call, the Board authorized the
`
`filing of the instant motion.
`
`
`
`3
`
`

`

`
`U.S.C. §§ 315(b) and 315(c), has exceeded its statutory authority when
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`promulgating its regulations relating to joinder, and that every decision by the
`
`Board on joinder to date is wrong. (Id. at 2-5.)
`
`Dell disagrees with Network-1’s position and respectfully submits that the
`
`USPTO and the Board are properly interpreting 35 U.S.C. §§ 315(b) and 315(c)
`
`and that the USPTO’s regulations are properly promulgated. See, e.g., 35 U.S.C.
`
`§ 316(a)(12) (authorizing the Director to set a time limit for requesting joinder); 37
`
`C.F.R. 42.122(b) (setting a time limit of one-month); see also Changes to
`
`Implement Inter Partes Review Proceedings, Post-Grant Review Proceedings, and
`
`Transitional Program for Covered Business Method Patents, Federal Register, Vol.
`
`77, No. 157 at 48690 (“the time period set forth in § 42.101(b) shall not apply
`
`when the petition is accompanied by a request for joinder. This is consistent with
`
`the last sentence of 35 U.S.C. 315(b), as amended”).
`
`Dell respectfully submits that the statutory interpretation advanced by the
`
`Opposition (as apparently adopted by Network-1) is incorrect. The last sentence of
`
`35 U.S.C. § 315(b) plainly states that the “[the one-year time limit] set forth in the
`
`preceding sentence shall not apply to a request for joinder under subsection (c).”
`
`Subsection (c) permits joinder of “any person who properly files a petition under
`
`section 311.” Whether a petition is “properly file[d]” within the meaning of 35
`
`U.S.C. § 311 is thus determined by whether that petition meets the requirements of
`
`
`
`4
`
`

`

`
`35 U.S.C. § 311, which are not altered by 35 U.S.C. § 315(b). Dell’s Petition
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`meets the requirements of 35 U.S.C. § 311 as Dell has (1) paid the fee prescribed
`
`by the Director pursuant to § 311(a); and (2) pursuant to § 311(b), requested
`
`cancellation of 1 or more claims of the ‘930 Patent on section 102 and 103 grounds
`
`premised on prior art patents or printed publications.3 See 35 U.S.C. § 311.
`
`Indeed, a strict reading of 35 U.S.C. § 315(c) actually contemplates that the Board
`
`does not even have to institute a trial on Dell’s Petition, but can simply join Dell to
`
`the Avaya IPR if it “determines” that Dell’s Petition “warrants the institution of an
`
`inter partes review under section 314.”
`
`Most importantly, the Board has already considered and granted motions for
`
`joinder in at least two other proceedings in which the subject petitions were not
`
`filed until after the one-year deadline of § 315(b) had passed. (See, e.g., Paper No.
`
`15, IPR2013-00109, February 15, 2013 (explaining “the one-year time bar does not
`
`apply to a request for joinder… an important consideration here, because
`
`[Petitioner] was served with a complaint asserting infringement of the [challenged]
`
`patent more than a year before filing the second Petition.”); Paper No. 10,
`
`IPR2013-00256, June 20, 2013.) Accordingly, Dell respectfully submits that its
`
`3 § 311(c) does not apply to the ‘930 Patent since it is not a patent described in
`
`section 3(n)(1) of the Leahy-Smith American Invents Act. See Pub. Law No. 112-
`
`274, § 1(d)(1) (2013).
`
`
`
`5
`
`

`

`
`Petition and the instant motion are timely and properly filed under both the
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`applicable statutes and regulations.
`
`During the June 24 conference call, Network-1’s counsel also raised
`
`concerns regarding Dell’s purported “delay” and “diligence” in filing its Petition
`
`and the instant motion. These concerns are misplaced. Dell has fully complied
`
`with the timelines provided in both the statute and regulations as written in order
`
`to protect its interests. Dell should not be punished for following the statutory and
`
`regulatory scheme for inter partes review, particularly when, as explained further
`
`below, it is making every effort to minimize the potential for prejudice to either
`
`Avaya or Network-1.
`
`III. Joinder will not impact the Board’s ability to complete the review
`within the one-year period
`
`Joinder in this case will not impact the Board’s ability to complete its review
`
`in a timely manner. 35 U.S.C. § 316(a)(11) and associated rule 37 C.F.R. §
`
`42.100(c) provide that inter partes review proceedings should be completed and
`
`the Board’s final decision issued within one year of institution of the review. Here,
`
`joinder should not affect the Board’s ability to issue its final determination within
`
`one year because Dell does not raise any issues that are not already before the
`
`
`
`6
`
`

`

`
`Board.4 Indeed, Dell’s Petition is based on the same grounds and combinations of
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`prior art considered by the Board in instituting trial in the Avaya IPR.
`
`Accordingly, since Dell’s inter partes review petition does not raise any new issues
`
`beyond those already considered by Network-1, Dell does not anticipate that
`
`Network-1 will need a substantial amount of time to complete its Preliminary
`
`Patent Owner’s Response (“POPR”).5
`
`Dell respectfully submits that briefing and discovery in the joined
`
`proceeding can be simplified to minimize any impact to the schedule or the volume
`
`of materials to be submitted to the Board. Given that Avaya and Dell will be
`
`4 Dell notes that 35 U.S.C. § 316(a)(11) and associated rule 37 C.F.R. § 42.100(c)
`
`also provide the Board with flexibility to extend the one-year period by up to six
`
`months in the case of joinder.
`
`5 On the June 24, 2013 conference call, the Board asked Dell’s undersigned
`
`counsel if Dell had any proposal for the schedule of Network 1’s POPR. Dell
`
`believes the Board supplied this schedule during the call and that the POPR is due
`
`July 9, 2013. On the call, Avaya’s counsel inquired as to the permissible scope of
`
`the POPR. Dell respectfully suggests that the Board adopt an Order similar to that
`
`contained in Paper No. 8, IPR2013-00256 and allow Network-1 the option to file a
`
`POPR addressing only those points raised in Dell’s Petition that are different from
`
`those in the Avaya IPR (there should be none).
`
`
`
`7
`
`

`

`
`addressing the same prior art and the same bases for rejection of the claims at issue
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`using the same expert, Dell envisions few, if any, differences in position. In any
`
`event, Dell has conferred with counsel for Avaya and is willing to agree to
`
`consolidated filings on the existing briefing schedule, for which Avaya will be
`
`responsible. (Paper No. 10 at 9, IPR2013-00256, June 20, 2013.) Similar to the
`
`procedures ordered by the Board in IPR2013-00256, Dell is willing to be limited to
`
`separate filings, if any, of no more than seven pages directed only to points of
`
`disagreement with Avaya, with the understanding that it will not be permitted any
`
`separate arguments in furtherance of those advanced in Avaya’s consolidated
`
`filings. (Id.) “This approach should avoid introducing delay that could arise from
`
`lengthy briefing by each party, while providing the parties an opportunity to
`
`address all issues that may arise.” (Id.)
`
`As also discussed during the June 24 conference call, Dell has retained the
`
`same expert as Avaya, Dr. George A. Zimmerman. Dr. Zimmerman has executed
`
`a declaration in support of Dell’s petition that is identical in substance to the
`
`declaration he previously filed in the Avaya IPR. The only difference is that Dr.
`
`Zimmerman has omitted his analysis of references and grounds not pursued by
`
`Dell in its Petition. Accordingly, Network-1 should not need any additional
`
`discovery of Dr. Zimmerman beyond that which it has already asked for in the
`
`Avaya IPR, nor should it be permitted any.
`
`
`
`8
`
`

`

`
`IV. Joinder would enhance efficiency by avoiding duplicate efforts and
`inconsistencies and would avoid prejudice to Dell
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`The validity of the ’930 patent is squarely at issue in, as described above,
`
`both the Underlying Litigation and the Avaya IPR, and a final written decision in
`
`the consolidated inter partes review has the potential to resolve the Underlying
`
`Litigation. Allowing a consolidated inter partes review would also avoid potential
`
`inconsistency and avoid prejudice to Dell in the event that Avaya and Network-1
`
`reach a resolution of their disputes during the pendency of the IPR. 35 U.S.C. §
`
`317(a) provides that an inter partes review “shall be terminated with respect to any
`
`petitioner upon the joint request of the petitioner and the patent owner” unless the
`
`Board has already reached its decision on the merits. If no petitioner remains after
`
`settlement, “the Office may terminate the review.” Id. Thus, if Network-1 and
`
`Avaya were to reach a settlement, the Avaya IPR could terminate without
`
`proceeding to a final written decision.
`
`Indeed, if the Board terminated the Avaya IPR, Dell (along with the other
`
`defendants) would be forced to start over before the District Court with the exact
`
`same arguments that Avaya has already shown it is reasonably likely to prevail on.
`
`(See Paper No. 18, IPR 2013-00071, May 24, 2013.) The potential for
`
`inconsistency would be also heightened because Dell (and the other defendants)
`
`would face a higher burden before the District Court of proving the invalidity of
`
`claims 6 and 9 by clear and convincing evidence, as opposed to the lower burden
`
`
`
`9
`
`

`

`
`here of a preponderance of the evidence. See 35 U.S.C. § 316(e). Having to
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`overcome a higher burden to get the same result is by definition prejudicial to Dell,
`
`especially since Dell has complied with the statute and regulations in filing its
`
`Petition and the instant motion. Additionally, if the Board permits Dell to join the
`
`Avaya IPR, and Network-1 is correct in its belief that claims 6 and 9 of the ‘930
`
`patent are patentable, Dell will be estopped from further challenging the validity of
`
`the patent in the Underlying Litigation, avoiding duplication of efforts at least as to
`
`Dell. See 35 U.S.C. § 315(e)(1). Accordingly, to avoid duplicate efforts, the
`
`possibility of inconsistencies, and prejudice to Dell, joinder is appropriate.
`
`V.
`
`Joinder will not prejudice Network-1 or Avaya
`
`Permitting joinder will not prejudice Network-1 or Avaya. Dell raises no
`
`issues that are not already before the Board, such that joinder would not affect the
`
`timing of the Avaya IPR or the content of Network-1’s Patent Owner response due
`
`on July 24, 2013. Dell also believes any additional costs to Network-1 and Avaya
`
`associated with its participation in the Avaya IPR will be minor, and certainly not
`
`so great as to justify the potential prejudice to Dell if the Avaya IPR were to be
`
`otherwise terminated before a final written decision by the Board.
`
`Finally, even if the Board were to determine that joinder will require a minor
`
`extension of the schedule (as indicated on the June 24, 2013 conference call), such
`
`
`
`10
`
`

`

`
`an extension is permitted by law and is not a reason for denying joinder. 35 U.S.C.
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`§ 316(a)(1); 37 C.F.R. § 42.100(c).
`
`VI. Conclusion
`For the foregoing reasons, Petitioner respectfully requests that its Petition for
`
`Inter Partes Review of U.S. Patent No. 6,218,930 be granted and that the
`
`proceedings be joined with Avaya Corporation v. Network-1 Security Solutions,
`
`Inc., Case IPR2013-00071.
`
`The undersigned attorney may be reached by telephone at (212) 294-3325.
`
`Although Petitioner believes that no fee is required for this Motion, the
`
`Commissioner is hereby authorized to charge any additional fees which may be
`
`required for this Motion to Deposit Account No. 50-1814.
`
`/Michael J. Scheer/
`Michael J. Scheer
`Reg. No. 34,425
`
`Lead Counsel for Petitioner
`Dell Inc.
`
`
`
`Respectfully submitted,
`
`Date: June 24, 2013
`
`
`
`WINSTON & STRAWN LLP
`200 Park Ave.
`New York, NY 10166
`Telephone: (212) 294-3325
`Fax: (202) 282-5100
`mscheer@winston.com
`
`
`
`11
`
`

`

`
`
`Dell’s Motion for Joinder (IPR2013-00385)
`
`CERTIFICATE OF SERVICE
`
`Pursuant to 37 C.F.R. §§ 42.6(e) and 42.105(a), this is to certify that on June
`
`24, 2013 I caused to be served a true and correct copy of the foregoing “MOTION
`
`FOR JOINDER UNDER 35 U.S.C. § 315(c), 37 C.F.R. §§ 42.22, AND 42.122(b)”
`
`by EXPRESS MAIL on the Patent Owner at the correspondence address of record
`
`for the U.S. Patent No. 6,218,930, as follows:
`
`BUCHANAN, INGERSOLL & ROONEY PC
`
`POST OFFICE BOX 1404
`
`ALEXANDRIA VA 22313-1404
`
`Date: June 24, 2013
`
`
`
`WINSTON & STRAWN LLP
`200 Park Ave.
`New York, NY 10166
`Telephone: (212) 294-3325
`Fax: (202) 282-5100
`mscheer@winston.com
`
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`/Michael J. Scheer/
`Michael J. Scheer
`Reg. No. 34,425
`
`Lead Counsel for Petitioner
`Dell Inc.
`
`12
`
`

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket