Task distribution method, device, equipment, system and storage medium

By obtaining the indicator parameters and types of registration tasks and dynamically determining priority, the registration failure and too long time in smart communities are solved, and the smooth issuance of registration information and efficiency improvement are achieved.

CN113873635BActive Publication Date: 2024-11-15BEIJING KINGSOFT CLOUD NETWORK TECH CO LTD +1
View PDF 11 Cites 0 Cited by

Patent Information

Application Number
CN202111131582.3
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-09-26
Publication Date
2024-11-15
Estimated Expiration
2041-09-26

AI Technical Summary

Technical Problem

In smart communities, community users often encounter problems such as registration failure or registration time when registering, mainly because the order of processing of registration information does not meet the requirements of the community equipment, resulting in registration failure; during centralized registration during construction, a large number of them are found The issuance of registration information causes the registration time of ordinary users to be too long or fail.

Method used

By obtaining the indicator parameters of the registered task, determine its type (batch task or non-batch task, text-based task or image-based task), and dynamically determine priority based on factors such as type and data volume, and in order of priority from high to low Send registration tasks to ensure that the processing order of registration information meets the equipment requirements.

Benefits of technology

It effectively solves the problems of registration failure and registration time too long, ensuring the smooth completion of the registration process and improving efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN113873635B_ABST
    Figure CN113873635B_ABST
Patent Text Reader

Abstract

The present application relates to a task issuing method, device, equipment, system and storage medium. The method includes obtaining at least two registration tasks; obtaining the indication parameters of each registration task; determining the type of each registration task based on the indication parameters; determining the priority of each registration task based on the type; and issuing each registration task in order of priority from high to low. Since the type of the registration task can be determined based on the indication parameters of the registration task, and the priority of the registration task can be further dynamically determined based on the type, the problems of registration failure or registration time process that often occur when cell users register can be solved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of computers, and in particular to a task issuing method, device, equipment, system and storage medium. Background Art

[0002] With the development of science and technology, in order to improve people's living standards and bring convenience to people's lives, multifunctional smart communities are emerging in various places. Smart communities refer to the integrated application of new generation information technologies such as the Internet, Internet of Things, big data, and cloud computing to provide community residents with a safe, comfortable, convenient, modern and intelligent living environment.

[0003] There are many community devices set up in the smart community. If community users want to use the community devices, they need to register their registration information in the community devices. Currently, community users often encounter problems such as registration failure or long registration time when registering. Summary of the invention

[0004] The present application provides a task issuing method, apparatus, device, system and storage medium, which are used to solve the problem that registration failure or long registration time often occurs when users in the current community register.

[0005] In a first aspect, a task issuing method is provided, comprising:

[0006] Get at least two registered tasks;

[0007] Obtaining respective indication parameters of each of the registration tasks;

[0008] Based on the indication parameters, respectively determine the type of each registered task;

[0009] Based on the types, respectively determine the priorities of the respective registration tasks;

[0010] The registration tasks are issued in sequence according to the priority from high to low.

[0011] Optionally, the indication parameter is used to indicate whether the type of the registered task is a batch task or a non-batch task;

[0012] and / or,

[0013] The indication parameter is used to indicate that the type of the registered task is a text task or an image task;

[0014] and / or,

[0015] The indication parameter is used to indicate the size of the data volume of the registration task.

[0016] Optionally, when the indication parameter indicates that the type of the registered task is the batch task or the non-batch task, the indication parameter includes at least one of the following:

[0017] The task identifier of the registered task;

[0018] The identity of the uploader of the registered task;

[0019] The number of registered tasks uploaded by the uploader of the registered tasks within a preset time period;

[0020] The interval between two adjacent registration tasks uploaded by the uploader of the registration task.

[0021] Optionally, when the indication parameter is used to indicate that the type of the registered task is a text task or an image task, the indication parameter includes at least one of the following:

[0022] The task identifier of the registered task;

[0023] The registration information carried by the registration task.

[0024] Optionally, determining the priority of each of the registration tasks based on the type includes:

[0025] Determine that the priority of the non-batch task in each of the registered tasks is higher than the priority of the batch task;

[0026] and / or,

[0027] Determine that among the registered tasks, the priority of a task type that is a text task is higher than the priority of a task type that is an image task;

[0028] and / or,

[0029] It is determined that the priority of the registration task with a large data volume is lower than the priority of the registration task with a small data volume.

[0030] Optionally, determining the priority of each of the registration tasks based on the type includes:

[0031] Obtain the current network bandwidth and resource delivery capabilities;

[0032] Respectively determine a weight coefficient corresponding to the network bandwidth, a weight coefficient corresponding to the resource delivery capability, and a weight coefficient corresponding to each of the types;

[0033] Based on the network bandwidth, the resource delivery capability, the type and the corresponding weight coefficient, respectively calculate a value indicating the priority of each of the registration tasks;

[0034] According to the numerical values, respective priorities of the registered tasks are determined respectively.

[0035] Optionally, based on the indication parameter, determining the type of each registration task includes:

[0036] When the task identifier of the registered task is a batch identifier, determining that the type of the registered task is the batch task; when the task identifier of the registered task is a non-batch identifier, determining that the type of the registered task is the non-batch task;

[0037] and / or,

[0038] When the identity identifier of the uploader of the registered task is a batch uploader identifier, it is determined that the type of the registered task is the batch task; when the identity identifier of the uploader of the registered task is a non-batch uploader identifier, it is determined that the type of the registered task is the non-batch task;

[0039] and / or,

[0040] When the number of registered tasks uploaded by the uploader of the registered task within a preset time period is greater than the number threshold, the type of the registered task is determined to be the batch task; when the number of registered tasks uploaded by the uploader of the registered task within the preset time period is not greater than the number threshold, the type of the registered task is determined to be the non-batch task;

[0041] and / or,

[0042] When the interval time between two adjacent registration tasks uploaded by the uploader of the registration task is less than the interval time threshold, it is determined that the type of the registration task is the batch task; when the interval time between two adjacent registration tasks uploaded by the uploader of the registration task is not less than the interval time threshold, it is determined that the type of the registration task is the non-batch task.

[0043] Optionally, based on the indication parameter, determining the type of each registration task includes:

[0044] When the task identifier of the registered task is a text identifier, the type of the registered task is determined to be the text task; when the task identifier of the registered task is an image identifier, the type of the registered task is determined to be the image task;

[0045] and / or,

[0046] The data format of the registration information carried by the registration task is obtained. When the data format is a text format, the type of the registration task is determined to be the text task; when the data format is an image format, the type of the registration task is determined to be the image task.

[0047] In a second aspect, a communication system is provided, including a server and at least one user terminal:

[0048] at least one user terminal, used to generate at least two registration tasks and send at least two registration tasks to the server;

[0049] The server obtains at least two of the registration tasks; obtains the indication parameters of each of the registration tasks; based on the indication parameters, determines the type of each of the registration tasks; based on the type, determines the priority of each of the registration tasks; and sends each of the registration tasks in order from high to low priority.

[0050] In a third aspect, a task issuing device is provided, comprising:

[0051] A first acquisition unit, used to acquire at least two registration tasks;

[0052] A second acquisition unit, used to acquire the indication parameter of each of the registration tasks;

[0053] A first determining unit, configured to determine the type of each registered task based on the indication parameter;

[0054] A second determining unit, configured to determine the priority of each of the registration tasks based on the type;

[0055] The sending unit is used to send each of the registration tasks in sequence according to the priority from high to low.

[0056] In a fourth aspect, a computer device is provided, comprising: a processor, a memory and a communication bus, wherein the processor and the memory communicate with each other via the communication bus;

[0057] The memory is used to store computer programs;

[0058] The processor is used to execute the program stored in the memory to implement the task issuing method described in the first aspect.

[0059] In a fifth aspect, a computer-readable storage medium is provided, storing a computer program, characterized in that when the computer program is executed by a processor, the task issuing method described in the first aspect is implemented.

[0060] The above technical solution provided by the embodiment of the present application has the following advantages over the prior art: the method provided by the embodiment of the present application obtains at least two registration tasks; obtains the indication parameters of each registration task; determines the type of each registration task based on the indication parameters; determines the priority of each registration task based on the type; and issues each registration task in order of priority from high to low. Since the type of the registration task can be determined based on the indication parameters of the registration task, and the priority of the registration task can be further dynamically determined based on the type, the problems of registration failure or registration time process that often occur when cell users register can be solved. BRIEF DESCRIPTION OF THE DRAWINGS

[0061] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.

[0062] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0063] Figure 1 A flowchart of a task issuing method in an embodiment of the present application;

[0064] Figure 2 This is another flowchart of the task issuing method in the embodiment of the present application;

[0065] Figure 3 This is a schematic diagram of the structure of the task issuing device in the embodiment of the present application;

[0066] Figure 4 This is a structural diagram of a task issuing system in an embodiment of the present application;

[0067] Figure 5 It is a schematic diagram of the structure of a computer device in an embodiment of the present application. DETAILED DESCRIPTION

[0068] In order to make the purpose, technical solution and advantages of the embodiments of the present application clearer, the technical solution in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

[0069] It should be noted that the terms "first", "second", etc. in the specification and claims of the present application and the above-mentioned 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 interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device comprising a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0070] In the related technology, in one scenario, for community users who have moved into a smart community, when registering, community users usually need to provide at least two types of registration information: personnel information and facial information. Since the community device has a sequential processing order for these two types of information, when the registration information sent to the community device does not conform to the device's processing order, registration failure will occur. Taking the community device as an access control device as an example, the order of entering registration information for the access control device is to enter personnel information first, and then facial information, otherwise the facial information will fail to be entered. This requires that personnel information be sent to the access control device earlier than facial information, so when facial information is sent to the access control device earlier than personnel information, the access control device will fail to enter facial information.

[0071] In another scenario, during the construction of a smart community, for community equipment that has been installed and debugged, the construction party will usually register the registration information of community users into the community equipment before the community users move in. Due to centralized registration, a large amount of registration information will be sent to the community equipment through the server in a short period of time. During this process, if there are ordinary users who have moved into another smart community and also send registration information to the community equipment through the server, the server will send the registration information of the ordinary user only after all the centralized registration information has been sent, resulting in a long registration time or registration failure for the ordinary user.

[0072] In order to solve the above technical problems, the present application embodiment provides a task delivery method, which can be applied to a server, such as Figure 1 As shown, the method may include the following steps:

[0073] Step 101: Obtain at least two registration tasks.

[0074] In this embodiment, at least two registration tasks may be for the same user, for implementing the registration of the user in the device; or at least two registration tasks may be for different users, for implementing the registration of different users in the device.

[0075] Step 102: Obtain the indication parameters of each registration task.

[0076] Step 103: Based on the indication parameters, the types of each registered task are determined respectively.

[0077] In this embodiment, the indication parameter can directly indicate the type of the registration task, and / or indicate the type of the registration task through the size of the data volume of the registration task.

[0078] When the indication parameter directly indicates the type of the registered task, the type of the registered task includes two types: one is a batch task or a non-batch task, and the other is a text task or an image task.

[0079] It should be understood that these two types belong to different dimensions, so for a certain task, the task can have both types. For example, the task belongs to both batch tasks and text tasks; for another example, the task belongs to both non-batch tasks and image tasks; etc.

[0080] Among them, when the type of the registration task is a batch task, it means that the registration task is any task among a large number of tasks centrally issued by the server in a short period of time; when the type of the registration task is a non-batch task, it means that the registration task is a task uploaded to the server by an ordinary user or several ordinary users.

[0081] Among them, text tasks are tasks that carry the user's personal information; image tasks are tasks that carry the user's facial information.

[0082] In the application, the personnel information includes but is not limited to personnel number, personnel name, and pass card information; the face information includes but is not limited to face image, face number and other information.

[0083] In this embodiment, when the indication parameter indicates that the type of the registered task is a batch task or a non-batch task, the indication parameter includes at least one of the following:

[0084] The task ID of the registered task;

[0085] The identity of the uploader of the registered task;

[0086] The number of registered tasks uploaded by the uploader of the registered tasks within the preset time period;

[0087] The interval between two consecutive registered tasks uploaded by the uploader of the registered tasks.

[0088] The task identifier of the registered task includes a batch identifier or a non-batch identifier. The batch identifier is used to indicate that the type of the registered task is a batch task, and the non-batch identifier is used to indicate that the type of the registered task is a non-batch task.

[0089] In the application, the server stores the correspondence between the task identifier and the type of the registered task, so based on the correspondence and the task identifier of the registered task in the indication parameter, the type of the registered task can be determined.

[0090] The identity of the uploader of the registered task includes a batch uploader identity or a non-batch uploader identity, the batch uploader identity is used to indicate that the type of the registered task is a batch task, and the non-batch uploader identity is used to indicate that the type of the registered task is a non-batch task. Corresponding to the second scenario in the related technology described above, the batch uploader identity can also be called the construction party identity, and the non-batch uploader identity can also be called the ordinary user identity.

[0091] In the application, when uploading the registered task through the user terminal, the uploader of the registered task can mark his / her identity on the user terminal before uploading, such as entering his / her identity in a preset mark input box.

[0092] Among them, when the number of registered tasks uploaded by the uploader of the registered task within the preset time is greater than the number threshold, the type of the registered task is determined to be a batch task; when the number of registered tasks uploaded by the uploader of the registered task within the preset time is not greater than the number threshold, the type of the registered task is determined to be a non-batch task.

[0093] Among them, the preset duration and number threshold can be set manually based on experience.

[0094] Among them, when the interval time between two adjacent registration tasks uploaded by the uploader of the registered task is less than the interval time threshold, the type of the registered task is determined to be a batch task; when the interval time between two adjacent registration tasks uploaded by the uploader of the registered task is not less than the interval time threshold, the type of the registered task is determined to be a non-batch task.

[0095] The interval duration may also be set manually based on experience.

[0096] It should be understood that in the application, when the construction party centrally registers the registration information of users in each community, the registration information of users in each community has been pre-stored in the user terminal used by the construction party. The construction party only needs to trigger the user terminal to upload the registration information of users in each community. Therefore, in this case, the interval time between the registrant uploading two adjacent registration tasks is relatively small, which is less than the interval time threshold; and when ordinary users register the registration information, the user terminal used by the ordinary users needs to collect the personnel information and face information of the ordinary users in real time, and upload them to the server respectively. Therefore, in this case, the interval time between the registrant uploading two adjacent registration tasks is relatively long, which is greater than or equal to the interval time threshold.

[0097] In this embodiment, when the indication parameter indicates that the type of the registered task is a text task or an image task, the indication parameter includes at least one of the following:

[0098] The task ID of the registered task;

[0099] Registration information carried by the registration task.

[0100] The task identifier of the registered task includes a text identifier or an image identifier. The text identifier is used to indicate that the type of the registered task is a text task, and the non-batch identifier is used to indicate that the type of the registered task is an image task.

[0101] In the application, when uploading the registered task through the user terminal, the uploader of the registered task can mark the task identifier of the registered task on the user terminal before uploading, such as inputting the task identifier in a preset mark input box.

[0102] The registration information carried by the registration task is actually the registration information of the cell user, so the type of the registration task can be determined based on the data format of the registration information. Specifically, the data format of the registration information carried by the registration task is obtained. When the data format is a text format, the type of the registration task is determined to be a text task; when the data format is an image format, the type of the registration task is determined to be an image task.

[0103] Step 104: Determine the priority of each registration task based on the type.

[0104] In this embodiment, in order to prevent the construction party from centrally registering registration information, which may cause ordinary users to fail to register or take too long to register, the priority of non-batch tasks in each registration task is set to be higher than the priority of batch tasks; in order to meet the processing order of the equipment, the priority of text tasks in each registration task is set to be higher than the priority of image tasks, or the priority of registration tasks with large data volume is set to be lower than the priority of registration tasks with small data volume.

[0105] It should be understood that, among the registered tasks, the data volume of the registered tasks whose task type is a text task is smaller than the data volume of the registered tasks whose task type is an image task.

[0106] In the application, when at least two registered tasks include task types of non-batch tasks, batch tasks, text tasks and image tasks, the at least two registered tasks can be divided into two batches of tasks according to batch tasks and non-batch tasks, and then for each batch of registered tasks, the priority of text tasks is set higher than that of image tasks. Therefore, when sending each registered task to the device, the text tasks in the non-batch tasks are sent first, then the image tasks in the non-batch tasks are sent, then the text tasks in the batch tasks are sent, and finally the image tasks in the batch tasks are sent; or, when sending each registered task to the device, the registered tasks in the non-batch tasks whose data volume is less than the data volume threshold are sent first, then the registered tasks in the non-batch tasks whose data volume is not less than the data volume threshold are sent, then the registered tasks in the batch tasks whose data volume is less than the data volume threshold are sent, and finally the registered tasks in the batch tasks whose data volume is not less than the data volume threshold are sent.

[0107] It should be understood that when at least two registered tasks include multiple registered tasks of the same type, the priorities of the multiple registered tasks can be differentiated based on the size of the data volume. For example, when the types of the multiple registered tasks are all non-batch tasks and image tasks, the priorities of the registered tasks can be differentiated based on the size of the data volume of each registered task.

[0108] Or, when the at least two registration tasks include multiple registration tasks of the same type, the priorities of the multiple registration tasks are differentiated in a first-come, first-served order.

[0109] In this embodiment, in order to realize adaptive dynamic adjustment of the priority of the registration task, the current network bandwidth and the resource delivery capability of the server may also be considered when determining the priority of the registration task based on the type.

[0110] Specifically, the current network bandwidth and resource delivery capability are obtained; the weight coefficient corresponding to the network bandwidth, the weight coefficient corresponding to the resource delivery capability, and the weight coefficient corresponding to the type are determined respectively; based on the network bandwidth, the resource delivery capability, the type, and the corresponding weight coefficients, numerical values ​​indicating the respective priorities of each registration task are calculated respectively; and according to the numerical values, the respective priorities of each registration task are determined respectively.

[0111] In the application, assuming that the weight coefficient corresponding to the current network bandwidth is a1, the weight coefficient corresponding to the resource delivery capability is a2, and the weight coefficient corresponding to the type of a certain registration task is a3, then the priority value Y of the registration task can be determined by the following formula:

[0112] Y=a1*network bandwidth value+a2*resource delivery capability value+a3*type corresponding value.

[0113] In the application, a first mapping relationship between network bandwidth and weight coefficient, a second mapping relationship between resource delivery capability and weight coefficient, and a third mapping relationship between type and weight coefficient can be pre-set in the form of a step function. Therefore, after obtaining the current network bandwidth and resource delivery capability, the weight coefficient corresponding to the current network bandwidth can be determined based on the first mapping relationship, the weight coefficient corresponding to the current resource delivery capability can be determined based on the second mapping relationship, and the weight coefficient corresponding to the type can be determined based on the third mapping relationship.

[0114] In the application, the first mapping relationship, the second mapping relationship and the third mapping relationship may be preset according to the network bandwidth, the resource delivery capability and the contribution of the type to the priority.

[0115] It should be understood that when the network bandwidth is large and the resource delivery capability is strong, it means that the current server can deliver multiple registration tasks at the same time. Therefore, at this time, multiple registration tasks of non-batch tasks and text tasks can be delivered at one time, or multiple registration tasks of non-batch tasks and image tasks can be delivered at one time, etc.

[0116] Step 105: Issue each registration task in order of priority from high to low.

[0117] Each of the at least two registration tasks may be a task for the same device or a task for different devices, which is not specifically limited in this embodiment. In the application, when issuing each registration task, the server may determine the device to which the registration task should be issued based on the destination address carried by the registration task.

[0118] In the technical solution provided by this embodiment, at least two registration tasks are obtained; the indication parameters of each registration task are obtained; based on the indication parameters, the types of each registration task are determined; based on the types, the priorities of each registration task are determined; and each registration task is issued in order of priority from high to low. Since the type of the registration task can be determined based on the indication parameters of the registration task, and the priority of the registration task can be further dynamically determined based on the type, the problem of registration failure or long registration time that often occurs when a cell user registers can be solved.

[0119] In order to more clearly describe the embodiments of the present application, the present application scheme is described below in conjunction with the registration scenario of access control devices in a smart community.

[0120] Please refer to Figure 2 , Figure 2The following is a flow chart of a task issuing method shown in an embodiment of the present application, and the method includes the following steps:

[0121] Step 201: An ordinary user who has moved into the smart community sends a registration task to the rule engine in the server through a user terminal. The registration task carries the registration information of the ordinary user, which includes personal information and / or facial information.

[0122] Step 202: The construction party user submits a large number of registration tasks to the rule engine in the server through the user terminal;

[0123] Each registration task submitted in a batch manner carries an indication parameter for indicating that it is submitted in batches.

[0124] Step 203: The rule engine in the server is used to receive registration tasks from ordinary users and large quantities of registration tasks from construction parties;

[0125] Step 204: Determine that the priority of the registration task submitted in a large batch is lower than the priority of the registration task submitted in a non-batch manner, and the priority of the registration task carrying face information is lower than the priority of the registration task carrying personnel information;

[0126] Step 205: Submit the registration tasks from ordinary users, the registration tasks from the construction party, and the corresponding priorities to the access control command center;

[0127] Step 206: The access control instruction issuing center issues registration tasks to the access control devices in order of priority.

[0128] Based on the same concept, a task issuing device is provided in the embodiment of the present application. The specific implementation of the device can be found in the description of the method embodiment part, and the repeated parts will not be repeated. Figure 3 As shown, the device mainly includes:

[0129] A first acquisition unit 301 is used to acquire at least two registration tasks;

[0130] The second acquisition unit 302 is used to acquire the indication parameters of each registration task;

[0131] A first determining unit 303, configured to determine the type of each registered task based on the indication parameter;

[0132] A second determining unit 304 is used to determine the priority of each registration task based on the type;

[0133] The issuing unit 305 is used to issue each registration task in order from high to low priority.

[0134] Optionally, the indication parameter is used to indicate whether the type of the registered task is a batch task or a non-batch task;

[0135] and / or,

[0136] The indication parameter is used to indicate whether the type of the registered task is a text task or an image task;

[0137] and / or,

[0138] The indication parameter is used to indicate the size of the data volume of the registered task.

[0139] Optionally, when the indication parameter indicates that the type of the registered task is a batch task or a non-batch task, the indication parameter includes at least one of the following:

[0140] The task ID of the registered task;

[0141] The identity of the uploader of the registered task;

[0142] The number of registered tasks uploaded by the uploader of the registered tasks within the preset time period;

[0143] The interval between two consecutive registered tasks uploaded by the uploader of the registered tasks.

[0144] Optionally, when the indication parameter is used to indicate that the type of the registered task is a text task or an image task, the indication parameter includes at least one of the following:

[0145] The task ID of the registered task;

[0146] Registration information carried by the registration task.

[0147] Optionally, the second determining unit 304 is configured to:

[0148] Determine that the priority of non-batch tasks among the registered tasks is higher than the priority of batch tasks;

[0149] and / or,

[0150] Determine that among the registered tasks, the priority of the task type being a text task is higher than the priority of the task type being an image task;

[0151] and / or,

[0152] It is determined that the priority of the registration task with a large data volume is lower than the priority of the registration task with a small data volume.

[0153] Optionally, the second determining unit 304 is configured to:

[0154] Obtain the current network bandwidth and resource delivery capabilities;

[0155] Determine the weight coefficient corresponding to the network bandwidth, the weight coefficient corresponding to the resource delivery capability, and the weight coefficient corresponding to the type respectively;

[0156] Based on the network bandwidth, resource delivery capability, type and corresponding weight coefficient, calculate the values ​​indicating the priority of each registered task respectively;

[0157] According to the numerical value, the priority of each registered task is determined respectively.

[0158] Optionally, the first determining unit 303 is configured to:

[0159] When the task identifier of the registered task is a batch identifier, the type of the registered task is determined to be a batch task; when the task identifier of the registered task is a non-batch identifier, the type of the registered task is determined to be a non-batch task;

[0160] and / or,

[0161] When the identity identifier of the uploader of the registered task is a batch uploader identifier, the type of the registered task is determined to be a batch task; when the identity identifier of the uploader of the registered task is a non-batch uploader identifier, the type of the registered task is determined to be a non-batch task;

[0162] and / or,

[0163] When the number of registered tasks uploaded by the uploader of the registered task within the preset time period is greater than the number threshold, the type of the registered task is determined to be a batch task; when the number of registered tasks uploaded by the uploader of the registered task within the preset time period is not greater than the number threshold, the type of the registered task is determined to be a non-batch task;

[0164] and / or,

[0165] When the interval time between two adjacent registered tasks uploaded by the uploader of the registered task is less than the interval time threshold, the type of the registered task is determined to be a batch task; when the interval time between two adjacent registered tasks uploaded by the uploader of the registered task is not less than the interval time threshold, the type of the registered task is determined to be a non-batch task.

[0166] Optionally, the first determining unit 303 is configured to:

[0167] When the task identifier of the registered task is a text identifier, the type of the registered task is determined to be a text task; when the task identifier of the registered task is an image identifier, the type of the registered task is determined to be an image task;

[0168] and / or,

[0169] The data format of the registration information carried by the registration task is obtained. When the data format is a text format, the type of the registration task is determined to be a text task; when the data format is an image format, the type of the registration task is determined to be an image task.

[0170] Based on the same concept, a communication system is provided in the embodiment of the present application. The specific implementation of the system can refer to the description of the method embodiment part, and the repeated parts will not be repeated. Figure 4 As shown, the system mainly includes:

[0171] Server 401 and at least one user terminal 402:

[0172] At least one user terminal 402, used to generate at least two registration tasks and send the at least two registration tasks to the server 401;

[0173] Server 401 obtains at least two registration tasks; obtains the indication parameters of each registration task; based on the indication parameters, determines the type of each registration task; based on the type, determines the priority of each registration task; and issues each registration task in order from high to low priority.

[0174] Based on the same concept, the present application also provides a computer device, such as Figure 5 As shown, the computer device mainly includes: a processor 501, a memory 502 and a communication bus 503, wherein the processor 501 and the memory 502 communicate with each other through the communication bus 503. The memory 502 stores a program executable by the processor 501, and the processor 501 executes the program stored in the memory 502 to implement the following steps:

[0175] Get at least two registered tasks;

[0176] Get the instruction parameters of each registered task;

[0177] Based on the indication parameters, the types of each registered task are determined respectively;

[0178] Determine the priority of each registration task based on the type;

[0179] The registration tasks are issued in order from high to low priority.

[0180] The communication bus 503 mentioned in the above computer device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. The communication bus 503 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 5 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0181] The memory 502 may include a random access memory (RAM) or a non-volatile memory, such as at least one disk memory. Alternatively, the memory may also be at least one storage device located away from the processor 501 .

[0182] The above-mentioned processor 501 can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc., and can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components.

[0183] In another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program runs on a computer, the computer executes the task issuing method described in the above embodiment.

[0184] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instruction is loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network or other programmable device. The computer instruction can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instruction is transmitted from a website site, a computer, a server or a data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, a data center, etc. that contains one or more available media integration. The available medium can be a magnetic medium (e.g., a floppy disk, a hard disk, a tape, etc.), an optical medium (e.g., a DVD) or a semiconductor medium (e.g., a solid-state hard disk), etc.

[0185] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0186] The foregoing is merely a specific embodiment of the present invention, which enables those skilled in the art to understand or implement the present invention. Various modifications to these embodiments will be apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features claimed herein.

Claims

1. A task issuing method, characterized in that: include: Acquire at least two registration tasks, wherein each of the registration tasks is a task for registering a user in a cell; Obtaining respective indication parameters of each of the registration tasks; Based on the indication parameter, respectively determine the type of each registered task, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, based on the indication parameter, respectively determine the type of each registered task includes: based on the indication parameter, determining that the registered task is a batch task or a non-batch task; Based on the type, respectively determining the priority of each of the registered tasks, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, respectively determining the priority of each of the registered tasks includes: determining that the priority of the non-batch task in each of the registered tasks is higher than the priority of the batch task in the batch task, wherein the batch task is any task in a large number of tasks centrally issued by the server in a short period of time, and the non-batch task is a task uploaded to the server by a user; The registration tasks are issued in sequence according to the priority from high to low.

2. The method according to claim 1, characterized in that The indication parameter is used to indicate whether the type of the registered task is a batch task or a non-batch task; and / or, The indication parameter is used to indicate that the type of the registered task is a text task or an image task; and / or, The indication parameter is used to indicate the size of the data volume of the registration task.

3. The method according to claim 2, characterized in that When the indication parameter indicates that the type of the registered task is the batch task or the non-batch task, the indication parameter includes at least one of the following: The task identifier of the registered task; The identity of the uploader of the registered task; The number of registered tasks uploaded by the uploader of the registered tasks within a preset time period; The interval between two adjacent registration tasks uploaded by the uploader of the registration task.

4. The method according to claim 2, characterized in that: When the indication parameter is used to indicate that the type of the registered task is a text task or an image task, the indication parameter includes at least one of the following: The task identifier of the registered task; The registration information carried by the registration task.

5. The method according to claim 2, characterized in that: The determining the priority of each of the registration tasks based on the type includes: Determine that the priority of the non-batch task in each of the registered tasks is higher than the priority of the batch task; and / or, Determine that among the registered tasks, the priority of a task type that is a text task is higher than the priority of a task type that is an image task; and / or, It is determined that the priority of the registration task with a large data volume is lower than the priority of the registration task with a small data volume.

6. The method according to any one of claims 1 to 4, characterized in that: The determining the priority of each of the registration tasks based on the type includes: Obtain the current network bandwidth and resource delivery capabilities; Respectively determine a weight coefficient corresponding to the network bandwidth, a weight coefficient corresponding to the resource delivery capability, and a weight coefficient corresponding to the type; Based on the network bandwidth, the resource delivery capability, the type and the corresponding weight coefficient, respectively calculate a value indicating the priority of each of the registration tasks; According to the numerical values, respective priorities of the registered tasks are determined respectively.

7. The method according to claim 3, characterized in that Based on the indication parameters, the types of the respective registration tasks are determined respectively, including: When the task identifier of the registered task is a batch identifier, determining that the type of the registered task is the batch task; when the task identifier of the registered task is a non-batch identifier, determining that the type of the registered task is the non-batch task; and / or, When the identity identifier of the uploader of the registered task is a batch uploader identifier, it is determined that the type of the registered task is the batch task; when the identity identifier of the uploader of the registered task is a non-batch uploader identifier, it is determined that the type of the registered task is the non-batch task; and / or, When the number of registered tasks uploaded by the uploader of the registered task within a preset time period is greater than the number threshold, the type of the registered task is determined to be the batch task; when the number of registered tasks uploaded by the uploader of the registered task within the preset time period is not greater than the number threshold, the type of the registered task is determined to be the non-batch task; and / or, When the interval time between two adjacent registration tasks uploaded by the uploader of the registration task is less than the interval time threshold, it is determined that the type of the registration task is the batch task; when the interval time between two adjacent registration tasks uploaded by the uploader of the registration task is not less than the interval time threshold, it is determined that the type of the registration task is the non-batch task.

8. The method according to claim 4, characterized in that Based on the indication parameters, the types of the respective registration tasks are determined respectively, including: When the task identifier of the registered task is a text identifier, the type of the registered task is determined to be the text task; when the task identifier of the registered task is an image identifier, the type of the registered task is determined to be the image task; and / or, The data format of the registration information carried by the registration task is obtained. When the data format is a text format, the type of the registration task is determined to be the text task; when the data format is an image format, the type of the registration task is determined to be the image task.

9. A communication system, characterized in that: It includes a server and at least one user terminal: at least one user terminal, configured to generate at least two registration tasks and send at least two registration tasks to the server, wherein each registration task is a task for registering a user in a cell; The server obtains at least two of the registered tasks; obtains an indication parameter of each of the registered tasks; based on the indication parameter, determines the type of each of the registered tasks, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, based on the indication parameter, determines the type of each of the registered tasks includes: based on the indication parameter, determines that the registered task is a batch task or a non-batch task; based on the type, determines the priority of each of the registered tasks, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, determines the priority of each of the registered tasks includes: determines that the priority of the task type of the non-batch task in each of the registered tasks is higher than the priority of the task type of the batch task, wherein the batch task is any task in a large number of tasks that are centrally issued by the server in a short period of time, and the non-batch task is a task uploaded to the server by a user; and issues each of the registered tasks in order of the priorities from high to low.

10. A task issuing device, characterized in that: include: A first acquisition unit, configured to acquire at least two registration tasks, wherein each of the registration tasks is a task for registering a user in a cell; A second acquisition unit, used to acquire the indication parameter of each of the registration tasks; A first determining unit is configured to determine the type of each registered task based on the indication parameter, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, determining the type of each registered task based on the indication parameter includes: determining that the registered task is a batch task or a non-batch task based on the indication parameter; A second determining unit is configured to determine the respective priorities of the registered tasks based on the type, wherein when the indication parameter is used to indicate that the type of the registered task is a batch task or a non-batch task, determining the respective priorities of the registered tasks includes: determining that the priority of the non-batch task in the registered tasks is higher than the priority of the batch task, wherein the batch task is any task in a large number of tasks centrally issued by the server in a short period of time, and the non-batch task is a task uploaded to the server by a user; The sending unit is used to send each of the registration tasks in sequence according to the priority from high to low.

11. A computer device, characterized in that: include: A processor, a memory and a communication bus, wherein the processor and the memory communicate with each other via the communication bus; The memory is used to store computer programs; The processor is used to execute the program stored in the memory to implement the task issuing method described in any one of claims 1-8.

12. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the task issuing method according to any one of claims 1 to 8 is implemented.

Citation Information

Patent Citations

  • Method for controlling batch processing of community platform and instant communication server

    CN102130851A

  • Congestion control method and device

    CN103548381A

  • Multi-queue multi-priority big data task management system and method for achieving big data task management by utilizing system

    CN104657214A

  • Multi-task processing method and multi-task processing device

    CN104731649A

  • Task request processing method and device, and user equipment

    CN106899649A