A protocol is bound to an underlying network channel which hold the characteristics of the "port" used for its communication. A communication protocol is used for the two sides of the communication, which means that any means of communicating data between UA and Server can be used.
The most simple of all protocols is an UDP protocol, (using UDP sockets), with one port for UA => Server communication, and one port for Server => UA communication.
By default there is only one channel of communication between the UA and the Server, but it is possible to specify more than one, see ARINC661 network configuration for more information.
Built-in protocols
The framework has several built-in protocols which can be used in the most common of use cases. The two most commonly used are:
"udp" (the default): an UDP protocol with two separate ports for the input and output sockets
"tcp": a TCP protocol with two separate ports for the input and output sockets
Characteristics of a protocol
The characteristics of a protocol are:
The port and size for the communication UA => Server
The port and size for the communication Server => UA
Sending the content of an ARINC 661 Buffer
The binary protocol specifies the content of the buffer which is sent from the UA to the CDS (and the CDS to the UA). For example, runtime buffers sent from the UA to the CDS: