throbber
Case IPR2016-00450
`Patent No. 8,462,920
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`Twilio Inc.
`Petitioner
`
`v.
`
`TeleSign Corporation
`Patent Owner
`
`Case No. IPR2016-00450
`Patent: 8,462,920
`
`
`
`
`
`
`
`PETITIONER’S REQUEST FOR REHEARING
`UNDER 37 C.F.R. § 42.71(c)
`
`
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`INTRODUCTION AND STATEMENT OF RELIEF REQUESTED
`
`I.
`
`The Board denied institution because “Petitioner has not provided evidence
`
`or argument that Bennett teaches a notification event that would result in the
`
`registrant being notified that the event occurred.” (Paper 17 at 14.) This conclusion
`
`was the Board’s only reason for denying institution. The Board, however,
`
`overlooked arguments and evidence in the Petition that directly contradict the
`
`Board’s finding.
`
`• The Petition stated: “[a] POSITA would have found it obvious and
`
`simple
`
`to
`
`include, as part of
`
`the SMS or voice message
`
`communicating the verification code, that a notification event has
`
`occurred, so that customers were not constantly calling to inquire
`
`why a re-verification was required.” (Paper 1 at 44-45 (emphasis
`
`added).)
`
`• The Petition explained that, when Rolfe’s system detects a transaction
`
`of a certain value, it “calls the [credit card] owner and informs the
`
`owner of the notification event.” (Paper 1 at 46.) The Petition explains
`
`that it would have been obvious to use Bennett’s verification message
`
`to transmit both the verification code and Rolfe’s notification so that
`
`the user would know why they were being contacted. (Paper 1 at 45-
`
`1
`
`47.)
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`• The Petition explained that, as part of the reverification process,
`
`Bennett teaches notifying the registrant of the occurrence of a
`
`notification event in the form of “transmit[ing] the completion code”
`
`to registrant upon the occurrence of the notification event. (Paper 1 at
`
`32-33.) Bennett discloses transmitting a completion or verification
`
`code to the registrant every time Bennett’s system determines a
`
`notification event requiring re-verification has occurred. (Paper 1 at
`
`11-12, 22-23, 32-33.) By transmitting this code in response to the
`
`occurrence of an event, Bennett is notifying the registrant that an
`
`event has occurred.
`
`These disclosures from the Petition directly contradict the Board’s sole reason for
`
`denying institution. Failing to consider these Petition disclosures in the decision
`
`denying institution is an error of fact and law warranting rehearing. As a result,
`
`Petitioner requests that the Board rehear its decision denying institution of inter
`
`partes review and consider Petitioner’s evidence related to the notification event.
`
`II.
`
`FACTUAL BACKGROUND AND PROCEDURAL POSTURE
`
`On January 11, 2016, Petitioner filed a petition challenging claims 1-10, 13,
`
`and 17-22 of the ‘920 patent on four grounds using Bennett as a base reference.
`
`(Paper 1 at 3-4.) Claim 1 recites a notification event that results in a registrant
`
`being contacted with a verification code for re-verification. (Ex. 1001, cl. 1[c]-
`
`2
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`[e][iv]; Paper 1 at 22-27, 32-34.) Claim 4, which depends from claims 1 and 2,
`
`adds a limitation requiring that the “notification event” of claim 1 result in
`
`“notifying the registrant of the occurrence of the established notification event.”
`
`(Ex. 1001, cl. 4; Paper 1 at 44-47.) Petitioner presented evidence and argument in
`
`relation to claim 1 that Bennett taught the claimed notification event in the form of
`
`a transaction that caused Bennet to transmit a completion code to the registrant.
`
`(Paper 1 at 32-33.) The completion code corresponds to notifying the user after the
`
`occurrence of a notification event. For claim 4, Petitioner presented argument and
`
`evidence that (1) Bennett or (2) Bennett plus Rolfe disclosed and rendered obvious
`
`notifying the user of the occurrence of the notification event. (Paper 1 at 44-46.)
`
`On July 8, 2016, the Board denied institution of inter partes review of ’920
`
`patent claims 1-10, 13, and 17-22. The Board construed “notification event” as “an
`
`event that results in the registrant being notified that the event occurred.” (Paper 17
`
`at 7-11.) Based on this construction, the Board determined that Petitioner did not
`
`present evidence or argument that Bennett disclosed a notification event that would
`
`result in the registrant being notified that the event occurred. (Paper 17 at 14.) This
`
`was the Board’s only stated rationale for denying institution of the Petition. (Id.)
`
`The Board did not address (1) the Bennett completion code sent to the registrant as
`
`a result of the notification event or (2) Petitioner’s evidence in claim 4 that the
`
`notification event results in notifying the registrant of the occurrence of the event.
`
`3
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`The fact that the Board did not address these Petition arguments is an error of fact
`
`and law warranting rehearing.
`
`III. LEGAL STANDARDS
`A request for rehearing “must specifically identify all matters the party
`
`believes the Board misapprehended or overlooked, and the place where each
`
`matter was previously addressed in a motion, an opposition, or reply.” 37 C.F.R.
`
`§ 42.71(d). Clearly erroneous fact findings and erroneous conclusions of law are
`
`abuses of discretion that warrant reconsideration. Stevens v. Tamai, 366 F.3d 1325,
`
`1330 (Fed. Cir. 2004).
`
`A.
`
`Finding a Dependent Claim Unpatentable Requires Finding the
`Broader Claims Also Unpatentable
`
`Dependent claims contain all the limitations of the claims from which they
`
`depend. Soverain Software LLC v. Victoria’s Secret Direct Brand Mgmt., LLC, 778
`
`F.3d 1311, 1315 (Fed. Cir. 2015). As a result, where a dependent claim is found
`
`obvious, the broader independent claims must also be obvious. Id.; also Callaway
`
`Golf Co. v. Acushnet Co., 576 F.3d 1331, 1344 (Fed. Cir. 2009) (“A broader
`
`independent claim cannot be nonobvious where a dependent claim stemming from
`
`that independent claim is invalid for obviousness.”) (citation omitted). And the
`
`PTAB has recognized that, when a Petitioner presents arguments regarding a
`
`dependent claim, those arguments may be applied to the claims from which that
`
`4
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`dependent claim depends. Garmin Int’l Inc. v. Cuozzo Speed Techs. LLC,
`
`IPR2012-00001, Paper 15 at 22 (PTAB Jan. 9, 2013).
`
`B.
`
`The APA Requires that the Board Articulate the Rationale for Its
`Decisions
`
`“[T]he Board must articulate its reasoning for making its decision,” as well
`
`as “develop and explain the basis for its findings.” Cutsforth, Inc. v. MotivePower,
`
`Inc., Case No. 2015-1316, 2016 WL 279984, at *3 (Fed. Cir. Jan. 22, 2016)
`
`(reversing the Board’s Final Written Decision where it did not provide enough
`
`explanation to support its finding of obviousness); In re Sang-Su Lee, 277 F.3d
`
`1338, 1342-45 (Fed. Cir. 2002) (reversing denial of a patent application and
`
`remanding so that the Board could provide “reasoned decisionmaking”); see also
`
`Administrative Procedure Act, Pub. L. No. 404, § 8(b) (1946). “Broad, conclusory
`
`statements are not enough to satisfy the Board’s obligation to provide reasoned
`
`explanation for its decision.” Cutsforth, 2016 WL 279984, at *3 (citing In re Sang-
`
`Sue Lee, 277 F.3d at 1343-45).
`
`IV. BASIS FOR RELIEF REQUESTED
`A. The Board’s Only Stated Reason for Denying Institution
`Overlooks Two Arguments in the Petition
`
`Rehearing is warranted because the Board overlooked two arguments in the
`
`Petition that show the Board’s only rationale for denying institution was based on
`
`an incorrect finding of fact. 37 C.F.R. § 42.71(d); Stevens, 366 F.3d at 1330. The
`
`5
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`Board denied institution because it found that “Petitioner has not provided
`
`evidence or argument that Bennett teaches a notification event that would result in
`
`the registrant being notified that the event occurred.” (Paper 17 at 14.) The Board
`
`concluded this finding was dispositive because Petitioner relied on Bennet to teach
`
`the “notification event” of claim 1. (Id. at 12.) Both conclusions overlook
`
`arguments in the Petition that (1) Bennett and (2) Bennett in view of Rolfe teach
`
`and render obvious notifying the registrant of the occurrence of the notification
`
`event. (Paper 1 at 44-47, 32-33.) Petitioner addresses each of the arguments that
`
`the Board overlooked in turn below.
`
`1.
`
`The Board Overlooked Petitioner’s Argument that (1)
`Bennett and (2) Bennet in View of Rolfe Render Obvious
`Notifying the Registrant of the Occurrence of the
`Notification Event
`
`Petitioner expressly argued that (1) Bennett and (2) Bennett in view of Rolfe
`
`render obvious notifying the user of the occurrence of the notification event. (Paper
`
`1 at 44-46.) Claim 4 depends from claims 1 and 2 and expressly adds the
`
`requirement that the registrant be notified of the occurrence of the notification
`
`event that was recited in claim 1. (Supra § II at 2-3; Ex. 1001, cls. 1[c]-[d], 4.)
`
`Claim 4 uses the term “notification event” in nearly the same way that the Board
`
`construed the term for claim 1. Thus, the Petition’s arguments for claim 4 are
`
`highly relevant to the “notification event.” Both the Federal Circuit and this Board
`
`have recognized that the dependent claim, and the claims from which it depends,
`6
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`should be independently analyzed in this situation. Soverain, 778 F.3d at 1315;
`
`Garmin, IPR2012-00001, Paper 15 at 22; Petroleum Geo-Services Inc. v.
`
`WesternGeco LLC, IPR2014-00689, 101 at 18 (Dec. 15, 2015); Ford Motor Co. v.
`
`Paice LLC, IPR2015-00801, Paper 12 at 32 (PTAB Oct. 26, 2015).
`
`In support of Grounds 1 and 2, Petitioner provided evidence and argument
`
`that Bennett “renders obvious notifying the registrant of the occurrence of the
`
`established notification event.” (Paper 1 at 44.) Petitioner explained that, because
`
`Bennett already disclosed contacting the registrant upon the occurrence of a
`
`notification event in order to provide a completion code for re-verification,
`
`“[a] POSITA would have found it obvious and simple to include, as part of the
`
`SMS or voice message communicating the verification code, that a notification
`
`event has occurred, so that customers were not constantly calling to inquire why a
`
`re-verification was required.” (Id. at 44-45 (emphasis added).) The Petition went
`
`on to explain that notifying users of particular events was well known at the time
`
`of the invention of the ‘920 patent. (Id.)
`
`In support of Grounds 3 and 4, Petitioner also provided evidence and
`
`argument showing that Bennett in view of Rolfe renders obvious notifying the user
`
`of the occurrence of the notification event. (Paper 1 at 45-47.) Specifically, Rolfe
`
`discloses a system that verifies certain credit card transactions depending upon the
`
`value of the transaction. (Paper 1 at 46.) When Rolfe’s system detects a transaction
`
`7
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`of a certain value, it “calls the [credit card] owner and informs the owner of the
`
`notification event.” (Paper 1 at 46.) As explained in the Petition, it would have
`
`been obvious to use Bennett’s verification message to transmit both the verification
`
`code and Rolfe’s notification so that the user would know why they were being
`
`contacted. (Paper 1 at 45-47.)
`
`As a result, Petitioner provided argument and evidence showing that Bennett
`
`and Bennett in view of Rolfe render obvious notifying the user of the occurrence of
`
`the notification event in accordance with the Board’s construction. (See Paper 17 at
`
`12-14.) Therefore, Petitioner requests the Board rehear and institute inter partes
`
`review at least against dependent claim 4.
`
`In addition, because claim 4 depends from claims 1 and 2, Petitioner’s
`
`arguments for claim 4 apply equally to claims 1 and 2. Soverain, 778 F.3d at 1315.
`
`As the Board has recognized and the Federal Circuit has confirmed, dependent
`
`claims include all the limitations of the claims from which they depend. Id.;
`
`Petroleum Geo-Services, IPR2014-00689, 101 at 18; Ford Motor Co., IPR2015-
`
`00801, Paper 12 at 32. As a result, the invalidity determination of dependent claim
`
`4 necessarily extends to claims 1 and 2 from which it depends. Soverain, 778 F.3d
`
`at 1315 (citing Callaway Golf, 576 F.3d at 1344). For the same reason, because
`
`claim 5 depends from claim 4, Petitioner’s arguments regarding claim 4 also apply
`
`8
`
`to claim 5. Id.
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`The Board overlooked the Petition’s arguments relating to the notification
`
`limitations of claim 4 when it denied institution by concluding that because claim 4
`
`depends from claim 1, the decision to institute inter partes review rose and fell
`
`with claim 1. (Paper 17 at 14.) As a result, the Board’s decision denying institution
`
`of inter partes review of claim 4 does not address the Petition’s arguments
`
`regarding claim 4’s notification requirement, which is the same limitation and
`
`argument the Board found lacking in the Petition for claim 1. (Paper 17 at 14.) The
`
`absence of explanation regarding claim 4 in the Board’s institution denial does not
`
`comply with the APA’s requirement that the Board “articulate its reasoning for
`
`making its decision,” as well as “develop and explain the basis for its findings.”
`
`Cutsforth, 2016 WL 279984, at *3; In re Sang-Su Lee, 277 F.3d at 1342-45; see
`
`also APA, Pub. L. No. 404, § 8(b). The Board’s denial of inter partes review of
`
`claim 4, without addressing the Petition’s arguments regarding notifying the
`
`registrant of the occurrence of the notification event, also supports rehearing. See
`
`Stevens, 366 F.3d at 1330.
`
`Based on the foregoing, Petitioner requests that the Board rehear its denial of
`
`institution of inter partes review of claims 1, 2, 4, and 5 in light of Petitioner’s
`
`arguments that Bennett and Bennett in view of Rolfe teach and render obvious
`
`notifying the registrant of the occurrence of the notification event.
`
`9
`
`
`
`

`
`2.
`
`Case IPR2016-00450
`Patent No. 8,462,920
`The Board Overlooked Petitioner’s Argument that Bennett
`Notifies the Registrant of the Occurrence of the Notification
`Event by Sending the Registrant a Verification Code as Part
`of the Re-verification Process
`
`The Board’s institution denial also warrants rehearing because the Board
`
`overlooked Petitioner’s evidence and argument that Bennett disclosed notifying the
`
`registrant of the occurrence of the notification event as part of the re-verification
`
`process. (Paper 1 at 23-26, 32-33.) In its denial of institution, the Board construed
`
`“notification event” as “an event that results in the registrant being notified that the
`
`event occurred.” (Decision at 7-11.) However, when the Board applied this
`
`construction to the arguments in the Petition, the Board overlooked that Bennett’s
`
`re-verification includes notifying the registrant of the occurrence of the notification
`
`event in the form of communicating a verification code to the registrant for use in
`
`two-factor authentication. (Paper 1 at 32-33, 22-23, 19-20; Ex. 1005, Fig. 3 (200).)
`
`As explained in the Petition and by Dr. Shamos, Bennett discloses a two-
`
`factor authentication system that is used to both initially authenticate a registrant
`
`and to re-verify the registrant upon the occurrence of a notification event. (Paper 1
`
`at 11-12, 22-36.) As the Petition explains, Bennett’s two-factor authentication
`
`process contains four steps.
`
`1. Detection: Bennett discloses detecting the occurrence of an event that
`
`warrants re-verification. (Paper 1 at 11, 22-23 (the purpose of Bennett’s
`
`10
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`decision module is to determine whether two factor authentication is
`
`required).
`
`2. Communicate: When Bennett determines re-verification is required, it
`
`communicates a verification code to the registrant for use in completing the
`
`required two-factor authentication. (Paper 1 at 32-33, 19-20 (two factor
`
`authentication includes communicating a verification code to the registrant),
`
`11-12, 22-23; Ex. 1005, Fig. 3 (200).)
`
`3. Receive: Bennett receives the verification code from the registrant through a
`
`web interface. (Paper 1 at 34-35, 21-22, 11-12, 22-23; Ex. 1005, Fig. 3.)
`
`4. Compare: Bennett re-verifies the registrant by comparing the verification
`
`code sent to the registrant with the code received through the web interface.
`
`(Paper 1 at 35-37, 11-12, 22-23; Ex. 1005, Fig. 3.)
`
`Step
`
`two of Bennett’s
`
`re-verification process—communicating
`
`the
`
`verification code to the registrant—meets the Board’s construction of notification
`
`event because the communication of the verification code is one form of notifying
`
`the registrant of the occurrence of the event. (Paper 1 at 32-33, 44.)
`
`The petitioned claims, under the Board’s construction, do not require a
`
`particular form of notification. For example, the Board’s construction does not
`
`require that the notification be in the form of a sentence. Any type of notification
`
`works under the Board’s construction. And Bennett sends a verification code as its
`
`11
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`form of notification. (Paper 1 at 32-33, 11.) As a result, Petitioner’s argument that
`
`Bennett discloses re-verifying registrants upon
`
`the occurrence of certain
`
`transactions includes notifying the user of the occurrence of the notification event
`
`in accordance with the Board’s claim construction. (Id.) Petitioner expressly
`
`described this position in its Petition. (Id.)
`
`Based on the foregoing, Petitioner requests the Board rehear its decision
`
`denying
`
`institution of
`
`the Petition
`
`in
`
`light of Bennett’s disclosure of
`
`communicating a verification code to the user upon the occurrence of certain
`
`transactions as part of the reverification process.
`
`V. CONCLUSION
`For the foregoing reasons, Petitioner requests that:
`
`(1) The Board rehear its institution denial of claims 1, 2, 4, and 5 in light
`
`of the Petition’s arguments that Bennett and Bennett in view of Rolfe teach and
`
`render obvious notifying the user of the occurrence of the notification event; and
`
`(2) The Board rehear its denial of institution of all claims in light of the
`
`Petition’s argument that Bennett teaches notifying the user of the occurrence of the
`
`notification event in the form of communicating a verification code to the user
`
`upon the occurrence of certain transactions as part of the reverification process.
`
`
`
`12
`
`
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`
`
`
`Respectfully submitted,
`
` / Wayne Stacy /
`Wayne Stacy
`Reg. No. 45,125
`
`
`
`
`
`
`
`
`
`
`
`13
`
`
`July 29, 2016
`
`
`
`
`
`
`
`
`
`
`
`
`

`
`Case IPR2016-00450
`Patent No. 8,462,920
`
`CERTIFICATE OF SERVICE
`
`I hereby certify pursuant to 37 C.F.R. §§ 42.6(e) and 42.105(a) that the
`
`foregoing PETITONER’S REQUEST FOR REHEARING UNDER 37 C.F.R.
`
`§ 42.71(c) and CERTIFICATE OF SERVICE was served electronically via email
`
`on the following:
`
`Elena McFarland
`(EMCFARLAND@shb.com)
`Tawni Wilhelm
`(TWILHELM@shb.com, TeleSignIPR@shb.com)
`Jesse Camacho
`(JCAMACHO@shb.com)
`Counsel for Patent Owner, TeleSign Inc.
`Shook, Hardy & Bacon LLP
`2555 Grand Blvd.
`Kansas City, MO 64108
`
`Amy Foust
`(AFOUST@shb.com)
`Counsel for Patent Owner, TeleSign Inc.
`Shook, Hardy & Bacon LLP
`201 S. Biscayne Blvd., Suite 3200
`Miami, FL 33131
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
` / Wayne Stacy /
`Wayne Stacy
`Reg. No. 45,125
`
`
`
`
`
`
`
`14
`
`
`
`134206088 v4
`
`
`
`
`
`
`
`July 29, 2016

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