JP2006244180A - Method for signaling protecting module - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a method for signaling a protecting module. <P>SOLUTION: A manufacturer ID is defined and placed in tool container, to indicate that DRM module carried in tool container is used for certain manufacturer's terminal, so that only the matched terminal will download and retrieve the DRM module. The detailed format of tool container is also defined for terminal to retrieve manufacturer ID and the corresponding DRM module in the right place. The detail format of rights container is defined to indicate which right express language is used and what format it is as well as usage rule itself. The DRM signaling for protection information in MPEG-2 system layer can also be declared in file format level or in SDP to support different applications. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a protection field for multimedia content. The present invention more particularly relates to a method for signaling protection modules used in various systems and terminals.

  An essential requirement for developing a thriving digital media market is the protection of copyright-protected content in digital form. Digital rights management (DRM) is a technology developed to prevent unauthorized distribution of copyright-protected digital content. It is very difficult to define a simple DRM system that is open and interoperable. This is one of the reasons why so many proprietary DRM systems exist in the current market, which is an obstacle to the formation of a horizontal market for the distribution, transmission and consumption of universal media content. It has become.

  The DRM field is very complex because it includes different investors, content providers / distributors, intermediaries, terminals and users from different consumer electronics (CE) manufacturers. The final interoperable end-to-end DRM system must consider all of these benefits and ultimately must be reasonably balanced.

  One balance is flexibility versus complexity. On the one hand, content providers tend to use different protection tools to protect content with different market values, while CE manufacturers support different tools for the same service on their hardware. Feels difficult.

  Another balance is updatability versus complexity. For security reasons, the DRM system must handle the protection tool once it has been broken and enable the revocation method, however, such updateability requires that the terminal It is necessary to have a certain function to support this, which increases hardware complexity.

In the prior art [Patent Document 1, Non-Patent Document 1], the moving picture coding expert group (MPEG) defined MPEG-2 based on the IPMP (Intellectual Property Management and Protection) system. Great attention is paid to flexibility and updatability by using a tool list that defines tool IDs and indicates what tools are needed and used in related media protection. Once certain tools need to be replaced, new tools are downloaded and searched. In addition, a rights container is defined to carry rights and usage rules related to the license in the PSI (Program Service Information) of the MPEG-2 system, and a tool container is defined to be missing for updatability. Transports existing or replacement tools. When such an IPMP scheme was then defined in MPEG, flexibility and updatability were the main focus. MPEG-2 IPMP protection scheme signaling is strictly based on the hierarchical encoding of the MPEG-2 system, and the syntactic and semantic rules imposed on this encoding can be decoded over a wide range of search or reception conditions. Provides information that allows synchronized decoding in the device buffer.
International Application PCT / JP02 / 08780 pamphlet (filed Aug. 30, 2002, Ji Ming, Shen Shengmei, Huang Zhongyang and Senoh Taka) "Apparatus of a flexible and common IPMP system for MPEG-2 content distribution and protection") [1] ISO / IEC 13818-11 Final International Standard Draft, IPMP Extensions on MPEG-2 System (IPMP extensions on MPEG-2 systems), March 2003 (N5608)

  The above prior art has the following problems.

  Terminals with the MPEG-2 IPMP framework are implemented in different ways for each CE manufacturer, and typically tamper resistant system (TRS) technology is also used in different ways to make important programs and DRMs at the terminal. Protect tools.

  Once a DRM tool needs to be changed, all DRM modules including some DRM tools and other programs must be replaced. This is because a newly replaced DRM tool may not work with others due to TRS differences.

  Secondly, each manufacturer may have its own specific implementation of this DRM module to be compatible with the OS (operating system), middleware and other interfaces at that terminal. There is no single and common DRM module used by all terminals manufactured by different manufacturers.

  Therefore, it is necessary to confirm the source and destination of the DRM module that is to be loaded into the terminal.

  Another problem is that the rights container is just a container as defined in the prior art. If the data in the container and its format are not defined and various data in different formats are placed in the content packaging, the terminal will not be able to understand the rights. Therefore, the terminal manufacturer must provide a corresponding rights parser and management tool to the terminal depending on the third party supplying the rights data to the container. The vertical market situation similar to conventional CA (Conditional Access) must be resolved by clearly defining usage rules in the rights container. The same applies to tool containers, and their syntax and semantics must be clearly defined.

  Further, media data protection should support various methods for distribution to consumers, in which case systems other than MPEG-2 systems are used for distribution. For example, popular and deliberately standardized media file formats, such as the ISO base file format from which other commonly used file formats are derived, provide a means for storing and distributing valuable multimedia. One.

  Multimedia streaming over IP (Internet Protocol) using RTP / UDP along with RTSP / SDP is also becoming increasingly popular in the current Internet era, but SDP uses any transport protocol for its transmission. Even when used, it can carry rich attributes for session level description and media level description and can be used to support such consumption. In the present invention, the inventors also aim to solve the signaling problem of flexible DRM protection with rights expressions within such popular file formats or multimedia streaming environments.

  The present invention uses an affordable and practical approach for improvement over the prior art.

  Introducing the manufacturer ID and placing it in the tool container, indicating that the DRM module carried in the tool container is used for a certain manufacturer's terminal, so that only the matching terminal downloads and searches the DRM module To.

  Define the detailed format of the rights container and indicate which rights expression language is used and what format (XML or binary) as well as the usage rules themselves.

  The detailed format of the tool container is also defined so that the terminal searches for the manufacturer ID and the corresponding DRM module in the rights place.

  The above signaling information is not only applicable in MPEG-2 system based on usage, but also applicable to file formats based on content distribution and streaming over IP (Internet Protocol) such as RTP / SDP It is.

  The present invention provides a practical and useful approach for DRM systems, particularly DRM solutions related to MPEG-2 systems, and updates that DRM module or DRM tool via a tool container. The present invention also facilitates using different rights expression languages in the same DRM system, and using both XML and binary formats to express usage rules. At the same time, the signaling information disclosed in the present invention can be carried in a media file or streaming protocol as well.

  Preferred embodiments of the present invention will be described below with reference to the accompanying drawings.

  FIG. 1 shows the MPEG-2 IPMP framework architecture, and FIG. 2 shows the structure of protected content using MPEG-2 IPMP. The tool list 105, the tool container 106, and the rights container 107 are included in the IPMP control information table 104 that is a part of the PSI 103 (program specific information). The IPMP stream 102 arrives as a multiplexed elementary stream in the MPEG-2 transport or program stream 101. Received content is demultiplexed by the MPEG-2 system demultiplexer. Audio and video bitstreams are fed into a decoding buffer (DB), which is then decoded and rendered. By embedding the IPMP descriptor 109 in the program map table (PMT) 108 in the transport stream and associating the IPMP tool with each individual stream under its protection, the IPMP control graph provides an explanation of the entire IPMP protection scheme.

  One or more binary representations of the IPMP tool may be carried directly in the IPMP control information as the payload of the IPMPToolContainer class to replace the broken IPMP tool. The representation format, package information, and IPMP tool ID may also be specified in the IPMPToolContainer class 301 shown in FIG. The usage rule can be carried in the IPMP control information as a payload of the IPMP_Rights_Container class 302 shown in FIG.

  The IPMP tool is a DRM module that executes IPMP functions such as authentication, decryption, and watermarking. A given IPMP (DRM) tool may work in conjunction with other IPMP (DRM) tools. Each IPMP tool has a unique IPMP tool ID for identifying the tool in an obvious way at the presentation level or universal level. For robustness, IPMP provides updatability, which prevents security failures. For flexibility, IPMP allows the use of various IPMP tools including cryptographic tools.

  However, in real hardware implementations, the flexibility or tool level updatability of such DRM tools is not practical. For example, a crypto engine (as one independent DRM tool) cannot be downloaded directly. The DRM tool can only be downloaded if the DRM tool does not contain a cipher or calls a cipher embedded in the LSI. Furthermore, at this stage, multiple TRS cannot coexist in one LSI design. That is, the meaning is that different TRSs cannot be run at the same time, i.e. downloaded DRM tools can only be run if they were created with the same TRS. Therefore, if one DRM tool breaks, a better way to take is to download all DRM modules, including several DRM tools or other programs. This is because a single replaced DRM tool may not work with others. As another example, each manufacturer may have its own specific implementation of the DRM module that is compatible with the OS, middleware and other interfaces at the terminal. There is no single and common DRM module used by all terminals.

  As shown in FIG. 4, in the present invention, the information in the tool container 401 is improved to not only carry the DRM module body 405 itself, but also “1” indicating that there is a DRM update or there is no DRM update. A flag 402, which is either “0” indicating that, a manufacturer ID 403 representing the identifier of the actual DRM module manufacturer, and supplemental and detailed information for the download process of such a DRM module, such as the syntax shown in FIG. As found in the table, Reboot, Add_on, Download_id, preferred receive Device_No. Group / Domain No. Or Module version No. A description 404 that may include, for example, is also carried. All this information provides the necessary means to identify the source and destination of certain DRM module loading.

  In any DRM system, the rights and usage rules associated with a license are important information for implementing actual media consumption. As shown in FIG. 5, in the present invention, the information in the rights container 501 is improved not only to carry the usage rule body 504 itself, but also to the actual rights expression language used in the DRM system (eg, based on XrML). It also carries a REL_ID 503 that identifies OMA DRM REL) based on MPEG-21 REL or ODRL, and a language_format 502 that identifies the REL format (binary or XML) that is actually carried. The detailed syntax for this information is fully defined in the syntax table shown in FIG.

  When the content stream is transmitted to the user via the MPEG-2 system shown in FIG. 6, the DRM tool container 401 and the rights container 501 described above together with other necessary DRM protection signaling information 602 are MPEG-2. It is carried in program specific information (PSI) 601 in the system stream.

  If the content is stored in a file format shape and sent to the end user or streamed through other transport protocols other than the MPEG-2 system, such DRM protection signaling such as DRM tool container and rights container Information should be declared in such file or session descriptions to protect the associated media content.

  One example relates to an ISO-based file format that is formed as a series of objects called boxes. All data is contained in a box and there is no other data in the file. The DRM signaling information (protection information) is stored in the protection information box 901 in the sample table box 902 associated with the DRM protected media sample in the movie level track as shown in FIG. 9, or in the metadata as shown in FIG. Carried in one clearly defined box, such as in an XML box 1001, which is in a (binary) XML box 1002 associated with DRM protected data at the description level, signaling protection.

  The protection information is a kind of control information that is related to DRM module download or usage rule search and is applied to media data in a file. Such protection control information can also be placed directly in the front of the file, eg, in the IPMP control box 903 of FIG. 9 at the movie level, or 1003 of FIG. 10 at the metadata description level.

  Another example is to use RTSP / SDP (Session Description Protocol) for streaming applications. Some additional SDP attributes should be defined to carry DRM signaling information. The defined DRM-related attributes should be mandatory so that the terminal can find the right place and download and retrieve the protection information.

  FIG. 11 shows that the above-mentioned DRM tool container 401 and rights container 501 can be transported in the SDP (Session Description Protocol) special attribute 1101 in the case of Internet streaming together with other necessary DRM protection signaling information 1102.

  FIG. 12 shows that the above DRM tool container 401 and rights container 501 can be placed on a server, eg, rights server 1201, along with other necessary DRM protection signaling information 1202.

  In FIG. 13, a content server 1301 transmits a content stream including protected content and corresponding protected information, and these content and information are transmitted to terminals via channels A and B, for example. Indicates.

  The protection information includes a tool container or a rights container, which includes DRM module download related information 1302 and rights related information 1303, respectively.

  The terminal 1304 receives the information 1302 and 1303, releases the protection of the content according to such information, and then consumes the content.

  In FIG. 14, the streaming server 1401 transmits protected content, and the corresponding protected information is retrieved or transmitted from a different channel or certain URL, such as SDP, and both the protected content and the protected information Indicates that terminal 1404 is reached via channels A and B.

  The protection information includes a tool container including DRM download related information 1402 and a rights container including usage rule related information 1403.

  The terminal 1404 receives the above information in 1402 and 1403, releases the protection of the content according to such information, and then consumes the content.

  FIG. 15 provides an executable flowchart regarding how the terminal retrieves and processes the protection information.

  In 1501, the terminal searches for protection information from a content stream, a file, an SDP session, or a URL.

  At 1502 and 1503, the terminal discovers the location of the tool container and rights container, respectively.

  At 1504, the terminal extracts the flag in the tool container and, at 1506, determines whether a subsequent step related to DRM module download is required.

  If the flag is zero, the following step is skipped at 1508, informing you that there are no new DRM modules that need to be downloaded. This is almost always the case.

  If the flag is set to 1, the terminal 1509 extracts the next parameter that is the manufacturer ID (maker identifier), and the terminal 1511 assigns this manufacturer ID to the ID (identifier) assigned to the terminal. To determine whether the transported DRM module is for that terminal. If not for that terminal, the DRM module download step is omitted at 1512 of the terminal. Otherwise, the terminal 1513 continues to check and download the description regarding the download process. Here, the pre-stored assigned ID can be searched from the terminal, can be searched from another device attached to the terminal, or can be keyed by a user pre-assigned to the terminal. . This depends on the capabilities of the terminal and user convenience.

  The terminal 1505 extracts the language format and REL_ID from the rights container, and the terminal 1507 downloads the usage rule. The terminal 1510 calls the corresponding REL parser to interpret the downloaded usage rules. Here, the usage rule may include copyright information.

  Finally, at the terminal 1514, the downloaded DRM module and the content protected using the downloaded and interpreted usage rules can be consumed.

  The invention is particularly applicable to the field of digital media applications used to signal a protection module that manages the production, distribution and consumption of digital media.

1 is a block diagram showing an MPEG-2 IPMP architecture. The block diagram which shows the content structure of MPEG-2 IPMP in FIG. Explanatory drawing which shows the syntax table of IPMPToolContainer and IPMP_Rights_Container. Explanatory drawing which shows the format of the newly proposed information conveyed with a tool container. Explanatory drawing which shows the format of the newly proposed information conveyed with a rights container. Explanatory drawing which shows the format of the information conveyed by MPEG-2 PSI. FIG. 5 is an explanatory diagram showing a syntax table of the newly proposed DRM tool container in FIG. 4. Explanatory drawing which shows the syntax table of the newly proposed rights container of FIG. Explanatory drawing which shows that protection information is arrange | positioned at the movie box of a file. Explanatory drawing which shows that protection information is arrange | positioned at the meta box of a file. Explanatory drawing which shows that protection information is searched from an SDP attribute session. Explanatory drawing which shows that protection information is searched from a server. Schematic which shows that a terminal searches the protection information transmitted from a content server with the protected content. Schematic which shows that a terminal searches the protection information searched from SDP and a server via the channel different from content transmission. 6 is a flowchart showing how a terminal retrieves and extracts protection information and further the download process.

Explanation of symbols

101 MPEG-2 transport or program stream 102 IPMP stream 103 PSI (program specific information)
104 IPMP control information table 105 Tool list 106 Tool container 107 Rights container 108 Program map table (PMT)
109 IPMP descriptor 301 IPMPToolContainer class 302 IPMP_Rights_Container class 401 Tool container 402 Flag 403 Manufacturer ID
404 Description 405 DRM module body 501 Rights container 502 Language_format 503 REL_ID
504 Usage rule body 601 Program specific information (PSI)
602 Other required DRM protection signaling information 901 Protection information box 902 Sample table box 903 IPMP control box 1001 XML box 1002 (binary) XML box 1003 IPMP control box 1101 SDP (session description protocol) special attribute 1102 Other required DRM protection Signaling information 1201 Rights server 1202 Other necessary DRM protection signaling information 1301 Content server 1302 DRM module download related information 1303 Rights related information 1304 Terminal 1401 Streaming server 1402 DRM download related information 1403 Usage rule related information 1404 Terminal

Claims (35)

Carrying protection information in a system stream including an MPEG-2 system to indicate protection details including protection modules, download information, usage rules and copyright information, and their corresponding formats;
Carrying a manufacturer identification associated with a DRM module for generating a location in said protection information and downloading in case of update;
A method for signaling a protection module, comprising: Defining a tool container for a DRM module to be transferred and downloaded to the terminal via any available network;
Defining a rights container for usage rules and copyright information that is transferred and retrieved and interpreted by the device;
The method for signaling a protection module according to claim 1, further comprising: Tool container
Using a flag to indicate whether there is a new DRM module carried for update;
Embedding a manufacturer identifier associated with the DRM module;
Describing the DRM module download process;
Transporting the DRM module itself in the tool container;
The method for signaling a protection module according to claim 2, further comprising: The rights container
Indicating whether XML or binary format is used for the usage rules and copyright information;
Embedding a rights expression language (REL) identifier to indicate what kind of REL is used to describe the corresponding usage rule and copyright information;
Conveying the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 2, further comprising: The device
Retrieving protection information from a content stream including an MPEG-2 system stream and obtaining the protection information by the terminal;
The transported DRM module verifies whether the terminal is intended to be downloaded by a certain means;
A method for signaling a protection module, comprising: The device
Retrieving the information in the tool container that is part of the protection information;
Retrieving the information in the rights container that is part of the protection information;
The method for signaling a protection module according to claim 5, further comprising: The terminal searching for information from the tool container;
Searching for a flag to be transported at the front of the tool container and checking if there is a DRM module transported for download; if not, skip the following steps;
Otherwise, search for a manufacturer identifier and check if the identifier matches that assigned to the terminal, and if not, skip the following steps;
Otherwise, retrieving the description regarding the DRM module download process and taking action according to the description;
Retrieving the DRM module carried in the tool container and replacing it with an old DRM module;
The method for signaling a protection module according to claim 6, further comprising: The terminal retrieving information from the rights container
Searching a language format flag to determine whether the usage rule and copyright information is in XML or binary format;
Retrieving the REL identifier and calling a corresponding REL parser to prepare to interpret the conveyed usage rules and copyright information;
Retrieving the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 6, further comprising: Carrying protection information in a file of a certain file format and showing protection details including protection modules, download information, usage rules and copyright information, and their corresponding formats;
Carrying a manufacturer identification associated with a DRM module for generating a location in said protection information and downloading in case of update;
A method for signaling a protection module, comprising: Defining a tool container for a DRM module to be transferred and downloaded to the terminal via any available network;
Defining a rights container for usage rules and copyright information that is transferred and retrieved and interpreted by the device;
The method for signaling a protection module according to claim 9 further comprising: Tool container
Using a flag to indicate whether there is a new DRM module carried for update;
Embedding a manufacturer identifier associated with the DRM module;
Describing the DRM module download process;
Transporting the DRM module itself in the tool container;
The method for signaling a protection module according to claim 10, further comprising: The rights container
Indicating whether XML or binary format is used for the usage rules and copyright information;
Embedding a rights expression language (REL) identifier to indicate what kind of REL is used to describe the corresponding usage rule and copyright information;
Conveying the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 10, further comprising: The device
Retrieving protection information from the file in a certain file format and obtaining the protection information by the terminal;
The transported DRM module verifies whether the terminal is intended to be downloaded by a certain means;
A method for signaling a protection module, comprising: The device
Retrieving the information in the tool container that is part of the protection information;
Retrieving the information in the rights container that is part of the protection information;
14. The method for signaling a protection module according to claim 13, further comprising: The terminal searching for information from the tool container;
Searching for a flag to be transported at the front of the tool container and checking if there is a DRM module transported for download; if not, skip the following steps;
Otherwise, search for a manufacturer identifier and check if the identifier matches that assigned to the terminal, and if not, skip the following steps;
Otherwise, retrieving the description regarding the DRM module download process and taking action according to the description;
Retrieving the DRM module carried in the tool container and replacing it with an old DRM module;
15. A method for signaling a protection module according to claim 14, further comprising: The terminal retrieving information from the rights container
Searching a language format flag to determine whether the usage rule and copyright information is in XML or binary format;
Retrieving the REL identifier and calling a corresponding REL parser to prepare to interpret the conveyed usage rules and copyright information;
Retrieving the usage rules and copyright information in the format according to the REL;
15. A method for signaling a protection module according to claim 14, further comprising: Protection information that can be transmitted via SDP (Session Description Protocol), which is one of the Internet Protocol (IP), protection including protection module, download information, usage rules and copyright information, and their corresponding formats Steps showing the details of
Carrying a manufacturer identification associated with a DRM module for generating a location in said protection information and downloading in case of update;
A method for signaling a protection module, comprising: Defining a tool container for a DRM module to be transferred and downloaded to the terminal via any available network;
Defining a rights container for usage rules and copyright information that is transferred and retrieved and interpreted by the device;
The method for signaling a protection module according to claim 17, further comprising: Tool container
Using a flag to indicate whether there is a new DRM module carried for update;
Embedding a manufacturer identifier associated with the DRM module;
Describing the DRM module download process;
Transporting the DRM module itself in the tool container;
The method for signaling a protection module according to claim 18 further comprising: The rights container
Indicating whether XML or binary format is used for the usage rules and copyright information;
Embedding a rights expression language (REL) identifier to indicate what kind of REL is used to describe the corresponding usage rule and copyright information;
Conveying the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 18 further comprising: The device
Retrieving protection information from the SDP via IP and obtaining the protection information by the terminal;
The transported DRM module verifies whether the terminal is intended to be downloaded by a certain means;
A method for signaling a protection module, comprising: The device
Retrieving the information in the tool container that is part of the protection information;
Retrieving the information in the rights container that is part of the protection information;
The method for signaling a protection module according to claim 21, further comprising: The terminal searching for information from the tool container;
Searching for a flag to be transported at the front of the tool container and checking if there is a DRM module transported for download; if not, skip the following steps;
Otherwise, search for a manufacturer identifier and check if the identifier matches that assigned to the terminal, and if not, skip the following steps;
Otherwise, retrieving the description regarding the DRM module download process and taking action according to the description;
Retrieving the DRM module carried in the tool container and replacing it with an old DRM module;
The method for signaling a protection module according to claim 22, further comprising: The terminal retrieving information from the rights container
Searching a language format flag to determine whether the usage rule and copyright information is in XML or binary format;
Retrieving the REL identifier and calling a corresponding REL parser to prepare to interpret the conveyed usage rules and copyright information;
Retrieving the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 22, further comprising: Details of protection, including rights server, carrying protection information that can be placed in a different location than the corresponding protected content, including protection modules, download information, usage rules and copyright information, and their corresponding formats Steps showing
Carrying a manufacturer identification associated with a DRM module for generating a location in said protection information and downloading in case of update;
A method for signaling a protection module, comprising: Defining a tool container for a DRM module to be transferred and downloaded to the terminal via any available network;
Defining a rights container for usage rules and copyright information that is transferred and retrieved and interpreted by the device;
The method for signaling a protection module according to claim 25, further comprising: Tool container
Using a flag to indicate whether there is a new DRM module carried for update;
Embedding a manufacturer identifier associated with the DRM module;
Describing the DRM module download process;
Transporting the DRM module itself in the tool container;
The method for signaling a protection module according to claim 26, further comprising: The rights container
Indicating whether XML or binary format is used for the usage rules and copyright information;
Embedding a rights expression language (REL) identifier to indicate what kind of REL is used to describe the corresponding usage rule and copyright information;
Conveying the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 26, further comprising: The device
Retrieving protection information from the location different from where the corresponding protected content exists, including a rights server, and obtaining the protection information by the terminal;
The transported DRM module verifies whether the terminal is intended to be downloaded by a certain means;
A method for signaling a protection module, comprising: The device
Retrieving the information in the tool container that is part of the protection information;
Retrieving the information in the rights container that is part of the protection information;
30. The method for signaling a protection module according to claim 29, further comprising: The terminal searching for information from the tool container;
Searching for a flag to be transported at the front of the tool container and checking if there is a DRM module transported for download; if not, skip the following steps;
Otherwise, search for a manufacturer identifier and check if the identifier matches that assigned to the terminal, and if not, skip the following steps;
Otherwise, retrieving the description regarding the DRM module download process and taking action according to the description;
Retrieving the DRM module carried in the tool container and replacing it with an old DRM module;
The method for signaling a protection module according to claim 30, further comprising: The terminal retrieving information from the rights container
Searching a language format flag to determine whether the usage rule and copyright information is in XML or binary format;
Retrieving the REL identifier and calling a corresponding REL parser to prepare to interpret the conveyed usage rules and copyright information;
Retrieving the usage rules and copyright information in the format according to the REL;
The method for signaling a protection module according to claim 30, further comprising: 32. Signaling protection module according to any one of claims 7, 15, 23 and 31, wherein a manufacturer identifier is retrieved and it is checked whether the identifier matches that assigned to the terminal. A method for
Retrieving the assigned ID previously stored in the terminal;
Comparing the manufacturer identifier retrieved from the tool container with the assigned ID retrieved from the terminal;
A method further comprising: 32. Signaling protection module according to any one of claims 7, 15, 23 and 31, wherein a manufacturer identifier is retrieved and it is checked whether the identifier matches that assigned to the terminal. A method for
Retrieving the assigned ID stored in advance in another device attached to the terminal;
Comparing the manufacturer identifier retrieved from the tool container with the assigned ID retrieved from the terminal;
A method further comprising: 32. Signaling protection module according to any one of claims 7, 15, 23 and 31, wherein a manufacturer identifier is retrieved and it is checked whether the identifier matches that assigned to the terminal. A method for
Keying in the assigned ID provided and assigned to the terminal;
Comparing the manufacturer identifier retrieved from the tool container with the assigned ID provided for the terminal;
A method further comprising:

Images