throbber

`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`_______________________________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`_______________________________
`
`AVAYA INC.
`Petitioner
`
`v.
`
`NETWORK-1 SECURITY SOLUTIONS, INC.
`Patent Owner
`____________________
`
`CASE IPR2013-00071
`U.S. Patent No. 6,218,930
`____________________
`
`Before the honorable Jameson Lee, Joni Y. Chang, and Justin T. Arbes
`____________________
`
`
`PETITIONER AVAYA INC’S RESPONSE TO MOTION
`FOR JOINDER FILED BY THIRD PARTIES
`SONY CORPORATION OF AMERICA, AXIS COMMUNICATION AB,
`AXIS COMMUNICATIONS INC., AND HEWLETT-PACKARD CO.
`
`
`
`
`
`
`
`
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`
`
`TABLE OF CONTENTS
`
`IPR2013-0071
`
`
`I.
`
`INTRODUCTION ........................................................................................... 1
`
`II. ARGUMENT ................................................................................................... 1
`
`A.
`
`B.
`
`Factual Background ............................................................................... 1
`
`The ’386 Petition Is Untimely For HP, Timely For Sony and
`
`Axis ........................................................................................................ 2
`
`C.
`
`The Board Should Preclude HP’s Participation to Discourage
`
`Future Parties From Seeking Late Joinder Requests ............................ 6
`
`D.
`
`If the Board Grants Joinder, it Should Adopt Several Procedural
`
`Conditions to Reduce Disruption .......................................................... 8
`
`III. CONCLUSION ................................................................................................ 9
`
`
`
`
`
`
`
`
`
`
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`
`I.
`
`INTRODUCTION
`
`IPR2013-0071
`
`
`Pursuant to the Board’s Order in Paper No. 27, Petitioner Avaya Inc.
`
`(“Avaya”) partially opposes the Motion for Joinder of Sony Corporation of
`
`America (“Sony”), Axis Communications AB, Axis Communications Inc. (both
`
`Axis entities, “Axis”), and Hewlett-Packard Co. (“HP”) (collectively, “the ’386
`
`Petitioners”). As set forth in greater detail below, Avaya opposes the joinder of
`
`HP, but consents to the joinder of Sony and Axis.
`
`First, pursuant to 35 U.S.C. § 315(b), the ’386 Petition, while timely for
`
`Sony and Axis, is untimely for HP. Accordingly, the joinder must be denied with
`
`respect to HP on that basis. Second, HP failed to act diligently in filing a petition,
`
`and the Board should deny the joinder request with respect to HP on those grounds.
`
`Finally, if the Board grants the ’386 Petitioners’ Motion, either in whole or in-part,
`
`Avaya requests the adoption of specific conditions identified in Section II.D., infra,
`
`to minimize the disruption to this Proceeding.
`
`II. ARGUMENT
`
`
`
`A.
`
`Factual Background
`
`In the district court infringement action, Sony was served on December 19,
`
`2011; Axis was served on December 27, 2011; and HP was served on December
`
`15, 2011. See Exs. AV-1023, AV-1024 and AV-1025.
`
`
`
`1
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`
`On December 19, 2012, Sony and Axis filed their first petition (“the ’092
`
`Petition”) seeking an IPR review of Patent 6,218,930 (“the ’930 patent). See
`
`IPR2013-0092, Paper No. 9. Sony and Axis filed the ’092 Petition one year before
`
`Patent Owner Network-1 Security Solutions, LLC (“Network-1”) served either
`
`Sony or Axis with its complaint, and thus the petition was “properly filed.” See
`
`Section II.A, supra. The Board determined not to institute a proceeding in the ’092
`
`Petition, and recently denied a request for rehearing. See IPR2013-0092, Paper
`
`Nos. 21 and 24. HP was not a petitioner to the ’092 Petition, and did not file any
`
`petitions on its own.
`
`On June 24, 2013, Sony and Axis filed its second petition (“the ’386
`
`Petition”). HP is also named as a petitioner, for the first time, in the ’386 Petition.
`
`HP’s petition is thus filed more than 18 months after Network-1 served HP with a
`
`complaint for infringement of the ‘930 patent.
`
`
`
`B.
`
`The ’386 Petition Is Untimely For HP, Timely For Sony and Axis
`
`The ’386 Petitioners collectively assert that they timely filed because they
`
`filed within one month after the Board granted the petition in this proceeding
`
`(“’071 Petition”). See ’386 Petitioners’ Motion, p. 5.
`
`Section 315(b)-(c) of Title 35 defines IPR petition timeliness:
`
`(b) . . . An inter partes review may not be instituted if the
`petition requesting the proceeding is filed more than 1
`
`
`
`2
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`
`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. The time
`limitation set forth in the preceding sentence shall not
`apply to a request for joinder under subsection (c).
`(c) JOINDER. - If the Director institutes an inter partes
`review, the Director, in his or her discretion, may join as
`a party to that inter partes review any person who
`properly files a petition under section 311 that the
`Director, after receiving a preliminary response under
`section 313 or the expiration of the time for filing such a
`response, determines warrants the institution of an inter
`partes review under section 314.
`
`35 U.S.C. § 315(b)-(c) (emphasis added).
`
`The plain language in subsection (b) mandates that an IPR petition is barred
`
`if filed more than one year after the petitioner was served with a complaint alleging
`
`infringement of the patent. While the final sentence of subsection (b) states that
`
`the one-year bar “shall not apply to a request for joinder under subsection (c),” that
`
`sentence relates to “requests for joinder,” not the filing of a new petition. But only
`
`a person who “properly files a petition under section 311” can request joinder. See
`
`35 U.S.C. § 315(c); see also IPR2013-00319, Paper No. 16 (including authorities
`
`cited within). Put another way, a condition precedent to a request for joinder is
`
`that the party in question already have properly filed a petition (i.e., a petition filed
`
`
`
`3
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`within the one-year bar). See 35 U.S.C. § 315(b) (stating that a petition is not
`
`“properly filed” if it has been filed more than one year after a complaint).
`
`In enacting the America Invents Act, Congress made clear that there are no
`
`exceptions to the one-year bar:
`
`[I]n his 2008 remarks on a substantially identical joinder
`provision in the bill that he introduced that year, Senator
`Kyl commented . . . time deadlines for filing petitions
`must be complied with in all cases.
`
`(Ex. AV-2021 at 613-14) (emphasis added).
`
`A few more words about joinder . . . additional petitions
`can be joined only if, among other things, they are
`properly filed. The words “properly filed” are a term of
`art that . . has been given content no less than three times
`during this decade by the U.S. Supreme Court . . . The
`gist of these decisions is that time deadlines for filing
`petitions must be complied with in all cases.
`154 Cong. Rec. S9988 (daily ed. Sep. 27, 2008) (statement of Sen. Kyl) (Ex. AV-
`
`1022 at S9988) (emphasis added).
`
`Thus, the one-year bar applies “in all cases” to petitions (as opposed to
`
`requests for joinder). Subsection (c) is consistent with subsection (b) and indicates
`
`that one may request joinder only if that person properly files a petition, as Sony
`
`and Axis previously did by filing the ’092 Petition. For HP, however, the ’386
`
`
`
`4
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`Petition was not properly filed because HP (unlike Sony and Axis) did not file a
`
`timely petition (i.e., a petition filed within one year of HP being served). HP’s
`
`inclusion in this Proceeding, should therefore be denied.
`
`Allowing Sony and Axis to join while denying HP comports with a prior
`
`Board ruling. In Microsoft Corp. v. Proxyconn, Inc., IPR2013-00109, the Board
`
`permitted joinder of a second petition filed by the same petitioner, Microsoft,
`
`“after learning that additional claims were being asserted by Patent owner in
`
`concurrent district court litigation.” (Paper No. 15). In filing its first petition,
`
`Microsoft has already “properly file[d] a petition under section 311,” and thus was
`
`entitled to seek joinder after the one-year bar for its second petition. See 35 U.S.C.
`
`§ 315(c). Here, similarly, Sony and Axis “properly file[d] [the ’092] petition”
`
`within the one-year bar, and thus Sony and Axis are entitled to join their ’386
`
`Petition with this Proceeding. HP, however, has not previously filed a timely-
`
`petition, and accordingly should not be joined.1
`
`
`1 In Motorola v. Softview LLC, IPR2013-00256, the Board permitted joinder of a
`
`petition filed by third party Motorola after the one-year bar, but the Board was not
`
`presented with the above statutorily-based argument for consideration in those
`
`cases. (Paper No. 10). Thus, the Motorola decision is inapplicable here.
`
`
`
`5
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`
`Allowing HP to join would also lead to a possible infinite string of follow-
`
`on IPR petitions by third parties. For instance, if the Board determines that third
`
`parties (such as HP) that failed to file timely-petitions are able to join timely filed-
`
`granted petitions, other third parties could file a third wave of IPR petitions and
`
`requests for joinder within 30 days of the ’386 Petition being granted. If the Board
`
`were to grant this third wave, the other parties’ requests could be followed by a
`
`fourth, fifth, and subsequent waves ad infinitum. Clearly, Congress did not intend
`
`this endless string of petitions as it would be disruptive to the goal to resolve IPR
`
`proceedings within one year from institution.
`
`C. The Board Should Preclude HP’s Participation to Discourage
`Future Parties From Seeking Late Joinder Requests
`
`The Board should also consider diligence when determining whether to
`
`
`
`grant a request for joinder. See Microsoft Corp. v. Proxyconn, Inc., IPR2013-
`
`00109 (Paper No. 15). Here, in the district court action, HP was served with the
`
`patent infringement complaint by Network-1 on December 15, 2011, the same day
`
`that Avaya was served. HP failed to act diligently during the same one-year period
`
`that Avaya shared. Moreover, even after Avaya filed its petition, HP had 12 days
`
`
`
`6
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`prior to the expiration of the one-year time period during which it could have filed
`
`a petition.2
`
`In crafting the AIA, Congress noted that “[t]he [USPTO] has made clear that
`
`it intends to use [its discretionary authority to allow joinder] to encourage early
`
`requests for joinder and to discourage late requests.” 157 Cong. Rec. S1376 (daily
`
`ed. Mar. 8, 2011) (statement of Sen. Kyl) (Ex. AV-1021 at 613). If HP had
`
`properly filed a petition of its own (within the one-year bar), it could have sought
`
`joinder with the ’071 Petition as early as March 12, 2013, after Network-1 filed its
`
`preliminary patent owner response. See 35 U.S.C. § 315(c). HP, however, took no
`
`such action. Nor did it seek joinder immediately after the ’071 Petition was
`
`granted on May 24, 2013. Rather, it waited a full 30 days after the ’071 Petition
`
`was granted. In its papers, HP has offered no justification for its delay.
`
`Accordingly, HP’s lack of diligence weighs against the Board granting its motion
`
`for joinder. As a matter of policy, allowing HP to join under these circumstances
`
`would create a disincentive for future parties to lodge early joinder requests, and
`
`would disrupt the Board’s goal of resolving these matters within one year from the
`
`institution of proceedings.
`
`2 HP’s petition would have been due on December 17, 2012, since December 15,
`
`2012 was a Saturday.
`
`
`
`7
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`
`
`
`
`IPR2013-0071
`
`
`In contrast, Sony and Axis timely filed their ’092 Petition. The Board
`
`denied the ’092 Petition on the same day that ’071 Petition was granted. Thus,
`
`Sony and Axis likely prepared their ’386 Petition after the Board declined to
`
`institute their ’092 Petition. Such circumstances do not appear to indicate a lack of
`
`diligence on the part of Sony and Axis. Rather, it is entirely reasonable that one
`
`set of parties (here Sony and Axis) would only seek joinder upon denial of their
`
`original petition.
`
`D.
`
`If the Board Grants Joinder, it Should Adopt Several Procedural
`Conditions to Reduce Disruption
`
`
`Avaya requests that, should the Board grants the ’386 Petitioners’ Motion, a
`
`number of procedural conditions be adopted that will reduce the prejudice to
`
`Avaya and reduce the disruption to this Proceeding.3 Those conditions include the
`
`following: (1) extend the briefing schedule by an appropriate amount of time so
`
`
`3 Avaya makes this proposal under the assumption that the Board will grant the
`
`’386 Petition on one or more of the new grounds (Grounds 1, 2, and 4) raised by
`
`Sony and Axis. Should the Board only grant the ’386 Petition on Ground 3
`
`(anticipation by Matsuno), Avaya seeks the same conditions it sought with respect
`
`to Dell’s joinder motion. Paper No. 30.
`
`
`
`8
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`that all adopted grounds of invalidity will be considered together; (2) provide for
`
`Avaya to maintain responsibility for all briefs that are to address grounds
`
`containing the Matsuno reference; (3) provide for Avaya to maintain control and
`
`responsibility for any depositions of any Patent Owner witness, including any
`
`experts, where any added entities from the ’386 Petitioners will be able to ask
`
`questions only after Avaya has completed its questioning and within the remaining
`
`time allowed for such depositions; (4) provide for Avaya to be given control and
`
`responsibility for any redirect depositions of Dr. Zimmerman, where any added
`
`entities from the ’386 Petitioners will be able to ask questions only after Avaya has
`
`completed its questioning and within the remaining time allowed for such
`
`depositions; (5) all motions filed by petitioners must be authorized by Avaya; and
`
`(6) provide for Avaya to be responsible for all oral arguments that are to address
`
`grounds containing the Matsuno reference, where any added entities from the ’386
`
`Petitioners will be able to present arguments only after Avaya has completed its
`
`arguments and within the remaining time allowed.
`
`III. CONCLUSION
`
`For the reasons set forth above, Avaya respectfully submits that the Board
`
`should reject the ’386 Petitioners Motion with respect to HP, but grant the motion
`
`for Sony and Axis. If the Board grants any part of the ’386 Petitioners’ Motion,
`
`
`
`9
`
`

`

`Avaya’s Response to the ’386 Petitioners’ Joinder Request
`
`IPR2013-0071
`
`
`
`Avaya respectfully requests that the Board adopt the suggested conditions to
`
`minimize disruption to this Proceeding.
`
`Respectfully submitted,
`
`
`
`
`July 3, 2013
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` /Jeffrey D. Sanok/
`Jeffrey D. Sanok, Reg. No. 32,169
`Jonathan M. Lindsay, Reg. No. 45,810
`CROWELL & MORING LLP
`Intellectual Property Group
`P.O. Box 14300
`Washington, DC 20044-4300
`
`
`
`10
`
`

`

`CERTIFICATE OF SERVICE UNDER 37 C.F.R. § 42.6(e)
`
`I hereby certify that on this 3rd day of July 2013, true and correct copies of
`the foregoing “PETITIONER AVAYA INC’S RESPONSE TO MOTION FOR
`JOINDER FILED BY THIRD PARTIES SONY CORPORATION OF
`AMERICA, AXIS COMMUNICATION AB, AXIS COMMUNICATIONS INC.,
`AND HEWLETT-PACKARD CO.” was served, in accordance with the parties’
`electronic service agreement, by electronic mail upon the following lead and
`backup counsel of record for the Patent Owner, Network-1 Security Solutions,
`Inc.:
`
`Robert G. Mukai, Lead Counsel
`Buchanan, Ingersoll & Rooney P.C.
`1737 King St., Suite 500
`Alexandria, VA 22314
`Service E-mail: Robert.Mukai@BIPC.com
`
`Charles F. Wieland III, Back-up Counsel
`Buchanan, Ingersoll & Rooney P.C.
`1737 King St., Suite 500
`Alexandria, VA 22314
`Service E-mail: Charles.Wieland@BIPC.com
`
`
`Respectfully submitted,
`
`
`July 3, 2013
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` /Jonathan Lindsay/
`Jonathan M. Lindsay, Reg. No. 45,810
`(Back-up Counsel)
`CROWELL & MORING LLP
`Intellectual Property Group
`1001 Pennsylvania Avenue, N.W.
`Washington, DC 20004-2595
`
`

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