Professional Documents
Culture Documents
Issue 03
Date 2013-06-30
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://enterprise.huawei.com
Intended Audience
This document describes the definition, purpose, and implementation of features on enterprise
datacom products including the campus network switch, enterprise router, data center switch,
and WLAN. For features supported by the device, see Configuration Guide.
This document is intended for:
l Network planning engineers
l Commissioning engineers
l Data configuration engineers
l System maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
&<1-n> The parameter before the & sign can be repeated 1 to n times.
Change History
Changes between document issues are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
l 4 LTE
l 8 RTC
Change History
Changes between document issues are cumulative. Therefore, the latest document version
contains all updates made to previous versions.
Contents
3 PPPoE.............................................................................................................................................24
3.1 Introduction to PPPoE..................................................................................................................................................25
3.2 Principles......................................................................................................................................................................25
3.2.1 PPPoE Networking....................................................................................................................................................25
3.2.2 PPPoE Packet Format................................................................................................................................................26
3.2.3 PPPoE Session Establishment Process......................................................................................................................28
3.2.4 PPPoE Packet Structure.............................................................................................................................................29
3.3 Applications..................................................................................................................................................................32
3.3.1 Connecting a LAN to the Internet Using an ADSL Modem.....................................................................................32
3.3.2 Wireless PPPoE Access.............................................................................................................................................33
3.4 References....................................................................................................................................................................34
4 LTE..................................................................................................................................................35
4.1 Introduction to LTE......................................................................................................................................................36
4.2 Principles......................................................................................................................................................................37
4.2.1 LTE Network Architecture........................................................................................................................................37
4.2.2 LTE Hardware and Supported Frequency Bands and Rates.....................................................................................39
4.2.3 LTE Dial-up Connection Setup.................................................................................................................................41
4.2.4 APN...........................................................................................................................................................................42
4.3 Applications..................................................................................................................................................................43
4.3.1 LTE Links as Backup WAN Links............................................................................................................................43
4.3.2 LTE Links as Primary WAN Links...........................................................................................................................44
4.3.3 VPN Tunnel to the Enterprise Headquarters over an LTE Link...............................................................................44
4.3.4 Data Communication and VoIP Communication Using LTE Multi-APN................................................................45
4.4 References....................................................................................................................................................................45
5 ATM...............................................................................................................................................47
5.1 Introduction..................................................................................................................................................................48
5.2 Principles......................................................................................................................................................................48
5.2.1 ATM Protocol Architecture.......................................................................................................................................48
5.2.2 ATM Physical layer...................................................................................................................................................51
5.2.3 ATM Layer................................................................................................................................................................51
5.2.4 ATM Adaptation Layer.............................................................................................................................................58
5.2.5 ATM Multiprotocol Encapsulation...........................................................................................................................60
5.2.6 ATM Service Classes................................................................................................................................................64
5.3 Application...................................................................................................................................................................65
5.3.1 IPoA...........................................................................................................................................................................65
5.3.2 IPoEoA......................................................................................................................................................................66
5.3.3 PPPoA........................................................................................................................................................................67
5.3.4 PPPoEoA...................................................................................................................................................................67
5.4 Reference......................................................................................................................................................................68
6 Frame Relay..................................................................................................................................70
6.1 Introduction..................................................................................................................................................................71
6.2 Principles......................................................................................................................................................................71
6.2.1 Basic Concepts of FR................................................................................................................................................71
6.2.2 LMI Protocol.............................................................................................................................................................73
6.2.3 InARP........................................................................................................................................................................78
6.2.4 Basic Principles of FR...............................................................................................................................................79
6.2.5 FR Sub-Interfaces......................................................................................................................................................80
6.2.6 FR QoS......................................................................................................................................................................83
6.2.7 PVC Group................................................................................................................................................................84
6.2.8 FR Compression........................................................................................................................................................85
6.2.9 Multilink FR..............................................................................................................................................................86
6.2.10 PPPoFR/MPoFR......................................................................................................................................................88
6.2.11 FRoISDN.................................................................................................................................................................88
6.2.12 FRoIP.......................................................................................................................................................................89
6.3 Application...................................................................................................................................................................89
6.3.1 FR Access..................................................................................................................................................................89
6.3.2 MFR...........................................................................................................................................................................90
6.3.3 PPPoFR/MPoFR........................................................................................................................................................91
6.3.4 FRoISDN...................................................................................................................................................................91
6.3.5 PVC Group................................................................................................................................................................91
6.4 Reference......................................................................................................................................................................92
7 ISDN..............................................................................................................................................94
7.1 Introduction to ISDN....................................................................................................................................................95
7.2 Principles......................................................................................................................................................................95
7.2.1 ISDN Protocol Architecture......................................................................................................................................95
7.2.2 ISDN Layer 2 Protocols............................................................................................................................................96
7.2.3 ISDN Layer 3 Protocols............................................................................................................................................98
7.3 Applications..................................................................................................................................................................99
7.3.1 ISDN Dial-up Access................................................................................................................................................99
7.3.2 ISDN Leased Line...................................................................................................................................................100
7.4 References..................................................................................................................................................................100
8 RTC...............................................................................................................................................102
8.1 Introduction to RTC....................................................................................................................................................103
8.2 Principles....................................................................................................................................................................103
8.3 Application.................................................................................................................................................................105
8.3.1 RTC Application......................................................................................................................................................105
8.4 References..................................................................................................................................................................106
1 DCC
Purpose
When the data to be transmitted is delay-insensitive, bursting, and has a small volume, the routers
can use the DCC mode to reduce costs. DCC is a flexible, cost-effective, and efficient solution.
The DCC functions are as follows:
l DCC uses link backup to ensure reliable communication. When communication fails
because of a link error or other reasons, the backup link is used to continue the
communication.
l DCC on a PPPoE/PPPoEoA/PPPoA client saves costs for users.
Benefits
The DCC function brings remarkable benefits to enterprises:
l Saving costs: The routers set up a connection by dialing only when there is data to be
transmitted between them, and tear down the connection when no data is transmitted on
the link.
l Ensuring reliable communication: DCC uses link backup to ensure reliable communication.
When communication fails because of a link error or other reasons, the backup link is used
to continue the communication.
l Flexible configurations: The resource-shared DCC (RS-DCC) mode allows physical
interfaces to negotiate proper working parameters. A physical interface can be used for
multiple links and provides multiple transmission rates.
1.2 Principle
The device supports two DCC modes: circular DCC (C-DCC) and resource-shared DCC (RS-
DCC). The two modes are applicable to different scenarios. The two ends in communication can
adopt different modes.
The following are the terms related to DCC:
l Physical interface
A physical interface can be an ISDN BRI interface, an ISDN PRI interface, or a cellular
interface.
l Dialer interface
A dialer interface is a logical interface for implementing DCC. After a physical interface
is bound to a dialer interface, the physical interface inherits the configurations of the dialer
interface.
l Dialup interface
A dialup interface can be a dialer interface, a physical interface bound to the dialer interface,
or a physical interface carrying DCC parameters.
Figure 1-1 Relationships between C-DCC physical interfaces and dialer interfaces
Dialer
interface
physical
interface dialer
number
Serial2/0/0:15 Dialer1
destination A
dialer
route
Serial1/0/0:15
destination B
Dialer2
Serial1/0/1:15
dialer
route
destination C
Serial2/0/1:15
As shown in the figure, a physical interface can belong to only one dialer interface, but each
dialer interface can be bound to multiple destination addresses. Each dialer interface can contain
multiple physical interfaces. A physical interface can be directly bound to one or multiple
destination addresses, but does not necessarily belong to any dialer interface.
Figure 1-2 Relationships between RS-DCC physical interfaces and dialer interfaces
physical Dialer
interface interface
Dialer Serial
bunde3 1/0/0:15 dialer number
Dialer1 destination A
Serial
1/0/1:15
Dialer Serial
bunde2 2/0/0:15 dialer number
Dialer2 destination B
As shown in the figure, a physical interface can belong to multiple dialer bundles. Each dialer
interface can use only one dialer bundle and be bound to only one destination address.
The physical interfaces in a dialer bundle have priorities. The dialer interface corresponding to
the dialer bundle chooses physical interfaces according to their priorities. As shown in the figure,
Dialer 2 uses Dialer bundle 2, and physical interfaces Serial2/0/0:15 and Serial1/0/1:15 belong
to Dialer bundle 2. A large priority value indicates a high priority. If the priority of Serial2/0/0:15
is 100 and the priority of Serial1/0/1:15 is 50, Dialer 2 will select Serial2/0/0:15 from Dialer
bundle 2.
A physical interface may have different priorities in different dialer bundles.
Overview
The dial-up backup function dynamically maintains dial-up links based on routes.
It provides the backup and routing functions, and implements reliable connections and on-
demand dialing function.
The dial-up backup function has the following characteristics:
l All routes can be backed up, including the routes generated by routing protocols, static
routes, and direct routes.
l Dial-up backup is used between interfaces or routers, but not used on a single interface or
link.
l If the primary link is broken, the backup link automatically takes over. There is no delay
during the switchover except the route convergence period.
l The dial-up backup function is applicable to all routing protocols, including RIP-1, RIP-2,
OSPF, IS-IS, and BGP. However, some routing protocols such as BGP choose the default
routes. If the primary link destined for the monitored network segment is broken, the backup
link begins to learn the routes destined for the monitored network segment by using BGP.
After the primary link recovers, the primary link learns routes again, but these routes may
not be the optimal routes. The router still uses the routes learned by the backup link. As a
result, the backup link cannot be disconnected and the dynamic route monitoring function
fails.
The following methods can solve the preceding problem:
– Set the IP address of the backup link to be greater than the IP address of the primary
link.
– Configure load balancing so that one route is learned by multiple links.
Internet
RouterA RouterB
Enterprise Enterprise
Branch Headquarters
ISDN
1.3 Application
DCC supports extensible dial-on-demand functions to meet various application requirements:
l DCC uses link backup to ensure reliable communication. When communication fails
because of a link error or other reasons, the backup link is used to continue the
communication.
Generally, a network of a different type is used for link backup. For example, an ISDN or
a 3G network can be used for the link backup of an IP network. The route implements link
backup by using either of the following modes:
– Interface backup
– Dial-up backup
l DCC on a PPPoE/PPPoEoA/PPPoA client saves costs for users.
Link Backup Using the Interface Backup Mode
As shown in Figure 1-4, Serial2/0/0:15, which is a dialup interface, is the backup of GE1/0/0.
When GE1/0/0 does not function properly, traffic on GE1/0/0 is switched to Serial2/0/0:15. The
DCC dialing process on Serial2/0/0:15 is triggered by the traffic. The link backup function is
implemented by the ISDN.
IP
Router Router
Router
GE1/0/0
Serial 2/0/0:15
ISDN Switch ISDN Switch Router
Dialer1
ISDN
The primary link
As shown in Figure 1-5, if RouterA does not have a reachable route to network segment
10.10.10.1/24 where RouterB resides, the dialup interface of RouterA starts the DCC dialing
process to implement link backup.
IP
Router Router
10.10.10.1/24
RouterA RouterB
Dialer1
ISDN Switch
ISDN
ISDN Switch The primary link
As shown in Figure 1-6, a dialing connection has been set up. If no traffic is transmitted between
the PPPoE client and the PPPoE server, the PPPoE client disconnects the PPPoE session. When
the traffic is restored, the PPPoE client sets up the PPPoE session again.
PC
Internet
PC
PPPoE PPPoE
Client Server
NOTE
If a router functions as a PPPoEoA/PPPoA client, the router needs to connect to the PPPoEoA/PPPoA
server through a DSLAM.
Only the RS-DCC mode can be used in this scenario.
1.4 References
None.
2 PPP and MP
Point-to-Point Protocol (PPP) is a link-layer protocol used to transmit point-to-point data over
full-duplex synchronous and asynchronous links.
Purpose
PPP is built upon the Serial Line Internet Protocol (SLIP). SLIP supports only the asynchronous
transfer mode (ATM), transmits only IP packets, and does not support negotiation. Due to these
disadvantages, SLIP is gradually being replaced by PPP.
Introduction to MP
Definition
Multilink PPP (MP) is a technique that binds multiple PPP links together to increase bandwidth
and ensure link reliability.
Purpose
SOCKET
TCP UDP
ICMP
IP
ARP
PPP
Physical Layer
l Flag field
The Flag field identifies the start and end of a physical frame and is always 0x7E.
l Address field
The Address field identifies a peer. Two communicating devices connected by using PPP
do not need to know the data link layer address of each other because PPP is used on P2P
links. This field must be filled with a broadcast address of all 1s and is of no significance
to PPP.
l Control field
The Control field value defaults to 0x03, indicating an unsequenced frame. By default, PPP
does not use sequence numbers or acknowledgement mechanisms to ensure transmission
reliability.
The Address and Control fields identify a PPP packet, so the PPP packet header value is
FF03.
l Protocol field
The Protocol field identifies the datagram encapsulated in the Information field of a PPP
data packet.
The structure of this field complies with the ISO 3309 extension mechanism for address
fields. All Protocol field values must be odd; the least significant bit of the least significant
byte must be "1"; the least significant bit of the most significant byte must be "0".
If a receiver receives a data packet that does not comply with these rules from a sender, the
receiver considers the packet unrecognizable and sends a Protocol-Reject packet padded
with the protocol code of the rejected packet to the sender.
8031 Bridging NC
l Information field
The Information field contains the datagram for the protocol specified in the Protocol field.
The maximum length for the Information field, including the Padding field, is the maximum
receive unit (MRU). The MRU defaults to 1500 bytes and can be negotiated.
In the Information field, the Padding field is optional. If there is the Padding field in the
Information field, two communicating parties can communicate only when they can
identify the padding information and information to be transmitted.
l FCS field
The frame check sequence (FCS) field checks the correctness of PPP packet transmission.
Some mechanisms are used to ensure data packet transmission, increasing the cost and
delay in data exchange at the application layer.
Communicating devices negotiate to establish a PPP link by exchanging LCP packets. The LCP
packets are encrypted in the Information field of a PPP data packet as the payload. The value of
the Protocol field of a PPP data packet is always 0xC021.
During establishment of a PPP link, the Information field is variable and contains various
packets, which need to be identified by corresponding fields.
l Code field
The Code field is 1 byte in length and identifies the LCP packet type.
If a receiver receives an LCP packet with an unknown Code field from a sender, the receiver
sends a Code-Reject packet to the sender.
0x01 Configure-Request
0x02 Configure-Ack
0x03 Configure-Nak
0x04 Configure-Reject
0x05 Terminate-Request
0x06 Terminate-Ack
0x07 Code-Reject
0x08 Protocol-Reject
0x09 Echo-Request
0x0A Echo-Reply
0x0B Discard-Request
0x0C Reserved
l Identifier field
The Identifier field is 1 byte long. It is used to match requests and replies. If a packet with
an invalid Identifier field is received, the packet is discarded.
The sequence number of a Configure-Request packet usually begins with 0x01 and
increases by 1 each time a Configure-Request packet is sent. After a receiver receives a
Configure-Request packet, it must send a reply packet with the same sequence number as
the received Configure-Request packet.
l Length field
The Length field specifies the length of a negotiation packet, including the Code, Identifier,
Length and Data fields.
The Length field specifies the total number of bytes in the negotiation packet.
The Length field value cannot exceed the MRU of the link. Bytes outside the range of the
Length field are treated as padding and are ignored after they are received.
l Data field
The Data field contains the contents of a negotiation packet, including the following fields:
– The Type field specifies the negotiation option type.
– The Length field specifies the total length of the Data field.
– The Data field contains the contents of the negotiation option.
0x01 Maximum-Receive-Unit
0x02 Async-Control-Character-Map
0x03 Authentication-Protocol
0x04 Quality-Protocol
0x05 Magic-Number
0x06 RESERVED
0x07 Protocol-Field-Compression
0x08 Address-and-Control-Field-Compression
SUCCESS/NONE
FAIL FAIL
DOWN CLOSING
Terminate Network
Dead Phase
The physical layer is unavailable during the Dead phase. A PPP link begins and ends with this
phase.
When two communicating devices detect that the physical link between them is activated (for
example, carrier signals are detected on the physical link), PPP enters the Establish phase from
the Dead phase.
Establish Phase
In the Establish phase, the two devices perform an LCP negotiation to negotiate the following
items: working mode (SP or MP), MRU, authentication mode, and magic number. After the LCP
negotiation is complete, PPP enters the next phase.
l When the link is unavailable (in the Dead phase), LCP is in the Initial or Starting state.
When detecting that the link is available, the physical layer sends an Up event to the link
layer. After receiving the Up event, the link layer changes the LCP status to Request-Sent.
Then the devices at both ends send Configure-Request packets to configure a data link.
l If the local device first receives a Configure-Ack packet from the peer, the LCP status
changes from Request-Sent to Ack-Received. After the local device sends a Configure-Ack
packet to the peer, the LCP status changes from Ack-Received to Opened.
l If the local device first sends a Configure-Ack packet to the peer, the LCP status changes
from Request-Sent to Ack-Sent. After the local device receives a Configure-Ack packet
from the peer, the LCP status changes from Ack-Sent to Opened.
l After LCP enters the Opened state, PPP enters the next phase.
The next phase is the Authentication or Network phase, depending on whether authentication is
required.
Authentication Phase
The Authentication phase is optional. By default, PPP does not perform authentication during
PPP link establishment. If authentication is required, the authentication protocol must be
specified in the Establish phase.
PPP authentication is performed on links between hosts and devices that are connected through
PPP network servers, switched circuits or dial-up lines, or on dedicated links.
PPP provides two password authentication modes: PAP authentication and CHAP
authentication.
Two CHAP authentication modes are available: unidirectional CHAP authentication and
bidirectional CHAP authentication. In unidirectional CHAP authentication, the device on one
end functions as the authenticating device, and the device on the other end functions as the
authenticated device. In bidirectional CHAP authentication, each device functions as both the
authenticating device and authenticated device. In practice, only unidirectional CHAP
authentication is used.
PAP is a two-way handshake authentication protocol that transmits passwords in plain text.
Authenticate-Request
Authenticate-Ack
Authenticate-Nak
l The authenticated device sends the local user name and password to the authenticating
device.
l The authenticating device checks whether the received user name is in the local user table.
– If the received user name is in the local user table, the authenticating device checks
whether the received password is correct. If so, the authentication succeeds. If not, the
authentication fails.
– If the received user name is not in the local user table, the authentication fails.
CHAP Authentication Process
CHAP is a three-way handshake authentication protocol. CHAP transmits only user names but
not passwords, so it is more secure than PAP.
Figure 2-5 shows the CHAP authentication process.
Challenge
Success
compares the generated cipher text with that carried in the received Response packet,
and returns a response based on the result of the check.
l When the authenticating device is not configured with a user name:
– The authenticating device initiates an authentication request by sending a Challenge
packet.
– After receiving the Challenge packet, the authenticated device encrypts the Challenge
packet with the packet ID and password configured by the ppp chap password
command by using the Message Digest 5 (MD5) algorithm. Then the authenticated
device sends a Response packet carrying the generated cipher text and local user name
to the authenticating device.
– The authenticating device encrypts the Challenge packet with the saved password of
the authenticated device by using the MD5 algorithm. Then the authenticating device
compares the generated cipher text with that carried in the received Response packet,
and returns a response based on the result of the check.
Comparison Between CHAP and PAP Authentication Processes
l In PAP authentication, passwords are sent over links in plain text. After a PPP link is
established, the authenticated device repeatedly sends the user name and password until
authentication finishes. This mode cannot ensure high security, so it is used on networks
that do not require high security.
l CHAP is a three-way handshake authentication protocol. In CHAP authentication, the
authenticated device sends only the user name to the authenticating device. Compared with
PAP, CHAP features higher security because passwords are not transmitted. On networks
requiring high security, CHAP authentication is used to establish a PPP connection.
Network Phase
In the Network phase, NCP negotiation is performed to select and configure a network protocol
and to negotiate network-layer parameters. Each NCP may be in Opened or Closed state at any
time. After an NCP enters the Opened state, network-layer data can be transmitted over the PPP
link.
Termination Phase
PPP can terminate a link at any time. A link can be terminated manually by an administrator, or
be terminated due to the loss of carrier, an authentication failure, or other causes.
2.3 Principles of MP
Implementation
MP is implemented by binding multiple PPP links to an MP link. The following table lists the
MP implementation types and principles.
Using a virtual Binding PPP links to Multiple interfaces are bound to a VT.
template (VT) a VT Authentication is optional.
l If authentication is configured, interface binding
takes effect only after the interfaces are
authenticated.
l If no authentication is configured, interface
binding takes effect only after the LCP status of
the interfaces becomes Up.
Searching for a VT The system searches for the bound VT using the
using the user name authenticated remote user name. Links with the
of the PPP link same user name are bound to the same VT. This
implementation subtype requires PPP
authentication. Binding takes effect only after the
interfaces are authenticated.
In a VT, you can differentiate virtual access (VA) interfaces by the MP binding condition:
l If the MP binding condition is authentication, links with the same remote user are bound
to the same VA interface.
l If the MP binding condition is descriptor, links with the same remote endpoint
discriminator are bound to the same VA interface.
l If the MP binding condition is both, links with the same remote user and the same remote
endpoint discriminator are bound to the same VA interface.
LFI
On low-speed serial links, real-time interactive communication such as Telnet and VoIP is often
delayed due to transmission of oversized packets. For example, a voice packet arrives when an
oversized packet is being scheduled. The voice packet can be scheduled only after the oversized
packet is transmitted, which deteriorates the voice communication quality.
The interactive voice communication requires that the end-to-end delay should be less than or
equal to 150 ms. If it takes 215 ms to transmit a 1500-byte packet over a 56 kbit/s link, this is
unacceptable. To shorten the delay in transmitting packets of a real-time application on low-
speed links, a method is required to fragment oversized packets and place fragmented packets
in the same queues as other packets.
Link fragmentation and interleaving (LFI) fragments oversized packets. Then the fragmented
packets are sent together with other packets. In this manner, the delay and jitter on a low-speed
link are reduced. The fragmented packets are reassembled at the destination.
Figure 2-6 shows the LFI process. When oversized packets and small voice packets arrive at an
interface simultaneously, the oversized packets are fragmented. If weighted fair queuing (WFQ)
is configured on the interface, the voice packets and the fragmented packets are placed into the
WFQ queues in interleaving mode.
Oversized packets
Queue
2.4 Applications
2.4.1 PPP
When a router functions as the enterprise egress gateway, the LAN-side interface connects to a
host on the intranet and the WAN-side interface connects to a carrier's device. The carrier's
device can be a digital subscriber line access multiplexer (DSLAM), an optical line terminal
(OLT), or a wireless base station, depending on the WAN-side interface type.
l RouterA connects to the WAN-side interface of RouterB using a PPP link. RouterA obtains
the IP address allocated by a carrier's device, through IPCP negotiation in the PPP link
establishment process, and connects to the WAN. PPP links are widely used for
communication between enterprise branches and the headquarters.
l PPP can be used with other technologies to provide various services. The services supported
by a router include PPPoE, PPP over ATM (PPPoA), PPP over Ethernet over ATM
(PPPoEoA), PPP over frame relay (PPPoFR), and PPP over Integrated Services Digital
Network (PPPoISDN).
2.4.2 MP
When high bandwidth is required, a single PPP link cannot provide sufficient bandwidth. To
increase link bandwidth and reliability, bind multiple PPP links into an MP link.
As shown in Figure 2-8, there are three PPP links between RouterA and RouterB. The three
PPP links can be bound into an MP link. The MP link provides higher speed and bandwidth.
When one PPP link fails, communication over the other links are normal.
RouterA RouterB
2.5 References
The following table lists the references of this document.
3 PPPoE
Purpose
Carriers want to connect multiple hosts at a site to the same remote access device. The access
device is expected to provide access control and accounting for these hosts in a manner similar
to dial-up access using PPP. Using PPPoE, carriers can achieve this goal at lower cost because
Ethernet is the most cost-effective among all access technologies and PPP implements access
control and accounting.
PPPoE allows a large number of hosts on an Ethernet to connect to the Internet using a remote
access device and controls each host using PPP. PPPoE features a large application scale, high
security, and convenient accounting.
The PPPoE technology implements practical applications such as Internet access accounting and
is widely used by broadband access carriers.
3.2 Principles
l Figure 3-2 shows the second PPPoE network structure. In the network, a PPPoE session
is established between the carrier's router and each host. The router functions as the PPPoE
server, and each host functions as a PPPoE client. Each host has a unique account, which
facilitates user accounting and control by the carrier. The PPPoE client software must be
installed on the hosts.
PPPoE Client
Host 1
PPPoE Server
PPPoE Client
Internet
Host 2
Router
PPPoE Client
Host n
VER(0x01)
Destination_Address Type(0x01)
( 48 bits ) Code
( 8 bits )
Source_Address Session_ID
( 48 bits ) ( 16 bits )
Ethernet_Type
( 16 bits )
Length
( 16 bits ) Tag_Type
Payload
CheckSum Tag_Length
Payload
Ethernet Tag_Value......
PPPoE
PPP
The value is fixed for a given PPPoE session and defines a PPPoE session along with
Ethernet Source_address and Destination_address.
The value 0xFFFF is reserved.
l Length: indicates the length of the PPPoE payload. This field is 16 bits in length. It does
not include the length of the Ethernet or PPPoE packet header.
l Tag_Type: indicates the network byte order. This field is 16 bits in length.
l Tag_Length: indicates the number of bytes of the Tag_Value field. It is an unsigned number
in network byte order. This field is 16 bits in length.
l Checksum: checks the validity of packets.
PADI
PADO
Discovery PADR
PADS
PPP negotiation
Session
Data transmission
PADT
Terminate
The PPPoE session establishment process includes three stages: Discovery, Session, and
Terminate.
Discovery Stage
The Discovery stage consists of the following steps:
1. A PPPoE client broadcasts a PADI packet that contains service information required by
the PPPoE client.
2. After receiving the PADI packet, all PPPoE servers compare the requested service with the
services they can provide. The PPPoE servers that can provide the requested service unicast
PADO packets to the PPPoE client.
3. Based on the network topology, the PPPoE client may receive PADO packets from more
than one PPPoE server. The PPPoE client selects the PPPoE server from which the first
PADO packet is received and unicasts a PADR packet to the PPPoE server.
4. The PPPoE server generates a unique session ID to identify the PPPoE session with the
PPPoE client. The PPPoE server sends a PADS packet containing this session ID to the
PPPoE client. When the PPPoE session is established, the PPPoE server and PPPoE client
enter the PPPoE Session stage.
When the PPPoE session is established, the PPPoE server and PPPoE client share the unique
PPPoE session ID and learns the peer Ethernet address.
Session Stage
The PPPoE Session stage involves PPP negotiation and PPP packet transmission.
PPP negotiation at the PPPoE Session stage is the same as common PPP negotiation, which
includes the LCP, authentication, and NCP phases.
1. In the LCP phase, the PPPoE server and PPPoE client establish and configure a data link,
and verify the data link status.
2. When LCP negotiation is complete, authentication starts. The authentication protocol
depends on the LCP negotiation result. The authentication protocol can be Challenge
Handshake Authentication Protocol (CHAP) or Password Authentication Protocol (PAP).
3. When authentication succeeds, PPP enters the Network Control Protocol (NCP) phase.
NCP is a protocol suite used to configure network–layer protocols. A commonly used
network-layer protocol is IP Control Protocol (IPCP), which is responsible for configuring
IP addresses for users and the domain name server (DNS).
When PPP negotiation succeeds, PPP data packets can be forwarded.
At the PPPoE Session Stage, the PPPoE server and PPPoE client unicast all Ethernet data
packets.
Terminate Stage
The PPPoE server and PPPoE client use PPP protocol packets to terminate the PPPoE session.
When the PPP protocol packets are unavailable, PPP communicating parties can use PADT
packets to terminate the PPPoE session.
After a PPPoE session is established, the PPPoE client or the PPPoE server can unicast a PADT
packet to terminate the PPPoE session at any time. After transmitting or receiving the PADT
packet, the PPPoE server and PPPoE client is not allowed to use this session to send any PPP
traffic.
Discovery Stage
PPPoE Active Discovery Initiation (PADI) packet
0 15 19 23 31
0xFFFFFFFF
0xFFFF Host_MAC_address
Host_MAC_address ( Continue )
Ethernet_Type ( 0x8863 ) V=1 T=1 Code ( 0x09 )
Session_ID ( 0x0000 ) Length ( 0x0004 )
Tag_Type ( 0x0101 ) Tag_Length ( 0x0000 )
0 15 19 23 31
Host_MAC_address
Host_MAC_address ( Continue ) Access_Concentrator_MAC_address
Access_Concentrator_MAC_address ( Continue )
Ethernet_Type ( 0x8863 ) V=1 T=1 Code ( 0x07 )
Session_ID ( 0x0000 ) Length ( 0x0020 )
Tag_Type ( 0x0101 ) Tag_Length ( 0x0000 )
Tag_Type ( 0x0102 ) Tag_Length ( 0x0018 )
Session Stage
l The Ethernet_Type field is set to 0x8864.
l The Code field is set to 0x00.
l The value of the Session_ID field must be that specified at the Discovery stage.
l The Tag_Type field contains a PPP frame with the first field being PPP Protocol-ID.
0 15 19 23 31
Access_Concentrator_MAC_address
Access_Concentrator_MAC_address
Host_MAC_address
( Continue )
Host_MAC_address ( Continue )
Ethernet_Type ( 0x8864 ) V=1 T=1 Code ( 0x00 )
Session_ID ( 0x0001 ) Length ( 0x???? )
PPP Protocol ( 0xC021 ) PPP Payload
Terminate Stage
PPPoE Active Discovery Terminate (PADT) packet
0 15 19 23 31
Host_MAC_address
Host_MAC_address ( Continue ) Access_Concentrator_MAC_address
Access_Concentrator_MAC_address ( Continue )
Ethernet_Type ( 0x8863 ) V=1 T=1 Code ( 0xa7 )
Session_ID ( 0x0001 ) Length ( 0x0000 )
3.3 Applications
l Router A functions as a PPPoE client and accesses the Internet using one account (that is,
enterprise users use this account to access the Internet).
l Router B functions as a PPPoE server. It is connected to a digital subscriber line access
multiplexer (DSLAM) to provide RADIUS authentication and accounting functions. Users
can access the Internet using RouterB.
Figure 3-11 Networking diagram for connecting a LAN to the Internet using an ADSL modem
PPPoE Server
Router Internet
AP AP AP AP
PPPoE Client
3.4 References
The following table lists the references of this document.
4 LTE
LTE is improvement over 3G technology, but not equal to 4G technology. LTE is a transition
from 3G to 4G technology. Compared with 3G technology, LTE has the following technical
advantages:
l Higher data transmission rate: LTE provides a downstream peak rate of 100 Mbit/s and an
upstream peak rate of 50 Mbit/s over a 20 MHz bandwidth.
l Improved spectrum efficiency.
l Increased network deployment flexibility: LTE supports bandwidth ranging from 1.25
MHz to 20 MHz.
l QoS guarantee: The LTE system design and strict QoS mechanism ensures better QoS for
delay-sensitive services such as voice over Internet Protocol (VoIP).
l Shorter delay on wireless networks.
l Higher cell edge bit rate: The high bit rate delivers higher performance for users located
on the cell edge.
l Backward compatible: LTE offers compatibility between the existing 3G system and
non-3GPP systems.
Purpose
LTE technology deployed on routers provides wireless access and interconnection for enterprise
branches or small- and medium-sized enterprises. Compared with 3G technology, LTE
technology provides higher bandwidth on wireless WAN links to transmit more voice, data, and
video services for enterprise users.
Enterprises can use LTE technology to replace or back up wired WAN links such as Ethernet,
digital subscriber line (DSL), frame relay (FR), and integrated services digital network (ISDN)
links. LTE allows flexible, efficient, and fast network deployment, and provides a backup for
wired WAN links on an enterprise network.
Benefits
LTE technology brings users the following benefits:
l Wired WAN link backup: LTE technology backs up wired links such as Ethernet and DSL,
ensuring uninterrupted services if the wired links fail.
l Flexible, efficient, and fast network deployment: LTE technology provides service
coverage even in remote areas and mobile office scenarios.
l Secure virtual private network (VPN) access: An enterprise branch can set up a tunnel with
the enterprise headquarters on LTE links using VPN technologies, such as Generic Routing
Encapsulation (GRE), Layer 2 Tunneling Protocol (L2TP), or Internet Protocol Security
(IPSec) VPN. This tunnel allows the enterprise branch to communicate with the
headquarters in a fast, secure, and efficient way.
l Data services and multimedia services: LTE allows a router to connect to different gateways
using different access point names (APNs). For example, the router can use one APN to
access the Internet, and another APN to access the IP multimedia subsystem (IMS). QoS
settings on the router can be configured to control the quality of data and multimedia
services on the router.
Limitations
Due to limitations in wireless transmission, LTE may be limited in terms of throughput, delay,
and customer requirements:
l Throughput: varies depending on the number of active users and network congestion. This
is a common limitation of wireless networks.
l Delay: varies depending on the quality of network services provided by carriers and may
increase due to network congestion. Compared with wired networks, wireless networks
may cause longer delays.
l Carriers may pose other limitations on LTE.
4.2 Principles
Serving PDN IP
Gateway Gateway Network
SGSN
UE
Router
NE Description
NE Description
l USB data card (LTE modem): inserted in the USB interface on the SRU.
l LTE interface card: integrates the LTE modem function and is installed in a slot on the
router.
NOTE
Install a SIM card on an LTE modem or interface card before using the LTE feature.
LTE is classified into time division LTE (TD-LTE) and frequency division duplex LTE (FDD-
LTE). Currently, LTE modems and LTE interface cards for the router support only the FDD-
LTE network.
Table 4-3 lists the frequency bands and rates supported by an LTE interface card (LTE-H).
Table 4-3 Frequency bands and rates supported by an LTE interface card
Attribute Description
Rates l GSM CS: upstream 14.4 kbit/s and downstream 14.4 kbit/s
l GPRS: upstream 85.6 kbit/s and downstream 85.6 kbit/s
l EDGE: upstream 236.8 kbit/s and downstream 236.8 kbit/s
l WCDMA CS: upstream 64 kbit/s and downstream 64 kbit/s
l WCDMA PS: upstream 384 kbit/s and downstream 384 kbit/s
l HSPA+: upstream 5.76 Mbit/s and downstream 21.6 Mbit/s
l DC-HSPA+: upstream 5.76 Mbit/s and downstream 42 Mbit/s
l LTE FDD: upstream 50 Mbit/s and downstream 100 Mbit/s
Table 4-4 lists the frequency bands and rates supported by a USB data card (E392).
Table 4-4 Frequency bands and rates supported by a USB data card
Attribute Description
As shown in Figure 4-2, when data needs to be transmitted or the dial-up timer expires, the
router uses C-DCC to initiate a dial-up on a cellular interface and enables the LTE modem to
connect to the PGW.
PGW
DCC Cellular LTE
interface modem
Connection setup request Connection setup request
Step 1 (with identity information)
Step 2
Set up the connection and
assign an IP address
Instruct cellular interface Step 3
Step 4 to go Up physically
1. When data needs to be transmitted or the dial-up timer expires, the router uses C-DCC to
initiate a dial-up on a cellular interface. The cellular interface sends a connection setup
request message to the LTE modem.
2. The LTE modem sends a connection setup request message to the PGW. The message
contains user authentication information including the access point name (APN), user
name, and password.
3. The PGW authenticates the user identity. After authentication succeeds, the PGW sets up
a connection with the LTE modem and assigns an IP address to the LTE modem.
4. The LTE modem instructs the cellular interface to go Up physically.
5. The cellular interface negotiates with the LTE modem to obtain an IP address.
6. The cellular interface sets up a connection with the PGW and forwards data services.
4.2.4 APN
Definition
An access point name (APN) identifies an external packet data network (PDN) that a user needs
to access. Users connect to a PDN using the APN of the PDN. As shown in Figure 4-3, a router
can connect to the carrier's PDN and the enterprise's gateway using the APNs configured for the
carrier and enterprise. For example, APN1 is used to access the IMS network, and APN2 is used
access the enterprise data gateway.
Branch Carrier
IMS
Analog phone network gateway
APN1
Router
Fax LTE core Internet
network gateway
eNodeB
APN2
IP phone LSW
Headquarters
Enterprise Enterprise
IMS gateway data gateway
PC1 PC2
LTE Multi-APN
In Figure 4-4, the LTE-H interface card on the router supports two APNs that share the same
cellular interface. You need to bind each APN to a cellular channel interface configured on the
cellular interface. Each cellular channel interface is a logical service interface that has its own
IP address, DCC dial-up configuration, and services (such as voice, data, and VPN).
LTE core
network
Router eNodeB
APN2 for voice IMS
IMS网关
gateway
The two APNs share uplink bandwidth on the cellular interface. QoS must be configured to
schedule services of the APNs. For example, if one APN is used to transmit voice services and
the other APN is used to transmit data services, voice services must be transmitted with a higher
priority. QoS parameters must be configured on the cellular interface to ensure that voice services
are preferentially scheduled.
4.3 Applications
DSL link
Branch Headquarters
Router DSLAM
LTE link
LTE
network
Primary link
Backup link
In Figure 4-6, an enterprise branch has two LTE links to connect to the headquarters. LTE link
1 is the primary link and connects to LTE network 1 of Carrier A. LTE link 2 is the backup link
and connects to LTE network 2 of Carrier B. If the primary link fails, traffic is immediately
switched to the backup LTE link, enhancing reliability of Internet access from the enterprise
branch.
Headquarters
Branch
Router
LTE
LTE link 2
network 2 Primary link
Backup link
LTE link
In Figure 4-8, an enterprise branch dials up to the Internet through an LTE link and sets up an
IPSec VPN tunnel with the headquarters. The tunnel protects traffic between the enterprise
branch and the headquarters.
Figure 4-8 Communication between the enterprise branch and the headquarters using an IPSec
VPN tunnel
LTE link
Branch LTE Headquarters
network
Router
IPSec tunnel
Internet
Branch LTE Headquarters
PGW
network
Router IMS
network
IMS
gateway
Data communication
VoIP communication
4.4 References
The following table lists the references for this document.
5 ATM
5.1 Introduction
5.2 Principles
5.3 Application
5.4 Reference
5.1 Introduction
Definition
ATM was designated as the transmission and switching mode for Broadband Integrated Services
Digital Networks (B-ISDN) by the ITU-T in June 1992. Due to its high flexibility and support
to the multi-media service, ATM is considered as the key for realizing broadband
communications.
Defined by the ITU-T, ATM implements transmission, multiplexing, and switching of data based
on cells. ATM is a cell-based and connection-oriented multiplexing and switching technology.
An ATM cell has a fixed length of 53 bytes. As defined by the ITU-T, ATM transmits,
multiplexes, and switches data based on cells. For example, the messages of voice, video, and
data are all transmitted in the cells of the fixed length. This ensures the fast data transmission.
Purpose
ATM provides the network with a versatile and connection-oriented transfer mode that applies
to different services.
Before the Gigabit Ethernet technology, ATM backbone switches were mostly used on backbone
networks to ensure high bandwidth. ATM dominated among network technologies because it
can provide good QoS and transmit voice, data, and video with high bandwidth.
Nevertheless, the initial roadmap for ATM, that is, coping with all the network communication
issues, was too ambitious and idealistic. As a result, the ATM implementation became so
complicated. The aim of the ATM technology is too ideal. The realization of ATM is complex.
The perfection of the ATM technology and complexity of its architecture result in the difficulties
of developing, configuring, managing, and troubleshooting the ATM system.
ATM network devices are quite expensive. The ATM network cannot be affordable for people
and its excellent performance is unknown from the origin of ATM.
In the late 1990's, Internet and IP technology overshadowed ATM for their simplicity and
flexibility. They developed at a fast rate in the application field. This made a severe impact on
the B-ISDN plan.
ATM is, however, still regarded as the best transmission technology of B-ISDN because it has
advantages in transporting integrated services. Thus, the IP technology integrated with ATM.
This brought about the new era of constructing broadband networks through the integration of
the IP and ATM technologies.
5.2 Principles
5.2.1 ATM Protocol Architecture
Management
plane
Control User
Plane management
plane plane
Layer management
Upper layer Upper layer
protocols protocols
ATM adaptation
layer
ATM layer
Physical
layer
l Control plane: This plane generates and manages signaling requests. It sets up, monitors,
and removes connections by using signaling protocols.
l User plane: This plane manages data transmission.
l Management plane: This plane is divided into layer management and plane management.
– Layer management: It is responsible for the management of every layer in each plane.
It has a layered structure corresponding to other planes.
– Plane management: It is responsible for the system management and the
communications between different planes.
l Physical layer: Similar to the physical layer of the OSI reference model, the physical layer
manages the transmission related to the medium.
l ATM layer: It integrates with the ATM adaptation layer (AAL) and is similar to the data
link layer of the OSI reference model. The ATM layer is responsible for sharing virtual
circuits on the physical link and transmitting ATM cells on the ATM network.
l AAL: It integrates with the ATM layer and is similar to the data link layer of the OSI
reference model. AAL is mainly responsible for isolating the upper-layer protocols from
the ATM layer. It prepares the switchover from the service data to cells, and divides the
data into a 48-byte cell payload.
l Upper layer: It receives service data, divides it into packets, and transmits it to AAL for
processing.
The comparison between the ATM protocol architecture and the OSI reference model is shown
in Figure 5-2.
Figure 5-2 Comparison between the ATM protocol architecture and the OSI reference model
ATM Model OSI Reference Model
Table 5-1 Functions of layers and sub-layers in the ATM reference model
Layers of the ATM Sub-layers of the ATM Function
Reference Model Reference Model
The detailed functions of layers and sub-layers in the ATM reference model are described in the
following sections.
The device provides ADSL-A/M and ADSL-B boards. Only ADSL-A/M boards support this
standard.
Figure 5-3 ATM network interfaces of the private and public networks
Public ATM
Public ATM networkB
Dedicated Public B-ICI
networkA
ATM network UNI
Public
Dedicated NNI Dedicated
NNI Dedicated UNI
UNI
Dedicated
UNI
NOTE
On the device, only user-to-network interfaces are used as ATM network interfaces.
VPI is used to identify the virtual path (VP) number of the virtual circuit connection (VCC).
VCI is used to identify the VC number of the VP. The combination of VPI and VCI comprises
the connection identifier.
As shown in Figure 5-4, a VCC contains multiple VPs, and a VP contains multiple VCs.
VP VC
VP VC
VP VC
Physical
channel VCC
VP VC
VP VC
VP VC
The VP is used to adapt to high-speed networks in which network control cost is increasing. The
VP technology reduces the control cost by binding the connections of the same paths on a shared
network into a unit. By doing so, the network management can only process lesser number of
connections, instead of a larger number of independent connections.
In the ATM communication, an ATM switch transmits the received cells to the output interface
according to the VPI/VCI of the input cells and the forwarding table that is generated during the
setup of a connection. At the same time, this ATM switch changes the VPI/VCI of a cell into
that of an outgoing interface to complete the VP switching or VC switching.
ATM VCs are of the following types: permanent virtual circuit (PVC), switching virtual circuit
(SVC), and soft virtual circuit (soft VC).
l The PVC is statically configured by the administrator. Once it is set up, it cannot be
removed. PVC applies to connections for advanced requirements.
l The SVC is set up through the signaling protocol. It can be connected and removed through
commands.
When a node receives the connection request from other nodes, the connection response
information needs to be sent to this node if configuration requirements are satisfied. After
the connection is set up, the connection request is sent to the next target node.
The removing process is similar to the setting up of the connection.
l Soft VC indicates that the ATM network is based on SVC, but peripheral devices access
the ATM network in PVC mode.
The setting up of soft VCs is similar to that of SVCs. The only difference is that PVCs must
be manually configured between ATM switch interfaces and peripheral devices.
The advantage of this mode is that it is easy to manage users if PVCs are connected to the
users. In addition, SVCs can ensure the proper usage of the links.
ATM Network
PVC PVC
SVC
Soft VC
The NNI cell header is used for communication between two switching nodes.
Figure 5-7 shows the NNI cell header format.
l GFC: indicates the general flow control with a length of 4 bits. It applies to the UNI
interfaces only. It performs flow control, and identifies different accesses on a shared media
network.
l VPI: indicates the virtual path identifier. In the UNI, it can identify 256 VPs and its length
is 8 bits. In the NNI, it can identify 4096 VPs and its length is 12 bits.
l VCI: indicates the virtual channel identifier. It can identify 65536 VCs and its length is 16
bits.
l CLP: indicates the cell loss priority. It is used for congestion control and its length is 1 bit.
When congestion occurs, cells with the CLP as 1 are discarded first.
l PTI: indicates the payload type indicator. It identifies the payload type and its length is 3
bits.
l HEC: indicates the header error control. It is used for error control and cell delimitation in
a cell header and its length is 8 bits. HEC can correct 1-bit error, find multi-bit error, and
perform HEC on the physical layer.
Some specified VPI/VCI values are reserved for special cells. These special cells are described
as follows:
l Idle cell: Its VPI is 0, VCI is 0, PTI is 0, and CLP is 1. It is used for rate adaptation.
l Unassigned cell: Its VPI is 0, VCI is 0, PTI can be any value, and CLP is 1.
l OAM cell: For the VP sub-layer, its VCI is 3 and it is used for the VP link. When VCI is
4, it is used for the VP connection. For the VC sub-layer, it is used for the VC link when
PTI is 4. When PTI is 5, it is used for the VC connection.
l Signaling cell: It is divided into the following types:
– Component signaling cell: Its VPI can be any value, and VCI is 1.
– General broadcast signaling cell: Its VPI can be any value, and VCI is 2.
– Point-to-point (P2P) signaling cell: Its VPI can be any value, and VCI is 5.
l Payload type: Its length is 3 bits. It is used to identify the information field, that is, the
payload type. The following lists the PT values and corresponding meanings defined by
the ITU-T I.361.
– PT = 000: indicates that the service data cell does not experience congestion and ATM
user to user (AUU) is 0.
– PT = 001: indicates that the service data cell does not experience congestion and AUU
is 1.
– PT = 010: indicates that the service data cell experiences congestion and AUU is 0.
– PT = 011: indicates that the service data cell experiences congestion and AUU is 1.
– PT = 100: indicates the cells related to the OAM F5 segment.
– PT = 101: indicates the OAM F5 end-to-end cells.
– PT = 110: indicates the resource management cells.
– PT = 111: This PT is for future use.
l The second bit identifies whether cells experience congestion and can be set through the
network node when there is congestion.
l The third bit is an AUU indicator. AUU = 0 indicates that the corresponding SAR-PDU is
the beginning segment or intermediate segment. AUU = 1 indicates that SAR-PDU is the
ending segment.
ATM OAM
ATM Operation, Administration and Maintenance (OAM) provides a mechanism to detect and
locate faults and verify network performance without interrupting services. Broadband-
Integrated Services Digital Network (ITU-T B-ISDN) I.610 defines the OAM function on the
ATM network and classifies the OAM function into the following five layers.
F1: Regenerator section layer Physical layer OAM: The OAM flow
depends on the concrete mechanism of the
F2: Digit section layer transmission system. The ATM network
F3: Transmission channel layer includes the following three types of
transmission systems:
l Transmission system based on SDH
(defined in G.707 and G.783)
l Transmission system based on cell
(defined in I.432.1, I.432.2, and I.432.4)
l Transmission system based on PDH
(defined in G.702, G.804 and G.832)
F4: Virtual path layer ATM layer OAM: based on VP/VC and does
not depend on the transmission system.
F5: Virtual channel layer
The two types of operation flows are defined in the ATM layer: F4 and F5.
l F4 flow is the OAM cell flow in the Virtual Path Connect (VPC) and provides the operation
management and maintenance of the VP layer.
l F5 flow is the Virtual Channel Connect (VCC) and provides the operation management
and maintenance of the VC layer.
After the OAM is activated in the F4 and F5 flows, the specified OAM cells are inserted into
the user cells to occupy certain bandwidth and to be transmitted in the same physical channel
with the cells of the other users.
The F4 and F5 flows support four types of OAM cells: FM OAM cell, PM OAM cell, active/
deactive OAM cell, and SM OAM cell, as shown in Table 5-3.
FM (Fault Management) AIS (reports the errors to The FM OAM cell is uses to
downstream) detect and locate the faults of
in-service which is real-time
RDI (reports the errors to and consecutive.
upstream)
CC (continuity detection)
BM (backward performance
monitoring)
Deactive PM (deactive
performance monitoring)
Deactive CC (deactive
continuity detection)
SM (System Management) Can only be used by the The SM OAM cell is used to
terminal system. maintain and control the
different functions among the
terminal devices and can only
exist in the end-to-end F4/F5.
On the ATM network, three types of the OAM functional nodes are as follows:
l End point
The end point is defined as the point connecting the ATM network and usually refers to
the border of the ATM network. The end points are the termination points of all the OAM
cells and cannot send the OAM cells backwards. If the end points detect that the link is
faulty, they do not insert the OAM cells into the downstream node but insert the end Remote
Defect Indication (RDI) cells into the upstream nodes and notify the upstream nodes that
the upstream link is faulty.
l Segment point
The segment point is defined in I.610. One ATM link may consist of many segments. The
segment points can terminate all the segment cells but not the end cells. If the segment
points detect that the link is faulty, they insert the end Alarm Indication Signal (AIS) cells
into the downstream nodes and the segment RDI cells into the upstream nodes.
l Middle point
The middle point is in between the two segment points or the two end points, so it can be
classified into two types: end middle point and segment middle point. The middle points
do not terminate any cells, and the segment cells and end cells can be transmitted
transparently. If the middle points detect that the link is faulty, they send the segment AIS
cells and end AIS cells to the downstream nodes.
The device supports F5 OAM and FM OAM cells. When the device implements OAM, it
functions only as an end point.
AAL lies on top of the ATM layers and corresponds to the data link layer of the OSI reference
model.
AAL Type
Currently,Currently, four types of AAL are available: AAL1, AAL2, AAL3/4, and AAL5. Each
type supports certain specified services on the ATM network. Products produced by most ATM
equipment manufacturers widely adopt AAL5 to support data communication service.
NOTE
The device supports only AAL5.
l AAL1
AAL1 is used for constant bit rate (CBR), sending data at a fixed interval.
AAL1 uses one part of the 48-byte payload to bear additional information, such as sequence
number (SN) and sequence number protection (SNP). SN contains 1-bit convergence sub-
layer identifier and 3-bit sequence counting (SC). CSI is also used for timing.
l AAL2
Compared with AAL1, AAL2 can transmit compressed voice and realize common channel
signaling (CCS) inside ISDN.
Details on AAL2 are defined in ITU-T 363.2.
AAL2 supports the processing of compressed voice at the upper limit rate of 5.3 Kbit/s.
This realizes silence detection, suppression, elimination, and CCS. In addition, higher
bandwidth utilization is available. Segments can be encapsulated into one or multiple ATM
cells.
CS of AAL2 can be divided into CPCS and SSCS. SSCS is on top of CPCS. The basic
structure of AAL2 users can be recognized through CPCS. Error check, data encapsulation,
and payload breakdown can be performed.
AAL2 allows payloads of variable length to exist in one or multiple ATM cells.
l AAL3/4
As the first technology trying to realize cell delay, AAL3/4 stipulates the connection-
oriented and connectionless data transmission.
CPCS is used to detect and process errors, identify the CPCS-service data unit (SDU) to
be transmitted, and determine the length of the CPCS-packet data unit (PDU).
l AAL5
AAL5 can also process connection-oriented and connectionless data. AAL5 is called the
simple and valid adaptation layer. It uses 48 bytes to load the payload information. AAL5
does not use the additional information bit. It contains no sequence number and cannot
detect errors.
AAL5 SAR sub-layer is simple. It divides CPCS-PDUs into 48-byte SAR-PDUs without
any overhead and realizes the reverse function when receiving data.
The CPCS-PDU format of AAL5 CPCS is shown in Figure 5-8.
The length of the CPCS-PDU payload is variable and ranges from 1 to 65535 bytes.
As shown in Figure 5-8, no CPCS-PDU header exists. A CPCS-PDU tail, however,
occupies eight bytes. The meaning of each field in Figure 5-8 is as follows:
– PAD: indicates the stuffing bit, making the CPCS-PDU length as the integer multiple
of 48-byte payload.
– UU: is used for transparent transmission of CPCS user information.
– CPI: is used to change the CPCS-PDU tail so that it is 8 bytes.
– L: indicates the payload length of CPCS-PDU.
– CRC: protects CPCS-PDU
SSCS of AAL5 CS is similar to AAL3/4. CPCS is also shared by upper layers. CPCS
performs error detection, processes errors, fills bytes to form 48-byte payloads, and discards
the received incomplete CPCS-PDU.
l Logical Link Control (LLC)/Sub-Network Attachment Point (SNAP), which is the default
encapsulation technology adopted in the RFC 2684
l LLC/SNAP allows multiprotocol multiplexing on a single ATM virtual circuit (AC). The
type of the protocol carrying the PDU is identified by the LLC header of the IEEE 802.2
standard that is added to the PDU.
l VC multiplexing
l VC multiplexing ensures the carrying of high-layer protocols on ATM VCs. Each protocol
is carried on a distinct ATM VC.
LLC/SNAP Encapsulation
LLC encapsulation is needed when several protocols are carried over the same VC. To ensure
that the receiver properly processes the received AAL5 CPCS-PDU packets, the payload field
must contain information necessary to identify the protocol of the routed or bridged PDU. In
LLC encapsulation, this information is encoded in an LLC header placed in front of the carried
PDU.
There are two types of LLC:
l LLC type 1: Unacknowledged connectionless mode
l LLC type 2: Connection-mode
Unless otherwise specified, LLC in this document refers to LLC type 1. The application of LLC
type 2 is similar to that of LLC type 1.
l LLC Encapsulation for Routed Protocols
In LLC encapsulation, the protocol of a routed PDU is identified by prefixing the PDU by
an IEEE 802.2 LLC header. As shown in Figure 5-10, an LLC header consists of three
fields with the length of 1 byte.
LLC 0xFE-FE-03
ISO PDU
PAD
CPCS-UU
CPI
Length
CRC
– The organizationally unique identifier (OUI) is 3 bytes in length. The OUI identifies an
organization that administers the meaning of the following Protocol Identifier (PID).
The OUI value 0x00-00-00 indicates that the PID is an Ethernet type.
– The PID is 2 bytes in length.
An SNAP header thus identifies a unique routed or bridged protocol.
For routed non-ISO PDUs, the format of an AAL5 CPCS-PDU payload is shown in Figure
5-13, in which the field indicating that the Ethernet type is 2 bytes in length.
LLC 0xAA-AA-03
OUI 0x00-00-00
EtherType 0x08-00
Non-ISO PDU
PAD
CPCS-UU
CPI
Length
CRC
In the detailed format of an IPv4 PDU, the Ethernet type value is 0x08-00. Figure 5-14
shows the format of the IP PDU.
LLC 0xAA-AA-03
OUI 0x00-00-00
EtherType
Non-ISO PDU
PAD
CPCS-UU
CPI
Length
CRC
Currently, the bridged media type is specified by the 2-byte PID. In addition, the PID
indicates whether the original frame check sequence (FCS) is preserved within the bridged
PDU.
Table 5-4 lists the media type values that are used in the ATM encapsulation.
- 0x00-0D Fragments
- 0x00-0E BPDUs
The AAL5 CPCS-PDU Payload field carrying a bridged PDU must have one of the
following formats.
It is required to add padding after the PID field to align the user information field of the
Ethernet and 802.3.
The sequence of a MAC address must be the same as that in the LAN or MAN.
Padding is added to ensure that the length of a frame on the Ethernet/802.3 physical layer
reaches the minimum value. Padding must be added when bridged Ethernet/802.3 PDU
encapsulation with the LAN FCS is used. Otherwise, you do not need to add padding.
When frames without the LAN FCS are received, the bridge must add some padding to the
frames before forwarding the frames to an Ethernet/802.3 subnet.
VC Multiplexing
In the multiplexing technologies based on the VC, the VC between two ATM sites is used to
differentiate the protocols that carry network interconnection. That is, each protocol must be
carried over each VC.
Thus, no additional multiplexing information is contained on the payload of each AAL5 CPCS-
PDU. This can save bandwidth and reduce the processing cost.
l VC Multiplexing for Routed Protocols
In VC multiplexing for routed protocols, the Payload field of an AAL5 CPCS-PDU contains
only the routed PDU packet. The format of the PDU packet is shown in Figure 5-16.
...
Carried PDU
(up to 2^16 - 1 octets)
...
Since the PID field is not contained in a bridged Ethernet/802.3 PDU packet, the VC
determines the LAN FCS. PDUs in the same bridged medium can carry different protocols
regardless of whether the PDUs contain the LAN FCS.
CBR
The CBR service class is designed for connections requiring a static amount of bandwidth that
is continuously available during the lifetime of the connections. The amount of bandwidth is
determined by the peak cell rate (PCR). The source end configured with the CBR service class
can send cells at the PCR at any time.
The CBR service class is usually used to support real-time services requiring low delay, such as
voice and video services.
VBR-RT
The VBR-RT service class is used for real-time applications requiring low delay and jitter, such
as voice and video services.
The VBR-RT is determined by the PCR, sustainable cell rate (SCR), and maximum burst size
(MBS). When the average cell rate is the SCR, the source end can transmit burst traffic of the
maximum length of the MBS at the PCR without packet loss.
VBR-NRT
The VBR-NRT service class supports burst and non-real-time applications. The VBR-NRT
service class does not require low delay and has the same parameters as the VBR-RT service
class.
UBR
The UBR service class is used for applications that tolerate the cell delay and cell loss on the
network. The UBR service class does not provide QoS guarantee, and the cell loss ratio and cell
delay are variable. If congestion occurs, UBR cells are discarded first.
5.3 Application
5.3.1 IPoA
IP over AAL5 (IPoA) means that AAL5 bears IP packets. That is, IP packets are encapsulated
in ATM cells and transmitted on the ATM network.
RouterB
ATM1/0/0
To A:0/50
RouterA To C:0/51
ATM1/0/0 ATM
Network
To B:0/40 RouterC
To C:0/41
ATM1/0/0
To A:0/60
To B:0/61
Realization
As shown in Figure 5-18, on RouterA, PVC 0/40 can reach RouterB, and PVC 0/41 can reach
RouterC. If IP packets sent to RouterB need to be sent from PVC 0/40, the IP address of RouterB
must be mapped on PVC 0/40. After address mapping is set up, RouterA sets up a route that
reaches the IP address of RouterB. The outgoing interface is the interface where ATM PVC 0/40
resides.
5.3.2 IPoEoA
IP over Ethernet over AAL5 (IPoEoA) has a three-layer architecture. The high layer is IP
encapsulation, the middle layer is IPoE, and the low layer is IPoE over AAL5. IPoE packets are
transmitted after being encapsulated on the ATM.
When devices are connected to the remote access server through a high rate link, the access to
the external network can be realized through the Ethernet packets over ATM.
ADSL
Router A
Ethernet
Server
202.38.160.1
PC
Router C
DSLAM To ADSL Router A: 0/60
To ADSL Router B: 0/61
Virtual Ethernet1/0/0
Ethernet
Server
ADSL
Router B
PC
Implementation
As shown in Figure 5-19, IP packets must be encapsulated into Ethernet frames and transmitted
as ATM cells. Thus, the interfaces with the IP address and Ethernet address information must
exist between routers. Setting up a VE interface and mapping it to the PVC of ATM can realize
IPoEoA. That is, all the packets sent from the local router to the VE interface are transmitted as
ATM cells after being encapsulated through the mapped ATM interface.
5.3.3 PPPoA
PPP over AAL5 (PPPoA) means that AAL5 carries PPP packets. It means that ATM cells are
used to encapsulate PPP packets. IP or other packets are encapsulated in PPP packets. In this
manner, AAL5 can be regarded as the bearer layer of PPP packets.
PPPoA can make use of the flexibility and extensive applications of PPP because the PPPoA
communication process is managed by PPP.
Users must create a Virtual Template (VT) before transmitting PPP packets over AAL5. Figure
5-20 shows typical networking of PPPoA.
RouterC
PC 1 DSLAM
ATM1/0/0
Realization
In PPPoA mode, PPP packets are encapsulated as ATM cells and transmitted on an ATM
network. The PPPoA mode is similar to the IPoEoA mode.
A VT interface is required because the establishment of PPP needs to be authenticated.
When authentication is performed on RouterC, the authenticated user name, password, and
assigned IP address pool need to be created on RouterC. Set parameters such as the local IP
address, authentication mode (PAP or CHAP) of remote users, and address pool that allocates
addresses to the authenticated users on the VT interface. The VT is mapped to the PVC, which
associates PPP and ATM.
On the ADSL Router A at the client end, a VT must be created and mapped onto the
corresponding ATM interface. The user name, password, authentication mode, and IP address
acquisition mode that are authenticated on RouterC must be configured on a VT interface.
5.3.4 PPPoEoA
PPPoE over AAL5 (PPPoEoA) means that AAL5 bears the PPPoE (PPP over Ethernet) packets.
ATM cells are used to encapsulate Ethernet packets. In this manner, a PVC simulates all the
functions of the Ethernet.
The router implements the Ethernet packets over AAL5 through a VE interface. This VE
interface has the feature of the Ethernet and can be dynamically created by using the
configuration commands.
l The bottom layer is the PVC of ATM, through which packets can be transmitted and
received.
l The link layer is an Ethernet protocol.
l The network layer and upper layer protocols are the same as the protocols of common
Ethernet interfaces.
PPP packets are encapsulated in the Ethernet packets that are encapsulated and transmitted in
the ATM network.
ADSL
Router A
Ethernet
Server
VT10: 202.38.160.1/24
VT11: 202.38.161.1/24
PC
Router C
DSLAM To ADSL Router A: 0/60
To ADSL Router B: 0/61
ATM1/0/0.1
Ethernet
Server
ADSL
Router B
PC
Realization Method
PPP encapsulation is implemented on a VT, PPPoE is used to encapsulate PPP packets on a VE,
and an ATM interface uses PPPoEoA to encapsulate PPPoE packets. PPPoEoA implementation
is similar to PPPoA implementation.
Configure parameters such as users and address pool on the authenticating router. External
remote authentication dial-in user service (RADIUS) can also be used. The local authentication
is described here. Configuration on the VT interface is the same as that described in PPPoA. A
VE interface is set up again. The VT is mapped on the VE interface to realize the encapsulation
or decapsulation of PPPoE packets. Then, the VE interface is mapped onto the ATM interface.
5.4 Reference
The following table lists the reference of this feature:
Document Description
Document Description
6 Frame Relay
6.1 Introduction
6.2 Principles
6.3 Application
6.4 Reference
6.1 Introduction
Definition
Working at the data link layer of the Open System Interconnection (OSI) model, Frame Relay
(FR) is a technique that uses simple methods to transmit and exchange data.
A distinct feature of FR is that FR simplifies processes of error control, confirmation and re-
transmission, traffic control, and congestion prevention on an X.25 packet switch network, thus
reducing processing time. This is quite important to effective use of high-speed digital
transmission channels.
NOTE
The delay of packet switching on an X.25 network is tens to hundreds milliseconds, whereas the delay of
packet switching on an FR network can be reduced to several milliseconds.
Purpose
Data communications devices such as routers are connected through private lines, which results
in many disadvantages.
l Firstly, private lines use fixed bandwidth and interfaces. It is inconvenient for users to
change bandwidth or expand capacity.
l Secondly, the cost of connecting the networks by the private lines is high and user rental
is also high.
l In addition, if the private lines are used to construct a fully-connected network and the
number of users is n, n (n-1) / 2 circuits are thus needed, which causes a lot of trouble to
the management and application of the network resources.
FR is mainly used on Wide Area Networks (WANs) and it supports multiple types of data
services. FR can address the following problems:
6.2 Principles
An FR network provides data communication between user devices (such as routers and hosts).
DLCI is applied to differentiate VCs. It is valid only on the local interface and the directly-
connected peer interface but not valid globally. On an FR network, the same DLCI on different
physical interfaces does not indicate the same VC.
A user interface on an FR network supports multiple VCs. The available DLCI ranges from 16
to 1022 among which DLCIs 1007 to 1022 are reserved. Because the FR VC is connection-
oriented, different local DLCIs are connected to different remote devices. Therefore, the local
DLCI can be considered as the "FR address" of the remote device.
The FR address mapping associates the peer protocol address with the FR address (local DLCL).
Thus, the upper-layer protocol can locate the remote device.
When transmitting IP packets over FR links, a router searches for the next-hop address in the
routing table first, and then it finds the corresponding DLCI in the address mapping table of FR.
This table maintains the mapping information between remote IP address and next hop DLCL.
The address mapping table can be configured manually or maintained dynamically by Inverse
ARP.
Virtual Circuit
A VC is the logical circuit built on the shared network between two network devices. VCs can
be divided into the Permanent VC (PVC) and Switching VC (SVC).
The PVC status of the DTE is determined by the DCE, and the PVC status of the DCE is
determined by the network.
If two network devices are connected directly, the VC status on DCE side is configured by the
administrator.
The Local Management Interface(LMI) protocol maintains the link and PVC status of the Frame
Relay through the status enquiry packet and status packet.
Multi-network PVC
When passing multiple networks, the PVC is called multi-network PVC. It consists of the PVC
of each network, which is called PVC segment. Figure 6-1 shows the multi-network PVC.
RouterA RouterB
Multi-network PVC
A multi-network PVC is formed only after all PVC segments are configured. All PVC segments
cannot be configured at the same time because a PVC segment is configured on each network.
The status of a PVC segment can be bidirectionally transferred through the LMI protocol of
NNI. This status is transferred to the DCEs of both ends. Then, the DCE reports the status to the
DTE device so that the DTE device can learn the end-to-end status of the PVC. If all PVC
segments are configured, the DTE device can find an available multi-network PVC.
DTE The PVC status request timer (N391) 1 to 255 times 6 times
These parameters in Table 6-1 are defined in the Q.933 Appendix A with the following meanings
in Table 6-2:
N391 DTE sends a status request packet at certain intervals (determined by T391).
There are two kinds of status request packets, namely, link integrity verification
packet and link full status demand packet. N391 defines the sending ratio of
the two kinds of status request packets. The formula is link integrity verification
packet number: link full status demand packet number = (N391-1):1.
T391 Indicates a time variable. It defines the time interval at which DTE sends a
status request packet.
DTE sends a status request packet at certain intervals to query the link status. DCE sends a status
response packet after receiving this request packet. If no response is received from DCE at the
specified interval, DTE records this error. If the number of errors exceeds the threshold, DTE
reckons that physical channel is unavailable, nor are all VCs.
Both N392 and N393 define the error threshold. For example, total N393 status request packets
are sent on device at DTE side, wherein N392 gets no response within the stipulated period.
DTE reckons that physical channel is unavailable, nor are all the VCs.
N392 N392 refers to the above section "Meanings of the parameters related to DTE".
Note that DCE requires T392 rather than T391 to determine the fixed time
interval at which DTE sends a status request packet. The time interval of a status
request packet sent by DTE is determined by T391.
N393 N393 refers to the above section "Meanings of the parameters related to DTE".
Note that DCE requires T392 rather than T391 to determine the fixed time
interval at which DTE sends a status request packet. The time interval of a status
request packet sent by DTE is determined by T391.
T392 Indicates a time variable. It defines the longest time for DCE to wait for a status
request packet. Its value should be greater than T391.
Status Packet
Status message is used to reply the status request message, notifying the PVC status and link
integrity detection. It contains the following information units.
2 Call reference 00 1
Status request message is used to query the PVC status and link integrity, containing the
following information units.
2 Call reference 00 1
Only the full status and asynchronous PVC status messages contain the PVC status information
unit which is not contained in the link integrity verification messages.
On a UNI interface, the PVC status of DTE is completely decided by DCE that notifies all PVCs
status of DTE. Therefore, DTE has to only query DCE at a fixed time, and then it can obtain the
current PVC status on this interface. The PVC status of DCE is determined by the network
devices.
On a NNI interface, the network devices on both sides exchange the PVC status at a fixed time
by using the LMI protocol. Different from UNI, the network devices on both sides of a NNI
interface send request packets to their peers. After receiving the request packets, the two ends
of the NNI interface can respond to the packets.
1. DTE sends a status request packet and the timer T391 begins to time. The interval of T391
is the interval of a polling. That is, DTE sends a status request packet in every other T391.At
the same time, the counter V391 of DTE begins to count.
l When V391 is less than N391, the status request packet sent by DTE queries only the
link integrity.
l When V391 is equal to N391, V391 is set to 0, and the status request packet sent by
DTE queries both the link integrity and the status of all PVCs, this status request packet
is called a full status request packet.
Therefore, N391 defines the time of a period, and DTE sends a full status request packet
in every other a period. Both N392 and N393 can use the default value or set manually.
2. After receiving the polling message, DCE uses the status message to respond the status
request message. At the same time, the polling of DCE proves that the timer T392 begins
to time, waiting for the next status request message. After T392 times out, DCE does not
receive the status request message, and DCE records this error and the times of error
increases by 1.
3. DTE reads the received the status response message to know the link integrity and PVC
status. DCE responds to the status that DTE needs to know. If the PVC status changes or
the added or deleted PVC exists in local network, DCE must respond to the status message
of all PVCs no matter DTE queries the PVC status or not. By doing so, DTE can know the
changes of DCE timely and renew the previous record.
4. After T391 times out, the DTE devices do not receive the status response message, and
DTE records this error and the number of errors increases by 1.
5. In N393 events, if the number of errors exceeds N392, DTE or DCE reckons that this
physical channel and all the VCs are unavailable. N393 indicates the total observed events.
N392 indicates the error threshold. Both N392 and N393 can be set manually or are set to
the default value.
Like Q933 Appendix A, ANSI T1-617Appendix D uses the PVC whose DLCI is 0 to transmit
the LMI packets. Different from the LMI packets of Q933, those of ANSI has a Locking shift
whose value is 0x95 behind the Message Type. In addition, the value of Protocol discriminator
is 0x08, value of Report Type ie information is 0x01, value of LIV ie information is 0x03 and
value of PVC status ie information is 0x07.
6.2.3 InARP
The main function of InARP is to solve the IP addresses of the remote device that is connected
to every VC.
If the protocol address of the remote device that is connected to a VC is known, the mapping
between the remote protocol address and DLCI can be created on the local end, which can avoid
configuring the address mapping manually.
The basic process is as follows:
1. When a new VC is found, InARP sends a request packet to the remote end on this VC if
the local interface is configured with the protocol address. This request packet contains the
local protocol address. When the remote device receives this request packet, the local
protocol address can be obtained to create the address mapping and an InARP response
packet is sent. The address mapping is thus created on the local end.
2. If the static mapping is configured manually or dynamic mapping is created, the InARP
request packet is not sent to the remote end on this VC regardless of whether the remote
address in the dynamic mapping is correct. An InARP request packet is sent to the remote
end only when no mapping exists.
3. If the receiver of the InARP request packet finds the remote protocol address is the same
as that in the local configured mapping, it does not create the dynamic mapping.
The format of an InARP packet is the same as that of a standard ARP packet. Table 6-9 shows
the format of an InARP packet which does not contain the FR header.
The hardware type allocates the value 0x000f to FR. The protocol type is determined by the
protocol address. IP is 0x0800 when the TCP/IP header compression is not configured. IPX is
0x8137.
Operation code indicates the packet types, that is, the request and reply packets. The operation
code of an InARP request packet is 0x08, while that of an InARP reply packet is 0x09.
The length of the hardware address and protocol address are determined by the environment
where InARP runs. On an FR, the length of a hardware address ranges from 2 bytes to 4 bytes
(Q.922 address), and that of a protocol address is 4.
Serial1/0/0 Serial1/0/0
10.1.1.1/24 10.1.1.2/24
DLCI=100
1. The interface in DTE mode periodically sends status enquiry messages to the interface in
DCE mode.
2. The interface in DCE mode, after receiving a status enquiry message, replies with a status
message to the interface in DTE mode.
3. The interface in DTE mode determines the link status and PVC status according to the
received status messages.
4. If interfaces in DCE and DTE modes can normally exchange LMI negotiation messages,
the link status changes to Up and the PVC status changes to Active.
5. The FR LMI negotiation succeeds.
1. If the interface on the local device has been configured with a protocol address, the PVC
of the interface on the local device can send Inverse ARP Request packets to the remote
device. The request packet carries the protocol address of the interface on the local device.
2. After receiving the request packet, the remote device generates an address mapping table
based on the local address carried in the request packet and sends an Inverse ARP Response
packet to the local device.
3. The local device obtains the remote address from the received Inverse ARP Response
packet and then generates an address mapping table.
4. Address mapping tables are generated on RouterA and RouterB. For example, in the address
mapping table on RouterA, the DLCI value corresponding to the IP address 10.1.1.2 is 100;
in the address mapping table on RouterB, the DLCI value corresponding to the IP address
10.1.1.1 is 100.
After the LMI and InARP negotiations, the protocol status of the FR interface goes Up and
address mapping tables are generated, which enable the PVC to transmit IP packets.
6.2.5 FR Sub-Interfaces
Origins of FR Sub-Interfaces
An FR network can connect the networks that are in different places. The possible network
structures are star structure, partial-connected and full-connected network structures.
From the aspect of economy, the star structure is the excellent network structure because it uses
the least PVCs and the primary node connects the multiple dispersive branch nodes by using
multiple PVCs on one interface. This structure is mainly used for the headquarters to connect
multiple subdivisions. The disadvantage of this structure is that the communication between
branch nodes needs to be transmitted through a primary node.
In the full-connected structure, all nodes are connected to other nodes through the PVCs and a
node does not need other nodes to transmit the communication. In addition, this structure has
high flexibility. When the directly-connected PVC is Down, the communication can be
transmitted through other nodes. The disadvantage of this structure is that many PVCs are
needed, and the number of PVCs needed increases sharply when the number of nodes increases
in the network.
In the partial-connected structure, not all nodes have PVCs to access other nodes. Its advantage
and disadvantage are intervenient between the star and full-connected structure. The defaulted
network of FR is Non-broadcast Multi-access (NBMA). Different from the Ethernet, the NBMA
network does not support the broadcast, though nodes are connected in an FR network. If one
node obtains the routing information, it generates many copies of the information and then sends
the information to the connected multiple nodes through the PVCs.
To decrease the routing loop, the split horizon mechanism does not allow the router to send out
the updated information through the interface that receives this information.
RouterB
DLCI=16
RouterD
DLCI=16
As shown in Figure 6-3, RouterB advertises RouterA a piece of router information, but RouterA
cannot advertise this information to RouterC or RouterD through Serial 1/0/0 that receives this
router information according to the split horizon. The methods to solve this problem are as
follows:
l Using multiple physical interfaces to connect multiple adjacent nodes: This requires the
router to have multiple physical interfaces, and increases the cost of users.
l Using the sub-interfaces (that is, configuring multiple logical interfaces on one physical
interface): Like a physical interface, every sub-interface has its network address.
l Deleting the split horizon: This needs the support from the routing protocol, and increases
the probability of routing loop.
FR Sub-Interfaces
RouterB
su
b-i
nte
rfa
ce
1
RouterC Switch RouterA
sub-interface2 Serial1/0/0.1
Serial1/0/0.2
e3 Serial1/0/0.3
RouterD r fac
e
b- int
su
You can define these logical sub-interfaces on the serial line. Every sub-interface uses one or
multiple DLCIs to connect to the remote device. After a DLCI is configured on a sub-interface,
the mapping between the destination protocol address and this DLCI needs to be created.
In this way, the DLCI on Serial 1/0/0.1 is defined to access RouterB, the DLCI on Serial 1/0/0.2
is defined to access RouterC, and the DLCI on Serial 1/0/0.3 is defined to access RouterD on
Serial1/0/0, though only one physical serial port, Serial 1/0/0, exists on RouterA.
After a logical sub-interface is defined on a physical interface, the FR connection can become
the partial-connected connection. routers can interconnect and forward the updated information
by configuring the sub-interfaces. In this way, multiple sub-interfaces on one physical interface
are not affected by the split horizon.
This connection of multiple sub-interfaces on one physical interface is different from the point-
to-point (P2P) connection in NBMA. In the configuration of NBMA, all routers are on the same
subnet, using the PVCs of the full-connected connection.
However, only the sub-interfaces of two connected routers are on the same subnet, when the
P2P sub-interface of FR is used. This FR configuration contains many subnets.
Classification of FR Sub-interfaces
FR sub-interfaces can be classified into the following types:
6.2.6 FR QoS
Frame relay (FR) has its own Quality of Service (QoS) mechanism that provides traffic shaping,
queue management, and fragmentation.
FR Bandwidth Management
FR is a statistical multiplexing protocol that dynamically allocates the bandwidth and provides
services for users having a large amount of burst data in local area networks (LANs).
If the sum of data traffic volume of all users exceeds the available physical bandwidth at a
moment, FR takes measures to manage bandwidth usage. FR monitors and controls user
information transmitted over virtual circuits (VCs) by allocating bandwidth control parameters
to users.
User rate
Discarded frames
Bc
Tansmitted frames
CIR
T0 T0+Tc Time
As shown in Figure 6-5, an FR network allocates two bandwidth control parameters, Bc and
committed information rate (CIR), to each FR user. In addition, the FR network monitors and
controls data traffic on VCs at an interval of Tc.
l The CIR is the committed rate at which users transmit information. If a user transmits
information at a rate smaller than or equal to the CIR, the information is transmitted.
Otherwise, the information is discarded.
l Bc is the maximum amount of service data that the network commits to transmit at the CIR
during Tc. The formula for calculating Tc is as follows:
Tc = Bc/CIR
The FR network controls the bandwidth of each VC. When the amount of service data is smaller
than Bc during Tc, the FR network continues to transmit received frames.
FR Traffic Shaping
Frame relay traffic shaping (FRTS) is applied to an outbound interface of a router on an FR
network to control outgoing traffic. Each permanent virtual circuit (PVC) of an outbound
interface can transmit traffic based on parameters provided by the applied FR class.
FRTS controls traffic based on the configured parameters, including the minimum CIR, CIR,
and Bc. Inheriting the traditional traffic shaping algorithm, FRTS is implemented by using the
token ring algorithm.
NOTE
If traffic shaping parameters are configured for an outbound interface and its PVC, the traffic shaping
parameters with the smaller CIR value take effect. If the CIR value of the PVC is smaller than that of the
outbound interface, the traffic shaping parameters of the PVC take effect.
FRTS determines whether to change the transmission rate based on the following items:
l Backward explicit congestion notification (BECN) flag: When network congestion occurs,
a DCE sends a packet with the BECN flag set to 1 to a DTE. After receiving this packet,
the DTE reduces the transmission rate of VCs from the allowed CIR by a specified
percentage each time until the transmission rate reduces to the CIR. If the DTE does not
receive any packet with the BECN flag set to 1 within a specified period, it restores the
transmission rate of VCs to the allowed CIR.
l Packet count in an interface's output queue: When the interface's output queue reaches the
specified length, the transmission rate of VCs begins to reduce. When the interface's output
queue is smaller than the specified length, the transmission rate of VCs increases.
FR Queue Management
Packets directly sent from PVCs at a rate smaller than the CIR and packets from PVC queues
are sent by an interface. If congestion occurs on the interface, these packets are placed into
interface queues. FRTS-enabled interfaces support only two queue scheduling mechanisms,
PVC priority queuing (PVC PQ) and class-based weighted fair queue (CBWFQ).
Only FRTS-enabled interfaces support PVC PQ queues.
When each PVC needs to transmit a type of traffic such as voice or data traffic and different
PVCs require differentiated services, PVC PQ allows different PVCs to have different priorities
and packets on these PVCs to be placed into queues of different priorities. PVC PQ uses the
same output queue scheduling mechanism as PQ, ensuring that packets on a high-priority PVC
are scheduled first. PVC PQ does not parse packets. Instead, PVC PQ extracts the data link
connection identifier (DLCI) from packets and searches for the configured priorities to classify
packets.
FR DE Rule List
On an FR network, packets with the Discard Eligibility (DE) value 1 are discarded first when
congestion occurs.
DE rule lists are used on FR VCs. A DE rule list contains multiple DE rules. If packets transmitted
over a VC match rules in a DE rule list, the DE value of the packets is set to 1 and these packets
are discarded first when congestion occurs.
packets need to be transmitted along FR PVCs in a PVC group, map the Type of Service (ToS)
fields of IP packets to FR PVCs so that IP packets with different priorities are transmitted along
separate PVCs. In addition, each PVC in the group can be configured with a different QoS policy
for transmitting a specific type of services.
As shown in Figure 6-6, a PVC group works as follows:
1. The system searches for an FR mapping according to the destination IP address of the
receiving packets.
2. If the FR mapping corresponds to a PVC group, and the packet is an IP packet, the system
searches the PVC group for a specific PVC based on the mapping between the packet
priority and the PVC Data-Link Connection Identifier (DLCI) value, and sends the packet
over this PVC.
3. If the system fails to obtain a mapping between the packet priority and a PVC DLCI value,
it forwards the packet based on the following rules: If the packet is a non-IP packet (such
as an MPLS or InARP packet) and IP Precedence values or DiffServ Code Point (DSCP)
values have been mapped to PVC DLCI values, the system sends the packet over the PVC
with the IP Precedence value of 6 or the DSCP value of 63. If neither IP Precedence values
nor DSCP values are mapped to PVC DLCI values, the system sends the packet over the
default PVC.
4. If no default PVC is configured, and no matching PVCs are found for packets with specific
priorities, the PVC group will become unavailable.
FR
Network
DLCI1
DLCI2
PVC PVC
Group 1 DLCI3 Group 1
DLCI4
6.2.8 FR Compression
FR compression provides a cost-effective solution for FR users by compressing FR packets to
reduce network bandwidth consumption and network workload, and improve transmission
efficiency on an FR network.
The device supports FRF.9 compression and IP header compression (IPHC).
FRF.9 Compression
The device supports FRF.9 STAC compression.
IP header compression
The FR features that the device supports IP header compression. IP header compression
compresses RTP and TCP headers.
6.2.9 Multilink FR
Multilink Frame Relay (MFR) is a kind of cost-effective bandwidth solution provided for FR
users. Based on the FRF.16.1 protocol of FR forum, it realizes MFR function on the User-to-
Network Interface (UNI) or NNI interface.
The MFR provides a kind of logical interface, namely, the MFR interface, which is bound from
multiple FR physical links. The MFR interface can provide high-speed and broad-bandwidth
links on the FR network.
To maximize the bandwidth of bundled MFR interfaces, physical interfaces with the same rate
are bundled to the same MFR interface. In this way, the management cost can be reduced.
l Bundle and bundle link
The bundle and bundle link are two basic concepts of MFR.
One MFR interface corresponds to one bundle, which may contain multiple bundle links.
One bundle link corresponds to one physical interface. Bundle manages its bundle links.
The relationship between the bundle and bundle link is described as follows.
For the real physical layer, the bundle link is visible; while for the real data link layer, only
the bundle is visible.
l MFR interface and physical interface
An MFR interface is a kind of logical interface. Multiple physical interfaces can be bundled
into one MFR interface. Configuring the bundle and bundle links is actually configuring
the MFR interface and physical interfaces.
The function and configuration of an MFR interface are the same as those of an FR interface.
After the physical interfaces are bundled into an MFR interface, the originally configured
parameters on the network layer and FR link layer no longer work. Parameters on this MFR
interface are thus used.
By binding multiple physical interfaces of the router, the Multilink FR (MFR) technique provides
higher bandwidth for users, which does not greatly increase investment in the network devices.
Based on the FRF.16.1 UNI MFR protocol of the FR Forum, the MFR realized in Huawei routers
provides a virtual physical interface, that is, an MFR interface, which multiple physical interfaces
are bundled into.
An MFR interface is called bundle in the protocol and the multiple physical interfaces that
compose this MFR interface are called bundle links. The transmission bandwidth provided by
an MFR interface to the upper-layer frames is almost the total of that provided by its multiple
physical interfaces.
The MFR protocol realizes the following mechanisms.
l The reordering of packets is realized by adding the MFR header information with sequence
number into the FR packets.
l The status management of a single physical interface in an MFR interface is realized by
sending and receiving multiple link management packets in fixed formats and enabling and
disabling the corresponding protocol timer.
l The status of all physical interfaces bundled into an MFR interface finally determines the
MFR interface status. When a physical interface is available in an MFR interface, this MFR
interface is available for the upper-layer FR application. When all physical interfaces are
unavailable, this MFR interface is unavailable for the upper-layer FR application. In other
words, for the FR, an MFR interface is a physical layer, while for the multiple physical
interfaces, it is a link layer. Figure 6-8 shows the detailed relationship of protocol layers.
MFR
MFR interface(bundle) protocol MFR interface(bundle)
stack
MFR MFR FRF.16 MFR MFR
bundle link bundle link bundle link bundle link
As shown in Figure 6-8, the physical interfaces of the two communicating sides are connected
one to one. The upper layer data first encapsulates the header information of the FR, and
encapsulates the header information of the MFR. Then, the header information of the FR and
MFR is transmitted on one MFR interface. However, data is actually transmitted by the multiple
physical interfaces, namely, the bundle links, which are bundled into an MFR interface.
6.2.10 PPPoFR/MPoFR
An Frame Relay (FR) network administrator cannot check whether or not users connecting to
enterprise networks are valid because FR does not provide any authentication function. To enable
FR networks to provide authentication functions, configure Point-to-Point Protocol (PPP) over
FR for FR networks. This allows FR networks to use PPP features such as the Link Control
Protocol (LCP), Network Control Protocol (NCP), Password Authentication Protocol (PAP),
Challenge Handshake Authentication Protocol (CHAP), and Multilink Point-to-Point Protocol
(MP) fragmentation. After PPPoFR is configured, an E2E PPP session can be established
between devices, as shown in Figure 6-9.
FR
Network
6.2.11 FRoISDN
Frame Relay over Integrated Services Digital Network (FRoISDN) allows FR data transmission
over ISDN B channel. With FRoISDN, data from access devices is sent to an aggregation device.
The aggregation device then sends the data to the core network. The cost of leasing FR lines is
relatively high. Using an FRoISDN scheme decreases the number of leased FR lines required,
reducing enterprise expenditures. On the network shown in Figure 6-10, devices on the left
connect to a router enabled with the FR switch function by means of ISDN dial-up. The router
removes ISDN headers from packets and forwards the data to the FR network.
FR Switch
ISDN FR
Network Network
6.2.12 FRoIP
In real world situations, devices on IP networks need to transmit FR packets. FRoIP can be used
to transmit FR packets through IP networks. In an FRoIP scenario, GRE tunnels are set up
between two ends of an FR network. FR packets are transmitted along the GRE tunnels. As
shown in Figure 6-11, after GRE tunnels are set up, tunnel interfaces are used to implement FR
switching and FR packets can be transmitted over an IP network.
IP network
Tunnel
FR packets transmitted along GRE tunnels can be classified into three types: FR data packets
encapsulated with IP headers, Inverse ARP packets, and LMI packets used to negotiate status
of a PVC on GRE tunnels.
FRoIP can be implemented by creating FR switching routes or FR switching PVCs.
6.3 Application
6.3.1 FR Access
One typical application of FR is the FR access. As the user end, FR bears the upper-layer packets
to the FR network.
FR network is used for data communication between the user devices.
As shown in Figure 6-12, the FR network can be a public network or a private network of an
enterprise.
Router A Router B
Serial1/0/0.1
10.1.1.2/24
DLCI=80
RouterA RouterB
Serial1/0/0 Serial1/0/0
IP:10.1.1.1/24 IP:10.1.1.2/24
DLCI=100
6.3.2 MFR
As shown in Figure 6-14, RouterA and RouterB are directly connected through Serial 1/0/0:0
and Serial 1/0/1:0. MFR bundles the two serial interfaces to provide larger bandwidth.
Router A Router B
Serial1/0/0:0 Serial1/0/0:0
Serial1/0/1:0 Serial1/0/1:0
MFR1/0/100 MFR1/0/200
10.1.1.1/24 10.1.1.2/24
6.3.3 PPPoFR/MPoFR
On the network shown in Figure 6-15, PPPoFR/MPoFR is configured on a device to provide
access services for users who intend to visit an enterprise intranet. The device uses PAP and
CHAP of PPP to authenticates users so that only valid users can visit the enterprise intranet.
FR
Network
6.3.4 FRoISDN
On the network shown in Figure 6-16, devices on the left connect to a router enabled with the
FR switch function by means of ISDN dial-up. The router removes ISDN headers from packets
and forwards data to the FR network.
FR Switch
ISDN FR
Network Network
FR
Network
DLCI1
DLCI2
PVC PVC
Group 1 DLCI3 Group 1
DLCI4
6.4 Reference
The following table lists the references of this document.
The international organizations that constitute the FR standard mainly include ITU-T, ANSI and
FR Forum.
ITU-T Standard
l I.122: FR Bearer Service Framework
l I.233: Frame Mode Bearer Services
l I.370: Congestion Management of FR Bearer Services
l I.555: Interworking of FR Bearer Services
l I.620: FR Network Management
l Q.922: ISDN Link Layer Technical Specification for Frame Mode Bearer Services
l Q.933: Frame Mode Basic Call Control Signaling Specification for Digital Subscriber
Signaling No.1 (DSS1)
ANSI Standard
l T1S1: Structure Framework and Service Description
l T1.620: ISDN Link Layer Technical Specification
l T1.606: FR Bearer Service Description
l T1.617: Signaling Specification for FR Bearer Service
FR Forum Standard
l FRF.1: UNI Implementation Agreement
l FRF.3: Multi-Protocol Encapsulation Implementation Agreement
l FRF.6: FR Services User Network Management Implementation Agreement
l FRF.7: FR PVC Broadcast Service and Protocol Description Implementation Agreement
l FRF.12: Frame Relay Fragmentation Implementation Agreement
l FRF.13: Service Level Definitions Implementation Agreement
l FRF.14: Physical Layer Interface Implementation Agreement
l FRF.15: End-to-End Multilink Frame Relay Implementation Agreement
l FRF.16: Multilink Frame Relay UNI/NNI Implementation Agreement
7 ISDN
Purpose
The device provides access to voice, video, and data for users.
Benefits
ISDNs have been widely used in some countries. The device provides the ISDN leased line
service of 64 kbit/s and 128 kbit/s and speeds up the establishment of connections between
branch companies, and between branch companies and their headquarters.
7.2 Principles
This section describes ISDN Layer 2 and Layer 3 protocols.
Layer1 I.430/I.431
Physical layer protocol: B channels and D channels are multiplexed on the same physical
interface. Therefore, ISDN B channels and D channels at the physical layer use the same
protocols: ITU-T I.430 (BRI) and ITU-T I.431 (PRI).
Data link layer protocol: ISDN does not define Layer 2 protocols dedicated to B channels. Any
Layer 2 protocols such as PPP, HDLC, and FR can be used between two communicating devices
as long as they can transparently transmit data on B channels. The device supports only PPP and
FR for B channels and Link Access Procedure on the D-channel (LAPD) defined in Q.921 for
D channels. These Layer 2 protocols transmit messages and data generated by a Layer 3 or
management entity.
Network layer protocol: ISDN does not define Layer 3 protocols dedicated to B channels. It just
defines Layer 3 protocols in the Q.931 standard for D channels. The Q.931 standard defines
Digital Subscriber Signaling System No.1 (DSS1), which controls and manages the
establishment and release of calls on B channels and is developed into different protocols based
on service applications. These protocols include National ISDN (NI) and National ISDN-2 (NI2)
in the United States, the ISDN protocol proposed by the European Telecommunications
Standards Institute (ETSI), and the ISDN protocol proposed by the Nippon Telegraph and
Telephone (NTT) Corporation. The device supports DSS1.
LAPD
ISDN Layer 2 protocols comply with the Q.921 standard, which defines Link Access Procedures
on the D-channel (LAPD). LAPD has the following functions:
l Transmits signaling packets over ISDN D channels.
l Allocates and manages terminal endpoint identifiers (TEIs).
l Controls the packet sequence.
l Detects and rectifies faults.
l Controls traffic to prevent links from being overloaded.
Format A
Format B
8 ... 3 2 1
TEI EA2
– SAPI: is short for service access point identifier and specifies the message type. The
value 63 indicates a Layer 2 TEI management message, and the value 0 indicates a Layer
3 call management message.
– C/R: is the command/response field bit. The C/R bit identifies a frame as a command
or a response. The user side sends commands with the C/R bit set to 0, and responses
with the C/R bit set to 1. The network side sends commands with the C/R bit set to 1,
and responses with the C/R bit set to 0.
– EA1: is the first address extension and has a value of 0.
– EA2: is the second address extension and has a value of 1.
– TEI: is short for terminal endpoint identifier and has the following values:
– Values 0 to 63 are selected by users. The device does not support user-defined TEI
values.
– Values 64 to 126 are requested by users and allocated by the network device.
– The value 127 is used to address packets to an unidentified device.
l Control field: is 1 byte or 2 bytes in length according to the frame type. This field identifies
the frame type:
– I: indicates information frames, which transmit valid information or data.
– S: indicates supervisory frames, which are used for error control and flow control.
Supervisory frames help to detect error data so that error data can be retransmitted.
– U: indicates unnumbered frames, which are used to establish, tear down, and control
links.
For more information about these frames, see the LAPD protocol.
l Information: consists of an integer number of bytes and transmits TEI management
messages or Layer 3 call management messages.
l FCS: is short for frame check sequence. The FCS field is 2 bytes in length and ensures the
validity of received frames.
ISDN uses the Q.931 protocol primitive for call control. The device and ISDN switch establish
a Q.921 link to transmit Q.931 messages.
Figure 7-4 shows the ISDN call control process on a data telecommunication network. There
are multiple switches on the ISDN network, and ISDN messages of the device are transparently
transmitted on the ISDN.
Call
SETUP
establishment
SETUP_ACK
INFORMATION
CALL PROCEEDING
SETUP
CONNECT
CONNECT CONNECT_ACK
CONNECT_ACK
Call Conversation
release
DISCONNECT
RELEASE
DISCONNECT
RELEASE COMPLETE
RELEASE
RELEASE COMPLETE
Call control goes through two phases: call establishment phase and call release phase.
l Call establishment phase
– The calling user sends a SETUP message to initiate call establishment. When the called
number is sent at one time, the SETUP message contains all information required by
the network to process this call. When the called number is sent in overlap mode, the
SETUP message contains no called user information or contains incomplete called user
information.
– When the called number is sent in overlap mode, an ISDN switch replies with a
SETUP_ACK message and requests the remaining called user information.
– When the called number is sent in overlap mode, the calling user sends one or more
INFORMATION messages carrying the remaining called number and additional
information to the ISDN switch.
– After the ISDN switch receives all required called user information, it replies with a
CALL PROCEEDING message to indicate that requested call establishment has been
initiated and sends a SETUP message to the called user to establish a call.
– The called user determines whether to answer the call according to information in the
SETUP message. If the called user decides to answer the call, it sends a CONNECT
message to the calling user to indicate that the call has been accepted.
– The calling user sends a CONNECT_ACK message.
– The call is established to transmit information between the calling user and called user.
l Call release phase
– The calling user sends a DISCONNECT message to terminate a connection.
– The ISDN switch sends a DISCONNECT message to the called user and sends a Release
message to the calling user.
– The calling user releases the call and sends a RELEASE_COMPLETE to the ISDN
switch.
– The called user receives the DISCONNECT message and sends a RELEASE message
to the ISDN switch.
– The ISDN switch sends a RELEASE_COMPLETE message to the called user.
– The call is released.
NOTE
Figure 7-4 describes the call release process initiated by the calling user. The call release process
initiated by the called user is similar.
7.3 Applications
Figure 7-5 and Figure 7-6 show typical networking diagrams of ISDN dial-up access.
Serial1/0/0:15
ISDN
RouterA RouterB
BRI1/0/0
ISDN
RouterA RouterB
NT1
NOTE
The ISDN dial-up access networking varies according to the physical interface of the device accessing an
ISDN network. When a BRI interface is used as an access interface, the device needs to be connected to
Network Termination 1 (NT1) and then to an ISDN. NT1 implements the physical layer functions, including
subscriber line transmission, loop detection, and D channel preemption. A maximum of eight devices can
access an ISDN by using NT1. The number of devices varies according to the NT1 type.
When a branch company needs to continuously transmit data with the headquarters or other
branch companies, an ISDN leased line can be used. No dial-up is needed if an ISDN leased line
is used, ensuring that data is reliably transmitted to the peer device in a timely manner. Before
using an ISDN leased line, ensure that a leased line has been established on the ISDN switch
and the ISDN switch has been connected to the peer device. The ISDN leased line networking
is similar to the ISDN dial-up access networking.
BRI interfaces support 64 kbit/s and 128 kbit/s leased lines, and PRI interfaces support 64 kbit/
s leased lines.
7.4 References
The following table lists the references of this document.
Document Description
8 RTC
Definition
Remote terminal connection (RTC) technology allows an HDLC terminal to connect to a router
using a synchronous serial port and transparently transmit HDLC packets over an IP network
so that the HDLC terminal can exchange data with other terminals.
Purpose
Many enterprises, such as civil aviation systems and banks, require real-time monitoring and
unified management on terminal data (such as data on radars and front end processors). To meet
the requirement, monitoring and monitored terminals must be able to exchange data with each
other. Asynchronous transfer mode (ATM) networks were widely used by enterprises to transmit
service data because ATM networks provide high bandwidth and good QoS. However, the ATM
implementation is complex, and ATM network devices are expensive. More and more
enterprises migrate their ATM networks to IP networks. Some non-IP terminals, such as High-
Level Data Link Control (HDLC) terminals, may be reserved after the network migration. Data
packets from HDLC terminals need to be transmitted over the IP network.
8.2 Principles
l Terminal
Terminals include monitoring and monitored terminals. A monitoring terminal collects
real-time data on monitored terminals and manages the data uniformly. For example, in a
civil aviation system, the ground control center functions as a monitoring terminal to
manage and monitor data collected on the radar. The radar, as the monitored terminal,
collects data in real time, responds to requests from the monitoring terminal promptly, and
sends the data to the ground control center.
l RTC client
An RTC client connects to a monitoring terminal. An RTC client can initiate a TCP
connection request to an RTC server at any time to collect data on the monitored terminal.
l RTC server
An RTC server connects to a monitored terminal. The RTC server is the receiver of TCP
connection requests and sends data on monitored devices to the RTC client.
1. Send an HDLC
packet. 2. Send a TCP
connection request.
3. TCP connection is
set up.
4. Encapsulate the HDLC 5. Decapsulate the
packet into a TCP packet. TCP to an HDLC
packet.
1. A monitoring terminal uses HDLC to encapsulate data packets and sends the packets to the
RTC client.
2. The RTC client sends a TCP connection request to the RTC server.
3. The RTC server receives the TCP connection request and sets up a TCP connection with
the RTC client after a three-way TCP handshake.
l RTC supports automatic TCP connection setup. This function enables the RTC client
to automatically set up a TCP connection with the RTC server after a specified interval.
Therefore, TCP connection setup does not need to be triggered by HDLC packets.
l RTC supports automatic TCP connection close. When no data is exchanged between
the monitoring terminal and the RTC client, the monitoring terminal is in idle state.
After RTC client keeps in idle state for a specified period, the RTC client automatically
closes the TCP connection with the RTC server.
4. The RTC client encapsulates HDLC packets into TCP packets and sends them to the RTC
server across an IP network.
5. After receiving the TCP packets, the RTC server decapsulates them to restore the HDLC
packets and sends them to the monitored terminal.
6. The monitored terminal sends HDLC packets containing collected data to the RTC server.
7. The RTC server encapsulates HDLC packets into TCP packets and sends them to the RTC
client across an IP network.
8. The RTC client decapsulates the TCP packets and sends the HDLC packets to the
monitoring terminal.
8.3 Application
Monitoring terminal 1
RTC client
Serial1/0/0
A typical RTC networking consists of one RTC server and multiple RTC clients. The RTC server
can set up independent TCP connections with RTC clients to transparently transmit HDLC
packets across an IP network.
8.4 References
The following table lists the reference for this feature.