A WAP Gateway is a server through which all wireless (WAP) data is transferred from wireless devices (using WAP

requests) to content sites (in WML format) and back again. A WAP Gateway is a server that typically resides within the wireless carrier's network but may also reside within a corporate business environment. Infinite WAP Gateways are the most popular and widely used WAP Servers in the world, and provides a range of solutions for both the corporate business and carrier markets. Infinite WAP Servers connect WAP compatible mobile phones to Internet- and Intranet- based applications and content.

A WAP gateway sits between mobile devices using the WAP protocol and the World Wide Web, passing pages from one to the other much like a proxy. This translates pages into a form suitable for the mobiles, for instance using the Wireless Markup Language (WML). This process is hidden from the phone, so it may access the page in the same way as a browser accesses HTML, using a URL (for example, http://example.com/foo.wml), provided the mobile phone operator has not specifically prevented this. The Domain Name System (DNS) is a hierarchical naming system built on a distributed database for computers, services, or any resource connected to the Internet or a private network. Most importantly, it translates domain names meaningful to humans into the numerical identifiers associated with networking equipment for the purpose of locating and addressing these devices worldwide. An often-used analogy to explain the Domain Name System is that it serves as the "phone book" for the Internet by translating human-friendly computer hostnames into IP addresses. For example, the domain name www.example.com translates to the addresses 192.0.32.10 (IPv4) and 2620:0:2d0:200::10 (IPv6). The Domain Name System makes it possible to assign domain names to groups of Internet resources and users in a meaningful way, independent of each entity's physical location. Because of this, World Wide Web (WWW) hyperlinks and Internet contact information can remain consistent and constant even if the current Internet routing arrangements change or the participant uses a mobile device. Internet domain names are easier to remember than IP addresses such as 208.77.188.166 (IPv4) or 2001:db8:1f70::999:de8:7648:6e8 (IPv6). Users take advantage of this when they recite meaningful Uniform Resource Locators (URLs) and e-mail addresses without having to know how the computer actually locates them. The Domain Name System distributes the responsibility of assigning domain names and mapping those names to IP addresses by designating authoritative name servers for each domain. Authoritative name servers are assigned to be responsible for their particular domains, and in turn can assign other authoritative name servers for their sub-domains. This mechanism has made the DNS distributed and fault tolerant and has helped avoid the need for a single central register to be continually consulted and updated. In general, the Domain Name System also stores other types of information, such as the list of mail servers that accept email for a given Internet domain. By providing a worldwide, distributed keyword-based redirection service, the Domain Name System is an essential component of the functionality of the Internet.

Other identifiers such as RFID tags, UPCs, International characters in email addresses and host names, and a variety of other identifiers could all potentially use DNS.[1][2] The Domain Name System also specifies the technical functionality of this database service. It defines the DNS protocol, a detailed definition of the data structures and communication exchanges used in DNS, as part of the Internet Protocol Suite.

Internet Protocol Suite

Application Layer DHCP DNS FTP HTTP IMAP IRC LDAP MGCP NNTP NTP POP RIP RPC RTP SIP SMTP SNMP SOCKS SSH Telnet XMPP (more) Transport Layer TCP TLS/SSL UDP DCCP SCTP RSVP ECN (more) Internet Layer IP (IPv4, IPv6) ICMP ICMPv6 IGMP BGP OSPF IPsec (more) Link Layer ARP/InARP NDP Tunnels (L2TP) PPP Media Access Control (Ethernet, DSL, ISDN, FDDI) (more) vde

RADIUS
From Wikipedia, the free encyclopedia Jump to: navigation, search For other uses, see Radius (disambiguation).

Internet Protocol Suite

Application Layer DHCP DNS FTP HTTP IMAP IRC LDAP MGCP NNTP NTP POP RIP RPC RTP SIP SMTP SNMP SOCKS SSH Telnet XMPP (more) Transport Layer TCP TLS/SSL UDP DCCP SCTP RSVP ECN (more) Internet Layer IP (IPv4, IPv6) ICMP ICMPv6 IGMP BGP OSPF IPsec (more) Link Layer ARP/InARP NDP Tunnels (L2TP) PPP

Media Access Control (Ethernet, DSL, ISDN, FDDI) (more) vde

Remote Authentication Dial In User Service (RADIUS) is a networking protocol that provides centralized Authentication, Authorization, and Accounting (AAA) management for computers to connect and use a network service. RADIUS was developed by Livingston Enterprises, Inc., in 1991 as an access server authentication and accounting protocol and later brought into the Internet Engineering Task Force (IETF) standards.[1] Because of the broad support and the ubiquitous nature of the RADIUS protocol, it is often used by ISPs and enterprises to manage access to the Internet or internal networks, wireless networks, and integrated e-mail services. These networks may incorporate modems, DSL, access points, VPNs, network ports, web servers, etc.[2] RADIUS is a client/server protocol that runs in the application layer, using UDP as transport. The Remote Access Server, the Virtual Private Network server, the Network switch with portbased authentication, and the Network Access Server (NAS), are all gateways that control access to the network, and all have a RADIUS client component that communicates with the RADIUS server. The RADIUS server is usually a background process running on a UNIX or Windows NT machine.[3] RADIUS serves three functions:
1. to authenticate users or devices before granting them access to a network, 2. to authorize those users or devices for certain network services and 3. to account for usage of those services.

GPRS Core Network

From Wikipedia, the free encyclopedia Jump to: navigation, search

The GPRS core network is the central part of the General Packet Radio Service which allows 2G, 3G and WCDMA mobile networks to transmit IP packets to external networks such as the Internet. The GPRS system is an integrated part of the GSM network switching subsystem.

Contents
[hide]

1 General support functions 2 GPRS tunnelling protocol (GTP) 3 GPRS support nodes (GSN) o 3.1 Gateway GPRS Support Node (GGSN) o 3.2 Serving GPRS Support Node (SGSN) 3.2.1 Common SGSN Functions 3.2.2 GSM/EDGE specific SGSN functions 3.2.3 WCDMA specific SGSN functions 4 Access point 5 PDP Context 6 Reference Points and Interfaces o 6.1 Interfaces in the GPRS network 7 See also 8 References 9 External links

[edit] General support functions

GPRS core structure

The GPRS core network provides mobility management, session management and transport for Internet Protocol packet services in GSM and WCDMA networks. The core network also provides support for other additional functions such as billing and lawful interception. It was also proposed, at one stage, to support packet radio services in the US D-AMPS TDMA system, however, in practice, all of these networks have been converted to GSM so this option has become irrelevant. Like GSM in general, GPRS module is an open standards driven system. The standardization body is the 3GPP.

[edit] GPRS tunnelling protocol (GTP)

Main article: GPRS tunnelling protocol

GPRS tunnelling protocol is the defining IP protocol of the GPRS core network. Primarily it is the protocol which allows end users of a GSM or WCDMA network to move from place to place while continuing to connect to the Internet as if from one location at the Gateway GPRS Support Node (GGSN). It does this by carrying the subscriber's data from the subscriber's current Serving GPRS Support Node (SGSN) to the GGSN which is handling the subscriber's session. Three forms of GTP are used by the GPRS core network.
GTP-U for transfer of user data in separated tunnels for each Packet Data Protocol (PDP) context GTP-C for control reasons including:

setup and deletion of PDP contexts verification of GSN reachability updates; e.g., as subscribers move from one SGSN to another.

GTP' for transfer of charging data from GSNs to the charging function.

GGSNs and SGSNs (collectively known as GSNs) listen for GTP-C messages on UDP port 2123 and for GTP-U messages on port 2152. This communication happens within a single network or may, in the case of international roaming, happen internationally, typically across a GPRS roaming exchange (GRX). The Charging Gateway Function (CGF) listens to GTP' messages sent from the GSNs on TCP or UDP port 3386. The core network sends charging information to the CGF, typically including PDP context activation times and the quantity of data which the end user has transferred. However, this communication which occurs within one network is less standardized and may, depending on the vendor and configuration options, use proprietary encoding or even an entirely proprietary system. GTP version zero supports both signalling and user data under one generic header. It can be used with UDP (User Datagram Protocol) or TCP (Transmission Control Protocol) on the registered port 3386. GTP version one is used only on UDP. The control plane protocol GTP-C (Control) using registered port 2123 and the user plane protocol GTP-U (User) using registered port 2152.

[edit] GPRS support nodes (GSN)

A GSN is a network node which supports the use of GPRS in the GSM core network. All GSNs should have a Gn interface and support the GPRS tunnelling protocol. There are two key variants of the GSN, namely Gateway and Serving GPRS Support Node.
[edit] Gateway GPRS Support Node (GGSN)

The Gateway GPRS Support Node (GGSN) is a main component of the GPRS network. The GGSN is responsible for the interworking between the GPRS network and external packet switched networks, like the Internet and X.25 networks. From an external network's point of view, the GGSN is a router to a sub-network, because the GGSN hides the GPRS infrastructure from the external network. When the GGSN receives data addressed to a specific user, it checks if the user is active. If it is, the GGSN forwards the data to the SGSN serving the mobile user, but if the mobile user is inactive, the data is discarded. On the other hand, mobile-originated packets are routed to the right network by the GGSN. The GGSN is the anchor point that enables the mobility of the user terminal in the GPRS/UMTS networks. In essence, it carries out the role in GPRS equivalent to the Home Agent in Mobile IP. It maintains routing necessary to tunnel the Protocol Data Units (PDUs) to the SGSN that service a particular MS (Mobile Station). The GGSN converts the GPRS packets coming from the SGSN into the appropriate packet data protocol (PDP) format (e.g., IP or X.25) and sends them out on the corresponding packet data network. In the other direction, PDP addresses of incoming data packets are converted to the GSM address of the destination user. The readdressed packets are sent to the responsible SGSN. For this purpose, the GGSN stores the current SGSN address of the user and his or her profile in its location register. The GGSN is responsible for IP address assignment and is the default router for the connected user equipment (UE). The GGSN also performs authentication and charging functions. Other functions include subscriber screening, IP Pool management and address mapping, QoS and PDP context enforcement. With LTE scenario the GGSN functionality moves to SAE gateway (with SGSN functionality working in MME).
[edit] Serving GPRS Support Node (SGSN)

A Serving GPRS Support Node (SGSN) is responsible for the delivery of data packets from and to the mobile stations within its geographical service area. Its tasks include packet routing and transfer, mobility management (attach/detach and location management), logical link management, and authentication and charging functions. The location register of the SGSN stores location information (e.g., current cell, current VLR) and user profiles (e.g., IMSI, address(es) used in the packet data network) of all GPRS users registered with this SGSN....

[edit] Common SGSN Functions

Detunnel GTP packets from the GGSN (downlink) Tunnel IP packets toward the GGSN (uplink) Carry out mobility management as Standby mode mobile moves from one Routing Area to another Routing Area Billing user data

[edit] GSM/EDGE specific SGSN functions

Enhanced Data Rates for GSM Evolution (EDGE) specific SGSN functions and characteristics are:

Maximum data rate of approx. 60 kbit/s (150 kbit/s for EDGE) per subscriber Connect via frame relay or IP to the Packet Control Unit using the Gb protocol stack Accept uplink data to form IP packets Encrypt down-link data, decrypt up-link data Carry out mobility management to the level of a cell for connected mode mobiles

[edit] WCDMA specific SGSN functions

Carry up to about 42 Mbit/s traffic downlink and 5.8 Mbit/s traffic uplink (HSPA+) Tunnel/detunnel downlink/uplink packets toward the radio network controller (RNC) Carry out mobility management to the level of an RNC for connected mode mobiles

These differences in functionality have led some manufacturers to create specialist SGSNs for each of WCDMA and GSM which do not support the other networks, whilst other manufacturers have succeeded in creating both together, but with a performance cost due to the compromises required.

[edit] Access point

Main article: Access point name

An access point is:

An IP network to which a mobile can be connected A set of settings which are used for that connection A particular option in a set of settings in a mobile phone

When a GPRS mobile phone sets up a PDP context, the access point is selected. At this point an access point name (APN) is determined

Example: aricenttechnologies.mnc012.mcc345.gprs Example: Internet Example: mywap Example: hcl.cisco.ggsn

This access point is then used in a DNS query to a private DNS network. This process (called APN resolution) finally gives the IP address of the GGSN which should serve the access point. At this point a PDP context can be activated.

[edit] PDP Context

The packet data protocol (PDP; e.g., IP, X.25, FrameRelay) context is a data structure present on both the Serving GPRS Support Node (SGSN) and the Gateway GPRS Support Node (GGSN) which contains the subscriber's session information when the subscriber has an active session. When a mobile wants to use GPRS, it must first attach and then activate a PDP context. This allocates a PDP context data structure in the SGSN that the subscriber is currently visiting and the GGSN serving the subscriber's access point. The data recorded includes

Subscriber's IP address Subscriber's IMSI Subscriber's o Tunnel Endpoint ID (TEID) at the GGSN o Tunnel Endpoint ID (TEID) at the SGSN

The Tunnel Endpoint ID (TEID) is a number allocated by the GSN which identifies the tunnelled data related to a particular PDP context. Several PDP contexts may use the same IP address. The Secondary PDP Context Activation procedure may be used to activate a PDP context while reusing the PDP address and other PDP context information from an already active PDP context, but with a different QoS profile.[1] Note that the procedure is called secondary, not the resulting PDP contexts that have no such relationship with the one the PDP address of which they reused. A total of 11 PDP contexts (with any combination of primary and secondary) can co-exist. NSAPI are used to differentiate the different PDP context.

[edit] Reference Points and Interfaces

Within the GPRS core network standards there are a number of interfaces and reference points (logical points of connection which probably share a common physical connection with other reference points). Some of these names can be seen in the network structure diagram on this page.

[edit] Interfaces in the GPRS network Ga The interface serves the CDRs (accounting records) which are written in the GSN and sent to the charging gateway (CG). This interface uses a GTP-based protocol, with modifications that supports CDRs (Called GTP' or GTP prime). Gb Interface between the base station subsystem and the SGSN the transmission protocol could be Frame Relay or IP. Gd Interface between the SGSN and the SMS Gateway. Can use MAP1, MAP2 or MAP3. Ge The interface between the SGSN and the service control point (SCP); uses the CAP protocol. Gf The interface between the SGSN and the Equipment Identity Register (EIR), used for checking the mobile's equipment identity number (IMEI) against a list of reported stolen mobile phones. Gi IP based interface between the GGSN and a public data network (PDN) either directly to the Internet or through a WAP gateway. Gmb The interface between the GGSN and the Broadcast-Multicast Service Center (BM-SC), used for controlling MBMS bearers. Gn IP Based interface between SGSN and other SGSNs and (internal) GGSNs. DNS also shares this interface. Uses the GTP Protocol. Gp IP based interface between internal SGSN and external GGSNs. Between the SGSN and the external GGSN, there is the border gateway (which is essentially a firewall). Also uses the GTP Protocol.

Gr Interface between the SGSN and the HLR. Messages going through this interface uses the MAP3 protocol. Gs Interface between the SGSN and the MSC (VLR). Uses the BSSAP+ protocol. This interface allows paging and station availability when it performs data transfer. When the station is attached to the GPRS network, the SGSN keeps track of which routing area (RA) the station is attached to. An RA is a part of a larger location area (LA). When a station is paged this information is used to conserve network resources. When the station performs a PDP context, the SGSN has the exact BTS the station is using. Gx The on-line policy interface between the GGSN and the charging rules function (CRF). It is used for provisioning service data flow based on charging rules. Uses the diameter protocol. Gy The on-line charging interface between the GGSN and the online charging system (OCS). Uses the diameter protocol (DCCA application). Gz The off-line (CDR-based) charging interface between the GSN and the CG. Uses GTP'. Lg The interface between the SGSN and the Gateway Mobile Location Center (GMLC), used for location based services.

BGF - Border Gateway Function

By: Bruce Bahlmann Performs policyenforcement and network address translation (NAT) functions under the control of the serving policy decision function (S-PDF). BGF operates on unidirectional flows related to aparticular session. BGF is part of TISPAN, a more generalized version of IP multimedia subsystem (IMS) that includes wireline environments. There are three types of BGF: access (A-BGF) located in between access and core network at the access network side, core (C-BGF) located in between access and core network at the core network side, and interconnect (I-BGF) located in between two core networks.

Network Policy Server

Updated May 12, 2011 Network Policy Server (NPS) is the Microsoft implementation of a Remote Authentication Dial-in User Service (RADIUS) server and proxy in Windows Server 2008. NPS is the replacement for Internet Authentication Service (IAS) in Windows Server 2003. As a RADIUS server, NPS performs centralized connection authentication, authorization, and accounting for many types of network access, including wireless and virtual private network (VPN) connections. As a RADIUS proxy, NPS forwards authentication and accounting messages to other RADIUS servers. NPS also acts as a health evaluation server for Network Access Protection (NAP).

Network access server

From Wikipedia, the free encyclopedia Jump to: navigation, search This article does not cite any references or sources.
Please help improve this article by adding citations to reliable sources. Unsourced material may be challenged and removed. (October 2009)

A Network Access Server (NAS) is a single point of access to a remote resource.

Contents
[hide]

1 Overview 2 Examples 3 Associated Protocols 4 See also

[edit] Overview
The NAS is meant to act as a gateway to guard access to a protected resource. This can be anything from a telephone network, to printers, to the Internet.

The client connects to the NAS. The NAS then connects to another resource asking whether the client's supplied credentials are valid. Based on that answer the NAS then allows or disallows access to the protected resource.

[edit] Examples
The above translates into different implementations for different uses. Here are some examples.

An Internet Service Provider which provides network access via common modem or modem-like devices (be it PSTN, DSL, cable or GPRS/UMTS) can have one or more NAS (network access server) devices which accept PPP, PPPoE or PPTP connections, checking credentials and recording accounting data via back-end RADIUS servers, and allowing users access through that connection.

Note: If you want to contribute to this website in any section kindly send us the Content/Links using Contact Us . We surely include the content in our website Email This to Friend

Push-to-Talk over Cellular

Some GSM operators are now offering Push-to-Talk over Cellular (PoC) services, which allow people to use their phones as walkie-talkies, merely pushing a button to talk to another user or group of users.

Users can check whether their 'buddies' (people pre-selected from their contacts' list) are connected before activating the service. Only one person can talk at a time and all other participants hear the speech. The service has been successful in the U.S. with business users and a number of European GSM operators are now offering PoC to consumers. In order to use the service, users need to be a customer of an operator that has launched PoC, and have a compatible handset that has the PoC software built into the device. Please contact your operator to determine whether your network supports PoC services

IMS == IP Multimedia Subsystem (and not as written)

In the article the acronym 'IMS' is expanded into "IP Multimedia System". The correct term is actually "IP Multimedia Subsystem".

IP Multimedia Subsystem
From Wikipedia, the free encyclopedia Jump to: navigation, search This article may be too technical for most readers to understand. Please improve this article to make it understandable to non-experts, without removing the technical details. (December 2010) This article uses abbreviations that may be confusing or ambiguous. Specific concerns may be found on the Talk page. Please improve this article if you can. (May 2011)

The IP Multimedia Subsystem (IMS) is an architectural framework for delivering Internet Protocol (IP) multimedia services. It was originally designed by the wireless standards body 3rd Generation Partnership Project (3GPP), as a part of the vision for evolving mobile networks beyond GSM. Its original formulation (3GPP R5) represented an approach to delivering "Internet services" over GPRS. This vision was later updated by 3GPP, 3GPP2 and TISPAN by requiring support of networks other than GPRS, such as Wireless LAN, CDMA2000 and fixed line. To ease the integration with the Internet, IMS uses IETF protocols wherever possible, e.g. Session Initiation Protocol (SIP). According to the 3GPP,[1] IMS is not intended to standardize applications but rather to aid the access of multimedia and voice applications from wireless and wireline terminals, i.e. create a form of fixed-mobile convergence (FMC). This is done by having a horizontal control layer that isolates the access network from the service layer. From a logical architecture perspective, services need not have their own control functions, as the control layer is a common horizontal layer. However in implementation this does not necessarily map into greater reduced cost and complexity. Alternative and overlapping technologies for access and provisioning of services across wired and wireless networks include combinations of Generic Access Network, soft switches and "naked" SIP. It is easier to sell services than to sell the virtues of "integrated services", but additionally the task to sell an IMS based on a single service is also difficult as there are often (cheaper) alternatives to creating and deploying that particular service. Since it is becoming increasingly easier to access content and contacts using mechanisms outside the control of traditional wireless/fixed operators, the interest of IMS is being challenged.[2] Introduction
Comarch Active Mediation is a solution for connecting a network to the billing system. It enables controlling, charging and billing of voice, data and content services in any billing system with a real-time charging interface. Connectivity is possible in any network type from PSTN to IMS.

The solution is 3GPP Standard based and also supports many additional industry standard interfaces. This flexibility allows for the use of appropriate components in the configuration required by the customer. Not all components are always required.

SCP / connectivity
An SCP provides connectivity to the SS7 based network. It may work as a real Service Control Point element or only provide simple SS7 network connectivity. The following protocols are supported: CAMEL, WIN MAP, ANSI-41 INAP, AIN, ISUP SIGTRAN In addition, SMS and DATA services may be controlled using proxy, gateway or signaling protocol.
Charging interface files

Billing System with real-time rating

Ro files Ro Real-time interface CAP SIP / ISC Rf xDR

IMS-GWF CDF CGF

Charging Data Function Charging Gateway Function

SCP / connectivity OCF

NGN / IMS network

Online Charging Function

telecommunications
IMS-GWF
IMS-GWF is an IMS standard element which works as a special type of application server and controls the services over SIP. It also controls SIP service sessions and charging over the DIAMETER Ro interface. This component controls user prepaid balances, performs balance reservations in the billing system and disconnects a call when the balance is zero.

OCF Online Charging Function

The Online Charging Function component integrates a few charging interfaces with the billing system interface. If the billing system supports Diameter Ro, this component only works as a proxy and is transparent. For a proprietary charging interface it contains the logic for translating different real-time charging interfaces.

Supported interfaces:
Diameter Ro (client and server) Parlay/OSA Charging & Account Management over CORBA (client and server) Parlay/OSA Charging & Account Management over WebServices (client and server) Various IN proprietary charging interfaces

CDF Charging Data Function

The Charging Data Function components receive information about service sessions over the DIAMETER Rf interface and spool events to specified files. These files are then processed by the Charging Gateway Function.

Charging Gateway Function

All xDR files received from CDF and different network elements are analyzed, unduplicated, correlated and converted to a single unified data format. Such service usage data is then uploaded to the retail or wholesale billing system. There are many industry formats supported by offline mediation. For new formats, it is possible to configure a new text or binary format and map data fields or even build custom mediation rules.

Other interfaces supported

These additional protocols are supported by the solution: RADIUS Parlay/OSA Multi-Party Call Control

Frame Relay is a standardized wide area network technology that specifies the physical and logical link layers of digital telecommunications channels using a packet switching methodology. Originally designed for transport across Integrated Services Digital Network (ISDN) infrastructure, it may be used today in the context of many other network interfaces. Network providers commonly implement Frame Relay for voice (VoFR) and data as an encapsulation technique, used between local area networks (LANs) over a wide area network (WAN). Each end-user gets a private line (or leased line) to a frame-relay node. The frame-relay network handles the transmission over a frequently-changing path transparent to all end-users. Frame Relay has become one of the most extensively-used WAN protocols. Its cheapness (compared to leased lines) provided one reason for its popularity. The extreme simplicity of configuring user equipment in a Frame Relay network offers another reason for Frame Relay's popularity. With the advent of Ethernet over fiber optics, MPLS, VPN and dedicated broadband services such as cable modem and DSL, the end may loom for the Frame Relay protocol and encapsulation.[citation needed] However many rural areas remain lacking DSL and cable modem services. In such cases the least expensive type of non-dial-up connection remains a 64-kbit/s frame-relay line. Thus a retail chain, for instance, may use Frame Relay for connecting rural stores into their corporate WAN.

Contents
[hide]

1 Technical description o 1.1 Protocol data unit o 1.2 Congestion control 2 Frame Relay versus X.25 3 Virtual circuits 4 Frame Relay origins 5 Local Management Interface (LMI) 6 Committed information rate (CIR) 7 Market reputation 8 See also 9 References 10 External links

[edit] Technical description

A basic Frame Relay network

The designers of Frame Relay aimed to a telecommunication service for cost-efficient data transmission for intermittent traffic between local area networks (LANs) and between end-points in a wide area network (WAN). Frame Relay puts data in variable-size units called "frames" and leaves any necessary error-correction (such as re-transmission of data) up to the end-points. This speeds up overall data transmission. For most services, the network provides a permanent virtual circuit (PVC), which means that the customer sees a continuous, dedicated connection without

having to pay for a full-time leased line, while the service-provider figures out the route each frame travels to its destination and can charge based on usage. An enterprise can select a level of service quality - prioritizing some frames and making others less important. Frame Relay can run on fractional T-1 or full T-carrier system carriers. Frame Relay complements and provides a mid-range service between basic rate ISDN, which offers bandwidth at 128 kbit/s, and Asynchronous Transfer Mode (ATM), which operates in somewhat similar fashion to frame Relay but at speeds from 155.520 Mbit/s to 622.080 Mbit/s. Frame Relay has its technical base in the older X.25 packet-switching technology, designed for transmitting data on analog voice lines. Unlike X.25, whose designers expected analog signals, Frame Relay offers a fast packet technology, which means that the protocol does not attempt to correct errors. When a Frame Relay network detects an error in a frame, it simply drops that frame. The end points have the responsibility for detecting and retransmitting dropped frames. (However, digital networks offer an incidence of error extraordinarily small relative to that of analog networks.) Frame Relay often serves to connect local area networks (LANs) with major backbones as well as on public wide-area networks (WANs) and also in private network environments with leased lines over T-1 lines. It requires a dedicated connection during the transmission period. Frame Relay does not provide an ideal path for voice or video transmission, both of which require a steady flow of transmissions. However, under certain circumstances, voice and video transmission do use Frame Relay. Frame Relay originated as an extension of Integrated Services Digital Network (ISDN). Its designers aimed to enable a packet-switched network to transport the circuit-switched technology. The technology has become a stand-alone and cost-effective means of creating a WAN. Frame Relay switches create virtual circuits to connect remote LANs to a WAN. The Frame Relay network exists between a LAN border device, usually a router, and the carrier switch. The technology used by the carrier to transport data between the switches is variable and may differ among carriers (i.e. to function, a practical Frame Relay implementation need not rely solely on its own transportation mechanism). The sophistication of the technology requires a thorough understanding of the terms used to describe how Frame Relay works. Without a firm understanding of Frame Relay, it is difficult to troubleshoot its performance. Frame-relay frame structure essentially mirrors almost exactly that defined for LAP-D. Traffic analysis can distinguish Frame Relay format from LAP-D by its lack of a control field.
ch Headquarters