WO2012090026A2

WO2012090026A2 - Reward system and method

Info

Publication number: WO2012090026A2
Application number: PCT/IB2010/056119
Authority: WO
Inventors: Philippus Jacobus KOCH
Original assignee: Koch Philippus Jacobus
Priority date: 2010-12-30
Filing date: 2010-12-30
Publication date: 2012-07-05

Description

REWARD SYSTEM AND METHOD

BACKGROUND OF THE INVENTION

THIS invention relates to a reward system and method.

Online websites providing products and solutions, for example, solutions to technical problems seldom recognise contributions or solutions offered by solution providers in a way which is meaningful to these solution providers. A resultant problem arguably stemming from this is that the quality of products or solutions provided to these websites is often not as good as it could possibly be.

In this regard, it is an object of the present invention at least to address the abovemeritioned problem.

SUMMARY OF THE INVENTION

According to a first aspect of the invention there is provided a reward system for rewarding at least one solution provider in a solution provider system, wherein the solution provider uploads one or more of solutions and products to the solution provider system for use by a solution consumer, the reward system comprising: a database storing information indicative of a plurality of reward accounts associated with one or more of solution providers, solution consumers, and solution provider systems, wherein the reward accounts are configured to store reward points, or information indicative thereof, arid wherein each reward point has a monetary value associated therewith; a reward point management module configured to receive a request to debit a reward account of a solution consumer for an amount of reward points, to process the request, and to credit a reward account of at least one solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to process the request; and an interface module configured to enable the solution provider system to interface with the reward system such that the solution consumer using the solution provider system is able to award reward points to at least one solution provider by way of the reward system.

The system may comprise a financial management module configured to enable holders of reward accounts to purchase reward points and to convert reward point to the monetary values associated therewith.

The financial management module may be further configured to facilitate communication with financial institutions associated with the reward account holders in order to debit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with purchased reward points and to credit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with cashed reward points.

The solution provider system may typically comprise a solution provider website. The interface module is therefore configured to provide a link within the solution provider website to the reward system.

The interface module may be configured to prompt a solution consumer for an amount of reward points which the solution consumer desires to award to the solution or solution provider. It may be noted that awarding reward points to solutions result in awarding of the reward point to the respective solution provider/s of the solution.

The interface module may further be configured to: establish communication between the solution provider system and the reward system; receive, from the solution provider system, an account identifier associated with the solution provider system; receive, from the solution provider system, a solution identifier associated with a particular solution provided by the solution provider in the solution provider system; receive, from the solution provider system, a user identifier of the solution consumer, of the particular solution, in the solution provider system; and receive, from the solution provider system, a user identifier of the solution provider, of the particular solution, in the solution provider system.

The reward point management module may be configured to: associate the received user identifier of the solution consumer in the solution provider system with a user reward identifier of the solution consumer in the reward system; associate the received user identifier of the solution provider in the solution provider system with a user reward identifier of the solution provider in the reward system; and facilitate prompting the solution consumer, at the solution provider system, for an amount of reward points which the solution consumer requests to be awarded to the solution provider.

The reward point management module may be configured to: determine the amount of reward points which the solution consumer has in their respective reward account; debit the amount of reward points from the reward account of the solution consumer and credit the reward account of the solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to cover the amount requested to be awarded to the solution provider; and at least provide a suitable message to the solution consumer if the reward account of the solution consumer has insufficient reward points to cover the amount requested to be awarded to the solution provider.

The reward system may further comprise a registration module configured to: receive particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to open a reward account therefor respectively; receive updated particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to update an existing reward account therefor respectively; associate and store particulars associated with the respective solution provider, solution consumer, and solution provider system in the database.

Instead of crediting the reward account of the solution provider, the reward point management module may be configured to credit the reward account of the solution provider system for the amount of reward points awarded to the solution or solution provider.

There may typically be a plurality of solution providers for a particular solution, wherein the interface module is configured to receive information indicative of a percentage contribution of each solution provider to the solution, wherein the reward points are allocated to each solution provider in accordance with their respective percentage contribution to the solution.

The reward system may further comprise a search engine interface module configured to interface with at least one search engine to provide the same with one or more of keywords associated with a particular solution, solution identifiers associated with the solution, and the reward points earned by the solution to enable the search engine to rank search results of solutions according to the reward points earned thereby.

According to a second aspect of the invention there is provided a method of rewarding at least one solution provider in a solution provider system by way of a reward system, wherein the solution provider uploads one or more of solutions and products to the solution provider system, the. method comprising: storing, in a database, information indicative of a plurality of reward accounts associated with one or more of solution providers, solution consumers, and solution provider systems, wherein the reward accounts are configured to store reward points, or information indicative thereof, and wherein each reward point has a monetary value associated therewith; facilitating communication between a solution provider system and the reward system such that, in use, a solution consumer using the solution provider system to obtain solutions or products is able to award reward points to at least one solution provider by way of the reward system; receiving, by way of a reward point management module, a request to debit a reward account of a solution consumer for an amount of reward points, processing the received request, and crediting a reward account of at least one solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to process the request.

The method may further comprise: establishing communication with financial institutions associated with the reward account holders; debiting financial accounts, at the respective financial institutions by way of a financial module, associated with reward account holders for monetary values associated with purchased reward points; and crediting financial accounts, at the respective financial institutions by way of the financial module, associated with reward account holders for monetary values associated with cashed reward points.

The method may comprise providing a link within a solution provider website of the solution provider system to the reward system.

The method may comprise prompting a solution consumer for an amount of reward points which the solution consumer desires to award to the solution provider.

The method may further comprise: establishing communication between the solution provider system and the reward system; receiving, from the solution provider system, an account identifier associated with the solution provider system; receiving, from the solution provider system, a solution identifier associated with a particular solution provided by the solution provider in the solution provider system; receiving, from the solution provider system, a user identifier of the solution consumer, of the particular solution, in the solution provider system; and receiving, from the solution provider system, a user identifier of the solution provider, of the particular solution, in the solution provider system.

The method may also comprise: associating the received user identifier of the solution consumer in the solution provider system with a user reward identifier of the solution consumer in the reward system; associating the received user identifier of the solution provider in the solution provider system with a user reward identifier of the solution provider in the reward. system; and prompting the solution consumer, at the solution provider system, for an amount of reward points which the solution consumer requests to be awarded to the solution provider.

The method may further comprise the steps of: determining the amount of reward points which the solution consumer has in their respective reward account; debiting the amount of reward points from the reward account of the solution consumer and crediting the reward account of the solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to cover the amount requested to be awarded to the solution provider; and providing a suitable message to the solution consumer if the reward account of the solution consumer has insufficient reward points to cover the amount requested to be awarded to the solution provider.

The method may also comprise: transmitting a questionnaire to the solution consumer, the questionnaire comprising questions to provide feedback to the solution provider or the solution provider system; and transmitting a suitable message to one or more of the solution provider, solution consumer, and solution provider system, on a successful debiting of the reward account of the solution consumer arid crediting the reward account of the solution provider for the amount of reward points.

The method may further comprise: receiving particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to open a reward account therefor respectively; receiving updated particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to update an existing reward account therefor respectively; and associating and storing particulars associated with the respective solution provider, solution consumer, and solution provider system in the database.

The method may also comprise, wherein there is a plurality of solution providers for a particular solution, the steps of: receiving information indicative of a percentage contribution of each solution provider to the solution; and allocating or awarding reward points to each solution provider in accordance with their respective percentage contribution to the solution.

BRIEF DESCRIPTION OF THE DRAWINGS Figure 1 shows a block diagram of a network incorporating a reward system in accordance with an example embodiment;

Figure 2 shows a context diagram of a network incorporating a reward system in accordance with an example embodiment;

Figure 3 shows a flow diagram of a method in accordance with an example embodiment;

Figure 4 shows a block flow diagram of a registration process or method for a solution consumer in accordance with an example embodiment;

Figure 5 shows a block flow diagram of a registration process or method for a solution provider in accordance with an example embodiment;

Figure 6 shows a block flow diagram of a process or method for purchasing reward points in accordance with an example embodiment;

Figure 7 shows a block flow diagram of a process or method for awarding reward points in accordance with an example embodiment;

Figure 8 shows a block flow diagram of a process or method for cashing reward points in accordance with an example embodiment;

Figure 9 shows a block flow diagram of a process or method for maintaining a reward account in accordance with an example embodiment;

Figures 10 and 11 shows a example embodiments of reward system banners in accordance with an example embodiment; and Figure 12 shows a diagrammatic representation of a machine in the example form of a computer system in which a set of instructions for causing the machine to perform any one or more of the methodologies discussed herein, may be executed.

DESCRIPTION OF PREFERRED EMBODIMENTS

In the following description, for purposes of explanation, numerous specific details are set fort in order to provide a thorough understanding of an embodiment of the present disclosure. It will be evident, however, to one skilled in the art that the present disclosure may be practiced without these specific details.

Referring to Figure 1 and 2 of the drawings where a network in accordance with an example embodiment is generally indicated by reference numeral 10. The network 10 comprises a reward system 12 in accordance with an example embodiment. The reward system 12 is configured to communicate with a solution provider system 14 via a communication network 16. Similarly, the system 12 is configured to communicate with one or more financial institutions 15 or banks {Figure 2) via the communication network 16. The communication network 16 may be a packet-switched network and may form part of the Internet. Instead, the communications network 16 may be a circuit switched network, public switched data network, or the like. In certain embodiments, the network 16 forms part of the mobile web or Internet. In this regard, the reward system 12 may be accessible via a mobile web-based application.

Although not limited thereto, the solution provider system 14 comprises a solution provider website which provides solutions or products. The solution provider website may be development or developer websites or networks, for example, websites which provide software developers with solutions to technical problems or may be websites which provide products for download or viewing, wherein the products may be data products such as multimedia products, for example, videos, music files, images, etc. It will be appreciated that the term "solution" within the context of this specification will be understood to also comprise any other resource, for example, a resource capable of being provided online. Differently defined, a solution may be any resource supplied to a solution consumer (described below) or solution provider website 14, for example, a video, recipe, Image, sound clip, a solution to a problem, an application, a game, blog post, an online encyclopedia post, an article, a review of an item or service, or the like. It follows that in certain example embodiments, solutions may be understood to comprise the products as hereinbefore described.

In one example embodiment, the solution provider website comprises a mobile solution provider website.

The solution provider website is accessible by solution providers 18 as well as solution consumers 20 by way of associated computing devices via the network 16. The solution providers 18 and solution consumers 20 may be natural persons, groups of natural persons, for example, software developers, legal persons, or the like. It will be appreciated that while only one solution provider system 14, solution provider 18, financial institution, and solution consumer 20 is illustrated, the network 10 may comprise a plurality of these entities. For brevity, reference will therefore alternate between singular and plural for these aforementioned entities. Further, it will be appreciated that a solution consumer 20 could possibly be a solution provider 18 and vice versa. However, for ease of explanation, this distinction will be used in the specification.

Conventionally, the solution provider 18 provides solutions or products freely on the website of the solution provider system 14. Without being rewarded for the provision of the solution or product in a way which is meaningful thereto, the quality of solutions or products offered on the solution provider website are often not of the highest quality which they could possibly be. In this regard, the reward system 12 as disclosed herein seeks to address this problem and to reward the solution provider 18 financially.

To this end, the reward system 12 comprises a plurality of components or modules which correspond to the functional tasks to be performed by the system 12. In this regard, "module" in the context of the specification will be understood to include an identifiable portion of code, computational or executable instructions, data, or computational object to achieve a particular function, operation, processing, or procedure. It follows that a module need not be implemented in software; a module may be implemented in software, hardware, or a combination of software and hardware. Further, the modules need not necessarily be consolidated into one device or system 12 but may be spread across a plurality of devices, for example, across the network 10.

In particular, the reward system 12 comprises a database 22 storing information indicative of a plurality of reward accounts associated with one or more of solution providers 18, solution consumers 20, and solution provider systems 14. The reward accounts are configured to store reward points, or information indicative thereof.

It will be appreciated that each reward point advantageously has a monetary value associated therewith, thereby making providing quality solutions and products more enticing to solution providers 18. In certain example embodiments, the monetary value of a reward point may be very low, almost insignificant to the solution consumer 20 thereby making it the system 12 accessible for the solution consumer 20 to use. It will be appreciated that the reward points may be awarded as tips to providers of solutions/resources as will be described below.

In this regard, the system 12 also comprises a reward point management module 24 configured to receive a request to debit a reward account of a solution consumer 20 for an amount of reward points. Differently defined, the request may be to credit a reward account of a solution provider 18 for an amount of reward point. However, it will be appreciated that either descriptions or definitions lead to a similar end.

The module 24 is further configured to process the received request, and to credit a reward account of the solution provider 18 with the amount of reward points if the reward account of the solution consumer 20 has sufficient reward points to process the request.

In particular, the reward point management module 24 is configured to determine the amount of reward points which the solution consumer 20 has in their respective reward account; debit the amount of reward points from the reward account of the solution consumer 20 and credit the reward account of the solution provider 18 with the amount of reward points if the reward account of the solution consumer has sufficient reward points to cover the amount requested to be awarded to the solution provider; and at least provide a suitable message to the solution consumer 20 if the reward account of the solution consumer 20 has insufficient reward points to cover the amount requested to be awarded to the solution provider 18. The message may simply be a message, for example, an e-mail, instant messaging message, or text/SMS (short message service) message informing the solution consumer 20 that they have insufficient reward points to cover the amount requested to be awarded to the solution provider 8.

It will be appreciated that though a solution provider 18 of solution provider system 14 receives the financial benefit from the reward points, the information associated therewith is uniquely associated with each solution, For example, whereas a solution provider 18 may receive the financial value associated with 10 reward points being associated with their solution, the information that the solution earned 10 points is uniquely associated with that particular solution and stored in the database 22. In this regard, a reward point awarded to a solution provider 18 may be understood to be a reward point awarded to a solution provided by the solution provider 18. The system 12 also comprises an interface module 26 configured to enable the solution provider system 14 to interface with the reward system 12 such that the solution consumer 20 using the solution provider system 14 is able to award reward points to the solution provider 18 by way of the reward system 12.

As mentioned, the solution provider system 14 typically comprises a solution provider website. The interface module 26 is therefore configured to provide a link within the solution provider website to the reward system 12. The link may be an interface, a web widget, hyper-link within the solution provider website to the reward system 12.

The interface module 26 may further be configured to establish communication between the solution provider system 14 and the reward system 12 The interface module 26 may be configured to only establish this communication if it determines that the solution provider system 14 is authorised to do so. The interface module 26 may therefore be configured to determine if an account identifier associated with the solution provider system 14 is valid in order to allow the system 14 to log-in to the reward system 12. The systems 12 and 14 may typically communicate over SSL protocol to ensure secure information exchange.

It follows that the interface module 26 may be configured to receive, from the solution provider system 14, an account identifier associated with the solution provider system 14, a solution identifier associated with a particular solution provided by the solution provider 18 on the solution provider website; a user identifier of the solution consumer 20 of the particular solution on the solution provider website, and a user identifier of the solution provider 18 of the particular solution on the solution provider website.

It will be appreciated that the user identifiers of the solution providers 18 and solution consumers 20 are from the solution provider system 14, for example, their usernames or user identification numbers, etc. from the solution provider system 14.

The reward point management module 24 is conveniently configured to associate the received user identifier of the solution consumer 20 in the system 14 with a user reward identifier of the solution consumer 20 in the reward system 12. In a preferred example embodiment, the user reward identifier is the reward account identifier, for example, an account number of the reward account of the solution consumer 20.

Similarly, the reward point management module 24 is configured to associate the received user identifier of the solution provider 18 with a user reward identifier of the solution provider 18 in the reward system 12.

The reward point management module 24 is also configured to facilitate prompting the solution consumer 20, at the solution provider system 14, for an amount of reward points which the solution consumer 20 requests to be awarded to the solution provider 18. It does this by instructing the interface module 26 to prompt the solution consumer 20 for an amount of reward points which the solution consumer 20 desires to award to the solution provider 18.

The module 26 may be configured to prompt the solution consumer for an amount of reward point which the solution consumer desires to award the solution provider 18 by providing the solution provider system 14 with a banner or instructing the system 14 to provide a banner, for example, the banners illustrated in Figures 10 and 11 , to the solution consumer 20. The banners may be generated by the system 12 and may comprise fields which prompt the solution consumer 20 for the amount of reward points they desire to award to the solution provider 18. A completed banner, i.e. one which has fields filled in by the solution consumer 20, is receivable by the module 24 and forms part of the request as hereinbefore described. The banner may also comprise information indicative of the name or unique identifier of the solution provider 18, as well as a field for rating the solution provider 18. The banner may also comprise information indicative of the name or unique identifier of the solution consumer 20, the total number of award points which the solution consumer 20 has in their reward account, and a status bar indicating a capacity of the solution consumer's 20 reward account. In any event, it will be appreciated that the. banner may be any shape, colour, pattern or configuration. However, it is important that the banner be user friendly, catchy and aesthetically appealing, must not intrude on a particular design of the solution provider website, and must be able to dynamically adapt in form, colour, and design to suite the solution provider's website.

The reward system 12 may comprise a financial management module 28 configured to enable holders of reward accounts, viz. the solution providers 18, the solution consumers 20, and solution provider systems 14, to purchase reward points and to convert reward points to the monetary values associated therewith.

The financial management module 28 may be further configured to facilitate communication with financial institutions, for example, banks associated with the reward account holders in order to debit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with purchased reward points and to credit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with cashed reward points. The financial management module 28, especially the ability of the same to facilitate cashing of reward points for monetary value advantageously incentivises the provision of quality solutions or products to the solution provider systems 14.

It will be appreciated that there may be a plurality of other methodologies to purchase reward points of the system 12, as well as a plurality of other methodologies to cash reward points for their monetary amount. In this regard, the financial management module 28 may be configured to facilitate these transactions accordingly. For example, the module 28 may be configured to facilitate purchasing of reward points in a similar fashion to the over-the-counter or point-of-sale purchasing of pre-paid airtime. Instead, or preferably in addition, the module 28 may be able to facilitate purchasing (or cashing) of reward points via conventional online credit/debit card transactions or online payment instruments or tokens.

The financial management module 28 may also be configured to allow an account holder to access their accounts at the reward system 12 to obtain a financial statement associated with transactions on their respective accounts. The financial statement may comprise information indicative of transactions on the reward account, for example, debits and credits of reward points during actions like purchasing, awarding, receiving and cashing of points. The financial statements may have the following information associated with each transaction:

Date

Time

Transaction type (purchase, reward, award or cassing)

Number of reward points

Balance of points at that point

Party that was rewarded

Link to solution that was rewarded (this link will be a user friendly description plus a hyper text link to solution)

The reward system 12 also comprises a registration module 30 configured to receive particulars associated with one or more of a solution provider 18, a solution consumer 20, and a solution provider system 14 in order to open a reward account therefor respectively in the database 22. The particulars may be one or more of banking details associated with the aforementioned entities, geographical data associated therewith, names of the entities (usernames and full names including company names if entities are companies), e-mail addresses, physical addresses, user identifiers which each entity uses in the solution provider system 14, as well as any other regulatory information required in order to open up a reward account therefor.

Once registered, the registration module 30 conveniently creates a profile of each registered entity in the database 22, wherein each profile is associated with at least one reward account of the entity in the database 22 as well as the particulars received therefrom.

The registration module 30 may be configured to receive updated particulars associated with one or more of a solution provider 18, a solution consumer 20, and a solution provider system 14 in order to update an existing reward account therefor respectively.

It follows that the module 30 is also configured to associate and store particulars associated with the respective solution provider 18, solution consumer 20, and solution provider system 14 in the database 22.

The registration module 30 may be configured to transmit a suitable message, for example, via e-mail, to the solution provider 18, the solution consumer 20 and the solution provider system 14 to confirm registration or profile update. The message may comprise reward account details associated with the particular entity.

In certain example embodiments, there may be a plurality of solution providers 18 for a particular solution. In these instances, the interface module 26 is configured to receive information indicative of a percentage contribution of each solution provider 18 to the solution, wherein the module 24 is configured to allocate reward points are to each solution provider 18 in accordance with their respective percentage contribution to the solution.

In a preferred example embodiment, the system 12 may be configured to motivate solution consumers 20 to utilise the same. For example, the system 12 may allocate free reward points to the solution consumers 20 when they consistently use the same.

In one example embodiment, instead of crediting the reward account of the solution provider 18, the reward point management module 24 is configured to credit the reward account of the solution provider system 14 for the amount of reward points awarded to the solution or solution provider 18. This may be the case if the solution provider 18 is, for example, employed to post solutions to the solution provider website 14.

It will be noted that in certain example embodiments, the solutions may be any information or data which solution consumers 20 feel strongly enough so as to award reward points to the solution provider 18 thereof in recognition of provision of the information or data.

The system 12 may also comprise a search engine interface module 29 configured to interface with at least one search engine (Internet keyword search engine) to provide the same with one or more of keywords associated with a particular solution, solution identifiers associated with the solution, and the reward points earned by the solution to enable the search engine to rank search results of solutions according to the reward points earned thereby. For example, Mr. X (solution provider 18) provides or posts a solution to a complex software development problem on a developer website (solution provider website 14). Mr. Y (solution consumer 20) finds the solution provided by Mr. X very useful and rewards Mr. X an amount of reward points by way of the system 12. While the financial value of the reward points accrues to Mr. X, in the present example embodiment, the information indicative thereof is uniquely associated with the solution. If many people find the solution useful and reward Mr. X in a similar fashion then the solution will have a large number of reward points associated therewith. In this regard, the module 29 is configured to transmit to a search engine keywords associated with Mr. X's solution, the amount of points associated with the solution (earned thereby) and an identifier for the solution. Should Mr. Z wish to use the search engine to search for a solution to the complex software development problem mentioned above, he would merely type in the keywords associated with the problem/desired solution into the search engine. The search engine would then list all the solutions corresponding to the keywords search in ranked order according to the reward points associated therewith, Assuming that Mr. X's solution has the most reward points associated therewith from all other solutions having the same or similar keywords associated therewith, the search engine will place Mr. X's solution at the top of the results list. Mr. Z may then access the solution (and hence the solution provider website 14) and may choose to reward the solution, solution provider 18, or solution provider system 14 as the case may be accordingly.

It will be appreciated that although the reward points awarded are earned by the solution provider system or solution provider, information indicative thereof is also conveniently associated with the solution (indentified by the solution identifier) and therefore reflects on the quality of the solution.

Example embodiments will now be further described in use with reference to Figures 3 to 9. The flow diagrams of example methods shown in Figures 3 to 9 are described with reference to Figures 1 , 2, 10, and 11, although it is to be appreciated that the example methods may be applicable to other systems (not illustrated) as well.

Referring to Figure 3 of the drawings, a flow diagram of a method of rewarding at least one solution provider 18 in a solution provider system 14 as hereinbefore described is generally indicated by reference numeral 40.

The method 40 comprises storing, at block 42 in the database 22, information indicative of a plurality of reward accounts associated with one or more of solution providers 18, solution consumers 20, and solution provider systems14. When a solution consumer 20 using the solution provider system 14, or particularly the website associated therewith, comes across a solution provided by the solution provider 20 which they are happy with, the solution consumer 20 operates a widget associated with the reward system 12 located on the solution provider website in order to reward the solution or solution provider 18 for their contribution. It will be appreciated that the solution consumer 20 may have posted a problem to which the solution provider has provided the solution to. However, this need not exclusively be the case.

Once the widget is operated, the method 40 comprises facilitating, at block 44 by way of module 26, communication between the solution provider system 14 and the reward system 12.

The method 40 may comprise generating and transmitting or facilitating generation and transmission of a banner to the solution consumer 20 as hereinbefore described.

The method 40 further comprises receiving, at block 46 by way of the reward point management module 24, a request to debit a reward account of a solution consumer 20 for an amount of reward points, as per the completed banner.

The method 40 then comprises processing the received request, at block 48 by way of the module 24 in a fashion as hereinbefore described.

The method 40 then comprises crediting, at block 50 by way of module 24, the reward account of the solution provider 18 with the amount of reward points if the reward account of the solution consumer 20 has sufficient reward points to process the request.

The method 40 may also comprise transmitting a feedback message to the solution provider system 14, the feedback message comprising information indicative of the whether the reward points were successfully awarded to the particular solution provider 18 or not, the number of points awarded, or the like. The feedback message may be transmitted after the reward points are awarded, or declined as the case may be.

It will be appreciated that in order to use the reward system 12, the solution providers 18, solution consumers 20, and solution provider system 14 may have to register to use the same.

In this iight, reference is now made to Figure 4 which illustrates a block flow diagram of a method for registering to the reward system 12. When a solution consumer 20 wishes to register to use the reward system 12 and to have an associated reward account in the database 22, the solution consumer 20 completes an online application form on the solution provider website or a website associated with the reward system 12. The module 30 receives information from the application form, which typically comprises personal data associated with the solution consumer 20 (e.g., name, e-mail address, physical and postal address, contact numbers, etc associated therewith), geographical data associated therewith, banking details of the solution consumer 20, etc. The module 30 validates the received data and hence the application and creates a profile (containing particulars of the solution consumer 20) and reward account for the solution consumer 20 in the database 22. Once this has been done, the solution consumer 20 is deemed to be registered to the reward system 12. The module 30 then transmits a registration confirmation message, for example, in the form of an e-mail message to the registered solution consumer 20 confirming registration and providing the same with their reward account details, a user reward identifier, for example, a user name in the reward system 12, and the like. The registered solution consumer 20 may at any time access the reward system 12, for example, via the website associated with the system 12 to view their reward account.

Bearing in mind that the solution consumer 20 may very well be a solution provider 18 in certain instances, the registration process described with reference to Figure 4 is similar to the registration process for a solution provider 18 as illustrated in Figure 5 and no further explanation thereof will be provided.

It will be appreciated that the solution provider system 14 may register to the system 12 in a similar fashion as described above.

Referring now to Figure 6 of the drawings which illustrates a block flow diagram of a method of purchasing reward points. An account holder (e.g., the solution consumer 20) wishing to purchase reward points completes a purchase form, typically an online form administered by the module 24.

The module 24 then validates the purchase request, for example, to determine if the account holder is a validly registered account holder.

The financial module 28 then establishes communication, typically secure communication, with the bank 15 associated with the account holder and transmits the purchase request thereto. If the purchase is successful the reward system 12 receives purchase data from the bank 15 and a bank account associated with the reward system 12 is updated with new credit.

The module 24 then updates the account holder's reward account with the newly purchased points. The newly updated reward account is then displayed to the account holder. It follows that if the purchase was not successful the system 12 displays a suitable error message to the account holder.

Referring to Figure 7 where a block flow diagram of a method or process of handling awarding of reward points is illustrated. It will be appreciated that the method illustrated in Figure 7 is more detailed than that described with reference to Figure 3.

In any event, once a solution is found by the solution consumer 20, the solution provider system 14 determines an account identifier associated with the solution provider system 14; a solution identifier associated with a particular solution provided by the solution provider 18; a user identifier of the solution consumer 20, of the particular solution; and a user identifier of the solution provider 18, of the particular solution. If more than one solution provider 18 is determined to have contributed to the solution, the system 14 determines the percentage share each account has in the reward process.

It will be appreciated that the module 26 is configured to receive all the abovementioned data determined by the solution provider system 14.

In any event, the solution provider system 14 logs onto the reward system 2 by way of the module 26. If an existing logon session exists, no logon is necessary.

Once logged on to the reward system 12, the system 12 determines if the solution provider system 14 is registered on the reward system 12 and that it has a valid reward account associated therewith. If the system 14 is validated, the module 24 associates the received user identifier of the solution consumer 20 in the solution provider system 14 with a user reward identifier of the solution consumer 20 in the reward system 12.

The module 24 then associates the received user identifier of the solution provider 18 in the solution provider system 14 with a user reward identifier of the solution provider 14 in the reward system 12. in any event, if the logon to the reward system 12 has not been successful an error message is transmitted for presentation to the solution consumer.

However, if the logon to the reward system 12 has been successful, the module 24 instructs the module 26 to generate and transmit a banner as hereinbefore described to the solution provider system 14 for display to the solution consumer 20 on the solution provider website substantially in realtime. The solution consumer 20 uses the banner to award points to the solution, and hence the solution provider/s 18. In this regard, the banner may prompt the solution consumer 20 for a score out of five stars for the solution, the number of reward point to be assigned to the solution (and hence the solution provider/s 18), as well as an optional section of questions which could provide feedback to the solution provider 18 or solution provider system 14.

The complete banner forms part of the request received by the module 24 for processing as hereinbefore described. In particular the module 24 decreases the solution consumer's reward account with the amount of points awarded and increases the solution provider/s reward account accordingly.

It follows that where there is more than one solution provider 18, the module 24 awards reward points thereto in accordance with their percentage contribution to the solution.

The system 12 advantageously transmits a confirmation message of the awarding of reward points for display on the solution provider website.

The system 12 may also transmit a feedback message to the solution provider system 14 as hereinbefore described. The feedback message and the confirmation message may be the same message or may be separate messages.

It will be appreciated that if the solution provider system 14 could not successfully log on to the reward system 12, a suitable message is transmitted thereto.

Referring to Figure 8 of the drawings where a block flow diagram for encashing or cashing reward points for their associated monetary amount is indicated. Once a solution provider 18 has received reward points and wishes to cash them or in other words exchange the reward point for a monetary value associated therewith, they complete an online encashment form, for example, on the website associated with the reward system 12.

The system 12 validates the encashment request, for example, by validating that the solution provider 18 is in fact a validly registered account holder and user of the system 12, and that the solution provider 18 has enough reward points in their respective reward account to cover the requested reward points to be cashed.

The financial management module 28 then establishes communication with the bank 15 and transfers the monetary value of the cashed reward points to the bank account associated with the solution provider 18 at the bank 15. it will be appreciated that the reward points may have a fixed monetary amount associated therewith (in a fixed currency) or may be linked to one or more financial indicators, commodities, currencies, etc.

Once the cashing is complete, the module 24 updates the solution provider's 18 reward account balance accordingly and the updated reward account balance is illustrated thereto.

If the encashment or cashing of reward points is not valid, a suitable error message is provided to the solution provider 8.

Figure 9 shows a basic block flow diagram of a method of maintaining an account in the reward system 12. When an account holder needs to update details stored in the database 22, they simply complete an online update form with the new details. The module 30 receives the updated details and proceeds to update the same in the database 22. If bank details are updated, the module 28 sends a request to the bank to validate the new details.

The system 12 then displays confirmation of the changes to the account holder. As hereinbefore mentioned, the reward points may be awarded as tips to providers of solutions/resources. For example, if a video is posted onto a solution provider website 14, the viewer (the solution consumer 20) will be able to "tip" or reward the uploader of that video (the solution provider 18) with reward points by way of the system 12 as hereinbefore described.

Similarly, a viewer will be able to tip a person who uploads a recipe on a website that provides recipes. A blogger who wrote a good story on a blogging site may be rewarded by a reader of the story via the system 12. A reader of an article on a website which provides news may be able to tip the author of the article or reporter via the system 12. A user of an internet site that provides ratings on hotels and guesthouses may be able to reward the website for supplying him with good information.

Figure 12 shows a diagrammatic representation of machine in the example form of a computer system 100 within which a set of instructions, for causing the machine to perform any one or more of the methodologies discussed herein, may be executed. In alternative embodiments_* the machine operates as a standalone device or may be connected (e.g., networked) to other machines. In a networked deployment, the machine may operate in the capacity of a server or a client machine in server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine may be a personal computer (PC), a tablet PC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellular telephone, a web appliance, a network router, switch or bridge, or any machine capable of executing a set of instructions (sequential or otherwise) that specify actions to be taken by that machine. Further, while only a single machine is illustrated, the term "machine" shall also be taken to include any collection of machines that individually or jointiy execute a set (or multiple sets) of instructions to perform any one or more of the methodologies discussed herein. The example computer system 100 includes a processor 102 (e.g., a central processing unit (CPU), a graphics processing unit (GPU) or both), a main memory 104 and a static memory 106, which communicate with each other via a bus 108. The computer system 100 may further include a video display unit 110 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 100 also includes an alphanumeric input device 12 (e.g., a keyboard), a user interface (Ul) navigation device 114 (e.g., a mouse), a disk drive unit 116, a signal generation device 118 (e.g., a speaker) and a network interface device 120.

The disk drive unit 116 includes a machine-readable medium 122 on which is stored one or more sets of instructions and data structures (e.g., software 124) embodying or utilized by any one or more of the methodologies or functions described herein. The software 124 may also reside, completely or at least partially, within the main memory 104 and/or within the processor 102 during execution thereof by the computer system 100, the main memory 104 and the processor 102 also constituting machine-readable media.

The software 124 may further be transmitted or received over a network 126 via the network interface device 120 utilizing any one of a number of well-known transfer protocols (e.g., HTTP).

While the machine-readable medium 122 is shown in an example embodiment to be a single medium, the term "machine-readable medium" should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, and/or associated caches and servers) that store the one or more sets of instructions. The term "machine-readable medium" shall also be taken to include any medium that is capable of storing, encoding or carrying a set of instructions for execution by the machine and that cause the machine to perform any one or more of the methodologies of the present invention, or that is capable of storing, encoding or carrying data structures utilized by or associated with such a set of instructions. The term "machine-readable medium" shall accordingly be taken to include, but not be limited to, solid-state memories, optical and magnetic media, and carrier wave signals.

The invention as hereinbefore described provides a way for solution consumers to show their appreciation to solution providers in a financial and more meaningful way than simply rating the solution provider's solution. The invention incentivises the provision of quality solutions and recognises their providers.

Claims

1. A reward system for rewarding at least one solution provider in a solution provider system, wherein the solution provider uploads one or more of solutions and products to the solution provider system for use by a solution consumer, the reward system comprising: a database storing information indicative of a plurality of reward accounts associated with one or more of solution providers, solution consumers, and solution provider systems, wherein the reward accounts are configured to store reward points, or information indicative thereof, and wherein each reward point has a monetary value associated therewith; a reward point management module configured to receive a request to debit a reward account of a solution consumer for an amount of reward points, to process the request, and to credit a reward account of at least one solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to process the request; and an interface module configured to enable the solution provider system to interface with the reward system such that the solution consumer using the solution provider system is able to award reward points to at least one solution provider by way of the reward system.

2. A reward system as claimed in claim 1 , further comprising a financial management module configured to enable holders of reward accounts to purchase reward points and to convert reward points to the monetary values associated therewith.

3. A reward system as claimed in claim 2, wherein the financial management module is further configured to facilitate communication with financial institutions associated with the reward account holders in order to debit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with purchased reward points and to credit financial accounts, at the respective financial institutions, associated with reward account holders for monetary values associated with cashed reward points.

4. A reward system as claimed in any one of the preceding claims, wherein solution provider system comprises a solution provider website, the interface module is therefore configured to provide a link within the solution provider website to the reward system.

5. A reward system as claimed in claim 4, wherein the interface module is configured to prompt a solution consumer for an amount of reward points which the solution consumer desires to award to the solution or solution provider.

6. A reward system as claimed in any one of the preceding claims, wherein the interface module is configured to: establish communication between the solution provider system and the reward system; receive, from the solution provider system, an account identifier associated with the solution provider system; receive, from the solution provider system, a solution identifier associated with a particular solution provided by the solution provider in the solution provider system; receive, from the solution provider system, a user identifier of the solution consumer, of the particular solution, in the solution provider system; and receive, from the solution provider system, a user identifier of the solution provider, of the particular solution, in the solution provider system.

7. A reward system as claimed in claim 6, wherein the reward point management module is configured to: associate the received user identifier of the solution consumer in the solution provider system with a user reward identifier of the solution consumer in the reward system; associate the received user identifier of the solution provider in the solution provider system with a user reward identifier of the solution provider in the reward system; and facilitate prompting the solution consumer, at the solution provider system, for an amount of reward points which the solution consumer requests to be awarded to the solution provider.

8. A reward system as claimed in claim 7, wherein the reward point management module is configured to: determine the amount of reward points which the solution consumer has in their respective reward account; debit the amount of reward points from the reward account of the solution consumer and credit the reward account of the solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to cover the amount requested to be awarded to the solution provider; and at least provide a suitable message to the solution consumer if the reward account of the solution consumer has insufficient reward points to cover the amount requested to be awarded to the solution provider.

9. A reward system as claimed in any one of the preceding claims, further comprising a registration module configured to: receive particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to open a reward account therefor respectively; receive updated particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to update an existing reward account therefor respectively; associate and store particulars associated with the respective solution provider, solution consumer, and solution provider system in the database.

10. A reward system as claimed in any one of the preceding claims, wherein instead or crediting the reward account of the solution provider, the reward point management module is configured to credit the reward account of the solution provider system for the amount of reward points awarded to the solution or solution provider.

11. A reward system as claimed in any one of the preceding claims, wherein there are a plurality of solution providers for a particular solution, wherein the interface module is configured to receive information indicative of a percentage contribution of each solution provider to the solution, and wherein the reward points are allocated to each solution provider in accordance with their respective percentage contribution to the solution.

12. A reward system as claimed in any one of the preceding claims, the reward system further comprising a search engine interface module configured to interface with at least one search engine to provide the same with one or more of keywords associated with a particular solution, solution identifiers associated with the solution, and the reward points earned by the solution to enable the search engine to rank search results of solutions according to the reward points earned thereby.

13. A method of rewarding at least one solution provider in a solution provider system by way of a reward system, wherein the solution provider uploads one or more of solutions and products to the solution provider system for use by a solution consumer, the method comprising: storing, in a database, information indicative of a plurality of reward accounts associated with one or more of solution providers, solution consumers, and solution provider systems, wherein the reward accounts are configured to store reward points, or information indicative thereof, and wherein each reward point has a monetary value associated therewith; facilitating communication between a solution provider system and the reward system such that, in use, a solution consumer using the solution provider system to obtain solutions or products is able to award reward points to at least one solution provider by way of the reward system; receiving, by way of a reward point management module, a request to debit a reward account of a solution consumer for an amount of reward points, processing the received request, and crediting a reward account of at least one solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to process the request.

14. A method as claimed in claim 13, comprising: establishing communication with financial institutions associated with the reward account holders; debiting financial accounts, at the respective financial institutions by way of a financial module, associated with reward account holders for monetary values associated with purchased reward points; and crediting financial accounts, at the respective financial institutions by way of the financial module, associated with reward account holders for monetary values associated with cashed reward points.

15. A method as claimed in either claim 13 or 14, comprising providing a link within a solution provider website of the solution provider system to the reward system.

16. A method as claimed in claim 15, comprising prompting a solution consumer for an amount of reward points which the solution consumer desires to award to the solution or solution provider.

17. A method as claimed in any one of claims 13 to 16, further comprising: establishing communication between the solution provider system and the reward system; receiving, from the solution provider system, an account identifier associated with the solution provider system; receiving, from the solution provider system, a solution identifier associated with a particular solution provided by the solution provider in the solution provider system; receiving, from the solution provider system, a user identifier of the solution consumer, of the particular solution, in the solution provider system; and receiving, from the solution provider system, a user identifier of the solution provider, of the particular solution, in the solution provider system.

18. A method as claimed in claim 17, further comprising: associating the received user identifier of the solution consumer in the solution provider system with a user reward identifier of the solution consumer in the reward system; associating the received user identifier of the solution provider in the solution provider system with a user reward identifier of the solution provider in the reward system; and prompting the solution consumer, at the solution provider system, for an amount of reward points which the solution consumer requests to be awarded to the solution provider.

19. A method as claimed in claim 18, comprising: determining the amount of reward points which the solution consumer has in their respective reward account; debiting the amount of reward points from the reward account of the solution consumer and crediting the reward account of the solution provider with the amount of reward points if the reward account of the solution consumer has sufficient reward points to cover the amount requested to be awarded to the solution provider; and at least providing a suitable message to the solution consumer if the reward account of the solution consumer has insufficient reward points to cover the amount requested to be awarded to the solution provider.

20. A method as claimed in claim 19, further comprising: transmitting a questionnaire to the solution consumer, the questionnaire comprising questions to provide feedback to the solution provider or the solution provider system; and transmitting a suitable message to one or more of the solution provider, solution consumer, and solution provider system, on a successful debiting of the reward account of the solution consumer and crediting the reward account of the solution provider for the amount of reward points.

21. A method as claimed in any one of claims 13 to 20, further comprising: receiving particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to open a reward account therefor respectively; receiving updated particulars associated with one or more of a solution provider, a solution consumer, and a solution provider system in order to update an existing reward account therefor respectively; and associating and storing particulars associated with the respective solution provider, solution consumer, and solution provider system in the database.

22. A method as claimed in any one of claims 13 to 21, wherein should there be a plurality of solution providers for a particular solution, the method comprises: receiving information indicative of a percentage contribution of each solution provider to the solution; and allocating or awarding reward points to each solution provider in accordance with their respective percentage contribution to the solution.