throbber
IN THE UNITED STATES DISTRICT COURT
`FOR THE EASTERN DISTRICT OF TEXAS
`MARSHALL DIVISION
`
`E-WATCH, INC. ET AL.,
`
`Plaintiffs,
`
`
`
`v.
`



`§ 2:13-cv-1061
`§ LEAD CASE



`§ 2:13-CV-01063



`
`PLAINTIFFS’ DISCLOSURE OF ASSERTED CLAIMS AND
`PRELIMINARY INFRINGEMENT CONTENTIONS AND
`ACCOMPANYING DOCUMENT PRODUCTION (LOCAL P.R. 3-1 AND 3-2)
`TO DEFENDANTS HTC CORPORATION AND HTC AMERICA, INC.
`
`
`
`
`
`
`
`
`
`
`APPLE, INC., ET AL.
`
`HTC CORPORATION AND
`HTC AMERICA, INC.,
`
`
`Defendants.
`
`Pursuant to CV-83, P.R. 3-1 and 3-2, Plaintiffs e-Watch, Inc. and e-Watch Corporation
`
`(collectively, “e-Watch”), by and through its undersigned attorneys, state as follows:
`
`I.
`DISCLOSURE OF ASSERTED CLAIMS AND INFRINGEMENT CONTENTIONS
`
`(A) Each claim of each patent in suit that is allegedly infringed by each opposing party;
`
`its
`the status of
`to e-Watch and
`information presently available
`Based on
`investigation, e-Watch alleges infringement of certain claims of U.S. Patent No.
`7,365,871 (the “’871 patent”) and U.S. Patent No. 7,643,168 (the “168 patent”) by
`defendants HTC Corporation and HTC America, Inc. (collectively, “HTC”). The specific
`asserted patent and associated claims relative to HTC are individually enumerated in the
`claim charts attached hereto. e-Watch reserves the right to amend and/or supplement the
`identification of asserted claims as discovery progresses, in response to the Court’s claim
`construction and otherwise in accordance with the Local Patent Rules and the Court’s
`Docket Control Order.
`
`Separately for each asserted claim, each accused apparatus, product, device, process,
`method, act, or other instrumentality (“Accused Instrumentality”) of each opposing
`party of which the party is aware. This identification shall be as specific as possible.
`Each product, device, or apparatus which, when used, allegedly results in the practice
`of the claimed method or process;
`
`
`(B)
`
`1
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 1 of 27
`
`

`
`
`
`
`(C)
`
`Based on information presently available to e-Watch and the status of its investigation, e-
`Watch provides the Attachments hereto, including claim charts identifying each Accused
`Instrumentality for each asserted claim. e-Watch reserves the right to amend and/or
`supplement the identification of each Accused System as discovery progresses, in
`response to the Court’s claim construction and otherwise in accordance with the Local
`Patent Rules and the Court’s Docket Control Order.
`
`A chart identifying specifically where each element of each asserted claim is found
`within each Accused Instrumentality, including for each element that such party
`contends is governed by 35 U.S.C. § 112(6), the identity of the structure(s), act(s), or
`material(s) in the Accused Instrumentality that performs the claimed function;
`
`The attachments hereto reflect the present infringement contentions of e-Watch based on
`information reasonably available to it as of this date. e-Watch reserves the right to seek to
`amend, supplement or narrow these contentions as discovery progresses, in response to
`the Court’s claim construction and otherwise in accordance with the Local Patent Rules
`and the Court’s Docket Control Order.
`
`(D) Whether each element of each asserted claim is claimed to be literally present or
`present under the doctrine of equivalents in the Accused Instrumentality;
`
`Based on the information currently available to e-Watch, each element of each asserted
`claim appears to be literally present. To the extent any element is not found to be literally
`present, e-Watch asserts an equivalent element is present having insubstantial differences.
`Following discovery regarding
`the defendants’ products,
`including confidential
`information, source code and technical specifications pertaining to the Accused System,
`e-Watch reserves the right to seek leave to amend or supplement its allegations under the
`doctrine of equivalents. e-Watch further reserves the right to amend and/or supplement its
`contentions relative to the doctrine of equivalents in response to the Court’s claim
`construction and otherwise in accordance with the Local Patent Rules and the Court’s
`Docket Control Order.
`
`(E)
`
`For any patent that claims priority to an earlier application, the priority date to which
`each asserted claim is entitled; and
`
`The asserted claims of the ‘871 patent and the ‘168 patent are entitled to a priority date of
`January 12, 1998 based on U.S. Application No. 09/006,073.
`
`(F)
`
`If a party claiming patent infringement wishes to preserve the right to rely, for any
`purpose, on the assertion that its own apparatus, product, device, process, method, act
`or other instrumentality practices the claimed invention, the party must identify,
`separately for each asserted claim, each such apparatus, product, device, process,
`method, act, or other instrumentality that incorporates or reflects that particular claim.
`
`Not applicable.
`
`
`
`
`
`2
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 2 of 27
`
`

`
`
`
`Dated: April 4, 2014
`
`
`
`
`
`
`
`
`
`
`
`By:
`
`Respectfully submitted,
`
`
`
` /s/ Christopher V. Goodpastor
`Christopher V. Goodpastor
`State Bar No. 00791991
`LEAD ATTORNEY
`Mikal C. Watts
`State Bar No. 20981820
`WATTS GUERRA LLP
`811 Barton Springs Road, Suite 725
`Austin, Texas 78704
`Telephone: (512) 479-0500
`Facsimile: (512) 479-0502
`Email: cgoodpastor@wattsguerra.com
` mcwatts@wattsguerra.com
`
`Francisco Guerra, IV
`State Bar No. 00797784
`WATTS GUERRA LLP
`300 Convent Street, Suite 100
`San Antonio, Texas 78205
`Telephone: (210) 527-0500
`Facsimile: (210) 527-0501
`Email: fguerra@wattsguerra.com
`
`Andrew G. DiNovo
`State Bar No. 00790594
`Adam G. Price
`State Bar No. 24027750
`Chester J. Shiu
`State Bar No. 24071126
`Stefanie T. Scott
`State Bar No. 24061617
`Gregory S. Donahue
`State Bar No. 24012539
`DINOVO PRICE ELLWANGER & HARDY, LLP
`7000 N. MoPac Expressway, Suite 350
`Austin, Texas 78731
`Telephone: (512) 539-2626
`Facsimile: (512) 539-2627
`Email: adinovo@dpelaw.com
` aprice@dpelaw.com
` cshiu@dpelaw.com
` sscott@dpelaw.com
` gdonahue@dpelaw.com
`
`5
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 3 of 27
`
`

`
`
`T. John Ward, Jr.
`State Bar No. 00794818
`WARD & SMITH LAW FIRM
`P.O. Box 1231
`Longview, Texas 75606-1231
`Telephone: (903) 757-6400
`Facsimile: (903) 757-2323
`Email: jw@wsfirm.com
`
`ATTORNEYS FOR PLAINTIFFS
`e-WATCH, INC. AND
`e-WATCH CORPORATION
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`6
`
`
`
`
`
`
`
`
`
`
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 4 of 27
`
`

`
`
`
`
`Cheng C Ko
`Evan Skinner Day
`Matthew C. Bernstein
`Kevin Patariu
`PERKINS COIE - SAN DIEGO
`11988 El Camino Real
`Suite 200
`San Diego, CA 92130
`858/720-5712
`Fax: 858/720-5799
`Email: cko@perkinscoie.com
` eday@perkinscoie.com
` mbernstein@perkinscoie.com
` kpatariu@perkinscoie.com
`Via Email
`
`
`Attorneys for HTC Corporation and
`HTC America, Inc.
`
`
`
`CERTIFICATE OF SERVICE
`
`I hereby certify that on the 4th day of April 2014, I served a true and correct copy of the
`foregoing document on all counsel of record in accordance with the Federal Rules of Civil
`Procedure as indicated below.
`
`
`/s/ Christopher V. Goodpastor
`Christopher V. Goodpastor
`
`
`
`
`
`7
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 5 of 27
`
`

`
`
`16. The apparatus according to
`claim 1 and further comprising;
`
`
`
`transmission
`one
`least
`at
`protocol algorithm embodied in
`suitable media;
`
`The accused apparatus includes at least one
`transmission protocol algorithm embodied in
`suitable media. The protocol algorithm
`includes, but is not limited to: Multimedia
`Messaging
`Service,
`WiFi,
`GSM/GPRS/EDGE 850/900/1800/1900 MHz
`(2G), 2.5G, 3G UMTS/HSPA, 3G CDMA
`and 4G – LTE.
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max/
`
`
`
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max
`
`
`
`
`
`HTC'168-IC 01984
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 6 of 27
`
`

`
`The Accused System consists of a portable housing with built
`in wireless connectivity including 2G, 2.5G, 3G, and 4G - LTE
`
`
`
`
`
`
`
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max/
`
`
`
`
`
`HTC'168-IC 01985
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 7 of 27
`
`

`
`
`
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max/
`
`
`
`
`
`Source:
`http://dl4.htc.com/web_materials/Manual/HTC_One_max/HTC_One_max_US_User_Guide.pdf
`(Page 92 of 216)
`
`
`
`WiFi chip enables WiFi
`transmission protocol
`
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max
`
`
`
`processing platform associated
`with
`the
`at
`least
`one
`transmission protocol algorithm,
`the
`associated
`processing
`platform being operable
`to
`execute
`the
`at
`least one
`transmission protocol algorithm,
`the
`associated
`processing
`platform being provided
`the
`compressed visual image data,
`execution of the at least one
`transmission protocol algorithm
`providing the compressed visual
`image data in a transmission
`format, the visual image data in
`a
`transmission format being
`compatible with
`the mobile
`phone for wireless transmission
`by the mobile phone.
`
`HTC'168-IC 01986
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 8 of 27
`
`

`
`Modem and Transceiver chips embedded in the device enabling
`these network transmission Protocols (2G, 2.5G, 3G and 4G)
`
`
`
`
`
`
`
`
`
`Source: http://www.htc.com/us/smartphones/htc-one-max/
`
`
`
`HTC'168-IC 01987
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 9 of 27
`
`

`
`The apparatus includes a processing platform—which includes but is not limited to
`circuitry implementing the baseband (alternatively referred to as digital baseband,
`baseband processor, or modem) and associated supporting circuitry. The processing
`platform may further include circuitry responsible for implementing and supporting
`IEEE 802.11-compliant (WiFi) functionality. The processing platform is associated
`with the protocols enumerated in the previous element. The processing platform
`includes an interface through which it is provided the compressed visual image data.
`The baseband circuitry which receives information, including the compressed visual
`image data, executes the transmission protocol algorithm and provides the information
`in a transmission format:
`
`
`
`
`
`
`
`
`• Baseband circuitry that supports transmission of visual image data via MMS
`will prepare the provided visual image data for transmission by the mobile
`phone in accordance with the MMS protocol. Compressed visual image data
`formats supported by the MMS specification include JPEG for still images and
`MPEG-4 for motion video.
`
`Source: See pg 21 of WAP MMS Client Transactions Version 15-Jan-2002 (downloaded from
`http://www.openmobilealliance.org/tech/affiliates/wap/wap-206-mmsctr-20020115-a.pdf) (aka
`“MMS Client”).
`
`
`
`
`
`HTC'168-IC 01988
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 10 of 27
`
`

`
`Execution of the MMS transmission protocol by the processing platform provides the
`compressed visual image data in a transmission format compatible with the mobile
`phone for wireless transmission by the mobile phone:
`
`
`
`Source: See pg 15 of WAP MMS Architecture Overview Version 25-April-2001 (downloaded
`from http://www.openmobilealliance.org/tech/affiliates/wap/wap-205-mmsarchoverview-
`20010425-a.pdf) (aka “MMSArchitecture”).
`
`
`
`Source: See pg 13 of MMS Architecture.
`
`
`
`HTC'168-IC 01989
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 11 of 27
`
`

`
`
`
`MMS uses WAP WSP/HTTP as an underlying protocol to transfer data,
`including compressed visual image data, from the client, e.g., phone, to the
`MMS Proxy-Relay, e.g., network.
`
`
`
`
`Source: See pg 10 of Multimedia Messaging Service Encapsulation Protocol Version 1.1 Version
`30-October-2002 Open Mobile Alliance OMA-MMS-ENC-v1_1-20021030-C
`
`
`
`HTC'168-IC 01990
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 12 of 27
`
`

`
`
`
`The reference model for the WSP/HTTP used by MMS is given below:
`
`
`
`
`Source: See pg 13 of Wireless Session Protocol 1.0 Candidate Version 1.0 – 20 Sept 2002 Open
`Mobile Alliance OMA-WAP-TS-WSP-V1_0-20020920-C (aka “MMS WSP”)
`
`HTC'168-IC 01991
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 13 of 27
`
`

`
`
`
`
`
`The Bearer Service / Network (e.g., GPRS, HSPA etc) carries the messages on the
`underlying wireless infrastructure.
`
`
`
`
`Source: See pg 10 of MMS WSP.
`
`
`The Bearer Network supported are provided by the Wireless Datagram Protocol (WDP)
`
`
`
`
`Source: See pg 69 of MMS WSP.
`
`
`
`Wireless Datagram
`Protocol (WDP)
`supports such
`wireless protocols
`as GSM, GPRS,
`CDMA per the
`2001 WDP
`specification and
`has been extended
`to support 3G
`protocols such as
`HSDPA / UMTS.
`
`
`
`Source: See pg 20 of Wireless Datagram Protocol Version 14-Jun-2001 Wireless Application
`Protocol WAP-259-WDP-20010614-a (aka “MMS WDP”).
`
`HTC'168-IC 01992
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 14 of 27
`
`

`
`Source:Seepg 25 of MMS WDP.
`
`Source: https://developer.att.com/support/faqs/umts-faqs
`
`
`
`
`
`
`HTC'168-IC 01993
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 15 of 27
`
`

`
`In non-MMS cellular operation over GSM, CDMA, and LTE networks via such
`protocols as GPRS, EDGE, UMTS (3G), HSDPA, HSUPA, CDMA 1XRTT, CDMA
`EV-DO, and LTE the baseband and other circuitry implement a transmission protocol
`algorithm that provides the compressed visual image data in a transmission format
`compatible for wireless transmission by the mobile phone.
`
`
`A transmission plane protocol diagram from the 3GPP Series (GPRS, EDGE,
`UMTS) providing the layered protocol is shown below.
`
`
`
`
`Source: See pg 25 of Digital cellular telecommunications system (Phase 2+); Universal Mobile
`Telecommunications System (UMTS); General Packet Radio Service (GPRS); Service
`description; Stage 2 (3GPP TS 23.060 version 5.13.0 Release 5) (“TS23.060”).
`
`
`
`HTC'168-IC 01994
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 16 of 27
`
`

`
`
`
`
`
`The term “MS” is mobile station, e.g., mobile phone, while “BSS” is for Base
`Station System, e.g., cell tower and related equipment. In A/Gb mode (GPRS,
`EDGE etc) the transmission protocol algorithm includes but is not limited to the
`SNDCP and LLC layers. These layers sit below the IP layer but remain independent
`of the radio interface protocols used for wireless transmission.
`
`
`
`
`Source: See pg 25 of TS23.040.
`
`The RLC, MAC, and RF layers are radio-solution dependent.
`
`
`
`Source:Seepg 25 of TS23.040.
`
`
`
`HTC'168-IC 01995
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 17 of 27
`
`

`
`The LLC implements a transmission protocol algorithm.
`
`
`
`
`
`
`
`Source: See pgs 12-13 of Digital cellular telecommunications system (Phase 2+); Mobile Station -
`Serving GPRS Support Node (MS-SGSN); Logical Link Control (LLC) Layer Specification
`(3GPP TS 44.064 version 5.2.0 Release 5) (“TS44.064”)
`
`
`HTC'168-IC 01996
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 18 of 27
`
`

`
`Source: See pg 15 of TS44.064
`
`
`
`
`HTC'168-IC 01997
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 19 of 27
`
`

`
`
`
`For 3GPP in lu mode (UTRAN / UMTS), e.g., 3G mode, we have the
`following transmission plane protocol diagram
`
`
`
`
`Source: See pg 26 of TS23.060.
`
`
`
`
`
`HTC'168-IC 01998
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 20 of 27
`
`

`
`In lu mode (UTRAN, UMTS/3G) the transmission protocol algorithm
`includes but is not limited to the PDCP layer.
`
`
`
`
`
`
`
`
`Source: See pg 26 of TS23.060
`
`
`Source: See pg 27 of TS23.060
`
`
`
`HTC'168-IC 01999
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 21 of 27
`
`

`
`The PDCP implements a transmission protocol algorithm.
`
`
`
`
`Source: See pgs 9-10 of Universal Mobile Telecommunications System (UMTS); Packet Data
`Convergence Protocol (PDCP) specification (3GPP TS 25.323 version 5.10.0 Release 5)
`(“TS25.323”).
`
`
`
`
`
`
`
`HTC'168-IC 02000
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 22 of 27
`
`

`
`Source: See pg 19 of TS25.323
`
`
`
`In LTE protocols, E-UTRAN, the same protocols and algorithms are used
`as in UTRAN (3G UTMS) with a different L1 interface for the higher
`speed radio technology
`
` .
`
`
`
`
`
`HTC'168-IC 02001
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 23 of 27
`
`

`
`
`
`In CDMA2000 systems (3GPP2), e.g., 1xRTT and EV-DO, similar
`architecture exists.
`
`
`
`
`Source: See pg 1-2 of cdma2000 High Rate Packet Data Air Interface Specification 3GPP2
`C.S0024-A Version 1.0 Date: March 2004 (“CDM2K”)
`
`
`
`
`HTC'168-IC 02002
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 24 of 27
`
`

`
`
`
`Source:See pg 1-3 of CDMA2K.
`
`For the above diagrams the application (and IP layer) would include such software
`running on the processing platform that provides compressed visual image data. Non-
`limiting examples of such software include Camera, Camcorder, and Video applications,
`Facebook, Instagram, Snapchat, twitter etc.
`
`
`
`
`HTC'168-IC 02003
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 25 of 27
`
`

`
`
`
`
`
`
`
`Baseband circuitry that supports IEEE 802.11 (WiFi) will necessarily provide the
`compressed visual image data in a format compatible for wireless transmission by the
`mobile phone over IEEE 802.11 network(s):
`
`
`Source: See pg 24 of Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer
`(PHY) Specifications IEEE Std 802.11™-2007 (“IEEE802.11”)
`
`The 802.11 standard provides for a similar architecture where the
`LLC is typically the IEEE802.2 standard.
`
`
`
`
`Source: See pg 51 of IEEE802.11
`
`HTC'168-IC 02004
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 26 of 27
`
`

`
`
`
`
`
`Source: See pg 55 of IEEE802.11
`
`
`
`
`
`HTC'168-IC 02005
`
`HTC and Samsung, Ex. 1010
`HTC v. E-Watch, IPR2014-00989
`Page 27 of 27

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