CIM metadata collection method, computing service equipment and computer program product

Abstract

The present application discloses a CIM metadata collection method, computing service equipment, and computer program product, relating to the field of CIM technology. The method is applied to a CIM metadata management system and includes: upon detecting a CIM metadata collection instruction, extracting the metadata items to be collected and the target CIM data source from the CIM metadata collection instruction; determining the target collection rules corresponding to the metadata items to be collected based on the metadata items to be collected, the target CIM data source, and a preset CIM metadata collection rule library; and collecting the CIM metadata corresponding to the metadata items to be collected from the target CIM data source according to the target collection rules. The present application can eliminate the need to wait for programmers to develop new scripts or maintain and update old scripts when the business requirements for CIM metadata collection change.

Description

Technical Field

[0001] The present application relates to the field of CIM technology, and in particular to a CIM metadata collection method, a computing service device, and a computer program product. Background Art

[0002] With the development of smart city construction, the importance of City Information Modeling (CIM) as a bridge between the physical and digital worlds has become increasingly prominent. CIM not only integrates a city's geospatial information but also encompasses heterogeneous data from multiple sources, including buildings, infrastructure, and public services. CIM metadata accurately and comprehensively describes CIM data's source, format, version, and update time, enabling it to be correctly understood, effectively shared, and maintained over the long term. Therefore, efficient metadata collection is fundamental to building a reliable and scalable urban information platform.

[0003] At present, the metadata collection of CIM (City Information Modeling) mainly relies on programmers to customize and develop scripts for the required metadata items based on the business needs of metadata collection, thereby realizing the automated collection of CIM metadata.

[0004] However, this approach usually requires programmers to intervene when business needs change, develop new scripts for new business needs or maintain and update old scripts, and cannot respond to CIM metadata collection business in a timely manner. Summary of the Invention

[0005] The main purpose of this application is to provide a CIM metadata collection method, computing service equipment and computer program product, aiming to solve the technical problem in related technologies that when the business requirements of CIM metadata collection change, it is necessary to wait for the development of new scripts or maintenance and update of old scripts, resulting in slow response speed.

[0006] To achieve the above objectives, the present application provides a CIM metadata collection method, which is applied to a CIM metadata management system and includes:

[0007] After detecting the CIM metadata collection instruction, extracting the metadata items to be collected and the target CIM data source from the CIM metadata collection instruction;

[0008] Determining a target collection rule corresponding to the metadata item to be collected based on the metadata item to be collected, the target CIM data source, and a preset CIM metadata collection rule library;

[0009] According to the target collection rule, CIM metadata corresponding to the metadata item to be collected is collected from the target CIM data source.

[0010] In one embodiment, the step of determining a target collection rule corresponding to the metadata item to be collected based on the metadata item to be collected, the target CIM data source, and a preset CIM metadata collection rule library includes:

[0011] Determining, from a plurality of preset CIM metadata collection rule bases, a CIM metadata collection rule base that matches the data source type of the target CIM data source as a target rule base;

[0012] Based on the target rule library, a target collection rule corresponding to the metadata item to be collected is determined.

[0013] In one embodiment, the step of determining the target collection rule corresponding to the metadata item to be collected based on the target rule library includes:

[0014] Determining the metadata layer of the metadata item to be collected according to the data source type of the target CIM data source;

[0015] Determining, from the target rule library, a CIM metadata collection rule that matches the metadata layer as a first collection rule to be adjusted;

[0016] According to the metadata item to be collected, the metadata item is adjusted for the first collection rule to be adjusted to obtain a target collection rule.

[0017] In one embodiment, the step of determining target CIM metadata collection rules based on the metadata items to be collected, the target CIM data source, and a preset CIM metadata rule base includes:

[0018] Determining, from a preset CIM metadata collection rule library, a CIM metadata collection rule that matches the metadata item to be collected as a second collection rule to be adjusted;

[0019] According to the data source type of the target CIM data source, the data source type of the second collection rule to be adjusted is adjusted to obtain the target collection rule.

[0020] In one embodiment, the step of determining target CIM metadata collection rules based on the metadata items to be collected, the target CIM data source, and a preset CIM metadata rule base includes:

[0021] Determining the metadata layer of the metadata item to be collected according to the data source type of the target CIM data source;

[0022] Determining, from a preset CIM metadata collection rule library, a CIM metadata collection rule that matches the metadata layer as a third collection rule to be adjusted;

[0023] According to the metadata item to be collected, adjusting the metadata item of the third collection rule to be adjusted to obtain a fourth collection rule to be adjusted;

[0024] According to the data source type of the target CIM data source, the data source type of the fourth collection rule to be adjusted is adjusted to obtain a target collection rule.

[0025] In one embodiment, the CIM metadata management system includes a CIM metadata extension module, and the method further includes:

[0026] After detecting a CIM metadata extension instruction for a target metadata set, extracting metadata items to be extended and a target extension method from the CIM metadata extension instruction, wherein the target extension method is manual editing, data mining, or internal system data synchronization;

[0027] The extended metadata corresponding to the metadata item to be extended is acquired through the target extension method, and the extended metadata is updated into the target metadata set.

[0028] In one embodiment, the CIM metadata management system includes a CIM metadata collection plan page, and the method further includes:

[0029] Acquire a CIM metadata collection plan developed through the CIM metadata collection plan page, wherein the CIM metadata collection plan includes metadata items to be collected, target CIM data sources, and a collection period;

[0030] According to the collection cycle, a CIM metadata collection instruction for collecting metadata for the metadata items to be collected in the target CIM data source is regularly generated.

[0031] In one embodiment, the CIM metadata management system includes a CIM metadata visualization module, and the method further includes:

[0032] After detecting the CIM metadata visualization instruction for the target metadata set, the CIM metadata visualization module constructs a knowledge graph for the target metadata set, and visualizes the constructed knowledge graph.

[0033] In addition, to achieve the above-mentioned purpose, the present application also provides a computing service device, which includes: a memory, a processor, and a computer program stored on the memory and executable on the processor. When the computer program is executed by the processor, the steps of the CIM metadata collection method as described above are implemented.

[0034] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program. When the computer program is executed by a processor, it implements the steps of the CIM metadata collection method as described above.

[0035] The present application provides a CIM metadata collection method, computing service device, and computer program product, relating to the field of CIM technology. The method is applied to a CIM metadata management system. After detecting a CIM metadata collection instruction, the method extracts metadata items to be collected and a target CIM data source from the CIM metadata collection instruction. Then, based on the metadata items to be collected, the target CIM data source, and a preset CIM metadata collection rule library, the method determines a target collection rule corresponding to the metadata items to be collected. Finally, based on the target collection rule, the CIM metadata corresponding to the metadata items to be collected is collected from the target CIM data source. This method enables the method to automatically select appropriate CIM metadata collection rules from the preset CIM metadata collection rule library based on changing CIM metadata collection business requirements to meet metadata item collection tasks that meet new business requirements. This method eliminates the need for programmer intervention and the need to wait for new script development or maintenance and updates of old scripts. It can promptly respond to new business requirements and quickly complete metadata collection tasks, thereby resolving the technical problem in related technologies of slow response times caused by the need to wait for new script development or maintenance and updates of old scripts when business requirements for CIM metadata collection change. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present application and, together with the description, serve to explain the principles of the present application.

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

[0038] Figure 1 Schematic diagram of the process of collecting CIM metadata in an embodiment of the present application;

[0039] Figure 2 This is a schematic diagram of the first process for determining target acquisition rules in an embodiment of the present application;

[0040] Figure 3 This is a schematic diagram of the adjustment process of the collection rules in the embodiment of the present application;

[0041] Figure 4 This is a schematic diagram of a second process for determining target acquisition rules in an embodiment of the present application;

[0042] Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the CIM metadata collection method in the embodiment of the present application.

[0043] The purpose, features and advantages of this application will be further explained with reference to the accompanying drawings in conjunction with the embodiments. DETAILED DESCRIPTION

[0044] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all embodiments consistent with the present application. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present application, as detailed in the appended claims.

[0045] It should be understood that the specific embodiments described herein are merely used to explain the technical solutions of the present application and are not intended to limit the present application.

[0046] At present, the metadata collection of CIM (City Information Modeling) mainly relies on programmers to customize and develop scripts for the required metadata items based on the business needs of metadata collection, thereby realizing the automated collection of CIM metadata.

[0047] However, this approach usually requires programmers to intervene when business needs change, develop new scripts for new business needs or maintain and update old scripts, and cannot respond to CIM metadata collection business in a timely manner.

[0048] The main solution of this application is a CIM metadata collection method, which is applied to a CIM metadata management system and includes: upon detecting a CIM metadata collection instruction, extracting a metadata item to be collected and a target CIM data source from the CIM metadata collection instruction; determining a target collection rule corresponding to the metadata item to be collected based on the metadata item to be collected, the target CIM data source, and a preset CIM metadata collection rule library; and collecting CIM metadata corresponding to the metadata item to be collected from the target CIM data source according to the target collection rule.

[0049] This application can automatically select appropriate CIM metadata collection rules from a preset CIM metadata collection rule library according to the changing business needs of CIM metadata collection, and use them to meet the metadata item collection tasks of the new business needs. This eliminates the need for programmer intervention and the need to wait for the development of new scripts or the maintenance and update of old scripts. It can respond to new business needs in a timely manner and quickly complete metadata collection work, thereby solving the technical problem in related technologies that when the business needs of CIM metadata collection change, it is necessary to wait for the development of new scripts or the maintenance and update of old scripts, resulting in slow response speed.

[0050] In order to better understand the technical solution of the present application, a detailed description will be given below in conjunction with the accompanying drawings and specific implementation methods.

[0051] Please refer to Figure 1 , Figure 1 Schematic diagram of the process of collecting CIM metadata in an embodiment of the present application.

[0052] In this embodiment, the CIM metadata collection method is applied to the CIM metadata management system. The method includes steps S100 to S300:

[0053] Step S100: After detecting a CIM metadata collection instruction, extract the metadata items to be collected and the target CIM data source from the CIM metadata collection instruction;

[0054] It should be noted that the CIM metadata collection instruction is a command used to trigger the CIM metadata management system to start executing the CIM metadata collection task. The metadata items to be collected refer to the metadata items to be collected, and the target CIM data source refers to the CIM data source to be collected.

[0055] It is easy to understand that the CIM metadata collection instruction can specify and trigger the CIM metadata management system to collect metadata for specific metadata items in a CIM data source by limiting the metadata items to be collected and the target CIM data source.

[0056] In this embodiment, the CIM metadata instruction may be an operation from a user interface, or may be generated by other automated processes.

[0057] For example, in a feasible implementation, the CIM metadata management system includes a CIM metadata collection plan page, and the method further includes steps A10 to A20:

[0058] Step A10: Acquire a CIM metadata collection plan developed through the CIM metadata collection plan page, wherein the CIM metadata collection plan includes metadata items to be collected, target CIM data sources, and a collection period;

[0059] It should be noted that the CIM metadata collection plan page is a user interface or tool within the CIM metadata management system that allows business personnel to develop detailed CIM metadata collection plans. It provides a graphical or form-based operating environment, allowing users to easily specify metadata items to be collected, select target CIM data sources, and set parameters such as the collection cycle. A CIM metadata collection plan is a specific task profile created by business personnel using the CIM metadata collection plan page. This CIM metadata collection plan details which metadata items to collect from which CIM data source, as well as the collection schedule (e.g., daily, weekly, or monthly).

[0060] This implementation introduces a CIM metadata collection plan page, allowing business personnel to easily create and manage complex collection plans without requiring programming knowledge. This intuitive interface design significantly lowers the barrier to entry and improves the system's usability and accessibility.

[0061] In this embodiment, business personnel can flexibly adjust the various parameters of the collection plan according to specific needs, including the selection of metadata items to be collected, the designation of the target CIM data source, and the setting of the collection cycle, to ensure that each collection can meet the current business needs while avoiding unnecessary waste of resources.

[0062] Step A20 : regularly generating CIM metadata collection instructions for collecting metadata from metadata items to be collected in the target CIM data source according to the collection cycle.

[0063] In this implementation, the CIM metadata management system automatically triggers the generation of CIM metadata collection instructions based on a pre-set collection cycle, without requiring manual intervention. This approach not only ensures timely data updates but also reduces the potential for errors associated with manual operations, improving overall reliability and stability.

[0064] In this implementation, by regularly executing collection tasks, the CIM metadata management system can continuously track and update the metadata in the city information model, ensuring that the data used is up-to-date and accurate. This is crucial for supporting the long-term development of smart city projects.

[0065] Furthermore, setting a reasonable collection cycle can help optimize system resource usage and avoid excessive computing resources being used during unnecessary periods. Furthermore, business personnel can dynamically adjust the collection cycle for each metadata item to be collected from each CIM data source based on actual needs to accommodate different business scenarios and load conditions.

[0066] Step S200: determining a target collection rule corresponding to the metadata item to be collected based on the metadata item to be collected, the target CIM data source, and a preset CIM metadata collection rule library;

[0067] It should be noted that the CIM metadata collection rule base is a collection of rules that guide the CIM metadata management system in metadata collection under various scenarios. These rules cover how to parse data in specific formats, which fields should be prioritized, and error handling mechanisms.

[0068] Through the rules stored in the CIM metadata collection rule library, the CIM metadata management system can clearly determine how to collect metadata corresponding to the metadata items to be collected from the target CIM data source, thereby automatically executing the metadata collection task for the metadata items to be collected in the target CIM data source, without the need for programmers to intervene to redevelop new scripts or maintain and update old scripts when business needs change.

[0069] It should also be noted that the target collection rule is a rule for guiding the CIM metadata management system on how to collect metadata corresponding to the metadata item to be collected from the target CIM data source.

[0070] In this embodiment, after external data is connected to the CIM platform, it is stored in different data sources within the CIM platform based on its source. For example, external data from an external MySQL database is stored within the CIM platform's internal MySQL database after being connected to the CIM platform. This ensures efficient and consistent CIM data access, while maintaining consistency in data structure and semantics. Therefore, in this embodiment, the CIM platform internally stores multiple data sources, including data in different formats.

[0071] This embodiment predefines metadata items that can be directly collected from each data source, and layers the metadata items to determine the metadata layer to which each metadata item belongs in each data source.

[0072] For example, for relational database data sources, such as MySQL and PostgreSQL, metadata items can be divided into the database layer, data table layer, field layer, and record layer. For spatiotemporal database data sources, such as Hive, metadata items can be divided into the database layer, data table layer, field layer, record layer, and spatiotemporal data item layer. For file system data sources, such as HDFS (Hadoop Distributed File System), metadata items can be divided into the folder layer, file layer, and spatiotemporal data item layer. For external third-party system data sources, such as OGC (Open Geospatial Consortium), metadata items can be divided into API (Application Programming Interface) groups, API layer, and spatiotemporal data item layer.

[0073] In this embodiment, the target CIM data source can be a relational database, a spatiotemporal database, or an external third-party system. For each data source type, this embodiment determines the metadata layer to which each predefined metadata item belongs. For metadata items within the same metadata layer, the collection rules are generally consistent. A general collection rule can be designed as a template. This template can then be adaptively modified based on the actual metadata item (also known as metadata item adjustment) to obtain a collection rule that can collect the metadata item from that data source type. Based on the specific data source, an appropriate collection method (also known as data source type adjustment) is then selected to implement the collection rule, such as SQL statements, SDKs, or API requests.

[0074] It is understandable that, taking MySQL and PostgreSQL as examples, when selecting the appropriate collection method, although both use SQL statements for querying, since the specific SQL implementations of the two databases are different, when adjusting the data source type in this embodiment, the final SQL statement determined for the same metadata item may be different.

[0075] In this embodiment, the programmer predefines the metadata items that can be collected from each data source, divides the metadata into layers, and then designs a general collection rule for each metadata layer in each type of data source.

[0076] After obtaining the general collection rules corresponding to each metadata layer in each type of data source, in a first feasible implementation method, the general collection rules can be directly stored as CIM metadata collection rules in a preset CIM metadata collection rule library. Then, based on the metadata layer of the metadata item to be collected and the data source type of the target CIM data source, the general collection rules applicable to this metadata collection are determined from the CIM metadata collection rule library. The general collection rules are then adaptively adjusted so that they can effectively guide the CIM metadata management system on how to collect CIM metadata corresponding to the metadata item to be collected from the target CIM data source.

[0077] Through this implementation, programmers only need to design general collection rules for each metadata layer in various data sources, and provide logic for adaptively adjusting the general rules based on the metadata layer of the metadata items to be collected and the data source type of the target CIM data source. The CIM metadata management system can then automatically realize the dynamic generation of target collection rules, greatly reducing the workload of programming development. Moreover, when new undefined metadata items need to be included in the system, it is only necessary to set the metadata layer to which they belong in various data sources. The system can then realize the collection task of the metadata item under the original box selection.

[0078] In a second feasible implementation, it is also possible to directly define the collection rules for each metadata item from each CIM data source and store them in a preset CIM metadata collection rule library. Then, based on the identifier of the metadata item to be collected and the identifier of the target CIM data source, the corresponding target collection rule is matched from the CIM metadata collection rules.

[0079] Through this embodiment, the CIM metadata management system does not need to adaptively adjust the collection rules, but directly matches the target collection rules and then applies the target collection rules to perform the corresponding CIM metadata collection operation, which makes the overall response faster.

[0080] In one example, if Figure 2 As shown, step S200 may include steps S210 to S220:

[0081] Step S210: From a plurality of preset CIM metadata collection rule bases, a CIM metadata collection rule base that matches the data source type of the target CIM data source is determined as a target rule base;

[0082] Step S220: determining the target collection rule corresponding to the metadata item to be collected based on the target rule library.

[0083] In this embodiment, a CIM metadata collection rule library is pre-set for each of the four types of data sources: relational databases, spatiotemporal databases, file systems, and external third-party systems. The CIM metadata collection rules corresponding to each type are stored in each library. Then, in actual application, the target CIM data source is first determined to be of one of the four types based on its data source type. For example, if the target CIM data source is of MySQL type, it is determined to be a relational database. The CIM metadata collection rule library corresponding to the relational database is selected as the target rule library, and the CIM metadata collection rules matching the metadata items to be collected are obtained from the target rule library.

[0084] It's easy to understand that when the target rule base stores general collection rules, it's necessary to adapt the general collection rules to a template and make adaptive adjustments to obtain target collection rules that truly guide the CIM metadata management system on how to collect CIM metadata corresponding to the metadata item to be collected from the target CIM data source. On the other hand, when the target rule base stores collection rules that specifically guide the CIM metadata management system on how to collect CIM metadata corresponding to a specific metadata item from a specific data source, it's necessary to identify the target collection rule from the target rule base based on both the identifier of the metadata item to be collected and the data source type (or identifier) ​​of the target CIM data source.

[0085] Specifically, if Figure 3 As shown, step S220 may include steps S221 to S223:

[0086] Step S221 , determining the metadata layer of the metadata item to be collected according to the data source type of the target CIM data source;

[0087] Step S222: From the target rule library, determine the CIM metadata collection rule that matches the metadata layer as the first collection rule to be adjusted;

[0088] Step S223 : According to the metadata items to be collected, the metadata items are adjusted for the first collection rule to be adjusted to obtain the target collection rule.

[0089] In this example, the target rule library stores general collection rules. Therefore, it is necessary to first determine which of the four types of data sources the target CIM data source belongs to based on its data source type, thereby determining the metadata layer to which the metadata item to be collected belongs in this type of data source. Then, the CIM metadata collection rule that matches the metadata layer in the target rule library is determined as the first collection rule to be adjusted. Then, the metadata item is adjusted, that is, the metadata item name, identifier and other information in the collection rule are replaced to obtain the final target collection rule.

[0090] In another example, Figure 4 As shown, step S200 may further include steps S230 to S240:

[0091] Step S230: Determine, from a preset CIM metadata collection rule library, a CIM metadata collection rule that matches the metadata item to be collected as a second collection rule to be adjusted;

[0092] Step S240 : adjusting the data source type of the second collection rule to be adjusted according to the data source type of the target CIM data source to obtain the target collection rule.

[0093] In this example, the CIM metadata collection rules stored in the CIM metadata collection rule library can specify how the CIM metadata management system collects metadata corresponding to specific metadata items from a certain type of data source. Therefore, it is only necessary to adjust the data source type to make it compatible with the target CIM data source, that is, to clarify the specific SQL query statements, API requests, etc., and to clarify how to convert the returned metadata format.

[0094] In another example, step S200 may further include steps S250 to S280:

[0095] Step S250 , determining the metadata layer of the metadata item to be collected according to the data source type of the target CIM data source;

[0096] Step S260: Determine, from a preset CIM metadata collection rule library, a CIM metadata collection rule that matches the metadata layer as a third collection rule to be adjusted;

[0097] Step S270: Adjust the metadata item of the third collection rule to be adjusted according to the metadata item to be collected, to obtain a fourth collection rule to be adjusted;

[0098] Step S280 : adjusting the data source type of the fourth collection rule to be adjusted according to the data source type of the target CIM data source to obtain the target collection rule.

[0099] In this example, the CIM metadata collection rules stored in the CIM metadata collection rule library are general collection rules. Therefore, it is necessary to first determine the metadata layer of the metadata item to be collected, and then obtain the general collection rules corresponding to the metadata layer from the CIM metadata collection rule library. Then, adjust the metadata items and data source types in sequence to obtain the final target collection rules.

[0100] Step S300 collects CIM metadata corresponding to the metadata item to be collected from the target CIM data source according to the target collection rule.

[0101] In this embodiment, after determining the target collection rule, the CIM metadata management system can automatically collect CIM metadata items corresponding to the metadata items to be collected from the target CIM data source based on the target collection rule, and complete the corresponding CIM metadata collection task.

[0102] After detecting a CIM metadata collection instruction, this embodiment extracts the metadata item to be collected and the target CIM data source from the CIM metadata collection instruction. Then, based on the metadata item to be collected, the target CIM data source, and a preset CIM metadata collection rule library, it determines the target collection rule corresponding to the metadata item to be collected. Finally, based on the target collection rule, it collects CIM metadata corresponding to the metadata item to be collected from the target CIM data source. This allows the present application to automatically select appropriate CIM metadata collection rules from the preset CIM metadata collection rule library based on changing CIM metadata collection business requirements to meet metadata item collection tasks that meet new business requirements. This eliminates the need for programmer intervention and the need to wait for the development of new scripts or the maintenance and update of old scripts. New business requirements can be promptly responded to and metadata collection can be quickly completed. This addresses the technical problem in related technologies where, when business requirements for CIM metadata collection change, the need to wait for the development of new scripts or the maintenance and update of old scripts results in slow response times.

[0103] Furthermore, in a feasible implementation, the CIM metadata management system includes a CIM metadata extension module, and the method further includes steps B10 to B20:

[0104] Step B10: After detecting a CIM metadata extension instruction for a target metadata set, extracting metadata items to be extended and a target extension method from the CIM metadata extension instruction, wherein the target extension method is manual editing, data mining, or internal system data synchronization;

[0105] Step B20: Obtain the extended metadata corresponding to the metadata item to be extended by target extension, and update the extended metadata into the target metadata set.

[0106] In this embodiment, for a certain metadata set in the CIM metadata management system, when business personnel need to expand it with new metadata items, they can specify the newly expanded metadata items and expansion methods, and then update the metadata corresponding to the newly expanded metadata items to the metadata set through the CIM metadata expansion module.

[0107] That is, business personnel can designate a metadata set as the target metadata set, and set the metadata items that need to be newly extended as the metadata items to be extended. At the same time, they can designate one of the three extension methods, namely manual editing, data mining, or internal system data synchronization, as the target extension method. Based on the CIM metadata extension module, the metadata corresponding to the metadata item to be extended (extended metadata) is updated to the target metadata set through the target extension method.

[0108] Furthermore, in a feasible implementation, the CIM metadata management system includes a CIM metadata visualization module, and the method further includes step C10:

[0109] Step C10: After detecting the CIM metadata visualization instruction for the target metadata set, a knowledge graph is constructed for the target metadata set through the CIM metadata visualization module, and the constructed knowledge graph is visualized.

[0110] In this embodiment, the CIM metadata management system also includes a CIM metadata visualization module, which is used to construct a knowledge graph for the metadata set pointed to by the CIM metadata visualization instruction after receiving the CIM metadata visualization instruction, and visualize the constructed knowledge graph to the user.

[0111] In addition, please refer to Figure 5 , Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the CIM metadata collection method in the embodiment of the present application.

[0112] The present application also provides a computing service device, which includes: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the steps of the CIM metadata collection method in the above embodiment.

[0113] Reference below Figure 5 , which shows a schematic diagram of the structure of a computing service device suitable for implementing the embodiments of the present application. The computing service device in the embodiments of the present application may include, but is not limited to, a physical server, a virtual machine, a cloud server, or any computing service device that can implement the above functions. Figure 5 The computing service device shown is merely an example and should not limit the functions and scope of use of the embodiments of the present application.

[0114] like Figure 5As shown, the computing service device may include a processing device 1001 (e.g., a central processing unit, a graphics processing unit, etc.), which can perform various appropriate actions and processes based on programs stored in a read-only memory 1002 or programs loaded from a storage device 1003 into a random access memory 1004. The random access memory 1004 also stores various programs and data required for the operation of the computing service device. The processing device 1001, the read-only memory 1002, and the random access memory 1004 are interconnected via a bus 1005. An input / output interface 1006 is also connected to the bus. Typically, the following systems may be connected to the input / output interface 1006: input devices 1007 including, for example, a touchscreen, touchpad, keyboard, mouse, image sensor, microphone, accelerometer, gyroscope, etc.; output devices 1008 including, for example, a liquid crystal display (LCD), speakers, and vibrator; storage devices 1003 including, for example, magnetic tape and hard disk; and communication devices 1009. Communication device 1009 can allow the computing service device to communicate with other devices wirelessly or wired to exchange data. Although the figure shows a computing service device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.

[0115] In particular, according to the embodiments disclosed in the present application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, the embodiments disclosed in the present application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program comprising program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network via a communication device, or installed from a storage device 1003, or installed from a read-only memory 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are performed.

[0116] The computing service device provided in this application utilizes the CIM metadata collection method described in the aforementioned embodiments, resolving the technical issue in related art where, when business requirements for CIM metadata collection change, the need to wait for new scripts to be developed or for old scripts to be maintained and updated results in slow response times. Compared to existing technologies, the computing service device provided in this application offers the same beneficial effects as the CIM metadata collection method described in the aforementioned embodiments. Other technical features of this computing service device are the same as those disclosed in the aforementioned embodiments and are not further elaborated upon here.

[0117] It should be understood that the various parts disclosed in this application can be implemented using hardware, software, firmware, or a combination thereof. In the description of the above embodiments, specific features, structures, materials, or characteristics can be combined in any one or more embodiments or examples in a suitable manner.

[0118] The above are merely specific embodiments of the present application, but the scope of protection of the present application is not limited thereto. Any modifications or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the above claims.

[0119] In addition, an embodiment of the present application further provides a computer program product, which includes a computer program. When the computer program is executed by a processor, the steps of the CIM metadata collection method in the above embodiment are implemented.

[0120] The computer program product provided in this application addresses the technical issue in related art where, when business requirements for CIM metadata collection change, the need to wait for new scripts to be developed or for old scripts to be maintained and updated results in slow response times. Compared to the prior art, the beneficial effects of the computer program product provided in this embodiment are similar to those of the CIM metadata collection method described in the aforementioned embodiment and are not further elaborated here.

[0121] The above description is only part of the embodiments of the present application and does not limit the patent scope of the present application. All equivalent structural transformations made by using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect application in other related technical fields are included in the patent protection scope of the present application.

Claims

1. A CIM metadata collection method, characterized in that: The method is applied to a CIM metadata management system, and includes: After detecting the CIM metadata collection instruction, extracting the metadata items to be collected and the target CIM data source from the CIM metadata collection instruction; Determining the metadata layer of the metadata items to be collected according to the data source type of the target CIM data source, wherein the data source type is a relational database type, a spatiotemporal database type, a file system type, or a third-party system type, and the metadata layer is a database layer, a data table layer, a field layer, a record layer, a spatiotemporal data item layer, a folder layer, a file layer, an API group layer, or an API layer; Determining, from a preset CIM metadata collection rule library, a CIM metadata collection rule that matches the metadata layer as a third collection rule to be adjusted; According to the metadata item to be collected, adjusting the metadata item of the third collection rule to be adjusted to obtain a fourth collection rule to be adjusted; According to the data source type of the target CIM data source, the fourth collection rule to be adjusted is adjusted according to the data source type to obtain the target collection rule; According to the target collection rule, CIM metadata corresponding to the metadata item to be collected is collected from the target CIM data source.

2. The CIM metadata collection method according to claim 1, wherein: The CIM metadata management system includes a CIM metadata extension module, and the method further includes: After detecting a CIM metadata extension instruction for a target metadata set, extracting metadata items to be extended and a target extension method from the CIM metadata extension instruction, wherein the target extension method is manual editing, data mining, or internal system data synchronization; The extended metadata corresponding to the metadata item to be extended is acquired through the target extension method, and the extended metadata is updated into the target metadata set.

3. The CIM metadata collection method according to claim 1, wherein: The CIM metadata management system includes a CIM metadata collection plan page, and the method further includes: Acquire a CIM metadata collection plan developed through the CIM metadata collection plan page, wherein the CIM metadata collection plan includes metadata items to be collected, target CIM data sources, and a collection period; According to the collection cycle, a CIM metadata collection instruction for collecting metadata for the metadata items to be collected in the target CIM data source is regularly generated.

4. The CIM metadata collection method according to claim 1, wherein: The CIM metadata management system includes a CIM metadata visualization module, and the method further includes: After detecting the CIM metadata visualization instruction for the target metadata set, the CIM metadata visualization module constructs a knowledge graph for the target metadata set, and visualizes the constructed knowledge graph.

5. A computing service device, characterized in that: The computing service device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, the steps of the CIM metadata collection method according to any one of claims 1 to 4 are implemented.

6. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the CIM metadata collection method according to any one of claims 1 to 4 are implemented.

Images