TECHNICAL FIELD

[001] This disclosure relates to the field of content sharing platforms and, in particular, to a user interface that supports access control technology for a peer-to-peer sharing system. BACKGROUND

10021 Content-sharing platforms and their corresponding websites and mobile applications ("apps ^" ) enabl e user devices to share and play streaming content, such as streaming music and video. Streaming content may require a large amount of bandwidth and some connections may not provide the bandwidth necessary to stream content. Content-sharing platforms may enable the user to download or offline the streaming content while using a higher bandwidth connection and enable the user to subsequently play the streaming content when the user device is disconnected or using a low bandwidth connection.

SUMMARY

10031 The follow ing is a simplified summary of the disclosure in order to provide a basic understanding of some aspects of the disclosure. This summary is not an extensive overview of the disclosure. It is intended to neither identify key or critical elements of the disclosure, nor delineate any scope of the particular implementations of the disclosure or any scope of the claims. Its sole purpose is to present some concepts of the di sclosure in a simplified form as a prelude to the more detailed description that is presented later.

10041 In an aspect of the disclosure, a method includes providing for display a user interface including a plurality of media items and a plurality of media availability indicators. A portion of the user interface may represent that an encrypted version of a media item and an encryption key are being received. The method may include updating a media avai lability indicator of the media item to represent that the encrypted version of the media item and the encryption key are saved. The method may further include receiving an indication that the encrypted version of the media item is decrypted and updating the media availability indicator to represent the media item is available to be experienced. In another

implementation, the media availability indicator may be used to distinguish between three states of the media item, a first state indicating the media item is not saved on a user device, a second state indicating the media item is saved in the encrypted version, and a third state indicating the media item is saved and available to be experienced. 10051 In one implementation, the user interlace may include a graphical control element to initiate the receiving of a wrapped version of the encryption key for the media item over a peer-to-peer connection. The user interface may indicate the peer-to-peer connection used to receive the encrypted version of the media item and may indicate that an internet connection is used to decrypt the media item, in a further implementation, the user interface may include a peer-to-peer connection indicator identifying a user device that is providing the encrypted version of the media item and identifying a user device that is receiving the encrypted version of the media item.

10061 In another implementation, each of the plurality of media items is represented within the user interface by a media entry comprising a first graphical portion and a second graphical portion . The first graphical portion may include an image of a respective media item and the second graphical portion may include textual information of the respective media item. In a further implementation, the method may involve receiving user input corresponding to a particular media item and initiating a presentation of the particular media item. The user interface may include a portion for the presenti ng of the particular media item on a user device.

[007] In further aspects of the disclosure, a system and/or a non-transitory machine- readable storage medium for storing instructions that cause a processing device to perform the above operations is disclosed.

BRI EF DESCRI PTION OF TH E DRAWINGS

10081 The present disclosure is il lustrated by way of example, and not by way of limitation, in the figures of the accompanying drawings.

100 1 FIG. 1 is a block diagram illustrating an exemplary system architecture, in accordance with an implementation of the disclosure.

[0010] FIG. 2 is a block diagram il lustrating the components and modules of an example user device, in accordance with an implementation of the disclosure.

[001 11 FIG. 3 is a flow diagram illustrati ng an example method of a media server, in accordance with an implementation of the disclosure.

[0012] FIG. 4 is a flow diagram illustrating an example method of a user device that provides a shared media item, in accordance with an implementation of the disclosure.

[0013] FIG. 5 is a flow diagram illustrating an example method of a user device that is receiving a shared media item, in accordance with an implementation of the disclosure. [0014] FIG. 6 A is an example graphical interface for enabling a user to interact with access control technology for peer-to-peer sharing, in accordance with an implementation of the disclosure.

10015] FIG. 6B is another example graphical interface for enabling a user to interact with access control technology for peer-to-peer sharing, in accordance with an implementation of the disclosure.

[0016] FIGS. 7 through 9 are example graphical interfaces for a user device that is providing a shared media item, in accordance with an implementation of the disclosure.

[0017] FIGS. 10 through 14 are exemplary graphical interfaces for a user device that is receiving a shared media item , in accordance with an implementation of the di sclosure.

[0018] FIG. 15 is a flow diagram illustrating an example method for providing a graphical interface enabling a user to interact with an access control technology for peer-to-peer sharing, in accordance with an implementation of the disclosure.

[0019] FIG. 16 is a block diagram illustrating one implementation of a computer system, in accordance with an implementation of the disclosure.

DETAI LED DESCRI PTION

[0020 j Aspects and implementations of the disclosure are directed to a user interface for peer-to-peer content sharing technology. The user interface enhances the user' s ability to share and receive media items using a peer-to-peer content sharing technology. Traditional content sharing technology may include centralized sharing systems that require a network connection with a large bandwidth in order to stream online content. In many emerging markets, the capabilities of the computing networks are limited and they often have low bandwidth, are unreliable, or unavailable. Peer-to-peer networking may allow for exchange of content when networking infrastructure or internet access is limited. A problem with peer- to-peer networking is that it often provides unrestricted reproduction and access to the exchanged content, which may be unauthorized by the content creators and/or providers and may be challenging to monitor or enforce.

[0021] Aspects of the present di sclosure address the above and other deficiencies by providing a user interface for a peer-to-peer sharing system that uses a centralized access control mechanism . The centralized access control mechanism may manage the access of user devices to media items stored on the user devices. The centralized access control mechanism may support one or more digital rights management (DRM) schemes to control the use, modification, and distribution of copyrighted media items. In one example, the content sharing technology may involve a media server and multiple user devices of different users. The media server may provide media items to a user dev ice of a first user ("first user dev ice ^" ) and enable the first user dev ice to share the media items with a user dev ice of a second user ("second user dev ice ^" ). The user dev ices may be mobile dev ices such as phones, tablets, or laptops and may be capable of storing the media items locally.

10022] In one example, the first user dev ice may stream the media item directly from the media server (e.g., over the Internet) and may store the streaming media locally. The first user dev ice may encrypt the media item using a locally generated encryption key and may wrap the encryption key using a public key from the media server. The first user dev ice may then transfer the encrypted media item and the wrapped encryption key to the second user dev ice (e.g., via a peer-to-peer connection when the first user dev ice and/or the second user dev ice have limited or no Internet access). The second user device may access the encrypted media item but may be restricted from playing the encrypted media item until it contacts the media server. The second user dev ice may contact the media server using a playability request, which may include the wrapped encryption key and identification information for the media item. The media server may then perform a playability check to ensure that the second user dev ice is authorized to view the media item. The media server may then respond using a playability response that includes the unwrapped encryption key, which may enable the second user dev ice to decrypt and play the media item.

[0023] The peer-to-peer content sharing technology may i nclude one or more user interfaces that enable a user to control which media items are shared and represent the states of the shared media items. The states may correspond to the availability of the media item . For example, a first state may correspond to a media item that is being receiv ed or transferred to one of the user devices. A second state may indicate that an encrypted version of the media item and a corresponding w rapped encryption key are sav ed on the user device. The third state may indicate that the media item has been decrypted and is ready to be presented on the user dev ice. The user interface may be updated during use to modify the media item indicators so that they represent the current state of the media items. In other examples, the user interface may also indicate a peer-to-peer connection used to receive the encrypted version of the media item and indicate that an internet connection is used to decrypt the media item.

10024] The technology disclosed herein is advantageous because it enhances the ability of a user to share media items using peer-to-peer sharing technology with limited or no Internet access and also prov ide a central mechanism to manage and monitor access to the shared media items. The technology may decrease the amount of bandwidth necessary to share media items, which may be beneficial to the media server, intermediate networking infrastructure (e.g., Internet Service Providers (ISPs), and user devices and may be particularly beneficial in emerging markets. In the past, each of the user devices may have accessed the media item from the media server and now many of the user devices can access the media item from a peer and only contact the media server to receive authorization to view the media item. The amount of network traffic required to check the authorization may be orders of magnitude less than the amount of network traffic or bandwidth required to stream or download the media item from the media server. The technology is also advantageous because it may enhance the ability of the media server to determine viewership of a media item shared via a peer-to-peer connection, and provide supplemental media items (e.g., related videos).

[0025] Implementations of the disclosure often reference videos for simplicity and brevity. However, the teaching of the present disclosure are applied to media items generally and can be applied to various types of content or media items, including for example, video, audio, text, images, program instructions, etc.

[0026] FIG. 1 illustrates an example system architecture 100, in accordance with one implementation of the disclosure. The system architecture 00 includes media server 110, user devices 120A-Z, a peer-to-peer connection 130, a peer network 140, a network 150, and a data store 160.

[0027] Media server 110 may be one or more computing devices (such as a rackmount server, a router computer, a server computer, a personal computer, a mainframe computer, a laptop computer, a tablet computer, a desktop computer, etc.), data stores (e.g., hard disks, memories, databases), networks, software components, and/or hardware components that may be used to provide a user with access to media items and/or provide the media items to the user. Media server 110 may be a part of a content sharing platform that may allow users to consume, upload, share, search for, approve of ("like"), dislike, and/or comment on media items. The content sharing platform may also include a website (e.g., a webpage) or application back-end software that may be used to provide a user with access to the media items.

[0028] Media server 110 may host content, such as media items 112 and supplemental media items 1 14. Media items 1 12 and supplemental media items 1 14 may be digital content chosen by a user, digital content made available by a user, digital content uploaded by a user, digital content chosen by a content provider, digital content chosen by a broadcaster, etc. Examples of media items 1 1 2 and supplemental media items 1 14 include, and are not limited to, digital video, digital movies, digital photos, digital music, website content, social media updates, electronic books (ebooks), electronic magazines, digital newspapers, digital audio books, electronic journals, web blogs, real simple syndication (RSS) feeds, electronic comic books, software applicati ons, etc.

10029] Media items 1 12 and supplemental media items I 14 may be consumed via the Internet and/or via a mobile device application. For brevity and simplicity, an online video (also hereinafter referred to as a video) is used as an example of a media item 1 12 throughout this document. As used herein, "media," media item," "online media item," "digital media," "digital media item, ^{" "} 'content, ^" and "content item ^" can include an electronic file that can be executed or loaded using software, linn ware or hardware configured to present the digital media item to an entity. In one implementation, the content sharing platform may store the media items I 12 using the data store 160. In one example, media item 1 12 may be a user generated video identified by a user of user device 120 A and supplemental media item 1 1 2 may be an advertisement selected by media server 1 10 to be presented before, during or after presenting media item I 12 on one or more of the user dev ices 1 20 A -Z.

100301 User devices 120A-Z may each include computing devices such as personal computers (PCs), laptops, mobile phones, smart phones, tablet computers, netbook computers, network -connected televisions, etc. In some implementations, user devices 120A- Z may also be referred to as "client devices. ^" User devices 120A-Z may be capable of receiving media items 1 1 2 from media server 1 10 over a network 150 and capable of sharing media items 1 12 with other user devices via a peer-to-peer connection 130, a peer network 140, a network 150, or a combination thereof.

[0031] Peer-to-peer connection 130 may be any communication channel between one or more user devi ces 120A-Z. Peer-to-peer connection 130 may be based on any wireless or wired communication technology and may connect a first user device directly or indirectly (e.g., involving an intermediate user device) to a second user device. The wireless communication technology may include Bluetooth®, Wifi®, infrared, ultrasonic or other technology. The wired communication may include universal serial bus (USB), ethernet, RS 232, or other wired connection. In other examples, the peer-to-peer connection 130 may involve transporting a remov able storage medium between user dev ices to transfer media items and other data. The remov able storage medium may be in any form including a Secure Digital (SD) card, Multi Media Card (MMC), flash drive, other data storage device, or combination thereof. The peer-to-peer connection may be an individual connection between two devices or may comprise multiple connections that are part of peer network 140.

100321 Peer network 140 may be a computing network that provides one or more communication channels between user devices 120A-Z. In one example, peer network 140 may be a peer-to-peer network that does not rely on a pre-existing network infrastructure ( e.g., access points, switches, routers) and the user devices A-Z may replace the networking infrastructure to route communications between the user devices. Peer-to-peer network 140 may be an wireless network that is self-configuring and enables user devices 120 A-Z to contribute to peer netw ork 140 and dynamically connect and disconnect from peer network 140 (e.g., ad hoc wireless network). In another example, peer network 140 may be a computing netw ork that includes networking infrastructure that enables user devices to communicate with other user devices. In the latter example, peer network 140 may or may not have access to the public network (e.g., internet). For example, a vehicle (e.g., bus, train) or location (e.g. , classroom, library, cafe) may provide an access point or user device that may function as an access point to enable user devices to communicate with one another without providing internet access. Alternatively, the peer network may provide access to a larger network such as network 150 (e.g., internet).

[0033] Network 150 may be a public network that provides one or more of user devices 120 A-Z with access to media serv er 1 10 and other publically available computing devices. Network 150 may include one or more wide area netw orks (WANs), local area networks (LANs), wired networks (e.g., Ethernet network), wireless networks (e.g., an 802.1 1 network or a Wi-Fi network), cellular networks (e.g., a Long Term Ev olution (LTE) network), routers, hubs, switches, server computers, and/or a combination thereof.

10034 ] Each of user devices 120 A-Z may include a media viewer that allows users to view- media items 1 12 that are shared over peer network 140 and/or network 150. The media viewer may present images, videos, audio, web pages, documents, etc. In one example, the media viewer may be a web browser that can access, retrieve, present, and/or navigate content (e.g., web pages such as Hyper Text Markup Language (HTML) pages, digital media items, etc.) served by a web server. The media viewer may render, display, and/or present the content (e.g., a web page, a media viewer) to a user. The media viewer may also display an embedded media player (e.g., a Flash® player or an HTML5 player) that is embedded in a web page (e.g. , a web page that may provide information about a product sold by an online merchant). In another example, the media viewer may be a standalone application (e.g., a mobile application or app) that allows users to view digital media items (e.g., digital videos, digital images, electronic books, etc.).

[0035] According to aspects of the disclosure, the media viewer may be a content sharing platform application for users to share, record, edit, and/or upload content to the content sharing platform. The media viewer may be provided to user devices 120A-Z by media sei'ver 110 or a content sharing platfomi. For example, the media viewers may be embedded media players that are embedded in web pages provided by the content sharing platform. In another example, the media viewers may be applications that are installed and executed on user devices 120A-Z.

10036] In the example shown in Fig. 1, each user device may function as a media sharing device (e.g., user device 120A), a media recipient device (e.g., user device 120B), or a combination of both. Each user devi ce may include a data store 122, a sharing interface component 124, a provider component 126, a recipient component 128, and a data store 122.

[0037] Data store 122 may be a memoiy (e.g., random access memory), a drive (e.g., a hard drive, a flash drive), a database system, or another type of component or device capable of storing data. Data store 122 may include multiple storage components (e.g., multiple drives or multiple databases) that may span multiple computing devices (e.g., multiple serv er computers). Data store 122 may include a media cache 123 that stores copies of media items that are received from the media server 110. In one example, each media item 112 may be a file that is downloaded from media server 1 10 and may be stored locally in media cache 123. In another example, each media item I 12 may be streamed from media server 1 10 and may exist as an ephemeral copy in memory of a user device until it is off-lined. Off-lining refers to a user device storing an ephemeral copy of the streaming media in persistent data storage of the user device. This may enable the user device to access the streamed media item at a later point in time (e.g., after a reboot) without using an internet connection. In one example, the media item may be streamed by the user device to itself when presenting the media item. In one example, a user device may off-line a streamed media item by copying one or more streams of a media item (e.g., video stream, audio stream) to the persistent data storage.

[0038] Sharing interface component 124 may provide a user interface that enables a user to select one or more user devices to be involved with sharing media items. Sharing interface component 124 may provide a user interface that enables a user to select one or more media items from a media cache to be shared. The media items may be available within the media cache of the local user device or the media cache of a remote user device. The user interface may enable the user to identify the state of media items and whether they are saved on the local user device and whether they need to be decrypted before being available for consumption. Example user interfaces will be discussed in more detail in regards to Figs. 6A-14.

[0039] Provider component 126 may include functionality that enables the user device to share media items to one or more other user devices. The provider component 126 may generate an encryption key and encrypt a media item to reduce unauthorized access to the media item. Provider component 126 may also wrap the encryption key and may share the wrapped encryption key and the encry pted media item with one or more other user devices (e.g., recipient devices).

10040] Recipient component 128 may include functionality that enables the user device to receive and process encrypted medi a items. Recipient component 1 28 may process an incoming media item by gathering information from the media item, the providing device, the recipient device, or a combination thereof. The information may be sent to the media server so that the media server can determine w hether the user device is authorized to play the media item. In one example, the receiving user device may send the wrapped encryption key to the media server in pi ay abi lity request 152 and the media server may unwrap the encryption key and send it back to the user device in payability response 1 54. The user device may then use the unwrapped encryption key to decrypt the media item .

10041 ] In general, functions described in one implementation as being performed by the content sharing platform can also be performed on the client devices 1 20 A through 120Z in other implementations, if appropriate. In addition, the functionality attributed to a particular component can be performed by different or multiple components operating together. The content sharing platform and media serv er 1 10 can also be accessed as a service provided to other systems or devices through appropriate application programming interfaces, and thus is not limited to use in websites.

100421 In implementations of the disclosure, a "user" may be represented as a single individual . However, other implementations of the di sclosure encompass a "user" being an entity controlled by a set of users and/or an automated source. For example, a set of individual users federated as a community in a social network may be considered a "user." In another example, an automated consumer may be an automated ingestion pipeline, such as a topic channel, of the content sharing platform.

10043] Although implementations of the di sclosure are di scussed in terms of a media server and a content sharing platform, implementations may also be generally applied to any type of social network providing digital content and connections between users. 10044] In situations in which the systems discussed here collect personal information about users, or may make use of personal information, the users may be provided with an opportunity to control whether the content sharing platform collects user information (e.g., information about a user' s social network, social actions or activities, profession, a user ^' s preferences, or a user's current location), or to control whether and/or how to receive content from the content server that may be more relevant to the user. In addition, certain data may be treated in one or more ways before it is stored or used, so that personally identifiable information is removed. For example, a user' s identity may be treated so that no personally identifiable information can be determined for the user, or a user's geographic location may be generalized where location information is obtained (such as to a city, ZIP code, or state level ), so that a particular location of a user cannot be determined. Thus, the user may have control over how information is collected about the user and used by the content sharing platform.

10045] FIG. 2 is a block diagram il lustrating an example user device 200. User dev ice 200 may be the same or similar to user devices 120A-Z. In the example shown in Fig. 2, user device 200 includes sharing interface component 1 24, provider component 126, recipient component 128, and data store 122.

10046] Sharing interface component 1 24 may provide a user interface that enables a user of user device 200 to view and select available user devices and media items for sharing.

Sharing interface component 124 may include a device selection module 210, a media item availability module 2 12, and an initiation module 2 14.

[0047] Device sel ection module 2 1 0 may search for and display one or more user devices that are av ai lable for sharing. Device selection module 210 may identify the user dev ices by sending out a broadcast message and waiting for a response. The broadcast message may identify informati on about user device 200 such as identification information (e.g. , dev ice identifier, user identifier), dev ice resources (e.g., processing power, storage capacity, battery power), media item presentation capabilities (e.g. , ability to play a particular media item format), other information or a combination thereof. User dev ice 200 may then receiv e a response from one or more other dev ices. The responses may include information about the other user dev ices such as media cache information (e.g., av ailable media items ),

identification information (e.g., dev ice identi ier, user identifier), dev ice resources (e.g., battery power, network connections, processing power, storage capacity), other information or a combination thereof In one example, the request and/or response may include anonymized data instead of identificati on information. Device selection module 210 may display the user devices that responded in a graphical interface, which may be capable of receiving user input to select one or more of the user devices. An example graphical user interface will be discussed in more detail in regards to Fig. 8.

[0048] Media item availability module 212 may determine which media items are available for sharing. In some examples, all media items that are in the media cache of a sharing user device may be available for sharing. In other examples, a user device may identify a subset of the media items in the media cache to share. The subset may include no media items, some media items, all media items, or other variation. The subset may be determined by the user device in view of user input, device resources, media server input, or a combination thereof. In one example, the user may identify one or more particular media items in the media cache to be made available for sharing. In another example, the user device may analyze device resources (e.g., battery power, network bandwidth) and determine which if any media items should be shared. In yet another example, the media server may provide input that identifies one or more media items to share. This may be in attempt to di stribute the number of user devices that have a particular media item to enhance media item availability and sharing without burdening any particular user device. Media item

availability module 2 12 may display the media items that are available for sharing in a graphical user interface, which may be capable of receiving user input to select one or more of the user devices.

[0049] Initiation module 2 14 may communicate with media item availability module 2 1 2 and device selection module 2 10 to identify a particular user device and/or media item for sharing. The sharing may involve pushing the media item to the user device or pulling the media item from the user device or a combination of both. In one example, user device 200 may receive user input identifying a remote user device and a local media item and the initiation module 2 14 may initiate the pushing of the identified media item to the remote user device. In another example, user device 200 may receive user input identifyi ng a remote user device and a media item available on the remote user device and the initiation module 2 14 may initiated the pulling of the identified media item from the remote user device. In other examples, user device may pull a media item from a first user device and may then push the media item to a second user device.

100501 Sharing interface component 124 may function in multiple modes including a one- on-one mode, a public mode, and a priv ate mode. The one-on-one mode may be similar to the push and pull features discussed above and may involve the user device receiving user input identifying a particular media item and a particular device for sharing. The media item may then be transferred from one device to the other device (i.e., one-to-one).

100511 The public mode may be similar to the one-on-one mode in that user device 200 may receive user input selecting a particular media item, but when the public mode is enabled there may be mul tiple sharing devices and multiple recipient devices. Some or all of the sharing devices may broadcast their available media items. User device 200 may then select one or more of the media items without selecting a specific user device. In this exampl e, the user device that is sharing the selected media item may remain anonymous to user device 200. Conversely, user device 200 may participate as a sharing device and broadcast a set of available media items and anonymously transfer one or more of the media items when requested by another user device.

[0052] The private mode may be similar to the one-on-one mode and the public mode but may include an approval stage. During the approval stage, the user device that is sharing the media item may receive a sharing request for a particular media item and may approve or disapprove the sharing request. In one example, the approval or disapproval may be based on user input, in which case the interaction module may notify the user and the user may provide input that approves or disapproves the sharing.

10053] After sharing interface component 124 has identified a media item and initiated the sharing, it may interact with provider component 126 or recipient component 128. Provider component 126 may be used when user device 200 is sharing a media item to another user devices and recipient component 128 may be used when user device 200 is receiving a shared media item from another user device.

[0054] Provider component 126 may include a key generation module 220, an encryption module 222, and a wrapping module 224. The functions performed by provider component 126 may be performed at any point in the sharing process, such as before, during, or after a media item is received from a media server, selected for sharing, or after the sharing is initiated.

[0055] Key generation module 220 may create one or more encryption keys 240 for a user dev ice. Each encryption key 240 may include a piece of infor ation that determines the functional output of a cryptographic function and may be used to encrypt and decrypt a media item. The key generation module 220 may generate encryption key 240 using a random number generator, a pseudorandom number generator, a key derivation function, other mechanism, or a combination thereof. Key generation module 220 may seed the key generation using information av ailable to the user device such as a dev ice identifier, a time stamp, an IP address, a MAC address, a user identifier, other information, or a combination thereof In an alternative example, encryption key 240 may be generated by the media server or other portion of the content sharing platform and sent to user device 200.

[0056] Encryption module 222 may use the encryption key 240 generated by key generation module 220 to encrypt one or more media items. In one example, each media item on user device 200 may be encrypted using a different encryption key 240. In another example, multiple (e.g., all ) media items on user device 200 may be encrypted using encryption key 240. Encryption module 222 may encrypt the media items using a symmetric key cryptography system that uses a single shared key, such as, Data Encryption Standard ( DES) or Adv anced Encryption Standard (AES). In other embodiments, encryption module 222 may also or alternativ ely encrypt the media items using an asymmetric cryptography or public-key cryptography system that uses multiple keys (e.g., public key and a private key), such as, Ri vest-Shamir- Adleman (RSA).

10057] Wrapping module 224 may wrap encryption key 240 using a media server key 244. Media serv er key 244 may be a public key that is generated by the media serv er or other portion of a content sharing platform and sent to user dev ice 200. Wrapping module 224 may use media server key 244 along with a key encapsulation mechanism to secure the encryption key 240 while it is transferred to and stored on another user device.

10058] In one example, encryption module 222 may use a symmetric key cryptography system to encrypt the media item and the w rapping module 224 may an assymetric cryptography system to wrap the encryption key 240. As discussed abov e, the asymmetric cryptography or public-key cryptography system may be the same or similar to RSA . After wrapping the encryption key, user dev i ce 200 may transfer the encrypted media item I 12 (e g , cipher text) and the wrapped encryption key 240 to another device.

[0059] Recipient component 128 may be used when user dev ice 200 is receiving a media item that is shared by another user dev ice. Recipient component 128 may include a playability module 230, a decryption module 232, and a veri fication module 234.

(0060) Playability module 230 may communicate with the media serv er to determine whether user device 200 is authorized to present the media item. The communication with the media serv er may inv olv e transmitting a playability request and receiv ing a playability response. The playability request may include the wrapped encryption key and information related to the media item, the recipient or sharing dev ice, the recipient or sharing user, other information, or combination thereof. The media serv er may then analyze this information and compare it to information from one or more data stores (e.g., databases) to determine whether user device 200 is authorized to present the media item to the user. The analysi s may involve checking whether the media item is still available for presentation and whether it has any restrictions. For example, the media item may be restricted to mature audiences (e.g., not for children) or it may be restricted to or from certain geographic areas (e.g., certain countries). After determining the playability check has been sati sfied, the media server may unwrap the wrapped encryption key. Unwrapping the encryption key may involve a similar cryptographic system that was used to wrap the encryption key and may utilize the private key associated with the media server key (e.g., public key). The media server may then send the unwrapped encryption key back to user device 200 in the playability response.

10061 ] Decryption module 232 may use the unwrapped encryption key to decrypt the encrypted media item 1 12. Unwrapping the encryption key may involve a similar

cryptographic system that was used to encrypt the media item as discussed above in regards to encryption module 222.

10062] Verification module 234 may determine whether the media item is authentic and whether it includes any unauthorized modifications. Verification module 234 may use a digital signature associated with the media item to verify the media item. The digital signature may be based on the media item (e.g., video and/or audio bytes) and a private signing key of the media serv er and may be computed using any digital signature mechanism. In one example, the digital signature mechanism may be the same or similar to an elliptic curve digital signature algorithm (ECDSA) and may use elliptic curve cryptography or any other form of cryptography to compute the digital signature. The digital signature may be computed by the media server or other portion of the content sharing platform and may be received by user device 200 from the user device that shared the media item (e.g. , with the encrypted media item ) or directly from the media server (e.g., with the playability response). Verification module 234 may analyze the decrypted media item in view of the digital signature to perform the verification. In one example, verification module 234 may compute a hash of the media item (e.g., video and/or audio bytes) and use the hash, the digital signature, and a public verification key of the media server to verify the decrypted media item. The hash may be computed using a cryptographic hash function such as a Secure Hash Algorithm ( SHA) or any other hash function.

100631 FIGS. 3, 4, and 5 depict flow diagrams for illustrative examples of methods 300, 400, and 500 for implementing an access control mechani sm for peer-to-peer media sharing. Method 300 illustrates an example process flow from the perspective of a media server and methods 400 and 500 are example methods for a sharing user device and a recipient user device respectively. Methods 300, 400, and 500 may be performed by processing devices that may comprise hardware (e.g., circuitry, dedicated logic), software (such as is run on a general purpose computer system or a dedicated machine), or a combination of both.

Methods 300, 400 and 500 and each of their individual functions, routines, subroutines, or operations m ay be perform ed by one or more processors of the computer device executing the method. In certain implementations, methods 300, 400, and 500 may each be performed by a single processing thread. Alternatively, methods 300, 400, and 500 may be performed by two or more processing threads, each thread executing one or more individual functions, routines, subroutines, or operations of the method.

10064] For simplicity of explanation, the methods of this disclosure are depicted and described as a series of acts. However, acts in accordance with this di sclosure can occur in various orders and/or concurrently, and with other acts not presented and described herein. Furthermore, not all illustrated acts may be required to implement the methods in accordance with the disclosed subject matter. In addition, those skil led in the art will understand and appreciate that the methods could alternatively be represented as a series of interrelated states via a state diagram or events. Additionally, it should be appreciated that the methods disclosed in this specification are capable of being stored on an article of manufacture to facilitate transporting and transferring such methods to computing devices. The term "article of manufacture, ^" as used herein, is intended to encompass a computer program accessible from any com puter-readabl e device or storage media. In one implementati on, methods 300 may be performed by media server 1 10 and methods 400 and 500 may be performed by user device 120 of FIG. 1 .

10065] Referring to FIG. 3, method 300 may be performed by one or more processing devices of a media server and may begin at block 302. At block 302, the processing device of the media server may transmit a media item to a first user device. The media item may comprise video, audio, images, text, other media or combination thereof. The processing device of the media server may also transmit one or more encryption keys to the first user dev ice. One of the encryption keys may be used by the first user device to wrap a device key (e g , encryption key) generated by the user device. Wrapping (e.g., encapsulating) the device key may be advantageous because it may mask the encryption key as cipher text when it is being transmitted over a peer-to-peer connection and/or stored on an untrusted peer. In another example, the media server may transmit a second encryption key to the first user device. The second encryption key may be generated by the media item and may be used as an alternative to the encryption key generated by the user device for encrypting the media item.

[0066] At block 304, the processing device may receive, from a second user device, a playability request and a wrapped encryption key associated with the media item. The playability request may inquire as to whether the second user device is authorized to play the media item that was shared by the first user device with the second user device via a peer-to- peer connection. In one example, the wrapped encryption key may comprise a symmetric encryption key that is encapsulated using an asymmetric encryption key. The symmetric encryption key may be the encryption key generated by the user device and used to encrypt the media item. The asymmetric encryption key may be a public key that was provided by the media server for wrapping the symmetric encryption key. In one example, the playability request may include the wrapped encryption key and information related to the media item, the recipient or sharing device, recipient or sharing user, other information or combination thereof.

10067] At block 306, the processing device may determine that the second user device is authorized to play the media item. The determination may involve the media item analyzing the information in the playability request and comparing it to information from one or more data stores (e.g., databases). The analysis may involve checking whether the media item is still available for presentation and whether the media has any restrictions on making copies or being viewed. In one example, the processing device of the media server may also verify that the media item does not include an unauthorized modification. The verification may be performed by comparing information (e.g., a hash) associated with the version of the media item on the second user device to information (e.g., digital signature) associated with the version of the media item on the media server.

[0068] At block 308, the processing device may transmit a response indicating that the second user device is authorized to play the media item, the response comprising the encryption key derived from the wrapped encryption key. Deriving the encryption key may involve unwrapping the wrapped encryption key using a private key that corresponds to the public key used to wrap the key. The private key and the public key may be part of a key pair accessible to the media server and the media server may have previously provided the public key to the first user device to wrap the encryption key. The wrapped encryption key may comprise cipher text and unwrapping the encryption key may involve using the private key in combination with an asymmetric cryptographic function (e.g., public-key cryptographic function ) to derive the encryption key from the cipher text. The second user device may use the encryption key to deciypt the media item and once decrypted the media item may be presented to a user of the second user device.

[0069] The processing device of the media server may also provide a supplemental media item to be presented by the second user device before, during, or after the presentation of the media item. The supplemental media item may include any media content and may function as an advertisement. In one example, the supplemental media item may be provided to the first user device along with the playability response. For example, the playability response may include the supplemental media item or the supplemental media item may be included in another response from the media server or other device (e.g., partner, affiliate). In another example, the supplemental media item may be prov ided to the first user device and may be transmitted from the first user device to the second user device before, during or after transmitting the encrypted media item. Responsive to completing the operations described herein above with references to block 308, the method may terminate.

10070] In other examples, method 300 may involve verifying the media item received by the second user dev ice originated from the media server. The verification may occur at any point prior to playing the media item on the second user device and may be performed by the media serv er, the first user device, the second user dev ice, other dev ice or combination thereof. For example, it may occur prior to the second user device receiving the encrypted media item from the first user dev ice, prior to decrypti ng the media item on the second user device, prior to playing media item, or any other time. In one example, the verification may be performed by the second device (e.g., recipient dev ice) and may involve analyzing a hash. The hash may be based on the decrypted version of the media item and may be computed by the second device. The second dev ice may also analyze a digital signature that was created by the media serv er and received directly from the media serv er or received from the user device that shared the encrypted media item and wrapped encryption key. The second user device may then analyze the hash and the digital signature to determine that the decrypted media item is authentic.

10071 ] Referring to FIG. 4, method 400 may be performed by processing devices of a user device that is sharing a media item with another user device. The sharing may be initiated by the sharing device or the recipient dev ice. Sharing that is initiated by the sharing device may be considered a push-based sharing because the media item may be pushed from the sharing device to the recipient dev ice. Sharing that is initiated by the recipient dev ice may be considered a pull -based sharing because the media item is pulled from the sharing device to the recipient device. 10072] Method 400 may begin at block 402, wherein the processing device of a first user device may receive a media item from a media server via a network. The media item may be streamed or downloaded from the media server to the first user dev ice using any streaming or file transfer technology. The streaming technology may separate the media item into an audio stream and a video stream. The audio stream may be compressed using an audio codec such as MP 3, advanced audio coding ( A AC), Opus, other encoding mechanism, or combination thereof The video stream may be compressed using a video codec such as H.264, VPS, other encoding mechanism, or combination thereof. The streaming technology may al o or alternativ ely assemble the audio stream and video stream into a container stream ( e.g., bitstream ) such as MP4, Flash Video ( FLV), advanced systems format (ASF), internet streaming media alliance ( ISM A), other encoding mechanism, or combination thereof. File transfer technology may be based on any file transfer protocol such as hypertext transfer protocol (HTTP), file transfer protocol (FTP), trivial file transfer protocol (TFTP),

BitT ^' orrent, other protocol, or a combination thereof.

10073] At block 404, the processing device may store the media item locally at the first user device. When uti lizing streaming media, the storing may inv olv e off-lining the streamed media item to persistent storage. A user device may off-line a streamed media item by copying one or more streams of the media item (e.g. , video stream, audio stream ) from memory to the persistent data storage. In one example, the first user device may request permission from the media server in order to off-li ne a media item and the media serv er may respond with an encryption key (e.g., caching token) to encrypt the off-lined media item. In another example, the first user dev ice may generate an encryption key itself as opposed to receiv ing it from the media server.

10074] At block 406, the processing device may encrypt the media item using an encryption key to generate an encrypted media item. The encryption key for encrypting the media item may be generated by the processing device or by the media server. In one example, encrypting the media item may involve using a symmetric key cryptography system that uses a single shared key, such as. Data Encryption Standard (DES) or Advanced

Encryption Standard (AES). In other example, encrypting the media item may involve using an asymmetric cryptography or public-key cryptography system that uses multiple keys (e.g., public key and a private key), such as, the Riv est-Shamir-Adleman cryptographic system (RSA).

10075] At block 408, the processing device may, in response to receiv ing a request to share the stored media item with a second user device, wrap the encryption key to generate a wrapped encryption key. As discussed above, the sharing of the media item may be requested by the sharing device (e.g., first user device) in which case the media item is pushed to the recipient device (e.g., second user device) or the sharing may be requested by the recipient device in which case the media item is pulled from by the recipient device from the sharing device. When pushing the media item, the request may be based on user input received from a user, which may select the media item, the destination device, or a combinati on of both. When pulling the media item, the request may be based on a message received by the recipient device that indicates the recipient device is requesting the media item to be shared. After receiving the request, the processing device may wrap the encryption key by encrypting the encryption key using a public key of the media serv er.

[0076] At block 410, the processing device may transmit, via a peer-to-peer connection, the enciypted media item and the wrapped encryption key to the recipient device. In one example, the sharing device may also transmit a supplemental media item or a link to the supplemental media item to the recipient device. The supplemental media item or link to the supplemental media item may have originated from the media server and may be transferred with the media item . In another example, the sharing dev ice may also transmit metadata of the media item to the recipient device and the metadata may be transferred while

unencrypted. Responsive to completing the operations described herein above with references to block 4 10, the method may terminate.

[0077] Referring to FIG. 5, method 500 may be performed by processing devices of a recipient user dev ice that i s receiving a media item from a sharing dev ice. Method 500 may begin at block 502, when a processing dev ice of the recipient user dev ice may receive an encrypted media item and a wrapped encryption key from a sharing user device over a peer- to-peer connection. In one example, the peer-to-peer connection may be a direct connection between the two dev ices using wireless technology, wired technology, or removable media. In another example, the peer-to-peer connection may be a peer-to-peer wireless network connection. In one example, the processing dev ice may receive the encrypted media item after transmitting a request for the media item to the sharing user device.

[0078] At block 504, the processing device may transmit the wrapped encryption key and a request to a media serv er to determine whether the recipient user device is authorized to play the encrypted media item . The request to determine whether the recipient user dev i e is authorized to play the encrypted media item may i nclude an identifier of the media item. In one example, the recipient user device may tether with the sharing user device and may transmit the request and the wrapped key to the media server using a network connection of the sharing user device.

[0079] At block 506, the processing device may receive a response from the media server indicating the recipient user device is authorized to play the encrypted media item. The response may include an encryption key derived from the wrapped encryption key. In some examples, the response from the media server may include a supplemental media item or a link to a supplement media item that may be presented before, during, or after playing the media item. In other examples, the supplemental media item may be received from the sharing user device when receiving the encrypted media item.

10080] At block 508, the processing device may decrypt the encrypted media item using the encryption key. The encryption key may be the same key that was used by the sharing user device to encrypt the media item . After decrypting the media item, the processi ng device may indicate via a graphical interface of the recipient user device that the media item is ready to be played. The graphical interface i s di scussed in more detail in regards to Fig. 14. After decrypting the media item, the recipient user device may add the media item to a media cache and make it avai lable to share with other devices. Sharing with the media item with another device (e.g., third device) is discussed in more detail below in regards to Figs. 6A-9.

Responsiv e to completing the operations described herein above with references to block 508, the method may terminate.

100811 FIGS. 6 A- 14 il lustrate example graphical interfaces for a peer-to-peer sharing mobi le application that includes an access control mechani sm . Figs. 6 A and 6B represent graphical interfaces that enable a user to view information pertaining to multiple media items and detect the availability of each of the multiple media items. Figs. 7-9 represent graphical interfaces for selecting a media item and transmitting the media item to another device. Figs. 10- 14 represent example graphical interfaces for receiving a shared media item and processing the media item to make it available to be presented.

10082] Referring to Fig. 6 A, user interface 600 may enabl e a user to view one or more media items and initiate the sharing of one or more of the media items. The one or more media items may be a subset (e.g., some or all ) of the media items that are av ailable in the media cache of the local user device (e.g., set of saved media items). The user device may provide user interface 600 to a user in response to receiving user input launching a software component (e.g. , mobile application ) or may automatically initiate user interface 600 in response to receiving a request to share (transmit or receiv e) a media item from one or more other user devi ces. User interface 600 may include one or more graphical elements that provide (e.g., present, display, indicate, reflect) graphical information to a user of a user device. The graphical elements may represent information of an underlying data structure (e.g., media item) and may be updated (e.g., refreshed) when the underlying data structure is modified. In one example, a graphical element may be configured to provide information to a user but may not be configured to receive information from a user (e.g., user input). In another example, a graphical element may be a graphical control element that provides information to a user and may also be configured to receive information from a user, such as receiving user input. The user input may be received by the user device via a touch screen (e.g., taps, swipes, or other touch gestures), a mouse/keyboard (e.g., clicks, scrolls, typing), a camera (e.g., gestures), an accelerometer (e.g., shakes), other sensory device, or a

combination thereof. In the example shown in Fig. 6A, user interface 600 may include a media entry region 610, one or more media entries 620, one or more media availability indicators 626 and 626B, and a sharing control element 630.

10083] Media entry region 610 may be any portion of user interface 600 that di splays information corresponding to one or more media items. Media entry region 610 may include multiple media items organized into a media item arrangement. In one example, the media item arrangement may be a sequence of media items or a list of media items. Media entry region 610 may be configured to receive user input to adjust (e.g., scrol l, pan, zoom, move, reposition) the media item arrangement in one or more directions (e.g., horizontal, vertical, or other direction). As the media item arrangement i s adjusted, the location of a particular media item may change and a new media item may be di splayed and an existing media item may be hidden. Each media item in the media entry region 610 may be represented by a media entry 620.

10084] Each media entry 620 may be a graphical data structure that provides information corresponding to a particular media item. As shown in Fig. 6 A, media entry 620 may include an image 622, metadata 624, and a media availability indicator 626 A. Image 622 may be an image representing the media item (e.g., cover image) or a portion of the media item such as an video frame of the media item (e.g., thumbnail image). Metadata 624 may include any information about the media item such as the title, creator, uploader, duration, creation date/time, upload date/time, number of viewers, number of sharers, other information, or a combination thereof.

10085] Media availability indicators 626A and 626B may be graphical elements that represent whether a corresponding media item is available on a particular user device. Media availability indicators 626 A and 626B may be any graphical elements or graphical control element and may include shapes (e.g., circles, squares, octagons), symbols (e.g., locks, check marks, arrows), colors (e.g., blue, green, red, yellow), text (e.g., different fonts, sizes), images, other graphics, or a combination thereof.

[0086] The graphical elements may be positioned at any location within media entry region 610 or within a corresponding media entry 620. Media availability indicators 626 A, 626B may be superimposed on image 622 of a respective media entry 620 or may be positioned at an adjacent position (e.g., above, below, to the side) of the image or media entry 620. In the example shown in Fig. 6 A, media availability indicator 626A may be an overlay graphical element that has a blue circular shape and an embedded lock symbol and media availability indicator 626B may be an overlay graphical element that has a blue circular shape and an embedded underlined checkmark symbol . In one example, some or all of the media availability indicators may be graphical control elements that receive user input and perform an action in response. For e ample, media availability indicator 626A may indicate a media item i s in a locked or encrypted state. When media av ailability indicator 626 A receiv es user input (e.g., tap, click, hov er, hold), it may initiate a state transition (e.g., manually initiated decryption ) or present information about how to transition the corresponding media item (see Fig. 12). Variations of a media availability indicator may be used to indicate a plurality of different media item states, which are di scussed in more detail in regards to Fig. 6B.

10087] Sharing control element 630 may be included within user interface 600 and may enable a user to share one or more media items. Sharing control element 630 may receiv e user input (e.g., tap, swipe, click, keystroke) and may initiate one or more user interfaces to share media items. Sharing media items may inv olv e transmitting one or more media items to another user dev ice and/or receiving one or more media items from another user dev ice. Sharing control element 630 may include one or more graphical elements and may include shapes (e.g., circles, squares, octagons), symbols (e.g., arrows, locks, check marks,), text, images, other graphics, or a combination thereof. Sharing control element 630 may be positioned at any location within user interface 600, which may or may not include media entry region 610. In the example shown in Fig. 6 A, sharing control element 630 may be a graphical control element that has a blue circular shape with embedded parallel horizontal arrows pointing in opposing directions and once selected may cause the user interface to proceed to user interface 700 of Fig. 7.

10088 ] Referring to Fig. 6B, user interface 650 may be similar to user interface 600 and may display media items that are in different states and one or more of the media items may be transitioning between states. In one example, user interface 650 may include multiple media item states 628A-B, a media entry 625, and a peer-to-peer connection region 660.

[0089] Media item states 628A-C may illustrate some of the states a media item may be in or transitioning to or from during use of the user device. Media item state 628 A may il lustrate an example first state of a media item, wherein the media item has not been saved on a user device but is in the progress of being received (e.g., downloaded) from another device. The other device may be one or more peer user devices, serv er devices, other devices, or a combination thereof. As discussed above, the version of the media item being received may be an encrypted version and may be accompanied with a wrapped encryption key. The user device may receive the wrapped encryption key before, duri ng, or after receiving the encrypted media item and may be received from the same device that transmitted the encrypted media item or from a different device.

1009 1 Media item state 628 B illustrates a second state of a media item, wherein the media item may be saved on a user device in an encrypted form . The media item may be saved along with a wrapped version of the encryption key. When a media item is in the second state, the user device is unable to interpret or present the media item but may be able to share the encrypted version of the media item with one or more other user devices.

[0091] Media item state 628C illustrates a third state of a media item, wherein the media item may be saved on the user device and available to be experienced by a user. A media item may transition from the second state to the third state when the user device decrypts the encrypted version of the media item . As di scussed above, the user device may decrypt the media item by sending the wrapped encryption key to a remote device (e.g., content sharing platform ), which perform s a playability check and unwraps the wrapped encryption key. The unwrapped version of the encryption key may then be sent to the user device and the user device may use it to decrypt the media item, which may enable the media item to transition to media item sate 628C.

[0092] Each of the media item states 628 A-C may be represented by a respective media availability indicator 626A and 626B or a lack of media availability indicator. For example, media item state 628A may be represented by a lack of a media availability indicator (e.g., hidden media availability indicator), whereas media item states 628B and 628C may be represented by media availability indicators 626A and 626B respectivel . A particular media item may transition between one or more of the states during operation of the peer-to-peer sharing technology. For example, a media item may begin in media item state 628 A when the encrypted version of the media item and the wrapped encrypti on key are being downloaded over a peer-to-peer connection from another user device. Once the download completes, the media item may transition to media item state 628B and the user interface 650 may be updated to transition media indicator from media indicator 626 A to media indicator 626B.

[0093] The media item states 628A-C may also be represented by one or more other graphical features. The other graphical features may include modifying the media entry or a portion of the medi a entry to adjust the transparency (e.g., greyed out), font (e.g., bol d, italicized, highlighted), size (e.g., enlarge, shrink), the arrangement (e.g., indent or protrude a particular media entry). In the example shown in Fig. 6B, media item state 628 A may be represented by example media entry 625, which may include a progress indicator 627 and a graphical control element 629. The existence of progress indicator 627, graphical control element 629, a hidden media availability indicator, other feature, or combination of features may indicate the media entry corresponds to media item state 628 A.

10094] Progress indicator 627 may be a graphical element that provides a graphical representation of the progression of receiving the media item and/or the wrapped encryption key. Progress indicator 627 may take on any shape such as a bar (e.g., progress bar), circle (e.g., spinning wheel, throbber), other shape, or a combination thereof. The graphical element may be accompanied by a textual representation of the progress in a percent format. The progress indicator may be located at any location on interface 650. In one example, progress indicator 627 may be di splayed adj acent (e.g., to the side, above, below) the media image and/or metadata. In another example, progress indicator 627 may be di splayed over the media image and/or meta data in a semi-transparent or opaque manner as shown in Fig. 6B.

[0095] Graphical control element 629 may enable a user to cancel the transmission of the media item . Cancelling the transmi ssion of the media item may transition the media item from state 628 A to another state (e.g., a fourth state) that represents a canceled or failed attempt at downloading the media item (fourth state not shown). Graphical control element 629 may be a button, widget, other element, or a combination thereof.

[0096] Connection region 660 may be any portion of user interface 650 that di splays information pertaining to one or more connections for transmitting or receiving the media item, encryption key (wrapped or unwrapped), other information, or a combination thereof. The connection may be a peer-to-peer connection, an internet connection, other connection, or a combination thereof In one example, a connection (e.g., peer-to-peer connection) may be displayed while the encrypted v ersion of the media item and the wrapped encryption key are being received by or transmit from the user device. In another example, the connection (e.g., internet connection) may be displayed while the wrapped or unwrapped encryption key is being receiv ed by or transmitted from the user dev ice.

[0097] Peer-to-peer connection indicator 662 may be displayed within connection region 660 and may be an example of one type of connection. Peer-to-peer connection indicator 662 may include one or more dev ice symbol s 664 A and 664B, dev ice information 666 A and 666B, and a connection symbol 668. The one or more device symbols 664 A and 664B may graphically represent the dev ice and may hav e different symbols for different types or classes of dev ices, such as phones, tablets, laptops, desktops, servers, or other dev ices. Dev ice information 666 A and 666 B may include identification information for a dev ice such as a dev ice identifier (e.g., dev ice name, user name, IP address) and a relativ e identifier, which may indicate whether the device identi ier corresponds to a local dev ice (e.g., "My Device ^" ) or a remote dev ice (e.g., "Other Dev ice, ^" "Transmitting Device, ^" ' Receiving Device ^" ). In one example, connection symbol 668 may indicate the underlying technology used for the connection such as a wifi, bluetooth, cellular (e.g., 3G, 4G), other technology, or a combination thereof.

[00981 Referring to Fig. 7, user interface 700 may display information for the selected media item and an interface for sharing the selected media item. User interface 700 may include a display region 7 10 and a sharing region 720. Display region 710 may include an embedded media player for presenting (e g., playing) the media item. Sharing region 720 may include one or more options for sharing the media item . A first option 722 may enable the media item to be shared with nearby user dev ices. A second option 724 may enable the media item to be shared with users that are accessible ov er the internet. When user input indicates a selection of first option 722, user interface 700 may proceed to user interface 800.

[0099] Referring to Fig. 8, user interface 800 may enable a user to select one or more user dev ices that are intended to be the recipient of the shared media item. In one example, the user dev ices displayed may be user dev ices that are in the geographi c area (e.g., within 30ft) of the user dev ice. User interface 800 may include a recipient selection region 8 10 that displays the sharing dev ice 8 12 and one or more recipient devi es 8 14 A and 814B. The locations of recipient dev ices 8 14 A and 814B relativ e to sharing dev ice 8 12 may correspond to the actual physical distance between the corresponding user devices. In response to user input indicating a selection of recipient device 814B, user interface 800 may proceed to user interface 900. 1001001 Referring to Fig. 9, user i nterface 900 may provide information about the sharing of a media item before, during, and after the transfer of the media item. User interface 900 may include a sharing indicator region 910 and a peer-to-peer connection indicator region 930. Sharing indicator region 910 may include a media entry 920, which may be the same or simil ar to media entry 620 of Fig. 6 A . Peer-to-peer connection indicator region 930 may display the local user device and the selected recipient device.

[00101] Figs 10-14 may include examples of user interfaces that are presented when receiving a shared media item, as opposed to sending the shared media item. Referring to Fig. 10, user interface 1000 may provide information about a media item before, during, and after receiving the media item. User interface 1000 may be similar to user interface 600 and 900 but may be presented by the receiving device as opposed to the sending device. User interface 1000 may include a media list 1010 and a peer-to-peer connection indicator region 1030. The media list 1010 may include one or more media entries 1020 that are the same or similar to media entries 620 of Fig. 6 A. Peer-to-peer connection indicator region 1030 may display the local user device and the selected sending device, as opposed to the recipient device shown in Fig. 9.

[001021 Referring to Fig. 1 I , user interface 1 100 may provide information about the media items that are in the media cache of the local user device (e.g., saved media items). User interface 1 100 may be the same or similar to user interface 600 and may include one or more media entries I 120. Each media entry 1 120 may include a media availability indicator 1 122 A or 1 1 22 B. Media availabi lity indicator I 1 22 A may indicate the media item is stored in the media cache (e.g., off-lined) but is not available to be played. This may be because the media item may be encrypted. Media avai lability indicator I 122B may indicate the media item is available to be played or shared with another user device.

[00103| Referring to Fig. 12, user interface 1200 may provide information about verifying and decrypting a received media item. User interface 1200 may include an informational overlay 1 240 that provides information about decrypting and verifying the media item . It may indicate to the user that a payability check is available to ensure the video is available and a verification check can be performed to ensure that the media item originated from the media server and is free of unauthorized modifications (e.g., security threats).

[ 001041 Referring to Fig. 13, user interface 1300 may prov ide information process steps related to the playabi lity check and the verification check . User interface 1300 may include a status region 1350 that prov ides information about the status of the decrypting and verification processes. In one example, it may display whether the each of the one or more process has completed.

[00105] Referring to Fig. 14, user interface 1400 may include a notification region 1460 that provides a notification that includes a graphical, textual, audio, tactile, or other component.

[00106] FIG. 15 depicts a flow diagram of an illustrative example of method 1500 for providing a user interface for a peer-to-peer media sharing application. Method 1500 may be similar to methods 300, 400, and 500 discussed above and may focus on providing a graphical interface on a user device that enables a user to visualize one or more features or steps of methods 300, 400, and 500. Method 1500 may be performed by one or more processing devices of the user device and may begin at block 1502.

[00107] At block 1502, the processing device of the user device may provide for di splay a user interface compri sing a plurality of media items and a plurality of media availability indicators. The user interface may be the same or similar to user interface 600 of Fig. 6 A and may include media av ailability indicators 626A and 626B. The processing dev i ce may prov ide the user interface in response to receiv ing user input launching a software component (e.g., mobi le application ) or may be initiated automatically in response to receiving a request to share (transmit or receiv e) a media item. In one example, each of the plurality of the media items may be di splayed along with a media availability indicator. In another example, some of the media items may be displayed with media av ailability indicator and other media items may be displayed with a hidden media indicator or without a media indicator. In the latter example, the hidden media indicator may indicate that the corresponding media item (e.g., an encrypted version of the media item ) is in the process of being received and the media item is not yet saved on the user dev ice or available to be experienced. When the user dev ice is receiving the media item there may be a portion of the user interface that represents that the encrypted version of the media item and a corresponding wrapped version of an encryption key are being receiv ed from another dev ice.

1001081 In one example, the user interface may include a graphical control element (e.g., sharing control element 630. in FIG. 6A) to initiate the receiv ing of the wrapped version of the encryption key for the media item over a peer-to-peer connection. In another example, the user interface may indicate a peer-to-peer connection (e.g., peer-to-peer connection 130 of Fig. 1) used to receiv e the encrypted version of the media item and indicate that an internet connection is used to decrypt the media item (e.g., status region 1350 in Fig. 13). The peer- to-peer connection may be displayed as a peer-to-peer connection indicator (e.g., peer-to-peer connection indicator 662 in Fig. 6B) that identifies a user dev i ce that i s prov iding the encrypted version of the media item and al so identi ies the user device that is receiving the encrypted version of the media item.

[ 0010 1 At block 1504, the processing device may update a media availabi lity indicator of the media availability indicators to represent that the encrypted v ersion of the media item and the encryption key are saved on the local devi ce. The update may be responsive to receiving a signal indicating that a download of the media item and encryption key has completed. In one example, the media av ailability indicator may be used to distinguish between three different states of a particular media item. A first state may indicate the media item is not sav ed on a user device. A second state may indicate the media item is sav ed locally in an encrypted form. A third state may indicate the media item is saved and av ailable to be experienced (e.g., consumed by a user of the user dev ice). More or less states may exist and may be displayed to a user via the user interface.

1001 101 At block 1506, the processing device may receiv e an indication that the encrypted v ersion of the media item is decrypted. The indication may be receiv ed from a module of the user device (e.g., decryption module 232 in Fig. 2). The decryption may be in view of an encryption key that may be used for encrypting and decrypting the media item. The encryption key may be received b a peer device or other remote device (e.g., content sharing platform ). In one example, a user dev ice may include a wrapped encryption key and may transfer the wrapped encryption key to a server and in response may receive an unwrapped encryption key. The user device may then use the unwrapped encryption key along with one or more cryptographic functions to decrypt the media item .

[00111] At block 1 508, the processing device may update the media availability indicator to represent the media item is available to be experienced. The update may be responsive to receiving the indication that the encrypted version of the media item is decrypted. Updating the media availability indicator may inv olv e replacing a first media availability indicator with a second media availability indicator. Updating the media av ailability indicator may also or alternatively involve modifying the exi sting media availability indicator to adjust the embedded symbol, color, shape, format, other graphical attribute, or a combination thereof. 1001 12| In one example, each of the plurality of media items may be represented within the user interface by a media entry. The media entry may include multiple graphical portions with different forms of data (e.g., images, text). A first graphical portion may include an image of the media item (e.g., image 622 of Fig. 6 A) and the second graphical portion may include textual information of the media item (e g , metadata 624 of Fig. 6A). One or more portions of the media entry or user interface may be configured to receive user input corresponding to a particular media item and initiating a presentation of the particular media item. The user input may be received by the user device via a touch screen (e.g., taps, swipes, or other touch gestures), a mouse/keyboard (e.g., clicks, scrolls, typing), a camera (e.g., gestures), an accelerometer (e.g., shakes), other sensory device, or a combination thereof. The presentation of the particular media item may occur by a media player that is embedded within a portion of the user interface or may occur within a different user interface. Responsive to completing the operations described herein above with references to block 1508, the method may terminate.

1001 131 FIG. 16 depicts a block diagram of a computer system operating in accordance with one or more aspects of the present disclosure. In certain implementations, computer system 1600 may be connected (e.g., via a network, such as a Local Area Network (LAN), an intranet, an extranet, or the Internet) to other computer systems. Computer system 1600 may operate in the capacity of a server or a client computer in a client-serv er environment, or as a peer computer in a peer-to-peer or distributed network environment. Computer system 1600 may be provided by a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assi stant (PDA ), a cellular tel ephone, a web appliance, a serv er, a network router, switch or bridge, or any device capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that device. Further, the tenn "computer" shall include any collection of computers that individually or jointly execute a set (or multiple sets) of instructions to perform any one or more of the methods described herei n .

1001 14| In a further aspect, the computer system 1600 may include a processing device 1602, a volatile memory 1604 (e.g., random access memory (RAM )), a non-volatile memory 1606 (e.g., read-only memory ( ROM ) or el ectri cal 1 y-erasab 1 e programmable ROM

(EEPROM)), and a data storage device 16 16, which may communicate with each other via a bus 1608.

1001 15| Processing device 1602 may be provided by one or more processors such as a general purpose processor (such as, for example, a complex instruction set computing (CISC ) microprocessor, a reduced instruction set computing (RISC ) microprocessor, a very long instruction word (VLIW ) microprocessor, a microprocessor implementing other types of instruction sets, or a microprocessor implementing a combination of types of instruction sets) or a specialized processor (such as, for example, an application specific integrated circuit (ASIC ), a field programmable gate array (FPGA), a digital signal processor (DSP), or a network processor). [00116] Computer system 1600 may further include a network interface device 1622.

Computer system 1600 also may include a video display unit 1610 (e.g., an LCD), an alphanumeric input device 1612 (e.g., a keyboard), a cursor control device 1614 (e.g., a mouse), and a si gnal generation device 1620.

[00117] Data storage device 1616 may include a non-transitory computer-readable storage medium 1624 on which may store instructions 1626 encoding any one or more of the methods or functions described herein, including instructions encoding sharing interface component 124 of FIG. 2 and for implementing method 500.

[00118] Instructions 1626 may also reside, completely or partially, within volatile memorv 1604 and/or within processing device 1602 during execution thereof by computer system 1600, hence, volatile memory 1604 and processing device 1602 may also constitute machine- readable storage media.

[00119] While computer-readable storage medium 1624 is shown in the illustrative examples as a single medium, the term "computer-readable storage medium" shall include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of executable instructions. The term "computer-readable storage medium" shall also include any tangible medium that is capable of storing or encoding a set of instructions for execution by a computer that cause the computer to perform any one or more of the methods described herein. The term "computer- readable storage medium" shall include, but not be limited to, solid-state memories, optical media, and magnetic media.

[00120] The methods, components, and features described herein may be implemented by discrete hardware components or may be integrated in the functionality of other hardware components such as ASICS, FPGAs, DSPs or similar devices. In addition, the methods, components, and features may be implemented by firmware modules or functional circuitry within hardware devices. Further, the methods, components, and features may be

impl emented in any combination of hardware devices and computer program components, or in computer programs.

[00121] Unless specifically stated otherwise, terms such as "detecting," "determining," "releasing," "destroying," "initiating," "creating," "abandoning," or the like, refer to actions and processes performed or implemented by computer systems that manipulates and transforms data represented as physical (electronic ) quantities within the computer system registers and memories into other data similarly represented as physical quantities within the computer system memories or registers or other such information storage, transmission or display devices. Also, the terras "first," "second," "third," "fourth," etc. as used herein are meant as labels to distinguish among different elements and may not have an ordinal meaning according to their numerical designation.

[00122] Examples described herein also relate to an apparatus for performing the methods described herein. This apparatus may be specially constructed for performing the methods described herein, or it may comprise a general purpose computer system selectively programmed by a computer program stored in the computer system. Such a computer program may be stored in a computer-readable tangible storage medium.

[00123] The methods and illustrative examples described herein are not inherently related to any particular computer or other apparatus. Various general purpose systems may be used in accordance with the teachings described herein, or it may prove convenient to construct more specialized apparatus to perform method 300, 400, 500 and/or each of its individual functions, routines, subroutines, or operations. Examples of the structure for a variety of these systems are set forth in the description above.

[00124] The above description is intended to be illustrative, and not restrictive. Although the present disclosure has been described with references to specific illustrative examples and implementations, it will be recognized that the present disclosure is not limited to the examples and implementations described. The scope of the di sclosure should be determined with reference to the following claims, along with the full scope of equivalents to which the claims are entitled.