we 99:39:35
`
`PC1‘fUS99l0l 988
`
`containers and components as they exit and enter one another, or interact with one another or
`
`any system process or system component within the logical domain of that container, or after
`
`exiting and entering that container, or defining how they interact with that unique gateway.
`
`Gateway’s registers comprise both system-defined and user-defined registers, alterable by
`
`author, duration, location, network-wide history, individual container history and/or interaction
`
`with other containers, gateways, networks or media, and evolve according to that gateway’s
`
`history on a computer network, or according to the network history of events and processes, or
`
`according to that
`
`information component’s interaction with other information containers,
`
`components, system components, network events or processes.
`
`10
`
`
`
`Referring now to FIG. 11, a flow chart of the gateway editor is shown. From the main
`
`title bar input is received from the user selecting “containerize“ or “gateway level" 20100.
`
`
`
`
`
`
`
`:!.l"'!!'-”|!'_".""!'!"'"_ll"'-!!-;:‘PT?’.".IL!.l.'
`
`
`
`
`
`
`
`
`
`20
`
`25
`
`30
`
`When input is received from the user selecting “containeria:e" the system enters the container
`
`editor process 110. When input is received fiom the user selecting “gateway,” the system
`
`shows the gateway levels available 20200. A menu of all possible gateways within the subset
`
`315
`
`and superset scheme of defined multiple hierarchically nested gateways appears. Input
`
`is
`
`received from the user selecting the gateway level 20300. The system searches the gateways
`
`20500 to locate the available gateway templates 20700 and the available gateways 20600- Input
`
`is received from the user selecting the gateway 20610 or gateway level template 20720. The
`
`system goes to the gateway 20620 or to the template 20720. A graphic representation of the
`
`chosen gateway 20630 or template 20730 appears. Input is received from the user to edit 20640
`
`or create a gateway 20740. Once completed, input may be received from the user selecting
`
`"analysis level" from the gateway 200 drop—down menu, to select the level of analysis in a
`
`multi-level analysis sequence to be accomplished at
`
`the local
`
`level by a gateway-resident
`
`analysis engine. The user accesses the container editor to containerize (Fig. 5). Input is received
`
`from the user selecting the registers by clicking on the graphically depicted register, or from a
`
`drop down menu. ). Input is received from the user setting the registers as described elsewhere
`
`in (“container registers”).
`
`Input
`
`is received from the user selecting or defining the rules
`
`governing the interaction of that gateway with transient containers. Input is received from the
`
`user selecting or defining the rules governing the interaction of containers existing within the
`
`logical domain of the container I00 to which that gateway is attached. The user publishes the
`
`gateway (Fig. 5). Input is received from the user selecting "residence" from the main menu bar.
`
`32
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:20)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 431
`
`

`
`WO 99239285
`
`PCTfUS99l01988
`
`). Input is received from the user choosing to leave the gateway where it was created, move it to
`
`container on another drive, directory, computer, or network. If the user chooses "move," a
`
`browse function allows the user to name the new location or browse a list of possible locations.
`
`Once input is received from the user choosing the residence of the gateway, the program
`
`restores the search interface screen.
`
`The invention includes a data reporting means editor 610, and a data collection means
`
`editor 710, Fig- 2 A, as a menu option under the gateway editor 210.
`
`The present invention also includes a gateway process.
`
`Referring now to FIG. 12, a flow chart of the gateway process is shown. A system
`
`10
`
`
`'?.'..'P*
`
`operation, search process or element container or process container is shown in transit 21100
`
`passing through a gateway 21200. The container, operation or process interacts with the
`
`gateway 21300, uploading, downloading and exchanging information with the container,
`
`operation or process. The gateway stores container information 21400 and the container
`
`
`
`
`
`.9-'!!"”!!!i‘“‘J!W11:"15"‘".|!"'-.1‘:-.-:
`
`
`
`
`
`registers are altered 21500. The container registers also interact with the search interface 21600.
`
`E15
`
`The gateways report the register information or make it available for collection by the data
`
`reporting and collection rneans (Fig. 8) operating on the communication device 26 to provide
`
`the information to the analysis engine 21800, which stores 90100, analyzes and instructs the
`
`execution engine 21900, which processes and instructions are also stored 90100 by the
`
`
`
`:l!‘..._|_l‘.I.".
`
`20
`
`25
`
`30
`
`execution engine upon receipt.
`
`All operations in Fig. 12 utilize the communication device 26 whenever necessary
`
`or expeditious.
`
`Referring now to FIG. 13 A, a drawing of nested containers 100 prior to the
`container modification process on a network 201 is shown.
`(Note: The same container
`
`numbering scheme is used in Fig. 13 A, 13 B, 13 C, 13 D and in 2 B.) Information containers
`
`505 and 909, residing within container 908, operating under the rules governing container
`
`interaction within that container 908 downloaded to container 505 and 909 from gateway 9081
`
`upon their entrance to container 908, which rules had been downloaded from execution engine
`
`500 acting under the direction of analysis engine 400, and under the rules programmed into their
`
`own registers 404120, 909120, compare the specified (by those rules) set of registers 404120,
`
`909120, i.e., time and space, and determine a container 404 encapsulated within 505 would be
`
`more appropriately encapsulated within container 909.
`
`33
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:21)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 432
`
`

`
`:1-*-'.-.r1"'!.r
`
`
`
`"H...1!..-
`
`-I’""".'.|~_']-:.-.‘P"'.5F""
`
`r|}I.'.
`
`WO 99239285
`
`PCT.r'US99I0l 988
`
`Referring now to FIG. 13 B a drawing of nested containers during a container
`
`modification process on a network 201 is shown. Container 404 is moved to reside with
`
`container 909. As the container 404 exits container 505, the gateway of container 505, being
`
`gateway 5051, operating under the rules governing container interaction with a gateway 5051
`
`upon egress or egress as programmed in the gateway editor 210 and modified by the execution
`
`engine 500 executing the instructions of the analysis engine 400, or any greater logical analysis
`
`engine 403 providing execution instructions to an execution engine 508 operating in a larger
`
`encompassing container 108 entering through that container’s gateway 208 or an independent
`
`gateway 707, or sub-analysis engine operating at any gateway level, records the register
`
`1o_
`
`information of container 404. The gateway 5051 reports the transaction to the gateway 9081 of
`
`container 908, being the next higher logical container. Gateway 908] holds in gateway storage
`
`205 the information until collected by one or more data collection processes 700, or reported to
`
`one or more data reporting processes 600, serving one or more analysis engines 400 residing
`
`independently on the system 10 or an analysis engine at higher logical container 303. The
`
`-E15
`
`analysis engine 400, comparing reports of user hierarchically graded usage under the operations
`
`of the search engine 320 and the search interface 300, on information container 808 after
`
`receiving reports from the data reporting means of container 404 being moved to container 909
`
`detennines, i.e-, that the number of time and space relevant containers residing within container
`
`909 is sufficient to warrant an action, and directs the execution engine 500 to copy container
`
`909, nested within container 908,
`
`to a third information container 808. As the copy instruction
`
`from execution engine 500 transits the gateway of container 908, the gateway 9081 records the
`
`instruction. The copy instruction interacts with the registers 909120 of container 909 regarding
`
`the rules governing its copying to another location. Once approved by the governing rules of_
`
`registers 909120 appended to container 909, container 909 is duplicated. As the duplicate
`
`container 909 exits the container 908, the gateway records the register information 909120 of
`
`container 909, and the registers 909120 of container 909 are altered by special instructions from
`
`gateway 908] under the rules residing in gateway 9081 regarding ingress and egress and the
`
`rules residing in the registers 909120 of container 909 regarding alteration by gateways upon
`
`ingress and egress. Passing through independent gateway 707, the register information 909120
`
`is recorded, and awaits data collection or reporting 700, 600. As container 909 enters container
`
`808, the gateway records the register infonnation 909120 of container 909, theregisters 909120
`
`.20
`
`25
`
`30
`
`34
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:22)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 433
`
`

`
`W0 99.89285
`
`PCTfUS99!0l 988
`
`of 909 are altered by special instructions from gateway 8031, operating under the rules as
`
`described in the paragraph above, and container 909 takes up residence within container 808.
`
`Referring now to FIG. 13 C, a drawing of nested containers after the container
`
`modification process on a network 201 process is shown. Container 909, now also logically
`residing within container 808, commences to interact with other containers 606 in 808 under the
`
`rules governing container interaction within container 808 as received from gateway 8081 upon
`
`transiting that gateway, and under the rules of registers 606120, 909120 of the interacting
`
`containers 606, 909, operating under the rules as described in the paragraph above. Through
`
`data collection and reporting 700, 600, analysis engine is appraised of containers 909 new
`
`duplicate residence.
`
`I.e., operating under the registers of space relevance, a body of law
`
`10
`
`!!'''.5‘.
`
`
`
`
`
`
`
`
`
`..=".-.r'"1.«-..r.r~.;.!'.'”!!In:11"'12-"’'!.|‘''--.‘.*---::::i!.”‘-3:.
`
`
`
`
`
`
`
`pertaining to Boston Municipal tax law may be housed in a container holding Massachusetts tax
`
`law, but it would be more appropriately located in a container holding Boston tax law, with only
`
`a pointer to that location residing in the Massachusetts tax law container.
`
`In this example, such
`
`an analysis could be accomplished by comparison of zip code information in the space registers,
`
`"315
`
`or logical rules-based analysis, with "state" being a larger set than "city". Or, i.e., operating
`
`under the registers of time relevance, the curve of time relevance for a concert might follow an
`
`ascending curve for the months prior, hit a brief plateau, and then reach a precipitous decline, at
`
`which time certain pertinent information only might be moved to an archival container of city
`
`events or rock concerts of that year.
`
`In this example, once the curve is mapped into a register,
`
`that map would cause an increasing frequency of pointers to that container in other containers or
`
`gateways, or inclusion of that container in other containers, as the analysis engine compares that
`
`curve with increasing user inquiry.
`
`Referring now to Fig. 13 D, a flowchart of the reconstruction process is shown-
`
`Infonnation containers 505 and 909, residing within container 908, operating under the
`
`rules governing container interaction within that container 908 downloaded 888103 to container
`
`505 and 909 from gateway 9081 upon their entrance to container 908, which rules had been
`
`downloaded 888102 from execution engine 500 acting under the direction 888101 of analysis
`
`engine 400, and under the rules programmed into their own registers 404120, 909120, compare
`
`888104 the specified (by those rules) set of registers 404120, 909120, i.e., time and space, and
`
`determine 888105 a container 404 encapsulated within 505 would be more appropriately
`
`encapsulated within container 909.
`
`35
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:23)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 434
`
`
`
`«FL..L'fI.
`
`20
`
`25
`
`30
`
`

`
`W0 99/39235
`
`PC'1‘fUS99I01988
`
`Container 404 is moved 888106 to reside with container 909. As the container 404 exits
`
`container 505, the gateway of container 505, being gateway 5051, operating under the rules
`
`governing container interaction with a gateway 5051 upon egress or egress as programmed in
`
`the gateway editor 210 and modified 888108 by the execution engine 500 executing the
`
`instructions of the analysis engine 400, or any greater logical analysis engine 408 providing
`
`execution instructions 888107 to an execution engine 508 operating in a larger encompassing
`
`container 108 entering through that container’s gateway 208 or an independent gateway 707, or__
`
`sub-analysis engine operating at any gateway level, records 888109 the register information of
`
`container 404, and alters the register information of container 404. The gateway 5051 reports
`
`888110 the transaction to the gateway 9081 of container 908, being the next higher logical
`
`container. Gateway 9081 holds 888111 in gateway storage 205 the information until collected
`
`by one or more data collection processes 700, or reported to one or more data reporting
`
`processes 600, serving 888112 one or more analysis engines 400 residing independently on the
`
`system 10 or an analysis engine at higher logical container 303. The analysis engine 400,
`
`comparing 888114 reports of user hierarchically graded usage on information container 808
`
`under the operations of the search engine 320 and the search interface 300, after receiving
`
`888113 reports from the data reporting means of container 404 being moved to container 909,
`
`determines 888115, i.e., that the number of time and space relevant containers residing within
`
`container 909 is sufficient to warrant an action, and directs 888115 the execution engine 500 to
`
`copy container 909, nested within container 908,
`
`to a third information container 808. As the
`
`copy instruction from execution engine 500 transits the gateway of container 908, the gateway
`
`9081 records 888116 the instruction. The copy instruction interacts 888117 with the registers
`
`909120 of container 909 regarding the rules governing its copying to another location. Once
`
`approved 888118 by the governing rules of registers 909120 appended to container 909,
`
`container 909 is duplicated 888118. As the duplicate container 909 exits the container 908, the
`
`gateway records 888119 the register information 909120 of container 909, and the registers
`909120 of container 909 are altered 888120 by special instructions from gateway 9081 under
`
`the rules residing in gateway 9081 regarding ingress and egress and the rules residing in the
`
`registers 909120 of container 909 regarding alteration by gateways upon ingress and egress.
`
`Passing through independent gateway 70?, the register information 909120 is recorded 888121,
`
`and awaits 888122 data collection or reporting 700, 600. As container 909 enters container 808,
`
`36
`
`10
`
`
`
` -1-r"-'2?"nz::.'!=H.!!'-5-'-..
`
`
`
`
`
`
`_-+".n.r's.=!.1'‘T4.-“=I::'"
`
`iis
`
`
`
`.=!!??.-1.1“-':.
`
`20
`
`25
`
`30
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:24)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 435
`
`

`
`W0 9959285
`
`PCT!US99I0l 988
`
`the gateway records 888123 the register information 909120 of container 909, the registers
`
`909120 of 909 are altered 888124 by special instructions from gateway 8081, operating under
`
`the rules as described in the paragraph above, and container 909 takes up residence 888125
`
`within container 808.
`
`Container 909, now also logically residing (in addition to its original container
`
`residence) within container 808, commences to interact 888126 with other containers 606 in 808
`
`under the rules governing container interaction within container 808 as received from gateway
`
`8081 upon transiting that gateway, and under the rules of registers 606120, 909120 of the
`
`interacting containers 606, 909, operating under the rules as described in the paragraph above.
`
`E‘H:
`:2
`
`Through data collection and reporting 700, 600, analysis engine is appraised 888127 of
`
`
`
`1"r.r.:*"_|!"’=:::='=::.='-.
`
`
`
`
`
`
`11555:.!!557-_..:i‘!!"'!!-I?-;:!l'''!.'
`
`15
`
`20
`
`25
`
`30
`
`container's 909 new duplicate residence.
`
`Referring now to Fig. 14, the screen interface of the container editor is shown- This
`
`interface is a process wherein input is received by the user using the main menu 78 or drop
`
`down menu 1419, or using an input device to “drag and drop” or click, causing the system 10 to
`
`acquire 1409, edit 1410 or create 1411 a file 1407, container 1408 or digital content 01, to
`
`search for 1412, acquire 1413, edit 1414 or create 1415, print 1416, or containerize 1417 a
`
`container 100, to select 1402, (or by clicking on register), search 1403, acquire 1404, edit 1405,
`
`or create a register 1406 to append or detach registers 120 to those containers, to set register
`
`values in those registers 120, to utilize the register editor 125 through 1405 to create new
`
`registers, or to 1418 add, detach, acquire a gateway 200 to append or detach to those containers,
`
`and utilize the gateway editor 210 through 1418. (See detailed description referring to Fig. 5)
`
`Referring now to Fig- 15, the screen interface of the gateway editor is shown. This
`
`interface is a process wherein input is received by the user using the main menu 150] or drop
`
`down menu 1513, or using an input device to “drag and drop" or click, causing the system 10 to
`
`search for 1507, acquire 1508, edit 1509 create 1510, print 151 1 or containerize 1512 gateways,
`and causing the system 10 to establish rules by which an individual gateway governs the
`
`transiting 1502, entering 1503, exiting 1504 of containers and the interaction of containers
`
`within its domain 1505, and external of its domain.l506. (See detailed description referring to
`
`Fig. 11).
`
`Referring now to Fig. 16, the screen interface of the search interface. This interface is a
`
`process wherein input is received by the user using the main menu 1625 or drop down menu
`
`37
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:25)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 436
`
`

`
`WO 99339285
`
`PCT{U899/0 I 988
`
`1624, or using an input device to “drag and drop” or click, or by entering text, causing the
`
`system 10 to select 1615, search for 1616, acquire 1617, edit 1618 create 1619, print 1620,
`
`containerize 1621 (by accessing the container editor 110) or insert 1622 digital search strings
`
`into the search box 1623 in order to submit that string to the search engine 320, or causing the
`
`system 10 to select 1602, search for 1603, acquire 1604, edit 1605, create 1612, containerize
`
`1613 (by accessing the container editor 110), or insert 1614 search keys (templates that
`
`comprise search scope in geographic range, container level, and specific key words or digital
`
`strings), or containerized searches (containers 110), into the search box 1623 in order to submit
`
`that string to the search engine 320 , or causing the system 10 to set a search range by
`
`geographic range 1607, container level 1608, or acquire 1609, edit 1610 or create 1611 a scope
`
`template. (templates that comprise search scope in geographic range and, container level.) (See
`
`detailed description refen-ing to Fig. 6).
`
`Referring now to Fig. 17, a drawing showing, on an input device or computer screen 24,
`
`in any genetic (dashed lines) sofiware appiication program, a drop-down menu link 1403 on a
`
`drop down menu 1402 dropping down from a main menu 1401, and a free-floating button link
`
`1404, is shown. When input is received at 1402 or 1403, the system 10 makes available to the
`
`user the containerization process or container editor 110. When input is received at drop-down
`
`menu link 1405 or a button link 1406, the system 10 makes available to the user the means to
`
`enter and interact with this system 10 or this network 201 in any of their aspects. The interfaces
`
`1403, 1404 show a process wherein input is received causing the system 10 to encapsulate
`
`content or access the container editor 110. The link also allows the user to encapsulate the page
`
`or file on which he is currently working, without selecting content, and if so desired, without
`
`accessing the container editor. The interfaces 1405, 1406 show a process wherein input is
`
`received causing the system 10 to access or interact with the system 10 or the network 201.
`
`The present invention also includes a search engine 320. Once the key word(s), phrase or
`
`digital segment is entered into the search interface 300, or an offered selection chosen on the
`
`menu, it is utilized by the search engine 320 to locate the desired site or data.
`
`The search engine employed may be any industry standard search engine such as Verity
`
`“Topic”, or Personal Library Software, as used in Dow Jones News Retrieval, or Internet search
`
`engines such as Webcrawler, Yahoo, Excite, lnfoseek, Alexa or any Internet search engine, or
`
`
`
`TE‘:5
`
`its
`
`L.F.
`Q:
`
`It]u_!'j"
`
`
`
`_,-'.-1."'!a-!!-«_.rt
`
`‘.]!::.'-I.
`
`20
`
`25
`
`30
`
`38
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:26)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 437
`
`

`
`W0 9989285
`
`PCTIUS99/0| 988
`
`any new engines to be developed capable of searching for and locating digital segments,
`
`whether text, audio, video or graphic.
`
`The present invention also includes an analysis engine 400. Utilizing rules-based
`
`analysis, the analysis engine determines the class of storage medium upon which containers
`
`reside, the subsets and supersets by which and in which containers encompass and reside within
`
`one another,
`
`the routes of access to those containers,
`
`the historically successful search
`
`parameters by which those containers are accessed based upon the identity of the user accessing
`
`the containers, and the grade of access chosen by the user in accessing that container 100.
`
`Utilizing a pre-programmed sequence of compilation, and inductive, deductive and
`
`derivative analysis, the analysis engine manufactures instructions based upon the analysis of the
`
`information submitted by the gateways and the search interface, and submits those instructions
`
`to the appropriate execution engine 500 in order to create new information containers, content
`
`assemblages, storage schemes, access routes, search templates, and gateway instructions, and
`
`others, and to provide informed search options through the search interface to the inquiring user.
`
`The present
`
`invention also includes an engine editor 510,
`
`that provides a system
`
`administrator with a means of editing the operating principles of that search engine, and search
`
`template loading in the search interface 300, a reporting and collection means editor 610, 710,
`
`governing data reporting 600 and data collection 700 at the gateways 200 as defined by the
`
`gateway editor 210 and the register editor 125, a container editor I 10 for creating and modifying
`
`containers and appending registers to containers, a register editor 125 for creating and
`
`modifying container registers and establishing and adjusting the values therein, container
`
`gateways 200 with their own storage 205, information containers 100 for holding information
`
`and container registers for holding information about specific containers and their history on the
`
`network.
`
`
`
`20
`
`25
`
`30
`
`The present invention also includes an execution engine 300. Based upon instructions
`
`received from the analysis engine 400 utilizing the communication device 26, the execution
`
`engine 500 provides search phrases to the search interface 300 based upon initially received
`
`inquiries, relocates containers including their programs, data and registers to other directories,
`
`drives, computers, networks on other classes of storage mediums, i.e., tape drive, optical drive,
`
`CD-ROM, deletes, copies, moves containers to nest within or encompass other containers on
`
`other directories, drives, computers, networks to nest within other containers, alters the class of
`
`39
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:27)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 438
`
`

`
`WO 99/39285
`
`PCTIUS99/01988
`
`
`
`‘yam:«H...
`
`
`storage medium upon which containers reside,
`
`the subsets and supersets by which and in which
`
`containers encompass and reside within one another, the routes of access to those containers,
`
`and the historically successful search parameters by which those containers are accessed based
`
`upon the identity of the user accessing the container and the grade of access chosen by the user
`
`in accessing that container.
`
`The execution engine 400 fulfills the instructions of the analysis search engine 500, to
`
`create new information containers, content sub and superset assemblages, storage schemes,
`
`access routes, search templates, gateway 200 instructions and other system functions. The
`
`execution engine includes an editor 510 that provides a system manager with a means of editing
`
`10
`
`the operating principles of that search engine, governing data reporting, data collection 700,
`
`search template loading, gateway instructions, and other functions.
`
`The present invention also includes flat or relational databases 900, used where, and as
`
`required.
`
`The present invention also includes a communication device 26 supporting all operations
`
`15
`
`on a network wide basis.
`
`The present invention also includes a search engine 300 to locate the desired site or data.
`
`The present
`
`invention also includes databases 900, flat or relational,
`
`to serve the other
`
`components of the system as needed and where needed.
`
`The present invention also includes editors, by which the user may alter the governing
`
`aspects of the system. Editors include, but are not limited to, a container editor 110, a register
`
`editor 125, a gateway editor.2l 0, an engine editor 510, a reporting means editor 610, a search
`
`interface 300, and a collection means editor 710.
`
`The present invention also includes specific screen interfaces for the editors, as described
`
`in Fig. 14, Fig. 15. and Fig. 16.
`
`The present invention also includes a means for this system 10 and network 201 or
`
`container editor 110 to be accessed from a menu or button selection within any program, as
`
`described in Fig. 17.
`
`‘While the present
`
`invention has been described with reference to certain preferred
`
`embodiments, those skilled in the art will recognize that various modifications may be provided.
`
`For example, both analysis engine and execution engine may be duplicated or modified for
`
`distribution at various locations and hierarchical positions in the gateway and container system
`
`40
`
`20
`
`25
`
`30
`
`(cid:51)(cid:72)(cid:87)(cid:76)(cid:87)(cid:76)(cid:82)(cid:81)(cid:72)(cid:85)(cid:86)(cid:3)(cid:55)(cid:90)(cid:76)(cid:87)(cid:87)(cid:72)(cid:85)(cid:15)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:68)(cid:81)(cid:71)(cid:3)(cid:60)(cid:72)(cid:79)(cid:83)(cid:3)(cid:44)(cid:81)(cid:70)(cid:17)(cid:3)(cid:16)(cid:3)(cid:40)(cid:91)(cid:75)(cid:76)(cid:69)(cid:76)(cid:87)(cid:3)(cid:20)(cid:19)(cid:19)(cid:27)(cid:3)(cid:16)(cid:3)(cid:51)(cid:68)(cid:74)(cid:72)(cid:3)(cid:23)(cid:22)(cid:28)
`Petitioners Twitter, Inc. and Yelp Inc. - Exhibit 1008 - Page 439
`
`

`
`.\
`
`WO 99139285
`
`Q
`
`PCTfUS99/0 1 988
`
`throughout
`
`the network and designed to work in concert. Also,
`
`the physical computing
`
`infrastructure may be mainframe, mini, client server or other with various network and
`
`distributed computing designs, including digitally supported or based physical or public media,
`
`and the components of the system 10, as described in Fig.
`
`1 may be physically distributed
`
`through space. Even the contents of a single container may be logically referenced but be
`
`physically distributed through the network and reside at multiple storage locations. The whole
`
`system may be hierarchically nested within other systems to the nth degree. VVhole systems may
`
`also be encapsulated within’ containers. A single container» may also encompass a single physical
`
`media, such as a CD-ROM disk, programmed with the container, gateway and register design.
`
`10.
`
`Gateways may be strategically placed on containers at ingress and/or egress points or may be
`
`placed strategically throughout the system for optimal collection and reporting output and
`
`gateway system control. Also, the loop of gateway data collection and reporting, analysis engine
`
`analysis,
`
`instruction, and gateway modification, and execution engine operations may be
`
`infinitely nested, from the smallest container of two sub-containers to whole networks holding
`
`millions of containers and thousands of levels, with analysis itself nested within the multiple
`
`levels. Gateways may be established at both logical and physical junctures such as a satellite
`
`uplink point. Also, the provision to establish a unique network identity might be designed to
`
`include as of yet unknown computer networks as they arise. The analysis and execution engines
`
`may operate on a rules-based, fuzzy lo