Consistency checking mechanism for configuration parameters in embedded systems

• US 6,877,051 B2
• Filed: 06/12/2001
• Issued: 04/05/2005
• Est. Priority Date: 06/12/2001
• Status: Expired due to Fees

• Current Assignee: Intel Corporation
• Original Assignee: Intel Corporation
• Inventors: Perycz, Krzysztof S., Kaminski, Adam, Przekop, Zbigniew, Iwanojko, Bohdan T.
• Primary Examiner(s): Dang, Khanh
• Application Number:
  US09/878,431
• Publication Number:
  US 20020188778A1
• Time in Patent Office: 1,393 Days
• Field of Search: 710/100, 710/104, 710/105, 709/203, 709/208, 709/217, 709/218, 709/219, 709/230, 706/45, 707/10
• US Class Current: 710/100
• CPC Class Codes: G06F 9/44505 Configuring for program initiating, e.g. using registry, configuration files
• CPC Class Codes: H04L 41/0846 based on copy from other elements
• CPC Class Codes: H04L 41/0856 by backing up or archiving configuration information
• CPC Class Codes: H04L 41/0863 by rolling back to previous configuration versions
• CPC Class Codes: H04L 41/0869 Validating the configuration within one network element

Abstract

An arrangement is provided for consistent parameter configuration in an embedded system. A consistent parameter configuration mechanism comprises a management client and a configuration manager. When the management client receives a set of configuration requests, it notifies the configuration manager to start a transaction, during which the configuration manager requests relevant embedded modules to perform parameter configurations according to the configuration requests, to manage hard coded dependencies, and to enforce registered dependencies. Any detected inconsistency during parameter configuration causes the consistent parameter configuration mechanism to undo the parameter configuration.

Claims

1. A system comprising:

at least one embedded module in an embedded system; and

a consistent parameter configuration mechanism in said embedded system, said consistent parameter configuration mechanism communicating with said at least one embedded module to manage configuration parameters in a consistent fashion,

wherein configuration parameters are configurable parameters associated with at least one embedded module,

wherein said consistent parameter configuration mechanism comprises;

a configuration database to store a set of configuration parameters of said embedded system, said set of configuration parameters having run-time counterpart variables in said at least one embedded module, said configuration database additionally to determine the behavior of said at least one embedded module and said embedded system, and

a consistency assurance mechanism to ensure that said set of configuration parameters stored in said configuration database is consistent,

wherein said consistent parameter configuration mechanism maintains configuration parameter dependency relationships associated with said at least one embedded module,

wherein said consistency assurance mechanism comprises;

a management client to receive a set of configuration requests to configure at least one configuration parameter from said set of configuration parameters and to manage the execution of said set of configuration requests, and

a configuration manager to manage the consistent configuration of said at least one configuration parameter according to said Set of configuration requests, said configuration manager communicating with both said management client and said at least one embedded module to execute said set of configuration requests in a consistent fashion, and

wherein said configuration manager comprises;

a temporary configuration database to store at least some of said configuration parameters that are set by said at least one embedded module according to said configuration requests;

a validation mechanism to perform consistency checking; and

a relay mechanism to coordinate execution of parameter configuration based on said configuration requests, validation of configuration consistency, undo operation when a configuration is found not consistent, and commitment to a consistent configuration after a validation of a consistent configuration.

2. The system according to claim 1, wherein said validation mechanism further comprises a parameter change signaling mechanism to notify an embedded module about a change in a configuration parameter according to a dependency relationship.

3. The system according to claim 1, said consistent parameter configuration mechanism further comprising:

a module registration mechanism to register said at least one embedded module;

a module database to record the modules that are registered through said module registration mechanism;

a dependency registration mechanism to register dependency relationships; and

a dependency database to store said dependency relationships registered through the dependency registration mechanism.

4. A method for consistent parameter configuration, comprising:

receiving, by a management client, a set of configuration requests, said set of configuration requests corresponding to a transaction;

creating, by a configuration manager, a temporary configuration database after said management client notifies the configuration manager the start of the transaction;

requesting an appropriate embedded module to perform a parameter configuration according to one of the configuration requests;

performing, by said appropriate embedded module, said parameter configuration, the appropriate module changing the value of a first parameter in said temporary configuration database and generating a first status code;

returning said first status code to the configuration manager,

undoing said parameter configuration if the first status code indicates an error;

recording said one of the configuration requests as an outstanding request if the first status code indicates that there is a hard coded dependency associated with the parameter configuration and defined based on said first parameter; and

enforcing, if the first status code is not an error, a registered dependency that is identified to associate with the parameter configuration and defined based on said first parameter.

5. The method according to claim 4, wherein said enforcing comprises:

identifying a dependent embedded module which contains a second parameter that depends on said first parameter according to said registered dependency; and

notifying said dependent embedded module to verify whether said first parameter remains consistent with the said second parameter and to optionally configure the second parameter.

6. The method according to claim 4, further comprising:

examining, by said configuration manager, configuration consistency at the end of said transaction to generate a second status code; and

finishing said transaction according to said second status code.

7. The method according to claim 4, further comprising:

registering, by a module registration mechanism prior to said receiving, said at least one embedded module; and

recording the at least one embedded module, registered through said registering, in a module database.

8. The method according to claim 5, further comprising:

registering, by a dependency registration mechanism prior to the receiving, a dependency relationship that is used in said examining to determine the consistency; and

storing the dependency relationship as a registered dependency relationship in a dependency database.

9. The method according to claim 8, wherein said registering includes:

specifying an independent parameter associated with an independent embedded module, said independent parameter being configurable in said independent embedded module, said independent embedded module being one of the at least one embedded module; and

specifying a dependent parameter associated with a dependent embedded module, said dependent parameter being configurable in said dependent embedded module, said independent embedded module being one of the at least one embedded module, the independent embedded module and the dependent embedded module forming said registered dependency that triggers a parameter configuration to be performed on the dependent parameter whenever there is a change made to the independent parameter.

10. The method according to claim 6, wherein said examining comprises:

determining, by said configuration manager, whether there is an outstanding request recorded by said recording;

sending said second status code indicating a consistent configuration if no outstanding request is recorded;

requesting an embedded module to perform a second parameter configuration based on said outstanding request that defines the embedded module and the parameter to be configured through said parameter configuration;

receiving a third status code specifying the status of the second parameter configuration;

determining whether the number of outstanding request is reduced; and

sending said second status code indicating an inconsistent configuration if the number of outstanding request is not reduced.

11. The method according to claim 6, wherein said finishing comprises:

determining whether said second status code indicates an inconsistent configuration;

undoing said transaction if said second status code indicates an inconsistent configuration; and

committing said transaction if said second status code indicates a consistent configuration.

12. The method according to claim 11, wherein said undoing comprises

sending a first command from said management client to said configuration manager;

deleting, by said configuration manager, said temporary configuration database based on said first command.

13. The method according to claim 11, wherein said committing comprises:

sending a second command from said management client to said configuration manager;

copying the content from said temporary configuration database to a configuration database based on said second command;

introducing changes to run-time variables based on the configuration database, and

deleting said temporary configuration database after said copying.

14. A computer-readable medium encoded with a program for consistent parameter configuration, said program comprising:

receiving, by a management client, a set of configuration requests, said set of configuration requests corresponding to a transaction;

creating, by a configuration manager, a temporary configuration database after said management client notifies the configuration manager the start of the transaction;

requesting an appropriate embedded module to perform a parameter configuration according to one of the configuration requests;

performing, by said appropriate embedded module, said parameter, said appropriate module changing the value of a first parameter in said temporary configuration database and generating a first status code;

returning said first status code to the configuration manager,

undoing said parameter configuration if the first status code indicates an error;

recording said one of the configuration requests as an outstanding request if the first status code indicates that there is a hard coded dependency associated with the parameter configuration and defined based on said first parameter; and

enforcing, if the first status code is not an error, a registered dependency that is identified to associate with the parameter configuration and defined based on said first parameter.

15. The medium according to claim 14, wherein said enforcing comprises:

identifying a dependent embedded module which contains a second parameter that depends on said first parameter according to said registered dependency; and

notifying said dependent embedded module to configure the second parameter.

16. The medium according to claim 14, said program further comprising:

examining, by said configuration manager, configuration consistency at the end of said transaction to generate a second status code; and

finishing said transaction according to said second status code.

17. The medium according to claim 14, said program further comprising:

registering, by a module registration mechanism prior to said receiving, said at least one embedded module; and

recording the at least one embedded module, registered through said registering, in a module database.

18. The medium according to claim 15, said program further comprising:

registering, by a dependency registration mechanism prior to the receiving, a dependency relationship that is used in said examining to determine the consistency; and

storing the dependency relationship as a registered dependency relationship in a dependency database.

19. The medium according to claim 18, wherein said registering includes:

specifying an independent parameter associated with an independent embedded module, said independent parameter being configurable in said independent embedded module, said independent embedded module being one of the at least one embedded module; and

specifying a dependent parameter associated with a dependent embedded module, said dependent parameter being configurable in said dependent embedded module, said independent embedded module being one of the at least one embedded module, the independent embedded module and the dependent embedded module forming said registered dependency that triggers a parameter configuration to be performed on the dependent parameter whenever there is a change made to the independent parameter.

20. The medium according to claim 16, wherein said examining comprises:

determining, by said configuration manager, whether there is an outstanding request recorded by said recording;

sending said second status code indicating a consistent configuration if no outstanding request is recorded;

requesting an embedded module to perform a second parameter configuration based on said outstanding request that defines the embedded module and the parameter to be configured through said parameter configuration;

receiving a third status code specifying the status of the second parameter configuration;

determining whether the number of outstanding request is reduced; and

sending said second status code indicating an inconsistent configuration if the number of outstanding request is not reduced.

21. The medium according to claim 16, wherein said finishing comprises:

determining whether said second status code indicates an inconsistent configuration;

undoing said transaction if said second status code indicates an inconsistent configuration; and

committing said transaction if said second status code indicates a consistent configuration.

22. The medium according to claim 21, wherein said undoing comprises

sending a first command from said management client to said configuration manager;

deleting, by said configuration manager, said temporary configuration database based on said first command.

23. The medium according to claim 21, wherein said committing comprises:

sending a second command from said management client to said configuration manager;

copying the content from said temporary configuration database to a configuration database based on said second command;

introducing changes to run-time variables based on the configuration database, and

deleting said temporary configuration database after said copying.