Data label processing method and device, equipment, medium and product

Abstract

The embodiment of the invention relates to a data label processing method and device, equipment, a medium and a program product. The data label processing method comprises the steps of obtaining a mapping relation of a data label under a target dimension, wherein the mapping relation indicates a corresponding relation between a plurality of universal labels of data and a plurality of user-defined labels of the target dimension; receiving a data processing strategy, wherein the data processing strategy at least indicates a target universal label in the plurality of universal labels and a target operation corresponding to the target universal label; based on the mapping relationship, determining a target custom tag corresponding to the target universal tag from the plurality of custom tags; and executing the target operation on the target data with the target custom tag. Therefore, the data labels can be conveniently and uniformly managed, and the existing label system of each dimension does not need to be modified.

Description

Technical Field

[0001] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to processing methods, devices, apparatuses, media, and products for data tags. Background Art

[0002] Data classification and grading is a data management strategy. By classifying and grading data, we can better protect data and manage its use and sharing. The labeling system is a system that can mark and classify data. By adding labels to data, we can easily identify, retrieve, analyze and manage data. Summary of the invention

[0003] In a first aspect of the present disclosure, a method for processing data tags is provided. The method includes: obtaining a mapping relationship of data tags under a target dimension, the mapping relationship indicating a corresponding relationship between multiple common tags of data and multiple custom tags of the target dimension; receiving a data processing strategy, the data processing strategy indicating at least a target common tag among multiple common tags and a target operation corresponding to the target common tag; determining a target custom tag corresponding to the target common tag from multiple custom tags based on the mapping relationship; and performing a target operation on target data having the target custom tag.

[0004] In a second aspect of the present disclosure, a method for processing data tags is provided. The method includes: generating a mapping relationship set for data tags based on tag configuration information, the mapping relationship set including multiple mapping relationships for multiple dimensions, each mapping relationship indicating a corresponding relationship between multiple common tags and multiple custom tags of the corresponding dimension; and providing a mapping relationship for a target dimension to a data user associated with a target dimension among the multiple dimensions.

[0005] In a third aspect of the present disclosure, a device for data tag processing is provided. The device includes: an acquisition module configured to acquire a mapping relationship between data tags under a target dimension, wherein the mapping relationship indicates a corresponding relationship between multiple common tags of data and multiple custom tags of the target dimension; a receiving module configured to receive a data processing strategy, wherein the data processing strategy at least indicates a target common tag among multiple common tags and a target operation corresponding to the target common tag; a determination module configured to determine a target custom tag corresponding to the target common tag from multiple custom tags based on the mapping relationship; and an execution module configured to execute a target operation on target data having a target custom tag.

[0006] In a fourth aspect of the present disclosure, a device for data tag processing is provided. The device includes: a generating module configured to generate a mapping relationship set for data tags based on tag configuration information, the mapping relationship set including multiple mapping relationships for multiple dimensions, each mapping relationship indicating a corresponding relationship between multiple common tags and multiple custom tags of the corresponding dimension; and a providing module configured to provide a mapping relationship for a target dimension to a data user associated with a target dimension among the multiple dimensions.

[0007] In a fifth aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory, the at least one memory is coupled to the at least one processing unit and stores instructions for execution by the at least one processing unit. When the instructions are executed by the at least one processing unit, the device executes the method of the first aspect or the second aspect.

[0008] In a sixth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect or the second aspect.

[0009] In a seventh aspect of the present disclosure, a computer program product is provided, comprising a computer program, wherein the computer program implements the method according to the first aspect or the second aspect of the present disclosure when executed by a processor.

[0010] It should be understood that the contents described in this content section are not intended to limit the key features or important features of the embodiments of the present disclosure, nor are they intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:

[0012] Figure 1 A schematic diagram showing an example environment in which embodiments according to the present disclosure may be implemented;

[0013] Figure 2 A flowchart illustrating an example process for data tag usage according to some embodiments of the present disclosure;

[0014] Figure 3 A schematic diagram showing an example architecture for data tag usage and management according to some embodiments of the present disclosure;

[0015] Figure 4A schematic diagram showing an example mapping table for a target dimension according to some embodiments of the present disclosure is shown;

[0016] Figure 5 A flowchart illustrating an example process of data tag management according to some embodiments of the present disclosure;

[0017] Fig. 6A A schematic diagram showing an example table of multiple custom labels for multiple dimensions according to some embodiments of the present disclosure;

[0018] Figure 6B A schematic diagram showing an example overall mapping table according to some embodiments of the present disclosure is shown;

[0019] Figure 7 A schematic structural block diagram of an example device for use of data tags according to some embodiments of the present disclosure is shown;

[0020] Figure 8 A schematic structural block diagram showing an example apparatus for data tag management according to some embodiments of the present disclosure; and

[0021] Fig. 9 A block diagram of an electronic device capable of implementing various embodiments of the present disclosure is shown. DETAILED DESCRIPTION

[0022] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as being limited to the embodiments set forth herein. On the contrary, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not intended to limit the scope of protection of the present disclosure.

[0023] It should be noted that the titles of any sections / subsections provided herein are not restrictive. Various embodiments are described throughout this article, and any type of embodiment may be included under any section / subsection. In addition, the embodiments described in any section / subsection may be combined in any manner with any other embodiments described in the same section / subsection and / or different sections / subsections.

[0024] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, that is, "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below. The terms "first", "second", etc. may refer to different or the same objects. Other explicit and implicit definitions may be included below.

[0025] The embodiments of the present disclosure may involve user data, data acquisition and / or use, etc. These aspects are subject to the corresponding laws, regulations and relevant provisions. In the embodiments of the present disclosure, all data collection, acquisition, processing, processing, forwarding, use, etc. are carried out on the premise that the user knows and confirms. Accordingly, when implementing each embodiment of the present disclosure, the type, scope of use, usage scenario, etc. of the data or information that may be involved should be informed to the user and the user's authorization should be obtained in an appropriate manner in accordance with the relevant laws and regulations. The specific notification and / or authorization method can vary according to the actual situation and application scenario, and the scope of the present disclosure is not limited in this respect.

[0026] In this specification and the embodiments, if personal information processing is involved, it will be processed on the premise of having a legal basis (such as obtaining the consent of the subject of personal information, or it is necessary to perform a contract, etc.), and will only be processed within the scope of regulations or agreements. If a user refuses to process personal information other than the necessary information for basic functions, it will not affect the user's use of basic functions.

[0027] As briefly mentioned above, data classification and grading is a data management strategy that categorizes and grades data to better protect data and manage its use and sharing. This can also facilitate data compliance. Data compliance refers to the compliance of organizations or enterprises with relevant laws, regulations, industry norms, regulatory requirements, and contractual agreements during the entire life cycle of data collection, storage, use, transmission, sharing, and deletion. Data protection refers to the use of a series of technical, management, and legal means to prevent data from unauthorized access, use, disclosure, tampering, or destruction, and to ensure the security, integrity, and availability of data.

[0028] The labeling system is a system for marking and classifying data. By adding labels to data, data can be easily identified, retrieved, analyzed and managed. The standards for data classification and grading are not yet unified. Different regions and industries have their own classification and grading standards.

[0029] Take the e-commerce industry as an example. Although a unified set of data classification and grading has been formulated to cover standards in multiple regions, the label system for data classification and grading is fragmented and untimely. Sometimes, the middle office staff is required to collect the data, which cannot be effectively closed.

[0030] Take the gaming industry as an example. Based on the development of the business, an international data classification and grading standard has been formulated. However, the classification and grading standards are updated lagging behind, and there is no unified standard. In addition, the labeling system is also governed by each business, and there is no unified system.

[0031] The embodiment of the present disclosure proposes a data tag usage scheme. According to the scheme, a mapping relationship of data tags under a target dimension is obtained, and the mapping relationship indicates the correspondence between multiple common tags of data and multiple custom tags of the target dimension. A data processing strategy is received, and the data processing strategy at least indicates a target common tag among multiple common tags and a target operation corresponding to the target common tag. Based on the mapping relationship, a target custom tag corresponding to the target common tag is determined from multiple custom tags. The target operation is performed on the target data with the target custom tag.

[0032] The embodiments of the present disclosure also propose a data tag management solution. According to the solution, based on the tag configuration information, a mapping relationship set for data tags is generated, and the mapping relationship set includes multiple mapping relationships for multiple dimensions, each mapping relationship indicating the correspondence between multiple common tags and multiple custom tags of the corresponding dimension. The mapping relationship for the target dimension is provided to the data user associated with the target dimension among the multiple dimensions.

[0033] In this way, the embodiments of the use of data tags disclosed in the present invention can standardize the labeling of data and facilitate the unified management of multi-dimensional tags. For a certain dimension, it is convenient to access the tag management party, which is conducive to the rapid deployment and cross-system use of data. By using custom tags, users of the corresponding dimension can be more easily understood and more targeted.

[0034] The disclosed data tag management embodiment can facilitate the reuse of data tags of different dimensions. It can solve the problem that the current custom tag capability is too weak and difficult to reasonably iterate. The unified tag can continuously be compatible with the diversity of businesses, and enrich the unified tag system from the dimensions of industry or business, which can meet the use of various businesses and industries. It can bring efficient update and iterative development, and bring efficient and minimalist access methods.

[0035] Various example implementations of the solution are described in detail below in conjunction with the accompanying drawings.

[0036] Example Environment

[0037] Figure 1 1 is a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. Figure 1 As shown, the example environment 100 includes a tag manager 110 and a data consumer 120. The tag manager 110 is configured to manage data tags. The data consumer 120 is configured to use data tagged with corresponding tags based on the data tags.

[0038] The tag manager 110 may communicate with the data user 120. The tag manager 110 may be configured to provide services for corresponding data tags based on the data usage requirements of the data user 120.

[0039] In some embodiments, the tag manager 110 and the data user 120 can be any type of mobile terminal, fixed terminal or portable terminal, including mobile phones, desktop computers, laptop computers, notebook computers, netbook computers, tablet computers, media computers, multimedia tablets, personal communication systems (PCS) devices, personal navigation devices, personal digital assistants (PDAs), audio / video players, digital cameras / camcorders, positioning devices, television receivers, radio broadcast receivers, e-book devices, gaming devices, or any combination of the foregoing, including accessories and peripherals of these devices or any combination thereof. In some embodiments, electronic devices can also support any type of interface for users (such as "wearable" circuits, etc.). The server can be various types of computing systems / servers that can provide computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like.

[0040] It should be understood that the structure and function of the various elements in the environment 100 are described for exemplary purposes only and do not imply any limitation on the scope of the present disclosure.

[0041] Some example embodiments of the present disclosure will be described below with continued reference to the accompanying drawings.

[0042] Example Process

[0043] An example process according to an embodiment of the present disclosure will be described below with reference to the accompanying drawings.

[0044] Figure 2 A flowchart of an example process 200 for data tag usage according to some embodiments of the present disclosure is shown. For ease of discussion, reference will be made to Figure 1 These embodiments are described with reference to the environment 100 of FIG. 1 . These embodiments regarding the use of data tags can be implemented in Figure 1 The data is used by 120 parties.

[0045] In box 210, the data user 120 obtains the mapping relationship between the data labels under the target dimension, and the mapping relationship indicates the correspondence between multiple common labels of the data and multiple custom labels of the target dimension. The data labels discussed in this article can be labels for marking or annotating data, which can be used to identify and describe the data type of the data. The data type can, for example, indicate a specific attribute, category, or purpose of the data. As an example, the labeled data can be data of the smallest granularity. It should be understood that in other examples, the labeled data can also be data of other granularities. When faced with a large amount of complex data of different dimensions, data labels can help users quickly understand the meaning of the data. Such dimensions can include, for example, industry dimensions, business dimensions, and the like.

[0046] Figure 3 A schematic diagram of an example architecture 300 for data tag usage and management according to some embodiments of the present disclosure is shown. The architecture 300 can be implemented in Figure 1 The architecture 300 may be shown as an architecture adopted by the steps of the process 200.

[0047] In the architecture 300, as an example, the data user 120 can obtain the mapping relationship 330 of the data tags under the target dimension from the tag manager 110. The target dimension may belong to a business dimension, an industry dimension, etc., for example, and is not limited here. Exemplarily, a common tag may be a tag with a common meaning in some businesses, industries, or fields. A custom tag may be a tag created by each business, industry, or field according to its own specific needs, business logic, or data characteristics. The mapping relationship 330 may indicate the correspondence between multiple common tags 310' of the data and multiple custom tags 320 of the target dimension. Based on different target dimensions, the corresponding multiple custom tags 320 may be, for example, multiple business dimension tags 322, multiple industry dimension tags 324, or other dimension tags 326.

[0048] In some embodiments, the mapping relationship 330 may be one of a plurality of mapping relationships included in the mapping relationship set, and the plurality of mapping relationships are respectively used for a plurality of dimensions, and the plurality of dimensions include a target dimension. As an example, the mapping relationship set may be stored in the tag manager 110. The tag manager 110 is at least configured to manage data tags. The mapping relationship set may include a unified universal tag 310 for a plurality of dimensions. Accordingly, the unified universal tag 310 may include a plurality of universal tags 310' for the target dimension. It should be noted that the unified universal tag 310 may be updated. For example, a new universal tag 312 may be added, or an old universal tag may be deleted.

[0049] In some embodiments, the mapping relationship can be represented by a mapping table. The mapping table at least includes mappings between universal identifiers of multiple universal tags and custom identifiers of multiple custom tags. Such identifiers can be, for example, IDs, or any other suitable characters, numbers, symbols, etc.

[0050] Figure 4 A schematic diagram of an example mapping table 400 for a target dimension according to some embodiments of the present disclosure is shown. Assuming that the target dimension is dimension A, its corresponding mapping table 400 may include multiple universal identifiers of multiple universal tags, such as universal tag_101, universal tag_102, etc. The mapping table 400 may also include multiple custom identifiers of multiple custom tags of dimension A, such as tag_101, tag_102, etc. Further, the mapping table 400 may include mappings between the multiple universal identifiers and the multiple custom identifiers.

[0051] In some embodiments, in the mapping relationship, one of the plurality of universal tags is mapped to zero or one of the plurality of custom tags of the target dimension. One custom tag of the target dimension is mapped to one of the plurality of universal tags. That is, one of the plurality of universal tags can be mapped to at most one custom tag of the target dimension. And each custom tag of the target dimension can be mapped to only one universal tag of the plurality of universal tags. For example, in the mapping table 400, the universal tag _101 can be mapped to only the custom tag _101 of dimension A, and will not be mapped to other custom tags of dimension A.

[0052] In some embodiments, multiple universal tags are applied to multiple dimensions including a target dimension, and each custom tag in each dimension of the multiple dimensions has a corresponding universal tag in the multiple universal tags. In other words, the multiple universal tags are not only for the target dimension, but multiple dimensions can use the multiple universal tags. In addition, for each dimension of the multiple dimensions, each custom tag can also be mapped to only one universal tag in the multiple universal tags.

[0053] Therefore, for each custom label in each of the multiple dimensions, there is a corresponding universal label, which enables the label manager to conveniently and uniformly manage labels in multiple dimensions.

[0054] Return to reference Figure 2In box 220, the data user 120 receives a data processing policy, which at least indicates a target general tag among multiple general tags and a target operation corresponding to the target general tag. In some embodiments, the data user 120 may receive the data processing policy from the tag manager 110. In other embodiments, the data user 120 may also receive the data processing policy from other platforms or other parties. As an example, the data processing policy may include relevant security policies, verification policies, visualization policies, etc., which are not limited here. It should be understood that the data processing policy may be any appropriate policy for performing corresponding processing on the data.

[0055] In order to facilitate the unified management of data of each dimension, the data processing strategy can at least indicate a target general label among multiple general labels for the target dimension and a target operation corresponding to the target general label. The target operation can be any appropriate operation or action for the specific processing of the data. The target operation can include, for example, intercepting the data, masking the data, vectorizing the data, etc. As an example, the data to be processed corresponding to the target operation can be the data corresponding to the target general label in the data user 120.

[0056] Furthermore, in block 230, based on the mapping relationship, the data user 120 determines a target custom tag corresponding to the target universal tag from the plurality of custom tags. Furthermore, in block 240, the data user 120 performs a target operation on the target data having the target custom tag.

[0057] For example, assuming that the data processing policy is an interception policy for user privacy data, the interception policy can indicate a common label for data types such as user privacy data among multiple common labels and a corresponding interception operation. The data user can determine the custom label corresponding to the common label from multiple custom labels based on the mapping relationship, and then perform an interception operation on the data marked with the custom label such as user privacy.

[0058] In some embodiments, the data processing policy may also indicate a target universal identifier of the target universal tag. To determine a target custom tag corresponding to the target universal tag, based on the mapping table, the data consumer 120 may determine a target custom identifier corresponding to the target universal identifier. Based on the target custom identifier, the data consumer 120 may determine the target custom tag.

[0059] For example, in Figure 4In the example, assuming that the interception policy indicates a universal identifier of a universal tag for user privacy data, such as universal tag_101, the data user 120 can determine a custom identifier corresponding to universal tag_101, such as custom tag_101, based on the mapping table 400. Then, the target custom tag is determined according to custom tag_101, so as to perform an interception operation on the data marked with the target custom tag.

[0060] In some embodiments, in order to obtain the mapping relationship, the data user 120 may receive a notification message about updating the first universal tag from the tag manager, and the notification message may indicate that the first universal tag and the first custom tag corresponding to the first universal tag are updated. Then, based on the notification message, the data user 120 may determine the updated mapping relationship.

[0061] In such an embodiment, the update of the first universal tag may include adding the first universal tag and deleting the first universal tag. In other embodiments, the update of the first universal tag may also include modifying the first universal tag. As an example, in both the updated mapping relationship and the unupdated mapping relationship, all custom tags of the target dimension need to have corresponding universal tags.

[0062] In some embodiments, in order to obtain the mapping relationship, if the second custom label of the target dimension is updated, the data user 120 may send a request to the label manager to update the second custom label. The data user 120 may receive a response to the request from the label manager, and the response may at least indicate the second common label corresponding to the second custom label. Then, the data user 120 may determine the updated mapping relationship based on the response.

[0063] In such an embodiment, the update of the second custom label may include adding the second custom label and deleting the second custom label. In other embodiments, the update of the second custom label may also include modifying the second custom label. If the second custom label is updated, it needs to be approved by the label management party 110, and then the mapping relationship is updated. As an example, in both the updated mapping relationship and the unupdated mapping relationship, all custom labels of each dimension need to have corresponding universal labels.

[0064] Therefore, custom tags under each dimension can find corresponding universal tags. This makes it easier for tag managers to update and uniformly manage data tags. For data users of each dimension, there is no need to modify their existing tag systems.

[0065] In some embodiments, the mapping relationship may be obtained by encapsulating a data packet. The encapsulated data packet may refer to a software development kit (sdk). Return to reference Figure 3 , architecture 300 shows that a unified labeling capability is provided through the SDK. Specifically, the unified general label 310 and the mapping table can be stored in a local file and packaged together with the SDK. After the SDK's label is initialized 340, these labels and mapping tables are stored in the local cache for query use, and some update capabilities are opened to update specific attributes of the label (345). For business-defined labels, the general label ID can be obtained through the mapping table, and the business label can be customized for storage, and its own business attributes can be managed, including adding, modifying, and deleting label attributes (350), updating the label directory, etc. (355). If it is a newly added label, a general label label can be formed and imported into the unified general label to form a positive cycle and enrich the entire label system. The SDK can be used in scenarios where general labels are immutable and business labels are customizable.

[0066] Alternatively or additionally, in some embodiments, the mapping relationship can be obtained through a microservice integrated with a label service. Exemplarily, a unified labeling capability can be provided through a microservice approach. As an example, general labels and custom labels for businesses, industries, etc. can be stored in a storage medium, supporting limited updates of general labels and supporting the management of business custom labels. Business custom labels can be refined and abstracted into general labels based on the business or industry, quickly forming a unified labeling system that can be reused in various businesses and industries. The form of microservices can maintain the latest use of general, business or industry custom labels, and is suitable for scenarios where real-time labels are queried.

[0067] Alternatively or additionally, in some embodiments, the mapping relationship can be obtained through a label service deployed in the form of function-as-a-service (Faas). Exemplarily, a unified label capability can be provided in a Faas manner. For the Faas method, the label service can be deployed independently, which is easy to deploy and scalable, and can be well integrated into the infrastructure services of various cloud vendors, and can also be integrated into various data security links. The user can use any language to quickly call the label function.

[0068] Through the various embodiments of the use of data tags disclosed in the present invention, it is possible to standardize the labeling of data and facilitate the unified management of multi-dimensional tags. For a certain dimension, it is convenient to access the tag management party, which is conducive to the rapid deployment and cross-system use of data. By using custom tags, users of the corresponding dimension can be more easily understood and more targeted.

[0069] Figure 5 FIG. 5 is a flowchart showing an example process 500 for data tag management according to some embodiments of the present disclosure. For ease of discussion, reference will be made to Figure 1These embodiments are described with reference to the environment 100 of FIG. 1 . These embodiments regarding data tag management can be implemented in Figure 1 The tag management party 110.

[0070] In block 510, based on the tag configuration information, the tag manager 110 generates a mapping relationship set for the data tag. The mapping relationship set includes a plurality of mapping relationships for a plurality of dimensions, each mapping relationship indicating a correspondence between a plurality of common tags and a plurality of custom tags of a corresponding dimension. In some embodiments, the tag configuration information may indicate the creation of the data tag.

[0071] Combination Figure 3 The mapping relationship set may include a unified universal tag 310 for multiple dimensions. Each mapping relationship in the mapping relationship set may indicate a corresponding relationship between multiple universal tags in the unified universal tag 310 and multiple custom tags of corresponding dimensions.

[0072] Return to reference Figure 5 In block 520, the tag manager 110 provides a mapping relationship for the target dimension to the data user 120 associated with the target dimension among the multiple dimensions. Figure 3 The tag manager 110 provides a mapping relationship 330 to the data user 120 associated with the target dimension. The mapping relationship 330 may indicate a correspondence between a plurality of common tags 310 ′ and a plurality of custom tags 320 of the target dimension.

[0073] In some embodiments, based on the policy information, the tag manager 110 can determine a data processing policy, which can indicate a target universal tag among multiple universal tags and a target operation corresponding to the target universal tag. Based on the mapping relationship set, the tag manager 110 can determine one or more target custom tags corresponding to the target universal tag and one or more dimensions to which the one or more target custom tags belong respectively. Then, the tag manager 110 can send the data processing policy to one or more data users respectively associated with the one or more dimensions.

[0074] In such an embodiment, the policy information may include relevant information published for a certain aspect or certain aspects of data. For example, relevant information about security policies on personal privacy published by an organization. The tag manager 110 can determine the corresponding data processing strategy after receiving such policy information. For example, a strategy for intercepting user privacy data can be determined. Then, the tag manager 110 can determine one or more dimensions corresponding to the target universal tag through a set of mapping relationships, thereby sending data processing policies to one or more data users 120 of one or more dimensions respectively. Furthermore, the one or more data users 120 can receive the data processing policies respectively, and then perform target operations on their respective target data having target custom tags corresponding to the target universal tags.

[0075] In other embodiments, the tag manager 110 may obtain a data processing strategy that indicates a target universal tag among multiple universal tags and a target operation corresponding to the target universal tag. Based on the mapping relationship set, the tag manager 110 may determine one or more target custom tags corresponding to the target universal tag. Then, the tag manager 110 may perform a target operation on the target data having one or more target custom tags. In such an embodiment, after the tag manager 110 determines one or more target custom tags based on the mapping relationship set, it may perform a target operation on the target data having one or more target custom tags.

[0076] In some embodiments, in the mapping relationship set, each universal tag corresponds to at least one custom tag of at least one dimension among the multiple dimensions, and the data identified by each of the at least one custom tag has the same data type. In other words, for custom tags of different dimensions, if the data identified by each of them belongs to the same data type, they will correspond to the same universal tag. This is conducive to unified management of custom tags of multiple dimensions.

[0077] In some embodiments, the mapping relationship set may be represented by a general mapping table, which may include at least a mapping between a general identifier of each general tag and at least one custom identifier of at least one custom tag. Figure 6A-6B Let's discuss the total mapping table of the mapping relationship set in detail.

[0078] Fig. 6AA schematic diagram of an example table 600A of multiple custom labels for multiple dimensions according to some embodiments of the present disclosure is shown. In table 600A, the multiple dimensions include, for example, dimension A, dimension B, dimension C, etc. Several custom labels for each dimension have custom identifiers, respectively. For example, the custom identifiers of several custom labels for dimension A include label_101, label_102, etc. The custom identifiers of several custom labels for dimension B include label_202, label_203, etc. The custom identifiers of several custom labels for dimension C include label_302, etc.

[0079] Figure 6B A schematic diagram of an example total mapping table 600B according to some embodiments of the present disclosure is shown. In the total mapping table 600B, for each universal tag, at least one custom tag of at least one dimension may correspond. The total mapping table 600B, for example, includes multiple universal identifiers of multiple universal tags, such as universal tag_101, universal tag_102, universal tag_103, etc. Universal tag_101 can be mapped to tag_101 of dimension A, tag_202 of dimension B, etc. respectively. Universal tag_102 can be mapped to tag_102 of dimension A, tag_302 of dimension C, etc. respectively. Universal tag_103 can be mapped to tag_203 of dimension B, etc. Thus, through the total mapping table, tags of multiple dimensions can be uniformly managed and marked.

[0080] In some embodiments, in a mapping relationship set, a universal label can be mapped to a custom label for each dimension in at least one dimension among multiple dimensions. For example, in the total mapping table 600B, the universal label _101 can be mapped to only the custom label _101 of dimension A, and can also be mapped to only the custom label _202 of dimension B. The universal label _101 will no longer be mapped to other custom identifiers of dimension A, nor will it be mapped to other custom identifiers of dimension B. It should be understood that the data corresponding to label _101 of dimension A and the data corresponding to label _202 of dimension B have the same data type. Through such an embodiment, it can be ensured that the data classification in each dimension is clear and unambiguous, so that data of the same type can be labeled with the same label.

[0081] In some embodiments, each custom tag in each dimension of the multiple dimensions has a corresponding universal tag in the multiple universal tags. That is, for each dimension of the multiple dimensions, each custom tag can be mapped to only one universal tag in the multiple universal tags. In this way, the custom tags under each dimension can find the corresponding universal tag. This allows the tag manager to easily update and uniformly manage the custom tags of multiple dimensions, and each dimension does not need to modify its existing tag system.

[0082] In some embodiments, in order to determine one or more target custom tags corresponding to the target universal tag, the tag manager 110 may determine a target universal identifier for the target universal tag. Based on the total mapping table, the tag manager 110 may determine one or more target custom identifiers corresponding to the target universal identifier. Based on the one or more target custom identifiers, the tag manager 110 may determine one or more target custom tags.

[0083] Taking the total mapping table 600B as an example, assuming that the target universal identifier of the target universal tag is determined to be universal tag_102, multiple target custom identifiers corresponding to the universal tag_102 can be determined based on the total mapping table 600B, such as tag_102, tag_302, etc. Then, the corresponding multiple target custom tags can be determined according to tag_102, tag_302, etc. Further, it can be determined that the multiple dimensions to which the multiple target custom tags respectively belong are dimension A, dimension C, etc. Then, the tag manager 110 can send data processing policies to the data users respectively associated with dimension A, dimension C, etc.

[0084] In some embodiments, if the first universal tag is updated, the tag manager 110 may determine the first custom tag corresponding to the updated first universal tag. Based on the updated first universal tag and the first custom tag, the tag manager 110 may update the mapping relationship set and send a notification message to the data user associated with the first custom tag. The notification message may indicate the updated mapping relationship set.

[0085] In such an embodiment, the update of the first universal tag may include adding the first universal tag and deleting the first universal tag. In other embodiments, the update of the first universal tag may also include modifying the first universal tag. As an example, in both the updated mapping relationship set and the unupdated mapping relationship set, all custom tags of each dimension need to have corresponding universal tags.

[0086] In some embodiments, the tag manager 110 may receive a request to update the second custom tag from the data user 120 associated with the second custom tag. If the request is received, the tag manager 110 may determine the second common tag corresponding to the second custom tag, and update the mapping relationship set based on the second common tag and the second custom tag. Then, the tag manager 110 may send a response to the request to the data user 120 associated with the second custom tag, and the response may at least indicate the second common tag corresponding to the second custom tag.

[0087] In such an embodiment, the update of the second custom label may include adding the second custom label and deleting the second custom label. In other embodiments, the update of the second custom label may also include modifying the second custom label. If the second custom label is updated, it needs to be approved by the label management party 110, and then the mapping relationship set is updated. As an example, in both the updated mapping relationship set and the unupdated mapping relationship set, all custom labels of each dimension need to have corresponding universal labels.

[0088] In some embodiments, the mapping relationship for the target dimension may be provided by encapsulating a data packet. Alternatively or additionally, in some embodiments, the mapping relationship may be provided by a microservice integrated with a label service. Alternatively or additionally, in some embodiments, the mapping relationship may be provided by a label service deployed in the form of a function as a service. The above has discussed how the mapping relationship for the target dimension can be provided by at least one of an encapsulated data packet, a microservice integrated with a label service, and a label service deployed in the form of a function as a service, and will not be repeated here.

[0089] Through the various embodiments of data tag management disclosed in the present invention, it is possible to standardize the labeling of data and facilitate the unified management of multi-dimensional tags. For a certain dimension, it is convenient to access the tag management party, which is conducive to the rapid deployment and cross-system use of data. It is convenient to reuse data tags of different dimensions. It can solve the current problem that the custom tag capability is too weak and difficult to iterate reasonably. Unified tags can continuously be compatible with the diversity of businesses, and enrich the unified tag system from dimensions such as industry or business, which can meet the use of various businesses, industries, etc. It can bring efficient update and iterative development, and bring efficient and minimalist access methods.

[0090] Example devices and equipment

[0091] The embodiments of the present disclosure also provide corresponding devices for implementing the above methods or processes. Figure 7 A schematic structural block diagram of an example apparatus 700 for data tag processing according to some embodiments of the present disclosure is shown. The apparatus 700 may be implemented as or included in a data consumer 120. Each module / component in the apparatus 700 may be implemented by hardware, software, firmware, or any combination thereof.

[0092] like Figure 7As shown, the device 700 includes an acquisition module 710, which is configured to acquire a mapping relationship between data labels under a target dimension, wherein the mapping relationship indicates a corresponding relationship between multiple common labels of data and multiple custom labels of the target dimension; a receiving module 720, which is configured to receive a data processing strategy, wherein the data processing strategy at least indicates a target common label among multiple common labels and a target operation corresponding to the target common label; a determination module 730, which is configured to determine a target custom label corresponding to the target common label from multiple custom labels based on the mapping relationship; and an execution module 740, which is configured to execute a target operation on target data having a target custom label.

[0093] In some embodiments, the mapping relationship is represented by a mapping table, which at least includes mappings between universal identifiers of each of the plurality of universal tags and custom identifiers of each of the plurality of custom tags.

[0094] In some embodiments, the data processing policy further indicates a target universal identifier of the target universal tag, and the determination module 730 is further configured to determine a target custom identifier corresponding to the target universal identifier based on a mapping table; and determine the target custom tag based on the target custom identifier.

[0095] In some embodiments, in the mapping relationship, one of the plurality of general tags is mapped to zero or one of the plurality of custom tags of the target dimension, and one custom tag of the target dimension is mapped to one of the plurality of general tags.

[0096] In some embodiments, the plurality of common tags are applied to a plurality of dimensions including the target dimension, and each custom tag in each dimension in the plurality of dimensions has a corresponding one common tag in the plurality of common tags.

[0097] In some embodiments, the mapping relationship is obtained by at least one of the following: encapsulating a data packet, integrating a microservice with a label service, or deploying a label service in the form of a function as a service.

[0098] In some embodiments, obtaining the mapping relationship includes: receiving a notification message about updating the first universal tag from a tag manager, the notification message indicating that the first universal tag and the first custom tag corresponding to the first universal tag are updated; and determining the updated mapping relationship based on the notification message.

[0099] In some embodiments, the acquisition module 710 is further configured to send a request to the tag manager to update the second custom label in response to the update of the second custom label of the target dimension; receive a response to the request from the tag manager, the response at least indicating the second universal label corresponding to the second custom label; and determine the updated mapping relationship based on the response.

[0100] In some embodiments, the mapping relationship is one of a plurality of mapping relationships included in the mapping relationship set, and the plurality of mapping relationships are respectively used for a plurality of dimensions, and the plurality of dimensions include a target dimension.

[0101] Figure 8 A schematic structural block diagram of an example apparatus 800 for data tag processing according to some embodiments of the present disclosure is shown. The apparatus 800 may be implemented as or included in the tag manager 110. Each module / component in the apparatus 800 may be implemented by hardware, software, firmware, or any combination thereof.

[0102] like Figure 8 As shown, the device 800 includes a generating module 810, which is configured to generate a mapping relationship set for data tags based on tag configuration information, the mapping relationship set including multiple mapping relationships for multiple dimensions respectively, each mapping relationship indicating a correspondence between multiple common tags and multiple custom tags of corresponding dimensions; and a providing module 820, which is configured to provide a mapping relationship for a target dimension to a data user associated with a target dimension among the multiple dimensions.

[0103] In some embodiments, the device 800 also includes a data processing policy sending module, which is configured to determine a data processing policy based on policy information, the data processing policy indicating a target general tag among multiple general tags and a target operation corresponding to the target general tag; determine one or more target custom tags corresponding to the target general tag and one or more dimensions to which the one or more target custom tags respectively belong based on a set of mapping relationships; and send the data processing policy to one or more data users respectively associated with the one or more dimensions.

[0104] In some embodiments, the device 800 also includes a target operation execution module, which is configured to obtain a data processing strategy, which indicates a target general tag among multiple general tags and a target operation corresponding to the target general tag; determine one or more target custom tags corresponding to the target general tag based on a mapping relationship set; and perform a target operation on target data having one or more target custom tags.

[0105] In some embodiments, in the mapping relationship set, each common tag corresponds to at least one custom tag of at least one dimension among the multiple dimensions, and the data identified by the at least one custom tag respectively have the same data type.

[0106] In some embodiments, the mapping relationship set is represented by a general mapping table, which includes at least a mapping between a general identifier of each general tag and at least one custom identifier of at least one custom tag.

[0107] In some embodiments, the device 800 is also configured to determine a target universal identifier of the target universal tag; determine one or more target custom identifiers corresponding to the target universal identifier based on the total mapping table; and determine one or more target custom tags based on the one or more target custom identifiers.

[0108] In some embodiments, each custom tag in each dimension of the multiple dimensions has a corresponding common tag in the multiple common tags.

[0109] In some embodiments, the device 800 also includes a first update module, which is configured to determine, in response to an update of the first general tag, a first custom tag corresponding to the updated first general tag; update a mapping relationship set based on the updated first general tag and the first custom tag; and send a notification message to a data user associated with the first custom tag, the notification message indicating the updated mapping relationship set.

[0110] In some embodiments, the device 800 also includes a second update module, which is configured to receive a request for updating the second custom tag from a data user associated with the second custom tag; determine the second universal tag corresponding to the second custom tag in response to the request; update the mapping relationship set based on the second universal tag and the second custom tag; and send a response to the request to the data user associated with the second custom tag, the response at least indicating the second universal tag corresponding to the second custom tag.

[0111] In some embodiments, in the mapping relationship set, a common label is mapped to a custom label for each dimension of at least one dimension among the multiple dimensions.

[0112] In some embodiments, the mapping relationship for the target dimension is provided by at least one of the following: an encapsulated data packet, a microservice integrated with a label service, or a label service deployed in the form of a function as a service.

[0113] Fig. 9 900 is a block diagram of an electronic device in which one or more embodiments of the present disclosure may be implemented. It should be understood that Fig. 9The electronic device 900 shown is merely exemplary and should not constitute any limitation on the functionality and scope of the embodiments described herein. Fig. 9 The electronic device 900 shown can be used to implement Figure 1 data user 120 or tag manager 110.

[0114] like Fig. 9 As shown, the electronic device 900 is in the form of a general electronic device. The components of the electronic device 900 may include, but are not limited to, one or more processors or processing units 910, a memory 920, a storage device 930, one or more communication units 940, one or more input devices 950, and one or more output devices 960. The processing unit 910 may be an actual or virtual processor and is capable of performing various processes according to a program stored in the memory 920. In a multi-processor system, multiple processing units execute computer executable instructions in parallel to improve the parallel processing capability of the electronic device 900.

[0115] The electronic device 900 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 900, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 920 can be a volatile memory (e.g., a register, a cache, a random access memory (RAM)), a non-volatile memory (e.g., a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), flash memory) or some combination thereof. The storage device 930 can be a removable or non-removable medium, and can include a machine-readable medium, such as a flash drive, a disk, or any other medium, which can be used to store information and / or data and can be accessed within the electronic device 900.

[0116] The electronic device 900 may further include additional removable / non-removable, volatile / non-volatile storage media. Fig. 9 As shown in , a disk drive for reading or writing from a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading or writing from a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to the bus (not shown) by one or more data media interfaces. Memory 920 may include a computer program product 929 having one or more program modules that are configured to perform various methods or actions of various embodiments of the present disclosure.

[0117] The communication unit 940 implements communication with other electronic devices through a communication medium. Additionally, the functions of the components of the electronic device 900 can be implemented with a single computing cluster or multiple computing machines that can communicate through a communication connection. Therefore, the electronic device 900 can operate in a networked environment using a logical connection with one or more other servers, a network personal computer (PC), or another network node.

[0118] The input device 950 may be one or more input devices, such as a mouse, a keyboard, a tracking ball, etc. The output device 960 may be one or more output devices, such as a display, a speaker, a printer, etc. The electronic device 900 may also communicate with one or more external devices (not shown) through the communication unit 940 as needed, such as a storage device, a display device, etc., communicate with one or more devices that allow a user to interact with the electronic device 900, or communicate with any device that allows the electronic device 900 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).

[0119] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.

[0120] Various aspects of the present disclosure are described herein with reference to the flowcharts and / or block diagrams of the methods, devices, equipment, and computer program products implemented according to the present disclosure. It should be understood that each box in the flowchart and / or block diagram and the combination of each box in the flowchart and / or block diagram can be implemented by computer-readable program instructions.

[0121] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, so that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device that implements the functions / actions specified in one or more boxes in the flowchart and / or block diagram is generated. These computer-readable program instructions can also be stored in a computer-readable storage medium, and these instructions cause the computer, programmable data processing device, and / or other equipment to work in a specific manner, so that the computer-readable medium storing the instructions includes a manufactured product, which includes instructions for implementing various aspects of the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0122] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable data processing apparatus, or other device implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.

[0123] The flow chart and block diagram in the accompanying drawings show the possible architecture, function and operation of the system, method and computer program product according to multiple implementations of the present disclosure. In this regard, each square box in the flow chart or block diagram can represent a part of a module, program segment or instruction, and a part of a module, program segment or instruction includes one or more executable instructions for realizing the logical function of the specification. In some implementations as replacements, the function marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous square boxes can actually be executed substantially in parallel, and they can sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.

[0124] The above descriptions of various implementations of the present disclosure are exemplary, non-exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described implementations. The selection of terms used herein is intended to best explain the principles of the implementations, practical applications, or improvements to the technology in the market, or to enable other persons of ordinary skill in the art to understand the various implementations disclosed herein.

Claims

1. A method for processing data labels, comprising: Acquire a mapping relationship between data labels under a target dimension, wherein the mapping relationship indicates a corresponding relationship between a plurality of common labels of data and a plurality of custom labels of the target dimension; receiving a data processing strategy, wherein the data processing strategy at least indicates a target general tag among the plurality of general tags and a target operation corresponding to the target general tag; Based on the mapping relationship, determining a target custom tag corresponding to the target universal tag from the multiple custom tags; as well as The target operation is performed on the target data having the target custom tag. 2 . The method according to claim 1 , wherein the mapping relationship is represented by a mapping table, and the mapping table at least includes mappings between universal identifiers of each of the plurality of universal tags and custom identifiers of each of the plurality of custom tags.

3. The method of claim 2, wherein the data processing policy further indicates a target universal identifier of the target universal tag, and wherein determining a target custom tag corresponding to the target universal tag comprises: Based on the mapping table, determining a target custom identifier corresponding to the target universal identifier; as well as The target custom tag is determined based on the target custom identifier.

4. The method according to claim 1, wherein in the mapping relationship, one of the multiple common tags is mapped to zero or one of the multiple custom tags of the target dimension, and one custom tag of the target dimension is mapped to one of the multiple common tags. 5 . The method according to claim 1 , wherein the plurality of common tags are applied to a plurality of dimensions including the target dimension, and each custom tag in each dimension of the plurality of dimensions has a corresponding common tag in the plurality of common tags.

6. The method according to claim 1, wherein the mapping relationship is obtained by at least one of the following: Encapsulate data packets, A microservice that integrates a label service, or Label service deployed as Function as a Service.

7. The method according to claim 1, wherein obtaining the mapping relationship comprises: receiving a notification message about updating a first universal tag from a tag manager, wherein the notification message indicates that the first universal tag and a first custom tag corresponding to the first universal tag are updated; as well as Based on the notification message, the updated mapping relationship is determined.

8. The method according to claim 1, wherein acquiring the mapping relationship comprises: In response to the update of the second custom label of the target dimension, sending a request for updating the second custom label to a label manager; receiving a response to the request from the tag manager, wherein the response at least indicates a second universal tag corresponding to the second custom tag; as well as An updated mapping relationship is determined based on the response. 9 . The method according to claim 1 , wherein the mapping relationship is one of a plurality of mapping relationships included in a mapping relationship set, the plurality of mapping relationships are respectively used for a plurality of dimensions, and the plurality of dimensions include the target dimension.

10. A method for processing data labels, comprising: Based on the tag configuration information, a mapping relationship set for the data tag is generated, wherein the mapping relationship set includes a plurality of mapping relationships for a plurality of dimensions respectively, and each mapping relationship indicates a correspondence between a plurality of general tags and a plurality of custom tags of a corresponding dimension; as well as A mapping relationship for a target dimension among the multiple dimensions is provided to a data consumer associated with the target dimension.

11. The method according to claim 10, further comprising: Determining a data processing strategy based on the strategy information, the data processing strategy indicating a target general tag among the plurality of general tags and a target operation corresponding to the target general tag; Based on the mapping relationship set, determining one or more target custom tags corresponding to the target universal tag and one or more dimensions to which the one or more target custom tags respectively belong; as well as The data processing policy is sent to one or more data consumers respectively associated with the one or more dimensions.

12. The method according to claim 10, further comprising: Acquire a data processing strategy, wherein the data processing strategy indicates a target general tag among the plurality of general tags and a target operation corresponding to the target general tag; Based on the mapping relationship set, determining one or more target custom tags corresponding to the target universal tag; as well as The target operation is performed on the target data having the one or more target custom tags.

13. The method according to claim 11, wherein in the mapping relationship set, each common tag corresponds to at least one custom tag of at least one dimension among the multiple dimensions, and the data identified by each of the at least one custom tag has the same data type.

14. The method according to claim 13, wherein the mapping relationship set is represented by a general mapping table, and the general mapping table at least includes a mapping between a general identifier of each general tag and at least one custom identifier of the at least one custom tag.

15. The method according to claim 14, wherein determining one or more target custom tags corresponding to the target universal tag comprises: Determine a target universal identifier of the target universal tag; Based on the total mapping table, determining one or more target custom identifiers corresponding to the target universal identifier; as well as Based on the one or more target custom identifiers, the one or more target custom tags are determined.

16. The method according to claim 10, wherein each custom tag in each dimension of the plurality of dimensions has a corresponding common tag in the plurality of common tags.

17. The method according to claim 10, further comprising: In response to an update of a first universal tag, determining a first custom tag corresponding to the updated first universal tag; Based on the updated first universal tag and the first custom tag, updating the mapping relationship set; as well as A notification message is sent to a data consumer associated with the first custom tag, wherein the notification message indicates the updated mapping relationship set.

18. The method according to claim 10, further comprising: receiving, from a data consumer associated with a second custom tag, a request to update the second custom tag; In response to the request, determining a second universal tag corresponding to the second custom tag; Based on the second general tag and the second custom tag, updating the mapping relationship set; as well as A response to the request is sent to a data user associated with the second custom tag, where the response at least indicates the second universal tag corresponding to the second custom tag.

19. The method according to claim 10, wherein in the mapping relationship set, a general label is mapped to a custom label of each dimension of at least one dimension among the multiple dimensions.

20. The method according to claim 10, wherein the mapping relationship for the target dimension is provided by at least one of the following: Encapsulate data packets, A microservice that integrates a label service, or Label service deployed as Function as a Service.

21. An electronic device comprising: at least one processing unit; as well as At least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions, when executed by the at least one processing unit, causing the electronic device to perform a method according to any one of claims 1 to 9 or 10 to 20.

22. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 9 or 10 to 20.

23. A computer program product tangibly stored in a computer storage medium and comprising computer executable instructions which, when executed by a device, cause the device to perform the method according to any one of claims 1 to 9 or 10 to 20.

Images