Tag information processing method, electronic device, and storage medium

Abstract

The present application discloses a tag information processing method, an electronic device, and a storage medium. The method comprises: obtaining original link tracing information corresponding to a request message, wherein the original link tracing information is used for distinguishing the request message and tagging a calling feature of the request message; on the basis of a preset hierarchical tagging mode, sorting a plurality of tags contained in the original link tracing information to obtain a sorting result, wherein the preset hierarchical tagging mode is used for determining a tagging classification level to which each tag among the plurality of tags belongs, and different tagging classification levels respectively correspond to different sorting priorities; and screening the sorting result on the basis of a preset screening strategy to obtain target link tracing information, wherein the preset screening strategy is used for determining a tag elimination rule matched with the preset hierarchical tagging mode. The present application solves the technical problems of bloated requests, large system burden, and high risks caused by using free tagging during link tracing.

Description

[0001]Technical Field: This application relates to the field of computer technology, and more specifically, to a method for processing tag information, an electronic device, and a storage medium. Background: In the process of link tracing in large-scale distributed systems, during the call process of an Application Programming Interface (API) request, a line tracing solution is typically implemented by freely tagging API requests. That is, at any given moment, any corresponding participant can tag an API request. However, a drawback of this free tagging approach is that multiple participants adding tags to an API request can make the API request extremely cumbersome. As can be seen above, while some existing systems cover link tracing solutions, they only consider functionality in freely tagging API requests, without designing a comprehensive request tagging solution. When the scope of API request call links is large, this free tagging solution often leads to cumbersome tags, heavy system burden, and low security. These issues are widespread in systems involving link tracing. Currently, no effective solution has been proposed to address these issues. SUMMARY OF THE INVENTION Embodiments of the present application provide a tag information processing method, electronic device, and storage medium to at least address the technical issues of using a free tagging approach during link tracing, which results in bloated requests, heavy system burden, and high risk. According to one aspect of an embodiment of the present application, a tag information processing method is provided, comprising: obtaining original link tracing information corresponding to a request message, wherein the original link tracing information is used to distinguish the request message and tag the call characteristics of the request message; sorting multiple tags contained in the original link tracing information according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, with different tag classification levels corresponding to different sorting priorities; and filtering the sorting result based on a preset filtering policy to obtain target link tracing information, wherein the preset filtering policy is used to determine a tag elimination rule that matches the preset hierarchical tagging method.According to another aspect of an embodiment of the present application, a tag information processing method is further provided, comprising: obtaining a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, the original link tracking information being used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, the target link tracking information being obtained by filtering a sorting result based on a preset screening strategy, the preset screening strategy being used to determine a tag elimination rule that matches a preset hierarchical tagging method, the sorting result being obtained by sorting multiple tags contained in the original link tracking information according to the preset hierarchical tagging method, the preset hierarchical tagging method being used to determine a tag classification level to which each of the multiple tags belongs, and different tag classification levels corresponding to different sorting priorities. According to another aspect of an embodiment of the present application, a tag information processing method is provided, comprising: obtaining a currently input link tracking screening dialogue request, wherein the request data carried in the link tracking screening request includes: original link tracking information, the original link tracking information being used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening dialogue reply in response to the link tracking screening dialogue request, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, the target link tracking information being obtained by filtering a sorting result based on a preset screening strategy, the preset screening strategy being used to determine a tag elimination rule that matches a preset hierarchical tagging method, the sorting result being obtained by sorting multiple tags included in the original link tracking information according to the preset hierarchical tagging method, the preset hierarchical tagging method being used to determine a tag classification level to which each of the multiple tags belongs, different tag classification levels corresponding to different sorting priorities; and displaying the target link tracking information in a graphical user interface. According to another aspect of an embodiment of the present application, an electronic device is provided, comprising: a memory storing an executable program; and a processor configured to execute the program, wherein when the program is executed, any one of the aforementioned methods for processing tag information is executed. According to another aspect of an embodiment of the present application, a computer-readable storage medium is provided, wherein the computer-readable storage medium includes a stored executable program, wherein when the executable program is executed, the computer-readable storage medium controls the device containing the computer-readable storage medium to execute any one of the aforementioned methods for processing tag information. According to another aspect of an embodiment of the present application, a computer program product is provided, comprising the computer program, wherein when executed by the processor, the computer program implements any one of the aforementioned methods for processing tag information.In an embodiment of the present application, original link tracking information corresponding to a request message is obtained, where the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message. Multiple tags contained in the original link tracking information are sorted according to a preset hierarchical tagging method to obtain a sorting result. The preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, with different tag classification levels corresponding to different sorting priorities. The sorting result is filtered based on a preset filtering strategy to obtain target link tracking information. The preset filtering strategy is used to determine a tag elimination rule that matches the preset hierarchical tagging method. Thus, the present application achieves the purpose of sorting and eliminating multiple tags in the link tracking information based on the preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging in link tracking and improving system security. This further solves the technical problem that the use of a free tagging method in the link tracking process leads to bloated requests, heavy system burden, and high risk. It should be noted that the general description above and the detailed description below are merely for the purpose of exemplifying and explaining the present application and do not constitute a limitation of the present application. BRIEF DESCRIPTION OF THE DRAWINGS The drawings described herein are used to provide a further understanding of the present application and constitute a part of the present application. The illustrative embodiments of the present application and their descriptions are used to explain the present application and do not constitute an improper limitation on the present application. In the accompanying drawings: Figure 1 shows a hardware structure block diagram of a computer terminal (or mobile device) configured to implement a tag information processing method; Figure 2 is a schematic diagram of an optional link tracking architecture according to Example 1 of the present application; Figure 3 is a flow chart of a tag information processing method according to Example 1 of the present application; Figure 4 is a schematic diagram of an optional link tracking information preliminary processing process according to Example 1 of the present application; Figure 5 is a schematic diagram of an optional link tracking information secondary screening process according to Example 1 of the present application; Figure 6 is a schematic diagram of another optional link tracking information secondary screening process according to Example 1 of the present application; Figure 7 is a flow chart of a tag information processing method according to Example 2 of the present application; Figure 8 is a flow chart of a tag information processing method according to Example 3 of the present application; Figure 9 is a structural schematic diagram of a tag information processing device according to Example 4 of the present application; Figure 10 is a structural schematic diagram of another tag information processing device according to Example 4 of the present application; Figure 11 is a structural schematic diagram of another tag information processing device according to Example 4 of the present application; Figure 12 is a structural block diagram of an electronic device according to Example 5 of the present application.DETAILED DESCRIPTION To help those skilled in the art better understand the present invention, the following will provide a clear and complete description of the technical solutions in the embodiments of the present invention, with reference to the accompanying drawings. It should be noted that the described embodiments represent only a portion of the present invention, and are not exhaustive. All other embodiments devised by persons of ordinary skill in the art based on the embodiments of the present invention without inventive effort should fall within the scope of protection of the present invention. It should be noted that the terms "first," "second," and so on, in the specification and claims of the present invention, and in the accompanying drawings, are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that such terms are interchangeable where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than that illustrated or described herein. Furthermore, the terms "including," "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not necessarily limited to the steps or elements expressly listed, but may include other steps or elements not expressly listed or inherent to such process, method, product, or apparatus. First, some nouns or terms that appear in the description of the embodiments of this application are subject to the following explanations. Application Programming Interface Request: A request to access a specific service or function by calling an Application Programming Interface (API). API requests are typically sent via the Hypertext Transfer Protocol (HTTP) and are used to request specific functions or data, such as obtaining data from a server, sending data to a server, or performing a specific operation. In this example, an API request refers to a request issued by a user when invoking a corresponding service through an API to complete an operation such as a query or create. Tracing: A technology used to track the flow and execution path of requests in a distributed system. By recording the call and transmission information of API requests between each component and service in a distributed system, the entire execution process of the request in the system can be tracked. Example 1: According to an embodiment of this application, an embodiment of a tag information processing method is also provided. It should be noted that the steps shown in the flowcharts of the accompanying figures can be executed in a computer system, such as a set of computer-executable instructions. Although the flowcharts show a logical order, in some cases, the steps shown or described can be executed in a different order than shown.The method embodiment provided in Example 1 of the present application can be executed in a mobile terminal, a computer terminal, or a similar computing device. Figure 1 shows a hardware block diagram of a computer terminal (or mobile device) configured to implement the tag information processing method. As shown in Figure 1, the computer terminal 10 (or mobile device 10) may include one or more processors 102 (illustrated as 102a, 102b, 102n in the figure) (the processor 102 may include, but is not limited to, a microcontroller unit (MCU) or a field programmable gate array (FPGA) processing device), a memory 104 configured to store data, and a transmission device 106 configured to perform communication functions. In addition, the computer terminal 10 may also include: a display, an input / output interface (I / O interface), a Universal Serial Bus (USB) port (which may be included as one of the ports of a computer bus), a network interface, a cursor control device (such as a mouse, touchpad, etc.), a keyboard, a power supply, and / or a camera. Those skilled in the art will appreciate that the structure shown in FIG. 1 is merely illustrative and does not limit the structure of the electronic device described above. For example, the computer terminal 10 may include more or fewer components than shown in FIG. 1 , or have a configuration different from that shown in FIG. It should be noted that the one or more processors 102 and / or other data processing circuits described above may generally be referred to herein as "data processing circuitry." This data processing circuitry may be embodied in whole or in part as software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuitry may be a single, independent processing module, or may be fully or partially integrated into any of the other components of the computer terminal 10 (or mobile device). As described in the embodiments of the present application, the data processing circuitry serves as a processor control (e.g., selecting a variable resistor terminal path connected to an interface). The memory 104 may be configured to store software programs and modules of application software, such as the program instructions / data storage device corresponding to the tag information processing method described in the embodiments of the present application. The processor 102 executes the software programs and modules stored in the memory 104 to perform various functional applications and data processing, thereby implementing the tag information processing method described above. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory.In some examples, the memory 104 may further include memories remotely located relative to the processor 102, and these remote memories may be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. The transmission device 106 is configured to connect to the network via a network interface to receive or transmit data. Specific examples of such networks may include wired and / or wireless networks provided by the computer terminal 10's communications provider. In one example, the transmission device 106 includes a network interface controller (NIC), which can be connected to other network devices via a base station to communicate with the Internet. In one example, the transmission device 106 may be a radio frequency (RF) module configured to communicate with the Internet wirelessly. Figure 2 is a schematic diagram of a link tracing architecture provided according to Example 1 of the present application. As shown in Figure 2, during the link tracing process in a large-scale distributed system, when each API request (in this example, a request message issued based on stress testing traffic and an operations and maintenance tool) enters the system, the system generates a unique identifier to identify the API request. This unique identifier is typically a Universally Unique Identifier (UUID). This unique identifier of the API request is used throughout the entire call process corresponding to the API request, in every sub-call process and subsystem (e.g., each of the multiple applications involved in the call). As shown in Figure 2, the multiple applications involved in the link tracing process in this example include: database-based source tracing, workflow-based full tracing, HTTP-based full tracing, distributed service framework-based full tracing, message-based full tracing, and asynchronous thread-based full tracing. For each application in the call process, this unique identifier will accompany the actual call process in a bypass manner. When a cross-application call occurs, the unique identifier is passed to the downstream application as additional data or an extended field. Upon receiving the unique identifier, the downstream application restores the API request content corresponding to the unique identifier to the same state as in the upstream application. This means that multiple applications involved in the API request's call flow can obtain the API request's identification information (including the unique identifier and other application tags). In subsequent API request call chains, tracing is typically achieved by freely tagging API requests. This means that any participating party can tag an API request at any given moment.However, the drawback of free tagging is that multiple parties adding tags to API requests can make the API request extremely cumbersome. Each set of key-value tags in an API request's call chain is passed through multiple applications along the chain. This means that adding key-value tags imposes a burden on every layer of the system. However, different nodes in the system have different requirements for the maximum amount of information required to meet API request requirements. When the number of key-value tags in API requests continues to increase, the system burden increases to a certain level, potentially leading to major system failures (such as system crashes). As can be seen from the above, while some existing systems include tracing solutions, they only consider functionality in free tagging API requests without designing a comprehensive request tagging solution. When the scope of API request call chains is large, free tagging solutions often lead to cumbersome tags, heavy system burdens, and low security. These issues are common in systems involving tracing. The display shown in Figure 1 can be, for example, a touchscreen liquid crystal display (LCD), which enables a user to interact with the user interface of the computer terminal 10 (or mobile device). In the aforementioned operating environment, the present application provides a tag information processing method as shown in Figure 3. Figure 3 is a flowchart of a tag information processing method according to Example 1 of the present application. As shown in Figure 3, the tag information processing method includes: Step S31: Obtaining original link tracking information corresponding to a request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message. The request message can be an API request message in a preset application scenario. The preset application scenario is an application scenario involving distributed system link tracking. Correspondingly, the tag information is link tracking information in the distributed system. For example, the preset application scenario can include, but is not limited to, scenarios providing API call services in fields such as e-commerce, education, healthcare, conferences, social networks, financial products, logistics, and navigation. Correspondingly, the aforementioned tag information processing method is used to provide link tracing information processing services for the aforementioned predefined application scenarios, thereby improving the performance of the link tracing system in the aforementioned predefined application scenarios. This embodiment of the present application expands upon the related art's free tagging scheme by extending the length and content of the identification field of the request message. This allows the original link tracing information obtained by tagging the request message to not only distinguish the request message but also to identify the call characteristics of the request message.The call features described above include features from multiple dimensions, for example, including the call source, caller, and call entry. In step S32, the multiple tags included in the original link tracing information are sorted according to a preset hierarchical labeling scheme to obtain a sorting result. The preset hierarchical labeling scheme is used to determine the labeling classification level to which each of the multiple tags belongs, with different labeling classification levels corresponding to different sorting priorities. The original link tracing information described above includes multiple tags, which may be the result of multiple applications in the call link corresponding to the request message labeling the request message. Under the predefined hierarchical labeling scheme in the embodiments of the present application, a sorting priority is determined for each of the multiple tags to determine the labeling classification level to which each tag belongs. The multiple preset sorting priorities correspond to the multiple labeling classification levels. Furthermore, based on the sorting priorities, the multiple tags are sorted to obtain a sorting result, in which the multiple tags are arranged in ascending or descending order of priority. In step S33, the sorting results are filtered based on a preset filtering strategy to obtain the target link tracking information. The preset filtering strategy is used to determine tag elimination rules that match the preset hierarchical tagging scheme. According to the above method steps of the embodiment of the present application, the sorting results are filtered under the preset filtering strategy to discard some tags in the original link tracking information to obtain the target link tracking information. The filtering strategy matches the preset hierarchical tagging scheme. For example, the filtering strategy is used to determine some tags to be discarded from multiple tags based on the tag classification level to which each tag belongs. For example, tags in tag classification levels corresponding to lower sorting priorities are preferentially determined as some tags to be discarded. In an embodiment of the present application, original link tracking information corresponding to the request message is obtained, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; multiple tags contained in the original link tracking information are sorted according to a preset hierarchical labeling method to obtain a sorting result, wherein the preset hierarchical labeling method is used to determine the labeling classification level to which each of the multiple tags belongs, and different labeling classification levels correspond to different sorting priorities; based on a preset screening strategy, the sorting result is filtered to obtain target link tracking information, wherein the preset screening strategy is used to determine a tag elimination rule that matches the preset hierarchical labeling method.Thus, the present application achieves the goal of sorting and filtering multiple tags in link tracking information based on a preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging in link tracking and improving system security. This further solves the technical problem that the use of a free tagging method in the link tracking process leads to bloated requests, heavy system burden, and high risk. In an optional embodiment, the tag information processing method further includes the following method steps: Step S341, tagging the request message to obtain multiple tags, wherein the multiple tags include: a tag type field, a tag key field, and a tag value field, and the tag type field, the tag key field, and the tag value field are all added according to the operation specifications corresponding to the preset hierarchical tagging method; Step S342, generating original link tracking information based on the multiple tags. When tagging the request message, the tag type field, tag key field, and tag value field are added to the link tracking information of the request message according to the operation specifications corresponding to the preset hierarchical tagging method. The tag type field is used to determine the tag classification level to which the corresponding tag belongs, further characterizing the sorting priority of the corresponding tag. Each tag classification level can correspond to multiple sets of key-value tags, each set of key-value tags including a tag key field and a tag value field (i.e., a key-value pair). During link tracing in a distributed system, raw link tracing information is generated based on multiple tags. Specifically, this can be achieved by storing the multiple tags in a specific data structure (such as a list or array) to obtain the raw link tracing information. In an exemplary application scenario, according to the operating specifications corresponding to the preset hierarchical tagging method, when adding a tag key field, the tag key field can include multiple subfields. The tag key field begins with an underscore, and the multiple subfields are separated by underscores. Each of the multiple subfields begins with a "$" symbol. The multiple subfields include at least a source subfield, an attribute subfield, and a priority subfield. The source subfield is used to determine the source information of the tag key field, the attribute subfield is used to determine the attribute information of the tag key field, and the priority subfield is used to determine the sorting priority information of the tag key field. In an exemplary embodiment, the free tagging scheme of the related art is expanded by extending the length and content of the identification field of the request message. The key-value (KV) structure is flexibly transmitted to the downstream of the call process in a distributed system in the same manner as the link tracking information (i.e., the identifier of the request message). In this case, the link tracking information is also called a coloring tag, and the information corresponding to the coloring tag includes call characteristics of multiple dimensions of the request message.Based on the aforementioned coloring tags, when performing link tracing in a distributed system, the tracing information can be modified in any application in the call flow of the API request corresponding to the coloring tag. In other words, any application in the call flow can add a key-value tag to each request message. According to the above-described method steps of the embodiment of the present application, a coloring tagging method based on link tracing is provided, which is suitable for large-scale distributed systems. The link tracing information includes a field for determining the sorting priority of each tag. This facilitates the management of link tracing information during the call flow of the request message, allowing for the timely deletion of lower-priority tags, thereby reducing system risks caused by excessive tags freely added to the link tracing information. In an optional embodiment, in step S32, multiple tags included in the original link tracing information are sorted according to a preset hierarchical tagging method to obtain a sorting result. The method steps include the following: Step S321: Identifying the tag classification level corresponding to the tag type field according to the preset hierarchical tagging method; Step S322: Sorting the multiple tags based on the tag classification level to obtain a sorting result. In the aforementioned optional embodiment, the tag type field corresponding to each of the multiple tags in the link tracking information is identified according to a preset hierarchical tagging method to determine the tag classification level of the tag. Furthermore, the multiple tags are sorted based on the tag classification levels to obtain a sorting result. In an exemplary embodiment, the multiple classification tag levels corresponding to the multiple tags determined according to the preset hierarchical tagging method (in descending order of priority) include: a first level, a second level, a third level, a fourth level, and a fifth level. In the first-level tags described above, the tag type field is divided into two types: the first type is used to mark system-level tag keys and has the highest priority. This type of tag type field uniformly begins with "_system". For example, the tag type field can be "_system_acs_sourcetype", "_system_acs_source", "_system_acs_markertype", "_system_acs_marker", etc. Tags corresponding to this type of tag type are in a non-discardable state (also known as a fixed state). The second type of tag type is used to mark other preset link tracking-related tag keys, such as the trace ID (traceID). It should be noted that if a non-system-level tag is identified as the first type at the first level, there is no availability guarantee for the tag, meaning that the tag can be discarded at any time.In the second-level tagging described above, the tag type field is divided into two types: the first type is used to mark a custom tag key for a service. For example, operations personnel will ensure that the tag keys of the services under their jurisdiction belong to this tag type field. Correspondingly, the tag type field corresponding to the devops service may be "_devops_debuglog"; the second type is used to mark the tag key for pass-through requests from other services. After the current service receives this tag key, it must prioritize ensuring that this tag key is passed to the downstream of the calling process. This tag type field begins with "_rpt" (short for Request Pass Through). For example, this tag type field may be "_rpt_passingthrough". In the third-level tags, the tag type field is used to identify other tag keys that require identification, as well as tag keys that contain service information (e.g., stress test source, external call, etc.). The third-level tag type field begins with ".traffic." For example, the tag type field corresponding to the tag key used to identify the stress test source might be "_traffic_pressure." The fourth-level tags include tags added by other services to request messages. For example, for the operations subsystem, tags added by the quality subsystem and the business subsystem belong to the fourth level. For example, the tag type field in the tag added by the quality subsystem might be "_quality_info." Tags whose subsystem origins are unidentifiable also belong to the fourth level. The fifth-level tags do not contain a tag header. Fifth-level tags are typically discarded and not passed in the call process. Therefore, multiple tags are sorted by priority based on the tag type field to obtain a sorting result. Based on this sorting result, when some tags need to be discarded, lower-priority tags can be easily identified as those to be discarded. In an optional embodiment, in step S321, identifying the tag classification level corresponding to the tag type field according to a preset hierarchical tagging method includes the following method steps: Step S3211: Parsing multiple tags to obtain a tag key field and a tag type field corresponding to the tag key field; Step S3212: Identifying the tag type field according to the preset hierarchical tagging method to obtain the tag classification levels corresponding to the multiple tags. During the link tracing process, each of the multiple tags may include a tag key field and a tag type field. Parsing each tag in the multiple tags to obtain the tag key field and tag type field in the tag further determines the tag classification level corresponding to the tag.According to the preset marking operation specification, the first level of marking (ie, system-level marking) includes a plurality of fixed reserved marks, and each fixed reserved mark includes a key-value pair. Specifically, the above-mentioned multiple fixed reserved tags include: a first tag key "_system_sourcetype", corresponding to the first tag value of the system from which the request message originally originated, which will not be modified once it exists; a second tag key "_system_source", corresponding to the second tag value of the source information originally carried by the request message, which will not be modified once it exists; a third tag key "_system_markertype", corresponding to the third tag value of the call source of this system, which serves as a marker for the system entry and can be modified by the system; a fourth tag key "_system_marker", corresponding to the fourth tag value of the call source information within this system, which can be modified by the system. It should be noted that the above-mentioned multiple fixed reserved tags are checked and supplemented at multiple external entrances of the system (in this example, each external entrance under the jurisdiction of each service) and cannot be supplemented in intermediate links other than the entrance. For example, the above-mentioned multiple external entrances include: external API, start node of scheduled task, Other non-determined aspects can be used to mark the complete start of a call. According to steps S3211 to S3213 above, taking the tag key field of a tag obtained as the first tag key "_system_sourcetype" as an example, the tag type field "_system" in the first tag key is further determined, thereby determining that the tag classification level to which the tag belongs is the first level (i.e., the system level). Therefore, through the above-mentioned unified tag identification method, each node in the system identifies the API request identifier according to this unified identification method. This allows the source and priority of multiple tags to be obtained without enumerating the tag keys in the key-value tag, which is highly efficient. In an optional embodiment, in step S322, multiple tags are sorted based on the tag classification level to obtain a sorting result, including the following method steps: Step S3221: Based on the tag classification level, the multiple tags are sorted from high to low according to sorting priority to obtain a sorting result. When some tags have the same sorting priority, the tags are sorted according to the length of the tag value field corresponding to the tags. In an exemplary application scenario, after determining the marking classification levels of multiple tags, the multiple tags are sorted in descending order of sorting priority to obtain a sorting result.For at least two tags with the same sorting priority, a secondary sort is performed on these tags based on their lengths, from shortest to longest. Furthermore, for tags with the same sorting priority and length, further sorting rules can be set based on scenario requirements, such as name sorting, random sorting, etc. For example, in one application scenario, the method steps described above, according to an embodiment of the present application, provide a process for processing multiple tags in link tracing information, as shown in FIG4 . The tag classification level of each tag is determined based on the key field in the multiple tags, and the multiple tags are sorted according to the tag classification level to obtain a sorting result. As shown in FIG4 , the value length of each tag is recorded during the sorting process for reference in the subsequent discarding process. Still as shown in FIG4 , in the sorting result, the top layer contains the retained fixed tags, followed by a sorting process from high to low priority (i.e., from level 1 to level 5). In particular, the three tags in level 4 are sorted from short to long value length. Thus, the sorting process considers not only priority but also tag length to obtain a sorting result. Based on this sorting result, when some tags need to be discarded, it is possible to more accurately identify tags with lower priority and longer length as tags to be discarded. In an optional embodiment, the preset filtering strategy includes a fixed filtering strategy and a custom filtering strategy. In step S33, the sorting results are filtered based on the preset filtering strategy to obtain target link tracking information. The method includes the following steps: Step S331: Initially filtering the sorting results based on the fixed filtering strategy to obtain a preliminary screening result. The fixed filtering strategy is a universal filtering strategy for all request messages. Step S332: Re-filtering the preliminary screening result based on the custom filtering strategy to obtain the target link tracking information. The custom filtering strategy is a personalized filtering strategy corresponding to the request message. Under the free tagging strategy, the number of field tags in the link tracking information may be very large. Over time, the number of custom tags from multiple applications will increase, and the system burden will correspondingly increase. Therefore, it is necessary to filter and discard the existing multiple tags. The above fixed screening strategy is used to perform a preliminary screening of the sorting results according to the general screening rules, discard some marks, and obtain the preliminary screening results.Still as shown in FIG4 , during the initial discarding of the tag sorting results, a fixed screening strategy is used to discard any overlong single tags from the multiple tags in the tag sorting results (i.e., overlong discard, in this example, the overlong tag is "_business_test"). Also, meaningless tags from the multiple tags in the tag sorting results are discarded (i.e., meaningless discard, discarding tags at the fifth level, in this example, the meaningless tag is "xxText"). Furthermore, based on the initial screening results, a second screening is performed according to a custom screening strategy, further discarding some tags to obtain target link tracking information. In an optional embodiment, in step S332, the initial screening results are re-screened based on a custom screening policy to obtain target link tracking information, including the following method steps: Step S3321: Re-screen the initial screening results based on the upper limit of the number of tag keys corresponding to the tag key field to obtain target link tracking information; Alternatively, Step S3322: Re-screen the initial screening results based on the upper limit of the tag value length corresponding to the tag value field to obtain target link tracking information. In this optional embodiment, during the processing of multiple tags, multiple applications in the call flow of the request message define their own upper limits on the tag value length, for example, the tag value of a single tag does not exceed 100 characters, and the total length of the tag values ​​of multiple tags does not exceed 1000 characters. Multiple applications may also define their own upper limits on the number of tag keys, for example, the number of tag keys does not exceed 6 (i.e., a maximum of 6 tags are retained). Based on the custom screening policy, the upper limit of the number of tag keys corresponding to the tag key field is determined to be 6 (i.e., a limit on the total number of keys). As shown in Figure 5, the results obtained after the initial discard are screened and discarded again, working backwards to ensure that the number of tag keys does not exceed six. Specifically, after the initial discard, 12 key-value tags remain. The first three are fixed tags and are not counted in the total. Starting from the 12th, tags are discarded in reverse order until six key-value tags remain, i.e., the 4th through 9th key-value tags are retained. This results in the second screening and second discard. Based on a custom screening strategy, the tag value length corresponding to the tag key field is set to an upper limit of 200 characters (also the total number of keys). As shown in Figure 6, the results obtained after the initial discard are screened and discarded again, working backwards to ensure that the tag value length does not exceed 300 characters.Specifically, after the initial discarding of the remaining 12 key-value tags, the first three of which are fixed tags and not counted in the total, tags are discarded starting from the 12th tag, in reverse order, until the total length of the remaining tag values ​​does not exceed 300 characters. In other words, the 4th to 11th key-value tags are retained, resulting in the secondary screening and secondary discarding results. Therefore, according to the above method steps, in application scenarios, the upper limit of the number of tag keys or the upper limit of the tag value length can be flexibly set according to scenario requirements to control the number of tag request messages retained by the system during link tracing, thereby reducing system burden and risk. In an optional embodiment, the tag information processing method further includes the following method steps: Step S35: Setting multiple checkpoints, wherein the multiple checkpoints are used to tag and intercept request messages during the transmission process to filter and obtain target link tracing information. The multiple checkpoints can be multiple checkpoints preset in the link tracing system. The multiple checkpoints typically include entry nodes for a set of applications (i.e., multiple applications) involved in a particular service. In an exemplary application scenario, during the processing of multiple tags, tagging and interception are performed at multiple checkpoints in the system. Performing inspection and interception within each service would incur significant system overhead, while performing inspection and interception only at the entry point would be less effective. Therefore, multiple applications are grouped together as a whole, and tagging and interception are performed on all request messages at the entry point of this whole. In an optional embodiment, the tag information processing method further includes the following method steps: Step S361: Obtaining multiple statistical values ​​at multiple checkpoints, where the multiple statistical values ​​include: the total number of requests passed through multiple channel entry points and the number of requests passed with preset tags, and the total number of requests passed through a single channel entry point and the number of requests passed with preset tags at the multiple checkpoints; Step S362: Evaluating the effectiveness of tagging for the multiple channel entry points based on the total number of requests passed through the multiple channel entry points and the number of requests passed with preset tags, and evaluating the effectiveness of tagging for the single channel entry points based on the total number of requests passed through the single channel entry points and the number of requests passed with preset tags. The aforementioned multi-channel entry points include the start node of an external APL scheduled task and other non-deterministic aspects that can mark the complete start of a call. The aforementioned preset tags can be first-level fixed tags. During the inspection, request messages with first-level fixed tags are considered to have no missing tags or delivery omissions. In other words, if a request message is accompanied by a first-level fixed tag, it is considered to contain a valid tag.In an exemplary application scenario, through statistics at multiple checkpoints, the total number of requests passing through the multi-channel entry is recorded as TO, and the number of requests passing through the multi-channel entry with preset tags is recorded as TL. Based on this, the effective labeling of the multi-channel entry can be evaluated by calculating the ratio of the number of requests passing through the multi-channel entry with preset tags to the total number of requests passing through the multi-channel entry, and the total labeling efficiency R of the multi-channel entry can be obtained, that is, R = T1 / TO. In an exemplary application scenario, through statistics at multiple checkpoints, the total number of requests passing through each of the multiple channel entry points is recorded as A0, and the number of requests with preset tags passing through each channel entry is recorded as A1. Based on this, the effective tagging of the multiple channel entry points can be evaluated by calculating the ratio of the number of requests with preset tags passing through each channel entry to the total number of requests passing through each channel entry, thereby obtaining the single-channel tagging efficiency RA for each channel entry, that is, RA = A1 / AO. Through the above method steps, statistical analysis of multiple indicators at multiple checkpoints can be performed to evaluate the tagging efficiency and further evaluate the performance and reliability of the system. In an optional embodiment, the tag information processing method further includes the following method steps: Step S363: During the transmission of the request message, the target link tracking information retained after screening is synchronously transmitted, and the transmission of the filtered and eliminated information is stopped. In an exemplary application scenario, after filtering and partially discarding multiple tags in the link tracking information, The retained tags will continue to be transmitted synchronously with the request message during the call process (e.g., they may be transmitted in a bypass), while the discarded tags will not be transmitted further, thereby reducing the system burden. It is easy to note that if problems caused by the large amount of tagged information are not addressed until the system has encountered them, the problem will be difficult to solve and the system will still face significant risks. Therefore, the solution provided by the embodiments of the present application is to pre-design a solution for tagging API requests in distributed system link tracing, and to standardize the tagging behavior in the system. According to the embodiments of the present application, a solution for tagging API requests in distributed system link tracing can be designed.This tagging scheme includes at least the following: determining a core tag (i.e., a first-level fixed tag) that must be maintained by every application in the entire system. An API request with this core tag indicates that there are no tag omissions or transfer omissions in the call chain corresponding to the API request; determining a unified tag identification method. Each node in the entire system identifies the API request tag according to this unified identification method, thereby obtaining the source and priority of the API request tag without enumerating the keys in the key-value tag; and determining a tag discarding method. At each key node in the system (such as a node where cross-application calls occur), the tag field length is determined. If the tag field length exceeds a preset threshold, portions of the tag field are discarded according to a discarding rule. In this embodiment of the present application, a hierarchical tagging approach is used to define tag levels without enumerating the tag key-value content. This tag level also helps evaluate tagging efficiency. Furthermore, the above-mentioned method provided in this embodiment of the present application can effectively address the problem of API request bloat caused by free tagging schemes. Some tags are discarded during the tagging process, thereby ensuring that system performance is not significantly affected by excessive tag information contained in bypassed API requests. It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, storage, and display, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of the relevant data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation portals are provided for the user to choose to authorize or reject. It should be noted that for the sake of simplicity, the aforementioned method embodiments are described as a series of actions. However, those skilled in the art should be aware that this application is not limited by the order of the actions described, as certain steps can be performed in a different order or simultaneously according to this application. Secondly, those skilled in the art should also be aware that the embodiments described in this specification are all preferred embodiments, and the actions and modules involved are not necessarily required for this application. Through the above description of the embodiments, those skilled in the art can clearly understand that the methods according to the above embodiments can be implemented using software and a necessary general-purpose hardware platform, or of course, hardware.Based on this understanding, the technical solution of this application, or the portion that contributes to the prior art, can essentially be embodied in the form of a software product. This computer software product is stored in a storage medium (such as a read-only memory (ROM), random access memory (RAM), magnetic disk, or optical disk) and includes instructions for enabling a terminal device (such as a mobile phone, computer, server, or network device) to execute the methods described in various embodiments of this application. Example 2: In the operating environment described in Example 1, this application provides another tag information processing method, as shown in Figure 7. FIG7 is a flowchart of a tag information processing method according to Example 2 of the present application. As shown in FIG7 , the tag information processing method includes: Step S71, obtaining a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; Step S72, returning a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening policy, wherein the preset screening policy is used to determine a tag elimination rule that matches a preset hierarchical tagging method, and the sorting result is obtained by sorting multiple tags included in the original link tracking information according to the preset hierarchical tagging method, wherein the preset hierarchical tagging method is used to determine a tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities. According to the above method steps, a cloud service for processing link tracing information is provided. The cloud service is deployed on a cloud server and receives a link tracing filtering request sent by a service caller via a first application programming interface (API). Based on the link tracing filtering request, the service obtains original link tracing information, sorts, filters, and eliminates multiple tags in the original link tracing information to obtain target link tracing information. A link tracing filtering response is generated based on the target link tracing information, and the link tracing filtering response is returned to the service caller via a second application programming interface (API). The request message may be an API request message in a predefined application scenario. The predefined application scenario is an application scenario involving distributed system link tracing. For example, the predefined application scenario may include, but is not limited to, scenarios providing API call services in fields such as e-commerce, education, healthcare, conferences, social networks, financial products, logistics, and navigation.Correspondingly, the tag information processing method described above is used to provide link tracing information processing services for the aforementioned preset application scenarios, thereby improving the performance of the link tracing system in the aforementioned preset application scenarios. This embodiment of the present application expands upon the related art's free tagging scheme by extending the length and content of the identification field of the request message. This allows the original link tracing information obtained by tagging the request message to not only distinguish the request message but also to tag the call characteristics of the request message. These call characteristics include features from multiple dimensions, such as the call source, caller, and call entry point. The original link tracing information includes multiple tags, which may be the result of multiple applications tagging the request message in the call link corresponding to the request message. Under the predefined hierarchical tagging method in this embodiment of the present application, a sorting priority is determined for each of the multiple tags, and the tag classification level to which each tag belongs is determined. Multiple preset sorting priorities correspond to the multiple tag classification levels. Furthermore, based on the sorting priorities, the multiple tags are sorted to obtain a sorting result, in which the multiple tags are arranged in ascending or descending order of priority. According to the above-described method steps of the embodiment of the present application, the sorting results are filtered under a preset filtering strategy to discard some tags in the original link tracking information, thereby obtaining the target link tracking information. This filtering strategy matches a preset hierarchical labeling scheme. For example, the filtering strategy is used to determine some tags to be discarded from a plurality of tags based on the labeling classification level to which each tag belongs. For example, tags in labeling classification levels corresponding to lower sorting priorities are preferentially determined as some tags to be discarded. In an embodiment of the present application, a link tracking screening request is obtained through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; a link tracking screening response is returned through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening strategy, wherein the preset screening strategy is used to determine a mark elimination rule that matches a preset hierarchical marking method, and the sorting result is obtained by sorting multiple marks included in the original link tracking information according to the preset hierarchical marking method, wherein the preset hierarchical marking method is used to determine a marking classification level to which each mark among the multiple marks belongs, and different marking classification levels correspond to different sorting priorities.Thus, this application achieves the goal of sorting and filtering multiple tags in link tracking information based on a preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging during link tracking and improving system security. This further solves the technical problem of using a free tagging method during link tracking, which leads to bloated requests, heavy system burden, and high risk. It should be noted that the preferred implementation of this embodiment can be found in the relevant description of Example 1 and will not be repeated here. Example 3 In the operating environment of Example 1, this application provides another tag information processing method as shown in Figure 8. FIG8 is a flowchart of a tag information processing method according to Embodiment 3 of the present application. As shown in FIG8 , the tag information processing method includes: Step S81, obtaining a currently input link tracking screening dialogue request, wherein the request data carried in the link tracking screening dialogue request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; Step S82, in response to the link tracking screening dialogue request, returning a link tracking screening dialogue reply, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening policy, wherein the preset screening policy is used to determine a tag elimination rule that matches a preset hierarchical tagging method; and the sorting result is obtained by sorting multiple tags included in the original link tracking information according to the preset hierarchical tagging method, wherein the preset hierarchical tagging method is used to determine a tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; and Step S83, displaying the target link tracking information in a graphical user interface. According to the above method steps, a visualization solution for link tracking information processing is provided. A terminal device provides a graphical user interface (GUI) that displays at least one link tracking information processing scenario. The GUI also includes an input component (e.g., a text input box, a voice input control, etc.) and a display component (e.g., a text display window, a table display window, etc.). A user enters a link tracking filtering dialog request through the input component to specify the original link tracking information in the link tracking information processing task. After detecting the user's input, the link tracking information processing process is executed based on the original link tracking information to obtain the target link tracking information. Furthermore, a link tracking filtering dialog response is generated based on the target link tracking information, returned to the user, and the target calculation result is displayed through the display component within the GUI. The request message can be an API request message in a predefined application scenario.The aforementioned predefined application scenarios involve distributed system link tracing. For example, these predefined application scenarios may include, but are not limited to, scenarios providing API call services in fields such as e-commerce, education, healthcare, conferences, social networks, financial products, logistics, and navigation. Accordingly, the aforementioned tag information processing method is used to provide link tracing information processing services for these predefined application scenarios, thereby improving the performance of the link tracing system in these predefined application scenarios. This embodiment of the present application expands upon the related art's free tagging scheme by extending the length and content of the identification field of the request message. This allows the original link tracing information obtained by tagging the request message to not only distinguish the request message but also to tag the call characteristics of the request message. These call characteristics include features from multiple dimensions, such as the call source, caller, and call entry point. The original link tracing information includes multiple tags, which may be the result of tagging the request message by multiple applications in the call link corresponding to the request message. Under the predefined hierarchical tagging method in this embodiment of the present application, each of the multiple tags is prioritized and the tag classification level to which each tag belongs is determined. Multiple preset sorting priorities correspond to multiple tag classification levels. Furthermore, based on the sorting priorities, the multiple tags are sorted to obtain a sorting result, in which the multiple tags are arranged in ascending or descending order of priority. According to the above-described method steps of the embodiment of the present application, the sorting result is filtered under a preset filtering strategy to discard some tags in the original link tracking information to obtain the target link tracking information. The above-described filtering strategy matches the preset hierarchical tagging method. For example, the above-described filtering strategy is used to determine some tags to be discarded from the multiple tags based on the tag classification level to which each tag belongs. For example, tags in the tag classification level corresponding to a lower sorting priority are preferentially determined as some tags to be discarded.In an embodiment of the present application, a currently input link tracking screening dialogue request is obtained, wherein the request data carried in the link tracking screening request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; in response to the link tracking screening dialogue request, a link tracking screening dialogue reply is returned, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening strategy, the preset screening strategy is used to determine a mark elimination rule that matches a preset hierarchical marking method, and the sorting result is obtained by sorting multiple marks included in the original link tracking information according to the preset hierarchical marking method, the preset hierarchical marking method is used to determine a marking classification level to which each mark among the multiple marks belongs, and different marking classification levels correspond to different sorting priorities; and the target link tracking information is displayed in a graphical user interface. Thus, the present application achieves the goal of sorting and filtering multiple tags in link tracking information based on a preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging during link tracking and improving system security. This further solves the technical problem of using a free tagging method during link tracking, which leads to bloated requests, heavy system burden, and high risk. It should be noted that the preferred implementation of this embodiment can be found in the relevant descriptions of Example 1 or Example 2 and will not be repeated here. Example 4 According to the embodiments of the present application, an embodiment of a device configured to implement the above-mentioned tag information processing method is also provided. 9 is a schematic structural diagram of a tag information processing device according to Example 4 of the present application. As shown in FIG9 , the device includes: an acquisition module 901, configured to acquire original link tracking information corresponding to a request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; a sorting module 902, configured to sort the multiple tags contained in the original link tracking information according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; a screening module 903, configured to screen the sorting result based on a preset screening strategy to obtain target link tracking information, wherein the preset screening strategy is used to determine a tag elimination rule that matches the preset hierarchical tagging method.Optionally, in addition to all of the above modules, the tag information processing device further includes: a tagging module 904 (not shown), configured to tag the request message to obtain multiple tags, wherein the multiple tags include: a tag type field, a tag key field, and a tag value field, wherein the tag type field, tag key field, and tag value field are added according to the operation specifications corresponding to the preset hierarchical tagging method; and to generate original link tracking information based on the multiple tags. Optionally, the sorting module 902 is further configured to: identify the tag classification level corresponding to the tag type field according to the preset hierarchical tagging method; sort the multiple tags based on the tag classification level to obtain a sorting result. Optionally, the sorting module 902 is further configured to: parse the multiple tags to obtain a tag key field and a tag type field corresponding to the tag key field; and identify the tag type field according to the preset hierarchical tagging method to obtain the tag classification levels corresponding to the multiple tags. Optionally, the sorting module 902 is further configured to: sort the multiple tags from high to low according to sorting priority based on the tag classification level to obtain a sorting result. Specifically, when some of the multiple tags have the same sorting priority, the tags are sorted according to the length of the tag value field corresponding to the tags. Optionally, the preset filtering strategy includes a fixed filtering strategy and a custom filtering strategy. The filtering module 903 is further configured to: perform an initial screening of the sorting result based on the fixed filtering strategy to obtain a preliminary screening result, wherein the fixed filtering strategy is a universal filtering strategy for all request messages; and perform a secondary screening of the preliminary screening result based on the custom filtering strategy to obtain target link tracking information, wherein the custom filtering strategy is a personalized customized filtering strategy corresponding to the request message. Optionally, the filtering module 903 is further configured to: perform a secondary screening of the preliminary screening result based on an upper limit on the number of tag keys corresponding to the tag key field to obtain target link tracking information; or perform a secondary screening of the preliminary screening result based on an upper limit on the tag value length corresponding to the tag value field to obtain target link tracking information. Optionally, in addition to all the above modules, the marking information processing device further includes: an inspection module 905 (not shown in the figure), which is configured to set multiple checkpoints, wherein the multiple checkpoints are used to mark and intercept the request message during the transmission process of the request message to filter and obtain the target link tracking information.Optionally, in addition to all of the aforementioned modules, the tag information processing apparatus further includes: a statistics module 906 (not shown in the figure), configured to obtain multiple statistical values ​​at multiple checkpoints. The multiple statistical values ​​include: the total number of requests passed through multiple channel entries and the number of requests passed with preset tags, and the total number of requests passed through a single channel entry and the number of requests passed with preset tags at the multiple checkpoints; an effective tagging evaluation of the multiple channel entries based on the total number of requests passed through the multiple channel entries and the number of requests passed with preset tags; and an effective tagging evaluation of the single channel entry based on the total number of requests passed through the single channel entry and the number of requests passed with preset tags. Optionally, in addition to all of the aforementioned modules, the tag information processing apparatus further includes: a synchronization module 907 (not shown in the figure), configured to synchronize the transmission of target link tracking information retained after screening during the transmission of request messages, and to stop the transmission of filtered out information. It should be noted that the acquisition module 901, sorting module 902, and screening module 903 correspond to steps S31 to S33 in Example 1. The examples and application scenarios implemented by these three modules and the corresponding steps are the same, but are not limited to the contents disclosed in Example 1. It should be noted that the above modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, 102n). The above modules may also be part of an apparatus and run in the computer terminal 10 provided in Example 1. In an embodiment of the present application, an acquisition module is used to obtain original link tracking information corresponding to a request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; a sorting module is used to sort multiple tags contained in the original link tracking information according to a preset hierarchical marking method to obtain a sorting result, wherein the preset hierarchical marking method is used to determine the marking classification level to which each of the multiple tags belongs, and different marking classification levels correspond to different sorting priorities; a screening module is used to screen the sorting result based on a preset screening strategy to obtain target link tracking information, wherein the preset screening strategy is used to determine a tag elimination rule that matches the preset hierarchical marking method.Thus, the present application achieves the goal of sorting and filtering multiple tags in link tracking information based on a preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging during link tracking and improving system security. This further solves the technical problem of using a free tagging method during link tracking, which leads to bloated requests, heavy system burden, and high risk. Furthermore, according to an embodiment of the present application, another device embodiment is provided, configured to implement the tag information processing method of the aforementioned embodiment 2. FIG10 is a schematic structural diagram of another tag information processing device according to Example 4 of the present application. As shown in FIG10 , the device includes: an acquisition module 1001, configured to acquire a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; and a response module 1002, configured to return a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening strategy, wherein the preset screening strategy is used to determine a tag elimination rule that matches a preset hierarchical tagging method, and the sorting result is obtained by sorting multiple tags included in the original link tracking information according to the preset hierarchical tagging method, wherein the preset hierarchical tagging method is used to determine a tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities. It should be noted that the acquisition module 1001 and response module 1002 correspond to steps S71 to S72 in Example 2. The examples and application scenarios implemented by these two modules and the corresponding steps are the same, but are not limited to the content disclosed in Example 2. It should be noted that the above modules or units may be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, ..., 102n). The above modules may also be part of a device that can run in the computer terminal 10 provided in Example 1. According to an embodiment of the present application, another embodiment of a device configured to implement the tag information processing method of Example 3 is also provided.FIG11 is a schematic structural diagram of another tag information processing device according to Embodiment 4 of the present application. As shown in FIG11 , the device includes: an acquisition module 1101 configured to acquire a currently input link tracing screening dialogue request, wherein the request data carried in the link tracing screening request includes: original link tracing information, which is used to distinguish the request message and mark the call characteristics of the request message; a return module 1102 configured to return a link tracing screening dialogue reply in response to the link tracing screening dialogue request, wherein the information carried in the link tracing screening dialogue reply includes: target link tracing information, which is obtained by filtering a sorting result based on a preset screening strategy, wherein the preset screening strategy is used to determine a tag elimination rule that matches a preset hierarchical tagging method; the sorting result is obtained by sorting multiple tags contained in the original link tracing information according to the preset hierarchical tagging method, wherein the preset hierarchical tagging method is used to determine a tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; and a presentation module 1103. It is configured to display target link tracking information within a graphical user interface. It should be noted that the acquisition module 1101, return module 1102, and display module 1103 correspond to steps S81 to S83 in Example 3. The examples and application scenarios implemented by these three modules and the corresponding steps are the same, but are not limited to the content disclosed in Example 3. It should be noted that the above modules or units can be hardware components or software components stored in a memory (e.g., memory 104) and processed by one or more processors (e.g., processors 102a, 102b, 102n). The above modules can also be part of an apparatus and run in the computer terminal 10 provided in Example 1. It should be noted that the preferred implementation of this embodiment can be found in the relevant descriptions of Example 1, Example 2, or Example 3 and will not be repeated here. Example 5 According to an embodiment of the present application, an electronic device is also provided. This electronic device can be any terminal device in a computer terminal group. Optionally, in this embodiment, the above electronic device can also be replaced with a terminal device such as a mobile terminal. Optionally, in this embodiment, the electronic device may be located in at least one network device among multiple network devices of a computer network.In this embodiment, the electronic device may execute the program code for the following steps in the tag information processing method: obtaining original link tracking information corresponding to the request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; sorting multiple tags contained in the original link tracking information according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; filtering the sorting result based on a preset filtering strategy to obtain target link tracking information, wherein the preset filtering strategy is used to determine a tag elimination rule that matches the preset hierarchical tagging method. Optionally, FIG12 is a block diagram of an electronic device according to Embodiment 5 of the present application. As shown in FIG12 , the electronic device 120 may include: one or more (only one is shown in the figure) processors 1202, a memory 1204, a storage controller 1206, and a peripheral interface 1208, wherein the peripheral interface 1208 is connected to a radio frequency module, an audio module, and a display. Memory 1204 may be configured to store software programs and modules, such as program instructions / modules corresponding to the tag information processing method and apparatus in the embodiments of the present application. The processor executes the software programs and modules stored in the memory to perform various functional applications and data processing, thereby implementing the aforementioned tag information processing method. Memory 1204 may include high-speed random access memory (RAM) and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some examples, memory 1204 may further include memory remotely located from the processor, and such remote memory may be connected to electronic device 120 via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof. The processor 1202 can call the information and application stored in the memory through the transmission device to perform the following steps: obtain the original link tracking information corresponding to the request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; sort the multiple tags contained in the original link tracking information according to the preset hierarchical labeling method to obtain the sorting result, wherein the preset hierarchical labeling method is used to determine the labeling classification level to which each tag in the multiple tags belongs, and different labeling classification levels correspond to different sorting priorities; based on the preset screening strategy, filter the sorting result to obtain the target link tracking information, wherein the preset screening strategy is used to determine the tag elimination rule that matches the preset hierarchical labeling method.Optionally, the processor 1202 may further execute program code for the following steps: tagging the request message to obtain multiple tags, wherein the multiple tags include a tag type field, a tag key field, and a tag value field, and the tag type field, the tag key field, and the tag value field are all added according to the operating specifications corresponding to the preset hierarchical tagging method. Optionally, the processor 1202 may further execute program code for the following steps: identifying the tag classification level corresponding to the tag type field according to the preset hierarchical tagging method; sorting the multiple tags based on the tag classification level to obtain a sorting result. Optionally, the processor 1202 may further execute program code for the following steps: parsing the multiple tags to obtain a tag key field and a tag type field corresponding to the tag key field; and identifying the tag type field according to the preset hierarchical tagging method to obtain the tag classification levels corresponding to the multiple tags. Optionally, the processor 1202 may further execute program code for the following steps: based on the tag classification level, sort the multiple tags from high to low according to sorting priority to obtain a sorting result, wherein, when some of the multiple tags have the same sorting priority, sort the tags according to the length of the tag value field corresponding to the tags. Optionally, the processor 1202 may further execute program code for the following steps: the preset filtering strategy includes: a fixed filtering strategy and a custom filtering strategy; based on the fixed filtering strategy, initially filtering the sorting result to obtain a preliminary filtering result, wherein the fixed filtering strategy is a universal filtering strategy for all request messages; and based on the custom filtering strategy, re-filtering the preliminary filtering result to obtain target link tracking information, wherein the custom filtering strategy is a personalized customized filtering strategy corresponding to the request message. Optionally, the processor 1202 may further execute program code for the following steps: re-screening the initial screening results based on the upper limit of the number of tag keys corresponding to the tag key field to obtain target link tracking information; or re-screening the initial screening results based on the upper limit of the tag value length corresponding to the tag value field to obtain target link tracking information. Optionally, the processor 1202 may further execute program code for the following steps: setting multiple checkpoints, wherein the multiple checkpoints are used to tag and intercept the request message during transmission to filter and obtain target link tracking information.Optionally, the processor 1202 may further execute program code for the following steps: obtaining multiple statistical values ​​at multiple checkpoints, where the multiple statistical values ​​include: the total number of requests passed through multiple channel entries and the number of requests passed with preset tags, and the total number of requests passed through a single channel entry and the number of requests passed with preset tags at the multiple checkpoints; performing an effective tagging evaluation on the multiple channel entries based on the total number of requests passed through the multiple channel entries and the number of requests passed with preset tags, and performing an effective tagging evaluation on the single channel entry based on the total number of requests passed through the single channel entry and the number of requests passed with preset tags. Optionally, the processor 1202 may further execute program code for the following steps: synchronously transmitting target link tracking information retained after screening during request message transmission, and ceasing transmission of filtered eliminated information. The processor 1202 can call the information and application stored in the memory through the transmission device to perform the following steps: obtain a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; return a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, the target link tracking information is obtained by filtering the sorting result based on a preset screening strategy, the preset screening strategy is used to determine the tag elimination rule that matches the preset hierarchical tagging method, the sorting result is obtained by sorting multiple tags contained in the original link tracking information according to the preset hierarchical tagging method, the preset hierarchical tagging method is used to determine the tag classification level to which each tag in the multiple tags belongs, and different tag classification levels correspond to different sorting priorities.The processor 1202 can call information and applications stored in the memory through a transmission device to perform the following steps: obtaining a currently input link tracking screening dialogue request, wherein the request data carried in the link tracking screening dialogue request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening dialogue reply in response to the link tracking screening dialogue request, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening policy, the preset screening policy is used to determine a mark elimination rule that matches a preset hierarchical marking method, and the sorting result is obtained by sorting multiple marks included in the original link tracking information according to the preset hierarchical marking method, the preset hierarchical marking method is used to determine the marking classification level to which each of the multiple marks belongs, and different marking classification levels correspond to different sorting priorities; and displaying the target link tracking information in a graphical user interface. According to an embodiment of the present application, an electronic device configured to implement the above-mentioned marking information processing method is provided. The original link tracking information corresponding to the request message is obtained, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; multiple tags contained in the original link tracking information are sorted according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; the sorting result is filtered based on a preset filtering strategy to obtain target link tracking information, wherein the preset filtering strategy is used to determine the tag elimination rules that match the preset hierarchical tagging method. As a result, the present application achieves the purpose of sorting and filtering multiple tags in the link tracking information based on the preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging in link tracking and improving system security, thereby solving the technical problem that the use of free tagging in the link tracking process leads to bloated requests, heavy system burden, and high risk. Those skilled in the art will appreciate that the structure shown in FIG12 is merely illustrative, and the electronic device may also be a terminal device such as a smartphone (e.g., an Android phone, an iOS phone, etc.), a tablet computer, a PDA, or a mobile internet device (MID). FIG12 does not limit the structure of the aforementioned electronic devices.For example, the electronic device 120 may include more or fewer components (such as a network interface, a display device, etc.) than those shown in FIG12 , or may have a configuration different from that shown in FIG12 . Those skilled in the art will appreciate that all or part of the steps in the various methods of the above embodiments can be completed by a program instructing the hardware associated with the terminal device. The program can be stored in a computer-readable storage medium, which may include a flash drive, ROM, RAM, a magnetic disk, or an optical disk. Example 6: According to an embodiment of the present application, a computer-readable storage medium is also provided. Optionally, in this embodiment, the storage medium may be configured to store program code executed by the tag information processing method provided in Example 1, Example 2, or Example 3. Optionally, in this embodiment, the storage medium may be located in any computer terminal in a computer terminal group in a computer network, or in any mobile terminal in a mobile terminal group. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: obtaining original link tracking information corresponding to the request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; sorting multiple tags contained in the original link tracking information according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, and different tag classification levels correspond to different sorting priorities; filtering the sorting result based on a preset filtering strategy to obtain target link tracking information, wherein the preset filtering strategy is used to determine a tag elimination rule that matches the preset hierarchical tagging method. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: tagging the request message to obtain multiple tags, wherein the multiple tags include: a tag type field, a tag key field, and a tag value field, and the tag type field, tag key field, and tag value field are all added according to the operation specification corresponding to the preset hierarchical tagging method. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: identifying a tag classification level corresponding to a tag type field according to a preset hierarchical tagging method; and sorting multiple tags based on the tag classification levels to obtain a sorting result. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: parsing multiple tags to obtain a tag key field and a tag type field corresponding to the tag key field; and identifying the tag type field according to a preset hierarchical tagging method to obtain tag classification levels corresponding to the multiple tags.Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: sorting multiple tags from high to low according to sorting priority based on the tag classification level to obtain a sorting result, wherein, when some of the multiple tags have the same sorting priority, sorting is performed based on the length of the tag value field corresponding to the tags. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: the preset filtering policy includes: a fixed filtering policy and a custom filtering policy; performing an initial screening on the sorting result based on the fixed filtering policy to obtain a preliminary screening result, wherein the fixed filtering policy is a universal filtering policy for all request messages; and performing a secondary screening on the preliminary screening result based on the custom filtering policy to obtain target link tracking information, wherein the custom filtering policy is a personalized customized filtering policy corresponding to the request message. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: re-screening the initial screening results based on the upper limit of the number of tag keys corresponding to the tag key field to obtain target link tracking information; or re-screening the initial screening results based on the upper limit of the tag value length corresponding to the tag value field to obtain target link tracking information. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: setting multiple checkpoints, wherein the multiple checkpoints are used to tag and intercept request messages during transmission of the request messages to obtain target link tracking information. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: obtaining multiple statistical values ​​at multiple checkpoints, wherein the multiple statistical values ​​include: the total number of requests passed through multiple channel entries and the number of requests passed with preset tags, and the total number of requests passed through a single channel entry and the number of requests passed with preset tags at the multiple checkpoints; performing an effective tagging evaluation on the multiple channel entries based on the total number of requests passed through the multiple channel entries and the number of requests passed with preset tags, and performing an effective tagging evaluation on the single channel entry based on the total number of requests passed through the single channel entry and the number of requests passed with preset tags. Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: synchronously transmitting target link tracking information retained after screening during request message transmission, and ceasing to transmit filtered eliminated information.Optionally, in this embodiment, the computer-readable storage medium is configured to store program code for executing the following steps: obtaining a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, the target link tracking information is obtained by filtering a sorting result based on a preset screening strategy, the preset screening strategy is used to determine a mark elimination rule that matches a preset hierarchical marking method, the sorting result is obtained by sorting multiple marks included in the original link tracking information according to the preset hierarchical marking method, the preset hierarchical marking method is used to determine a marking classification level to which each of the multiple marks belongs, and different marking classification levels correspond to different sorting priorities. Optionally, in this embodiment, a computer-readable storage medium is configured to store program code for executing the following steps: obtaining a currently input link tracking screening dialogue request, wherein the request data carried in the link tracking screening request includes: original link tracking information, which is used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening dialogue reply in response to the link tracking screening dialogue request, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, which is obtained by filtering a sorting result based on a preset screening policy, wherein the preset screening policy is used to determine a mark elimination rule that matches a preset hierarchical marking method; and the sorting result is obtained by sorting multiple marks contained in the original link tracking information according to the preset hierarchical marking method, wherein the preset hierarchical marking method is used to determine a marking classification level to which each of the multiple marks belongs, wherein different marking classification levels correspond to different sorting priorities; and displaying the target link tracking information in a graphical user interface. According to an embodiment of the present application, a computer-readable storage medium configured to implement the above-described marking information processing method is provided.The original link tracking information corresponding to the request message is obtained, where the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; multiple tags contained in the original link tracking information are sorted according to a preset hierarchical tagging method to obtain a sorting result, where the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, with different tag classification levels corresponding to different sorting priorities; the sorting result is filtered based on a preset filtering strategy to obtain target link tracking information, where the preset filtering strategy is used to determine a tag elimination rule that matches the preset hierarchical tagging method. Thus, the present application achieves the purpose of sorting and filtering multiple tags in the link tracking information based on the preset hierarchical tagging method and filtering strategy, thereby achieving the technical effect of reducing the system burden caused by tagging in link tracking and improving system security, thereby solving the technical problem that the use of a free tagging method in the link tracking process leads to bloated requests, heavy system burden, and high risk. According to embodiments of the present application, a computer program product is also provided. Optionally, in this embodiment, the computer program product may provide a tag information processing service based on the tag information processing method provided in Embodiment 1, Embodiment 2, or Embodiment 3. Optionally, in this embodiment, the computer program product may be a set of instructions and codes pre-written based on the tag information processing method. The computer program product may run on various computer platforms, including personal computers, servers, mobile devices, and the like. Optionally, in this embodiment, the instructions and codes corresponding to the computer program product are used to implement the following method steps: obtaining original link tracking information corresponding to a request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; sorting multiple tags contained in the original link tracking information according to a preset hierarchical tagging method to obtain a sorting result, wherein the preset hierarchical tagging method is used to determine the tag classification level to which each of the multiple tags belongs, with different tag classification levels corresponding to different sorting priorities; and filtering the sorting result based on a preset screening policy to obtain target link tracking information, wherein the preset screening policy is used to determine a tag elimination rule that matches the preset hierarchical tagging method.The computer program product described above can provide tag information processing services in application scenarios involving link tracing information processing in a distributed system. This achieves the goal of sorting and filtering multiple tags in link tracing information based on a preset hierarchical tagging method and filtering strategy, thereby reducing the system burden caused by tagging in link tracing and improving system security. This further addresses the technical problem of using a free tagging method in link tracing, which leads to bloated requests, high system burden, and high risk. The serial numbers of the above-mentioned embodiments of this application are for illustrative purposes only and do not represent the advantages or disadvantages of the embodiments. In the above-mentioned embodiments of this application, the description of each embodiment has its own emphasis. For portions not detailed in a particular embodiment, reference should be made to the relevant descriptions of other embodiments. In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of the units described is merely a logical functional division. In actual implementation, other divisions may be used. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not implemented. Furthermore, the coupling, direct coupling, or communication connection shown or discussed may be through interfaces, indirect coupling, or communication connection between units or modules, and may be electrical or otherwise. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the objectives of the present embodiment as needed. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, each unit may exist physically separately, or two or more units may be integrated into a single unit. These integrated units may be implemented in either hardware or software functional units. If these integrated units are implemented as software functional units and sold or used as independent products, they may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a number of instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the method described in each embodiment of the present application.The aforementioned storage media include various media capable of storing program code, such as USB flash drives, ROM, RAM, mobile hard drives, magnetic disks, or optical disks. The above description is merely a preferred embodiment of the present application. It should be noted that those skilled in the art may make various improvements and modifications without departing from the principles of the present application, and such improvements and modifications should also be considered within the scope of protection of the present application.

Claims

Claims 1. A method for processing label information, wherein: include: Obtain original link tracking information corresponding to the request message, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; sort the multiple tags contained in the original link tracking information according to a preset hierarchical labeling method to obtain a sorting result, wherein the preset hierarchical labeling method is used to determine the labeling classification level to which each of the multiple tags belongs, and different labeling classification levels correspond to different sorting priorities; filter the sorting result based on a preset screening strategy to obtain target link tracking information, wherein the preset screening strategy is used to determine a tag elimination rule that matches the preset hierarchical labeling method.

2. The tag information processing method according to claim 1, further comprising: The request message is labeled to obtain the multiple tags, wherein the multiple tags include: a tag type field, a tag key field, and a tag value field, and the tag type field, the tag key field, and the tag value field are all added according to the operation specification corresponding to the preset hierarchical tagging method; and the original link tracking information is generated based on the multiple tags.

3. The tag information processing method according to claim 2, wherein the steps of sorting the multiple tags included in the original link tracking information according to the preset hierarchical tagging method to obtain the sorting result include: Identify the marking classification level corresponding to the marking type field according to the preset hierarchical marking method; The multiple tags are sorted based on the tag classification level to obtain the sorting result.

4. The marking information processing method according to claim 3, wherein identifying the marking classification level corresponding to the marking type field according to the preset hierarchical marking method comprises: Parsing the multiple tags to obtain the marking key field and the marking type field corresponding to the marking key field; The marking type field is identified according to the preset hierarchical marking method to obtain marking classification levels corresponding to the multiple marks.

5. The tag information processing method according to claim 3, wherein sorting the multiple tags based on the tag classification level to obtain the sorting result comprises: Based on the marking classification level, the multiple marks are sorted from high to low according to the sorting priority, 27 The sorting result is obtained, wherein, when the sorting priorities of some of the multiple tags are the same, the tags are sorted according to the lengths of the marking value fields corresponding to the some of the tags.

6. The tag information processing method according to claim 1, wherein the preset screening strategy comprises: Fixed screening strategy and custom screening strategy, based on the preset screening strategy, the sorting results are screened to obtain the target link tracking information, including: based on the fixed screening strategy, the sorting results are initially screened to obtain the primary screening results, wherein the fixed screening strategy is a screening strategy common to all request messages; based on the custom screening strategy, the primary screening results are re-screened to obtain the target link tracking information, wherein the custom screening strategy is a personalized customized screening strategy corresponding to the request message.

7. The tag information processing method according to claim 6, wherein the step of re-screening the initial screening result based on the custom screening strategy to obtain the target link tracking information comprises: Based on the upper limit of the number of marking keys corresponding to the marking key field, the initial screening result is screened again to obtain the target link tracking information; Alternatively, based on the upper limit of the length of the tag value corresponding to the tag value field, the initial screening result is screened again to obtain the target link tracking information.

8. The tag information processing method according to claim 1, further comprising: A plurality of checkpoints are set, wherein the plurality of checkpoints are used to mark and intercept the request message during the transmission process of the request message, so as to filter and obtain the target link tracking information.

9. The tag information processing method according to claim 8, further comprising: A plurality of statistical values are obtained at the plurality of checkpoints, wherein the plurality of statistical values include: a total number of requests passed through the multi-channel entry and a number of requests with preset tags passed through, and a total number of requests passed through the single-channel entry and a number of requests with the preset tags passed through, at the plurality of checkpoints; an effective tagging evaluation is performed on the multi-channel entry based on the total number of requests passed through the multi-channel entry and the number of requests with the preset tags passed through, and an effective tagging evaluation is performed on the single-channel entry based on the total number of requests passed through the single-channel entry and the number of requests with the preset tags passed through.

10. The tag information processing method according to claim 8, further comprising: During the transmission of the request message, the target link tracking information retained after screening is synchronously transmitted, and the transmission of the eliminated information after screening is stopped.

11. A method for processing label information, wherein: The method includes: obtaining a link tracking screening request through a first application programming interface, wherein the request data carried in the link tracking screening request includes: original link tracking information, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; returning a link tracking screening response through a second application programming interface, wherein the response data carried in the link tracking screening response includes: target link tracking information, wherein the target link tracking information is obtained by filtering a sorting result based on a preset screening strategy, wherein the preset screening strategy is used to determine a mark elimination rule that matches the preset hierarchical marking method, and the sorting result is obtained by sorting multiple marks included in the original link tracking information according to a preset hierarchical marking method, wherein the preset hierarchical marking method is used to determine a marking classification level to which each mark in the multiple marks belongs, and different marking classification levels correspond to different sorting priorities.

12. A method for processing label information, wherein: include: Obtain a currently input link tracking screening dialogue request, wherein the request data carried in the link tracking screening request includes: original link tracking information, wherein the original link tracking information is used to distinguish the request message and mark the call characteristics of the request message; in response to the link tracking screening dialogue request, return a link tracking screening dialogue reply, wherein the information carried in the link tracking screening dialogue reply includes: target link tracking information, wherein the target link tracking information is obtained by filtering a sorting result based on a preset screening strategy, wherein the preset screening strategy is used to determine a mark elimination rule that matches the preset hierarchical marking method, wherein the sorting result is obtained by sorting multiple marks included in the original link tracking information according to a preset hierarchical marking method, wherein the preset hierarchical marking method is used to determine a marking classification level to which each mark in the multiple marks belongs, and different marking classification levels correspond to different sorting priorities; and display the target link tracking information in a graphical user interface.

13. An electronic device, wherein: include: a memory storing an executable program; A processor is configured to run the program, wherein the program executes the marking information processing method according to any one of claims 1 to 12 when running.

14. A computer-readable storage medium, wherein: The computer-readable storage medium includes a stored executable program, wherein when the executable program is run, the device where the computer-readable storage medium is located is controlled to execute the marking information processing method according to any one of claims 1 to 12.

15. A computer program product, wherein: The present invention comprises a computer program, wherein when the computer program is executed by a processor, the marking information processing method according to any one of claims 1 to 12 is implemented.

Images