JP2012203849A - Server device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide information useful for selecting a shop with a server device connected to plural user terminals via a network and providing shop information to each user terminal.SOLUTION: A server device 1 is connected to user terminals 3 via a network NW and provides shop information to each user terminal 3. The server device includes: a user attribute database 30 in which each identification information for identifying a user of the user terminal 3 is associated with preference information indicating the user's preference in food and drink; and an information providing unit 11 for, in response to a request from the user terminal 3, using the user attribute database 30 to generate image information for the user of the user terminal and transmitting the image information to the user terminal 3. The image information includes user preference information in which the preference of the user of the user terminal in food and drink is represented graphically.

Description

  The present invention relates to a server device that provides various information to a network terminal.

  Web sites that provide search engines, store information, and the like to user terminals such as personal computers and smartphones are widely used. Some of these websites accept membership registrations from users, provide their dedicated pages (my pages) to the user terminals of the registered users, and provide various services from my pages. Are known. In addition, the Web site that accepts member registration as described above provides a bookmark function for registering user's favorite store information (information such as store URL, address, service contents, etc.) on the My Page. Convenience is also being improved. In addition, on websites that accept member registration as described above, points that can be used for discounts when purchasing products or eating and drinking are given to product purchase histories and operation histories (comment postings). It has been broken. Patent Document 1 discloses a technique related to a browser device having a bookmark function.

Japanese Patent Laid-Open No. 2005-010882

  By the way, in the Web site that provides store information as described above, if information that is helpful for store selection can be referred to in addition to information that introduces a store provided by a restaurant, it is possible to select a store. It is useful as an effective judgment material.

  However, the website providing the bookmark function as described above can browse store information (information provided from the restaurant side) registered by the user with the bookmark function on My Page, The store information registered by the user and the reputation (comments) about the store cannot be viewed, and useful information has not been sufficiently provided to users who are looking for a store. Therefore, the user may not be able to select a store that can be satisfied efficiently. On the Web site to which points are given, there are many users to whom points are given, but information that prompts the acquisition and use of points is not sufficiently provided, and the use record is low. As a result, in the above-mentioned Web site, there is a store where points can be effectively used, but the store may not be selected as a store selection target.

  This invention is made in view of the said subject, Comprising: In the server apparatus connected with a some user terminal via a network and providing store information with respect to each user terminal, information effective for selection of a store is provided. The purpose is to provide.

  The present invention for solving the above-mentioned problems is a server device that is connected to a plurality of user terminals via a network and provides store information to each user terminal, and each identification information that identifies a user of the user terminal In addition, in response to a request from the user terminal, a user attribute database that associates preference information indicating the user's preference, the user attribute database is used to generate image information for the user of the user terminal. And an information providing unit that transmits the image information to the terminal, wherein the image information includes user preference information that shows a graph of user preferences of the user terminal.

  Thus, according to this invention, the user preference information which showed the user's preference in the graph was shown to the user of a user terminal. For this reason, the user can select a store after confirming his / her preference (for example, to narrow down the search target to a store that matches his / her preference), so that the store that matches his / her preference is efficiently used. You can search well.

  Moreover, it has the user registration database with which the information regarding the store selected and registered by the user specified by this identification information was linked | related for every said identification information, The said information provision part is the said user terminal on the said image information To the user terminal of the user terminal is configured to be able to accept a request for presentation of information related to other users, and when the presentation request is received, the user terminal user and the preference of the user terminal are selected from the user attribute database. Other users who are similar to each other are provided and an introduction page for introducing the selected other users is provided to the user terminal, and other users introduced on the introduction page using the user registration database It is desirable to be able to select and provide information related to the store registered by the user terminal. The information on the store selected and registered by the user includes at least one of store information introducing the store selected by the user and menu information introducing a menu provided by the user. It is desirable that it be included. The preference information includes at least restaurant area information used by the user, restaurant preference information indicating preference for each genre of the restaurant, beverage preference information indicating taste for each type of beverage, taste, and It is desirable that any one of the food preference / taste information indicating the preference for each ingredient is included.

  As described above, according to the present invention, the user terminal is provided with an introduction page that introduces other users who have similar preferences to the user, thereby providing the user with pleasure other than shop search. It becomes like this. In addition, since the user terminal is provided with information about stores registered by other users who have similar preferences to the user, it is possible to select a store that can be satisfied more efficiently. In other words, according to the present invention, it is possible to see information on stores that other users with similar preferences like (or recommend), so it is possible to efficiently search for stores that match their preferences. be able to.

  Further, for each of the identification information, a user database in which points given to the user specified by the identification information and a user rank set for the specified user are associated, and for each user rank, the rank A user privilege table in which privilege information provided to the user is registered, and the image information includes a user point of the user terminal, a user rank set for the user, and an introduction of the privilege for the user rank. The information providing unit is set to the user of the user terminal by using the user database and the user privilege table when the reception button is selected by the user terminal. A user privilege page presenting a privilege for the user rank is generated, and the user privilege page is displayed on the user terminal. It is desirable to trust. With this configuration, the user of the user terminal is made to recognize the user rank of the user and the user's point, and the privilege for the user rank is guided, so that the user can be prompted to acquire and use the point.

  In addition, the point includes an expiration date, and includes a time-limited point that automatically expires after the expiration date, and further, the validity of the time-limited point given to the user of the user terminal It is desirable to provide an e-mail processing unit that generates an e-mail indicating that the expiration date is approaching and sends the e-mail to the user terminal when the expiration date approaches. As described above, according to the present invention, a limited time point is provided, and when the limited time point approaches the expiration date, the user is notified of this fact (notified by e-mail). This makes it possible to prompt the user to use points.

  ADVANTAGE OF THE INVENTION According to this invention, in the server apparatus connected with a some user terminal via a network and providing shop information with respect to each user terminal, the information effective for selection of a shop can be provided.

It is the block diagram which showed the structure of the information provision system of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the user database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the 1st database which comprises the user attribute database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the 2nd database which comprises the user attribute database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the 3rd database which comprises the user attribute database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the 4th database which comprises the user attribute database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the my restaurant database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the menu contribution database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the fan registration database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the shop utilization log | history database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the store database of embodiment of this invention. It is the schematic diagram which showed an example of the data structure of the member privilege table of embodiment of this invention. It is the schematic diagram which showed an example of the main page of the shop information provision site which the server apparatus of embodiment of this invention provides to a user terminal. It is the schematic diagram which showed an example of the information presentation page regarding the person similar to the user of the store information provision site which the server apparatus of embodiment of this invention provides to a user terminal. It is the schematic diagram which showed an example of the my restaurant introduction page of the information provision site which the server apparatus of embodiment of this invention provides to a user terminal. It is the schematic diagram which showed an example of the menu ranking presentation page of the information provision site which the server apparatus of embodiment of this invention provides to a user terminal.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings. First, the configuration of an information providing system according to an embodiment of the present invention will be described with reference to FIG. FIG. 1 is a block diagram showing the configuration of the information providing system of this embodiment.

  As shown in the figure, the information providing system of the present embodiment is connected to a server device 1 connected to a communication network NW such as the Internet, a plurality of user terminals 3 connected to a communication network NW, and a communication network NW. And a plurality of store terminals 5. The server device 1 can perform data communication with the user terminal 3 via the communication network NW, and provides store information to the user terminal 3 in response to a request from the user terminal 3. It is like that. The server device 1 can perform data communication with the store terminal 5 via the communication network NW. The store terminal 5 is installed in a store such as a restaurant.

  In addition, the server device 1 accepts member registration from a user who uses the user terminal 3, and the user terminal 3 of the user who has registered as a member is dedicated to the user's dedicated page (my page (dedicated to configure a restaurant information providing site). Page)). The server device 1 uses the restaurant or EC site for the user terminal 3 of the user who registered as a member for the use history or operation history (comment posting) of the user's restaurant or EC site. In addition to giving points that can be used for services such as discounts, member ranks (user ranks) are given according to usage histories and operation histories, and privileges according to member ranks are provided.

  Further, the server device 1 bookmarks (selects and registers) a restaurant to be worried from among the store information presented on the restaurant information providing site for the user terminal 3 of the user who has registered as a member. A function (My restaurant function) for listing and displaying registered restaurants is provided. Further, the server device 1 provides the store information listed by the user terminal 3 to the other user terminals 3, or the information related to the store information (the comment introducing the menu of the store) between the user terminals 3. ) Can be exchanged.

  Further, the user terminal 3 includes an information processing apparatus (computer or Smartphone).

  Then, the user terminal 3 can access the server device 1 via the communication network NW, receive a web page constituting the web site transmitted from the server device 1, and display the web page on the display unit. ing. In addition, the user terminal 3 receives an operation via the input unit, selects various data displayed on the Web page, transmits the selected data to the server device 1, or is presented on the Web page. The search conditions can be transmitted to the server device 1.

  In addition, when the user registered as a member uses the restaurant (or EC site), the store terminal 5 sends the use result (utilization date, member's date) to the server device 1 via the communication network NW. The user name (user ID) and accounting amount) are transmitted. In addition, the information provision system of this embodiment has the characteristics in the server apparatus 1, and the user terminal 3 and the shop terminal 5 are implement | achieved by a well-known information processing apparatus. Therefore, in the following, the configuration of the server device 1 will be described in detail, and the description of other configurations will be simplified.

  The server device 1 includes a control unit 10, an information providing unit 11, a data update unit 12, a mail processing unit 13, and a storage unit 14, and provides information related to restaurants to the user terminal 3. It is configured to provide a restaurant information providing site (Web site). Further, the server device 1 provides a member-dedicated service on the Web site to the user terminal 3 of the user who has registered as a member. Here, the storage unit 14 includes a user database 20, a user attribute database 30, a my restaurant database 40, a menu posting database 50, a fan registration database 60, a store use history database 70, a store database 80, A member privilege table 90 is stored. In addition, Web page data (not shown) in which information (icon, frame data, image information) necessary for generating the restaurant information providing site is registered is registered in the storage unit 14.

  The hardware configuration of the server device 1 is not particularly limited. For example, the server device 1 is configured by a computer including a CPU, an auxiliary storage device, a main storage device, a network interface, and an input / output interface. In this case, the auxiliary storage device stores programs for realizing the functions of the control unit 10, the information providing unit 11, the data update unit 12, and the mail processing unit 13. In addition, the storage unit 14 described above is formed in a predetermined area of the auxiliary storage device. The functions of the control unit 10, the information providing unit 11, the data updating unit 12, and the mail processing unit 13 are realized by the CPU loading and executing the program stored in the auxiliary storage device on the main storage device. Is done.

  Specifically, the control unit 10 controls the operation of the entire server device 1 and accepts various settings of the server device 1.

  The information providing unit 11 includes each database (user database 20, user attribute database 30, my restaurant database 40, menu posting database 50, fan registration database 60, store usage history database 70, store database 80 stored in the storage unit 14. The restaurant information providing site is provided to the user terminal 3 using the member privilege table 90). Moreover, the information provision part 11 provides the user preference information which graphed the information which showed the preference regarding a user's eating and drinking using the user attribute database 30. FIG. Further, the information providing unit 11 can open the graphed user preference information to other user terminals 3 (other members). In addition, the information providing unit 11 has information on a registered store on the restaurant information providing site (store information of a restaurant registered by the My Restaurant function, information on a restaurant menu posted by the user, etc. ) Can be disclosed to other user terminals 3 (other members).

  Further, the information providing unit 11 presents the user's member rank and the given points to the user of the user terminal 3, and guides the privilege according to the user's member rank, Encourage use.

  In addition, when the data update unit 12 receives a usage record (usage date, member user name (user ID), store name (store ID), accounting amount) transmitted from the store terminal 5, the store update history database The received usage record is registered (stored) in 70. In addition, the data update unit 12 is a predetermined member rank update timing (for example, once every three months), the user's store use history registered in the store use history database 70, and the results on the restaurant information providing site ( The member rank of the user is set using the number of comment posts, the number of fan registrations, the number of browsing, etc., and the member rank registered in the user database 20 is updated. In addition, the data update unit 12 has a predetermined point update timing (for example, every time the use record is registered), the use record, the record on the restaurant information providing site (the number of comments posted, the number of fans registered, the number of browsing times). Etc.), points are given to the user of the user terminal 3. In this case, the data update unit 12 updates the user points registered in the user database 20. In addition, the results (the number of comment postings, the number of fan registrations, the number of browsing, etc.) on the restaurant information providing site of each user terminal 3 are stored in a predetermined area of the storage unit 14.

  In addition, the data updating unit 12 refers to the store use history database 70 every predetermined period (for example, once every six months) and clears the conditions based on the conditions determined for each member rank (the conditions are satisfied). B) Bonus points are given to users who have a history of use (user terminal 3). With this configuration, the user is encouraged to use the restaurant.

  Moreover, the data update part 12 may be comprised so that a time-limited point (point which expires automatically when an expiration date passes) may be provided to a user. And when a user has a plurality of point-limited points, it is consumed preferentially from the one with the near expiration date.

  In addition, when the number of fans of the user is updated or when the user is registered at the top of the gourmet ranking, the mail processing unit 13 generates an e-mail notifying the user, An electronic mail is transmitted to the terminal 3. Further, when the expiration date of the limited time point given to the user approaches, the mail processing unit 13 generates an email indicating that the expiration date is imminent and transmits the email to the user terminal 3. It has become.

  Next, each database (user database 20, user attribute database 30, my restaurant database 40, menu posting database 50, fan registration database 60, store use history database 70, store database 80, member benefits stored in the storage unit 14 is stored. The data structure of the table 90) will be described with reference to FIGS. Here, FIG. 2 is a schematic diagram showing an example of the data structure of the user database of the present embodiment. FIG. 3 is a schematic diagram showing an example of the data structure of the first database constituting the user attribute database of this embodiment. FIG. 4 is a schematic diagram showing an example of the data structure of the second database constituting the user attribute database of this embodiment. FIG. 5 is a schematic diagram showing an example of a data structure of a third database constituting the user attribute database of the present embodiment. FIG. 6 is a schematic diagram showing an example of the data structure of the fourth database constituting the user attribute database of the present embodiment. FIG. 7 is a schematic diagram showing an example of the data structure of the my restaurant database of the present embodiment. FIG. 8 is a schematic diagram showing an example of the data structure of the menu posting database of the present embodiment. FIG. 9 is a schematic diagram showing an example of the data structure of the fan registration database of the present embodiment. FIG. 10 is a schematic diagram showing an example of the data structure of the store use history database of the present embodiment. FIG. 11 is a schematic diagram showing an example of the data structure of the store database of the present embodiment. FIG. 12 is a schematic diagram showing an example of the data structure of the member privilege table of the present embodiment.

  First, the user database 20 will be described. The user database 20 is a database in which information about registered users is registered. Specifically, as shown in FIG. 2, the user database 20 includes a field 201 for registering a user ID (user identification information) for identifying a registered user, a field 202 for registering a user name, and the user. A field 203 for registering the member rank, a field 204 for registering the number of points acquired by the user, a field 205 for registering the number of browsed information (number of views) published by the user, and the user A field 206 for registering the number of members who are fans, a field 207 for registering the gourmet ranking of the user, a field 208 for registering a comment (text information) of the user's self-introduction, and the public information of the user A field 209 for registration and a field for registering the mail address of the user. One record and a Rudo 210 are configured. In the actual user database 20, in addition to the above, an authentication password, a user address, and the like are registered. In the field 204, the above-mentioned limited time points are registered separately from normal points.

  The “user ID (member number)” registered in the field 201 refers to unique text information (information such as alphanumeric characters) given to the registered user. “User name” refers to text information indicating a user name (such as a nickname) of a user ID registered in the field 201. The “member rank” means any one of five predetermined ranks (regular member, bronze member, silver member, gold member, platinum member). As described above, the data update unit 12 determines the member rank based on the user's restaurant / EC site usage record, the number of comments posted, the number of public information, and the like at a predetermined member rank update timing. Assign. Note that the user at the time of membership registration is set to “regular member”.

  In addition, “Points” are given when using restaurants or posting comments, etc., and purchase products on affiliated EC sites or use affiliated restaurants and stores. It can be used for discount services, etc. The “Gourmet Ranking” is a ranking based on the usage of restaurants and EC sites, the number of comments posted, the number of public information, etc., among the users registered as members of the restaurant information providing site. . For example, the data updating unit 12 ranks the fields based on the usage results of restaurants and EC sites, the number of comment posts, the number of public information, etc. at predetermined timings. The data 207 is updated.

  “Public information” is information that the user of the user terminal 3 has made public to other members. In the present embodiment, a case where three types of information “my restaurant, recommended menu, preference”, which will be described later, is disclosed is taken as an example. Of the three types of information, only information set to be disclosed by the user is registered in the field 209. The “mail address” is the “mail address” of the user terminal 3, and the mail processing unit 13 updates the number of fans of the user with respect to the user terminal 3 or registers it at the top of the gourmet ranking. It is used as the destination of e-mails sent in the case of

  Next, the user attribute database 30 will be described. This user attribute database 30 is for registering the attribute information of the user who has registered as a member (information indicating the user's preference regarding eating and drinking), and is composed of four databases, a first database 30a to a fourth database 30d. ing.

  Information registered in the user attribute database 30 is registered in the server device 1 when the user terminal 3 is registered as a member. Specifically, when the user of the user terminal 3 registers as a member, the information providing unit 11 of the server device 1 registers information registered in each field of the first database 30a to the fourth database 30d in the user terminal 3. Provide an input screen. The user terminal 3 can input information registered in each field of the first database 30a to the fourth database 30d to the server device 1 by selecting each item on the input screen or inputting data. It has become. In this embodiment, for convenience of explanation, the user attribute database 30 is configured by four databases. However, the user attribute database 30 may be configured as one database.

  Specifically, as shown in FIG. 3, the first database 30 a constituting the user attribute database 30 includes a field 301 for registering a user ID, a field 302 for registering the “secretary degree” of the user, and a field 302. The field 303 for registering whether or not to disclose the “secretary degree” registered in the field, the field 304 for registering the user's “frequently visited area”, and the “frequently visited area” registered in the field 304 are disclosed. One record is configured with a field 305 for registering whether or not. In the fields 303 and 305, either “public” or “private” is registered.

  Here, the above-mentioned “secretary level” is a percentage value indicating that it is suitable for a secretary (experience of secretary), and the higher the value, the more suitable for the secretary ( Has a lot of secretary experience). Therefore, the user can obtain information useful for selecting a store by referring to store information such as a my restaurant list registered by a person with a high secretary value among other members. It should be noted that the secretary level of each user is disclosed to other members only for those users whose “public” is registered in the field 303. In addition, only the area of the user whose “public” is registered in the field 305 is frequently disclosed to other members.

  As shown in FIG. 4, the second database 30b constituting the user attribute database 30 is a field 306 for registering a user ID, and information indicating the interest / interest (preference) of the user's restaurant genre with numerical values. The fields 307, 308, 309, 310, 311, 312, and 313 for registering (information indicated by 0 to 400) and the interests / interests for the restaurant genres registered in the fields 307 to 313 are indicated by numerical values. One record is configured with a field 314 for registering whether to disclose information. In the field 314, either “public” or “private” is registered. Also, the information indicating the interest / interest in the restaurant genre registered in the fields 307 to 313 is disclosed to other members only for the user whose “public” is registered in the field 314.

  Here, in the fields 307, 308, 309, 310, 311, 312, and 313, “Class B gourmet”, “Japanese food”, “Italian”, “Sweets cafe”, “Ramen”, “Curry”, Information indicating the interests and preferences (preferences) related to “Chinese Chinese” in numerical values is registered. The numerical value indicates that the higher the value is, the higher the interest of the restaurant genre is. The genres of restaurants registered in the fields 307 to 313 (“Class B gourmet”, “Japanese food”, “Italian”, “Sweets cafe”, “Ramen”, “Curry”, “Chinese”) are: It is just an example.

  As shown in FIG. 5, the third database 30c constituting the user attribute database 30 is a field 315 for registering a user ID and a user's interest / interest (preference) for the beverage genre (beverage type) by numerical values. Fields 316, 317, 318, 319, 320 for registering the indicated information (information indicated by 0 to 400) and information indicating the interest / interest for the beverage genre registered in the fields 316 to 320 in numerical values. One record is configured with a field 321 for registering whether to disclose or not. In the field 321, “public” or “non-public” is registered. In addition, information indicating interest / interest in the beverage genre registered in the fields 316 to 320 is disclosed to other members only for the users whose “public” is registered in the field 321.

  Here, in the fields 316, 317, 318, 319, and 320, the interests / interests (preferences) about “beer”, “shochu”, “cocktail”, “wine”, and “makikori” are indicated by numerical values, respectively. Information is registered. Moreover, the said numerical value has shown that the interest of the genre of the drink is so high that a value is high. The types of beverages to be registered in the fields 316 to 320 (“beer”, “shochu”, “cocktail”, “wine”, “makikori”) are merely examples.

  Further, as shown in FIG. 6, the fourth database 30 d constituting the user attribute database 30 includes a field 322 for registering a user ID, and information (in a range of 0 to 500) indicating the user's food preference and taste preference. Field 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 333, 334, 335, and the user's food preference / taste registered in the fields 323-335. One record is configured with a field 336 for registering whether or not to disclose information indicating the preference of the user as a numerical value. In the field 336, either “public” or “private” is registered. In addition, information indicating the food preference / taste preference registered in the fields 323 to 335 is disclosed to other members only for users whose “public” is registered in the field 336.

  Here, in the fields 323, 324, 325, 326, 327, 328, 329, 330, 331, 332, 333, 334, and 335, respectively, “Stick”, “Lightly”, “Sour”, “Sweat”, Numerical value of preference for “sweet”, “spicy”, “fish lover”, “meat lover”, “vegetable lover”, “fruit lover”, “oyster lover”, “boiled lobster lover”, “noodle lover” The information indicated by is registered. For example, in the illustrated example, “500” is registered in “Sour” in the field 325. This also indicates that the user likes the “sour” taste. In the field 327, “50” is registered in “sweet”. This indicates that the user dislikes the “sweet” taste. Items related to food taste / taste registered in the fields 323 to 335 ("Koriteri", "Asari", "Surpur", "Shoppai", "Sweet", "Spicy", "Fish lover", "General meat") , “Vegetables”, “fruit lovers”, “oyster lovers”, “boiled lobster lovers”, “noodle lovers”) are just examples.

  Next, the my restaurant database 40 will be described. This my restaurant database 40 is a database in which store information of restaurants with bookmarks as stores of interest to the user is registered. Data registered in the my restaurant database 40 is registered at a timing when the user terminal 3 selects a store as a store of interest on the restaurant information providing site. That is, when providing the restaurant information providing site to the user terminal 3, the information providing unit 11 receives a request from the user terminal 3 to register the store on the restaurant information providing site in the my restaurant. Store information of the requested store is registered in the restaurant database 40.

  Specifically, as shown in FIG. 7, the my restaurant database 40 includes a field 401 for registering a user ID, a field 402 for registering a store ID, a field 403 for registering an area where a restaurant is located, and a restaurant. One record is configured to include a field 404 for registering the type of business, a field 405 for registering the category of the restaurant to be registered, and a field 406 for registering whether or not to disclose the user's my restaurant data. In the field 406, either “public” or “private” is registered. Further, the store information registered in the fields 402 to 405 is disclosed to other members only for the users whose “public” is registered in the field 406.

  Here, the “store ID” registered in the field 402 is unique text information (information such as alphanumeric characters) given to the store registered in the restaurant information providing site, and is registered in the store database 80 described later. Is the same as The “area” and “business type” registered in the fields 403 and 404 are the same as those registered in the store database 80 described later. The “category” registered in the field 405 is an item provided so that the user can classify and manage the my restaurant list. In the illustrated example, either “I want to go” or “I want to go again” is registered. Thereby, the user can classify and register “restaurants to go” and “restaurants to go to”.

  Next, the menu posting database 50 will be described. The menu posting database 50 is a database in which menu information posted by the user is registered. Data registered in the menu posting database 50 is registered at a timing when the user terminal 3 makes a posting regarding a recommended menu on the restaurant information providing site. That is, when the information providing unit 11 provides a restaurant information providing site to the user terminal 3 and receives a posting request regarding a recommended menu from the user terminal 3, the information providing unit 11 requests the menu posting database 50 to make the request. The posting information of the menu is registered.

  Specifically, as shown in FIG. 8, the menu posting database 50 registers a field 501 for registering a user ID, a field 502 for registering a store ID, and a store menu of the store ID registered in the field 502. One record is made up of a field 503 for registering, a field 504 for registering a comment for the menu registered in the field 503, and a field 505 for registering whether or not to disclose the menu posted by the user. In the field 505, either “public” or “private” is registered. In addition, information registered in the fields 502 to 504 is disclosed to other members only for users whose “public” is registered in the field 504.

  Next, the fan registration database 60 will be described. The fan registration database 60 is a database in which information for identifying members selected as fans by the user is registered. Data registered in the fan registration database 60 is registered at a timing when the user terminal 3 selects an interested member as a fan on the restaurant information providing site. That is, when providing the restaurant information providing site to the user terminal 3, the information providing unit 11 receives a request to register the member displayed on the restaurant information providing site with the fan from the user terminal 3. In the fan registration database 60, the requested member information is registered.

  Specifically, as shown in FIG. 9, the fan registration database 60 includes a field 601 for registering a user ID, and a field 602 for registering a user ID of another user (member) registered as a fan by the user. One record is formed. In the fan registration database 60, a predetermined number of members (for example, 10 members) can be registered for each user (one user ID).

  Next, the store use history database 70 will be described. The store use history database 70 is a database for registering the use history of the user's registered store (store listed on the restaurant providing site) and the EC site. The data registered in the store usage history database 70 is that the server device 1 sends the “user usage record (use date, member user name (user ID), store name (store ID)” transmitted from the store terminal 5. , Accounting amount) ”. In other words, the data update unit 12 receives the usage record (the date of use, the user name (user ID) of the member, the store name (store ID) accounting amount) transmitted from the store terminal 5 via the communication network NW. Then, the accepted usage record is registered in the store usage history database 70.

  Specifically, as illustrated in FIG. 10, the store use history database 70 registers a field 701 for registering a user ID, and the date and time when the user used the store (or EC site) (paid payment). One record includes a field 702, a field 703 for registering a store ID for identifying a store (or EC site) used by the user, and a field 704 for registering the user's payment amount.

  Next, the store database 80 will be described. The store database 80 is a database in which store information about stores introduced on the restaurant information providing site is registered. The store database 80 is registered in the storage unit 14 by the operator of the server device 1 when the server device 1 is set. The store database 80 is updated at a predetermined timing by the operator.

  Specifically, as shown in FIG. 11, the store database 80 includes a field 801 for registering a store ID, a field 802 for registering a store name, a field 803 for registering the location (address) of the store, A field 804 for registering an area (Shinjuku, Ginza, etc.), a field 805 for registering a store telephone number, a field 806 for registering a store URL, a field 807 for registering a store business type, One record includes a field 808 for registering a menu to be provided. In addition to the above, the actual store database 80 stores store characteristics, PR documents, and the like, but is simplified for convenience of explanation.

  Next, the member privilege table 90 will be described. The member privilege table 90 shows the privileges provided for each member rank. When the information providing unit 11 guides the member privileges to the user terminal 3, or when the data updating unit 12 updates the member's points. It has come to be used. In this embodiment, “platinum member” has the highest member rank (user rank), and the member ranks are “gold member”, “silver member”, “bronze member”, and “regular member” in this order. It's down.

  Specifically, as shown in FIG. 12, the member privilege table 90 is registered in association with a privilege to be provided for each member rank. The regular member is associated with “birthday gift (giving 100 points for the month of birth)” and “e-mail magazine for regular members”. In addition, “birthday gifts (100 points are given for the month of birth)”, “mail magazine for bronze members”, and “special offer campaigns (visit points twice a month)” are associated with bronze members. In addition, “birthday gifts (100 points are given for the month of birth)”, “silver mail e-mail magazine”, and “special offer campaign (visit points for visits 5 times a month)” are associated with silver members. Gold members also have a “Birthday Gift (100 points for the month of birth)”, “Gold Member Mail Magazine”, “Special Offer Campaign (Points to visits 10 times a month)” and “Eligible to participate in affiliates” Associated. Platinum members can also receive “Birthday gifts (100 points for the month of birth)”, “Platinum e-mail magazine”, “Special offer campaign (visit points 10 times a month)”, “Eligible to participate in affiliates” "Platinum card presentation", "Platinum card 1 year keeps a privilege", "Member party invitation" are associated. Thus, in this embodiment, as the member rank increases, the benefits and services that are granted increase. Thereby, the incentive for raising a member rank is provided to the user who registered as a member.

  Next, the function in which the server apparatus 1 of this embodiment provides restaurant information to the user terminal 3 will be described with reference to FIGS. Here, FIG. 13 is a schematic diagram illustrating an example of a main page of a store information providing site provided to the user terminal by the server device of the present embodiment. FIG. 14 is a schematic diagram showing an example of an information presentation page related to a person who has a similar preference to the user of the store information providing site provided to the user terminal by the server device of the present embodiment. FIG. 15 is a schematic diagram showing an example of a my restaurant introduction page of an information providing site provided to the user terminal by the server device of the present embodiment. FIG. 16 is a schematic diagram showing an example of the menu ranking presentation page of the information providing site provided to the user terminal by the server device of the present embodiment.

  First, the user terminal 3 accesses the server device 1 via the communication network NW, and requests the server device 1 to present a restaurant information providing site. When receiving the presentation request, the information providing unit 11 of the server device 1 transmits a Web page (not shown) including a login screen to the user terminal 3. The user terminal 3 inputs the assigned user ID and user name (or authentication password) on the Web page including the login screen (transmits the user ID and authentication password to the server device 1).

  Then, the server device 1 performs user authentication using the input “user ID and user name” and the user database 20. If the input user ID and user name are correct (if the user database 20 has a record that matches the input user ID and user name), the server device 1 authenticates that the user is a member, and the user A web page (image information) constituting a restaurant search site for the user is generated, and the generated web page is transmitted to the user terminal 3. Specifically, the information providing unit 11 uses the user database 20 and the user attribute database 30 to generate the web page 100 (see FIG. 13) that constitutes the main page of the restaurant information providing site, and sends it to the user terminal 3. Send. When the user terminal 3 receives the Web page 100 as the main page, the user terminal 3 displays the Web page 100 on the display unit. In addition, if the input user ID and user name are not correct (if there is nothing that matches the user database 20), the server device 1 provides the user terminal 3 with a restaurant information site that is not dedicated to members. However, a case where the user terminal 3 is logged in as a member will be described below.

  Here, the Web page 100 is presented with an area 101 in which the user's member rank is presented, a privilege guidance button 102 for accepting a privilege guidance given to the member rank given to the user, and the current point of the user. An area 103, a menu column 104 that accepts content provided on a restaurant information providing site, an area 105 that presents user preference information that graphs user preferences (user preferences related to eating and drinking), and a list of my restaurants Reception button 106 and a reception button 107 for receiving a menu ranking display.

  The user of the user terminal 3 can confirm his / her member rank based on the data presented in the area 101. In addition, the user can confirm the points acquired by the user based on the data presented in the area 103. In the Web page 100, a privilege guide button 102 is provided near the lower side of the area 101 indicating the user's member rank. Therefore, the content of the privilege provided to the user can be effectively guided. Note that the user's membership rank and points presented in the areas 101 and 103 are extracted from the user database 20.

  Further, when the user terminal 3 selects (clicks) the privilege guidance button 102 on the Web page 100, a privilege introduction page (image information) that introduces a member-oriented privilege set for the user on the display unit of the user terminal 3. (Not shown)) is displayed.

  Specifically, when the user terminal 3 selects (clicks) the privilege guidance button 102, a privilege guidance request for each member is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the privilege guidance request, the information providing unit 11 refers to the member privilege table 90, generates a privilege introduction page that introduces the privilege of the member rank of the user who has requested the privilege guidance, and provides the user terminal 3 with the privilege. Send an introduction page. For example, in the example shown in the figure, since the user is presented as a platinum member in the area 101, a privilege introduction page for platinum members is transmitted to the user terminal 3. In addition, on the privilege introduction page, a privilege granted to a member higher than the user may be introduced to make the user aware of raising the member rank.

  Further, the user's preference and popularity ranking are presented in the area 105 of the Web page 100. Specifically, the area 105 is provided with a presentation column 110 for information related to user popularity (popularity from other members). In the presenting column 110, “the number of browsing information related to the store that is disclosed by the user”, “the number of members who have the user as a fan”, and “the popularity ranking of the user” are presented. The information displayed in the presentation column 110 is extracted from the user database 20 (fields 205, 206, and 207).

  Further, in the area 105, the managerial degree graph 120 showing the degree of managerial work of the user (the managerial degree explained in FIG. 3), the area graph 121 showing the area where the user frequently goes, and the user's interest / interest A restaurant graph 122 showing the genre of a restaurant as a graph, a beverage graph 123 showing a genre of a beverage that the user is interested in, and a food preference / taste graph showing the user's food preference / taste in a graph 124. Each graph (secretary degree graph 120, area graph 121, restaurant graph 122, beverage graph 123, food preference / taste graph 124) is created by the information providing unit 11 using data in the user attribute database 30. . Thereby, the user can grasp | ascertain the tendency of his preference visually easily. For example, an efficient restaurant search can be performed by searching for restaurants under search conditions that suit their preferences.

  In addition, buttons (public / private buttons) 120a, 121a, 122a are located near each graph (secretary level graph 120, area graph 121, restaurant graph 122, beverage graph 123, food preference / taste graph 124). , 123a, 124a are provided. When each graph (secretary degree graph 120, area graph 121, restaurant graph 122, beverage graph 123, food preference / taste graph 124) is not disclosed, each button 120a, 121a, 122a, 123a, 124a is clicked. And each preference of the user is made open to other members. On the other hand, in the state where each graph (secretary degree graph 120, area graph 121, restaurant graph 122, beverage graph 123, food preference / taste graph 124) is open, each button 120a, 121a, 122a, 123a, 124a is clicked. Then, each preference of the user is not disclosed to other members (will not be disclosed).

  For example, when the button 124 a is clicked in a state where the food preference / taste graph 124 is not disclosed, a food preference / taste graph publication request is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the food preference / taste graph disclosure request, the information providing unit 11 registers the disclosure in the field 336 (see FIG. 6) of the user attribute database 30. In addition, the information providing unit 11 registers the preference (food preference / taste) in the field 209 (see FIG. 2) of the user database 20. On the other hand, when the publish button 124 a is clicked in the state where the food preference / taste graph 124 is open, a request for non-disclosure of food taste / taste graph is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the food preference / taste graph non-disclosure request, the information providing unit 11 registers non-disclosure in the field 336 (see FIG. 6) of the user attribute database 30. Further, the information providing unit 11 deletes the preference (food preference / taste) registered in the field 209 (see FIG. 2) of the user database 20.

  Thus, according to this embodiment, the user can present his / her preference tendency to other members. In addition, the user can refer to the preferences of other members (members set to disclose preferences) other than the user.

  The area 105 is provided with a reception button 112 for receiving a search for members having similar preferences to the user and a fan list reception button 113 for displaying a list of other members registered as fans by the user. When this acceptance button 112 is clicked, a member introduction page (image information) displaying a list of members having similar preferences to the user is displayed on the user terminal 3. Specifically, when the user button 3 is clicked on by the user of the user terminal 3, the user terminal 3 requests the information providing unit 11 to search for a member having a preference similar to the user (preference similar member search request). ) Is sent. Upon receiving the preference similar member search request, the information providing unit 11 extracts a record of the user ID of the user from the user attribute database 30, and searches for a record in which data similar to the extracted record is registered. . Further, the information providing unit 11 extracts a predetermined number of cases searched for similarity (for example, 10 records from the top in the order of similarity). And the information provision part 11 produces | generates the member introduction page 130 shown in FIG. 14 using the predetermined number of records searched as similar, and the user database 20, and transmits to the user terminal 3. FIG. The member introduction page 130 is displayed on the display unit of the user terminal 3. Thereby, enjoyment other than shop search is provided to the user. For the similarity determination, a known technique is used (for example, a numerical value registered in each record of the user attribute database 30 is expressed by a vector, and a similarity between records is calculated by a similarity between vectors). .

  The member introduction page 130 shown in FIG. 14 is provided with member introduction fields 131a, 131b, and 131c that introduce members having similar preferences to the user who clicks the accept button 112, and lists members who have similar preferences to the user. It is displayed. Each member introduction column 131a, 131b, 131c presents “member name” and “member self-introduction comment” as well as a presentation request button 132 and a fan registration request button for information published by the member. 133 is provided. When the user terminal 3 clicks the presentation request button 132 on the member introduction page 130, the corresponding member information is presented.

  The presentation request buttons 132 in the member introduction fields 131a, 131b, and 131c are for users who have registered information that discloses each data in each database (user attribute database 30, my restaurant database 40, menu posting database 50). Only things are displayed. As for preferences, in the user attribute database 30, “secretary level”, “frequently visited area”, “restaurant genre with interest / interest”, “beverage genre with interest / interest” and “food preference / taste” Although “public / non-public” is set for each of these, in this embodiment, if there is even one that is set as public, the button 132c is displayed.

  For example, it is assumed that the user of the user terminal 3 clicks the presentation request button 132a in the member introduction column 131a. In this case, a user's my restaurant presentation request of the member introduction column 131 a is transmitted from the user terminal 3 to the information providing unit 11. When the information providing unit 11 receives the my restaurant presentation request, the information providing unit 11 accesses the my restaurant database 40, generates a my restaurant introduction page that introduces the user's (other members) my restaurant in the member introduction column 131a, and a user terminal. 3 to send. On the user terminal 3, a My Restaurant introduction page registered by another member who has similar preferences to the user is presented. Thus, when selecting a store, the user can browse restaurant information registered as a store in which a member who has a preference similar to that of the user is interested, so that an efficient store search can be performed.

  Further, for example, it is assumed that the user of the user terminal 3 clicks the presentation request button 132b in the member introduction column 131a. In this case, a user recommended menu presentation request in the member introduction field 131 a is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the recommended menu presentation request, the information providing unit 11 accesses the menu posting database 50, generates a menu introduction page that presents the recommended menu of the user (other member) in the member introduction column 131a, and the user terminal 3 Send to. The user terminal 3 is presented with a menu introduction page of another member who has similar preferences to the user. Thereby, when selecting a store, the user can browse information indicating a favorite menu of a member whose preference is similar to that of the user, so that the user can refer to the store selection.

  Further, for example, assume that the user of the user terminal 3 clicks the presentation request button 132c in the member introduction column 131a. In this case, a user preference presentation request in the member introduction field 131 a is transmitted from the user terminal 3 to the information providing unit 11. When the information providing unit 11 receives the preference presentation request, the information providing unit 11 accesses the user attribute database and presents the preference introduction page (the contents of the area 105 in FIG. 13 are presented) that presents the preference of the user (other member) in the member introduction column 131a. Generated image information) is generated and transmitted to the user terminal 3. The user terminal 3 is presented with a preference introduction page of another member who has similar preferences to the user. As a result, it is possible to confirm which part of the other members selected as having similar preferences to the user is similar to the user.

  When the user of the user terminal 3 clicks the fan registration request button 133 on the member introduction page 130, fan registration request information is transmitted from the user terminal 3 to the information providing unit 11. When receiving the fan registration request information, the information providing unit 11 accesses the fan registration database 60 and associates the user ID of the user of the user terminal 3 with the user of the member introduction page 130 (other user). Register the ID. In this way, the user can determine whether or not to register the member as a fan after referring to the public information of the member whose preference is similar to that of the user. Note that the user of the user terminal 3 can acquire the registered member list as a fan from the server device 1 by clicking the fan list reception button 113 on the Web page 100 (FIG. 13). .

  Next, returning to FIG. 13, the my restaurant list display function of the information providing unit 11 will be described. The information providing unit 11 has a my restaurant function that can be registered by category as a my restaurant if there is a store that the user is interested in in the store information introduced on the restaurant information providing site. When the information providing unit 11 accepts bookmark registration for the searched store from the user terminal 3 on the search screen (not shown), the information providing unit 11 accesses the my restaurant database 40 and accepts the registration in association with the user ID of the user. Store information (store ID, area, business type, category, open / closed) is registered. The information providing unit 11 specifies “category” and “public / private” from the user terminal 3 when accepting the bookmark registration, for example.

  When the selection of the accept button 106 is accepted from the user terminal 3 on the Web page 100 shown in FIG. 13, the my restaurant list display request is transmitted from the user terminal 3 to the information providing unit 11. When the information providing unit 11 receives the my restaurant list display request, the information providing unit 11 accesses the my restaurant database 40 (see FIG. 7), generates a my restaurant introduction page 140 shown in FIG. 15, and transmits it to the user terminal 3. Thereby, the my restaurant display introduction page 140 is displayed on the display unit of the user terminal 3.

  In addition, a public acceptance button 141 is provided on the illustrated my restaurant display introduction page 140. When the public acceptance button 141 is clicked by the user terminal 3, the my restaurant registered by the user can be disclosed to other members. Specifically, when this button 141 is clicked, the user restaurant 3 transmits the my restaurant publication request to the information providing unit 11. Upon receiving the My Restaurant publishing request, the information providing unit 11 accesses the My Restaurant database 40 (see FIG. 7) and publishes it in the field 406 of the record in which the user ID of the user transmitted by the My Restaurant publishing request is registered. Register. In addition, the information providing unit 11 accesses the user database 20 and adds “My Restaurant List” to the field 209 of the record in which the user ID of the user transmitted by the My Restaurant publishing request is registered.

  Moreover, the information provision part 11 can accept registration of a user's recommendation menu from the user terminal 3 in a restaurant information provision site. Specifically, the information providing unit 11 receives recommended menu information (store name (and store ID), menu, comment on the menu, designation of disclosure / non-disclosure) from the user terminal 3 on a reception screen (not shown). Can be done. The received menu information is registered in the menu posting database 50 (see FIG. 8) in association with the user ID of the user terminal 3 that transmitted the menu information.

  When the selection of the accept button 107 is accepted from the user terminal 3 on the Web page 100 shown in FIG. 13, the display request for the menu is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the menu display request, the information providing unit 11 accesses the menu posting database 50 (see FIG. 8), generates the menu introduction page 150 shown in FIG. 16, and transmits it to the user terminal 3. As a result, the menu introduction page 150 is displayed on the display unit of the user terminal 3.

  The menu introduction page 150 shown in the figure is provided with a public acceptance button 151. When the public acceptance button 151 is clicked by the user terminal 3, the menu registered by the user can be disclosed to other members. Specifically, when this button 151 is clicked, a menu publication request is transmitted from the user terminal 3 to the information providing unit 11. Upon receiving the menu publication request, the information providing unit 11 accesses the menu posting database 50 and registers publication in the field 505 of the record in which the user ID of the user who transmitted the menu publication request is registered. The information providing unit 11 accesses the user database 20 and adds “recommended menu” to the field 209 of the record in which the user ID of the user transmitted by the menu publication request is registered.

  As described above, according to the present embodiment, it is possible to publish to other members (my information can be transmitted) my restaurants and recommended menus registered as stores that the user registered as a member is interested in. In addition, you can browse My Restaurant and recommended menus registered as shops that other members are interested in, so when choosing a store, refer to the store's reputation as well as information sent from the store. be able to.

  Moreover, according to this embodiment, the user who becomes a member registers the preference (user attribute information) regarding his / her restaurant, and the preference regarding the restaurant is displayed in a graph. Therefore, the user can grasp | ascertain the preference regarding own restaurant easily. In addition, according to the present embodiment, the user can search for a member similar to his / her preference, and can browse a recommended menu of a member whose preference is similar to the user's preference or a shop of interest. . That is, in selecting a store, a user who has similar preferences to the user can refer to a store or menu that the user likes. Therefore, a store that suits his / her preference can be efficiently selected. Moreover, according to this embodiment, on the Web page which is a main page, while showing a user's member rank and a point, the guidance request | requirement of the privilege for the user is received. Therefore, according to this embodiment, the user can be prompted to acquire or use points.

  In addition, this invention is not limited to embodiment mentioned above, A various change is possible within the range of the summary. For example, in the above-described embodiment, the data registered in the user attribute database 30 is set when the user registers as a member. However, the present invention is not particularly limited to this. For example, the data updating unit 12 may update frequently used area information from the address of the actually visited store by using data registered in the store use history database 30 (store use history database 30). The information in the field 304 may be updated).

DESCRIPTION OF SYMBOLS 1 ... Server apparatus, 3 ... User terminal, 5 ... Store terminal, 10 ... Control part, 11 ... Information provision part, 12 ... Data update part, 13 ... Mail processing part, 14 ... Memory | storage part, 20 ... User database, 30 ... User attribute database, 40 ... My restaurant database, 50 ... Menu posting database, 60 ... Fan registration database, 70 ... Store usage history database, 80 ... Store database, 90 ... Member benefit table

Claims (6)

A server device connected to a plurality of user terminals via a network and providing store information to each user terminal,
For each identification information for identifying a user of a user terminal, a user attribute database that associates preference information indicating the preference of the user,
An information providing unit that generates image information for a user of the user terminal using the user attribute database in response to a request from the user terminal, and transmits the image information to the user terminal;
The server information characterized in that the image information includes user preference information that shows a graph of user preferences of the user terminal. For each of the identification information, a user registration database in which information related to a store selected and registered by the user specified by the identification information is associated,
The information providing unit is configured to be able to accept a presentation request for information related to other users having similar preferences to the user of the user terminal from the user terminal on the image information, and receives the presentation request. The user attribute database is provided with an introduction page for selecting another user having a similar preference to the user of the user terminal and introducing the selected user to the user terminal, and the user registration database. A server device characterized in that information relating to a store registered by another user introduced on the introduction page can be selected and provided to the user terminal. The information related to the store selected and registered by the user includes at least one of store information introducing the store selected by the user and menu information introducing a menu provided by the store posted by the user. The server device according to claim 2, wherein: The preference information includes at least restaurant area information used by the user, restaurant preference information indicating preference for each genre of the restaurant, beverage preference information indicating taste for each type of beverage, taste, and each ingredient. 4. The server device according to claim 2, wherein any one of the food preference / taste information indicating the preference of the user is included. For each of the identification information, a user database that associates a point given to a user specified by the identification information with a user rank set for the specified user;
For each user rank, a user privilege table that registers privilege information provided to users of that rank, and
The image information includes a user button of the user terminal, a user rank set for the user, and a reception button for receiving an introduction of a privilege for the user rank,
When the acceptance button is selected by the user terminal, the information providing unit uses the user database and the user privilege table to present a user privilege for a user rank set for the user of the user terminal. The server apparatus according to claim 1, wherein a page is generated and the user privilege page is transmitted to the user terminal. The point includes an expiration date, and includes a limited time point that automatically expires after the expiration date,
Furthermore, when the expiration date of the limited time point assigned to the user of the user terminal approaches, an email processing unit that generates an email indicating that the expiration date is near and transmits the email to the user terminal The server device according to claim 5, further comprising:

Images