BS EN 62481-4-2014 pdf download.Digital living network alliance (DLNA) home networked device interoperability guidelines Part 4: DRM interoperability solutions (TA9).
The following sequence gives DTCP-IP DIS Download Move.
• A Download Controller obtains URI, DTCP Socket information and availability of DTCP-lP DIS Move for a specific content by the CDS:Browse action, The availability is indicated by the DIS-DTCP-move flag in DLNA.ORG_FLAGS parameter.
• The Download Controller initiates DTCP-IP Move RTT-AKE to the DTCP Socket. As the result of DTCP-IP Move RTT-AKE, the DMS and the Download Controller share an encryption key for Move Transmission identified by Kxi&Jabel.
• The Download Controller invokes HTTP GET request with Kxu_label as a value of BLKM0ve.dtcp.com HTTP header to the URI. The DMS sends the corresponding content encrypted using the encryption key identified by the KxM_label.
• After the Move Transmission completes, the Download Controller initiates DTCP-IP Move Commitment process. As a result of this process, the content on the DMS becomes unusable and the content on the Download Controller becomes usable.
A.2.4 Upload Copy sequence
Figure A.4 and the explanation following Figure A.4 describe the Upload Copy sequence example.
The following sequence gives DTCP-IP DIS Upload Copy.
An Upload Controller obtains Device Description and checks whether a <dlna:XDLNACAP> element includes the av-upload and dtcp-copy Capability ID in order to know an upload copy capability of a DMS for a content of AV Media Class. Next the Upload Controller obtains Service Description and checks whether the DMS implements CDS:X_GetDLNAUploadProfiles action. If the DMS implements CDS : X_GetDLNAUploadProfiles action, the Upload Controller invokes CDS:X_GetDLNAUploadProfiles request in order to know the acceptable DLNA Media Format Profile ID(s) of the uploading content If not, the Upload Controller invokes CMS:GetProtocollnfo request.
• The Upload Controller invokes CDS:CreateObject request to create CDS item for a content which will be copied. The DMS returns a URI for HTTP POST with res@importUri property in CDS:CreateObject response.
• To initiate a content transfer, the Upload Controller sends HTTP POST request header to the URI which is a value of the res@importUri property. It includes Content-Type HTTP header with DTCP Socket information.
• The DMS initiates DTCP-IP AKE to that DTCP Socket. As the result of DTCP-IP AKE, the DMS and the Upload Controller share an encryption key for the content transfer, and then the DMS returns the HTTP status code of 100 (Continue).
• The Upload Controller sends the corresponding content encrypted. using the encryption key shared previously to the URI.
A.2.5 Upload Move sequence
Figure A.5 and the explanation following Figure A.5 describe the Upload Move sequence example.
The following sequence gives DTCP-IP DIS Upload Move.
An Upload Controller obtains Device Description and checks whether a <dlna:X_DLNACAP> element includes the av-upload and dtcp-move Capability ID in order to know an upload move capability of a DMS for a content of AV Media Class. Next the Upload Controller obtains Service Description and checks whether the DMS implements CDS:X_GetDLNAUploadProfiles action. If the DMS implements CDS:X_GetDLNAUploadProfiles action, the Upload Controller invokes CDS:X_GetDLNAUploadProfiles request in order to know acceptable DLNA Media Format Profile ID(s) of the uploading content. If not, the Upload Controller invokes CMS:GetProtocollnfo request.
The Upload Controller invokes CDS:CreateObject request to create CDS item for a content which will be moved. The CDS:CreateOblect request includes res@dtcp:uploadlnfo property since the subsequent content transfer follows the DTCP-IP Move. The DMS returns a URI for HTTP POST with res@importUri property in CDS:CreateObject response.
• To initiate the Move transaction, the Upload Controller sends HTTP POST request header to the URI which is a value of the res@importUri property. It includes a Content-Type HTTP header with DTCP Socket information.
• The DMS initiates DTCP-IP Move RTT-AKE to the DTCP Socket. As the result of DTCP-lP
Move RTT-AKE, the DMS and the Upload Controller share an encryption key for Move
Transmission identified by Kxu_Iabel, and then the DMS returns the HTTP status code of 100
(Continue). It includes BLKMove.dtcp.com HTTP header whose value is the Kxujabel.
• The Upload Controller sends the corresponding content encrypted using the encryption key identified by the KXM_Iabel to the URI.
• After the Move Transmission completes, the DMS initiates DTCP-IP Move Commitment process. As a result of this process, the content on the Upload Controller becomes unusable and the content on the DMS becomes usable.BS EN 62481-4-2014 pdf download.