Need for Byte-Stuffing
In variable-size framing at the data link layer, we need to define a way to separate one frame from the next. Byte stuffing is employed to accomplish the task. In byte stuffing an 8-bit flag (‘F’) is added at the beginning and at the end of the frame, thereby distinguishing one frame from the next. Therefore, every time a flag sequence (‘F’) is encountered, it signifies the beginning or end of a frame. This, ingenious scheme, however would give rise to a discrepancy, if the flag pattern (‘F’) would occur within the data carried by the frame itself. Byte stuffing comes to the rescue here, by stuffing the original data with an extra 8-bit escape sequence (‘E’) before the flag pattern, whenever it occurred within the data carried by a frame. The receiver would then have to de-stuff the escape sequence, in order to obtain the original data.
A simple question that might arise at this juncture is, what if the escape sequence (‘E’) formed a part of the data to be sent! This scenario is handled in exactly the same way as described above, i.e an extra 8-bit escape sequence (‘E’) is added to the original data before the escape sequence that formed part of the data.
In character-oriented protocols, where data to be carried are 8-bit characters, byte stuffing is employed to handle the problems discussed above.
To make things simpler we will consider only three types of byte sequences in the sent data, as :
F : Flag Sequence
E : Escape Sequence
D : Any other Data Sequence
For Example :
At Sender Side
Enter the Message to be Sent :
DDEDFFDE
The data being sent (with byte stuffed) is : FDDEEDEFEFDEEF
Seding Message....
Thanks for the Feedback Server!!
At Receiver Side
Message Received...Successfully!!!
The Stuffed Message is : FDDEEDEFEFDEEF
The Destuffed Message is : DDEDFFDE
Messaging is over.....EXITING
From the above example we can see how the original data is recovered at the receiver end.
Approach
At Sender (Client) Side
- Data of each frame at the sender side, is first stuffed with 8-bit flag sequence (‘F’) at the beginning and end of each frame.
- Next, the data is scanned to see if any similar flag sequence (‘F’) forms a part of it or not. If yes, then before each such flag sequence, an extra escape sequence (‘E’) is stuffed.
- Now, if any similar escape sequence (‘E’) is found to form a part of the data to be sent, then an extra escape sequence (‘E’) is stuffed before the occurrence of each such escape sequence.
- Finally, this stuffed data is sent by the sender.
At Receiver (Server) Side
- The receiver skips over the first and last bytes of data received, as they are merely for signalling the beginning and end of one frame, respectively and does not carry any useful data.
- From the next byte on wards data is scanned and if two escape sequences (‘E’) are found in succession, the first one is de-stuffed. Similarly, if an escape sequence is followed by a flag sequence (‘F’), the former is de-stuffed.
- This strategy helps the receiver recover the actual sent data, accurately.
Implementation
At Sender (Client) Side
package byte_stuffing;
import java.io.*;
import java.util.*;
import java.net.*;
public class Byte_Stuffing_Client {
public static void main(String args[]) throws IOException
{
InetAddress ip = InetAddress.getLocalHost();
int port = 45678 ;
Scanner sc = new Scanner(System.in);
Socket s = new Socket(ip, port);
DataInputStream dis = new DataInputStream(s.getInputStream());
DataOutputStream dos = new DataOutputStream(s.getOutputStream());
while ( true ) {
System.out.println( "Enter the Message to be Sent : " );
String data = sc.nextLine();
String res = new String();
data = 'F' + data + 'F' ;
for ( int i = 0 ; i < data.length(); i++) {
if (data.charAt(i) == 'F' && i != 0 && i != (data.length() - 1 ))
res = res + 'E' + data.charAt(i);
else if (data.charAt(i) == 'E' )
res = res + 'E' + data.charAt(i);
else
res = res + data.charAt(i);
}
System.out.println( "The data being sent (with byte stuffed) is : " + res);
dos.writeUTF(res);
System.out.println( "Seding Message...." );
if (dis.readUTF().equals( "success" ))
System.out.println( "Thanks for the Feedback Server!!" );
dos.writeUTF( "bye" );
break ;
}
s.close();
dis.close();
dos.close();
}
}
|
At Receiver (Server) Side
package byte_stuffing;
import java.io.*;
import java.net.*;
public class Byte_Stuffing {
public static void main(String[] args) throws IOException
{
ServerSocket servsock = new ServerSocket( 45678 );
Socket socket = servsock.accept();
DataInputStream dis = new DataInputStream(socket.getInputStream());
DataOutputStream dos = new DataOutputStream(socket.getOutputStream());
while ( true ) {
String out = new String();
String res = dis.readUTF();
System.out.println( "Message Received...Successfully!!!" );
System.out.println( "The Stuffed Message is : " + res);
for ( int i = 1 ; i < res.length() - 1 ; i++) {
if (res.charAt(i) == 'D' || res.charAt(i) == 'F' )
out = out + res.charAt(i);
else if (res.charAt(i) == 'E' && res.charAt(i + 1 ) == 'E' ) {
out = out + 'E' ;
i++;
}
}
System.out.println( "The Destuffed Message is : " + out);
dos.writeUTF( "success" );
String ch = dis.readUTF();
if (ch.equals( "bye" )) {
System.out.println( "Messaging is over.....EXITING" );
break ;
}
}
socket.close();
dis.close();
dos.close();
}
}
|
The Server (Receiver) should start running prior to the Client (Sender). This is essential because the client needs an open connection (socket) to send the data and this connection is opened by the server.
Output
At Client (Sender) Side
Enter the Message to be Sent :
DFEDDFED
The data being sent (with byte stuffed) is : FDEFEEDDEFEEDF
Seding Message....
Thanks for the Feedback Server!!
At Server (Receiver) Side
Message Received...Successfully!!!
The Stuffed Message is : FDEFEEDDEFEEDF
The Destuffed Message is : DFEDDFED
Messaging is over.....EXITING
Feeling lost in the vast world of Backend Development? It's time for a change! Join our
Java Backend Development - Live Course and embark on an exciting journey to master backend development efficiently and on schedule.
What We Offer:
- Comprehensive Course
- Expert Guidance for Efficient Learning
- Hands-on Experience with Real-world Projects
- Proven Track Record with 100,000+ Successful Geeks
Last Updated :
02 Dec, 2022
Like Article
Save Article