throbber
Case IPR2019-00820
`Patent 7,937,581
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`____________
`
`APPLE INC.,
`Petitioner,
`
`v.
`
`MPH TECHNOLOGIES OY,
`Patent Owner.
`____________
`
`Case IPR2019-00820
`Patent 7,937,581
`____________
`
`EXHIBIT 2009
`
`DECLARATION OF PROFESSOR GEORGE N. ROUSKAS, PH.D.
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 1
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`I.
`
`II.
`
`TABLE OF CONTENTS
`
`Page
`
`INTRODUCTION ........................................................................................ 1
`
`QUALIFICATIONS ..................................................................................... 1
`
`III. BASES OF OPINIONS ................................................................................ 6
`
`IV. APPLICABLE LEGAL STANDARDS ...................................................... 8
`
`A. Ordinary Skill in the Art ........................................................................ 8
`
`B. Claim Construction.............................................................................. 10
`
`C. Obviousness (35 U.S.C. § 103) ........................................................... 10
`
`V.
`
`OVERVIEW OF THE ’581 PATENT AND THE STATE OF THE
`ART AT THE TIME OF THE INVENTION ..........................................14
`
`A. Technical Background ......................................................................... 15
`
`B. The Mobility Problem Addressed by the ’581 Patent ......................... 21
`
`C. The ’581 Patent’s Solution to the Mobility Problem .......................... 23
`
`VI. CLAIM CONSTRUCTION .......................................................................28
`
`VII. CLAIMS 1 AND 9 ARE PATENTABLE OVER THE
`COMBINATION OF ISHIYAMA AND MURAKAWA (GROUND 1)
` 42
`
`A. Overview of Ishiyama ....................................................................... 42
`
`B. The Petition Fails to Establish that the Prior Art Teaches the
`“Security Gateway” in “At Least One Mobile Terminal and
`Another Terminal and a Security Gateway Therebetween”
`and Other Limitations ...................................................................... 49
`
`1. Multiple Publications from the Relevant Timeframe
`Confirm that a Correspondent Host is Not a Security
`Gateway .................................................................................... 52
`
`i
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 2
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`2.
`
`3.
`
`4.
`
`5.
`
`Ishiyama’s Correspondent Host is Demonstrably Not a
`Security Gateway Because it is an End System with a
`Single Communication Interface ........................................... 54
`
`Ishiyama’s Description of the IPSec Processing Using the
`Security Databases Proves that the Correspondent Host is
`not a Security Gateway ............................................................. 55
`
`Petitioner’s Theory that the Correspondent Host Must
`be a Security Gateway Because IPSec Tunnel Mode is
`Used is Incorrect...................................................................... 57
`
`Petitioner’s Argument in this Proceeding that the
`Correspondent Host is a Security Gateway is
`Contradicted by the Position Taken in IPR2019-00821 ...... 66
`
`C. The Petition Fails to Establish that the Prior Art Discloses the
`“Other Terminal” in “At Least One Mobile Terminal and
`Another Terminal and a Security Gateway Therebetween”
`and Other Limitations ...................................................................... 69
`
`D. The Petition Fails to Establish that the Prior Art Teaches
`“While at the Second Address, the Mobile Terminal Sending a
`Request Message to the Gateway Address of the Security
`Gateway to Request the Security Gateway to Change the
`Secure Connection to Be Defined Between the Second Address
`and the Gateway Address of the Security Gateway” ..................... 77
`
`E. The Petition Fails to Establish that the Prior Art Teaches the
`“Mobile Terminal Sending a Secure Message . . . From the
`Second Address of the Mobile Terminal to the Other Terminal
`via the Security Gateway” ................................................................ 78
`
`F. Claim 9 Is Not Unpatentable Over the Combination of
`Ishiyama and Murakawa .................................................................. 83
`
`VIII. CLAIM 4 IS PATENTABLE OVER THE COMBINATION OF
`ISHIYAMA AND MURAKAWA (GROUND 1) BECAUSE THE
`PETITION FAILS TO ESTABLISH THAT THE PRIOR ART
`TEACHES THE “REQUEST MESSAGE AND/OR A REPLY
`MESSAGE IS ENCRYPTED AND/OR AUTHENTICATED” ............88
`
`ii
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 3
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`IX. CLAIMS 3 AND 5 ARE PATENTABLE OVER THE
`COMBINATION OF ISHIYAMA, MURAKAWA AND AHONEN
`(GROUND 2) ...............................................................................................91
`
`A. Overview of Ahonen .......................................................................... 92
`
`B. The Combination of Ishiyama, Murakawa and Ahonen Fails
`to Teach Sending a “Reply Back to the Mobile Terminal . . .
`From the Security Gateway” (Claim 3) or a “Reply Message
`to the Mobile Terminal at the Second Address to Confirm the
`Address Change” (Claim 5) .............................................................. 95
`
`C. The Prior Art Fails to Render Obvious Claims 6-7 ....................... 98
`
`X.
`
`CLAIM 8 IS PATENTABLE OVER THE COMBINATION OF
`ISHIYAMA, MURAKAWA AND FORSLOW (GROUND 3) ..............99
`
`XI. CONCLUSION .........................................................................................100
`
`
`
`iii
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 4
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`I.
`
`INTRODUCTION
`
`1.
`
`My name is George Rouskas. I have been retained as an expert
`
`witness to provide my independent opinion in regards with matters at issue in the
`
`inter partes review of U.S. 7,937,581 (“the ’581 Patent”) in the IPR2019-00820
`
`proceeding. I have been retained by MPH Technologies Oy (“MPH”), the Patent
`
`Owner, in the above proceedings. Petitioner in this case is Apple Inc. (“Apple”).
`
`2.
`
`Unless otherwise noted, the statements made herein are based on my
`
`personal knowledge, and if called to testify about this declaration, I could and
`
`would do so competently and truthfully.
`
`3.
`
`A detailed record of my professional qualifications including cases in
`
`which I was an expert is being submitted herewith as Exhibit 2004 and is
`
`summarized in Section II, infra.
`
`4.
`
`I am not a legal expert and offer no opinions on the law. However, I
`
`have been informed by counsel of the various legal standards that apply, and I have
`
`applied those standards in arriving at my conclusions.
`
`II.
`
`QUALIFICATIONS
`
`5.
`
`I am an Alumni Distinguished Graduate Professor with Tenure in the
`
`Department of Computer Science at North Carolina State University (NC State),
`
`where I also serve as the Director of Graduate Programs. I am an experienced
`
`researcher and educator in the field of computer networking, with expertise in
`
`1
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 5
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`Internet architectures and protocols, virtualization and cloud computing, mobile
`
`devices, network devices, network security and security protocols, in a variety of
`
`applications including providing for the protection of information transmitted
`
`between devices within and among networks.
`
`6.
`
`I have thirty years of experience in computer networking since I
`
`received my bachelor’s degree in 1989. I have twenty-five years of experience as a
`
`professor in the Department of Computer Science of NC State.
`
`7.
`
`During this time, I have led, overseen, and contributed to numerous
`
`research projects involving technical concepts that are related to the technology at
`
`issue in the IPR2019-00820 proceeding, which relates to the issue of providing
`
`mobility to secure connections over networks, such as where a first computer
`
`device in secure communication with a second computer device changes its
`
`location from a first address to a second address. For example, as part of our NSF-
`
`funded ChoiceNet project, my research group developed a new Internet
`
`architecture, a suite of communication protocols, and a proof-of-concept prototype
`
`implementation to enable real-time economic transactions in the network layer,
`
`including secure payments. For an earlier NSA-funded Jumpstart project, my
`
`group developed a novel signaling architecture and protocol for high-speed
`
`networks and designed relevant security mechanisms.
`
`2
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 6
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`8.
`
`I have taught courses on computer networks, Internet protocols, data
`
`structures and computer performance evaluation. In 1997 I created one of the first
`
`graduate level courses on Internet Protocols, which I teach regularly, and in which
`
`I cover in detail topics related to network security (including IPSec) and mobile IP.
`
`9.
`
`I received numerous accolades for my contributions to computer
`
`networking and was elected as Fellow of the IEEE in 2012. These include the
`
`Outstanding Service Award for the Optical Networking Technical Committee
`
`(ONTC) of the IEEE Communication Society (2019); the Joyce Hatch Service
`
`Award from the NC State Chapter of the Association for Computing
`
`Machinery/Association of Information Technology Professionals (ACM/AITP)
`
`(2018); Distinguished Lecturer in the IEEE (2010-2012); an IBM Faculty Award
`
`(2007); the Best Paper Award for the International Workshop on End-to-End
`
`Virtualization and Grid Management (EVGM) (2007) (with C. Castillo and K.
`
`Harfoush); the Best Paper Award for the International Symposium on
`
`Communication Systems, Networks and Digital Signal Processing (CSNDSP)
`
`(2006) (with B. Chen and R. Dutta); the ALCOA Foundation Engineering
`
`Research Achievement Award, NC State College of Engineering (2004); Alumni
`
`Outstanding Research Award, NC State (2003); a CAREER Award from the
`
`National Science Foundation (1997); and the Graduate Research Award from the
`
`Georgia Tech College of Computing (1994).
`
`3
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 7
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`10.
`
`I received my PhD in Computer Science (Georgia Institute of
`
`Technology, 1994); M.S. in Computer Science (Georgia Institute of Technology,
`
`1991); and B.S. in Computer Engineering (National Technical University of
`
`Athens, 1989).
`
`11.
`
`In 2000-2001, while on Sabbatical from NC State, I worked as
`
`Network Architect for Vitesse Semiconductor, where I was responsible for the
`
`design of a state-of-the-art 2.5 Gbps network processor.
`
`12. My work as an academic began in 1994, when I joined NC State as an
`
`Assistant Professor. In 1999, I was promoted to Associate Professor with Tenure at
`
`NC State. In 2002, I was promoted to the position of Professor at NC State.
`
`13.
`
`I have had visiting positions at a number of international universities,
`
`including positions as a Distinguished Scientist at King Abdulaziz University
`
`(Saudi Arabia, March 2013 to present); Visiting Professor at the Laboratoire
`
`d’Informatique University of Paris 6 (France, October 2012); Visiting Professor at
`
`the Universidad Tenia Federico Santa Maria (Chile, December 2008); and Visiting
`
`Professor at the Laboratoire de Methods’ Informatiques University of DeVry
`
`(France, July 2006, December 2002, June 2000).
`
`14.
`
`I have received funding from numerous agencies, foundations and
`
`companies for research on network design and communication. The sources of
`
`funding for this research include the National Science Foundation (NSF), the
`
`4
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 8
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`Defense Advanced Research Projects Agency (DARPA), the National Security
`
`Agency (NSA), Microsoft, IBM and Cisco.
`
`15.
`
`I have served in a number of leadership roles for the IEEE, including
`
`as Chair of the IEEE Communications Society’s Distinguished Lecturer Selection
`
`Committee (2016-2017); Vice Chair of the IEEE Communications Society’s
`
`Technical and Educational Activities Council (2016-2017); and Chair of the IEEE
`
`Communications Society’s Optical Networking Technical Committee (2016-2017).
`
`16.
`
`I have served in various editorial positions, including as founding
`
`Editor-in-Chief of IEEE Networking Letters (2018-present); founding Editor-in-
`
`Chief of Elsevier Optical Switching and Networking Journal (2004-2017);
`
`Associate Editor, IEEE/OSA Journal of Communications and Networking (2010-
`
`2012); Co-Guest Editor, JCM Journal of Communications, Special Issue on the
`
`“Advances in Communications and Networking,” vol. 6, no. 9, December 2011;
`
`Associate Editor, IEEE/ACM Transactions on Networking (2000-2004); Associate
`
`Editor, Computer Networks (2001-2004); Associate Editor, Optical Networks
`
`(2000-2004); and Co-Guest Editor, IEEE Journal on Selected Areas in
`
`Communications, Special Issue on “Protocols for Next Generation Optical WDM
`
`Networks,” vol. 18, no. 10, October 2000.
`
`17.
`
`I have graduated twenty-five Ph.D. students. Two received PhD
`
`dissertation awards, one received an NSF Career award, and one became an NSA
`
`5
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 9
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`Fellow. Three of my former Ph.D. students became Assistant Professors upon
`
`graduation, and the rest joined significant technology companies or research
`
`institutes, including RENCI (UNC-Chapel Hill), IBM Research, Google,
`
`Facebook, Cisco, Oracle, Ericsson, Riverbed Technologies, Sprint, and Sierra
`
`Wireless, among others. I have graduated twelve M.S. students.
`
`18. During the course of my career, I had more than 200 scientific
`
`articles, three books and ten book chapters published, which have collectively
`
`received more than 8500 citations (Google Scholar, as of November 21, 2019).
`
`These are summarized in my curriculum vitae.
`
`III.
`
`BASES OF OPINIONS
`
`19.
`
`In the course of conducting my analysis and forming my opinions, I
`
`have reviewed at least the materials listed below as well as all of the exhibits
`
`submitted by Patent Owner in IPR2019-00820 and IPR2019-00821:
`
`i.
`
`ii.
`
`U.S. Patent No. 7,937,581 and its prosecution history;
`
`Petition by Apple in IPR2019-00819;
`
`iii.
`
`Petition by Apple in IPR2019-00820;
`
`iv.
`
`Petition by Apple in IPR2019-00821;
`
`v.
`
`Declaration of Dr. David Goldschlag in IPR2019-00819;
`
`vi. Declaration of Dr. David Goldschlag in IPR2019-00820;
`
`vii. Declaration of Dr. David Goldschlag in IPR2019-00821;
`
`6
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 10
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`viii. Patent Owner’s Preliminary Response in IPR2019-00819;
`
`ix.
`
`Patent Owner’s Preliminary Response in IPR2019-00820;
`
`x.
`
`Patent Owner’s Preliminary Response in IPR2019-00821;
`
`xi.
`
`Institution Decision by the PTAB in IPR2019-00819;
`
`xii.
`
`Institution Decision by the PTAB in IPR2019-00820;
`
`xiii.
`
`Institution Decision by the PTAB in IPR2019-00821
`
`xiv. U.S. Pat. No. 7,620,810;
`
`xv. U.S. Pat. No. 8,037,302;
`
`xvi. U.S. Pat. No. 6,904,466 (“Ishiyama”);
`
`xvii. U.S. Pat. No. 7,028,337 (“Murakawa”);
`
`xviii. U.S. Pat. No. 6,976,177 (“Ahonen”);
`
`xix. WIPO Pub. WO 01/54379 A1 (“Ahonen WO”);
`
`xx. U.S. Pat. No., 6,954,790 (“Forslow”);
`
`xxi. Gupta et al., “Complete Computing,” WWCA '98 Proceedings of the
`Second International Conference on Worldwide Computing and Its
`Applications (March 4-5, 1998) (“Gupta”)
`
`
`xxii. Network Working Group Requests for Comments: 2401(S. Kent, R.
`Atkinson) (Nov. 1998), “Security Architecture for the Internet
`Protocol”) (RFC 2401)
`
`xxiii. Network Working Group Requests for Comments: 2002 (C. Perkins,
`ed.) (Oct. 1996), “IP Mobility Support” (RFC 2002)
`
`
`xxiv. RFC 1122, “Requirements for Internet Hosts -- Communication
`Layers (R. Braden; October 1989)
`
`
`
`7
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 11
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`IV.
`
`APPLICABLE LEGAL STANDARDS
`
`A. Ordinary Skill in the Art
`
`20. My opinions in this declaration are based on the understandings of a
`
`person of ordinary skill in the art, which I understand is sometimes referred to as
`
`an “ordinary artisan” or by the acronyms “POSITA” (person of ordinary skill in the
`
`art) or “PHOSITA” (person having ordinary skill in the art), as of the time of the
`
`invention, which I understand is here assumed to be at least September 27, 2002.
`
`This is because the application leading to the ’581 Patent was filed as a
`
`continuation application of the parent application, U.S. App. No. 12/560,481,
`
`which was filed on September 27, 2002. I also understand that the ’581 Patent
`
`application also asserted priority to the filing date (September 28, 2001) of the
`
`application filed in Finland, FI 20011910. See Ex. 1001 [’581 Patent] (Cover Page)
`
`0001. My analysis and conclusions are same whether the relevant time period is
`
`2001 or 2002. I understand that the person of ordinary skill in the art is a
`
`hypothetical person who is presumed to have known the relevant art at the time of
`
`the invention. By “relevant,” I mean relevant to the challenged claims of the ’581
`
`Patent.
`
`21.
`
`I understand that, in assessing the level of skill of a person of ordinary
`
`skill in the art, one should consider the type of problems encountered in the art, the
`
`prior solutions to those problems found in the prior art references, the rapidity with
`
`8
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 12
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`which innovations are made, the sophistication of the technology, the level of
`
`education of active workers in the field, and my own experience working with
`
`those of skill in the art at the time of the invention.
`
`22.
`
`In this case, Dr. Goldschlag has asserted in his declaration that a
`
`person of ordinary skill in the art as of the time of the ʼ581 Patent would have had
`
`a Bachelor’s degree in Electrical Engineering, Computer Engineering, Computer
`
`Science, or an equivalent field, as well as at least 2-5 years of academic or industry
`
`experience in computer network security. Ex. 1002 [Goldschlag dec.] ¶ 20. For the
`
`purposes of the subject IPR proceedings, I have been asked to employ this standard
`
`of a person of ordinary skill.
`
`23.
`
`I was at the time of invention, and am, one of more than ordinary skill
`
`in the art through my education and research experience. As of the date of the
`
`invention, I am very familiar with the types of problems encountered in computer
`
`network security, the types of prior art solutions described in prior art references,
`
`and the rapidity at which innovations are made. Indeed, I am very familiar with
`
`people having this level of skill in the area of computer network security. At the
`
`time of the invention, and since that time, I have been teaching undergraduate and
`
`graduate level courses in computer network architecture and protocols including
`
`various techniques for addressing information security.
`
`9
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 13
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`B. Claim Construction
`
`24.
`
`I understand that claims of the patent-at-issue in this IPR are generally
`
`interpreted according to their ordinary and customary meaning taking into
`
`consideration the so-called “intrinsic evidence” of the patent consisting of (1) the
`
`claim language; (2) the specification; and (3) the prosecution history.
`
`25.
`
`I understand that claim terms may be explicitly defined in the patent
`
`specification or they may be implicitly defined through consistent usage in the
`
`specification. I also understand that the scope of claim terms may be limited by
`
`statements in the specification or prosecution history where the applicant clearly
`
`disavows or disclaims subject matter.
`
`26. Petitioner has not offered any specific claim constructions, opting
`
`instead to assert that all claim terms should be accorded their ordinary and
`
`customary meaning. Pet., 11.
`
`27.
`
`I will offer my opinion on the proper claim construction of “security
`
`gateway” in the sections that follow.
`
`C. Obviousness (35 U.S.C. § 103)
`
`28.
`
`I have been informed that a patent may be invalid if the claimed
`
`invention would have been obvious at the time the invention was made to a person
`
`having ordinary skill in the art. I have been informed that the following factors
`
`10
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 14
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`must be evaluated to determine whether Petitioner has met its burden of proof that
`
`a claimed invention is obvious:
`
`1. The scope and content of the prior art relied upon by Petitioner;
`
`2. The difference or differences, if any, between each claim of the patent
`
`and the prior art;
`
`3. The level of ordinary skill in the art at the time the invention of the patent
`
`was made; and
`
`4. Any objective indicia of non-obviousness, including, for example:
`
`(1) commercial success of an embodiment; (2) a long-felt need;
`
`(3) skepticism; (4) failure by others to find the solution provided by the
`
`claimed invention; (5) copying by others of the subject matter of the
`
`claim invention; (6) unexpected results of the claimed invention;
`
`(7) acceptance of others and industry praise; and (8) licensing of the
`
`patents.
`
`29.
`
`I have been informed that a claim is not proved obvious merely by
`
`demonstrating that each of the elements was independently known in the prior art.
`
`I have been informed that many, if not all, inventions rely on building blocks
`
`already known, and claimed inventions almost of necessity will likely be
`
`combinations of what is already known.
`
`11
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 15
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`30.
`
`I have been informed that a combination of prior art references must
`
`disclose, teach or suggest all of the recited limitations of the claim for the invention
`
`to be found obvious.
`
`31.
`
`I have been informed that it is important in the obviousness inquiry to
`
`identify whether a reason existed at the time of the invention that would have
`
`motivated a person of ordinary skill in the art in the relevant field to combine or
`
`modify the prior art references in the manner proposed by the Petitioner so as to
`
`arrive at the claimed invention. Put another way, a finding of obviousness should
`
`be supported by an apparent reason to combine or modify the prior art references
`
`as proposed by the Petitioner.
`
`32.
`
`I have been informed that it is important in the obviousness inquiry
`
`that it is understood how the combination of references is supposed to work. An
`
`explanation of the operation of the combined references is often a prerequisite to
`
`showing that a person of ordinary skill in the art would have been motivated to
`
`make the proposed combination and would have had a reasonable expectation of
`
`success.
`
`33.
`
`I have been informed that a finding of obviousness “requires the
`
`additional showing that a person of ordinary skill at the time of the invention
`
`would have selected and combined those prior art elements in the normal course of
`
`research and development to yield the claimed invention.” Unigene Labs., Inc. v.
`
`12
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 16
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`Apotex, Inc., 655 F.3d 1352, 1360 (Fed. Cir. 2011). In addition, I have been
`
`informed that a person of ordinary skill in the art should have had a reasonable
`
`expectation of success in combining the references as proposed.
`
`34.
`
` In assessing obviousness, I have been instructed to consider both the
`
`ordinary creativity and common sense of the person of ordinary skill in the art. I
`
`also understand that it is impermissible for common sense to be applied to fill gaps
`
`in the prior art that fails to teach or suggest a limitation of the claim. I also
`
`understand that the obviousness inquiry should guard against hindsight bias or
`
`hindsight reconstruction where after-the-fact reasoning is applied to combine prior
`
`art elements using the claimed invention as a template, without establishing that, as
`
`of the date of the invention, there exists a motivation to combine or apparent
`
`reason to combine the prior art as proposed.
`
`35.
`
`In assessing obviousness, I have been instructed that, in order to
`
`qualify as proper prior art for an obviousness analysis, a reference must qualify as
`
`analogous art. I have been informed that a reference qualifies as analogous art with
`
`respect to the claims if it is either: (1) from the same field or endeavor as the
`
`patent; or (2) the reference is reasonably pertinent to the particular problem
`
`addressed by the invention. I have also been informed that for a reference to be
`
`reasonably pertinent, it must logically have commended itself during the ordinary
`
`course of development to an inventor’s attention in considering his problem.
`
`13
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 17
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`36.
`
`In assessing obviousness, I have also been instructed that, as noted
`
`above, secondary considerations can often be probative evidence of non-
`
`obviousness and can serve to avoid hindsight bias. I have been instructed that
`
`secondary considerations can be sufficient to overcome a prima facie case of
`
`obviousness. I have been instructed that Patent Owner can show non-obviousness
`
`if: (1) the industry praised their work; (2) their design was copied by others; (3)
`
`their design achieved a high level of commercial success; or (4) their invention had
`
`unexpected beneficial results, for example.
`
`V.
`
`OVERVIEW OF THE ’581 PATENT AND THE STATE OF THE ART
`AT THE TIME OF THE INVENTION
`
`For clarity to the reader, my citations will adhere to these formats:
`
` Petitions and other papers filed by the parties. Example: Pet., at 10,
`
`12) refers to the Petition at pages 10 and 12.
`
` Patents will be cited by their exhibit number, bates stamped page and
`
`specific column and line numbers when feasible. Example: Ex. 1004
`
`[Ishiyama] 0011 (1:10-12) refers to the Ishiyama patent at page 0011
`
`and Col. 1, lines 10-12. Ex. 1004 (1:10-12) refers to same passage of
`
`Ishiyama.
`
` Articles and other publications will be cited by their exhibit number,
`
`bates stamped page and their original page number when feasible (and
`
`14
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 18
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`line numbers or paragraph numbers, if appropriate). Ex. 2005 [RFC
`
`1122] 5.
`
`A. Technical Background
`
`37. Telecommunications networks can encompass a vast array of
`
`components including local area networks (LANs), wide area networks (WANs)
`
`and various computing devices all interconnected using intermediary networking
`
`devices. Intermediary networking devices such as routers enable different networks
`
`to be interconnected to function as an “internetwork,” that is, as an internet. Such
`
`interconnected networks can allow geographically dispersed users to communicate.
`
`Ex. 1001 [’581 Patent] 0007 (1:30-42).
`
`38. Normally, a person who mails a sealed letter does not want and does
`
`not expect that the contents of the letter will be read by a third party while the letter
`
`is en route to the intended recipient. In a similar manner, those parties who
`
`exchange communications between a first host device and a second host device
`
`want to protect the confidentiality and integrity of the information they are
`
`exchanging.
`
`39. The ’581 Patent explains that secure communications of messages
`
`across networks is extremely important. The ’581 Patent identifies various types of
`
`security that may be sought for the protection of messages:
`
`15
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 19
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`There is a need to protect data and resources from disclosure, to
`
`guarantee the authenticity of data, and to protect systems from network
`
`based attacks. More in detail, there is a need for confidentiality
`
`(protecting the contents of data from being read), integrity (protecting
`
`the data from being modified, which is a property that is independent
`
`of confidentiality), authentication (obtaining assurance about the actual
`
`sender of data), replay protection (guaranteeing that data is fresh, and
`
`not a copy of previously sent data), identity protection (keeping the
`
`identities of parties exchanging data secret from outsiders), high
`
`availability, i.e. denial-of-service protection (ensuring that the system
`
`functions even when under attack) and access control. Ex. 1001 [’581
`
`Patent] 0007 (1:43-55).
`
`40. At the time of the invention, there was a technique for message
`
`protection in computer networks that was described in an Internet specification
`
`document, “Security Architecture for the Internet Protocol,” that was issued by the
`
`Internet Engineering Task Force (IETF) Network Working Group as RFC 2401.
`
`See Ex. 1011 [Security Architecture for the Internet Protocol] (November 1998).
`
`This document refers to a technology for message protection known as “IPsec.”
`
`Id., 3 (“This memo specifies the base architecture for IPsec compliant systems.”)
`
`41. RFC 2401 describes the fundamental features and processes of IPSec
`
`secure connections:
`
`This memo specifies the base architecture for IPsec compliant systems.
`
`The goal of the architecture is to provide various security services for
`
`traffic at the IP layer . . . The following fundamental components of the
`
`16
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 20
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`IPsec security architecture are discussed in terms of their underlying,
`
`required functionality . . .
`
`a. Security Protocols -- Authentication Header (AH) and
`
`Encapsulating Security Payload (ESP)
`
`b. Security Associations -- what they are and how they work,
`
`how they are managed, associated processing
`
`c. Key Management -- manual and automatic (The Internet Key
`
`Exchange (IKE))
`
`d. Algorithms for authentication and encryption
`
`
`
`
`
`
`
`Id., [Section 1.1: Summary of Contents of Document] 3.
`
`42. The ’581 Patent explicitly references RFC 2401. Ex. 1001 [’581
`
`Patent] 0007 (2:12), 0009 (5:54-57). The ’581 Patent provides a detailed
`
`explanation of the features of IPSec:
`
`The IP security protocols (IPSec) provides the capability to secure
`
`communications between arbitrary hosts, e.g. across a LAN, across
`
`private and public wide area networks (WANs) and across the internet
`
`IPSec can be used in different ways, such as for building secure virtual
`
`private networks, to gain a secure access to a company network, or to
`
`secure
`
`communication with
`
`other
`
`organisations,
`
`ensuring
`
`authentication and confidentiality and providing a key exchange
`
`mechanism. Id., 0007 (1:59-66).
`
`43. Addressing the need for secure messaging, the ’581 Patent discloses
`
`that IPSec secure connections provide “confidentiality[,] integrity, authentication,
`
`replay protection, limited traffic flow confidentiality, limited identity protection,
`
`and access control based on authenticated identities.” Id., 0007 (1:67-2:3).
`
`17
`
`MPH Technologies Oy, Exhibit 2009
`Page 2009 - 21
`IPR2019-00820, Apple Inc. v. MPH Technologies Oy
`
`

`

`
`
`44. The ’581 Patent describes fundamental concepts of IPSec secure
`
`connections. For example, Security Associations (SAs) are data structures that are
`
`fundamental to IPSec processing. Id., 0007 (2:23-34). RFC 2401 also discloses
`
`SAs as fundamental to IPSec processing. Ex. 1011 [RFC 2401] 3. I understand the
`
`key role of SAs in IPSec from my personal experience with that technology.
`
`45. The ’581 Patent explains that an SA defines a one-way security
`
`relationship that protects the message traffic sent from sender to a receiver. If a
`
`two-way secure connection between the sender and receiver is desired, then two
`
`SA definitions are required. In some cases, multiple SAs, referred to as an “SA
`
`bundle,” are used to protect a data packet being sent from one address to another.
`
`In the ’581 Patent, the term “IPsec connection” encompasses an IPSec bundle or
`
`IPSec bundles (e.g., one for each direction) of SAs that define the security
`
`protocols that will be employed for message traffic between two host devices, for
`
`example. Ex

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