CN111506674A - Matching method and device - Google Patents

Matching method and device Download PDF

Info

Publication number
CN111506674A
CN111506674A CN202010397613.9A CN202010397613A CN111506674A CN 111506674 A CN111506674 A CN 111506674A CN 202010397613 A CN202010397613 A CN 202010397613A CN 111506674 A CN111506674 A CN 111506674A
Authority
CN
China
Prior art keywords
user
users
matching
item
participation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Granted
Application number
CN202010397613.9A
Other languages
Chinese (zh)
Other versions
CN111506674B (en
Inventor
林飞
林晨
孙斌
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202311346324.6A priority Critical patent/CN117370477A/en
Priority to CN202010397613.9A priority patent/CN111506674B/en
Publication of CN111506674A publication Critical patent/CN111506674A/en
Application granted granted Critical
Publication of CN111506674B publication Critical patent/CN111506674B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/28Databases characterised by their database models, e.g. relational or object models
    • G06F16/284Relational databases
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06FELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/24Querying
    • G06F16/245Query processing
    • G06F16/2457Query processing with adaptation to user needs
    • G06F16/24573Query processing with adaptation to user needs using data annotations, e.g. user-defined metadata
    • GPHYSICS
    • G06COMPUTING; CALCULATING OR COUNTING
    • G06QINFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q30/00Commerce
    • G06Q30/02Marketing; Price estimation or determination; Fundraising
    • G06Q30/0201Market modelling; Market analysis; Collecting market data

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Development Economics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Finance (AREA)
  • Physics & Mathematics (AREA)
  • Entrepreneurship & Innovation (AREA)
  • General Engineering & Computer Science (AREA)
  • Library & Information Science (AREA)
  • Computational Linguistics (AREA)
  • Game Theory and Decision Science (AREA)
  • Economics (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

The embodiment of the specification provides a matching method and a matching device, wherein the matching method applied to a credit platform comprises the steps of receiving a participation item selected by a user based on a client and a participation user tag; generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server; receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client; after the credit platform uploads a matching request generated by a user selecting a to-be-participated item and a participated user tag at a client to a server, the credit platform can receive the target user which is close to the user expectation and is quickly and accurately matched by the server based on the to-be-participated item and the participated user tag carried in the matching request, so that the amount of the issue and the rate of response are improved.

Description

Matching method and device
Technical Field
The embodiment of the specification relates to the technical field of computers, in particular to a matching method. One or more embodiments of the present specification relate to a matching apparatus, a computing device, and a computer-readable storage medium.
Background
With the development of internet technology, the internet is adopted for contract establishment, and a mode that people can jointly complete a certain event based on the contract is gradually popularized through the contract, but in the prior art, when people receive the contract, the contract content is not clear, the contract participants are uncertain, and the rejection is easily caused, so that the contract response rate is low.
Therefore, it is urgently needed to provide a matching method which can quickly and accurately match a user to a target user and finally realize establishment of a reasonable contract.
Disclosure of Invention
In view of this, the embodiments of the present specification provide a matching method. One or more embodiments of the present disclosure are directed to a matching apparatus, a computing device, and a computer-readable storage medium, which solve technical problems of the related art.
According to a first aspect of embodiments of the present specification, there is provided a matching method applied to a credit platform, including:
receiving participation items selected by a user based on a client and participation user tags;
generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server;
and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client.
According to a second aspect of the embodiments of the present specification, there is provided a matching method, applied to a server, including:
s1, receiving a matching request sent by a credit platform, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user label selected by the ith user at the corresponding client;
s2, matching the participation items selected by the ith user at the corresponding client with the item set in a preset item library;
s3, judging whether a matched item set exists or not,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, continuing to execute step S1,
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
According to a third aspect of the embodiments of the present specification, there is provided a matching apparatus applied to a credit platform, including:
a first receiving module configured to receive a participation item selected by a user at the client and a participation user tag;
the first request generation module is configured to generate a matching request based on the participation item and the participation user tag, and send the matching request to a server;
a second receiving module configured to receive a target user matched by the server for the user based on the matching request, and return the target user to the user.
According to a fourth aspect of the embodiments of the present specification, there is provided a matching apparatus, applied to a server, including:
a third receiving module, configured to receive a matching request sent by an ith user based on a client, and record receiving time of the matching request, where the matching request carries a participating item and a participating user tag selected by the ith user at a corresponding client;
the first matching module is configured to match the participation item selected by the ith user at the corresponding client with an item set in a preset item library;
a target user determination module configured to determine whether a matching set of items exists,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with association relation under each item set, matching target users for each user, sending the target users of each user to corresponding clients,
if not, increasing i by 1, and continuing to execute the third receiving module;
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
According to a fifth aspect of embodiments herein, there is provided a computing device comprising:
a memory and a processor;
the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:
receiving participation items and participation user tags selected by a user at the client;
generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server;
and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the user.
According to a sixth aspect of embodiments herein, there is provided a computing device comprising:
a memory and a processor;
the memory is used for storing computer executable instructions and the processor is used for executing the computer executable instructions
S1, receiving a matching request sent by an ith user based on a client, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user label selected by the ith user at the corresponding client;
s2, matching the participation items selected by the ith user at the corresponding client with the item set in a preset item library;
s3, judging whether a matched item set exists or not,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with association relation under each item set, matching target users for each user, sending the target users of each user to corresponding clients,
if not, increasing i by 1, and continuing to execute the step S1;
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
According to a seventh aspect of embodiments herein, there is provided a computer-readable storage medium storing computer-executable instructions that, when executed by a processor, implement the steps of the matching method.
One embodiment of the specification realizes a matching method and a matching device, wherein the matching method applied to the credit platform comprises the steps of receiving participation items selected by a user based on a client and participation user tags; generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server; receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client; after the credit platform uploads a matching request generated by a user selecting a to-be-participated item and a participated user tag at a client to a server, the credit platform can receive the target user which is close to the user expectation and is quickly and accurately matched by the server based on the to-be-participated item and the participated user tag carried in the matching request, so that the amount of the issue and the rate of response are improved.
Drawings
FIG. 1 is a flow chart of a matching method applied to a credit platform according to an embodiment of the present disclosure;
fig. 2 is a flowchart of a matching method applied to a server according to an embodiment of the present disclosure;
FIG. 3 is an interaction flow diagram of a matching method provided by an embodiment of the present specification;
FIG. 4 is a schematic structural diagram of a matching device applied to a credit platform according to an embodiment of the present disclosure;
fig. 5 is a schematic structural diagram of a matching apparatus applied to a server according to an embodiment of the present disclosure;
FIG. 6 is a block diagram of a first computing device, provided in one embodiment of the present description;
fig. 7 is a block diagram of a second computing device provided in one embodiment of the present specification.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present description. This description may be embodied in many different forms and should not be construed as limited to the embodiments set forth herein, as those skilled in the art will be able to make and use the present disclosure without departing from the spirit and scope of the present disclosure.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used in one or more embodiments of the present specification refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It will be understood that, although the terms first, second, etc. may be used herein in one or more embodiments to describe various information, these information should not be limited by these terms. These terms are only used to distinguish one type of information from another. For example, a first can also be referred to as a second and, similarly, a second can also be referred to as a first without departing from the scope of one or more embodiments of the present description. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
First, the noun terms to which one or more embodiments of the present specification relate are explained.
And (3) credit agreement: a credible social contact mode is characterized in that an appointment-making party issues appointments through credit appointments, and other personnel participate in the appointments and complete the accumulation of credit after completing corresponding matters together or respectively.
And (4) appointing roles: contractor-the individual who issues the credit agreement; party-the individual who accepts the credit agreement.
Contract theme: the technical personnel or the operation personnel define the scope of the appointed contents, such as eating and drinking music, living, body building and the like.
Contract performing: after the contractor and the contractor have reached the contract, the contract is completed by the desired performance.
And (3) credit accumulation: after the contracts of the two parties are normally finished on time, the two parties can respectively accumulate the own credit wealth.
In this specification, a matching method is provided. One or more embodiments of the present disclosure relate to a matching device, a computing apparatus, and a computer-readable storage medium, which are described in detail in the following embodiments.
With the continuous development of the internet technology, the convenience and richness of life can be greatly improved by applying the internet technology to life. Based on the development of the internet technology, the internet of things technology is widely applied to daily life, electronic contracts are produced as soon as possible, and the technology for realizing contract establishment by two contract parties by using a credit platform is produced as soon as possible.
Referring to fig. 1, fig. 1 shows a flowchart of a matching method applied to a credit platform according to an embodiment of the present specification, including steps 102 to 106.
Step 102: and receiving the participation items selected by the user based on the client and the participation user tags.
The client includes, but is not limited to, a mobile terminal or a fixed terminal, such as a smart phone, a tablet computer, a desktop computer capable of being operated by touch, and the like.
The participating items can be understood as the items that the user wants to participate in, and can also be understood as contract topics on which the user wants to establish a contract, such as contract topics of eating and playing music, contract topics of life classes, contract topics of fitness classes, and the like.
The participating user tag may be understood as a tag of a participating user with whom the user wants to participate in the same participating item, i.e., attribute information of the participating user selected by the user, such as gender, age, hobby, occupation, geographical location, and the like.
For example, the client is a smart phone, the participation item is running, and the participation user tag is female, 25 years old and long; at this time, receiving the participation item and the participation user tag selected by the user at the client, it can be understood that: the credit platform receives participation items selected by a user on a display interface of the smart phone: running and participating user tags: female, 25 years old, growing hair.
Step 104: and generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server.
The matching request generated based on the participation item and the participation user tag carries the participation item and the participation user tag, so that the server side can match a proper target user for the user based on the participation item and the participation user tag.
In practical application, in order to increase user interaction and improve interestingness of a matching process, after receiving a participating item and a participating user tag selected by a user at a client, a matching request is generated based on the participating item and the participating user tag only when receiving action operation of the user based on the client again, and the specific operation mode is as follows:
the client comprises a mobile terminal;
correspondingly, the generating a matching request based on the participation item and the participation user tag comprises:
generating a matching request based on the participation item and the participation user tag under the condition that the user is detected to complete a preset operation action based on the mobile device.
The preset operation actions include, but are not limited to, shaking one time, pressing a certain button in the mobile device for a long time, sliding up or down on a touch display screen of the mobile device, and the like.
Taking the preset operation as a shaking operation as an example, after the credit platform receives the participation item and the participation user tag selected by the user at the mobile terminal, and in case that the user is detected to shake the mobile device, a matching request is generated based on the participation item and the participation user tag.
Step 106: and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client.
The target user is a user of the credit platform receiving and sending the service end and selecting the participation item and the participation user label based on the corresponding client, namely the user of the credit platform selecting the participation item and the participation user label at the client in the matching request of other clients sent by the credit platform, which is received by the service end; for example, the credit platform receives the participation item and the participation user tag selected by the user 1a through the mobile terminal 1a, and receives the participation item and the participation user tag selected by the user 2a through the mobile terminal 2a, generates the matching request 1a based on the participation item and the participation user tag selected by the user 1, generates the matching request 2a based on the participation item and the participation user tag selected by the user 2a, and then sends the matching request 1a and the matching request 2a to the server, so that the user 1a may be the target user of the user 2a based on the matching of the server.
The target user is the target user which is carried in the matching request by the service end and selected by the user at the client, and the participating user tag is matched with the user.
In a specific implementation, the credit platform may receive participation items and participation user tags selected by a plurality of users based on the client at the same time, for example, the credit platform may receive participation items and participation user tags selected by 10 or 30 users through respective smartphones at the same time; after the credit platform simultaneously receives the participation items and the participation user tags selected by a plurality of users based on the client, a matching request is generated based on the participation items and the participation user tags selected by each user through the client, and then each matching request is sent to the server; then after receiving a matching success message returned by the server based on each matching request, uniformly receiving a target user matched for each user by the server based on each matching request, and returning the target user to the corresponding client; the target user is the user except the user, and any one or more other users select the participation item and the participation user label through the smart phone, so that the credit platform generates the matching request.
According to the matching method applied to the credit platform, after the credit platform uploads the item to be participated selected by the user through the client and the matching request generated by the participator user tag to the server, the server can receive the target user which is close to the user expectation for the user based on the item to be participated and the participator user tag carried in the matching request, so that the amount of the offer and the rate of the offer can be improved.
In another embodiment of this specification, after receiving the target user matched by the server for the user based on the matching request, the method further includes:
and constructing a project contract based on the user and the target user, wherein the project contract comprises the to-be-performed items of the user and the target user.
A project contract may be understood as a project contract that implements a contract relationship between a user and a target user, and the project contract has agreed on terms to be performed by the user and terms to be performed by the target user.
When the project contract is specifically implemented, the items to be performed in the project contract are edited based on the participating projects selected by the user and the target user; for example, if the participation item selected by the user is running and the participation item selected by the target user is food, the to-be-performed item of the user in the project contract may be how many kilometers the user needs to run in what time, and the to-be-performed item of the target user may be what food the target user needs to do in what time; in practical application, at least one target user of each user is provided, and a plurality of target users are generally provided, so that a project contract is constructed between one user and a plurality of target users, and then performing performance based on the project contract.
In practical application, because the matching relationship exists between the user and the target user, the user and the target user are extremely similar groups after being matched by the server, so that the project contract is constructed between the user and the target user matched with the user, and the performance rate of the project contract can be greatly improved.
In another embodiment of this specification, after the building a project contract based on the user and the target user, the method further includes:
receiving a fulfillment result of the fulfillment by the user and the target user according to the to-be-fulfilled item in the project contract, and determining a reward value for the user and the target user based on the fulfillment result.
Specifically, after the receiving user and the target user perform according to the to-be-performed items in the constructed project contract, obtaining a performing result of performing, and then determining corresponding reward values for the user and the target user based on the performing result, where the reward values may be credit values representing levels on a credit platform.
In practical application, after a project contract is constructed, if a user completes the performance based on corresponding to-be-performed items in the project contract (for example, running 5 kilometers before 7 am), the to-be-performed items corresponding to the user are completed; the target user also completes the performance based on the corresponding to-be-performed item in the project contract (e.g. making breakfast between 7 a.m. and 7 a.30 a.m.), that is, the to-be-performed item corresponding to the target user is completed, at this time, the performance results of both the user and the target user are completely completed, at this time, corresponding credit values, such as 5 credit values, may be added to the user and the target user, respectively, and the specific reward value may be set according to the actual application, which is not limited herein.
After the user and the target user construct a project contract and complete the performance behavior based on the project contract, the mode of awarding credit values to the user and the target user can encourage the user and the target user to perform the performance behavior in other contracts, so as to encourage all the users to possibly complete the performance and obtain the performance awards, and improve the performance rate.
In another embodiment of this specification, after receiving the target user matched by the server for the user based on the matching request, the method further includes:
and receiving the user label of the target user acquired and returned by the server, and returning the user label to the client.
Specifically, when receiving a target user matched by the server for each user based on each matching request, the credit platform also receives a user tag of each target object itself returned by the server.
For example, the credit platform receives the participating items, participating user tags, and user tags for each user themselves, as selected by user 1, user 2, and user 3, see table 1.
TABLE 1
Client terminal Participating in a project Participant user tags User tag
User 1 Smart phone 1 Exercise of sports Male, 25 years old Female, age 26
User 2 Smart phone 2 Exercise of sports Female, age 26 Female, 28 years old
User 3 Smart phone 3 Food Female, age 26 Male, age 30 years old
At this time, the credit platform receives the target user matched by the service end for the user 1: user 2, then the credit platform may receive not only the target user: user 2, also receives user 2: a woman, a 28 year old user tag, and the credit platform returns the user tag to the client for presentation to user 1 in the client's display.
The target user portrait can be precipitated by adding the user tag of the target user as the user tag by returning the user tag of the target user, so that the target user can be matched more accurately based on rich crowd tags when the target user is selected and matched by the follow-up user.
Referring to fig. 2, fig. 2 is a flowchart illustrating a matching method applied to a server according to an embodiment of the present disclosure, including the following steps:
step 202: receiving a matching request sent by a credit platform, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user tag selected by an ith user at a corresponding client.
Wherein i is a positive integer, and specifically, the participation item and the participation user tag selected by the ith user at the corresponding client may be understood as the participation item and the participation user tag selected by the 1 st user at the corresponding client.
Specifically, receiving the matching request sent by the credit platform includes: receiving a participation item and a participation user tag which are sent by a credit platform and carry the selection of the ith user at the corresponding client; and recording the time of receipt of the matching request.
Step 204: and matching the participation items selected by the ith user at the corresponding client with the item set in the preset item library.
The preset project library comprises a plurality of project sets, and each project set comprises at least one project; in practical applications, one item set is regarded as one bucket, a plurality of buckets are stored in the preset item library, and a plurality of items can be placed in each bucket.
In specific implementation, the participation item selected by the ith user at the corresponding client is matched with the item set in the preset item library, that is, it is determined to which item set in the preset item library the participation item selected by the ith user at the corresponding client belongs, for example, the participation item selected by the ith user at the corresponding client is a sport, and the preset item library has an item set a: and if the user does exercise and eats, matching the participation item selected by the ith user at the corresponding client with the item set a in the preset item library.
Step 206: and judging whether a matched item set exists, if so, executing the step 208, and if not, executing the step 216.
Step 208: and associating the ith user with the matched item set.
Step 210: determining whether the time interval between the receiving time and the current time is greater than or equal to a preset time threshold, if so, executing step 212, and if not, executing step 214.
Step 212: and counting the users with the association relation under each item set, matching target users for each user, and returning the target users of each user to the credit platform.
Step 214: incrementing i by 1, and continuing to execute step 202.
Specifically, step 202 is executed to receive the next matching request sent by the credit platform, and the receiving time of the matching request is recorded.
Step 216: and creating a corresponding item set in the preset item library based on the participation item selected by the ith user at the corresponding client.
Wherein the determining whether there is a matching set of items comprises:
and judging whether an item set matched with the participation item selected by the ith user at the corresponding client exists in the preset item library.
Specifically, matching the participation item selected by the ith user at the corresponding client with an item set in a preset item library, then judging whether the preset item library has an item set matched with the participation item selected by the ith user at the corresponding client,
specifically, the preset time threshold may be set according to an actual application, and is not limited herein, for example, set to 5s or 10s, in the actual application, if the receiving time of the server receiving the matching request and the current time exceed 5s or 10s, the server refuses to receive the matching request sent by the credit platform again, then statistics is performed on the first matching request sent by the received credit platform to the current last matching request, target user matching is performed for each user, and after each user in the matching requests sent by the credit platform matches the target user, the matching request of the credit platform is received again; if the preset time threshold value is not set, the server side always receives a matching request sent by the credit platform and then matches a target user for each user; and the preset time threshold value is set, so that users who want to establish a project contract in the same time period can be clustered, and then each user is reasonably matched with a target user in time, so that the user experience is enhanced.
Under the condition that the participation items selected by the ith user at the corresponding client are matched with the item sets in the preset item library, and the time interval between the receiving time and the current time is greater than or equal to the preset time threshold, the server stops receiving the matching request sent by the credit platform, then counts all the item sets with the association relation with the user, and then matches the target user for each user through the association relation of the user in each item set; the specific implementation mode is as follows:
the counting of users with association relation under each item set, matching of target users for each user, and returning of the target users of each user to the credit platform comprises:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag of the selected participating user,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, determining all users under each associated item set and with the same selected participation items, taking each user as a target user of other users, and returning the target user of each user to the credit platform.
When the method is specifically implemented, all item sets with association relation with users are determined firstly and are taken as association item sets, and then the users with association relation with the item sets under each item set are counted.
For example, still taking table 1 as an example, if the predetermined item library includes: item set 1: sports, item set 2: gourmet, item set 3: travel, item set 4: and (5) taking the car.
Firstly, all item sets which have an association relation with users are taken as association item sets, and the users which have an association relation under each association item set are counted, according to table 1, it can be seen that the users 1 and 2 have an association relation with the item set 1, the users 3 have an association relation with the item set 2, and the item sets 3 and 4 have no association relation with the users, so that all the item sets which have an association relation with the users are the item set 1 and the item set 2, namely association item sets;
at this time, counting users having an association relationship under each association item set, namely counting users 1 and 2 having an association relationship under the item set 1, and counting users 3 having an association relationship under the item set 2;
then, whether users with the same labels of the selected participating users exist in each associated item set is judged, and according to table 1, it can be seen that the user 1 with the association relationship in the item set 1 and the user 2 with the same labels of the selected participating users are different, and only one user 3 with the association relationship exists in the item set 2, so that users with the same labels of the selected participating users do not exist in each associated item set.
In practical application, if there is a user with the same tag selected for participating users, for example, the tags selected for participating users by user aa, user bb and user cc are the same, the user bb and user cc are used as target users of the user aa, and then the user bb and user cc are returned to the credit platform and sent to the mobile terminal of the user aa by the credit platform; the user aa and the user cc are used as target users of the user bb, then the user aa and the user cc are returned to the credit platform, and the credit platform sends the target users to the mobile terminal of the user bb; and taking the user aa and the user bb as target users of the user cc, then returning the user aa and the user bb to a credit platform, and sending the user aa and the user bb to the mobile terminal of the user cc by the credit platform.
If the selected users with the same participating user tags do not exist, judging whether the users with the same participating items exist in each associated item set, and as can be seen from the table 1, the participating items selected by the user 1 and the user 2 in the item set 1 are the same, at this time, taking the user 1 as a target user of the user 2, returning the user 1 to the credit platform to be associated with the user 2, and sending the user 1 to the mobile terminal of the user 2 through the credit platform; user 2 is taken as a target user of user 1, and then user 2 is returned to the credit platform to be associated with user 1, and the credit platform sends the user 2 to the mobile terminal of user 1.
In the embodiment of the specification, the server side matches users with the same tag of the selected participating user in the same project set, so that the matching accuracy of the target user can be improved and the user experience can be enhanced in a manner that the selected participating user tag matches the target user for each user.
In practical application, under each associated item set, if users with the same tags of the selected participating items and the participating users exist, determining all the users with the same tags of the selected participating users, taking each user as a target user of other users, and returning the target user of each user to the credit platform; if only users with the same selected participation items exist, determining all users with the same selected participation items under each associated item set, taking each user as a target user of other users, and returning the target user of each user to the credit platform; if the selected participation item and the participation user with the same label do not exist, the target user matching is carried out on each user according to the credit value of the user on the credit platform as the standard for matching the target user for each user; the specific implementation mode is as follows:
counting users with incidence relation under each item set, matching target users for each user, and returning the target users of each user to the credit platform:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag for the selected participating item and the participating users,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, acquiring credit values of all users under each associated item set, matching target users for each user based on the credit values, and returning the target users of each user to the credit platform.
In specific implementation, if there is no user with the same participating item and participating user tag under a certain associated item set, the credit values of all users under the associated item set can be obtained, then users with closer credit values are determined, and then each user with closer credit value is used as a target user of other users; for example, a user a1, a user a2 and a user a3 with different participating items and different participating user tags exist under the associated item set a, wherein the credit value of the user a1 is 500, the credit value of the user a2 is 200 and the credit value of the user a3 is 600, at this time, it can be determined that the credit values of the user a1 and the user a3 are relatively close, the user a1 can be used as a target user of the user a3, then the user a1 is returned to the credit platform to be associated with the user a3, and the credit platform sends the result to the mobile terminal of the user a 3; and user a3 is the target user of user a1, and then user a3 is returned to the credit platform to be associated with user a1, and sent by the credit platform to the mobile terminal of user a 1.
In this embodiment, if there is no user with the same tag for the selected participating item and the participating user in the associated item set, in order to match the target user with the user, the user with the closer credit value may be used as the target user for matching, so as to avoid returning an empty result to the user, which may result in poor user experience.
In another embodiment of this specification, a reasonable target user may be matched for each user based on a distance between users, and the specific implementation manner is as follows:
the client comprises a mobile terminal;
correspondingly, after receiving the matching request sent by the credit platform, the method further includes:
and acquiring the position information of the mobile terminal.
The position information of the mobile terminals includes, but is not limited to, the distance between the mobile terminals, and the coordinate position of the mobile terminals.
Specifically, counting users having an association relationship under each item set, matching a target user for each user, and returning the target user of each user to the credit platform includes:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
and matching target users for each user based on the position information of the mobile terminal corresponding to each user, and returning the target users of each user to the credit platform.
Specifically, matching the target user for each user based on the location information of the mobile terminal corresponding to each user includes:
determining the position information of the mobile terminal corresponding to each user with an association relation in each association item set, then calculating the distance between every two users and the mobile terminal, counting the users with the distance greater than or equal to a preset distance threshold, and finally taking each user with the distance greater than or equal to the preset distance threshold as a target user of other users; the preset distance threshold includes, but is not limited to, 100m, 200m, or 300m, and the like, and is specifically set according to an actual application, and is not limited herein.
In specific implementation, after determining users having an association relationship under each association item set, matching a target user for each user based on a distance between mobile terminals corresponding to each user; still taking table 1 as an example, if the distance between the mobile terminal of the user 1 and the mobile terminal of the user 2 is 100m, the distance between the mobile terminal of the user 3 is 200m, and the distance between the mobile terminal of the user 2 and the mobile terminal of the user 3 is 100m, the user 2 can be the target user of the user 1, the users 1 and 3 can be the target users of the user 2, and the user 2 can be the target user of the user 3.
In practical application, the life range and the consumption concept of the users in the same area are similar, so that the target user is matched for each user at a distance, other users in the same area are matched for each user as target users, and the response rate of subsequent target users can be greatly improved.
In another embodiment of this specification, after counting users having an association relationship under each item set, matching a target user for each user, and returning the target user of each user to the credit platform, the method further includes:
and acquiring a user tag of a target user of each user, and returning the user tag of the target user to the credit platform.
Specifically, after the target user is matched for each user, the target user of each user is returned to the credit platform, so that project contracts of the users and the target users on the credit platform are constructed, the user tags of the target users matched with each user can be obtained and returned to the credit platform, the user tags are returned to the users by the credit platform, the user tags of the users are enriched, the users can more accurately select the target users based on the enriched user tags when the users match the target users next time, and the follow-up matching of the service end for the users is more accurate.
In the matching method provided in the embodiment of the present specification, after receiving a matching request sent by a credit platform, a server matches a more reasonable target user for each user based on the matching request, so as to improve the possibility of building a project contract between the user and the target user, and improve the contract sending rate and the contract responding rate of the target user.
Referring to fig. 3, fig. 3 is an interactive flowchart of a matching method provided in an embodiment of the present specification, including the following steps:
the matching method provided in the embodiment of the present specification realizes interaction between a credit platform and a server, and details are described by taking an example that a user a, a user b, and a user c all send contract topics and crowd labels to the credit platform based on corresponding mobile terminals, where the user label of the user a is a crowd label 1, the user label of the user b is a crowd label 2, and the user label of the user c is a crowd label 3.
Step 1: contract topic 1, crowd label 2 is selected.
Specifically, the credit platform receives the contract theme 1 and the crowd label 2 selected by the user a at the mobile terminal 1.
Step 1.1: and sending the matching record of the user a to the server.
Specifically, the credit platform selects a contract theme 1 from the mobile terminal 1, and the crowd label 2 generates a matching request to be sent to the server.
Step 1.1.1: polling for matching buckets based on subject and tag.
Specifically, the server queries whether a bucket matched with the contract theme selected by the user a exists in a preset bucket library according to a matching request for the user a sent by the credit platform, if so, the user a is put into the corresponding bucket, and if not, a matched bucket can be newly built according to the contract theme selected by the user a.
Step 1.1.2: bucket a is not generated.
Specifically, if the server does not inquire a bucket matched with the contract theme selected by the user a in the preset bucket library, a matched bucket a can be newly created according to the contract theme selected by the user a.
Step 1.1.3: and (5) matching is successful.
Specifically, after matching the user a to the appropriate bucket, the server sends an indication of successful matching to the credit platform.
Step 1.2: and waiting.
Specifically, wait is performed on the credit platform, and wait for the matching of the server to the user b and the user c, for example, wait for 5 s.
Step 2: contract topic 1, crowd label 1 is selected.
Specifically, the credit platform receives the contract theme 1 and the crowd label 2 selected by the user b at the mobile terminal 2.
Step 2.1: the matching record of the user b is sent to the server.
Specifically, the credit platform selects a contract theme 1 from the mobile terminal 2, and the received user b generates a matching request by the crowd label 1 and sends the matching request to the server.
Step 2.1.1: polling for matching buckets based on subject and tag.
Specifically, the server queries whether a bucket matched with the contract theme selected by the user b exists in a preset bucket library according to a matching request aiming at the user b and sent by the credit platform.
Step 2.1.2: poll bucket a.
Specifically, the server determines that the contract theme selected by the user b is matched as the bucket a according to a matching request aiming at the user b and sent by the credit platform.
Step 2.1.3: and (5) matching is successful.
Specifically, after matching the user b to the appropriate bucket a, the server sends an indication of successful matching to the credit platform.
Step 2.2: and waiting.
Specifically, wait on the credit platform for the matching of the server to the user c.
And step 3: contract theme 1, crowd label 3 are selected.
Specifically, the credit platform receives the contract theme 1 and the crowd label 3 selected by the user c at the mobile terminal 3.
Step 3.1: the matching record of user c is sent to the server.
Specifically, the credit platform selects the contract theme 1 from the mobile terminal 3 by the received user c, and the crowd label 3 generates a matching request and sends the matching request to the server.
Step 3.1.1: polling for matching buckets based on subject and tag.
Specifically, the server queries whether a bucket matched with the contract theme selected by the user c exists in a preset bucket library according to a matching request aiming at the user c and sent by the credit platform.
Step 3.1.2: poll bucket a.
Specifically, the server determines that the contract theme selected by the user c is matched as the bucket a according to a matching request aiming at the user c and sent by the credit platform.
Step 3.1.3: and (5) matching is successful.
Specifically, after matching the user c to the appropriate bucket a, the server sends an indication of successful matching to the credit platform.
Step 3.2: and waiting.
Specifically, after waiting on the credit platform and waiting for the server to match the user a, the user b and the user c in the bucket a, the user b and the user c are used as target users of the user a, the crowd label 2 of the user b and the crowd label 3 of the user c are returned to the credit platform, the user a and the user c are used as target users of the user b, the crowd label 1 of the user a and the crowd label 3 of the user c are returned to the credit platform, the user a and the user b are used as target users of the user c, and the crowd label 1 of the user a and the crowd label 2 of the user b are returned to the credit platform.
Step 3.3: and returning to the users a and b, and simultaneously labeling the users c with labels 1 and 2.
Specifically, the credit platform returns the target users a and b of the user c to the user c, and adds a crowd tag 1 and a crowd tag 2 to the user c.
Step 3.4: and returning to the users a and c, and simultaneously labeling the users b with labels 1 and 3.
Specifically, the credit platform returns the target users a and c of the user b to the user b, and adds a crowd tag 1 and a crowd tag 3 to the user b.
Step 3.5: returning to the users b and c, and marking the labels 2 and 3 for the user a at the same time, wherein three users establish an appointment.
Specifically, the credit platform returns target users b and c of the user a to the user a, and adds a crowd label 2 and a crowd label 3 to the user a.
Based on the matching relationship, the contract establishment of the user a, the user b and the user c is realized, and the contract established on the credit platform based on the user a, the user b and the user c is sent to the user a, the user b and the user c.
In practical application, the above steps may be performed sequentially or simultaneously, and are not limited herein.
In specific implementation, a user a (crowd label 1) selects a contract theme 1 at a client end and defines a crowd label 2, then starts to shake the mobile phone (or long-press a certain button), a user b (crowd label 2) also selects the contract theme 1 at the client end and defines a crowd label 3 at the client end, then starts to shake the mobile phone (or long-press a certain button), a user c (crowd label 3) selects the contract theme 1 at the client end and defines a crowd label 1, then starts to shake the mobile phone (or long-press a certain button), a server end preferentially matches requests of the same contract theme and the same crowd label, places the people in a bucket, returns the users to the users together after waiting for a fixed time, and returns the users who are not matched to be empty, the users are matched again, and the users are matched together, the appointed crowd labels are shared, for example, users a, b and c all have crowd labels 1, 2 and 3, raw materials are provided for subsequent matching, after contracts of the users a, b and c are established, the users a, b and c can see corresponding contract contents in appointed management, three parties need to complete own obligations (items to be performed) on time, and after completion, a credit platform can carry out accumulated reward on credit values of the completed users, so that the users can perceive the increase of own credit; by the matching method, the amount of the appointment and the rate of the appointment can be rapidly increased, the user portrait can be deposited, subsequent matching can be more accurate, the user can be helped to accumulate own credit assets, and credit perception is improved.
The matching method provided by the embodiment of the description adopts a brand-new product form, realizes the quick matching of blind boxes, realizes matching of people of the same class, deposits personal credit labels through products, and enables users to continuously accumulate credits by using continuous performance data of the users, thereby greatly improving the user experience.
Corresponding to the above method embodiment, the present specification further provides an embodiment of a matching device applied to a credit platform, and fig. 4 shows a schematic structural diagram of a matching device provided in an embodiment of the present specification. As shown in fig. 4, the apparatus includes:
a first receiving module 402 configured to receive an engagement item selected by a user based on a client and an engagement user tag;
a first request generation module 404, configured to generate a matching request based on the participating item and the participating user tag, and send the matching request to a server;
a second receiving module 406, configured to receive a target user matched by the server for the user based on the matching request, and return the target user to the client.
Optionally, the apparatus further includes:
a contract construction module configured to construct a project contract based on the user and the target user, wherein the project contract includes the to-be-performed items of the user and the target user.
Optionally, the apparatus further includes:
a fulfillment module configured to receive fulfillment results of the fulfillment by the user and the target user according to the to-be-fulfilled items in the project contract, and determine reward values for the user and the target user based on the fulfillment results.
Optionally, the apparatus further includes:
and the label receiving module is configured to receive the user label of the target user acquired and returned by the server and return the user label to the client.
Optionally, the client includes a mobile terminal;
accordingly, the first request generating module 404 is further configured to:
generating a matching request based on the participation item and the participation user tag under the condition that the user is detected to complete a preset operation action based on the mobile device.
The above is an exemplary scheme of the matching apparatus applied to the credit platform according to the embodiment. It should be noted that the technical solution of the matching device and the technical solution of the matching method applied to the credit platform belong to the same concept, and details that are not described in detail in the technical solution of the matching device can be referred to the description of the technical solution of the matching method applied to the credit platform.
Corresponding to the above method embodiment, the present specification further provides an embodiment of a matching device applied to a server, and fig. 5 shows a schematic structural diagram of the matching device provided in an embodiment of the present specification.
As shown in fig. 5, the apparatus includes:
a third receiving module 502, configured to receive a matching request sent by a credit platform, and record receiving time of the matching request, where the matching request carries a participating item and a participating user tag selected by an ith user at a corresponding client;
a first matching module 504, configured to match the participation item selected by the ith user at the corresponding client with an item set in a preset item library;
a target user determination module 506 configured to determine whether there is a matching set of items,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, and continuing to execute the third receiving module;
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
Optionally, the target user determining module 506 is further configured to:
and judging whether an item set matched with the participation item selected by the ith user at the corresponding client exists in the preset item library.
Optionally, the target user determining module 506 is further configured to:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag of the selected participating user,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, determining all users under each associated item set and with the same selected participation items, taking each user as a target user of other users, and returning the target user of each user to the credit platform.
Optionally, the target user determining module 506 is further configured to:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag for the selected participating item and the participating users,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, acquiring credit values of all users under each associated item set, matching target users for each user based on the credit values, and returning the target users of each user to the credit platform.
Optionally, the client includes a mobile terminal;
correspondingly, the device further comprises:
a location information acquisition module configured to acquire location information of the mobile terminal.
Optionally, the target user determining module 506 is further configured to include:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
and matching target users for each user based on the position information of the mobile terminal corresponding to each user, and returning the target users of each user to the credit platform.
Optionally, the method further includes:
and the label sending module is configured to acquire a user label of a target user of each user and return the user label of the target user to the credit platform.
The foregoing is an exemplary scheme of the matching apparatus applied to the server side in this embodiment. It should be noted that the technical solution of the apparatus applied to the server side and the technical solution of the method applied to the server side belong to the same concept, and details that are not described in detail in the technical solution of the apparatus applied to the server side can be referred to the description of the technical solution of the method applied to the server side
FIG. 6 illustrates a block diagram of a first computing device 600 provided in accordance with one embodiment of the present description. The components of the computing device 600 include, but are not limited to, a memory 610 and a processor 620. The processor 620 is coupled to the memory 610 via a bus 630 and a database 650 is used to store data.
Computing device 600 also includes AN access device 640 that enables computing device 600 to communicate via one or more networks 660. examples of such networks include a Public Switched Telephone Network (PSTN), a local area network (L AN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet Access device 640 may include one or more of any type of network interface, e.g., a Network Interface Card (NIC), wired or wireless, such as AN IEEE802.11 Wireless local area network (W L AN) wireless interface, a Global microwave Internet Access (Wi-MAX) interface, AN Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 600, as well as other components not shown in FIG. 6, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 6 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 600 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 600 may also be a mobile or stationary server.
Wherein processor 620 is configured to execute the following computer-executable instructions:
receiving participation items selected by a user based on a client and participation user tags;
generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server;
and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the matching method applied to the credit platform belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the matching method applied to the credit platform.
FIG. 7 illustrates a block diagram of a second computing device 700 provided in accordance with one embodiment of the present description. The components of the computing device 700 include, but are not limited to, memory 710 and a processor 720. Processor 720 is coupled to memory 710 via bus 730, and database 750 is used to store data.
The computing device 700 also includes AN access device 740, the access device 740 enabling the computing device 700 to communicate via one or more networks 760, examples of which include a Public Switched Telephone Network (PSTN), a local area network (L AN), a Wide Area Network (WAN), a Personal Area Network (PAN), or a combination of communication networks such as the Internet the access device 740 may include one or more of any type of network interface, e.g., a Network Interface Card (NIC), wired or wireless, such as AN IEEE802.11 wireless local area network (W L AN) wireless interface, a Global microwave Internet Access (Wi-MAX) interface, AN Ethernet interface, a Universal Serial Bus (USB) interface, a cellular network interface, a Bluetooth interface, a Near Field Communication (NFC) interface, and so forth.
In one embodiment of the present description, the above-described components of computing device 700, as well as other components not shown in FIG. 7, may also be connected to each other, such as by a bus. It should be understood that the block diagram of the computing device architecture shown in FIG. 7 is for purposes of example only and is not limiting as to the scope of the present description. Those skilled in the art may add or replace other components as desired.
Computing device 700 may be any type of stationary or mobile computing device, including a mobile computer or mobile computing device (e.g., tablet, personal digital assistant, laptop, notebook, netbook, etc.), mobile phone (e.g., smartphone), wearable computing device (e.g., smartwatch, smartglasses, etc.), or other type of mobile device, or a stationary computing device such as a desktop computer or PC. Computing device 700 may also be a mobile or stationary server.
Wherein processor 720 is configured to execute the following computer-executable instructions:
s1, receiving a matching request sent by a credit platform, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user label selected by the ith user at the corresponding client;
s2, matching the participation items selected by the ith user at the corresponding client with the item set in a preset item library;
s3, judging whether a matched item set exists or not,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, continuing to execute step S1,
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
The above is an illustrative scheme of a computing device of the present embodiment. It should be noted that the technical solution of the computing device and the technical solution of the matching method applied to the server belong to the same concept, and details that are not described in detail in the technical solution of the computing device can be referred to the description of the technical solution of the matching method applied to the server.
An embodiment of the present specification also provides a computer readable storage medium storing computer instructions which, when executed by a processor, implement the steps of the matching method.
The above is an illustrative scheme of a computer-readable storage medium of the present embodiment. It should be noted that the technical solution of the storage medium belongs to the same concept as the above technical solution of the matching method applied to the credit platform or the server side, and details of the technical solution of the storage medium, which are not described in detail, can be referred to the above description of the technical solution of the matching method applied to the credit platform or the server side.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The computer instructions comprise computer program code which may be in the form of source code, object code, an executable file or some intermediate form, or the like. The computer-readable medium may include: any entity or device capable of carrying the computer program code, recording medium, usb disk, removable hard disk, magnetic disk, optical disk, computer Memory, Read-Only Memory (ROM), Random Access Memory (RAM), electrical carrier wave signals, telecommunications signals, software distribution medium, and the like. It should be noted that the computer readable medium may contain content that is subject to appropriate increase or decrease as required by legislation and patent practice in jurisdictions, for example, in some jurisdictions, computer readable media does not include electrical carrier signals and telecommunications signals as is required by legislation and patent practice.
It should be noted that, for the sake of simplicity, the foregoing method embodiments are described as a series of acts, but those skilled in the art should understand that the present embodiment is not limited by the described acts, because some steps may be performed in other sequences or simultaneously according to the present embodiment. Further, those skilled in the art should also appreciate that the embodiments described in this specification are preferred embodiments and that acts and modules referred to are not necessarily required for an embodiment of the specification.
In the above embodiments, the descriptions of the respective embodiments have respective emphasis, and for parts that are not described in detail in a certain embodiment, reference may be made to related descriptions of other embodiments.
The preferred embodiments of the present specification disclosed above are intended only to aid in the description of the specification. Alternative embodiments are not exhaustive and do not limit the invention to the precise embodiments described. Obviously, many modifications and variations are possible in light of the above teaching. The embodiments were chosen and described in order to best explain the principles of the embodiments and the practical application, to thereby enable others skilled in the art to best understand and utilize the embodiments. The specification is limited only by the claims and their full scope and equivalents.

Claims (17)

1. A matching method applied to a credit platform comprises the following steps:
receiving participation items selected by a user based on a client and participation user tags;
generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server;
and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client.
2. The matching method of claim 1, after receiving a target user matched by the server for the user based on the matching request, further comprising:
and constructing a project contract based on the user and the target user, wherein the project contract comprises the to-be-performed items of the user and the target user.
3. The matching method of claim 2, after the building of a project contract based on the user and the target user, further comprising:
receiving a fulfillment result of the fulfillment by the user and the target user according to the to-be-fulfilled item in the project contract, and determining a reward value for the user and the target user based on the fulfillment result.
4. The matching method of claim 1, after receiving a target user matched by the server for the user based on the matching request, further comprising:
and receiving the user label of the target user acquired and returned by the server, and returning the user label to the client.
5. The matching method according to claim 1, the client comprising a mobile terminal;
correspondingly, the generating a matching request based on the participation item and the participation user tag comprises:
generating a matching request based on the participation item and the participation user tag under the condition that the user is detected to complete a preset operation action based on the mobile device.
6. A matching method is applied to a server and comprises the following steps:
s1, receiving a matching request sent by a credit platform, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user label selected by the ith user at the corresponding client;
s2, matching the participation items selected by the ith user at the corresponding client with the item set in a preset item library;
s3, judging whether a matched item set exists or not,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, continuing to execute step S1,
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
7. The matching method of claim 6, the determining whether there is a matching set of items comprising:
and judging whether an item set matched with the participation item selected by the ith user at the corresponding client exists in the preset item library.
8. The matching method of claim 7, wherein the counting users who have association relationship under each item set, and matching target users for each user, and returning the target users of each user to the credit platform comprises:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag of the selected participating user,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, determining all users under each associated item set and with the same selected participation items, taking each user as a target user of other users, and returning the target user of each user to the credit platform.
9. The matching method according to claim 6, wherein the users having association relationship under each item set are counted, the target user is matched for each user, and the target user of each user is returned to the credit platform:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
determining whether there are users under each associated item set having the same tag for the selected participating item and the participating users,
if yes, determining all users with the same label of the selected participating users, taking each user as a target user of other users, returning the target user of each user to the credit platform,
if not, acquiring credit values of all users under each associated item set, matching target users for each user based on the credit values, and returning the target users of each user to the credit platform.
10. The matching method according to claim 6, wherein the client comprises a mobile terminal;
correspondingly, after receiving the matching request sent by the credit platform, the method further includes:
and acquiring the position information of the mobile terminal.
11. The matching method of claim 10, wherein counting users having an association relationship under each item set, matching a target user for each user, and returning the target user of each user to the credit platform comprises:
taking all item sets with association relation with users as association item sets, and counting the users with association relation under each association item set;
and matching target users for each user based on the position information of the mobile terminal corresponding to each user, and returning the target users of each user to the credit platform.
12. The matching method according to claim 6, after counting users having an association relationship under each item set, matching a target user for each user, and returning the target user of each user to the credit platform, further comprising:
and acquiring a user tag of a target user of each user, and returning the user tag of the target user to the credit platform.
13. A matching device applied to a credit platform comprises:
a first receiving module configured to receive a participation item selected by a user based on a client and a participation user tag;
the first request generation module is configured to generate a matching request based on the participation item and the participation user tag, and send the matching request to a server;
a second receiving module configured to receive a target user matched by the server for the user based on the matching request, and return the target user to the client.
14. A matching device is applied to a server and comprises:
the third receiving module is configured to receive a matching request sent by a credit platform and record the receiving time of the matching request, wherein the matching request carries a participation item and a participation user tag selected by an ith user at a corresponding client;
the first matching module is configured to match the participation item selected by the ith user at the corresponding client with an item set in a preset item library;
a target user determination module configured to determine whether a matching set of items exists,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, and continuing to execute the third receiving module;
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
15. A computing device, comprising:
a memory and a processor;
the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:
receiving participation items selected by a user based on a client and participation user tags;
generating a matching request based on the participation item and the participation user tag, and sending the matching request to a server;
and receiving a target user matched with the user by the server based on the matching request, and returning the target user to the client.
16. A computing device, comprising:
a memory and a processor;
the memory is to store computer-executable instructions, and the processor is to execute the computer-executable instructions to:
s1, receiving a matching request sent by a credit platform, and recording the receiving time of the matching request, wherein the matching request carries a participation item and a participation user label selected by the ith user at the corresponding client;
s2, matching the participation items selected by the ith user at the corresponding client with the item set in a preset item library;
s3, judging whether a matched item set exists or not,
if yes, the ith user is associated with the matched item set, whether the time interval between the receiving time and the current time is more than or equal to a preset time threshold value or not is judged,
if yes, counting users with incidence relation under each item set, matching target users for each user, returning the target users of each user to the credit platform,
if not, increasing i by 1, continuing to execute step S1,
if not, a corresponding project set is created in the preset project library based on the participation projects selected by the ith user at the corresponding client.
17. A computer readable storage medium storing computer instructions which, when executed by a processor, carry out the steps of the matching method of any one of claims 1 to 12.
CN202010397613.9A 2020-05-12 2020-05-12 Matching method and device Active CN111506674B (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202311346324.6A CN117370477A (en) 2020-05-12 2020-05-12 Matching method and device
CN202010397613.9A CN111506674B (en) 2020-05-12 2020-05-12 Matching method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010397613.9A CN111506674B (en) 2020-05-12 2020-05-12 Matching method and device

Related Child Applications (1)

Application Number Title Priority Date Filing Date
CN202311346324.6A Division CN117370477A (en) 2020-05-12 2020-05-12 Matching method and device

Publications (2)

Publication Number Publication Date
CN111506674A true CN111506674A (en) 2020-08-07
CN111506674B CN111506674B (en) 2023-11-03

Family

ID=71869990

Family Applications (2)

Application Number Title Priority Date Filing Date
CN202311346324.6A Pending CN117370477A (en) 2020-05-12 2020-05-12 Matching method and device
CN202010397613.9A Active CN111506674B (en) 2020-05-12 2020-05-12 Matching method and device

Family Applications Before (1)

Application Number Title Priority Date Filing Date
CN202311346324.6A Pending CN117370477A (en) 2020-05-12 2020-05-12 Matching method and device

Country Status (1)

Country Link
CN (2) CN117370477A (en)

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013020485A (en) * 2011-07-12 2013-01-31 Hideki Matsumura Matching system and matching method
CN105207895A (en) * 2015-09-23 2015-12-30 深圳中创未来科技有限公司 Social contact processing method and device and social contact server
CN108985881A (en) * 2018-06-22 2018-12-11 平安科技(深圳)有限公司 Share room-mate's recommended method, device and computer readable storage medium, server
WO2019080637A1 (en) * 2017-10-27 2019-05-02 上海掌门科技有限公司 Friend recommendation method and device
CN109993329A (en) * 2019-01-31 2019-07-09 阿里巴巴集团控股有限公司 About vehicle information displaying method, device, system and equipment
CN110196951A (en) * 2019-04-24 2019-09-03 上海任意门科技有限公司 User matching method and equipment

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2013020485A (en) * 2011-07-12 2013-01-31 Hideki Matsumura Matching system and matching method
CN105207895A (en) * 2015-09-23 2015-12-30 深圳中创未来科技有限公司 Social contact processing method and device and social contact server
WO2019080637A1 (en) * 2017-10-27 2019-05-02 上海掌门科技有限公司 Friend recommendation method and device
CN108985881A (en) * 2018-06-22 2018-12-11 平安科技(深圳)有限公司 Share room-mate's recommended method, device and computer readable storage medium, server
CN109993329A (en) * 2019-01-31 2019-07-09 阿里巴巴集团控股有限公司 About vehicle information displaying method, device, system and equipment
CN110196951A (en) * 2019-04-24 2019-09-03 上海任意门科技有限公司 User matching method and equipment

Also Published As

Publication number Publication date
CN111506674B (en) 2023-11-03
CN117370477A (en) 2024-01-09

Similar Documents

Publication Publication Date Title
CN108243086B (en) Message processing method and system
US11895563B2 (en) Selectively prompting matched individuals to initiate an in-person meeting
CN111768231B (en) Product information recommendation method and device
US11276075B2 (en) Increasing social media presence using machine-learning relevance techniques
CN105393267A (en) Opportunity events
US20140279626A1 (en) System and method for managing social relationship information
CN111027838B (en) Crowd-sourced task pushing method, device, equipment and storage medium thereof
WO2017143773A1 (en) Crowdsourcing learning method and device
CN109241202B (en) Stranger social user matching method and system based on clustering
CN111353103A (en) Method and apparatus for determining user community information
US10924568B1 (en) Machine learning system for networking
CN113343148A (en) Resource processing method, client, server and system
CN111787042B (en) Method and device for pushing information
CN110232148B (en) Project recommendation system, method and device
CN110197196B (en) Question processing method and device, electronic equipment and storage medium
CN111506674B (en) Matching method and device
CN110737845A (en) method, computer storage medium and system for realizing information analysis
CN106844504B (en) A kind of method and apparatus for sending song and singly identifying
CN112990662B (en) Target resource determination method and device
CN111985900B (en) Information processing method and device
WO2021051874A1 (en) Information pushing method and related device
CN109842546B (en) Conversation expression processing method and device
CN110555703A (en) Credit contract multi-view display method and device
CN113704596A (en) Method and apparatus for generating a set of recall information
WO2017083875A1 (en) A system and method for recording and displaying a reaction to a focus

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant