Software configuration of module dependent on history

• US 10,013,535 B2
• Filed: 11/21/2003
• Issued: 07/03/2018
• Est. Priority Date: 11/21/2003
• Status: Active Grant

• Current Assignee: Ciena Corporation
• Original Assignee: Ciena Corporation
• Inventors: Thomas, Andrew James, Skrebels, Mark, Irvine, Stewart
• Primary Examiner(s): Hayes, John W
• Assistant Examiner(s): Winter, John M
• Application Number:
  US10/719,867
• Publication Number:
  US 20050114234A1
• Time in Patent Office: 5,338 Days
• Field of Search: None
• CPC Class Codes: G06F 21/109 by using specially-adapted hardware at the client
• CPC Class Codes: G06F 2221/2137 Time limited access, e.g. to a computer or data
• CPC Class Codes: G06Q 10/087 Inventory or stock management, e.g. order filling, procurement or balancing against orders
• CPC Class Codes: H04L 2463/101 applying security measures for digital rights management data processing systems or methods, specially adapted for commerce, e.g. marketing, shopping, billing, auctions or e-commerce G06Q30/00

Abstract

A program controller is arranged to automatically authorize or configure or upgrade a program for a customer replaceable card of a system, the controller being arranged to manage the program automatically, according to a licence agreement, and according to a stored history of use of the hardware module. A supplier can track customer changes and enforce more easily different conditions for authorizing the program on, different modules from different sources, having different levels of capability. There can be less interaction with the supplier to get specific authorizations. The history can be stored on the module. It can be used to ease inventory tracking and generate billing information.

Claims

1. A modular system forming a network element in a telecommunications system, the modular system comprising:

one or more hardware modules which are customer replaceable each comprising a processor and associated memory for running software, each of the one or more hardware modules carry out functions for a telecommunications network;

a backplane, wherein the one or more hardware modules are configured to plug into the backplane; and

a processor running a program controller for the modular system;

wherein the processor in the one or more hardware modules is configured to execute a program when each is plugged into the backplane and the program is separately executed from the program controller, and wherein the associated memory in the one or more hardware modules contains a history of use of the associated hardware module including a list of backplanes that have used the associated hardware module and license information indicative of authorization to use the associated hardware module; and

wherein the program controller is configured to automatically manage each of the associated hardware modules in conjunction with the program executed on the processor and the associated memory in the associated hardware modules to determine whether the license information indicates authorization for the associated hardware module to be used with a particular backplane and control use of the software associated with the associated hardware module and use of the associated hardware module with the modular system, according to the license information.

2. The modular system of claim 1, wherein at least part of the history of use is obtained from the associated hardware module.

3. The modular system of claim 1, wherein the program controller is part of a shelf controller for managing modules in the form of cards for carrying out functions of the network element for the telecommunications network, wherein the shelf controller is configured to control and monitor traffic between the plurality of hardware modules plugged into the backplane.

4. The modular system of claim 1, wherein the program controller is configured to determine an identity of the modular system and determine whether the program is authorized for use with that modular system.

5. The modular system of claim 1, wherein the history of use comprises a program identifier of a program previously loaded on the associated hardware module.

6. The modular system of claim 1, wherein the history of use comprises a license identifier of a program previously loaded on the associated hardware module.

7. The modular system of claim 1, wherein the program controller is located remoted from the backplane and is coupled to the backplane by a communications link.

8. The modular system of claim 1, wherein the program controller maintains an inventory record of identities and relationships of modules, programs, and license information for a given customer.

9. The modular system of claim 1, wherein the program controller copies at least a part of the program to the hardware module at initialization.

10. The modular system of claim 1, wherein the program controller authorizes at least a part of the program for the hardware module at initialization.

11. The modular system of claim 1, wherein the program has license information indicating a capability licensed, and wherein the program controller configures the program according to the capability licensed.

12. The modular system of claim 1, wherein the program has license information indicating license expiry information.

13. The modular system of claim 1, wherein the program controller is executed on a shelf controller of the modular system, the shelf controller stores or generates a copy of the program for downloading to the associated hardware module when plugged into the backplane.

14. The modular system of claim 1, wherein the license information indicates licenses for the associated hardware module, software in the modular system, and the backplane, and performs configuration based on a combination of the licenses.

15. The modular system of claim 1, wherein the software is distributed from an element management system to the program controller to the hardware module, based on the license information.

16. The modular system of claim 1, wherein the program controller is configured to checking a configuration of the associated hardware module when it is plugged into the backplane.

17. The modular system of claim 1, wherein the history of use of the associated hardware module is only stored on the associated hardware module, and accessed by the program controller whenever the associated hardware module is plugged into the backplane or any other backplane.

18. The modular system of claim 1, wherein the program controller is configured to maintain a history of all of the plurality of hardware modules that have plugged into the backplane.

19. The modular system of claim 1, wherein the program controller is configured to use the history of use to enforce consistency between a version of the program and a module type or version of the associated hardware module.

20. A modular network element system in a telecommunications system, comprising:

one or more hardware modules;

a backplane wherein the one or more hardware modules are configured to plug into a backplane of the modular network element system, each of the one or more hardware modules carry out functions for a telecommunications network, each hardware module having a processor and memory storing

a history of use of the hardware module, the stored history including a list of backplanes that have used the hardware module; and

license information indicative of authorization to use the hardware modules; and

a processor running a program controller for the network element system, wherein the program controller is either part of the modular network element system or in communication therewith, wherein the program controller is configured to

manage a program stored on and executed on the processor of at least one of the one or more hardware modules of the modular network element system automatically when plugged into the backplane and the program is executed separately from the program controller, the hardware module being a customer-replaceable part, the program controller being arranged to manage the hardware module in conjunction with the program to automatically determine whether the license information indicates authorization for the hardware module to be used with a particular backplane and to control use of software associated with the hardware module and use of the hardware module with the modular network element system according to the license information.

21. The modular network element system of claim 20, further comprising:

an interface for coupling the modular network element system to a remote server to pass information for a supplier to maintain an inventory of programs and modules associated with the modular network element system.

22. A method implemented in a modular system comprising one or more hardware modules which are customer replaceable each comprising a processor and associated memory for running software;

a backplane, wherein the one or more hardware modules are configured to plug into the backplane; and

a processor running a program controller for the modular system, each of the one or more hardware modules carry out functions for a telecommunications network, the method comprising;

executing a program by the processor in the one or more hardware modules when each is plugged into the backplane and the program is separately executed from the program controller, wherein the associated memory in the one or more hardware modules contains a history of use of the associated hardware module including a list of backplanes that have used the associated hardware module and license information indicative of authorization to use the associated hardware module; and

automatically managing, by the program controller, each of the associated hardware modules in conjunction with the program executed on the processor and the associated memory in the associated hardware modules to determine whether the license information indicates authorization for the associated hardware module to be used with a particular backplane and controlling use of the software associated with the associated hardware module and use of the associated hardware module with the modular system, according to the license information.

23. A method for a modular system forming a network element in a telecommunications system, the method comprising:

providing one or more hardware modules which are customer replaceable each comprising a processor and associated memory for running software, each of the one or more hardware modules carry out functions for a telecommunications network;

providing a backplane, wherein the one or more hardware modules are configured to plug into the backplane; and

providing a processor running a program controller for the modular system;

wherein the processor in the one or more hardware modules is configured to execute a program when each is plugged into the backplane and the program is separately executed from the program controller, and wherein the associated memory in the one or more hardware modules contains a history of use of the associated hardware module including a list of backplanes that have used the associated hardware module and license information indicative of authorization to use the associated hardware module; and

wherein the program controller is configured to automatically manage each of the associated hardware modules in conjunction with the program executed on the processor and the associated memory in the associated hardware modules to determine whether the license information indicates authorization for the associated hardware module to be used with a particular backplane and control use of the software associated with the associated hardware module and use of the associated hardware module with the modular system, according to the license information.

24. A system, comprising:

a plurality of network elements each comprising;

one or more hardware modules which are customer replaceable each comprising a processor and associated memory for running software, each of the one or more hardware modules carry out functions for a telecommunications network;

a backplane, wherein the one or more hardware modules are configured to plug into the backplane; and

a processor running a program controller for the associated network element;

wherein the processor in the one or more hardware modules is configured to execute a program when each is plugged into the backplane and the program is separately executed from the program controller, and wherein the associated memory in the one or more hardware modules contains a history of use of the associated hardware module including a list of backplanes that have used the associated hardware module and license information indicative of authorization to use the associated hardware module; and

wherein the program controller is configured to automatically manage each of the associated hardware modules in conjunction with the program executed on the processor and the associated memory in the associated hardware modules to determine whether the license information indicates authorization for the associated hardware module to be used with a particular backplane and control use of the software associated with the associated hardware module and use of the associated hardware module with the associated network element, according to the license information; and

a central system communicatively coupled to the plurality of network elements for a supplier to maintain an inventory of programs and modules associated with each of the plurality of network elements.