JP2021056685A - Real estate information providing system, real estate information providing method and program - Google Patents

Abstract

To provide a real estate information providing system, a real estate information providing method and a program capable of providing a user with more appropriate real estate information by a supplier.SOLUTION: A real estate information providing system 10 that provides real estate information, comprises: first storage means (HDD 14) for storing the real estate information as information about real estate supplied by a supplier; second storage means (HDD 14) for storing desired conditions as conditions desired by a user in real estate; acquisition means (CPU 11) for acquiring the real estate information that meets the desired conditions stored in the second storage means from the first storage means; and presentation means (CPU 11) for presenting the real estate information acquired by the acquisition means to the user.SELECTED DRAWING: Figure 2

Description

The present invention relates to a real estate information providing system, a real estate information providing method, and a program.

Conventionally, when a user searches for information on a desired real estate, for example, as in the technology disclosed in Patent Document 1, information on rent, specific use structure, equipment, and external convenience of the real estate property is registered in a database. , It is common to specify the desired real estate property by searching these items as a search key.

Japanese Unexamined Patent Publication No. 2003-85402

However, in the technology disclosed in Patent Document 1, since the search key can be selected only within the range assumed by the user, for example, when there is a real estate more suitable for an unexpected area, such a real estate is encountered. There is a problem that it cannot be done.

In addition, since the supplier has no choice but to wait for inquiries from users simply by uploading the real estate information to the server, there is also a problem that the real estate to be traded by the supplier cannot be provided to an appropriate user.

The present invention has been made in view of the above circumstances, and provides a real estate information providing system, a real estate information providing method, and a program capable of providing a user with more appropriate real estate information by a supplier. The purpose is.

In order to solve the above problems, the present invention provides a first storage means for storing real estate information as information about real estate supplied by a supplier in a real estate information providing system that provides real estate information, and a user desires the real estate. By the second storage means for storing the desired condition as a condition, the acquisition means for acquiring the real estate information corresponding to the desired condition stored in the second storage means from the first storage means, and the acquisition means. It is characterized by having a presenting means for presenting the acquired real estate information to the user.
With such a configuration, the supplier can provide more appropriate real estate information to the user.

Further, in the present invention, the desired condition includes the nearest station of the workplace and the desired commuting time, and the acquisition means is the real estate information located in the range where the commuting time can be commuting centered on the nearest station of the workplace. Is obtained from the first storage means.
With such a configuration, it is possible to provide information about a property located in an area where the user is not paying attention, based on the commuting time from the station closest to the workplace.

Further, in the present invention, the desired conditions are information on a down payment of a loan, a monthly payment amount, a repayment period, and an interest rate, and the acquisition means obtains real estate information having a price close to the budget calculated from the information. It is characterized in that it is obtained from the first storage means.
According to such a configuration, it is possible to provide real estate information that more reflects the financial power of the user.

Further, in the present invention, the desired condition is information indicating the floor plan and the size, and the acquisition means stores the real estate information having the floor plan and the size close to the information indicating the floor plan and the size as the first storage means. It is characterized by being obtained from.
According to such a configuration, it is possible to provide real estate information suitable for the user by referring to the information regarding the desired floor plan and size.

Further, in the real estate information providing method for providing real estate information, the present invention comprises a first storage step of storing real estate information as information about real estate supplied from a supplier in a storage unit, and as a condition desired by the user for real estate. A second storage step for storing the desired condition in the storage unit, an acquisition step for acquiring the real estate information stored in the storage unit that matches the desired condition from the storage unit, and an acquisition step acquired by the acquisition step. It is characterized by having a presentation step of presenting the real estate information to the user.
According to such a method, the supplier can provide more appropriate real estate information to the user.

Further, the present invention is a first storage means for storing real estate information as information about real estate supplied from a supplier in a computer-readable program that causes a computer to function a real estate information providing process for providing real estate information. , A second storage means for storing a desired condition as a condition desired by the user in the real estate, an acquisition means for acquiring the real estate information that matches the desired condition stored in the second storage means from the first storage means. The real estate information acquired by the acquisition means is made to function as a presentation means to be presented to the user.
Such a program allows the supplier to provide more appropriate real estate information to the user.

According to the present invention, it is possible to provide a real estate information providing system, a real estate information providing method, and a program capable of providing a user with more appropriate real estate information by a supplier.

It is a figure which shows the structural example of the real estate information provision system which concerns on embodiment of this invention. It is a figure which shows the configuration example of the service providing server shown in FIG. It is a figure which shows the configuration example of the supplier terminal and the user terminal shown in FIG. It is a figure which shows an example of the UI which a user registers a desired condition. It is a figure which shows an example of UI which a supplier registers property information. It is a figure which shows an example of the UI which lists and displays the user's desired condition on the supplier side. FIG. 6 is a diagram showing an example of a UI displayed when a predetermined match button is operated in FIG. FIG. 7 is a diagram showing an example of a UI displayed when a predetermined offer button is operated in FIG. 7. FIG. 7 is a diagram showing an example of a UI displayed when a predetermined detail button is operated in FIG. 7. It is a figure which shows an example of the UI which displays a list of registered properties. FIG. 10 is a diagram showing an example of a UI displayed when a match button is operated in FIG. FIG. 10 is a diagram showing an example of a UI displayed when a detail button is operated in FIG. FIG. 12 is a diagram showing an example of a UI displayed when a link for viewing an offer is operated in FIG. 12. It is a flowchart for demonstrating an example of the process which is executed in a service providing server when a supplier accesses. It is a flowchart for demonstrating the detail of the property registration process shown in FIG. It is a flowchart for demonstrating the detail of the desired condition list display processing shown in FIG. It is a flowchart for demonstrating the detail of the registered property list UI display processing shown in FIG. It is a flowchart for demonstrating an example of the process which is executed in a service providing server when a user accesses. It is a flowchart for demonstrating the detail of the desired condition registration process shown in FIG. It is a flowchart for demonstrating the detail of the offer list UI display processing shown in FIG.

Next, an embodiment of the present invention will be described.

(A) Explanation of Configuration of Embodiment of the Present Invention FIG. 1 is a diagram showing a configuration example of a real estate information providing system according to the embodiment of the present invention. In the configuration shown in FIG. 1, the real estate information providing system 1 has a service providing server 10, user terminals 30-1 to 30-2, supplier terminals 50-1 to 50-2, and the Internet 70 as main components. .. In FIG. 1, in order to simplify the drawing, the number of user terminals 30-1 to 30-2 and the number of supplier terminals 50-1 to 50-2 are two, but three or more may be used. Needless to say. Further, two or more service providing servers 10 may be provided.

Here, the service providing server 10 registers real estate information by the supplier terminals 50-1 to 50-2 and supplies the real estate information to the user terminals 30-1 to 30-2.

FIG. 2 is a diagram showing a detailed configuration example of the service providing server 10. As shown in FIG. 2, the service providing server 10 includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an HDD (Hard Disk Drive) 14, and an I / F (Interface). ) 15 and a bus 16.

Here, the CPU 11 executes processing based on the programs stored in the ROM 12 and the HDD 14, and supplies information for displaying a necessary UI (User Interface) to, for example, an accessing user and a supplier. ..

The ROM 12 is a semiconductor storage device that stores basic programs and data executed by the CPU 11.

The RAM 13 is a semiconductor storage device for temporarily storing a program executed by the CPU 11 and data in the middle of calculation.

The HDD 14 is a magnetic storage device that stores programs and data executed by the CPU 11.

The I / F 15 is an interface for inputting information from an input device such as a keyboard (not shown) and exchanging information with the Internet 70.

The bus 16 is a group of signal lines for connecting the CPU 11, ROM 12, RAM 13, HDD 14, and I / F 15 to each other and enabling information exchange between them.

Return to FIG. User terminals 30-1 to 30-2 are terminals owned by a user who receives real estate information, and are composed of, for example, a personal computer or a smartphone. Further, the supplier terminals 50-1 to 50-2 are terminals owned by a supplier who provides real estate information, and are composed of, for example, a personal computer or a smartphone.

FIG. 3 is a diagram showing a configuration example of user terminals 30-1 to 30-2 and supplier terminals 50-1 to 50-2. Since the user terminals 30-1 to 30-2 and the supplier terminals 50-1 to 50-2 have the same configurations, the user terminals 30-1 to 30-2 will be taken as examples below, and these will be referred to as user terminals. It will be described as 30.

The user terminal 30 has a CPU 31, a ROM 32, a RAM 33, an HDD 34, a GPU (Graphics Processing Unit) 35, an I / F 36, a bus 37, and a display device 38.

Here, the CPU 31 executes processing based on the programs stored in the ROM 32 and the HDD 34, accesses the service providing server 10 based on the information input via the I / F 36, for example, and displays the UI. And give and receive information.

The ROM 32 is a semiconductor storage device that stores basic programs and data executed by the CPU 31.

The RAM 33 is a semiconductor storage device for temporarily storing a program executed by the CPU 31 and data in the middle of calculation.

The HDD 34 is a magnetic storage device that stores programs and data executed by the CPU 31.

The GPU 35 executes a drawing process in response to a drawing command supplied from the CPU 31, and supplies the obtained image, video, or the like to the display device 38 for display.

The I / F 36 is an interface for inputting information from an input device such as a keyboard (not shown) and exchanging information with the Internet 70.

The bus 37 is a group of signal lines for connecting the CPU 31, ROM 32, RAM 33, HDD 34, and I / F 36 to each other and enabling information exchange between them.

The display device 38 is composed of, for example, an LCD (Liquid Crystal Display) or the like, and displays an image, a video, or the like supplied from the GPU 35 on the display unit.

Return to FIG. The Internet 70 is a global computer network that connects computers and communication devices all over the world to each other using common communication specifications.

(B) Description of Operation of Embodiment of the Present Invention Next, the operation of the embodiment of the present invention will be described. For example, when a user who is considering purchasing real estate operates the user terminal 30-1 to access the service providing server 10, the service providing server 10 reads a predetermined information stored in the HDD 14 and reads the predetermined information. It is transmitted to the user terminal 30-1 via the I / F15. As a result, for example, the UI as shown in FIG. 4 is displayed on the display device 38. In the following, the user terminal 30-1 will be referred to as the user terminal 30 in order to simplify the description.

In the display example of FIG. 4, a window 100 entitled "Registration of desired conditions" is displayed. In the menu bar at the top of the window 100, "in progress", "offer list", "desired condition registration", "user registration", "logout", and "inquiry" are displayed as menu items. Here, "in progress" is a menu item that is operated when the process related to the offer displays the desired conditions in progress. The "offer list" is a menu item that is operated when displaying a list of offers related to properties that match the registered desired conditions. "Registration of desired conditions" is a menu item operated when registering desired conditions of a property. "User registration" is a menu item that is operated when registering personal information about a user. "Logout" is a menu item that is operated when the user logs out. "Inquiry" is, for example, a menu item that is operated when making an inquiry to the system administrator. When the menu item "Registration of desired conditions" is operated from such a menu, the information shown in FIG. 4 is displayed in the window 100.

In the example of FIG. 4, in the window 100, a text box 101 in which the station closest to the workplace is input, a text box 102 in which the time to the station closest to the workplace is input, a text box 103 in which the commuting time is input, and a budget (up deposit) ) Is entered in the text box 104, the budget (monthly loan amount) is entered in the text box 105, the assumed interest rate of the loan is entered in the text box 106, the repayment period of the loan is entered in the text box 107, and the desired property A pull-down type selection menu 108 where the layout is selected, ^{a text box 109 where the desired property size (m 2} ) is entered, and a pull-down type selection menu 111 where the desired property is selected whether it is new or used. , Button 112 operated when registering the input information, and button 113 operated when returning to the original screen are displayed.

In such a UI, the user inputs desired conditions. In the example of FIG. 4, "Otemachi (Tokyo)" is input to the text box 101, "10 (minutes)" is input to the text box 102, and "30 (minutes)" is input to the text box 103. It is input, "0 (10,000 yen)" is input to the text box 104, "13 (10,000 yen)" is input to the text box 105, and "1.0 (%)" is input to the text box 106. Then, "35 (year)" is input in the text box 107, "3LDK" is selected in the pull-down type selection menu 108, "70 (m ² )" is input in the text box 109, and the pull-down type selection menu is displayed. In 110, "either new or used" is selected, and in the pull-down type selection menu 111, "either apartment or detached house" is selected.

When the button 112 is operated after the information as shown in FIG. 4 is input, the input information is transmitted to the service providing server 10 via the I / F 36.

The service providing server 10 receives the information transmitted from the user terminal 30 and stores it in the HDD 14 in association with the information for identifying the user (for example, the user ID (Identification)).

On the other hand, a supplier who intends to mediate real estate operates, for example, the supplier terminal 50-1 (hereinafter, will be described as the supplier terminal 50 for the sake of brevity) to provide a service for registering property information. When the server 10 is accessed and the menu item "property registration" is operated from the menu bar described later, the UI as shown in FIG. 5 is displayed on the display device 58 of the supplier terminal 50.

In the UI shown in FIG. 5, a window 130 displaying property registration is displayed at the upper part. In the example of FIG. 5, the menu bar of the window 130 has menu items such as "in progress", "desired condition list", "property registration", "property list", "point", "logout", and "O". Inquiry "is displayed. Here, "in progress" is a menu item that is operated when the process related to the offer displays the desired conditions in progress. "Property registration" is a menu item that is operated when registering new property information. The "property list" is a menu item that is operated when displaying a list of registered properties. "Logout" is a menu item that is operated when the supplier logs out. "Inquiry" is, for example, a menu item that is operated when making an inquiry to the system administrator. When the menu item "property registration" is operated from such a menu, the information shown in FIG. 5 is displayed in the window 100.

In FIG. 5, inside the window 130, there are a text box 131 in which the property name is input, a text box 132 in which the nearest station 1 is input, a text box 133 in which the time to the nearest station 1 is input, and the nearest station 2. Text box 134 to be entered, text box 135 to enter the time to the nearest station 2, text box 136 to enter the nearest station 3, text box 137 to enter the time to the nearest station 3, and the location of the property A text box 138 for entering a postal code, a button 139 for entering an address from a postal code, a text box 140 for entering the city, town, and village of the address of the property, and a text for entering the address after the city, town, and village. Box 141, text box 142 where the price of the property is entered, pull-down type selection menu 143 where the layout of the property is selected, ^{text box 144 where the size of the property (m 2} ) is entered, management fee of the property is entered Text box 145, text box 146 for entering the repair cost of the property, text box 147 for entering the floor where the property is located, text box 148 for entering the number of floors of the property, text box 149 for entering the available date of occupancy , Text box 150 for entering the completion date, Text box 151 for entering the number of units in the property, Pull-down selection menu 152 for selecting whether the property is in a state (newly built, used, or any of them), Property Type (apartment, detached house, any of them is acceptable) is entered in the pull-down selection menu 153, the button 154 is operated when attaching a file, the text box 155 in which remarks are entered, and the entered information is registered. The button 156 to be operated in the case and the button 157 to be operated when returning to the original screen are displayed.

In such a UI, the supplier inputs property information. In the example of FIG. 5, "Kasai 1" is input as the property name in the text box 131, "Kasai (station)" is input as the nearest station 1 in the text box 132, and "5 (minutes)" is input as the time in the text box 133. Is entered, "Funabori (station)" is entered as the nearest station 2 in the text box 134, "34 (minutes)" is entered as the time in the text box 135, and "Kasai Rinkai" is entered as the nearest station 3 in the text box 136. "Park (station)" is entered, "40 (minutes)" is entered as the time in the text box 137, "134-0083" is entered as the postal code in the text box 138, and "Tokyo" is entered as the municipality in the text box 140. "Nakakasai, Edogawa-ku" is entered, "○○ chome △△ address" is entered in the text box 141, and "4500 (10,000 yen)" is entered in the text box 142 as the subsequent address. In 143, "3LDK" is selected as the layout, "72 (m ² )" is entered in the text box 144 as the size, and "15,000 (yen / month)" is entered in the text box 145 as the management fee. "5,000 (yen / month)" is entered in the text box 146 as the repair cost, "5 (floor)" is entered in the text box 147 as the location floor, and "10 (story)" is entered in the text box 148 as the number of floors. Is entered, "2019/3/3" is entered in the text box 149 as the available date, "2019/3/3" is entered in the text box 150 as the completion date, and "110" is entered in the text box 151 as the number of units. (Door) ”is input,“ new construction ”is selected in the pull-down type selection menu 152,“ apartment ”is selected in the pull-down type selection menu 153, and the text box 155 is left blank.

When the button 156 is operated after the information shown in FIG. 5 is input, the information input to the UI is transmitted to the service providing server 10 via the I / F 56.

The service providing server 10 receives the information transmitted from the supplier terminal 50 and stores it in the HDD 14 in association with the information for identifying the supplier (for example, the supplier ID).

Next, the supplier operates, for example, the supplier terminal 50 to operate the menu item "desired condition list" displayed on the menu bar of FIG. As a result, the supplier terminal 50 requests the service providing server 10 to display a list of registered desired conditions. As a result, the service providing server 10 acquires the registered desired conditions from the HDD 14 and transmits the registered desired conditions to the supplier terminal 50 via the I / F 15, and the display device 58 of the supplier terminal 50 is provided with, for example, the UI shown in FIG. Is displayed.

In the UI shown in FIG. 6, a window 170 displayed as a desired condition list is displayed at the upper part. In the example of FIG. 6, the menu bar has the same menu items as those of FIG. In the window 170, Table 171 showing a list of desired conditions is displayed. In the example of FIG. 6, in Table 171, "user ID", "station closest to work", "commuting time", "budget", "floor plan", "size", "new / old", "type", And, "Match" is displayed as an item. Specifically, the desired condition at the top where the user ID is "1" corresponds to the condition input in the UI shown in FIG. In the "match" shown on the right side of FIG. 6, buttons (match buttons) for displaying a list of properties corresponding to the desired conditions are displayed. Further, in FIG. 6, the budget is calculated from the down payment of the loan, the monthly loan amount, the assumed interest rate, and the number of years of repayment shown in FIG.

As the order of displaying the desired conditions, for example, the registered date and time may be displayed in the order of newest, or the user's browsing frequency (or browsing time) may be displayed in descending order. Alternatively, the desired conditions of the user who responds to the offer frequently may be displayed with priority. In this way, by preferentially displaying the users who are likely to purchase, the supplier can efficiently make an offer.

In the UI shown in FIG. 6, when the supplier operates the match button with the user ID "1", the supplier terminal 50 sends the list of match properties corresponding to the user ID "1" to the service providing server 10. Request against. As a result, the service providing server 10 searches for the property corresponding to the desired condition in which the user ID is "1", and transmits the information to the supplier terminal 50 together with the information for displaying the UI.

FIG. 7 is an example of the UI displayed on the supplier terminal 50 when the match button of the user ID “1” is operated in the UI shown in FIG. In this example, the menu bar displays the same menu items as in FIG. Further, in the window 190, desired conditions are displayed at the upper part, and matching properties are displayed at the lower part. As the desired conditions, the desired conditions of the user with the user ID "1" selected in FIG. 6 are displayed as Table 191. As the matched property, among the property information registered in the UI as shown in FIG. 5, the property information corresponding to the desired conditions displayed in Table 191 is displayed in a list.

As a method of selecting property information that meets the desired conditions, first, the floor plan, size, new / used, and condominium / detached house are selected. The size is selected in the range of minus α (for example, −5) and plus β (for example, 10) from the desired size. Next, the properties are narrowed down within the range of the budget calculated from the loan amount (“46 million yen” in the example of FIG. 7) plus less than 10 million yen (for example, the range of less than 56 million yen). And finally, it narrows down by commuting time. More specifically, the time obtained by subtracting the time to the nearest station of the workplace entered in the text box 102 from the commuting time entered in the text box 103 of the UI of FIG. 4 is the commuting time of the train. Search for properties that are greater than the sum of (including transfer and walking time inside the station) and the time from the station to the property. Of course, it also includes cases where the commuting time desired by the user is the same as the time required from the workplace to the property, or the required time is longer than the desired commuting time (for example, 5 to 10 minutes). You may do so. The train commuting time can be calculated based on the data registered in advance. Further, as the time from the station to the property, the time entered in the text boxes 133, 135, 137 shown in the UI of FIG. 5 can be used. Since it takes time to calculate the commuting time, the processing load can be reduced by narrowing down the candidates first according to the floor plan, size, new construction / used, and condominium / detached house.

As the order of displaying the matched properties, for example, they are displayed in ascending order of deviation from the user's desired condition, or each of the desired conditions is weighted and displayed based on the evaluation result in consideration of the weighting. Or, the property information can be displayed in descending order of browsing frequency. More specifically, for example, the weight values of commuting time, budget, and size are w1 to w3. Then, when the desired commuting time is x11 and the actual commuting time of the property is x12, the evaluation value of the commuting time is obtained by w1x (x11-x12), the desired budget is x21, and the property price is x22. Then, when the evaluation value of the budget is obtained by w2 × (x21-x22), the desired size is x31, and the size of the property is x32, the evaluation value of the area is calculated by w3 × (x31-x32). Ask for. Then, the property can be evaluated by the total evaluation value E = w1 × (x11-x12) + w2 × (x21-x22) + w3 × (x31-x32), and can be displayed in descending order of the evaluation value. The weight values w1 to w3 may be fixed values, may be optimized for each individual user by using the browsing time or the like as an evaluation value in a direction in which the evaluation value increases, or the user may be an attribute (for example,). It may be grouped according to the presence or absence of a spouse, the presence or absence of children, etc., and optimized for each group.

Further, for the commuting time, the entrance / exit of the station to be used may be specified and the required time may be calculated. Specifically, a station often has a plurality of entrances and exits, and the time often differs depending on the entrance and exit used. Therefore, the doorway may be registered for each station, and the time required for each doorway may also be registered.

In the UI shown in FIG. 7, the "offer" displayed on the right side is a button (offer button) operated when offering (suggesting) the property to the user. The "details" are buttons (detail buttons) that are operated when displaying and confirming the details of the property.

Next, when the supplier operates the offer button corresponding to the name "Kasai 1" in the UI shown in FIG. 7, the UI shown in FIG. 8 is displayed. The UI shown in FIG. 8 has a window 210 at the top indicating that the offer is sent. Menu items similar to those in FIG. 5 are displayed on the menu bar. In the window 210, a text box 211 for displaying the destination, a window 212 for displaying the sender, a window 213 for displaying the property name, a text box 214 for inputting a message about the offer, and the offer are sent. Button 215, which is operated when the button is operated, is displayed. In the UI shown in FIG. 7, when the button 215 is operated after inputting predetermined information (for example, a message regarding an offer), the property is offered to the destination user displayed in the text box 211. An email will be sent.

Further, in the UI shown in FIG. 7, when the detail button is operated, the UI shown in FIG. 9 is displayed. The UI shown in FIG. 9 has a window 230. Menu items similar to those in FIG. 5 are displayed on the menu bar. In the window 230, the property details 231 showing the details of the property registered in the UI of FIG. 5, the property photo 232 selected by the button 154 of the UI of FIG. 5, and the property registered in the UI of FIG. 5 A map 233 centered on the address is displayed. By displaying such a UI of FIG. 7, the supplier can reconfirm the contents of the property and offer it to the user.

Further, when the supplier operates the menu item "property list" from the menu bar shown in FIG. 9, for example, the UI shown in FIG. 10 is displayed. In the display example shown in FIG. 10, the same menu items as in FIG. 5 are displayed. Further, in the window 250, a list of registered properties registered by this supplier is displayed as Table 251. The registered property list is a list of property information registered in the UI as shown in FIG.

On the right side of the window 130 of FIG. 10, an update button, a delete button, a match button, and a detail button are displayed. The update button is a button that is operated when updating the corresponding property information. The delete button is a button that is operated when deleting the corresponding property information. The match button is a button that is operated when offering the property to a predetermined user, and the operation when this button is operated will be described later with reference to FIG. The detail button is a button for displaying detailed information of the property, and when this button is operated, the UI as shown in FIG. 9 is displayed.

When the match button corresponding to "Kasai 1" shown in FIG. 10 is operated, the UI shown in FIG. 11 is displayed. In FIG. 11, menu items similar to those in FIG. 5 are displayed in the menu bar. Further, in the upper part of the window 270, the property information corresponding to "Kasai 1" selected in FIG. 10 is displayed as Table 271. Further, at the lower part of the window 270, the desired conditions matching "Kasai 1" are displayed as Table 272 in a list. As a method of selecting the desired conditions corresponding to the property, as explained in FIG. 7, the commuting time is calculated after narrowing down the candidates by floor plan, size, new construction / used, and condominium / detached house. Identify the applicable desired conditions. The desired conditions identified in this way are listed according to predetermined rules. For example, the registration date and time can be displayed in the order of newest, the total time for browsing the offered property information can be displayed in the order of longest, or the users closest to their own trade area can be displayed in order. Of course, the display order may be determined by a method other than these. Specifically, as described above with reference to FIG. 7, the total evaluation value E of the properties is obtained based on the desired conditions of each user, and the desired total evaluation value E is desired in descending order. The condition may be displayed.

In FIG. 10, for example, when the offer button of a predetermined user is operated, the same UI as in FIG. 8 is displayed, and an offer can be made to the predetermined user.

As described above, the offer by the supplier is made. When the user operates, for example, the "offer list" which is a menu item of the menu bar shown in FIG. 4, the display device 38 of the user terminal 30 displays the UI as shown in FIG.

In the UI shown in FIG. 12, "in progress", "offer list", "change desired conditions", "change user information", "logout", and "inquiry" are displayed as menu items on the menu bar. There is. Since the same as in the case of FIG. 4 except for "change of desired condition" and "change of user information", the description thereof will be omitted. Here, "change desired condition" is a button operated when changing the registered desired condition. Further, the user information change is a button operated when changing the registered user information.

In the window 270 shown in FIG. 12, property information 271 having a property name of "Kasai 1" and property information 272 having a property name of "Kitasenju 1" are displayed. A link is provided in the character string "View offer", and the character string is manipulated when referring to the details of the offer related to each property.

For example, in FIG. 12, when the character string “view offer” relating to the property name “Kitasenju 1” is operated, the UI shown in FIG. 13 is displayed. In the UI of FIG. 13, a menu bar similar to that of FIG. 12 is displayed. Further, in the window 290, Table 291 as an offer list is displayed. Table 291 lists the messages received from the supplier in chronological order. In addition, a "Reply" button and a "Company" button are displayed on the right side of each message. The reply button is a button that is operated when replying to each message. In addition, the company button is operated when displaying detailed information of the company to which the supplier belongs. The user can reply to the offer from the supplier by operating the reply button. By exchanging messages between the supplier and the user in this way, it is possible to promote the user's understanding of the property and carry out a more satisfying transaction.

The user's message input in FIG. 13 is stored in the HDD 14, for example, a morphological analysis process is executed to extract the morpheme included in the message, and the user's preference is specified based on the morpheme. Based on the specified taste, for example, the order in which the property information is displayed in Table 192 of FIG. 7 may be changed.

As described above, according to the embodiment of the present invention, the user can register the desired conditions for the property, and the supplier can transmit the property information satisfying the registered desired conditions. In general, the user often searches for a property near the address where he / she currently resides, but according to this embodiment, the user finds a property located within a desired commuting time centered on the workplace. be able to. In addition, as commuting time, we decided to comprehensively judge the time from the workplace to the nearest station, the travel time by train (including transfer time), and the time from the nearest station to the property. You can select properties based on accurate commuting time.

In addition, as a supplier, after the conventional system has registered a property, it has only waited for inquiries from users, but it is possible to propose the most suitable property based on the desired conditions of the registered user. it can. In addition, when displaying a list of desired conditions, it is possible to efficiently proceed with the transaction by processing so that the user who has a higher probability of making a contract is displayed at the top based on the user's information, browsing history, and the like.

Next, an example of the processing executed in the embodiment of the present invention will be described with reference to FIGS. 14 to 20.

FIG. 14 is a flowchart for explaining an example of processing executed when the supplier operates the supplier terminal 50 to access the service providing server 10. When the processing of the flowchart shown in FIG. 14 is started, the following steps are executed.

In step S10, the CPU 11 determines whether or not there is a login request from the supplier terminal 50 via the Internet 70, and if it is determined that there is a login request (step S10: Y), the process proceeds to step S11. In other cases (step S10: N), the process ends.

In step S11, the CPU 11 executes an authentication process for the supplier ID and password supplied from the supplier terminal 50, and if it is determined that these match the registered information (step S11: Y), the step S12 is performed. The process proceeds, and in other cases (step S11: N), the process ends.

In step S12, the CPU 11 determines whether or not the menu item "property registration" is selected from the menu bar and an instruction to register the property is given, and if property registration is selected (step S12: Y), 13 In other cases (step S12: N), the process proceeds to step S14.

In step S13, the CPU 11 executes the property information registration process for registering the property information. The details of this process will be described in detail with reference to FIG.

In step S14, the CPU 11 determines whether or not the menu item "desired condition list" is selected from the menu bar and is instructed to display the desired condition list, and when the desired condition list is selected (step S14: Y). ), And in other cases (step S14: N), the process proceeds to step S16.

In step S15, the CPU 11 executes a desired condition list display process for displaying the desired condition list. The details of this process will be described in detail with reference to FIG.

In step S16, the CPU 11 determines whether or not the menu item "registered property list" is selected from the menu bar and is instructed to display the registered property list UI, and when the registered property list is selected (step S16: In Y), the process proceeds to 17, and in other cases (step S16: N), the process proceeds to step S18.

In step S17, the CPU 11 executes the registered property list UI display process for displaying the registered property list UI. The details of this process will be described in detail with reference to FIG.

In step S18, the CPU 11 determines whether or not to end the process, and if it is determined not to end (step S18: N), the CPU 11 returns to step S12 and repeats the same process as described above, and other than that. In the case (step S18: Y), the process ends.

Next, with reference to FIG. 15, the details of the “property information registration process” in step S13 shown in FIG. 14 will be described. When the process shown in FIG. 15 is started, the following steps are executed.

In step S30, the CPU 11 transmits predetermined information stored in the HDD 14 to the supplier terminal 50 via the I / F 15 and the Internet 70, and causes the display device 58 to display the property registration UI. As a result, the UI as shown in FIG. 5 is displayed.

In step S31, the CPU 11 determines whether or not the registration button 156 has been operated after the predetermined information has been input in the UI as shown in FIG. 5, and if it is determined that the registration button 156 has been operated (step S31: Y). Proceeds to step S32, and in other cases (step S31: N), the same process is repeated.

In step S32, the CPU 11 acquires the property information input in the UI as shown in FIG. 5 via the Internet 70 and the I / F15, and registers the property information in the predetermined area of the HDD 14 in association with the supplier ID.

In step S33, the CPU 11 determines whether or not to end the process, and if it is determined not to end (step S33: N), the CPU 11 returns to step S30 and repeats the same process as described above, and other than that. In the case (step S33: Y), the process ends.

Next, with reference to FIG. 16, the details of the “desired condition list display process” in step S15 shown in FIG. 14 will be described. When the process shown in FIG. 16 is started, the following steps are executed.

In step S50, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the supplier terminal 50 via the I / F 15 and the Internet 70, and causes the display device 58 to display the desired condition list list UI. As a result, the UI window 170 as shown in FIG. 6 is displayed.

In step S51, the CPU 11 acquires desired conditions registered by a plurality of users. More specifically, the CPU 11 acquires the desired conditions of the user registered in the HDD 14.

In step S52, the CPU 11 sorts and displays the desired conditions acquired in step S51, for example, in order of newest registration date and time. As a result, for example, as shown in FIG. 6, the desired conditions are displayed in Table 171 in the window 170 in the order of newest registration date and time. The registration date and time is an example, and the display order may be determined based on other conditions. For example, the items may be sorted and displayed in descending order of frequency of browsing by the user, or may be displayed in order of earliest scheduled purchase time of the property (entered as necessary).

In step S53, the CPU 11 determines whether or not the match button has been operated, and if it determines that the match button has been operated (step S53: Y), the process proceeds to step S54, and in other cases (step S53: N). ) Repeats the same process. For example, when the predetermined match button shown in FIG. 6 is operated, it is determined as Y and the process proceeds to step S54.

In step S54, the CPU 11 acquires property information satisfying the desired conditions. More specifically, the CPU 11 narrows down the candidates by floor plan, size, new construction / used, and condominium / detached house from the property information stored in the HDD 14, and then determines the commuting time to the workplace. Calculate and obtain property information that meets the requirements.

In step S55, the CPU 11 sorts the property information acquired in step S54 in the order in which the conditions are met, for example. For example, a weight value may be set for each condition, and if the condition is satisfied, the corresponding weight value may be added to obtain the evaluation value and sort in descending order of the evaluation value.

In step S56, the CPU 11 displays the property information sorted in step S55. As a result, for example, as shown in FIG. 7, property information is displayed in a list.

In step S57, the CPU 11 determines whether or not the detail button has been operated, and if it determines that the detail button has been operated (step S57: Y), the process proceeds to step S58, and in other cases (step S57: N). ) Proceeds to step S60.

In step S58, the CPU 11 acquires the detailed information of the property corresponding to the detail button operated in step S57 from the HDD 14, and displays the property detail UI as shown in FIG. 9 on the display device 58 of the supplier terminal 50.

In step S59, the CPU 11 determines whether or not to end the process, and if it is determined to end the process (step S59: Y), the process proceeds to step S60, and in other cases (step S59: N). The process returns to step S58 and the same process is repeated.

In step S60, the CPU 11 determines whether or not the offer button has been operated, and if it is determined that the offer button has been operated (step S60: Y), the process proceeds to step S61, and in other cases (step S60: N). The process returns to step S57 and the same process as described above is repeated.

In step S61, the CPU 11 acquires predetermined information from the HDD 14 and causes the display device 58 of the supplier terminal 50 to display the offer UI. As a result, for example, the offer UI as shown in FIG. 8 is displayed.

In step S62, the CPU 11 determines whether or not the offer transmission button 215 of the offer UI has been operated, and if the offer transmission button 215 determines that the operation has been performed (step S62: Y), the process proceeds to step S63, and the other steps are taken. In the case (step S62: N), the process returns to step S61 and the same process as described above is repeated.

In step S63, the CPU 11 transmits the offer input in the offer UI to the user set as the destination.

Next, with reference to FIG. 17, the details of the “registered property list UI display process” in step S17 shown in FIG. 14 will be described. When the process shown in FIG. 17 is started, the following steps are executed.

In step S70, the CPU 11 acquires predetermined information from the HDD 14 and causes the display device 58 of the supplier terminal 50 to display the registered property list UI. As a result, for example, the window 250 as shown in FIG. 10 is displayed on the display device 58.

In step S71, the CPU 11 acquires the property information from the HDD 14. As a result, the property information input by the UI as shown in FIG. 5 is acquired.

In step S72, the CPU 11 displays the property information acquired in step S71, for example, in descending order of the number of applicable desired conditions. As a result, for example, the UI as shown in FIG. 10 is displayed on the display device 58. It should be noted that the desired conditions may be displayed in ascending order or in ascending order as the registration date and time, instead of in descending order.

In step S73, the CPU 11 determines whether or not the update button shown in FIG. 10 has been operated, and if it is determined that the update button has been operated (step S73: Y), the process proceeds to step S74, and in other cases (step S73: Y). Step S73: N) proceeds to step S75.

In step S74, the CPU 11 executes a process of updating the property information corresponding to the operated update button. More specifically, the UI as shown in FIG. 5 can be displayed and the information can be updated.

In step S75, the CPU 11 determines whether or not the delete button shown in FIG. 10 has been operated, and if it is determined that the delete button has been operated (step S75: Y), the process proceeds to step S76, and in other cases (step S75: Y). Step S75: N) proceeds to step S77.

In step S76, the CPU 11 executes a process of deleting the property information corresponding to the operated delete button. More specifically, the CPU 11 deletes the property information corresponding to the delete button from the HDD 14.

In step S77, the CPU 11 determines whether or not the match button shown in FIG. 10 has been operated, and if it is determined that the match button has been operated (step S77: Y), the process proceeds to step S78, and in other cases (step S77). In step S77: N), the process returns to step S73 and the same process as described above is repeated.

In step S78, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the supplier terminal 50, and displays the match desired condition UI on the display device 58. As a result, for example, the window 270 as shown in FIG. 11 is displayed.

In step S79, the CPU 11 acquires desired conditions satisfying the conditions from the HDD 14. For example, in FIG. 10, when the match button of Kasai 1 is operated, the property information of Kasai 1 is acquired, and the desired conditions for which the property information satisfies the condition are acquired from the HDD 14.

In step S80, the CPU 11 sorts the desired conditions acquired in step S79 based on, for example, the past browsing history of the user. For example, the desired conditions are sorted in descending order of the number of browsing times or the browsing time. In addition, you may sort based on the registration date and time of the desired condition instead of the number of browsing times or the browsing time.

In step S81, the CPU 11 lists the desired conditions sorted in step S80 in the match desired condition UI. As a result, as shown in FIG. 11, the desired conditions are listed.

In step S82, the CPU 11 determines whether or not the detail button as shown in FIG. 10 has been operated, and if it is determined that the detail button has been operated (step S82: Y), the process proceeds to step S83, and the other steps are taken. In the case (step S82: N), the process proceeds to step S85.

In step S83, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the supplier terminal 50, and causes the display device 58 to display the detailed information UI of the property. As a result, for example, the UI as shown in FIG. 9 is displayed.

In step S84, the CPU 11 determines whether or not to end the process, and if it is determined to end the process (step S84: Y), the process proceeds to step S85, and in other cases (step S84: N). The process returns to step S83 and the same process as described above is repeated.

In step S85, the CPU 11 determines whether or not the offer button shown in FIG. 10 has been operated, and if it is determined that the offer button has been operated (step S85: Y), the process proceeds to step S86, and in other cases (step S85: Y). In step S85: N), the process returns to step S82 and the same process as described above is repeated.

In step S86, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the supplier terminal 50, and displays the offer UI on the display device 58. As a result, for example, the UI as shown in FIG. 8 is displayed.

In step S87, the CPU 11 determines whether or not the offer transmission button shown in FIG. 8 has been operated, and if it determines that the offer transmission button has been operated (step S87: Y), the process proceeds to step S88, and the other steps are taken. In the case (step S87: N), the process returns to step S86 and the same process as described above is repeated.

In step S88, the CPU 11 transmits the information input in the offer UI to the destination user. As a result, for example, the information input in FIG. 8 is transmitted to the destination user.

FIG. 18 is a flowchart for explaining an example of processing executed when the user operates the user terminal to access the service providing server 10. When the processing of the flowchart shown in FIG. 18 is started, the following steps are executed.

In step S90, the CPU 11 determines whether or not there is a login request from the user terminal 30 via the Internet 70, and if it is determined that there is a login request (step S90: Y), the process proceeds to step S91. In other cases (step S90: N), the process ends.

In step S91, the CPU 11 executes an authentication process for the supplier ID and password supplied from the user terminal 30, and if it is determined that these match the registered information (step S91: Y), the step S92 is performed. The process proceeds, and in other cases (step S91: N), the process ends.

In step S92, the CPU 11 determines whether or not to register the desired condition, and if it is determined to register the desired condition (step S92: Y), the process proceeds to step S93, and in other cases (step S92: N). To step S94. For example, when the desired condition registration, which is a menu item of the menu bar shown in FIG. 4, is operated, it is determined as Y and the process proceeds to step S93.

In step S93, the CPU 11 executes the "desired condition registration process" for registering the desired condition. The details of this process will be described later with reference to FIG.

In step S94, the CPU 11 determines whether or not to display the offer list UI, and if it is determined to display the offer list UI (step S94: Y), the process proceeds to step S95, and in other cases (step S94: In N), the process proceeds to step S96. For example, when the "offer list", which is a menu item of the menu bar shown in FIG. 4, is operated, it is determined as Y and the process proceeds to step S95.

In step S95, the CPU 11 executes the "offer list display UI display process" for displaying the offer list display UI. The details of this process will be described later with reference to FIG.

In step S96, the CPU 11 determines whether or not to end the process, ends the process when it is determined to end the process (step S96: Y), and ends the process in other cases (step S96: N). The process returns to step S92 and the same process as described above is repeated.

Next, with reference to FIG. 19, the details of the “desired condition registration process” shown in step S93 of FIG. 18 will be described. When the processing of the flowchart of FIG. 19 is started, the following steps are executed.

In step S110, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the user terminal 30, and displays the desired condition registration UI on the display device 38. As a result, for example, the UI as shown in FIG. 4 is displayed.

In step S111, the CPU 11 determines whether or not the registration button 112 shown in FIG. 4 has been operated, and if it is determined that the registration button 112 has been operated (step S111: Y), the process proceeds to step S112, and other than that. In the case (step S111: N), the same process is repeated.

In step S112, the CPU 11 acquires, for example, the information input in the desired condition registration UI as shown in FIG. 4, and records it in the HDD 14 in association with the user ID.

In step S113, the CPU 11 determines whether or not to end the process, ends the process when it is determined to end the process (step S113: Y), and ends the process in other cases (step S113: N). The process returns to step S110 and the same process as described above is repeated.

Next, with reference to FIG. 20, the details of the “offer list UI display process” shown in step S95 of FIG. 18 will be described. When the processing of the flowchart of FIG. 20 is started, the following steps are executed.

In step S130, the CPU 11 acquires predetermined information from the HDD 14, transmits it to the user terminal 30, and displays the offer list UI on the display device 38. As a result, for example, the window 270 as shown in FIG. 12 is displayed.

In step S131, the CPU 11 acquires the offer transmitted from the HDD 14 to the user. More specifically, for example, the offer entered in the UI as shown in FIG. 8 is acquired.

In step S132, the CPU 11 sorts and displays the offers acquired in step S131 in descending order of frequency of browsing by other users, for example. As a result, as shown in FIG. 12, a UI displaying a list of offers is displayed. It should be noted that sorting may be performed based on a criterion other than the browsing frequency (for example, the length of the browsing time or the old and new posting date and time).

In step S133, the CPU 11 determines whether or not the "view offer" link as shown in FIG. 12 has been operated, and if it is determined that the link has been operated (step S133: Y), the process proceeds to step S134, otherwise the process proceeds to step S134. In the case of (step S133: N), the same process is repeated.

In step S134, the CPU 11 acquires the offer corresponding to the link for viewing the manipulated offer from the HDD 14. For example, when the link for viewing the offer of Kasai 1 shown in FIG. 12 is operated, the offer related to Kasai 1 is acquired.

In step S135, the CPU 11 causes the user terminal 30 to display the offer acquired in step S134. As a result, for example, the UI as shown in FIG. 13 is displayed on the display device 38 of the user terminal 30.

In step S136, for example, the CPU 11 determines whether or not the company button as shown in FIG. 13 has been operated, and if it is determined that the company button has been operated (step S136: Y), the process proceeds to step S137, and in other cases. In (step S136: N), the process proceeds to step S139.

In step S137, the CPU 11 acquires the information related to the company button operated in step S136 from the HDD 14, and causes the display device 38 of the user terminal 30 to display the company detailed information UI. As a result, information about the supplier company that provides the property information is displayed on the display device 38.

In step S138, the CPU 11 determines whether or not to end the process, and if it is determined to end the process (step S138: Y), the process proceeds to step S139, and in other cases (step S138: N). The process returns to step S137 and the same process as described above is repeated.

In step S139, the CPU 11 determines whether or not the response button has been operated, and if it is determined that the response button has been operated (step S139: Y), the process proceeds to step S140, and in other cases (step S139: N). The process returns to step S136 and the same process as described above is repeated. For example, when the response button as shown in FIG. 13 is operated, it is determined as Y and the process proceeds to step S140.

In step S140, the CPU 11 acquires predetermined information from the HDD 14 and displays the response UI on the display device 38 of the user terminal 30. As a result, for example, the same UI as in FIG. 8 is displayed on the display device 38.

In step S141, the CPU 11 determines whether or not the response transmission button has been operated, and if it is determined that the response transmission button has been operated (step S141: Y), the process proceeds to step S142, and in other cases (step S141: N). Returns to step S140 and repeats the same process. As a result, for example, when the response transmission button (not shown) displayed on the UI similar to FIG. 8 is operated, it is determined as Y and the process proceeds to step S142.

In step S142, the CPU 11 transmits the information input in the response UI to the destination supplier.

As described above, according to the flowcharts shown in FIGS. 14 to 20, the operation of the above-described embodiment can be realized.

(C) Description of Modified Embodiments It goes without saying that each of the above embodiments is an example, and the present invention is not limited to the cases described above. For example, in the above example, real estate information related to for-sale properties has been described as an example, but it is also possible to handle real estate information related to rental properties. In the case of a rental property, the rental property can be targeted for transaction by registering the rent, security deposit, and key money as desired conditions instead of the loan as a budget.

Further, in the above embodiment, the commuting time includes the time from the workplace to the nearest station, the time from the nearest station to the nearest station of the property (including the transfer time), and the time to the nearest station of the property. The total time is the total time, but the time related to the doorway to be used may also be included. That is, since the distance and time may change depending on the doorway used, which doorway to use may be included in the desired conditions. Furthermore, the commuting time is calculated by summing the time from the doorway to boarding, the boarding time, the transfer time (calculated for each route), the time from getting off to the doorway, and the time from the doorway to the property. You may do so. Desirably, the car number of the train to be boarded may be specified when determining the time to transfer or the entrance / exit of the station. This makes it possible to obtain a more accurate commuting time.

Further, in the above embodiment, the supplier selects and offers the property information, but such a process may be automatically executed. For example, user attribute information (for example, occupation, life pattern, income, family structure, current residence area, etc.) is registered, and the property is also included in the property information (for example, address, age, new / used, location, etc.). Group based on. Then, the attribute information of the user who purchased the property may be associated with the group to which the purchased property belongs, and the property belonging to the same group may be offered to the user having the same attribute information. Further, for the group, the optimum grouping may be set by the learning process. According to such a configuration, the learning process progresses as the data is accumulated, and more appropriate grouping becomes possible.

In addition, instead of selecting the property to be offered from the attribute information of other users who purchased the property, for example, the offer is made from the browsing history (for example, browsing frequency, browsing time, etc.) of the property information of the user who is the target of the offer. You may try to narrow down the property information to be done. For example, different property A and property B may be offered, and if property A has a longer browsing time, another property C having the same attributes as property A may be offered.

Further, instead of performing everything automatically, the property information candidates may be automatically selected, and the property information selected by the supplier from the selected candidates may be offered to the user.

The flowcharts shown in FIGS. 14 to 20 are examples, and the present invention is not limited to the flowcharts shown in FIGS. 14 to 20.

1 Real estate information provision system 10 Service provision server 11 CPU
12 ROM
13 RAM
14 HDD
15 I / F
16 Bus 30-1, 30-2 User terminal 31 CPU
32 ROM
33 RAM
34 HDD
35 GPU
36 I / F
37 Bus 38 Display device 50-1, 50-2 Supplier terminal 51 CPU
52 ROM
53 RAM
54 HDD
55 GPU
56 I / F
57 Bus 58 Display 70 Internet

Claims (6)

In the real estate information provision system that provides real estate information
The first storage means for storing real estate information as information about real estate supplied by the supplier,
A second storage means for storing desired conditions as conditions desired by the user in real estate, and
An acquisition means for acquiring the real estate information stored in the second storage means that meets the desired conditions from the first storage means, and
A presenting means for presenting the real estate information acquired by the acquiring means to the user, and
A real estate information provision system characterized by having. The desired conditions include the nearest station to the workplace and the desired commuting time.
The acquisition means acquires real estate information located in a range where commuting can be performed during the commuting time from the first storage means, centering on the station closest to the workplace.
The real estate information providing system according to claim 1. The desired conditions are information on the down payment, monthly payment amount, repayment period, and interest rate of the loan.
The acquisition means acquires real estate information having a price close to the budget calculated from the information from the first storage means.
The real estate information providing system according to claim 1 or 2. The desired condition is information indicating the floor plan and the size, and is
The acquisition means acquires real estate information having a floor plan and a size close to the information indicating the floor plan and the size from the first storage means.
The real estate information providing system according to any one of claims 1 to 3, characterized in that. In the method of providing real estate information that provides real estate information,
The first storage step of storing real estate information as information about real estate supplied by the supplier in the storage unit,
A second storage step of storing the desired condition as a condition desired by the user in the real estate in the storage unit, and
An acquisition step of acquiring the real estate information stored in the storage unit that meets the desired conditions from the storage unit, and
A presentation step of presenting the real estate information acquired by the acquisition step to the user,
A method of providing real estate information, which is characterized by having. In a computer-readable program that allows a computer to perform real estate information provision processing that provides real estate information
The computer
First storage means for storing real estate information as information about real estate supplied by the supplier,
A second storage means for storing desired conditions as conditions desired by the user in real estate,
An acquisition means for acquiring the real estate information stored in the second storage means that meets the desired conditions from the first storage means.
A presenting means for presenting the real estate information acquired by the acquiring means to the user,
A computer-readable program characterized by acting as.

Images