throbber
IN THE UNITED STATES PATENT AND TRADEMARK OFFICE
`
`In re Reexamination of US. Patent of:
`
`Toshiharu Enmei
`
`Control No.: 90/011,692
`
`Patent No.: 7,057,605
`
`Issued: June 6, 2006
`
`For: Portable Communicator
`
`vvvvvvvvvv
`
`Examiner: Nguyen, Minh
`
`Group Art Unit: 3992
`
`October 21, 2011
`
`DECLARATION OF STEVEN ISAAC UNDER 37 C.F.R.
`
`1.132
`
`I am of lawful age and if called upon to testify, I could and would competently testify to
`
`the facts set for below.
`
`1.
`
`I am currently the CEO of TouchFire, Inc., a startup company in the tablet
`
`computer space.
`
`2.
`
`In 1979, I was awarded a Bachelor degree in Computer Science from the State
`
`University of New York at Buffalo.
`
`3.
`
`From 1979-1982, I was employed by NCR where I developed firmware for a pre-
`
`production NCR minicomputer.
`
`4.
`
`From 1982-1985, I was employed by Burroughs Corporation where I worked in the
`
`semiconductor research division developing an operating system for a new line of reduced
`
`instruction set CPUs.
`
`1
`
`EXHIBIT
`Petitioner . Kyocera
`
`PX 1047
`
`Kyocera PX 1047_1
`
`

`

`
`
`5.
`
`From 1985-1988, I was employed by Sun Microsystems where I led a group that
`
`ported NFS (Network File System) to non-Sun systems and made NFS an industry standard.
`
`6.
`
`From 1988-1993, I was employed by GO Corporation (“GO”). I joined GO as the
`
`Team Manager for the Filesystem and Connectivity group. GO developed a mobile operating
`
`system for portable tablet computers named PenPoint. I was the seventh employee at GO, and
`
`my job was to develop the storage and connectivity strategy for PenPoint, and to then implement
`
`it. PenPoint was one of the world’s first operating systems specifically designed for mobile
`
`operation, and I invented numerous new approaches and technologies that addressed the unique
`
`requirements and characteristics of a mobile environment. GO shipped the first version of
`
`PenPoint in 1991. I was subsequently promoted to Principal Engineer, which was the title I had
`
`until I left GO. When I first joined GO, the company was developing both hardware and
`
`software. I participated in some of the connectivity aspects of the hardware design, and I was
`
`responsible for the software in this area. Subsequently, GO spun off its hardware group into a
`
`separate company, EO, Inc. (“EO”). EO was then acquired by AT&T. Thereafter, EO acquired
`
`GO. I worked in the merged EO/GO organization during my last year at the company. EO built
`
`two portable tablet computers that ran PenPoint exclusively, namely the EO 440 and 880
`
`Personal Communicators. I was responsible for the connectivity aspects of the PenPoint software
`
`that ran on these machines.
`
`7.
`
`From 1993-2000, I was at Microsoft Corporation where I was Group Program
`
`Manager for a research project that became Windows CE. I was on the Internet Explorer 1.0
`
`team and was responsible for the IE home page. I then published the first MSN.COM, and
`
`developed the first customizable home page on the Internet. The technology that my team
`
`developed for this became Active Server Pages 1.0. I then went to the Developer Tools Division
`
`2
`
`Kyocera PX 1047_2
`
`

`

`
`
`and managed a group that was responsible for the design time and portions of the runtime for
`
`ASP.NET 1.0.
`
`8.
`
`From 2008-2010, I was at Earth Class Mail as Vice President of Product where I led
`
`the product direction for the company. Earth Class Mail gives customers online access and
`
`control of their postal mail.
`
`9.
`
`In 2010, I started TouchFire, Inc. (“TouchFire”). TouchFire is a startup that is
`
`developing a product that provides a better way to input information on tablet computers.
`
`10.
`
`I am named as an inventor or co-inventor on 10 issued U.S. patents: 5,724,492,
`
`5,959,621, 6,091,411, 6,216,143, 6,421,694, 6,424,981, 6,632,248, 6,647,531, 6,915,454,
`
`7,451,352.
`
`11.
`
`I have reviewed United States Patent No. 7,057,605, the named inventor of which is
`
`Toshiharu Enmei, hereinafter referred to as the “’605 Patent.” The first page of the ’605 patent
`
`shows that a Japanese application was filed on November 9, 1992. For purposes of this
`
`Declaration, the term “application date” of the ’605 patent means November 9, 1992.
`
`12. Each of the functional components disclosed and claimed by the ‘605 patent,
`
`typically illustrated as simple block diagrams, was well known in the art at the time of the
`
`application date. The ‘605 patent merely purports to have invented a multifunctional laptop
`
`device aggregated from a multitude of known components and technologies.
`
`13. The EO Personal Communicators running
`
`the PenPoint operating system
`
`implemented the key features described in the ‘605 patent. The EO Personal Communicators are
`
`portable, battery operated, handheld devices – for example, the dimensions of the main body of
`
`3
`
`Kyocera PX 1047_3
`
`

`

`
`
`the EO 440 are 10.8" x 7.1" x 0.9", and it weighed 2.3 lbs. The EO Personal Communicators
`
`provided both voice and data communication over the analog cellular network that was in use in
`
`the 1991 timeframe. Data capabilities included sending and receiving email, sending and
`
`receiving faxes, and remote file access to desktop PCs and networks. Voice capabilities included
`
`making and receiving voice calls, monitoring roaming status, keeping track of call times,
`
`displaying signal strength, managing phone numbers and dialing phone numbers via a built-in
`
`address book. For talking and listening to cellular voice calls, the EO Personal Communicators
`
`utilized a telephone handset or a headset worn by the user.
`
`14.
`
`I reviewed the Patent Owner’s Statement filed in this reexamination, including the
`
`May 13, 2011 Declaration of Michael Kotzin, Ph.D., hereinafter referred to as the “Kotzin
`
`Declaration” or simply “Kotzin.”
`
`15.
`
`I have reviewed an English translation of excerpts of Japanese Patent Publication
`
`No. JP H3-235116, the named inventor of which is Inoue, hereinafter referred to as the “Inoue.”
`
`16. A person skilled in the art as of the application date would have understood that the
`
`Inoue reference discloses a multifunctional laptop word processor equipped with various
`
`features, including, for example, a touch screen, floppy disk drive, memory, fax machine,
`
`scanner, printer interface, a keyboard and a telephone handset.
`
`17. Despite disclosing fax functionality, it is incorrect to suggest that the Inoue
`
`reference “requires” fax functionality. Like the device of the ‘605 patent, fax functionality is just
`
`a feature of the device. For example, the Inoue Translation discloses the following on Page 5:
`
`“E26 is a 1200/300-baud asynchronous communication modem (CCITT V.21, V.22 standards).
`
`When this modem board is inserted into a corresponding connector, the public circuit E14 [sic],
`
`4
`
`Kyocera PX 1047_4
`
`

`

`
`
`used for both telephone and fax, can also be used for PC communication.” Thus, fax
`
`functionality is clearly not required at all times, since the public circuit can also be used at other
`
`times for PC communication.
`
`18. The Inoue reference plainly discloses a touch screen display for inputting
`
`commands. (Inoue Translation, Page 6.). As was well known in the art as of the application date,
`
`commercially available touch-sensitive LCD displays were overlaid with a digitizer (i.e., a touch
`
`layer). This is because commercially available LCD displays were not able to detect an input.
`
`Commercially available LCD displays as of the application date were unable to receive inputs
`
`without a secondary device, such as a digitizer. As a result, the “display device” claimed in the
`
`‘605 patent simply cannot be a single device capable of both displaying images and receiving
`
`inputs and generating outputs. For this reason, a person skilled in the art as of the application
`
`date would understand that the term “display device” claimed in the ‘605 patent would require
`
`both a digitizer and a display.
`
`19.
`
`I have reviewed European Patent Application No. EP0499012, the named inventor
`
`of which is Zvi Yaniv, hereinafter referred to as the “Yaniv.”
`
`20. The Yaniv reference discloses a hand-held portable communicator enabled for both
`
`voice and data transmission (e.g., fax) over a cellular network. To facilitate user input, the Yaniv
`
`portable communicator also employs a touch screen display.
`
`21. One skilled in the art as of the application date would understand that the Yaniv
`
`reference clearly discloses a compact telecommunications system adapted to send and receive
`
`information in either voice or facsimile fashion by way of a wireless communication
`
`terminal/cellular telephone network. See e.g., Col. 1:3-15.This is confirmed by the Yaniv
`
`5
`
`Kyocera PX 1047_5
`
`

`

`
`
`reference’s statement that the simplest operation of the device is its use as a telephone for voice
`
`communication, whereby a microphone and speaker are provided in the device and either hand-
`
`held or speakerphone operation can be selected. See Col. 4:39-43.
`
`22. Contrary to Dr. Kotzin’s declaration (Kotzin, ¶¶18-25), coupling a fax machine, or
`
`fax functionality, with a cellular device for use over cellular channels was well known as of the
`
`application date, and would not require detailed knowledge about the cellular telephone’s
`
`operation and control. For example, U.S. Patent Number 4,977,609 discloses a simple interface
`
`circuit for adapting an existing facsimile machine to successfully operate through an existing
`
`cellular mobile radiotelephone.
`
`23. Furthermore, the EO 440 and 880 Personal Communicators provided fax
`
`capabilities over cellular channels. The EO devices utilized an “off the shelf” third-party cellular
`
`modem manufactured by Data Race, Inc., of San Antonio, Texas. This modem interfaced directly
`
`to a cellular channel and provided both data and fax capabilities (data throughput rate was
`
`14.4kbps, fax throughput rate was 9.6kbps). I had personal experience prior to the application
`
`date developing communication software for the EO devices, testing them in the lab and in the
`
`field, and using them as an end user. Dr. Kotzin conjectures that the performance of a standard
`
`fax machine would be inadequate due to the susceptibility of cellular channels to various forms
`
`of interference. However, that was simply not the case in my experience. Fax transmission over
`
`cellular channels with an EO device performed quite satisfactorily. The Data Race cellular
`
`modem specifically included technology to overcome the issues Dr. Kotzin describes, such as the
`
`ability to automatically analyze the quality of the cellular link and dynamically adjust modem
`
`speed accordingly.
`
`6
`
`Kyocera PX 1047_6
`
`

`

`
`
`24.
`
`I have reviewed United States Patent No. 5,128,981, the named inventor of which is
`
`Tsukamoto, hereinafter referred to as the “Tsukamoto.”
`
`25. The Tsukamoto reference discloses wireless communicators enabled to wirelessly
`
`communicate with a public communication network by way of an office system (“PBX”).
`
`26. The Tsukamoto wireless communicators are enabled to communicate with a public
`
`telephone network by way of a wireless base station (transmitter/relay) and communication
`
`controller that is connected to a public network. See e.g., Col. 5:61-63 and Figure 1.
`
`27. One skilled in the art as of the application date would have concluded that
`
`Tsukamoto is enabled to communicate with a public network, and that adapting a private
`
`network device to operate over a public network would require minimal modifications. For
`
`example, U.S. Patent No. 5,127,041 provides a simple system and method for adapting a
`
`computer to operate over a cellular network.
`
`28.
`
`I have reviewed United States Patent No. 5,117,449, the named inventor of which is
`
`Metroka, hereinafter referred to as the “Metroka.”
`
`29. Metroka teaches an integrated paging and radiotelephone apparatus that combines
`
`paging and cellular radiotelephone functions in a single unit. Metroka notes that the apparatus
`
`consists of dual receivers allowing reception of paging signals simultaneously with cellular
`
`radiotelephone signals. See e.g., Col. 2:10-14.
`
`30. ADC incorrectly concludes that the Metroka cellular radiotelephone does not
`
`comply with any cellular network because the radiotelephone is user-tunable. Based on this
`
`incorrect conclusion, ADC goes on to mischaracterize the Metroka cellular radiotelephone as a
`
`7
`
`Kyocera PX 1047_7
`
`

`

`
`
`“push-to-talk, simplex, radio system known as a ‘walkie-talkie’.” (Patent Owner’s Statement, p.
`
`22-23). The Metroka patent, however, clearly states that the Metroka cellular radiotelephone
`
`does in fact participate in a standard cellular telephone network - one that provides access to the
`
`landline telephone system and charges users for incoming and outgoing calls: “The cellular
`
`radiotelephone allows a mobile user to place a call anywhere within an area covered by the
`
`cellular communications system antennas. The cellular radiotelephone allows the user to access
`
`the landline telephone system to conduct two way telephone conversations. The cellular
`
`radiotelephone user can also receive telephone calls on the radiotelephone … the radiotelephone
`
`user typically pays for incoming as well as outgoing calls.” Col. 1:39-52.
`
`31. Despite the clear teachings in Metroka that it discloses a standard cellular
`
`radiotelephone, ADC cites three passages in Metroka to allegedly show that its cellular
`
`radiotelephone receiver is user-tunable.
`
`1.
`
`ADC states that “Metroka describes how the microprocessor controls the
`
`“frequency control of the radiotelephone. (Col. 3, Ins. 15-20).” (Patent
`
`Owner’s Statement, p. 23) The actual text in the patent is: “The
`
`microprocessor (106) handles both the radiotelephone and the paging
`
`functions,
`
`including
`
`frequency control of
`
`the
`
`radiotelephone.”
`
`Cellular networks operate on multiple frequencies and cellular phones are
`
`often required to switch frequencies as they travel from cell to cell.
`
`However, this occurs without any user intervention; in fact, the user is
`
`unaware that this frequency switching is taking place. The microprocessor
`
`that controlled a cellular radiotelephone typically performs this frequency
`
`8
`
`Kyocera PX 1047_8
`
`

`

`
`
`switching task, as set forth in Metroka. Notably, Metroka never states that
`
`there is any user interaction for the frequency control task.
`
`2.
`
`ADC states that “Additionally, Metroka explains that “[I]t it is determined
`
`that the programming command was input, then flow proceeds from (412)
`
`to block (414) where a prompt is displayed on the display (103) asking the
`
`user to input the first of a series of programmable radiotelephone
`
`parameters(frequency) via the keypad (102).” (Patent Owner’s Statement,
`
`p. 23). The actual text of the patent does not contain the denotation
`
`“(frequency)” for the first radiotelephone parameter. In fact, there is no
`
`mention of a radiotelephone parameter for frequency anywhere in the
`
`patent. Also, entering radiotelephone parameters only occurs when the
`
`radiotelephone is in a test mode, not when the radiotelephone is in normal
`
`operation. This can be seen by reviewing the entire text in Col 7: 1-34, not
`
`merely a portion of text taken out of context. This is also shown in Fig. 4.
`
`3.
`
`ADC states that “The paging system is typically a one-way radio
`
`communication system … the keypad can be used to program it via the
`
`microprocessor (106) and synthesizer programming bus (201). In this way,
`
`the user can change the receiving frequency of the secondary receiver
`
`(105) … the first keypad (102) can also program radiotelephone
`
`parameters. These parameters include, but are not limited to, the system
`
`identification number and the user’s telephone number.” The first two
`
`parts of this statement show that the user can change the frequency of the
`
`paging receiver (the secondary receiver). However, there is no mention
`
`9
`
`Kyocera PX 1047_9
`
`

`

`
`
`anywhere in the patent that the user can change the frequency of the
`
`radiotelephone receiver. The third portion of the statement describes the
`
`typical first-time setup for a cellular phone – setting the system
`
`identification number and setting the user’s telephone number. The patent
`
`allows for other parameters to be set, but never mentions radiotelephone
`
`frequency as one of those parameters.
`
`32.
`
`In summary, the radiotelephone described in Metroka is a standard cell phone that
`
`works with a standard cellular network.
`
`33.
`
`I have reviewed Japanese Patent Publication No. JP H04-116449, the named
`
`inventor of which is Yutaka Yamagishi, hereinafter referred to as the “Yamagishi.”
`
`34.
`
`It is my belief that images displayed by the Yamagishi display would not be
`
`distorted. It is common to use layers of different materials when constructing a digitizer overlay
`
`for use with an LCD device. For instance, digitizer layers are often formed from two very thin
`
`glass layers with top and bottom conductive layers (ITO Glass or Film) placed in between. To
`
`protect the outermost glass layer from scratches, it is also common to install a protective layer
`
`formed form a third material. Because the various layers are very thin, closely packed and clear,
`
`the image being displayed by an LCD panel is not distorted when viewed through the digitizer.
`
`35. To maintain the narrow air gap between the conductive layers, small spacer dots are
`
`often used. Due to the size and clarity of the spacer dots, they do not have a noticeable impact on
`
`the clarity of the LCD image as viewed through the digitizer.
`
`10
`
`Kyocera PX 1047_10
`
`

`

`
`
`I declare under penalties of perjury set out in 18 U.S.C. §1001 that the foregoing
`
`statements are true and correct to the best of my knowledge
`
`
`
`Date : ____10/21/2011___________
`
`
`
`
`
`
`
`
`
`
`
`
`________________________________
`
` Steven Isaac
`
`11
`
`Kyocera PX 1047_11
`
`

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