METHODS AND SYSTEMS FOR IDENTIFYING MUSICAL COMPOSITIONS IN A SOUND RECORDING AND LICENSING THE SAME
Disclosed herein is a musical works administration service to digital music service providers (DSPs), to provide a streamlined approach for such DSPs to comply with copyright licensing, accounting, and reporting requirements. The service receives, from the DSP, information relating to sound recordings used by the DSP during a relevant time period. Using several matching techniques, the service identifies specific musical compositions embodied in each sound recording, and also determines corresponding publisher-share information. Subsequently, the service employs several mechanisms to attempt to obtain licenses for publisher-shares that are not already covered by preexisting client licenses. Based on the client's usage of such sound recordings and other related information, the service also performs accounting, reporting, and payment operations for the client. The service, in some instances, receives funds from the client and makes corresponding royalty payments (and makes accounting reports available) to the respective rights holders.
This application is a continuation of U.S. application Ser. No. 15/060,480, filed Mar. 3, 2016, and now pending, which is a continuation of U.S. application Ser. No. 12/764,897, filed Apr. 21, 2010 and now abandoned, which claims priority to U.S. Provisional Patent Application No. 61/171,302, entitled ACCOUNTING, PAYMENT, AND REPORTING SYSTEMS AND PROCESSES, filed Apr. 21, 2009, all of which are hereby incorporated by reference in their entirety.
This application hereby incorporates by reference in its entirety U.S. patent application Ser. No. 12/764,901, filed Apr. 21, 2010, entitled METHODS AND SYSTEMS FOR LICENSING SOUND RECORDINGS USED BY DIGITAL MUSIC SERVICE PROVIDERS.
FIELDThe techniques described in this application generally relate to the field of identifying musical compositions in sound recordings and licensing such compositions on behalf of online music stores.
BACKGROUNDBefore the advent of the Internet and the popularity of “online music,” users traditionally purchased music through physical media (e.g., tape records, audio CDs, etc.). However, more recently, with the advancements in Internet technology and availability of high-quality music renderings over the Internet, consumers prefer to obtain music directly from digital music service providers “DSPs” (e.g., Apple iTunes®, lala media, inc., Slacker®, Zune®, etc.). Some DSPs offer users the ability to download a copy of the actual music file on a permanent or “limited download” basis, while other music stores stream the music (without actually providing a file for downloading) for the user to listen to. The users typically pay such DSPs on a per-song or a per-period subscription basis, while some DSPs operate on an advertising-supported model.
The DSPs do not typically hold a “copyright interest” in the sound recordings (“recordings” or “tracks”) that they make available to their consumers, or in the musical compositions (“compositions” or “songs”) that may be embodied in those sound recordings. Instead, the DSPs must obtain copyright licenses to use (e.g., by reproducing and distributing) a particular sound recording and any musical composition(s) embodied in such sound recording, and, in exchange, compensate (e.g., in terms of royalty payments) one or more entities that hold a copyright interest in the particular sound recording and the underlying composition(s).
Music licensing in the United States is based on the protection that U.S. copyright law provides for such rights holders. The Copyright Act of the United States (title 17 of the U.S. Code) provides for copyright protection in “sound recordings.” The U.S. copyright office defines “sound recordings” as “works that result from the fixation of a series of musical, spoken, or other sounds, but not including the sounds accompanying a motion picture or other audiovisual work.” So, a “sound recording” is just that—a recording of sounds. Common examples include recordings of music, drama, or lectures. Sound recordings are typically owned and licensed by record companies or “labels”. A given sound recording may embody one or more compositions, or “musical works” (i.e., the notes and lyrics), which compositions have copyright protection under the Copyright Act that is separate from the copyright in any sound recording which may embody that composition. Each such composition may have one or more copyright owners or co-owners, which are typically music publishers, or simply “publishers”. Accordingly, a sound recording may include multiple “publisher-shares,” representing entities that have a copyright interest in at least a portion of at least one musical composition embodied in a given sound recording. In some instances, a “publishing administrator” works on behalf of such entities, which may include, for example, a music publisher, the composer(s) (i.e., the person(s) who wrote the music of the composition), the author(s) (i.e., the person(s) who wrote the lyrics), etc. In a typical example, the composer and the author share co-ownership of the actual copyright to the musical composition with the publisher, who represents the composition in business dealings.
In order to comply with the Copyright Act, a DSP would have to identify each rights holder associated with nearly every sound recording ever used, reproduced, or distributed by the DSP, and attempt to obtain licenses from (and make corresponding royalty payments to) such rights holders. Because record companies (as the typical owners of sound recordings) represent a limited group of concentrated copyright ownership and typically control 100% of the copyright in any given recording, DSPs are usually able to efficiently license from and account to record companies without assistance from third parties. In contrast, the ownership of musical compositions tends to be far less concentrated, and split ownership of individual songs is commonplace. As a result, DSPs often turn to third party service providers to obtain licenses from, and account to the various owners of those compositions.
Overall, the examples herein of some prior or related systems and their associated limitations are intended to be illustrative and not exclusive. Other limitations of existing or prior systems will become apparent to those of skill in the art upon reading the following Detailed Description.
SUMMARY OF THE DESCRIPTIONAt least one embodiment of the present invention discusses a technique for providing a “musical works administration service” to a DSP (a “client”), to enable the client to comply with various copyright requirements in connection with the use or distribution of licensed sound recordings. In one embodiment, the service receives client label metadata (“CLM”) from a client, wherein the CLM consists of identifying a sound recording. The service then performs a processing routine to integrate the received CLM into a normalized CLM database. Subsequent to integrating the CLM data, the service performs a matching operation to identify publishing rights-holder information associated with the sound recording identified by the received CLM and to enter the CLM as a “matched sound recording” entry in a pivot table. The service then performs a licensing operation to evaluate the extent to which the musical composition embodied in a matched sound recording is already licensed and to acquire new licenses for any remaining unlicensed publishing shares of such matched sound recording. In addition to the CLM data, the service receives other data for a relevant accounting period from the client, such as information about the number of uses of the sound recording during the period and the resulting revenue, and associates that information with the publishing information about the sound recording. The service then performs an accounting operation for the relevant accounting period to determine a royalty rate associated with the reported usage of the sound recording. The service then performs a reporting function to report license status to the client and to request royalty funds from the client for use of the matched sound recording during the applicable accounting period. Finally, the service performs a reporting operation to provide royalty statements to, and a payment operation to compensate, the relevant publishing rights-holders based on the client's use of the sound recording.
Other advantages and features will become apparent from the following description and claims. It should be understood that the description and specific examples are intended for purposes of illustration only and not intended to limit the scope of the present disclosure.
These and other objects, features and characteristics of the present invention will become more apparent to those skilled in the art from a study of the following detailed description in conjunction with the appended claims and drawings, all of which form a part of this specification. In the drawings:
The headings provided herein are for convenience only and do not necessarily affect the scope or meaning of the claimed invention.
In the drawings, the same reference numbers and any acronyms identify elements or acts with the same or similar structure or functionality for ease of understanding and convenience. To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the Figure number in which that element is first introduced (e.g., element 204 is first introduced and discussed with respect to
Various examples of the invention will now be described. The following description provides specific details for a thorough understanding and enabling description of these examples. One skilled in the relevant art will understand, however, that the invention may be practiced without many of these details. Likewise, one skilled in the relevant art will also understand that the invention can include many other obvious features not described in detail herein. Additionally, some well-known structures or functions may not be shown or described in detail below, so as to avoid unnecessarily obscuring the relevant description.
The terminology used below is to be interpreted in its broadest reasonable manner, even though it is being used in conjunction with a detailed description of certain specific examples of the invention. Indeed, certain terms may even be emphasized below; however, any terminology intended to be interpreted in any restricted manner will be overtly and specifically defined as such in this Detailed Description section.
While aspects of the invention, such as certain functions, are described as being performed exclusively on a single device, the invention can also be practiced in distributed environments where functions or modules are shared among disparate processing devices. The disparate processing devices are linked through a communications network, such as a Local Area Network (LAN), Wide Area Network (WAN), or the Internet. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Aspects of the invention may be stored or distributed on tangible computer-readable media, including magnetically or optically readable computer discs, hard-wired or preprogrammed chips (e.g., EEPROM semiconductor chips), nanotechnology memory, biological memory, or other data storage media. Alternatively, computer implemented instructions, data structures, screen displays, and other data related to the invention may be distributed over the Internet or over other networks (including wireless networks), on a propagated signal on a propagation medium (e.g., an electromagnetic wave(s), a sound wave, etc.) over a period of time. In some implementations, the data may be provided on any analog or digital network (packet switched, circuit switched, or other scheme).
As shown in
In some instances, the network 1140 is the Internet, allowing the phone 1108 (with, for example, WiFi capability) or the personal computer 1104 to access and retrieve multimedia data (e.g., digital streaming music, digital streaming videos, etc.) from music service providers (e.g., client 1112). In some instances, especially where the phone 1108 is used to access web content through the network 1140 (e.g., when a 3G or an LTE service of the phone 102 is used to connect to the network 1140), the network 1140 may be any type of cellular, IP-based or converged telecommunications network, including but not limited to Global System for Mobile Communications (GSM), Time Division Multiple Access (TDMA), Code Division Multiple Access (CDMA), Orthogonal Frequency Division Multiple Access (OFDM), General Packet Radio Service (GPRS), Enhanced Data GSM Environment (EDGE), Advanced Mobile Phone System (AMPS), Worldwide Interoperability for Microwave Access (WiMAX), Universal Mobile Telecommunications System (UMTS), Evolution-Data Optimized (EVDO), Long Term Evolution (LTE), Ultra Mobile Broadband (UMB), Voice over Internet Protocol (VoIP), Unlicensed Mobile Access (UMA), etc.
Other advantages and features will become apparent from the following description and claims. It should be understood that the description and specific examples are intended for purposes of illustration only and not intended to limit the scope of the present disclosure.
A user 1102 uses one of the personal computing devices (e.g., the phone 1108, the personal computer 1104, etc.) to access digital content (e.g., online streaming music) offered by the client 1112. In one example, the client 1112 is a digital music service provider that allows the user 1102 to select and play (and/or or download) sound recordings (or tracks) offered by the client 1112.
In one embodiment, the client 1112 maintains a database of information about the sound recordings in its catalog in the form of client label metadata (CLM) 1113. The tracks or sound recordings comprised in the client's music database 1114 (as identified, for example, through the CLM 1113) may be used or played by the client's users (e.g., music user 1102). As will be explained in detail with reference to
In an exemplary illustration, the music user 1102 utilizes an online interface (e.g., a website through which the user can select a particular sound recording for online streaming or downloading) operated by the client 1112. The client 1112 uses the interface to provide access to the sound recordings stored in the client's music data base 1114. In response to gaining access to the sound recordings, the music user 1102 may provide monetary compensation to the client 1114. The monetary compensation may be in one of several manners, as can be appreciated by a person of ordinary skill in the art. For example, the client 1112 may charge the music user 1102 a specific amount for every download or online-streaming request of each sound recording requested by the music user 1102. In other examples, the client 1112 may collect a subscription fee for the music user's unlimited access to the sound recordings for a specific period of time (e.g., weekly, monthly, yearly, etc.).
In most instances, as explained above, the client 1112 may not have a direct copyright ownership or interest in the sound recordings comprised (and offered to the music users 1102) in its music database 1114. Instead, such ownership interests are vested in one or more rights holders 1120. Examples of such rights holders 1120 include: (i) record companies, who typically own or control the copyrights in the sound recordings themselves; and (ii) music publishers, who typically own or control the copyrights in the musical compositions which may be embodied in those sound recordings. Other rights holders may include publishing catalog administrators, care/of entities or payee designees (as designated by, for example, the publishers and/or composers of the applicable musical composition, authors, composers, etc. As necessitated by Copyright Law provisions, the client 1112 is typically obligated to obtain licenses, for the use and distribution of the sound recordings and any musical compositions embodied in such sound recordings. For example, for the use or distribution of a given sound recording embodying a musical composition that comprises four publisher-shares, the client 1112 may be obligated to obtain (or identify a previously existing) license for each publisher-share and subsequently provide accounting and make royalty payments for each publisher-share.
A music works administration service 1160, offered by an administration server 1164, enables the client 1112 to adhere to such obligations. In one embodiment, the client 1112 transmits one or more CLM files to the administration server 1164 over the network 1140. The administration server 1164, as will be discussed in detail below, provides the musical works administration service 1160, which allows the client 1112 to, for example, obtain appropriate licenses, and to provide reporting and royalty payment to the rights holders 1120.
The receiving module 1172 is configured to receive, from the client 1112, CLM data and other client accounting data 2102 (as illustrated in
In some embodiments, the receiving module 1172 receives other types of client accounting data 2102 in addition to the CLM data, as is illustrated in
The CLM data 1113, as briefly discussed above, includes several identifiers relating to a particular sound recording. An exemplary illustration of such identifiers is provided in
Subsequent to receiving the CLM data 1113 and/or client accounting data 2102, the receiving module 1172 conveys such information to a CLM integration module 1174 of the licensing subsystem 1150.
Subsequent to the CLM integration operation, the CLM matching module 1176 operates on the CLM data 1113 stored in the CLM database 1190 to match the sound recording (as identified by the CLM data 1113) with composition and publisher information from a publishing information data structure (PIDS) 1194 associated with the administration server 1164. In one embodiment, the PIDS 1194 is as a database that stores, for example, composition, copyright, and publisher information associated with an enormous corpus of sound recordings. As will be explained in detail below, the CLM matching module 1176 matches the record of a particular sound recording identified in the received CLM 1113 to a particular record (storing, copyright information, publisher information, etc. for a given musical composition) in the PIDS 1194.
The CLM matching module 1176 performs one or more of the following processes to ensure that the sound recording identified in the CLM data 1113 is matched to a known record in the PIDS 1194: a primary (systemic) matching process that includes a phase 1 (syntax matching) operation and a phase 2 (extended matching) operation; and a secondary (manual) matching process.
In one embodiment, the CLM pivot data structure 1192 is a database comprising a unique pivot record for every successfully matched record in the CLM database 1190. Following a successful match, the CLM matching module 1176 includes one or more of the following fields into each such unique record: a CLM row ID (e.g., to identify a location of the CLM data 1113 in the CLM database 1190), a source song ID (e.g., identifying a corresponding known record in the PIDS 1194), a match confidence (e.g., indicating a level of confidence based on the results of the syntax search algorithms, etc.), a pivot ID (e.g., indicating a location of the unique record within the CLM pivot data structure 1192), etc.
If the CLM matching module 1176 is unable to match a record from the CLM database 1190 based on a systemic matching of the primary identifiers 2224, the CLM matching module 1176 performs a phase 2 (extended matching) operation of the systemic matching process. This operation is illustrated in
It is worthwhile to note that the extended matching phase is performed only if the primary matching phase does not yield a positive result. This is because use of the primary identifiers 2224 alone results in fewer processing cycles reducing search latency and minimizing cost.
In some instances, the CLM matching module 1176 stages the CLM data files to be matched in a CLM sandbox before performing the various systemic matching operations. Sandboxing the CLM database 1190 to be evaluated facilitates a unified index of unevaluated records. This enables, for example, (simultaneous) multiple processing instances of the systemic matching operation, where the primary matching process is executed multiple times in tandem to expedite processing.
At the end of the primary (systemic) matching process, the CLM matching module 1176 determines whether there are any CLM files that are yet to be matched to a record from the PIDS 1194. If the CLM matching module 1176 detects the presence of such files, it tags such files for submission to a secondary (manual) matching process.
The secondary matching is performed, for example, by a user using additional functionalities provided by the CLM matching module 1176. In one embodiment, the CLM matching module 1176 provides a “point and shoot” research interface. In one example, this interface provides a split window view, with a top half of the interface window containing a table listing the unmatched tracks from the secondary matching queue. A bottom half of the interface window contains a table listing potential composition matches for the track selected in the unmatched tracks table. The composition table automatically populates as selections are made in the unmatched tracks table.
If the user cannot identify a composition in the list provided, or there are no potential matches listed, a search feature can be manually utilized to search through the PIDS 1194 on a variety of query parameters that may lead to a matching composition being discovered. The user selects, for example, a search function, which opens an interface presenting the ability to search on title, artist, composer, data source, and other potential attributes. The user may then select an execute function, which executes the query and returns the results to the composition table in the bottom half of the “Point and Shoot” interface.
If the user can identify a composition in the composition table, he selects the composition in the table and then selects “Match.” A new pivot record is then created in the CLM Pivot Data Structure 1194 (with, in addition to other parameters, a match confidence ranking indicating the match was made via the manual match process).
If no record in the composition table matches the subject record in the the CLM database (1190) and no matching composition can be found via the search function, manual research must be performed to collect information (e.g., through external publishing information sources 3810 or secondary research processes 3304) to identify the underlying composition copyrights associated with such record in the CLM database (1190). The user may refer to, for example, industry web sites, industry books, physical phonorecord label copy, and in some cases direct communication via email and phone with the parties involved with the sound recording and/or music publishers to collect this information. When sufficient information is retrieved, the user stores the record to the PIDS 1194. With the new composition record automatically selected, the CLM matching module 1176 creates a pivot record in the CLM pivot data structure 1192.
In some instances, if the manual research process fails to yield enough information, the user will flag the record for later review by selecting, for example, a “First-Pass” function, which prompts for an amount of time in which to wait before presenting the record again for manual matching. For example, the user may specify a period of six months to allow for the release of the proper composition information (e.g., for newly released sound recordings), at which time the unmatched track will reappear in the secondary matching queue for the client 1112.
Ultimately, if an unmatched track continues to appear in the secondary matching queue for the client 1112 for an excessive time period (e.g., for a period of more than two years), the CLM matching module 1176 (or the user using a manual process) marks the unmatched track as “Unmatchable” (through, for example, the PIDS 1194), and the CLM entry is excluded from future manual match processing.
Also, in some instances, unmatched tracks that do not qualify as sound recordings from compositions, such as, for example, comedy routines, and other non-composition audio are also marked as unmatchable and excluded from future match processing.
Subsequent to the various matching operations, a licensing module 1178 of the administration server 1164 performs a suite of licensing operations, as will be discussed below. Broadly, the licensing module 1178 performs one or more of the following operations: (1) identification of existing client-licenses; (2) a CRO license request and acquisition process; and (3) an NOI license invocation process.
In the example shown in
As indicated above, the client may already have a licensing agreement with certain rights holders. If the existing client license structures 4130 indicate that any of the shares are already under a voluntarily negotiated license agreement, the licensing module 1178 marks such publisher-shares as “VOL,” meaning that such shares are covered by an existing voluntary licensing agreement. If the existing client license structures 4130 indicate that any of the shares are already under a license agreement through a collective rights organization (“CRO”), or through a compulsory statutory license invoked by a Notice of Intent to Obtain a Compulsory License (“NOI”), then such existing licenses are marked accordingly. In the example of
Subsequent to evaluating existing licenses, the licensing module 1178 proceeds to perform a license acquisition process for the publisher-shares that are not already covered under an existing licensing agreement. For this operation, the licensing module first looks at whether the client 1112 has an agreement with a collective rights organization (e.g., the Harry Fox Agency (“HFA”), the Canadian Musical Reproduction Rights Agency (“CMRRA”), etc.). If the client 1112 has such an agreement, the licensing module 1178 submits the unlicensed shares to the, collective rights organization license acquisition process.
In some instances, the licensing module 1178 places such publisher-shares in a CRO ready track table 4522. The licensing module 1178 then copies the CRO track data to a staging schema 4524 that includes, for example, the title of the sound recording for which the share is a part, a unique request ID, etc., according to specifications dictated by the applicable CRO. The licensing module 1178 then exports the staged records in a file format dictated by the CRO 4500. In some instances, the licensing module 1178 submits the records to the CRO 4500 using the network 1140 (e.g., by an FTP transfer, or by transmitting the record by email, etc.).
The CRO 4500 maintains a matching and licensing system which evaluates submitted license requests on a track level by identifying the underlying copyright shares for each underlying sound recording, and grants licenses for publisher-shares where CRO 4500 is able to identify publisher-shares held by its members, and is authorized to license such publisher-shares. If the CRO 4500 is unable to license a particular publisher-share, it returns a code to the licensing module 1178 indicating that the applicable share is not licensed. Subsequent to completion of the licensing process, the CRO 4500 returns a response file to the licensing module 1178. The licensing module 1178 receives, for example, a CRO response file, which indicates which of the shares submitted for CRO licensing have been licensed. Based on this information, the licensing module 1178 enters the newly granted CRO licenses within, for example, a CRO license response database 4530.
The licensing module 1178 then determines whether any of the remaining publisher-shares are still without a licensing agreement. This may be because the client 1112 does not have an agreement with a CRO or because the CRO was unable to grant a license for those publisher-shares. In such an event, the licensing module 1178 submits the remaining unlicensed publisher-shares to the NOI licensing mechanism.
The statutory compulsory mechanical license requirements are outlined in Section 115 of the Copyright Act and allow a client to reproduce and distribute a musical composition without obtaining permission from the copyright holders by serving an NOI on any one of them.
Once a NOI package 4628 is posted to a publishing administrator's web reporting interface 4630, the song shares within that NOI package 4628 are considered licensed, and will be included in the next license status report 5014 transmitted to the client. Alternatively, if mailed, and if after a period of time chosen by the client the NOI package 4628 is not returned to the service, the song shares within that NOI package 4628 are considered licensed, and will be included in the next license status report 5014 transmitted to the client. If a NOI packet 4628 is returned for any delivery failure, such as incorrect address, the NOI in question is considered invalid, and the client's license structure 4130 is updated to prevent any compositions associated with such NOI from being identified to the client as licensed or, if they have been previously included in a license status report 5014 transmitted to the client, to delete such compositions from the next license status report transmitted to the client 5014.
Subsequent to completion of the licensing operation, the goal is for the musical composition embodied in each sound recording associated with each CLM record received from the client 1112 to be completely licensed (i.e., a license has been established for each publisher-share corresponding to the sound recording identified by each record of the CLM).
Accounting and Reporting OperationsSubsequent to ensuring that the musical compositions embodied in the sound recordings associated with the CLM data 1113 received from the client 1112 have been completely licensed, an accounting module 1180 of the administrator server's 1164 accounting subsystem 1152 performs an accounting operation. In some instances, the accounting module 1180 communicates with the receiving module 1172 to receive the client accounting data 2102 transmitted by the client 1112. Using the client accounting data 2102, the accounting module 1180 retrieves data for a relevant accounting period for the licensed sound recordings. Using this information, and using the percentage-share information associated with each publisher-share, the accounting module 1180 computes total royalty payments the client 1112 needs to make to the identified rights holders.
A reporting module 1182 of the accounting subsystem 1152 performs a reporting operation to update the client with licensing and royalty related information. In one embodiment, the reporting module 1182 generates a report specifying, for each CLM record received from the client 1112, a license status report (indicating, for example, the extent to which each sound recording identified in the CLM data 1113 is licensed). Additionally, the reporting module 1182 may also prepare a report on the total royalties that are due from the client 1112 to the various rights holders for an accounting period. The reporting module 1182 may also request overall royalty funds from the client.
The accounting subsystem 1152 further includes a payment module 1184 to receive a royalty payment from the client 1112, and also to transfer royalty payments to the various rights-holders (as indicated by the accounting module 1180). Additionally, the reporting module 1182 may be further configured to prepare a report on the royalty payments and license usage information to the various rights holders.
The processor(s) 605 may include central processing units (CPUs) to control the overall operation of, for example, the host computer. In certain embodiments, the processor(s) 605 accomplish this by executing software or firmware stored in memory 610. The processor(s) 605 may be, or may include, one or more programmable general-purpose or special-purpose microprocessors, digital signal processors (DSPs), programmable controllers, application specific integrated circuits (ASICs), programmable logic devices (PLDs), or the like, or a combination of such devices.
The memory 610 is or includes the main memory of the computer system 600. The memory 610 represents any form of random access memory (RAM), read-only memory (ROM), flash memory (as discussed above), or the like, or a combination of such devices. In use, the memory 610 may contain, among other things, a set of machine instructions which, when executed by processor 605, causes the processor 605 to perform operations to implement embodiments of the present invention.
Also connected to the processor(s) 605 through the interconnect 625 is a network adapter 615. The network adapter 615 provides the computer system 600 with the ability to communicate with remote devices, such as the storage clients, and/or other storage servers, and may be, for example, an Ethernet adapter or Fiber Channel adapter.
Unless the context clearly requires otherwise, throughout the description and the claims, the words “comprise,” “comprising,” and the like are to be construed in an inclusive sense (i.e., to say, in the sense of “including, but not limited to”), as opposed to an exclusive or exhaustive sense. As used herein, the terms “connected,” “coupled,” or any variant thereof means any connection or coupling, either direct or indirect, between two or more elements. Such a coupling or connection between the elements can be physical, logical, or a combination thereof. Additionally, the words “herein,” “above,” “below,” and words of similar import, when used in this application, refer to this application as a whole and not to any particular portions of this application. Where the context permits, words in the above Detailed Description using the singular or plural number may also include the plural or singular number respectively. The word “or,” in reference to a list of two or more items, covers all of the following interpretations of the word: any of the items in the list, all of the items in the list, and any combination of the items in the list.
The above Detailed Description of examples of the invention is not intended to be exhaustive or to limit the invention to the precise form disclosed above. While specific examples for the invention are described above for illustrative purposes, various equivalent modifications are possible within the scope of the invention, as those skilled in the relevant art will recognize. While processes or blocks are presented in a given order in this application, alternative implementations may perform routines having steps performed in a different order, or employ systems having blocks in a different order. Some processes or blocks may be deleted, moved, added, subdivided, combined, and/or modified to provide alternative or sub-combinations. Also, while processes or blocks are at times shown as being performed in series, these processes or blocks may instead be performed or implemented in parallel, or may be performed at different times. Further any specific numbers noted herein are only examples. It is understood that alternative implementations may employ differing values or ranges.
The various illustrations and teachings provided herein can also be applied to systems other than the system described above. The elements and acts of the various examples described above can be combined to provide further implementations of the invention.
Any patents and applications and other references noted above, including any that may be listed in accompanying filing papers, are incorporated herein by reference. Aspects of the invention can be modified, if necessary, to employ the systems, functions, and concepts included in such references to provide further implementations of the invention.
These and other changes can be made to the invention in light of the above Detailed Description. While the above description describes certain examples of the invention, and describes the best mode contemplated, no matter how detailed the above appears in text, the invention can be practiced in many ways. Details of the system may vary considerably in its specific implementation, while still being encompassed by the invention disclosed herein. As noted above, particular terminology used when describing certain features or aspects of the invention should not be taken to imply that the terminology is being redefined herein to be restricted to any specific characteristics, features, or aspects of the invention with which that terminology is associated. In general, the terms used in the following claims should not be construed to limit the invention to the specific examples disclosed in the specification, unless the above Detailed Description section explicitly defines such terms. Accordingly, the actual scope of the invention encompasses not only the disclosed examples, but also all equivalent ways of practicing or implementing the invention under the claims.
While certain aspects of the invention are presented below in certain claim forms, the applicant contemplates the various aspects of the invention in any number of claim forms. For example, while only one aspect of the invention is recited as a means-plus-function claim under 35 U.S.C. § 112, sixth paragraph, other aspects may likewise be embodied as a means-plus-function claim, or in other forms, such as being embodied in a computer-readable medium. (Any claims intended to be treated under 35 U.S.C. § 112, ¶ 6 will begin with the words “means for.”) Accordingly, the applicant reserves the right to add additional claims after filing the application to pursue such additional claim forms for other aspects of the invention.
Claims
1. A method for providing a licensing service to an online music service provider, the method comprising:
- a) receiving from the online music service provider, at an administration server, a request for providing administration service for a first sound recording, and a first set of client label metadata (CLM) including track identifier information of the first sound recording;
- b) integrating the first CLM into a CLM database, comprising:
- b-1) normalizing the first CLM to a canonical format;
- b-2) attaching a client identifier to the normalized first CLM when the first CLM does not include the client identifier; and
- b-3) integrating the normalized first CLM with the client identifier into a CLM database (incorporated first CLM), wherein the incorporated first CLM comprises one or more primary identifiers and/or one or more extended identifiers; and
- c) matching the incorporated first CLM with a musical composition entry from a publishing information database (PID) comprising:
- c-1) comparing, by the administration server, one or more primary identifiers of the incorporated first CLM and the primary identifiers stored in the PID;
- c-2) when step c-1) identifies the musical composition entry from the PID corresponding to the first sound recording, a new entry is entered into a CLM pivot data structure comprising a unique pivot record for every successfully matched record in the CLM database, wherein the new entry comprises one or more fields selected from the group consisting of a first CLM row ID identifying a location of the first CLM data in the CLM database, a source song ID identifying the corresponding musical composition entry in the PIDs, a match confidence indicating a level of confidence based on the results of the comparison of step c-1), and a pivot ID indicating the unique record within the CLM pivot data structure; and
- c-3) when step c-1) fails to match a musical composition entry from the PID with the first sound recording, one or more of the extended identifiers are used to match against the musical composition entries in the PIDs, and a new entry is entered into the CLM pivot data structure as described in step c-2);
- d) identifying, by the administration server, based on the information stored in association with the musical composition entry of the PID corresponding to the first sound recording, one or more publisher-shares, wherein each publisher-share represents an entity holding a copyright interest in at least a portion of a musical composition embodied in the first sound recording;
- e) identifying, by the administration server, whether each of the one or more identified publisher-shares identified in step d) is covered under a preexisting license; and
- f) automatically executing, by the administration server, a licensing function to acquire a license for each publisher-share that is not covered under a preexisting license.
Type: Application
Filed: Dec 14, 2018
Publication Date: Nov 28, 2019
Inventors: Michael Shanley (Los Angeles, CA), Richard Revilla (Woodland Hills, CA), Roger Ging (Camarillo, CA), Ronald H. Gertz (Woodland Hills, CA), Miller L. Watkins, III (Los Angeles, CA), William B. Colitre, II (Topanga, CA)
Application Number: 16/220,602