The layering models don't use protocols. The layering models provide a structure to build the protocols on.
The OSI model is a very detailed and strict model. It was developed as a theoretical model (somewhat) in parallel to the growing TCP/IP or DoD model which largely came out of practice. OSI is good way to structure a protocol concept as long as you don't stick to it literally.
The DoD model pretty much throws together everything above the transport layer (=application layer) and everything below the network layer (=link layer) which may be a practical approach when concentrating on the network layer but it lacks coverage above and below when doing more complex designs.
But even OSI might not be detailed enough for every purpose. For example, Ethernet generally covers OSI's physical layer and data link layer. However, IEEE 802.3 defines up to four sublayers for the physical layer and up to three sublayers for the data link layer.
[Data link layer] That confuses me a little bit since the physical layer puts the bits on the wire and collects it from there, which is effectively transferring data between nodes on the same network (please help me cut this more clear if you can).
The physical layer puts bits and bytes on the wire - between two nodes. The data link layer frames them and directs the frames to the local destination.
The data link layer is usually completely handled in hardware. A NIC covers physical and data link layer, so does a switch. (Frame assembly and interpretation used to be software as well but see below.)
The network layer used to be handled in software, due to complexity, but specialized hardware has long since learned to handle network and even transport layer in hardware, partially or entirely: multilayer switches, hardware router, offloading function in NICs, ...
why is this division missing from the TCP/IP model?
It's an important distinction to make if you are developing services within these layers, but the folks from ARPA (or IETF later on) defining the TCP/IP model simply didn't care. They abstracted the data link layer downward as the link layer. To be fair, the TCP/IP model predates the OSI model quite a bit. The ISO, developing the OSI model, aimed at standardizing the full stack, from top to bottom.
If you're studying the popular physical and data link layer protocols, you will see that they are even sublayered - for work distribution and modularity reasons.
Best Answer
TCP/IP is a protocol stack which contains different protocols required for the data transfer from sender to receiver.
TCP - Layer 4 protocol which ensures reliability and is connection oriented.
TCP/IP is also a layered protocol but does not use all of the OSI layers, though the layers are equivalent in operation and function (Fig. 2). The network access layer is equivalent to OSI layers 1 and 2. The Internet Protocol layer is comparable to layer 3 in the OSI model. The host-to-host layer is equivalent to OSI layer 4. These are the TCP and UDP (user datagram protocol) functions. Finally, the application layer is similar to OSI layers 5, 6, and 7 combined.
The TCP layer packages the data into packets. A header that’s added to the data includes source and destination addresses, a sequence number, an acknowledgment number, a check sum for error detection and correction, and some other information. The header is 20 octets (octet = 8 bits) grouped in 32-bit increments.
Source: https://stackoverflow.com/questions/31473578/tcp-ip-and-tcp-and-ip-difference