throbber
UNITED STATES PATENT AND TRADEMARK OFFICE
`
`
`
`
`
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
`
`
`
`
`
`BITDEFENDER INC.,
`Petitioner
`
`v.
`
`UNILOC USA, INC. and UNILOC LUXEMBOURG S.A.,
`Patent Owners
`
`
`
`
`
`
`
`
`IPR2017-1315
`PATENT 6,510,466
`
`
`
`
`
`
`
`
`PATENT OWNER RESPONSE TO PETITION
`PURSUANT TO 37 C.F.R. § 42.120
`
`
`
`
`
`
`i
`
`

`

`I.
`II.
`
`Tables of Contents
`INTRODUCTION ......................................................................................... 1
`THE '466 PATENT ....................................................................................... 2
`A.
`Effective Filing Date .......................................................................... 2
`B.
`Overview of the '466 Patent ............................................................... 3
`III. THE PETITION FAILS TO ESTABLISH UNPATENTABILITY ......... 5
`A.
`The Petition Does Not Render Obvious The Limitation
`“receiving at the server a login request form a user at the client”,
`as Claim 1 Requires ............................................................................ 6
`1.
`No Reasoning Or Support For The Proposed “single-
`server” Modification ................................................................ 6
`No Reasoning Or Support For The Proposed “offload”
`Modification ........................................................................... 16
`Claims 2, and 7-9 Are Patentable ..................................................... 19
`B.
`IV. THE SUPREME COURT IS CURRENTLY REVIEWING THE
`CONSTITUTIONALITY OF INTER PARTES REVIEW
`PROCEEDINGS .......................................................................................... 20
`V. CONCLUSION ............................................................................................ 20
`
`2.
`
`ii
`
`

`

`I.
`
`INTRODUCTION
`Pursuant to 35 U.S.C. § 313 and 37 C.F.R. § 42.120, Uniloc Luxembourg S.A.
`
`IPR2017-01315
`U.S. Patent 6,510,466
`
`(“Patent Owner”) submits this Response to the Petition for Inter Partes Review (“the
`
`Petition”) of U.S. Patent No. 6,728,766 (“the '466 Patent”) filed by BitDefender Inc.
`
`(“Petitioner”).
`
`In the Institution Decision (IPR2017-01315, Paper No. 7), trial was instituted
`
`for Claims 1, 2, and 7-9 of the ’466 Patent. Among other fatal deficiencies, the
`
`Petition does not establish obviousness for receiving login requests from users at the
`
`server where a plurality of application programs are installed. Rather than identify
`
`any disclosure within a printed publication, as required by law, Petitioner instead
`
`uses the patent as a blueprint to fundamentally rewrite Kasso’s system architecture.
`
`More specifically, Petitioner proposes, without reasoning or support, that a person
`
`of ordinary skill in the art would have been motivated to modify Kasso by
`
`incorporating the dedicated functionality of one server (the NIS server 230), instead,
`
`into an entirely different server (the HTTP server 208).
`
`Neither the Petition nor its attached declaration bothers to provide
`
`explanation, reasoning, or support for the overall system architecture of its proposed
`
`rewrite of Kasso. On the contrary, Petitioner and its declarant, Mr. Day, cannot even
`
`envision or articulate the overall system architecture of its proposed modification,
`
`much less articulate an explanation of why a person of ordinary skill in the art would
`
`1
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`modify the prior art reference to create the claimed invention. For this reason alone,
`
`all challenges to the ’466 Patent should be dismissed.
`
`The Petitioner’s so-called “reasons” for the proposed rewrite of Kasso is
`
`illusory. While in each instance the Petition purports to rely on expert testimony for
`
`support, a review of the declaration reveals that it merely parrots verbatim the
`
`conclusory attorney arguments of the Petition. Petitioner cannot merely speculate
`
`through its declarant, outside the four corners of the reference, to carry its burden.
`
`The Federal Circuit has instructed that determinations of obviousness should be
`
`based on evidence rather than on mere speculation or conjecture. And therefore, in
`
`addition to the above, the continuing and repeated failings of the petition to carry its
`
`burden provide additional reasons to dismiss all challenges to the ’466 Patent.
`
`In view of the reasons presented herein, Patent Owner respectfully submits
`
`that the Petition fails to meet its burden to prove unpatentability. Consequently, all
`
`challenges against the ’466 Patent should be dismissed.
`
`II. THE '466 PATENT
`A. Effective Filing Date
`The '466 Patent is titled “Methods, Systems and Computer Program Products
`
`for Distribution of Application Programs to a Target Station on a Network.” EX1001
`
`at [54]. The '466 Patent issued from U.S. Patent Application No. 09/211,528, filed
`
`December 14, 1998. The '466 Patent issued on January 21, 2003, after five years of
`
`2
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`thorough prosecution, and was originally assigned to the International Business
`
`Machines Corporation (“IBM”). EX1001 at [45], [73].
`
`B. Overview of the '466 Patent
`The '466 Patent relates to centrally managing the provision of application
`
`programs within a heterogeneous computer network environment. EX1001, 1:21-
`
`23; 3:24-36; 5:37-6:9. An application program (or simply “application”) is software
`
`written to perform a particular function for a user and is distinguishable from, for
`
`example, the operating system of a particular device, system-level software designed
`
`to operate the network, etc.
`
`As of 1998, designers of heterogeneous computer networks for large
`
`enterprises were confronted with various problems including, for example, users
`
`who login at different times from different client devices on the network—i.e., a
`
`roaming user. Around that same timeframe, computer network designers were also
`
`confronted with the problems of efficiently distributing and updating applications
`
`throughout the enterprise network, while maintaining consistency among roaming
`
`users as to both application updates and the application of preferences.
`
`The '466 teaches innovative solutions to those problems, among others. As
`
`disclosed in the ‘466 Patent, for example, the IBM inventors had reduced to practice
`
`various embodiments that enable a roaming user to access the user’s authorized
`
`applications from any client on the network, while consistently providing the user’s
`
`3
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`own selected preferences for those applications and maintaining application updates
`
`in a manner transparent to the user. In certain embodiments, application programs
`
`are provided on an as-needed basis and specifically-adapted to the specific client the
`
`user happens to be accessing at the time. EX1001, 11:4-8.
`
`Claims 1, 15, and 16 are the independent claims of the '466 Patent. For the
`
`convenience of the Board, independent Claim 1 is reproduced below:
`
`1. A method for management of application programs on a network
`including a server and a client comprising the steps of:
`
`installing a plurality of application programs at the server;
`
`receiving at the server a login request from a user at the client;
`
`establishing a user desktop interface at the client associated with the user
`responsive to the login request from the user, the desktop interface
`including a plurality of display regions associated with a set of the
`plurality of application programs installed at the server for which the
`user is authorized;
`
`
`receiving at the server a selection of one of the plurality of application
`programs from the user desktop interface; and
`
`
`providing an instance of the selected one of the plurality of application
`programs to the client for execution responsive to the selection.
`Figure 1 (copied below) of the '466 Patent illustrates certain features recited
`
`in the independent claims.
`
`4
`
`

`

`IPR2017-01315
`
`US. Patent 6,510,466
`
`
`
`III. THE PETITION FAILS TO ESTABLISH UNPATENTABILITY
`
`The Board instituted trial on the following grounds presented in the Petition:
`
`—@—
`l, 7, and 9 _ Kasso and Rad—licheF
`
`_— Kasso Raduchel and Bennetf
`
`l EX1009, US. Patent No. 5,832,505 (“Kasso”).
`2 EX1010, US. Patent No. 6,338,138 (“Raduchel”).
`3 EX101 1, US. Patent No. 5,615,367 (“Bennett”).
`
`

`

`9
`
`103
`
`IPR2017-01315
`U.S. Patent 6,510,466
`Kasso, Raduchel, and Olsen4
`
`
`A. The Petition Does Not Render Obvious the Limitation “receiving
`at the server a login request form a user at the client”, as Claim 1
`Requires
`1.
`No Reasoning or Support For The Proposed “single-server”
`Modification
`The Petition concedes that Kasso does not disclose the claim element
`
`“receiving at the server a login request from a user at the client.” It is undisputed
`
`Kasso expressly and specifically discloses at least three separate servers, one of
`
`which, the NIS server 230, handles authentication, which is separate and distinct
`
`from the HTTP server 208, that delivers applications to clients. See Pet. at 32.
`
`Nevertheless, the Petition posits that it “would have been obvious” to “implement
`
`the authentication functionality described for the NIS server 230 on the HTTP
`
`server 208 of Kasso”. Id. (emphasis added). The Board should not engage in such
`
`hindsight and speculative reconstruction outside the four corners of the reference.
`
`“[A] patent composed of several elements is not proved obvious merely by
`
`demonstrating that each of its elements was, independently, known in the prior art.”
`
`KSR Int'l Co. v. Teleflex Inc., 550 U.S. 398, 418, 127 S.Ct. 1727, 167 L.Ed.2d 705
`
`(2007). “In appropriate circumstances, a single prior art reference can render a claim
`
`obvious. However, there must be a showing of a suggestion or motivation to modify
`
`
`4 EX1012, U.S. Patent No. 5,905,860 (“Olsen”).
`
`6
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`the teachings of that reference to the claimed invention in order to support the
`
`obviousness conclusion.” SIBIA Neurosciences, Inc. v. Cadus Pharm. Corp., 225
`
`F.3d 1349, 1356 (Fed. Cir. 2000), aff'd, 659 F.3d 1109 (Fed. Cir. 2011). The
`
`obviousness analysis must focus on the knowledge and motivations of the skilled
`
`artisan at the time of the invention. InTouch Techs., Inc. v. VGO Commc'ns, Inc.,
`
`751 F.3d 1327, 1348 (Fed. Cir. 2014). In a case of obviousness, there must be an
`
`explanation of why a person of ordinary skill in the art would modify the prior art
`
`references to create the claimed invention. Cutsforth, Inc. v. MotivePower, Inc., 636
`
`Fed. Appx. 575, 577–78 (Fed. Cir. 2016) citing In re Kotzab, 217 F.3d 1365, 1371
`
`(Fed.Cir.2000); In re Rouffet, 149 F.3d 1350, 1359 (Fed.Cir.1998).
`
`The Petition allegedly proffers “three
`
`reasons”
`
`for
`
`its hindsight
`
`reconstruction. However, each “reason” fails at least because (1) the Petition fails to
`
`provide reasoning or support for the overall architecture of its proposed modification
`
`to Kasso, and (2) there is insufficient reasoning and support for a POSITA to make
`
`the alleged modification to Kasso.
`
`a)
`
`The Petition Provides No Explanation, Reasoning, Or
`Support For The Overall System Architecture Of The
`Proposed Modification Of Kasso
`As a threshold matter, the Petition fails to provide explanation, reasoning, and
`
`support for the overall architecture and system of its proposed modification to Kasso.
`
`Petitioner argues that it would have been obvious for a POSITA to modify Kasso
`
`7
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`such that the functionality of one of the at least three servers (the NIS server 230) is
`
`incorporated, instead, into a separate server (the HTTP server 208). However, Kasso
`
`discloses at least three distinct and separate servers – the JBS server 206, the HTTP
`
`server 208, and the NIS server 230. See EX1009, 4:54-5:7. Petitioner provides no
`
`explanation, reasoning, or evidence as to why a POSITA would have been motivated
`
`to completely redesign the Kasso system, such that the authentication functionality
`
`dedicated to a server designed for that purposes is, instead, implemented in an
`
`entirely different server having an expressly different purpose.
`
`The Petition even admits that it provides no explanation, reasoning, or support
`
`for its proposed modification, conceding that it would have “involved a change in
`
`the entities involved in intercommunication”, and merely concluding, through its
`
`expert, who also provides no reasoning or support, that doing so “would not have
`
`fundamentally altered
`
`the functioning of
`
`the authentication or delivery
`
`functionalities.” Pet. at 34; EX1008, Day Decl, ¶ 30. To make a showing of
`
`obviousness, there must be an explanation of why a person of ordinary skill in the
`
`art would modify the prior art reference to create the claimed invention. Cutsforth,
`
`636 Fed. Appx. at 577–78; In re Kotzab, 217 F.3d at 1371; In re Rouffet, 149 F.3d
`
`at 1359. And here, there is none.
`
`Instead of providing the required reasoning and support, the Petition merely
`
`remarks that “the ’466 patent itself envisions including multiple entities … on a
`
`8
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`single machine, and does not deem further explanation of such an approach to be
`
`necessary.” Pet. at 34. However, “[c]are must be taken to avoid hindsight
`
`reconstruction by using ‘the patent in suit as a guide through the maze of prior art
`
`references, combining the right references in the right way so as to achieve the result
`
`of the claims in suit.’” Grain Processing Corp., 840 F.2d at 1075 (internal citations
`
`omitted). Regardless, the invention of the ’466 Patent is irrelevant to motivation and
`
`reasoning to modify the at least three servers of Kasso to implement the
`
`authentication functionality from one server into another. Moreover, as will be
`
`discussed below, the Petition and Mr. Day cannot even envision or articulate the
`
`proposed modification, much less articulate an explanation of why a person of
`
`ordinary skill in the art would modify the prior art reference to create the claimed
`
`invention. Instead, there is only speculation upon speculation that the proposed
`
`modification “would have saved costs and potentially simplified the system
`
`architecture.” Pet. at 33-34; EX1008, ¶ 28 (emphasis added).
`
`For this reason alone, all challenges against the ’466 Patent should be
`
`dismissed. See SIBIA Neurosciences, Inc., 225 F.3d at 1356; see also InTouch
`
`Techs., 751 F.3d at 1348.
`
`b)
`
`Kasso Does Not “Suggest” A Single Server – Instead
`Kasso Distinguishes The Disclosure Of Its Figure 1
`From Its Figure 2
`Next, even considering the Petition’s alleged “three reasons” individually,
`
`9
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`each fails on the merits. First, contrary to what Petitioner argues, Kasso does not
`
`“suggest” in its description of Figure 1 that the alternative embodiment of Figure 2
`
`may be modified by combining the distinct servers into a single server. Kasso
`
`distinguishes its “computer system” in Figure 1 from the alternative “networked
`
`computer model” in Figure 2 at least on the basis that only the latter involves client-
`
`server communication over a network. See, e.g., EX1009 (Kasso), 4:46-53. The
`
`system of Figure 1 is self-contained and operates locally within the computer itself.
`
`Notably, the entire disclosure regarding the system of Figure 1 in Kasso never
`
`mentions a user logging in, because there is no network and no server to
`
`communicate with. This is confirmed by Kasso’s description of the system of Figure
`
`2, which is titled “NETWORK COMPUTER ENVIRONMENT”. EX1009, 4:45.
`
`Moreover, Kasso expressly states that the computer system of Figure 1 as
`
`corresponding only to a network computer (i.e., client) of Figure 2. Id. (“Each of the
`
`network computers may be configured in the form of computer system 100[.]”).
`
`Therefore, Kasso expressly distinguishes between its client computer systems and
`
`its multiple server systems, which must perform numerous and specific tasks not
`
`required or envisioned by the client computer systems. Regardless, to make a
`
`showing of obviousness, there must be an explanation of why a person of ordinary
`
`skill in the art would modify the prior art reference to create the claimed invention.
`
`Cutsforth, 636 Fed. Appx. at 577–78; In re Kotzab, 217 F.3d at 1371; In re Rouffet,
`
`10
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`
`149 F.3d at 1359. And again, there is none.
`
`Additionally, nothing in Figures 1 or 2, alone or together provides
`
`explanation, reasoning, or support for a POSITA to modify Kasso such that the
`
`functionality of one of the at least three servers (the NIS server 230) be incorporated
`
`into a separate server (the HTTP server 208) as Petitioner proposes.
`
`c)
`
`The Petition Provides No Explanation, Reasoning, Or
`Support For Its Conclusory Argument That
`“implementing two functions … on the same server”
`Would Have “saved costs and potentially simplified
`the system architecture”
`The Petition makes the conclusory argument, without explanation, reasoning,
`
`or support, that “implementing two functions … on the same server” would have
`
`“saved costs and potentially simplified the system architecture”. See Pet. at 33-34.
`
`And the Petition makes the further unsupported conclusory argument that “[a]
`
`single-machine implementation … would not have required the additional
`
`processing power of a dedicated authentication server.” Id. For all its conclusory
`
`propositions, Petitioner cites (without explanation) to a single paragraph in its expert
`
`declaration. See Pet. at 33-34. However, its expert declaration merely parrots the
`
`Petition’s conclusory statements verbatim, providing no substance or rational
`
`underpinning of its own. Petitioner cannot merely speculate through its declarant,
`
`outside the four corners of the reference, to carry its burden. The Federal Circuit has
`
`instructed that “legal determinations of obviousness, as with such determinations
`
`11
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`generally, should be based on evidence rather than on mere speculation or
`
`conjecture.” Alza Corp. v. Mylan Labs., Inc., 464 F.3d 1286, 1290 (Fed. Cir. 2006);
`
`K/S HIMPP v. Hear-Wear Techs., LLC, 751 F.3d 1362, 1365-66 (Fed. Cir. 2014)
`
`(finding the P.T.A.B. correctly rejected conclusory assertions of what would have
`
`been common knowledge in the art).
`
`Further, the obviousness analysis must focus on the knowledge and
`
`motivations of the skilled artisan at the time of the invention. InTouch Techs, 751
`
`F.3d at 1348. And there must be an explanation of why a person of ordinary skill in
`
`the art would modify the prior art reference to create the claimed invention.
`
`Cutsforth, 636 Fed. Appx. at 577–78; In re Kotzab, 217 F.3d at 1371; In re Rouffet,
`
`149 F.3d at 1359. There is nothing in the Petition or Mr. Day’s mere conclusory
`
`assertion that provides any such analysis. For example, nothing in the Petition or Mr.
`
`Day’s mere conclusory assertion provides explanation, reasoning, or support for a
`
`POSITA to modify Kasso such that the functionality of one specifically-designed
`
`server (the NIS server 230) is implemented, instead, within a distinct server designed
`
`for an entirely different purpose (the HTTP server 208), as Petitioner proposes. In
`
`fact, Petitioner cannot even envision its own proposed modifications to the system
`
`architecture of Kasso, the Petition and Mr. Day can only pile speculation upon
`
`speculation that the proposed modification “would have saved costs and potentially
`
`simplified the system architecture.” Pet. at 33-34; EX1008, ¶ 28 (emphasis added).
`
`12
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`The Petition Fails To Show Or Support Its
`Conclusory Argument Of Simple Substitution
`Petitioner undermines its own conclusory argument that “implementing
`
`d)
`
`authentication and delivery functionality on the same server, as opposed to distinct
`
`servers, involves the simple substitution of one known element for another (a server
`
`implementing two functions for two servers implementing the functions separately)
`
`to obtain predictable results, applying a known technique (authentication) to a
`
`known device (delivery server) ready for improvement to yield predictable results,
`
`and choosing from a finite number of identified, predictable solutions (single server
`
`and multi-server implementations for authentication and application delivery), with
`
`a reasonable expectation of success.” Pet. 34 (citing EX1008 ¶ 29, which again,
`
`merely repeats verbatim the same conclusory statement). For example, Petitioner
`
`concedes “[s]uch a single-machine implementation would have involved a change
`
`in the entities involved in intercommunication.” Pet. at 34. As another example,
`
`Petitioner cannot even envision its own proposed modifications to the system
`
`architecture of Kasso, and can only pile speculation upon speculation that the
`
`proposed modification “would have saved costs and potentially simplified the
`
`system architecture.” Pet. at 33-34; EX1008, ¶ 28 (emphasis added).
`
`In other words, if the Petitioner cannot even understand or articulate the
`
`resulting system architecture of its proposed modifications, then Petitioner has not
`
`shown that its proposed modifications “apply a known technique”, “obtain
`
`13
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`predictable results”, from a “finite number of identified, predictable solutions”, and
`
`“with a reasonable expectation of success.”
`
`Furthermore, as with the above, Petitioner cannot merely speculate through
`
`its declarant, outside the four corners of the reference, to carry its burden. The
`
`Federal Circuit has instructed that “legal determinations of obviousness, as with such
`
`determinations generally, should be based on evidence rather than on mere
`
`speculation or conjecture.” Alza Corp., 464 F.3d at 1290; Hear-Wear Techs., 751
`
`F.3d at 1365-66.
`
`Finally, the obviousness analysis must focus on the knowledge and
`
`motivations of the skilled artisan at the time of the invention. InTouch Techs, 751
`
`F.3d at 1348. And there must be an explanation of why a person of ordinary skill in
`
`the art would modify the prior art reference to create the claimed invention.
`
`Cutsforth, 636 Fed. Appx. at 577–78; In re Kotzab, 217 F.3d at 1371; In re Rouffet,
`
`149 F.3d at 1359. None of that is provided here, and nothing in the Petition’s and
`
`Mr. Day’s conclusory assertions provide explanation, reasoning, or support for a
`
`POSITA to modify such that the functionality of one specifically-designed server
`
`(the NIS server 230) is implemented, instead, within a distinct server designed for
`
`an entirely different purpose (the HTTP server 208), as Petitioner proposes.
`
`e)
`
`Kasso’s explicit description of separate, dedicated
`servers would lead a POSITA away from attempting
`to utilize a single server instead
`
`14
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`Kasso’s explicit description of separate, dedicated servers would lead a
`
`POSITA away from attempting to utilize a single server instead. In re Gurley, 27
`
`F.3d 551, 553 (Fed. Cir. 1994) (A prior art reference teaches away from the claimed
`
`invention when a person of ordinary skill, upon reading the reference, “would be led
`
`in a direction divergent from the path that was taken by the applicant.”). Kasso
`
`describes Figure 2 as a distributed system in which distinct, specialized servers
`
`perform particular tasks. Dr. DiEuliis Decl., EX2001 ¶¶ 64-69, 88. The NIS Server
`
`230, for example, controls access to the system by verifying whether usernames and
`
`password are correct and valid. Id. ¶ 68 (citing EX1009, 5:4-6, 5:38-39). By using a
`
`dedicated server as a security gateway, assets and sensitive information stored on
`
`other servers within the system is protected. Id. ¶ 90-92. Petitioner’s proposed
`
`“single-server” modification would eliminate that enhanced security aspect of the
`
`disclosure. Id. ¶ 93.
`
`Petitioner relies on the testimony of Mr. Day (who received no academic
`
`degree beyond a “Bachelor’s degree in Business Administration”)5 for the
`
`proposition that “implementing two functions such as authentication and delivery on
`
`the same server, as opposed to separate dedicated servers, would have saved costs
`
`
`5 See EX1008, Exhibit A. Petition did not provide the requisite page-labeling for any
`of its exhibits. The quoted statement from Mr. Day’s declaration appears on page 1
`of its attached Exhibit A, as originally numbered at the top of the page.
`
`15
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`and potentially simplified the system architecture.” Pet. 33-34 (citing EX1008 ¶ 28).
`
`Dr. DiEuliis disagrees (and evidently so did Kasso). According to Dr. DiEuliis, if a
`
`single-server architecture was such an obvious variant of the distributed system
`
`disclosed in Kasso, surely Kasso would have said so. EX2001 ¶ 88. The fact that
`
`Kasso only describes a distributed-server architecture, with a dedicated NIS Server
`
`230 for handling security, suggests to a POSITA that using separate, dedicated
`
`servers as disclosed was an intentional and necessary aspect of controlling access to
`
`Kasso’s distributed system. Id. ¶ 91.
`
`2.
`
`No Reasoning Or Support For The Proposed “offload”
`Modification
`For the same reasons as discussed above, the Petition’s alternative “offload”
`
`modification also fails. For example, the “three reasons” in this section are again,
`
`conclusory attorney argument which purports rely on Mr. Day’s expert declaration,
`
`however, as before, the paragraphs in Mr. Day’s declaration are identical to the
`
`paragraphs of the Petition. Compare Pet. at 35-36 with EX1008, ¶¶ 32-35. Petitioner
`
`cannot merely speculate through its declarant, outside the four corners of the
`
`reference, to carry its burden. Alza Corp., 464 F.3d at 1290; Hear-Wear Techs., 751
`
`F.3d at 1365-66.
`
`Contrary to the express and undisputed disclosure in Kasso that only the NIS
`
`Server 230 receives authentication requests from clients, Petitioner argues a
`
`16
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`POSITA would be motivated to deviate from that disclosure by, instead, receiving
`
`authentication requests at the HTTP Server 208 and then “offloading” the
`
`authentication process to the NIS Server 230. Petitioner’s concession that a POSITA
`
`would need to significantly deviate from the disclosure in Kasso to arrive at certain
`
`claim limitations for the “server” only confirms that there is no prima facie
`
`obviousness. The Board should reject Petitioner’s improper attempt to use the '466
`
`Patent as a blueprint to fundamentally rewrite the disclosure in Kasso. See, e.g., 35
`
`U.S.C. § 311(b); 37 C.F.R. § 42.104(b)(4); In re Sang Su Lee, 277 F.3d at 1345; K/S
`
`HIMPP, 751 F.3d at 1365-66.
`
`First, “having all client requests … directed to a single server”, as Petitioner
`
`proposes in the “offload” modification, is contrary to the express disclosure in Kasso
`
`and would not simplify communications at either the client side or the server side.
`
`Cf. Pet. 35. It is undisputed that Kasso discloses its distributed system, by intended
`
`design, uses various distinct servers to handle client requests. That disclosure leads
`
`away from directing all client requests to a single server. In re Gurley, 27 F.3d at
`
`553. Furthermore, directing all client requests to a single server, as Petitioner
`
`proposes, introduces a potential bottleneck concern that is otherwise addressed in
`
`Kasso’s distributed system. EX2001 ¶ 89. The proposed “offload” modification also
`
`requires additional server-to-server communications that are not required by the
`
`simplified design in Kasso. Id. ¶ 102. Implementation of those additional and
`
`17
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`undisclosed communications would unnecessarily consume bandwidth and
`
`processing power, thereby further undermining the alleged motivation to deviate
`
`from the disclosure in Kasso. Id.
`
`Second, Kasso itself does not suggest its distributed system presents the
`
`contrived security concerns identified in the Petition. Kasso expressly provides what
`
`it considers to be an adequate solution to security: a dedicated NIS Server 230 having
`
`the sole purpose of controlling access to the distributed system. EX1009, 5:34-44.
`
`A POSITA would not be motivated by that disclosure to look for some other way to
`
`address security. EX2001 ¶ 93. In the case of In re Omeprazole Patent Litigation,
`
`536 F.3d 1361 (Fed. Cir. 2008), the Federal Circuit affirmed a finding of
`
`nonobviousness because the alleged flaws in the prior art that ostensibly prompted
`
`the modification had not been recognized in the art itself. Thus, there would have
`
`been no reason to modify as proposed, even though the modification could have been
`
`done. Analogous reasoning and the same conclusion of nonobviousness apply here.
`
`Third, the Petition and the testimony cited therein provide no cognizable
`
`explanation with some rational underpinning in support of the ipse dixit statement:
`
`“receiving login requests and application selections at the same server and
`
`forwarding the login requests, as distinct from directly receiving login requests at
`
`one server and application selections at a different server, involves choosing from a
`
`finite number of identified, predictable solutions (direct v. indirect communication
`
`18
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`with a server), with a reasonable expectation of success.” Pet. 35-36 (citing EX1008
`
`¶ 34, which merely repeats verbatim the same conclusory statement). Petitioner’s
`
`unexplained incantation of magical obviousness catchphrases is inapposite here at
`
`least because Kasso does not leave it to POSITA to decide between two alternatives.
`
`Rather, as the Petition acknowledges, Kasso expressly discloses receiving and
`
`processing authentication requests at a distinct and separate NIS Server 230
`
`dedicated to that sole purpose.
`
`Finally, the obviousness analysis must focus on the knowledge and
`
`motivations of the skilled artisan at the time of the invention. InTouch Techs, 751
`
`F.3d at 1348. And there must be an explanation of why a person of ordinary skill in
`
`the art would modify the prior art reference to create the claimed invention.
`
`Cutsforth, 636 Fed. Appx. at 577–78; In re Kotzab, 217 F.3d at 1371; In re Rouffet,
`
`149 F.3d at 1359. None of that is provided, and nothing in the Petition’s and Mr.
`
`Day’s conclusory assertions in that section provide explanation, reasoning, or
`
`support for a POSITA to modify Kasso, where Petitioner cannot articulate or
`
`envision the resulting system architecture of the proposed modifications.
`
`B. Claims 2, and 7-9 Are Patentable
`Because Claims 2, and 7-9 depend directly or indirectly from Claim 1, for all
`
`the same reasons above, Claims 2, and 7-9 are also patentable.
`
`19
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466
`IV. THE SUPREME COURT IS CURRENTLY REVIEWING THE
`CONSTITUTIONALITY OF INTER PARTES REVIEW
`PROCEEDINGS
`The Supreme Court is currently considering the constitutionality of inter
`
`partes review proceedings. Oil States Energy Servs., LLC v. Greene’s Energy Grp.,
`
`LLC, 137 S. Ct. 2239 (2017). The constitutional challenge is primarily based on the
`
`argument that adversarial challenges to an issued patent—like inter partes
`
`reviews—are “Suits at common law” for which the Seventh Amendment guarantees
`
`a jury trial. U.S. Const. amend. VII; Markman v. Westview Instruments, Inc., 517
`
`U.S. 370, 377 (1996). Further, because patents are private property rights, disputes
`
`concerning their validity must be litigated in an Article III court, not before an
`
`executive branch agency. McCormick Harvesting Mach. Co. v. C. Aultman & Co.,
`
`169 U.S. 606, 609 (1898). Out of an abundance of caution, Patent Owner hereby
`
`adopts this constitutional challenge now to preserve the issue pending the Supreme
`
`Court’s decision.
`
`V. CONCLUSION
`For the forgoing reasons, Patent Owner respectfully submits that the Petition
`
`fails to meet its burden to prove unpatentability. Consequently, all challenges against
`
`the ’466 Patent should be dismissed.
`
`
`
`
`
`20
`
`

`

`Date: December 4, 2017
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`IPR2017-01315
`U.S. Patent 6,510,466
`Respectfully submitted,
`
`By: /s/ Brett A. Mangrum
`
`Brett A. Mangrum
`
`Attorney for Patent Owners
`
`Reg. No. 64,783
`
`Ryan Loveless
`
`Attorney for Patent Owners
`Reg. No. 51,970
`
`
`
`21
`
`

`

`IPR2017-01315
`U.S. Patent 6,510,466

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