`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`I 1111111111111111 1111111111 11111 11111 111111111111111 IIIII IIIIII IIII IIII IIII
`
`USO 11003622B2
`
`(IO) Patent No.: US 11,003,622 B2
`
`c12) United States Patent
`(45)Date of Patent:*May 11, 2021
`
`
`Manzano
`
`(54)ARCHITECTURE FOR MANAGEMENT OF
`
`DIGITAL FILES ACROSS DISTRIBUTED
`NETWORK
`
`(71)Applicant: TOPIA TECHNOLOGY, INC.,
`
`
`Tacoma, WA (US)
`
`(56)
`
`
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`5,600,834 A 2/1997 Howard
`
`
`
`5,675,802 A 10/1997 Allen
`(Continued)
`
`
`
`(72)Inventor:
`(US)
`
`Michael R. Manzano, Seattle, WA
`
`FOREIGN PATENT DOCUMENTS
`
`(73)Assignee: TOPIA TECHNOLOGY, INC.,
`
`
`
`Tacoma, WA (US)
`
`EP
`WO
`WO
`
`1 130 511 A2
`9/2001
`12/1998
`
`WO 98/56149 Al
`4/2007
`
`WO 2007/047302 A2
`
`( *) Notice: Subject to any disclaimer, the term of this
`
`
`
`
`
`patent is extended or adjusted under 35
`
`
`U.S.C. 154(b) by O days.
`
`OTHER PUBLICATIONS
`
`FolderShare---Secure Remote Access VPN Solution; Document
`
`
`
`
`
`This patent is subject to a terminal dis­
`
`
`
`
`Management & Real-time File Mirroring Solution; < https://web.
`claimer.
`
`
`archive.org/web/20040804020435/http://www.foldershare.com :
`80/>; Aug. 4 , 2004.
`(Continued)
`
`Appl. No.: 16/361,641
`(21)
`
`
`
`(22) Filed: Mar. 22, 2019
`
`(65)
`
`
`
`Prior Publication Data
`
`
`
`US 2019/0220442 Al Jul. 18, 2019
`
`Primary Examiner - Srirama Channavajjala
`
`
`
`
`
`
`
`(74)Attorney, Agent, or Firm - Pillsbury Winthrop Shaw
`
`Pittman LLP
`
`
`
`
`
`Related U.S. Application Data
`
`ABSTRACT
`
`(57)
`Continuation of application No. 16/017,348, filed on
`
`
`
`(63)
`In certain embodiments, automatic modification-triggered
`
`
`
`
`Jun. 25, 2018, now Pat. No. 10,289,607, which is a
`
`
`transfer of a file among two or more computer systems
`(Continued)
`
`
`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. The first file copy
`
`
`may be automatically received from the second application
`
`
`
`responsive to the user modifying a content of the first file,
`(52)
`U.S. Cl.
`
`where the first file copy is a version of the first file that is
`CPC ............ G06F J{,1122 (2019.01); G06F 15116
`
`
`
`
`
`generated from the user modifying the content of the first
`
`
`(2013.01); G06F 16/00 (2019.01); G06F
`
`
`file. Responsive to receiving the first file copy from the
`J{,1]0 (2019.01);
`
`
`second computer system, the first file copy may be auto­
`(Continued)
`
`
`
`matically transferred via the first application to a third
`(58)
`
`Field of Classification Search
`
`
`
`computer system associated with the user to replace an older
`
`
`
`CPC ...... G06F 16/00; G06F 16/178; G06F 16/182;
`
`
`
`version of the first file stored on the third computer system.
`
`G06F 16/10; G06F 16/1873;
`(Continued)
`
`(51)
`Int. Cl.
`G06F 1(,100
`
`(2019.01)
`(2019.01)
`G06F J{,111
`(Continued)
`
`
`
`17 Claims, 3 Drawing Sheets
`
`370
`
`370
`
`2_:J_Q
`
`STORAGE
`
`llQ
`
`1 JS.F:R nFIJl(;F
`2.§.Q
`
`Box & Dropbox Exhibit 1006
`Page 1
`
`

`

`10
`04 04
`
`06
`06
`06
`06
`07
`07
`07
`07
`07
`
`07
`07
`08
`O08
`08
`08
`08
`08
`08
`09
`09
`09
`09
`09
`09
`09
`09
`10
`10
`10
`10
`10
`10
`10
`
`8/2
`11/2
`(2/2
`12/2
`1/2
`$/2'
`7/2
`8/2
`8/2
`
`9/2
`10/2
`1/2
`32
`
`28
`
`/2
`8/2
`11/2
`12/2
`12
`4/2
`5/2
`8/2
`9/2
`9/2
`11/2
`12/2
`2/2
`3/2
`32
`4/2
`
`21
`
`2
`8/2
`9/2
`2/2011
`2/2011
`72011
`8/2011
`9/2011
`12
`2/2
`12
`6/2
`12
`8/2
`12
`11/2
`2/2
`13
`13
`2/2
`13
`8/2
`13
`10/2
`13
`11/2
`10/2
`14
`IS
`9/2
`18
`9/2
`19
`5/2
`02
`2/2
`02
`3/2
`02
`5/2
`02
`7/2
`02
`10/2
`02
`12/2
`02
`12/2
`
`(60)
`
`(51)
`
`(52)
`
`(58)
`
`Related U.S. Application Data
`
`continuation of application No. 14/860,289, filed on
`Sep. 21, 2015, now Pat. No. 10,067,942, which is a
`continuation of application No. 12/267,852, filed on
`Nov. 10, 2008, now Pat. No. 9,143,561.
`
`Provisional application No. 60/986,896, filed on Nov.
`9, 2007.
`
`(2006.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2019.01)
`(2006.01)
`
`Int. Cl.
`GO6F 15/16
`GO06F 16/13
`GO6F 16/14
`GO6F 16/176
`GO6F 16/178
`GO6F 16/18
`GO6F 16/182
`GO6F 16/10
`HOAL 29/08
`U.S. CL
`CPC woe. GO6F 16/128 (2019.01): GO6F 16/13
`(2019.01); GO6F 16/14 (2019.01); GO6F
`16/176 (2019.01); G06F 16/7178 (2019.01);
`GO6F 16/182 (2019.01); GO6F 16/1873
`(2019.01); HO4L 67/1095 (2013.01)
`Field of Classification Search
`CPC vice GO6F 16/1756; GO6F 16/1824; GO6F
`16/1844; GO6F 16/23; GO6F 8/71; GOGF
`11/1435; GO6F 11/1448; GO6F 16/273;
`GO6F 16/275; GO6F 16/128; GO6F
`16/122; GO6E 16/16; GO6F 16/13-14;
`GO6F 16/176
`See application file for complete search history.
`
`(56)
`
`References Cited
`
`U.S. PATENT DOCUMENTS
`
`9/1998 Hug
`5,806,078 A
`6/1999 Park
`5,909,581 A
`7/1999 Van Huben
`5,920,867 A
`2/2000 Anglin
`6,026,414 A
`7/2000 Van Huben......... GOG6F 16/2343
`6,088,693 A *
`11/2000 Mohan et al.
`6,154,817 A
`7/2001 Anglin
`6,260,069 B
`9/2002 Hammacketal.
`6,449,624 B
`10/2002 Godfrey et al.
`6,463,463 B
`1/2003 Kawamuraetal.
`6,504,994 B2
`1/2003 Imsctal.
`6,505,200 B
`2/2003 Midgley
`6,526,418 B
`8/2003 Feigenbaum
`6,606,646 B2
`8/2003 Raff et al.
`6,611,849 B
`12/2003 Creemeret al.
`6,671,700 B
`3/2004 Mendezetal.
`6,708,221 B
`6/2004 Multer etal.
`6,757,696 B2
`6/2004 Haikin
`6,757,893 B
`7/2004 Chan
`6,760,759 B
`10/2004 Larueet al.
`6,810,405 B
`6,826,626 B1* 11/2004 McManus........... GO6I 16/9574
`709/246
`
`
`
`12/2004 Beyda
`3/2005 Abram etal.
`8/2005 Deshpandeet al.
`1/2006 Wu
`4/2006 Huang etal.
`4/2006 Brownet al.
`5/2006 Tackman ............. G06Q 50/188
`705/80
`
`5/2006 Bloch et al.
`6/2006 Goldick wn. GO6F 16/10
`6/2006 Barabanetal.
`
`
`
`6,829,622 B2
`6,874,037 B
`6,931,454 B2
`6,990,522 B2
`7,024,428 B
`7,035,847 B2
`7,051,364 B1*
`
`7,054,594 B2
`7,058,667 B2*
`7,065,658 B
`
`
`
`B2
`B2
`BI *
`Bl
`B2 *
`B2
`Bl
`Bl
`B1*
`
`B2
`B2
`Bl
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`B2
`Bl
`B2
`B2
`Bl
`B2
`B2
`B2
`Bl
`B2
`Bl
`B2
`B2
`B2
`Bl
`Bl
`Bl
`Bl
`B2
`Bl
`B2
`B2
`B2
`Bl
`B2
`B2
`Bl
`B2
`Bl
`B2
`B2
`B2
`B2
`Al
`Al
`Al
`Al
`Al
`Al
`Al*
`
`Al
`Al
`Al
`Al
`Al
`Al*
`
`Al
`Al
`Al
`Al
`Al
`Al
`Al*
`
`7,089,307
`7,136,934
`7,149,760
`7,155,488
`7,162,501
`7,224,973
`7,243,163
`7,260,646
`7,263,493
`
`7,269,433
`7,290,244
`7,325,038
`7,340,534
`7,398,327
`7,415,588
`7,415,615
`7,457,631
`7,A6T 353
`7,483,925
`7,526,575
`7,529,778
`7,574,711
`7,584,186
`7,587,446
`7,613,773
`7,639,116
`7,657,271
`7,680,838
`7,680,885
`7,707,165
`7,752,166
`7,761,414
`7,788,303
`7,796,779
`7,885,925
`7,895,334
`7,987,420
`8,009,966
`8,019,900
`8,112,549
`8,208,792
`8,244,288
`8,321,534
`8,370,423
`8,386,558
`8,504,519
`8,565,729
`8,595,182
`8,874,534
`9,143,561
`10,067,942
`10,289,607
`2002/0026478
`2002/0035697
`2002/0055942
`2002/0087588
`2002/0143795
`2002/0184318
`2002/0194382
`
`2003/00285 14
`2003/0028542
`2003/0038842
`2003/0074376
`2003/0078946
`2003/0115547
`
`2003/0125057
`2003/0135565
`2003/0233241
`2004/0003013
`2004/003 1027
`2004/0049345
`2004/0088348
`
`2004/0093361
`2004/0107225
`2004/0133629
`
`Al
`Al
`Al
`
`US 11,003,622 B2
`Page 2
`
`Zintel et al.
`Carter et al.
`Breer oo... cee GO06F 16/93
`Lunsford etal.
`Kupkova oc GOG6F 16/93
`Tsutazawa et al.
`Friend et al.
`Stefanik et al
`Provost voce GO6F 19/328
`705/2
`
`Vargaset al.
`Pecketal.
`Wang
`Cameronet al.
`Lee
`Hong et al.
`Skygebjer
`Yach etal.
`Kurlanderetal.
`Koskimieset al.
`Rabberset al.
`Dewey
`Zondervan et al.
`Chenet al.
`Onyonetal.
`Watt
`Saunders
`Kim
`Shaw
`Schauseret al.
`Jiang
`Quinlanet al.
`Freedman
`Mikesell et al.
`Strong et al.
`Strong et al.
`Tu etal.
`Klobactal.
`Bloom etal.
`Sekar et al.
`Srinivasan et al.
`Morioka
`Chipchase
`Roskindet al.
`Ozzie et al.
`Schleifer et al.
`Sachs
`Moseler et al.
`Nelson
`March
`Manzano
`Manzano
`Manzano
`Rodgerset al.
`McCurdy
`Reynolds
`McBride et al.
`Fletcher
`Pincau
`
`Kausik wo. GO06F 9/54
`709/246
`
`Lord
`Muttik et al.
`Peck etal.
`Benayoun
`Costello
`Ohwada oc. GO06F16/93
`715/229
`
`Pesola
`Estrada
`Marsh
`Coulthard
`Hiltgen
`McDonough et al.
`Yeager we HO4L 67/1068
`709/202
`
`Therrien et al.
`Rudoff
`Reynolds
`
`2/2
`2/2
`2/2
`4/2
`4/2
`6/2
`
`7/2
`7/2
`12/2
`1/2
`2/2
`3/2
`5/2
`
`5/2
`6/2
`7/2
`
`03
`03
`03
`03
`03
`03
`
`03
`03
`03
`
`04
`04
`
`04
`04
`04
`
`Box & Dropbox Exhibit 1006
`Page 2
`
`Box & Dropbox Exhibit 1006
`Page 2
`
`

`

`2004/0158817 A
`2004/0172424 A
`2005; 027757 A
`2005) 091316 A
`2005/0097225 A
`2005/0165722 Al
`2005/0177602 A
`2005/0188051 Al*®
`2005/0192966 A
`2005/0210371 Al*
`
`References Cited
`U.S. PATENT DOCUMENTS
`
`
`
`
`
`(56)
`
`
`
`US 11,003,622 B2
`
`Page 3
`
`8/2004 Okachi
`9/2004 Edelstein et al.
`2/2005 Kiessig al
`4/2005 Ponceet
`al.
`5/2005 Glatt et al.
`7/2005 Cannon
`8/2005 Kaler
`
`8/2005 Sneh cccccccccccccecses GO6F 9/44526
`709/213
`9/2005 Hilbert
`9/2005 Pollock ww. GO6F 17/212
`715/212
`
`FolderShare; Your Smart File Transfer Solution; <https://web.archive.
`org/web/20031220151508/hitp://www.foldcrshare.com:80/>; Dec. 20,
`2003.
`FolderShare—Secure Remote Access VPN Solution; Need your
`files on more than one computer?; <https://web.archive.org/web/
`20041230211050/http://www.foldershare.com:80/>; Dec. 30, 2004.
`FolderShare—Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/20040701113739/http://foldershare.com:80/>; Jul
`3004.
`P
`omens
`a
`,
`.
`.
`FolderShare—Secure Remote Access VPN Solution; Document
`Management & Real-time File Mirroring Solution; <https://web.
`archive.org/web/20040711062548/http://www.foldershare.com:
`80/>; Jul. 11, 2004.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`2003072205434?/http://foldershare.com:80/>; Jul. 22, 2003.
`10/2005 Ronkainenetal.
`2005/0220080 A
`FolderShare—Secure Remote Access VPN Solution; Document
`10/2005 Shah
`2005/0223047 A
`Management & Real-time File Mirroring Solution; <https://web.
`1/2006 Pyhalammi
`2006/0004698 A
`archive.org/web/20040730030655/http://www.foldershare.com:
`1/2006 Shaath etal.
`2006/0010150 A
`80/>: Tul. 30. 2004.
`2/2006 McVoy
`2006/0026567 A
`FolderShare—Secure Remote Access VPN Solution; Document
`3/2006 Suderman
`2006" 058907 A
`.
`.
`:
`:
`.
`-
`4/2006 Wolfish
`2006/0074985 A
`Management & Real-time File Mirroring Solution; <https://web.
`;
`ae
`iweb
`3
`113/http.//
`foldersh
`:
`5/2006 Strongetal.
`2006/0101064 A
`archive.org web/20040603205 113/http://www.foldershare.com:
`6/2006 Phillips
`3006'0129627 A
`80/>; Jun. 3, 2004.
`6/2006 Hughes
`2006/0136446 Al
`FolderShare—Secure Remote Access VPN Solution; Document
`6/2006 Holm
`2006/0143129 A
`Management & Real-time File Mirroring Solution; <https://web.
`7/2006 Godlin
`2006/0168118 A
`archive.org/web/200406 13 16 1906/http://www.foldershare.com:
`8/2006 Montulli et al.
`2006/0189348 A
`80/>; Jun. 13, 2004.
`10/2006 Lakshminath
`2006/0224626 A
`FolderShare—Secure Remote Access VPN Solution; Document
`1/2007 O'Neil
`2007/ 014314 A
`Management & Real-lime File Mirroring Solution; <https://web.
`1/2007 Reinsch
`2007) 1016629 A
`archive.org/web/20040629075057/http://www.foldershare.com:
`1/2007 Vasa _
`2007/0022158 A
`80/>:
`Jun. 29, 2004
`2/2007 Stakutis
`2007/0027936 A
`on :
`.
`.
`5/2007 Sumneret al.
`2007/0100913 A
`FolderShare—Secure Remote Access VPN Solution; Your Smart
`.
`i
`Tile Transfer & Real-time
`Solution: <
`File Mirrorine
`sJiwvels
`5/2007 Pepin
`2007/0124334 A
`
`
`
`2007/0174246 Al* ile Transter&Real-time7/2007 Sigurdsson......... GO6F 16/1787 Tile Mirroring Solution; <https://web.
`
`
`
`2007/0180084 Al*
`8/2007 Mohanty............. GO6F11/1464
`archive.org/web/200403 1623515 1/http://foldershare.com:80/>;, Mar.
`709/223
`16, 2004.
`2007/0191057 A
`8/2007 Kamada
`FolderShare—Secure Remote Access VPN Solution; Your Smart
`2007/0203927 A
`8/2007 Cave
`File Transfer & Real-time File Mirroring Solution; <https://web.
`2007/0238440 A
`10/2007 Sengupta etal.
`archive.org/web/20040325034239/http://www.foldershare.com:
`gup
`&
`Pp
`
`2007/0239725 Al* 10/2007 Bhat we HO04L 67/1095
`80/>; Mar. 25, 2004.
`2008/0005114 A
`1/2008 Li
`FolderShare—Secure Remote Access VPN Solution; Document
`2008; 005195 A
`1/2008 Li
`Management & Real-time File Mirroring Solution; <https://web.
`2008/0005280 A
`1/2008 Adams
`archive.org/web/200405 122 11417/http://www.foldershare.com:
`2008/0086494 A
`4/2008 [eller et al.
`80/>: May
`12. 2004
`2008/0168526 A
`7/2008 Robbin et al.
`F Ide She Ly,
`Fill Anywhere: <https://
`hi
`elweb/
`2008/0288578 Al
`11/2008 Silfverberg
`30 3031 180252/h svi
`»voldensha ttps:/ "80rn.Mag31 003
`2009/0013009 A
`1/2009 Nakayama
`2
`*http:/www toldershare.conr:80/>;
`May
`31,
`2003.
`2009/0024922 A
`1/2009 Markowitz etal.
`FolderShare—Secure Remote Access VPN So lution; Need your
`2009/0037718 A
`2/2009 Ganesh
`files on more than one computer?; <https://web.archive.org/web/
`2009/0063711 A
`3/2009 Finkelstein
`2004110403 1510/http:/Avww.foldershare.com:80/>: Nov. 4, 2004.
`2009/0282050 A
`11/2009 Thomasetal.
`FolderShare—Secure Remote Access VPN Solution; Need your
`2012/0192064 A
`7/2012 Antebi
`files on more than one computer?; <https://web.archive.org/web/
`2013/0226871 A
`8/2013 Sarnowski
`20041117092357/hitp: //www.foldershare.com:80/>; Nov. 17, 2004.
`2013! 226872 A
`8/2013 Barefoot
`FolderShare—Secure Remote Access VPN Solution; Need your
`2014" 053227 A
`2/2014 Ruppin
`files on more than one computer?; <https://web.archive.org/web/
`2016/0125058 A
`5/2016 Jain
`20041123085254/http://www.foldershare.com:80/>; Nov. 23, 2004.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`2003 1128 143634/http://foldershare.com:80/>; Nov. 28, 2003.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`20031001071631/http://foldershare.com:80/>; Oct.1, 2003.
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`Reeeashare“Secure Remote fechupotive ution. om’your
`2003080818393?/http://www.foldershare.com:80/>; Aug. 8, 2003.
`es on more
`than one computer?; <https://web.archive.org/we
`FolderShare—Secure Remote
`Access
`VPN Solution: Need your
`20041012083 127/http://www.foldershare.com:80/>; Oct. 12, 2004.
`ONESESIALST
`OCUISCATIONS
`“ACCESS
`NIN
`DOMMORS NESE YOU"
`FolderShare—Secure Remote Access VPN Solution; Need
`your
`files on more than one computer?; shitps:/‘web.archive.org/web/
`fil
`th
`a, hy
`5://
`hi
`¥ b/
`200408 140 15727/http://www.foldershare.com:80/>; Aug. 14, 2004.
`es on more
`than one computer?; <https://web.archive.org/we
`FolderShare—Secure Remote Access VPN Solution; Need your
`20041029085820/hUp://www.foldershare.com:80/>; Ocl. 29, 2004.
`°
`>
`J
`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?; <https://web.archive.org/web/
`20040820052105/http:/www.toldershare.com:80/>; Aug. 20, 2004.
`FolderShare—Secure Remote Access VPN Solution; Need your—_29940901034646/http://www.foldershare.com:80/>; Sep. 1, 2004.
`files on more than one computer?; <https://web.archive.org/web/
`FolderShare—Secure Remote Access VPN Solution; Need your
`2004 1211020957/http://foldershare.com:80/>; Dec. 11, 2004.
`files on more than one computer?; <https://web.archive.org/web/
`FolderShare—Secure Remote Access VPN Solution; Need your
`20040909075254/http://www.foldershare.com:80/>; Sep. 9, 2004.
`files on more than one computer?; <https://web.archive.org/web/
`FolderShare; Your Files Anywhere; <https://web.archive.org/web/
`20041217041726/http://foldershare.com:80/>; Dec. 17, 2004.
`2003092005 1943/http://www.foldershare.com:80/>; Sep. 20, 2003.
`
`
`
`
`
`
`
`
`
`
`
`
`Box & Dropbox Exhibit 1006
`Page 3
`
`OTHER PUBLICATIONS
`
`Box & Dropbox Exhibit 1006
`Page 3
`
`

`

`US 11,003,622 B2
`Page 4
`
`(56)
`
`References Cited
`OTHER PUBLICATIONS
`
`FolderShare—Secure Remote Access VPN Solution; Need your
`files on more than one computer’; <https://web.archive.org/web/
`20040924032 146/http://www.foldershare.com:80/>; Sep. 24, 2004.
`Marshall, M., “The Y CombinatorT.ist,” Venture Beat, Aug. 2007,
`Retrieved from the Internet: TTRI.: <https://venturebeat.com/2007/
`08/16/the-y-combinator-list/>, 4 pages.
`Jarvis, A., “Dropbox pitch deck to raise seed capital investment,”
`Medium, Mar. 2018, Retrieved from the Internet: URL: <https://
`medium.com/@adjblog/dropbox-pitch-deck-to-raise-seed-capital-
`investment-6a6cd65 17e56>, 12
`pages.
`
`* cited by examiner
`
`Box & Dropbox Exhibit 1006
`Page 4
`
`Box & Dropbox Exhibit 1006
`Page 4
`
`

`

`U.S. Patent
`
`May 11, 2021
`
`Sheet 1 of 3
`
`US 11,003,622 B2
`
`is7aSnow
`WHOMISNWauTHOTM1||¥asn|
`
`COwane,OE4gt_OHVOSADYgytS
`acim|-boLLES
`premaHWau
`
`
`
`GBL SIWWEOOHd—Ot
`iNI||OWIHAIN>)RON||2M
`NOLVONddfTLOWSH,
`
`
`
`SWvUOONd|WILSAS|WYHOOUd_NOUWONdaSNLtvdad0WwdOOUdUID
`
`(AMOINSINTIOANION|FIeVAOWGH|
`
`“vaSTINGOW"
`JOVEN[zeke|AYOWIN“lonwon||-——AWS90#¢_|
`JTSVAOINSU-NON
`
`WSISAS|
`
`
`
`LeLWAOU):|AHOWSW
`
`
`
`NdLNG
`
`WHSHdidd
`3OWUIENI.
`
`
`
`ONISSSO0Ud
`
`LIND
`
`ONUVead0
`
`WISAS
`
`
`NOLWONdel
`
`SAWHOOUd
`
`iii
`
`uaindo
`
`bol
`
`enGOL
`
`
`
`L‘Old
`
`|SOUMALN
`
`
`
`
`
`Box & Dropbox Exhibit 1006
`Page 5
`
`
`
`Box & Dropbox Exhibit 1006
`Page 5
`
`
`
`
`
`
`
`
`
`
`
`
`

`

`U.S. Patent
`
`May11, 2021
`
`Sheet 2 of 3
`
`US 11,003,622 B2
`
`FIG.2
`
`200
`
`DISPLAY
`
`290
`
`COMPUTERSYSTEM
`
`USERDEVICE
`
`
`STORAGE 270
`SERVER
`
`
` 2
`
`6
`
`
`
`8
`
`
`
`
`USERDEVICE
`
`
`DISPLAY
`
`| | |||
`
`Lu
`YO
`©
`Ss
`<aer
`ft
`Q
`
`Box & Dropbox Exhibit 1006
`Page 6
`
`Box & Dropbox Exhibit 1006
`Page 6
`
`

`

`U.S. Patent
`
`May11, 2021
`
`Sheet 3 of 3
`
`US 11,003,622 B2
`
`uw
`O
`
`>m
`
`fO
`
`it
`”
`3
`
`oO
`t+
`ise)
`
`
`
`
`
`
`
`
`
`
`
`
`Y
`%
`°
`
`»
`©
`
`oO
`™~
`o
`
`OQ
`oO
`o
`
`2
`oO
`
`Oo
`|
`oO
`
`a
`5
`
`
`
`|
`oOCe
`oO
`
`oO
`oO
`
`Nl
`
`
`370
`
`370
`
`%NI
`
`STORAGE
`
`Oo
`N
`
`FIG.3
`
`
`
`
`
`
`
`
`oO
`
`™o
`
`uw
`
`0>W
`
`o
`ONa
`Ww
`
`”5
`
`Oo
`Ww
`oO
`
`Box & Dropbox Exhibit 1006
`Page 7
`
`
`
`
`
`
`
`
`Box & Dropbox Exhibit 1006
`Page 7
`
`

`

`US 11,003,622 B2
`
`1
`ARCHITECTURE FOR MANAGEMENT OF
`DIGITAL FILES ACROSS DISTRIBUTED
`NETWORK
`
`
`
`
` eslCROSS-REFERENCE TO RELATED
`APPLICATIONS
`
`This application is a continuation of U.S. patent applica-
`tion Ser. No. 16/017,348. filed Jun. 25, 2018. which is a
`continuation of U.S. patent application Ser. No. 14/860,289,
`filed Sep. 21, 2015, now U.S. Pat. No. 10,067,942, whichis
`a continuation of U.S. patent application Ser. No. 12/267,
`852, filed Nov. 10, 2008, now U.S. Pat. No. 9,143,561,
`which claims priority to U.S. Provisional Application No.
`
`60/986,896 entitled “ARCHITECTURE FOR MANAGE-
`MENT OF DIGITAL FILES ACROSS DISTRIBUTED
`
`NETWORK”andfiled Nov. 9, 2007, the contents of which
`are hereby incorporated by reference in their entirety.
`
`FIELD OF THE INVENTION
`
`This invention relates 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
`application, second only to email, on the Internet. Further,
`customers are increasingly using more than one computing
`device; a customer may have a desktop computer at home,
`one at work, and a constantly connected “smart phone”. Due
`to the confluence of these two trends, file management
`across these devices has become a problem.
`Although modern devices are easily connected, they do
`not provide the customer a seamless environment; the cus-
`tomer must manually handle many aspects of that connec-
`tion. With regards to file management, customers must
`manually move files between their devices using some
`protocol like email, ftp, or by posting, them on the Web.
`These practices lead to problems that include:
`The proliferation of redundantfile copies. This prolifera-
`tion creates a confusing environment where the cus-
`tomeris unclear where the “official” or newest version
`of a file exists.
`The creation of an error-prone environment. Some docu-
`ments, such as those associated with word processing
`and desktop publishing, externally reference otherfiles.
`Copying such a document can break these references
`causing errors that the customer has to handle manu-
`ally. An example of such a document is a desktop
`publishing document that contains a reference to an
`image. Ifthat imagefile is not transferred along with
`the desktop publishing file, the image will appear as a
`brokenlink.
`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 move files around to
`ensure their accessibility on his devices is unnecessary, and
`
`20
`
`25
`
`40
`
`45
`
`60
`
`65
`
`2
`is an indicator of a lack of customer-focused design in
`modern file systems. File systems in use today are direct
`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 problemthat 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 customeraccessto 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
`for 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,
`place data on an always-connected host machine. Unlike
`remote desktop software, the hast machine is not one on
`which the customer performs computing tasks. ‘he host
`machine is used as a storage mechanism, and any compu-
`tation performed on that machine serves to supports its use
`as such. Distributed file systems generally provide the right
`functionality for customers to share files between their
`devices. However, distributed file systems are usually
`deployed as a shared resource; that is, other customers have
`access to it. Because of this sharing, a customer’s files may
`be buried deep ina filing structure, and it may not always be
`immediately evident to customers what kind of access they
`have to a particular file. Further, to use a distributed file
`system, the customer must always be connected to it. Files
`stored on a distributed file system are generally inaccessible
`if the customer’s machine is not connected to it, unless the
`customer has copied or moved the files to his machine’s
`local hard drive. However, doing so immediately creates the
`problem of having two filing systems for the samefile,
`creating a mental burden on the customer.
`Additionally, accessing a file located on a distributedfile
`system tends to be slower than accessing files on the local
`hard drive. Modern applications are usually written to
`assumethatthefiles they access are located locally, and thus
`are not optimized to access remote files. When these appli-
`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 never entirely sure if the 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 notreflect the existenceofthe file
`at all until synchronization finishes.
`
`Box & Dropbox Exhibit 1006
`Page 8
`
`Box & Dropbox Exhibit 1006
`Page 8
`
`

`

`US 11,003,622 B2
`
`3
`FTPis similar to a distributed file system with regards to
`files being hosted on a remote server. However FTP gener-
`ally docs 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
`distributedfile 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.
`Email was originally invented for messaging. From the
`beginning, the model it employs to make files 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 customer to another. A customer can
`makea file remotely available using email by attaching the
`file to an email and sendingit 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
`FTP as the process is even more manual: a customer must
`find the message containing the file 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 it back out, the results would be
`ambiguousto 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
`
`20
`
`25
`
`preclude the customer from employing several effective
`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 ofthe files, the customer must carry
`the device with them at all times, and must followthe
`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 5
`ordinary skill in the art after reading, this disclosure.
`
`40
`
`45
`
`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 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. ‘lhe first file copy
`may be automatically received from the second application
`responsive to the user modifying a content ofthefirst file,
`where the first file copy is a version of the first 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
`
`60
`
`65
`
`4
`computer system associated with the userto replace an older
`version ofthefirst file stored on the third computer system.
`
`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 embodimentof the invention can
`be implemented;
`FIG. 2 is a functional block diagram of an exemplary
`operating 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
`
`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 itselfto 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. Once transported to the remote host, the
`string of data is decoded to generate a computerprocess,still
`called the mobile agent object, within the remote host
`system. ‘he decoded mobile agent object includes those
`objects encoded as described above and remains in its
`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 referenceasif
`fully set forth herein.
`FIG. 1 illustrates an example ofa 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 of a 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
`numerous other general purpose or special purpose comput-
`ing system environments or configurations. Examples of
`
`Box & Dropbox Exhibit 1006
`Page 9
`
`Box & Dropbox Exhibit 1006
`Page 9
`
`

`

`US 11,003,622 B2
`
`5
`well known computing systems, environments, and/or con-
`figurations that may he suitable for use with the invention
`include, but are not limited to, personal computers, server
`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 the like.
`[Embodiments of the invention may be described in the
`general context of compuler-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 mayalso be practiced in
`distributed computing environments where tasks are per-
`formed byremote processing devicesthat are linked through
`a communications network.
`In a distributed computing
`environment, program modules maybe located 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 maybe any of several 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
`
`Ele