A network transmission method and system compatible with multi-vendor proprietary encryption

By integrating network interface layer and call table routing mechanism, the problems of large workload in commercial cryptographic upgrades and difficulty in equipment replacement in hydropower monitoring systems are solved. Flexible compatibility and secure and controllable switching of commercial cryptographic technologies from multiple vendors are achieved, ensuring the real-time performance and security of hydropower monitoring systems.

CN123074786APending Publication Date: 2026-11-10NANJING HEHAI NANZI HYDROPOWER AUTOMATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611253396.X
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-18
Publication Date
2026-11-10

AI Technical Summary

Technical Problem

Existing technologies for upgrading commercial cryptography in hydropower monitoring systems present several challenges, including a large workload for upgrades, difficulty in replacing commercial cryptography vendors, increased latency and single points of failure in proxy gateways, and difficulty in balancing business continuity and security compliance when commercial cryptography malfunctions.

Method used

It adopts a compatible network interface layer and call table routing mechanism, and achieves flexible compatibility and secure and controllable switching of multi-vendor commercial cryptography through default call tables, dynamic loading of vendor plugins, interface version verification and transmission level negotiation, including health monitoring and fault-tolerant switching mechanisms.

Benefits of technology

It achieved zero-intrusion transformation of existing services, reduced the workload of transformation and regression testing costs, improved the flexibility of equipment selection, avoided the latency and single point of failure risks caused by proxy gateways, and ensured the security, continuity and compliance of critical monitoring services.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123074786A_ABST
    Figure CN123074786A_ABST
Patent Text Reader

Abstract

This invention discloses a network transmission method and system compatible with multiple vendors' proprietary cryptographic protocols, belonging to the field of industrial monitoring network security communication technology. The invention establishes a compatible network interface layer between business network calls and the underlying network implementation. First, a default call table for the native network is established. Then, vendor-specific cryptographic plugins are located based on the priority of environment variables, symbolic links, and configuration files. After interface version verification, valid interfaces selectively overwrite the default call table. During communication, the proprietary cryptographic service and link status are monitored. In case of anomalies, the next transmission level is determined through negotiation between the local security policy and the peer's capability set. With mutual permission, the switch is completed through controlled reconnection and session recovery. This invention requires no modification to existing business code or the addition of a proxy gateway, supports flexible replacement of proprietary cryptographic protocols from multiple vendors, and balances security compliance with business continuity.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of network security communication and cryptographic application adaptation technology for industrial monitoring systems, and in particular to a network transmission method and system compatible with multi-vendor commercial cryptography for existing monitoring platforms such as hydropower monitoring systems. Background Technology

[0002] The hydropower monitoring system's backend handles core tasks such as data synchronization, message synchronization, monitoring terminal access, dispatch communication, and file / stream data transmission. After long-term operation, this has resulted in a large amount of business code, driver code, and communication services based on socket interfaces. With increasing requirements for cryptographic application upgrades, it is necessary to add commercial cryptographic protection capabilities to the existing communication links.

[0003] The existing commercial security upgrade plan has the following four main shortcomings:

[0004] First, the invasive modification is a large undertaking. If the underlying communication module is reconstructed, all business modules, drivers, and send / receive logic need to be rewritten to the secure communication interface of the specified vendor. This involves a wide range of changes, high regression verification costs, and the business code needs to be modified again when changing the cryptographic vendor, resulting in poor vendor replacement flexibility.

[0005] Second, proxy gateway solutions introduce additional burdens. Deploying proxy gateways or middleware at the front end of the business system to perform encryption / decryption and protocol conversion increases network hop count, maintenance workload, and single point of failure risk. It also introduces additional latency to real-time monitoring communication, affecting monitoring response speed.

[0006] Third, the interfaces of multiple vendors are not standardized. The software development kits, dynamic library entry points, interface versions, and supported network operations of different cryptographic vendors vary. Once the monitoring system is directly bound to a single vendor's interface, it is difficult to switch vendors without interrupting business operations.

[0007] Fourth, the anomaly handling mechanism is unbalanced. If there is no controlled handling mechanism when the commercial encryption service fails to initialize or malfunctions, it will directly lead to the interruption of critical monitoring services; if it is degraded to plaintext transmission without constraints, it will violate the security policy and create the risk of data leakage.

[0008] Therefore, there is an urgent need for a network transmission solution that can be compatible with multi-vendor proprietary implementations and has secure, controllable, fault-tolerant switching capabilities without modifying existing business code or adding proxy gateways. Summary of the Invention

[0009] The purpose of this invention is to overcome the shortcomings of the prior art and provide a network transmission method and system compatible with multi-vendor commercial cryptography, solving the technical problems in the prior art such as large amount of existing service transformation, difficulty in replacing commercial cryptography vendors, increased latency and single point of failure of proxy gateways, and difficulty in balancing service continuity and security compliance when commercial cryptography is abnormal.

[0010] To achieve the above objectives, the present invention adopts the following technical solution: a network transmission method compatible with multiple vendors' proprietary encryption methods, comprising the following steps:

[0011] S1: Establish a default call table that includes native network implementations. The default call table shall include at least the call interfaces corresponding to socket creation, connection establishment, data sending and receiving, message sending and receiving, address resolution, and event listening.

[0012] S2: Locate and dynamically load commercial cryptography vendor plugins according to preset priorities, obtain the vendor call table carrying the interface version identifier through the service provider's function, and perform compatibility verification on the interface version identifier;

[0013] S3: Selectively override the corresponding interfaces in the default call table with the valid interfaces in the vendor call table, and keep the interfaces that are not overridden mapped to the native network implementation;

[0014] S4: Receive network call requests from the business side through a unified network interface, and route them to the corresponding network through the overridden call table to realize the execution communication;

[0015] S5: Real-time monitoring of the status of commercial cryptography services and the health status of communication links; when an anomaly that meets the preset switching conditions occurs, the next candidate transmission level is determined based on the local security policy and the capability set of the peer. Under the premise that both communicating parties permit the candidate transmission level, the system switches to the next candidate transmission level through controlled reconnection, retry, or session recovery, and records the switching result.

[0016] In a preferred embodiment of the present invention, the preset priorities, from high to low, are: the plugin path specified by the environment variable, the plugin path pointed to by the preset soft link in the user directory, and the plugin path specified by the configuration file in the user directory; when the previous priority path fails to load, the next priority path is automatically tried.

[0017] In a preferred embodiment of the present invention, the service provider retrieval function takes the interface version number as input parameter and outputs the corresponding version of the vendor call table; when the service provider retrieval function is missing, returns the air conditioning user table, or the interface version verification fails, the default call table remains unchanged, and the plugin unavailable state is recorded.

[0018] In a preferred embodiment of the present invention, the effective interface is a non-empty function interface in the vendor call table; the selectively overridden interface types include at least one of socket creation, connection establishment, data sending and receiving, message sending and receiving, file transfer, address resolution, network option configuration, file descriptor copying, and event listening.

[0019] As a preferred embodiment of the present invention, the file descriptor, return value, error code, blocking / non-blocking behavior, and event listening behavior of the unified network interface are consistent with the original business call convention.

[0020] As a preferred embodiment of the present invention, the health status is determined based on at least one of the following: commercial cryptography service initialization result, commercial cryptography handshake result, vendor plug-in return code, link heartbeat detection result, number of consecutive communication anomalies, and key service operation status.

[0021] As a preferred embodiment of the present invention, the transmission level includes hardware encrypted transmission, software encrypted transmission and unencrypted transmission; a lower security level transmission level may be switched only if the local security policy allows it and the peer capability set indicates support.

[0022] As a preferred embodiment of the present invention, the controlled reconnection, retry, or session recovery specifically involves: setting a message identifier and a sending sequence number for the data to be sent; retransmitting unacknowledged data according to the confirmation status after the connection is restored, or restoring the session context to maintain continuous communication.

[0023] As a preferred embodiment of the present invention, the switching result includes at least: vendor identifier, interface version, fault type, transmission level before and after switching, session identifier, retry result and timestamp information.

[0024] As a preferred embodiment of the present invention, if the next candidate transmission level is not mutually agreed upon by both communicating parties, the current transmission level is maintained, and an error message matching the unified network interface is returned to the service side, or a preset fault protection strategy is executed.

[0025] The present invention also provides a network transmission system compatible with multiple vendors' proprietary encryption based on the above method, including a compatible network interface module, a default network implementation module, a vendor plug-in management module, a call table management module, a transmission strategy control module, a health monitoring and fault tolerance switching module, and an audit log module;

[0026] The compatible network interface module is used to provide a unified network call entry point to the outside world and receive network calls from the service side.

[0027] The default network implementation module is used to provide native network communication capabilities and generate a default call table;

[0028] The vendor plugin management module is used to discover and dynamically load commercial crypto vendor plugins according to preset priorities, and call the service provider to obtain the vendor call table;

[0029] The call table management module is used to verify the interface version of the vendor's call table, so that the valid interface can selectively override the default call table;

[0030] The transmission strategy control module is used to maintain the local security policy and the capability set of the peer, and to negotiate and determine the transmission level.

[0031] The health monitoring and fault tolerance switching module is used to monitor the health status of commercial cryptography services and links, and to perform controlled reconnection, retry and session recovery when an anomaly is triggered.

[0032] The audit log module is used to record the entire process information of plugin loading, interface coverage, and transmission level switching.

[0033] Compared with the prior art, the present invention has the following beneficial effects:

[0034] 1. Zero-intrusion transformation of existing services. By ensuring compatibility with the network interface layer and call table routing mechanism, the original network call conventions remain completely unchanged externally, requiring no modification to the business-side code, significantly reducing the workload of cryptographic application transformation and regression testing costs.

[0035] 2. Flexible compatibility with multi-vendor proprietary security protocols. Utilizing standardized plug-in interfaces and a partial overriding mechanism for call tables, different vendors only need to implement differentiated secure communication interfaces to connect. Vendor replacement requires no changes to the business code, enhancing the flexibility of equipment selection.

[0036] 3. No need to add a proxy gateway. The commercial encryption capability is embedded in the communication link in the form of library functions, without adding extra network nodes or forwarding latency. It also avoids the single point of failure risk and operation and maintenance costs brought by proxy gateways, and is suitable for scenarios with high real-time requirements such as water and electricity monitoring.

[0037] 4. Secure and controllable fault-tolerant switching. Transmission level downgrades must be approved by both the local security policy and the peer's capabilities, and unrestricted plaintext downgrades are prohibited. At the same time, through controlled reconnection and session recovery mechanisms, the continuity of critical monitoring services is guaranteed to the maximum extent under the premise of security and compliance.

[0038] 5. Full-process auditability and traceability. The entire process of plug-in loading, interface coverage, and fault switching is audited, which facilitates security and compliance verification and fault location, and meets the audit requirements of information security protection and cryptographic application of industrial control systems. Attached Figure Description

[0039] Figure 1 This is a diagram illustrating the overall architecture of a multi-vendor proprietary network transmission system as described in this invention.

[0040] Figure 2 This is a flowchart illustrating the discovery, version verification, and call table overriding of commercial cryptography vendor plugins in an embodiment of the present invention.

[0041] Figure 3 This is a flowchart of transmission level health monitoring and dual-end permission fault-tolerant switching in an embodiment of the present invention;

[0042] Figure 4 This is a schematic diagram illustrating the interaction between the monitoring service module, the compatible network interface layer, and the peer monitoring terminal in an embodiment of the present invention. Detailed Implementation

[0043] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0044] like Figure 1 As shown in the figure, the network transmission system compatible with multi-vendor commercial cryptography described in this embodiment is deployed between the business side and the underlying network implementation of the hydropower monitoring system. It is divided into three layers: hydropower monitoring business side, pluggable commercial cryptography transmission compatibility layer, and commercial cryptography service and transmission bearer side.

[0045] The hydropower monitoring service side includes existing business modules, such as database synchronization service, message service, terminal communication service, file transfer service, and streaming media service. These modules are developed based on the original socket interface, and the code remains unchanged.

[0046] The pluggable commercial cryptographic transmission compatibility layer (sc_socket) is the core layer of this invention. It includes existing Socket-compatible APIs, runtime plugin discovery and dual-end capability negotiation / session state machine, function table partial overriding mechanism, integrity verification and audit logging functions. This layer provides a fully compatible unified network interface to business modules above and routes to different network implementations below.

[0047] The commercial cryptography service and transmission bearer side includes commercial cryptography implementations from multiple vendors as well as native Socket implementations, such as vendor A's commercial cryptography implementation, vendor B's commercial cryptography implementation, software commercial cryptography implementation, and native Socket transmission.

[0048] The system is modularly divided as follows: compatible network interface module, default network implementation module, vendor plug-in management module, call table management module, transmission policy control module, health monitoring and fault-tolerant switching module, and audit log module. These modules work together to achieve compatible access and secure fault-tolerant transmission for multi-vendor proprietary encryption.

[0049] like Figure 2 As shown in the figure, this embodiment details the discovery, version verification, and call table overriding process for commercial cryptographic vendor plugins. The specific steps are as follows:

[0050] The first step is to initialize the default call table. Upon system startup, all native network functions, including native socket functions, connection functions, send functions, receive functions, message functions, file transfer functions, address resolution functions, and event listener functions, are written into the default call table. This default call table serves as a fallback, ensuring that business communication can still proceed normally even without proprietary plugins or when plugins are malfunctioning.

[0051] The second step involves discovering and loading vendor plugins based on priority. The vendor plugin management module attempts to locate plugins sequentially according to a three-tier priority level:

[0052] First priority: Read the plugin path specified in the environment variable and load the corresponding dynamic library directly;

[0053] Second priority: If the environment variables are not configured or loading fails, read the plugin path pointed to by the preset symbolic link in the user directory and load it;

[0054] Third priority: If the symbolic link method fails, load the plugin from the configuration file specified in the user's directory.

[0055] If each level fails to load, it will automatically downgrade to try the next level; if all levels fail, it will maintain the original default implementation.

[0056] The third step is to obtain and verify the vendor call table. After the plugin is successfully loaded, the preset service provider retrieval function is called, passing the interface version number as an input parameter to obtain the corresponding version's vendor call table. If the retrieval function does not exist, returns an air-conditioning vendor call table, or the returned interface version is incompatible with the system's supported version, the plugin is determined to be unusable, the default call table is not overwritten, and a plugin unusable log is recorded.

[0057] The fourth step is selective overwriting of valid interfaces. The call table management module iterates through the function interfaces in the vendor's call table one by one, and only overwrites the corresponding positions in the default call table with non-null valid function pointers; for interfaces not implemented by the vendor, the native network implementation continues to be used.

[0058] For example, vendor A can provide only four types of interfaces: secure socket creation, connection, and data sending and receiving, while the remaining interfaces such as address resolution, event listening, and file transfer can continue to use the native implementation; vendor B can provide another set of secure sockets and message sending and receiving interfaces without requiring the monitoring business module to rewrite the calling logic.

[0059] Through this "default fallback + partial coverage" mechanism, commercial cryptography vendors only need to implement differentiated secure communication capabilities to access the system without having to completely replicate all network operations, which greatly reduces the vendor adaptation costs while ensuring the integrity of system functions.

[0060] like Figure 3 , Figure 4 As shown in the figure, this embodiment details the transmission level negotiation and fault-tolerant switching mechanism in the communication process.

[0061] The first step is capability negotiation during the connection establishment phase. When establishing a connection, the local network interface layer sends information such as the set of supported transmission levels, security policy identifiers, and interface versions to the peer, while simultaneously receiving the capability set and policy identifiers returned by the peer. The system selects the highest transmission level that is supported by both parties and satisfies the local security policy as the initial transmission level. The transmission levels, from highest to lowest, are: hardware encrypted transmission, software encrypted transmission, and unencrypted transmission.

[0062] Secondly, there is runtime health monitoring. The health monitoring and fault-tolerant switching module continuously monitors the status of the cryptographic service and the link status. Monitoring indicators include: the initialization result of the cryptographic service, whether the cryptographic handshake was successful, the error codes returned by the vendor plugin, whether the link heartbeat is normal, the number of consecutive communication anomalies, and whether the key service is online. When the above indicators meet the preset anomaly trigger rules, a fault requiring switching is determined to have occurred.

[0063] Then comes the tiered fault-tolerant switching with dual-end permissions. In the event of an anomaly, the system does not immediately degrade to plaintext transmission, but instead executes the following process:

[0064] From the candidate levels lower than the current level, select the level that meets both the conditions of "local security policy allows" and "peer capability set supports" as the candidate transmission level;

[0065] If a valid candidate level exists, the current abnormal session is isolated, and a new alternative session is established according to the candidate level.

[0066] Based on message identifier, sending sequence number and acknowledgment sequence number, controlled reconnection and session recovery are performed: data that has been acknowledged by the peer will not be retransmitted, and data that has not been acknowledged but is allowed to be retried will be retransmitted to avoid duplicate messages causing business anomalies.

[0067] After the switch is complete, update the session state and transport class.

[0068] If no candidate level is found that is permitted by both parties after screening, the downgrade will not be performed. Instead, the current transmission level will be maintained, and a compatible error message will be returned to the service layer. Alternatively, a preset service protection policy will be triggered to prevent unauthorized plaintext transmission.

[0069] The audit logging module tracks key operations throughout the entire process, including: plugin loading events (vendor identifier, interface version, loading path type, loading result), interface overriding events (overridden interface type, overriding result), and transmission level switching events (fault category, level before and after switching, session identifier, number of retries, processing result, timestamp). Audit logs can be integrated with the monitoring system's log service or a security audit platform to meet compliance audit requirements.

[0070] In other extended embodiments:

[0071] The priority of plugin positioning can be flexibly adjusted through configuration files, and is not limited to three levels;

[0072] The call table can be maintained independently by process, business module, connection group or session, supporting different business secrets to be adopted by different business secrets.

[0073] The transmission level can be further subdivided, for example, supporting the coexistence of multiple hardware commercial encryption cards and multiple software commercial encryption implementations;

[0074] The controlled recovery mechanism can be extended to support application-layer transaction compensation, breakpoint resumption, and other methods to adapt to the reliability requirements of different services.

[0075] The above description is merely a preferred embodiment of the present invention and is not intended to limit the scope of the invention. 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 network transmission method compatible with multiple vendors' proprietary encryption methods, characterized in that, Includes the following steps: S1: Establish a default call table that includes native network implementations. The default call table shall include at least the call interfaces corresponding to socket creation, connection establishment, data sending and receiving, message sending and receiving, address resolution, and event listening. S2: Locate and dynamically load commercial cryptography vendor plugins according to preset priorities, obtain the vendor call table carrying the interface version identifier through the service provider's function, and perform compatibility verification on the interface version identifier; S3: Selectively override the corresponding interfaces in the default call table with the valid interfaces in the vendor call table, and keep the interfaces that are not overridden mapped to the native network implementation; S4: Receive network call requests from the business side through a unified network interface, and route them to the corresponding network through the overridden call table to realize the execution communication; S5: Real-time monitoring of the status of commercial cryptography services and the health status of communication links; when an anomaly that meets the preset switching conditions occurs, the next candidate transmission level is determined based on the local security policy and the capability set of the peer. Under the premise that both communicating parties permit the candidate transmission level, the system switches to the next candidate transmission level through controlled reconnection, retry, or session recovery, and records the switching result.

2. The network transmission method compatible with multiple vendors' proprietary encryption as described in claim 1, characterized in that: In S2, the preset priorities from high to low are: the plugin path specified by the environment variable, the plugin path pointed to by the preset soft link in the user directory, and the plugin path specified by the configuration file in the user directory; when the previous priority path fails to load, the next priority path is automatically tried.

3. The network transmission method compatible with multi-vendor proprietary encryption as described in claim 1, characterized in that: In S2, the service provider obtains a function that takes the interface version number as input parameter and outputs the corresponding version of the vendor call table. When the service provider fails to retrieve a function, returns an air conditioning table, or the interface version verification fails, the default call table remains unchanged, and the plugin's unavailable status is recorded.

4. The network transmission method compatible with multiple vendors' proprietary encryption as described in claim 1, characterized in that: In S3, the valid interface is a function interface that is not empty in the vendor call table; the selectively overridden interface types include at least one of socket creation, connection establishment, data sending and receiving, message sending and receiving, file transfer, address resolution, network option configuration, file descriptor copying, and event listening.

5. The network transmission method compatible with multi-vendor proprietary encryption as described in claim 1, characterized in that: In S4, the file descriptor, return value, error code, blocking / non-blocking behavior, and event listening behavior of the unified network interface are consistent with the original business call convention.

6. The network transmission method compatible with multiple vendors' proprietary encryption as described in claim 1, characterized in that: In S5, the health status is determined based on at least one of the following: commercial cryptography service initialization result, commercial cryptography handshake result, vendor plug-in return code, link heartbeat detection result, number of consecutive communication anomalies, and key service operation status; the transmission level includes hardware commercial cryptography transmission, software commercial cryptography transmission, and unencrypted transmission; a lower security level transmission level can only be switched to if the local security policy allows it and the peer capability set indicates support.

7. The network transmission method compatible with multiple vendors' proprietary encryption as described in claim 1, characterized in that: The controlled reconnection, retry, or session recovery specifically involves: setting a message identifier and a sending sequence number for the data to be sent; retransmitting unacknowledged data based on the confirmation status after the connection is restored; or restoring the session context to maintain continuous communication.

8. The network transmission method compatible with multiple vendors' proprietary encryption as described in claim 1, characterized in that: The switching result includes at least: vendor identifier, interface version, fault type, transmission level before and after the switching, session identifier, retry result and timestamp information.

9. The network transmission method compatible with multi-vendor commercial cryptography according to claim 1, characterized in that: If the next candidate transmission level is not mutually agreed upon by both communicating parties, the current transmission level is maintained, and an error message matching the unified network interface is returned to the service side, or a preset fault protection strategy is executed.

10. A network transmission system compatible with multi-vendor proprietary cryptography based on the method of any one of claims 1-9, characterized in that: It includes a compatible network interface module, a default network implementation module, a vendor plugin management module, a call table management module, a transmission policy control module, a health monitoring and fault tolerance switching module, and an audit log module; The compatible network interface module is used to provide a unified network call entry point to the outside world and receive network calls from the service side. The default network implementation module is used to provide native network communication capabilities and generate a default call table; The vendor plugin management module is used to discover and dynamically load commercial crypto vendor plugins according to preset priorities, and call the service provider to obtain the vendor call table; The call table management module is used to verify the interface version of the vendor's call table, so that the valid interface can selectively override the default call table; The transmission strategy control module is used to maintain the local security policy and the capability set of the peer, and to negotiate and determine the transmission level. The health monitoring and fault tolerance switching module is used to monitor the health status of commercial cryptography services and links, and to perform controlled reconnection, retry and session recovery when an anomaly is triggered. The audit log module is used to record the entire process information of plugin loading, interface coverage, and transmission level switching.