A task allocation method, device, electronic device and storage medium
By obtaining and analyzing the current and historical identity information of the account, determining its identity categories and assigning tasks, the problem of poor task allocation flexibility in the existing technology is solved, and the diversity and flexibility of account identity conversion tasks is realized, reducing duplicate tasks implement.
Patent Information
- Application Number
- CN202211008469.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-08-22
- Publication Date
- 2024-11-26
- Estimated Expiration
- 2042-08-22
AI Technical Summary
In the prior art, the identity conversion task is relatively single, and the task allocation flexibility is poor, resulting in the account that needs to repeatedly execute the same tasks during identity conversion, and lack targeted services.
By obtaining the current identity information and historical identity information of the target account, determining its identity category, and assigning corresponding tasks according to the identity category, monitoring the task execution status, pushing virtual resources, and improving the flexibility and diversity of task allocation.
It realizes customizing tasks according to account identity categories, enriches the diversity of tasks, reduces the possibility of repeated execution of the same task in the account, and improves the flexibility and user experience of task allocation.
Smart Images

Figure CN115499438B_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of the Internet, and in particular to a task allocation method, device, electronic device and storage medium. Background Art
[0002] At present, there are more and more accounts on the Internet platform. According to the activity and usage of the accounts, the accounts can be divided into different categories. It is understandable that different categories of accounts have different characteristics. By classifying the accounts and providing different services to different categories of accounts in a targeted manner, users can be provided with a personalized experience.
[0003] In some scenarios, the same account can be converted between different categories by executing identity conversion tasks. However, in the prior art, identity conversion tasks are relatively simple, and the account needs to repeat the same task each time it converts its identity, which makes task allocation less flexible. Summary of the invention
[0004] The present disclosure provides a task allocation method, device, electronic device and storage medium to at least solve the problem that the identity conversion task in the related art is relatively single and the flexibility of task allocation is poor. The technical solution of the present disclosure is as follows:
[0005] According to a first aspect of an embodiment of the present disclosure, a task allocation method is provided, including:
[0006] Get the current identity information of the target account;
[0007] Determine the identity category of the target account according to the current identity information and the previously acquired historical identity information of the target account;
[0008] When a task push request from 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 allocated to the target account.
[0009] Optionally, obtaining the current identity information of the target account includes:
[0010] Obtain the current identity information of the target account at a preset time interval; or,
[0011] Get the current identity information sent by the client after the target account identity is changed.
[0012] Optionally, the identity information includes an identity category and an update time of the identity category, and determining the identity category of the target account according to the current identity information and pre-acquired historical identity information of the target account further includes:
[0013] 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, the identity category of the target account is determined to be the identity category in the historical identity information.
[0014] 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:
[0015] According to a preset category rule, a higher category of the identity category in the current identity information and the identity category in the historical identity information is determined as the identity category of the target account.
[0016] Optionally, after allocating the target task to the target account, the method further includes:
[0017] Monitoring the execution status of the target task by the target account;
[0018] When the target account completes the target task, the virtual resources corresponding to the identity category are pushed to the target account.
[0019] Optionally, before pushing the virtual resources corresponding to the identity category to the target account, the method further includes:
[0020] Sending the current identity information of the target account and the task information of the target task to the risk control platform;
[0021] In response to the risk control hit information returned by the risk control platform, the risk control hit information is pushed to the target account.
[0022] 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:
[0023] In response to the target account's access operation on a preset page, displaying task information of candidate tasks that match the identity category of the target account;
[0024] In response to a task push request of the target account for any candidate task, executing the any candidate task, the task push request being generated based on a selection operation of the target account for task information of the any candidate task.
[0025] According to a second aspect of an embodiment of the present disclosure, there is provided a task allocation device, comprising:
[0026] An acquisition unit, configured to acquire current identity information of a target account;
[0027] a determining unit configured to determine the identity category of the target account based on the current identity information and the pre-acquired historical identity information of the target account;
[0028] The allocating unit is configured to, upon receiving a task push request from the target account, determine the target task corresponding to the target account according to the identity category, and allocate the target task to the target account.
[0029] Optionally, the acquisition unit is configured to execute:
[0030] Obtain the current identity information of the target account at a preset time interval; or,
[0031] Get the current identity information sent by the client after the target account identity is changed.
[0032] Optionally, the identity information includes an identity category and an update time of the identity category, and the determining unit is further configured to execute:
[0033] 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, the identity category of the target account is determined to be the identity category in the historical identity information.
[0034] Optionally, the determining unit is further configured to execute:
[0035] When the difference between the update time in the current identity information and the update time in the historical identity information of the target account obtained in advance is not less than a preset period, the higher category of the identity category in the current identity information and the identity category in the historical identity information is determined according to the preset category rule as the identity category of the target account.
[0036] Optionally, the device further comprises:
[0037] The pushing 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 resources corresponding to the identity category to the target account.
[0038] Optionally, the push unit is further configured to execute:
[0039] Sending the current identity information of the target account and the task information of the target task to the risk control platform;
[0040] In response to the risk control hit information returned by the risk control platform, the risk control hit information is pushed to the target account.
[0041] Optionally, the device further comprises:
[0042] The receiving unit is configured to execute, in response to the target account's access operation on a preset page, display task information of candidate tasks that match the identity category of the target account; in response to the target account's task push request for any candidate task, execute any candidate task, wherein the task push request is generated based on the target account's selection operation for the task information of any candidate task.
[0043] According to a third aspect of an embodiment of the present disclosure, there is provided a task allocation electronic device, including:
[0044] processor;
[0045] a memory for storing instructions executable by the processor;
[0046] The processor is configured to execute the instructions to implement any one of the task allocation methods described above.
[0047] According to a fourth aspect of an embodiment of the present disclosure, a computer-readable storage medium is provided. When instructions in the computer-readable storage medium are executed by a processor of a task allocation electronic device, the task allocation electronic device is enabled to perform any one of the task allocation methods described above.
[0048] According to a fifth aspect of an embodiment of the present disclosure, there is provided a computer program product, comprising a computer program / instruction, wherein when the computer program / instruction is executed by a processor, the task allocation method described in any one of the above is implemented.
[0049] The technical solution provided by the embodiments of the present disclosure brings at least the following beneficial effects:
[0050] Acquire the multimedia data to be processed and the account behavior data corresponding to the multimedia data; acquire the current identity information of the target account; determine the identity category of the target account based on the current identity information and the historical identity information of the target account acquired in advance; upon receiving a task push request from the target account, determine the target task corresponding to the target account based on the identity category, and assign the target task to the target account.
[0051] In this way, different tasks can be assigned to accounts of different identity categories according to their different identity categories. In other words, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks, improving the flexibility of task allocation, and reducing the possibility of accounts repeatedly performing the same task.
[0052] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0053] The drawings herein are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the description are used to explain the principles of the present disclosure, and do not constitute improper limitations on the present disclosure.
[0054] Figure 1 The figure is a flowchart of a task allocation method according to an exemplary embodiment.
[0055] Figure 2 is a system diagram of a task allocation method according to an exemplary embodiment.
[0056] Figure 3 is a system flow chart of a task allocation method according to an exemplary embodiment.
[0057] Figure 4 The figure is a block diagram of a task allocation device according to an exemplary embodiment.
[0058] Figure 5 It is a block diagram of an electronic device for task allocation according to an exemplary embodiment.
[0059] Figure 6 It is a block diagram of a device for task allocation according to an exemplary embodiment. DETAILED DESCRIPTION
[0060] 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.
[0061] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present disclosure described herein can be implemented in an order other than those illustrated or described herein. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. Instead, they are merely examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.
[0062] Figure 1 is a flowchart of a task allocation method according to an exemplary embodiment. Figure 1 As shown, the task allocation method includes the following steps.
[0063] In step S11, the current identity information of the target account is obtained.
[0064] Generally, accounts on Internet platforms have different identity categories, and accounts of different identity categories have different characteristics. Therefore, treating accounts of different identity categories in a targeted manner can enrich the user experience.
[0065] 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 based on the client's determination of 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.
[0066] In one implementation, the step of obtaining the current identity information of the target account may include:
[0067] The current identity information of the target account is obtained at 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. In this way, the server can regularly obtain the current identity information of the target account according to its own needs or user settings to maintain the stability of the system.
[0068] Alternatively, obtain the current identity information sent by the client after the target account identity changes. That is, whenever the client determines that the target account identity has changed, the updated current identity information of the target account is sent to the server. In this way, the server only needs to synchronize the identity of the updated target account, thereby saving the server's computing resources. For example, at point T, the target account is a Class A account, and at T+15, the target account is determined by the client to be a Class B account. Then, the client can synchronize the Class B account identity of the target account to the server at T+16.
[0069] In step S12, the identity category of the target account is determined based on the current identity information and the previously acquired historical identity information of the target account.
[0070] In the present disclosure, the server also stores historical identity information of the target account. The historical identity information is used to indicate the identity maintained by the server for the target account before the current time. As can be seen from the above, the current identity information is obtained after the client updates the identity information of the target account. In other words, the historical identity information and the current identity information are usually in conflict. Therefore, the server needs to synchronize and update the identity information of the target account based on the current identity information and the historical identity information.
[0071] In one implementation, the identity information includes the identity category and the update time of the identity category. Then, based on the current identity information and the historical identity information of the target account obtained in advance, the step of determining the identity category of the target account may include: when the difference between the update time in the current identity information and the update time in the historical identity information is less than a preset period, determining the identity category of the target account to be the identity category in the historical identity information. The preset period may be set according to system requirements, and the present disclosure does not limit this.
[0072] That is to say, if the target account has been 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 the preset period. In this way, the rationality of the identity conversion of each account in the system can be effectively maintained, and the abnormality of account identity conversion caused by client misjudgment can be reduced.
[0073] 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, and the target account remains in identity category A.
[0074] In addition, when the difference between the update time in the current identity information and the update time in the historical identity information is not less than the preset period, this step also includes: according to the preset category rule, determining the identity category in the current identity information and the identity category in the historical identity information as the identity category of the target account. The preset category rule is used to indicate the priority order of each identity category, which can be set according to system requirements, and the present disclosure does not limit this.
[0075] That is to say, if the target account's identity category in the historical identity information is maintained for longer than a preset period, then when the target account's current identity information is obtained, the target account has multiple identity categories that match it. The server needs to update the target account's identity category and, according to the preset category rules, determine the highest identity category from the multiple identity categories that the target account matches as the target account's updated identity category. The target account can then enter updated, higher-level activities.
[0076] In this way, according to the preset category rules, the server can determine the identity category of the target account when there are multiple matching identity categories for the target account, thereby maintaining the uniqueness of the identity category of the target account in the system.
[0077] In step S13, when a task push request from a target account is received, a target task corresponding to the target account is determined according to the identity category, and the target task is allocated to the target account.
[0078] In the present disclosure, accounts with different identity categories can perform different tasks. Therefore, after determining the identity category of the target account, the server responds to the task push request of the target account. It can determine the target task corresponding to the target account based on the identity category of the target account and assign the target task to the target account, thereby enriching the diversity of account tasks.
[0079] Among them, the target task can be displayed at a fixed position on the preset page. After receiving the display instruction of the target task from the client, the target task page can be displayed to the client. If the target account is currently in identity category A, it cannot access tasks corresponding to other identity categories. In this way, the task form has a guiding and promoting effect on the account to execute the corresponding target task, and will have a positive impact on improving the task execution rate and other aspects.
[0080] In one implementation, the server may display task information of candidate tasks that match the identity category of the target account in response to the target account's access operation on a preset page; and execute any candidate task in response to the target account's task push request for 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.
[0081] That is to say, the task information of each candidate task can be displayed on a preset page. The target account can select a target task from multiple candidate tasks that match its own identity category by accessing the preset page, and send a task push request for the selected target task to the server. In this way, users can independently select the target task they want to perform, the task allocation method is more flexible, and the user experience is better.
[0082] In some scenarios, the target task may be an account identity conversion task. That is, as the target account performs more target tasks, the identity category of the target account will also change accordingly, thereby causing the identity category of the target account to change continuously, thereby promoting the account activity in the system.
[0083] In one implementation, after the target task is assigned to the target account, the present disclosure further includes the following steps: monitoring the execution status of the target task by the target account; when the target account completes the target task, pushing the virtual resources corresponding to the identity category to the target account.
[0084] That is to say, corresponding virtual resources can be configured as feedback for each target task, 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 matching the identity category of the target account are pushed to the target account. The virtual resources can be virtual currency or virtual goods, etc., without specific limitation.
[0085] For example, if the target task is to configure 400 telephones, and both Class A accounts and Class B accounts correspond to the target task, then after Class A accounts complete the task of configuring 400 telephones, the virtual goods distribution operation corresponding to the quantity of Class A accounts can be triggered; after Class B accounts complete the task of configuring 400 telephones, the virtual goods distribution operation corresponding to Class B accounts can be triggered.
[0086] 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 an account repeatedly performing the same task, and also helping to increase users' enthusiasm for performing tasks.
[0087] Among them, before pushing the virtual resources corresponding to the identity category to the target account, you can also: send 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.
[0088] 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. The risk control platform can analyze the target account and the target task to determine whether there are any abnormalities in the target account and the target task, thereby achieving risk control of the target account and the target task, such as whether the identity of the target account is changed too quickly, or whether the target task is a repeated task of the target account, etc. If the risk control platform determines that there are risks in the target account and the target task, then the risk control hit information can be returned 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, thereby reducing the losses caused to the system by account abnormalities.
[0089] This solution can be applied to the interactive system composed of server and client. Figure 2As shown, it is a system diagram of this solution. 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, which can be a MySQL (relational database management system) database or a redis (REmoteDIctionary Server, remote dictionary service) database. The user data includes task snapshots, user information, and activity information. The task system can also obtain virtual resources from the reward database, and the virtual resources can be stored in the redis database; the task system updates the task execution status and task completion status of each account through the task middle platform, and feeds back the task information to the risk control platform for evaluation. After the risk control platform passes the evaluation, the traffic middle platform will issue rewards to the account. If the risk control platform fails to pass the evaluation, the account can be notified through SMS and private message platforms; at the same time, the Grafana program is used to perform perf monitoring to display user data and virtual resources. In addition, the task system can obtain task completion event messages through the kafka mechanism, wherein the task completion event messages can correspond to a variety of different tasks, such as publishing videos, starting live broadcasts, watching videos, smart phones, and identity authentication, etc., without specific limitations.
[0090] like Figure 3 As shown, it is the system flow chart of this solution. 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 category, it notifies the user that he can participate in the task. Then, the account can visit the task page, initialize the task, and perform the corresponding task, and give feedback to the server. The server updates the task status of the completed task in the task middle station according to the feedback of the account. Then, 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 middle station. After the task middle station 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 sends a risk control notification to the account. If the evaluation passes, the server can request the traffic middle station to issue virtual resources, where the virtual resources can be traffic coupons. Then, the virtual resource issuance message can be notified to the user, and the display data of the service number can be updated.
[0091] From the above, it can be seen that the technical solution provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to the different identity categories of the accounts. That is to say, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks, improving the flexibility of task allocation, and reducing the possibility of accounts repeatedly performing the same task.
[0092] Figure 4is a block diagram of a task allocation device according to an exemplary embodiment, the device comprising:
[0093] An acquisition unit 201 is configured to acquire current identity information of a target account;
[0094] A determination 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;
[0095] The allocating unit 203 is configured to, upon receiving a task push request from the target account, determine the target task corresponding to the target account according to the identity category, and allocate the target task to the target account.
[0096] In one implementation, the obtaining unit 201 is configured to execute:
[0097] Obtain the current identity information of the target account at a preset time interval; or,
[0098] Get the current identity information sent by the client after the target account identity is changed.
[0099] In one implementation, the identity information includes an identity category and an update time of the identity category, and the determining unit 202 is further configured to execute:
[0100] 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, the identity category of the target account is determined to be the identity category in the historical identity information.
[0101] In one implementation, the determining unit 202 is further configured to execute:
[0102] When the difference between the update time in the current identity information and the update time in the historical identity information of the target account obtained in advance is not less than a preset period, the higher category of the identity category in the current identity information and the identity category in the historical identity information is determined according to the preset category rule as the identity category of the target account.
[0103] In one implementation, the device further includes:
[0104] The pushing 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 resources corresponding to the identity category to the target account.
[0105] In one implementation, the push unit is further configured to execute:
[0106] Sending the current identity information of the target account and the task information of the target task to the risk control platform;
[0107] In response to the risk control hit information returned by the risk control platform, the risk control hit information is pushed to the target account.
[0108] In one implementation, the device further includes:
[0109] The receiving unit is configured to execute, in response to the target account's access operation on a preset page, display task information of candidate tasks that match the identity category of the target account; in response to the target account's task push request for any candidate task, execute any candidate task, wherein the task push request is generated based on the target account's selection operation for the task information of any candidate task.
[0110] From the above, it can be seen that the technical solution provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to the different identity categories of the accounts. That is to say, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks, improving the flexibility of task allocation, and reducing the possibility of accounts repeatedly performing the same task.
[0111] Regarding the device in the embodiment, the specific manner in which each module performs operations has been described in detail in the embodiment of the method, and will not be elaborated here.
[0112] Figure 5 It is a block diagram of an electronic device for task allocation according to an exemplary embodiment.
[0113] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory including instructions, and the instructions can be executed by a processor of an electronic device to complete the method. Optionally, the computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0114] In an exemplary embodiment, a computer program product is also provided. When the computer program product is executed on a computer, the computer is enabled to implement the task allocation method.
[0115] From the above, it can be seen that the technical solution provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to the different identity categories of the accounts. That is to say, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks, improving the flexibility of task allocation, and reducing the possibility of accounts repeatedly performing the same task.
[0116] Figure 6 It is a block diagram of a device 800 for task allocation according to an exemplary embodiment.
[0117] For example, apparatus 800 may be a mobile phone, a computer, a digital broadcast electronic device, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.
[0118] Reference Figure 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 a communication component 816 .
[0119] The processing component 802 generally controls the overall operation of the device 800, such as operations associated with display, phone 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 described method. In addition, the processing component 802 may include one or more modules to facilitate the interaction between the processing component 802 and other components. For example, the processing component 802 may include a multimedia module to facilitate the interaction between the multimedia component 808 and the processing component 802.
[0120] The memory 804 is configured to store various types of data to support operations on the device 800. Examples of such data include instructions for any application or method operating on the device 800, contact data, phone book data, messages, pictures, videos, etc. The memory 804 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, 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 disk or optical disk.
[0121] The power supply component 807 provides power to the various components of the device 800. The power supply component 807 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the device 800.
[0122] The multimedia component 808 includes a screen that provides 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 input signals from the account. The touch panel includes one or more touch sensors to sense touch, slide, and gestures on the touch panel. The touch sensor may not only sense the boundaries of the touch or slide action, but also detect the duration and pressure associated with the touch or slide operation. In some embodiments, the multimedia component 808 includes a front camera and / or a rear camera. When the device 800 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera may receive external multimedia data. Each front camera and rear camera may be a fixed optical lens system or have a focal length and optical zoom capability.
[0123] The audio component 810 is configured to output and / or input audio signals. For example, the audio component 810 includes a microphone (MIC), and when the device 800 is in an operating mode, such as a call mode, a recording mode, and a speech recognition mode, the microphone is configured to receive an external audio signal. The received audio signal can be further stored in the memory 804 or sent via the communication component 816. In some embodiments, the audio component 810 also includes a speaker for outputting audio signals.
[0124] I / O interface 812 provides an interface between processing component 802 and peripheral interface modules, which may be keyboards, click wheels, buttons, etc. These buttons may include but are not limited to: home button, volume button, start button, and lock button.
[0125] The sensor assembly 814 includes one or more sensors for providing various aspects of the status assessment of the device 800. For example, the sensor assembly 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 assembly 814 can also detect the position change of the device 800 or a component of the device 800, the presence or absence of contact with the device 800, the orientation or acceleration / deceleration of the device 800, and the temperature change of the device 800. The sensor assembly 814 may include a proximity sensor configured to detect the presence of a nearby object without any physical contact. The 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 assembly 814 may also include an accelerometer, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.
[0126] The communication component 816 is configured to facilitate wired or wireless communication between the device 800 and other devices. The device 800 can access a wireless network based on a communication standard, such as WiFi, a carrier network (such as 2G, 3G, 4G or 5G), or a combination thereof. In an exemplary embodiment, the communication component 816 receives a broadcast signal 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 can be implemented based on radio frequency identification (RFID) technology, infrared data association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology and other technologies.
[0127] In an exemplary embodiment, the apparatus 800 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors or other electronic components to execute the methods described in the first and second aspects.
[0128] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 804 including instructions, which can be executed by a processor 820 of the device 800 to complete the method. Alternatively, for example, the storage medium can be a non-transitory computer-readable storage medium, for example, the non-transitory computer-readable storage medium can be a ROM, a random access memory (RAM), a CD-ROM, a magnetic tape, a floppy disk, an optical data storage device, etc.
[0129] In an exemplary embodiment, a computer program product including instructions is also provided. When the computer program product is executed on a computer, the computer is enabled to execute the task allocation method described in any one of the embodiments.
[0130] From the above, it can be seen that the technical solution provided by the embodiments of the present disclosure can assign different tasks to accounts of different identity categories according to the different identity categories of the accounts. That is to say, different tasks can be customized for accounts of different identity categories, thereby enriching the diversity of account identity conversion tasks, improving the flexibility of task allocation, and reducing the possibility of accounts repeatedly performing the same task.
[0131] Those skilled in the art will readily appreciate other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art that are not disclosed in the present disclosure. The specification and examples are intended to be exemplary only, and the true scope and spirit of the present disclosure are indicated by the following claims.
[0132] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that 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
1. A task allocation method, characterized in that: include: Obtaining the current identity information of the target account; the identity information includes the identity category and the update time of the identity category; Determine the identity category of the target account according to the current identity information and the previously acquired historical identity information of the target account; Upon receiving a task push request from the target account, determining a target task corresponding to the target account according to the identity category, and assigning the target task to the target account; Wherein, 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: When the difference between the update time in the current identity information and the update time in the previously acquired historical identity information of the target account is less than a preset period, determining the identity category of the target account to be the identity category in the historical identity information; When the difference between the update time in the current identity information and the update time in the historical identity information of the target account obtained in advance is not less than a preset period, the higher category of the identity category in the current identity information and the identity category in the historical identity information is determined according to the preset category rule as the identity category of the target account.
2. The task allocation method according to claim 1, characterized in that: The obtaining of the current identity information of the target account includes: Obtain the current identity information of the target account at a preset time interval; or, Get the current identity information sent by the client after the target account identity is changed.
3. The task allocation method according to claim 1, characterized in that: After allocating the target task to the target account, the method further includes: Monitoring the execution status of the target task by the target account; When the target account completes the target task, the virtual resources corresponding to the identity category are pushed to the target account.
4. The task allocation method according to claim 3, characterized in that: Before pushing the virtual resources 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, the risk control hit information is pushed to the target account.
5. The task allocation method according to claim 1, characterized in that: 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: In response to the target account's access operation on a preset page, displaying task information of candidate tasks that match the identity category of the target account; In response to a task push request of the target account for any candidate task, executing the any candidate task, the task push request being generated based on a selection operation of the target account for task information of the any candidate task.
6. A task allocation device, characterized in that: include: An acquisition unit, configured to acquire current identity information of a target account; The identity information includes the identity category and the update time of the identity category; a determining unit configured to determine the identity category of the target account based on the current identity information and the pre-acquired historical identity information of the target account; an allocating unit configured to, upon receiving a task push request from the target account, determine a target task corresponding to the target account according to the identity category, and allocate the target task to the target account; Wherein, 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 previously acquired historical identity information of the target account is less than a preset period, determining the identity category of the target account to be the identity category in the historical identity information; When the difference between the update time in the current identity information and the update time in the historical identity information of the target account obtained in advance is not less than a preset period, the higher category of the identity category in the current identity information and the identity category in the historical identity information is determined according to the preset category rule as the identity category of the target account.
7. The task allocation device according to claim 6, characterized in that: The acquisition unit is configured to execute: Obtain the current identity information of the target account at a preset time interval; or, Get the current identity information sent by the client after the target account identity is changed.
8. The task allocation device according to claim 6, characterized in that: The device also includes: The push unit is 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 resources corresponding to the identity category to the target account.
9. The task allocation device according to claim 8, characterized in that: 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, the risk control hit information is pushed to the target account.
10. The task allocation device according to claim 6, characterized in that: The device also includes: The receiving unit is configured to execute, in response to the target account's access operation on a preset page, display task information of candidate tasks that match the identity category of the target account; in response to the target account's task push request for any candidate task, execute any candidate task, wherein the task push request is generated based on the target account's selection operation for the task information of any candidate task.
11. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the task allocation method according to any one of claims 1 to 5.
12. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of the task allocation electronic device, the task allocation electronic device is enabled to execute the task allocation method as claimed in any one of claims 1 to 5.
13. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the task allocation method according to any one of claims 1 to 5 is implemented.
