throbber
a2) United States Patent
`US 10,289,607 B2
`do) Patent No.:
`Manzano
`*May 14, 2019
`(45) Date of Patent:
`
`US010289607B2
`
`(58) Field of Classification Search
`CPC ou... GO6F 17/30082; GO6F 17/30067; GO6F
`17/3023; GO6F 17/30194; GO6F
`17/30174;
`
`(Continued)
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`5,600,834 A
`5,675,802 A *
`
`2/1997 Howard
`10/1997 Allen wo GO6F 8/71
`707/999.202
`
`(Continued)
`
`Subject to any disclaimer, the term ofthis
`patent is extended or adjusted under 35
`U.S.C. 154(b) by 0 days.
`
`This patent is subject to a terminal dis-
`claimer.
`
`EP
`WO
`WO
`
`FOREIGN PATENT DOCUMENTS
`
`1130 511 AQ
`WO 98/56149 Al
`WO 2007/047302 A2
`
`9/2001
`12/1998
`4/2007
`
`
`
`OTHER PUBLICATIONS
`
`FolderShare—Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; < https://web.
`archive.org/web/20040804020435/http://www.foldershare.com:
`80/>; Aug. 4, 2004.
`
`(Continued)
`
`Primary Examiner — Srirama Channavajjala
`(74) Attorney, Agent, or Firm Pillsbury Winthrop Shaw
`Pittman LLP
`
`ABSTRACT
`(57)
`In certain embodiments, automatic modification-triggered
`transfer of a file among two or more computer systems
`associated with a user. In some embodiments, a copy of a
`first file may be received, via a first application at a first
`computer system, from a second application at a second
`computer system associated with a user. Thefirst file copy
`may be automatically received from the second application
`responsive to the user modifying a content ofthefirst file,
`wherethe first file copy is a version of thefirst file that is
`generated from the user modifying the content of the first
`file. Responsive to receiving the first file copy from the
`(Continued)
`
`(54) ARCHITECTURE FOR MANAGEMENT OF
`DIGITAL FILES ACROSS DISTRIBUTED
`NETWORK
`
`(71) Applicant: TOPIA TECHNOLOGY,INC..,
`Tacoma, WA (US)
`
`(72)
`
`Inventor: Michael R. Manzano,Seattle, WA
`(US)
`
`(73) Assignee: TOPLA TECHNOLOGY, INC.,
`Tacoma, WA (US)
`
`(*)
`
`Notice:
`
`(21) Appl. No.: 16/017,348
`
`(22)
`
`Filed:
`
`Jun. 25, 2018
`
`(65)
`
`Prior Publication Data
`
`US 2018/0307698 Al
`
`Oct. 25, 2018
`
`Related U.S. Application Data
`
`(63)
`
`Continuation of application No. 14/860,289, filed on
`Sep. 21, 2015, now Pat. No. 10,067,942, which is a
`(Continued)
`
`(51)
`
`Int. Cl.
`GOOF 16/00
`GO6F 16/11
`
`US. Cl.
`
`(52)
`
`(2019.01)
`(2019.01)
`(Continued)
`
`CPC wie GO6F 16/122 (2019.01); G06F 15/16
`(2013.01); GO6F’ 16/00 (2019.01); G06F
`16/128 (2019.01);
`
`(Continued)
`
`STORAGE
`270
`
`
`
`SERVER
`DATABASE
`COMPUTER SYSTEM
`
`240
`230
`260
`
`
`
`
`
`
`
`
`
`320
`
`
`
`
`
`
`
`
`
`\
`370
`
`
`370
`370
`
`
`
`a
`
`
`315
`
`
`
`
`
`
`
`
`
`
`
`USERDEVICE
`219
`
`
`
`
`
`USER DEVICE,
`230
`
`
`
`
`

`STORAGE
`
`
`
`
`
`
`USER DEVICE
`USER DEVICE
`280
`20
`
`
`
`
`
`
`
`
`DISPLAY
`
`250
`
`
`
`
`
`
`
`
`DISPLAY
`
`220
`
`
`
`
`
`J200
`
`370,
`
`
`
`
`
`
`
`
`
`Box & Dropbox Exhibit 1003
`Page 1
`
`Box & Dropbox Exhibit 1003
`Page 1
`
`

`

`US 10,289,607 B2
`Page 2
`
`second computer system, the first file copy may be auto-
`matically transferred via the first application to a third
`computer system associated with the user to replace an older
`version ofthefirst file stored on the third computer system.
`
`21 Claims, 3 Drawing Sheets
`
`Related U.S. Application Data
`
`continuation of application No. 12/267,852, filed on
`Nov. 10, 2008, now Pat. No. 9,143,561.
`
`(60) Provisional application No. 60/986,896, filed on Nov.
`9, 2007.
`
`(51)
`
`(2006.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2006.01)
`
`Int. Cl.
`GO6F 15/16
`GO6F 16/13
`GO6F 16/14
`GO6F 16/176
`GO6F 16/178
`HOAL 29/08
`(52) U.S. CL.
`CPC vices GO6F 16/13 (2019.01); GO6F 16/14
`(2019.01); GO6F 16/176 (2019.01); G06F
`16/178 (2019.01); HO4E 67/1095 (2013.01)
`(58) Field of Classification Search
`CPC .. GO6F 17/30362; GO6F 16/122; GO6F 16/10;
`GOG6F 16/16; GO6F 16/13-14; GO6F
`16/128; GO6F 16/176; GO6F 16/178
`See application file for complete search history.
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`5,806,078 A
`5,909,581 A
`5,920,867 A *
`6,026,414 A
`6,154,817 A
`6,260,069 B
`6,449,624 B
`6,463,463 B
`6,504,994 B2
`6,505,200 B
`6,526,418 BL*
`
`6,606,646 B2
`6,611,849 B
`6,671,700 B
`6,708,221 B
`6,757,696 B2
`6,757,893 BL*
`
`6,760,759 B
`6,810,405 B
`6,829,622 B?2
`6,874,037 B
`6,931,454 B2
`6,990,522 B2
`7,024,428 B
`7,054,594 B?
`7,065,658 B
`7,089,307 B2
`7,136,934 B2
`7,155,488 B
`7,224,973 B2
`7,243,163 B
`7,260,646 B
`7,269,433 B2
`
`
`
`9/1998 Hug
`6/1999 Park
`7/1999 Van Huben....... GO6F 17/30362
`2/2000 Anglin
`11/2000 Mohanetal.
`7/2001 Anglin
`9/2002 Hammack etal.
`10/2002 Godfreyet al.
`1/2003 Kawamuraetal.
`1/2003 Imsetal.
`2/2003 Midgley ........... GO6F 11/1451
`707/640
`
`8/2003 Feigenbaum
`8/2003 Raff ct al.
`12/2003 Creemeret al.
`3/2004 Mendezetal.
`6/2004 Multer et al.
`
`6/2004 Haikin wn. GO6F 8/71
`717/170
`
`7/2004 Chan
`10/2004 Larueet al.
`12/2004 Beyda
`3/2005 Abram etal.
`8/2005 Deshpandeet al.
`1/2006 Wu
`4/2006 Huanget al.
`5/2006 Bloch et al.
`6/2006 Baraban etal.
`8/2006 Zintel et al.
`11/2006 Carteretal.
`12/2006 Lunsford et al.
`5/2007 Tsutazawaetal.
`7/2007 Friend et al.
`8/2007 Stefanik et al.
`9/2007 Vargas et al.
`
`
`
`Peck etal.
`Wang ccc GO06F 9/543
`707/999 01
`Cameronet al.
`Lee
`Ilong etal.
`Skygebjer
`Yach etal.
`Kurlanderetal.
`Koskimieset al.
`Rabbers et al.
`Zondervan et al.
`Chenet al.
`Onyonet al.
`Watt
`Saunders
`Kim
`Schauseretal.
`Quinlan et al.
`Freedman
`Mikesell et al.
`Tu etal.
`Klobaetal.
`Bloom etal.
`Srinivasan et al.
`Chipchase
`Roskind et al.
`Ozzie etal.
`Schleifer etal.
`Moseleretal.
`Nelson wo... HO4L 67/1095
`707/602
`Manzano.......... GO6T' 17/30174
`Manzano.......... GO6F 17/30082
`Rodgersetal.
`McCurdy
`Reynolds 0... GO6F 21/64
`McBride et al.
`Fletcher vee GO6F 8/61
`Lord.
`Muttik et al.
`Peck etal.
`Costello
`Pesola
`Estrada
`Marsh 0... eee GO6F16/48
`725/14
`
`tees GO06F 16/10
`
`McDonough et al.
`Therrien et al.
`Rudoff
`Reynolds
`Okachi
`Edelstein et al.
`
`Kiessig ....
`Ponceetal.
`Glatt et al.
`
`Cannon....
`... GO6F 11/1451
`
`Hilbert... HO0A4T, 51/22
`Ronkainen etal.
`Pyhalammi............. GOGF 16/44
`Shaath et al.
`Suderman
`Wolfish
`Phillips
`Hughes oe GOGF 16/10
`Holm
`Godlin
`Montulli et al.
`O'Neil
`Reinsch
`VASA eee HO4M 1/72522
`709/204
`
`Stakutis
`Sumneretal.
`Mohanty ...0..0.... GO6F 11/1451
`709/223
`
`Kamada
`Sengupta et al.
`Li
`
`08
`
`10/2
`1/2
`
`07
`08
`
`08
`3/2
`08
`7/2
`08
`8/2
`08
`8/2
`08
`11/2
`08
`(2/2
`09
`1/2
`09
`4/2
`09
`8/2
`09
`9/2
`09
`9/2
`09
`11/2
`09
`12/2
`10
`2/2
`10
`3/2
`10
`72
`10
`7/2
`10
`8/2
`2/2011
`T2011
`8/2011
`12
`2/2
`12
`8/2
`12
`11/2
`13
`2/2
`2/2
`13
`13
`10/2
`13
`11/2
`
`15
`18
`02
`02
`02
`02
`02
`03
`03
`03
`03
`03
`03
`03
`
`04
`04
`04
`04
`04
`04
`05
`05
`05
`10)
`05
`05
`06
`06
`06
`06
`06
`06
`06
`06
`06
`07
`07
`07
`
`07
`07
`07
`
`07
`07
`
`9/2
`9/2
`2/2
`3/2
`5/2
`7/2
`10/2
`2/2
`2/2
`2/2
`4/2
`7/2
`7/2
`12/2
`
`3/2
`5/2
`6/2
`7/2
`8/2
`9/2
`2/2
`4/2
`5/2!
`7/2
`9/2
`10/2
`1/2
`1/2
`3/2
`4/2
`6/2
`6/2
`6/2
`7/2
`8/2
`1/2
`1/2
`1/2
`
`2/2
`5/2
`8/2
`
`8/2
`10/2
`1/2
`
`
`
`B2
`Bl *
`
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`Bl
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`Bl
`Bl
`B2
`B2
`B2
`Bl
`B2
`B2
`B2
`B1*
`
`B2*
`B2 *
`Al
`Al
`Al*
`Al
`Al*
`Al
`Al
`Al
`Al
`Al
`Al
`Al*
`
`Al
`Al
`Al
`Al
`Al
`Al
`Al*
`Al
`Al
`Al*
`*
`Al
`Al
`Al*
`Al
`Al
`Al
`Al
`Al*
`Al
`Al
`Al
`Al
`Al
`Al*
`
`Al
`Al
`Al*
`
`7,290,244
`7,325,038
`
`7,340,534
`7,398,327
`7,415,588
`7A15,615
`7,A57,631
`7 AGT 353
`7,483,925
`7,526,575
`7,574,711
`7,584,186
`7,587 446
`7,613,773
`7,639,116
`7,657,271
`7,680,885
`7,752,166
`7,761,414
`7,788,303
`7,895,334
`7,987,420
`8,009,966
`8,112,549
`8,244,288
`8,321,534
`8,370,423
`8,386,558
`8,565,729
`8,595,182
`
`9,143,561
`10,067,942
`2002/0026478
`2002/0035697
`2002/0055942
`2002/0087588
`2002/0143795
`2003/0028514
`2003/0028542
`2003/0038842
`2003/0078946
`2003/0125057
`2003/0135565
`2003/0233241
`
`2004/0049345
`2004/0093361
`2004/0107225
`2004/0133629
`2004/0158817
`2004/0172424
`2005/0027757
`2005/0091316
`2005/0097225
`2005/0165722
`2005/0192966
`2005/0220080
`2006/0004698
`2006/00 10150
`2006/0058907
`2006/0074985
`2006/0129627
`2006/0136446
`2006/0143129
`2006/0168118
`2006/0189348
`2007/00 14314
`2007/00 16629
`2007/0022158
`
`2007/0027936
`2007/01009 13
`2007/0180084
`
`2007/0191057
`2007/0238440
`2008/0005114
`
`Al
`Al
`Al
`
`Box & Dropbox Exhibit 1003
`Page 2
`
`Box & Dropbox Exhibit 1003
`Page 2
`
`

`

`US 10,289,607 B2
`Page 3
`
`(56)
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`1/2008 Adams
`4/2008 Heller et al.
`7/2008 Robbin et al.
`11/2008 Silfverberg
`1/2009 Nakayama
`2/2009 Ganesh... GO6F 9/4416
`713/2
`
`FolderShare Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/200406 13 16 1906/http://www.toldershare.com:
`80/>; Jun. 13, 2004.
`FolderShare—Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/20040629075057/http://www.foldershare.com:
`80/>; Jun. 29, 2004.
`FolderShare—Secure Remote Access VPN Solution; Your Smart
`Tile Transfer & Real-time Tile Mirroring Solution; <https://web.
`archive.org/web/200403 1623515 | /http://foldershare.com:80/>; Mar.
`16, 2004.
`FoldcrShare—Sccure Remote Access VPN Solution; Your Smart
`File Transfer & Real-time File Mirroring Solution; <https://web.
`archive.org/web/20040325034239/http://www.foldershare.com:
`80/>; Mar. 25, 2004.
`FolderShare—Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/200405 122 11417/http://www.foldershare.com:
`80/>; May 12, 2004.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`20030531 180252/http:/Avww.foldershare.com:80/>: May 31, 2003.
`FolderShare—Secure Remote Access VPN Solution; Need your
`FolderShare,; Your Files Anywhere; <https://web.archive.org/web/
`files on more than one computer?: <https://web.archive.org/web/
`20030808 183932/http://www.foldershare.com:80/>; Aug. 8, 2003.
`2004110403 1510/http://www.foldershare.com:80/>; Nov. 4, 2004.
`FolderShare—Secure Remote Access VPN Solution; Need your
`FolderShare—Secure Remote Access VPN Solution; Need your
`files on more than one computer?; <https://web.archive.org/web/
`files on more than one computer?; <https://web.archive.org/web/
`20041117092357/http:/www.foldershare.com:80/>; Nov. 17, 2004.
`200408 140 15727/http://www.toldershare.com:80/>; Aug. 14, 2004.
`FolderShare—Secure Remote Access VPN Solution; Need your
`FolderShare—Secure Remote Access VPN Solution; Need your
`files on more than one computer?; <https://web.archive.org/web/
`files on more than one computer’; <https://web.archive.org/web/
`20041123085254/http://www.foldershare.com:80/>; Nov. 23, 2004.
`20040820052 105/http://www.toldershare.com:80/>; Aug. 20, 2004.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`FolderShare—Secure Remote Access VPN Solution; Need your
`2003 1128 [43634/http://foldershare.com:80/>; Nov. 28, 2003.
`files on more than one computer?; <https://web.archive.org/web/
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`
`2004 12|1020957/http://foldershare.com:80/>; Dec. [1, 2004.
`2003100107163 1/http://foldershare.com:80/>; Oct. 1, 2003.
`FolderShare—Secure Remote Access VPN Solution; Need your
`FolderShare—Secure Remote Access VPN Solution; Need your
`files on more than one computer?; <https://web.archive.org/web/
`files on more than one computer?; <https://web.archive.org/web/
`2004 1217041726/http://foldershare.com:80/>; Dec. 17, 2004.
`20041012083 127/http://www.foldershare.com:80/>; Oct. 12, 2004.
`FolderShare; Your Smart File Transfer Solution; <https://web.archive.
`FolderShare—Secure Remote Access VPN Solution; Need your
`org/web/2003 1220151508/http://www.foldershare.com:80/>; Dec. 20,
`2003.
`files on more than one compuler?; <hUps://web.archive.org/web/
`20041029085820/hUp://www. foldershare.com:80/>;, Ocl. 29, 2004.
`FolderShare—Secure Remote Access VPN Solution; Need your
`FolderShare—Secure Remole Access VPN Solution; Need your
`files on more than one computer?; <https://web.archive.org/web/
`files on more than one compuler?; <hUps://web.archive.org/web/
`200412302 11050/http://www.foldershare.com:80/>; Dec. 30, 2004.
`FolderShare—Secure Remote Access VPN Solution; Document
`2004090 1034646/http://www.foldershare.com:80/>; Sep. 1, 2004.
`FolderShare—Secure Remote Access VPN Solution; Need your
`Management & Real-time File Mirroring Solution; <htips://web.
`files on more than one computer?; <https://web.archive.org/web/
`archive.org/web/20040701113739/http://foldershare.com:80/>; Jul.
`1, 2004.
`20040909075254/http://www.foldershare.com:80/>; Sep. 9, 2004.
`FolderShare—Secure Remote Access VPN Solution; Document
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`2003092005 1943/http://www.foldershare.com:80/>; Sep. 20, 2003.
`Management & Real-time Tile Mirroring Solution; <https://web.
`FolderShare—Secure Remote Access VPN Solution; Need your
`archive.org/web/200407 11062548/http://www.foldershare.com:
`80/>; Jul. 11, 2004.
`files on more than one computer?; <https://web.archive.org/web/
`20040924032 146/http://www.foldershare.com:80/>; Sep. 24, 2004.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`Marshall, M., “The Y Combinator List,” Venture Beat, Aug. 2007,
`20030722054342/http://foldersharc.corn:80/>; Jul. 22, 2003.
`Retrieved from the Internet: URL: <https://venturebeat.com/2007/
`FolderShare—Sccure Remote Acccss VPN Solution; Document
`08/16/the-y-combinator-list/>, 4 pages.
`Management & Real-time File Mirroring Solution; <https://Aweb.
`Jarvis, A., “Dropbox pitch deck to raise seed capital investment, ”
`archive.org/web/20040730030655/http://www.foldershare.com:
`80/>; Jul. 30, 2004.
`Medium, Mar. 2018, Retrieved from the Internet: URL: <https://
`FolderShare
`Secure Remote Access VPN Solution; Document
`medium.com/@adjblog/dropbox-pitch-deck-to-raise-seed-capital-
`investment-6a6cd6517e56>, 12 pages.
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/20040603205113/http://www.foldershare.com:
`80/>; Jun. 3, 2004.
`
`2008/0005280 Al
`20080086494 Al
`2008/0168526 Al
`2008/0288578 Al
`2009/0013009 Al
`2009/0037718 Al*
`
`2009/0063711 Al
`2009/0282050 Al
`2012/0192064 Al*
`
`2013/0226871 Al
`2013/0226872 Al*
`
`2014/0053227 Al*
`
`3/2009 Finkelstein
`11/2009 Thomasetal.
`7/2012 Antebi oe GO6F 17/2288
`715/255
`
`8/2013 Sarnowski
`8/2013 Barefoot
`........... GO6F 17/30575
`707/638
`
`2/2014 Ruppin oe GO6F 21/10
`726/1
`
`OTHER PUBLICATIONS
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`* cited by examiner
`
`Box & Dropbox Exhibit 1003
`Page 3
`
`Box & Dropbox Exhibit 1003
`Page 3
`
`

`

`U.S. Patent
`
`May 14, 2019
`
`Sheet 1 of 3
`
`US 10,289,607 B2
`
`
`
`
`—_—3SUOMLIN||LONIIONNON||ANOW3WAMOS“IOANON
`ae‘naga||he|NOESaESa.mafhaF_|Odb“||pees\|SOWSUSINE|3Vs43.N|JowMaIN)
`||30WHBINI
`
`YHOMLSNWaH¥TyooT4SHa]|STOVAOWId||SeVAOINGUNON
`
`JLOWSY,;=aaGPLPre
`
`TWUSHdIIdOIAWaiSkSAdLAGiUNONO
`
`
`|OWIUAIN|oe
`
`SWYHOOHd§ WSILSAS9|WYHSOHd|WWHDOUGWHO)NOLLWONddY=ONILWESdO
`
`
`SHONvivasnndon
`
`
`
`SOWAHSLN
`
`
`
`I
`
`oleWLSAS
`LZb>y
`
`BNISSIOOUd
`
`
`
`
`__AMOWGINWAISAS
`LetWOU!
`
`
`sangon|WYHSOUdHSHLO
`
`NOLOddl
`
`SIWHOOHd
`
`
`
`LOI
`
`
`
`
`
`
`
`
`
`
`
`
`
`Box & Dropbox Exhibit 1003
`Page 4
`
`Box & Dropbox Exhibit 1003
`Page 4
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`May14, 2019
`
`Sheet 2 of 3
`
`US 10,289,607 B2
`
` 2
`
`6
`
`
`
`Lu
`
`DISPLAY
`
`250
`
`COMPUTERSYSTEM
`
`
` USERDEVICE
`
`FIG.2 STORAGE 2/0
` SERVER
`NETWORK
`
`
`DATABASE
`
`a3
`
`Q>L
`
`uQo
`
`r
`rm
`
`
`
`2N
`
`4
`I
`
`9
`
`DISPLAY
`
`200
`
`Box & Dropbox Exhibit 1003
`Page 5
`
`Box & Dropbox Exhibit 1003
`Page 5
`
`

`

`U.S. Patent
`
`May14, 2019
`
`Sheet 3 of 3
`
`US 10,289,607 B2
`
`Oo
`Mo
`o
`
`oO
`oO)
`e)]
`
`uu
`Qo
`fi
`agN
`oi
`5
`
`
`

`—_

`
`R

`5
`e
`
`
`
`
`DEVICE 210
`
`
`
`
`STORAGE
`
`FIG.3
`
`USER
`
`Box & Dropbox Exhibit 1003
`Page 6
`
`Box & Dropbox Exhibit 1003
`Page 6
`
`

`

`US 10,289,607 B2
`
`1
`ARCHITECTURE FOR MANAGEMENT OF
`DIGITAL FILES ACROSS DISTRIBUTED
`NETWORK
`
`
`CROSS-REFERENCE TO RELAT!
`APPLICATIONS
`
` eslD
`
`This application is a continuation of U.S. patent applica-
`tion Ser. No. 14/860,289, filed Sep. 21, 2015, which is a
`continuation of U.S. patent application Ser. No. 12/267,852,
`filed Nov. 10, 2008, which claims priority to U.S. Provi-
`sional Application No. 60/986,896 entitled “ARCHITEC-
`TURE TOR MANAGEMENT OF DIGITAL TILES
`
`ACROSS DISTRIBUTED NETWORK”and filed Nov. 9,
`2007,
`the contents of which are hereby incorporated by
`reference in their entirety.
`
`FIELD OF THE INVENTION
`
`2
`offspring of systems used when graphical customer inter-
`faces were nonexistent. Modern file system customer inter-
`faces, such as Windows® Explorer and Mac OS X’s Finder
`are just nowstarting to provide experiences that are more in
`line to a customer’s workflow. Whereas, before, these inter-
`faces were concerned with representing files with abstracted
`icons, the file’s actual contents are becoming, paramount in
`how files are organized and presented.
`Problems still exist with how these newer customer
`interfaces are implemented. They are not completely inte-
`grated with applications, suffer from performance problems,
`and do not generally work well outside of a device’s local
`file system.
`There are several solutions to this problem that are in one
`way or another inadequate to the task:
`Remote Desktop software allows a customer to remotely
`“see” his desktop. Remote desktop software screen-scrapes
`a remote machine’s screen (a “server’”) and displays it on a
`screen local to the customer (a “client’”). Remote desktop
`gives a customeraccess to not only hisfiles, but also to his
`applications. However, this approach requires that the host
`machine be turned on and connected to the internet at all
`times. Consequently, this approach would not be appropriate
`tor mobile hosts such as laptops. Remote desktop does not
`use the resources of a local machine. For full accessibility,
`the customer would haveto keep all files and application on
`the host machine as any files stored on a client are not
`guaranteed to be accessible.
`Distributed File Systems, like remote desktop software,
`application, second only to email, on the Internet. Further,
`place data on an always-connected host machine. Unlike
`customers are increasingly using more than one computing
`remote desktop software, the host machine is not one on
`device; a customer mayhave a desktop computer at home,
`which the customer performs computing tasks. The host
`one at work, and a constantly connected “smart phone”. Due
`machine is used as a storage mechanism, and any compu-
`to the confluence of these two trends, file management
`tation performed on that machine serves to supportsits use
`across these devices has become a problem.
`as such. Distributed file systems generally provide the right
`Although modern devices are easily connected, they do
`functionality for customers to share files between their
`not provide the customer a seamless environment; the cus-
`devices. However, distributed file systems are usually
`tomer must manually handle many aspects of that connec-
`deployed as a shared resource; that is, other customers have
`tion. With regards to file management, customers must
`access to it. Because of this sharing, a customer’s files may
`manually move files between their devices using some
`be buried deepin a filing structure, and it may not always be
`protocol like email, ftp, or by posting them on the Web.
`immediately evident to customers what kind of access they
`These practices lead to problems that include:
`have to a particular file. Further, to use a distributed file
`The proliferation of redundant file copies. This prolifera-
`system, the customer must always be connectedtoit. Files
`tion creates a confusing environment where the cus-
`tomeris unclear where the “official” or newest version
`stored on a distributed file system are generally inaccessible
`of a file exists.
`if the customer’s machine is not connected to it, unless the
`customer has copied or movedthe files to his machine’s
`The creation of an error-prone environment. Some docu-
`local hard drive. However, doing so immediately creates the
`ments, such as those associated with word processing
`problem of having two filing systems for the samefile,
`and desktop publishing, externally reference otherfiles.
`creating a mental burden on the customer.
`Copying, such a document can break these references
`
`causing errors that the customer has to handle manu- Additionally, accessingafile located on a distributed file
`ally. An example of such a document is a desktop
`system tends to be slower than accessing files on the local
`publishing document that contains a reference to an
`hard drive. Modem applications are usually written to
`image. If that imagefile is not transferred along with
`assumethatthe files they access are located locally, and thus
`the desktop publishing file, the image will appear as a
`are not optimized to access remotefiles. When these appli-
`broken link.
`cations are used with remotefiles, they can lose performance
`by an order of magnitude. This problem can be fixed by
`automatically caching often-used files on the local
`file
`system, and only synchronizing them when they have been
`changed. However, this separate synchronization step intro-
`duces another problem: because the synchronization process
`can be lengthy, the customeris neverentirely sure ifthe file
`he is remotely accessing is the latest version of the file,
`versus an earlier one that has been marked to be updated.
`Further, the directory may not reflect the existence ofthe file
`at all until synchronization finishes.
`FTPis similar to a distributed file system with regards to
`files being hosted on a remote server. [lowever I'TP gener-
`
`Unnecessary complexity. Because devices tend to have
`their own filing system, customers must manage a
`different filing model on each of his devices. For
`example, instead of having a single “Movies”folder, he
`may have to deal with many “Movies” folders, which
`may be in different locations on each of his devices.
`Each device may also have its own security model,
`further complicating the matter.
`That a customer has to manually movefiles around to
`ensure their accessibility on his devices is unnecessary, and
`is an indicator of a lack of customer-focused design in
`modern file systems. Vile systems in use today are direct
`
`This inventionrelates generally to computer-implemented
`processes and, more specifically, to sharing of electronic
`files among computer systems.
`
`
`
`BACKGROUND OF THE INVENTION
`
`Users of modern computing systems are increasingly
`finding themselves in constantly-connected, high-speed net-
`worked environments. The Web continues to be a killer
`
`20
`
`25
`
`40
`
`45
`
`60
`
`65
`
`Box & Dropbox Exhibit 1003
`Page 7
`
`Box & Dropbox Exhibit 1003
`Page 7
`
`

`

`US 10,289,607 B2
`
`
`
`3
`ally does manifest as a “disk drive” on the customer’s
`desktop; the customer must use special FTP client software
`to access an FTP server. It shares the same problem as
`distributed file systems, with the additional problem of weak
`integration with applications. Applications can generally
`write and read files directly to and from a distributed file
`system. This is not the case with FTP, as the customer has
`to manually use the client software to perform these opera-
`tions as a separate task.
`[mail was originally invented for messaging. [rom the
`beginning, the model it employs to makefiles accessible
`remotely is necessarily inefficient. Email’s model for mak-
`ing files accessible is in the form of an email “attachment”
`Attachments are so named because they piggy-back on a
`message sent from one customerto another. A customer can
`makea file remotely available using email by attaching the
`file to an email and sending it to himself. He can then
`retrieve the file from a remote location by accessing the
`message on the email server. Email used in this way is even
`worse than I'TP as the process is even more manual: a
`customer mustfind the message containingthefile before he
`can even access it. Further,
`the location in which the
`attachmentlives is read only. If the customer, for example,
`were to open the file, change it, then save il back out, the
`results would be ambiguous to the user because the email
`application, not the user, specified its location. Usually, the
`saved file would end up buried in an email file cache in an
`undisclosed. area of the file system.
`Flash Drives and External Disk Drives, although seem-
`ingly the most “primitive” way to ensure file availability,
`avoid all the problemsrelated to network latency. However,
`these devices must be physically connected to the computer
`on which the files will be accessed. These restrictions
`preclude the customer from employing several ellective
`work-flows including: using more than one computer to
`complete a single task(the files can only be accessed on one
`computer) and setting up an automated backup (the com-
`puter running the backup can’t guarantee that the storage
`device will be connected come backup time). Further, to
`ensure full availability of the files, the customer must carry
`the device with them at all
`times, and must follow the
`associated protocols for mounting and dismounting the
`device.
`Other problems with the prior art not described above can
`also be overcomeusing the teachings of embodimentsof the
`present invention, as would be readily apparent to one of
`ordinary skill in the art after reading this disclosure.
`
`SUMMARYOF THE INVENTION
`
`In certain embodiments, automatic modification-triggered
`transfer of a file among two or more computer systems
`associated with a user. In some embodiments, a copy ofa
`first file may be received, via a first application at a first
`computer system, from a second application at a second
`computer system associated with a user. Thefirst file copy
`may be automatically received from the second application
`responsive to the user modifying a content ofthefirst file,
`wherethe first file copy is a version ofthefirst file that is
`generated from the user modifying the content of the first
`file. Responsive to receiving the first file copy from the
`second computer system, the first file copy may be auto-
`matically transferred via the first application to a third
`computer system associated with the user to replace an older
`version of thefirst file stored on the third computer system.
`
`4
`BRIEF DESCRIPTION OF THE DRAWING
`
`Preferred and alternative embodiments of the present
`invention are described in detail below with reference to the
`following drawings.
`FIG. 1 is a schematic view of an exemplary operating,
`environment in which an embodiment of the invention can
`
`be implemented;
`FIG. 2 is a functional block diagram of an exemplary
`operaling environment
`in which an embodiment of the
`invention can be implemented; and
`FIG. 3 is a functional block diagram illustrating file
`sharing and/or synchronization according to an embodiment
`of the invention.
`
`DETAILED DESCRIPTION OF THE
`PREFERRED EMBODIMENT
`
`20
`
`25
`
`40
`
`45
`
`60
`
`65
`
`An embodiment of the invention leverages remote pro-
`gramming concepts by utilizing processes called mobile
`agents (sometimes referred to as mobile objects or agent
`objects). Generally speaking,
`these concepts provide the
`ability for an object (the mobile agent object) existing on a
`first (“host”) computer system to transplant itself'to a second
`(“remote host”) computer system while preserving its cur-
`rent execution state. The operation of a mobile agent object
`is described briefly below.
`The instructions of the mobile agent object, its preserved
`execution state, and other objects owned by the mobile agent
`object are packaged, or “encoded,” to generate a string of
`data that is configured so that the string of data can be
`transported by all standard means of communication over a
`computer network. Oncetransported to the remote hast, the
`string ofdata is decoded to generate a computerprocess,still
`called the mobile agent object, within the remote host
`system. The decoded mobile agent object includes those
`objects encoded as described above and remains in ils
`preserved execution state. The remote host computer system
`resumes execution of the mobile agent object which is now
`operating in the remote host environment.
`While nowoperating in the new environment, the instruc-
`tions of the mobile agent object are executed by the remote
`host to perform operations of any complexity,
`including
`defining, creating, and manipulating data objects and inter-
`acting with other remote host computer objects.
`File transfer and/or synchronization, according to an
`embodiment, may be accomplished using someorall of the
`concepts described in commonly owned U.S. patent appli-
`cation Ser. No. 11/739,083, entitled “Electronic File Shar-
`ing,” the entirety of which is incorporated by reference as if
`fully set forth herein.
`FIG. 1 illustrates an example of a suitable computing
`system environment 100 in which one or more embodiments
`of the invention may be implemented. The computing sys-
`tem environment 100 is only one example ofa suitable
`computing environment and is not intended to suggest any
`limitation as to the scope of use or functionality of the
`invention. Neither should the computing environment 100
`be interpreted as having any dependency or requirement
`relating to any one or combination of componentsillustrated
`in the exemplary operating environment 100.
`Embodiments of the invention are operational with
`numerousother general purpose or special purpose compul-
`ing system environments or configurations. Examples of
`well known computing systems, environments, and/or con-
`figurations that may be suitable for use with the invention
`include, but are not limited to, personal computers, server
`
`Box & Dropbox Exhibit 1003
`Page 8
`
`Box & Dropbox Exhibit 1003
`Page 8
`
`

`

`US 10,289,607 B2
`
`5
`computers, hand-held or laptop devices, multiprocessor sys-
`tems, microprocessor-based systems, set top boxes, pro-
`grammable consumerelectronics, network PCs, minicom-
`puters, mainframe
`computers,
`distributed
`computing
`environments that include any of the above systems or
`devices, and thelike.
`Embodiments of the invention may be described in the
`general context of computer-executable instructions, such as
`program modules, being executed by a computer and/or by
`computer-readable media on which such instructions or
`modules can be stored. Generally, program modules include
`routines, programs, objects, components, data structures,
`etc. that perform particular tasks or implement particular
`abstract data types. The invention may also be practiced in
`distributed computing environments where tasks are per-
`formed by remote processing devices that are linked through
`a communications network.
`In a distributed computing
`environment, program modules may belocated in both local
`and remote computer storage media including memory
`storage devices.
`With reference to FIG. 1, an exemplary system for imple-
`menting the invention includes a general purpose computing
`device in the form of a computer 110. Components of
`computer 110 may include, but are not limited to, a pro-
`cessing unit 120, a system memory 130, and a system bus
`121 that couples various system components including the
`system memory to the processing unit 120. The system bus
`121 may be any ofseveral types of bus structures including
`a memorybus or memory controller, a peripheral bus, and a
`local bus using anyof a variety of bus architectures. By way
`of example, and not limitation, such architectures include
`Industry Standard Architecture (ISA) bus, Micro Channel
`Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video
`Electronics Standards Association (VESA) local bus, and
`Peripheral ComponentInterconnect (PCI) bus also knownas
`Mezzanine bus.
`Computer 110 typically includes a variety of computer
`readable media. Computer readable media can be anyavail-
`able media that can be accessed by computer 110 and
`includes both volatile and nonvolatile media, removable and
`non-removable media. By way of example, and not limita-
`tion, computer readable media may comprise computer
`storage media and communication media. Computer storage
`media includes both volatile and nonvolatile, removable and
`non-removable media implemented in any method or tech-
`nology for storage of information such as computer readable
`instructions, data structures, program modulesor other data.
`Computer storage media includes, but is not limited to,
`RAM, ROM, EEPROM, flash memory or other memory
`technology, CD-ROM,digital versatile disks (DVD)or other
`optical disk storage, magnetic cassettes, magnetic tape,
`magnetic disk storage or other magnetic storage devices, or
`any other medium which can be used to store the desired
`information and which can accessed by computer 110.
`Communication media typically embodies computer read-
`able instructions, data structures, program modules or other
`data in a modulated data signal such as a carrier wave or
`other transport mechanism and includes any information
`delivery media. The term “modulated data signal” meansa
`signal that has one or more of its characteristics set or
`changed in such a manner as to encode information in the
`signal. By way of example, and not limitation, communi-
`cation media includes wired media such as a wired network
`or direct-wired connection, and wireless media such as
`acoustic, RF, infrared and other wireless media. Combina-
`tions of the any of the above should also be included within
`the scope of computer readable media.
`
`ra 0
`
`5
`
`20
`
`25
`
`40
`
`wi 2
`
`wi on
`
`60
`
`6
`Th

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