(19) United States
`(12) Patent Application Publication (10) Pub. No.: US 2003/0009518A1
`(43) Pub. Date:
`Jan. 9, 2003
`Harrow et al.
`
`US 2003OOO9518A1
`
`(54) METHOD AND APPARATUS FOR
`PEER-TO-PEER SERVICES
`
`(75) Inventors: Ivan P. Harrow, Navan (IE); David O.
`Fleming, Killarney (IE); Frank X.
`Daly, Killiney (IE); Dermot E. Honan,
`Leixlip (IE); Martin G. Curley,
`Maynooth (IE)
`Correspondence Address:
`BLAKELY SOKOLOFFTAYLOR & ZAFMAN
`12400 WILSHIRE BOULEVARD, SEVENTH
`FLOOR
`LOS ANGELES, CA 90025 (US)
`(73) Assignee: Intel Corporation, Santa Clara, CA
`(21) Appl. No.:
`10/095,323
`
`(22) Filed:
`
`Mar. 8, 2002
`Related U.S. Application Data
`(60) Provisional application No. 60/303,706, filed on Jul.
`6, 2001.
`
`Publication Classification
`
`(51) Int. Cl." ..................................................... G06F 15/16
`(52) U.S. Cl. .............................................................. 709/203
`
`(57)
`
`ABSTRACT
`
`A method and apparatus for peer-to-peer Services have been
`described.
`
`A 400
`
`
`
`Web Server
`A22
`
`Directory Server
`402
`
`415
`
`Client P
`404-P
`
`
`
`Client B
`
`404-B
`
`Client C
`
`4O4-C
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 1 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 1 of 24
`
`US 2003/0009518A1
`
`100
`1.
`
`
`
`FIG. 1 (Prior Art)
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 2 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 2 of 24
`
`US 2003/0009518A1
`
`aS
`
`&
`
`CD
`O
`s
`9
`CO
`
`9
`CN
`
`g
`CN
`
`O
`O
`CN
`
`a-
`CN
`
`?
`l
`O
`
`3. &
`
`OO O
`CN CN
`CN,
`CN
`
`S
`CN
`
`r
`S.
`
`CN
`&
`
`S.
`
`asa
`
`5.
`O
`k n
`
`se
`
`CN
`CD
`l
`
`S
`E
`O
`O
`
`O g
`
`9.
`O
`n
`
`O
`g
`CD
`Na
`
`9.
`O
`s CC
`
`Da
`c
`O
`2
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 3 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 3 of 24
`
`US 2003/0009518A1
`
`
`
`
`
`Directory Server
`3O2
`
`A 300
`
`Client P
`304-P
`
`
`
`Client D
`304-D
`
`Client B
`
`3O4-B
`
`(...)
`
`FG. 3
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 4 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 4 of 24
`
`US 2003/0009518A1
`
`A- 400
`
`Web Server
`422
`
`
`
`internet
`418
`
`
`
`
`
`
`
`416
`
`-
`
`415
`
`Y
`
`Directory Server
`402
`
`Client P
`404-P
`
`FG. 4
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 5 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 5 of 24
`
`US 2003/0009518A1
`
`A - 500
`
`File Server
`
`522
`
`
`
`Directory Server
`502
`
`- 50
`
`512 -1
`
`Client P
`
`
`
`Client A
`504-A
`
`(E)
`
`504-B
`
`Client C
`
`N
`Client D
`514
`
`504-D
`
`FIG. 5
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 6 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 6 of 24
`
`US 2003/0009518A1
`
`Directory Server
`6O2
`
`A- 600
`
`Client P
`604-P
`
`
`
`
`
`Client B
`604-B
`
`Client C
`604-C
`
`FIG. 6
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 7 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 7 of 24
`
`US 2003/0009518A1
`
`OO/ -7
`
`XNN-90/
`
`
`
`-
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 8 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 8 of 24
`
`US 2003/0009518A1
`
`
`
`
`
`
`
`
`
`
`
`User launches
`SS from Start
`Menu Shortcut
`
`is user on
`network?
`
`Read Local
`database
`
`Launch SLS in
`offine node
`
`
`
`
`
`
`
`and Learn Website
`
`
`
`Does the use
`have the latest
`components?
`
`Download new
`COG. tO
`p user's PC
`
`2
`
`Ooes the use
`exist in the
`database?
`
`Create an entry in
`the Users table fo
`the user's D
`
`Are the lates
`anti-virus files
`present?
`
`Issue warning and
`how to update
`
`dentify user's
`subnet & match to
`site.
`
`Has the user's
`ubnet changed?
`
`Update subnet in
`Users table. If
`different site, update
`content location
`
`is the local
`share created
`
`
`
`Create directory and
`share on c:\ drive
`
`FIG. 8A
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 9 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 9 of 24
`
`US 2003/0009518A1
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Update
`sharename field in
`Users table
`
`
`
`N
`
`Update
`permissions on
`local share
`
`Are the share
`permissions
`correct?
`
`
`
`Y
`
`Get Table Sync
`value from
`Database
`
`
`
`
`
`S value same as
`local DB value?
`
`N
`
`Sync Filelindex
`Sync Modules
`
`Y
`
`
`
`ls the eLearning
`player up to date?
`
`Y
`
`is the SS
`hortcut present?
`
`
`
`
`
`Update eLearning
`player
`
`Create SS
`shortcut
`
`Open main SLS
`webpage
`
`FIG
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 10 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 10 of 24
`
`US 2003/0009518A1
`
`
`
`()
`
`Select File
`
`s the file
`local on the
`client?
`
`Lookup User's Site
`Query for file
`on local site
`
`N
`
`is the file of
`he local site2
`
`Query in turn each
`site on search list
`until site with file is
`found
`
`Buildlist of PCs
`with file.
`Check each PC in
`turn until found.
`
`
`
`
`
`is the file
`available?
`
`
`
`
`
`s the file date
`time correct2
`
`Return an
`estimated
`download tirne to
`the user and
`prompt for action
`
`FIG. 9A
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 11 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 11 of 24 US 2003/0009518A1
`
`Copy File to local
`share and update
`database as to
`new Ocation
`availability
`
`ownload and
`Run later
`
`ownload and Run Now
`Download and Run Later?
`Schedule for later downloag'
`
`Download Later
`
`Schedule
`download to
`happen at a later
`time.
`
`
`
`Download &
`Run Now
`
`Copy File to local
`share.
`Update Database
`as to flew
`location
`availability
`
`Decompress File
`to temp directory
`
`Open File in SLS
`or launch player
`for file
`
`
`
`FIG. 9B
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 12 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 12 of 24
`
`US 2003/0009518A1
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 13 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 13 of 24
`
`US 2003/0009518A1
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 14 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 14 of 24
`
`US 2003/0009518A1
`
`:
`
`?
`
`
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 15 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 15 of 24
`
`US 2003/0009518A1
`
`8.
`
`
`
`,
`
`
`
`peo?uMop 3? e fiu?ump SIS JO M??A
`
`
`
`eienwiyos uueetbue eleS º?ºitti
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 16 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 16 of 24
`
`US 2003/0009518A1
`
`
`
`AL SNIÐI - 1.00? fº??itið að þ!
`
`&
`
`grea.
`
`
`
`
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 17 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 17 of 24
`
`US 2003/0009518A1
`
`TOET)
`
`ENTZUTZER! **
`
`
`
`
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 18 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 18 of 24
`
`US 2003/0009518A1
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 19 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 19 of 24
`
`US 2003/0009518A1
`
`
`
`|
`
`
`
`QuæquoO Màu 6uppe ?||?M STIS JO M??A
`
`
`
`
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 20 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 20 of 24 US 2003/0009518A1
`
`A-1 100
`
`
`
`Web Server
`
`
`
`
`
`PC
`
`PC2
`
`FIG 11
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 21 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 21 of 24 US 2003/0009518A1
`
`A- 1200
`
`iser requests a
`efer 3 jet-sites
`
`
`
`
`
`
`
`
`
`
`
`
`
`
`Cennect to
`he website in ornia
`way
`
`et
`website &
`enroad tie
`
`
`
`pdate
`database
`it
`is
`is
`ti
`
`F.G. 12
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 22 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 22 of 24 US 2003/0009518A1
`
`A - 1300
`
`PC
`
`
`
`Directory Server
`
`ide Area letfjork
`
`Handheid FC
`
`FIG. 13
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 23 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 23 of 24 US 2003/0009518A1
`
`A 1400
`
`Client A
`
`
`
`FIG. 14
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 24 of 36
`
`

`

`Patent Application Publication
`
`Jan. 9, 2003 Sheet 24 of 24 US 2003/0009518A1
`
`A 1500
`
`
`
`
`
`Database
`
`Computer
`
`
`
`Computer
`
`Computer
`
`Computer
`
`Computer
`
`F.G. 15
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 25 of 36
`
`

`

`US 2003/0009518 A1
`
`Jan. 9, 2003
`
`METHOD AND APPARATUS FOR PEER-TO-PEER
`SERVICES
`
`RELATED APPLICATION
`0001. The present patent application claims priority of
`U.S. Provisional Application Serial No. 60/303,706 filed Jul.
`6, 2001 titled “Share and Learn Software”, which is hereby
`incorporated herein by reference.
`
`FIELD OF THE INVENTION
`0002 The present invention pertains to networks. More
`particularly, the present invention relates to a method and
`apparatus for peer-to-peer Services.
`
`BACKGROUND OF THE INVENTION
`0003. Many companies are adopting the use of networks
`for sharing information. The Internet and Intranets are
`examples of Such a networks. This information may be
`shared within a company, university, local group, or to users
`around the World, etc.
`0004. As the information shared becomes richer in con
`tent, Such as Streaming video, etc., it may place more
`demands on servers, which may lower available bandwidth,
`and Slow down access to the information on, for example, a
`Wide Area Network (WAN), etc. One approach to improving
`performance is to “widen the pipe” or bandwidth that the
`WAN may handle. This may be a very expensive approach
`particularly where peak or spikes in traffic may be a limiting
`factor. This may present a problem.
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`0005 The present invention is illustrated by way of
`example and not limitation in the figures of the accompa
`nying drawings, in which like references indicate Similar
`elements and in which:
`0006 FIG. 1 illustrates a network environment in which
`the method and apparatus of the present invention may be
`implemented;
`0007 FIG. 2 is a block diagram of a computer system;
`0008 FIG. 3 illustrates one embodiment of the present
`invention being used for file sharing;
`0009 FIG. 4 illustrates one embodiment of the present
`invention being used as a web proxy Service;
`0010 FIG. 5 illustrates one embodiment of the present
`invention where a third party is controlling the content
`transfer between clients across a WAN/LAN,
`0.011
`FIG. 6 illustrates one embodiment of the present
`invention being used for distributed backup and Storage;
`0012 FIG. 7 illustrates one embodiment of the present
`invention using router table analysis for a network;
`0013 FIGS. 8A and 8B illustrate one embodiment of
`SLS launch flow;
`0014 FIGS. 9A and 9B illustrate one embodiment of
`SLS file flow;
`0015 FIGS. 10A through 10H illustrate possible user
`interfaces of the present invention;
`
`0016 FIG. 11 illustrates one embodiment of the present
`invention a for a peer-to-peer proxy,
`0017 FIG. 12 is a flow chart of one embodiment of the
`present invention as a peer-to-peer proxy,
`0018 FIG. 13 illustrates one embodiment of the present
`invention where a third party is controlling a file transfer;
`0019 FIG. 14 illustrates one embodiment of the present
`invention for backup Storage; and
`0020 FIG. 15 illustrates one embodiment of the present
`invention for router table analysis.
`
`DETAILED DESCRIPTION
`0021. A method and apparatus for peer-to-peer services
`are described.
`0022. The present invention by providing a capability
`whereby network traffic may be shifted to another network
`may allow more efficient transfer of information, data, etc.
`One Such example of shifting network traffic may be shifting
`WAN traffic to LAN peer-to-peer traffic.
`0023. Both a WAN such as the Internet and a WAN such
`as a corporate Intranet may find this traffic shifting capability
`to be useful. To better illustrate the present invention,
`references will be made to an Intranet, however, one of
`ordinary skill in the art will recognize that the present
`invention may be practiced on other networks, Such as the
`Internet.
`0024 Intranets and particularly large corporate Intranets
`are host to, and are sharing and transferring, much more
`information than in the past. The advent of Streaming video
`is an example of content which may require more instanta
`neous bandwidth than the network was designed for. Shift
`ing WAN traffic to a LAN communication may free up WAN
`bandwidth. If a server based content is able to be placed on
`a client on a LAN, then another client on the LAN may be
`able to access the information through peer-to-peer client
`interaction. This shifting of WAN server based content to a
`LAN client for peer-to-peer transfer allows for file sharing.
`0025 FIG. 1 illustrates a network environment 100 in
`which the techniques described may be applied. The net
`work environment 100 has a network 102 that connects S
`servers 104-1 through 104-S, and C clients 108-1 through
`108-C. More details are described below.
`0026 FIG. 2 illustrates a computer system 200 in block
`diagram form, which may be representative of any of the
`clients and/or servers shown in FIG. 1. More details are
`described below.
`0027 FIG. 3 illustrates one embodiment of the present
`invention 300 being used for file sharing. Directory Server
`302 maintains a directory of where files are located. Client
`A 304-A makes a file request 310 to directory server 302.
`Directory server 302 looks to see where the file is located by
`referencing a prioritized list of closest clients with the latest
`revision of the file. The directory server 302 communicates
`the location of the file 312 to Client A. In this illustration that
`communication 312 conveys to Client A304-A that Client D
`304-D has a copy of the file. Client A 304-A then commu
`nicates 314 with Client D 304-D and gets the file located on
`Client D 304-D. The communication 314 between Client A
`304-A and Client D 304-D is a peer-to-peer communication.
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 26 of 36
`
`

`

`US 2003/0009518 A1
`
`Jan. 9, 2003
`
`0028. Thus, rather than Client A304-A having to retrieve
`the file from a server possibly located on a WAN, the
`directory server 302 has communicated to Client A 304-A
`that the file may be retrieved from another Client D 304-D.
`Thus, traffic that may have originally had to occur on a WAN
`has been shifted to a peer-to-peer transfer, possibly on a
`LAN
`0029 Note that since directory server 302 maintains a list
`of files and locations, after Client A304-A has a copy of the
`file, directory server 302 will have this information also.
`Now, for example, if Client B 304-B requests from directory
`server 302 a copy of the file, the directory server 302 would
`know that Client A 304-A and Client D 304-D both have
`copies. Directory server 302 may then inform Client B
`304-B that Client A 304-A is the nearest client that has a
`copy. Client B 304-B may then effect a peer-to-peer transfer
`with Client A 304-A. After this transfer, directory sever 302
`would then know that Clients A304-A, Client B 304-B, and
`Client D 304-D have a copy of the file.
`0.030. One of ordinary skill in the art will appreciate that
`the file sharing approach may “propagate' files acroSS
`networks. This propagation will allow directory server 302
`to communicate to any requesting client the closest client
`having a file for a transfer. When the clients are located on
`the same local network then a LAN peer-to-peer transfer will
`be possible. LAN transfers are generally faster than WAN to
`LAN transferS because of fewer intervening routers,
`Switches, proxies, firewalls, etc.
`0031) If there is no local client that has the file requested,
`then the directory server 302 may direct the client to get the
`file from a client on a WAN and/or a file server. For example,
`Client D 304-D may have originally placed a file request
`with the directory server 302 and been informed that there
`was no copy of the file on a local client. Client D 304-D may
`have had to obtain a copy of the file, for example, over the
`Internet from Some remote server. Once Client D 304-D has
`a copy of the file, directory server 302 knows this and so as
`explained above, if Client A 304-A then requests the file
`directory server 302 can inform Client A 304-A that Client
`D 304-D has a copy.
`0032. As discussed above, the capability for shifting of
`WAN server based content to a LAN client for peer-to-peer
`transfer allows for file sharing. One of ordinary skill in the
`art will appreciate that by practicing the present invention in
`Such an environment, a client based proxy Service used to
`redirect data transferS from the network in a peer-to-peer
`environment may be achieved. That is, by redirecting, for
`example, Internet web requests to a more local network copy
`of the file, a web proxy service may be effected with the
`present invention.
`0.033
`FIG. 4 illustrates one embodiment of the present
`invention 400 being used as a web proxy service. Directory
`Server 402 maintains a directory of where web files are
`located on a local network 415. Client A404-A makes a file
`request 410 (via, for example, Surfing the web) to directory
`server 402. Directory server 402 looks to see where the file
`may be located on the local network 415 by referencing a
`prioritized list of closest clients with the latest version of the
`file. The directory server 402 communicates 412 the location
`of the file to Client A 404-A. In this illustration that
`communication 412 conveys to Client A404-A that Client D
`404-D has a copy of the file and redirects Client A 404-A to
`
`get the file located on Client D 404-D. The communication
`414 between Client A 404-A and Client D 404-D is a
`peer-to-peer communication.
`0034. Thus, rather than Client A404-A having to retrieve
`the file from a web server 422 connected via 420 to the
`Internet 418, and via connection 416 to the directory server
`402, Client A 404-A has retrieved the file from Client D
`404-D. Thus, possible Internet traffic has been redirected
`resulting in a peer-to-peer transfer, possibly on a LAN. Thus,
`“local” Storage of the file, plus the redirection allowing
`access to the local copy of the file, Serves the function of a
`proXy.
`0035. Note that since directory server 402 maintains a list
`of files and locations, after Client A404-A has a copy of the
`file, directory server 402 will have this information also.
`Now, for example, if Client B 404-B requests the same file
`while, for example, web browsing, the directory server 402
`would know that Client A 404-A and Client D 404-D both
`have copies. Directory server 402 may then inform Client B
`404-B that Client A 404-A is the nearest client that has a
`copy. Client B 304-B may then affect a peer-to-peer transfer
`with Client A 404-A. After this transfer, directory sever 402
`would then know that Clients A404-A, Client B 404-B, and
`Client D 404-D have a copy of the file.
`0036) One of ordinary skill in the art will appreciate that
`this file sharing approach may “propagate' web files acroSS
`networks. Web Sites have information that changes on a
`regular basis. AS was detailed previously, the directory
`server 402 maintains where the latest files are located. Thus,
`for example, assume it is time X, in FIG. 4, where Client A
`404-A has retrieved a copy of the file from Client D 404-D.
`ASSume next that at time X--10 minutes, Client B 404-B
`requests the same file. If directory server 402 is aware of a
`more recent copy of the file, it will direct Client B 404-B to
`retrieve the file from that location. This will also be the
`situation, where, for example, Client A 404-A has a local
`copy of the file at time X, but at time X+10 minutes requests
`the file again. If the most recent copy is on Client A 404-A
`then the directory server 402 will direct Client A 404-A to
`Client A404-A. If the most recent copy is on another client,
`say for example, Client C 404-C, then the directory server
`402 will direct Client A404-A to Client 404-C for the copy.
`The directory server 402 will direct Client A 404-A to the
`web for a copy if there is no copy available on the local
`network 415. If the most recent copy is on the web, then the
`directory server 402 may direct Client A 404-A to the web
`for a copy.
`0037. The directory server 402 may also have an expi
`ration timeout feature. That is, after Say 10 minutes, the
`directory server 402 may direct a client to retrieve a copy of
`the file from the web server 422. In this way web content on
`a local network would be updated after being on the local
`network for more than 10 minutes. This timeout feature may
`be tailored to the web content. For example, a website
`dealing with word definitions may not need to be updated as
`frequently as a website having current news events.
`0038. As discussed above, the capability for shifting of
`WAN server based content to a LAN client for peer-to-peer
`transfer allows for file sharing. The clients discussed above
`were assumed, for convenience of discussion, to be con
`nected to the network for most of the time. This may not be
`the case. For example, portable computers, PDAS, etc. may
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 27 of 36
`
`

`

`US 2003/0009518 A1
`
`Jan. 9, 2003
`
`be connected and disconnected as needed. One example may
`be a Sales office, where the outside Sales people only connect
`to the network when they are in the office. Portable com
`puterS may not be connected to the network long enough to
`download a large file, Such as a Video presentation. This may
`be due to a time constraint or a bandwidth constraint.
`However, if the user of the portable computer could affect a
`LAN peer-to-peer transfer of the information, the bandwidth
`may be higher than from, for example, a server on the WAN.
`By allowing the user of the portable to select what infor
`mation needs to be downloaded and having that information
`directed to a nearby client on the LAN, then the next time
`the user connects to the network, a LAN peer-to-peer
`transfer may be possible. Thus, the portable computer user,
`in effect, is a third party controlling the WAN to LAN
`transfer.
`0039 FIG. 5 illustrates one embodiment of the present
`invention 500 where a third party is controlling the WAN to
`LAN transfer. Here, Client P 504-P represents a portable
`client such as a portable computer or PDA. Client P504-P
`may need a file from File Server 522. A request 510 to
`directory server 502 may indicate that there is no local copy
`on Client A, B, C, D, or P (504-A through P, respectively).
`At this point Client P504-P may decide to either stay online
`and download the file or direct that it be downloaded to the
`nearest client. If the latter choice is Selected, then the
`directory server 502 may determine that Client D 504-D is
`the nearest client and direct that the download of the file
`from File server 522 be directed to Client D 504-D. This
`transfer (via 522,520,518,502,512) may occur with Client
`P 504-P either presently connected to the network or dis
`connected. When the file has been downloaded to Client D
`504-D, the directory server 502 has this information stored,
`and so when Client P504-P again connects to the network
`and requests the file, a local peer-to-peer transfer 514 from
`Client D 504-D to Client P 504-P is possible. In another
`embodiment, the local peer-to-peer transfer 514 from Client
`D 504-D to Client P 504-P may be initiated automatically
`when Client P504-P is connected to the network and Client
`D504-D has the file locally. Again, once Client P504-P has
`transferred the file, directory server 502 is aware that Client
`D504-D and now Client P504-Pboth have copies of the file.
`The device referred to in this section as the File Server 522
`may also be another device, Such as, a client on a remote
`network, etc.
`0040. In another embodiment, when Client P 504-P is
`connected to the network, directory server 502 may query
`Client P504-P to see if Client P504-P has selected files to
`be downloaded while offline. This download list may have
`previously been retrieved from a directory file server (either
`502 and/or other directory file servers).
`0041). In another embodiment, when Client P 504-P is
`connected to the network, files resident on Client P 504-P
`may be communicated to a directory Server, Such as direc
`tory server 502. If new files, or files modified having a more
`recent date are communicated to directory server 502, then
`other clients will now have access to these files. Thus, for
`example, a portable computer used by a SalesperSon may be
`used to detail customer Visit information while the Salesper
`Son is at the customer. Upon returning to the Sales office and
`plugging into the network, the Client P504-P may send to
`the directory server 502 information regarding files on
`
`Client P504-P. These updated files would then be available
`via directory server 502 knowing they were on Client P
`504-P.
`0042. In another embodiment, when Client P 504-P
`returns with updated files, the directory server 502 and/or the
`Client P504-P may direct that a local copy of the updated
`files be made on a non-portable computer. In this embodi
`ment then, the third party control may effect a transfer of
`files so that when the portable client is disconnected from the
`network a local copy is available to the rest of the network.
`The directory server 502 and/or the Client P504-P may also
`direct that a copy of the updated files be sent to a central
`and/or web server. Thus, third party control of transfers is to
`and from any Source and/or destination. The ability for a
`portable client, such as Client P504-P to send files to another
`client Serves as a backup of those files.
`0043 New and updated files are not limited to a portable
`client, such as Client P504-P. Other clients, such as desktop
`clients, with new files or updated files may also use the
`techniques discussed above. Thus, in one embodiment of the
`present invention clients may use the network Services for
`distributed backup and Storage. Clients are not the only
`Source of content and In yet another embodiment, files from
`all Sources, clients, Servers, etc., may make use of the
`present invention to effect shifting of content for distributed
`backup and Storage.
`0044 FIG. 6 illustrates one embodiment 600 of the
`present invention being used for distributed backup and
`storage. Client A 604-A communicates with directory server
`602 via link 610 a request to store a local file which is
`located on Client A 604-A on another client or clients.
`Directory server 602 informs Client A 604-A that Client B
`604-B and Client D 604-D are nearest and have available
`storage. Client A604-Athen transfers the files or parts of the
`files to Client B 604-B via link 612. If more storage is
`needed and/or a distributed backup was requested, then
`Client A 604-A may transfer files via 614 to Client D 604-D.
`These transferS are peer-to-peer and may occur on a LAN.
`In this example, the client has initiated the backup request.
`In another embodiment of the present invention, the backup
`request may originate from the directory Server 604 and/or
`may originate from a file Server on a network.
`0045. As discussed above, the capability for shifting of
`content from one network to another allows for many
`capabilities. Reference has been made to clients, Servers,
`WAN, LAN, peer-to-peer, etc. In many cases the benefit of
`peer-to-peer transferS occurs when the clients are “nearest'
`to each other. From a network viewpoint the “nearest' client
`for file Sharing, transfer, etc. may not be the closest physi
`cally. From a network performance Standpoint the “nearest'
`client may be that client and/or clients, that may transfer the
`information the fastest. Thus, all the above approaches for
`shifting traffic may benefit from Such an analysis of the
`network. One Such approach to generating the “nearest'
`client information may use router table analysis.
`0046 FIG. 7 illustrates one embodiment 700 of the
`present invention using router table analysis for a network.
`Server 702 is connected to routers 706-A through 706-N.
`Each router (706-A through 706-N) is connected to a respec
`tive group 706-ANX through 706-NNX. Each group (706
`ANX through 706-NNX) includes a Network 706-AN
`through 706-NN respectively and respective Clients A
`
`Major Data Ex. 1129
`Major Data UAB v. Bright Data Ltd.
`IPR2022-00915
`Page 28 of 36
`
`

`

`US 2003/0009518 A1
`
`Jan. 9, 2003
`
`through N. Database 704 is connected to the server 702.
`During operation, the Server and router traffic is monitored
`to determine transfer times of files. This information is
`analyzed and stored in database 704. In one embodiment of
`the present invention, the database 704 would maintain a
`prioritized list of closest clients for a particular file. This
`database 704 information may then be accessed by a direc
`tory Server to determine how to re-route and/or redirect
`traffic So as to effect the fastest peer-to-peer transfer between
`clients.
`0047 Thus, what has been described are embodiments of
`the present invention for use in Such areas as file sharing,
`redirected data transfers, third party control of transfers,
`distributed backup and Storage, and router table analysis.
`0.048. The descriptions above have been kept simple to
`not obscure and yet illustrate the present invention. What
`now follows are more detailed possible embodiments of the
`present invention. Screen shots are used to illustrate possible
`features and capabilities of the present invention. However,
`it is to be understood that these are other embodiments of the
`present invention and that many others are possible.
`0049. Today's Intranet is rather one-dimensional
`enabling the transfer of information, text, files etc. Intel (R)
`Share and Learn Software (SLS) introduces the ability to
`Significantly improve the capability and effectiveness of an
`Intranet by enabling much more efficient transport of Video
`and rich media files by shifting the bottleneck for Video
`Intranet from the network to the computer. Note that, for
`purposes of illustrating this embodiment of the present
`invention, an intranet may be defined as: a computer net
`work connecting an affiliated Set of clients using Standard
`internet protocols, such as, TCP/IP and HTTP; and/or: an
`IP-based network of nodes behind a firewall, or behind
`Several firewalls connected by Secure, possibly virtual, net
`WorkS.
`0050. In traditional Intranet configurations, rich multime
`dia communications are Streamed acroSS the network to a
`desktop. The network is almost always the bottleneck as
`typically the file will have to be streamed across the network
`and as Wide Area Networking (WAN) is expensive there is
`typically not enough bandwidth to Support more than just a
`couple of Simultaneously streamed files. SLS allows moving
`compressed Video, rich multimedia files, and large files
`rapidly to multiple desktop or mobile machines. SLS in
`effect creates a new protocol for sharing large files (Such as,
`Video, multimedia, etc) across the network or Intranet. SLS
`moves the bottleneck for video transfer across the Intranet
`from the network to the processor in a personal computer
`(PC).
`0051 One example is using SLS on a laptop to download
`video. The laptop when connected to a LAN may rapidly
`download a file from a local device connected to the LAN
`thus avoiding WAN transfers. This type of peer-to-peer
`transfer is preferable to WAN to LAN transfers because of
`the generally higher Sustained transfer rates. SLS may
`increase performance for a number of different applications
`including Knowledge Management, Corporate Video Com
`munications, eLearning, etc.
`0.052 SLS has implications for Knowledge Manage
`ment-one opportunity is that much codified knowledge
`exists in the form of presentations, text documents, etc. on
`
`individuals’ PC hard drives. In traditional network