A metadata-based railway engineering ECM management method, system and device

Abstract

The application provides a metadata-based railway engineering ECM management method, system and device, steps of the method comprising: performing primary coding and secondary coding on railway metadata types based on an international dictionary framework; establishing connection of data nodes and constructing a connection system; a document management stage of railway engineering involves multiple types of engineering construction nodes, and metadata and unstructured data required to be managed by engineering construction nodes of the same type are different in different document management stages, each engineering construction node corresponds to a data node, and in the same engineering stage document management stage, the data node corresponding to the lower-level engineering construction node inherits the data work authority of the higher-level data; whether a data instruction is effective is determined based on the work authority, if effective, the basic data is processed based on the data instruction, and is shared in each data node, and in each document management stage, metadata, authority data and unstructured data contained in the basic data are uniformly managed.

Description

Technical Field

[0001] This invention relates to the field of data management technology, and in particular to a method, system and device for railway engineering ECM management based on metadata. Background Technology

[0002] Enterprise Content Management (ECM) is a strategy and approach that helps businesses acquire, manage, store, protect, and utilize data related to their organizational processes, including unstructured data.

[0003] In the process of enterprise data content management, enterprise data includes data contained in documents of various formats, mainly unstructured data, including text, images, design models, design drawings, various forms, reports, official documents, videos, and audio, etc. Unstructured data accounts for approximately 80% of the total enterprise data volume. Enterprise data content management typically involves the acquisition, management, storage, display, sharing, and utilization of enterprise content to uncover its value, enhance the enterprise's competitive advantage, and support its long-term development.

[0004] However, in the current railway engineering field, railway construction includes the construction drawing design stage, delivery stage, construction stage, and archiving and operation stage. The amount of data is quite large, and the formats and contents of documents such as measurement, testing, construction, and quality acceptance generated during the railway project construction process vary depending on the different specifications and requirements of the participating parties. Furthermore, the rules for the circulation of various documents are not uniform. Summary of the Invention

[0005] In view of this, embodiments of the present invention provide a metadata-based railway engineering ECM management method to eliminate or improve one or more defects existing in the prior art.

[0006] One aspect of the present invention provides a metadata-based ECM management method for railway engineering, the method comprising the following steps:

[0007] The railway metadata type is obtained, and the railway metadata type is initially encoded based on the international dictionary framework to obtain the initially encoded data. The railway metadata type is then secondarily encoded based on the data attributes of the railway metadata type to obtain the secondarily encoded data. The secondarily encoded data of railway metadata types with the same data attributes have the same prefix.

[0008] The data attributes include data format, usage specifications, collection requirements, and utilization requirements.

[0009] Establish connections between data nodes based on predefined data interfaces, and build a connection system based on each connected data node;

[0010] Railway engineering includes multiple document management phases, each of which includes multiple types of engineering construction nodes. The management of unstructured data in each document management phase is achieved by managing the engineering construction nodes. Each engineering construction node corresponds to a data node. In the same document management phase, the working permissions of the data nodes are determined based on the working level of the engineering construction nodes. The data nodes corresponding to the lower-level engineering construction nodes inherit the working permissions of the data nodes corresponding to the higher-level engineering construction nodes.

[0011] The system receives data instructions from each data node. These instructions are processing instructions for the basic data under any of the secondary encoded data. The system determines whether the data instructions are effective based on the working permissions of each data node. If effective, the system processes the basic data based on the data instructions and shares the processed basic data among the data nodes.

[0012] By adopting the above scheme, on the one hand, this scheme enables data nodes corresponding to lower-level engineering construction nodes to inherit the work permissions of data nodes corresponding to higher-level engineering construction nodes, making work permissions transferable and improving the efficiency of permission allocation. On the other hand, this scheme unifies railway metadata types into secondary encoded data, allowing staff to issue data instructions at various nodes in the connection system. Based on the unified secondary encoded data, staff process basic data according to the unified metadata secondary encoded data, ensuring the uniformity of various document flow rules in railway construction work.

[0013] In some embodiments of the present invention, in the step of initially encoding railway metadata types based on the international dictionary framework, the initial encoding is performed based on the correspondence of railway metadata types in the international dictionary framework standard.

[0014] In some embodiments of the present invention, in the step of performing secondary encoding of railway metadata type based on data attributes of railway metadata type, secondary encoded data is allocated to the railway metadata type based on a preset correspondence.

[0015] In some embodiments of the present invention, in the step of establishing a connection between data nodes based on a predefined data interface, it is determined whether to establish a connection between data nodes based on the preset identity code.

[0016] In some embodiments of the present invention, the engineering construction node includes project units, line units, professional units, and design units. In the same document management stage, the working permissions of data nodes are determined based on the working level of the engineering construction node, and the data nodes corresponding to lower-level engineering construction nodes inherit the working permissions of data nodes corresponding to higher-level engineering construction nodes. The working level of the engineering construction node is determined based on the inclusion relationship between engineering construction nodes.

[0017] In some embodiments of the present invention, a project unit includes multiple line units, a line unit includes multiple professional units, a professional unit includes multiple design units, the work level of the project unit is higher than that of the line unit, the work level of the line unit is higher than that of the professional unit, and the work level of the professional unit is higher than that of the design unit.

[0018] In some embodiments of the present invention, the step of determining whether a data instruction is effective based on the working permissions of the data node includes:

[0019] Based on the received data instructions, determine the data node that issued the data instructions, and determine whether the data node has working permissions;

[0020] If the data node does not have working permissions, an instruction indicating that it does not have working permissions will be returned.

[0021] If the data node has working permissions, then the processing operation corresponding to the data instruction is parsed. The processing operation includes adding, deleting, modifying, and viewing. Metadata permissions include reading, writing, and deleting. Unstructured data permissions include list, reading, writing, deleting, and full control. Then, it is determined whether the data node has the operation permission corresponding to the processing operation.

[0022] If the data node has the operation permission corresponding to the processing operation, then the processing operation is executed;

[0023] If the data node does not have the operation permission corresponding to the processing operation, an instruction of no operation permission will be returned.

[0024] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node of the construction drawing design stage, then during the data interaction between the data node and the connection system data, data interaction is performed based on an encryption algorithm.

[0025] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node of the construction drawing delivery stage, then during the data interaction between the data node and the connection system data, an asymmetric algorithm is used to transcode and decode the data packet before delivery and after receipt to complete the data interaction.

[0026] In practice, the document management phase also includes a construction management phase and an organization and archiving phase.

[0027] In the specific implementation process, during the data interaction between this data node and the connection system data, the basic railway engineering data such as metadata and unstructured data managed by this data node interact with the connection system data.

[0028] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is an engineering construction node in the construction management stage, then during the data interaction between the data node and the connection system data, the data node is authenticated based on preset extended authentication information. If the authentication is successful, the data interaction is completed; if the authentication fails, the data interaction is stopped.

[0029] In some embodiments of the present invention, in the step of authenticating data nodes based on preset extended authentication information, JWT+extended authentication information is used to authenticate data nodes.

[0030] This invention also provides a metadata-based railway engineering ECM management system, the system comprising:

[0031] The encoding module is used to obtain railway metadata types. It performs initial encoding on the railway metadata types based on the international dictionary framework to obtain initial encoded data. It then performs secondary encoding on the railway metadata types based on the data attributes of the railway metadata types to obtain secondary encoded data. The secondary encoded data of railway metadata types with the same data attributes have the same prefix.

[0032] The node connection module establishes connections between data nodes based on predefined data interfaces and constructs a connection system based on the connected data nodes.

[0033] The permission allocation module is used in railway engineering, which includes multiple document management stages. Each document management stage includes multiple types of engineering construction nodes, and each engineering construction node corresponds to a data node. In the same document management stage, the work permissions of the data nodes are determined based on the work level of the engineering construction node. The data nodes corresponding to the lower-level engineering construction node inherit the work permissions of the data nodes corresponding to the higher-level engineering construction node.

[0034] The data processing module receives data instructions from each data node. The data instructions are processing instructions for the basic data under any of the secondary encoded data. The module determines whether the data instructions are effective based on the working permissions of the data nodes. If effective, the module processes the basic data based on the data instructions and shares the processed basic data among the data nodes.

[0035] The present invention also provides a metadata-based railway engineering ECM management device, which includes a computer device, the computer device including a processor and a memory, the memory storing computer instructions, the processor executing the computer instructions stored in the memory, and when the computer instructions are executed by the processor, the device implements the steps of the method described above.

[0036] Additional advantages, objects, and features of the invention will be set forth in part in the description which follows, and will also become apparent in part to those skilled in the art upon studying the text, or may be learned by practice of the invention. The objects and other advantages of the invention will become apparent from the description and the accompanying drawings.

[0037] Those skilled in the art will understand that the objectives and advantages achievable with the present invention are not limited to those specifically described above, and that the above and other objectives achievable with the present invention will become clearer from the following detailed description. Attached Figure Description

[0038] The accompanying drawings, which are provided to further illustrate the invention and form part of this application, are not intended to limit the scope of the invention.

[0039] Figure 1 This is a schematic diagram illustrating one implementation of the metadata-based railway engineering ECM management method of the present invention;

[0040] Figure 2 This is a schematic diagram of the data structure of the present invention;

[0041] Figure 3 This is a schematic diagram of a processing flow of the present invention;

[0042] Figure 4 This is a schematic diagram of another processing flow of the present invention. Detailed Implementation

[0043] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the embodiments and accompanying drawings. Here, the illustrative embodiments and descriptions of this invention are used to explain the invention, but are not intended to limit the invention.

[0044] It should also be noted that, in order to avoid obscuring the invention with unnecessary details, only the structures and / or processing steps closely related to the solution according to the invention are shown in the accompanying drawings, while other details that are not closely related to the invention are omitted.

[0045] It should be emphasized that the term "including / comprises" as used herein refers to the presence of a feature, element, step, or component, but does not exclude the presence or addition of one or more other features, elements, steps, or components.

[0046] It should also be noted that, unless otherwise specified, the term "connection" in this article can refer not only to a direct connection, but also to an indirect connection involving an intermediary.

[0047] In the following description, embodiments of the invention will be illustrated with reference to the accompanying drawings. In the drawings, the same reference numerals represent the same or similar parts, or the same or similar steps.

[0048] To solve the above problems, such as Figure 1 As shown, this invention proposes a metadata-based ECM management method for railway engineering, the steps of which include:

[0049] Step S100: Obtain railway metadata type, perform initial encoding on railway metadata type based on international dictionary framework to obtain initial encoded data, perform secondary encoding on railway metadata type based on data attributes to obtain secondary encoded data, and railway metadata type with the same data attributes has the same prefix for secondary encoded data.

[0050] In practice, the International Dictionary Framework (IFD) is used to ensure that the information exchanged is the same as the information needed. It separates concepts and descriptions and uses a Globally Unique Identifier (GUID) to define a unique identifier for each concept. The name and description are bound to the GUID for information transmission. Therefore, the information obtained by each participant after the exchange is consistent with the information they expect to obtain.

[0051] In specific implementation, the secondary encoding can be obtained by adding a prefix to the initial encoded data, or it can be obtained by directly mapping the railway metadata types one-to-one based on a preset lookup table.

[0052] In the specific implementation process, if the data attribute of the railway metadata type is a numeric number, then the secondary encoding data prefix is ​​PO, which can be the corresponding encoding method shown in Table 1 below:

[0053] Table 1

[0054]

[0055] In the specific implementation process, "PO" is used as a fixed prefix, and the English name, Chinese name, or Chinese abbreviation of the railway-specific terminology of the railway metadata is used as a suffix. The prefix and suffix are connected by the English underscore character "_", which is commonly used in development languages ​​such as Java, PHP, and JS.

[0056] Using the above scheme, this scheme uses this two-level encoded metadata as the underlying support and will be applied to the system's underlying data storage, data network transmission, application data interaction and other levels.

[0057] Step S200: Establish a connection between data nodes based on a predefined data interface, and construct a connection system based on each connected data node. The connection system includes multiple data nodes connected to the server, and each data node can be a computer.

[0058] In some embodiments of the present invention, in the step of establishing a connection between data nodes based on a predefined data interface, the data interface is defined using JWT (JSON Web Tokens) + identity code + standard data format. JWT serves as a token in JSON format for securely transmitting information as a JSON object between parties. During data transmission, data encryption, signing, and other related processing can also be performed, along with application system information, for valid authentication of applications on external networks.

[0059] The identification code serves as the user identifier for the node and is used for effective user authentication.

[0060] Standard data is defined using JSON Schema and includes a string containing valid data.

[0061] In some embodiments of this invention, the JSONSchema includes a standard definition of the metadata IFD code. Each piece of information in every sent and received data packet contains its own unique IFD code. When data is received and sent in interaction with the database, the IFD code undergoes a data conversion with the metadata secondary encoding to achieve the effect of storing and transmitting data according to the standard.

[0062] Step S300: The railway project includes multiple document management stages, each document management stage includes multiple types of project construction nodes, and each project construction node corresponds to a data node. In the same document management stage, the work permissions of the data node are determined based on the work level of the project construction node. The data node corresponding to the lower-level project construction node inherits the work permissions of the data node corresponding to the higher-level project construction node.

[0063] In the specific implementation process, according to the engineering construction management stage, the documents generated during railway construction can be divided into multiple document management stages, and the document management is built on multiple types of engineering construction nodes.

[0064] like Figure 2 , 3 As shown in Figure 4, in some embodiments of the present invention, railway engineering includes a construction drawing design stage, a construction management stage, and a construction drawing delivery stage. Each engineering construction node in the document management stage can include a project unit, a line unit, a professional unit, and a design unit.

[0065] Specifically, the project construction nodes also include section units, industry units, benchmark point units, and unit project units.

[0066] In the specific implementation process, the project unit can be a project unit corresponding to a railway engineering project, the line unit can be a line unit corresponding to a section of the line under a railway engineering project, the professional unit can be a professional unit corresponding to a specific building under a section of the line, and the design unit can be a design unit corresponding to a part of a specific building.

[0067] In the specific implementation process, the engineering construction nodes can be classified from high to low as project unit, line unit, professional unit, and design unit.

[0068] Step S400: Receive data instructions from each data node. The data instructions are processing instructions for basic data under any of the secondary encoded data. Determine whether the data instructions are effective based on the working permissions of the data nodes. If effective, process the basic data based on the data instructions and share the processed basic data among the data nodes.

[0069] If it does not take effect, the data instructions will not be executed.

[0070] Each data node can process the shared data based on data instructions.

[0071] In some embodiments of the present invention, the processing instructions may be instructions for adding, deleting, modifying or viewing the basic data under the secondary encoded data.

[0072] In the specific implementation process, the basic data is shared among various data nodes after processing. When other nodes process the basic data again, they process the basic data after the previous processing instruction has been changed.

[0073] By adopting the above scheme, on the one hand, this scheme enables data nodes corresponding to lower-level engineering construction nodes to inherit the work permissions of data nodes corresponding to higher-level engineering construction nodes, making work permissions transferable and improving the efficiency of permission allocation. On the other hand, this scheme unifies railway metadata types into secondary encoded data, allowing staff to issue data instructions at various nodes in the connection system. Based on the unified secondary encoded data, staff process basic data according to the unified metadata secondary encoded data, ensuring the uniformity of various document flow rules in railway construction work.

[0074] In some embodiments of the present invention, in the step of initially encoding railway metadata types based on the international dictionary framework, the initial encoding is performed based on the correspondence of railway metadata types in the international dictionary framework standard.

[0075] In practice, the International Dictionary Framework (IFD) is used to ensure that the information exchanged is the same as the information needed. It separates concepts and descriptions and uses a Globally Unique Identifier (GUID) to define a unique identifier for each concept. The name and description are bound to the GUID for information transmission. Therefore, the information obtained by each participant after the exchange is consistent with the information they expect to obtain.

[0076] In some embodiments of the present invention, in the step of performing secondary encoding of railway metadata type based on data attributes of railway metadata type, secondary encoded data is allocated to the railway metadata type based on a preset correspondence.

[0077] In specific implementation, the secondary encoding can be obtained by adding a prefix to the initial encoded data, or it can be obtained by directly mapping the railway metadata types one-to-one based on a preset lookup table.

[0078] By adopting the above scheme, secondary encoded data can be assigned to railway metadata types, and the secondary encoded data of railway metadata types with the same data attributes have the same prefix, which makes it easier for operators to find the corresponding railway metadata type according to the data attributes and improves processing efficiency.

[0079] In some embodiments of the present invention, in the step of establishing a connection between data nodes based on a predefined data interface, it is determined whether to establish a connection between data nodes based on the preset identity code.

[0080] In some embodiments of the present invention, in the step of establishing a connection between data nodes based on a predefined data interface, the data interface is defined using JWT (JSON Web Tokens) + identity code + standard data format. JWT serves as a token in JSON format for securely transmitting information as a JSON object between parties. During data transmission, data encryption, signing, and other related processing can also be performed, along with application system information, for valid authentication of applications on external networks.

[0081] By adopting the above solution and using the same interface format, the uniformity of each access node is improved, and the security of data transmission is enhanced.

[0082] In some embodiments of the present invention, the engineering construction node includes project units, line units, professional units, and design units. In the same document management stage, the working permissions of data nodes are determined based on the working level of the engineering construction node, and the data nodes corresponding to lower-level engineering construction nodes inherit the working permissions of data nodes corresponding to higher-level engineering construction nodes. The working level of the engineering construction node is determined based on the inclusion relationship between engineering construction nodes.

[0083] like Figure 2 , 3 As shown in Figure 4, in some embodiments of the present invention, railway engineering includes a construction drawing design stage, a construction management stage, and a construction drawing delivery stage. Each engineering construction node in the document management stage can include a project unit, a line unit, a professional unit, and a design unit.

[0084] In the specific implementation process, the project unit can be a project unit corresponding to a railway engineering project, the line unit can be a line unit corresponding to a section of the line under a railway engineering project, the professional unit can be a professional unit corresponding to a specific building under a section of the line, and the design unit can be a design unit corresponding to a part of a specific building.

[0085] In the specific implementation process, the engineering construction nodes can be classified from high to low as project unit, line unit, professional unit, and design unit.

[0086] By adopting the above scheme, the data nodes corresponding to the lower-level engineering construction nodes inherit the working permissions of the data nodes corresponding to the higher-level engineering construction nodes, which facilitates permission transfer and solves the problem that traditional permissions can only be allocated by the system, thus improving allocation efficiency.

[0087] like Figure 3 As shown, in some embodiments of the present invention, a project unit includes multiple line units, a line unit includes multiple professional units, a professional unit includes multiple design units, the work level of the project unit is higher than that of the line unit, the work level of the line unit is higher than that of the professional unit, and the work level of the professional unit is higher than that of the design unit.

[0088] In some embodiments of the present invention, the step of determining whether a data instruction is effective based on the working permissions of the data node includes:

[0089] Based on the received data instructions, determine the data node that issued the data instructions, and determine whether the data node has working permissions;

[0090] If the data node does not have working permissions, an instruction indicating that it does not have working permissions will be returned.

[0091] If the data node has working permissions, then the processing operation corresponding to the data instruction is parsed. The processing operation includes adding, deleting, modifying, and viewing, and it is determined whether the data node has the operation permission corresponding to the processing operation.

[0092] If the data node has the operation permission corresponding to the processing operation, then the processing operation is executed;

[0093] If the data node does not have the operation permission corresponding to the processing operation, an instruction of no operation permission will be returned.

[0094] In some embodiments of the present invention, the operation permissions are assigned by a preset administrator node.

[0095] By adopting the above scheme, on the one hand, the data nodes corresponding to the lower-level engineering construction nodes can inherit the working permissions of the data nodes corresponding to the higher-level engineering construction nodes, which facilitates permission transfer; on the other hand, in the actual data operation process, this scheme needs to rely on both operation permissions and working permissions to further ensure data security.

[0096] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node of the construction drawing design stage, then during the data interaction between the data node and the connection system data, data interaction is performed based on an encryption algorithm.

[0097] In specific implementation, the encryption algorithm can be either SM2 or SM4.

[0098] Using the above scheme, during the construction drawing design phase, we expanded the support for national cryptographic standard (NCS) modification of railway metadata secondary encoding to ensure data security in the design drawings. The NCS modification involves using algorithms based on the national cryptographic standard for plaintext and ciphertext transposition storage during this phase. Ciphertext transposition is used during data interaction and transmission, while plaintext data is used for data display and use. The identification code is used to encode the delivered data packets. Completeness verification is performed on the data packets before and after data transmission to ensure data consistency.

[0099] In the specific implementation process, the documents that may be used during railway construction are predictable. Therefore, we store the document itself and use a specific positioning method to calculate and locate a certain area within the document using the secondary encoding of railway metadata. This allows one piece of secondary encoded metadata to control a specific area within the document. Different positioning algorithms were developed for different document types. For example, we use horizontal and vertical coordinates for Excel files, bookmarks for Word documents, row and column coordinates for TXT files, and latitude, longitude, azimuth, and viewpoint for model and map documents, etc.

[0100] Once the document is positioned correctly, the true and false values ​​of the doWrite and doAble standards can be used to dynamically control that area, determining when it can be edited, when data can be overwritten, and when data can be extracted.

[0101] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node of the construction drawing delivery stage, then during the data interaction between the data node and the connection system data, an asymmetric algorithm is used to transcode and decode the data packet before delivery and after receipt to complete the data interaction.

[0102] In specific implementation, the asymmetric algorithm can be the SM9 algorithm.

[0103] Using the above scheme, during the construction drawing delivery phase, we extended support for asymmetric algorithm verification and electronic identity authentication to address the requirement for validity and consistency in the delivered data packets. Asymmetric algorithms are used to transcode and decode the data packets before delivery and after receipt. The comparison results of the transcoded and byte-level data are then analyzed to verify that the data packets originate from a valid data source. Additionally, the data packets accompanying the delivery are authenticated byte-by-byte using an identification code, and the consistency of the data bytes is verified upon receipt.

[0104] In some embodiments of the present invention, the document management stage of railway engineering includes the construction drawing design stage, the construction management stage, and the construction drawing delivery stage. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is an engineering construction node in the construction management stage, then during the data interaction between the data node and the connection system data, the data node is authenticated based on preset extended authentication information. If the authentication is successful, the data interaction is completed; if the authentication fails, the data interaction is stopped.

[0105] In the specific implementation process, the document management stage of railway engineering also includes the archiving stage of completion acceptance data.

[0106] The above solution incorporates numerous nodes in the construction and management phase. To improve verification efficiency and further enhance security, this solution adds extended identity verification information.

[0107] During the construction management phase, the construction management business system built using the ECM management framework underwent standardized adaptation at the data and interface levels for other phases, including before and after. It also expanded the strategy for secondary transcoding of railway metadata during the construction management phase. Data generated at different phases is collected in the system generated during the construction management phase, and different strategies are used to control the data, interfaces, and presentation levels.

[0108] The above-described scheme features a highly detailed strategy definition that permeates the entire system construction and management phase. This ranges from large-scale definitions such as key policies supporting national cryptographic upgrades during delivery, digital signature policies for electronic authentication used in project drawings, and which secondary encoded metadata to use during structured data transmission—covering multi-system interaction levels—to smaller details like log auditing methods, including sequential logs, by role, by function, and by operation subject. The strategy can also be integrated with client-side mini-programs for offline data management on terminal devices, controlling whether structured data can be viewed offline, and whether unstructured data can be opened offline, dragged and dropped, and copied. During the final acceptance phase, we added support for data volume assembly, allowing the recombination of any type (structured, unstructured, structured, process-based) of secondary encoded railway metadata. The volume assembly method is also configured through strategies, dynamically tailored to the management requirements of local archives.

[0109] This invention also provides a metadata-based railway engineering ECM management system, the system comprising:

[0110] The encoding module is used to obtain railway metadata types. It performs initial encoding on the railway metadata types based on the international dictionary framework to obtain initial encoded data. It then performs secondary encoding on the railway metadata types based on the data attributes of the railway metadata types to obtain secondary encoded data. The secondary encoded data of railway metadata types with the same data attributes have the same prefix.

[0111] By adopting the above approach, we leverage the universality of metadata to create a standard secondary encoding of railway metadata through in-depth analysis. Based on this encoding, we define standard data storage structures, data network transmission structures, security verification specifications, standard data interaction formats, and data application usage specifications. These standards are highly universal and adaptable to any ECM management system in the railway engineering field. Furthermore, nodes using this ECM management system inherently possess secure network transmission paths and standard network transmission data formats.

[0112] The node connection module establishes connections between data nodes based on predefined data interfaces and constructs a connection system based on the connected data nodes.

[0113] The permission allocation module is used in railway engineering, which includes multiple document management stages. Each document management stage includes multiple types of engineering construction nodes, and each engineering construction node corresponds to a data node. In the same document management stage, the work permissions of the data nodes are determined based on the work level of the engineering construction node. The data nodes corresponding to the lower-level engineering construction node inherit the work permissions of the data nodes corresponding to the higher-level engineering construction node.

[0114] The data processing module receives data instructions from each data node. The data instructions are processing instructions for the basic data under any of the secondary encoded data. The module determines whether the data instructions are effective based on the working permissions of the data nodes. If effective, the module processes the basic data based on the data instructions and shares the processed basic data among the data nodes.

[0115] In existing technologies, current railway data management suffers from the following problems: 1. Inconsistent document creation. Due to varying specifications and requirements from different participants in railway construction projects, the formats and contents of documents generated during the construction process, such as measurement, testing, construction, and quality acceptance documents, differ, and the rules for document circulation are not uniform. Furthermore, issues exist such as non-standard document content, inaccurate terminology, unclear signatures, and untimely acceptance. 2. Difficult document collection. Railway project construction periods can last several years, while operation periods can extend to decades or even centuries. Participating units and project organizations are not fixed, and personnel turnover is high, which increases the difficulty of document collection, easily leading to document loss, incompleteness, omissions, and distortion. Shortcomings in the collection process create significant difficulties for subsequent document utilization. 3. Wide range of document content. Railway construction project documents cover various types of data, including surveying and design, construction, supervision, and completion. Document creation often involves approvals from the competent authority, design unit evaluations, on-site assessments by construction units, supervision by supervision units, and quality assessments by supervisory agencies. Different projects and participating parties have varying requirements for document formats and content, often requiring construction units to prepare several sets of documents for handover based on each party's requirements. 4. Difficulty in document utilization. Project management documents are archives generated during the construction process, not only truthfully recording the entire construction process but also providing traceability for project quality. Railway construction project documents are collected and organized by the construction unit's document controller before being transferred to the archives. Currently, only the archiving management of the resulting documents is achieved; full-process control over document creation, circulation, approval, organization, compilation, acceptance, and handover based on a unified collaborative platform has not yet been realized, nor has document sharing and utilization among relevant participating parties been achieved.

[0116] This solution constructs a metadata-based ECM management system for railway engineering. Using metadata as a foundation and a universal interface standard, it builds corresponding management systems based on the characteristics of ECM management at different stages. These systems are then integrated around metadata to form a unified ECM management system for the entire railway industry. Based on this system, a unified railway engineering ECM management system can be built for unified management. This solution aims to leverage the standardization and universality of metadata to standardize and regulate the ECM management issues faced by the railway industry at various stages, forming a metadata-based universal interface standard. Based on the characteristics of ECM management at different stages, corresponding management systems are built, and these systems are integrated around metadata to form a unified railway industry ECM management system. Business systems built upon this system naturally possess standardized interoperability, and their data formats conform to standards, meeting the requirements for external provision. This significantly solves problems related to construction costs, resource utilization, and operational efficiency.

[0117] The present invention also provides a metadata-based railway engineering ECM management device, which includes a computer device, the computer device including a processor and a memory, the memory storing computer instructions, the processor executing the computer instructions stored in the memory, and when the computer instructions are executed by the processor, the device implements the steps of the method described above.

[0118] This invention also provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the aforementioned metadata-based railway engineering ECM management method. The computer-readable storage medium can be a tangible storage medium, such as random access memory (RAM), main memory, read-only memory (ROM), electrically programmable ROM, electrically erasable programmable ROM, registers, floppy disks, hard disks, removable storage disks, CD-ROMs, or any other form of storage medium known in the art.

[0119] Those skilled in the art will understand that the exemplary components, systems, and methods described in conjunction with the embodiments disclosed herein can be implemented in hardware, software, or a combination of both. Whether implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this invention. When implemented in hardware, it can be, for example, electronic circuits, application-specific integrated circuits (ASICs), appropriate firmware, plug-ins, function cards, etc. When implemented in software, the elements of this invention are programs or code segments used to perform the desired tasks. The programs or code segments can be stored in a machine-readable medium or transmitted over a transmission medium or communication link via data signals carried in a carrier wave.

[0120] It should be clarified that the present invention is not limited to the specific configurations and processes described above and shown in the figures. For the sake of brevity, detailed descriptions of known methods are omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown. Those skilled in the art can make various changes, modifications, and additions, or change the order of steps, after understanding the spirit of the present invention.

[0121] In this invention, features described and / or illustrated for one embodiment may be used in the same or similar manner in one or more other embodiments, and / or combined with or in place of features of other embodiments.

[0122] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, various modifications and variations of the embodiments of the present invention are possible. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A metadata-based ECM management method for railway engineering, characterized in that, The steps of the method include: The railway metadata type is obtained, and the railway metadata type is initially encoded based on the international dictionary framework to obtain the initially encoded data. The railway metadata type is then secondarily encoded based on the data attributes of the railway metadata type to obtain the secondarily encoded data. The secondarily encoded data of railway metadata types with the same data attributes have the same prefix. Establish connections between data nodes based on predefined data interfaces, and build a connection system based on each connected data node; Railway engineering includes multiple document management phases, each of which includes various types of engineering construction nodes. The management of unstructured data in each document management phase is achieved by managing these engineering construction nodes. Each engineering construction node corresponds to a data node. Within the same document management phase, the work permissions of the data nodes are determined based on the work level of the engineering construction nodes. Data nodes corresponding to lower-level engineering construction nodes inherit the work permissions of data nodes corresponding to higher-level engineering construction nodes. The engineering construction nodes include project units, line units, professional units, and design units. The work level of the engineering construction nodes is determined based on the inclusion relationship between them. The system receives data instructions from various data nodes. These instructions are processing instructions for basic data under any of the secondary encoded data. The system determines whether the data instructions are effective based on the working permissions of the data nodes. It then identifies the data node that issued the instructions based on the received instructions and determines whether that data node has working permissions. If the data node does not have working permissions, it sends an instruction indicating no working permissions. If the data node has working permissions, it parses the processing operation corresponding to the data instructions. These processing operations include adding, deleting, modifying, and viewing. It then determines whether the data node has the operation permission corresponding to the processing operation. If the data node has the operation permission, it executes the processing operation. If the data node does not have the operation permission, it sends an instruction indicating no operating permissions. If the instructions are effective, the system processes the basic data based on the data instructions and shares the processed basic data among all data nodes.

2. The railway engineering ECM management method based on metadata according to claim 1, characterized in that, In the step of initially encoding railway metadata types based on the international dictionary framework, the initial encoding is performed based on the correspondence of railway metadata types in the international dictionary framework standard; In the step of performing secondary encoding of railway metadata types based on data attributes of railway metadata types, secondary encoded data is assigned to the corresponding railway metadata types based on a preset correspondence.

3. The railway engineering ECM management method based on metadata according to claim 1, characterized in that, In the step of establishing a connection between data nodes based on a predefined data interface, a preset identity code is used to determine whether to establish a connection between data nodes.

4. The railway engineering ECM management method based on metadata according to claim 1, characterized in that, The document management phase of railway engineering includes the construction drawing design phase and the construction drawing delivery phase. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node in the construction drawing design phase, then during the data interaction between the data node and the connection system data, data interaction is carried out based on an encryption algorithm.

5. The railway engineering ECM management method based on metadata according to claim 1, characterized in that, The document management phase of railway engineering includes the construction drawing design phase, the construction management phase, and the construction drawing delivery phase. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is the engineering construction node in the construction drawing delivery phase, then during the data interaction between the data node and the connection system data, an asymmetric algorithm is used to transcode and decode the data packets before delivery and after receipt to complete the data interaction.

6. The railway engineering ECM management method based on metadata according to claim 1, characterized in that, The document management phase of railway engineering includes the construction drawing design phase, the construction management phase, and the construction drawing delivery phase. In the step of processing basic data based on the data instructions, if the engineering construction node corresponding to the data node is an engineering construction node in the construction management phase, then during the data interaction between the data node and the connection system data, the data node is authenticated based on the preset extended authentication information. If the authentication is successful, the data interaction is completed; if the authentication fails, the data interaction is stopped.

7. A metadata-based railway engineering ECM management system, characterized in that, The system includes: The encoding module is used to obtain railway metadata types. It performs initial encoding on the railway metadata types based on the international dictionary framework to obtain initial encoded data. It then performs secondary encoding on the railway metadata types based on the data attributes of the railway metadata types to obtain secondary encoded data. The secondary encoded data of railway metadata types with the same data attributes have the same prefix. The node connection module establishes connections between data nodes based on predefined data interfaces and constructs a connection system based on the connected data nodes. The permission allocation module is used in railway engineering, which includes multiple document management stages. Each document management stage includes multiple types of engineering construction nodes, and each engineering construction node corresponds to a data node. In the same document management stage, the work permissions of the data nodes are determined based on the work level of the engineering construction node. The data nodes corresponding to the lower-level engineering construction node inherit the work permissions of the data nodes corresponding to the higher-level engineering construction node. The engineering construction nodes include project units, line units, professional units, and design units. The work level of the engineering construction nodes is determined based on the inclusion relationship between the engineering construction nodes. The data processing module receives data instructions from various data nodes. These instructions are processing instructions for basic data under any of the secondary encoded data. The module determines whether the data instructions are effective based on the data node's permissions, identifies the data node that issued the instructions based on the received instructions, and determines whether that data node has the necessary permissions. If the data node does not have the necessary permissions, it sends a "no permissions" message. If the data node has the necessary permissions, it parses the processing operation corresponding to the data instructions. These processing operations include adding, deleting, modifying, and viewing. The module determines whether the data node has the corresponding operation permission. If the data node has the corresponding operation permission, it executes the processing operation. If the data node does not have the corresponding operation permission, it sends a "no permissions" message. If the instructions are effective, the module processes the basic data based on the data instructions and shares the processed basic data among all data nodes.

8. A metadata-based railway engineering ECM management device, characterized in that, The device includes a computer device, which includes a processor and a memory, wherein the memory stores computer instructions, and the processor executes the computer instructions stored in the memory. When the computer instructions are executed by the processor, the device implements the steps of the method as described in any one of claims 1-6.

Images