Data processing method, device, storage medium and program product

Abstract

The method comprises the following steps: receiving a first processing request for adding a target label to a target object sent by a first client; obtaining a to-be-executed function associated with the target label; determining a second client set for processing the first processing request according to the to-be-executed function; obtaining a permission identifier of at least one second client; sending a second processing request to the second client set, wherein the second processing request comprises target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client; enabling the second client with the permission identifier in the second client set to process the second processing request; receiving an authorization message sent by a target second client; and adding the target label to the target object according to the authorization message. In the embodiment of the present disclosure, the accuracy of the label adding process can be ensured, the to-be-executed function of the label binding can be accurately executed, and the stable operation of the label system can be ensured.

Description

TECHNICAL FIELD

[0001] Embodiments of the present disclosure relate to the technical field of computer and network communication, and particularly relate to a data processing method, device, storage medium and program product. BACKGROUND

[0002] User tags can not only facilitate the classification of users by category or interest, but also the addition of tags to users and the maintenance of tags, which are essential daily operations for operators.

[0003] The existing tag system can implement simple tag tree relationships and multiple selection, mutual exclusion and other regular operations. However, in the process of adding tags, the tags are usually directly added to users by administrators. Different administrators may add different tags to the same user, which may result in errors and cannot guarantee the accuracy of user tags, cannot accurately play the functions related to tags, and leads to instability of the tag system. SUMMARY

[0004] Embodiments of the present disclosure provide a data processing method, device, storage medium and program product to improve the accuracy of the process of adding tags to users.

[0005] In a first aspect, embodiments of the present disclosure provide a data processing method, comprising:

[0006] receiving a first processing request for adding a target tag to a target object sent by a first client;

[0007] According to the first processing request, the target tag is associated with a to-be-executed function, the second client set for processing the first processing request is determined according to the to-be-executed function, and the permission identifier of at least one second client in the second client set is obtained;

[0008] sending a second processing request to the second client set, the second processing request including target object information, the target tag and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier in the second client set processes the second processing request;

[0009] receiving an authorization message sent by a target second client, and adding the target tag to the target object according to the authorization message.

[0010] In a second aspect, embodiments of the present disclosure provide a data processing device, comprising:

[0011] a receiving unit configured to receive a first processing request for adding a target tag to a target object sent by a first client;

[0012] The processing unit is configured to acquire a to-be-executed function associated with the target label according to the first processing request, determine a second client set for processing the first processing request according to the to-be-executed function, and acquire a permission identifier of at least one second client in the second client set;

[0013] The sending unit is configured to send a second processing request to the second client set, the second processing request including target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that a second client with the permission identifier in the second client set processes the second processing request;

[0014] The receiving unit is further configured to receive an authorization message sent by a target second client.

[0015] The processing unit is further configured to add the target label to the target object according to the authorization message.

[0016] In a third aspect, an electronic device is provided, including at least one processor and a memory.

[0017] The memory stores computer-executable instructions.

[0018] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the data processing method as described in the first aspect and various possible designs of the first aspect.

[0019] In a fourth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores computer-executable instructions. When a processor executes the computer-executable instructions, the data processing method as described in the first aspect and various possible designs of the first aspect is implemented.

[0020] In a fifth aspect, a computer program product is provided, and the computer program product includes computer-executable instructions. When a processor executes the computer-executable instructions, the data processing method as described in the first aspect and various possible designs of the first aspect is implemented.

[0021] The data processing method, device, storage medium and program product provided by the embodiment, the method comprises the following steps: receiving a first processing request for adding a target label to a target object sent by a first client; obtaining a to-be-executed function associated with the target label according to the first processing request, determining a second client set for processing the first processing request according to the to-be-executed function, and obtaining a permission identifier of at least one second client in the second client set; sending a second processing request to the second client set, the second processing request comprising target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier in the second client set processes the second processing request; receiving an authorization message sent by a target second client, and adding the target label to the target object according to the authorization message. In the embodiment of the disclosure, the second client is authorized according to the to-be-executed function associated with the target label when the target label is added to the target object, and the target label is added to the target object after the authorization is passed, thereby ensuring the accuracy of the label adding process, and the to-be-executed function bound by the label can be accurately executed, and the stable operation of the label system is ensured. BRIEF DESCRIPTION OF DRAWINGS

[0022] In order to more clearly illustrate the technical solutions in the embodiments of the present disclosure or the prior art, the following will briefly introduce the drawings needed to be used in the embodiments or prior art description. Obviously, the drawings in the following description are some embodiments of the present disclosure, and other drawings can also be obtained by those skilled in the art without creative labor.

[0023] Figure 1 The communication system architecture example diagram of the data processing method provided by an embodiment of the present disclosure is shown in the figure.

[0024] Figure 2 The data processing method flowchart provided by an embodiment of the present disclosure is shown in the figure.

[0025] Figure 3 The data processing method flowchart provided by another embodiment of the present disclosure is shown in the figure.

[0026] Figure 4 The data processing method flowchart provided by another embodiment of the present disclosure is shown in the figure.

[0027] Figure 5 The data processing method flowchart provided by another embodiment of the present disclosure is shown in the figure.

[0028] Figure 6 The data processing method flowchart provided by another embodiment of the present disclosure is shown in the figure.

[0029] Figure 7 The structure block diagram of the data processing device provided by the embodiment of the present disclosure is shown in the figure.

[0030] Figure 8 A hardware structure schematic diagram of an electronic device provided by an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0031] To make the objects, technical solutions, and advantages of the embodiments of the present disclosure clearer, the following will be combined with the drawings in the embodiments of the present disclosure to clearly and completely describe the technical solutions in the embodiments of the present disclosure. Obviously, the described embodiments are some but not all of the embodiments of the present disclosure. Based on the embodiments in the present disclosure, all other embodiments obtained by a person of ordinary skill in the art without creative work fall within the protection scope of the present disclosure.

[0032] The user label can not only conveniently classify users according to categories or interests, but also often binds complex function algorithms such as recommended content. Labeling and maintaining the label are necessary daily work for operation.

[0033] The existing label system can realize simple label tree relationship and general operations such as multiple selection and mutual exclusion. However, in the labeling process, the management personnel usually directly label the users, and there is a lack of sufficient authorization. Especially for some labels that bind functions, there may be specific function algorithm operations. The lack of sufficient authorization may cause security risks and inaccuracy of the label system, and the label binding function cannot be accurately executed, resulting in instability of the label system.

[0034] To solve the above technical problems, in the embodiments of the present disclosure, the labeling process can be confirmed and authorized by multiple parties when the management personnel label the target object, and the target object is added with the label after the authorization is passed, so as to ensure the accuracy of the process of adding the label to the target object, and then the to-be-executed function of the label binding can be accurately executed, and the stable operation of the label system is ensured.

[0035] The data processing method provided by the embodiments of the present disclosure is suitable for Figure 1The illustrated communication system includes a server 101, a first client 102 of a manager, a second client set 110 of auditors, wherein the second client set 110 can include a client 111 of an operator and / or a client 112 of a target object; the first client 102 can send a first processing request for adding a target label to the target object to the server 101; the server 101 obtains an associated to-be-executed function of the target label, determines a second client set 110 for processing the first processing request according to the to-be-executed function, and obtains a permission identifier of at least one second client in the second client set 110; sends a second processing request to the second client set 110, wherein the second processing request includes target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier determines whether to authorize the addition of the target label to the target object; and the second client can send an authorization message to the server 101, so that the server 101 adds the target label to the target object according to the authorization message.

[0036] If multiple operators need to confirm and authorize, the second processing request is sent to the second client 111 of the operator, so that the second processing request is displayed only on the interface of the second client with the permission identifier; and / or if the target object needs to confirm and authorize, the second processing request is sent to the client 112 of the target object, so that the second processing request is displayed on the interface of the client of the target object. The client in the embodiment of the disclosure includes but is not limited to a mobile phone, a personal computer, a notebook computer, a tablet computer, a personal digital assistant and the like, and the server can be a server, or a server cluster composed of several servers, or a cloud computing service center.

[0037] The data processing method provided by the embodiment of the disclosure will be described in detail below with reference to specific embodiments.

[0038] Reference Figure 2 , Figure 2 The data processing method provided by the embodiment of the disclosure is shown in the flowchart. The method of the embodiment can be applied in a terminal device or a server, and the data processing method includes the following steps.

[0039] S201, receiving a first processing request for adding a target label to a target object sent by a first client.

[0040] In the embodiment, a manager can specify a target label needed to be added for a target object, and trigger a labeling process, that is, the manager can send a first processing request for adding a target label to a target object through a first client.

[0041] The target label can be selected from a label set, and the label set includes pre-created labels, or the target label can be a newly created label and can be added to the label set. The label set can include different types of labels, and each type of label can have different attributes, such as a label name, a label description, and the like, and can be associated with different to-be-executed functions, such as a recommendation function for a user, and the to-be-executed function bound to the target label can be executed by an execution device on any object detected to have the target label.

[0042] In this embodiment, the administrators can include administrators of different levels, such as super administrators, local administrators, local operators, and the like, and are respectively assigned different permissions. For example, a super administrator can create and manage labels across regions (including labels that are cross-region visible or cross-region effective), a local administrator can only create and manage labels that are visible in a region, labels that are effective in a region, and labels that are effective in a region and created by a super administrator, and an ordinary operator can only see local visible labels on a user account.

[0043] S202, acquiring a to-be-executed function associated with the target label according to the first processing request, determining a second client set for processing the first processing request according to the to-be-executed function, and acquiring a permission identifier of at least one second client in the second client set.

[0044] In this embodiment, since the target label is associated with a to-be-executed function, in order to solve the problems of label security and accuracy, the first processing request of the first client for adding the target label to the target object needs to be confirmed and authorized by at least one second client.

[0045] In this embodiment, different confirmation processes can be required for target labels associated with different to-be-executed functions, that is, different second clients need to be confirmed and authorized, including but not limited to a second client of a user operator and a second client of an administrator. In addition, in order to protect the right to know of the target object, the target object can also be confirmed and authorized. The confirmation process can involve different multiple clients, which are referred to as a second client set.

[0046] Optionally, in this embodiment, the confirmation process can be pre-set for various to-be-executed functions, and then the corresponding confirmation process can be determined according to the to-be-executed function associated with the target label, that is, the second client set for processing the first processing request is determined. Alternatively, the confirmation process corresponding to the to-be-executed function associated with the target label can be pre-determined, and the confirmation process or the identifier of the confirmation process is written in the attribute information of the target label, or the identifier of the second client set for processing the first processing request is written in the attribute information of the target label.

[0047] And, since it is also necessary to agree which clients in the second client set have the right to confirm and authorize, for example, there are multiple user operators, and which user operator specifically confirms and authorizes, and for different labels, different people can confirm and authorize, after determining the confirmation process of the target label, the permission identifier of the second client that can confirm and authorize the target label is obtained, and only the second client with the permission identifier has the right to confirm and authorize. Optionally, the permission identifier of the second client that can confirm and authorize the target label can be written in the attribute information of the target label, and only the second client with the permission identifier can confirm and authorize the first processing request of the target label.

[0048] S203, send a second processing request to the second client set, the second processing request including target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that the second client in the second client set with the permission identifier processes the second processing request.

[0049] In the embodiment, the second processing request can be sent to the corresponding second client according to the confirmation process of the target label, and the second processing request includes but is not limited to target object information, a target label and an associated to-be-executed function, and a permission identifier of a second client, so that the second client with the permission identifier confirms and authorizes, for example, judges whether the target object information is consistent with the target label, whether the target object is suitable for the to-be-executed function, whether the region where the target object is located is consistent with the effective region of the target label, whether the target label conflicts with other labels of the target object, whether the first client has the right to add the target label to the target object, and the like, so as to finally determine whether to authorize adding the target label to the target object.

[0050] Optionally, if the confirmation process of the target label includes the confirmation process of different operators, that is, the second client set includes second clients of multiple operators, the second processing request is sent to the client of each operator respectively, so that the second processing request is displayed on the interface of the client with the permission identifier, so that the operator determines whether adding the target label to the target object conforms to the preset rule; and / or

[0051] If the confirmation process of the target label includes the confirmation process of the target object, that is, the second client set includes the client of the target object, the second processing request is sent to the terminal of the target object, so that the second processing request is displayed on the interface of the terminal of the target object, so that the target object determines whether to authorize adding the target label, so as to protect the right to know of the target object.

[0052] S204, receiving the authorization message sent by the target second client, and adding the target tag to the target object according to the authorization message.

[0053] In the embodiment, after receiving the authorization message sent by the second client, if all the second clients with the permission identifier are authorized, the target tag is added to the target object, for example, the target tag is added to the personal information of the target object, or is displayed on the personal homepage of the target object, the user avatar, and the like.

[0054] Optionally, if there are multiple confirmation links in the confirmation process, the next confirmation link can be entered after the authorization of one confirmation link, that is, the second processing request is sent to the next second client with the permission identifier after the authorization of one second client with the permission identifier, otherwise, the confirmation process is ended and the subsequent confirmation link is not needed; in addition, if the target tag needs to be authorized by the target object, the second processing request is sent to the client of the target object in the last confirmation link of the confirmation process, so that the second processing request is displayed on the client interface of the target object, if the authorization message of the client of the target object is received, the target tag can be added to the target object, otherwise, the process is ended.

[0055] Optionally, the above process can also be used for the tag deletion process and other operations of the target object. Specifically, the tag deletion process can be: receiving the deletion request for deleting the target tag of the target object sent by the first client, obtaining the to-be-executed function associated with the target tag according to the first processing request, determining the second client set for processing the deletion request according to the to-be-executed function, obtaining the permission identifier of at least one second client in the second client set, sending the third processing request to the second client set, the third processing request including the target object information, the target tag and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier determines whether to authorize the deletion of the target tag of the target object, receiving the authorization message sent by the second client, and deleting the target tag of the target object according to the authorization message.

[0056] The data processing method provided in the embodiment comprises the following steps: receiving a first processing request for adding a target label to a target object sent by a first client; obtaining a to-be-executed function associated with the target label according to the first processing request, determining a second client set for processing the first processing request according to the to-be-executed function, and obtaining a permission identifier of at least one second client in the second client set; sending a second processing request to the second client set, wherein the second processing request comprises target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier in the second client set processes the second processing request; receiving an authorization message sent by a target second client, and adding the target label to the target object according to the authorization message. In the embodiment, the second client is authorized according to the to-be-executed function associated with the target label when the target label is added to the target object, and the target label is added to the target object after the authorization is passed, so that the accuracy of the label adding process is ensured, and then the to-be-executed function bound by the label can be accurately executed, and the stable operation of the label system is ensured.

[0057] On the basis of the above embodiment, S203 can further comprise the following before sending the second processing request to the second client set:

[0058] The target object information and the target label are checked in at least one of the following manners:

[0059] It is checked whether the region where the target object is located is consistent with the effective region of the target label;

[0060] It is checked whether the target label conflicts with other labels of the target object;

[0061] It is checked whether the first client has the permission to add the target label to the target object.

[0062] In the embodiment, before starting the confirmation process, the target object information and the target label can also be automatically checked. Since the target label has a region attribute, i.e., it is visible or effective in some specific region, the region where the target object is located can be checked to be consistent with the effective region of the target label. If they are not consistent, the subsequent confirmation process is not needed. In addition, some labels are mutually exclusive, e.g., label A and label B are mutually exclusive. If the target object already has label A, adding label B to the target object will conflict with label A. Therefore, if it is determined that the target label conflicts with other labels of the target object, the subsequent confirmation process is also not needed. Since different managers have different permissions, some managers have the permission to add target labels to target objects, and some managers do not have the permission to add target labels to target objects. Therefore, if it is determined that the first client does not have the permission to add target labels to the target object, the subsequent confirmation process is also not needed. Of course, specific checks can also be included, which are not described here.

[0063] In the embodiment, before receiving the first processing request sent by the first client for adding the target label to the target object, the method further includes: Figure 3

[0064] S301, receiving a target label creation request sent by the first client, the target label creation request including attribute information of the target label, the attribute information of the target label being attribute information that can be configured for the target label within a permission range corresponding to the first client;

[0065] S302, creating the target label according to the target label creation request and adding the target label to a label set, so as to be used by the first client to select a target label to be added to the target object from the label set.

[0066] In the embodiment, a manager can create a target label in advance. The manager can send a target label creation request through the first client and set attribute information of the target label in the target label creation request. Since different managers have different permissions, the manager can only create labels within the permission range of the manager and set attribute information that can be set within the permission range of the label.

[0067] For example, a first type of manager can set a label that is visible across regions and / or effective across regions, e.g., a super administrator. Therefore, a first target label creation request sent by a first client of the first type can be received, the first target label creation request including first attribute information of the target label, the first attribute information including at least one of the following: a label visible region, a label effective region, a permission identifier of a second client, a function to be executed, and whether to hide a label description. ​

[0068] For another example, the second type of manager can set a tag that is visible in a local region and / or effective in the local region, for example, a local administrator, and thus can receive a second target tag creation request sent by a second type of first client, the second target tag creation request including second attribute information of the target tag, the second attribute information including at least one of whether the tag is visible in the local region, whether the tag is effective in the local region, a permission identifier of the second client, a function to be executed, and whether to hide a tag description.

[0069] In this embodiment, a tag visible region refers to that an operation personnel and / or a user belonging to a specified region can see the tag, a tag effective region refers to that only a user belonging to a specified region can be tagged, a permission identifier of a second client refers to that only a user with the permission identifier can add or delete a tag to an object, and whether to hide a tag description refers to setting whether to display the tag description to an operation personnel and / or a user.

[0070] In addition, on the basis of the above-mentioned embodiments, some managers can also set tag attributes such as a tag name, a business to which the tag belongs, a tag description, a tag level, and whether to select the tag singly.

[0071] After creating a tag, the created tag can be added to a tag collection, so as to facilitate subsequent selection of the tag from the tag collection to add the tag to other objects.

[0072] On the basis of any of the above-mentioned embodiments, a manager can also bind a function to be executed to a tag, and specifically, as shown in FIG. 8, before obtaining the function to be executed associated with the target tag, the method further includes: Figure 4

[0073] S401, receiving a target tag and a function to be executed associated request sent by the first client, and associating the target tag with the function to be executed;

[0074] S402, sending an association relationship between the target tag and the function to be executed to an execution device of the function to be executed, so that the execution device executes the function to be executed on any object having the target tag.

[0075] In this embodiment, a manager can specify which function to be executed to be associated with a target tag, and initiate a target tag and a function to be executed associated request, and store association information between the target tag and the function to be executed. After associating the target tag with the function to be executed, an association relationship between the target tag and the function to be executed can be sent to an execution device of the function to be executed. Subsequently, when the execution device detects any object having the target tag, the function to be executed associated with the target tag can be executed, for example, the function to be executed is a warning function, and when the function to be executed is triggered (for example, a user is reported), a warning information can be sent.​

[0076] Optionally, the receiving, at S401, the association request of the target label sent by the first client and the to-be-executed function, and associating the target label with the to-be-executed function, can specifically include at least the following two manners:

[0077] Manner one: receiving the function acquisition request sent by the first client, pulling a function list from a server according to the function acquisition request, and sending the function list to the first client; receiving the association request sent by the first client, the association request including the to-be-executed function selected from the function list by the administrator, and associating the target label with the to-be-executed function; or

[0078] Manner two: receiving the association request sent by the first client, the association request including identification information of the to-be-executed function, searching for the to-be-executed function according to the identification information, and associating the target label with the to-be-executed function.

[0079] In the embodiment, in the manner one, the to-be-executed function is dynamically generated by the server, can be accessed in the form of a service, the function list is pulled from the server, and the administrator selects the to-be-executed function as needed from the function list. The advantage lies in that the function list can be dynamically generated, and there is only interaction between systems when the function is requested to be acquired, and the execution of the function is completed only in the server after the association is completed. The access in the form of a service needs to implement the read-write mode IDL (Interface description language) defined by the label system first. When the label system configures the binding relationship between the to-be-executed function and the label, the read service is called to acquire the current available function. After the association is completed by the label system, the server is called back to inform the association relationship and the to-be-executed function ID.

[0080] In the manner two, the function does not change frequently, the server does not need to separately set two interfaces, and after the association is completed, the to-be-executed function ID needs to be hard coded (or TCC configured) in the server. When the to-be-executed function needs to be associated with the target label, the identification information (to-be-executed function ID) of the to-be-executed function to be associated can be directly carried in the association request. The server can search for the corresponding to-be-executed function according to the identification information of the to-be-executed function, and associate the target label with the to-be-executed function. Alternatively, the server can directly associate the target label with the identification information of the to-be-executed function, and then search for the corresponding to-be-executed function according to the identification information of the to-be-executed function when the to-be-executed function needs to be executed.

[0081] On the basis of any of the above embodiments, as shown in Figure 5 the first processing request of adding the target label to the target object sent by the first client includes:

[0082] S501, receiving a batch processing request for adding labels to a plurality of target objects sent by the first client, the batch processing request including a request file, the request file including the plurality of target objects and target labels to be added corresponding to each target object;

[0083] S502, parsing the request file to obtain the plurality of target objects and target labels to be added corresponding to each target object, and adding them to a message queue to sequentially consume each target object and the corresponding target label to be added from the message queue.

[0084] In this embodiment, considering the scenario where a plurality of target objects need to be labeled, in order to avoid waste of manpower and material resources, a batch labeling method is provided. In this embodiment, the administrator can save a plurality of target objects and target labels to be added corresponding to each target object in a request file. The plurality of target objects can correspond to the same target label to be added, or the plurality of target objects can correspond to different target labels to be added. Then, the first client can initiate a batch processing request, and carry the request file in the batch processing request. After receiving the batch processing request, the request file can be parsed to obtain the plurality of target objects and target labels to be added corresponding to each target object, and added to a message queue to sequentially consume each target object and the corresponding target label to be added from the message queue. The processes of S202-S204 in the above embodiment are executed, and details are not repeated here. Optionally, in this embodiment, when the number of target objects to be labeled exceeds a preset number, the batch processing request method can be used, and when the number of target objects to be labeled does not exceed the preset number, a first processing request for adding a target label can be initiated for each target object.

[0085] On the basis of any of the above embodiments, as shown in Figure 6 this embodiment can also perform periodic labeling, which can specifically include:

[0086] S601, obtaining a preset period and a detection rule;

[0087] S602, every interval of the preset period, judging whether the added label of the target object matches the target object according to the detection rule;

[0088] S603, if it is determined that the labels do not match, creating a label processing task for the target object and adding it to a stream processing platform, so that the first client obtains the label processing task from the stream processing platform and sends a first processing request for adding a target label to the target object.

[0089] In the embodiment, since some conditions of the target object can change, the current label is not applicable, and thus a preset period and a detection rule can be acquired, the target object to which the label is added is detected every preset period, it is judged according to the detection rule whether the added target object matches the target object, if not, a label processing task such as a Dorado task Hive is created for the target object, and is added to a stream processing platform such as Kafka, and then the first client can acquire the label processing task from the stream processing platform and execute the processes of S201-S204, which will not be described herein again.

[0090] The data processing method corresponding to the above embodiment, Figure 7 A structural block diagram of a data processing device provided by an embodiment of the present disclosure is shown. For ease of illustration, only parts related to the embodiment of the present disclosure are shown. Refer to Figure 7 The data processing device 700 includes a receiving unit 701, a processing unit 702, and a sending unit 703.

[0091] The receiving unit 701 is configured to receive a first processing request for adding a target label to a target object sent by a first client.

[0092] The processing unit 702 is configured to acquire a to-be-executed function associated with the target label according to the first processing request, determine a second client set for processing the first processing request according to the to-be-executed function, and acquire a permission identifier of at least one second client in the second client set.

[0093] The sending unit 703 is configured to send a second processing request to the second client set, the second processing request including target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that a second client with the permission identifier in the second client set processes the second processing request.

[0094] The receiving unit 701 is further configured to receive an authorization message sent by a target second client.

[0095] The processing unit 702 is further configured to add the target label to the target object according to the authorization message.

[0096] In one or more embodiments of the present disclosure, when the sending unit 703 sends the second processing request to the second client set, it is configured to:

[0097] If the second client set includes a plurality of second clients, the second processing request is sent to the plurality of second clients, so that the second processing request is displayed only on the interface of the second client with the permission identifier according to the permission identifier; and / or

[0098] If the second client set includes a client of the target object, the second processing request is sent to the client of the target object to display the second processing request on the interface of the client of the target object.

[0099] In one or more embodiments of the present disclosure, the processing unit 702 is further configured to, before sending the second processing request to the second client set:

[0100] The target object information and the target label are checked in at least one of the following manners:

[0101] It is checked whether the region where the target object is located is consistent with the effective region of the target label;

[0102] It is checked whether the target label conflicts with other labels of the target object;

[0103] It is checked whether the first client has the permission to add the target label to the target object.

[0104] In one or more embodiments of the present disclosure, the receiving unit 701 is further configured to, before receiving the first processing request for adding the target label to the target object sent by the first client:

[0105] The target label creation request sent by the first client is received, and the target label creation request includes attribute information of the target label, the attribute information of the target label being attribute information that can be configured by the first client within the permission range corresponding to the first client;

[0106] The processing unit 702 is further configured to create the target label according to the target label creation request and add the target label to a label set, so as to be used by the first client to select the target label to be added to the target object from the label set.

[0107] In one or more embodiments of the present disclosure, the receiving unit 701, when receiving the target label creation request sent by the first client, is configured to:

[0108] The first target label creation request sent by the first client of the first type is received, and the first target label creation request includes first attribute information of the target label, the first attribute information including at least one of the following: label visible region, label effective region, permission identifier of the second client, to-be-executed function, and whether to hide label description; or

[0109] receive a second target tag creation request sent by the first client of the second type, the second target tag creation request comprising second attribute information of the target tag, the second attribute information comprising at least one of the following: whether the tag is visible in the local region, whether the tag is valid in the local region, a permission identifier of the second client, a function to be executed, and whether to hide the tag description.

[0110] In one or more embodiments of the present disclosure, before obtaining the function to be executed associated with the target tag, the receiving unit 701 is further configured to:

[0111] receive an association request of the target tag and the function to be executed sent by the first client;

[0112] The processing unit 702 is further configured to associate the target tag with the function to be executed, and send an association relationship between the target tag and the function to be executed to an execution device of the function to be executed, so that the execution device executes the function to be executed on any object having the target tag.

[0113] In one or more embodiments of the present disclosure, the receiving unit 701 is further configured to receive a function acquisition request sent by the first client;

[0114] The processing unit 702 is further configured to pull a function list from a server according to the function acquisition request, and send the function list to the first client, receive the association request sent by the first client, the association request comprising the function to be executed selected by the administrator from the function list, and associate the target tag with the function to be executed; or

[0115] The receiving unit 701 is further configured to receive the association request sent by the first client, the association request comprising identification information of the function to be executed;

[0116] The processing unit 702 is further configured to find the function to be executed according to the identification information, and associate the target tag with the function to be executed.

[0117] In one or more embodiments of the present disclosure, when receiving a first processing request for adding a target tag to a target object sent by the first client, the receiving unit 701 is configured to:

[0118] receive a batch processing request for adding a tag to a plurality of target objects sent by the first client, the batch processing request comprising a request file, and the request file comprising a plurality of target objects and target tags to be added corresponding to each target object;

[0119] The request file is parsed to obtain the plurality of target objects and the target labels to be added corresponding to each target object, and the plurality of target objects and the target labels to be added corresponding to each target object are added to a message queue to sequentially consume each target object and the target label to be added corresponding to each target object from the message queue.

[0120] In one or more embodiments of the present disclosure, the processing unit 702 is further configured to:

[0121] obtain a preset period and a detection rule;

[0122] every interval of the preset period, determine whether the added label of the target object matches the target object according to the detection rule;

[0123] if it is determined that the added label does not match the target object, create a label processing task for the target object and add the label processing task to a stream processing platform, so that the first client obtains the label processing task from the stream processing platform and sends a first processing request for adding a target label to the target object.

[0124] The data processing device provided in the embodiment can be used to execute the technical solutions of the above method embodiments, and has similar implementation principles and technical effects. Details are not described herein.

[0125] Reference Figure 8 Fig. 8 shows a structural schematic diagram of an electronic device 800 suitable for implementing the embodiments of the present disclosure. The electronic device 800 can be a terminal device or a server. The terminal device can include, but is not limited to, a mobile terminal such as a mobile phone, a notebook computer, a digital broadcast receiver, a personal digital assistant (PDA), a tablet computer (PAD), a portable media player (PMP), a vehicle-mounted terminal (such as a vehicle-mounted navigation terminal), and the like, and a fixed terminal such as a digital TV, a desktop computer, and the like. Figure 8 The electronic device shown is only an example and should not limit the functions and use range of the embodiments of the present disclosure.

[0126] As Figure 8As shown, the electronic device 800 can include a processing device (e.g., a central processor, a graphics processor, etc.) 801 that can perform various suitable actions and processes in accordance with programs stored in a Read Only Memory (ROM) 802 or loaded from a storage device 808 into a Random Access Memory (RAM) 803. Various programs and data required by the electronic device 800 for operation are also stored in the RAM 803. The processing device 801, the ROM 802, and the RAM 803 are connected to each other by a bus 804. An Input / Output (I / O) interface 805 is also connected to the bus 804.

[0127] Generally, the following devices can be connected to the I / O interface 805: input devices 806 including, for example, a touch screen, a touch pad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 807 including, for example, a Liquid Crystal Display (LCD), a speaker, a vibrator, etc.; storage devices 808 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 809. The communication devices 809 can allow the electronic device 800 to communicate wirelessly or wired with other devices to exchange data. Although Figure 8 The electronic device 800 is shown with various devices, but it should be understood that not all of the shown devices are required to be implemented or present. More or fewer devices can alternatively be implemented or present.

[0128] In particular, the processes described above with reference to the flowcharts can be implemented as a computer software program according to embodiments of the present disclosure. For example, embodiments of the present disclosure include a computer program product comprising a computer program carried on a computer readable medium, the computer program containing program code for performing the methods illustrated by the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network through the communication devices 809, or installed from the storage devices 808, or installed from the ROM 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the methods of embodiments of the present disclosure are performed.

[0129] It should be noted that the computer-readable medium in the above disclosure can be a computer-readable signal medium or a computer-readable storage medium or any combination of the two. The computer-readable storage medium may, for example, but is not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or apparatus, or any combination of the above. More specific examples of the computer-readable storage medium can include, but are not limited to, an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, device or apparatus. In the present disclosure, the computer-readable signal medium can include a data signal carried in a baseband or as a part of a carrier wave, which carries computer-readable program code. Such a propagated data signal can take many forms, including but not limited to an electromagnetic signal, an optical signal or any suitable combination of the above. The computer-readable signal medium can also be any computer-readable medium other than the computer-readable storage medium, which can send, propagate or transmit a program for use by or in conjunction with an instruction execution system, device or apparatus. The program code contained in the computer-readable medium can be transmitted by any suitable medium, including but not limited to a wire, a cable, an RF (radio frequency) or the like, or any suitable combination of the above.

[0130] The computer-readable medium described above can be contained in the electronic device described above; or can exist separately and not be assembled into the electronic device.

[0131] The computer-readable medium described above carries one or more programs, which, when executed by the electronic device, cause the electronic device to perform the methods shown in the above embodiments.

[0132] Computer program code for carrying out operations of the present disclosure can be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code can execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection can be made to an external computer (for example, through the Internet using an Internet Service Provider).

[0133] The flow diagrams and the block diagrams in the drawings are meant as possible implementations of systems, methods, and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flow diagrams and the block diagrams can represent a module, a segment, or a portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions noted in the blocks can occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently or the blocks can sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flow diagrams, and combinations thereof, can be implemented by special purpose hardware-based systems that perform the specified functions or operations, or combinations of special purpose hardware and computer instructions.

[0134] The units described in the embodiments of the present disclosure can be implemented by software, or by hardware. In some cases, the name of the unit does not constitute a limitation on the unit itself. For example, the first obtaining unit can also be described as a unit for obtaining at least two Internet protocol addresses.

[0135] The functions described above in the specification of the present disclosure can be performed by one or more hardware logic components. For example, and without limitation, illustrative types of hardware logic components that can be used include Field-programmable Gate Arrays (FPGAs), Program-specific Integrated Circuits (ASICs), Application-specific Standard Products (ASSPs), System-on-a-chip systems (SOCs), Complex Programmable Logic Devices (CPLDs), etc.

[0136] In the context of this disclosure, a machine-readable medium can be a tangible medium that contains or stores a program for use by or in connection with an instruction execution system, apparatus, or device. The machine-readable medium can be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium can include but is not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0137] In a first aspect, according to one or more embodiments of the present disclosure, a data processing method is provided, comprising:

[0138] receiving a first processing request for adding a target tag to a target object sent by a first client;

[0139] obtaining a to-be-executed function associated with the target tag according to the first processing request, determining a second client set for processing the first processing request according to the to-be-executed function, and obtaining a permission identifier of at least one second client in the second client set;

[0140] sending a second processing request to the second client set, the second processing request including target object information, the target tag and the associated to-be-executed function, and the permission identifier of the second client, so that the second client with the permission identifier in the second client set processes the second processing request;

[0141] receiving an authorization message sent by a target second client, and adding the target tag to the target object according to the authorization message.

[0142] According to one or more embodiments of the present disclosure, the sending of the second processing request to the second client set comprises:

[0143] if the second client set includes a plurality of second clients, the second processing request is sent to the plurality of second clients, so that the second processing request is displayed only on the interface of the second client with the permission identifier according to the permission identifier; and / or

[0144] if the second client set includes a client of the target object, the second processing request is sent to the client of the target object, so that the second processing request is displayed on the interface of the client of the target object.

[0145] According to one or more embodiments of the present disclosure, before the sending of the second processing request to the second client set, further comprising:

[0146] The target object information and the target label are checked in at least one of the following manners:

[0147] Checking whether the region where the target object is located is consistent with the effective region of the target label;

[0148] Checking whether the target label conflicts with other labels of the target object;

[0149] Checking whether the first client has the permission to add the target label to the target object.

[0150] According to one or more embodiments of the present disclosure, before the receiving of the first processing request for adding the target label to the target object sent by the first client, further comprising:

[0151] Receiving a target label creation request sent by the first client, the target label creation request comprising attribute information of the target label, the attribute information of the target label being attribute information that can be configured by the first client within the permission range corresponding to the first client;

[0152] According to the target label creation request, the target label is created and added to a label set, so as to be selected by the first client from the label set for adding to the target object.

[0153] According to one or more embodiments of the present disclosure, the receiving of the target label creation request sent by the first client comprises:

[0154] Receiving a first target label creation request of a first type sent by a first client of the first type, the first target label creation request comprising first attribute information of the target label, the first attribute information comprising at least one of the following: a label visible region, a label effective region, a permission identifier of a second client, a to-be-executed function, and whether to hide a label description; or

[0155] Receiving a second target label creation request of a second type sent by a first client of the second type, the second target label creation request comprising second attribute information of the target label, the second attribute information comprising at least one of the following: whether the label is visible in the current region, whether the label is effective in the current region, a permission identifier of a second client, a to-be-executed function, and whether to hide a label description.

[0156] According to one or more embodiments of the present disclosure, before the obtaining of the to-be-executed function associated with the target label, further comprising:

[0157] receive a request for associating a target tag with a function to be executed sent by the first client, and associate the target tag with the function to be executed;

[0158] send the association relationship between the target tag and the function to be executed to an execution device of the function to be executed, so that the execution device executes the function to be executed on any object having the target tag.

[0159] According to one or more embodiments of the present disclosure, the receiving of the request for associating a target tag with a function to be executed sent by the first client and the associating of the target tag with the function to be executed include:

[0160] receiving a function acquisition request sent by the first client, pulling a function list from a server according to the function acquisition request, and sending the function list to the first client, receiving the association request sent by the first client, the association request including the function to be executed selected by the administrator from the function list, and associating the target tag with the function to be executed; or

[0161] receiving the association request sent by the first client, the association request including identification information of the function to be executed, searching for the function to be executed according to the identification information, and associating the target tag with the function to be executed.

[0162] According to one or more embodiments of the present disclosure, the receiving of the first processing request for adding a target tag to a target object sent by the first client includes:

[0163] receiving a batch processing request for adding tags to multiple target objects sent by the first client, the batch processing request including a request file, the request file including multiple target objects and target tags to be added corresponding to each target object;

[0164] parsing the request file to obtain the multiple target objects and the target tags to be added corresponding to each target object, and adding them to a message queue to sequentially consume each target object and the corresponding target tag to be added from the message queue.

[0165] According to one or more embodiments of the present disclosure, the method further includes:

[0166] obtaining a preset period and a detection rule;

[0167] every interval of the preset period, judging whether the added tag of a target object matches the target object according to the detection rule;

[0168] If it is determined that there is no match, a label processing task is created for the target object, and is added to the stream processing platform, so that the first client obtains the label processing task from the stream processing platform and sends a first processing request for adding a target label to the target object.

[0169] In a second aspect, according to one or more embodiments of the present disclosure, a data processing device is provided, comprising:

[0170] a receiving unit configured to receive a first processing request for adding a target label to a target object sent by a first client;

[0171] a processing unit configured to obtain a to-be-executed function associated with the target label according to the first processing request, determine a second client set for processing the first processing request according to the to-be-executed function, and obtain a permission identifier of at least one second client in the second client set;

[0172] a sending unit configured to send a second processing request to the second client set, the second processing request comprising target object information, the target label and the associated to-be-executed function, and the permission identifier of the second client, so that a second client with the permission identifier in the second client set processes the second processing request;

[0173] The receiving unit is further configured to receive an authorization message sent by a target second client.

[0174] The processing unit is further configured to add the target label to the target object according to the authorization message.

[0175] According to one or more embodiments of the present disclosure, when the sending unit sends the second processing request to the second client set, it is configured to:

[0176] If the second client set comprises a plurality of second clients, the second processing request is sent to the plurality of second clients, so that the second processing request is only displayed on the interface of the second client with the permission identifier according to the permission identifier; and / or

[0177] If the second client set comprises a client of the target object, the second processing request is sent to the client of the target object, so that the second processing request is displayed on the interface of the client of the target object.

[0178] According to one or more embodiments of the present disclosure, before the sending unit sends the second processing request to the second client set, the processing unit is further configured to:

[0179] The target object information and the target label are checked in at least one of the following manners:

[0180] Verify whether the region where the target object is located is consistent with the region where the target tag is effective;

[0181] Verify whether the target tag conflicts with other tags of the target object;

[0182] Verify whether the first client has permission to add target tags to the target object.

[0183] According to one or more embodiments of this disclosure, before receiving a first processing request from a first client to add a target tag to a target object, the receiving unit is further configured to:

[0184] The system receives a target tag creation request sent by the first client. The target tag creation request includes the attribute information of the target tag. The attribute information of the target tag is the attribute information that can be configured for the target tag within the permission range corresponding to the first client.

[0185] The processing unit is further configured to create the target tag according to the target tag creation request and add it to the tag set, so that the first client can select the target tag to add to the target object from the tag set.

[0186] According to one or more embodiments of this disclosure, when the receiving unit receives a target tag creation request sent by a first client, it is configured to:

[0187] The system receives a first target tag creation request sent by a first type of first client. The first target tag creation request includes first attribute information of the target tag, which includes at least one of the following: tag visibility area, tag effective area, second client permission identifier, function to be executed, and whether the tag description is hidden; or...

[0188] The system receives a second target tag creation request sent by a first client of the second type. The second target tag creation request includes second attribute information of the target tag. The second attribute information includes at least one of the following: whether the tag is visible in the local area, whether the tag is effective in the local area, the permission identifier of the second client, the function to be executed, and whether the tag description is hidden.

[0189] According to one or more embodiments of this disclosure, before obtaining the function to be executed associated with the target tag, the receiving unit is further configured to:

[0190] Receive the request from the first client to associate the target tag with the function to be executed;

[0191] The processing unit is further configured to associate the target label with the to-be-executed function, and send the association relationship between the target label and the to-be-executed function to an execution device of the to-be-executed function, so that the execution device executes the to-be-executed function on any object having the target label.

[0192] According to one or more embodiments of the present disclosure, the receiving unit is further configured to receive the function acquisition request sent by the first client;

[0193] The processing unit is further configured to pull a function list from a server according to the function acquisition request, and send the function list to the first client, receive the association request sent by the first client, the association request including the to-be-executed function selected by the administrator from the function list, and associate the target label with the to-be-executed function; or

[0194] The receiving unit is further configured to receive the association request sent by the first client, the association request including the identification information of the to-be-executed function;

[0195] The processing unit is further configured to find the to-be-executed function according to the identification information, and associate the target label with the to-be-executed function.

[0196] According to one or more embodiments of the present disclosure, when the receiving unit receives the first processing request for adding a target label to a target object sent by the first client, the receiving unit is configured to:

[0197] Receive a batch processing request for adding labels to multiple target objects sent by the first client, the batch processing request including a request file, and the request file including the multiple target objects and the target labels to be added corresponding to each target object;

[0198] Parse the request file to obtain the multiple target objects and the target labels to be added corresponding to each target object, and add the multiple target objects and the target labels to be added corresponding to each target object to a message queue to sequentially consume the multiple target objects and the target labels to be added corresponding to each target object from the message queue.

[0199] According to one or more embodiments of the present disclosure, the processing unit is further configured to:

[0200] Obtain a preset period and a detection rule;

[0201] Every interval of the preset period, determine whether the added label of a target object matches the target object according to the detection rule;

[0202] If it is determined that there is no match, a label processing task is created for the target object, and the label processing task is added to the stream processing platform, so that the first client obtains the label processing task from the stream processing platform and sends a first processing request for adding a target label to the target object.

[0203] In a third aspect, an electronic device is provided, including: at least one processor and a memory;

[0204] The memory stores computer-executable instructions;

[0205] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the data processing method as described in the first aspect and various possible designs of the first aspect.

[0206] In a fourth aspect, a computer-readable storage medium is provided, and the computer-readable storage medium stores computer-executable instructions, and when a processor executes the computer-executable instructions, the data processing method as described in the first aspect and various possible designs of the first aspect is implemented.

[0207] In a fifth aspect, a computer program product is provided, and the computer program product includes computer-executable instructions, and when a processor executes the computer-executable instructions, the data processing method as described in the first aspect and various possible designs of the first aspect is implemented.

[0208] The above description is merely preferred embodiments of the present disclosure and a description of the principles of the technology applied. Those skilled in the art should understand that the disclosed scope of the present disclosure is not limited to the technical solutions formed by the specific combinations of the above technical features, and should also cover other technical solutions formed by any combination of the above technical features or equivalent features without departing from the above disclosed concept. For example, the above features can be replaced with technical features disclosed in the present disclosure (but not limited to) having similar functions to form technical solutions.

[0209] In addition, although each operation is described in a specific order, this should not be understood as requiring the operations to be performed in the specific order shown or in a sequential order. In certain circumstances, multitasking and parallel processing can be advantageous. Similarly, although several implementation details are included in the above discussion, these should not be interpreted as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments can also be combined in a single embodiment. Conversely, various features described in the context of a single embodiment can also be separated and implemented in multiple embodiments.

[0210] Although the subject matter has been described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A data processing method, characterized in that, include: Receive the first processing request sent by the first client to add a target tag to the target object; According to the first processing request, the function to be executed associated with the target tag is obtained. Based on the preset mapping relationship between the function to be executed and the confirmation process, the second client set for processing the first processing request is dynamically determined according to the function to be executed, and the permission identifier of at least one second client in the second client set is obtained. Different functions to be executed correspond to different confirmation processes and different second client sets. The target object information and the target tag are verified using at least one of the following methods: verifying whether the region where the target object is located is consistent with the region where the target tag is effective; verifying whether the target tag conflicts with other tags of the target object; and verifying whether the first client has the permission to add target tags to the target object. A second processing request is sent to the second client set. The second processing request includes target object information, the target tag and the associated function to be executed, and the permission identifier of the second client, so that the second client in the second client set with the permission identifier processes the second processing request based on the confirmation process corresponding to the function to be executed. Receive the authorization message sent by the second target client, and add the target tag to the target object according to the authorization message; Before obtaining the function to be executed associated with the target tag, the method further includes: Receive a request from the first client to associate a target tag with a function to be executed, and associate the target tag with the function to be executed; The association between the target label and the function to be executed is sent to the execution device of the function to be executed, so that the execution device executes the function to be executed on any object when it detects that any object has the target label.

2. The method according to claim 1, characterized in that, Sending the second processing request to the second client set includes: If the second client set includes multiple second clients, then the second processing request is sent to the multiple second clients to display the second processing request only on the interface of the second client with the permission identifier; and / or If the second client set includes the client of the target object, then the second processing request is sent to the client of the target object to display the second processing request on the client interface of the target object.

3. The method according to claim 1, characterized in that, Before receiving the first processing request from the first client to add a target tag to the target object, the method further includes: The system receives a target tag creation request sent by the first client. The target tag creation request includes the attribute information of the target tag. The attribute information of the target tag is the attribute information that can be configured for the target tag within the permission range corresponding to the first client. Based on the target tag creation request, the target tag is created and added to the tag set for use by the first client to select target tags to add to the target object from the tag set.

4. The method according to claim 3, characterized in that, The step of receiving the target tag creation request sent by the first client includes: The system receives a first target tag creation request sent by a first type of first client. The first target tag creation request includes first attribute information of the target tag, which includes at least one of the following: tag visibility area, tag effective area, second client permission identifier, function to be executed, and whether the tag description is hidden; or... The system receives a second target tag creation request sent by a first client of the second type. The second target tag creation request includes second attribute information of the target tag. The second attribute information includes at least one of the following: whether the tag is visible in the local area, whether the tag is effective in the local area, the permission identifier of the second client, the function to be executed, and whether the tag description is hidden.

5. The method according to claim 1, characterized in that, The step of receiving the association request between the target tag and the function to be executed sent by the first client, and associating the target tag with the function to be executed, includes: Receive a function retrieval request sent by the first client, retrieve a function list from the server according to the function retrieval request, and send the function list to the first client; receive the association request sent by the first client, the association request including the function to be executed selected by the administrator from the function list, and associate the target tag with the function to be executed; or The system receives the association request sent by the first client, the association request including the identification information of the function to be executed, locates the function to be executed based on the identification information, and associates the target tag with the function to be executed.

6. The method according to claim 1, characterized in that, The process of receiving a first processing request from the first client to add a target tag to the target object includes: The system receives a batch processing request from the first client to add tags to multiple target objects. The batch processing request includes a request file, which includes multiple target objects and target tags to be added to each target object. The request file is parsed to obtain the multiple target objects and the target tags to be added to each target object, and added to the message queue so that each target object and the corresponding target tag to be added can be read from the message queue in sequence.

7. The method according to claim 1, characterized in that, The method further includes: Obtain the preset cycle and detection rules; At preset intervals, for target objects with added tags, it is determined whether the added tags match the target object according to the detection rules. If a mismatch is determined, a tag processing task is created for the target object and added to the stream processing platform, so that the first client obtains the tag processing task from the stream processing platform and sends a first processing request to add the target tag to the target object.

8. A data processing device, characterized in that, include: The receiving unit is used to receive the first processing request sent by the first client to add a target tag to the target object; The processing unit is configured to obtain the function to be executed associated with the target tag according to the first processing request, dynamically determine the second client set to process the first processing request based on the preset mapping relationship between the function to be executed and the confirmation process, and obtain the permission identifier of at least one second client in the second client set, wherein different functions to be executed correspond to different confirmation processes and different second client sets. The processing unit is further configured to perform at least one of the following checks on the target object information and the target tag: check whether the region where the target object is located is consistent with the effective region of the target tag; check whether the target tag conflicts with other tags of the target object; check whether the first client has the permission to add target tags to the target object; The sending unit is used to send a second processing request to the second client set. The second processing request includes target object information, the target tag and the associated function to be executed, and the permission identifier of the second client, so that the second client in the second client set with the permission identifier processes the second processing request based on the confirmation process corresponding to the function to be executed. The receiving unit is further configured to receive an authorization message sent by the target second client; The processing unit is further configured to add the target tag to the target object according to the authorization message; Before acquiring the function to be executed associated with the target tag, the receiving unit is further configured to: Receive a request from the first client to associate a target tag with a function to be executed, and associate the target tag with the function to be executed; The association between the target label and the function to be executed is sent to the execution device of the function to be executed, so that the execution device executes the function to be executed on any object when it detects that any object has the target label.

9. An electronic device, characterized in that, include: At least one processor and memory; The memory stores computer-executed instructions; The at least one processor executes computer execution instructions stored in the memory, causing the at least one processor to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, implement the method as described in any one of claims 1-7.

11. A computer program product, characterized in that, Includes computer execution instructions, which, when executed by a processor, implement the method as described in any one of claims 1-7.

Images