Senin, 08 Juni 2009

Universal Mobile Telecommunications System (UMTS)

Universal Mobile Telecommunications System (UMTS) is one of the third-generation (3G) mobile telecommunications technologies, which is also being developed into a 4G technology. It is specified by 3GPP and is part of the global ITU IMT-2000 standard. The most common form of UMTS uses W-CDMA (IMT Direct Spread) as the underlying air interfaceTD-CDMA and TD-SCDMA (both IMT CDMA TDD). Being a complete network system, UMTS also covers the radio access network (UMTS Terrestric Radio Access Network; UTRAN), the core network (Mobile Application Part; MAP) as well as authentication of users via USIM cards (Subscriber Identity Module). but the system also covers

Unlike EDGE (IMT Single-Carrier, based on GSM) and CDMA2000 (IMT Multi-Carrier), UMTS requires new cell towers and new frequency allocations. However, it is closely related to GSM/EDGE as it borrows and builds upon concepts from GSM. Further, most UMTS handsets also support GSM, allowing seamless dual-mode operation. Therefore, UMTS is sometimes marketed as 3GSM, emphasizing the close relationship with GSM and differentiating it from competing technologies.

Contents

[hide]

Features

UMTS, using W-CDMA, supports up to 21 Mbit/s data transfer rates in theory (with HSDPA),[1]HSDPA handsets in the downlink connection. This is still much greater than the 9.6 kbit/s of a single GSM error-corrected circuit switched data channel or multiple 9.6 kbit/s channels in HSCSD (14.4 kbit/s for CDMAOne), and—in competition to other network technologies such as CDMA2000, PHS or WLAN—offers access to the World Wide Web and other data services on mobile devices. although at the moment users in deployed networks can expect a transfer rate of up to 384 kbit/s for R99 handsets, and 7.2 Mbit/s for

Precursors to 3G are 2G mobile telephony systems, such as GSM, IS-95, PDC, CDMA PHS and other 2G technologies deployed in different countries. In the case of GSM, there is an evolution path from 2G, to GPRS, also known as 2.5G. GPRS supports a much better data rate (up to a theoretical maximum of 140.8 kbit/s, though typical rates are closer to 56 kbit/s) and is packet switched rather than connection oriented (circuit switched). It is deployed in many places where GSM is used. E-GPRS, or EDGE, is a further evolution of GPRS and is based on more modern coding schemes. With EDGE the actual packet data rates can reach around 180 kbit/s (effective). EDGE systems are often referred as "2.75G Systems".

Since 2006, UMTS networks in many countries have been or are in the process of being upgraded with High Speed Downlink Packet Access (HSDPA), sometimes known as 3.5G. Currently, HSDPA enables downlink transfer speeds of up to 21 Mbit/s. Work is also progressing on improving the uplink transfer speed with the High-Speed Uplink Packet Access (HSUPA). Longer term, the 3GPP Long Term Evolution project plans to move UMTS to 4G speeds of 100 Mbit/s down and 50 Mbit/s up, using a next generation air interface technology based upon Orthogonal frequency-division multiplexing.

The first national consumer UMTS networks launched in 2002 with a heavy emphasis on telco-provided mobile applications such as mobile TV and video calling. The high data speeds of UMTS are now most often utilised for Internet access: experience in Japan and elsewhere has shown that user demand for video calls is not high, and telco-provided audio/video content has declined in popularity in favour of high-speed access to the World Wide Web - either directly on a handset or connected to a computer via Wi-Fi, Bluetooth, Infrared or USB.

Technology

UMTS combines the W-CDMA, TD-CDMA, or TD-SCDMA air interfaces, GSM's Mobile Application Part (MAP) core, and the GSM family of speech codecs.

Air Interfaces

A UMTS Terrestrial Radio Access Network (UTRAN) can use three different air interfaces, all of which are part of ITU's IMT-2000. In the currently most popular variant for cellular mobile telephones, W-CDMA (IMT Direct Spread) is used. UMTS networks are often combined with GSM/EDGE, the later of which is also a part of IMT-2000. UMTS and GSM/EDGE can share a Core Network (CN), making UTRAN an alternative radio access network to GERAN (GSM/EDGE RAN), and allowing (mostly) transparent switching between the RANs according to available coverage and service needs. Because of that, UMTS' and GSM/EDGE's radio access networks are sometimes collectively referred to as UTRAN/GERAN.

Non-terrestrial radio access networks are currently under research.

W-CDMA (UTRA-FDD)

UMTS transmitter on the roof of a building

UMTS over W-CDMA uses a pair of 5 MHz channels. In contrast, the competing CDMA2000 system uses one or more arbitrary 1.25 MHz channels for each direction of communication. W-CDMA systems are widely criticized for their large spectrum usage, which has delayed deployment in countries that acted relatively slowly in allocating new frequencies specifically for 3G services (such as the United States).

The specific frequency bands originally defined by the UMTS standard are 1885–2025 MHz for the mobile-to-base (uplink) and 2110–2200 MHz for the base-to-mobile (downlink). In the US, 1710–1755 MHz and 2110–2155 MHz will be used instead, as the 1900 MHz band was already utilized.[2] While UMTS2100 is the most widely-deployed UMTS band, some countries' UMTS operators use the 850 MHz and/or 1900 MHz bands (independently, meaning uplink and downlink are within the same band), notably in the US by AT&T Mobility, and in Australia by Telstra on the Next G network.

W-CDMA is a part of IMT-2000 as IMT Direct Spread.

TD-CDMA (UTRA-TDD 3.84 Mcps High Chip Rate)

TD-CDMA uses increments of 5MHz of spectrum, with each slice divided into 10ms frames containing fifteen time slots (1500 per second). The time slots are allocated in fixed percentage for downlink and uplink. TD-CDMA is used to multiplex streams from or to multiple transceivers. Unlike W-CDMA, it does not need separate frequency bands for up- and downstream, allowing deployment in tight frequency bands.

TD-CDMA is a part of IMT-2000 as IMT CDMA TDD.

TD-SCDMA (UTRA-TDD 1.28 Mcps Low Chip Rate)

TD-SCDMA uses 1.6MHz slices of spectrum, allowing deployment in even tighter frequency bands than TD-CDMA. However, the main incentive for development of this Chinese-developed standard was avoiding or reducing the license fees that have to be paid to non-Chinese patent owners. Unlike the other air interfaces, TD-SCDMA was not part of UMTS from the beginning but has been added in Release 4 of the specification.

Like TD-CDMA, it is known as IMT CDMA TDD within IMT-2000.

Core network

With Mobile Application Part, UMTS uses the same core network standard as GSM/EDGE. This allows a simple migration for exiting GSM operators. However, the migration path to UMTS is still costly: while much of the core infrastructure is shared with GSM, the cost of obtaining new spectrum licenses and overlaying UMTS at existing towers is high.

The CN can be connected to various backbone networks like the Internet, ISDN. UMTS (and GERAN) include the three lowest layers of OSI model. The network layer (OSI 3) includes the Radio Resource Management protocol (RRM) that manages the bearer channels between the mobile terminals and the fixed network, including the handovers.

Spectrum allocation

Over 130 licenses have already been awarded to operators worldwide (as of December 2004), specifying W-CDMA radio access technology that builds on GSM. In Europe, the license process occurred at the tail end of the technology bubble, and the auction mechanisms for allocation set up in some countries resulted in some extremely high prices being paid for the original 2100 MHz licenses, notably in the UK and Germany. In Germany, bidders paid a total €50.8 billion for six licenses, two of which were subsequently abandoned and written off by their purchasers (Mobilcom and the Sonera/Telefonica consortium). It has been suggested that these huge license fees have the character of a very large tax paid on future income expected many years down the road. In any event, the high prices paid put some European telecom operators close to bankruptcy (most notably KPN). Over the last few years some operators have written off some or all of the license costs. More recently, a carrier in Finland has begun using 900 MHz UMTS in a shared arrangement with its surrounding 2G GSM base stations, a trend that is expected to expand over Europe in the next 1–3 years.

The 2100 MHz UMTS spectrum allocated in Europe is already used in North America. The 1900 MHz range is used for 2G (PCS) services, and 2100 MHz range is used for satellite communications. Regulators have, however, freed up some of the 2100 MHz range for 3G services, together with the 1700 MHz for the uplink. UMTS operators in North America who want to implement a European style 2100/1900 MHz system will have to share spectrum with existing 2G services in the 1900 MHz band.

AT&T Wireless launched UMTS services in the United States by the end of 2004 strictly using the existing 1900 MHz spectrum allocated for 2G PCS services. Cingular acquired AT&T Wireless in 2004 and has since then launched UMTS in select US cities. Cingular renamed itself AT&T and is rolling out some cities with a UMTS network at 850 MHz to enhance its existing UMTS network at 1900 MHz and now offers subscribers a number of UMTS 850/1900 phones.

T-Mobile's rollout of UMTS in the US will focus on the 2100/1700 MHz bands, whereas UMTS coverage in Canada is being provided on the 850 MHz band of the Rogers Wireless network. In 2008, Australian telco Telstra replaced its existing CDMA network with a national 3G network, branded as NextG, operating in the 850 MHz band. Telstra currently provides UMTS service on this network, and also on the 2100 MHz UMTS network, through a co-ownership of the owning and administrating company 3GIS. This company is also co-owned by Hutchison 3G Australia, and this is the primary network used by their customers. Optus is currently rolling out a 3G network operating on the 2100 MHz band in cities and most large towns, and the 900 MHz band in regional areas. Vodafone is also building a 3G network using the 900 MHz band. The 850 MHz and 900 MHz bands provide greater coverage compared to equivalent 1700/1900/2100 MHz networks, and are best suited to regional areas where greater distances separate subscriber and base station.

Carriers in South America are now also rolling out 850 MHz networks.

Interoperability and global roaming

UMTS phones (and data cards) are highly portable—they have been designed to roam easily onto other UMTS networks (assuming your provider has a roaming agreement). In addition, almost all UMTS phones are UMTS/GSM dual-mode devices, so if a UMTS phone travels outside of UMTS coverage du

Sabtu, 23 Mei 2009

BlackBerry Storm

The BlackBerry Storm is a touchscreen smartphone developed by Research In Motion (RIM).

Contents

[hide]


[edit] Introduction

The BlackBerry Storm is the second newest addition to the BlackBerry family. It is part of the BlackBerry 9500 series of phones.[4] It is RIM's first touchscreen device and the first device without a physical keyboard. It features a touchscreen which reacts physically like a button via SurePress, a Research In Motion patented technology of providing haptic feedback. It is available through Vodafone (SFR) in the UK, France, Italy, Ireland, Australia, and India; [5] Verizon Wireless in the United States; Telus and Bell in Canada; Iusacell in Mexico.[6] and on bMobile and Digicel in Barbados and other parts of the Caribbean.[7]

The BlackBerry Storm is a world-phone, featuring CDMA with EV-DO Rev. A data, UMTS with HSDPA, and quad-band GSM with EDGE data access speed. However, the BlackBerry Storm only has European, Oceania, Asia and Brazil UMTS and HSDPA frequency bands. Therefore if the BlackBerry Storm is used with GSM wireless carriers in North America, the BlackBerry Storm will only be able to access wireless internet at EDGE data speed maximum. This is because GSM carriers in North America, namely AT&T, T-Mobile, Rogers and Fido do not operate on the same frequency bands for 3G as the rest of the world. If BlackBerry Storm is used in Europe, Africa, Asia, Oceania or Brazil, HSDPA wireless data speed can be achieved, provided that the local GSM networks support it.[8] The phone will use the primary network technology of its intended carrier (Verizon) when traveling domestically in the US, and rely upon the GSM/UMTS/HSDPA networks of Vodafone mainly when traveling abroad. There are currently no unlocked and unbranded versions available for the GSM Blackberry Storm however unlocking the phone will allow it to be used with any GSM service provider. [9]

It is intended to be a direct competitor to Apple iPhone 3G, the T-Mobile G1 by HTC[10] and the HTC Touch family.

[edit] Hardware

  • Touchscreen: The Storm uses a "SurePress" glass capacitive touchscreen which provides haptic feedback - clicks physically depress the screen into the phone. The screen's settings can be adjusted so that double tapping can be employed as an alternate method to select and navigate the phone.
  • Display: 3.25 in (8.3 cm) TFT-LCD flat touch-sensitive scratch-resistant screen with 360 X 480 pixel resolution and able to display 65,536 colours. The touchscreen eliminates the need for use of a stylus as it uses a capacitive touchscreen. The touchscreen also provides haptic feedback when it is used.
  • CPU: The Storm utilizes the MSM7600 from Qualcomm[11] a dual core CPU with ARM11 400 MHz and ARM9 274 MHz.
  • Battery: The Storm features a user-replaceable, rechargeable DX-1 Li-ion battery stated to be capable of providing up to 5.5 hours of GSM talk time, 6 hours of CDMA talk time, or 360 hours of standby.
  • Camera: The device features a built-in 3.2 megapixel camera located on back which features a flash, autofocus, and has video recording capabilities with a maximum resolution of 480 x 352 pixels.
  • Memory: The device features 1GB of onboard memory and an expandable memory slot support for a microSD card of up to an additional 16GB. Verizon Wireless includes a preinstalled 8GB microSD card onboard.

[edit] Critical reception

The Storm was met with generally mixed reviews, some focusing on serious usability problems in particular. Many gadget reviewers, including Bonnie Cha of CNET[12], Joshua Topolsky of Engadget[13] and Sascha Segan from PC Magazine[14] noted the Storm's much-improved web browser and impressive call quality, while also deeming the SurePress touchscreen difficult to learn and a hindrance to fast typing. Several reviews also noted that the web browser was still unable to handle complex webpages correctly, saying that the iPhone's MobileSafari is still a better mobile browser. A number of reviewers also ran into multiple software glitches during their testing, such as lockups, sluggish performance and refusal to switch orientation[15]. The lack of Wi-Fi support also irked a few reviewers, but as noted by Jeff Rauschert of MLive, Verizon's wireless network somewhat makes up for this[16]. David Haskin of the Reseller News noted that BlackBerry's major business features, such as enterprise e-mail integration and Microsoft Office document editing capabilities were on par with BlackBerry's previous offerings, noting that these features would likely make the Storm more popular with the business crowd[17]. Also noted by a number of reviewers was the fact that a number if not most of the problems (lag, accelerometer accuracy, etc.) could potentially be fixed by future software updates.

[edit] Software Update

Ongoing firmware updates have been released since 5 December 2008 that addressed most of these issues; updates can be downloaded online or OTA and can be installed by the user. The most current (official) software to date is:

Device ↓ Carrier ↓ Package Version ↓ Applications ↓ Software Platform ↓
BlackBerry Storm 9530 Verizon Wireless 4.7.0.109 4.7.0.75 4.0.0.136
BlackBerry Storm 9530 Telus Mobility 4.7.0.172 4.7.0.122 4.0.0.153
BlackBerry Storm 9530 Bell Mobility 4.7.0.172 4.7.0.122 4.0.0.153
BlackBerry Storm 9500 Vodafone 4.7.0.195 4.7.0.141 4.0.0.174
BlackBerry Storm 9500 Si.mobil 4.7.0.113 4.7.0.113 4.0.0.144

As of May 20, 2009, the latest unofficial software for the Blackberry Storm (9530 only) is 4.7.0.148. [18]

[edit] SIM Lock

The Blackberry Storm by default is SIM locked, and can be subsequently unlocked on both the Vodafone & Verizon Wireless Storm editions to use on any GSM network if the code is obtained from the respective provider. The Verizon Wireless Blackberry Storm is not fully compatible with AT&T Mobility's 3G UMTS/HSDPA network as it uses different radio signals, but will still work over the slower EDGE network.

[edit] References

  1. ^ a b c d e f g h i Research In Motion. "BlackBerry Storm Specs". http://www.blackberry.com/blackberrystorm/specifications.shtml. Retrieved on 2008-10-12.
  2. ^ http://www.phonewreck.com/wiki/index.php?title=BlackBerry_Storm
  3. ^ The Boy Genius (2008-06-10). "BlackBerry Thunder: after the storm". The Boy Genius Report. http://www.boygeniusreport.com/2008/06/10/blackberry-thunder-after-the-storm. Retrieved on 2008-08-10. /
  4. ^ The Boy Genius (2008-08-08). "BlackBerry Thunder gets 9530 model designation on Verizon, October 13th release date?". The Boy Genius Report. http://www.boygeniusreport.com/2008/08/08/blackberry-thunder-gets-9530-model-designation-on-verizon/. Retrieved on 2008-08-10.
  5. ^ Vodafone Australia. "BlackBerry Storm Pre-register Vodafone Australia". http://www.vodafone.com.au/personal/blackberrystorm/index.htm?pid=vca:home:1-4. Retrieved on 2008-12-10.
  6. ^ The Boy Genius (2008-05-13). "BlackBerry Thunder, the touchscreen BlackBerry we've all been waiting for". The Boy Genius Report. http://www.boygeniusreport.com/2008/05/13/blackberry-thunder-the-touchscreen-blackberry-weve-all-been-waiting-for/. Retrieved on 2008-08-10.
  7. ^ Deborah Hoyte (2009-05-01). "Research In Motion introduces the Blackberry Storm to Barbados". Barbados Advocate. http://www.barbadosadvocate.com/newsitem.asp?more=business&NewsID=3368. Retrieved on 2009-05-01. "Yesterday officials from Research In Motion (RIM) launched the BlackBerry Storm smartphone in Barbados at the Hilton Hotel, Needham’s Point. The stylish BlackBerry Storm is expected to be available from May by both of the major cellphone providers in Barbados. “We are very pleased to introduce the BlackBerry Storm in this country”, commented Mark Guibert, Vice President of Corporate Marketing at RIM."
  8. ^ Arar, Yardena (2008-10-13). "BlackBerry Storm: RIM's Un-iPhone". The Washington Post. http://www.washingtonpost.com/wp-dyn/content/article/2008/10/08/AR2008100800105.html. Retrieved on 2008-10-19.
  9. ^ "BlackBerry Storm Info". http://www.blackberry9500.us.
  10. ^ Hamilton, Anita (2008-10-07). "BlackBerry's Storm Aims to Blow the iPhone Away". Time. http://www.time.com/time/business/article/0,8599,1847791,00.html. Retrieved on 2008-10-19.
  11. ^ http://www.phonewreck.com/wiki/index.php?title=BlackBerry_Storm
  12. ^ "RIM BlackBerry Storm (Verizon Wireless) Smartphone reviews - CNET Reviews". http://reviews.cnet.com/smartphones/rim-blackberry-storm-verizon/4505-6452_7-33311850.html. Retrieved on 2008-11-22.
  13. ^ "BlackBerry Storm reviews - Engadget". http://www.engadget.com/2008/11/19/blackberry-storm-review/l. Retrieved on 2008-11-23.
  14. ^ "T-Mobile's G1 vs. the Smartphone Heavyweights - RIM BlackBerry Storm 9530 - At A Glance - Reviews by PC Magazine". http://www.pcmag.com/article2/0,2817,2331977,00.asp. Retrieved on 2008-11-23.
  15. ^ "BlackBerry Storm Review (Verdict: Not Quite a Perfect Storm)". http://gizmodo.com/5093715/blackberry-storm-review-verdict-not-quite-a-perfect-storm. Retrieved on 2008-11-22.
  16. ^ "BlackBerry Storm review: Inelegant touch screen doesn't live up to the hype - The Flint Journal Online News - Michigan Newspaper - MLive.com". http://www.mlive.com/flintjournal/index.ssf/2008/11/blackberry_storm.html. Retrieved on 2008-11-23.
  17. ^ "BlackBerry Storm: not just an iPhone wannabe". http://reseller.co.nz/reseller.nsf/review/7F78D2F9888806D4CC25750A006EE311. Retrieved on 2008-11-24.
  18. ^ http://crackberry.com/leaked-4-7-0-148-9530

[edit] External links

Jumat, 16 Januari 2009

Internet Protocol Suite

The Internet Protocol Suite (commonly known as TCP/IP) is the set of communications protocols used for the Internet and other similar networks. It is named from two of the most important protocols in it: the Transmission Control Protocol (TCP) and the Internet ProtocolInternet and LANs (Local Area Networks), which emerged in the mid- to late-1980s, together with the invention of the World Wide Web by Tim Berners-Lee in 1989 (and which exploded with the availability of the first popular web browser: Mosaic). (IP), which were the first two networking protocols defined in this standard. Today's IP networking represents a synthesis of several developments that began to evolve in the 1960s and 1970s, namely the

The Internet Protocol Suite, like many protocol suites, may be viewed as a set of layers. Each layer solves a set of problems involving the transmission of data, and provides a well-defined service to the upper layer protocols based on using services from some lower layers. Upper layers are logically closer to the user and deal with more abstract data, relying on lower layer protocols to translate data into forms that can eventually be physically transmitted.

The TCP/IP model consists of four layers (RFC 1122).[1][2] From lowest to highest, these are the Link Layer, the Internet Layer, the Transport Layer, and the Application Layer.

Contents

1 History

History

The Internet Protocol Suite resulted from work done by Defense Advanced Research Projects Agency (DARPA) in the early 1970s. After building the pioneering ARPANET in 1969, DARPA started work on a number of other data transmission technologies. In 1972, Robert E. Kahn was hired at the DARPA Information Processing Technology Office, where he worked on both satellite packet networks and ground-based radio packet networks, and recognized the value of being able to communicate across them. In the spring of 1973, Vinton Cerf, the developer of the existing ARPANET Network Control Program (NCP) protocol, joined Kahn to work on open-architecture interconnection models with the goal of designing the next protocol generation for the ARPANET.

By the summer of 1973, Kahn and Cerf had worked out a fundamental reformulation, where the differences between network protocols were hidden by using a common internetwork protocol, and, instead of the network being responsible for reliability, as in the ARPANET, the hosts became responsible. Cerf credits Hubert Zimmerman and Louis Pouzin, designer of the CYCLADES network, with important influences on this design.

With the role of the network reduced to the bare minimum, it became possible to join almost any networks together, no matter what their characteristics were, thereby solving Kahn's initial problem. One popular saying has it that TCP/IP, the eventual product of Cerf and Kahn's work, will run over "two tin cans and a string." There is even an implementation designed to run using homing pigeons, IP over Avian Carriers, documented in RFC 1149. [3] [4].

A computer called a router (a name changed from gateway to avoid confusion with other types of gateways) is provided with an interface to each network, and forwards packets back and forth between them. Requirements for routers are defined in (Request for Comments 1812). [5]

The idea was worked out in more detailed form by Cerf's networking research group at Stanford in the 1973–74 period, resulting in the first TCP specification (Request for Comments 675) [6] (The early networking work at Xerox PARC, which produced the PARC Universal Packet protocol suite, much of which existed around the same period of time (i.e. contemporaneous), was also a significant technical influence; people moved between the two).

DARPA then contracted with BBN Technologies, Stanford University, and the University College London to develop operational versions of the protocol on different hardware platforms. Four versions were developed: TCP v1, TCP v2, a split into TCP v3 and IP v3 in the spring of 1978, and then stability with TCP/IP v4 — the standard protocol still in use on the Internet today.

In 1975, a two-network TCP/IP communications test was performed between Stanford and University College London (UCL). In November, 1977, a three-network TCP/IP test was conducted between the U.S., UK, and Norway. Between 1978 and 1983, several other TCP/IP prototypes were developed at multiple research centers. A full switchover to TCP/IP on the ARPANET took place January 1, 1983.[7]

In March 1982, the US Department of Defense made TCP/IP the standard for all military computer networking.[8] In 1985, the Internet Architecture Board held a three day workshop on TCP/IP for the computer industry, attended by 250 vendor representatives, helping popularize the protocol and leading to its increasing commercial use.

On November 9, 2005 Kahn and Cerf were presented with the Presidential Medal of Freedom for their contribution to American culture.

Layers in the Internet Protocol Suite

The concept of layers

The TCP/IP suite uses encapsulation to provide abstraction of protocols and services. Such encapsulation usually is aligned with the division of the protocol suite into layers of general functionality. In general, an application (the highest level of the model) uses a set of protocols to send its data down the layers, being further encapsulated at each level.

This may be illustrated by an exmple network scenario, in which two Internet host computers communicate across local network boundaries constituted by their internetworking gateways (routers).

TCP/IP stack operating on two hosts connected via two routers and the corresponding layers used at each hop
Encapsulation of application data descending through the protocol stack.

The functional groups of protocols and methods are the Application Layer, the Transport Layer, the Internet Layer, and the Link Layer (RFC 1122). It should be noted that this model was not intended to be a rigid reference model into which new protocols have to fit in order to be accepted as a standard.

The following table provides some examples of the protocols grouped in their respective layers.

Application DNS, TFTP, TLS/SSL, FTP, Gopher, HTTP, IMAP, IRC, NNTP, POP3, SIP, SMTP,SMPP, SNMP, SSH, Telnet, Echo, RTP, PNRP, rlogin, ENRP
Routing protocols like BGP and RIP which run over TCP/UDP, may also be considered part of the Internet Layer.
Transport TCP, UDP, DCCP, SCTP, IL, RUDP, RSVP
Internet IP (IPv4, IPv6) ICMP, IGMP, and ICMPv6
OSPF for IPv4 was initially considered IP layer protocol since it runs per IP-subnet, but has been placed on the Link since RFC 2740.
Link ARP, RARP, OSPF (IPv4/IPv6), IS-IS, NDP

Layer names and number of layers in the literature

The following table shows the layer names and the number of layers in the TCP/IP model as presented in widespread university course textbooks on computer networking used today.


Forouzan [9] Comer[10], Kozierok[11] Stallings[12] Tanenbaum[13] Kurose[14], RFC 1122 Cisco Academy[15]

Five layers Five layers Five layers Four layers Four layers Four layers
L5 Application Application Application Application Application Application
L4 Transport Transport Host-to-host or transport Transport Transport Transport
L3 Network Internet Internet Internet Internet Internetwork
L2 Data link Data link (Network interface) Network access Host-to-network Link Network interface
L1 Physical (Hardware) Physical

These textbooks are secondary sources that may contravene the intent of RFC 1122 and other IETF primary sources[16].

Different authors have interpreted the RFCs differently regarding whether the Link Layerphysical layer issues or a "hardware layer" is assumed below the link layer. Some authors have tried to use other names for the link layer, such as Network interface layer, in effort to avoid confusion with the Data link layer of the seven-layer OSI model. Others have attempted to map the Internet Protocol model onto the seven-layer OSI Model. The mapping often results in a five-layer TCP/IP model, wherein the Link Layer is split into a Data Link Layer on top of a Physical Layer. Especially in literature with a bottom-up approach to computer networking, where physical layer issues are emphasized, an evolution towards a five-layer Internet model can be observed out of pedagogical reasons. (and the four-layer TCP/IP model) covers

The Internet Layer is usually directly mapped to the OSI's Network Layer. At the top of the hierarchy, the Transport Layer is always mapped directly into OSI Layer 4 of the same name. OSIs Application Layer, Presentation Layer, and Session Layer are collapsed into TCP/IP's Application Layer. As a result, these efforts result in either a four- or five-layer scheme with a variety of layer names. This has caused considerable confusion in the application of these models. Other authors dispense with rigid pedagogy[17] focusing instead on functionality and behavior.

The Internet protocol stack has never been altered by the Internet Engineering Task Force (IETF) from the four layers defined in RFC 1122. The IETF makes no effort to follow the seven-layer OSI model and does not refer to it in standards-track protocol specifications and other architectural documents. The IETF has repeatedly stated that Internet protocol and architecture development is not intended to be OSI-compliant.

RFC 3439, addressing Internet architecture, contains a section entitled: "Layering Considered Harmful".[16]

[edit] Implementations

Today, most operating systems include and install a TCP/IP stack by default. For most users, there is no need to look for implementations. TCP/IP is included in all commercial UnixMac OS X, and all free-software Unix-like systems such as Linux distributions and BSDMicrosoft Windows operating systems. systems, systems, as well as all

Unique implementations include Lightweight TCP/IP, an open source stack designed for embedded systems and KA9Q NOS, a stack and associated protocols for amateur packet radiopersonal computers connected via serial lines. systems and

See also

References

  1. ^ RFC 1122, Requirements for Internet Hosts -- Communication Layers, R. Braden (ed.), October 1989
  2. ^ RFC 1123, Requirements for Internet Hosts -- Application and Support, R. Braden (ed.), October 1989
  3. ^ D. Weitzmann (April 1990). "[http:www.isi.edu/in-notes/rfc1149.txt A Standard for the Transmission of IP Datagrams on Avian Carriers]". Internet Engineering Task Force. Retrieved on 2007-11-20.
  4. ^ Bergen Linux User Group (April 2001). "The informal report from the RFC 1149 event".
  5. ^ F. Baker (June 1995). "Requirements for IP Routers".
  6. ^ V.Cerf et al (December 1974). "Specification of Internet Transmission Control Protocol".
  7. ^ Internet History
  8. ^ Ronda Hauben. "From the ARPANET to the Internet". TCP Digest (UUCP). Retrieved on 2007-07-05.
  9. ^ Behrouz A. Forouzan, Data Communications and Networking
  10. ^ Douglas E. Comer, Internetworking with TCP/IP: Principles, Protocols and Architecture, Pearson Prentice Hall 2005, ISBN 0131876716
  11. ^ Charles M. Kozierok, "The TCP/IP Guide", No Starch Press 2005
  12. ^ William Stallings, Data and Computer Communications, Prentice Hall 2006, ISBN 0132433109
  13. ^ Andrew S. Tanenbaum, Computer Networks, Prentice Hall 2002, ISBN 0130661023
  14. ^ James F. Kurose, Keith W. Ross, Computer Networking: A Top-Down Approach, 2007, ISBN 0321497708
  15. ^ Mark Dye, Mark A. Dye, Wendell, Network Fundamentals: CCNA Exploration Companion Guide, 2007, ISBN 1587132087
  16. ^ a b R. Bush; D. Meyer (December 2002), Some Internet Architectural Guidelines and Philosophy, Internet Engineering Task Force, http://www.isi.edu/in-notes/rfc3439.txt, retrieved on 20 November 2007
  17. ^ IP Fundamentals: What Everyone Needs to Know About Addressing and Routing, T. Maufer, Computer Networks, Prentice Hall 1999, ISBN 0130661023

Further reading

External links