This scenario involves content registration, protection, search, licensing, authorization-based content access control, content storage and reporting. It is devised for limited capabilities devices. In some cases, the encryption strength being used should be limited so as not to be detrimental to the devices performance. In such cases, if content is already registered and protected using non-compatible protection mechanisms, the Workflow Manager could be responsible for decrypting content and reencrypting it to deal with the devices limitations. Otherwise, if content is only to be used by limited capabilities devices, it should be encrypted using the suitable protection mechanism when uploaded to the CS.

Example: A content distributor that is already using mtPlatform for trading and distributing protected content wants that content to be available for mobile devices. Since the device’s decryption capabilities are limited, content may not use the same encryption strength as for PC-devised content or may be adapted to fulfill the device’s requirements.