Method and apparatus for extending protected content access with peer to peer applications

[0001] The present invention relates generally to providing content access protection and, more particularly, to providing content access protection with a common set of peer-to-peer interfaces.

[0002] There have been many advances in consumer electronics devices. Consumer electronics devices may include devices such as cellular telephones, pagers, digital cameras, personal digital assistants (PDAs), remote controls, and the like.

[0003] In addition to becoming smaller, an increasing number of consumer electronic devices are network enabled and capable of accessing Web services through the Internet operated by the device vendor and/or third parties. With their ability to access the Internet directly, these consumer electronic devices will no longer rely on the traditional personal computer as intermediary device.

[0004] Once consumer electronics devices have their own network interfaces, in addition to communicating to other devices as a client from a client-server relationship, these interfaces can also be used for device-to-device, so-called peer-to-peer, communication.

[0005] Due to a variety of peer-to-peer protocols which can be customized for particular consumer electronics devices, there are challenges associated with offering applications which can be utilized by consumer electronic devices having different communications protocols.

[0006] The invention illustrates a system and method of sharing content with multiple peer device while protecting the content from unauthorized use. In one embodiment, the system and method comprises: identifying a plurality of peer devices within a predetermined area wherein each of the plurality of peer devices includes an interface framework; directly transmitting content among the plurality of devices; and a selected plurality of peer devices requesting a license from a digital rights management server for the content, wherein the selected plurality of peer devices possess the content, wherein the interface framework is configured to allow the plurality of peer devices to directly communicate and utilize an application

[0007] Other aspects and advantages of the invention will become apparent from the following detailed description, taken in conjunction with the accompanying drawings, illustrated by way of example of the principles of the invention.

[0008] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate one embodiment of the invention and, together with the description, explain one embodiment of the invention. In the drawings,

[0009] FIG. 1A is a diagram illustrating an environment within which the invention may be implemented.

[0010] FIG. 1B is a diagram illustrating an environment within which the invention may be implemented.

[0011] FIG. 2 is a simplified block diagram illustrating one embodiment in which the invention may be implemented.

[0012] FIG. 3 is a simplified block diagram illustrating an interface framework, consistent with one embodiment of the invention.

[0013] FIG. 4 is a simplified block diagram illustrating a system overview, consistent with one embodiment of the invention.

[0014] FIG. 5 is a simplified block diagram illustrating a system overview, consistent with one embodiment of the invention.

[0015] FIG. 6 is a system diagram consistent with one embodiment of the invention.

[0016] FIG. 7 illustrates a flow diagram for performing a peer-to-peer exchange according to one embodiment of the invention.

[0017] FIG. 8 illustrates a flow diagram for performing a peer-to-peer exchange according to one embodiment of the invention.

[0018] FIG. 9 illustrates a flow diagram for performing a peer-to-peer exchange according to one embodiment of the invention.

[0019] FIG. 10 illustrates a flow diagram for performing a peer-to-peer exchange according to one embodiment of the invention.

[0020] FIG. 11 illustrates a flow diagram for performing a peer-to-peer exchange according to one embodiment of the invention.

[0021] The following detailed description of the invention refers to the accompanying drawings. The detailed description does not limit the invention. Instead, the scope of the invention is defined by the appended claims and equivalents.

[0022] The invention includes methods and apparatus for providing seamless and universal interfaces for consumer electronic devices. The invention also includes methods and apparatus for enabling a variety of different interfaces from various consumer electronic devices to communicate with each other. Through the invention, the consumer electronic devices may leverage the flexibility of peer-to-peer communication while still ensuring protection for digital content through unified digital rights management.

[0023] Direct communication from one device to another enables a variety of features such as instant messaging, content distribution, and special community features. Further, integration of digital rights management functions within each consumer electronics device prevents unauthorized use of protected content. In one embodiment, content distribution involves the distribution of content directly from one consumer to another consumer through a peer device while still retaining digital rights management functions. In one embodiment, special community features include features such as recommendations, collaborative filtering, and affinity matching.

[0024] In one embodiment, the invention streamlines the integration of peer-to-peer functionality into content-based services and applications by utilizing plug-ins. In one embodiment, the plug-in encapsulates an existing peer to peer protocol and expresses it via high-level interfaces that can be accessed by applications. For example, an existing peer-to-peer protocol may include a file sharing protocol or an instant messaging protocol.

[0025] In one embodiment, the plug-ins also insulate developers from specific peer to peer protocols. According to one embodiment of the invention, the interfaces are designed to be protocol-agnostic and allow developers to easily switch protocols, to build protocol bridges, or to build multi-headed clients while using a common interface core on the peer devices.

[0026] In one embodiment, the invention is capable of integrating multiple functionalities such as content, communication and community within a peer device.

[0027] With respect to content, peer-to-peer content distribution allows content to be obtained from peer devices in addition to central content servers. Peer to peer distribution may result in reduced costs to the service provider and also improved response for consumers. When coupled with communication and community, the ability to move content directly between peer devices gives the basis of the viral-like form of content distribution known as superdistribution and content distribution networking. The invention also integrates digital rights management functions which ensures that unauthorized use of protected content is prevented.

[0028] With respect to communication, instant messaging, voice over IP and other types of real-time communication may rely on peer-to-peer connectivity. Some instant messaging systems use proprietary protocols. In one embodiment, the invention provides multi-headed clients to bridge the different propriety instant messaging systems on a single peer device.

[0029] With respect to community, various features may tend to have interfaces which are proprietary and application specific. The various features include special interest groups, collaborative filtering (e.g., using group ratings to help find content), affinity matching (e.g., matching users based on preferences), playlist sharing, and sending and receiving recommendations.

[0030] In one embodiment, the invention supports proprietary or specialized interfaces to communicate with the various applications and/or services as well standardized interfaces to communicate with other peer devices.

[0031] Those skilled in the art will recognize that many other implementations are possible, consistent with the present invention.

[0032] A. Environment and Architecture

[0033] FIG. 1A is a diagram illustrating an environment within which the invention may be implemented. The environment includes a client 110, a network 120, and a server 130.

[0034] The client 110 may be a consumer electronics device. The consumer electronics device includes an interface framework which allows the unique interface protocol of the electronics device to seamless communicate with the server 130. Specifics of the interface framework are discussed below.

[0035] The network 120 interfaces with both the client 110 and the server 130. In one embodiment, the network 120 is the Internet. In another embodiment, the network 120 may be any transmission medium between the client 110 and the server 130.

[0036] The sever 130 is a device configured to interface with the client 110 through the network 120.

[0037] The client 110 and/or the server 130 may include a combination of software, hardware, and/or firmware to provide customized financing applications.

[0038] FIG. 1B is a diagram illustrating an environment within which the invention may be implemented. The environment includes a client 140, a network 150, and a client 160.

[0039] The clients 140 and 160 may each be a consumer electronics device. The consumer electronics device includes an interface framework which allows the clients 140 and 160 to seamlessly communicate with each other through a common set of protocols. Specifics of the interface framework are discussed below.

[0040] The network 150 interfaces with both the client 140 and the client 160. In one embodiment, the network 150 is the Internet. In another embodiment, the network 150 may be any transmission medium between the client 140 and the client 160.

[0041] The client 140 and/or the client 160 may include a combination of software, hardware, and/or firmware to provide the interface framework.

[0042] FIG. 2 is a simplified diagram illustrating an exemplary architecture in which the present invention may be implemented. The exemplary architecture includes a plurality of client devices 202, a server device 210, and a network 201. In one embodiment, the network 201 may be the Internet. The plurality of client devices 202 are each configured to include a computer-readable medium 209, such as random access memory, coupled to a processor 208. Processor 208 executes program instructions stored in the computer-readable medium 209. In another embodiment, the plurality of client devices 202 may also include a number of additional external or internal devices, such as, without limitation, a mouse, a CD-ROM, a keyboard, and a display.

[0043] The interface framework may be stored on the plurality of client devices 202 within each computer-readable medium 209.

[0044] Similar to the plurality of client devices 202, the server device 210 may include a processor 211 coupled to a computer-readable medium 212. The server device 210 may also include a number of additional external or internal devices, such as, without limitation, a secondary storage element, such as database 240.

[0045] The interface framework may be stored on the server device 210 within each computer-readable medium 212.

[0046] The plurality of client processors 208 and the server processor 211 can be any of a number of well known computer processors, such as processors from Intel Corporation, of Santa Clara, Calif. In general, the plurality of client devices 202 may be any type of computing platform connected to a network and that interacts with application programs, such as a digital assistant or a smart cellular telephone or pager. The server 210, although depicted as a single computer system, may be implemented as a network of computer processors.

[0047] The plurality of client devices 202 and the server 210 may include the interface framework. In one embodiment, the plurality of computer-readable medium 209 and 212 may contain, in part, the interface framework. Additionally, the plurality of client devices 202 and the server 210 are configured to receive and transmit electronic messages for use with the interface framework. Similarly, the network 201 is configured to transmit electronic messages for use with the interface framework.

[0048] FIG. 3 illustrates one embodiment of an interface framework 300. The interface framework 300 includes a manager 305, a framework application program interface 310, a plurality of interfaces 315, a plug-in programmer interface 320, a plurality of plug-ins 330, and a framework protocol 335.

[0049] In one embodiment, the manager 305 is configured to coordinate tasks, requests and communications between the framework application program interface 310, the plurality of interfaces 315, the plug-in programmer interface 320, the plurality of plug-ins 330, and the framework protocol 335.

[0050] In one embodiment, the manager 305 is configured to install, configure, and run the plurality of plug-ins 330. In one embodiment, the manager 305 also utilizes the framework protocol 335 to communicate with the interface framework 300 running on other devices. In one embodiment, the framework protocol 335 allows one device with the interface framework 300 to determine specific plug-ins which are installed on another device with the interface framework 300.

[0051] In one embodiment, the framework application program interface 310 is configured to communicate between the interface framework 300 and a device such as a consumer electronic device.

[0052] In one embodiment, the plurality of interfaces 315 are configured to be utilized by various applications for accessing the functionality of the plurality of plug-ins 330. In one embodiment, the plurality of interfaces 315 may include the functions of search, transfer, group manager, session manager, device group, proximity group, content distribution network group, instant messaging group, remote player, and the like.

[0053] In one embodiment, the plug-in programmer interface 320 is configured to communicate between the plurality of interfaces 315 and the plurality of plug-ins 330.

[0054] In one embodiment, each the plurality of plug-ins 330 implements a particular peer-to-peer protocol. For example, a plug-in may be configured to implement the distribution protocol such as the Napster protocol, or the Gnutella protocol in one embodiment. In another embodiment, a plug-in may be configured to implement a peer-to-peer content distribution network such as Gnutella and Napster.

[0055] In one embodiment, the plurality of plug-ins 330 includes a plurality of adaptors 325 and a plurality of native protocols 340. Each of the plurality of adaptors 325 is configured to integrate a corresponding one of the plurality of native protocols 340 into the interface framework 300.

[0056] In one embodiment, the plurality of adapters 325 include a remote player plug-in, a device plug-in, a proximity plug-in, an instant messaging plug-in, a content distribution network plug-in, and the like.

[0057] In one embodiment, the plurality of native protocols 340 is configured to correspond with an adaptor. For example, a device control protocol is an exemplary native protocol 340 which corresponds with the remote player plug-in. A directory protocol is an exemplary native protocol 340 which corresponds with the device plug-in. A discovery protocol is an exemplary native protocol 340 which corresponds with the proximity plug-in. An instant messaging protocol is an exemplary native protocol 340 which corresponds with the instant messaging plug-in. A peer-to-peer content distribution network protocol is an exemplary native protocol 340 which corresponds with the content distribution network plug-in.

[0058] In one embodiment, the plug-in programmer interface 320 is utilized to access both internal functionality and external functionality of the interface framework 300 to develop the plurality of adaptors 325.

[0059] In one embodiment, the plurality of plug-ins 330 provide functionality to applications outside the interface framework 300 via the plurality of interfaces 315. In one embodiment, the plurality of interfaces 315 are defined by the interface framework 300 and implemented by the plurality of plug-ins 330.

[0060] In one embodiment, the plurality of plug-ins 330 are configured to provide developers with a set of high-level application program interfaces. In one embodiment, developers are not concerned with the details of the underlying protocols and can easily add functionality to their applications by use of the plurality of plug-ins 330.

[0061] The specific plurality of interfaces 315, plurality of adaptors 325, plurality of native protocols 340 are shown for exemplary purposes and are not intended to limit the invention. Similarly, various elements are shown included within the interface framework 300 for exemplary purposes; additional elements may be added, elements may be deleted, and elements may be combined without departing from the scope of the invention.

[0062] FIG. 4 illustrates one embodiment of a system 400. The system 400 includes platform components 410, an interface framework 415, and an operating system 495. The system 400 illustrates one embodiment of the interface framework 415 communicating with external components such as the platform components 410. In one embodiment, the platform components 410 may include a content manager, a network manager, a user manager, and a digital rights manager.

[0063] In one embodiment, the interface framework 415 includes a platform component adaptor 420, a platform component interface 430, an interface framework applications program interface 440, a core module 450, a plurality of plug-in adaptors 460, a plurality of internal plug-ins 470, a plurality of external plug-ins 480, and an XML module 490.

[0064] In one embodiment, the plurality of plug-ins 470 and 480 may need to access the platform components 410. To facilitate access to the platform components 410, the platform component interface 430 is utilized to encapsulate the components within the platform components 410.

[0065] In one embodiment, a portion of the platform component adaptor 420, the platform component interface 430, the interface framework applications program interface 440, the core module 450, the plurality of plug-in adaptors 460, the plurality of internal plug-ins 470, and a portion of the XML module 490 are platform independent. In one embodiment, portion of the platform component adaptor 420, the plurality of external plug-ins 480, and a portion of the XML module 490 are implemented for specific platforms. For example, the plurality of external plug-ins 480 are developed independently of the interface framework 415 and later integrated within the interface framework 415. In one embodiment, the plurality of internal plug-ins 470 are developed utilizing the tools within the interface framework 415.

[0066] In one embodiment, the platform component interface 430 increases the portability of the interface framework 415 by shielding the plurality of plug-ins 470 and 480 from changes to the platform components 410.

[0067] For example, the content manager within the platform components 410 which is utilized by a music jukebox application will likely differ from the content manager utilized by a video application. However in this example, both the music jukebox application and the video application may expose their unique content managers to one of the plurality of plug-ins 470 and 480 that would facilitate sharing the content from each respective content manager.

[0068] FIG. 5 illustrates one embodiment of a consumer electronics device 500. The electronics device 500 is a networked portable player in one embodiment. The networked portable player is configured to communicate with other networked portable players, exchange content with other networked portable players, store content, play content, and ensure authorized access to protected content.

[0069] The device 500 includes a user interface 505, application logic module 510, a taste engine 515, a content manager 520, a community module 530, a license manager 535, a content player 540, a digital rights manager 545, an XML module 575, and an interface framework 580.

[0070] In one embodiment, the user interface 505 is configured to accept input from a user of the device. Similarly, the user interface 505 is also configured to display information to the user.

[0071] In one embodiment, the application logic module 510 is configured to coordinate the functions of the taste engine 515, the content manager 520, the community module 530, the license manager 535, the content player 540, the digital rights manager 545, the XML module 575, and the interface framework 580. For example, the application logic module 510 coordinates authenticating a license by the license manager 535 for a particular content prior to playing the particular content on the content player 540.

[0072] In one embodiment, the taste engine 515 monitors a user's interaction with the device 500 and captures the content that the user accesses. The taste engine also builds a profile of the user based on the actions of the user and the content that is accessed.

[0073] In one embodiment, the content manager 520 is configured to track and catalog content within the device 500. The content manager 520 is also configured to interface with the digital rights manager 545 in one embodiment.

[0074] In one embodiment, the community module 530 tracks and polls other device within a predetermined range. In another embodiment, the community module 530 selectively tracks the status of predetermined devices such as on/off status, in/out of range status, and the like.

[0075] In one embodiment, the license manager 535 tracks and stores the licenses which are within the device 500.

[0076] In one embodiment, the content player 540 plays the content within the device 500.

[0077] In one embodiment, the digital rights manager 545 places restrictions on utilizing content that is not properly licensed. In one embodiment, the digital rights manager is OpenMG X. In other embodiments, other digital rights management system may be utilized.

[0078] In one embodiment, the XML module 575 is configured to communicate with a remote server. The XML module 575 utilizes XMLRPC. However, SOAP, http, or IP/TCP could be used in alternate embodiments. The interface framework 580 is similar to the interface framework 300 described in FIG. 3. The interface framework 580 may also include plug-ins related to universal plug and play (UPnP), Simple Session Discovery Protocol (SSDP), instant messaging, content distribution networks, and file sharing applications.

[0079] FIG. 6 illustrates a simplified block diagram showing a system 600. The system 600 includes a digital rights system 602, servers to mediate peer connectivity 617, a network 635, and a plurality of networked portable players 640, 645, and 650. In one embodiment, the digital rights system 602, the peer connectivity module 617, and the plurality of networked portable players 640, 645, and 650 are configured to communicate with each other via the network 635. The plurality of networked portable players 640, 645, and 650 are also configured to communicate directly with each other without utilizing the network 635.

[0080] In one embodiment, the digital rights system 602 includes a content server 605, a license server 610, and a billing server 615. The digital rights system 602 is configured to ensure that only authorized content is allowed to be played on one of the plurality of networked portable players 640, 645, and 650.

[0081] In one embodiment, the content server 605 tracks the location of protected content. In another embodiment, the content server 605 transmits content to one of the plurality of networked portable players 640, 645, and 650.

[0082] In one embodiment, the license server 610 tracks and authenticates the licenses that allow corresponding content to be played on one of the plurality of networked portable players 640, 645, and 650.

[0083] In one embodiment, the billing server 615 tracks payment for licenses for corresponding content. In another embodiment, the billing server 615 is also configured to message one of the plurality of networked portable players 640, 645, and 650 to request payment for a license.

[0084] The peer connectivity module 617 includes an instant messaging server 620, a content distribution network server 625, and a community server 630. In one embodiment, the instant messaging server 620 may utilize any known messaging application such as Yahoo Messenger, MSN Messenger, and the like. In one embodiment, the content distribution network server 625 may utilize commercial content distribution networks such as Napster. In one embodiment, there is no content distribution network server and content and the networked portable players support a server-less content distribution protocol such as Gnutella or FastTrack. Each of the plurality of networked portable players 640, 645, and 650 may be represented by the device 500 as shown in FIG. 5.

[0085] B. Operation

[0086] The flow diagrams as depicted in FIGS. 7, 8, 9, 10, and 11 illustrate merely one embodiment of the invention. The flow diagrams in FIGS. 7, 8, 9, 10, and 11 are one particular use of the invention based on a specific application. In other embodiments, the invention may be utilized with other applications. The blocks within the flow diagrams may be performed in a different sequence without departing from the spirit of the invention. Further, blocks may be deleted, added, or combined within each of the flow diagrams without departing from the spirit of the invention.

[0087] The flow diagram in FIG. 7 illustrates interactions with multiple devices utilizing the interface framework and a digital rights management server according to one embodiment.

[0088] In Block 710, peer devices that wish to interact are identified. In one embodiment, the interface framework within each device is initiated. In one embodiment, the peer device may be a networked portable player.

[0089] In one embodiment, a unique identification corresponding to each of the peer devices is confirmed. In one embodiment, each device has an identification such as a serial number which uniquely identifies a device.

[0090] In Block 720, the peer devices exchange data. In one embodiment, the peer devices exchange metadata with each other. The metadata may include content listing within each device, device identification, licensing information corresponding with the content, contact lists, instant messaging lists, and user profile information such as the sex of the user, age of the user, name of the user, location of the user, and interests of the user.

[0091] In Block 730, content is moved from a lender device to a borrower device. In one embodiment, the content is protected content such as music, movies, and the like. In one embodiment, the content is copied from the lender device to the borrower device, and the content is removed from the lender device. For example, without the content on the lender device, the lender device may not utilize the content.

[0092] In Block 740, a license is moved from the lender device to the borrower device. The license corresponds to the content moved from the lender device to the borrower device. In one embodiment, the license is copied from the lender device to the borrower device, and the license is removed from the lender device. For example, without the license on the lender device, the lender device may not utilize the content even if the content is currently within the lender device.

[0093] In Block 750, the transfer of the content and the license is reported to a digital rights management server. The information reported to the digital rights management may include the device identification of the borrower device and identification of the content.

[0094] The digital rights management server may bill the lender device and/or the borrower device. In one embodiment, a provisional license may be issued to the borrower device for a predetermined length of time, for a predetermined number of plays, or another restrictive measure.

[0095] In another embodiment, a full license may be issued to the borrower device with no restrictions. In one embodiment, if the content and license are transferred to the borrower device and sufficient payment is not made, the lender device is responsible for completing the payment. Otherwise, the content and corresponding license may be deactivated even for the lender device.

[0096] In one embodiment, a license is not need to preview content. For example, if a license is not issued, small sample sized portions of the content may be played for previewing the content.

[0097] In one embodiment, the transfer may be reported by the lender device. In another embodiment, the transfer may be reported by the borrower device.

[0098] In Block 760, an automatic return of the content may be performed. In one embodiment, the lender device, the borrower device, and/or the digital rights management server may store the transfer of the content from the lender device to the borrower device. By storing the transfer information of the content, the content along with the corresponding license may be returned to the lender device.

[0099] In one embodiment, the return of the content and corresponding license may occur automatically after a predetermined amount of time, a predetermined number of plays, and the like. The automatic return of the content and corresponding license also may occur if payment is not made to the digital rights management server.

[0100] In one embodiment, the lender device and the borrower device are located in proximity to each other such that direct transfer between the lender device and the borrower device are possible. In another embodiment, the lender device and the borrower device are on each other's contact list.

[0101] In another embodiment, the borrower device may transfer an additional content and corresponding license to the lender device. For example, in this embodiment, the borrower device and the lender device effectively both serve as a borrowing and lending party.

[0102] The flow diagram in FIG. 8 illustrates interactions with multiple devices utilizing the interface framework and a digital rights management server according to one embodiment.

[0103] In Block 810, peer devices that wish to interact are identified. In one embodiment, the interface framework within each device is initiated. In one embodiment, the peer device may be a networked portable player.

[0104] In one embodiment, a unique identification corresponding to each of the peer devices is confirmed. In one embodiment, each device has an identification such as a serial number which uniquely identifies a device.

[0105] In Block 820, the peer devices exchange data. In one embodiment, the peer devices exchange metadata with each other. The metadata may include content listing within each device, device identification, licensing information corresponding with the content, contact lists, instant messaging lists, and user profile information such as the sex of the user, age of the user, name of the user, location of the user, and interests of the user.

[0106] In Block 830, content is copied from an originating device to at least one receiving device. In one embodiment, the content is protected content such as music, movies, and the like. In one embodiment, there are multiple receiving devices.

[0107] In one embodiment, the content is copied from the originating device to the receiving device, and the content remains on the originating device.

[0108] In Block 840, a license is moved from the originating device to the receiving device. The license corresponds to the content copied from the originating device to the receiving device. In one embodiment, the license is copied from the originating device to the lending device, and the license is removed from the originating device. For example, without the license on the originating device, the originating device may not utilize the content even if the content is currently within the originating device.

[0109] In one embodiment, the license may be moved multiple times if there are multiple receiving devices.

[0110] In Block 850, an automatic return of the license may be performed. In one embodiment, the originating device and/or the receiving device(s) may store the transfer of the license from the originating device to the receiving device. By storing the transfer information of the license, the license may be returned to the originating device.

[0111] In one embodiment, the return of the license may occur automatically after a predetermined amount of time, a predetermined number of plays, and the like.

[0112] In one embodiment, the originating device and the receiving device(s) are located in proximity to each other such that direct transfer between the originating device and the receiving device(s) are possible. In another embodiment, the originating device and the receiving device(s) are on each other's contact list.

[0113] The flow diagram in FIG. 9 illustrates interactions with multiple devices utilizing the interface framework and a digital rights management server according to one embodiment.

[0114] In Block 910, peer devices that wish to interact are identified. In one embodiment, the interface framework within each device is initiated. In one embodiment, the peer device may be a networked portable player.

[0115] In one embodiment, a unique identification corresponding to each of the peer devices is confirmed. In one embodiment, each device has an identification such as a serial number which uniquely identifies a device.

[0116] In Block 920, the peer devices exchange data. In one embodiment, the peer devices exchange metadata with each other. The metadata may include content listing within each device, device identification, licensing information corresponding with the content, contact lists, instant messaging lists, and user profile information such as the sex of the user, age of the user, name of the user, location of the user, and interests of the user.

[0117] In Block 930, content is copied from a distribution device to a purchaser device. In one embodiment, the content is protected content such as music, movies, and the like.

[0118] In Block 940, the purchaser device is authenticated. In one embodiment, the purchaser device is authenticated through the device identification. In another embodiment, the user of the purchaser device is authenticated via a biometric parameter, a personal information number, a password and the like. The biometric parameter may include a finger print, an iris scan, or a DNA sample.

[0119] One reason for peer authentication is so that that the purchaser can provide a history of the license when the licensing/billing system is contacted by the purchaser. For example, the purchase can relay information relating to the content provider device, and the content provider device may receive a credit as an incentive for sharing the content.

[0120] The purchaser also is authenticated for the billing system when making a purchase. Accordingly, there may be two stages of authentication: 1) authentication of content provider device to the purchaser and 2) authentication of the purchaser to the billing system. In Block 950, the purchaser device submits a payment to a digital rights management server for a license to use the content. In one embodiment, the payment may be a micropayment.

[0121] In one embodiment, a license is not need to preview content. For example, if a license is not issued, small sample sized portions of the content may be played for previewing the content.

[0122] In Block 960, the license corresponding with the content is received by the purchaser device. The license may be a provisional license or a full license.

[0123] In one embodiment, the distribution device and the purchaser device are located in proximity to each other such that direct transfer between the distribution device and the purchaser device are possible. In another embodiment, the distribution device and the purchaser device are on each other's contact list.

[0124] The flow diagram in FIG. 10 illustrates interactions with multiple devices utilizing the interface framework and a digital rights management server according to one embodiment.

[0125] In Block 1010, peer devices that wish to interact are identified. In one embodiment, the interface framework within each device is initiated. In one embodiment, the peer device may be a networked portable player.

[0126] In one embodiment, a unique identification corresponding to each of the peer devices is confirmed. In one embodiment, each device has an identification such as a serial number which uniquely identifies a device.

[0127] In Block 1020, the purchaser device initiates a content query. The content query may request the location and/or availability of specific content. In addition, the content query may be directed to another peer device such as a distribution device or to a remote server.

[0128] In Block 1030, content is copied from a distribution device to a purchaser device. In one embodiment, the content is protected content such as music, movies, and the like.

[0129] In Block 1040, the purchaser device is authenticated. In one embodiment, the purchaser device is authenticated through the device identification. In another embodiment, the user of the purchaser device is authenticated via a biometric parameter, a personal information number, a password and the like. The biometric parameter may include a finger print, an iris scan, or a DNA sample.

[0130] In Block 1050, the purchaser device receives a provisional license for the content. The provisional license may allow the use of the content by the purchaser for a predetermined length of time, for a predetermined number of plays, or a limited portion of the content may be available.

[0131] In Block 1060, the purchaser device submits a payment to a digital rights management server for a license to use the content. In one embodiment, the payment may be a micropayment.

[0132] In Block 1070, the license corresponding with the content is received by the purchaser device. The license may be a full license which allows unlimited use by the purchaser device.

[0133] In one embodiment, the distribution device and the purchaser device are located in proximity to each other such that direct transfer between the distribution device and the purchaser device are possible. In another embodiment, the distribution device and the purchaser device are on each other's contact list.

[0134] The flow diagram in FIG. 11 illustrates interactions with multiple devices utilizing the interface framework and a digital rights management server according to one embodiment.

[0135] In Block 1110, peer devices that wish to interact are identified. In one embodiment, the interface framework within each device is initiated. In one embodiment, the peer device may be a networked portable player.

[0136] In one embodiment, a unique identification corresponding to each of the peer devices is confirmed. In one embodiment, each device has an identification such as a serial number which uniquely identifies a device. The identified peer devices may form a peer group.

[0137] In Block 1120, a track list is exchanged among he peer devices within the peer group. In one embodiment, the track list is a listing of songs that are stored within the peer devices within the peer group.

[0138] In Block 1130, a track is identified from the track list by one of the devices within the peer group.

[0139] In Block 1140, the identified track is copied from an originating device to a receiving device. In one embodiment, the originating device may be one of a home stereo system, a computer, and the like. In one embodiment, the receiving device may be a networked portable player such as a personal digital assistant, an MP3 player, and the like. In one embodiment, the originating device and the receiving device communicate through a Bluetooth communication system or any other wireless protocol.

[0140] In Block 1150, the receiving device submits a payment to a digital rights management server for a license to use the selected track. In one embodiment, the payment may be a micropayment.

[0141] In one embodiment, a license is not need to preview content. For example, if a license is not issued, small sample sized portions of the selected track may be played for previewing the content.

[0142] In Block 1160, the license corresponding with the content is received by the purchaser device. The license may be a provisional license or a full license.

[0143] C. Conclusion

[0144] The foregoing descriptions of specific embodiments of the invention have been presented for purposes of illustration and description

[0145] They are not intended to be exhaustive or to limit the invention to the precise embodiments disclosed, and naturally many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to explain the principles of the invention and its practical application, to thereby enable others skilled in the art to best utilize the invention and various embodiments with various modifications as are suited to the particular use contemplated. It is intended that the scope of the invention be defined by the Claims appended hereto and their equivalents.