Property management system and property management method

The property management system addresses the lack of post-purchase utilization by integrating rental management, enabling users to efficiently rent out their properties, thus optimizing property utilization.

JP2026116337APending Publication Date: 2026-07-09NOT A HOTEL INC

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
NOT A HOTEL INC
Filing Date
2026-04-23
Publication Date
2026-07-09

AI Technical Summary

Technical Problem

Conventional systems for managing real estate properties only support the decision to purchase or lease, without considering how the property will be utilized thereafter.

Method used

A property management system and method that includes a management server connected to user terminals via a network, featuring a sales processing unit for purchasing real estate and a rerent processing unit for lending the property to others, enabling effective utilization through rental management.

Benefits of technology

Enables effective utilization of real estate properties by allowing users to rent out their purchased properties, enhancing the system's functionality beyond mere purchase or lease decisions.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026116337000001_ABST
    Figure 2026116337000001_ABST
Patent Text Reader

Abstract

This invention provides a new property management system and property management method that enables the effective utilization of real estate properties. [Solution] A property management system in one aspect of the present invention is characterized in that a management server for managing information on real estate properties and a user terminal are connected via a network, and the management server comprises a sales processing unit that processes information related to the procedure for purchasing real estate properties by a user based on a purchase request from the user terminal, and a lending processing unit that processes information related to lending the real estate properties purchased by the user to others based on a lending request from the user terminal.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a property management system and a property management method.

Background Art

[0002] Conventionally, a system has been known that can obtain information regarding the sale, purchase, or lease of real estate properties by accessing a management server from a user terminal via the Internet.

[0003] For example, Patent Document 1 discloses a system that presents information on real estate properties that can be sold, purchased, or leased based on various conditions specified by a user. According to such a system, information on real estate properties based on the user's wishes can be obtained, and the decision to purchase or lease a real estate property can be supported.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] However, in the conventional system as described above, it only supports the decision to purchase or lease a real estate property, and does not consider how the user will use the real estate property thereafter.

[0006] Therefore, an object of the present invention is to provide a novel property management system and a property management method that enable effective utilization of real estate properties.

Means for Solving the Problems

[0007] The property management system according to one aspect of the present invention is A management server that manages real estate property information and user terminals are connected via a network. The aforementioned management server A sales processing unit that processes information related to the user's purchase procedure for the real estate property based on a purchase request from the user terminal, The system is characterized by comprising a rerent processing unit that, based on a loan request from the user terminal, performs processing of information regarding the lending of the real estate property purchased by the user to another party. [Effects of the Invention]

[0008] According to the present invention, it is possible to provide a novel property management system and property management method that enable the effective utilization of real estate properties. [Brief explanation of the drawing]

[0009] [Figure 1] This is a block diagram showing a property management system according to one embodiment of the present invention. [Figure 2] Figure 1 is a functional block diagram showing the server device. [Figure 3] Figure 1 is a functional block diagram showing the user terminal. [Figure 4] This figure shows an example of user data stored on a server device. [Figure 5] This figure shows an example of real estate property data stored on a server device. [Figure 6] This figure shows an example of recurrent data stored in a server device. [Figure 7] This is an example of a flowchart relating to a property management method according to one embodiment of the present invention. [Figure 8] This figure shows an example of a user interface screen displayed on a user terminal according to one embodiment of the present invention. [Figure 9] This figure shows another example of a user interface screen displayed on a user terminal according to one embodiment of the present invention. [Figure 10]FIG. showing still another example of a user interface screen displayed on a user terminal according to an embodiment of the present invention. [Figure 11] FIG. showing an example of a flowchart related to a property management method according to an embodiment of the present invention. [Figure 12] FIG. showing still another example of a user interface screen displayed on a user terminal according to an embodiment of the present invention. [Figure 13] FIG. showing still another example of a user interface screen displayed on a user terminal according to an embodiment of the present invention. [Figure 14] FIG. showing an example of a flowchart related to a property management method according to an embodiment of the present invention. [Figure 15] FIG. showing still another example of a user interface screen displayed on a user terminal according to an embodiment of the present invention. [Figure 16] FIG. showing still another example of a user interface screen displayed on a user terminal according to an embodiment of the present invention.

MODE FOR CARRYING OUT THE INVENTION

[0010] Hereinafter, embodiments of the present invention will be described with reference to the drawings. Note that the embodiments described below do not unduly limit the content of the present disclosure described in the claims. Also, not all of the components shown in the embodiments are essential components of the present disclosure.

[0011] (Embodiment 1) <Configuration> FIG. 1 is a block configuration diagram showing a property management system according to an embodiment of the present invention. This property management system 1 (hereinafter also referred to as "this system") includes a server device 100 as a management server that manages information on real estate properties (hereinafter also referred to as "properties"), and user terminals 200 used by users (for example, "owners" described later) who are users of the property management service using this system 1. Note that, as shown in FIG. 1, this system 1 is assumed to include user terminals 300 used by other users (for example, "guests" described later) who use this service, but is not limited thereto. Also, "real estate property" here includes various buildings such as single-family houses, condominiums, apartments, villas, etc. and land, regardless of the number of floors, structure, size, and area of the building.

[0012] The server device 100, the user terminals 200 and 300 are each connected via a network NW. The network NW is composed of the Internet, an intranet, a wireless LAN (Local Area Network), a WAN (Wide Area Network), etc.

[0013] The server device 100 is managed, for example, by a system administrator (service provider). Based on a purchase request from a user terminal, the server device 100 executes processing of information associated with the purchase procedure of a real estate property by the user. The server device 100 can, for example, generate and output a list of real estate properties available for sale based on a purchase request from a user terminal used by a user who is a service user. In this embodiment, the real estate property subject to sale is owned by the service provider until it is purchased by the user, but is not limited thereto. Also, the "service provider" and the "user" may each be a natural person or a legal entity.

[0014] Furthermore, the server device 100 receives rental requests from user terminals and processes information regarding the rental of real estate properties purchased by the user to others based on those rental requests. For example, the server device 100 can generate and output a rental schedule input screen for users who own real estate properties purchased using this service, allowing them to rent out the property to others.

[0015] The server device 100 is, for example, a computer (information processing device), and may be a general-purpose computer such as a workstation or personal computer, or it may be logically implemented by cloud computing. In this embodiment, for the sake of explanation, one server device is given as an example, but it is not limited to this, and there may be multiple devices.

[0016] The user terminal 200 is used by users who purchase real estate properties using the services provided by the service provider mentioned above. The user terminal 200 can be, for example, an information processing device such as a personal computer, tablet, smartphone, mobile phone, or PDA.

[0017] In this embodiment, System 1 is described as having a server device 100 and a user terminal 200, and the user performs operations on the server device 100 using the user terminal 200. However, the server device 100 may be configured as a standalone unit and may have functions that allow the user to operate it directly.

[0018] Figure 2 is a functional block diagram of the server device 100 shown in Figure 1. The server device 100 comprises a communication unit 110, a storage unit 120, and a control unit 130.

[0019] The communication unit 110 is a communication interface for communicating with user terminals 200 and 300 via the network NW, and communication is performed using a communication protocol such as TCP / IP (Transmission Control Protocol / Internet Protocol).

[0020] The storage unit 120 stores programs for executing various control processes and functions within the control unit 130, input data, etc., and is composed of RAM (Random Access Memory), ROM (Read Only Memory), etc. The storage unit 120 also has a user data storage unit 121 for storing various data related to the user, a property data storage unit 122 for storing various data related to real estate properties, and a relent data storage unit 123 for storing various data related to relent services provided to the user. Furthermore, the storage unit 120 can also temporarily store data obtained through communication with the user terminal 200. A database (not shown) containing various data may be constructed outside the storage unit 120 or outside the server device 100. Relent services refer to a service in which a user who has purchased a real estate property whose information is managed by the server device 100 temporarily rents out the real estate property to others as accommodation or event space, etc., through this system 1.

[0021] The control unit 130 controls the overall operation of the server device 100 by executing programs stored in the memory unit 120, and is composed of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc. The functions of the control unit 130 include an instruction receiving unit 131 that receives instructions (requests) from the user terminal 200, a user data management unit 132 that refers to and processes various data related to the user, a property data management unit 133 that refers to and processes various data related to real estate properties, a relent data management unit 134 that refers to and processes data related to relent services, a sales processing unit 135 that generates information related to the buying and selling of real estate properties based on the above various data and provides it to the user terminal 200, and a relent processing unit 136 that generates information related to relent services, in which real estate properties are leased to others after being sold to a user, based on the above various data and provides it to the user terminal 200, etc. The instruction receiving unit 131, user data management unit 132, property data management unit 133, relent data management unit 134, sales processing unit 135, and relent processing unit 136 are activated by programs stored in the storage unit 120 and executed by the server device 100, which is a computer (electronic calculator).

[0022] The instruction receiving unit 131 receives instructions from the user terminal 200 via the communication unit 110 when the user makes a predetermined request (by entering characters or numbers, pressing (selecting) icons such as various buttons, etc.) through a user interface such as a screen displayed on the user terminal 200 via a web browser or application, which is provided by the server device 100.

[0023] The User Data Management Unit 132 manages and processes various data related to users. This data may include, but is not limited to, user ID, basic user information (user's name, address, telephone number, email address, and other contact information, age, gender, etc.), purchased property information, payment information (payment history, credit card information, financial institution information, etc.), point information (amount of points usable within this system, point information (usage / acquisition) history, etc.), and Relent Service usage history information (history of using Relent Services in this system 1).

[0024] The property data management unit 133 manages and processes various types of data related to real estate properties. These various types of data may include, but are not limited to, property IDs, basic information, facility information, and surrounding area information.

[0025] The Relent Data Management Unit 134 manages and processes various data related to the Relent service (for example, as shown in Figure 6, information on properties available for rent (property ID, owner information (user ID, etc.)), rental period information, usage conditions information (restrictions on use, number of people, gender restrictions, etc.), usage information (whether or not it was used, user information), payment information, and vacancy plan information (use, period, fee, etc.).

[0026] The sales processing unit 135 generates information related to the buying and selling of real estate properties based on requests from the user and various data stored in the storage unit 120, and provides it to the user terminal 200. For example, based on a purchase request from the user terminal, the sales processing unit 135 processes information related to the user's procedure for purchasing real estate properties.

[0027] The relent processing unit 136 generates information related to the relent service, which involves leasing a real estate property to others after its sale to a user, based on requests from the user and various data stored in the storage unit 120, and provides this information to the user terminal 200. For example, based on a leasing request from the user terminal 200, the relent processing unit 136 processes information regarding the leasing of the real estate property purchased by the user to others.

[0028] Furthermore, the Relent Processing Unit 136 can, for example, generate a vacancy plan based on a user request and provide it to user terminals 200 and 300. A vacancy plan is planning information that includes various conditions for renting out a property to another party for which a rental request has been made by the owner (the server device 100 has received the rental request). The vacancy plan includes information related to the Relent service, such as the rental period (start date and time of use, end date and time of use, number of nights, etc.), information on the purpose of use (whether or not there are restrictions on the purpose of use such as accommodation, event use, conference use, office work use, etc., and the content of those restrictions), the target of rental (whether or not there are restrictions on the number of guests, age, gender, etc., and the content of those restrictions), and the price. The Relent Processing Unit 136 can store the generated vacancy plan information in the Relent Data Storage Unit 123 via the Relent Data Management Unit 134.

[0029] Figure 3 is a functional block diagram showing the user terminal 200 in Figure 1. The user terminal 200 comprises a communication unit 210, a display operation unit 220, a storage unit 230, and a control unit 240.

[0030] The communication unit 210 is a communication interface for communicating with the communication unit 110 of the server device 100 via the network NW, and communication is performed using a communication protocol such as TCP / IP.

[0031] The display operation unit 220 is a user interface used to display text, images, etc., in response to user input (requests) from the control unit 240. If the user terminal 200 is a personal computer, it consists of a display and a keyboard or mouse. If the user terminal 200 is a smartphone or tablet, it consists of a touch panel, etc. This display operation unit 220 is activated by a control program stored in the storage unit 230 and executed by the control unit 240 of the user terminal 200, which is a computer (electronic calculator).

[0032] The memory unit 230 stores programs for executing various control processes and functions within the control unit 240, input data, etc., and is composed of RAM, ROM, etc. The memory unit 230 also temporarily stores the contents of communication with the server device 100.

[0033] The control unit 240 controls the overall operation of the user terminal 200 by executing programs stored in the memory unit 230, and is composed of a CPU, GPU, etc.

[0034] The server device 100 may also be configured to include a display and operation unit.

[0035] Figure 4 shows an example of user data stored in the server device 100.

[0036] The user data 1000 shown in Figure 4 includes various data related to the user and is stored in the user data storage unit 121. In Figure 4, for the sake of explanation, an example of one user (a user identified by user ID "10001") is shown, but it can include information for multiple users. Examples of various data related to the user include the user's basic information (e.g., the user's name, address, telephone number, email address and other contact information, age, gender, etc.), owned (purchased) / rented real estate property information (information about real estate properties owned / rented by the user), cart information (information about properties added to the cart), payment information (purchase price of real estate properties, rental usage amount, and information necessary for reservations / payments for buying, selling, renting, or renting real estate properties), rental information (the user's current or past rental information), and point information (information about points usable in this service). Various data related to the user are stored in the user data storage unit 121 linked (associated) with the user ID.

[0037] Figure 5 shows an example of real estate property data stored in the server device 100.

[0038] The real estate property data 2000 shown in Figure 5 stores various data related to real estate properties. In Figure 5, for the sake of explanation, an example of one real estate property (a real estate property identified by property ID "20001") is shown, but information on multiple real estate properties can be stored. Examples of various data related to real estate properties include basic information of the real estate property (property name, address, sales / rental price, rental price for a specified period, etc.), detailed information (information on size and structure such as floor number, floor area, layout, furniture for each room, information on various facilities inside and outside the property, and surrounding area information (tourist attractions around the property, restaurants, transportation access information (bus, taxi, train, airline, etc.))). Various data related to real estate properties include information such as property number, property name, property location (address), sales price, description of property features, floor number, and size. Various data related to the property are stored in the property data storage unit 122, linked to the property ID.

[0039] Figure 6 shows an example of relent data stored in the server device 100.

[0040] The Relent data 3000 shown in Figure 6 stores various data related to the Relent service. In Figure 6, for the sake of explanation, an example of one loan request (a loan request identified by loan request ID "30001") is shown, but it can store information on multiple loan requests. Examples of various data related to the Relent service include information on the property to be rented (property ID, owner information (user ID, etc.)), loan period information, usage conditions information (use restrictions, number of people restrictions, gender restrictions, etc.), usage information (whether it was used or not, user information), payment information, and vacancy plan information (use, period, fee, etc.). Various data related to the property are stored in the property data storage unit 122 linked to the property ID.

[0041] <Processing flow> Referring to Figures 7-16, the processing flow of the property management method executed by System 1 of this embodiment will be described.

[0042] Figures 7, 11, and 14 are examples of flowcharts relating to a property management method as one embodiment of the present invention. In this system 1, the user accesses the server device 100 using a web browser on the user terminal 200 or an application provided by the service provider. When using the service, if the user is using the service for the first time, they may enter the user's basic information as described above. If they already have a user account, they may log in after undergoing a predetermined authentication, such as entering an ID and password, to enable the use of the service. In this case, a predetermined user interface may be provided via a website, application, etc., after this authentication. Furthermore, the timing at which the server device 100 requests the user to log in is not particularly limited, and login may be requested during the process of using the service. For example, login may not be required until the stage of displaying a list of real estate properties for purchase, and login may be required when deciding which property to purchase.

[0043] First, when a user operates the user terminal 200 to access the server device 100, as part of step S101, the control unit 130 (sales processing unit 135) of the server device 100 refers to the status information of each real estate property stored in the property data storage unit 122 via the property data management unit 133, generates a list of real estate properties available for sale (property list), and outputs it. The property list may contain information about only one real estate property, or it may contain information about multiple real estate properties. The property list may contain some or all of the information about each real estate property stored in the property data storage unit 122. The control unit 130 (sales processing unit 135) of the server device 100 transmits the property list data to the user terminal 200 via the communication unit 110 (and via the network NW). The user terminal 200 receives the property list data via the communication unit 210 and displays (browses) it on the display operation unit 220 (step S102).

[0044] Figure 8 shows an example of a screen displayed on the display operation unit 220, which serves as a user interface provided via a web browser or application on the user terminal 200. The property list can be displayed as shown in Figure 8, for example, but is not limited to this. When generating the property list, it may be generated based on the user's desired conditions, or it may be generated based on conditions set in advance by the service provider. When receiving a request for the user's desired conditions and generating a property list based on those conditions, the control unit 130 of the server device 100 processes the input of the user's desired conditions (receives a request for desired conditions) before, after, or during step S101. Specifically, for example, the user operates the user terminal 200 to input or select the desired conditions for the real estate property they wish to purchase. These desired conditions may include, for example, the desired purchase price, the upper limit, lower limit, or range of the desired purchase price, the location of the property (e.g., prefecture, city, town, or region), size, floor plan, floor level, building structure, etc. Furthermore, the server device 100 may have a search function that searches for properties based on the user's desired conditions and extracts only those properties that match those conditions. In that case, for example, the control unit 130 of the server device 100 is configured to search for properties that match the user's desired conditions received from the user terminal 200 from the data stored in the property data storage unit 122.

[0045] The property list displayed in the example screen in Figure 8 includes the property number associated with each property ID (No. 001, No. 002 in Figure 8), the property name (ISE, NASU in Figure 8), the property's location (Mie (Ise-Shima), Tochigi (Nasu) in Figure 8), the selling price (in the example in Figure 8, the selling price is "¥10,000,000 (tax included)", "¥20,000,000 (tax included)"), a description of the property's features (in the example in Figure 8, "Excellent location with a panoramic view of the sea", "Close to a ranch"), the number of floors, and the size (in the example in Figure 8, "3-story building, 200m² of floor space"). 2 "Two-story building, 150m² of floor space" 2 It includes information such as ").

[0046] The user can operate the user terminal 200 to select a property they wish to purchase from the property list mentioned above. For example, if a user wishes to purchase property number "No. 001" in Figure 8, they select it by tapping the "Add to Cart" button P1. Here, "cart" refers to a virtual "shopping cart," and information indicating that the user has selected the "Add to Cart" button for a given property is stored as cart information in the user data storage unit 121 of the server device 100. As a result, the user can display the properties added to the cart by selecting the cart icon P2 (cart image) shown in Figure 8. Furthermore, if the user selects the "Add to Cart" button for multiple properties, they can complete the payment for all of those properties at once. It should be noted that once an property has been added to the cart, it can also be removed from the cart (the information is changed to indicate that the property is not in the cart) by updating the cart information in the user data storage unit 121, for example by tapping the "Remove from Cart" button P4 in Figure 9.

[0047] When a user selects the "Add to Cart" button P1, the control unit 240 of the user terminal 200, as part of the process in step S103, transmits information to the server device 100 via the communication unit 210 indicating that item "No. 001" has been selected as a purchase candidate (information indicating that the user has selected the "Add to Cart" button P1 for item "No. 001"). The server device 100 receives this information transmitted from the user terminal 200 via the communication unit 110. Then, the control unit 130 of the server device 100 updates the user data in the storage unit 120 based on this information (step S104). Specifically, the sales processing unit 135 of the server device 100 updates the cart information in the user data storage unit 121 of the storage unit 120 to store item "No. 001". Then, when the user operates the user terminal 200 and selects the cart icon P2, the user terminal 200 sends a request to the server device 100 to display all the items selected with the "Add to Cart" button P1 (step S105). Upon receiving this request, the server device 100 refers to the cart information in the user data storage unit 121 and generates a list of all the items selected with the "Add to Cart" button. The sales processing unit 135 of the server device 100 then sends information regarding this cart item list to the user terminal 200 (step S106).

[0048] Figure 9 shows an example of a screen displayed on the user terminal 200 when the user selects the cart icon P2. Based on the information about the cart item list received from the server device 100, the user terminal 200 displays all items added to the cart on the display operation unit 220 (step S107). In the example screen shown in Figure 9, only one item is displayed, but this is not limited to this, and multiple items may be displayed.

[0049] In the example screen shown in Figure 9, when the user operates the user terminal 200 and selects the "Purchase" button P5 in Figure 9, a purchase request (purchase procedure commencement request) is sent from the user terminal 200 to the server device 100 (step S108).

[0050] In the example above, we described a purchase request for an item via the "cart," but this is not the only way. It is also possible to directly request the purchase of a desired item (a request to start the purchase procedure) without going through the "cart." Specifically, for example, if a user wishes to purchase item "No. 001" in Figure 8, they would select the "Buy Now" button P3 instead of the "Add to Cart" button P1. This would cause the user terminal 200 to send a purchase request to the server device 100 (step S108), similar to selecting the "Buy Now" button P4 in Figure 9.

[0051] When the server device 100 receives the purchase request, it performs, for example, inventory check and inventory reservation processing for the property (step S109). Specifically, the sales processing unit 135 of the server device 100 refers to the status information of the property data storage unit 122 via the property data management unit 133 to confirm that the status of the property is "available for sale" (inventory check processing), and if the status of the property is "available for sale", it changes (updates) the status to "unavailable for sale" (inventory reservation processing). This prevents other users from starting the purchase procedure for the property. The inventory reservation processing may also be performed when the deposit payment process, described later, is completed. If the status of the property at the time of inventory check is "unavailable for sale", the server device 100 sends information to the user terminal 200 indicating this and cancels the purchase procedure.

[0052] Next, the server device 100 transmits information regarding the user information input screen to the user terminal 200, causing the user terminal 200 to display the user information input screen. The user operates the user terminal 200 to input user information such as the user's basic information (step S110). The user terminal 200 transmits the input user information to the server device 100, and the server device 100 registers the user information by storing it in the user data storage unit 121 of the storage unit 120 (step S111). Note that if the user information is already stored in the server device 100, such as when the user has already logged into this system 1, the user information input step S110 and the user information registration step S111 can be omitted.

[0053] Next, based on the user's operation of the user terminal 200, the user terminal 200 sends a deposit payment settlement request to the server device 100. The server device 100 processes the deposit payment settlement, paying a portion of the cost of the real estate property to be purchased as a deposit online to the property owner (in this example, the service provider) (step S112). For example, the server device 100 generates information regarding the screen for requesting the deposit payment, sends this information to the user terminal 200, and displays the deposit payment screen on the user terminal 200.

[0054] Figure 10 shows an example of the application fee payment screen displayed on the user terminal 200. The user operates the user terminal 200 to input or select various information related to their credit card (card number, expiration date, etc.). If the user has already registered information about their credit card, they can skip inputting or selecting that information. When the user operates the user terminal 200 and selects the "Pay with Credit Card" button P6 in Figure 10, the user terminal 200 sends information to the server device 100 indicating the execution of the payment process (step S112). The settlement process for application fee payment is not limited to credit card use, and any payment method that can be linked with this system can be used. For example, points usable within this service may be used, or debit card payments or prepaid card payments may be used, or electronic money may be used, or electronic payment services including code payments using barcodes, 2D codes, etc., or electronic accounts of financial institutions may be used, or a combination of these may be used. The control unit 130 of the server device 100 stores information related to the settlement process for application fee payments (payment method, payment amount, date, etc.) in the user data storage unit 121.

[0055] When the control unit 130 of the server device 100 confirms the payment (deposit) of the application fee (step S113), it performs a process to update the property data and user data in the storage unit 120 (step S114). For example, it stores in the storage unit 120 the information that the user has completed the payment of the application fee for the property as the status of the property data and user data. In this way, the application procedure for purchasing a real estate property using this system 1 is completed. Thus, with this system 1, the entire application procedure for purchasing a real estate property can be performed online (by exchanging information between the server device 100 and the user terminal 200 via the network NW).

[0056] After completing the above application procedure, for example, as shown in Figure 7, the user terminal 200 and the server device 100 can complete the real estate transaction procedure and transfer the property from the property owner (service provider) to the user by performing the following: processing of the electronic signature of the contract (step S115), processing of the request for payment of the purchase price (remaining balance) (step S116), processing of the payment settlement of the purchase price (remaining balance) (step S117), processing of payment confirmation (step S118), and processing of the issuance of an electronic key (step S119).

[0057] The electronic signature processing of the contract (step S115) can be performed by the user operating the user terminal 200 to input or select the necessary information for the electronic signature of the contract. Information regarding the electronic signature of the contract is transmitted from the user terminal 200 to the server device 100 and stored in the storage unit 120 of the server device 100. In this case, for example, after the payment confirmation step S113, the server device 100 may generate and output the electronic data of the contract in advance and transmit it to the user terminal 200.

[0058] The processing of the payment request for the remaining balance of the purchase cost (step S116) is transmitted from the server device 100 to the user terminal 200 after receiving information regarding the electronic signature of the contract. The user terminal 200 receives the information transmitted from the server device 100 and displays a screen indicating the payment request for the remaining balance of the purchase cost.

[0059] The payment of the remaining balance of the purchase cost (step S117) is performed when the user operates the user terminal 200 and instructs it to pay the remaining balance of the purchase cost, for example, in the same manner as the payment of the application fee described above. The server device 100 stores the information regarding the payment in the user data storage unit 121.

[0060] The server device 100 performs a payment confirmation process (step 118), and after confirming that the payment has been received, it refers to the storage unit 120 to issue electronic key information and transmits it to the user terminal 200. The user can then use the electronic key received by the user terminal 200, for example, to unlock the door of the property.

[0061] In the above embodiment, the user can also complete the payment simultaneously with the purchase request based on the selection of the "Buy Now" button, etc., by pre-registering the information necessary for payment processing (payment method and information necessary for payment (credit card information, etc.)) with the server device 100 in advance and giving prior consent. In other words, the purchase payment can be completed with a single click.

[0062] Furthermore, in the above embodiment, the system may be configured to allow cancellation even after the application procedure for purchasing real estate using this system 1 has been completed. In that case, for example, a "Cancel" button that the user can select may be displayed on the screen of the user terminal 200. When the user selects the "Cancel" button, a cancellation request is sent from the user terminal 200 to the server device 100. The sales processing unit 135 of the server device 100 executes the cancellation process for the purchase procedure.

[0063] Furthermore, in the above embodiment, the settlement of various expenses is not limited to being processed in a lump sum, but may also be processed in multiple installments.

[0064] The following describes the process by which a user (owner) who has purchased the above-mentioned property using System 1 of this embodiment stores (registers) the rental period for which the property can be rented out to others in the server device 100.

[0065] As shown in Figure 11, first, when a user operates the user terminal 200 to access the server device 100 and performs a login operation as appropriate, as part of step S201, the relent processing unit 136 of the control unit 130 of the server device 100 generates and outputs a loan period input screen while referring to the relent data management unit 134. The relent processing unit 136 of the server device 100 transmits the property list data to the user terminal 200 via the communication unit 110. The user terminal 200 receives the property list data via the communication unit 210 and displays (browses) it on the display operation unit 220 (step S202).

[0066] Figure 12 shows an example of a screen (rental period input screen) displayed on the display operation unit 220 of the user terminal 200. In the example screen of Figure 12, if the user owns multiple properties, they can select which property to rent out. They can also select the rental period (dates) for each property. In the example screen of Figure 12, the dates are displayed in a calendar format, and the user can operate the user terminal 200 to select the days on which the property can be rented out, in one-day increments. In the example of Figure 12, the user selects the days on which the property can be rented out and the rental period is displayed, but this is not limited to this configuration. The user (owner) may select the period on which the property cannot be rented out and the unavailable period is displayed. In that case, the server can determine that days other than the "unavailable days" selected by the user (owner) are "available days" and proceed with subsequent processing on the server side. Furthermore, the timing and other conditions for when the relent processing unit 136 generates or outputs the vacancy plan can be arbitrarily set on the server side or the user side. For example, the system may generate or output vacancy plans at a predetermined time before the dates when the rooms become available for rent. Specifically, for example, the Relent Processing Unit 136 may be configured to automatically generate vacancy plans to be sold as accommodations, etc., when it is three months prior to the dates when the rooms become available for rent. Furthermore, the selection of the available period (or unavailable period) can be 0 days, 1 day, or multiple days consecutively or intermittently. In the example screen in Figure 12, a total of 23 days are selected as the available period: 15 days from August 9th to August 23rd, and 3 days from August 29th to August 31st, with the dates of the available period enclosed in a frame. Note that the input screen for the available period (or unavailable period) does not necessarily have to be in calendar format; any display format can be used as long as the available period can be entered or selected. Also, the unit used when entering or selecting the available period is not limited to "days," but may be "hours," "minutes," "months," "years," etc.

[0067] When a user operates the user terminal 200 to select a rental period for which the property can be rented out, the user terminal 200 transmits information about the rental period to the server device 100 (step S203). The rerent processing unit 136 of the server device 100 refers to the property data storage unit 122 of the storage unit 120, etc., and calculates the amount of consideration (revenue) to be paid to the user in connection with renting out the property according to the rental period, and transmits the information of the revenue amount to the user terminal 200 (step S204). The user terminal 200 displays the revenue amount received from the server device 100 on the display operation unit 220. The user can consider the rental period while referring to the revenue amount displayed on the user terminal 200.

[0068] When a user operates the user terminal 200 and selects the "Lend" button P9 in the example screen shown in Figure 12, the user terminal 200 sends a loan request (loan period registration request) to the server device 100 (step S205). When the relent processing unit 136 of the server device 100 receives a loan request, it assigns a loan request ID to each loan request and stores information about the loan request in the relent data storage unit 123 (step S206). This allows the server device 100 to register information about the loan request for that item.

[0069] The relent processing unit 136 of the server device 100 processes the payment of the above-mentioned revenue amount according to the loan period to the user and transmits information regarding the payment processing to the user terminal 200 (step S207). When the user terminal 200 receives the payment information, it can display it on the display operation unit 220 of the user terminal 200, and the user can confirm that the payment has been made (step S208). The method of payment from the service provider (server device 100) to the user (user terminal 200) is not particularly limited, but for example, it may be done using an electronic account of a financial institution, or payment may be made using points usable within this service, or payment may be made using electronic money.

[0070] In this system 1, the user may select a method for receiving (depositing) the revenue amount according to the loan period. For example, when a user operates the user terminal 200 and selects the "Select Deposit Method" button P7 in the example screen shown in Figure 12, information indicating that the "Select Deposit Method" button P7 has been selected is sent from the user terminal 200 to the server device 100, and the server device 100 outputs a deposit method selection screen and sends it to the user terminal 200. The user terminal 200 displays the deposit method selection screen on the display operation unit 220. The user selects or enters their desired deposit method from the options displayed on the deposit method selection screen, such as "Receive in points," "Receive in electronic money," or "Receive in an electronic account at a financial institution." The user terminal 200 sends information about the desired deposit method to the server device 100. The server device 100 processes the deposit using the desired deposit method. The server device 100 can also store information about the deposit method in the storage unit 120.

[0071] Furthermore, in this system 1, the user may be allowed to specify the purpose (rental use) for which the property is leased to others. For example, when a user operates the user terminal 200 and selects the "Select Purpose" button P8 in the example screen shown in Figure 12, a rental purpose selection screen request is sent from the user terminal 200 to the server device 100. Based on this request, the server device 100 generates and outputs a rental purpose selection screen as shown in the example screen shown in Figure 13 and sends it to the user terminal 200. The user terminal 200 displays the rental purpose selection screen as shown in the example screen shown in Figure 13 on the display operation unit 220. The user can select a purpose from multiple options such as "accommodation use," "event use," "office work use," and "no usage restrictions" for each available rental period.

[0072] Thus, by providing a usage selection function, it becomes possible to prevent the property from being leased for uses undesirable to the user who owns the property. Furthermore, by selecting uses that generate higher revenue, it is possible to increase the revenue generated from renting.

[0073] Furthermore, in this system 1, the server device 100 (service provider) may determine the rental use. In this case, for example, the rental use may be determined by appropriately combining rental uses based on various conditions such as the property's location, the season and time of rental period, in order to reduce vacancy time or increase revenue.

[0074] The following describes the process of lending out a property with the above-mentioned rental period registered to another user (guest) using System 1 of this embodiment.

[0075] As shown in Figure 14, first, the relent processing unit 136 of the server device 100 refers to the relent data storage unit 123 via the relent data management unit 134 and generates and outputs a vacancy plan (vacancy list) based on the rental period for each property subject to relent and the rental purpose and other conditions (step S301).

[0076] To use this system 1, the guest accesses the server device 100 using a web browser on the user terminal 300 or an application provided by the service provider. When using the service, if the guest is using the service for the first time, they may enter the basic user information mentioned above. If they already have a user account, they may log in after undergoing a prescribed authentication, such as entering their ID and password, to enable them to use the service. In this case, a prescribed user interface may be provided via a website, application, etc., after this authentication. Furthermore, there are no particular limitations on when the server device 100 requests the guest to log in; they may be asked to log in during the process of using the service. For example, login may not be required until the stage of displaying available room plans, and login may be required when booking / paying for a room.

[0077] When a guest accesses the server device 100 by operating the user terminal 300, information including the vacancy plan output in step S301 is sent from the server device 100 to the user terminal 300. Upon receiving this information, the user terminal 300 displays (browses) the vacancy plan on the display operation unit 220 (step S302).

[0078] The guest operates the user terminal 300 to select an available room plan for their desired property. The guest also operates the user terminal 300 to input or select the period of use, purpose, number of users, gender, etc., as needed, and submits a reservation request (step S303).

[0079] Figure 15 shows an example of a screen (loan period input screen) displayed on the display operation unit 220 of the user terminal 200. In the example screen in Figure 15, dates are displayed in a calendar format, allowing the user to confirm the available dates within the loan period they have set. In the example screen in Figure 15, all dates within the loan period are available, surrounded by a frame, and the date text is displayed in bold. The user can operate the user terminal 300 to select the desired date for the property in one-day increments. If there are multiple properties available to the user, the user can select the property they wish to reserve. In the example screen in Figure 15, when the user selects a desired date, the desired date is displayed surrounded by a colored frame. In the example screen shown in Figure 15, when a user selects a desired date for a reservation and taps the "Make a Reservation" button P10, a request to display the reservation application screen is sent from the user terminal 200 to the server device 100. Based on this request, the server device 100 generates and outputs information for the reservation request screen, for example, as shown in Figure 16, and sends it to the user terminal 200. Upon receiving this information, the user terminal 200 displays a reservation application screen on the display operation unit 220, similar to the example screen shown in Figure 16. The user can then input or select information such as the "Name of the property to be used," "Period of use," "Purpose," and "Number of people" when using the property.

[0080] When the server device 100 receives information regarding a reservation request from the user terminal 200, it refers to the relent data storage unit via the relent data management unit 134 to check whether the reservation is possible (step S304). For example, it determines whether the reservation is possible by comparing the information included in the reservation request with the rental conditions of the property, or by referring to the reservation information to check if another reservation has already been made. If the relent processing unit 136 of the server device 100 determines that the reservation is possible, it confirms the reservation and updates the reservation information in the relent data storage unit 123. For example, by changing the status of the property for the period related to the reservation to "reserved" and stopping other people from making reservations for the property for that period, the property can be secured (step S305).

[0081] A user who has made the above reservation request will process the payment of the usage fee at the time of the reservation request or afterward, for example by operating the user terminal 300, and will send information regarding the payment process to the server device 100 (step S306). The service provider can confirm that payment has been received based on the information received by the server device 100 (step S307). The method of payment is not particularly limited, but for example, it may be done using an electronic account of a financial institution, or payment may be made using points usable within this service, or payment may be made using electronic money. The server device 100 may also send the above vacancy plan information to other reservation sites, etc., to solicit use of the property.

[0082] As described above, in System 1 of this embodiment, a server device 100, which serves as a management server for managing information on real estate properties, and a user terminal 200 are connected via a network NW. The server device 100 includes a sales processing unit 135 that processes information related to the user's purchase procedure for real estate properties based on a purchase request from the user terminal 200, and a relent processing unit 136 that processes information related to the user's rental of the real estate property to others based on a rental request from the user terminal 200.

[0083] Thus, according to System 1 of this embodiment, even when a user is away on a business trip or otherwise unavailable and does not use the property they own, the property can be effectively utilized by making it available for rent to others.

[0084] Furthermore, in System 1 of this embodiment, the purchase of real estate properties and the temporary rental of purchased real estate properties can be performed using a common system. For example, compared to cases where information management for the purchase and rental of real estate properties is performed using separate systems, the operational and procedural burden on the user is significantly reduced. In addition, a user who purchases real estate properties can earn revenue by renting them out to others during the period they are absent. The service operator can also earn revenue not only from the sale of real estate properties to users, but also from the rental of those properties to others. It should be noted that the above revenue amount is basically smaller than the usage fee (rental fee) that the service operator receives when renting out to others, and the difference becomes the service operator's profit.

[0085] Furthermore, in System 1 of this embodiment, the entire process, from purchasing a real estate property to leasing the purchased property, can be carried out online. Therefore, there is no need to meet in person with service operators or guests (other users) during the various procedures associated with purchasing a real estate property and the various procedures associated with leasing the property, which significantly reduces the effort involved in the procedures.

[0086] Furthermore, in System 1 of this embodiment, a loan request includes information regarding the loan period during which the property can be rented out to others. With this configuration, a user who owns a property can prevent it from being rented out on days when they do not wish to rent it out to others.

[0087] Furthermore, in System 1 of this embodiment, the rerent processing unit 136 calculates the amount of consideration to be paid to the user in connection with the rental of the real estate property based on the rental period. With this configuration, it becomes easier for the user to understand the amount of consideration and to determine the rental period.

[0088] Furthermore, in System 1 of this embodiment, the lending processing unit 136 performs settlement processing to pay the user the amount of consideration when it receives a lending request, regardless of whether the real estate property is used for lending during the lending period. With this configuration, the user can easily adjust the amount of consideration and the timing of receiving the consideration.

[0089] Furthermore, in System 1 of this embodiment, a loan request includes information regarding the intended use of the real estate property. This configuration allows users to rent out real estate properties only for their desired purposes, thereby increasing user convenience.

[0090] Furthermore, in System 1 of this embodiment, the rerent processing unit generates a vacancy plan that includes multiple rental uses for the real estate property based on the rental request. With this configuration, it is possible to recruit a wider range of users compared to when there is only one rental use, enabling more effective utilization of the real estate property.

[0091] In addition, in System 1 of this embodiment, when selling a real estate property to a user, a time limit may be set regarding the ownership of the real estate property. In other words, in System 1 of this embodiment, the user may be sold the right to own the real estate property for a predetermined period of time. Furthermore, along with the real estate property, software for a property management system, including an application for using the above-mentioned Rent Service, may be sold to the user, and a time limit may also be set for the use of the application and software.

[0092] As described above, this embodiment provides a novel property management system and property management method that enable the effective utilization of real estate properties.

[0093] Although embodiments of the disclosed invention have been described above, these can be implemented in various other forms and can be implemented with various omissions, substitutions, and modifications. These embodiments and modifications, as well as those with omissions, substitutions, and modifications, are included within the technical scope of the claims and their equivalents. Furthermore, the processes shown in Figures 7, 11, and 14 are examples of processes performed by the system of this embodiment and are not intended to limit the present invention. Each step (process) included in the processes in Figures 7, 11, and 14 may be performed in an order different from that shown in the figures, some processes may be performed in parallel, some processes may be omitted, or other processes may be added.

[0094] Furthermore, the following configurations also fall within the technical scope of this disclosure. [Item 1] A management server that manages real estate property information and user terminals are connected via a network. The aforementioned management server A sales processing unit that processes information related to the user's purchase procedure for the real estate property based on a purchase request from the user terminal, A property management system characterized by comprising: a rerent processing unit that performs processing of information regarding the lending of the real estate property purchased by the user to another party, based on a lending request from the user terminal. [Item 2] The property management system described in item 1 includes information regarding the loan period that enables the real estate property to be leased to another party. [Item 3] The property management system described in item 2, wherein the rent processing unit calculates the amount of consideration to be paid to the user in connection with the rental of the real estate property based on the rental period. [Item 4] The property management system described in item 3, wherein the rent processing unit performs a settlement process to pay the amount of consideration to the user when it receives a rental request, regardless of whether the property is rented out or not during the rental period. [Item 5] The aforementioned loan request includes information regarding the intended use of the real estate property, as described in any one of items 1 to 4 of the property management system. [Item 6] The property management system according to any one of claims 1 to 5, wherein the rent processing unit generates a vacancy plan including multiple rental uses for the real estate property based on the rental request. [Item 7] A management server that manages real estate property information and user terminals are connected via a network. The aforementioned management server A sales processing step that processes information related to the user's purchase procedure for the real estate property based on a purchase request from the user terminal, A property management method characterized by including a rerent processing step that performs processing of information regarding the lending of the real estate property purchased by the user to another party, based on a lending request from the user terminal. [Explanation of Symbols]

[0095] 1: Property Management System 100: Server device (management server) 110: Communications Department 120: Storage section 130: Control Unit 200: User terminal NW: Network

Claims

1. A management server that manages real estate property information and user terminals are connected via a network. The aforementioned management server A sales processing unit that processes information related to the user's purchase procedure for the real estate property based on a purchase request from the user terminal, A property management system characterized by comprising: a rerent processing unit that performs processing of information regarding the lending of the real estate property purchased by the user to another party, based on a lending request from the user terminal.

2. The property management system according to claim 1, wherein the loan request includes information regarding the loan period that enables the real estate property to be leased to another party.

3. The property management system according to claim 2, wherein the rent processing unit calculates the amount of consideration to be paid to the user in connection with the rental of the real estate property based on the rental period.

4. The property management system according to claim 3, wherein the rerent processing unit performs a settlement process to pay the amount of consideration to the user when it receives a rental request, regardless of whether the property is rented out or not during the rental period.

5. The property management system according to any one of claims 1 to 4, wherein the loan request includes information regarding the intended use of the real estate property.

6. The property management system according to any one of claims 1 to 5, wherein the rerent processing unit generates a vacancy plan including multiple rental uses for the real estate property based on the rental request.

7. A management server that manages real estate property information and user terminals are connected via a network. The aforementioned management server A sales processing step that processes information related to the user's purchase procedure for the real estate property based on a purchase request from the user terminal, A property management method characterized by including a rerent processing step that performs processing of information regarding the lending of the real estate property purchased by the user to another party, based on a lending request from the user terminal.