Method and system for modeling options for opaque management data for a user and/or an owner

• US 8,359,636 B2
• Filed: 05/09/2008
• Issued: 01/22/2013
• Est. Priority Date: 05/10/2007
• Status: Expired due to Fees

• Current Assignee: Avago Technologies General IP PTE Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Rajagopal, Murali, Shah, Hemal
• Primary Examiner(s): Flynn, Nathan
• Assistant Examiner(s): Vaughan, Michael R
• Application Number:
  US12/118,179
• Publication Number:
  US 20080282328A1
• Time in Patent Office: 1,719 Days
• Field of Search: None
• US Class Current: 726/4
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/102 Entity profiles

Abstract

Distributed Management Task Force (DMTF) management profiles, based on the Common Information Model (CIM) protocol, may be utilized to perform access authentication during opaque management data profile operations based on DMTF/CIM Role Based Authorization (RBA) profile and/or Simple Identity Management (SIM) profiles. Instances of CIM_Identity class may be utilized to enable validation of ownership and/or access rights, via instances of CIM_Role class and/or instances of CIM_Privilege class for a plurality of common users and/or applications. Quota related operations may be performed via “QuotaAffectsElement” associations between instances of CIM_Identity class and instances of the CIM_OpaqueManagementDataService class. The “QuotaAffectsElement” association may comprise “AllocationQuota” and/or “AllocatedBytes” properties to enable tracking and/or validating of quota related information within the opaque management data profile.

Claims

1. A method for network management, the method comprising:

in a network device managed via Distributed Management Task Force (DMTF) protocols;

receiving a request during opaque management data operations, wherein said request is handled in said network device using one or more instances of Common Information Model (CIM) based CIM_OpaqueManagementData class representing one or more corresponding storage components in said network device; and

authenticating operations performed during said handling of said request using Common Information Model (CIM) data model access profiles by utilizing one or more instances of at least one of CIM_Role and CIM_Privilege, via one or more instances of CIM_Identity class.

2. The method according to claim 1, comprising validating access related information via said Common Information Model (CIM) data model access profiles during said opaque management data operations, wherein said access related information comprise one or more of ownership, access rights, and quota information.

3. The method according to claim 2, wherein said CIM data model access profiles comprise one or more of Role Based Authorization (RBA) and Simple Identity Management (SIM) based profiles.

4. The method according to claim 3, comprising utilizing said one or more instances of said CIM_Identity class while utilizing RBA/SIM based profiles to perform said validation of said access related information.

5. The method according to claim 4, comprising utilizing a plurality of CIM_Account class to represent a plurality of common users sharing a common instance of said CIM_Identity class.

6. The method according to claim 4, comprising utilizing a plurality of instances of CIM_UserEntity class to represent a plurality of common applications sharing a common instance of said CIM_Identity class.

7. The method according to claim 4, comprising associating said one or more instances of CIM_OpaqueManagementData class with corresponding instances of said CIM_Identity class via OpaqueManagementDataUserElement associations to enable performing said validation of said access related information.

8. The method according to claim 7, wherein each of said OpaqueManagementDataUserElement associations comprises at least one of ownership, access right properties, and information to enable performing said validation of said access permission related information.

9. The method according to claim 4, comprising associating instances of a CIM_OpaqueManagementDataService class with corresponding instances of said CIM_Identity class via QuotaAffectsElement associations to enable performing quota related operations.

10. The method according to claim 9, wherein each of said QuotaAffectsElement associations comprises one or more of quota related properties and information to enable performing said quota related operations.

11. The method according to claim 10, wherein said quota related properties comprise one or more of “

AllocationQuota” and

“

AllocatedBytes”

properties.

12. A system for network management, the system comprising:

one or more processors in a network device that is managed via Distributed Management Task Force (DMTF) protocol, said one or more processors being operable to;

receive a request during opaque management data operations, wherein said request is handled in said network device using one or more instances of Common Information Model (CIM) based CIM_OpaqueManagementData class representing one or more corresponding storage components in said network device; and

authenticate operations performed during said handling of said request using Common Information Model (CIM) data model access profile by utilizing one or more instances of at least one of CIM_Role and CIM_Privilege, via one or more instances of CIM_Identity class.

13. The method according to claim 12, wherein said one or more processors enable validation of access related information via said Common Information Model (CIM) data model access profiles during said opaque management data operations, wherein said access related information comprise one or more of ownership, access rights, and quota information.

14. The system according to claim 13, wherein said CIM data model access profiles comprise one or more of Role Based Authorization (RBA) and Simple Identity Management (SIM) based profiles.

15. The system according to claim 14, wherein said one or more processors enable utilization of said one or more instances of said CIM_Identity class while utilizing RBA/SIM based profiles to perform said validation of access related information.

16. The system according to claim 15, wherein said one or more processors enable utilization of a plurality of CIM_Account class to represent a plurality of common users sharing a common instance of said CIM_Identity class.

17. The system according to claim 15, wherein said one or more processors enable utilization of a plurality of instances of CIM_UserEntity class to represent a plurality of common applications sharing a common instance of said CIM_Identity class.

18. The system according to claim 15, wherein said one or more processors enable association of said one or more instances of CIM_OpaqueManagementData class with corresponding instances of said CIM_Identity class via OpaqueManagementDataUserElement associations to enable performing said validation of said access related information.

19. The system according to claim 18, wherein each of said OpaqueManagementDataUserElement associations comprises at least one of ownership, access right properties, and information to enable performing said validation of said access related information.

20. The system according to claim 15, wherein said one or more processors enable association of instances of a CIM_OpaqueManagementDataService class with corresponding instances of said CIM_Identity class via QuotaAffectsElement associations to enable performing quota related operations.

21. The system according to claim 20, wherein each of said QuotaAffectsElement associations comprises one or more of quota related properties and information to enable performing said quota related operations.

22. The system according to claim 21, wherein said quota related properties comprise one or more of “

AllocationQuota” and

“

AllocatedBytes”

properties.

23. A non-transitory computer readable medium having stored thereon, a computer program having at least one code section for network management, the at least one code section being executable by a computer, managed via Distributed Management Task Force (DMTF) protocols, for causing the computer to perform steps comprising:

receiving a request during opaque management data operations, wherein said request is handled in the computer using one or more instances of Common Information Model (CIM) based CIM_OpaqueManagementData class representing one or more corresponding storage components in the computer; and

authenticating operations performed during said handling of said request using Common Information Model (CIM) data model access profiles by utilizing one or more instances of at least one of CIM_Role and CIM_Privilege, via one or more instances of CIM_Identity class.

24. The non-transitory computer readable medium according to claim 23, comprising validating access related information via said Common Information Model (CIM) data model access profiles during said opaque management data operations, wherein said access related information comprise one or more of ownership, access rights, and quota information.

25. The non-transitory computer readable medium according to claim 24, wherein said CIM data model access profiles comprise one or more of Role Based Authorization (RBA) and Simple Identity Management (SIM) based profiles.

26. The non-transitory computer readable medium according to claim 25, comprising utilizing said one or more instances of said CIM_Identity class while utilizing RBA/SIM based profiles to perform said validation of said access related information.

27. The non-transitory computer readable medium according to claim 26, comprising utilizing a plurality of CIM_Account class to represent a plurality of common users sharing a common instance of said CIM_Identity class.

28. The non-transitory computer readable medium according to claim 26, comprising utilizing a plurality of instances of CIM_UserEntity class to represent a plurality of common applications sharing a common instance of said CIM_Identity class.

29. The non-transitory computer readable medium according to claim 26, comprising associating said one or more instances of CIM_OpaqueManagementData class with corresponding instances of said CIM_Identity class via OpaqueManagementDataUserElement associations to enable performing said validation of said access related information.

30. The non-transitory computer readable medium according to claim 29, wherein each of said OpaqueManagementDataUserElement associations comprises at least one of ownership, access right properties, and information to enable performing said validation of said access permission related information.

31. The non-transitory computer readable medium according to claim 26, comprising associating instances of a CIM_OpaqueManagementDataService class with corresponding instances of said CIM_Identity class via QuotaAffectsElement associations to enable performing quota related operations.

32. The non-transitory computer readable medium according to claim 31, wherein each of said QuotaAffectsElement associations comprises one or more of quota related properties and information to enable performing said quota related operations.

33. The non-transitory computer readable medium according to claim 32, wherein said quota related properties comprise one or more of “

AllocationQuota” and

“

AllocatedBytes”

properties.