EP1687731A2 - Systeme et procede de gestion de la configuration de composants de systemes de support d'operations - Google Patents

Systeme et procede de gestion de la configuration de composants de systemes de support d'operations

Info

Publication number
EP1687731A2
EP1687731A2 EP04811475A EP04811475A EP1687731A2 EP 1687731 A2 EP1687731 A2 EP 1687731A2 EP 04811475 A EP04811475 A EP 04811475A EP 04811475 A EP04811475 A EP 04811475A EP 1687731 A2 EP1687731 A2 EP 1687731A2
Authority
EP
European Patent Office
Prior art keywords
configuration
level configuration
items
oss
level
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.)
Withdrawn
Application number
EP04811475A
Other languages
German (de)
English (en)
Inventor
Brett Watson-Luke
David John Cooke
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Intec Telecom Systems Ltd
Original Assignee
Intec Telecom Systems Ltd
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
Priority claimed from US10/723,581 external-priority patent/US20050114479A1/en
Priority claimed from US10/723,243 external-priority patent/US20050114851A1/en
Priority claimed from US10/723,246 external-priority patent/US20050114642A1/en
Priority claimed from US10/723,612 external-priority patent/US20050114692A1/en
Priority claimed from US10/723,582 external-priority patent/US20050114240A1/en
Application filed by Intec Telecom Systems Ltd filed Critical Intec Telecom Systems Ltd
Publication of EP1687731A2 publication Critical patent/EP1687731A2/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Definitions

  • the present invention relates generally to telephony OSS systems, and more particularly to managing the configuration of such systems.
  • One aspect of the systems and methods includes a method for managing configurations for multiple OSS components.
  • the 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.
  • the present invention describes systems, clients, servers, methods, and computer-
  • FIG. 1 is a block diagram illustrating the major components of a configuration management system according to embodiments of the invention
  • FIG. 2 is a block diagram illustrating an example of the use of configuration servers in the typical software product development environment according to embodiments of the invention
  • FIG. 3 is a block diagram illustrating configuration abstractions, including high level, low level and OSS component database configuration abstractions according to various embodiments of the invention
  • FIG. 4 is a diagram illustrating a method for managing configurations according to embodiments of the invention.
  • FIG. 5 is diagram illustrating partial configuration items used in various embodiments of the invention.
  • Java based system such as J2EE and JSEE.
  • J2EE and JSEE Java based system
  • J2EE and JSEE Java based system
  • the detailed description below uses terminology, components, and functions common to Java based systems. However, the invention is not limited to such systems, and equivalents to such systems maybe utilized in various embodiments. Such alternative implementation systems are included within the scope of the invention.
  • the following table presents definitions of terms and acronyms used in the detailed description and appendices that follow. Some of the terms are in common usage in the art, while others are specific to the present invention.
  • J2EE Java 2 enterprise edition A specification for an execution environment for enterpris applications written in Java. It includes EJB and JMS.
  • MDB Message driven beans
  • MOM Message oriented middleware OSS Operational support systems
  • Swing User interface toolkit that is part of J2SE UI User interface W3C World wide web consortium XML Extensible markup language XML Schema A W3C recommendation for expressing schemas (structure and valid content) of XML documents.
  • XPath XML Path Language XPath XML Path Language
  • FIG. 1 is a block diagram of the major components of a hardware and software environment 100 incorporating various embodiments of the invention.
  • the systems and methods of the present invention may be provided on a variety of hardware and software systems, including personal-computers, server computers and mainframe computers and may be stored on and executed from various computer-readable media such as RAM, ROM, CD- ROM, DVD-ROM, hard disks, floppy disks, Flash Memory, Compact Flash etc.
  • environment 100 includes configuration server 102, OSS components 108, version control server 114, version control tools 112, configuration tools workbench 106, and additional tools 120.
  • OSS components 108 may include billing OSS component 108.1, customer management OSS component 108.2, or other OSS components such as customer relationship managers, content providers, provisioning systems and the like. Each of these OSS components 108 typically has a database 110 that is proprietary to the OSS component and stores data relevant to the tasks performed by the OSS component. For example, billing database 110.1 will contain data relevant data relevant to billing system 108.1. APIs exist within the OSS components 108 for manipulation of their configuration. The nature of the APIs varies between these systems and depending on the configuration item, but they typically provide the ability to create, read, update and delete or obsolete configuration items in these systems. These APIs may be, however, low level - they deal with configuration in the terms of the OSS components.
  • the function of the configuration server 102 is to provide versions of higher-level configuration items, such as the high-level product catalog items (that span multiple OSS components), or configuration policies and composite configuration items.
  • the configuration server 102 stores these higher level representations of configuration. It can be used to query the configuration in the OSS components, and to update it. It sends (or receives) messages to (from) OSS components 108 when configuration data is updated.
  • a configuration workbench tool 106 may be provided. This GUI application can work either off a file-based representation of the product definitions, or by communicating with the configuration server 102, via its APIs.
  • the configuration server 102 may obtain versions of configurations from version control server 114 through configuration workbench tool 106.
  • version control tools 112 may be provided. These are applied to the file-based data/representation 130 of the configuration. These include basic tools-f ⁇ r committing changes to configuration, viewing differences ' between configuration, and grouping configuration items, for version control purposes. Additional configuration tools 120 may be provided that can extract configuration from these systems, to an extemal ⁇ le-based form, where it may easily be manipulated using file-based tools and to load the configuration from its file-based representation back into the OSS components. These are part of the configuration tools user interface. These tools 120 interact with the OSS components via the configuration server 102.
  • the XML schemata 132 depicted as "interacting" with the file-based representation of the configuration 134 are the documents that define the structure of the configuration data in its file-based form. Tools and developers can use the knowledge embedded in these schemas in order to assist them in reading or processing the configuration.
  • Configuration APIs provide access to the configuration data in OSS components 108 .
  • the configuration server 102 provides a unified API for accessing the configuration in the OSS.
  • the API in one example embodiment, include the following functions:
  • the OSS component configuration-APIs maybe part of the OSS component 108 itself, and may execute on any platform on which these OSS components are available.
  • the general configuration API maybe part of the configuration server 102, and executes on the supported platforms for the ' donfiguration server 102.
  • OSS Import and Export Overview The terms import and export are used, respectively, to mean obtaining configuration data from the OSS component 1 8 so that it can be placed into the configuration server database 104, and to load the configuration data back into the OSS component 108.
  • requirements for these components include the following functionality:
  • supported versions of OSS components 108 are supported by the import and export tools.
  • the configuration items that apply for the various versions of the product differ between releases.
  • the attributes of some configuration items differ between releases.
  • Validations and business rules that apply to various configuration items differ between releases.
  • the API for accessing the configuration items can vary between releases. •
  • the transport mechanism for API calls varies between the releases. (Note that the variations may not be just between major releases. Minor releases and maintenance releases may also introduce changes of this nature.)
  • Import and Export Mechanisms The import and export functionality may be met in part by functionality provided by the configuration server 102 and in part by functionality provided by the configuration tools GUI.
  • the configuration server 102 provides an API that allows clients to directly obtain or update a file-based, which in one example embodiment is an XML representation, of the configuration items stored in CB 122 and CM ⁇ 24 .
  • a file-based which in one example embodiment is an XML representation
  • XML is just one type of file-based form that can be used for this purpose, and that the inventive subject matter hereof is in no way limited to XML files formats.
  • the import and export operations may be performed by components called publishers. These are described in the Configuration Server section herein.
  • the GUI provides file/folder explorer views of the configuration server database 104 that allow imports and exports via menu actions, and allow items to be sent to the OSS components 108 via file copy-and-paste operations.
  • the configuration server 102 filesystem module that provides this functionality is described in U.S.
  • the configuration server 102 administration console also provides commands for import/export, and is described in U.S. patent application serial number , filed November 26, 2003, entitled “SYSTEMS, METHODS AND SOFTWARE TO CONFIGURE AND SUPPORT A TELECOMMUNICATIONS SYSTEM” (Attorney Docket No.: 500.825US 1) which has been previously incorporated by reference.
  • the import may be to an XML format
  • the export may be from the XML format
  • the product catalog format may be specified as a set of related XML Schemas for the * catalogs, categories, charge types and components.
  • the product catalog schemas may be extensible.
  • the schema for the OSS components 108 representations may be generated from the as described in detail below.
  • Execution Environment The import and export related functionality may be provided in the configuration server 102 and configuration tools UI.
  • the execution environments of these components may be described in other sections hereof.
  • version control system 114 The implementation of the version control system 114 ma be based on CVS. See
  • CVS Web site http://www.cvshome.org for documentation on CVS.
  • the implementation consists of the following components:
  • CVS server software for managing the version control repository.
  • CVS client software for accessing the version control repository. Additional support for determining the differences between configuration items in the repository and local changes and for assisting the user to merge them.
  • These operations may be provided in the configuration GUI by the Netbeans modules 510 for CVS.
  • An API is provided to perform grouping operations.
  • a visual representation of groups may be provided for usability purposes.
  • CVS Server CVS provides the core version control facilities, and the management of the version control repository in some embodiments of the invention.
  • the software environment 100 may include software components for CVS that have been built for supported platforms.
  • CVS Client There may be numerous CVS client applications and libraries available for accessing CVS.
  • the configuration tools GUI is required to interact with the version control system, and so the CVS client facilities provided is based on the needs of the GUI.
  • a command-line client may be provided in some embodiments of the invention.
  • Grouping API Support for version control operations on groups of configuration items are typically required.
  • a grouping API may be provided, and actions may be provided in the configuration tools GUI for performing version control operations on these groups. See U.S. patent application serial number , filed November 26,
  • the grouping API provides Java classes for manipulating grouping information, and serialisation to XML form, and instantiation from XML form.
  • the following facilities maybe provided: • JavaBeans may be provided for representing grouping information.
  • an XML form is used for grouping information. The ability to select items from a group in the GUI and apply CVS operations on them. The ability to select items from a group in the GUI and import or export them
  • the version control server 128 can be run on any platform that CVS can be ported to. Examples of such operating systems include but are not limited to: Solaris available from Sun Microsystems, Inc., AIX available from IBM, Inc., and HP/UX available from Hewlett
  • the version control client tools utilize a system with the IRE version 1.4.1 or later.
  • the configuration server 102 is responsible for one or more of the following functions: Providing a centralised location that can be queried or accessed to update configuration in the OSS. Ensuring that configuration is changed consistently across the OSS. Auditing changes to configuration across the OSS. Providing notifications to interested parties when configuration changes. Enforcing security on changes to the configuration. • Enforcing locking on configuration items.
  • the configuration server 102 may store these higher-level configuration items, and may propagate changes to these items to the OSS components 108 in the form of the lower level configuration items that may be used to implement the abstractions.
  • the configuration may include a catalog component.
  • the catalog component may be responsible for: Providing transactional updates to the catalog. Managing the persistence of the catalog. Validating updates to the catalog. Enforcing security on catalog updates and reads. Auditing catalog changes. Providing mechanisms for publishing the catalog into OSS systems. Notifying clients when the catalog changes so they can reflect these changes. Providing facilities for clients to search the catalog.
  • the catalog requirements and the configuration server 102 requirements may be practically the same - the catalog merely represents a subset of the configuration data.
  • the various components of the configuration server 102 maybe implemented using a Java environment and include one or more of the following functions:
  • the core enterprise Java beans that represent configuration entities and catalog entities and that provide business interfaces to these entities. Publishing components that push changes to the configuration data into the various OSS.
  • the CS runs inside an EJB container. This provides: • A standardised application environment, with proven portability. Transaction support, including two-phase commit (if required). Choice in application servers (There may be a multitude of vendors with tested J2EE conformance. See http://java.sun.com/j2ee/compatibility.html). Security (container managed authorization). • Distributed application server support, failover, etc for high performance and availability, for customers that require it. Easy integration of EAI tools (via Java APIs, JMS, etc) and OSS components (via Java APIs, or the Java connector architecture). It should be noted that XML schemas may be used for specifying the catalog data.
  • FIG. 2 provides an exemplary environment 200 according to various embodiments of the invention.
  • Environment 200 illustrates an example of the use of configuration servers in the typical software product development environments.
  • Exemplary environment 200 includes configuration servers 102, development environment 202, test environment 204, and production environment 206.
  • Development environment 202 may be a set of OSS components 108 and other software development tools used by software developers to develop OSS component configurations.
  • the development of an OSS component configuration is an iterative process where new versions of configurations are often developed as the OSS component software is created and enhanced.
  • Test environment 204 typically comprises a set of OSS components that are in the testing phase of a development cycle.
  • the test environment 204 typically uses configuration versions that have been released from the development environment (possibly through an export process) that require further testing to determine whether any faults exist in the configuration.
  • Production environment 206 typically comprises a set of OSS components that is in actual use by a service provider for providing services to their customers, and typically requires configurations that are fairly stable and relatively fault free (as determined in the testing environment).
  • each of these environments 202, 204 and 206 have their own configuration server 102.1, 102.2 and 102.3 respectively.
  • a single configuration server 102 may be used to provide the configuration versions required by the various environments.
  • multiple configuration servers may access a single version control repository.
  • configuration versions are exported through a release generated 208.
  • FIG. 3 is a block diagram illustrating configuration abstractions, including high level, low level and OSS component database configuration abstractions according to various embodiments of the invention.
  • configuration server 102 maintains one or more versions of high-level configuration 302. These versions may be obtained from a version control system 114.
  • the high-level configuration 302 comprises a set of one or more configuration items each of which themselves may be independently versioned.
  • the configuration items may represent product codes, product names, product pricing, product validity dates, invoice formats, address formats and other such data.
  • high-level configuration 302 is a superset of many of the data items found in the various OSS components 108 and represent an abstraction of the various OSS components.
  • configuration tools 106 maybe used to create, update, delete and otherwise manipulate one or more of the configuration items in high-level configuration 302.
  • Configuration server 102 may then generate low-level configuration 304.
  • Low-level configuration 304 typically comprises configuration items that are specific to a particular OSS * ⁇ component 108. These items are obta ⁇ ned ' by selecting relevant high-level ' configuration items and transforming the high-level configuration item (when necessary) to produce low-level configuration items.
  • the transformation may include various sorts of mappings, including numeric transformation, concatenation, truncation, many-to-one, one-to-many and other types of transformations.
  • the embodiments of the invention are not limited to any particular type of transformation.
  • the transformations may include filtering high-level configuration items so that the do not appear in the low-level configuration.
  • the low-level configuration items maybe further transformed into a format that can be exported to an OSS component 108 for updating the OSS component database 110.
  • the high-level configuration 302 and the low-level configuration 304 may be expressed in XML (extensible Markup Language).
  • FIG. 4 is a diagram providing further details on the processes and methods that transform a high-level configuration to a low-level configuration according to some embodiments of the invention.
  • the transformation of a high-level configuration to a low- level configuration maybe referred to as "generation.”
  • the generation process of some embodiments of the invention will now be described.
  • Configuration tools 106 maybe used to modify high-level configuration items 302, resulting in a set of modified items being supplied to the initial generation process 404.
  • the initial generation process 404 distributes each modified configuration item sequentially to all available configuration generators 406.
  • Each configuration generator 406 will process only those items that it is specifically designed to handle.
  • two configuration generators 406 are supplied with the Configuration Server 102 to provide high-level to low-level transformation for product related configuration data.
  • One configuration generator is designed to handle the processing of base and companion products, and the other to handle pricing schemes.
  • the Configuration Server 102 of some embodiments is designed so that it is possible for the configuration users to develop and integrate other configuration generators. Additional configuration generators mayb'e useful; for example, to handle non- XML transformations for a third party OSS component.
  • Each generator 406 may have a stylesheet 410 associated with it. These stylesheets 410 may be stored in the Configuration Server repository 104.
  • a generate ( ) method 408 is invoked. This method applies the stylesheet 410 to the high-level configuration item, transforming it into one or more low-level configuration items 412. This transformation may also include the generation of partial item specifications.
  • a reconciliation process 416 takes the set of newly generated low-level items 412 and compares them with the low-level configuration previously generated 414 (or imported) for these items. Based on this comparison, the reconciliation process 416 creates any new items, updates the existing items, and deletes any items no longer required.
  • the reconciler process 416 is also responsible for processing partial item specifications and merging the reconciled partial items 420 into reconciled low-level configuration items 304.
  • Partial Item Specification it may be necessary as part of the generation process to generate the definition of a single low-level configuration item from multiple high-level configuration items. While in some embodiments stylesheets may be used to produce multiple output XML documents from a single XML input document, multiple input XML documents typically cannot be passed into the generation process. Consequently in some embodiments the generation process includes support for a type of configuration item known as a partial item specification (partial). Partials, which imsome embodiments are internal to a configuration server 102, may be used to improve the flexibility and efficiency of the generation process by allowing the creation of multiple incomplete definitions for the same low-level item. As noted above, single XML document typically cannot be output from multiple input documents.
  • Partials are generated for OSS configuration items that can be represented by multiple values.
  • these entities may include: • Derived attribute arrays, which can have thousands of rows, each represented by unique index values. • Attribute types, which may be based on SQL queries or reference types that may be enumerated to possible multiple values. • Reference Types, which can contain multiple values uniquely identified by a reference code.
  • FIG. 5 provides an example of the use of partials according to particular embodiments of the invention. Assume that several high-level product definitions can result in the generation of a row in a derived attribute table (a low-level configuration item). Each row represents the initial status of an equipment type associated with a service type.
  • a full configuration item definition (in this case, a derived attribute table) typically has to be generated for each status. Partials allow each status to be created as an incomplete part of a derived attribute definition 502, which are later combined to form a single complete definition 504 as illustrated in FIG. 5.
  • partials are stored in the configuration server 102 like any other configuration item.
  • Direct updates to partials may invoke the generation process 404 like , updates to other configuration items.
  • Partials are passed to the configuration- generators.
  • stylesheets do not match on the ⁇ partial> root element of all partial documents. Therefore, no high-level to low-level transformation is required. Instead, they are added to the update list, and are subsequently passed into the reconciliation process 416. In some embodiments, during reconciliation, partials are reconciled against the previously generated items in the configuration server 102, and then combined into full definitions. This reconciliation and merge process is further described below.
  • Predefined or generated Partials may either be generated during the normal transformation of high-level configuration to low-level configuration, or predefined at some stage prior to generation.
  • FIG. 5 illustrates an example of how partials may be combined to form a full configuration item definition that is output to the result document of the generation process.
  • partials 502 are still regarded as complete configuration item definitions but are only used internally in the generation process 404 and reconciler process 416.
  • a partial has its own XML representation.
  • the XML schema for a partial comprises a root ⁇ partiai> element that has an output attribute referencing another configuration item.
  • the output attribute is a mandatory attribute.
  • the item referenced is the item that the partial contributes to.
  • the contents of the ⁇ partiai> element comprises the same schema for the referenced item, except that there are no mandatory elements or attributes. For elements that appear more than once, an id attribute is used to identify the element uniquely. The actual value of the identifier is arbitrary, but must be consistent across all partials for-a given item.
  • a partial element may be predefined as a default value by using the default attribute.
  • the default attribute is set on a partial element, it is possible to have a duplicate partial with a different value and/or different attribute values.
  • duplicate elements and attributes must match in value, otherwise an exception is raised.
  • the entire element branch that is, all its children
  • Default values are typically used to ensure the successful creation of a complete item definition in situations where not all the required partial items are created during the imtial generation process. The handling of default element values during merge processing is further described below.
  • the Reconciler Process In some embodiments, the reconciler process 416 is the final phase of the generation process illustrated in FIG. 4.
  • the reconciler process 416 examines the existing low-level configuration items in the configuration server 102 and compares them with the newly generated low-level configuration items 418 output from the imtial generation process 404. The process identifies (and applies) any changes required to the master copy of the low-level items stored within the configuration server repository 104.
  • each generated low-level item records the high-level item from which it was generated, as a result, the set of existing low-level items used for the comparison may be derived based on the set of modified high-level items that were input into the initial generation process 404.
  • the comparison of each item may result in one of the following actions: • If the newly generated low-level configuration item already exists in the configuration server 102, it is used to update the existing item.
  • the reconciler process 416 also recognises and processes partial items.
  • merge processing 420 involves merging of XML node trees (including partials) to form a single node tree, then attempting to convert the result into a configuration item.
  • the merging may be accomplished as follows: • One of the partials is selected as the basis for the combined item. Each remaining partial being designated as merge items (including the master partial). • The first merge item candidate is selected and its top-level node is compared with the top-level node of the combined item. These nodes must match, otherwise a MergeExcep ion is raised. • If they match, each child node in the merge candidate is recursively compared against the nodes in the combined item. Matching elements are checked to ensure their values are the same. If the values are the same, they are ignored (that is, no changes are required). If the values differ, a MergeExcept ion is raised.
  • the id attribute is used to distinguish between each element. This mechanism allows matching elements to have different values,, without raising a MergeExcept ion, as long as their identifiers differ.
  • the element and all its extended children that is, the entire element branch
  • element attributes are also checked to ensure they contain the same values. If not, a MergeException is raised. Element attributes that exist only in the merge candidate are added to the appropriate element in the combined item. • After each merge candidate has been processed, the merge attempts to convert the combined item into a full item definition.
  • default element values may be handled by the merge process 420 as follows: • With no existing element, the entire element (including children) is merged into the merge document according to normal merge processing (described above). • With an existing element in the merge document, it is merged according to the following rules: • If the existing element is not a default element, and the new element is a default element, the new element will be ignored; that is, the existing element will be used.
  • partials may create a single low-level entity based on what is present in the configuration server 102 at the time of the reconciliation process 416.
  • a low-level item created by the partials is modified in an OSS component such as a billing component and a user does a commit that triggers the reconciliation process on those partials, the OSS component entity is overwritten. If information needs to be modified in an OSS component and retained, the master partial should be updated to include this new information. Doing this may ensure that the changes made in the OSS component are not overwritten the next time a partial is committed and reconciled.
  • Stylesheets As noted above, some embodiments of the invention use XML for high-level and low- level configurations.
  • XSL is the stylesheet language of XML. It allows for the transformation of XML documents into other formats, such as HTML, or into other XML documents.
  • a typical XSL consists of three parts: • XSLT, a language for transforming XML documents.
  • • XPath a language for addressing elements of an XML document.
  • • XSL Formatting Objects a vocabulary for formatting XML documents. Stylesheets are used as input to the configuration generator to transform high-level XML to low-level configuration XML. Separate sets of stylesheets may need to be developed for each new product or product group (for example, POTS products).
  • XML objects link to other external resources for information through a URI (Uniform Resource Identifier).
  • URI Uniform Resource Identifier
  • a URI is an extension of a URL (Uniform Resource Locator) that conceptually encompasses other identifier schemes such as ISBN book numbers and international telephone numbers. The URL scheme is still the most commonly used resource location.
  • confrep URI resolver A URI specified as a resource during the transformation process must be resolved to an XML source object.
  • the URI implementation used in some embodiments of the invention is called confrep, and represents the root of a configuration repository. Text appearing after "confrep:/" represents a location relative to the root of the repository.
  • references are typically in a human interpretable format.
  • namespace conflicts with other repositories can be avoided.
  • a URI can be specified as the value of a href attribute (locator attribute) as follows:
  • a URI can also be referenced by the XML document within a ⁇ xsl : import > element. Accessing other configuration items in some embodiments using stylesheets, the confrep URI allows references to other items in the Configuration Server.
  • an XSLT documentO function could use the following confrep URI: document ( "confrep: /ci/PEzyStarter. xml") This XSL example searches the Configuration Server for the XML file PE zystarter . xmi. It then builds an XML document (or node tree) from the retrieved file. The document can be assigned to a variable and any data required extracted from it, through the use of XPath expressions.
  • confrep : /ci/PEzyStarter. x l This example searches the Configuration Server for the XML file PEzystarter' . xmi. It is a reference only with no interrogation of the contents of the file. The transformer would then drill down into the contents of the file during the generation process.
  • the previous version of a configuration item can be retrieved from the Configuration Server by using a suffix of ?old in the confrep URI; for example: document("confrep:/cs/PEzyStarter.XML?old”) Exemplary high-level and low-level configurations are provided in Appendix A and
  • the update of a configuration item may require updates in multiple OSS components 108. Often, the order that the OSS components are updated may be important. For example, in the case of provisioning OSS components and billing OSS components, the provisioning system must first be updated in order to provision a product before the product is billed to a customer.
  • the configuration includes rules that may be used to specify an order for updates.
  • the update order to use is selected based on whether items match particular regular expressions.
  • the update order used is selected based on whether items mach particular XPath expressions.
  • the configuration item type e.g.
  • an XML type may be used in the configuration rules to determine update order.
  • the configuration rules cause the configuration server to examine the content of the configuration item to determine the update order.
  • a regular expression is provided for matching purposes.
  • Type specifies an item type
  • identifier specifies the item name using a regular expression.
  • an XPath pattern may also be used to specify the item name. In the example, if the item type is "AAAA and the item-name matches the regular expression "w*AA", then the order of update is the CB system followed by the CM system. For items having a type of BBBB or CCCC, the CM system is updated.

Landscapes

  • Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
  • Stored Programmes (AREA)
  • User Interface Of Digital Computer (AREA)
  • Digital Computer Display Output (AREA)
  • Machine Translation (AREA)

Abstract

L'invention concerne des systèmes et des procédés permettant de gérer des configurations de plusieurs composants de systèmes de support d'opérations (OSS). Le procédé consiste en premier lieu à recevoir une configuration de haut niveau qui comporte plusieurs éléments de configuration de haut niveau. La configuration de haut niveau est traduite en configuration de niveau inférieur qui comporte plusieurs éléments de configuration de niveau inférieur. La configuration de niveau inférieur est traduite en au moins une configuration propre au composant OSS et envoyée au composant OSS concerné.
EP04811475A 2003-11-26 2004-11-19 Systeme et procede de gestion de la configuration de composants de systemes de support d'operations Withdrawn EP1687731A2 (fr)

Applications Claiming Priority (7)

Application Number Priority Date Filing Date Title
US52533103P 2003-11-26 2003-11-26
US10/723,581 US20050114479A1 (en) 2003-11-26 2003-11-26 System and method for hierarchically representing configuration items
US10/723,243 US20050114851A1 (en) 2003-11-26 2003-11-26 System and method for configuring a graphical user interface based on data type
US10/723,246 US20050114642A1 (en) 2003-11-26 2003-11-26 System and method for managing OSS component configuration
US10/723,612 US20050114692A1 (en) 2003-11-26 2003-11-26 Systems, methods and software to configure and support a telecommunications system
US10/723,582 US20050114240A1 (en) 2003-11-26 2003-11-26 Bidirectional interfaces for configuring OSS components
PCT/US2004/038763 WO2005055561A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de gestion de la configuration de composants de systemes de support d'operations

Publications (1)

Publication Number Publication Date
EP1687731A2 true EP1687731A2 (fr) 2006-08-09

Family

ID=34658299

Family Applications (5)

Application Number Title Priority Date Filing Date
EP04811745A Withdrawn EP1706805A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de configuration d'une interface utilisateur graphique en fonction d'un type de donnees
EP04811538A Withdrawn EP1687925A2 (fr) 2003-11-26 2004-11-19 Systeme et procede pour representation hierarchique d'articles de configuration
EP04811768A Withdrawn EP1716493A2 (fr) 2003-11-26 2004-11-19 Interfaces bidirectionnelles permettant de configurer des composants de systemes de soutien a l'exploitation (oss)
EP04811659A Withdrawn EP1687691A2 (fr) 2003-11-26 2004-11-19 Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication
EP04811475A Withdrawn EP1687731A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de gestion de la configuration de composants de systemes de support d'operations

Family Applications Before (4)

Application Number Title Priority Date Filing Date
EP04811745A Withdrawn EP1706805A2 (fr) 2003-11-26 2004-11-19 Systeme et procede de configuration d'une interface utilisateur graphique en fonction d'un type de donnees
EP04811538A Withdrawn EP1687925A2 (fr) 2003-11-26 2004-11-19 Systeme et procede pour representation hierarchique d'articles de configuration
EP04811768A Withdrawn EP1716493A2 (fr) 2003-11-26 2004-11-19 Interfaces bidirectionnelles permettant de configurer des composants de systemes de soutien a l'exploitation (oss)
EP04811659A Withdrawn EP1687691A2 (fr) 2003-11-26 2004-11-19 Systemes, procedes et logiciel pour configurer et gerer un systeme de telecommunication

Country Status (2)

Country Link
EP (5) EP1706805A2 (fr)
WO (5) WO2005054988A2 (fr)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB9603582D0 (en) 1996-02-20 1996-04-17 Hewlett Packard Co Method of accessing service resource items that are for use in a telecommunications system
US7240068B2 (en) * 2002-09-06 2007-07-03 Truetel Communications, Inc. Service logic execution environment (SLEE) that is running on a device, supporting a plurality of services and that is compliant with a telecommunications computing standard for SLEES
US7803203B2 (en) * 2005-09-26 2010-09-28 Cabot Microelectronics Corporation Compositions and methods for CMP of semiconductor materials
US9122719B2 (en) * 2006-04-28 2015-09-01 Bmc Software, Inc. Database application federation
US8238538B2 (en) 2009-05-28 2012-08-07 Comcast Cable Communications, Llc Stateful home phone service
US8671036B2 (en) * 2009-11-06 2014-03-11 Microsoft Corporation User interface for defining account dimension combinations
US11436197B2 (en) * 2020-07-29 2022-09-06 Zixcorp Systems, Inc. Asynchronous method for provisioning a service using file distribution technology
US11611473B2 (en) 2014-01-14 2023-03-21 Zixcorp Systems, Inc. Provisioning a service using file distribution technology
US9531589B2 (en) 2014-05-30 2016-12-27 Cisco Technology, Inc. Automating monitoring using configuration event triggers in a network environment
CN113656347B (zh) * 2021-08-17 2023-12-05 成都统信软件技术有限公司 文件目录导出方法、文件目录导入方法及计算设备

Family Cites Families (18)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5175800A (en) * 1987-03-23 1992-12-29 Case Group Plc Expert and data base system and method for communications network
US5103421A (en) * 1988-11-29 1992-04-07 Massachusetts Institute Of Technology Process and apparatus for designing a system made of components
US5579384A (en) * 1995-02-17 1996-11-26 Bellsouth Corporation Telecommunications network service central management system interfacing with protocol specific regional stations providing services to subscribers
US5805602A (en) * 1995-09-25 1998-09-08 Bell Atlantic Network Services, Inc. Network monitoring system for cell delay variation
US6154738A (en) * 1998-03-27 2000-11-28 Call; Charles Gainor Methods and apparatus for disseminating product information via the internet using universal product codes
US6772396B1 (en) * 1999-10-07 2004-08-03 Microsoft Corporation Content distribution system for network environments
US6449624B1 (en) * 1999-10-18 2002-09-10 Fisher-Rosemount Systems, Inc. Version control and audit trail in a process control system
US7150037B2 (en) * 2001-03-21 2006-12-12 Intelliden, Inc. Network configuration manager
US6889172B2 (en) * 2001-08-15 2005-05-03 National Instruments Corporation Network-based system for configuring a measurement system using software programs generated based on a user specification
US20040205562A1 (en) * 2001-12-27 2004-10-14 G.E. Information Services, Inc. System and method for transforming documents to and from an XML format
US20030158919A1 (en) * 2002-02-20 2003-08-21 Sun Microsystems, Inc., A Delaware Corporation Method for deploying version control system server software having remote access capability
US7082460B2 (en) * 2002-04-19 2006-07-25 Axeda Corporation Configuring a network gateway
US20050089027A1 (en) * 2002-06-18 2005-04-28 Colton John R. Intelligent optical data switching system
US8073935B2 (en) * 2002-07-25 2011-12-06 Oracle America, Inc. Pluggable semantic verification and validation of configuration data
US7124145B2 (en) * 2003-03-27 2006-10-17 Millennium It (Usa) Inc. System and method for dynamic business logic rule integration
US7398307B2 (en) * 2003-04-30 2008-07-08 Hewlett-Packard Development Company, L.P. Method and system for managing a network
US7444376B2 (en) * 2003-05-22 2008-10-28 Hewlett-Packard Development Company, L.P. Techniques for creating an activation solution for providing commercial network services
US20050091346A1 (en) * 2003-10-23 2005-04-28 Brijesh Krishnaswami Settings management infrastructure

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO2005055561A3 *

Also Published As

Publication number Publication date
WO2005055561A3 (fr) 2006-03-09
WO2005054989A2 (fr) 2005-06-16
EP1687691A2 (fr) 2006-08-09
EP1716493A2 (fr) 2006-11-02
EP1687925A2 (fr) 2006-08-09
WO2005054987A2 (fr) 2005-06-16
WO2005054988A3 (fr) 2007-06-07
WO2005054989A3 (fr) 2006-05-11
WO2005055561A2 (fr) 2005-06-16
EP1706805A2 (fr) 2006-10-04
WO2005055491A3 (fr) 2006-12-07
WO2005054988A2 (fr) 2005-06-16
WO2005055491A2 (fr) 2005-06-16
WO2005054987A3 (fr) 2007-07-19

Similar Documents

Publication Publication Date Title
US10324690B2 (en) Automated enterprise software development
CA2576478C (fr) Systeme, methode et dispositif permettant d'utiliser des outils uml definissant des applications d'elements liees au service web
US7599947B1 (en) Method and system for converting hierarchical database schemas into relational database schemas
CA2249386C (fr) Systeme et procede informatiques servant a representer des descriptions de systemes logiciels et a generer des programmes informatiques executables et des configurations de systemes a partir de ces descriptions
KR101117945B1 (ko) 분산형 컴퓨팅 시스템을 위한 아키텍쳐 및 분산형 애플리케이션의 자동화된 설계, 배치 및 관리
US6018627A (en) Tool-independent system for application building in an object oriented development environment with data stored in repository in OMG compliant UML representation
US9804837B2 (en) System and method for creating, managing, and reusing schema type definitions in services oriented architecture services, grouped in the form of libraries
US20080189679A1 (en) Method and system for creating, deploying, and utilizing a service
US20110125804A1 (en) Modular distributed mobile data applications
US7739691B2 (en) Framework for declarative expression of data processing
WO1997035254A9 (fr) Systeme et procede informatiques servant a representer des descriptions de systemes logiciels et a generer des programmes informatiques executables et des configurations de systemes a partir de ces descriptions
US20100185701A1 (en) Method and system for enabling life cycle maintenance of hierarchical database schemas in modeling tool
US7191404B2 (en) System and method for mapping management objects to console neutral user interface
US20050114692A1 (en) Systems, methods and software to configure and support a telecommunications system
EP1687731A2 (fr) Systeme et procede de gestion de la configuration de composants de systemes de support d'operations
WO2002046909A1 (fr) Exploitation et mise a niveau automatique d'une application utilisant une definition d'application de langage de balisage
US20050114240A1 (en) Bidirectional interfaces for configuring OSS components
US20050114642A1 (en) System and method for managing OSS component configuration
EP1684170A2 (fr) Système et méthode de développement de logiciel
Le Zou et al. On synchronizing with web service evolution
Selly et al. Expert ASP. NET 2.0: Advanced Application Design
Ferreira Data Adapters
Krause et al. Data Access
Guide Red Hat Web Application Framework 6.0
Hasegawa Oracle Fusion Middleware Migration Guide for Oracle Application Integration Architecture, 11g Release 1 (11.1. 1.4. 0) E17361-02

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20060526

AK Designated contracting states

Kind code of ref document: A2

Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LU MC NL PL PT RO SE SI SK TR

AX Request for extension of the european patent

Extension state: AL HR LT LV MK YU

DAX Request for extension of the european patent (deleted)
STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION HAS BEEN WITHDRAWN

18W Application withdrawn

Effective date: 20080423