throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`———————
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`———————
`
`APPLE INC.,
`Petitioner,
`
`v.
`
`FINTIV, INC.,
`Patent Owner.
`———————
`
`IPR2022-00976
`U.S. Patent No. 9,892,386
`_____________________
`
`DECLARATION OF DR. HENRY HOUH,
`UNDER 37 C.F.R. § 1.68 IN SUPPORT OF PETITION FOR
`INTER PARTES REVIEW
`
`1
`
`APPL-1003
`APPLE INC. / Page 1 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`TABLE OF CONTENTS
`Introduction .................................................................................................. 4
`I.
`Qualifications and Professional Experience .................................................. 6
`II.
`III. Level of Ordinary Skill in the Art ............................................................... 13
`IV. Relevant Legal Standards ............................................................................ 14
`V. Overview of the ’386 Patent ....................................................................... 17
`VI. Claim Construction ..................................................................................... 31
`VII.
`Identification of How the Claims are Unpatentable ..................................... 32
`A. Ground 1: Claims 1 and 3 would have been obvious under 35
`U.S.C. § 103(a) over Dill in view of Vadhri, Akashika, and
`Hansen. ............................................................................................. 34
`1.
`Summary of Dill (APPL-1005) .................................... 34
`
`B.
`
`Summary of Vadhri (APPL-1006) ............................... 42
`2.
`Summary of Akashika (APPL-1007) ........................... 46
`3.
`Summary of Hansen (APPL-1008) .............................. 53
`4.
`Overview of Analysis .................................................. 57
`5.
`Claim 1 ........................................................................ 59
`6.
`Grounds 1 and 2: claim 3 would have been obvious over Dill in
`view of Vadhri, Akashika, and Hansen (Ground 1); claim 2
`would have been obvious over Dill in view of Vadhri,
`Akashika, Hansen, and Liao (Ground 3). ........................................ 143
`1.
`Limitations in Claims 2 and 3 That are Identical or
`Similar to Claim 1 ..................................................... 144
`Limitations Unique to Both Claims 2 and 3 ............... 150
`Limitations Unique to Claim 3 (Ground 1) ................ 153
`
`2.
`3.
`
`
`
`
`2
`
`
`
`APPL-1003
`APPLE INC. / Page 2 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`Limitations Unique to Claim 2 (Ground 2) ................ 158
`4.
`VIII. Conclusion ................................................................................................ 176
`
`
`
`
`
`
`
`
`3
`
`
`
`APPL-1003
`APPLE INC. / Page 3 of 176
`
`

`

`Houh Declaration
`
`
`I, Henry Houh, do hereby declare as follows:
`
`I.
`
`INTRODUCTION
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`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,892,386 (“the ’386 patent”) to
`
`Michael A. Liberty.
`
`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-
`
`3 (“the Challenged Claims”) of the ’386 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.
`
`4.
`
`In the preparation of this declaration, I have studied:
`
`a.
`
`b.
`
`the ’386 patent, APPL-1001;
`
`the prosecution history of the ’386 Patent (“’386 File History”),
`
`APPL-1002;
`
`c. U.S. Patent Publication No. 2009/0265272 to Dill et al. (“Dill,”
`
`APPL-1005);
`
`
`
`
`4
`
`
`
`APPL-1003
`APPLE INC. / Page 4 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`d. U.S. Patent Publication No. 2010/013334 to Vadhri (“Vadhri,” APPL-
`
`1006);
`
`e. U.S. Patent Publication No. 2009/0217047 to Akashika et al.
`
`(“Akashika,” APPL-1007);
`
`f. U.S. Patent Publication 2004/0230527 (“Hansen,”APPL-1008);
`
`g. U.S. Patent No. 7,865,141 to Liao et al. (“Liao,” APPL-1009);
`
`h. 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
`
`my own knowledge and experience based upon my work in the field
`
`of software and telecommunications as described below, as well as the
`
`following materials:
`
`a. G. Winfield Treese et al., “Designing Systems for Internet
`
`Commerce,” Second Edition, Addison-Wesley, 2003 (“Treese”) (excerpt), APPL-
`
`1012;
`
`b. H. Newton, “Newton’s Telecom Dictionary,” 17th Edition, CMP
`
`Books, 2001 (excerpt, p. 52), APPL-1014; and
`
`
`
`
`5
`
`
`
`
`
`APPL-1003
`APPLE INC. / Page 5 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`c.
`
` T. Thai et al., “.Net Framework Essentials,” Third Edition, O’Reilly
`
`& Associates, Inc., 2003 (excerpt, pp. 1-10), APPL-1015.
`
`d. any other document cited in this analysis.
`
`The materials I have reviewed and studied, including those listed in this
`
`paragraph, are the type of evidence an expert in the field of software and mobile
`
`application development would consider in reaching conclusions.
`
`5.
`
`Unless otherwise noted, all emphasis in any quoted material has been
`
`added.
`
`II. QUALIFICATIONS AND PROFESSIONAL EXPERIENCE
`
`6. My complete qualifications and professional experience are described
`
`in my Curriculum Vitae, a copy of which can be found in APPL-1004. The
`
`following is a brief summary of my relevant qualifications and professional
`
`experience.
`
`7.
`
`I received a Ph.D. in Electrical Engineering and Computer Science
`
`from the Massachusetts Institute of Technology (“MIT”) in 1998. I also 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.
`
`8.
`
`I am currently self-employed as an independent technical consultant. I
`
`am also president of a company, Einstein’s Workshop, that provides supplemental
`
`
`
`
`6
`
`
`
`APPL-1003
`APPLE INC. / Page 6 of 176
`
`

`

`Houh Declaration
`
`science, technology, engineering, and mathematics (“STEM”) education to
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`children of all ages.
`
`9.
`
`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 well as programming. As a TA, I helped write homework
`
`assignments, lab assignments (including those that involved programming), and
`
`exams. I also taught in the recitation sections.
`
`10. 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
`
`Laboratory for Computer Science. The TNS group built a high-speed gigabit
`
`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 (which was based on FPGAs), designing and building the high-speed
`
`links (which included programmable logic devices), and designing and writing the
`
`
`
`
`7
`
`
`
`APPL-1003
`APPLE INC. / Page 7 of 176
`
`

`

`Houh Declaration
`
`device drivers for the interface cards (which included programmable logic
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`devices), I also set up the group’s web server. Also, along with the other graduate
`
`students, I helped to maintain, install, and upgrade the networking devices used
`
`within the group, including setting up and configuring access control lists
`
`(“ACLs”) for accounts and file systems. Such ACLs are standard methods of
`
`controlling permissions associated with system resources and I have utilized and
`
`managed them with in many other contexts, including in web-based systems,
`
`networked systems, and operating systems.
`
`11.
`
`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.
`
`12.
`
`I defended and submitted my Ph.D. thesis, titled “Designing Networks
`
`
`
`
`8
`
`
`
`APPL-1003
`APPLE INC. / Page 8 of 176
`
`

`

`Houh Declaration
`
`for Tomorrow’s Traffic,” in January 1998. As part of my thesis research, I
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`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.
`
`13. 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.
`
`14. As part of my work at NBX, I designed the core audio reconstruction
`
`software 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 part of this work. I also programmed the first prototype of
`
`
`
`
`9
`
`
`
`APPL-1003
`APPLE INC. / Page 9 of 176
`
`

`

`Houh Declaration
`
`our phone which communicated using IP, and I demonstrated our IP phones
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`working over the Internet when we attended a trade show in California. The phone
`
`connected over the Internet to our headquarters in Andover, MA. I also
`
`programmed a data capture and analysis system that provided data on the operation
`
`of the system.
`
`15. 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
`
`captured packets, including detailed Ethernet header decoding, IP header decoding,
`
`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. At Empirix, I also rearchitected the
`
`
`
`
`10
`
`
`
`APPL-1003
`APPLE INC. / Page 10 of 176
`
`

`

`Houh Declaration
`
`design of the Web Test division’s core product, e-Test Suite. E-Test Suite was a
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`software program designed to perform functional and load testing of web
`
`applications. I was technical lead on the project, and also worked on programming
`
`a Javascript interpreter for the product. Javascript, standardized as ECMAScript, is
`
`the flexible programming layer that allows users to interact with web pages
`
`through actions such as clicking and dragging that allows web page programmers
`
`to extend the functionality of a web page beyond clicking on links.
`
`16.
`
`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.
`
`17.
`
`I also worked with setting up accounting systems and integrating on-
`
`line payment systems on numerous occasions. In 1994, I started a company, Agora
`
`Technology Group, that set up web sites for targeted advertising, and later
`
`provided consulting services to companies and organizations to set up their web
`
`sites. I managed all the finances and bookkeeping for the company, including
`
`
`
`
`11
`
`
`
`APPL-1003
`APPLE INC. / Page 11 of 176
`
`

`

`Houh Declaration
`
`keeping all the books and ledgers. Starting in the early 2000’s, I integrated web
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`payment systems with various web sites, writing the necessary code for the
`
`systems integration.
`
`18. At my educational company, Einstein’s Workshop, I created the initial
`
`web site and integrated it with online payment solutions. I also evaluated, sourced,
`
`and configured the point-of-sale system for the company, which also involved
`
`integration with and setup of mobile shopping terminals. Furthermore, I set up the
`
`accounting system, built the web site, integrated various web payment mechanisms
`
`with the web site, set up mobile payment systems, and also set up a mobile point of
`
`sale system. At Einstein’s Workshop, we teach programming to children of all
`
`ages, starting with Scratch programming for young elementary students and
`
`advancing through programming in Python and for game development for high
`
`school students. I conceived many of the programming classes and have taught
`
`programming to novice and more advanced students. We also created an
`
`educational computer-aided design tool, called BlocksCAD. We received a grant,
`
`on which I was the principal investigator, to further develop BlocksCAD and
`
`successfully met our grant objectives. BlocksCAD was spun-off from Einstein’s
`
`Workshop and has been part of various incubator/accelerator programs in
`
`education as well as at the MIT Media Lab. Today, BlocksCAD is used worldwide
`
`in makerspaces as well as in schools throughout the U.S.
`
`
`
`
`12
`
`
`
`APPL-1003
`APPLE INC. / Page 12 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`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 No. 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;
`
`and (4) the prior art solutions to those problems.
`
`21. A person of ordinary skill in the art (“POSITA”) in June 2011 would
`
`
`
`
`13
`
`
`
`APPL-1003
`APPLE INC. / Page 13 of 176
`
`

`

`Houh Declaration
`
`have had a working knowledge of monetary transaction systems pertinent to the
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`’386 patent, including software development in the field of mobile payment
`
`techniques. Such POSITA would have had a bachelor’s degree in electrical
`
`engineering, computer science, or equivalent training, and approximately two years
`
`of work experience in software development. 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 ’386 patent (i.e., June 3, 2011 (“priority date”)). 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 ’386 patent.
`
`IV. RELEVANT LEGAL STANDARDS
`
`23.
`
`I am not an attorney. In preparing and expressing my opinions and
`
`considering the subject matter of the ’386 patent, I am relying on certain basic
`
`legal principles that counsel have explained to me. These principles are discussed
`
`below.
`
`24.
`
`I understand that prior art to the ’386 patent includes patents and
`
`printed publications in the relevant art that predate the priority date of the alleged
`
`
`
`
`14
`
`
`
`APPL-1003
`APPLE INC. / Page 14 of 176
`
`

`

`Houh Declaration
`
`
`invention recited in the ’386 patent. For purposes of this declaration, I am applying
`
`Inter Partes Review of U.S. 9,892,386
`
`June 3, 2011, as the priority date of the ’386 patent (“priority date”).
`
`25.
`
`It is my understanding that, to anticipate a claim under 35 U.S.C.
`
`§ 102, a reference must disclose each and every element of the claim. I have been
`
`informed that a reference may disclose an element expressly or inherently. I
`
`understand that, for a limitation to be inherently disclosed by a reference, the
`
`limitation necessarily must be present, or the natural result of the combination of
`
`elements explicitly disclosed by the prior art.
`
`26.
`
`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.
`
`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
`
`
`
`
`15
`
`
`
`APPL-1003
`APPLE INC. / Page 15 of 176
`
`

`

`Houh Declaration
`
`the invention, any long-felt but unsolved need in the art that was satisfied by the
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`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
`
`recited in the claims. 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 ’386
`
`patent or any assignee of the ’396 patent that any secondary considerations are
`
`relevant to the obviousness analysis of any Challenged Claim of the ’386 patent.
`
`29.
`
`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)
`
`choosing from a finite number of identified, predictable solutions, with a
`
`reasonable expectation of success; and (f) some teaching, suggestion, or motivation
`
`
`
`
`16
`
`
`
`APPL-1003
`APPLE INC. / Page 16 of 176
`
`

`

`Houh Declaration
`
`in the prior art that would have led one of ordinary skill to modify the prior art
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`reference or to combine prior art reference teachings to arrive at the claimed
`
`invention.
`
`V. OVERVIEW OF THE ’386 PATENT
`
`30. The ’386 patent was originally filed as U.S. Application No.
`
`15/201,152 (“the ’152 application”) on July 1, 2016. I have been informed that the
`
`’152 application is related to several earlier non-provisional applications, the
`
`earliest of which was U.S. Application No. 13/484,199, which was filed on May
`
`30, 2012, and which is now U.S. Patent No. 8,538,845. I have also been informed
`
`that the ’152 application claims priority to two provisional applications, the earliest
`
`of which was U.S. Provisional Application No. 61/493,064, which was filed on
`
`June 3, 2011.
`
`31. The ’386 patent relates to a “monetary transaction system for
`
`conducting monetary transactions between transaction system subscribers and
`
`other entities.” APPL-1001, 1:39-37, 3:43:45. The ’386 patent explains that “the
`
`monetary transaction system includes a mobile device configured to run a
`
`monetary transaction system application,” and “a monetary transaction system
`
`subscriber that has a profile with the system.” APPL-1001, 1:39-44, 3:46-50.
`
`According to the ’386 patent, “[t]he subscriber indicates, via the monetary
`
`transaction system application, one or more specified transactions that are to be
`
`
`
`
`17
`
`
`
`APPL-1003
`APPLE INC. / Page 17 of 176
`
`

`

`Houh Declaration
`
`performed using the monetary transaction system.” APPL-1001, 1:44-47, 3:50-53.
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`The ’386 patent explains that “[p]erforming these transactions includes
`
`communicating with a monetary transaction database to determine whether the
`
`transaction is permissible based on data indicated in the subscriber's profile.”
`
`APPL-1001, 1:49-52, 3:55-58.
`
`32.
`
`In addition, the ’386 patent explains that “[t]he monetary transaction
`
`system also includes at least one entity that is to be involved in the specified
`
`transaction, where the entity has a profile with the monetary transaction system.
`
`This entity may be a person, a retail store, an agent or other entity.” APPL-1001,
`
`1:53-57, 3:59-63.
`
`33. Figure 1 of the ’386 patent below illustrates “an example system
`
`architecture of a mobile wallet platform.” APPL-1001, 13:3-4. The “mobile wallet
`
`platform” shown in Figure 1 includes various functional components such as an
`
`“integration tier 101,” “notification services 102,” “business process services 104,”
`
`“payment handler 105,” “security services 106,” “database 108,” and “rules engine
`
`109.” APPL-1001, 13:4-51. The ’386 patent explains that the “[c]omponents of a
`
`mobile wallet platform can be connected to one another over (or be part of) a
`
`system bus and/or a network. Networks can include a Local Area Network
`
`(“LAN”), a Wide Area Network (“WAN”), and even the Internet. Accordingly,
`
`components of the mobile wallet platform can be ‘in the cloud.’” APPL-1001, 13:-
`
`
`
`
`18
`
`
`
`APPL-1003
`APPLE INC. / Page 18 of 176
`
`

`

`Houh Declaration
`
`65-14:3. Thus, the ’386 patent envisions that the “components” of the “mobile
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`
`
`wallet platform” may be embodied in a distributed computing environment.
`
`APPL-1001, Fig. 1
`
`34. The ’386 patent explains that “FIG. 2 depicts a monetary transaction
`
`system 200 similar to that described in FIG. 1. The monetary transaction
`
`system 200 may provide a more simplified system structure in which each of the
`
`above services may be provided.” APPL-1001, 14:27-30. Figure 2 of the ’386
`
`patent is reproduced below. Thus, the ’386 patent discloses that the monetary
`
`transaction system 200 shown in Figure 2 includes the functional components (e.g.,
`
`“services”) shown in Figure 1. APPL-1001, 14:27-28 (“FIG. 2 depicts a monetary
`
`
`
`
`19
`
`
`
`APPL-1003
`APPLE INC. / Page 19 of 176
`
`

`

`Houh Declaration
`
`transaction system 200 similar to that described in FIG. 1.”).
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`
`
`Subscriber
`
`Subscriber
`
`APPL-1001, Fig. 2 (annotated)
`
`Agent
`
`35. Figure 2 above shows an embodiment of a monetary transaction
`
`system 200 in which a first subscriber 205 utilizes a mobile device 206 having a
`
`mobile wallet application 207 to conduct a transaction with another entity (e.g.,
`
`another subscriber 222, or a retail store or agent 223) through a monetary
`
`transaction system 210. APPL-1001, 14:27-39.
`
`36. The monetary transaction system 210 performs certain services in
`
`support of the requested transaction by accessing the profile information 211 about
`
`
`
`
`20
`
`
`
`APPL-1003
`APPLE INC. / Page 20 of 176
`
`

`

`Houh Declaration
`
`the subscriber and using a rules engine 200 to determine whether the transaction is
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`permissible based on factors such as whether the requesting subscriber (i) has
`
`sufficient money in her account, or (ii) has exceeded a specified number of allowed
`
`transactions. APPL-1001, 14:40-64.
`
`The subscriber can indicate, using the mobile application 207 which
`transaction or other action he or she would like to perform. The
`indicated transaction 208 is sent to the mobile wallet platform 210 to be
`carried out by the platform. The transaction processor 216 (which may
`be similar to or the same as transaction processor 121 of FIG. 1)
`performs the transaction(s) specified by the (unbanked) subscriber 205.
`The transaction processor may implement various other components to
`perform
`the
`transaction
`including memory 217,
`(wireless)
`communication module 215, rules engine 210 and/or
`transaction
`database 225.
`Performing the specified transactions may include communicating with
`the monetary transaction database 225 to determine whether the
`transaction is permissible based on data indicated in the unbanked
`subscriber's profile (for instance, whether the subscriber has enough
`eMoney in his or her stored value account, or has enough money in his
`or her bank account). Rules engine 220 may also be consulted to
`determine whether the subscriber has exceeded a specified number of
`allowed transactions. Then, if funds are available, and the transaction
`is otherwise permissible, the monetary transaction system can transfer
`money or eMoney 221 to or from an entity such as a user or agent (e.g.
`entity 222) to or from an establishment such as a retail store or agent
`
`
`
`
`21
`
`
`
`APPL-1003
`APPLE INC. / Page 21 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`company (e.g. entity 223).
`APPL-1001, 14:40-64.
`37.
`I understand that the Examiner issued two Office Actions during
`
`prosecution of the ’386 patent. APPL-1002, 1606-1612 (first Office Action), 1368-
`
`1371 (second Office Action). I understand that the Examiner rejected the
`
`prosecution claims only on patent-eligibility grounds under 35 U.S.C. § 101. I
`
`understand that the Examiner did not reject the prosecution claims on the basis of
`
`any prior art.
`
`38.
`
`I have been informed that claim 1 of the ’386 patent corresponds to
`
`prosecution claim 1, claim 2 of the ’386 patent corresponds to prosecution claim 4,
`
`and claim 3 of the ’386 patent corresponds to prosecution claim 5.
`
`39. To obtain allowance, claim 1 of the ’386 patent (prosecution claim 1),
`
`claim 2 (prosecution claim 4), and claim 3 (prosecution claim 5) were amended as
`
`follows (amendments shown with underlining).
`
`Claim 1 (prosecution claim 1). A monetary transaction system for
`conducting monetary transactions between subscribers and other entities, the
`system comprising one or more of:
`an integration tier operable to manage mobile wallet sessions, the
`integration tier also including a communication application programming
`interface (API) and other communication mechanisms to accept messages
`from channels;
`
`
`
`
`22
`
`
`
`APPL-1003
`APPLE INC. / Page 22 of 176
`
`

`

`Houh Declaration
`
`
`Inter Partes Review of U.S. 9,892,386
`
`
`
`notification services operable to send notifications through different
`notification channels including one or more of short message peer-to-peer,
`short-message services and simple mail transfer protocol emails;
`business process services operable to implement business workflows,
`including at least one of executing financial transactions, auditing financial
`transactions, invoking third-party services, handling errors, and logging
`platform objects;
`database services operable to store financial transaction details, store
`customer profiles, and manage money containers;
`a payment handler service operable to use APIs of different payment
`processors including one or more APIs of banks, credit and debit cards
`processors, bill payment processors;
`a rules engine operable to gather financial transaction statistics and
`use the gathered financial transaction statistics to enforce constraints
`including transaction constraints;
`a security service operable to perform subscriber authentication;
`at least one entity that is to be involved in the specified transaction, the at
`least one entity having a profile with the monetary transaction system:
`wherein the at least one entity is the agent; and
`wherein the monetary transaction system is implemented to deposit
`funds at an agent branch, the funds being deposited by a subscriber at the
`agent branch using a mobile device configured to run a monetary transaction
`system application, the monetary transaction system performing the
`following steps:
`receiving a communication message from the mobile device over one
`of a plurality of channels connected to the monetary transaction system, the
`communication message being received by an API associated with the
`
`
`
`
`23
`
`
`
`APPL-1003
`APP

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