Metadata acquisition and application method, device, system, equipment, cluster, product and medium

Abstract

The invention provides metadata acquisition and application methods, devices, systems, equipment, a cluster, a product and a medium. The method comprises the steps that an extraction instruction is received, first metadata are extracted from any one or more of primitives, texts, connecting lines and backgrounds of a first architecture diagram according to the extraction instruction, and any one or more of the primitives, the texts, the connecting lines and the backgrounds are elements in the architecture diagram; the first metadata is stored; receiving an acquisition instruction, and acquiring first metadata according to the acquisition instruction; the first metadata is applied to any one or more of primitives, texts, connecting lines and backgrounds in a second architecture diagram, and the first architecture diagram and the second architecture diagram are different architecture diagrams.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of cloud computing, and in particular to a metadata obtaining and application method, device, system, equipment, cluster, product and medium. BACKGROUND

[0002] An architecture diagram is generally used to graphically represent the relationship between the structure and components of a system, software or process flow. Architecture diagrams are widely used in computer, cloud computing, database, communication network, automation control and other fields, which can help people better understand and communicate the structure, function and interaction of complex systems, and is one of the important tools to improve work efficiency and project success rate.

[0003] As systems, software, process flows and the like become increasingly complex, an architecture diagram may need to be collaborated by multiple users to complete, for example, an enterprise needs to design an architecture diagram of a communication network within the enterprise, wherein a user A loads an architecture diagram of a communication network of an A park, and a user B loads an architecture diagram of a communication network of the A park. However, the design styles of different users may be completely different, causing a very chaotic feeling. SUMMARY

[0004] The present application provides a metadata obtaining and application method, device, system, equipment, cluster, product and medium, which can unify the styles of different architecture diagrams.

[0005] In a first aspect, a metadata application method is provided. The method comprises:

[0006] A client sends an extraction instruction to a metadata service system. Accordingly, the metadata service system receives the extraction instruction sent by the client. The metadata service system extracts first metadata from any one or more of a graph element, text, a connection line and a background of a first architecture diagram according to the extraction instruction, and stores the first metadata. The graph element, text, connection line and background are elements in the architecture diagram. The client sends an obtaining instruction to the metadata service system. Accordingly, the metadata service system receives the obtaining instruction sent by the client. The metadata service system applies the first metadata to any one or more of a graph element, text, a connection line and a background in a second architecture diagram. The first architecture diagram and the second architecture diagram are different architecture diagrams.

[0007] In the above scheme, the first metadata can be extracted from the first architecture diagram, and the first metadata can be applied to the second architecture diagram, so that the style of the second architecture diagram can follow the style of the first architecture diagram, thereby unifying the styles of different architecture diagrams.

[0008] In some possible design, the first metadata of the first architecture diagram is stored, and a specific implementation manner of acquiring the first metadata according to the acquisition instruction can be that the metadata service system stores the first metadata of the first architecture diagram into any one or more of a personal metadata area, a workspace metadata area and an acceleration metadata area corresponding to the first user corresponding to the first architecture diagram. Then, the metadata service system acquires the first metadata from any one of the personal metadata area, the workspace metadata area and the acceleration metadata area. The personal metadata area is used to store metadata set by the first user or metadata extracted from the first architecture diagram drawn by the first user. The workspace metadata area is used to store metadata set by each user of a workspace where the first user is located or metadata extracted from an architecture diagram drawn by each user of the workspace. The acceleration metadata area is used to store metadata set by each user of the public including the first user or metadata extracted from an architecture diagram drawn by each user of the public.

[0009] In the above solution, the metadata of the architecture diagram can be stored in different metadata areas according to needs, and the confidentiality of different metadata areas can be selectively different. Specifically, the personal metadata area has the highest confidentiality and the lowest selectivity; the workspace metadata area has the highest confidentiality and medium selectivity; and the acceleration metadata area has the lowest confidentiality and the highest selectivity. The user can select the most suitable one according to needs.

[0010] In a case where the first metadata is acquired from the personal metadata area, the first architecture diagram and the second architecture diagram are drawn by the first user.

[0011] In a case where the first metadata is acquired from the workspace metadata area, the first architecture diagram is drawn by the first user, and the second architecture diagram is drawn by a second user, and the first user and the second user belong to the same workspace.

[0012] In a case where the first metadata is acquired from the acceleration metadata area, the first architecture diagram is drawn by the first user, and the second architecture diagram is drawn by a third user, and the first user and the third user do not belong to the same workspace.

[0013] In some possible design, applying the first metadata to the second architecture diagram can at least include the following two manners:

[0014] In a first manner, the second metadata in the second architecture diagram is modified into the first metadata.

[0015] Secondly, the metadata of any one of the newly added graph element, text, connection line, and background in the second architecture diagram is set as second metadata.

[0016] In some possible designs, the first metadata includes any one or more of the following: line size, line type, line color, superscript color, background color, fill pattern, size, whether to have a shadow, transparency, round corner preset, three-dimensional rotation, font, font size, bold, underline, text position, font color, background color, background image, background color, and whether to include grid lines.

[0017] Secondly, the metadata of any one of the newly added graph element, text, connection line, and background in the second architecture diagram is set as second metadata.

[0018] Thirdly, a metadata application method is provided. The metadata service system receives an acquisition instruction, acquires the first metadata according to the acquisition instruction, and applies the first metadata to any one or more of the graph element, text, connection line, and background in the second architecture diagram. The first metadata includes the metadata of any one or more of the graph element, text, connection line, and background, and any one or more of the graph element, text, connection line, and background is an element in the architecture diagram.

[0019] In some possible designs, the first metadata is stored in at least the following two ways:

[0020] In the first way, the first metadata is extracted from any one or more of the graph element, text, connection line, and background in the first architecture diagram according to an extraction instruction, and the first metadata of the first architecture diagram is stored.

[0021] In the second way, the first metadata set by a user is received and stored.

[0022] In a fourth aspect, a metadata application method is provided. A metadata service system receives an extraction instruction, extracts first metadata from any one or more of a figure element, a text, a connection line, and a background of a first architecture diagram according to the extraction instruction, and stores the first metadata. The metadata service system receives an acquisition instruction, acquires the first metadata according to the acquisition instruction, and applies the first metadata to any one or more of a figure element, a text, a connection line, and a background of a second architecture diagram.

[0023] In a fifth aspect, a metadata acquisition apparatus is provided. The apparatus includes a receiving module configured to receive an extraction instruction and extract first metadata from any one or more of a figure element, a text, a connection line, and a background of a first architecture diagram according to the extraction instruction, and a storage module configured to store the first metadata.

[0024] In a sixth aspect, a metadata application apparatus is provided. The apparatus includes a receiving module configured to receive an acquisition instruction and acquire first metadata according to the acquisition instruction, and an application module configured to apply the first metadata to any one or more of a figure element, a text, a connection line, and a background of a second architecture diagram. The first metadata includes metadata of any one or more of a figure element, a text, a connection line, and a background, and the figure element, the text, the connection line, and the background are elements in an architecture diagram.

[0025] In a seventh aspect, a metadata system is provided. The system includes:

[0026] a client configured to send an extraction instruction;

[0027] a metadata service system configured to extract first metadata from any one or more of a figure element, a text, a connection line, and a background of a first architecture diagram according to the extraction instruction, and store the first metadata;

[0028] the client is configured to send an acquisition instruction;

[0029] the metadata service system is configured to acquire the first metadata according to the acquisition instruction, and apply the first metadata to any one or more of a figure element, a text, a connection line, and a background of a second architecture diagram. The first architecture diagram and the second architecture diagram are different architecture diagrams.

[0030] In an eighth aspect, a chip system is provided, the chip system comprising a processor and a power supply circuit, the power supply circuit configured to supply power to the processor, the processor configured to perform the operational steps of the method according to any one of the first to fourth aspects.

[0031] In a ninth aspect, a computing device is provided, the computing device comprising a processor and a memory; the processor configured to execute instructions stored in the memory to cause the computing device to perform the operational steps of the method according to any one of the first to fourth aspects.

[0032] In a tenth aspect, a computing device cluster is provided, comprising at least one computing device, each computing device comprising a processor and a memory; the processor of the at least one computing device configured to execute instructions stored in the memory of the at least one computing device to cause the computing device cluster to perform the operational steps of the method according to any one of the first to fourth aspects.

[0033] In an eleventh aspect, a computer program product comprising instructions which, when executed by a computing device cluster, cause the computing device cluster to perform the operational steps of the method according to any one of the first to fourth aspects.

[0034] In a twelfth aspect, a computer-readable storage medium is provided, comprising computer program instructions which, when executed by a computing device cluster, cause the computing device cluster to perform the operational steps of the method according to any one of the first to fourth aspects. BRIEF DESCRIPTION OF DRAWINGS

[0035] Figure 1 is a schematic diagram of a graph element provided by the present application;

[0036] Figure 2 is a schematic diagram of metadata of a graph element provided by the present application;

[0037] Figure 3 is a schematic diagram of a structure of a metadata system provided by the present application;

[0038] Figure 4 is a schematic diagram of a flow of a metadata application method provided by the present application;

[0039] Figure 5 is a schematic diagram of a flow of a metadata application method provided by the present application;

[0040] Figure 6 is a schematic diagram of a structure of a metadata application device provided by the present application;

[0041] Figure 7 is a schematic diagram of a structure of a metadata system provided by the present application;

[0042] Figure 8 is a structural schematic diagram of a computing device provided by the present application;

[0043] Figure 9 is a structural schematic diagram of a computing device cluster provided by the present application;

[0044] Figure 10 is a structural schematic diagram of another computing device cluster provided by the present application. DETAILED DESCRIPTION

[0045] The elements of the architecture diagram can include one or more of a graphic, text, and a line, etc. The graphic, text, line, and background will be introduced in detail respectively.

[0046] The graphic is generally used to refer to the basic constituting element in the architecture diagram. The graphic can be a shape schematic diagram of the element in the architecture diagram, so that the user can clearly know the element represented by the graphic through the shape of the graphic. For example, the graphic can be the shape of a mobile phone or a notebook, so that the user can know that the graphic represents the mobile phone or the notebook through the shape of the graphic. Alternatively, the graphic can be an abstract shape agreed in the industry, for example, the shape of Wifi. Alternatively, the graphic can be represented in the form of a frame + text, wherein the frame is used to represent the boundary of the object, and the text is used to represent the name of the object. The graphic can be a simple geometric shape or a more complex graphic object. For example, the graphic can be composed of one or more of a point, a line segment, a polygon, a circle, a rectangle, text, and a bitmap.

[0047] The types of the graphic can be very diverse: when the graphic is a basic graphic, it can be a triangle, an ellipse, a rectangle, a circle, a diamond, etc.; when the graphic is a business graphic, it can be a title, a main title, a plurality of titles, etc.; when the graphic is an architectural graphic, it can be a cabinet, a refrigerator, a bed, a wardrobe, a bedside table, a TV cabinet, a sofa, a dining table, etc.; when the graphic is a network graphic, it can be a server, a repeater, a wireless transmission tower, a satellite, etc.; when the graphic is a network graphic, it can be a schematic shape of a server, a repeater, a wireless transmission tower, a satellite, etc.; when the graphic is an electrical graphic, it can be a schematic shape of a switch, a capacitor, a resistor, a variable capacitor, a variable resistor, a relay, a fuse, an indicator light, etc.; when the graphic is a cloud service, it can be a schematic shape of a region, an available region, a virtual private cloud, a cluster, a business layering, a dedicated cloud, a dedicated computing cluster, a dedicated host, a security group, an elastic cloud service, a cloud phone, and an image service, etc. In a specific embodiment, as shown in FIG. 1, the graphic can include a rectangle, a square, an ellipse, a cylindrical shape, a diamond, a cube, a ring, a cross, and an L shape, etc. Figure 1 ​

[0048] The figure element can include one or more kinds of metadata: line size, line type, line color, superscript color, background color, fill pattern, size, whether to have a shadow, transparency, round corner preset, three-dimensional rotation. Among them, the line size can be 0.5pt, 0.75pt, 1.0pt, etc. The line type can be a dashed line, a solid line, a dotted line, a dot-dash line, a long dash line, etc. The line color can be red, orange, yellow, green, blue, green, purple, white, black, etc. The superscript color can be red, orange, yellow, green, blue, green, purple, white, black, etc. The background color can be red, orange, yellow, green, blue, green, purple, white, black, etc. The fill pattern is a dark vertical line, a grid, a chessboard, a shed, etc. The size can be 60x60, 48x48, 36x36, etc. The transparency range can be 0%~100%, when the transparency is 0%, it is completely opaque, when the transparency is 100%, it is completely transparent. The round corner preset can include small round corner, medium round corner, large round corner, and extra large round corner, etc. The three-dimensional rotation can include X rotation, Y rotation, and Z rotation, etc., wherein the X rotation can be 0 degrees to 360 degrees, the Y rotation can be 0 degrees to 360 degrees, and the Z rotation can be 0 degrees to 360 degrees. In a specific embodiment, as shown in FIG. 1, the metadata of the figure element includes font size, font size, text position, and line segment type, etc. Figure 2

[0049] Text can be used to display a collection of languages or symbols. The text can include one or more kinds of metadata: font, font size, bold, underline, text position, font color, background color, etc. Among them, the font can be bold, Kai, Song, color cloud, new Wei, running script, cursive, thin black, etc. The font size can be primary, small primary, one, small one, two, small two. The text position can be left, center, right, upper middle, lower, etc. The font color can be red, orange, yellow, green, blue, green, purple, white, black, etc. The background color can be red, orange, yellow, green, blue, green, purple, white, black, etc.

[0050] The connection line is used to connect the figure elements. The connection line can be a connection line with a double-headed arrow, can be a connection line with a single-headed arrow, or can be a connection line without an arrow. The connection line can include one or more kinds of metadata: line size, line type, line color, etc. Among them, the line size can be 0.5pt, 0.75pt, 1.0pt, etc. The line type can be a dashed line, a solid line, a dotted line, a dot-dash line, a long dash line, etc. The line color can be red, orange, yellow, green, blue, green, purple, white, black, etc.

[0051] ​Background refers to the environment or scenario behind the architecture diagram. The background can include one or more metadata: background picture, background color, whether to include grid lines. Among them, the background picture can be a custom picture, a preset picture, etc. The background color can be red, orange, yellow, green, blue, green, purple, white, black, etc.

[0052] It can be understood that the above architecture diagram is illustrated by taking the graphic element, text, connection line and background as examples. In actual application, the architecture diagram can further include more elements, which are not specifically illustrated here.

[0053] When designing the architecture diagram, it is usually necessary to design in the page of the file of the design software. Among them, the file is a basic unit for saving and managing the work results in the design software. In the design software, each project created by the user is saved in the form of a file. The file can include one or more pages. The page is a separate work area in the file, which is used to display and edit the drawing content. The page can be a canvas, on which the user can draw, edit and arrange graphic elements. In a multi-page file, each page can be independently edited, but all pages are saved in the same file for easy management and sharing. In summary, the file is a container in the drawing software for saving the work results of the entire project, and the page is a work area inside the file for displaying and editing the drawing content.

[0054] The design software can run under a computing device or a metadata system. Among them, the computing device can be a hardware device that can perform computing tasks, process data and execute various algorithms. They can be simple or highly complex, and the main function is to receive input data, process and then output results, for example, it can be a tablet computer, a mobile notebook, a personal computer, etc. The metadata system is a system platform based on cloud computing technology, which provides computing resources, storage resources, network resources and a series of management and service functions. The following will take the design software running under the metadata system as an example for illustration.

[0055] Referring to Figure 3 , Figure 3 is a structural schematic diagram of a metadata system provided by the present application. As Figure 3As shown, the metadata system of the present application comprises a client 110 and a metadata service system 120. In the architecture, the number of clients 110 and metadata service systems 120 can be one or more, which is not specifically limited in the present application. The client 110 and the metadata service system 120 establish a communication connection through a network, which can be a wired connection or a wireless connection, and the network can be a public Internet, an internal LAN, a virtual private network (VPN), a dedicated line such as a fiber line, a copper line, a satellite connection, a wireless network such as a wireless fidelity (Wi-Fi) network, a cellular network, and the like, which is not specifically limited in the present application.

[0056] The client 110 is deployed on a terminal device or a computing device to realize human-computer interaction. The terminal device includes a personal computer, a smart phone, a wearable device, a palm-held processing device, a tablet computer, a mobile notebook, an augmented reality (AR) device, a virtual reality (VR) device, a smart conference device, and the like, which is not specifically limited herein. The description of the computing device can refer to the foregoing content, which is not repeated here. The client 110 can also be deployed on a physical server such as an ARM server or an X86 server, which is not specifically limited in the present application.

[0057] In a specific implementation, the client 110 can be a software or an application running on a terminal device or a computing device controlled by a user, such as a personal computer (PC) client, a web client based on browser access, an application (APP) client running on a mobile terminal, or a console of a cloud platform, which is not specifically limited in the present application.

[0058] Optionally, the client 110 can be a client specially used for metadata extraction or metadata application, which can be used when a user needs to extract metadata from an architecture diagram or apply metadata to an architecture diagram.

[0059] Optionally, the client 110 can also be a comprehensive drawing client including the metadata extraction or metadata application, such as a graphical designer client, which not only includes the metadata extraction or metadata application function, but also includes other functions, such as a drawing design function, etc. The above examples are used for illustration, and the application is not limited specifically.

[0060] Optionally, the client 110 can also be a client of a cloud platform for users to purchase and rent various cloud services. The metadata extraction or metadata application scheme provided by the application can be one of the cloud services, and the user can purchase the cloud service to realize the metadata extraction or metadata application; or the cloud platform provides a comprehensive service to the user, and the metadata extraction or metadata application can be a sub-service in the comprehensive cloud service, such as a user purchasing a drawing cloud service, and the metadata extraction or metadata application function can be a sub-service in the cloud service, and the application is not limited specifically.

[0061] The metadata service system 120 can be deployed on a computing device, or a computing device cluster composed of multiple computing devices. The computing device can be a bare metal server (BMS), a virtual machine, a container, or a storage device. The BMS refers to a general-purpose physical server, such as an ARM server or an X86 server; the virtual machine refers to a complete computer system running in a completely isolated environment by software simulation, which has complete hardware system functions. The work that can be completed in the entity computer can be realized in the virtual machine. When creating a virtual machine in a computing device, part of the hard disk and memory capacity of the entity machine needs to be used as the hard disk and memory capacity of the virtual machine. Each virtual machine has independent BIOS, hard disk and operating system, and can be operated like using the entity machine; the container is a portable software unit, which can combine an application and all its dependencies into a software package, which is not limited by the underlying host operating system, so that the complex environment does not need to be built again, simplifying the application development to deployment process. In specific implementation, the computing device cluster can be a cloud data center, can also be an enterprise private cluster, and can also be a hybrid cloud environment, that is, a deployment mode of using public cloud and private cloud at the same time, and the application is not limited specifically.

[0062] In the above example, the metadata system only exemplarily lists the client 110 and the metadata service system 120. In actual application, the metadata system can also include one or more of a storage device, a data center, a storage system, etc.

[0063] Referring to Figure 4 ,Figure 4 is a metadata application method provided by the present application. As shown in Figure 4 the metadata application method provided by the present application comprises:

[0064] S101: The client sends an extraction instruction to the metadata service system. Accordingly, the metadata service system receives the extraction instruction sent by the client.

[0065] S102: The metadata service system extracts first metadata from elements of the first architecture diagram based on the extraction instruction.

[0066] The first metadata of the elements of the first architecture diagram determines the style of the first architecture diagram. Style refers to the unique and stable personality characteristics of individuals or groups in the design field under certain cultural background. For example, the style can include pastoral style, Nordic style, Mediterranean style, minimalist style, princess style, fresh and clean style, ancient style, retro style, etc. When the architecture diagram adopts different first metadata, the architecture diagram can embody different styles. For example, when the graph elements, lines and backgrounds in the first architecture diagram adopt bright colors such as red and yellow, the style of the first architecture diagram is festive; when the graph elements, lines and backgrounds in the first architecture diagram adopt colors such as pink and powder blue, the style of the first architecture diagram is cute. Here, only color is taken as an example, in actual application, graph element size, graph element line color, line width, line type, line color, text font, text size, text color, etc. can all affect the style of the first architecture diagram. As mentioned above, the number of first metadata of elements of the architecture diagram is very large, therefore, the style of the architecture diagram is naturally very large.

[0067] The first architecture diagram can be a user-specified architecture diagram, for example, when a user feels that the design style of a certain architecture diagram is very good, the user can specify the architecture diagram as the first architecture diagram.

[0068] The first architecture diagram is designed by using the design software, and therefore, the first architecture diagram can include a plurality of application programming interfaces, such as a new file interface, a new page interface, an open file interface, an open page interface, a metadata interface of a graph element, an event interface of a graph element, a metadata interface of a text, an event interface of a text, a metadata interface of a connection, an event interface of a connection, a metadata interface of a background, and an event interface of a background, and the like. Among them, the new file interface can be used to create a file for drawing the first architecture diagram, the new page interface can be used to create a page for drawing the first architecture diagram, the metadata interface of the graph element can be used to obtain the metadata of the graph element, the event interface of the graph element can be used to respond to the event of the graph element operated by the user, the metadata interface of the text can be used to obtain the metadata of the text, the event interface of the text can be used to respond to the event of the text operated by the user, the metadata interface of the connection can be used to obtain the metadata of the connection, the event interface of the connection can be used to respond to the event of the connection operated by the user, the metadata interface of the background can be used to obtain the metadata of the background, and the event interface of the background can be used to respond to the event of the background operated by the user.

[0069] The metadata service system extracts the first metadata from the elements of the first architecture diagram based on the extraction instruction can include the following manners:

[0070] In the first manner, the first metadata of the elements of the same type in the first architecture diagram is the same, and the first metadata is extracted from any one element of the type. Specifically, when the first metadata of the graph element in the first architecture diagram is the same, the first metadata of the graph element can be extracted from any one graph element, when the first metadata of the connection in the first architecture diagram is the same, the first metadata of the connection can be extracted from any one connection, and when the first metadata of the text in the first architecture diagram is the same, the first metadata of the text can be extracted from any one text. Therefore, the metadata service system can obtain the first metadata of any one graph element through the first metadata interface of the graph element, the first metadata of any one text through the first metadata interface of the text, the first metadata of any one connection through the first metadata interface of the connection, and the first metadata of the background through the first metadata interface of the background by opening the file in which the first architecture diagram is located through the open file interface and opening the page in which the first architecture diagram is located through the open page interface.

[0071] In the second mode, in the case that the elements of the same class in the first architecture diagram include multiple first metadata, the first metadata is extracted from a specified element in the class elements. Specifically, in the case that the graph element in the first architecture diagram includes multiple first metadata, the first metadata is extracted from a specified graph element in the graph element; in the case that the text in the first architecture diagram includes multiple first metadata, the first metadata is extracted from a specified text in the text; in the case that the connection line in the first architecture diagram includes multiple first metadata, the first metadata is extracted from a specified connection line in the connection line; in the case that the background in the first architecture diagram includes multiple first metadata, the first metadata is extracted from a specified background in the background. Therefore, the metadata service system can open the file in which the first architecture diagram is located through the file opening interface, open the page in which the first architecture diagram is located through the page opening interface, and then obtain the metadata of the specified graph element through the metadata interface of the graph element, obtain the metadata of the specified text through the metadata interface of the text, obtain the metadata of the specified connection line through the metadata interface of the connection line, and obtain the metadata of the background through the metadata interface of the background.

[0072] It can be understood that the above-mentioned mode of extracting the first metadata from the elements of the first architecture diagram is only a specific example, and in actual application, more modes can be included, which are not limited here.

[0073] The first architecture diagram can be an architecture diagram uploaded by a client, can be pre-stored in the metadata service system, or can be

[0074] S103: The metadata service system stores the first metadata of the first architecture diagram.

[0075] The metadata service system stores the first metadata of the first architecture diagram in the memory of the metadata service system, including at least the following two modes:

[0076] (1) The metadata service system stores the first metadata of the first architecture diagram in the memory of the metadata service system in the form of a metadata file.

[0077] The metadata file can be a text file, for example, a file with a suffix name such as txt, csv, log, etc., can also be a binary file, or a data file, for example, a file with a suffix name such as json, etc.

[0078] The number of metadata files can be one or more.

[0079] When the number of metadata files is one, the metadata of different architecture diagrams in the metadata service system can be stored in the same metadata file, and when storing, the metadata service system stores the business request in the metadata file according to the time sequence of receiving the metadata.

[0080] The process of the metadata service system storing the first metadata of the first architecture diagram in the metadata service system in the form of a metadata file is:

[0081] Firstly, the metadata service system can open the metadata file through a file opening function. The file opening function can be an open() function in Python programming language, a FileInputStream class or a FileReader class in Java programming language, an ifstream class in C++ programming language, a FileStream class in C# programming language, a fs.readFile() method in JavaScript programming language, a fopen() function in PHP programming language, etc.

[0082] Secondly, the metadata service system can write the first metadata of the first architecture diagram into the metadata file. The writing function can be a write() method in Python programming language, a FileOutputStream class or a FileWriter class in Java programming language, an ofstream class in C++ programming language, a StreamWriter class in C# programming language, a fs.writeFile() method in JavaScript programming language, a fwrite() function in PHP programming language, etc.

[0083] Finally, the metadata service system can close the metadata file through a closing function to release resources. The closing function can be a close() method in Python programming language, a close() method in Java programming language, a close() method or a destructor in C++ programming language, a Close() method or a Dispose() method in C# programming language, a fs.close() method in JavaScript programming language, a fclose() function in PHP programming language, etc.

[0084] When the number of metadata files is multiple, multiple metadata files can be created according to one or more of the name of the architecture diagram, the creation time, or a custom style name, etc. For example, metadata files can be created according to the custom style name and the creation time, or metadata files can be created according to the name of the architecture diagram.

[0085] (2) The metadata service system stores the first metadata of the first architecture diagram in the metadata service system in the form of a metadata database.

[0086] The metadata database can include a relational database management system (RDBMS), a Not Only SQL (NoSQL) database, a cloud database, and a memory database, and the like. The relational database can include MySQL, PostgreSQL, Oracle Database, Microsoft SQL Server, and SQLite.

[0087] The number of tables in the metadata database can be one or multiple.

[0088] When the number of tables is one, the metadata of different architecture diagrams can be stored in the same table. When storing, the metadata service system stores the received metadata in the table in chronological order.

[0089] When the number of tables is multiple, multiple tables can be created according to one or more of the name of the architecture diagram, the creation time, or a custom style name, and the like. For example, the tables can be created according to the custom style name and the creation time, or the tables can be created according to the name of the architecture diagram.

[0090] The process in which the metadata service system stores the first metadata in the metadata database in the first memory of the metadata service system is as follows:

[0091] First, the metadata service system can establish a connection with the metadata database. Specifically, the connection with the metadata database can be established through the host address, port, username, password, and the like of the metadata database.

[0092] Second, the metadata service system can write the first metadata into the first table of the metadata database as a parameter of a SQL statement (for example, an INSERT statement). When inserting the metadata, the metadata can be inserted one by one, or the metadata can be inserted in batches.

[0093] Finally, the metadata service system can disconnect the connection with the metadata database to release resources.

[0094] The metadata service system can store the first metadata in one or more of the personal metadata area, the workspace metadata area, and the acceleration metadata area of the first architecture diagram. The metadata in the personal metadata area can only be used by the user himself / herself, the metadata in the workspace metadata area can only be used by the users belonging to the same workspace, and the metadata in the acceleration metadata area can be provided to the public for use.

[0095] S104: The client sends an acquisition instruction to the metadata service system. Accordingly, the metadata service system receives the acquisition instruction sent by the client.

[0096] S105: The metadata service system acquires the first metadata based on the acquisition instruction.

[0097] The metadata service system acquires the first metadata based on the acquisition instruction, at least including the following two kinds:

[0098] (1) Corresponding to the above, the metadata service system stores the first metadata in the metadata service system in the form of a metadata file in the storage of the metadata service system, and the metadata service system acquires the first metadata based on the acquisition instruction, specifically: the metadata service system scans whether the metadata file in the storage of the metadata service system has data through a file operation interface and method, if there is no data, the metadata service system terminates the process; if there is data, the metadata service system opens the metadata file through the file opening function, and then reads the first metadata from the metadata file through the reading function. Wherein, scanning whether the metadata file in the storage of the metadata service system has data through a file operation interface and method can be realized through the read() method in the file operation interface, when the read content is empty, it means that there is no data in the metadata file, when the read content is not empty, it means that there is data in the metadata file. The reading function can be read() method in Python programming language, read() method in Java programming language, getline() method in C++ programming language, Read() method in C# programming language, readFile() method in JavaScript programming language, fread() function in PHP programming language, etc.

[0099] (2) Corresponding to the above, the metadata service system stores the first metadata in the metadata service system in the form of a metadata file in the storage of the metadata service system, and the metadata service system acquires the first metadata based on the acquisition instruction, specifically: the metadata service system can establish a connection with the metadata database, then the metadata service system can determine whether there is data in the metadata database through a statistical statement (for example, SELECT COUNT), if there is no data, the metadata service system terminates the process; if there is data, the metadata service system reads the first metadata from the metadata database through a selection statement (for example, SELECT statement), and the metadata service system can close the connection with the metadata database.

[0100] S106: The metadata service system applies the first metadata to the second architecture diagram.

[0101] The second architecture diagram can be an architecture diagram that has been designed, partially designed, or just started to be designed. The following will introduce how the metadata service system applies the first metadata to the second architecture diagram when the second architecture diagram is an architecture diagram that has been designed, partially designed, or just started to be designed. The second architecture diagram is similar to the first architecture diagram, and specific descriptions can be found in the foregoing descriptions of the first architecture diagram, which will not be repeated here.

[0102] When the second architecture diagram is an architecture diagram that has been designed, the metadata service system opens the file in which the second architecture diagram is located through the file opening interface, opens the page in which the second architecture diagram is located through the page opening interface, then acquires the second metadata of each graphic element of the second architecture diagram through the metadata interface of the graphic element, modifies the second metadata of each graphic element to the first metadata corresponding to the graphic element in the first architecture diagram, acquires the second metadata of each text of the second architecture diagram through the metadata interface of the text, modifies the second metadata of each text to the first metadata corresponding to the text in the first architecture diagram, acquires the second metadata of each connection line of the second architecture diagram through the metadata interface of the connection line, modifies the second metadata of each connection line to the first metadata corresponding to the connection line in the first architecture diagram, acquires the second metadata of the background of the second architecture diagram through the metadata interface of the background, and modifies the second metadata of the background to the first metadata corresponding to the background in the first architecture diagram.

[0103] When the second architecture diagram is a partially completed design architecture diagram, the metadata service system opens the file in which the second architecture diagram is located through the open file interface, opens the page in which the second architecture diagram is located through the open page interface, then acquires second metadata of each graphic element that has been designed in the second architecture diagram through the metadata interface of the graphic element, modifies the second metadata of each graphic element that has been designed to first metadata corresponding to the graphic element in the first architecture diagram, acquires second metadata of each text that has been designed in the second architecture diagram through the metadata interface of the text, modifies the second metadata of each text that has been designed to first metadata corresponding to the text in the first architecture diagram, acquires second metadata of each connection line that has been designed in the second architecture diagram through the metadata interface of the connection line, modifies the second metadata of each connection line that has been designed to first metadata corresponding to the connection line in the first architecture diagram, and acquires second metadata of a background that has been designed in the second architecture diagram through the metadata interface of the background, and modifies the second metadata of the background that has been designed to first metadata corresponding to the background in the first architecture diagram. Then, when an element needs to be added in the second architecture diagram, the following operations can be performed: when a graphic element needs to be added, metadata of the added graphic element can be set to second metadata through the metadata interface of the graphic element; when a text needs to be added, metadata of the added text can be set to second metadata through the metadata interface of the text; and when a connection line needs to be added, metadata of the added connection line can be set to second metadata through the metadata interface of the connection line. In the above example, the metadata of the background has been set to first metadata, but in actual applications, the background can also not have been set to first metadata, and when a background needs to be added, metadata of the added background can be set to second metadata through the metadata interface of the background.

[0104] When the second architecture diagram is a just-started design architecture diagram, the metadata service system opens the file in which the second architecture diagram is located through the open file interface, opens the page in which the second architecture diagram is located through the open page interface, then, when an element needs to be added in the second architecture diagram, the following operations can be performed: when a graphic element needs to be added, metadata of the added graphic element can be set to second metadata through the metadata interface of the graphic element; when a text needs to be added, metadata of the added text can be set to second metadata through the metadata interface of the text; and when a connection line needs to be added, metadata of the added connection line can be set to second metadata through the metadata interface of the connection line. In the above example, the metadata of the background has been set to first metadata, but in actual applications, the background can also not have been set to first metadata, and when a background needs to be added, metadata of the added background can be set to second metadata through the metadata interface of the background.

[0105] In the above scheme, steps S101 to S106 are all executed as an example for illustration, in actual application, steps S101 to S103 can be used alone as a metadata acquisition method, and steps S104 to S106 can be used alone as a metadata application method, which is not limited here.

[0106] In the above scheme, metadata is extracted from an existing first architecture diagram as an example for illustration, in actual application, the metadata of the architecture diagram can also be directly defined by the user, at this time, the user can input the metadata of the architecture diagram in the configuration interface, and apply the metadata to the architecture diagram which has been designed, partially designed, or just started to design.

[0107] The following will be described with specific examples as an example, how to upload and apply metadata. As shown in Figure 5 Assume that the users include user A, user B, user C and user D, wherein user A is a user of workspace 1 of the design software, user B, user C and user D are all users of workspace 2 of the design software, and an acceleration space can also be provided outside workspace 1 and workspace 2.

[0108] Workspace 1 is provided with workspace metadata area 1, which is used to store the metadata set by each user in workspace 1 or the metadata extracted from the architecture diagram of each user, for example, user A. Workspace 1 is also provided with personal metadata area A, which is used to store the metadata set by user A or the metadata extracted from the architecture diagram drawn by user A.

[0109] Workspace 2 is provided with workspace metadata area 2, which is used to store the metadata set by each user in workspace 2 or the metadata extracted from the architecture diagram of each user, for example, user B, user C and user D. Workspace 2 is also provided with personal metadata area B, which is used to store the metadata set by user B or the metadata extracted from the architecture diagram drawn by user B.

[0110] The acceleration space is a space independent of workspace 1 and workspace 2. The acceleration space is provided with an acceleration metadata area, which is used to store the metadata set by each user of the public or the metadata extracted from the architecture diagram of each user of the public, for example, user A in workspace 1, user B, user C and user D in workspace 2.

[0111] User A uploads first metadata set by user A or extracted from first architecture diagram to personal metadata area A, workspace metadata 1 and acceleration metadata area. User D downloads first metadata from acceleration metadata area and modifies second metadata in second architecture diagram to first metadata. User B uploads third metadata set by user B or extracted from third architecture diagram to personal metadata area B and workspace metadata 2.

[0112] It can be understood that, Figure 5 Examples in the above description are merely specific examples, and in actual applications, other examples can also be used, which are not limited herein.

[0113] Referring to Figure 6 , Figure 6 is a structural schematic diagram of a metadata application device provided by the present application. As shown in Figure 6 , the metadata acquisition device of the present application comprises a receiving module 210, an extraction module 220, a storage module 230 and an application module 240.

[0114] The receiving module 210 is configured to receive an extraction instruction.

[0115] The extraction module 220 is configured to extract first metadata from any one or more of a figure element, a text, a connection line and a background in a first architecture diagram according to the extraction instruction, wherein the any one or more of the figure element, the text, the connection line and the background are elements in the architecture diagram.

[0116] The storage module 230 is configured to store the first metadata.

[0117] The receiving module 210 is configured to receive an extraction instruction.

[0118] The application module 240 is configured to apply the first metadata to any one or more of a figure element, a text, a connection line and a background in a second architecture diagram, wherein the first architecture diagram and the second architecture diagram are different architecture diagrams.

[0119] The receiving module 210, the extraction module 220, the storage module 230 and the application module 240 can be implemented by software or by hardware. For example, the implementation of the extraction module 220 is described as follows. Similarly, the implementation of the receiving module 210, the storage module 230 and the application module 240 can refer to the implementation of the extraction module 220.

[0120] As an example of a software functional unit, the extraction module 220 can include code running on a compute instance. The compute instance can include at least one of a physical host (computing device), a virtual machine, a container. Further, the compute instance can be one or more. For example, the extraction module 220 can include code running on multiple hosts / virtual machines / containers. It is noted that the multiple hosts / virtual machines / containers running the code can be distributed in the same region, or in different regions. Further, the multiple hosts / virtual machines / containers running the code can be distributed in the same availability zone (AZ), or in different AZs, each of which includes one data center or multiple data centers in close geographical proximity. Typically, a region can include multiple AZs.

[0121] Similarly, the multiple hosts / virtual machines / containers running the code can be distributed in the same virtual private cloud (VPC), or in multiple VPCs. Typically, a VPC is set up within a region, and a communication gateway needs to be set up in each VPC for cross-region communication between two VPCs in the same region or between VPCs in different regions, and the interconnection between VPCs is realized through the communication gateway.

[0122] As an example of a hardware functional unit, the extraction module 220 can include at least one computing device, such as a server, etc. Alternatively, the extraction module 220 can also be a device implemented by a central processing unit (CPU), or an application-specific integrated circuit (ASIC), or a programmable logic device (PLD), etc. The PLD can be implemented by a complex programmable logical device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), a data processing unit (DPU), a neural network processing unit (NPU), a system on chip (SoC), an offload card, an acceleration card, or any combination thereof.

[0123] The plurality of computing devices included in the extraction module 220 can be distributed in the same region or in different regions. The plurality of computing devices included in the extraction module 220 can be distributed in the same AZ or in different AZs. Likewise, the plurality of computing devices included in the extraction module 220 can be distributed in the same VPC or in multiple VPCs. Among them, the plurality of computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, DPUs, NPUs, SoCs, offload cards, acceleration cards, etc.

[0124] It should be noted that in other embodiments, the extraction module 220 can be used to perform any step of the metadata application method, the receiving module 210, the storage module 230 and the application module 240 can be used to perform any step of the metadata application method, and the steps responsible for implementation by the extraction module 220, the storage module 230 and the application module 240 can be specified as needed. The entire function of the metadata application device is realized by the receiving module 210, the extraction module 220, the storage module 230 and the application module 240 respectively implementing different steps in the metadata application method.

[0125] It can be understood that the receiving module 210, the extraction module 220 and the storage module 230 can constitute a metadata obtaining device alone, and the receiving module 210 and the application module 240 can also constitute a metadata application device alone, which is not limited here.

[0126] Referring to Figure 7 , Figure 7 is a structural schematic diagram of a metadata system provided by the present application. As Figure 7 shown, the present application also provides a metadata system, as Figure 7 shown, the metadata system comprises:

[0127] The client 310 is configured to send an extraction instruction.

[0128] The metadata service system 320 is configured to extract first metadata from any one or more of the graph elements, text, lines, and background of the first architecture diagram according to the extraction instruction, and store the first metadata.

[0129] The client 310 is configured to send an extraction instruction.

[0130] The metadata service system 320 is configured to extract first metadata from any one or more of the graph elements, text, lines, and background of the first architecture diagram according to the extraction instruction, and store the first metadata.

[0131] The metadata service system 320 and the client 310 can be implemented by software or by hardware. As an example, the implementation of the metadata service system 320 is introduced as follows. Similarly, the implementation of the client 310 can refer to the implementation of the metadata service system 320.

[0132] As an example of the software functional unit, the metadata service system 320 can include code running on a computing instance. The computing instance can be at least one of a physical host (computing device), a virtual machine, a container, and the like. Further, the computing device can be one or more. For example, the metadata service system 320 can include code running on multiple hosts / virtual machines / containers. It should be noted that the multiple hosts / virtual machines / containers for running the application can be distributed in the same region or in different regions. The multiple hosts / virtual machines / containers for running the code can be distributed in the same AZ or in different AZs, and each AZ includes a data center or multiple data centers with similar geographical locations. Generally, one region can include multiple AZs.

[0133] Similarly, the multiple hosts / virtual machines / containers for running the code can be distributed in the same VPC or in multiple VPCs. Generally, one VPC is set in one region. Communication between two VPCs in the same region and between VPCs in different regions requires setting a communication gateway in each VPC to realize the interconnection between VPCs through the communication gateway.

[0134] As an example of the hardware functional unit, the metadata service system 320 can include at least one computing device, such as a server or the like. Alternatively, the metadata service system 320 can also be a device implemented by a CPU, an ASIC, a PLD, a CPLD, an FPGA, a GAL, a DPU, an NPU, a SoC, an offload card, an acceleration card, and the like. The PLD can be implemented by a CPLD, an FPGA, a GAL, or any combination thereof.

[0135] The plurality of computing devices included in the metadata service system 320 can be distributed in the same region or in different regions. The plurality of computing devices included in the metadata service system 320 can be distributed in the same AZ or in different AZs. Similarly, the plurality of computing devices included in the metadata service system 320 can be distributed in the same VPC or in multiple VPCs. The plurality of computing devices can be any combination of servers, ASICs, PLDs, CPLDs, FPGAs, GALs, DPUs, NPUs, SoCs, offload cards, acceleration cards, etc. Alternatively, the metadata service system 320 includes a metadata application device as shown in Figure 6

[0136] The present application also provides a chip system including a processor and a power supply circuit for performing power supply to the processor, and the processor is configured to perform the operation steps corresponding to the metadata application method. For brevity, the details are not repeated here. The processor can be implemented by a GPU, or by a DPU, NPU, XPU, SoC, offload card, acceleration card, etc.

[0137] The present application also provides a computing device 400. As shown in Figure 8 The computing device 400 includes a bus 402, a processor 404, a memory 406, and a communication interface 408. The processor 404, the memory 406, and the communication interface 408 communicate with each other through the bus 402. The computing device 400 can be a server or a terminal device. It should be understood that the present application does not limit the number of processors and memories in the computing device 400.

[0138] The bus 402 can be a peripheral component interconnect Express (PCIe) bus or an extended industry standard architecture (EISA) bus, a unified bus (Ubus or UB), a compute express link (CXL), a cache coherent interconnect for accelerators (CCIX), etc. The unified bus is also known as a versatile bus. The bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 ​The bus 402 is represented in the figure as a single bus, but it can comprise different buses or lines, of different types of technologies, that are interconnected to each other. The bus 402 can comprise a path for transferring information between the different components of the computing device 400 (e.g., the memory 406, the processor 404, the communication interface 408). Among others, the unified bus can also be referred to as a system bus.

[0139] The processor 404 can comprise any one or more of a central processing unit (CPU), a graphics processing unit (GPU), a microprocessor (MP), or a digital signal processor (DSP), an ASIC, a FPGA, a CPLD, an NPU, a SoC, an offload card, an acceleration card, or any other processing device.

[0140] The memory 406 can comprise a volatile memory, such as a random access memory (RAM) including a dynamic or static RAM. The processor 404 can also include a non-volatile memory, such as a read-only memory (ROM), a flash memory, a hard disk drive (HDD) or a solid-state drive (SSD). In addition, the memory 406 can also be implemented by a storage class memory (SCM), a phase change memory (PCM), or other types of storage media.

[0141] It is worth mentioning that the same type of storage medium can be configured to implement the function of the memory 406 in the same computing device, or two or more types of storage media can be configured to implement the function of the memory 406, which is not limited in the present application.

[0142] The memory 406 stores executable program code, and the processor 404 executes the executable program code to respectively implement the functions of the aforementioned receiving module 210, the extracting module 220, the storing module 230, and the application module 240, so as to implement the metadata obtaining method or the metadata application method. That is, the memory 406 stores instructions for executing the metadata obtaining method or the metadata application method.

[0143] Alternatively, the memory 406 may store executable code, which the processor 404 executes to implement the functions of the aforementioned metadata service system 320 and client 310, thereby realizing the metadata acquisition method or the metadata application method. That is, the memory 406 stores instructions for executing the metadata acquisition method or the metadata application method.

[0144] The communication interface 408 uses transceiver modules such as, but not limited to, network interface cards and transceivers to enable communication between the computing device 400 and other devices or communication networks.

[0145] As one possible implementation, the computing device 400 may also include a chip system, which includes a processor and a power supply circuit. The power supply circuit supplies power to the processor, and the processor executes the operation steps corresponding to the metadata acquisition method or the metadata application method. For simplicity, further details are omitted here. The processor can be implemented using a GPU, or it can be implemented using computing devices or AI chips such as a DPU, NPU, XPU, SoC, offloading card, or accelerator card.

[0146] As one possible implementation, the computing device 400 may include multiple types of processors 404, meaning the computing device 400 is a heterogeneous device. For example, the computing device 400 may include a CPU and a GPU, and at least one of the processors 404 may execute the operation steps corresponding to the metadata acquisition method or the metadata application method. For the sake of brevity, further details will not be elaborated here.

[0147] This application also provides a computing device cluster. The computing device cluster includes at least one computing device. The computing device can be a server, such as a central server, an edge server, or a local server in a local data center. In some embodiments, the computing device can also be a terminal device such as a desktop computer, a laptop computer, or a smartphone.

[0148] like Figure 9 As shown, the computing device cluster includes at least one computing device 400. The memory 406 of one or more computing devices 400 in the computing device cluster may store the same instructions for executing metadata retrieval methods or metadata application methods.

[0149] In some possible implementations, the memory 406 of one or more computing devices 400 in the computing device cluster may also store partial instructions for executing metadata acquisition methods or metadata application methods. In other words, a combination of one or more computing devices 400 can jointly execute the instructions for executing metadata acquisition methods or metadata application methods.

[0150] It should be noted that the memories 406 in different computing devices 400 in the computing device cluster can store different instructions for performing part of the functions of the metadata service system 320, respectively. That is, the memories 406 in different computing devices 400 store instructions that can implement the functions of one or more of the receiving module 210, the extracting module 220, the storing module 230, and the applying module 240.

[0151] In some possible implementation manners, one or more computing devices in the computing device cluster can be connected through a network. The network can be a wide area network or a local area network, etc. Figure 10 A possible implementation manner is shown. As shown in Figure 10 The two computing devices 400A and 400B are connected through a network. Specifically, the computing devices are connected to the network through the communication interfaces in the computing devices. In this type of possible implementation manner, the memory 406 in the computing device 400A stores instructions for performing the functions of the extracting module 220. Meanwhile, the memory 406 in the computing device 400B stores instructions for performing the functions of the receiving module 210, the storing module 230, and the applying module 240.

[0152] Figure 10 The connection manner between the computing device cluster shown in the figure can be that, considering that the metadata obtaining method and the metadata applying method provided in the present application need to store a large amount of data and perform a large amount of computation, the functions implemented by the receiving module 210, the storing module 230, and the applying module 240 are performed by the computing device 400B.

[0153] It should be understood that Figure 10 The functions of the computing device 400A shown in the figure can also be performed by multiple computing devices 400. Similarly, the functions of the computing device 400B can also be performed by multiple computing devices 400.

[0154] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection manner of the computing device cluster Figure 9 and Figure 10 The connection manner of the computing device cluster. The difference is that the memories 406 in one or more computing devices 400 in the computing device cluster can store the same instructions for performing.

[0155] In some possible implementation manners, the memories 406 in one or more computing devices 400 in the computing device cluster can also respectively store part of the instructions for performing the metadata applying method and the metadata obtaining method. In other words, the combination of one or more computing devices 400 can collectively perform the instructions for performing the metadata applying method and the metadata obtaining method. In some possible implementation manners, one or more computing devices in the computing device cluster can be connected through a network. The network can be a wide area network or a local area network, etc. Figure 10 A possible implementation manner is shown. As shown in Figure 10 The two computing devices 400A and 400B are connected through a network. Specifically, the computing devices are connected to the network through the communication interfaces in the computing devices. In this type of possible implementation manner, the memory 406 in the computing device 400A stores instructions for performing the functions of the extracting module 220. Meanwhile, the memory 406 in the computing device 400B stores instructions for performing the functions of the receiving module 210, the storing module 230, and the applying module 240.

[0152] Figure 10 The connection manner between the computing device cluster shown in the figure can be that, considering that the metadata obtaining method and the metadata applying method provided in the present application need to store a large amount of data and perform a large amount of computation, the functions implemented by the receiving module 210, the storing module 230, and the applying module 240 are performed by the computing device 400B.

[0153] It should be understood that Figure 10 The functions of the computing device 400A shown in the figure can also be performed by multiple computing devices 400. Similarly, the functions of the computing device 400B can also be performed by multiple computing devices 400.

[0154] The present application embodiment also provides another computing device cluster. The connection relationship between the computing devices in the computing device cluster can be similar to the connection manner of the computing device cluster Figure 9 and Figure 10 The connection manner of the computing device cluster. The difference is that the memories 406 in one or more computing devices 400 in the computing device cluster can store the same instructions for performing.

[0155] In some possible implementation manners, the memories 406 in one or more computing devices 400 in the computing device cluster can also respectively store part of the instructions for performing the metadata applying method and the metadata obtaining method. In other words, the combination of one or more computing devices 400 can collectively perform the instructions for performing the metadata applying method and the metadata obtaining method.

[0156] It should be noted that the memories 406 in different computing devices 400 in the computing device cluster can store different instructions for performing part of the functions of the metadata system. That is, the memories 406 in different computing devices 400 store instructions that can implement the functions of the metadata service system 320, one or more of the devices in the client 310.

[0157] Embodiments of the present application also provide a computer program product containing instructions. The computer program product can be a software or program product containing instructions, which can be run on a computing device or stored in any available medium. When the computer program product is run on at least one computing device, the at least one computing device is caused to perform the metadata application method or the metadata obtaining method.

[0158] Embodiments of the present application also provide a computer readable storage medium. The computer readable storage medium can be any available medium or data storage device that can be accessed by a computing device or a data center containing one or more available media. The available medium can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk), etc. The computer readable storage medium contains instructions that instruct the computing device to perform the XXX method, or instruct the computing device to perform the metadata application method or the metadata obtaining method.

[0159] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those of ordinary skill in the art should understand that they can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacements to some of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the protection scope of the technical solutions of the embodiments of the present application.

Claims

1. A method for applying metadata, characterized in that, include: Receive an extraction instruction, and extract first metadata from any one or more of the graphic elements, text, lines, and background of the first architecture diagram according to the extraction instruction, wherein any one or more of the graphic elements, text, lines, and background are elements in the architecture diagram; Store the first metadata; Receive an acquisition instruction and acquire the first metadata according to the acquisition instruction; The first metadata is applied to any one or more of the elements, text, lines, and background in the second architecture diagram, wherein the first architecture diagram and the second architecture diagram are different architecture diagrams.

2. The method according to claim 1, characterized in that, The first metadata of the first architecture diagram is stored, including: The first metadata of the first architecture diagram is stored in any one or more of the personal metadata area, workspace metadata area and acceleration metadata area corresponding to the first user of the first architecture diagram; The first metadata is obtained according to the acquisition instruction, including: The first metadata is obtained from any one of the personal metadata area, the workspace metadata area, and the acceleration metadata area; The personal metadata area is used to store metadata set by the first user or metadata extracted from the first architecture diagram drawn by the first user. The workspace metadata area is used to store metadata set by each user in the workspace where the first user is located or metadata extracted from the architecture diagram drawn by each user in the workspace. The acceleration metadata area is used to store metadata set by each user in the public, including the first user, or metadata extracted from the architecture diagram drawn by each user in the public.

3. The method according to claim 2, characterized in that, In the case that the first metadata is obtained from the personal metadata area, the first architecture diagram and the second architecture diagram are drawn by the first user; When the first metadata is obtained from the workspace metadata area, the first architecture diagram is drawn by the first user, the second architecture diagram is drawn by the second user, and the first user and the second user belong to the same workspace; In the case where the first metadata is obtained from the accelerated metadata area, the first architecture diagram is drawn by the first user, the second architecture diagram is drawn by the third user, and the first user and the third user do not belong to the same workspace.

4. The method according to any one of claims 1 to 3, characterized in that, Applying the first metadata to the second architecture diagram includes: Modify the second metadata in the second architecture diagram to the first metadata.

5. The method according to claim 1 or 3, characterized in that, Applying the first metadata to the second architecture diagram includes: Set any one of the newly added elements, text, lines, or background metadata in the second architecture diagram as the second metadata.

6. The method according to any one of claims 1 to 5, characterized in that, The first metadata includes line size, line type, line color, subscript color, background color, fill pattern, size, whether it has a shadow, transparency, rounded corner preset, 3D rotation, font, font size, bold, underline, text position, font color, background color, background image, background color, and whether it includes any one or more of the following: grid lines.

7. A method for obtaining metadata, characterized in that, Receive an extraction instruction, and extract first metadata from any one or more of the elements, text, lines, and background of the first architecture diagram according to the extraction instruction; Store the first metadata.

8. A method for applying metadata, characterized in that, include: Receive an acquisition instruction, and acquire first metadata according to the acquisition instruction, wherein the first metadata includes any one or more of the metadata of graphic elements, text, lines, and background, and any one or more of the graphic elements, text, lines, and background are elements in the architecture diagram; Apply the first metadata to any one or more of the elements, text, lines, and background in the second architecture diagram.

9. The method according to claim 8, characterized in that, The method further includes: Receive an extraction instruction, and extract first metadata from any one or more of the elements, text, lines, and background of the first architecture diagram according to the extraction instruction; The first metadata of the first architecture diagram is stored, wherein the first architecture diagram and the second architecture diagram are different architecture diagrams.

10. The method according to claim 8, characterized in that, The method further includes: Receive the initial metadata set by the user; Store the first metadata.

11. A method for applying metadata, characterized in that, include: Receive an extraction instruction, and extract first metadata from any one or more of the graphic elements, text, lines, and background of the first architecture diagram according to the extraction instruction, wherein any one or more of the graphic elements, text, lines, and background are elements in the architecture diagram; Store the first metadata; Receive an acquisition instruction and acquire the first metadata according to the acquisition instruction; The first metadata is applied to any one or more of the elements, text, lines, and background in the second architecture diagram, wherein the first architecture diagram and the second architecture diagram are different architecture diagrams.

12. A metadata acquisition device, characterized in that, The device includes: The receiving module is used to receive extraction instructions and extract first metadata from any one or more of the graphic elements, text, lines, and background of the first architecture diagram according to the extraction instructions; A storage module is used to store the first metadata.

13. A metadata application device, characterized in that, The device includes: The receiving module is used to receive an acquisition instruction and acquire first metadata according to the acquisition instruction. The first metadata includes one or more of the following metadata: graphic elements, text, lines, and background. The graphic elements, text, lines, and background are elements in the architecture diagram. The application module is used to apply the first metadata to any one or more of the graphic elements, text, lines, and backgrounds in the second architecture diagram.

14. A metadata system, characterized in that, The system includes: The client is used to send extraction commands; The metadata service system is used to extract first metadata from any one or more of the graphic elements, text, lines, and background of the first architecture diagram according to the extraction instructions, and to store the first metadata. The client is used to send acquisition commands; The metadata service system is used to obtain first metadata according to the acquisition instruction, and apply the first metadata to any one or more of the graphic elements, text, lines, and backgrounds in the second architecture diagram, wherein the first architecture diagram and the second architecture diagram are different architecture diagrams.

15. A chip system, characterized in that, The chip system includes a processor and a power supply circuit, the power supply circuit being used to supply power to the processor, the processor being used to perform the operation steps of the method as described in any one of claims 1 to 11.

16. A computing device, characterized in that, The computing device includes a processor and memory; The processor is configured to execute instructions stored in the memory to cause the computing device to perform the operational steps of the method as described in any one of claims 1 to 11.

17. A computing device cluster, characterized in that, It includes at least one computing device, each computing device including a processor and memory; The processor of the at least one computing device is configured to execute instructions stored in the memory of the at least one computing device to cause the cluster of computing devices to perform the operational steps of the method as described in any one of claims 1 to 11.

18. A computer program product containing instructions, characterized in that, When the instruction is executed by the computing device cluster, the computing device cluster causes the computing device cluster to perform the operation steps of the method as described in any one of claims 1 to 11.

19. A computer-readable storage medium, characterized in that, It includes computer program instructions, which, when executed by a cluster of computing devices, perform the operational steps of the method as described in any one of claims 1 to 11.

Images