Method and system for providing efficient object-based network management

• US 7,793,301 B2
• Filed: 11/18/2005
• Issued: 09/07/2010
• Est. Priority Date: 11/18/2005
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Hall, Michael D., Gattu, BalaSubrahmanyam, Bhat, Kong-Posh
• Primary Examiner(s): Cao; Diem K
• Application Number:
  US11/282,326
• Publication Number:
  US 20070150563A1
• Time in Patent Office: 1,754 Days
• Field of Search: 719/315, 719/318, 709/223
• US Class Current: 719/313
• CPC Class Codes: H04L 12/66 Arrangements for connecting between networks having differing types of switching systems, e.g. gateways

Abstract

A method for providing efficient object-based network management is provided. The method includes receiving a request for a reference to an object that represents at least one managed network element. A determination is made regarding whether the object is currently activated. The object is activated based on the request for a reference to the object when the object is not currently activated.

Claims

1. A method for providing efficient object-based network management, comprising:

receiving a reference request from a collaborating object for a reference to an object, the object representing one of a number of managed network elements that are managed by a plurality of collaborating objects, the collaborating object being one of the plurality of collaborating objects, and each of the plurality of collaborating objects corresponding to one of a number of applications;

determining whether the object is currently activated in a management platform;

activating the object based on the reference request for the reference to the object when the object is not currently activated;

providing the reference to the object to the collaborating object;

receiving a release request from the collaborating object;

providing a release confirmation to the collaborating object in response to the release request from the collaborating object, the release confirmation comprising setting the reference to the object to a stale value for the collaborating object; and

managing a count of references to the object.

2. The method as set forth in claim 1, wherein activating the object comprises:

creating an instance of the object in a memory of the management platform, wherein the instance of the object is a copy of a corresponding original object stored in a repository;

adding an entry including the reference to the object and a handle for the object to a mapping table, wherein the reference to the object is a reference to the instance of the object.

3. The method as set forth in claim 2, further comprising:

incrementing the count of references to the object in response to receiving the reference request for the object, when the object is activated; and

retrieving the reference to the object when the object is currently activated.

4. The method as set forth in claim 1, further comprising releasing the object in response to receiving a release request from the collaborating object, wherein releasing the object comprises:

decrementing the count of references to the object.

5. The method as set forth in claim 1, further comprising deactivating the object when the count of references to the object drops below a threshold, wherein deactivating includes:

copying a content of an instance of the object over a corresponding original object stored in a repository;

deleting the instance of the object from a memory in the management platform; and

removing an entry, including the reference to the object and a handle for the object, from a mapping.

6. The method as set forth in claim 1, wherein the at least one managed network element associated with the object is managed at least partially by the collaborating object invoking one or more of the functions of the object.

7. A method for providing efficient object-based network management, comprising:

providing a reference to an object to a collaborating object in response to a reference request from the collaborating object;

detecting a deactivation event for the object in a management platform;

identifying a type of the deactivation event, the type being one of a timer expiration and a request from the collaborating object to release the object, the object representing one of a number of managed network elements that are managed by a plurality of collaborating objects, the collaborating object being one of the plurality of collaborating objects, and each of the plurality of collaborating objects corresponding to one of a number of applications; and

in response to identifying the request from the collaborating object to release the object, providing a release confirmation to the collaborating object upon releasing the object, the release confirmation comprising setting the reference to the object to a stale value for the collaborating object;

based on the deactivation event, determining whether to deactivate the object; and

managing a count of references to the object.

8. The method as set forth in claim 7, further comprising deactivating the object after determining to deactivate the object, wherein deactivating the object comprises:

copying a content of an instance of the object over a corresponding original object stored in a repository;

deleting the instance of the object from a memory in the management platform; and

removing a table entry that corresponds to the object from a mapping table.

9. The method as set forth in claim 8, wherein determining whether to deactivate the object is based on the count of references to the object when the request to release the object is identified.

10. The method as set forth in claim 7, further comprising:

decrementing the count of references to the object in response to identifying the request to release the object.

11. The method as set forth in claim 10, further comprising determining to deactivate the object when the decremented count of references to the object drops below a threshold.

12. The method as set forth in claim 7, wherein the timer expiration is a notification that an access timer for the object has expired.

13. The method as set forth in claim 12, further comprising:

setting the reference for the object to the stale value for every collaborating object that has a valid resource reference for the object; and

deactivating the object.

14. The method as set forth in claim 12, the access timer operable to expire after a period of time equal to a predetermined multiple of a maximum length for a typical transaction for the object.

15. A management platform, comprising:

a first memory operable to store a plurality of objects; and

a controller configured to;

create an instance of an object in the first memory based on receiving a reference request for the object from a collaborating object, the object representing one of a number of managed network elements that are managed by a plurality of collaborating objects, the collaborating object being one of the plurality of collaborating objects, and each of the plurality of collaborating objects corresponding to one of a number of applications,

provide a reference to the created object to the collaborating object, and

release the object based on receiving a release request for the object from the collaborating object by providing a release confirmation to the collaborating object, the release confirmation comprising setting the reference to the object to a stale value for the collaborating object.

16. The management platform as set forth in claim 15, the controller further configured to create the instance of the object in the first memory based on receiving the reference request when the object is not stored in the first memory.

17. The management platform as set forth in claim 16, the controller further configured to store a handle for the object when the instance of the object is created in the first memory and to determine whether the object is stored in the first memory based on the handle.

18. The management platform as set forth in claim 17, wherein the instance of the object is created by copying a portion of the content of a second memory as a data component of the object and storing the object in the first memory.

19. The management platform as set forth in claim 15, the controller further configured to delete the object from the first memory based on a deactivation event.

20. The management platform as set forth in claim 19, the deactivation event comprising one of receiving a request to release the object and receiving a notification that an access timer for the object has expired.

21. The management platform as set forth in claim 19, the controller further configured to:

increment a count of references to the object in response to receiving the reference request for the object;

decrement the count of references to the object in response to receiving the release request for the object; and

determining the deactivation event when the count of references is below a predetermined value.