DTCP-IP

DTCP 

Digital Transmission Content Protection. DTCP Specifications defines a cryptographic protocol for protecting media content as it traverses digital transmission mechanisms such as IEEE 1394-1995 standards.

DTCP specification addresses four layers of copy protection:
  • Copy control information (CCI)
  • Device authentication and key exchange (AKE)
  • Content encryption
  • System renewability

DTCP is originally designed for IEEE 1394(FireWire) , but was latter mapped to TCP/IP.

DTCP-IP

(DTCP Volume 1,Supplement E, Mapping DTCP to IP)

  •  V1SE.10.1 Recommended MIME type for DTCP protected content
application/x-dtcp1;CONTENTFORMAT=mimetype
or
application/x-dtcp1;DTCP1HOST=;DTCP1PORT=;CONTENTFORMAT=mimetype

the appended new data is used to facilitate the AKE(Authentication and Key Exechange) process.

  • V1SE.10.2.1 URI Recommended Format
service://host:port/path/filename.fileextension?CONTENTPROTECTIONTYPE=DTCP1&DTCP1HOST=host&DTCP1PORT=port

  • V1SE10.2.2 HTTP response / request
Content-Type:application/x-dtcp1;DTCP1HOST=host;DTCP1PORT=port;CONTENTFORMAT=mimetype

  • V1SE10.3.1 Range.dtcp.com
The Range.dtcp.com header is used in the same manner as the RANGE header.
  • V1SE10.3.2 Content-Range.dtcp.com
The Content-Range.dtcp.com header is used in the same manner as the CONTENT-RANGE header

When performing a request for a video item, the source must align the returned PCP(Protected Content Packet) to specific points(GOP or VOB boundary in MPEG content) . This ensures that the returned data can be rendered without further request.
The size of encrypted and non encrypted media are different. In the DLNA Link Protection Guidelines, we refer to two "byte domains': "Cleartext Byte Domain" refers to the byte position in the unencrypted media content; the "Network Byte Domain" refers to the byte position in the encrypted media content.
The Cleartext Byte Seek Request Header can be different depending on the Link Protection System used.
8.4.1 HTTP Cleartext Byte Seek Request Header for DTCP-IP
8.4.2 HTTP Cleartext Byte Seek Response Header for DTCP-IP


  • V1SE.10.4 BLKMove.dtcp.com
The BLKMove.dtcp.com header is used to specify which Kxm is used in the Move Transmission process
BLKMove.dtcp.com:

  • V1SE.10.5.1 DTCP.COM_FLAGS param
The DTCP.COM_FLAGS param is used in 4th field of res@protocolInfo property to show static attribute of content regarding DTCP transmission.

  • V1SE.10.5.2 res@dtcp:uploadInfo
The res@dtcp:uploadInfo property is used to show how the content is uploaded using DTCP.










留言

熱門文章