WO2011086465A1 - Systèmes et procédés permettant une collaboration, une protection et/ou une promotion de musique en ligne - Google Patents

Systèmes et procédés permettant une collaboration, une protection et/ou une promotion de musique en ligne Download PDF

Info

Publication number
WO2011086465A1
WO2011086465A1 PCT/IB2011/000070 IB2011000070W WO2011086465A1 WO 2011086465 A1 WO2011086465 A1 WO 2011086465A1 IB 2011000070 W IB2011000070 W IB 2011000070W WO 2011086465 A1 WO2011086465 A1 WO 2011086465A1
Authority
WO
WIPO (PCT)
Prior art keywords
sketch
computer system
track
music
host computer
Prior art date
Application number
PCT/IB2011/000070
Other languages
English (en)
Inventor
Stephen Brett
Original Assignee
Stephen Brett
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 Stephen Brett filed Critical Stephen Brett
Publication of WO2011086465A1 publication Critical patent/WO2011086465A1/fr

Links

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/06Buying, selling or leasing transactions

Definitions

  • the present invention relates to an on-line network for musicians and more particularly, relates to systems and methods for on-line music collaboration, protection, and/or promotion.
  • a home computer may be used by musicians to record, edit, mix and master music similar to a recording studio.
  • the home computer facilitates music recording by an individual musician, effective collaboration with other musicians to create and record music together has often required musicians to be at the same location playing and recording together.
  • the creation of a musical work often involves the combination of unique and complimentary talents from different musicians.
  • conventional music collaborations the ability to locate and work with other musicians is limited geographically.
  • FIG. 1 is a diagrammatic view of a music collaboration, protection, and promotion network, consistent with an embodiment of the present invention.
  • FIG. 2 is a diagrammatic view of an on-line music collaboration, protection, and/or promotion system, consistent with an embodiment of the present invention.
  • FIG. 3 is a functional block diagram of a system for creating a music sketch and publishing a song, consistent with an embodiment of the present invention.
  • FlG. 4 is a functional block diagram of a system for collaborating on a music sketch, consistent with an embodiment of the present invention.
  • FIG. 5 is a functional block diagram of a system for generating, managing, and/or
  • FIG. 5A is a block flow diagram of one method of generating an electronic copyright certificate using digitally-signed time-stamping, consistent with an embodiment of the present invention.
  • FIG. 6 is a functional block diagram of a system for providing anti-piracy protection for a purchased song, consistent with an embodiment of the present invention.
  • FIG. 6A is a block flow diagram of one method of embedding anti-piracy information in a purchased song, consistent with an embodiment of the present invention.
  • FIGS. 7A and 7B are diagrammatic views of arrangements of web pages for providing on-line music collaboration, protection, and/or promotion, consistent with an embodiment of the present.
  • FIGS. 8 A and 8B are screen shots illustrating a music collaboration, protection and promotion system home page and a registered user home page, respectively, consistent with an embodiment of the present invention.
  • FIGS. 8C-8F are screen shots illustrating sketch pages, consistent with an embodiment pf the present invention.
  • FIGS. 8G-8J are screen shots illustrating musician pages, consistent with an embodiment. "
  • FIGS. 8K-8L are screen shots illustrating songs pages, consistent with an embodiment/
  • FIG. 8M is a screen shot illustrating a radio playlist generation page, consistent with an embodiment.
  • FIG. 8N is a screen shot illustrating a charts page, consistent with an embodiment.
  • FjGS. 80-8P are screen shots illustrating a member song page and a publish song page, consistent with an embodiment.
  • FIGS. 8Q-8R are screen shots illustrating a member sketch page and a create sketch page, consistent with an embodiment.
  • FIG. 8S is a screen shot illustrating a member collaborations page, consistent with an embodiment.
  • FIG. 8T is a screen shot illustrating a member sales page, consistent with an embodiment.
  • FIGS. 8U and 8V are screen shots illustrating a member copyright page and a create copyright page, consistent with an embodiment.
  • FIGS. 9A-9Y are screen shots illustrating web pages providing a method for on-line music collaboration by creating a music sketch, consistent with one embodiment of the present invention.
  • FIGS. 10A-10F are screen shots illustrating web pages providing a method for on- line music collaboration by enabling other musicians to collaborate on a music sketch, consistent with another embodiment of the present invention.
  • FIGS. 1 1 A-l II are screen shots illustrating web pages providing a method for generating an electronic copyright certificate, consistent with a further embodiment of the present invention.
  • FIGS. 12A-12E are screen shots illustrating web pages providing a method for verifying an electronic copyright certificate, consistent with another embodiment of the present invention.
  • On-line music collaboration may be enabled by allowing multiple musicians to create sketches and, to upload digital audio files for tracks associated with the sketches to form a musical work.
  • On-line music protection may be enabled by generating, managing, and/or verifying electronic copyright certificates for the musical work and/or for the tracks created by collaborating musicians for the musical work.
  • On-line promotion may be enabled by allowing finished musical works and/or music tracks to be played, downloaded, and/or purchased.
  • On-line music protection may also be enabled by embedding anti-piracy information identifying a purchaser in a purchased digital audio file for a musical work.
  • a “sketch” refers to a draft of a musical work and includes one or more components of the musical work.
  • a “track” refers to a component of a musical work and a “mix” or “mixdown” refers to a combination of tracks.
  • a “published song” refers to a completed musical work made available for download or purchase.
  • an on-line, computerized music collaboration, protection and promotion system 100 may be used to establish a network of users (e.g., musicians and music listeners) who access the system 100 over a computer network 102 such as the Internet.
  • the system 100 thus allows the musicians to collaborate over the computer network 102 to create musical works and to promote those musical works to music listeners while also protecting each individual contribution to the musical works.
  • the illustrated embodiment shows a music collaboration, protection and promotion system 100
  • embodiments of the present invention may include computerized systems that provide one or more of the collaboration, protection and promotion functions described herein.
  • the music collaboration, protection and promotion system 100 may be implemented using a combination of hardware and software.
  • the hardware may generally include a host computer system 110 and one or more data storage systems 112, 112a.
  • the software may include code 120 for providing the functionality of the system and may include data generated by and accessed by the system, such as user data 122, audio files 124, and copyright files 126. Users may access the functionality provided by the software code 120 and the data .122, 124, 126 over the network 102.
  • the software code 120 may be executed to interact with the users (e.g. by displaying web pages) and to perform the processes, procedures or functions that enable music collaboration, protection and promotion, as described in greater detail below.
  • the terms process, procedure, and function are generally used interchangeably to refer to one or more actions performed by software being executed by a computer system to achieve a result.
  • the software code 120 may be executed to access or generate the user data 122, to collaborate on generating music and to provide access to music stored as audio files 124, and to generate and manage copyright certificates stored as copyright files 126.
  • the host computer system 110 may be coupled to the network 102 and accessed by various user, computer systems 130, 150, 170, 190-192 coupled to the network 102, for example, by accessing a web site using a web browser.
  • the host computer system 110 may include one 'or more server computers such as a web server running a network operating system, such as Microsoft Windows XP Server tm , Novell Netware tm , or Redhat Linux tm .
  • th ⁇ host computer system 110 is shown as a single server unit, the host computer system 110 may include a combination of computers or computing components such as a blade server system.
  • the host computer system 110 may also execute a web server application, such as Microsoft IIS Novell Webserver tm , or Apache Webserver tm , that allows for HTTP (i.e., Hypertext Transfer Protocol) access to the host computer system 110 via the network 102.
  • a web server application such as Microsoft IIS Novell Webserver tm , or Apache Webserver tm , that allows for HTTP (i.e., Hypertext Transfer Protocol) access to the host computer system 110 via the network 102.
  • HTTP Hypertext Transfer Protocol
  • the music collaboration, protection and promotion system 100 may also use the Microsoft .NET tm Framework as the overall technology platform.
  • the data storage system 112 may be integrated with or coupled directly to the host computer system 110.
  • the host computer system 110 may also be coupled to a data storage system 1 12a accessible over the network 102 in addition to or instead of the data storage system 112.
  • the data storage system 112, 112a may include, for example, one or more hard disk drives, tape drives, optical drives, RAID arrays, random access memory (RAM) devices, and/or read-only memory (ROM) devices.
  • a relational database management system (not shown), such as Microsoft SQL Server, may be used to manage all or a portion of the stored data.
  • the music collaboration, protection and promotion software code 120 may reside on and may be executed, at least in part, by the host computer system 110.
  • instruction sets and/or subroutines of the software code 120 may be stored on a storage device or system coupled to or integrated in the host computer system 110 (e.g., a storage system 1 12). and may be executed using one or more processors (not shown) and one or more memory architectures (not shown) incorporated into the host computer system 110.
  • the users may access the music collaboration, protection and promotion system 100 using the computer systems 130, 150, 170, 190-192 that are connected to the network 102 and executing a client application 140, 160, 180 such as a web browser (e.g., Microsoft Internet Explorer®, Netscape Navigator®, Firefox®, or Google Chrome®) or a specialized interface.
  • the user computer systems may be the user's desktop or laptop PC or MAC® computer 13Q, 150, 170, 190 or may be a mobile computing device 191 or tablet computing device 192.
  • the client application 140, 160, 180 is a web browser
  • the music collaboration protection and promotion system 100 may be accessed by rendering web pages in the web browser.
  • the user may be presented with web pages that allow the user to enter information, " to request and manage collaborations, to generate and manage copyright certificates, and to play, download, and purchase songs, as described in greater detail below.
  • At least a portion of the music collaboration, protection and promotion software code 120 may also reside on and/or be executed by the user computer systems 130, 150, 170, 190. At least a portion of music collaboration, protection and promotion code 120, for example, may be executed on the user computer systems 130, 150, 170, 190 as an HTML document, an Active XTM control, a JavaTM Applet, JavaScriptTM functions, and/or an AdobeTM Flash player or other type of plug-in, as the user accesses the functions of the system 100.
  • All or a portion of the data 122, 124, 126 may also be stored on other storage devices, for example, coupled to the user computer systems 130, 150, 170, 190.
  • audio files 142, 162, 182 and copyright files 144, 164, 184 may be stored locally on storage devices
  • Some of the user computer systems 130, 150 accessing the music collaboration, protection arid promotion system 100 may be coupled to an audio interface 134, 154 capable of interfacing with musical instruments 136, 156, microphones 155, monitor speakers, headphones, and/or other audio or recording equipment to facilitate recording and transferring music track audio files to the user computer systems 130, 150.
  • audio interfaces include the CI Series of audio interfaces provided by Steinberg.
  • the musician computer systems 130, 150 may also include one or more digital audio workstation (DAW) software applications 141, 161 for recording, editing, mixing and/or mastering recorded music tracks. Examples of DAW software applications include the Cubase series of applications available from Steinberg.
  • DAW digital audio workstation
  • DAW software applications may also be accessible over the network 102, for example, by including an online mixer, online sequencer, waveform display, equalizer, or other such tools on the music collaboration web page.
  • the music collaboration, protection, and promotion code 120 may include DAW software applications.
  • Other user computer systems accessing the music collaboration, protection and promotion system 100 may include a DAW software application 181 for editing, mixing and/or mastering pre-recorded music tracks but without being coupled to an audio interface.
  • the audio tracks may be recorded using separate audio equipment, for example, and transferred to the computer system 170 for editing, mixing and/or mastering.
  • Other user computer systems e.g., laptop 190, mobile device 191, or tablet computer 192 accessing the music collaboration, protection and promotion system 100 may be configured only for playing, downloading, and/or purchasing music.
  • An administrator computer system 114 may be coupled to the network and used by an administrator to access and administer the music collaboration, protection and promotion system 100 through a client application 128 such as a web browser (e.g., Microsoft Internet Explorer®, Netscape Navigator®, Firefox®, or Google Chrome®) or a specialized interface.
  • the administrator' computer system 114 may be located at the same location as the music collaboration, protection and promotion system 100 or located remotely.
  • the promotion system 200 may include a host computer system 210 providing web server code 220, registration code 222, music collaboration code 224, music protection code 226, music promotion code 228, or any combination thereof.
  • the web server code 220 may be executed primarily on the host computer system 210 to provide web pages to the user computer system 202.
  • the registration code 222, music collaboration code 224, music protection code 226, music promotion code 228 may include code executed on the host computer system 210 to perform at least some of the processes, procedures and/or functions associated with member registrations, musician collaboration, music protection, and/or music promotion. All or a
  • the registration code 222, music collaboration code 224, music protection code 226, music promotion code 228 may also include code (e.g., web page code) executed on the user computer system 202.
  • the web page code may be written in various computer languages including, but not limited to, HTML, Dynamic HTML, Java, Javascript, PHP, other scripting languages.
  • Web server code 220 may include instructions executed by the host computer system 210 to provide a web server process that causes web pages to be sent to the user computer system 202 in response to an HTTP request.
  • the web pages generated and sent by the web server code 220 are displayed on the user computer system 202 to allow the user to access and interact with the music collaboration, protection and promotion system 200 by causing execution of the registration code 222, music collaboration code 224, music protection code 226, music promotion code 228.
  • Registration code 222 may include instructions executed by the host computer system 210 and/or the user computer 202 to perform processes, procedures and/or functions involved with managing user registrations.
  • the registration code 222 may provide one or more web pages that prompt the user to enter registration information (e.g., username, password, and profile information) and may perform registration functions such as receiving the registration information and establishing a user account.
  • the registration code 222 may also perform a log-in process by prompting the user to enter log-in information (e.g., username and password), verifying the log-in information, and enabling access to a user home page and registered user or member features of the system.
  • the registration code 222 may also perform a log-off process by disabling access to the user home page and to the registered user features of the system.
  • Musician collaboration code 224 may include instructions executed by the host computer system 210 and/or the user computer 202 to perform processes, procedures and/or functions that enable collaboration between musicians to create a musical work.
  • Musician collaboration code 224 may generate one or more web pages that allow musicians to create new sketches for collaboration, to modify sketches, to enable access to those sketches by potential collaborating musicians, to enable searching of sketches (e.g., by genre or talent required), and to identify and communicate with collaborating musicians.
  • Musician collaboration code 224 may also perform audio file download and upload functions to allow musicians to,,download and upload the tracks to be associated with the sketches and used in the collaboration.
  • Music protection code 226 may include instructions executed by the host computer system 210 and/or the user computer 202 to perform processes, procedures and/or functions that enable protection of music such as copyright protection and anti-piracy protection.
  • Music protection code 226 may generate one or more web pages that allow musicians to ' request generation, download, and/or verification of electronic copyright certificates.
  • Music protection code 226 may also perform the functions involved with generating the electronic copyright certificates from a digital audio file and copyright information provided by the user/creator.
  • Music protection code 226 may further perform the functions involved with storing and managing the electronic copyright certificates.
  • Music protection code 226 may also perform the functions involved with embedding anti-piracy information into songs when downloaded and/or purchased.
  • Music promotion code 228 may include instructions executed by the host computer system 210 and/or the user computer 202 to perform processes, procedures and/or functions that enable promotion of musical works, for example, by playing and/or making songs available for download and purchase.
  • Music promotion code 228 may generate one or more web pages that allow musicians to publish songs for download or purchase, that allow users to browse and listen to published songs, that allow users to search for songs and/or musicians, that provide rankings of musicians and/or songs (e.g., most viewed, most downloaded), and that allow users to initiate a purchase transaction to purchase a song.
  • Music promotion code 228 may also provide audio players capable of rendering audio files on the user's computer system 2020 to play individual songs or a playlist of songs.
  • Music promotion code 228 may also provide download functions to allow users to download songs.
  • Music promotion code 228 may further provide music share functions that allow users to share songs with others, for example, by email communication and/or by posting to a social networking website, such as Facebook®.
  • the music collaboration, protection and promotion system 200 may also include a data storage system 212 that stores data generated by and accessed by the code 220-228 being executed to perform the registration, collaboration, protection and promotion functions.
  • the data storage system 212 may store user data 230, electronic copyright certificate files 242, and/or digital audio files 244.
  • the user data 230 may include, for example, profile data 232, sketch data 234, published song data 236, song sales data 238 and/or promotion data 239.
  • Profile data 232 may include registered user or member information including, without limitation, the member's name, password, location, email address, payment details, payment credits, and account information (e.g., membership type, copyright credits allocated and remaining, managed copyright credits allocated and remaining, allocated and available storage space, number of songs and sketches, and anti-piracy credits allocated and remaining).
  • Profile data 232 may also include data identifying songs published by the member, sketches created by the member, collaborations made by the member, sales records for songs published by the member or with user collaboration, and copyright certificates created by the member.
  • the profile data 232 may further include data identifying sketches matching the; member's talents, musicians being followed by the member, other members following the member, recommendations for the member, and activities involving other musicians being followed by the member or sketches created or being collaborated on by the member.
  • the sketch data 234 may include, without limitation, sketch information, track information identifying tracks associated with the sketch, and mixes information for mixdown tracks associated with the sketch.
  • the sketch information may include, without limitation, a sketch title, a sketch creator, a sketch genre, a sketch creation date, beats per minute or other musical information, talent required, and names of collaborators.
  • the sketch information may further include a copyright indicator indicating whether or not a copyright certificate has been generated for any of the tracks associated with the sketch.
  • the track information may include, without limitation, track type, track name, name of uploading member, date added, comments, and a cue playback value.
  • Mixes information may include, without limitation, a version name, name of uploading member, date added, and comments.
  • the published song data 236 may include, without limitation, a song title, a creator name, a creation date, a genre, a purchase price, collaborator names, notes, a number of downloads, and a number of plays.
  • the published song data 236 may also include copyright information and an indication of anti-piracy protection for the song.
  • the sales data 238 may include sales records indicating songs sold, an amount of sales, a purchaser, sale dates, and sajes percentages attributed to collaborators.
  • the promotion data 239 may include, without limitation, information identifying featured musicians, songs, and sketches; most viewed musicians, songs and sketches; most downloaded musicians, songs and sketches; most commented songs and sketches; editor's picks for musicians, songs, and sketches; and most active musicians.
  • the electronic copyright certificate files 242 may include files including a representation (e.g., a digital fingerprint) of a digital work protected by copyright, a name of the creator of the work, and a time stamp providing evidence of the copyright date.
  • a representation e.g., a digital fingerprint
  • an electronic copyright certificate file may be generated by generating a digital fingerprint of a digital work file, time-stamping the digital fingerprint, and digitally ⁇ signing with an encrypted digital signature, for example, using the PKCS #7 standard.
  • Other formats may also be used to create a secure file providing evidence of a copyright in a particular digitally recorded work.
  • the digital audio files 244 may include files in an audio file format capable of producing audio signals when the audio data contained in the file is rendered by a suitable audio player application.
  • the audio file formats include, without limitation, WAV, AIFF, MP3, AAC, WMA, AU, and MIDI.
  • the illustrated embodiment of the music collaboration, protection and promotion system 200 includes the code 222, 224, 226, 228 for performing all of the member registration, music collaboration, music protection, and music promotion functions or processes
  • other embodiments of the system 200 may include code for performing only one or more of these functions in combination with the web server 220.
  • the code 222, 224, 226, 228 is illustrated as discrete elements, these elements may not necessarily be executed as separate, discrete processes, procedures, or functions within the music collaboration, protection and promotion system 200.
  • the music collaboration, protection and promotion system 200 may also include other code and other types of data to facilitate other processes, procedures, functions and features described herein.
  • the music collaboration, protection and promotion system 200 may include, for example, code that allows integration or linking with other online digital media (e.g., embedding YouTube® videos on song pages) and/or with online social networking web sites (e.g., Facebook®) to share and promote music creations and to network with other musicians and potential collaborators.
  • online digital media e.g., embedding YouTube® videos on song pages
  • online social networking web sites e.g., Facebook®
  • one system and method for on-line music collaboration involves creation of a music sketch.
  • a user 302 may interact with a user interface 320 (e.g., web pages) to invoke a create sketch process 324 that prompts the user via the user interface to provide sketch information 334 for the new sketch.
  • the create sketch process 324 stores the sketch information 334 such that the user (and others) may view the sketch information 334 via the user interface 320.
  • the user 302 may then interact with the user interface 320 to invoke a new track upload process 325 that prompts the user via the user interface 320 to provide new track information and to select a track audio file for upload.
  • the new track upload process 325 then stores the new track information with the associated sketch information 334 and causes the track audio file to be uploaded and stored with the audio files 344.
  • the uploaded and stored track audio files 344 may be played and/or downloaded by any user with access via the user interface 302.
  • the track upload process 325 may optionally invoke a copyright generation process 326 and a copyright management process 327, for example, by including a user selectable option when prompting the user for the new track information.
  • the copyright generation process 326 generates an electronic copyright certificate from the audio file and track information, as will be described in greater detail below, and causes the electronic copyright certificate to be sent to the user for download via the user interface 320.
  • the electronic copyright certificate may also be sent to the user via an email including copyright information (e.g., certificate date, creation date, owner name, file name, digital fingerprint, and algorithm used).
  • the copyright management process 327 causes the copyright certificate to be stored with the copyright files 342 in the system.
  • the user 302 may also interact with the user interface 320 to upload multiple track audio files and associate those tracks with the sketch.
  • the user may also authorize other users (i.e., collaborators) to upload and associate tracks with the sketch, as described below.
  • At least one of the tracks may be a mixdown track that includes a mix of multiple tracks, which eventually may form a completed or finished song.
  • the user may interact with the user interface 320 to invoke a publish song process 328.
  • the publish song process.328 prompts the user via the user interface 320 to provide song information and then stores the song information 336.
  • the published song is then available for purchase by any user with access to the published song information 326 via the user interface 302.
  • a user 402 may interact with a user interface 420 (e.g., web pages) to view sketches and to play and/or download audio tracks associated with the sketches.
  • a user interface 420 e.g., web pages
  • the user may interact with the user interface 420 to invoke a request collaboration process 423, which may prompt the user for a message to the sketch creator.
  • the request collaboration process 423 causes the request to be communicated to the sketch creator, for example, by updated profile information 432 associated with the sketch creator such that the ' sketch creator receives the request when accessing the profile of the sketch creator.
  • the collaboration request process 423 may also cause the collaboration request to be communicated by email or other communication means to the sketch creator.
  • the sketch creator receives the collaboration request (e.g., when viewing profile information)
  • the sketch creator user may invoke an accept collaboration process 424.
  • the accept collaboration process 424 may update the sketch information 434 and/or profile information 432 such that the collaborator is provided with access to the new track upload process 425 for uploading and associating a new track with the sketch.
  • the accept collaboration process 424 may also cause the acceptance to be communicated to the collaborating user.
  • the collaborator may invoke the new track upload process 425 that prompts the collaborator via the user interface 420 to provide new track information and to select a track audio file for upload.
  • the new track may then be uploaded and associated with the sketch as described above in connection with FIG. 3.
  • the new track upload process 425 may also invoke a copyright generation process 426 and manage copyright process 427 to allow the collaborator to generate and store copyright files 442 for protecting copyright in the collaborator's contribution to the sketch.
  • the sketch information 434 including the new tracks associated with the sketch may then be viewed by the sketch creator and by other potential collaborators and the track audio files 444 may be played and/or downloaded.
  • the sketch creator may give access to all members for collaboration on a sketch without requiring acceptance of a collaboration request.
  • Each of the collaborators may be notified (e.g., by email) in response to an action involving the sketch, such as uploading a track, uploading a mix, publishing a song, and finalizing percentages.
  • one system and method for on-line music protection involves the creation or generation of electronic copyright certificates or seals and optionally the managemen and verification of the copyright certificates.
  • a user 502 may interact with a user interface 520 (e.g., web pages) to invoke a copyright generation process 526, which prompts the user to enter copyright information and to select an audio file for upload.
  • the generate copyright function then invokes an upload file process 525 to upload the selected audio file and generates the electronic copyright certificate using the uploaded digital audio file and the entered copyright information.
  • the generate copyright process 526 then provides an electronic copyright certificate file for download by the user and stores details of the electronic copyright certificate in the profile information associated with the user.
  • the copyright generation process may be applied to any type of copyrightable work represented in digital form including, without limitation, photographs, artwork, literature, poetry, scripts, articles, architectural designs, and software.
  • FIG. 5A illustrates one embodiment of the copyright generation process in greater detail.
  • the digital work file may be combined with copyright information including at least a name of the creator and a hashing function may be used to generate a hash or digital fingerprint of the digital work file and copyright information.
  • the digital fingerprint is time-stamped and the time-stamped digital fingerprint is then digitally signed using a verifiable digital cryptographic signature.
  • the digitally-signed, time-stamped digital fingerprint forms the electronic copyright certificate and the resulting electronic copyright certificate file may be stored together with the digital work file and copyright information.
  • the time-stamping and digital signature may be provided by a time- stamping authority using a trusted time-stamping technique.
  • One example of the hashing function used to generate the digital fingerprint of the digital work file and copyright information is a one-way hashing function such as SHA-256.
  • One example of the encryption used to generate the digital signature is a public-private key encryption such as RSA 2048-bit key asymmetric encryption based on the Cryptographic Message Syntax standard PKCS #7.
  • Other techniques for generating an encrypted, time-stamped representation of the digital audio file and copyright information may also be used to create the electronic copyright certificate.
  • the generate copyright process 526 may also store the electronic copyright certificate file together with the original digital audio file in a secure system database of copyright certificate files 542.
  • the user 502 may also interact with the user interface 520 to view profile information 532 including information identifying copyright certificates generated and/or managed for the user and to invoke a download copyright process 527 or a verify copyright process 528.
  • the download copyright process 527 causes the copyright certificate file stored in the secure system database to be downloaded to a user computer.
  • the verify copyright process 528 may verify an electronic copyright certificate being managed by the system (e.g., stored with the copyright files 542) or may verify an electronic copyright certificate that is uploaded to the system by invoking an upload copyright process 529.
  • the verify copyright process 528 calculates the digital fingerprint of the original digital work file (e.g., using the hashing function), extracts the digital fingerprint from the electronic copyright file (e.g., using a public key provided with the digital signature), and compares the digital fingerprints. If the digital fingerprints match, the electronic copyright certificate is verified for that particular digital work file.
  • a user 602 may interact with a user interface 620 (e.g., web pages) to view song information 636 for published songs available for purchase and/or download.
  • the user 602 may invoke a purchase request process 628 for a selected song.
  • the purchase request process 628 may prompt the user to enter purchaser information and may invoke a purchase transaction process 629 that carries out a purchase transaction (e.g., a credit card transaction).
  • a purchase transaction e.g., a credit card transaction.
  • an anti-piracy protection process 626 embeds anti- piracy information into the purchased digital audio file retrieved from the audio files 644.
  • the anti -piracy information includes at least purchaser identifying information (e.g., purchaser account details and purchaser IP address) and may also include copyright ownership information (e.g., copyright owner name and creation date).
  • a download process 627 then causes the song to be downloaded to the user computer of the purchaser.
  • the anti- piracy protection process may be invoked based on a user preference selected by the user (e.g., when publishing the song) and stored with the song information 636.
  • FIG. 6A illustrates one embodiment of the anti-piracy protection process in greater detail.
  • the anti-piracy information including at least purchaser identifying information is encrypted and the encrypted anti-piracy information is converted to an audio signal.
  • the anti-piracy audio signal is then embedded within the song digital audio file such that the anti-piracy audio signal is inaudible and has negligible affect the audio quality of the
  • the anti-piracy audio signal may be embedded as lower volume sounds immediately following a louder peak, which makes the anti-piracy audio signal undetectable to the human ear.
  • One example of software capable of embedding the anti- piracy audio .signal in this way is the audio watermarking software known as Audio
  • the protected song audio file may be converted into numerous audio formats without losing the embedded anti-piracy information. If an unauthorized copy of the protected song audio file is discovered (e.g., on a torrent website or P2P file sharing site), the file may be decoded to determine where the file originated from (e.g., the original purchaser). Both the copyright owner(s) and original purchaser may be notified (e.g., via email) of the discovered unauthorized copy.
  • FIGS. 7 A and 7B one arrangement of web pages on a music collaboration, protection and promotion web site is shown and described.
  • FIG. 7A generally shows an arrangement of web pages accessible from a music collaboration, protection and promotion home page
  • FIG. 7B generally shows an arrangement of web pages accessible from a registered user or member home page.
  • Other arrangements of web pages may also be used to achieve the functionality of the systems and methods described herein.
  • FIGS. 8A-8V show screen shots of one example of web pages that may be used on the music collaboration, protection arid promotion web site. Other web page designs and layouts may also be used.
  • FIGS. 8A and 8B show screen shots of one example of home pages generated by collaboration, protection and promotion software code and displayed on a user computer system.
  • The'system home web page shown in FIG. 8A allows a user to access music, sketches, musician information, and other information stored in the music collaboration, protection and promotion system.
  • the system home page also allows a registered user or member to log in and access features available to members of the music collaboration, protection and promotion system.
  • the member home page shown in FIG. 8B allows a member to access user profile information, songs associated with the member, sketches created by the member, collaborations involving the member, song sales associated with the member, and copyrights associated with the member.
  • the member home page may also display sketches requiring the member's talents, musicians that the member is following, other registered users or members following the member, recommended music, musicians or sketches for the member, and/or activities involving the member.
  • the user may activate or "click on” hyperlinks on the home pages to access other web pages of the music collaboration, protection and promotion system.
  • the home pages may also include a search interface allowing the user to access a search tool capable of searching the music collaboration, protection and promotion system for music, sketches, musicians, or other information.
  • the web pages may also include buttons or hyperlinks for invoking the' music collaboration, protection and promotion functions, procedures and processes described herein.
  • FIGS. 8C-8F show screen shots of one example of sketch pages for displaying sketch information and for providing access to sketches on the system.
  • the illustrated sketches page lists sketches with a sketch title, a brief description and an embedded audio player for playing a track associated with the sketch (FIG. 8C).
  • the illustrated sketch details pages provide sketch information (FIG. 8D), list tracks associated with the sketch (FIG. 8E), and list mixdown tracks associated with the sketch (FIG. 8F).
  • the illustrated sketch details pages also include embedded audio players, add to playlist buttons or hyperlinks and/or download buttons or hyperlinks to play and/or download the tracks or mixdown tracks. Any of the sketch pages may also include a request collaboration button or hyperlink to allow a user to request collaboration on the sketch. If a user is an accepted collaborator and
  • the sketch details page displayed to that collaborator may include an upload new track button or hyperlink (not shown) allowing the collaborator to upload a new track for association with the sketch.
  • FIGS. 8G-8J show screen shots of one example of musician pages for providing musician information.
  • the illustrated musicians page lists musicians with information about the musicians (FIG. 8G).
  • the illustrated musician details pages list songs published by the musician (FIG. 8H), sketches created by the musician (FIG. 81), and the musician's collaborations on other sketches (FIG. 8J).
  • the songs section of the musician details page includes an embedded audio player to play the song, an add to playlist button or hyperlink to cause the song to be added to a playlist for playback, and a purchase button or hyperlink to initiate a purchase transaction.
  • the sketches section of the musician details page includes an embedded audio player for playing a track associated with the sketch.
  • the collaborations section of the musician details page identifies the sketches on which the musician has collaborated ; and the tracks uploaded by the musician for those sketches and includes a download button or hyperlink to download those tracks.
  • Any of the musicians pages may also include a contact button or hyperlink for initiating contact with the musician (e.g., via email) and a follow button or hyperlink for following the musician (e.g., by listing sketches created by the musician, tracks uploaded by the musician, and songs published by the musician on the users home page).
  • FIGS. 8K-8L show screen shots of one example of songs pages for displaying song information and for making the songs available for playing, download and/or purchase.
  • the illustrated songs page may list songs according to different rankings (e.g., most recent, editor's picks, most viewed, and search results).
  • the illustrated songs page also includes an embedded audio player for playing the song and includes add to playlist, purchase, contact and follow buttons or hyperlinks.
  • the illustrated song details page (FIG. 8L) further includes additional song information and a share this song button or hyperlink that causes an email to be generated and sent with a link to the song on the system web site.
  • FIG. 8M is a screen shot of one example of a radio playlist generation page for creating, displaying and playing a playlist of songs available on the system.
  • the illustrated radio playlist generation page includes a sortable list of songs for selection by the user, an embedded audio player for playing the song, and an add to playlist button or hyperlink for adding the selected song to a playlist for playback.
  • the songs may be filtered based on genre.
  • FIG. 8N is a screen shot of one example of a charts page for displaying songs, sketches and musicians based on, for example, most downloaded, most viewed, and most commented.
  • the illustrated charts page includes a playlist audio player for rendering a featured playlist of songs.
  • FIGS. 80-8U show screen shots of one example of member pages accessible from the member home page shown in FIG. 8B.
  • FIG. 80 shows a screen shot of one example of a member song page displaying songs published by the member.
  • the illustrated member song page includes a create new song button or link and
  • FIG. 8P shows a screen shot of one example of a publish song page to acquire song information for publishing a song.
  • the illustrated publish song page includes text fields for song information (e.g., name, notes, lyrics, price); a file selection control for selecting the song audio file for upload, and user selectable options for purchase or free download.
  • the illustrated publish song page also includes user selectable options for generating a copyright certificate, managing the copyright certificate, and providing anti-piracy protection for the song.
  • FIG. 8Q shows a screen shot of one example of a member sketch page for displaying sketches created by the member.
  • the illustrated member sketch page may provide links to sketch details pages for sketches created by the member and includes a create sketch button or link for initiating creation of a new sketch.
  • FIG. 8R shows a screen shot of one example of a: create sketch page to acquire sketch information and create a sketch for the member.
  • the illustrated create sketch page includes text fields for receiving a sketch name, notes, tags, and beats per minute, a drop down menu for selecting a key, and check boxes for selecting talent required, genre, style, and tempo.
  • FIG. 8S shows a screen shot of one example of a member collaborations page for identifying current collaborations of the member and published songs on which the member has collaborated.
  • the current collaborations may identify sketches and the tracks that the member has -uploaded for those sketches.
  • FIG. 8T shows a screen shot of one example of a member sales page for identifying sales records for member songs that are purchased.
  • the member sales page may include a song name, price and date of last sale.
  • FIG. 8U shows a screen shot of one example of a member copyright page for identifying copyright certificates generated for the member.
  • the member copyright page may include the name of the file associated with the copyright, the owner of the copyright, the date added to the system, and an indication of whether or not the copyright is managed by the system.
  • the illustrated member copyright page also includes a create new copyright button or hyperlink for invoking a copyright generation process.
  • FIG. 8V shows a screen shot of one example of a create copyright page that receives information and selects a file for uploading and generating an electronic copyright certificate.
  • FIGS . 9 A-9Y, 1 OA- 1 OF, 1 1 A- 1 11 and 12A- 12F various methods of on-line music collaboration, protection and promotion, consistent with embodiments of the present invention, are described in greater detail.
  • the methods are illustrated with a series of screen shots of web pages displayed to the user.
  • the illustrated web pages have designs according to one example, those skilled in the art will recognize that other implementations of these methods are possible using other web page designs.
  • FIGS. 9A-9Y show screen shots of a series of web pages used to implement a method for on-line collaboration by creating a new sketch, consistent with an embodiment.
  • a registered user or member may first log in to the member's account by entering a username and password (FIG. 9A). If the username and password are verified, a member home page including member profile information is displayed (FIG. 9B). From the member home page, the member may click on a hyperlink for member sketches to cause a member sketches page to be displayed, which identifies and provides access to sketches created by the member and includes a create new sketch button (FIG. 9C). Clicking on the create, new sketch button causes a create new sketch page to be displayed for receiving sketch information (FIG.
  • the create sketch page may be a web form including data fields for entering sketch information, radio buttons, check boxes, and drop down menus for selecting options, and/or file selection tools for selecting files from the user computer for upload.
  • the illustrated create new sketch page receives a sketch name, a short description, tags, beats per minute (BPM), a musical key selection, and a picture selection (FIG. 9E).
  • the illustrated create new sketch page also receives a talent required selection, genre selection, style selection, and tempo selection (FIG. 9F). Clicking on a create button (FIG. 9G) then causes the sketch information to be stored and causes the new sketch to appear on the sketches page listing member sketches (FIG. 9H).
  • the illustrated sketches page includes sketch information and an embedded audio player for rendering an audio file for the sketch.
  • Clicking on the sketch causes a sketch details page to be displayed with more detailed information for the selected sketch and tracks and mixes associated with the sketch (FIG. 91).
  • Clicking on the tracks tab causes a tracks section of the sketch details page to be displayed (FIG. 9 J), which identifies uploaded tracks associated with the sketch and provides access to those tracks.
  • the tracks section of the sketch details page also provides access to an upload new track button for creators of the sketch and for collaborators authorized to collaborate on the sketch.
  • Clicking on the upload new track button causes an upload new track page to be displayed for receiving track information and initiating a track upload (FIG. 9L).
  • the upload new track page may be a web form including data fields for entering track information, ;radio buttons, check boxes, and drop down menus for selecting options, and/or file selection tools for selecting audio files from the user computer for upload.
  • the illustrated upload new track page receives a track name, a track type selection, a cue playback value, an audio file selection, a generate copyright certificate selection, and a manage copyright selection (FIGS. 9L-9S). Clicking on the upload button (FIG. 9S) then causes the track information ⁇ be stored, causes the selected audio file to be uploaded as the track, and causes the track to be listed under the tracks associated with the sketch (FIG. 4T). If the track type selection is a'mixdown, the track is listed under the mixes section of the sketch details page.
  • the track section of the illustrated sketch details page includes track information, an embedded audio player, an add to playlist button for causing the track to be added to an audio playlist, and a download button for causing the track audio file to be downloaded to a user computer.
  • the mixes section of the illustrated sketch details page accessible to the creator of the sketch also includes a publish button for causing the mixdown to be published as a complete song. Clicking on the publish button (FIG. 9U) causes a publish song page to be displayed for receiving published song information and for initiating publication.
  • the publish song, page may be a web form including data fields for entering song information, radio buttons ⁇ check boxes, and/or drop down menus for selecting options, and/or file selection tools for image files from the user computer for upload.
  • the illustrated publish song page receives a song name, notes, a song icon, a for sale selection, a price, lyrics, collaborator selections, a genre selection, an anti-piracy protection selection, and collaborator royalty values (FIGS. 9L-9S). Clicking on the submit button causes the song information to be stored and causes the song to be made available for download and/or purchase. If the anti- piracy protection is selected, anti-piracy information will be embedded in the song audio file when the file is downloaded or purchased.
  • FIGS. 10A-10F show screen shots of a series of web pages used to implement a method for on-line collaboration by enabling musicians to collaborate on a sketch, consistent with an embodiment.
  • a potential collaborator may browse sketch pages to identify sketches for collaboration. When a sketch page is displayed, the potential collaborator may click on the play button of the embedded audio player to cause an audio file associated with the sketch to be played (FIGS. 10A and 10B). When the potential collaborator finds a sketch for collaboration, the potential collaborator may click on a sketch name to cause a sketch details page with sketch information to be displayed (FIG. IOC). From the sketch details page, the potential collaborator may review sketch details and other collaborators and may also access the tracks section or the mixes section to review and/or listen to tracks and/or mixes created for the sketch.
  • the potential collaborator does not yet have access to an upload new track process to upload a new track associated with a sketch.
  • the sketch details page also includes a request collaboration button for initiating a collaboration request (FIG. 10D). Clicking on the request collaboration button may cause a request collaboration text box to open for entering a reason and/or plan for the collaboration (FIG. 10E). Clicking on a submit button causes a communication of the collaboration request to the sketch creator, for example, by email or by notification on the sketch creator's home page.
  • the potential collaborator becomes a collaborator associated with the sketch, the sketch data is updated, and the collaborator has access to an upload new track process (e.g., an upload new track button appears on the sketch page accessed by the potential collaborator).
  • the collaborator may thus initiate a new track upload, for example, similar to a new track upload initiated by the sketch creator as described above. '
  • FIGS. 11 A- 111 show screen shots of exemplary web pages used to implement a method for generating an electronic copyright certificate, consistent with an embodiment.
  • the user may first log in to the user's account by entering a username and password (FIG. 11 A). If the username and password are verified, a member home page including member profile information is displayed (FIG. 1 IB). From the member home page, the member may click on a hyperlink for member copyrights to cause a member copyrights page to be displayed, which identifies copyright certificates generated for the member (FIG. 11C).
  • the member copyrights page may also include a download copyright seal button to initiate a download of the electronic copyright certificate file and a verify button to initiate verification of the copyright certificate (FIG. 1 ID).
  • the member copyrights page also includes a create new copyright button (FIG. 1 ID). Clicking on the create new copyright button causes a create new copyright page to be displayed for receiving copyright information (FIG. 1 IE).
  • the create new copyright page may be a web form including data fields for entering copyright information, radio buttons, check boxes, and drop down menus for selecting options, and/or file selection tools for selecting files from the user computer for upload.
  • the create new copyright page may receive a file; name, a track type selection, an upload file selection, and a manage copyright selection. Clicking on the file selection tool causes a file selection window to be displayed for selecting a file on the user computer (FIG. 1 IF).
  • the create new copyright page may also include an upload button for initiating an upload of the file selected using the file selection window (FIG. 11G). Clicking on the upload button causes a copyright certificate generation process to generate an electronic copyright certificate file based on the uploaded file, causes the electronic copyright certificate file to be downloaded to the user computer (FIG. 11H), and causes the electronic copyright certificate to be stored on the system (e.g., if the manage copyright option is selected). The copyright certificate will then be identified on the member copyrights page (FIG. 111).
  • an upload button for initiating an upload of the file selected using the file selection window
  • Clicking on the upload button causes a copyright certificate generation process to generate an electronic copyright certificate file based on the uploaded file, causes the electronic copyright certificate file to be downloaded to the user computer (FIG. 11H), and causes the electronic copyright certificate to be stored on the system (e.g., if the manage copyright option is selected).
  • the copyright certificate will then be identified on the member copyrights page (FIG.
  • FIGS. 12A-12F show screen shots of web pages used to implement a method for verifying an electronic copyright certificate, consistent with an embodiment.
  • the member copyright page identifies the works for which electronic copyright certificates have been generated, the owner, the date added, and whether or not the system is managing (i.e., storing) the copyright certificate for the work (FIG. 12A). If the system is managing the copyright certificate, the member may click on a download seal button to cause a copy of the electronic certificate to be sent to the user computer (FIG. 12C). To verify the electronic copyright certificate, the member may click on a verify button (FIG.
  • the copyright certificate or seal to be verified e.g., a copyright certificate file stored on the user computer or previously sent to the user computer.
  • the copyright certificate file on the user computer will be uploaded, a copyright verification process will compare the digital fingerprint of the work to the digital fingerprint extracted from the uploaded copyright certificate file, and the member will be provided with a confirmation of the result.
  • the music collaboration, protection and promotion systems and methods described herein may be used to allow musicians to collaborate on-line to create musical works, to protect individual rights to copyrights in those works, and to promote those works to listeners and potential purchasers.
  • the music collaboration, protection and promotion systems and methods advantageously allow musicians at remote geographic locations to identify other musicians for collaboration and to collaborate with those musicians despite the geographic separation.
  • the music collaboration, protection and promotion systems and methods advantageously allow the musicians to protect copyrights more quickly and efficiently for digital works that are accessible on-line and facilitate protection when multiple musicians collaborate and make creative contributions to a single work.
  • the music collaboration, protection and promotion systems and methods advantageously allow musicians to promote the works by creating a network of musicians and music listeners and allow musicians to obtain royalties for sales of musical works even when the musician is only one collaborator on a completed work.
  • the music collaboration, protection and promotion systems and methods further advantageously allow anti-piracy protection for the musical works that are sold and/or distributed from the system.
  • Embodiments of the methods described above may be implemented as software or a computer program product for use with a processing system or computer. Such
  • implementation may include, without limitation, a series of computer instructions that embody all or part of the functionality described herein.
  • the series of computer instructions may be stored in any tangible machine-readable medium, such as semiconductor, magnetic, optical or other memory devices, and may be transmitted using any communications technology, such as optical, infrared, microwave, or other transmission technologies.
  • Such a computer program product may be distributed as a removable machine-readable medium (e.g., a diskette, CD-ROM), preloaded with a computer system (e.g., on system ROM or fixed disk), or distributed from a server or electronic bulletin board over the network (e.g., the Internet or World Wide Web).
  • Alternative embodiments of the invention may be implemented as pre-programmed hardware elements or as a combination of hardware, software and/or firmware.
  • a music collaboration, protection and promotion system may also include other processes, procedures or functions in addition to or in place of the processes, procedures or functions described herein. These or process, procedures or functions may be executed by a processor on one computer or may be executed by processors on separate computers.
  • the data may include other types of data in addition to or in place of the data described herein.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Finance (AREA)
  • Development Economics (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Reverberation, Karaoke And Other Acoustics (AREA)

Abstract

Des systèmes et des procédés informatisés selon l'invention peuvent être utilisés pour permettre une collaboration, une protection et une promotion de musique en ligne. Une collaboration de musique en ligne peut être rendue possible en permettant à plusieurs musiciens de créer des morceaux de musique et de télécharger vers le serveur des fichiers audio numériques pour trouver des pistes associées aux morceaux afin de former une œuvre musicale. Une protection de musique en ligne peut être rendue possible en générant, en gérant et/ou en vérifiant des certificats de droits d'auteur électroniques pour l'œuvre musicale et/ou pour les pistes créées en collaboration par des musiciens pour l'œuvre musicale. Une promotion en ligne peut être rendue possible en permettant à des œuvres musicales finies et/ou à des pistes de musique d'être lues, téléchargées et/ou achetées. Une protection de musique en ligne peut également être rendue possible en incorporant des informations de protection contre la copie identifiant un acheteur dans un fichier audio numérique d'une œuvre musicale achetée.
PCT/IB2011/000070 2010-01-18 2011-01-18 Systèmes et procédés permettant une collaboration, une protection et/ou une promotion de musique en ligne WO2011086465A1 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
IES2010/0108 2010-01-18
IE20100108 2010-01-18
IE20100136 2010-03-09
IES2010/0136 2010-03-09
IES2010/0667 2010-10-18
IE20100667 2010-10-18
US41542010P 2010-11-19 2010-11-19
US61/415,420 2010-11-19

Publications (1)

Publication Number Publication Date
WO2011086465A1 true WO2011086465A1 (fr) 2011-07-21

Family

ID=44303881

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IB2011/000070 WO2011086465A1 (fr) 2010-01-18 2011-01-18 Systèmes et procédés permettant une collaboration, une protection et/ou une promotion de musique en ligne

Country Status (1)

Country Link
WO (1) WO2011086465A1 (fr)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9298416B2 (en) * 2013-02-06 2016-03-29 Google Inc. Adding media to a locker
US9336360B1 (en) 2013-03-14 2016-05-10 Kobalt Music Group Limited Analysis and display of a precis of global licensing activities
USD773490S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773492S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773491S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
US10057205B2 (en) 2014-11-20 2018-08-21 GroupLuv, Inc. Systems and methods for creating and accessing collaborative electronic multimedia compositions
US10319040B1 (en) 2013-03-14 2019-06-11 Ktech Services Limited Control of the generation and display of royalty administration and rights management data based on the user's rights of access
EP4287090A1 (fr) * 2022-05-31 2023-12-06 Sparwk AS Système et procédé de recommandation de créateur de musique basé sur le contenu

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008033840A2 (fr) * 2006-09-12 2008-03-20 Eyespot Corporation Systèmes et procédés de création, de collecte et d'utilisation de métadonnées
US20080263359A1 (en) 2007-04-17 2008-10-23 Alex Radzishevsky Water mark embedding and extraction
US20090116668A1 (en) * 2005-09-15 2009-05-07 Digital Layers Inc. Method, a System and an Apparatus for Delivering Media Layers

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20090116668A1 (en) * 2005-09-15 2009-05-07 Digital Layers Inc. Method, a System and an Apparatus for Delivering Media Layers
WO2008033840A2 (fr) * 2006-09-12 2008-03-20 Eyespot Corporation Systèmes et procédés de création, de collecte et d'utilisation de métadonnées
US20080263359A1 (en) 2007-04-17 2008-10-23 Alex Radzishevsky Water mark embedding and extraction

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US9298416B2 (en) * 2013-02-06 2016-03-29 Google Inc. Adding media to a locker
US9336360B1 (en) 2013-03-14 2016-05-10 Kobalt Music Group Limited Analysis and display of a precis of global licensing activities
US10319040B1 (en) 2013-03-14 2019-06-11 Ktech Services Limited Control of the generation and display of royalty administration and rights management data based on the user's rights of access
USD773490S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773492S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
USD773491S1 (en) 2013-03-15 2016-12-06 Kobalt Music Group Limited Display screen with a graphical user interface
US10057205B2 (en) 2014-11-20 2018-08-21 GroupLuv, Inc. Systems and methods for creating and accessing collaborative electronic multimedia compositions
EP4287090A1 (fr) * 2022-05-31 2023-12-06 Sparwk AS Système et procédé de recommandation de créateur de musique basé sur le contenu

Similar Documents

Publication Publication Date Title
US11256788B2 (en) Tokenized media content management
US11250111B2 (en) Tokenized media content management
WO2011086465A1 (fr) Systèmes et procédés permettant une collaboration, une protection et/ou une promotion de musique en ligne
US20190318348A1 (en) Media licensing method and system using blockchain
JP4549673B2 (ja) マルチメディア・コンテンツの許可されない再記録を防ぐ方法およびシステム
US8199935B2 (en) Method, a system and an apparatus for delivering media layers
US11983253B2 (en) Non-fungible token (NFT) content identifier with split tracking
US20150154385A1 (en) Site Directed Management of Audio Components of Uploaded Video Files
US20030115349A1 (en) System and method for delivering a multimedia presentation to a user and to allow the user to play a musical instrument in conjunction with the multimedia presentation
US20020159304A1 (en) Method and apparatus for information processing, and medium for storing program
JP2011504617A (ja) デジタルコンテンツを配信する方法及び装置
KR20020007290A (ko) 정보 처리 장치, 정보 처리 방법 및 정보 저장 매체
US11687628B2 (en) Non-fungible token (NFT) authenticity protocol with fraud deterrent
US20230222187A1 (en) Media composition using non-fungible token (nft) configurable pieces
TWI227423B (en) Device and method for processing information, and computer readable storage medium
JP2001236081A (ja) 情報処理装置および方法、並びにプログラム格納媒体
US9171179B2 (en) System and method for the provision of multimedia materials
WO2020015410A1 (fr) Procédé et dispositif d'envoi de récompense à un auteur de travail sur la base d'une chaîne de blocs
JP4739669B2 (ja) 楽器を演奏する際にユーザを支援するマルチメディア・プレゼンテーション
EP1156478A1 (fr) Procede et machine de traitement des donnees, et support de stockage de programmes
US11954147B1 (en) Methods, systems, and media for tracking content items
WO2022232184A1 (fr) Gestion de contenu multimédia tokenisé
WO2022232180A1 (fr) Gestion de contenu multimédia tokenisé
JP2001144750A (ja) 情報処理装置および方法、情報提供装置および方法、並びにプログラム格納媒体

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: 11710859

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11710859

Country of ref document: EP

Kind code of ref document: A1