JP7114504B2 - Systems, methods and programs for supporting joint use of subject matter - Google Patents

Description

Application of Patent Act Article 30, Paragraph 2 June 27, 2017 <Android version> https://play. google. com/store/apps/details? id=jp. dena. ride, <iOS version> https://itunes. apple. com/jp/app/anyca/id982410763

The present invention relates to systems, methods, and programs for supporting shared use of objects (vehicles, dwellings, etc.).

2. Description of the Related Art In recent years, services have been provided for joint use (sharing) of a vehicle or a residence among users. For example, Patent Literature 1 below discloses a system for supporting guest use of an accommodation facility provided by a host (accommodation facility sharing). In such a system, typically, the user (owner of the object) who provided the object for joint use (accommodation facility, etc.) and the user who used the object (user who uses the object) ) have introduced a mutual review mechanism in which they mutually review each other. The accumulated reviews are utilized when each user selects a trading partner. It becomes possible to determine whether or not to approve the transaction.

Japanese Patent Publication No. 2016-512645

However, with the conventional mutual review mechanism described above, for example, although it is possible for the owner of an object such as an accommodation facility to avoid becoming a trading partner with a user who has a significantly low evaluation in the review, However, it was not possible to actively encourage the use of the object by the user who is preferable to the person himself/herself. For example, the owner may want some of the users who have a track record of using the object owned by him/herself to become repeaters of the transaction.

One of the objects of the embodiments of the present invention is to encourage reuse of the object by a user who is preferable to the owner of the object for joint use. Other objects of embodiments of the present invention will become apparent upon review of the specification as a whole.

A system according to one embodiment of the present invention is a system for supporting collaborative use of an object comprising one or more computer processors, the one or more computer processors for executing readable instructions. According to the above, a process to manage transactions between each of the multiple owners and each of the multiple users for the user to use the object owned by the owner, and to the user and the process of giving the privilege to the object identified by the specific owner, among a plurality of users who have used the object owned by the specific owner. This includes granting a user specific privileges applicable for use of an object owned by said specific owner.

A method according to one embodiment of the present invention is a method, performed by one or more computers, for facilitating joint use of an object, wherein each of a plurality of owners and each of a plurality of users managing a transaction for the user's use of an object owned by the owner; and granting a benefit to the user, wherein the granting of the privilege comprises: For use of an object owned by a specific owner for a target user identified by the specific owner among multiple users who used the object owned by the specific owner including granting certain benefits applicable to

A program according to one embodiment of the present invention is a program for supporting joint use of an object, wherein, in response to execution on one or more computers, said one or more computers are provided with a plurality of proprietary A process of managing transactions between each person and each of a plurality of users for the user to use the object owned by the owner, and a process of granting benefits to the user , and granting the privilege to the target user identified by the specific owner, among a plurality of users who have used the target object owned by the specific owner, Including granting specific privileges applicable for use of objects owned by specific owners.

Various embodiments of the present invention encourage reuse of the shared object by the preferred user for the owner of the object.

1 is a configuration diagram schematically showing the configuration of a network including a joint use support system 10 according to one embodiment of the present invention; FIG. FIG. 2 is a block diagram schematically showing the functions of the joint use support system 10; 4 is a diagram exemplifying information managed by an object management table 411; FIG. 4 is a diagram exemplifying information managed by a user management table 412; FIG. 4 is a diagram exemplifying information managed by a transaction management table 413; FIG. FIG. 2 is a flowchart illustrating processing executed by the shared use support system 10; FIG. 5 is a diagram exemplifying a search screen 50; FIG. 6 is a diagram exemplifying a vehicle detail screen 60; FIG. FIG. 7 is a diagram illustrating an example of a schedule list screen 70; FIG. The figure which illustrates the schedule details screen 80. FIG. The figure which illustrates the schedule details screen 80. FIG. The figure which illustrates the review input screen 120. FIG. FIG. 10 is a view exemplifying a user selection screen 90; FIG. The figure which illustrates the coupon creation screen 100. FIG. The figure which illustrates the schedule details screen 80 in which message MSG1 which notifies issue of a coupon is displayed. The figure which illustrates the coupon browsing screen 110. FIG. The figure which illustrates the vehicle details screen 60 when the coupon is issued. The figure which illustrates 120 A of review input screens.

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

FIG. 1 is a configuration diagram schematically showing the configuration of a network including a joint use support system 10 according to one embodiment of the present invention. As illustrated, the system 10 is communicably connected to a user terminal 30 via a network 20 such as the Internet. Although only one user terminal 30 is illustrated in FIG. 1 , the system 10 is communicatively connected to a plurality of user terminals 30 . The system 10 provides the user via the user terminal 30 with an inter-individual sharing service that supports joint use of objects such as vehicles and residences owned by the user with other users.

The system 10 is configured as a general computer, and as shown in FIG. 1, a CPU (computer processor) 11, a main memory 12, a user I/F 13, a communication I/F 14, a storage ) 15, and these constituent elements are electrically connected via a bus or the like (not shown).

The CPU 11 loads various programs stored in the storage 15 or the like into the main memory 12 and executes various instructions included in the programs. The main memory 12 is composed of, for example, a DRAM.

The user I/F 13 includes various input/output devices for exchanging information with the user. The user I/F 13 includes, for example, information input devices such as keyboards and pointing devices (for example, mice and touch panels), voice input devices such as microphones, and image input devices such as cameras. The user I/F 13 also includes an image output device such as a display and an audio output device such as a speaker.

The communication I/F 14 is implemented as hardware such as a network adapter, various types of communication software, or a combination thereof, and is configured to enable wired or wireless communication via the network 20 or the like.

The storage 15 is composed of, for example, a magnetic disk, flash memory, or the like. The storage 15 stores various programs including an operating system, various data, and the like.

In this embodiment, the system 10 can be configured using multiple computers each having the hardware configuration described above. For example, system 10 may be configured with multiple server devices.

The joint use support system 10 configured in this manner has functions as a web server and an application server, and is installed in the user terminal 30 with a web browser or other applications (for example, the inter-individual sharing system of this embodiment). It executes various processes in response to requests from service applications), and transmits screen data (for example, HTML data) and control data according to the results of the processes to the user terminal 30 . The user terminal 30 displays a web page or other screen based on the received data.

The user terminal 30 is configured as a general computer, and as shown in FIG. 35, and these constituent elements are electrically connected via a bus or the like (not shown).

The CPU 31 loads various programs stored in the storage 35 or the like into the main memory 32 and executes various instructions included in the programs. The main memory 32 is composed of, for example, a DRAM.

The user I/F 33 is various input/output devices for exchanging information with the user. The user I/F 33 includes, for example, information input devices such as keyboards and pointing devices (for example, mouse, touch panel, etc.), voice input devices such as microphones, and image input devices such as cameras. The user I/F 33 also includes an image output device such as a display and an audio output device such as a speaker.

The communication I/F 34 is implemented as hardware such as a network adapter, various types of communication software, or a combination thereof, and is configured to enable wired or wireless communication via the network 20 or the like.

The storage 35 is configured by, for example, a magnetic disk or flash memory. The storage 35 stores various programs including an operating system, various data, and the like. A program stored in the storage 35 can be downloaded from an application market or the like and installed.

In this embodiment, the user terminal 30 may be configured as a smart phone, tablet terminal, wearable device, personal computer, game terminal, or the like.

A user of the user terminal 30 configured in this way communicates with the system 10 via a web browser installed in the storage 35 or the like or an application for the person-to-person sharing service of the present embodiment. A person-to-person sharing service provided by the system 10 can be used. An application for personal sharing service executed on the user terminal 30 can be an example of a program implementing part or all of the program of the present invention.

Next, functions of the shared use support system 10 will be described. FIG. 2 is a block diagram schematically showing the functions of system 10. As shown in FIG. As shown in the figure, the system 10 includes an information storage management unit 41 that stores and manages various information, a basic function control unit 43 that controls the basic functions of sharing services between individuals, and management of transactions between users. and a privilege granting unit 47 that grants a privilege to the user. These functions are realized by the cooperative operation of hardware such as the CPU 11 and the main memory 12, and various programs and data stored in the storage 15 and the like. It is implemented by the CPU 11 executing instructions included in the program. Also, part or all of the functions shown in FIG.

The information storage management unit 41 of the system 10 stores and manages various information in the storage 15 or the like. For example, as shown in FIG. 2, the information storage management unit 41 includes an object management table 411 that manages information on shared objects, a user management table 412 that manages information on users, and a user management table 412. and a transaction management table 413 for managing information on transactions.

The basic function control unit 43 of the system 10 executes various processes related to control of the basic functions of the person-to-person sharing service. For example, the basic function control unit 43 transmits HTML data or control data of various screens related to the basic functions to the user terminal 30, and responds to the operation input by the user via the screen displayed on the user terminal 30 to perform various operations. processing, and transmits HTML data or control data according to the result of the processing to the user terminal 30 . Basic functions controlled by the basic function control unit 43 include, for example, login processing (user authentication), payment processing, object management (for example, updating the object management table 411), and user management (for example, , update of the user management table 412, etc.).

The transaction management unit 45 of the system 10 executes various processes related to management of transactions between users. The transaction is an interpersonal transaction between each of a plurality of owners and each of a plurality of users, and is a transaction for a user to use an object owned by the owner. For example, when the transaction management unit 45 receives a reservation request for use of an object owned by a specific owner from a specific user, the transaction management unit 45 transmits the reservation request to the specific owner, and then Upon approval of the reservation request by the owner, a reservation for use of the object is established between the specific user and the specific owner.

The privilege granting unit 47 of the system 10 executes various processes related to granting a privilege to the user. In the present embodiment, the privilege granting unit 47 provides the target user specified by the specific owner, among a plurality of users who have used the target object owned by the specific owner, with the target user specified by the specific owner. It is configured to grant a specific privilege applicable for use of an object owned by the owner. In other words, the person-to-person sharing service in this embodiment allows the owner of an object to specify applicable information for future use of the object from past users of the object of the owner. It is configured to be able to specify (select) the user to whom the privilege of is granted.

In this way, the joint use support system 10 of the present embodiment is applied to the use of an object owned by the owner from among the users who have used the object owned by the owner himself/herself. It is configured to identify (select) users to whom certain possible benefits are granted. Therefore, reuse of the object by a user who is preferable to the owner of the object for joint use is encouraged.

In this embodiment, the privilege given to the user may include various kinds of privileges. For example, benefits include discounts on usage fees for objects. The discount is set at a predetermined discount rate or amount, and given to the user as an electronic/virtual coupon, for example. Benefits include discounts on fees for optional items, relaxation of usage conditions (for example, relaxation of gasoline replenishment conditions in car sharing, etc.), and the like.

Further, the transaction management unit 45 can be configured to receive a first evaluation of the user by the owner. A predetermined screen for granting a specific privilege to the specific user is presented to the specific owner (for example, the user displayed on the terminal 30). Such a configuration enables the owner to grant benefits to a specific user in accordance with the input of a rating (e.g., evaluation in peer review) for the specific user, and as a result, the specific privilege Smooth grant of is promoted.

In this embodiment, the predetermined screen for awarding the privilege can be configured such that presentation/non-presentation is controlled according to the value (result) of the first evaluation. That is, if the first evaluation by the specific owner for the specific user is within the first range (for example, the value is equal to or greater than a predetermined threshold value), the privilege granting unit 47 displays the predetermined screen as the specific user. while presenting a predetermined screen to the owner of the specific user if the first evaluation by the specific owner for the specific user is outside the first range (e.g., the value is less than a predetermined threshold) may be configured not to present to the owner of the Such a configuration encourages the granting of benefits to users whose evaluations are within a predetermined range, while suppressing the granting of benefits to users whose evaluations are outside the predetermined range.

In this embodiment, the specific benefit may be automatically given to the user according to the value (result) of the first evaluation. That is, the privilege granting unit 47 selects a user whose first evaluation by the specific owner is within the first range among a plurality of users who have used the target object of the specific owner. can be configured to automatically grant certain benefits as Such a configuration promotes the granting of benefits to users whose evaluation by the owner is within a predetermined range, and reduces the burden on the owner accompanying the granting of the benefits.

In the present embodiment, the first evaluation can be configured to be disclosed to the user, and the transaction management unit 45 is the evaluation of the user by the owner, which is not disclosed to the user. It may be configured to accept a rating of 2. In this case, the privilege granting unit 47 selects the user whose first evaluation by the specific owner is within the first range and whose second evaluation by the specific owner is within the second range. It can be configured to automatically grant certain benefits as an intended user. In this configuration, in addition to the result of the evaluation (first evaluation) that is open to users, the necessity of automatic granting of benefits is determined based on the results of evaluation that is not disclosed to users (second evaluation). make it possible to judge

Further, the transaction management unit 45 can be configured to receive a third evaluation of the owner by the user. It may be configured to grant a particular benefit to a target user identified by that particular owner among those within range. Such a configuration promotes granting of privileges to users whose evaluation (e.g., evaluation in mutual review) for the owner is within a predetermined range (e.g., the value is equal to or greater than a predetermined threshold).

In addition, the privilege granting unit 47 can be configured to transmit a predetermined message to the target user in accordance with the granting of a specific privilege. In response to a request by a person via a predetermined message, a screen for making an application (reservation application) for the use of an object owned by a specific owner is presented to the target user. . Such a configuration encourages use of the object by the user to whom the privilege has been granted.

Next, a specific example of the joint use support system 10 of this embodiment having such functions will be described. The service provided by system 10 in this example is a peer-to-peer car-sharing service that facilitates the joint use of a user's own vehicle with other users. A user of the service can use a car owned by another user as a driver, and can provide another user with a car owned by the user as an owner.

FIG. 3 illustrates information managed by the object management table 411 in this specific example. The object management table 411 manages information about automobiles owned by owners. ID', 'vehicle basic information', 'usage condition information', 'delivery place information', etc. are managed. The basic vehicle information includes an image (photograph) of the vehicle, a description, and information on accessories. The usage condition information includes whether or not smoking is permitted, whether or not pets are allowed in the vehicle, whether or not gasoline needs to be replenished, cancellation policy, and the like. The delivery location information includes an address corresponding to the vehicle delivery location, the name of the nearest station, and the like. These pieces of information are registered in advance by the owner.

FIG. 4 illustrates information managed by the user management table 412 in this specific example. The user management table 412 manages information about users of the car sharing service between individuals. )”, “evaluation information (driver)”, and “holding coupon information”. User basic information includes a user image, a nickname, payment information (credit card information, etc.), and the like. The evaluation information (owner) is information about the user's evaluation as the owner, and includes the average value of the evaluations (numerical values in the range of 1 to 5) received from the driver in the mutual review between users described later, and the review The number of cases, etc. are included. Similarly, the evaluation information (driver) is information about the user's evaluation as a driver, and includes the average value of the evaluations received from the owner so far in mutual reviews between users described later, the number of reviews, and the like. The owned coupon information is information about coupons owned by the user. Although details will be described later, the coupon includes an owner-issued coupon issued by the owner.

FIG. 5 illustrates information managed by the transaction management table 413 in this specific example. The transaction management table 413 manages information related to transactions between the owner and the driver, and as shown in the figure, associates a "transaction ID" that identifies individual transactions with a "driver user ID" that identifies the driver. ", "Vehicle ID", "Transaction Status", "Date and Time of Use", "Charge Information", "Owner Review Information", "Driver Review Information", and "Owner Satisfaction Information" that identify vehicles subject to joint use. , "Driver Satisfaction Information", etc. The transaction status is set to any value corresponding to the three states of "reservation being requested", "reservation confirmed", and "transaction completed".

FIG. 6 is a flow diagram illustrating processing executed by the shared use support system 10 in this example. As shown, the system 10 first receives a vehicle reservation request from a driver (step S100). A reservation request by the driver is made via a screen displayed on the user terminal 30 .

FIG. 7 illustrates a search screen 50 displayed on the user terminal 30. As shown in FIG. The screen 50 is a screen for the driver to search for a car to use. As illustrated, the search screen 50 has a location information input area 52, a search button 54, and an information display area 56 for displaying a list of cars as search results.

In the information display area 56, a plurality of individual display areas 561 that respectively display information about individual automobiles are arranged side by side in the vertical direction. Area 561 switches.

In this example, in the initial state immediately after the search screen 50 is displayed, the address corresponding to the current location of the user terminal 30 is entered in the location information input area 52, and the current location is displayed in the information display area 56. (For example, the closer the set delivery place is to the current position, the more preferentially it is displayed). When the driver changes the information entered in the location information input area 52 and selects the search button 54, a search is performed again using the changed information (address, station name, etc.), and the information display area 56 Cars listed in are also updated.

An individual display area 561 of the information display area 56 displays information about an individual vehicle, specifically, a photograph of the vehicle, a usage fee, a delivery location (nearest station), a user image of the owner, and the like. These pieces of information are managed in the object management table 411 or user management table 412 .

When the driver selects (for example, taps) the individual display area 561 corresponding to the desired vehicle from among the vehicles listed in the information display area 56, the vehicle details screen 60 shown in FIG. 8 is displayed. be done. The screen 60 displays detailed information about the vehicle corresponding to the selected individual display area 561, and as shown, has a vehicle information display area 61, an owner information display area 63, and a usage condition display area 65. . A reservation request button 67 is arranged at the lower right corner of the vehicle details screen 60 . On the entire screen of the vehicle details screen 60, the display contents are switched by a vertical flick operation or the like, but the position of the reservation request button 67 is fixed.

The vehicle information display area 61 displays information about an individual vehicle, specifically information such as a photograph of the vehicle, usage fee, delivery location (nearest station), and the like. The owner information display area 63 displays information about the owner of the vehicle, specifically information such as a nickname, user image, and evaluation information. The evaluation information is displayed based on the owner's evaluation information (owner) managed in the user management table 412. Specifically, the average value of the evaluations so far set in the evaluation information (owner) is 5. It is displayed using two star-shaped objects, and the number of reviews so far is displayed. The use condition display area 65 displays information about the use conditions of the automobile (permission of smoking, permission of riding with a pet, etc.).

A reservation request button 67 on the vehicle detail screen 60 is an object for the driver to make a reservation request for a car. When the driver selects the reservation request button 67, a reservation request is made with input of the date and time of use of the car. When a reservation request is made, the system 10 creates a new record in the transaction management table 413 and sets the transaction status to "reservation requested".

Returning to the flow chart of FIG. 6, once the reservation request by the driver is accepted, the system 10 next accepts approval of the request by the owner (step S110). Approval of the request by the owner is performed via a screen displayed on the user terminal 30 .

FIG. 9 exemplifies a schedule list screen 70 displayed on the user terminal 30 . On the screen 70, one or a plurality of individual display areas 72 that respectively display information about individual schedules are arranged side by side in the vertical direction. When a driver makes a reservation request, the schedule displayed on the schedule list screen 70 is created for both the driver and the owner of the car that made the reservation request. In this way, the schedule can also be said to be a unit for managing the transaction that is created according to the start of the transaction.

The individual display area 72 of the schedule list screen 70 displays information (user image, etc.) related to the trading partner in the corresponding schedule, transaction status, and the like. Immediately after the reservation request is made, the transaction status is "reservation being requested".

When one of the individual display areas 72 listed on the schedule list screen 70 is selected, a schedule details screen 80 shown in FIG. 10 displaying information about the corresponding schedule is displayed. The screen 80 has a selection area 82 and an information display area 83 . The selection area 82 is an area for selecting the content to be displayed in the information display area 83, specifically, an area for switching the display content between "chat" and "details". The schedule details screen 80 in FIG. 10 corresponds to a state in which the chat contents are displayed in the information display area 83 . In this case, in the information display area 83, text chat messages MSG between the driver and the owner in the corresponding schedule (transaction) are arranged in the vertical direction in chronological order. It has an input area 85 and a send button 86 . When the user selects the send button 86, the message entered in the message input area 85 is sent as a text chat message.

FIG. 11 shows the schedule details screen 80 in which the details of the schedule are displayed in the information display area 83 . The details of the schedule displayed in the information display area 83 specifically include information on the trading partner, information on the vehicle, date and time of use, and the like. Further, the information on the trading partner specifically includes a nickname, user image, and evaluation information. The evaluation information is displayed based on the evaluation information of the owner (owner) or the evaluation information of the driver (driver) managed in the user management table 412. Specifically, the evaluation information (owner) or the evaluation information (driver) is displayed. is displayed using five star-shaped objects, and the number of reviews so far is also displayed.

Also, when the user himself/herself is scheduled to be the owner, a request approval button 84 is arranged in the lower right corner of the information display area 83 . On the entire screen of the schedule details screen 80, the display contents are switched by a vertical flick operation or the like, but the position of the request approval button 84 is fixed.

A request approval button 84 on the schedule details screen 80 is an object for the owner to approve the reservation request made by the driver. The reservation request is approved when the owner selects the request approval button 84 . Once the reservation request is approved, system 10 updates the transaction status in the corresponding record of transaction management table 413 to "reservation confirmed."

Returning to the flow chart of FIG. 6, after receiving approval of the request by the owner, the system 10 next receives mutual reviews from both the driver and the owner after the reserved date and time of use has passed (step S115) (step S120). During the period up to the date and time of use, the owner and the driver can communicate via text chat (for example, adjustment of the delivery method of the car, etc.).

FIG. 12 illustrates a review entry screen 120 for entering a review of a trading partner. As illustrated, the screen 120 displays information (user image, etc.) about the user to be reviewed, and also has an evaluation input area 122 for inputting an evaluation and a comment input area 124 for inputting a comment. , and a confirmation button 126 . In the evaluation input area 122, five star-shaped objects are arranged in the horizontal direction, and by selecting one of the objects, the corresponding five-level evaluation can be input. When the confirm button 126 is selected, the evaluation value and comments are registered as review results. Specifically, the review result of the driver by the owner is registered in the owner review information of the transaction management table 413 , and the review result of the driver by the owner is registered in the driver review information of the transaction management table 413 . These owner review information and driver review information are also open to general users through screens that display information about users.

Subsequently, the system 10 receives satisfaction with the transaction from both the driver and the owner (step S130). Transaction satisfaction is entered in the form of responses to questionnaires. The transaction satisfaction level input by the owner is registered in the owner satisfaction level information of the transaction management table 413 , and the transaction satisfaction level input by the driver is registered in the driver satisfaction level information of the transaction management table 413 . These satisfaction level information are not disclosed to general users, but are managed and utilized by operators and the like.

Here, the operation related to issuing a coupon by the owner will be described. FIG. 13 exemplifies a user selection screen 90 for the owner to select a user to issue a coupon. The screen 90 has one or a plurality of individual display areas 92 arranged vertically to display information about individual users. The user selection screen 90 displays a list of users (drivers) who have used the owner's automobile in a predetermined order (for example, in order of newest date and time of use). Also, in this example, when the owner issues a coupon to the driver, a new coupon cannot be issued until the issued coupon is used or the coupon expires (that is, One owner is limited to one valid coupon that can be issued to one user). On the user selection screen 90, an object 921 displaying "Issued" is superimposed on the user image for a user who has been issued a valid coupon but has not used the coupon.

When the individual display area 92 of the user selection screen 90 is selected, a coupon creation screen (predetermined screen) 100 shown in FIG. 14 for creating a coupon to be issued to the corresponding user (driver) is displayed. As shown, the screen 100 displays information about the driver issuing the coupon (user image, etc.), a discount rate input area 101 for inputting the discount rate, and an expiration date for inputting the expiration date. It has an input area 102 , a message input area 103 for inputting a message, and a coupon issue button 105 .

When the user (owner) selects the issue coupon button 105, the coupon is issued to the corresponding driver. A discount rate input via the discount rate input area 101 and an expiration date input via the expiration date input area 102 are set for the coupon to be issued. The owned coupon information in the user management table 411 is updated according to the issuance of the coupon. Specifically, the vehicle ID of the vehicle owned by the owner who issued the coupon, the discount rate, and the expiration date are set as the owned coupon information of the driver to whom the coupon was issued.

Issuance of the coupon to the driver is notified to the driver via a chat message on the schedule details screen 80 described above. FIG. 15 exemplifies a schedule detail screen 80 displaying a message MSG1 for notifying issuance of a coupon. A chat message notifying the issuance of the coupon is displayed on the schedule detail screen 80 corresponding to the past schedule with the owner who issued the coupon.

The message MSG1 for notifying the issuance of the coupon displays the contents of the coupon (the issuer's owner, the discount rate, and the expiration date), as shown in FIG. Note that the user image indicating the sender of the message MSG1 is the image of the operating account. Further, an object OBJ1 displaying "confirm coupon content" is arranged below the message MSG1.

When the user (driver) selects object OBJ1, a coupon browsing screen 110 illustrated in FIG. 16 is displayed. As shown, the screen 110 includes a coupon display area 112 for displaying the contents of the coupon, a message display area 114 for displaying a message from the owner who issued the coupon, and a confirmation button displaying "Confirm car". 116. The coupon display area 112 displays a discount rate, information on the owner of the issuing source (user image, etc.), information on automobiles, an expiration date, and the like. The message displayed in the message display area 114 is the message input by the owner via the message input area 103 of the coupon creation screen 100 .

When the user (driver) selects the confirmation button 116, the vehicle details screen 60 described above is displayed. FIG. 17 exemplifies the vehicle detail screen 60 when a coupon for the corresponding vehicle has been issued (the driver owns the coupon). In this case, as shown in the figure, a coupon notification object 611 is arranged at the upper end of the vehicle information display area 61 to notify information (discount rate, etc.) regarding the issued coupon. When the user selects the reservation request button 67, a reservation request is made using the issued coupon, and the discount set for the coupon is applied to the usage fee.

In the above example, a coupon is issued to a driver selected by the owner from among multiple drivers who have used the owner's car in the past. The timing is not limited to this. For example, the drivers for whom coupons are issued are limited to drivers who have used the owner's car in the past and whose evaluation value for the owner is equal to or higher than a predetermined threshold (e.g., 4 or higher). You can do it.

Further, for example, in another specific example of the present embodiment, it is configured such that a coupon can be issued in accordance with the input of a review to the driver. FIG. 18 illustrates a review input screen 120A in this other specific example. 120A of the said screen has the coupon issue button 123 in addition to the evaluation input area 122, the comment input area 124, and the determination button 126 so that it may illustrate. When the owner selects the issue coupon button 123, the coupon creation screen 100 illustrated in FIG. 14 is displayed. Here, the coupon issue button 123 may be enabled when the evaluation value input through the evaluation input area 122 is equal to or greater than a predetermined value, and disabled when the evaluation value is less than the predetermined value. good.

In yet another specific example of the present embodiment, coupons are automatically issued based on evaluation values in reviews. For example, when the confirmation button 126 of the review input screen 120 illustrated in FIG. 12 is selected, immediately or It can be configured such that a coupon with predetermined contents (discount rate and expiration date) is automatically issued through predetermined confirmation by the owner. In this case, the coupon is automatically issued based on the owner's transaction satisfaction value (for example, when the owner's transaction satisfaction value is greater than or equal to a predetermined value) in addition to the evaluation value in the review. You can do so. Here, since the owner's satisfaction with the transaction can be said to be a private evaluation of the driver, adding such transaction satisfaction to the conditions for automatic coupon issuance promotes the issuance of coupons to more appropriate drivers. can be

The joint use support system 10 according to the present embodiment described above allows the owner to select the object owned by the owner from among the users who used the object owned by the owner (for example, a car). It is configured to identify (select) a user to whom a particular benefit applicable for use (eg, a coupon with a discount on the usage fee) is granted. Therefore, reuse of the object by a user who is preferable to the owner of the object for joint use is encouraged.

The processes and procedures described herein, other than those explicitly described, may be implemented in software, hardware, or any combination thereof. For example, the processes and procedures described herein are implemented by implementing logic corresponding to the processes and procedures in media such as integrated circuits, volatile memory, non-volatile memory, magnetic disks, and the like. Moreover, the processes and procedures described in this specification can be implemented as computer programs corresponding to the processes and procedures, and can be executed by various computers.

Although the processes and procedures described herein are described as being performed by a single device, software, component or module, such processes or procedures may be performed by multiple devices, software, components or modules. and/or by multiple modules. Also, the software and hardware elements described herein can be implemented by consolidating them into fewer components or decomposing them into more components.

In this specification, even if the components of the invention are described as either singular or plural, or are described without being limited to either singular or plural, they should be interpreted differently depending on the context. , the component may be singular or plural.

10 joint use support system 20 network 30 user terminal 41 information storage management unit 411 target object management table 412 user management table 413 transaction management table 43 basic function control unit 45 transaction management unit 47 privilege giving unit 50 search screen 60 vehicle details screen 70 plan List screen 80 Schedule detail screen 90 User selection screen 100 Coupon creation screen (predetermined screen)
110 Coupon browsing screen 120, 120A Review input screen

Claims (7)

1. A system, comprising one or more computer processors, for supporting collaborative use of objects, comprising:
The one or more computer processors, in response to executing readable instructions,
A process of managing transactions between each of a plurality of owners and each of a plurality of users for the user to use the object owned by the owner;
Execute a process of granting benefits to the user,
The processing for managing the transaction includes a first evaluation of the user by the owner that is open to the users, and a second evaluation of the user by the owner that is not open to the users. including accepting
The process of giving the privilege is
Presenting a plurality of past users who used an object owned by a specific owner to the specific owner, and identifying the specific owner from among the plurality of past users presented Granting intended users specific privileges applicable for use of objects owned by said specific owner ; and
Among a plurality of past users who used objects owned by the specific owner, the first evaluation by the specific owner is within a first range, and the specific owner Automatically granting the specific privilege as the target user to the user whose second evaluation is within a second range ;
system. The process of granting the privilege includes presenting the plurality of past users to the specific owner via a first screen,
wherein the first screen is configured to display the grant status of the privilege for each of the plurality of past users;
The system of Claim 1. The object includes a vehicle or a residence,
3. The system of claim 1 or 2. the benefits include discounts on usage fees for the object;
4. The system of any one of claims 1-3. The process of granting the privilege includes transmitting a predetermined message to the target user in response to granting the specific privilege,
The processing for managing the transaction includes, in response to a request by the target user via the predetermined message, displaying a screen for applying for use of an object owned by the specific owner to the target. including presenting it to users;
5. The system of any one of claims 1-4 . 1. A method, implemented by one or more computers, for supporting collaborative use of an object, comprising:
managing transactions between each of a plurality of owners and each of a plurality of users for the use of objects owned by the owners;
a step of granting a privilege to the user,
The step of managing the transaction includes a first evaluation of the user by the owner that is open to the users and a second evaluation of the user by the owner that is not open to the users. including accepting
The step of granting the privilege includes:
Presenting a plurality of past users who used an object owned by a specific owner to the specific owner, and identifying the specific owner from among the plurality of past users presented Granting intended users specific privileges applicable for use of objects owned by said specific owner ; and
Among a plurality of past users who used objects owned by the specific owner, the first evaluation by the specific owner is within a first range, and the specific owner Automatically granting the specific privilege as the target user to the user whose second evaluation is within a second range ;
Method. A program for supporting joint use of subject matter, comprising:
Upon execution on one or more computers, to said one or more computers,
A process of managing transactions between each of a plurality of owners and each of a plurality of users for the user to use the object owned by the owner;
to execute a process of granting a privilege to the user,
The processing for managing the transaction includes a first evaluation of the user by the owner that is open to the users, and a second evaluation of the user by the owner that is not open to the users. including accepting
The process of giving the privilege is
Presenting a plurality of past users who used an object owned by a specific owner to the specific owner, and identifying the specific owner from among the plurality of past users presented Granting intended users specific privileges applicable for use of objects owned by said specific owner ; and
Among a plurality of past users who used objects owned by the specific owner, the first evaluation by the specific owner is within a first range, and the specific owner Automatically granting the specific privilege as the target user to the user whose second evaluation is within a second range ;
program.

Images