Patent ID: 12229820

MODE(S) FOR CARRYING OUT THE INVENTION

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[System Configuration]

FIG.1is a diagram showing a configuration of a restaurant information providing system according to this embodiment.

As shown in the figure, this system includes a restaurant information providing server100on the Internet50, a plurality of user terminals200, a plurality of restaurant terminals300, and an e-commerce (EC) server400.

The restaurant information providing server100is a webserver that operates a portal site on which restaurant-related information is placed. The restaurant information providing server100is connected to the plurality of user terminals200and the restaurant terminals300of a plurality of restaurants via the Internet50.

The restaurant information providing server100provides a search system of the restaurant information for users of the user terminals200on the portal site. Specifically, the restaurant information providing server100searches for restaurant information that matches a search condition on the basis of a search request from one of the user terminals200. Then, the restaurant information providing server100generates a webpage on which search results are placed and sends it to the user terminal200. Moreover, the restaurant information providing server100performs reservation reception processing on any restaurant from the user terminal200of the user who has viewed the restaurant information, in place of the user.

The user terminal200(200A,200B,200C . . . ) is a terminal used by a user. The user terminal200(200A,200B,200C . . . ) is a smartphone, a portable phone, a tablet personal computer (PC), a laptop PC, a desktop PC, or the like, for example. The user terminal200accesses the restaurant information providing server100, receives the webpage, and displays it on the screen through a browser or the like.

The user terminal200determines a restaurant search condition on the basis of a user's operation and sends a restaurant search request based on the search condition to the restaurant information providing server100. In this embodiment, the user of the user terminal200can send the search request by selecting a pre-set search condition such as a restaurant location (nearest station), a genre, prices, and the like. Then, based on a user's operation, the user terminal200is capable of sending a reservation request of any restaurant displayed as the search result to the restaurant information providing server100.

In order for the user to use various services such as restaurant reservation via the portal site, the user needs to have an account (ID) as a member of the service provided by the restaurant information providing server100and log in the portal site with the account. In a case where the user uses a predetermined service with the account, points depending on the contents of the service are given to (the account of) the user.

Moreover, on the other hand, the restaurant information providing server100provides a management screen (webpage) of the restaurant information for restaurants (member restaurants) to be placed on the portal site. Via the management screen, a user of the restaurant terminal300can edit and update the restaurant information on the webpage, which is provided to ordinary users as the search result, and upload that webpage to the portal site.

The restaurant terminal300(300A,300B,300C . . . ) is a terminal installed in each restaurant. The restaurant terminal300(300A,300B,300C . . . ) is a tablet PC, a laptop PC, a desktop PC, or the like. The restaurant terminal300is capable of executing processing on its own restaurant information in communication with the restaurant information providing server100on the basis of a manager's operation. The processing on its own restaurant information includes editing and updating the restaurant information.

Moreover, the EC server400provides an EC service for members like the restaurant information providing server100. For using the service provided by the EC server400, the user of the user terminal200needs to have an account as a member and log in the portal site with the account. Also in a case where the user uses a predetermined service with that account, points depending on the contents of the service are given to (the account of) the user.

In this embodiment, the restaurant information providing server100is capable of linking an account (hereinafter, a first account) for using a restaurant information providing service provided by the restaurant information providing server100and an account (hereinafter, a second account) for using the EC service provided by the EC server400by predetermined linking processing. Details of the linking processing will be described later.

Moreover, the restaurant information providing server100is capable of controlling points granting processing such that in a case where the user of the user terminal200uses the restaurant information providing service, points are given to either of the accounts in accordance with whether or not the first account and the second account have been linked.

[Hardware Configuration of Restaurant Information Providing Server]

FIG.2is a diagram showing a hardware configuration of the restaurant information providing server100. As shown in the figure, the restaurant information providing server100includes a central processing unit (CPU)11, a read only memory (ROM)12, a random access memory (RAM)13, an input/output interface15, and a bus14that connects them to one another.

The CPU11accesses the RAM13or the like as appropriate in a manner that depends on needs. Then, the CPU11comprehensively controls all the respective blocks of the restaurant information providing server100while performing various types of arithmetic processing. The ROM12is a nonvolatile memory in which an OS, firmware such as programs and various parameters to be executed by the CPU11are fixedly stored. The RAM13is used as a working area of the CPU11or the like and temporarily retains the OS, the running various applications, and various types of data being processed.

A display unit16, an operation receiving unit17, a storage unit18, a communication unit19, and the like are connected to the input/output interface15.

The display unit16is a display device using a liquid crystal display (LCD), an organic electroluminescence display (OELD), a cathode ray tube (CRT), or the like, for example.

The operation receiving unit17is a pointing device such as a mouse, a keyboard, a touch panel, and another input device, for example. In a case where the operation receiving unit17is a touch panel, the touch panel can be integral with the display unit16.

The storage unit18is a nonvolatile memory such as a hard disk drive (HDD), a flash memory (solid state drive (SSD)), and another solid-state memory, for example. The above-mentioned OS, various applications, and various types of data are stored in the storage unit18.

As will be described later, particularly in this embodiment, the storage unit18includes a restaurant information database, a user information database, and a reservation information database in addition to programs such as applications necessary for account linking processing to be described later.

The communication unit19is a network interface card (NIC) for Ethernet or various modules for wireless communication such as wireless LAN, for example. The communication unit19serves to perform processing of communication with the user terminals200.

It should be noted that, although not shown in the figure, the basic hardware configurations of the user terminal200and the restaurant terminal300are approximately similar to the hardware configuration of the restaurant information providing server100.

[Database Configuration of Restaurant Information Providing Server]

FIG.3is a diagram showing a configuration of databases of the restaurant information providing server100.

As shown in the figure, the restaurant information providing server100includes a restaurant information database31, a user information database32, and a reservation information database33in the storage unit18.

The restaurant information database31stores, for each restaurant, the name of that restaurant, location (address or latitude/longitude) information, area information, access information (nearest-station information, information regarding a walking distance from nearest station), a telephone number, an ID for identifying that restaurant (restaurant ID), category information of the type of operation and service of that restaurant, information for presenting that restaurant (information indicating features of the restaurant such as PR text of the restaurant, information regarding an event presented by the restaurant, and the like), image data related to the restaurant (presenting the restaurant), menu information related to menus offered by the restaurant, average budget information, and other information such as business hours and a website URL, and the like. Such information is input through the restaurant terminal300of each restaurant via the management screen provided by the restaurant information providing server100. Moreover, the restaurant information database31may store information (reservation list information) indicating reservation availability in each restaurant.

The menu information is information associated with menus to be placed on each restaurant site of the portal site. In the menu information, the menu names of a plurality of menus that each restaurant can offer are stored for each restaurant. The menu information may be stored for each menu category such as appetizer/main and lunch/dinner/course, for example. Moreover, besides as well as text information indicating the menu names, prices, descriptions, and the like, image information of photographs of the menus or the like is also stored as the menu information in association with them.

The area information includes information regarding a plurality of areas different in unit of area. Examples of a wide area can include prefectures and municipalities, examples of a narrow area can include an area within several hundreds of meters from the station (e.g., “Ginza area”), and examples of an intermediate wide area can include an area within 1 km from the station and an area group of a plurality of areas near the station (e.g., “Ginza, Shinbashi, and Yurakucho area”), though not limited thereto. That is, even the same restaurant is associated with a plurality of areas in a manner that depends on its unit of area.

The category information includes, for example, main categories such as Japanese cuisine, Chinese cuisine, Italian cuisine, French cuisine, and Yakiniku (BBQ) and may further include more specific sub-categories such as Yakitori (grilled meat and vegetables skewers), Tempura (deep fried shrimp and vegetables), and the like in Japanese cuisine and pasta, pizza, and the like in Italian cuisine.

The user information database32stores information regarding a user who possesses the user terminal200and is a user (member) of a restaurant information service via the portal site provided by the restaurant information providing server100. Specifically, the user information database32stores, for each user, information regarding a user ID, a password, the name, a mail address (information that can be another message destination), a telephone number, an address, age (group), sex, the date of birth, and the like. As the user ID, the user's mail address can be used in addition to any character string specified by the user.

Moreover, in a case where the second account linked to the first account exists, the user information database32also stores information (hereinafter, link information) regarding the second account in association with the user ID. The link information is stored in a case where a request to link to the second account is sent to the restaurant information providing server100from the user terminal200. Otherwise, in a case where a request to link the first account is sent from the user terminal200to the EC server400that manages the second account which is a linking destination, the linking information may be received and stored from the EC server400.

In addition, the user information database32also stores information regarding points given to the user. As information regarding those points, information regarding points given to the first account is stored in a case where the second account linked to the first account does not exist. Otherwise, in a case where the second account linked to the first account exists, information regarding points given to the second account as well as the points given to the first account are stored.

Moreover, even in a case where the second account linked to the first account exists, the user information database32may store only information regarding the points given to the first account and the EC server400or another server associated therewith may store the information regarding the points given to the second account.

The reservation information database33stores reservation information (e.g., restaurant name, reservation time, number of costomers, selected course, etc.) included in the reservation request of each restaurant, which has been received from the user terminal200via a predetermined reservation form or the like, in association with user information for identifying the user of the user terminal200.

Those databases are used by cross-referencing in the account linking processing to be described later in a manner that depends on needs, the account linking processing being performed by the restaurant information providing server100.

[Operation of Restaurant Information Providing Server]

Next, an operation of the restaurant information providing server100configured in the above-mentioned manner will be described. The operation is executed by cooperation between the hardware and the software, the hardware including the CPU11of the restaurant information providing server100and the communication unit19, the software being stored in the storage unit18. In the following description, it is assumed that the CPU11performs the operation for the sake of convenience.

FIG.4is a flowchart showing the flow of the account linking processing by the restaurant information providing server100.

As shown in the figure, the CPU11determines whether or not a reservation form screen of the restaurant has been accessed from the user terminal200in a state not logged in with the first account (Step41). The reservation form screen is accessed in such a manner that the user of the user terminal200presses any one of reservation buttons displayed in a restaurant information field of each restaurant on the portal site, for example.

In a case where the CPU11determines that the reservation form screen has been accessed (Yes), the CPU11generates a reservation form screen and sends the reservation form screen to the user terminal200(Step42).

FIG.5is a diagram showing an example of the reservation form screen sent to the user terminal200by the restaurant information providing server100and displayed on the user terminal200.

As shown in the figure, a reservation form screen50includes, for example, a name input field51for entering the name of a reservation person, a mail address input field52for entering the mail address of the reservation person, a telephone number input field53for entering the telephone number of the reservation person, and a reservation request button54for requesting a reservation on the basis of the information entered in each input field.

Subsequently, the CPU11determines whether or not the mail address as user identification information has been entered in the mail address input field52on the reservation form screen50(Step43). Here, whether or not the mail address has been entered may be determined by, for example, detecting that an input cursor has moved to another input field from the mail address input field52or detecting that the duration of a state in which a character is not entered is longer than or equal to a predetermined time (e.g., 10 seconds or the like) after the last character is entered in the mail address input field52.

In a case where the CPU11determines that the mail address has been entered (Yes), the CPU11inquires of the EC server400whether or not the second account associated with the mail address (account required for logging into the service provided by the EC server400) exists (Step44).

Subsequently, the CPU11determines whether or not a response indicating that the second account associated with the mail address exists has been received from the EC server400(Step45).

In a case where a response indicating that the associated second account does not exist has been received (No), the CPU11terminates the account linking processing.

On the other hand, in a case where the response indicating that the associated second account exists has been received (Yes), the CPU11determines whether or not a predetermined percentage or more of the input items other than the mail address has been entered on the reservation form screen50(Step46).

Here, the input items other than the mail address include the name entered in the name input field51and the telephone number entered in the telephone number input field53, which are described above, in this example. Examples of the predetermined percentage include 20%, 50%, 70%, and the like, though not limited thereto. In this example, in a case where, for example, 50%, i.e., one of the name and the telephone number, has been entered, it is determined that the predetermined percentage or more of the input items has been entered.

In a case where the CPU11determines that the predetermined percentage or more of the input items other than the mail address has been entered (Yes), the CPU11checks whether or not the first account associated with the mail address exists by referring to the user information database32(Step47).

In a case where the CPU11determines that the first account associated with the mail address exists (Yes), the CPU11generates an account log-in/linking suggestion dialog and sends the account log-in/linking suggestion dialog to the user terminal200for displaying the account log-in/linking suggestion dialog (Step48).

FIG.6is a diagram showing an example of the account log-in/linking suggestion dialog. As shown in the figure, an account log-in/linking suggestion dialog60is displayed superimposed on the reservation form screen50, for example.

The account log-in/linking dialog60includes character information indicating that the first account owned by the user can be linked to the second account and that linking of the account and log-in to the first account are suggested, a log-in/linking button61for requesting the linking and log-in, and a non-linking button62for returning to the reservation form screen50without linking.

The CPU11may generate display information for account log-in/linking suggestion not as a dialog but as a separate screen that transitions from the reservation form screen50.

Subsequently, the CPU11determines whether or not a request for log-in with the first account and linking of the first account and the second account have been received by the user of the user terminal200pressing the log-in/linking button61on the account log-in/linking dialog60(Step49).

In a case where the CPU11determines that the CPU11has received the log-in and linking request (Yes), the CPU11first sends a log-in screen with the first account to the user terminal200. When log-in information is entered by the user of the user terminal200and the log-in request has been received from the user terminal200, the CPU11causes the user terminal200to log in with the first account. Subsequently, in a case where the log-in is successful, the CPU11generates a linking processing execution screen for performing the linking processing of the first account and the second account and sends the linking processing execution screen to the user terminal200(Step50).

On the other hand, in a case where the CPU11determines that the first account associated with the mail address does not exist (No), the CPU11generates an account registration/linking suggestion dialog and sends the account registration/linking suggestion dialog to the user terminal200for displaying the account registration/linking suggestion dialog (Step51).

FIG.7is a diagram showing an example of the account registration/linking suggestion dialog. As shown in the figure, an account registration/linking suggestion dialog70is also displayed superimposed on the reservation form screen50, for example.

The account registration/linking suggestion dialog70has character information indicating that the first account and the second account can be linked when the first account has been registered and that the registration of the first account and the linking of the first account to the second account are suggested, a registration/linking button71for requesting registration/linking of the account, and a non-registration button72for returning to the reservation form screen50without registering/linking the account.

The CPU11may generate display information for the account registration/linking suggestion not as a dialog but as a separate screen for transitioning from the reservation form screen50.

Subsequently, the CPU11determines whether or not a request for registration of the first account and linking of the first account and the second account has been received in such a manner that the user of the user terminal200presses the registration/linking button71on the account registration/linking dialog70(Step52).

In a case where the CPU11determines that the CPU11has received the registration/linking request (Yes), the CPU11first sends a registration screen for the first account to the user terminal200. When the user of the user terminal200has entered registration information (user name, mail address, telephone number, and the like) and the CPU11has received a registration request from the user terminal200, the CPU11registers the registration information as first account information in the user information database32. Subsequently, the CPU11generates a linking processing execution screen for performing the linking processing of the registered first account and the second account, and sends the linking processing execution screen to the user terminal200(Step53).

FIG.8is a diagram showing an example of the linking processing execution screen. As shown in the figure, the CPU11sends a linking processing execution screen80to the user terminal200in a case where the log-in is successful in response to the log-in/linking request and the account registration processing has been completed in response to the registration/linking request. As shown in the figure, the linking processing execution screen80includes a message for confirming whether or not to perform the linking processing of the second account and the first account, a linking button81for performing the linking processing, and a cancel button82for canceling the linking processing as well as information regarding the second account such as the user name and the user ID (mail address).

The CPU11performs the linking processing when the CPU11receives a link execution request from the user terminal200in such a manner that the linking button81is pressed on the linking processing execution screen80. Specifically, the CPU11receives information regarding the second account by communication with the EC server400and stores the information regarding the second account in the user information database32in association with information regarding the first account.

In a case where the CPU11determines that the linking processing has been completed (Yes in Step50), the CPU11resends the reservation form screen50having one or more input items not entered to the user terminal200for transitioning from the linking processing execution screen80to the reservation form screen50(Step51).

Thus, the user of the user terminal200can enter the remaining input items on the reservation form screen50and send the reservation request of the restaurant to the restaurant information providing server100to thereby obtain points associated with the second account in accordance with the reservation contents. That is, when the restaurant information providing server100receives the reservation request, the restaurant information providing server100stores the reservation-related information in the reservation information database33and requests the EC server400to perform points granting processing for the second account with the reservation-related information. The request for the points granting processing may be performed collectively not for each reservation request but for a plurality of reservations periodically, for example, once a day, once a week, or the like.

Alternatively, in a case where after the completion of the account linking, the CPU11has received the reservation request based on the information entered on the reservation form screen50and has completed the reservation, the CPU11may generate a completion screen for simultaneously notifying of the completion of the reservation (service purchase) and the completion of the account linking (and the completion of the account registration) and may send the completion screen to the user terminal200. Accordingly, the time and effort to separately notify the user of the completion of the account linking processing (and the account registration processing) and the completion of the purchase processing with the linked account can be saved.

Conclusion

As described above, in accordance with this embodiment, the restaurant information providing server100suggests to log in with the first account or register the first account and to link to the second account at a timing when the user identification information (mail address) is entered on the reservation form screen50. In this manner, by using a reward to be obtained from the second service as an incentive, the restaurant information providing server100can prompt the user who has not logged in with the first service account or the user who does not have the first service account to link to the second service account without difficulty and prevent the loss of the opportunity to provide the service.

Modified Examples

The present invention is not limited to the above-mentioned embodiment and can be variously modified without departing from the gist of the present disclosure.

Although in the above-mentioned embodiment, the example in which the present invention is applied to the reservation form screen in the reservation processing of the restaurant has been shown, the present invention is not limited thereto. The present invention can be applied to a purchase request screen for requesting the purchase (use) of any other services or commodities.

Although in the above-mentioned embodiment, the presence or absence of the second account associated with the mail address as the user identification information is inquired to the EC server400, the presence or absence of the second account associated with other user identification information, such as the telephone number, may be inquired.

In the above-mentioned embodiment, the restaurant information providing server100may determine whether or not there is a log-in history with the first account within a predetermined period of time (e.g., one day, one week, one month, etc.) before the reception of the reservation request on the reservation form50from the user terminal200, and may be configured not to generate the account log-in/linking dialog60even if the associated second account exists in a case where there is a log-in history. Accordingly, in a case where there is a reservation request without logging in despite the presence of a history of log-in with the first account immediately before, the restaurant information providing server100considers that there is a possibility of spoofing and does not suggest to link the account, such that damage of illegal acquisition of points or the like can be prevented.

In the above-mentioned embodiment, the restaurant information providing server100inquires of whether or not the second account associated with the EC server400exists by using the mail address of the user as a key. In addition to the mail address, the restaurant information providing server100may inquire of the EC server400whether or not predetermined information (e.g., telephone number, etc.) other than the mail address, which has been entered on the reservation form screen50, is associated with the second account, and may generate and send the account log-in/linking suggestion dialog60or the account registration/linking suggestion dialog70in a case where the predetermined information is associated with the second account. Accordingly, whether or not the second account that can be linked exists can be determined more accurately.

In the above-mentioned embodiment, when the mail address is entered by the user on the reservation form screen50, whether or not the second account exists is checked regardless of the reservation contents, and the account log-in/linking suggestion dialog60or the account registration/linking suggestion dialog70is generated. However, the restaurant information providing server100may determine points to be given to the second account in accordance with the reservation (purchase processing of commodity or service), and may generate and send the account log-in/linking suggestion dialog60or the account registration/linking suggestion dialog70only in a case where those points are predetermined points or more. Accordingly, the restaurant information providing server100can prompt the user to link the first account and the second account by using relatively many points to be given through the link as an incentive.

Although in the above-mentioned embodiment, the restaurant information providing server100inquires the EC server400for the presence or absence of the second account associated with the first account, the presence or absence of the second account may be inquired to another server associated with the EC server400instead of directly inquiring the EC server400. It is because, for example, in a case where a plurality of service providers have a common account system, it is conceivable that an entity that provides services to users is different from an entity that manages accounts.

Moreover, when the restaurant information providing server100inquires about the presence or absence of the second account to the EC server400or another server associated therewith, it is conceivable that the EC server400or the server associated therewith is operated by an organization different from (e.g., not capital-related to) an organization that operates the restaurant information providing server100. In such a case, the restaurant information providing server100may not be able to access the EC server400or the server associated therewith from the viewpoint of security. In such a case, when inquiring of whether or not the second account exists, the restaurant information providing server100may perform access permission (access right setting) processing with the EC server400or (the database of) the server associated therewith.

In the above-mentioned embodiment, the restaurant information providing server100checks whether or not the first account associated with the mail address exists after inquiring the EC server400of whether or not the second account associated with the mail address entered by the user exists. However, the restaurant information providing server100may inquire of the presence or absence of the associated second account to the EC server400after checking whether or not the first account associated with the entered mail address exists.

Regarding inventions each recited as an “information processing method” of the inventions defined in the scope of claims of this patent application, at least one apparatus such as a computer automatically performs the respective steps through information processing based on software and a person does not perform those steps by using the apparatus such as the computer. That is, such an “information processing method” is not a method for a person to operate a calculation tool such as the computer, but an information processing method for the computer and the software.

In the above-mentioned embodiment, the program for executing the account linking processing may be stored in the storage unit18, may be stored in a computer-readable portable recording medium (e.g., semiconductor memory, optical disc, or the like), traded independently of the restaurant information providing server100, and distributed to a market, or may be sent to not only Japan but also overseas in accordance with an electronic order via the Internet or the like, for example.

REFERENCE SIGNS LIST

11CPU18storage unit19communication unit31restaurant information database32user information database33reservation information database50reservation form screen51name input field52mail address input field53telephone number input field60account log-in/linking suggestion dialog61log-in and linking button70account registration/linking suggestion dialog71registration and linking button80linking processing execution screen100restaurant information providing server200user terminal300restaurant terminal400another EC server