Patent Grant
9009308
The invention relates to a method of generating an Authorized Domain. The invention further relates to a system for generating an Authorized Domain. Further, the invention relates to a computer readable medium having stored thereon instructions for causing one or more processing units to execute the method according to the invention.
Recent developments in content distribution technologies (i.e. the Internet and removable media) make it much easier to exchange content than ever before. The rapid adoption by consumers shows that such technologies really address their needs. A side effect is that they also enable easy illegal copying and distribution of content. The content industry sees this latter development as a threat to their business. Therefore in recent years, the amount of content protection systems is growing in a rapid pace. Some of these systems only protect the content against illegal copying, while others are also prohibiting the user (person) to get access to the content. The first category is called Copy Protection (CP) systems. CP systems have traditionally been the main focus for consumer electronics (CE) devices, as this type of content protection is thought to be cheaply implemented and does not need bi-directional interaction with the content provider. Some examples are the Content Scrambling System (CSS), the protection system of DVD ROM discs and DTCP (a protection system for IEEE 1394 connections).
The second category is known under several names. In the broadcast world, systems of this category are generally known as conditional access (CA) systems, while in the Internet world they are generally known as Digital Rights Management (DRM) systems.
A home network can be defined as a set of devices that are interconnected using some kind of network technology (e.g., Ethernet, IEEE 1394, BlueTooth, 802.11b, 802.11g, etc.). Although network technology allows the different devices to communicate, this is not enough to allow devices to interoperate. To be able to do this, devices need to be able to discover and address the functions present in the other devices in the network. Such interoperability is provided by home networking middleware. Examples of home networking middleware are Jini, HAVi, UPnP, AVC.
The concept of Authorized Domains (ADs) tries to find a solution to both serve the interests of the content owners (that want protection of their copyrights) and the content consumers (that want unrestricted use of the content). The basic principle is to have a controlled network environment in which content can be used relatively freely as long as it does not cross the border of the authorized domain. Typically, authorized domains are centered around the home environment, also referred to as home networks. Of course, other scenarios are also possible. A user could for example take a portable device for audio and/or video with a limited amount of content with him on a trip, and use it in his hotel room to access or download additional content stored on his personal audio and/or video system at home. Even though the portable device is outside the home network, it is a part of the user's authorized domain. In this way, an Authorized Domain (AD) is a system that allows access to content by devices in the domain, but not by any others.
For a more extensive introduction to the use of an Authorized Domain, etc., see S. A. F. A. van den Heuvel, W. Jonker, F. L. A. J. Kamperman, P. J. Lenoir, Secure Content Management in Authorised Domains, Philips Research, The Netherlands, IBC 2002 conference publication, pages 467-474, held at 12-16 Sep. 2002.
Various proposals exist that implement the concept of authorized domains to some extent.
One type of previous solutions include device based Authorized Domains (ADs). Examples of such systems are SmartRight (Thomson Multimedia), xCP, and NetDRM (Matshushita). A further example of a device based AD given, for example, in European patent application serial number 02076998.0 (Ser. No. 10/514,901) by the same applicant.
In typical device based ADs, the domain is formed by a specific set of devices and content. Only the specific set of devices of the domain is allowed to access, use, etc. the content of that domain. There is not made any distinction of the various users of the specific set of devices.
A drawback of device based AD systems is that they typically do not provide the typical flexibility that a user wants or need, since users are restricted to a particular and limited set of devices. In this way, a user is not allowed to exercise the rights that the user has obtained anytime and anywhere he chooses. For example, if a user is visiting a friend's house he is not able to access his legally purchased content on the friend's devices as these devices would not typically be part of the particular and limited set of devices forming the domain comprising the user's content.
Another type of previous solutions are person based Authorized Domains, where the domain is based on persons instead of devices as was the case for device based ADs. An example of such a system is described, fpr example, in European patent application serial number 02079390.7 (Ser. No. 10/531,939) by the same applicant in which content is coupled to persons which then are grouped into a domain.
In a typical person based AD access to content bound to that AD is allowed by only a specific and limited set of users, but e.g. using any compliant device. Person based Authorized Domains typically offer easier domain management compared to device based ADs.
However, person based systems require person identification which is not always convenient or preferred by users. Further, a visitor to your home may want to access your content. As he does not have a person id device for that domain, it is not possible for him to access content. It would be preferred if devices in the home belonging to the domain could enable access of domain content by the visitor.
Therefore there is a need for a hybrid person and device based authorized domain having the individual advantages of each system.
It is an object of the invention to provide a method and corresponding system for providing an Authorized Domain structure based on both persons and devices. An additional object is to provide a method and system solving the above-mentioned shortcomings of prior art. A further object is to provide this in a simple, flexible, and efficient way.
These objects, among others, are achieved by a method (and corresponding system) generating an Authorized Domain (AD), the method comprising the steps of selecting a domain identifier uniquely identifying the Authorized Domain, binding at least one user to the domain identifier, and binding at least one device to the domain identifier, and thereby obtaining a number of devices and a number of persons that is authorized to access a content item of the Authorized Domain.
Hereby, a simple and efficient way of grouping devices and persons to an AD is obtained. Further, a hybrid device and person based Authorized Domain is provided. In this way, access is enabled to a content item of an authorized domain by a user operating a device either by verifying that the content item and the user is linked the same domain or by verifying that the device and the content item is linked to the same domain. Thereby, enhanced flexibility for one or more users when accessing content in an authorized domain is obtained while security of the content is still maintained. This is further done in a simple, secure, and reliable way.
In one embodiment, the method further comprises the step of binding at least one content item to the Authorized Domain given by the domain identifier.
In one embodiment, the step of binding at least one user to the domain identifier comprises: obtaining or generating a Domain Users List (DUC) comprising the domain identifier and a unique identifier for a user thereby defining that the user is bound to the Authorized Domain and/or the step of binding at least one device to the domain identifier comprises: obtaining or generating a Domain Devices List comprising the domain identifier and a unique identifier for a device thereby defining that the device is bound to the domain.
In one embodiment, the step of binding at least one content item to the Authorized Domain (AD) comprises:
In one embodiment, the step of binding at least one content item to the Authorized Domain comprises:
In one embodiment, the User Right or the Device Right or the Domain Rights comprises rights data representing which rights exists in relation to the at least one content item bound to the User Right or the Device Right or the Domain Rights.
In one embodiment, the method further comprises the step of controlling access to a given content item bound to the Authorized Domain by a given device being operated by a given user, the step comprising:
and allowing access for the given user via the given device and/or other devices to the content item if the given user is bound to the same Authorized Domain,
or allowing access for the given user and/or other users via the given device to the content item if the given device is part of the same Authorized Domain.
In one embodiment, the method further comprises the step of controlling access to a given content item, being bound to the Authorized Domain and having a unique content identifier, by a given device being operated by a given user comprising:
In one embodiment, the step of controlling access of a given content item further comprises:
In one embodiment, every content item is encrypted and that a content right is bound to each content item and to a User Right or a Device Rights or a Domain Rights, and that the content right of a given content item comprises an decryption key for decrypting the given content item.
In one embodiment,
Advantageous embodiments of the system according to the present invention are defined in the sub-claims described in detail in the following. The embodiments of system correspond to the embodiments of the method and have the same advantages for the same reasons.
Further, the invention also relates to a computer readable medium having stored thereon instructions for causing one or more processing units to execute the method according to the present invention.
These and other aspects of the invention will be apparent from and elucidated with reference to the illustrative embodiments shown in the drawings, in which:
a illustrates an exemplary (partial) data structure of a content container, a content right (CR) and a user right certificate (URC) according to the embodiment of the present invention shown in
b illustrates an exemplary (partial) data structure of a content container, a content right (CR) and a Domain Rights Certificate (DRC) according to the embodiment of the present invention shown in
Throughout the figures, same reference numerals indicate similar or corresponding features. Some of the features indicated in the drawings are typically implemented in software, and as such represent software entities, such as software modules or objects.
For more information on an authorized domain architecture and implementation options, the reader is referred to European patent application serial number 01204668.6 by the same applicant or European patent application serial number 02076998.0 (Ser. No. 10/514,901) by the same applicant. European patent application serial number 02076998.0 (Ser. No. 10/514,901) more specifically describes an implementation in which content and devices are coupled to a domain. Additionally, European patent application serial number 02079390.7 (Ser. No. 10/531,939) by the same applicant describes an implementation in which content is coupled to persons which then are grouped into a domain.
Please note that in practice content can only be accessed/used by means of a user operating a device. In the following text we assume that devices used in the system are compliant and “public” devices. This means that a device will adhere to certain operation rules (e.g. will not illegally output content on an unprotected digital interface) and that ownership of a device is not important (public). Device compliancy management, i.e. compliant device identification, renew-ability of devices, and revocation of devices, will be assumed to be in place (using known techniques), and will not be considered further here.
The user right (URC1, . . . URCN2) is a single connection, binding, coupling etc. between one user and a content right (which is required to decrypt a piece of content). By introducing this user right we now have five main entities in our system that could work as follows:
Preferably, authorized devices are bound to the AD (100) by a certificate. Likewise authorized persons/users are preferably also bound to the AD (100) via certificates. Content items are, in this particular embodiment, bound to a person by means of a user right certificate (URC). This user right certificate enables the use of a corresponding content right (CR) that preferably contains a cryptographic key for accessing the content, as will be explained in greater detail in connection with
Domain certificates are preferably issued by a domain authority. Alternatively, compliant devices with domain management capabilities can manage these certificates.
In the example shown in
In this way, specific content C1 and C2 are coupled to a specific person P1, specific content C3 coupled to a specific person P2, specific content CN2-2, CN2-1 and CN2 are coupled to a specific person PN1, and specific content C4-CN2-3 are distributed among specific person(s) P3-PN1-1 via their respective URC.
In this shown embodiment, a single content item is only allowed to be coupled to a single URC (indirectly via a content right) and thereby a single person. If several users needs a copy of the same content item it would in this embodiment be present once for each user and treated as different content items, which make rights management simpler. Alternatively and just as applicable, a single content item could be coupled to more than one person, as a CR can be linked to multiple URCs.
Persons P1, P2, . . . , PN1 and Domain devices D1, D2, . . . , DM are then grouped into forming the authorized domain (100).
Preferably, the binding, i.e. grouping and coupling, of devices, persons and content is according to the present invention done by the use of certificates. Preferably a Domain Devices Certificate or Domain Devices List (DDC), a Domain Users Certificate or Domain Users List (DUC), and a User Right Certificate or User Right List (URC) are used. In the following, reference is only made to certificates, although it is to be understood that such structures may, for example, be implemented as lists or the like instead.
The DDC lists the device(s), which are part of the domain (100), e.g. by comprising for each device a unique identifier. The DUC lists the user(s), which are part of the domain, e.g. by comprising a unique identifier or a (e.g. public) cryptographic key or a hash thereof for each user. DUC and DDC are shown an explained in greater detail in connection with
In a preferred embodiment, the DDC and DUC are associated with each other by means of a Domain Identifier (Domain_ID) contained in both certificates. In this way, a very simple way of linking the user(s) (and thereby the content item(s)) and the device(s) of a given domain together (and thereby forming the domain) is obtained.
If a specific device (e.g. device D3) wants to access a certain piece of content (e.g. content C1) it has to be proved or checked, etc. (using the certificates) that the certain piece of content is coupled to a specific person (e.g. person P1) that is a member of the same domain (100) as the specific device. This may, for example, be done by checking that an (unique) identifier of the specific device (e.g. device D3) is part of the DDC, that an (unique) identifier of the specific person (e.g. person P1) is part of the DUC, that both the DDC and DUC comprises the same Domain Identifier (e.g. Domain_ID=4 or Domain_ID=8 byte value (e.g. generated randomly); not shown), and that the URC for the specific person (e.g. URC1) specifies that the specific person has the right to access the certain piece of content (e.g. if it is within the validity period of his license or has not been used more than three times, etc.). This will be illustrated in greater detail in connection with
By having the content items coupled to persons (via URCs) the ownership of content is easily reflected. Additionally, it is easier to administer a split of the AD, since by splitting the persons the appropriate content items is also split, since the content items are linked to persons.
Hereby, one or more devices, one or more persons, and at least one content item (via a person) are linked together in the domain preferably with the use of certificates or alternatively with the use of lists comprising the same described elements as for the certificates. It may be possible for the domain to comprise zero persons and/or zero devices and/or zero content items during some points. For example, when initially building the domain it may comprise zero content items or zero devices bound to the domain, etc.
In this way, a user that has been verified as belonging to the same domain as the content item being accessed may access the specific content using any device. Additionally, a user that is using a device that has been verified as belonging to the same domain as the content item being accessed may access the specific content using that specific device. Further all users may access the specific content item on that specific device.
This gives enhanced flexibility for one or more users when accessing content in an AD while security of the content is still maintaining.
In an alternative embodiment, the content may be bound to the devices of the domain instead of to the persons of the domain. Instead of a User Right Certificate a Device Right Certificate (DevRC) (not shown) is used. The Device Right Certificate (DevRC) would then have the same content as the URC with the exception of a Device ID instead of a Person ID. The rest is unchanged.
It is also to be understood that instead of having one list or certificate comprising users (i.e. the DUC) and one list or certificate comprising devices (i.e. DDC) above and in the following other arrangements may also be used. As an alternative, both devices and users could be comprised in a single list/certificate. Further, several lists/certificates comprising devices and/or several lists/certificates comprising users and/or combinations thereof may be used just as well.
If a specific device (e.g. device D3), in this embodiment, wants to access a certain piece of content (e.g. content C1) it has to be proved or checked, etc. (using the certificates) that the certain piece of content is coupled to the same domain (100) as the specific device or that a specific person (e.g. person P1) operating the device is a member of the domain. This may in this embodiment, for example, be done by checking that an (unique) identifier of the specific device is part of the DDC or that an (unique) identifier of the specific person is part of the DUC. Further it should be checked that the certain piece of content is coupled to a DRC that is part of the domain and that the DDC or the DUC comprises the same Domain Identifier, and that the DRC for the specific content specifies that a person of the domain has the right to access the certain piece of content (e.g. if it is within the validity period of a license or it has not been used more than three times). Hereby access to a content item is given either via a compliant device of the domain or via a valid person id. This will be illustrated in greater detail in connection with
Certificates according to the present invention (DDC, DUC, etc.) could, for example, be implemented by the well-known SPKI authorization certificate. Additionally, one useful option is to put a Domain_ID in a holder field of such a SPKI certificate implementing the DDC, the DUC and/or the DRC.
The Domain Users Certificate (DUC) comprises a listing of unique identifiers (Pers_ID1, Pers_ID2, . . . ) for one or more users/persons belonging to the given domain, i.e. being authorized users in the domain. The given domain that the listed users are authorized within is specified by the value of the Domain ID like described above for the Domain Devices Certificate (DDC). A Domain Users Certificate (DUC) and a Domain Devices Certificate (DDC) is linked by having the same value of the Domain ID and thereby defines the authorized domain (comprising both devices and users).
a illustrates an exemplary (partial) data structure of a content container, a content right (CR) and a user right certificate (URC) according to the embodiment of the present invention shown in
Also shown is a content right (CR) (502) comprising a content identifier (Cont_ID) and a content encryption key (Cont Encr K). The content identifier is used to establish a link to the encrypted content item (in a content container) that the content encryption key is for, i.e. the content that the key is needed to de-crypt and thereby enable access to. In this particular embodiment, the encryption key is a symmetrical key, i.e. the same key is used to both encrypt and decrypt data. Alternatively, other secure schemes may be used.
Further shown is a user right (UR) or User Right Certificate (URC) (503). The URC comprises a content identifier (Cont_ID) used for linking a specific content item (and content right) with a specific URC. The URC also comprises a person/user identifier (Pers_ID) that indicates which person the specific content is bound to. The person/user identifier could for example, be an ID or serial number for a given person, a name, a hash value of a public key of the user or in general any unique identifier of a person.
Further, the URC comprises rights data (Rghts Dat) that define what the given user (as identified by the Pers_ID) is allowed to do in relation with the specific content item (contained in the content container comprising the same Cont_ID). These rights data may, for example, specify play rights (e.g. restricted to viewers 18 years or older, or European market only, etc.), one-generation copy rights, a validity period, not used more than three times etc. Further, the rights data (Rghts Dat) may also define what all users are allowed to do in relation with the specific content item (which may be the same or different than the rights of the person identified by Pers_ID).
As an example, the well-known SPKI authorization certificate could be used to implement such a URC.
In the embodiment, where content is linked via devices to the domain instead of via persons, no URC would be needed, but a Device Right Certificate, that would be the same as the URC except that it contains a Device ID instead of a Person ID.
To illustrate the use of a content container, a content right (CR) and a user right certificate (URC) according to this embodiment of the present invention consider the following simple example illustrating access to a content item by a user.
The content identifier (Cont_ID) for the given content item that the user wants to access and the person identifier (Pers_ID) of the user are obtained. The person identifier may, for example, be obtained on the basis of a personalized identification device (e.g. a smart card, mobile phone, a mobile phone containing a smartcard, a biometric sensor, etc. or in another way). The content identifier may, for example, be obtained on the basis of a file name, the selection of a file, from a header of the content container, etc.
It is checked if the content item and the user belong to the (same) Authorized Domain. Checking whether a user belongs to a domain is done by checking if the person identifier (Pers_ID) is comprised in a Domain Users Certificate (DUC) (shown in
Then it is checked whether the given content item also belongs to the same domain, by checking if the content identifier of the content item is bound to a person bound to the same domain, i.e. by checking whether there exist a URC bound to the domain that comprises the same content identifier. If so, then the content item belongs to the same domain and the user (given that the user and/or the device that is used have been verified) therefore has the right to access it. Further, the rights data (Rghts Dat) of the URC may also specify a restricted access to the content item. The rights data may specify rules, rights, conditions for the person identified with Pers_ID and/or rules, rights, conditions in general. For example, it could specify that that every user in the domain has play rights while the user linked via Pers_ID in addition has exclusive first generation copy rights.
Usually, the user will obtain access to the content item using a specific device. If the user is not part of the domain or no valid user ID can be obtained (e.g. because it is a friend accessing the content), then it has to be checked whether the specific device that the user is using to access the content item is part of the same domain as the content item in order to allow the user to access the content item, since he is not (or it can not be established that he is) part of the same domain as the content item. This is done by obtaining the Domain_ID of the DUC that the content item (via a person) was bound to. This Domain_ID is used to determine a Domain Devices Certificate (DDC) (shown in
These three steps of validating access to the content item, the user and the device may alternatively be done in another order than the one described and e.g. also in parallel at least to a certain extent.
After it has been verified that the user or the device is part of the same domain as the content, then the obtained content identifier is used to locate the content right (CR) of the specific content item being accessed in order to obtain the cryptographic key that has to be used to decrypt the encrypted content item. Further, the content container comprising the encrypted content item is also located using the content identifier.
Finally, the key in the content right is used to decrypt the content item which is now accessible, e.g. for rendering, copying on an optical disk, editing, etc. Alternatively, the content item may also be decrypted using the content right before sending it to the device for access, whereby only the content item needs to be transmitted. However, this requires special measures in order to protect the content item during transfer so that it is not possible to ‘leak’ the unprotected content.
This process is illustrated in
In this way, if a specific user that has been verified as belonging to the same domain as the content item being accessed then there is, as mentioned, no need for checking whether the device he is using also belongs to the same domain. Further, the validated user may access the specific content item using all devices. Likewise, if a specific device has been verified as belonging to the same domain, then all users may access the specific content item using that specific device and there is no need to verify the user.
Therefore, enhanced flexibility for one or more users when accessing content in an AD is obtained while security of the content is still maintaining.
b illustrates an exemplary (partial) data structure of a content container, a content right (CR) and a Domain Rights Certificate (DRC) according to the embodiment of the present invention shown in
Further shown is a Domain Rights Certificate (504) that comprises a content identifier (Cont_D) used for linking a specific content item (and content right) with a specific DRC. The DRC also comprises a domain identifier (Domain_ID) that indicates which domain the specific content is bound to. The domain identifier corresponds to the one in the Domain Devices Certificate (DDC) and the Domain Users Certificate (DUC) explained in connection with
Further, the DRC (504) comprises rights data (Rghts Dat) that define what one or more users are allowed to do in relation with the specific content item (contained in the content container comprising the same Cont_ID). These rights data correspond to the rights data of the URC explained in connection with
To illustrate the use of a content container, a content right and a domain rights certificate according to this embodiment of the present invention consider the following simple example illustrating access on a specific device to a content item by a user.
The content identifier (Cont_ID) for the given content item that the user wants to access, the person identifier (Pers_ID) of the user, and the domain identifier (Domain_ID) of the domain containing the content item are obtained. The content identifier and the person identifier may be obtained as described in connection with
It is checked if the content item and the user belong to the (same) Authorized Domain. Checking whether a user belongs to a domain is done by checking if the person identifier (Pers_ID) is comprised in a Domain Users Certificate (DUC) (as shown in
Then it is checked whether the given content item also belongs to the same domain, by checking if the content identifier of the content item is bound to the same domain, i.e. by checking whether there exist a DRC bound to the domain that comprises the same content identifier. If so, then the content item belongs to the same domain and the user (given that the user and/or the device that is used have been verified) therefore has the right to access it. Further, the rights data (Rghts Dat) of the DRC may also specify a restricted access to the content item, as described in connection with
Usually, the user will obtain access to the content item using a specific device. If the user is not part of the domain or no valid user ID can be obtained (e.g. because it is a friend accessing the content), then it has to be checked whether the specific device that the user is using to access the content item is part of the same domain as the content item in order to allow the user to access the content item, since he is not (or it can be established that he is) part of the same domain. This is done by obtaining the Domain_ID of the DRC that the content was bound to. This Domain_ID is used to determine a Domain Devices Certificate (DDC) (shown in
These three steps of validating access to the content item, the user and the device may alternatively be done in another order than the one described and e.g. also in parallel at least to a certain extent.
After it has been verified that the user, the content and the device is part of the same domain, then the content item is accessed as described in connection with
This process is illustrated in
In one exemplary scenario, an Authorized Domain (100) has the television set (504), the digital video (503), the music set (502) and the user (505) bound to it in addition to a number of content items (not shown) (bound according to
In this scenario, the user wants to access a given content item on the portable device (507). He may be located in the same place as the devices or at another place (e.g. in a hotel room). For a user to obtain access to the content item according to the invention, it has to be checked that the person (505) belongs to the domain (100) since the portable device (507) does not. This may be done by uniquely identifying the user e.g. using a smart card reader in the portable device (507), which then may transfer the User ID to the network (101). The content right and the content item is assumed to be on the portable device (507) (otherwise it may be transmitted there). The user is then checked as described in connection with
In another exemplary scenario, an Authorized Domain (100) has the television set (504), the digital video (503), the music set (502) and the portable device (507) bound to it in addition to a number of content items (not shown) (bound according to
For a user to obtain access to the content item according to the invention, it has to be checked that the portable device (507) belongs to the domain (100) since the person (505) does not.
This may be done by checking if the portable device (507) is bound to the same domain as the content item as described in connection with
In the claims, any reference signs placed between parentheses shall not be constructed as limiting the claim. The word “comprising” does not exclude the presence of elements or steps other than those listed in a claim. The word “a” or “an” preceding an element does not exclude the presence of a plurality of such elements.
The invention can be implemented by means of hardware comprising several distinct elements, and by means of a suitably programmed computer. In the device claim enumerating several means, several of these means can be embodied by one and the same item of hardware. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage.
| Number | Date | Country | Kind |
|---|---|---|---|
| 03102281 | Jul 2003 | EP | regional |
| Filing Document | Filing Date | Country | Kind | 371c Date |
|---|---|---|---|---|
| PCT/IB2004/051226 | 7/14/2004 | WO | 00 | 1/23/2006 |
| Publishing Document | Publishing Date | Country | Kind |
|---|---|---|---|
| WO2005/010879 | 2/3/2005 | WO | A |
| Number | Name | Date | Kind |
|---|---|---|---|
| 6223291 | Puhl et al. | Apr 2001 | B1 |
| 6324645 | Andrews et al. | Nov 2001 | B1 |
| 6460023 | Bean et al. | Oct 2002 | B1 |
| 6463534 | Geiger et al. | Oct 2002 | B1 |
| 6880007 | Gardos et al. | Apr 2005 | B1 |
| 7047560 | Fishman et al. | May 2006 | B2 |
| 7194543 | Robertson et al. | Mar 2007 | B2 |
| 20010039624 | Kellum | Nov 2001 | A1 |
| 20020031230 | Sweet et al. | Mar 2002 | A1 |
| 20020040439 | Kellum | Apr 2002 | A1 |
| 20020062451 | Scheidt et al. | May 2002 | A1 |
| 20020073308 | Benantar | Jun 2002 | A1 |
| 20020144108 | Benantar | Oct 2002 | A1 |
| 20020144119 | Benantar | Oct 2002 | A1 |
| 20020146237 | Safadi | Oct 2002 | A1 |
| 20020157002 | Messerges et al. | Oct 2002 | A1 |
| 20030018491 | Nakahara et al. | Jan 2003 | A1 |
| 20030076955 | Alve et al. | Apr 2003 | A1 |
| 20030126431 | Beattie et al. | Jul 2003 | A1 |
| 20030144894 | Robertson et al. | Jul 2003 | A1 |
| 20030177376 | Arce Velleggia et al. | Sep 2003 | A1 |
| 20040025020 | Yoshimura et al. | Feb 2004 | A1 |
| 20040059941 | Hardman et al. | Mar 2004 | A1 |
| 20040078573 | Matsuyama | Apr 2004 | A1 |
| 20040083306 | Gloe | Apr 2004 | A1 |
| 20040088543 | Garg et al. | May 2004 | A1 |
| 20040098615 | Mowers et al. | May 2004 | A1 |
| 20050022227 | Shen et al. | Jan 2005 | A1 |
| 20060106836 | Masugi et al. | May 2006 | A1 |
| 20080010365 | Schneider | Jan 2008 | A1 |
| Number | Date | Country |
|---|---|---|
| 2003131751 | May 2003 | JP |
| 2003178163 | Jun 2003 | JP |
| 2004062870 | Feb 2004 | JP |
| 2004139473 | May 2004 | JP |
| 2007531102 | Nov 2007 | JP |
| 02067449 | Aug 2002 | WO |
| 02067449 | Aug 2002 | WO |
| 03009112 | Jan 2003 | WO |
| 03034408 | Apr 2003 | WO |
| 03039155 | May 2003 | WO |
| 03039155 | May 2003 | WO |
| 03047204 | Jun 2003 | WO |
| 03098931 | Nov 2003 | WO |
| 2004038568 | May 2004 | WO |
| 2005093544 | Oct 2005 | WO |
| Entry |
|---|
| Van Den Heuvel et al, “Secure Content Management in Authorised Domains”, International Broadcasting Convention, XP002273504, Sep. 15, 2002, pp. 1-8. |
| Number | Date | Country | |
|---|---|---|---|
| 20060190621 A1 | Aug 2006 | US |
