Computer system and store search method

Abstract

To activate local economic activity.SOLUTION: A computer system holds interpersonal relationship information for managing interpersonal relationships and store information for managing relationships between stores and persons associated with the stores. The computer system receives a store search request from a terminal operated by a user, refers to the interpersonal relationship information to identify related parties who have interpersonal relationships with the user, refers to the store information to retrieve stores that the related parties are associated with, selects the stores to be presented from among the retrieved stores, and presents the selected stores to the user.SELECTED DRAWING: Figure 7

Description

[Technical Field]

[0001] The present invention relates to a store search technology that promotes local economic activity. [Background technology]

[0002] It is becoming increasingly important to address the declining birthrate and aging society. The decline in the young population in a region leads to a decline in the vitality of the region, and ultimately to a decline in the local economy. As a solution to this issue, attempts are being made to introduce local currencies and hold events to revitalize the region.

[0003] A local currency is a currency that can only be used in a specific region. By introducing a local currency, it is expected that local consumption activities will be promoted and the local economy will be revitalized. It is also expected that the local economy will be revitalized by holding events to rediscover the charm of the region.

[0004] The introduction of a local currency raises the question of whether it will encourage the use of locally rooted stores. This is because it is expected that increasing consumption at stores that are economically self-sufficient within the local area will have a greater effect on revitalizing the local economy than increasing consumption at franchise stores that are spread across a wide area.

[0005] Patent Document 1 describes the following in order to revitalize the local economy: "When the advertising information registration device 2 receives advertising information from a store device 4 installed in a store located in the region 1a, it categorizes and stores the advertising information, and also generates and stores coupon information including the distance from the store that registered the advertising information to the terminal device 3 and a benefit corresponding to that distance, and at a predetermined timing, transmits to the terminal device 3 the advertising information that is common to all the terminal devices 3 and the coupon information corresponding to the destination terminal device 3. The terminal device 3 displays a list of stores to the user, and when the user selects a store from the displayed stores, it displays coupon information with an advertisement in which the coupon information corresponding to the store selected by the user has been added with the advertising information of the store, and executes a process of writing the coupon information with an advertisement selected by the user to the mobile terminal 5." [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Japanese Patent Application Laid-Open No. 2013-145520 Summary of the Invention [Problem to be solved by the invention]

[0007] By using the technology described in Patent Document 1, local stores can send coupons to users, thereby encouraging them to use the stores.

[0008] However, the technology described in Patent Document 1 imposes a financial burden on stores through advertisements and coupons. This makes it difficult for stores with limited financial resources to implement. Furthermore, the effect of increasing consumption activity through advertisements and coupons tends to be temporary, making it difficult to achieve a sustained effect.

[0009] The present invention provides a system and method for realizing a service that promotes the use of local stores and helps revitalize the local economy. [Means for solving the problem]

[0010] A representative example of the invention disclosed in this application is as follows: That is, a computer system including at least one computer, the computer system including: human relationship information for managing human relationships; store information for managing relationships between stores and people associated with the stores; History information for managing the store's usage history; receiving a store search request from a terminal operated by a user, and identifying a person who has a relationship with the user by referring to the human relationship information; Further, by referring to the human relationship information, an additional party having a human relationship with the party is identified; referring to the store information, searching for the store to which the person in question is related; Further, by referring to the store information, the store related to the additional related party is searched for, by referring to the history information, the store used by the related party is searched for, and further by referring to the history information, the store used by the additional related party is searched for, A store to be presented is selected from the searched stores, and the selected store is presented to the user. [Effects of the Invention]

[0011] According to one embodiment of the present invention, it is possible to present stores related to people who have relationships with the user, thereby revitalizing local economic activity. Other issues, configurations, and effects will become clear from the following description of the embodiments. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 illustrates an example of a system configuration according to a first embodiment. [Figure 2] FIG. 2 is a diagram illustrating an example of a hardware configuration of a computer that configures a system according to a first embodiment. [Figure 3A] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3B] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3C] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3D] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3E] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3F] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 3G] FIG. 10 is a diagram illustrating an example of information stored in a user terminal database according to the first embodiment. [Figure 4A] FIG. 10 is a diagram illustrating an example of information stored in a store terminal database according to the first embodiment. [Figure 4B] FIG. 10 is a diagram illustrating an example of information stored in a store terminal database according to the first embodiment. [Figure 4C] FIG. 10 is a diagram illustrating an example of information stored in a store terminal database according to the first embodiment. [Figure 5] 10 is a flowchart illustrating an example of a process of subscribing to a support service executed by the user terminal according to the first embodiment. [Figure 6] 10 is a flowchart illustrating an example of a process for subscribing to a support service executed by the store terminal according to the first embodiment. [Figure 7] 10 is a sequence diagram showing the flow of a support service in the system of the first embodiment. [Figure 8] FIG. 10 is a diagram illustrating an example of a screen presented on a user terminal according to the first embodiment. [Figure 9] FIG. 10 is a diagram showing an example of a screen displayed on a store terminal according to the first embodiment. [Figure 10] FIG. 10 is a diagram illustrating an example of a screen presented on a user terminal according to the first embodiment. [Figure 11A] 10 is a flowchart illustrating an example of a search process executed by the management server according to the first embodiment. [Figure 11B] 10 is a flowchart illustrating an example of a search process executed by the management server according to the first embodiment. [Figure 11C] 10 is a flowchart illustrating an example of a search process executed by the management server according to the first embodiment. [Figure 12] FIG. 10 is a diagram illustrating an example of an administrator list generated by the management server according to the first embodiment. [Figure 13] FIG. 10 is a diagram showing an example of a candidate store list generated by the management server according to the first embodiment. [Figure 14] FIG. 10 is a diagram illustrating an example of interaction information generated by the management server according to the first embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the description of the embodiments shown below. Those skilled in the art will readily understand that the specific configuration can be changed without departing from the spirit or intent of the present invention.

[0014] In the configuration of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and redundant explanations will be omitted.

[0015] In this specification, the terms "first," "second," "third," etc. are used to identify components and do not necessarily limit the number or order. [Example]

[0016] Fig. 1 is a diagram illustrating an example of the configuration of a system according to the first embodiment. Fig. 2 is a diagram illustrating an example of the hardware configuration of a computer that constitutes the system according to the first embodiment.

[0017] The system is composed of a plurality of user terminals 11, a plurality of store terminals 12, and a management server 13. The plurality of user terminals 11, the plurality of store terminals 12, and the management server 13 are connected to one another via a network 14 such as a LAN (Local Area Network) or WAN (Wide Area Network). The network 14 may be connected via either a wired or wireless method.

[0018] The user terminal 11, the store terminal 12, and the management server 13 are realized, for example, by using a computer 20 having a hardware configuration as shown in FIG.

[0019] The computer 20 has a CPU 21, a main memory device 22, a secondary memory device 23, a network interface 24, and an input / output device 25. Each hardware element is connected via a bus.

[0020] The CPU 21 executes a program stored in the main memory device 22. The CPU 21 operates as a functional unit (module) that realizes a specific function by executing processing in accordance with the program. In the following description, when processing is described using a functional unit as the subject, it indicates that the CPU 21 is executing a program that realizes the functional unit.

[0021] The main storage device 22 is a memory or the like, and stores programs executed by the CPU 21 and information used by the programs. The secondary storage device 23 is a hard disk drive (HDD) or solid state drive (SSD), and permanently stores large amounts of data. The programs and information stored in the main storage device 22 may be stored in the secondary storage device 23. In this case, the CPU 21 reads the programs and information from the secondary storage device 23 and loads them into the main storage device 22.

[0022] The network interface 24 communicates with external devices via a network. The input / output device 25 is a device for inputting and outputting information, and is, for example, a keyboard, a mouse, a touch panel, a display, and the like.

[0023] In this specification, the services provided by the management server 13 are referred to as support services, and the services provided by the stores are simply referred to as services.

[0024] The user terminal 11 is a terminal used by an individual, and includes a communication control unit F11, a screen control unit F12, and a control unit F13, and also holds a user terminal database D111.

[0025] The communication control unit F11 controls communication with external devices. The screen control unit F12 controls the display of images on a display or the like of the user terminal 11. The control unit F13 executes processing related to the support service. The user terminal database D111 stores various information related to the user operating the user terminal 11.

[0026] The store terminal 12 is a terminal owned by the owner of the store that provides the service or a terminal installed in the store, and has a communication control unit F21, a screen control unit F22, and a control unit F23, and also holds a store terminal database D121. The communication control unit F21, the screen control unit F22, and the control unit F23 have the same functions as the communication control unit F11, the screen control unit F12, and the control unit F13. The store terminal database D121 stores various information related to the store.

[0027] The management server 13 is a device that provides support services to promote local economic activity, and has a communication control unit F31, a screen control unit F32, and a service processing unit F33, and also holds an integrated database D131. The communication control unit F31 and the screen control unit F32 have the same functions as the communication control unit F11 and the screen control unit F12. The service processing unit F33 executes processing to realize the support service. The integrated database D131 stores various information related to users and stores.

[0028] The functions of the management server 13 may be realized using a computer system made up of a plurality of computers 20.

[0029] 3A, 3B, 3C, 3D, 3E, 3F, and 3G are diagrams illustrating an example of information stored in the user terminal database D111 of the first embodiment.

[0030] 3A is a table for managing basic information of users who operate user terminal 11. Table T300 includes name 301 and date of birth 302. Note that the attributes included in table T300 are merely an example and are not limited to these.

[0031] 3B is a table for managing the history of the residence of a user who operates the user terminal 11. Table T310 stores entries including a time 311 and a residence 312. Note that the fields included in the entry are merely an example and are not limiting.

[0032] Table T320 shown in Fig. 3C is a table for managing the educational background of the user who operates the user terminal 11. T320 stores entries including a period 321 and a school name 322. Note that the fields included in the entries are merely examples and are not limited to these.

[0033] 3D is a table for managing the work history of a user who operates the user terminal 11. Table T330 stores entries including a time period 331 and a company name 332. Note that the fields included in the entries are merely an example and are not limiting.

[0034] 3E is a table for managing the relatives of the user who operates the user terminal 11. Table T340 stores entries including person attributes 341 and names 342. Note that the fields included in the entries are merely examples and are not limited to these.

[0035] Table T350 shown in Fig. 3F is a table for managing people who are on friendly terms with the user who operates the user terminal 11. T350 stores an entry including a name 351 and an intimacy level 352. The intimacy level is a value indicating the degree of intimacy with the user, and can be set, for example, as an integer between 1 and 10. Note that the fields included in the entry are merely examples and are not limiting.

[0036] 3G is a table for managing groups to which a user who operates user terminal 11 belongs. Table T360 stores entries including group name 361, group attribute 362, and group member 363. Group member 363 stores the names of people who belong to the group, etc. Note that the fields included in the entry are merely an example and are not limited to these.

[0037] The user terminal database D111 may include a table for managing the interaction history of users.

[0038] In the following explanation, the tables T310, T320, T330, T340, T350, and T360 managed by the user terminal database D111 will be collectively referred to as human relationship information.

[0039] 4A, 4B, and 4C are diagrams illustrating an example of information stored in the store terminal database D121 according to the first embodiment.

[0040] 4A is a table for managing basic information about a store where a store terminal 12 is installed. Table T400 includes a store name 401, a category 402, and an address 403. The category 402 stores the category of services provided by the store. Note that the attributes included in table T400 are merely examples and are not limiting.

[0041] 4B is a table for managing the owner and employees of a store where the store terminal 12 is installed. Table T410 stores entries including a name 411 and a job title attribute 412. The job title attribute 412 is a field for storing the job title of a person in the store. Note that the fields included in the entry are merely an example and are not limited to this.

[0042] Table T420 shown in Fig. 4C is a table for managing the usage history of a store where the store terminal 12 is installed. Table T420 stores entries including a date 421 and a user 422. The user 422 stores the name of the person who used the store, or a membership number managed independently by the store, etc. Note that the fields included in the entries are merely examples and are not limiting.

[0043] In the following explanation, the table T400 and the table T410 All of this will be listed together as store information.

[0044] FIG. 5 is a flowchart showing an example of a process of subscribing to a support service executed by the user terminal 11 according to the first embodiment.

[0045] The user terminal 11 accesses the management server 13 and transmits a request to join the support service. The management server 13 presents the terms and conditions of the support service to the user terminal 11, and if consent to the terms and conditions is obtained from the user terminal 11, presents a screen for inputting human relationship information to the user terminal 11.

[0046] The user terminal 11 acquires human relationship information (step S101). If the human relationship information exists in the user terminal database D111, the user terminal 11 acquires the human relationship information from the user terminal database D111. If the human relationship information exists in an external service or external storage, the user terminal 11 acquires the human relationship information from the external service or external storage. If there is missing human relationship information, the user terminal 11 displays a screen prompting the user to input human relationship information.

[0047] External services include social networking sites, private services that provide maps and job information, and government services. By linking with external services, the effort required to input information can be reduced.

[0048] The user terminal 11 stores the acquired human relationship information in the user terminal database D111 (step S102).

[0049] The user terminal 11 transmits the acquired human relationship information to the management server 13 (step S103).

[0050] The management server 13 assigns user IDs to users and people related to the users as needed, and generates a user correspondence table that associates user IDs with names. The management server 13 also stores the user correspondence table and human relationship information that associates the user's user ID in the integrated database D131. The management server 13 also transmits a registration completion notification including the user ID to the user terminal 11.

[0051] By storing the same human relationship information in the user terminal database D111 and the integrated database D131, data inconsistency can be prevented.

[0052] Information about the current employment may be reflected in table T410. Management server 13 confirms the employment status with the store owner or the like, and if confirmation is obtained, adds data to table T410 corresponding to the store.

[0053] FIG. 6 is a flowchart showing an example of a support service subscription process executed by the store terminal 12 according to the first embodiment.

[0054] The store terminal 12 accesses the management server 13 and transmits a request to join the support service. The management server 13 presents the store terminal 12 with terms and conditions for the support service, and if the store terminal 12 agrees to the terms and conditions, the management server 13 presents the store terminal 12 with a screen for entering store information.

[0055] The store terminal 12 acquires store information (step S201). If the store information exists in the store terminal database D121, the store terminal 12 acquires the store information from the store terminal database D121. If the store information exists in an external service or external storage, the store terminal 12 acquires the store information from the external service or external storage. If there is missing store information, the store terminal 12 displays a screen prompting the store owner or employee to enter store information.

[0056] The shop terminal 12 stores the acquired shop information in the shop terminal database D121 (step S202).

[0057] The store terminal 12 transmits the acquired store information to the management server 13 (step S203). The management server 13 assigns a store ID to the store as needed, and generates a store correspondence table that associates the store ID with the store name. The management server 13 also stores the store correspondence table and the store information associated with the store ID in the integrated database D131. The management server 13 also transmits a registration completion notification including the store ID to the store terminal 12.

[0058] By storing the same store information in the store terminal database D121 and the integrated database D131, data inconsistency can be prevented.

[0059] When storing human relationship information and store information in the integrated database D131, the management server 13 may associate users with stores, thereby improving the efficiency of information management and search.

[0060] When adding new information or updating registered information, the user terminal 11 and the shop terminal 12 store the information in the respective databases D111 and D121, and then transmit the information to the management server 13.

[0061] Fig. 7 is a sequence showing the flow of a support service in the system of the first embodiment. Fig. 8 is a diagram showing an example of a screen presented on the user terminal 11 of the first embodiment. Fig. 9 is a diagram showing an example of a screen presented on the shop terminal 12 of the first embodiment. Fig. 10 is a diagram showing an example of a screen presented on the user terminal 11 of the first embodiment.

[0062] The user terminal 11 transmits a search request including a user ID, a current location, a current time, a desired store category, etc. to the management server 13 (step S301).

[0063] When the management server 13 receives the search request, it executes the search process (step S302). Details of the search process will be explained using Figures 11A, 11B, and 11C.

[0064] The management server 13 transmits the search results to the user terminal 11 (step S303). The search results include, for example, information about the store and the reason for selection. The reason for selecting the store may be, for example, "used by a related person" or "a related person works here."

[0065] Based on the search results, the user terminal 11 displays a screen such as that shown in FIG. 8. The user selects the store to use by referring to the information about the store and the reason for selection displayed on the screen. At this time, the user terminal 11 transmits a store visit advance notice to the store terminal 12 of the selected store (step S304). The store visit advance notice may be transmitted to the store terminal 12 via the management server 13.

[0066] When the store terminal 12 receives the advance notice of a store visit, it presents store employees and the like with information about the user (membership rank, details of services to be used), the planned time of visit, and the like. For example, a screen such as that shown in FIG. 9 is displayed. The store terminal 12 may also cooperate with the store's management system (not shown) to present information about services provided by the store to the user terminal 11. For example, in the case of a restaurant, a menu and an order form are presented. It is also possible to display information that matches the user's preferences using the user's usage history. This is expected to improve the quality of service provided to users.

[0067] When the user uses a service, the shop terminal 12 stores the usage history in the shop terminal database D121, and also transmits the usage history to the management server 13 (step S305).

[0068] The management server 13 may, as necessary, present a screen such as that shown in FIG. 10 on the user terminal 11 and accept input regarding the evaluation of the store.

[0069] 11A, 11B, and 11C are flowcharts showing an example of a search process executed by the management server 13 of the first embodiment. Fig. 12 is a diagram showing an example of a manager list generated by the management server 13 of the first embodiment. Fig. 13 is a diagram showing an example of a candidate store list generated by the management server 13 of the first embodiment.

[0070] The management server 13 determines a reference area based on the current location of the user (step S401).

[0071] Specifically, management server 13 refers to table T310 associated with the user ID and identifies the current user's place of residence. Management server 13 determines whether the distance between the current location and the place of residence is less than a predetermined threshold. If the distance between the current location and the place of residence is less than the predetermined threshold, management server 13 determines the area including the place of residence (e.g., a city, ward, town, or village) as the reference area. If the distance between the current location and the place of residence is equal to or greater than the predetermined threshold, management server 13 determines the area including the current location as the reference area.

[0072] The management server 13 selects one table from among the tables T340, T350, and T360 that are managed in association with the user ID (step S402).

[0073] The management server 13 selects one related person from among the related people registered in the selected table (step S403).

[0074] The management server 13 determines whether or not the related person resides in the reference area (step S404). Specifically, the following process is executed.

[0075] (S404-1) The management server 13 refers to the user correspondence table based on the name of the selected related person and acquires the user ID of the selected related person. If the user ID of the selected related person does not exist in the user correspondence table, the management server 13 determines that the related person does not reside in the reference area.

[0076] (S404-2) The management server 13 refers to the table T310 associated with the acquired user ID, and identifies the residence of the selected related person. The management server 13 determines whether the residence of the selected related person is within the reference area.

[0077] If the related person does not reside in the reference area, the management server 13 proceeds to step S406.

[0078] If the related person resides in the reference area, the management server 13 registers the related person in the related person list 1200 (step S405), and then proceeds to step S406.

[0079] Related person list 1200 stores entries including a user ID 1201 and an attribute 1202. Attribute 1202 stores a value indicating the relationship between the user and the related person. For example, for a related person selected from table T340, the value of person attribute 341 is stored in attribute 1202; for a related person selected from table T350, "friend" is stored in attribute 1202; and for a related person selected from table T360, the group attribute of the group to which the related person belongs is stored in attribute 1202.

[0080] In step S405, the management server 13 adds an entry to the related party list 1200, and sets the user ID identified in step S404 to the user ID 1201 of the added entry. The management server 13 also sets a value to the attribute 1202 of the added entry.

[0081] In step S406, the management server 13 determines whether or not the processing has been completed for all the related parties registered in the selected table (step S406).

[0082] If the process has not been completed for all the related parties registered in the selected table, the management server 13 returns to step S403 and executes the same process.

[0083] When the processing has been completed for all related parties registered in the selected table, the management server 13 determines whether the processing has been completed for all tables T340, T350, and T360 (step S407).

[0084] If the processing has not been completed for all of the tables T340, T350, and T360, the management server 13 returns to step S402 and executes the same processing.

[0085] By performing the processing from step S401 to step S407, it is possible to identify related parties who are related to the user and who reside in the reference area. This makes it possible to recommend stores that will deepen the relationship between the user and related parties in the reference area.

[0086] In addition, the following process may be added to the process using table T340. First, the management server 13 obtains the user ID of the related person (relative) from the user correspondence table, and executes the processes of steps S402 to S407 using tables T340, T350, and T360 associated with the user ID. This makes it possible to identify related people who have relationships with the user's relatives. Note that it may be possible to limit the search to only the wife and children. The above search is expected to stimulate interactions with various people connected to the user.

[0087] When processing has been completed for all tables T340, T350, and T360, management server 13 selects one related person from related person list 1200 (step S408).

[0088] The management server 13 refers to the table T410 and determines whether the selected related person is a store related person (step S409). Specifically, the following process is executed.

[0089] (S409-1) The management server 13 refers to the integrated database D131 and searches the table T410 in which the selected person concerned is registered.

[0090] (S409-2) If there is no table T410 in which the selected related party is registered, the management server 13 determines that the selected related party is not a store related party. If there is a table T410 in which the selected related party is registered, the management server 13 determines that the selected related party is a store related party.

[0091] If the selected person involved is not a store person, the management server 13 proceeds to step S413.

[0092] If the selected related person is a store related person, the management server 13 identifies the address of the store related to the related person (step S410).

[0093] Specifically, the management server 13 searches the table T400 associated with the store ID based on the store ID associated with the table T410 searched in step S409, and identifies the address.

[0094] The management server 13 determines whether or not a store related to the related person exists in the reference area (step S411). This is to promote economic activity in the reference area by recommending stores in the reference area.

[0095] If there is no store related to the related person in the reference area, the management server 13 proceeds to step S413.

[0096] If a store related to the related person exists in the reference area, the management server 13 registers the store in the candidate store list 1300 (step S412), and then proceeds to step S413.

[0097] The candidate store list 1300 stores entries including a user ID 1301, an attribute 1302, a job title attribute 1303, a store ID 1304, and a priority 1305. The job title attribute 1303 is a field that stores the job title of a person at the store. Note that if the person is not a store associate, the job title attribute 1303 is left blank. The priority 1305 is a field that stores the priority of the recommendation. In this embodiment, an integer equal to or greater than "1" is stored in the priority 1305. "1" is the highest priority, meaning that the item is recommended preferentially.

[0098] In step S412, the management server 13 adds an entry to the candidate store list 1300, and sets the user ID 1301 and attribute 1302 of the added entry to the values ​​of the user ID 1201 and attribute 1202 of the entry in the related party list 1200. The management server 13 sets the value of the position attribute 412 of the entry searched for from table T410 in step S409 to the position attribute 1303 of the added entry. The management server 13 sets the store ID identified in step S410 to the store ID 1304 of the added entry. The management server 13 also sets a priority in the priority 1305 of the added entry based on the position. For example, if the position is "owner," the priority is set to "1," if the position is "store manager," the priority is set to "2," and if the position is other than "owner" or "store manager," the priority is set to "3."

[0099] In step S413, the management server 13 determines whether or not there is a store that the related person has used (step S413).

[0100] Specifically, the management server 13 refers to the integrated database D131 and searches for the table T420 in which the related parties are registered.

[0101] If there is no store used by the related person, the management server 13 proceeds to step S417.

[0102] If a store used by the related person exists, the management server 13 identifies the address of the store (step S414).

[0103] Specifically, the management server 13 searches the table T400 associated with the store ID based on the store ID associated with the table T420 searched in step S413, and identifies the address.

[0104] The management server 13 determines whether the store used by the related person is located in the reference area (step S415). This is to promote economic activity in the reference area by recommending stores in the reference area.

[0105] If the store used by the related person does not exist in the reference area, the management server 13 proceeds to step S417.

[0106] If the store used by the related person is located in the reference area, the management server 13 registers the store in the candidate store list 1300 (step S416), and then proceeds to step S413.

[0107] Specifically, the management server 13 adds an entry to the candidate store list 1300, and sets the values ​​of the user ID 1201 and attribute 1202 of the entry in the related party list 1200 to the user ID 1301 and attribute 1302 of the added entry. The management server 13 sets the store ID identified in step S414 to the store ID 1304 of the added entry. The management server 13 also sets a priority in the priority 1305 of the added entry based on the relationship with the related party. For example, if the related party is a "friend," the priority is set to "4," if the related party is a "group member," the priority is set to "5," and if the related party is other than a "friend" or a "group member," the priority is set to "6."

[0108] In step S417, the management server 13 determines whether or not the process has been completed for all of the related parties registered in the related party list 1200 (step S417).

[0109] If the process has not been completed for all the parties registered in the party list 1200, the management server 13 returns to step S408 and executes the same process.

[0110] When the process has been completed for all related parties registered in the related party list 1200, the management server 13 generates search results based on the candidate store list 1300 (step S418), and then ends the search process.

[0111] Specifically, the management server 13 selects a predetermined number of stores from the candidate store list 1300 and generates display information for displaying the selected stores. Like There are ways to do this.

[0112] (Method 1) The management server 13 sorts the entries in the candidate store list 1300 based on priority. The management server 13 selects a predetermined number of stores in descending order of priority.

[0113] (Method 2) The management server 13 may generate groups for each priority level and select a predetermined number of stores from each group. The number of stores selected from a group may differ for each priority level.

[0114] (Method 3) The management server 13 randomly selects a store, which creates opportunities to use a variety of stores.

[0115] (Method 4) The management server 13 calculates the user's recent (for example, one month) frequency of use based on the table T420 of stores registered in the candidate store list 1300, and selects stores that are used least frequently.

[0116] If the support service is provided on a regional basis, the processes of steps S401, S410, S411, S414, and S415 can be omitted.

[0117] The management server 13 can also use the table T420 of each store to tally information about people with whom the user has interacted, and generate interaction information T1400 as shown in Fig. 14. The area and period for which the information is to be tallied can be set arbitrarily.

[0118] The interaction information T1400 stores entries including a user ID 1401 and a number of interactions 1402. The user ID 1401 is a field for storing the user IDs of people who have interacted with the target user. The interaction information T1400 is generated for each user. The interaction information T1400 for each user may be compiled into a single piece of information.

[0119] By aggregating the interaction information T1400 of people living in the same area, it is possible to quantitatively grasp the degree of human interaction in the area.

[0120] As explained above, when a person engages in economic activity, the management server 13 can present local stores related to people with whom the person has formed relationships. Stores can also improve the quality of their services by knowing when users visit the store. This encourages the use of local stores and revitalizes the local economy. Furthermore, the service can strengthen ties between people and between people and stores, thereby achieving sustainable revitalization of the local economy.

[0121] The present invention is not limited to the above-described embodiments, but includes various modifications. For example, the above-described embodiments are provided to explain the present invention in detail, and the present invention is not necessarily limited to those including all of the described configurations. Furthermore, some of the configurations of each embodiment can be added to, deleted from, or replaced with other configurations.

[0122] Furthermore, the above-described configurations, functions, processing units, processing means, etc. may be partially or entirely implemented in hardware, for example, by designing them as integrated circuits. The present invention can also be realized by software program code that implements the functions of the embodiments. In this case, a storage medium on which the program code is recorded is provided to a computer, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium on which it is stored constitute the present invention. Examples of storage media for providing such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, solid-state drives (SSDs), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, non-volatile memory cards, and ROMs.

[0123] Furthermore, the program code that realizes the functions described in this embodiment can be implemented in a wide range of program or script languages, such as assembler, C / C++, perl, Shell, PHP, Python, and Java (registered trademark).

[0124] Furthermore, the program code of the software that realizes the functions of the embodiments may be distributed via a network and stored in a storage means such as a computer's hard disk or memory, or in a storage medium such as a CD-RW or CD-R, and the processor of the computer may read and execute the program code stored in the storage means or storage medium.

[0125] In the above-described embodiment, the control lines and information lines are those that are considered necessary for the explanation, and not all control lines and information lines are necessarily shown in the product. All components may be interconnected. [Explanation of symbols]

[0126] 11 User terminal 12 Store terminals 13 Management Server 14 Network F11, F21, F31 Communication control unit F12, F22, F32 Screen control section F13, F23 control section F33 Service Department D111 User terminal database D121 Store terminal database D131 Integrated Database 20 Calculator 21 CPU 22 Main storage 23 Secondary storage device 24 Network Interface 25 Input / Output Devices

Claims

1. A computer system comprising at least one computer, retaining human relationship information for managing human relationships, store information for managing relationships between stores and people associated with the stores, and history information for managing usage history of the stores; receiving a store search request from a terminal operated by a user; Identifying a related party having a relationship with the user by referring to the human relationship information, and further identifying an additional related party having a relationship with the related party by referring to the human relationship information; Searching for the store to which the related party is related by referring to the store information, and further searching for the store to which the additional related party is related by referring to the store information; Searching for the store used by the related party by referring to the history information, and further searching for the store used by the additional related party by referring to the history information; Select a store to be presented from the searched stores, A computer system that presents the selected store to the user.

2. A computer system according to claim 1, determining a reference region based on the user's place of residence and current location; Searching for the store to which at least one of the related party and the additional related party is related and which is present in the reference area; A computer system that searches for the store that is used by at least one of the related party and the additional related party and that is located in the reference area.

3. A computer system according to claim 2, determining a priority for controlling a display order of the stores searched for based on the human relationship information based on the relationship between the related person and the store; determining the priority of the store searched for based on the history information based on the relationship between the user and the related person; A computer system characterized in that a store to be presented is selected from the searched stores based on the priority.

4. A computer system according to claim 2, Calculating the frequency of use of the searched store by the user based on the history information; A computer system that selects a store to be presented from among the searched stores based on the frequency of use of the store.

5. A store search method executed by a computer system including at least one computer, comprising: the computer system holds human relationship information for managing human relationships, store information for managing relationships between stores and people associated with the stores, and history information for managing usage history of the stores; The store search method includes: a first step in which the at least one computer receives a store search request from a terminal operated by a user; a second step in which the at least one computer refers to the human relationship information to identify a person involved in a human relationship with the user; a third step in which the at least one computer refers to the store information and searches for the store associated with the related person; a fourth step in which the at least one computer refers to the history information to search for the store used by the related person; a fifth step in which the at least one computer selects a store to be presented from the searched stores; a sixth step in which the at least one computer presents the selected store to the user; the second step includes a step of identifying an additional party having a relationship with the party by referring to the human relationship information, by the at least one computer; the third step includes a step of the at least one computer referring to the store information to search for the store associated with the additional party; The fourth step includes a step in which the at least one computer refers to the history information to search for the store used by the additional party.

6. A store search method according to claim 5, the second step includes a step of determining, by the at least one computer, a reference region based on the user's place of residence and current location; the third step includes a step in which the at least one computer searches for the store to which at least one of the related party and the additional related party is related and which is located in the reference area; A store search method characterized in that the fourth step includes a step in which the at least one computer searches for stores that are used by at least one of the related party and the additional related party and that are located in the reference area.

7. A store search method according to claim 6, comprising: The fifth step includes: a step of determining, by the at least one computer, a priority for controlling a display order of the stores searched based on the human relationship information, based on a relationship between the related person and the store; a step of determining, by the at least one computer, the priority of the store searched for based on the history information, based on a relationship between the user and the related person; and a step of selecting, by the at least one computer, a store to be presented from among the searched stores based on the priority.

8. A store search method according to claim 6, comprising: The fifth step includes: a step in which the at least one computer calculates the frequency of use of the searched store by the user based on the history information; and a step of selecting, by the at least one computer, a store to be presented from the searched stores based on the frequency of use of the store.

Images