Efficient license validation in MPML DRM architecture

Abstract

Multiparty multilevel DRM architecture (MPML-DRM-A) involves multiple parties such as owner, multiple levels of distributors and consumers. The owner issues redistribution licenses to its distributors, who in turn generate and issue variations of these redistribution licenses to their subdistributors. Also the distributors generate and issue usage licenses to the consumers to consume the contents. But, these variations of the redistribution licenses and usage licenses generated and issued by each distributor must be validated by a validation authority against the redistribution licenses that it has received. In MPML-DRM-A, there may exist multiple, different types of redistribution licenses for a content. Validation using multiple redistribution licenses may become difficult in real time. Further, storage of multiple redistribution licenses for validation presents a challenge of reducing storage space requirements. Hence, in this paper we propose a bit-vector transform based license organizing structure, and present a method to do the validation of issued licenses in the bit-vector transform domain efficiently. Experimental results show that our license organization structure helps to achieve low validation time and storage space complexity. Categories and Subject Descriptors General TermsAlgorithms, Security Keywords Digital Rights Management (DRM), License Organization, License ValidationPermission to make digital or hard copies of all or part of this work for personal or classroom use is granted without fee provided that copies are not made or distributed for profit or commercial advantage and that copies bear this notice and the full citation on the first page. To copy otherwise, to republish, to post on servers or to redistribute to lists, requires prior specific permission and/or a fee. DRM'09, November 9, 2009, Chicago, Illinois, USA. Copyright 2009 ACM 978-1-60558-779-0/09/11 ...$10.00.

Aggregate licenses validation for digital rights violation detection

“…In DRM systems, the contents are generally distributed from the owner to consumers through middle distributors [Hwang et al 2004;Sachan et al 2009;Jamkhedkar and Heileman 2009]. Each party, namely the owner, distributors, and consumers have their own rights over the contents [Iannella 2008;Arnab and Hutchison 2005].…”

“…Each party, namely the owner, distributors, and consumers have their own rights over the contents [Iannella 2008;Arnab and Hutchison 2005]. Their rights in DRM systems are specified using two types of licenses: redistribution licenses and usage licenses [Sachan et al 2009]. A redistribution license allows a distributor to redistribute the content to its subdistributors and consumers as per the permissions and constraints [Sachan et al 2009;Garcia and Gil 2010] specified in the redistribution license that it has received.…”

“…Their rights in DRM systems are specified using two types of licenses: redistribution licenses and usage licenses [Sachan et al 2009]. A redistribution license allows a distributor to redistribute the content to its subdistributors and consumers as per the permissions and constraints [Sachan et al 2009;Garcia and Gil 2010] specified in the redistribution license that it has received. The distributors in turn can use their received redistribution license to generate and issue new different types of redistribution licenses to their subdistributors and new usage licenses to consumers.…”

“…L 2 U is invalid because UK is outside Asia and L 4 U is invalid because the sum of the aggregate constraint's counts in previously issued valid licenses (L 1 U and L 3 U ) and L 4 U becomes 105, which exceeds the maximum allowed 100 using L D . For business flexibility reasons, distributors may need to acquire multiple redistribution licenses for the same content [Sachan et al 2009]. In case of multiple redistribution licenses, the validation becomes complex for both instance-based and aggregate constraints.…”

“…For instance-based constraints, it requires the verification of each constraint range in an issued license with the same constraint in each redistribution license received by the distributor. If all the instance-based constraints' ranges/values in an issued license are within the respective constraint range in one or more than one redistribution licenses (say, a set S of redistribution licenses) then the issued license is instance-based validated [Sachan et al 2009]. For aggregate validation, we can randomly select a redistribution license with sufficient number of remaining aggregate constraint counts (after validation of previously issued licenses) from set S to validate the aggregate constraints count in the issued license.…”