HK1242485B - Purchasing, sharing and transferring ownership of digital music using authenticated data files from near field communication chips - Google Patents

Description

Method and system for purchasing, sharing, and transferring digital music ownership using authentication data files from a near field communication (NFC) chip

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of priority to U.S. patent application serial number 62/086,384, filed December 2, 2014, the contents of which are incorporated herein by reference in their entirety.

Technical Field

The present invention relates to the use of Near Field Communication (NFC) technology for transferring data files between mobile devices, and more particularly to the use of NFC chips to authenticate the purchase, sharing, and ownership transfer of music files.

Background Art

Ever since the advent of Internet file sharing, the music industry has been experimenting with new models for distributing music. Before the invention of music downloads, the music industry moved through a phase of physical exchange media, such as eight-track tapes, vinyl records, cassettes, and CDs. Today, with the advent of electronic music purchasing services, purely digital transfer of music dominates music distribution. Brick-and-mortar stores selling music in physical form have become rare and exist primarily as specialty stores for music enthusiasts.

In the past, borrowing and giving music as gifts was simple. Individuals could simply give or borrow physical media. However, digital music files present more problems because digital media can be easily copied and transferred to multiple different individuals. For this reason, encryption systems have been used to prevent music files from being transferred, but these systems have the disadvantage of not providing a convenient system for temporarily sharing music and the option to purchase shared music. Therefore, there is still a need for a middle ground that allows users to temporarily share music files with others while still maintaining control over the copying and further distribution of the music files, and that provides the borrower with the opportunity to conveniently purchase the same music.

Summary of the Invention

The above challenges are solved by the methods and devices of the present invention. In one aspect of the present invention, a method for transferring music files to an initial purchaser using near field communication (NFC) is provided, the method comprising: providing an NFC identifier (ID) unique to the NFC chip to an NFC chip; assigning a set of music files to an NFC ID and purchase code pair, wherein the NFC ID and purchase code pair is stored on a server system configured to access and transfer the music files; reading the NFC ID from the NFC chip using an NFC-enabled device, the NFC-enabled device being loaded with music sharing software configured to play the music files; entering the purchase code into the NFC-enabled device; authenticating the NFC ID and purchase code pair received by the NFC-enabled device through communication with the server system; and, if authenticated, registering the music files to a user of the NFC-enabled device. Once the music files are registered, the user is allowed to download the music files to the NFC-enabled device for playback of the downloaded music files, or the music files can be played by saving the music files to a registered account and playing the music files remotely from the account using the NFC-enabled device. In some embodiments, remotely playing the files is performed using streaming technology. Additionally, once registered, a user may designate other users to receive temporary access to streaming copies of music files, which is mediated and monitored by the server system.

The NFC chip is preferably provided in a form that protects the NFC chip itself from damage while facilitating physical exchange.In some embodiments, the NFC chip is encapsulated in a polymer and shaped to form an NFC bead.

In some embodiments, the purchase code is preloaded onto the NFC chip. In such embodiments, the NFC chip is provided in packaging that includes a metal wrap that prevents the NFC chip from communicating with the NFC chip. However, in a preferred embodiment, the purchase code does not utilize near-field technology for communication and is therefore not preloaded onto the NFC chip. In some embodiments, the purchase code is entered into the music sharing software by the user, for example, by typing a string of numbers, letters, and symbols through a user interface on an NFC-enabled device.

In a preferred embodiment, the music files are stored in a database within the server system along with the purchase code. The server system may also store the device ID unique to the NFC-enabled device that is allowed to play the music files, and the NFC ID.

In a related aspect, the present invention also provides a method for playing music files using near field communication (NFC), the method comprising: providing an NFC-enabled device loaded with music sharing software, and an accessible playlist of music files from a library of accessible music files, wherein the playlist is assigned to a playlist identifier (playlist ID) encoded on an NFC chip; establishing near field communication between the NFC-enabled device and the NFC chip to receive the playlist ID from the NFC chip to the NFC-enabled device; and playing the playlist on the NFC-enabled device in response to receiving the playlist ID from the NFC chip.

In some embodiments, multiple playlists can be accessed via an NFC-enabled device, wherein each playlist within the multiple playlists is assigned a unique playlist ID. In some embodiments, a playlist of music files and a library of music files are stored on the NFC-enabled device. In other embodiments, a playlist of music files is stored on the NFC-enabled device, and fewer music files are stored on the NFC-enabled device than the library of all accessible music files accessible via the NFC-enabled device. In other embodiments, the playlist of music files and the library of music files are stored on a server system in a user account accessible by a user using an NFC-enabled device. Preferably, the NFC-enabled device is registered with the user account to allow access to the library of music files. The NFC-enabled device can distinguish playlists by their unique playlist IDs, and therefore multiple NFC chips can be provided, each encoded with a different playlist ID for activating different playlists or music files.

In another related aspect, the present invention provides a method for sharing a music playlist using near field communication (NFC), the method comprising: assigning a playlist identifier (playlist ID) to a playlist of music files; receiving an NFC identifier (NFC ID) from an NFC chip using an NFC-enabled device; programming the playlist ID to the NFC chip using the NFC-enabled device; storing the NFC ID and the playlist ID to a server system, wherein the server system has accessible copies of the music files encoded in the playlist ID for streaming; receiving the NFC ID and the playlist ID using a subsequent NFC-enabled device; authenticating the NFC ID and the playlist ID received on the subsequent NFC-enabled device using the server system; and, if authenticated, streaming a copy of the music files via the subsequent NFC-enabled device. The playlist ID may be generated and assigned by the NFC-enabled device for programming to the NFC chip and for transmission to the server system. Alternatively, the server system may generate and assign the playlist ID and then provide the playlist ID to the NFC-enabled device for programming to the NFC chip.

The NFC chip is preferably provided in a form that protects the NFC chip itself from damage while facilitating physical exchange.In some embodiments, the NFC chip is encapsulated in a polymer to form an NFC bead.

The sharing feature does not transfer ownership of the music files. Instead, it only allows limited access to the server system for streaming the music files, without allowing the music files to be downloaded to the memory of a subsequent NFC-enabled device for further playback. In some embodiments, the music files used for streaming are shortened files that are shorter than the original music files, while in other embodiments, the music files used for streaming are full-length files. Access restrictions on streaming music files can be implemented using various methods. In some embodiments, streaming is subject to a predetermined time limit. In such cases, the server system may only provide access to the streaming files for a predetermined period of time. After the predetermined time expires, the permission to stream the music files is automatically revoked. Alternatively, the server system may provide access to play the files for a predetermined number of repetitions, where the music files in the playlist can only be played a predetermined number of times before the permission to play the music files is automatically revoked. In some embodiments, the sharing feature also provides subsequent users with the option to purchase one or more of the music files in the playlist after the NFC ID and playlist ID are authenticated.

In another related aspect, the present invention provides a method for transferring music files between users using a near field communication (NFC) enabled device, the method comprising: providing a library of music files to an NFC enabled device; registering an NFC ID, a purchase code, and music files from the library of music files to a user account on a server system; reading the NFC ID from an NFC chip using a subsequent NFC enabled device; entering the purchase code into the subsequent NFC enabled device without using an NFC chip; authenticating the NFC ID and purchase code on the server system; requesting permission to transfer the music files from the user account to a different user account; and if approved, deleting the music files from the library of music files; registering the purchase code and music files to a different user account; and optionally downloading the music files to the subsequent NFC enabled device.

Once the music files have been transferred from the original user, the music sharing software may provide the user with additional options. In some embodiments, an optional option is provided that allows the original user to stream a copy of the deleted music file. In such cases, the streamed file or playable file can be a shortened file shorter than the original music file, can be temporarily streamed, or both. When such optional options are provided, the display can be different from that of the music files owned in the music file library to emphasize the difference in ownership. A first display feature can be used to characterize the owned music files as being playable from the music file library, and a second display feature can be used to characterize the copy of the deleted music file as being only playable for streaming or playback without downloading it to storage for playback. The different display features can be different background shading, different color fonts, different identifiable symbols, or other identifiers that are clearly visible to the observer. In addition, after the transfer of ownership, the music sharing software provides an optional option to repurchase a copy of the deleted music file through the server system.

The NFC chip is preferably provided in a form that protects the NFC chip itself from damage while facilitating physical exchange.In some embodiments, the NFC chip is encapsulated in a polymer to form an NFC bead.

In another related aspect, the present invention provides a method for transferring music files between near field communication (NFC) enabled devices, the method comprising: providing an NFC enabled device loaded with a library of music files and an NFC chip encoded with an NFC identifier (NFC ID); generating a playlist of music files from the library of music files; assigning the playlist ID, a transfer code, and the NFC identifier to the playlist on a server system; saving the playlist ID to the NFC chip; receiving the playlist ID from the NFC chip using a subsequent NFC enabled device; entering the transfer code into the subsequent NFC enabled device; authenticating the NFC ID, playlist ID, and transfer code on the server system; sending a permission request from the server system to the NFC enabled device to confirm the transfer of the music file to the subsequent user; and if approved, deleting the music file from the library of music files; and registering the music file to the subsequent user account, wherein the registration updates ownership of the music file.

Once the music files have been transferred from the user, the music sharing software can provide the user with additional options. In some embodiments, an optional option is provided that allows the user to stream rather than download a copy of the deleted music file. In such cases, the streaming file can be a shortened file that is shorter than the original music file, can be temporarily streamed, or both. When such optional options are provided, the display can be different from the music files in the database of music files to emphasize the difference in ownership. A first display feature can be used to characterize the music file as being available for playback from the database of music files stored in long-term storage, and a second display feature can be used to characterize the copy of the deleted music file as being only available for streaming. The different display features can be different background shading, different color fonts, different identifiable symbols, or other identifiers that are obvious to the observer. In addition, after the transfer of ownership, the music sharing software provides an optional option to repurchase a copy of the deleted music file through the server system.

The NFC chip is preferably provided in a form that protects the NFC chip itself from damage while facilitating physical exchange.In some embodiments, the NFC chip is encapsulated in a polymer to form an NFC bead.

In another related aspect, the present invention provides a near-field communication chip encoded with a playlist ID associated with a playlist of music files, wherein the playlist ID is in a format that can be read by an NFC-enabled device loaded with music sharing software to play the playlist of music files. In a preferred embodiment, the NFC chip is provided in a format that facilitates physical exchange while protecting the NFC chip itself from damage. In some embodiments, the NFC chip is encapsulated in a polymer to form an NFC bead.

In another related aspect, the present invention provides a near-field communication (NFC)-enabled device loaded with music sharing software, wherein the music sharing software includes: NFC programming configured to receive data files from an NFC chip and program the data files to the NFC chip; a music player for playing music files; programming that populates one or more databases with an NFC ID assigned to the NFC chip and a playlist identifier (playlist ID) assigned to a playlist of music files; query programming that compares the received NFC ID and the received playlist ID to the one or more databases; and if a pair is authorized, activates the playlist assigned to the received playlist ID; and communication programming that communicates with a server system to update the playlist ID and NFC ID. In some embodiments, the music sharing software generates a playlist and assigns a playlist ID to the playlist. The playlist ID can be generated using data from each music file to generate a data string that can be decoded by comparison with the music files. In such embodiments, the software can retrieve a code from each music file and order the retrieved codes according to the order of the playlist. Alternatively, software may comprise a random string generator that generates a string of data comprising numerals, letters and symbols in random order. In this type of embodiment, playlist data files may also be generated to decode playlists for transfer to a server system.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments of the present invention can be better understood with reference to the following drawings, and the text in each drawing is incorporated into the description of the embodiments of the present invention. The components in the drawings are not necessarily drawn to scale, but emphasis is placed on illustrating the principles of the present invention.

FIG. 1A is a cross-sectional view of an NFC bead 110 , illustrating an NFC chip 102 encapsulated within a protective coating 104 .

FIG1B is a flow diagram depicting an NFC bead 110 used for communication between two NFC-enabled devices 112a and 112b. Specifically, the flow diagram depicts: the transfer of a data file between the original purchaser's NFC-enabled device 112a and a server system 114 over the Internet 116; the physical transfer of the NFC bead 110 to transfer the data to a subsequent user's NFC-enabled device 112b; and the authentication of the data received from the NFC bead 110 over the Internet 116 between the subsequent user's NFC-enabled device 112b and the server system 114. Also illustrated are a server 118a and a database 118b within the server system 114, which are used for communication functions and for storing identifiers, security codes, music files, and other data files.

Figures 2A-2G are screenshots taken from a mobile phone loaded with music sharing software. Figure 2A is an NFC bead activation screen 202 prompting for a purchase code. Figure 2B is a successful activation screen 204, shown after activation or registration of the NFC bead and purchase code. Figure 2C is a music file screen 206, shown while playing a music file. Figure 2D is a playlist generation screen 208, which indicates which music files will be added to the playlist for sharing. Figure 2E depicts a synchronization screen 210, which instructs the music sharing software to write the playlist ID to the NFC bead. Figure 2F is a social media screen 212, which allows the user to select a social media platform to share a preview of the music file. Figure 2G is a preview screen 214, which provides the user with the option to share a playable preview of the music file or purchase the music file from the server system.

3 is a flow chart depicting a method of purchasing music files using the newly purchased NFC beads of FIG. 1 .

4 is a flow chart depicting a method for sharing access to a playlist by providing a temporary access portal to an account for temporary playback of music files within the playlist.

5 is a flow chart depicting a method of sharing temporary access to a playlist between NFC-enabled devices by providing a playlist ID on the NFC chip of FIG. 1 for authentication with a system server and providing an option to purchase music files within the playlist.

6 is a flow diagram depicting the transfer of ownership of music files from an original purchase playlist between NFC-enabled devices.

7 is a flow diagram depicting the transfer of ownership of a generated playlist between NFC-enabled devices.

FIG8 is a flow chart depicting the retrieval of a lost purchase code.

DETAILED DESCRIPTION

For purposes of clarity of disclosure and non-limiting purpose, the present invention is discussed in terms of various detailed embodiments; however, those skilled in the art will recognize, through guidance herein, that features of one embodiment may be combined with other embodiments, and that such combinations are therefore within the intended scope of the present invention.

The music-sharing software disclosed in this patent application is protected by copyright under the copyright laws of the United States and other countries. This material is protected as unpublished material as of the filing date of this application. Permission to copy this material is hereby granted to the extent that the material appears in the United States Patent and Trademark Office patent file or records or is otherwise in any patent Office file or records. The copyright owner otherwise reserves all copyright rights in this work.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the invention belongs. If a definition set forth in this document is contrary to or otherwise inconsistent with a definition set forth in the art, the definition set forth in this document takes precedence over the contradictory definition.

As used herein, the term "NFC chip" refers to an unpowered integrated circuit capable of near field communication and capable of storing data in a memory, and having an antenna for electric field modulation. The NFC chip is capable of communicating with an NFC-enabled mobile device.

As used herein, the term "packaged NFC chip" refers to an NFC chip disposed within a protective cover, wherein the protective cover does not prevent near field communication between the NFC chip and an NFC-enabled device. The packaged NFC chip requires power from the NFC-enabled device for near field communication.

The term "NFC bead" as used herein refers to a generally spherical or teardrop-shaped housing with an embedded NFC chip that is capable of communicating with an NFC-enabled device. An "NFC bead" is a decorative variant that encapsulates an NFC chip.

As used herein, the term "NFC-enabled device" refers to an electronic device with near field communication software and hardware for powering an NFC chip, transmitting data files to the NFC chip, and receiving data files from the NFC chip.

As used herein, the term "software" refers to a set of commands that directs an NFC-enabled device to perform specific operations. The term "software" is intended to encompass computer programs, libraries, and related non-executable data.

As used herein, the term "system server" refers to a system that includes a computer loaded with computer server software and is accessible on a computer network, where the system server manages network resources, for example, by storing files, processing database queries, or managing network traffic. The system server includes any external and internal databases, memory, and processors.

As used herein, the term "user ID" refers to an identifier used by an individual to identify who owns a music file or playlist.

The term "purchase code" as used herein refers to a code that allows a set of files to be downloaded from the system server to the user's NFC-enabled device.

The term "NFC identifier" or "NFC ID" as used herein refers to an identifier used by music sharing software and server systems to identify one NFC chip from another.

The term "device identifier" or "device ID" as used herein refers to an identifier code used to obtain the identity of an NFC-enabled device.

As used herein, the term "playlist identifier" or "playlist ID" refers to an identifier code used to identify a group of music files.

The term "sharing" refers to providing another user with access to play or stream a copy of a music file owned by the user. "Sharing" means granting limited access to the music file, which is mediated by a server. "Sharing" means that the "shared music file" cannot be downloaded to long-term storage by others for later playback. "Sharing" can use streaming technology, which transfers data so that it can be processed as a steady and continuous stream and is not stored in the long-term storage of the NFC-enabled device. "Sharing" can be achieved by providing limited access to a portal that allows temporary playback of the music file but does not allow the music file to be downloaded to long-term storage on the NFC-enabled device.

As used herein, the term "copy of a music file" refers to an identical or similar version of a music file that is previously possessed and which is not necessarily the same actual music file.

As used herein, the term "download" refers to receiving an entire data object from a server system for local storage and later use.

As used herein, the term "long-term storage" refers to storage within an NFC-enabled device that allows music files to be accessed for playback via the NFC-enabled device at any time without restrictions on time, number of repetitions, or access to the Internet.

Figures 1A-B introduce the present invention, which provides a system and method for purchasing and sharing music files using NFC technology. The system and method combine: a packaged NFC chip 102, preferably embodied as an NFC bead 110, which is provided in the form of a physical exchange between individuals; and NFC-enabled devices 112a, 112b loaded with music sharing software, each capable of wirelessly communicating with a server system 114, which itself can store and stream music files. Server system 114 can transfer music files for playback/streaming and/or provide access to play music files using NFC-enabled devices 112a, 112b, without allowing the music files to be downloaded to storage for later use. In this system, an encapsulated NFC chip 102 or NFC bead 110 communicates with NFC-enabled devices 112a, 112b, which in turn communicate with a server system 114, such as server 118a, via the Internet 116. Server 118a has access to one or more databases 118b storing music files for temporary sharing and corresponding security codes for authentication. Authentication is performed in part by transferring an NFC identifier along with a playlist identifier between NFC-enabled devices 112a, 112b, using the encapsulated NFC chip 110 as a medium of exchange. Because the music sharing software from the original purchaser's NFC-enabled device 112a uploads the shared NFC identifier and playlist identifier to server system 114, subsequent authentication of the identifiers can be achieved by server system 114 when provided by a subsequent NFC-enabled device 112b. To this end, the system and method allow for downloading music files to an identified purchaser's NFC-enabled device 112a, generating a playlist from the purchased music files on the identified purchaser's NFC-enabled device 112a, and temporarily sharing the playlist of music files via another person's NFC-enabled device 112b, in part via the exchange of an encapsulated NFC chip 102. This is generally accomplished by encoding and transferring a playlist identifier on the encapsulated NFC chip 102 and announcing the NFC identifier and playlist identifier to a server system 114, thereby maintaining the music files for streaming during the sharing process. The system and method also provide for purchasing music files from a shared playlist and transferring ownership of the original shared music files.

In one aspect of the present invention, a near field communication (NFC) chip 102 is provided, which is encoded with a playlist ID assigned to a playlist of music files, wherein the playlist ID is in a form that can be read by NFC-enabled devices 112a, 112b loaded with music sharing software. As shown in FIG1A , the NFC chip 102 is preferably encapsulated in a protective layer 104, most preferably in a polymer. As shown in FIG1B , it is preferably shaped for improved decoration to form an NFC bead 110. Preferably, the NFC-enabled devices 112a, 112b are embodied as mobile phones loaded with near field communication software, near field communication hardware, and music sharing software. The server system 114 is preferably a conventional computer server 118a, which is loaded with server software and is configured to host user accounts and multiple music files that can be used for streaming, purchasing, and downloading, for example, by using a database 118b, which can be located inside or outside the server 118a.

Near Field Communication (NFC) is a more sophisticated version of Radio Frequency Identification (RFID). It operates within a maximum range of approximately 4-10 cm and can operate with one-way or two-way communication. NFC communication involves modulating an electric or magnetic field to power a circuit in the form of an NFC chip 102, which, in the present invention, is not powered by itself. To this end, the packaged NFC chip 102 is placed against or in close proximity to an NFC-enabled device 112a, 112b, for example, within approximately 4 cm, 5 cm, 6 cm, 7 cm, 8 cm, 9 cm, or 10 cm of the NFC-enabled device 112a, 112b, to power the packaged NFC chip 102 and thereby allow data to be transferred between the packaged NFC chip 102 and the NFC-enabled device 112a, 112b. Unlike technologies such as Bluetooth, discovery or pairing of the packaged NFC chip 102 with the NFC-enabled device 112a, 112b does not require any manual pairing or device discovery. Alternatively, once the packaged NFC chip 102 is in close proximity to the NFC-enabled devices 112a, 112b, the packaged NFC chip 102 and the NFC-enabled devices 112a, 112b will immediately communicate.

The NFC chip 102 itself is currently available through various manufacturers. The NFC chip 102 is small and fragile, and therefore presents a risk of loss or damage. Therefore, the NFC chip 102 is packaged in a form that reduces the risk of loss or damage and facilitates physical exchange between individuals. The packaged NFC chip 102 can be packaged in various forms, such as a sphere, a card, a figurine, or any decorative physical form that an individual might want to physically exchange with another person, as long as the form does not prevent near-field communication between the packaged NFC chip 102 and the NFC-enabled devices 112a, 112b. For example, enclosing the NFC chip 102 in a metal shell may disrupt near-field communication between the packaged NFC chip 102 and the NFC-enabled devices 112a, 112b and should therefore be avoided without requiring modification to allow near-field communication. As another example, the surrounding shell should not be so thick as to prevent near-field communication with the packaged NFC chip 102. In a preferred embodiment, the NFC chip 102 is enclosed in a polymer shell that serves as a protective coating 104 and is shaped to create the desired decorative effect. This can be accomplished using injection molding techniques with a suitable polymer, such as polypropylene, polystyrene, polyethylene, and other polymers known in the art of polymer and plastic manufacturing. For example, a polymer can be polymerized around the NFC chip 102 to form a polymer shell, or the polymer can be formed and then holes or drilled to allow for the insertion of the NFC chip 102. While metals and metal alloys can be incorporated into the shell, testing should then be done to ensure that near-field communication can be maintained between the encapsulated NFC chip 102 and the NFC-enabled devices 112a, 112b, as the inventors have discovered that metals and metal alloys in some shells can interfere with near-field communication.

The packaged NFC chip 102 can be distinguished from others by an NFC identifier, also known as an NFC ID. The NFC ID is a string of numbers, letters, or symbols specific to the packaged NFC chip. The NFC ID can be programmed into the NFC chip 102 in an unchangeable form, or can be generated and programmed into the NFC chip 102 in a rewritable form. In some embodiments, the NFC chip 102 has a permanent, unrewritable NFC ID and a rewritable temporary NFC ID. If the NFC ID is rewritable, the NFC ID can preferably be rewritten using music sharing software loaded on an NFC-enabled device. This allows a user to generate a vanity NFC bead 110.

Because the packaged NFC chip 102 is not powered by itself, but instead is powered by the electric field generated by the NFC-enabled devices 112a, 112b, a security feature is provided to prevent others from retrieving data for downloading music files before the NFC chip 102 is purchased. That is, because the packaged NFC chip 102 is suitable for retail sale, an NFC-enabled device 112a, 112b positioned in close proximity to the NFC chip 102 during the sales process or while being observed by a potential purchaser could retrieve data from the NFC chip 102 before purchase and, therefore, illegally obtain music files. For this reason, additional security features have been developed to protect the distribution of music files.

One solution to the challenge of preventing unauthorized downloading of music is to require registration of the packaged NFC chip 102 before use in a playlist. This can be performed by registering an NFC ID associated with each packaged NFC chip 102. The music sharing software provides an option for activating a newly acquired NFC chip 102, which may involve transferring the NFC ID from an approved NFC-enabled device 112a, 112b and/or an approved user to the server system 114 for insertion into the database.

Another solution to the challenge of preventing unauthenticated downloading of music in the packaged NFC chip 102 before purchase is to require a purchase code separate from the NFC chip 102. That is, although the NFC chip 102 can be preloaded with an NFC ID and optionally preloaded with a playlist ID associated with one or more music files, downloading the music files is prevented without separately entering a purchase code. Even if the NFC ID and playlist ID are provided to the server system 114, the NFC ID and playlist ID will not be authenticated without pre-registering the NFC ID and/or playlist ID using the purchase code. In some embodiments, the server system 114 will not allow subsequent registration of the pre-registered NFC chip 102 or subsequent downloading of pre-downloaded music files without additional confirmation or authorization from the registered owner.

In some embodiments, the purchase code is provided in a form that is not initially programmed into the packaged NFC chip 102. For example, the purchase code may be written separately on the plug-in, requiring the user to manually enter the purchase code into the music sharing software application after establishing near-field communication with the NFC chip 102. The music sharing software application may then transfer the purchase code to the server system 114 for authentication. Authentication may involve several other authentication steps, such as calculating and adjusting the number of times the purchase code or NFC ID can be submitted.

In other embodiments, the purchase code is activated at the point of sale and can therefore be provided separately from or loaded onto the packaged NFC chip 102. In such embodiments, the cash register terminal can act as a conduit for communication with the server system 114, for example, via the Internet 116, to exchange data and thereby activate the purchase code. In some embodiments, the purchase code is programmed into the packaged NFC chip 102 at the point of sale. The purchaser can then follow the download command, which is typically displayed in the music sharing software application.

In other embodiments, the purchase code is preloaded into the packaged NFC chip 102, but the packaged NFC chip 102 is stored in packaging that blocks near-field communication between the packaged NFC chip 102 and the NFC-enabled devices 112a, 112b. This can be achieved by providing the packaging with a metal layer or film in a configuration that blocks near-field communication between the packaged NFC chip 102 and the NFC-enabled devices 112a, 112b only while the packaging is in place. In some embodiments, the packaging is a metal or metal alloy that completely encapsulates the packaged NFC chip 102. In other embodiments, the packaging includes a metal or metal alloy material configured as a strip that surrounds the packaged NFC chip 102 360 degrees, thereby blocking near-field communication between the NFC chip 102 and the NFC-enabled devices 112a, 112b until the chip 102 is removed. In some embodiments, the NFC chip 102 is surrounded by a metal or metal alloy sphere, thereby blocking near-field communication until the NFC chip 102 or NFC bead 110 is removed from its packaging. Non-limiting examples of usable metals and metal alloys include various conductive materials, such as steel, iron, silver, and gold. In these embodiments, the package must be destroyed to interrupt its sealing effect, or the encapsulated NFC chip 102 must be removed from the package.

In a related aspect, the present invention provides a near field communication (NFC) enabled device 112a, 112b loaded with music sharing software. The music sharing software includes: NFC programming configured to receive data files from the NFC chip 102 and write the data files to the NFC chip 102; a music player in the form of an audio player for playing music files; programming that populates one or more databases with an NFC ID assigned to the NFC chip 102 and a playlist ID assigned to a playlist of music files; query programming that compares the received NFC ID and the received playlist ID with the one or more databases; and if a pair is authorized, starts the playlist assigned to the received playlist ID; and communication programming that communicates with a server system to update the playlist ID and the NFC ID.

Figures 2A-2G are screenshots depicting a graphical user interface on a mobile phone loaded with music sharing software. The music sharing software can be used on a variety of operating systems with modifications consistent with the specific operating system. Such modifications are known to those skilled in the art. Therefore, the music sharing software is provided in a manner that guides the skilled person in implementing the required and optional functions with additional reference to the accompanying drawings. As a further non-limiting guide, the system of the present invention can be used with Java, PHP, Python, and SQL.

While a technician can connect music playing software to near field communication software already on an NFC-enabled device, music sharing software itself includes near field communication software for improved integration with the system and method. NFC programming is a set of codes that receives a data file from an NFC chip and writes the data file to the NFC chip. Software applications are commercially available that generate NFC programming themselves and can therefore vary from application to application. To this end, these software applications can be used to generate NFC programming modules for specific operating systems.

In some embodiments, once the NFC chip is powered, the data encoded on the NFC chip is immediately discovered and the music sharing software unpacks the data. Those skilled in the art will appreciate that the differences in unpacking may depend on the programming of the NFC chip itself. Once unpacked, the music sharing software reads the unpacked data and performs a series of operations depending on the received data and whether the NFC ID and/or playlist ID is already stored in the NFC-enabled device and/or server system.

As shown in Figures 2A-2B, newly purchased NFC beads will not be considered to have been registered by music sharing software or server system. For this reason, the NFC chip must be activated or registered. When not recognized or if you wish to activate the NFC beads, the music sharing software displays a prompt in the form of an activation screen 202, as shown in Figure 2A. Activation or registration is completed by manually entering a purchase code, which is preferably supplied separately from the NFC beads themselves. The purchase code and NFC ID are transmitted to the server system and compared with a secure database in the server system. Once the purchase code and NFC ID are authenticated, the server system notifies the music sharing software loaded on the NFC-enabled device and allows the purchased music files to be downloaded to the long-term storage in the NFC-enabled device for playback at any time. As shown in Figure 2B, the music sharing software command graphical user interface displays a successful verification screen 204. In certain embodiments, the successful verification screen 204 will display a graphic corresponding to the purchased music file or playlist.

Once downloaded to the NFC-enabled device, the music file can be added to a library of music files, which allows the library to be arranged or sorted according to music file identifiers, such as artist, album, song, genre, and other identifiers known in electronic art. As shown in Figure 2C, once downloaded, the music player allows the music file to be played, and when the music file is played, the corresponding music file screen 206 is preferably displayed through a graphical user interface. The music player module contains conventional functions, such as play, stop, pause, fast forward, rewind, and others. In a preferred embodiment, the music files are provided in a format that prevents playback in different audio players.

As shown in the playlist generation screen 208 of Figure 2D, the music sharing software allows the user to select from all the music files in the library to generate a playlist. Identifying files to add to the playlist can be performed by selecting or deselecting the indicators for each music file as shown in Figure 2D throughout the music library. Once all desired songs have been selected, the user can change the order of the music files as needed and can select the option to generate the playlist when ready. Generating the playlist includes: identifying each song and optionally identifying its order; and compiling the data into a database file. The database can be populated by placing files in a data file according to a predetermined format. In some embodiments, the generated database file is assigned to the playlist as a playlist ID. This method allows the playlist to be later decoded directly from the playlist ID itself for sharing via a server system, such as a music file. In other embodiments, a random data string generator generates a data string of numbers, letters, and symbols, which provides a shorter data string and may therefore be preferred when generating large playlists.

Once the playlist ID is assigned to the playlist, the software can prompt the user to synchronize the NFC bead, thereby programming the playlist ID to the NFC bead. An example of a synchronization screen 210 is shown in FIG2E . When synchronizing to the NFC bead, the NFC ID corresponding to the NFC bead and the playlist ID is communicated to the server system, where the NFC ID can be stored in a database for later authentication of the streamed music file. The music sharing software can also upload a playlist database file separate from the playlist ID to further identify the music files assigned to the playlist ID.

The music sharing software also allows for sharing music files via social media platforms, such as shown in the social media screen 212 in FIG. 2F . Non-limiting examples include email programs, messenger programs, business networking programs, social networking programs, and others. In some embodiments, a playlist is generated and provided to a server system, which generates an access code that allows for temporary streaming or playback of the music files without downloading them to the long-term storage of a subsequent NFC-enabled device. The access code can then be transmitted to the social media platform via the music sharing software or the server system.

As shown in FIG. 2G , the music sharing software in conjunction with the server system allows music files to be previewed and then temporarily shared or purchased.

Example 1: Purchasing music files using NFC technology

1A-B , in the invention disclosed herein, a method for transferring music files to an initial purchaser using near field communication (NFC) is provided. The exemplary method includes: providing an NFC identifier (ID) unique to the NFC chip 102 to the NFC chip 102; assigning a set of music files to NFC ID and purchase code pairs, wherein the NFC ID and purchase code pairs are stored on a server system 114 configured to access and transfer the music files; reading the NFC ID from the NFC chip 102 using an NFC-enabled device 112a loaded with music sharing software configured to play the music files; entering the purchase code into the NFC-enabled device 112a; authenticating the NFC ID and purchase code pair received by the NFC-enabled device 112a through communication with the server system 114; and, if authenticated, registering the music files to a user of the NFC-enabled device 112a. Once a music file is registered, the user is allowed to download the music file to the long-term storage of the NFC-enabled device 112a for playback at any time, or can stream or play the music file by saving the music file to the registered account and streaming or playing the music file from the account. In addition, once registered, the user can designate other users to temporarily stream or play the music file without requiring permission to download to the long-term storage, which is regulated and monitored by the server system 114.

Figure 3 is a flow chart illustrating an exemplary embodiment of purchasing a music file using an NFC-enabled device by using an encapsulated NFC chip before sharing. In this example, the encapsulated NFC chip is embodied as an NFC bead having a spherical polymer shell surrounding the NFC chip, and the NFC-enabled device is a mobile phone.

Step 302 represents the initial purchase of NFC beads, which is often carried out by music retailers. The beads are preloaded with an NFC ID for identification, and the purchase code is provided separately in the packaging. In step 304, the beads are touched to the buyer's mobile phone to start communication with the music sharing software. If the mobile phone already has music sharing software, the software starts. If the music sharing software is not yet installed on the mobile phone, the mobile phone is directed to a website via a web browser, where the music sharing software can be downloaded to the mobile phone and then opened. A series of conditional decisions to realize step 304 can be implemented by executable code consistent with the current method for opening and retrieving software programs used in the software industry. For example, executable programming can guide a browser to various suppliers that provide software applications, such as Google Play or Apple App Store. It is entirely within the capabilities of those skilled in the art to which the invention pertains to guiding a browser to such websites and downloading software applications.

In step 306, the music sharing software identifies the NFC ID as unregistered and therefore requires the use of a graphical user interface to enter a purchase code. Verification registration can be automatically performed by communication with the system server or can be manually instructed. In step 308, the server authenticates the NFC ID and purchase code by comparing their respective data strings with a database of valid combinations. The server queries its database and, if the NFC ID and purchase code match, considers the combination to be trustworthy, and the server approves the download of the music file. The buyer can subsequently see a verification message on the graphical user interface. If the combination of NFC ID and purchase code is not found in the database, the music file is not downloaded. In some embodiments, if the combination of NFC ID and purchase code is not found in the database, the option of purchasing the music file is provided to the user.

In step 310, after authenticating the NFC ID and purchase code, the purchased music files are downloaded to the user's NFC-enabled mobile phone for long-term storage. In some embodiments, the music files are stored on the mobile phone, and a copy is saved to the user's online account, which can be created using methods well known in the art. In alternative embodiments, the music is not downloaded to the user's mobile phone, but rather assigned to the user's online account and linked in a manner that allows unlimited streaming from the music storage location to the mobile phone. This streaming option allows the user to conserve storage space on the mobile phone via fast internet.

In step 312, the user's unique user ID, the music ID associated with the music files purchased by the user, the device ID unique to the mobile phone, and the NFC ID associated with the specific NFC bead are stored as a data set in a database accessible by the server, which can be used as a backup function or for sharing applications. The purchase code can also be saved. By storing the user ID, the music sharing software and server system can interactively track the ownership of music files, devices, and NFC chips. By storing the music ID, the music sharing software and server system can maintain a list of purchased or owned music files. By storing the device ID, the music sharing software and server system can authenticate the user's mobile phone and all other devices that play the user's music files, such as tablet computers, laptops, network media players (DVD players, TVs), and other devices. By storing the NFC ID, the music sharing software and server system can track the exchange, sharing, and transfer of music files between NFC-enabled devices. The identifier itself is typically in the form of a data string with multiple letters, numbers, and symbols. In some embodiments, the purchase code is saved to facilitate the transfer of ownership of one or more music files.

In step 314, the music sharing software starts the music player and the playlist is played. In a preferred embodiment, the music files are provided in encrypted form or with an extension that prevents playback in other media players. As with other media players, the music sharing software allows the music files to be played in a pre-arranged order, a random or shuffled order, and allows fast forward, rewind, skip forward and backward, pause, stop, sample, and other functions found in audio media players.

Example 2: Previewing music via social media

Among the features provided in music sharing software is the ability to temporarily share preview files by providing a link or portal to the music files for previewing without providing permission to download the music files to long-term storage. An overview of an exemplary method is summarized in FIG4. For example, once a purchaser has purchased music files, a playlist can be generated from one or more music files to share with subsequent users of the music sharing software.

In some embodiments, the preview music file is shorter than the original music file, and the property defining the length can be updated by the server. In some embodiments, the preview music file is played or streamed via remote access and is therefore only allowed when the receiving user is connected to the Internet. Preferably, access to the preview music file shared by subsequent users will not be possible offline and will be temporary.

In step 402, a playlist is generated from one or more purchased music files. This can be accomplished on the user interface of the NFC-enabled device by navigating to the desired music file and selecting it for sharing. After this, the playlist is generated and a playlist ID is assigned. The user then executes a share command. The user also selects a platform to deliver playable temporary access to the music files, including email, text messaging, social media, and others.

The share command communicates the playlist ID to the server system, which generates an executable access link to a remote site that allows temporary playback of music files from the playlist.

In step 404, an executable access link is sent to the subsequent user using the selected platform. The access link may be in HTTP format or another link format used to connect the subsequent NFC-enabled device to the server, for example, through a secure portal, for playing the music file via the Internet.

In step 406, subsequent users receive the link and are able to play the music file subject to time limits or repetition limits regulated by the system server.

Example 3: Sharing a music playlist using NFC technology

1A-B , the present invention provides a method for sharing a playlist generated from purchased music files by pairing and authenticating an NFC ID with a playlist ID. As an example, the present invention provides a method for sharing a music playlist using near field communication (NFC), the method comprising: assigning a playlist identifier (playlist ID) to a playlist of music files; receiving an NFC identifier (NFC ID) from an NFC chip 102 using an NFC-enabled device 112a; programming the playlist ID to the NFC chip 102 using the NFC-enabled device 112a; storing the NFC ID and the playlist ID to a server system 114, wherein the server system 114 has accessible copies of the music files encoded in the playlist ID for playback or streaming; receiving the NFC ID and the playlist ID from the NFC chip 102 using a subsequent NFC-enabled device 112b; authenticating the received NFC ID and playlist ID on the subsequent NFC-enabled device 112b with the server system 114; and, if authenticated, playing or streaming the copy of the music files via the subsequent NFC-enabled device 112b. The playlist ID may be generated and assigned by the NFC-enabled device 112a for programming to the NFC chip 102 and for transmission to the server system 114. Alternatively, the server system may generate and assign the playlist ID and then provide the playlist ID to the NFC-enabled device 112a for programming to the NFC chip 102.

FIG5 provides an example where a packaged NFC chip embodied as an NFC bead is shared between users via an NFC-enabled device embodied as a mobile phone to temporarily share a playlist of music files.

In step 502, a playlist is generated and the assigned playlist ID is saved to the bead using the music sharing software. The playlist can be the same as a pre-purchased playlist, or it can be a custom playlist defined by assigning one or more songs to the playlist. The sharing program prompts the user to tap the NFC bead against their mobile phone and confirm that the playlist ID has been programmed to the NFC bead. Before or during this process, the NFC ID associated with the NFC bead is recorded by the music sharing software and paired with the playlist ID. The NFC ID and playlist ID are then uploaded to the server system.

In some embodiments, the playlist ID is a data file that identifies each of the music files contained in the playlist. This may be performed by grouping a series of music track identifiers (track IDs), also referred to herein as "music IDs" or "music file IDs," into a data string or data matrix, wherein each track ID is associated with a music file and is provided in a readable order that conforms to the order in the playlist. The playlist ID and NFC ID are transmitted to the server system for entry into a database where they are retained for later retrieval upon authentication queries. Preferably, the server system has access to authorized copies of individual music files through separate licensing agreements so that the music files themselves do not need to be uploaded to the server system via the mobile phone. Because the playlist ID can identify the music files within the playlist, the server system can simply retrieve the authorized copies for playback or streaming after authenticating the NFC ID and playlist ID. Although not preferred, the present invention also encompasses embodiments in which the music files themselves are uploaded to the server system

In an alternative embodiment, the playlist ID is a data string generated by a random data string generator program in the music sharing software, and the program generates a random string with a mixture of numbers, letters and symbols. In addition, the music sharing software stores the track identifier (track ID) of the series in a playlist data file, wherein each track ID is associated with a music file and is provided in a readable order that meets the order in the playlist. The playlist ID, NFC ID and playlist data file are transmitted to a server system for input into a database, wherein the playlist ID and NFC ID are retained for authentication query later, and the playlist data file is retained for identifying the track ID so that the music file is played after authentication. Preferably, the server system has access to the authorized copy of the individual music file through a separate license agreement so that the music file itself does not need to be uploaded to the server system by a mobile phone. Because the playlist ID can identify the music file in the playlist, the server system can simply retrieve the authorized copy for playing after NFC ID and playlist ID authentication. Although not preferred, the present invention also encompasses embodiments in which the music file itself is uploaded to the server system.

In step 504, the bead is lightly touched to the subsequent user's mobile phone to initiate near-field communication with the bead, and in step 506, the music sharing software on the subsequent user's mobile phone reads the received file to begin the authentication process. This can be performed automatically through near-field communication between the NFC bead and the mobile phone, or the music sharing software can be started before the near-field communication by separately starting the music sharing software using the mobile phone's graphical user interface. Naturally, if the music sharing software is not yet installed on the mobile phone, the browser can be directed to a website for downloading the music sharing software to the mobile phone. This series of conditional decisions can be implemented by executable code preloaded on the bead, or it can be implemented by code provided on the mobile device as known in the art to which the present invention belongs.

In step 508, the music sharing software retrieves both the NFC ID and the playlist ID and transmits them to the server system for authentication. The server system compares the NFC ID and the playlist ID with a database of security codes for authentication. If authenticated, the playlist is allowed to be temporarily streamed on the mobile phone, as provided in step 510.

The step of streaming or playing the music files may be performed consistently according to an embodiment in which the playlist is initially provided by a server and according to the music sharing software.

In an embodiment, where a playlist ID is a data file identifying each of the music files contained in the playlist, the track IDs associated with the music files can be parsed from the playlist ID on the server system, a list of available music files can be transferred to the mobile phone for display on an interactive user interface for selection, and once selected, the corresponding music file can be retrieved by the server system and streamed in accordance with any licensing agreement. Alternatively, the music sharing software can parse the track ID from the playlist ID retrieved from the NFC bead, present the list of track IDs to the user via an optional user interface, and once selected, transmit a command to the server system for playback or streaming without downloading the music file to long-term storage.

In an embodiment where the playlist ID is a data string generated from a random data string generator program within the music sharing software, a playlist data file previously provided to the server system is parsed for available track IDs, and a list of track IDs is provided to the mobile phone for display on an interactive user interface for selection, and once selected, the corresponding music file can be retrieved by the server system and streamed in accordance with any licensing agreement.

In some embodiments, access to playable music is limited to a predetermined time, such as a predetermined number of hours. Regulating access by hours can be implemented by providing a timer program within the server system that times access to playable music and is configured to terminate access once the predetermined time limit is met. Non-limiting examples of such time limits include a time limit selected from the group consisting of: 1 hour, 2 hours, 3 hours, 4 hours, 5 hours, 6 hours, 7 hours, 8 hours, 9 hours, 10 hours, 12 hours, 18 hours, 24 hours, 36 hours, 48 hours, 72 hours, 96 hours, 120 hours, 144 hours, 168 hours, and others. In other embodiments, access to playable music is limited to a predetermined number of plays, wherein the server system counts the number of repetitions of one or more music files and compares the count to the predetermined limit. Non-limiting examples of such repetitions include 1-5 repetitions per music file or 1-5 repetitions of a playlist. In another embodiment, access to playable music is limited to the number of times the same mobile phone contacts the server system to initiate music playback. Non-limiting examples of such repetition numbers include 1-5 repetitions of contacting the server system.

In step 512, the user is provided with an option to purchase the music files in the playlist. This can be accomplished using conventional shopping carts and checkout programming on a server system as is known in the online retail field. In some embodiments, the purchase option is interfaced with another music retailer.

Example 4: Using NFC technology to transfer ownership of music files from the original purchaser to subsequent users

1A-B , in some embodiments, the present invention uses NFC technology and a purchase code to provide for a transfer of ownership of music originally associated with an NFC bead 110. In an exemplary method, the present invention includes a method for transferring music files between near field communication (NFC) enabled devices 112a, 112b, the method comprising: providing a library of music files to the NFC enabled device 112a; registering an NFC ID, a purchase code, and the music files from the library of music files with a user account on a server system 114; reading the NFC ID from the NFC chip 102 using a subsequent NFC enabled device 112b; entering the purchase code into the subsequent NFC enabled device 112b without using the NFC chip 102; authenticating the NFC ID and purchase code on the server system 114; requesting permission to transfer the music files from the user account to a different user account; and, if approved, deleting the music files from the library of music files; registering the purchase code and the music files with the different user account; and downloading the music files to the subsequent NFC enabled device 112b. Another exemplary method is shown in FIG. 6 , which transfers ownership of a music file after an initial purchase and registration of a bead ID, purchase code, and user ID.

In step 602, the original purchaser of the music file transfers the NFC bead to the subsequent user. In addition, the initial purchaser provides the subsequent user with the original purchase code or a newly generated purchase code. The purchase code is preferably not loaded onto the NFC bead, but instead provided separately.

In step 604, near-field communication (NFC) between the NFC bead and the mobile phone is initiated when the NFC bead is nearly touching the mobile phone. To do this, a subsequent user touches the NFC bead against the subsequent mobile phone. If the mobile phone already has music sharing software, the software is activated. If the music sharing software is not already installed on the mobile phone, the browser is directed to a website where the music sharing software can be downloaded to the mobile phone and then activated, as in the previous embodiment. Alternatively, the music sharing software can be activated and then near-field communication with the NFC bead is initiated. Near-field communication transfers the bead ID to the mobile phone.

In step 606, the subsequent user chooses to enter a purchase code associated with the bead ID. In some embodiments, this is accomplished by selecting an option in the software to purchase the music file associated with the bead ID, which prompts the user to enter the purchase code. In other embodiments, the bead ID is transmitted to a server system, and in response, the server system, having been notified by the original purchaser that the music file will be transferred, prompts the subsequent user for the purchase code.

In step 608, the bead ID and purchase code are transmitted to the server system for authentication. The server system queries its database, and if the bead ID and purchase code are found in the database, a request is sent from the server system to the original purchaser to verify or authenticate the transfer of the music file, as shown in step 610. This can be achieved by sending an authorization request to the music sharing software on the original purchaser's mobile phone to verify the intention to transfer the music file to the subsequent user. The transfer means that the original purchaser surrenders the ability to play the music file. To ensure that there is only one registered owner at a time, the music file or the ability to play the music file on the original purchaser's NFC-enabled device or the original purchaser's account at any time can be revoked or deleted before the transfer of ownership of the music file to the new owner is complete. In some embodiments, after the transfer, the purchaser can stream preview files associated with the music file. In some embodiments, additional security information is required to complete the music file transfer to prevent the music file from being stolen from a stolen phone, such as additional security issues known in the art. On the other hand, if the NFC bead and purchase code are lost or stolen from the original purchaser, the authorization request allows the original purchaser to take subsequent actions and then discover the lost NFC bead.

In step 612, the music file is downloaded to the subsequent user's mobile phone.

In step 614, the transferred music file is deleted from the original purchaser's available music library. In some cases, the original purchaser can preview the music file by playing a shortened version from the server system. The music file can be deleted from the original purchaser's phone before the new owner is allowed to play it at any time to ensure that there is always at most one owner.

Example 6: Transferring ownership of a playlist to a subsequent user using NFC technology and a transfer code

1A-B , the present invention also provides a method for transferring ownership of a customized playlist using NFC technology and a transfer code. In an exemplary embodiment, the present invention provides a method for transferring music files between near field communication (NFC) enabled devices 112a, 112b, the method comprising: providing an NFC enabled device 112a loaded with a library of music files and an NFC chip 102 encoded with an NFC identifier (NFC ID); generating a playlist of music files from the library of music files; assigning the playlist ID, a transfer code, and the NFC identifier to the playlist on a server system 114; saving the playlist ID to the NFC chip 102; receiving the playlist ID from the NFC chip 102 using a subsequent NFC enabled device 112b; entering the transfer code into the subsequent NFC enabled device 112b; authenticating the NFC ID, playlist ID, and transfer code on the server system 114; sending a permission request from the server system 114 to the NFC enabled device 112a to confirm the transfer of the music file to the subsequent user; and, if approved, deleting the music file from the library of music files; and registering the music file with the subsequent user account, wherein the registration updates ownership of the music file. A related exemplary embodiment is shown in Figure 7, which uses NFC technology to transfer a customized playlist. The packaged NFC chip is embodied as an NFC bead, and the NFC-enabled device is embodied as a mobile phone.

In step 702, a batch of music files are grouped to form a playlist, and a playlist data file is generated that provides identification and order of the music files. The playlist ID is generated using a random string generator. The original purchaser, who has the option to share or transfer entire ownership of the playlist, chooses to transfer. The music sharing software generates a transfer code to initiate the transfer. The playlist ID is loaded onto the NFC bead. The playlist ID, bead ID, playlist data file, and transfer code are uploaded to the server system.

In step 704, the original purchaser of the music files physically transfers the NFC bead with the playlist ID programmed into it to the subsequent user and provides the user with a transfer code. The transfer code is a code that allows a set of files to be downloaded onto an NFC-enabled device. Without the transfer code, the music sharing software can only ultimately stream the playlist or purchase the music files through the music sharing software. Without the transfer code, the complete music files will not be downloaded.

In step 706, near-field communication between the NFC bead and the mobile phone is initiated by tapping the NFC bead against the mobile phone. If the mobile phone already has music sharing software, the software is activated. If the music sharing software is not yet installed on the mobile phone, the mobile phone is directed to a website via a web browser, where the music sharing software can be downloaded and then opened on the mobile phone. The series of conditional decisions that implement the above content can be implemented by executable code preloaded on the NFC chip of the bead, or it can be implemented by code displayed on the mobile phone, which is consistent with the method used in the software industry to open and retrieve software programs. Alternatively, the music sharing software can be launched before activating near-field communication with the NFC bead.

In step 708, the music sharing software prompts the user to enter the transfer code associated with the NFC bead and playlist ID. In some embodiments, the prompt is initiated after the NFC ID and playlist ID are transferred to the server system. During the verification process, the server system reveals that the transfer code exists in the database, thereby indicating that the music file will be transferred. In other embodiments, the file transfer option is a menu option in the music sharing software, and the user can select it from the menu option.

In step 710, the transfer code is provided to the server for authentication. The server queries its database, and if bead ID, playlist code and the transfer code of transfer code matching database, the original purchaser is notified of the transfer request. In step 712, a request is sent from the server system to the original purchaser, with the transfer of verification or authentication music file, as shown in step 712. This can be achieved in the following way: authorization request is sent to the music sharing software on the mobile phone of the original purchaser, with the intention that the music file is transferred to subsequent users, to verify. The meaning of transfer is that the original purchaser surrenders the ability of playing the transferred music file from playlist. In certain embodiments, after the transfer, the purchaser can stream the preview file associated with the music file. In certain embodiments, additional security information is needed to complete the music file transfer, to prevent that the music file from being stolen from the stolen phone, such as, additional security issues as known in the art.

After granting permission to transfer the music file, the server system allows the music file to be downloaded to the mobile phone, as outlined in step 714 .

In step 716, the transferred music file is deleted from the original purchaser's available music library. In some cases, the original purchaser can preview the music file by playing a shortened version from the server system.

Example 7: Retrieving a Lost Purchase Code

1A-B , a situation may arise where a user who is the owner of an NFC bead 110 loses the purchase code associated with the bead 110, which in some embodiments may prevent downloading of music files associated with the NFC bead 110. In some embodiments, the loss of the purchase code may prevent the transfer of ownership of the NFC bead 110 and/or its associated music tracks to a subsequent NFC-enabled device 112 b or user. The flowchart in FIG8 illustrates an example of a process a user may go through to recover a lost purchase code.

In step 802 of Figure 6, the user contacts customer service about the lost purchase code. This step can be accomplished by various methods, such as through a messaging or email feature within the music sharing software, by phone, email, online chat, text messaging, in person, or other methods.

In step 804, the purchaser provides proof of purchase. Proof of purchase may be in the form of a receipt number presented on a receipt issued with the purchase of the beads. In such an embodiment, the receipt number will be stored in a database on the server system. In step 806, each time a customer service representative ("Admin") enters a receipt number into the database, the server system will check to ensure that the receipt number has not been previously reported to prevent fraud.

In some embodiments, the proof of purchase is in the form of a bead ID. In step 806, the customer service representative instructs the user on how to locate the bead ID. If the user has not yet activated the NFC bead, the user will be able to find the bead ID on the product packaging. If the user has activated the NFC bead, the bead ID can be retrieved through the music sharing software using a pre-stored additional security question.

In step 808, the customer service representative deactivates the original purchase code and/or bead ID and generates a new purchase code and/or bead ID. These changes can be accomplished by the representative directly accessing the database stored on the system server and manually changing the values. The process can also be performed indirectly through a mechanism where the representative checks for inadvertent errors. Optionally, a backup copy of the previous database values can be generated.

In step 810, the server stops access to the music file by any previous user who may have downloaded the track or linked to the track via the previous purchase code and/or user ID. This step is used to cut off access by someone who may have gained unauthorized access to the purchase code and/or user ID and transferred ownership of the music file without authorization.

Those skilled in the art will appreciate that, in light of the above teachings, many modifications and variations of the described examples and embodiments are possible. The disclosed examples and embodiments are provided for illustrative purposes only. Other alternative embodiments may include some or all of the features disclosed herein. Therefore, it is intended to cover all such modifications and alternative embodiments that may fall within the true scope of the present invention.

Claims (14)

1. A method for transferring music files between Near Field Communication (NFC) enabled devices, the method comprising: a) Provide a library of music files to NFC-enabled devices; b) Register the NFC ID, purchase code, and music files from the music file library on the server system to the user account; c) Read the NFC ID from the NFC chip using a subsequent NFC-enabled device; d) Without using the NFC chip, enter the purchase code into the subsequent NFC-enabled device; e) Authenticate the NFC ID and purchase code on the server system; f) Request permission to transfer the music files from the user account to a different user account; and if approved, g) Delete the music file from the music file's database; h) Register the purchase code and music file to the different user accounts; and optionally i) Download the music file to the subsequently NFC-enabled device. 2. The method of claim 1, wherein the method further comprises: providing an option within the music file library to stream copies of deleted music files. 3. The method of claim 2, wherein the optional option is displayed differently from the music file owned by the user, wherein a first display feature characterizes the music file as available for playback at any time, and a second display feature characterizes the copy of the deleted music file as available for temporary streaming. 4. The method of claim 1, wherein the method further comprises: providing an optional option to repurchase a copy of the deleted music file via the server system using the NFC-enabled device. 5. The method of claim 1, wherein the NFC chip is encapsulated in a polymer. 6. A method for transferring music files between Near Field Communication (NFC) enabled devices, the method comprising: a) Provide an NFC-enabled device loaded with a library of music files and an NFC chip encoded with an NFC identifier (NFC ID); b) Generate a playlist of music files from the music file library; c) Assign the playlist ID, transfer code, and NFC identifier to the playlist on the server system; d) Save the playlist ID to the NFC chip; e) Receive the playlist ID from the NFC chip using a subsequent NFC-enabled device and near-field communication; f) Input the transfer code into the subsequent NFC-enabled device; g) Authenticate the NFC ID, playlist ID, and transfer code on the server system; h) Send a permission request from the server system to the NFC-enabled device to confirm the transfer of the music file to the subsequent user; and if approved, i) Delete the music file from the music file's database; and j) Registering the music file to a subsequent user's account, wherein the registration updates the ownership of the music file. 7. The method of claim 6, wherein the method further comprises: providing an option within the music file library to stream a copy of the deleted music file without downloading the music file to long-term storage. 8. The method of claim 7, wherein the optional option is displayed differently from the music file owned by the user, wherein a first display feature characterizes the music file as available for playback at any time, and a second display feature characterizes the copy of the deleted music file as available for temporary streaming. 9. The method of claim 6, wherein the method further comprises: providing an optional option to repurchase a copy of the deleted music file through the server system. 10. The method of claim 6, wherein the NFC chip is encapsulated in a polymer. 11. A method for transferring music files to the original purchaser using Near Field Communication (NFC), the method comprising: a) Provide the NFC chip with an NFC identifier (ID) unique to the NFC chip. b) Assign a set of music files to NFC ID and purchase code pairs, wherein the NFC ID and purchase code pairs are stored in a server system configured to access and transfer the music files; c) Using an NFC-enabled device, the NFC ID is read from the NFC chip, and the NFC-enabled device is loaded with music sharing software configured to play the music file; d) Enter the purchase code into the NFC-enabled device; e) Authenticate the NFC ID and purchase code pair received by the NFC-enabled device by communicating with the server system; and if authenticated... f) Registering the music file with a user of the NFC-enabled device, wherein the user is permitted to play the music file on the NFC-enabled device, and optionally downloading the music file to the NFC-enabled device for playback at any time. 12. The method of claim 11, wherein the NFC chip is encapsulated in a polymer. 13. The method of claim 11, wherein the purchase code does not utilize near-field technology for communication. 14. The method of claim 11, wherein, after the step of inputting the purchase code into the NFC-enabled device, the method further comprises pairing a device ID unique to the NFC-enabled device with the NFC ID and the purchase code in the server system.