CN107135321A - A kind of queuing strategy and system based on redis - Google Patents
A kind of queuing strategy and system based on redis Download PDFInfo
- Publication number
- CN107135321A CN107135321A CN201710391652.6A CN201710391652A CN107135321A CN 107135321 A CN107135321 A CN 107135321A CN 201710391652 A CN201710391652 A CN 201710391652A CN 107135321 A CN107135321 A CN 107135321A
- Authority
- CN
- China
- Prior art keywords
- service
- online
- list
- customer service
- same day
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
- H04M3/5232—Call distribution algorithms
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04M—TELEPHONIC COMMUNICATION
- H04M3/00—Automatic or semi-automatic exchanges
- H04M3/42—Systems providing special services or facilities to subscribers
- H04M3/50—Centralised arrangements for answering calls; Centralised arrangements for recording messages for absent or busy subscribers ; Centralised arrangements for recording messages
- H04M3/51—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing
- H04M3/523—Centralised call answering arrangements requiring operator intervention, e.g. call or contact centers for telemarketing with call distribution or queueing
- H04M3/5232—Call distribution algorithms
- H04M3/5234—Uniform load distribution
Abstract
The present invention relates to a kind of queuing strategy based on redis and system.Methods described comprises the following steps：Receive visitor's session request, generation request ID, the insertion request ID in queuing list；Acquisition once services customer service list, the current service session list of all customer sides and same day service conversation list；All online customer service ID are obtained, it is determined that once servicing customer service list, the online current service session list at all online customer service ends and the service conversation list of the online same day online；A request ID is taken out, serviced weight, online once service customer service list, online current service session list and the service conversation list of the online same day according to once service weight, current service weight, the same day determines matching customer side for request ID.The present invention realizes the ability and stability of lifting business processing, balanced each customer service workload.
Description
Technical field
The invention belongs to communication technical field, more particularly to a kind of queuing strategy and system based on redis.
Background technology
In online customer service system, most crucial business also has the row to visitor's session request in addition to instant messaging communication
Team's business, traditional queuing service to visitor's session request is the internal memory that queuing service program is deployed in individual server
In, and information corresponding with visitor's session request is stored in internal memory, when internal memory is in individual server effectively, in internal memory
Queuing service program is not shared and indivisible, visitor's session request could be ranked when information is in internal memory, it is impossible to enter
Row distributed deployment；When visitor's session request amount increase, the disposal ability of individual server is low, and user experience is poor；It is single
Server delay machine when queuing service interrupt, cause handle queuing service the stability of a system it is poor；Queue machine can not be disposed individually；Row
Team's process simply obtains visitor's session request from internal memory, and preferred first customer side is used as matching customer side, this mode
So that the workload of each customer service is uneven when contact staff is numerous.
The content of the invention
The technical problems to be solved by the invention are that there is provided a kind of queuing based on redis in view of the shortcomings of the prior art
Method and system.
The technical scheme that the present invention solves above-mentioned technical problem is as follows：A kind of queuing strategy based on redis, including it is as follows
Step：
S1, receives visitor's session request that guest is sent, and according to visitor's session request generation request ID, is being pre-created
Queuing list in insertion request ID；
S2, obtains according to visitor's session request and once services customer service list, obtains the current service session column of all customer sides
The service conversation list of table and the same day；
S3, obtains all online customer service ID, is once taken online with once service customer service list determination according to all online customer service ID
Business customer service list, distinguishes true according to all online customer service ID, all current service session lists and same day service conversation list
The online current service session list at fixed all online customer service ends and the service conversation list of the online same day；
S4, takes out a request ID from queuing list, according to default once service weight, current service weight, the same day
Having serviced weight, online once service customer service list, online current service session list and the service conversation list of the online same day is
One request ID determines matching customer side.
The beneficial effects of the invention are as follows：By being queued up according to visitor's session request generation request ID, and by request ID insertions
In list, distributed deployment is realized, the ability and stability of business processing is lifted, user experience is improved.By once servicing power
Weight, current service weight, the same day have serviced weight, online once service customer service list, online current service session list and online
Same day service conversation list determines matching client for the request ID taken out, realizes the work of balanced each customer service
Amount, realizes the scalability of business processing.
On the basis of above-mentioned technical proposal, the present invention can also do following improvement：
Further, the S4 steps include：
S41, takes out a request ID from queuing list；
S42, judges whether there is data in online once service customer service list, is to perform S44, otherwise performs S43；
S43, weight, online current service session list and online had been serviced according to default current service weight, the same day
Same day service conversation list is that one request ID determines matching customer side；
S44, weight, online once service customer service row had been serviced according to default once service weight, current service weight, the same day
Table, online current service session list and the service conversation list of the online same day are that one request ID determines matching customer service
End.
Further, the S43 steps include：
S431, the current of each online customer service end is obtained according to the online current service session list at each online customer service end
Service conversation numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online
The current service session ratio of customer side；
S432, working as each online customer service end is obtained according to the service conversation list of the online same day at each online customer service end
Day service conversation numerical value, according to the same day at each online customer service end, service conversation numerical value and the second preset value calculated and obtained every
The same day at individual online customer service end service conversation ratio；
S433, according to default current service weight, the same day serviced weight, each online customer service end current service meeting
The same day at words ratio and each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
S434, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the score
Highest online customer service end is one request ID matching customer side.
Further, the S44 steps include：
S441, according to the total service times and the service times meter at each online customer service end once serviced online in customer service list
Calculate the once service ratio for obtaining each online customer service end in online once service customer service list；
S442, the current of each online customer service end is obtained according to the online current service session list at each online customer service end
Service conversation numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online
The current service session ratio of customer side；
S443, working as each online customer service end is obtained according to the service conversation list of the online same day at each online customer service end
Day service conversation numerical value, according to the same day at each online customer service end, service conversation numerical value and the second preset value calculated and obtained every
The same day at individual online customer service end service conversation ratio；
S444, had serviced weight according to default once service weight, current service weight, the same day, has once serviced customer service online
Once the service ratio at each online customer service end, the current service session ratio at each online customer service end and each online visitor in list
The same day for taking end, service conversation ratio calculated the score value for obtaining all online customer service ends；
S445, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the score
Highest online customer service end is one request ID matching customer side.
Further, the S1 steps include：
S11, receives at least one visitor's session request of at least one guest transmission；
S12, at least one request ID is generated according at least one visitor's session request；
S13, is sequentially inserted into according to the order for receiving at least one visitor's session request in the queuing list being pre-created
Each request ID at least one request ID.
The technical scheme that the present invention solves above-mentioned technical problem is as follows：A kind of queuing system based on redis, including：
Queue module, visitor's session request for receiving guest transmission, according to visitor's session request generation request ID,
The insertion request ID in the queuing list being pre-created；
Acquisition module, customer service list is once serviced for being obtained according to visitor's session request, obtains the current of all customer sides
The service conversation list of service conversation list and the same day；
Determining module, for obtaining all online customer service ID, according to all online customer service ID and once service customer service list was true
It is scheduled on line and once services customer service list, according to all online customer service ID, all current service session lists and the same day service conversation
List determines online current service session list and the service conversation list of the online same day at all online customer service ends respectively；
Matching module, for taking out a request ID from queuing list, according to default once service weight, current service
Weight, the same day have serviced weight, online once service customer service list, online current service session list and the online same day meeting of service
It is that one request ID determines matching customer side to talk about list.
The beneficial effects of the invention are as follows：By being queued up according to visitor's session request generation request ID, and by request ID insertions
In list, distributed deployment is realized, the ability and stability of business processing is lifted, user experience is improved.By once servicing power
Weight, current service weight, the same day have serviced weight, online once service customer service list, online current service session list and online
Same day service conversation list determines matching client for the request ID taken out, realizes the work of balanced each customer service
Amount, realizes the scalability of business processing.
On the basis of above-mentioned technical proposal, the present invention can also do following improvement：
Further, the matching module includes：
Module is taken out, for taking out a request ID from queuing list；
Judge module, is to call the second matching module for judging online whether there is data in once service customer service list,
Otherwise the first matching module is called；
First matching module, for having serviced weight, online current service meeting according to default current service weight, the same day
It is that one request ID determines matching customer side to talk about list and the service conversation list of the online same day；
Second matching module, for according to default once service weight, current service weight, the same day serviced weight,
Line once serviced customer service list, online current service session list and the service conversation list of the online same day for one request ID
It is determined that matching customer side.
Further, first matching module includes：
First computing module, each exists for being obtained according to the online current service session list at each online customer service end
The current service session numerical value of line customer side, according to the current service session numerical value at each online customer service end and the first preset value meter
Calculate the current service session ratio for obtaining each online customer service end；
First computing module again, for obtaining each according to the service conversation list of the online same day at each online customer service end
The same day at online customer service end service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and second pre-
If value, which is calculated, obtains same day at each online customer service end service conversation ratio；
First whole computing module, for having serviced weight, each online customer service according to default current service weight, the same day
The service conversation ratio calculating of the same day at the current service session ratio at end and each online customer service end obtains all online customer services
The score value at end；
First matching determining module, be ranked up for the score value to all online customer service ends, determine highest scoring
Line customer side, the online customer service end of the highest scoring is one request ID matching customer side.
Further, second matching module includes：
Second first computing module, for the total service times and each online customer service in online once service customer service list
The service times at end calculate the once service ratio for obtaining each online customer service end in online once service customer service list；
Second computing module again, each exists for being obtained according to the online current service session list at each online customer service end
The current service session numerical value of line customer side, according to the current service session numerical value at each online customer service end and the first preset value meter
Calculate the current service session ratio for obtaining each online customer service end；
Second computing module again, for obtaining each according to the service conversation list of the online same day at each online customer service end
The same day at online customer service end service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and second pre-
If value, which is calculated, obtains same day at each online customer service end service conversation ratio；
Second whole computing module, for according to default once service weight, current service weight, the same day serviced weight,
Once service ratio, the current service session ratio at each online customer service end at each online customer service end in customer service list were once serviced online
The same day at example and each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
Second matching determining module, be ranked up for the score value to all online customer service ends, determine highest scoring
Line customer side, the online customer service end of the highest scoring is one request ID matching customer side.
Further, the queue module includes：
Receiving module, at least one visitor's session request for receiving the transmission of at least one guest；
Generation module, for generating at least one request ID according at least one visitor's session request；
Insert module, for according to receive at least one visitor's session request order in the queuing list being pre-created
It is sequentially inserted into each request ID at least one request ID.
Brief description of the drawings
The schematic flow sheet for the queuing strategy based on redis that Fig. 1 provides for one embodiment of the invention；
The schematic flow sheet of step 4 in the queuing strategy based on redis that Fig. 2 provides for another embodiment of the present invention；
The structural representation for the queuing system based on redis that Fig. 3 provides for one embodiment of the invention；
The structural representation of matching module in the queuing system based on redis that Fig. 4 provides for another embodiment of the present invention.
Embodiment
The principle and feature of the present invention are described below in conjunction with accompanying drawing, the given examples are served only to explain the present invention, and
It is non-to be used to limit the scope of the present invention.
As shown in figure 1, the queuing strategy provided in an embodiment of the present invention based on redis, comprises the following steps：
S1, receives visitor's session request that guest is sent, and according to visitor's session request generation request ID, is being pre-created
Queuing list in insertion request ID；
S2, obtains according to visitor's session request and once services customer service list, obtains the current service session column of all customer sides
The service conversation list of table and the same day；
S3, obtains all online customer service ID, is once taken online with once service customer service list determination according to all online customer service ID
Business customer service list, distinguishes true according to all online customer service ID, all current service session lists and same day service conversation list
The online current service session list at fixed all online customer service ends and the service conversation list of the online same day；
S4, takes out a request ID from queuing list, according to default once service weight, current service weight, the same day
Having serviced weight, online once service customer service list, online current service session list and the service conversation list of the online same day is
One request ID determines matching customer side.
Queuing strategy provided in an embodiment of the present invention based on redis, by asking ID according to the generation of visitor's session request,
And insert request ID in queuing list, distributed deployment is realized, the ability and stability of business processing is lifted, user's body is improved
Degree of testing.Weight, online once service customer service list, online current clothes have been serviced by once servicing weight, current service weight, the same day
Session list of being engaged in and the service conversation list of the online same day determine matching client for the request ID taken out, realize equilibrium
The workload of each customer service, realizes the scalability of business processing.
As shown in Fig. 2 the queuing strategy provided in an embodiment of the present invention based on redis, on the basis of a upper embodiment,
The S4 steps include：
S41, takes out a request ID from queuing list；
S42, judges whether there is data in online once service customer service list, is to perform S44, otherwise performs S43；
S43, weight, online current service session list and online had been serviced according to default current service weight, the same day
Same day service conversation list is that one request ID determines matching customer side；
S44, weight, online once service customer service row had been serviced according to default once service weight, current service weight, the same day
Table, online current service session list and the service conversation list of the online same day are that one request ID determines matching customer service
End.
In the embodiment, request ID is taken out according to first taking-up mode is first inserted, to realize the fairness of queuing.
In the embodiment, also receive corresponding with visitor's session request while the visitor's session request for receiving guest transmission
Information, described information deposit Hash entity in, when take out one request ID and determine matching customer side when from Hash entity
The information is taken out, the session of guest and matching customer side is set up according to the information.
In the embodiment, the once service customer service list can include following content：Played from current time before one month
Between all customer sides once serviced for guest customer service ID and customer side job number.Set and always once took for each guest
Business customer service list, after guest is serviced by a customer side, customer service list was once serviced on the same day to the total of the guest is belonged to
Middle insertion this customer service ID and customer side job number.Once service customer service list once serviced objective according to current time and a month time limit from always
Take list to acquire, and this is deleted after guest and customer side set up session and once service customer service list, once service customer service row
The List name of table can be visitor ID.
Current service session list is set up to each customer side, the List name of current service session list can be customer service
ID, and the session id of the session is inserted into after a customer side and guest set up session belongs to one customer side
In current service session list, the session id is subordinated to the current service session list of a customer side in the conversation end
Middle to delete, real-time update belongs to the current service session list of each customer side.One customer side can be same with multiple guests
Shi Jianli sessions.All the time customer service ID is included in current service session list.
Same day service conversation list is set up to each customer side, the List name of same day service conversation list can be
Customer service ID, and when completing a session in a customer side and guest, the session id of this session is inserted into and belongs to a visitor
In the same day service conversation list on the same day for taking end, real-time update belongs to the same day service conversation list of each customer side.
Same day service conversation list includes customer service ID all the time.
Because some guests are probably to use the queuing strategy provided in an embodiment of the present invention based on redis for the first time,
Thus belong to the once service customer service list of some guests without any data, thus perform S42 steps.
In the embodiment, it is default that once service weight, current service weight and the same day, which had serviced weight,.Current service
The weighted value that weight, once service weight and the same day have serviced weight is reduced successively.Preferably, pre-setting current service weight is
0.5, it is 0.3 to pre-set once service weight, pre-sets the same day and has serviced weight for 0.2.Current service weight sets highest
Be due to it characterize be current time each customer side service session total amount, when the current time session of a customer side is total
When measuring very few, a customer side more preferably should turn into matching customer side in other customer sides, and the workload of each customer service is
Can be more balanced.Once service weight set that time high be due to that it characterizes is the guest for sending visitor's session request by some customer service
The service times at end, when the service times of a customer side within certain time limit are higher, illustrate that guest is easier to being somebody's turn to do
One customer side is linked up, thus a customer side more preferably should turn into matching customer side, the experience of user in other customer sides
Effect just can be more preferable.What the same day had serviced weight sign is the same day session total amount that has serviced of each customer side, when a customer service
When the same day at end, service conversation total amount was very few, a customer side more preferably should turn into matching customer side in other customer sides,
The workload of each customer service could be more balanced.
Queuing strategy provided in an embodiment of the present invention based on redis, be by judging once to service in customer service list online
It is no to have data, and then use a kind of mode when there is data to take out one asks ID to determine matching customer side, in no data
Shi Caiyong another ways determine matching customer side for the request ID taken out, realize the workload of balanced each customer service,
Realize the scalability of business processing.
Alternatively, in the embodiment of the present invention, the S43 steps include：
S431, the current of each online customer service end is obtained according to the online current service session list at each online customer service end
Service conversation numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online
The current service session ratio of customer side；
S432, working as each online customer service end is obtained according to the service conversation list of the online same day at each online customer service end
Day service conversation numerical value, according to the same day at each online customer service end, service conversation numerical value and the second preset value calculated and obtained every
The same day at individual online customer service end service conversation ratio；
S433, according to default current service weight, the same day serviced weight, each online customer service end current service meeting
The same day at words ratio and each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
S434, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the score
Highest online customer service end is one request ID matching customer side.
In the embodiment, the current service session numerical value for obtaining each online customer service end is by each online customer service end
Session id number in online current service session list is determined.Obtain same day at each online customer service end service conversation numerical value
It is the session id number determination in the service conversation list of the online same day by each online customer service end.First preset value is root
It is set in advance according to the session number that customer side is currently at most serviced, it is fixed value.Second preset value is worked as according to customer side
Day at most the session numbers that have serviced and it is set in advance, be fixed value.By the current service session number at each online customer service end
The value current service session ratio for being worth to each online customer service end more default than upper first；By the same day at each online customer service end
The second default same day for being worth to each online customer service end service conversation ratio on service conversation numeric ratio.
S433 steps are specially：By multiplying for the current service session ratio at each online customer service end and current service weight
Product, along with same day at each online customer service end, service conversation ratio and the same day had serviced the product of weight, obtain it is all
The score value of line customer side.
In above-described embodiment, weight, the current service at each online customer service end had been serviced by current service weight, the same day
The score value at all online customer service ends of the same day at session ratio and each online customer service end service conversation ratio calculating, according to score value
Size determines matching customer side, realizes the workload of balanced each customer service, realizes the scalability of business processing.
Alternatively, in the embodiment of the present invention, the S44 steps include：
S441, according to the total service times and the service times meter at each online customer service end once serviced online in customer service list
Calculate the once service ratio for obtaining each online customer service end in online once service customer service list；
S442, the current of each online customer service end is obtained according to the online current service session list at each online customer service end
Service conversation numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online
The current service session ratio of customer side；
S443, working as each online customer service end is obtained according to the service conversation list of the online same day at each online customer service end
Day service conversation numerical value, according to the same day at each online customer service end, service conversation numerical value and the second preset value calculated and obtained every
The same day at individual online customer service end service conversation ratio；
S444, had serviced weight according to default once service weight, current service weight, the same day, has once serviced customer service online
Once the service ratio at each online customer service end, the current service session ratio at each online customer service end and each online visitor in list
The same day for taking end, service conversation ratio calculated the score value for obtaining all online customer service ends；
S445, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the score
Highest online customer service end is one request ID matching customer side.
In the embodiment, the S441 steps are specially：Once service customer service list is to record in certain time limit to own online
The customer service ID and customer side job number at the online customer service end once serviced for guest, according to once customer service in service customer service list online
ID calculates the service times at each online customer service end, and the service times at each online customer service end were once serviced online than upper respectively
Total service times at all online customer service ends in customer service list obtain each online customer service end in online once service customer service list
Once service ratio.
The S444 steps are specially：Will online once in service customer service list the once service ratio at each online customer service end with
Once the product of weight was serviced, the product of current service weight and the current service session ratio at each online customer service end is added, then
The product of same day at weight and each online customer service end service conversation ratio was serviced plus the same day, calculating obtains all online
The score value of customer side.
In above-described embodiment, by once servicing weight, current service weight, the same day had serviced weight, once service is objective online
Take the once service ratio at each online customer service end in list, the current service session ratio at each online customer service end and each online
The score value at all online customer service ends of the same day of customer side service conversation ratio calculating, matching customer service is determined according to score value size
End, realizes the workload of balanced each customer service, realizes the scalability of business processing.
Alternatively, in the embodiment of the present invention, the S1 steps include：
S11, receives at least one visitor's session request of at least one guest transmission；
S12, at least one request ID is generated according at least one visitor's session request；
S13, is sequentially inserted into according to the order for receiving at least one visitor's session request in the queuing list being pre-created
Each request ID at least one request ID.
In the embodiment, visitor's session request that guest is sent is variant in time, thus receives visitor
Session request is also to have time sequencing, and is inserted in the queuing list being pre-created according to asking that visitor's session request is generated
It is also sequential to seek ID, and insertion request ID order is identical with the order for receiving visitor's session request.
In above-described embodiment, order of the ID order with receiving visitor's session request is asked by being inserted in queuing list
It is identical, first queuing, distributed deployment in an orderly manner are realized, the ability and stability of business processing is lifted, improves user experience.
Alternatively, in the embodiment of the present invention, S0 steps are also included before the S1 steps, the S0 steps include：In collection
Distributed environment is built in group's server.
Alternatively, in the embodiment of the present invention, the queuing list being pre-created is pre-sales queuing list.
In the embodiment, visitor's session request carries pre-sales mark, is given birth to according to visitor's session request with pre-sales mark
Into request ID, request ID is inserted into pre-sales queuing list according to pre-sales mark.It is to sell using the queuing strategy based on redis
Request ID in front-seat queue table determines matching customer side.
Alternatively, in the embodiment of the present invention, the queuing list being pre-created is list of queuing up after sale.
In the embodiment, visitor's session request is given birth to identifying after sale according to the visitor's session request identified after sale
Into request ID, request ID is inserted into queuing list after sale according to identifying after sale.It is to sell using the queuing strategy based on redis
Request ID in heel row queue table determines matching customer side.
In above-described embodiment, pre-sales queuing list is set to by queuing list or list of queuing up after sale, at pre-sales group and
Organize after sale and apply the queuing strategy based on redis, realize distributed deployment, lift the ability and stability of business processing, carry
High user experience, the workload of balanced each customer service, eliminate because pre-sales group different with the customer side organized after sale and caused by row
Team's difference.
As shown in figure 3, the queuing system provided in an embodiment of the present invention based on redis, including：
Queue module, visitor's session request for receiving guest transmission, according to visitor's session request generation request ID,
The insertion request ID in the queuing list being pre-created；
Acquisition module, customer service list is once serviced for being obtained according to visitor's session request, obtains the current of all customer sides
The service conversation list of service conversation list and the same day；
Determining module, for obtaining all online customer service ID, according to all online customer service ID and once service customer service list was true
It is scheduled on line and once services customer service list, according to all online customer service ID, all current service session lists and the same day service conversation
List determines online current service session list and the service conversation list of the online same day at all online customer service ends respectively；
Matching module, for taking out a request ID from queuing list, according to default once service weight, current service
Weight, the same day have serviced weight, online once service customer service list, online current service session list and the online same day meeting of service
It is that one request ID determines matching customer side to talk about list.
Queuing system provided in an embodiment of the present invention based on redis, by asking ID according to the generation of visitor's session request,
And insert request ID in queuing list, distributed deployment is realized, the ability and stability of business processing is lifted, user's body is improved
Degree of testing.Weight, online once service customer service list, online current clothes have been serviced by once servicing weight, current service weight, the same day
Session list of being engaged in and the service conversation list of the online same day determine matching client for the request ID taken out, realize equilibrium
The workload of each customer service, realizes the scalability of business processing.
As shown in figure 4, the queuing system provided in an embodiment of the present invention based on redis, on the basis of a upper embodiment,
The matching module includes：
Module is taken out, for taking out a request ID from queuing list；
Judge module, is to call the second matching module for judging online whether there is data in once service customer service list,
Otherwise the first matching module is called；
First matching module, for having serviced weight, online current service meeting according to default current service weight, the same day
It is that one request ID determines matching customer side to talk about list and the service conversation list of the online same day；
Second matching module, for according to default once service weight, current service weight, the same day serviced weight,
Line once serviced customer service list, online current service session list and the service conversation list of the online same day for one request ID
It is determined that matching customer side.
Queuing system provided in an embodiment of the present invention based on redis, be by judging once to service in customer service list online
It is no to have data, and then use a kind of mode when there is data to take out one asks ID to determine matching customer side, in no data
Shi Caiyong another ways determine matching customer side for the request ID taken out, realize the workload of balanced each customer service,
Realize the scalability of business processing.
Alternatively, in the embodiment of the present invention, first matching module includes：
First computing module, each exists for being obtained according to the online current service session list at each online customer service end
The current service session numerical value of line customer side, according to the current service session numerical value at each online customer service end and the first preset value meter
Calculate the current service session ratio for obtaining each online customer service end；
First computing module again, for obtaining each according to the service conversation list of the online same day at each online customer service end
The same day at online customer service end service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and second pre-
If value, which is calculated, obtains same day at each online customer service end service conversation ratio；
First whole computing module, for having serviced weight, each online customer service according to default current service weight, the same day
The service conversation ratio calculating of the same day at the current service session ratio at end and each online customer service end obtains all online customer services
The score value at end；
First matching determining module, be ranked up for the score value to all online customer service ends, determine highest scoring
Line customer side, the online customer service end of the highest scoring is one request ID matching customer side.
Alternatively, in the embodiment of the present invention, second matching module includes：
Second first computing module, for the total service times and each online customer service in online once service customer service list
The service times at end calculate the once service ratio for obtaining each online customer service end in online once service customer service list；
Second computing module again, each exists for being obtained according to the online current service session list at each online customer service end
The current service session numerical value of line customer side, according to the current service session numerical value at each online customer service end and the first preset value meter
Calculate the current service session ratio for obtaining each online customer service end；
Second computing module again, for obtaining each according to the service conversation list of the online same day at each online customer service end
The same day at online customer service end service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and second pre-
If value, which is calculated, obtains same day at each online customer service end service conversation ratio；
Second whole computing module, for according to default once service weight, current service weight, the same day serviced weight,
Once service ratio, the current service session ratio at each online customer service end at each online customer service end in customer service list were once serviced online
The same day at example and each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
Second matching determining module, be ranked up for the score value to all online customer service ends, determine highest scoring
Line customer side, the online customer service end of the highest scoring is one request ID matching customer side.
Alternatively, in the embodiment of the present invention, the queue module includes：
Receiving module, at least one visitor's session request for receiving the transmission of at least one guest；
Generation module, for generating at least one request ID according at least one visitor's session request；
Insert module, for according to receive at least one visitor's session request order in the queuing list being pre-created
It is sequentially inserted into each request ID at least one request ID.
Function in the queuing system based on redis that the embodiment is provided performed by modules is in above-mentioned implementation
Have been described in detail, will not be repeated here in the queuing strategy based on redis that example is provided.
Memory setting in individual server is the distributed memory in cluster server by all embodiments of the invention,
Individually queuing system of the deployment based on redis, is queued up to visitor's session request using the queuing system based on redis and determined
With customer side, the queuing system based on redis is independent, can constantly be extended, the business processing of the queuing system based on redis
Ability enhancing.All embodiments of the invention all should be used in online customer service system, and online customer service system is to visitor's session request
Queue up, preferentially take out the visitor's session request first inserted, be the visitor's session request matching customer side first inserted, then this is matched
Session is set up in customer side with guest, and the guest is the guest for sending the visitor's session request first inserted, session establishment
Guest and customer side can start instant messaging communication afterwards.
Redis be the use increased income an ANSI C language write, support network, can based on internal memory also can persistence day
Will type, Key-Value databases, i.e. distributed caching.
The foregoing is only presently preferred embodiments of the present invention, be not intended to limit the invention, it is all the present invention spirit and
Within principle, any modification, equivalent substitution and improvements made etc. should be included in the scope of the protection.
Claims (10)
1. a kind of queuing strategy based on redis, it is characterised in that comprise the following steps：
S1, receives visitor's session request that guest is sent, according to visitor's session request generation request ID, in the row being pre-created
Insertion request ID in queue table；
S2, obtains according to visitor's session request and once services customer service list, obtain all customer sides current service session list and
Same day service conversation list；
S3, obtains all online customer service ID, according to all online customer service ID and once serviced customer service list and determines online once service visitor
List is taken, institute is determined according to all online customer service ID, all current service session lists and same day service conversation list respectively
There are online current service session list and the service conversation list of the online same day at online customer service end；
S4, takes out a request ID from queuing list, has been taken according to default once service weight, current service weight, the same day
Business weight, online once service customer service list, online current service session list and the service conversation list of the online same day are described
One request ID determines matching customer side.
2. the queuing strategy according to claim 1 based on redis, it is characterised in that the S4 steps include：
S41, takes out a request ID from queuing list；
S42, judges whether there is data in online once service customer service list, is to perform S44, otherwise performs S43；
S43, weight, online current service session list and the online same day had been serviced according to default current service weight, the same day
Service conversation list is that one request ID determines matching customer side；
S44, according to default once service weight, current service weight, the same day serviced weight, online once service customer service list,
Online current service session list and the service conversation list of the online same day are that one request ID determines matching customer side.
3. the queuing strategy according to claim 2 based on redis, it is characterised in that the S43 steps include：
S431, the current service at each online customer service end is obtained according to the online current service session list at each online customer service end
Session numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online customer service
The current service session ratio at end；
S432, the same day at each online customer service end has been obtained according to the service conversation list of the online same day at each online customer service end
Service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and the second preset value calculate obtain it is each
The same day of line customer side service conversation ratio；
S433, according to default current service weight, the same day serviced weight, each online customer service end current service session ratio
The same day at example and each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
S434, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the highest scoring
Online customer service end be one request ID matching customer side.
4. the queuing strategy according to claim 2 based on redis, it is characterised in that the S44 steps include：
S441, is calculated according to the total service times and the service times at each online customer service end that once service online in customer service list
To the once service ratio for once servicing each online customer service end in customer service list online；
S442, the current service at each online customer service end is obtained according to the online current service session list at each online customer service end
Session numerical value, calculates according to the current service session numerical value at each online customer service end and the first preset value and obtains each online customer service
The current service session ratio at end；
S443, the same day at each online customer service end has been obtained according to the service conversation list of the online same day at each online customer service end
Service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and the second preset value calculate obtain it is each
The same day of line customer side service conversation ratio；
S444, had serviced weight according to default once service weight, current service weight, the same day, has once serviced customer service list online
In each online customer service end once service ratio, the current service session ratio at each online customer service end and each online customer service end
Service conversation ratio calculates and obtains the score value at all online customer service ends the same day；
S445, is ranked up to the score value at all online customer service ends, determines the online customer service end of highest scoring, the highest scoring
Online customer service end be one request ID matching customer side.
5. the queuing strategy based on redis according to claim any one of 1-4, it is characterised in that the S1 steps bag
Include：
S11, receives at least one visitor's session request of at least one guest transmission；
S12, at least one request ID is generated according at least one visitor's session request；
S13, is sequentially inserted into described according to the order for receiving at least one visitor's session request in the queuing list being pre-created
Each request ID at least one request ID.
6. a kind of queuing system based on redis, it is characterised in that including：
Queue module, visitor's session request for receiving guest transmission, according to visitor's session request generation request ID, pre-
Insertion request ID in the queuing list first created；
Acquisition module, customer service list is once serviced for being obtained according to visitor's session request, obtains the current service of all customer sides
The service conversation list of session list and the same day；
Determining module, for obtaining all online customer service ID, exists according to all online customer service ID with once service customer service list determination
Line once services customer service list, according to all online customer service ID, all current service session lists and same day service conversation list
Online current service session list and the service conversation list of the online same day at all online customer service ends are determined respectively；
Matching module, for taking out a request ID from queuing list, is weighed according to default once service weight, current service
Weight, the same day have serviced weight, online once service customer service list, online current service session list and the online same day service conversation
List is that one request ID determines matching customer side.
7. the queuing system according to claim 6 based on redis, it is characterised in that the matching module includes：
Module is taken out, for taking out a request ID from queuing list；
Judge module, is to call the second matching module, otherwise for judging online whether there is data in once service customer service list
Call the first matching module；
First matching module, for having serviced weight, online current service session column according to default current service weight, the same day
Table and the service conversation list of the online same day are that one request ID determines matching customer side；
Second matching module, for according to default once service weight, current service weight, the same day serviced weight, it is online once
Customer service list, online current service session list and the service conversation list of the online same day is serviced to determine for one request ID
Match customer side.
8. the queuing system according to claim 7 based on redis, it is characterised in that first matching module includes：
First computing module, for obtaining each online visitor according to the online current service session list at each online customer service end
The current service session numerical value at end is taken, is calculated according to the current service session numerical value and the first preset value at each online customer service end
To the current service session ratio at each online customer service end；
First computing module again, for obtaining each online according to the service conversation list of the online same day at each online customer service end
The same day of customer side service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and the second preset value
Calculate and obtain same day at each online customer service end service conversation ratio；
The first whole computing module, for having serviced weight, each online customer service end according to default current service weight, the same day
The service conversation ratio calculating of the same day at current service session ratio and each online customer service end obtains all online customer service ends
Score value；
First matching determining module, is ranked up for the score value to all online customer service ends, determines the online visitor of highest scoring
End is taken, the online customer service end of the highest scoring is one request ID matching customer side.
9. the queuing system according to claim 7 based on redis, it is characterised in that second matching module includes：
Second first computing module, for according to the total service times and each online customer service end once serviced online in customer service list
Service times calculate the once service ratio for obtaining each online customer service end in online once service customer service list；
Second computing module again, for obtaining each online visitor according to the online current service session list at each online customer service end
The current service session numerical value at end is taken, is calculated according to the current service session numerical value and the first preset value at each online customer service end
To the current service session ratio at each online customer service end；
Second computing module again, for obtaining each online according to the service conversation list of the online same day at each online customer service end
The same day of customer side service conversation numerical value, according to the same day at each online customer service end service conversation numerical value and the second preset value
Calculate and obtain same day at each online customer service end service conversation ratio；
Second whole computing module, for having serviced weight according to default once service weight, current service weight, the same day, online
Once the once service ratio at each online customer service end in service customer service list, the current service session ratio at each online customer service end and
The same day at each online customer service end, service conversation ratio calculated the score value for obtaining all online customer service ends；
Second matching determining module, is ranked up for the score value to all online customer service ends, determines the online visitor of highest scoring
End is taken, the online customer service end of the highest scoring is one request ID matching customer side.
10. the queuing system based on redis according to claim any one of 6-9, it is characterised in that the queue module
Including：
Receiving module, at least one visitor's session request for receiving the transmission of at least one guest；
Generation module, for generating at least one request ID according at least one visitor's session request；
Insert module, for according to receive at least one visitor's session request order in the queuing list being pre-created successively
Each request ID in insertion at least one request ID.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710391652.6A CN107135321B (en) | 2017-05-27 | 2017-05-27 | queuing method and system based on redis |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710391652.6A CN107135321B (en) | 2017-05-27 | 2017-05-27 | queuing method and system based on redis |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107135321A true CN107135321A (en) | 2017-09-05 |
| CN107135321B CN107135321B (en) | 2019-12-06 |
Family
ID=59734192
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710391652.6A Active CN107135321B (en) | 2017-05-27 | 2017-05-27 | queuing method and system based on redis |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107135321B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108924256A (en) * | 2018-08-09 | 2018-11-30 | 北京中关村科金技术有限公司 | Method for intelligently routing in a kind of online customer service |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH02266741A (en) * | 1989-04-07 | 1990-10-31 | Nec Corp | Telephone system for conference |
| JP2012507976A (en) * | 2008-11-06 | 2012-03-29 | ザ リソース グループ インターナショナル， リミテッド | Two-step routing procedure at the call center |
| CN102546986A (en) * | 2011-12-14 | 2012-07-04 | 中兴通讯股份有限公司 | Call center, method of calling, client side and agent service side |
| US20140114876A1 (en) * | 2012-10-23 | 2014-04-24 | ReviewBuzz Inc. | Systems and methods for obtaining and utilizing online customer service reviews of individual employees |
| CN104796422A (en) * | 2015-04-22 | 2015-07-22 | 北京京东尚科信息技术有限公司 | Online customer service staff equilibrium assignment method and online customer service staff equilibrium assignment device |
| CN105530387A (en) * | 2015-12-14 | 2016-04-27 | 上海携程商务有限公司 | Incoming call processing method of IVR system |
| CN105898087A (en) * | 2016-06-20 | 2016-08-24 | 上海久科信息技术有限公司 | Full-routing customer service distribution method |
| CN106341562A (en) * | 2016-11-07 | 2017-01-18 | 上海易谷网络科技有限公司 | Method for selecting customer service staff in Internet environment |
-
2017
- 2017-05-27 CN CN201710391652.6A patent/CN107135321B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JPH02266741A (en) * | 1989-04-07 | 1990-10-31 | Nec Corp | Telephone system for conference |
| JP2012507976A (en) * | 2008-11-06 | 2012-03-29 | ザ リソース グループ インターナショナル， リミテッド | Two-step routing procedure at the call center |
| CN102546986A (en) * | 2011-12-14 | 2012-07-04 | 中兴通讯股份有限公司 | Call center, method of calling, client side and agent service side |
| US20140114876A1 (en) * | 2012-10-23 | 2014-04-24 | ReviewBuzz Inc. | Systems and methods for obtaining and utilizing online customer service reviews of individual employees |
| CN104796422A (en) * | 2015-04-22 | 2015-07-22 | 北京京东尚科信息技术有限公司 | Online customer service staff equilibrium assignment method and online customer service staff equilibrium assignment device |
| CN105530387A (en) * | 2015-12-14 | 2016-04-27 | 上海携程商务有限公司 | Incoming call processing method of IVR system |
| CN105898087A (en) * | 2016-06-20 | 2016-08-24 | 上海久科信息技术有限公司 | Full-routing customer service distribution method |
| CN106341562A (en) * | 2016-11-07 | 2017-01-18 | 上海易谷网络科技有限公司 | Method for selecting customer service staff in Internet environment |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108924256A (en) * | 2018-08-09 | 2018-11-30 | 北京中关村科金技术有限公司 | Method for intelligently routing in a kind of online customer service |
Also Published As
| Publication number | Publication date |
|---|---|
| CN107135321B (en) | 2019-12-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102361995B1 (en) | Techniques for behavioral pairing in a contact center system | |
| CN103684874B (en) | Method and device for automatically distributing online customer service executives to conduct customer service | |
| CN104796422B (en) | A kind of method and device of online customer service equilibrium assignment | |
| US20210218842A1 (en) | Method, device, server and storage medium of agent allocation | |
| CN100499492C (en) | Method for realizing electronic work order queuing | |
| US7761323B2 (en) | Method and system for scheduling a customer service callback | |
| CN108874640A (en) | A kind of appraisal procedure and device of clustering performance | |
| EP1094655A1 (en) | Arrangement for resource and work-item selection | |
| CN102737159B (en) | The operation of data processing net with multiple data centers being geographically separated | |
| CN110233860A (en) | A kind of load-balancing method, device and system | |
| CN1268851A (en) | Improved and technique-based paging route | |
| CN107958526A (en) | One kind is lined up processing method and processing device | |
| CN109600798A (en) | Multi-domain resource allocation method and device in a kind of network slice | |
| CN111142746B (en) | System quota calculation method and device | |
| CN107231393A (en) | A kind of conversation processing method and device | |
| CN106504396A (en) | A kind of queuing strategy, device and transaction processing system | |
| CN106570679A (en) | Participant capability based excitation method for crowdsourcing task of group | |
| CN111028406A (en) | Real-time automatic reminding system and method for queuing and calling | |
| CN105338064B (en) | Task cooperative based on Stackelberg game performs method | |
| CN107135321A (en) | A kind of queuing strategy and system based on redis | |
| CN107067187A (en) | Telephony task management method, storage device, storage medium and device | |
| WO2018227864A1 (en) | Information processing method and apparatus | |
| CN111126779B (en) | Customer service work order distribution method and device | |
| Whitt | A multi-class fluid model for a contact center with skill-based routing | |
| CN115394003A (en) | Service handling time length estimation method, device, equipment, storage medium and product |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |