We should soften up four sections.
IP is the Internet Protocol. It's a system layer convention, which enables parcels to be transmitted between two has anyplace on the system (which can be a private, detached system, or the Internet). As said above, IP is about bundles; it doesn't say anything in regards to the substance of the parcels. Despite the fact that you could send IP bundles to whatever other host in the system, the base convention is not as valuable for end clients, as there's no real way to separate between parcels unless you take a gander at the substance. So there are other "larger amount" conventions that expand upon IP and enable applications to utilize the system all the more brilliantly.
TCP is the Transmission Control Protocol. It keeps running over IP, so the normal name TCP/IP. It's intended to give a solid stream of correspondence between two hosts. One host (the customer) sends a correspondence demand to the next host (the server); a correspondence channel is stablished and the two hosts begin conversing with each other. TCP ensures that the messages are conveyed in a similar request they were initially sent. Additionally, TCP incorporates exceptional instruments to manage clog, utilizing extraordinary calculations that recognize bundle misfortunes and alter transmission speed in like manner.
UDP is the User Datagram Protocol. It's another convention that runs specifically over IP. The contrast amongst TCP and UDP is that UDP is significantly more straightforward and doesn't offer any of the specific ensures that make TCP so helpful. UDP messages are sent to the goal, without ensured conveyance, and without assurances about the request of conveyance. UDP additionally doesn't offer blockage control. Then again, UDP is less complex and more proficient, which makes it extremely appropriate for conventions that either require short message trades to work (DNS is a decent case), or don't require a similar conveyance ensures (like RTP, which is utilized for VoIP and other media gushing applications).
(A few people may ask: why we require two conventions, UDP and TCP, running over IP? Every convention is more qualified to an alternate sort of use, and keeping in mind that TCP is by a wide margin the better known convention, UDP has its place and is exceptionally valuable. Be that as it may, as the two conventions keep running over IP, they have a similar system framework, which makes things less demanding to work with.)
HTTP is the HyperText Transfer Protocol. It's an application convention, intended to offer courses for customers to recover and work with hypertext items and parts (counting HTML pages, PNG imagens, et cetera). HTTP keeps running over TCP, which in its turn keeps running over IP. Contrasted with IP (which is a system convention) and TCP (which is a vehicle convention), HTTP is an application convention - which implies that it is specifically devoured by applications.
There are numerous other application conventions. To recover router password and get the 192.168.1.1 login, SMTP (utilized for email), SIP (utilized for VoIP), FTP (utilized for record exchanges), and numerous others. A large portion of these application conventions have in like manner the way that they utilize TCP/IP as a typical premise, however stablish their own messages to execute particular usefulness.
To complete the clarification, a similarity may offer assistance:
IP resembles the postal administration. It conveys letters to your entryway, yet it couldn't care less about the letter substance.
TCP resembles your secretary. She utilizes the postal administration to send and get letters, and she takes care to ensure that the letters are conveyed to the ideal individual on the goal. She likewise investigate the letters you get and place it into the right order - may putting the messages in partitioned stacks or containers - which makes your work simpler.
HTTP (and any application convention, so far as that is concerned) is your main event when you get the message. Your secretary got a letter from the postal office, opened it, and saw that it was routed to you. She put the message on a requested stack, so you simply need to pick the top message and read.
Trust the case enlightens the ideas driving the convention layers!