Channel management method and system based on red-black isolation architecture
By configuring peer device information and control commands in a red-black isolation architecture, the channel management method solves the problems of insufficient security and operational flexibility of channel management control data, realizes secure channel management under multiple channel types and triggering methods, and improves the security and flexibility of the system.
Patent Information
- Application Number
- CN202511920128.4
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-12-18
- Publication Date
- 2026-03-17
AI Technical Summary
Existing technologies lack effective channel management mechanisms under red-black isolation architectures, resulting in insufficient security and operational flexibility of channel management control data.
In the red zone, the policy information of the peer device is configured, a control message carrying the peer device information and control instructions is generated, and after the legality is verified by the isolation unit, it is forwarded to the black zone. The black zone performs channel link establishment or dismantling operation according to the control instructions, and feeds back the results to the user through a closed-loop feedback mechanism.
It achieves secure channel management under multiple channel types and triggering methods in a red-black isolation architecture, improving the security and flexibility of channel management, reducing redundant operations, and improving system operating efficiency and user experience.
Smart Images

Figure CN121690775A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of channel management technology, and specifically to a channel management method and system based on a red-black isolation architecture. Background Technology
[0002] With the rapid development of information technology, especially against the backdrop of the widespread application of technologies such as cloud computing and big data, data security and network reliability have become the focus of attention across various industries. Traditional network security protection measures, such as firewalls and encryption technologies, mainly target the security of business data packet transmission, while paying less attention to the protection of channel management and control data. Especially under a red-black isolation architecture, how to achieve secure channel management while maintaining physical or logical isolation between the red and black zones, and ensure the legitimacy and validity of channel management and control data, remains a technical challenge. Existing technologies often lack effective mechanisms to guarantee the security, flexibility, and adaptability to various triggering methods of channel management data during channel establishment, maintenance, and teardown. Summary of the Invention
[0003] This application provides a channel management method and system based on a red-black isolation architecture, which addresses the technical problems of existing technologies that rely heavily on a single channel type for communication, lack security protection for channel management control data, and have insufficient operational flexibility.
[0004] In a first aspect, this application provides a channel management method based on a red-black isolation architecture. The method includes: configuring policy information of peer devices in the red zone; in response to a channel management event based on the policy information, generating a control message carrying peer device information and control instructions by the channel management module in the red zone, and sending the control message to an isolation unit; in the isolation unit, verifying the legitimacy of the control message from the red zone, and forwarding the verified control message to the black zone; in the black zone, parsing the control message, and assembling and sending a channel management message to the peer device in the red zone according to the parsed peer device information and control instructions, so as to perform the corresponding channel establishment or disassembly operation.
[0005] Secondly, this application provides a channel management system based on a red-black isolation architecture. The system includes: a policy information configuration module for configuring policy information of peer devices in the red zone; a control message generation module for responding to channel management events based on the policy information, generating control messages carrying peer device information and control commands by the channel management module in the red zone, and sending the control messages to the isolation unit; a legitimacy verification module for verifying the legitimacy of control messages from the red zone in the isolation unit, and forwarding verified control messages to the black zone; and a channel management module for parsing the control messages in the black zone, assembling and sending channel management messages to the peer devices in the red zone based on the parsed peer device information and control commands, to perform corresponding channel establishment or disassembly operations.
[0006] One or more technical solutions provided in this application have at least the following technical effects or advantages: This application provides a channel management method and system based on a red-black isolation architecture, relating to the field of channel management technology. It configures peer device policy information in the red zone, generates control messages, and forwards them to the black zone after verification by the isolation unit. The black zone executes channel connection establishment or disconnection operations according to control commands and feeds back the operation results to the user through a closed-loop feedback mechanism. This solves the technical problems of existing technologies that rely heavily on a single channel type for communication, lack security protection for channel management control data, and have insufficient operational flexibility. It achieves secure channel management under multiple channel types and triggering methods based on a red-black isolation architecture and multiple triggering mechanisms, improving the security and flexibility of channel management operations. Attached Figure Description
[0007] Figure 1 A schematic diagram of a channel management method based on a red-black isolation architecture provided in this application; Figure 2 This application provides a schematic diagram of a channel management system based on a red-black isolation architecture.
[0008] Explanation of reference numerals in the attached diagram: Policy information configuration module 11, control message generation module 12, legality verification module 13, channel management module 14. Detailed Implementation
[0009] This application provides a channel management method and system based on a red-black isolation architecture to solve the technical problems of existing technologies that rely on a single channel type for communication, lack security protection for channel management control data, and have insufficient operational flexibility.
[0010] Example 1, as Figure 1As shown, this application provides a channel management method based on a red-black isolation architecture, the method comprising: P10: Configure policy information for peer devices in the red zone.
[0011] Specifically, the first step is to configure the policy information for the peer device within the red zone intranet environment. This step is fundamental to the entire channel management process, providing accurate and secure identification of the peer device for subsequent channel establishment and teardown operations, ensuring that the system can communicate securely with legitimate peer devices.
[0012] The red zone, as an internal network area, is a high-security area primarily responsible for handling plaintext data and management operations directly related to users. When configuring policy information for peer devices in the red zone, key information about the peer devices needs to be entered into the system through the configuration management module. This key information includes the peer device's external network address, device certificate, and other necessary parameters for authentication and communication negotiation. This configuration is based on the Security Policy Database (SPD) and the Security Association Database (SAD). The SPD stores security policies that define the security requirements for data transmission, such as which data needs encryption and which data requires authentication; while the SAD stores the specific parameters required to establish secure communication with the peer device, such as encryption keys and authentication algorithms.
[0013] In practice, the configuration management module provides a user interface or configuration interface for system administrators or users to input relevant information about the peer device. This information is stored in the SPD and SAD and is retrieved during subsequent channel management processes. For example, when the system needs to establish a channel with the peer device, the channel management module retrieves the security policy from the SPD and the parameters required for establishing secure communication with the peer device from the SAD, thereby generating a control message carrying peer device information and control commands. This process not only provides the necessary data support for channel establishment and teardown but also ensures communication security from the source through strict configuration of policy information, preventing security risks such as unauthorized device access or data leakage.
[0014] To ensure the accuracy and completeness of configuration information, the system performs a series of verification operations during the configuration process. For example, it checks whether the entered external network address complies with network protocol requirements, whether the device certificate is valid and not revoked, and whether other parameters comply with security policy regulations. Only after all configuration information passes verification will it be officially written to the SPD and SAD. Furthermore, the system regularly updates and maintains the configuration information to adapt to changes in the network environment and security policy updates.
[0015] By configuring policy information for peer devices in the red zone, a solid foundation can be provided for subsequent channel management operations, ensuring that the system can communicate with peer devices securely and efficiently.
[0016] P20: In response to a channel management event based on the policy information, the channel management module of the red zone generates a control message carrying peer device information and control instructions, and sends the control message to the isolation unit.
[0017] Furthermore, step P20 in this embodiment of the application also includes: P21: The channel management event is triggered by one of the following methods: manual triggering, audit triggering, or transmission service triggering; P22: Among them, the manually triggered channel management event is an XML message carrying preset channel type or channel priority information; P23: The audit triggered channel management event is generated after the service message fails to match the unnegotiated security policy in the isolation unit and is sent to the red zone; P24: The transmission service triggered channel management event is a fixed-format message forwarded by a non-user of this device after establishing a connection with the transmission service proxy module through a TCP connection.
[0018] It should be understood that, in response to channel management events based on policy information, the channel management module in the red zone generates a control message carrying information about the peer device and control commands, and sends the control message to the isolation unit. This process is the core of implementing the channel management function, ensuring that the management intent of the red zone can be accurately transmitted to the isolation unit, thereby guiding subsequent channel operations. To achieve this objective, this application further refines the triggering methods of channel management events, including manual triggering, audit triggering, and transmission service triggering, to adapt to different application scenarios and user needs.
[0019] First, one way to trigger channel management events is manually. In this mode, the user actively initiates channel management operations through the configuration management module. The user can specify the channel type or set the channel priority according to actual needs to manage specific channels. Specifically, the user inputs relevant channel management parameters through the configuration management module. These parameters include, but are not limited to, the identification information of the peer device, the channel type (such as Ethernet channel, 4G channel, PSTN channel, ISDN channel, etc.), and the channel priority information. The configuration management module encapsulates these parameters into an XML message. XML messages, as a standardized data exchange format, can clearly describe the specific content of the channel management event. After receiving the XML message, the channel management module can parse the information and generate a corresponding control message. This control message contains peer device information and control commands, and is then sent to the isolation unit.
[0020] Secondly, channel management events can also be triggered by auditing. Audit-triggered channel management events occur when a service packet fails to match an unnegotiated security policy within the isolation unit. When the isolation unit receives a service packet from the red zone, it performs a match according to preset policy rules. If the packet fails to negotiate with the existing security policy, an audit event is triggered. At this point, the isolation unit sends audit information to the red zone. Upon receiving this information, the channel management module generates a control message according to preset rules and executes the relevant channel management operations. This triggering method ensures timely initiation of channel management operations when a service packet fails to meet security policy requirements, guaranteeing system security and stability.
[0021] Finally, channel management events can also be triggered by transport services. Transport service-triggered channel management events occur after a non-user establishes a connection with the transport service proxy module via TCP. In some application scenarios, other devices may need to establish channel connections with peer devices through this device. In this case, these devices will establish communication with this device's transport service proxy module via TCP and send a fixed-format message. Upon receiving the message, the transport service proxy module forwards it to the channel management module. The channel management module parses the fixed-format message, converts it into a channel management event, and generates a corresponding control message. This control message also contains peer device information and control commands, and is subsequently sent to the isolation unit. This triggering method enables this device to support the channel management needs of other devices, enhancing the system's versatility and flexibility.
[0022] During the generation of control messages, the channel management module generates control messages conforming to a specific format based on different triggering methods and user-input parameters. The format and content of the control messages are carefully designed to ensure they accurately describe the details of channel management events, including the identification information of the peer device, the control commands to be executed (such as link establishment or disconnection operations), and information related to channel type or priority. The accuracy and completeness of this information directly affect the isolation unit's processing of control messages and the assembly and transmission of channel management messages by the black zone.
[0023] Once the control message is generated, the channel management module sends it to the isolation unit. This process is completed through a dedicated communication channel between the red zone and the isolation unit, ensuring the security and reliability of the control message during transmission. After receiving the control message, the isolation unit verifies its legitimacy to ensure it complies with preset security policies and rules, thereby avoiding potential security risks.
[0024] Furthermore, when the channel management event is triggered manually, step P20 in this embodiment further includes: P25: If the channel management event is configured as a preset channel type, then only the preset channel type will be used to initiate the connection establishment operation; wherein, the channel type includes Ethernet channel, 4G channel, Public Switched Telephone Network (PSTN) channel, and Integrated Services Digital Network (ISDN) channel. P26: If the channel management event is configured as a channel type priority selection, then different channel types will be tried sequentially according to the configured priority order to initiate the connection establishment operation until the connection is successfully established or all attempts fail.
[0025] Optionally, when the channel management event is triggered manually, the manually triggered channel management event allows the user to configure the channel type or channel type priority according to actual needs, thereby providing greater flexibility and adaptability in the link establishment process.
[0026] First, when the channel management event is configured with a preset channel type, the system will only initiate connection establishment operations using the configured preset channel type. At this time, the channel management module in the red zone will select only the specified channel type for connection establishment based on the user's configuration. For example, if the user selects Ethernet channel as the preset channel type, the system will perform connection establishment operations on this channel type, and other channel types will not be attempted. Available channel types include Ethernet channels, 4G channels, Public Switched Telephone Network (PSTN) channels, and Integrated Services Digital Network (ISDN) channels. Each channel type has different advantages and applicability depending on its network characteristics and application scenarios. For example, Ethernet channels are often used for high-speed data transmission within a local area network, while 4G channels are suitable for application scenarios in mobile network environments with high bandwidth and speed requirements. Based on actual needs, users can choose the channel type that best suits their current communication requirements.
[0027] Next, if the user has configured channel type priority selection, the system will attempt to establish a connection using different channel types sequentially according to the configured priority order, until a channel is successfully established or all attempts fail. Specifically, the channel management module will first attempt to establish a connection using the highest priority channel type. If connection establishment fails for this channel type, for example, due to network unavailability or the peer device not supporting the channel type, the system will automatically switch to the next highest priority channel type to continue attempting connection establishment. This process will continue until connection establishment is successful, or all configured channel type attempts fail. In this way, the system can provide alternative solutions while ensuring the user's priority selection, thus ensuring the reliability and success rate of connection establishment operations.
[0028] For example, a user can set the 4G channel as the highest priority to take advantage of its high-speed transmission; the PSTN channel as the second highest priority to cope with the unavailability of the 4G network; and finally, the ISDN channel as the lowest priority as a backup plan. During the connection establishment process, the system will first try the 4G channel, and if it fails, it will automatically switch to the PSTN channel, and finally try the ISDN channel. This priority selection mechanism not only improves the adaptability of the system, but also ensures communication continuity in different network environments.
[0029] In practice, the channel management module generates corresponding control messages based on the channel type or priority information entered by the user in the configuration management module. These control messages explicitly instruct the isolation unit to use a specific channel type or to attempt different channel types according to priority. Upon receiving the control message, the isolation unit processes it accordingly and feeds the results back to the channel management module. If the link establishment is successful, the channel management module records relevant information and notifies the user; if all attempts fail, it reports the link establishment failure to the user. Through this priority setting, the system can maximize the use of existing resources and ensure that channel establishment is completed as quickly as possible in various channel environments.
[0030] Furthermore, step P20 in this embodiment of the application also includes: P27: When the channel management event is audit-triggered, after the peer device successfully establishes a link and completes security negotiation, the isolation unit stops sending audit-triggered instructions for service packets that match the same policy.
[0031] In one possible embodiment of this application, when the channel management event is audit-triggered, after the peer device successfully establishes a link and completes security negotiation, the isolation unit will stop sending audit trigger instructions for service packets that match the same policy, thereby optimizing the system's operating efficiency, avoiding unnecessary audit trigger operations, and ensuring that the system can operate efficiently during communication after security negotiation is completed.
[0032] Specifically, in audit-triggered scenarios, when a service packet passes through the isolation unit, its five-tuple information—source IP, destination IP, source port, destination port, and protocol type—is matched against the security policy configured in the isolation unit. If the matching result indicates that the security policy corresponding to the service packet is in an unnegotiated state, and the audit log upload switch is enabled, the isolation unit will trigger an audit event, generate an audit log, and send an audit trigger command to the channel management module in the red zone. Upon receiving the audit trigger command, the channel management module will initiate a connection establishment operation to establish a secure communication channel with the peer device.
[0033] During the link establishment process, the channel management module generates a control message based on the information in the audit log and sends it to the black zone through the isolation unit. Upon receiving the control message, the black zone assembles and sends a channel management message to the peer device based on the peer device information and control commands contained within, thus executing the link establishment operation. If the link establishment is successful, the peer device will respond with an acknowledgment message. Upon receiving this message, the black zone will further complete the security negotiation process to ensure communication security.
[0034] Once security negotiation is complete, communication between the red zone and the peer device is securely established. At this point, the isolation unit will stop sending audit trigger commands again for subsequent service packets matching the same policy. The core purpose of this behavior is to avoid unnecessary duplicate audit operations, thereby improving system efficiency and performance.
[0035] Specifically, after security negotiation is completed, both parties establish a trust relationship, and the corresponding security policy takes effect. In this case, the isolation unit remembers the policy, and as long as subsequent service packets conform to the security policy, audit events will not be triggered again. This means that after the channel is established and security negotiation is completed, the audit mechanism becomes more efficient, auditing only packets that are not negotiated for the first time, and not repeatedly performing audit operations on packets with established trust relationships. In this way, the system can focus on processing actual communication data, rather than frequently triggering audits and establishing connections, thereby ensuring the efficiency and smoothness of communication.
[0036] This mechanism optimizes the audit triggering process, avoiding performance losses caused by repeated audits while maintaining rigorous scrutiny of first-time unnegotiated messages. This mechanism ensures that audit operations are performed only when necessary, effectively reducing redundant operations and improving the overall system's response speed and stability.
[0037] Furthermore, step P20 in this embodiment of the application also includes: P28: When the channel management event is triggered by the transmission service, after the operation is completed, the connection establishment or disconnection result will be returned to the non-user who initiated the operation via the TCP connection through the transmission service proxy module.
[0038] Specifically, when a channel management event is triggered by a transmission service, after completing the link establishment or dismantling operation, the system returns the operation result to the non-user who initiated the operation through the transmission service proxy module, so as to ensure that the user can receive operation feedback in a timely manner and enhance the interactivity of the system and the user experience.
[0039] In scenarios triggered by transmission services, non-users of this device, such as other network devices or terminal users, establish communication with the device's transmission service proxy module via a TCP connection and send a fixed-format connection establishment or disconnection request message. Upon receiving the request, the transmission service proxy module forwards it to the channel management module. The channel management module parses the request content, generates the corresponding control message, and sends the control message to the black zone through the isolation unit to initiate the connection establishment or disconnection operation.
[0040] After establishing or dismantling a link in the black zone, the result (success or failure) is fed back to the channel management module in the red zone. Upon receiving the result, the channel management module encapsulates it into a message of a specific format and returns it to the non-user who initiated the operation via the transmission service proxy module. This process ensures that the user can understand the operation status in real time, allowing them to make subsequent operations or decisions based on the feedback.
[0041] For example, when a user not connected to this device sends a link establishment request to this device via a TCP connection, the device's transmission service proxy module receives the request and forwards it to the channel management module. The channel management module generates a control message based on the request content and sends it to the black zone through the isolation unit. After completing the link establishment operation, the black zone sends the link establishment result, such as "link establishment successful" or "link establishment failed," back to the channel management module. The channel management module then encapsulates the link establishment result into a message and returns it to the user not connected to this device through the transmission service proxy module. If the link establishment is successful, the user can begin data transmission; if the link establishment fails, the user can make corresponding adjustments or re-initiate the request based on the reason for the failure.
[0042] Through the above mechanism, the embodiments of this application not only provide powerful channel management capabilities, but also enable flexible and efficient communication with external devices via the transmission service module. This approach provides the system with high scalability, supporting external users to remotely initiate channel management operations and receive operation results, effectively improving system availability and user experience.
[0043] P30: In the isolation unit, the legality of control messages from the red zone is verified, and the verified control messages are forwarded to the black zone.
[0044] Furthermore, step P30 in this embodiment of the application also includes: P31: The control message is encrypted and decrypted in the isolation unit, and the five-tuple information of the control message is extracted; P32: The five-tuple information is matched with the pre-configured security policy. If the match is successful, the verification is passed. The five-tuple information includes source IP, destination IP, source port, destination port, and protocol type.
[0045] It should be understood that after the channel management module in the red zone generates a control message carrying information about the peer device and control commands, this message is transmitted to the isolation unit through a dedicated communication channel between the red zone and the isolation unit. Upon receiving the control message, the isolation unit first encrypts and decrypts it. The control message may involve encryption during transmission to protect the confidentiality and integrity of the data. Therefore, the isolation unit must process the message using an encryption and decryption mechanism to ensure that only the decrypted message can proceed to the subsequent verification process. The encryption and decryption can employ preset encryption algorithms, such as AES or other symmetric encryption algorithms. These algorithms ensure that the message content will not be stolen or tampered with by unauthorized third parties during data transmission. The decrypted control message contains detailed information about the peer device, control commands, and other data related to channel management.
[0046] After encryption and decryption, the isolation unit further extracts the five-tuple information from the control message. This five-tuple information is a crucial identifier in network communication, including the source IP address, destination IP address, source port number, destination port number, and protocol type. This information collectively defines the message's transmission path and communication context within the network, forming the basis for security policy matching. Specifically, the source and destination IP addresses identify the sender and receiver of the message; the source and destination port numbers further refine the specific port information for communication; and the protocol type specifies the network protocol used by the message, such as TCP or UDP.
[0047] After extracting the 5-tuple information, the isolation unit further matches this information against pre-configured security policies. These pre-configured security policies are stored in the isolation unit's Security Policy Database (SPD), defining which communications are permitted and which are prohibited. The matching process checks each field in the 5-tuple information one by one to ensure it conforms to the preset security rules. For example, if a security policy specifies that only packets from a specific source IP address are allowed to communicate through a specific port, the isolation unit checks whether the source IP address and port number of the control packet match the policy. Furthermore, the protocol type is also checked to ensure that the packet transmission method complies with security requirements.
[0048] If the five-tuple information matches the pre-configured security policy, the verification is successful. This means that the content and transmission context of the control message meet the system's security requirements, and the isolation unit forwards the control message to the black zone to continue subsequent channel management operations. During forwarding, the isolation unit may re-encrypt the control message to ensure its security during transmission in the black zone. Conversely, if the match fails, the control message is discarded, and the isolation unit generates corresponding log records for system administrators to perform subsequent security analysis and auditing.
[0049] This process provides strong security for the entire channel management, avoiding potential security risks and the transmission of illegal data. It not only improves the security of the system, but also ensures the legality and stability of data transmission.
[0050] P40: In the black zone, the control message is parsed, and based on the parsed peer device information and control instructions, a channel management message is assembled and sent to the peer device in the red zone to perform the corresponding channel establishment or dismantling operation.
[0051] Specifically, after the isolation unit forwards the validated control message to the black zone, the black zone's processing module first parses the received control message. The parsing process aims to extract key information contained in the control message, including detailed information about the peer device, such as its IP address and port number, as well as specific control commands, such as link establishment or dismantling commands. By identifying the format and protocol of the control message, the parsing process accurately extracts this information, providing necessary data support for subsequent channel management operations.
[0052] After parsing the peer device information and control commands, the processing module in the black zone assembles channel management messages based on this information. Channel management messages are standardized messages used for communication with peer devices, and their format and content are designed according to specific network protocols and security requirements. For example, if the control command is a link establishment operation, the channel management message will contain the necessary parameters for establishing a secure communication channel, such as encryption keys, authentication information, and channel type; if the control command is a link termination operation, the channel management message will contain instructions and related parameters for terminating the communication channel.
[0053] After assembly, the black zone's processing module sends channel management messages to the red zone's peer device via the network. The transmission process must adhere to the relevant network protocols to ensure the messages accurately reach the peer device. During transmission, the black zone encrypts the channel management messages to ensure communication security.
[0054] After receiving a channel management message, the peer device will perform the corresponding channel establishment or disconnection operation according to the message content. If the operation is successful, the peer device will send a response message to confirm the operation result. After receiving the response message, the black zone will further process the response information and feed the operation result back to the channel management module in the red zone. If the connection establishment operation is successful, the system will record relevant channel information for subsequent data transmission; if the disconnection operation is successful, the system will clear the relevant channel resources to ensure the normal operation of the system.
[0055] In this way, channel management operations between the black and red zones are realized. Black zone devices parse control messages and initiate channel management operations, ensuring that channels can be flexibly established and torn down as needed. The entire process relies on a red-black isolation architecture, ensuring effective isolation between internal and external networks and secure data transmission, while also achieving flexible channel management and operational control.
[0056] Furthermore, performing the corresponding channel establishment or dismantling operation also includes response processing steps: P41: Receive response messages from peer devices; P42: The black zone parses the response messages and encapsulates the results into a response control message in a preset format; P43: The response control message is forwarded back to the channel management module in the red zone via the isolation unit. The channel management module in the red zone updates the link status according to the response control message and feeds back the operation results to the user.
[0057] Optionally, performing the link establishment or dismantling operation of the corresponding channel not only includes sending channel management messages, but also covers the processing of the response from the peer device. This ensures that the system can update the link status in a timely manner based on the feedback from the peer device and feed back the operation results to the user, thereby realizing a closed-loop channel management mechanism.
[0058] Specifically, after a device in the black zone completes a link establishment or dissolution operation, it waits for a response from the peer device, i.e., it receives a response message from the peer device. This response message is used to confirm whether the peer device successfully processed the channel management request, or whether any errors or anomalies occurred. The response message contains key information about the channel status, such as whether link establishment was successful, whether dissolution was successful, and whether any errors occurred.
[0059] Upon receiving a response message from the peer device, the black zone first parses the message to extract key information, including the operation result status code, error messages (if any), and other response-related data. After parsing, the black zone encapsulates the result from the response message into a pre-formatted response control message. This response control message contains the peer device's response status, ensuring efficient and accurate information transmission between the red and black zones, while also facilitating further processing by the red zone's channel management module.
[0060] Next, the response control message is forwarded back to the channel management module in the red zone via the isolation unit. During forwarding, the isolation unit performs necessary security checks and processing on the received response control message, such as verifying its integrity and validity, ensuring that only messages conforming to the security policy can be forwarded to the red zone. Upon receiving the response control message, the channel management module in the red zone updates the link status based on the result information in the message. For example, if the response message indicates successful link establishment, the channel management module records the link establishment status and updates the relevant parameters in the system; if the response message indicates link establishment failure, the channel management module records the reason for the failure and cleans up the relevant temporary resources.
[0061] Finally, the channel management module feeds back the operation results to the user. This feedback process is completed through the configuration management module, and the user can view the results through the user interface or configuration interface. Feedback information may include the operation status (success or failure), link status information, and possible error messages. For example, if the link establishment is successful, the user will receive a success notification and can view the relevant link parameters in the system; if the link establishment fails, the user will receive a failure notification with the reason for the failure, such as the peer device being unreachable or a security policy mismatch. This mechanism not only ensures that the system can respond promptly to the peer device's operation results but also improves system reliability and user experience through a closed-loop feedback mechanism.
[0062] In summary, the embodiments of this application have at least the following technical effects: This application enhances the security of channel management by encrypting, decrypting, and verifying the legitimacy of control messages within the isolation unit. This ensures the security of control data transmission between red and black zones, preventing unauthorized operations and data tampering. It supports multiple channel types, including Ethernet, 4G, PSTN, and ISDN, allowing for flexible channel selection for link establishment based on requirements, thus improving the system's adaptability to different network environments. Through various triggering methods, such as manual triggering, audit triggering, and transmission service triggering, it can meet the channel management needs of different scenarios, enhancing the system's flexibility and automation level. Simultaneously, the standardized channel establishment and teardown process reduces redundant operations and invalid audits, significantly improving the overall operating efficiency of the system.
[0063] It achieves the technical effect of secure channel management under multiple channel types and triggering methods based on red-black isolation architecture and multiple triggering mechanisms, thereby improving the security and flexibility of channel management operations.
[0064] Example 2 is based on the same inventive concept as the channel management method based on a red-black isolation architecture implemented in the previous examples, such as... Figure 2As shown, this application provides a channel management system based on a red-black isolation architecture. The system and method embodiments in this application are based on the same inventive concept. The system includes: The policy information configuration module 11 is used to configure the policy information of the peer device in the red zone.
[0065] The control message generation module 12 is used to respond to channel management events based on the policy information, generate a control message carrying peer device information and control instructions by the channel management module of the red zone, and send the control message to the isolation unit.
[0066] The legitimacy verification module 13 is used to perform legitimacy verification on control messages from the red zone in the isolation unit, and forward the verified control messages to the black zone.
[0067] The channel management module 14 is used to parse the control message in the black zone, and assemble and send the channel management message to the peer device in the red zone according to the parsed peer device information and control instructions, so as to perform the corresponding channel establishment or dismantling operation.
[0068] Furthermore, the control message generation module 12 is also used to perform the following steps: The channel management event can be triggered by one of the following methods: manual triggering, audit triggering, or transmission service triggering. Among them, the manually triggered channel management event is an XML message carrying preset channel type or channel priority information; the audit triggered channel management event is generated after the service message fails to match the unnegotiated security policy in the isolation unit and is sent to the red zone; the transmission service triggered channel management event is a fixed-format message forwarded by a non-user of this device after establishing a connection with the transmission service proxy module through a TCP connection.
[0069] Furthermore, when the channel management event is triggered manually, the control message generation module 12 is also used to perform the following steps: If the channel management event is configured as a preset channel type, then only the preset channel type will be used to initiate the connection establishment operation; if the channel management event is configured as a channel type priority selection, then different channel types will be tried sequentially according to the configured priority order to initiate the connection establishment operation until the connection is successfully established or all attempts fail. The channel types include Ethernet channels, 4G channels, Public Switched Telephone Network (PSTN) channels, and Integrated Services Digital Network (ISDN) channels.
[0070] Furthermore, the control message generation module 12 is also used to perform the following steps: When the channel management event is audit-triggered, after the peer device successfully establishes a link and completes security negotiation, the isolation unit stops sending audit-triggered instructions for service packets that match the same policy.
[0071] Furthermore, the control message generation module 12 is also used to perform the following steps: When the channel management event is triggered by the transmission service, after the operation is completed, the connection establishment or disconnection result will be returned to the non-user who initiated the operation via the TCP connection through the transmission service proxy module.
[0072] Furthermore, the legality verification module 13 is also used to perform the following steps: The isolation unit encrypts and decrypts the control message and extracts its five-tuple information. The five-tuple information is then matched against a pre-configured security policy; if a match is successful, verification is complete. The five-tuple information includes the source IP, destination IP, source port, destination port, and protocol type.
[0073] Furthermore, the legality verification module 13 is also used to perform the following steps: The system receives response messages from peer devices; the black zone parses the response messages and encapsulates the results into a response control message in a preset format; the response control message is forwarded back to the channel management module in the red zone via the isolation unit, and the channel management module in the red zone updates the link status according to the response control message and feeds back the operation results to the user.
[0074] It should be noted that the order of the embodiments described above is merely for descriptive purposes and does not represent the superiority or inferiority of the embodiments. Furthermore, the above description focuses on specific embodiments of this specification. Additionally, the processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are possible or may be advantageous.
[0075] The above description is only a preferred embodiment of this application and is not intended to limit this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the protection scope of this application.
[0076] This specification and accompanying drawings are merely illustrative examples of this application and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of this application. Clearly, those skilled in the art can make various alterations and modifications to this application without departing from its scope. Therefore, if such modifications and variations fall within the scope of this application and its equivalents, this application intends to include such modifications and variations.
Claims
1. A channel management method implemented based on a red-black isolated architecture, characterized in that, The system comprises: configuring policy information of a peer device in a red zone; in response to a channel management event based on the policy information, generating, by a channel management module of the red zone, a control packet carrying peer device information and a control instruction, and sending the control packet to an isolation unit; in the isolation unit, verifying the control packet from the red zone for legitimacy, and forwarding the control packet that passes the verification to a black zone; in the black zone, analyzing the control packet, and assembling and sending a channel management packet to the peer device in the red zone according to the analyzed peer device information and the control instruction, to perform a link-up or link-down operation of a corresponding channel.
2. The channel management method based on the red-black isolation architecture of claim 1, wherein, The trigger mode of the channel management event comprises one of manual triggering, audit triggering or transmission service triggering; the channel management event triggered manually is an XML message carrying preset channel type or channel priority information; the channel management event triggered by audit is generated and sent to the red zone after a service packet fails to match a non-negotiated security policy in the isolation unit; the channel management event triggered by transmission service is a fixed format message forwarded by a non-equipment user through a TCP connection and a transmission service agent module.
3. The channel management method based on the red-black isolation architecture of claim 2, wherein, When the trigger mode of the channel management event is manual triggering, comprising: if the channel management event is configured as a preset channel type, only the preset channel type is used to initiate a link-up operation; if the channel management event is configured as a channel type priority selection, different channel types are tried in turn according to the configured priority order to initiate a link-up operation, until the link-up is successful or all attempts fail.
4. The channel management method based on the red-black isolation architecture of claim 3, wherein, The channel types comprise an Ethernet channel, a 4G channel, a public switched telephone network (PSTN) channel and an integrated services digital network (ISDN) channel.
5. The channel management method based on the red-black isolation architecture of claim 1, wherein, In the isolation unit, the control packet from the red zone is verified for legitimacy, comprising: the isolation unit performs encryption and decryption processing on the control packet, and extracts five-tuple information of the control packet; the five-tuple information is matched with a preconfigured security policy, and if the matching is successful, the verification is passed.
6. The channel management method based on the red-black isolation architecture of claim 5, wherein, The five-tuple information comprises a source IP, a destination IP, a source port, a destination port and a protocol type.
7. The channel management method based on the red-black isolation architecture of claim 2, wherein, When the channel management event is audit triggered, after the peer device successfully links up and completes security negotiation, the isolation unit stops sending audit triggered instructions for matching the same policy for service packets.
8. The channel management method based on the red-black isolation architecture of claim 2, wherein, When the channel management event is transmission service triggered, after the operation is completed, the link-up or link-down result is returned to the non-equipment user who initiates the operation through the TCP connection via the transmission service agent module.
9. The channel management method based on a red-black isolation architecture of claim 1, wherein, Performing the link-up or link-down operation of the corresponding channel further comprises a response processing step: receiving a response packet from the peer device; analyzing the response packet by the black zone, and packaging the result into a response control packet in a preset format; forwarding the response control packet to the channel management module of the red zone through the isolation unit, and updating the link state according to the response control packet by the channel management module of the red zone, and feeding back the operation result to the user.
10. A channel management system implemented based on a red-black isolation architecture, characterized in that, The system comprises: a policy information configuration module configured to configure policy information of a peer device in a red zone; The control message generation module is configured to generate a control message carrying peer device information and a control instruction by the channel management module in the red zone in response to a channel management event based on the policy information, and send the control message to the isolation unit. The legality verification module is configured to verify the legality of the control message from the red zone in the isolation unit, and forward the control message passing the verification to the black zone. The channel management module is configured to analyze the control message in the black zone, assemble a channel management message according to the peer device information and the control instruction obtained by the analysis, and send the channel management message to the peer device in the red zone to perform a link establishment or disconnection operation of a corresponding channel.
