Interconnetion Model Referance â The Open System
Legacy signals
Legacy popularity: 698 legacy views
Reader rating
Not enough ratings yet
Aggregate average appears after enough eligible reader ratings.
Rate this resource
Sign in to rate this resource.
The Open System Interconnection Reference Model or OSI Reference Model or OSI Model is basically a conceptual description for layered communications and computer network protocol design. It was created as part of the Open Systems Interconnection or OSI initiative. In its most fundamental form, it segments network architecture into seven distinct layers: the Application, Presentation, Session, Transport, Network, Data-Link, and Physical Layers.
As a result it is frequently referred to as the OSI Seven Layer Model. A layer is a collection of theoretically similar functions that provide services to the layer directly above it and gets service from the layer beneath it. On each single layer an instance provides services to the instances at the layer above and requests service from the layer beneath. An example of this relates to a layer that provides error-free communications across a network which then provides the path needed by applications above it, while it calls the next lower layer to send and receive packets that comprise the contents of the path.
Work on a layered model of network architecture commenced in the year 1977. Simultaneously the International Organization for Standardization or ISO started to develop its OSI framework architecture. OSI has two major parts: an abstract model of networking, called the Basic Reference Model or seven-layer model and a set of specific protocols. It is important to note that the standard documents that describe the OSI model can be freely downloaded from the ITU-T as the X.200-series of recommendations. A number of the protocol specifications can also be accessed as part of the ITU-T X series. The equivalent ISO and ISO/IEC standards for the OSI model are available from ISO, however not all of these are available free.
Every area of the OSI design evolved from experiences with the CYCLADES network, which also had a large influence on the design of the internet. The latest design has been meticulously documented in ISO 7498 and several of its addenda. In this latest model, a networking system is segmented into layers. Within each layer, one or more entities proves its functionality. Each entity will interact directly only with the layer just below it, and enables facilities for use by the layer above it.
Protocols will allow an entity in one host to interact with a corresponding entity at the same layer in another host. Service definitions ideally describe the functionality provided to an (N)-layer by an (N-1) layer, where N is one of the seven layers of protocols operating in the local host.
Neither the OSI Reference Model nor OSI protocols designate any programming interfaces, other than a purposely abstract service specifications. Protocol specifications precisely define the interfaces between multiple computers, but the software interfaces within computers are implementation-specific.
Take for example, Microsoft Windows' Winsock, and Unix's Berkeley sockets and System V Transport Layer Interface, are interfaces between applications (Layer 5 and above) and the transport (Layer 4). NDIS and ODI are interfaces between the media in Layer 2 and the network protocol in Layer 3. Interface standards, with the exception of the Physical Layer to media, are estimated implementations of OSI Service Specifications.
Article author
About the Author
Further reading
Further Reading
Article
What to Consider When Adopting Multi-Tenancy in Kubernetes?
Organizations are starting to scale their cloud native operations. And as they do, the inefficiency of managing dozens of isolated clusters has become an evident problem. As the clusters continue to sprawl, businesses must unite diverse workloads onto shared infrastructure. This is because companies need better resource utilization and centralized governance among other things. But it is imperative to remember that going from a single tenant to a multi-tenant environment need
March 12, 2026
Article
Product Engineering Services: Driving Faster Development for Startups
It has been for everyone to see the short product lifecycles and a pressing need for rapid technical scalability that have come to define the modern startup ecosystem. For early-stage companies, the challenge is no longer just conceptualizing a solution. But they must also carry it out with enough precision to withstand high market volatility and fierce competition. We know that internal teams concentrate on core business strategy and fundraising. That still leaves us with th
March 12, 2026
Article
Why Modern Facilities Rely on Environmental Monitoring and Remote Temperature Probes for Compliance and Control
In today’s regulated and data-driven environments, organizations are under constant pressure to ensure that temperature and environmental conditions remain within defined limits. Even small fluctuations can result in product loss, compliance violations, or operational downtime. As a result, many facilities are moving away from manual checks and standalone sensors and adopting comprehensive environmental monitoring solutions instead. An environmental monitor provides rea
March 5, 2026
Article
Role of Data Warehousing in Ensuring Data Quality and Consistency
Organizations have come to rely heavily on large amounts of data in today's competitive markets. But to what end? For starters, to inform strategic decisions and power machine learning models. It goes without saying that the value of these digital assets is completely dependent on the accuracy of the underlying data. So, when data is fragmented or inconsistent across departments, you will obviously have inaccurate reporting and operational inefficiencies at your hands. This c
March 2, 2026