Abstract:
A method for incentivizing sharing of a software product through awarding incentive points utilizing unique identifiers including removable storage identification, user console identification and user identification. The granting of access permissions and the awarding of incentive points are facilitated through a host server.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS  
       [0001]     This application is a continuation application and claims the priority benefit of U.S. patent application Ser. No. 09/894,182 filed Jun. 28, 2001, which claims the priority benefit of U.S. provisional patent application No. 60/270,235 filed Feb. 20, 2001. This application is related to U.S. patent application Ser. No. 09/894,793 filed Jun. 28, 2001. The disclosure of these applications is incorporated by reference. This application is also related to U.S. patent application Ser. No. 11/196,564 filed Aug. 2, 2005. 
     
    
     BACKGROUND OF THE INVENTION  
       [0002]     1. Field of the Invention  
         [0003]     This invention relates generally to electronic processing systems and more particularly to a point reward system utilizing unique disc identification to authorize access to disc storage media.  
         [0004]     2. Description of the Background Art  
         [0005]     Disc storage media, such as CD-ROM and DVD-ROM storage discs, are typical storage devices for commercially available software programs. For example, publishers and manufacturers of games for electronic gaming systems use read-only storage devices such as CD-ROM discs to distribute and sell their products. Discs may be passed and shared among users; however, there is no effective system in place to account for the potential multiple users of commercially available software products.  
         [0006]     Even though discs may be shared without any constraints, it may be that discs are shared only between small groups of users without widespread distribution among the entire user population. The software product is not widely shared, thereby forcing others to purchase their own copy. The software product does not achieve widespread advertising either, limiting the potential for a larger consumer base. For example, the publishers and distributors of game software would like their products advertised to a wide customer base as well as purchased by a wide customer base.  
         [0007]     A system that would offer an incentive to a user of a software product when this user shares the product with others, or when the user plays the product, is a concern of publishers and distributors of software products. A user may tire of a product on a disc, but instead of storing the disc away, maybe never to be seen again, the user is offered an incentive to share. Therefore, the user may be more inclined to share a software product with others. Such a system would (1) promote the product, (2) attract other users who may purchase more products in the future, and (3) offer all users incentives to purchase more products.  
       SUMMARY OF THE INVENTION  
       [0008]     An electronic processing system includes a disc storage medium with a permanently recorded disc identification, a user console with a set identification, a network, a host server managing a user database and a disc database, and multiple publisher servers managing multiple publisher databases. The user console may include a memory card or other removable storage medium, for storing data including the set identification and disc identification. Upon the first use of the console, the user is prompted for user information from the host server, and a user identification is assigned to the user. The user identification is functionally interchangeable with the set identification, and either may be used to identify the user.  
         [0009]     The user database includes a plurality of user tables, each user table including a user identification associated with a point account. The point account includes data relevant to the management of an incentive point system including the total points accumulated by the user identified with the associated user identification. The disc database includes a plurality of disc tables, each disc table including a disc identification with an associated owner consent data field and a sub-account. The owner consent data field includes data regarding other user access permissions. The sub-account includes data relevant to the management of an incentive point system including the points accumulated by the user identified with the associated disc identification. In addition, each publisher database includes a plurality of sub-accounts, where each sub-account is similar in content to the sub-account of the disc table. Instead of managing the sub-accounts by the host server, the sub-accounts may be managed by the publisher servers.  
         [0010]     In one embodiment, the user console connects to the host server and transmits the user identification and disc identification read from the disc storage medium to gain permission to execute the programs residing on the disc storage medium. In another embodiment, the user console connects to the host server and transmits the user identification and disc identification the first time a disc is booted by the user console, but after the initial access permission is granted, the disc identification and user identification are stored on the memory card to grant access permission for subsequent disc sessions.  
         [0011]     The host server compares the transmitted disc identification with the stored disc identifications associated with the transmitted user identification in the user table, and if necessary, with the stored disc identifications associated with the other user identifications. The host server awards incentive points to (1) the sub-account of a user of a first-time registered disc, (2) the sub-account of a previous user of a disc that has granted another user access permission, and (3) the sub-account of a user of a disc used previously by the same user.  
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0012]      FIG. 1  is a block diagram of one embodiment of an electronic processing system according to the invention;  
         [0013]      FIG. 2  is a diagram of one embodiment of the disc storage medium of  FIG. 1  according to the invention;  
         [0014]      FIG. 3A  shows one embodiment of the user database managed by the host server of  FIG. 1  according to the invention;  
         [0015]      FIG. 3B  shows one embodiment of the disc database managed by the host server of  FIG. 1  according to the invention;  
         [0016]      FIG. 4  shows one embodiment of the publisher database managed by the publisher server of  FIG. 1  according to the invention;  
         [0017]      FIG. 5  is a flowchart of method steps for acquiring disc access permission according to one embodiment of the invention; and  
         [0018]      FIG. 6  is a flowchart of method steps for granting disc access permission and awarding reward/incentive points according to one embodiment of the invention.  
     
    
     DETAILED DESCRIPTION  
       [0019]      FIG. 1  is a block diagram of one embodiment of an electronic processing system according to the invention. The processing system includes, but is not limited to, a disc storage medium (disc)  110 , a user console  115 , a set identification (ID)  120 , a network  125 , a host server  130 , a user database (DB)  135 , a disc database (DB)  140 , a plurality of publisher servers  145 , and a plurality of publisher databases (Pub. DB)  150 .  
         [0020]     The disc  110  is a read-only storage device such as a CD-ROM or a DVD-ROM. As will be discussed further below in conjunction with  FIG. 2 , a disc identification is stored on the disc  110  to uniquely identify the disc  110 .  
         [0021]     The user console  115  is an electronic device, such as an electronic gaming system, a general-purpose computer, or a set-top box, that may access the contents of the disc  110 . The user console  115  has an interface to the network  125 . The network  125  may be a local area network (LAN), a wide area network (WAN), a wireless network, a cable network, or the Internet. The Internet is a broad network of interconnected computers and servers allowing for the transmission and exchange of Internet Protocol (IP) data between users connected to the Internet through a network service provider. Examples of network service providers are the public switched telephone network, a cable service provider, or a satellite service provider.  
         [0022]     The user console  115  may be configured to access data from other removable storage media, such as memory cards, floppy discs, or hard disc drives.  
         [0023]     During a first use of the user console  115 , a user registers the user console  115  with the host server  130 . The user console  115  may be registered and identified by either a set ID  120  or a USER ID. The host server  130  stores the set ID  120 , the USER ID, or both in the user database  135 . As further discussed below in conjunction with  FIG. 6 , the first time user of the user console  115  will be prompted by the host server  130  to enter user information. This user information will be used to associate a USER ID with a user. In the preferred embodiment of the invention, the USER ID identifies users. However, the set ID  120  may be used instead of the USER ID to identify users.  
         [0024]     The host server  130  stores data in the user database  135  and the disc database  140 . The databases will be discussed in more detail below in conjunction with  FIGS. 3A-3B . In the preferred embodiment of the invention, the host server  130  has access to a plurality of publisher servers  145 . The publisher servers  145  manage sub-accounts associated with DISC UNIQUE IDs and stored in a plurality of publisher databases  150 . The publisher databases  150  will be discussed below in conjunction with  FIG. 4 .  
         [0025]      FIG. 2  is a diagram of one embodiment of the disc  110  according to the invention. The disc  110  includes, but is not limited to, a data access area  210 , a DISC UNIQUE ID address  220 , and a DISC UNIQUE ID  230 . The disc  110  has a data access area  210  delineated by an inner and outer radius. Data is typically recorded within the data access area  210 . The data may include software programs, video data, audio data, or any other type of stored content. Although  FIG. 2  shows the DISC UNIQUE ID address  220  and the DISC UNIQUE ID  230  recorded within the data access area  210 , either can be recorded outside of the data access area  210 .  
         [0026]     The DISC UNIQUE ID address  220  contains the disc address of the DISC UNIQUE ID  230 . The DISC UNIQUE ID  230  uniquely identifies the disc  110 . The contents of the disc  110  cannot be played on the user console  115  or other devices without access permission for the disc  110 . Access instructions are sent to the user console  115  from the host server  130  upon receipt of the DISC UNIQUE ID  230  and the USER ID by the host server  130  from the user console  115 . Access permission and incentive/reward point transactions will be discussed below in conjunction with  FIGS. 5-6 .  
         [0027]      FIG. 3A  shows one embodiment of the user database  135  of  FIG. 1  according to the invention. The user database  135  has a user table  310 , including user information and point account information. User information includes the USER ID and may also include, for example, user name, address, billing information, and user preferences. The point account information includes incentive and reward point information, such as the total point count and other data relevant to the management of the incentive and reward point system. The user table  310  may also include a plurality of DISC UNIQUE IDs that are associated with each USER ID. Each DISC UNIQUE ID has associated owner consent data. The owner consent data is a data field that contains information regarding the transfer of access permission to another user.  
         [0028]      FIG. 3B  shows one embodiment of the disc database  140  of  FIG. 1  according to the invention. The disc database  140  has a disc table  320  including disc information and sub-account information. The disc information includes the DISC UNIQUE ID accompanied by owner consent data and may also include, for example, title, publisher, type, date of purchase, and transfer charge. The disc table  320  may also contain a USER ID associated with each DISC UNIQUE ID. The transfer charge data field includes the payment amount due the user upon transfer of ownership to another user. The transfer charge data field may include other data relevant to charges incurred when ownership of a disc is transferred. The disc table  320  includes a sub-account associated with each DISC UNIQUE ID. The host server  130  manages the sub-accounts. The sub-account includes incentive and reward point information for each DISC UNIQUE ID, such as point count or other data relevant to the management of the incentive and reward point system.  
         [0029]      FIG. 4  shows one embodiment of the publisher database  150  of  FIG. 1  according to the invention. In addition to the host server  130  managing the sub-accounts stored in the disc database  140 , the publisher server  145  may manage sub-accounts that are subsequently stored in the publisher database  150 . The sub-accounts of the publisher database  150  include incentive and reward point information for each DISC UNIQUE ID, such as point count or other data relevant to the management of the incentive and reward point system. For example, sub-accounts of the publisher database  150  may include a plurality of DISC UNIQUE IDs with related reward and incentive point data for all discs manufactured by the publisher and registered by users. A user may have multiple sub-accounts with each publisher. The user may transfer points from the main point account of the user database  135  to any of the sub-accounts stored on the plurality of publisher databases  150  or the sub-account stored on the disc database  140 .  
         [0030]      FIG. 5  is a flowchart of method steps for a user to acquire access permission for a disc  110  on the user console  115 , according to one embodiment of the invention. First, in step  505 , the user console  115  reads basic data from the disc  110 . In step  510  the user console  115  determines if a DISC UNIQUE ID address  220  is stored on the disc  110 . If the DISC UNIQUE ID address  220  does not exist, then the method continues with step  560 , and the disc program is executed. However, if a DISC UNIQUE ID address  220  does exist, then, in step  515 , the user console  115  determines whether a DISC UNIQUE ID  230  is stored at the location given by the DISC UNIQUE ID address  220 . If there is no DISC UNIQUE ID  230  recorded, then disc program execution is stopped in step  520 . If there is a DISC UNIQUE ID  230  recorded, then, in step  525 , the DISC UNIQUE ID  230  is read by the user console  115 . In step  530 , the user console  115  determines if a memory card is present. The memory card is a removable storage device compatible with the user console  115  or other user consoles that may store data such as USER ID and DISC UNIQUE ID  230 .  
         [0031]     The  FIG. 5  embodiment shows two paths to gain access permission to the disc  110 . If a memory card is not present in user console  115 , then the DISC UNIQUE ID  230  and USER ID will be sent to the host server  130  every time the disc  110  is booted. If a memory card is present, then the DISC UNIQUE ID  230  and USER ID is only sent to the host server  130  the first time a user boots the disc  110 . When the same user boots the disc  110  on subsequent occasions, host server  130  access is not needed to access the disc  110 . Instead of sending the USER ID and DISC UNIQUE ID  230  to the host server  130  for access confirmation, the USER ID and DISC UNIQUE ID  230  stored on the memory card are used to confirm or deny access to the disc  110 .  
         [0032]     In step  530 , if the user console  115  determines that a memory card is not present, then, in step  535 , the user console  115  sends the DISC UNIQUE ID  230  to the host server  130 . In step  540 , the USER ID is sent to the host server  130 . In step  545 , access instructions regarding user authorization are generated and, if appropriate, an incentive point or reward point transaction is made and recorded in the point account and sub-account data fields in the user database  135 , disc database  140 , and publisher database  150 . Moreover, if necessary, disc ownership or changes in disc ownership is recorded in the appropriate data fields in the user database  135 , disc database  140 , and publisher database  150 . The details of step  545  will be discussed in more detail in conjunction with  FIG. 6 .  
         [0033]     In step  550 , the user console  115  receives from the host server  130  the access instructions, and in addition, point information for any incentive point or reward point transactions conducted. If access permission is granted, step  555 , then disc program execution can commence in step  560 . However, if access permission is not granted, disc program execution is stopped in step  520 . The details regarding access permission and access denial will be discussed below in conjunction with  FIG. 6 .  
         [0034]     Returning to step  530 , if the user console  115  determines that a memory card is present, then, in step  565 , the user console  115  determines whether the DISC UNIQUE ID  230  is recorded on the memory card. If the DISC UNIQUE ID  230  is stored on the memory card, then the host server  130  is not contacted and the disc program can be executed in step  560 . However, if the user console  115  determines that the DISC UNIQUE ID  230  is not stored on the memory card, then in step  535  the user console  115  sends the DISC UNIQUE ID  230  to the host server  130 . In step  540 , the user console  115  sends the USER ID to the host server  130 . In step  545 , the host server  130  generates user authorization and point transaction data. In step  550 , the user console  115  receives access instructions and point information from the host server  130 . In step  555 , if disc access permission is granted, the DISC UNIQUE ID  230  and USER ID are stored on the memory card in step  570  and then the disc program is executed in step  560 . Consequently, the next time the user boots up the disc  110  with the same memory card installed, the host server  130  does not need to be contacted for access permission.  
         [0035]      FIG. 6  is a flowchart of method steps for granting disc access permission and awarding reward/incentive points according to one embodiment of the invention. First, in step  605 , a network connection is established from the user console  115  to the host server  130 . Then, in step  610 , the host server  130  determines whether the user is a first time user. If the user is a first time user, then, in step  615 , the host server  130  prompts the user for initial user data. The user is then assigned a USER ID by host server  130 . If the user is not a first time user, then step  615  is skipped. In steps  620  and  625  the host server  130  receives the USER ID (or set ID) and DISC UNIQUE ID  230  from the user console  115 , respectively.  
         [0036]     In step  630 , the host server  130  accesses the user database  135  associated with the USER ID and determines if the received DISC UNIQUE ID  230  matches any of the DISC UNIQUE IDs in the user table  310 . If there is a match, then the disc  110  has been previously played by the user. Subsequently, in step  635 , incentive point information can be recorded by the host server  130  to the user&#39;s point accounts or sub-accounts in any of the databases  135 ,  140 , and  150 . Finally, in step  640 , access permission and incentive point information is sent to the user console  115 .  
         [0037]     Users can be awarded incentive points for playing a disc  110 . Incentive point schemes may be developed and implemented by the host server  130  or publisher servers  145 , and may depend, for example, on disc publication date, disc popularity, special promotional schemes, or user performance. In addition, as discussed further below, users can be awarded reward points for either purchase of a new disc or transfer of disc ownership to another user. The reward point system provides users incentives to purchase new discs or sell used discs to other users, thereby promoting a disc to a wider audience and developing a larger customer base. Reward points and incentive points are recorded by the host server  130  and publisher servers  145  to the user&#39;s point accounts and sub-accounts. Points have value, and may, for example, be redeemed for rebates on disc purchases, publisher promotional items, updated versions of discs or user consoles, or may be traded among users. The foregoing examples of point redemption are not inclusive, however, and points may be redeemed for other items as well.  
         [0038]     If the received DISC UNIQUE ID  230  does not match any of the DISC UNIQUE IDs in the user table  310  in step  630 , then in step  645  the host server  130  searches for the received DISC UNIQUE ID  230  in other user&#39;s user tables. If the host server  130  does not locate a match, then the disc  110  associated with the received DISC UNIQUE ID  230  has been purchased new by the user and never played. Therefore, in step  650 , the DISC UNIQUE ID  230  is recorded to the user table  310 . The DISC UNIQUE ID  230  may also be recorded in the disc table  320  in the disc database  140  or the publisher database  150 . The user may be granted reward points for purchase of the new disc. Reward points granted are recorded to the user point account or sub-accounts in the multiple databases  135 ,  140 , and  150  in step  655 . Finally, in step  640 , the host server  130  sends access permission and point information to the user console  115 .  
         [0039]     If, in step  645 , the host server  130  does match the received DISC UNIQUE ID  230  to a DISC UNIQUE ID in another user&#39;s user table, then another user owns the disc  110 . Therefore, in step  660 , the host server  130  searches the databases of the other user for owner consent data. If the other user has not granted access permission, then the user is denied access in step  665 . However, if the other user has granted access permission, then, in step  670 , the host server  130  deletes the DISC UNIQUE ID in the other user&#39;s user table and records the received DISC UNIQUE ID  230  to the user&#39;s user table  310 . The other user may store the content of the disc  110  to a hard disc drive before granting access permission. In step  675 , the host server  130  then records reward points to the other user&#39;s point account or sub-accounts stored in the multiple databases. Finally, in step  640 , the host server  130  sends the user console  115  access permission and point information.  
         [0040]     The invention has been explained above with reference to a preferred embodiment. Other embodiments will be apparent to those skilled in the art in light of this disclosure. For example, the present invention may readily be implemented using configurations other than those described in the preferred embodiment above. Additionally, the present invention may effectively be used in conjunction with systems other than the one described above as the preferred embodiment. Therefore, these and other variations upon the preferred embodiments are intended to be covered by the present invention, which is limited only by the appended claims.