mr-udp

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mr-udp [2014/10/27 16:26]
mroriz [Architecture and Implementation Details]
mr-udp [2014/10/27 23:13]
mroriz [Architecture and Implementation Details]
Line 68: Line 68:
 ---- ----
  
 +The client state machine is similar to the server automata.  The primary difference is that the client start in the "negotiate and save" state. In this state, the client start the connection with the server information (address and port) using a given connection profile.  It sends a ''SYN'' segment with the connections parameters and waits on this state for a corresponding ''SYN'' reply from the server. When the client this message it sends an ''ACK'' message to finish the handshake. After that, the client transit to the "open" state.
 +
 +When an MRUDP application sends a message to the server, the message is divided in a sequence of ''DAT'' segments of size ''MAX_SEGMENT_SIZE''. For each segment, the protocol verify if the unack queue is empty, if it is not, the client cannot send additional segments. If the unack queue is empty the protocol queues the segment in the unack queue and sends to the server in a conventional UDP socket. 
 {{::sender.png?1200|}} {{::sender.png?1200|}}
 ** Sender FSM ** ** Sender FSM **
- 
 ===== References ===== ===== References =====
 MR-UDP: Yet another Reliable User Datagram Protocol, now for Mobile Nodes MR-UDP: Yet another Reliable User Datagram Protocol, now for Mobile Nodes
  • mr-udp.txt
  • Last modified: 2017/07/21 03:08
  • (external edit)