Method and a System Relating to Network Management

• US 20080294418A1
• Filed: 12/05/2005
• Published: 11/27/2008
• Est. Priority Date: 12/05/2005
• Status: Active Grant

• Current Assignee: Ericsson AB (Telefonaktiebolaget LM Ericsson)
• Original Assignee: Telefonaktiebolaget LM Ericsson
• Inventors: Cleary, David, Danev, Boris
• Granted Patent: US 7,953,580 B2
• Time in Patent Office: Days
• US Class Current: 703/21
• CPC Class Codes: H04L 41/0233 Object-oriented techniques, for representation of network management data, e.g. common object request broker architecture [CORBA]
• CPC Class Codes: H04L 41/0803 Configuration setting
• CPC Class Codes: H04L 41/0889 Techniques to speed-up the configuration process
• CPC Class Codes: H04L 41/16 using machine learning or artificial intelligence

Abstract

The present invention relates to a method for network management comprising configuration of control protocols between network elements in a network represented through a current, static, network element object model comprising a number of managed objects with attributes and instances and representing resources. It comprises the steps of: transforming the current network element object model to a machine readable and executable formal network element object model; identifying configuration tasks needed for the configuration of the relevant control protocols; modelling a formal configuration task model using information about the configuration tasks and the formal network element object model; building a formal configuration workflow model using the formal network element object model and the formal configuration task model, said formal configuration workflow model defining the relationships between different configuration tasks required for performing or completing a number of given actions or to achieve a number of given goals.

Claims

1-23. -23. (canceled)

24. A method of network management including configuring control protocols between network elements in a network represented by a current static network element object model comprising managed objects having attributes and instances to represent network resources, the method comprising:

transforming, in a transforming component, a current static network element object model to a machine readable and executable formal network element object model by;

forming a formal ontology to represent the current static network element object model by adding formal semantics and formal domain assumptions; and

using frame logic to formally model managed object classes, attributes and relationships;

identifying, in an identifying component, configuration tasks needed to configure relevant control protocols;

modeling, in a modeling component, a formal configuration task model using information about the configuration tasks and the formal network element object model by;

forming a formal ontology to represent the formal configuration task model;

creating formal configuration ontologies for different configuration tasks needed to configure one or more of the relevant control protocols using frame logic; and

building, in a workflow building component, a formal configuration workflow model using the formal network element object model and the formal configuration task model by providing respective workflows using frame logic primitives, wherein the formal configuration workflow model defines relationships between the different configuration tasks required for performing or completing one or more given actions, or to perform a selected action.

25. The method of claim 24 wherein transforming the current static network element object model further comprises creating conceptual or explicit meanings for the managed objects associated with the current static network element object model using frame logic primitives to represent managed object sub-classes, containments, and association relationships.

26. The method of claim 25 wherein the formal domain assumptions comprise domain constraints.

28. The method of claim 26 further comprising:

fetching the domain assumptions from specifications specifying the managed objects included in the current static network element managed object model; and

adding the domain assumptions.

29. The method of claim 24 wherein the frame logic comprises F-logic, and wherein transforming the current static network element object model further comprises:

mapping a Unified Modeling Language (UML) Managed Object Model to F-logic; and

modeling constraints using F-logic rules.

30. The method of claim 24 wherein modeling the formal configuration task model further comprises ontologically establishing relationships between the protocol configuration tasks and the formal representation of the managed objects associated with the formal network element managed object model.

31. The method of claim 24 wherein the configuration tasks comprise one or more of adding a network element, replacing a network element, removing a network element, preparenting a network element, reconfiguration of a network element, and performing a configuration task on part of a network element.

32. The method of claim 30 wherein a configuration task comprises one or more sub-tasks, and further comprising ontologically representing the configuration task and the sub-tasks.

33. The method of claim 24 further comprising manually or automatically providing external information to the formal configuration workflow model.

34. The method of claim 24 wherein the workflow model is configured to:

order the configuration task and/or sub-tasks to perform one or more different configuration task actions;

provide relevant data to respective configuration tasks; and

propagate relevant data between configuration tasks and sub-tasks.

35. The method of claim 24 further comprising inputting actual data from the network to assist in providing relationships between configuration tasks and/or sub-tasks.

36. The method of claim 24 further comprising using frame logic axioms to build configuration workflows.

37. The method of claim 24 further comprising executing the formal configuration workflows with data associated with network elements to obtain a semi-automatic configuration of the control protocols.

38. The method of claim 37 wherein executing the formal configuration workflows comprises using an inference engine to execute relevant workflows.

39. The method of claim 38 further comprising performing a configuration task by:

loading the formal network element managed object model, the formal configuration task model, and a relevant configuration workflow ontology stored in an ontology repository for a given configuration task comprising one or more configuration tasks and/or one or more sub-tasks into a database;

requesting a representation of network data from the network to be configured;

converting the representation of network data to ontology instances;

providing a connection to the database via an inference engine Application Programming Interface (API) to provide a user interface;

automaticall performing the configuration task via the user interface;

converting the resulting configuration ontology instances to configured network data; and

introducing the configured network data into the network to obtain a configured or reconfigured network or network element.

40. The method of claim 24 wherein the network comprises a Radio Access Network (RAN).

41. The method of claim 40 wherein the RAN comprises one of a Third Generation RAN (3G RAN), a Wideband Code Division Multiple Access RAN (WCDMA RAN), a Universal Mobile Telecommunications System Terrestrial RAN (UTRAN), a Global System for Mobile Enhanced Data rates for GSM Evolution RAN (GERAN), and a Code Division Multiple Access 2000 RAN (CDMA 2000 RAN).

42. The method of claim 24 wherein the current network element managed object model comprises an Operation and Maintenance model.

43. The method of claim 39 wherein the representation of network data comprises an eXtensible Markup Language (XML) representation of network data.

44. The method of claim 39 wherein the XML representation of network data comprises a Bulk Configuration Management (CM) XML representation.

45. A network management system for configuring network element control protocols between network elements in a network represented by a current static network element managed object model comprising one or more managed objects having attributes and instances to represent network resources, the system comprising:

a transformer component configured to transform a current static network element managed object model to a machine readable and executable formal network element managed object model;

an enriching component communicatively connected to the transformer component, and configured to add formal semantics and formal domain assumptions to the formal network element managed object model;

an identifying component configured to identify configuration tasks needed to configure one or more control protocols;

a modeling component configured to model a formal configuration task model using information in the formal network element managed object model and information about the configuration tasks;

a workflow building component configured to build a formal configuration workflow model using the formal network element managed object model, the formal configuration task model, and external information, wherein the formal workflow configuration model defines relationships between different configuration tasks needed to perform or complete one or more actions comprising one or more configuration tasks; and

wherein the transforming component and the modeling component comprise an ontogical forming component configured to;

form ontologies representing the current network managed object model and the configuration task model; and

generate the formal network element managed object model and the formal configuration task model based on the formed ontologies, respectively.

46. The system of claim 45 wherein the enriching component is configured to create conceptual or explicit meanings for the managed objects of the current static network element object model using frame logic primitives to represent managed object sub-classes, containments, and association relationships.

47. The system of claim 46 wherein the workflow building component is configured to collect dedicated or external knowledge to provide workflows, and wherein the generated formal configuration workflows are configured to automatically collect data required for configuration workflows and to distribute data to configuration tasks.

48. The system of claim 45 wherein each of the transforming component, the modeling component, and the workflow building component are communicatively connected to an ontology repository that stores the formal models, and wherein the system further comprises:

an application database;

a network data to ontology instance converting component;

an ontology instance to network data converting component; and

a controller connected to a user interface, and configured to request the network data and provide a connection to the application database via an interface engine.