What is the ap­plic­a­tion layer in the OSI model?

The ap­plic­a­tion layer is the seventh and, therefore, highest layer of the OSI model. It manages com­mu­nic­a­tion across different ap­plic­a­tion programs within a network. The OSI model ap­plic­a­tion layer can carry out general as well as user-ori­ent­ated services and is used by a wide range of protocols.

The OSI model (short for Open Systems In­ter­con­nec­tion Model) has been the standard for open com­mu­nic­a­tion between different systems since 1983. It defines common features that are not tied to a specific man­u­fac­turer, allowing for different software and hardware to be com­pat­ible. This reference model dif­fer­en­ti­ates network com­mu­nic­a­tion across seven layers. The seventh, which is also the highest layer, is called the ap­plic­a­tion level. This layer has different contact with different ap­plic­a­tions and makes services as well as data struc­tures available. The different layers from bottom to top are as follows:

1. Physical layer
2. Data link layer
3. Network layer
4. Transport layer
5. Session layer
6. Present­a­tion layer
7. Ap­plic­a­tion layer

The ap­plic­a­tion layer ensures efficient and secure com­mu­nic­a­tion between different ap­plic­a­tion programs within a network. In doing so, it not only works as an ap­plic­a­tion on its own, but also carries out other functions as well. Among these are:

• Iden­ti­fic­a­tion: to do this, the OSI model ap­plic­a­tion layer ensures that the page you are trying to reach, can, on the one hand, be reached and, on the other, clearly identify itself without any issues.
• Au­then­tic­a­tion: in the context of com­mu­nic­a­tion by email, the ap­plic­a­tion layer can identify both the sender and the receiver of an email, or just one of the two.
• Analysis: the ap­plic­a­tion layer can be used to ensure that the relevant re­quire­ments have been met so that two systems can com­mu­nic­ate with each other. For example, it can be used to check if there is an active network con­nec­tion.
• Security: the ap­plic­a­tion layer verifies that protocols and pro­ced­ures regarding privacy, data status and troubleshoot­ing are followed and con­sist­ent on both sides of the com­mu­nic­a­tion systems.
• Mon­it­or­ing: the ap­plic­a­tion layer monitors data syntax rules and ensures that the network protocol is main­tained during the in­ter­ac­tion.

The ap­plic­a­tion layer operates several services, most of which can be split into two larger cat­egor­ies: CASE (Common Ap­plic­a­tion Service Elements) and SASE (Specific Ap­plic­a­tion Service Elements).

CASE is the found­a­tion for SASE and refers to general functions which regulate the co­ordin­a­tion of other protocols. Among standard ap­plic­a­tions, this includes order transfer, data transfer and email features. An example of a common ap­plic­a­tion service element in the ap­plic­a­tion layer would be directory services. These can be used to create a dis­tri­bu­tion list or give a server a specific name or address for a specific service or action.

In contrast to CASE, SASE is used to create user-oriented functions that are ap­plic­a­tion specific and often built upon CASE. This may include user-oriented dir­ect­or­ies, email, virtual terminals, data transfers, or the transfer of graphics and media.

While the two services were initially designed to be used sep­ar­ately, in practice, there is a great deal of overlap between the two. This is due to how SASE and CASE interact with each other as well as the fact that SASE is dependent on CASE. Together, they are commonly known as As­so­ci­ation Control Service Elements (ACSE).

There are many protocols which use the OSI model ap­plic­a­tion layer. The most well-known of these are the TCP/IP protocols sein, which form the basis of network com­mu­nic­a­tion and the internet. Other programs that use the ap­plic­a­tion layer include:

• HTTP (hypertext transfer protocol): this is used to transfer HTML sites. 
• HTTPS (hypertext transfer protocol): this is the encrypted version of the transfer protocol.
• Telnet (tele­com­mu­nic­a­tion network): this network allows remote computers to access virtual terminals.
• FTP (file transfer protocol): FTP allows data to be trans­ferred between two computers even if they are built dif­fer­ently and have different operating systems.
• TFTP (trivial file transfer protocol): this protocol is similar to FTP but uses UDP.
• SMTP (simple mail transfer protocol): this protocol allows emails to be sent between two computers.
• DNS (domain name system): this protocol trans­forms domains into IP addresses.
• NFS (network file system):this protocol provides access to remote data via a network.
• POP (post office protocol): this protocol retrieves emails from a server and, if necessary, can delete them.
• NTP (network time protocol): this protocol is the syn­chron­iz­a­tion standard for multiple networks. Ad­di­tion­ally, time stamps can be created using this protocol.
• NNTP (network news transfer protocol): this transfer protocol is used to manage messages and news­groups.
• SSH (secure shell): this allows for a secure con­nec­tion between two computers in a network.
• SNMP (simple network man­age­ment protocol): this is used to manage and monitor networks. In addition, it also enables com­mu­nic­a­tion to networks from a central location.