Wednesday, September 16, 2009



GraphicRiver?
http://graphicriver.net
GraphicRiver is an Envato Marketplace. At GraphicRiver you can buy and sell royalty free layered Adobe Photoshop Files, Vector Graphics, Icon Sets and Add-ons for Adobe Photoshop and Illustrator. It's like having an entire graphics department at your fingertips!

Files are priced from just one dollar, based on the complexity, quality and use of the file. Anyone is free to sign up for an account and begin trading or purchasing files.

Other Envato Marketplaces include FlashDen, ThemeForest, VideoHive and AudioJungle.
The Team Our core staff are:

* Vahid - Chief
* Cyan - Marketplace Manager
* Jun - Money Man
* John - Lead Programming & Vocals
* Clinton - Bass Programming & Backup Vocals
* Erin - Keyboards & Backup Vocals
* James - Drum Programming
* Stuart - Band Stylist
* Collis - Mr Pixel
* Rodney - Radial Gradient Correspondent
* scottwills - AudioJungle Site Manager
* LanceSnider - FlashDen Site Manager
* AmandaLinder - GraphicRiver Site Manager
* JeffreyWay - ThemeForest Site Manager
* MarkBrodhuber - VideoHive Site Manager

Additionally we have some great members who review and feature items as well as provide support for files, monitor the forums and are generally awesome, they are:

* Aaron_Osteraas
* ADG3studios
* adrianpelletier
* AmandaLinder
* ArikB
* baf2681
* bgm
* envato
* flashjunkie
* JeffreyWay
* JimmyP
* joelfalconer
* kailoon
* LanceSnider
* loziosecchi
* MarkBrodhuber
* RimV
* SaafiDesign
* scottwills
* Slats
* Solidbeats
* xmdsys

Contact & Business Details

FlashDen Pty Ltd trading as Envato
ABN 11 119 159 741
PO Box 21177, Little Lonsdale Street, VIC 8011, Australia

If you'd like to get in touch with us, use one of these methods:

General business enquiries: please use this form
All other enquiries: use our support system

BCC Circulation

BCC 7 th Scholarship circulation is published. Please contact http://www.bcc.net.bd

Saturday, August 1, 2009

Happy Friendship day

A good friend is like a computer. I 'enter' in your life, 'save' you in my heart, 'format' your problems, 'shift' you to opportunities & never 'delete' you from my memory!

Wednesday, July 22, 2009


Hypertext Transfer Protocol

Hypertext Transfer Protocol (HTTP) is an application-level protocol for distributed, collaborative, hypermedia information systems.[1] Its use for retrieving inter-linked resources led to the establishment of the World Wide Web.

HTTP development was coordinated by the World Wide Web Consortium and the Internet Engineering Task Force (IETF), culminating in the publication of a series of Requests for Comments (RFCs), most notably RFC 2616 (June 1999), which defines HTTP/1.1, the version of HTTP in common use.

Support for pre-standard HTTP/1.1 based on the then developing RFC 2068 was rapidly adopted by the major browser developers in early 1996. By March 1996, pre-standard HTTP/1.1 was supported in Netscape 2.0, Netscape Navigator Gold 2.01, Mosaic 2.7, Lynx 2.5, and in Internet Explorer 3.0. End user adoption of the new browsers was rapid. In March 1996, one web hosting company reported that over 40% of browsers in use on the Internet were HTTP 1.1 compliant. That same web hosting company reported that by June 1996, 65% of all browsers accessing their servers were HTTP 1.1 Compliant.[2] The HTTP 1.1 standard as defined in RFC 2068 was officially released in January 1997. Improvements and updates to the The HTTP/1.1 standard were released under RFC 2616 in June 1999.

HTTP is a request/response standard of a client and a server. A client is the end-user, the server is the web site. The client making a HTTP request—using a web browser, spider, or other end-user tool—is referred to as the user agent. The responding server—which stores or creates resources such as HTML files and images—is called the origin server. In between the user agent and origin server may be several intermediaries, such as proxies, gateways, and tunnels. HTTP is not constrained to using TCP/IP and its supporting layers, although this is its most popular application on the Internet. Indeed HTTP can be "implemented on top of any other protocol on the Internet, or on other networks." HTTP only presumes a reliable transport; any protocol that provides such guarantees can be used."[3]

Typically, an HTTP client initiates a request. It establishes a Transmission Control Protocol (TCP) connection to a particular port on a host (port 80 by default; see List of TCP and UDP port numbers). An HTTP server listening on that port waits for the client to send a request message. Upon receiving the request, the server sends back a status line, such as "HTTP/1.1 200 OK", and a message of its own, the body of which is perhaps the requested resource, an error message, or some other information.

Resources to be accessed by HTTP are identified using Uniform Resource Identifiers (URIs)—or, more specifically, Uniform Resource Locators (URLs)—using the http: or https URI schemes.

Read More

SOAP



SOAP, originally defined as Simple Object Access Protocol, is a protocol specification for exchanging structured information in the implementation of Web Services in computer networks. It relies on Extensible Markup Language (XML) as its message format, and usually relies on other Application Layer protocols (most notably Remote Procedure Call (RPC) and HTTP) for message negotiation and transmission. SOAP can form the foundation layer of a web services protocol stack, providing a basic messaging framework upon which web services can be built.

As a layman's example of how SOAP procedures can be used, a SOAP message could be sent to a web service enabled web site (for example, a house price database) with the parameters needed for a search. The site would then return an XML-formatted document with the resulting data (prices, location, features, etc). Because the data is returned in a standardized machine-parseable format, it could then be integrated directly into a third-party site.

The SOAP architecture consists of several layers of specifications for message format, message exchange patterns (MEP), underlying transport protocol bindings, message processing models, and protocol extensibility. SOAP is the successor of XML-RPC, though it borrows its transport and interaction neutrality and the envelope/header/body from elsewhere (probably from WDDX).

Read More

cPanel


cPanel is a unix based web hosting control panel that provides a graphical interface and automation tools designed to simplify the process of hosting a web site. cPanel utilized a 3 tier structure that provides functionality for administrators, resellers, and end-user website owners to control the various aspects website and server administration through a standard web browser.

In addition to the GUI interface cPanel also has command line and API based access that allows third party software vendors, web hosting organizations, and developers to automate standard system administration processes.

cPanel is designed to function either as a dedicated server or virtual private server and it supports CentOS, Red Hat Linux, and FreeBSD.

Application based support includes Apache, PHP, mySQL, Postgres, Perl, Python, and BIND. Email based support includes POP3, IMAP, SMTP services. cPanel is commonly accessed on port 2082.




History

cPanel was originally designed as the control panel for high Speed Hosting[citation needed], a now defunct web hosting company. The original author of cPanel, J. Nicholas Koston, had a stake in Speed Hosting. Web King quickly began using cPanel after their merger with Speed Hosting. After Speed Hosting and Webking merged, the new company moved their servers to Virtual Development Inc. (VDI), a now-defunct hosting facility. Following an agreement between J. Nick Koston and VDI, cPanel was only available to customers hosted directly at VDI. At the time there was little competition in the control panel market with the main choices being VDI and Alabanza[1]. cPanel 3 was released in 1999; its main features over cpanel 2 were an automatic upgrade and the Web Host Manager.

cPanel 3 tended to be buggy and did not have a good user interface. The interface improved when Carlos Rego of WizardsHosting made what became the default theme of cPanel. Eventually due to internal problems between VDI and J. Nick Koston, cPanel split into two separate programs called cPanel and WebPanel. WebPanel was the version run by VDI. Without the lead programmer, VDI was not able to continue any work on cPanel and eventually stopped supporting it completely. J. Nick Koston kept working on cPanel while also working at BurstNET. Eventually Nick left BurstNET on good terms to focus fully on cPanel. cPanel has been updated and improved over the years. It is now a stable and reliable control panel.

[edit] Add-Ons

To the client, cPanel provides front-ends for a number of common operations, including the management of PGP keys, crontab tasks, mail and FTP accounts, and mailing lists.

Several add-ons exist for an additional fee, the most notable being Fantastico, a bundle of scripts which automate the installation of, but not the update of (see article[1]), web applications such as WordPress, SMF, phpBB, Drupal, Joomla!, TikiWiki CMS/Groupware, Moodle and over 50 others.

cPanel manages some software packages separately from the underlying operating system, applying upgrades to Apache, PHP, MySQL, and related software packages automatically. This ensures that these packages are kept up-to-date and compatible with cPanel, but makes it more difficult to install newer versions of these packages.

[edit] WHM (Web Host Manager)

WebHost Manager (WHM) is a web-based tool used by server administrators and resellers to manage hosting accounts on a web server. WHM listens on ports 2086 and 2087 by default.

As well as being accessible by the root admin, WHM is also accessible to users with reseller privileges. Reseller users of cPanel have a smaller set of features than the root user, generally limited by the server administrator, to features which they determine will affect their customers' accounts rather than the server as a whole. From WHM, the server administrator can perform maintenance operations such as compile Apache and upgrade RPMs installed on the system.

File Transfer Protocol

Download FTP downloader:
FilZilla:
FilZilla
SmartFTP
SmartFtp
Core Ftp
CoreFtp

File Transfer Protocol (FTP) is a standard network protocol used to exchange and manipulate files over an Internet Protocol computer network, such as the Internet. FTP is built on a client-server architecture and utilizes separate control and data connections between the client and server applications. Client applications were originally interactive command-line tools with a standardized command syntax, but graphical user interfaces have been developed for all desktop operating systems in use today. FTP is also often used as an application component to automatically transfer files for program internal functions. FTP can be used with user-based password authentication or with anonymous user access.


Connection methods

FTP runs over the Transmission Control Protocol (TCP).[1] Usually FTP servers listen on the well-known port number 21 (IANA-reserved) for incoming connections from clients. A connection to this port from the FTP client forms the control stream on which commands are passed to the FTP server and responses are collected. FTP uses out-of-band control; it opens dedicated data connections on other port numbers. The parameters for the data streams depend on the specifically requested transport mode. Data connections usually use port number 20.

In active mode, the FTP client opens a dynamic port, sends the FTP server the dynamic port number on which it is listening over the control stream and waits for a connection from the FTP server. When the FTP server initiates the data connection to the FTP client it binds the source port to port 20 on the FTP server.

In order to use active mode, the client sends a PORT command, with the IP and port as argument. The format for the IP and port is "h1,h2,h3,h4,p1,p2". Each field is a decimal representation of 8 bits of the host IP, followed by the chosen data port. For example, a client with an IP of 192.168.0.1, listening on port 49154 for the data connection will send the command "PORT 192,168,0,1,192,2". The port fields should be interpreted as p1×256 + p2 = port, or, in this example, 192×256 + 2 = 49154.

In passive mode, the FTP server opens a dynamic port, sends the FTP client the server's IP address to connect to and the port on which it is listening (a 16-bit value broken into a high and low byte, as explained above) over the control stream and waits for a connection from the FTP client. In this case, the FTP client binds the source port of the connection to a dynamic port.

To use passive mode, the client sends the PASV command to which the server would reply with something similar to "227 Entering Passive Mode (127,0,0,1,192,52)". The syntax of the IP address and port are the same as for the argument to the PORT command.

In extended passive mode, the FTP server operates exactly the same as passive mode, however it only transmits the port number (not broken into high and low bytes) and the client is to assume that it connects to the same IP address that was originally connected to. Extended passive mode was added by RFC 2428 in September 1998.

While data is being transferred via the data stream, the control stream sits idle. This can cause problems with large data transfers through firewalls which time out sessions after lengthy periods of idleness. While the file may well be successfully transferred, the control session can be disconnected by the firewall, causing an error to be generated.

The FTP protocol supports resuming of interrupted downloads using the REST command. The client passes the number of bytes it has already received as argument to the REST command and restarts the transfer. In some commandline clients for example, there is an often-ignored but valuable command, "reget" (meaning "get again"), that will cause an interrupted "get" command to be continued, hopefully to completion, after a communications interruption.

Resuming uploads is not as easy. Although the FTP protocol supports the APPE command to append data to a file on the server, the client does not know the exact position at which a transfer got interrupted. It has to obtain the size of the file some other way, for example over a directory listing or using the SIZE command.

In ASCII mode (see below), resuming transfers can be troublesome if client and server use different end of line characters.

[edit] Security problems

The original FTP specification is an inherently unsecure method of transferring files because there is no method specified for transferring data in an encrypted fashion. This means that under most network configurations, user names, passwords, FTP commands and transferred files can be captured by anyone on the same network using a packet sniffer. This is a problem common to many Internet protocol specifications written prior to the creation of SSL, such as HTTP, SMTP and Telnet. The common solution to this problem is to use either SFTP (SSH File Transfer Protocol), or FTPS (FTP over SSL), which adds SSL or TLS encryption to FTP as specified in RFC 4217.

[edit] FTP return codes
Main article: List of FTP server return codes

FTP server return codes indicate their status by the digits within them. A brief explanation of various digits' meanings are given below:

* 1xx: Positive Preliminary reply. The action requested is being initiated but there will be another reply before it begins.
* 2xx: Positive Completion reply. The action requested has been completed. The client may now issue a new command.
* 3xx: Positive Intermediate reply. The command was successful, but a further command is required before the server can act upon the request.
* 4xx: Transient Negative Completion reply. The command was not successful, but the client is free to try the command again as the failure is only temporary.
* 5xx: Permanent Negative Completion reply. The command was not successful and the client should not attempt to repeat it again.
* x0x: The failure was due to a syntax error.
* x1x: This response is a reply to a request for information.
* x2x: This response is a reply relating to connection information.
* x3x: This response is a reply relating to accounting and authorization.
* x4x: Unspecified as yet
* x5x: These responses indicate the status of the Server file system vis-a-vis the requested transfer or other file system action.

[edit] Anonymous FTP

A host that provides an FTP service may additionally provide anonymous FTP access. Users typically login to the service with an 'anonymous' account when prompted for user name. Although users are commonly asked to send their email address in lieu of a password, little to no verification is actually performed on the supplied data.

As modern FTP clients typically hide the anonymous login process from the user, the ftp client will supply dummy data as the password (since the user's email address may not be known to the application). For example, the following ftp user agents specify the listed passwords for anonymous logins:

* Mozilla Firefox (3.0.7) — mozilla@example.com
* KDE Konqueror (3.5) — anonymous@
* wget (1.10.2) — -wget@
* lftp (3.4.4) — lftp@
* Opera (9.6.2) — opera@

The Gopher protocol has been suggested as an alternative to anonymous FTP, as well as File Service Protocol.[citation needed]

[edit] Transfer parameters

According to the FTP standard RFC959, the transfer of data is determined by four main parameters:

* the data structure: stream-oriented, record-oriented or page-oriented
* the data type: the textual types of ASCII, EBCDIC, with subtypes for different carriage control disciplines; the binary types of byte-oriented, or arbitrary length word-oriented
* the vertical format control: for the textual types of ASCII and EBCDIC, whether vertical format control is specified using
* the transfer mode: stream-oriented transfer, uncompressed block-oriented transfer or compressed block-oriented transfer

By the 1990s, the usage of FTP centred on stream-oriented file structure and stream-oriented transfer mode; most FTP servers and clients from the 1990s onwards do not support other file structures or transfer modes.

[edit] Data structure

Data structure is specified using the STRU command. The following file structures are defined in section 3.1.1 of RFC959:

* F or FILE structure (stream-oriented). Files are viewed as an arbitrary sequence of bytes, characters or words. This is the usual file structure on Unix systems and other systems such as CP/M, MSDOS and Microsoft Windows. [Section 3.1.1.1]
* R or RECORD structure (record-oriented). Files are viewed as divided into records, which may be fixed or variable length. This file organization is common on mainframe and midrange systems, such as MVS, VM/CMS, OS/400 and VMS.
* P or PAGE structure (page-oriented). Files are divided into pages, which may either contain data or metadata; each page may also have a header giving various attributes. This file structure was specifically designed for TENEX systems, and is generally not supported on other platforms. RFC1123 section 4.1.2.3 recommends that this structure not be implemented.

[edit] Data type

Data type is specified using the TYPE command. The following data types are defined:

* A (ASCII). Textual data transferred over the network in the NVT ASCII character set.
* E (EBCDIC). Textual data transferred over the network in the EBCDIC character set.
* I or IMAGE (byte-oriented). Binary data transferred as a stream of 8-bit bytes.
* L or LOCAL (word-oriented). Binary data transferred as a stream of words. The number of bits in the word is specified as an argument, e.g. L32 for 32-bit words, L36 for 36-bit words. The words are packed into

A common problem historically has been FTP clients and servers which default to ASCII type, but do not provide any protection against transferring binary files. As a result, the binary files are corrupted, through e.g. translation of newline characters. In most contemporary clients, this is avoided by automatically defaulting to image type. Another approach would be to choose the FTP TYPE based on the type of the file as recorded in the filesystem (for those filesystems which do this) or heuristically.

L8 is effectively equivalent to I, and most FTP servers or clients do not accept other word sizes, save for 36-bit platforms. The data is to be transferred in packed binary format for transfer.

Note the data type indicates the type for transfer, not the type in which the data is stored on the source or destination systems. The client and server are free to convert the data to a form which is most convenient on their platform. For example, the textual data types of A and E may be subjected to translation of character set (e.g. ASCII vs EBCDIC), translation of newline convention (e.g. CRLF vs LF), or translation of textual data between stream-oriented and record-oriented formats (i.e. one record per a line, possibly padded with spaces to the maximum line length v.s. stream-oriented with newline characters to separate the lines). Similarly, a 36-bit platform may choose to store an L32 format file sent or received as 36-bit words each padded with four zero bits. The I data type is the least likely to be converted, but even it may be subject to conversion on non-byte oriented platforms.

Frequently FTP clients use the word "MODE" to refer to the data type, although that is a misnomer, since the word "MODE" is already taken to refer to the transfer mode.

[edit] Vertical format control

Only applicable to the the textual data types (A and E), and indicated as the second parameter to the TYPE command (section 3.1.1.5):

* N for non-print, meaning no vertical format control is specified. This is the default if none is specified.
* T to indicate that vertical format control is specified using the ASCII/EBCDIC TELNET format control characters, i.e. CR, LF, NL, VT, FF
* A to indicate that ASA vertical format control is to be applied

[edit] Transfer mode

The transfer mode is specified by the MODE command (section 3.40. The following modes are defined:

* S or STREAM MODE: data is represented as a stream of 8-bit bytes. An escape mechanism is defined for record-oriented files, to explicitly indicate record boundaries and explicit end of file. For stream-oriented files, no escape mechanism is defined and end of file is represented by closing the connection.
* B or BLOCK MODE: data is represented as a stream of blocks. Each block has a header to indicate its length, and also flags to mark end-of-record and end-of-file. The flags can also be used to indicate a suspect data block, e.g. a block of data read from a magnetic tape which failed its checksum, but is being transferred anyway even though it may contain errors. Also supports restart markers, which enable restarting the data transmission from that point.
* C or COMPRESSED MODE: similar to stream mode, but adds support for run-length encoding and also the flags defined in block mode.

As of the 1990s, most FTP clients and servers only support STREAM mode.

[edit] FTP commands

Commands which begin with the letter X are generally reserved for experimental extensions, although one should use SITE subcommands instead for this purpose.

RFC959 defines the following FTP commands, which were also present in RFC765:

* USER: supplies the username for login
* PASS: supplies the password for login
* ACCT: supplies accounting information. For example, a user may work on multiple projects; the account can be used to ensure that the charges for the data storage are billed to the correct project. (Not commonly implemented).
* CWD: changes the working directory to that specified
* REIN: removes all authentication information and parameter settings; must be followed by relogin via USER
* QUIT: terminates the connection
* PORT: host/port specification for data transfer
* PASV: enter passive mode
* TYPE: specify data type and vertical format control (see above)
* STRU: specify data structure (see above)
* MODE: specify transmission mode (see above)
* RETR: initiates a data transfer from server to client, specifying name of file to retrieve
* STOR: initiates a data transfer from client to server, specifying name file is to be stored in on server
* APPE: similar to STOR, except if file already exists, append received data to end of it rather than create
* ALLO: allocates space for a file. Optionally, specifies the maximum size of each record.
* REST: specifies the restart marker from which the transfer is to resume. Originally intended for use with restart markers sent by the server in B or C mode, but later extended in RFC3659 to byte offsets specified in S mode.
* RNFR: to rename a file, specify the file to be renamed
* RNTO: to rename a file, specifies the new name for the file, and performs the rename. Often also used to implement moves.
* DELE: deletes a file
* PWD: prints the current working directory
* LIST: opens a data connection with A or E data type, to transfer a listing of files in the current directory. The format of data is system-specific, but intended to be human readable.
* NLST: similar to LIST, but transfer unadorned names of files with CRLF or NL.
* SITE: provides subcommands to perform system specific services. The nature of these services is undefined.
* STAT: without arguments, current status of connection. With argument, equivalent to LIST, but the listing is transfered over the control connection encapsulated in messages.
* HELP: provides HELP, optionally with an argument to specify the specific command on which help is requested.
* NOOP: does nothing

RFC959 adds the following new commands which were not present in RFC765:

* CDUP: changes the working directory to the parent. Present since the notation for parent directory varies from platform to platform (although most commonly .. on systems descended from Unix or MS DOS).
* SMNT: mount a different file system or volume. Intended for systems such as DOS or VMS where there is a distinction between volume and directory in pathnames; but commonly unimplemented even on such systems.
* STOU: store unique - initiates a data transfer from client to server; server shall chose a unique name for file to be received
* RMD: removes a directory
* MKD: creates a directory
* PWD: prints the current directory
* SYST: identifies the operating system of the server

RFC765 described a number of commands which were removed in RFC959. These have not been part of FTP implementations since the early 1980s, since their functionality was later replaced (in part) by SMTP:

* MLFL: used to send email over the data connection
* MAIL: used to send email over the control connection
* MSND: like MAIL, but sends data directly to user's terminal rather than their mailbox
* MSOM: behaves as either MAIL or MSND -- send to terminal if allowed, otherwise to mailbox
* MSAM: similar to MSOM -- except that MSOM only sends to mailbox if delivery to terminal not possible; but MSAM sends to mailbox irrespective of whether terminal delivery is successfully attempted
* MRSQ: enables transmission of a single email to multiple users at the same host
* MRCP: subsequent to MRSQ, identifies one such recipient; repeated for each recipient

RFC2228 adds a number of commands related to encryption and message authentication:

* AUTH: identifies the authentication/security mechanism to be used
* ADAT: specifies security data specific to the chosen AUTH mechanism
* PBSZ: used to negotiate maximum buffer size for encrypted data
* PROT: specifies protection level for data channel. Following levels are defined:
o C (Clear) - data channel is subject neither to encryption nor integrity protection
o S (Safe) - integrity protection applied to data channel
o E (Confidential) - encryption applied to data channel
o P (Private) - both encryption and integrity protection applied to data channel
* CCC: disables integrity protection for subsequent commands on control channel
* MIC: sends a command with integrity protection
* CONF: sends a command with confidentiality protection
* ENC: sends a command with both integrity and confidentiality protection

RFC1639 ("FOOBAR"; succeeded RFC1545) adds support for FTP over arbitrary transport protocols, such as IPX/SPX or OSI. For this, it defines two new commands:

* LPRT: similar to PORT, but supports arbitrary address and port formats.
* LPSV: similar extension to PASV

RFC2389 defines two new commands used as a generic extension mechanism for FTP:

* FEAT: retrieves a listing of optional features supported by FTP server
* OPTS: a generic mechanism for the client to specify options to arbitrary FTP commands

RFC2428 adds two new commands, similar in principle to RFC1639 but differing in details:

* EPRT: similar to PORT, but supports arbitrary address families rather than only IPv4; specifically intended for IPv6.
* EPSV: similar extension to PASV

LPRT sends addresses as an arbitrary octet string (albeit decimal encoded), EPRT sends them as formatted strings, the format of the string being dependent upon the address format. EPRT assumes a the use of TCP-style 16-bit port numbers, whereas LPRT is more flexible and supports transport protocols with greater than 16-bit port numbers.

RFC2640 adds one new command:

* LANG: used to choose the language for FTP messages

RFC3659 defines several new commands:

* MDTM: retrieve file modification time
* SIZE: retrieve file size
* MLSD: retrieve listing of files in a directory. Unlike NLST, this returns not only file names but also attributes; but unlike LIST, it returns the attributes in an extensible standardised format rather than an arbitrary platform-specific one.
* MLST: same as MLSD, but retrieves listing for an individual file rather than a directory. For directories, retrieves their own attributes rather than a listing of their members. MLST does not require a data connection, but returns a single line containing the listing for the requested path.

[edit] FTP and web browsers

Most recent web browsers and file managers can connect to FTP servers, although they may lack the support for protocol extensions such as FTPS. This allows manipulation of remote files over FTP through an interface similar to that used for local files. This is done via an FTP URL, which takes the form ftp(s):// (e.g., ftp://ftp.gimp.org/). A password can optionally be given in the URL, e.g.: ftp(s)://:@:. Most web-browsers require the use of passive mode FTP, which not all FTP servers are capable of handling. Some browsers allow only the downloading of files, but offer no way to upload files to the server.

[edit] FTP and NAT devices

The representation of the IP addresses and port numbers in the PORT command and PASV reply poses another challenge for Network address translation (NAT) devices in handling FTP. The NAT device must alter these values, so that they contain the IP address of the NAT-ed client, and a port chosen by the NAT device for the data connection. The new address and port will probably differ in length in their decimal representation from the original address and port. This means that altering the values on the control connection by the NAT device must be done carefully, changing the TCP Sequence and Acknowledgment fields for all subsequent packets. Such translation is not usually performed in most NAT devices, but special application layer gateways exist for this purpose.

See also Application-level gateway

[edit] FTP over SSH (not SFTP)

FTP over SSH (not SFTP) refers to the practice of tunneling a normal FTP session over an SSH connection.

Because FTP uses multiple TCP connections (unusual for a TCP/IP protocol that is still in use), it is particularly difficult to tunnel over SSH. With many SSH clients, attempting to set up a tunnel for the control channel (the initial client-to-server connection on port 21) will protect only that channel; when data is transferred, the FTP software at either end will set up new TCP connections (data channels) which will bypass the SSH connection, and thus have no confidentiality, integrity protection, etc.

Otherwise, it is necessary for the SSH client software to have specific knowledge of the FTP protocol, and monitor and rewrite FTP control channel messages and autonomously open new forwardings for FTP data channels. Version 3 of SSH Communications Security's software suite, and the GPL licensed FONC are two software packages that support this mode.

FTP over SSH is sometimes referred to as secure FTP; this should not be confused with other methods of securing FTP, such as with SSL/TLS (FTPS). Other methods of transferring files using SSH that are not related to FTP include SFTP and SCP; in each of these, the entire conversation (credentials and data) is always protected by the SSH protocol.

3G


3G

International Mobile Telecommunications-2000 (IMT-2000), better known as 3G or 3rd Generation, is a family of standards for wireless communications defined by the International Telecommunication Union[1], which includes GSM EDGE, UMTS, and CDMA2000 as well as DECT and WiMAX. Services include wide-area wireless voice telephone, video calls, and wireless data, all in a mobile environment. Compared to 2G and 2.5G services, 3G allows simultaneous use of speech and data services and higher data rates (up to 14.4 Mbit/s on the downlink and 5.8 Mbit/s on the uplink with HSPA+). Thus, 3G networks enable network operators to offer users a wider range of more advanced services while achieving greater network capacity through improved spectral efficiency.

The International Telecommunication Union (ITU) defined the third generation (3G) of mobile telephony standards – IMT-2000 – to facilitate growth, increase bandwidth, and support more diverse applications. For example, GSM (the current most popular cellular phone standard) could deliver not only voice, but also circuit-switched data at download speeds up to 14.4 kbps. But to support mobile multimedia applications, 3G had to deliver packet-switched data with better spectral efficiency, at far greater speeds.



Overview

In 1999, ITU approved five radio interfaces for IMT-2000 as a part of the ITU-R M.1457 Recommendation; WiMAX was added in 2007.[2]

There are evolutionary standards that are backwards-compatible extensions to pre-existing 2G networks as well as revolutionary standards that require all-new networks and frequency allocations.[3] The later group is the UMTS family, which consists of standards developed for IMT-2000, as well as the independently-developed standards DECT and WiMAX, which were included because they fit the IMT-2000 definition.
Overview of 3G/IMT-2000 standards[4] ITU IMT-2000 common name(s) high-speed data pre-4G duplex channel description geographical areas
CDMA Single‑Carrier (IMT‑SC) EDGE (UWT-136) EDGE Evolution none FDD TDMA evolutionary upgrade to GSM/GPRS[nb 1] worldwide, except Japan and Korea
CDMA Multi‑Carrier (IMT‑MC) CDMA2000 EV-DO UMB[nb 2] CDMA evolutionary upgrade to cdmaOne (IS-95) Americas, Asia, some others
CDMA Direct Spread (IMT‑DS) UMTS[nb 3] W‑CDMA[nb 4] HSPA LTE family of revolutionary standards. worldwide
CDMA TDD (IMT‑TC) TD‑CDMA[nb 5] TDD Europe
TD‑SCDMA[nb 6] China
FDMA/TDMA (IMT‑FT) DECT none FDMA/TDMA short-range; standard for cordless phones Europe, USA
IP‑OFDMA WiMAX (IEEE 802.16) OFDMA late addition worldwide

While EDGE is part of the 3G standard, most GSM/UMTS phones report EDGE (“2.75G”) and UMTS (“3G”) network availability as separate functionality.

[edit] History

The first pre-commercial 3G network was launched by NTT DoCoMo in Japan branded FOMA, in May 2001 on a pre-release of W-CDMA technology.[7] The first commercial launch of 3G was also by NTT DoCoMo in Japan on October 1, 2001, although it was initially somewhat limited in scope;[8][9] broader availability was delayed by apparent concerns over reliability.[10] The second network to go commercially live was by SK Telecom in South Korea on the 1xEV-DO technology in January 2002. By May 2002 the second South Korean 3G network was by KTF on EV-DO and thus the Koreans were the first to see competition among 3G operators.

The first European pre-commercial network was at the Isle of Man by Manx Telecom, the operator then owned by British Telecom, and the first commercial network in Europe was opened for business by Telenor in December 2001 with no commercial handsets and thus no paying customers. These were both on the W-CDMA technology.

The first commercial United States 3G network was by Monet Mobile Networks, on CDMA2000 1x EV-DO technology, but this network provider later shut down operations. The second 3G network operator in the USA was Verizon Wireless in October 2003 also on CDMA2000 1x EV-DO, and this network has grown strongly since then.

The first pre-commercial demonstration network in the southern hemisphere was built in Adelaide, South Australia by m.Net Corporation in February 2002 using UMTS on 2100 MHz. This was a demonstration network for the 2002 IT World Congress. The first commercial 3G network was launched by Hutchison Telecommunications branded as Three in March 2003.

In December 2007, 190 3G networks were operating in 40 countries and 154 HSDPA networks were operating in 71 countries, according to the Global Mobile Suppliers Association (GSA). In Asia, Europe, Canada and the USA, telecommunication companies use W-CDMA technology with the support of around 100 terminal designs to operate 3G mobile networks.

In Europe, mass market commercial 3G services were introduced starting in March 2003 by 3 (Part of Hutchison Whampoa) in the UK and Italy. The European Union Council suggested that the 3G operators should cover 80% of the European national populations by the end of 2005.

Roll-out of 3G networks was delayed in some countries by the enormous costs of additional spectrum licensing fees. (See Telecoms crash.) In many countries, 3G networks do not use the same radio frequencies as 2G, so mobile operators must build entirely new networks and license entirely new frequencies; an exception is the United States where carriers operate 3G service in the same frequencies as other services. The license fees in some European countries were particularly high, bolstered by government auctions of a limited number of licenses and sealed bid auctions, and initial excitement over 3G's potential. Other delays were due to the expenses of upgrading equipment for the new systems.

By June 2007 the 200 millionth 3G subscriber had been connected. Out of 3 billion mobile phone subscriptions worldwide this is only 6.7%. In the countries where 3G was launched first - Japan and South Korea - 3G penetration is over 70%[11]. In Europe the leading country is Italy with a third of its subscribers migrated to 3G. Other leading countries by 3G migration include UK, Austria, Australia and Singapore at the 20% migration level. A confusing statistic is counting CDMA 2000 1x RTT customers as if they were 3G customers. If using this definition, then the total 3G subscriber base would be 475 million at June 2007 and 15.8% of all subscribers worldwide.

Still several major countries such as Indonesia have not awarded 3G licenses and customers await 3G services. China delayed its decisions on 3G for many years, mainly because of their Government's delay in establishing well defined standards[12]. China announced in May 2008, that the telecoms sector was re-organized and three 3G networks would be allocated so that the largest mobile operator, China Mobile, would retain its GSM customer base. China Unicom would retain its GSM customer base but relinquish its CDMA2000 customer base, and launch 3G on the globally leading WCDMA (UMTS) standard. The CDMA2000 customers of China Unicom would go to China Telecom, which would then launch 3G on the CDMA 1x EV-DO standard. This meant that China would have all three main cellular technology 3G standards in commercial use. Finally in January 2009, Ministry of industry and Information Technology of China has awarded licenses of all three standards,TD-SCDMA to China Mobile, WCDMA to China Unicom and CDMA2000 to China Telecom.

In November 2008, Turkey has auctioned four IMT 2000/UMTS standard 3G licenses with 45, 40, 35 and 25 MHz top frequencies. Turkcell has won the 45MHz band with its €358 million offer followed by Vodafone and Avea leasing the 40 and 35MHz frequencies respectively for 20 years. The 25MHz top frequency license remains to be auctioned.

The first African use of 3G technology was a 3G videocall made in Johannesburg on the Vodacom network in November 2004. The first commercial launch of 3G in Africa was by EMTEL in Mauritius on the W-CDMA standard. In north African Morocco in late March 2006, a 3G service was provided by the new company Wana.

Telus first introduced 3G services in Canada in 2005. Rogers Wireless began implementing 3G HSDPA services in eastern Canada early 2007 in the form of Rogers Vision. Fido Solutions and Rogers Wireless now offer 3G service in most urban centres.

T-Mobile, a major Telecommunication services provider has recently rolled out a list of over 120 U.S. cities which will be provided with 3G Network coverage in the year 2009.[13] M/AAL2 or IP/RTP.

[edit] Features

[edit] Data rates

ITU has not provided a clear definition of the data rate users can expect from 3G equipment or providers. Thus users sold 3G service may not be able to point to a standard and say that the rates it specifies are not being met. While stating in commentary that "it is expected that IMT-2000 will provide higher transmission rates: a minimum speed of 2 Mbit/s and maximum of 14.4 Mbit/s for stationary users, and 348 kbit/s in a moving vehicle,"[14] the ITU does not actually clearly specify minimum or average rates or what modes of the interfaces qualify as 3G, so various rates are sold as 3G intended to meet customers expectations of broadband speed.

[edit] Security

3G networks offer a greater degree of security than 2G predecessors. By allowing the UE to authenticate the network it is attaching to, the user can be sure the network is the intended one and not an impersonator. 3G networks use the KASUMI block crypto instead of the older A5/1 stream cipher. However, a number of serious weaknesses in the KASUMI cipher have been identified[citation needed].

In addition to the 3G network infrastructure security, end to end security is offered when application frameworks such as IMS are accessed, although this is not strictly a 3G property.

[edit] Evolution from 2G

2G networks were built mainly for voice services and slow data transmission.

[edit] From 2G to 2.5G

The first major step in the evolution to 3G occurred with the introduction of General Packet Radio Service (GPRS). So the cellular services combined with GPRS became' 2.5G.'

GPRS could provide data rates from 56 kbit/s up to 114 kbit/s. It can be used for services such as Wireless Application Protocol (WAP) access, Multimedia Messaging Service (MMS), and for Internet communication services such as email and World Wide Web access. GPRS data transfer is typically charged per megabyte of traffic transferred, while data communication via traditional circuit switching is billed per minute of connection time, independent of whether the user actually is utilizing the capacity or is in an idle state.

[edit] From 2.5G to 2.75G (EDGE)

GPRS networks evolved to EDGE networks with the introduction of 8PSK encoding. Enhanced Data rates for GSM Evolution (EDGE), Enhanced GPRS (EGPRS), or IMT Single Carrier (IMT-SC) is a backward-compatible digital mobile phone technology that allows improved data transmission rates, as an extension on top of standard GSM. EDGE can be considered a 3G radio technology and is part of ITU's 3G definition, but is most frequently referred to as 2.75G. EDGE was deployed on GSM networks beginning in 2003—initially by Cingular (now AT&T) in the United States.

EDGE is standardized by 3GPP as part of the GSM family, and it is an upgrade that provides a potential three-fold increase in capacity of GSM/GPRS networks. The specification achieves higher data-rates by switching to more sophisticated methods of coding (8PSK), within existing GSM timeslots. EDGE can be used for any packet switch

[edit] Evolution towards 4G

Both 3GPP and 3GPP2 are currently working on further extensions to 3G standards, named Long Term Evolution and Ultra Mobile Broadband, respectively. Being based on an all-IP network infrastructure and using advanced wireless technologies such as MIMO, these specifications already display features characteristic for IMT-Advanced (4G), the successor of 3G. However, falling short of the speed requirements for 4G (which is 1 Gbit/s for stationary and 100 Mbit/s for mobile operation), these standards are classified as 3.9G or Pre-4G.

3GPP plans to meet the 4G goals with LTE Advanced, whereas Qualcomm has halted development of UMB in favour of the LTE family.[5].

WiMAX






WiMAX


The Internet Protocol Suite
Application Layer
BGP · DHCP · DNS · FTP · GTP · HTTP · IMAP · IRC · Megaco · MGCP · NNTP · NTP · POP · RIP · RPC · RTP · RTSP · SDP · SIP · SMTP · SNMP · SOAP · SSH · Telnet · TLS/SSL · XMPP · (more)
Transport Layer
TCP · UDP · DCCP · SCTP · RSVP · ECN · (more)
Internet Layer
IP (IPv4, IPv6) · ICMP · ICMPv6 · IGMP · IPsec · (more)
Link Layer
ARP · RARP · NDP · OSPF · Tunnels (L2TP) · PPP · Media Access Control (Ethernet, MPLS, DSL, ISDN, FDDI) · Device Drivers · (more)
This box: view • talk • edit
WiMAX base station equipment with a sector antenna and wireless modem on top
A pre-WiMAX CPE of a 26 km connection mounted 13 meters above the ground (2004, Lithuania).

WiMAX, meaning Worldwide Interoperability for Microwave Access, is a telecommunications technology that provides wireless transmission of data using a variety of transmission modes, from point-to-multipoint links to portable and fully mobile[citation needed] internet access. The technology provides up to 3 Mbit/s [1][2][3][4][5][6][7][8][9][10][11][12] broadband speed without the need for cables. The technology is based on the IEEE 802.16 standard (also called Broadband Wireless Access). The name "WiMAX" was created by the WiMAX Forum, which was formed in June 2001 to promote conformity and interoperability of the standard. The forum describes WiMAX as "a standards-based technology enabling the delivery of last mile wireless broadband access as an alternative to cable and DSL".[13]
Contents




Definitions

The terms "fixed WiMAX", "mobile WiMAX", "802.16d" and "802.16e" are frequently used incorrectly. Correct definitions are the following:

* 802.16-2004 is often called 802.16d, since that was the working party that developed the standard. It is also frequently referred to as "fixed WiMAX" since it has no support for mobility.
* 802.16e-2005 is an amendment to 802.16-2004 and is often referred to in shortened form as 802.16e. It introduced support for mobility, amongst other things and is therefore also known as "mobile WiMAX".

Uses

The bandwidth and range of WiMAX make it suitable for the following potential applications:

* Connecting Wi-Fi hotspots to the Internet.
* Providing a wireless alternative to cable and DSL for "last mile" broadband access.
* Providing data and telecommunications services.
* Providing a source of Internet connectivity as part of a business continuity plan. That is, if a business has both a fixed and a wireless Internet connection, especially from unrelated providers, they are unlikely to be affected by the same service outage.
* Providing portable connectivity.

Broadband access

Companies are closely examining WiMAX for last mile connectivity.[citation needed] The resulting competition may bring lower pricing for both home and business customers or bring broadband access to places where it has been economically unavailable.[citation needed]

WiMAX access was used to assist with communications in Aceh, Indonesia, after the tsunami in December 2004.[citation needed] All communication infrastructure in the area, other than amateur radio, was destroyed, making the survivors unable to communicate with people outside the disaster area and vice versa. WiMAX provided broadband access that helped regenerate communication to and from Aceh.[citation needed]

In addition, WiMAX was donated by Intel Corporation to assist the FCC and FEMA in their communications efforts in the areas affected by Hurricane Katrina.[15] In practice, volunteers used mainly self-healing mesh, VoIP, and a satellite uplink combined with Wi-Fi on the local link.[16]

[edit] Subscriber units (Client Units)

WiMAX subscriber units are available in both indoor and outdoor versions from several manufacturers. Self-install indoor units are convenient, but radio losses mean that the subscriber must be significantly closer to the WiMAX base station than with professionally-installed external units. As such, indoor-installed units require a much higher infrastructure investment as well as operational cost (site lease, backhaul, maintenance) due to the high number of base stations required to cover a given area. Indoor units are comparable in size to a cable modem or DSL modem. Outdoor units are roughly the size of a laptop PC, and their installation is comparable to the installation of a residential satellite dish.

With the potential of mobile WiMAX, there is an increasing focus on portable units.[citation needed] This includes handsets (similar to cellular smartphones), PC peripherals (PC Cards or USB dongles), and embedded devices in laptops, which are now available for Wi-Fi services. In addition, there is much emphasis from operators on consumer electronics devices such as Gaming consoles, MP3 players and similar devices[citation needed]. It is notable that WiMAX is more similar to Wi-Fi than to 3G cellular technologies.

Current certified devices can be found at the WiMAX Forum web site. This is not a complete list of devices available as certified modules are embedded into laptops, MIDs (Mobile Internet Devices), and private labeled devices.[citation needed]

Mobile handset applications

Sprint Nextel announced in mid-2006 that it would invest about US$ 5 billion in a WiMAX technology buildout over the next few years.[17] Since that time Sprint has faced many setbacks, that have resulted in steep quarterly losses. On May 7, 2008, Sprint, Imagine, Google, Intel, Comcast, and Time Warner announced a pooling of an average of 120 MHz of spectrum and formation of a new company which will take the name Clearwire. The new company hopes to benefit from combined services offerings and network resources as a springboard past its competitors. The cable companies will provide media services to other partners while gaining access to the wireless network as a Mobile virtual network operator. Google will contribute Android handset device development and applications and will receive revenue share for advertising and other services they provide. Clearwire Sprint and current Clearwire gain a majority stock ownership in the new venture and ability to access between the new Clearwire and Sprint 3G networks. Some details remain unclear including how soon and in what form announced multi-mode WiMAX and 3G EV-DO devices will be available. This raises questions that arise for availability of competitive chips that require licensing of Qualcomm's IPR.

Some analysts have questioned how the deal will work out: Although fixed-mobile convergence has been a recognized factor in the industry, prior attempts to form partnerships among wireless and cable companies have generally failed to lead to significant benefits to the participants. Other analysts point out that as wireless progresses to higher bandwidth, it inevitably competes more directly with cable and DSL, thrusting competitors into bed together. Also, as wireless broadband networks grow denser and usage habits shift, the need for increased backhaul and media service will accelerate, therefore the opportunity to leverage cable assets is expected to increase.

Backhaul/access network applications

WiMAX is a possible replacement candidate for cellular phone technologies such as GSM and CDMA, or can be used as an overlay to increase capacity. It has also been considered as a wireless backhaul technology for 2G, 3G, and 4G networks in both developed and poor nations.[18][19]

In North America, backhaul for urban cellular operations is typically provided via one or more copper wire line T1 connections, whereas remote cellular operations are sometimes backhauled via satellite. In most other regions, urban and rural backhaul is usually provided by microwave links. (The exception to this is where the network is operated by an incumbent with ready access to the copper network, in which case T1 lines may be used). WiMAX is a broadband platform and as such has much more substantial backhaul bandwidth requirements than legacy cellular applications. Therefore traditional copper wire line backhaul solutions are not appropriate. Consequently the use of wireless microwave backhaul is on the rise in North America and existing microwave backhaul links in all regions are being upgraded. [20] Capacities of between 34 Mbit/s and 1 Gbit/s are routinely being deployed with latencies in the order of 1ms.[citation needed] In many cases, operators are aggregating sites using wireless technology and then presenting traffic on to fiber networks where convenient.

Deploying WiMAX in rural areas with limited or no internet backbone will be challenging as additional methods and hardware will be required to procure sufficient bandwidth from the nearest sources — the difficulty being in proportion to the distance between the end-user and the nearest sufficient internet backbone.

[edit] Technical information
Illustration of a WiMAX MIMO board

WiMAX is a term coined to describe standard, interoperable implementations of IEEE 802.16 wireless networks, similar to the way the term Wi-Fi is used for interoperable implementations of the IEEE 802.11 Wireless LAN standard. However, WiMAX is very different from Wi-Fi in the way it works.

[edit] MAC layer/data link layer

In Wi-Fi the media access controller (MAC) uses contention access — all subscriber stations that wish to pass data through a wireless access point (AP) are competing for the AP's attention on a random interrupt basis.[citation needed] This can cause subscriber stations distant from the AP to be repeatedly interrupted[citation needed] by closer stations, greatly reducing their throughput.[citation needed]

In contrast, the 802.16 MAC uses a scheduling algorithm for which the subscriber station needs to compete only once (for initial entry into the network). After that it is allocated an access slot by the base station. The time slot can enlarge and contract, but remains assigned to the subscriber station, which means that other subscribers cannot use it.[citation needed] In addition to being stable under overload and over-subscription[citation needed], the 802.16 scheduling algorithm can also be more bandwidth efficient.[citation needed] The scheduling algorithm also allows the base station to control QoS parameters by balancing the time-slot assignments among the application needs of the subscriber stations[citation needed].

[edit] Physical layer

The original version of the standard on which WiMAX is based (IEEE 802.16) specified a physical layer operating in the 10 to 66 GHz range. 802.16a, updated in 2004 to 802.16-2004, added specifications for the 2 to 11 GHz range. 802.16-2004 was updated by 802.16e-2005 in 2005 and uses scalable orthogonal frequency-division multiple access (SOFDMA) as opposed to the orthogonal frequency-division multiplexing (OFDM) version with 256 sub-carriers (of which 200 are used) in 802.16d. More advanced versions, including 802.16e, also bring multiple antenna support through MIMO. See: WiMAX MIMO. This brings potential benefits in terms of coverage, self installation, power consumption, frequency re-use and bandwidth efficiency. 802.16e also adds a capability for full mobility support. The WiMAX certification allows vendors with 802.16d products to sell their equipment as WiMAX certified, thus ensuring a level of interoperability with other certified products, as long as they fit the same profile.

Most commercial interest is in the 802.16d and 802.16e standards, since the lower frequencies used in these variants suffer less from inherent signal attenuation and therefore give improved range and in-building penetration. Already today, a number of networks throughout the world are in commercial operation using certified WiMAX equipment compliant with the 802.16d standard.

[edit] Deployment
This article contains too much jargon and may need simplification or further explanation. Please discuss this issue on the talk page, and/or remove or explain jargon terms used in the article. Editing help is available. (June 2009)

Being a standard intended to satisfy the needs of next-generation data networks (4G), it is distinguished by its dynamic burst algorithm adaptive to the physical digital modulation of which is determined by environmental variables affecting RF propagation; modulation is chosen to be spectrally more efficient (more bits per OFDM/SOFDMA symbol). That is, when the bursts have a high signal strength and a carrier to noise plus interference ratio (CINR), they can more be easily decoded using digital signal processing (DSP). In contrast, operating in less favorable environments for RF communication, the system automatically steps down to a more robust mode (burst profile) which means less bits per OFDM/SOFDMA symbol; with the advantage that power per bit is higher and therefore simpler accurate signal processing can be performed.

Burst profiles are used inverse (algorithmically dynamic) to low signal attenuation; meaning throughput between subscriber stations and the base station is determined largely by proximity. Maximum distance is achieved by the use of the most robust burst profile; that is, the profile with the largest MAC frame allocation trade-off requiring more symbols (a larger portion of the MAC frame) to be allocated in transmitting a given amount of data than if the subscriber station was closer to the base station.

In the MAC Frame the subscriber stations are allocated and their individual burst profiles defined as well as the specific time allocation, but even if that is done automatically practical deployment should avoid high interference and high multipath environments as opposed to what the average radio network planning team (and executive staff from the adopting operator) could think, the reason for it lies in excessive interference and competition during the Initial Ranging (IR) process due to the usage of high transmitting power in base station (BS) and subscriber station (SS) alike, which can result in unwanted delays and ranging attempts that effectively detracts from a good user experience and can even result in wasted allocated symbols due to continuous connections/re-connections.

The system therefore is very complex to deploy as it is necessary to keep in mind not only the signal strength and CINR (as in systems like GSM) but it is also necessary to think how the spectrum is going to be dynamically assigned (resulting in dynamically changing total available bandwidth) to the served subscriber stations (other dynamic burst systems have 2 or 3 burst profiles, WiMAX developments have showed up to 7 in use at the same time), the DSP algorithms (Decodification) are tougher than in any other wireless systems, yet they cannot reconstruct any burst in any environment; It is usually very effective though, but coupled with OFDM/SOFDMA, it can result in a double edged sword which means by having a tougher set of DSP algorithms, usually deployed on specific purpose chips, the signal could (harmfully) reach farther distances than expected due to tunnel effects (constructive interference with neighbor frequencies). This could lead to highly interfered clutters with highly reflected signals and very high signal strength which can fool non-experienced planning staff (usually coming from 3gpp networks).

As a result the system has to be initially deployed in conjunction with product development staff (who are usually involved in the technology development in some way) from the given vendor as opposed to service technical staff (radio planning) from the operator or vendor as is usual practice, thus raising the cost of deployment. As with all new technologies, configuration and maintenance will become easier to use as more deployments occur.

[edit] Integration with an IP based Network
The WiMAX Forum WiMAX Architecture

The WiMAX Forum has proposed an architecture that defines how a WiMAX network can be connected with an IP based core network, which is typically chosen by operators that serve as Internet Service Providers (ISP); Nevertheless the WiMAX BS provide seamless integration capabilities with other types of architectures as with packet switched Mobile Networks.

The WiMAX forum proposal defines a number of components, plus some of the interconnections (or reference points) between these, labeled R1 to R5 and R8:

* SS/MS: the Subscriber Station/Mobile Station
* ASN: the Access Service Network[21]
* BS: Base station, part of the ASN
* ASN-GW: the ASN Gateway, part of the ASN
* CSN: the Connectivity Service Network
* HA: Home Agent, part of the CSN
* AAA: Authentication, Authorization and Accounting Server, part of the CSN
* NAP: a Network Access Provider
* NSP: a Network Service Provider

It is important to note that the functional architecture can be designed into various hardware configurations rather than fixed configurations. For example, the architecture is flexible enough to allow remote/mobile stations of varying scale and functionality and Base Stations of varying size - e.g. femto, pico, and mini BS as well as macros.

[edit] Comparison with Wi-Fi

Comparisons and confusion between WiMAX and Wi-Fi are frequent because both are related to wireless connectivity and Internet access.

* WiMAX uses spectrum to deliver a point-to-point connection to the Internet. Different 802.16 standards provide different types of access, from portable (similar to a cordless phone) to fixed (an alternative to wired access, where the end user's wireless termination point is fixed in location.)
* Wi-Fi uses unlicensed spectrum to provide access to a network. Wi-Fi is more popular in end user devices.
* WiMAX and Wi-Fi have quite different quality of service (QoS) mechanisms. WiMAX uses a mechanism based on connections between the base station and the user device. Each connection is based on specific scheduling algorithms. Wi-Fi has a QoS mechanism similar to fixed Ethernet, where packets can receive different priorities based on their tags. For example VoIP traffic may be given priority over web browsing.
* Wi-Fi runs on the Media Access Control's CSMA/CA protocol, which is connectionless and contention based, whereas WiMAX runs a connection-oriented MAC.

Both 802.11 and 802.16 define Peer-to-Peer (P2P) and ad hoc networks, where an end user communicates to users or servers on another Local Area Network (LAN) using its access point or base station.

[edit] Spectrum allocation issues

The 802.16 specification applies across a wide swath of the RF spectrum, and WiMAX could function on any frequency below 66 GHz,[22] (higher frequencies would decrease the range of a Base Station to a few hundred meters in an urban environment).

There is no uniform global licensed spectrum for WiMAX, although the WiMAX Forum has published three licensed spectrum profiles: 2.3 GHz, 2.5 GHz and 3.5 GHz, in an effort to decrease cost: economies of scale dictate that the more WiMAX embedded devices (such as mobile phones and WiMAX-embedded laptops) are produced, the lower the unit cost. (The two highest cost components of producing a mobile phone are the silicon and the extra radio needed for each band.) Similar economy of scale benefits apply to the production of Base Stations.

In the unlicensed band, 5.x GHz is the approved profile. Telecommunication companies are unlikely to use this spectrum widely other than for backhaul, since they do not own and control the spectrum.

In the USA, the biggest segment available is around 2.5 GHz,[23] and is already assigned, primarily to Sprint Nextel and Clearwire. Elsewhere in the world, the most-likely bands used will be the Forum approved ones, with 2.3 GHz probably being most important in Asia. Some countries in Asia like India and Indonesia will use a mix of 2.5 GHz, 3.3 GHz and other frequencies. Pakistan's Wateen Telecom uses 3.5 GHz.

Analog TV bands (700 MHz) may become available for WiMAX usage, but await the complete roll out of digital TV, and there will be other uses suggested for that spectrum. In the USA the FCC auction for this spectrum began in January 2008 and, as a result, the biggest share of the spectrum went to Verizon Wireless and the next biggest to AT&T.[24] Both of these companies have stated their intention of supporting LTE, a technology which competes directly with WiMAX. EU commissioner Viviane Reding has suggested re-allocation of 500–800 MHz spectrum for wireless communication, including WiMAX.[25]

WiMAX profiles define channel size, TDD/FDD and other necessary attributes in order to have inter-operating products. The current fixed profiles are defined for both TDD and FDD profiles. At this point, all of the mobile profiles are TDD only. The fixed profiles have channel sizes of 3.5 MHz, 5 MHz, 7 MHz and 10 MHz. The mobile profiles are 5 MHz, 8.75 MHz and 10 MHz. (Note: the 802.16 standard allows a far wider variety of channels, but only the above subsets are supported as WiMAX profiles.)

Since October 2007, the Radio communication Sector of the International Telecommunication Union (ITU-R) has decided to include WiMAX technology in the IMT-2000 set of standards.[26] This enables spectrum owners (specifically in the 2.5-2.69 GHz band at this stage) to use Mobile WiMAX equipment in any country that recognizes the IMT-2000.

Spectral efficiency

One of the significant advantages of advanced wireless systems such as WiMAX is spectral efficiency. For example, 802.16-2004 (fixed) has a spectral efficiency of 3.7 (bit/s)/Hertz, and other 3.5–4G wireless systems offer spectral efficiencies that are similar to within a few tenths of a percent. The notable advantage of WiMAX comes from combining SOFDMA with smart antenna technologies. This multiplies the effective spectral efficiency through multiple reuse and smart network deployment topologies. The direct use of frequency domain organization simplifies designs using MIMO-AAS compared to CDMA/WCDMA methods, resulting in more effective systems.[citation needed]

Limitations

A commonly-held misconception is that WiMAX will deliver 70 Mbit/s over 50 kilometers (~31 miles). In reality, WiMAX can either operate at higher bitrates or over longer distances but not both: operating at the maximum range of 50 km increases bit error rate and thus results in a much lower bitrate. Conversely, reducing the range (to <1 km) allows a device to operate at higher bitrates. There are no known examples of WiMAX services being delivered at bit rates over around 40 Mbit/s.[citation needed]

Typically, fixed WiMAX networks have a higher-gain directional antenna installed near the client (customer) which results in greatly increased range and throughput. Mobile WiMAX networks are usually made of indoor "Customer-premises equipment" (CPE) such as desktop modems, laptops with integrated Mobile WiMAX or other Mobile WiMAX devices. Mobile WiMAX devices typically have omnidirectional antennae which are of lower-gain compared to directional antennas but are more portable. In current deployments, the throughput may reach 2 Mbit/s symmetric at 10 km with fixed WiMAX and a high gain antenna. It is also important to consider that a throughput of 2 Mbit/s can mean 2 Mbit/s, symmetric simultaneously, 1 Mbit/s symmetric or some asymmetric mix (e.g. 0.5 Mbit/s downlink and 1.5 Mbit/s uplink or 1.5 Mbit/s downlink and 0.5 Mbit/s uplink), each of which required slightly different network equipment and configurations. Higher-gain directional antennas can be used with a WiMAX network with range and throughput benefits but the obvious loss of practical mobility.

Like most wireless systems, available bandwidth is shared between users in a given radio sector, so performance could deteriorate in the case of many active users in a single sector. In practice, most users will have a range of 2-3 Mbit/s services and additional radio cards will be added to the base station to increase the number of users that may be served as required.

Because of these limitations, the general consensus is that WiMAX requires various granular and distributed network architectures to be incorporated within the IEEE 802.16 task groups. This includes wireless mesh, grids, network remote station repeaters which can extend networks and connect to backhaul.

[edit] Silicon implementations

A critical requirement for the success of a new technology is the availability of low-cost chipsets and silicon implementations.

Intel Corporation is a leader in promoting WiMAX, and has developed its own chipset. However, it is notable that most of the major semiconductor companies have not and most of the products come from specialist smaller or start-up suppliers. For the client-side these include Sequans, whose chips are in more than half of the WiMAX Forum Certified(tm) MIMO-based Mobile WiMAX client devices, GCT Semiconductor, ApaceWave, Altair Semiconductor, Beceem, Comsys, Runcom, Motorola with TI, NextWave Wireless, Wavesat, Coresonic and SySDSoft. Both Sequans and Wavesat manufacture products for both clients and network while Texas Instruments, DesignArt, and picoChip are focused on WiMAX chip sets for base stations.

[edit] Standards

The current WiMAX incarnation, Mobile WiMAX, is based upon IEEE Std 802.16e-2005,[27] approved in December 2005. It is a supplement to the IEEE Std 802.16-2004,[28] and so the actual standard is 802.16-2004 as amended by 802.16e-2005 — the specifications need to be read together to understand them.

IEEE Std 802.16-2004 addresses only fixed systems. It replaced IEEE Standards 802.16-2001, 802.16c-2002, and 802.16a-2003.

IEEE 802.16e-2005 improves upon IEEE 802.16-2004 by:

* Adding support for mobility (soft and hard handover between base stations). This is seen as one of the most important aspects of 802.16e-2005, and is the very basis of 'Mobile WiMAX' (though this has yet to be demonstrated in any installed systems).
* Scaling of the Fast Fourier transform (FFT) to the channel bandwidth in order to keep the carrier spacing constant across different channel bandwidths (typically 1.25 MHz, 5 MHz, 10 MHz or 20 MHz). Constant carrier spacing results in a higher spectrum efficiency in wide channels, and a cost reduction in narrow channels. Also known as Scalable OFDMA (SOFDMA). Other bands not multiples of 1.25 MHz are defined in the standard, but because the allowed FFT subcarrier numbers are only 128, 512, 1024 and 2048, other frequency bands will not have exactly the same carrier spacing, which might not be optimal for implementations.
* Advanced antenna diversity schemes, and hybrid automatic repeat-request (HARQ)
* Adaptive Antenna Systems (AAS) and MIMO technology
* Denser sub-channelization, thereby improving indoor penetration
* Introducing Turbo Coding and Low-Density Parity Check (LDPC)
* Introducing downlink sub-channelization, allowing administrators to trade coverage for capacity or vice versa
* Fast Fourier transform algorithm
* Adding an extra QoS class for VoIP applications.

802.16d vendors point out that fixed WiMAX offers the benefit of available commercial products and implementations optimized for fixed access. It is a popular standard among alternative service providers and operators in developing areas due to its low cost of deployment and advanced performance in a fixed environment. Fixed WiMAX is also seen as a potential standard for backhaul of wireless base stations such as cellular, or Wi-Fi.

SOFDMA (used in 802.16e-2005) and OFDM256 (802.16d) are not compatible thus most equipment will have to be replaced if an operator wants or needs to move to the later standard. However, some manufacturers are planning to provide a migration path for older equipment to SOFDMA compatibility which would ease the transition for those networks which have already made the OFDM256 investment. Intel provides a dual-mode 802.16-2004 802.16-2005 chipset for subscriber units.

[edit] Conformance testing

TTCN-3 test specification language is used for the purposes of specifying conformance tests for WiMAX implementations. The WiMAX test suite is being developed by a Specialist Task Force at ETSI (STF 252).[29]

[edit] Associations

[edit] WiMAX Forum

The WiMAX Forum is a non profit organization formed to promote the adoption of WiMAX compatible products and services.[30]

A major role for the organization is to certify the interoperability of WiMAX products.[31] Those that pass conformance and interoperability testing achieve the "WiMAX Forum Certified" designation, and can display this mark on their products and marketing materials. Some vendors claim that their equipment is "WiMAX-ready", "WiMAX-compliant", or "pre-WiMAX", if they are not officially WiMAX Forum Certified.

Another role of the WiMAX Forum is to promote the spread of knowledge about WiMAX. In order to do so, it has a certified training program that is currently offered in English and French. It also offers a series of member events and endorses some industry events.

[edit] WiMAX Spectrum Owners Alliance
WiSOA logo

WiSOA was the first global organization composed exclusively of owners of WiMAX spectrum with plans to deploy WiMAX technology in those bands. WiSOA focussed on the regulation, commercialisation, and deployment of WiMAX spectrum in the 2.3–2.5 GHz and the 3.4–3.5 GHz ranges. WiSOA merged with the Wireless Broadband Alliance in April 2008. [32]

[edit] Competing technologies
Speed vs. Mobility of wireless systems: Wi-Fi, HSPA, UMTS, GSM

Within the marketplace, WiMAX's main competition comes from existing, widely deployed wireless systems such as UMTS and CDMA2000, as well as a number of Internet-oriented systems such as HiperMAN, and of course long range mobile Wi-Fi and mesh networking.

3G cellular phone systems usually benefit from already having entrenched infrastructure, having been upgraded from earlier systems. Users can usually fall back to older systems when they move out of range of upgraded equipment, often relatively seamlessly.

The major cellular standards are being evolved to so-called 4G, high-bandwidth, low-latency, all-IP networks with voice services built on top. The worldwide move to 4G for GSM/UMTS and AMPS/TIA (including CDMA2000) is the 3GPP Long Term Evolution effort. A planned CDMA2000 replacement called Ultra Mobile Broadband has been discontinued. For 4G systems, existing air interfaces are being discarded in favor of OFDMA for the downlink and a variety of OFDM based techniques for the uplink, similar to WiMAX.

In some areas of the world, the wide availability of UMTS and a general desire for standardization has meant spectrum has not been allocated for WiMAX: in July 2005, the EU-wide frequency allocation for WiMAX was blocked.

[edit] Mobile Broadband Wireless Access

Mobile Broadband Wireless Access (MBWA) is a technology being developed by IEEE 802.20 and is aimed at wireless mobile broadband for operations from 75 to 220 mph (120 to 350 km/h). The 802.20 standard committee was first to define many of the methods which were later funneled into Mobile WiMAX, including high speed dynamic modulation and similar scalable OFDMA capabilities. It apparently retains fast hand-off, Forward Error Correction (FEC) and cell edge enhancements.

The Working Group was temporarily suspended in mid-2006 by the IEEE-SA Standards Board because it had been the subject of a number of appeals. A preliminary investigation of one of these "revealed a lack of transparency, possible 'dominance,' and other irregularities in the Working Group".[33]

In September 2006, the IEEE-SA Standards Board approved a plan to enable the working group to continue under new conditions, and on 12 June 2008, the IEEE approved the new standard.

Qualcomm, a leading company behind 802.20, has dropped support for continued development in order to focus on LTE.[34]

[edit] Internet-oriented systems

Early WirelessMAN standards, the European standard HiperMAN and Korean standard WiBro have been harmonized as part of WiMAX and are no longer seen as competition but as complementary. All networks now being deployed in South Korea, the home of the WiBro standard, are now WiMAX.

As a short-range mobile Internet technology, such as in cafes and at transportation hubs like airports, the popular Wi-Fi 802.11b/g system is widely deployed, and provides enough coverage for some users to feel subscription to a WiMAX service is unnecessary.

[edit] Comparison
Main article: Comparison of wireless data standards
The neutrality of this article is disputed. Please see the discussion on the talk page. Please do not remove this message until the dispute is resolved. (January 2009)

The following table should be treated with caution because it only shows peak rates which are potentially very misleading. In addition, the comparisons listed are not normalized by physical channel size (i.e., spectrum used to achieve the listed peak rates); this obfuscates spectral efficiency and net through-put capabilities of the different wireless technologies listed below.
v • d • e
Comparison of Mobile Internet Access methods Standard ↓ Family ↓ Primary Use ↓ Radio Tech ↓ Downlink (Mbit/s) ↓ Uplink (Mbit/s) ↓ Notes ↓
LTE UMTS/4GSM General 4G OFDMA/MIMO/SC-FDMA 360 80 LTE-Advanced update to offer over 1 Gbit/s speeds.
WiMAX 802.16 Mobile Internet MIMO-SOFDMA 144 35 WiMAX m update to offer over 1 Gbit/s speeds.
Flash-OFDM Flash-OFDM Mobile Internet
mobility up to 200mph (350km/h) Flash-OFDM 5.3
10.6
15.9 1.8
3.6
5.4 Mobile range 18miles (30km)
extended range 34 miles (55km)
HIPERMAN HIPERMAN Mobile Internet OFDM 56.9 56.9
Wi-Fi Wi-Fi Mobile Internet OFDM/MIMO/CDMA 108 108 Mobile range (3km)
iBurst 802.20 Mobile Internet HC-SDMA/TDD/MIMO 95 36 Cell Radius: 3–12 km
Speed: 250kmph
Spectral Efficiency: 13 bits/s/Hz/cell
Spectrum Reuse Factor: "1"
EDGE Evolution GSM Mobile Internet TDMA/FDD 1.9 0.9 3GPP Release 7
UMTS W-CDMA
HSDPA+HSUPA
HSPA+ UMTS/3GSM General 3G CDMA/FDD

CDMA/FDD/MIMO 0.384
14.4
42 0.384
5.76
11.5 HSDPA widely deployed. Typical downlink rates today 2 Mbit/s, ~200 kbit/s uplink; HSPA+ downlink up to 42 Mbit/s.
UMTS-TDD UMTS/3GSM Mobile Internet CDMA/TDD 16 16 Reported speeds according to IPWireless using 16QAM modulation similar to HSDPA+HSUPA
1xRTT CDMA2000 Mobile phone CDMA 0.144 0.144 Succeeded by EV-DO
EV-DO 1x Rev. 0
EV-DO 1x Rev.A
EV-DO Rev.B CDMA2000 Mobile Internet CDMA/FDD 2.45
3.1
4.9xN 0.15
1.8
1.8xN Rev B note: N is the number of 1.25 MHz chunks of spectrum used. Not yet deployed.

Notes: All speeds are theoretical maximums and will vary by a number of factors, including the use of external antennae, distance from the tower and the ground speed (e.g. communications on a train may be poorer than when standing still). Usually the bandwidth is shared between several terminals. The performance of each technology is determined by a number of constraints, including the spectral efficiency of the technology, the cell sizes used, and the amount of spectrum available. For more information, see Comparison of wireless data standards.

LTE is expected to be ratified at the end of 2008, with commercial implementations becoming viable within the next two years.

[edit] Future development

Mobile WiMAX based upon 802.16e-2005 has been accepted as IP-OFDMA for inclusion as the sixth wireless link system under IMT-2000. This can hasten acceptance by regulatory authorities and operators for use in cellular spectrum. WiMAX II, 802.16m will be proposed for IMT-Advanced 4G.

The goal for the long term evolution of both WiMAX and LTE is to achieve 100 Mbit/s mobile and 1 Gbit/s fixed-nomadic bandwidth as set by ITU for 4G NGMN (Next Generation Mobile Network) systems through the adaptive use of MIMO-AAS and smart, granular network topologies. 3GPP LTE and WiMAX-m are concentrating much effort on MIMO-AAS, mobile multi-hop relay networking and related developments needed to deliver 10X and higher Co-Channel reuse multiples.

Since the evolution of core air-link technologies has approached the practical limits imposed by Shannon's Theorem, the evolution of wireless has embarked on pursuit of the 3X to 10X+ greater bandwidth and network efficiency by advances in the spatial and smart wireless broadband networking technologies.

[edit] Interference

A field test conducted by SUIRG (Satellite Users Interference Reduction Group) with support from the U.S. Navy, the Global VSAT Forum, and several member organizations yielded results showing interference at 12 km when using the same channels for both the WiMAX systems and satellites in C-band.[35] The WiMAX Forum has yet to respond.

[edit] Current deployments

[edit] Networks
Main article: List of deployed WiMAX networks

The WiMAX Forum now claims there are over 455 WiMAX networks deployed in over 135 countries.

[edit] By territory

This section gives details of regulatory decisions in various parts of the world. For information on deployments around the world see the List of deployed WiMAX networks

[edit] Africa

In South Africa Telecoms Regulator ICASA has only issued four licences for commercial WiMAX services: to wireless broadband solutions provider iBurst, state-owned signal distributor Sentech, second network operator Neotel, [Amatole Telecommunication Services] (under serviced area license holder in S.A.) and Telkom, all on the 3.5 GHz band. See the List of deployed WiMAX networks for details.

[edit] Americas

See the List of deployed WiMAX networks for details.

[edit] Asia

See the List of deployed WiMAX networks for details.

[edit] Europe

Commission Decision of 2008-05-21 on the harmonisation of the 3400-3800 MHz frequency band for terrestrial systems capable of providing electronic communications services in the Community.[36]

It includes:

* Pursuant to Article 4(2) of Decision 676/2002/EC (of the European Parliament and of the Council of 7 March 2002 on a regulatory framework for radio spectrum policy in the European Community - Radio Spectrum Decision -),[37] the Commission gave a mandate dated 4 January 2006 to the European Conference of Postal and Telecommunications Administrations (hereinafter the “CEPT”) to identify the conditions relating to the provision of harmonised radio frequency bands in the EU for Broadband Wireless Access (BWA) applications.
* In response to that Mandate, the CEPT issued a report (CEPT Report 15) on BWA, which concludes that the deployment of fixed, nomadic and mobile networks is technically feasible within the 3400-3800 MHz frequency band under the technical conditions described in the European Conference of Postal and Telecommunications Administrations Decision ECC/DEC/(07)02 and Recommendation ECC/REC/(04)05.
* No later than six months after entry into force of this Decision, Member States shall designate and make available, on a non-exclusive basis, the 3400-3600 MHz band for terrestrial electronic communications networks.
* By 1 January 2012 Member States shall designate and subsequently make available, on a non-exclusive basis, the 3600-3800 MHz band for terrestrial electronic communications networks.
* The designation of the 3400-3800 MHz band for fixed, nomadic and mobile applications is an important element addressing the convergence of the mobile, fixed and broadcasting sectors and reflecting technical innovation. Member States shall allow the use of the 3400-3800 MHz band in for fixed, nomadic and mobile electronic communications networks.
* This Decision is addressed to the Member States.

[edit] Germany

German Federal Network Agency has begun assigning frequencies for wireless Internet access in the band 3400 to 3600 MHz (in some places up to 4000 MHz).[38]

[edit] United Kingdom

The UK telecoms industry is waiting for OFCOM the UK’s telecoms regulator, to launch the tender process for the 2.6 GHz spectrum range for a number of services which can include WiMAX, including mobile services based on the 802.16e standard. This is currently delayed indefinitely due to the digital Britain report.[39]

[edit] Indonesia

* The Indonesian government announced on January 22, 2009 two ministry decrees and three regulations releasing spectrum at 2.3GHz and 3.3GHz for wireless broadband access across all regions of Indonesia. This means Indonesia will be using 2.3-GHz band for the Wimax 16.e standard while 3.3-GHz will be used for the 16.d standard.[40]

[edit] Literature

* K. Fazel and S. Kaiser, Multi-Carrier and Spread Spectrum Systems: From OFDM and MC-CDMA to LTE and WiMAX, 2nd Edition, John Wiley & Sons, 2008, ISBN 978-0-470-99821-2

* M. Ergen, Mobile Broadband - Including WiMAX and LTE, Springer, NY, 2009 ISBN 978-0-387-68189-4

[edit] See also
Search Wikimedia Commons Wikimedia Commons has media related to: WiMAX
Search Wikibooks Wikibooks has a book on the topic of
Nets, Webs and the Information Infrastructure

* Com-bridge
* Customer-premises equipment
* Evolved HSPA
* High-Speed Packet Access (HSPA)
* List of deployed WiMAX networks
* Mobile broadband
* Mobile VoIP
* Municipal broadband
* Packet Burst Broadband (PBB)
* Switched mesh
* WiBro
* wireless bridge
* Wireless broadband
* Wireless local loop

[
Pre Cellular (0G)

PTT • MTS • IMTS • AMTS • OLT • MTD • Autotel/PALM • ARP
1G

NMT • Hicap • CDPD • Mobitex • DataTAC
2G

iDEN • PDC • CSD • PHS • WiDEN
Pre-4G

iBurst • HiperMAN • WiMAX • WiBro • GAN (UMA)
Frequency Bands
Cellular • GSM • UMTS • PCS • SMR
[hide]Internet access
Network type Wired Wireless
Optical Coaxial cable Ethernet cable Phone line Power line Unlicensed terrestrial bands Licensed terrestrial bands Satellite
LAN 1000BASE-X G.hn Ethernet HomePNA · G.hn G.hn Wi-Fi · Bluetooth · DECT · Wireless USB
WAN PON DOCSIS Dial-up · ISDN · DSL BPL Muni Wi-Fi GPRS · iBurst · WiBro/WiMAX · UMTS-TDD, HSPA · EVDO · LTE Satellite
[show]
v • d • e
Wireless video and data distribution methods

Advanced Wireless Services · Amateur television · Analog television · Digital radio · Digital television · Digital television in Europe · Digital terrestrial television (DTT or DTTV) ·
Digital Video Broadcasting: ( Terrestrial - Satellite - Handheld ) · DVB-MS · Ku band · Local Multipoint Distribution Service (LMDS) · Microwave · Mobile TV · Multichannel Multipoint Distribution Service (MMDS) now known as Business Radio Service (BRS) · Instructional Television Fixed Service (ITFS) now known as Educational Broadband Service (EBS) · MVDS · MVDDS · Satellite Internet access · Satellite radio · Satellite television · Wi-Fi · WiMAX · Wireless local loop
[show]
v • d • e
Wireless system generations
1G
NMT · AMPS · Hicap · CDPD · Mobitex · DataTAC · TACS · ETACS
2G
GSM · iDEN · D-AMPS · IS-95 · PDC · CSD · PHS · GPRS · HSCSD · WiDEN
2.75G
EDGE/EGPRS · CDMA2000 (1xRTT)
3G
UMTS (W-CDMA) · CDMA2000 (1xEV-DO/IS-856) · FOMA · TD-SCDMA · GAN/UMA · WiMAX
3.5G
UMTS (HSDPA) · UMTS (HSUPA) · CDMA2000 (EV-DO Rev.A)
3.75G
UMTS (HSPA+) · CDMA2000 (EV-DO Rev.B/3xRTT)
4G
Flash-OFDM · 3GPP LTE
Related articles
Comparison of mobile telecommunications standards · List of mobile telecommunications standards
Retrieved from "http://en.wikipedia.org/wiki/WiMAX"
Categories: Mobile telecommunications standards | IEEE 802 | Wireless networking | Metropolitan area networks | Ethernet | Network access
Hidden categories: Articles needing additional references from April 2009 | All articles with unsourced statements | Articles with unsourced statements from March 2009 | Cleanup from June 2009 | Wikipedia articles needing style editing from June 2009 | All articles needing style editing | Articles with unsourced statements from September 2007 | Articles with unsourced statements from April 2009 | NPOV disputes from January 2009 | All NPOV disputes
Views