A multi-standard oriented interactive electronic manual integrated loading device and method

Abstract

The application relates to a multi-standard-oriented interactive electronic manual integrated loading device and method, and belongs to the technical field of ship comprehensive support, which comprises an IETM equipment tree analysis module, a data packet interface module, a data packet structure verification module, a PM verification module, a DM verification module, a registration information confirmation module, a data packet publishing module, a data analysis import module, a platform access module, a log output module, an IETM manual change module and an IETM manual uninstallation module. The application can check from the standard compliance and the data packet content integrity, can issue a check report and give accurate problem positioning, can greatly improve the efficiency and accuracy of data packet acceptance work, internally has a Schema set of mainstream IETM technical standards and different versions thereof, supports checking of various standards, and can continuously expand support for new standards, can complete structure conversion and automatic loading of IETM data packets, reduces the failure rate of manual operation, and improves the efficiency of integration work.

Description

Technical Field

[0001] This invention belongs to the field of ship integrated support technology, and in particular relates to an interactive electronic manual integration loading device and method for multiple standards. Background Technology

[0002] With the continuous development of IETM (Interactive Electronic Technical Manual) technology, the industry frequently updates the two mainstream technical standards, S1000D and GJB6600. However, when new versions are released, older versions of the technical standards are not repealed. Therefore, IETM software vendors on the market often have their own main supported technical standard system and corresponding versions.

[0003] The IETM integration loading device is a software tool specifically designed for large and complex equipment and for integrating multi-standard IETM data packets. It can automatically perform standard compliance and integrity checks on data packets, and load verified data packets into IETM browsing devices, effectively improving the efficiency of IETM integration.

[0004] Traditionally, when integrating large and complex equipment into IETM (Integrated Equipment Technology), a specific technical standard and version number are specified during the project initiation phase. Each subsystem or component is required to adhere to this standard when creating its IETM data packages. During project integration, DDN (Digital Data Interchange) data packages are used as the data exchange medium for verification and integration. This approach has the following problems: 1. Tools from different vendors may not support the required standards and version numbers. 2. While vendors may have previously created IETM manuals for the equipment, the supported technical standards and version numbers are often outdated, requiring additional manpower to recreate them to meet the requirements of new projects. Summary of the Invention

[0005] The technical problem to be solved by the present invention is to provide an automated interactive electronic manual data package verification tool that supports multiple standards and data acquisition software interfaces, and can load the verified interactive electronic manual data package into the IETM browsing device, thereby avoiding the workload caused by each device manufacturer repeatedly producing device IETM data packages and improving project efficiency.

[0006] To achieve the above objectives, the present invention provides a multi-standard interactive electronic manual integration and loading device, comprising:

[0007] The IETM equipment tree parsing module is used to generate a hierarchical IETM equipment catalog tree and distinguish them according to whether the IETM manual is loaded.

[0008] The data packet interface module is used for the structure conversion of standard data packets. Data packets processed by this module are converted to a standard structure before subsequent verification and import are performed.

[0009] The data packet structure verification module is used to check the correctness and integrity of the data packet structure selected by the user or converted by the data acquisition software.

[0010] The PM verification module is used to verify the legitimacy of the PM module.

[0011] The resource location verification module is used to verify the legality of resource location files;

[0012] The DM verification module is used to verify the legality and integrity of all data modules in resource location.

[0013] The registration information confirmation module is used to extract manual registration information from the data packet, and at the same time verify that the IETM release directory name conforms to the standard release project name specification to ensure the uniqueness of the IETM release directory name in the running platform;

[0014] The data packet publishing module is used to establish the data packet entity storage area in the server;

[0015] The data parsing and import module is used to parse data packets and registration information and insert the relevant data into the database of the IETM runtime platform;

[0016] The platform access module is used to register the IETM manual for this equipment in the database of the running platform;

[0017] The log output module is used to record the process log of IETM packet loading or unloading;

[0018] The IETM manual modification module is used to change the configuration of IETM status.

[0019] The IETM Manual Uninstallation Module is used to uninstall the IETM manual for the equipment and delete the release data package for this project in the release directory of the running platform.

[0020] Preferably, the directory tree adopts an asynchronous loading strategy, possesses the basic functions of a general navigation tree while supporting keyboard shortcut operations, and allows for "expand all" and "close all" node operations on the tree. It can also distinguish the current IETM status of the equipment as needed: 1. Gray - IETM system not loaded; 2. Black - IETM system available; 3. Red - IETM system disabled or failed to load.

[0021] The technical solution of the present invention also provides a method for integrating and loading interactive electronic manuals for multiple standards, including the following steps:

[0022] Step 201: Select the IETM equipment to be loaded;

[0023] Step 202: Select the pre-loaded IETM manual data package and perform structural verification on the data package;

[0024] Step 203: Verify the validity and legality of the files in the data packet, and whether there are any entity files or files in formats not supported by the running platform;

[0025] Step 204: Extract the necessary information about the pre-loaded IETM manual from the data packet, display it to the user, and verify the information changed by the user.

[0026] Step 205: Place the data package into the corresponding folder in the runtime platform's release directory;

[0027] Step 206: Insert the relevant data information of the IETM manual into the runtime platform database;

[0028] Step 207: Register the equipment's IETM manual with the platform database;

[0029] Step 208: Record the entire IETM loading process, including the reasons for verification failure and the reasons for unsuccessful loading, or the details of the successful loading process.

[0030] Preferably, the PMC code compliance verification includes extracting the device's PMC code from pm.xml and verifying the PMC length, segments, and characters used according to the selected standard and version number.

[0031] Preferably, the resource file integrity verification includes verifying whether the data module file and external file pointed to in pm.xml are mapped in the resource location file. If the resource location file does not contain this data module file or external file, the PM module verification fails.

[0032] Preferably, the schema validity verification of the resource location file includes retrieving the schema file urn_map.xsd of the resource location file and verifying the validity of the urn_map.xml file in the data packet.

[0033] Preferably, the resource entity file integrity verification includes verifying whether the relevant resource in the urn_map.xml file has an entity file.

[0034] Preferably, the resource entity file integrity verification specifically involves extracting data from urn_map.xml. <urn>The value of the element's [name] attribute depends on <target>Different values ​​of the element's [nss] attribute will result in different truncation methods for [name] as the basis for querying entity file names. The checks are as follows: 1. Whether there is a corresponding entity file for the name dm in the dm folder; 2. Whether there is a corresponding entity file for the name icn in the illustration folder; 3. Whether there is a corresponding entity file for the name pmc in the file folder. If any are missing, a list of missing entity files will be displayed to the user, and the verification will fail.

[0035] Preferably, the schema validity verification of the DM module includes verification based on the description of dm in urn_map.xml. <target>The [type] attribute value is used to call the corresponding data module schema from the network to verify the validity of all dm entity files in the dm folder.

[0036] Preferably, the integrity verification of the DM reference files includes verifying whether all graphics and multimedia referenced in all data module files under the dm folder are described in urn_map.xml, and whether there are any graphics or multimedia formats that are not supported by the running platform.

[0037] The present invention has the following advantages:

[0038] This invention provides an automated IETM standard data packet verification device that can verify compliance with standards and integrity of data packet content, generate verification reports, and provide accurate problem location, thereby significantly improving the efficiency and accuracy of data packet acceptance work.

[0039] Secondly, this invention incorporates the mainstream IETM technology standards and their different versions of schema sets, supports the verification of multiple standards, and can continuously expand support for new standards.

[0040] Finally, this invention has an information interface with the IETM browsing device, which can complete the structural conversion and automatic loading of IETM data packets, reducing the error rate of manual operation and improving the efficiency of integration work. Attached Figure Description

[0041] Figure 1 This is a schematic block diagram of an interactive electronic manual integration and loading device and method oriented towards multiple standards, according to an embodiment of the present invention.

[0042] Attached reference numerals: 101, IETM Equipment Tree Parsing Module; 102, Data Packet Interface Module; 103, Data Packet Structure Verification Module; 104, PM Verification Module; 105, Resource Location Verification Module; 106, DM Verification Module; 107, Registration Information Confirmation Module; 108, Data Packet Publishing Module; 109, Data Parsing and Import Module; 110, Platform Access Module; 111, Log Output Module; 112, IETM Manual Modification Module; 113, IETM Manual Uninstallation Module. Detailed Implementation

[0043] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0044] This invention discloses an interactive electronic manual integration and loading device oriented towards multiple standards, comprising:

[0045] The IETM equipment tree parsing module 101 is used to generate a hierarchical IETM equipment directory tree and distinguish it according to whether the IETM manual is loaded.

[0046] The data packet interface module 102 is used for the structure conversion of standard data packets. Data packets that pass through this module are converted to a standard structure before subsequent verification and import are performed.

[0047] The data packet structure verification module 103 is used to check the correctness and integrity of the data packet structure selected by the user or the data packet structure converted by the data acquisition software.

[0048] PM verification module 104 is used to verify the legitimacy of the PM module.

[0049] The resource location verification module 105 is used to verify the legality of the resource location file.

[0050] DM verification module 106 is used to verify the legality and integrity of all data modules in resource location.

[0051] The registration information confirmation module 107 is used to extract manual registration information from the data packet, and at the same time verify that the IETM release directory name conforms to the standard release project name specification to ensure the uniqueness of the IETM release directory name in the running platform.

[0052] The data packet publishing module 108 is used to establish the data packet entity storage area in the server.

[0053] The data parsing and import module 109 is used to parse the "data packet" and "registration information" and insert the relevant data into the database of the IETM runtime platform.

[0054] The platform access module 110 is used to register the IETM manual of the equipment in the running platform database.

[0055] Log output module 111 is used to record the process log of IETM packet loading or unloading.

[0056] IETM manual change module 112 is used to change the configuration of IETM status.

[0057] IETM Manual Uninstall Module 113 is used to uninstall the IETM manual of the equipment and delete the release data package of the project in the release directory of the running platform.

[0058] Furthermore, this embodiment discloses a method for integrating and loading multi-standard interactive electronic manuals, including the following steps:

[0059] Step 201: Select the IETM equipment to be loaded;

[0060] Step 202: Select the pre-loaded IETM manual data package and perform structural verification on the data package;

[0061] Step 203: Verify the validity and legality of the files in the data packet, and whether there are any entity files or files in formats not supported by the running platform;

[0062] Step 204: Extract the necessary information about the pre-loaded IETM manual from the data packet, display it to the user, and verify the information changed by the user.

[0063] Step 205: Place the data package into the corresponding folder in the runtime platform's release directory;

[0064] Step 206: Insert the relevant data information of the IETM manual into the runtime platform database;

[0065] Step 207: Register the equipment's IETM manual with the platform database;

[0066] Step 208: Record the entire IETM loading process, including the reasons for verification failure and the reasons for unsuccessful loading, or the details of the successful loading process.

[0067] To make the objectives, technical solutions, and advantages of the present invention clearer, the embodiments disclosed herein will be described in further detail below with reference to the accompanying drawings.

[0068] Reference Figure 1 The diagram shows a schematic block diagram of an interactive electronic manual integration loading device and method oriented towards multiple standards, according to an embodiment of the present invention.

[0069] The IETM equipment tree parsing module 101 is used to generate a hierarchical multi-IETM equipment catalog tree and distinguish them according to whether the IETM manual is loaded.

[0070] The directory tree uses an asynchronous loading strategy. While possessing the basic functions of a general navigation tree, it also supports keyboard shortcut operations. Users can perform "expand all" and "close all" node operations on the tree. It can distinguish the current IETM status as needed: 1. Gray - IETM system not loaded; 2. Black - IETM system available; 3. Red - IETM system disabled or failed to load.

[0071] Selecting a specific equipment node will display information from its IETM manual, including: PMC code, IETM status, IETM publication directory name, IETM security level, and loading / modification operations.

[0072] The data packet interface module 102 primarily converts IETM data packets created by other manufacturers into data packets conforming to the IETM browsing device standard format. It then calls subsequent verification and import modules to load the IETM manual. The page provides an option entry for this interface module, allowing users to select different standards and version numbers.

[0073] The data packet structure verification module 103 is used to check the correctness and integrity of the data packet structure selected by the user or the data packet structure converted by the data acquisition software.

[0074] The data packet structure is shown in Table 1:

[0075] Table 1 Data Package Directory Structure

[0076]

[0077] The system analyzes whether the files or folders within the data packet conform to the standard data packet structure (as shown in Table 1). The absence of the equiplogo.jpg image will not affect verification; the system will automatically add a default equipment image to the data packet and provide a prompt to the user. If other files or folders are missing, a list of missing files should be displayed to the user.

[0078] PM verification module 104 is used to verify the legality of PM modules. The verification content includes PM module schema legality verification, PMC code compliance verification, and resource file integrity verification.

[0079] The schema validity verification of PM verification module 104 refers to retrieving the schema file pm.xsd from the publishing module and verifying the validity of the pm.xml file in the data packet.

[0080] PMC code compliance verification refers to extracting the device's PMC code from pm.xml and verifying the PMC length, segments, and characters used according to the selected standard and version number.

[0081] Resource file integrity verification refers to verifying whether the data module files and external files pointed to in pm.xml are mapped in the resource location file. If the resource location file does not contain the data module file or external file, the PM module verification fails.

[0082] The resource location verification module 105 is used to verify the legality of the resource location file. The verification content includes the legality verification of the schema of the resource location file and the integrity verification of the resource entity file.

[0083] The schema validity verification of the resource location file refers to retrieving the schema file urn_map.xsd of the resource location file and verifying the validity of the urn_map.xml file in the data packet.

[0084] Resource entity file integrity verification refers to verifying whether the relevant resource entity files exist in the urn_map.xml file. Specifically, it involves extracting the relevant data from urn_map.xml. <urn>The value of the element's [name] attribute depends on

[0085] <target>Different values ​​for the element's [nss] attribute will result in different truncation methods for [name] as the basis for querying entity file names, checking the following: 1. Whether the name 'dm' has a corresponding entity file in the 'dm' folder; 2. Whether the name 'icn' has a corresponding entity file in the 'illustration' folder; 3. Whether the name 'pmc' has a corresponding entity file in the 'file' folder. If any are missing, a list of missing entity files will be displayed to the user, and the validation will fail.

[0086] The DM verification module 106 is used to verify the legality and integrity of all data modules in resource location. The verification content includes the legality verification of the DM module's schema and the integrity verification of the DM reference files.

[0087] The schema validity verification of the DM module refers to the validation of the schema based on the description in urn_map.xml. <target>The [type] attribute value is used to call the corresponding data module schema from the network to verify the validity of all dm entity files in the dm folder.

[0088] The integrity verification of DM reference files refers to verifying whether all graphics and multimedia referenced in all data module files under the dm folder are described in urn_map.xml, and whether there are any graphics and multimedia formats that are not supported by the running platform.

[0089] Finally, it should be noted that the above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art can still modify the technical solutions described in the foregoing embodiments or make equivalent substitutions for some of the technical features. 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.< / target> < / target> < / urn> < / target> < / target> < / urn>

Claims

1. A multi-standard interactive electronic manual integration and loading device, characterized in that, include: The IETM equipment tree parsing module (101) is used to generate a hierarchical IETM equipment catalog tree and distinguish it according to whether the IETM manual is loaded. The data packet interface module (102) is used for the structure conversion of standard data packets. Data packets passing through this module are converted into standard structures before subsequent verification and import are performed. The data packet structure verification module (103) is used to check the correctness and integrity of the data packet structure selected by the user or converted by the data acquisition software. The PM verification module (104) is used to verify the legitimacy of the PM module; The resource location verification module (105) is used to verify the legality of the resource location file; The DM verification module (106) is used to verify the legality and integrity of all data modules in resource location. The registration information confirmation module (107) is used to extract manual registration information from the data packet and verify that the IETM release directory name conforms to the standard release project name specification to ensure the uniqueness of the IETM release directory name in the running platform. The data packet publishing module (108) is used to establish the data packet entity storage area in the server; The data parsing and import module (109) is used to parse data packets and registration information and insert relevant data into the database of the IETM runtime platform; The platform access module (110) is used to register the IETM manual of the equipment in the database of the running platform; The log output module (111) is used to record the process log of IETM packet loading or unloading; The IETM manual change module (112) is used to change the configuration of the IETM status; The IETM Manual Uninstall Module (113) is used to uninstall the IETM manual of the equipment and delete the release data package of the project in the release directory of the running platform.

2. The multi-standard interactive electronic manual integration and loading device according to claim 1, characterized in that, The directory tree adopts an asynchronous loading strategy, and while having the basic functions of a navigation tree, it also supports keyboard shortcut operations, allowing for "expand all" and "close all" node operations on the tree. It can also distinguish the current IETM status as needed:

1. Gray - IETM system not loaded; 2. Black - IETM system available; 3. Red - IETM system disabled or failed to load.

3. A method for integrating and loading multi-standard interactive electronic manuals using the device described in claim 1 or 2, characterized in that, Includes the following steps: Step 201: Select the IETM equipment to be loaded; Step 202: Select the pre-loaded IETM manual data package and perform structural verification on the data package; Step 203: Verify the validity and legality of the files in the data packet, and whether there are any entity files or files in formats not supported by the running platform; Step 204: Extract the necessary information about the pre-loaded IETM manual from the data packet, display it to the user, and verify the information changed by the user. Step 205: Place the data package into the corresponding folder in the runtime platform's release directory; Step 206: Insert the relevant data information of the IETM manual into the runtime platform database; Step 207: Register the equipment's IETM manual with the platform database; Step 208: Record the entire IETM loading process, including the reasons for verification failure and the reasons for unsuccessful loading, or the process details of successful loading.

4. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, PMC code compliance verification includes extracting the device's PMC code from pm.xml and verifying the PMC length, segments, and characters used according to the selected standard and version number.

5. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, Resource file integrity verification includes verifying whether the data module file and external file pointed to in pm.xml are mapped in the resource location file. If the resource location file does not contain the data module file or external file, the PM module verification fails.

6. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, The schema validity verification of the resource location file includes retrieving the schema file urn_map.xsd of the resource location file and verifying the validity of the urn_map.xml file in the data packet.

7. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, Resource entity file integrity verification includes verifying whether the relevant resource entity files exist in the urn_map.xml file.

8. The method for integrating and loading multi-standard interactive electronic manuals according to claim 7, characterized in that, Resource entity file integrity verification, specifically, extracting data from urn_map.xml. <urn>The value of the element's [name] attribute depends on <target> Different values ​​of the element's [nss] attribute will result in different truncation methods for [name] as the basis for querying entity file names. The checks are as follows:

1. Whether there is a corresponding entity file for the name dm in the dm folder; 2. Whether there is a corresponding entity file for the name icn in the illustration folder; 3. Whether there is a corresponding entity file for the name pmc in the file folder. If any are missing, a list of missing entity files will be displayed to the user, and the verification will fail.< / target> < / urn> 9. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, The schema validity verification of the DM module includes verification based on the description of dm in urn_map.xml. <target> The [type] attribute value is used to call the corresponding data module schema from the network to verify the validity of all dm entity files in the dm folder.< / target> 10. The method for integrating and loading multi-standard interactive electronic manuals according to claim 3, characterized in that, The integrity verification of DM reference files includes verifying whether all graphics and multimedia referenced in all data module files under the dm folder are described in urn_map.xml, and whether there are any graphics or multimedia formats that are not supported by the running platform.

Images