Computer systems and methods to assist in tenant registration.

Abstract

This computer system for assisting with the registration to a service for matching a tenant and a space manages space characteristics indicative of the characteristics of the space; acquires, from a tenant, account information for a social network service (SNS) used by the tenant; accesses the SNS using the account information, and extracts keywords contained in posting information as SNS information; estimates a tenant attribute indicative of a business characteristic of the tenant on the basis of the SNS information; and for each combination of tenant attribute and space characteristic, estimates the amount of sales if the space were to be utilized and presents, to the tenant, an estimation result for the amount of sales for each space.

Description

Computer system and tenant registration support method Incorporation by Reference

[0001] This application claims priority to Japanese Patent Application No. 2021-099404, filed on June 15, 2021, the contents of which are incorporated herein by reference.

[0002] The present invention relates to a system and method for assisting registration with a service that matches tenants with spaces.

[0003] BACKGROUND ART In recent years, a technology described in Patent Document 1, for example, has been known as a matching system that matches spaces managed by commercial facilities such as malls with businesses (tenants) that wish to open stores.

[0004] Patent Document 1 states that "the content matching system selects recommended booth candidates based on the desired date and time of the booth exhibition input by the user, the content keywords of the content to be exhibited in the booth, the target customer attributes targeted by the user, the content keywords of each booth stored in the matching data table, the date and time of the booth exhibition, the calculated number of visitors to each booth, the attention level, which is the ratio of people who gazed at or stopped at the booth when the content was exhibited to the total number of passersby, the attention level, which is the ratio of people who entered the booth to the people who were highly interested, and the high interest level, which is the ratio of people who entered the booth to the people who were highly interested, and the high interest attribute rate, which is the attribute of people who were highly interested."

[0005] Japanese Patent Application Laid-Open No. 2021-5233

[0006] When considering opening a store, it is time-consuming to input the products or services that the tenant will handle and the characteristics of the target customers, so there is a problem that it is difficult to encourage people to use the matching system.

[0007] An object of the present invention is to provide a system and method for presenting information that encourages the use of a matching system.

[0008] A representative example of the invention disclosed in the present application is as follows: That is, a computer system that supports registration with a service that matches tenants with spaces to be used by the tenants manages space features that represent the characteristics of the spaces, acquires account information for an SNS used by the tenants from the tenants, accesses the SNS using the account information, extracts keywords included in posted information as SNS information, estimates tenant attributes that represent the business characteristics of the tenants based on the SNS information, estimates sales when the spaces are used for each combination of the tenant attributes and the space features, and presents the estimated sales for each space to the tenants.

[0009] According to one aspect of the present invention, it is possible to present information that encourages the use of a matching system. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments.

[0010] 1 is a diagram illustrating an overview of the present invention. FIG. 1 is a diagram illustrating an example of a system configuration of Example 1. FIG. 2 is a diagram illustrating an example of a hardware configuration of a registration support server of Example 1. FIG. 3 is a diagram illustrating an example of information managed by an SNS information storage unit of Example 1. FIG. 4 is a diagram illustrating an example of information managed by a tenant attribute storage unit of Example 1. FIG. 5 is a diagram illustrating an example of information managed by a space information storage unit of Example 1. FIG. 6 is a diagram illustrating an example of information managed by a shop opening history information storage unit of Example 1. FIG. 7 is a diagram illustrating an example of information managed by a shop opening condition information storage unit of Example 1. FIG. 8 is a diagram illustrating an example of information managed by a sales information storage unit of Example 1. FIG. 9 is a diagram illustrating an example of information managed by a space feature information storage unit of Example 1. FIG. 10 is a flowchart illustrating an example of space feature information extraction processing executed by an edge server of Example 1. FIG. 11 is a flowchart illustrating an example of tenant attribute estimation processing executed by the registration support server of Example 1. FIG. 12 is a flowchart illustrating an example of tenant attribute update processing executed by the registration support server of Example 1. FIG. 13 is a flowchart illustrating an example of sales estimation processing executed by the registration support server of Example 1.

[0011] First, the concept of the present invention will be explained. Fig. 1 is a diagram for explaining an outline of the present invention.

[0012] The system includes a registration support server 100, a tenant 101, and a social networking service (SNS) 102.

[0013] The tenant 101 represents a business operator (either an individual or a corporation) who wishes to open a store. The tenant 101 uses a terminal 105 to input information to the registration support server 100 and also refers to information output from the registration support server 100. In the present invention, the tenant 101 inputs account information for accessing the SNS 102, past store opening information, and store opening condition information (information related to the store opening space and information related to the opening date and time), and receives information related to tenant attributes, space, and sales forecasts from the registration support server 100.

[0014] The registration support server 100 is a system that supports the registration of tenants 101 in a matching system (not shown), estimates tenant attributes, and predicts sales if the tenant 101 opens a store in a given space. Here, the tenant attributes are attributes that represent the business characteristics of the tenant 101, such as the products and services handled by the tenant 101 and the target customer base. The matching system is a system that matches tenants 101 with spaces.

[0015] The registration support server 100 includes an SNS information extraction unit 220 , a tenant attribute estimation model storage unit 216 , and a sales estimation model storage unit 217 .

[0016] The SNS information extraction unit 220 uses the account information to extract predetermined keywords as SNS information from the posted information of the tenant 101 posted on the SNS 102. Note that the SNS information is not limited to keywords. For example, the SNS information may be an image posted on the SNS 102 or information extracted from an image.

[0017] The tenant attribute estimation model storage unit 216 stores a tenant attribute estimation model. Tenant attributes are estimated by inputting SNS information into the tenant attribute estimation model. The estimated tenant attributes are transmitted to the sales estimation model storage unit 217 and the terminal 105. The estimated tenant attributes are displayed on a screen 110 of the terminal 105. The screen 110 includes an operation button for correcting the tenant attributes and an operation button for confirming the tenant attributes.

[0018] The sales estimation model storage unit 217 stores a sales estimation model. Sales are estimated by inputting tenant attributes into the sales estimation model. The sales estimation results are sent to the terminal 105. The screen 110 of the terminal 105 displays spaces where high sales are expected and the estimated sales.

[0019] The registration assistance server 100 estimates tenant attributes from information posted on the SNS 102 using account information and presents the estimate to the tenant 101, thereby reducing the effort required for the tenant 101 to input information when registering the tenant 101 in the matching system. In addition, by presenting the space along with sales forecasts, the tenant 101 can perform a business simulation if the matching system is used.

[0020] Increasing the number of tenants 101 registered in the matching system has the advantage that developers who provide space to tenants 101 can more easily reach a variety of tenants 101. Another advantage is that the operator of the matching system can propose events and the like to developers along with the tenant attributes of the various tenants 101.

[0021] 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.

[0022] 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.

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

[0024] To facilitate understanding of the invention, the position, size, shape, range, etc. of each component shown in the drawings etc. may not represent the actual position, size, shape, range, etc. Therefore, the present invention is not limited to the position, size, shape, range, etc. disclosed in the drawings etc.

[0025] Fig. 2 is a diagram illustrating an example of a system configuration according to the first embodiment. Fig. 3 is a diagram illustrating an example of a hardware configuration of the registration support server 100 according to the first embodiment.

[0026] The system includes a registration assistance server 100, a terminal 105, an edge server 200, and a sensor group 201. The registration assistance server 100, the terminal 105, the edge server 200, and the sensor group 201 are connected to one another via a network 202. The network 202 is, for example, a wide area network (WAN) or a local area network (LAN), and the connection method may be either wired or wireless. Note that the network connecting the registration assistance server 100 and the terminal 105, the network connecting the registration assistance server 100 and the edge server 200, and the network connecting the edge server 200 and the sensor group 201 may be different networks.

[0027] The registration support server 100 is a computer having a hardware configuration as shown in Fig. 3. Specifically, the registration support server 100 has a CPU 300, a memory 301, a storage device 302, a network interface 303, an input device 304, and an output device 305. Note that the hardware configuration of the registration support server 100 shown in Fig. 3 is an example and is not limited to this. For example, the registration support server 100 does not have to have the input device 304 and the output device 305.

[0028] The CPU 300 is a computing device that controls the entire registration assistance server 100 and executes programs stored in the memory 301. The CPU 300 executes processes according to the programs, thereby operating as a functional unit (module) that realizes a specific function. In the following description, when a process is described using a functional unit as the subject, this indicates that the CPU 300 is executing a program that realizes the functional unit.

[0029] The memory 301 is a storage device that stores programs executed by the CPU 300 and information used by the programs. The memory 301 is also used as a work area. The storage device 302 is a storage device that permanently stores data, such as a hard disk drive (HDD) or a solid state drive (SSD). The programs and information stored in the memory 301 may be stored in the storage device 302. In this case, the CPU 300 reads the programs and information from the storage device 302 and loads them into the memory 301.

[0030] The network interface 303 is an interface for communicating with an external device or system via a network. The input device 304 is a device for inputting data, commands, etc. to the registration assistance server 100, such as a keyboard, mouse, or touch panel. The output device 305 is a device for outputting information, such as a display.

[0031] The hardware configurations of the terminal 105 and the edge server 200 are the same as those of the registration support server 100, and therefore will not be described again. Returning to the description of FIG.

[0032] The registration support server 100 has an SNS information storage unit 210, a tenant attribute storage unit 211, a space information storage unit 212, a store opening history information storage unit 213, a store opening condition information storage unit 214, a sales information storage unit 215, a tenant attribute estimation model storage unit 216, a sales estimation model storage unit 217, an SNS information extraction unit 220, a sales estimation unit 221, a new post determination unit 222, an input data generation unit (for tenant attribute learning) 223, a tenant attribute estimation model learning unit 224, an input data generation unit (for sales estimation learning) 225, and a sales estimation model learning unit 226.

[0033] The SNS information storage unit 210 manages SNS information extracted from posted information on the SNS 102. The tenant attribute storage unit 211 manages tenant attributes estimated from SNS information. The space information storage unit 212 manages information related to spaces handled by the matching system. The store opening history information storage unit 213 manages information related to sales and the like of past store openings (store opening history information). The store opening condition information storage unit 214 manages information related to store opening conditions (store opening condition information), such as the space conditions desired by the tenant 101. The sales information storage unit 215 manages estimated sales results.

[0034] The tenant attribute estimation model storage unit 216 manages a model (tenant attribute estimation model) that estimates tenant attributes. The tenant attribute estimation model of this embodiment accepts SNS information as input and outputs tenant attributes. Note that the model may also accept information other than SNS information as input. The sales estimation model storage unit 217 manages a model (sales estimation model) that estimates sales. The sales estimation model of this embodiment accepts tenant attributes and space features as input and outputs sales. Note that the model may also accept store opening conditions as input.

[0035] The SNS information extraction unit 220 extracts SNS information from information posted on the SNS 102. The sales estimation unit 221 estimates sales using a sales estimation model. The new post determination unit 222 searches for new posted information on the SNS 102.

[0036] The input data generation unit (for tenant attribute learning) 223 generates input data for learning the tenant attribute estimation model. For example, the input data generation unit 223 generates the input data using information managed by the SNS information storage unit 210 and the tenant attribute storage unit 211. The tenant attribute estimation model learning unit 224 learns the tenant attribute estimation model using the input data, and outputs the tenant attribute estimation model that is the learning result to the tenant attribute estimation model storage unit 216.

[0037] The input data generation unit (for sales estimation learning) 225 generates input data for learning the sales estimation model. For example, the input data generation unit 225 generates input data using information managed by the space information storage unit 212 and the store opening history information storage unit 213. The sales estimation model learning unit 226 learns the sales estimation model using the input data and outputs the sales estimation model that is the learning result to the sales estimation model storage unit 217.

[0038] It should be noted that with regard to each functional unit of the registration assistance server 100, multiple functional units may be combined into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0039] The registration support server 100 may be a registration support system made up of multiple computers.

[0040] The terminal 105 is a terminal operated by the tenant 101, and has a tenant attribute input unit 230, an SNS account information input unit 231, a store opening conditions information input unit 232, a store opening history information input unit 233, a screen output unit 234, and a user interface processing unit 235.

[0041] The tenant attribute input unit 230 inputs corrections and additions to the tenant attributes to the registration support server 100. The tenant 101 refers to the tenant attributes estimated by the registration support server 100 and corrects and adds the tenant attributes using the tenant attribute input unit 230. The SNS account information input unit 231 inputs account information of the SNS 102 used by the tenant 101 to the registration support server 100. The shop opening condition information input unit 232 inputs shop opening condition information to the registration support server 100. The shop opening history information input unit 233 inputs shop opening history information to the registration support server 100. The screen output unit 234 outputs a screen. The user interface processing unit 235 performs processing related to the user interface.

[0042] It should be noted that with regard to each functional unit of the terminal 105, multiple functional units may be combined into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0043] The sensor group 201 is a group of sensors installed in a space where a space exists, and acquires sensor data etc. related to people who use the space. The sensor group 201 acquires, for example, images.

[0044] The edge server 200 analyzes and manages the characteristics of the space. The edge server 200 includes a space characteristic information storage unit 240, a sensor control unit 250, and a space characteristic information extraction unit 251.

[0045] The space characteristic information storage unit 240 manages information related to the characteristics of a space (space characteristic information). In this embodiment, information about people passing through or using a space is managed as space characteristics. The sensor control unit 250 controls the sensor group 201. Note that the edge server 200 has a storage unit that manages sensor data, but this is omitted. The space characteristic information extraction unit 251 analyzes the sensor data to extract space characteristic information for each space and outputs it to the space characteristic information storage unit 240.

[0046] It should be noted that with regard to each functional unit of the edge server 200, multiple functional units may be combined into one functional unit, or one functional unit may be divided into multiple functional units for each function.

[0047] In this embodiment, the registration support server 100 is configured to be able to grasp the space characteristics by communicating with the edge server 200, but is not limited to this. For example, the edge server 200 may transmit space characteristic information to the registration support server 100 in advance.

[0048] Next, the information managed by the registration support server 100 and the edge server 200 will be described with reference to FIGS.

[0049] FIG. 4 is a diagram illustrating an example of information managed by the SNS information storage unit 210 according to the first embodiment.

[0050] The SNS information storage unit 210 manages a table 400 as shown in FIG. 4. The table 400 stores entries including an account ID 401 and a tag 402. One entry exists for one piece of account information. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above-described fields, or may include other fields.

[0051] The account ID 401 is a field for storing an account ID, which is account information for accessing the SNS 102 used by the tenant 101. The tag 402 is a group of fields for storing hash tags, which are SNS information extracted from posted information on the SNS 102. The tag 402 includes a plurality of fields for storing hash tags.

[0052] In this embodiment, hashtags are extracted as SNS information, but this is not limiting. Words related to products, users, etc. may also be extracted as SNS information.

[0053] The data format of the information managed by the SNS information storage unit 210 may be a format other than a table, such as CSV or XML.

[0054] FIG. 5 is a diagram illustrating an example of information managed by the tenant attribute storage unit 211 according to the first embodiment.

[0055] The tenant attribute storage unit 211 manages a table 500 as shown in FIG. 5 . The table 500 stores entries including an ID 501, a tenant name 502, an account ID 503, and tenant attributes 504. One entry exists for each combination of a tenant 101 and tenant attributes. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above-described fields, or may include other fields.

[0056] The ID 501 is a field that stores identification information of an entry in the table 500. The tenant name 502 is a field that stores identification information of the tenant 101. In this embodiment, the name of the tenant 101 is stored. The account ID 503 is the same field as the account ID 401. The tenant attributes 504 are a group of fields that store the tenant attributes of the tenant 101. The tenant attributes 504 include a sales item 511, a target gender 512, and a target age group 513. Note that the tenant attributes 504 may include fields other than those described above.

[0057] The data format of the information managed by the tenant attribute storage unit 211 may be a format other than a table, such as CSV or XML.

[0058] FIG. 6 is a diagram illustrating an example of information managed by the space information storage unit 212 according to the first embodiment.

[0059] The space information storage unit 212 manages a table 600 as shown in Fig. 6. The table 600 stores entries including a space name 601, an address 602, space attributes 603, facilities 604, and application / usage status 605. One entry exists for one space. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above fields, or may include other fields.

[0060] Space name 601 is a field that stores identification information for a space. In this embodiment, the name of the space is stored. Address 602 is a field that stores information indicating where the space is located. In this embodiment, the address of the facility that provides the space is stored. Space attributes 603 is a field that stores the usage format of the space, etc. Equipment 604 is a field that stores information about equipment that can be used in the space or equipment that is installed. Application / usage status 605 is a field that stores the application status and usage status of the space. For example, the usage period of the space, etc. is stored.

[0061] The data format of the information managed by the space information storage unit 212 may be a format other than a table, such as CSV or XML.

[0062] FIG. 7 is a diagram illustrating an example of information managed by the store opening history information storage unit 213 according to the first embodiment.

[0063] The store opening history information storage unit 213 manages a table 700 as shown in FIG. 7. The table 700 stores entries including a tenant name 701, a sales item 702, a space name 703, a period 704, and sales 705. There is one entry for one store opening history. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above-described fields, or may include other fields.

[0064] The tenant name 701 is the same field as the tenant name 502. The sales item 702 is the same field as the sales item 511. The space name 703 is the same field as the space name 601. The period 704 is a field that stores the store opening period. The sales 705 is a field that stores sales.

[0065] The data format of the information managed by the store opening history information storage unit 213 may be a format other than a table, such as CSV or XML.

[0066] FIG. 8 is a diagram illustrating an example of information managed by the shop opening condition information storage unit 214 according to the first embodiment.

[0067] The store opening condition information storage unit 214 manages a table 800 as shown in FIG. 8. Note that it is displayed in two stages due to the margins of the drawing. The table 800 stores entries including an ID 801, a tenant name 802, an area 803, a sales item 804, a passerby attribute 805, equipment 806, a period 807, and a time 808. There is one entry for each combination of a tenant 101 and a sales item. Note that the fields included in an entry are not limited to those described above. It is possible to omit any of the above-described fields, or to include other fields.

[0068] ID 801 is a field that stores identification information for an entry in table 800. Tenant name 802 is the same field as tenant name 502. Area 803 is a field that stores the area in which the tenant wishes to open a store. Area 803 stores the name, address, etc. of the area. Sales item 804 is a field that stores the products to be sold or the services to be provided, etc.

[0069] The passerby attributes 805 are a group of fields for storing desired space characteristics. The passerby attributes 805 include a number of people 811, a gender 812, and an age 813. Note that the passerby attributes 805 may include fields other than those described above. The number of people 811 is a field for storing the number of people passing through or using the space per unit time. The gender 812 is a field for specifying the gender distribution of people passing through or using the space. If the gender 812 is "male", it indicates that it is desired that a higher proportion of people passing through or using the space are male. The age 813 is a field for specifying the age distribution of people passing through or using the space. If the age 813 is "30s", it indicates that it is desired that a higher proportion of people passing through or using the space are in their 30s.

[0070] Facility 806 is a field for storing the desired facility. Period 807 is a field for storing the desired usage period of the space. Time 808 is a field for storing the usage hours (business hours) of the desired space.

[0071] The data format of the information managed by the shop opening condition information storage unit 214 may be a format other than a table, such as CSV or XML.

[0072] FIG. 9 is a diagram illustrating an example of information managed by the sales information storage unit 215 according to the first embodiment.

[0073] The sales information storage unit 215 manages a table 900 as shown in FIG. 9. The table 900 has fields for storing entries including a tenant name 901, a sort number 902, a space name 903, estimated sales 904, past sales 905, and a store opening condition information ID 906. One entry exists for each combination of a tenant 101, a space, and a store opening condition. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above fields, or may include other fields.

[0074] Tenant name 901 is the same field as tenant name 502. Sort number 902 is a field that stores the display order of estimated sales. Space name 903 is the same field as space name 601. Estimated sales 904 is a field that stores estimated sales. Past sales 905 is a field that stores past sales. Shop opening condition information ID 906 is a field that stores identification information of an entry in table 800. A value corresponding to ID 801 is stored in shop opening condition information ID 906.

[0075] The data format of the information managed by the sales information storage unit 215 may be a format other than a table, such as CSV or XML.

[0076] FIG. 10 is a diagram illustrating an example of information managed by the space characteristic information storage unit 240 according to the first embodiment.

[0077] The space characteristic information storage unit 240 manages a table 1000 as shown in FIG. 10. The table 1000 has fields for storing entries including a space name 1001 and a passerby attribute 1002. One entry exists for one space. Note that the fields included in an entry are not limited to those described above. An entry may not include any of the above fields, or may include other fields.

[0078] The space name 1001 is the same field as the space name 601. The passerby attributes 1002 are a group of fields that store passerby attributes 1002 that represent the characteristics of a space. The passerby attributes 1002 include number of people 1011, gender 1012, and age 1013. The number of people 1011 is a field that stores the number of people who pass through or use a space per unit time. Gender 1012 is a field that stores the gender distribution of people who pass through or use the space. Age 1013 is a field that stores the age distribution of people who pass through or use the space.

[0079] Next, the processing executed in the system will be described with reference to FIGS.

[0080] FIG. 11 is a flowchart illustrating an example of a space characteristic information extraction process executed by the edge server 200 according to the first embodiment.

[0081] The edge server 200 starts the space feature information extraction process periodically or when an execution instruction is received. Note that Fig. 11 explains the process executed for one space. If there are multiple spaces, the same process is executed for each space.

[0082] The space characteristic information extraction unit 251 determines whether the space is currently open (step S1101).

[0083] If it is determined that the space is not currently open, the space characteristic information extraction unit 251 ends the space characteristic information extraction process.

[0084] If it is determined that the space is currently open for business, the space characteristic information extraction unit 251 starts measuring the elapsed time (step S1102).

[0085] The space characteristic information extraction unit 251 determines whether the elapsed time is greater than a threshold value T1 (step S1103). The threshold value T1 is a preset value that can be set arbitrarily.

[0086] If the elapsed time is equal to or less than the threshold value T1, the space characteristic information extraction unit 251 returns to step S1103 after a certain time has elapsed.

[0087] If the elapsed time is greater than the threshold T1, the space characteristic information extraction unit 251 outputs passerby attributes by analyzing the sensor data acquired from the sensor group 201 (step S1104). For example, the space characteristic information extraction unit 251 performs known image analysis to identify the gender, age, and number of people passing through or using the space.

[0088] The sensor data is acquired and managed by the sensor control unit 250.

[0089] The space characteristic information extraction unit 251 updates the space characteristic information (step S1105), and then returns to step S101. At this time, the space characteristic information extraction unit 251 initializes the elapsed time.

[0090] Specifically, the space characteristic information extraction unit 251 outputs the space identification information and passerby attributes to the space characteristic information storage unit 240. The space characteristic information storage unit 240 searches for an entry in which the accepted space identification information is stored in the space name 1001. If the entry exists, the space characteristic information storage unit 240 overwrites the accepted passerby attributes 1002 of the entry. If the entry does not exist, the space characteristic information storage unit 240 adds the entry to the table 1000 and sets the accepted values ​​to the space name 1001 and passerby attributes 1002 of the entry.

[0091] FIG. 12 is a flowchart illustrating an example of a tenant attribute estimation process executed by the registration support server 100 according to the first embodiment.

[0092] When the registration support server 100 receives an operation from the terminal 105, the registration support server 100 starts the tenant attribute estimation process.

[0093] The SNS information extraction unit 220 presents a screen for inputting account information on the terminal 105 and waits for the account information to be input.

[0094] The SNS information extraction unit 220 receives account information via the SNS account information input unit 231 of the terminal 105 (step S1201).

[0095] The SNS information extraction unit 220 accesses the SNS 102 using the account information and extracts SNS information from the posted information of the tenant 101 on the SNS 102 (step S1202). At this time, the SNS information extraction unit 220 outputs the account information and the extracted SNS information to the SNS information storage unit 210. The SNS information storage unit 210 searches for an entry in which the received account information is stored in the account ID 401. If the entry exists, the SNS information storage unit 210 overwrites the tag 402 of the entry with the received SNS information. If the entry does not exist, the SNS information storage unit 210 adds the entry to the table 400 and sets the received values ​​in the account ID 401 and tag 402 of the entry.

[0096] In this embodiment, hashtags are extracted as SNS information, but known natural language processing techniques may be used to obtain keywords related to the items handled and customers as SNS information.

[0097] The SNS information extraction unit 220 acquires tenant attributes by inputting SNS information into the tenant attribute estimation model (Step S1203).

[0098] The SNS information extraction unit 220 displays the estimated tenant attributes on the screen of the terminal 105 (step S1204), and waits for an operation by the tenant 101.

[0099] When the SNS information extraction unit 220 receives an operation via the tenant attribute input unit 230 of the tenant 101, the SNS information extraction unit 220 determines whether the operation is a correction request (step S1205). Note that the correction request includes the correction content.

[0100] If it is determined that the received operation is a modification request, the SNS information extraction unit 220 modifies the tenant attributes in accordance with the modification request (step S1206), and then returns to step S1204.

[0101] Specifically, the SNS information extraction unit 220 outputs the account information and the correction content of the tenant attribute to the tenant attribute storage unit 211. The tenant attribute storage unit 211 searches for an entry in which the received account information is stored in the account ID 503, and reflects the correction content of the tenant attribute in the tenant attribute 504 of the entry.

[0102] If it is determined that the received operation is a completion request, the SNS information extraction unit 220 registers the tenant attribute (Step S1207). After that, the SNS information extraction unit 220 ends the tenant attribute estimation process.

[0103] Specifically, the SNS information extraction unit 220 outputs the identification information, account information, and tenant attributes of the tenant 101 to the tenant attribute storage unit 211 .

[0104] If an entry exists in which the tenant name 502 is identification information of the tenant 101 and the sales item item 511 is a sales item included in the data, the tenant attribute storage unit 211 overwrites the tenant attribute 504 of the entry with the tenant attribute included in the data. If the above-mentioned entry does not exist, the tenant attribute storage unit 211 adds an entry, sets identification information in the ID 501, sets identification information and account information of the tenant 101 in the tenant name 502 and account ID 503, and sets the tenant attribute included in the data in the tenant attribute 504. The tenant attribute storage unit 211 starts measuring elapsed time.

[0105] FIG. 13 is a flowchart illustrating an example of a tenant attribute update process executed by the registration support server 100 according to the first embodiment.

[0106] After being started, the registration support server 100 starts the tenant attribute update process.

[0107] The tenant attribute storage unit 211 determines whether the elapsed time is greater than a threshold T2 (Step S1301).

[0108] If the elapsed time is equal to or less than the threshold T2, the tenant attribute storage unit 211 returns to step S1301 after a certain time has elapsed.

[0109] If the elapsed time is greater than the threshold T2, the tenant attribute storage unit 211 calls the new post determination unit 222. The new post determination unit 222 accesses the SNS information storage unit 210 and acquires account information (step S1302).

[0110] The new post determination unit 222 starts a loop process of the account information (step S1303). Specifically, the new post determination unit 222 selects one piece of account information from the acquired account information.

[0111] The new post determination unit 222 accesses the SNS 102 using the selected account information and determines whether or not there is new posted information for the tenant 101 that corresponds to the account information (step S1304). The new post determination unit 222 determines, for example, whether or not there is posted information that was posted after a date and time obtained by subtracting an elapsed time from the current date and time.

[0112] If it is determined that new posted information of the tenant 101 does not exist, the new post determining unit 222 proceeds to step S1310.

[0113] If it is determined that new posted information of the tenant 101 exists, the new post determination unit 222 calls the SNS information extraction unit 220. At this time, the new post determination unit 222 outputs the selected account information to the SNS information extraction unit 220.

[0114] The SNS information extraction unit 220 accesses the SNS 102 using the account information, and extracts the SNS information from the posted information of the tenant 101 on the SNS 102 (step S1305). The process of step S1305 is the same as the process of step S1202.

[0115] The SNS information extraction unit 220 inputs the SNS information into the tenant attribute estimation model (step S1306) and acquires tenant attributes. The processing of step S1306 is the same as the processing of step S1203. Note that the previously extracted SNS information and newly extracted SNS information are input to the tenant attribute estimation.

[0116] The SNS information extraction unit 220 displays the estimated tenant attributes on the screen of the terminal 105 (step S1307), and waits for an operation from the tenant 101. The process of step S1307 is the same as the process of step S1204.

[0117] When the SNS information extraction unit 220 receives an operation via the tenant attribute input unit 230 of the tenant 101, the SNS information extraction unit 220 determines whether the operation is a correction request (step S1308). The correction request includes the correction content. The processing of step S1308 is the same as the processing of step S1205.

[0118] If it is determined that the received operation is a modification request, the SNS information extraction unit 220 modifies the tenant attributes in accordance with the modification request (step S1309), and then returns to step S1307. The processing in step S1309 is the same as the processing in step S1206.

[0119] If it is determined that the received operation is a completion request, the SNS information extraction unit 220 notifies the new posting determination unit 222 of the completion of the process.

[0120] In step S1310, the new post determining unit 222 determines whether or not the processing has been completed for all of the account information acquired in step S1302 (step S1310).

[0121] If it is determined that the processing has not been completed for all the account information, the new post determining unit 222 returns to step S1303 and executes the same processing.

[0122] If it is determined that the processing has been completed for all account information, the new post determination unit 222 calls the sales estimation unit 221 (step S1311), and then returns to step S1301. At this time, the new post determination unit 222 outputs the account information of the tenant 101 for which the new post has been made to the sales estimation unit 221.

[0123] By automatically updating tenant attributes and estimating sales based on the latest tenant attributes, it becomes possible to recommend spaces that are suited to the current situation of the tenant 101.

[0124] If there is no tenant 101 that has made a new post, the new post determination unit 222 does not call the sales estimation unit 221 and ends the process.

[0125] FIG. 14 is a flowchart illustrating an example of a sales estimation process executed by the registration support server 100 according to the first embodiment.

[0126] The registration support server 100 starts the sales estimation process when it receives an execution instruction from the terminal 105 or when it is called by the new post determination unit 222. Fig. 14 describes the sales estimation process that is executed when it receives an execution instruction from the terminal 105.

[0127] The sales estimation unit 221 acquires the store opening condition information of the tenant 101 from the store opening condition information storage unit 214 (step S1401). Specifically, the sales estimation unit 221 outputs the identification information of the tenant 101 to the store opening condition information storage unit 214. The store opening condition information storage unit 214 searches for an entry in which the identification information of the tenant 101 received in the tenant name 802 is stored, and outputs the entry to the sales estimation unit 221.

[0128] Here, it is assumed that the store opening condition information has been input before the start of the sales estimation process. Note that the sales estimation unit 221 may prompt the tenant 101 to input the store opening condition information at this point.

[0129] The sales estimation unit 221 starts a loop process of spaces (step S1402). Specifically, the sales estimation unit 221 acquires space information from the space information storage unit 212 and selects one piece of space information from the acquired space information.

[0130] The sales estimation unit 221 acquires the space characteristics of the selected space from the space characteristic information storage unit 240 of the edge server 200 (step S1403).

[0131] Specifically, the sales estimation unit 221 sends an acquisition request including the space identification information to the edge server 200. The space characteristic information storage unit 240 searches the space name 1001 for an entry in which the space identification information included in the acquisition request is stored, and sends a response including the value stored in the passerby attribute 1002 of the searched entry.

[0132] The sales estimation unit 221 acquires estimated sales by inputting tenant attributes and space features into the sales estimation model (step S1404).

[0133] The sales estimation unit 221 refers to the store opening history information (step S1405).

[0134] Specifically, the sales estimation unit 221 outputs the space identification information and the sales item items included in the store opening condition information to the store opening history information storage unit 213.

[0135] The store opening history information storage unit 213 searches for an entry whose combination of values ​​of the sales item 702 and space name 703 matches the combination of the received sales item and space identification information. If the entry exists, the store opening history information storage unit 213 outputs the value stored in the sales 705 of the entry as a response to the sales estimation unit 221. If the entry does not exist, the store opening history information storage unit 213 outputs a response to the sales estimation unit 221 indicating that the entry does not exist.

[0136] It is also possible to acquire only the past sales of the target tenant 101. In this case, the sales estimation unit 221 may output the identification information of the tenant 101, the identification information of the space, and the items for sale to the store opening history information storage unit 213.

[0137] The sales estimation unit 221 updates the sales information (step S1406). Specifically, the sales estimation unit 221 outputs the identification information of the tenant 101, the identification information of the space, the identification information of the store opening condition information, the estimated sales, and the past sales to the sales information storage unit 215.

[0138] The sales information storage unit 215 searches for an entry whose combination of values ​​of tenant name 901, space name 903, and shop opening condition information ID 906 matches the combination of the received identification information of the tenant 101, space identification information, and shop opening condition information. If the entry exists, the sales information storage unit 215 overwrites the estimated sales 904 of the entry with the estimated sales, and overwrites the past sales 905 with the past sales. At this time, the sort number 902 is deleted. If the entry does not exist, the sales information storage unit 215 adds an entry and sets the received values ​​to the tenant name 901, space name 903, estimated sales, past sales 905, and shop opening condition information ID 906 of the entry.

[0139] The sales estimation unit 221 determines whether the process has been completed for all spaces (step S1407).

[0140] If it is determined that the processing has not been completed for all spaces, the sales estimation unit 221 returns to step S1402 and executes the same processing.

[0141] If it is determined that processing has been completed for all spaces, the sales estimation unit 221 identifies spaces that meet the store opening conditions and sorts the entries in table 900 corresponding to the identified spaces in descending order of estimated sales (step S1408).

[0142] Specifically, the sales estimation unit 221 identifies spaces whose space characteristics match or are similar to the passerby attributes included in the store opening condition information. The sales estimation unit 221 also acquires entries corresponding to the identified spaces from the sales information storage unit 215, sorts them in descending order of estimated sales, and outputs the sorted results to the sales information storage unit 215.

[0143] Based on the sorting result, the sales information storage unit 215 sets a value in the sort number 902 of the entry corresponding to the identified space.

[0144] The sales estimation unit 221 presents the estimation result to the terminal 105 (step S1409), and ends the sales estimation process.

[0145] Specifically, the sales estimation unit 221 retrieves a predetermined number of entries from the sales information storage unit 215 in ascending order of sort number, and based on the retrieved entries, presents an estimation result to the terminal 105. Note that the estimation result may include space features.

[0146] Through the above processing, the registration support server 100 can present a space that meets the conditions desired by the tenant 101 and a forecast of sales if the tenant 101 opens a store in that space.

[0147] The sales estimation unit 221 may identify spaces that match the store opening condition information before starting the space loop process, and execute the loop process for the identified spaces. In this case, in step S1408, the sales estimation unit 221 executes only sorting based on estimated sales. This allows more effective spaces to be proposed to the tenant 101.

[0148] In step S1408, the sales estimation unit 221 may perform sorting without limiting the space. In this case, it is not necessary to input the store opening conditions. This reduces the input burden on the tenant 101 and allows the tenant 101 to present an estimated sales amount.

[0149] When called by the new post determination unit 222, the sales estimation unit 221 executes the process shown in Fig. 14 for the tenant 101 that has made a new post. In this case, the estimation result does not need to be presented to the terminal 105.

[0150] The registration assistance server 100 executes a learning process for the tenant attribute estimation model and a learning process for the sales estimation model at any timing. Since the models may be learned using a known learning method, detailed description thereof will be omitted.

[0151] As described above, according to this embodiment, the tenant 101 can input account information to know which spaces are most effective for opening a store and the estimated sales that would be generated if the space were used. This allows the tenant 101 to perform a business simulation using the matching system.

[0152] Increasing the number of tenants 101 registered in the matching system has the advantage that the developer can more easily reach various tenants 101. Another advantage is that the operator of the matching system can propose events and the like to the developer along with the tenant attributes of various tenants 101.

[0153] 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.

[0154] Furthermore, some or all of the above-described configurations, functions, processing units, processing means, etc. may be 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 tape, non-volatile memory cards, and ROMs.

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

[0156] 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 the storage medium.

[0157] 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.

Images