JP2006215890A - Software licensing system and method - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a system and a method for licensing only a technology module registered by an end user, by licensing software by using an information center. <P>SOLUTION: The information center maintains registration information which can be used for accounting a software provider regarding the technology licensed to the end user. The system can be used for paying reward to a technology holder after the end user registered the technology module which is not licensed. Therefore, the system and method enable a software seller to reduce cost by licensing only the technology the end user actually uses. The information center can be used for tracking usage of software function to determine the popularity of specific technologies. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates generally to systems and methods for licensing software, and more particularly to systems and methods for licensing specific technical modules within a software product as needed.

  Personal computers are often sold with bundled software packages pre-installed on the computer. Similarly, computer peripherals are sold with bundled software packages that are available on bundled media such as DVDs, CD-ROMs, floppy disks, or other known portable media. The Alternatively, software used with a personal computer and computer peripherals may be downloaded from a remote server over a network. These software packages typically provide functionality used by end users with purchased computers or peripheral devices. For example, a DVD optical drive may be tangled with software used to play or record a DVD movie or data. Similarly, an optical scanner captures a scanned image, views it, processes the image, and bundles software to provide optical character recognition (OCR), ie a scanner shared by the same personal computer and It may be sold with software that allows the printer to be used as a copier. Similarly, personal computers may be sold with pre-installed antivirus software, software tools for viewing digital photos, video editing software, or operating system software.

  These bundled software products often include functionality that incorporates a portion of executable software that requests royalty payments from technology holders. Technologies used in a single software product may be developed and licensed by one or more technology holders. Software suppliers typically license intellectual property rights from each technology owner before selling the product to the end user. A license typically covers each copy of software sold. This licensing fee is incorporated into the cost of the software product and passed on to the end user. In the case of playback software used for playback of commercially produced DVD movies, this software is typically expensive per unit in relation to the licensed technology required to play certain content. With licensing fee. The cost of these licenses is passed on to the end user at the purchase price of the playback software or hardware linking the playback software. An example of such a licensed function is Dolby® digital audio decoding provided by Dolby Laboratories. In particular, a license for Dolby Digital technology is required within the DVD playback software used to decode DVD movies that incorporate this audio technology.

  However, the actual percentage of end users playing playback DVDs that require Dolby technology is less than 100%. The reason is that some users only play personal content while others may use the DVD drive only for data storage or other computing purposes. In addition, some users may not use their DVD drive at all. In the case of Dolby Digital Audio cited above, this technique is required for playback of commercial DVD discs using this technique. However, decoding techniques are not required to view many DVD movie libraries that do not use Dolby Digital technology. For these users, technology-related license fees are wasted.

  A prior art licensing system, such as that shown in FIG. 1A, interacts between end user 10 and software supplier 20. In the first example, the software supplier 20 provides the software product directly to the end user 10 in exchange for a reward from the end user 10. In this case, licensing fees for technologies such as Dolby Digital are charged by the software supplier 20 for each copy of software sold, regardless of the actual use by the end user 10 of the licensed technology. May be paid to holder 30. The technology holder 30 then provides a technology license for each copy of the software sold by the software supplier 20.

  In the context of bundled DVD player software, the prior art system shown in FIG. 1B licenses bundled software between end user 10, hardware supplier 40, software supplier 20, and technology holder 30. Do. The software supplier 20 provides the hardware supplier 40 with a license for a software product with unrestricted functionality in exchange for rewards. The end user 10 is provided with the software product 12 as bundled software included in a computer or computer peripheral device supplied by a computer or hardware supplier 40. Under the current state of the art, licensing fees for technologies such as Dolby Digital are charged to the software supplier 20 (and / or hardware supplier) regardless of the actual use by the end user 10 of the licensed technology. 40) to the technology holder 30. Accordingly, since the use of specific functions within a software product is not generally tracked, a license for a specific technology is required for each software product 12 sold that includes the specific technology. Thus, there is a discrepancy between the cost of the technology license (by the hardware or software supplier 20) and the actual request (by the end user 10), which is inconvenient for both the end user 10 and the software supplier 20. . For the end user 10, if the technology is not used, the money for the license is wasted. For software suppliers 20, the high cost of license fees reduces margins or is passed on to end users 10 at selling prices, which may reduce market share.

  Accordingly, there is a need in the industry for systems and methods that address the aforementioned shortcomings and inadequacies in licensing software.

  In accordance with one embodiment of the present invention, a method for licensing software on a computer hardware platform is provided. The software includes at least one function that is restricted to limited use. The method includes sending an activation request to a registration information center to activate a technology that must be registered in order to use the function. The method also includes collecting registration information related to the technology in a registration database in the registration information center. The method also includes receiving a communication that can remove a limited use restriction of functionality. Finally, the actual use of the technology is determined based on registration information collected in a registration database.

  Following further expansion of the previous process, the software developer may pay the technology owner based on the registration information collected in the registration database.

  Accordingly, one object of the present invention is to provide a company (eg, a personal computer or DVD drive manufacturer) that provides bundled software by paying only a technology license fee for a copy of the software that actually uses the technology. Is to reduce the cost of

  Another object of the present invention is to pay the technology holder for each copy of the software that actually uses the technology holder's technology to provide a clear understanding and support for the value of the technology in the market. .

  Another object of the present invention is to lower the price for the end user, which is necessary to meet the end user's requirements while the end user benefits from the reduced cost to the company providing the bundled software. Easy access to all technologies.

  Another object of the present invention is to allow software suppliers to add more value to companies that provide bundled software and to provide expanded opportunities for direct conversation with end users. is there.

  The present invention is responsive to end-user software requests or activations (between hardware supplier and software supplier, or between software supplier and technology holder, or hardware supplier and technology holder). It is broadly directed to new systems and methods for initiating financial payments or billing between two other businesses (such as between a business partner).

  2A-2E schematically illustrate some embodiments of the proposed effective software licensing system. In accordance with a broader aspect of the system, FIG. 2A illustrates a software licensing system that includes a first party (typically an end user 160), a second party (typically a software supplier 150), and a technology holder 120. FIG. 1 illustrates a first embodiment. In such a system, the second party 150 pays the technology holder 120 for a license associated with each copy of the software product 110 sold including the technology owned by the technology holder 120. The first party 160 has acquired the software product 110, which is fully licensed, but the software product 110 includes unregistered software features. Accordingly, neither the first party 160 nor the second party 150 is required to pay the technology holder 120 any further rewards for the software functions used. However, although a feature is licensed, certain software features are disabled until the first party 160 requests registration of the feature with the second party 150. Upon receiving the registration request, the second party 150 records the registration and enables the newly registered software by delivering a release mechanism to the first party 160. The second party 150 can use the registration information obtained from the first party 160 to determine which features of the software 110 are used more frequently. The second party 150 can determine which technologies to include in future software releases.

  FIG. 2B illustrates a broader aspect of the second embodiment in which a third party (generally a hardware supplier 170) provides the first party 160 with bundled software that includes functional limitations. Yes. The bundled software is manufactured by the second party 150, and the software incorporates technology that requires a license from the fourth party (generally the technology holder 120). The first party 160 requests registration of the unregistered function with the second party 150. Upon receiving the registration request, the second party 150 records the registration and enables the newly registered software by delivering a release mechanism to the first party 160. Finally, the second party 150 pays the fourth party 120 for a license for the actual technology used by the first party 160. Compared to FIG. 2A, the system of FIG. 2B pays the fourth party 120 only when the end user 160 registers a technology owned by the fourth party 120.

  FIG. 2C illustrates a broader aspect of the third embodiment, in which a third party 170 provides the first party 160 with bundled software 110 that includes functional limitations. Bundled software 110 is manufactured by second party 150, and software 110 incorporates technology that requires a license from fourth party 120. The first party 160 issues a request to register unregistered functions with the second party 150. Upon receiving the registration request, the second party 150 records the registration and enables the newly registered software by delivering a release mechanism to the first party 160. The second party 150 pays the fourth party 120 for the actual technology used by the first party 160. Finally, the third party 170 pays the second party 150 for the actual technology used by the first party 160.

  FIG. 2D illustrates a broader aspect of the fourth embodiment, where a third party 170 provides the first party 160 with bundled software 110 that includes functional limitations. Bundled software 110 is manufactured by second party 150, and software 110 incorporates technology that requires a license from fourth party 120. The first party 160 issues a request to register unregistered functions with the second party 150. Upon receiving the registration request, the second party 150 records the registration and enables the newly registered software by delivering a release mechanism to the first party 160. Finally, the third party 170 may pay the fourth party 120 for the actual technology used by the first party 160. Accordingly, the fourth party 120 can deliver the license to the third party 170.

  FIG. 2E illustrates a broader aspect of the fifth embodiment, in which a third party 170 provides the first party 160 with bundled software 110 that includes functional limitations. The bundled software is manufactured by the second party 150 and the software incorporates technology that requires a license from the fourth party 120. The first party 160 issues a request to register unregistered functions with the third party 170. Upon receipt of the registration request, the third party 170 records the registration and enables the newly registered software by delivering a release mechanism to the first party 160. Finally, the third party 170 pays the fourth party 120 for the actual technology used by the first party 160. Accordingly, the fourth party 120 delivers the license to the third party 170.

  It will be appreciated that there are many obvious variations of the previous embodiments, and these variations are intended to be included within the scope and spirit of the broader aspects of the present invention. The system allows the intermediate party between the end user and the technology holder (eg, a second or third party) to pay the technology holder a licensing fee based on the actual use of the technology by the end user. Designed. The system's logistics should be exchanged, such as which party delivers the software, which party tracks registration, which party provides the release mechanism to the end user, and which party pays the technology holder Which remains within the scope of the present invention. This concept reflects an improvement from the prior art system, which relies on the intermediate party paying the technology holder for a full license for each copy of the software sold. Similarly, the system is identified from prior art systems that require the end user to pay for additional functionality.

  FIG. 3 illustrates a broader aspect of a method for implementing a system such as that shown in FIGS. First, protected software with limited functionality is provided to the first party (step 200). The first party may be an end user who receives software, such as entangled with a computer system. In step 210, the first party invokes a software function in the protected software. Limited functions, such as functions including DVD playback using Dolby Digital decoding, require registration. Accordingly, in step 220, the software determines whether registration is required to perform the function. If the function does not require registration (“NO” state), as represented by step 230, the user may perform the function without performing another action. If the function requires registration (“YES” state), the software is registered with the second or third party (step 240). For example, the second or third party may be a hardware supplier or a software supplier. In step 250, the software determines whether payment is required to license the newly registered function. If payment is not required (“NO” state), as in the system of FIG. 2A, the first party may execute the newly registered software (step 230). If payment is required ("YES" state), registration initiates payment from the second or third party to the fourth party (steps 270 and 280). For example, a hardware or software supplier may pay a technology holder for a registered technology. Similarly, registration may initiate payment from the second party to the third party (step 260). For example, a hardware supplier may pay a software supplier for a registered technology. Depending on the configuration, those skilled in the art will appreciate that even though the first party is authorized to run the software immediately, payment may actually be made at a later time.

  Referring back to FIG. 2B, by way of a more specific example, the system may include software provided to the computer system 100, or software entrapped with computer peripherals, only for the technology required by the end user 160. Can be licensed to For example, as a way to reduce useless license payments, software that plays DVD media has a limited function, in particular, removes some technologies related to licensing fees and allows hardware suppliers to end users. 160 can be provided. The end user 160 can download or enable these technologies from the software supplier 150 only when needed through the Internet or some other electronic or physical mechanism. This can occur automatically when the end user 160 first tries to play a commercial DVD, or whenever the end user requests prior to playback.

  When the end user 160 requests the required technology, the end user 160 himself is the only authorized recipient of this technology and informs the company that provides the technology activation service (in this proposal the DVD software supplier). Identify. There are several possible mechanisms for this, such as using a serial number (provided with the initial purchase) or something that uniquely identifies the computer system 100, such as a service code on a Dell personal computer. Using means. Based on this identification information, the appropriate technology is provided to the end user and the software supplier 150 is charged for the technology license. Software supplier 150 may choose to reclaim the license fee from the hardware producer. Alternatively, the hardware supplier 170 may be required to pay a license fee to the technology holder 170 based on the end user 160 registration of the software.

  When the end user 160 is receiving or activating the requested technology, there is an opportunity to acquire additional product sales and user information for future sales. Revenue from these additional operations can be shared with hardware suppliers to help compensate costs. This also provides an opportunity to sell more advanced technology from technology holders, which adds additional licensing fees.

  Referring to FIG. 4, a more detailed view of the licensing system is illustrated. Software product 110 may be executed within computer system 100. The computer system 100 may also include input devices such as a mouse and keyboard (not shown) to provide the end user 160 with a means to interact with the user interface of the computer system 100. The computer system may include various storage devices such as an optical drive that reads data information from an optical disc, such as a technique using CD or DVD technology. The software product 110 includes a functional module 106. The function module 106 represents licensed or unlicensed software functions. For example, if software product 110 is software that plays a DVD movie, the software can decode the compressed video in the DVD movie, or Dolby digital decoding, Dolby surround decoding, DivX decoding, or DTS digital sound. A functional module capable of reproducing a DVD movie by using the audio technology as described above may be included. Although only one functional module 106 is illustrated, it should be understood that more than one functional module may be present in the software product 110.

  Each functional module 106 may use one or more technology modules 107. The technology module 107 represents intellectual property rights embodied in the software product 110 and may be required to implement a particular software function module 106. For example, the technology module 107 may incorporate the technology required to decode Dolby Digital audio. The technology module 107 embodied in the function module 106 is owned by the technology holder 120. For example, Dolby Digital Audio is owned by Dolby Laboratories. Accordingly, technology holder 120 may have his / her own patent rights, copyrights, or other protectable rights associated with technology module 107.

  Accordingly, the software product 110 may include a functional module 106 that makes a request to ensure additional licensing from one or more technology holders 120. These modules are referred to as unlicensed technology modules 107. Software product 110 may also include functional modules 106 that do not require additional licenses beyond those required to use base software product 110. For example, a function module 106 that allows a DVD to be played without some audio functions or to view extended content on a DVD is an example of a function that does not require a separate technology license. The function module 106 may include several technology modules 107. Thus, although only one technology holder 120 is illustrated in FIG. 4, there may be several different technology holders 120 for one or more technology modules 107 in the software product 110. You should understand that.

  Some functional modules are protected until all technical modules 107 required to use the functional module 106 are registered. This means that the function module 106 is disabled or otherwise restricted. For example, an unlicensed technology module 107 may be required to be registered by the end user 160 in order to obtain an appropriate license and remove the functional restriction. A registration information center 140 is provided to supply the software product 110 with an appropriate release mechanism 130 to release the functional restriction. Once registered, software supplier 150 may convert unlicensed technology module 107 into licensed technology module 107 by paying the technology holder for the license. Already licensed technology modules 107 may also require registration only for the purpose of tracking their use.

  The registration information center 140 functions as an interface between the computer system 100 or the end user 160 and the technology holder 120. The registration information center 140 may be associated with the software supplier 150 as shown in FIG. 4 or may be another entity. Registration information center 140 and computer system 100 are preferably interfaced through communication network 112. The registration information center 140 receives the registration request from the computer system 100, stores the registration information 134, delivers the release mechanism 130 to the computer system 100 and releases the protection on the technology module 107. The registration information center 140 also functions to store licensing information related to the identification information in the registration database 133. In particular, registration database 133 contains information used to track the use of technology module 107. Software supplier 150 may use this technology usage information in determining whether a technology product is frequently used by end user 160. This technology usage information can be used in determining whether the technology should be included in future software releases. Software supplier 150 may choose to omit less popular technology modules 107 from future releases in an attempt to keep licensing costs to a minimum. Similarly, software supplier 150 may choose to remotely disable technologies that software supplier 150 no longer wants to license.

  The release mechanism 130 may be, for example, a key code 131 that is automatically transmitted to the computer system 100 through the communication network 112, a key code 131 that is provided to the end user 160 through the telephone network 113, or a software product to release protection of the function module The missing source code 132 supplied to 110 may be used.

  FIG. 5 illustrates a preferred flow diagram for using the software licensing system described in FIG. In step 300, the protected software product 110 is provided to the computer system 100. For example, in the example where the software product 110 is software used to play a DVD movie, the software product 110 may be combined with a purchased DVD drive. In other embodiments, the software product 110 is preinstalled on the computer system 100. Alternatively, the software product 110 may be supplied by being physically delivered to the end user 160 in the form of a CD-ROM, DVD, or other known portable storage medium. End user 160 may install software product 110 through an optical drive or other known device that has the ability to read portable storage media within computer system 100. Alternatively, the software product 110 may be provided to the computer system 100 by any conventional distribution system known in the art, such as downloading from a remote software repository over a communications network. For example, the communication network can be the Internet.

  In step 301, once the software product 110 is executed on the computer system 100, the end user 160 replaces any unprotected functional module 106 provided in the initial installation with the technical module associated with it already registered. It may be used with any functional module 106 having all 107. For example, in the case of software used for DVD playback, end user 160 may play a movie that does not require Dolby Digital decoding technology.

  Prior to obtaining registration of any technology module 107, the functional module 106 may be protected to prevent unauthorized use of the technology module 107. For example, the functional module 106 using the technical module 107 may be required for the technical module 107 by disabling execution of the functional module 106, hiding functionality from the user interface of the computer system 100, or in the software product 110. May be protected by not including the correct source code.

  In step 302, the end user 160 requests the use of a functional module 106 that uses at least one unlicensed technology module 107. As shown in step 303, when the software product 110 does not allow the end user 160 to execute the functional module 106 having the unregistered technology module 107, the software product 110 is a user of the computer system 100. An error screen may be configured to be displayed in the interface to notify the end user 160 that the functional module 106 is protected. In addition, the error screen may register the technology module 107 and instruct the end user 160 how to unprotect and enable the use of the function module 106.

  Instead, the software product 110 may not display information indicating that the functional module is protected in the user interface of the computer system 100, but rather may issue the activation request 304 without notifying the end user 160. It may start automatically.

  As shown in step 304, the software product 110 initiates an activation request to the registration information center 140. In step 305, registration information center 140 acknowledges the activation request. Next, in step 306, the registration information center 140 requests identification information for the technical module 107 to be registered. The identification information preferably uniquely identifies a particular end user 160 or a particular copy of the software product 110 so that the identification information can be used to determine whether a particular software product 110 is already registered. . For example, the identification information may comprise an end user 160 identifier, a technical module 107 identifier, and a serial number for the software product 110 such as a CD key.

  As shown in step 307, in response to the request for the identifier, the software product 110 prepares the identification information for transmission to the registration information center 140. As indicated by step 308, the software product 110 sends identification information to the registration information center 140. Next, in step 309, the registration information center 140 is authorized to verify that the identification information is associated with at least one technology module 107 and register the at least one technology module 107.

  In step 310, the registration information center 140 records the technology module 107 to be registered in the registration database 133. In the preferred embodiment, the registration information center 140 records the technology module 107 as “registered” after successful initial license acquisition. Thus, once registration of a technical module 107 associated with a particular software product 110 is successful, the registration information center 140 no longer records subsequent registration requests in the registration database 133. For example, when the end user 160 reinstalls the software product 110, the registration information center may perform the step of registering the technical module 107 as described above, but the additional registration must not be recorded in the registration database 133. However, in other embodiments, the number of consecutive installations may be recorded. Still other embodiments may require registration of the technology module 107 on a per-use basis to collect other usage information, or may be licensed on a per-use basis. For example, at each time the end user 160 executes the functional module 106, the registration procedure may increment and record a count in the registration database 133 for use in determining the ongoing licensing fee. It may be included.

  In step 311, the registration information center 140 provides the release mechanism 130 to the software product 110, thereby enabling the previously protected technology module 107 in connection with the release mechanism 130. The release mechanism 130 is preferably transmitted over the communication network 112. However, the release mechanism 130 may be sent from the registration information center 140 to the system computer 100 using other well-known methods. For example, release mechanism 130 may be provided through an email message, telephone callback, postal service, or any other known communication method suitable for delivering an appropriate release mechanism 130.

  As shown in step 312, the supplied release mechanism 130 is used to enable the technology module 107. For example, the key code 131 is automatically entered into the software product 110 or the missing source code 132 is automatically provided to enable the technology module 107. Once all the technical modules 107 in the functional module 106 are registered, the end user 160 may use the functional module 106 immediately.

  In step 314, the software supplier 150 may be provided with registration information 134 that is used to determine which registered technologies 107 are used more frequently by the end user 160. This registration information 134 may be sent immediately to the software supplier 150 at the time of registration, collected and retrieved by the software supplier as needed, or sent periodically to the software supplier. Information may be transmitted over a communication network such as the Internet. However, other methods of communicating registration information 134, including by postal mail or by telephone, are acceptable. Further, registration information 134 may be provided to other interested parties in addition to software supplier 150. For example, the technology holder 120 may want to charge for a registered technology module 107.

  The registration information center 140 may use the registration step as an opportunity for additional end-user 160 interaction. For example, software products and services may be advertised, or additional user information may be collected for use at future sales opportunities.

  Step 314 provides registration information 134 to software supplier 150 for use in tracking the usage pattern of technology module 107, but the licensing system of FIG. 4 is the technology actually used by end user 160. Used additionally to determine licensing loyalty to be paid for modules only. In particular, software supplier 150 may manufacture software product 110 without first paying for a license from technology holder 120. Alternatively, software supplier 150 may use registration information 134 received at step 314 to determine the royalty to be paid to technology holder 120. Accordingly, as shown in step 315, only after the end user 160 registers the technology module 107, the software provider 150 pays the technology holder 120 for a license. It should be understood that payment may be made instantaneously or may be charged periodically through well-known charging methods. It should also be understood that the hardware supplier 170 may be required to make a payment to the technology holder 120 in accordance with the collected registration information 134.

  Thus, the method of FIG. 5 describes a method of software licensing, where the software supplier 150 pays only for the technology module 107 registered by the end user 160. It should be understood that the licensing software method reduces costs to software merchants 150 and end users 160 by not requiring payment for unused technology in software product 110. Thus, the discrepancy between the purchase cost by the software supplier 150 and the actual request of the end user 160 is eliminated. If the technology module 107 is not used, the money for the license is no longer wasted for the end user 160. For software suppliers 150, license fees associated with unused technology modules no longer reduce margins. Similarly, because unused technology 107 is not passed on to end users 160 at the selling price, the cost of the product is lower, thereby increasing market share. Finally, the interaction between the registration database and the end user provides another opportunity to promote the sale of additional products by software suppliers, technology holders, and / or manufacturers.

  In other embodiments, the launch and enable steps 304-312 may be performed through the telephone interface 113 between the registration information center 140 and the end user 160. For example, in such an embodiment, in step 304, the end user 160 calls the registration information center 140 to initiate an activation request to the technology module 107. The registration information center 140 acknowledges the activation request 305, requests identification information 306, receives the identification information 309, records the registration 310, and performs a function to provide the release mechanism 130 to a live person You may hire or use an automated telephone system. User 160 may communicate identification information, receive release mechanism 130, interact with computer 100, enter received release mechanism 130, and enable technology module 107.

  Although the embodiment of completing the activation of the technical module 107 over the communication network 112 and the telephone network 113 has been described in detail above, any means for communicating the necessary activation request, identification information and release mechanism 130 are technical routines. Those skilled in the art will appreciate that skills can be substituted. For example, it is anticipated that the activation and registration steps can be completed through postal mail as well.

  In other embodiments, the software licensing system of FIG. 4 may be used when the computer system 100 temporarily leaves the network 112 or when the end user 160 cannot immediately register the product through the telephone network 113. The use of the technology module 107 may be temporarily activated. This allows the functional module 106 to operate for a limited time even if the technology module 107 is not properly registered. In this case, a predetermined time period or number of uses of the technology module 107 may be given to the end user 160 before the functional module requesting the registered technology module 107 is disabled. This embodiment is particularly useful for users 160 who do not have access to telephone network 113 or communication network 112 for a short period of time. For example, in an aircraft where access to the telephone network 113 or the communication network 112 is often inconvenient, the user 160 who wants to watch a DVD movie using Dolby Digital Sound may be temporarily used by the unlicensed technology module 107 You may need it. Once the user 160 has access to the telephone network 113 or the computer system 100 can access the registration information center 140 through the communication network 112, as described in steps 304-312 of FIG. The module is registered and released.

  Further, the software supplier 150 may agree to license the technology module 107 from the technology holder 120 for each unit of use. Thus, the system may be designed to fit loyalty contracts based on multiple registrations for the same user and the same technology. Accordingly, the licensing system may perform some combination of registration and enable steps 304-312 each time the technology module 107 is used. In this embodiment, registration information for each use is stored in registration database 133 and is billed to software supplier 150 using well-known billing methods. Accordingly, the software licensing system may be configured to register the technology module 107 for each use, ie, one use unit.

  The present invention can also be described as a three party software trading system and method. In the prior art system and method of the software trading system, FIG. 6 illustrates that the software supplier 12 provides the software 122 to a single user 14. The software supplier 12 pays a license fee for the technology 162 to all the technology owners 16. Software supplier 12 may be a software manufacturer, hardware manufacturer, or any party that distributes software 122 to users 14. User 14 may be any consumer or any party that legally obtains the right to use software 122. The technology owner 16 can obtain a license fee from the software supplier 12 based on the sales volume. Although the user 14 may not explicitly pay the license fee to the technology owner 16, this license fee is typically included in the selling price. In addition, to protect software 122 from illegal copying, user 14 asks for a CD key or service code associated with software 122 when downloaded from the Internet, bought from a store, or sent through email. May be. Neither software supplier 12 nor technology owner 16 is generally notified of the installation. Therefore, they do not know the actual number of installed copies of software 122. One or more techniques 162 may also be associated with the software 122. Since the user 14 may never use some features of the software 122, the number of installations is unknown and the actual use of the licensed technology 162 is unknown.

  The system of the first embodiment of the software trading system is to be distinguished from the conventional trading system, in which the software supplier sends the license fee to the technology owner for each unit shipped. Pay. Rather, in the present invention, the software supplier can monitor which technologies in the software are not being used so much, so that data is provided to the software supplier and which technologies are used more frequently. The product can be judged based on whether or not

  Referring to FIG. 7A, in a first preferred embodiment of a software trading system, the protected software 520 of the present invention comprises one or more technical limitations 526, one or more functions 522, and a registration program 528. Yes. Each technology limitation 526 is used to limit the use of one or more technologies 524. Each function 522 uses one or more techniques 524, and each technique 524 is used by one or more functions 522. A technology limitation 526 associated with one technology 524 may prohibit the use of one or more functions 522. Each registration program 528 is used to remove a limitation on the technology limitation 526 associated with one or more technologies 524. Each technique 524 corresponds to one registration program 528. Accordingly, one registration program 528 is associated with one or more technology limitations 526 and is executed before the function 522 of the technology 524 associated with the technology limitations 526 is performed. Once the execution of the registration program 528 is successful, the technical limitation 526 related to the registration program 528 is released. When the technology limitation 526 related to the technology 524 is released, the registration program 528 related to the technology 524 is not executed again. For example, if one function 522 requires three technologies 524 and three technologies 524 require two registration programs 528 to release the imposed technology limitation 526, the two registration programs 528 In total, the technology limitation 526 for the six technologies 524 can be released. If the other three techniques 524 are required by other functions 522, the other functions 522 can be automatically accessed once the two registration programs 528 are executed.

  FIG. 7B illustrates the process steps used to execute the registration program 528. First, an activation step 582 is executed. In a subsequent identification step 584, the license identifier is transmitted to the server. In a subsequent acknowledgment step 586, a license acknowledgment is obtained and registration is complete. Finally, a release step 588 is executed to release the technical limitation 526.

  In the present invention, the activation step 582 is related to all the techniques 524 that are invoked, by automatically activating the registration program 528 by manually activating the registration program 528, and by automatically activating the registration program when the relevant function is executed. The registration program 528 may be executed manually and continuously.

  License identification step 584 is used to justify the use of protected software 520. In order to access the payment technology 524 in the protected software 520, the software usage entity 414 must send a license identifier. This may be in the form of a string or electronic signal, a document such as a CD key, serial number or service code. The license identifier may be manually entered by the software usage entity 414 and automatically checked by the registration program 528, or may be indicated by an identification document after software installation when using payment technology during software installation.

  License acknowledgment step 586 is used to acknowledge whether technical limitation 526 for software 520 is removed. License acknowledgment automatically starts fetching acknowledgments from the server through the network, manually starts fetching acknowledgments from the server through the network, starts fetching after sending actual mail to the server, and e Fetching may be started after sending the mail, or may be obtained by some other similar method. The registration is almost finished after the registration program 528 receives the license identifier.

  In previous embodiments, the software 520 may be protected by a failure function, a hidden function, or lacking the necessary source code for the function 522 to operate. If software 520 is protected by a failure function, some functions 522 associated with a particular technology 524 have failed until the technology limitation 526 is removed by registration of the associated technology 524. If the software 520 is protected by a hidden function, the function 522 is hidden from the software usage entity 414 until the relevant technology registration is complete. If software 520 is protected by the lack of necessary source code, a requirement to operate a particular technique 524 so that one or more functions 522 cannot be performed by lacking the necessary source code. Source code is not included in the software 520. The source code required to operate the technology 524 is provided after the relevant technology registration is complete. For example, the required source code can be provided by adding missing source code or by replacing the entire source code for protected software 520.

  Using the previous embodiment, the software supply entity 742 can track which technology 524 is registered by a particular user or copy of the software. This is particularly suitable for video software such as DVD playback software, which may include many unit-based licensing technologies that are expensive. For example, by tracking which technologies 524 are used by the software usage entity 414, the software delivery entity 742 may determine which technologies will continue to be provided in future software 520 releases.

  A second preferred embodiment of the software transaction invention involves a three party transaction method as illustrated in FIG. First, in step 632, the protected software 520 is delivered by the first party to the second party. As in the previous embodiment, the delivered software 520 includes one or more technology limitations 526 related to the technology 524. Next, in registration step 634, the second party registers the required techniques 524 with one or more third parties. The third party records registration information. Next, in a release step 636, the second party requests a release mechanism related to the particular technology from the third party. In addition, a release mechanism is received and used to release the technology limitation 526. Finally, in payment step 638, the first party pays a license fee to the third party.

  The protected software 520 in the second embodiment of the software trading system is the same protected software 520 as in the first embodiment. Thus, the specific functions of the protected software 520 are the same as those previously described in the first embodiment. In this second embodiment, the second party using software 520 (generally software usage entity 414) does not pay the license fee directly to the payment technology. Rather, the second party registers the payment technology with a third party (which may be a software supplier or technology owner) according to practical needs. The first party (such as a software supplier) then pays a license fee to the third party (which may be the technology owner) according to the registration information regarding the registered technology 524.

  The registration information 762 includes initial registration information, and may include subsequent registration information. Initial registration information occurs when a third party first receives a license identifier from the second party's registration program 528 for the first time. Subsequent registration information occurs when the third party again receives the license identifier from the registration program 528 of the second party. For example, the software usage entity 414 may reinstall the software and the third party again receives the license identifier from the second party registration program 528. Technology 524 may require only payment for initial registration. The third party may receive payment from the first party or the first party's licensee. Further, the payment may be made directly or indirectly to the third party. Further, the third party may provide an interaction mechanism to the second party at the same time as or after technology 524 is released by the second party. For example, the interaction mechanism may include custom services, advertisements, promotions, or special billing.

  Compared to the prior art based on a single and complete payment for the license fee, the previously described embodiments can prevent wasted expenses by registering and paying only the licenses that are actually used.

  FIG. 9 shows a third embodiment of a three-party transaction system. The three parties include a software supply entity 742, a software usage entity 414, and one or more software registration entities 746. Software provision entity 742 provides protected software 520 to software usage entity 414. Protected software 520 includes one or more functions 522, one or more technologies 524, one or more technology limitations 526, and one or more registration programs 528. Each technology limitation 526 is used to limit the use of one or more technologies 524. Each function 522 uses one or more techniques 524, and each technique 524 is used by one or more functions 522. Each registration program 528 is used to release a technology limitation 526 associated with one or more technologies 524. Each software registration entity 746 is provided with registration information 762 provided by the registration program 528. Each registration entity 746 records registration information 762 after registration of technology 524.

  The protected software 520 in the third embodiment of the software trading system is the same protected software 520 as in the first and second embodiments. Software 520 may be delivered from software supply entity 742 to software usage entity 414 by any mechanism, such as network download, cross-selling, physical delivery, or other known software delivery methods. Software supply entity 742 controls payment for software usage entity 414. One skilled in the art should understand that the method of payment is not limited. Software registration entity 746 controls the registration process and the technology restriction release process for software usage entity 414. Software registration entity 746 may be accessed by software usage entity 414 through a communications network, telephone, mail, voice communication, letter, electronic signature, remote download, storage media delivery, or other known methods.

  Registration information 762 stored by software registration entity 746 may include initial registration information 762 and subsequent registration information 762. Multiple registrations for the same technology from the same software usage entity 414 may be charged once or repeatedly. The initial registration information 762 is generated when the software registration entity 746 receives a license identifier from the registration program 528 of the software usage entity 414 for the first time. The subsequent registration information 762 is generated, for example, when the software registration entity 746 receives the license identifier from the registration program 528 of the software usage entity 414 again. For example, the software usage entity 414 may reinstall the software, and the software registration entity 746 may receive the license identifier again from the registration program 528 of the software usage entity 414. Technology 524 may require payment only for initial registration. Software registration entity 746 may be paid for by software supply entity 742 or a licensee of software supply entity 742. Further, the payment may be transferred directly or indirectly to the software registration entity 746. Further, the software registration entity 746 may provide a mechanism for interaction with the second party at the same time as or after the technology 524 is released by the software registration entity 746. For example, the interaction mechanism may include custom services, advertisements, promotions, or special billing.

  The previously described embodiments of the present invention emphasize that the particularly “preferred” embodiments are merely examples of possible configurations and are merely shown for a clear understanding of the principles of the present invention. Many variations and modifications may be made to the previously described embodiments of the invention without substantially departing from the spirit and principles of the invention. All such variations and modifications are intended to be included within the scope of this disclosure and the present invention and protected by the following claims.

FIG. 1A is a diagram of a prior art software licensing system. FIG. 1B is a diagram of another prior art software licensing system for bundled software. FIG. 2A is a diagram of one embodiment of a software licensing system in which a second party records first party registration information for a licensed technology in a software product. FIG. 2B is a diagram of one embodiment of a software licensing system in which a third party provides bundled software to a first party, and a second party exchanges a license for registered technology. In order to determine payment to the four parties, the registration information of the first party is recorded. FIG. 2C is a diagram of one embodiment of a software licensing system in which a third party provides bundled software to a first party, and a second party provides a fourth for a license to a registered technology. The first party registration information is recorded in order to determine payment to the first party. FIG. 2D is a diagram of one embodiment of a software licensing system in which a third party pays a fourth party based on registration information recorded by the second party. FIG. 2E is a diagram of one embodiment of a software licensing system in which a third party pays a fourth party based on registration information recorded by the third party. FIG. 3 is a flow diagram of a system and method for a software licensing system. FIG. 4 is a diagram illustrating an embodiment of a software licensing system. FIG. 5 is a flow diagram illustrating the steps for implementing a software licensing system as described in the system and method of the present invention. FIG. 6 is a schematic diagram of three parties used in a prior art software trading system. FIG. 7A shows a diagram of protected software used in a software trading system. FIG. 7B is a flow diagram of a first preferred embodiment of a software trading system. FIG. 8 is a flow diagram of a second preferred embodiment of a software trading system. FIG. 9 illustrates a third embodiment of the software trading system.

Claims (26)

In a method related to executing software on a computer system,
Request execution of a software routine in the software, the request initiated by the first party;
Determining whether execution of the software routine requires payment to the third party;
Sending a notification to the second party 150 indicating that the software routine has been called by the first party;
A method in which a notification indicating that the third party requests payment from the second party for execution of the software routine charges the second party. The third party is the technology holder,
The second party
With computer hardware suppliers,
With the software supplier,
The method of claim 1, wherein the party is selected from the group consisting of:   The method of claim 1, wherein the second party is a computer hardware supplier and the third party is a software supplier.   The method of claim 1, further comprising the step of restricting use of the software routine before the notification is sent to the second party. In a method of licensing software on a computer hardware platform that includes at least one feature that is restricted to limited use,
Send an activation request to the Registration Information Center for the technology to be registered to use at least one function;
Let the registration database collect registration information related to the technology to be registered to use at least one function;
Receiving a communication that can remove a limited use restriction of at least one function;
Determining the actual use of the technology based on registration information collected in a registration database.   6. The method of claim 5, further comprising the step of making a payment to the technology holder, wherein payment is based on actual use of the technology. Its limited use is
Disallow the execution of the function,
Only allow a predetermined number of functions to be used,
Hide features from the user interface,
Avoid using executable code necessary to perform functions,
6. The method of claim 5, wherein the method is selected from the group consisting of:   The method of claim 7 wherein the predetermined number of uses is zero.   6. The method of claim 5, further comprising receiving a call from the computer to perform at least one function that is restricted to limited use. In the software used in the software licensing system,
At least one function that is restricted to limited use, including at least one technology to be registered before the limited use is lifted;
Logic to send an activation request related to at least one technology to be registered to use at least one function to a registration information center;
Logic to send registration information related to the technology to be registered to use at least one function to the registration information center;
Receiving a communication including means for releasing a limited use restriction of at least one function,
The registration information center includes means for collecting registration information,
The means for collecting registration information is software accessible to determine the actual use of the technology based on the registration information.   The software of claim 10, wherein the means for collecting registration requests is a registration database.   The system according to claim 10, wherein the means for releasing the limited use restriction includes a key code or a source code.   The system of claim 10, wherein at least one function is to play a DVD movie. At least one technology
The technology used to decode the digital audio, and
The technology used to decode the digital video, and
The system of claim 10, selected from the group consisting of: Limited use is
Disallow the execution of the function,
Only allow a predetermined number of functions to be used,
Hide features from the user interface,
Avoid using executable code necessary to perform functions,
The system of claim 10, wherein the system is selected from the group consisting of:   The system of claim 10, wherein the means for collecting registration information may be accessed by a software supplier to determine the actual use of the technology based on the registration information.   17. The system of claim 16, wherein the software supplier pays the technology holder and the payment is based on the actual use of the technology. In a system that licenses software,
Including at least one function restricted to limited use, the function including at least one technology to be registered before the limited use is released, and the software includes logic to receive communication, A protected software product that includes means for releasing at least one limited use restriction;
A registration information center for storing registration information relating to identification information collected in a registration database used to track the use of the technology, including means for releasing limited use restrictions of at least one function System.   19. The system of claim 18, wherein the means for releasing the limited usage restriction comprises a key code or source code.   The system of claim 18, wherein at least one function is to play a DVD movie. At least one technology
The technology used to decode the digital audio, and
The technology used to decode the digital video, and
The system of claim 18 selected from the group consisting of: Limited use is
Disallow the execution of the function,
Only allow a predetermined number of functions to be used,
Hide features from the user interface,
Avoid using executable code necessary to perform functions,
19. The system of claim 18, wherein   The system of claim 18, wherein the registration database may be accessed by a software supplier to determine the actual use of the technology based on the registration information.   24. The system of claim 23, wherein the software supplier pays the technology holder and the payment is based on actual use of the technology. In the method of licensing software,
Providing the user with software comprising at least one unregistered technology within at least one restricted function module;
Receive a request from the user to release the restricted functional module,
Release restricted functions, generate activated functions,
A method comprising licensing a registered technology from a technology holder. In a way to manage the cost of licensed technology,
Providing the user with software comprising at least one unregistered technology within at least one restricted function module;
Receive a request from the user to release the restricted functional module,
Collect registration data in the registration database,
Release restricted functions,
Determining the use of a registered technology based on registration data in a registration database.

Images