Media transport protocol extensions for system integrity and robustness, and applications thereof

• US 9,172,710 B2
• Filed: 12/31/2007
• Issued: 10/27/2015
• Est. Priority Date: 02/05/2007
• Status: Active Grant

• Current Assignee: Avago Technologies International Sales Pte Limited (Broadcom, Inc.)
• Original Assignee: Broadcom Corporation (Broadcom, Inc.)
• Inventors: Krig, Scott
• Primary Examiner(s): Meky, Moustafa M
• Application Number:
  US11/967,939
• Publication Number:
  US 20080189348A1
• Time in Patent Office: 2,857 Days
• Field of Search: 709/227, 709/228, 709/230, 709200-203, 709217-226, 709/229, 726/27
• US Class Current: 1/1
• 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
• CPC Class Codes: H04L 63/12 Applying verification of the received information cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32
• CPC Class Codes: H04L 65/1066 Session management
• CPC Class Codes: H04L 65/65 Network streaming protocols, e.g. real-time transport protocol [RTP] or real-time control protocol [RTCP]

Abstract

Methods, systems and computer program products to implement extensions of the Media Transport Protocol (MTP) are provided herein. The methods include opening a session between an initiator and a responder, exchanging one or more of device and system information and sending one of an operation or event based on media player application features. The operation includes one or more of a dataset, response code, operation parameter and response parameter. In an embodiment, the extensions enable the initiator and responder to manage connections efficiently between devices, send media player application information to a media player device, exchange device and system information, manage digital rights, monitor system security and specify properties within one or more extensions of MTP. These extensions may be in the form of one or more of an operation, an event, a dataset or property code.

Claims

1. A method for exchanging system and protocol integrity information between an initiator and a responder operating under a data transfer protocol, comprising:

opening a session between an initiator and a responder;

exchanging one or more of device and system information between the initiator and the responder; and

sending an event from the responder to the initiator upon detecting code or data tampering of objects or upon detecting code or data tampering of digital rights management (DRM) licenses stored on the responder.

2. The method of claim 1, wherein the protocol is a Media Transport Protocol (MTP).

3. The method of claim 1, wherein the event includes a dataset that has one or more of:

a DRM system integrity status, a DRM code integrity status, a Media Transport Protocol (MTP) code integrity status, a platform code integrity status, an application code integrity status and an error message.

4. The method of claim 3, wherein the DRM system integrity status, the DRM code integrity status, the MTP code integrity status, and the platform code integrity status are one of:

component compromised, component secure or component status unknown.

5. The method of claim 1, further comprising sending an operation from the initiator to the responder to determine a system integrity of the responder.

6. The method of claim 5, wherein in response to receiving the operation, the responder checks:

an integrity of DRM secrets in storage, an integrity of executable DRM library code, an integrity of executable MTP code stack and a system integrity.

7. The method of claim 5, wherein in response to receiving the operation, the responder sends to the initiator a dataset that has one or more of:

a DRM system integrity status, a DRM code integrity status, a Media Transport Protocol (MTP) code integrity status, a platform code integrity status, an application code integrity status and an error message.

8. A method for exchanging system and protocol integrity information between an initiator and a responder operating under a data transfer protocol, comprising:

opening a session between an initiator and a responder;

exchanging one or more of device and system information between the initiator and the responder;

sending an operation from the initiator to command the responder to perform a sequence of steps to determine protocol integrity of the responder; and

sending an event from the responder to the initiator upon detecting code or data tampering of objects or upon detecting code or data tampering of digital rights management (DRM) licenses stored on the responder.

9. The method of claim 8, wherein in response to receiving the operation, the responder opens a session, waits to receive an operation from the initiator requesting system information, provides system information to the initiator, sends a request to the initiator for a 1-byte object, receives a 1-byte object, sends the received 1-byte object to the initiator and closes the session.

10. The method of claim 8, wherein the initiator measures a round-trip delay time to send and receive a 1-byte object and determines whether the sequence of steps were completed by the responder as required by a Media Transfer Protocol (MTP).

11. A method for managing Digital Rights Management (DRM) between an initiator and a responder operating under a Media Transport Protocol (MTP), comprising:

opening a session between an initiator and a responder;

exchanging one or more of device and system information between the initiator and the responder; and

sending an event from the initiator to the responder to check an integrity of objects stored on the responder.

12. The method of claim 11, further comprising sending an operation from the responder to the initiator that includes DRM system information of the responder.

13. The method of claim 12, wherein the operation includes a dataset having one or more of:

a manufacturer, a serial number, a model number, a version number, a DRM friendly name, DRM operations supported, DRM events supported, DRM capabilities and a DRM store capacity in bytes.

14. The method of claim 12, wherein the operation includes a response code, said response code being one of OK or Parameter_not_Supported.

15. The method of claim 11, further comprising sending an operation from the responder to the initiator indicating space available in a DRM storage of the responder.

16. The method of claim 15, wherein the operation includes a response parameter indicating the space availability in the DRM storage of the responder.

17. The method of claim 15, wherein in response to the operation, the responder checks for a DRM status code and a DRM license for each object and records an object identification for objects that do not have the DRM status code and/or the DRM license.

18. The method of claim 15, wherein in response to the operation, the responder determines whether a DRM license is associated with each object and records a DRM license ID for offending licenses.

19. The method of claim 15, wherein in response to the operation, the responder determines whether object properties are valid and records Object IDs for objects with invalid properties.

20. The method of claim 15, wherein the responder sends an operation to the initiator with a dataset that indicates integrity of object metadata stored on the responder.

21. The method of claim 20, wherein the dataset includes one or more of:

a count of orphaned DRM licenses, an array of DRM license identifications, a count of DRM protected objects without associated DRM licenses, an array of DRM protected object identifications without associated DRM licenses, a count of objects with invalid or corrupt metadata property codes and an array of object identifications with corrupted metadata property codes.

22. The method of claim 11, further comprising sending an event from the responder to the initiator indicating that a DRM storage space is full.

23. The method of claim 11, further comprising sending an operation from the initiator to the responder to delete media objects without associated DRM licenses and to delete DRM licenses without corresponding media objects.

24. The method of claim 23, wherein in response to the operation, the responder checks for a DRM status code and a DRM license for each object and deletes objects that do not have the DRM status code and/or the DRM license.

25. The method of claim 23, wherein in response to the operation, the responder determines whether each DRM license is associated with an object and deletes unassociated DRM licenses.

26. The method of claim 11, further comprising sending an event from the responder to the initiator to indicate objects and/or DRM licenses that are invalid or corrupt.

27. The method of claim 26, wherein the responder sends the event if an object does not have a DRM status code and/or a DRM license.

28. The method of claim 26, wherein the responder sends the event if a DRM license is unassociated with an object.

29. The method of claim 26, wherein the responder sends the event if an object has invalid properties.