JP2010113659A - Donation management device - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a donation management device for appropriately feeding back how point contribution or donations are used to those who have donated and for promoting donation activities. <P>SOLUTION: The donation management device includes: a means for receiving application of point contribution or donations accompanying purpose restriction in which a donated party is designated by a user to register the application to a donation management database; a means for totalizing donation application registered to the donation management database by donated party, displaying products within a range of purpose restriction, and transmitting data of a donation situation notification picture incorporating purchase buttons including links to a purchase page where products are purchased to respective donated parties; a means for receiving contents of the product purchase by the purchase page; and a means for notifying a user of a donating user of a received content of the product purchase. <P>COPYRIGHT: (C)2010,JPO&INPIT

Description

  The present invention relates to a technique for making a donation via a network such as the Internet.

  In portal sites on the Internet, in order to secure stable users and promote the use of services provided, points are often obtained by using various services for registered users. The acquired points can be used for product purchases in online shopping.

  However, there are many cases in which some registered users do not actively use points and leave points to accumulate. For such registered users, the effect of incentive to use the service by providing points is scarce, which is one factor that hinders the increase in service users.

  One way to use points is to donate to the volunteer group (funds), and it is expected to promote the use of points by registered users who are interested in social issues.

Patent Document 1 does not target acquisition points by registered users of portal sites, but there is a technology that uses service points for each sales store used in accordance with commercial transactions for fund-raising while using the Internet. Proposed.
JP 2006-134265 A

  However, in the technique disclosed in Patent Document 1 described above, donation points are only counted and then cashed and transferred to a donation destination, so the donor knows how the donated points were used. I can't do it, and I don't feel that it has helped others. Therefore, don't bother to donate again, and donation activities are stagnant, making it difficult to establish a stable point usage method.

  Although the point donation has been described, there is a similar problem in that when donating cash via a network such as the Internet, donation activities are stagnant because it is unknown how the donation is used.

  The present invention has been proposed in view of the above-mentioned conventional problems, and the purpose of the present invention is to accurately feed back the use status of points or cash donation to the person who has donated and encourage donation activities. It is to provide a donation management device that can do.

  In order to solve the above-described problems, in the present invention, as described in claim 1, a donation management database accepting an application for a point or cash donation with a limited use designating a donation destination from a user. And a purchase button including a link to a purchase page for collecting the donation registered in the donation management database for each donation destination, displaying the product within a limited range of use, and purchasing the product. Means for transmitting the data of the incorporated donation status notification screen to each donation destination, means for receiving the content of the product purchase by the purchase page, means for notifying the user of the donation of the content of the received product purchase, The gist of the donation management device with

  In addition, as described in claim 2, in the donation management device according to claim 1, the contents of the product purchase notified to the user include the name of the donation destination, the name of the purchased product, and the points used. Can be included.

  In addition, as described in claim 3, in the donation management device according to claim 1, the transmission of the donation status notification screen includes a URL link to the donation status notification screen. This can be done by sending an e-mail and sending the donation status notification screen in response to access via the URL link.

  In addition, as described in claim 4, a step of accepting an application for a point or cash donation with a limited use specifying a donation destination from a user and registering it in the donation management database; Donation status notification screen data that includes a purchase button that includes a link to the purchase page that displays the products within a limited range of usage and links to the purchase page is displayed for each donor. It can be configured as a donation management method including a step of transmitting to the user, a step of receiving the content of the product purchase by the purchase page, and a step of notifying the user of the donation of the content of the received product purchase.

  In the donation management device of the present invention, it is possible to accurately feed back the use status of points or cash donation to the person who has donated, thereby promoting the donation activity.

  When applied to donation of points, it becomes easy to establish a stable point use method, and the effect of inducing service use by giving points can be improved.

  Further, by limiting the use of donated points or cash to the online shopping service within the same operator, it is possible to contribute to the activation of the online shopping service.

  Hereinafter, preferred embodiments of the present invention will be described. In addition, although the following embodiment demonstrates the case where the point which a user (general user) holds is donated, it can replace with a point and can be applied to the donation in cash.

<Configuration>
FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.

  In FIG. 1, a network 1 such as the Internet is connected with a plurality of terminals 2 such as PCs (Personal Computers), PDAs (Portable Digital Assistants), mobile phones, etc. operated by general users, and a person in charge of a volunteer group operates them. A plurality of terminals 3 such as PCs, PDAs, and mobile phones are connected. The terminals 2 and 3 include general browsers (Web browsers) 21 and 31 and mailers 22 and 32.

  On the other hand, various network groups 4 for members including a shopping server 41 and a donation management server 5 are connected to the network 1.

  The donation management server 5 includes a donation content receiving unit 501, a donation status notification unit 502, a purchase purpose monitoring unit 503, and a purchase status notification unit 504 as functional units. These functional units are realized by a computer program executed on hardware resources such as a CPU (Central Processing Unit), a ROM (Read Only Memory), and a RAM (Random Access Memory) of the computer constituting the donation management server 5. Is. These functional units do not need to be arranged on a single computer, and may be distributed as necessary.

  The donation management server 5 includes a user management database 511, a volunteer group management database 512, and a donation management database 513 as databases. These databases systematically hold data on a storage medium such as an HDD (Hard Disk Drive) in the donation management server 5. The user management database 511 can be omitted by using the database in the case where there is a database for managing user information in the member server group 4 in a unified manner.

  The donation contents receiving unit 501 has a function of receiving donation contents from the shopping server 41 and registering them in the donation management database 513 based on the point donation operation performed by the general user at the shopping server 41. The donation operation is performed by specifying a volunteer group and a donation point, and limiting the purchase purpose. The reason why the point donation operation is performed in the shopping server 41 is that donation is part of the use of points and is considered to be closely related to the purchase of goods. Further, by allowing the shopping server 41 to perform a point donation operation, there is an advantage that the subtraction of the point balance and the like can be substituted with an existing product purchase mechanism. However, technically, the donation operation may be performed on any server.

  The donation status notification unit 502 has a function of periodically counting the donation status from the donation management database 513 for each volunteer group and notifying each volunteer group of the donation status by e-mail or the like. The donation status to be notified to the volunteer group includes a purchase button with a link that allows purchase items to be purchased at the shopping server 41 within the scope of the limited purchase use, as well as a limited purchase purpose. .

  The purchase usage monitoring unit 503 has a function of receiving purchase contents of a product made by the shopping server 41 based on the notification of the donation status by the volunteer group from the shopping server 41 and registering it in the donation management database 513.

  The purchase status notification unit 504 has a function of notifying purchase contents by e-mail or the like to a general user who has contributed points that are the basis of purchase when receiving purchase contents from the purchase purpose monitoring unit 503. ing. Note that the purchase status notification unit 504 does not receive purchase contents from the purchase purpose monitoring unit 503 every time a purchase is made by a volunteer group, but periodically counts the donation management database 513 to provide purchase contents to general users. May be notified by e-mail or the like.

  FIG. 2 is a diagram illustrating examples of data structures of various databases.

  FIG. 2A shows an example of the data structure of the user management database 511, and includes items such as “user ID”, “profile (age, region, sex)”, “point balance”, and “mail address”. “User ID”, “Profile (age, region, sex)” and “Mail address” are values set at the time of member registration. The “point balance” is a value given (added) by using the various server groups 4 for members (FIG. 1) and consumed (subtracted) by using the points at the shopping server 41 or the like.

  FIG. 2B shows an example of the data structure of the volunteer group management database 512, and includes items such as “volunteer group ID”, “group name”, “location”, and “mail address”. These items are values set when registering a volunteer group.

  FIG. 2C shows an example of the data structure of the donation management database 513. “Donation ID” “Volunteer organization ID” “User ID” “Donation points” “Use limited” “Reception date” “Purchase history” “Points” It has items such as “Balance”. “Donation ID” is an identifier assigned to each donation of a general user. “Volunteer group ID” is an identifier indicating the volunteer group that has made a donation. “User ID” is an identifier of a general user who has made a donation. “Donated points” is the value of points donated. “Use limited” is a use designated by a general user when donating points. “Reception date” is the date on which the donation of points was accepted. “Purchase history” is a history of the details (purchase date, product name, usage points, etc.) of the product purchase made at the point by the volunteer group. The “point balance” is a balance after being consumed by purchasing a product.

<Operation>
FIG. 3 is a sequence diagram showing a processing example of the above embodiment.

  In FIG. 3, it is assumed that the general user has already accessed the shopping server 41 from the browser 21 of the terminal 2, has performed a login process (input of a user ID, a password, etc.), and the session has been confirmed by a cookie or the like.

  In this state, when a general user requests a donation acceptance page from the browser 21 of the terminal 2 to the shopping server 41 by specifying a volunteer organization as a donation destination (step S1), the shopping server 41 displays the browser 21 of the terminal 2. The data of the donation acceptance page is transmitted to (Step S2), and the browser 21 of the terminal 2 displays the donation acceptance page. FIG. 4A shows a screen example of a donation acceptance page, which includes a donation destination display field 201, a donation point input field 202, a use limitation selection field 203, and a donation execution button 204.

  Returning to FIG. 3, the general user makes a desired input to the donation acceptance page from the browser 21 of the terminal 2 (step S3). FIG. 4B shows an example of a state where an input has been made on the donation acceptance page, in which “100” is input in the donation point input field 202 and “stationery” is selected from the use limitation selection field 203. Is shown.

  Returning to FIG. 3, the donation content is transmitted from the browser 21 of the terminal 2 to the shopping server 41 by pressing the donation execution button or the like on the donation reception page (step S <b> 4).

  The shopping server 41 confirms that the point usage is within the range of the general user's point balance (“point balance” in the user management database 511 in FIG. 2A) by a mechanism for normal product purchases by points. Then, the donation points are subtracted from the point balance, and the donation contents are transmitted to the donation contents receiving unit 501 of the donation management server 5 (step S5). The donation content to be transmitted includes the volunteer organization ID of the volunteer organization to which the contribution is made, the user ID of the donor, the donation point, and limited use. When the donation points exceed the point balance, the shopping server 41 displays an error message indicating that the donation content is not appropriate for the browser 21 of the terminal 2.

  When receiving the donation content from the shopping server 41, the donation content receiving unit 501 registers the donation content in the donation management database 513 (step S6). That is, in the donation management database 513 in FIG. 2C, a new donation ID is issued and set in the “donation ID” field, and the volunteer organization ID, user ID, donation point, and use limitation of the donation contents are set as “volunteer organization”. Set in the “ID”, “User ID”, “Donation Points”, “Usage Restricted” fields, and set the current date to “Reception Date”.

  Returning to FIG. 3, after that, the donation status notification unit 502 of the donation management server 5 creates data for displaying the donation status notification by totaling the data of the donation management database 513 for each volunteer organization ID by periodic processing. (Step S7) The mail address of the volunteer group is acquired from the volunteer group management database 512 using the volunteer group ID as a key (Step S8), and the mail is transmitted to the terminal 3 of the volunteer group (Step S9). The email to be sent does not include the donation status notification display data itself, but includes an access URL (Uniform Resource Locator) to the display data. The mail transmission is actually performed to the mail server, and the mail message is acquired from the mailer 32 of the terminal 3 to the mail server mailbox. However, the mail server is omitted in the figure. Notification may be performed by IM (Instant Messaging) or the like instead of notification by mail.

  The mailer 32 of the terminal 3 that has received the donation status notification email displays the content of the email and then displays a donation status notification screen by the browser 31 via the access URL. FIG. 5 is a diagram illustrating an example of a donation status notification screen. The donation status notification includes a bibliographic item column 301 such as “donation ID”, “acceptance date”, “user ID”, “point”, and “use limitation”. And a purchase button field 302 in which a purchase button including a link to a purchase page for a product indicated for limited use is arranged. For example, when a purchase button corresponding to the use-limited “stationery” is pressed, a link is made to a stationery purchase page. Further, the URL transmitted to the link destination at the time of linking indicates that the transition to the purchase page has been performed based on the donation status notification, and the shopping server 41 side notifies the donation management server 5 of the purchase contents later. The access URL and donation ID of the donation management server 5 are added as URL parameters.

  Returning to FIG. 3, when the person in charge of the volunteer group presses a desired purchase button from the donation status notification screen displayed by the browser 31 of the terminal 3 (step S10), the browser 31 of the terminal 3 is embedded in the purchase button. A page request is made to the shopping server 41 according to the link (step S11), and the shopping server 41 responds to the browser 31 of the terminal 3 with the corresponding purchase page (step S12). FIG. 6A shows an example of a purchase page screen, and shows an example of a purchase page corresponding to the use-limited “stationery”. Here, products such as “pencil” and “eraser” are displayed in the product column 311, points “100” and “50” necessary for purchase are displayed in the point column 312, and a purchase button corresponding to the purchase button column 313 is displayed. Has been placed. By pressing one of the purchase buttons from the purchase button column 313, the confirmation screen shown in FIG. 6B is displayed, and it is determined that there is no problem with the contents of the purchase content column 314 and the confirmation button 315 is pressed. The purchase is confirmed. Although it is assumed that the transition from the purchase page in FIG. 6A to the confirmation screen in FIG. 6B is performed by the operation of a script or the like in the page, the shopping server 41 is pressed by pressing the purchase button on the purchase page. May be accessed once, and the display data of the confirmation screen may be sent from the shopping server 41.

  Returning to FIG. 3, the person in charge of the volunteer group performs a purchase operation based on the purchase page displayed by the browser 31 of the terminal 3 (pressing the purchase button from the purchase button column 313 in FIG. 6A and FIG. 6B). When the confirmation button 315 is pressed (step S13), the browser 31 of the terminal 3 transmits a purchase request to the shopping server 41 (step S14), and the shopping server 41 makes a purchase to the browser 31 of the terminal 3. A confirmation response is returned (step S15). Further, the shopping server 41 sends the purchase contents to the purchase usage monitoring unit 503 of the donation management server 5 based on the access URL and donation ID of the donation management server 5 acquired at the time of transition from the donation status notification to the purchase page. Is transmitted (step S16). This purchase content includes a donation ID, a product (name), a purchase point, and a purchase date.

  Upon receiving the purchase contents from the shopping server 41, the purchase purpose monitoring unit 503 of the donation management server 5 accesses the donation management database 513 using the donation ID included in the purchase contents as a key, sets (appends) purchase history, and points The balance is updated (step S17). Thereafter, the purchase purpose monitoring unit 503 of the donation management server 5 transfers the purchase contents to the purchase status notification unit 504 (step S18).

  The purchase status notifying unit 504 that has received the transfer of the purchase contents acquires the volunteer group ID from the donation management database 513 using the donation ID included in the purchase contents as a key, and uses the volunteer group ID as a key for the volunteer group management database 512. The organization name and e-mail address are acquired from (step S19). Then, a purchase status e-mail is generated using the product and purchase point of the purchase content and the group name acquired by the database search (step S20), and a purchase status notification is sent to the terminal 2 with the e-mail address acquired by the database search as the destination. The mail is transmitted (step S21). The mail transmission is actually performed to the mail server, and the mail message is acquired from the mailer 22 of the terminal 2 to the mail server mailbox, but the mail server is omitted in the figure. Notification may be performed by IM or the like instead of notification by mail.

  FIG. 7 is a diagram showing an example of a purchase status notification screen, showing an example of an e-mail with the title “Point Usage Report” and “XX NPO has purchased 100 pencils”.

  General users who operate the terminal 2 can know that their donated points have been used for actual product purchases by volunteer organizations that donated in accordance with the designated use restrictions, and get a sense that they have been useful to others. Can do. Therefore, it is possible to encourage motivation to donate again and encourage donation activities. Therefore, it becomes easy to establish as a stable point use method, and it is possible to improve the effect of inducing service use by giving points.

  Further, since the donated points are used in the online shopping service within the same operator, it is possible to contribute to the activation of the online shopping service.

<Summary>
The present invention has been described above by the preferred embodiments of the present invention. While the invention has been described with reference to specific embodiments, various modifications and changes may be made to the embodiments without departing from the broad spirit and scope of the invention as defined in the claims. Obviously you can. In other words, the present invention should not be construed as being limited by the details of the specific examples and the accompanying drawings.

It is a figure which shows the structural example of the system concerning one Embodiment of this invention. It is a figure which shows the data structure example of various databases. It is a sequence diagram which shows the process example of embodiment. It is a figure which shows the example of a screen of a contribution reception page. It is a figure which shows the example of a screen of a donation status notification. It is a figure which shows the example of a screen, such as a purchase page. It is a figure which shows the example of a screen of purchase condition notification.

Explanation of symbols

1 network 2 terminal 21 browser 22 mailer 201 donation destination display field 202 donation point input field 203 limited use selection field 204 donation execution button 3 terminal 31 browser 32 mailer 301 bibliographic item field 302 purchase button field 311 product field 312 point field 313 purchase button Field 314 Purchase content field 315 Confirmation button 4 Various server groups for members 41 Shopping server 5 Donation management server 501 Donation content receiving unit 502 Donation status notification unit 503 Purchase usage monitoring unit 504 Purchase status notification unit 511 User management database 512 Volunteer organization management database 513 Donation Management Database

Claims (4)

A means of accepting applications for point-of-use or cash donations that specify donations from users and registering them in the donation management database;
A donation status notification screen that incorporates a purchase button that includes a link to a purchase page that aggregates the donation registrations registered in the donation management database for each donation destination, displays the products within a limited range of use, and purchases the products. Means to send the data to each donor,
Means for receiving the content of the product purchase by the purchase page;
A donation management device comprising means for notifying a user of a donation of the contents of a received product purchase. In the donation management device according to claim 1,
A donation management apparatus characterized in that the contents of the product purchase notified to the user include the name of the donation destination, the name of the purchased product, and the points used. In the donation management device according to claim 1 or 2,
The donation status notification screen is transmitted by transmitting an email including a URL link to the donation status notification screen and transmitting the donation status notification screen in response to access via the URL link. A special donation management device. Accepting applications for point-of-use or cash donations that specify donations from users and registering them in the donation management database;
A donation status notification screen that incorporates a purchase button that includes a link to a purchase page that aggregates the donation registrations registered in the donation management database for each donation destination, displays the products within a limited range of use, and purchases the products. Sending the data to each donor,
Receiving the contents of the product purchase by the purchase page;
A donation management method comprising: a step of notifying a user of a donation of the contents of the received product purchase.

Images