WO2011072722A1 - Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication - Google Patents

Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication Download PDF

Info

Publication number
WO2011072722A1
WO2011072722A1 PCT/EP2009/067190 EP2009067190W WO2011072722A1 WO 2011072722 A1 WO2011072722 A1 WO 2011072722A1 EP 2009067190 W EP2009067190 W EP 2009067190W WO 2011072722 A1 WO2011072722 A1 WO 2011072722A1
Authority
WO
WIPO (PCT)
Prior art keywords
managed object
object model
mom
query
repository
Prior art date
Application number
PCT/EP2009/067190
Other languages
English (en)
Inventor
Zoltan Theisz
Epifanio Salamanca
David Cleary
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to PCT/EP2009/067190 priority Critical patent/WO2011072722A1/fr
Publication of WO2011072722A1 publication Critical patent/WO2011072722A1/fr

Links

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/0233—Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
    • G06F16/36—Creation of semantic tools, e.g. ontology or thesauri
    • G06F16/367—Ontology

Definitions

  • the invention relates to a semantic digital repository for management models for communications networks.
  • Telecommunications networks comprise a plurality of interconnected hardware devices or so-called nodes.
  • Each node comprises a managed object model MOM containing a collection of objects or so-called classes through which the BSS and OSS programs can examine and manipulate the node and thus the MOM provides an object-oriented network specific implementation and network features.
  • MOMs In practice, the large quantity of standardised and vendor specific MOMs creates a proprietary environment with a substantial degree of inherent complexity and interdependency between MOMs. Hence, the current approach to managing, structuring and indexing such MOMs is one that requires a substantial amount of human interaction and expertise. As with any human intense activities, the resulting system is prone to errors and is very labour intense to test.
  • MOMs form the basis of the information needed to create integration software.
  • Such models change as the network changes and currently the only way to manage and understand these changes is to search for objects or classes that have been added or removed.
  • MOM Managed Object Model
  • the Managed Object Model defines the information model with regard to node management, at the time of the design of the node.
  • the MOM presents a view of all the manageable resources in the node, and all the parameters and actions associated with these resources.
  • An example of a MOM is the configuration model as defined by the network element design team for a given version of a radio base station RBS of the network.
  • the MOMs describe the management capabilities of a network element such as the RBS from the configuration management CM, fault management FM and performance management PM perspective.
  • Each MOM may contain many managed object classes MOCs, which are abstract representations of any resource or network element available in the node, defined at design time. The class maintain all characteristics of a managed object e.g. attributes, notifications and management operations.
  • the generated MOM is then documented as a textual description in a word processing document, which is written to explain the model.
  • the MOM information is also captured in diagrams expressed in UML notation, which are pasted into the document to depict the relationships between the managed object classes.
  • the MOM is then implemented in either the network element (i.e. the node) or the management system which manages the network.
  • the MOM When the management system is deployed, the MOM is instantiated with network information to create a Managed Information Model (MIM).
  • MIM Managed Information Model
  • An adaptor thus needs to be created if a multi-vendor application or bespoke network management application needs to access MOM information, for example when a node is added or upgraded.
  • the knowledge to understand the existing MIM is drawn from the MOM documentation and encoded into software logic.
  • a disadvantage of this is that captured UML diagrams embedded within the documents are not searchable via classic text based retrieval.
  • the above-mentioned process is a state-of-the-art procedure of contemporary network management methodology, the procedure is very difficult and labour intensive and as such has been identified as an area for potential operating expenditure reduction by telecom vendors.
  • the key point of mitigating the non-optimal characteristics of the above-mentioned process is to reduce the development effort required to create a running management system by increasing the reuse of previous modelling assets via extensible data repository architecture.
  • an object of the present invention is to provide a digital repository for MOMs which is searchable and which can expose many other features that facilitate the task needed to create integration software.
  • a computer system which comprises a repository containing a plurality of semantic representations of managed object models MOMs of respective nodes of a communication network.
  • Each managed object model MOM comprises a plurality of managed object classes MOCs which define attributes of respective network resources within a given node, the representations being stored in the repository as directed graph machine-readable data that define relationships between the managed object classes MOCs within the node.
  • the computer system further comprises an input for receiving a search query concerning information relating to a managed object model MOM stored within the repository, and a processor arranged to receive the query and to perform a search of the repository and to output information relating to one or more managed object models MOMs in accordance with the defined search criteria.
  • the present invention thus provides a model repository that can store every version of the relevant management models, which can include relevant instantiated managed information models MIMs.
  • the invention also provides adequate mechanisms to compare and analyse any versions of those models in order to help users to investigate network management related business scenarios.
  • this invention improves the current situation, where such investigations are mostly carried out via manual inspection that necessitates searching through various structured and unstructured databases of text documents.
  • the present invention capitalises on the beneficial properties of semantic ontologies when it comes to compare both structural (T-Box) and individual (A-Box) elements within them.
  • the invention stores the managed object models in formalised ontologies and any later changes to those pieces of information can also be stored.
  • Each representation of the managed object model MOM in the repository may comprise supplementary identifying information, for example defining at least one of: the type of node, the version of the managed object model MOM, the creation date of the managed object model MOM, and an expiry date of the managed object model MOM.
  • the processor can be arranged to identify the or each Managed Objects MOs in a managed object model MOM in response to a query for Managed Objects MOs having defined supplementary identifying information and to output information concerning the or each identified managed object.
  • the processor may be arranged to determine the difference or provide a comparison between the managed objects MOs of two different versions of a managed object model MOM for a given node and to output information giving the attributes of respective network resources.
  • the processor may be arranged to determine the interdependency between managed objects MOs in a managed object model MOM in response to a query and to output information defining the interdependency. In this manner a developer is able to determine which managed object classes in a managed object model are affected by a change in an attribute of another object class in the managed object model MOM.
  • the processor is arranged to output information in response to a query in the form of text, in the form of a script or in the form of a graph, the user being able to select the desired form of output as appropriate.
  • a method for the provision of information relating to a plurality of managed object models MOMs of nodes of a communication network Each managed object model MOM comprises a plurality of managed object classes MOCs defining attributes of respective network resources within a given node.
  • the method according to the second aspect comprises the step of generating a managed object model MOM for each node, then converting each managed object model MOM into a respective directed graph machine-readable data representation of the managed object model MOM in such as way that the representation defines relationships between the managed objects MOCs within the managed object model MOM.
  • Each representation is then stored in a data repository together with representations of other managed object models MOMs.
  • a query for information relating to a managed object model MOM stored within the repository can then be performed by entering relevant search criteria into a processor connected to the repository and causing the processor to perform a search of the repository using the search criteria.
  • the processor then outputs information from the repository relating to one or more managed object models MOMs within the repository in accordance with the defined search criteria.
  • Each representation of a managed object model MOM is advantageously enriched with supplementary identifying information for the managed object model MOM prior to storage in the repository.
  • the representations may be enriched with supplementary identifying information which define at least one of the type of node, the version of the managed object model, the creation date of the managed object model MOM, and an expiry date of the managed object model MOM.
  • a query for information relating to a managed object model MOM having defined supplementary identifying information can then be performed by entering relevant search criteria.
  • the supplementary identifying information defines the type of node and the version of the managed object model MOM
  • a query can be performed to determine the comparison between the managed objects MOs of two different versions of a managed object model MOM for a given node.
  • queries may be performed to determine the interdependency or difference between managed object classes MOCs in a managed object model MOM.
  • the user may select whether the information output in response to a query is output in the form of text, in the form of a script or in the form of a graph.
  • the initial generating step for each managed object model MOM for example comprises generating a managed object model MOM in the UML or another unified modelling language.
  • the converting step for each managed object model MOM then comprises converting the managed object model MOM into a standardized format such as XMI.
  • the standardised format of managed object model MOM can then be enriched with the above-mentioned supplementary identifying information and converted into the prevailing web ontology language such as the current version of OWL, in which format the managed object model MOM is stored in the repository.
  • Similar representations of standardised managed object models MOMs can also be stored in the repository.
  • the repository is also able to store text and other documents which describe respective managed object models MOMs.
  • the information output by the processor can thus be used to configure a communications network.
  • system in accordance with this invention can be implemented on a user's computer system using software provided to a user on a computer usable medium having computer readable instructions.
  • the system operated by one user with other users being allowed, for example by means of a licence, to store semantic representations of managed object models MOMs of respective nodes of their communication networks thereon.
  • a method of analysing the software configuration in a communication network comprising a plurality of nodes having respective managed object models MOMs defining attributes of network resources within the node.
  • the method comprises accessing a repository containing a plurality of managed object models MOMs stored as directed graph machine-readable data representations of the respective managed object models MOMs, the representations defining relationships between managed object classes MOCs within the respective managed object models MOMs.
  • the method further comprises performing a semantic query for information relating to an attribute of a managed object model MOM stored within the repository, and outputting information from the repository relating to one or more managed object models MOMs within the repository in accordance with the query.
  • the information which is output can merely provide general information about a managed object models MOMs such as its object classes and the attributes thereof. This information can then be used as point of reference by others when designing a network element or system.
  • the system is also able to compare different versions of the same managed object models MOM or to determine the interdependence between managed object classes within the models.
  • the information output from the system thus facilities the analysis and configuration of communications networks.
  • Figure 1 is a schematic diagram of a portion of mobile telephone communications network
  • Figure 2 is a graphical representation of a managed object model for an RNC node of the apparatus of Figure 1 ;
  • Figure 3 is a graphical snapshot of a given managed object class MOC (iubLink) of the RNC node of Figure 2;
  • Figure 4 is a schematic diagram of a computer system illustrating an embodiment of the invention
  • Figure 5 is a flow diagram illustrating a first part of an embodiment of method in accordance with this invention
  • Figure 6 is a flow diagram illustrating a second part of the method of Figure 5;
  • Figure 7 shows a graphical -style output by the system of Figure 1 ;
  • Figure 8 shows a report -style output produced the system of Figure 1 ;
  • FIG. 1 of the drawings there is shown a portion of a mobile telecommunications network 10 which comprises a plurality of nodes 11 or so-called managed objects MOs and links 12 that are capable of carrying audio, visual, and data communications.
  • Each node 11 or so-called managed object MOs comprises one or more network resources or so-called object classes that can be managed through the use of OSS and BSS systems.
  • FIG 2 of the drawings there is shown the managed object model 30 of a radio base station (RBS) node 1 1 of the network of Figure 1 .
  • the managed object model 30 shows the managed classes 31 within the node 1 1 and the relationships 80 between those managed classes 31.
  • the managed object model 30 is instantiated using proprietary modelling software such as unified modeling language UML.
  • RNC radio network
  • Each managed object class 31 e.g. iubLink
  • Each managed object class 31 within the model comprises one or more attributes 32 (e.g. iubLoadUIThresholdSpeech and iubLoadDIThresholdSpeech) having defined values.
  • the representation 22 is then stored in a repository 21 of a computer system 20 along with similar representations of other managed objects 30.
  • the repository 21 may also contain representations 29 of standard managed object models and text documents 28 describing the managed object models 30.
  • the repository 21 is provided in a data storage device, such as a hard drive or other media within the computer system 20.
  • the converting step 76 initially comprises converting the generated managed object model 30 into a standardized XMI format at step 72.
  • the XMI-converted managed object model is then enriched at step 73 with supplementary data 71 and converted into the directed-graph web ontology language OWL at step 74.
  • the supplementary data 71 defines at least one of: the type of node 1 1 , the version of the managed object model MOM 30, the creation date of the managed object model MOM, and an expiry date of the managed object model MOM.
  • the OWL-converted representation of the managed object model 22 is then stored in the repository at step 75 along with other such representations 22: this ensures that all managed object models are stored in a uniformed manner.
  • the computer system 20 further comprises a processor 45 having a data store 40 arranged to query and receive information from the repository 21 .
  • the data store 40 is connected to an input device 43 and an output device 44 of the computer system 20.
  • the processor 45 further comprises a knowledge system 41 and a script generator 42, which are connected to the data store 40.
  • a query is entered by a user at step 90.
  • the data store 40 receives the query and performs a search of the repository 21 at step 91 for records 22,29 having the defined search criteria.
  • the data store 40 may then pass the retrieved records to the knowledge system 41 for classification or to the into the computer system 20 via the input device 43.
  • a first type of search that can be performed is a semantic search, which can analyse domain specific information from one or more model records 22,29. Since the models 30 are stored as directed graph representations 22,29, graph inference engines in the data store 40 can perform first order logic operations on the relationships contained within the managed object model or models 30.
  • a second type of search that can be performed is a model search, which enables the retrieval of information based on any parts of the representative data within the repository 21 and mostly relies on the inherent structure of one record.
  • a third type of search that can be performed is a model difference search, which enables the user to investigate the difference between two different versions of the same managed object model 30.
  • a fourth type of search that can be performed is a model comparison search, which enables the user to compare two different versions of the same managed object model 30 and to deliver the difference report in an efficient graphical representation of the kind shown in Figure 7 of the drawings, in which the differing managed object classes 31 (e.g. iubLink) and attributes 32 are highlighted in one colour Y for simple identification. Any added classes 31 or attributes 32 are highlighted by a second colour G and likewise any deleted classes 31 or attributes 32 are highlighted by a third colour R. Alternatively the result may be output in the form of a report of the kind shown in Figure 8, which shows each class 31 and an indication of whether the attributes 32 thereof have been created, changed or deleted.
  • iubLink e.g. iubLink
  • the blank nodes in Q1 and Q2 match if their property topologies match, i.e. all the non-blank nodes pointed to by matching properties from the current blank nodes in Q1 and Q2 match and the remaining blank nodes pointed to by other matching properties from the same current blank nodes can be matched by applying this rule recursively. In case of recursive cycles reaching the current blank node pairs in Q1 and Q2 again, they are considered a matching pair, (finite termination policy)
  • Blank nodes in Q1 and Q2 match if their property topologies match, i.e. all the non-blank nodes pointed to by matching properties from the current blank nodes in Q1 and Q2 match and the remaining blank nodes pointed to by other matching properties from the same current blank nodes can be matched by applying this rule recursively. In case of recursive cycles reaching the current blank node pairs in Q1 and Q2 again, they are considered a matching pair, (finite termination policy) Query Orchestration
  • the script generator 42 provides operations to compare any two representations 22,29 in the repository 21 and to output an executable script on the basis of the differences that can map between the respective managed object models MOMs.
  • the repository 21 is thus an ontology storage enabled content management data store, which serves both as a semantic managed object model MOM repository storing all versions, and releases of a managed object model MOM for use by the various network engineers and management systems and also as library of documents which describe the managed object model MOMs in natural languages.
  • the common functionalities of the architecture establish the core of the managed object model MOM store that empowers it with the following facilities:
  • MOM version handling provides version handling facilities of MOM data such as version tagging of MOM elements, version evolution trees etc.
  • managed object model MOM compatibility checking provides a compliancy test in order to check managed object model MOM compatibility against industry standards such as TMForum SID, 3GPP IRP and MTMN models.
  • Management of standardised MOMs enables fast incorporation of standardised managed object model MOMs as the versions change.
  • Mapping between managed object model MOMs provides concise information on the semantic difference between different managed object model MOM ontology representations.
  • Model indexing facilitates fast semantic searchability of managed object model MOM data.
  • Managed object model MOM life-cycle management safeguards the proper handling of managed object model MOM creation, usage and retirement.
  • the system also provides a controlled way for accessing managed object model MOM and related information via a set of well-defined interfaces in order to support the current business processes of system integration with minimal technology adaptation demands.
  • the structure of the service provision environment remains the same.
  • adaptor development requirement is tamed by the substitution thereof by a consistent, future-proof interface set.
  • the same interface set also incorporates managed information model MIM information access facilities.
  • the present invention thus improves current engineering steps through the use of an ontology repository to store the network management data. This allows an increased understanding of the MOMs and MIMs via flexible and effective search facilities.
  • the present invention also enables versatile migration opportunities of already existing (database stored) MOM and MIM assets.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computational Linguistics (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Data Mining & Analysis (AREA)
  • Databases & Information Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Animal Behavior & Ethology (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Stored Programmes (AREA)

Abstract

L'invention porte sur un système informatique (20) qui comprend un référentiel (21) contenant une pluralité de représentations sémantiques (22) de modèles d'objet géré (MOM) (30) de nœuds respectifs (11) d'un réseau de communication. Chaque modèle d'objet géré (MOM) (30) comprend une pluralité de classes d'objet géré (MOC) (31) qui définissent des attributs (32) de ressources de réseau respectives dans un nœud donné (11), les représentations étant stockées dans le référentiel sous la forme de données de graphe orienté lisibles par machine qui définissent des relations entre les classes d'objet géré (MOC) (31) dans le nœud. Le système informatique (20) comprend en outre une entrée (90) pour recevoir une interrogation de recherche concernant des informations relatives à une représentation de modèle d'objet géré (22) stockée dans le référentiel, et un processeur (23) conçu pour recevoir l'interrogation et pour réaliser une recherche dans le référentiel (2) et pour délivrer des informations relatives à un ou plusieurs modèles d'objet géré (MOM) conformément aux critères de recherche définis. Le système peut être utilisé par des ingénieurs de réseau pour analyser et configurer le logiciel dans des réseaux de télécommunication.
PCT/EP2009/067190 2009-12-15 2009-12-15 Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication WO2011072722A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/067190 WO2011072722A1 (fr) 2009-12-15 2009-12-15 Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2009/067190 WO2011072722A1 (fr) 2009-12-15 2009-12-15 Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication

Publications (1)

Publication Number Publication Date
WO2011072722A1 true WO2011072722A1 (fr) 2011-06-23

Family

ID=42629461

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2009/067190 WO2011072722A1 (fr) 2009-12-15 2009-12-15 Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication

Country Status (1)

Country Link
WO (1) WO2011072722A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020526138A (ja) * 2017-09-30 2020-08-27 中興通訊股▲ふん▼有限公司Ｚｔｅ Ｃｏｒｐｏｒａｔｉｏｎ データインタラクションの方法、装置および機器

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
D. CLEARY, B. DANEV, D.O'DONOGHUE: "Using Ontologies to Simplify Wireless Network Configuration", 9 June 2005 (2005-06-09) - 10 June 2005 (2005-06-10), Verona, Italy, pages 1 - 16, XP002598396, Retrieved from the Internet <URL:http://www.cs.nuim.ie/~dod/pubs/05-fomi.pdf> [retrieved on 20100827] *
DANEV B ET AL: "Building semantically rich network management interfaces", WIRELESS COMMUNICATIONS AND NETWORKING CONFERENCE, 3 April 2006 (2006-04-03) - 6 April 2006 (2006-04-06), IEEE LAS VEGAS, NV, USA, pages 2297 - 2304, XP031387549, ISBN: 978-1-4244-0269-4 *
F. STAMATELOPOULOS, N. ROUSSOPOULOS, B. MAGLARIS: "Using a DBMS for Hierarchical Network Management", 1 March 1995 (1995-03-01), pages 1 - 10, XP002598397, Retrieved from the Internet <URL:www.citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.79> [retrieved on 20100827] *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2020526138A (ja) * 2017-09-30 2020-08-27 中興通訊股▲ふん▼有限公司Ｚｔｅ Ｃｏｒｐｏｒａｔｉｏｎ データインタラクションの方法、装置および機器

Similar Documents

Publication Publication Date Title
US8776009B2 (en) Method and system for task modeling of mobile phone applications
US8533660B2 (en) Annotation of models for model-driven engineering
Scicluna et al. Visual modeling of owl-s services
Davy et al. The policy continuum–Policy authoring and conflict analysis
US11348019B2 (en) Advanced workflow based self-serve automation system
US20140337273A1 (en) Upper merged ontology for it architecture
Paskevicius et al. Change impact analysis of feature models
Vitkus et al. Automated expert system knowledge base development method for information security risk analysis
Popoola et al. EMG: A domain-specific transformation language for synthetic model generation
Huynh et al. Automatic modularity conformance checking
Guizzardi et al. Using objects and Patterns to implement domain ontologies
Chaturvedi et al. Service evolution analytics: change and evolution mining of a distributed system
Barros et al. Static analysis for improved modularity of procedural web application programming interfaces
Lu et al. Zen-CC: An automated and incremental conformance checking solution to support interactive product configuration
WO2011072722A1 (fr) Référentiel de modèles numériques sémantiques pour modèles de gestion de réseau de communication
Bouzguenda et al. An agent-based approach for organizational structures and interaction protocols mining in workflow
de Castro Leal et al. Cataloguing provenance-awareness with patterns
Wolvers et al. Embedded systems design flows: integrating requirements authoring and design tools
Bu et al. An analysis of decision-centric architectural design approaches
Deng et al. Trustworthiness Derivation Tree: A Model of Evidence-Based Software Trustworthiness
Kritikos et al. A flexible semantic kpi measurement system
Fill On the social network based semantic annotation of conceptual models
Hartig et al. Automatic component selection with semantic technologies
Hallerbach et al. Correct configuration of process variants in provop
Cares et al. A Reference Model for i

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 09803747

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09803747

Country of ref document: EP

Kind code of ref document: A1