`
`
`
`
`UNITED STATES PATENT AND TRADEMARK OFFICE
`
`____________
`
`BEFORE THE PATENT TRIAL AND APPEAL BOARD
`
` ____________
`
`UBISOFT ENTERTAINMENT S.A. AND SQUARE ENIX,
`Petitioners,
`
`v.
`
`UNILOC USA, INC. AND UNILOC LUXEMBOURG S.A.,
`Patent Owner.
`
`____________
`
`Case No. IPR2017-01827
`U.S. Patent No. 7,069,293
` ____________
`
`
`
`
`
`PETITION FOR INTER PARTES REVIEW
`
`OF U.S. PATENT NO. 7,069,293
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`INTRODUCTION ............................................................................................... 1
`I.
`II. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R.
`§ 42.104 .......................................................................................................... 1
`A. Grounds for Standing Under 37 C.F.R. § 42.104(a) ............................... 1
`Identification of Challenge Under 37 C.F.R. §42.104(b) and Relief
`B.
`Requested ............................................................................................. 1
`1. Level of Ordinary Skill in the Art .................................................. 2
`2. Claim Construction ........................................................................ 2
`III. OVERVIEW OF THE ‘293 PATENT ............................................................. 7
`A. Description of the ‘293 Patent ................................................................. 7
`B. Prosecution History of the ‘293 Patent .................................................... 8
`C. Prior Inter Partes Review Petition of the ‘293 Patent ............................. 9
`IV. THERE IS A REASONABLE LIKELIHOOD THAT THE CHALLENGED
`CLAIMS ARE UNPATENTABLE .............................................................. 10
`A. TME Cookbook Anticipates Claims 1, 12, and 17 under §102(b) ........ 10
`V. MANDATORY NOTICES UNDER 37 C.F.R. § 42.8(A)(1) ......................... 50
`A. Real Party-In-Interest and Related Matters ........................................... 50
`B. Lead and Back-Up Counsel Under 37 C.F.R. § 42.8(b)(3) ................... 51
`C. Payment of Fees Under 37 C.F.R. § 42.103 .......................................... 51
`VI. CONCLUSION .............................................................................................. 51
`
`
`
` ii
`
`
`
`I.
`
`INTRODUCTION
`
`Petitioners request Inter Partes Review (“IPR”) of claims 1, 12, and 17 of
`
`U.S. Patent No. 7,069,293 (“‘293 Patent”). EX1001.
`
`II. REQUIREMENTS FOR INTER PARTES REVIEW UNDER 37 C.F.R.
`§ 42.104
`A. Grounds for Standing Under 37 C.F.R. § 42.104(a)
`Petitioners certify that the ‘293 Patent is available for IPR and that no
`
`Petitioner is barred or estopped. Specifically, Petitioners state: (1) they are not the
`
`owner of the ‘293 Patent; (2) have not filed a civil action challenging the validity
`
`of any claim of the ‘293 Patent; (3) this Petition is timely filed less than one year
`
`after it was served with a complaint alleging infringement of the ‘293 Patent; and
`
`(4) this Petition is filed more than nine months after the ‘293 Patent issued.
`
`B.
`
`Identification of Challenge Under 37 C.F.R. §42.104(b) and Relief
`Requested
`
`In view of the prior art, evidence, and discussion of claim limitations, claims
`
`1, 12, and 17 of the ‘293 Patent are unpatentable and should be cancelled. 37 C.F.R.
`
`§42.104(b)(1). This review is governed by pre-AIA §§102 and 103.
`
`Proposed Statutory Rejections for the ‘293 Patent
`
`Claims 1, 12, and 17: Anticipated under §102(b) by TME Cookbook [EX1002]
`
`
`
`
`
` 1
`
`
`
`1.
`
`Level of Ordinary Skill in the Art
`
`A person of ordinary skill in the field of computer networking at the time of
`
`the alleged invention, December 14, 1998, (“POSITA”) would have had at least an
`
`undergraduate degree, in computer science, computer engineering, or a related
`
`field or an equivalent number of years of working experience. In addition, a
`
`POSITA would have at least one to two years of experience in networking
`
`environments, including at least some experience with management of application
`
`programs in a network environment.
`
`2.
`
`Claim Construction
`
`A claim subject to IPR receives the “broadest reasonable construction in
`
`light of the specification of the patent in which it appears.” 37 C.F.R. §42.100(b).
`
`Unless otherwise noted below, Petitioners propose, for purposes of this proceeding
`
`only, that the claim terms of the ‘293 Patent are presumed to take on their ordinary
`
`and customary meaning that the term would have to one of ordinary skill in the art.
`
`The claim construction analysis is not, and should not be viewed as a concession
`
`by Petitioners as to the proper scope of any claim term in litigation. These
`
`assumptions are not a waiver of any argument in any litigation that claim terms in
`
`the ‘293 Patent are indefinite or otherwise invalid or unpatentable.
`
`
`
` 2
`
`
`
`a. “means for providing to the network management server an
`application program to be distributed to remote servers” (Claim
`12)
`
`“computer readable program code that provides to the network
`management server an application program to be distributed to
`remote servers” (Claim 17)
`
`The stated function is “providing to the network management server an
`
`application program to be distributed to remote servers.” The disclosed structure
`
`for performing the function is a disk or storage device accessible to the network
`
`management server on which the application program is placed, and equivalents
`
`thereof. EX1001 at 17:55-58 (“[O]perations begin when the application software
`
`to be distributed is placed by a system administrator on a disk or storage device
`
`accessible by Tivoli™ server 20 (FIG. 1).”); see also id. at 5:36-40, Fig. 8 (block
`
`110).
`
`b. “means for specifying a source directory and a target directory
`for distribution of the application program” (Claim 12)
`
`“computer readable program code that specifies a source
`directory and a target directory for distribution of the application
`program” (Claim 17)
`
`The stated function is “specifying a source directory and a target directory
`
`for distribution of the application program.” The disclosed structure is a server
`
`(Claim 12) or code/software (Claim 17) programmed to provide an input screen for
`
`allowing a user to enter: 1) a source directory path indicating the directory path on
`
`the server of the application program to be distributed; and 2) a target directory
`
`
`
` 3
`
`
`
`path indicating “a directory path on a receiving device which will be used for
`
`software package delivery at each of the selected target on-demand servers 22, 22’
`
`receiving distribution of the custom file package,” and equivalents thereof.
`
`EX1001 at 18:46-61; see also id. at 17:58-61, Fig. 8 (block 112), Fig. 9A (block
`
`132), Fig. 10 (Depicting “Source Path” and “Target Path” inputs on user interface).
`
`c. “means for preparing a file packet associated with
`the
`application program, the file packet including a segment
`configured to initiate registration operations for the application
`program at the target on-demand server” (Claim 12)
`
`“computer readable program code means that prepares a file
`packet associated with the application program, the file packet
`including a segment configured to initiate registration operations
`for the application program at the target on-demand server”
`(Claim 17)
`
`The stated function is “preparing a file packet associated with the application
`
`program, the file packet including a segment configured to initiate registration
`
`operations for the application program at the target on-demand server.”
`
`“Registration operations” must at least include “maintaining at the on-demand
`
`server a profile management list identifying application programs available for use
`
`by the user.” See Claim 4. Additionally, a “profile management list” must at least
`
`“include[] a designation of authorized users for application programs.” See Claim
`
`5. EX1001 at 17:65-18:3, 4:14-22, 18:8-29, 19:5-13, 19:22-37, 20:15-32.
`
`Accordingly, the claimed function includes a segment configured to designate a list
`
`of authorized users for the application program. The necessary and corresponding
`
`
`
` 4
`
`
`
`disclosed structure is a server (Claim 12) or code/software (Claim 17) programmed
`
`to perform steps 134, 140, 142, and 144 of Figure 9A and equivalents thereof.
`
`Namely, the server (Claim 12) or code/software (Claim 17) is programmed to: 1)
`
`create a file package definition (block 134); 2) determine if a file name, such as for
`
`an after distribution script, has been specified (block 140) and, if so, add a
`
`command script to the package of information to be distributed to the target on-
`
`demand server (block 142); and 3) save the file package definition. EX1001 at Fig.
`
`9A, 19:17-38. The determination at step 136 of Fig. 9A is not necessary structure
`
`to performing the claimed function. To be able to complete the claimed function in
`
`accordance with Fig. 9A, there must necessarily be an existing source directory or
`
`the function would terminate before completion. Where the function is performed
`
`to completion, the determination in step 136 must always be “yes” rendering the
`
`determination unnecessary to performance of the claimed function.
`
`d. “means for distributing the file packet to the target on demand
`server to make the application program available for use by a
`user at a client” (Claim 12)
`
`“computer readable program code means that distributes the file
`packet to the target on-demand server to make the application
`program available for use by a user at a client” (Claim 17)
`
`The stated function is “distributing the file packet to the target on demand
`
`server to make the application program available for use by a user at a client.” The
`
`disclosed necessary structure for performing the claimed function is a server
`
`
`
` 5
`
`
`
`(Claim 12) or code/software (Claim 17) programmed to perform steps 150 and
`
`164-168 of Figure 9B and a recipient on-demand server (Claim 12) or
`
`code/software (Claim 17) programmed to perform steps 170-172, 176 and 184 of
`
`Figure 9C. EX1001 at Figs. 9B, 9C, 19:39-20:32. From Fig. 9B, steps 152-158
`
`relate to modifying a preexisting file package which is not a required component of
`
`the claimed function. Steps 160-162 are unnecessary for the same reasons
`
`described with respect to Fig. 9A above. For Fig. 9C, step 174 and 178-182 are
`
`unnecessary to the claimed function. Accordingly, the necessary corresponding
`
`structure is a server (Claim 12) or code/software (Claim 17) that is at least
`
`programmed to: 1) commence a file package distribution task; 2) determine if any
`
`before distribution program has been designated and, if so, process the before
`
`distribution program; 3) distribute the file package to the specified target servers.
`
`Additionally the recipient on-demand server (Claim 12) or code/software (Claim
`
`17) that is at least programmed to: 4) determine if any after distribution program
`
`has been designated by the file package and, if so, process the after distribution
`
`program; and 5) execute code to perform registration operations consistent in scope
`
`with at least the “registration operations” described above with respect to Element
`
`12(c), and make the application available to the user at a client.
`
`
`
` 6
`
`
`
`III. OVERVIEW OF THE ‘293 PATENT
`A. Description of the ‘293 Patent
`The ‘293 Patent was filed as U.S. Patent Application 09/870,608 on May 31,
`
`2001 (EX1001), claiming priority to U.S. Patent 6,510,466, filed on December 14,
`
`1998. The ‘293 Patent relates to centralized control of software distribution for a
`
`computer network managed by a network management server. EX. 1001, 4:14-16.
`
`Figure 1 of the ‘293 is reproduced below.
`
`
`
`Figure 1 illustrates a computer network according to an embodiment of the
`
`invention. Id. at 6:60-63. In particular, network management server 20 is
`
`
`
`
`
` 7
`
`
`
`connected to on-demand servers 22 and 22’ which are in turn connected to client
`
`stations 24 and 24’ and 26 and 26’ respectively. Id. at 6:63-7:9.
`
`The ‘293 patent describes a method of distributing software from the
`
`network management server to the on-demand servers. Id. at 17:20-18:36. Using
`
`a network management server managed computer network “such as a Tivoli
`
`environment,” application programs are distributed as file packages (packets) to
`
`on-demand servers. Id. at 4:14-18. The file packet includes data required to install
`
`and register the application program on the on-demand server and make it
`
`available to authorized users. Id. at 4:18-22.
`
`Prosecution History of the ‘293 Patent
`
`B.
`The ‘293 Patent was filed on May 31, 2001, as a divisional of U.S. Patent
`
`No. 6,510,466, including 15 claims submitted in a Preliminary Amendment.
`
`EX1003, ‘293 Patent File History at Claims and Preliminary Amendment. On
`
`September 8, 2004, the Examiner rejected all claims as obvious under 35 U.S.C.
`
`§103(a). Id. at 9/8/2004 Non-Final Rejection. In response, Patent Owner amended
`
`the independent claims to “clarify that the target station is an on-demand server
`
`and that the file packet is distributed to ‘make the application program available for
`
`use by a user at a client.’” Id. at 12/9/2004 Office Action Response at p. 7. Patent
`
`owner also added six additional dependent claims.
`
`
`
` 8
`
`
`
`On April 22, 2005, the Examiner again rejected all claims under the
`
`previously-cited prior art as well as a new reference, U.S. Patent Application No.
`
`2003/0010241 to Cheng, Jr. (“Cheng”), which was cited as teaching “providing a
`
`file packet to target on-demand servers to initiate registration operations to make
`
`an application program available to a use[r] at a client.” Id. at 4/22/05 Non-Final
`
`Rejection at p.2. In response, Patent Owner argued that Cheng did not “enable
`
`availability of a program at a target on-demand server” as claimed, but instead
`
`“assumes the program is already available at the service provider computer.” Id. at
`
`6/24/2005 Office Action Response at p.9.
`
`On September 22, 2005, the Examiner again rejected all claims under the
`
`previously-cited art as well as a “new prior art” – U.S. Patent No. 6,047,194 to
`
`Andersson (“Andersson”) – to teach “including a segment configured to initiate
`
`registration operations for the application program at the target station in the file
`
`packet.” Id. 9/22/2005 Non-Final Rejection at 2. Patent Owner responded,
`
`arguing that Andersson did not teach the limitation. Id. at 11/9/2005 Office Action
`
`Response at p. 8-9. On February 23, 2006, the USPTO mailed a Notice of
`
`Allowability and the patent issued on June 27, 2006.
`
`Prior Inter Partes Review Petition of the ‘293 Patent
`
`C.
`On November 10, 2016, Unified Patents filed a petition for inter partes
`
`review challenging all claims of the ‘293 patent (“the Unified IPR”). IPR 2017-
`
`
`
` 9
`
`
`
`00184, Petition, Paper 1. The Unified IPR proposed that independent claims 1, 12,
`
`and 17, were obvious over (1) the combination of U.S. Patent No. 5,845,090 to
`
`Collins (“Collins”) and the IBM On-Demand Handbook (Id. at 20-23), and the
`
`combination of U.S. Patent No. 6,446,198 to Gupta (“Gupta”) and U.S. Patent No.
`
`5,950,010 to Hesse (“Hesse”).
`
`The Board denied institution of the Unified IPR. IPR 2017-00184,
`
`Institution Decision, Paper 9. In doing so, the Board determined that for purposes
`
`of the institution decision, it was not necessary to construe any terms. Id. at 5. As
`
`to both grounds of rejection, however,
`
`the Board determined
`
`that
`
`the
`
`Petitioner had not established that the cited references taught “preparing a file
`
`packet associated with the application program and including a segment configured
`
`to initiate registration operations for the application program at the target on-
`
`demand server.” Id.at 8-21.
`
`IV. THERE IS A REASONABLE LIKELIHOOD THAT THE
`CHALLENGED CLAIMS ARE UNPATENTABLE
`
`The following prior art references disclose each limitation of the Challenged
`
`Claims. As such, the Challenged Claims are unpatentable. Included below are
`
`exemplary citations to the prior art references.
`
`TME Cookbook Anticipates Claims 1, 12, and 17 under §102(b)
`
`A.
`The TME Deployment Cookbook is dated April 1997 on its face, and
`
`appears in the Internet Archive’s Wayback Machine as being publicly available
`
`
`
` 10
`
`
`
`online
`
`via
`
`the
`
`web
`
`address
`
`https://web.archive.org/web/19970716014351/http://www.redbooks.ibm.com:80/S
`
`G244976/sg244976.htm at least as early as August 3, 1997 (EX1002; see generally
`
`EX1004, Declaration of Mark Lang), and is therefore prior art under at least
`
`§102(b).1
`
`
`
` 1
`
` Petitioners note that panels of the Board have previously held a printout of the
`
`Internet Archive’s Wayback Machine to be “facially [] authentic and is
`
`authenticated further by accessing the website.” IPR2013-00465, SDI Technologies,
`
`Inc. v. Bose Corp., Paper 40 at 13 – 16; see, e.g., IPR2015-01460, Crestron
`
`Electronics, Inc. v. Intuitive Building Controls, Inc., Paper 14, at 12 (finding that
`
`Internet Archive printout constitutes printed publication under §102(b)) and
`
`IPR2015-01460, EX1002 (Internet Archive Affidavit explaining how date of an
`
`archived web page can be determined from the URL printed on each archived web
`
`page). The Board in SDI Technologies noted that the Internet Archive’s standard
`
`affidavits do not materially add anything to the record to establish authenticity.
`
`IPR2013-00465, Paper 40 at 15; see also
`
`IPR2016-001187, Rubicon
`
`Communications, LP v. Lego A/S, Paper 38 at 12-13 (granting institution and
`
`noting that Wayback Machine printouts bearing logo of Internet Archive and a
`
`
`
`
`
` 11
`
`
`
`Claim 1. A method for distribution of application programs to a target on-
`demand server on a network comprising the following executed on a centralized
`network management server coupled to the network:
`
`See TME Cookbook applied to Claim 12.
`
`[1(a)] providing an application program to be distributed to the network
`management server;
`
`See TME Cookbook applied to Element 12(a).
`
`[1(b)] specifying a source directory and a target directory for distribution of the
`application program;
`
`See TME Cookbook applied to Element 12(b).
`
`[1(c)] preparing a file packet associated with the application program and
`including a segment configured to initiate registration operations for the
`application program at the target on-demand server; and
`
`See TME Cookbook applied to Element 12(c).
`
`[1(d)] distributing the file packet to the target on-demand server to make the
`application program available for use by a user at a client.
`
`See TME Cookbook applied to Element 12(d).
`
`Claim 12. An application program distribution system for distributing
`application programs to a target on-demand server on a network executing on a
`centralized network management server coupled to the network, the system
`comprising:
`
`Like the ‘293 Patent, the TME Cookbook describes the Tivoli Management
`
`Environment (“TME”) version 10 software, including the TME 10 Software
`
`
`URL indicating Internet Archive as the source were sufficient to make threshold
`
`showing regarding authenticity of the printouts).
`
`
`
` 12
`
`
`
`Distribution. Compare, e.g., EX1002, TME Cookbook at p.17 (“We use the latest
`
`features in TME 10 Software Distribution and show how to integrate them with
`
`other components of Tivoli Management Environment (TME) 10, Tivoli/IBM's
`
`solution for enterprise systems management. … We also show an example of a
`
`large customer environment where TME 10 Software Distribution is used for
`
`typical software distribution tasks in a Windows NT environment.”) with EX1001
`
`at 18:4-6 (“The software distribution operations at block 116 may be accomplished
`
`using the software deployment capabilities, for example, of the TME 10TM
`
`package.”), 7:10-13 (“System 10, as illustrated in FIG. 1, is a centrally managed
`
`computer network with Tivoli™ server 20 acting as the central administration
`
`station executing network management software such as TME 10™ from Tivoli
`
`Systems, Inc.”).
`
`The TME Cookbook discloses an application program distribution system,
`
`such as using TME 10 Software Distribution. Namely, TME 10 Software
`
`Distribution is an application program that, when installed on a Tivoli
`
`Management Region (“TMR”) Server (i.e., centralized network management
`
`server) allows for distribution of application programs to managed nodes (i.e.,
`
`target on-demand servers) on the network. Additionally, when the TME 10
`
`UserLink application is installed on the TMR server, managed nodes, and all PC
`
`managed nodes, each managed node can act as an “on-demand server” in that a
`
`
`
` 13
`
`
`
`user at a PC managed node (i.e., client) can decide when a software packet will be
`
`installed from the managed node.
`
`“In our real customer environment, we have a slow link between the Tivoli
`Management Region (TMR) server and the several managed nodes. Because
`of this circumstance, we want to distribute the data once from the TMR
`server over the slow link to the managed nodes, but start the distribution to
`the PC managed node from the TMR server. To avoid inadvertently altering
`the data on the PC managed nodes, we create a file package block from our
`file package. With this example, we also show how the compression option
`works. To keep the systems busy, we distribute the entire MS Office 95 code.”
`
`EX1002, TME Cookbook at p.259.
`
`“TME 10 Software Distribution 3.1 (Courier 3.1) is used for the software
`distribution. So you can push the software packages from the TMR server
`via managed node to the PC managed node.
`
`For the pull function, the TME 10 UserLink application is installed on the
`TMR server, managed nodes and all PC managed nodes, to allow the user at
`the PC managed node to decide when a software package will be installed
`from the managed node.”
`
`Id. at p. 205.
`
`TME Cookbook discloses an exemplary network that includes a TMR server
`
`(i.e., network management server), FOXTROT, which includes a Windows NT
`
`Server 4.0 operating system and is installed with TME 10 Framework 3.1 and
`
`TME 10 Software Distribution 3.1 software. The network also includes a
`
`
`
` 14
`
`
`
`Managed Node (i.e., target on-demand server), ROMEO, which also includes a
`
`Windows NT Server 4.0 operating system and is installed with TME 10
`
`Framework 3.1 and TME 10 Software Distribution 3.1 software. The network
`
`further includes a PC managed node (i.e., client), JULIET, which includes a
`
`Windows NT Workstation 4.0 operating system and is installed with TME 10
`
`Agent and Tivoli TCP/IP Agent 3.0 software. Id. at pp.205-206.
`
`
`
`Additionally, the TME Cookbook discloses that a TMR Server called
`
`FOXTROT can be installed with the TME 10 Desktop software, which provides a
`
`graphical user interface for the Tivoli Management Environment and through
`
`which an administrator can perform all management functions for the network.
`
`“TME 10 Desktop is the Graphical User Interface (GUI) for the Tivoli
`Management Environment. From this desktop, you can perform all
`management functions. You can install the GUI on a Windows, OS/2 or
`UNIX system. This book guides you through the installation on our Windows
`NT TMR Server (FOXTROT). For more information about the desktop, refer
`to the Desktop for Windows User's Guide 3.1.”
`
`Id. at p. 215.
`
`[12(a)] means for providing to the network management server an application
`program to be distributed to remote servers;
`
`The TME Cookbook discloses the function. Namely, TME Cookbook
`
`discloses that, prior to creating a file package or file package block for distribution,
`
`an administrator installs the application program to be distributed (e.g., Microsoft
`
`
`
` 15
`
`
`
`Office for Windows 95) to a storage device accessible to a TMR server (i.e.,
`
`network management server). TME Cookbook discloses the structure for
`
`performing the function is a storage device associated with the network
`
`management server on which the application program is placed. For example,
`
`TME Cookbook discloses that an application program for distribution, such as
`
`Microsoft Office, can be installed on a source (such as TMR server) by installing
`
`the program from a CD-ROM or Floppy Disk to the source hard drive:
`
`“We are now ready to perform the manual installation of Microsoft Office
`for Windows 95. …
`
`Click on Install Software. …
`
`Click on Browse to change to the source directory of Microsoft Office. As we
`are installing Microsoft Office for Windows 95 from the CD drive (D:) in
`this example, we change the Look in selection box to D:.
`
`Before performing this step, make sure that the Microsoft Office for
`Windows 95 CD has been inserted into the CD drive. …”
`
`EX1002, TME Cookbook at pp.120-121; see generally id. at pp.119-122.
`
` “As we are installing Freelance Graphics 2.1 for Windows from the diskette
`drive in this example, we change the Look in selection box to Floppy (A:).
`
`Before performing this step, make sure that the first installation diskette of
`Freelance Graphics has been inserted in diskette drive A. …
`
`The installation of Freelance Graphics on tango is now completed.”
`
`Id. at pp.106-107; see generally id. at pp.104-110.
`
`
`
` 16
`
`
`
`“In the Hosts list box, we could select either TMR server foxtrot or managed
`node romeo, but the program, HIJAAK, that we want to distribute, is on host
`romeo.”
`
`Id. at p.239; see also id. at p. 691 (Figure 371); see generally id. at pp. 236-243.
`
`In the context of generating a file package block for distribution, TME
`
`Cookbook discloses that the MS Office application program is installed on the
`
`ROMEO managed node C: drive, which is accessible to the TMR server including
`
`the application files in the file package block.
`
`“Now we want to create a file package block file from our File Package
`MSOffice_Files. The difference between a file package and a file package
`block is that the file package contains only pointers to the files which are
`going to be distributed. The file package block contains all files.”
`
`EX1002, TME Cookbook at p.260; see also id. at p.259 (“we want to distribute the
`
`data once from the TMR server over the slow link to the managed nodes”); pp.
`
`259-260 (describing creating file package and properties where “source host” is set
`
`to “Romeo” and “Source Directories & Files” is set to C:/MSOffice, depicted in
`
`Figure 422 below); p.246 (“We perform all steps from foxtrot (the TMR server).
`
`The data files and the procedure that we want to use are on romeo (a managed
`
`node).”); p.21 (“In the TMR controlled by foxtrot there is a managed node romeo
`
`attached to it[.]”).
`
`
`
` 17
`
`
`
`
`
`Id. at p.772 (Figure 422); see generally id. at pp.236-251, pp.259-265.
`
`Consistent with the ‘293 Patent disclosed embodiment, each TMR server
`
`and/or managed node acts as the central administration station executing TME
`
`10TM network management software from Tivoli Systems, Inc., and is therefore a
`
`“network management server.” Compare, e.g., EX1002, TME Cookbook at p.72
`
`
`
` 18
`
`
`
`(“foxtrot is the TMR Server running Windows NT Server 4.0”) and pp.205-206
`
`(disclosing FOXTROT TMR Server installed with TME 10 Framework 3.1 and
`
`TME 10 Software Distribution 3.1) with EX1001 at 7:10-13.
`
`[12(b)] means for specifying a source directory and a target directory for
`distribution of the application program;
`
`TME Cookbook discloses the function – specifying a source directory and a
`
`target directory for distribution of the application program. And, the TME
`
`Cookbook discloses the structure for performing this function is a server
`
`programmed with TME 10 Software Distribution 3.1 software to provide the
`
`following input screen that allows the user to enter: 1) a source directory path
`
`indicating the directory path on the server of the application program to be
`
`distributed; and 2) a target directory path indicating a directory path on a receiving
`
`managed node, which will be used for software package delivery at each of the
`
`selected target on-demand servers receiving distribution of the custom file package.
`
`Namely, the TME 10 Software Distribution 3.1 allows users to create file packages
`
`through which they specify source and target directories for distribution of an
`
`application program. EX1002, TME Cookbook at p.236 (“In scenario 1, we
`
`distribute a program named HIJAAK. This is a program to capture screen images.
`
`If you want to install a small program, like HIJAAK, you must transfer some files,
`
`create a directory and an icon. We show the step-by-step procedure on how you
`
`can do this with TME 10 Software Distribution 3.1 (Courier 3.1).”).
`
`
`
` 19
`
`
`
`With respect to specifying a source directory (structural step 1), TME
`
`Cookbook discloses that during the process of building a custom file package, an
`
`administrator uses the File Package Properties input screen to specify the source
`
`directory path that provides the directory path of the application program to be
`
`distributed.
`
`“Now we build the file package for our Scenario 1.
`
`1. Double-click on the Scenario 1 profile icon and the File Package
`Properties window (Figure 368) appears. Next, we specify the source host
`and the files we want to distribute.
`
`…
`
`2. To select the source host, click on the Source Host... button in the Source
`Host field.
`
`Figure 368. File Package Properties 1 []
`
`The Select Source Host window (Figure 369) appears.
`
`In the Hosts list box, we could select either TMR server foxtrot or managed
`node romeo, but the program, HIJAAK, that we want to distribute, is on host
`romeo.
`
`3. Select romeo in the Hosts list box.
`
`4. To complete the selection, click on the Select & Close button.
`
`Figure 369. Select Source Host []
`
`5. Click on the Directories & Files button in the File Package Properties
`window (Figure 368) and the Select Directory & Files window (Figure 370)
`appears.
`
`
`
` 20
`
`
`
`6. Select the path in the Directories list where the files that we want to
`distribute are located. The correct directory path name must be in the Path
`Name field. You will see the files in the Files list box. …
`
`8. Click on the Select & Close button.
`
`Figure 370. Select Directory & Files []
`
`The File Package Properties window (Figure 371) appears. You will see, in
`the Source Directories & Files list box, the selected directories and files.
`
`Figure 371. File Package Properties 2”
`
`EX1002, TME Cookbook at pp.239-240.
`
`Id. at p.690 (Figure 367).
`
`
`
` 21
`
`
`
`
`
`
`
`Id. at p. 693 (Figure 371); see also id. at pp. 691-693 (Figures 368-370).
`
`Although the source host of the above screenshot is the managed node
`
`ROMEO, TME Cookbook discloses that the source host can be set to the TMR
`
`server FOXTROT, such that file packages are distributed from the TMR server to
`
`another managed node.
`
`
`
` 22
`
`
`
`
`
`Id. at p.793 (Figure 441) also compare with EX1001 at Fig. 10 (“Source Path”
`
`input field specified as “d:\My_Applets”); see generally EX1002, TME Cookbook
`
`at pp. 265-268 (describing Figure 441).
`
`Additionally, TME Cookbook discloses that the TME 10 Software
`
`Distribution 3.1 application allows administrators to create a file package block
`
`
`
` 23
`
`
`
`that contains the underlying application program files so that they can be
`
`distributed from the FOXTROT TMR server to several managed nodes.
`
`“Now we want to create a file package block file from our File Package
`MSOffice_Files. The difference between a file package and a file package
`block is that the file package contains only pointers to the files which are
`going to be distributed. The file package block contains all files. Therefore,
`after you build the file package block, you can alter or delete the source files
`and nothing happens to the file package block. However, you cannot alter a
`file package block. You must create a new one. For this reason, a file
`package block is a safe way for a main administrator to prepare file package
`blocks, distribute them to the several managed nodes and be certain what
`was sent to the targets. The administrators of the managed nodes can now
`distribute the file package blocks to the PC managed nodes, but they are not
`able to change the content of the package.
`
`To create a file package block, open a command line interface (CLI) window.
`Type the following command:
`
`wcrtfpblock -a @MSOffice_Files \uwe\offpack @foxtrot
`
`where
Accessing this document will incur an additional charge of $.
After purchase, you can access this document again without charge.
Accept $ Charge
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.
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.
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
