CA2221654A1 - Knowledge module - Google Patents
Knowledge module Download PDFInfo
- Publication number
- CA2221654A1 CA2221654A1 CA 2221654 CA2221654A CA2221654A1 CA 2221654 A1 CA2221654 A1 CA 2221654A1 CA 2221654 CA2221654 CA 2221654 CA 2221654 A CA2221654 A CA 2221654A CA 2221654 A1 CA2221654 A1 CA 2221654A1
- Authority
- CA
- Canada
- Prior art keywords
- information
- class
- attribute
- modeled
- modeled object
- 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.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/465—Distributed object oriented systems
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Computer And Data Communications (AREA)
Abstract
A object, known as a Knowledge Module encapsulates all network management information which is required about a class of network component, including the name of the class, the object-oriented superclass, attribute descriptions which includes the valid values, type of the attribute, and translation information, containment rules, communication protocol information, provisioning rules, inter-object relationship information, intra-object inter-attribute relationship information, customizable provisioning screens, database storage and retrieval information.
Description
CA 022216~4 1997-11-20 KNOWLEDGE MODULE
This invention relates to the field of object-oriented pro~~ g, and in particular to a new kind of class object known as a KnowledgeModule.
A KnowledgeModule builds on the concepts of "Managed Object" (see ITU/CCITT standard M.3010) and the object-oriented "class" from the Sm~llt~lk pro~,l;..."";l~g language (see Goldberg, A. and Robson, D., "Sm~ lk-80: The Language and its Impl~m~nt~tion", R~ ing, Mass.: Addison-Wesley, 1983).
A Managed Object definition contains n~min~, colll~ilmlent, attribute, and structure information needed for Network Management Systems (NMS's) to communicate about a particular type of network compollent but it does not contain useful information about how the network management system should behave. Information which is lacking includes the rules for how the network component should be provisioned. Also, a Managed Object includes a subset of the object-oriented paradigm.
Conversely, an object-oriente~ "Class" can contain provisioning rules and behavior but it is limited in what mech~ni~m~ are provided for describing n~min~, colllaillment, attribute, and structure information.
Both Managed Object and Class definition are typically manipulated by technical experts in these respective technologies. They are not readily manipulated by "domain experts" who are those who are f~mili~r with the particular type of network component.
An object of the invention is enc~rs~ te all the required information about a type of network component into a single unit.
Accor~illg to the present invention there is provided in an object-oriented pro~,~.,...,il~g eL~vilolllllent, an object that enca~ulates all network management il~"l,ation which is required about a class of network component, said information being selected as one or more items from the group con~i~ting of: the name of the class, the object-oriented superclass, attribute descriptions which includes the valid values, type ofthe attribute, and tr~ncl~tion information, co.ll;.;lll"ent rules, communication protocol information, provisioning rules, inter-object relationship il~llllation, intra-object inter-attribute relationship information, cu~lollli~able provisioning screens, 11~t~b~ce storage and retrieval information.
CA 022216~4 1997-11-20 Such objects are known as KnowledgeModules and are arranged in a object-oriented hie.~.;hy and fully support inhf ;~ ce and polymorphism. KnowledgeModules may be hll~)Gl led and exported to and from text files.
Once a KnowledgeModule has been imported, it behaves as an extended class object, allowing instances to be created. The instances refer back to the KnowledgeModule to obtain information to guide the behavior of applications including Provisioning and Management Information Base navigation.
Any language which fully supports inh~rit~nce, polymorphism, and run-time compilation may be used to implement Knowledge Modules. The implement~tion consists of a (object-oriented) "Class" in which is a subclass of "Modeled Object" and an h~ ce of "Modeled Object Template" class. The network management system creates instances of t_e Modeled Object subclass at runtime. The Modeled Object class implements the basic behavior of all Modeled Objects and has facilities to for subclasses to create their Modeled Object Template object instance.
The Modeled Object Templ~te object instance is a normal Object and so can be manipulated as such through a user int~ ce. The updated Modeled Object Template has the ability to regenerate the source code of its Modeled Object class.
Using the services provided by the software development ellvirolllllent, the source code ofthe Modeled Object subclass may be exported and imported to a text file. After iln~o~ g, a Modeled Object subclass can create its Modeled Object Template, thereby boo~ g the system.
Knowledge Modules are a key component of CrossKeys' "OpenKnowledge"
vvolL which is the basis of the West End Astrolabe Net.~,vork Node Manager. In this system, the KnowledgeModules are used to model the West End network eq lipment in the resi~çnti~l broaclh~n~l market. OpenKnowledge implements the KnowledgeModules in the Sm~llt~lk prog~...~ language as implement~l by ParcPlace-Digitalk.
Pe~i~tent multi-user access to the Modeled Object instances in provided by the GemStone object-oriented ~lat~b~e of GemStone Systems.
The invention will now be described in more detail, by way of example only, withreference to the accol~ hlg drawings, in which:-CA 022216~4 1997-11-20 Figure 1 shows the relationships between a sample Modeled Object (a WENode9600Typel) and the Modeled Object which contain it (a WEDomain) and are contained by it (a collection of Modeled Objects of type WEShelf9600); and Figure 2 shows the relationship between a sample Modeled Object, a WENode9600Typel, and its Modeled Object Template.
1. MODELED OBJECT DESIGN OVERVIEW
A KnowledgeModule e~c~rs~ tçs all network management information which is required about a class of network component. This information includes:
~ the name of the class ~ the object-oriented superclass ~ attribute descriptions which includes the valid values, type of the attribute, and translation inro~ ation ~ cont~inm~nt rules ~ collllllu"ication protocol inforrnation ~ provisioning rules ~ inter-object relationship information ~ intra-object inter-attribute relationship information lOll~i~ble provisioning screens ~ ~qt~b~e storage and retrieval information KnowledgeModules are arranged in a object-oriented hierarchy and fully support inheritance and polymorphism. KnowledgeModules may be imported and exported to and from text files.
Once a KnowledgeModule has been imported, it behaves as an extended class object, allowing instances to be created. The instances refer back to the CA 022216~4 1997-11-20 KnowledgeModule to obtain information to guide the behavior of applications including Provisioning and M~n~gen ~nt Information Base navigation.
Any language which fully supports inh~rit~nce, polymorphism, and run-time compilation may be used to implement Knowledge Modules. The implelnentation consists of a (object-oriented) "Class" in which is a subclass of "Modeled Object" and an in.~t~n~.e of "Modeled Object Template" class. The network management system creates instances of the Modeled Object subclass at runtime. The Modeled Object class implements the basic behavior of all Modeled Objects and has facilities to for subclasses to create their Modeled Object Template object instance.
The Modeled Object Template object instance is a normal Object and so can be manipulated as such through a user interface. The updated Modeled Object Template has the ability to regenerate the source code of its Modeled Object class.
Using the services provided by the software development environment, the source code of the Modeled Object subclass may be exported and imported to a text file. After ollhlg~ a Modeled Object subclass can create its Modeled Object Template, thereby boul~L,~pillg the system.
1.1 object Model 1.1.1 Class Hierarchy The class hie,dl~clly and structure of the relevant classes is shown below Object Modeled Object In~ ce variables:
conl~ er - reference to the co~ ,g object dep~.n~nt.~
addressKey inventory - collection of contained objects connectionRegistry registries objectState compoundState myName CreationDate CreationTime CreatedBy LastModifiedDate LastModifiedTime LastModifiedBy GeneralInformation alarms Class variables: -ObjectRegistry Modeled Object Template Instance variables:
dependents listOfAttributes - a list of the specifications for the Modeled Object's attributes typeOfModeledObject - the name of the Modeled Object reqAttributesForCreation - required attributes for creation isIndexable - indexing directive for ~at~b~e schema generation myNameBlock creationRule dep~.n~l~nt~ttributes uniqueIdBlock extensions maxNumOfSubParts - m;1X;~ number of Modeled Objects which can be contained by the Modeled Object instance myBitmapBlock superclassTemplate - name of the Modeled Object Template which is the superclass allAttributeNames attributeDictionary attributeGroupSpecs subPartClassSpecs - specifies the conlai~ ent rules subPartKeySpecs menu relationships allVisibleGroups isCopyable 1.1.2 Object Relationships Shown below are two diagrams. The first figure shows the relationships between a sample Modeled Object (a WENode9600Typel) and the Modeled Object which containit (a WEDomain) and are contained by it (a collection of Modeled Objects of typeWEShelf9600).
This invention relates to the field of object-oriented pro~~ g, and in particular to a new kind of class object known as a KnowledgeModule.
A KnowledgeModule builds on the concepts of "Managed Object" (see ITU/CCITT standard M.3010) and the object-oriented "class" from the Sm~llt~lk pro~,l;..."";l~g language (see Goldberg, A. and Robson, D., "Sm~ lk-80: The Language and its Impl~m~nt~tion", R~ ing, Mass.: Addison-Wesley, 1983).
A Managed Object definition contains n~min~, colll~ilmlent, attribute, and structure information needed for Network Management Systems (NMS's) to communicate about a particular type of network compollent but it does not contain useful information about how the network management system should behave. Information which is lacking includes the rules for how the network component should be provisioned. Also, a Managed Object includes a subset of the object-oriented paradigm.
Conversely, an object-oriente~ "Class" can contain provisioning rules and behavior but it is limited in what mech~ni~m~ are provided for describing n~min~, colllaillment, attribute, and structure information.
Both Managed Object and Class definition are typically manipulated by technical experts in these respective technologies. They are not readily manipulated by "domain experts" who are those who are f~mili~r with the particular type of network component.
An object of the invention is enc~rs~ te all the required information about a type of network component into a single unit.
Accor~illg to the present invention there is provided in an object-oriented pro~,~.,...,il~g eL~vilolllllent, an object that enca~ulates all network management il~"l,ation which is required about a class of network component, said information being selected as one or more items from the group con~i~ting of: the name of the class, the object-oriented superclass, attribute descriptions which includes the valid values, type ofthe attribute, and tr~ncl~tion information, co.ll;.;lll"ent rules, communication protocol information, provisioning rules, inter-object relationship il~llllation, intra-object inter-attribute relationship information, cu~lollli~able provisioning screens, 11~t~b~ce storage and retrieval information.
CA 022216~4 1997-11-20 Such objects are known as KnowledgeModules and are arranged in a object-oriented hie.~.;hy and fully support inhf ;~ ce and polymorphism. KnowledgeModules may be hll~)Gl led and exported to and from text files.
Once a KnowledgeModule has been imported, it behaves as an extended class object, allowing instances to be created. The instances refer back to the KnowledgeModule to obtain information to guide the behavior of applications including Provisioning and Management Information Base navigation.
Any language which fully supports inh~rit~nce, polymorphism, and run-time compilation may be used to implement Knowledge Modules. The implement~tion consists of a (object-oriented) "Class" in which is a subclass of "Modeled Object" and an h~ ce of "Modeled Object Template" class. The network management system creates instances of t_e Modeled Object subclass at runtime. The Modeled Object class implements the basic behavior of all Modeled Objects and has facilities to for subclasses to create their Modeled Object Template object instance.
The Modeled Object Templ~te object instance is a normal Object and so can be manipulated as such through a user int~ ce. The updated Modeled Object Template has the ability to regenerate the source code of its Modeled Object class.
Using the services provided by the software development ellvirolllllent, the source code ofthe Modeled Object subclass may be exported and imported to a text file. After iln~o~ g, a Modeled Object subclass can create its Modeled Object Template, thereby boo~ g the system.
Knowledge Modules are a key component of CrossKeys' "OpenKnowledge"
vvolL which is the basis of the West End Astrolabe Net.~,vork Node Manager. In this system, the KnowledgeModules are used to model the West End network eq lipment in the resi~çnti~l broaclh~n~l market. OpenKnowledge implements the KnowledgeModules in the Sm~llt~lk prog~...~ language as implement~l by ParcPlace-Digitalk.
Pe~i~tent multi-user access to the Modeled Object instances in provided by the GemStone object-oriented ~lat~b~e of GemStone Systems.
The invention will now be described in more detail, by way of example only, withreference to the accol~ hlg drawings, in which:-CA 022216~4 1997-11-20 Figure 1 shows the relationships between a sample Modeled Object (a WENode9600Typel) and the Modeled Object which contain it (a WEDomain) and are contained by it (a collection of Modeled Objects of type WEShelf9600); and Figure 2 shows the relationship between a sample Modeled Object, a WENode9600Typel, and its Modeled Object Template.
1. MODELED OBJECT DESIGN OVERVIEW
A KnowledgeModule e~c~rs~ tçs all network management information which is required about a class of network component. This information includes:
~ the name of the class ~ the object-oriented superclass ~ attribute descriptions which includes the valid values, type of the attribute, and translation inro~ ation ~ cont~inm~nt rules ~ collllllu"ication protocol inforrnation ~ provisioning rules ~ inter-object relationship information ~ intra-object inter-attribute relationship information lOll~i~ble provisioning screens ~ ~qt~b~e storage and retrieval information KnowledgeModules are arranged in a object-oriented hierarchy and fully support inheritance and polymorphism. KnowledgeModules may be imported and exported to and from text files.
Once a KnowledgeModule has been imported, it behaves as an extended class object, allowing instances to be created. The instances refer back to the CA 022216~4 1997-11-20 KnowledgeModule to obtain information to guide the behavior of applications including Provisioning and M~n~gen ~nt Information Base navigation.
Any language which fully supports inh~rit~nce, polymorphism, and run-time compilation may be used to implement Knowledge Modules. The implelnentation consists of a (object-oriented) "Class" in which is a subclass of "Modeled Object" and an in.~t~n~.e of "Modeled Object Template" class. The network management system creates instances of the Modeled Object subclass at runtime. The Modeled Object class implements the basic behavior of all Modeled Objects and has facilities to for subclasses to create their Modeled Object Template object instance.
The Modeled Object Template object instance is a normal Object and so can be manipulated as such through a user interface. The updated Modeled Object Template has the ability to regenerate the source code of its Modeled Object class.
Using the services provided by the software development environment, the source code of the Modeled Object subclass may be exported and imported to a text file. After ollhlg~ a Modeled Object subclass can create its Modeled Object Template, thereby boul~L,~pillg the system.
1.1 object Model 1.1.1 Class Hierarchy The class hie,dl~clly and structure of the relevant classes is shown below Object Modeled Object In~ ce variables:
conl~ er - reference to the co~ ,g object dep~.n~nt.~
addressKey inventory - collection of contained objects connectionRegistry registries objectState compoundState myName CreationDate CreationTime CreatedBy LastModifiedDate LastModifiedTime LastModifiedBy GeneralInformation alarms Class variables: -ObjectRegistry Modeled Object Template Instance variables:
dependents listOfAttributes - a list of the specifications for the Modeled Object's attributes typeOfModeledObject - the name of the Modeled Object reqAttributesForCreation - required attributes for creation isIndexable - indexing directive for ~at~b~e schema generation myNameBlock creationRule dep~.n~l~nt~ttributes uniqueIdBlock extensions maxNumOfSubParts - m;1X;~ number of Modeled Objects which can be contained by the Modeled Object instance myBitmapBlock superclassTemplate - name of the Modeled Object Template which is the superclass allAttributeNames attributeDictionary attributeGroupSpecs subPartClassSpecs - specifies the conlai~ ent rules subPartKeySpecs menu relationships allVisibleGroups isCopyable 1.1.2 Object Relationships Shown below are two diagrams. The first figure shows the relationships between a sample Modeled Object (a WENode9600Typel) and the Modeled Object which containit (a WEDomain) and are contained by it (a collection of Modeled Objects of typeWEShelf9600).
Claims
OR PRIVILEGE IS CLAIMED ARE DEFINED AS FOLLOWS:
1. In an object-oriented programming environment, an object that encapsulates all network management information which is required about a class of network component, said information being selected as one or more items from the group consisting of: the name of the class, the object-oriented superclass, attribute descriptions which includes the valid values, type of the attribute, and translation information, containment rules, communication protocol information, provisioning rules, inter-object relationship information, intra-object inter-attribute relationship information, customizable provisioning screens, database storage and retrieval information.
Priority Applications (4)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA 2221654 CA2221654A1 (en) | 1997-11-20 | 1997-11-20 | Knowledge module |
| CA002311328A CA2311328A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
| EP98955292A EP1031080A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
| PCT/CA1998/001079 WO1999027447A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CA 2221654 CA2221654A1 (en) | 1997-11-20 | 1997-11-20 | Knowledge module |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CA2221654A1 true CA2221654A1 (en) | 1999-05-20 |
Family
ID=4161784
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CA 2221654 Abandoned CA2221654A1 (en) | 1997-11-20 | 1997-11-20 | Knowledge module |
Country Status (3)
| Country | Link |
|---|---|
| EP (1) | EP1031080A1 (en) |
| CA (1) | CA2221654A1 (en) |
| WO (1) | WO1999027447A1 (en) |
Families Citing this family (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| FR2816420B1 (en) * | 2000-11-06 | 2003-01-31 | Evidian | METHOD FOR MANAGING AT LEAST ONE COMPUTER RESOURCE |
| US20030115308A1 (en) * | 2001-12-19 | 2003-06-19 | Michael Best | Network management system architecture |
| US20030115309A1 (en) * | 2001-12-19 | 2003-06-19 | Mann Robert Alexander | Methods of invoking polymorphic operations in a statically typed language |
| GB2401206A (en) * | 2003-04-29 | 2004-11-03 | Infinite Reason Ltd | Object orientated data processing system |
| CN1333336C (en) * | 2006-06-23 | 2007-08-22 | 清华大学 | Method for unified management of component library supporting heterogeneous component |
Family Cites Families (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CA2124720C (en) * | 1993-06-25 | 2002-10-22 | Michael R. C. Seaman | Integration of systems management services with an underlying system object model |
| WO1995003586A1 (en) * | 1993-07-21 | 1995-02-02 | Persistence Software, Inc. | Method and apparatus for generation of code for mapping relational data to objects |
| AU5853696A (en) * | 1995-05-05 | 1996-11-29 | Apple Computer, Inc. | A network component system |
-
1997
- 1997-11-20 CA CA 2221654 patent/CA2221654A1/en not_active Abandoned
-
1998
- 1998-11-20 WO PCT/CA1998/001079 patent/WO1999027447A1/en not_active Application Discontinuation
- 1998-11-20 EP EP98955292A patent/EP1031080A1/en not_active Ceased
Also Published As
| Publication number | Publication date |
|---|---|
| EP1031080A1 (en) | 2000-08-30 |
| WO1999027447A1 (en) | 1999-06-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| Kolovos et al. | The epsilon transformation language | |
| Virding et al. | Concurrent programming in ERLANG | |
| CN1811702B (en) | System and method for developing portal applications and automatically deploying them into a portal server application | |
| Crnkovic et al. | A case study: demands on component-based development | |
| Tavares et al. | A gentle introduction to OSGi | |
| AU4754600A (en) | System and method for the visual customization of business object interfaces | |
| CN102221998A (en) | Method for extending EJB container in component running support platform | |
| Weinreich et al. | Component models and component services: Concepts and principles | |
| Selic | Tutorial: real-time object-oriented modeling (ROOM) | |
| Bernardi et al. | M3D: a tool for the model driven development of web applications | |
| CA2221654A1 (en) | Knowledge module | |
| Schranz et al. | Engineering complex World Wide Web services with JESSICA and UML | |
| Fuentes et al. | How MDA can help designing component and aspect-based applications | |
| Dinkloh et al. | A tool for integrated design and implementation of conversations in multiagent systems | |
| Kubczak et al. | eXtreme model-driven design with jABC | |
| Rouvoy et al. | Rapid prototyping of domain-specific architecture languages | |
| Thramboulidis et al. | Towards a service-oriented IEC 61499 compliant engineering support environment | |
| Stojanovic et al. | Integration of Component-Based Development Concepts and RM-ODP Viewpoints. | |
| Lee et al. | An architecture model for dynamically converting components into web services | |
| Kettemann et al. | Product line implementation technologies | |
| Fregonese et al. | Architectural framework modeling in telecommunication domain | |
| Retkowitz et al. | Ontology-based configuration of adaptive smart homes | |
| Dellarocas | A coordination perspective on software system design | |
| Mukhin et al. | A method of concurrent object-oriented design using high-level Petri nets | |
| CA2311328A1 (en) | Knowledge module |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| FZDE | Dead |