103), where at least one of the waypoints modifies the secure event communication en route to the recipient device. Additionally or alternatively, the secure communication model may output that the event processing request should be routed, as a secure event communication, via one or more intervening waypoints, and multiple waypoints should be used to modify the secure event communication. Accordingly, the secure messaging platform 102 may dynamically adjust security parameters for the secure event communication accordingly.

In addition to identifying the communication parameters (e.g., the path across which the secure event communication should be sent and if or how it should be modified along the way), the secure communication model may output communication validation information (which may, e.g., be an audio signal such as a piece of a song, an audio tone, an audio note, an audio pitch, or a sound), which may, e.g., be embedded in the secure event communication. In some instances, secure communication model may dynamically adjust a complexity of the communication validation information in a similar way as discussed above with regard to the communication parameters and the corresponding threshold ranges. For example, the secure communication model may be configured to initially randomly produce communication validation information and then adjust its complexity (e.g., a duration of the sound, a number of notes, a number of frequencies or points in time across which the communication validation information is spread, or the like).

Referring to FIG. 2B, at step 206, the secure messaging platform 102 may generate the secure event communication by embedding the communication validation information into one or more bits of an audio signal according to the communication parameters. For example, the secure messaging platform 102 may generate the secure event communication using time domain multiplexing, where the communication validation information may be divided across different moments in time across an audio signal. Additionally or alternatively, the secure messaging platform 102 may generate the secure event communication using frequency domain multiplexing, where the communication validation information is divided across different frequencies and/or frequency bands of an audio signal. In some instances, the secure messaging platform 102 may embed the communication validation information within the secure event communication at a particular frequency (which may, in some instances, be an audible or inaudible frequency) or time.

In some instances, the secure messaging platform 102 may encrypt the secure event communication.

In some instances, the secure messaging platform 102 may generate white noise and/or otherwise embed decoy information in the secure event communication at one or more times or frequencies different than those at which the legitimate communication validation information is embedded. This may, in some instances, assist in hiding and/or otherwise concealing the communication validation information.

In some instances, in generating the secure event communication, the secure messaging platform 102 may select a song, and a particular tone corresponding to the song at a given time may comprise the communication validation information. In some instances, the tone may be selected based on the available tones in a given song.

At step 207, the secure messaging platform 102 may establish a connection with the communication server 103 (which may, e.g., be identified as part of the communication parameters at step 205). For example, the secure messaging platform 102 may establish a second wireless data connection with the communication server 103 to link the secure messaging platform 102 with the communication server 103 (e.g., in preparation for sending secure event communications).

In some instances, the secure messaging platform 102 may identify whether or not a connection is already established with the communication server 103. If a connection is already established with the communication server 103, the secure messaging platform 102 might not re-establish the connection. If a connection is not yet established with the communication server 103, the secure messaging platform 102 may establish the second wireless data connection as described herein.

At step 208, the secure messaging platform 102 may train a machine learning model (e.g., an interference response model). For example, the secure messaging platform 102 may train the interference response model to identify response actions (e.g., change a path of secure event communications, change a frequency or frequency band at which the communication validation information is embedded, change a time or times at which the communication validation information is embedded, adjust a complexity of the communication parameters, resend the communication, and/or other actions) for detected interference (e.g., interference detected with a secure event communication at one or more waypoints and/or otherwise during transmission). For example, the secure messaging platform 102 may receive historical interference information (e.g., where was the interference, what was the interference, or the like), and corresponding response actions. The secure messaging platform 102 may then input this historical information into the interference model to train the interference model to establish stored correlations between types of interference and the corresponding response actions. In doing so, the secure messaging platform 102 may train the interference model to identify, based on detected interference, corresponding response actions, which may, e.g., be used to further secure communications.

In some instances, in training the interference response model, the secure messaging platform 102 may train a supervised learning model (e.g., decision tree, bagging, boosting, random forest, neural network, linear regression, artificial neural network, support vector machine, and/or other supervised learning model), unsupervised learning model (e.g., classification, clustering, anomaly detection, feature engineering, feature learning, and/or other unsupervised learning models), and/or other model.

At step 209, the secure messaging platform 102 may send the secure event communication to the communication server 103 (e.g., which may, e.g., be an intervening waypoint as discussed above). For example, the secure messaging platform 102 may send the secure event communication to the communication server 103 via the communication interface 113 and while the second wireless data connection is established.

At step 210, the communication server 103 may receive the secure event communication sent at step 209. For example, the communication server 103 may receive the secure event communication while the second wireless data connection is established.

Referring to FIG. 2C, at step 211, the communication server 103 may, in some instances, modify the secure event communication. For example, in some instances, the communication server 103 may modify the communication validation information, one or more frequencies at which the communication validation information is embedded, one or more times at which the communication validation information is embedded, encryption of the secure event communication, or the like. In some instances, the communication server 103 may modify the secure event communication based on one or more commands form the secure messaging platform 102 (which may, in some instances, be sent along with the secure event communication). Additionally or alternatively, the communication server 103 may itself be configured with an instance of the secure communication model trained at step 201, and may know whether or not to modify (and how to modify) the secure event communication based on its corresponding value accordingly. In some instances, any modifications to the secure event communication, made by the communication server 103, may be tracked (e.g., by the secure messaging platform 102, or the like) and/or otherwise communicated to the recipient user device 105. In doing so, the recipient user device 105 may be configured to validate the secure event communication against a known truth value and/or otherwise identify a location of any embedded communication validation information despite any modifications performed by intermediary communication servers along a path of the secure event communication.

At step 212, the communication server 103 may send communication modification information to the secure messaging platform 102, which may, e.g., indicate interference with the secure event communication at the communication server 103 (e.g., attempts to access the communication, or the like). In some instances, the communication server 103 may send the communication modification information to the secure messaging platform 102 while the second wireless data connection is established.

At step 213, the secure messaging platform 102 may receive the communication modification information sent at step 212. For example, the secure messaging platform 102 may receive the communication modification information via the communication interface 113 and while the second wireless data connection is established.

At step 214, the secure messaging platform 102 may detect, based on the communication modification information received at step 213, interference with the secure event communication, and may identify corresponding response actions. For example, the secure messaging platform 102 may detect an attempt to intercept the secure event communication, access the secure event communication, and/or otherwise affect airwaves corresponding to the secure event communication.

In some instances, the secure messaging platform 102 may identify one or more response actions. For example, the secure messaging platform 102 may input information of the interference into the interference response model (trained at step 208), which may identify corresponding response actions. For example, the interference response model may output that the secure messaging platform 102 should perform one or more of: change a path of the secure event communication (e.g., route to the recipient user device 105 via one or more alternative intervening waypoints), change a frequency (or frequencies) or frequency band (or bands) at which the communication validation information is embedded, change a time or times at which the communication validation information is embedded, adjust a complexity of the communication parameters (e.g., increase a number of intervening waypoints that may modify the secure event communication and/or the way in which they modify the secure event communication), resend the communication, and/or other actions.

In some instances, the secure messaging platform 102 may use the interference response model to track any detected interference, and may enable the secure messaging platform 102 to apply any stored intelligence in the future routing of secure event communications (e.g., avoiding a compromised waypoint in the future, or the like).

At step 215, the secure messaging platform 102 may initiate the one or more response actions identified at step 214. For example, the secure messaging platform 102 may change a path of the secure event communication (e.g., route to the recipient user device 105 via one or more alternative intervening waypoints), change a frequency (or frequencies) or frequency band (or bands) at which the communication validation information is embedded, change a time or times at which the communication validation information is embedded, adjust a complexity of the communication parameters (e.g., increase a number of intervening waypoints that may modify the secure event communication and/or the way in which they modify the secure event communication), resend the communication, and/or perform other actions. Although steps 212-215 indicate communication of the communication server 103 with the secure messaging platform 102 and determination/implementation of the response actions by the secure messaging platform 102 accordingly, in some instances, the communication server 103 itself may be configured to identify and/or initiate the response actions automatically. For example, in some instances, the communication server 103 may be configured with the interference response model, and may be configured to make go/no-go decisions (e.g., indicating whether or not the secure event communication should be routed to a subsequent waypoint and/or the recipient user device) based on detected interference. In some instances, the communication server 103 may be configured to check for secondary communication validation information if initial communication validation information is not detected. For example, the communication server 103 may be configured to check for the communication validation information at a second point in time if it is not detected at a first moment in time, or the like.

Referring to FIG. 2D, at step 216, the communication server 103 may establish a connection with the recipient user device 105. For example, the communication server 103 may establish a third wireless data connection with the recipient user device 105 to link the communication server 103 to the recipient user device 105 (e.g., in preparation for sending secure event communications). In some instances, the communication server 103 may identify whether or not a connection is already established with the recipient user device 105. If a connection is already established with the recipient user device 105, the communication server 103 might not re-establish the connection. If a connection is not yet established with the recipient user device 105, the communication server 103 may establish the third wireless data connection as described herein.

At step 217, the communication server 103 may send the secure event communication to the recipient user device 105. For example, the communication server 103 may send the secure event communication to the recipient user device 105 while the third wireless data connection is established. In some instances, in sending the secure event communication to the recipient user device 105, the communication server 103 may convert the secure event communication to a machine-readable code, such as a quick response (QR) code, and may send the QR code to the recipient user device 105.

At step 218, the recipient user device 105 may receive the secure event communication sent at step 217. For example, the recipient user device 105 may receive the secure event communication while the third wireless data connection is established.

At step 219, the recipient user device 105 may process the requested event. For example, the recipient user device 105 may process the payment and/or other request included in the secure event communication. In some instances, the recipient user device