Method And System For Device Property For Specification Of Vendor Specific Protocol Features

• US 20090182892A1
• Filed: 08/20/2008
• Published: 07/16/2009
• Est. Priority Date: 01/16/2008
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Krig, Scott
• Granted Patent: US 8,819,256 B2
• Time in Patent Office: Days
• US Class Current: 709/232
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions

Abstract

One or more vendor extensions that may be communicated to and/or from a device that may communicate via media transfer protocol (MTP) may be specified within an extension of the MTP. The vendor extension may comprise vendor specific information such as proprietary supported features. Vendor extensions may be indicated as a device property and may be communicated to another device during initiation of communication. Supported vendor extensions may be specified in an MTP DevicePropDesc dataset as a response to a request such as a MTP GetDevicePropDesc operation. Alternatively, data from a current value field of an MTP DevicePropDesc dataset may be returned in response to a GetDevicePropValue operation. An MTP SetDevicePropValue operation may be utilized for selecting a vendor extension. However, the selection may be accepted or rejected by a device. An event may be issued to other devices when a change of vendor extension has occurred.

Claims

1. A method for communicating multimedia information, the method comprising:

specifying within an extension of a media transfer protocol (MTP), one or more vendor extensions that enables exchange of vendor specific information when communicating to and/or from a device that communicates via said MTP.

2. The method according to claim 1, comprising indicating said one or more vendor extensions as a device property within said extension of the MTP.

3. The method according to claim 1, comprising communicating said one or more vendor extensions to another device when said device initiates communication with said another device.

4. The method according to claim 1, comprising specifying said one or more vendor extensions in response to a request.

5. The method according to claim 4, wherein said request comprises an MTP GetDevicePropDesc operation.

6. The method according to claim 4, wherein said response comprises an MTP DevicePropDesc dataset.

7. The method according to claim 4, wherein said request comprises a GetDevicePropValue operation.

8. The method according to claim 4, wherein said response comprises data from a current value field of an MTP DevicePropDesc dataset.

9. The method according to claim 1, comprising selecting a vendor extension for said communicating to and/or from said device.

10. The method according to claim 9, wherein said device accepts or rejects said selected vendor extension.

11. The method according to claim 1, comprising selecting a vendor extension for said communicating to and/or from said device via a SetDevicePropValue operation.

12. The method according to claim 1, comprising issuing an event to indicate when changes to said specified vendor extension occurs.

13. A system for communicating multimedia information, the system comprising:

one or more processors in a device that specifies within an extension of a media transfer protocol (MTP), one or more vendor extensions that enables exchange of vendor specific information when communicating to and/or from a device that communicates via said MTP.

14. The system according to claim 13, wherein said one or more processors enables indication of said one or more vendor extensions as a device property within said extension of the MTP.

15. The system according to claim 13, wherein said one or more processors enables communication of said one or more vendor extensions to another device when said device initiates communication with said another device.

16. The system according to claim 13, wherein said one or more processors specifies said one or more vendor extensions in response to a request.

17. The system according to claim 16, wherein said request comprises an MTP GetDevicePropDesc operation.

18. The system according to claim 16, wherein said response comprises an MTP DevicePropDesc dataset.

19. The system according to claim 16, wherein said request comprises a GetDevicePropValue operation.

20. The system according to claim 16, wherein said response comprises data from a current value field of an MTP DevicePropDesc dataset.

21. The system according to claim 13, wherein said one or more processors enables selection of a vendor extension for said communicating to and/or from said device.

22. The method according to claim 21, wherein said device accepts or rejects said selected vendor extension.

23. The system according to claim 13, wherein said one or more processors enables selection of a vendor extension for said communicating to and/or from said device via a SetDevicePropValue operation.

24. The system according to claim 13, wherein said one or more processors enables issuance of an event to indicate when changes to said specified vendor extension occurs.

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

specifying within an extension of a media transfer protocol (MTP), one or more vendor extensions that enables exchange of vendor specific information when communicating to and/or from a device that communicates via said MTP.

26. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for indicating said one or more vendor extensions as a device property within said extension of the MTP.

27. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for communicating said one or more vendor extensions to another device when said device initiates communication with said another device.

28. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for specifying said one or more vendor extensions in response to a request.

29. The machine-readable storage according to claim 28, wherein said request comprises an MTP GetDevicePropDesc operation.

30. The machine-readable storage according to claim 28, wherein said response comprises an MTP DevicePropDesc dataset.

31. The machine-readable storage according to claim 28, wherein said request comprises a GetDevicePropValue operation.

32. The machine-readable storage according to claim 28, wherein said response comprises data from a current value field of an MTP DevicePropDesc dataset.

33. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for selecting a vendor extension for said communicating to and/or from said device.

34. The machine-readable storage according to claim 33, wherein said device accepts or rejects said selected vendor extension.

35. The machine-readable storage according to claim 25, selecting a vendor extension for said communicating to and/or from said device via a SetDevicePropValue operation.

36. The machine-readable storage according to claim 25, wherein said at least one code section comprises code for issuing an event to indicate when changes to said specified vendor extension occurs.