Classifications

• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/104—Peer-to-peer [P2P] networks
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/10—File systems; File servers
  • G06F16/18—File system types
  • G06F16/182—Distributed file systems
  • G06F16/1834—Distributed file systems implemented based on peer-to-peer networks, e.g. gnutella
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/01—Protocols
  • H04L67/10—Protocols in which an application is distributed across nodes in the network
  • H04L67/104—Peer-to-peer [P2P] networks
  • H04L67/1074—Peer-to-peer [P2P] networks for supporting data block transmission mechanisms
  • H04L67/1078—Resource delivery mechanisms
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/2866—Architectures; Arrangements
  • H04L67/2895—Intermediate processing functionally located close to the data provider application, e.g. reverse proxies
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/2866—Architectures; Arrangements
  • H04L67/30—Profiles
  • H04L67/303—Terminal profiles
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L67/00—Network arrangements or protocols for supporting network services or applications
  • H04L67/50—Network services
  • H04L67/56—Provisioning of proxy services
  • H04L67/565—Conversion or adaptation of application format or content

Definitions

• the present invention relates to content sharing technology in a network, more particularly relates to technology for sharing content information in a network.
• broadcast encryption technology based on public key cryptography provides an efficient sharing and protection method. In comparison with public key methods, broadcast encryption requires orders of magnitude less computational overhead in compliant devices.
• broadcast encryption protocols are one-way, not requiring any low-level handshakes. Low-level handshakes will increase the dependence on the network connection at server end, and tend to weaken the security of copy protection schemes.
• xCP extensible Content Protection
• xCP supports a trusted domain called a x cluster' that groups together a number of compliant devices with xCP cluster protocol, the structure of which is shown in figure 1.
• Content in cluster with cluster specific information can be freely moved among these devices, but it is useless to devices that are outside the cluster. There could be more than one cluster within private network.
• the present invention provides a method as claimed in claim 1, and corresponding method and computer program.
• a device for content information sharing is provided.
• the device for content information sharing is a first device, said first device comprises: a communication module, for exchange information with at least a second device via a network, and receiving a content information request from the second device; a content management module, for managing the content information of the content that the first device could provide; wherein, the content information request from the second device comprises the capability information of the second device, and wherein said first device further comprises a content information filter, for filtering the content information of the content that the first device could provide according to the capability information of the second device, and sending the filtered content information of the content that the first device could provide to the second device.
• the present invention also provides a method for content information sharing, the method comprises: a first device sending a content information request to a second device via a network, said content information request comprises the capability information of the first device; said first device receiving content information from said second device, said content information is obtained by the second device filtering the content information of the content that the second device could provide according to the capability information of the first device.
• the present invention also provides a device for content information sharing, said device is a first device, said first device comprises: a communication module, for exchange information with a second device via a network; a device capability management module, for managing the capability information of the first device; and a content information handler, for generating a content information request according to the capability information of the first device, sending the request to a second device in a network, and receiving content information from said second device, said content information is obtained by the second device filtering the content information of the content that the second device could provide according to the capability information of the first device.
• the present invention realizes effective content sharing among devices by sharing content information according to the capability of devices.
• the first device of the present invention might have the function of the second device for content information sharing as described above. While the second device might implement the content information sharing method of the first device as described above. Differentiating the first device and the second device herein and after is just for description. A person skilled in the art could understand the function of the first device and the function of the second device might be same or different according to the real requirement.
• the first device and the second device are preferably peer to peer in a network or in a cluster. Wherein, the first device and the second device implement the method of the present invention independently.
• Figure 1 illustrates an example private network for implementing the present invention.
• Figure 2 illustrates a device for content information sharing according to one embodiment of the present invention.
• FIG. 3 illustrates a flowchart for content information sharing according to another embodiment of the present invention.
• FIG. 4 illustrates a flowchart for content information updating according to a further embodiment of the present invention. Detailed Description of Embodiment
• the present invention is suitable but not limited to be implemented in middle or small networks, and more particularly in broadcast encryption networks, e.g. an xCP network.
• the present invention is also suitable for other kinds of networks, e.g. a home network or an office network, which require content sharing.
• the following description of the present invention in combination with the prior art is for explaining rather than limiting the invention.
• the broadcast encryption method is a well known method in the technical field of content sharing.
• every device sharing protected content uses its device key to decrypt a management key from a key management block.
• the management key is used for protecting shared content.
• Devices sharing protected content together constitute a cluster or a domain.
• sharable contents are preferably protected with broadcast encryption technology.
• the present invention is implemented in a network using broadcast encryption, and devices are peer to peer in the network or a cluster.
• devices are peer to peer in the network or a cluster.
• every device in the cluster has passed certification based on broadcast encryption technology between each other when joining an associated cluster, and will share media content.
• every device could implement the present invention independently.
• the devices are preferably peer to peer in associated clusters or in the same cluster.
• Figure 1 illustrates an example private network for implementing the present invention.
• contents are shared among PDA 120, set top box/TV 130, computer 140 and DVD player 150.
• Licensing agency 110 manages device keys and key management block. Every device in figure 1 uses its device key to decrypt management key from the key management block provided by licensing agency 110. Then, these devices share contents in peer to peer mode or in end to end mode. These devices that could share contents via a network together form a cluster. However, in such peer to peer network with different devices, sometimes, contents could not be shared, copied and played effectively among the devices due to the difference in the content types, the required storage spaces and network bandwidths and devices' capability. This causes waste of human resources or other resources.
• xCP extensible Content Protection
• IBM extensible Content Protection
• xCP technology could be implemented in PDA 120, set top box/TV 130, computer 140 and DVD player 150. These devices together form an xCP cluster. Contents are shared among the devices in the xCP cluster. For example, computer 140 or set top box/TV 130 may play the media contents stored in DVD player 150.
• the network according to the present invention e.g. an xCP network, usually has the following features.
• the devices in such environment are loosely coupled without central server.
• the structure of cluster is dynamically changed with device leaving and joining.
• the content is stored on different devices.
• some mechanism should be provided to access remote content, for example, copy or media steaming.
• the network always consists of devices with different hardware and software media player, and there may be more than one media player installed on one device.
• the network always consists of diversified devices with different system capability, such as display, decoder, processor, storage, and network bandwidth based on different network connection types (Ethernet, wireless LAN, Bluetooth ... )
• content shared is dynamically changed, accordingly any device should be aware of change of content within a network in real-time.
• content information is shared in client- server mode with centralized directory or registry service. It means that a device registers content information to a centralized server and other devices gets information of shared content from the server.
• Such solution always uses technologies derived from enterprise technologies, such as JNDI/LDAP.
• Some dedicated solutions defined for home network multimedia applications, for example, the registration service of open source project Network-Integrated Multimedia Middleware, are also working in such mode.
• Conventional peer-to-peer system also always involve server for content sharing and popularity, for example, methods presented by US Patent 2003/0005035 Al and 2003/0204613.
• the present invention provides a peer-to-peer method to enable the private network (e.g. xCP private network) as a virtual multimedia device, in which content information is dynamically shared according to device capability.
• Each device is responsible for management of local content information and capability information.
• the content information is requested based on device capability within cluster.
• the changes of content information one each device or topology of cluster may trigger the update of content information. It has following advantages 1. Peer-to-peer structure for content sharing.
• the content and content information are maintained by each device and updated dynamically within cluster. It is consistent to the network structure.
• Each device could only get the information of content that could be rendered according to its device capability. It could avoid replicating and rendering of useless content, and decrease the user involvement.
• a user does not need to consider the system capability and/or content processing capability of the device being used when the user selects content according to the content information.
• the user even does not need to know the system capability and/or content processing capability of the device being used and the location where the content is stored. The user just directly selects the required content according to the content information.
• the capability used for content sharing comprises both static and dynamic system capability and media processing capability, where media processing capability comprises the capability of all the software and hardware media players in the device system.
• Dynamically content information updating The changes of content information will be broadcast actively. The content information updating could be triggered by changes of content, cluster topology and device capability.
• Figure 2 illustrates a device for content information sharing according to one embodiment of the present invention.
• the device 200 for content information sharing comprises the following components.
• Communication Module 202 is responsible for interacting with other devices, sending messages and, receiving and dispatching message to internal components. Communication Module 202 will process the following messages.
• Requesting device sends this message to requested device to ask for shared content information. It contains information of clusters that requesting device belongs to, media capability and system capability of requesting device.
• Requested device sends this message in response to CONTENT_REQUEST. It contains all the information of shared content that could be rendered by requesting device according to device capability. NOTIFY_REFRESH
• This message is sent to other devices to notify the changes of local content.
• xCP Cluster Management Module This module maintains information of xCP clusters that local device belongs to.
• the cluster is built based on broadcast encryption mechanism, and contains all the authorized devices among those the content could be shared.
• the change of cluster topology for example, new device joining and device leaving, will also trigger the notification to other devices, and a transaction of content information updating within cluster.
• This module acts as a virtual media player and manages all the media players (210) that could be used to render xCP content shared within clusters. It collects all the media capability information from managed media players, including support media type and input mode. It triggers a transaction of content information updating to other devices when local media capability changed.
• This module maintains all the local system capability related information, including CPU information, memory, network connection of the device, size and color set of display, etc. It triggers a transaction of content information updating to other devices when system capability changed.
• xCP Content Management Module 208 manages all the local encrypted xCP content stored in local content repository (218) and could provide local content information, for example content name, type, size, etc. to content information handler 204 and content information filter 205. It triggers a transaction of content information updating to other devices within cluster when local content changed, for example, new content is ingested. Preferably, these sharable contents are protected with broadcast encryption.
• Content Information Handler 204 is responsible for the following tasks. Content Information Handler 204 receives and responds to a user request or request from outside applications, change of local device capability and changes of cluster topology, and sends a content information request to collect content information shared within private network and merge the information with local content information.
• Content Information Filter 205 filters local content information using device capability information, e.g. system capability information and media processing capability information attached in CONTENT_REQUEST message.
• device capability information e.g. system capability information and media processing capability information attached in CONTENT_REQUEST message.
• a device for content information sharing is provided; said device is a first device, said first device preferably comprises: a communication module 202, for exchanging information with at least a second device via a network, and receiving a content information request from the second device; a content management module 208, for managing the content information of the content that the first device could provide; the content information request from the second device comprising the capability information of the second device, and said first device further comprising: a content information filter 205, for filtering the content information of the content that the first device could provide according to the capability information of the second device, and sending the filtered content information of the content that the first device could provide to the second device.
• another device for content information sharing is provided; said device is a first device, said first device comprises: a communication module 202, for exchange information with a second device via a network; a device capability management module 206 or 207, for managing the capability information of the first device; and a content information handler 204, for generating a content information request according to the capability information of the first device, sending the request to a second device in a network, and receiving content information from said second device via the communication module 202, said returned content information is obtained by the second device filtering the content information of the content that the second device could provide according to the capability information of the first device.
• This first device is suitable for requesting other devices returning content information as required.
• Figure 3 illustrates a flowchart for content information sharing according to another embodiment of the present invention. Following local events may trigger the process to collect content information within private network.
• User request wherein the user could be an end user or an application.
• System capability change for example, change of one or more of the CPU capability information, local storage quota, addition of memory and storage means, network connection information and displayer information of the device.
• Media capability change for example, installing and removing content processing software, e.g. media player.
• the 380 receives request for collecting content information from a user. Or at step S302, when the device capability of the local device 380 changes, e.g. the system capability or media processing capability changes, Media Processing Capability Management Module 206 or System Capability Management Module 207 sends a request for updating content information to the Content Information Handler 204.
• the Content Information Handler 204 obtains from the xCP Cluster Management Module 203 all the related cluster information of the cluster that this local device belongs to.
• the Content Information Handler 204 obtains from the xCP Cluster Management Module 203 the addresses of all the authorized devices (or xCP devices) in the cluster or in the related clusters.
• the Content Information Handler 204 sends content information request to remote devices according to the addresses via the communication module 202.
• the step S305 further comprises steps S306-S312.
• the local device 380 might send the request to other devices by other means, e.g. by broadcasting the request to other devices (e.g. the remote device 390) .
• the Content Information Handler 204 obtains the local media processing capability information from the Media Capability
• the Content Information Handler 204 obtains the local system capability information from the System Capability Management Module 207. Then, at step S308, the Content Information Handler 204 add the local system capability information and the local media processing capability information to the content information request message CONTENT_INFO_REQUEST, and sends the message via the Communication Module 202 to other connected devices, e.g. the remote device 390.
• the remote device will carry out steps S309-S312. At step S309, the remote device receives the content information request message
• the content information filter of the remote device obtains its local content information from its xCP content management module.
• the content information filter of the remote device filters the local content information of the remote device 390 according to the system capability information and the media capability information of the device 380 in the content information request message CONTENT_INFO_REQUEST.
• the remote device sends the filtered local content information to the content information requester, the device 380.
• the Content Information Handler 204 of the local device 380 check whether responses are received from all the requested devices.
• step S314 If yes, then process step S314; if no, then repeat the steps S306-S308 at the requesting device, while non-responding remote devices process steps S309-S312.
• the Content Information Handler 204 provides the remote device content information and local content information to the user.
• the requesting device 380 obtains the content information of the content it can process or display.
• the user of the local device 380 might request contents suitable for its system capability via proper means as required.
• the requested content will be suitable for its system, and its local media player can display the content.
• step S314 might be carried out during the time when steps S306-S313 are repeated.
• the method for content information sharing illustrated in figure is only for explaining, not for limiting the present invention.
• the method for content information sharing of the present invention preferably comprises: step S309, a first device receiving a content information request from at least a second device via a network, said content information request comprises the capability information of the second device; step S310, said first device retrieving the information of the content that the first device could provide; step S311, said first device filtering the content information of the content that the first device could provide according to the capability information of the second device; and step S312, said first device sending the filtered content information of the content that the first device could provide to the second device.
• another method for content information sharing of the present invention comprises: step S306 and/or step S307, a first device sending a content information request to a second device via a network, said content information request comprises the capability information of the first device; said first device receiving content information from said second device, said content information is obtained by the second device filtering the content information of the content that the second device could provide according to the capability information of the first device.
• remote events may trigger content information updating within private network: e.g. notification of change of content on remote device, notification of change of cluster topology.
• Figure 4 illustrates a flowchart for content information updating in a private network according to a further embodiment of the present invention.
• the content information will be updated in the private network.
• the content information handler of device B receives from its xCP content management module the information that its local content changes.
• the device B obtains cluster information related with the device B in the private network.
• device B obtains all the addresses of all the authorized devices (or xCP devices) in the clusters related with device B.
• device B generates an update message NOTIFY_REFRESH and sends it to the above devices.
• other devices e.g. device A in the figure
• receive the update message NOTIFY_REFRESH receive the update message NOTIFY_REFRESH.
• device A as a local device and device B as a remote device will carry out content information request process similar to the above step S305.
• the device A as a local device will carry out procedures similar to steps S306-S308 of figure 3; and device B as a remote device will carry out procedures similar to steps S309-S312 of figure 3.
• the content changes in a device in the private network is broadcast to related devices in the network, and the related device will update the resource information it could utilize in the network.
• a new device is authorized and added in the xCP cluster, or a device belonging to the cluster is physically reconnected to the private network of the cluster.
• a device logically leaves the cluster, or a device physically disconnects to the private network of the cluster.
• Figure 4 also shows the process for updating content information when the cluster topology changes.
• the xCP cluster management module of device A informs the content information handler to carry out corresponding process.
• the information of cluster topology change might be obtained from the following ways.
• the device A periodically or intermittently communicates with other cluster devices to explore cluster topology changes.
• the device which caused the cluster topology change sends message to other devices.
• the information of cluster topology change might also be obtained by other means known to a person skilled in the art.
• device A receives a cluster topology change notification.
• the type of cluster topology change is identified.
• step S416 If a remote device logically leaves the cluster, or a remote device physically disconnect from the private network of the cluster, then execute step S416, device A cancels the content information related to the remote device. If a new device is authorized to join the xCP cluster, or a device belonging to the cluster reconnects to the private network of the cluster, then execute step S418, device A and the remote device will execute content information request similar to the above step S305.
• Device A as a local device executes steps similar to the above steps S306-S308, the remote device executes steps similar to the above steps S309-S312.

Landscapes

• Engineering & Computer Science (AREA)
• Computer Networks & Wireless Communication (AREA)
• Signal Processing (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• Databases & Information Systems (AREA)
• General Physics & Mathematics (AREA)
• Data Mining & Analysis (AREA)
• Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
• Storage Device Security (AREA)
• Information Transfer Between Computers (AREA)
• Computer And Data Communications (AREA)

Priority Applications (6)

Applications Claiming Priority (2)

Publications (1)

Family

ID=35999535

Family Applications (1)

Country Status (8)

Cited By (9)

Families Citing this family (1)

Citations (8)

Family Cites Families (1)

• 2004
  • 2004-12-29 CN CNA2004101029963A patent/CN1798048A/zh active Pending
• 2005
  • 2005-12-22 JP JP2007548810A patent/JP2008532102A/ja active Pending
  • 2005-12-22 WO PCT/EP2005/057101 patent/WO2006069967A1/en active Application Filing
  • 2005-12-22 CA CA002585723A patent/CA2585723A1/en not_active Abandoned
  • 2005-12-22 EP EP05821594A patent/EP1831802A1/en not_active Withdrawn
  • 2005-12-22 BR BRPI0519669-8A patent/BRPI0519669A2/pt not_active IP Right Cessation
  • 2005-12-22 AU AU2005321287A patent/AU2005321287B2/en not_active Ceased
  • 2005-12-22 MX MX2007008014A patent/MX2007008014A/es not_active Application Discontinuation

Patent Citations (8)

Non-Patent Citations (1)

Also Published As

Similar Documents

Legal Events