BS EN 62227-2008 pdf download.Multimedia home server systems – Digital rights permIssIon code.
The permission code’s permission actor identifier has the ability to subsume an existing ID system. For example, with respect to issuer lDs, some rights organizations maintain ID systems with member ids or internal management ids. Identifiers for internal management also exist for content. Open systems such as the ISBN code for publications are already in place. By placing a header/prefix specified in the permission code onto these existing id systems, these existing identifiers can be repurposed as permission actor identifiers. This allows for a smooth transition from existing systems.
With permission receivers in particular, the permission actor Is frequently an Individual end user without the kind of existing ID system mentioned above from which to draw upon. Furthermore, the DM utilizing the permission code shall be able to decipher the nature of the user that would be accessing the content. For these purposes, the standard allows for identifiers of respective devices that intermediate the content distribution chain to serve as receiver IDs.
Permission actor ids are assigned and managed by id centers. Existing organizations such as rights holder agencies. for example, can become ID centers. This means existing organizations would be able to assign permission actor ids by combining the ID center code and a code from the existing code system used within the organization itself. There may be multiple ID centers for each permission actor category.
The following are some examples rn which device lOs are used as alternate identifiers of individuals. Each example has its own respective pros and cons. The methodology chosen is left up to implementation and is Out of scope of this standard. This standard will define the framework for permission actors only. The actual manner in which permission actor identifiers are assigned will be specified in a separate implementation-level document.
• Use identifiers (serial numbers etc.) that belong to viewing, recording and playback devices, such as televisions and video recorders, as alternate identifiers for individual end users.
• Use identifiers (serial numbers etc.) that belong to integrated or removable storage media, such as HOD, DVD media and memory cards, as alternate identifiers for individual end users.
• Use identifiers (phone numbers etc.) that belong to quasi-personal devices (devices that can generally be thought of as belonging to an individual, though not in the strictest sense), such as cell phones, as alternate identifiers for individual end users.
4.3.1.3 Domain
A domain in this standard refers to a set of actors to which a common set of rules apply in the context of content management. These common set of rules can be applied to each piece of content, or applied independently from content.
Generally, usage permissions for content have been bound to storage media or devices. For example, ihis content cannot be copied to other storage medIa,” or this content can only be played on this device”, are some of the common ways in which content have been handled. However, when permission is granted to a domain instead, all storage media and devices that belong to it are handled equally and will operate under a common set of permission terms and rules.
For example, consider home domains. A home domain refers to “a set of devices present within a given home. A content permission issuer can issue permission to freely copy content a within the home domain.tm Here. the permission receiver would have the ability to handle content a in accordance with the common rule: content a can be freely copied within the home domain.
Likewise, a set of devices that belong to a school can be defined as a school domain. Assuming content b will be used for educational purposes, a permission issuer can issue permission that “allows copying and editing of content b within the school domain.” Here, the permission receiver would be able to extract and compile portions of content b needed, and insert them within the school’s own content to create new educational material. The permission receiver can also copy the resulting content to devices that belong to the school domain across classrooms.
As described, content usage permissions can be bound to domains. On the other hand, other types of permission bindings can also be supported. For example, permission can be bound to an individual storage media unit in a conventional manner (for example, “nO copying allowed from this disk”). Permission can also be bound to an individual user (for example, only Mr. X can view this content). The advantage of binding permissions to domains in contrast to conventional permissions issued to individual units is in their ability to constrain undesirable diffusion of content for the benefit of rights holders while allowing for the sharing of content within a community.BS EN 62227-2008 pdf download.