Contact

Instant Messaging Function of Command Communication System

📅Apr 8, 2026
Brief:The instant messaging function of the command communication system establishes a highly reliable, low-latency instant messaging capability, avoiding system latency and packet loss issues. The end-to-end delivery success rate for point-to-point and group messages is ≥99.999% (exceeding the tender requirement of 99.99%), with no noticeable latency; supports message delivery status receipts (sent, delivered, read), supports sending and receiving text, images, files, and voice short messages, supports drag-and-drop upload and online preview of files and images; supports creating permanent groups and temporary task groups, with historical message storage of ≥1 year (extended to 3 years), full-text search by conversation, time, and keywords, and important command-type messages can be marked as "Important" requiring recipient confirmation; messages sent from AOC positions can be pushed in real time to the mobile terminals of outstation support personnel.
Instant Messaging Function of Command Communication System

1 Core Function Implementation

Establish a highly reliable, low-latency instant messaging function, avoiding system latency and packet loss issues. The end-to-end delivery success rate for point-to-point and group messages is ≥99.999% (exceeding the tender requirement of 99.99%), with no noticeable latency.

Support message delivery status receipts (sent, delivered, read), support sending and receiving text, images, files, and voice short messages, and support drag-and-drop upload and online preview of files and images.

Support creating permanent groups and temporary task groups, with historical message storage of ≥1 year (extended to 3 years), full-text search by conversation, time, and keywords. Important command-type messages can be marked as "Important," requiring recipient confirmation.

Messages sent from AOC positions can be pushed in real time to the mobile terminals of outstation support personnel. The message transmission channel is encrypted, and filtering and auditing of sensitive information are supported.

2 Technical Implementation Solution

Message Core Engine: The domestically produced distributed message middleware RocketMQ is adopted to achieve reliable message delivery, supporting persistent message storage and consumption acknowledgment to ensure messages are neither lost nor duplicated.

Long Connection Maintenance: WebSocket long connections are used to achieve real-time communication between clients and the server, combined with a heartbeat detection mechanism to ensure connection stability, with automatic reconnection after network interruption.

Message Encryption: The message transmission channel is encrypted using the SM4 domestically produced encryption algorithm, and message storage adopts encrypted storage. Custom sensitive word library filtering and auditing for sensitive information (such as flight passwords and passenger information) are supported. The system automatically detects and blocks sensitive information while logging sensitive information sending operations.

3 Highlight Features

Historical Message Cloud Sync: After users log in on different terminals (PC, tablet, mobile), historical messages achieve full-terminal cloud sync, supporting viewing of complete historical messages to meet cross-terminal operation requirements.

Message Recall and Edit: Supports message recall within 5 minutes after sending, supports editing of sent messages. Both recall and edit operations are logged, and recipients can see recall/edit notifications.

Message Favorites and Forwarding: Supports favoriting important messages, with favorited messages viewable in a dedicated favorites folder. Supports single/multiple message forwarding, with the ability to add remarks when forwarding.

Message Archiving and Cleanup: Supports archiving conversations. Archived conversations do not appear in the message list and can be restored at any time. Supports manual cleanup of historical messages. After cleanup, local messages are deleted while server-side copies remain, ensuring data security.

Do Not Disturb Settings: Supports do-not-disturb settings for individual conversations and groups, with configurable do-not-disturb time periods. During do-not-disturb periods, messages are only cached locally without triggering sound or vibration alerts, meeting the rest needs of duty personnel.