Method, computing system and non-transitory computer-readable storage medium for authorizing usage of media content of a content owner by other content creators

Abstract

This invention discloses a method comprising generating a first media item identifier for a first media item owned by a first media item owner, the first media item being associated with one or more media usage options. The method further comprises generating a media usage option identifier for each of the one or more media usage options. The method further comprises receiving a media usage request from a second media item owner. The method further comprises generating a media usage token when determining that the media usage request satisfies one or more criteria regarding selected media usage options. The method further comprises transmitting the media usage token to a user device of the second media item owner to authorize the second media item owner to include at least a portion of the first media item in a second media item of the second media item owner.

Description

Authorize other content creators to use the content owner's media content Aspects and implementations of the present invention relate to methods and systems for authorizing the use of a content owner's media content by other content creators. A first content creator wants to include one or more media items produced by a second content creator in a media project they create. The first content creator needs to obtain permission from the second content creator to incorporate the second content creator's media item(s) into the created media project. Negotiating a media usage agreement with the second content creator can be expensive and cumbersome. The following summary is a simplified overview designed to provide a basic understanding of some aspects of the present invention. This summary is not an extensive overview of the present invention. It is not intended to identify key or critical elements of the present invention, nor is it intended to delineate any scope of the specific embodiments of the present invention or any scope of the claims. Its sole purpose is to present some concepts of the present invention in a simplified form as a prelude to the more detailed description that follows. Systems and methods for authorizing media usage agreements between content creators are disclosed. In some embodiments, a method includes generating a first media item identifier for a first media item of a first media item owner. The first media item is associated with one or more media usage options provided by the first media item owner. The method further includes generating a media usage option identifier for each of the one or more media usage options. The method further includes storing the first media item identifier and the one or more media usage option identifiers. The method further includes receiving a media usage request from a second media item owner. The media usage request identifies the first media item and a selected media usage option of the one or more media usage options. The method further includes generating a media usage token upon determining that the media usage request satisfies one or more criteria regarding the selected media usage option. The media usage token is based on the media usage request and the selected media usage option. The method further includes transmitting the media usage token to a user device of the second media item owner to authorize the second media item owner to include at least a portion of the first media item in a second media item of the second media item owner. In some embodiments, the method further includes tracking usage of the first media item associated with the media usage token of the second media item owner and the second media item. The method may further include receiving payment from the second media item owner based on the tracked usage according to the selected media usage option. In some embodiments, the one or more criteria associated with the selected media usage option include at least one of payment of a fee or approval of the media usage request by the first media item owner. In some embodiments, the selected media usage option has an associated payment scheme that includes at least one of a one-time payment amount, an amount per interaction with the second media item, an amount per interaction with the first media item within the second media item, or a percentage of total revenue earned by the second media item owner associated with the second media item. In some embodiments, the method further includes receiving a public uniform resource locator (URL) associated with the second media item. The method may further include accessing the public URL associated with the second media item after expiration of the media usage token. The method may further include automatically renewing the media usage request in response to public access to the second media item after expiration of the media usage token. In some embodiments, the media usage token is based on a smart contract using a distributed ledger technology. In some embodiments, the method further includes locating a third media item that is a third media item owner of the first media item. The method may further include transmitting a media usage proposal to the third media item owner. In another aspect, a computing system includes: a memory; and one or more processors coupled to the memory to generate a first media item identifier for a first media item of a first media item owner. The first media item is associated with one or more media usage options provided by the first media item owner. The one or more processors are further configured to generate a media usage option identifier for each of the one or more media usage options. The one or more processors are further configured to store the first media item identifier and the one or more media usage option identifiers. The one or more processors are further configured to receive a media usage request from a second media item owner. The media usage request identifies the first media item and a selected media usage option of the one or more media usage options. The one or more processors are further configured to generate a media usage token based on the media usage request and the selected media usage option when it is determined that the media usage request satisfies one or more criteria regarding the selected media usage option. In some embodiments, the one or more processors are further configured to track usage of the first media item associated with the media usage token of the second media item owner and the second media item. The one or more processors may be further configured to receive payment from the second media item owner based on the tracked usage according to the selected media usage option. In some embodiments, the one or more criteria associated with the selected media usage option include at least one of payment of a fee or approval of the media usage request by the first media item owner. In some embodiments, the selected media usage option has an associated payment scheme comprising at least one of a one-time payment amount, an amount per interaction with the second media item, an amount per interaction with the first media item within the second media item, or a percentage of total revenue earned by the second media item owner associated with the second media item. In some embodiments, the one or more processors are further configured to receive a public uniform resource locator (URL) associated with the second media item. The one or more processors may be further configured to access the public URL associated with the second media item after expiration of the media usage token. The one or more processors may be further configured to automatically update the media usage request in response to public access to the second media item after expiration of the media usage token. In some embodiments, the media usage token is based on a smart contract using a distributed ledger technology. In some embodiments, the one or more processors are further configured to locate a third media item that includes a third media item owner of the first media item. The one or more processors may further transmit a media usage proposal to the third media item owner. In another aspect, a non-transitory machine-readable storage medium stores instructions that, when executed, cause a processing device to perform operations including generating a first media item identifier for a first media item of a first media item owner. The first media item is associated with one or more media usage options provided by the first media item owner. The operations further include generating a media usage option identifier for each of the one or more media usage options. The operations further include storing the first media item identifier and the one or more media usage option identifiers. The operations further include receiving a media usage request from a second media item owner. The media usage request identifies the first media item and a selected media usage option of the one or more media usage options. The operations further include generating a media usage token based on the media usage request and the selected media usage option when it is determined that the media usage request satisfies one or more criteria regarding the selected media usage option. The operations further include transmitting the media usage token to a user device of the second media item owner to authorize the second media item owner to include at least a portion of the first media item in a second media item of the second media item owner. In some embodiments, the operations further include tracking usage of the first media item associated with the media usage token of the second media item owner and the second media item. The operations further include receiving payment from the second media item owner according to the selected media usage option and based on the tracked usage. In some embodiments, the one or more criteria regarding the selected media usage option include at least one of payment of a fee or approval of the media usage request by the first media item owner. In some embodiments, the selected media usage option has an associated payment scheme that includes at least one of a one-time payment amount, an amount per interaction with the second media item, an amount per interaction with the first media item within the second media item, or a percentage of the total revenue earned by the second media item owner associated with the second media item. In some embodiments, the operations further include receiving a public uniform resource locator associated with the second media item. The operations further include accessing the public URL associated with the second media item after expiration of the media usage token. The operations further include automatically renewing the media usage request in response to public access to the second media item after expiration of the media usage token. In some embodiments, the media usage token is based on a smart contract using a distributed ledger technology. Optional features of one aspect may be combined with other aspects as appropriate. Media item owners (e.g., content creators) typically want to include (several) media items (e.g., audio, video, images, or the like) from other media item owners in their own media items. For example, a first media item owner wants to use a song created by another media item owner as background music in a video created by the first media item owner. Including (several) media items from a second media item owner in the first media item owner's new media project infringes on the rights of the second media item owner. Negotiating traditional media usage agreements (e.g., licensing agreements) is expensive and generally not feasible for many media item owners. In addition, content sharing platforms must employ tools specifically designed to identify potential infringements by media item owners and to resolve such infringements. These tools typically use content analysis and other similar technologies that consume a large amount of computing resources of the content sharing platform and cannot always produce accurate results. Aspects of the present invention address these inefficiencies by providing methods and systems for authorizing media usage agreements between media item owners. In some embodiments, a first media item owner (e.g., a licensor) who wishes to grant media usage rights (e.g., a license) to a media item may upload the media item to a media usage rights platform. The first media item owner may specify one or more media usage (e.g., licensing) options for the media item. A media usage option may have an associated payment scheme. For example, in return for including at least a portion of its media item in a media item of a second media item owner (e.g., a licensee), the first media item owner may require the second media item owner to pay a one-time fee, a certain amount for each user interaction (e.g., viewing, listening, streaming, or the like) with the second media item owner's media item, or a certain percentage of the total revenue received by the second media item owner related to the second media item owner's media item. In some embodiments, the first media item owner may only require the second media item owner to pay a certain amount when a user interacts with the first media item owner's media item within the second media item owner's media item. For example, a licensee may request permission to use a licensor's video as part of a new video created by the licensee. If the licensor's video begins 10 minutes into the licensee's video and a user only interacts with (e.g., watches) the first 5 minutes of the licensee's video, the licensee does not need to pay the licensor any money under the terms of the media use agreement. A media usage option may have restrictions or conditions on resale. For example, in some embodiments, a media usage option may not allow a second media item owner to obtain a media usage token and then sell the media usage token to a third media item owner. In some embodiments, a media usage option may allow a second media item owner to sell their media usage token to a third media item owner, provided that the first media item owner receives a portion of the total sales amount (e.g., a predetermined percentage, a specific amount). In some embodiments, a second media item owner can sell a portion of the usage rights of their media usage token, thereby reducing their usage rights while increasing the usage rights of a third media item user. For example, if a second media item owner selects a media usage option that authorizes 10,000 interactions with the second media item owner's media item (which contains at least a portion of the first media item owner's media item), the second media item owner can sell 5,000 interactions with the second media item owner's media item to a third media item owner. The second media item owner will retain authorization from the first media item owner to interact with their media item 5,000 times. A media usage option may include information associated with a financial account of a first media item owner. The payment scheme of the media usage option may require the second media item owner to transfer payment directly to the first media item owner's financial account. The financial account may be a bank account, an escrow account, a cryptocurrency account, or some other financial account capable of receiving payment from a second media item owner. Once the media item and associated media usage options are uploaded to the media usage rights platform, an identifier (e.g., a hash) can be generated for each of the media item and the media usage options. The media item identifier and (several) media usage option identifiers can then be stored in a database (e.g., a relational database, a non-relational database). In some embodiments, the identifiers can be stored in a distributed ledger (e.g., a blockchain). In some embodiments, the distributed ledger can be immutable and / or open to the public. A public distributed ledger can facilitate accounting and can help resolve disputes. In some embodiments, the identifier of the media item is stored in a distributed ledger, while the identifier of the media usage options is stored in a database. In some embodiments, the media item identifier is a unique identifier that identifies the media item. A second media item owner ("licensed person") is able to search for the first media item owner's media items ("first media items") based on the attributes of the first media item. For example, the second media item owner may search for the first media item by name, tag, media item type, or the like. Alternatively, the second media item owner may search for the media items based on the attributes of the media usage options associated with each media item. In some embodiments, the second media item owner may use a combination of media item attributes and media usage options attributes to search for media items. In some embodiments, a second media item owner is able to search for the first media item (e.g., reverse search) by uploading all or part of the first media item to the content licensing platform. The media usage rights platform may provide the second media item owner with a list of results that match the search criteria. The second media item owner may then select a media item and view the associated media usage options. The second media item owner may submit a media usage request by selecting one of a media item and associated media usage options. The media usage request may be stored. Upon determining that the media usage request satisfies one or more criteria for the selected media usage option, a media usage token may be generated based on the media usage request and the selected media usage option. In some embodiments, the selected media usage option may require the second media item owner to pay a fee (a licensing fee) as one of the one or more criteria. In some embodiments, the selected media usage option may require the media usage request to be approved by the first media item owner (e.g., a licensor) as a criterion (e.g., before generating the media usage token). In some embodiments, the media usage token may be a smart contract based on a distributed ledger technology (e.g., Ethereum, Solana, etc.). The smart contract may include an escrow feature that requires funds to be provided by a second media item owner (e.g., a licensee). Such funds may be automatically allocated to the appropriate party (e.g., a media usage rights platform, a licensor, etc.) according to the terms of the selected media usage option. The media usage token may have an associated expiration condition based on the selected media usage option. For example, the media usage token may expire after a user interacts with the licensee's media items a certain number of times, after a user interacts with the licensor's media items within the licensee's media items a certain number of times, or after a predetermined duration. In some embodiments, when a second media item user submits their media item to a content sharing platform, the second media item owner is required to provide a media usage token along with their media item. In some embodiments, the second media item owner may provide a unique identifier for the media usage token rather than the media usage token itself. The media usage rights platform can track the use of the first media item owner's media item in relation to the second media item owner's media usage token and the second media item owner's media item. The media usage rights platform can receive payment from the second media item owner according to the terms of a selected media usage option (e.g., a payment plan). In some embodiments, the media usage rights platform sends a payment request (e.g., an invoice) to the second media item owner. In some embodiments, the media usage request is submitted along with a corresponding account (e.g., an escrow account, a deposit account) from which payment can be received according to the terms of the selected media usage option. After receiving payment from the second media item owner, the media usage rights platform may transfer some or all of the payment received to the first media item owner. In some embodiments, the payment transaction is handled by a payment processor on behalf of the media usage rights platform. In some embodiments, the media usage rights platform may request the second media item owner to provide a public uniform resource locator (URL) at which the second media item owner's media item can be accessed and incorporated into the first media item owner's media item. After the second media item owner's media usage token expires, the media usage rights platform may access the public URL of the second media item owner's media item to determine whether the second media item owner's media item is still publicly accessible. In some embodiments, if the second media item owner's media item is accessible after the expiration of the second media item owner's media usage token, the media usage rights platform may automatically update the second media item owner's media usage request and associated media usage token according to the terms of the original media usage request. In some embodiments, a media item created by a third media item owner that includes at least a portion of a first media item owner's media item may be located (e.g., on a content sharing platform). If the media usage rights platform determines that the third media item owner does not have a valid media usage token associated with the second media item owner's media item, the media usage rights platform may send a media usage proposal to the third media item owner. The media usage proposal may include one or more media usage options associated with the first media item owner's media item. If the third media item owner accepts the media usage proposal, the media usage rights platform may provide the third media item owner with a media usage token. In some embodiments, the media usage rights platform may require the third media item owner to provide payment based on the use of the second media item owner's media item before granting the media usage token. In some embodiments, the media usage rights platform may expose an application programming interface (API) that allows the content sharing platform to interact with the media usage rights platform. For example, a content sharing platform may allow a media item owner to upload a media item to the content sharing platform and specify one or more media usage options associated with the media item. The content sharing platform may then send the media item and media usage options to the media usage rights platform via the API. In some embodiments, when a media item owner interacts with a specific media item on the content sharing platform, the content sharing platform may allow the media item owner to submit a media usage request for the media item to the media usage rights platform. In some embodiments, a content sharing platform may track user interactions with media items (e.g., licensed media items) that have corresponding media usage tokens and transmit interaction statistics to the media usage rights platform via the API. For example, when a licensed media item is viewed or listened to, the content sharing platform may notify the media usage rights platform. The content sharing platform may require a media item owner who uploads a media item containing one or more licensed media items to include the media usage token(s) associated with the licensed media item(s) on the content sharing platform. In some embodiments, if a media usage token is included in a media item on a content sharing platform, the content sharing platform may check the status of the media usage token via an API of the media usage rights platform. For example, if the media usage token expires when the content sharing platform checks the status of the media usage token, the content sharing platform may prevent the user from interacting with the media item with the expired media usage token. In some embodiments, a content licensing platform may allow licensing fees to be passed on to consumers of media items rather than being paid by the licensor, the media item owner. For example, a media item owner may license a media item using an agreement to pay a certain amount each time a user interacts with the licensed media item. The licensor may then upload its new media item (which includes the licensed media item) along with a media usage token to a content sharing platform. Before a user can interact with the licensor's media item, the content sharing platform may require the user to agree to pay an amount that satisfies the media usage agreement. Thus, aspects of the present invention provide a mechanism for facilitating media usage agreements between media item owners and tracking the execution of such agreements. This improves workflow within the content sharing platform and consumes less computing resources of the content sharing platform to detect and prevent potential infringement by media item owners. Consequently, more computing resources can be used for other processes within the content sharing platform, which can improve the overall efficiency of the content sharing platform and reduce overall latency. 1 illustrates an exemplary system architecture 100 for authorizing media usage agreements between content creators according to some embodiments. The system architecture 100 includes a media usage rights server 110, a content sharing platform 140, a data storage 150, a network 130, and client devices 160A to 160Z. The content sharing platform 140 may include one or more servers and may enable users to consume, upload, share, search, like ("like"), dislike, and / or comment on media items 112A-112N (collectively referred to herein as "media items 112"). The content sharing platform 140 may include a website (e.g., a webpage) or application backend software for providing a user with access to media items (e.g., via a client device 160). A media item may be consumed via the Internet or via a mobile application on the client device 160. A media item may correspond to a media file (e.g., a video file, an audio file, etc.) or a portion of a media file (e.g., a portion or block of a video file, an audio file, etc.). As used herein, "media," "media item," "online media item," "digital media," "digital media item," "content," and "content item" may include an electronic file that can be executed or loaded using software, firmware, or hardware configured to present a digital media item to an entity. In some embodiments, media item 112 is a video item. A video item refers to a set of sequential video frames (e.g., image frames) representing a moving scene. For example, a series of sequential video frames can be captured continuously or later reconstructed to produce an animation. Video items can be provided in various formats, including, but not limited to, analog, digital, two-dimensional, and three-dimensional video. In addition, a video item can include a movie, a video clip, or any set of animated images displayed in sequence. In some embodiments, a video item can be stored (e.g., at data storage 150) as a video file comprising a video component and an audio component. The video component can include video data corresponding to one or more sequential video frames of the video item. The audio component may include audio data corresponding to the video data. The media usage rights server 110 may include a media usage rights platform 120. The media usage rights server 110 may be a rack-mounted server, a router computer, a server computer, a personal computer, a mainframe computer, a laptop computer, a tablet computer, a desktop computer, or the like. The media usage rights server 110 may be part of the content sharing platform 140 or part of another system. In some embodiments, the media usage rights server 110 may be connected to the data storage 150 via a network 130. The network 130 may be a public network (e.g., the Internet), a private network (e.g., a local area network (LAN)), a wide area network (WAN), a wired network (e.g., Ethernet), a wireless network (e.g., an 802.11 network), a cellular network (e.g., a long-term evolution (LTE) network), and / or a combination thereof. In some embodiments, the data storage 150 may be part of the media usage rights server 110. Data storage 150 may reside in memory (e.g., random access memory), cache, a drive (e.g., a hard drive, a solid-state drive), a flash drive, etc., and may be part of one or more database systems, one or more file systems, one or more distributed ledgers, or another type of component or device capable of storing data. Data storage 150 may include multiple storage components (e.g., multiple drives or multiple databases) that may also span multiple computing devices (e.g., multiple server computers). Data storage 150 may be a persistent storage device capable of storing data. A persistent storage device may be a local storage unit or a remote storage unit, an electronic storage unit (e.g., main memory), or a similar storage unit. The persistent storage device may be a single-chip device or a group of distributed devices. Client devices 160A to 160Z may include devices such as televisions, smartphones, personal digital assistants, portable media players, laptops, e-book readers, tablet computers, desktop computers, game consoles, set-top boxes, or the like. Client devices 160A to 160Z may each include a media item 162A to 162Z and / or a media usage token 164A to 164Z. Client device 160A may correspond to an authorizer, an authorized person, a content sharing platform user, or another user. If client device 160A corresponds to an authorizer, media item 162A may be a media item created by the authorizer. Client device 160A may upload media item 162A to content sharing platform 140 or media usage rights server 110 via network 130. Client device 160A may also upload media usage options (not shown) corresponding to media item 162A. If client device 160A corresponds to a licensee, media item 162A may be a media item created by a licensee, including a licensed media item created by a licensor. Media usage token 164A may correspond to a media item created by the licensor. Examples of media items 162A-162Z may include, but are not limited to, digital videos, digital movies, animated images, digital photos, digital music, digital audio, digital video games, collaborative media content presentations, website content, social media updates, e-books, e-journals, digital audiobooks, online blogs, software applications, and the like. In general, functions described in one embodiment as being performed by the content sharing platform 140 and / or the media usage rights server 110 may also be appropriately performed on the client device 160 in other embodiments. Furthermore, functionality attributed to a particular component may be performed by different or multiple components operating together. The content sharing platform 140 and / or the media usage rights server 110 may also be provided as a service to other systems or devices via an appropriate application programming interface and is therefore not limited to use within a website. It should be noted that although some embodiments of the present invention are directed to a content sharing platform, the embodiments of the present invention can be applied to other types of platforms. For example, the embodiments of the present invention can be applied to a content file platform, a content storage platform, etc. In embodiments of the present invention, a "user" or an "owner" may be represented as a single individual. However, other embodiments of the present invention encompass a "user" or an "owner" as an entity controlled by a group of users and / or an automated source. For example, a group of individual users or owners united as a community on a social network may be considered a "user" or an "owner." In another example, an automated consumer may be an automated ingestion pipeline of the content sharing platform 140 or the media usage rights server 110, such as a topic channel. In situations where the systems discussed herein collect personal information about users (including owners) or may use personal information, users may be provided with an opportunity to control whether the content sharing platform 140 or the media usage rights server 110 collects user information (e.g., information about a user's social network, social actions or activities, occupation, a user's hobbies, or a user's current location) or to control whether and / or how content that may be more relevant to the user is received from the content server. In addition, certain data may be processed in one or more ways to remove personally identifiable information before being stored or used. For example, a user's identity may be processed so that the user's personally identifiable information cannot be determined, or a user's geographic location may be generalized (such as to a city, zip code, or state level) when obtaining location information so that a specific location of the user cannot be determined. Thus, users may control how information about users is collected and how it is used by the content sharing platform 140 or the media usage rights server 110. FIG2 illustrates an exemplary system architecture 200 for authorizing media usage agreements between content creators according to some embodiments. The media usage rights platform 120 may include a token manager 210, a usage tracker 220, a payment manager 230, and an application programming interface (API) 240. The token manager 210 may generate media usage tokens based on media usage requests. The token manager 210 may store the media usage tokens in the data storage 150 (e.g., media usage tokens 164A to 164Z). Each media usage token may have a corresponding unique identifier. The token manager 210 may store attributes of the media usage tokens. For example, each media usage token may have attributes including an associated media item owner (e.g., a content creator), an associated media item, an associated media usage option with an associated payment scheme, an expiration condition, and a status. The status may indicate whether the media usage token is valid or expired. The attributes of the media usage token may be stored in the data storage 150 along with the media usage token. In some embodiments, the token manager 210 may also process media items, media usage options, and media usage requests. For example, the token manager 210 may receive a media item (e.g., media item 162A) with one or more associated media usage options (e.g., media usage options 250A-250Z) from a media item owner. The token manager 210 may generate an identifier for the media item and each media usage option. The token manager 210 may store the media item (e.g., media items 162A-162Z) and / or the corresponding identifier along with the media usage option(s) (e.g., media usage options 250A-250Z) and / or their identifiers in the data storage 150. Upon receiving a media usage request (e.g., media usage requests 260A-260Z), the token manager 210 may store the media usage request (and / or an identifier of the media usage request) in the data storage 150. As mentioned above, the data store 150 can be a relational database, a non-relational database, a distributed ledger, another form of persistent storage, or any combination thereof. The usage tracker 220 can monitor the use of media usage tokens and licensed media items. For example, if the payment scheme corresponding to a media usage token depends on interaction with a licensee's media items, the usage tracker 220 can track the number of times a user interacts with the licensee's media items. In some embodiments, the usage tracker 220 can receive interaction statistics (e.g., the number of user interactions) from a content sharing platform. In some embodiments, the usage tracker 220 can monitor a publicly accessible uniform resource locator (URL) associated with the licensee's media items. For example, if a media usage token has a predetermined duration as an expiration condition, the usage tracker 220 can attempt to access the publicly accessible URL after the predetermined duration has elapsed since the creation of the media usage token (e.g., after the media usage token expires). In some embodiments, if the media item remains publicly accessible after the media usage token expires, the media usage request can be automatically updated. In some embodiments, a media usage token may have an expiration condition based on the number of interactions with the licensee's media items. In some embodiments, a media usage token may have an expiration condition based on the number of interactions with the licensor's media items within the licensee's media items. If a media usage token has an expiration condition based on the number of interactions (e.g., interactions by users of a content sharing platform), the usage tracker 220 may mark the media usage token as expired (e.g., by changing the status attribute of the media usage token to "expired") after the number of interactions with the licensee's media items exceeds a threshold value specified in the expiration condition. The payment manager 230 can receive payments from media item owners associated with media usage tokens. For example, if a media option requires payment of a fee (e.g., a licensing fee) before generating a media usage token, the payment manager 230 can send a payment request (e.g., an invoice) to the media item owner requesting the media usage token. Upon receiving the completed payment, the payment manager 230 can signal the token manager 210 to generate a media usage token for the media item owner. The payment manager 230 can also receive and / or request payment from the media item owner after the media item owner receives a media usage token. For example, if the payment scheme associated with the media usage token requires payment based on the number of user interactions, the payment manager 230 can request regular (e.g., daily, weekly, monthly, or the like) payments from the media item owner based on the number of interactions reported by the usage tracker 220. In some embodiments, the payment manager 230 can automatically withdraw funds from an account associated with the media item owner (e.g., a bank account, a credit account, an expense account, a cryptocurrency account) according to the payment scheme of the media usage option selected by the media item owner. The API 240 can interact with the token manager 210, the usage tracker 220, and the payment manager 230. In some embodiments, the API 240 can allow other platforms (e.g., the content sharing platform 140) to interact with the media usage rights platform 120. For example, the content sharing platform 140 can use the API 240 to send user interaction statistics related to a media item to the media usage rights platform 120. In some embodiments, the content sharing platform 140 can use the API 240 to allow a media item owner to submit a media item and corresponding media usage options to the media usage rights platform 120 when using the content sharing platform 140. 3A is a sequence diagram 300 of a media usage agreement for licensing content creators according to some embodiments. The licensor device 310 may correspond to a user device of a first media item owner, and the licensee device 320 may correspond to a user device of a second media item owner. The licensor device 310 may send (322) a first media item to the media usage rights platform 120. The media usage rights platform 120 may generate (324) a first media item identifier. The media usage rights platform 120 may store (326) the first media item identifier in the data storage 150. The licensor device 310 may send (328) one or more media usage options to the media usage rights platform 120. The media usage rights platform 120 may generate (330) one or more media usage option identifiers and may then store (332) the one or more media usage option identifiers in the data storage 150. The licensee device 320 may send (334) a media usage request to the media usage rights platform 120. The media usage rights platform 120 may store (336) the media usage request in the data storage 150. In some embodiments, the media usage rights platform 120 may request (338) approval of the media usage request from the authorizer device 310. The authorizer device 310 may send (340) approval of the media usage request to the media usage rights platform 120. The media usage rights platform 120 may then generate (342) a media usage token. In some embodiments, the media usage rights platform 120 may request payment of a fee from the licensee device 320 before generating a media usage token. The media usage rights platform 120 stores (344) the media usage token in the data storage 150. The media usage rights platform transmits (346) the media usage token to the licensee device 320. 3B is a sequence diagram 350 for authorizing a media usage agreement between content creators according to some embodiments. User device 360 ​​may correspond to a user device of a user interacting with a media item (e.g., a user of a content sharing platform). Licensee device 320 may upload (362) a second media item to content sharing platform 140. Licensee device 320 may upload (364) a media usage token to content sharing platform 140. User device 360 ​​may interact with the second media item (366). Content sharing platform 140 may send (368) interaction statistics related to the second media item and the media usage token to media usage rights platform 120 (e.g., via API 240). In some embodiments, media usage rights platform 120 may request (370) payment from licensee device 320. Licensee device 320 may send (372) payment to media usage rights platform 120. Media usage rights platform 120 may transmit (374) the payment to licensor device 310. FIG4 is a flow chart illustrating an exemplary method 400 for authorizing a media usage agreement between content creators, according to some embodiments. Method 400 may be performed by processing logic, which may include hardware (e.g., circuitry, dedicated logic, programmable logic, microcode, a processing device, etc.), software (e.g., instructions executed on a processing device, a general-purpose computer system, or a dedicated machine), firmware, microcode, or a combination thereof. In some embodiments, method 400 may be performed in part by media usage rights server 110 and / or client devices 160A-160Z of FIG1 . In some embodiments, a non-transitory machine-readable storage medium stores instructions that, when executed by a processing device (e.g., of media usage rights server 110), cause the processing device to perform method 400. For simplicity of explanation, method 400 is depicted and described as a series of operations. However, operations according to the present invention may occur in various orders and / or concurrently with other operations not shown and described herein. Furthermore, less than all of the illustrated operations may be performed to implement method 400 according to the subject matter of the present invention. Furthermore, those skilled in the art will appreciate that method 400 may alternatively be represented as a series of interrelated states via a state diagram or events. 4 , in block 410, processing logic implementing method 400 may generate a first media item identifier for a first media item of a first media item owner, the first media item being associated with one or more media usage options. In block 420, processing logic may generate a media usage option identifier for each of the one or more media usage options. In block 430, processing logic may store the first media identifier and the one or more media usage option identifiers. In block 440, processing logic may receive a media usage request from a second media item owner, the media usage request identifying the first media item and a selected media usage option. In block 450, upon determining that the media usage request satisfies one or more criteria regarding the selected media usage option, processing logic may generate a media usage token based on the media usage request and the selected media usage option. In block 460, processing logic may transmit the media usage token to a user device of the second media item owner to authorize the second media item owner to include at least a portion of the first media item in a second media item of the second media item owner. FIG5 is a block diagram of an exemplary computer system 500 according to an embodiment of the present invention. In some embodiments, computer system 500 can be connected to other computer systems (e.g., via a network, such as a local area network (LAN), an intranet, an extranet, or the Internet). Computer system 500 can operate as a server or client computer in a client-server environment or as a peer computer in a peer-to-peer or distributed network environment. Computer system 500 can be provided by a personal computer (PC), a tablet PC, a set-top box (STB), a personal digital assistant (PDA), a cellular phone, a network appliance, a server, a network router, switch, or bridge, or any device capable of executing a set of instructions (sequentially or otherwise) specifying an action to be taken by the device. Furthermore, the term "computer" shall include any collection of computers that individually or collectively execute a set (or multiple sets) of instructions to perform any one or more of the methods described herein. In another embodiment, the computer system 500 may include a processing device 502, a volatile memory 504 (such as random access memory (RAM)), a non-volatile memory 506 (such as read-only memory (ROM) or electrically erasable programmable ROM (EEPROM)), and a data storage device 518, which may communicate with each other via a bus 508. The processing device 502 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 that implements other types of instruction sets, or a microprocessor that implements a combination of multiple types of instruction sets) or a special-purpose 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). The computer system 500 may further include a network interface device 522 (e.g., coupled to the network 574). The computer system 500 may also include a video display unit 510 (e.g., an LCD), an alphanumeric input device 512 (e.g., a keyboard), a cursor control device 514 (e.g., a mouse), and a signal generating device 520. In some embodiments, the data storage device 518 may include a non-transitory computer-readable storage medium 524 (e.g., a non-transitory machine-readable medium) on which instructions 526 encoding any one or more of the methods described herein may be stored, including encoding components of Figures 1 and / or 2 (e.g., the media usage rights platform 120, the token manager 210, the usage tracker 220, the payment manager 230, etc.) and instructions for implementing the methods described herein. The instructions 526 may also reside, completely or partially, within the volatile memory 504 and / or the processing device 502 during execution thereof by the computer system 500 ; thus, the volatile memory 504 and the processing device 502 may also constitute machine-readable storage media. Although computer-readable storage medium 524 is shown as a single medium in the illustrative example, the term "computer-readable storage medium" shall include a single medium or multiple media (e.g., a centralized or distributed database and / or associated cache and servers) that store one or more sets of executable instructions. The term "computer-readable storage medium" shall also include any tangible medium that can store or encode a set of instructions executable by a computer, causing the computer to perform any one or more of the methodologies described herein. The term "computer-readable storage medium" shall include, but is not limited to, solid-state memory, optical media, and magnetic media. The methods, components, and features described herein may be implemented by discrete hardware components or may be integrated into the functionality of other hardware components, such as ASICs, FPGAs, DSPs, or similar devices. Furthermore, the methods, components, and features may be implemented by firmware modules or functional circuitry within a hardware device. Furthermore, the methods, components, and features may be implemented in any combination of hardware devices and computer program components, or in a computer program. Unless otherwise expressly stated, terms such as "receive," "execute," "provide," "obtain," "cause," "access," "determine," "add," "use," "train," "reduce," "generate," "correct," or the like refer to actions and procedures performed or implemented by a computer system to manipulate and transform data represented as physical (e.g., electronic) quantities within computer system registers and memories into other data similarly represented as physical quantities within computer system registers or memories or other such information storage, transmission, or display devices. In addition, as used herein, the terms "first," "second," "third," "fourth," etc. are meant to distinguish between different elements and should not be taken to have a sequential meaning based on their numerical designations. The 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. This computer program may be stored in a computer-readable tangible storage medium. 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 the methods described herein and / or their individual functions, routines, subroutines, or operations. Examples of structures for various such systems are described above. The foregoing description is intended to be illustrative and not restrictive. Although the present invention has been described with reference to certain illustrative examples and embodiments, it should be understood that the present invention is not limited to the described examples and embodiments. The scope of the present invention should be determined by reference to the following claims, along with the full scope of equivalents to which the claims are entitled. Reference throughout this specification to "one embodiment" or "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment. Thus, depending on the context, the phrase "in one embodiment" or "in an embodiment" appearing in various places throughout this specification may, but do not necessarily, refer to the same embodiment. Furthermore, the particular features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. To the extent that the terms "include," "have," "contain," variations thereof, and other similar terms are used in the descriptions or claims, these terms are intended to be inclusive in a manner similar to the term "comprise" as an open transition and do not exclude any additional or other elements. As used in this application, the terms "component," "module," "system," or the like are generally intended to refer to a computer-related entity, hardware (e.g., a circuit), software, a combination of hardware and software, or an entity associated with an operating machine having one or more specific functionalities. For example, a component may be, but is not limited to, a program running on a processor (e.g., a digital signal processor), a processor, an object, an executable code, a thread, a program, and / or a computer. For example, an application running on a controller and the controller may both be a component. One or more components may reside within a program and / or thread, and a component may be localized on one computer and / or distributed between two or more computers. Furthermore, a "device" may take the form of: specially designed hardware; generalized hardware specialized by executing software that causes the hardware to perform specific functions (e.g., generating points of interest and / or descriptors); software on a computer-readable medium; or a combination thereof. The aforementioned systems, circuits, modules, etc. have been described with respect to interactions between several components and / or blocks. It should be understood that such systems, circuits, components, blocks, etc. may include such components or specified subcomponents, some specified components or subcomponents, and / or additional components and according to various arrangements and / or components described above. Subcomponents may also be implemented as components that are communicatively coupled to other components rather than being included in a previous generation of components (hierarchy). In addition, it should be noted that one or more components may be combined into a single component that provides aggregate functionality or separated into several separate subcomponents, and any one or more intermediate layers (such as a management layer) may be provided to communicatively couple to such subcomponents to provide integrated functionality. Any component described herein may also interact with one or more other components not explicitly described herein but known to those skilled in the art. Furthermore, the terms “exemplary” or “exemplary” are used herein to mean serving as an example, instance, or illustration. Any aspect or design described herein as “exemplary” is not necessarily to be construed as better or superior to other aspects or designs. Rather, the use of the terms “exemplary” or “exemplary” is intended to present concepts in a specific manner. As used in this application, the term “or” is intended to mean an inclusive “or” rather than an exclusive “or.” That is, unless otherwise specified or clear from the context, “X employs A or B” is intended to mean any naturally inclusive permutation. That is, if X employs A, X employs B, or X employs both A and B, then “X employs A or B” is satisfied under any of the aforementioned instances. In addition, as used in this application and the accompanying claims, unless otherwise specified or clear from the context to refer to a singular form, the articles “a” and “an” should generally be interpreted to mean “one or more.” 100: System Architecture 110: Media Usage Rights Server 112: Media Items 112A to 112N: Media Items 120: Media Usage Rights Platform 130: Network 140: Content Sharing Platform 150: Data Storage 160: Client Devices 160A to 160Z: Client Devices 162A to 162Z: Media Items 164A to 164Z: Media Usage Tokens 200: System Architecture 210: Token Manager 220: Usage Tracker 230: Payment Manager 240: Application Programming Interface (API) 250A to 250Z: Media Usage Options 260A to 260Z: Media Usage Request 300: Sequence Diagram 310: Authorizer Device 320: Authorizee Device 322: Send 324: Generate 326: Store 328: Send 330: Generate 332: Store 334: Send 336: Store 338: Request 340: Send 342: Generate 344: Store 346: Transmit 350: Sequence Diagram 360: User Device 362: Upload 364: Upload 366: Interact 368: Send 370: Request 37 2: Send 374: Transmission 400: Method 410: Block 420: Block 430: Block 440: Block 450: Block 460: Block 500: Computer System 502: Processing Device 504: Volatile Memory 506: Non-Volatile Memory 508: Bus 510: Video Display Unit 512: Alphanumeric Input Device 514: Cursor Control Device 518: Data Storage Device 520: Signal Generator 522: Network Interface Device 524: Non-Transitory Computer-Readable Storage Medium 526: Instruction 574: Network A more complete understanding of the aspects and embodiments of the present invention will be obtained from the detailed description given below and from the accompanying drawings of various aspects and embodiments of the present invention. However, the same should not be construed as limiting the present invention to specific aspects or embodiments, but are for explanation and understanding only. FIG. 1 illustrates an exemplary system architecture for authorizing media usage agreements between content creators, according to some embodiments. FIG. 2 illustrates an exemplary system architecture for authorizing media usage agreements between content creators, according to some embodiments. FIG. 3A is a sequence diagram illustrating a protocol for authorizing media usage between content creators, according to some embodiments. FIG. 3B is a sequence diagram of a media usage protocol for authorizing content creators according to some embodiments. 4 is a flow chart illustrating an example method for authorizing a media usage agreement between content creators, according to some embodiments. FIG5 is a block diagram illustrating an exemplary computer system according to an embodiment of the present invention. 400:Method 410:Block 420:Block 430:Block 440:Block 450: Block 460:Block

Claims

1. A method for licensing media usage agreements between content creators, the method comprising: The process involves: generating a first media project identifier for a first media project owned by one of the first media project owners, the first media project being associated with one or more media usage options provided by the first media project owner, wherein each media usage option defines the right to incorporate a portion of the first media project into a new media project created by another media project owner; generating a media usage option identifier for each of the one or more media usage options; storing the first media project identifier and the one or more media usage option identifiers; receiving a media usage request from one of the second media project owners to authorize the incorporation of a specified portion of the first media project into a second media project created by the second media project owner, the media usage request identifying the first media project and a selected media usage option from the one or more media usage options; and generating a media usage token based on the media usage request and the selected media usage option when the media usage request is determined to meet one or more criteria regarding the selected media usage option. The media usage token is transmitted to the user device of one of the owners of the second media project to authorize the second media project owner to include at least a portion of the first media project in one of the second media project owners' second media projects; the use of the first media project associated with the media usage token of the second media project owner and the second media project is tracked; and payment is received from the second media project owner based on the selected media usage option and the tracked usage.

2. The method of request item 1, wherein the criteria for the selected media use option include at least one of the following: payment of a fee; or approval of the media use request by the owner of the first media project.

3. The method of claim 1, wherein the selected media usage option has an associated payment scheme including at least one of the following: a one-time payment amount; an amount per interaction with the second media item; an amount per interaction with the first media item within the second media item; or a percentage of the total revenue earned by the owner of the second media item in relation to the second media item.

4. The method of request item 1, further comprising: Receive one of the public Uniform Resource Locators (URLs) associated with this second media project; Access the public URL associated with the second media item after the expiration of the media usage mark; and automatically update the media usage request in response to the public accessibility of the second media item after the expiration of the media usage mark.

5. The method of request item 1, wherein the medium uses symbols based on a smart contract of a distributed ledger technology.

6. The method of claim 1, further comprising: The positioning includes one of the owners of the third media project, which is part of the first media project; and the transmission of a media use proposal to the owner of the third media project.

7. A computing system comprising: One memory; and one or more processors, coupled to the memory, for: generating a first media project identifier for a first media project owned by one of the first media project owners, the first media project being associated with one or more media usage options provided by the first media project owner, wherein each media usage option defines a right to incorporate a portion of the first media project into a new media project created by another media project owner; generating a media usage option identifier for each of the one or more media usage options; storing the first media project identifier and the one or more media usage option identifiers; receiving a media usage request from one of the second media project owners to authorize the incorporation of a specified portion of the first media project into a second media project created by the second media project owner, the media usage request identifying the first media project and a selected media usage option from the one or more media usage options; and generating a media usage identifier based on the media usage request and the selected media usage option when it is determined that the media usage request satisfies one or more criteria regarding the selected media usage option. The media usage token is transmitted to the user device of one of the owners of the second media project to authorize the second media project owner to include at least a portion of the first media project in one of the second media project owners' second media projects; the use of the first media project associated with the media usage token of the second media project owner and the second media project is tracked; and payment is received from the second media project owner based on the selected media usage option and the tracked usage.

8. The system of request item 7, wherein the criteria for the selected media use option include at least one of the following: payment of a fee; or approval of the media use request by the owner of the first media project.

9. The system of request item 7, wherein the selected media usage option has an associated payment scheme including at least one of the following: a one-time payment amount; an amount per interaction with the second media item; an amount per interaction with the first media item within the second media item; or a percentage of the total revenue earned by the owner of the second media item in relation to the second media item.

10. The system of request item 7, wherein the one or more processors are further configured to: receive a public Uniform Resource Locator (URL) associated with the second media item; access the public URL associated with the second media item after the media usage period expires; and automatically update the media usage request in response to the public access to the second media item after the media usage period expires.

11. The system of claim 7, wherein the media uses symbols based on a smart contract of a distributed ledger technology.

12. The system of claim 7, wherein the one or more processors are further configured to: locate a third media project including a third media project owner of a first media project; and transmit a media use proposal to the third media project owner.

13. A non-transitory computer-readable storage medium comprising instructions which, when executed by one or more processors, cause the one or more processors to perform operations, the operations including: The process involves: generating a first media project identifier for a first media project owned by one of the first media project owners, the first media project being associated with one or more media usage options provided by the first media project owner, wherein each media usage option defines the right to incorporate a portion of the first media project into a new media project created by another media project owner; generating a media usage option identifier for each of the one or more media usage options; storing the first media project identifier and the one or more media usage option identifiers; receiving a media usage request from one of the second media project owners to authorize the incorporation of a specified portion of the first media project into a second media project created by the second media project owner, the media usage request identifying the first media project and a selected media usage option from the one or more media usage options; and generating a media usage symbol based on the media usage request and the selected media usage option when the media usage request is determined to meet one or more criteria regarding the selected media usage option. The media usage token is transmitted to the user device of one of the owners of the second media project to authorize the second media project owner to include at least a portion of the first media project in one of the second media project owners' second media projects; the use of the first media project associated with the media usage token of the second media project owner and the second media project is tracked; and payment is received from the second media project owner based on the selected media usage option and the tracked usage.

14. The non-transitory computer-readable storage medium as in claim 13, wherein the criteria for the use of the selected medium include at least one of the following: payment of a fee; or approval of the use request for the medium by the owner of the first media item.

15. The non-transitory computer-readable storage medium of claim 13, wherein the selected media use option has an associated payment scheme including at least one of the following: a one-time payment amount; an amount per interaction with the second media item; an amount per interaction with the first media item within the second media item; or a percentage of the total revenue earned by the owner of the second media item in relation to the second media item.

16. The non-transitory computer-readable storage medium as requested in item 13, wherein the instructions further cause one or more processors to perform operations including: receiving a public Uniform Resource Locator (URL) associated with the second media item; accessing the public URL associated with the second media item after the media usage period expires; and automatically updating the media usage request in response to the public accessibility of the second media item after the media usage period expires.

17. The non-transitory computer-readable storage medium of claim 13, wherein the medium uses symbols based on a smart contract of a distributed ledger technology.

Images