{"id":101,"date":"2025-10-18T09:06:55","date_gmt":"2025-10-18T09:06:55","guid":{"rendered":"https:\/\/ciphermq.com\/blog\/?p=101"},"modified":"2025-10-18T09:33:56","modified_gmt":"2025-10-18T09:33:56","slug":"message-transmission-process-and-examplescenario-labs-and-research-centers","status":"publish","type":"post","link":"https:\/\/ciphermq.com\/blog\/index.php\/2025\/10\/18\/message-transmission-process-and-examplescenario-labs-and-research-centers\/","title":{"rendered":"Message Transmission Process and ExampleScenario (Labs and Research Centers)"},"content":{"rendered":"\n

Message Transmission Process<\/strong><\/p>\n\n\n\n

Objective To enable secure data transmission from senders to receivers via a central server using CipherMQ, leveraging mTLS for authentication and x25519 encryption for message security.<\/p>\n\n\n\n

Process Steps<\/strong><\/p>\n\n\n\n

    \n
  1. Initial Setup<\/strong>
    1. Server Configuration: The server is configured with TLS 1.3 for secure communication.<\/li><\/ol>\n
        \n
      1. Client Configuration: Receivers register their public keys with the server; senders retrieve and load the public keys of intended recipients.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
      2. Message Generation & Encryption<\/strong>
        1. Senders generate messages in a standardized format: { “message_id”: “”, “sender_id”: “”, “sent_timestamp”: “”, “content”: “” }<\/li><\/ol>\n
            \n
          1. Messages are encrypted for each recipient using their x25519 public key, including message_id, receiver_client_id, and ciphertext.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
          2. Transmission to Central Server<\/strong>
            1. Senders connect to the server via mTLS for secure authentication.<\/li><\/ol>
              1. Encrypted messages are sent with a publish command.<\/li><\/ol>\n
                  \n
                1. The server stores metadata in the table and sends an ACK to the sender.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                2. Processing & Distribution<\/strong>
                  1. The server queues messages using a high-performance DashMap.<\/li><\/ol>
                    1. Based on routing_key and bindings, messages are directed to recipient queues.<\/li><\/ol>\n
                        \n
                      1. Messages are delivered to connected recipients.<\/li>\n<\/ol>\n<\/li>\n\n\n\n
                      2. Reception & Decryption<\/strong>
                        1. Receivers connect to their designated queue, consume messages, and decrypt them using their private key.<\/li><\/ol>\n
                            \n
                          1. Decrypted messages are saved in a standardized file.<\/li>\n<\/ol>\n<\/li>\n<\/ol>\n\n\n\n

                            Receivers send an ACK to the server, which updates acknowledged_time in the database, removes the message from the queue, and retains only metadata.<\/strong><\/p>\n\n\n\n

                            <\/p>\n\n\n\n

                            ExampleScenario: Labs and Research Centers<\/strong><\/p>\n\n\n\n

                            \"\"<\/figure>\n\n\n\n

                            Locations Defined<\/strong><\/p>\n\n\n\n

                              \n
                            • Labs (Senders)<\/strong>: These generate and encrypt data.<\/li>\n<\/ul>\n\n\n\n

                              FL-LAB<\/strong> (Florida Laboratory)                       <\/p>\n\n\n\n

                              PA-LAB<\/strong> (Pennsylvania Laboratory)<\/p>\n\n\n\n

                              MA-LAB<\/strong> (Massachusetts Laboratory)    <\/p>\n\n\n\n

                              IL-LAB<\/strong> (Illinois Laboratory)<\/p>\n\n\n\n

                                \n
                              • Research Centers (Receivers)<\/strong>: These receive and decrypt data.<\/li>\n<\/ul>\n\n\n\n

                                CA-RC<\/strong> (California Research Center)<\/p>\n\n\n\n

                                NY-RC<\/strong> (New York Research Center)<\/p>\n\n\n\n

                                SF-RC<\/strong> (San Francisco Research Center)<\/p>\n\n\n\n

                                  \n
                                • Central Server (Headquarters)<\/strong>: server, responsible for managing and distributing messages.<\/li>\n<\/ul>\n\n\n\n

                                  DC-HQ<\/strong> (Washington D.C Headquarters)<\/p>\n\n\n\n

                                  <\/p>\n\n\n\n

                                  <\/div>\n\n\n\n

                                  Event<\/strong><\/p>\n\n\n\n

                                  FL-LAB<\/strong>: Generates raw data (FL-LAB_DAT_20251008_001), encrypts it for CA-RC<\/strong> and SF-RC<\/strong>, and sends via mTLS to DC-HQ<\/strong>.<\/p>\n\n\n\n

                                  PA-LAB<\/strong>: Generates report (PA-LAB_RPT_20251008_125), encrypts it for CA-RC<\/strong>, NY-RC<\/strong> and SF-RC<\/strong>, and sends via mTLS to DC-HQ<\/strong>.<\/p>\n\n\n\n

                                  MA-LAB<\/strong>: Generates raw data (MA-LAB_DAT_20251008_045), encrypts it for NY-RC<\/strong> and SF-RC<\/strong>, and sends via mTLS to DC-HQ<\/strong>.<\/p>\n\n\n\n

                                  IL-LAB<\/strong>: Generates report (IL-LAB_RPT_20251008_175), encrypts it for CA-RC<\/strong> and SF-RC<\/strong>, and sends via mTLS to DC-HQ<\/strong>.<\/p>\n\n\n\n

                                  <\/div>\n\n\n\n

                                  Processing at Headquarters:<\/strong><\/p>\n\n\n\n

                                  Routes messages to queues (ca_rc_queue, ny_rc_queue, sf_rc_queue) based on routing_key.<\/p>\n\n\n\n

                                  <\/div>\n\n\n\n

                                  Reception at Research Centers:<\/strong><\/p>\n\n\n\n

                                  CA-RC<\/strong>: Receives and decrypts messages from FL-LAB, PA-LAB, IL-LAB<\/strong>.<\/p>\n\n\n\n

                                  NY-RC<\/strong>: Receives and decrypts messages from PA-LAB, MA-LAB<\/strong>.<\/p>\n\n\n\n

                                  SF-RC<\/strong>: Receives and decrypts messages from FL-LAB, PA-LAB, MA-LAB, IL-LAB<\/strong>.<\/p>\n","protected":false},"excerpt":{"rendered":"

                                  Message Transmission Process Objective To enable secure data transmission from senders to receivers via a central server using CipherMQ, leveraging mTLS for authentication and x25519 encryption for message security. Process Steps Receivers send an ACK to the server, which updates acknowledged_time in the database, removes the message from the queue, and retains only metadata. ExampleScenario: […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-101","post","type-post","status-publish","format-standard","hentry","category-uncategorized"],"_links":{"self":[{"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/101","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/comments?post=101"}],"version-history":[{"count":4,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/101\/revisions"}],"predecessor-version":[{"id":124,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/posts\/101\/revisions\/124"}],"wp:attachment":[{"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/media?parent=101"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/categories?post=101"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/ciphermq.com\/blog\/index.php\/wp-json\/wp\/v2\/tags?post=101"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}