http://ingex.blogspot.

com/

Comunicando con PROFINET

EVOLUCIN DE PROFIBUS A PROFINET Dentro de los sistemas de automatizacin SIMATIC han existido diversos buses de campo. Los mismos fueron evolucionando con el tiempo hacia nuevas tecnologas. Por ejemplo los buses SINEC L1, SINEC L2 o SINEC H1. En 1989, con el fin de permitir a los usuarios interconectar equipos de diferentes fabricantes se desarroll el protocolo Profibus, gracias al trabajo de quince empresas e institutos, entre ellos la firma Siemens. Profibus es una evolucin del protocolo SINEC L2, aunque no son compatibles entre s. No es raro encontrar en funcionamiento mdulos de comunicacin IM308B para los S5-135U, comunicados con S5-95U con puerto integrado SINEC L2. Si estudiamos el protocolo Profibus segn el modelo ISO/OSI para protocolos de comunicacin veremos que en la capa 1, capa fsica, utiliza el estndar RS485. Esto es un bus diferencial de dos hilos no trenzados y apantallados. Hoy en da Profibus cuenta con aproximadamente 20 millones de nodos instalados alrededor del mundo, y demostr ser uno de los mejores buses de campo. INTRODUCCIN A PROFINET An as, el mercado exige un paso ms y as nace el estndar PROFINET; un bus de comunicacin industrial basado en Ethernet industrial.

Aqu dejo un link hacia un muy buen curso online gratuito de Siemens sobre PROFINET: Curso online PROFINET
Publicado por Ingex en 18:58 2 comentarios

martes 20 de noviembre de 2007

Automatizando con Step7 - S7-300/400

Lleg la hora de los grandes de la familia SIMATIC. El S7-300 y el S7400. Estos PLC son programados desde una misma interfase con los mismos lenguajes y mismos procedimientos. Estas familias se integran al SIMATIC Manager, un verdadero administrador de proyectos que no solo nos permite crear programas sino tambin interconectar equipos, administrar Paneles HMI, sistemas SCADA, variadores de velocidad, instrumentos de campo, y todo tipo de equipamiento utilizado en la industria. Todo esto se debe al concepto TIA de Siemens (Totally Integrated Automation). Es mucho lo que hay para aprender sobre el Step7 y el SIMATIC Manager, as que aqu dejo una serie de enlaces a los cursos gratuitos de Siemens. Los mismos se descargan al PC y estn en ingls nicamente. 1) 2) 3) 4) 5) 6) 7) 8) El SIMATIC Manager Arquitectura SIMATIC S7 Los lenguajes de programacin KOP, FUP y AWL Comunicacin con SIMATIC S7 Visualizacin - la integracin HMI Funciones de test y puesta en funcionamiento El idioma elevado S7-SCL (Similar al Pascal) El idioma grfico S7-GRAPH

Recomiendo seguirlos en ste orden.

Publicado por Ingex en 18:50 0 comentarios

Profibus
From Wikipedia, the free encyclopedia

Jump to: navigation, search PROFIBUS Protocol Information Type of Device Bus, Process Control Network Physical Media Twisted pair, fiber Network Bus Topology Device DIP Switch or hardware/software Addressing Governing PROFIBUS&PROFINET Body International (PI) Website www.profibus.com PROFIBUS (Process Field Bus) is a standard for field bus communication in automation technology and was first promoted (1989) by BMBF (German department of education and research). It should not be confused with the PROFINET standard for industrial Ethernet.

Contents
[hide]

1 Origin 2 Use 3 Technology o 3.1 Application layer o 3.2 Security layer o 3.3 Bit-transmission layer 4 Standardization 5 Organization 6 References 7 External links

[edit] Origin

The history of PROFIBUS goes back to a publicly promoted plan for an association started in Germany in 1987 and for which 21 companies and institutes devised a master project plan called "field bus". The goal was to implement and spread the use of a bitserial field bus based on the basic requirements of the field device interfaces. For this purpose, respective member companies agreed to support a common technical concept for production and process automation. First, the complex communication protocol Profibus FMS (Field bus Message Specification), which was tailored for demanding communication tasks, was specified. Subsequently in 1993, the specification for the simpler and thus considerably faster protocol PROFIBUS DP (Decentralized Peripherals) was completed. It replaced FMS.

[edit] Use
There are two variations of PROFIBUS; the most commonly used DP, and the lesser used PA variations:

PROFIBUS DP (Decentralized Peripherals) is used to operate sensors and actuators via a centralized controller in production technology. The many standard diagnostic options, in particular, are focused on here. Other areas of use include the connection of "distributed intelligence", i.e. the networking of multiple controllers to one another (similar to PROFIBUS FMS). Data rates up to 12 Mbit/s on twisted pair cables and/or fiber optics are possible. PROFIBUS PA (Process Automation) is used to monitor measuring equipment via a process control system in process engineering. This PROFIBUS variant is ideal for explosion-hazardous areas (Ex-zone 0 and 1). Here, a weak current flows through bus lines in an intrinsically safe circuit so that explosive sparks are not created, even if a malfunction occurs. The disadvantage of this variant is the slower data transmission rate of 31.25 kbit/s.

PROFIBUS is the only field bus that can be used in equal measure in production automation and process automation and has since become a global market leader. Worldwide, over 20 million PROFIBUS devices are in use (as of 2007).

[edit] Technology
PROFIBUS Protocol (OSI reference model) OSI-Layer 7 Application 6 Presentation 5 Session 4 Transport 3 Network PROFIBUS DPV0 DPV1 DPV2 Management --

2 Data Link FDL 1 Physical EIA-485 Optical MBP

[edit] Application layer

To utilize these functions, various service levels of the DP protocol were defined:

DP-V0 for cyclic exchange of data and diagnosis DP-V1 for acyclic and cyclic data exchange and alarm handling DP-V2 for isochronous mode and data exchange broadcast (slave-to-slave communication)

[edit] Security layer

The security layer FDL (Field bus Data Link) works with a hybrid access method that combines token passing with a master-slave method. In a PROFIBUS DP network, the controllers or process control systems are the masters and the sensors and actuators are the slaves. Various telegram types are used. They can be differentiated by their start delimiter (SD): No data: SD1 = 0x10 SD1 DA SA FC FCS ED Variable length data: SD2 = 0x68 SD2 LE LEr SD2 DA SA FC PDU FCS ED Fixed length data: SD3 = 0xA2 SD3 DA SA FC PDU FCS ED

Token: SD4 = 0xDC SD4 DA SA Brief acknowledgement: SC = 0xE5 SC

SD: Start Delimiter LE: Length of protocol data unit, (incl. DA,SA,FC,DSAP,SSAP) LEr: Repetition of protocol data unit, (Hamming distance = 4) FC: Function Code DA: Destination Address SA: Source Address DSAP: Destination Service Access Point SSAP: Source Service Access Point PDU: Protocol Data Unit (protocol data) FCS: Frame Checking Sequence ED: End Delimiter (= 0x16 !) The FCS is calculated by simply adding up the bytes within the specified length. An overflow is ignored here. Each byte is saved with an even parity and transferred asynchronously with a start and stop bit. There may not be a pause between a stop bit and the following start bit when the bytes of a telegram are transmitted. The master signals the start of a new telegram with a SYN pause of at least 33 bits (logical "1" = bus idle).

[edit] Bit-transmission layer

Three different methods are specified for the bit-transmission layer:

With electrical transmission pursuant to EIA-485, twisted pair cables with a wave impedances of 150 ohms are used in a bus topology. Bit rates from 9.6 kbit/s to 12 Mbit/s can be used. The cable length between two repeaters is limited to 100 to 1200 m, depending on the bit rate used. This transmission method is primarily used with PROFIBUS DP. With optical transmission via fiber optics, star-, bus- and ring-topologies are used. The distance between the repeaters can be up to 15 km. The ring topology can also be executed redundantly. With MBP (Manchester Bus Powered) transmission technology, data and field bus power are fed through the same cable. The power can be reduced in such a way that use in explosion-hazardous environments is possible. The bus topology can be up to 1900 m long and permits branching to field devices (max. 60 m branches). The bit rate here is a fixed 31.25 kbit/s. This technology was specially established for use in process automation for PROFIBUS PA.

For data transfer via sliding contacts for mobile devices or optical or radio data transmission in open spaces, products from various manufacturers can be obtained, however they do not conform to any standard.

[edit] Standardization
PROFIBUS was defined in 1991/1993 in DIN 19245, was then included in EN 50170 in 1996 and, since 1999, established in IEC 61158/IEC 61784.

[edit] Organization
The PROFIBUS Nutzerorganisation e.V. (PROFIBUS User Organization) (PNO) was created in 1989. This group is comprised of manufacturers and users from Germany. In 1992, the first regional PROFIBUS organization was founded (PROFIBUS Schweiz in Switzerland). In the following years, additional RPAs (Regional PROFIBUS & PROFINET Associations) were added. Today, PROFIBUS is represented by 25 RPAs around the world. In 1995, all the RPAs joined together into the international umbrella association PROFIBUS & PROFINET International (PI).

[edit] References

Sinec H1
From Wikipedia, the free encyclopedia

Jump to: navigation, search Sinec H1 is an Ethernet-based protocol that provides the transport layer function. The protocol was developed by Siemens and is used mainly for control applications. It has large bandwidth and is well suited to the transmission of large volumes of data.

http://www.ipcomm.de/protocol/SinecH1/en/sheet.html

OSI model
From Wikipedia, the free encyclopedia

Jump to: navigation, search This article needs additional citations for verification.
Please help improve this article by adding reliable references. Unsourced material may be challenged and removed. (February 2008)

OSI Model 7 Application Layer 6 Presentation Layer 5 Session Layer 4 Transport Layer 3 Network Layer 2 Data Link Layer

LLC sublayer MAC sublayer

1 Physical Layer The Open Systems Interconnection Basic Reference Model (OSI Reference Model or OSI Model) is an abstract description for layered communications and computer network

protocol design. It was developed as part of the Open Systems Interconnection (OSI) initiative[1]. In its most basic form, it divides network architecture into seven layers which, from top to bottom, are the Application, Presentation, Session, Transport, Network, Data-Link, and Physical Layers. It is therefore often referred to as the OSI Seven Layer Model. A layer is a collection of conceptually similar functions that provide services to the layer above it and receives service from the layer below it. For example, a layer that provides error-free communications across a network provides the path needed by applications above it, while it calls the next lower layer to send and receive packets that make up the contents of the path. Even though it has been largely superseded by newer IETF, IEEE, and indeed OSI protocol developments (subsequent to the publication of the original architectural standards), the basic OSI model is considered an excellent place to begin the study of network architecture. Not understanding that the pure seven-layer model is more historic than current, many beginners make the mistake of trying to fit every protocol under study into one of the seven basic layers. Especially the attempts of cross-layer optimization break the boundaries of the original layer scheme. Describing the actual layer concept with implemented systems is not always easy to do as most of the protocols in use on the Internet were designed as part of the TCP/IP model, and may not fit cleanly into the OSI Model.

Contents
[hide]

1 History 2 Description of OSI layers o 2.1 Layer 7: Application Layer o 2.2 Layer 6: Presentation Layer o 2.3 Layer 5: Session Layer o 2.4 Layer 4: Transport Layer o 2.5 Layer 3: Network Layer o 2.6 Layer 2: Data Link Layer 2.6.1 WAN Protocol architecture 2.6.2 IEEE 802 LAN architecture o 2.7 Layer 1: Physical Layer 3 Interfaces 4 Examples 5 Comparison with TCP/IP 6 Remembering The OSI Layers 7 References 8 External links

[edit] History
In 1977, work on a layered model of network architecture was started, and the International Organization for Standardization (ISO) began to develop its OSI framework architecture. The ISO is a worldwide federation of national standards bodies from some 130 countries, one from each country.[citation needed] OSI has two major components: an abstract model of networking (the Basic Reference Model, or seven-layer model) and a set of specific protocols. The standard documents that describe the OSI model can be freely downloaded from the ITU-T as the X.200-series of recommendations [2]. A number of the protocol specifications are also available as part of the ITU-T X series. The equivalent ISO and ISO/IEC standards for the OSI model are available from the ISO, but only some of the ISO/IEC standards are available as cost-free downloads.[3] Some aspects of OSI design evolved from experiences with the CYCLADES network, which also influenced Internet design. The new design was documented in ISO 7498 and its various addenda. In this model, a networking system is divided into layers. Within each layer, one or more entities implement its functionality. Each entity interacts directly only with the layer immediately beneath it, and provides facilities for use by the layer above it.

OSI Model Data unit Host Data layers Packet Media Frame layers Bit Layer Function 7. Application Network process to application 6. Presentation Data representation and encryption 5. Session 3. Network 2. Data Link 1. Physical
Interhost communication End-to-end connections and reliability Path determination and logical addressing Physical addressing (MAC & LLC) Media, signal and binary transmission

Segment/Datagram 4. Transport

Protocols enable an entity in one host to interact with a corresponding entity at the same layer in another host. Service definitions abstractly 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.

[edit] Description of OSI layers

[edit] Layer 7: Application Layer
Main article: Application Layer

The application layer is the OSI layer closest to the end user, which means that both the OSI application layer and the user interact directly with the software application. This layer interacts with software applications that implement a communicating component. Such application programs fall outside the scope of the OSI model. Application layer functions typically include identifying communication partners, determining resource availability, and synchronizing communication. When identifying communication partners, the application layer determines the identity and availability of communication partners for an application with data to transmit. When determining resource availability, the application layer must decide whether sufficient network resources for the requested communication exist. In synchronizing communication, all communication between applications requires cooperation that is managed by the application layer. Some examples of application layer implementations include Telnet, File Transfer Protocol (FTP), and Simple Mail Transfer Protocol (SMTP).

[edit] Layer 6: Presentation Layer

Main article: Presentation Layer The Presentation Layer establishes a context between Application Layer entities, in which the higher-layer entities can use different syntax and semantics, as long as the Presentation Service understands both and the mapping between them. The presentation service data units are then encapsulated into Session Protocol Data Units, and moved down the stack. The original presentation structure used the Basic Encoding Rules of Abstract Syntax Notation One (ASN.1), with capabilities such as converting an EBCDIC-coded text file to an ASCII-coded file, or serializing objects and other data structures into and out of XML. ASN.1 has a set of cryptographic encoding rules that allows end-to-end encryption between application entities.

[edit] Layer 5: Session Layer

Main article: Session Layer The Session Layer controls the dialogues/connections (sessions) between computers. It establishes, manages and terminates the connections between the local and remote application. It provides for full-duplex, half-duplex, or simplex operation, and establishes checkpointing, adjournment, termination, and restart procedures. The OSI model made this layer responsible for "graceful close" of sessions, which is a property of TCP, and also for session checkpointing and recovery, which is not usually used in the Internet Protocol Suite. The Session Layer is commonly implemented explicitly in application environments that use remote procedure calls (RPCs).

[edit] Layer 4: Transport Layer

Main article: Transport Layer

The Transport Layer provides transparent transfer of data between end users, providing reliable data transfer services to the upper layers. The Transport Layer controls the reliability of a given link through flow control, segmentation/desegmentation, and error control. Some protocols are state and connection oriented. This means that the Transport Layer can keep track of the segments and retransmit those that fail. Although not developed under the OSI Reference Model and not strictly conforming to the OSI definition of the Transport Layer, the best known examples of a Layer 4 protocol are the Transmission Control Protocol (TCP) and User Datagram Protocol (UDP). Of the actual OSI protocols, there are five classes of transport protocols ranging from class 0 (which is also known as TP0 and provides the least error recovery) to class 4 (which is also known as TP4 and is designed for less reliable networks, similar to the Internet). Class 0 is closest to UDP. Class 4 is closest to TCP, although TCP contains functions, such as the graceful close, which OSI assigns to the Session Layer. Detailed characteristics of TP0-4 classes are shown in the following table:[4] Feature Name TP0 TP1 TP2 TP3 TP4

Connection oriented

Yes Yes

Connectionless

No Yes

Segmentation/Fragmentation

Yes Yes Yes Yes Yes

Reassembly

Yes Yes Yes Yes Yes

Error Recovery

No Yes No No Yes

Reinitiate connection (if an excessive number of PDUs are unacknowledged)

No Yes No Yes Yes

multiplexing and demultiplexing over a single virtual circuit

No No Yes Yes Yes

Reliable Transport Service

No Yes Yes Yes Yes

Perhaps an easy way to visualize the Transport Layer is to compare it with a Post Office, which deals with the dispatch and classification of mail and parcels sent. Do remember, however, that a post office manages the outer envelope of mail. Higher layers may have the equivalent of double envelopes, such as cryptographic presentation services that can be read by the addressee only. Roughly speaking, tunneling protocols operate at the Transport Layer, such as carrying non-IP protocols such as IBM's SNA or Novell's IPX over an IP network, or end-to-end encryption with IPsec. While Generic Routing Encapsulation (GRE) might seem to be a Network Layer protocol, if the encapsulation of the payload takes place only at endpoint, GRE becomes closer to a transport protocol that uses IP headers but contains complete frames or packets to deliver to an endpoint. L2TP carries PPP frames inside transport packet.

[edit] Layer 3: Network Layer

Main article: Network Layer The Network Layer provides the functional and procedural means of transferring variable length data sequences from a source to a destination via one or more networks, while maintaining the quality of service requested by the Transport Layer. The Network Layer performs network routing functions, and might also perform fragmentation and reassembly, and report delivery errors. Routers operate at this layersending data throughout the extended network and making the Internet possible. This is a logical addressing scheme values are chosen by the network engineer. The addressing scheme is hierarchical. The best-known example of a Layer 3 protocol is the Internet Protocol (IP). It manages the connectionless transfer of data one hop at a time, from end system to ingress router, router to router, and from egress router to destination end system. It is not responsible for reliable delivery to a next hop, but only for the detection of errored packets so they may be discarded. When the medium of the next hop cannot accept a packet in its current length, IP is responsible for fragmenting into sufficiently small packets that the medium can accept it. A number of layer management protocols, a function defined in the Management Annex, ISO 7498/4, belong to the Network Layer. These include routing protocols, multicast group management, Network Layer information and error, and Network Layer address assignment. It is the function of the payload that makes these belong to the Network Layer, not the protocol that carries them.

[edit] Layer 2: Data Link Layer

Main article: Data Link Layer The Data Link Layer provides the functional and procedural means to transfer data between network entities and to detect and possibly correct errors that may occur in the Physical Layer. Originally, this layer was intended for point-to-point and point-to-

multipoint media, characteristic of wide area media in the telephone system. Local area network architecture, which included broadcast-capable multiaccess media, was developed independently of the ISO work, in IEEE Project 802. IEEE work assumed sublayering and management functions not required for WAN use. In modern practice, only error detection, not flow control using sliding window, is present in modern data link protocols such as Point-to-Point Protocol (PPP), and, on local area networks, the IEEE 802.2 LLC layer is not used for most protocols on Ethernet, and, on other local area networks, its flow control and acknowledgment mechanisms are rarely used. Sliding window flow control and acknowledgment is used at the Transport Layer by protocols such as TCP, but is still used in niches where X.25 offers performance advantages. Both WAN and LAN services arrange bits, from the Physical Layer, into logical sequences called frames. Not all Physical Layer bits necessarily go into frames, as some of these bits are purely intended for Physical Layer functions. For example, every fifth bit of the FDDI bit stream is not used by the Data Link Layer.

[edit] WAN Protocol architecture

Connection-oriented WAN data link protocols, in addition to framing, detect and may correct errors. They also are capable of controlling the rate of transmission. A WAN Data Link Layer might implement a sliding window flow control and acknowledgment mechanism to provide reliable delivery of frames; that is the case for SDLC and HDLC, and derivatives of HDLC such as LAPB and LAPD.

[edit] IEEE 802 LAN architecture

Practical, connectionless LANs began with the pre-IEEE Ethernet specification, which is the ancestor of IEEE 802.3. This layer manages the interaction of devices with a shared medium, which is the function of a Media Access Control sublayer. Above this MAC sublayer is the media-independent IEEE 802.2 Logical Link Control (LLC) sublayer, which deals with addressing and multiplexing on multiaccess media. While IEEE 802.3 is the dominant wired LAN protocol and IEEE 802.11 the wireless LAN protocol, obsolescent MAC layers include Token Ring and FDDI. The MAC sublayer detects but does not correct errors.

[edit] Layer 1: Physical Layer

Main article: Physical Layer The Physical Layer defines all the electrical and physical specifications for devices. In particular, it defines the relationship between a device and a physical medium. This includes the layout of pins, voltages, cable specifications, Hubs, repeaters, network adapters, Host Bus Adapters (HBAs used in Storage Area Networks) and more.

To understand the function of the Physical Layer in contrast to the functions of the Data Link Layer, think of the Physical Layer as concerned primarily with the interaction of a single device with a medium, where the Data Link Layer is concerned more with the interactions of multiple devices (i.e., at least two) with a shared medium. The Physical Layer will tell one device how to transmit to the medium, and another device how to receive from it (in most cases it does not tell the device how to connect to the medium). Obsolescent Physical Layer standards such as RS-232 do use physical wires to control access to the medium. The major functions and services performed by the Physical Layer are:

Establishment and termination of a connection to a communications medium. Participation in the process whereby the communication resources are effectively shared among multiple users. For example, contention resolution and flow control. Modulation, or conversion between the representation of digital data in user equipment and the corresponding signals transmitted over a communications channel. These are signals operating over the physical cabling (such as copper and optical fiber) or over a radio link.

Parallel SCSI buses operate in this layer, although it must be remembered that the logical SCSI protocol is a Transport Layer protocol that runs over this bus. Various Physical Layer Ethernet standards are also in this layer; Ethernet incorporates both this layer and the Data Link Layer. The same applies to other local-area networks, such as Token ring, FDDI, and IEEE 802.11, as well as personal area networks such as Bluetooth and IEEE 802.15.4.

[edit] Interfaces
Neither the OSI Reference Model nor OSI protocols specify any programming interfaces, other than as deliberately abstract service specifications. Protocol specifications precisely define the interfaces between different computers, but the software interfaces inside computers are implementation-specific. 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 (Layer 2) and the network protocol (Layer 3). Interface standards, except for the Physical Layer to media, are approximate implementations of OSI Service Specifications.

[edit] Examples

Layer Misc. examples # Name TCP/IP SS7[ AppleTalk IPX OSI suite SNA 5] suite suite suite UMTS

Applica HL7, tion Modbus

NNTP, SIP, SSI, DNS, INA FTP, P, Gopher, MA HTTP, P, AFP, ZIP, NFS, TCA RTMP, NBP NTP, P, DHCP, ISU SMPP, P, SMTP, TUP SNMP, Telnet

FTAM, X.400, X.500, DAP, ROSE, RTSE, ACSE

RIP, APP SAP C

MIME, XDR, TDI, ASCII, SSL, Present 6 EBCDIC, TLS ation MIDI, MPEG (Not a separate layer)

AFP

ISO/IEC 8823, X.226, ISO/IEC 9576-1, X.236

Sockets. Session establish ment in Named Pipes, TCP. NetBIOS, SIP. SAP, Half 5Session (Not a Duplex,Full separate Duplex,Simpl layer ex,SDP with standardi zed API.)

ISO/IEC 8327, ASP, ADSP, X.225, NWL DLC PAP ISO/IEC ink ? 9548-1, X.235

NBF, Transpo 4 nanoTCP, rt nanoUDP

TCP, UDP,PP TP, L2TP, SCTP, RTP

DDP

ISO/IEC 8073, TP0, TP1, TP2, SPX TP3, TP4 (X.224), ISO/IEC 8602, X.234

IP, IPsec, ARP, ICMP, Networ 3 NBF, Q.931 RIP, k OSPF, BGP, IGMP, IS-IS

ISO/IEC 8208, X.25 (PLP), SCC ATP ISO/IEC P, (TokenTalk 8878, IPX MT or EtherTalk) X.223, P ISO/IEC 8473-1, CLNP X.233.

RRC (Radio Resource Control) Packet Data Convergence Protocol (PDCP) and BMC (Broadcast/M ulticast Control)

Data Link

802.3 (Ethernet), 802.11a/b/g/n MAC/LLC, 802.1Q (VLAN), ATM, HDP, PPP, FDDI, Fibre SLIP Channel, Frame Relay, HDLC, ISL, PPP, Q.921, Token Ring, CDP

ISO/IEC 7666, X.25 (LAPB), MT LocalTalk,Ap Token P, pleTalk Bus, Q.71 Remote X.222, 0 Access, PPP ISO/IEC 8802-2 LLC Type 1 and 2

IEEE 802.3 LLC (Logical frami Link ng, SDL Control), Ether C MAC (Media net II Access frami Control) ng

RS-232, Physica V.35, V.34, 1 l I.430, I.431, T1, E1,

X.25 MT RS-232, RS(X.21bis, P, 422, STP, EIA/TIAQ.71 PhoneNet 232,

Twin UMTS L1 ax (UMTS Physical

10BASE-T, 100BASETX, POTS, SONET, SDH,DSL, 802.11a/b/g/n PHY

EIA/TIA449, EIA530, G.703)

Layer)

[edit] Comparison with TCP/IP

In the TCP/IP model of the Internet, protocols are deliberately not as rigidly designed into strict layers as the OSI model.[6] RFC 3439 contains a section entitled "Layering considered harmful." However, TCP/IP does recognize four broad layers of functionality which are derived from the operating scope of their contained protocols, namely the scope of the software application, the end-to-end transport connection, the internetworking range, and lastly the scope of the direct links to other nodes on the local network. Even though the concept is different than in OSI, these layers are nevertheless often compared with the OSI layering scheme in the following way: The Internet Application Layer includes the OSI Application Layer, Presentation Layer, and most of the Session Layer. Its end-to-end Transport Layer includes the graceful close function of the OSI Session Layer as well as the OSI Transport Layer. The internetworking layer (Internet Layer) is a subset of the OSI Network Layer, while the Link Layer includes the OSI Data Link and Physical Layers, as well as parts of OSI's Network Layer. These comparisons are based on the original seven-layer protocol model as defined in ISO 7498, rather than refinements in such things as the internal organization of the Network Layer document. The presumably strict consumer/producer layering of OSI as it is usually described does not present contradictions in TCP/IP, as it is permissible that protocol usage does not follow the hierarchy implied in a layered model. Such examples exist in some routing protocols (e.g., OSPF), or in the description of tunneling protocols, which provide a Link Layer for an application, although the tunnel host protocol may well be a Transport or even an Application Layer protocol in its own right. The TCP/IP design generally favors decisions based on simplicity, efficiency and ease of implementation.

[edit] Remembering The OSI Layers

Various mnemonics have been created over the years to help remember the order of the OSI layers. Often cited are the following:

Please Do Not Throw Sausage Pizza Away All People Seem To Need Data Processing

[edit] References
1. 2. 3. 4. ^ reference needed ^ ITU-T X-Series Recommendations. ^ Publicly Available Standards ^ "ITU-T Recommendation X.224 (11/1993) [ISO/IEC 8073]". Retrieved on 2008-06-18. 5. ^ ITU-T Recommendation Q.1400 (03/1993), Architecture framework for the development of signalling and OA&M protocols using OSI concepts, pp 4, 7. 6. ^ RFC 3439

[edit] External links