CN105160572A

CN105160572A - Device and method for controlling order to generate, and seckilling system

Info

Publication number: CN105160572A
Application number: CN201510642366.3A
Authority: CN
Inventors: 林泽通
Original assignee: Nubia Technology Co Ltd
Current assignee: Nubia Technology Co Ltd
Priority date: 2015-09-30
Filing date: 2015-09-30
Publication date: 2015-12-16

Abstract

The invention discloses a device for controlling an order to generate. The device comprises a seckilling information acquisition module, a seckilling request determining module, and a seckilling order generation module. The seckilling information acquisition module is used for acquiring related information in seckilling requests when receiving a plurality of seckilling requests which are sent from client sides and are forwarded by a front-end server. The related information at least comprises user information, seckilled commodity information and IP addresses of client sides. The seckilling request determining module is used for selecting and obtaining corresponding seckilling requests capable of generating seckilling orders from the plurality of seckilling requests randomly and/or at different times. The seckilling order generation module is used for generating corresponding seckilling orders according to related information in the determined seckilling requests. The invention also discloses a method for controlling the order to generate, and a seckilling system. Through adoption of the device and method for controlling the order to generate and the seckilling system, a maliciously ordering behavior can be prevented so as to eliminate impact of the maliciously ordering behavior on an E-commerce platform, the performance of an E-commerce platform system can be improved relatively, and the user shopping experience can be improved.

Description

Control device, the method for order generation and kill system second

Technical field

The present invention relates to e-commerce field, particularly relate to device, the method for control order generation and kill system second.

Background technology

Along with the development of mobile terminal and e-commerce technology, increasing user uses mobile terminal or computing machine to carry out shopping online, buy train ticket etc., under normal circumstances, existing electric business's platform is all can supporting user system resource overhead required when normally doing shopping, but in certain class in particular cases, the second that such as electric business releases kills advertising campaign or the Spring Festival buys train ticket etc., now at one time or to buy the user of same commodity in the same time period very many, now electric business's platform needs instantaneously to bear high concurrent and ensure that the commodity sold are super simultaneously and sell, but realistic situation is then electric business's platform be difficult to instantaneous bear high concurrent, trace it to its cause, prior art level on the one hand, the reasons such as the operating cost of electricity business platform, be then on the other hand the malice brush single file of user by being caused, such as ox party passes through to brush singly rushes to purchase train ticket.

In addition, by accelerating the technical research speed of software and hardware, strengthen the cost input etc. of electric business's platform simultaneously, and then inherently directly promote the high concurrent processing ability of electric business's platform, but this type of mode is very undesirable.Therefore, by the generation preventing malice brush single file from being, thus the high concurrent processing ability indirectly, relatively promoting electric business's platform then preferably and operability is stronger.

Summary of the invention

Fundamental purpose of the present invention is that providing a kind of controls device, the method for order generation and kill system second, is intended to solve the technical matters how realized the strick precaution that malice brush single file is.

For achieving the above object, a kind of device controlling order and generate provided by the invention, the device that described control order generates comprises:

Second kills data obtaining module, for when receive some seconds that client that front-end server forwards sends kill request time, obtain the relevant information of killing second in request, described relevant information at least comprises user profile, second kills merchandise news and client ip address;

Second kills request determination module, selects to obtain can generating accordingly to kill request the second of killing order second at random and/or at times for killing from described some seconds in request;

Second kills order generation module, for according to the described relevant information of killing determined second in request, generates and kills order corresponding second.

Preferably, the device that described control order generates also comprises: IP blacklist determination module, for according to preset IP blacklist strategy, determines that the second corresponding to client ip address writing IP blacklist kills request;

Wherein, described IP blacklist determination module comprises:

Access times increase unit, for being killed access times increase in request corresponding to client ip address received second once;

Access times judging unit, for judging that each received second kills the current accumulative access times that in request, client ip address is corresponding in default access duration and whether equal preset access times threshold value;

IP blacklist determining unit, for kill when each received second the current accumulative access times corresponding in default access duration of client ip address in request equal preset access times threshold value time, this second to be killed in the IP blacklist in the client ip address write caching server corresponding to request and return this second and kill the customer terminal webpage corresponding to request and refresh, wherein, the second that described IP blacklist sends for described front-end server interception relative client kills request.

Preferably, kill request determination module described second and comprise: submodule is determined in the request of killing in first second, obtain can generating accordingly kill request the second of killing order second for killing Stochastic choice in request from described some seconds;

Wherein, the request of killing in described first second determines that submodule comprises:

Random number generation unit, for carrying out label process to the received request of killing second and generating a random number range;

Kill request label judging unit second, for according to the random number range generated, judge that each received second kills the label of request whether within described random number range respectively;

Second kill solicited status judging unit, for kill request when second label within described random number range time, in the middle of judging whether request of killing this second is in and is processing;

Second kills request determining unit, when processing central for not being in when this request of killing second, determining that this request of killing second can generate and killing order second;

Page furbishing unit, when processing central for being in when this request of killing second, returning this second kills the customer terminal webpage corresponding to request and refreshes.

Preferably, kill request determination module described second and comprise: submodule is determined in the request of killing in second second, and the second for obtaining from Stochastic choice kills in request, select to obtain can generating accordingly at times to kill request the second of killing order second;

Wherein, the request of killing in described second second determines that submodule comprises:

Stock's acquiring unit, kills the current stock of commodity for obtaining Stochastic choice the second of killing corresponding to request second obtained;

Second kills request statistic unit, and for entering in duration default, whether the quantity of killing request second of adding up the processing stage of entering the bill of lading equals the current stock that the second of killing corresponding to request this second kills the preset ratio of commodity;

When described page furbishing unit also equals that this second, the second of killing corresponding to request killed the current stock of the preset ratio of commodity for: the quantity of killing request the second when entering the bill of lading processing stage, the processing stage of stopping entering the bill of lading, and refresh process is carried out to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

Preferably, the device that described control order generates also comprises:

, there is for judging whether the restrictive condition that preset second kills commodity purchasing quantity in the first judge module;

Second judge module, for when exist kill the restrictive condition of commodity purchasing quantity preset second time, before second kills order in generation, judge that whether request of killing second corresponding and meet described restrictive condition;

Described page furbishing unit also for: when the request of killing second is corresponding meet described restrictive condition time, returning this second kills the customer terminal webpage corresponding to request and refreshes.

Further, for achieving the above object, the present invention also provides a kind of method controlling order and generate, and the method that described control order generates comprises:

When receive some seconds that client that front-end server forwards sends kill request time, obtain the relevant information of killing second in request, described relevant information at least comprises user profile, second kills merchandise news and client ip address;

Kill request from described some seconds and select to obtain can generating accordingly to kill request the second of killing order second at random and/or at times;

According to the described relevant information of killing determined second in request, generate and kill order corresponding second.

Preferably, described to kill request at random from described some seconds and/or select at times to obtain can generating accordingly kill request the second of killing order second before comprise: according to preset IP blacklist strategy, determine that the second corresponding to client ip address writing IP blacklist kills request;

Wherein, according to preset IP blacklist strategy, determine that the request of the killing second corresponding to client ip address writing IP blacklist comprises further:

Is killed access times increase in request corresponding to client ip address received second once;

Judge that each received second kills the current accumulative access times that in request, client ip address is corresponding in default access duration and whether equal preset access times threshold value respectively;

If, then this second to be killed in the IP blacklist in the client ip address write caching server corresponding to request and return this second and kill the customer terminal webpage corresponding to request and refresh, wherein, the second that described IP blacklist sends for described front-end server interception relative client kills request.

Preferably, describedly kill Stochastic choice request from described some seconds and obtain generating the request of killing second of killing order second accordingly and comprise:

Label process is carried out to the received request of killing second and generates a random number range;

According to the random number range generated, judge that each received second kills the label of request whether within described random number range respectively;

If the label killing request second is within described random number range, then in the middle of judging whether request of killing this second is in and is processing;

When this request of killing second be not in process central time, determine that this request of killing second can generate and kill order second;

When this request of killing second be in process central time, returning this second kills the customer terminal webpage corresponding to request and refreshes.

Preferably, described when this request of killing second be not in process central time, determine this request of killing second can generate kill order second after comprise: kill request from the second that Stochastic choice obtains, select at times to obtain can generating accordingly and kill request the second of killing order second;

Wherein, kill request from the second that Stochastic choice obtains, select to obtain generating request of the killing second of killing order second accordingly at times and comprise further:

Obtain the current stock killing commodity the second of killing corresponding to request second that Stochastic choice obtains;

Enter in duration default, whether the quantity of killing request second of adding up the processing stage of entering the bill of lading equals the current stock that the second of killing corresponding to request this second kills the preset ratio of commodity;

If so, the processing stage of then stopping entering the bill of lading, and refresh process is carried out to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

Preferably, the described described relevant information according to killing determined second in request, generates before killing order corresponding second and comprises:

Judge whether to there is the restrictive condition that preset second kills commodity purchasing quantity;

If exist, then, before second kills order in generation, judge that whether request of killing second is corresponding and meet described restrictive condition;

If so, then returning this second kills the customer terminal webpage corresponding to request and refreshes.

Further, for achieving the above object, the present invention also provides kill system a kind of second, comprises some clients, some front-end servers, some back-end servers and some caching servers, and described back-end server comprises the device that the control order described in above-mentioned any one generates.

Preferably, described front-end server comprises:

The black name acquisition module of IP, for obtaining the IP blacklist that described caching server is preserved;

Second kills request receiving module, and the second sent for receiving described client kills request;

IP judge module, for receive second that described client sends kill request time, judging whether to exist in described IP blacklist this second kills client ip address in request;

Second killing request forward module, for when there is not the client ip address that this second kill in request in described IP blacklist, being killed request forward extremely described back-end server this second.

What present invention improves over that electric business's product panic buying in the past adopts is introduced into the strategy first obtained, by adopt random selection strategy and/or at times selection strategy kill request the second of killing order second to determine to select can generate accordingly, buy user by Stochastic choice and determine the purchase number of users that each period can enter, thus can prevent malice brush single user from occupying a large amount of queuing position and causing other users successfully cannot buy the generation of condition of merchandise to a certain extent, and then can take precautions against or reduce the generation that malice brush single file is to a certain extent.In addition, also can the IP address buying user be monitored further, thus interception has the user purchase request of malice buying behavior.Can be taken precautions against and the generation reducing malice brush single file and be by the present invention, thus relatively promote the high concurrency performance of electric business's platform, also improve the experience of user simultaneously.

Accompanying drawing explanation

Fig. 1 is the high-level schematic functional block diagram that the present invention controls device first embodiment that order generates;

Fig. 2 is the basic function structural representation of system of killing existing second;

Fig. 3 is the high-level schematic functional block diagram that the present invention controls device second embodiment that order generates;

Fig. 4 is the refinement high-level schematic functional block diagram of IP blacklist determination module one embodiment in Fig. 3

Fig. 5 be in Fig. 1 second the refinement high-level schematic functional block diagram of killing request determination module one embodiment;

Fig. 6 is the refinement high-level schematic functional block diagram that submodule one embodiment is determined in the request of killing in Fig. 5 first second;

Fig. 7 be in Fig. 1 second the refinement high-level schematic functional block diagram of killing request determination module another embodiment;

Fig. 8 is the refinement high-level schematic functional block diagram that submodule one embodiment is determined in the request of killing in Fig. 7 second second;

Fig. 9 is the high-level schematic functional block diagram that the present invention controls device the 3rd embodiment that order generates;

Figure 10 is the schematic flow sheet that the present invention controls method first embodiment that order generates;

Figure 11 is the schematic flow sheet that the present invention controls method second embodiment that order generates;

Figure 12 is the refinement schematic flow sheet of step S210 in Figure 11

Figure 13 is the refinement schematic flow sheet of step S20 mono-embodiment in Figure 10;

Figure 14 is the refinement schematic flow sheet of another embodiment of step S20 in Figure 10;

Figure 15 is the schematic flow sheet that the present invention controls method the 3rd embodiment that order generates;

Figure 16 is the high-level schematic functional block diagram of killing system one embodiment second of the present invention;

Figure 17 is the refinement high-level schematic functional block diagram of front-end server in Figure 16.

The realization of the object of the invention, functional characteristics and advantage will in conjunction with the embodiments, are described further with reference to accompanying drawing.

Embodiment

Should be appreciated that specific embodiment described herein only in order to explain the present invention, be not intended to limit the present invention.

Reference Fig. 1, Fig. 1 are the high-level schematic functional block diagram that the present invention controls device first embodiment that order generates.In the present embodiment, the device that described control order generates comprises:

Second kills data obtaining module 10, for when receive some seconds that client that front-end server forwards sends kill request time, obtain the relevant information of killing second in request, described relevant information at least comprises user profile, second kills merchandise news and client ip address;

Kill the basic function structural representation of system second as shown in Figure 2.User is sent by client (mobile terminal, computing machine etc.) forward end server and kills request second, wherein, in view of the visit capacity that electric business's platform (comprise and kill system second) is higher, for promoting the high concurrent processing ability of electric business's platform, the service end of correspondence is set to the secondary echelon process structure of the front-end server of the first level and the back-end server of the second level; Wherein, front-end server is intended for all clients, and the multiple seconds sent in order to receive all clients kill request, and is killed Requests routing multiple second on different multiple back-end servers.

Such as, adopt load-balanced server (load-balancingserver, LBS) load distribution is carried out, all first the request of killing second of client arrives load-balanced server, then killed the state of the back-end server of request second according to each actual treatment by load-balanced server, by second, request of killing specifically is assigned in the back-end server of certain actual treatment, and the domain name of external disclosure and IP address are all this load-balanced servers.In addition, load-balanced server generally only does loadbalancing tasks and distributes, but is not actual in the network server that second, the request of killing processed.By in the back-end server that performed to reality by multiple services request equilibrium assignment, thus ensure the concurrent response speed of height of whole system.

Kill some seconds that client that data obtaining module 10 receiving front-end server forwards sends second and kill request, and kill request the IP address etc. of resolving and obtaining as the account (user ID) of user, user basic information (name, phone, ship-to), trade name, quantity purchase and client from second.

Killing request determination module 20 second, selecting to obtain can generating accordingly to kill request the second of killing order second at random and/or at times for killing from described some seconds in request;

In view of killing movable processing feature second, being such as introduced into and just first obtaining, seeming a kind of panic buying strategy of justice, reality is but easy to single by malice brush thus makes brush single user can obtain more commodity sales promotion or other interests; And in view of the brush list feature of malice brush single user, such as concentrate on and use multiple stage client or multiple account to carry out brush singly sometime.Therefore, in the present embodiment, kill request determination module 20 second buy the strategy of user by adopting Stochastic choice and/or adopt time segment, thus select to determine the user that can buy promotional product, also namely determine to select can generate accordingly to kill request the second of killing order second.Stochastic choice user and time segment select the methods of user all a lot of in addition, are not limited in the present embodiment.Such as, determine that any 500 users in 1000 users being introduced into can obtain purchasing opportunities at random; Or randomly draw 500 users at every turn and obtain purchasing opportunities etc.Again such as, the number of users that can enter the processing stage that order being submitted to is limited in per second or every 500 milliseconds.Random selection strategy in the present invention and selection strategy at times seem and violate the basic of First come first served and rush to purchase rule, but reality is from the overall fairness of the activity of killing second, and the present invention also further improves the fairness of the activity of killing second.The competition of First come first served is mainly reflected in the competition on hardware resource, such as network speed, panic buying equipment (computing power) etc., and the hardware resource of vast domestic consumer is relative to the hardware resource of malice brush single user, performance wants much inferior, therefore, based on this, the basic panic buying rule of First come first served is not very fair for most of domestic consumer.

The random selection strategy adopted in the present embodiment and at times selection strategy can be from the brush single file of preventing malice brush single user actual techniques level not only, simultaneously, owing to changing the basic panic buying rule of existing First come first served, therefore, even if user can be allowed to feel, and being discharged to first also not necessarily can obtain purchasing opportunities, thus correspondingly the generation occurring same time height complications is avoided, thus can from the concurrent processing ability changing user's panic buying behavior and relatively promote electric business's platform.

Second kills order generation module 30, for according to the described relevant information of killing determined second in request, generates and kills order corresponding second.

In the present embodiment, kill after request determination module 20 determines and can generate and kill request the second of killing order second in second, second kills order generation module 30 by according to the user profile of killing second received by data obtaining module 10, second killing merchandise news and client ip address etc., generates and kills order corresponding second.

It should be noted that, the brush list described in the present embodiment specifically refers to kill second in activity and to the brush single file of the concurrent processing ability generation restricted influence of electric business's platform is.The visit capacity that this type of malice brush single file is is very huge, thus needs to carry out stricks precaution process to it, but general all can only strick precaution it the to a certain extent and generation that brush single file is can not be stopped completely.

What the present embodiment improved that electric business's product panic buying in the past adopts is introduced into the strategy first obtained, by adopt random selection strategy and/or at times selection strategy kill request the second of killing order second to determine to select can generate accordingly, buy user by Stochastic choice and determine the purchase number of users that each period can enter, thus can prevent malice brush single user from occupying a large amount of queuing position and causing other users successfully cannot buy the generation of condition of merchandise to a certain extent, and then can take precautions against or reduce the generation that malice brush single file is to a certain extent, thus relatively promote the high concurrency performance of electric business's platform, also improve the experience of user simultaneously.

Reference Fig. 3, Fig. 3 are the high-level schematic functional block diagram that the present invention controls device second embodiment that order generates.In the present embodiment, the device that described control order generates also comprises:

IP blacklist determination module 40, for according to preset IP blacklist strategy, determines that the second corresponding to client ip address writing IP blacklist kills request;

In the present embodiment, the client ip address used in view of usual malice brush single user is all more concentrated, also namely on a few IP address, list is brushed by logging in more register account number to carry out malice, namely also malice brushes that to kill second that single client sends the IP address that request is carried all identical, therefore, can be judged to be that brush single file is.Therefore, the present embodiment is locked by IP address and stops the generation that malice brush single file is.

Comprise with reference to Fig. 4, IP blacklist determination module 40:

Access times increase unit 401, for being killed access times increase in request corresponding to client ip address received second once;

For the locking of the IP address corresponding to the request of killing improper second (malice brushes list), counting mode in the present embodiment, is adopted to lock.When receive kill request second time, increase the unit 401 IP address corresponding to the request of killing the second received by access times and carry out counting preservation.When next time receive the request of killing new second again and the IP address of its correspondence has been recorded preservation time, increase unit 401 again to the counting increase of the access times of this identical IP address once by access times.

Access times judging unit 402, for judging that each received second kills the current accumulative access times that in request, client ip address is corresponding in default access duration and whether equal preset access times threshold value;

When normally doing shopping, the access times of the request of killing second corresponding in Preset Time can not exceed certain limit, more than 10 times, if reach this normal level, then can not can think that the request of killing this second is that malice brushes list in such as 1 second.

Therefore, after receiving and killing request new second, access times judging unit 402 judges in default access duration, whether the accumulative access times that this second kills the IP address of request current have reached preset access times threshold value, if reach, then illustrate that this second corresponding to IP address of the request of killing brushes list for malice.

IP blacklist determining unit 403, for kill when each received second the current accumulative access times corresponding in default access duration of client ip address in request equal preset access times threshold value time, this second to be killed in the IP blacklist in the client ip address write caching server corresponding to request and return this second and kill the customer terminal webpage corresponding to request and refresh, wherein, the second that described IP blacklist sends for described front-end server interception relative client kills request.

When access times judging unit 402 judge and the request of killing the second determining corresponding to current IP address exist malice brush single problem time, IP blacklist determining unit 403 determines that this IP address needs locked follow-uply to be tackled by front-end server when visiting again, also namely by IP blacklist determining unit 403, this IP address is write in the IP blacklist in caching server, return this second kills the customer terminal webpage corresponding to request and refreshes this customer terminal webpage simultaneously, wherein, refresh page operation can be used as a kind of feedback system to malice brush single user, certainly the operation returning client is also not limited to refresh operation.

It should be noted that in addition, existing second caching server kill in system, for a kind of server for storing public resource keeping high concurrent processing ability to arrange, so that fast processing stores, searches, obtains public resource, also system of namely killing second adopts a kind of distributed Servers installed mode, thus reduces the impact of high concurrent process on back-end server performance.

In the present embodiment, the IP address of request is killed to add up the access times of this IP address by monitoring each second, thus kill request in order to the second that locking exists malice brush single, and upper once receive kill request new second time, the second of the IP address (being namely present in the IP address in IP blacklist) that interception is locked kills request.Tackled with request by the IP address locking of the present embodiment, the generation of most malice brush one-states can be taken precautions against, but if desired promote the strick precaution effect of malice being brushed to single problem further, the Precaution Tactics adopting other can be combined again, specifically arrange according to actual needs.

With reference to Fig. 5, Fig. 5 be in Fig. 1 second the refinement high-level schematic functional block diagram of killing request determination module one embodiment.In the present embodiment, kill request determination module 20 described second and comprise:

Submodule 201 is determined in the request of killing in first second, obtains can generating accordingly kill request the second of killing order second for killing Stochastic choice in request from described some seconds;

As shown in Figure 6, the request of killing in described first second determines that submodule 201 comprises:

Random number generation unit 2011, for carrying out label process to the received request of killing second and generating a random number range;

In the present embodiment, in view of the advanced person that existing second, the mode of killing adopted first obtains mode, also namely submit to request of killing second more early more can rob to buy second and kill commodity, but which is easily maliciously brushed list, therefore, in the present embodiment, determine that the second that can submit to kills request by adopting the mode of random number, thus weaken to a certain extent existing advanced person first panic buying rule, avoid user for contention " first " and at one time in submit the request of killing second to or uninterrupted submit to kill request the second repeated, thus cause the concurrent processing ability of electric business's platform sharply to decline.

In the present embodiment, by random number generation unit 2011 label process carried out to the received request of killing second and generate a random number range.Such as, often receive to kill a second and ask random number generation unit 2011 just to carry out label to it, such as label is 001-1000, and the random number range of generation is 100-500.It should be noted that, the random number range of generation needs to keep occuring simultaneously with label.

Kill request label judging unit 2012 second, for according to the random number range generated, judge that each received second kills the label of request whether within described random number range respectively;

In the present embodiment, the label request of the killing second within random number range is defined as carrying out order and submits to kill request the second of process, also namely can generate and kill request the second of killing order second.Due to employing is that random number is determined, therefore, is likely again defined as carrying out order and submits to kill request the second of process, therefore, need again to carry out secondary judgement to this type of situation.

Second kill solicited status judging unit 2013, for kill request when second label within described random number range time, in the middle of judging whether request of killing this second is in and is processing;

Kill request determining unit 2014 second, when processing central for not being in when this request of killing second, determining that this request of killing second can generate and killing order second;

Page furbishing unit 2015, when processing central for being in when this request of killing second, returning this second kills the customer terminal webpage corresponding to request and refreshes.

When second kill label that request label judging unit 2012 judges to kill request received second within random number range time, repeat for avoiding generation to submit, therefore by killing second in the middle of solicited status judging unit 2013 judges whether request of killing this second is in and is processing; When determine this request of killing second be not in process central time, kill request determining unit 2014 second and determine that this request of killing second can generate and kill order second; And if this request of killing second is in when processing central, then returns this second by page furbishing unit 2015 and kill the customer terminal webpage corresponding to request and refresh this customer terminal webpage.

The random selection strategy adopted in the present embodiment can be from the brush single file of preventing malice brush single user actual techniques level not only, simultaneously, owing to changing the basic panic buying rule of existing First come first served, therefore, even if user can be allowed to feel, and being discharged to first also not necessarily can obtain purchasing opportunities, thus correspondingly the generation occurring same time height complications is avoided, thus can from the concurrent processing ability changing user's panic buying behavior and relatively promote electric business's platform.

With reference to Fig. 7, Fig. 7 be in Fig. 1 second the refinement high-level schematic functional block diagram of killing request determination module another embodiment.In the present embodiment, kill request determination module 20 described second and comprise:

Submodule 202 is determined in the request of killing in second second, and the second for obtaining from Stochastic choice kills in request, selects to obtain can generating accordingly at times to kill request the second of killing order second;

It is very huge that the maximum feature of malice brush list is exactly the quantity placed an order, and enter except line-locked mode except by IP address, electric business's platform is generally difficult to distinguish with normal order request.Therefore, for the request of killing second single to malice brush is further taken precautions against, adopt selection strategy at times in the present embodiment, the second entering order presentation stage by controlling each period kills the quantity of request, relatively to reduce the generation of the quantity on order situation of the malice brush list be successfully committed.

As shown in Figure 8, the request of killing in described second second determines that submodule 202 comprises:

Stock's acquiring unit 2021, kills the current stock of commodity for obtaining Stochastic choice the second of killing corresponding to request second obtained;

In the present embodiment, killing a movable principal character second is exactly kill commodity second can not surpass and sell, and the quantity of the order application also namely submitted to can not exceed current commodity stocks number.Therefore, by stock's acquiring unit 2021 to obtain the current stock killing commodity second, also namely corresponding when to kill request determined second according to random selection strategy stockpile number.

Kill request statistic unit 2022 second, for entering in duration default, whether the quantity of killing request second of adding up the processing stage of entering the bill of lading equals the current stock that the second of killing corresponding to request this second kills the preset ratio of commodity;

Based on the consideration of electric business's platform processes efficiency and user's experience, the preset ratio entering duration and current stock processing stage of entering the bill of lading is preset in the present embodiment, the setting entering the concrete numerical value of duration and stock's ratio is not limit, and specifically arranges according to actual conditions.Such as, the duration arranged the processing stage of entering the bill of lading is 1 second, and be arranged on this to enter in duration allow kill the second of carrying out order submission number of requests is current stock 50%, also even current stock is 1000, then within the bill of lading time of 1 second, only allow the request of killing 500 seconds to generate submit order to.

When described page furbishing unit 2015 also equals that this second, the second of killing corresponding to request killed the current stock of the preset ratio of commodity for: the quantity of killing request the second when entering the bill of lading processing stage, the processing stage of stopping entering the bill of lading, and refresh process is carried out to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

When second kill that request statistic unit 2022 adds up enter the bill of lading processing stage the quantity of killing request second equal that this second, the second of killing corresponding to request killed the current stock of the preset ratio of commodity time, stop the order processing processing stage of entering the bill of lading, and by page furbishing unit 2015, refresh process is carried out to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

In the present embodiment, order is submitted to processing stage, need the relevant information of being killed second in request, such as user ID (account), merchandise news, client ip address etc. are written in caching server so that corresponding second is killed order in follow-up generation.Therefore, by arranging the expired duration of IP address, thus the second that corresponding control enters the bill of lading stage kills number of request, but the present embodiment is not limited to aforesaid way.Adopt selection strategy at times not only can reduce the single success ratio of malice brush in the present embodiment, meanwhile, also can the concurrent processing performance of the electric business's platform of corresponding lifting, thus improve user's experience.

Reference Fig. 9, Fig. 9 are the high-level schematic functional block diagram that the present invention controls device the 3rd embodiment that order generates.In the present embodiment, the device that described control order generates also comprises:

, there is for judging whether the restrictive condition that preset second kills commodity purchasing quantity in the first judge module 50;

For limiting same user further being killed to the quantity purchase of commodity same second, in the present embodiment, the restrictive condition killing commodity purchasing quantity second can be pre-set further, but specifically whether arrange and determine according to actual needs.Meanwhile, before second kills order in generation, need by the first judge module 50 to judge to determine whether there is default restrictive condition.

Second judge module 60, for when exist kill the restrictive condition of commodity purchasing quantity preset second time, before second kills order in generation, judge that whether request of killing second corresponding and meet described restrictive condition;

When the first judge module 50 judges to determine that there is preset second kills the restrictive condition of commodity purchasing quantity, judge to kill this second whether request is corresponding meets this restrictive condition further by the second judge module 60.Such as, limiting same user to the quantity purchase killing commodity same second is 5, and if current same user have purchased 3 or prepare purchase 3, then still can continue to kill second and buy these commodity.

Described page furbishing unit 2015 also for: when the request of killing second is corresponding meet described restrictive condition time, returning this second kills the customer terminal webpage corresponding to request and refreshes.

When the second judge module 60 judges that the request of killing this second meets preset restrictive condition, namely also when user has reached the quantity purchase of setting, then return this second by page furbishing unit 2015 and kill the customer terminal webpage corresponding to request and refresh this customer terminal webpage.

Further contemplate in the present embodiment and the restricted number of killing commodity second has been bought to user, because quantity purchase is limited, thus also can the generation of preventing malice brush one-state to a certain extent, thus relatively promote the concurrent processing performance of electric business's platform, also improve user's experience simultaneously.

Reference Figure 10, Figure 10 are the schematic flow sheet that the present invention controls method first embodiment that order generates.In the present embodiment, the method that described control order generates comprises:

Step S10, when receive some seconds that client that front-end server forwards sends kill request time, obtain the relevant information of killing second in request, described relevant information at least comprises user profile, second kills merchandise news and client ip address;

In the present embodiment, user is sent by client (mobile terminal, computing machine etc.) forward end server and kills request second, wherein, in view of the visit capacity that electric business's platform (comprise and kill system second) is higher, for promoting the high concurrent processing ability of electric business's platform, the service end of correspondence is set to the secondary echelon process structure of the front-end server of the first level and the back-end server of the second level; Wherein, front-end server is intended for all clients, and the multiple seconds sent in order to receive all clients kill request, and is killed Requests routing multiple second on different multiple back-end servers, as shown in Figure 4.

Some seconds that the client forwarded when receiving front-end server sends kill request, kill request the IP address etc. of resolving and obtaining as the account (user ID) of user, user basic information (name, phone, ship-to), trade name, quantity purchase and client from second.

Step S20, kills request from described some seconds and selects to obtain can generating accordingly to kill request the second of killing order second at random and/or at times;

In view of killing movable processing feature second, being such as introduced into and just first obtaining, seeming a kind of panic buying strategy of justice, reality is but easy to single by malice brush thus makes brush single user can obtain more commodity sales promotion or other interests; And in view of the brush list feature of malice brush single user, such as concentrate on and use multiple stage client or multiple account to carry out brush singly sometime.Therefore, in the present embodiment, by adopting Stochastic choice buy the strategy of user and/or adopt time segment, thus selecting to determine the user that can buy promotional product, also namely determining to select can generate accordingly to kill request the second of killing order second.Stochastic choice user and time segment select the methods of user all a lot of in addition, are not limited in the present embodiment.

Random selection strategy in the present embodiment and selection strategy at times seem and violate the basic of First come first served and rush to purchase rule, but reality is from the overall fairness of the activity of killing second, and the present invention also further improves the fairness of the activity of killing second.The competition of First come first served is mainly reflected in the competition on hardware resource, such as network speed, panic buying equipment (computing power) etc., and the hardware resource of vast domestic consumer is relative to the hardware resource of malice brush single user, performance wants much inferior, therefore, based on this, the basic panic buying rule of First come first served is not very fair for most of domestic consumer.

Step S30, according to the described relevant information of killing determined second in request, generates and kills order corresponding second.

In the present embodiment, after determining and can generating and kill request the second of killing order second, by according to received user profile, second killing merchandise news and client ip address etc., generating and killing order corresponding second.

Reference Figure 11, Figure 11 are the schematic flow sheet that the present invention controls method second embodiment that order generates.Based on above-described embodiment, in the present embodiment, comprised before above-mentioned steps S20:

Step S210, according to preset IP blacklist strategy, determines that the second corresponding to client ip address writing IP blacklist kills request;

With reference to the refinement schematic flow sheet that Figure 12, Figure 12 are step S210 in Figure 11.In the present embodiment, step S210 comprises further:

Step S2101, kills access times increase in request corresponding to client ip address once by received second;

For the locking of the IP address corresponding to the request of killing improper second (malice brushes list), counting mode in the present embodiment, is adopted to lock.When receive kill request second time, carry out counting preservation by the IP address that the request of killing the second received is corresponding.When next time receive the request of killing new second again and the IP address of its correspondence has been recorded preservation time, then to the counting increase of the access times of this identical IP address once.

Step S2102, judges that each received second kills the current accumulative access times that in request, client ip address is corresponding in default access duration and whether equal preset access times threshold value respectively;

Therefore, after receiving and killing request new second, judge in default access duration, whether the accumulative access times that this second kills the IP address of request current have reached preset access times threshold value, if reach, then illustrate that this second corresponding to IP address of the request of killing brushes list for malice.

Step S2103, if, then this second to be killed in the IP blacklist in the client ip address write caching server corresponding to request and return this second and kill the customer terminal webpage corresponding to request and refresh, wherein, the second that described IP blacklist sends for described front-end server interception relative client kills request.

Step S2104, if not, performs next step.

When judge and the request of killing the second determining corresponding to current IP address exist malice brush single problem time, determine that this IP address needs locked follow-uply to be tackled by front-end server when visiting again, also by the IP blacklist in this IP address write caching server, return this second kills the customer terminal webpage corresponding to request and refreshes this customer terminal webpage simultaneously, wherein, refresh page operation can be used as a kind of feedback system to malice brush single user, and the operation certainly returning client is also not limited to refresh operation.

With reference to the refinement schematic flow sheet that Figure 13, Figure 13 are step S20 mono-embodiment in Figure 10.Based on above-described embodiment, in the present embodiment, above-mentioned steps S20: kill Stochastic choice request from described some seconds and obtain generating request of the killing second of killing order second accordingly and comprise further:

Step S201, carries out label process to the received request of killing second and generates a random number range;

In the present embodiment, by carrying out label process to the received request of killing second and generating a random number range.Such as, often receive the request of killing a second and just carry out label to it, such as label is 001-1000, and the random number range of generation is 100-500.It should be noted that, the random number range of generation needs to keep occuring simultaneously with label.

Step S202, according to the random number range generated, judges that each received second kills the label of request whether within described random number range respectively;

Step S203, if the label killing request second is within described random number range, then in the middle of judging whether request of killing this second is in and is processing;

Step S204, when this request of killing second be not in process central time, determine that this request of killing second can generate and kill order second;

Step S205, when this request of killing second be in process central time, returning this second kills the customer terminal webpage corresponding to request and refreshes.

When the label killing request second received by judging is within random number range, repeat for avoiding generation to submit, in the middle of therefore judging whether request of killing this second is in and is processing; When determine this request of killing second be not in process central time, determine that this request of killing second can generate and kill order second; And if this request of killing second is in when processing central, then returning this second kills the customer terminal webpage corresponding to request and refreshes this customer terminal webpage.

With reference to the refinement schematic flow sheet that Figure 14, Figure 14 are another embodiment of step S20 in Figure 10.Based on above-described embodiment, in the present embodiment, after above-mentioned steps S204, above-mentioned steps S20: kill request from the second that Stochastic choice obtains, selects to obtain generating request of the killing second of killing order second accordingly at times and comprises further:

Step S206, obtains the current stock killing commodity the second of killing corresponding to request second that Stochastic choice obtains;

In the present embodiment, killing a movable principal character second is exactly kill commodity second can not surpass and sell, and the quantity of the order application also namely submitted to can not exceed current commodity stocks number.Therefore, obtain and kill the current stock of commodity second, also namely corresponding when to kill request determined second according to random selection strategy stockpile number.

Step S207, enters in duration default, and whether the quantity of killing request second of adding up the processing stage of entering the bill of lading equals the current stock that the second of killing corresponding to request this second kills the preset ratio of commodity;

Step S208, the processing stage of if so, then stopping entering the bill of lading, and carries out refresh process to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

When add up enter the bill of lading processing stage the quantity of killing request second equal that this second, the second of killing corresponding to request killed the current stock of the preset ratio of commodity time, stop the order processing processing stage of entering the bill of lading, and refresh process is carried out to the customer terminal webpage that the second processing stage of not entering the bill of lading kills corresponding to request.

Reference Figure 15, Figure 15 are the schematic flow sheet that the present invention controls method the 3rd embodiment that order generates.Based on above-described embodiment, in the present embodiment, comprise before above-mentioned steps S30:

Step S40, judges whether to there is the restrictive condition that preset second kills commodity purchasing quantity;

For limiting same user further being killed to the quantity purchase of commodity same second, in the present embodiment, the restrictive condition killing commodity purchasing quantity second can be pre-set further, but specifically whether arrange and determine according to actual needs.Meanwhile, before second kills order in generation, need to judge to determine whether there is default restrictive condition.

Step S50, if exist, then, before second kills order in generation, judges that whether request of killing second is corresponding and meets described restrictive condition;

When judging to determine that there is preset second kills the restrictive condition of commodity purchasing quantity, judge further to kill this second whether request is corresponding meets this restrictive condition.Such as, limiting same user to the quantity purchase killing commodity same second is 5, and if current same user have purchased 3 or prepare purchase 3, then still can continue to kill second and buy these commodity.

Step S60, if so, then returning this second kills the customer terminal webpage corresponding to request and refreshes;

Step S70, if not, performs next step.

When judging to kill this second request and meeting preset restrictive condition, when also namely user has reached the quantity purchase of setting, then returning this second kills the customer terminal webpage corresponding to request and refreshes this customer terminal webpage.

Reference Figure 16, Figure 16 are the high-level schematic functional block diagram of killing system second of the present invention.In the present embodiment, second, the system of killing comprised some clients 510, some front-end servers 520, some back-end servers 530 and some caching servers 540, and wherein, back-end server 530 comprises the device 5301 controlling order and generate.

In the present embodiment, user, by the browser application in client 510, kills the panic buying page second logged on electric business's platform (service end), and submits to kill request second to electric business's platform.Existing electric business's platform is the process better realized high concurrent data, the distributed multistage server structure of usual employing, also namely electric business's platform at least comprises front-end server 520, back-end server 530 and caching server 540, wherein, the second that front-end server 520 is submitted to specifically for reception client 510 kills request, and is distributed to back-end server 530 after carrying out rough handling; Caching server 540, specifically for storing public resource, has influence on the overall concurrency performance of system of killing second to avoid repetition to obtain from database.Such as, the data resource needed first can obtain from database, follow-up, can directly obtain from caching server.

Such as, front-end server 520 can adopt load-balanced server (load-balancingserver, LBS) load distribution is carried out, all first the request of killing second of client 510 arrives load-balanced server, then killed the state of the back-end server 530 of request second according to each actual treatment by load-balanced server, request of being killed second is specifically assigned in the back-end server 530 of certain actual treatment, and the domain name of external disclosure and IP address are all this load-balanced servers.In addition, load-balanced server generally only does loadbalancing tasks and distributes, but is not actual in the network server that second, the request of killing processed.By in the back-end server that performed to reality by multiple services request equilibrium assignment, thus ensure the concurrent response speed of height of whole system.Wherein, for the high concurrent processing ability of proof load equalization server, preferably adopt Nginx as Reverse Proxy in the present embodiment, to kill Requests routing the second of the client received 510 being submitted to back-end server 530, thus ensure the overall concurrency performance killing system second.

In addition, for ensureing the overall concurrency performance of electric business's platform further, caching server 540 adopts Redis storage system (key-value structure) to carry out the storage of data.Such as using the IP address of client as Key value, and user ID (account) and the merchandise news value value as this Key to be written in caching server 540.

Back-end server 530 by the device 5301 that controls order and generate with to the brush single file that may exist for taking precautions against, by limiting or reducing the process of brush being killed to request for single second, thus minimizing brush single file is the resource consumption to killing system second, improve the high concurrent processing ability of system of killing second, and reduce the impact that brush single file is the fairness on the activity of killing second, and then promote the purchase experiences of user.

With reference to the refinement high-level schematic functional block diagram that Figure 17, Figure 17 are front-end server in Figure 16.In the present embodiment, described front-end server 520 comprises:

The black name acquisition module 5201 of IP, for obtaining the IP blacklist that described caching server is preserved;

Second kills request receiving module 5202, and the second sent for receiving described client kills request;

IP judge module 5203, for receive second that described client sends kill request time, judging whether to exist in described IP blacklist this second kills client ip address in request;

Second killing request forward module 5204, for when there is not the client ip address that this second kill in request in described IP blacklist, being killed request forward extremely described back-end server this second.

For the locking of the IP address corresponding to the request of killing improper second (malice brushes list), counting mode in the present embodiment, is adopted to lock.When back-end server 530 receive kill request second time, counting preservation is carried out in the IP address that back-end server 530 is corresponding to the request of killing the second received.When next time receive the request of killing new second again and the IP address of its correspondence has been recorded preservation time, then to the counting increase of the access times of this identical IP address once.

When normally doing shopping, the access times of the request of killing second corresponding in Preset Time can not exceed certain limit, more than 10 times, if reach this normal level, then can not can think that the request of killing this second is that malice brushes list in such as 1 second.Therefore, back-end server 530 is new second after receiving and killing request, first judge in default access duration, whether the accumulative access times that this second kills the IP address of request current have reached preset access times threshold value, if reach, then illustrate that this second corresponding to IP address of the request of killing brushes list for malice.Back-end server 530 by this IP address write caching server 540 in IP blacklist in case follow-up visit again time tackled by front-end server 520.

First front-end server 520 obtains by the black name acquisition module 5201 of IP the IP blacklist that caching server 540 is preserved.Meanwhile, receive kill request the second that family end 510 submits to by killing request receiving module 5202 second.Then, judge whether to exist in IP blacklist this second by IP judge module 5203 and kill client ip address in request; If do not exist, then by killing request forward module 5204 second, is killed request forward this second to back-end server 530.And if exist, then return this place, IP address client 510, and refresh process carried out to the page of this client 510.

These are only the preferred embodiments of the present invention; not thereby the scope of the claims of the present invention is limited; every utilize instructions of the present invention and accompanying drawing content to do equivalent structure or equivalent flow process conversion; or be directly or indirectly used in other relevant technical fields, be all in like manner included in scope of patent protection of the present invention.

Claims

1. control the device that order generates, it is characterized in that, the device that described control order generates comprises:

2. the device controlling order and generate as claimed in claim 1, it is characterized in that, the device that described control order generates also comprises: IP blacklist determination module, for according to preset IP blacklist strategy, determines that the second corresponding to client ip address writing IP blacklist kills request;

Wherein, described IP blacklist determination module comprises:

3. the device controlling order and generate as claimed in claim 1 or 2, it is characterized in that, kill request determination module described second to comprise: submodule is determined in the request of killing in first second, obtain can generating accordingly kill request the second of killing order second for killing Stochastic choice in request from described some seconds;

4. the device controlling order and generate as claimed in claim 3, it is characterized in that, killing request determination module described second to comprise: submodule is determined in the request of killing in second second, and the second for obtaining from Stochastic choice kills in request, selecting to obtain can generating accordingly at times to kill request the second of killing order second;

5. the device controlling order and generate as claimed in claim 4, it is characterized in that, the device that described control order generates also comprises:

6. control the method that order generates, it is characterized in that, the method that described control order generates comprises:

7. the method controlling order and generate as claimed in claim 6, it is characterized in that, described to kill request at random from described some seconds and/or select at times to obtain can generating accordingly kill request the second of killing order second before comprise: according to preset IP blacklist strategy, determine that the second corresponding to client ip address writing IP blacklist kills request;

8. the method that generates of control order as claimed in claims 6 or 7, is characterized in that, describedly kills Stochastic choice request from described some seconds and obtains generating the request of killing second of killing order second accordingly and comprise:

9. the method controlling order and generate as claimed in claim 8, it is characterized in that, described when this request of killing second be not in process central time, determine this request of killing second can generate kill order second after comprise: kill request from the second that Stochastic choice obtains, select at times to obtain can generating accordingly and kill request the second of killing order second;

10. the method controlling order and generate as claimed in claim 9, is characterized in that the described described relevant information according to killing determined second in request generates before killing order corresponding second and comprises:

11. 1 kinds of seconds kill system, comprise some clients, some front-end servers, some back-end servers and some caching servers, it is characterized in that, described back-end server comprises the device that the control order according to any one of claim 1-5 generates.

12. seconds as claimed in claim 11 killed system, and it is characterized in that, described front-end server comprises: