JP2023145235A - Transaction promotion system, transaction promotion method, and transaction promotion program - Google Patents

Abstract

To provide a technique capable of securing continuity of a platform.SOLUTION: A transaction promotion system for promoting transaction of a provider and a user of a service in a community includes a reception unit, a matching unit, and an affinity degree determination unit. The reception unit receives provider service information indicating contents of the service provided by the provider and receives user service information indicating contents of a service desired by the user, and the matching unit creates a combination of the provider service information and the user service information, on the basis of an affinity degree indicating shortness in a psychological distance between the provider and the user determined by the affinity degree determination unit.SELECTED DRAWING: Figure 1

Description

The present invention relates to a transaction promotion system, a transaction promotion method, and a transaction promotion program.

Traditionally, Internet platforms have matched groups of service users and service providers within local communities. Examples of such matching techniques are proposed in, for example, Patent Documents 1, 2, and 3.

For example, Patent Documents 1, 2, and 3 disclose technology that matches service providers and service users by checking service information sent from the service provider and selecting the service that the user desires. Disclosed.

Patent No. 6994129 Patent No. 7002688 JP2021-71880A

Such technology allows a service user to perform matching by selecting a desired service from among services provided by a service provider. However, there have been many cases where the compatibility between the service provider and the service user is not compatible.

In addition, in matching platforms between two parties such as BtoC (Business to Consumer) and CtoC (Consumer to Consumer), the platform is There was a problem with continuity.

In view of the above circumstances, an object of the present invention is to provide a technique that enables matching that is more suitable for providers and users.

Further, in a preferred embodiment of the present invention, an object to be solved is to provide a technology that can ensure continuity of the platform.

In order to solve the above problems, the present invention is a transaction promotion system that promotes transactions between service providers and users in a community, and the transaction promotion system includes a reception section, a matching section, and an affinity determining section. The receiving unit receives provider service information indicating the content of the service provided by the provider and also receives user service information indicating the content of the service desired by the user, and the matching unit includes: A combination of the provider service information and the user service information is created based on a degree of familiarity indicating psychological closeness between the provider and the user determined by the degree of affinity determination unit. .

In order to solve the above problems, the present invention provides a transaction promotion method for promoting transactions between a service provider and a user in a community, wherein the reception unit indicates the content of the service provided by the provider. a step of receiving provider service information and receiving user service information indicating the content of the service desired by the user; A computer executes the step of creating a combination of provider service information and the user service information.

In order to solve the above problems, the present invention is a transaction promotion program that promotes transactions between a service provider and a user in a community, the computer being a provider who shows the content of the service provided by the provider. Accepting service information and user service information indicating the content of the service desired by the user, and determining the provider service information based on the degree of familiarity indicating the closeness of the psychological distance between the provider and the user. and the user service information.
With such a configuration, it is possible to match a provider and a user who are more compatible.

In a more preferred form, the provider service information is a resource for filling a gap when the provider provides a service and/or when the user uses a service, and is provided by a third party. The matching unit further creates the combination including the third-party provided resource based on the type of the third-party provided resource.
With this configuration, even if the provider lacks resources when providing a service, the provider can still provide the service by having a third party provide the resources. can.

In a more preferable form, the familiarity determining unit determines the familiarity based on provider attribute information indicating attributes of the provider and user attribute information indicating attributes of the user.
With such a configuration, the compatibility of the provider and the user can be determined using the provider's and user's attributes.

In a more preferred embodiment, the transaction promotion system further includes a classification section, and the classification section generates user groups by classifying the user attribute information into a predetermined number based on the plurality of user attribute information. The familiarity determination unit determines the familiarity based on the user group and provider attribute information.
With such a configuration, by categorizing the user's attributes, it is possible to understand the user's attributes without receiving input of detailed attributes.

In a more preferred form, the transaction promotion system further includes a storage unit, the storage unit stores a reliability level indicating a high level of reliability of the provider or the user, and the familiarity determination unit stores the reliability level of the provider or the user. The degree of familiarity is determined based on the degree of familiarity.
With this configuration, it is possible to perform more compatible matching by considering the results of previous transactions.

In a more preferred form, the transaction promotion system further includes a performance update unit, and the performance update unit receives an evaluation of the provider from the user after the transaction performance based on the combination, and updates the evaluation and The reliability is updated based on the previous reliability, and the familiarity determining unit determines the familiarity based on the reliability.
With this configuration, the degree of familiarity is determined more appropriately by updating the degree of familiarity using the degree of trust (individual trust) received from the user who used the service to evaluate the transaction. be able to.

In a more preferred form, the familiarity determining unit determines a predetermined value as the familiarity in the case of the combination in which there is no transaction history based on the presence or absence of the transaction.
With such a configuration, matching can be performed even when matching is performed for the first time between a provider and a user.

In a more preferred form, the transaction promotion system further includes a storage unit, the storage unit stores transaction performance information indicating information regarding transaction performance for each of the combinations, and the transaction performance information stores transaction performance information for each of the combinations. It further includes transaction record time information indicating the date and time when the transaction record occurred, and the familiarity determination unit determines, based on the presence or absence of the transaction, the immediately preceding transaction record in the transaction record time information in the case of a combination with the transaction record. The period since the previous transaction is calculated based on the date and time, and the degree of familiarity is updated based on the period.
With this configuration, there are cases where time has passed since the last transaction and the two parties have become estranged, and matching can be performed that reflects such a situation.

In a more preferred form, the transaction promotion system further includes a display processing section, and the display processing section notifies third party information regarding the third party on a user screen used by the user.
With such a configuration, information of a third party other than the provider and the user can be viewed.

In a more preferred form, the display processing unit displays the third party information upon creation of the combination.
With such a configuration, information of a third party can be viewed upon completion of a transaction between a provider and a user.

In a more preferred form, the reception unit receives an input of an amount of investment funds from the third party,
The display processing unit displays the third party information when the amount is equal to or greater than a predetermined value.
With this configuration, it is possible to display information about third parties who have made large investments to the user.

In a more preferred form, the transaction promotion system further includes a monetization section, and the reception section collects user funds, which are funds provided by the users, and provider funds, which are funds provided by the provider. and investment funds provided by a third party, and the monetization unit determines the sources based on the investment funds, user funds, and provider funds.
With such a configuration, it is possible to determine the remuneration paid to the provider.

In a more preferred form, the transaction promotion system includes a proximity determination unit, and the proximity determination unit includes provider attribute information indicating attributes of the provider and user attribute information indicating attributes of the user. , generates a degree of proximity indicating the physical proximity between the provider and the user, and generates a degree of proximity between the provider service information and the user service information based on the degree of proximity. Create a combination.
With this configuration, by using the physical distance between the provider and the user, it is possible to perform matching that takes into account ease of access for problem solving.

In a more preferable form, the matching unit performs the matching based on the available time, which is the time during which the provider can provide the service, and the desired usage time, which is the time when the user wishes to use the service. Create a combination of provider and user.
With such a configuration, matching can be performed at a time desired by the user and the provider.

In a more preferable form, the transaction promotion system further includes a determination unit, the reception unit accepts a price for each service as the provider service information, and the determination unit provides the provider with a price for providing the service. The number of available services is determined based on the source of the remuneration to be paid and the price for each service, and further, after the combination is created, the price of the service provided in the combination and the source Then, the available number of the services is updated based on the price for each service.
With this configuration, it is possible to check the number of times a service can be used.

In a more preferred embodiment, the transaction promotion system further includes a matching score calculation unit, and the matching score calculation unit calculates the degree of appropriateness of the combination based on the provider service information, the user service information, and the degree of familiarity. The matching section extracts an appropriate combination of the provider service information and the user service information based on the calculated matching score, and extracts a suitable combination of the provider service information and the user service information. , perform user matching.
With such a configuration, more compatible matching can be performed by quantitatively calculating the compatibility.

The present invention is effective in providing a technique that allows providers and users to perform matching that is more suitable for them.

FIG. 1 is a block diagram showing the configuration of a system according to an embodiment. FIG. 1 is a hardware configuration diagram of a system according to an embodiment. FIG. 1 is a functional block diagram of an apparatus according to an embodiment. 1 is a processing flowchart of a system according to an embodiment. A monetization processing flowchart of one embodiment. 2 is a matching processing flowchart according to an embodiment. 5 is a processing flowchart of trust confirmation according to an embodiment.

A more detailed explanation will be given below with reference to the accompanying drawings. Preferred embodiments are shown in the drawings. However, it can be implemented in many different forms and is not limited to the embodiments described herein.

For example, in this embodiment, the configuration, operation, etc. of the transaction promotion system 0 will be described, but similar effects can be achieved depending on the method, device, computer program, etc. that are executed. The transaction promotion program in this embodiment may be provided as a computer-readable non-transitory recording medium, or may be provided so as to be downloadable from an external server. The transaction facilitation program may be run on the server computer. In this embodiment, a case will be described in which a transaction promotion system is realized by starting a monetization program in the monetization device 1, which is a server computer, a matching program in the matching device 2, and a trust confirmation program in the trust confirmation device 3.

The present invention provides services for service providers (hereinafter referred to as providers), service users (hereinafter referred to as users), and third parties in a community in a specific region (prefecture, city, ward, town, village, etc.). Matching is performed between the three intervening parties. In this embodiment, an invention will be described in which a provider and a user are matched using the degree of familiarity.

The degree of familiarity in the present invention is an index indicating the psychological distance determined by information regarding attributes and/or transaction results between the user and the provider. In this embodiment, the degree of familiarity is determined based on the closeness of attributes between the user and the provider and information regarding transaction performance. Here, the closeness of the attributes of the user and the provider is determined by the degree of similarity of the user and the provider, such as age, gender, personality, nature, type, etc. classification (group), which will be described later.

In addition, in this embodiment, information regarding transaction results includes individual reliability, which is the statistical processing of evaluations made by one of the users and the provider to the other after service provision, the number of transactions, and the period since the previous transaction. Contains one or more.

Note that in this embodiment, the degree of familiarity is determined based on information regarding the direct transaction history between the user and the provider, but in addition to or in place of the direct transaction history, It may be determined based on information regarding indirect transaction performance of the provider. Here, the information regarding indirect transaction results is information regarding the transaction results of the provider and the user with the common transaction partner when the provider and the user have a common transaction partner. The information regarding indirect transaction performance includes one or more of the individual reliability of the common trading partner, the number of transactions with the common trading partner, and the period since the previous transaction with the common trading partner.

In this embodiment, the degree of familiarity is determined for each combination of a user and a provider, but it may also have more directionality. That is, the degree of familiarity with the provider from the user's perspective and the degree of familiarity with the user from the provider's perspective may be determined respectively. For example, by using a directional index such as individual reliability or evaluation, the degree of familiarity can be determined for each direction.

Further, the third party in the present invention is a person who fills in the gap in matching between the provider and the user. In this embodiment, the third party is a person or organization such as a local government that provides resource support to fill the gap when the provider provides the service and/or when the user uses the service. be. Further, a third party is a person or organization such as an investor who can display information about itself on a user's screen by investing the funds of the remuneration paid as compensation for the provider's service provision.

Note that in the present invention, the provider and the user may be able to take both positions. That is, a person who provides a service as a provider in one transaction can also use the service as a user in another transaction.

<System configuration>
FIG. 1 is a block diagram showing the configuration of a system according to an embodiment. As shown in FIG. 1, the transaction promotion system 0 includes a monetization device 1, a matching device 2, a trust confirmation device 3, a user terminal 4, and a provider terminal 5.

In this embodiment, the monetization device 1, the matching device 2, the trust confirmation device 3, the user terminal 4, and the provider terminal 5 are configured to be able to communicate via the communication network NW. Although the communication network NW is an IP (Internet Protocol) network in this embodiment, there are no restrictions on the type of communication protocol, and there are also no restrictions on the type or size of the network. In this embodiment, the monetization device 1, the matching device 2, and the trust confirmation device 3 communicate via the communication network NW, but they can also communicate via a LAN (Local Area Network) or a WAN (Wide Area Network). may be configured.

Note that as the monetization device 1, the matching device 2, and the trust confirmation device 3, it is possible to use a general-purpose server computer, a personal computer, or the like. Furthermore, in this embodiment, the monetization device 1, the matching device 2, and the trust confirmation device 3 are each exemplified as one server, but the monetization device 1, the matching device 2, and the trust confirmation device 3 can be implemented using multiple computers. It is also possible to configure 3. As the user terminal 4 and the provider terminal 5, a smartphone, a tablet terminal, a personal computer, a wearable device, etc. can be used.

<Hardware configuration>
FIG. 2 is a hardware configuration diagram in this embodiment. FIG. 2A is a diagram showing an example of the hardware configuration of the server 10 (the monetization device 1, the matching device 2, and the trust confirmation device 3). The server 10 includes a processing section 11, a storage section 12, and a communication section 13 as a hardware configuration.

The processing unit 11 includes one or more processors such as a CPU, and controls the entire operation processing of the server 10 by executing the transaction promotion program according to the present invention, the OS, browser software, and other applications.

The storage unit 12 is a HDD, ROM, RAM, etc., and is used when the processing unit 11 executes the transaction promotion program, monetization program, matching program, or trust confirmation program according to the present invention based on the program. Store data etc. When the processing unit 11 executes processing based on a transaction promotion program etc. stored in the storage unit 12, the functional configuration described below is realized.

The communication unit 13 executes communication control with the communication network NW, and performs inputs necessary for operating the server 10 and outputs related to operation results.

FIG. 2(b) is a diagram showing an example of the hardware configuration of the terminal 9 (user terminal 4 and provider terminal 5). Similarly, the terminal 9 includes a processing section 91, a storage section 92, a communication section 93, an input section 94, and an output section 95 as a hardware configuration.

The processing unit 91 of the terminal 9 includes one or more processors such as a CPU, and controls the entire operation processing of the terminal 9. The storage unit 92 of the terminal 9 is an HDD, ROM, RAM, etc., and stores applications for operating the monetization device 1 and the matching device 2, and the like. The communication unit 93 of the terminal 9 controls communication with the communication network NW. The input unit 94 of the terminal 9 is a touch panel, a mouse, a keyboard, etc., and inputs an operation request from a user to the processing unit 91. The output unit 95 of the terminal 9 is a display or the like, and displays the results of processing by the processing unit 91 and the like.

<Monetization device 1>
As shown in FIG. 3, the monetization device 1 includes a reception section 101, a display processing section 102, a monetization section 103, and a resource DB as functional components.

<Resources DB>
The funding DB stores information regarding funding. In this embodiment, the funding DB includes funding information such as identification information of the funding provider (any one of the user, the provider, and a third party that only makes investments), the funding provider name, the category of the funding, and the amount. , the date and time of funding are stored in association with each other. In addition to the funding information, the funding DB may also store funding calculated based on the funding information. Note that all of these may be stored in the storage unit 12 or the like, or some or all of these may be stored in another storage unit. Here, the funding information may include information that can identify the funding provider, such as a company logo, instead of or in place of the funding provider's name.

<Functional components of monetization device 1>
The reception unit 101 receives fund information and stores it in the fund DB. Funds in this embodiment include user funds, which are funds provided by users, provider funds, which are funds provided by providers, and funds provided by third parties who only make investments. Including investment funds. In this embodiment, when these funds are provided to the administrator of the transaction promotion system 0, fund information is registered by specifying the category of funds from an administrator terminal (not shown). At this time, the display processing unit 102 displays on the administrator terminal an amount input screen that accepts input of fund information regarding user funds, provider investments, and investment funds.

The reception unit 101 may accept fund information stored in another server via the communication unit 13. In addition, the display processing unit 102 displays a user fund input screen, a provider fund input screen, and an investment fund input screen on the terminals of users, providers, and third parties, and the reception unit 101 Fund information may be input from each terminal and stored in the fund DB.

The monetization unit 103 determines the funds to be paid to the provider as compensation for providing the service, based on user funds, provider funds, and investment funds. In this embodiment, a portion of user funds, provider funds, and investment funds are allocated to development funds and operating funds for the transaction promotion system 0, and the remaining funds are accounted for as capital. For example, the monetization unit 103 determines the capital by multiplying each of user funds, provider funds, and investment funds by a predetermined ratio and summing them. Specifically, the monetization department 103 calculates the following: 1 million yen (user funds) x 0.5 + 1.5 million yen (provider funds) x 0.7 + 2 million yen (investment funds) x 1 = 3.55 million yen (source capital). Determine the source of funds.

<Matching device 2>
As shown in FIG. 3, the matching device 2 includes a reception section 201, a display processing section 202, a matching section 203, a closeness determination section 206, a proximity determination section 207, a determination section 208, and a performance update section 209 as functional components. , a classification section 210, and a matching information DB. Further, the matching unit 203 includes a matching control unit 204 and a matching score calculation unit 205.

<Matching information DB>
The matching information DB stores provider information, user information, service information, provider service information, combination information, reservation information, insufficient resource information, proximity information, and familiarity information. Some or all of these may be stored in the storage unit 12 or the like, or some of these may be stored in another database or the like.

The provider information includes provider identification information, provider name, provider attribute information, reliability, expertise information, and available time information. The provider attribute information includes the provider's gender, age, personality, address, provider group category, and the like. In addition, when substituting provider attribute information stored in the matching information DB in non-numeric expressions such as gender and personality into the model that calculates the matching score described below, for example, "1. Male", "2. A correspondence table is stored, which is a table in which non-numeric expressions and numerical values correspond, such as ".woman". Note that the provider information may include comments, icon images, and contact information such as a phone number.

Reliability is a comprehensive evaluation given to each provider and user by others. In this embodiment, the reliability is determined based on all the individual reliability associated with each user or provider and external information of the user or provider (described later).

Further, the expertise information is information that is input from the provider at the preliminary input stage, and is information that indicates the expertise of the provider's service. Specifically, the expertise information is a numerical value indicating the presence or absence of expertise or the degree of expertise for each category. In this embodiment, the expertise information is registered as information indicating the presence or absence of expertise for each combination of provider and category.

Further, the provider group category is information determined by the classification unit 210 and indicating to which group the provider belongs. A specific classification method will be described later.

The available time information is information regarding the time when a provider can provide a service, and is information indicating a time zone. In addition, when the available time information stored in the matching information DB as a number that is not uniquely determined, such as a time zone, is substituted into the model that calculates the matching score described later, for example, "1.14:00- 16:00'' and ``2. 16:00-18:00'', which are tables in which non-unique numbers correspond to each other, are stored.

The user information includes user identification information, user name, reliability, and user attribute information. The user attribute information includes the user's gender, age, personality, address, user group category, and the like. Similar to provider information, when substituting user attribute information stored in non-numeric expression into a model, a correspondence table is stored. Note that the user information may include comments, icon images, and contact information such as a phone number. Further, the user group category is information determined by the classification unit 210 and indicating to which group the user belongs.

Service information is information regarding services traded between providers and users. The service information includes service identification information, service name, and category. Note that, like provider information, when service information stored in non-numeric expression is to be substituted into a model, a correspondence table is stored. Here, in this embodiment, a category is information that is equivalent (one-to-one) to a service name, and is comprehensive category information that includes multiple services in each category such as general housework, general education, general childcare, etc. It is. Note that categories may have a one-to-many relationship between categories and service names. The category may be subdivided category information. For example, general housework is comprehensive category information that includes subdivided categories such as childcare and shopping. Note that the service information may include uniform price information indicating a uniform price for each service determined by the system administrator. Further, the uniform price information may be cash currency, points, etc. that are system currency.

The provider service information is information indicating services that each provider can provide, their prices, etc. The provider service information includes provider service identification information, provider identification information, service identification information, insufficient resource category, service provision time, and price information. Here, the insufficient resource category is information indicating a category of resources that are insufficient for the provider to provide a service to the user. For example, categories of insufficient resources regarding human resources include assistants, substitutes, and the like. Categories of insufficient resources regarding goods include childcare supplies, nursing care supplies, and the like. Categories of insufficient resources regarding locations include gymnasiums, playgrounds, and the like.

Further, the price information is information indicating the price of the service determined by the provider, and may be cash currency, points, etc. that are system currency. In this embodiment, the price information is registered for each service in the service information by the administrator, but it may be configured so that it can be independently registered by the service provider.

Reservation information includes reservation identification information, provider service identification information, user identification information, reservation date and time, status, third party resource identification information, and reservation information made by the user to the provider or from one of the provider and the user to the other. Individual reliability is obtained by statistically processing the evaluations. Here, the status includes "before provision", "currently providing", "completed provision", "cancelled", and the like. In this embodiment, a combination of user service information and provider service information (hereinafter simply referred to as a "combination" unless it is unclear) is created, and when a reservation is made and the combination is determined, Reservation information with a status before provision is stored in the matching information DB. The third party resource identification information will be described later.

Proximity information is information indicating the physical distance between the user and the provider. The proximity information includes user identification information, provider identification information, and proximity. Here, a method for determining the degree of proximity will be described later.

The familiarity information is information indicating the psychological distance between the user and the provider. The familiarity information includes user identification information, provider identification information, and familiarity. Further, the familiarity information includes user group identification information, provider group identification information, and familiarity. Here, a method for determining the degree of familiarity will be described later.

Third party provided resource information is information regarding resources provided by a third party to a provider. The third party provided resource information includes third party resource identification information, third party resource name, resource category (type), and available time. Here, in this embodiment, the third-party provided resource is a resource provided by a third party to fill the gap when the provider provides the service and/or when the user uses the service. be. Note that the third party provided resource information may include the name of the third party providing the resource and the location where the resource is provided.

<Functional components of matching device 2>
The reception unit 201 receives information used for matching processing via the input unit 94. In the present embodiment, the reception unit 201 receives input of provider information, user information, provider service information, and third-party provided resource information in the preliminary input stage, and passes the input to the matching information DB.

Further, the display processing unit 202 displays an input screen that accepts input of user service information, and transmits the display processing result to the user terminal 4. The output unit 95 of the user terminal 4 receives the display processing result and displays an input screen. In the matching stage, the reception unit 201 receives input of user service information, which is information regarding a service that each user desires to use, via an input screen. The user service information includes user identification information, service identification information, desired time of use, and desired start date and time of use. Note that the price of the service may be displayed on the input screen, and the user service information input to the reception unit 201 may further include the payable self-payment amount or burden rate.

The display processing unit 202 displays the combinations created by the matching unit 203. In this embodiment, the display processing unit 202 displays one or more created combinations on the service viewing screen of the user terminal 4.

The display processing unit 202 displays third party information regarding a third party on a user screen used by the user. In the present embodiment, the display processing unit 202 displays information on the user screen that allows identification of the funder regarding one or more third parties who have contributed capital. The display processing unit 202 displays information by which the funder can be identified on the user screen when or after the matching unit 203 creates the combination. In addition to the user screen, information that can identify the fund provider may be displayed on the provider screen used by the provider.

Furthermore, when the investment funds received from a third party who only makes investments via the reception unit 201 are equal to or greater than a predetermined value, the display processing unit 202 displays information that allows identification of the fund provider on the user screen. Display processing may also be performed. For example, when the total amount of investment funds received from a single third party is a predetermined value, the display processing unit 202 displays information that allows identification of the third party's fund provider. Further, for example, when the amount of investment funds received at one time from a single third party is a predetermined value, the display processing unit 202 displays information that can identify the fund provider of the third party.

Furthermore, the display processing unit 202 displays the number of acceptable services determined by the determination unit 208. In this embodiment, the display processing unit 202 displays the number of acceptable services in association with each service, and transmits the display processing result to the user terminal 4.

The matching unit 203 creates a combination of provider service information and user service information. In this embodiment, the matching unit 203 creates combinations based on the degree of familiarity stored in the matching information DB. Furthermore, in addition to the degree of familiarity, the attributes of the provider, the attributes of the user, the type of third-party provided resource, the user group and provider group determined by the classification unit 210, the available time, One or more of desired usage time, proximity, and reliability may be used.

The matching control unit 204 sends a matching score calculation request for each combination to the matching score calculation unit 205, receives the matching score, and creates a combination. The matching score calculation unit 205 calculates a matching score indicating the appropriateness of the combination based on the provider service information, the user service information, and the degree of familiarity. In this embodiment, the matching score calculation unit 205 matches user service information and provider service information by inputting provider information, user information, user service information, and provider service information. A matching score is calculated using a matching model that calculates a score. Here, the matching model is created using a known technique such as a neural network, deep learning, or regression analysis, or based on a rule.

Specifically, the matching score calculation unit 205 receives the provider service identification information and the user service information, and acquires the degree of familiarity based on the provider service identification information and the user service information. Furthermore, for non-numerical information included in the provider service information and the user service information, the corresponding numerical values are obtained from the correspondence table. The numerical value, the degree of familiarity, and the numerical expression information are input into a matching model to calculate a matching score.

The matching unit 203 filters the provider service information based on one or more pieces of information (for example, address, time, service type, etc.) included in the user service information, and targets the filtered provider service information. A matching score may be calculated to create a combination.

The matching unit 203 defines a plurality of user groups and a plurality of provider groups, and also defines one or more provider groups corresponding to the user groups. A user group may be determined based on information or user service information, and a matching score may be calculated for provider service information of a provider group corresponding to that user group to create a combination. .

Furthermore, the matching unit 203 identifies combination candidates in descending order of matching score and creates combinations. A specific method for creating combinations will be described later.

The familiarity determining unit 206 determines the familiarity based on provider information and/or provider service information, and user information and/or user service information. In this embodiment, the familiarity determination unit 206 determines the familiarity based on provider attribute information, user attribute information, and reservation information (transaction performance information) for each combination.

The degree of familiarity determining unit 206 determines the degree of familiarity based on the presence or absence of a transaction record for each combination. First, the familiarity determination unit 206 determines whether there is a direct transaction record based on the status of reservation information.

In this embodiment, the familiarity determination unit 206 determines the familiarity based on one or more past transaction records between the user and the provider, if there is a direct transaction record. Specifically, the familiarity determination unit 206 determines the familiarity based on the individual reliability input in the previous transaction as the transaction record.

Furthermore, if there is no direct transaction record, the familiarity determining unit 206 determines whether or not there is an indirect transaction record. If there is no indirect transaction record, a predetermined value determined in advance is determined as the degree of familiarity. On the other hand, if there is a track record of indirect transactions, the degree of familiarity determination unit 206 determines the degree of familiarity based on the individual trustworthiness of the common business partners with whom indirect transactions are made and the number of common business partners. decide.

In addition, in this embodiment, the familiarity determining unit 206 is designed so that the user and the provider can take a position that balances both, but the user and the provider cannot take both positions. If so, we will only judge whether or not there is a direct transaction record. If there is no direct transaction record, a predetermined value is determined as the degree of familiarity, and if there is a direct transaction record, the degree of familiarity is determined based on the transaction record.

Further, the familiarity determining unit 206 may determine the familiarity using the period since the previous transaction in addition to or instead of the individual reliability. Specifically, the familiarity determination unit 206 may calculate the period since the previous transaction based on the reservation date and time (transaction performance time information) of the latest reservation information, and determine the familiarity.

Furthermore, the familiarity level determination unit 206 may determine the familiarity level using a user group and/or a provider group. At this time, the degree of affinity using groups may be determined only when there is no transaction history for each combination, or the degree of affinity may be determined using groups regardless of whether there is a transaction history for each combination. good. Specifically, if there is no transaction record for each combination, the familiarity determination unit 206 determines the usage to which the user belongs based on a predetermined value predetermined for each combination of user group and provider group. A predetermined value corresponding to the combination of the provider group and the provider group to which the provider belongs is determined as the degree of familiarity. On the other hand, if there is a transaction record for each combination, the familiarity determination unit 206 updates the previous familiarity based on a predetermined value determined for each combination.

The proximity determination unit 207 generates a proximity degree indicating the closeness of the physical distance between the provider and the user based on the provider attribute information and the user attribute information, and stores it in the matching information DB. do. Proximity in the present invention is an index indicating the physical distance between the user and the provider, which is determined by the positions of the user and the provider. Specifically, the proximity determination unit 207 generates the proximity based on the user's address included in the user attribute information and the provider's address included in the provider attribute information. Furthermore, using publicly known technology such as GPS (Global Positioning System), the location information of the user and the provider is acquired, and the degree of proximity is generated based on the location information of the user and the location information of the provider. You can.

The determining unit 208 determines the number of available services based on the price for each service and the source of the remuneration to be paid as consideration for providing the provider service, which are received as the provider service information through the receiving unit 201. decide. In the present embodiment, the determining unit 208 specifically determines the number of times that each service can be used by dividing the resource for each service and dividing each divided resource by the price of the corresponding service.

The performance update unit 209 receives the evaluation of the provider from the user after the transaction performance based on the combination, and updates the individual reliability. The performance update unit 209 updates, for example, the average value of past evaluations from the user to the provider as the individual reliability. Furthermore, the performance update unit 209 transmits the evaluation and/or individual reliability and the reliability before update to the trust evaluation update unit 301, receives the changed reliability, and stores it in the matching information DB. . In this embodiment, the evaluation of the user may be received from the provider, and the reliability of the user may also be updated. In addition, in this embodiment, the individual reliability is a comprehensive evaluation calculated by statistically processing past evaluations from one user and a certain provider to the other, but it is not an evaluation for each transaction. There may be. In that case, the track record updating unit 209 transmits the individual reliability, which is the evaluation for the latest transaction, and the reliability before updating to the trust evaluation updating unit 301.

The classification unit 210 classifies users into user groups based on a plurality of user attribute information. Furthermore, providers are classified into provider groups based on a plurality of provider attribute information. In this embodiment, the classification unit 210 specifically generates user groups using a known clustering algorithm such as the k-means method that generates an input number of groups from a plurality of pieces of user attribute information. do. The classification unit 210 also generates provider groups using a similar known algorithm for provider attribute information. Note that the individual groups included in the user group group and the individual groups included in the provider group group may all or partially match, or may be entirely different.

<Functional components of trust confirmation device 3>
As shown in FIG. 3, the trust confirmation device 3 includes a trust evaluation update section 301 and an external information DB.

The reliability evaluation update unit 301 determines the reliability after the update based on the external information stored in the external information DB, the reliability before the update, and the evaluation. In the present embodiment, the trust evaluation updating unit 301 specifically determines the updated trustworthiness based on the presence or absence of a loan and/or the presence or absence of a change regarding loan repayment, age, and annual income as external information.

The external information DB has external information that is information indicating the credibility of the provider. The external information includes provider identification information, provider name, and credit information. Here, credit information is sensitive information such as personal information, and includes information regarding loans such as card loans and bank loans, the presence or absence of loans, and the presence or absence of changes regarding loan repayment. Note that the provider identification information included in the external information DB may be the same as the provider identification information included in the matching information DB. If they are different, it is preferable that provider identification information included in the external information DB is associated with the provider information.

In this embodiment, the trust evaluation updating unit 301 is provided in the trust confirmation device 3, but it may be provided in the matching device 2, which is configured to be able to acquire external information from the trust confirmation device 3. .

<Processing procedure>
Hereinafter, the transaction promotion method using the transaction promotion system and the processing contents of each functional configuration will be explained using FIGS. 4 to 7. Note that the processing shown here is only an example, and the processing procedure may be changed as appropriate.

FIG. 4 is a flowchart showing an overview of processing performed by each device in the transaction promotion system. First, in step SD1 (hereinafter, the "step" in "step SD" is omitted), the monetization device 1 and the matching device 2 perform processing, then in SD2, the matching device performs the processing, and in SD3, trust confirmation Device 3 performs the processing. Specific processing will be explained using FIGS. 5 to 7.

<Monetization process>
FIG. 5 is a flowchart showing the processing of the monetization process. First, in the SD 101, the receiving unit 101 receives input of amounts of user funds, provider funds, and investment funds via the input unit 94 on the input screen. Note that the reception unit 101 may accept funds collected on an external server through crowdfunding or the like via the communication unit 13.

Next, in SD102, the monetization unit 103 determines the funds to be paid as compensation for the provider's service provision, based on the user funds, provider funds, and investment funds received in SD101. The monetization unit 103 then passes the information to the determination unit 208 via the communication unit 13.

Then, in SD103, the determining unit 208 determines the number of services that can be accepted based on the funding and the price for each service included in the service provision information.

<Matching process>
FIG. 6 is a flowchart showing the processing of the matching process. In this embodiment, the matching process is roughly divided into a pre-input stage in which information used for matching is received as SD2A, a matching stage in which a combination of a provider and a user is created as SD2B, and a matching stage in which a combination of a provider and a user is created as SD2C. It has an update stage for updating transaction results.

<Pre-input stage SD2A>
First, in SD201 of the pre-input stage SD2A, the reception unit 201 receives inputs of provider information, provider service information, user information, and third-party provided resource information, and stores them in the matching information DB. Note that this information can be registered at any timing before the matching stage SD2B. Here, on the usage screen of the provider terminal 5, a plurality of categories registered as category information are displayed so as to be selectable, and the selected category is registered as expertise information in the provider information.

<Matching stage SD2B>
First, in SD202 of the matching stage SD2B, the reception unit 201 receives from the user the designation of the desired time and the category of the desired service, and receives the input of user service information from the user terminal 4.

Next, in SD203, the matching score calculation unit 205 calculates the reliability, the degree of familiarity, the provider attribute of the provider information received in SD201, the expertise information, the user attribute of the user information, and the provider service. A matching score is calculated based on the service identification information of the information, the time and category received in the SD 202. Here, the degree of familiarity is determined by the degree of familiarity determination unit 206 based on the transaction performance information for each combination and the attributes of the user and the provider.

In the present embodiment, the familiarity determining unit 206 creates temporary combinations, and determines whether there is a direct or indirect transaction record for each temporary combination based on the presence or absence of transactions. Then, when there is no direct transaction record and no indirect transaction record, the familiarity determination unit 206 determines a predetermined value as the familiarity level. On the other hand, if there is a direct or indirect transaction record, the familiarity determination unit 206 determines the familiarity determined by the familiarity determination unit 206 after the previous transaction record as the familiarity at the time of the transaction record. do. The method of determining the degree of familiarity when there is a previous transaction will be described later in SD209.

Next, in this embodiment, in SD204, the matching unit 203 determines the provider with the highest matching score as a provider candidate for creating a combination, and proceeds to SD205. Note that the matching unit 203 may determine a provider whose degree of familiarity is equal to or greater than a predetermined value and who has the highest matching score as a provider candidate.

In SD205, the matching unit 203 determines whether the identified provider has insufficient resource information.

If the provider identified in SD204 has insufficient resource information (YES in SD205), in SD206, the matching unit 203 determines that there is a third-party provided resource that has a resource category that matches the category of the insufficient resource information. to judge. At this time, it is preferable to check whether the third-party provided resource is reserved based on the reservation information.

In SD206, if there is no third-party provided resource with a category that matches the category of the insufficient resource information (NO in SD206), the matching unit 203 returns to SD203 and creates a combination of providers with the next highest matching score. identified as a candidate.

Then, if the provider identified as a candidate does not have insufficient resource information (NO in SD205), or if there is insufficient resource information but there are resources provided by a third party (YES in SD205 and YES in SD206), creates a combination of the provider specified as the candidate and the user who input the user service information in SD202 (SD207). In this embodiment, the matching unit 203 repeats SD204 to SD206 until one combination is created, but it may repeat SD204 to SD206 until a predetermined number of combinations can be created. Further, the display processing unit 202 displays the combination determined by the matching unit 203, and is configured to be able to accept input such as rejection or decline from the user, and when input such as rejection or decline is accepted, SD204~ It may be configured to repeat SD206 to determine the next combination.

<Update stage SD2C>
First, in SD208 of the update stage SD2C, the performance update unit 209 receives evaluations of the providers of the combination from the users who form the combination created in the matching stage SD2B via the input unit 94 of the user terminal 4. accept. In this embodiment, the evaluation is, for example, a five-point evaluation from 1 to 5 points.

Next, in SD209, the performance update unit 209 updates the individual reliability based on the evaluation received in SD208. Furthermore, the track record updating unit 209 transmits the evaluation and/or individual reliability and the reliability before updating to the trust evaluation updating unit 301, receives the changed reliability, and updates the reliability.

Further, in SD209, the degree of familiarity is determined by the degree of familiarity determination unit 206. For example, when there is a direct transaction record, the closeness determination unit 206 specifies that, after the transaction record of the combination, the affinity determination unit 206 determines that the attributes of the provider that match the provider attribute information included in the provider attribute information that formed the combination are specified. , the degree of familiarity is determined based on the number of user attributes included in the user attribute information forming the combination. In addition, when there is no direct transaction record but there is indirect transaction record, the familiarity determination unit 206 determines the degree of familiarity based on the individual trustworthiness of the common transaction partner.

Further, the familiarity determining unit 206 may determine the familiarity based on the individual reliability updated in the SD 208.

<Trust confirmation process>
FIG. 7 is a flowchart showing the trust confirmation process. First, the SD 301 receives the reliability and evaluation before updating from the matching device 2 via the communication unit 13.

Next, in SD302, the reliability evaluation updating unit 301 calculates reliability based on the individual reliability, the reliability before updating, the evaluation, and external information. In the present embodiment, the trust evaluation updating unit 301 updates the trustworthiness of the provider to a lower value, for example, in the case of a provider whose credit information has a loan and there is a change in loan repayment. Note that the reliability evaluation updating unit 301 may update the reliability based on the evaluation and/or the reliability before updating.

Then, in SD303, the reliability evaluation update unit 301 transmits the reliability updated in SD302 to the matching device 2 via the communication unit 13.

As described above, the monetization device 1 executes the monetization process, the matching device 2 executes the matching process, and the trust confirmation device 3 executes the trust confirmation process, whereby funds are collected in the monetization process, and the provider's trust is established in the trust confirmation process. By ensuring continuity and performing matching in consideration of provider and user information in the matching process, it is possible to ensure continuity and enable more suitable matching between providers and users.

Note that in another embodiment, the transaction promotion program may be activated in a server computer including the monetization device 1, the matching device 2, and the trust confirmation device 3.

0: Transaction promotion system 1: Monetization device 2: Matching device 3: Trust confirmation device 10: Server 11: Processing section 12: Storage section 13: Communication section 4: User terminal 5: Provider terminal 9: Terminal 91: Processing section 92: Storage section 93: Communication section 94: Input section 95: Output section NW: Communication network 101: Reception section 102: Display processing section 103: Monetization section 201: Reception section 202: Display processing section 203: Matching section 204: Matching control Unit 205: Matching score calculation unit 206: Closeness determination unit 207: Proximity determination unit 208: Determination unit 209: Performance update unit 210: Classification unit 301: Trust evaluation update unit

Claims (18)

A transaction promotion system that promotes transactions between service providers and users in a community,
The transaction promotion system includes a reception unit, a matching unit, and a familiarity determination unit,
The reception unit receives provider service information indicating the content of the service provided by the provider and also receives user service information indicating the content of the service desired by the user,
The matching unit is configured to match the provider service information and the user service information based on a degree of closeness indicating psychological distance between the provider and the user determined by the degree of familiarity determination unit. A trade promotion system that creates combinations of. The provider service information is a resource for filling a gap when the provider provides a service and/or when the user uses the service, and is a resource provided by a third party. Contains information indicating the type of resource,
The transaction promotion system according to claim 1, wherein the matching unit creates the combination further including the third party provided resource based on the type of the third party provided resource.
. 3. The familiarity level determination unit determines the familiarity level based on provider attribute information indicating attributes of the provider and user attribute information indicating attributes of the user. The transaction promotion system described in . The transaction promotion system further includes a classification section,
The classification unit generates user groups by classifying the user attribute information into a predetermined number based on the plurality of user attribute information,
The transaction promotion system according to claim 3, wherein the familiarity level determination unit determines the familiarity level based on the user group and provider attribute information. The transaction promotion system according to any one of claims 1 to 4, wherein the familiarity level determination unit determines the familiarity level based on a reliability level indicating a high degree of reliability of the provider or the user. The transaction promotion system further includes a performance update section,
The performance update unit receives an evaluation of the provider from the user after the transaction performance based on the combination, and updates the reliability based on the evaluation and the reliability before updating,
The transaction promotion system according to claim 5, wherein the familiarity level determination unit determines the familiarity level based on the reliability. 7 . The transaction promotion system according to claim 5 , wherein the familiarity determining unit determines a predetermined value as the familiarity in the case of the combination for which there is no transaction history based on whether or not there is a transaction. 7 . The transaction promotion system further includes a storage unit,
The storage unit stores transaction performance information indicating information regarding transaction performance for each of the combinations,
The transaction performance information further includes transaction performance time information indicating the date and time when the transaction performance occurred for each of the combinations,
The familiarity determining unit calculates a period since the previous transaction based on the date and time of the immediately previous transaction performance in the transaction performance time information in the case of a combination with the transaction history based on the presence or absence of the transaction; The transaction promotion system according to any one of claims 5 to 7, wherein the degree of familiarity is updated based on the period. The transaction promotion system further includes a display processing section,
9. The transaction promotion system according to claim 1, wherein the display processing unit notifies third party information regarding the third party on a user screen used by the user. The transaction promotion system according to claim 9, wherein the display processing unit displays the third party information upon creation of the combination. The reception unit receives input of an amount of investment funds from the third party,
11. The transaction promotion system according to claim 9, wherein the display processing section displays the third party information when the amount is equal to or greater than a predetermined value. The transaction promotion system further includes a monetization section,
The reception unit is configured to collect user funds, which are funds provided by the user, provider funds, which are funds provided by the provider, and investment funds, which are funds provided by a third party. Accepts input of amount,
12. The transaction promotion system according to claim 1, wherein the monetization unit determines the source based on the investment fund, user fund, and provider fund. The transaction promotion system includes a proximity determination unit,
The proximity determination unit determines the physical distance between the provider and the user based on provider attribute information indicating attributes of the provider and user attribute information indicating attributes of the user. Generates a proximity measure that indicates the closeness,
13. The transaction promotion system according to claim 1, wherein a combination of the provider service information and the user service information is created based on the proximity. The matching unit matches the provider and usage based on the available time, which is the time during which the provider can provide the service, and the desired usage time, which is the time when the user wishes to use the service. The transaction promotion system according to any one of claims 1 to 13, wherein a combination of persons is created. The transaction promotion system further includes a determination unit,
The reception unit receives a price for each service as the provider service information,
The determining unit determines the number of services available for use based on the source of remuneration to be paid to the provider as consideration for providing the service and the price for each service,
Further, after the combination is created, the available number of the services is updated based on the price of the service provided in the combination, the resource, and the price for each service. The transaction promotion system according to any one of Item 14. The transaction promotion system further includes a matching score calculation unit,
The matching score calculation unit calculates a matching score indicating the degree of appropriateness of the combination based on the provider service information, the user service information, and the degree of familiarity,
The matching unit extracts an appropriate combination of the provider service information and the user service information based on the calculated matching score, and matches the provider and the user. The transaction promotion system according to any one of claims 1 to 15. A transaction promotion method for promoting transactions between service providers and users in a community, the method comprising:
the reception unit receiving provider service information indicating the content of the service provided by the provider and receiving user service information indicating the content of the service desired by the user;
A computer executes the step of creating a combination of the provider service information and the user service information based on a degree of familiarity indicating psychological closeness between the provider and the user. How to promote transactions. A transaction promotion program that promotes transactions between service providers and users in the community,
computer,
accepting provider service information indicating the content of the service provided by the provider and receiving user service information indicating the content of the service desired by the user;
A transaction that functions as an information processing device that creates a combination of the provider service information and the user service information based on a degree of familiarity indicating psychological closeness between the provider and the user. promotion program.