First, Internet Architecture was built on the Open Systems Interconnection (OSI) seven-layers Model, used by ARPANET and its successor the WorldWide Internet. This architecture became in 1974 the TCP/IP Reference Model, which differs from its predecessor by layers functionalities:
 
 

OSI seven-layers Model
TCP-IP Reference Model
 
It is the totality of all applications and their relating protocols that use networks and have not yet been represented by the lower layers.  Like OSI Model, it contains all the higher-level protocols.
Here are the standards necessary for unambiguously representing data and more generally, a syntax of messages to be transmitted (simple text, executable code, pictures...). . Because no need for them was perceived, Presentation and Session layers are not included in the TCP/IP Model
It establishes a connection with another node and manages the data flow from the higher layers to the lower ones by managing the timing of data transmission and the memory buffer managing, when several applications try to transmit data at the same time.
. .
It handles the transmission, reception and error checking of the data.
The same as OSI Model
It is concerned with the physical transmission of the data from computer to computer. There is one further level of software to be considered, the network level. It routes the packages across a particular network.
It is the linchpin that holds the whole architecture together : it permits to send and receive packets, even if they are in random order. 
 
It handles the transmission of a framed set of data (usually a sequence of bits) from one point in a network (node) to another one. This layer also represents the boundary betweenhardware (e.g. CRC) and software implementation (e.g. physical addressing).
 
 
 
The TCP/IP reference model does not really say much about what happens here, except to point out that the host has to  
 
The physical medium used to transmit the information. To specify this layer, it is necessary to define the physical properties of the connection, such as mechanical properties, electrical/optical properties, functional aspects of the data transmission (modulation/demodulation for example) and procedural aspects of data transmission (e.g. bit stuffing to ensure that special signals are unequivocal).
 
 
 
 
 
 
 
 
connect to the network using some protocol so it can send IP packets over it. This protocol is not defined and varies from host to host and network to network. 
 
 
 
 
 
So, you can see that TCP/IP Reference Model and OSI Reference Model have a lot of things in common. Conceptually, it is useful to envision TCP/IP as a stack, each layer corresponding to a different facet of communication.