throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`UNITED SERVICES AUTOMOBILE ASSOCIATION,
`
`
`
`Petitioner
`
`
`
`v.
`
`NADER ASGHARI-KAMRANI and KAMRAN ASGHARI-KAMRANI,
`
`Patent Owners
`
`
`
`U.S. PATENT NO. 8,266,432
`
`
`
`CBM2016-00063 and CBM2016-00064
`
`
`
`PATENT OWNER’S RESPONSE TO PETITIONER’ MOTION FOR
`OBSERVATION REGARDING CROSS EXAMINATION OF REPLY
`WITNESS DR. SETH NIELSON
`
`
`
`
`
`

`

`Patent Owner (“PO”) submits the following response to Petitioner’s Motion
`
`for Observations regarding the March 28, 2017, cross-examination testimony of
`
`Dr. Seth Nielson (paper 33).
`
`
`
`I. Petitioner’s Motion for Observation was not Expressly Authorized.
`
`The PTAB rules state (with emphasis added):
`
`The party taking the cross examination files the observations. The
`
`opposing party may file a response to an observation. The opposing
`
`party may not file observations without express prior authorization.
`
`(Fed. Reg. vol. 66, no. 155, p. 48768.)
`
`
`
`Pursuant to the above rule, the PO took the cross examination of Dr. Nielson
`
`and filed observations on April 7, 2017 (paper 31). Thus, the Petitioner was
`
`permitted under the Scheduling Order to file a response to PO’s observations by
`
`April 24, 2017. However, the Petitioner also filed a Motion for Observations on
`
`April 10, 2017 (paper 33) without obtaining express prior authorization.
`
`Accordingly, the Board should not enter the Petitioner’s observation (paper 33). If
`
`such paper were entered in error, PO respectfully requests that the Petitioner’s
`
`observation (paper 33) be expunged.
`
`
`
`
`
` 2
`
`

`

`II. Response to Petitioner’s Observation 1.
`
`Petitioner’s Observation 1 attempts to cure Dr. Neilson’s testimony that he
`
`was unaware that PO filed two different PO Responses and the commensurate fact
`
`that Petitioner’s Counsel failed to make Dr. Neilson aware of both papers. As
`
`evident later in Dr. Neilson’s deposition, Petitioner’s counsel also did not make Dr.
`
`Neilson aware of U.S. Patent No. 7,356,837 (exhibit 1005), the grandparent of the
`
`U.S. Patent No. 8,266,432 (“the ‘432 Patent”) when considering the knowledge
`
`possessed by a person of ordinary skill in the art (“POSITA”) at the time of the
`
`invention. (See, e.g., exhibit 2014, page 40, lines 11-18, and page 56, line 17 to
`
`page 57, line 8.) These facts are relevant to the foundation and credibility of Dr.
`
`Nielson’s analysis as to what a POSITA would reasonably conclude regarding
`
`written description support for the claims of the ‘432 Patent at the time of the
`
`invention.
`
` III. Response to Petitioner’s Observation 3.
`
`Petitioner’s Observation 3 attempts to cure Dr. Neilson’s testimony that he
`
`did not consider the disclosure of the ‘837 Patent as being within the presumed
`
`knowledge of a POSITA when analyzing whether the application for U.S. Patent
`
`No. 8,281,129 (“the ‘129 patent, exhibit 2004) provides written description support
`
`for the terms recited in the ‘432 patent. (See, e.g., exhibit 2014, page 40, lines 11-
`
`18, and page 56, line 17 to page 57, line 8.) Instead, as established later in the
`
`
`
`
`
` 3
`
`

`

`deposition, Dr. Nielson’s Declaration only considered the terminology of the ‘432
`
`Patent and the ‘129 Patent in a vacuum and determined whether or not some words
`
`were broader than another. (See, e.g., exhibit 2014, page 65, line 3 to page 67.)
`
`These facts are relevant to the foundation and credibility of Dr. Nielson’s analysis
`
`regarding written description support for the claims of the ‘432 Patent in the ‘129
`
`Patent.
`
`IV. Response to Petitioner’s Observations 4 and 5.
`
`Petitioner’s Observations 4 and 5 are directed to whether a POSITA would
`
`conclude that the “individual” disclosed in the ‘129 patent requires a “trusted
`
`relationship” that affects whether the “individual” provides written description
`
`support for the “user” claimed in the ‘432 patent. However, Dr. Neilson’s later
`
`testimony in the deposition expressly conceded that the “user” recited in the ‘432
`
`Patent is disclosed as having a trusted relationship. (See, e.g., exhibit 2014, on
`
`page 95, line 15 to page 96, line 6.)
`
`V. Response to Petitioner’s Observation 6.
`
`Petitioner’s Observation 6 is directed to whether a POSITA would conclude
`
`that the “dynamic key” disclosed in the ‘129 Patent provides written description
`
`support for the claimed “dynamic code” in the ‘432 Patent. On page 105, line 9 to
`
`page 106, line 9, of Exhibit 2014 Dr. Nielson testified that the ‘129 Patent
`
`
`
`
`
` 4
`
`

`

`discloses each of the elements of the claimed “dynamic code” in the 432 Patent, as
`
`construed by the Board. (See Exhibit. 2010, p. 17, para. 40.)
`
`
`
`Date: April 24, 2017
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
` /Steven L Ashburn/
`Steven L. Ashburn
`
`Reg. No. 56,636
`
`
`
`
`
`
`
`Attorney for Patent Owner
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
` 5
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`CERTIFICATE OF SERVICE
`
`Pursuant to 37 C.F.R. § 42.6(e)(4), the undersigned certifies that on April
`
`24, 2017, a complete and entire copy of this Patent Owner’s Response to
`
`Petitioner’ Motion for Observation Regarding Cross Examination of Reply
`
`Witness Dr. Seth Nielson was provided via electronic mail to the Petitioner’s
`
`counsel of record at the following email addresses:
`
`W. Karl Renner, Lead Counsel
`
`CBM36137-0007CP1@fr.com
`
`CBM36137-0007CP2@fr.com
`
`
`
`Thomas Rozylowicz, First Back-up Counsel
`
`PTABInbound@fr.com
`
`
`
`Timothy Riffe, Back-up Counsel
`
`riffe@fr.com
`
`
`
`
`
`Date: April 24, 2017
`
`
`
`
`
`
`
`
`
`Respectfully submitted,
`
`
`
`
`
`
`
`
`
`
`
`/Steven L Ashburn/
`Steven L. Ashburn
`MH2 TECHNOLOGY LAW GROUP
`LLP
`1951 Kidwell Drive
`Suite 550
`Tysons Corner, VA 22182
`Phone: (703) 917-0000 x138
`Facsimile: (703) 997-4905
`
`
`
`
`
` 6
`
`

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