Stamp card management device and stamp card management method

The system allows a single stamp card to be used across multiple communities by associating it with community identification, facilitating cross-community usage and encouraging visits with incentives, while allowing operators to choose point costs.

JP2024165326AActive Publication Date: 2024-11-28RAKUTEN GROUP INC
View PDF 4 Cites 0 Cited by

Patent Information

Application Number
JP2023081438
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-17
Publication Date
2024-11-28
Estimated Expiration
2043-05-17

AI Technical Summary

Technical Problem

Existing stamp card systems require users to carry multiple cards for different businesses, limiting their usability across different communities and preventing stamps from being shared or recognized across different business operators.

Method used

A system that allows a stamp card creator to designate multiple communities, associating stamp card identification information with community identification information, and stamps the card when the user's location is within the designated community areas, enabling a single stamp card to be used across multiple communities.

Benefits of technology

Enables a single stamp card to be used across multiple communities, encouraging users to visit associated locations and providing incentives through stamp accumulation and community membership, while allowing operators to choose whether to bear the cost of awarding points.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024165326000001_ABST
    Figure 2024165326000001_ABST
Patent Text Reader

Abstract

To enable a creator of a stamp card to designate two or more communities and to create stamp cards that can be commonly used in places related to the designated communities.SOLUTION: In a communication system, an SNS server acquires two or more pieces of community identification information identifying each of two or more designated communities, stores stamp card identification information in an identification information storage in association with the two or more pieces of community identification information, acquires location information indicating a location of a portable user terminal, and puts a stamp on a stamp card for a user of the user terminal if the location indicated by the location information is included in a region indicated by region information associated with any of the two or more pieces of community identification information associated with the stamp card identification information of the region information stored in a region information storage.SELECTED DRAWING: Figure 7
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to a method for stamping a user's stamp card on the condition that the user visits a particular location. [Background technology]

[0002] Conventionally, there is known a service that stamps a stamp card owned by a user when the user visits a specific place. For example, a business operator that operates a store issues a stamp card to the user. When the user uses the store, a stamp is pressed on the user's stamp card. When a certain number of stamps are accumulated, the user is generally able to receive some kind of benefit from the business operator's store. Also, a technology is known for managing electronic stamp cards, rather than tangible stamp cards such as pieces of paper.

[0003] Such stamp cards are usually different for each business. Therefore, when a user uses stores of multiple business operators, the user needs to have multiple stamp cards. Also, the user cannot use a stamp that is stamped at a store of one business operator at a store of another business operator. In relation to this situation, Patent Document 1 discloses a technology for using a common stamp at multiple stores. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] JP 2019-91146 A Summary of the Invention [Problem to be solved by the invention]

[0005] For example, assume that an Internet community related to a specific place is created, and information related to the place is provided within this community. Members of the community can share information related to the place online. It is conceivable to provide a service of creating a stamp card for such a community and stamping the stamp card for users who have visited a place related to the community. When providing such a service, it is convenient to be able to specify separate communities with different related places and create a common stamp card for these communities.

[0006] The present invention has been made in consideration of the above points, and one example of its objective is to provide a stamp card management device and a stamp card management method that enable a stamp card creator to specify two or more communities and create a stamp card that can be commonly used in locations related to the specified communities. [Means for solving the problem]

[0007] One aspect of the present invention is characterized in that it comprises an acquisition means for acquiring two or more community identification information that identifies two or more communities designated by a creator who creates a stamp card, among a plurality of different communities in which information related to each predetermined area is provided within the community; an identification information storage control means for storing in an identification information storage means a stamp card identification information that identifies the stamp card to be created, in association with the acquired two or more community identification information; an acquisition means for acquiring location information indicating a location of a portable terminal device; and a stamp means for executing a stamp process for pressing a stamp on the stamp card for a user of the terminal device when the location indicated by the acquired location information is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information, among the area information stored in an area information storage means that stores area information indicating the area related to the community, in association with the community identification information that identifies the community, for each of the plurality of communities.

[0008] According to this aspect, the creator of the stamp card can specify two or more communities among the multiple communities. The stamp card identification information of the stamp card to be created is stored in the identification information storage means in association with the community identification information of each of the two or more communities specified. In addition, the area information storage means stores area information indicating an area related to each of the multiple communities in association with the community identification information of the community. If the location of the terminal device is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information, a stamp process is executed to stamp the stamp card for the user of the terminal device. Therefore, even if the community associated with the area where the user went corresponds to any of the two or more communities specified by the creator of the stamp card, the user can have the stamp stamped on the stamp card. Therefore, the creator of the stamp card can specify two or more communities and create a stamp card that can be commonly used in places related to the specified communities.

[0009] Another aspect of the present invention is characterized in that the device further comprises a joining means for executing a process of joining the user to the community identified by the community identification information associated with any of the area information stored in the area information storage means when the location indicated by the acquired location information is included in the area indicated by any of the area information stored in the area information storage means.

[0010] According to this aspect, a user can join a community by going to an area associated with that community. It is believed that a user goes to a particular area because he or she has a certain level of interest in things in that area. Thus, a community can be formed by users who have a certain level of interest in the subject of information exchange in the community.

[0011] Yet another aspect of the present invention is characterized in that, for each of the two or more communities, either non-stamp information indicating that the stamp has not been pressed or stamp information indicating that the stamp has been pressed is stored in a stamp information storage means in association with the stamp card identification information and user identification information identifying the user who has the created stamp card, and when the non-stamp information is stored in the stamp information storage means in association with the stamp card identification information and the user identification information identifying the user of the terminal device for a community among the two or more communities indicated by the community identification information associated with the area information indicating the area including the location indicated by the acquired location information, the stamp means changes the non-stamp information to the stamp information as the stamp processing, and when the number of the stamp information stored in the stamp information storage means in association with the stamp card identification information and the user identification information reaches a predetermined number, a privilege is granted to the user identified by the user identification information.

[0012] According to this aspect, the stamp information storage means stores non-stamp information indicating that no stamp has been applied or stamp information indicating that a stamp has been applied for each community in association with the stamp card identification information and the user identification information. If non-stamp information is stored in the stamp information storage means for a community related to an area visited by the user, the non-stamp information is changed to a stamp change. That is, the user can have a stamp applied to the stamp card for that community. If stamp information is stored in the stamp information storage means for that community, there is no particular change. That is, since a stamp has already been applied to the stamp card for that community, no further stamps are applied. Then, when the number of communities with stamps applied reaches a predetermined number, a privilege is given to the user. Thus, a stamp rally can be realized in which the user visits two or more areas related to each of two or more communities designated by the creator of the stamp card.

[0013] Yet another aspect of the present invention is characterized in that the two or more communities are two or more business communities in which information related to two or more different businesses that each sell a trading object is provided within the community, each of the two or more businesses sells the trading object at a facility associated with the business, and for each of the two or more businesses, the area indicated by the area information associated with the community identification information that identifies the business community associated with the business includes the location of the facility associated with the business.

[0014] According to this aspect, the creator of the stamp card designates communities related to different businesses as the two or more communities. By visiting a facility related to any one of the two or more businesses, the user can have a stamp placed on the stamp card. Therefore, a stamp card common to two or more businesses can be created as a stamp card that encourages the user to visit the facility.

[0015] In still another aspect of the present invention, the stamping means executes the stamping process on condition that the user is a member of at least one of the two or more communities.

[0016] According to this aspect, if a user is a member of at least one of two or more communities designated by the creator of the stamp card, the user can have the stamp pressed, thus encouraging the user to join the community.

[0017] Yet another aspect of the present invention is characterized in that the two or more areas indicated by the two or more pieces of area information stored in the area information storage means for each of the two or more communities include locations that are different from each other.

[0018] According to this aspect, two or more communities, each of which may relate to a different location, are designated by the creator of the stamp card.

[0019] In yet another aspect of the present invention, the terminal device further includes an assigning means for executing an assigning process of assigning points of a point program to a user of the terminal device when the stamp process is executed by the stamping means.

[0020] According to this aspect, it is possible to encourage users to go to areas related to the community designated by the creator of the stamp card.

[0021] Yet another aspect of the present invention is characterized in that a first billing amount to be billed to the creator for the granting of the points is stored in a billing amount storage means, a second billing amount to be billed to an administrator of one of the multiple communities that has chosen to bear the cost of granting the points is stored in the billing amount storage means, and when the granting process is executed by the granting means, the system further includes an update means for updating at least one of the stored first billing amount and second billing amount, wherein when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that does not bear the cost, the update means adds the entire cost burden amount for granting the points to the first billing amount, and when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that does bear the cost, the update means adds at least a portion of the cost burden amount to the second billing amount, and the sum of the first additional amount added to the first billing amount and the second additional amount added to the second billing amount becomes the cost burden amount.

[0022] According to this aspect, the manager of each community can choose whether or not to bear the costs for granting points. If the user goes within an area related to a community whose manager does not bear the costs, the creator of the stamp card bears the costs equivalent to the entire cost of granting points. On the other hand, if the user goes within an area related to a community whose manager bears the costs, the manager of that community bears the costs that are at least a part of the cost of granting points. The sum of the costs borne by the creator of the stamp card and the costs borne by the manager of the community is the cost of granting points. Therefore, the costs can be billed to an appropriate billing party depending on whether the manager of the community bears the costs.

[0023] Yet another aspect of the present invention is characterized in that the update means adds the entire amount of the cost to the second billing amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost.

[0024] According to this aspect, when a user enters an area related to a community for which the operator bears the costs, the operator of the community bears the costs equivalent to the entire cost of awarding the points.

[0025] Yet another aspect of the present invention further comprises a screen information transmitting means for transmitting to a creator terminal device used by the creator screen information that displays a screen on which each of the community display information indicating at least a portion of the multiple communities is displayed in a manner corresponding to a display priority of the community display information, and that is capable of accepting an operation to select at least one of the community display information displayed on the screen, wherein the acquiring means acquires from the creator terminal device the community identification information that identifies the community indicated by the community display information selected by the creator from the screen, and the screen information transmitting means generates the screen information by setting the priority of the community display information indicating communities that will bear the cost, among the at least a portion of the communities, higher than the priority of the community display information indicating communities that will not bear the cost.

[0026] According to this aspect, community display information indicating at least some of the communities is displayed on a screen for selecting a community for which points are to be awarded by stamping a stamp card to a user who visits the area. Each community display information is displayed in a manner according to a display priority determined for the community display information. For example, the higher the display priority of the community display information, the higher the display priority of the community display information. Therefore, the higher the display priority of the community display information, the higher the probability that the community display information will be selected from the screen. The display priority of the community display information of a community whose manager bears the cost for awarding points is higher than the display priority of the community display information of a community whose manager does not bear the cost. Therefore, the probability that a community whose manager bears the cost for awarding points is selected can be higher than the probability that a community whose manager does not bear the cost is selected. Therefore, it is possible to urge the manager of the community to bear the cost for awarding points.

[0027] Yet another aspect of the present invention is characterized in that the system further includes a burden rate acquisition means for acquiring a burden rate specified by an administrator of the community that will bear the cost of granting the points, and when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost, the update means adds the second additional amount equivalent to the acquired burden rate to the second billing amount for the cost burden amount, and adds the first additional amount equivalent to the difference between the cost burden amount and the second additional amount to the first billing amount.

[0028] According to this aspect, the administrator of a community that chooses to bear the cost of granting points specifies the burden rate. When a user enters an area related to the community, the administrator of the community bears the cost of granting points in an amount equivalent to the specified burden rate. The creator of the stamp card bears the cost obtained by deducting the amount borne by the administrator of the community from the burden amount.

[0029] Yet another aspect of the present invention further comprises a screen information transmitting means for transmitting to a creator terminal device used by the creator screen information that displays a screen on which each of the community display information indicating at least a portion of the plurality of communities is displayed in a manner corresponding to a display priority of the community display information, and that is capable of accepting an operation to select at least one of the community display information displayed on the screen, wherein the acquiring means acquires from the creator terminal device the community identification information that identifies the community indicated by the community display information selected by the creator from the screen, and the screen information transmitting means generates the screen information by increasing the priority of the community display information indicating the community, the higher the burden rate specified by an administrator of the community.

[0030] According to this aspect, community display information indicating at least some of the communities is displayed on a screen for selecting a community for which points are to be awarded by stamping a stamp card to a user who visits the area. Each community display information is displayed in a manner according to a display priority determined for the community display information. For example, the higher the display priority of the community display information, the higher the display priority of the community display information. Therefore, the higher the display priority of the community display information, the higher the probability that the community display information will be selected from the screen. The higher the burden rate specified by the manager of the community, the higher the display priority of the community display information of the community. Therefore, the higher the burden rate specified by the manager, the higher the probability that the community will be selected. Therefore, it is possible to encourage the manager of the community to increase the burden rate for the cost of awarding points.

[0031] Yet another aspect of the present invention further comprises a number acquisition means for acquiring the number of users who have been granted points by the granting means and who have been granted points because their terminal device was located within the area indicated by the area information associated with the community identification information that identifies the community for which the operator bears the costs, and a recommendation information sending means for sending recommendation information indicating a recommended burden rate to an operator terminal device used by the operator who bears the costs, the recommendation information sending means setting the recommended burden rate to a higher number of users acquired, wherein the burden rate acquisition means acquires the specified burden rate from the operator terminal device to which the recommendation information is sent.

[0032] According to this aspect, the number of users who have had their stamp cards stamped and points awarded by going into an area related to a community for which the operator bears the cost of awarding points is obtained. The fewer the number of users, the higher the burden rate is recommended to the operator. The operator can specify an actual burden rate with reference to the recommended burden rate. The higher the designated burden rate, the higher the probability that the community will be selected by the creator of the stamp card. Since points are awarded to users who go into an area related to the selected community, if the number of users going into the area related to the community is small, the number can be increased.

[0033] Yet another aspect of the present invention is a stamp card management method executed by a computer, comprising: an acquisition step of acquiring two or more community identification information identifying two or more communities designated by a creator who creates a stamp card from among a plurality of different communities in which information related to each of the predetermined areas is provided within the community; an identification information storage control step of storing stamp card identification information identifying the stamp card to be created in an identification information storage means in association with the acquired two or more community identification information; an acquisition step of acquiring location information indicating the location of a portable terminal device; and a stamp step of executing a stamp process of pressing a stamp on the stamp card for a user of the terminal device when the location indicated by the acquired location information is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information among the area information stored in an area information storage means that stores area information indicating the area related to the community in association with the community identification information identifying the community for each of the plurality of communities. Effect of the Invention

[0034] According to the present invention, the creator of a stamp card can designate two or more communities and create a stamp card that can be commonly used in locations related to the designated communities. [Brief description of the drawings]

[0035] [Figure 1] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Diagram 2] FIG. 13 is a diagram showing an example of the concept of a stamp card common to two or more communities. [Diagram 3] FIG. 13 is a diagram showing an example of a stamp being applied to a stamp card. [Figure 4] 1 is a block diagram showing an example of a schematic configuration of an SNS server 1 according to an embodiment. [Diagram 5] FIG. 13 is a diagram illustrating an example of contents stored in a database. [Figure 6] 2 is a diagram illustrating an example of a functional block of a system control unit 11 of the SNS server 1 according to an embodiment. FIG. [Figure 7] 1 is a sequence diagram showing an example of an operation of a communication system S according to an embodiment. [Figure 8] 11 is a flowchart showing an example of a check-in permission / prohibition determination process by a system control unit 11 of the SNS server 1 according to an embodiment. [Figure 9] 10 is a flowchart showing an example of stamp control processing by a system control unit 11 of the SNS server 1 according to an embodiment. [Figure 10] 1 is a block diagram showing an example of a schematic configuration of an SNS server 1 according to an embodiment. [Figure 11] 14A and 14B are diagrams showing an example of contents stored in a stamp card DB 14f, a stamp card association DB 14g, and an issued card rally DB 14k. [Figure 12] FIG. 13 is a diagram showing an example of a stamp card. [Figure 13] FIG. 13 is a diagram showing an example of a stamp being applied to a stamp card. [Figure 14] 10 is a flowchart showing an example of stamp control processing by a system control unit 11 of the SNS server 1 according to an embodiment. [Figure 15] 10 is a flowchart showing an example of stamp control processing by a system control unit 11 of the SNS server 1 according to an embodiment. [Figure 16] 1 is a diagram illustrating an example of a schematic configuration of a communication system S according to an embodiment. [Figure 17] 1 is a block diagram showing an example of a schematic configuration of an SNS server 1 according to an embodiment. [Figure 18] 13A to 13C are diagrams showing an example of contents stored in a stamp card DB 14f, a cost burden DB 14l, and a fee DB 14m. [Figure 19] 2 is a diagram illustrating an example of a functional block of a system control unit 11 of the SNS server 1 according to an embodiment. FIG. [Figure 20] FIG. 13 is a diagram showing an example of how points are given to a user. [Figure 21] 1 is a sequence diagram showing an example of an operation of a communication system S according to an embodiment when creating a stamp card. [Figure 22] 10 is a flowchart showing an example of stamp control processing by a system control unit 11 of the SNS server 1 according to an embodiment. [Figure 23] 13 is a flowchart showing an example of a billing amount update process by the system control unit 11 of the SNS server 1 according to an embodiment. [Figure 24] 1 is a block diagram showing an example of a schematic configuration of an SNS server 1 according to an embodiment. [Diagram 25] 13A to 13C are diagrams showing an example of contents stored in a stamp history DB 14i, a cost burden DB 14l, and a burden rate setting history DB 14n. [Figure 26] 2 is a diagram illustrating an example of a functional block of a system control unit 11 of the SNS server 1 according to an embodiment. FIG. [Figure 27] FIG. 13 is a diagram showing an example of how points are given to a user. [Figure 28]10 is a sequence diagram showing an example of an operation at the time of setting a cost burden in a communication system S according to an embodiment. FIG. [Figure 29] 13 is a flowchart showing an example of an expense burden setting screen information generating process by a system control unit 11 of the SNS server 1 according to an embodiment. [Diagram 30] 1 is a sequence diagram showing an example of an operation of a communication system S according to an embodiment when creating a stamp card. [Diagram 31] 13 is a flowchart showing an example of a billing amount update process by the system control unit 11 of the SNS server 1 according to an embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0036] [1. First embodiment] Hereinafter, a first embodiment of the present invention will be described in detail with reference to the drawings.

[0037] [1-1. Communication system configuration] First, the configuration and functional overview of a communication system S according to this embodiment will be described with reference to Fig. 1. Fig. 1 is a diagram showing an example of a schematic configuration of a communication system S according to this embodiment.

[0038] 1, a communication system S includes an SNS (social networking service) server 1 and a plurality of user terminals 2. The SNS server 1 and each user terminal 2 are connected to a network NW. The network NW is constructed, for example, by the Internet, a dedicated communication line (for example, a CATV (Community Antenna Television) line), a mobile communication network (including base stations, etc.), a gateway, etc.

[0039] The SNS server 1 may be a server device that executes processing related to the spot SNS. For example, the SNS server 1 may perform processing for controlling the creation of a community, the joining of a community by a user, and the exchange of information between members of the community. The spot SNS may be an SNS for exchanging information related to a spot or information related to things related to the spot within the community. The theme of information exchanged in the community may be the spot or the thing. The spot may be, for example, a facility, a tourist spot, a monument, a landmark, a natural geographical object, a place where a specific event is held or occurs, or other places. The facility may be a place where a business operator related to the facility provides or sells a trading object. Such a facility may be a store or a business office. The trading object may be something that can be the subject of a commercial transaction. The trading object may be at least one of a product and a service. The thing related to the spot may be, for example, an individual or organization that performs some activity at the spot, an object at the spot, or an event that is held or occurs at the spot. A user of the spot SNS may be able to create a community. When creating the community, the manager of the community can set one or more spot areas related to the community. A spot area is a geographical area. A community manager can set a spot area to include a specific spot that is the subject of information exchange in the community. A spot SNS may be an SNS that allows a user to become a member of the community on the condition that the user is located in any of the set spot areas. Only members of the community can post information to the community. In addition, in the case of a community that is set to private by a community manager, only members of the community can view information posted to the community. A user who is even slightly interested in a specific spot within the spot area may or may not go to the spot area.However, going to a certain spot consumes a user's time and effort. Therefore, a user who goes to a spot area is likely to be a user who has a certain level of interest in that particular spot. Therefore, a community can be formed by users who have a certain level of interest in a particular thing.

[0040] A user may be able to join a community by taking a predetermined procedure within the spot area. This procedure is called check-in. A user can check-in by operating the user terminal 2. Check-in may be a procedure for joining a community when the user is not a member of the community. Alternatively, check-in may be a procedure for notifying the SNS server 1 that the user has entered a spot area related to a specific community or visited a specific spot within the spot area. In order to join a community, it may be necessary to further read code information specific to the community with the camera of the user terminal 2. Examples of the code information include a one-dimensional barcode and a two-dimensional code. The code information may be printed on paper or the like and posted at the spot. In addition, approval of the community manager may be further required to join a community.

[0041] The SNS server 1 may execute a process related to a stamp card that can be used in association with a community. For example, the SNS server 1 may execute a process of creating a stamp card, issuing the created stamp card, stamping the stamp card, and the like. Creating a stamp card may mean, for example, determining the specifications of the stamp card and putting the stamp card in a state in which it can be issued. A stamp card may have a plurality of stamp fields. Each stamp field is an area in which a stamp can be pressed. The number of stamp fields that one stamp card has is called the number of stamp fields. The number of stamp fields may be previously determined commonly for all stamp cards, or may be set by the stamp card creator for each stamp card. Issuing a stamp card may mean, for example, providing the stamp card to an individual user. This stamp card may be issued to a member of the community. Pressing a stamp on a stamp card is also referred to as giving a stamp. Also, having a stamp pressed on a stamp card owned by a user is also referred to as acquiring a stamp. A user may be able to acquire a stamp by going within any spot area set for the community. When a predetermined number of stamps are accumulated, the user can obtain some kind of benefit. For example, a benefit may be given to the user when all stamp columns are stamped. Alternatively, the stamp card creator may be able to set a number of stamps to which the user's benefit is given. The benefit may be provided, for example, by the creator of the stamp card, by the administrator of at least one of two or more designated communities, or by a person involved in a specific spot within the spot area associated with those communities. A person involved in a spot may be, for example, a business that sells a trading object at that spot. For example, a community for a certain ramen chain is created by the headquarters of the ramen chain. At this time, the headquarters can set a spot area for each store of the ramen chain so that the store is included therein.Examples of benefits offered by this ramen chain's community stamp card include free toppings, free ramen, and discounts.

[0042] Each user terminal 2 may be a portable terminal device used by a user who uses the spot SNS. The user may be an individual, a business operator, a corporation, or other organization or group. The user may be able to create a community, check in, join a community, post information to a community, and view information posted to a community by operating the user terminal 2. The user terminal 2 may also display a stamp card, or display the acquisition status or usage status of a benefit based on the user's operation. Examples of the user terminal 2 include a mobile information terminal such as a smartphone or a tablet computer, a mobile phone, a PDA (Personal Digital Assistant), and the like. An application program for the communication system S (hereinafter referred to as a dedicated app) may be stored in each user terminal 2. The user can use the spot SNS through the user terminal 2 transmitting and receiving information to and from the SNS server 1 according to the dedicated app.

[0043] Each user terminal 2 may have a function to acquire location information indicating the location of the user terminal 2. For example, a satellite positioning system such as a global positioning system (GPS) may be used to calculate longitude and latitude as location information. For example, a mobile communication carrier may provide location information using a base station to the user terminal 2. In this case, the user terminal 2 acquires longitude and latitude, address, or postal code corresponding to the location of a base station near the user terminal 2 as location information. For example, the location information may be acquired using a wireless LAN (Local Area Network). For example, when the user terminal 2 receives wireless signals from multiple access points, the user terminal 2 measures the radio wave intensity from each access point and acquires the SSID of each access point. The user terminal 2 transmits information including the radio wave intensity and SSID to a predetermined server device (not shown). The server device stores the longitude and latitude of the installation location of the access point. The server device calculates the location of the user terminal 2 by, for example, triangulation using the information received from the user terminal 2.

[0044] [1-2. Stamp card common to multiple communities] Next, the stamp card in the spot SNS will be described with reference to Fig. 2 and Fig. 3. Usually, the manager of a certain community creates a stamp card that can be used for that community. Therefore, the member of the community who becomes the owner of the stamp card can acquire stamps by going to the spot area related to that community.

[0045] Furthermore, it may be possible to create a stamp card that can be used in common for two or more communities. In this case, the creator of the stamp card can specify two or more communities with which the stamp card will be shared. The creator of the stamp card may be, for example, the administrator of one of the communities, or may be a different person from the administrator of any of the communities. In this case, the owner of the stamp card can acquire stamps by visiting a spot related to one of the two or more communities.

[0046] FIG. 2 is a diagram showing an example of the concept of a stamp card common to two or more communities. As shown in FIG. 2, it is assumed that at least communities 201, 202, and 203 exist. Community 201 is a community related to a hotel in X city. Community 201 is associated with spot area 301. Spot area 301 includes the location of the hotel. Community 202 is a community related to a ramen chain with multiple stores in X city. Community 202 is associated with spot areas 302, 303, and 304. Each of these spot areas includes the location of the store. Community 203 is a community related to a soba restaurant in X city. Community 203 is associated with spot area 305. Spot area 305 includes the location of the soba restaurant. User U1 shown in FIG. 2 is X city as a local government. X city specifies communities 201, 202, and 203 and creates a stamp card 101. The stamp card 101 is associated with these communities.

[0047] FIG. 3 is a diagram showing an example of a state in which a stamp is pressed on a stamp card. As shown in FIG. 3, a user U2 has not joined the community 201, but has joined the community 202. The user U2 does not yet have the stamp card 101. The user U2 has a user terminal 2-2 as the user terminal 2. When the user U2 is located outside any spot area, the user U2 cannot check in to any community (step S1). After that, the user U2 stays at a hotel 401 in the spot area 301. The spot area 301 is related to the community 201. Here, the user U2 operates the user terminal 2-2 to check in to the community 201 (step S2). In response to the check-in, the SNS server 1 makes the user U2 join the community 201 (step S3). The SNS server 1 also issues a stamp card 101-1 as a copy of the stamp card 101 to the user U2, and stamps one stamp on the stamp card 101-1 (step S4). The user terminal 2-2 displays information about the stamp card. For example, the user terminal 2-2 may display, as an image of the stamp card, each of a plurality of stamp columns of the stamp card so that it is possible to distinguish whether or not a stamp has been stamped in the stamp column. After that, the user U2 goes to a ramen shop 402 in the spot area 302. The spot area 302 is related to the community 202. Here, the user U2 checks in to the community 202 (step S5). In response to this check-in, the SNS server 1 stamps another stamp on the stamp card 101-1 (step S6). This allows two stamps to be accumulated.

[0048] [1-3.SNS server configuration] Next, the configuration of the SNS server 1 will be described with reference to Fig. 4 and Fig. 5. Fig. 4 is a block diagram showing an example of a schematic configuration of the SNS server 1 according to this embodiment. As shown in Fig. 4, the SNS server 1 includes a system control unit 11, a system bus 12, an input / output interface 13, a storage unit 14, and a communication unit 15. The system control unit 11 and the input / output interface 13 are connected via the system bus 12.

[0049] The system control unit 11 includes a central processing unit (CPU) 11a, a read only memory (ROM) 11b, a random access memory (RAM) 11c, and the like.

[0050] The input / output interface 13 performs interface processing between the storage unit 14 and the communication unit 15 and the system control unit 11 .

[0051] The storage unit 14 is composed of, for example, a hard disk drive, etc. The storage unit 14 stores databases such as a member DB 14a, a community DB 14b, an area DB 14c, a check-in history DB 14d, a community member DB 14e, a stamp card DB 14f, a stamp card association DB 14g, an issued card DB 14h, a stamp history DB 14i, and a privilege DB 14j. "DB" is an abbreviation for database.

[0052] 5 is a diagram showing an example of contents stored in the database. Member DB 14a may store member information on each user of the spot SNS. For example, member DB 14a may store, as member information, a user ID, nickname, name, sex, date of birth, telephone number, email address, address, and the like, in association with one another. The user ID is identification information that identifies a user.

[0053] The community DB 14b may store community information related to each community. For example, the community DB 14b may store a community ID, a community name, category information, a community manager ID, and an area ID as community information in association with each other. The community ID is identification information for identifying a community. The category information is information indicating a category to which the community belongs. Examples of categories include anime and manga, sightseeing, gourmet, local areas, and outdoors. The community manager ID is a user ID of a user who created the community. The area ID is identification information for identifying a spot area associated with the community. When a community manager sets multiple spot areas, multiple area IDs for the community may be stored in the community DB 14b.

[0054] The area DB14c stores area information indicating each spot area set by each community manager. For example, the area DB14c stores area IDs and area information in association with each other. Examples of area shapes include circles, ellipses, squares, rectangles, and diamonds. For example, if the specified area is a circular area, the area information may include the latitude and longitude of the center and the radius. The center may be the location of a specific spot. Instead of the latitude and longitude of the center, the area information may include an address, a facility name, a building name, and a landmark name of the center. If the shape of the area is a shape other than a circle, the area information may include information according to the shape. Alternatively, the area information may include the latitude and longitude of each line segment that constitutes the boundary of the area. Alternatively, the area information may include the name of the area or section.

[0055] The check-in history DB14d may store a history of check-ins to communities by each user. For example, each time a check-in is performed, the check-in history DB14d may store a check-in log including a check-in log number, check-in date and time, a community ID, an area ID, and a user ID, which are associated with each other. The check-in log number is a number that identifies the check-in log. The check-in date and time indicates the date and time when the check-in was performed. The community ID indicates the community where the check-in was performed. The area ID indicates the spot area where the check-in was performed. The user ID indicates the user who performed the check-in.

[0056] The community member DB 14e may store information indicating which user belongs to which community as a member. For example, the community member DB 14e may store a community ID and a user ID in association with each other for each combination of a community and a member of the community. The user ID indicates a user who is a member of the community indicated by the community ID. Only a user whose user ID is stored in the community member DB 14e can post information to the community. For example, in a dedicated app, a user performs an operation to display a screen of a community. At this time, the SNS server 1 may search the community member DB 14e for a combination of the user's user ID and the community ID of the community. If a matching combination is found, the SNS server 1 may display an input field on the screen of the community for the user to input information to be posted. The SNS server 1 may store the input information in a predetermined database as posted information in association with the community ID of the community. The SNS server 1 may transmit posted information associated with the community ID of the community in response to a request from the user terminal 2 of a member of the community. If there is no corresponding combination, the SNS server 1 does not have to display the input field on the screen of that community.

[0057] The stamp card DB 14f may store stamp card information on each stamp card created. For example, the stamp card DB 14f may store stamp card information such as a stamp card ID, a stamp card name, a stamp card creator ID, an explanation, and benefit setting information in a mutually associated manner. The stamp card ID is identification information for identifying a stamp card. The stamp card creator ID indicates the user who created the stamp card. The benefit setting information indicates information on a benefit. For example, the benefit setting information may include the number of benefit stamps, a benefit name, a use start date, a use end date, a use end date setting flag, and a use condition. The number of benefit stamps indicates the number of stamps required to acquire a benefit. The benefit name indicates the name of the benefit so that the content of the benefit that can be acquired can be identified. The use start date indicates the start date of the period during which the benefit can be used. The use end date indicates the end date of the period during which the benefit can be used. The use end date setting flag indicates whether the use end date setting is valid or not. The use condition indicates the condition for using the benefit. If multiple special offers can be obtained from one issued stamp card, multiple special setting information may be stored in the stamp card DB 14f. In this case, the number of special stamps for each of the special offers may differ.

[0058] The stamp card association DB 14g may store stamp card association information about a community that can be used to promote visits to a spot for each combination of the stamp card and the community. For example, the stamp card association DB 14g may store the stamp card ID of the stamp card and the community ID of the community in association with each other as the stamp card association information.

[0059] In the issued card DB 14h, issued card information on stamp cards issued to users may be stored for each combination of a stamp card and a user to which the stamp card was issued. For example, in the issued card DB 14h, the issued card number, the issue date, the stamp card ID, the user ID, the number of issued cards, and the number of stamps may be stored in association with each other as the issued card information. The issued card number is a number that identifies the issuance of the stamp card. The issue date indicates the date on which the stamp card was issued to the user. The stamp card ID indicates the issued stamp card. The user ID indicates the user to whom the stamp card was issued. The number of issued cards indicates how many stamp cards were issued to the user. The number of stamps indicates the number of stamps pressed on the stamp card. When the number of stamps pressed on one stamp card reaches the number of stamp card columns, a new stamp card may be automatically issued. In this case, the number of issued cards is increased by one, and the number of stamps is reset to zero.

[0060] The stamp history DB14i may store a history of stamps being pressed on stamp cards. For example, each time a stamp is pressed, the stamp history DB14i may store a stamp log in which a stamp log number, stamp date and time, stamp card ID, community ID, area ID, user ID, and the like are associated with each other. The stamp log number is a number that identifies the stamp log. The stamp date and time indicates the date and time when the stamp was pressed. The stamp card ID indicates the stamp card on which the stamp was pressed. The community ID indicates the community where the user checked in, as a prerequisite for the stamp being pressed on the stamp card. The area ID indicates the spot area where the user checked in. The user ID indicates the user who checked in.

[0061] The privilege DB 14j may store privilege information on a privilege that can be acquired by using a stamp card for each combination of an issued stamp card and a privilege set on the stamp card. For example, the privilege DB 14j may store, as privilege information, an issued card number, a stamp card ID, a user ID, the number of issued cards, the number of privilege stamps, and a privilege status, in association with one another. The issued card number identifies the issuance of a stamp card on which a privilege is set. The stamp card ID indicates the issued stamp card. The user ID indicates the user to whom the stamp card is issued. The issued number indicates which stamp card the stamp card on which the privilege is set is issued to the user. The number of privilege stamps indicates the number of stamps required for the user to acquire the privilege. The privilege status indicates the status of the privilege. The privilege status may be set to, for example, any of "not acquired", "available", and "used". "Not acquired" indicates a state in which the user has not yet acquired the privilege. "Available" indicates a state in which the user has acquired the privilege but has not yet used the privilege. "Already used" indicates that the user has already used the benefit.

[0062] The storage unit 14 further stores various programs such as an operating system, a DBMS (Database Management System), and a server program. The server program is a program that causes the system control unit 11 to execute various processes related to the spot SNS. The server program may be obtained from another device via the Internet NW, or may be recorded on a recording medium such as a magnetic tape, an optical disk, or a memory card and read via a drive device.

[0063] The communication unit 15 is configured by, for example, a network interface card, etc. The communication unit 15 connects to the user terminal 2 etc. via the network NW, and controls the state of communication with the connected device.

[0064] [1-4. Functional overview of the system control unit of the SNS server] Next, a functional overview of the system control unit 11 of the SNS server 1 will be described with reference to Fig. 6. Fig. 6 is a diagram showing an example of a functional block of the system control unit 11 of the SNS server 1 according to this embodiment. The system control unit 11 may function as a community ID acquisition unit 1101, a stamp card creation unit 1102, a location information acquisition unit 1103, a check-in determination unit 1104, a subscription unit 1105, a stamp unit 1106, a privilege granting unit 1107, and the like, as shown in Fig. 6, by the CPU 11a reading and executing various program codes included in the server program.

[0065] The community ID acquisition unit 1101 may acquire two or more community IDs for identifying two or more communities designated by a stamp card creator who creates a stamp card, among a plurality of mutually different communities. The community ID acquisition unit 1101 may acquire a community ID, for example, from the user terminal 2 of the stamp card creator. For example, the stamp card creator selects the creation of a stamp card in a dedicated application. In response to this selection, the user terminal 2 may display a stamp card creation screen for inputting various information of the stamp card. The stamp card creation screen may include a user interface element for selecting a community. For example, when a user selects to add a community on the stamp card creation screen, the user terminal 2 may display a search window. The search window may be a window for searching for a community. In the search window, the user can specify search conditions for the community. Examples of search conditions include a community name, a category, an address, a community created by the stamp card creator, and the like. The SNS server 1 may search for a community that satisfies the specified search conditions, for example, by using the community DB 14b, the area DB 14c, and the like. The user terminal 2 may display a list of the searched communities in the search window. The user specifies a community that he or she wants to add from the list. Alternatively, the user terminal 2 may display a map and a mark indicating a spot associated with the community on the map. The user may specify a spot of the community to be added from the map. When the community is specified, the user terminal 2 may add and display the community name of the specified community on the stamp card creation screen. When the user specifies two or more communities, this procedure is repeated. Note that the user may specify only one community. For example, it may be possible to specify a community created by the user. When the input of necessary information on the stamp card creation screen is completed, the user terminal 2 may transmit the community ID of each of the specified two or more communities to the SNS server 1 together with other input information.In this manner, the community ID acquisition unit 1101 may acquire the community ID.

[0066] The two or more communities designated by the stamp card creator may be two or more communities in which information related to two or more different businesses that sell trading objects is provided within the community. Each of these businesses may be a business that sells trading objects at a facility related to the business. The facility related to the business may be, for example, a facility owned, managed, rented, or used by the business. Examples of such facilities include a store, a sales office, etc. The spot area indicated by the area information stored in the storage unit 14 in association with the community ID of each of these communities may include the location of the facility related to the business related to the community. The stamp card creator can designate communities related to different businesses as the two or more communities. By visiting a facility related to one of the two or more businesses, the user can have a stamp pressed on the stamp card. Therefore, a stamp card common to two or more businesses divided by communities can be created as a stamp card that encourages the user to visit the facility.

[0067] The stamp card creation unit 1102 may store in the storage unit 14 a stamp card ID that identifies the stamp card to be created in association with two or more community IDs acquired by the community ID acquisition unit 1101. For example, the stamp card creation unit 1102 may generate a new stamp card ID. The stamp card creation unit 1102 may generate stamp card information including information transmitted from the user terminal 2 and the stamp card ID. The stamp card creation unit 1102 may store the generated stamp card information in the stamp card DB 14f. The stamp card creation unit 1102 may store in the stamp card association DB 14g the community ID and the generated stamp card ID in association with each acquired community ID.

[0068] The two or more spot areas indicated by the two or more area information stored in the storage unit 14 for each of the two or more communities designated by the stamp card creator may include different locations from each other. The two or more spot areas including different locations from each other may mean that the spot areas do not coincide with each other. For example, the two or more spot areas being different from each other may mean that the areas do not overlap at all, or may include that only a part of the areas overlap. Since the spots related to each community are often different from each other, the spot areas are often at least partially different from each other. The stamp card creator can designate two or more communities that may be related to different locations from each other.

[0069] The position information acquisition unit 1103 may acquire the position information of the portable user terminal 2. The position information acquisition unit 1103 may acquire the position information from the user terminal 2, for example. For example, the user terminal 2 may acquire the position information of the user terminal 2 periodically in the background according to a dedicated application using a GPS or the like, and transmit the position information to the SNS server 1. Alternatively, the user terminal 2 may be capable of selecting a spot of a community where the user wants to check in, in a dedicated application. For example, the user terminal 2 may display a map and display marks indicating each spot on the map. The user may select a spot from the map. In response to this selection, the user terminal 2 may display a map including a spot area corresponding to the spot, and may display the spot area and a mark indicating the current position of the user terminal 2 on the map. While displaying this map, the user terminal 2 may periodically acquire position information and transmit it to the SNS server 1. The user terminal 2 may transmit the user ID of the user of the user terminal 2 to the SNS server 1 together with the position information. In this way, the position information acquisition unit 1103 may acquire the position information.

[0070] The check-in determination unit 1104 may determine whether or not the user can check in to any community based on the location information acquired by the location information acquisition unit 1103. For example, the check-in determination unit 1104 may determine whether or not the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 is included in a spot area indicated by any area information stored in the storage unit 14. If the location of the user terminal 2 is included in any spot area, the check-in determination unit 1104 may determine that the user can check in to that community. Here, when a user is trying to check in at the same spot area as the spot area where the user previously checked in, the check-in determination unit 1104 may allow the user to check in only once per predetermined period (for example, within 24 hours from a predetermined time). This prevents excessive acquisition of stamps due to repeated check-ins at the same spot area.

[0071] When the check-in determination unit 1104 determines that the position of the user terminal 2 indicated by the position information acquired by the position information acquisition unit 1103 is included in a spot area indicated by any of the area information stored in the storage unit 14, the joining unit 1105 may execute a process of having the user of the user terminal 2 join a community identified by a community ID associated with any of the area information. For example, the joining unit 1105 may associate the community ID of the community with the user ID of the user and store them in the community member DB 14e. The joining unit 1105 may join the user to the community only when the user performs a check-in operation.

[0072] When the check-in determination unit 1104 determines that the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 is included in the area indicated by the area information associated with any one of the two or more community IDs acquired by the community ID acquisition unit 1101 among the area information stored in the storage unit 14 that stores area information indicating a spot area related to each of the multiple communities in association with the community ID of the community, the stamp unit 1106 may execute a stamp process to stamp a stamp card for the user of the user terminal 2. The stamp unit 1106 may execute the stamp process regardless of which of the two or more acquired community IDs the area information indicating the spot area including the user terminal 2 is associated with. The community DB 14b stores the community ID and the area ID in association with each other. The area DB 14c stores the area ID and the area information in association with each other. Therefore, the community ID and the area information are associated with each other via the area ID. As the stamp process, the stamp unit 1106 may increase the number of stamps included in the issued card information stored in the issued card DB 14h, for example. The identification of the issued card information may be performed as described below. For example, the stamp unit 1106 may acquire a community ID associated with area information indicating a spot area including the user terminal 2. The stamp unit 1106 may acquire a stamp card ID associated with this community ID from the stamp card DB 14f. The stamp unit 1106 may search the issued card information including this stamp card ID and the user ID of the user of the user terminal 2 from the issued card DB 14h. If there is no corresponding issued card information, the stamp unit 1106 may generate new issued card information and store it in the issued card DB 14h. When storing the new issued card information, the stamp unit 1106 may generate new privilege information and store it in the privilege DB 14j. For example, the stamp unit 1106 may generate benefit information for each benefit based on the issued card information and the stamp card information of the stamp card stored in the stamp card DB 14f.At this time, the stamp card DB 14f may set the privilege status of the privilege information to "not acquired."

[0073] The stamp unit 1106 may execute the stamp process on the condition that the user is a member of at least one of the two or more communities designated by the stamp card creator. For example, the stamp unit 1106 may refer to the community member DB 14e and determine whether the user is a member of any of the communities based on the community IDs of those communities and the user ID of the user. Here, the stamp unit 1106 may execute the stamp process when the user is not a member of the community associated with the spot area in which the user terminal 2 of the user is located among the two or more communities designated by the stamp card creator, but is a member of any of the other communities. Alternatively, the stamp unit 1106 may execute the stamp process only when the user is a member of the community associated with the spot area in which the user terminal 2 of the user is located. Here, if the joining unit 1105 joins the user to the community in response to the location of the user terminal 2 being included in the spot area associated with any of the two or more communities designated, the user can automatically satisfy the condition.

[0074] The privilege granting unit 1107 may execute a process of granting a privilege to a user when the number of stamps pressed reaches a preset number of privilege stamps as a result of the stamping process being executed by the stamping unit 1106. For example, the privilege granting unit 1107 may change the privilege status stored in the privilege DB 14j in association with the issued card number of the stamped stamp card, the number of issued stamps, the user ID of the user, and the number of privilege stamps, to "available."

[0075] [1-5. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 7 to Fig. 9. The system control unit 11 executes the process of the SNS server 1 shown in Fig. 7 and the processes shown in Fig. 8 and Fig. 9 according to the program code included in the server program.

[0076] FIG. 7 is a sequence diagram showing an example of the operation of the communication system S according to this embodiment. In response to the user U1 as a stamp creator selecting to create a stamp card, the user terminal 2-1 displays a stamp card creation screen. Then, as shown in FIG. 7, the user U1 inputs stamp card information to the stamp card creation screen (step S101). For example, a stamp card name, a description, privilege setting information, etc. are input. Furthermore, the user U1 specifies multiple communities (step S102). In response to completion of input of necessary information, the user terminal 2-1 transmits the input stamp card information, a list of community IDs of the specified communities, and the user ID of the user U1 to the SNS server 1 (step S103).

[0077] The stamp card creation unit 1102 of the SNS server 1 that receives the information from the user terminal 2-1 generates a stamp card ID (step S104). The stamp card creation unit 1102 also generates stamp card information and stamp card association information and stores them in the storage unit 14 (step S105). For example, the stamp card creation unit 1102 may generate stamp card information including the generated stamp card ID, information input by the user U1, and the user ID of the user U1. The stamp card creation unit 1102 may store the stamp card information in the stamp card DB 14f. The stamp card creation unit 1102 may also store each community ID included in the list of community IDs in the stamp card association DB 14g in association with the generated stamp card ID. In this way, a new stamp card is created.

[0078] Thereafter, in response to an operation by user U2 as a user checking in to the community, the user terminal 2-2 displays a map and a mark of the spot. By selecting a spot from the map, the user U2 selects a community associated with the spot area including the spot (step S106). The user terminal 2-2 transmits the community ID of the selected community, the area ID of the spot area including the selected spot, and the user ID of the user U2 to the SNS server 1 (step S107). The user terminal 2-2 also displays a map with an enlarged spot area and a check-in button. The check-in button is a button for checking in to the selected community. At this time, the user terminal 2-2 sets the operation on the check-in button to be invalid. That is, the user U2 cannot check in at this point. Then, the user terminal 2-2 periodically generates position information of the user terminal 2-2 and transmits it to the SNS server 1 (steps S107, S108). The SNS server 1 executes a check-in possibility determination process every time it receives position information (steps S109, S111).

[0079] Fig. 8 is a flowchart showing an example of a check-in possibility determination process by the system control unit 11 of the SNS server 1 according to this embodiment. As shown in Fig. 8, the check-in determination unit 1104 acquires area information associated with the area ID received from the user terminal 2-2 in step S107 from the area DB 14c (step S201). Next, the check-in determination unit 1104 determines whether or not the location of the user terminal 2-2 indicated by the location information received from the user terminal 2-2 is included in the spot area indicated by the area information (step S202). If the location of the user terminal 2-2 is not included in the spot area (step S202: NO), the check-in possibility determination process ends.

[0080] If the location of the user terminal 2-2 is included in the spot area (step S202: YES), the check-in determination unit 1104 searches the check-in history DB 14d for a check-in log including the user ID of the user U2 and the area ID received from the user terminal 2-2, the check-in log including a check-in date and time indicating a time after the most recent predetermined time (for example, 7:00) (step S203). As a result of the search, the check-in determination unit 1104 determines whether or not there is a corresponding check-in log (step S204). If there is a corresponding check-in log (step S204: YES), the check-in possibility determination process ends. If there is no corresponding check-in log (step S204: NO), the check-in determination unit 1104 transmits a check-in possibility notification to the user terminal 2-2 (step S205), and the check-in possibility determination process ends.

[0081] Returning to FIG. 7, it is assumed that the check-in determination unit 1104 transmits a check-in possible notification to the user terminal 2-2 as a result of the check-in possible / not possible determination process in step S111 (step S112). In response to receiving the check-in possible notification, the user terminal 2-2 changes the operation of the check-in button to enabled (step S113). Next, the user U2 performs an operation of pressing the check-in button (step S114). In response to this operation, the user terminal 2-2 transmits a check-in request to the SNS server 1 (step S115). The check-in request may include a community ID and an area ID corresponding to the community and spot selected by the user U2, respectively, and the user ID of the user U2.

[0082] The check-in determination unit 1104 of the SNS server 1 that has received the check-in request generates a check-in log and stores it in the check-in history DB 14d (step S116). For example, the check-in determination unit 1104 may generate a check-in log that includes the information included in the check-in request and the current date and time as the check-in date and time. Next, the joining unit 1105 executes a community joining control process (step S117). For example, the joining unit 1105 may determine whether or not a combination of a community ID and a user ID that is the same as the combination included in the check-in request is stored in the community member DB 14e. If the same combination is not stored, the joining unit 1105 may associate the community ID with the user ID and store them in the community member DB 14e. Next, the stamp unit 1106 executes a stamp control process (step S118).

[0083] Fig. 9 is a flowchart showing an example of stamp control processing by the system control unit 11 of the SNS server 1 according to this embodiment. As shown in Fig. 9, the stamp unit 1106 searches the stamp card association DB 14g for a stamp card ID associated with the community ID of the community where the user U2 has checked in (step S301). As a result of the search, the stamp unit 1106 determines whether or not there is a corresponding stamp card ID (step S302). If there is no corresponding stamp card (step S302: NO), the stamp card control processing ends.

[0084] If there is a corresponding stamp card ID (step S302: YES), the stamp unit 1106 acquires stamp card information including the searched stamp card ID from the stamp card DB 14f. Next, the stamp unit 1106 searches the issued card DB 14h for issued card information including the searched stamp card ID and the user ID of the checked-in user U2 (step S303). As a result of the search, the stamp unit 1106 judges whether there is corresponding issued card information (step S304). If there is no corresponding issued card information (step S304: NO), the stamp unit 1106 generates new issued card information and benefit information and stores them in the storage unit 14 (step S305). For example, the stamp unit 1106 may generate a new issued card number. The stamp unit 1106 may generate an issued card number including the issued card number, the searched stamp card ID, the user ID of the user U2, the number of issued cards indicating 1, and the number of stamps indicating zero. The stamp unit 1106 may store the issued card information in the issued card DB 14h. The stamp unit 1106 may also acquire the number of bonus stamps from the bonus setting information included in the acquired stamp card information. The stamp unit 1106 may generate bonus information for each acquired number of bonus stamps, including the same combination of the issued card number, the stamp card ID, the user ID, and the number of issued cards included in the issued card information, the number of bonus stamps, and a bonus status indicating "unused." The stamp 1106 may store the bonus information in the bonus DB 14j.

[0085] If there is corresponding issued card information (step S304: YES), or after step S305, the stamp unit 1106 increments the number of stamps included in the corresponding issued card information or the generated issued card information by 1 (step S306). Next, the stamp unit 1106 stores the stamp log in the stamp history DB 14i (step S307). For example, the stamp unit 1106 may generate a stamp log including the searched stamp card ID, the community ID and area ID received from the user terminal 2-2, the user ID of the user U2, and the stamp date and time indicating the current date and time.

[0086] Next, the stamp unit 1106 judges whether the stamp number matches any of the bonus stamp numbers included in the bonus setting information of the acquired stamp card information (step S308). If the stamp number matches any of the bonus stamp numbers (step S308: YES), the bonus granting unit 1107 changes the bonus status stored in the bonus DB 14j in association with the same combination of the bonus stamp number that matches the stamp number and the issued card number, user ID, and issued number included in the searched issued card information or the generated issued card information to "available" (step S309).

[0087] After step S309, or if the number of stamps does not match any of the bonus stamp numbers (step S308: NO), it is determined whether the number of stamps matches the number of stamp columns (step S310). If the number of stamps matches the number of stamp columns (step S310: YES), the stamp unit 1106 increases the number of issued cards included in the searched issued card information or the generated issued card information by 1 (step S311), and changes the number of stamps included in the issued card information to zero (step S312). Next, the stamp unit 1106 generates new bonus information and stores it in the bonus DB 14j (step S313). The method of generating the bonus information may be the same as that of step S305.

[0088] After step S313, or if the number of stamps does not match the number of stamp columns (step S310: NO), the stamp unit 1106 generates stamp card display information and transmits the display information to the user terminal 2-2 (step S314), and the stamp control process ends. The stamp card display information is information for displaying the stamp card on the user terminal 2-2. For example, the stamp card display information may include the stamp card name, the number of stamps, etc.

[0089] Returning to FIG. 7, it is assumed that the stamp unit 1106 transmits stamp card display information to the user terminal 2-2 through the stamp control process (step S119). The user terminal 2-2 displays a stamp card screen based on the stamp card display information (step S120). For example, the user terminal 2-2 may display an image of a stamp card having multiple stamp columns and may also display the name of the stamp card. The user terminal 2-2 may display an image showing a stamp in each of the stamp columns included in the stamp card, the number of which corresponds to the number of stamps.

[0090] As described above, according to this embodiment, the SNS server 1 may acquire two or more community IDs that identify two or more communities designated by the stamp card creator. The SNS server 1 may also store in the stamp card DB 14f a stamp card ID that identifies the stamp card to be created in association with the two or more community IDs. The SNS server 1 may also acquire the location information of the user terminal 2. If the location indicated by the location information is included in a spot area indicated by area information associated with any of the two or more community IDs associated with the stamp card ID among the area information stored in the spot area DB 14c, the SNS server 1 may execute a stamp process for the user of the user terminal 2. In this case, even if the community associated with the spot area visited by the user corresponds to any of the two or more communities designated by the stamp card creator, the user can have the stamp pressed on the stamp card. Therefore, the stamp card creator can specify two or more communities and create a stamp card that can be commonly used in places related to the specified communities.

[0091] Here, when the location indicated by the location information is included in a spot area indicated by any area information stored in the area DB 14c, the SNS server 1 may allow the user to join a community identified by a community ID associated with the area information. In this case, the user can join a community by going to a spot area associated with any community. It is considered that the user goes to a particular spot area because he or she is more than a certain level interested in things in that spot area. Therefore, the community can be formed by users who are more than a certain level interested in the subject of information exchange in the community.

[0092] The SNS server 1 may also execute the stamp processing on the condition that the user is a member of at least one of two or more communities designated by the stamp card creator. In this case, the user can be prompted to join the community.

[0093] [2. Second embodiment] Next, a second embodiment will be described. Except for the points described below, the second embodiment may be the same as the first embodiment. In this embodiment, the SNS server 1 is configured to enable a user to participate in a stamp rally using a stamp card. A typical stamp rally is an activity in which a user visits different spots and has a stamp put on a stamp card. Even if the user visits a spot where a stamp has been put once again, the user cannot have the stamp put on. The stamp rally in this embodiment may be an activity in which a user visits spots associated with different communities and has a stamp put on a stamp card. For a community where a stamp has been put once, the user cannot have the stamp put on even if the user visits a spot associated with that community. In this case, even if the spot where the user went after having the stamp put on is different from the spot where the user had the stamp put on, the user cannot have the stamp put on.

[0094] [2-1.SNS server configuration] Next, the configuration of the SNS server 1 will be described with reference to Figs. 10 to 12. Fig. 10 is a block diagram showing an example of a schematic configuration of the SNS server 1 according to this embodiment. In Fig. 10, the same elements as in Fig. 4 are given the same reference numerals. The difference between Fig. 4 and Fig. 10 is that in Fig. 10, an issued card rally DB 14k is further stored in the memory unit 14.

[0095] FIG. 11 is a diagram showing an example of contents stored in the stamp card DB 14f, the stamp card association DB 14g, and the issued card rally DB 14k. The stamp card DB 14f shown in FIG. 11 differs from the stamp card DB 14f shown in FIG. 5 in that the stamp card DB 14f shown in FIG. 11 further stores a card type. The card type indicates the type of stamp card. The card type may be set to, for example, either "stamp rally" or "normal." "Stamp rally" indicates that the stamp card is a card for a stamp rally. "Normal" indicates that the stamp card is not a card for a stamp rally. When creating a stamp card, the stamp card creator may be able to select the card type.

[0096] The stamp card association DB 14g shown in Fig. 5 differs from the stamp card association DB 14g shown in Fig. 11 in that a stamp column number is further stored in the stamp card association DB 14g shown in Fig. 11. The stamp column number indicates the number of the stamp column in which a stamp is to be placed for the community identified by the community ID.

[0097] FIG. 12 is a diagram showing an example of a stamp card. The stamp card 102 shown in FIG. 12 is a card for a stamp rally. The stamp card 102 has ten stamp columns. A stamp column number from 1 to 10 is assigned to each stamp column. A community is also associated with each stamp column. For example, communities 201, 202, 203, 204, 205, 206, 207, 208, 209, and 210 are associated with the stamp column from the stamp column 1 to the stamp column 10 in that order. For example, the communities may be associated with the stamp columns in the order of the communities specified by the stamp card creator when the stamp card is created. Alternatively, the stamp card creator may be able to specify the allocation of communities to the stamp columns. The number of stamp columns may be determined in advance, for example. Alternatively, the number of communities specified by the stamp card creator may be determined as the number of stamp columns.

[0098] Returning to FIG. 11, the issued card rally DB 14k may store, among information related to stamp cards issued to users, issued card rally information related to stamp rally for each combination of a stamp card for stamp rally, a user to whom the stamp card was issued, and a stamp column. For example, the issued card rally DB 14k may store, for each of two or more communities designated by a stamp card creator, either information indicating that a stamp is not pressed or information indicating that the stamp is pressed, in association with the stamp card ID of the created stamp card and the user ID of the user who has the stamp card. Specifically, the issued card rally DB 14k may store, as issued card rally information, for example, an issued card number, a stamp card ID, a user ID, a community ID, a stamp column number, and a stamp state in association with each other. The issued card number identifies the issuance of a stamp card including a specific stamp column. The stamp card ID indicates the issued stamp card. The user ID indicates the user to whom the stamp card is issued. The community ID indicates the community associated with the stamp column. The stamp column number indicates the stamp column. The stamp status indicates whether or not a stamp has been applied to the stamp column. The stamp status may be set to, for example, either "not acquired" or "acquired." "Not acquired" indicates that a stamp has not been applied. "Acquired" indicates that a stamp has been applied.

[0099] [2-2. Functional overview of the system control unit of the SNS server] Next, the function outline of the system control unit 11 of the SNS server 1 will be described with reference to FIG. 13. In this embodiment, the stamp unit 1106 may change the stamp state to "acquired" as a stamp process for a community indicated by a community ID associated with area information indicating a spot area including the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 among two or more communities designated by the stamp card creator, in association with the stamp card ID and the user ID of the user of the user terminal 2, when the stamp state indicating "not acquired" is stored in the issued card rally DB 14k. That is, a stamp is pressed on the stamp card, and the number of stamps acquired by the user increases. The stamp state for a community may be a stamp state associated with the stamp column number assigned to the community. On the other hand, the stamp unit 1106 may not do anything in particular when the stamp state indicating "acquired" is stored in the issued card rally DB 14k. That is, a stamp is not pressed on the stamp card, and the number of stamps acquired by the user does not increase. It is stipulated that when the number of stamp states indicating "acquired" stored in the issued card rally DB14k in association with the stamp card ID of a certain stamp card and the user ID of a certain user reaches the number of bonus stamps, a bonus will be granted to that user.

[0100] FIG. 13 is a diagram showing an example of a state in which a stamp is pressed on a stamp card. A user U2 shown in FIG. 13 does not yet own a stamp card 102. The user U2 who owns a user terminal 2-2 goes to a ramen shop 402 in a spot area 302. The spot area 302 is related to a community 202. Here, the user U2 operates the user terminal 2-2 to check in to the community 202 (step S11). In response to the check-in, the SNS server 1 issues a stamp card 102-1 as a copy of the stamp card 102 to the user U2. As shown in FIG. 12, the community 202 is assigned to the second stamp column. No stamps are pressed in any of the stamp columns of the stamp card 102-1 that has just been issued. Therefore, the SNS server 1 presses a stamp in the second stamp column of the stamp card 102-1 (step S12). The next day, the user U2 goes to a ramen shop 403 in a spot area 303. The spot area 303 is also related to the community 202. Here, the user U2 operates the user terminal 2-2 to check in to the community 202 (step S13). A stamp has already been placed in the second stamp column of the stamp card 102-1. Therefore, the SNS server 1 does not place a stamp on the stamp card 102-1 (step S14). After that, the user U2 goes to the bakery 406 in the spot area 306. The spot area 306 is assumed to be related to the community 209, for example. The community 209 is related to the bakery 406. As shown in FIG. 12, the community 209 is assigned to the ninth stamp column. Here, the user U2 operates the user terminal 2-2 to check in to the community 202 (step S15). A stamp has not been placed in the ninth stamp column of the stamp card 102-1. Therefore, the SNS server 1 places a stamp in the ninth stamp column (step S16).

[0101] [2-3. Operation of communication system] Next, the operation of the communication system S will be described with reference to FIG. 14 and FIG. 15. In this embodiment, as shown in FIG. 7, steps S101 to S117 may be executed first. Here, in step S101, the stamp card creator selects the card type. In step S105, when the card type is "stamp rally", the stamp card creation unit 1102 adds a stamp column number to the stamp card association information when generating stamp card association information for each community specified by the stamp card creator. For example, the stamp card creator may assign the stamp column numbers to be added to the stamp card association information in the order of the communities specified by the stamp card creator. After step S117, a stamp control process is executed (step S118).

[0102] 14 and 15 are flow charts showing an example of stamp control processing by the system control unit 11 of the SNS server 1 according to this embodiment. In Fig. 14, the same processes as those in Fig. 9 are denoted by the same reference numerals.

[0103] As shown in FIG. 14, steps S301 and S302 are executed first. If there is no corresponding stamp card ID as a result of the search in step S301 (step S302: NO), the stamp card control process ends. If there is a corresponding stamp card ID (step S302: YES), the stamp unit 1106 acquires stamp card information including the searched stamp card ID from the stamp card DB 14f. Next, the stamp unit 1106 determines whether the card type included in the acquired stamp card information is "stamp rally" (step S321). If the card type is not "stamp rally" (step S321: NO), steps S303 to S305 are executed as in the first embodiment.

[0104] If the card type is "stamp rally" (step S321: YES), as shown in FIG. 15, the stamp unit 1106 searches the issued card DB 14h for issued card information including the searched stamp card ID and the user ID of the checked-in user U2 (step S401). As a result of the search, the stamp unit 1106 determines whether there is corresponding issued card information (step S402). If there is no corresponding issued card information (step S402: NO), the stamp unit 1106 generates new issued card information and benefit information and stores them in the storage unit 14 (step S403). Step S403 may be the same as step S305. Next, the stamp unit 1106 generates issued card rally information and stores it in the issued card rally DB 14k (step S404). For example, the stamp unit 1106 may search all stamp card association information including the searched stamp card ID from the stamp card association DB 14g. The stamp unit 1106 may obtain a combination of a community ID and a stamp column number from each of the stamp card association information retrieved. The stamp unit 1106 may generate issued card rally information for each of the retrieved combinations, including the generated issued card number, the retrieved stamp card ID, the combination, and a stamp status indicating "not acquired." The stamp unit 1106 may store each of the generated issued card rally information in the issued card rally DB 14k.

[0105] If there is corresponding issued card information (step S402), or after step S404, the stamp unit 1106 searches the issued card rally DB 14k for a stamp status associated with the combination of the searched stamp card ID, the user ID of the user U2, and the community ID received from the user terminal 2-2 (step S405). Next, the stamp unit 1106 judges whether the searched stamp status is "not acquired" (step S406). If the stamp status is "acquired" (step S406: NO), the stamp control process ends. If the stamp status is "not acquired" (step S406: YES), the stamp unit 1106 changes the stamp status to "acquired" (step S407).

[0106] If there is the corresponding issued card information (step S304: YES), after step S306 or after step S407, steps S306 to S313 are executed as in the first embodiment, as shown in FIG. 14. After step S313, the stamp unit 1106 judges whether the card type included in the acquired stamp card information is "stamp rally" (step S322). If the card type is "stamp rally" (step S323: YES), the stamp unit 1106 changes each stamp state stored in the issued card rally DB 14k in association with the combination of the searched stamp card ID and the user ID of the user U2 to "not acquired" (step S323). After step S323, if the number of stamps does not match the number of stamp columns (step S310: NO) or if the card type is not "stamp rally" (step S322: NO), the stamp unit 1106 transmits stamp card display information to the user terminal 2-2 (step S314), and the stamp control process ends. If the card type is "stamp rally", the stamp card display information may include a combination of a stamp section number and a stamp status for each stamp section.

[0107] When the stamp control process ends, steps S119 and S120 are executed as shown in Fig. 7. In step S120, the user terminal 2-2 may determine the stamp status associated with the stamp column number for each stamp column. The user terminal 2-2 may display an image of a stamp in the stamp column whose stamp status is "acquired".

[0108] As described above, according to this embodiment, it is possible to realize a stamp rally in which a user visits two or more spot areas associated with two or more communities designated by a stamp card creator.

[0109] [3. Third embodiment] Next, the third embodiment will be described. Except for the points described below, the third embodiment may be the same as the first or second embodiment. In this embodiment, when a stamp card of a user is pressed in response to the user being located in any spot area, the user is given points of a predetermined point program. The point program may be a service that gives a user points of a predetermined percentage of the purchase price of a transaction object at a facility or online, and allows the user to use the points to purchase the transaction object. Each user of the spot SNS may be able to use the point program. The cost of giving points to a user is borne by at least one of the creator of the stamp card and the operator of the community of the spot area. Points may be given to a user for all stamp cards. Alternatively, each stamp card creator may be able to select whether or not to give points. For convenience of explanation, hereinafter, it is assumed that points are given to a user for all stamp cards.

[0110] [3-1. Communication system configuration] First, the configuration and functional overview of the communication system S according to this embodiment will be described with reference to Fig. 16. Fig. 16 is a diagram showing an example of the schematic configuration of the communication system S according to this embodiment. In Fig. 16, the same elements as in Fig. 1 are given the same reference numerals. Fig. 16 differs from Fig. 1 in that a point management server 3 is added in Fig. 16. The point management server 3 is connected to a network NW.

[0111] The point management server 3 may be a server device that manages points of each user in a point program. For example, the point management server 3 may store a point DB 31. The point DB 31 may store information regarding points owned by each user. The number of points currently owned by a user is called the number of available points. The point DB 31 may store, for example, a user ID and the number of available points for each user in association with each other. The point management server 3 may provide the SNS server 1 with an API (Application Programming Interface) for accessing the point DB 31.

[0112] [3-2.SNS Server Configuration] Next, the configuration of the SNS server 1 will be described with reference to Figs. 17 and 18. Fig. 17 is a block diagram showing an example of a schematic configuration of the SNS server 1 according to this embodiment. In Fig. 17, the same elements as in Fig. 4 are given the same reference numerals. Fig. 17 differs from Fig. 4 in that in Fig. 17, an expense burden DB 14l and a fee DB 14m are further stored in the storage unit 14.

[0113] FIG. 18 is a diagram showing an example of contents stored in the stamp card DB 14f, the expense burden DB 14l, and the fee DB 14m. The stamp card DB 14f shown in FIG. 18 is different from the stamp card DB 14f shown in FIG. 5 in that the stamp card DB 14f shown in FIG. 18 further stores a budget amount. The budget amount indicates the amount of the budget of the cost borne by the stamp card creator to grant points. This budget amount may indicate the amount per a predetermined period (for example, per month, etc.). The budget amount may be set by the creator. When creating a stamp card, it may be determined that the creator is basically required to set the budget amount. Note that even if the actual cost within the predetermined period exceeds the budget amount, the SNS server 1 may grant points to the user who has stamped the stamp card. In this case, the amount of the point fee as the cost actually borne by the stamp card creator exceeds the budget amount.

[0114] The cost burden DB 14l may store cost burden information regarding the cost burden for each community in which the manager selects to bear the cost for granting points. The SNS server 1 may be configured so that the manager of each community can select whether or not to bear the cost of points. For example, the selection may be possible when creating a community, or the selection may be changeable after the community is created. By the manager bearing the cost of points, as described below, it is possible to increase the number of users visiting the spot associated with the community. The cost burden DB 14l may store, as cost burden information, for example, a community ID, a community manager ID, a budget amount, etc. in association with each other. The community ID indicates a community in which the burden of the cost is selected. The community manager ID is the user ID of the manager of the community. The budget amount indicates the amount of the budget of the cost to be borne by the manager to grant points to users. This budget amount may indicate, for example, an amount per predetermined period. The budget amount may be set by the manager. Also, as described above, the amount of the point fee actually borne by the community manager may exceed the budget amount.

[0115] The fee DB 14m may store billing information on the point fee charged to the stamp card creator or the community manager as a cost for granting points, for each billing destination. For example, the fee DB 14m may store a user ID, a target period, a billing amount, and the like, as the fee information, in association with each other. The user ID indicates the billing destination. The billing destination is the stamp card creator or the community manager. The target period indicates the period for which the point fee is collected. For example, the target period may indicate a combination of a year and a month. The billing amount indicates the amount of the point fee to be billed. The initial value of the billing amount is 0 yen. After the period indicated by the target period has elapsed, the billing destination is billed for the point granting fee equivalent to the billing amount. For example, the SNS server 1 or another server device may execute a process for settling the point granting fee with the billing destination's credit card.

[0116] [3-3. Functional overview of the system control unit of the SNS server] Next, a functional overview of the system control unit 11 of the SNS server 1 will be described with reference to Figs. 19 and 20. Fig. 19 is a diagram showing an example of a functional block of the system control unit 11 of the SNS server 1 according to this embodiment. In Fig. 19, the same elements as in Fig. 6 are given the same reference numerals. Fig. 19 differs from Fig. 6 in that in Fig. 19, the system control unit 11 further functions as a community selection screen information transmission unit 1108, a point allocating unit 1109, and a billing amount updating unit 1110.

[0117] The community selection screen information sending unit 1108 may send community selection screen information to the user terminal 2 used by the stamp card creator. The community selection screen information may be information for displaying a community selection screen on the user terminal 2. The community selection screen may be a screen for the stamp card creator to select a community in which the stamp card can be used to promote visits to spots. For example, the community ID acquiring unit 1101 may acquire the community ID of each of two or more communities specified by the creator from the community selection screen. For example, the community selection screen information may be an HTML (HyperText Markup Language) document or other information.

[0118] The community selection screen may be a screen on which community display information indicating at least some of a plurality of mutually different communities is displayed. The community display information may include at least a community name, for example. The community selection screen may also be a screen capable of accepting an operation to designate at least any of the communities indicated by the community display information. The community selection screen may be a screen showing, for example, a search result of communities. For example, in response to a stamp card creator inputting a search condition for a community, the SNS server 1 may search for a community that satisfies the search condition.

[0119] A display priority may be set for each piece of community display information. Then, on the community selection screen, each piece of community display information may be displayed in a manner according to the display priority of the community display information. The display priority may be a display priority order. The higher the priority (or priority order) of the community display information, the higher the display priority of the community display information. For example, when the community display information is displayed in a line from top to bottom in the community selection screen, the higher the priority of the community display information, the higher the display priority of the community display information. For example, on the community selection screen, a priority order may be assigned to each position at which the community display information is displayed. The positions may be assigned priorities from top to bottom, starting from number 1. The community selection screen information transmitting unit 1108 may increase the priority of the community display information as the priority of the community display information increases. The community selection screen information transmitting unit 1108 may display each piece of community display information in a position with the same priority order as the priority order of the community display information. Alternatively, the higher the priority of the community display information, the more conspicuous the display mode of the community display information may be. Examples of the display mode include the size and color density of the community display information. The community selection screen information may be information in which the community ID of each community is associated with a display priority or an order of priority for each community. Based on the community selection screen information, the user terminal 2 may display each community display information on the community selection screen in a mode according to the priority.

[0120] The community selection screen information transmission unit 1108 may generate community selection screen information by setting the display priority of community display information indicating communities that bear the cost for granting points among at least some communities higher than the display priority of community display information indicating communities that do not bear the cost for granting points. This allows the community display information indicating communities that bear the cost to be displayed with higher priority. Therefore, the stamp card creator is more likely to select a community that bears the cost as a community in which the stamp card can be used than a community that does not bear the cost. When a user visits a spot in a specified community, the user is given points, which promotes visits to spots in the community. Whether or not the administrator of the community bears the cost can be determined by, for example, referring to the cost burden DB 14l.

[0121] When the stamping process is executed by the stamping unit 1106, the point granting unit 1109 may execute a point granting process to grant points to a user who owns a stamp card on which a stamp is to be stamped. For example, when the check-in determination unit 1104 determines that the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 is included in an area indicated by area information associated with any one of two or more community IDs acquired by the community ID acquisition unit 1101, the point granting unit 1109 may grant points to the user of the user terminal 2. For example, a predetermined number of points may be granted to the user. For convenience of explanation, it is assumed that 10 points are granted. As the point granting process, the point granting unit 1109 may add a predetermined number to the number of available points of the user stored in the point DB 31. For example, the point granting unit 1109 may execute the point granting process after the stamping process, or may execute the point granting process before the stamping process. Also, the point allocating unit 1109 may allocate points, for example, at the timing of check-in, or on the last day of the month or the last day of the next month.

[0122] When the point granting unit 1109 executes the point granting process, the billing amount update unit 1110 may update at least one of the billing amount to the stamp card creator and the billing amount to the community manager, which is the billing amount of the point granting fee stored in the fee DB 14m. For example, a unit price of the point fee may be set for each point grant. This unit price is called the point granting unit price. The point granting unit price may be, for example, an amount equal to or greater than the amount of the number of points granted to the user. If the point fee is considered to be an expense for advertising the community, the point granting unit price may be set to an amount higher than the amount of the number of points granted. The exchange rate between points and money may be predetermined. For example, one point may be equivalent to one yen. If 10 points are granted to a user for each stamp, the point granting unit price may be an amount higher than 10 yen.

[0123] If the community ID associated with the spot area including the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 indicates a community different from the community that will bear the cost of awarding the points, the billing amount update unit 1110 may add the entire point award unit price to the billing amount owed to the stamp card creator. Since the manager of that community has not chosen to bear the cost, the entire point award unit price is billed to the stamp card creator.

[0124] When the community ID associated with the spot area including the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 indicates a community that bears the cost of granting points, the billing amount update unit 1110 may add at least a part of the point grant unit price to the billing amount to the community manager. In this case, the billing amount update unit 1110 may increase at least one of the billing amounts so that the sum of the amount added to the billing amount to the stamp card creator and the amount added to the billing amount to the community manager matches the point grant unit price. Since the manager of the community has chosen to bear the cost, at least a part of the point grant unit price may be billed to the manager. For example, the billing amount update unit 1110 may add the entire point grant unit price to the billing amount to the community manager. In this case, the stamp card creator does not bear the cost.

[0125] FIG. 20 is a diagram showing an example of how points are given to a user. For example, the manager of the hotel-related community 201 shown in FIG. 2 has chosen not to bear the cost for giving points. On the other hand, the manager of the ramen chain-related community 202 has chosen to bear the cost. As shown in FIG. 20, a user U2 who owns a user terminal 2-2 stays at a hotel 401 in the spot area 301 and checks into the community 201 (step S21). In response to the check-in, the SNS server 1 stamps the stamp card 101-1 of the user U2 and gives points to the user U2 (step S22). Since the manager of the community 201 does not bear the cost, the SNS server 1 adds the point giving unit price to the amount charged to the creator of the stamp card 101 (step S23). After that, the user U2 goes to a ramen restaurant 402 in the spot area 302 and checks into the community 202 (step S24). In response to this check-in, the SNS server 1 stamps another stamp on the stamp card 101-1 and gives more points to the user U2 (step S25). Since the manager of the community 202 bears the costs, the SNS server 1 adds the unit price of the points to the amount billed to the manager (step S26).

[0126] [3-4. Operation of communication system] Next, the operation of the communication system S will be described with reference to Fig. 21 to Fig. 23. Fig. 21 is a sequence diagram showing an example of the operation of the communication system S according to this embodiment when creating a stamp card. In Fig. 21, the same processes as those in Fig. 7 are denoted by the same reference numerals.

[0127] As shown in FIG. 21, the user U1 inputs stamp card information to the stamp card creation screen (step S101). At this time, the user U1 also inputs a budget amount. Next, the user U1 inputs search conditions for the community (step S501). The user terminal 2-1 transmits a community search request including the input search conditions to the SNS server 1 (step S502). The community selection screen information transmitting unit 1108 of the SNS server 1 that receives the community search request searches for communities that satisfy the search conditions (step S503). Next, the community selection screen information transmitting unit 1108 sets a priority of each searched community (step S504). For example, the community selection screen information transmitting unit 1108 sets a priority of a community that bears the cost for giving points higher than that of other communities. The community selection screen information transmitting unit 1108 determines whether the administrator of the community bears the cost by determining, for example, the presence or absence of cost bearing information including the community ID of the searched community. Next, the community selection screen information transmitting unit 1108 generates an HTML document of a search result screen as community display information display screen information (step S505). The search result screen is a screen showing the search result of the communities. For example, the community selection screen information transmitting unit 1108 may generate community display information including the community ID and the community name of each searched community. The community selection screen information transmitting unit 1108 may generate an HTML document so that the community display information of a community with a higher priority is displayed at a higher position on the search result screen. The community selection screen information transmitting unit 1108 transmits the generated HTML document to the user terminal 2-1 (step S506). The user terminal 2-1 that has received the HTML document displays the search result screen based on the HTML document (step S507). The user U1 selects at least one community display information from the search result screen (step S508). Note that steps S501 to S508 may be executed multiple times according to the operation of the user U1.After the user U1 has finally selected two or more pieces of community display information, the user terminal 2-1 transmits the input stamp card information, a list of community IDs of the communities corresponding to the selected community display information, and the user ID of the user U1 to the SNS server 1 (step S103). The SNS server 1 generates a stamp card ID and stores the stamp card information and the stamp card association information in the storage unit 14 (steps S104, S105). Thereafter, steps S106 to S120 may be executed as shown in FIG.

[0128] Fig. 22 is a flow chart showing an example of stamp control processing by the system control unit 11 of the SNS server 1 according to this embodiment. In Fig. 22, the same processes as those in Fig. 9 are given the same reference numerals. As shown in Fig. 22, first, steps S301 to S307 are executed as in the first embodiment. After step S307, the point allocating unit 1109 adds 10 points to the number of available points stored in the point DB 31 in association with the user ID of the checked-in user U2, and updates the number of available points (step S341). Next, the billing amount updating unit 1110 executes a billing amount update process (step S342).

[0129] FIG. 23 is a flowchart showing an example of a billing amount update process by the system control unit 11 of the SNS server 1 according to the present embodiment. As shown in FIG. 23, the billing amount update unit 1110 judges whether or not the expense information is stored in the expense DB 14l in association with the community ID of the community where the user U2 has checked in (step S601). If the expense information is not stored (step S601: NO), the billing amount update unit 1110 adds the point allocation unit price to the billing amount of the stamp card creator to update the billing amount (step S602). For example, the billing amount update unit 1110 may obtain the stamp card ID associated with the community ID of the community where the user U2 has checked in from the stamp card association DB 14g. The billing amount update unit 1110 may obtain the stamp card creator ID associated with this stamp card ID from the stamp card DB 14f. The billing amount update unit 1110 may add the point allocation unit price to the billing amount stored in the fee DB 14m in association with this stamp card creator ID.

[0130] If the expense sharing information is stored (step S601: YES), the billing amount updating unit 1110 adds the point allocation unit price to the billing amount of the community manager to update the billing amount (step S603). For example, the billing amount updating unit 1110 may obtain, from the community DB 14b, a community manager ID associated with the community ID of the community to which the user U2 has checked in. The billing amount updating unit 1110 may add the point allocation unit price to the billing amount stored in the fee DB 14m in association with this community manager ID. When step S602 or S603 is completed, the billing amount update process ends. Returning to FIG. 22, when the billing amount update process ends, steps S308 to S314 are executed as in the first embodiment.

[0131] As described above, according to this embodiment, when the stamp process is executed, the SNS server 1 executes a point-granting process for granting points to the user of the user terminal 2. Therefore, the user can be more urged to go to an area related to the community designated by the creator of the stamp card.

[0132] Here, when the point granting process is executed, the SNS server 1 may update at least one of the amount billed to the stamp card creator and the amount billed to the community creator. Furthermore, when the community associated with the area including the location of the user terminal 2 is a community that does not bear the cost, the SNS server 1 may add the entire point grant unit price to the amount billed to the stamp card creator. Furthermore, when the community associated with the area including the location of the user terminal 2 is a community that bears the cost, the SNS server 1 may add at least a part of the point grant unit price to the amount billed to the community manager. In this case, the cost can be billed to an appropriate billing destination depending on whether the manager of the community bears the cost.

[0133] At this time, if the community associated with the area including the location of the user terminal 2 is a community for which the SNS server 1 bears the costs, the entire point-granting unit price may be added to the amount billed to the community manager. In this case, when the user goes within the area related to a community for which the manager bears the costs, the manager of the community bears the costs equivalent to the entire point-granting unit price.

[0134] The SNS server 1 may also transmit community selection screen information for displaying a community selection screen to the user terminal 2 used by the stamp card creator. The SNS server 1 may also generate a community selection screen by setting the priority of community display information indicating communities that will bear the cost higher than the priority of community display information indicating communities that will not bear the cost. In this case, the probability that a community whose manager bears the cost for granting points is selected can be made higher than the probability that a community whose manager does not bear the cost is selected. Therefore, it is possible to encourage the manager of the community to bear the cost for granting points.

[0135] [4. Fourth embodiment] Next, a fourth embodiment will be described. Except for the points described below, the fourth embodiment may be the same as the third embodiment. In this embodiment, if the manager of the community where the user checks in selects to bear the cost for granting points, the manager bears a part of the unit price for granting points, and the stamp card creator bears the remaining part of the unit price for granting points. The manager of the community can set the burden rate of this cost. The SNS server 1 operates so that the higher the burden rate, the more users will check in to the community. In addition, the burden rate of the cost is recommended to the community manager.

[0136] [4-1.SNS Server Configuration] Next, the configuration of the SNS server 1 will be described with reference to Figs. 24 and 25. Fig. 24 is a block diagram showing an example of a schematic configuration of the SNS server 1 according to this embodiment. In Fig. 24, the same elements as in Fig. 17 are given the same reference numerals. Fig. 24 differs from Fig. 17 in that in Fig. 24, a burden rate setting history DB 14n is further stored in the storage unit 14.

[0137] Fig. 25 is a diagram showing an example of the contents stored in the stamp history DB 14i, the cost burden DB 14l, and the burden rate setting history DB 14n. The stamp history DB 14i shown in Fig. 25 differs from the stamp history DB 14i shown in Fig. 5 in that the stamp history DB 14i shown in Fig. 25 further stores a community manager burden rate. The community manager burden rate indicates the proportion of the amount borne by the manager of the community indicated by the community ID out of the point grant unit price that occurs when points are granted to a user in response to a stamp being pressed on a stamp card. If the stamp card creator bears the entire point grant unit price, the community manager burden rate is 0 percent.

[0138] The cost burden DB 14l shown in Fig. 25 differs from the cost burden DB 14l shown in Fig. 18 in that a burden rate is further stored in the cost burden DB 14l shown in Fig. 25. The burden rate indicates the proportion of the amount of the point grant unit price that is to be borne by the manager of the community indicated by the community ID. The community manager may be able to set the burden rate. The burden rate may be, for example, greater than 0 percent and less than or equal to 100 percent.

[0139] The burden rate setting history DB 14n may store a history of the burden rate settings made by the community manager. For example, the burden rate setting history DB 14n may store, each time a burden rate is set or changed, a community ID, a community manager ID, a burden rate setting date, the set burden rate, and the like, in association with one another, as a burden rate setting log. The community ID indicates the community in which the burden rate was set. The community manager ID is the user ID of the manager who set the burden rate. The burden rate setting date indicates the date on which the burden rate was set.

[0140] [4-2. Functional overview of the system control unit of the SNS server] Next, a functional overview of the system control unit 11 of the SNS server 1 will be described with reference to Figs. 26 and 27. Fig. 26 is a diagram showing an example of a functional block of the system control unit 11 of the SNS server 1 according to this embodiment. In Fig. 26, the same elements as in Fig. 19 are given the same reference numerals. Fig. 26 differs from Fig. 19 in that in Fig. 26, the system control unit 11 further functions as a burden rate recommended information transmission unit 1111 and a burden rate acquisition unit 1112.

[0141] The burden rate recommended information transmission unit 1111 may transmit, to the user terminal 2 used by the community manager, burden rate recommended information indicating a burden rate recommended as a burden rate for the cost of granting points to a user. For example, the burden rate recommended information transmission unit 1111 may cause the user terminal 2 to display a cost burden setting screen. The burden rate recommended information may be displayed in this cost burden setting screen. The cost burden setting screen may be a screen for the community manager to select whether or not to bear the cost for granting points and to set the burden rate. The cost burden setting screen may be displayable when creating a community or when changing the cost burden setting. When it is selected to bear the cost on the cost burden setting screen, the manager sets the burden rate. At this time, the manager can refer to the burden rate recommended information. For example, a plurality of predetermined burden rates may be displayed as options on the cost burden setting screen. A burden rate may be selectable from among the options. In this case, the burden rate recommended information displayed on the cost burden setting screen may indicate which option is the recommended burden rate. Alternatively, the burden rate may be directly inputted into the cost burden setting screen. The burden rate recommended information transmission unit 1111 may display the recommended burden rate on the expense burden setting screen. Alternatively, the burden rate recommended information transmission unit 1111 may display the burden rate recommended information on a screen different from the expense burden setting screen, and after that screen is displayed, display the expense burden setting screen.

[0142] The burden rate recommended information transmission unit 1111 may determine whether to transmit the burden rate recommended information or may determine the recommended burden rate based on the past record of points being given to a user by checking in to the community. For example, the burden rate recommended information transmission unit 1111 may determine the recommended burden rate based on the number of stamps. The number of stamps is the number of users who have had their stamp cards stamped by checking in to the community managed by the administrator. The number of stamps can be calculated by referring to the stamp history DB 14i. For example, the burden rate recommended information transmission unit 1111 may determine a higher burden rate as the recommended burden rate as the number of stamps is smaller. As described later, the higher the burden rate designated by the administrator of the community, the higher the probability that the community will be selected by the stamp card creator as a community in which the stamp card can be used. Since the community can use more stamp cards, the number of users who own those stamp cards will also increase, and the number of users who check in to the community and have stamps pressed will also increase. If the community manager has never set a burden rate, the burden rate recommendation information transmission unit 1111 does not need to transmit the burden rate recommendation information. In this case, the burden rate recommendation information is not displayed on the expense burden setting screen, etc.

[0143] The burden rate recommended information transmission unit 1111 may calculate another index using the number of people who have stamped. This index may be, for example, an index that indicates a higher value as the number of people who have stamped increases, or an index that indicates a lower value as the number of people who have stamped increases. In either case, the burden rate recommended information transmission unit 1111 may recommend a higher burden rate as the number of people who have stamped decreases. For example, a table or the like that stores information indicating the correspondence between the value of the index and the burden rate may be stored in the storage unit 14. The burden rate recommended information transmission unit 1111 may determine a recommended burden rate from the calculated index based on this table or the like. The burden rate recommended information transmission unit 1111 may calculate, for example, an average value or a median value of the index per predetermined period (for example, per month, etc.), or may calculate the value of the index without dividing the period. The number of people who have stamped itself may be an index.

[0144] It is assumed that the index used is an index that indicates a higher value as the number of people who have stamped increases. In this case, the burden rate recommendation information transmission unit 1111 may transmit the burden rate recommendation information to the user terminal 2 of the administrator only when the calculated index value is equal to or less than a predetermined threshold value. That is, the burden rate recommendation information is displayed on the expense burden setting screen or the like only when the index value is equal to or less than the threshold value. When the number of people who have stamped is relatively large, it is not necessary to recommend a particular burden rate. Alternatively, it is assumed that the administrator of the community has already set some burden rate. The burden rate recommendation information transmission unit 1111 may transmit the burden rate recommendation information to the user terminal 2 of the administrator only when the burden rate corresponding to the calculated index value is higher than the burden rate set by the administrator. When a causal relationship or correlation is found between the burden rate specified by the administrator of the community and the value of the index, the burden rate recommendation information transmission unit 1111 may calculate an index for the period during which the burden rate was applied for each burden rate set by the administrator. The period during which a certain burden rate was applied can be calculated by referring to the burden rate setting history DB 14n. The burden rate recommendation information transmission unit 1111 may determine, as the recommended burden rate, a burden rate for which an index of a value higher than a predetermined threshold is calculated among the burden rates set so far. If such a burden rate does not exist, the burden rate recommendation information transmission unit 1111 may determine, as the recommended burden rate, a burden rate higher than the burden rate set so far. As described above, the higher the burden rate, the more likely the number of people who have stamped tends to be, so there is at least a correlation between the burden rate and the number of people who have stamped. However, the index calculated from the number of people who have stamped does not necessarily have a causal relationship or correlation with the burden rate. Note that, when the index used is an index that indicates a smaller value as the number of people who have stamped increases, the burden rate recommendation information transmission unit 1111 may make a judgment under the opposite condition to the conditions described so far regarding the comparison between the index and the threshold.

[0145] The index may be, for example, a stamp rate. The stamp rate is the ratio of the number of users who have stamp cards available to the community and have received a stamp by checking in to the community. The stamp rate can be calculated by referring to the issued card DB 14h and the stamp history DB 14i. The burden rate recommendation information transmission unit 1111 may recommend a higher burden rate as the stamp rate is lower.

[0146] The index may be, for example, a budget amount per person. The budget amount per person may be calculated by dividing the budget amount set by the manager of the community by the number of stamp users counted during the period in which the budget is consumed (i.e., one month, etc.). A user who checks in to a community is also a user who has earned points in response to the check-in. The budget amount per person can be calculated by referring to the stamp card DB 14f and the stamp history DB 14i. For example, the higher the budget amount per person, the higher the recommended burden rate may be. The budget amount may be an amount that the community manager is willing to bear per predetermined period. If the number of people who check in is small relative to that amount, the budget amount per person will be high. Therefore, if the budget amount per person is relatively high, the number of people who check in will be smaller than the number expected by the manager. The recommended burden rate information transmission unit 1111 may calculate the budget amount per person for each burden rate set by the manager, as described above. It is considered that there is at least a correlation between the burden rate and the budget amount per person. For example, the burden rate recommendation information transmission unit 1111 may obtain a budget amount designated by the community manager from the stamp card DB 14f. The burden rate recommendation information transmission unit 1111 may obtain a user ID included in each of the obtained stamp logs. The burden rate recommendation information transmission unit 1111 may also search for a burden rate setting log associated with the community ID of the community from the burden rate setting history DB 14n. The burden rate recommendation information transmission unit 1111 may specify the period and the number of days during which each set burden rate was applied based on the burden rate setting date included in the searched burden rate setting log. The burden rate recommendation information transmission unit 1111 may search for a stamp log including the community ID of the community from the stamp history DB 14i. The burden rate recommendation information transmission unit 1111 may calculate, for each burden rate, the number of people who stamped the stamp card during the period during which the burden rate was applied, as the number of people who stamped.The burden rate recommendation information transmission unit 1111 may calculate, for each burden rate, the budget amount per person for the period to which that burden rate is applied by dividing the number of people who checked in by the budget amount. The burden rate recommendation information transmission unit 1111 may calculate the budget amount per person per month for each burden rate based on the calculated per person budget amount and the ratio of the number of days in the period during which that burden rate was maintained to 30 days.

[0147] The burden rate recommended information transmission unit 1111 may further transmit index information indicating the calculated index value to the user terminal 2 used by the manager of the community. As a result, the burden rate recommended information transmission unit 1111 may cause the index information to be displayed on an expense burden setting screen or the like. This allows the manager to check past performance. When the burden rate recommended information transmission unit 1111 has calculated the index value for each burden rate, it may transmit index information indicating a combination of the burden rate and the index value for each burden rate.

[0148] The burden rate acquisition unit 1112 may acquire a burden rate designated by a manager of a community who will bear the cost of granting points from the manager's user terminal 2. For example, the burden rate acquisition unit 1112 may acquire a burden rate designated by the manager on a cost burden setting screen. The burden rate acquisition unit 1112 may store the acquired burden rate in the cost burden DB 14l in association with the community ID of the community.

[0149] As in the third embodiment, the community selection screen sending unit 1108 may generate community selection screen information by setting the display priority of community display information indicating communities that bear the cost of granting points higher than the display priority of community display information indicating communities that do not bear the cost of granting points. Furthermore, the community selection screen sending unit 1108 may generate community selection screen information by setting the display priority of community information indicating a community to a higher value as the burden rate designated by the manager of the community increases. As a result, the community display information of a community is displayed with higher priority as the burden rate of the manager of the community increases. Therefore, the probability that a stamp card creator will select a community with a higher burden rate as a community in which a stamp card can be used increases. Therefore, visits to spots in communities with a high burden rate are promoted.

[0150] When the community ID associated with the spot area including the location of the user terminal 2 indicated by the location information acquired by the location information acquisition unit 1103 indicates a community that bears the cost of granting points, the billing amount updating unit 1110 may add an amount equivalent to the burden rate acquired by the burden rate acquisition unit 1112 for the point grant unit price to the billing amount owed to the manager of that community.The billing amount updating unit 1110 may then add an amount equivalent to the difference between the point grant unit price and the amount added to the billing amount owed to the manager to the billing amount owed to the stamp card creator.

[0151] FIG. 27 is a diagram showing an example of how points are given to a user. For example, the manager of the community 202 related to the ramen chain shown in FIG. 2 has chosen to cover the cost and has specified a 40% burden rate. On the other hand, the manager of the community 203 related to the community related to the soba noodle restaurant has chosen to cover the cost and has specified a 70% burden rate. As shown in FIG. 27, a user U2 who has a user terminal 2-2 goes to a ramen shop 402 in the spot area 302 and checks in to the community 202 (step S31). In response to the check-in, the SNS server 1 stamps the stamp card 101-1 of the user U2 and gives points to the user U2 (step S32). The SNS server 1 adds 40% of the point-granting unit price to the amount billed to the manager of the community 202 (step S33), and adds 60% of the point-granting unit price to the amount billed to the creator of the stamp card 101 (step S34). For example, if the point grant unit price is 20 yen, 80 yen is added to the billing amount of the manager of the community 202, and 120 yen is added to the billing amount of the creator of the stamp card 101. After that, the user U2 goes to the soba restaurant 407 in the spot area 305 and checks in to the community 203 (step S35). In response to the check-in, the SNS server 1 stamps the stamp card 101-1 of the user U2 and grants points to the user U2 (step S36). The SNS server 1 adds 70% of the point grant unit price to the billing amount of the manager of the community 203 (step S37), and adds 30% of the point grant unit price to the billing amount of the creator of the stamp card 101 (step S38). For example, 140 yen is added to the billing amount of the manager of the community 202, and 60 yen is added to the billing amount of the creator of the stamp card 101.

[0152] [4-3. Operation of communication system] Next, the operation of the communication system S will be described with reference to Figs. 28 to 31. Fig. 28 is a sequence diagram showing an example of the operation of the communication system S according to this embodiment when setting the cost burden. As shown in Fig. 28, a user U3 who is a manager of a community operates a user terminal 2-3 as the user terminal 2 of the user U3. In response to this operation, the user terminal 2-3 transmits a cost burden setting screen request to the SNS server 1 (step S701). The cost burden setting screen request may include, for example, the user ID of the user U3 and the community ID of the community managed by the user U3. The SNS server 1 that receives the cost burden setting screen request executes a cost burden setting screen information generation process (step S702).

[0153] FIG. 29 is a flowchart showing an example of the cost burden setting screen information generation process by the system control unit 11 of the SNS server 1 according to this embodiment. As shown in FIG. 29, the burden rate recommended information transmission unit 1111 acquires an HTML document template of the cost burden setting screen from the storage unit 14 (step S801). Next, the burden rate recommended information transmission unit 1111 searches the stamp card association DB 14g for a stamp card ID associated with the community ID included in the cost burden setting screen request (step S802). As a result of the search, the burden rate recommended information transmission unit 1111 determines whether or not there is a corresponding stamp card ID (step S803). If there is no corresponding stamp card ID (step S803: NO), the cost burden setting screen information generation process ends.

[0154] If there is a corresponding stamp card ID (step S803: YES), for each stamp card ID found, the issued card DB 14h is searched for issued card information including that stamp card ID (step S804). Next, the burden rate recommendation information transmission unit 1111 searches the stamp history DB 14i for a stamp log including the community ID included in the expense burden setting screen request (step S805).

[0155] Next, the burden rate recommended information transmission unit 1111 calculates the stamp rate (step S806). For example, the burden rate recommended information transmission unit 1111 may calculate the number of users who own stamp cards by counting the number of issued card information that has been searched. The burden rate recommended information transmission unit 1111 may also calculate the number of people who have stamps based on the user IDs included in each of the searched stamp logs. The burden rate recommended information transmission unit 1111 may calculate the stamp rate by dividing the number of people who have stamps by the number of users who own stamp cards.

[0156] Next, the recommended burden rate information sending unit 1111 adds index information indicating the calculated stamp rate to the HTML document of the expense sharing setting screen (step S807). Next, the recommended burden rate information sending unit 1111 determines whether the stamp rate is higher than the threshold (step S808). If the stamp rate is higher than the threshold (step S808: YES), the expense sharing setting screen information generating process ends. If the stamp rate is equal to or lower than the threshold (step S808: NO), the recommended burden rate information sending unit 1111 adds recommended burden rate information indicating the burden rate corresponding to the calculated stamp rate to the HTML document of the expense sharing setting screen (step S809), and the expense sharing setting screen information generating process ends.

[0157] Returning to FIG. 28, when the cost burden setting screen information generating process is completed, the incentive burden rate information transmitting unit 1111 transmits the generated HTML document of the cost burden setting screen to the user terminal 2-3 (step S703). The user terminal 2-3 displays the cost burden setting screen based on this HTML document (step S704). On the cost burden setting screen, the user U3 selects to bear the cost for giving points and specifies the burden rate (step S705). The user terminal 2-3 transmits the cost burden information including the specified burden rate to the SNS server 1 (step S706). The burden rate acquiring unit 1112 of the SNS server 1 that has received the cost burden information stores this cost burden information in the cost burden DB 14l (step S707). The burden rate acquiring unit 1112 also stores the burden rate setting log in the burden rate setting history DB 14n. For example, the burden rate acquisition unit 1112 may generate a burden rate setting log based on the community ID, the community manager ID, and the burden rate included in the expense burden information, as well as today's date.

[0158] FIG. 30 is a sequence diagram showing an example of the operation of the communication system S according to this embodiment when creating a stamp card. In FIG. 30, the same processes as those in FIG. 21 are assigned the same reference numerals. As shown in FIG. 30, first, steps S101 and S501 to S503 are executed as in the third embodiment. Next, the community selection screen information sending unit 1108 sets the priority of each community found (step S511). For example, the community selection screen information sending unit 1108 sets the priority of a community that will bear the cost of giving points higher than that of other communities. Furthermore, based on the burden rate included in the cost burden information, the community selection screen information sending unit 1108 sets the priority of a community that will bear the cost higher among the communities that will bear the cost. Next, steps S505 to S508 and S103 to S105 are executed as in the third embodiment.

[0159] Fig. 31 is a flow chart showing an example of a billing amount update process by the system control unit 11 of the SNS server 1 according to this embodiment. In Fig. 31, the same processes as those in Fig. 23 are given the same reference numerals. As shown in Fig. 31, the billing amount update unit 1110 judges whether or not the expense burden information is stored in the expense burden DB 141 in association with the community ID of the community where the user U2 has checked in (step S601). If the expense burden information is not stored (step S601: NO), the billing amount update unit 1110 adds the point grant unit price to the billing amount of the stamp card creator to update the billing amount (step S602).

[0160] If the cost sharing information is stored (step S601: YES), the billing amount updating unit 1110 obtains the community manager's share of the cost from the cost sharing information (step S611). Next, the billing amount updating unit 1110 adds the share of the cost to the point grant unit price to calculate an additional amount. Then, the billing amount updating unit 1110 adds this additional amount to the billed amount of the community manager to update the billed amount (step S612). Next, the billing amount updating unit 1110 subtracts the community manager's share of the cost from 1 to calculate the stamp card creator's share of the cost. The billing amount updating unit 1110 calculates the share of the cost to the point grant unit price to calculate an additional amount. Then, the billing amount updating unit 1110 adds this additional amount to the billed amount of the stamp card creator to update the billed amount (step S613). After step S602 or step S613, the billing amount update unit 1110 adds the burden rate of the community manager to the stamp log stored in the stamp history DB 14i in the stamp control process shown in FIG. 22 (step S614), and the billing amount update process ends.

[0161] As described above, according to this embodiment, the SNS server 1 may obtain a burden rate designated by the manager of the community who will bear the cost of granting points. Furthermore, when the community associated with the area including the location of the user terminal 2 is a community that will bear the cost, the SNS server 1 may add an amount equivalent to the obtained burden rate to the amount billed to the community manager for the point grant unit price. Furthermore, the SNS server 1 may add an amount equivalent to the difference between the point grant unit price and the amount added to the amount billed to the community manager to the amount billed to the stamp card creator.

[0162] Here, when the SNS server 1 transmits the community selection screen information, the higher the burden rate designated by the administrator of the community, the higher the priority of the community display information representing that community may be given to generate the community selection screen information. In this case, the higher the burden rate designated by the administrator, the higher the probability that that community will be selected. Therefore, it is possible to encourage the administrator of the community to bear a higher burden rate for the costs of granting points.

[0163] The SNS server 1 may also acquire the number of users who have been granted points because the user terminal 2 was located in a spot area indicated by area information associated with a community ID that identifies a community for which the administrator bears the costs, among users who have been granted points. The SNS server 1 may also transmit recommended burden rate information indicating a recommended burden rate to the user terminal 2 used by the administrator. At this time, the SNS server 1 may increase the recommended burden rate as the number of users acquired is smaller. In this case, the administrator can specify an actual burden rate with reference to the recommended burden rate. The higher the designated burden rate, the higher the probability that the community will be selected by the stamp card creator. Since points are granted to users who have been in a spot area related to the selected community, if the number of users who go to a spot area related to the community is small, the number of users can be increased.

[0164] (Supplementary Note 1) A stamp card management device characterized by comprising: an acquisition means for acquiring two or more community identification information that identifies two or more communities designated by a creator who creates a stamp card, among a plurality of different communities in which information related to each of the predetermined areas is provided within the community; an identification information storage control means for storing in an identification information storage means a stamp card identification information that identifies the stamp card to be created, in association with the acquired two or more community identification information; an acquisition means for acquiring location information that indicates a location of a portable terminal device; and a stamp means for executing a stamp process for pressing a stamp on the stamp card for a user of the terminal device when the location indicated by the acquired location information is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information, among the area information stored in an area information storage means that stores area information indicating the area related to the community, in association with the community identification information that identifies the community, for each of the plurality of communities.

[0165] (Appendix 2) The stamp card management device described in Appendix 1 is characterized in that it further comprises a joining means for executing a process of joining the user to the community identified by the community identification information associated with any of the area information stored in the area information storage means when the location indicated by the acquired location information is included in the area indicated by any of the area information stored in the area information storage means.

[0166] (Appendix 3) The stamp card management device according to appendix 1 or 2, characterized in that, for each of the two or more communities, non-stamp information indicating that the stamp has not been pressed and stamp information indicating that the stamp has been pressed are stored in a stamp information storage means in association with the stamp card identification information and user identification information identifying the user who has the created stamp card, and the stamp means is configured to change the non-stamp information to the stamp information as the stamp processing when the non-stamp information is stored in the stamp information storage means in association with the stamp card identification information and the user identification information identifying the user of the terminal device for a community identified by the community identification information associated with the area information indicating the area including the location indicated by the acquired location information.

[0167] (Appendix 4) The two or more communities are two or more business communities in which information related to two or more different businesses that each sell a trading object is provided within the community, each of the two or more businesses sells the trading object at a facility related to the business, and for each of the two or more businesses, the area indicated by the area information associated with the community identification information that identifies the business community related to the business includes the location of the facility related to the business. This stamp card management device is characterized in that:

[0168] (Appendix 5) The stamp card management device described in any one of Appendices 1 to 4, characterized in that the stamp means executes the stamp processing on the condition that the user is a member of at least one of the two or more communities.

[0169] (Appendix 6) A stamp card management device as described in any one of Appendices 1 to 5, characterized in that the two or more areas indicated by the two or more area information stored in the area information storage means for each of the two or more communities include locations that are different from each other.

[0170] (Appendix 7) The stamp card management device according to appendix 1, further comprising an assigning means for executing an assigning process to assign points of a point program to a user of the terminal device when the stamp process is executed by the stamping means.

[0171] (Appendix 8) The stamp card management device according to appendix 7, further comprising an update means for updating at least one of the stored first and second billing amounts when the granting process is executed by the granting means, wherein a first billing amount to be billed to the creator for the granting of the points is stored in a billing amount storage means, and a second billing amount to be billed to an administrator of one of the multiple communities that has chosen to bear the cost of granting the points is stored in the billing amount storage means, and wherein the update means adds the entire cost burden amount for granting the points to the first billing amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that does not bear the cost, and adds at least a part of the cost burden amount to the second billing amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that does bear the cost, and wherein the sum of the first additional amount added to the first billing amount and the second additional amount added to the second billing amount becomes the cost burden amount.

[0172] (Appendix 9) The stamp card management device described in Appendix 8 is characterized in that the update means adds the entire amount of the cost to the second billing amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost.

[0173] (Appendix 10) The stamp card management device according to appendix 8 or 9, further comprising a screen information transmitting means for transmitting to a creator terminal device used by the creator screen information that displays a screen in which each piece of community information indicating at least a portion of the multiple communities is displayed in a manner corresponding to the display priority of the community information, and that can accept an operation to select at least one of the community information displayed on the screen, wherein the acquiring means acquires from the creator terminal device the community identification information that identifies the community indicated by the community information selected by the creator from the screen, and the screen information transmitting means generates the screen information by setting the priority of the community information indicating communities that will bear the cost, among the at least a portion of the communities, higher than the priority of the community information indicating communities that will not bear the cost.

[0174] (Appendix 11) The stamp card management device described in Appendix 8 is further provided with a burden rate acquisition means for acquiring a burden rate specified by an administrator of the community that bears the cost of granting the points, and the update means adds the second additional amount equivalent to the acquired burden rate to the second billing amount for the cost burden amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the cost, and adds the first additional amount equivalent to the difference between the cost burden amount and the second additional amount to the first billing amount.

[0175] (Appendix 12) The stamp card management device according to appendix 11 further comprises a screen information transmitting means for transmitting to a creator terminal device used by the creator screen information that displays a screen in which each of community information indicating at least a portion of the multiple communities is displayed in a manner corresponding to the display priority of the community information, and that can accept an operation to select at least one of the community information displayed on the screen, wherein the acquiring means acquires from the creator terminal device the community identification information that identifies the community indicated by the community information selected by the creator from the screen, and the screen information transmitting means generates the screen information by increasing the priority of the community information indicating the community as the burden rate specified by the administrator of the community increases.

[0176] (Appendix 13) The stamp card management device described in appendix 11 or 12 further comprises a number acquisition means for acquiring the number of users who have been granted points by the granting means and who have been granted points because their terminal device was located within the area indicated by the area information associated with the community identification information that identifies the community for which the operator bears the costs, and a recommendation information sending means for sending recommendation information indicating a recommended burden rate to an operator terminal device used by the operator who bears the costs, the recommendation information sending means setting the recommended burden rate to a higher number of users acquired, wherein the burden rate acquisition means acquires the specified burden rate from the operator terminal device to which the recommendation information is sent.

[0177] (Appendix 14) A stamp card management method executed by a computer, comprising: an acquisition step of acquiring two or more community identification information identifying two or more communities designated by a creator who creates a stamp card, among a plurality of mutually different communities in which information related to each of the predetermined areas is provided within the community; an identification information storage control step of storing stamp card identification information identifying the stamp card to be created in an identification information storage means, in association with the acquired two or more community identification information; an acquisition step of acquiring location information indicating a location of a portable terminal device; and a stamp step of executing a stamp process of pressing a stamp on the stamp card for a user of the terminal device when the location indicated by the acquired location information is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information, among the area information stored in an area information storage means that stores area information indicating the area related to the community, in association with the community identification information identifying the community, for each of the plurality of communities. [Explanation of symbols]

[0178] 1. SNS Server 2. User terminal 3 Point Management Server 11 System control section 12 System Bus 13 Input / Output Interface 14 Storage section 14a Member DB 14b Community DB 14c area DB 14d Check-in history DB 14e Community Member DB 14f Stamp Card DB 14g Stamp card association DB 14h Issued card DB 14i Stamp History DB 14j Bonus DB 14k Issued Card Rally DB 14l Cost sharing DB 14m Fee DB 14n Contribution rate setting history DB 15 Communications Department 1101 Community ID Acquisition Department 1102 Stamp Card Creation Department 1103 Location information acquisition unit 1104 Check-in Judgment Unit 1105 Participation 1106 Stamp Section 1107 Benefits Granting Department 1108 Community selection screen information transmission section 1109 Point Granting Department 1110 Billing Amount Update Department 1111 Transmission of recommended burden rate information 1112 Contribution Rate Acquisition Department NW Network S Communication System

Claims

1. An acquisition means for acquiring two or more community identification information for identifying two or more communities designated by a creator who creates a stamp card, among a plurality of different communities in which information related to each of the predetermined areas is provided within the community; an identification information storage control means for storing, in an identification information storage means, stamp card identification information for identifying the stamp card to be created in association with the two or more acquired community identification information; An acquisition means for acquiring location information indicating a location of a portable terminal device; a stamp means for executing a stamp process for pressing a stamp on the stamp card of the user of the terminal device when the location indicated by the acquired location information is included in the area indicated by the area information associated with any of the two or more community identification information associated with the stamp card identification information among the area information stored in an area information storage means for storing area information indicating the area related to the community in association with the community identification information identifying the community for each of the plurality of communities; A stamp card management device comprising:

2. The stamp card management device of claim 1, further comprising a joining means for executing a process of joining the user to the community identified by the community identification information associated with any of the area information stored in the area information storage means when the location indicated by the acquired location information is included in the area indicated by any of the area information stored in the area information storage means.

3. Either non-stamp information indicating that the stamp is not affixed or stamp information indicating that the stamp is affixed is stored in a stamp information storage means for each of the two or more communities in association with the stamp card identification information and user identification information identifying a user having the created stamp card; the stamp means, for a community among the two or more communities indicated by the community identification information associated with the area information indicating the area including the position indicated by the acquired location information, changes the non-stamp information to the stamp information as the stamp processing when the non-stamp information is stored in the stamp information storage means in association with the stamp card identification information and the user identification information identifying the user of the terminal device; A stamp card management device as described in claim 1 or 2, characterized in that when the number of stamp information stored in the stamp information storage means in association with the stamp card identification information and the user identification information reaches a predetermined number, a privilege is granted to the user identified by the user identification information.

4. the two or more communities are two or more business communities in which information related to two or more different businesses that sell the transaction object is provided within the community, Each of the two or more businesses sells the trading object at a facility related to the business; The stamp card management device described in claim 1 or 2, characterized in that for each of the two or more businesses, the area indicated by the area information associated with the community identification information identifying the business community related to the business includes the location of the facility related to the business.

5. 3. The stamp card management device according to claim 1, wherein said stamping means executes said stamping process on the condition that said user is a member of at least one of said two or more communities.

6. A stamp card management device as described in claim 1 or 2, characterized in that the two or more areas indicated by the two or more area information stored in the area information storage means for each of the two or more communities include different locations from each other.

7. 2. The stamp card management device according to claim 1, further comprising an assigning means for executing an assigning process for assigning points of a point program to a user of the terminal device when the stamp process is executed by the stamping means.

8. a first billing amount to be billed to the creator for the provision of the points is stored in a billing amount storage means; a second billing amount to be billed to a manager of a community that has selected to bear the cost of granting the points among the plurality of communities is stored in the billing amount storage means; and updating means for updating at least one of the stored first claim amount and the stored second claim amount when the granting process is executed by the granting means, The update means includes: If the community identification information associated with the area including the location indicated by the acquired location information indicates the community that does not bear the cost, the entire cost to be paid for granting the points is added to the first billing amount; The stamp card management device described in claim 7, characterized in that when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost, at least a portion of the cost burden amount is added to the second billing amount, and the sum of a first additional amount added to the first billing amount and a second additional amount added to the second billing amount becomes the cost burden amount.

9. The stamp card management device of claim 8, characterized in that the update means adds the entire amount of the cost to the second billing amount when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost.

10. a screen information transmitting means for transmitting, to a creator terminal device used by the creator, screen information for displaying a screen in which each of community display information indicating at least a portion of the plurality of communities is displayed in a mode corresponding to a display priority of the community display information, and the screen information capable of receiving an operation for selecting at least one of the community display information displayed on the screen, the acquiring means acquires, from the creator terminal device, the community identification information for identifying a community indicated by the community display information selected by the creator from the screen; The stamp card management device described in claim 8 or 9, characterized in that the screen information sending means generates the screen information by setting the priority of the community display information indicating communities that will bear the cost, among the at least some of the communities, higher than the priority of the community display information indicating communities that will not bear the cost.

11. The system further includes a burden rate acquisition means for acquiring a burden rate designated by a manager of the community who bears the cost of granting the points, The stamp card management device of claim 8, characterized in that when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that will bear the cost, the update means adds the second additional amount corresponding to the acquired burden rate for the cost burden amount to the second billing amount, and adds the first additional amount corresponding to the difference between the cost burden amount and the second additional amount to the first billing amount.

12. a screen information transmitting means for transmitting, to a creator terminal device used by the creator, screen information for displaying a screen in which each of community display information indicating at least a portion of the plurality of communities is displayed in a mode corresponding to a display priority of the community display information, and the screen information capable of receiving an operation for selecting at least one of the community display information displayed on the screen, the acquiring means acquires, from the creator terminal device, the community identification information for identifying a community indicated by the community display information selected by the creator from the screen; The stamp card management device according to claim 11, characterized in that the screen information sending means generates the screen information by increasing the priority of the community display information representing the community, the higher the burden rate specified by the administrator of the community.

13. a number-of-users acquiring means for acquiring the number of users to whom the points have been granted by the granting means and who have been granted the points because the terminal device was located within the area indicated by the area information associated with the community identification information that identifies the community for which the administrator bears the costs; a recommended information transmission means for transmitting recommended information indicating a recommended burden rate to a manager terminal device used by the manager who bears the expenses, the recommended information transmission means setting the recommended burden rate to a higher value as the acquired number of people decreases; Further comprising:

13. The stamp card management device according to claim 12, wherein said burden rate acquisition means acquires said designated burden rate from said administrator terminal device to which said recommendation information is to be transmitted.

14. 1. A stamp card management method executed by a computer, comprising: An acquisition step of acquiring two or more community identification information for identifying two or more communities designated by a creator who creates a stamp card, among a plurality of different communities in which information related to a predetermined area is provided within the community; an identification information storage control step of storing stamp card identification information for identifying the stamp card to be created in association with the two or more acquired community identification information in an identification information storage means; An acquisition step of acquiring location information indicating a location of a portable terminal device; a stamp step of executing a stamp process for pressing a stamp on the stamp card for a user of the terminal device when the location indicated by the acquired location information is included in the location indicated by the location information associated with any of the two or more community identification information associated with the stamp card identification information among the location information stored in a location information storage means for storing, for each of the plurality of communities, location information indicating the location related to the community in association with the community identification information identifying the community; A stamp card management method comprising:

Citation Information

Patent Citations

  • Simulation game device

    JP2018037051A

  • Commodity sales processing system, commodity sales processing apparatus and method, and control program

    JP2021033588A

  • Information processor and information processing method

    JP2023128452A

  • Information processing system and program

    JP2019091146A