WO1999027447A1 - Knowledge module - Google Patents
Knowledge module Download PDFInfo
- Publication number
- WO1999027447A1 WO1999027447A1 PCT/CA1998/001079 CA9801079W WO9927447A1 WO 1999027447 A1 WO1999027447 A1 WO 1999027447A1 CA 9801079 W CA9801079 W CA 9801079W WO 9927447 A1 WO9927447 A1 WO 9927447A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- information
- class
- modeled
- attribute
- oriented
- Prior art date
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
Definitions
- This invention relates to the field of object-oriented programming, and in particular to a new kind of class object.
- Code driven software is very flexible, but has the disadvantage of being labor intensive, cloned rather than shared, and requiring long development and testing cycles.
- Data Driven software offers fast development, improved reliability, shorter testing cycle, allows many tasks to be automated, but has limited flexibility, and demands that every possible requirement in framework design must be anticipated.
- MIB Management Information Base
- NMS Network Management Systems
- a Managed Object definition as specified in a Management Information Base (MIB) contains naming, containment, attribute, and structure information needed for Network Management Systems (NMS's) to communicate about a particular type of network component, 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.
- MIB Management Information Base
- NMS Network Management Systems
- a Managed Object includes a subset of the object-oriented paradigm.
- an object-oriented "Class” can contain provisioning rales and behavior but it is limited in what mechanisms are provided for describing naming, containment, attribute, and structure information. Certain parameters of network components are not inherited.
- 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 familiar with the particular type of network component, for example, an LGS (Loop/Ground start Subscriber) card for a Newbridge Networks Corporation 3600 Bandwidth Manager.
- An object of the invention is to alleviate this problem.
- 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, and at least some of the behavior of said object being data driven.
- the invention is typically applied to a digital communications network.
- the object encapsulates all the required information about a type of network component into a single unit.
- Such objects are known as generally known KnowledgeModules and are arranged in an object-oriented hierarchy and fully support inheritance and polymorphism.
- KnowledgeModules may be imported and exported to and from text files.
- a KnowledgeModule builds on the concepts of "Managed Object” (see ITU/CCITT standard M.3010) and the object-oriented "Class” from the Smalltalk programming language (see Goldberg, A. and Robson, D., "Smalltalk-80: The Language and its Implementation", Reading, Mass.: Addison- Wesley, 1983).
- Knowledge modules are class with extra properties, such as the ability to specify certain things about objects.
- KnowledgeModule 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.
- Knowledge Modules combine the data driven and code driven approaches to provide a very efficient, flexible, quick development of Network Element objects within an Element Management environment.
- Knowledge Modules provide data driven development of the most common parts of the network element objects, generating code for the object classes and accessors, and code for recreating the Knowledge Module data on system initialization. However, due to the varied requirements of the different network element equipment that cannot be anticipated in advance through a data driven approach, Knowledge Modules provide the user with the ability to customize the class by writing code in it. This provides the ultimate in flexibility and efficiency of development.
- KnowledgeModules differ from the traditional object oriented subclass paradigm in that some of the behavior of the KnowledgeModules is data driven, not code driven. For example, when determining the equipment that can be contained within another piece of equipment, the KnowledgeModule looks to its data to determine this information. It is not done through logic within the class, as would be the case in a traditional code based environment. On the other hand, it differs from the traditional data driven environment in that some behavior is generated from the data into class/instance methods, but other behavior is custom, and is written by the developer.
- the implementation consists of an (object-oriented) "Class” which is a subclass of "Modeled Object” and an instance 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 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.
- the source code of the Modeled Object subclass may be exported and imported to a text file or source code management system. After importing, a Modeled Object subclass can create its Modeled Object Template, thereby bootstrapping the system.
- KnowledgeModules can be implemented in the Smalltalk programming language as implemented by ObjectShare Inc.. Persistent multi-user access to the Modeled Object instances in provided by the GemStone object-oriented database of GemStone Systems.
- 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.
- a KnowledgeModule encapsulates all network management information which is required about a class of network component. This information includes:
- KnowledgeModules are arranged in an object-oriented hierarchy and fully support inheritance and polymorphism. KnowledgeModules may be imported and exported to and from text files.
- KnowledgeModule 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 inheritance and polymorphism may be used to implement Knowledge Modules.
- the implementation consists of a (object-oriented) "Class” in which is a subclass of "Modeled Object" and an instance 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.
- the source code of the Modeled Object subclass may be exported and imported to a text file. After importing, a Modeled Object subclass can create its Modeled Object Template, thereby bootstrapping the system.
- Instance variables container - reference to the containing object dependents addressKey inventory - collection of contained objects connectionRegistry registries objectState compoundState myName
- Figure 2 shows the relationship between a sample Modeled Object, a WENode9600Type 1, and its Modeled Object template.
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP98955292A EP1031080A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
CA002311328A CA2311328A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CA 2221654 CA2221654A1 (en) | 1997-11-20 | 1997-11-20 | Knowledge module |
CA2,221,654 | 1997-11-20 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1999027447A1 true WO1999027447A1 (en) | 1999-06-03 |
Family
ID=4161784
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/CA1998/001079 WO1999027447A1 (en) | 1997-11-20 | 1998-11-20 | Knowledge module |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP1031080A1 (pt-BR) |
CA (1) | CA2221654A1 (pt-BR) |
WO (1) | WO1999027447A1 (pt-BR) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2816420A1 (fr) * | 2000-11-06 | 2002-05-10 | Evidian | Procede de gestion d'au moins une ressource informatique |
EP1326373A2 (en) * | 2001-12-19 | 2003-07-09 | Alcatel Canada Inc. | Method of invoking polymorphic operations in statically typed language |
EP1361697A2 (en) * | 2001-12-19 | 2003-11-12 | Alcatel Canada Inc. | Network management system architecture |
GB2401206A (en) * | 2003-04-29 | 2004-11-03 | Infinite Reason Ltd | Object orientated data processing system |
CN1333336C (zh) * | 2006-06-23 | 2007-08-22 | 清华大学 | 一种支持异构构件的构件库统一管理方法 |
Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0631232A2 (en) * | 1993-06-25 | 1994-12-28 | Microsoft Corporation | 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 |
WO1996035991A1 (en) * | 1995-05-05 | 1996-11-14 | 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
Patent Citations (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP0631232A2 (en) * | 1993-06-25 | 1994-12-28 | Microsoft Corporation | 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 |
WO1996035991A1 (en) * | 1995-05-05 | 1996-11-14 | Apple Computer, Inc. | A network component system |
Cited By (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
FR2816420A1 (fr) * | 2000-11-06 | 2002-05-10 | Evidian | Procede de gestion d'au moins une ressource informatique |
EP1326373A2 (en) * | 2001-12-19 | 2003-07-09 | Alcatel Canada Inc. | Method of invoking polymorphic operations in statically typed language |
EP1361697A2 (en) * | 2001-12-19 | 2003-11-12 | Alcatel Canada Inc. | Network management system architecture |
EP1326373A3 (en) * | 2001-12-19 | 2006-01-11 | Alcatel Canada Inc. | Method of invoking polymorphic operations in statically typed language |
EP1361697A3 (en) * | 2001-12-19 | 2006-10-04 | Alcatel Canada Inc. | Network management system architecture |
GB2401206A (en) * | 2003-04-29 | 2004-11-03 | Infinite Reason Ltd | Object orientated data processing system |
CN1333336C (zh) * | 2006-06-23 | 2007-08-22 | 清华大学 | 一种支持异构构件的构件库统一管理方法 |
Also Published As
Publication number | Publication date |
---|---|
CA2221654A1 (en) | 1999-05-20 |
EP1031080A1 (en) | 2000-08-30 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
KR100550758B1 (ko) | 구성 변경 관리 방법, 컴퓨터 판독가능한 기록 매체 및 데이터 처리 시스템 | |
US7188335B1 (en) | Product configuration using configuration patterns | |
US5504892A (en) | Extensible object-oriented file system | |
JP4515541B2 (ja) | 電気通信サービスを支援し管理するシステム及び方法 | |
CN101315604B (zh) | 软件定制模块的实现方法及系统 | |
WO2006099046A2 (en) | Automated interface-specification generation for enterprise architectures | |
US7346899B2 (en) | Lookup facility in distributed computer systems | |
WO1999008211A1 (en) | Auto definition of data sets and provisioning interfaces for call automation | |
AU6137398A (en) | Automatic generation of reconfiguration scripts for telecommunication devices | |
US20160239271A1 (en) | Method and Apparatus for Enabling Agile Development of Services in Cloud Computing and Traditional Environments | |
Ledeczi et al. | Metaprogrammable toolkit for model-integrated computing | |
WO1999027447A1 (en) | Knowledge module | |
Henttonen et al. | Integrability and extensibility evaluation from software architectural models–A case study | |
Cheong et al. | Frame-based method for customizing generic software architectures | |
CN117055766A (zh) | 基于Ant Design的树形数据处理方法、装置、介质及电子设备 | |
CA2311328A1 (en) | Knowledge module | |
Pavlou | Using distributed object technologies in telecommunications network management | |
Sengul et al. | Building a service provisioning system using the Enterprise JavaBean framework | |
Fregonese et al. | Architectural framework modeling in telecommunication domain | |
Klimathianakis et al. | DELOS-A repository based environment for developing network centric applications | |
Akehurst et al. | UML specification of distributed system environments | |
Talevski et al. | Meta model driven framework for the integration and extension of application components | |
US20050278349A1 (en) | Data model architecture with automated generation of data handling framework from public data structures | |
Al-Tahat et al. | Using hot-spot-driven approach in the development of a framework for multimedia presentation on the Web | |
Kurata et al. | Object-Oriented Programming in Visual Basic .NET |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): CA JP US |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LU MC NL PT SE |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
ENP | Entry into the national phase |
Ref document number: 2311328 Country of ref document: CA Kind code of ref document: A Ref document number: 2311328 Country of ref document: CA |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1998955292 Country of ref document: EP |
|
WWP | Wipo information: published in national office |
Ref document number: 1998955292 Country of ref document: EP |
|
WWR | Wipo information: refused in national office |
Ref document number: 1998955292 Country of ref document: EP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: 1998955292 Country of ref document: EP |