All language subtitles for 3. TCP & UDP Protocols

Hello, guys, let's continue our explanation to the sector, and, of course, I know we're going to

talk about the second chapter in our course, which is about the Tsipi and UDP protocols.

OK, let's remember in the first chapter we were talking about the protocol we need to use in the 16

so that this protocol enable us to move or transfer the signaling IP packets from one destination to

another destination, of course.

OK, so we were having to read the existing options, which is the DCP protocol and the UDP protocol.

OK.

But as a conclusion of what happened and what we said, we found that the DP and the DP was not good

and not suitable to be used for the signaling of a transmission.

So we derived another protocol, which is a CETP protocol to do this process.

OK, so now in this chapter, we are going to revise what is DP and what is UDP is a vote so that you

can be convinced that you are completely aligned.

Why we refuse to use the DCP and the DP protocol.

OK, OK, let's talk to you.

Boothby Protocol stands for user data graph protocol over DCP stands for transmission control protocol,

OK, this is the actual naming of these two protocols.

OK, this is just really simple.

If someone didn't say UDP a user lithographic protocol automatically, we know that this is that he's

talking about the Adibi, of course.

OK.

However, that is a transmission control protocol.

OK, let's see.

What each protocol provides is mainly designed for broadcast and multicast.

I mean here by broadcast, a multicast is when sending information to a specific destination or to many

destination.

OK, this is a broadcast broadcast extending from one party or one destination to another to another

destination.

OK, over multicast is sending from one party to many parties.

OK, OK, this is the UDP.

There is a data group protocol over in the TCAP.

It is mainly designed to connect between two PCs or with the Internet.

We designed the DCP protocol or the transmission control protocol to connect between one computer and

another computer.

OK, or connecting this computer to the Internet protocol.

OK, so this is the main design or the main use we designed the two protocol for OK, OK, need to be

protocol is a connection, less protocol.

I mean, here by connection protocol, we don't have a specific route for the information to be sent

from one destination to another.

We have multiple passes for this information to be sent on.

OK, this is the connection lists that are safe.

OK, over vorticity.

It is a connection related protocol, which means that.

I have a specific route for this information to be sent from a signaling point to another signaling

point, OK, where I initiate first the link between the two the two destinations and then send the

data and terminate the connection after receiving the dead.

I first establish a connection between the two points and that sense of this connection and after the

connection is received at the end.

I terminated this connection.

OK, OK, one of the problems that GDP suffers from is that it has no acknowledgement.

Which means that when I send information or I send any packet over.

I am not waiting for foreign to send an acknowledgement that it has received this packet.

OK, so no acknowledgement is received after sending packets over in the TCAP protocol.

There is a guaranteed acknowledgment which is sent from foreign to the sender, indicating that it has

successfully received this packet.

Of course, this is an important feature that exists in the disparate.

OK, OK.

In the UDP protocol.

We do not know whether the package is received or not at the forehead.

So if the package is not received automatically, we'll send the other the next package in the series,

let's say we have package number one and two or three and four and five and they are sent I would send

packet number one, the twos and threes for the first.

Let's see, the package number two was sent but not delivered in the protocol as there is no acknowledgement,

as we said to you.

So I will not know that this packet number two.

Doesn't arrive at the destination, so I would automatically send back at number three and act normal.

OK.

However, in the TCAP protocol, I have a guaranteed acknowledgement.

So if bucket number two was it received at the far end, I will retransmitted again over the connection.

OK, so here is the protocol.

There is no retransmission of Becket's.

However, in the TCP IP protocol we have a retransmission of packets.

OK, so since we don't have retransmission of packets so there is no delay in the buckets, I will continuously

send packets.

The packet which is not delivered.

I will ignore it and then continue in the second and third and fourth and fifth packet over in the TCAP

protocol, it suffers from delay as the packet which is not received at the forefront.

I will retransmitted Baccarin.

So when I send the packet number two, two or three times, of course it will.

This will make me suffer from some delay in the packet transmission.

OK, ok, so since there is no retransmission of packets, here is be protocol.

There is a data loss of course.

OK, over in the DCP protocol, there's no data as I use the mechanism of resubmission.

OK.

The header of the packet here is a small header, however, it is a large header here because I use

visual circuits, so I make four connections between the sender and the receiver, maybe over different

routes.

So in the header of the packet, I put many addressing in it so that I guarantee that it will reach

the destination correctly and on time.

OK, so since I put many addressing that in the header, this means that the packet size will be very

large.

Looks like Redzepi, which has a small header into pockets, of course.

So.

After this conversion, I could say that the protocol that we need to use in the signaling transmission.

Overhype, of course, is not the protocol or the protocol as the protocol suffers from.

A big problem, which is no acknowledgement for the transmission of that and the reception of these

packets, of course, over the DCP protocol suffers from a big problem, which is the delay in the transmission

and receiving of these packets.

OK, so.

We agreed here to use another protocol, which is the SCDP protocol for packet's transmission over IP.

Of course.

OK, this is city protocol, which is train control transmission protocol.

Fulfill our signalling requirements to be transferred over the IP network.

Of course.

OK.

OK, thanks.