CN113869866A

CN113869866A - Request processing method, device, equipment and storage medium

Info

Publication number: CN113869866A
Application number: CN202111154036.1A
Authority: CN
Inventors: 王达; 李炜豪
Original assignee: Suzhou Dajiaying Information Technology Co Ltd
Current assignee: Suzhou Dajiaying Information Technology Co Ltd
Priority date: 2021-09-29
Filing date: 2021-09-29
Publication date: 2021-12-31

Abstract

The application discloses a request processing method, a request processing device, request processing equipment and a storage medium, and belongs to the technical field of computers. The method comprises the following steps: receiving an information service request of a first account; acquiring a second account set matched with the target position information; acquiring historical service information corresponding to each second account; determining a target account matched with the first account from the second account set according to the historical service information and the second service demand information; and sending an information service request to a client corresponding to the target account to acquire feedback information corresponding to the information service request. According to the technical scheme provided by the embodiment of the application, the demand information in the service request and the service information of the second account can be fully combined, the second account which is matched with the first account in position and has better service quality is distributed to the first account to perform service, the quality and the speed of service request processing are improved, and the request processing efficiency is comprehensively improved.

Description

Request processing method, device, equipment and storage medium

Technical Field

The present application relates to the field of computer technologies, and in particular, to a request processing method, apparatus, device, and storage medium.

Background

With the development of internet technology, more and more users choose to initiate service requests on internet platforms. When a user initiates a service request on the internet platform, the internet platform can distribute corresponding service accounts to service personnel pointed by the service account to process the service request.

In the related art, after a user initiates a service request, the internet platform randomly allocates a corresponding service account to the user account to process the user request. For example, the user request is randomly distributed to the client logged in with the service staff account, so that the service staff pointed by the service account feeds back the user request. However, in practical applications, the service requests of users are various, the random allocation mode is inefficient, and it is not possible to respond to the user's needs and allocate appropriate resource information in a timely and effective manner.

Disclosure of Invention

The embodiment of the application provides a request processing method, a request processing device, request processing equipment and a storage medium.

According to an aspect of an embodiment of the present application, there is provided a request processing method, including:

receiving an information service request of a first account, wherein the information service request comprises first service requirement information and second service requirement information, and the first service requirement information comprises target position information;

acquiring a second account set matched with the target position information, wherein the service position corresponding to each second account in the second account set corresponds to the target position indicated by the target position information;

acquiring historical service information corresponding to each second account;

according to the historical service information and the second service demand information, determining a target account matched with the first account from the second account set, wherein the historical service information corresponding to the target account is matched with the second service demand information;

and sending the information service request to a client corresponding to the target account to acquire feedback information corresponding to the information service request.

According to an aspect of an embodiment of the present application, there is provided a request processing apparatus, including:

the system comprises a request receiving module, a first service request receiving module and a second service request receiving module, wherein the request receiving module is used for receiving an information service request of a first account, the information service request comprises first service requirement information and second service requirement information, and the first service requirement information comprises target position information;

the account acquisition module is used for acquiring a second account set matched with the target position information, and the service position corresponding to each second account in the second account set corresponds to the target position indicated by the target position information;

the historical information acquisition module is used for acquiring historical service information corresponding to each second account;

a target account determining module, configured to determine, according to the historical service information and the second service demand information, a target account matched with the first account from the second account set, where the historical service information corresponding to the target account is matched with the second service demand information;

and the request distribution module is used for sending the information service request to the client corresponding to the target account so as to acquire feedback information corresponding to the information service request.

According to an aspect of an embodiment of the present application, there is provided a computer device including at least one processor, and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the at least one processor implements the request processing method by executing the instructions stored by the memory.

According to an aspect of embodiments of the present application, there is provided a computer-readable storage medium having at least one instruction, at least one program, a set of codes, or a set of instructions stored therein, which is loaded and executed by a processor to implement the above request processing method.

The technical scheme provided by the embodiment of the application can bring the following beneficial effects:

the method comprises the steps of analyzing a received information service request of a first account to obtain first service demand information and second service demand information carried in the information service request, screening a second account with a service position matched with target position information in the first service demand information to obtain a second account set, finding a target account with historical service information matched with the second service demand information from the second account set, finally distributing the service request to the target account to obtain corresponding feedback information, fully combining the demand information in the service request and the service information of the second account, distributing the second account with a matched position and good service quality for the first account to perform service, improving the quality and speed of service request processing, and comprehensively improving the request processing efficiency.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1 is a schematic diagram of an application execution environment provided by one embodiment of the present application;

FIG. 2 is a flow diagram of a request processing method provided by one embodiment of the present application;

FIG. 3(a) is a schematic diagram illustrating an account registration page;

FIG. 3(b) is a schematic diagram illustrating an exemplary page for filling out service requirement information;

fig. 4 to fig. 9 are flowcharts of a request processing method according to an embodiment of the present application, respectively;

FIG. 10 is a block diagram of a request processing device provided in one embodiment of the present application;

fig. 11 is a block diagram of a computer device according to an embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

Referring to fig. 1, a schematic diagram of an application execution environment according to an embodiment of the present application is shown. The application execution environment may include: a terminal 10 and a server 20.

The terminal 10 may be an electronic device such as a mobile phone, a tablet Computer, a game console, an electronic book reader, a multimedia playing device, a wearable device, a PC (Personal Computer), and the like. A client of the application may be installed in the terminal 10.

In the embodiment of the present application, the application program may be an application program capable of providing a life service. Typically, the application is a recruitment-type application. Of course, besides the recruitment-type application, other types of applications may provide lifestyle services. For example, the application may be a placement application, a shopping application, a social contact application, an interactive entertainment application, a browser application, a customer service application, and the like, which is not limited in this embodiment. In addition, for different applications, the provided life services may also be different, and the corresponding functions may also be different, which may be configured in advance according to actual requirements, and this is not limited in the embodiment of the present application. Optionally, a client of the above application program runs in the terminal 10. In some embodiments, the living service includes a recruitment information sharing service for providing work information to the user.

The server 20 is used to provide background services for clients of applications in the terminal 10. Optionally, the server 20 provides background services for applications in multiple terminals 10 simultaneously.

Alternatively, the terminal 10 and the server 20 may communicate with each other through the network 30. The terminal 10 and the server 20 may be directly or indirectly connected through wired or wireless communication, and the present application is not limited thereto.

Referring to fig. 2, a flowchart of a request processing method according to an embodiment of the present application is shown. The method can be applied to a computer device, which refers to an electronic device with data calculation and processing capabilities, for example, the execution subject of each step can be the server 20 in the application program running environment shown in fig. 1. The method can comprise the following steps (210-250).

Step 210, receiving an information service request of a first account.

The first account may be an electronic account held by a user using the relevant application service. For example, in the job application, the user may be a user with job application requirements, such as a blue-collar finder.

The information service request refers to a request for requesting an information service triggered by a user executing a preset operation. Optionally, the information service request may be a request that a new user performs a registration operation trigger, or may be a request that the user performs a preset operation on a third-party application that is detectable by the system, where the preset operation is, for example, a form filling operation and a registration operation, and the embodiment of the present application is not limited to this.

The information service request includes first service requirement information and second service requirement information, and the first service requirement information includes target location information. The first service requirement information and the second service requirement information comprise different types of service requirement information, and the service requirement information can be divided into the first service requirement information and the second service requirement information according to actual conditions.

In one possible implementation, the service requirement information includes personal information. In some application scenarios, personal information is filled in by the user at application registration, or is modified during later use.

In one possible embodiment, the service requirement information comprises target location information. The target position information is position information set by a user. Optionally, the target location information may be divided into the first service requirement information or the second service requirement information. In one possible implementation, the first service requirement information includes target location information. Optionally, the target location information is used to characterize a service area set by a user. For example, in job hunting applications, a user may set an intended work area or set a service area of a service person to obtain target location information. For example, if it is desired to search for local service personnel in the application, the target location information may be set as the area where the user is located. Optionally, the target location information is used to represent a location of a user, and the target location information may be obtained in the following two ways. The 1 st is a user input mode, namely, when registering or inputting the current requirement, the user inputs the current position (such as a city) of the user; the second type is system automatic acquisition, which may be that the system automatically acquires its location when the user registers/inputs the current requirement, or prompts the user to locate the current location or directly acquires the current location of the user when the user registers/inputs the current requirement.

In one possible embodiment, the service requirement information further includes a server profile. The server characteristics may be divided into the first service requirement information or the second service requirement information. In one possible embodiment, the second service requirement information includes a server profile. Optionally, the service characteristic refers to a personality characteristic of the service set by the user based on the user's own needs, and represents a user personality corresponding to the second account that the user desires to allocate. For example, a user's desired broker character in a job hunting class application. The character features have a plurality of character categories, and can be determined by a specific algorithm or information, which is not limited in the embodiments of the present application.

In one possible embodiment, the service requirement information further includes resource requirement information. The resource requirement information refers to information about resources required by the client pointed by the first account. Optionally, the resource requirement information may be divided into the first service requirement information, and may also be divided into the second service requirement information. In one possible embodiment, the second service requirement information includes resource requirement information.

In a possible implementation manner, the resource requirement information includes resource acquisition time limit information and request resource type information.

Optionally, the resource obtaining time limit information is used to characterize a time limit for obtaining the resource by the first account. For example, in job application, the user pointed to by the first account may set the resource acquisition time limit information by selecting an option of "whether to want to find work as soon as possible".

Optionally, the resource demand information further includes response time limit information. The response time limit information can also represent the time limit of the response time of the first account to the second account, namely the demand response time. Illustratively, in the job hunting application, the demand response time represents whether the user has a requirement for the feedback time of the broker, for example, the user wants to contact with him as soon as possible, and the value of the "demand response time" may be: fast, general (for response time), it is also possible: yes, no (for whether it is desired to find the work as soon as possible).

Optionally, the request resource type information is used to characterize the type of the resource required by the first account. Illustratively, in the job hunting application, the requested resource type information includes, but is not limited to, salary information of the user's intended work, work category information, business type information, and work stability information. Optionally, the user may fill in and find a work target, for example, a target such as "family care is stuck with a mouth, issue time, self-realization", and the like, and the system may determine salary information, work type information, enterprise type information, and work stability degree information corresponding to each target according to a preset mapping rule, and further perform resource allocation, so that the requirement information of the user can be quantified, and subsequent matching is facilitated.

Alternatively, the business types may include: the service industry, new energy (manufacturing), chemical industry (manufacturing), vehicle/accessory (manufacturing), electronic factory (manufacturing and assembling), supply chain/logistics, education and training, real estate/building, medical health, etc., which are not limited in the embodiments of the present application.

In one example, as shown in fig. 3(a), a schematic diagram of a page of a registered account is exemplarily shown. When the user registers the first account, the user is required to fill in personal information (including whether the city is expected to find a broker-yes or no; the character of the broker is expected-atmosphere hard type, mild and compatible type, strong and certain type; and the work target is found-family care, mouth pasting, sending time and self realization). The user can click on the expansion control 302 in the personal preference setting field 301 to supplement the filling-out service requirement information. After the user performs corresponding operation on the expansion control 302, the page jumps, and the page after jumping is shown in fig. 3 (b). Fig. 3(b) is a schematic diagram illustrating a page for filling out service requirement information. In fig. 3(b), the user can set the above target position information. For example, for the question of "whether you like the broker is not in the city", the user may select the idea option 303 to indicate that the target location information is set as the city, or the user may select the do-nothing option 304 to indicate that the target location information is set as the unlimited area. In addition, the user can also select the broker personality option 305, can also select the work tendency option 306, and can further set through the personalized demand setting frame 306 to improve the service demand information. It should be noted that, in the embodiment of the present application, the content of the service requirement information is not limited.

Step 220, a second account set matched with the target position information is obtained.

And the service position corresponding to each second account in the second account set corresponds to the target position indicated by the target position information.

The second account may be an account providing a corresponding service for the first account. In some application scenarios, the second account is an intelligent robot, which is used to provide self-service for the user, or may be an electronic account held by the user who provides service in the application. For example, the account held by the broker in the job hunting class application is the second account.

The service location may be a geographic location corresponding to the second account, or an entity service location corresponding to the second account. For example, store locations corresponding to broker accounts in job hunting applications.

And in the distribution rule, matching the service position corresponding to the second account with the target position information, determining the service position matched with the target position information, and then summarizing the second account corresponding to the matched service position to obtain the second account set.

In an exemplary embodiment, as shown in FIG. 4, the implementation of step 220 includes the following steps (221-222).

Step 221, the target service area corresponding to the target location information is determined.

Optionally, it is determined, through the target location information, that the first account selects a service area corresponding to the second account desired to be searched, that is, the target service area. In one example, the target service area is a city in which the second account is currently located.

In step 222, if at least one service location exists in the target service area, a second account set is generated based on the at least one service location.

After determining the target service area, it is determined whether the target service area has a service location, such as a broker store. In one example, if the target service area selected by the user is not the city in which the first account is located, a second account in the region of the country may be selected.

In a possible implementation manner, the target service area is an area where the current login location of the first account is located. Accordingly, as shown in fig. 5, the implementation of step 222 includes the following steps (222A to 222B).

In step 222A, if at least one service location exists in the target service area, a target service location corresponding to the current login location is determined from the at least one service location.

After the target service area is determined in the above step, the following judgment can be made for the target service area:

and if the target service area has the service position, acquiring the service position closest to the current login position of the first account, namely the target service position.

Step 222B, using at least one second account corresponding to the target service location as a second account set.

If the service position does not exist in the target service area, the first account is brought into a default service area, and information is pushed to the first account: because the current service area is limited, the current service area is not distributed to the second account in the target service area, the current service second account is the xx account, and the current service second account can be replaced if an objection exists. And push the information to the second account: the target service area is the xxx area, and since the service area is not involved, the first account may generate regional requirement, please pay attention to the process.

Step 230, obtaining historical service information corresponding to each second account.

In one possible embodiment, in the background or the database, the historical service information corresponding to the second account includes, but is not limited to, the account user characteristics, the response behavior information, the resource usage data, and the request processing data corresponding to the second account.

In one possible embodiment, the historical service information includes account user characteristics. Optionally, the process of determining the account user characteristic includes: acquiring account user information corresponding to each second account, wherein the account user information comprises at least one of a character tag, a message corpus and an operation behavior log; and determining account user characteristics corresponding to each second account based on the account user information. The character tag can be a character tag added by an account user, the message corpus can be a historical chat message record of the account user, and the operation behavior log can also be an operation record of the account user in application. Optionally, the account user characteristics corresponding to the second account may be obtained by modeling the account user information with a user representation.

For example, in a job hunting application, the system sends questionnaires to brokers before each broker is first assigned to handle the user's service needs; the broker fills in and submits the questionnaire based on the actual situation of the broker to obtain the questionnaire survey result of the broker, and the following scores of 16 personality factors are obtained through calculation: groupe (A), clever (B), stability (C), strength (E), excitability (F), constancy (G), dare (H), sensitivity (I), suspicion (L), hallucination (M), ancestry (N), apprehension (O), experimental (Q1), independence (Q2), autonomy (Q3), tonicity (Q4); performing second-order factor analysis based on the scores of the 16 personality factors, and respectively calculating the scores of the broker in four personality types, namely adaptability, extroversion, alertness and courageness; and taking the character type with the highest score value as the character type of the broker. The adaptability corresponding type is friendly, the score is obtained to represent the strength of 'adaptation', and high-score people have smooth living adaptation and feel satisfied; the corresponding type of extroversion is extroversion, the score represents the alert of peaceful mechanism, and the high-grade extroversion is good at the interpersonal activities, clear and no matter how minor; the corresponding type of the alertness of the peaceful system is the alertness of the peaceful system, the obtained score represents the alertness of the peaceful system, the high-grade person is alert of the peaceful system, and the person is on duty and persevered to get spirits; the corresponding type of the dare is the dare type, the high-grade people are independent, dare and limpid, the soul is created, and the long environment or opportunity can be developed is always automatically searched.

Optionally, the response speed of the second account is characterized by the response behavior information. Optionally, the response behavior information includes a response time interval, and the response time interval may be an average response time interval of the second account. Optionally, the response behavior information includes a total response time duration, where the total response time duration is a sum of response time intervals corresponding to the second account processing information service request. Illustratively, in the job hunting application, the response behavior information characterizing the feedback time attribute includes, but is not limited to, data of response time, feedback time, response speed, feedback speed and the like of the broker to the demand. Optionally, the feedback time attribute has 2 value-taking modes, which may be divided into "good, medium, and bad" according to different ranges, or may be directly counted in minutes for the average response time or average feedback time of the second account for all the requirements. Illustratively, in the job application, the response time interval may be a time interval from the detection of the user initiating the information service request by the system to the contact of the broker with the user by one of calling, texting, messaging social software messages, and writing chat records. Alternatively, the response time interval is rated as, on average, 10 minutes (including 10 minutes): good; on average 10 to 30 minutes (including 30 minutes) then rated: good; an average of 30 to 60 minutes (including 60 minutes) was rated medium; over 60 minutes, the rating was poor. And counting the first 20 requirements of the second account of the new access system, wherein the response time attributes corresponding to the second account of the new access system are calculated according to the priority, and the normal calculation process is started from the 21 st requirement distribution.

Under the scene that a user uses the application A and a broker uses the application B, the user initiates a demand or registers personal information in the application A, the demand is sent to a background or a server, the background or the server judges the distribution rule and sends the distribution rule to a target broker, and the broker receives the information of the server through the application B, responds to the demand and feeds back the information. The background can acquire response time intervals of the broker to different demands through monitoring of the application B. The specific manner of responding to the requirement may be to contact the user using the application a through the chat function of the application B; the response time interval may be calculated using the following formula: response time interval-the time at which the broker responds to the demand-the time at which the system allocates the demand to the broker.

For the above calling scenario, the manner of obtaining the historical service information is as follows: firstly, the system acquires the call record and the address book of the mobile phone through the authorization of the address book of the mobile phone (the system can automatically acquire the address book authorization information of the mobile phone of the user, or the system can send an authorization request to the mobile phone of the user, and the system acquires the address book authorization information of the mobile phone after the user agrees), so that the call contact condition of the broker is judged based on the call start time, the call object and the call duration of the broker; and the other is that if the broker passes through the virtual dialing function, the system can perform voice record monitoring, call record and call content, so as to acquire the processing state of the broker receiving the requirement and process the feedback condition. Optionally, the recording feedback needs manual judgment, sensitive word detection is carried out after the recording is converted into characters, sensitive words are found and pushed to customer service, the customer service judges whether service problems exist or not, and if yes, follow-up punishment is carried out.

For the above short message sending scenario, the historical service information is obtained in the following manner: the monitoring of the short message sending scene requires the system to acquire short message information, short message sending records and sending contents of the broker through the authorization of the short message of the mobile phone in advance.

For the above scenario of sending the social software message, the manner of obtaining the historical service information is as follows: the monitoring of the message scene of the social software is as follows: and after the chat record data based on the social software is communicated with the background system which is currently applied, the chat record and the chat time of the broker are regularly pulled from the social software.

For the above scenario of writing the chat record, the manner of obtaining the historical service information is as follows: the system provides a background interface for entering the remark of the chat content, so that an account user can fill in and submit the chat record and the chat content, and the broker can automatically mark the requirement of the user as the return visit after filling in the return visit content.

In one possible embodiment, the resource usage data is used to characterize the service capability attribute of the second account. Optionally, the service capability attribute has 3 sub-attributes, namely (1) user salary capability, (2) enterprise type or payroll type, (3) user stability.

The user salary capability refers to an analysis result of the salary level of the historical first account served by the second account, and may be specifically represented by a numerical value, for example, a numerical value corresponding to an average salary. For example, in the job hunting application, the average monthly salary of all users already served by the broker (i.e., users involved in all completed demands) pointed to by the second account is counted periodically (every 3 months/every 6 months/every 1 year), and only the working users are counted, because there is no salary in the user's off-duty status, which affects the accuracy of the average salary statistical analysis. Alternatively, there are 2 ways: mode 1: for each user, counting the average monthly salary of the user during the period of employment, and then carrying out secondary average on the average monthly salaries of all users; mode 2: for each user, the salaries of the last month (month of full work) at the current time point (statistical time point) are obtained, and then the monthly salaries of all users are averaged.

The enterprise type or work category type refers to an enterprise type or work category type that is good for the user of the account corresponding to the second account or has a work opportunity. For example, in the job hunting application, all users already served by the broker corresponding to the second account (i.e., users involved in all demands completed by the broker) are tracked, and the type of enterprise or work category where the broker is located is counted, and the final counting result may be 2 types: 1. the number of users served by the broker for different business types or job types; 2. the top 3 ranked in the above numbers are the types of businesses or work categories with which the broker is most familiar.

The user stability refers to the resource usage stability of the historical first account served by the second account. For example, in a job hunting type application, the user stability may be reflected from 3 angles, the percentage of departure, the number of days of employment, or the number of months of employment. And regularly (every 3 months/every 6 months/every 1 year), tracking all users already served by the broker corresponding to the second account (namely, users involved in all demands completed by the broker), and counting the average value. Firstly, the stability of the user is judged through the working days, the user can be judged according to the punching records of the staff, and if an effective punching record of going to work and going to work is available on a certain day, the user is considered to be working on the same day. And secondly, judging the stability of the user through the number of months/the percentage of leaving. Alternatively, there are 3 methods: 1. the judgment can be carried out in a salary record mode, namely if the salary record in the current month of the enterprise after 3 months does not have the record of the employee, the employee can be considered to be out of work, otherwise, the employee is in work; 2. the employee can be checked into the card record, if the number of times of checking the card in the current month exceeds a certain threshold value, the employee is considered to be on duty in the current month, and the enterprise can recover the employee card or clear the employee record from the system after leaving the duty; 3. and the enterprise can also directly give the job leaving rate of the employees and judge the job leaving rate of the employees.

Optionally, the current working status indicates whether the second account currently has an unprocessed requirement, and may be in working or idle.

Step 240, determining a target account matched with the first account from the second account set according to the historical service information and the second service demand information.

And matching the historical service information corresponding to the target account with the second service requirement information.

In an exemplary embodiment, the historical service information includes response behavior information from which a match may be made. As shown in FIG. 4, the implementation of step 240 includes the following steps (241-242).

Step 241, determining the second account whose response behavior information meets the response behavior condition in the second account set as a candidate second account.

The response behavior information includes response time interval levels such as excellent, good, and medium. The condition that the response behavior is satisfied may be that the response time interval level is a preset level, or the response time interval is in a preset time interval, which is not limited in the embodiment of the present application.

Step 242, determining a target account matched with the first account from the candidate second accounts based on the second service demand information and the historical service information corresponding to the candidate second accounts.

In an exemplary embodiment, the second service requirement information further includes server characteristics, which may be matched in conjunction with the server characteristics. As shown in fig. 5, the step 242 may alternatively be implemented by the step (242A).

Step 242A, determining a target account matching the first account from the candidate second accounts based on the historical service information corresponding to the server features and the candidate second accounts.

In one possible embodiment, the historical service information includes account user characteristics. Optionally, when the response time interval levels of some second accounts are consistent, the account user characteristics corresponding to the candidate second accounts may be compared with the server characteristics, so as to obtain second accounts corresponding to account user characteristics matched with the server characteristics, and the second accounts are used as target accounts.

In an exemplary embodiment, the historical service information includes account user characteristics. Accordingly, as shown in FIG. 6, the implementation of the step 242A includes the following steps (242A 1-242A 2).

In step 242a1, a user characteristic matching degree is determined based on the characteristics of the service provider and the account user characteristics corresponding to the candidate second account.

The user feature matching degree is used for representing the similarity between the characteristics of the server set by the first account and the account user characteristics corresponding to the candidate second account, and the user feature matching degree and the similarity are in positive correlation. Optionally, if the characteristics of the server are matched with the characteristics of the account user corresponding to the candidate second account, the matching degree of the characteristics is recorded as 1, and if the characteristics of the server are not matched with the characteristics of the account user corresponding to the candidate second account, the matching degree of the characteristics is recorded as 0. Alternatively, the user feature matching degree may also be a continuous numerical value, which is not limited in the embodiment of the present application.

In step 242a2, a target account is determined from the candidate second accounts based on the matching degree of the user characteristics.

And according to the user feature matching degree, performing descending arrangement on the candidate second accounts. Optionally, the first candidate second account after the descending order is taken as the target account.

In a possible embodiment, the historical service information further includes resource usage data and request processing data. The resource use data refers to data generated by using the resource information corresponding to the second account by the user pointed by the first account. The request processing data refers to data of the second account processing request, such as the number of processing requests.

Accordingly, as shown in FIG. 7, the above step 242A2 can be alternatively implemented by the following steps (242A 3-242A 6).

Step 242a3, determining the resource stability corresponding to the candidate second account based on the resource usage data.

The resource usage data includes usage time of the account resource corresponding to the second account used by other accounts, the usage time is positively correlated with the resource stability, and the longer the usage time is, the higher the resource stability is. In a specific application scenario, the account resource in the second account is a work resource corresponding to the recruitment information, the user corresponding to the first account receives the work resource provided by the second account, the time for engaging in the work corresponding to the work may be understood as the usage time, and the resource stability may be determined according to a certain mapping relationship, which is not limited in the embodiment of the present application.

In one example, the resource stability is determined by specific resource usage data, such as a broker good business stability factor, and a higher or equal average counts the resource stability as 1, otherwise it is 0.5. The resource stability may also be a broker adept type/enterprise type (1 consistent with the requested resource type, 0 inconsistent with the requested resource type) "or a" broker service user salary level (higher than or equal to 1 average, 0.5 lower than average) ", which is not limited in this embodiment of the present application.

Step 242a4, based on the request processing data, determines a request processing index corresponding to the candidate second account.

The request processing index is used for representing the request processing amount corresponding to the candidate second account.

Optionally, the request processing data includes a request processing amount of the second account processing resource configuration request. Optionally, the request processing amount is positively correlated with the request processing index, and the larger the request processing amount is, the larger the processing pressure of the second account is, the higher the request processing index is, and the lower the account vacancy is. Therefore, the request processing index corresponding to the candidate second account can be determined through the request processing data.

The request processing index may be a current distributed demand coefficient of the second account, and if the number of the current distributed information service requests of the second account is greater than or equal to the average number, the request processing index is marked as 0.5, otherwise, the request processing index is marked as 1.

Step 242a5, based on the preset first weight, second weight and third weight, performing weighted summation on the user feature matching degree, the resource stability and the request processing index to obtain a service behavior score corresponding to the candidate second account.

The preset first weight, the second weight and the third weight respectively correspond to the user feature matching degree, the resource stability and the weight of the request processing index. Optionally, the sum of the preset first weight, the preset second weight and the preset third weight is 1.

Optionally, the preset first weight, the preset second weight and the preset third weight are 0.3, 0.3 and 0.4, respectively. The service behavior is classified into a user feature matching degree 0.3+ a resource stability degree 0.3+ a request processing index 0.4.

Step 242a6, determine the target account from the candidate second accounts according to the service behavior score.

The second account with higher service behavior is preferentially distributed; if a plurality of service behaviors are divided into the same second account, the second account which is accessed to the system and has later time or less processed information service requests is preferentially distributed, and if the service behaviors are still the same, the second account is evenly distributed.

Step 250, sending an information service request to the client corresponding to the target account to acquire feedback information corresponding to the information service request.

In a possible implementation manner, the service requirement information corresponding to the information service request is sent to the target account in a requirement list form. The demand list refers to information generated after a user operates in the system, and is pushed to a client corresponding to the target account in a list mode. Optionally, the target account is an electronic account held by the broker, and the requirement list with the user requirement is pushed to the client corresponding to the target account to remind the corresponding broker to process the relevant task, so as to generate corresponding feedback information.

Optionally, a communication connection between the client corresponding to the target account and the client corresponding to the first account is established, so that the client corresponding to the target account sends feedback information to the client corresponding to the first account, for example, the recruitment information.

To sum up, in the technical scheme provided in the embodiment of the present application, the received information service request of the first account is analyzed to obtain the first service requirement information and the second service requirement information carried in the information service request, the second account whose service position matches the target position information in the first service requirement information is screened to obtain the second account set, and the target account whose historical service information matches the second service requirement information is found from the second account set, and finally the service request is distributed to the target account to obtain the corresponding feedback information.

Referring to fig. 8, a flowchart of a request processing method according to an embodiment of the present application is shown. The method can be applied to a computer device, which refers to an electronic device with data calculation and processing capabilities, for example, the execution subject of each step can be the server 20 in the application program running environment shown in fig. 1. The method can comprise the following steps (801-809).

Step 801, receiving an information service request of a first account.

The information service request includes first service requirement information and second service requirement information, and the first service requirement information includes target location information.

Step 802, a second account set matched with the target position information is obtained.

Step 803, obtaining the historical service information corresponding to each second account.

Step 804, acquiring resource information corresponding to each second account.

The resource information may be resource information required for providing a service for the first account, or resource information requested by the first account. Optionally, the resource information includes recruitment resource information. In some embodiments, each second account may have different resource information or the same resource information.

Step 805, determining target resource information matched with the resource demand information.

The target resource information is resource information matched with the resource demand information. For example, if the job type, the salary and the resource demand information in one piece of recruiting resource information are all matched, the recruiting resource information can be determined as the target resource information.

Step 806, determining at least one second account corresponding to the target resource information as a candidate second account.

And determining at least one second account having the calling authority for the target resource information as a candidate second account.

In step 807, a target account matched with the first account is determined from the candidate second accounts based on the second service requirement information and the historical service information corresponding to the candidate second accounts.

Optionally, the implementation process of step 240 includes steps (804-807).

In a possible implementation manner, the resource requirement information includes resource acquisition time limit information and request resource type information. Accordingly, as shown in fig. 9, the above step 805 may be alternatively implemented by the following step 805 a.

Step 805a, determining target resource information matched with both the resource acquisition time limit information and the request resource type information.

The explanation of the above resource acquisition time limit information and the request resource type information has been explained in the above embodiments, and is not described herein again.

In step 805a, the target resource information needs to satisfy the requirements of the resource acquisition time limit information and the request resource type information at the same time.

Accordingly, as shown in fig. 9, before the step 806, the following step 809 can be further included.

Step 809, determining the response time data corresponding to each second account.

Accordingly, as shown in FIG. 9, the above step 806 can be alternatively implemented by the following step 806 a.

Step 806a, determining at least one second account corresponding to the target resource information and having response time data meeting a preset response time condition as a candidate second account.

Step 808, sending an information service request to the client corresponding to the target account to obtain feedback information corresponding to the information service request.

The following are embodiments of the apparatus of the present application that may be used to perform embodiments of the method of the present application. For details which are not disclosed in the embodiments of the apparatus of the present application, reference is made to the embodiments of the method of the present application.

Referring to fig. 10, a block diagram of a request processing device according to an embodiment of the present application is shown. The device has the function of realizing the request processing method, and the function can be realized by hardware or by hardware executing corresponding software. The device can be a computer device and can also be arranged in the computer device. The apparatus 1000 may include: the system comprises a request receiving module 1010, an account number obtaining module 1020, a history information obtaining module 1030, a target account number determining module 1040 and a request distributing module 1050.

A request receiving module 1010, configured to receive an information service request of a first account, where the information service request includes first service requirement information and second service requirement information, and the first service requirement information includes target location information;

an account acquiring module 1020, configured to acquire a second account set matched with the target location information, where a service location corresponding to each second account in the second account set corresponds to a target location indicated by the target location information;

a history information obtaining module 1030, configured to obtain history service information corresponding to each second account;

a target account determining module 1040, configured to determine, according to the historical service information and the second service demand information, a target account matched with the first account from the second account set, where the historical service information corresponding to the target account is matched with the second service demand information;

the request allocating module 1050 is configured to send the information service request to the client corresponding to the target account to obtain feedback information corresponding to the information service request.

In an exemplary embodiment, the second service requirement information includes resource requirement information, and the target account determining module 1040 includes:

a resource obtaining unit, configured to obtain resource information corresponding to each second account;

the resource determining unit is used for determining target resource information matched with the resource demand information;

a candidate account determining unit, configured to determine at least one second account corresponding to the target resource information as a candidate second account;

and the target account determining unit is used for determining a target account matched with the first account from the candidate second accounts based on the second service demand information and the historical service information corresponding to the candidate second accounts.

In an exemplary embodiment, the resource requirement information includes resource acquisition time limit information and request resource type information, and the resource determining unit is further configured to:

determining target resource information matched with both the resource acquisition time limit information and the request resource type information;

the history information obtaining module 1030 includes:

determining response time data corresponding to each second account;

the candidate account determining unit is configured to:

and determining at least one second account, corresponding to the target resource information and with response time data meeting a preset response time condition, as the candidate second account.

In an exemplary embodiment, the historical service information includes response behavior information, and the candidate account determination unit is further configured to:

determining a second account in the second account set, of which the response behavior information meets the response behavior condition, as a candidate second account;

the target account determining unit is further configured to determine a target account matched with the first account from the candidate second accounts based on the second service demand information and historical service information corresponding to the candidate second accounts.

In an exemplary embodiment, the second service requirement information further includes a server characteristic, and the target account determining unit is specifically configured to:

and determining a target account matched with the first account from the candidate second accounts based on the historical service information corresponding to the server characteristics and the candidate second accounts.

In an exemplary embodiment, the historical service information includes account user characteristics, and the target account determination unit includes: a feature matching subunit and a target account number determining subunit.

The characteristic matching subunit is used for determining the user characteristic matching degree based on the characteristics of the server and the account user characteristics corresponding to the candidate second account;

and the target account determining subunit is used for determining the target account from the candidate second accounts based on the user characteristic matching degree.

In an exemplary embodiment, the historical service information further includes resource usage data and request processing data, and the target account determining unit further includes: the system comprises a stability determining subunit, a request processing index determining subunit and a service behavior score calculating subunit.

A stability determining subunit, configured to determine, based on the resource usage data, a resource stability corresponding to the candidate second account;

a request processing index determining subunit, configured to determine, based on the request processing data, a request processing index corresponding to the candidate second account, where the request processing index is used to characterize a request processing amount corresponding to the candidate second account;

the service behavior score calculating subunit is configured to perform weighted summation on the user feature matching degree, the resource stability degree, and the request processing index based on a preset first weight, a preset second weight, and a preset third weight, so as to obtain a service behavior score corresponding to the candidate second account;

the target account determining subunit is further configured to determine the target account from the candidate second accounts according to the service behavior score.

In an exemplary embodiment, the historical service information includes account user characteristics, and the historical information obtaining module 1030 includes: the device comprises a user information acquisition unit and a user characteristic determination unit.

And the user information acquisition unit is used for acquiring account user information corresponding to each second account, wherein the account user information comprises at least one of a character tag, a message corpus and an operation behavior log.

And the user characteristic determining unit is used for determining the account user characteristics corresponding to each second account based on the account user information.

In an exemplary embodiment, the account number obtaining module 1020 includes: an area determining unit and an area account determining unit.

And the area determining unit is used for determining a target service area corresponding to the target position information.

And the area account determining unit is used for generating the second account set based on at least one service position if at least one service position exists in the target service area.

In an exemplary embodiment, the target service area is an area where the current login location of the first account is located, and the area account determining unit includes: a service position determining subunit and a service account number determining subunit.

And the service position determining subunit is used for determining a target service position corresponding to the current login position from at least one service position if at least one service position exists in the target service area.

And the service account determining subunit is configured to use at least one second account corresponding to the target service location as the second account set.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the functional modules is illustrated, and in practical applications, the functions may be distributed by different functional modules according to needs, that is, the internal structure of the apparatus may be divided into different functional modules to implement all or part of the functions described above. In addition, the apparatus and method embodiments provided by the above embodiments belong to the same concept, and specific implementation processes thereof are described in the method embodiments for details, which are not described herein again.

Referring to fig. 11, fig. 11 is a block diagram illustrating a computer device according to an embodiment of the present application, the computer device including at least one processor and a memory communicatively coupled to the at least one processor; the memory stores instructions executable by at least one processor, and the at least one processor implements the request processing method by executing the instructions stored in the memory, and the apparatus may participate in forming or including the device or system provided by the embodiments of the present application.

As shown in fig. 11, the apparatus 100 may include one or more (shown as 102a, 102b, … …, 102 n) processors 102 (the processors 102 may include, but are not limited to, a processing device such as a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. Besides, the method can also comprise the following steps: a display, an input/output interface (I/O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of the I/O interface), a network interface, a power source, and/or a camera. It will be understood by those skilled in the art that the structure shown in fig. 11 is only an illustration and is not intended to limit the structure of the electronic device. For example, device 100 may also include more or fewer components than shown in FIG. 11, or have a different configuration than shown in FIG. 11.

It should be noted that the one or more processors 102 and/or other data processing circuitry described above may be referred to generally herein as "data processing circuitry". The data processing circuitry may be embodied in whole or in part in software, hardware, firmware, or any combination thereof. Further, the data processing circuitry may be a single, stand-alone processing module, or incorporated in whole or in part into any of the other elements in the device 100 (or mobile device). As referred to in the embodiments of the application, the data processing circuit acts as a processor control (e.g. selection of a variable resistance termination path connected to the interface).

The memory 104 may be used to store software programs and modules of application software, such as program instructions/data storage devices corresponding to the methods described above in the embodiments of the present application, and the processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, so as to implement the aforementioned corpus processing model training method. The memory 104 may include high speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, the memory 104 may further include memory located remotely from the processor 102, which may be connected to the device 100 over a network. Examples of such networks include, but are not limited to, the internet, intranets, local area networks, mobile communication networks, and combinations thereof.

The transmission device 106 is used for receiving or transmitting data via a network. Specific examples of such networks may include wireless networks provided by the communication provider of the device 100. In one example, the transmission device 106 includes a network adapter (NIC) that can be connected to other network devices through a base station so as to communicate with the internet. In one example, the transmission device 106 can be a Radio Frequency (RF) module, which is used for communicating with the internet in a wireless manner.

The display may be, for example, a touch screen type Liquid Crystal Display (LCD) that may enable a user to interact with a user interface of the device 100 (or mobile device).

In an exemplary embodiment, a computer readable storage medium is provided, in which at least one instruction, at least one program, a set of codes, or a set of instructions is stored, which is loaded and executed by a processor to implement the above request processing method.

It should be understood that reference to "a plurality" herein means two or more. "and/or" describes the association relationship of the associated objects, meaning that there may be three relationships, e.g., a and/or B, which may mean: a exists alone, A and B exist simultaneously, and B exists alone. The character "/" generally indicates that the former and latter associated objects are in an "or" relationship. In addition, the step numbers described herein only exemplarily show one possible execution sequence among the steps, and in some other embodiments, the steps may also be executed out of the numbering sequence, for example, two steps with different numbers are executed simultaneously, or two steps with different numbers are executed in a reverse order to the order shown in the figure, which is not limited by the embodiment of the present application.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for processing a request, the method comprising:

acquiring historical service information corresponding to each second account;

2. The method of claim 1, wherein the second service requirement information comprises resource requirement information, and wherein determining the target account from the second account set that matches the first account according to the historical service information and the second service requirement information comprises:

acquiring resource information corresponding to each second account;

determining target resource information matched with the resource demand information;

determining at least one second account corresponding to the target resource information as a candidate second account;

and determining a target account matched with the first account from the candidate second accounts based on the second service demand information and the historical service information corresponding to the candidate second accounts.

3. The method according to claim 2, wherein the resource requirement information includes resource acquisition time limit information and request resource type information, and the determining target resource information matching the resource requirement information includes:

before determining at least one second account corresponding to the target resource information as a candidate second account, the method further includes:

determining response time data corresponding to each second account;

the determining at least one second account corresponding to the target resource information as a candidate second account includes:

4. The method of claim 1, wherein the historical service information includes response behavior information, and wherein determining the target account from the second account set that matches the first account according to the historical service information and the second service requirement information comprises:

5. The method of any one of claims 2 to 4, wherein the second service requirement information further includes a characteristic of a server, and the determining a target account matching the first account from the candidate second accounts based on the second service requirement information and historical service information corresponding to the candidate second accounts comprises:

6. The method of claim 5, wherein the historical service information includes account user characteristics, and wherein determining the target account matching the first account from the candidate second accounts based on the historical service information corresponding to the candidate second accounts based on the account user characteristics comprises:

determining a user feature matching degree based on the server features and account user features corresponding to the candidate second accounts;

and determining the target account number from the candidate second account numbers based on the user characteristic matching degree.

7. The method of claim 6, wherein the historical service information further comprises resource usage data and request processing data, and wherein determining the target account from the candidate second accounts that matches the first account based on the historical service information corresponding to the candidate second accounts by the server characteristic further comprises:

determining the resource stability corresponding to the candidate second account based on the resource usage data;

determining a request processing index corresponding to the candidate second account based on the request processing data, wherein the request processing index is used for representing the request processing amount corresponding to the candidate second account;

based on a preset first weight, a preset second weight and a preset third weight, carrying out weighted summation on the user feature matching degree, the resource stability and the request processing index to obtain a service behavior score corresponding to the candidate second account;

and determining the target account from the candidate second accounts according to the service behavior score.

8. The method according to claim 5, wherein the historical service information includes account user characteristics, and the obtaining the historical service information corresponding to each second account includes:

acquiring account user information corresponding to each second account, wherein the account user information comprises at least one of a character tag, a message corpus and an operation behavior log;

and determining account user characteristics corresponding to the second accounts based on the account user information.

9. The method of claim 1, wherein obtaining the second set of accounts matching the target location information comprises:

determining a target service area corresponding to the target location information;

and if at least one service position exists in the target service area, generating the second account set based on the at least one service position.

10. The method of claim 9, wherein the target service area is an area where a current login location of the first account is located, and if at least one service location exists in the target service area, generating the second account set based on the at least one service location comprises:

if at least one service position exists in the target service area, determining a target service position corresponding to the current login position from the at least one service position;

and taking at least one second account corresponding to the target service position as the second account set.

11. A request processing apparatus, characterized in that the apparatus comprises:

12. A computer device comprising a processor and a memory, wherein at least one instruction or at least one program is stored in the memory, and the at least one instruction or the at least one program is loaded and executed by the processor to implement the request processing method according to any one of claims 1 to 10.

13. A computer readable storage medium having stored therein at least one instruction or at least one program, the at least one instruction or the at least one program being loaded and executed by a processor to implement the request processing method of any one of claims 1 to 10.