US6292942B1 - Manager for dynamic complex systems - Google Patents
Manager for dynamic complex systems Download PDFInfo
- Publication number
- US6292942B1 US6292942B1 US09/206,213 US20621398A US6292942B1 US 6292942 B1 US6292942 B1 US 6292942B1 US 20621398 A US20621398 A US 20621398A US 6292942 B1 US6292942 B1 US 6292942B1
- Authority
- US
- United States
- Prior art keywords
- management
- manager
- kernel
- layer
- kernels
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Expired - Fee Related
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/02—Standardisation; Integration
- H04L41/0213—Standardised network management protocols, e.g. simple network management protocol [SNMP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/16—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks using machine learning or artificial intelligence
Definitions
- the present invention relates to the management of systems which may be dynamic and complex and is particularly concerned with a system manager.
- Managed systems may be of any kind or classification or combination of kinds and classifications including, but not limited to: computer software, computer software objects, computer hardware, computer operating systems, computer applications, computer communications, computer processing, computer data storage and/or access and/or retrieval, nodal or network management systems, computer networking, neural and/or fuzzy computer implementations and/or applications, systems where the Heisenberg Uncertainty Principle must be considered (e.g., integrated circuit systems and molecular, atomic and subatomic systems and experiments), computer graphic design, communication systems employing any method or medium, electrical, mechanical, physical, chemical, manufacturing, electromechanical, electro-physical, electrochemical, economic, financial, business, accounting, organizational, biological, sociological, political, psychological, medical, experimental systems of any and all kinds, observational, data collection, expert systems, artificial intelligence systems, navigational, flight, military, surveillance, theoretical (including computer modelling), or any other such system, existing now or in the future.
- computer software computer software objects, computer hardware, computer operating systems, computer applications, computer communications, computer processing, computer data storage and/or
- An entity of a managed system is a portion, division, or constituent of the whole that is separate either in reality or in thought only. Entities of a system can be modelled as sets of a universal class of the system.
- a class is a collection of members.
- the class of software options in a particular software system is made up of all software options in the system.
- a particular class may be specified by either listing all of its members or by stating some condition of membership.
- the class of software options in a particular software system may be specified either by listing all such options (e.g., by name or code number) or by stating that “all software options in the software system belong to the class of software options”.
- Identity of classes is identity of membership not identity of specifying conditions. It is important to note that, while class inclusion is transitive, class membership is not.
- “options” can be considered a class of software. Individual options are members of the class “options”. But, individual options, although included in the class software are not a class of software as, if an option is added, the number of classes of software does not increase.
- Hierarchical relationships are required, both in reality and in Class Theory, or unreasonableities result in attempting entity management.
- Propositional calculus requires that, for every statable condition, there be a class of entities that satisfy that condition. This Principle of Comprehension can only be met, so far as is known, by placing entities to be managed in class hierarchies with the universal class U at a tier zero and sets on the other tiers.
- a set is a class that is itself a member of some class.
- membership function values lie in a range (0 ⁇ m F 1), with the equalities reducing fuzzy logic to crisp logic. It is important to realize that m F is not a probability value.
- Entities can have diverse intrinsic natures and yet belong to the same system. For example, both hardware and software entities make up a digital computing system. Entities of entities are sets at a lower hierarchical level than simply entities. This hierarchical classification can continue for any system until the lowest tier of sets that it is reasonable or necessary to consider is reached. To simplify discussion, any system may be considered an entity, i.e., an entity which includes all other entities.
- a software system of a digital computer can be considered to be made up of applications.
- Each application in turn can be considered to be made up of code modules.
- Three hierarchies are to be managed here: the system, the applications and the code modules.
- Managed systems comprise an assemblage or combination of entities forming a complex unitary whole, either in reality or in thought only. Any such system can be represented or modelled as a universal class which may be crisp (i.e., with precisely defined members) or fuzzy (i.e., where membership is imprecisely defined to varying degrees).
- fuzzy systems are increasing in importance in communications, for example, where diverse intravendor and intervendor product lines and products are being melded into fuzzy systems to provide “one stop shopping plug and play” capability for consumers.
- Systems are fuzzy when the membership functions of any of their parts or elements (entities) are indefinite to any degree.
- Characteristics are distinctive and proper activities or actions that reflect the intrinsic nature of each entity, or of the system itself. Examples of characteristics would be the inputs and outputs of an object in a class of object oriented computer software code modules.
- the characteristics of each entity are modified by parameters attributable to that entity.
- Parameters determine, at any given time, such things as the information content, state, or activities of an entity, but do not determine or affect the intrinsic nature of the entity. Parameters are, in general, variable.
- Systems can be classified as either homogeneous or heterogeneous.
- Homogeneous systems consist of entities that are either all crisp or all fuzzy.
- Heterogeneous systems consist of a mix of crisp and fuzzy entities and thus are always fuzzy.
- Homogeneous fuzzy systems can be successfully managed.
- the indefinite nature of the membership function of the system can place significant restrictions on the purpose and operational effectiveness of the management capability of the system only homogeneous crisp systems can incorporate all the purposes of their tier one member sets in the overall system purpose and can thus be termed 100% generalized. If system generalization is less than 100%, as must be the case for all systems with one or more fuzzy components, the system is termed more specialized (or less efficient) as judged in relation to design intent.
- Software in general, is fuzzy, especially if not object oriented. Software can have unintentionally fuzzy characteristic, parameter, functionality and purpose sets due to various design inadequacies (bugs).
- the Internet is an example of a catanet with a large software based constituency.
- the Internet can be considered a heterogeneous system because, from a management perspective, the membership functions of the characteristic and parameter sets of at least some entities can be fuzzy at any given time.
- the only practicable management system for the Internet would have to be highly specialized due to the complexity of the system itself and to the undetermined (or undeterminable) nature of the membership functions for elements of its constituent fuzzy sets of entity characteristics, parameters, functionalities and purposes.
- gateway management is aware that a device is attempting to join as a full network member before the membership is confirmed by authentication procedures. Between the time that the device has made overtures to join the network and the actual acceptance of the device as a full member, its membership is fuzzy. While the device is in a fuzzy state, gateway management can initiate preparations such as an anticipatory user group assignment, virtual communications port assignments, etc. preparatory to having the device join the network as a full member.
- a device that was formerly a full member of a network, but is awaiting a software load update to bring its functionality up to the network norm, can be considered a fuzzy component as it is fairly close to full membership but is not quite there until its improved functionality software is actually functioning.
- U.S. Pat. No. 5,692,106 issued Nov. 25, 1997 to Simon Towers and Paul Mellor discloses a management method and apparatus for computer system tasks and services.
- An example of a service may be e-mail and tasks related to this services may be installing, configuring and diagnosing and removing faults.
- declarative models are constructed of the various services provided by the system. These models specify the requirements that need to be met for the corresponding service to be available. These requirements are set out in terms of the system entities that need to be present and the inter-relationships of these entities.
- each management task is specified in a corresponding task program in terms of general inferencing operations that can be performed on any of the models. Execution of a particular management task involves carrying out inferencing operations on the appropriate service model in accordance with the task program for the management task under consideration.
- a method of managing a plurality of networked manageable devices includes at least one file server having a system board, a drive array subsystem associated with the file server and a server manager installed in the file server for monitoring the system board from a manager console using a management information base or “MIB”.
- MIB management information base
- a hierarchical communication network management system comprises a plurality of agents and sub-managers connected to lower communication networks and an integration manager connected to a higher communication network.
- Each of the sub-managers functions as an agent to the integration manager and functions as a manager to each agent, so that it becomes possible to employ Simple Network Management Protocol (SNMP) between each agent and its sub-manager and between a sub-manager and the integration manager.
- SNMP Simple Network Management Protocol
- Information is collected by managers and stored in a management information base or “MIB”.
- the system manager of the subject invention has a table associating each element in the system with a number representing a management scheme.
- a method for facilitating management of an electrical, electronic, electro-mechanical or computer system comprising receiving at an electronic manager a plurality of management rules and associated management kernels, each management kernel including a prime number factor raised to a positive integer power.
- a method of managing an electrical, electronic, electro-mechanical or computer system including receiving a plurality of management rules and associated management kernels, each management kernel comprising a prime number factor raised to a positive integer power. The factor. Also provided is a computer readable medium for providing program control for a manager of a system for carrying out this method.
- an electronic manager for an electrical, electronic, electro-mechanical or computer system comprising: a directive acceptance and result reporting layer for receiving an indicator of each managed entity in the system and an associated control parameter, a manager instructions and rules of operation layer, a management kernel definition and redefinition layer which, together with the manager instruction and rules layer, has management kernels and associated management rules, each management kernel comprising a prime number factor raised to a positive integer power, a mathematical manipulation layer for dividing each control parameter by ones of the management kernels; a system entity information management layer responsive to the manager instructions and rules of operation layer, the management kernel definition and redefinition layer and the mathematical manipulation layer for deriving management rules; and a management plane communications capability layer responsive to the system entity information management layer for managing the system.
- FIG. 1 illustrates a Control Parameter in accordance with an embodiment of the invention.
- FIG. 2 illustrates, as a block diagram, software system.
- FIG. 3 illustrates a simplified view of the system in FIG. 2 .
- FIG. 4 illustrates a table in which management kernels are associated with their meaning in accordance with an embodiment of the present invention.
- FIG. 5 illustrates a table in which Management Schemes are calculated in accordance with an embodiment of the present invention.
- FIG. 6 illustrates a table in which inputs are identified in accordance with an embodiment of the present invention.
- FIG. 7 illustrates a table in which data input is identified in accordance with an embodiment of the present invention.
- FIG. 8 illustrates a table in which control input is interpreted in accordance with an embodiment of the present invention.
- FIG. 9 illustrates a management table in accordance with an embodiment of the invention.
- FIG. 10 illustrates, as a block diagram, a management system in accordance with an embodiment of the invention.
- FIG. 11 illustrates, as a block diagram, a communications network.
- system management is to control the activities of system entities and of the system itself so that both entities and system can fulfill their respective purposes.
- the invention achieves this via a simple algorithm that maps hierarchical systems to what may be considered a flat (i.e., nonhierarchical) management plane. Entity and system activities are manipulated by the manager on the management plane via their characteristics and parameters and management instructions from a Management Intelligence Source (MIS). Once manipulation is complete, management directives flow back from the manager to the system to control and give direction to the system and entity activities. Due to the nature and simplicity of the algorithm, ongoing iterative corrections and adjustments can be made by the manager “on the fly”. This permits most types of systems to be managed, including those that are fuzzy and extremely dynamic. The management of very complicated and extensive systems can be accommodated via management hierarchies.
- MIS Management Intelligence Source
- the manager requires that, regardless of tier, every entity of a system to be managed have a Control Parameter 102 comprising a unique Code Number C 108 in an Identifier Field 104 and a Management Scheme S 110 in a Management Field 106 . It is not necessary that Code Number 108 be part of a single numbering scheme, only that it be unique. If Code Number 108 is not unique, then the manager requires that it be unique on the tier occupied and that the tier then be identified to the manager.
- Identifier Field 104 is a binary digit field long enough to accommodate any Code Number 108 used.
- Management Field 106 is a binary digit field of sufficient length to accommodate Management Scheme 110 .
- Management Scheme 110 embodies the essence of a plan or program of action to be followed by the manager and the system under differing management conditions.
- Management Scheme 110 is a positive integer number greater than zero that defaults to one if unassigned.
- Management kernels are the core of Management Scheme 110 . Implicit in k i n is the information needed to inform the manager of characteristics and/or parameters and/or functions of each entity, as well as the information required by the manager to manipulate, associate and dissociate, reconfigure, communicate with and control entities on all tiers and to assign subsystem management hierarchies. To meet algorithm requirements, each k i must be drawn only from the set of integer prime numbers raised to positive integer powers n. This enables all k i n (except for k i 0 , which is “1”) to be unequivocally and simply extracted from Management Scheme S 110 at any time or place and thus enables effective, versatile and dynamic management and management communications between the manager and the system together with all its entities.
- the set of the first 303 prime numbers drawn from the integers zero through 2000 , in combination with the integer one, is sufficient to assign k i for most dynamic complex systems.
- the numerical distribution of the first 303 prime integers is such that a relatively large number of integer primes exist with low numbers of decimal digits.
- Low numbers of decimal digits in the k i are important to keep the maximum number of binary digits in Management Scheme 110 to a minimum for any given system, both to reduce the length, L, of Management Field 106 and to ease the real-time computational requirements on the manager if the manager is designed to employ ongoing real-time computational, as opposed to tabular look up, management. Either methodology can be used, depending on design choices made in response to how dynamic and complex the system is.
- a software system 200 is assembled to perform some simple arithmetic operations.
- a system 208 has three inputs 202 , 204 , 206 and one output 210 .
- inputs A 202 and B 204 and output D 210 are for data and input J 206 is for control.
- FIG. 3 A simplified view of the entities of system 200 is shown in FIG. 3 .
- Each entity of the system, and the system itself, is given a Code Number, from G1 to G8, known to a manager 300 .
- Manager 300 may be a computer loaded with system management software for executing the method of this invention from software medium 310 , which could be a disk, a tape, a chip or a random access memory containing a file downloaded from a remote source. From the Code Number C and associated Management Scheme S manager 300 can identify each entity and the system itself, together with entity or system characteristics, parameters and functions and can manage the system based on this information. Systems that are much more complex than this trivial example can be managed just as easily.
- Manager 300 receives from a Management Intelligence Source 312 the purpose of the system.
- the purpose is to find the absolute value of the difference of data inputs 303 , 304 and send the absolute value of the difference to output 305 .
- a zero control input 302 requires that manager 300 find a sum of data inputs 303 , 304 and send the sum to output 305 .
- a product of two data inputs 303 , 304 is sent to output 305 as a result of a positive control input 302 .
- Manager 300 also receives from the Management Intelligence Source the table 402 (FIG. 4) dealing with the system 200 inputs 202 , 204 , 206 and the system output 210 as well as with the interpretation of the signals received via such inputs 202 , 204 , 206 , and provided by the system 200 to such output 210 .
- the table 402 FIG. 4
- a distinctive management kernel of numerical value the integer prime “5” is assigned to inputs 202 , 204 , 206
- a prime number value for the management kernel 30 need not be assigned to the output 210 .
- the numerical value for the management kernel assigned to output 210 can then default (for simplicity) to the numerical value “1”.
- a distinctive management kernel of numerical value the integer prime “3” is assigned to the data inputs 202 and 204 a prime number value for the management kernel need not be assigned to the control input 206 .
- the numerical value for the management kernel assigned to control input 206 can also default (for simplicity) to the numerical value “1”.
- the parameter values in this simple example system 200 at the control input 206 must be differentiated in the FIG. 4 table 402 and are assigned the management kernels: “2” for a negative parameter value; “2 2 ” for a zero parameter value and “2 3 ” for a positive parameter value.
- the resultant numbers 5,3,1,2,4, and 8 are termed “management kernels” or “kernels” for the system.
- FIG. 4 table in conjunction with the purpose of the system, provides an association of each kernel with a management rule.
- a table 502 (FIG. 5) is then loaded by Management Intelligence Source 312 into manager 300 , equating each Code Number, C, to one management scheme, S. It is contemplated that this table may change for each system operation.
- G2 has one of three values; for illustration purposes all three possible values for G2 are shown in FIG. 5 .
- manager 300 knows nothing else about the system and has to control the system from what it knows.
- Manager 300 remains idle until it is prompted (typically by receiving a new table 502 , or a new entry in table 502 , from Management Intelligence Source 312 ) that system 301 requires an operation. Precisely what operation, manager 300 does not yet know. Upon receiving a prompt, manager 300 knows it needs to find system inputs and from table 402 it notes that inputs are identified by management kernel “5”. Therefore, all of the S values in table 502 (FIG. 5) are divided by management kernel “5”, with the result shown in table 602 (FIG. 6 ). Manager 300 identifies as input entities whose result of the division are integers in column 3 of table 602 (FIG. 6 ).
- manager 300 divides S for the inputs identified in table 602 (FIG. 6) by management kernel “3” associated with “data” in table 402 (FIG. 4 ). The results of this division are shown in table 702 (FIG. 7 ), where a noninteger value in column 3 indicates an entity that is a control input. In this way, manager 300 identifies entity G2 as the only entity providing a control input.
- manager 300 next needs to determine what type of control input G2 is generating. From the purpose known by manager 300 , this control input may be negative, zero or positive.
- Manager 300 repeatedly divides the S value for entity G2 by the management kernel “2” until the dividend is determined to be nonintegral. The division result preceding the noninteger indicates the power of 2 and, therefore, the control value (see the FIG. 8 table 802 ).
- management kernel “3” is assigned, by Management Intelligence Source 312 via table 402 (FIG. 4 ), to data and “1” is assigned to control because any input (indicated by management kernel “5”) without a management kernel “3” (the data designator) assigned as well, must be a control input.
- This method of identifying characteristics and parameters can be extended to dynamic systems whose inputs, or other entity characteristics or parameters, come and go rapidly and continuously.
- the method can also be applied to fuzzy systems where the closeness to presence or absence of a characteristic or parameter is indefinite to some extent as defined by the membership function of that characteristic or entity.
- numeric parameter may be included as a factor in the management scheme for the system. If more than one entity has an associated numeric parameter, the numeric parameters of each such entity can be included in a subsystem via assignment of a unique hierarchy of subsystem identifiers, k u1 n , k u2 n , k u3 n , . . . , to the management scheme for these entities.
- n may then be a positive integer greater than or equal to zero outside of any subsystem defined to store numeric parameters.
- the n in k i n must be a positive integer equal to zero or one only.
- Very complicated systems may be subdivided into any type (or types) of subsystems to simplify management as well as to store numeric parameters.
- k ui n use of a unique numeric subsystem hierarchy identifier kernel, k ui n , allows for reuse of primes for kernels within a particular subsystem hierarchy which leads to more compact management schemes.
- the manager of this invention may be modelled a layered architecture device as shown in FIG. 10 .
- Inputs and outputs to manager 1008 occur at layers 1007 and 1003 .
- the layers are as follows. Adjacent layers intercommunicate via the minimum number of interfaces practicable, with services being requested by the uppermost layer and services being provided by the lowermost layer of each adjacent layer pair.
- Management Intelligence Source 1010 is a resource (human or otherwise) capable of and authorized to issue directives to manager 1008 concerning system management. Such directives must reflect a high degree of understanding of how the system is to be configured and run. Management Intelligence Source directives provide sufficient input to manager 1008 to permit it to control any system under consideration.
- Output from layer 1007 is in the form of reports from manager 1008 back to Management Intelligence Source 1010 as Management Intelligence Source 1010 may require.
- Layer 1007 is otherwise concerned with accepting and interpreting the directives from Management Intelligence Source 1010 and with putting these directives into effect via Manager Instructions and Rules of Operation of layer 1006 .
- An example of layer 1007 activities might be a directive by Management Intelligence Source 1010 to send a result of an operation performed on the values at inputs A and B to output D in the forgoing example ( 200 , FIG. 2 ).
- Manager 1008 would follow the Management Intelligence Source Directive and report back to Management Intelligence Source 1010 on the success (or otherwise) of managed system 1012 in carrying out Management Intelligence Source instructions.
- Layer 1006 deals with those manager instructions and rules of operation analogous to, but generally much simpler than, the instructions that must be provided to an expert system to permit it to function. In the forgoing example, these would be the association of specific operations with values at control input J ( 206 , FIG. 2 ).
- FIG. 4 illustrates an association of kernels with instructions and rules of operation for the exemplary system.
- Layer 1004 deals with information access, storage and retrieval as it pertains to entities in system 1012 .
- information is stored in a Control Parameter 102 as an Identifier Field 104 containing the Code Number C 108 together with an associated Management Field 106 containing the Management Scheme S 110 .
- this layer represents a complete set of characteristics and parameters for inputs, outputs and operations.
- FIG. 5 illustrates a Code Number and Management Scheme associated with each entity in the exemplary system.
- coded information to manage system 1012 is distributed to the system by manager 1008 while iterative feedback is passed back to manager 1008 from system 1012 .
- Communications between manager 1008 and system 1012 may be via any useful communications protocol, such as SNMP in a datacommunications context.
- such intercommunication between the manager 300 and the system 301 is represented by the double-ended arrows joining each of the system's active parts G2, G3, . . . , G8 ( 302 , 303 , . . . , 308 ) with the manager 300 .
- Layer 1002 is a decoding and encoding layer. At layer 1002 , mathematical operations take place to extract to encode the management kernels, k i n , and any numeric parameters N p from the management scheme assigned to each code number.
- Layer 1001 is a basic operating system for manager 1008 .
- a manager 1102 in a complicated system can manage more effectively and more efficiently if the member collector networks 1106 , 1108 , included local networks 1110 , 1112 , 1114 , 1116 and nodes 1120 , 1122 , 1124 , 1126 , 1128 , 1130 are each treated as subsystems of the backbone network system 1100 .
- a manager 1102 in a complicated system such as a backbone network 1104
- the member collector networks 1106 , 1108 included local networks 1110 , 1112 , 1114 , 1116 and nodes 1120 , 1122 , 1124 , 1126 , 1128 , 1130 are each treated as subsystems of the backbone network system 1100 .
- hierarchical relationships are essential amongst the system entities to be managed or management is impossible.
- Entities on Higher Tiers May Request Services From Appropriate Entities on Lower Tiers.
- OSI Open Systems Interconnection
- Entities on Lower Tiers Must Provide Services to Those Appropriate Entities on Higher Tiers from Which Such Services were Requested.
- a notable exception to this rule involves service requests sent directly by the manager 1008 to a layer ( 1007 through 1001 inclusive), with the requested services provided directly back to the manager 1008 .
- instructions given to the manager by the Management Intelligence Source (layer 1007 ) may permit entities to exchange services beyond the scope of the mandate of the manager.
- management kernels are assigned and defined in layer 1005 .
- the Code Number, C, and S make up the manager view of each system entity. Encoded in S are the k i n which permit the manager to construct or reconfigure the system in accordance with Management Intelligence Source directives and from iterative feedback (if any) provided by the system entities.
- this rule is embedded in the Manager Instructions and Rules of Operation at layer 1006 and cannot be violated.
- Characteristics are distinctive activities or actions that reflect the inherent nature of each entity. The characteristics of each entity are modified by parameters attributable to that entity. Parameters determine, at any given time, such things as the information content, state, or activities of an entity. Characteristics cannot be perverted by the form, configuration or the function of an entity else the entity will not work as per design intent.
- a characteristic of an entity may be a one litre capacity.
- a parameter corresponding to this characteristic may be the volume currently held in the entity.
- Class or Set Characteristics cannot Violate the Characteristics of their Members or Included Sets or Entities.
- Class or Set Parameters cannot Violate the Parameters of their Members or Included Sets or Entities.
- each distinct instruction or rule of operation may be associated with a kernel which is a distinct prime number.
- kernels may be represented by k i n (with n being a positive integer), n may ideally be set at “1” for all kernels making the set of k i n more homogeneous and (ideally) easier to process and interpret.
- Code Number may be a number, a word, an alphanumeric or any other marker used to uniquely identify an entity.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Artificial Intelligence (AREA)
- Computer Vision & Pattern Recognition (AREA)
- Databases & Information Systems (AREA)
- Evolutionary Computation (AREA)
- Medical Informatics (AREA)
- Software Systems (AREA)
- Computer And Data Communications (AREA)
Abstract
Description
Claims (15)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/206,213 US6292942B1 (en) | 1998-12-07 | 1998-12-07 | Manager for dynamic complex systems |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/206,213 US6292942B1 (en) | 1998-12-07 | 1998-12-07 | Manager for dynamic complex systems |
Publications (1)
Publication Number | Publication Date |
---|---|
US6292942B1 true US6292942B1 (en) | 2001-09-18 |
Family
ID=22765435
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US09/206,213 Expired - Fee Related US6292942B1 (en) | 1998-12-07 | 1998-12-07 | Manager for dynamic complex systems |
Country Status (1)
Country | Link |
---|---|
US (1) | US6292942B1 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100263045A1 (en) * | 2004-06-30 | 2010-10-14 | Daniel Wesley Dulitz | System for reclassification of electronic messages in a spam filtering system |
US20140149324A1 (en) * | 2009-05-29 | 2014-05-29 | Mark Gordon Damm | Method and System to Manage Complex Systems Knowledge |
US11394749B2 (en) * | 2019-11-15 | 2022-07-19 | Ent. Services Development Corporation Lp | Systems and methods for automated determination of trust levels associated with regions and securely transporting data between the regions |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471617A (en) | 1991-06-24 | 1995-11-28 | Compaq Computer Corporation | Computer management system and associated management information base |
US5559958A (en) * | 1991-06-24 | 1996-09-24 | Compaq Computer Corporation | Graphical user interface for computer management system and an associated management information base |
US5651006A (en) | 1994-06-14 | 1997-07-22 | Hitachi, Ltd. | Hierarchical network management system |
US5774669A (en) * | 1995-07-28 | 1998-06-30 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Scalable hierarchical network management system for displaying network information in three dimensions |
-
1998
- 1998-12-07 US US09/206,213 patent/US6292942B1/en not_active Expired - Fee Related
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5471617A (en) | 1991-06-24 | 1995-11-28 | Compaq Computer Corporation | Computer management system and associated management information base |
US5559958A (en) * | 1991-06-24 | 1996-09-24 | Compaq Computer Corporation | Graphical user interface for computer management system and an associated management information base |
US5651006A (en) | 1994-06-14 | 1997-07-22 | Hitachi, Ltd. | Hierarchical network management system |
US5774669A (en) * | 1995-07-28 | 1998-06-30 | The United States Of America As Represented By The Administrator Of The National Aeronautics And Space Administration | Scalable hierarchical network management system for displaying network information in three dimensions |
Cited By (8)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20100263045A1 (en) * | 2004-06-30 | 2010-10-14 | Daniel Wesley Dulitz | System for reclassification of electronic messages in a spam filtering system |
US8782781B2 (en) * | 2004-06-30 | 2014-07-15 | Google Inc. | System for reclassification of electronic messages in a spam filtering system |
US20140325007A1 (en) * | 2004-06-30 | 2014-10-30 | Google Inc. | System for reclassification of electronic messages in a spam filtering system |
US9961029B2 (en) * | 2004-06-30 | 2018-05-01 | Google Llc | System for reclassification of electronic messages in a spam filtering system |
US20140149324A1 (en) * | 2009-05-29 | 2014-05-29 | Mark Gordon Damm | Method and System to Manage Complex Systems Knowledge |
US9406022B2 (en) * | 2009-05-29 | 2016-08-02 | Mark Gordon Damm | Method and system to manage complex systems knowledge |
US11394749B2 (en) * | 2019-11-15 | 2022-07-19 | Ent. Services Development Corporation Lp | Systems and methods for automated determination of trust levels associated with regions and securely transporting data between the regions |
US11689572B2 (en) | 2019-11-15 | 2023-06-27 | Ent. Services Development Corporation Lp | Systems and methods for inventory management using prime numbers |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Kargupta et al. | Collective data mining: A new perspective toward distributed data mining | |
Lin | Granular computing on binary relations II: Rough set representations and belief functions | |
Davey et al. | The development of a software clone detector | |
Yao | Decision-theoretic rough set models | |
US6728727B2 (en) | Data management apparatus storing uncomplex data and data elements of complex data in different tables in data storing system | |
EP0757336B1 (en) | Data exchange systems comprising portable data processing units | |
CN101730099B (en) | Terminal management method based on authority control and device | |
Salonikias et al. | Access control in the industrial internet of things | |
Liu et al. | A multiagent evolutionary algorithm for combinatorial optimization problems | |
CN101689239B (en) | A security token and system and method for generating and decoding the security token | |
Ascia et al. | A VLSI fuzzy expert system for real-time traffic control in ATM networks | |
AU2002334162A1 (en) | Policy based system management | |
WO2003034207A2 (en) | Policy based system management | |
CN111708849A (en) | Data management method, device, equipment and storage medium | |
US6292942B1 (en) | Manager for dynamic complex systems | |
Goertzel et al. | Fast and slow enigmas and parental guidance | |
Hitchens et al. | Design and specification of role based access control policies | |
Barto et al. | Cooperativity in networks of pattern recognizing stochastic learning automata | |
CN115022020B (en) | Access control method and system based on multidimensional set calculation | |
Brookes et al. | Continuous functions and parallel algorithms on concrete data structures | |
Anderson et al. | Simplex-like trajectories on quasi-polyhedral sets | |
Zhang et al. | An agent-based hybrid intelligent system for financial investment planning | |
Sakakibara et al. | Learning languages by collecting cases and tuning parameters | |
Armstrong et al. | Some results concerning adaptive logic networks | |
Wu et al. | On Implementing a Protocol Independent MIB |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NORTHERN TELECOM LIMITED, CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KENNEDY, JOHN EDWIN DAVID;REEL/FRAME:009657/0643 Effective date: 19981130 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS CORPORATION, CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTHERN TELECOM LIMITED;REEL/FRAME:010567/0001 Effective date: 19990429 |
|
AS | Assignment |
Owner name: NORTEL NETWORKS LIMITED, CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 Owner name: NORTEL NETWORKS LIMITED,CANADA Free format text: CHANGE OF NAME;ASSIGNOR:NORTEL NETWORKS CORPORATION;REEL/FRAME:011195/0706 Effective date: 20000830 |
|
FEPP | Fee payment procedure |
Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
FPAY | Fee payment |
Year of fee payment: 4 |
|
SULP | Surcharge for late payment | ||
AS | Assignment |
Owner name: INDEPENDENCE MANZANAR LLC, NEVADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NORTEL NETWORKS LIMITED;REEL/FRAME:017286/0465 Effective date: 20050406 |
|
FPAY | Fee payment |
Year of fee payment: 8 |
|
FEPP | Fee payment procedure |
Free format text: PAYER NUMBER DE-ASSIGNED (ORIGINAL EVENT CODE: RMPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY |
|
REMI | Maintenance fee reminder mailed | ||
LAPS | Lapse for failure to pay maintenance fees | ||
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20130918 |
|
AS | Assignment |
Owner name: HANGER SOLUTIONS, LLC, GEORGIA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLECTUAL VENTURES ASSETS 161 LLC;REEL/FRAME:052159/0509 Effective date: 20191206 |