This invention relates to methods for configuring network elements in a broadband network.
From time to time, it is necessary to make changes to the network by adding or reconfiguring elements making up the system, for example the routers 14. This configuration is achieved by downloading the configuration data from the control and provisioning system 20 to the router 14. The configuration data is contained in templates that are stored in a database forming part of the control and provisioning system 20. However, problems can arise due to the large number of network elements in use and their ever changing nature. If a new router (or, more likely, a revised version of an existing router) is deployed into the network and there is no configuration template that matches it exactly, the configuration can fail. Reconfiguration in such cases often requires manual intervention with the associated cost and delay.
In many cases, the reason for failure can be that certain parameters relating to a router vary without making substantial changes to functionality. For example, the name may change to indicate a new version. If the configuration template specifies the old name, it may not operate properly to configure the latest version even though it is functionally identical since the parameters on the router will not match the values in the template.
It is an object of the invention to provide a system which does not require discrete templates to be stored in the control and provisioning system for all network elements but which can create configuration statements according to data that can be retrieved from the system.
This invention provides a method of configuring network elements in a system comprising network elements and a network provisioning and control system by which connection of network elements to a broadband network is controlled, the network provisioning and control system including a configuration rendering engine that operates to configure the network elements connected to the network, the method comprising:
The conditional configuration data can be static data such as data relating to the particular type of network equipment (name, model, version, etc.), the type of connection (DSL, optical fibre, etc.), connection port, end user equipment etc. The conditional data can also be temporal, indicative of a time varying parameter, such as a time-limited connection, current port status, etc.
The method can also comprise capturing data relating to the system during operation and using the system operation data to determine discrete values for the conditional configuration data.
Data relating to the status of the interface or port to which an element is attached can be used to provide configuration data, including aspects such as signal to noise ratio, latency, etc.
The method according to the invention avoids the need to have discrete templates for every type of network element. This reduces the possibility of there being no template available when a device is to be configured.
A network system in which the invention operates is shown in
For the function of the control and provisioning system 20, the network can be considered in an abstract way as comprising a core 22 having one or more cells 24, each cell having one or more network elements 26 as is shown in
The invention primarily forms part of the configuration rendering engine 36. The relevant part of the system shown in
The following example considers connection of a new router 40 to the call 24. On connection and powering up of the new network element 40, the element manager 38 detects the presence of the new hardware and invokes operation of the configuration rendering engine(CRE) 36. The CRE 36 includes an embodiment of the invention known as configuration pre-processor language (CPL) 42. The CRE 36 sends a message x to the element 40 to return various data y. On receipt of this data, the CRE 40/CPL 42 interrogates a configuration template database 44 to obtain an appropriate configuration template 46. The templates 46 contain predetermined configuration data (i.e. data that are fixed for the device in question) and conditional configuration data (i.e. data that are dependent on returned values following interrogation of the system).
The predetermined configuration data can be the same as are used in prior art configuration templates. The conditional configuration data can be static and/or temporal data. Examples of static conditional configuration data can be data such as the name, model or version of the network element 40, the link speed to be assigned, etc. These are data that will not change for any configuration of the element 40. Temporal configuration data are dynamic data that can vary during the operation of the element 40. these can include parameters that must be determined at the time of configuration, such as the nature of end user equipment (not shown) attached to the router 40, data relating to the interface/ports status such as signal to noise ratio, latency. Other types of temporal or dynamic data include time, for use in establishing time-limited configurations or the like.
The configuration template is populated with data to create a configuration statement that is sent from the CRE 36 via the element manager 38, to the element 40.
In a further embodiment of the invention, a data capture engine (DCE) 48 is included in the system 20. This operates to receive data from the various parts of the system during operation. Thus it can provided statistical data which can also be used for creation of the configuration statement.
By using conditional data in the preparation of the configuration statement, it is possible for the system to adapt to changes in the configuration parameters of the network element without the need for a new template to be created. It also allows time-limited data or configurations to be used.
While the invention is described above in relation to connection of a new network element, it can equally be applied to re-configuration of an existing element, such as following a restart, or on commencement of new system capabilities.
Number | Date | Country | Kind |
---|---|---|---|
07104707.0 | Mar 2007 | EP | regional |
Filing Document | Filing Date | Country | Kind | 371c Date |
---|---|---|---|---|
PCT/EP2008/053374 | 3/20/2008 | WO | 00 | 3/4/2010 |