throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`———————
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`———————
`
`APPLE INC,
`Petitioner,
`
`v.
`
`MOZIDO, INC.,
`Patent Owner.
`———————
`
`U.S. Patent No. 9,189,785
`_____________________
`
`DECLARATION OF DR. HENRY HOUH,
`UNDER 37 C.F.R. § 1.68 IN SUPPORT OF PETITION FOR
`INTER PARTES REVIEW
`
`1
`
`Ex. 1003
`APPLE INC. / Page 1 of 89
`
`

`

`Houh Declaration
`
`Inter Partes Review of U.S. 9,189,785
`
`TABLE OF CONTENTS
`Introduction ...................................................................................................... 4
`I.
`Qualifications and Professional Experience .................................................... 5
`II.
`Level of Ordinary Skill in the Art ................................................................. 11
`III.
`IV. Relevant Legal Standards .............................................................................. 12
`V.
`Background .................................................................................................... 15
`VI. Overview of the ’785 Patent .......................................................................... 15
`VII. Claim Construction ........................................................................................ 19
`VIII. Identification of how the Claims are Unpatentable ....................................... 19
`A.
`Ground 1: Claims 1-21 are obvious under 35 U.S.C. § 103(a)
`over Easterly in view of Luz. .............................................................. 20
`1.
`Summary of Easterly ..................................................... 20
`Summary of Luz ............................................................ 23
`2.
`Reasons to Combine Easterly and Luz .......................... 26
`3.
`4.
`Claim 1 ........................................................................... 30
`5.
`Claim 2 ........................................................................... 73
`6.
`Claim 3 ........................................................................... 75
`7.
`Claim 4 ........................................................................... 76
`8.
`Claim 5 ........................................................................... 77
`9.
`Claim 6 ........................................................................... 80
`10.
`Claim 7 ........................................................................... 81
`11.
`Claim 8 ........................................................................... 82
`12.
`Claim 9 ........................................................................... 84
`
`2
`
`Ex. 1003
`APPLE INC. / Page 2 of 89
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`Claim 10 ......................................................................... 84 
`13. 
`Claim 11 ......................................................................... 85 
`14. 
`Claim 12 ......................................................................... 85 
`15. 
`Claim 13 ......................................................................... 85 
`16. 
`Claim 14 ......................................................................... 85 
`17. 
`Claim 15 ......................................................................... 85 
`18. 
`Claim 16 ......................................................................... 87 
`19. 
`Claim 17 ......................................................................... 87 
`20. 
`Claim 18 ......................................................................... 87 
`21. 
`Claim 19 ......................................................................... 87 
`22. 
`Claim 20 ......................................................................... 88 
`23. 
`Claim 21 ......................................................................... 88 
`24. 
`IX.  Conclusion ..................................................................................................... 89 
`
`
`
`
`
`
`3
`
`
`
`Ex. 1003
`APPLE INC. / Page 3 of 89
`
`

`

`Houh Declaration
`
`
`I, Henry Houh, do hereby declare as follows:
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`I.
`
`INTRODUCTION
`1.
`
`I am making this declaration at the request of Apple, Inc. in the matter
`
`of the Inter Partes Review of U.S. Patent No. 9,189,785 (“the ’785 Patent”) to
`
`Liberty et al.
`
`2.
`
`I am being compensated for my work in this matter at my standard
`
`hourly rate. I am also being reimbursed for reasonable and customary expenses
`
`associated with my work and testimony in this investigation. My compensation is
`
`not contingent on the outcome of this matter or the specifics of my testimony.
`
`3.
`
`I have been asked to provide my opinions regarding whether claims 1-
`
`21 (“the Challenged Claims”) of the ’785 Patent are unpatentable as they would
`
`have been obvious to a person having ordinary skill in the art (“POSITA”) at the
`
`time of the alleged invention, in light of the prior art. It is my opinion that all of the
`
`limitations of the challenged claims would have been obvious to a POSITA.
`
`In the preparation of this declaration, I have studied:
`
`the ’785 Patent, Ex.1001;
`
`the prosecution history of the ’785 Patent (“’785 File History”),
`
`4.
`
`a.
`
`b.
`
`Ex.1002;
`
`c.
`
`U.S. Patent Publication No. 2011/0208659 to Easterly et al.
`
`(“Easterly”), Ex.1005;
`
`
`
`
`4
`
`
`
`Ex. 1003
`APPLE INC. / Page 4 of 89
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,189,785
`
`d.
`
`U.S. Patent Publication No. 2013/0346291 to Vellozo Luz et al.
`
`(“Luz”), Ex.1006;
`
`5.
`
`a.
`
`b.
`
`In forming the opinions expressed below, I have considered:
`
`the documents listed above;
`
`the relevant legal standards, including the standard for obviousness,
`
`and any additional authoritative documents as cited in the body of this declaration;
`
`and
`
`c.
`
`my own knowledge and experience based upon my work in the field
`
`of networking as described below, as well as the following materials.
`
`U.S. Patent No. 9,317,850 to Keresman (“Keresman”), Ex.1007;
`
`U.S. Patent No. 8,380,177 to Laracey (“Laracey”), Ex.1008; and
`
`U.S. Patent No. 7,536,352 to Lapsley (“Lapsley”), Ex.1009.
`
`Unless otherwise noted, all emphasis in any quoted material has been
`
`d.
`
`e.
`
`f.
`
`6.
`
`added.
`
`II. QUALIFICATIONS AND PROFESSIONAL EXPERIENCE
`7. My complete qualifications and professional experience are described
`
`in my Curriculum Vitae, a copy of which can be found in Exhibit 1004. The
`
`following is a brief summary of my relevant qualifications and professional
`
`experience.
`
`8.
`
`I received a Ph.D. in Electrical Engineering and Computer Science
`
`
`
`
`5
`
`
`
`
`
`Ex. 1003
`APPLE INC. / Page 5 of 89
`
`

`

`Houh Declaration
`
`from the Massachusetts Institute of Technology (“MIT”) in 1998. Beforehand, I
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`received a Master of Science degree in Electrical Engineering and Computer
`
`Science in 1991, a Bachelor of Science degree in Electrical Engineering and
`
`Computer Science in 1989, and a Bachelor of Science degree in Physics in 1990,
`
`all from MIT.
`
`9.
`
`I am currently self-employed as an independent technical consultant. I
`
`am also president of a company, Einstein’s Workshop, that provides supplemental
`
`science, technology, engineering, and mathematics (“STEM”) education to
`
`children of all ages.
`
`10.
`
`I first entered telecommunications in 1987 when I worked as a
`
`summer intern at AT&T Bell Laboratories as part of a five-year dual degree
`
`program at MIT. I continued to work at AT&T Bell Laboratories as part of this
`
`MIT program. While at MIT, I was a teaching assistant (“TA”) in the Electrical
`
`Engineering and Computer Science Department’s core Computer Architectures
`
`course. I first was a TA as a senior for a role typically reserved for graduate
`
`students. I later became head TA. The course covered various topics in computer
`
`architectures. As a TA, I helped write homework assignments, lab assignments,
`
`and exams. I also taught in the recitation sections.
`
`11. Later, as part of my doctoral research at MIT from 1991-1998, I was a
`
`research assistant in the Telemedia Network Systems (“TNS”) group at the
`
`
`
`
`6
`
`
`
`Ex. 1003
`APPLE INC. / Page 6 of 89
`
`

`

`Houh Declaration
`
`Laboratory for Computer Science. The TNS group built a high-speed gigabit
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`network and created applications that ran over the network. Example applications
`
`included ones for remote video capture, processing, and display of video on
`
`computer terminals. In addition to working on the design of core network
`
`components, designing and building the high-speed links, and designing and
`
`writing the device drivers for the interface cards, I also set up the group’s web
`
`server. Also, I helped to maintain, install, and upgrade the networking devices used
`
`within the group, along with other graduate students.
`
`12.
`
`I also helped to build the web pages that initiated the above-
`
`mentioned video sessions via a web interface. Vice President Al Gore visited our
`
`group in 1996 and received a demonstration of—and remotely drove—a radio-
`
`controlled toy car with a wireless video camera mounted on it that was built by our
`
`group. This toy car device received commands transmitted over a network from a
`
`remote computer, and video data from the toy car was transmitted wirelessly then
`
`over a computer network back to the user controller. On occasion, we allowed
`
`users visiting our web site to drive the toy car from their remote computer while
`
`they watched the video on their computer. The video stream was encoded by TNS-
`
`designed hardware, streamed over the TNS-designed network, and displayed using
`
`TNS-designed software.
`
`13.
`
`I defended and submitted my Ph.D. thesis, titled “Designing Networks
`
`
`
`
`7
`
`
`
`Ex. 1003
`APPLE INC. / Page 7 of 89
`
`

`

`Houh Declaration
`
`for Tomorrow’s Traffic,” in January 1998. As part of my thesis research, I
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`analyzed local area and wide area flows to show a more efficient method for
`
`routing packets in a network, based on traffic patterns at the time. The traffic flow
`
`data included Ethernet, IP, TCP or UDP, and RTP header information, which I
`
`analyzed to come to the conclusions in my thesis.
`
`14. From 1997 to 1999, I was a Senior Scientist and Engineer at NBX
`
`Corporation, a start-up that made business telephone systems for streaming
`
`packetized audio over data networks instead of using traditional telephone lines.
`
`NBX was later acquired by 3Com Corporation and the phone system is still used
`
`today by numerous businesses.
`
`15. As part of my work at NBX, I designed the core audio reconstruction
`
`algorithms for the telephones, as well as the packet transmission algorithms. I also
`
`designed and validated the core packet transport protocol used by the phone
`
`system. The protocol was used for all signaling in the phone system, including for
`
`the setup of conference calls. The NBX system also featured a computer interface
`
`for initiating phone calls, which could also initiate conference calls. The NBX
`
`system also supported the Telephony Application Programming Interface (“TAPI”)
`
`that allowed other computer programs to integrate with our system telephony
`
`features. We obtained U.S. Patent No. 6,697,963, entitled “Telecommunication
`
`method for ensuring on-time delivery of packets containing time-sensitive data,” as
`
`
`
`
`8
`
`
`
`Ex. 1003
`APPLE INC. / Page 8 of 89
`
`

`

`Houh Declaration
`
`part of this work. The first release of the phones had integrated Ethernet repeater
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`hubs embedded in them, and I worked with the documentation and field support
`
`people to develop sets of guidelines so that customers would not build their
`
`networks to violate the Ethernet specifications, typically by chaining too many hub
`
`repeaters and NBX phones together. The first release of the phones also worked
`
`using Ethernet-layer packets (without the use of IP). I also programmed the first
`
`prototype of our phone which communicated using IP, and I demonstrated our IP
`
`phones working over the Internet when we attended a trade show in California.
`
`The phone connected over the Internet to our headquarters in Andover, MA.
`
`16. From 1999-2004, I was employed by Empirix or its predecessor
`
`company, Teradyne. Empirix was a leader in test tools for telecommunications
`
`protocols and systems, providing functional testing tools as well as load testing
`
`tools. From 2000-2001, I conceived and built a test platform for testing Voice-
`
`over-IP (VoIP). The first application on this new test platform was a cloud
`
`emulator for simulating the effects of transmitting VoIP over a busy network. The
`
`test platform was based on a network processor chip, which could be programmed
`
`to cut-through packets while processing packet data such as various protocol later
`
`headers including addresses included therein and even packet data contents. I also
`
`designed a protocol analyzer built on the same platform. The application captured
`
`and performed protocol decoding at various layers in the protocol stacks of
`
`
`
`
`9
`
`
`
`Ex. 1003
`APPLE INC. / Page 9 of 89
`
`

`

`Houh Declaration
`
`
`captured packets, including detailed Ethernet header decoding, IP header decoding,
`
`Inter Partes Review of U.S. 9,189,785
`
`TCP header decoding, UDP header decoding, RTP header decoding, and many
`
`other specified protocols. The application was also designed to reconstruct entire
`
`conversations that spanned multiple packets.
`
`17.
`
`In 2006, as part of my role at BBN Technologies, I helped found
`
`PodZinger Inc., now known as RAMP Inc. PodZinger utilized BBN’s speech
`
`recognition algorithms to search through the spoken words in audio and video
`
`segments. While I was Vice President of Operations and Technology, PodZinger
`
`followed its initial prototype with a full streaming audio and video search solution.
`
`I also created a social networking web site, which BBN sold to a venture-funded
`
`startup company. In the process of creating the web site, I designed and specified
`
`the authentication and authorization protocols.
`
`18.
`
`I started a robotics league in 2009 that eventually grew into Einstein’s
`
`Workshop when I found a facility in 2012. I evaluated and selected the point of
`
`sale solution, and established merchant accounts with a credit card processor. I set
`
`up and configured the point of sale solution, including entering all our initial stock
`
`units and configuring a mobile solution so that we could process payments using a
`
`mobile device when not at our physical point of sale station. I also set up online
`
`purchasing and established a separate relationship with Paypal for our online
`
`payments. In addition, I set up the accounting system, later bringing in a
`
`
`
`
`10
`
`
`
`Ex. 1003
`APPLE INC. / Page 10 of 89
`
`

`

`Houh Declaration
`
`bookkeeper and later a CPA. For my consulting business, I have maintained the
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`books to this day.
`
`19.
`
`I have been awarded several United States patents, including the
`
`following examples:
`
` U.S. Patent No. 7,975,296, “Automated security threat testing of
`
`web pages”;
`
` U.S. Patent No. 7,877,736, “Computer language interpretation and
`
`optimization for server testing”;
`
` U.S. Patent No. 7,801,910, “Method and apparatus for timed tagging
`
`of media content”;
`
` U.S. Patent 7,590,542, “Method of Generating Test Scripts Using a
`
`Voice-Capable Markup Language”; and
`
` U.S. Patent No. 6,967,963, “Telecommunication method for
`
`ensuring on-time delivery of packets containing time-sensitive
`
`data.”
`
`III. LEVEL OF ORDINARY SKILL IN THE ART
`20.
`
`I understand there are multiple factors relevant to determining the
`
`level of ordinary skill in the pertinent art, including (1) the levels of education and
`
`experience of persons working in the field at the time of the invention; (2) the
`
`sophistication of the technology; (3) the types of problems encountered in the field;
`
`
`
`
`11
`
`
`
`Ex. 1003
`APPLE INC. / Page 11 of 89
`
`

`

`Houh Declaration
`
`and (4) the prior art solutions to those problems.
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`21. A person of ordinary skill in the art (“POSITA”) in the field of the
`
`’785 Patent, as of its earliest possible filing date of August 24, 2012, would have
`
`been someone knowledgeable and familiar with the software arts that are pertinent
`
`to the ’785 Patent. That person would have a bachelor’s degree in electrical
`
`engineering, computer science, or equivalent training, and approximately two years
`
`of experience working in the field of software programming. Lack of work
`
`experience can be remedied by additional education, and vice versa.
`
`22. For purposes of this Declaration, in general, and unless otherwise
`
`noted, my statements and opinions, such as those regarding my experience and the
`
`understanding of a POSITA generally (and specifically related to the references I
`
`consulted herein), reflect the knowledge that existed in the field as of the priority
`
`date of the ’785 Patent (i.e., August 24, 2012). Unless otherwise stated, when I
`
`provide my understanding and analysis below, it is consistent with the level of a
`
`POSITA prior to the priority date of the ’785 Patent.
`
`IV. RELEVANT LEGAL STANDARDS
`23.
`
`I am not an attorney. In preparing and expressing my opinions and
`
`considering the subject matter of the ’785 Patent, I am relying on certain basic
`
`legal principles that counsel have explained to me. These principles are discussed
`
`below.
`
`
`
`
`12
`
`
`
`Ex. 1003
`APPLE INC. / Page 12 of 89
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`24.
`
`I understand that prior art to the ’785 Patent includes patents and
`
`printed publications in the relevant art that predate the priority date of the alleged
`
`invention recited in the ’785 Patent. For purposes of this Declaration, I am
`
`applying August 24, 2012 as the earliest possible priority date of the ’785 Patent.
`
`25.
`
`I have been informed that a claimed invention is unpatentable under
`
`35 U.S.C. § 103 if the differences between the invention and the prior art are such
`
`that the subject matter as a whole would have been obvious at the time the
`
`invention was made to a person having ordinary skill in the art to which the subject
`
`matter pertains. I have also been informed by counsel that the obviousness analysis
`
`takes into account factual inquiries including the level of ordinary skill in the art,
`
`the scope and content of the prior art, and the differences between the prior art and
`
`the claimed subject matter.
`
`26.
`
`I have been informed by counsel that the Supreme Court has
`
`recognized several rationales for combining references or modifying a reference to
`
`show obviousness of claimed subject matter. Some of these rationales include the
`
`following: (a) combining prior art elements according to known methods to yield
`
`predictable results; (b) simple substitution of one known element for another to
`
`obtain predictable results; (c) use of a known technique to improve a similar device
`
`(method, or product) in the same way; (d) applying a known technique to a known
`
`device (method, or product) ready for improvement to yield predictable results; (e)
`
`
`
`
`13
`
`
`
`Ex. 1003
`APPLE INC. / Page 13 of 89
`
`

`

`Houh Declaration
`
`choosing from a finite number of identified, predictable solutions, with a
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`reasonable expectation of success; and (f) some teaching, suggestion, or motivation
`
`in the prior art that would have led one of ordinary skill to modify the prior art
`
`reference or to combine prior art reference teachings to arrive at the claimed
`
`invention.
`
`27.
`
`I further understand that certain factors may support or rebut the
`
`obviousness of a claim. I understand that such secondary considerations include,
`
`among other things, commercial success of the patented invention, skepticism of
`
`those having ordinary skill in the art at the time of invention, unexpected results of
`
`the invention, any long-felt but unsolved need in the art that was satisfied by the
`
`alleged invention, the failure of others to make the alleged invention, praise of the
`
`alleged invention by those having ordinary skill in the art, and copying of the
`
`alleged invention by others in the field. I understand that there must be a nexus—a
`
`connection—between any such secondary considerations and the alleged invention.
`
`I also understand that contemporaneous and independent invention by others is a
`
`secondary consideration tending to show obviousness.
`
`28.
`
`I am not aware of any allegations by the named inventor of the ’785
`
`Patent or any assignee of the ’785 Patent that any secondary considerations are
`
`relevant to the obviousness analysis of any Challenged Claim of the ’785 Patent.
`
`
`
`
`14
`
`
`
`Ex. 1003
`APPLE INC. / Page 14 of 89
`
`

`

`Houh Declaration
`
`V. BACKGROUND
`29. Mobile wallets, sometimes referred to as e-wallets, are virtual wallets
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`that allow users to enter debit card, credit card, or other account type information
`
`into an application on their mobile phones. The application on the mobile phone
`
`can then be used to pay for goods or services either online or at point-of-sale
`
`terminals at merchant locations. In some cases, the mobile application may
`
`generate a barcode for scanning at a point-of-sale terminal. The barcode may have
`
`embedded therein various pieces of information, such as the user’s account number
`
`and other data for processing a transaction. As will be explained in more detail
`
`below, the ’785 Patent describes and claims no more than commonly known pieces
`
`of information that can be embedded within such a barcode.
`
`VI. OVERVIEW OF THE ’785 PATENT
`30. The ’785 Patent was filed on August 23, 2013 and claims priority to a
`
`provisional application filed August 24, 2012. The ’785 Patent relates to a payment
`
`processing system in which a customer uses an application on their phone to create
`
`a “scannable code” such as a QR code that is then presented to the merchant for
`
`payment of goods or services. The ’785 Patent summarizes its purported invention
`
`as follows:
`
`Embodiments described herein are directed to selecting a debit network
`using a quick response (QR) code and to processing a payment using a
`debit network selected according to information embedded in a QR
`
`
`
`
`15
`
`
`
`Ex. 1003
`APPLE INC. / Page 15 of 89
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,189,785
`
`code. In one embodiment, a mobile computer system receives input
`indicating that a user has initiated a payment for various items sold by
`a provider of goods or services. The mobile computer system
`determines that the user or the provider has specified a preference
`indicating which debit network is to be used to process the payment.
`The mobile computer system then generates a QR code with the debit
`network selection and portions of the user's debit account information
`embedded in the QR code, and sends the generated QR code to a
`payment processing system. The payment processing system may be
`cloud-based, or may be run locally at the provider's point of sale.
`
`’785 Patent, 1:37-51; see also abstract.
`
`31. To get the patent allowed, the Patent Owner amended the claims to
`
`further recite the types of information that are included in the QR code. ’785 File
`
`History, 90. The information in the scannable code is illustrated in Fig. 5.
`
`
`
`
`16
`
`
`
`
`
`Ex. 1003
`APPLE INC. / Page 16 of 89
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`
`
`’785 Patent, Fig. 5.
`
`
`
`32.
`
` The independent claims of the ’785 patent recite that the barcode
`
`includes each of the items shown above, except for the user’s purchase history.
`
`Claim 1 (originally claim 12 in prosecution) is recited below as an example.
`
`A computer system comprising the following:
`one or more processors;
`system memory;
`one or more computer-readable storage media having stored
`thereon computer-executable instructions that, when executed by the
`one or more processors, cause the computing system to perform a
`method for processing a payment using a debit network selected
`
`
`
`
`17
`
`Ex. 1003
`APPLE INC. / Page 17 of 89
`
`

`

`Inter Partes Review of U.S. 9,189,785
`
`
`
`Houh Declaration
`
`
`according to information embedded in a scannable code, the method
`comprising the following:
`receiving a scannable code with one or more portions of
`embedded payment information, the embedded payment information
`including at least the following: a total payment amount that is to be
`paid by a user, debit account information for the user, and an
`indication of which debit network is to be used to process the payment,
`the debit network comprising a debit payment processing entity that
`processes the initiated debit payment, wherein the indication of which
`debit network to be used includes (1) a user preferred network, (2) a
`provider preferred network and (3) a selected network, such that the
`scannable code includes all of (1) the user preferred network, (2) the
`provider preferred network and (3) the selected network, the scannable
`code also including an identification of rewards to be provided when
`the selected network is used and an identification of one or more
`goods or services associated with the total payment amount;
`determining which debit network is to be used to process the
`payment based on the indication provided in the embedded payment
`information in the received scannable code;
`sending the payment amount and the user's debit account
`information to the determined debit network; and
`receiving an indication that the payment was processed by the
`determined debit network.
`
`’785 Patent, Claim 1.
`
`33. The other claim limitations relate to routine payment processing steps,
`
`such as sending the payment amount and account numbers for processing and
`
`
`
`
`18
`
`
`
`Ex. 1003
`APPLE INC. / Page 18 of 89
`
`

`

`Houh Declaration
`
`receiving confirmation of payment.
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`34. As I explain below, the concept of a using a scannable code (e.g., QR
`
`code) to pay for goods and services was well known at the time the ’785 patent
`
`was filed. Moreover, the prior art shows that it was known for each of the claimed
`
`pieces of information to be included in the barcode.
`
`VII. CLAIM CONSTRUCTION
`35.
`
`It is my understanding that in order to properly evaluate the ’785
`
`Patent, the terms of the claims must first be interpreted. It is my understanding that
`
`for the purposes of this inter partes review, the claims are to be construed under
`
`the so-called Phillips standard, under which claim terms are given their ordinary
`
`and customary meaning as would be understood by one of ordinary skill in the art
`
`in light of the specification and prosecution history, unless the inventor has set
`
`forth a special meaning for a term. Counsel has explained to me that none of the
`
`claim terms are believed to require express construction.
`
`VIII. IDENTIFICATION OF HOW THE CLAIMS ARE UNPATENTABLE
`36.
`
`I have been asked to provide my opinion as to whether the Challenged
`
`Claims of the ’785 Patent would have been obvious in view of the prior art. The
`
`discussion below provides a detailed analysis of how the prior art references
`
`identified below teach the limitations of the Challenged Claims of the ’785 Patent.
`
`37. As part of my analysis, I have considered the scope and content of the
`
`
`
`
`19
`
`
`
`Ex. 1003
`APPLE INC. / Page 19 of 89
`
`

`

`Houh Declaration
`
`Inter Partes Review of U.S. 9,189,785
`
`prior art and any differences between the alleged invention and the prior art. I
`
`describe in detail below the scope and content of the prior art, as well as any
`
`differences between the alleged invention and the prior art, on an element-by-
`
`element basis for each Challenged Claims of the ’785 Patent.
`
`38. As described in detail below, the alleged invention of the Challenged
`
`Claims would have been obvious in view of the teachings of the identified prior art
`
`references as well as the knowledge of a POSITA.
`
`Ground 1: Claims 1-21 are obvious under 35 U.S.C. § 103(a) over
`A.
`Easterly in view of Luz.
`
`1.
`
`Summary of Easterly
`
`39.
`
`Like the ’785 Patent, Easterly relates to “the facilitation of certain
`
`financial and nonfinancial transactions between customers, retailers and suppliers
`
`using smart devices.” Easterly, [0002]. Easterly describes “an application residing
`
`on a smart device to provide secure, encrypted communications with a proprietary
`
`server using scanable barcodes to authenticate the identity of the purchaser and
`
`authorize, clear and settle a transaction between the purchaser and a third party
`
`who may be a merchant.” Easterly, [0002].
`
`40.
`
`Easterly describes a proprietary application referred to as “eCache.”
`
`The eCache application utilizes “a link between the retailer's POS system and the
`
`ACH network.” Easterly, [0013]. The eCache system also provides an additional
`
`link that “allows general purpose cards such as credit cards, debit cards, charge
`
`20
`
`Ex. 1003
`APPLE INC. / Page 20 of 89
`
`

`

`Houh Declaration
`
`cards, gift cards, and prepaid cards, to be switched to and authorized through a
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`
`
`merchant processor network, association network, debit (EFT) network or ATM
`
`network, where they may be used to complete a sales transaction.” Easterly,
`
`[0013].
`
`Easterly, Fig. 1.
`
`41. To facilitate payment over such networks, Easterly describes “a
`
`system of unique primary barcodes which are personal to a customer and may be
`
`tendered at the POS of a merchant or retailer.” Easterly, [0018]. Easterly provides
`
`an example in which the primary barcodes are “2-D barcodes.” In Easterly’s
`
`system, “[e]ach customer-specific primary barcode is further linked to an extension
`
`barcode or barcodes. The extension barcodes are linked to specific retailers' POS
`
`systems.” Easterly, [0019]. “In a preferred embodiment of the invention, primary
`
`
`
`
`21
`
`
`
`Ex. 1003
`APPLE INC. / Page 21 of 89
`
`

`

`Houh Declaration
`
`and extension barcode data may be combined into a single ‘combined’ barcode for
`
`Inter Partes Review of U.S. 9,189,785
`
`scanning.” Easterly, [0020]. The combined barcode may be presented to a
`
`merchant to facilitate the sale of goods or services, and includes “all of the data
`
`required to authenticate, authorize, clear and settle a transaction.” Easterly,
`
`[0020].
`
`2-D barcode
`
`Easterly, Fig. 17 (annotated).
`
`42. Easterly further describes information that is included in the code, as
`
`part of “all of the data required to authenticate, authorize, clear and settle a
`
`transaction.” Easterly, [0020]. For example, Easterly describes how “[t]he 2-D
`
`barcode has encoded detailed information concerning the transaction which may
`
`include designating particular accounts through which a transaction may be
`
`
`
`
`22
`
`
`
`
`
`
`
`Ex. 1003
`APPLE INC. / Page 22 of 89
`
`

`

`Houh Declaration
`
`settled.” Easterly, [0125]. The code may also include “a specific route to settle
`
`Inter Partes Review of U.S. 9,189,785
`
`the transaction, say from a checking account or by executing an ACH
`
`transaction.” Easterly, [00124].
`
`43. Easterly’s barcode includes both preferences from the user as well as
`
`the merchant. “[T]he eCache system will generate a unique 2-D barcode that
`
`encodes all such preferences and instructions.” Easterly, [0095]. “The system is
`
`not, however, just limited to customer's preferences. Merchants themselves may
`
`also establish a profile and incorporate preferences.” Easterly, [0096]. These
`
`preferences include the route for settling a transaction: “Where a customer has
`
`expressed no preference for possible clearance routes, the merchant can indicate
`
`preferences of its own that could be used to advantageously clear a transaction
`
`through the least expensive or fastest route.” Easterly, [0096]. As mentioned
`
`above, Easterly provides one example in which the route for settling a transaction
`
`is a debit network. See Easterly, [0013].
`
`44. Accordingly, Easterly provides evidence that it was known to use a
`
`scannable barcode to facilitate payment between a purchaser and a merchant.
`
`Easterly also provides examples of the types of information that may be included
`
`in the barcode.
`
`2.
`Summary of Luz
`45. Luz provides additional examples of what types of information may
`
`
`
`
`23
`
`
`
`
`
`Ex. 1003
`APPLE INC. / Page 23 of 89
`
`

`

`Houh Declaration
`
`be included within a scannable code. Like Easterly and the ’785 Patent, Luz
`
`Inter Partes Review of U.S. 9,189,785
`
`
`
`describes

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