Label generation method and device, equipment, medium and product

Abstract

The invention relates to the technical field of pipeline engineering, and discloses an annotation generation method and device, equipment, a medium and a product, and the method comprises the steps: obtaining a first annotation entity; in response to the adjustment of the user on the target annotation object, obtaining an adjustment parameter based on the first identifier of the target annotation object and the first mapping relationship; obtaining a second identifier of the first annotation entity based on the first identifier and a second mapping relationship; and updating the first annotation entity based on the adjustment parameter and the second identifier to obtain an updated second annotation entity. When the user adjusts the target annotation object, the first annotation entity is updated on the basis of the target annotation object, the identifier of the first annotation entity and the mapping relation, the situation that manual change depends on design change can be avoided, and therefore time and labor cost is reduced, annotation content is automatically updated, and annotation efficiency is improved.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of pipeline engineering, and particularly relates to a generation method and device of annotation, equipment, medium and product. BACKGROUND

[0002] In the design process of a pipeline engineering construction drawing, a traditional method manually inputs attribute information of a pipeline to perform corresponding annotation on the pipeline in the drawing, and when a design change occurs, attribute information in the drawing also needs to be manually changed one by one.

[0003] The traditional method has certain limitations when performing annotation on the drawing. Since the attribute information is manually input, and manual change is needed when a design change occurs, the annotation content cannot be automatically updated according to the current model, and the designer needs to spend a lot of time and effort to perform annotation, resulting in high time cost and labor cost and low annotation efficiency. SUMMARY

[0004] Therefore, the present disclosure provides a generation method and device of annotation, equipment, medium and product to solve the problem of low annotation efficiency.

[0005] In a first aspect, the present disclosure provides a generation method of annotation, comprising:

[0006] obtaining a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style;

[0007] in response to adjustment of the target annotation object by a user, obtaining an adjustment parameter based on a first identifier of the target annotation object and a first mapping relationship, wherein the first mapping relationship is used to represent a mapping relationship between the first identifier and the adjustment parameter;

[0008] obtaining a second identifier of the first annotation entity based on the first identifier and a second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier;

[0009] updating the first annotation entity based on the adjustment parameter and the second identifier to obtain an updated second annotation entity.

[0010] In the embodiments of the present disclosure, the first labeled entity is obtained; in response to adjustment of the target labeling object by a user, an adjustment parameter is obtained based on the first identifier of the target labeling object and the first mapping relationship; a second identifier of the first labeled entity is obtained based on the first identifier and the second mapping relationship; and the first labeled entity is updated based on the adjustment parameter and the second identifier to obtain an updated second labeled entity. Since the embodiments of the present disclosure update the first labeled entity based on the identifiers of the target labeling object and the first labeled entity and the mapping relationship when the user adjusts the target labeling object, the embodiments of the present disclosure can avoid relying on manual changes when a design is changed, thereby reducing time and labor costs, realizing automatic updating of labeling content, and improving labeling efficiency.

[0011] In a second aspect, the present disclosure provides a labeling generation apparatus, which comprises:

[0012] A first obtaining module is configured to obtain a first labeled entity, wherein the first labeled entity is generated by labeling a target labeling object based on a target labeling style;

[0013] A first obtaining module is configured to obtain a first labeled entity, wherein the first labeled entity is generated by labeling a target labeling object based on a target labeling style;

[0014] A second obtaining module is configured to obtain a second identifier of the first labeled entity based on the first identifier and a second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier;

[0015] A first updating module is configured to update the first labeled entity based on the adjustment parameter and the second identifier to obtain an updated second labeled entity.

[0016] In a third aspect, the present disclosure provides a computer device, which comprises a memory and a processor, the memory and the processor are communicatively connected with each other, the memory stores computer instructions, and the processor executes the computer instructions to perform the labeling generation method of the first aspect or any of the corresponding embodiments thereof.

[0017] In a fourth aspect, the present disclosure provides a computer readable storage medium, which stores computer instructions, and the computer instructions are used to make a computer execute the labeling generation method of the first aspect or any of the corresponding embodiments thereof.

[0018] In a fifth aspect, the present disclosure provides a computer program product, which comprises computer instructions, and the computer instructions are used to make a computer execute the labeling generation method of the first aspect or any of the corresponding embodiments thereof. BRIEF DESCRIPTION OF DRAWINGS

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

[0020] Figure 1 is a flowchart of a generation method of a label according to an embodiment of the present disclosure;

[0021] Figure 2 is a schematic diagram of a label object and a label entity according to an embodiment of the present disclosure;

[0022] Figure 3 is a label style editing interface according to an embodiment of the present disclosure;

[0023] Figure 4 is a text content editing page according to an embodiment of the present disclosure;

[0024] Figure 5 is a character style setting page according to an embodiment of the present disclosure;

[0025] Figure 6 is a label format setting page according to an embodiment of the present disclosure;

[0026] Figure 7 is a parameter format setting page according to an embodiment of the present disclosure;

[0027] Figure 8 is a label object modification page according to an embodiment of the present disclosure;

[0028] Figure 9 is a label object modification result according to an embodiment of the present disclosure;

[0029] Figure 10 is a flowchart of another generation method of a label according to an embodiment of the present disclosure;

[0030] Figure 11 is a label style modification page according to an embodiment of the present disclosure;

[0031] Figure 12 is a label style modification result according to an embodiment of the present disclosure;

[0032] Figure 13 is a flowchart of still another generation method of a label according to an embodiment of the present disclosure;

[0033] Figure 14 is a flowchart of still another generation method of a label according to an embodiment of the present disclosure;

[0034] Figure 15 is a label style tree schematic diagram according to an embodiment of the present disclosure;

[0035] Figure 16 is a structural block diagram of a label generation device according to an embodiment of the present disclosure;

[0036] Figure 17 is a hardware structure schematic diagram of a computer device of an embodiment of the present disclosure. DETAILED DESCRIPTION

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

[0038] In the design process of a pipeline engineering construction drawing, a traditional method manually inputs attribute information of a pipeline to perform corresponding labeling on the pipeline in a drawing, and when a design change occurs, attribute information in the drawing also needs to be manually changed one by one.

[0039] The traditional method has certain limitations when labeling a drawing. Since attribute information is manually input, and manual change is needed when a design change occurs, the labeling content cannot be automatically updated according to a current model, and a designer needs to spend a lot of time and effort to perform labeling, resulting in high time cost and labor cost and low labeling efficiency.

[0040] To solve the above problems, according to an embodiment of the present disclosure, a label generation method embodiment is provided. It should be noted that the steps shown in the flowchart of the drawings can be executed in a computer system such as a group 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 herein.

[0041] In the present embodiment, a label generation method is provided, as shown in Figure 1 Figure 1 is a flowchart of a label generation method according to an embodiment of the present disclosure. The flowchart can be applied to a server and includes the following steps:

[0042] In step S101, a first labeling entity is obtained, wherein the first labeling entity is generated by labeling a target labeling object based on a target labeling style.

[0043] ​In the embodiments of the present disclosure, the first annotation entity refers to an annotation entity generated by the server based on the target annotation style for the target annotation object. The annotation entity is composed of annotation text content and annotation format, as shown in Figure 2 "dn500 L=54.5", "dn500 L=39.2" and "dn500 L=42.3" are annotation entities of the pipe, and "JS-1100" is an annotation entity of the node.

[0044] The target annotation object refers to a model entity in the pipeline engineering, such as a pipe and a node. As shown in Figure 2 The line segment in Figure 2 is a pipe, and the end point of the line segment is a node.

[0045] The target annotation style refers to a user-set annotation style, as shown in Figure 3 The annotation style includes visibility (yes / no), annotation text content (such as [node number prefix]-[node number]), annotation text style (such as GStandard), text height (such as 0.000), and color (such as smart color).

[0046] As shown in Figure 4 The annotation text content is composed of an annotation field and a format of the annotation field. The annotation field refers to an annotation attribute, and the annotation attribute is a feature possessed by the annotation object. For example, the annotation attributes of the node include node system type, node system abbreviation, node measurement coordinate X, node measurement coordinate Y, and the like, and the annotation attributes of the pipe include pipe system type, pipe system abbreviation, pipe two-dimensional length, pipe inner diameter, and the like.

[0047] In addition, the annotation style also includes a character style, an annotation format, and a parameter format, and the like. As shown in Figure 5 The character style includes a font (such as a Chinese font, an English font, and the like), a size (such as a height, and the like), an effect (such as a width factor, a Chinese character height ratio, an English character height ratio, and the like), and the like. As shown in Figure 6 The annotation format includes a text (such as a text style, a text height, and the like), a spacing (such as a character-to-line spacing, a line-end character spacing, and the like), and the like. As shown in Figure 7 The parameter format includes a basic format (such as a prefix, a suffix, and the like), a slope (such as a format, a precision, a rounding mode, a rounding-off zero, and the like).

[0048] Specifically, the server receives a target labeling style set by a user, parses the target labeling style to obtain a target labeling attribute in the target labeling style, obtains an identifier of the target labeling attribute according to a mapping relationship between the labeling attribute and the identifier of the labeling attribute, obtains an identifier of a target labeling object according to a mapping relationship between the identifier of the target labeling attribute and the identifier of the target labeling object, obtains an attribute value of the target labeling attribute according to a mapping relationship between the identifier of the target labeling object and the attribute value of the target labeling attribute, combines and adjusts the attribute value of the target labeling attribute according to the target labeling style set by the user, and labels the target labeling object to obtain a first labeling entity.

[0049] The server can also obtain the first labeling entity based on direct dragging of the graphical interface, pre-set a labeling component library (such as a pipeline labeling, a node labeling, etc.) and a labeling template, parse a component type and a template configuration after receiving a request of the client to drag a component to a model object, obtain a field corresponding model attribute value (such as a node stake number, a pipeline length, etc.) through a mapping relationship table, generate a labeling entity data according to a format (such as a text height, a color, etc.) set by the client, return to the client to render and display, and thus obtain the first labeling entity.

[0050] The server can also obtain the first labeling entity based on an application programming interface, pre-set the application programming interface and a script analysis engine, extract a target labeling attribute (such as a pipeline material, a two-dimensional length, etc.) of a target labeling object from a database through an interface parameter when receiving a labeling generation request sent by a developer through a code or a script, combine labeling content according to a pre-defined style rule (such as a text style, a parameter format, etc.), batch generate labeling entity data, and return to the client to render and display, and thus obtain the first labeling entity.

[0051] In step S102, an adjustment parameter is obtained based on the first identifier of the target labeling object and the first mapping relationship in response to adjustment of the target labeling object by the user, where the first mapping relationship is used to represent a mapping relationship between the first identifier and the adjustment parameter.

[0052] In the embodiments of the present disclosure, the first identifier refers to an identifier of the target labeling object, for example, the identifier can be a Guid, that is, a globally unique identifier with a binary length of 128 bits generated by an algorithm. The first mapping relationship refers to a mapping relationship between the first identifier and the adjustment parameter, which is automatically constructed by the server in the process of generating the target labeling object by the user and stored in the database. The adjustment parameter refers to an attribute value of an attribute in the target labeling object after adjustment of the target labeling object, for example, the node design elevation is adjusted from 100 to 99.8, and the adjustment parameter of the node design elevation is 99.8.

[0053] Specifically, the server listens to the attribute change event of the model object in real time, and when a user adjusts the attribute of a target annotation object (such as a node) (such as adjusting the design elevation of the node), the server queries the first mapping relationship pre-constructed by using the first identifier of the target annotation object, so as to obtain the attribute value of the attribute in the target annotation object after the target annotation object is adjusted, and obtain the adjustment parameter.

[0054] The server can also obtain the adjustment parameter based on the message queue. When the server detects the attribute change of the target annotation object, the first identifier of the object is encapsulated as a message and pushed to the message queue. After the message is obtained by using the parameter analysis service for monitoring the queue, the first mapping relationship table is queried, the adjustable parameter (such as the pipe slope and the node elevation) corresponding to the first identifier is matched, and the parameter value (such as the slope is adjusted from 0.02 to 0.03) modified by the user is extracted from the model database. The adjustment parameter in the format of “parameter name = change value” is combined and delivered to the annotation update module through the event bus, and the adjustment parameter is obtained.

[0055] In step S103, the second identifier of the first annotation entity is obtained based on the first identifier and the second mapping relationship, where the second mapping relationship is used to represent the mapping relationship between the first identifier and the second identifier.

[0056] In the embodiments of the present disclosure, the second identifier refers to the identifier of the first annotation entity. The second mapping relationship refers to the mapping relationship between the first identifier and the second identifier, which is automatically constructed by the server during the process in which the user generates the first annotation entity, and is stored in the database.

[0057] Specifically, the server queries the second mapping relationship pre-constructed by using the first identifier of the target annotation object, and obtains the second identifier corresponding to the first identifier.

[0058] The server can also obtain the second identifier of the first annotation entity based on the distributed key-value storage. The server stores the second mapping relationship by using the distributed key-value storage, stores the first identifier as a key, and stores the second identifier as a value in the cache. When the second identifier is obtained, the server queries the key-value pair by using the first identifier, and obtains the second identifier of the first annotation entity.

[0059] The server can also obtain the second identifier of the first annotation entity based on the graph database. The server uses the graph database (such as Neo4j) to construct the relationship graph of “annotation object-annotation entity”, and stores the first identifier as an attribute of the annotation object node and the second identifier as an attribute of the annotation entity node. The two are connected through a relationship edge. When the second identifier is obtained, the server takes the first identifier as a starting point, traverses the relationship edge to find the corresponding annotation entity node, and obtains the second identifier of the first annotation entity.

[0060] In step S104, the first annotation entity is updated based on the adjustment parameter and the second identifier, to obtain an updated second annotation entity.

[0061] In the embodiments of the present disclosure, the second annotation entity refers to an annotation entity obtained by updating the first annotation entity based on the adjusted target annotation object.

[0062] Specifically, the server locates the first annotation entity to be updated through the second identifier, combines and adjusts the adjustment parameter according to the target annotation style, generates new annotation text content, updates the annotation text content of the first annotation entity with the new annotation text content, synchronizes the new annotation text content to the front end for display, and generates the second annotation entity.

[0063] As shown in Figure 8 , Figure 9 , Figure 8 is an annotation object modification page according to an embodiment of the present disclosure, Figure 9 is an annotation object modification result according to an embodiment of the present disclosure, when the user adjusts the design elevation of the water supply node "JS-1" from 100 to 99.8 in Figure 8 , the first annotation entity "JS-1 water supply 100" of the node is updated to the second annotation entity "JS-1 water supply 99.8", and the modification result in Figure 9 is obtained.

[0064] The server can also generate the updated second annotation entity based on a message queue. The server encapsulates the adjustment parameter and the second identifier into an update message, pushes the update message to the message queue, and uses the annotation update service to listen to the message queue. After obtaining the update message from the message queue, the server retrieves the style configuration (such as text height, parameter format, etc.) of the first annotation entity from the cache through the second identifier, combines and adjusts the adjustment parameter according to the target annotation style, generates new annotation text content, updates the annotation text content of the first annotation entity with the new annotation text content, and triggers the front end to push, to generate the second annotation entity.

[0065] The server can also generate the updated second annotation entity based on the componentization of microservices. The server splits the annotation update into three microservices: parameter analysis, style acquisition, and content generation. The parameter analysis service is used to extract the adjustment parameter, the style acquisition service is used to obtain the target annotation style from the configuration center through the second identifier, the content generation service is used to combine the adjustment parameter and the target annotation style, and the annotation text content is reorganized. Finally, based on the reorganized annotation text content, the first annotation entity is updated through the gateway of the application programming interface, and the front end rendering engine is notified to refresh the corresponding annotation component, to generate the second annotation entity.

[0066] In an embodiment of the present disclosure, a first annotation entity is obtained; in response to a user's adjustment of a target annotation object, an adjustment parameter is obtained based on a first identifier of the target annotation object and a first mapping relationship; a second identifier of the first annotation entity is obtained based on the first identifier and the second mapping relationship; and the first annotation entity is updated based on the adjustment parameter and the second identifier to obtain an updated second annotation entity. Because the embodiment of the present disclosure updates the first annotation entity based on the identifiers and mapping relationship between the target annotation object and the first annotation entity when the user adjusts the target annotation object, it can avoid relying on manual changes when the design is changed, thereby reducing time and labor costs, achieving automatic updating of annotation content, and improving annotation efficiency.

[0067] In this embodiment, a method for generating a label is provided, such as Figure 10 As shown, Figure 10 FIG. 1 is a flow chart of another method for generating annotations according to an embodiment of the present disclosure. The flow chart can be applied to a server and includes the following steps:

[0068] Step S1001: Obtain a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style. Figure 1 Step S101 of the illustrated embodiment will not be described in detail here.

[0069] Step S1002 : in response to the user adjusting the target annotation style, obtaining an adjusted target annotation style.

[0070] In the embodiment of the present disclosure, the user's adjustment of the target annotation style includes but is not limited to adjusting the text content rules (such as adjusting the combination format of "[node number prefix]-[node number]"), adjusting the text style (such as changing the font type, adjusting the font height value, changing the font color, etc.), adjusting the annotation properties (such as adding the "design elevation" property, deleting the "node number prefix" property, etc.), and adjusting the annotation component layout (such as changing the position and visibility of the "upper node text").

[0071] Specifically, the server monitors the user's adjustment operations on the target annotation style (such as modifying the text height, parameter format, etc. through the style editor). When the user selects a style (such as "Stormwater Pipe Annotation") in the annotation style tree and adjusts its properties (such as changing the font height from 2.5mm to 3mm, or adding a "Pipe Diameter" field), the server obtains the adjusted style configuration parameters, and by parsing the style definition in the configuration file or database, synchronizes the user's modified content (such as font height value, field combination) to the style storage structure to generate the adjusted target annotation style.

[0072] Step S1003: Acquire a target annotation object whose annotation style is the target annotation style.

[0073] Specifically, since the user adjusts the target annotation style, the server needs to locate all target annotation objects applying the target annotation style first, and then update the annotation styles of these target annotation objects to the adjusted annotation style.

[0074] More specifically, the server first acquires the identifier of the target annotation style, and uses the identifier to search in the database to obtain the first identifiers of all associated target annotation objects, and then extracts the corresponding target annotation objects (such as a certain pipe, a certain node) according to the first identifiers, to obtain all target annotation objects with the annotation style of the target annotation style.

[0075] In step S1004, the second identifier of the first annotation entity is obtained based on the first identifier of the target annotation object and the second mapping relationship, where the second mapping relationship is used to represent the mapping relationship between the first identifier and the second identifier.

[0076] Specifically, the server queries the pre-constructed second mapping relationship using the first identifier of the target annotation object to obtain the second identifier corresponding to the first identifier.

[0077] In step S1005, the first annotation entity is updated based on the adjusted target annotation style and the second identifier, to obtain an updated third annotation entity.

[0078] In the embodiments of the present disclosure, the third annotation entity refers to the annotation entity obtained by updating the first annotation entity based on the adjusted target annotation format.

[0079] Specifically, the server locates the first annotation entity to be updated through the second identifier, combines and adjusts the attribute values according to the adjusted target annotation style, generates new annotation text content, updates the annotation text content of the first annotation entity with the new annotation text content, synchronizes the new annotation text content to the front end for display, and generates the third annotation entity.

[0080] As shown in Figure 11 , Figure 12 , the annotation style modification page according to the embodiments of the present disclosure is shown in Figure 11 , the annotation style modification result according to the embodiments of the present disclosure is shown in Figure 12 When the user adjusts the text content rule in the annotation style of the node to “[node number prefix]-[node number]” in Figure 11 , the first annotation entities “JS-1 99.8”, “JS-2 100”, and “JS-3 100” of the node applying the annotation style will be updated to the second annotation entities “JS-1 99.8”, “JS-2 100”, and “JS-3 100” respectively, and the third annotation entity is obtained Figure 12the modification result in the modified result.

[0081] In the embodiments of the present disclosure, by updating the first annotation entity based on the identifier and the mapping relationship when the user adjusts the target annotation style, one-key update of all first annotation entities with the target annotation style can be realized, thereby significantly reducing the workload of updating annotation and improving annotation efficiency.

[0082] In the present embodiment, a generation method of annotation is provided, as shown in Figure 13 Figure 13 is a flow diagram of another generation method of annotation according to the embodiments of the present disclosure. The flow can be applied to a server and includes the following steps:

[0083] In step S1301, a first annotation entity is obtained, wherein the first annotation entity is generated based on a target annotation style for a target annotation object.

[0084] Specifically, the above step S1301 includes:

[0085] In step S13011, a third identifier of a target annotation attribute is obtained based on the target annotation attribute in the target annotation style and a third mapping relationship, wherein the third mapping relationship is used to represent a mapping relationship between the annotation attribute and the identifier of the annotation attribute.

[0086] In the embodiments of the present disclosure, the third identifier refers to the identifier of the target annotation attribute. The third mapping relationship refers to the mapping relationship between the annotation attribute and the identifier of the annotation attribute, which is constructed by the server in advance before the user performs annotation and stored in a configuration file.

[0087] Specifically, the server first parses the target annotation style to obtain the target annotation attribute, and then queries the pre-constructed third mapping relationship by using the target annotation attribute to obtain the third identifier of the target annotation attribute.

[0088] In step S13012, a first identifier of a target annotation object is obtained based on the third identifier and a fourth mapping relationship, wherein the fourth mapping relationship is used to represent a mapping relationship between the first identifier and the third identifier.

[0089] In the embodiments of the present disclosure, the fourth mapping relationship refers to the mapping relationship between the first identifier and the third identifier, which is constructed by the server automatically in the process of generating the first annotation entity by the user and stored in a database.

[0090] Specifically, the server queries the pre-constructed fourth mapping relationship by using the third identifier of the target annotation attribute to obtain the first identifier of the target annotation object corresponding to the third identifier.

[0091] ​At step S13013, an attribute value of the target annotation attribute is obtained based on the first identifier and a fifth mapping relationship, where the fifth mapping relationship is used to represent a mapping relationship between the first identifier and the attribute value of the target annotation attribute.

[0092] In the embodiments of the present disclosure, the fifth mapping relationship refers to a mapping relationship between the first identifier and the attribute value of the target annotation attribute, which is automatically constructed by the server in the process that the user generates the first annotation entity and stored in the database.

[0093] Specifically, the server queries the pre-constructed fifth mapping relationship by using the first identifier of the target annotation object to obtain the attribute value of the target annotation attribute corresponding to the first identifier.

[0094] At step S13014, the target annotation object is annotated based on the target annotation style and the attribute value of the target annotation attribute to generate the first annotation entity.

[0095] Specifically, the server first reads the target annotation style (such as the text content rule “[node number prefix]-[node number]” and the like), identifies the target annotation object (such as the water supply nodes “JS-1”, “JS-2”, “JS-3” and the like), and extracts the target annotation attributes (such as the design elevation) and the corresponding attribute values (such as 99.8, 100 and the like) of these target annotation objects.

[0096] Then, the server integrates and formats the attribute values according to the text format (such as font, font size and the like) and layout mode (such as text position and the like) set in the target annotation style. For example, the server associates the water supply node “JS-1” and the attribute value “99.8” to the corresponding target annotation object position in the form specified by the target annotation style (such as “number+space+design elevation”), and generates a visual annotation on the drawing to obtain the first annotation entity “JS-1 99.8”.

[0097] At step S1302, in response to the adjustment of the target annotation object by the user, an adjustment parameter is obtained based on the first identifier of the target annotation object and a first mapping relationship, where the first mapping relationship is used to represent a mapping relationship between the first identifier and the adjustment parameter. For details, please refer to Figure 1 The step S102 of the embodiment shown in the figure will not be repeated here.

[0098] At step S1303, a second identifier of the first annotation entity is obtained based on the first identifier and a second mapping relationship, where the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier. For details, please refer to Figure 1 The step S103 of the embodiment shown in the figure will not be repeated here.

[0099] Step S1304, updating the first annotated entity based on the adjustment parameter and the second identifier, to obtain an updated second annotated entity. For details, please refer to Figure 1 Step S104 of the embodiment shown in the figure will not be described here.

[0100] In the embodiments of the present disclosure, by obtaining the attribute value based on the identifier and the mapping relationship, and then annotating the target annotation object based on the target annotation style and the attribute value, the first annotated entity can be automatically generated, thereby reducing the time and labor cost of annotation and improving the annotation efficiency.

[0101] In the present embodiment, a generation method of annotation is provided, as shown in Figure 14 Figure 14 is a flow diagram of another generation method of annotation according to an embodiment of the present disclosure. The flow can be applied to a server and includes the following steps:

[0102] Step S1401, obtaining an annotation object, an annotation sub-object, and an annotation attribute.

[0103] In the embodiments of the present disclosure, the annotation object refers to a model entity in a pipeline engineering, such as a pipe and a node. The annotation sub-object is a component of the annotation object and is a further disintegration of the annotation object, for example, the annotation sub-objects of a node include a node number annotation and a node stake number annotation, and the annotation sub-objects of a pipe include a pipe line side annotation, a pipe line end annotation, and a pipe symbol annotation.

[0104] The annotation attribute is a feature possessed by the annotation object, for example, the annotation attributes of a node include a node system type, a node system abbreviation, a node measurement coordinate X, and a node measurement coordinate Y, and the annotation attributes of a pipe include a pipe system type, a pipe system abbreviation, a pipe two-dimensional length, and a pipe inner diameter.

[0105] Specifically, the server first parses the structure definition of the pipeline engineering model, extracts basic entities such as pipes and nodes from the model as annotation objects, and then subdivides the annotation objects, such as disintegrating a node into node number annotations and node stake number annotations, and disintegrating a pipe into pipe line side annotations, pipe line end annotations, and pipe symbol annotations.

[0106] Then, the server parses the features of the annotation objects, such as taking the node system type and the node system abbreviation of a node as the annotation attributes of the node, and taking the pipe two-dimensional length and the pipe inner diameter of a pipe as the annotation attributes of the pipe.

[0107] Step S1402, generating an identifier of the annotation attribute based on a preset algorithm and the annotation attribute, wherein the identifier of the annotation attribute is a unique identifier for representing the annotation attribute.

[0108] ​In the embodiments of the present disclosure, the preset algorithm refers to an algorithm for generating an identifier.

[0109] Specifically, the server processes each annotation attribute based on the preset algorithm, takes the name, type, and other information of the annotation attribute as input, generates a corresponding unique identifier (such as a 128-bit Guid), and obtains the identifier of the annotation attribute.

[0110] In step S1403, a configuration file is generated based on the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute.

[0111] In the embodiments of the present disclosure, the configuration file is a structured file for storing annotation information such as the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute, which can be an XML format file, a key-value pair, or a database storage form.

[0112] Specifically, the server constructs a hierarchical mapping relationship among the annotation information based on the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute, and stores the mapping relationship in the configuration file.

[0113] Specifically, the above step S1403 includes:

[0114] In step S14031, a sixth mapping relationship between the annotation object and the annotation sub-object is constructed based on the annotation object and the annotation sub-object.

[0115] In the embodiments of the present disclosure, the sixth mapping relationship refers to the mapping relationship between the annotation object and the annotation sub-object, which is constructed by the server in advance before the user performs annotation and stored in the configuration file.

[0116] Specifically, the server can define the annotation sub-object set corresponding to the annotation object through a dictionary data structure, such as {“pipe”: [“pipe line side annotation”, “pipe line end annotation”, “pipe symbol annotation”]}, or create a table structure in the database to record the corresponding relationship between the annotation object name and the annotation sub-object name, and obtain the sixth mapping relationship.

[0117] In step S14032, a seventh mapping relationship between the annotation sub-object and the annotation attribute is constructed based on the annotation sub-object and the annotation attribute.

[0118] In the embodiments of the present disclosure, the seventh mapping relationship refers to the mapping relationship between the annotation sub-object and the annotation attribute, which is constructed by the server in advance before the user performs annotation and stored in the configuration file.

[0119] Specifically, the server can define the annotation attribute set corresponding to the annotation sub-object through a dictionary data structure, such as {“pipe line side annotation”:[“pipe system type”, “pipe system abbreviation”, “pipe two-dimensional length”, “pipe inner diameter”]}, or create a table structure in the database to record the corresponding relationship between the annotation sub-object name and the annotation attribute name, to obtain the sixth mapping relationship.

[0120] In step S14033, a third mapping relationship between the annotation attribute and the identifier of the annotation attribute is constructed based on the annotation attribute and the identifier of the annotation attribute.

[0121] In the embodiments of the present disclosure, the third mapping relationship refers to the mapping relationship between the annotation attribute and the identifier of the annotation attribute, which is constructed by the server in advance before the user performs annotation and stored in the configuration file.

[0122] Specifically, the server can define the identifier set of the annotation attribute corresponding to the annotation attribute through a dictionary data structure, such as {“pipe two-dimensional length”:“Attr-Guid-001”, “pipe inner diameter”:“Attr-Guid-002”}, or create a table structure in the database to record the corresponding relationship between the annotation attribute name and the identifier of the annotation attribute, to obtain the sixth mapping relationship.

[0123] In step S14034, the configuration file is generated based on the sixth mapping relationship, the seventh mapping relationship, and the third mapping relationship.

[0124] Specifically, the server integrates the sixth mapping relationship, the seventh mapping relationship, and the third mapping relationship into structured data, and stores the structured data in the configuration file in the XML format or the key-value pair manner.

[0125] In step S1404, the annotation style tree is constructed based on the configuration file, and the target annotation style is set based on the annotation style tree.

[0126] In the embodiments of the present disclosure, as shown in Figure 15 The annotation style tree refers to an annotation rule framework presented in a tree structure, the root node is an annotation object (such as a pipe or a node), the child node is an annotation sub-object (such as the annotation sub-objects of a node including node number annotation and node stake number annotation, and the annotation sub-objects of a pipe including pipe line side annotation, pipe line end annotation, and pipe symbol annotation), and the leaf node is an annotation attribute. When the user clicks the “standard” control under the annotation sub-object, a text content editor as shown in Figure 4 is triggered, and the optional fields in the editor are annotation attributes (such as the annotation attributes of a node including node system type, node system abbreviation, node measurement coordinate X, and node measurement coordinate Y, and the annotation attributes of a pipe including pipe system type, pipe system abbreviation, pipe two-dimensional length, and pipe inner diameter).

[0127] Specifically, the server first extracts the labeling object from the configuration file and takes it as a root node of the labeling style tree, then extracts the labeling sub-object corresponding to each labeling object from the configuration file and takes it as a child node under the corresponding root node respectively, and then extracts the labeling attribute corresponding to each labeling sub-object from the configuration file and takes it as a leaf node under the child node respectively, and renders the above hierarchical relationship into a tree component that can be interacted with the front end to obtain the labeling style tree.

[0128] In step S1405, a first labeling entity is obtained, wherein the first labeling entity is generated by labeling the target labeling object based on a target labeling style. For details, please refer to Figure 1 The step S101 of the embodiment shown in the figure will not be repeated here.

[0129] In step S1406, in response to the adjustment of the target labeling object by the user, an adjustment parameter is obtained based on the first identifier of the target labeling object and a first mapping relationship, wherein the first mapping relationship is used to represent the mapping relationship between the first identifier and the adjustment parameter. For details, please refer to Figure 1 The step S102 of the embodiment shown in the figure will not be repeated here.

[0130] In step S1407, a second identifier of the first labeling entity is obtained based on the first identifier and a second mapping relationship, wherein the second mapping relationship is used to represent the mapping relationship between the first identifier and the second identifier. For details, please refer to Figure 1 The step S103 of the embodiment shown in the figure will not be repeated here.

[0131] In step S1408, the first labeling entity is updated based on the adjustment parameter and the second identifier to obtain an updated second labeling entity. For details, please refer to Figure 1 The step S104 of the embodiment shown in the figure will not be repeated here.

[0132] In step S1409, the target labeling requirement of the user is obtained.

[0133] In the embodiments of the present disclosure, the target labeling requirement refers to the newly added labeling attribute or the deleted part of the existing labeling attribute of the user, for example: adding the labeling attributes of "node material" and "pipeline pressure grade", or deleting the labeling attributes of "node measurement coordinate X" and "node measurement coordinate Y".

[0134] Specifically, the server receives the target labeling requirement input by the user or selected from the extended attribute library through the front-end interactive interface, and converts the target labeling requirement into structured data (such as JSON format data), and stores it in the temporary cache or database as the basis for subsequent adjustment of the configuration file and the labeling style tree.

[0135] At step S14010, the annotation attribute in the configuration file is adjusted based on the target annotation requirement, and an adjusted configuration file is obtained.

[0136] Specifically, the server parses the target annotation requirement proposed by the user to obtain the adjustment content of the annotation attribute by the target annotation requirement, that is, to add an annotation attribute or delete part of an existing annotation attribute.

[0137] If the target annotation requirement is to add an annotation attribute, the server first generates an identifier of the added annotation attribute by using a preset algorithm, and establishes a corresponding relationship between the name of the added annotation attribute and the identifier of the added annotation attribute. Then, the server determines the annotation sub-object to which the added annotation attribute belongs, and writes the added annotation attribute and its identifier into the configuration file to obtain a configuration file containing the added annotation attribute.

[0138] If the target annotation requirement is to delete part of an existing annotation attribute, the server first queries the identifier of the annotation attribute to be deleted through the third mapping relationship, and then determines the annotation sub-object to which the annotation attribute belongs. Then, the server locates the corresponding annotation attribute entry under the annotation sub-object in the configuration file and deletes it to obtain a configuration file in which part of the existing annotation attribute is deleted.

[0139] At step S14011, the annotation style tree is updated based on the adjusted configuration file, and an updated annotation style tree is obtained.

[0140] Specifically, the server reads and parses the adjusted configuration file to determine the adjustment content of the configuration file. If an annotation attribute is added in the configuration file, the server adds a corresponding annotation attribute node under the annotation sub-object corresponding to the annotation style tree and sets the related style parameters to obtain an updated annotation style tree. If part of the annotation attribute is deleted in the configuration file, the server removes the corresponding annotation attribute node from the annotation style tree to obtain an updated annotation style tree.

[0141] In the embodiments of the present disclosure, by generating a configuration file based on the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute, and constructing an annotation style tree, the structured management of the annotation style can be realized, and the user can set a target annotation style based on the annotation style tree. By constructing a mapping relationship and generating a configuration file based on the mapping relationship, the logical association between the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute can be determined, and the structured management of the annotation style can be realized. By adjusting the annotation attribute in the configuration file based on the target annotation requirement of the user, and then updating the configuration file and the annotation style tree, the user can add or delete the annotation attribute according to the actual design requirement, thereby improving the flexibility and expandability of the annotation system.

[0142] A device for generating annotations is also provided in this embodiment, which is used to implement the above-mentioned embodiments and preferred embodiments, and will not be described again. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the device described in the following embodiments is preferably implemented in software, implementation of hardware, or a combination of software and hardware, is also possible and contemplated.

[0143] The present embodiment provides a device for generating annotations, as shown in Figure 16 The device comprises:

[0144] The first obtaining module 1601 is configured to obtain a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style;

[0145] The first obtaining module 1601 is configured to obtain a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style;

[0146] The second obtaining module 1603 is configured to obtain a second identifier of the first annotation entity based on the first identifier and a second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier.

[0147] The first updating module 1604 is configured to update the first annotation entity based on the adjustment parameter and the second identifier to obtain an updated second annotation entity.

[0148] In the embodiments of the present disclosure, by obtaining a first annotation entity; in response to a user's adjustment of a target annotation object, obtaining an adjustment parameter based on a first identifier of the target annotation object and a first mapping relationship; obtaining a second identifier of the first annotation entity based on the first identifier and a second mapping relationship; and updating the first annotation entity based on the adjustment parameter and the second identifier to obtain an updated second annotation entity. Since the embodiments of the present disclosure update the first annotation entity based on the identifiers of the target annotation object and the first annotation entity and the mapping relationship when the user adjusts the target annotation object, it can avoid relying on manual changes when the design changes, thereby reducing time and labor costs, achieving automatic updating of annotation content, and improving annotation efficiency.

[0149] In some optional embodiments, the device further comprises:

[0150] The third obtaining module is configured to obtain an adjusted target annotation style in response to a user's adjustment of the target annotation style.

[0151] The second obtaining module is configured to obtain a target annotation object with a target annotation style as the annotation style;

[0152] The fourth obtaining module is configured to obtain a second identifier of the first annotation entity based on the first identifier of the target annotation object and a second mapping relationship, where the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier.

[0153] The second updating module is configured to update the first annotation entity based on the adjusted target annotation style and the second identifier, to obtain an updated third annotation entity.

[0154] In some optional embodiments, the first obtaining module 1601 includes:

[0155] The first obtaining sub-module is configured to obtain a third identifier of the target annotation attribute based on the target annotation attribute in the target annotation style and a third mapping relationship, where the third mapping relationship is used to represent a mapping relationship between the annotation attribute and the identifier of the annotation attribute.

[0156] The second obtaining sub-module is configured to obtain the first identifier of the target annotation object based on the third identifier and a fourth mapping relationship, where the fourth mapping relationship is used to represent a mapping relationship between the first identifier and the third identifier.

[0157] The third obtaining sub-module is configured to obtain an attribute value of the target annotation attribute based on the first identifier and a fifth mapping relationship, where the fifth mapping relationship is used to represent a mapping relationship between the first identifier and the attribute value of the target annotation attribute.

[0158] The first generating sub-module is configured to annotate the target annotation object based on the target annotation style and the attribute value of the target annotation attribute, to generate the first annotation entity.

[0159] In some optional embodiments, the apparatus further includes:

[0160] The third obtaining module is configured to obtain an annotation object, an annotation sub-object, and an annotation attribute.

[0161] The first generating module is configured to generate an identifier of the annotation attribute based on a preset algorithm and the annotation attribute, where the identifier of the annotation attribute is a unique identifier used to represent the annotation attribute.

[0162] The second generating module is configured to generate a configuration file based on the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute.

[0163] The constructing module is configured to construct an annotation style tree based on the configuration file, where the target annotation style is set based on the annotation style tree.

[0164] In some optional embodiments, the second generation module comprises:

[0165] The first construction submodule is configured to construct a sixth mapping relationship between the annotation object and the annotation sub-object based on the annotation object and the annotation sub-object.

[0166] The second construction submodule is configured to construct a seventh mapping relationship between the annotation sub-object and the annotation attribute based on the annotation sub-object and the annotation attribute.

[0167] The third construction submodule is configured to construct a third mapping relationship between the annotation attribute and the identifier of the annotation attribute based on the annotation attribute and the identifier of the annotation attribute.

[0168] The second generation submodule is configured to generate the configuration file based on the sixth mapping relationship, the seventh mapping relationship, and the third mapping relationship.

[0169] In some optional embodiments, the apparatus further comprises:

[0170] The fourth acquisition module is configured to acquire a target annotation requirement of a user.

[0171] The adjustment module is configured to adjust the annotation attribute in the configuration file based on the target annotation requirement to obtain an adjusted configuration file.

[0172] The third update module is configured to update the annotation style tree based on the adjusted configuration file to obtain an updated annotation style tree.

[0173] Further function descriptions of the above-mentioned modules and units are the same as those of the corresponding embodiments, and will not be repeated here.

[0174] The annotation generation apparatus in the present embodiment is presented in the form of a functional unit. The unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and a memory executing one or more software or fixed programs, and / or other devices that can provide the above functions.

[0175] The present embodiment also provides a computer device with the above-mentioned Figure 16 annotation generation apparatus.

[0176] Please refer to Figure 17 , Figure 17 is a structural schematic diagram of a computer device provided by an optional embodiment of the present disclosure, as Figure 17As shown, the computer device includes one or more processors 10, memory 20, and interfaces 30 for the various components to communicate with one another. The various components communicate through the use of the various buses, and can be mounted on a common motherboard or in other manners as appropriate. The processor 10 can process instructions for execution within the computer device, including instructions stored in the memory 20 or elsewhere to implement routines for displaying graphical information, such as a GUI on an external input / output device, such as a display device coupled to the interface 30. In some embodiments, multiple processors and / or multiple buses can be employed as appropriate, as will be appreciated by those skilled in the art. Additionally, various components of the computer device can be used for other purposes, such as storage of data to implement routines, as will also be appreciated by those skilled in the art. Figure 17 The processor 10 is taken as an example in the embodiments.

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

[0178] The memory 20 stores instructions that are executable by the at least one processor 10, so as to enable the at least one processor 10 to perform the method shown in the above embodiments.

[0179] The memory 20 can include a program storage area and a data storage area. The program storage area can store an operating system, application programs required by at least one function, and the like. The data storage area can store data created according to the use of the computer device, and the like. In addition, the memory 20 can include a high-speed random access memory, and can further include a non-transitory memory, such as at least one magnetic disk storage device, a flash memory device, or other non-transitory solid-state memory device. In some alternative embodiments, the memory 20 can optionally include a memory that is remotely arranged with respect to the processor 10, and these remote memories can be connected to the computer device through a network. Examples of the network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof.

[0180] The memory 20 can include a volatile memory, such as a random access memory, and can also include a non-volatile memory, such as a flash memory, a hard disk, or a solid state disk. The memory 20 can further include a combination of the above-mentioned kinds of memories.

[0181] The computer device further includes a communication interface 30 for the computer device to communicate with other devices or communication networks.

[0182] The embodiments of the present disclosure further provide a computer readable storage medium, and the method according to the embodiments of the present disclosure can be implemented in hardware, firmware, or recorded in a storage medium, or be implemented as computer code originally stored in a remote storage medium or a non-transitory machine readable storage medium and downloaded through a network and stored in a local storage medium, so that the method described herein can be processed by such software on a storage medium using a general purpose computer, a special purpose processor, or programmable or special purpose hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only memory, a random access memory, a flash memory, a hard disk or a solid state disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that the computer, processor, 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 the computer, processor or hardware, the method shown in the above embodiments is implemented.

[0183] Part of the present disclosure can be applied as a computer program product, for example, computer program instructions, when executed by a computer, through the operation of the computer, the method and / or technical solutions according to the present disclosure can be invoked or provided. Those skilled in the art should understand that the form of computer program instructions in computer readable medium includes but is not limited to source file, executable file, installation package file, etc., accordingly, the way of computer program instructions executed by computer includes but is not limited to: the computer directly executes the instructions, or the computer compiles the instructions and then executes the corresponding compiled program, or the computer reads and executes the instructions, or the computer reads and installs the instructions and then executes the corresponding installed program. Here, the computer readable medium can be any available computer readable storage medium or communication medium accessible to the computer.

[0184] Although the embodiments of the present disclosure are described in conjunction with the accompanying drawings, various modifications and changes can be made by those skilled in the art without departing from the spirit and scope of the present disclosure, and such modifications and changes fall within the scope defined by the appended claims.

Claims

1. A method for generating a label, characterized in that: The method comprises: Acquire a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style; In response to a user's adjustment of the target annotation object, obtaining an adjustment parameter based on a first identifier of the target annotation object and a first mapping relationship, wherein the first mapping relationship is used to represent a mapping relationship between the first identifier and the adjustment parameter; Obtaining a second identifier of the first annotation entity based on the first identifier and the second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier; The first annotation entity is updated based on the adjustment parameter and the second identifier to obtain an updated second annotation entity.

2. The method according to claim 1, characterized in that After obtaining the first annotation entity, the method further includes: In response to the user adjusting the target annotation style, obtaining an adjusted target annotation style; Acquire the target annotation object whose annotation style is the target annotation style; Obtaining a second identifier of the first annotation entity based on a first identifier and a second mapping relationship of the target annotation object, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier; Based on the adjusted target annotation style and the second identifier, the first annotation entity is updated to obtain an updated third annotation entity.

3. The method according to claim 1, characterized in that The obtaining of the first annotation entity includes: Obtaining a third identifier of the target annotation attribute based on the target annotation attribute in the target annotation style and a third mapping relationship, wherein the third mapping relationship is used to represent a mapping relationship between the annotation attribute and the identifier of the annotation attribute; Obtaining a first identifier of the target annotation object based on the third identifier and a fourth mapping relationship, wherein the fourth mapping relationship is used to represent a mapping relationship between the first identifier and the third identifier; Obtaining an attribute value of the target annotation attribute based on the first identifier and a fifth mapping relationship, wherein the fifth mapping relationship is used to represent a mapping relationship between the first identifier and the attribute value of the target annotation attribute; The target annotation object is annotated based on the target annotation style and the attribute value of the target annotation attribute to generate the first annotation entity.

4. The method according to claim 1, wherein Before obtaining the first annotation entity, the method further includes: Get annotation objects, annotation sub-objects and annotation properties; Based on a preset algorithm and the annotation attribute, an identifier of the annotation attribute is generated, wherein the identifier of the annotation attribute is a unique identifier for representing the annotation attribute; generating a configuration file based on the annotation object, the annotation sub-object, the annotation attribute, and an identifier of the annotation attribute; A label style tree is constructed based on the configuration file, wherein the target label style is set based on the label style tree.

5. The method according to claim 4, characterized in that The generating of a configuration file based on the annotation object, the annotation sub-object, the annotation attribute, and the identifier of the annotation attribute includes: Based on the marked object and the marked sub-object, constructing a sixth mapping relationship between the marked object and the marked sub-object; Based on the annotation sub-object and the annotation attribute, constructing a seventh mapping relationship between the annotation sub-object and the annotation attribute; Based on the annotation attribute and the identifier of the annotation attribute, constructing a third mapping relationship between the annotation attribute and the identifier of the annotation attribute; The configuration file is generated based on the sixth mapping relationship, the seventh mapping relationship, and the third mapping relationship.

6. The method according to claim 5, characterized in that After constructing the annotation style tree based on the configuration file, the method further includes: Obtain the user's target labeling requirements; Based on the target labeling requirement, adjusting the labeling attributes in the configuration file to obtain an adjusted configuration file; The annotation style tree is updated based on the adjusted configuration file to obtain an updated annotation style tree.

7. A device for generating a label, characterized in that: The device comprises: A first acquisition module is configured to acquire a first annotation entity, wherein the first annotation entity is generated by annotating a target annotation object based on a target annotation style; a first obtaining module, configured to obtain, in response to a user's adjustment of the target annotation object, an adjustment parameter based on a first identifier of the target annotation object and a first mapping relationship, wherein the first mapping relationship is used to represent a mapping relationship between the first identifier and the adjustment parameter; A second obtaining module is configured to obtain a second identifier of the first annotation entity based on the first identifier and the second mapping relationship, wherein the second mapping relationship is used to represent a mapping relationship between the first identifier and the second identifier; A first updating module is configured to update the first annotation entity based on the adjustment parameter and the second identifier to obtain an updated second annotation entity.

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 annotation generation method according to any one of claims 1 to 6 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 annotation generation method according to any one of claims 1 to 6.

10. A computer program product, characterized in that The invention comprises computer instructions for causing a computer to execute the annotation generation method according to any one of claims 1 to 6.

Images