Data labeling method and device, electronic equipment, storage medium and program product

Abstract

The invention discloses a data annotation method and device, electronic equipment, a storage medium and a program product. The method can be applied to artificial intelligence, and comprises the steps of obtaining current business data of a business server; based on the target service label information, historical service label information corresponding to the service server is updated, and updated service label information corresponding to the service server is obtained; for each business service object of the business server, determining reference object label information matched with the object information of each business service object from the updated business label information; and for each business service object, performing data labeling processing on the business service object according to the reference object label information matched with the object information of the business service object. In the embodiment of the invention, the data labeling process of each business service object has consistency and repeatability, and does not need to depend on the participation of labeling personnel. Therefore, according to the scheme, the data labeling quality and efficiency can be improved.

Description

Technical Field

[0001] The present application relates to the field of computers, and specifically to a data annotation method, device, electronic device, storage medium, and program product. Background Art

[0002] Data labeling involves tagging or annotating raw data so that computer systems can understand and process it. The current data labeling process requires consideration of the labeler's domain expertise, workload balancing, and labeling quality control. Labelers classify, label, or annotate data according to labeling rules and label definitions.

[0003] However, because current data annotation relies on the subjective judgment of individual annotators, different annotators may have different understandings and interpretations of the same data. This subjective difference may lead to inconsistent annotation results, which in turn affects the objectivity and accuracy of the annotation results, thereby reducing the quality and efficiency of annotation. Summary of the Invention

[0004] The embodiments of the present application provide a data labeling method, device, electronic device, storage medium, and program product, which can improve the quality and efficiency of data labeling.

[0005] This embodiment of the present application provides a data labeling method, including:

[0006] Acquire current business data of the business server, where the current business data includes current target business tag information of the business server and object information of at least one business service object;

[0007] Based on the target business tag information, the historical business tag information corresponding to the business server is updated to obtain the updated business tag information corresponding to the business server;

[0008] For each business service object on the business service side, determine reference object label information that matches the object information of each business service object from the updated business label information;

[0009] For each business service object, data annotation processing is performed on the business service object according to the reference object label information matched with the object information of the business service object, and the object annotation data of the business service object is obtained and output.

[0010] The present application also provides a data annotation device, including:

[0011] A data acquisition unit, configured to acquire current business data of the business server, the current business data including current target business tag information of the business server and object information of at least one business service object;

[0012] An information updating unit, configured to update historical service tag information corresponding to the service server based on the target service tag information, and obtain updated service tag information corresponding to the service server;

[0013] An information matching unit, configured to determine, for each business service object of the business service end, from the updated business tag information, reference object tag information that matches the object information of each business service object;

[0014] The data annotation unit is used to perform data annotation processing on each business service object according to the reference object label information matched with the object information of the business service object, and obtain and output the object annotation data of the business service object.

[0015] In some embodiments, the data acquisition unit includes a request receiving subunit, a channel matching subunit, and a data acquisition subunit:

[0016] A request receiving subunit is used to receive a service data transmission request sent by a service server;

[0017] A channel matching subunit is used to determine a target service data transmission channel that matches the service server from at least one service data transmission channel based on the service data transmission request;

[0018] The data acquisition subunit is used to obtain the current business data of the business server through the target business data transmission channel.

[0019] In some embodiments, the information updating unit includes an information acquiring subunit, a difference determining subunit, and an information updating subunit:

[0020] The information acquisition subunit is used to obtain the historical business tag information corresponding to the business server;

[0021] A difference determination subunit, configured to determine difference service label information between historical service label information and target service label information;

[0022] The information updating subunit is used to update the historical service tag information according to the difference service tag information, and obtain the updated service tag information corresponding to the service server.

[0023] In some embodiments, the difference service tag information includes historical service tag information to be updated and service tag information to be added;

[0024] The information update subunit includes the attribute comparison module, the attribute update module and the information update module:

[0025] An attribute comparison module is used to compare the attribute contents of the historical service tag information to be updated and the target service tag information based on the tag attributes of the historical service tag information to be updated and the tag attributes of the target service tag information, thereby obtaining the attribute contents to be updated in the historical service tag information to be updated and the reference attribute contents corresponding to the attribute contents to be updated in the target service tag information;

[0026] An attribute update module is used to use the attribute content to be referenced to perform attribute update processing on the attribute content to be updated in the historical service tag information to be updated, and obtain the updated historical service tag information;

[0027] The information updating module is used to update the historical service tag information based on the updated historical service tag information and the service tag information to be added, and obtain the updated service tag information corresponding to the service server.

[0028] In some embodiments, the data tagging unit includes a label tagging subunit, a label data acquisition subunit, a label detection subunit, and a label data update subunit:

[0029] The label marking subunit is used to perform data labeling processing on each business service object according to the reference object label information matched with the object information of the business service object, and obtain the current target object label of the business service object;

[0030] The annotation data acquisition subunit is used to obtain the historical object annotation data corresponding to the business service object;

[0031] A label detection subunit is used to detect whether there is a target object history label corresponding to the target object label in the object history label of the historical object annotation data;

[0032] The annotation data update subunit is used to obtain the tag survival time corresponding to the target object tag if the existence of the target object historical tag is detected; use the tag survival time corresponding to the target object tag to update the tag survival time corresponding to the target object historical tag in the historical object annotation data, and obtain and output the object annotation data of the business service object.

[0033] In some embodiments, the annotation data update subunit is also used to merge the target object tag and the tag survival time of the target object tag into the historical object annotation data corresponding to the business service object if no target object historical tag is detected, and obtain and output the object annotation data of the business service object.

[0034] In some embodiments, it further includes a deletion instruction acquisition unit and a first data deletion unit;

[0035] A deletion instruction acquisition unit is used to acquire a data deletion instruction sent by the business server, where the data deletion instruction is a deletion instruction related to a key tag;

[0036] The first data deletion unit is used to delete the business tag information that matches the key tag in the updated business tag information if the data deletion instruction indicates to delete the key tag; if the data deletion instruction indicates to delete the tag annotation data associated with the key tag, determine the target annotation data corresponding to the tag annotation data from the object annotation data corresponding to the business service object; and delete the target annotation data from the object annotation data corresponding to the target object.

[0037] In some embodiments, the data deletion instruction includes the target annotation survival time corresponding to the key tag;

[0038] It also includes a list acquisition unit, an object matching unit, and a second data deletion unit:

[0039] A list acquisition unit is used to acquire an object label survival list of a key tag corresponding to the business service end based on the target label survival time, wherein the object label survival list includes a preset survival time and a surviving business service object corresponding to the preset survival time;

[0040] An object matching unit, configured to determine, based on a preset survival time, a target surviving object that matches the target marked survival time from an object marked survival list;

[0041] The second data deletion unit is configured to delete the tag annotation data associated with the key tag in the object annotation data corresponding to the target surviving object if the data deletion instruction indicates to delete the tag annotation data associated with the key tag.

[0042] In some embodiments, it further includes a query instruction acquisition unit, a query strategy determination unit, a query data determination unit, and a query data sending unit;

[0043] A query instruction acquisition unit is used to acquire a data query instruction sent by the business server, where the data query instruction includes a tag to be queried;

[0044] A query strategy determination unit is configured to determine a target query strategy from a tag query strategy and an object query strategy based on a data query instruction, wherein the tag query strategy is used to query business service objects marked with tags to be queried, and the object query strategy is used to query tags to be queried for business service objects indicated in the data query instruction;

[0045] A query data determining unit, configured to determine target annotated query data from the object annotated data of the business service object according to a target query strategy;

[0046] The query data sending unit is used to send target annotation query data to the business server.

[0047] In some embodiments, the query data determining unit includes a time obtaining subunit, a label list determining subunit, and a first query data determining subunit:

[0048] The time acquisition subunit is used to obtain the query annotation survival time corresponding to the tag to be queried from the data query instruction if the target query strategy is the tag query strategy;

[0049] A label list determination subunit is used to determine a target object label list from object label lists corresponding to each preset survival time of the tag to be queried based on the query label survival time;

[0050] The first query data determining subunit is configured to determine target annotation query data from the object annotation data of each business service object in the target object annotation list according to the tag to be queried.

[0051] In some embodiments, the query data determination unit includes an object acquisition subunit and a second query data determination subunit:

[0052] The object acquisition subunit is used to acquire the target business service object from the data query instruction if the target query strategy is an object query strategy;

[0053] The second query data determining subunit is configured to determine target annotated query data from the object annotated data of the target business service object according to the tag to be queried.

[0054] An embodiment of the present application also provides an electronic device, including a processor and a memory, wherein the memory stores multiple instructions; the processor loads instructions from the memory to execute the steps of any data labeling method provided in the embodiment of the present application.

[0055] An embodiment of the present application also provides a computer-readable storage medium, which stores multiple instructions, and the instructions are suitable for a processor to load to execute the steps in any data labeling method provided in the embodiment of the present application.

[0056] An embodiment of the present application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, implements the steps of any data labeling method provided in the embodiment of the present application.

[0057] The embodiment of the present application can obtain the current business data of the business service end, and the current business data includes the current target business tag information of the business service end and the object information of at least one business service object; based on the target business tag information, the historical business tag information corresponding to the business service end is updated to obtain the updated business tag information corresponding to the business service end; for each business service object of the business service end, the reference object tag information that matches the object information of each business service object is determined from the updated business tag information; for each business service object, the business service object is data labeled according to the reference object tag information that matches the object information of the business service object, and the object labeling data of the business service object is obtained and output.

[0058] In this application, after obtaining the current business data of the business service end, the current target business tag information of the business service end in the current business data can be first used to timely update the historical business tag information corresponding to the business service end, which can ensure that the updated business tag information obtained can meet the current business needs of the business service end. Subsequently, when performing data annotation on each business service object of the business service end in the current business data, the updated business tag information is used to match the object information of each business service object, and the reference object tag information obtained by matching can ensure that the business service object is correctly annotated. This data annotation process for each business service object is consistent and repeatable, does not require the participation of annotators, reduces the impact of subjective differences between annotators on the annotation results, ensures that the data annotation process can be more accurate and efficient, and improves the quality and efficiency of data annotation. BRIEF DESCRIPTION OF THE DRAWINGS

[0059] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative work.

[0060] Figure 1a Schematic diagram of a data annotation method according to an embodiment of the present invention;

[0061] Figure 1b This is a flow chart of the data annotation method provided in the embodiment of the present application;

[0062] Figure 2a This is a schematic diagram of the data annotation method provided in an embodiment of the present application being applied in a tagging hosting platform scenario;

[0063] Figure 2b This is a flowchart of the label registration method for data annotation provided in an embodiment of the present application;

[0064] Figure 2c This is a schematic diagram of the interaction between the business service end and the marking hosting platform provided in an embodiment of the present application;

[0065] Figure 2d This is a functional diagram of the data definition layer provided in an embodiment of the present application;

[0066] Figure 2e This is a schematic diagram of the reference method of the annotation data provided in the embodiment of the present application;

[0067] Figure 2f This is the data transmission intention between the business service end and the tag hosting platform provided in the embodiment of the present application;

[0068] Figure 2g This is a schematic diagram of the service data transmission channel and various data management modules provided in an embodiment of the present application;

[0069] Figure 2h is a schematic diagram of a data association organization module provided in an embodiment of the present application;

[0070] Figure 2i This is a schematic diagram of the first tag deletion provided in the embodiment of the present application;

[0071] Figure 2j This is a second tag deletion schematic diagram provided in an embodiment of the present application;

[0072] Figure 2k This is a schematic diagram of label query provided by an embodiment of the present application;

[0073] Figure 2l This is a query data association diagram provided by an embodiment of the present application;

[0074] Figure 2m This is a schematic diagram of label addition provided in an embodiment of the present application;

[0075] Figure 3 Schematic diagram of the structure of the data labeling device provided in an embodiment of the present application;

[0076] Figure 4 It is a structural diagram of the server provided in an embodiment of the present application. DETAILED DESCRIPTION

[0077] The following will be combined with the drawings in the embodiments of this application to clearly and completely describe the technical solutions in the embodiments of this application. Obviously, the embodiments described are only part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without making creative efforts are within the scope of protection of this application.

[0078] Embodiments of the present application provide a data annotation method, apparatus, electronic device, storage medium, and program product.

[0079] The data annotation device can be integrated into an electronic device, which can be a terminal, a server, or other device. The terminal can be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, or a personal computer (PC); the server can be a single server or a server cluster consisting of multiple servers.

[0080] In some embodiments, the data labeling device can also be integrated into multiple electronic devices. For example, the data labeling device can be integrated into multiple servers, and the data labeling method of the present application can be implemented by multiple servers.

[0081] In some embodiments, the server may also be implemented in the form of a terminal.

[0082] In the embodiments of the present application, the term "module" or "unit" refers to a computer program or a part of a computer program that has a predetermined function and works together with other related parts to achieve a predetermined goal, and can be implemented in whole or in part by using software, hardware (such as processing circuits or memories) or a combination thereof. Similarly, a processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be part of an overall module or unit that includes the function of the module or unit.

[0083] It can be understood that in the specific implementation of this application, when the embodiment of this application is applied to specific products or technologies, user permission or consent is required for the target business tag information and object information of each business service object in the current business data, and the collection, use and processing of relevant data need to comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0084] For example, reference Figure 1aThe electronic device V can obtain the current business data of the business service end W, where the current business data includes the current target business tag information of the business service end and the object information of at least one business service object; based on the target business tag information, the historical business tag information corresponding to the business service end W is updated to obtain the updated business tag information corresponding to the business service end W; for each business service object of the business service end W, the reference object tag information that matches the object information of each business service object is determined from the updated business tag information; for each business service object, data annotation processing is performed on the business service object according to the reference object tag information that matches the object information of the business service object, and the object annotation data of the business service object is obtained and output.

[0085] Among them, after obtaining the current business data of the business service end, the current target business label information of the business service end in the current business data is first used to timely update the historical business label information corresponding to the business service end, which can ensure that the updated business label information can meet the current business needs of the business service end. Subsequently, when performing data annotation on each business service object of the business service end in the current business data, the updated business label information is used to match the object information of each business service object. By matching the obtained reference object label information, it can be ensured that the business service object is correctly labeled. This data annotation process for each business service object is consistent and repeatable, does not require the participation of annotation personnel, reduces the impact of subjective differences between annotation personnel on the annotation results, ensures that the data annotation process can be more accurate and efficient, and improves the quality and efficiency of data annotation.

[0086] In addition, by automatically updating historical business tag information and applying it to the data annotation process, incorrect annotations can be avoided and the consistency and reliability of data annotation can be improved.

[0087] It should be noted that the serial numbers of the following embodiments are not intended to limit the preferred order of the embodiments.

[0088] Artificial intelligence (AI) is a technology that uses digital computers to simulate human-like perception of the environment, acquisition, and application of knowledge. This technology enables machines to possess human-like perception, reasoning, and decision-making capabilities. Foundational AI technologies generally include sensors, specialized AI chips, cloud computing, distributed storage, big data processing, operating / interaction systems, and mechatronics. AI software technologies primarily encompass computer vision, speech processing, natural language processing, as well as machine learning / deep learning, autonomous driving, and smart transportation.

[0089] Machine learning (ML) is a multidisciplinary field that encompasses probability theory, statistics, approximation theory, convex analysis, and algorithmic complexity theory. It specifically studies how computers can simulate or implement human learning behaviors to acquire new knowledge or skills and reorganize existing knowledge structures to continuously improve their performance. Machine learning is at the core of artificial intelligence and the fundamental way to make computers intelligent. Its applications span all areas of AI. Machine learning and deep learning typically include techniques such as artificial neural networks, belief networks, reinforcement learning, transfer learning, inductive learning, and learning through demonstration.

[0090] With the research and progress of artificial intelligence technology, artificial intelligence technology has been studied and applied in many fields, such as common smart homes, smart wearable devices, virtual assistants, smart speakers, smart marketing, unmanned driving, automatic driving, drones, robots, smart medical care, smart customer service, Internet of Vehicles, automatic driving, smart transportation, etc. It is believed that with the development of technology, artificial intelligence technology will be applied in more fields and play an increasingly important role.

[0091] In this embodiment, a data annotation method based on machine learning involving artificial intelligence is provided, such as Figure 1b As shown, the specific process of the data annotation method can be as follows:

[0092] 101. Acquire current business data of a business server, where the current business data includes current target business tag information of the business server and object information of at least one business service object.

[0093] A business server is a server-side system that provides specific business functions and communicates with clients supporting those services to meet their business needs. For example, a business server could be a server-side system for an instant messaging application, a video player application, a gaming application, an e-commerce platform, or an AI model to be trained.

[0094] The service server may also include but is not limited to mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc. The embodiments of the present application can be applied to various scenarios, including but not limited to cloud technology, artificial intelligence, smart transportation, assisted driving, etc.

[0095] Current business data refers to the data currently held by the business server that is relevant to a specific business. For example, current business data can be data currently held by the server system of an instant messaging application, video playback application, gaming application, e-commerce platform, or a machine learning model to be trained.

[0096] The target service tag information is the relevant service tag information required to mark the relevant service data of the current service server. For example, the target service tag information may not contain any tag information, but may also include service tag information newly added by the service server, service tag information that needs to be updated, service tag information that needs to be deleted, etc.

[0097] The target service tag information may specifically include tag identifier, tag name, parent tag, tag type, associated tag, tag registration time, tag lifetime, etc.

[0098] Business service objects are objects that need to be annotated in the relevant business data of the current business server. For example, business service objects can be products provided by the business server (such as functional applications in instant messaging applications, functional applications or video data in video playback applications, virtual characters or virtual props in game applications, functional applications on e-commerce platforms, etc.), users of clients communicating with the business server, samples used to train artificial intelligence models, and so on.

[0099] Object information is information related to business service objects.

[0100] For example, if the business service object is a product provided by the business service end, the object information may be information on the usage status of the business service object. The usage status may be usage frequency, resource allocation information when using the business service object, target user groups, etc.

[0101] If the business service object is a user of a client communicating with the business server, the object information may be information related to the user's use of the services provided by the business server. For example, the object information may specifically include the user's needs, preferences, and basic information.

[0102] If the business service object is a sample used to train an artificial intelligence model, the object information can be information describing the sample, or description information of the object of interest in the sample, and so on.

[0103] In some embodiments, in order to support obtaining current service data sent by different service servers, obtaining the current service data of the service server includes:

[0104] Receive business data transmission requests sent by the business server;

[0105] Based on the service data transmission request, determining a target service data transmission channel that matches the service server from at least one service data transmission channel;

[0106] Obtain the current business data of the business server through the target business data transmission channel.

[0107] The service data transmission request is a request sent by the service server when sending service data, and the type of the service data transmission request is related to the type of the service server.

[0108] For example, if the business server is a web application, the business data transmission request is usually a request based on the Hypertext Transfer Protocol (HTTP protocol), and methods such as get or post can be used.

[0109] If the business server is an application based on a consumer queue, the business data transmission request is usually implemented by the business server through a message queue.

[0110] If the business server is a distributed application, the business data transmission request is usually implemented by the business server through the remote procedure call protocol.

[0111] If the business server is a mobile application, the business data transmission request is usually implemented by the business server through an application programming interface (API).

[0112] A business data transmission channel is a channel provided for transmitting business data. For example, a business data transmission channel can implement data transmission by using the interfaces and functions provided by a software development kit (SDK). Using the SDK, specific functions can be directly called to connect data with the business server. A business data transmission channel can also implement data transmission by calling an API. Using the API, data can be connected with the business server through network requests and responses. A business data transmission channel can also implement data connection by using a web page. The web page can provide functions such as data entry, query, and display, etc.

[0113] The target business data transmission channel is a business data transmission channel obtained based on the business data transmission request and matched with the business server.

[0114] For example, if the business data transmission request is a request based on the HTTP protocol or a request sent by an application based on a consumer queue, the target business data transmission channel can be any of the channels such as SDK, API, Web page, etc.

[0115] If the business data transmission request is a request sent by a distributed application or a mobile application, the target business data transmission channel may be a channel of the SDK, API, or other type.

[0116] In some embodiments, different business service terminals may match different target business data transmission channels.

[0117] In some embodiments, current business data of at least one business server may be obtained simultaneously.

[0118] In some embodiments, the current service data includes at least one target service tag information of the service server and at least one of object information of the service service object.

[0119] 102. Based on the target service tag information, update the historical service tag information corresponding to the service server to obtain updated service tag information corresponding to the service server.

[0120] The historical service tag information is service tag information related to the service server recorded before the current service data is acquired. For example, the historical service tag information may include historical service tag information that does not need to be updated, historical service tag information that needs to be updated, and historical service tag information that needs to be deleted. In addition, the target service tag information may also contain newly added service tag information relative to the historical service tag information.

[0121] The updated service tag information is the historical service tag information after being updated by the target service tag information.

[0122] For example, the target service tag information is compared with the historical service tag information.

[0123] If the target service tag information A and the historical service tag information a have some identical contents, such as the same tag identifier but different tag names, then the historical service tag information a is the historical service tag information that needs to be updated. The target service tag information A is used to update the historical service tag information a so that the tag name in the updated service tag information a' is the same as the target service tag information A.

[0124] If the historical service tag information does not include the target service tag information B, the target service tag information B is the historical service tag information that needs to be added. The target service tag information B is used to update the historical service tag information so that the updated service tag information includes the target service tag information B.

[0125] If the target service label information C is indicated as historical service label information that needs to be deleted, and the historical service label information C is the same as the target service label information C, the target service label information C is used to update the historical service label information C, and the updated service label information does not include the historical service label information C.

[0126] Historical service tag information that exists but is not mentioned in the target service tag information is service tag information that does not need to be updated. For example, the target service tag information includes target service tag information A, target service tag information B, and target service tag information C, while the historical service tag information includes historical service tag information a, historical service tag information c, and historical service tag information d. Since there is no target service tag information in the target service tag information that matches historical service tag information d, historical service tag information d is service tag information that does not need to be updated.

[0127] In some embodiments, in order to update the historical service tag information corresponding to the service server so as to use the updated service tag information to annotate data, the historical service tag information corresponding to the service server is updated based on the target service tag information to obtain the updated service tag information corresponding to the service server, including:

[0128] Get the historical business tag information corresponding to the business server;

[0129] Determine the difference between the historical service label information and the target service label information;

[0130] According to the difference business tag information, the historical business tag information is updated to obtain the updated business tag information corresponding to the business server.

[0131] The difference service tag information is service tag information that is different between the historical service tag information and the target service tag information.

[0132] For example, different service tag information can be service tag information that has some of the same content as the target service tag information, which can be considered historical service tag information that needs to be updated. Alternatively, target service tag information that does not appear in the historical service tag information can be considered newly added service tag information. Alternatively, target service tag information that indicates the need for deletion, while historical service tag information that has not yet been deleted, can be considered historical service tag information that needs to be deleted.

[0133] In some embodiments, in order to quickly determine the difference service tag information, determining the difference service tag information between the historical service tag information and the target service tag information includes:

[0134] The tag identifier of the historical service tag information is compared with the tag identifier of the target service tag information to obtain difference service tag information.

[0135] The tag identifier of the historical service tag information refers to a unique identifier of the historical service tag information.

[0136] The tag identifier of the target service tag information refers to a unique identifier of the target service tag information.

[0137] For example, the tag identifier of the historical service tag information and the tag identifier of the target service tag information may be any form of unique identifier, such as a number, a combination of letters, a hash value, and the like.

[0138] For example, since the target service tag information can only be newly added service tag information, service tag information that needs to be updated, or service tag information that needs to be deleted by the service server, if the tag identifier of the target service tag information is the same as the tag identifier of the historical service tag information, the historical service tag information is differential service tag information, which includes the historical service tag information that needs to be updated and the historical service tag information that needs to be deleted. If the tag identifier of the target service tag information is different from the tag identifier of the historical service tag information, the differential service tag information is the target service tag information, that is, the service tag information that needs to be newly added.

[0139] In some embodiments, in order to update historical service label information using differential service label information, the differential service label information includes historical service label information to be updated and service label information to be added;

[0140] Based on the difference business tag information, the historical business tag information is updated to obtain the updated business tag information corresponding to the business server, including:

[0141] Based on the tag attributes of the historical service tag information to be updated and the tag attributes of the target service tag information, the attribute contents of the historical service tag information to be updated and the target service tag information are compared to obtain the attribute contents to be updated in the historical service tag information to be updated and the referenced attribute contents corresponding to the attribute contents to be updated in the target service tag information;

[0142] Using the attribute content to be referenced, the attribute content to be updated in the historical service tag information to be updated is processed to obtain the updated historical service tag information;

[0143] Based on the updated historical service tag information and the service tag information to be added, the historical service tag information is updated to obtain the updated service tag information corresponding to the service server.

[0144] The historical service tag information to be updated is historical service tag information that contains some of the service tag content in the target service tag information. For example, the historical service tag information to be updated can be historical service tag information that needs to be updated or deleted. The service tag information to be added is the target service tag information that does not appear in the historical service tag information.

[0145] The tag attributes of the historical service tag information to be updated are used to describe the characteristics of the historical service tag information to be updated. For example, the tag attributes of the historical service tag information to be updated may include the tag identifier, tag name, parent tag, tag type, associated tags, tag registration time, tag lifetime, etc.

[0146] The tag attributes of the target service tag information are used to describe the characteristics of the target service tag information. The tag attributes of the target service tag information correspond one-to-one to the tag attributes of the historical service tag to be updated.

[0147] Attribute content refers to the specific content corresponding to a tag attribute. For example, attribute content includes the specific identifier corresponding to the tag identifier, the specific name corresponding to the tag name, the tag identifier corresponding to the parent tag, the category to which the tag type belongs, the tag identifier corresponding to the associated tag, the specific time range corresponding to the tag registration time, the specific time range corresponding to the tag lifetime, and so on.

[0148] The attribute content to be updated is the attribute content in the historical service tag information to be updated that is different from the target service tag information for the same tag attribute.

[0149] For example, since the tag identifier is the unique identifier of the service tag information, if the tag identifier of the historical service tag information to be updated is the same as the tag identifier of the target service tag information, the attribute contents of the historical service tag information to be updated and the target service tag information are compared one by one for all tag attributes other than the tag identifier. The attribute contents in the historical service tag information to be updated that are different from those in the target service tag information are the attribute contents to be updated. The attribute contents to be referenced are the attribute contents of the tag attributes corresponding to the attribute contents to be updated in the target service tag information corresponding to the historical service tag information to be updated, where the historical service tag information to be updated and the target service tag information corresponding to the historical service tag information to be updated have the same tag identifier.

[0150] For example, if the tag attribute corresponding to the attribute content to be updated is the target tag attribute, then the attribute content to be referenced is the specific name corresponding to the target tag attribute in the target business tag information corresponding to the historical business tag information to be updated, where the target tag attribute can be the tag name, parent tag, tag type, associated tag, tag registration time, tag survival time, etc.

[0151] The updated historical service tag information refers to historical service tag information that is consistent with the target service tag information after the attribute content to be updated in the historical service tag information to be updated is updated according to the attribute content to be referenced.

[0152] The updated service tag information refers to the final service tag information obtained after updating the updated historical service tag information in combination with the service tag information to be added. The updated service tag information includes the unupdated historical service tag information, the updated historical service tag information, and the service tag information to be added.

[0153] 103. For each business service object of the business service end, determine reference object label information that matches the object information of each business service object from the updated business label information.

[0154] The reference object label information is the business label information in the updated business label information that matches the object information of the business service object.

[0155] In some embodiments, in order to obtain reference object tag information that matches the object information of the business service object, the updated business tag information includes preset object information corresponding to the preset tag;

[0156] For each business service object on the business service side, reference object label information that matches the object information of each business service object is determined from the updated business label information, including:

[0157] For each business service object of the business service end, if the preset object information corresponding to the preset tag in the updated business tag information matches the object information of the business service object, the updated business tag information is used as the reference object tag information.

[0158] The preset tag is a tag pre-set in the updated service tag information.

[0159] The preset object information is the object information corresponding to the preset tag preset in the updated business tag information. For example, if the business service object is a product provided by the business service end and the object information is information about the usage status of the business service object, the preset object information is the preset usage status information.

[0160] If the business service object is a user of a client communicating with the business server, and the object information is information related to the user using a service provided by the business server, then the preset object information is pre-set user service information.

[0161] If the business service object is a sample used to train an artificial intelligence model and the object information is information describing the sample, then the preset object information is pre-set information describing the sample.

[0162] 104. For each business service object, perform data annotation processing on the business service object according to the reference object label information matched with the object information of the business service object, and obtain and output the object annotation data of the business service object.

[0163] The object annotation data is data obtained by annotating the business service object with reference to the object tag information, and may include relevant content in the reference object tag information.

[0164] For example, object annotation data may include the tag identifier of the preset tag in the reference object tag information. In addition, it may also include the tag name, parent tag, tag type, associated tag, tag registration time, tag survival time, and annotation data obtained by the business service object outside the current one, etc.

[0165] In some embodiments, considering that a business service object may be marked with the same object tag at different marking times, in order to avoid redundant storage of the object tag, for each business service object, data marking processing is performed on the business service object based on reference object tag information matched with the object information of the business service object, and object marking data of the business service object is obtained and output, including:

[0166] For each business service object, perform data labeling on the business service object based on the reference object label information matched with the object information of the business service object to obtain the current target object label of the business service object;

[0167] Get the historical object annotation data corresponding to the business service object;

[0168] Detect whether there is a target object history label corresponding to the target object label in the object history label of the historical object annotation data;

[0169] If the target object history tag is detected, the tag survival time corresponding to the target object tag is obtained;

[0170] The tag survival time corresponding to the target object tag is used to update the tag survival time corresponding to the target object historical tag in the historical object annotation data, and the object annotation data of the business service object is obtained and output.

[0171] The target object label is a label obtained by labeling the business service object with reference to the object label information.

[0172] The historical object annotation data is the data obtained by annotating the business service objects before.

[0173] For example, the historical object annotation data corresponding to the business service object may be an empty set, and may also include at least one object history tag and the tag lifetime corresponding to each object history tag.

[0174] The object history label is the label obtained by previously annotating the business service object with data.

[0175] The target object history tag is an object history tag corresponding to the target object tag, wherein the tag identifier of the target object history tag is the same as the tag identifier of the target object tag.

[0176] The tag lifetime corresponding to the target object tag refers to the length of time that the target object tag currently marked on the business service object needs to remain valid.

[0177] The tag lifetime corresponding to the target object history tag refers to the length of time that the business service object needs to keep the target object history tag valid before the tag is marked.

[0178] For example, if the label survival time corresponding to the historical label of the target object in the historical object annotation data is X-year-x-month-xx-day - X-year-x-month-xxx-day, the label survival time corresponding to the currently updated historical label of the target object is X-year-x-month-s-day, and the label survival time corresponding to the target object label is Y days, then the label survival time obtained after the label survival time corresponding to the historical label of the target object is updated is X-year-x-month-s-day - X-year-x`-month-s`-day, and the distance between X-year-x-month-s-day and X-year-x`-month-s`-day is Y days.

[0179] In some embodiments, in order to reflect the frequency of the business service object having the target object history tag, the tag survival time corresponding to the target object tag is used. After the tag survival time corresponding to the target object history tag in the historical object annotation data is updated, the following steps are further included:

[0180] Get the number of updates of the tag lifetime corresponding to the historical tag of the target object;

[0181] Based on the target object label, the update times are updated to obtain the target update times.

[0182] The number of updates is the number of times the tag survival time corresponding to the historical tag of the target object is updated before.

[0183] The target update number is the number of times the update number is updated after the tag survival time corresponding to the target object's historical tag is updated. The target update number = the update number + 1.

[0184] In some embodiments, it further includes:

[0185] Send the target update number to the business service end so that the business service end can manage the business service object according to the target update number. In some embodiments, in order to add a new object tag to the business service object, the following is also included:

[0186] If no historical tag of the target object is detected, the target object tag and the tag lifetime of the target object tag are merged into the historical object tag data corresponding to the business service object, and the object tag data of the business service object is obtained and output.

[0187] For example, the tag identifier of the target object tag and the tag survival time of the target object tag are merged into the historical object annotation data corresponding to the business service object. In addition, the tag name, parent tag, tag type, associated tag, tag registration time, etc. in the reference object tag information used to annotate the target object tag can also be merged into the historical object annotation data.

[0188] In some embodiments, in order to clean the object annotation data, the following steps are further included:

[0189] Get the data deletion instruction sent by the business server. The data deletion instruction is the deletion instruction related to the key tag.

[0190] If the data deletion instruction indicates to delete the key tag, the business tag information matching the key tag in the updated business tag information is deleted;

[0191] If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, then determining the target annotation data corresponding to the tag annotation data from the object annotation data corresponding to the business service object;

[0192] The target annotation data is deleted from the object annotation data corresponding to the target object.

[0193] A data deletion instruction is a command sent by the service server to delete data associated with a tag. For example, a data deletion instruction can be an instruction to delete a specific tag, an instruction to delete an object tagged with a specific tag, or an instruction to delete an object tagged with a specific tag, etc.

[0194] A key tag is a specific tag specified in a data deletion instruction. For example, a key tag can be a tag that needs to be deleted, or a tag that is specified for deleting specific annotated data. Specifically, the annotated data can be the annotated data of the key tag, or the annotated data of an associated tag of the key tag, and so on.

[0195] Tag annotation data refers to the data of tag annotation objects related to key tags. For example, tag annotation data can be the annotation data of key tags, or the annotation data of tags associated with key tags, etc.

[0196] For example, if a key tag corresponds to a subtag, it is also necessary to traverse each subtag of the key tag. The tag annotation data includes the annotation data of the key tag and the annotation data of its corresponding subtag.

[0197] If the associated tag of the key tag corresponds to a subtag, it is also necessary to traverse the subtags of the associated tag of the key tag. The tag annotation data includes the annotation data of the associated tag of the key tag and the annotation data of its corresponding subtag.

[0198] The target annotated data is the annotated data associated with the key tag to be deleted.

[0199] For example, if the data deletion instruction indicates to delete the tag annotation data of the key tag M, the tag identifier, tag name, tag lifetime, associated tags, etc. of the key tag M are determined from the object annotation data corresponding to the business service object as the target annotation data.

[0200] If the data deletion instruction indicates to delete the annotation data of the associated tags of the key tag M, and the associated tags of the key tag M may include at least one tag, the tag identifier, tag name, tag lifetime, associated tags, etc. of each tag associated with the key tag M are determined from the object annotation data corresponding to the business service object as the target annotation data.

[0201] In some embodiments, to facilitate cleaning of object annotation data, the data deletion instruction includes the target annotation survival time corresponding to the key tag;

[0202] After receiving the data deletion instruction sent by the business server, it also includes:

[0203] Based on the target label survival time, obtain the object label survival list of the key tag corresponding to the business service end, the object label survival list includes the preset survival time and the surviving business service object corresponding to the preset survival time;

[0204] Based on the preset survival time, determine the target survival object that matches the target marked survival time from the object marked survival list;

[0205] If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, the tag annotation data associated with the key tag in the object annotation data corresponding to the target surviving object is deleted.

[0206] The target tag survival time is the tag survival time of the key tag indicated in the data deletion instruction after the tag is marked. For example, the target tag survival time can be the tag expiration time of the key tag after the tag is marked. Specifically, it can be the expiration time of the tag, such as expiration time of 1 day, expiration time of 1 week, expiration time of 1 month, etc. It can also be the tag expiration countdown of the key tag after the tag is marked, such as expiration time of 1 day, 1 week, 1 month, etc.

[0207] The preset expiration time is the pre-set time of the tag. For example, the preset expiration time can be a preset time of 1 day, 1 week, 1 month, etc., or a preset expiration time of 1 day, 1 week, 1 month, etc., or a preset expiration countdown of 1 day, 1 week, 1 month, etc.

[0208] A surviving business service object means that after a key tag is marked on the business service object, the tag survival time of the key tag matches the preset survival time, so that the business service object is regarded as a surviving business object.

[0209] For example, if the label survival time of the key label of the business service object is X year x month s day - X year x` month s` day, and X year x` month s` day is regarded as the marking expiration time of the key label, the current time for obtaining the data deletion instruction is X year x` month t day, when the preset survival time includes the preset expiration of 1 day, the preset expiration of 1 week, the preset expiration of 1 month, etc., when X year x` month t day exceeds X year x` month s` day by 1 day, the business service object is regarded as the surviving business service object corresponding to the preset expiration of 1 day, and so on, to obtain the surviving business service objects corresponding to each preset survival time.

[0210] The object annotation survival list refers to the annotation information list of the key tags corresponding to the business service end obtained based on the target annotation survival time. This list includes the preset survival time of the key tags and the corresponding surviving business service objects, which helps to manage and detect the validity period of the key tags and ensure the accuracy and effectiveness of the object annotation data.

[0211] The target survival object refers to the survival business service object corresponding to the preset survival time that matches the target marked survival time.

[0212] In some embodiments, in order to enable the business server to query the corresponding object annotation data, the following is also included:

[0213] Get the data query instruction sent by the business server, which includes the tag to be queried;

[0214] Based on the data query instruction, determine the target query strategy from the tag query strategy and the object query strategy. The tag query strategy is used to query the business service objects marked with the tags to be queried. The object query strategy is used to query the tags to be queried of the business service objects indicated in the data query instruction.

[0215] Determine target annotation query data from the object annotation data of the business service object according to the target query strategy;

[0216] Send target annotation query data to the business server.

[0217] The data query instruction is a query instruction sent in the object annotation data of each business service object corresponding to the query business service end.

[0218] The tag to be queried refers to the tag identifier to be queried, wherein the data query instruction may include at least one tag to be queried. When the tag to be queried is a parent tag, when querying the tag to be queried, the child tags of the tag to be queried must also be queried.

[0219] For example, the business service end corresponds to at least one updated business tag information, each updated business tag information includes a tag identifier, and the data query instruction indicates that there is at least one tag identifier in the updated business tag information, so that the object annotation data related to the tag identifier can be obtained through the data query instruction.

[0220] The target query strategy is the query strategy that matches the data query instruction among the tag query strategy and the object query strategy.

[0221] For example, if the business service object does not exist in the data query instruction, the tag query strategy is used as the target query strategy to instruct to query the business service object with the tag to be queried.

[0222] If there is a business service object in the data query instruction, the object query strategy is used as the target query strategy to query the to-be-queried tag of the business service object indicated in the data query instruction.

[0223] The target annotation query data is the data obtained by querying the object annotation data of the business service object according to the target query strategy.

[0224] For example, if the target query strategy is a tag query strategy, the business service object with the tag to be queried is obtained, and the data related to the tag to be queried is obtained from the object annotation data of this type of business service object as the target annotation query data. The target annotation query data includes the tag name, parent tag, tag type, associated tag, tag registration time, tag survival time and other data of the tag to be queried.

[0225] If the target query strategy is an object query strategy, data related to the tag to be queried is obtained from the object annotation data of the business service object indicated in the data query instruction as target annotation query data.

[0226] In some embodiments, in order to use the tag query strategy to query the object annotation data corresponding to the business service end, according to the target query strategy, the target annotation query data is determined from the object annotation data of all business service objects, including:

[0227] If the target query strategy is a tag query strategy, the query annotation survival time corresponding to the tag to be queried is obtained from the data query instruction;

[0228] Based on the query annotation survival time, determine the target object annotation list from the object annotation lists corresponding to each preset survival time of the tag to be queried;

[0229] According to the tag to be queried, target annotation query data is determined from the object annotation data of each business service object in the target object annotation list.

[0230] The query tag lifetime indicates the query range of the tag lifetime of the tag to be queried. For example, the query tag lifetime can refer to the most recent month, week, day, etc. after the tag to be queried is tagged, or it can refer to the tag expiration time after the tag to be queried is tagged, etc.

[0231] The object annotation list corresponding to the preset survival time refers to a list of business service objects whose corresponding tag survival time matches the preset survival time after the tag to be queried is annotated.

[0232] For example, the object tag list corresponding to each preset survival time of the tag to be queried can refer to the object tag list corresponding to the preset 1 day, 1 week, 1 month, etc., or the object tag list corresponding to the preset expiration time of 1 day, 1 week, 1 month, etc., or the object tag list corresponding to the preset expiration countdown of 1 day, 1 week, 1 month, etc., and so on.

[0233] For example, if the object labeling list corresponding to each preset survival time refers to the preset object label list corresponding to 1 day, 1 week, 1 month, etc., when the label survival time of the label to be queried of the business service object is X year x month s day - X year x` month s` day, X year x month s day is regarded as the label labeling time of the label to be queried, and X year x` month s` day is the labeling expiration time of the label to be queried. The current time of obtaining the data query instruction is X year x` month t day, then the marked time can be calculated through X year x month s day - X year x` month t day. When the marked time matches the preset survival time, the business service object is classified into the object labeling list corresponding to the preset survival time.

[0234] If the object label lists corresponding to each preset expiration time refer to object label lists corresponding to preset expiration times of 1 day, 1 week, or 1 month, or refer to object label lists corresponding to preset expiration countdowns of 1 day, 1 week, or 1 month, then the label expiration time is calculated based on X year x month t day - X year x month s day. If the label expiration time matches the preset expiration time, the business service object is assigned to the object label list corresponding to the preset expiration time. The target object label list refers to the object label list corresponding to the preset expiration time that matches the query label expiration time.

[0235] For example, if the query annotation survival time refers to the most recent month after the query tag is labeled, the preset object annotation list corresponding to the labeled one month will be used as the target object annotation list. If the query annotation survival time refers to the expiration of the query tag one month after it is labeled, the preset object annotation list corresponding to the expiration of one month will be used as the target object annotation list, and so on.

[0236] In some embodiments, in order to use the object query strategy to query the object annotation data corresponding to the business service end, according to the target query strategy, the target annotation query data is determined from the object annotation data of all business service objects, including:

[0237] If the target query strategy is an object query strategy, obtain the target business service object from the data query instruction;

[0238] According to the tag to be queried, target annotation query data is determined from the object annotation data of the target business service object.

[0239] For example, in order to quickly query the object annotation data of a specific business service object, the business service object in the data query instruction is used as the target business service object, and the data related to the label to be queried is determined from the object annotation data of the target business service object as the target annotation query data.

[0240] As can be seen from the above, the embodiment of the present application can obtain the current business data of the business service end, and the current business data includes the current target business tag information of the business service end, and the object information of at least one business service object; based on the target business tag information, the historical business tag information corresponding to the business service end is updated to obtain the updated business tag information corresponding to the business service end; for each business service object of the business service end, the reference object tag information that matches the object information of each business service object is determined from the updated business tag information; for each business service object, the business service object is data labeled according to the reference object tag information that matches the object information of the business service object, and the object labeling data of the business service object is obtained and output.

[0241] Therefore, after obtaining the current business data of the business service end, this solution can first use the current target business tag information of the business service end in the current business data to promptly update the historical business tag information corresponding to the business service end, which can ensure that the updated business tag information can meet the current business needs of the business service end. Subsequently, when performing data annotation on each business service object of the business service end in the current business data, the updated business tag information is used to match the object information of each business service object. By matching the obtained reference object tag information, it can be ensured that the business service object is correctly annotated. This data annotation process for each business service object is consistent and repeatable, does not require the participation of annotators, reduces the impact of subjective differences between annotators on the annotation results, ensures that the data annotation process can be more accurate and efficient, and improves the quality and efficiency of data annotation.

[0242] The method described in the above embodiment will be further described below.

[0243] In this embodiment, the method of the embodiment of the present application will be described in detail by taking the tag hosting platform managing the business data of at least one business service end as an example.

[0244] like Figure 2a As shown in Figure 2, the specific process of a data annotation method is as follows:

[0245] 201. Receive a service data transmission request sent by at least one service server.

[0246] In some embodiments, the target service tag information includes service tag information to be added, and before receiving a service data transmission request sent by at least one service server through the target service data transmission channel, the following steps are further included:

[0247] After the business server registers the business tag information to be added, a business data transmission request sent by at least one business server is received.

[0248] like Figure 2b As shown, the registration process for adding business tag information:

[0249] 203-1. The business server obtains tag configuration information of the tag to be added. The tag configuration information of the tag to be added includes at least one of the tag name, additional information, description information, tag person in charge information, tag classification, source, weight, associated tag information, tag survival time, preset survival time, and statistical granularity.

[0250] The tag lifetime refers to the lifetime of the tag after it is annotated.

[0251] The preset survival time is used to indicate that after the business service object is marked with the tag to be added and the tag survival time of the tag to be added reaches the preset survival time, the business service object is classified into the object marking list corresponding to the preset survival time.

[0252] The statistical granularity can be used to specify the time unit used for statistical analysis of the tags to be added.

[0253] 203-2. The business server verifies the tag classification and associated tags in the received tag configuration information and obtains a verification result.

[0254] 203-3. If the verification result shows that the tag configuration information of the tag to be added is successfully verified, the registration information is submitted based on the tag configuration information of the tag to be added.

[0255] 203 - 4. If the verification result shows that the tag configuration information of the tag to be added fails to be verified, the tag configuration information of the tag to be added is updated to obtain updated tag configuration information of the tag to be added, and the registration information is submitted based on the updated tag configuration information.

[0256] 203-5. After completing the registration of the tag to be added, the service tag information to be added is returned. The service tag information to be added includes the tag identifier of the tag to be added.

[0257] like Figure 2c As shown, in some embodiments, the business service end includes a label definition layer, a data processing and production layer, and a labeled data usage layer.

[0258] The tag definition layer includes a tag setting module and a tag configuration module. The tag setting module is used to add / delete / modify / query tags, and the tag configuration module is used to configure the addition / deletion / modification / query of tags.

[0259] Figure 2d As shown, the label setting module and label configuration module in the data definition layer include registration function, modification function, deletion function and query function. The registration function and modification function are used to manage label configuration information. The label configuration information includes descriptive information such as label name, label ID of parent label, whether to scroll, label marking time, and the deletion function cabinet can delete icon description data and associated labels. The query function can query label registration information, label statistical information, hierarchical relationship between labels, etc.

[0260] The data processing and production layer includes a logic definition module, a manual labeling module, a labeling data push module, and a labeling data modification module. The logic definition module is used to define the labeling logic corresponding to the business server, the manual labeling module is used to provide manual labeling on the business server, the labeling data push module is used to push the labeling data obtained from the labeling hosting platform, and the labeling data modification module is used to modify or delete the labeling data.

[0261] The annotation data usage layer includes a data query module and a data reference module. The data query module is used to provide annotation data from the query tag hosting platform, and the data reference module is used to provide reference tag data from the tag hosting platform.

[0262] like Figure 2e As shown, the reference methods of annotation data include jump, embedding and API call. Jump is used to reference annotation data in the form of a hyperlink, embedding is used to embed other pages in the form of embedded pages to reference annotation data, and API call is to call the API interface to return annotation data.

[0263] In some embodiments, the business data transmission channel of the business service end includes at least one of the business data transmission channels of the marking hosting platform.

[0264] 202. Based on the service data transmission request, determine a target service data transmission channel that matches each service server from at least one service data transmission channel.

[0265] 203. For each business server, obtain the current business data of the business server through the target business data transmission channel. The current business data includes the current target business tag information of the business server and the object information of at least one business service object.

[0266] like Figure 2c As shown, in some embodiments, the tag hosting platform includes a data docking layer, a data management layer, and a data storage layer.

[0267] The data connection layer is used to provide data connection capabilities to the business server, including at least one business data transmission channel, which includes but is not limited to SDK, API, Web page and other types of channels.

[0268] like Figure 2f As shown, through the SDK, API, web page, and other types of channels of the tag hosting platform, the business tag information of the business service end, the object information of the business service object, and other data are received to manage and store the data.

[0269] The data management layer is used to manage the business data sent by the business server. The data management layer includes the label data management module, the annotation data management module, the basic metadata module, and other data modules.

[0270] a1) The tag data management module is used to manage business tag information. The business tag information includes tag attributes and attribute content corresponding to the tag attributes. The tag data management module is used to provide the ability to add, delete, modify and query business tag information.

[0271] a2) The annotation data management module is used to manage annotation data and provide data association, addition, deletion, modification and query capabilities.

[0272] a3) The basic metadata module is used to manage the object information of the business service objects sent by the business server.

[0273] a4) Other data modules are used to manage statistical data, log data, audit data and other data of the tag hosting platform, and provide the ability to add, delete, modify and query.

[0274] like Figure 2c As shown, the data storage layer is used to store data of different data types. The data storage layer includes a basic metadata storage module, an annotation data module storage module, a business tag information storage module, and other data storage modules.

[0275] b1) The basic metadata storage module is used to store object information of business service objects sent by the business server.

[0276] b2) The tag data module storage module is used to store tag tag data, which is the data obtained by tagging the business service object according to the business tag information.

[0277] b3) The service tag information storage module is used to store the service tag information of the service server.

[0278] b4) Other data storage modules are used to store other data of the tag hosting platform, including but not limited to statistical data, log data, audit data and other data of the tag hosting platform.

[0279] like Figure 2g As shown in the figure, when managing data, the tag hosting platform interacts with the tag data management module, annotation data management module, basic metadata module, and other data modules through API channels. After receiving current business data through channels such as SDKs and web pages, the tag hosting platform needs to use API channels to manage data. The current business data received by the tag hosting platform through API channels can directly interact with the tag data management module, annotation data management module, basic metadata module, and other data modules.

[0280] Among them, the labeling hosting platform manages the label data management module through the API channel, adds current business label information, deletes and modifies historical business label information, queries current business label information and historical business label information, etc.

[0281] The labeling hosting platform manages the labeling data management module through the API channel, inserting, deleting, querying, and modifying labeling data.

[0282] The tag hosting platform manages the basic metadata module through the API channel, inserting, modifying, deleting, and object information of business service objects.

[0283] like Figure 2h As shown, in some embodiments, the tagging hosting platform includes a data association organization module, which can organize and summarize the data that needs to be output or input in the tag data management module, the annotation data management module, the basic metadata module, and other data modules.

[0284] For example, as shown in Table 1, the object information of the business service object can be stored in the data storage layer in the form of a table structure:

[0285] Field illustrate Example _id Business service objects For example, the account number is "123456" create_time Warehouse time "yyyy-mm-dd HH:MM:SS" update_time Update Time "yyyy-mm-dd HH:MM:SS" user_name Object name of the business service object "xxx.com" auth_name Business server name "ABC" … Any field can be expanded infinitely …

[0286] Table 1

[0287] The object information of the business service object can be stored in the data storage layer in the form of a document structure, as shown below:

[0288]

[0289] 204. Based on the target service tag information, update the historical service tag information corresponding to the service server to obtain updated service tag information corresponding to the service server.

[0290] For example, as shown in Table 2, the updated business tag information can be stored in the data storage layer in the form of a table structure:

[0291]

[0292]

[0293] Table 2

[0294] The data storage layer can be a relational database or a document database, and the tag dependency is specified based on the tag identifier of the parent tag.

[0295] The updated business tag information can be stored in the data storage layer in the form of a document structure, as shown below:

[0296]

[0297] 205. For each business service object of the business service end, determine reference object label information that matches the object information of each business service object from the updated business label information.

[0298] 206. For each business service object, perform data annotation processing on the business service object according to the reference object label information matched with the object information of the business service object, and obtain and output the object annotation data of the business service object.

[0299] In some embodiments, it further includes:

[0300] Get the data deletion instruction sent by the business server. The data deletion instruction is the deletion instruction related to the key tag.

[0301] If the data deletion instruction indicates to delete the key tag, the business tag information matching the key tag in the updated business tag information is deleted;

[0302] If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, then determining the target annotation data corresponding to the tag annotation data from the object annotation data corresponding to the business service object;

[0303] The target annotation data is deleted from the object annotation data corresponding to the target object.

[0304] like Figure 2i As shown, c1) the business service terminal inputs the tag identifier of the key tag, whether to delete the business tag information of the subtag of the key tag, whether to delete the tag annotation data of the subtag, whether to delete the tag annotation data of the associated tag of the key tag, and other deletion options to generate a data deletion instruction.

[0305] c2) Detect whether the subtags of the key tag need to be deleted. When the subtags of the key tag need to be deleted, query the service tag information storage module to obtain the subtag list of the key tag.

[0306] c3) traverse the subtag list of the key tag and delete the subtag of the key tag.

[0307] c4) Detect whether to delete the label marking data of the sub-label. If deletion is required, delete the label marking data of the sub-label.

[0308] c5) If the label data of the sub-label does not need to be deleted, the next sub-label is deleted.

[0309] c6) Repeat steps c4 and c5 until all subtags in the subtag list are traversed.

[0310] c7) Detect whether to delete the tag annotation data of the associated tag of the key tag. If yes, delete the tag annotation data of the associated tag of the key tag.

[0311] c8) If there is no need to delete the tag annotation data of the associated tags of the key tag, the process ends.

[0312] c9) Return to step c4 and check whether the label data of the sub-label is deleted. If not, go directly to step g.

[0313] like Figure 2j As shown, in some embodiments, the data deletion instruction includes the target annotation survival time corresponding to the key tag;

[0314] After receiving the data deletion instruction sent by the business server, it also includes:

[0315] Based on the target label survival time, obtain the object label survival list of the key tag corresponding to the business service end, the object label survival list includes the preset survival time and the surviving business service object corresponding to the preset survival time;

[0316] Based on the preset survival time, determine the target survival object that matches the target marked survival time from the object marked survival list;

[0317] If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, the tag annotation data associated with the key tag in the object annotation data corresponding to the target surviving object is deleted.

[0318] like Figure 2k As shown, in some embodiments, it also includes:

[0319] Get the data query instruction sent by the business server, which includes the tag to be queried;

[0320] Based on the data query instruction, determine the target query strategy from the tag query strategy and the object query strategy. The tag query strategy is used to query the business service objects marked with the tags to be queried. The object query strategy is used to query the tags to be queried of the business service objects indicated in the data query instruction.

[0321] Determine target annotation query data from the object annotation data of the business service object according to the target query strategy;

[0322] Send target annotation query data to the business server.

[0323] In some embodiments, according to the target query strategy, determining target annotation query data from the object annotation data of all business service objects includes:

[0324] If the target query strategy is a tag query strategy, the query annotation survival time corresponding to the tag to be queried is obtained from the data query instruction;

[0325] Based on the query annotation survival time, determine the target object annotation list from the object annotation lists corresponding to each preset survival time of the tag to be queried;

[0326] According to the tag to be queried, target annotation query data is determined from the object annotation data of each business service object in the target object annotation list.

[0327] In some embodiments, according to the target query strategy, determining target annotation query data from the object annotation data of all business service objects includes:

[0328] If the target query strategy is an object query strategy, obtain the target business service object from the data query instruction;

[0329] According to the tag to be queried, target annotation query data is determined from the object annotation data of the target business service object.

[0330] In some embodiments, based on the query annotation survival time, determining the target object annotation list from the object annotation lists corresponding to the preset survival times of the tags to be queried includes:

[0331] If there is a query tag survival time, determine the target object tag list from the object tag lists corresponding to the preset survival times of the tags to be queried;

[0332] If there is no query tag survival time, a target object tag list is obtained based on all business service objects corresponding to the tag to be queried.

[0333] In some embodiments, after determining target annotation query data from the object annotation data of the business service object according to the target query strategy, the method further includes:

[0334] According to the sub-tag list of the tag to be queried, detecting whether the target annotation query data contains the tag annotation data of the sub-tag of the tag to be queried;

[0335] If the tag annotation data of the subtag of the tag to be queried is not included, then continue to query the tag annotation data of the subtag of the tag to be queried, and update the target annotation query data;

[0336] If the tag annotation data contains the sub-tag of the tag to be queried, the target annotation query data is output.

[0337] In some embodiments, it further includes:

[0338] Detect whether the data query instruction indicates to carry object information of the target business service object;

[0339] If so, query the object information of the target business service object and merge the object information of the target business service object into the target annotation query data;

[0340] If not, directly output the target annotation query data.

[0341] like Figure 2l As shown, in some embodiments, when querying data, the data will eventually be organized into a unified structure for output, responsible for data integration and association, providing data association query capabilities externally, responsible for data routing internally, and storing data with different attributes in different storage modules, and also includes:

[0342] Integrate and associate the tag annotation data in the target annotation query data according to the target business service object, and output the data organization corresponding to the target annotation query data;

[0343] The label annotation data and object information in the target annotation query data are integrated and associated according to the target business service object, and the data association organization corresponding to the target annotation query data is output.

[0344] For example, as shown in Table 3, data organization can be presented in the form of a table structure:

[0345]

[0346]

[0347] Table 3

[0348] Data organization can be stored in the data storage layer in the form of a document structure, as shown below:

[0349]

[0350] like Figure 2m As shown, in some embodiments, for each business service object, data annotation processing is performed on the business service object according to reference object label information matched with object information of the business service object, and object annotation data of the business service object is obtained and output, including:

[0351] For each business service object, perform data labeling on the business service object based on the reference object label information matched with the object information of the business service object to obtain the current target object label of the business service object;

[0352] Get the historical object annotation data corresponding to the business service object;

[0353] Detect whether there is a target object history label corresponding to the target object label in the object history label of the historical object annotation data;

[0354] If the target object history tag is detected, the tag survival time corresponding to the target object tag is obtained;

[0355] Using the tag lifetime corresponding to the target object tag, update the tag lifetime corresponding to the target object's historical tag in the historical object annotation data to obtain and output the object annotation data of the business service object;

[0356] If no historical tag of the target object is detected, the target object tag and the tag lifetime of the target object tag are merged into the historical object tag data corresponding to the business service object, and the object tag data of the business service object is obtained and output.

[0357] For example, as shown in Table 4, the relevant information of the target object label in the object annotation data can be stored in the data storage layer in the form of a table structure:

[0358]

[0359] Table 4

[0360] The relevant information of the target object label in the object annotation data can be stored in the data storage layer in the form of a document structure, as shown below:

[0361]

[0362]

[0363] As can be seen from the above, this application proposes a unified and efficient solution for data labeling. It highly abstracts businesses with different scenarios, different data sources, and different goals into a capability-specific platform. The platform provides basic general capabilities, liberates business productivity, and enables businesses to focus more on the business itself.

[0364] Furthermore, this application lowers the barrier to entry for developing a tagging system, allowing developers to focus on the tagging logic required to achieve their business needs, significantly improving development efficiency. The universal tagging hosting platform provides unified tagging rules, label definitions, and tagging processes to ensure consistent and accurate tagging. This helps improve data quality and reliability and reduces repetitive work. Flexible configuration options and customizable features are provided to meet the needs of different fields and tasks.

[0365] Furthermore, the tagging hosting platform supports multiple annotation types (such as text, images, and audio), and provides features such as custom tags, annotation tools, and interfaces to meet specific task requirements. Resource sharing and collaboration: This platform enables resource sharing and collaboration, sharing data and annotation results, improving work efficiency and collaboration, and further optimizing the division of labor. It also provides unified data management and storage capabilities for the efficient organization and storage of annotation data. This includes data indexing, version control, data backup, and permissions management to ensure data security and traceability.

[0366] To better implement the above method, the present application also provides a data annotation device. The data annotation device can be integrated into an electronic device, such as a terminal or a server. The terminal can be a mobile phone, tablet computer, smart Bluetooth device, laptop computer, personal computer, etc. The server can be a single server or a server cluster consisting of multiple servers.

[0367] For example, in this embodiment, the method of the embodiment of the present application will be described in detail by taking the specific integration of the data labeling device into an electronic device as an example.

[0368] For example, Figure 3 As shown, the data tagging device may include a data acquisition unit 301, an information updating unit 302, an information matching unit 303, and a data tagging unit 304, as follows:

[0369] (1) Data acquisition unit 301.

[0370] The data acquisition unit 301 is configured to acquire current business data of the business server. The current business data includes current target business tag information of the business server and object information of at least one business service object.

[0371] In some embodiments, the data acquisition unit includes a request receiving subunit, a channel matching subunit, and a data acquisition subunit:

[0372] A request receiving subunit is used to receive a service data transmission request sent by a service server;

[0373] A channel matching subunit is used to determine a target service data transmission channel that matches the service server from at least one service data transmission channel based on the service data transmission request;

[0374] The data acquisition subunit is used to obtain the current business data of the business server through the target business data transmission channel.

[0375] (2) Information updating unit 302.

[0376] The information updating unit 302 is configured to update the historical service tag information corresponding to the service server based on the target service tag information to obtain updated service tag information corresponding to the service server.

[0377] In some embodiments, the information updating unit includes an information acquiring subunit, a difference determining subunit, and an information updating subunit:

[0378] The information acquisition subunit is used to obtain the historical business tag information corresponding to the business server;

[0379] A difference determination subunit, configured to determine difference service label information between historical service label information and target service label information;

[0380] The information updating subunit is used to update the historical service tag information according to the difference service tag information, and obtain the updated service tag information corresponding to the service server.

[0381] In some embodiments, the difference service tag information includes historical service tag information to be updated and service tag information to be added;

[0382] The information update subunit includes the attribute comparison module, the attribute update module and the information update module:

[0383] An attribute comparison module is used to compare the attribute contents of the historical service tag information to be updated and the target service tag information based on the tag attributes of the historical service tag information to be updated and the tag attributes of the target service tag information, thereby obtaining the attribute contents to be updated in the historical service tag information to be updated and the reference attribute contents corresponding to the attribute contents to be updated in the target service tag information;

[0384] An attribute update module is used to use the attribute content to be referenced to perform attribute update processing on the attribute content to be updated in the historical service tag information to be updated, and obtain the updated historical service tag information;

[0385] The information updating module is used to update the historical service tag information based on the updated historical service tag information and the service tag information to be added, and obtain the updated service tag information corresponding to the service server.

[0386] (3) Information matching unit 303.

[0387] The information matching unit 303 is configured to determine, for each business service object of the business service end, from the updated business label information, reference object label information that matches the object information of each business service object.

[0388] (4) Data labeling unit 304.

[0389] The data annotation unit 304 is used to perform data annotation processing on each business service object according to the reference object label information matched with the object information of the business service object, and obtain and output the object annotation data of the business service object.

[0390] In some embodiments, the data tagging unit includes a label tagging subunit, a label data acquisition subunit, a label detection subunit, and a label data update subunit:

[0391] The label marking subunit is used to perform data labeling processing on each business service object according to the reference object label information matched with the object information of the business service object, and obtain the current target object label of the business service object;

[0392] The annotation data acquisition subunit is used to obtain the historical object annotation data corresponding to the business service object;

[0393] A label detection subunit is used to detect whether there is a target object history label corresponding to the target object label in the object history label of the historical object annotation data;

[0394] The annotation data update subunit is used to obtain the tag survival time corresponding to the target object tag if the existence of the target object historical tag is detected; use the tag survival time corresponding to the target object tag to update the tag survival time corresponding to the target object historical tag in the historical object annotation data, and obtain and output the object annotation data of the business service object.

[0395] In some embodiments, the annotation data update subunit is also used to merge the target object tag and the tag survival time of the target object tag into the historical object annotation data corresponding to the business service object if no target object historical tag is detected, and obtain and output the object annotation data of the business service object.

[0396] In some embodiments, it further includes a deletion instruction acquisition unit and a first data deletion unit;

[0397] A deletion instruction acquisition unit is used to acquire a data deletion instruction sent by the business server, where the data deletion instruction is a deletion instruction related to a key tag;

[0398] The first data deletion unit is used to delete the business tag information that matches the key tag in the updated business tag information if the data deletion instruction indicates to delete the key tag; if the data deletion instruction indicates to delete the tag annotation data associated with the key tag, determine the target annotation data corresponding to the tag annotation data from the object annotation data corresponding to the business service object; and delete the target annotation data from the object annotation data corresponding to the target object.

[0399] In some embodiments, the data deletion instruction includes the target annotation survival time corresponding to the key tag;

[0400] It also includes a list acquisition unit, an object matching unit, and a second data deletion unit:

[0401] A list acquisition unit is used to acquire an object label survival list of a key tag corresponding to the business service end based on the target label survival time, wherein the object label survival list includes a preset survival time and a surviving business service object corresponding to the preset survival time;

[0402] An object matching unit, configured to determine, based on a preset survival time, a target surviving object that matches the target marked survival time from an object marked survival list;

[0403] The second data deletion unit is configured to delete the tag annotation data associated with the key tag in the object annotation data corresponding to the target surviving object if the data deletion instruction indicates to delete the tag annotation data associated with the key tag.

[0404] In some embodiments, it further includes a query instruction acquisition unit, a query strategy determination unit, a query data determination unit, and a query data sending unit;

[0405] A query instruction acquisition unit is used to acquire a data query instruction sent by the business server, where the data query instruction includes a tag to be queried;

[0406] A query strategy determination unit is configured to determine a target query strategy from a tag query strategy and an object query strategy based on a data query instruction, wherein the tag query strategy is used to query business service objects marked with tags to be queried, and the object query strategy is used to query tags to be queried for business service objects indicated in the data query instruction;

[0407] A query data determining unit, configured to determine target annotated query data from the object annotated data of the business service object according to a target query strategy;

[0408] The query data sending unit is used to send target annotation query data to the business server.

[0409] In some embodiments, the query data determining unit includes a time obtaining subunit, a label list determining subunit, and a first query data determining subunit:

[0410] The time acquisition subunit is used to obtain the query annotation survival time corresponding to the tag to be queried from the data query instruction if the target query strategy is the tag query strategy;

[0411] A label list determination subunit is used to determine a target object label list from object label lists corresponding to each preset survival time of the tag to be queried based on the query label survival time;

[0412] The first query data determining subunit is configured to determine target annotation query data from the object annotation data of each business service object in the target object annotation list according to the tag to be queried.

[0413] In some embodiments, the query data determination unit includes an object acquisition subunit and a second query data determination subunit:

[0414] The object acquisition subunit is used to acquire the target business service object from the data query instruction if the target query strategy is an object query strategy;

[0415] The second query data determining subunit is configured to determine target annotated query data from the object annotated data of the target business service object according to the tag to be queried.

[0416] In specific implementation, the above units can be implemented as independent entities, or can be arbitrarily combined to be implemented as the same or several entities. The specific implementation of the above units can be found in the previous method embodiments and will not be repeated here.

[0417] As can be seen from the above, the data labeling device of this embodiment obtains the current business data of the business service end by the data acquisition unit, and the current business data includes the current target business label information of the business service end and the object information of at least one business service object; the information update unit updates the historical business label information corresponding to the business service end based on the target business label information, and obtains the updated business label information corresponding to the business service end; the information matching unit determines the reference object label information that matches the object information of each business service object of the business service end from the updated business label information; the data labeling unit performs data labeling on each business service object according to the reference object label information that matches the object information of the business service object, and obtains and outputs the object labeling data of the business service object.

[0418] Therefore, the embodiments of the present application can improve the quality and efficiency of data annotation.

[0419] The present application also provides an electronic device, which may be a terminal, a server, or the like. The terminal may be a mobile phone, a tablet computer, a smart Bluetooth device, a laptop computer, a personal computer, or the like; the server may be a single server or a server cluster consisting of multiple servers, or the like.

[0420] In some embodiments, the data labeling device can also be integrated into multiple electronic devices. For example, the data labeling device can be integrated into multiple servers, and the data labeling method of the present application can be implemented by multiple servers.

[0421] In this embodiment, the electronic device of this embodiment is a server as an example for detailed description, for example, Figure 4 As shown, it shows a schematic diagram of the structure of the server involved in the embodiment of the present application, specifically:

[0422] The server may include one or more processing core processors 401, one or more computer-readable storage media memories 402, a power supply 403, an input module 404, and a communication module 405. Those skilled in the art will appreciate that Figure 4 The server structure shown in the figure does not constitute a limitation on the server, and may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently.

[0423] Processor 401 is the server's control center, connecting various components of the server using various interfaces and circuits. It executes software programs and / or modules stored in memory 402 and accesses data stored in memory 402 to perform various server functions and process data. In some embodiments, processor 401 may include one or more processing cores. In some embodiments, processor 401 may integrate an application processor and a modem processor. The application processor primarily handles the operating system, user interface, and application programs, while the modem processor primarily handles wireless communications. It is understood that the modem processor may not be integrated into processor 401.

[0424] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area may store data created according to the use of the server, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0425] The server also includes a power supply 403 that supplies power to various components. In some embodiments, the power supply 403 can be logically connected to the processor 401 via a power management system, thereby enabling the power management system to manage charging, discharging, and power consumption. The power supply 403 can also include one or more DC or AC power supplies, a recharging system, a power failure detection circuit, a power converter or inverter, a power status indicator, and other arbitrary components.

[0426] The server may further include an input module 404, which may be configured to receive input digital or character information and generate keyboard, mouse, joystick, optical or trackball signal input related to user settings and function control.

[0427] The server may also include a communication module 405. In some embodiments, the communication module 405 may include a wireless module. The server may use the wireless module of the communication module 405 to perform short-range wireless transmission, thereby providing users with wireless broadband Internet access. For example, the communication module 405 may be used to help users send and receive emails, browse web pages, and access streaming media.

[0428] Although not shown, the server may further include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the server loads the executable files corresponding to one or more application processes into the memory 402 according to the following instructions, and the processor 401 runs the application stored in the memory 402, thereby implementing the steps of the method in each embodiment of the present application.

[0429] The specific implementation of the above operations can be found in the previous embodiments and will not be repeated here.

[0430] From the above, we can see that this data labeling process for various business service objects is consistent and repeatable, does not require the participation of labelers, reduces the impact of subjective differences between labelers on the labeling results, ensures that the data labeling process can be more accurate and efficient, and improves the quality and efficiency of data labeling.

[0431] Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments may be accomplished by instructions, or by controlling related hardware through instructions. The instructions may be stored in a computer-readable storage medium and loaded and executed by a processor.

[0432] To this end, an embodiment of the present application provides a computer-readable storage medium storing a plurality of instructions that can be loaded by a processor to execute the steps of any of the data annotation methods provided in the embodiments of the present application. For example, the instructions can execute the following steps:

[0433] Acquire current business data of the business server, where the current business data includes current target business tag information of the business server and object information of at least one business service object;

[0434] Based on the target business tag information, the historical business tag information corresponding to the business server is updated to obtain the updated business tag information corresponding to the business server;

[0435] For each business service object on the business service side, determine reference object label information that matches the object information of each business service object from the updated business label information;

[0436] For each business service object, data annotation processing is performed on the business service object according to the reference object label information matched with the object information of the business service object, and the object annotation data of the business service object is obtained and output.

[0437] The storage medium may include a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, etc.

[0438] According to one aspect of the present application, a computer program product or computer program is provided, the computer program product or computer program including a computer program / instructions stored in a computer-readable storage medium. A processor of an electronic device reads the computer program / instructions from the computer-readable storage medium and executes the computer program / instructions, causing the electronic device to perform the methods provided in the various optional implementations of the data labeling aspects provided in the above embodiments.

[0439] Since the instructions stored in the storage medium can execute the steps in any data labeling method provided in the embodiments of the present application, the beneficial effects that can be achieved by any data labeling method provided in the embodiments of the present application can be achieved. Please refer to the previous embodiments for details and will not be repeated here.

[0440] The above is a detailed introduction to a data labeling method, device, electronic device, storage medium and program product provided in the embodiments of the present application. Specific examples are used herein to illustrate the principles and implementation methods of the present application. The description of the above embodiments is only used to help understand the method of the present application and its core idea; at the same time, for technical personnel in this field, based on the ideas of the present application, there will be changes in the specific implementation methods and application scope. In summary, the content of this specification should not be understood as a limitation on the present application.

Claims

1. A data annotation method, characterized in that: include: Acquire current business data of the business server, where the current business data includes current target business tag information of the business server and object information of at least one business service object; Based on the target service tag information, updating the historical service tag information corresponding to the service server to obtain updated service tag information corresponding to the service server; For each business service object of the business service end, determining reference object label information that matches the object information of each business service object from the updated business label information; For each business service object, data annotation processing is performed on the business service object according to reference object label information matched with object information of the business service object, and object annotation data of the business service object is obtained and output.

2. The data annotation method according to claim 1, wherein: The obtaining of the current business data of the business server includes: Receive business data transmission requests sent by the business server; Based on the service data transmission request, determining a target service data transmission channel that matches the service server from at least one service data transmission channel; The current business data of the business server is obtained through the target business data transmission channel.

3. The data annotation method according to claim 1, wherein: The updating process of the historical service tag information corresponding to the service server based on the target service tag information to obtain the updated service tag information corresponding to the service server includes: Get the historical business tag information corresponding to the business server; Determine difference service tag information between the historical service tag information and the target service tag information; The historical service label information is updated according to the difference service label information to obtain updated service label information corresponding to the service server.

4. The data annotation method according to claim 3, wherein: The difference service label information includes historical service label information to be updated and service label information to be added; The updating process of the historical service tag information according to the difference service tag information to obtain updated service tag information corresponding to the service server includes: Based on the tag attributes of the historical service tag information to be updated and the tag attributes of the target service tag information, performing attribute content comparison processing on the historical service tag information to be updated and the target service tag information to obtain attribute content to be updated in the historical service tag information to be updated and attribute content to be referenced corresponding to the attribute content to be updated in the target service tag information; Using the attribute content to be referenced, performing attribute update processing on the attribute content to be updated in the historical service tag information to be updated, to obtain updated historical service tag information; Based on the updated historical service tag information and the service tag information to be added, the historical service tag information is updated to obtain updated service tag information corresponding to the service server.

5. The data annotation method according to claim 1, wherein: The method of performing data annotation processing on each business service object according to reference object label information matched with object information of the business service object, and obtaining and outputting object annotation data of the business service object, includes: For each business service object, data labeling processing is performed on the business service object according to the reference object label information matched with the object information of the business service object to obtain the current target object label of the business service object; Obtaining historical object annotation data corresponding to the business service object; Detecting whether there is a target object history tag corresponding to the target object tag in the object history tags of the historical object annotation data; If the target object history tag is detected, the tag lifetime corresponding to the target object tag is obtained; The tag survival time corresponding to the target object tag is used to update the tag survival time corresponding to the target object history tag in the historical object annotation data, and the object annotation data of the business service object is obtained and output.

6. The data annotation method according to claim 5, wherein: Also includes: If the target object history tag is not detected, the target object tag and the tag lifetime of the target object tag are merged into the historical object annotation data corresponding to the business service object, and the object annotation data of the business service object is obtained and output.

7. The data annotation method according to claim 1, wherein: Also includes: Obtaining a data deletion instruction sent by the business server, wherein the data deletion instruction is a deletion instruction related to a key tag; If the data deletion instruction indicates to delete the key tag, deleting the service tag information matching the key tag in the updated service tag information; If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, then determining the target annotation data corresponding to the tag annotation data from the object annotation data corresponding to the business service object; The target annotation data is deleted from the object annotation data corresponding to the target object.

8. The data annotation method according to claim 7, wherein: The data deletion instruction includes the target label survival time corresponding to the key tag; After obtaining the data deletion instruction sent by the business server, the method further includes: Based on the target label survival time, obtaining the object label survival list of the key tag corresponding to the business service end, the object label survival list including the preset survival time and the surviving business service object corresponding to the preset survival time; Based on the preset survival time, determining a target survival object that matches the target marked survival time from the object marked survival list; If the data deletion instruction indicates to delete the tag annotation data associated with the key tag, the tag annotation data associated with the key tag in the object annotation data corresponding to the target surviving object is deleted.

9. The data annotation method according to claim 1, wherein: Also includes: Obtaining a data query instruction sent by the business server, wherein the data query instruction includes a tag to be queried; Based on the data query instruction, determining a target query strategy from a tag query strategy and an object query strategy, wherein the tag query strategy is used to query the business service object marked with the tag to be queried, and the object query strategy is used to query the tag to be queried of the business service object indicated in the data query instruction; Determining target annotation query data from the object annotation data of the business service object according to the target query strategy; Send the target annotation query data to the business service end.

10. The data labeling method according to claim 9, wherein: Determining target annotation query data from the object annotation data of all the business service objects according to the target query strategy includes: If the target query strategy is the tag query strategy, obtaining the query annotation survival time corresponding to the tag to be queried from the data query instruction; Based on the query annotation survival time, determining a target object annotation list from the object annotation lists corresponding to the preset survival times of the tags to be queried; According to the tag to be queried, target annotation query data is determined from the object annotation data of each business service object in the target object annotation list.

11. The data annotation method according to claim 9, wherein: Determining target annotation query data from the object annotation data of all the business service objects according to the target query strategy includes: If the target query strategy is the object query strategy, obtaining the target business service object from the data query instruction; According to the tag to be queried, target annotation query data is determined from the object annotation data of the target business service object.

12. A data labeling device, characterized in that: include: A data acquisition unit, configured to acquire current business data of the business server, wherein the current business data includes current target business tag information of the business server and object information of at least one business service object; An information updating unit, configured to update the historical service tag information corresponding to the service server based on the target service tag information, to obtain updated service tag information corresponding to the service server; An information matching unit, configured to determine, for each business service object of the business service end, from the updated business tag information, reference object tag information that matches the object information of each business service object; The data labeling unit is used to perform data labeling processing on each business service object according to the reference object label information matched with the object information of the business service object, and obtain and output the object labeling data of the business service object.

13. A server electronic device, characterized in that: The method comprises a processor and a memory, wherein the memory stores a plurality of instructions; the processor loads instructions from the memory to execute the steps in the data labeling method according to any one of claims 1 to 11.

14. A computer-readable storage medium, characterized in that The computer-readable storage medium stores a plurality of instructions, which are suitable for loading by a processor to execute the steps in the data labeling method according to any one of claims 1 to 11.

15. A computer program product comprising a plurality of instructions, characterized in that: When the instructions are executed by the processor, the steps in the data labeling method according to any one of claims 1 to 11 are implemented.

Images