throbber

`
`
`
`
`
`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`WHATSAPP, INC. AND FACEBOOK, INC.
`Petitioner
`
`v.
`
`TRIPLAY, INC.
`Patent Owner
`
`Inter Partes Review Nos. IPR2016-00717
`U.S. Patent No. 8,874,677
`
`
`
`PETITIONERS’ RESPONSE TO PATENT OWNER’S
`OBSERVATIONS ON TESTIMONY OF MR. KLAUSNER
`
`
`
`
`
`
`
`
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`
`Pursuant to the Board’s September 7, 2016 Scheduling Order (Paper 16),
`
`Petitioners WhatsApp, Inc. and Facebook, Inc. (“Petitioners”) respond as follows
`
`to TriPlay, Inc.’s (“Patent Owner”) Observations on Testimony of Mr. Klausner
`
`(Paper 29).
`
`
`
`RESPONSES TO PATENT OWNER’S “OBSERVATIONS”
`The Patent Owner’s motion for observation improperly attempts to raise
`
`substantive arguments about the merits of the underlying petition. See Scheduling
`
`Order (Paper 16), at 6; see also Office Patent Trial Practice Guide, 77 Fed. Reg.
`
`48,756, 48,768 (Aug. 14, 2012) (“An observation (or response) is not an
`
`opportunity to raise new issues, re-argue issues, or pursue objections.”). As
`
`demonstrated below, the Patent Owner’s proposed observations do not relate Mr.
`
`Klausner’s testimony to any precisely identified argument but instead improperly
`
`attempt to raise arguments and address substantive issues. See Medtronic, Inc. v.
`
`Nuvasive Inc., IPR2013-00506, Paper 37 at 2-4 (finding that “the motions for
`
`observations contain arguments and are excessively long, and, thus, improper”).
`
`For the convenience of the Board, the Petitioners will adopt the Patent Owner’s
`
`numbering.
`
`Response to Observation #1
`
`The Patent Owner argues that Mr. Klausner’s testimony “contradicts the
`
`
`
`1
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`statement that SIP provides no ability to adapt streaming video based on terminal
`
`characteristics.” (Observations, at 3.) The Patent Owner mischaracterizes
`
`Petitioners’ arguments. Petitioners did not argue that “SIP provides no ability to
`
`adapt streaming video based on terminal characteristics.” Rather, as expressly
`
`stated in the section header to Petitioner’s argument at pages 7 to 9 of the Reply
`
`Petition, Petitioners more specifically argued
`
`that “SIP Streaming Video
`
`Transcoding Does Not Adapt Videos for Display Characteristics.” (Petitioners’
`
`Reply, at 7 (underlining in original).)
`
`To the extent “the statement that SIP provides no ability to adapt streaming
`
`video based on terminal characteristics” refers to a “statement” in Coulombe ¶ 69
`
`rather than an argument made by Petitioners, the patent owner improperly argues
`
`for a strained interpretation of the term “recipient’s terminal characteristics,” as
`
`used in Coulombe ¶ 69, to manufacture an inconsistency with Mr. Klausner’s
`
`testimony. Coulombe ¶ 69 states:
`
`It is said in SIP that proxies may transcode content. However, the
`scope of this claim was mainly for multimedia sessions (audio or
`video calls) where codecs or the bandwidths between users don’t
`match. In that case, the proxy can use the information in SDP to “fill
`the gap” between the two terminals. There is no mention that such
`adaptation could take place for messaging applications and no
`it should be based on recipient’s
`terminal
`mention
`that
`
`
`
`2
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`
`characteristics.
`
`(Coulombe, Ex. 1003, ¶ 69 (underlining and bolding added).) It is clear that the
`
`term “recipient’s terminal characteristics” used in the context of Coulombe ¶ 69
`
`(emphasized in bold above) refers to characteristics other than “codecs.”
`
`Response to Observation #2
`
`The Patent Owner argues that “when read in proper context, the reference to
`
`‘messaging applications’ in the sentence from ¶ 69 of Coulombe cited by Petitioner
`
`(i.e., ‘There is no mention that such adaptation could take place for messaging
`
`applications and no mention that it should be based on recipient’s terminal
`
`characteristics.’) refers to non-session based SIP instant messaging--not session-
`
`based SIP video streaming.” (Observations, at 4-5 (underlining in original).) To
`
`the extent the Board chooses to consider this improper argument, it should be
`
`rejected. The mere reference to the SIMPLE protocol in the next sentence in
`
`Coulombe ¶ 69 does not indicate that Coulombe intended to limit the term
`
`“messaging applications,” as used in that paragraph, to only “non-session based
`
`SIP instant messaging.” The more straightforward interpretation is that the
`
`SIMPLE protocol is discussed as an example of existing “messaging applications.”
`
`It is also unclear how this (improper) argument is relevant to what the Patent
`
`Owner refers to as “Petitioner’s active discouragement argument at pages 7 to 9 of
`
`
`
`3
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`the Reply Petition.” (Observations, at 4.) Those pages do not argue that the term
`
`“messaging applications” in Coulombe ¶ 69 refers to “session-based SIP video
`
`streaming.” (Petitioners’ Reply, at 7-9.) In fact, those pages do not contain any
`
`references to the term “messaging application” other than in a block quote of
`
`Coulombe ¶ 69 on page 7. (Id.)
`
`Response to Observation #3
`
`The Patent Owner argues:
`
`“[A] person of ordinary skill would understand” [as Mr. Klausner
`testified] the “terminal characteristics” disclosed in Coulombe include
`formats supported and such testimony is contrary to Petitioner’s
`reading of Coulombe as teaching “SIP provides no ability to adapt
`streaming video ‘based on the recipient’s terminal characteristics,’”
`given Coulombe’s teachings (as discussed above) of adapting video
`where formats supported (a ‘terminal characteristic’) do not match.
`
`(Observations, at 6 (second bracket in original).) To the extent the Board chooses
`
`to consider this improper argument, it should be rejected. The Patent Owner asked
`
`Mr. Klausner about the use of the term “terminal characteristics” in ¶ 2 of
`
`Coulombe and did not ask him about the use of the term “recipient’s terminal
`
`characteristics” in ¶ 69. As discussed above in Response to Observation #1, it is
`
`clear that the term “recipient’s terminal characteristics,” as used in the context of
`
`Coulombe ¶ 69, refers to characteristics other than “codecs.”
`
`
`
`4
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`Response to Observation #4
`
`The Patent Owner argues that “Mr. Klausner admits that video will not
`
`display if format not supported and, thus, Coulombe discloses that SIP adapts
`
`video based on display capabilities (in view of its disclosure discussed above of
`
`adapting video where formats supported do not match).” (Observations, at 7.) The
`
`Patent Owner’s argument and gloss about Mr. Klausner’s testimony is improper in
`
`a motion for observations, for the reasons previously mentioned. The Patent
`
`Owner has also omitted other testimony from Mr. Klausner at the deposition that
`
`provides further context on this topic:
`
`Q. We talked previously about codecs, and that refers to hardware
`and/or software that’s installed on a computer to enable
`decoding and displaying particular formats?
`
`A. No. A codec is not for displaying; a codec is for decoding what
`has been encoded.
`
`Q. Okay. So a codec would refer to hardware and/or software
`that’s installed on a computer to enable the encoding and
`decoding of particular formats?
`
`I would say a codec is intended for encoding and decoding a
`particular format.
`
`A.
`
`. . .
`
`Q. Okay. And a computer includes a terminal?
`
`
`
`5
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`
`A. Depending on the purpose for which the computer is prepared,
`it may or may not include a display.
`
`. . .
`
`Q. And as we talked about before when we talked about the second
`paragraph of Coulombe, Coulombe does list format supported
`as a terminal characteristic, correct?
`
`A. Yes. And as I’ve said many times today, Coulombe, I think the
`person of ordinary skill would understand Coulombe to mean
`the entire recipient side that includes the physical display as
`well as the -- particularly, the programs and the hardware that
`are sensitive to formats that are supported. The display, of
`course, not sensitive to supported formats.
`
`(Ex. 2010, at 13:17-14:14, 36:2-12 (underlining added); see also id., 16:10-17:1.)
`
`Response to Observation #5
`
`This observation relies on mischaracterizations of Petitioners’ arguments
`
`and Mr. Klausner’s testimony. The word “criticism,” or any form of it, appears
`
`nowhere in “pages 7 to 9 of the Reply Petition.” (Observations, at 9.) Rather,
`
`Petitioners argued that ¶ 69 of Coulombe “makes clear that existing SIP
`
`techniques did not adapt video based on the display capabilities of the recipient’s
`
`terminal.” (Petitioners’ Reply, at 8 (underlining in original) (bold italics added);
`
`see also id. at 7 (section header titled “SIP Streaming Video Transcoding Does Not
`
`
`
`6
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`Adapt Videos for Display Characteristics”) (underlining in original).) This
`
`argument is wholly consistent with Mr. Klausner’s testimony that the sentence in ¶
`
`69 cited by the Patent Owner is not a “criticism,” but “a statement of Coulombe’s
`
`understanding based on ¶ 64, where he is listing the elements that are novel
`
`compared to the present SIP related specifications.” (Observations, at 8 (quoting
`
`Ex. 2010, 36:22-37:1) (bold italics added); see also Ex. 2010, 29:15-30:1.)
`
`Response to Observation #6
`
`The purported relevance of Patent Owner’s (improper) argument that
`
`“SIMPLE is a real time system and not an email system and that the contents are
`
`intended to be small in size,” (Observations, at 10), relies on a mischaracterization
`
`of Petitioners’ proposed combination. Petitioners never proposed “using SIP
`
`instant messaging to attach a video,” as the Patent Owner contends. (Id.
`
`(underlining added).) To the contrary, “Petitioner’s argument at page 3 of
`
`Petitioner’s Reply,” (id.), expressly states that “Coulombe is not limited to ‘instant’
`
`messaging,” and cites to the SIMPLE standard because it “provides insight into the
`
`knowledge of persons of ordinary skill in the art regarding how to use SIP in a
`
`messaging system.” (Petitioners’ Reply, at 3 (underlining added).) There is
`
`simply no basis to (improperly) suggest that the Coulombe messaging system, on
`
`which Petitioners’ proposed combination relies, must conform to all of the
`
`
`
`7
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`requirements of SIMPLE. (Klausner Reply, Ex. 1028, ¶ 5 n. 2.) The Patent Owner
`
`has also omitted other testimony from Mr. Klausner at the deposition on the point
`
`that Coulombe is not limited to instant messaging. (Ex. 2010, 42:14-24, 56:17-
`
`57:5.) And even assuming that messages in Coulombe are “intended to be small in
`
`size” (Observations, at 10), this poses no obstacle to Petitioners’ proposed
`
`combination because, as Petitioners have explained, “the size of a video file
`
`depends on its length and resolution, and could be just a few frames in length.”
`
`(Petitioners’ Reply, at 6; see also Klausner Reply, Ex. 1028, ¶¶ 12-16.)
`
`Response to Observation #7
`
`The purported relevance of Patent Owner’s (improper) argument that “email
`
`is not the common usage of an instant messaging system and that that [sic] the
`
`SIMPLE protocol does not have any discussion of the usage of the protocol as an
`
`email
`
`system with attachments,”
`
`(Observations, at 12),
`
`relies on a
`
`mischaracterization of Petitioners’ proposed combination. As explained above in
`
`Response to Observation #6, Petitioners never proposed “using SIP instant
`
`messaging to attach a video” (id.). (See Petitioners’ Reply, at 3; see also Ex. 2010,
`
`42:14-24.) And there is simply no basis to (improperly) suggest that the Coulombe
`
`messaging system, on which Petitioners’ proposed combination relies, must
`
`conform to all of the requirements of SIMPLE. (Klausner Reply, Ex. 1028, ¶ 5 n.
`
`
`
`8
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`2; see also Ex. 2010, 56:17-57:5.) Rather, Petitioners cited to the SIMPLE
`
`protocol because, as an example of a SIP messaging system that had used MIME to
`
`transport message data, it “confirms that it would have been technologically trivial
`
`for a message sent using SIP (such as a message in Coulombe) to include a video.”
`
`
`
`By:
`
`
`
`
`
`Respectfully submitted,
`
`/ Heidi L. Keefe /
`Heidi L. Keefe
`Reg. No. 40,673
`Counsel for Petitioners
`
`(Petitioners’ Reply, at 3-4.)
`
`
`
`Dated: May 12, 2017
`
`COOLEY LLP
`ATTN: Patent Group
`1299 Pennsylvania Ave., NW, Suite 700
`Washington, DC 20004
`Tel: (650) 843-5001
`Fax: (650) 949-7400
`
`
`
`
`
`
`9
`
`

`

`Petitioners’ Response to Observations
`on Cross-Examination
`IPR2016-00717
`
`
`CERTIFICATE OF SERVICE
`
`
`
`I hereby certify, pursuant to 37 C.F.R. Section 42.6, that a complete copy of
`the attached PETITIONERS’ RESPONSE TO PATENT OWNER’S
`OBSERVATIONS ON TESTIMONY OF MR. KLAUSNER and related
`documents, are being served via electronic mail on the 12th day of May, 2017,
`upon the counsel of record for the patent owner as follows:
`
`Barry Schindler
`SchindlerB@gtlaw.com
`Greenberg Traurig LLP
`njdocket@gtlaw.com
`
`Jeremy J. Monaldo
`Fish & Richardson PC
`monaldo@fr.com
`
`/ Heidi L. Keefe /
`Heidi L. Keefe
`Reg. No. 40,673
`
`
`
`
`
`DATED: May 12, 2017
`
`COOLEY LLP
`Patent Docketing
`1299 Pennsylvania Ave. NW, Suite 700
`Washington, D.C. 20004
`Tel: (650) 843-5001
`Fax: (650) 849-7400
`
`
`
`
`
`1
`
`

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