WO2004036435A1

WO2004036435A1 - System for managing digital item management information

Info

Publication number: WO2004036435A1
Application number: PCT/JP2003/013153
Authority: WO
Inventors: Ming Ji; Zhongyang Huang; Sheng Mei Shen; Takanori Senoh
Original assignee: Matsushita Electric Industrial Co., Ltd.
Priority date: 2002-10-15
Filing date: 2003-10-15
Publication date: 2004-04-29
Also published as: AU2003273001A1

Abstract

A system for managing digital item management information between first and second terminals that utilize digital items. The first terminal comprises management information producing means for producing information of management of digital items; management information recording means for recording the digital item management information; and transmitting means for transmitting a request for reservation of a region in which to record the digital item management information and also transmitting the digital item management information. The second terminal comprises management information recording means for recording the digital item management information; and receiving means for receiving the digital item management information.

Description

Specification

Digital item management information management system

The present invention relates to MPEG-21, and more particularly to exchanging information in different parts of an MPEG-21 system that require negotiation between different MPEG-21 peers.

Background art

Today, there are many factors to build an infrastructure for the delivery and consumption of multimedia content. However, there is no “big picture” to describe how these elements, either existing or in development, are interrelated. The purpose of MPEG-21 is to describe how these various elements fit together. Where gaps exist, MPEG-21 recommends which new standards are required. While other relevant standards may be developed by other bodies, MPEG will then develop new standards as appropriate. These specifications will be integrated into the multimedia framework through joint research between MPEG and these organizations.

MPEG-21 aims to set a vision for enabling transparent and augmented use of multimedia resources across a wide range of networks and devices used by different communities. Setting the big picture is describing how to specify all the elements that exist to build the infrastructure for the delivery and consumption of multimedia content. There are now six key technology elements: DID (Digital 'Item Declaration), DII & D (Digital Item Identification and Description), IPMP (Intellectual Property Management and Protection), RDD (Rights Data Dictionary), REL (Rights) Expression Language) and DIA (Digital Item Adaptation) are defined in MP EG-21.

Digital items are defined as structured digital objects, including standard representation and identification, and metadata. This entity collectively provides the basic distribution and transaction unit within the MPEG-21 framework. It is. IPMP (Intellectual Property Management and Protection) is a standardized framework for digital 'item protection. RDD / REL specifies expression languages and dictionaries that issue rights to users for acting on digital 'items, their components, fragments, and containers.

The transmission and negotiation of DIA (Digital 'Item Adaptation) descriptions, usage rights information, IPMP information (which may also include usage rights), and negotiations to enable content exchange between MPEG-21 compliant peers It should be defined in the MPEG-21 framework to provide operability. In addition, renewal mechanisms should be provided for DIA, IPMP or rights.

As shown in Figure 1, there are useful scenarios where information exchange is required. Examples include one-way broadcast applications to different terminals, interactive two-way applications for content adaptation, real-time 'streaming adaptation to different networks', and the like. In these cases, the DIA description for the terminal, network, user preferences, usage rights information, and IPMP information (which can be associated with content-specific usage rights) must be exchanged (1.1). Negotiations are made based on the above information as needed. Therefore, the interoperable negotiation mechanism and messages are used to transmit powerful information to terminals, servers, gateways, proxies (1.2, 1.3, 1.4, 1.5, 1.6, 1. 7) Should be defined to facilitate communication between peers, such as. By following the standardized negotiation mechanism defined here, a universal multimedia framework can be set up that can handle usage environments with different multimedia terminals, networks and content adaptation and exchange. Disclosure of the invention

Issues to be solved

The present invention seeks to solve the following problems.

IMPPP information, which may include tools' lists, tools ■ containers, and / or usage rights, can be exchanged, updated, and transmitted between multimedia terminals and peers, and various operating systems. Run on different physical machines with system And operates in a variety of security, application, and tool environments, but the negotiation is built on a high-level basis.

The usage right information can be exchanged in the same way as the above IPMP information, but can be sent individually.

MPEG—Other information defined in the 21 framework.

Regardless of the network 'protocol used by terminals and peers, negotiations between peers for IPMP information, usage rights information or other information achieve effective and seamless digital' item adaptation and exchange. It is performed individually using the IPMP information message and the usage right message defined for this purpose.

Means for solving the problem

In the management system of the management information of the digital item between the first terminal and the second terminal using the digital item according to the present invention,

The first terminal is

Management information generating means for generating management information of the digital item, management information recording means for recording the digital item management information,

Transmitting means for transmitting an area securing request for recording the digital item management information in the second terminal, and transmitting the digital item management information to the second terminal;

With

The second terminal is

Management information recording means for recording the digital item management information,

Receiving means for receiving the digital item management information;

It is characterized by having.

Further, in the case of using a digital item between the first terminal and the second terminal according to the present invention, the management method of the management information of the digital item in the first terminal,

Generating, at the first terminal, management information of the digital item; Recording the digital item management information in the first terminal; and requesting the second terminal to secure an area for recording the digital item management information from the first terminal to the second terminal. ,

Transmitting the digital item management information to the second terminal.

In addition, this digital item management information management system,

Detecting a change in the digital item management information in at least one of the first terminal and the second terminal;

Updating the digital item management information recorded in the first terminal when the digital item management information is changed;

Sending the updated digital item management information to the second terminal.

Still further, the digital item management information includes an IPMP description regarding encryption and decryption, signing and verification, permission and confirmation of the digital item, and reproduction, copying, and transfer of rights to access, purchase, and consume the digital item. At least one of the following: a description of the rights of the action, record, transfer, number of times, and time limit, and the event of the digital item. ■ Reporting, digital 'item' menu.

MPEG-21 defines IPMP information that may include tool.list and / or tool'containers exchanged between peers. The right to use can be carried as part of the IPMP information.

Also, the usage right information is defined to allow separate transmission of the usage right, and the remote IPM for carrying, transferring and updating the above IPMP information and usage right, or other useful information. Means for defining general high-level negotiation messages, including P information messages, usage rights messages, and other messages. This set of negotiation information is not limited to a particular network protocol.

Action IPMP Information to be exchanged between MPEG-21 peers carrying the list of IDs, usage rights, and binary IPMP tools is defined. Interoperability is ensured by defining the syntax of the IPMP information General IPMP information messages are defined to enable negotiation, transmission or updating of the above IPMP information.

Rights information exchanged between MPE G-21 peers, which may carry RDDZREL or other proprietary rights, is defined.

A general usage right message is defined to allow negotiation, transmission or updating of the usage right information.

MPEG-21 peers are built by implementing high-level negotiation 'messages (IPMP information messages and usage rights messages) that can be coupled to network protocols. Also, the message 'parser needs to be implemented at the peer.

The invention's effect

The present invention is to design a negotiation mechanism with defined IPMP information and usage rights messages as used for translation of IPMP information and usage rights to various types of devices in the market.

The defined IPMP information and usage rights messages allow IPMP information and usage rights to be exchanged between MPEG-21 compliant peers in an interoperable manner.

BRIEF DESCRIPTION OF THE FIGURES

Various objects, features and advantages of the present invention will become apparent from the preferred embodiments described below with reference to the accompanying drawings.

Figure 1 is a block diagram of a multimedia distributed network with information exchange.

FIG. 2 is a schematic diagram of an MPEG-21 generic message layer for negotiation.

FIG. 3 is a flowchart of a general IPMP information message between peers. Figure 4 is a conceptual diagram of the structure of the IPMP information message, schema, syntax and semantics.

Figure 5 is a conceptual diagram of the syntax and semantics of the tool list of the IPMP information message schema.

Figure 6 is a conceptual diagram of the syntax and semantics of the tool container of the IPMP information message 'schema.

Figure 7 is a conceptual diagram of the structure of the syntax and semantics of the rights container of the IPMP information message 'schema.

Figure 8 shows a typical usage rights message flow chart between peers. Figure 9 is a conceptual diagram of the tree structure of the usage rights message 'schema' syntax and semantics.

Figure 10 is a conceptual diagram of the tree structure of usage right syntax and semantics.

Figure 11 is a block diagram of the MPEG-21 browser that processes negotiation messages.

FIG. 12 is a schematic diagram of a digital item management information management system including terminal A and terminal B.

FIG. 13 is a time chart showing a negotiation regarding digital item management information between terminal A and terminal B.

BEST MODE FOR CARRYING OUT THE INVENTION

Hereinafter, embodiments of the present invention will be described with reference to the accompanying drawings. In each drawing, the same reference numeral indicates the same component or a component having the same function and operation.

1. Negotiation of IPMP information and usage rights based on common protocols

It is assumed that a general peer-to-peer negotiation protocol that exchanges IPMP information and usage rights is provided as disclosed in JP-A-2002-204286. I PMP information messages and usage rights messages are defined in sections 2 and 3. Here, some terms will be briefly described.

Peer (peer>): A peer is a networked device that implements a protocol. Each peer operates independently and asynchronously from all other peers. One peer has a special relationship (gateway or (Router) may have additional dependencies with other peers.Peers can discover each other on the network to form a peer 'domain.Peers can publish resources to other peers. Peer's endpoint is a URI that uniquely identifies a peer network interface Peer endpoints are used by peers to establish a direct peer-to-peer connection between two peers. Peers will have to use one or more intermediate peers to send messages to other peers, each with its own peer ID. It is uniquely identified.

Peer domain: A peer domain is a collection of peers that have some common problem. Also, the peer 'domain can be statically predefined. Peers self-organize into peer 'domains. Each peer 'domain is also identified by its own peer' domain ID. The protocol describes how peers publish, discover, join, and monitor peers' domains.

Channel: A channel is a virtual communication pipe used to send and receive messages between services or applications across endpoints. A channel is an abstraction of a network that transmits from one end point of a peer to another. Peer An endpoint is an available peer network interface that can be used to send data to another peer and receive data from another peer. A channel may be a single peer location and virtual in and out mailbox images independent of the network topology. Channels can provide a point-to-point mode of communication.

Messages: Information sent using channels and between end points is packaged as messages. The protocol is specified as a set of XML messages exchanged between peers. The use of XML messages to define the protocol allows many different types of peers to participate in the protocol. You. Each peer is free to implement the protocol in the way that best suits its function and role.

ID (Identifier): Within a defined protocol there are a number of entities (peers, peers' domains, pipes and content) that need to be uniquely identifiable. ID serves as a standard way to uniquely identify an entity and to indicate that entity. U

RI is used as a representation of ID.

The negotiation protocol defined in MPEG-21 is a set of open

• Composed of protocols and implements peer-to-peer communication by exchanging peer-to-peer DIA metadata between public 'networks in a powerful and general manner. Peers defined by the protocol are directly accessible even when some of the peers are behind a firewall or on a different network transport.

Create virtual networks that can communicate with other peers and resources. The defined protocol is defined to meet the requirements of interoperability, which means that interconnected peers can easily communicate with each other between different systems and communities. Also, the peer-to-peer network may have different programming languages, operating systems and TCP / IP, HTPTP

Should support networking platforms that run Bluetooth, Home PNA, and many other protocols. It is also

It can also support the widest range of digital devices, including CE, PDAs, appliances, networks, routers, PCs, servers and storage systems, etc.

A protocol is a set of mechanisms designed specifically for peer-to-peer networking and combining. Using these mechanisms, peers can form self-organizing and self-configuring peers, domains independent of their location in the network and without the need for a centralized management infrastructure.

Peers use protocols to exchange IPMP information and rights. The protocol can also be used to discover available network resources (servers, channels, etc.) from other peers. Peers create special relationships To form and combine peer 'domains. Peers are created to send messages that allow full peer connectivity. All protocols can communicate to peers without having to understand or manage a potentially complex and dynamic network 'topology. The protocol can dynamically send messages to multiple network peers at the destination of the network. Each message carries with it either a fully or partially ordered list of gateway peers through which the message is sent. If the route information is incorrect, intermediate peers can help find new routes dynamically. In Figure 2, Module 2.1 contains IPMP information, usage rights, or other messages that may be accessed by the URI or carried as a payload in a negotiation 'message, between MPEG-21 peers. Indicate various information exchanged in. Modules 2.2, 2.3, and 2.4 are separate layers for the messages for information exchange, the protocol for peer-to-peer communications, and the negotiation mechanism that defines the physical network transport, respectively.

Figure 11 is a block diagram of two MPEG-21 browsers with built-in parsers that communicate with each other using negotiation messages. Module 5.1 is a negotiation message that includes a DI description negotiation message, an IPMP information negotiation message, a usage rights negotiation message, and other negotiation messages. Modules 5.2 and 5.3 are two MPEG-21 browsers that have a communication mechanism with a built-in message. Versa and other parsers. Module 5.4 is the underlying peer-to-peer protocol.

2. IPMP information messages exchanged between distributed peers using XML Schema

The IPMP information messages defined here are intended for peer-to-peer forwarding of IPMP information across the public network in a general manner. Open'network platforms are designed for peer-to-peer combining. Cell phones and wireless PDAs to PCs and Suppose that there is a set of open protocols that allow connected devices on a network ranging from a gateway gateway to a proxy to communicate and cooperate in a peer-to-peer manner.

Figure 3 shows a flow chart of IPMP information message negotiation and conversion between peers.

Based on the defined IPMP Information Schema, the IPMP Tools' list, the IPMP Tool. MP EG—2 1 for the peer A containing the container and / or the IPMP Rights Container generates the IPMP message. Shown in module 3.1;

Constructing a registration, transmission, and update message at Peer A when Peer A wants to send or update the current IPMP information to Peer B is shown in Module 3.2;

Sending a registration, transmission, and update message with peer A's IPMP information to peer B at peer A is shown in module 3.3;

Constructing a response message for registration, transmission and renewal with “response” information to peer A at peer B is shown in module 3.4;

Sending a response message for registration, transmission and renewal with "response" information from peer B to peer A is shown in module 3.5;

Checking the "Response" value in the response message at Peer A to see if the IPMP information negotiation between Peer A and Peer B was successful is described in Module 3.6. When the "response" value is "true", it indicates that peer B has accepted registration from peer A and that peer A's new or updated IP PMP information, as shown in module 3.7. Indicates to either that it is ready to receive IPMP information from peer A.

When the "Response" value is "False", as shown in Module 3.8, it means that Peer B rejects the registration from Peer A and it wants to receive the IPMP information from Peer A. Indicates that there is no or a problem with receiving new or updated IPMP information.

I PMP information messageSchema syntax and semantics 4 to Figure 7 and in the XML schema below.

<? xml version = 〃l, 0 "encoding 〃 UTF-8"?>

Ku!-Edited with XML Spy v4.3 (http://www.xmlspy.com) by Ming Ji (Panasonic Singapore Laboratories Pte Ltd) -I>

Xs: schema xmlns: xs = ^ ht tp: / / www. W3.org/2001/XMLSchema e 1 ementFormDef au 1 t = 〃qualif ied〃 attributeFormDefault ^=, unqualif ied ")

Xs: element name = ^ IPMPInformation essage ^// >

<xs: annotation>

Xs: documentation〉 messages for IPMP Information exchange (I xs: documentation)

</ xs' annotation)

Xs: complexType>

Xs: sequence)

Xs: element name = Type〃>

Xs: simpleType>

Xs: restriction base = 〃xs: string ^)

Xs: enumeration value = Registering ^// /> xs: enumeration value = Transmitting /> xs: enumeration value = ^, Updating /> ku / xs: restriction)

C / xs: simpleType>

K / xs: element)

Xs: element name = 〃Msg— ID〃 type ⁼ xs: nonNegativeInteger

7>

<s ^ element name SenderPeer— ID "type =" xs: ID7> c xs: element name = 〃RecipientPeer— ID〃 type = 〃xs: ID〃 /> c xs: element name element IP PInformation min0ccurs = 〃0 〃〉 ku xs ： complexType>

Xs: sequence> Xs: element name = ^/ Reference ^/ type = "xs: anyURI" minOccurs ^^ OV)

Xs: element name = "IPMPToolList type

ToolList ^y minOccurs = 〃0〃 /〉

Xs: element name ⁼ IPMPToolContainer t ype ⁼ ToolContainer minOccurs = 〃0〃 maxOccurs = unbounded ^/ />

Xs: element name ^=, IPMPRightsContainer type = 〃RightsContainer〃 minOccurs = 〃0〃 maxOccurs = unbounded ^ /)

</ xs: sequence)

C / xs: complexType>

Ku / xs: e 丄 ement>

Xs: element name = 〃Response type = 〃xs: boolean "minOccu rs =" (T />

</ xs: sequence)

C / xs: complexType>

K / xs: element)

Xs: complexType name = loolList ">

Xs: sequence)

Xs: element name = Tool ID type = 〃xs: string /> xs: element name = 〃ToolURLs minOccurs o〃〉

Xs: comp 丄 exType>

Xs: sequence)

Ku xs: element name = ^, No0fURLs' type = xs: int "/〉 ku xs: element name = 〃Tooll) RL〃 type = xs: anyURI〃 maxOccurs = 〃unbounded〃 /〉

X / xs: sequence)

, 1 xs: complexType>

^ xs * element)

Xs: element name = 丄 PMPAlternative min0ccurs = 0> Xs: complexType)

<xs ^ sequence)

Xs: element name = ^/ NoOfAlternates ^// type ^{= //} xs: intV>

Xs: element name = "AltToolID〃 type = xs: strin g〃 maxOccurs = 〃unbounded〃 /〉

K / xs: sequence)

K / xs: complexType)

Ku / xs: element ；〉

<xs: element name = ^ I PMPPar ame t r ic ^ min0ccurs = "07>

</ xs: sequence)

C / xs: complexType)

Xs: complexType name = ToolContainer

<xs: sequence)

<xs' element name Tool ID〉

<xs: complexType)

Xs: simpleContent)

Xs: extension base base xs: imsignellnt '〉

Xs: attribute name = ^/ FormatID type = xs ： int〃 use = 〃optiona 丄 /〉

<xs "attribute name ⁼ PackageID" type ^{= /} xs' int ^ use = 〃optiona 丄 /〉

</ xs: extension>

Gu / xs: simpleContent)

V xs: complexType)

^ / xs ". element)

Ku xs: element name = ΓοοΙΒοαγ type xs: byte /> ku / xs: sequence>

C / xs: complexType) <xs: coraplexType name = "RightsContainer">

Xs: sequence>

Xs: element name ⁼ UsageRules type = xs: string "/)

<xs: element name = "IsProprietary type =" xs'- boolean "/) xs: element name =" RightsToolID "type =" xs: string "minOccur s =" 07>

</ xs: sequence)

</ xs: coraplexType)

K / xs: schema)

Type: Indicates the type of IPMP information message, such as "Register", "Send", and "Update";

Registration: The type of message used to initiate IPMP information conversion when a peer attempts to send or update IPMP information;

Send: type of message used to send current IPMP information; Update: type of message used to update current IPMP information;

Ms g—ID: The message identifier identified by the message originator. All messages sent in response to a message should include the identifier of the original message;

Sender Peer-ID (senderPeer-ID): Indicates the peer ID of the originator of the message;

Recipient Peer — ID (rec eiv e r Peer_ID): Indicates the peer ID of the intended recipient of the message;

I PMP information: All I PMP information that needs to be transmitted, converted, and updated, including the I PMP tool list, the I PMP tools container, and the I PMP rights container;

The IPMP information can be carried in the message as the payload "IPMP information" or the MP EG—21 peer refers to the "reference" that refers to the entity of the IPMP information located on the world 'wide' web. Can be used.

Response: Same "Ms g ID" and "Type" with either true or false value Used to carry a response message that responds to the original input message with (Type). When the “Response” element is used, “IPMP Information” is not used.

In the case of registration, "true" indicates that the message sender agrees to receive the IPMP information after processing the registration message;

For transmission, "true" indicates that the message sender successfully receives the IPMP information;

And in the case of an update, “true” indicates that the message sender successfully receives the updated IPMP information.

“False” indicates that in the above three cases, “I do not agree”, “Something is wrong when receiving the IPMP information”, “Something is wrong when receiving the updated IPMP information” .

I PMP Tools' List: It contains a list of I PMP tools. It is used to identify all IPMP tools that should be used to play the content. The logical I PMP tool is one of the following:

Vendor specific I PMP tool, identified by Tunole ID

One of a list of alternative I PMP tools,

I PMP tool identified by parametric description.

Tool URL: It contains a list of information URLs that peers use to search for IPMP tools that are not available on the terminal.

I PMP Alternatives: A list of alternative tools with specified A1tToo1IDs that perform similar functions. MPEG-21 peers are free to choose one of them.

I PMP parametric: A parametric description of the I PMP tool.

Tounolle Container: This allows you to carry the IP PMP tool in a message. The device retrieves the IPMP tool from the message, loads it, instantiates it, and uses it directly to play protected content.

Tool 'body': A binary tool. It is binary, two It shows the binary representation of the file and has a format assigned by the registered right holder—the Ford—ID, and a package that gives the package details of the tool—the Id (Package—Id). For example, self-implemented and executable such as CAB or Winzip. The ID value is assigned by the right holder.

I PMP rights container: It represents the usage rules and status associated with the I PMP protected content, by which REL etc. are carried.

Proprietary Scheme (is Proprietary) —Boolean algebra, if true, is because the following usage rules are proprietary, and it is the rights management tool of that scheme to parse and understand it Means that it must be sent to Rights Tool ID—Tool ID for proprietary rights management tools. The following usage rules are sent to the rights management tool that refers to them.

Usage rules—this includes details of usage rights information.

3. Rights message exchanged between distributed peers using XML Schema The rights message defined here is a peer-to-peer conversion of rights information individually across a public network in a general manner. Is aimed at. The open network platform is designed for peer-to-peer combining. There is a set of open protocols that allow connected devices on networks ranging from cell phones and wireless PDAs to PCs and servers / gateways / proxyes to communicate and cooperate in a peer-to-peer manner Suppose that.

Figure 8 shows a flow chart of the usage right message negotiation and conversion between peers.

The generation of the MPEG-21 Usage Rights message included in Peer A is shown in Module 4.1;

Building a registration, transmission, and update message at Peer A when Peer A wants to send or update current usage rights information to Peer B is shown in Module 4.2;

At Peer A, register, send, and update messages with Peer A's usage rights information to Peer B. Sending a message is shown in module 4.3;

Constructing a response message for registration, transmission, and updating with "response" information to peer A at peer B is shown in module 4.4;

Sending a response message for registration, transmission and renewal with "response" information at Peer B to Peer A is shown in Module 4.5;

Checking the "Response" value in the response message at Peer A to see if the rights information negotiation between Peer A and Peer B was successful is shown in Module 4.6. When the "Response" value is "True", it indicates that Peer B accepts registration from Peer A and indicates that Peer A's new or updated entitlement information, as shown in Section 4.7. Indicates to either that they are ready to receive usage rights from peer A. When the "response" value is "false j", as shown in module 4.8, it indicates that peer B has refused to register from peer A and that it does not want to receive usage rights information from peer A. Or indicate that it has a problem receiving new or updated usage rights information.

Usage rights messages · Schemas · Syntax and semantics are shown in Figure 9 and Figure 10 and in the XML schema below.

fxml version = 1.0 encoding = UTF-8〃?>

<! -edited with XML Spy v4. 3 (nttp: //www.xmlspy.com) by Huang Zhongyang (Panasonic Singapore Laboratories Pte Ltd)->

Xs: schema xralns: xs = "htt: // www. 3. org / 2001 / XMLSchema" elementFormDefaul t = "qualif ied" attributeFormDefault ^ unqualif ied ">

<xs: element name = UsageRightsMessage ">

<xs: annotation)

<xs: documentation> messages for usage rights </ xs: documentation>

</ xs: annotation)

<xs: complexType>

<xs: sequence) Xs: element name = ^/ Type>

Xs: simpleType>

Xs: restriction base ⁼ xs: string>

Xs: enumeration value ^{= /} Registering /> ku xs: enumeration value = Transmitting /> ku xs: enumeration value = 〃Updating〃 /〉 ku / xs: restriction)

Ku / xs: simpleType>

C / xs: element>

Xs: element name = 〃Msg— ID〃 type = xs: nonNegativeInteger

7>

<xs: element name = 〃SenderPeer-ID〃 type = 〃xs: ID /) x xs: element name = 〃RecipientPeer-ID〃 type = 〃xs: ID〃 /> xxs: element name = ^, UsaegRightsInformation ^A 'minOccurs ^{= //} (T>

Xs: complexType)

Fuck xs: sequence>

K xs: element name 〃 Reference "type = xs: anyUR 丄 minOccurs (T /〉

Xs: element name = 'UsageRightsContainer

〃 type = 〃UsageRights min0ccurs = 〃0〃 max0ccurs = 〃unbounded〉

K / xs: sequence)

K / xs: complexType)

K / xs: element)

Ku ^{xs: element name = / Response "} type = xs: boolean"'minOccu rs = / 0/7>

K / xs: sequence)

C / xs: complexType>

C /: s: element) <xs: complexType name = "UsageRights">

<xs: sequence)

Xs: element name = "UsageRules" type = xs: string "/>

<xs: element name = "I sPropr i etary" type = "xs: boolean" /) Ku xs: element name = "RightsToolID" type = xs: string "minOccur s ="0/7>

</ xs: sequence)

K / xs: complexType)

/ Xs: schema>

Type: Indicates the usage rights message type, such as "Register", "Send", and "Update";

Registration: The type of message used to initialize the rights information conversion when the peer attempts to send or update the rights information;

Transmission: type of message used to transmit current usage right information; update: type of message used to update current usage right information;

Sender Peer-ID (send de r Peer r ID): Indicates the peer ID of the originator of the message;

Rights Information: All rights information that needs to be transmitted, converted and updated The rights information can be carried in the message as a payload "rights container" or the MPEG-21 peer can A “reference” can be used to indicate the substance of the usage rights information that is placed on the World Wide Web. Response: To carry a response message that responds to the original message with the same "Ms g—ID" and "Type J" values that have either a true or false value Used. When the "Response" element is used, "Usage Rights Information" is not used.

In the case of registration, "true" indicates that the message sender agrees to receive usage rights information after processing the registration message;

For transmission, "true" indicates that the message sender has successfully received the usage rights information;

And in the case of an update, “true” indicates that the message sender successfully receives the updated entitlement information.

“False” indicates that in the above three cases, “I do not agree”, “Something is wrong when receiving the usage rights information”, “Something is wrong when receiving the updated usage rights information” .

Usage rights container: This carries the usage rules and status associated with the protected content, such as REL.

Proprietary Scheme (is Proprietary) —Boolean algebra, if true, is because the following usage rules are proprietary, and it is the rights management tool of that scheme to parse and understand it Means that it must be sent to Rights Tool ID—Tool ID for proprietary rights management tools. The following usage rules are sent to this referenced rights management tool.

Usage rules—this includes details of usage rights information.

Next, a management system of management information of digital items in the first terminal and the second terminal using digital items according to the embodiment of the present invention will be described. In the following description, it is assumed that terminal A is the first terminal and terminal B is the second terminal. An example of digital items is content from the Internet. The following description is an example, and the present invention is not limited to this.

FIG. 12 is a schematic diagram of terminal A 101 and terminal 8 11 1. The terminal A 101 includes a CPU 102, a memory 103, an audio output unit 104, a video output unit 105, and an input / output device 106. The terminal B 111 also has the same configuration as the terminal A, and includes a CPU 112, a memory 113, an audio output unit 114, a video output unit 115, and an input / output device 116. Audio output on each terminal And the video output unit may not be included. Terminal A is connected to an external input, for example, the Internet 100. The input / output device 106 of the terminal A is connected to the input / output device 116 of the terminal B.

Terminal A receives distribution of content (for example, a movie) via the Internet, and manages digital item management information (for example, information on a decryption tool for decrypting encryption, and limits the number of copies) to use the content. Information and contract information). Terminal B also receives the content and digital item management information from terminal A. In this case, the digital item management information, which is as important as the content information itself, needs to be transmitted from terminal A to terminal B without fail, so that it is transmitted according to a certain format (negotiation). Is configured. Next, negotiation for ensuring that digital item management information is transmitted from terminal A to terminal B will be described with reference to FIG.

FIG. 13 shows a time chart in which time elapses in the vertical direction. At time point S1, terminal A receives a decryption tool X for decrypting the content from the Internet. In addition to the Internet, it is also possible to receive via cable or recording media. Terminal A sets tool X to the contents specific to terminal A at time S2. The tool X thus set and generated is recorded and stored in the memory 103 of the terminal A. In response to this recording and storage, terminal A determines whether the terminal to which decryption tool X is to be transferred is connected. In this example, terminal B is connected. If it is determined that the connection is established, the “registration” procedure described below is executed.

At time S3, terminal A performs a “registration” procedure with terminal B. This “registration” procedure sends from terminal A to terminal B an instruction to secure a memory area for storing tool X along with information on tool X (data size information, attribute information, etc. of tool X). At the time point S4, the terminal B receiving the command secures a memory area for storing the tool X in the memory 113 of the terminal B. Then, at time S5, a confirmation Ack indicating that the memory area has been secured is sent from terminal B to terminal A. In response to the acknowledgment Ack, at time S6, the tool X is transmitted from the terminal A to the terminal B according to the “transmission” procedure. Sent through this "send" procedure The information includes information about the secured memory area. At time S7, the terminal B saves the transmitted tool X in the secured memory area. By the “registration” and “transmission” procedures, the terminal B can store and manage digital item management information in a predetermined memory area, distinguished from other information such as contents.

Later, at time S 8, when the changed tool X is sent to the terminal A via the Internet, at time S 9, the terminal A converts the changed tool X to the terminal A-specific tool X. Generate and overwrite the location where tool X before change was recorded. In response to this overwrite, the "update" procedure described below is performed. At time S10, terminal A performs an "update" procedure with terminal B. According to the “update” procedure, the change tool X is transmitted from the terminal A to the terminal B. The information sent in this “send” procedure also includes information about previously secured memory areas. At time SI1, the terminal B saves the transmitted change tool X over the secured memory area.

Further, at the terminal A of the above digital item management information management system, a management information change detecting means for detecting a change of the digital item management information at at least one of the terminal A and the terminal B;

Management information updating means for updating the digital item management information recorded in terminal A when the digital item management information is changed;

May be further provided.

With the above configuration, even when the digital item management information changes at the terminal A and the terminal B using the digital item, the digital item management information at each terminal can be updated so as to be consistent. As a result, digital item management information can be centrally managed for the entire system including the terminal A and the terminal B.

Note that the present invention can have the following configurations shown in various embodiments. According to a first configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Encryption and decryption, signing and verification of terminals (also referred to here as peers) Generating an IPMP (Intellectual Property Management and Protection) statement of attestation, authorization and confirmation;

Generating a rights statement regarding rights to access, purchase and consume digital 'content, such as playback, copy, move, record, transfer, count, time limit, etc., for a terminal (also referred to herein as a peer);

Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers), and at appropriate locations for use in exchanges, transmissions, and updates in negotiation protocols Locating the IPMP description;

Placing said rights statement in an appropriate location for use in exchanges, transmissions, and updates in a negotiation protocol;

Placing said other description in an appropriate location for use in exchanges, transmissions, and updates in the negotiation protocol;

Identifying and defining a generic protocol 'message' schema to perform the functions of the generic protocol;

Exchanging, updating and transmitting the IPMP description using the defined protocol;

Exchanging, updating and transmitting the rights statement using the defined protocol;

Exchanging, updating and transmitting the other description using the defined protocol.

According to a second configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Generating an IPM (Intellectual Property Management and Protection) description of encryption and decryption, signing and verification, authorization and verification for the terminal (also referred to herein as a peer);

Generating a rights statement regarding rights to access, purchase, and consume digital 'content, such as playback, copy, move, record, transfer, count, time limit, etc., for a terminal (also referred to herein as a peer); Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers) and suitable locations for use in exchanges, transmissions, and updates in negotiation protocols Placing the IPMP description in

Placing said other description in an appropriate location for use in exchanges, transmissions, and updates in a negotiation protocol;

Identifying and defining a flexible advertising metadata description schema to describe various types of resources, including peers, peers' domains, channels, etc., and incorporating the IPMP description into the advertising metadata Steps and

Incorporating the rights statement into the advertising metadata;

Incorporating the other description in the advertising metadata;

Identifying and defining a common protocol 'message' schema; and

Exchanging, updating, and transmitting the other description using the defined protocol.

According to a third configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Right to access, purchase, and consume digital 'content, such as playback, copy, move, record, transfer, count, time limit, etc. for terminals (also referred to herein as peers) Generating a rights statement on the interests;

Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers) and suitable locations for use in exchanges, transmissions, and updates in negotiation protocols Placing the IPMP description in

Identifying and defining a flexible advertising metadata description schema to describe various types of resources, including peers, peers, domains, channels, etc., and incorporating the IPMP description into the advertising metadata Steps and

Incorporating the rights statement into the advertising metadata;

Incorporating the other description in the advertising metadata;

Negotiating an advertising metadata description schema to interpret the advertising metadata description at the peer;

Generic protocol '' Identify and define message schema

Exchanging, updating, and transmitting the rights statement using the defined protocol;

According to a fourth aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Generate an IPMP (Intellectual Property Management and Protection) description of encryption and decryption, signing and verification, authorization and verification for terminals (also referred to herein as peers) Steps

Generating a rights statement regarding rights to access, purchase, and consume digital 'content, such as playback, copy, move, record, transfer, count, time limit, etc., for a terminal (also referred to herein as a peer);

Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers), and suitable locations for use in exchanges, transmissions, and updates in negotiation protocols Placing the IPMP description in

Identify and define a common protocol schema

By establishing the channel by using a channel binding protocol, the peers need to exchange, send, and update the IMPPP description in the Routing the protocol message using a routing protocol, and peers knowing each other by using a resolver protocol;

Constructing the channel by using a channel binding protocol to establish the connection of the peer that needs to exchange, send and update the rights statement in the peer domain, and endpoint 'routing' Routing the protocol message by using a protocol, peers knowing each other by using a resolver protocol, and establishing the channel by using a channel binding protocol in the peer 'domain. The other connections need to be exchanged, sent and updated to establish the peer's connection, endpoints, routing, Routing the protocol message using a mouth protocol and knowing the peer to each other by using a peer resolver protocol;

According to a fifth aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Generating an IPMP (intellectual property management and protection) description of encryption and decryption, signature verification, authorization and verification for the terminal (also referred to herein as a peer);

Generating other descriptions of event reporting, digital items, menus, etc. for terminals (also referred to herein as peers) and appropriate for use in exchanges, transmissions and updates in the negotiation protocol Placing said IPMP description in a location;

Placing said rights statement in an appropriate location for use in exchanges, transmissions and updates in a negotiation protocol;

Identify and define a common protocol schema

Exchanging, updating, and transmitting the IPMP description using the defined protocol; Exchanging, updating and transmitting the rights statement using the defined protocol;

Exchanging, updating, and transmitting the other description using the defined protocol;

Critical discovery messagesExchange, update, and send the IPMP description by enabling infrastructure to query and respond to advertising metadata containing the IPMP description based on peer discovery protocol Steps and

Key discovery messagesExchange, update, and send the rights descriptions by enabling the infrastructure to query and respond to advertising metadata containing the rights descriptions based on the peer discovery protocol Exchanging and updating key discovery messages by enabling the infrastructure to query and respond to advertising metadata containing the other descriptions based on a peer discovery protocol Steps to send and send

A method that includes

According to a sixth aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

The step of identifying and defining the general protocol message 'schema to implement the functions of the general protocol comprises: a message schema at all peers involved in implementing all protocols. (2) the step of implementing a parser.

According to a seventh aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Steps to establish a connection between peers that require an IMP P negotiation based on common high-level peer-to-peer protocols and real network protocols;

Steps to establish a connection between peers that need to negotiate rights based on common high-level peer-to-peer protocols and real network protocols. And

General high-level peer-to-peer protocol and real network protocol Steps to build connections between peers that require other negotiations based on the protocol,

Generating a rights statement for a terminal (also referred to herein as a peer) regarding the right to access, purchase and consume digital 'content, such as play, copy, move, record, transfer, count, time limit, etc. When,

Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers); and said IPMP description, IPMP description element to implement a negotiation mechanism. Identifying and defining common and important IPMP negotiation messages, including the schema

Identifying and defining a general and important rights negotiation message schema including said rights description, rights description element, to implement a negotiation mechanism;

Identifying and defining said other description, general and important other negotiation message schemas, including specific descriptive elements, to implement a negotiation mechanism;

Registering, transmitting, and updating the IPMP description with the IPMP Negotiation message between the negotiation peer; registering the rights description with the rights negotiation message between the negotiation peer Transmitting, transmitting, and updating;

Registering, transmitting, and updating the other description with the other negotiation message between the negotiation peer.

According to the eighth configuration, the necessity for information exchange within the MPEG-21 framework is obtained. A method for defining a negotiation mechanism, comprising:

Steps to establish a connection between peers that require IPM negotiation based on common high-level peer-to-peer protocols and real network protocols;

Steps to establish a connection between peers that need to negotiate rights based on common high-level peer-to-peer protocols and real network protocols;

Steps to build connections between peers that require other negotiations based on common high-level peer-to-peer protocols and real networks.

Generating a rights statement for the right to access, purchase and consume digital 'content, such as play, copy, move, record, transfer, count, expiration, etc., for the terminal (also referred to herein as a peer);

Identify the IPMP description as a criterion using "predetermined criteria" to specify the entity of the IPMP description to be placed on the world's wide web, or Identifying the IPMP description as a message payload using P-Tools 'List', 'IPMP Tournament Container', and / or 'IPMP Rights Container';

Specify the rights statement as a criterion using `` prescribed criteria '' to specify the entity of the rights statement to be placed on the web, or as a message payload using `` usage rights container '' The step of identifying a rights statement and identifying the other statement as a criterion using "predetermined criteria" to specify the substance of the other statement to be placed on the World Wide Web, or a "specific container" ) To identify other descriptions as message payload,

Registering, transmitting and updating the IPMP description with the IPMP Negotiation message between the negotiation peer, and registering the rights description with the rights negotiation message between the negotiation peer Transmitting, transmitting, and updating;

Registering, transmitting and updating the other description with the other negotiation 'message between the negotiation peer.

According to a ninth configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

Steps to establish a connection between peers that require IPPM negotiation based on common high-level peer-to-peer protocols and real network protocols;

Steps to establish connections between peers that need to negotiate rights based on common high-level peer-to-peer protocols and real network protocols;

Steps to build a connection between peers that need other negotiations based on the general high-level peer-to-peer protocol real network protocol;

Generating a rights statement for a terminal (also referred to herein as a peer) regarding the right to access, purchase, and consume digital content, such as play, copy, move, record, transfer, count, time limit, etc. When,

Generating other descriptions of events, reporting, digital items, menus, etc., for terminals (also referred to herein as peers); and the IPMP description, IPMP description to implement a negotiation mechanism. Identifying and defining general and important IPMP negotiations, including message and message schemas;

Registering, transmitting and updating the IPMP description with the IPMP negotiation message between the negotiation peer; and registering the rights description with the rights negotiation message between the negotiation peer. Transmitting, transmitting, and updating;

Registering, sending, and updating the other description with the other negotiation message between the peers; and peer A sends or updates the current IPMP description to peer B. Constructing a registration message with the message ID for peer A when

Constructing a registration message with a message ID for peer A when said peer A wants to send or update the current rights statement to peer B;

That said peer A sends or updates the current other description to peer B. Steps to construct a registration message with the message ID for peer A when desired;

Sending the registration message to the peer B;

Sending a response message from the peer B with the same message ID and message type to the peer A with "response" information, wherein "true" means that the peer B receives an IPMP description from the peer A Means false and "false" means that peer B refuses to receive the IPMP description from peer A for some reason;

Sending a response message from the peer B with the same message ID and message type to the peer A with "response" information, wherein "true" means that the peer B receives the rights statement from the peer A Means ready and "false" means that peer B refuses to receive the rights statement from peer A for some reason;

Sending a response message from the peer B having the same message ID and message type to the peer A having the "response" information, wherein "true" indicates that the peer B has received another description from the peer A. Means that it is ready to receive, where "false" means that said peer B refuses to receive said other description from said peer A for some reason.

According to a tenth aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

General high-level peer-to-peer steps that establish connections between peers that require other negotiations based on the peer protocol and the real network protocol; Generating an IPMP (Intellectual Property Management and Protection) description of encryption and decryption, signing and verification, authorization and verification for the terminal (also referred to herein as a peer);

Registering, transmitting, and updating the IPMP description with the IPMP negotiation message between the negotiation peer; andthe right to have the rights negotiation 'message between the negotiation peer. Registering, submitting and updating the description;

Constructing a registration message with a message ID for peer A when said peer A wants to send or update the current rights statement to peer B; A step of constructing a registration message with a message ID for peer A when said peer A wants to send or update the current other description to peer B;

Sending the outgoing message to the peer B;

Sending a response message from the peer B having the same message ID and message type to the peer A having "response" information, wherein "true" is transmitted from the peer A to the peer B. Means that the received IPMP description from the peer A to the peer B is not successfully received for some reason. Sending a response message from the peer B with the same message ID and message type to the peer A with "response" information; "true" indicates the transmitted right from the peer A to the peer B "False" means that the transmitted right description from peer A to peer B is not successfully received for some reason. And a step which means that,

Sending a response message from the peer B having the same message ID and message type to the peer A having "response" information, wherein "true" is transmitted from the peer A to the peer B. `` False '' means that the other description sent from peer A to peer B is not successfully received for some reason. And a method comprising steps.

According to a first configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework.

General high-level steps to build a connection between peers that require IMP P negotiation based on peer-to-peer protocols and real network protocols;

Steps to establish connections between peers that require rights negotiation based on common high-level peer-to-peer protocols and real network protocols;

General high-level peer-to-peer protocols and real network protocols Steps to establish a connection between peers that need other negotiations based on protocol

Generating an IPMP (Intellectual Property Management and Protection) description of the terminal (also referred to herein as a peer) regarding encryption and decryption, signing and verification, authorization and verification;

Generating a rights statement for the rights to access, purchase and consume digital 'content, such as playback, copy, move, record, transfer, count, time limit, etc., for the terminal (also referred to herein as a peer);

Generating other descriptions for a terminal (also referred to herein as a peer) regarding event reporting, digital 'item' menus, etc., and said IPMP description, IPMP description element to implement a negotiation mechanism. Identifying and defining common and important IPMP negotiation messages, including the schema

Registering, transmitting and updating the IPMP description with the IPMP Negotiation 'message between the negotiation peers; andthe negotiation. The rights description with the rights negotiation message between the peers. Registering, sending and updating;

Registering, transmitting, and updating the other description with the other negotiation message between the peers; and peer A sends or updates the current IMPP description to peer B. Building a registration message with the message ID for peer A when it wishes to do so;

Said peer A wants to send or update the current rights statement to peer B Sometimes constructing a registration message with a message ID for peer A;

A step of constructing a registration message with a message ID for peer A when said peer A wants to send or update the current other description to peer B;

Sending the update message to the peer B;

Sending a response message from the peer B having the same message ID and message type to the peer A having the "response" information, wherein "true" means that the peer A has successfully updated the updated IPMP description. Receiving, wherein "false" means that for some reason the updated IPMP description is not successfully received from the peer A;

Sending a response message from the peer B having the same message ID and message type to the peer A having the "response" information, wherein "true" means that the update right description has been successfully transmitted from the peer A. Receiving, wherein "false" means not receiving the renewed rights statement successfully from Peer A for some reason;

Sending a response message from the peer B having the same message ID and message type to the peer A having the "response" information, wherein "true" means that the update and other descriptions from the peer A have been successfully completed. Receiving the update or other description from the peer A for some reason.

According to a twelfth aspect, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework, wherein the IPMP, rights and Z or other information is used to implement the negotiation mechanism described above. General and important IPMP, rights, or other negotiation messages including description 'Identifying and defining schema exchange IPMP, rights, and Z or other descriptions A method further comprising the step of enforcing IPMP, rights, and Z or other negotiations, messages, schemas, and parsers at all peers included in the. According to the thirteenth configuration, there is provided a method for defining a negotiation mechanism for information exchange within the MPEG-21 framework, comprising an open and defined scheme.

A method comprising parsing a message verser, a DID parser, a DIA parser, an IPMP parser, a rights verser, and a peer with a Z or other parser to parse and process the negotiation message by the machine . According to a fifteenth aspect, there is provided a method for defining a negotiation mechanism for information exchange within an MPEG-21 framework, comprising: a peer having a browser to provide a user with the parsed and processed result. Constructing the method.

As described above, the present invention has been described in detail with reference to preferred embodiments. However, the present invention is not limited to these embodiments, and many of them are within the technical scope of the present invention described in the claims. It will be obvious to those skilled in the art that preferred variations and modifications of the present invention are possible.

Claims

The scope of the claims

1. A management system of management information of the digital item between a first terminal and a second terminal using a digital item,

The first terminal is

With

The second terminal is

Receiving means for receiving the digital item management information;

A digital item management information management system, comprising:

2. The first terminal in the digital item management information management system between a first terminal and a second terminal that use a digital item, wherein the management information generating means generates management information of the digital item; ,

Transmitting means for transmitting, to the second terminal, an area reservation request for recording the management information of the digital item in the second terminal; and

A first terminal, comprising:

3. management information change detection means for detecting a change in the digital item management information in at least one of the first terminal and the second terminal;

Management information updating means for updating the digital item management information recorded in the first terminal when the digital item management information is changed; and x_,

3. The first terminal according to claim 2, wherein the transmitting unit sends the updated digital item management information to the second terminal.

4. A method for managing the management information of the digital item in the first terminal when the digital item is used between the first terminal and the second terminal, wherein the first terminal includes the management of the digital item. Generating information; and

Recording the digital item management information in the first terminal; requesting the second terminal to secure an area for recording the digital item management information from the first terminal to the second terminal. ,

Transmitting the digital item management information to the second terminal.

5. detecting a change in the digital item management information in at least one of the first terminal and the second terminal;

The method for managing digital item management information according to claim 4, further comprising: sending the updated digital item management information to the second terminal.

6. The digital item management information includes the IPMP description of encryption and decryption, signing and verification, permission and confirmation of the digital item, playback, copy, and transfer of rights to access, purchase, and consume the digital item. 5. The digital item management method according to claim 4, wherein the digital item management method is at least one of a description of rights regarding recording, transfer, the number of times, and a time limit, an event / reporting of the digital item, and a description of digital / item / menu.