JP7847170B2 - Stamp card management device and stamp card management method - Google Patents

Description

This invention relates to a method for stamping a user's stamp card upon their visit to a specific location.

Traditionally, a service has been known where users receive stamps on their stamp cards when they visit a specific location. For example, a store operator issues stamp cards to users. Users receive stamps on their cards when they use the store. Generally, once a certain number of stamps are accumulated, users can receive some kind of benefit from the operator's store. Furthermore, technologies for managing electronic stamp cards, rather than physical paper cards, are also known.

These stamp cards typically differ from one business to another. Therefore, users who frequented multiple businesses needed to possess multiple stamp cards. Furthermore, users could not use stamps obtained at one business's store at another. In relation to this situation, Patent Document 1 discloses a technology for using a common stamp across multiple stores.

Japanese Patent Publication No. 2019-91146

For example, suppose an internet community is created related to a specific location, and information related to that location is provided within this community. Members of this community can share information related to that location online. One possibility is to create a stamp card for such a community and offer a service where users who visit locations related to that community receive stamps on the card. When providing such a service, it would be convenient to be able to specify separate communities with different related locations and create a common stamp card for those communities.

The present invention has been made in view 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 can better encourage users to go to areas related to communities designated by the creator of the stamp card.

One aspect of the present invention is a stamp card management device in which stamp card identification information for identifying a stamp card and community identification information for identifying a community associated with the stamp card from among a plurality of communities each associated with a predetermined area are stored in an identification information storage means; for each of the plurality of communities, area information indicating the area associated with the community is stored in an area information storage means in association with the community identification information for identifying the community; a first billing amount to be charged to the creator who created the stamp card for the awarding of points in the point program is stored in a billing amount storage means; a second billing amount to be charged to the operator of a community that has chosen to bear the cost of awarding the points from among the plurality of communities is stored in the billing amount storage means; a location information acquisition means for acquiring location information indicating the location of a portable terminal device and area information stored in the area information storage means, associated with the community identification information associated with the stamp card identification information The device comprises: a processing means that, when the area indicated by the assigned area information includes the location indicated by the acquired location information, performs a stamping process to stamp the stamp card for the user of the terminal device and performs a granting process to grant points to the user of the terminal device; and an update means that, when the granting process is performed by the processing means, updates at least one of the stored first billing amount and second billing amount, wherein the update means adds the entire amount of the cost to grant 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 a community that does not bear the cost, and adds at least a portion 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 a community that bears the cost, and the sum of the first added amount added to the first billing amount and the second added amount added to the second billing amount becomes the cost to be borne .

This aspect suggests that users can be more encouraged to visit areas related to the community specified by the stamp card creator.

A further aspect of the present invention is that the updating means, when the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the costs, adds the entire amount of the costs to the second invoice amount.

According to this aspect, if a user engages in activities within a community-related area where the administrator bears the costs, the administrator of that community will bear the entire cost of awarding points.

A further aspect of the present invention is a screen information transmission means that transmits to a creator terminal device used by the creator screen information that displays a screen in which each of the community display information representing at least some of the communities among the plurality of communities is displayed in a manner corresponding to the priority of display of the community display information, and which accepts an operation to select at least one of the community display information displayed on the screen; a community identification information acquisition means that acquires from the creator terminal device community identification information that identifies the community indicated by the community display information selected by the creator from the screen; and an identification information storage control means that stores the stamp card identification information in the identification information storage means in association with the acquired community identification information, wherein the screen information transmission means generates the screen information by setting the priority of the community display information representing the community that bears the cost among at least some of the communities to be higher than the priority of the community display information representing the community that does not bear the cost.

According to this aspect, the screen for selecting communities to which users who have visited a given area will receive stamps on their stamp card and points will display community information for at least some of the communities. Each community information is displayed in a manner corresponding to its predetermined display priority. For example, the higher the display priority of the community information, the more frequently it will be displayed. Therefore, the higher the display priority of the community information, the higher the probability that it will be selected from the screen. The display priority of community information for communities where the operator bears the cost of awarding points will be higher than that of communities where the operator does not. Therefore, the probability of selecting communities where the operator bears the cost of awarding points can be made higher than the probability of selecting communities where the operator does not. Consequently, this encourages community operators to bear the cost of awarding points.

A further aspect of the present invention further comprises a burden rate acquisition means for acquiring a burden rate specified by the operator of the community that bears the cost of awarding the points, wherein the update means, 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, adds the second additional amount corresponding to the acquired burden rate to the cost amount to the second billing amount, and adds the first additional amount corresponding to the difference between the cost amount and the second additional amount to the first billing amount.

According to this aspect, community administrators who choose to bear the cost of awarding points specify their contribution rate. When a user engages in activities within the community's relevant area, the community administrator bears an amount equivalent to the specified contribution rate of the cost of awarding points. The creator of the stamp card then bears the remaining cost after deducting the community administrator's contribution from the total cost.

A further aspect of the present invention is a screen information transmission means that transmits to a creator terminal device used by the creator screen information that displays a screen in which each of the community display information representing at least some of the communities among the plurality of communities is displayed in a manner corresponding to the display priority of said community display information, and which accepts an operation to select at least one of the community display information displayed on said screen,
The screen information transmission means further comprises community identification information acquisition means for acquiring community identification information from the creator terminal device to identify a community indicated by the community display information selected by the creator from the screen, and identification information storage control means for storing the stamp card identification information in the identification information storage means in association with the acquired community identification information, wherein the screen information transmission means generates the screen information by increasing the priority of the community display information indicating the community as the burden rate specified by the operator of the community is higher.

According to this aspect, the screen for selecting communities to which users who have visited a given area will receive stamps on their stamp card and points will display community information for at least some of the communities. Each community information is displayed in a manner corresponding to the display priority set for that community information. For example, the higher the display priority of the community information, the more frequently it will be displayed. Therefore, the higher the display priority of the community information, the higher the probability that it will be selected from the screen. The higher the burden rate specified by the community administrator, the higher the display priority of the community information for that community. Therefore, the higher the burden rate specified by the administrator, the higher the probability that the community will be selected. Consequently, this encourages community administrators to increase the burden rate for the costs of awarding points.

A further aspect of the present invention is a number acquisition means for acquiring the number of users who have been awarded points by the processing means, and who have been awarded points because the terminal device is 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 transmission means for transmitting recommendation information indicating a recommended burden rate to an operator terminal device used by the operator who bears the costs, wherein the recommendation information transmission means increases the recommended burden rate as the number of acquired people decreases, and the burden rate acquisition means acquires the specified burden rate from the operator terminal device to which the recommendation information is transmitted.

According to this aspect, the number of users who receive stamps on their stamp cards and earn points by visiting areas related to communities where the operator bears the cost of awarding points is recorded. The lower this number, the higher the operator is recommended to bear the cost. The operator can then specify their actual burden rate, using the recommended rate as a reference. A higher designated burden rate increases the likelihood that the community will be selected by the stamp card creator. Since points are awarded to users who visit areas related to the selected community, if the number of users visiting these areas is low, this can be increased.

A further aspect of the present invention is a computer-based stamp card management method, wherein stamp card identification information for identifying a stamp card and community identification information for identifying a community associated with the stamp card from among a plurality of communities each associated with a predetermined area are stored in an identification information storage means, for each of the plurality of communities, area information indicating the area associated with the community is stored in an area information storage means in association with the community identification information for identifying the community, a first billing amount to be billed to the creator who created the stamp card for the awarding of points in the point program is stored in a billing amount storage means, and a second billing amount to be billed to the operator of a community that has chosen to bear the cost of awarding the points from among the plurality of communities is stored in the billing amount storage means, and a location information acquisition step to acquire location information indicating the location of a portable terminal device, and the community identification information associated with the stamp card identification information among the area information stored in the area information storage means The process includes, if the area indicated by the area information associated with the information includes the location indicated by the acquired location information, a process step of performing a stamping process to stamp the stamp card for the user of the terminal device and a granting process to grant points to the user of the terminal device; and, if the granting process is performed by the process step, an update step of updating at least one of the stored first billing amount and second billing amount, wherein the update step is characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates a community that does not bear the costs, the entire amount of the cost to grant the points is added to the first billing amount, and if the community identification information associated with the area including the location indicated by the acquired location information indicates a community that bears the costs, at least a portion of the cost is added to the second billing amount, and the sum of the first added amount added to the first billing amount and the second added amount added to the second billing amount becomes the cost burden amount .

According to the present invention, users can be more encouraged to go to areas related to the community specified by the creator of the stamp card .

This figure shows an example of the outline configuration of a communication system S according to one embodiment. This diagram illustrates an example of the concept of a stamp card shared by two or more communities. This is a diagram illustrating an example of how stamps are applied to a stamp card. This is a block diagram showing an example of the outline configuration of an SNS server 1 according to one embodiment. This figure shows an example of the contents stored in the database. This figure shows an example of a functional block of the system control unit 11 of an SNS server 1 according to one embodiment. This is a sequence diagram showing an example of the operation of a communication system S according to one embodiment. This flowchart shows an example of the check-in/check-out determination process by the system control unit 11 of the SNS server 1 according to one embodiment. This flowchart shows an example of stamp control processing by the system control unit 11 of the SNS server 1 according to one embodiment. This is a block diagram showing an example of the outline configuration of an SNS server 1 according to one embodiment. This figure shows an example of the contents stored in the stamp card DB14f, the stamp card association DB14g, and the issued card rally DB14k. This is a diagram showing an example of a stamp card. This is a diagram illustrating an example of how stamps are applied to a stamp card. This flowchart shows an example of stamp control processing by the system control unit 11 of the SNS server 1 according to one embodiment. This flowchart shows an example of stamp control processing by the system control unit 11 of the SNS server 1 according to one embodiment. This figure shows an example of the outline configuration of a communication system S according to one embodiment. This is a block diagram showing an example of the outline configuration of an SNS server 1 according to one embodiment. This figure shows an example of the contents stored in the stamp card DB14f, expense burden DB14l, and fee DB14m. This figure shows an example of a functional block of the system control unit 11 of an SNS server 1 according to one embodiment. This figure shows an example of how points are awarded to a user. This is a sequence diagram showing an example of the operation of a communication system S according to one embodiment when creating a stamp card. This flowchart shows an example of stamp control processing by the system control unit 11 of the SNS server 1 according to one embodiment. This flowchart shows an example of the billing amount update process performed by the system control unit 11 of the SNS server 1 according to one embodiment. This is a block diagram showing an example of the outline configuration of an SNS server 1 according to one embodiment. This figure shows an example of the contents stored in the stamp history DB14i, the cost burden DB14l, and the cost burden rate setting history DB14n. This figure shows an example of a functional block of the system control unit 11 of an SNS server 1 according to one embodiment. This figure shows an example of how points are awarded to a user. This sequence diagram shows an example of the operation when setting the cost burden of a communication system S according to one embodiment. This flowchart shows an example of the cost burden setting screen information generation process by the system control unit 11 of the SNS server 1 according to one embodiment. This is a sequence diagram showing an example of the operation of a communication system S according to one embodiment when creating a stamp card. This flowchart shows an example of the billing amount update process performed by the system control unit 11 of the SNS server 1 according to one embodiment.

[1. First Embodiment]
A first embodiment of the present invention will be described in detail below with reference to the drawings.

[1-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 Figure 1. Figure 1 is a diagram showing an example of the general configuration of the communication system S according to this embodiment.

As shown in Figure 1, the communication system S consists of an SNS (Social Networking Service) server 1 and multiple user terminals 2. The SNS server 1 and each user terminal 2 are connected to a network NW. The network NW is constructed using, for example, the internet, dedicated communication lines (e.g., CATV (Community Antenna Television) lines), mobile communication networks (including base stations, etc.), and gateways.

SNS Server 1 may be a server device that performs processing related to Spot SNS. For example, SNS Server 1 may perform processing to control the creation of communities, user joining of communities, and the exchange of information among community members. Spot SNS may be an SNS for exchanging information related to a spot or things related to a spot within a community. The themes for information exchange in the community may be spots or things related to spots. A spot may be, for example, a facility, a tourist spot, a monument, a landmark, a natural geographical feature, a place where a particular event is held or occurs, or other place. A facility may be a place where a business related to that facility provides or sells goods for trade. Such a facility may be a store or an office. Goods for trade may be anything that can be the subject of a commercial transaction. Goods for trade may be at least one of goods and services. Things related to a spot may be, for example, an individual or organization that conducts some activity at that spot, an object at that spot, or an event held or occurring at that spot. Users of Spot SNS may be able to create communities. When creating a community, the community administrator can define one or more "spot areas" associated with that community. A spot area is a geographical area. The community administrator can define spot areas to include specific locations where information is exchanged within the community. A spot-based SNS may be one that allows users to become members of a community on the condition that they are located within one of the defined spot areas. Only community members can post information to that community. Furthermore, if the community administrator has set it to private, only community members can view the information posted to that community. A user who has even a slight interest in a particular spot within a spot area may or may not go into that spot area. However, the act of going to a spot consumes the user's time and effort. Therefore, users who go into a spot area are highly likely to have a certain level of interest in that particular spot. Thus, a community can be formed with users who have a certain level of interest in a particular subject.

Users may be able to join a community by following a prescribed procedure within the spot area. This procedure is called a check-in. Users can perform a check-in by operating user terminal 2. Check-in may also be a procedure for joining a community if the user is not already a member. Alternatively, check-in may be a procedure for notifying SNS server 1 that the user has entered a spot area associated with a specific community or visited a specific spot within that area. Furthermore, joining a community may require scanning community-specific code information using the camera on user terminal 2. Examples of code information include one-dimensional barcodes and two-dimensional codes. The code information may be printed on paper, for example, and posted at the spot. Additionally, approval from the community administrator may be required to join a community.

SNS server 1 may perform processing related to stamp cards available in connection with the community. For example, SNS server 1 may perform processing such as creating stamp cards, issuing created stamp cards, and stamping stamp cards. Creating a stamp card may mean, for example, defining the specifications of the stamp card and making it available for issuance. A stamp card may have multiple stamp fields. Each stamp field is an area where a stamp can be placed. The number of stamp fields on a single stamp card is called the number of stamp fields. The number of stamp fields may be predetermined and common to all stamp cards, or it 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 members of the community. Stamping a stamp card is also called granting a stamp. Also, when a user has their stamp card stamped, it is called acquiring a stamp. Users may be able to acquire stamps by going into any of the designated spot areas set for the community. When a user collects a predetermined number of stamps, they can receive some kind of reward. For example, a reward may be given to the user when all stamp spaces are filled. Alternatively, the stamp card creator may be able to set multiple numbers of stamps required to grant a reward to the user. The reward may be provided, for example, by the stamp card creator, by the operator of at least one of two or more designated communities, or by a party involved with a specific spot within the spot area associated with those communities. A party involved with a spot may be, for example, a business that sells the items traded at that spot. For example, suppose a community about a certain ramen chain is created by the headquarters of that ramen chain. In this case, the headquarters can set a spot area to include each store of the ramen chain. Examples of rewards for the stamp card of this ramen chain community include free toppings, free ramen, or discounted ramen.

Each user terminal 2 may be a portable terminal device used by users of the Spot SNS. Users may be individuals, businesses, corporations, or other organizations or groups. Users may be able to create communities, check in, join communities, post information to communities, and view information posted to communities by operating the user terminal 2. Furthermore, the user terminal 2 may display stamp cards or show the status of reward acquisition and usage based on user operations. Examples of user terminals 2 include smartphones, tablet computers, mobile phones, and PDAs (Personal Digital Assistants). Each user terminal 2 may store an application program for the communication system S (hereinafter referred to as a dedicated app). Users can use the Spot SNS by sending and receiving information between the user terminal 2 and the SNS server 1 according to the dedicated app.

Furthermore, each user terminal 2 may have a function to acquire location information indicating its own location. For example, the latitude and longitude may be calculated as location information using a satellite positioning system such as GPS (Global Positioning System). Alternatively, for example, location information using a base station may be provided to the user terminal 2 by a mobile communications carrier. In this case, the user terminal 2 acquires the latitude and longitude, address, or postal code corresponding to the location of a base station near the user terminal 2 as location information. Alternatively, for example, location information may be obtainable using a wireless LAN (Local Area Network). For example, when the user terminal 2 receives wireless signals from multiple access points, it measures the signal strength from each access point and acquires the SSID of each access point. The user terminal 2 transmits information including the signal strength and SSID to a predetermined server device (not shown). This server device stores the latitude and longitude of the access point locations, etc. The server device uses the information received from the user terminal 2 to calculate the location of the user terminal 2, for example, by triangulation.

[1-2. A stamp card that can be used in multiple communities]
Next, we will explain stamp cards in spot-based social networking services (SNS) with reference to Figures 2 and 3. Typically, the operator of a community creates a stamp card that can be used within that community. Therefore, members of that community who become owners of that stamp card can earn stamps by visiting spot locations related to that community.

Furthermore, it may be possible to create a stamp card that can be used in common by two or more communities. In this case, the creator of the stamp card can specify two or more communities to share the card with. The creator of the stamp card may be, for example, the administrator of one of those communities, or may be different from the administrator of any of those communities. In this case, the holder of the stamp card can earn stamps by visiting locations associated with any of those two or more communities.

Figure 2 illustrates an example of a common stamp card concept shared by two or more communities. As shown in Figure 2, assume that at least three communities exist: 201, 202, and 203. Community 201 is a community related to a hotel in City X. A spot area 301 is associated with Community 201. Spot area 301 includes the hotel's location. Community 202 is a community related to a ramen chain with multiple locations in City X. Community 202 is associated with spot areas 302, 303, and 304. Each of these spot areas includes the location of a store. Community 203 is a community related to a soba noodle restaurant in City X. Community 203 is associated with spot area 305. Spot area 305 includes the location of the soba noodle restaurant. User U1, as shown in Figure 2, represents City X as a local government. City X creates a stamp card 101, specifying communities 201, 202, and 203. The stamp card 101 is associated with these communities.

Figure 3 shows an example of how stamps are applied to a stamp card. As shown in Figure 3, user U2 is not yet a member of community 201, but is a member of community 202. Also, user U2 does not yet possess a stamp card 101. User U2 possesses user terminal 2-2 as user terminal 2. When user U2 is located outside the area of any spot area, user U2 cannot check in to any community (step S1). Subsequently, user U2 stays at hotel 401 located within spot area 301. Spot area 301 is associated with community 201. Here, user U2 operates user terminal 2-2 to check in to community 201 (step S2). In response to the check-in, SNS server 1 adds user U2 to community 201 (step S3). Furthermore, SNS server 1 issues a stamp card 101-1, a copy of stamp card 101, to user U2 and stamps it with one stamp (step S4). User terminal 2-2 displays information about the stamp card. For example, user terminal 2-2 may display an image of the stamp card, showing each of the multiple stamp fields on the stamp card in a way that allows identification of whether or not a stamp has been placed in that field. Afterward, user U2 goes to ramen shop 402 within spot area 302. Spot area 302 is associated with community 202. Here, user U2 checks in to community 202 (step S5). In response to this check-in, SNS server 1 stamps stamp card 101-1 with another stamp (step S6). This brings the total number of stamps to two.

[1-3. SNS Server Configuration]
Next, the configuration of the SNS server 1 will be described with reference to Figures 4 and 5. Figure 4 is a block diagram showing an example of the schematic configuration of the SNS server 1 according to this embodiment. As shown in Figure 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.

The system control unit 11 is composed of a CPU (Central Processing Unit) 11a, ROM (Read Only Memory) 11b, RAM (Random Access Memory) 11c, and the like.

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

The storage unit 14 is composed of, for example, a hard disk drive. This storage unit 14 stores databases such as the Member DB 14a, Community DB 14b, Area DB 14c, Check-in History DB 14d, Community Member DB 14e, Stamp Card DB 14f, Stamp Card Association DB 14g, Issued Card DB 14h, Stamp History DB 14i, and Benefits DB 14j. "DB" is an abbreviation for Database.

Figure 5 shows an example of the contents stored in the database. Member DB 14a may store member information for each user of the Spot SNS. For example, Member DB 14a may store member information such as User ID, nickname, name, gender, date of birth, telephone number, email address, and address, all linked together. The User ID is identification information that identifies the user.

Community DB 14b may store community information for each community. For example, Community DB 14b may store community information such as Community ID, Community Name, Category Information, Community Administrator ID, and Area ID, all of which are associated with each other. The Community ID is identification information that identifies the community. Category Information indicates the category to which the community belongs. Examples of categories include anime/manga, tourism, gourmet food, local areas, and outdoor activities. The Community Administrator ID is the user ID of the user who created the community. The Area ID is identification information that identifies the spot area associated with the community. If a community administrator has set up multiple spot areas, multiple Area IDs may be stored in Community DB 14b for that community.

Area DB14c stores area information representing each spot area set by each community operator. For example, Area DB14c stores area IDs and area information in association. Examples of area shapes include circles, ellipses, squares, rectangles, and rhombuses. For example, if a designated area is circular, the area information may include the latitude and longitude of the center and its 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 the address, facility name, building name, or landmark name of the center. If the area shape is other than circular, the area information may include information corresponding to that shape. Alternatively, the area information may include the latitude and longitude of each line segment constituting the area's boundary. Alternatively, the area information may include the name of the region or area.

The check-in history DB14d may store a history of each user's check-ins to communities. For example, each time a check-in is made, the check-in history DB14d may store a check-in log containing the check-in log number, check-in date and time, community ID, area ID, and user ID, all 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 the check-in was made. The community ID indicates the community to which the check-in was made. The area ID indicates the spot area to which the check-in was made. The user ID indicates the user who made the check-in.

The community member DB 14e may store information indicating which users belong as members to which communities. For example, the community member DB 14e may store community IDs and user IDs associated with each other for each combination of a community and its members. The user ID indicates a user who is a member of the community indicated by the community ID. Only users whose user IDs are stored in the community member DB 14e can post information to a community. For example, in a dedicated application, a user performs an operation to display the screen of one of the communities. 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 that community. If a matching combination is found, the SNS server 1 may display an input field on the screen of that community for the user to enter the information to be posted. The SNS server 1 may associate the entered information with the community ID of that community and store it in a predetermined database as posted information. SNS server 1 may send posting information associated with the community ID of that community in response to a request from a user terminal 2 of a member of that community. If no matching combination exists, SNS server 1 does not need to display the input field on the community's screen.

The stamp card database 14f may store stamp card information for each stamp card created. For example, the stamp card database 14f may store stamp card information such as stamp card ID, stamp card name, stamp card creator ID, description, and reward setting information, all in a related manner. The stamp card ID is identification information that identifies the stamp card. The stamp card creator ID indicates the user who created the stamp card. The reward setting information indicates information about the reward. For example, the reward setting information may include the number of reward stamps, the reward name, the start date of use, the end date of use, the end date setting flag, and the usage conditions. The number of reward stamps indicates the number of stamps required to obtain the reward. The reward name indicates the name of the reward in a way that identifies the content of the reward that can be obtained. The start date of use indicates the start date of the period during which the reward can be used. The end date of use indicates the end date of the period during which the reward can be used. The end date setting flag indicates whether the setting of the end date of use is valid or not. The usage conditions indicate the conditions for using the reward. If multiple rewards are available for a single issued stamp card, multiple special selection settings may be stored in the stamp card DB14f. In this case, the number of reward stamps will differ for each of these rewards.

The stamp card association database 14g may store stamp card association information for each stamp card and community combination, including information about communities that can be used to encourage visits to specific locations. For example, the stamp card association database 14g may store the stamp card ID of a stamp card and the community ID of that community, associated with each other, as stamp card association information.

The Issued Cards DB14h may store issued card information for stamp cards issued to users, categorized by stamp card and the user to whom it was issued. For example, the Issued Cards DB14h may store the following information as issued card information, associated with each other: issued card number, issue date, stamp card ID, user ID, number of cards issued, and number of stamps. The issued card number is a number that identifies the issuance of the stamp card. The issue date indicates the date the stamp card was issued to that 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 cards issued indicates how many of that stamp card were issued to that user. The number of stamps indicates the number of stamps on that stamp card. When the number of stamps on a single stamp card reaches the number of stamp card slots, a new stamp card may be automatically issued. In this case, the number of cards issued increases by 1, and the number of stamps is reset to zero.

The stamp history DB14i may store a history of stamps applied to stamp cards. For example, each time a stamp is applied, the stamp history DB14i may store a stamp log containing the stamp log number, stamp date and time, stamp card ID, community ID, area ID, and user ID, all 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 the stamp was applied. The stamp card ID indicates the stamp card to which the stamp was applied. The community ID indicates the community to which the user checked in, prior to the stamp being applied to the stamp card. The area ID indicates the spot area to which the user checked in. The user ID indicates the user who checked in.

The rewards database 14j may store reward information related to rewards obtainable through the use of stamp cards, for each combination of issued stamp cards and the rewards set on those stamp cards. For example, the rewards database 14j may store reward information such as the issued card number, stamp card ID, user ID, number of cards issued, number of reward stamps, and reward status, all associated with each other. The issued card number identifies the issuance of a stamp card with a reward set on it. 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 cards issued indicates which stamp card with that reward has been issued to that user. The number of reward stamps indicates the number of stamps required for the user to obtain that reward. The reward status indicates the status of the reward. The reward status may be set to, for example, "Not obtained," "Available," or "Used." "Not obtained" indicates that the user has not yet obtained the reward. "Available" indicates that the user has obtained the reward but has not yet used it. "Used" indicates that the user has already used the benefit.

The storage unit 14 also stores various programs, including the operating system, DBMS (Database Management System), and server programs. The server program is a program that instructs the system control unit 11 to execute various processes related to the Spot SNS. The server program may, for example, be acquired from another device via the Internet network, or it may be recorded on a recording medium such as magnetic tape, optical disk, or memory card and read via a drive device.

The communication unit 15 is composed of, for example, a network interface card. The communication unit 15 connects to the user terminal 2, etc., via the network NW and controls the communication status with the connected device.

[1-4. Functional Overview of the System Control Unit of the SNS Server]
Next, the functional overview of the system control unit 11 of the SNS server 1 will be explained with reference to Figure 6. Figure 6 is a diagram showing an example of the functional blocks 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 membership unit 1105, a stamp unit 1106, and a reward granting unit 1107, etc., as shown in Figure 6, by the CPU 11a reading and executing various program codes included in the server program.

The community ID acquisition unit 1101 may acquire two or more community IDs that identify two or more communities specified by the stamp card creator who creates the stamp card, from among multiple different communities. The community ID acquisition unit 1101 may acquire community IDs from, for example, the stamp card creator's user terminal 2. For example, the stamp card creator selects to create a stamp card in a dedicated application. In response to this selection, the user terminal 2 may display a stamp card creation screen for entering various information for the stamp card. The stamp card creation screen may include user interface elements for selecting a community. For example, if the 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 communities. In the search window, the user can specify search conditions for communities. Examples of search conditions include community name, category, address, and communities created by the stamp card creator. The SNS server 1 may search for communities that satisfy the specified search conditions using, for example, the community DB 14b, area DB 14c, etc. The user terminal 2 may display a list of the searched communities in the search window. The user selects a community to add from the list. Alternatively, user terminal 2 may display a map and show markers on the map indicating spots associated with the community. The user may then select a spot for the community they wish to add from the map. Once a community is selected, user terminal 2 may add and display the community name of the selected community on the stamp card creation screen. This procedure is repeated if the user selects two or more communities. Note that the user may select only one community. For example, the user may select a community they have created. Once the user has completed entering the necessary information on the stamp card creation screen, user terminal 2 may send the community IDs of each of the two or more selected communities, along with any other information entered, to the SNS server 1. In this way, the community ID acquisition unit 1101 may acquire the community IDs.

The two or more communities designated by the stamp card creator may be two or more communities where information related to two or more different businesses that sell the transaction items is provided within each community. Each of these businesses may be a business that sells the transaction items at a facility associated with that business. A facility associated with a business may be, for example, a facility owned, managed, leased, or used by that business. Examples of such facilities include stores and offices. The spot area indicated by the area information stored in the storage unit 14, associated with the community ID of each of these communities, may include the location of a facility related to a business associated with that community. The stamp card creator can designate two or more communities as communities associated with different businesses. By visiting a facility associated with any of these two or more businesses, the user can get a stamp on their stamp card. Therefore, a common stamp card can be created for two or more businesses separated by a community, encouraging users to visit facilities.

The stamp card creation unit 1102 may store a stamp card ID in the storage unit 14 that identifies the stamp card to be created, associated with two or more community IDs obtained 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 the 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 database 14f. The stamp card creation unit 1102 may associate each acquired community ID with the generated stamp card ID and store this information in the stamp card association database 14g.

The two or more spot areas indicated by the two or more area information stored in the memory unit 14 for each of the two or more communities designated by the stamp card creator may include locations that are different from each other. For two or more spot areas to include locations that are different from each other means that they do not overlap with each other. For example, two or more spot areas being different from each other means that they do not overlap at all, or that only a portion of their areas overlap. Since the spots associated with each community are often different from each other, their spot areas are often at least partially different from each other. The stamp card creator can designate two or more communities that may each be associated with different locations.

The location information acquisition unit 1103 may acquire location information of the portable user terminal 2. The location information acquisition unit 1103 may, for example, acquire location information from the user terminal 2. For example, the user terminal 2 may periodically acquire its location information in the background using GPS or the like, according to a dedicated application, and transmit that location information to the SNS server 1. Alternatively, the user terminal 2 may be able to select a community spot that the user wants to check into, using the dedicated application. For example, the user terminal 2 may display a map and display markers 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 the spot area corresponding to that spot, and may also display the spot area and a marker indicating the current location of the user terminal 2 on the map. While this map is displayed, the user terminal 2 may periodically acquire location information and transmit it to the SNS server 1. The user terminal 2 may also transmit the user ID of the user terminal 2 to the SNS server 1 along with the location information. Thus, the location information acquisition unit 1103 may acquire location information.

The check-in determination unit 1104 may determine whether a 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 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, if the user is attempting to check in to the same spot area where they previously checked in, the check-in determination unit 1104 may allow check-ins only once per predetermined period (for example, within 24 hours from a predetermined time). This suppresses excessive stamp acquisition due to repeated check-ins in the same spot area.

If 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 a spot area indicated by any of the area information stored in the storage unit 14, the joining unit 1105 may execute a process to add the user of the user terminal 2 to the community identified by the community ID associated with that area information. For example, the joining unit 1105 may associate the community ID of that community with the user ID of that user and store it in the community member DB 14e. The joining unit 1105 may add the user to the community only if the user has performed a check-in operation.

The stamp unit 1106 may, for each of the multiple communities, perform a stamping process to stamp the stamp card for the user of the user terminal 2 if the check-in determination unit 1104 determines that the location of the user terminal 2, indicated by the location information obtained by the location information acquisition unit 1103, is included in the area indicated by the area information associated with any of the two or more community IDs obtained by the community ID acquisition unit 1101, among the area information stored in the storage unit 14 which stores area information indicating a spot area associated with that community in association with the community ID of that community. The stamp unit 1106 may also perform the stamping process even if the area information indicating the spot area including the user terminal 2 is associated with any of the two or more community IDs obtained. The community DB 14b stores community IDs and area IDs in association. The area DB 14c stores area IDs and area information in association. Therefore, community IDs and area information are associated via area IDs. As part of the stamping process, the stamping unit 1106 may, for example, increase the number of stamps included in the issued card information stored in the issued card DB 14h. The identification of this issued card information may be performed as described below. For example, the stamping unit 1106 may obtain a community ID associated with area information indicating a spot area including the user terminal 2. The stamping unit 1106 may obtain a stamp card ID associated with this community ID from the stamp card DB 14f. The stamping unit 1106 may search the issued card DB 14h for issued card information including this stamp card ID and the user ID of the user of the user terminal 2. If no matching issued card information is found, the stamping unit 1106 may generate new issued card information and store it in the issued card DB 14h. When storing new issued card information, the stamping unit 1106 may generate new reward information and store it in the reward DB 14j. For example, the stamp unit 1106 may generate reward information for each reward based on the issued card information and the stamp card information of that stamp card stored in the stamp card DB 14f. In this case, the stamp card DB 14f may set the reward status of the reward information to "not yet acquired".

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

The reward granting unit 1107 may grant a reward to the user when the number of stamps stamped by the stamping unit 1106 reaches a preset number of reward stamps. For example, the reward granting unit 1107 may change the reward status stored in the reward DB 14j, associated with the stamped stamp card's issued card number, the number of issued cards, the user's user ID, and the number of reward stamps, to "Available."

[1-5. Operation of the communication system]
Next, the operation of the communication system S will be explained with reference to Figures 7 to 9. The system control unit 11 executes the processing of the SNS server 1 shown in Figure 7, as well as the processing shown in Figures 8 and 9, according to the program code included in the server program.

Figure 7 is a sequence diagram showing an example of the operation of the communication system S according to this embodiment. When user U1, as the stamp creator, selects to create a stamp card, user terminal 2-1 displays the stamp card creation screen. Then, as shown in Figure 7, user U1 inputs information about the stamp card on the stamp card creation screen (step S101). For example, the stamp card name, description, and reward setting information are entered. Furthermore, user U1 specifies multiple communities (step S102). Upon completion of the input of the necessary information, user terminal 2-1 transmits the entered stamp card information, a list of community IDs for the specified communities, and user U1's user ID to the SNS server 1 (step S103).

The stamp card creation unit 1102 of the SNS server 1, upon receiving information from 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 entered by user U1, and user U1's user ID. The stamp card creation unit 1102 may store the stamp card information in the stamp card DB 14f. Furthermore, the stamp card creation unit 1102 may associate each community ID included in the community ID list with the generated stamp card ID and store them in the stamp card association DB 14g. In this way, a new stamp card is created.

Subsequently, in response to user U2's actions as a user checking into a community, user terminal 2-2 displays a map and a spot marker. User U2 selects a spot from the map, thereby selecting the community associated with the spot area containing that spot (step S106). User terminal 2-2 sends the community ID of the selected community, the area ID of the spot area containing the selected spot, and user U2's user ID to SNS server 1 (step S107). User terminal 2-2 also displays a magnified map of the spot area and a check-in button. The check-in button is for checking into the selected community. At this point, user terminal 2-2 disables the check-in button; that is, user U2 cannot check in at this stage. Then, user terminal 2-2 periodically generates its own location information and sends it to SNS server 1 (steps S107, S108). SNS server 1 performs a check-in eligibility determination process each time it receives location information (steps S109, S111).

Figure 8 is a flowchart showing an example of the check-in/failure determination process by the system control unit 11 of the SNS server 1 according to this embodiment. As shown in Figure 8, the check-in determination unit 1104 obtains 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 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/failure determination process ends.

If the location of 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 check-in logs that include the user ID of user U2 and the area ID received from user terminal 2-2, and that contain a check-in date and time indicating a time after the most recent predetermined time (e.g., 7:00) (step S203). Based on the search results, the check-in determination unit 1104 determines whether or not a matching check-in log exists (step S204). If a matching check-in log exists (step S204: YES), the check-in eligibility determination process ends. If no matching check-in log exists (step S204: NO), the check-in determination unit 1104 sends a check-in possible notification to user terminal 2-2 (step S205), and the check-in eligibility determination process ends.

Returning to Figure 7, we assume that, following the check-in availability determination process in step S111, the check-in determination unit 1104 sent a check-in availability notification to the user terminal 2-2 (step S112). Upon receiving the check-in availability notification, the user terminal 2-2 enables the operation of the check-in button (step S113). Next, user U2 performs the operation of pressing the check-in button (step S114). In response to this operation, user terminal 2-2 sends a check-in request to the SNS server 1 (step S115). The check-in request may include the community ID and area ID corresponding to the community and spot selected by user U2, as well as user U2's user ID.

The check-in determination unit 1104 of the SNS server 1, upon receiving a 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 contained in the check-in request, as well as the current date and time as the check-in date and time. Next, the joining unit 1105 executes community joining control processing (step S117). For example, the joining unit 1105 may determine whether the same combination of community ID and user ID as the one 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 that community ID with its user ID and store it in the community member DB 14e. Next, the stamping unit 1106 executes stamping control processing (step S118).

Figure 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 Figure 9, the stamp unit 1106 searches the stamp card association DB 14g for the stamp card ID associated with the community ID of the community checked in by user U2 (step S301). Based on the search results, the stamp unit 1106 determines whether or not a matching stamp card ID exists (step S302). If no matching stamp card is found (step S302: NO), the stamp card control processing terminates.

If a matching stamp card ID exists (Step S302: YES), the stamp unit 1106 retrieves stamp card information, including the retrieved 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 retrieved stamp card ID and the user ID of the user U2 who checked in (Step S303). As a result of the search, the stamp unit 1106 determines whether or not there is matching issued card information (Step S304). If there is no matching 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 that includes the issued card number, the retrieved stamp card ID, the user ID of user U2, the number of issued cards (1), and the number of stamps (zero). The stamp unit 1106 may store the issued card information in the issued card database 14h. The stamp unit 1106 may also obtain the number of reward stamps from the reward setting information included in the acquired stamp card information. For each acquired number of reward stamps, the stamp unit 1106 may generate reward information including the same combination as the issued card number, stamp card ID, user ID, and number of issued cards included in the issued card information, the number of reward stamps, and a reward status indicating "unused." The stamp unit 1106 may store the reward information in the reward database 14j.

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 retrieved stamp card ID, the community ID and area ID received from user terminal 2-2, the user ID of user U2, and the stamp date and time indicating the current date and time.

Next, the stamp unit 1106 determines whether the number of stamps matches any of the reward stamp counts included in the reward setting information of the acquired stamp card information (step S308). If the number of stamps matches any of the reward stamp counts (step S308: YES), the reward granting unit 1107 changes the reward status stored in the reward DB 14j to "Available" in association with the same combination as the reward stamp count that matches the number of stamps, and the issued card number, user ID, and number of issued cards included in the retrieved issued card information or generated issued card information (step S309).

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

After step S313, or if the number of stamps does not match the number of stamp fields (step S310: NO), the stamp unit 1106 generates stamp card display information and transmits this information to the user terminal 2-2 (step S314), thereby terminating the stamp control process. The stamp card display information is the information necessary to display the stamp card on the user terminal 2-2. For example, the stamp card display information may include the stamp card name and the number of stamps.

Returning to Figure 7, we assume that the stamp control process has transmitted stamp card display information from the stamp unit 1106 to the user terminal 2-2 (step S119). The user terminal 2-2 displays the 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 with multiple stamp fields, as well as the stamp card name. The user terminal 2-2 may also display images representing stamps in each of the stamp fields on the stamp card, corresponding to the number of stamps.

As described above, according to this embodiment, the SNS server 1 may acquire two or more community IDs that identify each of the two or more communities specified by the stamp card creator. The SNS server 1 may also store stamp card IDs in the stamp card DB 14f that identify the stamp cards to be created, associated with the two or more community IDs. Furthermore, the SNS server 1 may acquire the location information of the user terminal 2. Additionally, if the location indicated by the location information is included in a spot area indicated by the area information associated with any of the two or more community IDs associated with the stamp card ID, the SNS server 1 may perform the stamping process for the user of the user terminal 2. In this case, regardless of which of the two or more communities specified by the stamp card creator the community associated with the spot area visited by the user belongs to, the user can have their stamp card stamped. Therefore, the stamp card creator can specify two or more communities and create a stamp card that can be commonly used at locations related to those specified communities.

Here, if the SNS server 1 finds that a location indicated by location information is included in a spot area indicated by any of the area information stored in the area DB 14c, it may add the user to the community identified by the community ID associated with that area information. In this case, the user can join the community by going to the spot area associated with that community. It is assumed that users go to a particular spot area because they have a certain level of interest in the things within that area. Therefore, the community can be formed with users who have a certain level of interest in the subjects of information exchange within that community.

Furthermore, SNS server 1 may perform the stamping process on the condition that the user is a member of at least one of the two or more communities specified by the stamp card creator. In this case, the user can be prompted to join a community.

[2. Second Embodiment]
Next, a second embodiment will be described. The second embodiment may be identical to the first embodiment, except for the points described below. In this embodiment, the SNS server 1 is configured to allow users 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 gets stamps on their stamp card. Even if a user goes to a spot where they have already been stamped, they cannot get another stamp. The stamp rally in this embodiment may be an activity in which a user visits spots associated with different communities and gets stamps on their stamp card. Even if a user goes to a spot associated with a community where they have already been stamped, they cannot get another stamp. In this case, even if the spot the user visits after getting a stamp is different from the spot where they were previously stamped, the user cannot get another stamp.

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

Figure 11 shows an example of the contents stored in the stamp card DB 14f, the stamp card association DB 14g, and the issued card rally DB 14k. The difference between the stamp card DB 14f shown in Figure 11 and the stamp card DB 14f shown in Figure 5 is that the stamp card DB 14f in Figure 11 also stores the card type. The card type indicates the type of stamp card. The card type may be set to, for example, "stamp rally" or "normal." "Stamp rally" indicates that the stamp card is for a stamp rally. "Normal" indicates that the stamp card is not for a stamp rally. The stamp card creator may be able to select the card type when creating the stamp card.

The difference between the stamp card association DB 14g shown in Figure 5 and the stamp card association DB 14g shown in Figure 11 is that the stamp card association DB 14g shown in Figure 11 also stores stamp field numbers. The stamp field number indicates the number of the stamp field where a stamp is placed for the community identified by the community ID.

Figure 12 shows an example of a stamp card. The stamp card 102 shown in Figure 12 is a card for a stamp rally. The stamp card 102 has 10 stamp spaces. Each stamp space is assigned one of the stamp space numbers from 1 to 10. Each stamp space is also associated with a community. For example, from stamp space 1 to stamp space 10, communities 201, 202, 203, 204, 205, 206, 207, 208, 209, and 210 are associated in order. For example, the communities may be associated with the stamp spaces in the order specified by the stamp card creator when the stamp card was created. Alternatively, the stamp card creator may specify the assignment of communities to the stamp spaces. The number of stamp spaces may be predetermined, for example. Alternatively, the number of communities specified by the stamp card creator may be determined as the number of stamp spaces.

Returning to Figure 11, the issued card rally DB 14k may store issued card rally information related to stamp rallies, among the information about stamp cards issued to users, for each combination of a stamp card for a stamp rally, the user to whom the stamp card was issued, and the stamp field. For example, the issued card rally DB 14k may store either information indicating that the stamp has not been applied or information indicating that the stamp has been applied for each of two or more communities specified by the stamp card creator, associated with the stamp card ID of the created stamp card and the user ID of the user who possesses that stamp card. Specifically, the issued card rally DB 14k may store issued card rally information such as the issued card number, stamp card ID, user ID, community ID, stamp field number, and stamp status, associated with each other. The issued card number identifies the issuance of a stamp card containing a specific stamp field. The stamp card ID indicates the issued stamp card. The user ID indicates the user to whom the stamp card was issued. The community ID indicates the community associated with that stamp field. The stamp field number indicates the stamp field. The stamp status indicates whether a stamp has been applied to that field. The stamp status may be set to either "Not Acquired" or "Acquired." "Not Acquired" indicates that no stamp has been applied. "Acquired" indicates that a stamp has been applied.

[2-2. Functional Overview of the SNS Server System Control Unit]
Next, the functional overview of the system control unit 11 of the SNS server 1 will be explained with reference to Figure 13. In this embodiment, the stamp unit 1106 may, as part of the stamp processing, change the stamp status to "acquired" for a community indicated by a community ID associated with area information indicating a spot area including the location of the user terminal 2, which is indicated by location information acquired by the location information acquisition unit 1103, among two or more communities specified by the stamp card creator, in association with the stamp card ID and the user ID of the user of the user terminal 2. That is, a stamp is placed on the stamp card, and the number of stamps acquired by the user increases. The stamp status for a community may be the stamp status associated with the stamp column number assigned to that community. On the other hand, the stamp unit 1106 does not need to do anything in particular if the stamp status indicating "acquired" is stored in the issued card rally DB 14k. That is, no stamp is placed on the stamp card, and the number of stamps acquired by the user does not increase. It is stipulated that when the number of stamps indicating "acquired" stored in the issued card rally DB14k, associated with a stamp card ID of a certain stamp card and a user ID of a certain user, reaches the number of reward stamps, the user will be granted the reward.

Figure 13 shows an example of how stamps are applied to a stamp card. User U2, shown in Figure 13, does not yet possess the stamp card 102. User U2, who possesses the user terminal 2-2, goes to the ramen shop 402 located in the spot area 302. The spot area 302 is associated with community 202. Here, user U2 operates the user terminal 2-2 to check in to community 202 (step S11). In response to the check-in, the SNS server 1 issues a stamp card 102-1 to user U2 as a copy of the stamp card 102. As shown in Figure 12, community 202 is assigned to the second stamp field. None of the stamp fields on the newly issued stamp card 102-1 have been stamped. Therefore, the SNS server 1 stamps the second stamp field on the stamp card 102-1 (step S12). The next day, user U2 goes to the ramen shop 403 located in the spot area 303. Spot area 303 is also associated with community 202. Here, user U2 operates user terminal 2-2 to check in to community 202 (step S13). The second stamp field on stamp card 102-1 is already stamped. Therefore, SNS server 1 does not stamp stamp card 102-1 (step S14). Afterward, user U2 goes to bakery 406 located within spot area 306. Let's assume spot area 306 is associated with community 209. Community 209 is associated with bakery 406. As shown in Figure 12, community 209 is assigned to the ninth stamp field. Here, user U2 operates user terminal 2-2 to check in to community 202 (step S15). The ninth stamp field on stamp card 102-1 is not stamped. Therefore, SNS server 1 stamps the ninth stamp field (step S16).

[2-3. Operation of the Communication System]
Next, the operation of the communication system S will be described with reference to Figures 14 and 15. In this embodiment as well, as shown in Figure 7, steps S101 to S117 may be executed first. Here, in step S101, the stamp card creator selects the card type. In step S105, if the card type is "stamp rally", the stamp card creation unit 1102 generates stamp card association information for each community specified by the stamp card creator and adds stamp field numbers to the stamp card association information. For example, the stamp card creator may assign the stamp field 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, the stamp control process is executed (step S118).

Figures 14 and 15 are flowcharts illustrating an example of stamp control processing by the system control unit 11 of the SNS server 1 according to this embodiment. In Figure 14, the same reference numerals are used for processes identical to those in Figure 9.

As shown in Figure 14, steps S301 and S302 are executed first. If the search in step S301 does not find a matching stamp card ID (step S302: NO), the stamp card control process terminates. If a matching stamp card ID is found (step S302: YES), the stamp unit 1106 retrieves stamp card information, including the retrieved stamp card ID, from the stamp card DB 14f. Next, the stamp unit 1106 determines whether the card type included in the retrieved 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 implementation.

If the card type is "stamp rally" (step S321: YES), as shown in Figure 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 user U2 who checked in (step S401). As a result of the search, the stamp unit 1106 determines whether or not there is any 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 reward information and stores it 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 the stamp card association DB 14g for all stamp card association information including the searched stamp card ID. The stamp unit 1106 may obtain a combination of community ID and stamp field number from the retrieved stamp card association information. For each obtained combination, the stamp unit 1106 may generate issued card rally information 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 generated issued card rally information in the issued card rally DB 14k.

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 the stamp status associated with the combination of the retrieved stamp card ID, user U2's user ID, and the community ID received from user terminal 2-2 (step S405). Next, the stamp unit 1106 determines whether the retrieved 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).

If there is corresponding issued card information (step S304: YES), after step S306 or after step S407, steps S306 to S313 are executed in the same manner as in the first embodiment, as shown in Figure 14. After step S313, the stamp unit 1106 determines 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 the status of each stamp stored in the issued card rally DB 14k to "not acquired" in association with the combination of the retrieved stamp card ID and the user ID of user U2 (step S323). After step S323, if the number of stamps does not match the number of stamp fields (step S310: NO), or if the card type is not "stamp rally" (step S322: NO), the stamp unit 1106 sends 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 stamp field number and stamp status for each stamp field.

Once the stamp control process is complete, steps S119 and S120 are executed as shown in Figure 7. In step S120, the user terminal 2-2 may determine the stamp status associated with the number of each stamp field. The user terminal 2-2 may display the stamp image in the stamp fields where the stamp status is "acquired".

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

[3. Third Embodiment]
Next, a 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 user's stamp card is stamped in accordance with the user's location in any of the spot areas, the user is awarded points from a predetermined points program. The points program may be a service that awards users points equivalent to a predetermined percentage of the purchase price of items traded at a facility or online, and also allows them to use the points to purchase items traded. Each user of the spot SNS may be able to use the points program. The cost of awarding points to users is borne by at least one of the creator of the stamp card and the operator of the community in the spot area. Points may be awarded to users for all stamp cards. Alternatively, each stamp card creator may be able to choose whether or not to award points. For the sake of explanation, it will be assumed from here on that points are awarded to users for all stamp cards.

[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 Figure 16. Figure 16 is a diagram showing an example of the general configuration of the communication system S according to this embodiment. In Figure 16, the same reference numerals are used for elements that are the same as in Figure 1. The difference between Figure 16 and Figure 1 is that a point management server 3 has been added in Figure 16. The point management server 3 is connected to the network NW.

The point management server 3 may be a server device that manages the points of each user in the points program. For example, the point management server 3 may store a point database 31. The point database 31 may store information about the points each user possesses. The number of points a user currently possesses is called the number of available points. The point database 31 may store, for example, a user ID and the number of available points associated with each user. The point management server 3 may provide an API (Application Programming Interface) to the SNS server 1 for accessing the point database 31.

[3-2. SNS Server Configuration]
Next, the configuration of the SNS server 1 will be described with reference to Figures 17 and 18. Figure 17 is a block diagram showing an example of the schematic configuration of the SNS server 1 according to this embodiment. In Figure 17, the same elements as in Figure 4 are denoted by the same reference numerals. The difference between Figure 17 and Figure 4 is that in Figure 17, the storage unit 14 further stores the cost burden DB 14l and the fee DB 14m.

Figure 18 shows an example of the contents stored in the stamp card DB 14f, cost burden DB 14l, and fee DB 14m. The difference between the stamp card DB 14f shown in Figure 18 and the stamp card DB 14f shown in Figure 5 is that the stamp card DB 14f in Figure 18 also stores a budget amount. The budget amount indicates the budgeted amount for the costs borne by the stamp card creator to award points. This budget amount may, for example, represent an amount per predetermined period (e.g., per month). The budget amount may be set by the creator. It may be stipulated that the creator is basically required to set a budget amount when creating a stamp card. Even if the actual costs within the predetermined period exceed the budget amount, the SNS server 1 may still award points to users whose stamp cards are stamped. In this case, the amount of point charges, which are the actual costs borne by the stamp card creator, will exceed the budget amount.

The cost burden DB 14l may store cost burden information for each community where the operator has chosen to bear the cost of awarding points. The SNS server 1 may be configured to allow each community operator to choose whether or not to bear the cost of points. For example, this selection may be possible when creating a community, or it may be possible to change the selection after the community has been created. By bearing the cost of points, the operator can increase the number of users visiting spots associated with that community, as described later. The cost burden DB 14l may store cost burden information such as community ID, community operator ID, and budget amount, linked to each other. The community ID indicates the community for which cost burden has been selected. The community operator ID is the user ID of the operator of that community. The budget amount indicates the budgeted amount for the cost that the operator will bear to award points to users. This budget amount may, for example, indicate an amount per predetermined period. The budget amount may be set by the operator. Also, as described above, the actual amount of point fees borne by the community operator may exceed the budget amount.

The fee database 14m may store billing information for point accrual fees charged to stamp card creators or community operators, for each billing recipient. For example, fee database 14m may store fee information such as user ID, period, and billing amount, associated with each other. The user ID indicates the billing recipient, which is the stamp card creator or community operator. The period indicates the period during which point accrual fees are calculated. For example, the period may be a combination of fiscal year and month. The billing amount indicates the amount of point accrual fees to be charged. The initial value of the billing amount is 0 yen. After the period indicated by the period has elapsed, the billing recipient is charged a point accrual fee equivalent to the billing amount. For example, SNS server 1 or other server equipment may execute a process to settle the point accrual fee using the billing recipient's credit card.

[3-3. Functional Overview of the System Control Unit of the SNS Server]
Next, the functional overview of the system control unit 11 of the SNS server 1 will be described with reference to Figures 19 and 20. Figure 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 Figure 19, the same reference numerals are used for elements that are the same as in Figure 6. The difference between Figure 19 and Figure 6 is that in Figure 19, the system control unit 11 also functions as a community selection screen information transmission unit 1108, a point awarding unit 1109, and a billing amount update unit 1110.

The community selection screen information transmission unit 1108 may transmit community selection screen information to the user terminal 2 used by the stamp card creator. The community selection screen information may be information that displays the community selection screen on the user terminal 2. The community selection screen may be a screen for the stamp card creator to select communities where the stamp card can be used to encourage visits to spots. For example, the community ID acquisition unit 1101 may acquire the community IDs 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.

The community selection screen may display community display information for at least some of several distinct communities. This community display information may include, for example, the community name. The community selection screen may also accept an operation to select at least one of the communities indicated by the community display information. The community selection screen may also display search results for communities. For example, in response to a stamp card creator entering community search criteria, the SNS server 1 may search for communities that meet those criteria.

Each community display information may have a display priority assigned to it. The community selection screen may then display each community display information in a manner corresponding to its display priority. The display priority may also be a display priority. The higher the priority (or priority) of the community display information, the more favorably it may be displayed. For example, if the community display information is displayed from top to bottom on the community selection screen, the higher the priority of the community display information, the higher it may be displayed. For example, each position where community display information is displayed on the community selection screen may be assigned a priority. These positions may be assigned priorities sequentially from 1 downwards. The community selection screen information transmission unit 1108 may assign a higher priority to the community display information the higher its priority. The community selection screen information transmission unit 1108 may display each community display information at a position with the same priority as its priority. Alternatively, the higher the priority of the community display information, the more prominent it may be displayed. Examples of display manners include the size and color density of the community display information. Furthermore, the community selection screen information may include information that associates each community's community ID with its display priority or priority level. The user terminal 2 may then display each community's display information on the community selection screen in a manner corresponding to its priority level, based on this community selection screen information.

The community selection screen information transmission unit 1108 may generate community selection screen information by prioritizing the display of community information indicating communities that bear the cost of awarding points, at least among some communities, above the display priority of community information indicating communities that do not bear the cost of awarding points. This ensures that community information indicating communities that bear the cost is displayed with higher priority. Therefore, stamp card creators are more likely to select communities that bear the cost as communities where stamp cards can be used, compared to communities that do not. Since points are awarded to users when they visit a designated community's spot, visits to that community's spot are encouraged. Whether or not a community operator bears the cost can be determined, for example, by referring to the cost burden DB 14l.

The point awarding unit 1109 may, when the stamping process is performed by the stamping unit 1106, perform a point awarding process to award points to the user who possesses the stamp card to be stamped. For example, if the check-in determination unit 1104 determines that the location of the user terminal 2, indicated by the location information obtained by the location information acquisition unit 1103, is included in the area indicated by the area information associated with any of the two or more community IDs obtained by the community ID acquisition unit 1101, the point awarding unit 1109 may award points to the user of that user terminal 2. For example, a predetermined number of points may be awarded to the user. For the sake of explanation, let's assume that 10 points are awarded. The point awarding unit 1109 may, as a point awarding process, add a predetermined number to the number of available points for that user stored in the point DB 31. The point awarding unit 1109 may, for example, perform the point awarding process after the stamping process, or it may perform the point awarding process before the stamping process. Furthermore, the point awarding unit 1109 may award points, for example, at the time of check-in, or on the last day of the current month or the last day of the following month.

The billing amount update unit 1110 may update the billing amount for point granting stored in the fee DB 14m when the point granting process is executed by the point granting unit 1109, specifically updating at least one of the billing amounts for the stamp card creator and the billing amount for the community operator. For example, a unit price for point granting may be defined 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 number of points granted to the user. If the point fee is considered an expense for advertising and promotion of the community, the point granting unit price may be set higher than the amount equal to the number of points granted. The exchange rate between points and money may be predetermined. For example, 1 point may be equivalent to 1 yen. If 10 points are granted to the user for each stamp, the point granting unit price may be higher than 10 yen.

The billing amount update unit 1110 may add the entire point accrual cost to the billing amount to the stamp card creator if the community ID associated with the spot area including the location of the user terminal 2, as indicated by the location information acquired by the location information acquisition unit 1103, indicates a community different from the community that bears the cost of awarding points. Since the operator of that community has not chosen to bear the cost, the entire point accrual cost will be billed to the stamp card creator.

The billing amount update unit 1110 may add at least a portion of the point accrual unit price to the billing amount to the community operator if the community ID associated with the spot area including the location of the user terminal 2, as indicated by the location information acquired by the location information acquisition unit 1103, indicates a community that bears the cost of awarding points. 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 operator matches the point accrual unit price. Since the community operator has chosen to bear the cost, at least a portion of the point accrual unit price can be billed to that operator. For example, the billing amount update unit 1110 may add the entire point accrual unit price to the billing amount to the community operator. In this case, the stamp card creator does not bear the cost.

Figure 20 shows an example of how points are awarded to a user. For example, the operator of community 201, which is related to a hotel as shown in Figure 2, has chosen not to bear the cost of awarding points. On the other hand, the operator of community 202, which is related to a ramen chain, has chosen to bear the cost. As shown in Figure 20, user U2, who possesses user terminal 2-2, stays at hotel 401 within spot area 301 and checks into community 201 (step S21). In response to the check-in, SNS server 1 stamps user U2's stamp card 101-1 and awards points to user U2 (step S22). Since the operator of community 201 does not bear the cost, SNS server 1 adds the point awarding unit price to the amount billed to the creator of stamp card 101 (step S23). After that, user U2 goes to ramen shop 402 within spot area 302 and checks into community 202 (step S24). In response to this check-in, SNS server 1 stamps the stamp card 101-1 with another stamp and awards additional points to user U2 (step S25). Since the operator of community 202 bears the costs, SNS server 1 adds the point awarding cost to the amount billed to the operator (step S26).

[3-4. Operation of the communication system]
Next, the operation of the communication system S will be described with reference to Figures 21 to 23. Figure 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 Figure 21, the same reference numerals are used for the same processes as in Figure 7.

As shown in Figure 21, user U1 enters stamp card information on the stamp card creation screen (step S101). At this time, user U1 also enters the budget amount. Next, user U1 enters community search criteria (step S501). User terminal 2-1 sends a community search request including the entered search criteria to SNS server 1 (step S502). The community selection screen information transmission unit 1108 of SNS server 1, which received the community search request, searches for communities that meet the search criteria (step S503). Next, the community selection screen information transmission unit 1108 sets the priority of each found community (step S504). For example, the community selection screen information transmission unit 1108 gives a higher priority to communities that bear the cost of awarding points than to other communities. The community selection screen information transmission unit 1108 determines whether the operator of a community bears the cost by, for example, determining whether there is cost-bearing information including the community ID of the found community. Next, the community selection screen information transmission unit 1108 generates an HTML document of the search results screen as community display information display screen information (step S505). The search results screen is a screen that shows the search results for communities. For example, the community selection screen information transmission unit 1108 may generate community display information that includes the community ID and community name of each searched community. Alternatively, the community selection screen information transmission unit 1108 may generate the HTML document so that the community display information of the community with higher priority is displayed higher up on the search results screen. The community selection screen information transmission unit 1108 transmits the generated HTML document to the user terminal 2-1 (step S506). The user terminal 2-1, having received the HTML document, displays the search results screen based on this HTML document (step S507). User U1 selects at least one community display information from the search results screen (step S508). Note that steps S501 to S508 may be executed multiple times depending on the operation of user U1. After user U1 has finally selected two or more community display information, user terminal 2-1 sends the entered stamp card information, a list of community IDs corresponding to the selected community display information, and user U1's user ID to SNS server 1 (step S103). SNS server 1 generates a stamp card ID and stores the stamp card information and stamp card association information in storage unit 14 (steps S104, S105). Subsequently, steps S106 to S120 may be executed as shown in Figure 7.

Figure 22 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. In Figure 22, the same reference numerals are used for the same processes as in Figure 9. As shown in Figure 22, steps S301 to S307 are executed first, similar to the first embodiment. After step S307, the point granting unit 1109 adds 10 points to the number of available points stored in the point DB 31 associated with the user ID of the checked-in user U2, and updates the number of available points (step S341). Next, the billing amount update unit 1110 executes the billing amount update process (step S342).

Figure 23 is a flowchart illustrating an example of the billing amount update process performed by the system control unit 11 of the SNS server 1 according to this embodiment. As shown in Figure 23, the billing amount update unit 1110 determines whether or not cost burden information is stored in the cost burden DB 14l in association with the community ID of the community checked in by user U2 (step S601). If cost burden information is not stored (step S601: NO), the billing amount update unit 1110 adds the point accrual unit price to the billing amount of the stamp card creator and updates 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 checked in by user U2 from the stamp card association DB 14g. The billing amount update unit 1110 may also 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 accrual unit price to the billing amount stored in the fee DB 14m in association with this stamp card creator ID.

If cost burden information is stored (step S601: YES), the billing amount update unit 1110 updates the billing amount by adding the point accrual unit price to the community operator's billing amount (step S603). For example, the billing amount update unit 1110 may obtain the community operator ID associated with the community ID of the community checked in by user U2 from the community DB 14b. The billing amount update unit 1110 may add the point accrual unit price to the billing amount stored in the fee DB 14m associated with this community operator ID. After step S602 or S603 is completed, the billing amount update process ends. Returning to Figure 22, after the billing amount update process is completed, steps S308 to S314 are executed as in the first embodiment.

As described above, according to this embodiment, when a stamp process is executed, the SNS server 1 executes a point-granting process to award points to the user on the user terminal 2. Therefore, it is possible to more effectively encourage users to go to areas related to the community specified by the creator of the stamp card.

Here, when the point awarding process is executed, the SNS server 1 may update at least one of the billing amounts to the stamp card creator and the community creator. Furthermore, if the community associated with the area containing the user terminal 2's location is a non-paying community, the SNS server 1 may add the entire point awarding unit price to the billing amount to the stamp card creator. Also, if the community associated with the area containing the user terminal 2's location is a paying community, the SNS server 1 may add at least a portion of the point awarding unit price to the billing amount to the community operator. In this case, the appropriate billing recipient can be contacted depending on whether the community operator pays the costs or not.

In this case, if the community associated with the area containing the user terminal 2's location is a community that bears the costs, SNS server 1 may add the entire point accrual unit price to the amount billed to the community operator. In this case, if the user travels within the area associated with a community where the operator bears the costs, the operator of that community will bear the costs equivalent to the entire point accrual unit price.

Furthermore, SNS server 1 may send community selection screen information to the user terminal 2 used by the stamp card creator. Alternatively, SNS server 1 may generate the community selection screen by prioritizing community display information indicating communities that bear the costs over community display information indicating communities that do not. In this case, the probability of selecting a community where the operator bears the cost of awarding points can be made higher than the probability of selecting a community where the operator does not bear the cost. Therefore, community operators can be encouraged to bear the cost of awarding points.

[4. Fourth Embodiment]
Next, a fourth embodiment will be described. Except for the points described below, the fourth embodiment may be identical to the third embodiment. In this embodiment, if the operator of a community where a user has checked in chooses to bear the cost of awarding points, the operator bears a portion of the point awarding cost, and the stamp card creator bears the remaining portion of the point awarding cost. The community operator can set this cost burden rate. The SNS server 1 operates in such a way that the higher the burden rate, the more users will check in to that community. The community operator is also recommended a cost burden rate.

[4-1. SNS Server Configuration]
Next, the configuration of the SNS server 1 will be described with reference to Figures 24 and 25. Figure 24 is a block diagram showing an example of the schematic configuration of the SNS server 1 according to this embodiment. In Figure 24, the same elements as in Figure 17 are denoted by the same reference numerals. The difference between Figure 24 and Figure 17 is that in Figure 24, the storage unit 14 also stores a load rate setting history DB 14n.

Figure 25 shows an example of the contents stored in the stamp history DB 14i, cost burden DB 14l, and burden rate setting history DB 14n. The difference between the stamp history DB 14i shown in Figure 25 and the stamp history DB 14i shown in Figure 5 is that the stamp history DB 14i in Figure 25 also stores the community operator burden rate. The community operator burden rate indicates the percentage of the point awarding cost incurred when points are awarded to users in response to stamps being placed on the stamp card that is borne by the community operator, indicated by the community ID. If the stamp card creator bears the entire point awarding cost, the community operator burden rate is 0 percent.

The difference between the cost-sharing DB14l shown in Figure 25 and the cost-sharing DB14l shown in Figure 18 is that the cost-sharing DB14l shown in Figure 25 also stores the cost-sharing rate. The cost-sharing rate represents the percentage of the point accrual unit price that the community operator, indicated by the community ID, bears. It may be possible for the community operator to set the cost-sharing rate. The cost-sharing rate may be, for example, greater than 0 percent and less than or equal to 100 percent.

The burden rate setting history DB14n may store a history of the community administrator's burden rate settings. For example, each time a burden rate is set or changed, the burden rate setting history DB14n may store the community ID, community administrator ID, burden rate setting date, and the set burden rate, etc., as a burden rate setting log, associated with each other. The community ID indicates the community for which the burden rate was set. The community administrator ID is the user ID of the administrator who set the burden rate. The burden rate setting date indicates the date on which the burden rate was set.

[4-2. Functional Overview of the System Control Unit of the SNS Server]
Next, the functional overview of the system control unit 11 of the SNS server 1 will be described with reference to Figures 26 and 27. Figure 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 Figure 26, the same reference numerals are used for elements that are the same as in Figure 19. The difference between Figure 26 and Figure 19 is that in Figure 26, the system control unit 11 also functions as a load rate recommendation information transmission unit 1111 and a load rate acquisition unit 1112.

The cost burden recommendation information transmission unit 1111 may transmit cost burden recommendation information to the user terminal 2 used by the community operator, indicating a recommended cost burden rate for awarding points to users. For example, the cost burden recommendation information transmission unit 1111 may display a cost burden setting screen on the user terminal 2. The cost burden recommendation information may be displayed on this cost burden setting screen. The cost burden setting screen may be a screen for the community operator to select whether or not to bear the cost of awarding points, or to set the cost burden rate. The cost burden setting screen may be displayable when creating a community or when changing the cost burden settings. If the operator selects to bear the cost on the cost burden setting screen, the operator sets the cost burden rate. At this time, the operator can refer to the cost burden recommendation information. The cost burden setting screen may display, for example, several predetermined cost burden rates as options. It may be possible to select a cost burden rate from among these options. In this case, the cost burden recommendation information displayed on the cost burden setting screen may indicate which option is the recommended cost burden rate. Alternatively, it may be possible to directly input the cost burden rate on the cost burden setting screen. The cost burden recommendation information transmission unit 1111 may display the recommended cost burden rate on the cost burden setting screen. Alternatively, the cost burden recommendation information transmission unit 1111 may display the cost burden recommendation information on a screen different from the cost burden setting screen, and then display the cost burden setting screen after that screen has been displayed.

The burden rate recommendation information transmission unit 1111 may decide whether or not to transmit burden rate recommendation information, or may decide on a recommended burden rate, based on past performance in which points were awarded to users by checking in to the community. For example, the burden rate recommendation information transmission unit 1111 may decide on a 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 operated by the operator. The number of stamps can be calculated by referring to the stamp history DB 14i. For example, the burden rate recommendation information transmission unit 1111 may decide on a higher burden rate as the recommended burden rate if the number of stamps is small. As will be described later, the higher the burden rate specified by the community operator, the higher the probability that the community will be selected by the stamp card creator as a community where stamp cards can be used. As more stamp cards become available to that community, the number of users who possess those stamp cards will also increase, and consequently, the number of users who check in to that community and get stamps will also increase. If the community administrator has never set a contribution rate before, the contribution rate recommendation information transmission unit 1111 does not need to send contribution rate recommendation information. In this case, the contribution rate recommendation information will not be displayed on the cost contribution setting screen, etc.

The burden rate recommendation information transmission unit 1111 may calculate another indicator using the number of stamps. This indicator may, for example, show a higher value as the number of stamps increases, or it may show a lower value as the number of stamps increases. In either case, the burden rate recommendation information transmission unit 1111 may recommend a higher burden rate as the number of stamps decreases. For example, a table or the like that storing information showing the correspondence between indicator values and burden rates may be stored in the storage unit 14. The burden rate recommendation information transmission unit 1111 may determine the recommended burden rate from the calculated indicator based on this table or the like. The burden rate recommendation information transmission unit 1111 may, for example, calculate the average or median value of the indicator per predetermined period (e.g., per month), or it may calculate the indicator value without dividing it into periods. The number of stamps itself may also be the indicator.

Assume that the indicator used is one that shows a higher value as the number of stamps increases. In this case, the burden rate recommendation information transmission unit 1111 may send burden rate recommendation information to the operator's user terminal 2 only if the calculated value of the indicator is below a predetermined threshold. That is, burden rate recommendation information is displayed on the cost burden setting screen, etc., only if the value of the indicator is below the threshold. If the number of stamps is relatively large, there is no need to recommend a particular burden rate. Alternatively, assume that the community operator has already set some kind of burden rate. The burden rate recommendation information transmission unit 1111 may send burden rate recommendation information to the operator's user terminal 2 only if the burden rate corresponding to the calculated value of the indicator is higher than the burden rate set by that operator. If a causal relationship or correlation is found between the burden rate specified by the community operator and the value of the indicator, the burden rate recommendation information transmission unit 1111 may calculate the indicator for each burden rate set by that operator so far during the period in which that burden rate was applied. The period in 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 the burden rate from among the previously set burden rates for which an indicator value higher than a predetermined threshold has been calculated as the recommended burden rate. If no such burden rate exists, the burden rate recommendation information transmission unit 1111 may determine a burden rate higher than the previously set burden rate as the recommended burden rate. As mentioned above, since a higher burden rate tends to result in a larger number of stamps, there is at least a correlation between the burden rate and the number of stamps. However, the indicator calculated from the number of stamps does not necessarily have a causal relationship or correlation with the burden rate. Furthermore, if the indicator used shows smaller values as the number of stamps increases, the burden rate recommendation information transmission unit 1111 may perform the comparison between the indicator and the threshold under conditions reversed from those described above.

The indicator could be, for example, the stamp rate. The stamp rate is the percentage of users who possess a stamp card available to that community and who have received a stamp by checking in to that 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 decreases.

The indicator may be, for example, the budget amount per person. The budget amount per person may be calculated by dividing the budget amount set by the community operator by the number of stamps collected during the period in which the budget is consumed (i.e., one month, etc.). Users who check in to the community are also users who have earned points in accordance with their check-in. The budget amount per person can be calculated by referring to the stamp card DB 14f and the stamp history DB 14i. The burden rate recommendation information transmission unit 1111 may, for example, recommend a higher burden rate the higher the budget amount per person. The budget amount may be the amount that the community operator 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 less than the number that the operator expected. As mentioned above, the burden rate recommendation information transmission unit 1111 may calculate the budget amount per person for each burden rate set by the operator. 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, for instance, the budget amount specified by the community operator from the stamp card DB 14f. The burden rate recommendation information transmission unit 1111 may also obtain the user ID included in each obtained stamp log. Furthermore, the burden rate recommendation information transmission unit 1111 may search the burden rate setting log associated with the community ID of that community from the burden rate setting history DB 14n. Based on the burden rate setting date included in the retrieved burden rate setting log, the burden rate recommendation information transmission unit 1111 may identify the period and number of days during which each set burden rate was applied. The burden rate recommendation information transmission unit 1111 may also search the stamp log containing the community ID of that community from the stamp history DB 14i. Based on the stamp date and time and user ID included in each retrieved stamp log, the burden rate recommendation information transmission unit 1111 may calculate the number of people who stamped their cards during the period in which that burden rate was applied as the number of stamps for each burden rate. The burden rate recommendation information transmission unit 1111 may calculate the per capita budget amount for the period in which each 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 also calculate the monthly per capita budget amount for each burden rate based on the calculated per capita budget amount and the ratio of the number of days in the period in which that burden rate was maintained to 30 days.

The burden rate recommendation information transmission unit 1111 may further transmit indicator information showing the calculated indicator values to the user terminal 2 used by the community administrator. This allows the burden rate recommendation information transmission unit 1111 to display the indicator information on the cost burden setting screen, etc. This allows the administrator to check past performance. If the burden rate recommendation information transmission unit 1111 has calculated indicator values for each burden rate, it may also transmit indicator information showing the combination of that burden rate and indicator value for each burden rate.

The cost burden acquisition unit 1112 may acquire the cost burden rate specified by the community operator who bears the cost of awarding points from the operator's user terminal 2. For example, the cost burden acquisition unit 1112 may acquire the cost burden rate specified by the operator on the cost burden setting screen. The cost burden acquisition unit 1112 may associate the acquired cost burden rate with the community ID of that community and store it in the cost burden DB 14l.

The community selection screen transmission unit 1108 may generate community selection screen information by prioritizing the display of community information indicating communities that bear the cost of awarding points, as in the third embodiment, above the display priority of community information indicating communities that do not bear the cost of awarding points. Furthermore, the community selection screen transmission unit 1108 may generate community selection screen information by prioritizing the display of community information indicating a community with a higher burden rate specified by the community operator. This ensures that the higher the burden rate of the community operator, the more preferentially the community information for that community is displayed. Therefore, stamp card creators are more likely to select communities with higher burden rates as communities where stamp cards can be used. This promotes visits to spots in communities with high burden rates.

The billing amount update unit 1110 may, if the community ID associated with the spot area including the location of the user terminal 2, as indicated by the location information acquired by the location information acquisition unit 1103, indicates a community that bears the cost of awarding points, add an amount equivalent to the burden rate acquired by the burden rate acquisition unit 1112 to the billing amount to the community operator. The billing amount update unit 1110 may then add an amount equivalent to the difference between the point awarding unit price and the amount added to the billing amount to the operator to the billing amount to the stamp card creator.

Figure 27 shows an example of how points are awarded to a user. For example, the operator of community 202, which is related to a ramen chain as shown in Figure 2, has chosen to bear the costs and has specified a 40% contribution rate. On the other hand, the operator of community 203, which is related to a soba noodle shop, has also chosen to bear the costs and has specified a 70% contribution rate. As shown in Figure 27, user U2, who possesses user terminal 2-2, goes to ramen shop 402 within spot area 302 and checks in to community 202 (step S31). In response to the check-in, SNS server 1 stamps user U2's stamp card 101-1 and awards points to user U2 (step S32). SNS server 1 adds 40% of the point awarding unit price to the amount billed to the operator of community 202 (step S33), and adds 60% of the point awarding unit price to the amount billed to the creator of stamp card 101 (step S34). For example, if the point accrual rate is 20 yen, 80 yen is added to the billing amount for the community 202 operator, and 120 yen is added to the billing amount for the creator of stamp card 101. Then, user U2 goes to soba restaurant 407 within spot area 305 and checks in to community 203 (step S35). In response to the check-in, SNS server 1 stamps user U2's stamp card 101-1 and awards points to user U2 (step S36). SNS server 1 adds 70% of the point accrual rate to the billing amount for the community 203 operator (step S37), and adds 30% of the point accrual rate to the billing amount for the creator of stamp card 101 (step S38). For example, 140 yen is added to the billing amount for the community 202 operator, and 60 yen is added to the billing amount for the creator of stamp card 101.

[4-3. Operation of the communication system]
Next, the operation of the communication system S will be described with reference to Figures 28 to 31. Figure 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 Figure 28, user U3, who is the operator of the community, operates user terminal 2-3 as user terminal 2 of user U3. In response to this operation, user terminal 2-3 sends a cost burden setting screen request to SNS server 1 (step S701). The cost burden setting screen request may include, for example, the user ID of user U3 and the community ID of the community operated by user U3. Upon receiving the cost burden setting screen request, SNS server 1 executes a cost burden setting screen information generation process (step S702).

Figure 29 is a flowchart illustrating 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 Figure 29, the cost burden recommendation information transmission unit 1111 obtains an HTML document template for the cost burden setting screen from the storage unit 14 (step S801). Next, the cost burden recommendation 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). Based on the search results, the cost burden recommendation information transmission unit 1111 determines whether a corresponding stamp card ID exists (step S803). If no corresponding stamp card ID is found (step S803: NO), the cost burden setting screen information generation process terminates.

If a matching stamp card ID exists (Step S803: YES), the issued card information containing that stamp card ID is retrieved from the issued card DB 14h for each retrieved stamp card ID (Step S804). Next, the cost burden recommendation information transmission unit 1111 retrieves the stamp log containing the community ID included in the cost burden setting screen request from the stamp history DB 14i (Step S805).

Next, the burden rate recommendation information transmission unit 1111 calculates the stamp rate (step S806). For example, the burden rate recommendation information transmission unit 1111 may calculate the number of users who possess stamp cards by counting the number of issued card information entries that have been retrieved. Alternatively, the burden rate recommendation information transmission unit 1111 may calculate the number of stamps based on the user IDs included in each retrieved stamp log. The burden rate recommendation information transmission unit 1111 may also calculate the stamp rate by dividing the number of stamps by the number of users who possess stamp cards.

Next, the recommended burden rate information transmission unit 1111 adds indicator information showing the calculated stamp rate to the HTML document of the cost burden setting screen (step S807). Then, the recommended burden rate information transmission unit 1111 determines whether the stamp rate is higher than a threshold (step S808). If the stamp rate is higher than the threshold (step S808: YES), the cost burden setting screen information generation process ends. If the stamp rate is below the threshold (step S808: NO), the recommended burden rate information transmission unit 1111 adds recommended burden rate information showing the burden rate corresponding to the calculated stamp rate to the HTML document of the cost burden setting screen (step S809), and the cost burden setting screen information generation process ends.

Returning to Figure 28, once the cost burden setting screen information generation process is complete, the cost burden rate information transmission unit 1111 sends 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, user U3 selects to bear the cost of awarding points and specifies the cost burden rate (step S705). The user terminal 2-3 sends the cost burden information, including the specified cost burden rate, to the SNS server 1 (step S706). The cost burden rate acquisition unit 1112 of the SNS server 1, having received the cost burden information, stores this cost burden information in the cost burden DB 14l (step S707). The cost burden rate acquisition unit 1112 also stores the cost burden rate setting log in the cost burden rate setting history DB 14n. For example, the cost burden acquisition unit 1112 may generate a cost burden setting log based on the community ID, community administrator ID, and cost burden rate included in the cost burden information, as well as today's date.

Figure 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 Figure 30, the same reference numerals are used for the same processes as in Figure 21. As shown in Figure 30, first, steps S101, S501 to S503 are executed, similar to the third embodiment. Next, the community selection screen information transmission unit 1108 sets the priority of each searched community (step S511). For example, the community selection screen information transmission unit 1108 gives a higher priority to communities that bear the cost of awarding points than to other communities. Furthermore, based on the cost burden rate included in the cost burden information, the community selection screen information transmission unit 1108 gives a higher priority to communities that bear the cost, the higher the community's cost burden rate. Next, steps S505 to S508 and S103 to S105 are executed, similar to the third embodiment.

Figure 31 is a flowchart showing an example of the billing amount update process by the system control unit 11 of the SNS server 1 according to this embodiment. In Figure 31, the same reference numerals are used for processes identical to those in Figure 23. As shown in Figure 31, the billing amount update unit 1110 determines whether or not cost burden information is stored in the cost burden DB 14l, associated with the community ID of the community checked in by user U2 (step S601). If cost burden information is not stored (step S601: NO), the billing amount update unit 1110 adds the point accrual unit price to the billing amount of the stamp card creator and updates the billing amount (step S602).

If cost burden information is stored (Step S601: YES), the billing amount update unit 1110 obtains the community operator's cost burden rate from the cost burden information (Step S611). Next, the billing amount update unit 1110 adds that cost burden rate to the point accrual unit price to calculate the added amount. Then, the billing amount update unit 1110 adds this added amount to the community operator's billing amount to update the billing amount (Step S612). Next, the billing amount update unit 1110 subtracts the community operator's cost burden rate from 1 to calculate the stamp card creator's cost burden rate. The billing amount update unit 1110 calculates the added amount by adding that cost burden rate to the point accrual unit price. Then, the billing amount update unit 1110 adds this added amount to the stamp card creator's billing amount to update the billing amount (Step S613). After step S602 or step S613, the billing amount update unit 1110 adds the community operator's burden rate to the stamp log stored in the stamp history DB 14i using the stamp control process shown in Figure 22 (step S614), and the billing amount update process ends.

As described above, according to this embodiment, the SNS server 1 may obtain the cost-sharing rate specified by the community operator who bears the cost of awarding points. Furthermore, if 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 an amount equivalent to the obtained cost-sharing rate to the amount billed to the community operator, relative to the point awarding unit price. Additionally, the SNS server 1 may add an amount equivalent to the difference between the point awarding unit price and the amount added to the billed amount to the community operator to the amount billed to the stamp card creator.

Here, when SNS server 1 transmits community selection screen information, it may generate community selection screen information with a higher priority for community display information representing a community, depending on the burden rate specified by the community operator. In this case, the higher the burden rate specified by the operator, the higher the probability that the community will be selected. Therefore, it is possible to encourage community operators to set a higher burden rate for the costs of awarding points.

Furthermore, SNS server 1 may obtain the number of users who have previously received points because their user terminal 2 was located within a spot area indicated by area information associated with a community ID that identifies a community for which the operator bears the costs. SNS server 1 may also send recommended burden rate information to user terminal 2 used by the operator. In this case, SNS server 1 may increase the recommended burden rate if the number of obtained users is small. In this case, the operator can specify the actual burden rate based on the recommended burden rate. A higher specified burden rate increases the probability that the community will be selected by the stamp card creator. Since points are awarded to users who visit the spot area associated with the selected community, if the number of users visiting the spot area associated with that community is small, that number can be increased.

(Note 1) A stamp card management device characterized by comprising: acquisition means for acquiring two or more community identification information that identifies two or more communities specified by the creator of the stamp card, from among multiple distinct communities where information related to each pre-set area is provided within the community; identification information storage control means for storing stamp card identification information that identifies the stamp card to be created, in association with the two or more acquired community identification information; acquisition means for acquiring location information indicating the location of a portable terminal device; and stamp means for executing a stamping process for 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 the area information indicating the area related to the community, in association with the community identification information that identifies the community, for each of the multiple communities;

(Note 2) The stamp card management device according to Note 1, further comprising a joining means that, if the region indicated by any of the region information stored in the region information storage means includes the location indicated by the acquired location information, performs a process of joining the user to the community identified by the community identification information associated with any of the region information.

(Note 3) The stamp card management device according to Note 1 or 2, characterized in that, for each of the two or more communities, either non-stamp information indicating that the stamp has not been applied or stamp information indicating that the stamp has been applied is stored in the stamp information storage means in association with the stamp card identification information and the user identification information identifying the user who possesses the created stamp card, and the stamp means, for the community indicated by the community identification information associated with the area information indicating the area including the location indicated by the acquired location information, if 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, the stamp processing is performed by changing the non-stamp information to stamp information, and 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 benefit is granted to the user identified by the user identification information.

(Note 4) The stamp card management device according to any one of Notes 1 to 3, characterized in that the two or more communities are two or more business communities where information relating to two or more different businesses that sell the transaction item is provided within the community, each of the two or more businesses sells the transaction item at a facility related to that 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 that business includes the location of the facility related to that business.

(Note 5) The stamping means is characterized in that it performs the stamping process on the condition that the user is a member of at least one of the two or more communities, as described in any one of Notes 1 to 4 of the stamping device.

(Note 6) The stamp card management device according to any one of Notes 1 to 5, characterized in that the two or more regions indicated by the two or more region information stored in the region information storage means for each of the two or more communities include locations that are different from each other.

(Note 7) The stamp card management device according to Note 1, further comprising a granting means for granting points of the point program to the user of the terminal device when the stamping process is performed by the stamping means.

(Note 8) The stamp card management device according to Note 7, wherein a first billing amount to be charged to the creator for the granting of the points is stored in a billing amount storage means, and a second billing amount to be charged to the operator of a community that has chosen to bear the cost of granting the points from among the plurality of communities is stored in the billing amount storage means, and when the granting process is executed by the granting means, the device further comprises an updating means for updating at least one of the stored first billing amount and second billing amount, wherein the updating means adds the entire amount of the cost of granting the points to the first billing amount if the community identification information associated with the area including the location indicated by the acquired location information indicates a community that does not bear the cost, and adds at least a portion of the cost of granting the points to the second billing amount if the community identification information associated with the area including the location indicated by the acquired location information indicates a community that bears the cost, and the sum of the first added amount added to the first billing amount and the second added amount added to the second billing amount becomes the cost of the cost.

(Note 9) The stamp card management device according to Note 8, characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the cost, the update means adds the entire amount of the cost to the second billing amount.

(Note 10) The stamp card management device according to Note 8 or 9, further comprising screen information transmission means for transmitting screen information to a creator terminal device used by the creator, which displays a screen showing community information representing at least some of the communities among the plurality of communities in a manner corresponding to the priority of displaying the community information, and which can accept an operation to select at least one of the community information displayed on the screen; wherein the acquisition means acquires community identification information from the creator terminal device that identifies the community indicated by the community information selected by the creator from the screen; and the screen information transmission means generates the screen information by setting the priority of the community information indicating the communities that bear the costs to be higher than the priority of the community information indicating the communities that do not bear the costs.

(Note 11) The stamp card management device according to Note 8, further comprising a means for acquiring a burden rate specified by the operator of the community that bears the cost of awarding the points, wherein the update means, 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, adds the second additional amount corresponding to the acquired burden rate to the cost amount to the second billing amount, and adds the first additional amount corresponding to the difference between the cost amount and the second additional amount to the first billing amount.

(Note 12) The stamp card management device according to Note 11, further comprising screen information transmission means for transmitting screen information to a creator terminal device used by the creator, which displays a screen showing community information representing at least some of the communities among the plurality of communities in a manner corresponding to the display priority of the community information, and which can accept an operation to select at least one of the community information displayed on the screen; wherein the acquisition means acquires community identification information from the creator terminal device that identifies the community indicated by the community information selected by the creator from the screen; and the screen information transmission means generates the screen information by increasing the priority of the community information representing the community as the burden rate specified by the operator of the community increases.

(Note 13) The stamp card management device according to Note 11 or 12, further comprising: a number acquisition means for acquiring the number of users who have been awarded points by the awarding means, and who have been awarded 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 operator bears the costs; and a recommendation information transmission means for transmitting recommendation information indicating the recommended burden rate to an operator terminal device used by the operator who bears the costs, wherein the recommendation information transmission means increases the recommended burden rate as the number of acquired users decreases, and the burden rate acquisition means acquires the specified burden rate from the operator terminal device to which the recommendation information is transmitted.

(Note 14) A stamp card management method performed by a computer, comprising: an acquisition step of acquiring two or more community identification pieces that identify two or more communities specified by the creator of the stamp card, from among multiple distinct communities where information related to pre-set areas is provided within the community; an identification information storage control step of storing stamp card identification pieces that identify the stamp card to be created in an identification information storage means in association with the two or more acquired community identification pieces; an acquisition step of acquiring location information indicating the location of a portable terminal device; and a stamp step of executing a stamping process for the user of the terminal device if, for each of the multiple communities, 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 pieces associated with the stamp card identification pieces, among the area information stored in the area information storage means that stores area information indicating the area related to the community in association with the community identification pieces that identify the community.

1 SNS server 2 User terminal 3 Point management server 11 System control unit 12 System bus 13 Input/output interface 14 Storage unit 14a Member DB
14b Community DB
14c Area DB
14d Check-in history DB
14e Community Member Database
14f Stamp Card DB
14g Stamp card association database
14h Issued Card Database
14i Stamp History DB
14j Bonus DB
14k Issued Card Rally Database
14L Cost-sharing DB
14m Rate DB
14n Load Rate Setting History DB
15 Communication Unit 1101 Community ID Acquisition Unit 1102 Stamp Card Creation Unit 1103 Location Information Acquisition Unit 1104 Check-in Determination Unit 1105 Membership Unit 1106 Stamp Unit 1107 Reward Granting Unit 1108 Community Selection Screen Information Transmission Unit 1109 Point Granting Unit 1110 Billing Amount Update Unit 1111 Burden Rate Recommendation Information Transmission 1112 Burden Rate Acquisition Unit NW Network S Communication System

Claims (7)

In a stamp card management device,
The identification information storage means stores stamp card identification information that identifies the stamp card, and community identification information that identifies the community associated with the stamp card from among a plurality of communities related to each of the pre-set areas.
For each of the aforementioned multiple communities, region information indicating the region related to the community is stored in the region information storage means, associated with the community identification information that identifies the community.
The first billing amount, which is charged to the creator who made the stamp card for the awarding of points in the points program, is stored in the billing amount storage means.
For the operator of one of the aforementioned multiple communities who has chosen to bear the cost of awarding the points, the second billing amount to be charged to the operator is stored in the billing amount storage means.
A location information acquisition means for acquiring location information indicating the location of a portable terminal device,
If, among the area information stored in the area information storage means, the area indicated by the area information associated with the community identification information associated with the stamp card identification information includes the location indicated by the acquired location information, then a processing means is provided to perform a stamping process for the user of the terminal device to stamp the stamp card and a granting process to grant points to the user of the terminal device.
When the granting process is performed by the processing means, an update means updates at least one of the stored first billing amount and second billing amount,
Equipped with ,
The update means is,
If the community identification information associated with the area including the location indicated by the acquired location information indicates a community that does not bear the costs, the entire amount of the costs for awarding the points shall be added to the first billing amount.
A stamp card management device characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the cost, at least a portion of the cost burden amount is added to the second billing amount, and the sum of the first added amount added to the first billing amount and the second added amount added to the second billing amount becomes the cost burden amount . The stamp card management device according to claim 1, characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the cost, the update means adds the entire amount of the cost to the second billing amount. A screen information transmission means transmits to a creator terminal device used by the creator screen information that displays a screen in which each of the community display information representing at least some of the communities among the plurality of communities is displayed in a manner corresponding to the display priority of the community display information, and which accepts an operation to select at least one of the community display information displayed on the screen, to the creator terminal device used by the creator.
Community identification information acquisition means for acquiring community identification information from the creator terminal device, which identifies the community indicated by the community display information selected by the creator from the aforementioned screen,
An identification information storage control means that stores the stamp card identification information in the identification information storage means in association with the acquired community identification information,
Furthermore,
The stamp card management device according to claim 1 or 2, characterized in that the screen information transmission means generates the screen information by setting the priority of the community display information indicating communities that bear the costs among at least some of the communities to be higher than the priority of the community display information indicating communities that do not bear the costs. The system further includes means for obtaining a burden rate, which is determined by the operator of the community that bears the cost of awarding the aforementioned points.
The stamp card management device according to claim 1, characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the costs, the update means adds the second additional amount corresponding to the acquired burden rate to the second billing amount, and adds the first additional amount corresponding to the difference between the cost amount and the second additional amount to the first billing amount. A screen information transmission means transmits to a creator terminal device used by the creator screen information that displays a screen in which each of the community display information representing at least some of the communities among the plurality of communities is displayed in a manner corresponding to the display priority of the community display information, and which accepts an operation to select at least one of the community display information displayed on the screen, to the creator terminal device used by the creator.
Community identification information acquisition means for acquiring community identification information from the creator terminal device, which identifies the community indicated by the community display information selected by the creator from the aforementioned screen,
An identification information storage control means that stores the stamp card identification information in the identification information storage means in association with the acquired community identification information,
Furthermore,
The stamp card management device according to claim 4, characterized in that the screen information transmission means generates the screen information by increasing the priority of the community display information indicating the community as the burden rate specified by the operator of the community is higher. A number acquisition means for acquiring the number of users who have been awarded points by the processing means, and who have been awarded 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.
A recommendation information transmission means for transmitting recommendation information indicating the recommended burden rate to an operator terminal device used by the operator who bears the aforementioned costs, wherein the recommendation information transmission means increases the recommended burden rate as the number of acquired people decreases.
Furthermore,
The stamp card management device according to claim 5, characterized in that the means for obtaining the burden rate obtains the specified burden rate from the operator terminal device to which the recommended information is transmitted. In a computer-based stamp card management method,
The identification information storage means stores stamp card identification information that identifies the stamp card, and community identification information that identifies the community associated with the stamp card from among a plurality of communities related to each of the pre-set areas.
For each of the aforementioned multiple communities, region information indicating the region related to the community is stored in the region information storage means, associated with the community identification information that identifies the community.
The first billing amount, which is charged to the creator who made the stamp card for the awarding of points in the points program, is stored in the billing amount storage means.
For the operator of one of the aforementioned multiple communities who has chosen to bear the cost of awarding the points, the second billing amount to be charged to the operator is stored in the billing amount storage means.
A location information acquisition step to obtain location information indicating the location of a portable terminal device,
If, among the area information stored in the area information storage means, the area indicated by the area information associated with the community identification information associated with the stamp card identification information includes the location indicated by the acquired location information, the processing step of performing a stamping process to stamp the stamp card for the user of the terminal device and performing a granting process to grant the points to the user of the terminal device,
When the granting process is performed by the processing step described above, an update step is performed to update at least one of the stored first billing amount and second billing amount,
Includes,
The aforementioned update step is:
If the community identification information associated with the area including the location indicated by the acquired location information indicates a community that does not bear the costs, the entire amount of the costs for awarding the points shall be added to the first billing amount.
A stamp card management method characterized in that, if the community identification information associated with the area including the location indicated by the acquired location information indicates the community that bears the costs, at least a portion of the cost burden amount is added to the second billing amount, and the sum of the first added amount added to the first billing amount and the second added amount added to the second billing amount becomes the cost burden amount .