System and method for managing OSS component configuration

• US 20050114642A1
• Filed: 11/26/2003
• Published: 05/26/2005
• Est. Priority Date: 11/26/2003
• Status: Abandoned Application

• Current Assignee: Intec Telecom Systems PLC (CSG Systems International Incorporated)
• Original Assignee: Intec Telecom Systems PLC (CSG Systems International Incorporated)
• Inventors: Cooke, David John, Watson-Luke, Brett
• Application Number:
  US10/723,246
• Publication Number:
  US 20050114642A1
• Time in Patent Office: Days
• US Class Current: 713/1
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files

Abstract

Systems and methods manage configurations for multiple OSS components. A method starts by receiving a high level configuration that includes multiple high level configuration items. The high level configuration is translated to a low level configuration, the low level configuration including multiple low level configuration items. The low level configuration is translated to at least one OSS component specific configuration and sent to the OSS component.

Claims

1. A method for managing a configuration for a plurality of OSS components, the method comprising:

receiving a high level configuration, the high level configuration including a plurality of high level configuration items;

translating the high level configuration to a low level configuration, the low level configuration including a plurality of low level configuration items;

translating the low level configuration to at least one OSS component specific configuration; and

sending the at least one OSS component specific configuration to at least one OSS component.

2. The method of claim 1, wherein the high level configuration substantially conforms to a version of XML.

3. The method of claim 2, wherein translating the high level configuration to a low level configuration includes applying an XML style sheet to the high level configuration.

4. The method of claim 1, wherein the low level configuration substantially conforms to a version of XML.

5. The method of claim 1, wherein each of the plurality of configuration items is identified by an identifier relative to a configuration root.

6. The method of claim 5, wherein the identifier is a URI.

7. The method of claim 1, wherein the high level configuration includes ordering rules defining an order for updating the plurality of OSS components and wherein the OSS specific configuration is sent in accordance with the ordering rules.

8. The method of claim 1, wherein each of the plurality of configuration items have a configuration type and wherein the order for updating the plurality of OSS components is determined based on the configuration type.

9. The method of claim 1, wherein translating the high level configuration to a low level configuration includes:

generating a set of partial configuration items;

reconciling the set of partial configuration items against previously generated configuration items; and

merging the reconciled set of partial configuration items with the low level configuration items to form a set of full item definitions.

10. The method of claim 1, wherein translating the high-level configuration to a low-level configuration includes mapping a set of high-level configuration items to a set of low-level configuration items.

11. The method of claim 1, wherein translating the high-level configuration to a low-level configuration includes filtering the set of high-level configuration items such that the filtered configuration items are not part of the set of low-level configuration items.

12. The method of claim 1, wherein the high-level configuration items represent an abstracted set of data elements for a set of OSS components and wherein the low-level configuration items represent a set of OSS-specific data elements.

13. A system for managing a configuration for a plurality of OSS components, the system comprising:

a version control system having a version repository operable to maintain a high-level configuration having a plurality of high-level configuration items, each of said high-level configuration and high-level configuration items having a version; and

a configuration server operable to receive a version of the high-level configuration and high-level configuration items for storage in a configuration database, wherein the configuration server is operable to;

translate the high level configuration to a low level configuration, the low level configuration including a plurality of low level configuration items;

translate the low level configuration to at least one OSS component specific configuration; and

send the at least one OSS component specific configuration to at least one OSS component.