CN109214884B - Demand matching method and device and electronic equipment - Google Patents

Demand matching method and device and electronic equipment Download PDF

Info

Publication number
CN109214884B
CN109214884B CN201810873602.6A CN201810873602A CN109214884B CN 109214884 B CN109214884 B CN 109214884B CN 201810873602 A CN201810873602 A CN 201810873602A CN 109214884 B CN109214884 B CN 109214884B
Authority
CN
China
Prior art keywords
matching
requirement
resource provider
resource
demand
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.)
Active
Application number
CN201810873602.6A
Other languages
Chinese (zh)
Other versions
CN109214884A (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.)
Advanced New Technologies Co Ltd
Advantageous New Technologies Co Ltd
Original Assignee
Advanced New Technologies 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 Advanced New Technologies Co Ltd filed Critical Advanced New Technologies Co Ltd
Priority to CN201810873602.6A priority Critical patent/CN109214884B/en
Publication of CN109214884A publication Critical patent/CN109214884A/en
Application granted granted Critical
Publication of CN109214884B publication Critical patent/CN109214884B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • 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/06Buying, selling or leasing transactions
    • G06Q30/0601Electronic shopping [e-shopping]
    • G06Q30/0605Supply or demand aggregation

Abstract

One or more embodiments of the present specification provide a method and an apparatus for matching a demand, and an electronic device, where the method may include: determining that a first resource provider has a matching requirement for a specified resource, the matching requirement being marked as an active matching state; searching a target history matching requirement of the corresponding target resource matched with the specified resource in the history matching requirement marked as a passive matching state corresponding to the second resource provider; when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, the matching requirement is modified into a passive matching state.

Description

Demand matching method and device and electronic equipment
Technical Field
One or more embodiments of the present disclosure relate to the field of a demand matching technology, and in particular, to a demand matching method and apparatus, and an electronic device.
Background
The resource provided by the resource provider is recorded in the matching platform, and the resource provider can obtain the resource matched with the self requirement by issuing a matching request to the matching platform. For example, a user may initiate a matching request to the matching platform to cause the matching platform to find a product that meets the needs of the user for the user.
Disclosure of Invention
In view of the above, one or more embodiments of the present disclosure provide a method and an apparatus for matching a demand, and an electronic device.
To achieve the above object, one or more embodiments of the present disclosure provide the following technical solutions:
according to a first aspect of one or more embodiments of the present description, a demand matching method is provided, which is applied to a matching platform; the method comprises the following steps:
determining that a first resource provider has a matching requirement for a specified resource, the matching requirement being marked as an active matching state;
searching a target history matching requirement of the corresponding target resource matched with the specified resource in the history matching requirement marked as a passive matching state corresponding to the second resource provider;
when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, the matching requirement is modified into a passive matching state.
According to a second aspect of one or more embodiments of the present description, there is provided a demand matching device applied to a matching platform; the device comprises:
the determining unit is used for determining that a first resource provider has a matching requirement aiming at a specified resource, and the matching requirement is marked to be in an active matching state;
the searching unit is used for searching a target historical matching requirement matched with the corresponding target resource and the specified resource in the historical matching requirement marked as a passive matching state corresponding to the second resource provider;
when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, the matching requirement is modified into a passive matching state.
According to a third aspect of one or more embodiments of the present specification, there is provided an electronic apparatus including:
a processor;
a memory for storing processor-executable instructions;
wherein the processor executes the executable instructions to implement the requirement matching method according to any of the embodiments.
Drawings
FIG. 1 is an architectural diagram of a demand matching system in accordance with an exemplary embodiment.
FIG. 2 is a flow diagram of a method for demand matching in accordance with an illustrative embodiment.
Fig. 3 is a schematic diagram of a matching platform responding to a matching request according to an exemplary embodiment.
FIG. 4 is a flow diagram of another method for demand matching provided by an exemplary embodiment.
FIG. 5 is a flow chart of another method for demand matching provided by an exemplary embodiment.
Fig. 6 is a schematic structural diagram of an apparatus according to an exemplary embodiment.
FIG. 7 is a block diagram of a demand matching apparatus provided by an exemplary embodiment.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
FIG. 1 is an architectural diagram of a demand matching system in accordance with an exemplary embodiment. As shown in fig. 1, the system may include a matching platform 11, a network 12, a first resource provider 13, and a second resource provider 14.
The matching platform 11 may be a physical server comprising an independent host, or the matching platform 11 may be a virtual server hosted by a cluster of hosts. In the running process, the matching platform 11 may run a server-side program of an application to implement a server of the application. In one or more embodiments of the present disclosure, the matching platform 11 may match the requirements of the first resource provider 13 or the second resource provider 14 by cooperating with the first resource provider 13 and the second resource provider 14.
The first resource provider 13 and the second resource provider 14 provide the matching resources to each other to meet the needs of each other. The first resource provider 13 and the second resource provider 14 may be PCs; of course, a PC is just one type of electronic device that a user may use. In practice it is obvious that also electronic devices of the type such as: tablet devices, notebook computers, Personal Digital Assistants (PDAs), cell phones, etc., to which one or more embodiments of the present disclosure are not limited. In operation, the first resource provider 13 and the second resource provider 14 may initiate a match request to the matching platform 11 to cause the matching platform 11 to find matching needs.
And the network 12 for interaction between the matching platform 11 and the first resource provider 13 and the second resource provider 14 can comprise various types of wired or wireless networks. In one embodiment, the Network 12 may include the Public Switched Telephone Network (PSTN) and the Internet.
Referring to fig. 2, fig. 2 is a flowchart illustrating a method for matching requirements according to an exemplary embodiment. As shown in fig. 2, the method applied to the matching platform may include the following steps:
step 202, determining that a first resource provider has a matching requirement for a specified resource, wherein the matching requirement is marked as an active matching state.
In an embodiment, when a match request initiated by a first resource provider for a specified resource is received, it may be determined that the first resource provider has a matching need for the specified resource. Then, the match requirement may be marked as an active match state. The active matching state can be understood as that the matching platform actively searches for the matching requirement matched with the matching requirement according to the matching requirement marked as the active matching state.
Step 204, searching a target historical matching requirement matched with the corresponding target resource and the specified resource in the historical matching requirement marked as a passive matching state corresponding to the second resource provider; when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, the matching requirement is modified into a passive matching state.
In one embodiment, the first resource provider and the second resource provider provide resources corresponding to each other (e.g., product resources of the same type) to each other, so that when there is a matching demand of each other, the resource meeting the matching demand can be provided to each other. It should be noted that, in the requirement matching scheme of the present specification, the first resource provider and the second resource provider are opposite to each other, and similar to the description manner of "first" and "second", they are only used to distinguish each other. For example, a first resource provider may also be referred to as a second resource provider, and similarly, a second resource provider may also be referred to as a first resource provider, without departing from the scope of this specification.
In an embodiment, when the matching platform searches for a matching requirement matching a certain matching requirement (at this time, the matching platform actively searches, that is, the matching requirement is in an active matching state), and the search fails (that is, the matching requirement is not found, which indicates that there is no matching requirement matching the matching requirement at present), if there is no new matching requirement subsequently, the matching platform continues to perform the search operation (find the matching requirement matching the matching requirement), and the search also fails. Therefore, after the matching platform performs active search operation on a certain matching requirement, if the search fails, the matching requirement can be modified into a passive matching state (at this time, the matching requirement belongs to the historical matching requirement). The passive matching state can be understood as that the matching platform needs not to actively search for the matching requirement marked as the passive matching state, that is, the matching requirement marked as the passive matching state waits for the matching platform to actively execute the search operation (the matching platform actively executes the search operation, which indicates that a new matching requirement exists, and at this time, the matching requirement marked as the passive matching state is possibly matched with the new matching requirement), and is searched. Based on the method for marking the matching requirements, when the first resource provider is determined to have the matching requirements, the matching requirements can be marked as an active matching state, and in the historical matching requirements corresponding to the second resource provider and marked as a passive matching state, the corresponding target historical matching requirements of the target resources matched with the specified resources are searched. Since the matching requirement marked as the active matching state is a new matching requirement and is possibly matched with the historical matching requirement, the probability that the historical matching requirement is matched can be improved by searching the target historical matching requirement in the historical matching requirement marked as the passive matching state, and thus the backlog of the historical matching requirement is effectively reduced.
In one embodiment, when it is determined that the matching requirement exists at the first resource provider, the operation of searching the target historical matching requirement can be executed without delay. The "executing search operation without delay" can be understood as executing search operation in real time when it is determined that a matching demand exists, so that the efficiency of the matching demand can be improved, and the backlog of the matching demand can be reduced; especially, when the matching platform needs to process fewer matching requests currently, the real-time execution of the search operation can fully utilize the processing performance of the matching platform.
In an embodiment, the matching platform may handle the matching requirement in a manner of a server cluster, that is, the matching platform may include a plurality of matching servers, each of which is configured to respond to a matching request initiated by the first resource provider (or the second resource provider) and perform the above-mentioned search operation.
Based on the condition that the matching platform comprises a plurality of matching servers, when any matching server determines that the first resource provider has the matching requirement (namely when a matching request initiated by the first resource provider is received), the matching requirement can be locked to prevent other matching servers from executing the operation of searching the target historical matching requirement, so that the situation that each matching server processes the matching requirement repeatedly can be avoided.
Meanwhile, based on the condition that the matching platform comprises a plurality of matching servers, each matching server executes search operation without mutual influence. When a certain resource is matched with a resource corresponding to a plurality of matching requirements and the plurality of matching requirements are respectively searched by different matching servers, the resource can be searched and hit by the plurality of matching servers, and if the resource is not enough to simultaneously meet the plurality of matching requirements, a conflict is generated. Therefore, when any matching server finds the target historical matching demand, the target resource corresponding to the target historical matching demand is locked, so that other matching servers are prevented from finding other matching demands matched by using the target resource.
In an embodiment, the first resource provider and the second resource provider may both initiate a match request to the match platform. Assume that a first resource provider initiates a first match request and a second resource provider initiates a second match request. Then the match requirement 1 of the first match request and the match requirement 2 of the second match request may exactly match each other. As can be known from the processing mechanism for the matching demands, when the matching platform processes the matching demand 1 and the matching demand 2, the matching demand is preferably searched in the historical matching demands marked as the passive matching state, and the matching demand 1 and the matching demand 2 are both marked as the active matching state, so that the matching demand 1 and the matching demand 2 cannot be matched in time, and the efficiency of the matching demand is reduced. Therefore, for the above-mentioned "two matching demands are missed", a preset threshold number and a delay time may be configured to reduce the probability that two matching demands are missed. As an exemplary embodiment, when any matching requirement marked as an active matching state does not find other matching requirements, if the search operation is executed again after a preset delay time period until the number of times of executing the search operation exceeds a preset number threshold and the search fails, the any matching requirement is modified into a passive matching state. For example, assuming that the preset number threshold and the preset delay time are configured for the first resource provider, as described above. Then, when the matching platform executes the search operation for the matching requirement 1, if the search fails (no matching requirement exists in the historical matching requirements, and the matching requirement 2 is currently in the active matching state), the search operation is executed again after a preset delay time, and at this time, the matching requirement 2 may be modified into the passive matching state, so that the matching platform can search the matching requirement 2 in the historical matching requirements, and further the matching efficiency of the matching requirement is improved. Further, when the number of times of executing the search operation exceeds a preset number threshold, the matching requirement 1 is modified into a passive matching state, so that the situation that other matching requirements marked as an active matching state are backlogged due to the fact that the matching platform processes the matching requirement 1 for a long time is avoided. It should be noted that, due to the existence of the preset number threshold, the matching platform may execute the search operation for multiple times according to the same matching requirement, and the delay durations between adjacent search operations may be the same or different. Meanwhile, specific values of the preset number threshold and the delay duration may be flexibly set according to actual conditions, which is not limited by one or more embodiments of the present specification.
In an embodiment, the preset number threshold and the delay duration are configured for both the first resource provider and the second resource provider, for example, a first preset number threshold and a first delay duration are configured for the first resource provider, and a second preset number threshold and a second delay duration are configured for the second resource provider. Then, if the first match request is initiated at the same time as the second match request, the "miss" problem described above may still occur. Thus, the following settings may be implemented: the first preset time threshold configured for the first resource provider is different from the second preset time threshold configured for the second resource provider; and/or the first preset delay duration configured for the first resource provider is different from the second preset delay duration configured for the second resource provider. By staggering the preset time thresholds and/or delay durations configured for the first resource provider and the second resource provider, the problem that the matching demand 1 and the matching demand 2 are missed can be effectively avoided, and the matching demand efficiency is improved.
For the convenience of understanding, the requirement matching scheme of the specification is described in detail in the following with reference to the accompanying drawings.
Referring to fig. 3, fig. 3 is a schematic diagram of a matching platform responding to a matching request according to an exemplary embodiment. As shown in fig. 3, assume that the first resource provider is resource provider a and the second resource provider is resource provider B. The resource provider A and the resource provider B mutually provide resources corresponding to each other (for example, product resources of the same type) for each other, so that the resources meeting the matching requirement can be provided for each other when the matching requirement exists. The following describes a process of responding to a matching request by the matching platform by taking A2B (i.e. AtoB, which indicates that the resource provider a initiates a matching request to the matching platform and matches the matching requirement of the resource provider B) as an example (the case of B2A is similar to A2B).
When a matching requirement A exists in a user on the resource provider A side, a matching request can be initiated to a matching platform through the resource provider A. After receiving the matching request, the matching platform responds to the matching request without delay (namely real-time), and the matching requirement A is stored in the resource provider A base table. The resource provider A base table is used for recording matching requirements corresponding to the matching requests initiated by the resource provider A. Meanwhile, the matching platform performs a search operation without delay to acquire a matching demand (matching demand of the resource provider B) matching the matching demand a. By executing the operation in real time, the efficiency of matching requirements can be improved, and the backlog of matching requirements can be reduced; especially, when the matching platform needs to process fewer matching requests currently, the real-time execution of the search operation can fully utilize the processing performance of the matching platform. The matching platform can process matching requirements in a server cluster mode, namely the matching platform can comprise a plurality of matching servers, and each server is used for responding to matching requests initiated by a resource provider A and a resource provider B so as to improve matching efficiency of the matching requirements.
The following describes in detail the process of performing the search operation by the matching platform in this description with reference to fig. 4-5.
Referring to fig. 4, fig. 4 is a flowchart of another requirement matching method according to an exemplary embodiment. As shown in fig. 4, the method applied to the matching platform may include the following steps:
step 402, a match request is received.
Step 404, determining that the resource provider A has a matching requirement.
And step 406, marking the determined matching requirement as an active matching state.
In this embodiment, when a matching request initiated by the resource provider a for a specified resource is received, it may be determined that the resource provider a has a matching requirement a for the specified resource. Then the MATCH requirement a may be marked as an active MATCH status (e.g., the MATCH requirement a may be marked as WAIT MATCH). The active matching state can be understood as that the matching platform actively searches for the matching requirement matched with the matching requirement according to the matching requirement marked as the active matching state.
Step 408, locking the matching requirements.
In this embodiment, based on the situation that the matching platform includes multiple matching servers, when any matching server determines that the resource provider a has the matching requirement a, the matching requirement a may be locked to prevent other matching servers from performing an operation of searching for a target history matching requirement (matching the matching requirement a), so that it is possible to prevent each matching server from repeatedly processing the matching requirement a.
For example, assuming that the matching platform comprises matching servers 1-6, the matching server 1 preferentially processes the matching requirement a; the match server 1 may lock the match demand a to prevent the match servers 2-6 from processing the match demand a. For example, the MATCHING requirement A may be marked MATCHING to indicate that the MATCHING requirement A is locked.
Step 410, searching for a target history matching requirement of the corresponding target resource and the specified resource.
In this embodiment, when the matching platform searches for a matching requirement matching a certain matching requirement (at this time, the matching platform actively searches, that is, the matching requirement is in an active matching state), and the search fails (that is, the matching requirement is not found, which indicates that there is no matching requirement matching the matching requirement at present), if there is no new matching requirement subsequently, the matching platform continues to execute the search operation (find the matching requirement matching the matching requirement), and the search also fails. Therefore, after the matching platform performs active search operation on a certain matching requirement, if the search fails, the matching requirement can be modified into a passive matching state (at this time, the matching requirement belongs to the historical matching requirement). The passive matching state can be understood as that the matching platform needs not to actively search for the matching requirement marked as the passive matching state, that is, the matching requirement marked as the passive matching state waits for the matching platform to actively execute the search operation (the matching platform actively executes the search operation, which indicates that a new matching requirement exists, and at this time, the matching requirement marked as the passive matching state is possibly matched with the new matching requirement), and is searched. Based on the above manner of marking matching demands, when it is determined that the resource provider a has the matching demand a, the matching demand a can be marked as an active matching state (step 406), and a target historical matching demand matching the corresponding target resource and the specified resource is searched in the historical matching demand marked as a passive matching state corresponding to the resource provider B. Since the matching requirement marked as the active matching state is a new matching requirement (for example, matching requirement A), the matching requirement is possibly matched with the historical matching requirement, and the probability that the historical matching requirement is matched can be improved by searching the target historical matching requirement in the historical matching requirement marked as the passive matching state preferentially, so that the backlog of the historical matching requirement is effectively reduced.
For example, a user issues a match request to the matching platform to indicate that there is a matching need to purchase a certain financial product, but there is no financial product currently matching the matching need by the merchant, at which point the matching need is marked as a passive matching status. When a merchant issues a new financing product (assuming that the financing product just meets the matching requirement of the user) and issues a matching request to a matching platform to indicate that the matching requirement for selling the financing product exists (at this moment, the matching requirement is marked as an active matching state), the matching platform can improve the efficiency of successful search by searching matched matching requirements in the history matching requirement marked as a passive matching state preferentially, so that the waiting time of the user is reduced, and the user experience is facilitated to be improved.
In step 412, it is determined whether the search is successful, and if the search is successful, the process proceeds to step 416, otherwise, the process proceeds to step 414.
And step 414, modifying the state into a passive matching state.
In this embodiment, when a target historical matching requirement matching with the matching requirement a is not found, the matching requirement a may be modified into a passive matching state, so as to determine whether the matching requirement matches with the matching requirement when the matching requirement of the resource provider B is subsequently processed. For example, MATCH requirement A may be modified to WAIT _ NEW _ MATCH.
At step 416, the target resource is locked.
In this embodiment, based on the situation that the matching platform includes a plurality of matching servers, each matching server performs the search operation without affecting each other. When a certain resource is matched with a resource corresponding to a plurality of matching requirements and the plurality of matching requirements are respectively searched by different matching servers, the resource can be searched and hit by the plurality of matching servers, and if the resource is not enough to simultaneously meet the plurality of matching requirements, a conflict is generated. Therefore, when the target historical matching requirements matched with the corresponding target resources and the specified resources are found, the target resources can be locked to prevent other matching servers from finding other matching requirements matched with the target resources.
For example, suppose there is a match demand X for selling product 1, with a sum of 5000 dollars and a quantity of 3 dollars; the matching demand A is a product 1 of which the purchase price is 10000 yuan and is processed by a matching server a, and the matching demand B is a product 1 of which the purchase price is 15000 yuan and is processed by a matching server B. As can be seen, product 1 matches the resources corresponding to matching demand A and matching demand B (i.e., 10000 yuan product 1, 15000 yuan product 1). However, if the number of products 1 is not sufficient to satisfy both match demand a and match demand B. Then, assuming that the matching server a finds the matching demand X first, the resource product 1 corresponding to the matching demand X may be locked to exclusively preempt the product 1. For example, a number of 2 products 1 may be preempted.
And step 418, modifying the matching requirement A into a matched state.
In this embodiment, when the historical matching requirement of the target is found, the matching requirement a may be modified to be in a matched state. For example, match requirement A may be modified to MATCHED to indicate that the marked match requirement has been MATCHED.
In this embodiment, when the target historical matching demand is found but the amount of the target resource is not enough, the matching demand may be updated back to the active matching state (i.e., WAIT _ MATCH), so as to continue performing the search operation on the matching demand a until the target historical matching demand is found and the amount of the target resource is enough, and then modify the matching demand a into MATCHED.
For example, assume that match demand A is purchase product 1 and the amount is 6000 dollars; the target history matching demand is 1 product for sale, the amount is 2000 yuan, and the quantity is 2. It can be seen that the amount of the target resource is not enough (the amount of the target resource is 2, and the total amount is 4000 yuan <6000 yuan). The MATCH A may be updated from MATCHING back to WAIT _ MATCH to re-execute the above operations of steps 406 and 418 until the final amount reaches 6000 dollars.
In this embodiment, when the target history matching demand is found, the log stream for processing the matching demand a this time can be generated by landing. The log stream can record information such as the ID of the matching demand A, the ID of the target historical matching demand, the ID of the target resource, the quantity of the target resource, the time and the like. Of course, the above description is merely exemplary of specific contents of the log stream, and one or more embodiments of the present disclosure are not limited to specific contents of the log stream.
In this embodiment, when the target history matching requirement is found, a final search result may be broadcast, or the search result may be notified to the device that subsequently processes matching requirement a through system call. The content of the search result may be flexibly set according to the actual situation, for example, the log stream may be used as a part of the search result, and one or more embodiments of the present specification do not limit the specific content of the log stream.
In this embodiment, when the requirement matching scheme of the present disclosure is abnormally interrupted, the operations of steps 402 and 418 may be performed according to a preset period to process the matching requirement marked as WAIT _ MATCH.
In the requirement matching scheme of the present specification, the matching platform can process matching requirements of the resource provider a and the resource provider B at the same time. The method comprises the steps that a resource provider A requests a matching requirement A, and a resource provider B requests a matching requirement B; then, the matching demand a and the matching demand B may exactly match each other. As can be known from the processing mechanism for the matching demands, when the matching platform processes the matching demand a and the matching demand B, the matching demand is preferably searched in the historical matching demands marked as the passive matching state, and the matching demand a and the matching demand B are both marked as the active matching state, so that the matching demand a and the matching demand B cannot be matched in time. Therefore, for the above-mentioned "two matching demands are missed", a preset threshold number and a delay time may be configured to reduce the probability that two matching demands are missed. This is explained below with reference to fig. 5.
Referring to fig. 5, fig. 5 is a flowchart of another requirement matching method according to an exemplary embodiment. As shown in fig. 5, the method applied to the matching platform may include the following steps:
step 502, perform a lookup operation.
In this embodiment, the step of performing the search operation is the process of the above step 404 and 410, which is not described herein again.
In step 504, it is determined whether the search is successful, and if the search is successful, the process proceeds to step 506, otherwise, the process proceeds to step 510.
Step 506, target resource is locked
And step 508, modifying the matched state.
In the present embodiment, the steps 506-508 are similar to the steps 416-418, and are not described herein again.
Step 510, determining whether the number of times of performing the search operation exceeds a preset number threshold, if so, turning to step 512, otherwise, returning to step 502.
In this embodiment, when the step 502 is executed again, the step 502 is executed after a preset delay time period.
And step 512, modifying the state into a passive matching state.
In this embodiment, a preset number threshold a and a preset delay time b are configured for the resource provider a. Then, when the matching platform executes the search operation according to the matching requirement a, if the search fails (no matching requirement exists in the historical matching requirements, and meanwhile, the matching requirement B is currently in an active matching state), the search operation is executed again after a preset delay time, and at this time, the matching requirement B may be modified into a passive matching state, so that the matching platform can search the matching requirement B in the historical matching requirements, and further, the matching efficiency of the matching requirement is improved. Furthermore, when the number of times of executing the search operation exceeds a preset number threshold, the matching requirement A can be modified into a passive matching state, so that the situation that other matching requirements marked as an active matching state are backlogged due to the fact that the matching platform processes the matching requirement A for a long time is avoided. It should be noted that, due to the existence of the preset number threshold, the matching platform may execute the search operation for multiple times according to the same matching requirement, and the delay durations between adjacent search operations may be the same or different. Meanwhile, specific values of the preset number threshold and the delay duration may be flexibly set according to actual conditions, which is not limited by one or more embodiments of the present specification.
In this embodiment, a preset number threshold and a delay duration may be configured for both the resource provider a and the resource provider B, for example, a preset number threshold a and a delay duration B are configured for the resource provider a, and a preset number threshold c and a delay duration d are configured for the resource provider B. Then, if the matching platform starts to process the matching demand a and the matching demand B at the same time (both the matching demand a and the matching demand B are marked as the active matching state), the above-mentioned "missing" problem may still occur. Thus, the following settings may be implemented: the preset times threshold a is different from the preset times threshold c; and/or the delay period c is different from the delay period d. In other words, the problem of "the matching demand a and the matching demand B miss" can be avoided only by any one of the preset time threshold and the preset delay time of the resource provider a and the resource provider B being different. By staggering the preset time thresholds and/or delay durations configured by the resource provider A and the resource provider B, the problem that the matching demand A and the matching demand B are missed can be effectively avoided, and the matching demand efficiency is improved.
Fig. 6 is a schematic structural diagram of an apparatus according to an exemplary embodiment. Referring to fig. 6, at the hardware level, the apparatus includes a processor 602, an internal bus 604, a network interface 606, a memory 608 and a non-volatile memory 610, but may also include hardware required for other services. The processor 602 reads a corresponding computer program from the non-volatile memory 610 into the memory 608 and runs the computer program to form a demand matching apparatus on a logical level. Of course, besides software implementation, the one or more embodiments in this specification do not exclude other implementations, such as logic devices or combinations of software and hardware, and so on, that is, the execution subject of the following processing flow is not limited to each logic unit, and may also be hardware or logic devices.
Referring to fig. 7, in a software implementation, the requirement matching apparatus may include:
a determining unit 701, configured to determine that a first resource provider has a matching requirement for a specified resource, where the matching requirement is marked as an active matching state;
a searching unit 702, configured to search, in the history matching requirements marked as a passive matching state corresponding to the second resource provider, a target history matching requirement in which the corresponding target resource matches the specified resource;
when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, the matching requirement is modified into a passive matching state.
Optionally, the search unit 702 is specifically configured to:
and when the first resource provider is determined to have the matching requirement, the operation of searching the target history matching requirement is executed without delay.
Optionally, the matching platform includes a plurality of matching servers; the device further comprises:
and a first locking unit 703, configured to lock the matching demand when any matching server determines that the first resource provider has the matching demand, so as to prevent other matching servers from performing an operation of searching the target historical matching demand.
Optionally, the matching platform includes a plurality of matching servers; the device further comprises:
a second locking unit 704, configured to lock, when any matching server finds the target historical matching demand, a target resource corresponding to the target historical matching demand, so as to prevent other matching servers from finding other matching demands matching with the target resource.
Optionally, when any matching requirement marked as an active matching state does not find other matching requirements matched with the active matching state, if the search operation is executed again after a preset delay time is up to the time when the number of times of executing the search operation exceeds a preset number threshold and the search fails, the matching requirement is modified into a passive matching state.
Optionally, the first preset time threshold configured for the first resource provider is different from the second preset time threshold configured for the second resource provider; and/or the first preset delay duration configured for the first resource provider is different from the second preset delay duration configured for the second resource provider.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
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 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 herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.

Claims (9)

1. A demand matching method is applied to a matching platform; the method comprises the following steps:
determining that a first resource provider has a matching requirement for a specified resource, the matching requirement being marked as an active matching state; the matching demand comprises a matching demand based on sales behaviors and purchasing behaviors;
searching a target history matching requirement of the corresponding target resource matched with the specified resource in the history matching requirement marked as a passive matching state corresponding to the second resource provider;
when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, modifying the matching requirement into a passive matching state;
when any matching requirement marked as an active matching state does not find other matching requirements matched with the active matching state, if the searching operation is executed again after a preset delay time is up to the time when the number of times of executing the searching operation exceeds a preset number threshold and the searching is failed, the matching requirement is modified into a passive matching state; the first preset time threshold configured for the first resource provider is different from the second preset time threshold configured for the second resource provider; and/or the first preset delay duration configured for the first resource provider is different from the second preset delay duration configured for the second resource provider.
2. The method of claim 1, wherein the searching for the historical matching demand of the corresponding target resource matching the specified resource from the historical matching demands of the second resource provider marked as the passive matching state comprises:
and when the first resource provider is determined to have the matching requirement, searching the target history matching without delay.
3. The method of claim 1, the matching platform comprising a plurality of matching servers; the method further comprises the following steps:
when any matching server determines that the first resource provider has the matching requirement, the matching requirement is locked to prevent other matching servers from executing the operation of searching the target historical matching requirement.
4. The method of claim 1, the matching platform comprising a plurality of matching servers; the method further comprises the following steps:
when any matching server finds the historical matching requirements of the target, target resources corresponding to the historical matching requirements of the target are locked, so that other matching servers are prevented from finding other matching requirements matched with the target resources.
5. A demand matching device is applied to a matching platform; the device comprises:
the determining unit is used for determining that a first resource provider has a matching requirement aiming at a specified resource, and the matching requirement is marked to be in an active matching state; the matching demand comprises a matching demand based on sales behaviors and purchasing behaviors;
the searching unit is used for searching a target historical matching requirement matched with the corresponding target resource and the specified resource in the historical matching requirement marked as a passive matching state corresponding to the second resource provider;
when any matching requirement is marked as an active matching state and other matching requirements matched with the matching requirement are not found, modifying the matching requirement into a passive matching state;
when any matching requirement marked as an active matching state does not find other matching requirements matched with the active matching state, if the searching operation is executed again after a preset delay time is up to the time when the number of times of executing the searching operation exceeds a preset number threshold and the searching is failed, the matching requirement is modified into a passive matching state; the first preset time threshold configured for the first resource provider is different from the second preset time threshold configured for the second resource provider; and/or the first preset delay duration configured for the first resource provider is different from the second preset delay duration configured for the second resource provider.
6. The apparatus according to claim 5, wherein the search unit is specifically configured to:
and when the first resource provider is determined to have the matching requirement, the operation of searching the target history matching requirement is executed without delay.
7. The apparatus of claim 5, the matching platform comprising a plurality of matching servers; the device further comprises:
and the first locking unit locks the matching demand when any matching server determines that the first resource provider has the matching demand, so as to prevent other matching servers from executing the operation of searching the target historical matching demand.
8. The apparatus of claim 5, the matching platform comprising a plurality of matching servers; the device further comprises:
and the second locking unit is used for locking the target resource corresponding to the target historical matching demand when any matching server finds the target historical matching demand so as to prevent other matching servers from finding other matching demands matched with the target resource.
9. An electronic device, comprising:
a processor;
a memory for storing processor-executable instructions;
wherein the processor implements the method of any one of claims 1-4 by executing the executable instructions.
CN201810873602.6A 2018-08-02 2018-08-02 Demand matching method and device and electronic equipment Active CN109214884B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN201810873602.6A CN109214884B (en) 2018-08-02 2018-08-02 Demand matching method and device and electronic equipment

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN201810873602.6A CN109214884B (en) 2018-08-02 2018-08-02 Demand matching method and device and electronic equipment

Publications (2)

Publication Number Publication Date
CN109214884A CN109214884A (en) 2019-01-15
CN109214884B true CN109214884B (en) 2022-04-15

Family

ID=64988526

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201810873602.6A Active CN109214884B (en) 2018-08-02 2018-08-02 Demand matching method and device and electronic equipment

Country Status (1)

Country Link
CN (1) CN109214884B (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110135988A (en) * 2019-04-26 2019-08-16 阿里巴巴集团控股有限公司 A kind of processing method of information, device, equipment and system

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101938789A (en) * 2009-07-01 2011-01-05 中兴通讯股份有限公司 Method and system for selecting packet network gateway with designated capability
CN103489108A (en) * 2013-08-22 2014-01-01 浙江工商大学 Large-scale order form matching method in community commerce cloud
CN104457133A (en) * 2014-11-28 2015-03-25 合肥华凌股份有限公司 Food managing method and food managing system
CN107203890A (en) * 2016-03-17 2017-09-26 阿里巴巴集团控股有限公司 Credential data distribution method, apparatus and system
CN107274284A (en) * 2016-04-07 2017-10-20 阿里巴巴集团控股有限公司 Bidirectinoally coupled method, device and transaction system
CN108154630A (en) * 2017-12-25 2018-06-12 衢州华睿工业设计有限公司 For the burglary-resisting installation of storage, terminal and method

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101938789A (en) * 2009-07-01 2011-01-05 中兴通讯股份有限公司 Method and system for selecting packet network gateway with designated capability
CN103489108A (en) * 2013-08-22 2014-01-01 浙江工商大学 Large-scale order form matching method in community commerce cloud
CN104457133A (en) * 2014-11-28 2015-03-25 合肥华凌股份有限公司 Food managing method and food managing system
CN107203890A (en) * 2016-03-17 2017-09-26 阿里巴巴集团控股有限公司 Credential data distribution method, apparatus and system
CN107274284A (en) * 2016-04-07 2017-10-20 阿里巴巴集团控股有限公司 Bidirectinoally coupled method, device and transaction system
CN108154630A (en) * 2017-12-25 2018-06-12 衢州华睿工业设计有限公司 For the burglary-resisting installation of storage, terminal and method

Also Published As

Publication number Publication date
CN109214884A (en) 2019-01-15

Similar Documents

Publication Publication Date Title
CN108829350B (en) Data migration method and device based on block chain
US10311230B2 (en) Anomaly detection in distributed ledger systems
US10999060B2 (en) Data processing method and apparatus
US9563426B1 (en) Partitioned key-value store with atomic memory operations
US20160260095A1 (en) Containerized Computational Task Execution Management Using a Secure Distributed Transaction Ledger
EP3565219B1 (en) Service execution method and device
US20160142369A1 (en) Service addressing in distributed environment
US10826980B2 (en) Command process load balancing system
CN108846749B (en) Partitioned transaction execution system and method based on block chain technology
WO2023179433A1 (en) Flow table storage method and apparatus, message forwarding method and apparatus, computer device, and medium
US20170052979A1 (en) Input/Output (IO) Request Processing Method and File Server
JP6975153B2 (en) Data storage service processing method and equipment
CN111737300A (en) Service processing method, device, equipment and computer readable storage medium
CN113220717A (en) Block chain-based data verification method and device and electronic equipment
CN113467970A (en) Cross-safe-area resource access method in cloud computing system and electronic equipment
WO2016101759A1 (en) Data routing method, data management device and distributed storage system
CN111694639A (en) Method and device for updating address of process container and electronic equipment
US9785724B2 (en) Secondary queue for index process
CN109214884B (en) Demand matching method and device and electronic equipment
WO2024021409A1 (en) Data retrieval method and device
CN110233843B (en) User request processing method and device
US10970341B2 (en) Predictive modeling in event processing systems for big data processing in cloud
US9256648B2 (en) Data handling in a cloud computing environment
US10067678B1 (en) Probabilistic eviction of partial aggregation results from constrained results storage
CN107016296B (en) Data index construction method, data index reading method, data index construction device, data reading device and electronic equipment

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
REG Reference to a national code

Ref country code: HK

Ref legal event code: DE

Ref document number: 40003195

Country of ref document: HK

TA01 Transfer of patent application right

Effective date of registration: 20200924

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Innovative advanced technology Co.,Ltd.

Address before: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant before: Advanced innovation technology Co.,Ltd.

Effective date of registration: 20200924

Address after: Cayman Enterprise Centre, 27 Hospital Road, George Town, Grand Cayman Islands

Applicant after: Advanced innovation technology Co.,Ltd.

Address before: A four-storey 847 mailbox in Grand Cayman Capital Building, British Cayman Islands

Applicant before: Alibaba Group Holding Ltd.

TA01 Transfer of patent application right
GR01 Patent grant
GR01 Patent grant