CN115499438A - A task allocation method, device, electronic equipment and storage medium - Google Patents

Abstract

The present disclosure relates to a task assignment method, device, electronic equipment, and storage medium, including: acquiring multimedia data to be processed and account behavior data corresponding to the multimedia data; acquiring the current identity information of the target account; according to the current identity information and The historical identity information of the target account obtained in advance determines the identity category of the target account; when the task push request of the target account is received, according to the identity category, the target corresponding to the target account is determined task, assigning the target task to the target account. In this way, different tasks can be assigned to accounts of different identity categories according to the different identity categories of the accounts, that is, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks and improving the accuracy of task assignment. Flexibility, thereby reducing the likelihood that an account will perform the same task repeatedly.

Description

A task allocation method, device, electronic equipment and storage medium

technical field

The present disclosure relates to the Internet field, and in particular, to a task allocation method, device, electronic equipment, and storage medium.

Background technique

At present, there are more and more accounts on the Internet platform, and accounts can be divided into different categories according to the activity and usage of the accounts. It can be understood that different types of accounts have different characteristics, and by classifying accounts and providing different services for different types of accounts in a targeted manner, personalized experience can be provided for users.

In some scenarios, the same account can be converted between different categories by performing an identity conversion task. However, in the prior art, the identity conversion task is relatively simple, and each time an account performs identity conversion, it needs to repeatedly execute the same Tasks, the flexibility of task assignment is poor.

Contents of the invention

The present disclosure provides a task allocation method, device, electronic equipment and storage medium, so as to at least solve the problems in the related art that the task of identity conversion is relatively single and the flexibility of task allocation is poor. The disclosed technical scheme is as follows:

According to a first aspect of an embodiment of the present disclosure, a task allocation method is provided, including:

Obtain the current identity information of the target account;

determining the identity category of the target account according to the current identity information and the pre-acquired historical identity information of the target account;

When a task pushing request of the target account is received, according to the identity category, the target task corresponding to the target account is determined, and the target task is assigned to the target account.

Optionally, the acquiring the current identity information of the target account includes:

Obtain the current identity information of the target account at preset time intervals; or,

Obtain the current identity information sent by the client after the identity of the target account is changed.

Optionally, the identity information includes an identity category and an update time of the identity category, and the identity category of the target account is determined according to the current identity information and the pre-acquired historical identity information of the target account ,Also includes:

When the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is less than a preset period, determine that the identity category of the target account is the historical identity information Identity category in .

Optionally, when the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is not less than a preset period, the method further includes:

According to a preset category rule, determine a high-level identity category among the identity categories in the current identity information and the identity categories in the historical identity information as the identity category of the target account.

Optionally, after assigning the target task to the target account, further comprising:

monitoring the execution status of the target account on the target task;

When the target account completes the target task, push the virtual resource corresponding to the identity category to the target account.

Optionally, before pushing the virtual resource corresponding to the identity category to the target account, the method further includes:

Sending the current identity information of the target account and the task information of the target task to the risk control platform;

In response to the risk control hit information returned by the risk control platform, push the risk control hit information to the target account.

Optionally, after determining the identity category of the target account according to the current identity information and the pre-acquired historical identity information of the target account, the method further includes:

displaying task information of candidate tasks matching the identity category of the target account in response to the target account's access operation on the preset page;

Execute any candidate task in response to the target account's task push request for any candidate task, and the task push request is generated based on the target account's selection operation on the task information of any candidate task.

According to a second aspect of an embodiment of the present disclosure, a task allocation device is provided, including:

an acquisition unit configured to acquire current identity information of the target account;

The determining unit is configured to determine the identity category of the target account according to the current identity information and the pre-acquired historical identity information of the target account;

The allocating unit is configured to determine the target task corresponding to the target account according to the identity category, and allocate the target task to the target account when the task push request of the target account is received.

Optionally, the acquiring unit is configured to execute:

Obtain the current identity information of the target account at preset time intervals; or,

Obtain the current identity information sent by the client after the identity of the target account is changed.

Optionally, the identity information includes an identity category and an update time of the identity category, and the determination unit is further configured to execute:

When the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is less than a preset period, determine that the identity category of the target account is the historical identity information Identity category in .

Optionally, the determining unit is further configured to execute:

When the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is not less than a preset period, determine the current identity information in accordance with preset category rules The identity category of the target account and the higher identity category among the identity categories in the historical identity information are used as the identity category of the target account.

Optionally, the device also includes:

The push unit is further configured to monitor the execution status of the target account on the target task; when the target account completes the target task, push the virtual resource corresponding to the identity category to the target account.

Optionally, the push unit is also configured to execute:

Sending the current identity information of the target account and the task information of the target task to the risk control platform;

In response to the risk control hit information returned by the risk control platform, push the risk control hit information to the target account.

Optionally, the device also includes:

The receiving unit is configured to display task information of candidate tasks matching the identity category of the target account in response to the target account’s access operation on the preset page; A task push request for executing any of the candidate tasks, where the task push request is generated based on the target account's selection operation on the task information of any of the candidate tasks.

According to a third aspect of the embodiments of the present disclosure, there is provided an electronic task distribution device, including:

processor;

memory for storing said processor-executable instructions;

Wherein, the processor is configured to execute the instructions, so as to implement any one of the task allocation methods described above.

According to the fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by the processor of the task distribution electronic device, the task distribution electronic device can execute the Any one of the task assignment methods.

According to a fifth aspect of the embodiments of the present disclosure, a computer program product is provided, including computer programs/instructions, and when the computer programs/instructions are executed by a processor, the task allocation method described in any one of the above items is implemented.

The technical solutions provided by the embodiments of the present disclosure bring at least the following beneficial effects:

Obtain the multimedia data to be processed and the account behavior data corresponding to the multimedia data; obtain the current identity information of the target account; determine the identity of the target account according to the current identity information and the pre-acquired historical identity information of the target account category: when the task push request of the target account is received, according to the identity category, determine the target task corresponding to the target account, and assign the target task to the target account.

In this way, different tasks can be assigned to accounts of different identity categories according to the different identity categories of the accounts, that is, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks and improving the accuracy of task assignment. Flexibility, reducing the likelihood that an account will perform the same task repeatedly.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure.

Description of drawings

The accompanying drawings here are incorporated into the specification and constitute a part of the specification, show embodiments consistent with the disclosure, and are used together with the description to explain the principle of the disclosure, and do not constitute an improper limitation of the disclosure.

Fig. 1 is a flow chart of a task allocation method according to an exemplary embodiment.

Fig. 2 is a system schematic diagram of a task allocation method according to an exemplary embodiment.

Fig. 3 is a system flowchart of a task allocation method according to an exemplary embodiment.

Fig. 4 is a block diagram of a device for assigning tasks according to an exemplary embodiment.

Fig. 5 is a block diagram showing an electronic device for task assignment according to an exemplary embodiment.

Fig. 6 is a block diagram of an apparatus for task assignment according to an exemplary embodiment.

detailed description

In order to enable ordinary persons in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below in conjunction with the accompanying drawings.

It should be noted that the terms "first" and "second" in the description and claims of the present disclosure and the drawings are used to distinguish similar objects, and not necessarily used to describe a specific order or sequence . It is to be understood that the data so used are interchangeable under appropriate circumstances such that the embodiments of the disclosure described herein can be practiced in sequences other than those illustrated or described herein. The implementations described in the following exemplary examples do not represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatuses and methods consistent with aspects of the present disclosure as recited in the appended claims.

Fig. 1 is a flow chart showing a method for assigning tasks according to an exemplary embodiment. As shown in Fig. 1 , the method for assigning tasks includes the following steps.

In step S11, the current identity information of the target account is obtained.

Generally, accounts on the Internet platform have different identity categories, and accounts of different identity categories have different characteristics. Therefore, targeted treatment of accounts of different identity categories can enrich user experience.

In this step, the server can obtain the current identity information of the target account from the client or a preset database, wherein the current identity information is determined according to the judgment result of the client on the identity of the target account, and the identity information includes but is not limited to The identity category of the target account and the update time of the identity category.

In an implementation manner, the step of obtaining the current identity information of the target account may include:

The current identity information of the target account is obtained according to a preset time interval, for example, every 24 hours or 1 hour, the server obtains the current identity information of the target account from the client once. In this way, the server can regularly obtain the current identity information of the target account according to its own needs or user settings, so as to maintain the stability of the system.

Or, obtain the current identity information sent by the client after the identity of the target account is changed, that is, whenever the client determines that the identity of the target account changes, it sends the updated current identity information of the target account to the server. In this way, the server only needs to synchronize the identity of the updated target account, thereby saving computing resources of the server. For example, when the target account is a Class A account at point T, and at T+15, the target account is determined to be a Class B account by the client, then the client can transfer the Class B account of the target account at T+16 The account identity is synchronized to the server.

In step S12, the identity category of the target account is determined according to the current identity information and the pre-acquired historical identity information of the target account.

In this disclosure, the historical identity information of the target account is also stored in the server, and the historical identity information is used to indicate the identity maintained by the server for the target account before the current time. That is to say, the historical identity information and the current identity information usually conflict. Therefore, the server needs to synchronize and update the identity information of the target account according to the current identity information and the historical identity information.

In one implementation, the identity information includes the identity category and the update time of the identity category, then, according to the current identity information and the pre-acquired historical identity information of the target account, the step of determining the identity category of the target account may include: When the difference between the update time in the identity information and the update time in the historical identity information is less than a preset period, determine that the identity category of the target account is the identity category in the historical identity information. Wherein, the preset period may be set according to system requirements, which is not limited in the present disclosure.

That is to say, if the target account remains in the identity category corresponding to the historical identity information for less than the preset period, then the identity category of the target account will remain unchanged and will not be updated with the identity category in the current identity information , that is, the duration of the target account in each identity category is not less than a preset period. In this way, the rationality of identity conversion of each account in the system can be effectively maintained, and the situation of abnormal account identity conversion caused by misjudgment by the client can be reduced.

For example, if the preset period is 30 days, then if the target account is within the 30-day period of identity category A, when the new identity category of the target account is obtained, there is no need to save the new identity of the target account, the target The account is still in status category A.

In addition, when the difference between the update time of the current identity information and the update time of the historical identity information is not less than the preset period, this step also includes: determining the identity category in the current identity information and the historical identity information according to the preset category rules. The high-level identity category in the identity category in the message is used as the identity category of the target account. Wherein, the preset class rule is used to indicate the priority order of each identity class, which can be specifically set according to system requirements, which is not limited in the present disclosure.

That is to say, if the identity category of the target account in the historical identity information has been maintained for longer than the preset period, then, if the current identity information of the target account is obtained, the target account has multiple matching identity categories, and the server The identity category of the target account needs to be updated. According to the preset category rules, the identity category of the highest category is determined from the multiple identity categories that the target account meets as the updated identity category of the target account. Then, the target account can enter the update more advanced activities later.

In this way, according to the preset category rules, the server can realize the judgment on the identity category of the target account and maintain the uniqueness of the identity category of the target account in the system when there are multiple matching identity categories for the target account.

In step S13, when the task push request of the target account is received, the target task corresponding to the target account is determined according to the identity category, and the target task is assigned to the target account.

In this disclosure, accounts of different identity categories can perform different tasks. Therefore, after determining the identity category of the target account, the server can determine the target account according to the identity category of the target account in response to the task push request of the target account. corresponding target tasks, and assign target tasks to target accounts, thereby enriching the diversity of account tasks.

Among them, the target task can be displayed at a fixed position on the preset page. After receiving the client’s display instruction for the target task, the target task page can be displayed for the client. If the target account is currently in identity category A, other identities cannot be accessed. The task corresponding to the category. In this way, the task form has a guiding and promoting effect on the execution of the corresponding target task of the account, and will have a positive impact on improving the task execution rate.

In one implementation, the server may display task information of candidate tasks matching the identity category of the target account in response to the target account's access operation on the preset page; in response to the target account's task push request for any candidate task, Executing any candidate task, wherein the task push request is generated based on the target account's selection operation of the task information of any candidate task.

That is to say, the task information of each candidate task can be displayed on the preset page. By accessing the preset page, the target account can select the target task from multiple candidate tasks matching its own identity category, and send the target task to the server. The task push request for the selected target task. In this way, for the user, the target task to be performed can be independently selected, the task allocation method is more flexible, and the user experience is better.

In some scenarios, the target task can be an account identity conversion task, that is, as the number of target tasks performed by the target account increases, the identity category of the target account will also change accordingly. The account activity in the system has a promoting effect.

In one implementation, after assigning the target task to the target account, the disclosure further includes the following steps: monitoring the execution status of the target account on the target task; when the target account completes the target task, push the virtual resource corresponding to the identity category to the target account.

That is to say, corresponding virtual resources can be configured for each target task as feedback, and the configured virtual resources correspond to the identity category of the target account. After the target account completes the target task, the virtual resources corresponding to the identity category of the target account The matched virtual resource is pushed to the target account, wherein the virtual resource can be virtual currency or virtual goods, etc., without specific limitation.

For example, if the target task is to configure 400 phones, and both Type A accounts and Type B accounts correspond to the target task, then after the Type A account completes the task of configuring 400 phones, it can trigger the corresponding number of virtual For the goods distribution operation, after the B-type account completes the task of configuring the 400 phone, the virtual goods distribution operation corresponding to the B-type account can be triggered.

In this way, different task plans and rewards are matched according to the identity of the account, thereby enriching the diversity of account tasks, reducing the possibility of the account performing the same task repeatedly, and also helping to improve the enthusiasm of users to perform tasks.

Among them, before pushing the virtual resource corresponding to the identity category to the target account, it is also possible to: send the current identity information of the target account and the task information of the target task to the risk control platform; respond to the risk control hit information returned by the risk control platform, Push the risk control hit information to the target account.

That is to say, before issuing virtual resources to the target account, the current identity information of the target account and the task information of the target task can be sent to the risk control platform. And whether there is any abnormality in the target task, so as to realize the risk control of the target account and the target task, for example, whether the identity of the target account is changed too quickly, or whether the target task is a repeated task of the target account, and so on. If the risk control platform determines that the target account and the target task are at risk, it can return the risk control hit information to the server, and then the server pushes the risk control hit information to the target account to prompt the server and the client to perform corresponding operations, reducing The loss caused by the account abnormality to the system.

This scheme can be applied to an interactive system composed of a server and a client. As shown in Figure 2, it is a schematic diagram of the system of this scheme. Among them, the account can obtain and start the task from the task system through the kafka mechanism; the task system can obtain user data from the user database, and the user database can be MySQL (relational database management system) database or redis (REmoteDIctionary Server , remote dictionary service) database, user data includes task snapshots, user information, and activity information, etc. The task system can also obtain virtual resources from the reward database, which can be stored in the redis database; the task system updates each The task execution status of the account and the completion of the task, and the task information is fed back to the risk control platform for evaluation. After the evaluation of the risk control platform is passed, the traffic platform will issue rewards to the account. If the evaluation of the risk control platform fails, then , the account can be notified through SMS and private message platforms; at the same time, the perf management monitoring can be performed through the Grafana program to display user data and virtual resources. In addition, the task system can obtain task completion event messages through the Kafka mechanism. The task completion event messages can correspond to a variety of different tasks, such as posting videos, starting live broadcasts, watching videos, smartphones, and identity authentication. There is no specific limit .

As shown in Figure 3, it is the system flow chart of this scheme. The account can be authenticated or bound through the service number. After the authentication or binding is successful, the access logic is verified, and the task record to be opened is inserted into the server interface. After the server determines the account identity type, it notifies the user that they can participate in the task. Then, the account can visit the task page, initialize the task, execute the corresponding task, and give feedback to the server. The server updates the task status of the completed task in the task center according to the feedback from the account. Furthermore, after the account completes the task, it sends a task completion message to the server, and the server updates the task completion message to the task center. After the task center monitors the task completion message, it determines that the task has been completed, and the risk control center evaluates it. If the evaluation fails, the server will send a hit risk control notification to the account. If the evaluation is passed, the server can request the distribution of virtual resources to the traffic center. The virtual resources can be traffic coupons. Update the display data of the service account.

It can be seen from the above that the technical solutions provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to different identity categories of accounts, that is, customize different tasks for accounts of different identity categories, thereby enriching The diversity of account identity conversion tasks improves the flexibility of task allocation, thereby reducing the possibility of accounts performing the same task repeatedly.

Fig. 4 is a block diagram of a task allocation device according to an exemplary embodiment, and the device includes:

The acquiring unit 201 is configured to acquire the current identity information of the target account;

The determining unit 202 is configured to determine the identity category of the target account according to the current identity information and the pre-acquired historical identity information of the target account;

The allocating unit 203 is configured to determine the target task corresponding to the target account according to the identity category and allocate the target task to the target account in the case of receiving the task push request of the target account. .

In an implementation manner, the acquiring unit 201 is configured to execute:

Obtain the current identity information of the target account at preset time intervals; or,

Obtain the current identity information sent by the client after the identity of the target account is changed.

In an implementation manner, the identity information includes an identity category and an update time of the identity category, and the determination unit 202 is further configured to execute:

When the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is less than a preset period, determine that the identity category of the target account is the historical identity information Identity category in .

In an implementation manner, the determining unit 202 is further configured to execute:

When the difference between the update time in the current identity information and the update time in the pre-acquired historical identity information of the target account is not less than a preset period, determine the current identity information in accordance with preset category rules The identity category of the target account and the higher identity category among the identity categories in the historical identity information are used as the identity category of the target account.

In an implementation manner, the device further includes:

The push unit is further configured to monitor the execution status of the target account on the target task; when the target account completes the target task, push the virtual resource corresponding to the identity category to the target account.

In an implementation manner, the push unit is further configured to execute:

Sending the current identity information of the target account and the task information of the target task to the risk control platform;

In response to the risk control hit information returned by the risk control platform, push the risk control hit information to the target account.

In an implementation manner, the device further includes:

The receiving unit is configured to display task information of candidate tasks matching the identity category of the target account in response to the target account’s access operation on the preset page; A task push request for executing any of the candidate tasks, where the task push request is generated based on the target account's selection operation on the task information of any of the candidate tasks.

It can be seen from the above that the technical solutions provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to different identity categories of accounts, that is, customize different tasks for accounts of different identity categories, thereby enriching The diversity of account identity conversion tasks improves the flexibility of task allocation, thereby reducing the possibility of accounts performing the same task repeatedly.

With regard to the apparatus in the above embodiments, the specific manner in which each module executes operations has been described in detail in the embodiments related to the method, and will not be described in detail here.

Fig. 5 is a block diagram showing an electronic device for task assignment according to an exemplary embodiment.

In an exemplary embodiment, there is also provided a computer-readable storage medium including instructions, such as a memory including instructions, executable by a processor of an electronic device to perform the method. Alternatively, the computer readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, optical data storage device, and the like.

In an exemplary embodiment, there is also provided a computer program product which, when run on a computer, causes the computer to implement the task allocation method.

It can be seen from the above that the technical solutions provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to different identity categories of accounts, that is, customize different tasks for accounts of different identity categories, thereby enriching The diversity of account identity conversion tasks improves the flexibility of task allocation, thereby reducing the possibility of accounts performing the same task repeatedly.

Fig. 6 is a block diagram of an apparatus 800 for task allocation according to an exemplary embodiment.

For example, apparatus 800 may be a mobile phone, computer, digital broadcast electronics, messaging device, game console, tablet device, medical device, fitness device, personal digital assistant, and the like.

Referring to FIG. 6, the device 800 may include one or more of the following components: a processing component 802, a memory 804, a power component 806, a multimedia component 808, an audio component 810, an input/output (I/O) interface 812, a sensor component 814, and communication component 816 .

The processing component 802 generally controls the overall operations of the device 800, such as those associated with display, telephone calls, data communications, camera operations, and recording operations. The processing component 802 may include one or more processors 820 to execute instructions to complete all or part of the steps of the method. Additionally, processing component 802 may include one or more modules that facilitate interaction between processing component 802 and other components. For example, processing component 802 may include a multimedia module to facilitate interaction between multimedia component 808 and processing component 802 .

The memory 804 is configured to store various types of data to support operations at the device 800 . Examples of such data include instructions for any application or method operating on device 800, contact data, phonebook data, messages, pictures, videos, and the like. The memory 804 can be implemented by any type of volatile or non-volatile storage device or their combination, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable Programmable Read Only Memory (EPROM), Programmable Read Only Memory (PROM), Read Only Memory (ROM), Magnetic Memory, Flash Memory, Magnetic or Optical Disk.

The power supply component 807 provides power to various components of the device 800 . Power components 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for device 800 .

The multimedia component 808 includes screens that provide an output interface between the device 800 and the account. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touch screen to receive an input signal from an account. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensor may not only sense a boundary of a touch or swipe action, but also detect duration and pressure associated with the touch or swipe action. In some embodiments, the multimedia component 808 includes a front camera and/or a rear camera. When the device 800 is in an operation mode, such as a shooting mode or a video mode, the front camera and/or the rear camera can receive external multimedia data. Each front camera and rear camera can be a fixed optical lens system or have focal length and optical zoom capability.

The audio component 810 is configured to output and/or input audio signals. For example, the audio component 810 includes a microphone (MIC) configured to receive external audio signals when the device 800 is in operation modes, such as call mode, recording mode and voice recognition mode. Received audio signals may be further stored in memory 804 or sent via communication component 816 . In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.

The I/O interface 812 provides an interface between the processing component 802 and a peripheral interface module, and the peripheral interface module may be a keyboard, a click wheel, a button, and the like. These buttons may include, but are not limited to: a home button, volume buttons, start button, and lock button.

Sensor assembly 814 includes one or more sensors for providing status assessments of various aspects of device 800 . For example, the sensor component 814 can detect the open/closed state of the device 800, the relative positioning of components, such as the display and keypad of the device 800, and the sensor component 814 can also detect a change in the position of the device 800 or a component of the device 800 , accounts for the presence or absence of contact with the device 800 , the device 800 orientation or acceleration/deceleration and the temperature change of the device 800 . Sensor assembly 814 may include a proximity sensor configured to detect the presence of nearby objects in the absence of any physical contact. Sensor assembly 814 may also include an optical sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 814 may also include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor or a temperature sensor.

The communication component 816 is configured to facilitate wired or wireless communication between the apparatus 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, an operator network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives broadcast signals or broadcast related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 816 also includes a near field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wide Band (UWB) technology, Bluetooth (BT) technology and other technologies.

In an exemplary embodiment, apparatus 800 may be programmed by one or more application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable Realized by a gate array (FPGA), a controller, a microcontroller, a microprocessor or other electronic components, for performing the methods described in the first aspect and the second aspect.

In an exemplary embodiment, there is also provided a non-transitory computer-readable storage medium comprising instructions, such as the memory 804 comprising instructions, executable by the processor 820 of the apparatus 800 to perform the method. Optionally, for example, the storage medium may be a non-transitory computer-readable storage medium, for example, the non-transitory non-transitory computer-readable storage medium computer-readable storage medium may be ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage devices, etc.

In an exemplary embodiment, there is also provided a computer program product containing instructions, which when run on a computer, causes the computer to execute the task allocation method described in any one of the above embodiments.

It can be seen from the above that the technical solutions provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to different identity categories of accounts, that is, customize different tasks for accounts of different identity categories, thereby enriching The diversity of account identity conversion tasks improves the flexibility of task allocation, thereby reducing the possibility of accounts performing the same task repeatedly.

Other embodiments of the present disclosure will be readily apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any modification, use or adaptation of the present disclosure, and these modifications, uses or adaptations follow the general principles of the present disclosure and include common knowledge or conventional technical means in the technical field not disclosed in the present disclosure . The specification and examples are to be considered exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.

It should be understood that the present disclosure is not limited to the precise constructions which have been described above and shown in the drawings, and various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims (10)

1. A task allocation method, comprising:

acquiring current identity information of a target account;

determining the identity type of the target account according to the current identity information and the pre-acquired historical identity information of the target account;

and under the condition that a task pushing request of the target account is received, determining a target task corresponding to the target account according to the identity category, and distributing the target task to the target account.

2. The task allocation method according to claim 1, wherein the obtaining current identity information of the target account comprises:

acquiring current identity information of a target account according to a preset time interval; or the like, or, alternatively,

and acquiring current identity information sent by the client after the identity of the target account is changed.

3. The task allocation method according to claim 1, wherein the identity information includes an identity category and an update time of the identity category, and the determining the identity category of the target account according to the current identity information and the pre-acquired historical identity information of the target account includes:

and under the condition that the difference between the updating time in the current identity information and the updating time in the pre-acquired historical identity information of the target account is less than a preset period, determining the identity type of the target account as the identity type in the historical identity information.

4. The task allocation method according to claim 3, wherein when a difference between an update time in the current identity information and an update time in the pre-acquired historical identity information of the target account is not less than a preset period, the method further comprises:

and determining the identity category in the current identity information and the high-category identity category in the identity categories in the historical identity information as the identity categories of the target account according to a preset category rule.

5. The task assignment method according to claim 1, wherein after the assigning the target task to the target account, further comprising:

monitoring the execution state of the target account on the target task;

and under the condition that the target account completes the target task, pushing the virtual resource corresponding to the identity category to the target account.

6. The task allocation method according to claim 5, wherein before the pushing the virtual resource corresponding to the identity category to the target account, the method further comprises:

sending the current identity information of the target account and the task information of the target task to a wind control platform;

responding to the wind control hit information returned by the wind control platform, and pushing the wind control hit information to the target account.

7. A task assigning apparatus, comprising:

an acquisition unit configured to perform acquisition of current identity information of a target account;

the determining unit is configured to determine the identity type of the target account according to the current identity information and the pre-acquired historical identity information of the target account;

the allocation unit is configured to determine a target task corresponding to the target account according to the identity category and allocate the target task to the target account when the task push request of the target account is received.

8. An electronic device, comprising:

a processor;

a memory for storing the processor-executable instructions;

wherein the processor is configured to execute the instructions to implement the task allocation method of any one of claims 1 to 6.

9. A computer-readable storage medium, wherein instructions in the computer-readable storage medium, when executed by a processor of a task distribution electronic device, enable the task distribution electronic device to perform the task distribution method of any of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program realizes the task assigning method according to any one of claims 1-6 when executed by a processor.

Images