throbber

`
`
`
`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`____________
`
`GOOGLE INC., and MOTOROLA MOBILITY LLC,
`
`Petitioners,
`
`v.
`
`Arendi S.A.R.L.,
`
`Patent Owner.
`
`____________
`
`Case No. IPR2014-00452
`
`Patent No. 6,323,853
`____________
`
`DECLARATION OF JOHN V. LEVY, Ph.D.
`
`
`Arendi S.A.R.L. - Ex. 2008
` Page 1 of 16
`
`

`

`I, John V. Levy, make this declaration in connection with the proceeding
`
`identified above.
`
`Qualifications
`
`1.
`
`I am the sole proprietor of John Levy Consulting, a consulting firm
`
`that specializes in consulting on managing development of high tech products,
`
`including computers and software. I have a Bachelor of Engineering Physics
`
`degree from Cornell University, a Master of Science degree in Electrical
`
`Engineering from California Institute of Technology, and a Ph.D. in Computer
`
`Science from Stanford University.
`
`2.
`
`From 1965 to 1966 at Caltech, my field of study was information
`
`processing systems. My coursework included systems programming, including the
`
`construction of compilers and assemblers. From 1966 to 1972, during my graduate
`
`study at Stanford, my field of study was computer architecture and operating
`
`systems. My coursework included computer systems design, programming and
`
`operating systems. During my employment at Stanford Linear Accelerator Center
`
`while I was a graduate student at Stanford University, I was a programmer and I
`
`participated in the design and implementation of a real-time operating system for
`
`use in data acquisition, storage and display. My Ph.D. thesis research related to
`
`computer systems organization and programming of multi-processor computers. I
`
`developed and measured the performance of several parallel programs on a
`
`Page 1 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 2 of 16
`
`

`

`simulated 16-processor system. I also studied file systems, disk and tape storage
`
`subsystems, and input/output.
`
`3.
`
`I have been an employee and a consultant for over thirty years in the
`
`computer systems, software and storage industry. After earning my doctorate from
`
`Stanford University in Computer Science, I worked as an engineer at a number of
`
`leading companies in the computer industry, including Digital Equipment
`
`Corporation, Tandem Computer, Inc., Apple Computer, Inc., and Quantum
`
`Corporation.
`
`4.
`
`From 1972 to 1974 at Digital Equipment Corporation I supervised the
`
`development of an input/output channel for high-speed mass storage (disk, drum
`
`and tape), and its implementation for 7 different peripheral units and 3 different
`
`computer systems. From 1974 to 1975 I was project engineer leading the
`
`development of a new computer system. From 1975 to 1976, I supervised an
`
`operating system development group. During this time, I reviewed design changes
`
`and bug reports and fixes for two operating systems. While working for Digital
`
`Equipment Corporation, I wrote a long-term strategic plan for input/output buses
`
`andcontrollersandoperatingsystems,includingtheconversionofmostI/Obuses
`
`to serial implementations. I am the author of a chapter on computer bus design in
`
`the book Computer Engineering, published in 1978 by Digital Press.
`
`Page 2 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 3 of 16
`
`

`

`5.
`
`From 1977 to 1979 I was employed at Tandem Computer, Inc., where
`
`I worked on design of future multiprocessor systems. I also worked on problems
`
`related to distributed (networked) systems including rollback and recovery of
`
`distributed databases.
`
`6.
`
`From 1979 to 1982 I was employed at Apple Computer, Inc., where I
`
`worked on the design of a new computer system, the Lisa, which was a precursor
`
`to the Macintosh. I also supervised hardware and software engineers in the
`
`development of a new local area network.
`
`7.
`
`In 1980-81 I taught an upper-division course at San Francisco State
`
`University titled (cid:210)Input/Output Architecture(cid:211) which dealt with design of I/O
`
`channels, controllers, storage devices and their associated software.
`
`8.
`
`From 1982 to 1992 I consulted for a variety of client companies,
`
`including Apple Computer, Quantum Corporation and Ricoh Co., Ltd., on project
`
`management and product development. Consulting work for Quantum included
`
`working as a temporary supervisor of a firmware development team for a new hard
`
`disk drive. During this time I co-authored a paper, cited in my CV attached as
`
`ExhibitA,onthedesignofafilesystemforwrite-onceopticaldiskdrives,related
`
`to work I did for client Ricoh.
`
`9.
`
`From 1993 to 1998 I was employed at Quantum Corporation, a
`
`manufacturer of hard disk drives, where I formed and managed a new group called
`
`Page 3 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 4 of 16
`
`

`

`Systems Engineering. While in this role I managed, among others, software and
`
`systems engineers who developed hard disk input/output drivers for personal
`
`computers and disk drive performance analysis and simulation software. While at
`
`Quantum, I also led the definition and implementation of high-speed improvements
`
`of the ATA disk interface standard, called Ultra-ATA/33 and /66, which also led to
`
`improvements in the SCSI interface standard. I was also involved in the design of
`
`file systems for hard disks, data compression schemes for disk data, and Ethernet-
`
`connected disk drives. I was Quantum(cid:213)s representative to the Audio/Video
`
`Working Group of the 1394 (FireWire) Trade Association, a Consumer Electronics
`
`industry standards group, and participated in Quantum(cid:213)s work in designing disks
`
`that could record and play back video and audio streams without needing an
`
`intervening computer system.
`
`10.My qualifications for forming the opinions set forth in this report are
`
`listed in this section and in Exhibit A attached, which is my curriculum vitae.
`
`Exhibit A also includes a list of my publications.
`
`11.I am a named inventor on seven United States patents, including
`
`severalrelatedtoinput/outputbusesandstoragesubsystems.Ihavebeen disclosed
`
`as an expert in over 50 cases and have testified at trial and in depositions. A list of
`
`my testimony is attached hereto as Exhibit B. I also have served as a technical
`
`advisor to two United States District Court Judges.
`
`Page 4 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 5 of 16
`
`

`

`12.I regularly teach courses such as (cid:210)Computers — the Inside Story(cid:211) and
`
`(cid:210)The Digital Revolution in the Home(cid:211) at the Fromm Institute for Lifelong
`
`Learning at the University of San Francisco.
`
`Compensation
`
`13.I base my opinions below on my professional training and experience
`
`and my review of documents and materials produced in this litigation. My
`
`compensation for this assignment is $625 per hour. My compensation is not
`
`dependent on the substance of my opinions or my testimony or the outcome of the
`
`above-captioned case.
`
`Information Considered in Forming Opinion
`
`14.I have read United States Patent No. US5923848 to Goodhand
`
`((cid:210)Goodhand(cid:211)), Exhibit 1003. I have relied on my own knowledge and experience
`
`as well as published documents in forming my opinions. In arriving at my
`
`opinions, I have reviewed Goodhand, the Petition in this proceeding, and the (cid:212)853
`
`patent (Exhibit 1001).
`
`15.For purposes of this declaration, in my opinion, a person of ordinary
`
`skill in the art pertaining to the (cid:213)853 Patent corresponds to one in 1998 who had at
`
`least a Bachelor(cid:213)s degree in Computer Science or Electrical Engineering or related
`
`Page 5 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 6 of 16
`
`

`

`discipline and approximately two years of experience designing user applications
`
`or software modules.
`
`United States Patent 5,923,848 to Goodhand
`
`16.Goodhand, Ex. 1003, describes methods and systems for resolving
`
`(cid:210)display names(cid:211) in an address field of an email template by processing the contents
`
`of that address field in the background. (cid:210)Resolving(cid:211) means determining a proper
`
`email address for the intended recipient by finding the display name among
`
`registered users of the system. A (cid:210)display name(cid:211) is a name that has been
`
`associated with a user in the registry (where registered users are recorded).
`
`17.An email template is a well-known form for composing an email
`
`message. For example, Microsoft Outlook, an email viewing and composing
`
`application program, presents a blank email template to the user whenever the user
`
`selects (cid:210)New email(cid:211) or the equivalent command in a menu. Each field in the
`
`template is used for a specific type of information. In particular, the Address or
`
`(cid:210)To:(cid:211) field is used to designate intended recipients of the email being composed.
`
`18.Fig. 8 of Goodhand illustrates the preferred method for resolving
`
`email addresses in a new email in the Goodhand system, from the user point of
`
`view. Flowchart 800 starts at the START 805 circle and proceeds to the (cid:210)Create
`
`New(cid:211) 810 step. At 815, (cid:210)Enter Recipients(cid:213) Addresses,(cid:211) the user enters text
`
`Page 6 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 7 of 16
`
`

`

`(display names) into the Address field. (cid:210)[T]he display names may include all or
`
`part of the recipient(cid:213)s first name, last name, or email alias.(cid:211) Ex, 1003, col. 18,
`
`lines 61-62. Then (cid:210)the user moves the cursor out of the address field and
`
`continues to compose the remainder of the message.(cid:211) (Compose 820 in Fig. 8)
`
`(See also Ex. 1003, col. 18, lines 57-65.) Later, the user returns to Review
`
`Resolved Addresses 825 and, if necessary, correct the addresses (845) before
`
`sending the message (835). The inventive step of Goodhand is to have the
`
`computer resolve the names in the background, i.e., while the user is performing
`
`other actions, such as composing the body of the message. Ex. 1003, col. 16, lines
`
`62-67. The (cid:210)process of matching the display name(s) to an e-mail address or alias
`
`is referred to as (cid:212)resolving(cid:213) the names.(cid:211) Id., col. 16, lines 51-53.
`
`
`
`The (cid:213)853 Patent
`
`19.The (cid:213)853 Patent is addressed to a method and system for retrieving
`
`address (cid:210)first information(cid:211) from a document created by an application program
`
`and completing the information by using a record retrieval program to look, in an
`
`information source, related information, such as mailing address, email address,
`
`telephone number or other information related to the company or person identified
`
`by the first information. The action taken by the method or system is not
`
`conditioned on any action of the user other than an initial activation by a single
`
`Page 7 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 8 of 16
`
`

`

`selection in a menu or other (cid:210)button.(cid:211) Retrieval of second information associated
`
`with the first information proceeds without user intervention and, in appropriate
`
`cases where there is just one associated person or company, the second
`
`information is inserted into the document.
`
`20.Claim 1 of the (cid:212)853 Patent reads in part
`
`upon a single entry of the execute command by means of the
`
`input device:
`
`analyzing the document to determine if the first information is
`
`contained therein, and
`
`if the first information is contained in the document, searching,
`
`using the record retrieval program, the information source for second
`
`information associated with the first information;
`
` (Ex. 1001, col. 10, lines. 36-43.) Analyzing the document(cid:211) requires
`
`examining text in the document and discriminating between text that
`
`represents (cid:210)first information(cid:211) and other text. No limitation is placed on the
`
`structure or content of text in the document to be analyzed. The program
`
`performing the analysis of the text must decide whether any portion of the
`
`text comprises (cid:210)first information(cid:211) such as a name, and address or other type
`
`of information. This is what is meant by (cid:210)Analyze what the user has typed
`
`in the Document(cid:211) at step 4 of Fig. 1a. The next step (6) asks (cid:210)What data did
`
`Page 8 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 9 of 16
`
`

`

`we find?(cid:211) and the flow of the program then branches to one of four different
`
`following steps depending on the result of the analysis. Possible results of
`
`the analysis step are finding a (cid:210)name only,(cid:211) (to step 12) an (cid:210)email address,
`
`mailing list, category name, tel. no. or other(cid:211) (to step 10), (cid:210)name and
`
`address(cid:211) (to step 14 in Fig. 1b), or (cid:210)nothing or not interpretable(cid:211) (to step 8).
`
`(Figs. 1a and 1b are parts of Fig. 1.)
`
`21.The logical flow in Figs. 2a and 2b (which are parts of Fig. 2)
`
`of the (cid:213)853 Patent is similar the logical flow in Figs. 1a and 1b and also
`
`includes the corresponding recited steps 2, 4, 6, 8, 12, and 14. Ex. 1, col. 5,
`
`lines 8-10 and following.
`
`22.The (cid:213)853 Patent teaches examination of text in the document using
`
`techniques such as (cid:210)analyzing (i) paragraph/line separations/formatting, etc.; (ii)
`
`street, avenue, drive, lane, boulevard, city, state, zip code, country designators and
`
`abbreviations, etc.; (iii) Mr., Mrs., Sir, Madam, Jr., Sr. designators and
`
`abbreviations, etc.; (iv) Inc., Ltd., P.C., L.L.C, designators and abbreviations, etc.;
`
`and (v) a database of common male/female names, etc.(cid:211) Ex. 1001, col. 4, lines
`
`31-37.
`
`23.Thus is it clear to a person of skill in the art in reading the (cid:213)853 Patent
`
`that the program performing the analysis is examining text in the document and
`
`distinguishing (cid:210)first information(cid:211) (exemplified by contact information) from
`
`Page 9 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 10 of 16
`
`

`

`other text in the document and also to distinguish among types of contact
`
`information.
`
`24.As quoted above, the analyzing process is required by claim 1 to be
`
`launched (cid:210)upon a single entry of the execute command by means of the input
`
`device(cid:211). The claim therefore makes the process of (cid:210)analyzing(cid:211) conditioned (cid:210)upon
`
`a single entry of the execute command by means of the input device(cid:211) (emphasis
`
`added). A person of ordinary skill in the art would understand that this limitation
`
`requires the analyzing process to occur as a result of and proximate in time to
`
`entry of the execute command.
`
`25.Additionally, the analyzing process required by claim 1 is launched
`
`(cid:210)upon a single entry(cid:211) of the execute command. A person of ordinary skill in the
`
`art would understand this limitation to require that a single entry of the execute
`
`command is sufficient to trigger analyzing to occur, and that it occurs
`
`automatically after the execute command. Since the single entry of the execute
`
`command is sufficient to trigger the analyzing, these limitations rule out action by
`
`the user, such as selection of text in the document to be analyzed, as a condition
`
`fortheanalyzing to takeplace.
`
`Goodhand in contrast to the (cid:213)853 Patent
`
`26.In Goodhand, by contrast, a user enters address information into an
`
`Address (or (cid:210)To:(cid:211)) field before the (cid:210)resolving(cid:211) process begins. The user then
`
`Page 10 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 11 of 16
`
`

`

`signals that he has finished entering address information by (cid:210)moving the cursor to
`
`another field.(cid:211) The system of Goodhand assumes that all text entered into the
`
`Address field of the email template is address information (i.e., first name, last
`
`name, or alias) and not any other type of information. Thus, Goodhand does not
`
`disclose or teach (cid:210)analyzing (cid:201) to determine if first information (i.e. address
`
`information) is in the document,(cid:211) because no analysis is needed to determine that
`
`text in the address field is a name or an alias, since the Address field is used for
`
`nothing else. The user must conform to this presumption or risk having text
`
`entered in the Address field misinterpreted or ignored.
`
`27.The requirement that (cid:210)[t]he entered display name may include all or
`
`part of the intended recipient’s first name, last name, and/or e-mail alias(cid:211) in the
`
`context of the Goodhand system conveys to a person of ordinary skill in the art
`
`that the Goodhand system does not distinguish between contact information and
`
`other text, but rather assumes that all text entered into the address field of the e-
`
`mail template is contact information. In other words, any and all text that is typed
`
`into the address field of the e-mail template is subjected by the Goodhand system
`
`to thesame process,namely (cid:210)attempting tomatch the displaynamesintheaddress
`
`field to specific user aliases that are included in a centralized address book or
`
`directory(cid:211).
`
`Page 11 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 12 of 16
`
`

`

`28.I have performed a simple experiment to illustrate this point. Since the
`
`Goodhand system in a preferred embodiment is implemented in Microsoft
`
`Outlook (Ex. 1003, col. 15, lines 38-40), and this functionality is preserved in
`
`Outlook 2010, one can employ Outlook 2010 to demonstrate the effect of the
`
`Goodhand system. In this experiment, I enter into the address field of the e-mail
`
`template of Outlook, a shopping list thus:
`
`cheesecake; apple sauce; baloney
`
`In response to entry of these items, Outlook attempts to (cid:210)resolve(cid:211) these entries by
`
`seeking corresponding entries in the Outlook contact database. Because these
`
`textual items do not in fact appear as names of contacts in the Outlook contact
`
`database, they have not been resolved into e-mail addresses. When one
`
`graphically invokes the (cid:210)send(cid:211) button on the e-mail template, a window
`
`containing an error message pops up, with the heading (cid:210) Check Names(cid:211) and the
`
`message (cid:210)Microsoft Outlook does not recognize (cid:212)cheesecake(cid:213)./ Select the address
`
`to use: / (No suggestions).(cid:211) Two graphically selectable boxes also appear in the
`
`same window: (cid:210)Show more names...(cid:211) and (cid:210)New Contact..." The result is
`
`illustratedbelow.
`
`Page 12 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 13 of 16
`
`

`

`
`
`
`
`29.This experiment is further confirmation that user entry of text into the
`
`address field constitutes characterization of the text as name or alias information,
`
`without analysis by the program. Thus, no analysis is required to (cid:210)determine if
`
`(cid:212)first information(cid:213) is present(cid:211) in this field. By entering text into the Address field,
`
`the user has designated that text as address information, just as if the user had
`
`selected particular text in a general-purpose field of a document to designate it as
`
`address information. The user (cid:210)selects(cid:211) text by choosing to enter it into the
`
`Address field rather than by entering it in any other field of the email form. All
`
`textual entries that are made in the address field of the e-mail template are treated
`
`Page 13 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 14 of 16
`
`

`

`by the system as contact information. Thus, the Goodhand system is not structured
`
`to distinguish between contact information and other textual content. It has no
`
`need to distinguish contact information from other text, and thus fails to meet the
`
`requirement in claim 1 of (cid:210)analyzing the document to determine if the first
`
`information is contained therein(cid:211).
`
`
`
`
`
`
`
`Page 14 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 15 of 16
`
`

`

`I declare that all statements made herein of my own knowledge are true and
`
`that all statements made on information and belief are believed to be true, and that
`
`these statements were made with knowledge that willful false statements and the
`
`like so made are punishable by fine or imprisonment, or both, under section 1001
`
`of Title 18 of the United States Code.
`
`
`
`
`
`
`Date: October 21, 2014
`
`
`
`_______________________
`John V. Levy, Ph.D.
`
`Page 15 of 15
`
`Arendi S.A.R.L. - Ex. 2008
`Page 16 of 16
`
`

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