Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6496824B1 Filed: 1999-02-19 Issued: 2002-12-17 Patent Holder: (Original Assignee) Trivnet Ltd     (Current Assignee) Trivnet Ltd Inventor(s): Saar Wilf Title: Session management over a stateless protocol
[FEATURE ID: 1] method	computer method, dynamic method, system, methods, process, methodology, technique	[FEATURE ID: 1] method
[TRANSITIVE ID: 2] monitoring, storing	identifying, processing, providing, determining, using, collecting, capturing	[TRANSITIVE ID: 2] receiving, containing, associating, sending
[FEATURE ID: 3] system, client location, central server, interaction, central server audits, particular interaction type, first interaction, server	client, database, session, network, resource, protocol, computer	[FEATURE ID: 3] stateless protocol
[TRANSITIVE ID: 4] comprising, including	having, includes, comprises, incorporating, containing, involving, compromising	[TRANSITIVE ID: 4] comprising
[FEATURE ID: 5] steps, analysis, information	functions, features, activities, elements, operations, phases, stages	[FEATURE ID: 5] steps, values
[TRANSITIVE ID: 6] providing	creating, establishing, identifying, building, obtaining, receiving, preparing	[TRANSITIVE ID: 6] generating
[FEATURE ID: 7] object, user usage	data, information, characteristics, parameters, communications, objects	[FEATURE ID: 7] identifiers
[FEATURE ID: 8] profile representative	level, metric, parameter	[FEATURE ID: 8] statistical significance value
[FEATURE ID: 9] passing, receiving, response	transmitting, communicating, providing, sending, broadcasting, use, processing	[FEATURE ID: 9] session management
[FEATURE ID: 10] subsequent interaction initiation, profile, audited profile, time component, part	record, message, notification, result, command, communication, state	[FEATURE ID: 10] request, response, reponse
[TRANSITIVE ID: 11] modified, passed	stored, received, supplied, used, created, transmitted, provided	[TRANSITIVE ID: 11] generated, associated
[FEATURE ID: 12] services	results, information, requests	[FEATURE ID: 12] hashes
[FEATURE ID: 13] claim	clair, the claim, embodiment, paragraph, step, fig, para claim	[FEATURE ID: 13] claim
[FEATURE ID: 14] count, creation	summary, value, total, checksum, length, calculation, tally	[FEATURE ID: 14] hash, total significance, total statistical significance
[FEATURE ID: 15] number	sum, percentage, time, extent	[FEATURE ID: 15] significance level
[FEATURE ID: 16] interaction count	identity, response, value, user, key, identifier	[FEATURE ID: 16] user identification
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns of a system [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : providing [TRANSITIVE ID: 6] at least one state object , the object [FEATURE ID: 7] including [TRANSITIVE ID: 4] a profile representative [FEATURE ID: 8] of user usage [FEATURE ID: 7] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 3] ; passing [FEATURE ID: 9] , to a central server [FEATURE ID: 3] , the state object with each subsequent interaction initiation [FEATURE ID: 10] ; and receiving [TRANSITIVE ID: 9] , from the central server , the state object along with the response [FEATURE ID: 9] of the central server ; wherein the profile [FEATURE ID: 10] is modified [TRANSITIVE ID: 11] to reflect the interaction [FEATURE ID: 3] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 3] the state object / profile passed [TRANSITIVE ID: 11] to it , and performs analysis [FEATURE ID: 5] on the audited profile [FEATURE ID: 10] in order to direct services [FEATURE ID: 12] and / or information [FEATURE ID: 5] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 13] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier of a particular interaction type [FEATURE ID: 3] , and the value - field contains a count [FEATURE ID: 14] of the number [FEATURE ID: 15] of occurrences of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 10] detailing the last modification of the interaction count [FEATURE ID: 16] and / or a time component detailing the creation [FEATURE ID: 14] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 3] between the server [FEATURE ID: 3] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 10]		1 . A method [FEATURE ID: 1] for session management [FEATURE ID: 9] over a stateless protocol [FEATURE ID: 3] , the is method comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : receiving [TRANSITIVE ID: 2] a request [FEATURE ID: 10] containing [TRANSITIVE ID: 2] a plurality of identifiers [FEATURE ID: 7] ; generating [TRANSITIVE ID: 6] a hash [FEATURE ID: 14] of at least one of said plurality of identifiers ; if said generated [TRANSITIVE ID: 11] hash is incompatible with previously generated hashes [FEATURE ID: 12] : associating [TRANSITIVE ID: 2] information with said generated hash ; and sending [TRANSITIVE ID: 2] a response [FEATURE ID: 10] based upon information associated [TRANSITIVE ID: 11] with said generated hash ; and if said generated hash is compatible with a previously generated hash , sending a reponse [FEATURE ID: 10] based upon information previously associated with said previously generated hash . 2 . A method according to claim [FEATURE ID: 13] 1 , the method further comprising the steps of : associating a statistical significance value [FEATURE ID: 8] with each of said at least one identifiers ; calculating a total significance [FEATURE ID: 14] for said hash from all of said associated values [FEATURE ID: 5] ; and if said generated hash is incompatible with previously generated hashes : obtaining a user identification [FEATURE ID: 16] ; associating - said user identification with said generated hash ; wherein said steps of sending a response are performed only when said total statistical significance [FEATURE ID: 14] is greater than a predetermined required significance level [FEATURE ID: 15]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6496203B1 Filed: 1998-05-27 Issued: 2002-12-17 Patent Holder: (Original Assignee) Microsoft Corp     (Current Assignee) Microsoft Technology Licensing LLC Inventor(s): Christian Beaumont, Gregory S Lindhorst, Stephen J. Millet, James F. Springfield, Victor A. Stone Title: Standardized and application-independent graphical user interface components implemented with web technology
[FEATURE ID: 1] method, steps, particular interaction type, server, part	process, procedure, technique, methods, service, mechanism, component	[FEATURE ID: 1] host application, steps, corresponding object, means, step, method
[TRANSITIVE ID: 2] monitoring, providing, passing	determining, identifying, generating, controlling, obtaining, storing, maintaining	[TRANSITIVE ID: 2] performing, defining, instantiating
[FEATURE ID: 3] user usage patterns, interaction, services, information	behavior, usage, functions, resources, performance, parameters, capabilities	[FEATURE ID: 3] host application functionality, functionality
[FEATURE ID: 4] system, central server, central server audits, creation, first interaction	client, computer, website, server, display, network, location	[FEATURE ID: 4] client computer, browser, operating system, host application interface, GUI display, host application function interface, web page, user, toolbar, flier computer, selection, computer system
[TRANSITIVE ID: 5] comprising, including, receiving	containing, providing, storing, incorporating, holding, bearing, carrying	[TRANSITIVE ID: 5] including, having
[FEATURE ID: 6] object, response, audited profile	profile, information, state, interaction, interface, account, configuration	[FEATURE ID: 6] appearance
[FEATURE ID: 7] profile representative, order, number, time component, interaction count	parameter, sequence, value, time, response, duration, state	[FEATURE ID: 7] respective size, respective appropriate time
[FEATURE ID: 8] user usage, passed, occurrences	action, events, data, parameters, received, feedback, entry	[FEATURE ID: 8] event handler, GUI parameters input, input
[TRANSITIVE ID: 9] storing	using, implementing, executing, processing, loading	[TRANSITIVE ID: 9] execution
[FEATURE ID: 10] client location	device, processor, controller, server	[FEATURE ID: 10] computer
[FEATURE ID: 11] subsequent interaction initiation, profile, identifier	event, application, object, instance, expression, message, address	[FEATURE ID: 11] associated web page
[TRANSITIVE ID: 12] modified	configured, stored, maintained	[TRANSITIVE ID: 12] being
[FEATURE ID: 13] claim	clair, embodiment, paragraph, step, preceding claim, clause, claimed	[FEATURE ID: 13] claim
[FEATURE ID: 14] least	lea, last, lease, lest, most, at least	[FEATURE ID: 14] least
[FEATURE ID: 15] count	display, function, component	[FEATURE ID: 15] portion
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 1] of : providing [TRANSITIVE ID: 2] at least one state object , the object [FEATURE ID: 6] including [TRANSITIVE ID: 5] a profile representative [FEATURE ID: 7] of user usage [FEATURE ID: 8] ; storing [TRANSITIVE ID: 9] the state object at a client location [FEATURE ID: 10] ; passing [FEATURE ID: 2] , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 11] ; and receiving [TRANSITIVE ID: 5] , from the central server , the state object along with the response [FEATURE ID: 6] of the central server ; wherein the profile [FEATURE ID: 11] is modified [TRANSITIVE ID: 12] to reflect the interaction [FEATURE ID: 3] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 4] the state object / profile passed [TRANSITIVE ID: 8] to it , and performs analysis on the audited profile [FEATURE ID: 6] in order [FEATURE ID: 7] to direct services [FEATURE ID: 3] and / or information [FEATURE ID: 3] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 13] 1 , wherein the profile includes at least [FEATURE ID: 14] one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 11] of a particular interaction type [FEATURE ID: 1] , and the value - field contains a count [FEATURE ID: 15] of the number [FEATURE ID: 7] of occurrences [FEATURE ID: 8] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 7] detailing the last modification of the interaction count [FEATURE ID: 7] and / or a time component detailing the creation [FEATURE ID: 4] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 4] between the server [FEATURE ID: 1] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 1]		1 . A host application [FEATURE ID: 1] for execution [FEATURE ID: 9] on a client computer [FEATURE ID: 4] , the client computer including [TRANSITIVE ID: 5] a browser [FEATURE ID: 4] and an operating system [FEATURE ID: 4] , the browser and the operating system being [TRANSITIVE ID: 12] separate from the host application , the host application including a host application interface [FEATURE ID: 4] and being stored on a computer [FEATURE ID: 10] - readable medium having [TRANSITIVE ID: 5] computer - executable instructions for performing [TRANSITIVE ID: 2] the steps [FEATURE ID: 1] comprising : defining [TRANSITIVE ID: 2] within the host application a respective size [FEATURE ID: 7] and a respective location for each of at least one GUI region on a GUI display [FEATURE ID: 4] ; instantiating [TRANSITIVE ID: 2] from the host application a corresponding browser that points to an associated web page [FEATURE ID: 11] defining a corresponding identifying appearance [FEATURE ID: 6] for each GUI region ; providing host application functionality [FEATURE ID: 3] corresponding to at least one of the at least one GUI region by calling from the corresponding browser a corresponding object [FEATURE ID: 1] exposed by the host application via the host application function interface [FEATURE ID: 4] ; determining a respective appropriate time [FEATURE ID: 7] for the corresponding functionality [FEATURE ID: 3] of each GUI region with a corresponding event handler [FEATURE ID: 8] within the corresponding browser for each GUI region ; executing the corresponding functionality at the respective appropriate time for each GUI region ; and wherein at least one of the at least one GUI region includes a plurality of subregions , each subregion having at least one of an identifying appearance and a corresponding functionality defined by the associated web page [FEATURE ID: 4] of said GUI region . 2 . The computer - readable medium of claim [FEATURE ID: 13] 1 , wherein the corresponding event handler within the corresponding browser of said GUI region includes a means [FEATURE ID: 1] for detecting that said GUI region has been selected by a user [FEATURE ID: 4] . 3 . The computer - readable medium of claim 1 , wherein said at least one GUI region defines at least [FEATURE ID: 14] a portion [FEATURE ID: 15] of a toolbar [FEATURE ID: 4] provided by the host application . 4 . The computer - readable medium of claim 1 , having flier computer [FEATURE ID: 4] - executable instructions for performing the step [FEATURE ID: 1] of : accepting GUI parameters input [FEATURE ID: 8] by a user for determining the respective size and the respective location for each GUI region ; and accepting as input [FEATURE ID: 8] by the user a selection [FEATURE ID: 4] of the associated web page for each of the at least one GUI region . 5 . In a computer system [FEATURE ID: 4] having a client computer that executes a host application and that includes a GUI display , a method [FEATURE ID: 1]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6490602B1 Filed: 1999-01-15 Issued: 2002-12-03 Patent Holder: (Original Assignee) Wish List Com Inc     (Current Assignee) Zarbana Digital Fund LLC Inventor(s): Keith M. Kraemer Title: Method and apparatus for providing enhanced functionality to product webpages
[FEATURE ID: 1] method, steps	methods, process, step, procedure, means, system method, first method	[FEATURE ID: 1] method
[TRANSITIVE ID: 2] monitoring, including, storing, passing, receiving	providing, processing, generating, presenting, collecting, capturing, obtaining	[TRANSITIVE ID: 2] adding, receiving
[FEATURE ID: 3] user usage patterns	metadata, characteristics, information, resources, content, parameters, functionality	[FEATURE ID: 3] code, data indicative
[FEATURE ID: 4] system, client location, central server, central server audits, services, particular interaction type, field further	client, database, second, first, computer, product, network	[FEATURE ID: 4] functionality toolbar, first product web page, first independent vendor server, first resource, second product web page, second user, second independent vendor server, first independent server, second independent server, second business entity, third business entity, second resource, list
[TRANSITIVE ID: 5] comprising	including, involving, featuring, containing, having, includes, comprises	[TRANSITIVE ID: 5] comprising, lacking
[TRANSITIVE ID: 6] providing	acquiring, capturing, obtaining, receiving, identifying	[TRANSITIVE ID: 6] retrieving
[FEATURE ID: 7] object	data, information, objects	[FEATURE ID: 7] URL information
[FEATURE ID: 8] user usage, audited profile, information	content, data, html, advertisements, commands, instructions, parameters	[FEATURE ID: 8] preexisting product web pages, location information, structural information, frameset information
[FEATURE ID: 9] subsequent interaction initiation, identifier, count, first interaction	query, message, call, command, link, entry, transaction	[FEATURE ID: 9] request, first broken reference, purchase command, register command, activation
[FEATURE ID: 10] response	location, address, signature, identification	[FEATURE ID: 10] web page elements
[FEATURE ID: 11] profile, time component, part	parameter, message, result, response, state, status, data	[FEATURE ID: 11] command
[TRANSITIVE ID: 12] modified	altered, revised, generated, created, configured, changed, embedded	[TRANSITIVE ID: 12] enhanced, associated, modified
[TRANSITIVE ID: 13] reflect	modify, include, define, identify	[TRANSITIVE ID: 13] create
[FEATURE ID: 14] interaction, order	relationship, real time, addition, correlation, association, parallel	[FEATURE ID: 14] response
[FEATURE ID: 15] claim	clair, preceding claim, figure, item, claims claim, clam, claimed	[FEATURE ID: 15] claim
[FEATURE ID: 16] interaction count	profile, data, table, number	[FEATURE ID: 16] database
[FEATURE ID: 17] server	users, customer, client, agent, system, network, application	[FEATURE ID: 17] intercept server, first user
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 1] of : providing [TRANSITIVE ID: 6] at least one state object , the object [FEATURE ID: 7] including [TRANSITIVE ID: 2] a profile representative of user usage [FEATURE ID: 8] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 4] ; passing [FEATURE ID: 2] , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 9] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 10] of the central server ; wherein the profile [FEATURE ID: 11] is modified [TRANSITIVE ID: 12] to reflect [TRANSITIVE ID: 13] the interaction [FEATURE ID: 14] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 4] the state object / profile passed to it , and performs analysis on the audited profile [FEATURE ID: 8] in order [FEATURE ID: 14] to direct services [FEATURE ID: 4] and / or information [FEATURE ID: 8] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 15] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 9] of a particular interaction type [FEATURE ID: 4] , and the value - field contains a count [FEATURE ID: 9] of the number of occurrences of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further [FEATURE ID: 4] contains a time component [FEATURE ID: 11] detailing the last modification of the interaction count [FEATURE ID: 16] and / or a time component detailing the creation of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 9] between the server [FEATURE ID: 17] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 11]		1 . A method [FEATURE ID: 1] of adding [TRANSITIVE ID: 2] an enhanced [TRANSITIVE ID: 12] functionality toolbar [FEATURE ID: 4] to preexisting product web pages [FEATURE ID: 8] at an intercept server [FEATURE ID: 17] , the method comprising [TRANSITIVE ID: 5] : receiving [TRANSITIVE ID: 2] a request [FEATURE ID: 9] for a first product web page [FEATURE ID: 4] at the intercept server from a first user [FEATURE ID: 17] , the first product web page being associated [TRANSITIVE ID: 12] with a first product and a first independent vendor server [FEATURE ID: 4] , the first product web page lacking [TRANSITIVE ID: 5] the enhanced functionality toolbar ; retrieving [TRANSITIVE ID: 6] the first product web page from the first independent vendor server to the intercept server ; adding the enhanced functionality toolbar to the first product web page at the intercept server to create [TRANSITIVE ID: 13] a modified [TRANSITIVE ID: 12] first product web page , the enhanced functionality toolbar including a command [FEATURE ID: 11] associated with the first product ; adjusting a first reference in the first product web page to create code [FEATURE ID: 3] in the modified first product web page that can be served from the intercept server without a first broken reference [FEATURE ID: 9] , the first reference pointing to a first resource [FEATURE ID: 4] on the first independent vendor server ; presenting the modified first product web page from the intercept server to the first user ; receiving a request for a second product web page [FEATURE ID: 4] at the intercept server from a second user [FEATURE ID: 4] , the second product web page being associated with a second product and a second independent vendor server [FEATURE ID: 4] , the second product web page lacking the enhanced functionality toolbar , the first independent server [FEATURE ID: 4] being administered by a first business entity , the second independent server [FEATURE ID: 4] being administered by a second business entity [FEATURE ID: 4] , the intercept server being administered by a third business entity [FEATURE ID: 4] , the first business entity being different than the second business entity , the first business entity being different than the third business entity , the second business entity being different than the third business entity ; retrieving the second product web page from the second independent vendor server to the intercept server ; adding the enhanced functionality toolbar to the second product web page at the intercept server to create a modified second product web page , the enhanced functionality toolbar including a command associated with the second product ; adjusting a second reference in the second product web page to create code in the modified second product web page that can be served from the intercept server without a second broken reference , the second reference pointing to a second resource [FEATURE ID: 4] on the second independent vendor server ; presenting the modified second product web page from the intercept server to the second user . 2 . A method as defined in claim [FEATURE ID: 15] 1 , wherein the command associated with the first product is a purchase command [FEATURE ID: 9] . 3 . A method as defined in claim 1 , wherein the command associated with the first product is a register command [FEATURE ID: 9] . 4 . A method as defined in claim 3 , further comprising adding data indicative [FEATURE ID: 3] of the first product to a list [FEATURE ID: 4] associated with the first user in response [FEATURE ID: 14] to activation [FEATURE ID: 9] of the register command . 5 . A method as defined in claim 1 , wherein adding the enhanced functionality toolbar to the first product web page comprises extracting location information [FEATURE ID: 8] from the first product web page . 6 . A method as defined in claim 1 , wherein adding the enhanced functionality toolbar to the first product web page comprises extracting structural information [FEATURE ID: 8] from the first product web page . 7 . A method as defined in claim 1 , wherein adding the enhanced functionality toolbar to the first product web page comprises extracting URL information [FEATURE ID: 7] . 8 . A method as defined in claim 7 , wherein adding the enhanced functionality toolbar to the first product web page comprises extracting frameset information [FEATURE ID: 8] . 9 . A method as defined in claim 1 , further comprising identifying the first product web page by comparing the web page elements [FEATURE ID: 10] of the first product web page to a database [FEATURE ID: 16]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6490601B1 Filed: 1999-01-15 Issued: 2002-12-03 Patent Holder: (Original Assignee) InfoSpace Inc     (Current Assignee) Liberty Peak Ventures LLC Inventor(s): Matthew A. Markus, Erick M. Herrarte Title: Server for enabling the automatic insertion of data into electronic forms on a user computer
[FEATURE ID: 1] method, steps, part	means, procedure, methods, process, mechanism, step, technique	[FEATURE ID: 1] method, shippable software module suitable
[TRANSITIVE ID: 2] monitoring, providing, including, receiving	storing, identifying, creating, defining, maintaining, generating, obtaining	[TRANSITIVE ID: 2] constructing, receiving, retrieving, containing
[FEATURE ID: 3] system, central server, central server audits, server	client, computer, database, network, website, customer, remote	[FEATURE ID: 3] shippable software module, personal information server suitable, remote computer, personal information server, particular user, form, server
[TRANSITIVE ID: 4] comprising	including, having, includes, involving, comprises, by, containing	[TRANSITIVE ID: 4] comprising
[FEATURE ID: 5] profile representative	profile, specification, pattern, history	[FEATURE ID: 5] preference condition
[FEATURE ID: 6] user usage, audited profile, occurrences	data, parameters, transactions, information, values, usage, events	[FEATURE ID: 6] fields, use descriptors, negotiation objects
[TRANSITIVE ID: 7] storing	editing, providing, updating, receiving, manipulating	[TRANSITIVE ID: 7] inserting
[FEATURE ID: 8] client location	memory, database, server, computer	[FEATURE ID: 8] pre-named
[FEATURE ID: 9] passing	transmitting, sending, issuing, requesting	[FEATURE ID: 9] remote computer issues
[FEATURE ID: 10] subsequent interaction initiation, response, first interaction	message, transmission, query, application, use, link, operation	[FEATURE ID: 10] execution, request, pre-named field, insertion, user identifier
[FEATURE ID: 11] profile	file, database, template, document, object, field, spreadsheet	[FEATURE ID: 11] electronic form, form mapping, raw data file, form identifier
[TRANSITIVE ID: 12] modified, passed	stored, transmitted, accessible, established, provided, maintained, updated	[TRANSITIVE ID: 12] associated
[FEATURE ID: 13] interaction	differences, interactions, mapping, relationship	[FEATURE ID: 13] associations
[FEATURE ID: 14] services, information, interaction count	data, messages, parameters, objects, records, applications, documents	[FEATURE ID: 14] data strings, mapping, raw data files
[FEATURE ID: 15] claim	statement, clause, preceding claim, claims claim, figure, clair, clam	[FEATURE ID: 15] claim
[FEATURE ID: 16] field pair, field further	value, file, set, pair, field, record, entry	[FEATURE ID: 16] data string
[FEATURE ID: 17] particular interaction type	class, pattern, field, method	[FEATURE ID: 17] type
[FEATURE ID: 18] time component	record, variable, value, data, parameter	[FEATURE ID: 18] field
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns of a system [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 1] of : providing [TRANSITIVE ID: 2] at least one state object , the object including [TRANSITIVE ID: 2] a profile representative [FEATURE ID: 5] of user usage [FEATURE ID: 6] ; storing [TRANSITIVE ID: 7] the state object at a client location [FEATURE ID: 8] ; passing [FEATURE ID: 9] , to a central server [FEATURE ID: 3] , the state object with each subsequent interaction initiation [FEATURE ID: 10] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 10] of the central server ; wherein the profile [FEATURE ID: 11] is modified [TRANSITIVE ID: 12] to reflect the interaction [FEATURE ID: 13] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 3] the state object / profile passed [TRANSITIVE ID: 12] to it , and performs analysis on the audited profile [FEATURE ID: 6] in order to direct services [FEATURE ID: 14] and / or information [FEATURE ID: 14] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 15] 1 , wherein the profile includes at least one key and value - field pair [FEATURE ID: 16] . 3 . A method as claimed in claim 2 , wherein the key is an identifier of a particular interaction type [FEATURE ID: 17] , and the value - field contains a count of the number of occurrences [FEATURE ID: 6] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further [FEATURE ID: 16] contains a time component [FEATURE ID: 18] detailing the last modification of the interaction count [FEATURE ID: 14] and / or a time component detailing the creation of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 10] between the server [FEATURE ID: 3] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 1]		1 . A method [FEATURE ID: 1] for constructing [TRANSITIVE ID: 2] a shippable software module [FEATURE ID: 3] on a personal information server suitable [FEATURE ID: 3] for execution [FEATURE ID: 10] on a remote computer [FEATURE ID: 3] for inserting [TRANSITIVE ID: 7] data strings [FEATURE ID: 14] into an electronic form [FEATURE ID: 11] , the method comprising [TRANSITIVE ID: 4] : receiving [TRANSITIVE ID: 2] a request [FEATURE ID: 10] from a remote computer for a shippable software module suitable [FEATURE ID: 1] for execution on the remote computer for inserting data strings into the electronic form ; retrieving [TRANSITIVE ID: 2] a form mapping [FEATURE ID: 11] containing [TRANSITIVE ID: 2] a plurality of associations [FEATURE ID: 13] between fields [FEATURE ID: 6] in the electronic form and pre-named [TRANSITIVE ID: 8] fields on the personal information server [FEATURE ID: 3] , the mapping [FEATURE ID: 14] being associated [TRANSITIVE ID: 12] with the electronic form ; retrieving a raw data file [FEATURE ID: 11] containing data strings from a plurality of raw data files [FEATURE ID: 14] , each data string [FEATURE ID: 16] corresponding to a pre-named field [FEATURE ID: 10] and the raw data file being associated with a particular user [FEATURE ID: 3] ; dynamically constructing a shippable software module suitable for execution on the remote computer for inserting data strings into an electronic form utilizing the form mapping and the raw data file and comparing an intended - practice condition associated with each field [FEATURE ID: 18] in the electronic form as determined by a form [FEATURE ID: 3] - originating server [FEATURE ID: 3] , with a use - preference condition [FEATURE ID: 5] associated with each pre-named field as determined by the particular user ; and transmitting the shippable software module to the remote computer . 2 . The method as recited in claim [FEATURE ID: 15] 1 further comprising attaching a data string from the raw data file corresponding to a pre-named field to the shippable software module for insertion [FEATURE ID: 10] into the field in the electronic form when the intended - practice condition of the field is consistent with the use - preference condition of the pre-named field . 3 . The method as recited in claim 1 wherein receiving a request from a remote computer further comprises receiving a user identifier [FEATURE ID: 10] associated with the particular user and a form identifier [FEATURE ID: 11] associated with the electronic form , and wherein the remote computer issues [FEATURE ID: 9] the request when the electronic form is downloaded by the particular user . 4 . The method as recited in claim 1 further comprising declining to attach a data string from the raw data file corresponding to a pre-named field to the shippable software module for insertion into the field in the electronic form when the intended - practice condition of the field is inconsistent with the use - preference condition of the pre-named field . 5 . The method as recited in claim 4 wherein the intended - practice condition and the use - preference condition are collections of type [FEATURE ID: 17] - of - use descriptors [FEATURE ID: 6] . 6 . The method as recited in claim 1 wherein dynamically constructing a shippable software module suitable for execution on the remote computer for inserting data strings into an electronic form utilizing the form mapping and the raw data file further comprises examining a plurality of negotiation objects [FEATURE ID: 6]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US20020178119A1 Filed: 2001-05-24 Issued: 2002-11-28 Patent Holder: (Original Assignee) International Business Machines Corp     (Current Assignee) International Business Machines Corp Inventor(s): Patricia Griffin, Gary Cole, Gregory Wilson Title: Method and system for a role-based access control model with active roles
[FEATURE ID: 1] method, client location	system, computer, methodology, device, system method, methods, process	[FEATURE ID: 1] method
[TRANSITIVE ID: 2] monitoring, providing, including, storing, passing, receiving	establishing, identifying, processing, defining, determining, generating, maintaining	[TRANSITIVE ID: 2] controlling, associating, authorizing, evaluating
[FEATURE ID: 3] user usage patterns, information	resources, characteristics, properties, privileges, attributes, features, rights	[FEATURE ID: 3] access rights, capabilities, principals, access conditions, role filters
[FEATURE ID: 4] system, central server, central server audits, interaction count, server	property, domain, user, client, database, profile, policy	[FEATURE ID: 4] requesting, resource, computer system, role, role filter, resource type, right, type
[TRANSITIVE ID: 5] comprising	including, having, includes, involving, comprises, by, containing	[TRANSITIVE ID: 5] comprising
[FEATURE ID: 6] steps	features, characteristics, elements, functions	[FEATURE ID: 6] resources
[FEATURE ID: 7] profile representative, field further, time component	parameter, list, value, field, type, history, counter	[FEATURE ID: 7] attribute
[FEATURE ID: 8] user usage, interaction, audited profile, occurrences	communications, interactions, activity, content, data, transactions, information	[FEATURE ID: 8] access
[FEATURE ID: 9] subsequent interaction initiation, profile, order, identifier, creation, first interaction	event, request, entry, access, attribute, authorization, instruction	[FEATURE ID: 9] association, access constraint, access type, notification, update, instance, response, determination
[FEATURE ID: 10] response	capabilities, configuration, status, property, policy, credential, context	[FEATURE ID: 10] access condition, filterCapabilities list
[TRANSITIVE ID: 11] modified	configured, established, maintained	[TRANSITIVE ID: 11] associated
[TRANSITIVE ID: 12] reflect	define, include, indicate, identify	[TRANSITIVE ID: 12] determine
[FEATURE ID: 13] analysis	filtering, processes, searches, checks	[FEATURE ID: 13] capability filters
[FEATURE ID: 14] services	resources, users, credentials, domains, privileges, access, permits	[FEATURE ID: 14] rights, roles
[FEATURE ID: 15] claim	statement, clause, para claim, preceding claim, the claim, figure, item	[FEATURE ID: 15] claim
[FEATURE ID: 16] particular interaction type, part	function, modality, resource, property, status, component, feature	[FEATURE ID: 16] capability
[FEATURE ID: 17] count, number	total, quantity, series, history, percentage, plurality, sum	[FEATURE ID: 17] set
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 6] of : providing [TRANSITIVE ID: 2] at least one state object , the object including [TRANSITIVE ID: 2] a profile representative [FEATURE ID: 7] of user usage [FEATURE ID: 8] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 1] ; passing [FEATURE ID: 2] , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 9] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 10] of the central server ; wherein the profile [FEATURE ID: 9] is modified [TRANSITIVE ID: 11] to reflect [TRANSITIVE ID: 12] the interaction [FEATURE ID: 8] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 4] the state object / profile passed to it , and performs analysis [FEATURE ID: 13] on the audited profile [FEATURE ID: 8] in order [FEATURE ID: 9] to direct services [FEATURE ID: 14] and / or information [FEATURE ID: 3] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 15] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 9] of a particular interaction type [FEATURE ID: 16] , and the value - field contains a count [FEATURE ID: 17] of the number [FEATURE ID: 17] of occurrences [FEATURE ID: 8] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further [FEATURE ID: 7] contains a time component [FEATURE ID: 7] detailing the last modification of the interaction count [FEATURE ID: 4] and / or a time component detailing the creation [FEATURE ID: 9] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 9] between the server [FEATURE ID: 4] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 16]		1 . A method [FEATURE ID: 1] for controlling [TRANSITIVE ID: 2] access rights [FEATURE ID: 3] of a requesting [TRANSITIVE ID: 4] principal to a protected resource [FEATURE ID: 4] in a computer system [FEATURE ID: 4] , wherein a principal is associated [TRANSITIVE ID: 11] with at least one role [FEATURE ID: 4] , the method comprising [TRANSITIVE ID: 5] : associating [TRANSITIVE ID: 2] a role filter [FEATURE ID: 4] with a role ; associating a set [FEATURE ID: 17] of one or more capabilities [FEATURE ID: 3] with the role ; associating a capability filter with a capability [FEATURE ID: 16] in the set of one or more capabilities ; and authorizing [TRANSITIVE ID: 2] access [FEATURE ID: 8] for the requesting principal to the protected resource based on an association [FEATURE ID: 9] between the requesting principal and the role and based on an association between the protected resource and a capability of the role . 2 . The method of claim [FEATURE ID: 15] 1 further comprising : evaluating [TRANSITIVE ID: 2] the role filter to determine [TRANSITIVE ID: 12] a set of one or more principals [FEATURE ID: 3] to be associated with the role ; and evaluating the capability filter to determine a set of one or more resources [FEATURE ID: 6] to be associated with the capability . 3 . The method of claim 1 further comprising : associating a resource type [FEATURE ID: 4] with each capability in the set of one or more capabilities , wherein each capability defines access to at least one resource of the resource type . 4 . The method of claim 1 further comprising : associating a set of one or more access conditions [FEATURE ID: 3] with each capability in the set of one or more capabilities , wherein each access condition [FEATURE ID: 10] defines an access constraint [FEATURE ID: 9] against authorizing access for the requesting principal to the protected resource . 5 . The method of claim 4 further comprising : associating a set of one or more rights [FEATURE ID: 14] with each access condition in the set of one or more access conditions , wherein each right [FEATURE ID: 4] defines an access type [FEATURE ID: 9] for authorized access for the requesting principal to the protected resource . 6 . The method of claim 1 further comprising : associating a filterRoles list with the requesting principal , wherein the filterRoles list is a multivalued attribute [FEATURE ID: 7] containing a set of one or more roles [FEATURE ID: 14] ; associating a filterMembers list with the role , wherein the filterMembers list is a multivalued attribute containing a set of one or more principals ; adding the role to the filterRoles list associated with the requesting principal if the requesting principal is added to the filterMembers list associated with the role ; and adding the requesting principal to the filterMembers list associated with the role if the role is added to the filterRole list associated with the requesting principal . 7 . The method of claim 1 further comprising : associating a filterCapabilities list [FEATURE ID: 10] with a resource , wherein the filterCapabilities list is a multivalued attribute containing a set of one or more capabilities ; associating a filterTargets list with a capability , wherein the filterTargets list is a multivalued attribute containing a set of one or more resources ; adding the capability to the filterCapabilities list associated with the resource if the resource is added to the filterTargets list associated with the capability ; and adding the resource to the filterTargets list associated with the capability if the capability is added to the filterCapabilities list associated with the resource . 8 . The method of claim 1 further comprising : receiving notification [FEATURE ID: 9] of an update [FEATURE ID: 9] to an instance [FEATURE ID: 9] , wherein the instance has a type [FEATURE ID: 4] selecting from the group of “ principal ” , “ resource ” , “ capability ” , or “ role ” ; determining the type of the instance ; searching for capabilities with a resource type that matches the type of the instance ; and running capability filters [FEATURE ID: 13] of matched capabilities against the instance . 9 . The method of claim 8 further comprising : in response [FEATURE ID: 9] to a determination [FEATURE ID: 9] that the type of the instance is “ principal ” , running all role filters [FEATURE ID: 3]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6487663B1 Filed: 1998-10-19 Issued: 2002-11-26 Patent Holder: (Original Assignee) RealNetworks Inc     (Current Assignee) Intel Corp Inventor(s): Mysore Y. Jaisimha, Phillip L. Barrett Title: System and method for regulating the transmission of media data
[FEATURE ID: 1] method	system method, system, procedure, technique, methodology, first method, process	[FEATURE ID: 1] method
[TRANSITIVE ID: 2] monitoring, comprising, providing, including, storing, receiving	identifying, defining, encoding, having, containing, using, determining	[TRANSITIVE ID: 2] comprising, including, representing, causing
[FEATURE ID: 3] user usage patterns	parameters, the, uses, characteristics	[FEATURE ID: 3] types
[FEATURE ID: 4] system, central server, central server audits	server, database, medium, client, user, media, location	[FEATURE ID: 4] computer, media storage accessible, media server, network, media player, media player responsive
[FEATURE ID: 5] steps, analysis, information	functions, features, operations, components, processes, actions, sequential steps	[FEATURE ID: 5] steps
[FEATURE ID: 6] profile representative, value, particular interaction type, number, interaction count, part	parameter, profile, rate, state, pattern, field, message	[FEATURE ID: 6] value, type
[FEATURE ID: 7] user usage	the, content, information	[FEATURE ID: 7] data
[FEATURE ID: 8] client location	computer, server, time, storage, media, device, memory	[FEATURE ID: 8] system, local storage
[FEATURE ID: 9] passing	streaming, sending, transmitting	[FEATURE ID: 9] transmission
[FEATURE ID: 10] subsequent interaction initiation, response, profile, identifier	transmission, command, message, address, query, entry, call	[FEATURE ID: 10] access, access code, request, first request, second request, user input, determination
[TRANSITIVE ID: 11] modified, passed	recorded, generated, provided, received, communicated, written, used	[TRANSITIVE ID: 11] stored, transmitted
[FEATURE ID: 12] order, creation	use, parallel, according, association, return, combination, connection	[FEATURE ID: 12] accordance, response
[FEATURE ID: 13] services	access, information, data	[FEATURE ID: 13] access code bits
[FEATURE ID: 14] claim	statement, clause, para claim, preceding claim, the claim, item, figure	[FEATURE ID: 14] claim
[FEATURE ID: 15] time component	tag, data, field, flag, code	[FEATURE ID: 15] header
[FEATURE ID: 16] first interaction	transmission, transfer, session, protocol, synchronization, connection	[FEATURE ID: 16] real time transmission protocol, streaming transmission access
[FEATURE ID: 17] server	system, network, servers	[FEATURE ID: 17] media server responsive
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 2] the steps [FEATURE ID: 5] of : providing [TRANSITIVE ID: 2] at least one state object , the object including [TRANSITIVE ID: 2] a profile representative [FEATURE ID: 6] of user usage [FEATURE ID: 7] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 8] ; passing [FEATURE ID: 9] , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 10] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 10] of the central server ; wherein the profile [FEATURE ID: 10] is modified [TRANSITIVE ID: 11] to reflect the interaction between the client location and the central server ; and wherein the central server audits [FEATURE ID: 4] the state object / profile passed [TRANSITIVE ID: 11] to it , and performs analysis [FEATURE ID: 5] on the audited profile in order [FEATURE ID: 12] to direct services [FEATURE ID: 13] and / or information [FEATURE ID: 5] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 14] 1 , wherein the profile includes at least one key and value [FEATURE ID: 6] - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 10] of a particular interaction type [FEATURE ID: 6] , and the value - field contains a count of the number [FEATURE ID: 6] of occurrences of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 15] detailing the last modification of the interaction count [FEATURE ID: 6] and / or a time component detailing the creation [FEATURE ID: 12] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 16] between the server [FEATURE ID: 17] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 6]		1 . An access [FEATURE ID: 10] coded media file stored [TRANSITIVE ID: 11] on a computer [FEATURE ID: 4] - readable medium , comprising [TRANSITIVE ID: 2] : media data ; and a header [FEATURE ID: 15] including [TRANSITIVE ID: 2] access code bits [FEATURE ID: 13] , said access code bits representing [TRANSITIVE ID: 2] a value [FEATURE ID: 6] causing [TRANSITIVE ID: 2] the media data to be transmitted [TRANSITIVE ID: 11] in accordance [FEATURE ID: 12] with at least one transmission protocol . 2 . The access coded media file of claim [FEATURE ID: 14] 1 wherein said access code bits are encrypted and wherein said value is determined by decrypting said access code bits . 3 . The access coded media file as described in claim 1 , wherein said at least one transmission protocol includes a streaming protocol . 4 . The access coded media file as described in claim 1 , wherein said at least one transmission protocol includes a faster than real time transmission protocol [FEATURE ID: 16] . 5 . An access coded media file stored on a computer - readable medium , comprising : media data ; and a header including access code bits , said access code bits representing a value causing the media data to be transmitted in accordance with at least one transmission protocol , said access code bits representing a value indicating that the media data may not be transmitted in accordance with at least one transmission protocol . 6 . A method [FEATURE ID: 1] for regulating types [FEATURE ID: 3] of access to a media file , the method comprising the steps [FEATURE ID: 5] of : placing an access code [FEATURE ID: 10] in a media file , said media file stored in a media storage accessible [FEATURE ID: 4] by a media server [FEATURE ID: 4] , said media server connected to a network [FEATURE ID: 4] , said access code indicating that data [FEATURE ID: 7] in the media file may be transmitted in accordance with at least one permitted transmission protocol ; requesting said media file with a media player [FEATURE ID: 4] , said media player connected to said network , said request [FEATURE ID: 10] specifying an intended transmission protocol to use in transmitting said media file over said network in response [FEATURE ID: 12] to said request ; transmitting said access code to said media player with said media server ; and checking said access code with said media player to determine whether said intended transmission protocol is one of said at least one permitted transmission protocols . 7 . A method for regulating types of access to a media file , the method comprising the steps of : placing an access code in a media file , said media file stored in a media storage accessible by a media server , said media server connected to a network , said access code indicating that data in the media file may be transmitted in accordance with at least one permitted transmission protocol ; requesting said media file with a media player , said media player connected to said network , said request specifying an intended transmission protocol to use in transmitting said media file over said network in response to said request ; transmitting said access code to said media player with said media server ; checking said access code with said media player to determine whether said intended transmission protocol is one of said at least one permitted transmission protocols ; encrypting said access code within said media file ; and decrypting said access code with said media player to perform said checking . 8 . A system [FEATURE ID: 8] for regulating the transmission [FEATURE ID: 9] of media data , the system comprising : a media file having media data and a header , said header including an access code corresponding to at least one permitted type [FEATURE ID: 6] of access to said media file ; a media server connected to a network and to media storage , said media file stored on said media storage , said media server responsive [FEATURE ID: 17] to a first request [FEATURE ID: 10] for said media file by transmitting said header , said media server responsive to a second request [FEATURE ID: 10] by transmitting said media data in accordance with one of said at least one permitted type of access ; and a media player connected to said network , said media player responsive [FEATURE ID: 4] to user input [FEATURE ID: 10] to transmit said first request to said media server , said media player receiving said header and extracting said access code from said header , said media player determining from said access code that said media file is enabled for one of said at least one permitted type of access , said media player transmitting said second request to said media server upon said determination [FEATURE ID: 10] . 9 . The system of claim 8 wherein said first request specifies said one of at least one permitted type of access . 10 . The system of claim 8 wherein said one of at least one permitted type of access is a streaming transmission access [FEATURE ID: 16] . 11 . The system of claim 8 wherein said one of at least one permitted type of access is a faster than real time reliable transmission access . 12 . The system of claim 10 wherein said permitted type of access includes recording media data to local storage [FEATURE ID: 8]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6487566B1 Filed: 1998-10-05 Issued: 2002-11-26 Patent Holder: (Original Assignee) International Business Machines Corp     (Current Assignee) LinkedIn Corp Inventor(s): Neelakantan Sundaresan Title: Transforming documents using pattern matching and a replacement language
[FEATURE ID: 1] method, information, part	step, process, procedure, means, methods, operation, features	[FEATURE ID: 1] method, steps
[TRANSITIVE ID: 2] monitoring, providing, including, storing, analysis	generating, defining, processing, establishing, implementing, identifying, executing	[TRANSITIVE ID: 2] transforming, creating
[FEATURE ID: 3] user usage patterns	activities, resources, parameters, services, operations	[FEATURE ID: 3] functions
[FEATURE ID: 4] system, object, client location, central server, audited profile, particular interaction type, time component, interaction count, server	database, data, content, network, profile, program, client	[FEATURE ID: 4] computer, document, first programming language, XML document
[TRANSITIVE ID: 5] comprising	with, through, by, including, employing, wherein, performing	[TRANSITIVE ID: 5] comprising, using
[FEATURE ID: 6] steps, occurrences	functions, applications, methods, programs, conversions, rules, operations	[FEATURE ID: 6] transformations, actions, step, class specifications, computer programs, Java objects, components, replacement components, action components
[FEATURE ID: 7] profile representative, count	definition, pattern, description, document, template, specification, function	[FEATURE ID: 7] rules specification, language, condition, target pattern, schema structure, schema, regular expression language
[FEATURE ID: 8] user usage	data, patterns, content	[FEATURE ID: 8] pattern
[FEATURE ID: 9] subsequent interaction initiation, response, identifier	request, entry, association, address, identification, item, element	[FEATURE ID: 9] action part
[FEATURE ID: 10] profile	file, database, program	[FEATURE ID: 10] group
[TRANSITIVE ID: 11] modified	created, formed, generated, compiled, produced, implemented, determined	[TRANSITIVE ID: 11] performed, defined
[TRANSITIVE ID: 12] reflect	include, represent, indicate, describe, characterize	[TRANSITIVE ID: 12] identify
[FEATURE ID: 13] interaction	mapping, correlation, relationship	[FEATURE ID: 13] pattern match
[TRANSITIVE ID: 14] passed	written, uploaded, downloaded	[TRANSITIVE ID: 14] external
[TRANSITIVE ID: 15] performs	does, runs, determines, operates, applies	[TRANSITIVE ID: 15] occurs
[FEATURE ID: 16] services	applications, rules, statements, definitions, objects, files, documents	[FEATURE ID: 16] programs, rule specifications, Java class specifications
[FEATURE ID: 17] claim	statement, clause, preceding claim, the claim, figure, item, clair	[FEATURE ID: 17] claim
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 6] of : providing [TRANSITIVE ID: 2] at least one state object , the object [FEATURE ID: 4] including [TRANSITIVE ID: 2] a profile representative [FEATURE ID: 7] of user usage [FEATURE ID: 8] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 4] ; passing , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 9] ; and receiving , from the central server , the state object along with the response [FEATURE ID: 9] of the central server ; wherein the profile [FEATURE ID: 10] is modified [TRANSITIVE ID: 11] to reflect [TRANSITIVE ID: 12] the interaction [FEATURE ID: 13] between the client location and the central server ; and wherein the central server audits the state object / profile passed [TRANSITIVE ID: 14] to it , and performs [TRANSITIVE ID: 15] analysis [FEATURE ID: 2] on the audited profile [FEATURE ID: 4] in order to direct services [FEATURE ID: 16] and / or information [FEATURE ID: 1] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 17] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 9] of a particular interaction type [FEATURE ID: 4] , and the value - field contains a count [FEATURE ID: 7] of the number of occurrences [FEATURE ID: 6] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 4] detailing the last modification of the interaction count [FEATURE ID: 4] and / or a time component detailing the creation of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction between the server [FEATURE ID: 4] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 1]		1 . A computer [FEATURE ID: 4] - implemented method [FEATURE ID: 1] for transforming [TRANSITIVE ID: 2] a document [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 1] of : ( a ) creating [TRANSITIVE ID: 2] one or more programs [FEATURE ID: 16] from one or more rule specifications [FEATURE ID: 16] , wherein : ( i ) the rules specifications identify [TRANSITIVE ID: 12] one or more transformations [FEATURE ID: 6] of the document to be performed [TRANSITIVE ID: 11] when a pattern match [FEATURE ID: 13] occurs [TRANSITIVE ID: 15] between the document and a source pattern ; ( ii ) the rules specifications are defined [TRANSITIVE ID: 11] using [TRANSITIVE ID: 5] a first programming language [FEATURE ID: 4] ; and ( iii ) the document is defined in the first programming language both before and after transformation ; and ( b ) executing the programs in the computer to perform the transformations of the document when the pattern match occurs between the document and the source pattern . 2 . The method of claim [FEATURE ID: 17] 1 , wherein the rules specifications identify one or more actions [FEATURE ID: 6] to be performed when a pattern match occurs between the document and a source pattern . 3 . The method of claim 2 , further comprising the step [FEATURE ID: 6] of performing the actions when the pattern match occurs between the document and the source pattern . 4 . The method of claim 1 , wherein the document is an eXtensible Markup Language ( XML ) document . 5 . The method of claim 4 above , wherein the rules specifications are defined in XML . 6 . The method of claim 5 above , wherein the rules specifications are embedded in the XML document [FEATURE ID: 4] . 7 . The method of claim 5 above , wherein the rules specifications are external [FEATURE ID: 14] to the XML document . 8 . The method of claim 1 , wherein the creating step further comprises the step of creating one or more class specifications [FEATURE ID: 6] from the rule specifications and the executing step further comprises the step of instantiating the class specifications as one or more of the computer programs [FEATURE ID: 6] . 9 . The method of claim 8 , wherein the class specifications comprise Java class specifications [FEATURE ID: 16] and the instantiated class specifications comprise Java objects [FEATURE ID: 6] . 10 . The method of claim 1 , wherein the computer programs are selected from a group [FEATURE ID: 10] comprising one or more pattern [FEATURE ID: 8] matching components [FEATURE ID: 6] , one or more replacement components [FEATURE ID: 6] , and one or more action components [FEATURE ID: 6] . 11 . The method of claim 1 above , further comprising the steps of : ( 1 ) registering one or more of the computer programs as a listener to be notified when a pattern match occurs between the source pattern and the document ; and ( 2 ) notifying the registered listener to perform one or more of the transformations whenever the pattern match occurs between the source pattern and the document . 12 . The method of claim 11 above , further comprising the step of invoking one or more functions [FEATURE ID: 3] from the notified listener . 13 . The method of claim 1 above , further comprising the steps of : ( 1 ) registering one or more of the computer programs as a listener to be notified when a pattern match occurs between the source pattern and the document ; and ( 2 ) notifying the registered listener to perform one or more actions whenever the pattern match occurs between the source pattern and the document . 14 . The method of claim 1 above , wherein the rules specification [FEATURE ID: 7] comprises a pattern matching language [FEATURE ID: 7] . 15 . The method of claim 14 above , wherein the pattern matching language includes one or more components selected from a group comprising : ( 1 ) a source pattern , ( 2 ) a condition [FEATURE ID: 7] , ( 3 ) a target pattern [FEATURE ID: 7] , and ( 4 ) an action part [FEATURE ID: 9] . 16 . The method of claim 14 above , wherein the pattern matching language is based upon a schema structure [FEATURE ID: 7] for the document . 17 . The method of claim 14 above , wherein the schema [FEATURE ID: 7] comprises a regular expression language [FEATURE ID: 7]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US20020173971A1 Filed: 2001-03-28 Issued: 2002-11-21 Patent Holder: (Original Assignee) Reuters Ltd     (Current Assignee) Refinitiv Ltd Inventor(s): Paul Stirpe, Michael Antico, William Pinfold, Tim Slavin Title: System, method and application of ontology driven inferencing-based personalization systems
[FEATURE ID: 1] method	methods, distributed method, novel method, system, process, methodology, technique	[FEATURE ID: 1] method
[TRANSITIVE ID: 2] monitoring	identifying, processing, mapping, analyzing, managing, logging, evaluating	[TRANSITIVE ID: 2] tagging
[FEATURE ID: 3] system, central server, central server audits, particular interaction type, server	client, network, computer, database, user, service, website	[FEATURE ID: 3] system, content store, display, third party, third party user, data mart
[TRANSITIVE ID: 4] comprising, including	containing, having, includes, incorporating, providing, with, compromising	[TRANSITIVE ID: 4] comprising
[FEATURE ID: 5] steps	features, following, automated steps, phases, step, components, sequential steps	[FEATURE ID: 5] steps
[FEATURE ID: 6] profile representative, count	history, summary, description, profile, log, listing, list	[FEATURE ID: 6] personalized view
[FEATURE ID: 7] user usage, occurrences, time component	metadata, activity, data, tags, transactions, events, preferences	[FEATURE ID: 7] user data, information, human resource data, content information, data rules, weighted nodes, stream data, source data, explicit data, implicit data
[TRANSITIVE ID: 8] storing, passing, receiving	presenting, sending, delivering, displaying, issuing, generating, returning	[TRANSITIVE ID: 8] providing
[FEATURE ID: 9] client location	system, computer, server, memory, cache, buffer, terminal	[FEATURE ID: 9] user, data warehouse
[TRANSITIVE ID: 10] passed	known, accessible, directed, provided, available	[TRANSITIVE ID: 10] corresponding
[TRANSITIVE ID: 11] performs	provides, includes, receives, processes, collects, has, maintains	[TRANSITIVE ID: 11] stores, generates, contains
[FEATURE ID: 12] analysis	inference, rules, reasoning, data, logic, decisions, results	[FEATURE ID: 12] consequences, based, conclusions
[FEATURE ID: 13] audited profile, information	data, features, evaluation, results, audit, operations, analysis	[FEATURE ID: 13] content, analytics
[FEATURE ID: 14] services	documents, resources, users, advertisements, objects, content, advertising	[FEATURE ID: 14] healthcare data, selective information
[FEATURE ID: 15] claim	statement, requirement, figure, item, clause, clam, step	[FEATURE ID: 15] claim
[FEATURE ID: 16] identifier	index, attribute, instance, image	[FEATURE ID: 16] ontology
[FEATURE ID: 17] creation	association, alignment, combination, correlation	[FEATURE ID: 17] accordance
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns of a system [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : providing at least one state object , the object including [TRANSITIVE ID: 4] a profile representative [FEATURE ID: 6] of user usage [FEATURE ID: 7] ; storing [TRANSITIVE ID: 8] the state object at a client location [FEATURE ID: 9] ; passing [FEATURE ID: 8] , to a central server [FEATURE ID: 3] , the state object with each subsequent interaction initiation ; and receiving [TRANSITIVE ID: 8] , from the central server , the state object along with the response of the central server ; wherein the profile is modified to reflect the interaction between the client location and the central server ; and wherein the central server audits [FEATURE ID: 3] the state object / profile passed [TRANSITIVE ID: 10] to it , and performs [TRANSITIVE ID: 11] analysis [FEATURE ID: 12] on the audited profile [FEATURE ID: 13] in order to direct services [FEATURE ID: 14] and / or information [FEATURE ID: 13] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 15] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 16] of a particular interaction type [FEATURE ID: 3] , and the value - field contains a count [FEATURE ID: 6] of the number of occurrences [FEATURE ID: 7] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 7] detailing the last modification of the interaction count and / or a time component detailing the creation [FEATURE ID: 17] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction between the server [FEATURE ID: 3]		1 . A system [FEATURE ID: 3] for providing [TRANSITIVE ID: 8] personalized content [FEATURE ID: 13] to a user [FEATURE ID: 9] , comprising [TRANSITIVE ID: 4] : a data warehouse [FEATURE ID: 9] that stores [TRANSITIVE ID: 11] user data [FEATURE ID: 7] corresponding [TRANSITIVE ID: 10] to a user ; an ontology [FEATURE ID: 16] ; an inferencing engine that generates [TRANSITIVE ID: 11] consequences [FEATURE ID: 12] based [TRANSITIVE ID: 12] on information [FEATURE ID: 7] in said data warehouse , wherein said user data is tagged in accordance [FEATURE ID: 17] with said ontology . 2 . The system of claim [FEATURE ID: 15] 1 , wherein the data warehouse contains [TRANSITIVE ID: 11] healthcare data [FEATURE ID: 14] . 3 . The system of claim 1 , wherein the data warehouse contains human resource data [FEATURE ID: 7] . 4 . The system of claim 1 , wherein the data warehouse contains financial data . 5 . The system of claim 1 , further comprising : a content store [FEATURE ID: 3] , wherein content information [FEATURE ID: 7] from said content store is tagged in accordance with said ontology . 6 . The system of claim 1 , wherein said inferencing engine generates and outputs a personal interest graph ( PIG ) created for the user based on data rules [FEATURE ID: 7] . 7 . The system of claim 5 , wherein said inferencing engine generates and outputs a personal interest graph ( PIG ) created for the user based on data rules , said system further comprising : a display [FEATURE ID: 3] for displaying selective information [FEATURE ID: 14] from said content store based at least in part on the PIG . 8 . The system of claim 1 , wherein the inferencing engine generates and outputs a list of weighted nodes [FEATURE ID: 7] . 9 . The system of claim 5 , said display providing a personalized view [FEATURE ID: 6] of said content for said user . 10 . The system of claim 5 , said display providing a personalized view of said content regarding said user for a third party [FEATURE ID: 3] . 11 . The system of claim 1 , wherein said user data includes click stream data [FEATURE ID: 7] . 12 . The system of claim 1 , wherein said user data includes source data [FEATURE ID: 7] . 13 . The system of claim 1 , wherein said user data includes explicit data [FEATURE ID: 7] . 14 . The system of claim 1 , wherein said user data includes implicit data [FEATURE ID: 7] . 15 . The system of claim 1 , further comprising a third party user [FEATURE ID: 3] obtaining a personalized view of said user , wherein the third party user is displayed information relating at least in part to said user ' s personalized view . 16 . The system of claim 15 , wherein the third party provides information to said user related to said displayed information . 17 . The system of claim 15 , wherein the third party provides information regarding said user to another , other than said user . 18 . The system of claim 1 , further comprising : a data mart [FEATURE ID: 3] that receives tagged user data and an analytics [FEATURE ID: 13] console that analyzes said tagged user data in at least one of said data mart and said data warehouse . 19 . A method [FEATURE ID: 1] for drawing conclusions [FEATURE ID: 12] for personalized content relating to a user , comprising the steps [FEATURE ID: 5] of : receiving user data corresponding to a user ; tagging [FEATURE ID: 2]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6484261B1 Filed: 1998-02-17 Issued: 2002-11-19 Patent Holder: (Original Assignee) Cisco Technology Inc     (Current Assignee) Cisco Technology Inc Inventor(s): Scott L. Wiegel Title: Graphical network security policy management
[FEATURE ID: 1] method, client location, central server, particular interaction type, server, part	system, service, computer, network, process, protocol, client	[FEATURE ID: 1] method, network device, security policy
[TRANSITIVE ID: 2] monitoring, receiving	processing, determining, obtaining, storing, identifying, collecting, constructing	[TRANSITIVE ID: 2] defining, interconnecting, generating
[FEATURE ID: 3] user usage patterns, analysis	activities, processing, functions, actions, features, operations, characteristics	[FEATURE ID: 3] steps, logical operations
[FEATURE ID: 4] system, central server audits	network, client, browser, server, controller, device, machine	[FEATURE ID: 4] computer, scripting language, user interface, user, database, network device such, router
[TRANSITIVE ID: 5] comprising	including, containing, employing, using, performing, with, compromising	[TRANSITIVE ID: 5] comprising
[FEATURE ID: 6] steps	features, components, elements	[FEATURE ID: 6] graphical symbols tat
[TRANSITIVE ID: 7] providing, including, storing, passing	generating, establishing, creating, using, implementing, forming, making	[TRANSITIVE ID: 7] controlling
[FEATURE ID: 8] object	data, information, objects	[FEATURE ID: 8] graphical symbols
[FEATURE ID: 9] profile representative, number, time component	sequence, history, version, state, description, plurality, subset	[FEATURE ID: 9] set, symbolic representation, list
[FEATURE ID: 10] user usage, audited profile, information, occurrences, interaction count	data, content, events, communications, requests, transactions, signals	[FEATURE ID: 10] information messages, instructions, messages, editing commands, user input
[FEATURE ID: 11] subsequent interaction initiation, response, order	request, operation, instruction, command, message, use, identifier	[FEATURE ID: 11] information communication policy, response, first security policy
[FEATURE ID: 12] profile, first interaction	message, protocol, procedure, information, request, rule, configuration	[FEATURE ID: 12] policy, source script
[TRANSITIVE ID: 13] reflect	characterize, model, control, define, represent, indicate, describe	[TRANSITIVE ID: 13] identify
[TRANSITIVE ID: 14] performs	processes, allows, provides, enables, makes	[TRANSITIVE ID: 14] passes
[FEATURE ID: 15] services	results, objects, documents, files, messages, actions	[FEATURE ID: 15] source scripts
[FEATURE ID: 16] claim, identifier	item, step, statement, claimed, element, para claim, preceding claim	[FEATURE ID: 16] claim, portion
[FEATURE ID: 17] count	portion, gui, page, frame, display, field, view	[FEATURE ID: 17] second window, first window
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 6] of : providing [TRANSITIVE ID: 7] at least one state object , the object [FEATURE ID: 8] including [TRANSITIVE ID: 7] a profile representative [FEATURE ID: 9] of user usage [FEATURE ID: 10] ; storing [TRANSITIVE ID: 7] the state object at a client location [FEATURE ID: 1] ; passing [FEATURE ID: 7] , to a central server [FEATURE ID: 1] , the state object with each subsequent interaction initiation [FEATURE ID: 11] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 11] of the central server ; wherein the profile [FEATURE ID: 12] is modified to reflect [TRANSITIVE ID: 13] the interaction between the client location and the central server ; and wherein the central server audits [FEATURE ID: 4] the state object / profile passed to it , and performs [TRANSITIVE ID: 14] analysis [FEATURE ID: 3] on the audited profile [FEATURE ID: 10] in order [FEATURE ID: 11] to direct services [FEATURE ID: 15] and / or information [FEATURE ID: 10] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 16] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 16] of a particular interaction type [FEATURE ID: 1] , and the value - field contains a count [FEATURE ID: 17] of the number [FEATURE ID: 9] of occurrences [FEATURE ID: 10] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 9] detailing the last modification of the interaction count [FEATURE ID: 10] and / or a time component detailing the creation of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 12] between the server [FEATURE ID: 1] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 1]		1 . A method [FEATURE ID: 1] for controlling [TRANSITIVE ID: 7] a network device [FEATURE ID: 1] that passes [TRANSITIVE ID: 14] or rejects information messages [FEATURE ID: 10] , the method comprising [TRANSITIVE ID: 5] the computer [FEATURE ID: 4] - implemented steps [FEATURE ID: 3] of : defining [TRANSITIVE ID: 2] a set [FEATURE ID: 9] of symbols that identify [TRANSITIVE ID: 13] logical operations [FEATURE ID: 3] that can be carried out by the network device ; defining an information communication policy [FEATURE ID: 11] for the network device by graphically interconnecting [TRANSITIVE ID: 2] one or more of the symbols into a symbolic representation [FEATURE ID: 9] of the policy [FEATURE ID: 12] ; and generating [TRANSITIVE ID: 2] a set of instructions [FEATURE ID: 10] based on the symbolic representation of the policy , wherein the set of instructions causes the network device to selectively pass or reject messages [FEATURE ID: 10] according to the policy , comprising the steps of generating a source script [FEATURE ID: 12] that defines the policy in a scripting language [FEATURE ID: 4] ; and displaying the source script in a window of the user interface [FEATURE ID: 4] . 2 . The method as recited in claim [FEATURE ID: 16] 1 , further comprising the steps of : after re-configuring the one or more symbols , highlighting a corresponding portion [FEATURE ID: 16] of the source script that is displayed in the window when one of the one or more symbols is selected by the user [FEATURE ID: 4] . 3 . The method as recited in claim 1 , further comprising the steps of : naming the source script ; storing the source script in a database [FEATURE ID: 4] ; and displaying , in a second window [FEATURE ID: 17] of the user interface , a list [FEATURE ID: 9] of one or more source scripts [FEATURE ID: 15] that are stored in the database . 4 . A method for establishing a security policy [FEATURE ID: 1] that is enforced by a network device such [FEATURE ID: 4] as a router [FEATURE ID: 4] , the method comprising the steps of : displaying a user interface , wherein the user interface comprises a first window [FEATURE ID: 17] that includes graphical symbols tat [FEATURE ID: 6] can be manipulated to define the security policy ; receiving editing commands [FEATURE ID: 10] that manipulate one or more symbols in the set of graphical symbols [FEATURE ID: 8] whereby the security policy is established based on the editing commands ; displaying a symbolic representation of the security policy in a second window of the user interface ; and generating a set of instructions that are executable by the network device , whereby the network device enforces the security policy according to the symbolic representation , comprising the steps of generating a source script that defines the policy in a scripting language ; and displaying the source script in a window of the user interface . 5 . A method for associating a security policy with a network device , the method comprising the steps of : displaying a first icon on a user interface , wherein the first icon is associated with a first , pre-defined security policy ; displaying a second icon on the user interface , wherein the second icon identifies the network device ; receiving user input [FEATURE ID: 10] that instructs the user interface to position the first icon near the second icon , comprising receiving user input that drags the first icon over the second icon ; and in response [FEATURE ID: 11] thereto , applying the first security policy [FEATURE ID: 11]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6484177B1 Filed: 2000-01-13 Issued: 2002-11-19 Patent Holder: (Original Assignee) International Business Machines Corp     (Current Assignee) International Business Machines Corp Inventor(s): Gary A. Van Huben, Joseph L. Mueller Title: Data management interoperability methods for heterogeneous directory structures
[FEATURE ID: 1] method, response, central server audits, analysis, order, particular interaction type, number	system, use, processing, procedure, means, time, processes	[FEATURE ID: 1] Method, steps, directory service, physical implementation, process
[TRANSITIVE ID: 2] monitoring	processing, handling, maintaining, defining, identifying, representing, use	[TRANSITIVE ID: 2] storing, managing, mapping, storage, return
[FEATURE ID: 3] user usage patterns, profile, audited profile, interaction count	information, content, interaction, record, data, event, state object	[FEATURE ID: 3] application transactions
[FEATURE ID: 4] system, central server, time component, server	client, database, computer, network, user, location, manager	[FEATURE ID: 4] data management system, virtual control repository, single access application, User Interface Layer, Package, Filetype, client station, service server
[TRANSITIVE ID: 5] comprising, providing, including, passing, receiving	employing, with, supporting, presenting, establishing, generating, creating	[TRANSITIVE ID: 5] having, comprising, providing, using
[FEATURE ID: 6] steps	action, methods, operation	[FEATURE ID: 6] related PFVL data
[FEATURE ID: 7] object	method, data, information, system, type, objects	[FEATURE ID: 7] data storage, PFVL Paradign
[FEATURE ID: 8] profile representative	model, specification, definition	[FEATURE ID: 8] common storage model
[FEATURE ID: 9] user usage	data, content, time	[FEATURE ID: 9] Level
[TRANSITIVE ID: 10] storing, last modification	processing, providing, implementing, generation, coupling, linking, creation	[TRANSITIVE ID: 10] use, mapping, addition, modification
[FEATURE ID: 11] client location	directory, system, metadata, location, memory, registry, cache	[FEATURE ID: 11] Variance, separate data storage
[FEATURE ID: 12] subsequent interaction initiation, interaction, identifier, creation, first interaction	association, access, session, interface, call, query, communications	[FEATURE ID: 12] interacting, access method appropriate, request
[FEATURE ID: 13] services, information, occurrences	applications, resources, users, objects, entries, databases, devices	[FEATURE ID: 13] data managers, data objects, other data objects, managers
[FEATURE ID: 14] part	service, receipt, response	[FEATURE ID: 14] processing
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns [FEATURE ID: 3] of a system [FEATURE ID: 4] , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 6] of : providing [TRANSITIVE ID: 5] at least one state object , the object [FEATURE ID: 7] including [TRANSITIVE ID: 5] a profile representative [FEATURE ID: 8] of user usage [FEATURE ID: 9] ; storing [TRANSITIVE ID: 10] the state object at a client location [FEATURE ID: 11] ; passing [FEATURE ID: 5] , to a central server [FEATURE ID: 4] , the state object with each subsequent interaction initiation [FEATURE ID: 12] ; and receiving [TRANSITIVE ID: 5] , from the central server , the state object along with the response [FEATURE ID: 1] of the central server ; wherein the profile [FEATURE ID: 3] is modified to reflect the interaction [FEATURE ID: 12] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 1] the state object / profile passed to it , and performs analysis [FEATURE ID: 1] on the audited profile [FEATURE ID: 3] in order [FEATURE ID: 1] to direct services [FEATURE ID: 13] and / or information [FEATURE ID: 13] suited to the profile to the client location . 2 . A method as claimed in claim 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 12] of a particular interaction type [FEATURE ID: 1] , and the value - field contains a count of the number [FEATURE ID: 1] of occurrences [FEATURE ID: 13] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 4] detailing the last modification [FEATURE ID: 10] of the interaction count [FEATURE ID: 3] and / or a time component detailing the creation [FEATURE ID: 12] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 12] between the server [FEATURE ID: 4] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 14]		1 . Method [FEATURE ID: 1] for use [FEATURE ID: 10] with a data management system [FEATURE ID: 4] having [TRANSITIVE ID: 5] a plurality of repositories of data and a plurality of data managers [FEATURE ID: 13] operating in one or more application layers , comprising [TRANSITIVE ID: 5] the steps [FEATURE ID: 1] of : providing [TRANSITIVE ID: 5] a directory service [FEATURE ID: 1] for interacting [TRANSITIVE ID: 12] with said data management system having a plurality of repositories of data and a plurality of data managers operating in one or more application layers , storing [TRANSITIVE ID: 2] a plurality of data objects [FEATURE ID: 13] in said directory service and storing other data objects [FEATURE ID: 13] in data repositories of said data management system having a plurality of repositories of data and a plurality of data managers operating in one or more application layers and managing [TRANSITIVE ID: 2] both said data objects and other data objects with a virtual control repository [FEATURE ID: 4] , and , using [TRANSITIVE ID: 5] a single access application [FEATURE ID: 4] at a User Interface Layer [FEATURE ID: 4] of said one or more application layers of the data management system , mapping [TRANSITIVE ID: 10] application transactions [FEATURE ID: 3] to an access method appropriate [FEATURE ID: 12] to a physical implementation [FEATURE ID: 1] of data storage [FEATURE ID: 7] used in said data management system and in said directory service , and in the process [FEATURE ID: 1] of mapping [FEATURE ID: 2] , classifying data objects of said directory service and of said data management system as data objects according to a PFVL Paradign [FEATURE ID: 7] according to Package [FEATURE ID: 4] , Filetype [FEATURE ID: 4] , Variance [FEATURE ID: 11] and Level [FEATURE ID: 9] , so that the PFVL Paradign serves as a common storage model [FEATURE ID: 8] for the storage [FEATURE ID: 2] of data objects both in the separate data storage [FEATURE ID: 11] used in said data management system and in the separate data storage used in said directory service , and managing the data objects residing in separate data storage to enable a directory service to interact with said data management system by : ( a ) acting on an initiated request [FEATURE ID: 12] from a client station [FEATURE ID: 4] for data classified according to the PFVL Paradign by determining whether the request should be directed to said directory service or to said data management system , ( b ) directing the request to the directory service or to said data management system as appropriate from the initiated request , ( c ) and employing one or more of said plurality of managers [FEATURE ID: 13] for processing the request and if the request is appropriate for the directory service causing at a service server [FEATURE ID: 4] for the directory service the processing [FEATURE ID: 14] of said initated request which was initiated from said client station and causing the return [FEATURE ID: 2] of any resulting data objects meeting the request along with related PFVL data [FEATURE ID: 6] associated with the returned data object to cause the addition [FEATURE ID: 10] , modification [FEATURE ID: 10]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6484149B1 Filed: 1997-10-10 Issued: 2002-11-19 Patent Holder: (Original Assignee) Microsoft Corp     (Current Assignee) Microsoft Technology Licensing LLC Inventor(s): Pierre J. Jammes, D. Chase Franklin, Darren B. Remington Title: Systems and methods for viewing product information, and methods for generating web pages
[FEATURE ID: 1] method, client location, central server, server	computer, client, database, network, service, process, main server	[FEATURE ID: 1] system
[TRANSITIVE ID: 2] monitoring, providing, storing, passing, receiving	collecting, identifying, maintaining, presenting, capturing, obtaining, recording	[TRANSITIVE ID: 2] viewing, including, describing, having
[FEATURE ID: 3] system	website, computer, database, browser, server, display, client	[FEATURE ID: 3] web server, first computer, product information database, computer storage media, web browser, second computer, user interface, network, user, query, web page, Internet, product
[TRANSITIVE ID: 4] comprising, including	having, includes, comprises, incorporating, containing, providing, featuring	[TRANSITIVE ID: 4] comprising
[FEATURE ID: 5] object, first interaction	data, information, interface, connection, objects, communications, link	[FEATURE ID: 5] access, icons
[FEATURE ID: 6] user usage, audited profile, occurrences	content, data, parameters, use, action, interactions, usage	[FEATURE ID: 6] information, selection, results
[FEATURE ID: 7] subsequent interaction initiation, field further, time component, interaction count, part	notification, message, parameter, value, field, data, command	[FEATURE ID: 7] network message, database query command, user input such
[FEATURE ID: 8] response, identifier, creation	identification, address, image, indication, appearance, association, information	[FEATURE ID: 8] related groups, arrangement, icon
[FEATURE ID: 9] profile	information, content, configuration	[FEATURE ID: 9] relationship
[TRANSITIVE ID: 10] modified	constructed, arranged, formed, disposed, designed, made, provided	[TRANSITIVE ID: 10] configured, stored
[TRANSITIVE ID: 11] reflect	control, include, define	[TRANSITIVE ID: 11] generate
[FEATURE ID: 12] interaction	path, relationship, distance	[FEATURE ID: 12] hierarchical relationship
[FEATURE ID: 13] central server audits	examines, monitors, checks	[FEATURE ID: 13] queries
[FEATURE ID: 14] order	sequence, real time, parallel, addition, succession, advance	[FEATURE ID: 14] response
[FEATURE ID: 15] services, information	objects, data, applications, contents, items, advertisements, messages	[FEATURE ID: 15] product information, products, second icons, additional icons
[FEATURE ID: 16] claim	statement, clause, preceding claim, of claim, figure, claimed, item	[FEATURE ID: 16] claim
[FEATURE ID: 17] particular interaction type	program, process, service, function	[FEATURE ID: 17] run
[FEATURE ID: 18] count	list, portion, number	[FEATURE ID: 18] first
[FEATURE ID: 19] number	plurality, numbers, grouping, series, set, grouped, types	[FEATURE ID: 19] groups, group
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns of a system [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] the steps of : providing [TRANSITIVE ID: 2] at least one state object , the object [FEATURE ID: 5] including [TRANSITIVE ID: 4] a profile representative of user usage [FEATURE ID: 6] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 1] ; passing [FEATURE ID: 2] , to a central server [FEATURE ID: 1] , the state object with each subsequent interaction initiation [FEATURE ID: 7] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response [FEATURE ID: 8] of the central server ; wherein the profile [FEATURE ID: 9] is modified [TRANSITIVE ID: 10] to reflect [TRANSITIVE ID: 11] the interaction [FEATURE ID: 12] between the client location and the central server ; and wherein the central server audits [FEATURE ID: 13] the state object / profile passed to it , and performs analysis on the audited profile [FEATURE ID: 6] in order [FEATURE ID: 14] to direct services [FEATURE ID: 15] and / or information [FEATURE ID: 15] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 16] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier [FEATURE ID: 8] of a particular interaction type [FEATURE ID: 17] , and the value - field contains a count [FEATURE ID: 18] of the number [FEATURE ID: 19] of occurrences [FEATURE ID: 6] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further [FEATURE ID: 7] contains a time component [FEATURE ID: 7] detailing the last modification of the interaction count [FEATURE ID: 7] and / or a time component detailing the creation [FEATURE ID: 8] of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 5] between the server [FEATURE ID: 1] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 7]		1 . A system [FEATURE ID: 1] for viewing [TRANSITIVE ID: 2] product information [FEATURE ID: 15] , comprising [TRANSITIVE ID: 4] : a web server [FEATURE ID: 3] configured [TRANSITIVE ID: 10] to run [TRANSITIVE ID: 17] on a first computer [FEATURE ID: 3] ; a product information database [FEATURE ID: 3] including [TRANSITIVE ID: 2] information [FEATURE ID: 6] describing [TRANSITIVE ID: 2] a hierarchical relationship [FEATURE ID: 12] between groups [FEATURE ID: 19] of products [FEATURE ID: 15] , said product information database stored [TRANSITIVE ID: 10] on a computer storage media [FEATURE ID: 3] , said web server having [TRANSITIVE ID: 2] access [FEATURE ID: 5] to said product information database ; a web browser [FEATURE ID: 3] configured to run on a second computer [FEATURE ID: 3] , said web browser configured to generate [TRANSITIVE ID: 11] a user interface [FEATURE ID: 3] , said user interface displaying icons [FEATURE ID: 5] representing said groups of products , said icons arranged to visually represent said relationship [FEATURE ID: 9] between said groups of products , said web browser configured to send a network message [FEATURE ID: 7] over a network [FEATURE ID: 3] to said web server in response [FEATURE ID: 14] to selection [FEATURE ID: 6] by a user [FEATURE ID: 3] of the second computer of one of said icons representing a first [FEATURE ID: 18] of said groups of products , said network message including a database query command [FEATURE ID: 7] that specifies a query [FEATURE ID: 3] of said product information database for related groups [FEATURE ID: 8] of products having said relationship to said first group of products ; and said web server configured to submit said query to said product information database , and to return to said web browser a web page [FEATURE ID: 3] including results [FEATURE ID: 6] of said query , said web page including information describing said related groups of products , said web browser configured to extract said information describing said related groups of products and to display second icons [FEATURE ID: 15] representing said related groups of products . 2 . The system as described in claim [FEATURE ID: 16] 1 wherein said network message complies with an Internet protocol and said network is the Internet [FEATURE ID: 3] . 3 . The system as described in claim 1 wherein an arrangement [FEATURE ID: 8] of said additional icons [FEATURE ID: 15] displayed by said user interface represents said relationship between said first group and said related groups . 4 . A system for viewing product information , comprising : a web server configured to run on a first computer ; a product information database including information describing a hierarchical relationship between a product [FEATURE ID: 3] and a group [FEATURE ID: 19] of products , said product information database stored on a computer storage media , said web server having access to said product information database ; a web browser configured to run on a second computer , said web browser configured to generate a user interface , said user interface displaying an icon [FEATURE ID: 8] representing said groups of products , said web browser responsive to user input such [FEATURE ID: 7] that a user , by selecting said icon , queries [FEATURE ID: 13]

---

Targeted Patent: Patent: US7392160B2 Filed: 2002-12-18 Issued: 2008-06-24 Patent Holder: (Original Assignee) Nice Systems Technologies UK Ltd     (Current Assignee) Alto Dynamics LLC Inventor(s): Tony Wicks Title: System and method for monitoring usage patterns	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US20020169893A1 Filed: 2001-05-09 Issued: 2002-11-14 Patent Holder: (Original Assignee) UNIVESSENCE DIGITAL STUDIOS Ltd     (Current Assignee) UNIVESSENCE DIGITAL STUDIOS Ltd Inventor(s): Li-Han Chen, Michael Takayama, Dominic Chan Title: System and method for computer data synchronization
[FEATURE ID: 1] method, modified, time component	system, network, way, configured, computer, used, arranged	[FEATURE ID: 1] adapted, database such
[TRANSITIVE ID: 2] monitoring, storing, receiving	collecting, capturing, maintaining, recording, displaying, providing, processing	[TRANSITIVE ID: 2] storing
[FEATURE ID: 3] system, central server, central server audits, particular interaction type, server	computer, client, network, service, browser, device, program	[FEATURE ID: 3] computer data synchronization system, database, server, synch application, synchronization system, language translation application, later time
[TRANSITIVE ID: 4] comprising, including	having, includes, comprises, incorporating, containing, featuring, providing	[TRANSITIVE ID: 4] comprising
[TRANSITIVE ID: 5] providing	using, selecting, maintaining, receiving	[TRANSITIVE ID: 5] controlling
[FEATURE ID: 6] object, audited profile, services, information, occurrences	data, objects, applications, users, resources, communications, profile	[FEATURE ID: 6] original computer data
[FEATURE ID: 7] user usage, analysis	content, data, information, instructions, text, language, same	[FEATURE ID: 7] movable pointer icon, annotated data, thesaurus information, user identification data, correspondence data
[FEATURE ID: 8] client location, number, last modification	time, duration, location, timing, controller, rate, point	[FEATURE ID: 8] movable pointer icon operating, same time
[FEATURE ID: 9] subsequent interaction initiation, first interaction	request, transmission, message, instruction, command, access, query	[FEATURE ID: 9] receive, synchronization data, other language
[FEATURE ID: 10] profile	application, file, database, program	[FEATURE ID: 10] hyperlink
[TRANSITIVE ID: 11] reflect	change, alter, modify	[TRANSITIVE ID: 11] edit
[TRANSITIVE ID: 12] passed	stored, accessible, directed, uploaded, provided	[TRANSITIVE ID: 12] connected
[FEATURE ID: 13] claim	statement, clause, preceding claim, the claim, of claim, figure, item	[FEATURE ID: 13] claim
[FEATURE ID: 14] count, part	copy, component, representation, function, data, version, display	[FEATURE ID: 14] portion
[FEATURE ID: 15] interaction count	type, table, number, field	[FEATURE ID: 15] group
1 . A method [FEATURE ID: 1] of monitoring [TRANSITIVE ID: 2] user usage patterns of a system [FEATURE ID: 3] , comprising [TRANSITIVE ID: 4] the steps of : providing [TRANSITIVE ID: 5] at least one state object , the object [FEATURE ID: 6] including [TRANSITIVE ID: 4] a profile representative of user usage [FEATURE ID: 7] ; storing [TRANSITIVE ID: 2] the state object at a client location [FEATURE ID: 8] ; passing , to a central server [FEATURE ID: 3] , the state object with each subsequent interaction initiation [FEATURE ID: 9] ; and receiving [TRANSITIVE ID: 2] , from the central server , the state object along with the response of the central server ; wherein the profile [FEATURE ID: 10] is modified [TRANSITIVE ID: 1] to reflect [TRANSITIVE ID: 11] the interaction between the client location and the central server ; and wherein the central server audits [FEATURE ID: 3] the state object / profile passed [TRANSITIVE ID: 12] to it , and performs analysis [FEATURE ID: 7] on the audited profile [FEATURE ID: 6] in order to direct services [FEATURE ID: 6] and / or information [FEATURE ID: 6] suited to the profile to the client location . 2 . A method as claimed in claim [FEATURE ID: 13] 1 , wherein the profile includes at least one key and value - field pair . 3 . A method as claimed in claim 2 , wherein the key is an identifier of a particular interaction type [FEATURE ID: 3] , and the value - field contains a count [FEATURE ID: 14] of the number [FEATURE ID: 8] of occurrences [FEATURE ID: 6] of that particular interaction type . 4 . A method as claimed in claim 3 , wherein the value - field further contains a time component [FEATURE ID: 1] detailing the last modification [FEATURE ID: 8] of the interaction count [FEATURE ID: 15] and / or a time component detailing the creation of the key and value - field . 5 . A method as claimed in claim 1 , wherein the at least one state object is provided by the central server during a first interaction [FEATURE ID: 9] between the server [FEATURE ID: 3] and the client location . 6 . A method as claimed in claim 5 , wherein the state object is provided as a part [FEATURE ID: 14]		1 . A computer data synchronization system [FEATURE ID: 3] comprising [TRANSITIVE ID: 4] : a database [FEATURE ID: 3] for storing [TRANSITIVE ID: 2] original computer data [FEATURE ID: 6] ; a server [FEATURE ID: 3] adapted [TRANSITIVE ID: 1] to communicate with a plurality of reception devices ; and a synch application [FEATURE ID: 3] connected [TRANSITIVE ID: 12] to said database , wherein said synch application is adapted to receive [TRANSITIVE ID: 9] synchronization data [FEATURE ID: 9] from a controlling [TRANSITIVE ID: 5] one of said plurality of reception devices , said synch application is further adapted to provide a portion [FEATURE ID: 14] of said original computer data to said plurality of reception devices , wherein said portion of said original computer data is based upon a synchronized portion of said original computer data that is being displayed on said controlling one of said plurality of reception devices . 2 . The synchronization system [FEATURE ID: 3] of claim [FEATURE ID: 13] 1 , wherein said synchronization data further comprises pointer icon data , wherein said pointer icon data corresponds to a movable pointer icon operating [FEATURE ID: 8] on said controlling one of said plurality of reception devices . 3 . The synchronization system of claim 2 , wherein said synch application is further adapted to provide said synchronization data to at least one other one of said plurality of reception devices such that said movable pointer icon [FEATURE ID: 7] is superimposed over said portion of said original computer data . 4 . The synchronization system of claim 1 , wherein said synch application is further adapted to provide said plurality of reception devices with a synch button , wherein said synch button is adapted to enable a non-controlling one of said plurality of reception devices to become said controlling one of said plurality of reception devices . 5 . The synchronization system of claim 1 , wherein said synch application is further adapted to receive annotated data from said controlling one of said plurality of reception devices , wherein said annotated data [FEATURE ID: 7] corresponds to said portion of said original computer data . 6 . The synchronization system of claim 5 , wherein said annotated data is selected from a group [FEATURE ID: 15] of annotated data consisting of text , graphic , program application , hyperlink [FEATURE ID: 10] , audio , and video . 7 . The synchronization system of claim 5 , wherein said synch application is further adapted to provide said controlling one of said plurality of reception devices with a toolbar , wherein said toolbar is adapted to enable said controlling one of said plurality of reception devices to create , edit [FEATURE ID: 11] , and delete said annotated data . 8 . The synchronization system of claim 5 , wherein said synch application is further adapted to provide said annotated data to at least one other one of said plurality of reception devices such that said annotated data is superimposed over said portion of said original computer data . 9 . The synchronization system of claim 8 , wherein said synch application further comprises a language translation application [FEATURE ID: 3] adapted to translate said annotated data into at least one other language [FEATURE ID: 9] . 10 . The synchronization system of claim 9 , wherein said language translation application is further adapted to provide thesaurus information [FEATURE ID: 7] to said controlling one of said plurality of reception devices . 11 . The synchronization system of claim 8 , wherein said synch application is further adapted to provide additional annotated data to said at least one other one of said plurality of reception devices , wherein said additional annotated data corresponds to said annotated data and comprises user identification data [FEATURE ID: 7] . 12 . The synchronization system of claim 8 , wherein said annotated data and correspondence data [FEATURE ID: 7] linking said annotated data to said portion of said original computer data is stored in said database such [FEATURE ID: 1] that said annotated data and said portion of said original computer data can be replayed at a later time [FEATURE ID: 3] . 13 . The synchronization system of claim 12 , wherein said synch application further comprises a language translation application adapted to translate said annotated data at approximately the same time [FEATURE ID: 8]

---