Without rules, the internet would be just like that—broken data and missing pieces. This is exactly why we need TCP (Transmission Control Protocol).

Introduction: What happens if data is sent without rules?

Imagine you are sending an important message to a friend, but:

• You don’t know if they are online

• You don’t know if your message reached them

• You don’t know if messages arrive in the correct order

That’s exactly what happens on the internet without rules.

Bina rules ke data bhejna = confusion, loss, and errors.

To solve this, the Internet uses TCP.

1. What is TCP, and why is it needed?

TCP (Transmission Control Protocol) is a transport-layer protocol that ensures reliable communication between two systems.

TCP is a connection-oriented protocol. Its only job is to make sure that data sent from Point A reaches Point B exactly as it was sent—no missing bits, no corruption, and in the right order.

Important Point: Simple words: Bina rules ke internet ek kachra hota jahan files corrupt ho jati. TCP wo "Guarantee" hai jo har data packet ko sahi salamat pahunchati hai.

→ TCP makes sure that:

• Data reaches the correct destination

• Data arrives in the correct order

• Lost data is retransmitted

TCP ka goal simple hai: data safe aur sahi pahunchna chahiye.

2. Problems TCP is designed to solve

In a wild network, three things happen constantly:

1. Packet Loss: A data packet gets lost in a router.

2. Out-of-Order Delivery: Packet 3 arrives before Packet 1.

3. Data Corruption: The data changes due to electrical interference.

TCP solves all of these using "Acknowledgements" and "Sequence Numbers."

→ TCP exists because raw network communication has problems:

• Packets can get lost

• Packets can arrive out of order

• Packets can get duplicated

• The receiver may get overwhelmed

TCP in sab problems ko systematically handle karta hai.

3. What is the TCP 3-Way Handshake?

The Famous TCP 3-Way Handshake

Before TCP sends even a single byte of data, it must establish a "trust" between the sender and receiver. This is the 3-way handshake.

Think of it like a polite conversation:

1. Step 1: SYN (Synchronise) The client says, "Hey, I want to talk to you. Here is my starting sequence number (e.g., 100)."

2. Step 2: SYN-ACK (Synchronise-Acknowledge) The server responds, "I hear you! I'm ready too. I received your 100, so I'm expecting 101. Also, here is my starting number (e.g., 500)."

3. Step 3: ACK (Acknowledge) The client says, "Got it! I received your 500, so I'm expecting 501. Let's start the data transfer!"

Important Point: Ye bilkul ek "Hello, kya aap mujhe sun rahe ho?" wali baat hai. Jab dono taraf se 'Haan' ho jati hai, tabhi asli data transfer shuru hota hai.

→ Before sending actual data, TCP first establishes a connection.

This connection setup is called the 3-Way Handshake.

It is a short conversation between the client and the server to confirm:

• Both are ready

• Both can send and receive data

“Data bhejne se pehle “hello–hello” zaroori hai.”

4. Step-by-step working of SYN, SYN-ACK, and ACK

How Data Transfer Works (Reliability and Order)

Once the connection is established, TCP breaks your data into small segments.

• Sequence Numbers: Each segment gets a number (1, 2, 3...). If they arrive out of order, the receiver uses these numbers to rearrange them.

• Acknowledgements (ACK): For every packet received, the receiver sends back an "ACK" (I got it!).

• Retransmission: If the sender doesn't get an ACK within a certain time, it assumes the packet was lost and sends it again.

  Important Point: Agar receiver ko packet #2 nahi mila, toh wo sender ko batayega. Sender tab tak packet #2 bhejta rahega jab tak receiver "Mil gaya!" (ACK) nahi bol deta.

→ Let’s break the handshake step by step.

Step 1: SYN (Client → Server)

The client sends a SYN message.

Meaning: “Hello Server, can we start communication?”

It also sends an initial sequence number.

“Client bolta hai: Main ready hoon.”

Step 2: SYN-ACK (Server → Client)

The server replies with SYN-ACK.

Meaning: “Yes, I got your request, and I’m ready too.”

The server:

• Acknowledges client’s sequence number

• Sends its own sequence number

Server bolta hai: message mil gaya, main bhi ready hoon.

Step 3: ACK (Client → Server)

The client sends a final ACK.

Meaning: “Got it. Let’s start data transfer.”

At this point, the connection is established.

Ab dono side ready hain—data transfer shuru.

TCP 3-Way Handshake (Conceptual Flow): Client → SYN → Server Client ← SYN-ACK ← Server Client → ACK → Server

(Connection is now open.)

→ Closing the Connection: The 4-Way Terminate

Closing a connection is just as important as opening it. It uses FIN (Finish) and ACK flags.

1. Client: "I'm done sending data. (FIN)"

2. Server: "Okay, I received your request to stop. (ACK)"

3. Server: (Waits a bit to finish its own tasks) "I'm also done. (FIN)"

4. Client: "Understood. Bye! (ACK)"

5. How data transfer works in TCP

Once the connection is established:

• Data is broken into segments

• Each segment gets a sequence number

• The receiver sends ACKs for received data

“Har data ka receipt milta hai.”

→ Sequence numbers and acknowledgements (High level)

• The sequence number tells the position of the data

• ACK number confirms how much data is received

If data is missing:

• The receiver does not ACK

• Sender retransmits

“Jo nahi mila, woh dubara bhejo.”

6. How TCP ensures reliability, order, and correctness

TCP guarantees reliability using:

1. Acknowledgements

The receiver confirms receipt of data.

2. Retransmission

Lost packets are sent again.

3. Ordered delivery

Data is rearranged before delivery to the application.

4. Flow control

The sender does not overwhelm the receiver.

“TCP ensures data is complete, ordered, and correct.”

→ How TCP handles packet loss

If a packet is lost:

• ACK is not received

• Timer expires

• The sender retransmits the missing packet

“Packet loss = retry, not failure.”

7. How a TCP connection is closed

Closing a TCP connection is also controlled and graceful.

Step 1: FIN (One side wants to close)

“I have no more data to send.”

Step 2: ACK (The other side confirms)

“Got it.”

Step 3: FIN (The other side also finishes)

“I’m done too.”

Step 4: ACK (Final confirmation)

The connection is now closed.

“TCP goodbye bhi politely bolta hai.”

TCP connection lifecycle (big picture):

Connection Establishment (3-Way Handshake)

↓

Reliable Data Transfer

↓

Graceful Connection Termination

TCP may look complex at first, but its logic is simple: Agar data important hai, TCP mandatory hai.

TCP uses a 3-way handshake to establish trust, sequence numbers and acknowledgements to ensure reliable data transfer, and a controlled termination process to close connections safely.

let’s connect on LinkedIn: → LinkedIn