Label-based management method and device

Abstract

The invention relates to the technical field of label management, and discloses a method and device based on label management, and the method comprises the steps: obtaining label demand information, and generating at least one first label corresponding to the label demand information based on the label demand information; in response to the first operation instruction, classifying the first tag to a first directory level corresponding to the first tag, and updating the database; when the scene demand information is obtained, determining a second directory hierarchy according to the scene demand information and the database, and determining a target user corresponding to the second directory hierarchy according to the second directory hierarchy; and sending a service corresponding to the scene demand information to a terminal of the target user.

Description

Technical Field

[0001] The present invention relates to the technical field of tag management, and in particular to a method and device based on tag management. Background Art

[0002] In related technologies, accurate user tagging and classification relies on administrators manually updating user tags in the database. The specific process involves analyzing changes in user behavior data to identify user groups whose tags need updating. Based on the analysis results, the administrator manually modifies or adds corresponding tag records in the database. Finally, the administrator ensures that the tag information in the database is up to date, allowing the service platform to match requests based on the latest user tags.

[0003] However, the process of administrators manually updating the database is time-consuming and error-prone, especially when there are a large number of users and a complex tag system. The update efficiency is extremely low, making it difficult to meet real-time or near real-time demand matching requirements, thereby reducing the efficiency of tag management.

[0004] Therefore, how to improve the efficiency of tag management has become a technical problem that needs to be solved. Summary of the Invention

[0005] In view of this, the present invention provides a method and apparatus based on tag management.

[0006] In a first aspect, the present invention provides a method based on tag management, the method comprising: obtaining tag requirement information, and based on the tag requirement information, generating at least one first tag corresponding to the tag requirement information; in response to a first operation instruction, classifying the first tag to a first directory level corresponding to the first tag, and updating the database; when scene requirement information is obtained, determining a second directory level according to the scene requirement information and the database, and determining a target user corresponding to the second directory level according to the second directory level; and sending the service corresponding to the scene requirement information to the terminal of the target user.

[0007] The tag management method provided in this embodiment obtains tag requirement information and, based on the tag requirement information, generates at least one first tag corresponding to the tag requirement information through an automated process. This process can dynamically generate tags based on the tag requirement information, avoiding the tedious and error-prone manual creation of tags. Simultaneously, the first tag is classified into the first directory level corresponding to the first tag, and the database is updated, thereby achieving automatic tag classification and automatic database updating, greatly improving the efficiency and accuracy of tag management.

[0008] In a possible implementation, the method further includes: configuring a tag type for the first tag in response to the second operation instruction; and classifying the tag type corresponding to the first tag into a directory level corresponding to the first tag.

[0009] The tag management method provided in this embodiment enables users to search, manage and maintain tags more conveniently by configuring the tag type for the first tag and classifying the tag type corresponding to the first tag into the directory level corresponding to the first tag, thereby improving the system's usability and operating experience.

[0010] In one possible implementation, in response to a first operating instruction, the first tag is classified into a first directory level corresponding to the first tag, and the database is updated, including: verifying the first tag to obtain a verification result; when the verification result indicates that the first tag is qualified, in response to the first operating instruction, the first tag is classified into a first directory level corresponding to the first tag, and the database is updated.

[0011] The tag management method provided in this embodiment verifies the first tag to obtain a verification result; when the verification result indicates that the first tag is qualified, it can be applied to the production environment, thereby effectively ensuring the consistency and accuracy of the tag in various environments and ensuring the smooth progress of the business process.

[0012] In one possible implementation, when scenario requirement information is obtained, the second directory level is determined based on the scenario requirement information and the database, including: determining at least one second tag corresponding to the scenario requirement information based on the scenario requirement information; and traversing the first directory level of each target user in the database based on the second tag to determine the second directory level including all second tags.

[0013] The tag management method provided in this embodiment can accurately locate the second directory level including all second tags directly from the database through the second tag corresponding to the scenario requirement information, thereby accurately determining the target users who can execute the service.

[0014] In one possible implementation, obtaining the label requirement information includes: in response to a third operation instruction, obtaining the business line type and the label, and determining the business line type and the label as the label requirement information.

[0015] The tag management method provided in this embodiment can achieve refined management of different business lines by clearly obtaining business line types and tags, ensuring that the specific needs of each business line are fully met without interfering with each other.

[0016] In the second aspect, the present invention provides a device based on label management, which includes: an acquisition module for acquiring label requirement information, and generating at least one first label corresponding to the label requirement information based on the label requirement information; a first classification module for classifying the first label to the first directory level corresponding to the first label in response to a first operation instruction, and updating the database; a determination module for determining the second directory level according to the scenario requirement information and the database when the scenario requirement information is acquired, and determining the target user corresponding to the second directory level according to the second directory level; a sending module for sending the service corresponding to the scenario requirement information to the terminal of the target user.

[0017] In one possible implementation, the apparatus further includes: a configuration module configured to configure a tag type for the first tag in response to a second operation instruction; and a second classification module configured to classify the tag type corresponding to the first tag into a directory level corresponding to the first tag.

[0018] In a third aspect, the present invention provides a computer device comprising: a memory and a processor, the memory and the processor being communicatively connected to each other, the memory storing computer instructions, and the processor executing the tag management method of the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0019] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the tag management method according to the first aspect or any corresponding embodiment thereof.

[0020] In a fifth aspect, the present invention provides a computer program product comprising computer instructions for causing a computer to execute the tag management method according to the first aspect or any corresponding embodiment thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] In order to more clearly illustrate the specific embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the specific embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0022] Figure 1 is a flowchart of a tag management method according to an embodiment of the present invention;

[0023] Figure 2 is a structural block diagram of a device based on tag management according to an embodiment of the present invention;

[0024] Figure 3 Schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0025] To make the purpose, technical solutions, and advantages of the embodiments of the present invention more clear, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without making creative efforts shall fall within the scope of protection of the present invention.

[0026] According to an embodiment of the present invention, a method embodiment based on tag management is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0027] In this embodiment, a tag-based management method is provided, which can be used for computer devices, such as computers, servers, etc. Figure 1 FIG. 1 is a flow chart of a tag management method according to an embodiment of the present invention. Figure 1 As shown, the process includes the following steps:

[0028] Step S101: Acquire tag requirement information, and generate at least one first tag corresponding to the tag requirement information based on the tag requirement information.

[0029] Tag requirement information can indicate the detailed tag requirements proposed by the user. This information can include basic tag information and behavior information. Basic tag information can include basic attributes such as the driver's age, gender, and ID. Behavior information can include order completion information, work time period information, and work hours information.

[0030] After obtaining the tag requirement information, at least one first tag corresponding to the tag requirement information is generated using preset rules and algorithms. The first tag may include basic tag information and tag behavior information, such as the driver's name and working hours.

[0031] As an example, a user may request labeling information, such as "five-star rated driver," "novice driver," or "nighttime active driver." The system generates corresponding first labels based on the labeling information.

[0032] Step S102 : In response to the first operation instruction, classify the first tag into a first directory level corresponding to the first tag, and update the database.

[0033] The first directory level may indicate a hierarchical structure for classifying and managing the first tag. There may be multiple target levels, and the first directory level may be any one of the multiple levels, for example, the first target level may be a secondary directory, a tertiary directory, etc., which may be selected by the user.

[0034] The first operation instruction may be an instruction to classify the first tag. The user may operate the system page by tapping the keyboard, clicking the mouse, etc. Accordingly, the computer device may classify the first tag into the first directory level corresponding to the first tag in response to the operation on the system page. At the same time, the database may be updated according to the updated first target level. The database may store all levels, and when a new tag is added to any level, the database may update the level in real time, i.e., add the tag to the level.

[0035] For example, after generating a "Five-Star Rating Driver" tag, the user can issue a first command through the system interface to categorize the tag into the "Service Quality" subdirectory under the first directory level of "Driver Management." The system responds to the command by updating the database and recording the tag's classification information.

[0036] Step S103: When the scenario requirement information is obtained, a second directory level is determined according to the scenario requirement information and the database, and a target user corresponding to the second directory level is determined according to the second directory level.

[0037] Scenario demand information can indicate demand information under a specific business scenario. For example, in the online car-hailing business, it may be order allocation demand during peak hours, vehicle scheduling demand in a specific area, etc. The second-level target can be a directory level determined based on the scenario demand information and database analysis, which is closely related to the scenario demand and is used to further locate the target user. When the system obtains scenario demand information, such as data analysis and business processing requirements under a specific business scenario. The system will analyze and determine the second directory level based on the scenario demand information and the existing data in the database. The second directory level may be divided based on factors such as business type, user group, time period, etc. Then, based on the determined second directory level, the target user corresponding to the level is further determined, that is, the user who has the authority or needs to handle the scenario demand.

[0038] For example, during holidays, an online ride-hailing platform receives demand information and needs to identify target users who work all day, have a positive review rate of over 90%, and a 100% order completion rate. Based on the demand information and the database, the system identifies a category that meets the criteria of working all day, having a positive review rate of over 90%, and a 100% order completion rate. The system then determines the target users for that category.

[0039] Step S104: Send the service corresponding to the scenario requirement information to the terminal of the target user.

[0040] The terminal is a device used by the target user to receive and process business data sent by the system, such as a computer, mobile phone, or tablet computer. The system sends business data, tasks, or notifications related to scenario requirements to the target user's terminal device through an appropriate communication method, so that the target user can obtain and process relevant business in a timely manner.

[0041] The tag management method provided in this embodiment obtains tag requirement information and, based on the tag requirement information, generates at least one first tag corresponding to the tag requirement information through an automated process. This process can dynamically generate tags based on the tag requirement information, avoiding the tedious and error-prone manual creation of tags. Simultaneously, the first tag is classified into the first directory level corresponding to the first tag, and the database is updated, thereby achieving automatic tag classification and automatic database updating, greatly improving the efficiency and accuracy of tag management.

[0042] In one possible implementation, the method further includes:

[0043] Step a1: In response to the second operation instruction, configure the tag type for the first tag.

[0044] The second operation instruction may be an instruction to configure the tag type of the first tag. The user may perform configuration operations on the system page by typing on the keyboard, clicking the mouse, or the like. Accordingly, the computer device may configure the tag type of the first tag in response to the configuration operation on the system page. The tag type may include a time type, an enumeration type, a numerical type, or the like.

[0045] The label type can be a more detailed classification description of the first label. For example, for the first label "order", the label types may include "real-time order", "pre-booked order", "long-distance order", "short-distance order", etc.; for "vehicle", the label types may include "new energy vehicle", "fuel vehicle", "luxury vehicle", "economy vehicle", etc.; for "driver", the label types may include "novice driver", "experienced driver", "five-star driver", etc.; for "passenger", the label types may include "ordinary passenger", "member passenger", "high-frequency passenger", etc.

[0046] In one possible implementation, users can customize the data type of a tag based on their specific needs, and set the corresponding input format and validation rules. This highly customizable design allows the tagging system to more accurately adapt to different business scenarios and ensure data accuracy and consistency.

[0047] Step a2: classify the tag type corresponding to the first tag into the directory level corresponding to the first tag.

[0048] After determining the tag type of the first tag, the tag type corresponding to the first tag may be classified into a directory level corresponding to the first tag.

[0049] As an example, tag types are automatically stored in the corresponding directory hierarchy based on pre-set rules and mapping relationships. For example, when the platform receives the "Real-time Order" tag type in the first tag of "Order", it will store the "Real-time Order" data in the database table corresponding to the "Business Object - Order Management - Order Type" directory hierarchy based on pre-set rules.

[0050] As an example, tag types such as "real-time order" and "scheduled order" should be classified under the "business object-order management-order type" directory level; if the order has statuses such as "completed", "in progress", and "cancelled", these tag types should be classified under the "business object-order management-order status" directory level.

[0051] In one possible implementation, step S102 includes:

[0052] Step b1: verify the first tag and obtain a verification result.

[0053] Verify the accuracy, completeness and compliance of the first label with business regulations.

[0054] As an example, a rules engine system can be built to pre-define the rules that various first tags should follow. Once a first tag is entered, the rules engine automatically checks it against these rules. For example, for the "Vehicle" first tag, the rules can be set to include key information such as the vehicle license plate number, vehicle type, and company, and the license plate number format must comply with specific specifications. The first tag is compared with existing reliable data sources or standard data templates. For example, for the "Driver" first tag, the entered driver information can be compared with the driver qualification database provided by the traffic management department to verify the accuracy of the driver's license information, professional qualification certificate information, etc. The rationality of the first tag is checked from a business logic perspective. For example, in the "Order" first tag, the pickup time must be before the drop-off time. If the pickup time is later than the drop-off time, the first tag is deemed illogical and the verification result is unsatisfactory.

[0055] As an example, depending on the type of first tag, corresponding verification rules can be formulated. For example, for the first tag "passenger", the verification rules may include whether the passenger's name is a real name (which can be verified through a real-name authentication system) and whether the contact number is a valid number (through number format checking and SMS verification, etc.).

[0056] Step b2: When the verification result indicates that the first tag is qualified, in response to the first operation instruction, the first tag is classified into the first directory level corresponding to the first tag, and the database is updated.

[0057] When the verification result indicates that the first tag is qualified, the above step S102 is executed. Please refer to the above step S102 for details, and no further details will be given here.

[0058] The tag management method provided in this embodiment verifies the first tag to obtain a verification result; when the verification result indicates that the first tag is qualified, it can be applied to the production environment, thereby effectively ensuring the consistency and accuracy of the tag in various environments and ensuring the smooth progress of the business process.

[0059] In one possible implementation, step S103 includes:

[0060] Step c1: determining at least one second tag corresponding to the scenario requirement information according to the scenario requirement information.

[0061] Scenario demand information can be information generated by the platform. Scenario demand information can indicate the content of the task being sent to the target user. For example, scenario demand information can include information about Area A and peak ride demand periods. Second tags corresponding to scenario demand information can include: Area A, Order Completion Rate Greater than 90%, Fast Order Completion Time, etc.

[0062] Step c2: traverse the first directory level of each target user in the database according to the second tag, and determine the second directory level including all the second tags.

[0063] After determining the second tag corresponding to the scenario requirement information, the database can be traversed based on the second tag to determine a second directory level that includes the second tag. For example, if the first directory level corresponding to user A includes the tags: Region A, Order Completion Rate Greater than 90%, and Fast Order Completion Time, then the first directory level can be determined to include all second tags and used as the second directory level.

[0064] The tag management method provided in this embodiment can accurately locate the second directory level including all second tags directly from the database through the second tag corresponding to the scenario requirement information, thereby accurately determining the target users who can execute the service.

[0065] In a possible implementation, step S101 includes: in response to a third operation instruction, obtaining a business line type and a label, and determining the business line type and the label as label requirement information.

[0066] In a multi-brand system, tags can be independently configured and published for each brand. For example, ride-hailing and chauffeur-driven services belong to two separate business lines. Tag management can meet their respective tagging requirements and enable independent configuration and management. By integrating different business line types and tags into tag requirement information through a third-party operation command, ride-hailing and chauffeur-driven services can be managed in a refined manner, ensuring that the specific needs of each brand are fully met without interfering with each other.

[0067] The tag management method provided in this embodiment can achieve refined management of different business lines by clearly obtaining business line types and tags, ensuring that the specific needs of each business line are fully met without interfering with each other.

[0068] In this embodiment, a tag management device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation methods. The details that have been described will not be repeated here. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, implementation in hardware, or a combination of software and hardware, is also possible and conceivable.

[0069] This embodiment provides a device based on tag management, such as Figure 2 As shown, it includes: an acquisition module 201, which is used to acquire label requirement information, and generate at least one first label corresponding to the label requirement information based on the label requirement information; a first classification module 202, which is used to classify the first label into the first directory level corresponding to the first label in response to the first operation instruction, and update the database; a determination module 203, which is used to determine the second directory level according to the scenario requirement information and the database when the scenario requirement information is acquired, and determine the target user corresponding to the second directory level according to the second directory level; a sending module 204, which is used to send the service corresponding to the scenario requirement information to the terminal of the target user.

[0070] In one possible implementation, the device further includes: a configuration module for configuring a tag type for the first tag in response to a second operation instruction; and a second classification module for classifying the tag type corresponding to the first tag into a directory level corresponding to the first tag.

[0071] The further functional description of each of the above modules and units is the same as that of the above corresponding embodiments and will not be repeated here.

[0072] The tag management-based device in this embodiment is presented in the form of a functional unit, where the functional unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0073] The embodiment of the present invention also provides a computer device having the above Figure 2 The device shown is based on tag management.

[0074] See also Figure 3 , Figure 3 is a structural diagram of a computer device provided by an optional embodiment of the present invention, such as Figure 3 As shown, the computer device includes: one or more processors 10, memory 20, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Equally, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 3 A processor 10 is taken as an example.

[0075] The processor 10 may be a central processing unit, a network processor, or a combination thereof. The processor 10 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit, a programmable logic device, or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable gate array, a general purpose array logic, or any combination thereof.

[0076] The memory 20 stores instructions that can be executed by at least one processor 10, so as to enable at least one processor 10 to execute the method shown in the above embodiment.

[0077] The memory 20 may include a program storage area and a data storage area, wherein the program storage area may store an operating system and application programs required for at least one function; the data storage area may store data created based on the use of the computer device, etc. In addition, the memory 20 may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some optional embodiments, the memory 20 may optionally include a memory remotely located relative to the processor 10, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0078] The memory 20 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid-state drive; the memory 20 may also include a combination of the above types of memory.

[0079] The computer device further includes an input device 30 and an output device 40. The processor 10, the memory 20, the input device 30 and the output device 40 may be connected via a bus or other means. Figure 3 The bus connection is taken as an example.

[0080] The input device 30 can receive input digital or character information and generate key signal input related to user settings and function control of the computer device, such as a touch screen, a keypad, a mouse, a trackpad, a touch pad, an indicator stick, one or more mouse buttons, a trackball, a joystick, etc. The output device 40 can include a display device, an auxiliary lighting device (e.g., an LED), and a tactile feedback device (e.g., a vibration motor). The above-mentioned display device includes but is not limited to a liquid crystal display, a light emitting diode, a display, and a plasma display. In some optional embodiments, the display device can be a touch screen.

[0081] The computer device further includes a communication interface for the computer device to communicate with other devices or a communication network.

[0082] The embodiment of the present invention also provides a computer-readable storage medium. The above-mentioned method according to the embodiment of the present invention can be implemented in hardware, firmware, or implemented as a computer code that can be recorded in a storage medium, or implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and downloaded through a network and will be stored in a local storage medium, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state drive, etc.; further, the storage medium can also include a combination of the above-mentioned types of memory. It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor or hardware, the method shown in the above embodiment is implemented.

[0083] A portion of the present invention may be applied as a computer program product, such as a computer program instruction, which, when executed by a computer, can call or provide the method and / or technical solution according to the present invention through the operation of the computer. Those skilled in the art should understand that the form in which the computer program instruction exists in a computer-readable medium includes, but is not limited to, a source file, an executable file, an installation package file, etc. Accordingly, the way in which the computer program instruction is executed by the computer includes, but is not limited to: the computer directly executes the instruction, or the computer compiles the instruction and then executes the corresponding compiled program, or the computer reads and executes the instruction, or the computer reads and installs the instruction and then executes the corresponding installed program. Here, the computer-readable medium may be any available computer-readable storage medium or communication medium that can be accessed by the computer.

[0084] Although the embodiments of the present invention have been described with reference to the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention. Such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A tag management method, characterized in that: The method comprises: Acquire label requirement information, and generate at least one first label corresponding to the label requirement information based on the label requirement information; In response to a first operation instruction, classify the first tag into a first directory level corresponding to the first tag, and update a database; When the scenario requirement information is obtained, determining a second directory level according to the scenario requirement information and the database, and determining a target user corresponding to the second directory level according to the second directory level; Send the service corresponding to the scenario requirement information to the target user's terminal.

2. The tag management method according to claim 1, characterized in that: The method further comprises: In response to a second operation instruction, configuring a tag type for the first tag; The tag type corresponding to the first tag is classified into the directory level corresponding to the first tag.

3. The tag management method according to claim 1, characterized in that: In response to a first operation instruction, classifying the first tag into a first directory level corresponding to the first tag and updating a database includes: Verifying the first tag to obtain a verification result; When the verification result indicates that the first tag is qualified, in response to a first operation instruction, the first tag is classified into a first directory level corresponding to the first tag, and a database is updated.

4. The tag management method according to claim 1, characterized in that: When the scenario requirement information is obtained, determining the second directory level according to the scenario requirement information and the database includes: Determining, according to the scenario requirement information, at least one second tag corresponding to the scenario requirement information; According to the second tag, the first directory level of each target user in the database is traversed to determine the second directory level including all the second tags.

5. The tag management method according to claim 1, characterized in that: The obtaining of label requirement information includes: In response to the third operation instruction, the business line type and the label are obtained, and the business line type and the label are determined as label requirement information.

6. A device based on tag management, characterized in that: The device comprises: an acquisition module, configured to acquire label requirement information and generate at least one first label corresponding to the label requirement information based on the label requirement information; a first classification module, configured to classify the first tag into a first directory level corresponding to the first tag and update a database in response to a first operation instruction; a determination module configured to, when the scenario requirement information is acquired, determine a second directory level according to the scenario requirement information and the database, and determine a target user corresponding to the second directory level according to the second directory level; The sending module is used to send the service corresponding to the scenario requirement information to the terminal of the target user.

7. The tag management-based device according to claim 6, characterized in that: The device further comprises: a configuration module, configured to configure a tag type for the first tag in response to a second operation instruction; The second classification module is configured to classify the tag type corresponding to the first tag into a directory level corresponding to the first tag.

8. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the tag management method according to any one of claims 1 to 5 by executing the computer instructions.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the tag-based management method according to any one of claims 1 to 5.

10. A computer program product, characterized in that The method comprises computer instructions for causing a computer to execute the tag-based management method according to any one of claims 1 to 5.

Images