Method and System for Light-Weight SOAP Transport for Web Services Based Management

• US 20080172482A1
• Filed: 01/12/2007
• Published: 07/17/2008
• Est. Priority Date: 01/12/2006
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Shah, Hemal
• Granted Patent: US 8,769,021 B2
• Time in Patent Office: Days
• US Class Current: 709/223
• CPC Class Codes: H04L 41/0213 Standardised network management protocols, e.g. simple network management protocol [SNMP]
• CPC Class Codes: H04L 41/344 Out-of-band transfers
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Certain aspects of a method and system for light-weight simple object access protocol (SOAP) transport for web services based management are disclosed. Aspects of a method may include managing a system using a simple object access protocol (SOAP) message that is mapped over one or both of: a remote management and control protocol (RMCP) and a RMCP security extensions protocol (RSP) to enable remote management of systems using Web services in out-of-band (OOB) management devices.

Claims

1. A method for processing network information, the method comprising:

managing a system using a simple object access protocol (SOAP) message that is mapped over one or both of;

a remote management and control protocol (RMCP) and a RMCP security extensions protocol (RSP).

2. The method according to claim 1, comprising managing said system using said mapped SOAP message and one or more Web services.

3. The method according to claim 2, comprising remotely managing said system via said one or more Web services through out-of-band (OOB) management.

4. The method according to claim 3, comprising securing said system via said out-of-band (OOB) management.

5. The method according to claim 1, wherein said mapping supports one-way message exchange of said SOAP messages.

6. The method according to claim 1, wherein said mapping supports a request-response message exchange of said SOAP messages.

7. The method according to claim 1, wherein said mapping supports multicasting of said SOAP messages.

8. The method according to claim 1, comprising retransmitting said mapped SOAP message.

9. The method according to claim 1, comprising acknowledging receipt of said mapped SOAP message.

10. The method according to claim 1, comprising securing said system by authenticating said mapped SOAP message.

11. The method according to claim 1, comprising securing said system by checking an integrity of said mapped SOAP message.

12. The method according to claim 1, wherein said mapping supports anti-replay protection of said SOAP messages.

13. A system for processing network information, the system comprising:

one or more circuits that enable management of a system using a simple object access protocol (SOAP) message that is mapped over one or both of;

a remote management and control protocol (RMCP) and a RMCP security extensions protocol (RSP).

14. The system according to claim 13, wherein said one or more circuits enables management of said system using said mapped SOAP message and one or more Web services.

15. The system according to claim 14, wherein said one or more circuits enables remote management of said system via said one or more Web services through out-of-band (OOB) management.

16. The system according to claim 15, wherein said one or more circuits enables securing said system via said out-of-band (OOB) management.

17. The system according to claim 13, wherein said mapping supports one-way message exchange of said SOAP messages.

18. The system according to claim 13, wherein said mapping supports a request-response message exchange of said SOAP messages.

19. The system according to claim 13, wherein said mapping supports multicasting of said SOAP messages.

20. The system according to claim 13, wherein said one or more circuits enables retransmission of said mapped SOAP message.

21. The system according to claim 13, wherein said one or more circuits enables acknowledgment of receipt of said mapped SOAP message.

22. The system according to claim 13, wherein said one or more circuits enables securing said system by authenticating said mapped SOAP message.

23. The system according to claim 13, wherein said one or more circuits enables securing said system by checking an integrity of said mapped SOAP message.

24. The system according to claim 13, wherein said mapping supports anti-replay protection of said SOAP messages.

25. A machine-readable storage having stored thereon, a computer program having at least one code section for processing network information, the at least one code section being executable by a machine for causing the machine to perform steps comprising:

managing a system using a simple object access protocol (SOAP) message that is mapped over one or both of;

a remote management and control protocol (RMCP) and a RMCP security extensions protocol (RSP).

26. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for managing said system using said mapped SOAP message and one or more Web services.

27. The machine-readable storage according to claim 26, wherein said at least one code section comprises code for remotely managing said system via said one or more Web services through out-of-band (OOB) management.

28. The machine-readable storage according to claim 27, wherein said at least one code section comprises code for securing said system via said out-of-band (OOB) management.

29. The machine-readable storage according to claim 25, wherein said mapping supports one-way message exchange of said SOAP messages.

30. The machine-readable storage according to claim 25, wherein said mapping supports a request-response message exchange of said SOAP messages.

31. The machine-readable storage according to claim 25, wherein said mapping supports multicasting of said SOAP messages.

32. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for retransmitting said mapped SOAP message.

33. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for acknowledging receipt of said mapped SOAP message.

34. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for securing said system by authenticating said mapped SOAP message.

35. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for securing said system by checking an integrity of said mapped SOAP message.

36. The machine-readable storage according to claim 25, wherein said mapping supports anti-replay protection of said SOAP messages.