Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6154778A Filed: 1998-05-19 Issued: 2000-11-28 Patent Holder: (Original Assignee) Hewlett Packard Co     (Current Assignee) Hewlett Packard Enterprise Development LP Inventor(s): Jari Koistinen, Aparna Seetharaman, Evan R. Kirshenbaum Title: Utility-based multi-category quality-of-service negotiation in distributed systems
[FEATURE ID: 1] method, network device, network device identifier, command, device, directory tree, HTTP message, network, central repository, proper syntax, central storage location, header portion	computer, user, database, node, session, protocol, message	[FEATURE ID: 1] method, client, server, system, steps, communications link, negotiating, service available, different QoS, QoS agreement, QoS levels available
[TRANSITIVE ID: 2] communicating	coupling, using, connecting	[TRANSITIVE ID: 2] having
[TRANSITIVE ID: 3] comprising, retrieving, includes, identifying	providing, including, having, defining, encompassing, obtaining, requesting	[TRANSITIVE ID: 3] negotiating, comprising, representing
[FEATURE ID: 4] steps, network devices	components, elements, features, aspects, segments, nodes, entities	[FEATURE ID: 4] categories
[TRANSITIVE ID: 5] receiving, corresponding	providing, identifying, obtaining, processing, requesting, setting, maintaining	[TRANSITIVE ID: 5] establishing, generating, related, transmitting, monitoring, calculation
[FEATURE ID: 6] repository, indication, format	description, structure, profile, implementation, representation, interpretation, definition	[FEATURE ID: 6] multi-category QoS specification
[TRANSITIVE ID: 7] containing	as, representing, including	[TRANSITIVE ID: 7] being
[FEATURE ID: 8] attribute field, identifier, article	item, attribute, option, application, parameter, account, offering	[FEATURE ID: 8] category, offer, QoS specification
[FEATURE ID: 9] attribute data	parameters, information, values, data, categories, descriptions, classes	[FEATURE ID: 9] multi-category QoS specifications, QoS specifications
[FEATURE ID: 10] claim	preceding claim, clair, embodiment, figure, paragraph, item, clause	[FEATURE ID: 10] claim
[FEATURE ID: 11] step	process step, method, step of, sub step, initial step, preceding step, method step	[FEATURE ID: 11] step
[FEATURE ID: 12] frame, accordance, configuration record	response, command, session, configuration, table, template, combination	[FEATURE ID: 12] agreement
[FEATURE ID: 13] operation	response, capability, performance	[FEATURE ID: 13] utility
[FEATURE ID: 14] populated attribute field, attribute value	condition, value, characteristic, metadata, property, class, content	[FEATURE ID: 14] multi-category quality, parameter, part
[FEATURE ID: 15] computer program product	data, request, transmission, communication	[FEATURE ID: 15] service
1 . A method [FEATURE ID: 1] for communicating [TRANSITIVE ID: 2] with a network device [FEATURE ID: 1] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier [FEATURE ID: 1] , the network device identifier corresponding [TRANSITIVE ID: 5] to the network device ; retrieving [TRANSITIVE ID: 3] a command [FEATURE ID: 1] - format template from a repository [FEATURE ID: 6] containing [TRANSITIVE ID: 7] a plurality of command - format templates , wherein the command - format template indicates how to construct a device [FEATURE ID: 1] - specific command for the network device and includes [TRANSITIVE ID: 3] an attribute field [FEATURE ID: 8] ; identifying [TRANSITIVE ID: 3] attribute data [FEATURE ID: 9] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 10] 1 , wherein the step [FEATURE ID: 11] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 1] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication [FEATURE ID: 6] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 1] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 12] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 13] of the network device in accordance [FEATURE ID: 12] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 4] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 14] and is in the proper syntax [FEATURE ID: 1] and format [FEATURE ID: 6] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 8] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 12] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 15] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 14] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 8]		1 . A method [FEATURE ID: 1] for negotiating [TRANSITIVE ID: 3] a multi-category quality [FEATURE ID: 14] - of - service [FEATURE ID: 15] ( QoS ) agreement [FEATURE ID: 12] between a client [FEATURE ID: 1] and a server [FEATURE ID: 1] in a system [FEATURE ID: 1] comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 1] of : establishing [TRANSITIVE ID: 5] a communications link [FEATURE ID: 1] having [TRANSITIVE ID: 2] a client - side of said negotiating [FEATURE ID: 1] and server - side ; generating [TRANSITIVE ID: 5] a plurality of multi-category QoS specifications [FEATURE ID: 9] , each said multi-category QoS specification [FEATURE ID: 6] being [TRANSITIVE ID: 7] representative of a probabilistic estimate of QoS levels for a service available [FEATURE ID: 1] via said server , each category [FEATURE ID: 8] of said QoS specifications [FEATURE ID: 9] representing [TRANSITIVE ID: 3] a different QoS [FEATURE ID: 1] - related [TRANSITIVE ID: 5] parameter [FEATURE ID: 14] ; transmitting [TRANSITIVE ID: 5] said plurality of multi-category QoS specifications over said communications link from said server - side to said client - side ; selecting at least one of said multi-category QoS specifications to be included in an offer [FEATURE ID: 8] for a QoS agreement [FEATURE ID: 1] ; identifying each said selected multi-category QoS specification as part [FEATURE ID: 14] of said offer , said offer requesting a service provided by said server at said probabilistic estimate of said QoS levels represented by said each selected multi-category QoS specification ; transmitting said offer over said communications link from said client - side to said server - side ; and monitoring [FEATURE ID: 5] said communications link at said client - side for a response to said offer indicating one of an acceptance , a rejection , and a counteroffer to said offer . 2 . The method of claim [FEATURE ID: 10] 1 further comprising the step [FEATURE ID: 11] of calculating an expected utility [FEATURE ID: 13] to said client for each said QoS specification [FEATURE ID: 8] , including calculating expected utilities of categories [FEATURE ID: 4] of said each multi-category QoS specification received via said communications link , said calculation [FEATURE ID: 5] of said expected utilities being performed at said client - side of said communications link and being based on said probabilistic estimate of said QoS levels available [FEATURE ID: 1]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6154776A Filed: 1998-03-20 Issued: 2000-11-28 Patent Holder: (Original Assignee) Sun Microsystems Inc     (Current Assignee) Oracle America Inc Inventor(s): Jean-Christophe Martin Title: Quality of service allocation on a network
[FEATURE ID: 1] method, device, frame, central repository, configuration record, central storage location, computer program product, header portion	network, memory, server, system, database, process, table	[FEATURE ID: 1] computer, method, flow, directory service, network element, controller
[FEATURE ID: 2] network device, command, network	node, query, message, router, system, database, client	[FEATURE ID: 2] network, network element separate, cache
[TRANSITIVE ID: 3] comprising, containing, includes	including, providing, comprises, defining, has, with, performing	[TRANSITIVE ID: 3] allocating, comprising, having
[FEATURE ID: 4] steps, network devices	nodes, elements, components, step, devices, aspects, states	[FEATURE ID: 4] steps
[TRANSITIVE ID: 5] receiving, retrieving, identifying	generating, obtaining, providing, requesting, defining, storing, recognizing	[TRANSITIVE ID: 5] detecting, determining
[FEATURE ID: 6] network device identifier	value, name, query, filter, default, trigger, profile	[FEATURE ID: 6] parameter, specific configuration rule, default configuration rule
[TRANSITIVE ID: 7] corresponding, specific command	particular, specific, unique, referring, appropriate, mapped, applicable	[TRANSITIVE ID: 7] allocated
[FEATURE ID: 8] repository	database, cache, table, queue, location, list, record	[FEATURE ID: 8] protocol header, directory, variable flow parameter, directory entry, local cache
[TRANSITIVE ID: 9] construct	generate, obtain, specify, define, create, configure	[TRANSITIVE ID: 9] access
[FEATURE ID: 10] attribute field, XML message, indication, operation, proper syntax, identifier, article	attribute, item, object, interface, action, identification, address	[FEATURE ID: 10] entity, entity binding, configuration rule, entry
[FEATURE ID: 11] claim	requirement, item, preceding claim, statement, the claim, of claim, clause	[FEATURE ID: 11] claim
[FEATURE ID: 12] step	10 step, method step, means, stage, steps, method, said step	[FEATURE ID: 12] step
[FEATURE ID: 13] directory tree, accordance	pointer, path, mapping, response, comparison, correspondence	[FEATURE ID: 13] link
[FEATURE ID: 14] populated attribute field, attribute value	value, parameter, condition, object, content, instruction, request	[FEATURE ID: 14] Quality
[FEATURE ID: 15] format	configuration, definition, description, data	[FEATURE ID: 15] Service definition
1 . A method [FEATURE ID: 1] for communicating with a network device [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier [FEATURE ID: 6] , the network device identifier corresponding [TRANSITIVE ID: 7] to the network device ; retrieving [TRANSITIVE ID: 5] a command [FEATURE ID: 2] - format template from a repository [FEATURE ID: 8] containing [TRANSITIVE ID: 3] a plurality of command - format templates , wherein the command - format template indicates how to construct [TRANSITIVE ID: 9] a device [FEATURE ID: 1] - specific command [FEATURE ID: 7] for the network device and includes [TRANSITIVE ID: 3] an attribute field [FEATURE ID: 10] ; identifying [TRANSITIVE ID: 5] attribute data corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 11] 1 , wherein the step [FEATURE ID: 12] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 13] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 10] comprising at least an indication [FEATURE ID: 10] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 1] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 10] of the network device in accordance [FEATURE ID: 13] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 2] formed of a plurality of network devices [FEATURE ID: 4] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 14] and is in the proper syntax [FEATURE ID: 10] and format [FEATURE ID: 15] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 10] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 1] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 1] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 14] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 10]		1 . A computer [FEATURE ID: 1] - implemented method [FEATURE ID: 1] of allocating [TRANSITIVE ID: 3] a Quality [FEATURE ID: 14] of Service to a flow [FEATURE ID: 1] on a network [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] : i ) detecting [TRANSITIVE ID: 5] a new instance of an entity [FEATURE ID: 10] associated with said flow on said network , said flow having [TRANSITIVE ID: 3] associated therewith at least one parameter [FEATURE ID: 6] allocated [TRANSITIVE ID: 7] to said entity ; ii ) determining [TRANSITIVE ID: 5] a flow to entity binding [FEATURE ID: 10] between said flow and said entity based on said at least one parameter of said flow ; iii ) using said flow to entity binding to access [FEATURE ID: 9] a Quality of Service definition [FEATURE ID: 15] for said entity , said Quality of Service definition being maintained in a directory service [FEATURE ID: 1] of said network and including at least one configuration rule [FEATURE ID: 10] for said flow , wherein said Quality of Service definition binds said flow with said Quality of Service ; and iv ) dynamically applying to said flow said at least one configuration rule identified by said Quality of Service definition . 2 . The method of claim [FEATURE ID: 11] 1 , wherein step [FEATURE ID: 12] ( i ) comprises responding to a flow event representative of said new instance of said entity associated with said flow on said network . 3 . The method of claim 2 , wherein step ( i ) comprises comparing at least one said parameter of said flow to at least one configuration rule and identifying said new instance of said entity associated with said flow where said at least one parameter of said flow matches with a specific configuration rule [FEATURE ID: 6] . 4 . The method of claim 3 , wherein step ( i ) comprises comparing at least one said parameter of said flow to at least one configuration rule and identifying said new instance of said entity associated with said flow where said at least one parameter of said flow matches with a default configuration rule [FEATURE ID: 6] . 5 . The method of claim 1 , wherein step ( i ) comprises responding to a directory event representative of said new instance of said entity associated with said flow on said network . 6 . The method of claim 1 , wherein at least one said parameter of said flow is a dynamically allocated parameter extracted from a protocol header [FEATURE ID: 8] . 7 . The method of claim 1 , wherein step ( ii ) comprises : retrieving a Quality of Service identification corresponding to said flow to entity binding , said Quality of Service identification being maintained in an entry [FEATURE ID: 10] for said entity in a directory [FEATURE ID: 8] of said directory service . 8 . The method of claim 7 , wherein step ( iii ) comprises : using said Quality of Service identification to retrieve said Quality of Service definition , said Quality of Service definition being maintained in an entry for said Quality of Service definition in a directory of said directory service . 9 . The method of claim 1 , wherein at least one said configuration rule comprises a link [FEATURE ID: 13] to at least one dynamically variable flow parameter [FEATURE ID: 8] in a directory entry [FEATURE ID: 8] for a said entity . 10 . The method of claim 1 , wherein at least one of steps [FEATURE ID: 4] ( i ) - ( iv ) is performed in a network element separate [FEATURE ID: 2] from said directory service and communication between said network element [FEATURE ID: 1] and said directory service is under LDAP ( Lightweight Directory Access Protocol ) . 11 . The method of claim 10 , further comprising steps of maintaining a local cache [FEATURE ID: 8] in said network element for at least one Quality of Service identification corresponding to said flow to entity binding , wherein step ( ii ) comprises : initially accessing said cache [FEATURE ID: 2] for retrieving said Quality of Service identification , if present , and , if not present , accessing said directory service for retrieving said Quality of Service identification . 12 . The method of claim 10 , further comprising steps of maintaining a local cache in said network element for at least one said Quality of Service definition , wherein step ( iii ) comprises : initially accessing said cache for retrieving said Quality of Service definition , if present , and , if not present , accessing said directory service for retrieving said Quality of Service definition . 13 . A Quality of Service mechanism for allocating a Quality of Service to a flow on a network , said Quality of Service mechanism comprising : a controller [FEATURE ID: 1]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6134581A Filed: 1997-10-06 Issued: 2000-10-17 Patent Holder: (Original Assignee) Sun Microsystems Inc     (Current Assignee) Oracle America Inc Inventor(s): Osman Abdoul Ismael, Serge Andre Rigori Title: Method and system for remotely browsing objects
[FEATURE ID: 1] method, device, directory tree, frame, network, populated attribute field, format, computer program product, header portion	computer, protocol, node, communication, payload, controller, structure	[FEATURE ID: 1] telecommunications network, network communications protocol, computing system connectable
[FEATURE ID: 2] network device, retrieving, identifying	database, resource, client, requesting, network, receiving, providing	[FEATURE ID: 2] enabling, bean, repository service object, network adaptor object, request
[TRANSITIVE ID: 3] comprising, containing, includes	including, comprises, defining, having, providing, implementing, has	[TRANSITIVE ID: 3] comprising, being, performing, comprise
[FEATURE ID: 4] steps, step	events, operations, functions, action, attributes, parameters, states	[FEATURE ID: 4] properties, methods, actions, object methods, object functions
[TRANSITIVE ID: 5] receiving	requesting, using, providing	[TRANSITIVE ID: 5] framework referencing
[FEATURE ID: 6] network device identifier, command, XML message, HTTP message	message, response, request, event, instruction, query, document	[FEATURE ID: 6] external request, subsequent response
[TRANSITIVE ID: 7] corresponding	coupled, assignable, applicable, linked, related	[TRANSITIVE ID: 7] responsive
[FEATURE ID: 8] repository, configuration record, attribute value	database, table, field, response, library, device, property	[FEATURE ID: 8] set, repository service
[TRANSITIVE ID: 9] indicates	defines, sets, specifies, includes, describes, represents, controls	[TRANSITIVE ID: 9] comprises
[TRANSITIVE ID: 10] construct	specify, handle, implement, provide, make, use, process	[TRANSITIVE ID: 10] effect
[FEATURE ID: 11] attribute field, indication, operation, identifier, article	attribute, item, interface, agent, object, address, asset	[FEATURE ID: 11] extensible framework, object method
[FEATURE ID: 12] attribute data	attributes, metadata, information, parameters	[FEATURE ID: 12] support
[FEATURE ID: 13] claim	the claim, preceding claim, claimed, clair, embodiment, figure, paragraph	[FEATURE ID: 13] claim
[FEATURE ID: 14] network devices	entities, components, agents, elements, nodes, clients, applications	[FEATURE ID: 14] objects, network adaptors, further service objects
[FEATURE ID: 15] central repository, proper syntax	structure, template, network, context	[FEATURE ID: 15] framework
[FEATURE ID: 16] central storage location	resource, network, container	[FEATURE ID: 16] network adaptor
1 . A method [FEATURE ID: 1] for communicating with a network device [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier [FEATURE ID: 6] , the network device identifier corresponding [TRANSITIVE ID: 7] to the network device ; retrieving [TRANSITIVE ID: 2] a command [FEATURE ID: 6] - format template from a repository [FEATURE ID: 8] containing [TRANSITIVE ID: 3] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 9] how to construct [TRANSITIVE ID: 10] a device [FEATURE ID: 1] - specific command for the network device and includes [TRANSITIVE ID: 3] an attribute field [FEATURE ID: 11] ; identifying [TRANSITIVE ID: 2] attribute data [FEATURE ID: 12] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 13] 1 , wherein the step [FEATURE ID: 4] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 1] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 6] comprising at least an indication [FEATURE ID: 11] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 6] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 1] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 11] of the network device in accordance with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 14] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 15] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 1] and is in the proper syntax [FEATURE ID: 15] and format [FEATURE ID: 1] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 11] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 8] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 16] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 1] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 8] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 11]		1 . The network agent for a telecommunications network [FEATURE ID: 1] , said network agent comprising [TRANSITIVE ID: 3] : an extensible framework [FEATURE ID: 11] ; one or more managed objects [FEATURE ID: 14] registerable with said framework [FEATURE ID: 15] ; and one or more network adaptors [FEATURE ID: 14] registerable with said framework for a network communications protocol [FEATURE ID: 1] for enabling [TRANSITIVE ID: 2] access to said managed objects ; and at least one of the managed objects being [TRANSITIVE ID: 3] a bean [FEATURE ID: 2] which comprises [TRANSITIVE ID: 9] a set [FEATURE ID: 8] of properties [FEATURE ID: 4] , a set of methods [FEATURE ID: 4] for performing [TRANSITIVE ID: 3] actions [FEATURE ID: 4] , and support [FEATURE ID: 12] for events and for introspection . 2 . The network agent of claim [FEATURE ID: 13] 1 , comprising a repository service object registrable with said framework , said managed object ( s ) and / or said network adaptor [FEATURE ID: 16] ( s ) and / or one or more further service objects [FEATURE ID: 14] being registrable with said repository service object [FEATURE ID: 2] , whereby said managed object and said network adaptors are registerable indirectly with said framework via said repository service object . 3 . The network agent of claim 2 , wherein said network adaptor ( s ) comprise [TRANSITIVE ID: 3] network adaptor object [FEATURE ID: 2] ( s ) . 4 . The network agent of claim 1 , wherein said framework comprises getter and setter properties and implements getter and setter methods for getting and / or setting objects and / or object methods [FEATURE ID: 4] . 5 . The network agent of claim 1 , wherein a said network adaptor is responsive [FEATURE ID: 7] to a received external request [FEATURE ID: 6] to cause said framework to get a managed object method [FEATURE ID: 11] for said request [FEATURE ID: 2] and to return a subsequent response [FEATURE ID: 6] . 6 . The network agent of claim 5 and including repository service object registrable with said framework , said managed object ( s ) and / or said network adaptor ( s ) being registrable with said repository service object , whereby said managed object and said network adaptors are registerable indirectly with said framework via said repository service object , said framework referencing [FEATURE ID: 5] said repository service [FEATURE ID: 8] for calling said managed object method . 7 . The network agent of claim 4 , wherein said framework is arranged to effect [FEATURE ID: 10] add object and remove object functions [FEATURE ID: 4] . 8 . A computing system connectable [FEATURE ID: 1]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6131119A Filed: 1997-04-01 Issued: 2000-10-10 Patent Holder: (Original Assignee) Sony Corp; Sony Trans Com Inc     (Current Assignee) Sony Corp ; Sony Trans Com Inc Inventor(s): Toshiharu Fukui Title: Automatic configuration system for mapping node addresses within a bus structure to their physical location
[FEATURE ID: 1] method, network device, command, directory tree, network, central repository, populated attribute field, configuration record, central storage location, header portion	system, device, database, memory, configuration, computer, server	[FEATURE ID: 1] method, bus structure, steps, wiring database, serial bus network, system manager unit, headend, zone bridge unit
[TRANSITIVE ID: 2] communicating, retrieving, identifying	processing, synchronizing, providing, transferring, locating, converting, linking	[TRANSITIVE ID: 2] mapping, comparing
[TRANSITIVE ID: 3] comprising, containing, includes	having, with, providing, comprises, using, identifying, defining	[TRANSITIVE ID: 3] comprising, including, representing
[FEATURE ID: 4] steps, operation	states, features, functions, elements, output, configuration, characteristics	[FEATURE ID: 4] physical locations, passenger sets
[TRANSITIVE ID: 5] receiving	acquiring, identifying, generating, providing, determining, collecting, establishing	[TRANSITIVE ID: 5] maintaining
[FEATURE ID: 6] network device identifier	device, name, network, link, message, identification, wiring	[FEATURE ID: 6] wiring diagram, device address, self
[TRANSITIVE ID: 7] corresponding	associated, appropriate, belonging, mapped, attached, linked, accessible	[TRANSITIVE ID: 7] corresponding, coupled, matching device addresses, existing
[FEATURE ID: 8] repository, frame, proper syntax	template, table, structure, database, memory, directory, group	[FEATURE ID: 8] topology map, configuration database, zone
[FEATURE ID: 9] device	user, specific device, different device, given device	[FEATURE ID: 9] new device
[FEATURE ID: 10] claim	requirement, preceding claim, step, claimed, clair, embodiment, figure	[FEATURE ID: 10] claim
[FEATURE ID: 11] step	process step, first step, step of, sub step, initial step, previous step, preceding step	[FEATURE ID: 11] step
[FEATURE ID: 12] network devices, computer program product, attribute value	equipment, nodes, connections, data, systems, buses, ports	[FEATURE ID: 12] device addresses, devices, protocol, seat peripherals, seat electronics units
[FEATURE ID: 13] format	configuration, definition, implementation	[FEATURE ID: 13] ID sequence
[FEATURE ID: 14] configuration records	tables, entries, locations	[FEATURE ID: 14] network protocol addresses
1 . A method [FEATURE ID: 1] for communicating [TRANSITIVE ID: 2] with a network device [FEATURE ID: 1] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier [FEATURE ID: 6] , the network device identifier corresponding [TRANSITIVE ID: 7] to the network device ; retrieving [TRANSITIVE ID: 2] a command [FEATURE ID: 1] - format template from a repository [FEATURE ID: 8] containing [TRANSITIVE ID: 3] a plurality of command - format templates , wherein the command - format template indicates how to construct a device [FEATURE ID: 9] - specific command for the network device and includes [TRANSITIVE ID: 3] an attribute field ; identifying [TRANSITIVE ID: 2] attribute data corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 10] 1 , wherein the step [FEATURE ID: 11] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 1] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 8] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 4] of the network device in accordance with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 12] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 1] and is in the proper syntax [FEATURE ID: 8] and format [FEATURE ID: 13] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 1] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records [FEATURE ID: 14] , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 12] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 12]		1 . A method [FEATURE ID: 1] of automatically mapping [TRANSITIVE ID: 2] device addresses [FEATURE ID: 12] to physical locations [FEATURE ID: 4] of devices [FEATURE ID: 12] within a bus structure [FEATURE ID: 1] corresponding [TRANSITIVE ID: 7] to the device addresses , comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 1] of : a. maintaining [TRANSITIVE ID: 5] a wiring database [FEATURE ID: 1] including [TRANSITIVE ID: 3] wiring diagram [FEATURE ID: 6] and physical locations of devices ; b. maintaining a topology map [FEATURE ID: 8] representing [TRANSITIVE ID: 3] device addresses of devices coupled [TRANSITIVE ID: 7] to the bus structure ; and c. comparing [TRANSITIVE ID: 2] the wiring database to the topology map and matching device addresses [FEATURE ID: 7] of devices coupled to the bus structure to physical locations of devices . 2 . The method as claimed in claim [FEATURE ID: 10] 1 wherein each device address [FEATURE ID: 6] is unique and further wherein when an existing [TRANSITIVE ID: 7] device is replaced by a new device [FEATURE ID: 9] , the device address of the new device is different than the device address of the existing device . 3 . The method as claimed in claim 1 further comprising the step [FEATURE ID: 11] of forming a configuration database [FEATURE ID: 8] including physical locations and corresponding device addresses . 4 . The method as claimed in claim 3 further comprising the step of matching the device addresses to network protocol addresses [FEATURE ID: 14] corresponding to physical locations of devices . 5 . The method as claimed in claim 1 wherein the bus structure is an IEEE 1394 serial bus network [FEATURE ID: 1] . 6 . The method as claimed in claim 5 wherein the step of maintaining the topology map further comprises automatically generating the topology map during a self [FEATURE ID: 6] - ID sequence [FEATURE ID: 13] of IEEE 1394 protocol [FEATURE ID: 12] . 7 . The method as claimed in claim 1 wherein the method is implemented within an in - flight entertainment system for use on board an aircraft . 8 . The method as claimed in claim 7 wherein the devices are seat CPUs coupled to control passenger sets [FEATURE ID: 4] of seat peripherals [FEATURE ID: 12] through which passengers have access to the in - flight entertainment system . 9 . The method as claimed in claim 8 wherein the wiring database is entered into and maintained by a system manager unit [FEATURE ID: 1] within a headend [FEATURE ID: 1] of the system . 10 . The method as claimed in claim 9 wherein the topology map is automatically generated for a zone [FEATURE ID: 8] within the aircraft by a zone bridge unit [FEATURE ID: 1] coupled to one or more seat electronics units [FEATURE ID: 12]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6131118A Filed: 1998-07-07 Issued: 2000-10-10 Patent Holder: (Original Assignee) Compaq Computer Corp     (Current Assignee) Hewlett Packard Enterprise Development LP Inventor(s): Richard A. Stupek, Jr., William D. Justice, Jr., James A. Rozzi Title: Flexible display of management data in a programmable event driven processing system
[FEATURE ID: 1] method, command, device, step, HTTP message, frame, network, central repository, configuration record, central storage location, header portion, attribute value	database, computer, request, server, protocol, message, response	[FEATURE ID: 1] management server, network, programmable event, basic function, first executable component
[TRANSITIVE ID: 2] communicating	processing, integration, use	[TRANSITIVE ID: 2] access
[FEATURE ID: 3] network device, proper syntax	controller, structure, processor, configuration, component, mechanism, template	[FEATURE ID: 3] construction editor, dispatcher
[TRANSITIVE ID: 4] comprising, containing	including, comprises, having, providing, with, includes, of	[TRANSITIVE ID: 4] comprising
[FEATURE ID: 5] steps, operation, network devices	elements, entities, functions, operations, applications, action, activities	[FEATURE ID: 5] processing, management events, executable components, instances, operation
[FEATURE ID: 6] network device identifier	data, request, message, response, signal, query, command	[FEATURE ID: 6] driven, boolean result
[TRANSITIVE ID: 7] corresponding	specific, associated, directed, indicating, pertaining, relating, referring	[TRANSITIVE ID: 7] corresponding
[FEATURE ID: 8] repository, attribute data	storage, structure, metadata, information, memory, architecture, input	[FEATURE ID: 8] interconnection logic, interconnection data
[TRANSITIVE ID: 9] indicates, includes	provides, controls, manages, defines, handles, allows, monitors	[TRANSITIVE ID: 9] facilitates, performs, receives, supports, enables
[TRANSITIVE ID: 10] construct	describe, handle, specify, provide, implement, define	[TRANSITIVE ID: 10] perform
[FEATURE ID: 11] attribute field, XML message, format, identifier, article	object, application, instruction, indicator, event, configuration, definition	[FEATURE ID: 11] listener, instance, internal event
[FEATURE ID: 12] claim	requirement, item, preceding claim, previous claim, the claim, statement, clause	[FEATURE ID: 12] claim
[FEATURE ID: 13] directory tree	structure, mapping, hierarchy	[FEATURE ID: 13] relationship
[FEATURE ID: 14] indication	expression, description, arrangement	[FEATURE ID: 14] construction
[FEATURE ID: 15] accordance	real time, proportion, relationship, according, connection	[FEATURE ID: 15] response
[FEATURE ID: 16] populated attribute field	event, message, information	[FEATURE ID: 16] event notifications
[FEATURE ID: 17] computer program product	software, network, memory	[FEATURE ID: 17] event detection logic
1 . A method [FEATURE ID: 1] for communicating [TRANSITIVE ID: 2] with a network device [FEATURE ID: 3] , the method comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : receiving a network device identifier [FEATURE ID: 6] , the network device identifier corresponding [TRANSITIVE ID: 7] to the network device ; retrieving a command [FEATURE ID: 1] - format template from a repository [FEATURE ID: 8] containing [TRANSITIVE ID: 4] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 9] how to construct [TRANSITIVE ID: 10] a device [FEATURE ID: 1] - specific command for the network device and includes [TRANSITIVE ID: 9] an attribute field [FEATURE ID: 11] ; identifying attribute data [FEATURE ID: 8] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 12] 1 , wherein the step [FEATURE ID: 1] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 13] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 11] comprising at least an indication [FEATURE ID: 14] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 1] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 1] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 5] of the network device in accordance [FEATURE ID: 15] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 5] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 16] and is in the proper syntax [FEATURE ID: 3] and format [FEATURE ID: 11] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 11] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 1] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 17] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 1] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 11]		1 . A management server [FEATURE ID: 1] for coupling to a network [FEATURE ID: 1] that facilitates [TRANSITIVE ID: 9] and performs [TRANSITIVE ID: 9] programmable event [FEATURE ID: 1] driven [TRANSITIVE ID: 6] processing [FEATURE ID: 5] , comprising [TRANSITIVE ID: 4] : event detection logic [FEATURE ID: 17] , for coupling to the network , that receives [TRANSITIVE ID: 9] any of a plurality of event notifications [FEATURE ID: 16] transmitted via the network , each event notification corresponding [TRANSITIVE ID: 7] to the occurrence of at least one of a plurality of management events [FEATURE ID: 5] , and that supports [TRANSITIVE ID: 9] registration of at least one listener [FEATURE ID: 11] of any of the plurality of management events ; a plurality of executable components [FEATURE ID: 5] that each perform [TRANSITIVE ID: 10] a basic function [FEATURE ID: 1] ; a construction editor [FEATURE ID: 3] that enables [TRANSITIVE ID: 9] access [FEATURE ID: 2] of the plurality of executable components to generate at least one construction [FEATURE ID: 14] including at least one instance [FEATURE ID: 11] of the plurality of executable components , that facilitates defining a relationship [FEATURE ID: 13] between instances [FEATURE ID: 5] of executable components comprising the at least one construction ; the at least one construction , when invoked , executing the at least one instance of the plurality of executable components to perform at least one desired operation [FEATURE ID: 5] in response [FEATURE ID: 15] to the occurrence of the at least one of the plurality of management events ; and the event detection logic receiving an event notification corresponding to the at least one of the plurality of management events and invoking the at least one construction . 2 . The management server of claim [FEATURE ID: 12] 1 , further comprising : the at least one construction comprising a plurality of constructions , each registered with the event detection logic as a listener of at least one of the plurality of management events . 3 . The management server of claim 2 , the event detection logic further comprising : interconnection logic [FEATURE ID: 8] that enables registration of internal and external events including the plurality of management events ; the plurality of constructions including a first construction that generates an internal event [FEATURE ID: 11] when invoked ; the plurality of constructions including a second construction registered with the interconnection logic as a listener of the internal event generated by the first construction ; and the interconnection logic invoking the second construction in response to the internal event generated by the first construction . 4 . The management server of claim 1 , the at least one construction comprising : the at least one construction including at least two instances of the plurality of executable components ; interconnection data [FEATURE ID: 8] that incorporates a relationship between the at least two instances of the plurality of executable components ; and a dispatcher [FEATURE ID: 3] that facilitates execution of the at least two instances of the plurality of executable components according to the interconnection data . 5 . The management server of claim 4 , the at least two instances of the plurality of executable components further comprising : a first executable component [FEATURE ID: 1] that generates a boolean result [FEATURE ID: 6]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6128729A Filed: 1997-12-16 Issued: 2000-10-03 Patent Holder: (Original Assignee) Hewlett Packard Co     (Current Assignee) Hewlett Packard Enterprise Development LP Inventor(s): Karen E. Kimball, Robert L. Faulk, Jr., Robert M. McGuire Title: Method and system for automatic configuration of network links to attached devices
[FEATURE ID: 1] method, repository, device, step, network, central repository, identifier, computer program product, header portion, article, manufacture	system, computer, server, host, processor, memory, switch	[FEATURE ID: 1] method, multi-segment network device, first link, device, network device, hardware, same housing, network bridge
[FEATURE ID: 2] network device	node, controller, relay, processor, hub, terminal, host	[FEATURE ID: 2] first bridging device, repeating, same external bridging device, switch, router
[TRANSITIVE ID: 3] comprising, containing	comprises, having, including, providing, incorporating, defining, executing	[TRANSITIVE ID: 3] comprising, has
[FEATURE ID: 4] steps	following, action, sequence, act, method, following steps, method steps	[FEATURE ID: 4] step, substep, substeps, segments, actions
[TRANSITIVE ID: 5] receiving, retrieving, identifying	providing, determining, collecting, processing, storing, requesting, acquiring	[TRANSITIVE ID: 5] performing
[TRANSITIVE ID: 6] corresponding	associated, coupled, used, applicable, linked, appropriate, present	[TRANSITIVE ID: 6] attached, available
[TRANSITIVE ID: 7] indicates, includes	establishes, determines, provides, defines, decides, comprises, assigns	[TRANSITIVE ID: 7] configures, detects
[FEATURE ID: 8] attribute field	address, interface, object	[FEATURE ID: 8] agent
[FEATURE ID: 9] attribute data, populated attribute field	attributes, metadata, configuration, input, content, parameters, property	[FEATURE ID: 9] information
[FEATURE ID: 10] claim	requirement, preceding claim, step, claimed, clair, embodiment, figure	[FEATURE ID: 10] claim
[FEATURE ID: 11] directory tree	path, node, link, list, network, ring, channel	[FEATURE ID: 11] segment, segment step
[FEATURE ID: 12] frame	bundle, combination, pair	[FEATURE ID: 12] maximum number
[FEATURE ID: 13] operation	features, characteristics, parameters	[FEATURE ID: 13] constraints
[FEATURE ID: 14] network devices	resources, ports, segments, interfaces, paths, connections, bridges	[FEATURE ID: 14] network device connections, other links, links, devices
[FEATURE ID: 15] central storage location	device, memory, system	[FEATURE ID: 15] housing
1 . A method [FEATURE ID: 1] for communicating with a network device [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier , the network device identifier corresponding [TRANSITIVE ID: 6] to the network device ; retrieving [TRANSITIVE ID: 5] a command - format template from a repository [FEATURE ID: 1] containing [TRANSITIVE ID: 3] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 7] how to construct a device [FEATURE ID: 1] - specific command for the network device and includes [TRANSITIVE ID: 7] an attribute field [FEATURE ID: 8] ; identifying [TRANSITIVE ID: 5] attribute data [FEATURE ID: 9] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 10] 1 , wherein the step [FEATURE ID: 1] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 11] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 12] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 13] of the network device in accordance with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 14] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 9] and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 1] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 15] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 1] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 1] of manufacture [FEATURE ID: 1]		1 . A method [FEATURE ID: 1] by which a multi-segment network device [FEATURE ID: 1] configures [TRANSITIVE ID: 7] network device connections [FEATURE ID: 14] to a first link [FEATURE ID: 1] , the method comprising [TRANSITIVE ID: 3] the following step [FEATURE ID: 4] : ( a ) if the multi-segment network device detects [TRANSITIVE ID: 7] that a first bridging device [FEATURE ID: 2] is attached [TRANSITIVE ID: 6] to the first link and that no repeating [TRANSITIVE ID: 2] device [FEATURE ID: 1] is attached to the first link , performing [TRANSITIVE ID: 5] the following substep [FEATURE ID: 4] : ( a. 1 ) if the first bridging device has [TRANSITIVE ID: 3] been designated as a preferred bridging device , performing the following substeps [FEATURE ID: 4] : adding the first link to a segment [FEATURE ID: 11] , if available [FEATURE ID: 6] , that does not include a link to the first bridging device and if there is no segment available that does not include a link to the first bridging device , disabling the first link . 2 . A method as in claim [FEATURE ID: 10] 1 wherein step ( a ) additionally includes the following substep : ( a. 2 ) if the first bridging device has not been designated as the preferred bridging device , performing the following substeps : if no other links [FEATURE ID: 14] to the first bridging device have been configured , adding the first link to any supported segment , and if another link to the first bridging device has already been configured , disabling the first link . 3 . A method as in claim 1 additionally comprising the following substep : ( b ) if the multi-segment network device detects that a first repeating device is attached to the first link , performing the following substep : ( b. 1 ) if another link to the first repeating device has already been configured , disabling the first link . 4 . A method as in claim 3 wherein step ( b ) additionally includes the following substep : ( b. 2 ) if another link to the first repeating device has not already been configured and the preferred bridging device is also attached to the first link , performing the following substeps : adding the first link to a segment , if available , that does not include a link to the preferred bridging device , and if there is no segment available that does not include a link to the preferred bridging device , disabling the first link . 5 . A method as in claim 4 wherein step ( b ) additionally includes the following substep : ( b. 3 ) if another link to the first repeating device has not already been configured and a bridging device which is not the preferred bridging device is attached to the first link , performing the following substep : adding the first link to any supported segment . 6 . A method by which a multi-segment network device configures network device connections to a first link , the method comprising the following step : ( a ) if the network device [FEATURE ID: 1] detects that a first repeating device is attached to the first link , performing the following substeps : ( a. 1 ) if another link to the first repeating device has already been configured , disabling the first link ( a. 2 ) if another link to the first repeating device has not already been configured and a preferred bridging device is also attached to the first link , performing the following substeps : adding the first link to a segment , if available , that does not include a link to the preferred bridging device , and if there is no segment available that does not include a link to the preferred bridging device , disabling the first link . 7 . A method as in claim 6 wherein step ( a ) additionally includes the following substep : ( a. 3 ) if another link to the first repeating device has not already been configured and a bridging device which is not the preferred bridging device is attached to the first link , performing the following substep : adding the first link to any supported segment . 8 . A multi-segment network device comprising : a plurality of segments [FEATURE ID: 4] ; a plurality of links [FEATURE ID: 14] ; an agent [FEATURE ID: 8] used to configure network device connections to the plurality of links , the agent adding the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects that a first bridging device is attached to the first link , that no repeating device is attached to the first link and that the first bridging device has been designated as a preferred bridging device , the agent disabling the first link when the first bridging device is attached to the first link , no repeating device is attached to the first link , the first bridging device has been designated as the preferred bridging device and there is available no segment that does not include a link to the first bridging device . 9 . A multi-segment network device as in claim 8 wherein the agent adds the first link to any supported segment when the multi-segment network device detects that a first bridging device is attached to the first link , that no repeating device is attached to the first link , that the first bridging device has not been designated as the preferred bridging device , and that no other links to the first bridging device have been configured , and the agent disables the first link when the multi-segment network device detects that a first bridging device is attached to the first link , that no repeating device is attached to the first link , that the first bridging device has not been designated as the preferred bridging device , and that another link to the first bridging device has already been configured . 10 . A multi-segment network device as in claim 8 , wherein the agent disables the first link when the multi-segment network device detects a first repeating device is attached to the first link and that another link to the first repeating device has already been configured , disabling the first link . 11 . A multi-segment network device as in claim 10 , wherein the agent adds the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured and that the preferred bridging device is also attached to the first link , and the agent disables the first link when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , that the preferred bridging device is also attached to the first link , and that there is no available segment that does not include a link to the preferred bridging device . 12 . A multi-segment network device as in claim 11 wherein the agent adds the first link to any supported segment step [FEATURE ID: 11] when the multi-segment network device detects the first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , and that a bridging device which is not the preferred bridging device is attached to the first link . 13 . A multi-segment network device comprising : a plurality of segments ; a plurality of links ; an agent used to configure network device connections to the plurality of links , the agent adding the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured and that the preferred bridging device is also attached to the first link , and the agent disabling the first link when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , that the preferred bridging device is also attached to the first link , and that there is no available segment that does not include a link to the preferred bridging device . 14 . A multi-segment network device as in claim 13 wherein the agent adds the first link to any supported segment step when the multi-segment network device detects the first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , and that a bridging device which is not the preferred bridging device is attached to the first link . 15 . A method by which a multi-segment network device configures network device connections to a first link , the method comprising the following step : ( a ) if the multi-segment network device detects that a first bridging device is attached to the first link and that no repeating device is attached to the first link , performing the following substep : ( a. 1 ) if the first bridging device has been designated as a preferred bridging device , performing the following substeps : adding the first link to a segment , if available , that does not include a link to the first bridging device and if there is no segment available that does not include a link to the first bridging device , making the first link a redundant connection . 16 . A method as in claim 15 wherein step ( a ) additionally includes the following substep : ( a. 2 ) if the first bridging device has not been designated as the preferred bridging device , performing the following substeps : if no other links to the first bridging device have been configured , adding the first link to any supported segment , and if another link to the first bridging device has already been configured , making the first link a redundant connection . 17 . A method as in claim 16 additionally comprising the following substep : ( b ) if the multi-segment network device detects that a first repeating device is attached to the first link , performing the following substep : ( b. 1 ) if another link to the first repeating device has already been configured , making the first link a redundant connection . 18 . A method as in claim 17 wherein step ( b ) additionally includes the following substep : ( b. 2 ) if another link to the first repeating device has not already been configured and the preferred bridging device is also attached to the first link , performing the following substeps : adding the first link to a segment , if available , that does not include a link to the preferred bridging device , and if there is no segment available that does not include a link to the preferred bridging device , making the first link a redundant connection . 19 . A method by which a multi-segment network device configures network device connections to a first link , the method comprising the following step : ( a ) if the network device detects that a first repeating device is attached to the first link , performing the following substeps : ( a. 1 ) if another link to the first repeating device has already been configured , making the first link a redundant connection ( a. 2 ) if another link to the first repeating device has not already been configured and a preferred bridging device is also attached to the first link , performing the following substeps : adding the first link to a segment , if available , that does not include a link to the preferred bridging device , and if there is no segment available that does not include a link to the preferred bridging device , making the first link a redundant connection . 20 . A multi-segment network device comprising : a plurality of segments ; a plurality of links ; an agent used to configure network device connections to the plurality of links , the agent adding the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects that a first bridging device is attached to the first link , that no repeating device is attached to the first link and that the first bridging device has been designated as a preferred bridging device , the agent making the first link a redundant connection when the first bridging device is attached to the first link , no repeating device is attached to the first link , the first bridging device has been designated as the preferred bridging device and there is available no segment that does not include a link to the first bridging device . 21 . A multi-segment network device as in claim 20 , wherein the agent disables the first link when the multi-segment network device detects a first repeating device is attached to the first link and that another link to the first repeating device has already been configured , making the first link a redundant connection . 22 . A multi-segment network device as in claim 21 , wherein the agent adds the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured and that the preferred bridging device is also attached to the first link , and the agent disables the first link when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , that the preferred bridging device is also attached to the first link , and that there is no available segment that does not include a link to the preferred bridging device . 23 . A multi-segment network device as in claim 22 wherein the agent adds the first link to any supported segment step when the multi-segment network device detects the first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , and that a bridging device which is not the preferred bridging device is attached to the first link . 24 . A multi-segment network device comprising : a plurality of segments ; a plurality of links ; an agent used to configure network device connections to the plurality of links , the agent adding the first link to a segment , if available , that does not include a link to the preferred bridging device when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured and that the preferred bridging device is also attached to the first link , and the agent making the first link a redundant connection when the multi-segment network device detects a first repeating device is attached to the first link , that another link to the first repeating device has not already been configured , that the preferred bridging device is also attached to the first link , and that there is no available segment that does not include a link to the preferred bridging device . 25 . A method by which a multi-segment network device configures network device connections to a first link , the method comprising the following step : ( a ) if the network device detects that a first repeating device is attached to the first link , performing the following substeps : ( a. 1 ) if another link to the first repeating device has already been configured , disabling the first link . 26 . A multi-segment network device comprising : a plurality of segments ; a plurality of links ; and , an agent used to configure the plurality of links , the agent obtaining information [FEATURE ID: 9] about devices [FEATURE ID: 14] connected to links in the plurality of links , and based on the information , the agent configuring each link by performing one of the following actions [FEATURE ID: 4] for each link : disabling the link , and assigning the link to one of the plurality of segments ; wherein in configuring links , the agent does not allow two links connected to a same external bridging device [FEATURE ID: 2] to be assigned to a same segment from the plurality of segments . 27 . A multi-segment network device as in claim 26 , wherein in configuring links , when more than one link from the plurality of links are connected to a first bridging device , a maximum number [FEATURE ID: 12] of links connected to the first bridging device are enabled with the following constraints [FEATURE ID: 13] : no looping is caused , and no two links connected to the first bridging device are assigned to a same segment from the plurality of segments . 28 . A multi-segment network device as in claim 26 wherein the agent is embedded within hardware [FEATURE ID: 1] that is in a same housing [FEATURE ID: 1] that houses hardware implementing the plurality of segments . 29 . A multi-segment network device as in claim 26 wherein the agent is embedded within hardware that is external to housing [FEATURE ID: 15] that houses hardware implementing the plurality of segments . 30 . A multi-segment network device as in claim 26 wherein the multi-segment network device is one of the following : a network bridge [FEATURE ID: 1] ; a switch [FEATURE ID: 2] ; a router [FEATURE ID: 2]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6122671A Filed: 1995-12-08 Issued: 2000-09-19 Patent Holder: (Original Assignee) AMSC Subsidiary Corp     (Current Assignee) ATC Technologies LLC Inventor(s): Samuel A. Farrar, Jr., Joseph A. Gruessing, Jr. Title: Mobile communications from computer aided dispatch system via a customer premises gateway for satellite communication system
[FEATURE ID: 1] method, directory tree, frame, accordance, header portion, format instruction, article	network, controller, server, device, terminal, gateway, transceiver	[FEATURE ID: 1] switching, office, satellite antenna, mobile communication system, satellite, central controller, system, customer premises gateway system, middleware service provider, CAD system, network manager, communications driver, communication protocol, physical transport medium
[TRANSITIVE ID: 2] communicating, corresponding	associated, coupled, coupling, linked, engaging, acting, communication	[TRANSITIVE ID: 2] communicating
[FEATURE ID: 3] network device, network device identifier, device, HTTP message, operation, network, central repository, populated attribute field, proper syntax, configuration record, central storage location, computer program product	command, configuration, data, database, gateway, structure, system	[FEATURE ID: 3] mobile satellite system, satellite communication, computer, central controller communication services, satellite message communication services, message, central controller interface, CAD system access
[TRANSITIVE ID: 4] comprising, indicates, includes, identifying	providing, containing, incorporating, comprises, provides, defining, performing	[TRANSITIVE ID: 4] including, having, comprising, supporting
[FEATURE ID: 5] steps	operations, requests, functions, services, calls, applications, tasks	[FEATURE ID: 5] customer messages, middleware services, middleware functions, control information, messages
[TRANSITIVE ID: 6] receiving, retrieving	requesting, collecting, providing, transferring, capturing, communicating, transmitting	[TRANSITIVE ID: 6] sending, receiving
[FEATURE ID: 7] command	instruction, data, message	[FEATURE ID: 7] aided
[FEATURE ID: 8] repository, indication, format	representation, description, database, structure, definition, configuration, specification	[FEATURE ID: 8] library
[TRANSITIVE ID: 9] containing	supporting, managing, maintaining	[TRANSITIVE ID: 9] providing
[TRANSITIVE ID: 10] construct	use, communicate, provide	[TRANSITIVE ID: 10] interface
[FEATURE ID: 11] attribute data, configuration records	the, information, and, requests, sms, message, inbound	[FEATURE ID: 11] outbound messages, inbound messages
[FEATURE ID: 12] network devices, attribute value	stations, carriers, users, cells, data, content, information	[FEATURE ID: 12] satellite messages
[FEATURE ID: 13] identifier	api, application, interface, agent, intermediate	[FEATURE ID: 13] Application Interface Agent, application programmer interface, API
1 . A method [FEATURE ID: 1] for communicating [TRANSITIVE ID: 2] with a network device [FEATURE ID: 3] , the method comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : receiving [TRANSITIVE ID: 6] a network device identifier [FEATURE ID: 3] , the network device identifier corresponding [TRANSITIVE ID: 2] to the network device ; retrieving [TRANSITIVE ID: 6] a command [FEATURE ID: 7] - format template from a repository [FEATURE ID: 8] containing [TRANSITIVE ID: 9] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 4] how to construct [TRANSITIVE ID: 10] a device [FEATURE ID: 3] - specific command for the network device and includes [TRANSITIVE ID: 4] an attribute field ; identifying [TRANSITIVE ID: 4] attribute data [FEATURE ID: 11] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim 1 , wherein the step of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 1] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication [FEATURE ID: 8] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 3] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 1] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 3] of the network device in accordance [FEATURE ID: 1] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 3] formed of a plurality of network devices [FEATURE ID: 12] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 3] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 3] and is in the proper syntax [FEATURE ID: 3] and format [FEATURE ID: 8] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 13] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 3] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 3] configured to store a plurality of configuration records [FEATURE ID: 11] , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 3] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction [FEATURE ID: 1] ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 12] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 1]		1 . In a mobile satellite system [FEATURE ID: 3] including [TRANSITIVE ID: 4] a satellite communication [FEATURE ID: 3] switching [TRANSITIVE ID: 1] office [FEATURE ID: 1] having [TRANSITIVE ID: 4] a satellite antenna [FEATURE ID: 1] for providing [TRANSITIVE ID: 9] communication of satellite messages [FEATURE ID: 12] with a mobile communication system [FEATURE ID: 1] via a satellite [FEATURE ID: 1] , a central controller [FEATURE ID: 1] communicating [TRANSITIVE ID: 2] with the mobile communication system via the satellite communication switching office , and a computer [FEATURE ID: 3] aided [TRANSITIVE ID: 7] dispatch ( CAD ) system [FEATURE ID: 1] sending [TRANSITIVE ID: 6] and receiving [TRANSITIVE ID: 6] customer messages [FEATURE ID: 5] to / from the mobile satellite system via a customer premises gateway system [FEATURE ID: 1] , the customer premises gateway system comprising [TRANSITIVE ID: 4] : a middleware service provider [FEATURE ID: 1] supporting [TRANSITIVE ID: 4] central controller communication services [FEATURE ID: 3] , satellite message communication services [FEATURE ID: 3] , and network management communication services , said middleware service provider configuring middleware services [FEATURE ID: 5] for invocation ; an Application Interface Agent [FEATURE ID: 13] ( AIA ) receiving outbound messages [FEATURE ID: 11] from the CAD system [FEATURE ID: 1] , and formatting the outbound messages as application programmer interface [FEATURE ID: 13] ( API [FEATURE ID: 13] ) calls to the middleware service provider , said AIA receiving inbound messages [FEATURE ID: 11] from the middleware service provider , interpreting the inbound messages , and delivering the inbound messages to the CAD system ; an application programmer interface ( API ) including a library [FEATURE ID: 8] of middleware functions [FEATURE ID: 5] and the API calls to invoke the middleware services of said middleware service provider ; a network manager [FEATURE ID: 1] performing message [FEATURE ID: 3] logging provided by said middleware service provider including logging control information [FEATURE ID: 5] for messages [FEATURE ID: 5] handled by said middleware service provider ; a communications driver [FEATURE ID: 1] including a communication protocol [FEATURE ID: 1] to interface [FEATURE ID: 10] with a physical transport medium [FEATURE ID: 1] of the CAD system ; and a central controller interface [FEATURE ID: 3] providing an interface between the CAD system and the central controller and providing the CAD system access [FEATURE ID: 3]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6122664A Filed: 1996-06-27 Issued: 2000-09-19 Patent Holder: (Original Assignee) Bull SA     (Current Assignee) EVIDAN Inventor(s): Marcel Boukobza, Gerard Sitbon Title: Process for monitoring a plurality of object types of a plurality of nodes from a management node in a data processing system by distributing configured agents
[FEATURE ID: 1] method, repository, attribute field, step, directory tree, central repository, identifier, configuration record, central storage location, computer program product, header portion, article	device, system, database, network, computer, server, memory	[FEATURE ID: 1] process, management node, data processing system, node, particular domain, graphical interface, object type, monitoring process
[FEATURE ID: 2] network device, command, XML message, frame, proper syntax, format	document, configuration, protocol, structure, language, order, message	[FEATURE ID: 2] way, domain, user
[TRANSITIVE ID: 3] comprising, includes	including, comprises, having, involves, providing, executing, has	[TRANSITIVE ID: 3] comprising, distributing
[FEATURE ID: 4] steps, indicates	functions, operations, states, events, tasks, modules, data	[FEATURE ID: 4] object types, monitoring functions, modules specific, step, objects, information, actions
[TRANSITIVE ID: 5] receiving, retrieving	determining, collecting, obtaining, identifying, processing, generating, requesting	[TRANSITIVE ID: 5] monitoring, configuring, testing
[TRANSITIVE ID: 6] corresponding	belonging, dedicated, pertaining, relating, particular, applicable, linked	[TRANSITIVE ID: 6] dynamic parameters particular
[TRANSITIVE ID: 7] containing	having, including, using	[TRANSITIVE ID: 7] providing
[FEATURE ID: 8] device	service, data, command	[FEATURE ID: 8] intertype correlation
[TRANSITIVE ID: 9] identifying	checking, monitoring, and	[TRANSITIVE ID: 9] testing conditions
[FEATURE ID: 10] attribute data	values, parameters, the	[FEATURE ID: 10] static
[FEATURE ID: 11] indication	extension, implementation, arrangement, example	[FEATURE ID: 11] application
[FEATURE ID: 12] operation	status, state, characteristics	[FEATURE ID: 12] conditions
[FEATURE ID: 13] network	zone, subsystem, domain	[FEATURE ID: 13] global object
[FEATURE ID: 14] network devices	hosts, components, platforms, users, resources, entities, devices	[FEATURE ID: 14] nodes
[FEATURE ID: 15] populated attribute field, configuration records	information, parameter, configuration, data, logs, variables, statistics	[FEATURE ID: 15] measurements, parameters
[FEATURE ID: 16] attribute value	database, parameter, information	[FEATURE ID: 16] dynamic parameters relative
1 . A method [FEATURE ID: 1] for communicating with a network device [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] the steps [FEATURE ID: 4] of : receiving [TRANSITIVE ID: 5] a network device identifier , the network device identifier corresponding [TRANSITIVE ID: 6] to the network device ; retrieving [TRANSITIVE ID: 5] a command [FEATURE ID: 2] - format template from a repository [FEATURE ID: 1] containing [TRANSITIVE ID: 7] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 4] how to construct a device [FEATURE ID: 8] - specific command for the network device and includes [TRANSITIVE ID: 3] an attribute field [FEATURE ID: 1] ; identifying [TRANSITIVE ID: 9] attribute data [FEATURE ID: 10] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim 1 , wherein the step [FEATURE ID: 1] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 1] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 2] comprising at least an indication [FEATURE ID: 11] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 2] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 12] of the network device in accordance with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 13] formed of a plurality of network devices [FEATURE ID: 14] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 15] and is in the proper syntax [FEATURE ID: 2] and format [FEATURE ID: 2] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 1] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 1] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records [FEATURE ID: 15] , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 1] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 16] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 1]		1 . A process [FEATURE ID: 1] for monitoring [TRANSITIVE ID: 5] from a management node [FEATURE ID: 1] in a data processing system [FEATURE ID: 1] a plurality of object types [FEATURE ID: 4] of a plurality of nodes [FEATURE ID: 14] comprising [TRANSITIVE ID: 3] : configuring [TRANSITIVE ID: 5] and then distributing [TRANSITIVE ID: 3] monitoring functions [FEATURE ID: 4] in a filtered way [FEATURE ID: 2] from the management node to at least one autonomous agent installed on each node [FEATURE ID: 1] to be monitored , each autonomous agent comprising a plurality of monitoring modules specific [FEATURE ID: 4] to different object types or to a particular domain [FEATURE ID: 1] , wherein after said distributing step [FEATURE ID: 4] said at least one agent operates independently without direct control from the management node providing [TRANSITIVE ID: 7] intertype correlation [FEATURE ID: 8] to an autonomous agent to locally process the different object types or all of the objects [FEATURE ID: 4] of a domain [FEATURE ID: 2] defined as a global object [FEATURE ID: 13] or to feed back information [FEATURE ID: 4] to be displayed to a graphical interface [FEATURE ID: 1] of the management node , measuring , by each specific monitoring module , static [FEATURE ID: 10] and dynamic parameters particular [FEATURE ID: 6] to the object type [FEATURE ID: 1] that the specific monitoring module monitors , collecting the measurements [FEATURE ID: 15] , said collecting being performed by said autonomous agents ; testing conditions [FEATURE ID: 9] on said dynamic parameters relative [FEATURE ID: 16] to predefined thresholds , said testing [FEATURE ID: 5] being performed by said autonomous agents ; initiating actions [FEATURE ID: 4] associated with said tested conditions [FEATURE ID: 12] , which parameters [FEATURE ID: 15] , conditions and actions can be modified by a user [FEATURE ID: 2] of the management node . 2 . A monitoring process [FEATURE ID: 1] according to claim for the application [FEATURE ID: 11]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6108703A Filed: 1998-07-14 Issued: 2000-08-22 Patent Holder: (Original Assignee) Massachusetts Institute of Technology     (Current Assignee) Massachusetts Institute of Technology Inventor(s): F. Thomson Leighton, Daniel M. Lewin Title: Global hosting system
[FEATURE ID: 1] method, command, repository, step, HTTP message, network, central repository, configuration record, attribute value	server, device, system, message, database, facility, domain	[FEATURE ID: 1] hosting, framework operative, computer network, content provider server, framework, routine, web page, domain name, ramework, buddy server, failure condition, mechanism
[FEATURE ID: 2] network device, device, central storage location, computer program product	network, database, computer, server, client, proxy, controller	[FEATURE ID: 2] distributed, client machines, set, first level name server, second level name server, redundant first level name server, redundant second level name server
[TRANSITIVE ID: 3] comprising, containing, includes	including, comprises, having, has, providing, defining, involving	[TRANSITIVE ID: 3] comprising
[TRANSITIVE ID: 4] receiving, identifying	processing, defining, generating, recognizing, collecting, analyzing, detecting	[TRANSITIVE ID: 4] modifying
[FEATURE ID: 5] network device identifier, indication, format	representation, name, first, domain, protocol, definition, configuration	[FEATURE ID: 5] first level domain name service, resolution
[TRANSITIVE ID: 6] corresponding	pointing, mapped, attached, relating, referring, related, linked	[TRANSITIVE ID: 6] pretended
[TRANSITIVE ID: 7] construct	specify, represent, provide, make, define, use	[TRANSITIVE ID: 7] include
[FEATURE ID: 8] attribute field, directory tree, populated attribute field, identifier, header portion, article	address, object, instruction, option, index, item, image	[FEATURE ID: 8] object URL
[FEATURE ID: 9] attribute data	information, content, data, pages, input, the	[FEATURE ID: 9] web pages, requests
[FEATURE ID: 10] claim	step, claimed, clair, figure, paragraph, item, clause	[FEATURE ID: 10] claim
[FEATURE ID: 11] XML message	element, file, document	[FEATURE ID: 11] object
[FEATURE ID: 12] frame	link, string, header	[FEATURE ID: 12] hostname
[FEATURE ID: 13] operation, proper syntax	configuration, state, address, status, name, length, scope	[FEATURE ID: 13] path, responsibilities
[FEATURE ID: 14] accordance	proportion, correspondence, connection	[FEATURE ID: 14] response
[FEATURE ID: 15] network devices	nodes, hosts, files, machines, components, devices, pages	[FEATURE ID: 15] users, content servers, objects, servers
1 . A method [FEATURE ID: 1] for communicating with a network device [FEATURE ID: 2] , the method comprising [TRANSITIVE ID: 3] the steps of : receiving [TRANSITIVE ID: 4] a network device identifier [FEATURE ID: 5] , the network device identifier corresponding [TRANSITIVE ID: 6] to the network device ; retrieving a command [FEATURE ID: 1] - format template from a repository [FEATURE ID: 1] containing [TRANSITIVE ID: 3] a plurality of command - format templates , wherein the command - format template indicates how to construct [TRANSITIVE ID: 7] a device [FEATURE ID: 2] - specific command for the network device and includes [TRANSITIVE ID: 3] an attribute field [FEATURE ID: 8] ; identifying [TRANSITIVE ID: 4] attribute data [FEATURE ID: 9] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 10] 1 , wherein the step [FEATURE ID: 1] of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 8] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 11] comprising at least an indication [FEATURE ID: 5] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 1] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 12] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 13] of the network device in accordance [FEATURE ID: 14] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 1] formed of a plurality of network devices [FEATURE ID: 15] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 8] and is in the proper syntax [FEATURE ID: 13] and format [FEATURE ID: 5] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 8] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 1] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 2] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 2] comprising : a header portion [FEATURE ID: 8] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 1] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 8]		1 . A distributed [TRANSITIVE ID: 2] hosting [TRANSITIVE ID: 1] framework operative [FEATURE ID: 1] in a computer network [FEATURE ID: 1] in which users [FEATURE ID: 15] of client machines [FEATURE ID: 2] connect to a content provider server [FEATURE ID: 1] , the framework [FEATURE ID: 1] comprising [TRANSITIVE ID: 3] : a routine [FEATURE ID: 1] for modifying [TRANSITIVE ID: 4] at least one embedded object URL [FEATURE ID: 8] of a web page [FEATURE ID: 1] to include [TRANSITIVE ID: 7] a hostname [FEATURE ID: 12] pretended [TRANSITIVE ID: 6] to a domain name [FEATURE ID: 1] and path [FEATURE ID: 13] ; a set [FEATURE ID: 2] of content servers [FEATURE ID: 15] , distinct from the content provider server , for hosting at least some of the embedded objects [FEATURE ID: 15] of web pages [FEATURE ID: 9] that are normally hosted by the content provider server ; at least one first level name server [FEATURE ID: 2] that provides a first level domain name service [FEATURE ID: 5] ( DNS ) resolution [FEATURE ID: 5] ; and at least one second level name server [FEATURE ID: 2] that provides a second level domain name service ( DNS ) resolution ; wherein in response [FEATURE ID: 14] to requests [FEATURE ID: 9] for the web page , generated by the client machines the web page including the modified embedded object URL is served from the content provider server and the embedded object [FEATURE ID: 11] identified by the modified embedded object URL is served from a given one of the content servers as identified by the first level and second level name servers . 2 . The hosting ramework [FEATURE ID: 1] as described in claim [FEATURE ID: 10] 1 further including a redundant first level name server [FEATURE ID: 2] . 3 . The hosting framework as described in claim 1 further including a redundant second level name server [FEATURE ID: 2] . 4 . The hosting framework as described in claim 1 wherein a given one of the set of servers [FEATURE ID: 15] includes a buddy server [FEATURE ID: 1] for assuming the hosting responsibilities [FEATURE ID: 13] of the given one of the set of servers upon a given failure condition [FEATURE ID: 1] . 5 . The hosting framework as described in claim 1 wherein the second level name server includes a load balancing mechanism [FEATURE ID: 1]

---

Targeted Patent: Patent: US6978301B2 Filed: 2000-12-06 Issued: 2005-12-20 Patent Holder: (Original Assignee) Intelliden Inc     (Current Assignee) Focus Global Solutions LLC Inventor(s): Glen D. Tindal Title: System and method for configuring a network device	Cross Reference / Shared Meaning between the Lines	Charted Against: Patent: US6108699A Filed: 1997-06-27 Issued: 2000-08-22 Patent Holder: (Original Assignee) Sun Microsystems Inc     (Current Assignee) Oracle America Inc Inventor(s): Hossein Moiin Title: System and method for modifying membership in a clustered distributed computer system and updating system configuration
[FEATURE ID: 1] method, device, central repository, central storage location, header portion, attribute value, article	computer, network, server, system, memory, database, structure	[FEATURE ID: 1] method, new node, distributed, computer system, computer readable medium
[TRANSITIVE ID: 2] communicating	synchronizing, coupling, connecting	[TRANSITIVE ID: 2] adding
[FEATURE ID: 3] network device, directory tree, network	node, cloud, facility, database, list, tree, query	[FEATURE ID: 3] cluster, cluster reconfiguration message
[TRANSITIVE ID: 4] comprising, containing, indicates, includes	including, comprises, having, providing, has, defines, identifying	[TRANSITIVE ID: 4] includes, comprising, specifying
[FEATURE ID: 5] steps	blocks, components, elements	[FEATURE ID: 5] nodes
[TRANSITIVE ID: 6] receiving, retrieving, identifying	requesting, providing, generating, storing, obtaining, reading, collecting	[TRANSITIVE ID: 6] transmitting
[FEATURE ID: 7] network device identifier, attribute field, XML message, indication, HTTP message, frame, populated attribute field, identifier, configuration record	message, request, response, command, first, event, instruction	[FEATURE ID: 7] reconfiguration petition message, additional cluster reconfiguration message, first cluster reconfiguration message, second cluster reconfiguration message, third cluster reconfiguration message
[FEATURE ID: 8] command, accordance	proportion, corresponding, order, connection, request, according	[FEATURE ID: 8] response
[FEATURE ID: 9] repository, proper syntax, format	structure, storage, memory, data, context, configuration, code	[FEATURE ID: 9] information, instructions
[FEATURE ID: 10] attribute data, operation	parameters, attributes, property, metadata, characteristics, information, state	[FEATURE ID: 10] cluster configuration information
[FEATURE ID: 11] claim	the claim, step, claimed, clair, embodiment, figure, paragraph	[FEATURE ID: 11] claim
[FEATURE ID: 12] network devices	resources, nodes, network, hosts, servers, locations, components	[FEATURE ID: 12] processors, memory
[FEATURE ID: 13] computer program product	response, communication, transmission	[FEATURE ID: 13] time
[FEATURE ID: 14] least	lea of, lease, east, last, lest, most, least one	[FEATURE ID: 14] least
1 . A method [FEATURE ID: 1] for communicating [TRANSITIVE ID: 2] with a network device [FEATURE ID: 3] , the method comprising [TRANSITIVE ID: 4] the steps [FEATURE ID: 5] of : receiving [TRANSITIVE ID: 6] a network device identifier [FEATURE ID: 7] , the network device identifier corresponding to the network device ; retrieving [TRANSITIVE ID: 6] a command [FEATURE ID: 8] - format template from a repository [FEATURE ID: 9] containing [TRANSITIVE ID: 4] a plurality of command - format templates , wherein the command - format template indicates [TRANSITIVE ID: 4] how to construct a device [FEATURE ID: 1] - specific command for the network device and includes [TRANSITIVE ID: 4] an attribute field [FEATURE ID: 7] ; identifying [TRANSITIVE ID: 6] attribute data [FEATURE ID: 10] corresponding to the attribute field ; generating the device - specific command for the network device using the retrieved command - format template and the identified attribute data ; and providing the generated device - specific command to the network device . 2 . The method of claim [FEATURE ID: 11] 1 , wherein the step of retrieving the command - format templates comprises the step of : traversing a directory tree [FEATURE ID: 3] to identify the command - format template in the plurality of command - format template that corresponds to the received network device identifier . 3 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming an XML message [FEATURE ID: 7] comprising at least an indication [FEATURE ID: 7] of the attribute data . 4 . The method of claim 3 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message [FEATURE ID: 7] comprising at least an indication of the network device identifier . 5 . The method of claim 4 , wherein the step of generating the device - specific command comprises the step of : forming a frame [FEATURE ID: 7] comprising the XML message and the HTTP message . 6 . The method of claim 1 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the generated device - specific command and at least an indication of the network device identifier . 7 . The method of claim 6 , wherein the step of providing the generated device - specific command to the network device comprises the step of : pushing the frame to the network device . 8 . The method of claim 6 , further comprising the step of : extracting , at the network device , the attribute data from the frame . 9 . The method of claim 8 , further comprising the step of : altering the operation [FEATURE ID: 10] of the network device in accordance [FEATURE ID: 8] with the extracted attribute data . 10 . A method for configuring a network device located in a network [FEATURE ID: 3] formed of a plurality of network devices [FEATURE ID: 12] , the method comprising the steps of : retrieving an attribute field from a central repository [FEATURE ID: 1] , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field [FEATURE ID: 7] and is in the proper syntax [FEATURE ID: 9] and format [FEATURE ID: 9] for the network device ; and providing the generated device - specific command to the network device . 11 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming an XML message comprising at least an indication of the attribute data . 12 . The method of claim 11 , wherein the step of generating the device - specific command comprises the step of : forming an HTTP message comprising at least an indication of an identifier [FEATURE ID: 7] associated with the network device . 13 . The method of claim 12 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising the XML message and the HTTP message . 14 . The method of claim 10 , wherein the step of generating the device - specific command comprises the step of : forming a frame comprising at least an indication of the attribute data and at least an indication of a network device identifier . 15 . The method of claim 10 , wherein the step of populating the attribute field comprises the step of : retrieving a configuration record [FEATURE ID: 7] associated with the network device ; and extracting the attribute data from the retrieved configuration record . 16 . The method of claim 15 , wherein the step of retrieving the configuration record comprises the step of : retrieving the configuration record from a central storage location [FEATURE ID: 1] configured to store a plurality of configuration records , each of the plurality of configuration records corresponding to at least one of a plurality of network devices . 17 . The method of claim 10 , further comprising the step of : extracting the attribute data from the generated device - specific command . 18 . The method of claim 17 , further comprising the step of : altering the operation of the network device in accordance with the extracted attribute data . 19 . A computer program product [FEATURE ID: 13] comprising : a header portion [FEATURE ID: 1] ; and a payload portion , wherein the payload portion is formed by : receiving a network device identifier , the network device identifier corresponding to a network device ; retrieving a command - format template associated with the received network device identifier , wherein the retrieved command - format template comprises at least [FEATURE ID: 14] an attribute field and a command - format instruction ; populating the attribute field with attribute data ; and generating a device - specific command according to the command - format instruction and the attribute data . 20 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving the command - format template from a central repository , wherein the central repository is configured to store a plurality of command - format templates . 21 . The computer program product of claim 19 , wherein the payload portion is formed by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 22 . A computer program product comprising : a header portion ; and a payload portion , wherein the payload portion is formed by : retrieving an attribute field from a central repository , the attribute field being associated with the network device ; retrieving a command - format template from a repository containing a plurality of command - format templates , wherein the command - format template indicates how to construct a device - specific command for the network device ; populating the retrieved attribute field with attribute data ; generating the device - specific command for the network device using the retrieved command - format template , wherein the generated device - specific command comprises at least an indication of the populated attribute field and is in the proper syntax and format for the network device ; and providing the generated device - specific command to the network device . 23 . The computer program product of claim 22 , wherein the attribute value [FEATURE ID: 1] is identified by : retrieving a configuration record associated with the network device ; and extracting the attribute data from the retrieved configuration record . 24 . An article [FEATURE ID: 1]		1 . A method [FEATURE ID: 1] for adding [TRANSITIVE ID: 2] a new node [FEATURE ID: 1] to an existing cluster [FEATURE ID: 3] of a distributed [TRANSITIVE ID: 1] computer system [FEATURE ID: 1] , wherein the existing cluster includes [TRANSITIVE ID: 4] a plurality of existing nodes [FEATURE ID: 5] , said method comprising [TRANSITIVE ID: 4] : the new node transmitting [TRANSITIVE ID: 6] a reconfiguration petition message [FEATURE ID: 7] to each of the plurality of existing nodes ; each of the plurality of existing nodes transmitting existing cluster configuration information [FEATURE ID: 10] to the new node and to each of the remaining of the plurality of existing nodes in response [FEATURE ID: 8] to the reconfiguration petition message ; each of the plurality of existing nodes transmitting a cluster reconfiguration message [FEATURE ID: 3] specifying [TRANSITIVE ID: 4] a proposed new cluster to the new node and to each of the remaining of the plurality of existing nodes ; the new node transmitting an additional cluster reconfiguration message [FEATURE ID: 7] specifying an additional proposed new cluster to each of the plurality of existing nodes ; and each of the plurality of existing nodes and the new node each determining whether the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 2 . The method as recited in claim [FEATURE ID: 11] 1 further comprising : each of the plurality of existing nodes and the new node each storing information [FEATURE ID: 9] which defines a new cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 3 . The method as recited in claim 2 further comprising : each of the plurality of existing nodes restoring information corresponding to said existing cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are not equivalent . 4 . The method as recited in claim 1 further comprising : the new node waiting a predetermined period of time [FEATURE ID: 13] for each of the plurality of existing nodes to respond to the reconfiguration petition message . 5 . The method as recited in claim 1 further comprising : each of the plurality of existing nodes and the new node each independently deriving a corresponding proposed new cluster . 6 . The method as recited in claim 5 , wherein each of the plurality of existing nodes derives a corresponding proposed new cluster based on the existing cluster configuration information and information identifying said new node . 7 . The method as recited in claim 5 , wherein the new node derives a corresponding proposed new cluster based on the existing cluster configuration information . 8 . A computer readable medium [FEATURE ID: 1] comprising instructions [FEATURE ID: 9] for adding a new node to an existing cluster of a distributed computer system , wherein the existing cluster includes a plurality of existing nodes , wherein the instructions are executable by the distributed computer system to implement a method comprising : the new node transmitting a reconfiguration petition message to each of the plurality of existing nodes ; each of the plurality of existing nodes transmitting existing cluster configuration information to the new node and to each of the remaining of the plurality of existing nodes in response to the reconfiguration petition message ; each of the plurality of existing nodes transmitting a cluster reconfiguration message specifying a proposed new cluster to the new node and to each of the remaining of the plurality of existing nodes ; the new node transmitting an additional cluster reconfiguration message specifying an additional proposed new cluster to each of the plurality of existing nodes ; and each of the plurality of existing nodes and the new node each determining whether the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 9 . The computer readable medium as recited in claim 8 , wherein the method further comprises : each of the plurality of existing nodes and the new node each storing information which defines a new cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 10 . The computer readable medium as recited in claim 9 , wherein the method further comprises : each of the plurality of existing nodes restoring information corresponding to said existing cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are not equivalent . 11 . The computer readable medium as recited in claim 8 , wherein the method further comprises : the new node waiting a predetermined period of time for each of the plurality of existing nodes to respond to the reconfiguration petition message . 12 . The computer readable medium as recited in claim 8 , wherein the method further comprises : each of the plurality of existing nodes and the new node each independently deriving a corresponding proposed new cluster . 13 . The computer readable medium as recited in claim 12 , wherein each of the plurality of existing nodes derives a corresponding proposed new cluster based on the existing cluster configuration information and information identifying said new node . 14 . The computer readable medium as recited in claim 12 , wherein the new node derives a corresponding proposed new cluster based on the existing cluster configuration information . 15 . A distributed computer system comprising : a plurality of nodes including a plurality of processors [FEATURE ID: 12] and memory [FEATURE ID: 12] ; wherein the memory includes instructions for adding a new node to an existing cluster including a plurality of existing nodes , wherein the instructions are executable by the plurality of nodes to implement a method of : the new node transmitting a reconfiguration petition message to each of the plurality of existing nodes ; each of the plurality of existing nodes transmitting existing cluster configuration information to the new node and to each of the remaining of the plurality of existing nodes in response to the reconfiguration petition message ; each of the plurality of existing nodes transmitting a cluster reconfiguration message specifying a proposed new cluster to the new node and to each of the remaining of the plurality of existing nodes ; the new node transmitting an additional cluster reconfiguration message specifying an additional proposed new cluster to each of the plurality of existing nodes ; and each of the plurality of existing nodes and the new node each determining whether the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 16 . The distributed computer system as recited in claim 15 , wherein the method further comprises : each of the plurality of existing nodes and the new node each storing information which defines a new cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are equivalent . 17 . The distributed computer system as recited in claim 16 , wherein the method further comprises : each of the plurality of existing nodes restoring information corresponding to said existing cluster in response to determining that the proposed new clusters specified in the cluster reconfiguration messages are not equivalent . 18 . The distributed computer system as recited in claim 16 , wherein the method further comprises : the new node waiting a predetermined period of time for each of the plurality of existing nodes to respond to the reconfiguration petition message . 19 . The distributed computer system as recited in claim 15 , wherein the method further comprises : each of the plurality of existing nodes and the new node each independently deriving a corresponding proposed new cluster . 20 . The distributed computer system as recited in claim 19 , wherein each of the plurality of existing nodes derives a corresponding proposed new cluster based on the existing cluster configuration information and information identifying said new node . 21 . The distributed computer system as recited in claim 19 , wherein the new node derives a corresponding proposed new cluster based on the existing cluster configuration information . 22 . A method for adding a new node to an existing cluster of a distributed computer system , wherein the existing cluster includes at least [FEATURE ID: 14] a first node and a second node , said method comprising : the new node transmitting a reconfiguration petition message to the first node and the second node ; the first node transmitting existing cluster configuration information to the new node and to the second node in response to the reconfiguration petition message ; the second node transmitting existing cluster configuration information to the new node and to the first node in response to the reconfiguration petition message ; the first node transmitting a first cluster reconfiguration message [FEATURE ID: 7] specifying a first proposed new cluster to the new node and to the second node ; the second node transmitting a second cluster reconfiguration message [FEATURE ID: 7] specifying a second proposed new cluster to the new node and to the first node ; the new node transmitting a third cluster reconfiguration message [FEATURE ID: 7]

---