WO2015175566A1 - Combined music rights licensing and royalty tracking system and methods - Google Patents

Combined music rights licensing and royalty tracking system and methods Download PDF

Info

Publication number
WO2015175566A1
WO2015175566A1 PCT/US2015/030425 US2015030425W WO2015175566A1 WO 2015175566 A1 WO2015175566 A1 WO 2015175566A1 US 2015030425 W US2015030425 W US 2015030425W WO 2015175566 A1 WO2015175566 A1 WO 2015175566A1
Authority
WO
WIPO (PCT)
Prior art keywords
music
license
rights
publisher
interface
Prior art date
Application number
PCT/US2015/030425
Other languages
French (fr)
Inventor
Kenneth C. BOOTH
Mark A. GREENBURG
Original Assignee
Tresona Multimedia, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Tresona Multimedia, Llc filed Critical Tresona Multimedia, Llc
Publication of WO2015175566A1 publication Critical patent/WO2015175566A1/en

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]

Definitions

  • a music rights license request system may comprise a processor running system software, associated with at least one music rights information database, and comprising a public user interface comprising a music rights license request interface configured to receive a music rights license request from a public user through the public user interface for a music rights license relating to at least one specifically identified music asset, and notify the public user of at least one change in a status of the music rights license request, a copyright owner interface configured to notify at least one music publisher of the specifically identified music asset when the music rights license request is received and to receive input from the at least one music publisher to at least one of approve, deny, approve with restrictions, and pre-approve at least one of the request from the public user for the music rights license, and future requests for music rights licenses relating to the at least one specifically identified music asset, and an agreement generator configured to generate at least one agreement between the at least one music publisher and at least one of the public user, a music organization associated with the public user, and a music arranger who will create a
  • the at least one music rights information database may comprise information regarding at least one of music titles, music composers, music arrangers, music publishers, music owners, music instrumentation, music performers, stock music available and music ownership interests.
  • the music rights license request interface may further be configured to receive input from the public user to indicate what type of music rights license is being requested, the type of music rights license comprising one of a music custom arrangement license, a music mechanical license, a master recording use license, and a music synchronization license.
  • the music rights license request module may further be configured to receive input from the user to indicate whether the music rights license relates to a medley comprising more than one specifically identified musical work.
  • the music rights license request may be configured for a music custom arrangement license and the system is further configured to receive input from the public user to identify a music arranger for the at least one specifically identified music asset.
  • the agreement generator may further be configured to generate a work for hire agreement between the music arranger for the at least one specifically identified music asset and the at least one music publisher relating to the at least one specifically identified music asset.
  • the work for hire agreement generated by the agreement generator may be taken from specific contract language approved by the at least one music publisher and is different from specific contract language approved by at least one other music publisher.
  • the public user interface may be adapted to a role of the public user and is at least one of a musical organization director and a music arranger.
  • the public user interface may comprise a checklist of work to be done to finalize the music rights license request that includes reminders specific to the role of the public user.
  • the music rights license request module may comprise a database search field configured to query the at least one music rights information database for at least one of a musical work title, a music performer, a music owner and a music composer for the at least one specifically identified musical work.
  • the music rights license request module may comprise a new musical work submission option configured to receive at least a title of a new musical work not found in the at least one music rights information database by the public user's search, which new musical work submission option submits the title to an administrator for addition to the at least one music rights information database or matching with an appropriate record in the at least one music rights information database.
  • a music publisher interface configured to provide the music publisher with at least one of an indication of the status of the music rights license request and a monetary report indicating the publisher's revenue relating to the at least one specifically identified musical work.
  • a payment interface configured to notify the public user of a payment due after the publisher approves the music license request.
  • a musical license approval system may comprise an interface where publishers view requests for song licenses and those requests may be reviewed, accepted, denied, approved with restrictions, or pre-approved, and wherein a publisher may limit the use of licenses for different songs based on the needs of the artists holding copyright ownership.
  • Particular embodiments may comprise one or more of the following.
  • aspects of the disclosure relate to a musical license management system comprising creating and storing a valid license certificate for a custom arrangement for future reference by a licensee, a checking system for verifying that a license is valid for a particular composition to a particular performing organization, a delivery system for the delivery of custom arrangements and accompaniment tracks to licensees after such have been uploaded by the publisher, wherein licensees and publishers verify the validity of licenses, upload and download custom arrangements, and sheet music.
  • Particular embodiments may further comprise printed copyright information and license term information on each sheet of the arrangement delivered by the publisher.
  • aspects of the disclosure relate to payment tracking system comprising an interface for viewing payments and tracking payments due to a given publisher, a search function wherein specified companies can request a viewing of payments due or received over specified date ranges, wherein publishers representing artists with copyright ownership are able to track the revenue earned over specified periods of time and are able to better track licensing business.
  • Particular embodiments may comprise one or more of the following.
  • Payment information may be updated automatically and in real-time by the system. Payment information may be updated manually.
  • FIG. 1 illustrates a user interface for creating and editing a user account on an automated music rights licensing and royalty tracking system
  • FIG. 2 illustrates a user interface for requesting new musical arrangements
  • FIG. 3 illustrates the availability and licensing restrictions of particular songs and artists
  • FIG. 4 illustrates licensee payment options, arranger or director assignment, and note leaving section
  • FIG. 5 illustrates a licensee checklist center where each required function of both licensee and publisher is displayed along with progress
  • FIG. 6 illustrates a publisher license request interface where publisher can approve or deny requests
  • FIG. 7 illustrates a publisher interface where ownership in songs can be verified and disputed
  • FIG. 8 illustrates a publisher interface where restrictions and terms can be placed on granted licenses
  • FIG. 9 illustrates a publisher interface where payments due to the publisher are updated and can be tracked in real-time
  • FIG. 10 illustrates a distribution network for client recordings and films
  • FIG. 11 illustrates a master recording automated music rights licensing and royalty tracking system
  • FIG. 12 is a schematic block diagram illustrating a suitable operating environment for aspects of the disclosure.
  • FIG. 13 is a schematic block diagram of a sample computing environment. DESCRIPTION
  • the present disclosure relates to a solution to issuing licensing for music copyright rights, tracking the rights for publishers and for performers, and compensating all of the appropriate parties for the licensed rights and for resulting music performance recording sales.
  • an automated music rights licensing and royalty tracking system may be applied to any type of music copyright license including, but not limited to, mechanical licenses and other audio-only rights licenses, synchronization licenses for any entertainment industry, movie, video game, commercial, television, DVD or Internet use, custom music arrangements, master recording use licenses, grand rights and other performance rights licenses, sheet music publishing, music product sales, and any other copyright right license available.
  • An automated music rights licensing and royalty tracking system is a combination of a system, methods and individual parts of the system and methods that interface with a music rights requester and/or the music publisher to enable the rights requestor to request music rights, complete the required licensing paperwork particular to the rights requested, have it authorized by the publisher(s), track custom arrangements and/or recordings being uploaded, make payment from the customer, track payments received and distribute payments to the publishers.
  • Embodiments of an automated music rights licensing and royalty tracking system and its parts may solve one or more of the problems discussed above by enabling publishers to identify their rights and their proportional share of the rights, automatically or manually grant rights to rights requestors, and instantly track revenue from every source with whom they are interacting.
  • An automated music rights licensing and royalty tracking system a non-limiting embodiment of which directed specifically to custom music arrangement rights but which, using the same principles and a similar interface, could be directed to other music copyright rights.
  • An automated music rights licensing and royalty tracking system may be used by purchasers of custom arrangement licensing to apply for and obtain custom arrangement licenses and by publishers to administer their music catalogues.
  • An advantage of using an automated music rights licensing and royalty tracking system over a system where music organization legal departments directly interact to negotiate fees and track and report revenues, is that an automated music rights licensing and royalty tracking system can frequently deliver the license that is required instantly at a consistent or at least at a pre-determined price, and provides instant feedback on the status of a music licensing request and all revenues received in its commercial life.
  • the director or arranger of a music ensemble is able to easily apply for the license through the online Interface, gauge the likelihood of obtaining a license in the case where the license cannot be granted instantly, and make instant substitutions when a license request is denied.
  • the music license requestor is not faced with tracking down multiple co-publishers to obtain independent licenses from each one, which is a very onerous task requiring expertise and often the advice of an attorney.
  • An automated music rights licensing and royalty tracking system consolidates this task automatically for both the requestor and the music owner.
  • FIG. 1 illustrates an interface that allows a music organization director or arranger to create or edit an account in the system to request new music copyright licenses and review the status of licenses already requested or granted.
  • the user may select the type of music license the user desires to request and the music asset, e.g. the particular song or master recording, the user desires to use for the license.
  • the user interface may include options for the particular user as a Director of a musical organization, an arranger of music, as illustrated in FIG. 2, or any other of a number of different roles in association with the music rights being requested.
  • the music copyright license the user desires may already have been pre-approved by the copyright owner for a given song and use.
  • the music copyright license may need to be approved by the copyright owner.
  • copyright owner it should be understood that in a large number of copyrights, the copyright owner is actually many different organizations, each owning a portion of the copyright right.
  • the system may request approval from one or more of those copyright owners depending upon the particular right being requested and the particular circumstances of the request, so the term copyright owner is intended to cover both the singular and plural.
  • a new license request may be made by searching an associated database of music assets and the licenses available for each asset.
  • an automated music rights license system if a particular music asset is available for instant approval and licensing, the user can select the song and initiate the transaction.
  • the first six items are color coded green
  • the seventh item is color coded red
  • the last four are color coded yellow.
  • the status of the availability of the song title in this case, is indicated by a color code of green for pre-approved, yellow for approval needed, and red for approval not likely.
  • a copyright owner interface allows a copyright owner to review all of its music assets for the various licenses that may be available through an interface, and pre- approve each music asset for particular uses and pricing based on the copyright owner's licensing criteria and preferences. That indication, then, is provided to the user so that a particular music organization does not have to waste time requesting licenses for music assets that are not going to be granted, or knows if they have a very short deadline for obtaining a license that they should select pre-approved assets for their particular purposes.
  • a user may be presented with a list of existing sheet music for the songs the user is interested in, that the user can purchase instead of requesting a new custom arrangement.
  • the user is able to make better financial decisions for the particular music organization they represent and arrangers have the ability to more widely extend their musical influence through wider dissemination of arrangements of which music organizations may not yet be aware.
  • multiple music assets may be used together for a project. For example, a music organization may desire to create a tribute to the Beatles that includes multiple Beatles songs within a single performance. In some cases, this requires a music arrangement called a medley.
  • An music copyright licensing system may ask the user if the music asset will be used as part of a medley.
  • copyright owners may place limitations on what other songs they do not want their music played with as a medley. This again allows for a user to know before hand the types of objections they may face in requesting approval and they can avoid those restrictions to more quickly obtain their desired licensing without the need to go back and forth with the copyright owners or their attorneys to personally explain the restrictions and intended uses.
  • the user After selecting additional medley song(s), if needed, the user confirms which music organization the license request is for (the default is set to the default music organization for the user). For particular music rights licenses, additional documentation is needed. For example, for music arrangement licenses, an arranger who is creating the musical arrangement under the license needs to also agree that the arranger understands that the music arrangement being created is a work for hire and will be owned by the copyright owner. The user also needs to indicate how the license fee will be paid and coordinate payment.
  • FIG. 4 provides an example of an interface that may be used with a music arrangement license where the user indicates who the particular music arranger is, how the license fee will be paid for, and other specific information about the use of the music asset for the license being requested.
  • the user may elect to pay immediately via credit card, they may request an invoice be sent to the user's address, may indicate that the arranger or director will pay, or may indicate that the requesting organization will pay.
  • the system may be configured so that payment cannot be received until the license has been approved. Thus, for licenses that are not pre-approved, payment will not be received despite the license request, until the copyright owner has approved the license request and terms. Once a license request is approved, payment may be made. Approval being received may be from one or all of the copyright owners depending upon the particular copyright right requested and the particular conditions for the license requested. In a particular embodiment of the system, all of the songs in a medley must be approved before payment is accepted and the songs are considered approved. AUTOMATED LICENSE APPROVAL SYSTEM FOR LICENSE REQUESTORS
  • the system is configured to take the request and related data and store it in a database associated with a computer server running the interface.
  • the database may also include access to a separate or incorporated database including the music assets listed in the interfaces and the copyright owner preferences and license criteria associated with each music asset and each music copyright license associated with each asset.
  • any of the parties associated with the licensing process has an option to select notification preferences.
  • the party may elect to receive notifications by email or text message or through the interface, or by any or all of the above.
  • the arranger is notified that a work for hire agreement is needed.
  • the arranger may then log in to the arranger's interface and see that the license being issued is dependent upon the work for hire agreement being signed.
  • the arranger interface is configured with an icon that, when clicked on, automatically generates, using an agreement generator running in association with the system, a work for hire agreement automatically formatted by the system to include the appropriate copyright and ownership information for the music assets requested and the information for the music organization the license relates to and the arranger who will be doing the arrangement.
  • the system may be configured to accept an electronic signature by the arranger, or for the arranger to print and scan in the work for hire agreement to upload to the system. Either way, when the signature is complete, the system updates the records associated with this particular license agreement and indicates that the work for hire agreement is completed.
  • the user's interface includes a list of license request relevant to their role in the licensing process.
  • the list of licensing requests includes a request number, submission date and identifier, identification of the music rights to which the request relates, a status section including a checklist of each paperwork or status change required for each step of the approval process.
  • the work for hire agreement needs to be signed by the arranger
  • the song(s) need to be approved for the custom arrangement by the publisher
  • licensing fees need to be paid and a copy of the music arrangement needs to be uploaded to the system for the publisher.
  • FIG. 5 illustrates a non-limiting example of an exemplary listing for a single song.
  • a listing of actions currently required by the user/account holder who is reviewing the display - the director and arranger and publisher will each have different actions required at different times to complete a license request - an identification of the arranger for the particular arrangement (in the case of a custom music arrangement license request), and a notes section where the different related parties can associate notes with the request for all parties to review is also included.
  • each item to be completed in the list includes a color coded symbol to indicate whether it is completed. For example, a green check mark for completed or a red exclamation point for uncompleted.
  • each license within the list may also be color coded to know the status of its completion toward approval by the copyright owner - green for approved, yellow for pending publisher Response, and red for denied as illustrated in FIG. 5. Recall that some copyright license requests are pre-approved (green), some need approval by the copyright owner (yellow), and some are already known to be extremely difficult or impossible to obtain permission to use (red). [0039] When any change is made in the system, each party involved in the process for that particular license request (director, arranger, publisher, performer, etc.) is notified. For example, when a director requests a license or licenses, the associated arranger(s) as well as the related publisher(s) are each notified and a status update is posted in their respective user interfaces.
  • the work for hire agreements as required by each publisher are automatically generated to be signed by the arranger.
  • a checklist to be completed to enable the license to be issued to the music organization is especially useful to the license requestor, in that he is able to track the progress of the request, and is notified every step of the way as progress is made by the publishers, or if further action is needed on his part or that of his organization.
  • the last step in the process is for the arranger to upload the actual music arrangement license to the system. Then the status of the request is changed to approved and a music license number can be issued. In that way, for each license issued, then the publisher is able to download the approved music arrangement and can watch for its use in the market.
  • a licensee has the ability to request a substitute song for approval, and again may select from the list of pre-approved songs, songs needing approval, or those songs that are not likely to become approved.
  • the interface for each copyright owner/publisher, or an administrator for the publisher allows the publisher to review each music asset and pre-approve particular licensing uses and pricing. For example, the publisher can pre- approve songs to indicate they are available for custom arrangements, or mark them not available or "need request” if the particular publisher wants to approve each request individually.
  • the publisher can also indicate through the publisher interface additional conditions of performance or use for the asset as restrictions on the license.
  • specific acknowledgment is required by at least one of the other parties associated with the creation or performance of the music under the license. For example, in the case of a custom music arrangement, both the director and arranger would need to specifically acknowledge the restrictions made by those publishers. Those specific acknowledgments are automatically generated by the system as part of the process for issuing the license through the checklist illustrated with FIG. 5.
  • FIG. 6 illustrates a non- limiting example of this publisher interface as applied to a custom music arrangement licensing system.
  • the requestor interface is immediately updated, and the requestor is is is notified of the changes made.
  • the requestor may then take action through the user interface to change music rights requested if a request is denied, substitute songs if only part of a request is denied, make payment on a license request that is approved, and download the sheet music that has been provided to the publishers.
  • FIG. 7 a screen of a copyright owner interface that shows the ownership share of the particular copyright owner in a variety of music assets.
  • the copyright owner interface allows the owner/publisher to verify ownership percentages of songs, and to record pro-rata ownership allocations to assist in accurate payments when licenses are issued for the respective music assets. Where an owner believes that its recorded or credited ownership share is incorrect, the user interface allows the owner to dispute the ownership percentage.
  • a system administrator then has the ability to research and verify the correct ownership
  • a screen of an owner interface illustrated in FIG. 8 allows an owner to place limitations on the licenses being approved to licensees such as the licensee usage duration or term, as well as limitations on the proper uses of that song or license, for example that a certain song cannot be played in a medley with other specified songs or artists.
  • An owner interface allows the flexibility to charge varying license prices based on several factors such as use of composition, type of performing group, size of performing group, and other factors. This allows the owner to automate its pricing models based on these programmable factors allowing for price uniformity among similar music performance organization types, groups, and sizes, or for particular uses such as Internet, television, video games or movies. It also allows the publisher to allow price-breaks for smaller organizations or groups with smaller budgets.
  • FIG. 9 illustrates a non-limiting example of a payment tracking interface for an automated copyright rights licensing system.
  • Each owner/publisher interface includes a similar screen specific to that particular publisher for music assets and/or license types associated with that publisher.
  • the payment tracking interface automatically updates through the processor associated with the database to update with new orders that are made, automatically allocating pro-rata payments due to all publishers who have ownership rights in the licenses that are issued or sales that are made.
  • By immediately and automatically updating the publisher interface with specific licensing revenue for each music asset on a real-time basis publishers have a transparent view into real revenues. Existing manual systems can take years to get payments to music publishers for similar license revenue.
  • the arranger uploads the custom arrangement digital sheet music into the database to associate with the license to finalize the license and allow the license to issue.
  • it may be configured to take the custom arrangement sheet music uploaded and automatically digitally imprint the sheet music with up to date and complete copyright information and the terms of the license printed on each sheet of the arrangement. Digital imprinting of documents is known in the art and there are existing programs that can accomplish this task.
  • the arranger may also upload a fully licensed accompaniment track of the music, or the music may be configured for display in a system that will generate the music shown in the sheet music as an audio sound to assist in practice of the music.
  • Particular embodiments of the system may also be configured to generate a custom arrangement sheet music is a license certificate showing the term and restrictions of the license agreement between the publisher(s) and licensee.
  • This certificate may be stored online and can be accessed, viewed, and printed by the licensee at any time. Further, publishers can access a verification system to verify that a particular performing organization has a valid license for a particular composition. These systems allow both licensees, publishers, even competition organizations and others in the public to verify that valid copyright licensing is in place for any performances, arrangements or other music asset usage that takes place if they have the music organization name and license number.
  • an automated music rights licensing and royalty tracking system take into account the different copyright laws of different countries.
  • the United States operates under what is called 100% licensing, which means that when a license is requested, the approval of just one of the publishers that has ownership rights is required in order for the license to be granted.
  • 100% licensing means that when a license is requested, the approval of just one of the publishers that has ownership rights is required in order for the license to be granted.
  • Another example is the European Union, where permission of every copyright owner is required to issue a license.
  • the system is automatically configured to notify all of the publishers holding ownership rights when a license request is made, and approval of all rights-holding publishers is sought by an automated music rights licensing and royalty tracking system.
  • FIG. 10 illustrates a non- limiting example of an automated music rights licensing and royalty tracking system embodied as a distribution network for client recordings and films, which is also tracked through the same database system and revenue and sales reports for publishers and for music organizations.
  • Each music organization may have its own affinity-based storefront through which music recordings are sold as downloads.
  • all mechanical and synchronization licensing for music recordings is paid by a company from sales proceeds.
  • An automated music rights licensing and royalty tracking system integrates music recording sales with the payment, tracking, and acquisition of the licensing required to enable the sales. In this way publishers can be assured that all copyright rights have been secured and the recordings being sold are in compliance with copyright laws in a simple, efficient manner.
  • the system may also be configured to automatically register the master recordings of the music performances with other distribution channels such as YouTube, The Orchard, iTunes, Google Play, Amazon, Spotify, Netflix, etc., as part of uploading a recording if the music organization's administrator selects the particular distribution channel for distribution.
  • other distribution channels such as YouTube, The Orchard, iTunes, Google Play, Amazon, Spotify, Netflix, etc.
  • FIG 11. illustrates a non-limiting example of an automated music rights licensing and royalty tracking system configured for licensing the master recordings of the music performances to the entertainment industry (TV, commercials, Internet, Video Games, movies, etc.), if the music organization elects to have the master recordings made available for consideration by the entertainment industry.
  • the entertainment industry TV, commercials, Internet, Video Games, movies, etc.
  • an automated music rights licensing and royalty tracking system for master recordings to license them to the entertainment industry
  • music and video supervisors for films, television shows, and advertising agencies are able to access the master recordings through an automated music rights licensing and royalty tracking system, search for recordings, select recordings on the basis of copyright status (public domain, copyright protected compositions that require additional licenses, or compositions where a particular company is in control of the copyright on the underlying composition.
  • Each master recording indicates in association with the recording whether the master recording is pre-cleared for use in entertainment, whether the master recording and synchronization licenses are pre-cleared, or whether a license is required (similar to other automated music rights licensing and royalty tracking system aspects discussed above).
  • master recordings can be automatically included in the searchable lists associated with this interface by the music organization that made the recording through the music organization's upload interface.
  • a component may be, but is not limited to being, a process running on a processor, a processor, an object, an instance, an executable, a thread of execution, a program, and/or a computer.
  • an application running on a computer and the computer can be a component.
  • One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
  • an exemplary environment 10 for implementing various aspects disclosed herein includes a computer 12 (e.g., desktop, laptop, server, hand held processing device, cellular phone device, programmable consumer or industrial electronics, and the like).
  • the computer 12 includes a processing unit 14, a system memory 16, and a system bus.
  • the system bus couples system components including, but not limited to, the system memory 16 to the processing unit 14.
  • the processing unit 14 can be any of various available
  • microprocessors are multi-core and other multiprocessor architectures. It is to be appreciated that dual microprocessors, multi-core and other multiprocessor architectures can be employed as the processing unit 14.
  • the system memory 16 includes volatile and nonvolatile memory.
  • the basic input/output system (BIOS) containing the basic routines to transfer information between elements within the computer 12, such as during start-up, is stored in nonvolatile memory.
  • nonvolatile memory can include read only memory (ROM) in some cases.
  • Volatile memory includes random access memory (RAM), which can act as external cache memory to facilitate processing.
  • Computer 12 may also include removable/non-removable, volatile/non-volatile computer storage media.
  • FIG. 3 illustrates, for example, mass storage 24.
  • Mass storage 24 includes, but is not limited to, devices like a magnetic or optical disk drive, floppy disk drive, flash memory, Internet cloud memory, or memory stick.
  • mass storage 24 can include storage media separately or in combination with other storage media.
  • FIG. 3 provides software application(s) 28 that act as an intermediary between users and/or other computers and the basic computer resources described in suitable operating environment 10.
  • Such software application(s) 28 include one or both of system and application software.
  • System software can include an operating system, which can be stored on mass storage 24 that acts to control and allocate resources of the computer system 12.
  • Application software takes advantage of the management of resources by system software through program modules and data stored on either or both of system memory 16 and mass storage 24.
  • Database data may be stored in system memory 16, mass storage 24, or some other storage associated with the computer 12.
  • the computer 12 also includes one or more interface components 26 that are communicatively coupled to the bus 18 and facilitate interaction with the computer 12.
  • the interface component 26 can be a port (e.g., serial, parallel, PCMCIA, USB, Fire Wire, and the like) or an interface card (e.g., sound, video, network, and the like) or the like.
  • the interface component 26 can receive input and provide output (wired or wirelessly). For instance, input can be received from devices including but not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, camera, other computer and the like.
  • Output can also be supplied by the computer 12 to output device(s) via interface component 26.
  • Output devices can include displays (e.g., CRT, LCD, plasma, projection, and the like), speakers, printers and other computers, among other things.
  • FIG. 4 is a schematic block diagram of a sample-computing environment 30 with which the subject innovation can interact.
  • the system 30 includes one or more client(s) 32, for example associated with a user's account.
  • the client(s) 32 can be hardware and/or software (e.g., threads, processes, computing devices).
  • the system 30 also includes one or more server(s) 34.
  • system 30 can correspond to a two-tier client server model or a multi-tier model (e.g., client, middle tier server, data server), amongst other models.
  • the server(s) 34 can also be hardware and/or software (e.g., threads, processes, computing devices).
  • the servers 34 can house threads to perform transformations by employing the aspects of the subject innovation, for example.
  • One possible communication between a client 32 and a server 34 may be in the form of a data packet transmitted between two or more computer processes while transmitting data from an account interface displaying on an account owner's computing device and an interface processor, or between an interface processor and an account owner's phone and/or data service carrier or a phone number and/or registration number registry, or between a phone and/or data service carrier and a phone number and/or registration number registry.
  • a communication framework 38 exists between the one or more client(s) 32 and the one or more server(s) to facilitate meaningful data transfer and communication.
  • system as used herein is intended to encompass a computer program accessible from any computer-readable device or media.
  • computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ).
  • a carrier wave can be employed to carry computer- readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN).
  • LAN local area network
  • systems/methods may be practiced with other computer system configurations, including single-processor, multiprocessor or multi-core processor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., personal digital assistant (PDA), phone, tablet, watch . . . ), microprocessor-based or programmable consumer or industrial electronics, and the like.
  • PDA personal digital assistant
  • the illustrated aspects may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. However, some, if not all aspects of the described subject matter can be practiced on stand-alone computers.
  • program modules may be located in both local and remote memory storage devices.
  • An exemplary environment for implementing various aspects disclosed herein includes a computer (e.g., desktop, laptop, server, hand held processing device, tablet, cellular phone device, programmable consumer or industrial electronics, and the like).
  • the computer includes a processing unit, a system memory, and a system bus.
  • the system bus couples system components including, but not limited to, the system memory to the processing unit.
  • the processing unit can be any of various available microprocessors. It is to be appreciated that dual microprocessors, multi-core and other multiprocessor architectures can be employed as the processing unit.
  • the system may also be implemented on an Internet accessible server to enable web-based access to the interfaces, screens and system by people all over the world.
  • Internet accessible server to enable web-based access to the interfaces, screens and system by people all over the world.
  • the system memory includes volatile and nonvolatile memory.
  • the basic input/output system (BIOS) containing the basic routines to transfer information between elements within the computer, such as during start-up, is stored in nonvolatile memory.
  • nonvolatile memory can include read only memory (ROM) in some cases.
  • Volatile memory includes random access memory (RAM), which can act as external cache memory to facilitate processing.
  • the computer may also include removable/non-removable, volatile/non-volatile computer storage media, for example, mass storage.
  • Mass storage includes, but is not limited to, devices like a magnetic or optical disk drive, floppy disk drive, flash memory, Internet cloud memory, or memory stick.
  • mass storage can include storage media separately or in combination with other storage media.
  • Software application(s) may act as an intermediary between users and/or other computers and the basic computer resources described in suitable operating environment.
  • Such software application(s) include one or both of system and application software.
  • System software can include an operating system, which can be stored on mass storage, that acts to control and allocate resources of the computer system.
  • Application software takes advantage of the management of resources by system software through program modules and data stored on either or both of system memory and mass storage. Database data may be stored in system memory, mass storage, or some other storage associated with the computer.
  • the computer also includes one or more interface components that are
  • the interface component can be a port (e.g., serial, parallel, PCMCIA, USB, Fire Wire, and the like) or an interface card (e.g., sound, video, network, and the like) or the like.
  • the interface component can receive input and provide output (wired or wirelessly).
  • input can be received from devices including but not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, camera, other computer and the like.
  • Output can also be supplied by the computer to output device(s) via interface component.
  • Output devices can include displays (e.g., CRT, LCD, plasma, projection, and the like), speakers, printers and other computers, among other things.
  • the system may include one or more client(s), for example associated with an account owner's account or tracking devices.
  • the client(s) can be hardware and/or software (e.g., threads, processes, computing devices).
  • the system also includes one or more server(s).
  • system can correspond to a two-tier client server model or a multi-tier model (e.g., client, middle tier server, data server), amongst other models.
  • the server(s) can also be hardware and/or software (e.g., threads, processes, computing devices).
  • the servers can house threads to perform transformations by employing the aspects of the subject innovation, for example.
  • One possible communication between a client and a server may be in the form of a data packet transmitted between two or more computer processes while transmitting data from an account interface displaying on an account owner's computing device and an interface processor, or between an interface processor and an account owner's phone and/or data service carrier.
  • a communication framework exists between the one or more client(s) and the one or more server(s) to facilitate meaningful data transfer and communication.
  • implementations are not limited to the specific components disclosed herein, as virtually any components consistent with the intended operation of a method and/or system implementation for an automated music rights licensing and royalty tracking system may be utilized. Accordingly, for example, although particular automated music rights licensing and royalty tracking system may be disclosed, such components may comprise any shape, size, style, type, model, version, class, grade and/or the like consistent with the intended operation of a method and/or system implementation for an automated music rights licensing and royalty tracking system may be used.

Abstract

A music rights license request system includes a processor running system software associated with at least one music rights information database with an interface that includes a music rights license request module configured to receive a request from a public user for a music rights license relating to at least one specifically identified music asset, a permission module configured to notify at least one music publisher of the specifically identified musical work when the request is received and to receive input from the at least one music publisher to at least one of approve, deny, approve with restrictions, and pre-approve at least one of the request from the public user for the music rights license, and future requests for music rights licenses relating to the at least one specifically identified musical work.

Description

COMBINED MUSIC RIGHTS LICENSING AND ROYALTY TRACKING SYSTEM
AND METHODS
RELATED APPLICATIONS
[0001] The present application is a continuation application to pending US patent application serial number 14/275,789, filed May 12, 2014, titled "COMBINED MUSIC RIGHTS LICENSING AND ROYALTY TRACKING SYSTEM AND METHODS," which claims priority to US provisional patent application serial number 61/822,089, filed May 10, 2013 to Booth et al., the entire disclosure of each of which are hereby incorporated herein by this reference.
BACKGROUND
1. Technical Field
[0002] Aspects of this document relate generally to automated systems and methods for licensing and tracking music and other copyright rights and royalties related to those rights.
2. Background Art
[0003] Many choirs, show choirs, marching bands, symphonies, and performance ensembles require customized music arrangement licenses for the music they perform. A music arranger or ensemble is required by law to secure an arrangement license from the copyright owner(s) before creating and distributing the custom music. Other licenses are also required for use of music copyright rights such as mechanical licenses and synchronization licenses when creating CDs and DVDs, synchronization licenses for Internet distribution or television or movie or video game display of a particular musical work and master recording use licenses. Obtaining the licensing required for music copyright use is difficult and expensive, and penalties for violations are costly. Copyright owners, and publishers who often own music and manage music rights for other owners, have been frustrated with the difficulty of this process because the legal costs in negotiating individual licenses with each music organization that wants to use a music copyright right and administering and monitoring the use of the music copyrighted work is time consuming. However, music organizations, and in particular educational music organizations, need music to perform and want to be able to provide their participants and audience with popular music. Additionally, they want to legally distribute their performance recordings and videos to the public without concern for copyright infringement. Yet, educational music organizations generally do not have much excess cash or legal departments who can readily negotiate the licenses needed, and due to the small license fees generated from such licenses, it is difficult for the publisher legal department to negotiate the license terms and cost affordably in a way that makes sense for both parties.
[0004] The music publishing industry has struggled for most of its existence to find affordable, reliable solutions for issuing small dollar amount licenses and tracking their revenue. Many songs have multiple publishers, each with varying degrees of ownership. Ownership is rarely split evenly and it is a cumbersome process to interact with all rights holders and determine who is owed what portion of the money from the commercial exploitation of a musical copyright right.
SUMMARY
[0005] Aspects of the disclosure relate to a music rights license request system that may comprise a processor running system software, associated with at least one music rights information database, and comprising a public user interface comprising a music rights license request interface configured to receive a music rights license request from a public user through the public user interface for a music rights license relating to at least one specifically identified music asset, and notify the public user of at least one change in a status of the music rights license request, a copyright owner interface configured to notify at least one music publisher of the specifically identified music asset when the music rights license request is received and to receive input from the at least one music publisher to at least one of approve, deny, approve with restrictions, and pre-approve at least one of the request from the public user for the music rights license, and future requests for music rights licenses relating to the at least one specifically identified music asset, and an agreement generator configured to generate at least one agreement between the at least one music publisher and at least one of the public user, a music organization associated with the public user, and a music arranger who will create a custom arrangement of the at least one specifically identified music asset.
[0006] Particular embodiments of the disclosure may include one or more of the following. The at least one music rights information database may comprise information regarding at least one of music titles, music composers, music arrangers, music publishers, music owners, music instrumentation, music performers, stock music available and music ownership interests. The music rights license request interface may further be configured to receive input from the public user to indicate what type of music rights license is being requested, the type of music rights license comprising one of a music custom arrangement license, a music mechanical license, a master recording use license, and a music synchronization license. The music rights license request module may further be configured to receive input from the user to indicate whether the music rights license relates to a medley comprising more than one specifically identified musical work. The music rights license request may be configured for a music custom arrangement license and the system is further configured to receive input from the public user to identify a music arranger for the at least one specifically identified music asset. The agreement generator may further be configured to generate a work for hire agreement between the music arranger for the at least one specifically identified music asset and the at least one music publisher relating to the at least one specifically identified music asset. The work for hire agreement generated by the agreement generator may be taken from specific contract language approved by the at least one music publisher and is different from specific contract language approved by at least one other music publisher. The public user interface may be adapted to a role of the public user and is at least one of a musical organization director and a music arranger. The public user interface may comprise a checklist of work to be done to finalize the music rights license request that includes reminders specific to the role of the public user. The music rights license request module may comprise a database search field configured to query the at least one music rights information database for at least one of a musical work title, a music performer, a music owner and a music composer for the at least one specifically identified musical work. The music rights license request module may comprise a new musical work submission option configured to receive at least a title of a new musical work not found in the at least one music rights information database by the public user's search, which new musical work submission option submits the title to an administrator for addition to the at least one music rights information database or matching with an appropriate record in the at least one music rights information database. A music publisher interface configured to provide the music publisher with at least one of an indication of the status of the music rights license request and a monetary report indicating the publisher's revenue relating to the at least one specifically identified musical work. A payment interface configured to notify the public user of a payment due after the publisher approves the music license request.
[0007] According to another aspect, a musical license approval system may comprise an interface where publishers view requests for song licenses and those requests may be reviewed, accepted, denied, approved with restrictions, or pre-approved, and wherein a publisher may limit the use of licenses for different songs based on the needs of the artists holding copyright ownership.
[0008] Particular embodiments may comprise one or more of the following. An interface wherein a publisher may review a requested custom arrangement. An interface for the limitation of the license term of a granted license. The ability of the publisher to vary license pricing based on factors not limited to the use of the composition, type of performing group, and size of performing group.
[0009] Aspects of the disclosure relate to a musical license management system comprising creating and storing a valid license certificate for a custom arrangement for future reference by a licensee, a checking system for verifying that a license is valid for a particular composition to a particular performing organization, a delivery system for the delivery of custom arrangements and accompaniment tracks to licensees after such have been uploaded by the publisher, wherein licensees and publishers verify the validity of licenses, upload and download custom arrangements, and sheet music. Particular embodiments may further comprise printed copyright information and license term information on each sheet of the arrangement delivered by the publisher.
[0010] Aspects of the disclosure relate to payment tracking system comprising an interface for viewing payments and tracking payments due to a given publisher, a search function wherein specified companies can request a viewing of payments due or received over specified date ranges, wherein publishers representing artists with copyright ownership are able to track the revenue earned over specified periods of time and are able to better track licensing business. Particular embodiments may comprise one or more of the following. Payment information may be updated automatically and in real-time by the system. Payment information may be updated manually. [0011] The foregoing and other aspects, features, and advantages will be apparent to those artisans of ordinary skill in the art from the DESCRIPTION and DRAWINGS, and from the CLAIMS.
BRIEF DESCRIPTION OF THE DRAWINGS
[0012] The invention will hereinafter be described in conjunction with the appended drawings, where like designations denote like elements, and:
[0013] FIG. 1 illustrates a user interface for creating and editing a user account on an automated music rights licensing and royalty tracking system;
[0014] FIG. 2 illustrates a user interface for requesting new musical arrangements;
[0015] FIG. 3 illustrates the availability and licensing restrictions of particular songs and artists;
[0016] FIG. 4 illustrates licensee payment options, arranger or director assignment, and note leaving section;
[0017] FIG. 5 illustrates a licensee checklist center where each required function of both licensee and publisher is displayed along with progress;
[0018] FIG. 6 illustrates a publisher license request interface where publisher can approve or deny requests;
[0019] FIG. 7 illustrates a publisher interface where ownership in songs can be verified and disputed;
[0020] FIG. 8 illustrates a publisher interface where restrictions and terms can be placed on granted licenses;
[0021] FIG. 9 illustrates a publisher interface where payments due to the publisher are updated and can be tracked in real-time;
[0022] FIG. 10 illustrates a distribution network for client recordings and films;
[0023] FIG. 11 illustrates a master recording automated music rights licensing and royalty tracking system;
[0001] FIG. 12 is a schematic block diagram illustrating a suitable operating environment for aspects of the disclosure; and
[0024] FIG. 13 is a schematic block diagram of a sample computing environment. DESCRIPTION
[0025] This disclosure, its aspects and implementations, are not limited to the specific license types, licensee user interfaces and methods, publisher user interfaces and methods, or other delivery and tracking methods as described herein. Many additional components and assembly procedures known in the art consistent with automated musical licensing and revenue tracking will become apparent for use with implementations of an automated music rights licensing and royalty tracking system from this disclosure. Accordingly, for example, although particular musical licensing and revenue tracking interfaces, methods, and delivery systems are disclosed, such interfaces, methods, and implementing components may comprise any shape, size, style, type, model, version, measurement, concentration, material, quantity, and/or the like as is known in the art for such systems and implementing components, consistent with the intended operation.
[0026] The present disclosure relates to a solution to issuing licensing for music copyright rights, tracking the rights for publishers and for performers, and compensating all of the appropriate parties for the licensed rights and for resulting music performance recording sales. It should be understood that although particular embodiments disclosed herein may relate to only particular music rights license types, like custom music arrangement licensing, an automated music rights licensing and royalty tracking system may be applied to any type of music copyright license including, but not limited to, mechanical licenses and other audio-only rights licenses, synchronization licenses for any entertainment industry, movie, video game, commercial, television, DVD or Internet use, custom music arrangements, master recording use licenses, grand rights and other performance rights licenses, sheet music publishing, music product sales, and any other copyright right license available.
[0027] An automated music rights licensing and royalty tracking system is a combination of a system, methods and individual parts of the system and methods that interface with a music rights requester and/or the music publisher to enable the rights requestor to request music rights, complete the required licensing paperwork particular to the rights requested, have it authorized by the publisher(s), track custom arrangements and/or recordings being uploaded, make payment from the customer, track payments received and distribute payments to the publishers.
Embodiments of an automated music rights licensing and royalty tracking system and its parts may solve one or more of the problems discussed above by enabling publishers to identify their rights and their proportional share of the rights, automatically or manually grant rights to rights requestors, and instantly track revenue from every source with whom they are interacting.
LICENSEE MUSIC RIGHTS LICENSE ACQUISITION SYSTEM
[0028] An automated music rights licensing and royalty tracking system, a non-limiting embodiment of which directed specifically to custom music arrangement rights but which, using the same principles and a similar interface, could be directed to other music copyright rights. An automated music rights licensing and royalty tracking system may be used by purchasers of custom arrangement licensing to apply for and obtain custom arrangement licenses and by publishers to administer their music catalogues. An advantage of using an automated music rights licensing and royalty tracking system over a system where music organization legal departments directly interact to negotiate fees and track and report revenues, is that an automated music rights licensing and royalty tracking system can frequently deliver the license that is required instantly at a consistent or at least at a pre-determined price, and provides instant feedback on the status of a music licensing request and all revenues received in its commercial life. The director or arranger of a music ensemble is able to easily apply for the license through the online Interface, gauge the likelihood of obtaining a license in the case where the license cannot be granted instantly, and make instant substitutions when a license request is denied. The music license requestor is not faced with tracking down multiple co-publishers to obtain independent licenses from each one, which is a very onerous task requiring expertise and often the advice of an attorney. An automated music rights licensing and royalty tracking system consolidates this task automatically for both the requestor and the music owner.
[0029] FIG. 1 illustrates an interface that allows a music organization director or arranger to create or edit an account in the system to request new music copyright licenses and review the status of licenses already requested or granted. Once a musical director or arranger account has been created, the user may select the type of music license the user desires to request and the music asset, e.g. the particular song or master recording, the user desires to use for the license. The user interface may include options for the particular user as a Director of a musical organization, an arranger of music, as illustrated in FIG. 2, or any other of a number of different roles in association with the music rights being requested. In many cases, the music copyright license the user desires may already have been pre-approved by the copyright owner for a given song and use. In other cases, the music copyright license may need to be approved by the copyright owner. When the term "copyright owner" is used, it should be understood that in a large number of copyrights, the copyright owner is actually many different organizations, each owning a portion of the copyright right. The system may request approval from one or more of those copyright owners depending upon the particular right being requested and the particular circumstances of the request, so the term copyright owner is intended to cover both the singular and plural. A new license request may be made by searching an associated database of music assets and the licenses available for each asset.
[0030] In embodiments of an automated music rights license system, if a particular music asset is available for instant approval and licensing, the user can select the song and initiate the transaction. In the particular embodiment of an interface illustrated in FIG. 3, the first six items are color coded green, the seventh item is color coded red and the last four are color coded yellow. In the display embodiment illustrated in FIG. 3, when a user performs a search for a particular music asset, the status of the availability of the song title, in this case, is indicated by a color code of green for pre-approved, yellow for approval needed, and red for approval not likely. As explained later below, a copyright owner interface allows a copyright owner to review all of its music assets for the various licenses that may be available through an interface, and pre- approve each music asset for particular uses and pricing based on the copyright owner's licensing criteria and preferences. That indication, then, is provided to the user so that a particular music organization does not have to waste time requesting licenses for music assets that are not going to be granted, or knows if they have a very short deadline for obtaining a license that they should select pre-approved assets for their particular purposes.
[0031] In particular embodiments of a custom arrangement license request system, a user may be presented with a list of existing sheet music for the songs the user is interested in, that the user can purchase instead of requesting a new custom arrangement. By providing the list of existing music beside the list of music assets for which the user can request a new arrangement, the user is able to make better financial decisions for the particular music organization they represent and arrangers have the ability to more widely extend their musical influence through wider dissemination of arrangements of which music organizations may not yet be aware. [0032] For particular uses, multiple music assets may be used together for a project. For example, a music organization may desire to create a tribute to the Beatles that includes multiple Beatles songs within a single performance. In some cases, this requires a music arrangement called a medley. An music copyright licensing system may ask the user if the music asset will be used as part of a medley. In some cases, copyright owners may place limitations on what other songs they do not want their music played with as a medley. This again allows for a user to know before hand the types of objections they may face in requesting approval and they can avoid those restrictions to more quickly obtain their desired licensing without the need to go back and forth with the copyright owners or their attorneys to personally explain the restrictions and intended uses.
[0033] After selecting additional medley song(s), if needed, the user confirms which music organization the license request is for (the default is set to the default music organization for the user). For particular music rights licenses, additional documentation is needed. For example, for music arrangement licenses, an arranger who is creating the musical arrangement under the license needs to also agree that the arranger understands that the music arrangement being created is a work for hire and will be owned by the copyright owner. The user also needs to indicate how the license fee will be paid and coordinate payment. FIG. 4 provides an example of an interface that may be used with a music arrangement license where the user indicates who the particular music arranger is, how the license fee will be paid for, and other specific information about the use of the music asset for the license being requested. In this particular embodiment, the user may elect to pay immediately via credit card, they may request an invoice be sent to the user's address, may indicate that the arranger or director will pay, or may indicate that the requesting organization will pay. For particular embodiments, the system may be configured so that payment cannot be received until the license has been approved. Thus, for licenses that are not pre-approved, payment will not be received despite the license request, until the copyright owner has approved the license request and terms. Once a license request is approved, payment may be made. Approval being received may be from one or all of the copyright owners depending upon the particular copyright right requested and the particular conditions for the license requested. In a particular embodiment of the system, all of the songs in a medley must be approved before payment is accepted and the songs are considered approved. AUTOMATED LICENSE APPROVAL SYSTEM FOR LICENSE REQUESTORS
[0034] Once the user has completed a music copyright license request, or other license request, in particular embodiments the system is configured to take the request and related data and store it in a database associated with a computer server running the interface. The database may also include access to a separate or incorporated database including the music assets listed in the interfaces and the copyright owner preferences and license criteria associated with each music asset and each music copyright license associated with each asset. Once the request is submitted into the system, the database is updated with data indicating the request and the copyright owner's interface is updated with the updated status of the request. In the case of a music arrangement permission request, the music arranger indicated by the user is notified of the request and the music arranger's interface is updated with the status of the request and the steps that need to be taken to complete approval of the license.
[0035] Any of the parties associated with the licensing process has an option to select notification preferences. For example, the party may elect to receive notifications by email or text message or through the interface, or by any or all of the above.
[0036] In the case of a music arrangement license, the arranger is notified that a work for hire agreement is needed. The arranger may then log in to the arranger's interface and see that the license being issued is dependent upon the work for hire agreement being signed. The arranger interface is configured with an icon that, when clicked on, automatically generates, using an agreement generator running in association with the system, a work for hire agreement automatically formatted by the system to include the appropriate copyright and ownership information for the music assets requested and the information for the music organization the license relates to and the arranger who will be doing the arrangement. The system may be configured to accept an electronic signature by the arranger, or for the arranger to print and scan in the work for hire agreement to upload to the system. Either way, when the signature is complete, the system updates the records associated with this particular license agreement and indicates that the work for hire agreement is completed.
[0037] Thus, if depending upon the license requested, there is other paperwork that is needed for that particular license, the parties who need to execute agreements may be contacted directly to interact with the system to complete the needed agreements or take additional steps needed to complete the license requirements. Other parties associated with the particular request(s), e.g. the publisher(s), the director, the arranger or even individual performers in particular situations, may be notified automatically by email or by some other electronic or other way, with each request, on a daily basis, on a weekly or monthly basis, or only receive updates through their interface to the system depending upon preferences set in their respective interfaces.
[0038] The user's interface, whether they be any of the parties associated with a particular request, includes a list of license request relevant to their role in the licensing process. The list of licensing requests, whether it be for custom arrangements or others, includes a request number, submission date and identifier, identification of the music rights to which the request relates, a status section including a checklist of each paperwork or status change required for each step of the approval process. For example, for custom arrangement licensing, the work for hire agreement needs to be signed by the arranger, the song(s) need to be approved for the custom arrangement by the publisher, licensing fees need to be paid and a copy of the music arrangement needs to be uploaded to the system for the publisher. FIG. 5 illustrates a non-limiting example of an exemplary listing for a single song. A listing of actions currently required by the user/account holder who is reviewing the display - the director and arranger and publisher will each have different actions required at different times to complete a license request - an identification of the arranger for the particular arrangement (in the case of a custom music arrangement license request), and a notes section where the different related parties can associate notes with the request for all parties to review is also included. Like the pre-approved request listing discussed in relation to FIG. 3, each item to be completed in the list includes a color coded symbol to indicate whether it is completed. For example, a green check mark for completed or a red exclamation point for uncompleted. Furthermore, each license within the list may also be color coded to know the status of its completion toward approval by the copyright owner - green for approved, yellow for pending publisher Response, and red for denied as illustrated in FIG. 5. Recall that some copyright license requests are pre-approved (green), some need approval by the copyright owner (yellow), and some are already known to be extremely difficult or impossible to obtain permission to use (red). [0039] When any change is made in the system, each party involved in the process for that particular license request (director, arranger, publisher, performer, etc.) is notified. For example, when a director requests a license or licenses, the associated arranger(s) as well as the related publisher(s) are each notified and a status update is posted in their respective user interfaces. As described above, the work for hire agreements as required by each publisher are automatically generated to be signed by the arranger. For each particular license type and music asset to be licensed, and copyright owner particularities, there is a checklist to be completed to enable the license to be issued to the music organization. The checklist illustrated in FIG. 5 is especially useful to the license requestor, in that he is able to track the progress of the request, and is notified every step of the way as progress is made by the publishers, or if further action is needed on his part or that of his organization. For a music arrangement license request, the last step in the process is for the arranger to upload the actual music arrangement license to the system. Then the status of the request is changed to approved and a music license number can be issued. In that way, for each license issued, then the publisher is able to download the approved music arrangement and can watch for its use in the market.
[0040] If a requested song is denied approval by the publisher(s) representing that song, then in particular embodiments a licensee has the ability to request a substitute song for approval, and again may select from the list of pre-approved songs, songs needing approval, or those songs that are not likely to become approved.
AUTOMATED PUBLISHER LICENSE REQUEST APPROVAL SYSTEM
[0041] The interface for each copyright owner/publisher, or an administrator for the publisher (collectively "owner" or "publisher"), allows the publisher to review each music asset and pre-approve particular licensing uses and pricing. For example, the publisher can pre- approve songs to indicate they are available for custom arrangements, or mark them not available or "need request" if the particular publisher wants to approve each request individually. The publisher can also indicate through the publisher interface additional conditions of performance or use for the asset as restrictions on the license. When special restrictions are imposed by the publishers, specific acknowledgment is required by at least one of the other parties associated with the creation or performance of the music under the license. For example, in the case of a custom music arrangement, both the director and arranger would need to specifically acknowledge the restrictions made by those publishers. Those specific acknowledgments are automatically generated by the system as part of the process for issuing the license through the checklist illustrated with FIG. 5.
[0042] Once a request is made for approval of a song that was not pre-approved by the publisher, the system automatically seeks out all publishers of that work, and notifies those publishers that a request has been made. The publishers then have the option, through their interface relating to the particular license requested, to approve for the particular requested use, approve with restrictions, deny, or pre-approve for this and future uses. FIG. 6 illustrates a non- limiting example of this publisher interface as applied to a custom music arrangement licensing system.
[0043] Once any of the above described changes are made, the requestor interface is immediately updated, and the requestor is is notified of the changes made. The requestor may then take action through the user interface to change music rights requested if a request is denied, substitute songs if only part of a request is denied, make payment on a license request that is approved, and download the sheet music that has been provided to the publishers.
ADDITIONAL PUBLISHER LICENSE CONTROL SYSTEM
[0044] One frustration by many copyright licensing organizations is that because there are often many separate copyright owners, and many different organizations representing those rights, allocation of ownership and rights to certain music assets are either not known, or are published incorrectly altogether. This is particularly a problem when a music organization desires to license rights, or even when co-owners desire to pay other co-owners a share of revenue from use of the copyright. FIG. 7 a screen of a copyright owner interface that shows the ownership share of the particular copyright owner in a variety of music assets. The copyright owner interface allows the owner/publisher to verify ownership percentages of songs, and to record pro-rata ownership allocations to assist in accurate payments when licenses are issued for the respective music assets. Where an owner believes that its recorded or credited ownership share is incorrect, the user interface allows the owner to dispute the ownership percentage. A system administrator then has the ability to research and verify the correct ownership
percentages, and then those ownership amounts can be corrected so that each owner is compensated in accordance with its true ownership percentage. Over time the site database should become an extremely accurate record of music copyright ownership rights.
[0045] A screen of an owner interface illustrated in FIG. 8 allows an owner to place limitations on the licenses being approved to licensees such as the licensee usage duration or term, as well as limitations on the proper uses of that song or license, for example that a certain song cannot be played in a medley with other specified songs or artists.
[0046] An owner interface allows the flexibility to charge varying license prices based on several factors such as use of composition, type of performing group, size of performing group, and other factors. This allows the owner to automate its pricing models based on these programmable factors allowing for price uniformity among similar music performance organization types, groups, and sizes, or for particular uses such as Internet, television, video games or movies. It also allows the publisher to allow price-breaks for smaller organizations or groups with smaller budgets.
AUTOMATED PUBLISHER PAYMENT TRACKING SYSTEM
[0047] FIG. 9 illustrates a non-limiting example of a payment tracking interface for an automated copyright rights licensing system. Each owner/publisher interface includes a similar screen specific to that particular publisher for music assets and/or license types associated with that publisher. The payment tracking interface automatically updates through the processor associated with the database to update with new orders that are made, automatically allocating pro-rata payments due to all publishers who have ownership rights in the licenses that are issued or sales that are made. By immediately and automatically updating the publisher interface with specific licensing revenue for each music asset on a real-time basis, publishers have a transparent view into real revenues. Existing manual systems can take years to get payments to music publishers for similar license revenue.
[0048] Unless a particular contract prohibits it, in order to use a copyright license, only one of the copyright owners needs to approve the license. In many cases in the past, this resulted in only the approving owner being paid for the licenses, even though many other owners may have had a share in the ownership rights of the particular music asset being licensed. Part of the difficulty of making the appropriate payments is the difficulty in accurately identifying the owners, and part was in getting approval by all of the owners to a particular licensing plan and the cost of tracking down the co-owners to make payment (the cost of tracking them down often outweighing the revenue they were to be paid). Through the use of an automated music rights licensing and royalty tracking system, all copyright owners recorded as having ownership rights are automatically, and properly compensated, even where a particular owner was not specifically available to approve a particular license or use of a music asset.
LICENSEE ONLINE LICENSE MANAGEMENT SYSTEM
[0049] For a custom music arrangement licensing system, once all songs in a compilation have been approved, all acknowledgements given, all work for hire agreements have been signed and the license fee has been paid, the arranger uploads the custom arrangement digital sheet music into the database to associate with the license to finalize the license and allow the license to issue. In particular embodiments of the system, it may be configured to take the custom arrangement sheet music uploaded and automatically digitally imprint the sheet music with up to date and complete copyright information and the terms of the license printed on each sheet of the arrangement. Digital imprinting of documents is known in the art and there are existing programs that can accomplish this task. However, by imprinting the custom music arrangement digital sheet music with current copyright information as well as the terms of the license, including the music organization to which the license is issued and the date the license expires, copyright infringement is significantly reduced and the arrangers, the music organizations and the copyright owners are each more free to commercially exploit the licenses they have issued and received for the greatest collective revenue for everyone. In particular embodiments, the arranger may also upload a fully licensed accompaniment track of the music, or the music may be configured for display in a system that will generate the music shown in the sheet music as an audio sound to assist in practice of the music.
[0050] Particular embodiments of the system may also be configured to generate a custom arrangement sheet music is a license certificate showing the term and restrictions of the license agreement between the publisher(s) and licensee. This certificate may be stored online and can be accessed, viewed, and printed by the licensee at any time. Further, publishers can access a verification system to verify that a particular performing organization has a valid license for a particular composition. These systems allow both licensees, publishers, even competition organizations and others in the public to verify that valid copyright licensing is in place for any performances, arrangements or other music asset usage that takes place if they have the music organization name and license number.
COMPLIANCE WITH INTERNATIONAL COPYRIGHT LAWS
[0051] Particular embodiments of an automated music rights licensing and royalty tracking system take into account the different copyright laws of different countries. For example, the United States operates under what is called 100% licensing, which means that when a license is requested, the approval of just one of the publishers that has ownership rights is required in order for the license to be granted. Another example is the European Union, where permission of every copyright owner is required to issue a license. In a country under this law, the system is automatically configured to notify all of the publishers holding ownership rights when a license request is made, and approval of all rights-holding publishers is sought by an automated music rights licensing and royalty tracking system.
DISTRIBUTION NETWORK AND MONETIZATION SYSTEM
[0052] FIG. 10 illustrates a non- limiting example of an automated music rights licensing and royalty tracking system embodied as a distribution network for client recordings and films, which is also tracked through the same database system and revenue and sales reports for publishers and for music organizations.
[0053] Each music organization may have its own affinity-based storefront through which music recordings are sold as downloads. For sales, as tracked through the system, all mechanical and synchronization licensing for music recordings is paid by a company from sales proceeds. There is no need for the customer to go through the process of tracking down all publishers, nor is there a need for customers to pay for their licenses up front (which is the prior art requirement for producing CDs). An automated music rights licensing and royalty tracking system integrates music recording sales with the payment, tracking, and acquisition of the licensing required to enable the sales. In this way publishers can be assured that all copyright rights have been secured and the recordings being sold are in compliance with copyright laws in a simple, efficient manner.
[0054] The system may also be configured to automatically register the master recordings of the music performances with other distribution channels such as YouTube, The Orchard, iTunes, Google Play, Amazon, Spotify, Netflix, etc., as part of uploading a recording if the music organization's administrator selects the particular distribution channel for distribution.
[0055] FIG 11. illustrates a non-limiting example of an automated music rights licensing and royalty tracking system configured for licensing the master recordings of the music performances to the entertainment industry (TV, commercials, Internet, Video Games, movies, etc.), if the music organization elects to have the master recordings made available for consideration by the entertainment industry.
[0056] In an automated music rights licensing and royalty tracking system for master recordings to license them to the entertainment industry, music and video supervisors for films, television shows, and advertising agencies are able to access the master recordings through an automated music rights licensing and royalty tracking system, search for recordings, select recordings on the basis of copyright status (public domain, copyright protected compositions that require additional licenses, or compositions where a particular company is in control of the copyright on the underlying composition. Each master recording indicates in association with the recording whether the master recording is pre-cleared for use in entertainment, whether the master recording and synchronization licenses are pre-cleared, or whether a license is required (similar to other automated music rights licensing and royalty tracking system aspects discussed above). As mentioned earlier, master recordings can be automatically included in the searchable lists associated with this interface by the music organization that made the recording through the music organization's upload interface.
[0057] For an end user, there is great advantage in searching licenses known to be pre- approved so that they can be obtained instantly. The conventional approach to obtaining custom music arrangement licenses involved a substantial delay due to the requirements of processing the work for hire agreements between all rights holders and the arranger, the contracts for the license between the rights holders and the arranger, negotiating terms of licenses between various publishers and requestors, tracking down multiple rights holders for the music rights to obtain the rights from each publisher, and the processing of the inbound payment and the payouts to the rights holders.
[0058] As used herein, the terms "component," "system" and the like are intended to refer to a computer-related entity, either hardware, a combination of hardware and software, software, or software in execution. For example, a component may be, but is not limited to being, a process running on a processor, a processor, an object, an instance, an executable, a thread of execution, a program, and/or a computer. By way of illustration, both an application running on a computer and the computer can be a component. One or more components may reside within a process and/or thread of execution and a component may be localized on one computer and/or distributed between two or more computers.
[0059] The word "exemplary," "example" or various forms thereof 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 preferred or advantageous over other aspects or designs. Furthermore, examples are provided solely for purposes of clarity and understanding and are not meant to limit or restrict the claimed subject matter or relevant portions of this disclosure in any manner. It is to be appreciated that a myriad of additional or alternate examples of varying scope could have been presented, but have been omitted for purposes of brevity.
[0060] With reference to FIG. 3, an exemplary environment 10 for implementing various aspects disclosed herein includes a computer 12 (e.g., desktop, laptop, server, hand held processing device, cellular phone device, programmable consumer or industrial electronics, and the like). The computer 12 includes a processing unit 14, a system memory 16, and a system bus. The system bus couples system components including, but not limited to, the system memory 16 to the processing unit 14. The processing unit 14 can be any of various available
microprocessors. It is to be appreciated that dual microprocessors, multi-core and other multiprocessor architectures can be employed as the processing unit 14.
[0061] The system memory 16 includes volatile and nonvolatile memory. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer 12, such as during start-up, is stored in nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM) in some cases. Volatile memory includes random access memory (RAM), which can act as external cache memory to facilitate processing.
[0062] Computer 12 may also include removable/non-removable, volatile/non-volatile computer storage media. FIG. 3 illustrates, for example, mass storage 24. Mass storage 24 includes, but is not limited to, devices like a magnetic or optical disk drive, floppy disk drive, flash memory, Internet cloud memory, or memory stick. In addition, mass storage 24 can include storage media separately or in combination with other storage media.
[0063] FIG. 3 provides software application(s) 28 that act as an intermediary between users and/or other computers and the basic computer resources described in suitable operating environment 10. Such software application(s) 28 include one or both of system and application software. System software can include an operating system, which can be stored on mass storage 24 that acts to control and allocate resources of the computer system 12. Application software takes advantage of the management of resources by system software through program modules and data stored on either or both of system memory 16 and mass storage 24. Database data may be stored in system memory 16, mass storage 24, or some other storage associated with the computer 12.
[0064] The computer 12 also includes one or more interface components 26 that are communicatively coupled to the bus 18 and facilitate interaction with the computer 12. By way of example, the interface component 26 can be a port (e.g., serial, parallel, PCMCIA, USB, Fire Wire, and the like) or an interface card (e.g., sound, video, network, and the like) or the like. The interface component 26 can receive input and provide output (wired or wirelessly). For instance, input can be received from devices including but not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, camera, other computer and the like. Output can also be supplied by the computer 12 to output device(s) via interface component 26. Output devices can include displays (e.g., CRT, LCD, plasma, projection, and the like), speakers, printers and other computers, among other things.
[0065] FIG. 4 is a schematic block diagram of a sample-computing environment 30 with which the subject innovation can interact. The system 30 includes one or more client(s) 32, for example associated with a user's account. The client(s) 32 can be hardware and/or software (e.g., threads, processes, computing devices). The system 30 also includes one or more server(s) 34. Thus, system 30 can correspond to a two-tier client server model or a multi-tier model (e.g., client, middle tier server, data server), amongst other models. The server(s) 34 can also be hardware and/or software (e.g., threads, processes, computing devices). The servers 34 can house threads to perform transformations by employing the aspects of the subject innovation, for example. One possible communication between a client 32 and a server 34 may be in the form of a data packet transmitted between two or more computer processes while transmitting data from an account interface displaying on an account owner's computing device and an interface processor, or between an interface processor and an account owner's phone and/or data service carrier or a phone number and/or registration number registry, or between a phone and/or data service carrier and a phone number and/or registration number registry. A communication framework 38 exists between the one or more client(s) 32 and the one or more server(s) to facilitate meaningful data transfer and communication.
[0066] Furthermore, all or portions of the subject innovation may be implemented as a method, apparatus or article of manufacture using standard programming and/or engineering techniques to produce software, firmware, hardware, or any combination thereof to control a computer to implement the disclosed innovation. The term "system" as used herein is intended to encompass a computer program accessible from any computer-readable device or media. For example, computer readable media can include but are not limited to magnetic storage devices (e.g., hard disk, floppy disk, magnetic strips . . . ), optical disks (e.g., compact disk (CD), digital versatile disk (DVD) . . . ), smart cards, and flash memory devices (e.g., card, stick, key drive . . . ). Additionally it should be appreciated that a carrier wave can be employed to carry computer- readable electronic data such as those used in transmitting and receiving electronic mail or in accessing a network such as the Internet or a local area network (LAN). Of course, those skilled in the art will recognize many modifications may be made to this configuration without departing from the scope or spirit of the claimed subject matter.
[0067] In order to provide a context for the various aspects of the disclosed subject matter, the following discussion is intended to provide a brief, general description of a suitable environment in which the various aspects of the disclosed subject matter may be implemented. While the subject matter has been described above in the general context of computer-executable instructions of a program that runs on one or more computers, those skilled in the art will recognize that the subject innovation also may be implemented in combination with other program modules. Generally, program modules include routines, programs, components, data structures, etc. that perform particular tasks and/or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the systems/methods may be practiced with other computer system configurations, including single-processor, multiprocessor or multi-core processor computer systems, mini-computing devices, mainframe computers, as well as personal computers, hand-held computing devices (e.g., personal digital assistant (PDA), phone, tablet, watch . . . ), microprocessor-based or programmable consumer or industrial electronics, and the like. The illustrated aspects may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. However, some, if not all aspects of the described subject matter can be practiced on stand-alone computers. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
[0068] An exemplary environment for implementing various aspects disclosed herein includes a computer (e.g., desktop, laptop, server, hand held processing device, tablet, cellular phone device, programmable consumer or industrial electronics, and the like). The computer includes a processing unit, a system memory, and a system bus. The system bus couples system components including, but not limited to, the system memory to the processing unit. The processing unit can be any of various available microprocessors. It is to be appreciated that dual microprocessors, multi-core and other multiprocessor architectures can be employed as the processing unit.
[0069] The system may also be implemented on an Internet accessible server to enable web-based access to the interfaces, screens and system by people all over the world. Those of ordinary skill in the art are familiar with creation and operation of Internet accessible server implementations and would readily be able to program such a system from the present disclosure.
[0070] The system memory includes volatile and nonvolatile memory. The basic input/output system (BIOS), containing the basic routines to transfer information between elements within the computer, such as during start-up, is stored in nonvolatile memory. By way of illustration, and not limitation, nonvolatile memory can include read only memory (ROM) in some cases. Volatile memory includes random access memory (RAM), which can act as external cache memory to facilitate processing.
[0071] The computer may also include removable/non-removable, volatile/non-volatile computer storage media, for example, mass storage. Mass storage includes, but is not limited to, devices like a magnetic or optical disk drive, floppy disk drive, flash memory, Internet cloud memory, or memory stick. In addition, mass storage can include storage media separately or in combination with other storage media.
[0072] Software application(s) may act as an intermediary between users and/or other computers and the basic computer resources described in suitable operating environment. Such software application(s) include one or both of system and application software. System software can include an operating system, which can be stored on mass storage, that acts to control and allocate resources of the computer system. Application software takes advantage of the management of resources by system software through program modules and data stored on either or both of system memory and mass storage. Database data may be stored in system memory, mass storage, or some other storage associated with the computer.
[0073] The computer also includes one or more interface components that are
communicatively coupled to the bus and facilitate interaction with the computer. By way of example, the interface component can be a port (e.g., serial, parallel, PCMCIA, USB, Fire Wire, and the like) or an interface card (e.g., sound, video, network, and the like) or the like. The interface component can receive input and provide output (wired or wirelessly). For instance, input can be received from devices including but not limited to, a pointing device such as a mouse, trackball, stylus, touch pad, keyboard, microphone, joystick, game pad, satellite dish, scanner, camera, other computer and the like. Output can also be supplied by the computer to output device(s) via interface component. Output devices can include displays (e.g., CRT, LCD, plasma, projection, and the like), speakers, printers and other computers, among other things.
[0074] The system may include one or more client(s), for example associated with an account owner's account or tracking devices. The client(s) can be hardware and/or software (e.g., threads, processes, computing devices). The system also includes one or more server(s). Thus, system can correspond to a two-tier client server model or a multi-tier model (e.g., client, middle tier server, data server), amongst other models. The server(s) can also be hardware and/or software (e.g., threads, processes, computing devices). The servers can house threads to perform transformations by employing the aspects of the subject innovation, for example. One possible communication between a client and a server may be in the form of a data packet transmitted between two or more computer processes while transmitting data from an account interface displaying on an account owner's computing device and an interface processor, or between an interface processor and an account owner's phone and/or data service carrier. A communication framework exists between the one or more client(s) and the one or more server(s) to facilitate meaningful data transfer and communication.
[0075] In places where the description above refers to particular implementations of asset tracking systems and techniques, it should be readily apparent that a number of modifications may be made without departing from the spirit thereof and that these implementations may be applied to other to asset tracking system technologies as well. Routing of communication connections between various communications devices and tracking devices may be done similar to the examples provided above relating to a cellular phone or other communications network. Accordingly, the disclosed subject matter is intended to embrace all such alterations,
modifications and variations that fall within the spirit and scope of the appended claims.
Furthermore, to the extent that the terms "includes," "contains," "has," "having" or variations in form thereof are used in either the detailed description or in any claims now included or in the future added, such terms are intended to be inclusive in a manner similar to the term
"comprising" as "comprising" is interpreted when employed as a transitional word in a claim.
[0076] It will be understood that implementations are not limited to the specific components disclosed herein, as virtually any components consistent with the intended operation of a method and/or system implementation for an automated music rights licensing and royalty tracking system may be utilized. Accordingly, for example, although particular automated music rights licensing and royalty tracking system may be disclosed, such components may comprise any shape, size, style, type, model, version, class, grade and/or the like consistent with the intended operation of a method and/or system implementation for an automated music rights licensing and royalty tracking system may be used.
[0077] In places where the description above refers to particular implementations of an automated music rights licensing and royalty tracking system, it should be readily apparent that a number of modifications may be made without departing from the spirit thereof and that these implementations may be applied to other automated music rights licensing and royalty tracking systems. The accompanying claims are intended to cover such modifications as would fall within the true spirit and scope of the disclosure set forth in this document. The presently disclosed implementations are, therefore, to be considered in all respects as illustrative and not restrictive, the scope of the disclosure being indicated by the appended claims rather than the foregoing description. All changes that come within the meaning of and range of equivalency of the claims are intended to be embraced therein.

Claims

1. A music rights license request system comprising:
a processor running system software, associated with at least one music rights information
database, and comprising a public user interface comprising:
a music rights license request interface configured to receive a music rights license
request from a public user through the public user interface for a music rights license relating to at least one specifically identified music asset, and notify the public user of at least one change in a status of the music rights license request; a copyright owner interface configured to notify at least one music publisher of the
specifically identified music asset when the music rights license request is received and to receive input from the at least one music publisher to at least one of approve, deny, approve with restrictions, and pre-approve at least one of:
the request from the public user for the music rights license; and future requests for music rights licenses relating to the at least one
specifically identified music asset; and
an agreement generator configured to generate at least one agreement between the at least one music publisher and at least one of the public user, a music organization associated with the public user, and a music arranger who will create a custom arrangement of the at least one specifically identified music asset.
2. The music rights license request system of claim 1, wherein the at least one music rights information database comprises information regarding at least one of music titles, music composers, music arrangers, music publishers, music owners, music instrumentation, music performers, stock music available and music ownership interests.
3. The music rights license request system of claim 1, wherein the music rights license request interface is further configured to receive input from the public user to indicate what type of music rights license is being requested, the type of music rights license comprising one of a music custom arrangement license, a music mechanical license, a master recording use license, and a music synchronization license.
4. The music rights license request system of claim 3, the music rights license request
module further configured to receive input from the user to indicate whether the music rights license relates to a medley comprising more than one specifically identified musical work.
5. The music rights license request system of claim 1 , wherein the music rights license
request is for a music custom arrangement license and the system is further configured to receive input from the public user to identify a music arranger for the at least one specifically identified music asset.
6. The music rights license request system of claim 5, wherein the agreement generator is further configured to generate a work for hire agreement between the music arranger for the at least one specifically identified music asset and the at least one music publisher relating to the at least one specifically identified music asset.
7. The music rights license request system of claim 6, wherein the work for hire agreement generated by the agreement generator is taken from specific contract language approved by the at least one music publisher and is different from specific contract language approved by at least one other music publisher.
8. The music rights license request system of claim 5, wherein the public user interface is adapted to a role of the public user and is at least one of a musical organization director and a music arranger.
9. The music rights license request system of claim 8, wherein the public user interface
comprises a checklist of work to be done to finalize the music rights license request that includes reminders specific to the role of the public user.
10. The music rights license request system of claim 1, wherein the music rights license
request module comprises a database search field configured to query the at least one music rights information database for at least one of a musical work title, a music performer, a music owner and a music composer for the at least one specifically identified musical work.
11. The music rights license request system of claim 10, wherein the music rights license request module comprises a new musical work submission option configured to receive at least a title of a new musical work not found in the at least one music rights information database by the public user's search, which new musical work submission option submits the title to an administrator for addition to the at least one music rights information database or matching with an appropriate record in the at least one music rights information database.
12. The music rights license request system of claim 1, further comprising a music publisher interface configured to provide the music publisher with at least one of an indication of the status of the music rights license request and a monetary report indicating the publisher's revenue relating to the at least one specifically identified musical work.
13. The music rights license request system of claim 1, further comprising a payment interface configured to notify the public user of a payment due after the publisher approves the music license request.
14. A musical license approval system comprising:
a computer interface, accessible through a computer accessing a central processor, where
publishers view requests for song licenses and those requests may be reviewed, accepted, denied, approved with restrictions, and pre-approved; and
wherein through the interface a publisher may limit the use of licenses for different songs based on the needs of artists holding copyright ownership.
15. The system of claim 14, further comprising an interface wherein a publisher may review a requested custom arrangement.
16. The system of claim 14, further comprising an interface for the limitation of the
license term of a granted license.
17. The system of claim 14, further comprising the ability of the publisher to vary license pricing based on factors not limited to the use of the composition, type of performing group, and size of performing group.
18. A musical license management system comprising:
a file management system configured to, using a processor, create and electronically store a valid license certificate for a custom arrangement for future reference by a licensee;
a checking system, associated with the file management system and processor, configured to verify that a license is valid for a particular composition to a particular performing organization; a delivery system, associated with the file management system and processor, configured to deliver at least one of custom arrangements and accompaniment tracks to licensees after such have been uploaded by the publisher;
wherein licensees and publishers verify the validity of licenses, upload and download custom arrangements, and sheet music.
19. The system of claim 11, further including printed copyright information and license term information on each sheet of the arrangement delivered by the publisher.
20. The system of claim 11, further comprising a payment tracking system comprising: an interface for viewing payments and tracking payments due to a given publisher;
a search function wherein specified companies can request a viewing of payments due or
received over specified date ranges;
wherein publishers representing artists with copyright ownership are able to track the revenue earned over specified periods of time and are able to better track licensing business.
PCT/US2015/030425 2014-05-12 2015-05-12 Combined music rights licensing and royalty tracking system and methods WO2015175566A1 (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US201414275789A 2014-05-12 2014-05-12
US14/275,789 2014-05-12
US201514644845A 2015-03-11 2015-03-11
US14/644,845 2015-03-11

Publications (1)

Publication Number Publication Date
WO2015175566A1 true WO2015175566A1 (en) 2015-11-19

Family

ID=54480564

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2015/030425 WO2015175566A1 (en) 2014-05-12 2015-05-12 Combined music rights licensing and royalty tracking system and methods

Country Status (1)

Country Link
WO (1) WO2015175566A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20190155997A1 (en) * 2017-11-17 2019-05-23 1969329 Ontario Inc. Content licensing platform, system, and method
US11204736B2 (en) 2014-09-23 2021-12-21 Zophonos Inc. Multi-frequency sensing method and apparatus using mobile-clusters
US11262976B2 (en) * 2014-09-23 2022-03-01 Zophonos Inc. Methods for collecting and managing public music performance royalties and royalty payouts
WO2023049908A1 (en) * 2021-09-24 2023-03-30 Artema Labs, Inc Systems and methods for transaction management in nft-directed environments
US11954147B1 (en) * 2018-05-10 2024-04-09 David Della Santa Methods, systems, and media for tracking content items

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940504A (en) * 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US6961714B1 (en) * 2000-02-13 2005-11-01 David Levine Method of quantifying royalty owner rights
US20080215494A1 (en) * 2006-12-13 2008-09-04 Ricall, Inc. Online music and other copyrighted work search and licensing system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940504A (en) * 1991-07-01 1999-08-17 Infologic Software, Inc. Licensing management system and method in which datagrams including an address of a licensee and indicative of use of a licensed product are sent from the licensee's site
US6961714B1 (en) * 2000-02-13 2005-11-01 David Levine Method of quantifying royalty owner rights
US20080215494A1 (en) * 2006-12-13 2008-09-04 Ricall, Inc. Online music and other copyrighted work search and licensing system

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11204736B2 (en) 2014-09-23 2021-12-21 Zophonos Inc. Multi-frequency sensing method and apparatus using mobile-clusters
US11262976B2 (en) * 2014-09-23 2022-03-01 Zophonos Inc. Methods for collecting and managing public music performance royalties and royalty payouts
US20190155997A1 (en) * 2017-11-17 2019-05-23 1969329 Ontario Inc. Content licensing platform, system, and method
US11954147B1 (en) * 2018-05-10 2024-04-09 David Della Santa Methods, systems, and media for tracking content items
WO2023049908A1 (en) * 2021-09-24 2023-03-30 Artema Labs, Inc Systems and methods for transaction management in nft-directed environments

Similar Documents

Publication Publication Date Title
US11500972B2 (en) Tokenized media content management
US11250111B2 (en) Tokenized media content management
US20230325890A1 (en) Self regulating transaction system and methods therefor
US20200143469A1 (en) Technological improvements to networked computer systems having particularized components that are specially programmed to unconventionally effectuate efficient blockchain storage
US7856414B2 (en) Assured archival and retrieval system for digital intellectual property
JP5746330B2 (en) Introducing, renting, and reselling digital items
US20160358161A1 (en) Systems and methods for an online music marketplace
US20100161499A1 (en) Centralized Rights Management System for Digital Media
US20120197785A1 (en) Apparatus and method for management of intellectual property rights
US20220366022A1 (en) Non-fungible token (nft) content identifier with split tracking
US20170243216A1 (en) Digital payment processing utilizing encrypted computer networking
US20220229883A1 (en) System and method for protecting, managing and monetizing creative works using blockchain
JP2007526583A (en) System and method for registering valuable items
WO2015175566A1 (en) Combined music rights licensing and royalty tracking system and methods
US11687628B2 (en) Non-fungible token (NFT) authenticity protocol with fraud deterrent
US20230222187A1 (en) Media composition using non-fungible token (nft) configurable pieces
Owen et al. How blockchain technology can monetize new music ventures: an examination of new business models
US20070282714A1 (en) System, method and computer program product for providing an e-commerce interface on a web page to facilitate e-commerce involving digital assets
JPWO2012014311A1 (en) Content sales promotion system and information processing method integrating digital rights management and affiliate
US20070268163A1 (en) System, method and computer program product for facilitating e-commerce involving digital assets
US20230419283A1 (en) Systems and Methods for Forming and Operating NFT Marketplace
Rennie et al. Blockchain and the Creative Industries: provocation paper
US20110054959A1 (en) System and method for a standards-based journalism marketplace
JP6730504B1 (en) Program and information processing method
US20070279262A1 (en) Automated right-holders registration system, method and computer program product for facilitating e-commerce involving digital assets

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 15792335

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 09.03.2017)

122 Ep: pct application non-entry in european phase

Ref document number: 15792335

Country of ref document: EP

Kind code of ref document: A1