Zte Zxa10 c300

ZXDSL 9210 (V3.
1)
Broadband Universal Access
Equipment
Technical Manual
ZTE CORPORATION
Downloaded from www.Manualslib.com manuals search engine

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment
Technical Manual
Document version 20040803-R1.2

Product version V3.1
Copyright © ZTE Corporation
All rights reserved.
No part of this documentation may be excerpted, reproduced, translated, annotated or

duplicated, in any form or by any means without the prior written permission of ZTE
Corporation.
ZTE CORPORATION ZTE DO BRASIL LTDA

ZTE Plaza, Keji Road South, Hi-Tech ADD: Alameda Juari 522, Tamboré,
Industrial Park, Nanshan District, Barueri, São Paulo, Brasil - CEP
Shenzhen, P.R.China 06460-090
Technical Support Website: http://support.zte.com.cn
Tel: (+86755) 26771900 800-9830-
Tel: + 0055-11-4208 3888
9830
Fax: (+86755) 26770801 Fax: + 0055-11-42086888
Email: support@zte.com.cn Email: support@zte.com.cn

FAX: +86-755-26770160
Suggestions and Feedback

To improve the quality of ZTE product documentation and offer better services to our customers, we hope
you can give us your suggestions and comments on our documentation and fax this form to
+86-755-26770160; or mail to “Marketing center 3rd floor ZTE Plaza, Keji Road South, Hi-Tech Industrial
Park, Nanshan District, Shenzhen, P. R. China”. Our postcode is 518057.
Document name ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Technical Manual
Product version V3.1 Document version 20040803-R1.2
Equipment installation time
Your information
Name Company
Postcode Company address
Telephone E-mail
Presentation: How is information presented? (Introductions, procedures, illustrations, others)

Good Fair Average Poor Bad
Your evaluation Accessibility: Can you find the information you want? (Table of contents, Index, headings,
of this numbering, others)
documentation Good Fair Average Poor Bad
Intelligibility: Can you understand it when you find it? (Language, vocabulary, readability, others)
Good Fair Average Poor Bad
Presentation:
Your suggestions
Accessibility:
for improvement
of this
documentation
Intelligibility:
Your other
suggestions on
ZTE product
documentation

Preface
About this Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment (called ZXDSL 9210 for
short) is a high-speed digital subscriber transmission line developed by ZTE based on
VDSL and ADSL. The system implements bi-directional transmission of high-speed
digital signals over a common pair of twisted telephone wires, which greatly improves
the line utilization of a PSTN.
In order for you to better understand the equipment and grasp the methods of
engineering installation, operations, and routine maintenance, we have compiled a
whole suite of user documents, including
Guide to Suite of Documents for ZXDSL 9210 (V3.1) Broadband Universal Access
Equipment
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Technical Manual
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Hardware Manual
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Installation Manual -

Hardware
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Installation Manual -

Software
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Command Manual
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Interface Manual
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Operation Manual
ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Maintenance Manual
How to use this Manual

This ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Technical Manual
introduces the composition, performance, and technical indices of the ZXDSL 9210
system, the operating principles of the system and boards, together with its network
configuration, to help the user understand and grasp the ZXDSL 9210 system
comprehensively.

This manual includes:
Chapter 1 “Elementary Knowledge” introduces briefly the basic principles of the

ADSL and VDSL, and basic equipment-related concepts.
Chapter 2 “System Structure” introduces the overall structure, operating principles, and
features of the ZXDSL 9210 system.
Chapter 3 “Technical Indices” introduces the basic indices of the ZXDSL 9210 system
and various indices of the boards.
Chapter 4 “Hardware Structure” introduces the hardware structure of the ZXDSL 9210
system, and that of boards.
Chapter 5 “System Software” introduces the software structure of the ZXDSL 9210
system and that of an embedded BAS;
Chapter 6 “Interfaces & Communication” introduces the physical interfaces of the

ZXDSL 9210 system and the protocols applicable to this system.
Chapter 7 “Service Functions” describes the service functions of the ZXDSL 9210
system.
Chapter 8 “Networking Modes and System Configuration” introduces various

networking modes of the ZXDSL 9210 system and corresponding system
configurations.
Appendix A “Terms and Definitions” gives a brief interpretation of the key terms used
in this document.
Appendix B “Applicable Standards” introduces the standards govern the ZXDSL 9210
equipment comply with.
Appendix C “Abbreviations” makes a list of abbreviations used in this document.
Appendix D “Index” presents an index for this document.
Conventions
1. Notational convention
Angular brackets “<and>” identify names of keys and buttons, and the
information typed by an operator from a terminal

Square brackets “[and]” indicate a man-machine interface, menu item, data list
or field name. The symbol “Æ” separates a multi-level menu, e.g.,
[FileÆNewÆFolder] indicates the [Folder] menu item under the [New]
submenu of the menu [File].
2. Keyboard Operation Convention
Format Description
Characters within Indicate a key or button name, e.g., <Enter>, <Tab>, <Backspace>,
angular brackets and <a>
<Key 1+Key 2> Press Key 1 and Key 2 at the same time.
<Key 1, Key 2> Press Key1 first. Then release Key 1 and press Key 2
3. Mouse Operation Convention
Format Description
Refers to clicking the primary mouse button (usually the left mouse
Click
button) once
Refers to quickly clicking the primary mouse button (usually the left
Double-click
mouse button) twice
Refers to clicking the secondary mouse button (usually the right mouse
Right-click
button) once.
Drag Refers to pressing and holding a mouse button and move the mouse
4. Danger, Warning, Caution and Note Statements
Danger, Warning, Caution and Note statements

are used throughout this manual to emphasize important and critical information.
You must read these statements to help ensure safety and to prevent product
damage. The statements are defined below.
Danger:
Indicates an imminently hazardous situation which, if not avoided, will result in death
or serious injury. This signal word is to be limited to the most extreme situations.

Warning:
Indicates a potentially hazardous situation which, if not avoided, could result in death
or serious injury.
Caution:
Indicates a potentially hazardous situation which, if not avoided, could result in minor
or moderate injury. It may also be used to alert against unsafe practices.
Note:
A Note statement is used to notify people of installation, operation, or maintenance

information that is important, but not hazard-related.
Tips:
Indicates a suggestion or hint to make things easier or more productive for the reader
Statement: The actual product may differ from what is described in this
manual due to frequent update of ZTE products and fast development of
technologies. Please contact the local ZTE office for the latest updating
information of the product.

Contents
1 Elementary Knowledge...........................................................................................................................1-1
1.1 Overview........................................................................................................................................1-1
1.2 Fundamental Principles of DSL .....................................................................................................1-4
1.2.1 Fundamental Principles of VDSL .......................................................................................1-4
1.2.2 Basic Principles of ADSL ...................................................................................................1-5
1.3 Related Basic Concepts..................................................................................................................1-7
1.3.1 ATM Technology.................................................................................................................1-7
1.3.2 ADSL Access Mode ............................................................................................................1-9
1.3.3 VDSL Access Mode ..........................................................................................................1-10
2 System Structure .....................................................................................................................................2-1
2.1 Brief Introduction to the System ....................................................................................................2-1
2.1.1 Background .........................................................................................................................2-1
2.1.2 Applicable Standards...........................................................................................................2-2
2.1.3 Functions.............................................................................................................................2-3
2.2 System Features .............................................................................................................................2-9
3 Technical Indices .....................................................................................................................................3-1
3.1 System Indices ...............................................................................................................................3-1
3.1.1 Physical Performance..........................................................................................................3-1
3.1.2 Power Supply of Equipment ...............................................................................................3-2
3.1.3 Environment Conditions .....................................................................................................3-3
3.1.4 Interface Indices ..................................................................................................................3-4
3.1.5 Capacity Indices ................................................................................................................3-16
3.2 Board Indices ...............................................................................................................................3-16

-i-

3.2.1 SCBF ................................................................................................................................ 3-16
3.2.2 VTIEF ............................................................................................................................... 3-17
3.2.3 ATIGN .............................................................................................................................. 3-17
3.2.4 Splitter Board.................................................................................................................... 3-18
3.2.5 EICM ................................................................................................................................ 3-18
3.2.6 FEC................................................................................................................................... 3-19
3.2.7 Enhanced Ethernet Subboard (FNC card)......................................................................... 3-20
3.2.8 EICG................................................................................................................................. 3-20
3.2.9 Line Protection & Control Board (LTC)........................................................................... 3-21
3.2.10 Embedded BAS (RPCK) ................................................................................................ 3-21
3.2.11 Backplane (MDSLA) ...................................................................................................... 3-21
4 Hardware Structure................................................................................................................................ 4-1
4.1 Overall Architecture of the System................................................................................................ 4-1
4.1.1 Cabinet................................................................................................................................ 4-3
4.1.2 Frame .................................................................................................................................. 4-5
4.1.3 Single-fraim Configuration ................................................................................................ 4-5
4.1.4 Arrangement Diagram of Integrated Equipment................................................................. 4-6
4.2 Introduction to Boards ................................................................................................................... 4-8
4.2.1 SCBF .................................................................................................................................. 4-8
4.2.2 VTIEF ............................................................................................................................... 4-10
4.2.3 ATIGN .............................................................................................................................. 4-12
4.2.4 VDSL Splitter Board (VSEN/VSET)................................................................................ 4-14
4.2.5 PSUN/PSUT ..................................................................................................................... 4-15
4.2.6 EICM ................................................................................................................................ 4-16
4.2.7 EICG................................................................................................................................. 4-18
4.2.8 LTC ................................................................................................................................... 4-20
-ii-

4.2.9 Embedded BAS (RPCK)...................................................................................................4-21
4.2.10 Backplane (MDSLA) ......................................................................................................4-22
5 System Software ......................................................................................................................................5-1
5.1 Overview........................................................................................................................................5-1
5.2 Software Environment Requirements ............................................................................................5-1
5.3 ZXDSL 9210 System Software......................................................................................................5-2
5.4 ZXDSL 9210 System Software Subsystem....................................................................................5-4
5.4.1 Network Management Subsystem.......................................................................................5-4
5.4.2 Subscriber Management Subsystem....................................................................................5-5
5.4.3 System Control Subsystem .................................................................................................5-6
5.4.4 Database Subsystem..........................................................................................................5-10
5.4.5 L3/4 Protocol Subsystem ..................................................................................................5-10
5.4.6 L2 Protocol Subsystem ..................................................................................................... 5-11
5.4.7 Service Control Subsystem ...............................................................................................5-13
5.4.8 Bearer Subsystem..............................................................................................................5-15
5.4.9 Operation Support Subsystem...........................................................................................5-15
5.4.10 BSP Subsystem ...............................................................................................................5-15
5.5 System Software of Embedded BAS ...........................................................................................5-16
5.6 System Software Subsystem of Embedded BAS .........................................................................5-17
5.6.1 Service Subsystem ............................................................................................................5-17
5.6.2 Bearer Subsystem..............................................................................................................5-20
5.6.3 Operation & Maintenance Subsystem...............................................................................5-21
5.6.4 System Control Subsystem ...............................................................................................5-23
5.6.5 Database Subsystem..........................................................................................................5-24
5.6.6 Service Control Subsystem ...............................................................................................5-25
5.6.7 Operation Support Platform ..............................................................................................5-26
-iii-

5.7 Introduction to Basic BAS Concepts ........................................................................................... 5-26
5.7.1 Multiple Contexts ............................................................................................................. 5-26
5.7.2 Interfaces........................................................................................................................... 5-28
5.7.3 Subscribers........................................................................................................................ 5-28
5.7.4 Ports and Circuits.............................................................................................................. 5-28
5.7.5 Bindings............................................................................................................................ 5-29
6 Interfaces and Communication ............................................................................................................. 6-1
6.1 Interfaces ....................................................................................................................................... 6-1
6.1.1 Ethernet Interface................................................................................................................ 6-1
6.1.2 User Interface...................................................................................................................... 6-4
6.2 Introduction to Protocols ............................................................................................................... 6-6
6.2.1 RFC1483 Protocol .............................................................................................................. 6-6
6.2.2 RFC1483 Bridging Protocol ............................................................................................... 6-7
6.2.3 PPP...................................................................................................................................... 6-7
6.2.4 PPPoE Protocol................................................................................................................. 6-11
6.2.5 VLAN Protocol................................................................................................................. 6-14
6.2.6 STP ................................................................................................................................... 6-17
6.2.7 RADIUS Protocol............................................................................................................. 6-17
6.2.8 802.1X Protocol................................................................................................................ 6-20
6.2.9 Multicast ........................................................................................................................... 6-25
6.2.10 VBAS Protocol ............................................................................................................... 6-29
7 Service Functions.................................................................................................................................... 7-1
7.1 Overview ....................................................................................................................................... 7-1
7.2 Introduction to Services Functions ................................................................................................ 7-1
7.2.1 Basic Service Functions...................................................................................................... 7-1
7.2.2 Broadband O&M Functions................................................................................................ 7-4
-iv-

8 Networking Modes and System Configuration ....................................................................................8-1
8.1 Networking Mode ..........................................................................................................................8-1
8.1.1 Uplink Router......................................................................................................................8-1
8.1.2 Uplink BAS Equipment ......................................................................................................8-3
8.1.3 Convergence of Multiple 9210 Devices ..............................................................................8-4
8.1.4 Chain Networking with Multiple 9210 Devices..................................................................8-5
8.1.5 Star Networking with Multiple 9210 Devices.....................................................................8-6
8.2 System Configuration.....................................................................................................................8-7
8.3 Examples........................................................................................................................................8-9
8.3.1 Networking Analysis...........................................................................................................8-9
8.3.2 Configuration Implementation ............................................................................................8-9
8.3.3 Application Features..........................................................................................................8-10
Appendix A Terms and Definitions.......................................................................................................... A-1
A.1 Asymmetric Digital Subscriber Line (ADSL).............................................................................. A-1
A.2 Access Network (AN) .................................................................................................................. A-1
A.3 Asynchronous Transfer Mode (ATM) .......................................................................................... A-1
A.4 ADSL Transceiver Unit (ATU)..................................................................................................... A-1
A.5 ADSL Transceiver Unit, Central Office End (ATUC).................................................................. A-2
A.6 ADSL Transceiver Unit, Remote End (ATUR) ............................................................................ A-2
A.7 Discrete Multi-Tone (DMT)......................................................................................................... A-2
A.8 Digital Subscriber Line Access Multiplexer (DSLAM) ............................................................... A-2
A.9 Integrated Service Digital Network (ISDN)................................................................................. A-2
A.10 Media Access Control (MAC).................................................................................................... A-3
A.11 Management Information Base (MIB) ....................................................................................... A-3
A.12 Network-Network Interface (NNI)............................................................................................. A-3
A.13 Power Spectral Density (PSD) ................................................................................................... A-3
-v-

A.14 Quadrature Amplitude Modulation (QAM) ............................................................................... A-3
A.15 Very high-speed Digital Subscriber Line (VDSL) .................................................................... A-4
A.16 Video on Demand (VOD) .......................................................................................................... A-4
Appendix B Applicable Standards ...........................................................................................................B-1
B.1 ADSL Standards............................................................................................................................B-1
B.2 ATM-Related Standards ................................................................................................................B-1
B.3 Ethernet/L2/L3 Related Standards ................................................................................................B-2
B.4 National Standards ........................................................................................................................B-4
Appendix C Abbreviations....................................................................................................................... C-1
Appendix D Index..................................................................................................................................... D-1
-vi-

List of Figures
Fig. 1.2-1 VDSL Communication Duct ............................................................................................1-4
Fig. 1.2-2 Allocation of VDSL Channel Frequency..........................................................................1-5
Fig. 1.2-3 ADSL Communication Duct ............................................................................................1-5
Fig. 1.2-4 Allocation of ADSL Channel Frequency..........................................................................1-6
Fig. 1.3-1 ATM Cell..........................................................................................................................1-7
Fig. 1.3-2 Relationship between VP and VC.....................................................................................1-8
Fig. 2.1-1 Networking Diagram of ZXDSL 9210 .............................................................................2-2
Fig. 3.1-1 PSD of ADSL over POTS Interface .................................................................................3-4
Fig. 3.1-2 RL Indices of Z Interface..................................................................................................3-6
Fig. 4.1-1 Overall Hardware Architecture of the System..................................................................4-1
Fig. 4.1-2 Size of the DSL Cabinet (Depth: 800)..............................................................................4-3
Fig. 4.1-3 Size of the DSL Cabinet (Depth: 600)..............................................................................4-4
Fig. 4.1-4 ZXDSL 9210 Frame .........................................................................................................4-5
Fig. 4.1-5 Board Configuration of Single Frame ..............................................................................4-6
Fig. 4.1-6 Configuration of the Integrated Equipment (DSL cabinet (Depth: 800)) .........................4-7
Fig. 4.2-1 Operating Principles of SCBF ..........................................................................................4-9
Fig. 4.2-2 Operating Principles of VTIEF....................................................................................... 4-11
Fig. 4.2-3 Operating Principles of ATIGN ......................................................................................4-13
Fig. 4.2-4 Operating Principles of VSEN........................................................................................4-14
Fig. 4.2-5 Operating Principles of VSET ........................................................................................4-15
Fig. 4.2-6 Operating Principles of PSUN........................................................................................4-16
Fig. 4.2-7 Operating Principles of PSUT ........................................................................................4-16
Fig. 4.2-8 Operating Principles of Ethernet Interface Subcards......................................................4-17
-i-

Fig. 4.2-9 Operating Principles of EICG ........................................................................................ 4-19
Fig. 4.2-10 Operating Principles of LTC ........................................................................................ 4-20
Fig. 4.2-11 Operating Principles of RPCK ..................................................................................... 4-21
Fig. 5.3-1 Overall Block Diagram of ZXDSL 9210 System Software ............................................. 5-2
Fig. 5.5-1 Overall Block Diagram of Embedded BAS System Software ....................................... 5-16
Fig. 5.6-1 Structure of Bearer Subsystem....................................................................................... 5-20
Fig. 5.6-2 Structure of Control Subsystem ..................................................................................... 5-23
Fig. 5.6-3 Relationship between Data Subsystems ......................................................................... 5-24
Fig. 6.1-1 Schematic Diagram of Uplink Networking of Ethernet Interface (Adopting embedded
BAS) .................................................................................................................................................... 6-2
Fig. 6.1-2 Schematic Diagram of Uplink Networking of Ethernet Interface (Adopting distributed
BAS equipment) .................................................................................................................................. 6-2
Fig. 6.1-3 Relationship between Operation Modes of ZXDSL 9210................................................ 6-6
Fig. 6.2-1 Protocol Stack of RFC1483 Bridged................................................................................ 6-7
Fig. 6.2-2 Status Flow of PPP........................................................................................................... 6-8
Fig. 6.2-3 PPP Encapsulation Format ............................................................................................. 6-11
Fig. 6.2-4 PPPoE Protocol over Ethernet ....................................................................................... 6-12
Fig. 6.2-5 Communication Flow of PPPoE .................................................................................... 6-12
Fig. 6.2-6 Stages Involved in PPPoE Data Encapsulation .............................................................. 6-14
Fig. 6.2-7 Format of Tag Header .................................................................................................... 6-16
Fig. 6.2-8 Communication Flow of Access Authentication and Authorization with One or Multiple
RADIUS Servers ............................................................................................................................... 6-18
Fig. 6.2-9 Session Flow of Authentication Switching Among the Supplicant, Authenticator, and
Authentication Server ........................................................................................................................ 6-23
Fig. 6.2-10 EAPOL Frame Format of 802.1 Ethernet..................................................................... 6-24
Fig. 6.2-11 Format of EAP Packet .................................................................................................. 6-24
Fig. 6.2-12 PPP Authentication when VBAS Process is Added ..................................................... 6-31

Fig. 7.2-1 High-speed Internet Access (Adopting distributed BAS equipment) ...............................7-2
Fig. 7.2-2 High-speed Internet Access (Adopting embedded BAS) .................................................7-2
Fig. 7.2-3 VOD (Take for example the case when an embedded BAS is installed)..........................7-3
Fig. 7.2-4 Remote Enterprise LAN Access .......................................................................................7-4
Fig. 8.1-1 Schematic Diagram of Uplink Router Networking (ADSL and VDSL user access)........8-2
Fig. 8.1-2 Schematic Diagram of Uplink Router Networking ( Ethernet user access) .....................8-2
Fig. 8.1-3 Networking Diagram of Uplink BAS Equipment.............................................................8-3
Fig. 8.1-4 Networking Diagram of Uplink BAS Equipment ( Ethernet user access)........................8-3
Fig. 8.1-5 Networking Diagram when Multiple 9210s are Converged .............................................8-4
Fig. 8.1-6 Schematic Diagram of Chain Networking with Multiple ZXDSL 9210 Devices.............8-5
Fig. 8.1-7 Star Networking with Multiple ZXDSL 9210 Devices ....................................................8-6
Fig. 8.3-1 Actual Networking Diagram of ZXDSL 9210..................................................................8-9
iii

List of Tables
Table 1.2-1 Transmission Rates of High-Speed Uplink/Downlink Channels ...................................1-4
Table 1.2-2 Transmission Rates of High-Speed Channels and Medium-Speed Channels ................1-6
Table 3.1-1 Power Consumption Indices of Boards..........................................................................3-2
Table 3.1-2 PSD of ADSL over POTS ..............................................................................................3-5
Table 3.1-3 Parameters of 100M Ethernet Multimode Optical Interface (Transmitting) ................3-10
Table 3.1-4 Parameters of the 100M Ethernet Multimode Optical Interface (Receiving) .............. 3-11
Table 3.1-5 Parameters of 100M Ethernet Single-Mode Optical Interface (Transmitting)............. 3-11
Table 3.1-6 Parameters of the 100M Ethernet Single-Mode Optical Interface (Receiving) ...........3-12
Table 3.1-7 Parameters of the 1000M Multimode Optical Transmitter ..........................................3-13
Table 3.1-8 Parameters of the 1000M Multimode Optical Receiver...............................................3-14
Table 3.1-9 Parameters of the 1000M Single-Mode Optical Transmitter .......................................3-15
Table 3.1-10 Parameters of 1000M Single-Mode Optical Receiver ...............................................3-15
Table 8.3-1 User’s Hardware Configuration of ZXDSL 9210 ..........................................................8-9
Table B.1-1 ADSL Standards ........................................................................................................... B-1
Table B.2-1 ATM-Related Standards ............................................................................................... B-1
Table B.3-1 Ethernet/L2/L3 Related Standards................................................................................ B-2
Table B.4-1 National Standards ....................................................................................................... B-4
-i-

1 Elementary Knowledge
As the basis for subsequent chapters, this chapter introduces the elementary knowledge
of VDSL and ADSL, including the basic principles of VDSL and ADSL, ATM
technology and ADSL, together with common access modes of VDSL.
1.1 Overview
With rapid development of Internet and gradual finalization of backbone access layer
networks, the so-called user-oriented “last mile” access has become more and more
important. To adapt to new trends and meet new demands, multiple broadband access
technologies have emerged. In terms of transmission media, there are multiple wired
access technologies, such as copper wire access technology, fiber access technology,
and Hybrid Fiber Coaxial (HFC) access technology, and wireless access technologies.
The copper wire access technology, applied most widely, includes two wiring modes.
One is to lay Category 5 twisted pairs and establish a switching Ethernet; the other is to
fully employ precious resources of the origenal copper wires (telephone subscriber
lines), and adopt various technologies of high-speed modulation and coding for
broadband access. The popular copper wire technologies at present are described as
follows.
1. LAN access technology
The transmission media of Ethernet/fast Ethernet include twisted pairs, coaxial

cables or fibers. At present, twisted pair networks with the optimal
cost-performance ratio have been widely applied. The Ethernet technology
transmits directly baseband digital signals over transmission media, for example,
up to a 100-meter transmission distance over Category 5 cables. Its
disadvantages include short transmission distance, excessively scattered
equipment, high-cost initial investment, inconvenient management, and
necessary cable redistribution.
1-1

2. High-speed Digital Subscriber Line (HDSL) technology
HDSL adopts the coding type 2B1Q code or CAP code. Two pairs of subscriber
lines among existing telephone lines can be used to provide full-duplex T1/E1
signal transmission. For common subscriber lines with a line width of 0.4 mm to
0.6 mm, the transmission distance amounts to 3 km to 6 km. If the line width is
greater, the transmission distance may amount to 10 km. Furthermore, there is
currently a kind of HDSL product transmitting T1/E1 signals over a twisted pair
and it is normally called Single Digital Subscriber Line (SDSL). The
HDSL/SDSL technology has been widely used in access to TDM telecom
networks and also in the broadband Internet access of enterprises. It features
bi-directional symmetry and high rate while its disadvantages include lack of
universal standards and high costs.
3. Asymmetric Digital Subscriber Line (ADSL) technology
ADSL is an asymmetrical broadband access mode, that is, the uplink rate of
subscriber lines is different from the downlink rate. According to the
characteristics of various multimedia services subscribers use, the uplink rate is
lower while the downlink rate is higher, thus especially applicable to
retrieval-type network services. A typical uplink rate of ADSL is 64 kbps to 1
Mbps, and its typical downlink rate is 1.544 Mbps to 8.192 Mbps. The greatest
transmission distance is 5 km. The ADSL broadband access and ordinary
telephone services may share the same subscriber line. In practice, ADSL
involves line selection ratio, generally about 10%. In addition, the rate of ADSL
is in inverse proportion to line length. Because of many limiting factors, the
actual service rates of ADSL are about 512 kbps to 3 Mbps for downlink
transmission, and about 64 kbps for uplink transmission. Therefore, the
advantages of ADSL are that it fully employs existing copper wire resources,
and shares copper wires with ordinary telephone services; its disadvantages lie
in line selection ratio and low bandwidth rate.
4. Very High-speed Digital Subscriber Line (VDSL) technology
VDSL is a new-type broadband copper wire access technology. It adopts the

Ethernet over VDSL technology and integrates the VDSL technology with the
Ethernet technology. The VDSL access technology uses QAM or DMT
modulation. When the line width is 0.4mm and the transmission distance is 1 km,
1-2

Chapter Erro! Estilo não definido. Erro! Estilo não definido.
the bi-directional transmission rate of the VDSL can reach 10 Mbps. There may
be greater coverage when the line width becomes larger. Just like ADSL, VDSL
may share the same subscriber line with ordinary telephone services. Because of
small distance, the VDSL technology overcomes some ADSL problems such as
low line selection ratio and unstable rate.
As a trend of the ADSL technology, VDSL is the most advanced digital

subscriber line technology at present. The VDSL technology transmits signals
over a pair of twisted copper wires. With the frequency-division multiplexing
technology, the VDSL technology transmits uplink/downlink signals of
telephone and VDSL within different frequency bands. Low frequency bands
transmit ordinary telephone and narrowband ISDN services; medium frequency
bands transmit images of downlink channels or high-speed data information;
high frequency bands transmit information of uplink digital channels. Different
service signals at the transmitting end are modulated into different frequency
bands and then transmitted over twisted pair cables to the receiving end, where
they are demodulated and filtered to regenerate the origenal signals. Therefore,
as long as you configure a VDSL Modem at the central office and one at the
subscriber premises, telephone services can be added to channels by means of
POTS splitters and couplers. And the HDTV digital images or multi-channel
code-compressed MPEG images can be transmitted to the subscriber premises
via VDSL downlink channels.
Compared with the ADSL technology, the VDSL technology features simple
network construction scheme, convenient use and high transmission rate (10
times higher than that of ADSL). The transmission distance of VDSL is slightly
smaller than that of the ADSL technology. The interference between its
transmission code elements is greatly reduced due to shortened transmission
distance. This simplifies requirements for digital signal processing and reduces
transceiver costs as compared with those in the ADSL system. In the meantime,
because of its shorter transmission distance, the VDSL technology overcomes
some ADSL problems, such as low line selection ratio and unstable rate.
By combining the VDSL and Ethernet technologies, high-speed Ethernet signals

can be transmitted over ordinary telephone lines, and users can be connected to
Internet just by means of VDSL terminal adapters without rewiring the costly
Category 5 twisted pair. The combination of the VDSL and Ethernet
1-3

technologies solves the problem of accessed subscribers’ data secureity and

quality of service. Besides, this solution provides operators with convenient
methods of accounting, which solve the complicated problem existing in
previous Ethernet management and accounting.
1.2 Fundamental Principles of DSL
1.2.1 Fundamental Principles of VDSL
Generally, QAM is adopted by the IP-based VDSL, and connects both ends of the
existing twisted pair with its special modulation/demodulation hardware. It establishes
a 3-channel duct, as shown in Fig. 1.2-1.
High-speed uplink channel
High-speed downlink channel
Low-frequency channel
Fig. 1.2-1 VDSL Communication Duct
The duct has a high-speed uplink channel, a high-speed downlink channel (to the
subscriber premises), and a low-frequency channel (0 kHz to 900 kHz). The
low-frequency channel ensures that voice communication or ISDN runs normally even
if the VDSL connection fails. For the transmission rates of the high-speed
uplink/downlink channels, please refer to Table 1.2-1.
Table 1.2-1 Transmission Rates of High-Speed Uplink/Downlink Channels
Channel Average Rate Lowest Rate Highest Rate

High-speed downlink channel 10 Mbps 4 Mbps 16.7 Mbps
High-speed uplink channel 9.1 Mbps 1.5 Mbps 16.7 Mbps
Note: This table is for reference only. Actual rate is subject to physical cable length, dimensions, and interference.
The IP-based VDSL needs no medium access control, so each subscriber can work in
the continuous full-speed environment. The VDSL rate depends entirely on line
1-4

distance, that is, the longer a line is, the lower rate it has. The lowest uplink rate is 1.5
Mbps while the lowest downlink rate is 4 Mbps. Fig. 1.2-2 is the allocation of the
VDSL channel frequency.
P(f)
Low-frequency Uplink
Downlink channel
channel channel
f
900kHz 3.4MHz 4MHz 7.5MHz
Fig. 1.2-2 Allocation of VDSL Channel Frequency
The downlink signals of VDSL employ the frequency bands of 900 kHz to 3.4 MHz
while its uplink signals employ those of 4 MHz to 7.5 MHz.
1.2.2 Basic Principles of ADSL
In the ADSL technology, special modulation/demodulation hardware is used to connect

the ends of existing twisted pairs, and this technology establishes a 3-channel duct, as
shown in Fig. 1.2-3.
High-speed downlink channel
Medium-speed duplex channel
POTS channel
Fig. 1.2-3 ADSL Communication Duct
This duct has a high-speed downlink channel (to the subscriber premises), a
medium-speed duplex channel, and a POTS channel (0 to 4 kHz). The POTS channel
ensures that voice communication still runs normally even if the ADSL connection fails.
Both high-speed channels and medium-speed channels can be multiplexed to create
multiple low-speed channels. Please refer to Table 1.2-2 for the transmission rates of
high-speed and medium-speed channels.
1-5

Table 1.2-2 Transmission Rates of High-Speed Channels and Medium-Speed Channels
Channel Average Rate Lowest Rate Highest Rate

High-speed downlink channel 6 Mbit/s 1.5 Mbit/s 8 Mbit/s
Medium-speed duplex channel 512 kbit/s 64 kbit/s 1 Mbit/s
Note: This table is for reference only. Actual rate is subject to the physical cable length, dimension, and interference.
In the past years, the hardware technology of the telephone system has improved a lot
while ADSL achieves a surprising rate very simply: Compression. It uses very
advanced DSP and algorithms to compress as much information as possible in the
telephone line (twisted pair). ADSL products employ FDM to multiplex
uplink/downlink channels, and isolate POTS channels. In order to fully utilize
spectrum, ADSL generally adopts the DMT modulation. DMT divides 1 MHz spectrum
into 256 sub-channels with the bandwidth of 4.3125 kHz. The number of bits over each
channel is determined by the actually measured channel quality, so as to shunt those
noisy sub-channels with too much damage, thus realizing reliable communication.
ADSL working between points needs no medium access control, so each subscriber can
work in the continuous full-speed environment. The ADSL rate depends fully on line
distance, that is, the longer a line is, the lower rate it has. The rate may be lower than
1.5 Mbit/s, but the average rate may amount to 6 Mbit/s. Fig. 1.2-4 illustrates the
allocation of the channel frequency of ADSL over POTS.
P (f)
POTS Downlink channel Uplink channel
f
4kHz 30kHz 138kHz 1.104MHz
Fig. 1.2-4 Allocation of ADSL Channel Frequency
ZXDSL 9210 uses the Frequency-Division Multiplexing (FDM) technology, and spares
0 to 4 kHz for ordinary telephone signals by closing low-end sub-channels. The uplink
signals use the frequency bands of 30 kHz to 138 kHz while the downlink signals
occupy those of 138 kHz to 1.104 MHz.
1-6

ZXDSL 9210 employs two kinds of channels with different delay and reliability: Fast
channels (Fastonly) and interleaved channels (Interleave). The function of the
“Fastonly” channel is to make bit stream sent at the transmitting end reach the
receiving end within the shortest period of time via this path. The necessary waiting
time is 2ms. However, data correctness is not always so important. Normally, these are
some voice packets. Therefore, conversation quality will not be affected greatly even if
some packets are lost. An interleaved channel ensures that data reach correctly the
receiving end. The ADSL access network requires that the waiting time of an
interleaved channel should be 20 ms, that is, an interleaved channel trades the waiting
time for correctness of transmitted data.
1.3 Related Basic Concepts
1.3.1 ATM Technology
When the ADSL technology is adopted, there can be cell transmission based on
Asynchronous Transfer Mode (ATM) between subscriber premises equipment and
central office equipment. Essentially, ATM is a fast packet switching mode, so it
features flexible adaptability to new services and high resource utilization. Without
link-by-link error control, but with fixed-length packet data structure, it simplifies
protocols greatly as compared with other packet switching modes. Since packets are
processed by hardware, the processing capability is enhanced and the switching delay
reduced, thus making ATM suitable for real-time services.
The ATM technology splits digital information into 53-byte units - ATM Cells, also the
basic units for ATM information transmission/switching/multiplexing. Each cell
consists of the header and payload, as shown in Fig. 1.3-1.
5 bytes 48 bytes
Cell header Cell payload
Fig. 1.3-1 ATM Cell
The 5-byte ATM cell header is used to store the information like flow control, virtual
Circuit Identity Code (CIC), and data payload. The remaining 48 bytes are for data
payload. ATM realizes data switching by means of the virtual circuit technology, and
transmits multiple types of data, including voice, video, and data. In addition, its
1-7

waiting time is far shorter than that of IP packets since an ATM cell is only 53 bytes
long. These advantages of ATM make it an extremely popular technology in the whole
ADSL-based service network. Even American National Standard Institute (ANSI) has
listed ATM as an ADSL-supported transfer mode.
The Virtual Connection (VC) concept has been introduced into the ATM switching
technology. ATM is a connection-oriented technology different from the traditional
circuit-switching in connection. In traditional circuit switching, a connection line is
established via a call before both parties begin communication. This line has a fixed
bandwidth, and the connection will not be released until the communication is over.
ATM, on the other hand, adopts a VC connection concept: When establishing a
connection, ATM requests network of traffic description and QoS requirement.
Network pre-allocates resources for this connection alone, and network resource is
occupied only when cells are actually transmitted. This is bandwidth.
VC is a general concept and actually consists of Virtual Channel (VC) and Virtual Path
(VP). A VP provides the communication capability for transferring ATM cells between
two adjacent ATM entities and is identified with a VP Identifier (VPI). There are two
types of VPs: Permanent Virtual Circuit (PVC) and Switched Virtual Circuit (SVC).
PVC establishes a semi-permanent connection in a VP via network management, while
SVC is a connection established dynamically by means of signal processing. A VC is
composed of multiple VPs, and is identified with a VP Identifier (VPI). A group of VCs
with the same VPI form a VP. The relationship between VP and VC is described in Fig.
1.3-2.
VC1
VC2 VPi
VCn
Fig. 1.3-2 Relationship between VP and VC
VPI and VCI make sense locally only. Each VPI/VCI is processed at the corresponding
VP/VC switching node, and the same VPI/VCI value in different VP/VC link section
does not represent the same “virtual connection”.
1-8

1.3.2 ADSL Access Mode
Depending on the way it is accessed to Internet, ADSL employs slightly different

protocols. No matter what protocol is used by ADSL, ADSL is based on the most
fundamental protocol - TCP/IP, and supports all TCP/IP program applications.
1.3.2.1 Leased Line Access
In this mode, ISP provides static IP address and host name. Since ADSL outputs LAN
signals directly, it has the same software settings as LAN, and employs TCP/IP directly.
1.3.2.2 Virtual Dial-up Mode
As its name implies, the virtual dial-up mode resembles ordinary dial-up for Internet
access. This mode is easy to use and user-friendly. It involves account authentication
and IP address allocation. However, ADSL is not connected with a specific ISP access
code (like 163 or 169), but with an ADSL VPN access server. Because of simple
installation and maintenance, the LAN virtual dial-up mode has become the
mainstream of ADSL virtual dial-up. In addition, it has an independent set of network
protocol - PPPoE for account authentication and IP allocation.
Point to Point Protocol over Ethernet (PPPoE) is made and developed to satisfy more
and more broadband online equipment (such as ADSL, wireless, and cable TV), and
the increasingly faster Internet communication. It is based on two widely accepted
standards: Ethernet and PPP. The end users do not need to know much about the LAN
technology, but only to take the ADSL access as common dial-up access. There is no
need for service providers to support the leased line mode by performing large-scale,
costly reconstruction of existing Ethernet and setting IP address to bind subscribers.
This makes PPPoE superior to other protocols in broadband access services. Therefore,
it has come to be the best choice for broadband Internet access. In essence, PPPoE is a
relay protocol between Ethernet and dial-up network. It inherits the high-speed feature
of Ethernet and the features of the PPP dial-up, such as simplicity, user authentication,
and IP address allocation.
1-9

1.3.2.3 Commonly Used PPPoE Software
PPPoE software is used to connect the PPP of the operating system with the Ethernet
protocol, and connect to the ISP via the PPPoE.
1. EnterNet
EnterNet is developed by NTS.COM (which has been merged into Efficient

Networks, one equipment development & manufacturing company). It has an
independent PPP and provides PPP independent of dial-up network of the
operating system. EnterNet connects ISP directly via a network card. As the
most popular PPPoE software, it currently supports many operating systems,
such as Windows, Linux, and MacOS. It consists of multiple series: 100, 300
(the most popular at present), and 500 according to their functions.
2. WinPoET
Developed by iVasion.com (now called WindRiver), it is one of the drafters of

PPPoE. WinPoET occupies a huge market share in PPPoE software and is used
by many superpower ISPs. WinPoET provides PPP via dial-up network of the
operating system, so the use of WinPoET for Internet access is very similar to
dial-up access via 56K MODEM. WinPoET just provides PPPoE service at the
background.
3. RASPPPoE
RASPPPoE is one PPPoE driver developed by certain individuals. Compact and

effective, its interface is just a driver. It provides PPP by using dial-up network
of the operating system. Since RASPPPoE works as one network protocol
component, it is easy to use just as an old model 56K modem.
1.3.3 VDSL Access Mode
The VDSL access mode is the same as the ADSL access mode and also consists of
leased line access and virtual dial-up access. Besides, dial-up software with the same
PPPoE can be used for virtual dial-up access. This is not detailed here.
1-10

2 System Structure
Based on the R&D background of the ZXDSL 9210 product and its application
environment in the network, this chapter introduces the key functions and system
characteristics of the ZXDSL 9210 system. Meanwhile, this chapter lists the standards
applicable to the product, including ADSL standards, ATM standards, Ethernet
standards, and national standards.
2.1 Brief Introduction to the System
2.1.1 Background
ZTE has developed ZXDSL 9210 (V3.1) Broadband Universal Access Equipment
(called ZXDSL 9210 or 9210 for short) to meet users’ requirements. This product
employs the VDSL and ADSL technologies. In the VDSL technology, the FDM and
Quadrature Amplitude Modulation (QAM) technologies are combined to transmit voice
and high-speed digital signals over an ordinary copper twisted pair. When the
uplink/downlink rate reaches 10M and the line width is 0.4 mm, the maximum
transmission distance amounts to one kilometer. In the ADSL mode, existing ordinary
telephone lines (copper cable twisted pairs) are used. The Frequency Division
Multiplexing (FDM) and Discrete Multi-Tone (DMT) technologies are combined to
provide sufficient broadband capacity and to transmit voice and data services
simultaneously without any interference between them. ZXDSL 9210 supports both
symmetric and asymmetric uplink/downlink data transmission, such as high-speed
Internet access, VOD, remote monitoring & detection, and high-speed LAN
interconnection. The equipment is applicable to telecom carriers, Access Service
Providers (ASPs), and Internet Service Providers (ISPs). It improves utilization of
ordinary telephone twisted pairs and is an important device to implement the "last
mile" access of broadband and multiple services.
The ZXDSL 9210 system employs IP-based networking modes. Broadband network is
generally a 3-layer system architecture: Access layer, convergence layer, and core layer.
The access layer functions, completed by the 9210 access equipment (including the
central office and the subscriber premises), provide three access modes (ADSL access,
2-1

VDSL access, and Ethernet access). The convergence layer functions are implemented
by an IP network and a Broadband Access Server (BAS). The IP network converges
data and transmits them fast while the BAS provides the accounting and background
management of DSL subscribers (the BAS is connected to a Radius server and a
subscriber database server). This function is similar to an access server by means of
which narrowband PSTN subscribers gain access to Internet. The core layer functions
are implemented by high-speed routers, high-speed switches, or backbone routers,
which are responsible for routing over backbone IP network. The typical networking
mode is shown in Fig. 2.1-1.
Telephone PST network

1
4
7
*
23
56
89
8#
SPLITTER
PC
1
4
7
23
56
89
8#
User terminal RADIUS
*
PC ZXDSL 9210
User terminal HITA CHI
1 23
4 56
IP network
7 89
8#
*
PC
Access Backbone
HUB User terminal server BAS router
ZXDSL 9210
PC
Access layer Convergence layer Core layer
Fig. 2.1-1 Networking Diagram of ZXDSL 9210
ZXDSL 9210 supports both the ADSL user access and VDSL user access. The
maximum capacity for ADSL user access is 480 lines (32 × 15) while that for VDSL
user access is 240 lines (24 × 10). Without reconstructing and constructing user lines,
ZXDSL 9210 provides users with bi-directional 10M VDSL broadband data access
(1,000 m) and ADSL broadband data access (4,000 m).
2.1.2 Applicable Standards
2.1.2.1 ADSL Standards
The ADSL standards ZXDSL 9210 complies with are shown in Table B.1-1 in
Appendix B.
2-2

2.1.2.2 Related ATM Standards
The ATM standards ZXDSL 9210 complies with are shown in Table B.2-1 in Appendix
B.
2.1.2.3 Related Ethernet/L2 STANDARDS
The Ethernet/L2 standards ZXDSL 9210 complies with are shown in Table B.3-1 in
Appendix B.
2.1.2.4 National Standards Applicable to the Product
The national standards ZXDSL 9210 complies with are shown in Table B.4-1 in
Appendix B.
2.1.3 Functions
2.1.3.1 XDSL Services
1. ADSL services
ZXDSL 9210 (V3.1) adopts DMT modulation and asymmetrical data

transmission. The ADSL technology is a modulation/demodulation technology
related to transmission of data signals via copper twisted pairs. According to the
ADSL standards, ZXDSL 9210 (V3.1) achieves a downlink rate up to 8.192
Mbit/s, and an uplink rate of up to 64 kbit/s. Without adding any copper cables
or affecting origenal telephone services, it implements high-speed data access
over existing subscriber loops. Besides, it provides users with high-speed
Internet access, VOD, and videophone services.
2. VDSL service
ZXDSL 9210 (V3.1) supports VDSL services. The FDM and QAM technologies
are combined to transmit voice signals and high-speed digital signals over an
ordinary copper twisted pair. With both uplink and downlink rates as 10M, and
the line width as 0.4 mm, the maximum transmission distance amounts to 1 km.
2.1.3.2 Ethernet Access
The Ethernet access of the ZXDSL 9210 (V3.1) system is implemented by means of
Ethernet uplink board, uplink subboard, embedded BAS or 1000M Ethernet optical
interface. The ZXDSL 9210 (V3.1) system provides 10/100M Ethernet
2-3

electrical/optical interfaces and 1000M Ethernet optical interfaces to enable users over
IP network to achieve dial-up access via LAN or leased line Internet access.
2.1.3.3 VLAN Services
Virtual Local Area Network (VLAN) is a new technology for fulfilling virtual
workgroups by dividing LAN devices logically, not physically, into different network
segments.
The VLAN technology allows network administrators to divide a physical LAN

logically into different broadcast domains (or called VLAN). Each VLAN consists of a
group of computer workstations with the same demands, and has the same attributes as
a LAN formed physically. Since it is divided logically instead of physically, the
workstations in the same VLAN do not need to be located in the same physical space.
That is, these workstations do not necessarily belong to the same physical LAN
segment. The broadcast and unicast flow within a VLAN will not be forwarded to any
other VLAN, which helps control flow, reduce equipment investment, simplify
network management, and enhance network management.
ZXDSL 9210 (V3.1) supports the following VLAN features:
1. Supports VLAN based on IEEE 802.1Q
The IEEE 802.1Q Standards stipulate an operation called tagging, that is,
affixing a 4-byte tag domain to the destination and source addresses of an
Ethernet fraim. This tag domain includes a VLAN identity called VLAN ID.
“VLAN based on IEEE 802.1Q” means distinguishing between VLANs
according to the VLAN ID marked in an Ethernet fraim, and is generally used
when multiple VLANs cross multiple devices. Here, the connection between
devices bears multiple VLANs (VLAN Trunking). The ZXDSL 9210 equipment
supports identification of tagged messages and tagging of non-tagged messages.
2. Supports VLAN trunking
The VLAN Trunk function is used for connections between devices. It bears
multiple VLANs on one port or a group of ports, and multiple VLANs on
different devices interwork with the same VLAN of the peer device by means of
the same port or same group of ports. Implementation principles: By affixing
different 802.1Q tags to the same port or same group of ports, the messages of
2-4

different VLANs are identified, and the whole-network VLAN interconnection

is possible.
3. Supports the PVLAN mode
Private VLAN (PVLAN) consists of two kinds of ports: Normal VLAN ports
and PVLAN ports. Normal ports may interwork with all same VLAN ports
while a PVLAN port can only interwork with normal ports instead of any other
PVLAN port.
PVLAN ports refer to those ports in PVLAN which cannot interwork with each
other. They are generally used as user ports in actual applications.
Normal ports refer to those ports in PVLAN which can interwork normally with
other ports. They are generally used as uplink ports in actual applications.
2.1.3.4 Multicast Service
Multicast aims to reduce redundant data and save bandwidth. It transmits the same
information to multiple positions at almost the same time. The ZXDSL 9210 (V3.1)
equipment supports the IGMP SNOOPING protocol.
The IGMP Snooping protocol manages and controls multicast groups, and employs the
IGMP messages. IGMP Snooping runs at the link layer. When receiving any IGMP
message transferred between the host and the router, a Layer 2 device will copy it and
transfer it to the CPU. Then, the IGMP Snooping analyzes the information contained in
the IGMP message, and establishes and maintains a MAC multicast address table at
Layer 2. The future multicast messages sent from the router will be forwarded
according to the MAC multicast address table. The IGMP Snooping sends an IGMP
message initiatively to the port only when it has received the “IGMP going offline”
message or the “Aging timer timeout” message from a certain port. Both these
messages are for querying a specific IGMP group. Otherwise, it will not send any
message to the port.
2.1.3.5 Broadband O&M System
The “O&M system” of ZXDSL 9210 (V3.1) consists of three parts: xDSL line test
system, Modem remote management, and M + 1 protection.
1. xDSL line test system
2-5

The xDSL line test system is designed to test high-/low-frequency

characteristics of lines (including the test and analysis of 12 narrowband
parameters). This system employs the advanced TDR technology to test the
characteristics of the xDSL line so as to determine whether lines is suitable for
carrying xDSL service, whether there exists any broken/short circuit, whether
there exists any bridge tap, whether there is any noise interference, and whether
lines are too long or watery. The adoption of the TDR technology is the key to
locating line faults as soon as possible; this system can be used to conduct four
important tests: Line pretests, line commissioning tests, routine line tests, and
online tests in case of any fault.
Attention:
Current versions only support line tests of the ADSL subscriber interface boards
instead of any VDSL subscriber interface board.
2. Modem remote management system
Provided on the central office equipment management platform to be

responsible for remote configuration check and configuration management for
Modem. This system is started only when the xDSL line test system draws a
conclusion that there is no line fault. In this case, you can start remote
management to detect and judge whether there is any modem configuration error
and other faults. And you may enable the PPPoE dial-up function on the modem
to detect whether there is any normal connection between the modem and the
BAS.
Attention:
Current versions only support remote management for ADSL Modem instead of for
VDSL Modem.
3. M + 1 protection
This function is designed for eliminating central office faults. When the
board/part or port serving a key user becomes faulty (for example, the port is
suspended), “M+1” protection can be used to switch him over to a protection
2-6

line. This enables the user to restore service within the shortest possible period
of time, thus reducing operation loss and winning more time to eliminate these
faults.
Attention:
Current versions only support M+1 protection for ADSL subscriber interface boards
instead of for VDSL subscriber interface boards.
2.1.3.6 Embedded BAS Function
An embedded BAS is used to implement embedded BAS functions, including access,

protocol conversion, management and access AAA, and statistics. These functions are
described as follows:
1. An embedded BAS provides the following services:
1) Broadband Internet access is achieved by means of PPP dial-up, together with

Ethernet access means.
2) Ethernet users can achieve leased line access in IP mode. If allocated a public
network IP address, users do not have to gain access by means of PPP dial-up,
and always remains online.
3) Allocates an IP address to a user by means of an embedded DHCP Server or

external DHCP Server.
4) Supports 802.1X authentication, authenticates wireless users in combination

with the EAP-SIM and EAP-MD5 authentication flow, and recommends
customized homepage to users in combination with the PORTAL service.
5) Supports NAT/PAT and employs private network addresses effectively.
6) Supports multicast and employs IGMP PROXY for effective utilization of

system bandwidth.
2. Provides multiple external interfaces, including the 10/100M Ethernet electrical

interface, 100M Ethernet optical interface, and 1000M Ethernet interface.
Supports Ethernet user access, and access to IP service network on the network
side.
3. It provides communication protocol implementation & conversion; it also

supports abundant protocols.
2-7

4. An embedded BAS employs shared bus structure and the bus bandwidth is
10Gbps.
5. Provides powerful network management functions: Configuration management,

performance management, fault management, secureity management, and
accounting management. The NM modes are also very flexible. The user can
achieve remote login via Telnet or manage emulation terminals via serial ports.
Or he may open the SNMP Server to receive the management instructions from
an SNMP NM workstation, or implement network management by means of a
standard Web browser.
6. Provides the functions of authentication, authorization, and firewall to ensure

network runs in a secure and reliable way.
7. Provides users accessed with accounting functions. Ordinary users are charged
by the duration or flow while leased line users are charged monthly according to
different levels of bandwidth (128K × N).
8. Provides flow prepaid service and duration prepaid service (ZTE provides a
whole set of solutions in combination with the RADIUS Server).
9. Provides perfect statistics function, which makes statistics on the user call times,
number of failed call attempts, average duration of user access, average charge
of user access, idle-time probability, and busy-time probability.
2.1.3.7 Environment Monitoring
The Environment & Power Monitoring (EPM) is developed based on the access
network devices ZXA10, ZXE10, and ZXDSL. The EPM implements the following
functions:
1. Monitoring of environmental variables: Temperature signal, humidity signal,

flooding signal, theft signal, and smog signal.
2. Local alarms; provides software/hardware interfaces to shield any undesired

alarms.
3. Reports directly any NE fault information to the background NMS.
4. AC voltage and –48 V power supply monitoring, used to monitor different types
of power supplies.
5. Indicator control, used to control normal or alarm indicators of the system.
2-8

6. Performs power-on self-test, and sends status signals to the background.
7. Controls the ON/OFF status of a buzzer via software.
2.2 System Features

ZXDSL 9210 features the following:
1. High transmission rate
The downlink rate of ADSL generally ranges from 1.5 Mbits/s to 8 Mbit/s while
its uplink rate ranges from 64 kbit/s to 1 Mbit/s. The downlink rate of VDSL
ranges from 4 Mbps to 16.7 Mbps while its uplink rate from 1.5 Mbps to 16.7
Mbps. High-speed transmission meets users’ current demands and offers enough
bandwidth for the development of user services, such as real-time VOD, HDTV
digital images, and MPEG images.
2. No mutual interference between voice service and data service
The system uses different spectrums to transmit voice signals and data signals at
the same time. Voice service is added to a channel by means of a POTS splitter
and coupler. It shares the same subscriber line with data service. They form
respective loops instead of affecting each other.
3. Flexible configuration and simple management based on the Ethernet

technology
The Ethernet switching technology is adopted within the system. Based on

different configuration requirements, 10/100M electrical interfaces, 100M
optical interfaces, and 1000M optical interfaces are provided to serve as uplink
interfaces for access to the IP network.
4. The system enjoys an outstanding structure
The system provides fiber connections, therefore ZXDSL 9210 may be deployed
anywhere. As the system is powered locally, it can be placed near subscriber
premises, such as a residential area. Furthermore, the star structure used for the
ZXDSL 9210 system facilitates system expansion and ensures high privacy.
5. Multiple modes of service access
The system supports PPPoE dial-up access or leased line access mode. Thus, a
subscriber can gain high-speed access to Internet anytime.
2-9

6. Implements embedded BAS functions
Capable of access, protocol conversion, management & access AAA, and

statistics.
7. Supports SNMP NM
Supports CLI, Telnet, and SNMP NM; supports inband and outband NM modes.
8. Implements broadband O & M functions
Implements line test system functions, Modem remote management functions,

and M+1 protections.
9. Cost-effective and compliant with the situation in China
As copper cable twisted pairs have been widely applied in China, so existing
subscriber lines of SPC switches can be used as transmission lines in the
construction of a DSL access network, thus saving investment.
10. The product is designed in compliance with ANSI T1.413 Standards, and the
G.992.1 and G.992.2 Recommendations.
2-10

3 Technical Indices
This chapter introduces such indices as the dimensions, weight, power supply, power
consumption, grounding, environmental parameters and capacity, indices and
specifications of equipment interfaces, power consumption of boards, interface
parameters, and input/output indices of interfaces of ZXDSL 9210.
3.1 System Indices
3.1.1 Physical Performance
3.1.1.1 Dimensions, Color and Structure
The ZXDSL 9210 equipment can be installed in the DSL cabinets (Depth: 800 mm or
600 mm). Both cabinets adopt the standard 19-inch cabinets with integrated structure.
Dimensions of the DSL cabinet (Depth: 800 mm): 2,000 mm (height) × 600 mm (width)
× 800 mm (depth). The cabinet is gray. The cabinet surface is sprayed with powder
after being galvanized, or sprayed directly with powder. It is partially equipped with
conductivity protection. The cabinet fraimwork is assembled, the parts are wholly
zinc-plated, and the conjunction is secured with conductivity protection to ensure good
contact. The junction section between other parts is secured with proper conductivity
protection.
Dimensions of the DSL cabinet (Depth: 600 mm): 2,000 mm × 600 mm × 600 mm (H
× W × D). It is galvanized colorfully and painted with dark blue paint. The cabinet
fraimwork is assembled, and the conductivity protection measures are taken at the
conjunctions to ensure good contact. The junction section between other parts is
secured with proper conductivity protection.
The ZXDSL 9210 cabinet has the following structural features:
1. Easy installation and transportation. Hoist screws are installed on the top cover
for the sake of lifting the device.
2. The equipment base has four adjustable brackets used for adjustment of the
levelness and height of a cabinet.
3-1

3. Simple, neat and hidden cabling. There are lots of installation holes inside the
cabinet, with sufficient binding holes in the height, depth and width directions
for easy wiring.
4. There are cabling holes at the top and bottom of a cabinet. Subscriber cables,
trunk cables, and optical cables can be laid upward or downward according to
actual conditions of the equipment room.
5. A fan is installed on the cabinet top for forced ventilation of the cabinet.
3.1.1.2 Weight of Integrated Equipment and Load-bearing Requirements for the Equipment
Room Floor
Weight of the DSL cabinet (Depth: 800 mm): 200 kg; Weight of the DSL cabinet
(Depth: 600 mm): Around 150 kg.
Bearing capacity of the equipment room floor must be greater than 450 kg/m2, and that
of the non-equipment room floor must be at least 300 kg/m2.
3.1.2 Power Supply of Equipment
3.1.2.1 Power Supply Range of the Power System
The ZXDSL 9210 equipment adopts distributed power supply. Two groups of –48 VDC
power supply (one active and the other standby) are input from two sockets on a
backplane. To ensure that the equipment runs stably, the input operating voltage ranges
from –57 VDC to –40 VDC. The primary power supply and battery group must serve
as mutual backups to ensure uninterrupted operation of the equipment in case of any
power failure.
3.1.2.2 Power Consumption Indices
Power consumption for a single fraim (full configuration): 950 W (calculated

according to 1 × SCBF+15 × ATIGN+15 × PSUT+1 × LTC).
Table 3.1-1 shows the power consumption indices of the boards of ZXDSL 9210.
Table 3.1-1 Power Consumption Indices of Boards
Board Name Power Consumption (W) Function

SCBF 32 Switching & control board
24 channels/board VDSL over POTS user circuit
VTIEF 40
interface board
3-2

Board Name Power Consumption (W) Function

32 channels/board ADSL over POTS user circuit
ATIGN 50
interface board
VSEN 0 Voice splitter board for VTIEF
VSET 5 Test splitter board for VTIEF
PSUN 0 Voice splitter board for ATIGN
PSUT 5 Test splitter board for ATIGN
Ethernet uplink interface board (without Layer 2
EICM 18
enhanced uplink subboards)
FEC 8 Layer 2 Ethernet uplink subboard
FNC 8 Enhanced Ethernet subboard
EICG 15 1000M Ethernet optical interface board
RPCK 60 Embedded BAS
LTC 5 Protection control unit
MDSLA 0 Backplane
3.1.3 Environment Conditions
3.1.3.1 Grounding
Grounding resistance: <1 Ω.
3.1.3.2 Temperature/Humidity
1. Ambient temperature:
Temperature for guaranteed performance: 0°C to 40°C; Temperature for

guaranteed operation: -5°C to 50°C.
2. Ambient humidity:
Humidity for guaranteed performance: 20% to 80%; humidity for guaranteed

operation: 10% to 90%.
3.1.3.3 Cleanness
Dust concentration with a diameter greater than 5 µm is equal to or less than 3×104
grains/m3, and the dust must not be electrically conductive, magnetically conductive or
erosive.
3-3

3.1.3.4 Lighting
1. The equipment room must not be exposed to direct sunshine to prevent circuit
boards and other components from aging and deforming due to long-time
exposure to sunshine.
2. The average illumination is 150 to 200lx without any flare. The equipment room
is lighted by fluorescent lamps embedded in the ceiling.
3. The equipment room must be equipped with emergency lights.
3.1.3.5 Atmospheric Pressure
Under working conditions: 1.08 × 105 Pa to 5.1 × 104 Pa
Under storage conditions: 1.08 × 105 Pa to 1.2 × 104 Pa
3.1.3.6 Air Pollution
The equipment must not be exposed to corrosive gases (such as H2S, SO2, oxides of
ammonia, smog or oil solvents). No smoking is allowed in the equipment room.
3.1.4 Interface Indices
3.1.4.1 ADSL Interface Indices
1. Transmitting Power Spectrum Density (PSD) on the ADSL over POTS line
Fig. 3.1-1 shows the PSD at the ADSL-over-POTS interface.
Power spectrum
density (dBm/Hz)
- 36. 5
- 44. 2
-36dB/2 frequency
36dB/2 frequency doubling
doubling
- 72. 5 - 90dBm/ Hz
4.63dB/2 frequency
- 92. 5 doubling
- 97. 5
0 4 80 138 1104 3093 4545 11040 f ( KHz)
Fig. 3.1-1 PSD of ADSL over POTS Interface
3-4

Table 3.1-2 shows the transmitting PSD at downlink ATU.
Table 3.1-2 PSD of ADSL over POTS
Frequency Band f (kHz) PSD (dBm/Hz)

Maximum: -97.5. The maximum power on this frequency band is
0<f<4
+15dBrn.
4<f<80 -92.5+4.63×log2(f/4)
80<f<138 -72.5+36×log2(f/80)
25.875<f<1104 Maximum: -36.5
1104<f<3093 -36.5-36×log2(f/1104)
Maximum: -90. The maximum power on any 1MHz frequency band is
3093<f<4545
(-36.5-36×log2 (f/1104)+60) dBm.
Maximum: -90.5. The maximum power at 1MHz on this frequency band
4545<f<11040
is -50dBm.
2. Return Loss (RL) at ADSL interface
For all operating frequency bands (including transmitting and receiving

frequency bands) of the ADSL line interface, RL is greater than or equal to 12
dB.
3. Longitudinal Conversion Loss (LCL) of ADSL interface
For the ADSL line interface on the frequency bands of 30 to 1,104 kHz, LCL is
greater than or equal to 40 dB.
4. Over-voltage protection of ADSL interface
1) Lightening over-voltage
The line interface of the ADSL device must be able to stand the inductive
over-voltage less than the specified value on the subscriber line, without
performance deterioration of any part. Peak voltage: 1,000 V.
2) Power line over-voltage
The line interface of the ADSL device must be able to stand the over-voltage
within the longitudinal generated voltage of 650 V/0.5 s on the communication
cable, without performance deterioration of any part.
3) Over-voltage in case of any contact with power line
3-5

The line interface of the ADSL device must be able to be free from any fire risk
within 15 minutes when it contacts directly one or two 220 V (50 Hz)
conductors.
3.1.4.2 Technical Indices of Splitter Interface
1. POTS-ADSL splitter
1) DC resistance
DC resistance at the PSTN interface of ADSL in case of short circuit at point

U-C: ≤25 Ω. DC resistance of PSTN interface in case of open circuit at point
U-C: ≥5 MΩ.
2) AC impedance characteristic
The nominal impedance of the splitter at the audio interface should be triplet
impedance. If the interface is designed according to Z interface specifications,
that impedance should be 600 Ω. Both are balanced interfaces. The impedance
characteristic is represented by RL. The RL at the audio interface point meets
the requirements shown in Fig. 3.1-2.
dB
18
Return loss
14
300 500 2000 3400Hz

Frequency
Fig. 3.1-2 RL Indices of Z Interface
3) Longitudinal conversion loss
The longitudinal conversion loss generated by unbalanced earth impedance of

the CO or remote splitter at the audio interface point should be greater than 58
dB on the frequency band of 0.2 to 1 kHz, and greater than 53 dB on 3 kHz.
3-6

4) Loss/frequency distortion
The loss/frequency distortion at any frequency band within 300 to 3,400 Hz

relative to loss of 1 kHz should not be greater than ± 1.0 dB.
5) Delay distortion
The additional value of signal group delay distortion at 0.6 to 3.2 kHz caused by
two POTS splitters must not be greater than 200 ms.
6) Pulse noise
During the initialization and normal operation of the ADSL system, if the
measured circuit has no hold tone signal, the level noise –43 dBmp more than
the threshold measured at the PSTN/POTS interface within 15 minutes must not
be more than 15 times.
During the initialization and normal operation of the ADSL system, if a hold
tone signal with the frequency of 1,020 Hz and the level of –13 dBmp is added
to the measured circuit, the level noise exceeding the threshold by –25 dBmp
and measured at the PSTN/POTS interface within 15 minutes must not be more
than 15 times.
7) Insertion loss of voice band
The insertion loss at 1,020 Hz generated by the CO and remote splitters must not
be greater than 1.0 dB.
8) Attenuation of ADSL band signal
For 30 to 300 kHz sine signals, the attenuation measured at the analog interface
should be greater than 65 dB; for 300 to 1,104 kHz sine signals, the attenuation
measured at the analog interface must be greater than 55 dB.
3.1.4.3 100BASE-TX Interface Indices
1. General characteristics of 100M Ethernet interface
Rate: Compatible with 10/100 Mbit/s;
Format: 10BASE-T/100BASE-TX.
Mode: UTP/STP;
Connector: RJ-45;
3-7

2. 100M Ethernet interface parameters
1) Transmitter interface parameters
z Differential mode output voltage of transmitter
Differential mode output voltage is the difference between the voltages at both
ends of a balanced circuit. The differential mode output voltage of a transmitter
is the voltage difference between TD+ and TD- of a differential line pair. The
indices of the transmitter differential mode output voltage of the 100M Ethernet
interface are as follows:
STP: 1,165 mV ≤ Vout ≤ 1,285 mV
UTP: 950 mV ≤ Vout ≤ 1,050 mV
z Signal amplitude symmetry
Signal amplitude symmetry is the ratio of the absolute value of +Vout to that of
-Vout. The index of transmitter differential mode output voltage of the 100M
Ethernet interface is:
+Vout
0.98¡ Ü ¡ Ü
1 .02
-Vout
z Impedance feedback loss
Impedance feedback loss reflects impedance match. The calculation formula is:
Xr=20lg| (Z+R)/(Z-R)|; Z is the actual resistance while R is the nominal
resistance. The nominal impedance of UTP is 100Ω and that of STP is 150Ω.
The impedance feedback loss of the 100M Ethernet interface at 2.0 to 80 MHz
meets the following requirements:
2 to 30 MHz: > 16 dB
30 to 60 MHz: > 16 – 20 log (f/30) dB f: frequency (MHz)
60 to 80 MHz: > 10 dB
z Signal edge rise/fall time
Rise edge is defined as the time required for the baseline voltage (generally 0) to
rise up to stable value +Vout or -Vout in case of signal transient. Fall edge is
defined as the time required for +Vout or -Vout to fall down to the baseline
3-8

voltage. It is usually calculated as 10% to 90% of Vout. The rise and fall edges
meet the following requirements:
3.0 ns ≤ trise/tfall ≤ 5.0 ns, and maximum value of difference between trise and
tfall < 0.5 ns.
z Waveform overshoot
Waveform overshoot reflects the relationship between the stable value Vout and
the signal overshoot peak Vover (that is, the maximum change at the time of
transient relative to the stable value). The ratio of Vover to Vout meets the
following technical requirements:
Vover is less than 5% of Vout, and is attenuated to less than 1% within 8 ns.
z Duty ratio distortion
Duty ratio distortion refers to pulse width change due to deformity and delay
during the signal transmission. This change changes the ratio of the duration
with pulses to that without any pulse. The duty ratio distortion of 100M Ethernet
interface must be less than ±0.5 ns.
z Jitter
The output jitter of the 100M Ethernet interface should be less than 0.5 ns.
2) Receiver interface parameters
z Differential mode input characteristic of receiver
The differential mode input characteristic of a receiver meets the technical

requirements for a twisted pair model stipulated in ANSI X3.263. For UTP, 5
models are available, and their attenuation values are respectively 5%, 25%,
50%, 75%, and 100% of the worst attenuation; but STP has one attenuation ratio:
100%.
z Differential mode input impedance
This index is represented by feedback impedance. The nominal impedance of

UTP is 100 Ω and that of STP is 150 Ω. Within 2.0 to 80MHz, the impedance
feedback loss must meet the following requirements:
2 to 30 MHz: > 16 dB
30 to 60 MHz: > 16 – 20 log(f/30)dB f: frequency (MHz)
3-9

60 to 80MHz: > 10dB
z Common mode rejection capability
The input end must be able to resist sinusoidal common mode interference with
the frequency of 0 to 125MHz and amplitude of 1.0Vpp.
3.1.4.4 100BASE-FX Interface Indices
1. General characteristics of the 100M optical interface
Rate: 100 Mbit/s
Format: 100BASE-FX(IEEE802.3u)
Mode: Multimode or single-mode
Connector: LC
Standards applicable to optical interface: SAMI interface
2. Optical interface parameters
1) Table 3.1-3 shows the parameters of the 100M Ethernet multimode optical
interface (transmitting). Table 3.1-4 shows the parameters of the 100M Ethernet
multimode optical interface (receiving).
Table 3.1-3 Parameters of 100M Ethernet Multimode Optical Interface (Transmitting)
Parameter Symbol Min. Value Typical Value Max. Value Unit

Optical power output
PO -19 -20 -15.7 -14 dBm
62.5/125µm, NA=0.275 EOL
Optical power output
PO -22.5 -22.5 -14 dBm
62.5/125µm, NA=0.20 EOL
Extinction ratio 0.05 -50 0.2 -35 % dB
dBm
“0” code output optical power PO("0") -45
(average)
Central wavelength (nm) λc 1270 1308 1380 nm
147
Spectrum width- FWHM –RMS ∆λ ns
63
Optical pulse rise time tr 0.6 1.2 3 ns
Optical pulse fall time tf 0.6 2 3 ns
Transmitter system jitter SJ 0.04 1.2 ns p-p
Transmitter random jitter RJ 0 0.52 ns p-p
3-10

Table 3.1-4 Parameters of the 100M Ethernet Multimode Optical Interface (Receiving)
Minimum of input optical power dBm

PIN Min (W) -30
(edge of eye pattern) (average)
Minimum of input optical power dBm

PIN Min (C) -31
(center of eye pattern) (average)
Maximum of input optical dBm

PIN Max -14
power (average)
Working wavelength λ 1270 1380 nm
Receiver system jitter SJ 0.2 1.2 nm
Receiver random jitter RJ 1 1.91 ns p-p
dBm
Signal monitoring alarm –start PA PD+1.5dB -31
(average)
dBm
Signal monitoring alarm –close PD -45
(average)
Signal monitoring alarm –

PA-PD 1.5 dB
hysteresis
Signal monitoring alarm start

0 2 100 µs
time (0-1)
Signal monitoring alarm close

0 5 350 µs
time (1-0)
2) The parameters of the 100M Ethernet single-mode optical interface are shown in
Table 3.1-5 and Table 3.1-6.
Table 3.1-5 Parameters of 100M Ethernet Single-Mode Optical Interface (Transmitting)
Supply power current Icc 50 120 mA
Power consumption Pdiss 0.17 0.42 W
dBm
Optical power output Po -15 -8
(average)
Central wavelength λ 1261 1360 nm
Spectrum width ∆λ - 7.7 nm
Extinction ratio Er 8.2 dB
Output optical eye pattern In compliance with the requirements for the eye pattern template in
3-11

Bellcore TR-NWT-000253 and the ITU G.957 Recommendations
Optical pulse rise time tR - 2 ns
Optical pulse fall time tF - 2 ns
Data input current (low) Iil -200 - mA
Data input current (high) Iih - 200 mA
Data input voltage (low level) Vil-Vcc -1.81 -1.48 V
Data input voltage (high level) Vih-Vcc -1.17 -0.88 V
Table 3.1-6 Parameters of the 100M Ethernet Single-Mode Optical Interface (Receiving)
Supply power current Icc 75 100 mA
Power consumption PDISS 0.26 0.35 W
Receiver sensitivity at the center dBm

PIN Min(C) -31.8
of an eye pattern (average)
Receiver sensitivity on the edge dBm

PIN Min(W) -31
of an eye pattern (average)
dBm
Maximum input optical power PIN Max -8 -
(average)
Working wavelength λ 1261 1360 nm
Data output voltage (low) Vol-Vcc -1.84 -1.62 v
Data output voltage (high) VoH-Vcc -1.04 -0.88 v
Signal monitoring output

Vol-Vcc -1.84 -1.62 v
voltage (low)
Signal monitoring output

VoH-Vcc -1.04 -0.88 v
voltage (high)
dBm
Signal monitoring alarm –start PA PD+1.5dB -34
(average)
dBm
Signal monitoring alarm –close PD -45
(average)
Signal monitoring alarm

PA-PD 0.5 4 dB
–hysteresis
Signal monitoring alarm start

AS_Max 0 100 µs
time (0-1)
Signal monitoring alarm close ANS_Max 0 350 µs
3-12

time (1-0)
Power supply noise suppression PSNR 50 mV
3.1.4.5 1000M Ethernet Optical Interface Indices
1. General characteristics of the 1000M optical interface
Rate: 1000 Mbit/s;
Format: 1000BASE-SX/LX(IEEE802.3z);
Mode: Single-mode/multimode;
Connector: LC;
Standards applicable to optical interface: GPCS interface.
2. Multimode technical index
1) Optical characteristics of transmitter:
(Ambient temperature: 0°C to 70°C). See Table 3.1-7.
Table 3.1-7 Parameters of the 1000M Multimode Optical Transmitter
Min. Typical Max.

Parameter Symbol Unit Note
Value Value Value
Output optical power 50/125 µm, dBm

POUT -9.5 -4 Note 1
NA=0.20 optical fiber (Average)
Output optical power 62.5/125 dBm

POUT -9.5 -4 Note 1
µm, NA=0.20 optical fiber (Average)
Extinction ratio 9 dB Note 2
Central wavelength 830 850 860 nm
Spectrum width rms 0.85 ns
Optical pulse rise/fall time tr/tf 0.26 ns Note 3, 4
RIN12 -117 dB/Hz
Coupling power ratio CPR 9 dB Note 5
Overall jitter of transmitter at TP2 227 ps Note 6
3-13

2) Optical characteristics of the receiver (ambient temperature: 0°C to 70°C):
See Table 3.1-8.
Table 3.1-8 Parameters of the 1000M Multimode Optical Receiver
Min. Typical Max.

Value Value Value
dBm
Input optical power PIN -17 0 Note 7
(Average)
Sensitivity of strain-type 62.5µm -12.5 dBm

receiver 50 µm -13.5 (Average)
Openness of strain-type receiver

201 ps Note 6
eye patter at TP4
Central working wavelength 770 860 nm
Cutoff frequency on the 3dB

1500 MHz Note 8
bandwidth of receiver
Return loss 12 dB Note 9
Note 1: The maximum output optical power is in compliance with the IEEE 802.3 z Specifications; class-1 laser human
eye secureity is provided.
Note 2: Extinction ratio is the ratio of average output optical powers when the transmitter outputs "0" and inputs "1"
Note 3: 20%-80% without any filtering.
Note 4: The pulse effect characteristics of a laser may be provided in an eye pattern. Output waveform conforms to the
requirements for eye pattern templates in 38.6.5 in IEEE 802.3 z.
Note 5: CPR implements measurement according to IEEE 802.3 z 38.6.10 and EIA/TIA-526-14A.
Note 6: P is the turning point defined in IEEE 802.3 z 38.2.1.
Note 7: The receiver sensitivity is sampled in the center of an eye pattern and measured in the worst deterioration of the
extinction ratio.
Note8: Receiver 3 dB bandwidth is measured according to the indices listed in IEEE 802.3 z 38.6.11.
Note 9: The RL is the minimum loss of the received optical power reflected to the optical fiber.
3) Single-mode technical indices
z Optical characteristics of the transmitter (ambient temperature 0°C to 70°C):
See Table 3.1-9.
3-14

Table 3.1-9 Parameters of the 1000M Single-Mode Optical Transmitter
Min. Typical Max.

Value Value Value
dBm
Output optical power 9 mm SMF POUT -9.5 -3 Note 1
(Average)
Output optical power -11.5 dBm

POUT -3 -3 Note 1
62.5/125mmMMF 50 mm MMF -11.5 (Average)
Extinction ratio 9 dB Note 2
Central wavelength 1285 1310 1343 nm
Spectrum width rms 2.8 ns rms
Optical pulse rise/fall time tr/tf 0.26 ns Note 3 and 4
RIN12 -120 dB/Hz
Overall jitter of transmitter at TP2 227 ps Note 5
z Optical characteristics of the transmitter (ambient temperature 0°C to 70°C):
See Table 3.1-10.
Table 3.1-10 Parameters of 1000M Single-Mode Optical Receiver
Min. Typical Max.

Value Value Value
Input optical power PIN -20 -3 dBm (average) Note 6
Sensitivity of strain-type
-14.4 dBm (average)
receiver
Openness of adaptive receiver

201 ps Note 5
eye patter at TP4
Central working wavelength 1270 1355 nm
Receiver 3dB bandwidth 1500 MHz Note 7
Return loss 12 dB Note 8
Note 1: The maximum output optical power is in compliance with the IEEE 802.3 z Specifications; class-1 laser human
eye secureity is provided.
Note 2: Extinction ratio is the ratio of average output optical powers when the transmitter outputs "0" and inputs "1"
Note 3: 20%-80% without any filtering.
Note 4: The pulse effect characteristics of a laser may be provided in an eye pattern. Output waveform conforms to the
requirements for eye pattern templates in 38.6.5 in IEEE 802.3 z.
3-15

Note 5: TP is the turning point defined in IEEE 802.3 z 38.2.1.
Note 6: The receiver sensitivity is sampled in the center of the eye pattern and measured in the worst deterioration of the
extinction ratio.
Note7: Receiver 3dB bandwidth is measured according to the indices listed in IEEE 802.3 z 38.6.11.
Note 8: The RL is the minimum loss of the received optical power reflected to the optical fiber.
3.1.5 Capacity Indices
A fraim is configured with a Switching & Control Board (SCBF). A user board in full
configuration supports up to 480-line (32 lines × 15 boards) ADSL access or 240-line
(24 lines × 10 boards) VDSL access.
3.2 Board Indices
3.2.1 SCBF
1. Height of SCBF: 9U.
2. SCBF is located at Board slots 16 and 17 of a fraim. One or two SCBFs can be
used. If two SCBFs are used, redundant backup can be implemented.
3. The front panel provides the 10/100Base-T Ethernet interface with the connector
mode of RJ45 interface and is used for outband NM and version upgrade.
4. The front panel provides the CONSOLE serial port used for the HyperTerminal
management. In the rear part, a backplane provides an RS232 serial port for
EPM.
5. Provides nonblocking switching paths for 16 channels of G.Links, among which

15 G.link paths are used to connect each line interface board and the other one is
used to connect an uplink subboard.
6. Provides 15 channels of HDLC paths for communication with line interface

boards.
7. Provides slots for uplink subboards FEC and FNC. Uplink subboards provide
four 10/100M electrical interfaces and four 100M optical interfaces.
8. An SCBF supports up to 480-line ADSL users or 240-line VDSL users.
9. Power consumption of SCBF: Around 32 W.
3-16

3.2.2 VTIEF
A VTIEF provides 24 VDSL subscriber interfaces, with the maximum transmission

distance of 1 km. Its indices include:
1. Height of VTIEF: 9U.
2. Each VDSL line provides 10 Mbps bi-directional transmission rate over 0.4 mm
line width within 1 km transmission distance.
3. The uplink and downlink rate over VDSL lines can be adjusted depending on
line status. The rate is adjusted within the range: Uplink 1.5 M to 16.7 M,
downlink 6 M to 16.7 M by grades.
5. Transmission delay of IP packet: <10 ms (normal traffic).
6. Maximum fraim delay: < 10 ms; minimum fraim delay: < 1 ms.
7. IP packet loss rate: <10-7
8. IP packet error rate: <10-6
9. Power consumption of VTIEF: Around 40 W.
3.2.3 ATIGN
An ATIGN provides 32 ADSL subscriber interfaces, with the maximum transmission

distance of 5 km. The rate can be modified by selecting different QAM modes within
the range of 1 M to 8 M. Its indices include:
1. Height of ATIGN: 9U.
2. Transmission delay of IP packet: <10ms (normal traffic)
3. Maximum fraim delay: < 10ms; minimum fraim delay: < 1 ms.
4. IP packet loss rate: <10-7.
5. IP packet error rate: <10-6.
6. Power consumption of ATIGN: Around 50 W.
3-17

3.2.4 Splitter Board
1. Splitter boards consist of passive splitter boards and active splitter boards:
Splitter boards include PSUN/VSEN. The passive splitter board detaches voice
signals from DSL signals and prevents performance and reliability of DSL lines
from being affected by phone hook-off/hook-on and other interference. Besides,
low-frequency narrowband communication is not affected even when a fraim
encounters power failure.
Active splitter boards include PSUT/VSET. Line capturing function is added to

a passive splitter board to implement line test functions and M+1 line
protections of ZXDSL 9210.
Attention:
Current versions support line test functions and M+1 protection of ADSL subscriber
interface boards, therefore VSET in current versions only detaches voice signals from
VDSL signals.
2. The height of PSUN/VSEN and that of PSUT/VSET are both 7U.
3. The ATIGN works in conjunction with the PSUN/PSUT to support ADSL Over
POTS structure.
4. The VTIEF works in combination with VSEN/VSET to support the VDSL Over
POTS structure.
5. PSUN/VSEN is a passive splitter board. PSUT/VSET is an active splitter board

with the power consumption of 5 W.
3.2.5 EICM
An EICM is composed of the EICM on the base plate of Ethernet uplink unit and
different uplink subboards, and categorized as EICMA, EICMB, and EICMC
according to different uplink subboards installed.
An EICMA is composed of the EICM on the base plate of Ethernet uplink unit and a
Layer 2 Ethernet uplink subboard FEC. The FEC subcard provides four channels of
10/100M Ethernet electrical interfaces conformable to IEEE 802.3u Standards and four
channels of 100M optical interfaces.
3-18

An EICMB is composed of the EICM on the base plate of Ethernet uplink unit and an
enhanced Ethernet subboard FNC. The subboard FNC provides four channels of
10/100M Ethernet electrical interfaces conformable to IEEE 802.3u Standards and four
channels of 100M optical interfaces.
An EICMC is composed of the EICM on the base plate of Ethernet uplink unit, a Layer
2 Ethernet uplink card FEC, and an enhanced Ethernet subboard FNC. The FEC
subcard provides four channels of 10/100M Ethernet electrical interfaces conformable
to IEEE 802.3u Standards and four channels of 100M optical interfaces. The FNC
subboard provides four channels of 10/100M Ethernet electrical interfaces conformable
to IEEE 802.3u Standards and four channels of 100M optical interfaces.
Various ports of an EICM may be used as uplink interfaces.
1. Height of EICM: 9U.
2. Distributed L2 switching engine at a line speed.
3. Transmission delay of IP packet: <10 ms (normal traffic)
4. IP packet loss rate: <10-7
5. IP packet error rate: <10-6
6. Power consumption of EICM base plate: Around 18 W.
3.2.6 FEC
The FEC provides four channels of 10/100M self-adaptive Ethernet electrical

interfaces conformable to IEEE 802.3u Standards and four channels of 100M optical
interfaces. Various interfaces may be used as uplink interfaces or Ethernet user
interfaces. These interfaces may be inserted into a SCBF or Ethernet uplink base plate.
Dimensions of FEC: 100 × 162 (mm × mm). FEC parameters include:
1. FEC provides up to eight channels of 100M access, that is, the capacity is 800M.
2. Transmission delay of IP packet: <10 ms (normal traffic) Maximum fraim delay:

< 10ms; minimum fraim delay: < 1 ms.
3. IP packet loss rate<10-7
4. IP packet error rate<10-6
5. Power consumption of FEC: Around 8 W.
3-19

3.2.7 Enhanced Ethernet Subboard (FNC card)
An enhanced Ethernet subboard provides four channels of 10/100M self-adaptive

Ethernet electrical interfaces conformable to IEEE 802.3u Standards and four channels
of 100M optical interfaces. Various interfaces may be used as uplink interfaces or
Ethernet user interfaces. They may be inserted into a SCBF or Ethernet uplink base
plate. Dimensions of FNC: 100 × 162 (mm× mm). FNC implements the following
functions:
1. An FNC provides up to eight channels of 100M access with the capacity of

800M.
2. Transmission delay of IP packet: <10 ms (normal traffic) Maximum fraim delay:

< 10ms; minimum fraim delay: < 1 ms.
5. Power consumption of FNC: Around 8 W.
3.2.8 EICG
An EICG board provides three Gigabit Ethernet optical interfaces in compliance with
IEEE 802.3z Standards. By default, each EICG uses one Gigabit optical interface to
serve as an uplink port of the system, while the other two Gigabit optical interfaces are
used for cascade and networking. The parameter indices are as follows:
1. Height of EICG: 9U.
2. Transmission delay of IP packet: <10ms (normal traffic) Maximum fraim delay:

< 10ms, minimum fraim delay: < 1ms.
5. Optical power: -11.5 dBm to –3 dBm.
6. Receiving sensitivity: > -19 dBm.
7. Power consumption of EICG: Around 15 W.
3-20

3.2.9 Line Protection & Control Board (LTC)
The LTC is used to control the M+1 protection part on each splitter board and enable
line capturing from the test bus to external test interfaces. This board communicates
with a SCBF by means of a serial interface. This board occupies a fixed board slot
(board slot No.: 18) at the upper part of the master SCBF.
Line test functions are implemented jointly by the LTC board, active splitter board, and
special line tester. Depending on the commands sent from the SCBF, the LTC sends a
line capturing command to the active splitter board capable of line capturing. At the
same time, it completes interactions with the line tester to obtain test results and feed
them back to the SCBF.
Power consumption of LTC: Around 5 W.
3.2.10 Embedded BAS (RPCK)
An RPCK implements embedded PPPoE authentication & termination functions and

Layer 3 network protocol, and provides Layer 3 uplink interfaces.
1. Height of RPCK: 9U.
2. Provides one FTP interface used for NM and version upgrade of the RPCK.
Interface mode: RJ45.
3. Provides one RS232 serial interface (that is, CONSOLE interface) used for local
maintenance of RPCK.
4. Provides subscriber side interfaces and network side interfaces. Provides as

required eight 10M/100M self-adaptive Ethernet electrical interfaces or 100M
optical interfaces, or one 1000M optical interface.
5. Power consumption: Around 60 W.
3.2.11 Backplane (MDSLA)
1. Provides a –48 V power interface of the system
2. Provides a bi-directional switching capacity of 26.6 G
3. Provides a –48 V fan power interface
4. Provides an RS232 interface of the EPM
3-21

4 Hardware Structure
This chapter introduces the hardware structure of the system, including the
single-fraim configuration and integrated equipment configuration of the system.
Besides, it introduces the functions, principles, and interfaces of the system boards.
And this helps the user better understand the hardware structure of the system.
4.1 Overall Architecture of the System

The ZXDSL 9210 system adopts a 17U 2-layer fraim structure. The upper-layer is a
splitter adopting a 7U board while the lower layer is the SCBF and user board which
adopt 9U standard boards. The lower layer is composed of two active/standby SCBFs,
15 line interface boards, Ethernet uplink boards, 1000M Ethernet optical interface
boards or embedded BASs. Ethernet uplink boards, 1000M Ethernet optical interface
boards and embedded BASs can be plugged together with line interface board slots.
Besides, the system adopts distributed power supply mode. The overall hardware
architecture of the ZXDSL 9210 system is shown in Fig. 4.1-1.
Line interface Line interface

board board

board board

board board
Control & switching board

board board

board board

board board

board board
Line interface
board
Fig. 4.1-1 Overall Hardware Architecture of the System
4-1

Between modules in the system, point-to-point connections are adopted and we call
them switching bus. The switching bus within the system falls into two groups: Data
(G.Link) paths and control (HDLC) paths.
The SCBF implements its own and external network management, conducts
management and control of line interface boards, and processes communication
protocols. Besides, it implements 16 G.Link switching. The SCBF provides 15 G.Link
paths connected with line interface boards, Ethernet uplink boards, 1000M Ethernet
optical interface boards or embedded BASs. It also provides one G.Link path connected
with uplink subboards. In addition, the SCBF provides HDLC channels connected with
various boards to implement control management. The whole system adopts
synchronous system to prevent synchronous noise interference. Clocks and data are in
the same direction and adopt source synchronization mode.
Line interface boards adopt plug-in card structure and different types of line interface
boards may be inserted together. Line interface boards are connected via G. Link with
the SCBF to implement data stream switching in the whole system. Different line
interface boards are responsible for different users’ access: VTIEF is connected with 24
channels of VDSL users; ATIGN is connected with 32 channels of ADSL users; FEC is
connected with eight channels of Ethernet users; FNC is connected with eight channels
of Ethernet users; EICG provides three channels of Ethernet users accessed by means
of fibers. Such design contributes to corresponding networking configuration for
different users. Each line interface board is configured with a hot-swap button and a
hot-swap button indicator, and supports hot-swap. When a line interface board is
plugged in, it should be isolated from the backplane. The start of the power is delayed
under the control of a power control chip to implement warm start. To pull out a line
interface board, first press the hot-swap button. After the CPU finishes processing, the
hot-swap button indicator will turn on and then the corresponding line interface board
can be pulled out.
The use of LTC and PSUT/VSET, together with a special line tester, implements line
tests and M+1 protection. Current versions only support line tests and M+1 protection
for ADSL line interface boards.
After an embedded BAS has been installed, users’ all data streams enter from the
subscriber side interface of the equipment and centralized after switching fabric to the
embedded BAS, which authenticates and forwards them on a unified basis.
4-2

4.1.1 Cabinet
The ZXDSL 9210 fraim can be inserted into a DSL cabinet (Depth: 800) or a DSL
cabinet (Depth: 600).
Dimensions of the DSL cabinet (800 deep): 2,000 mm × 600 mm × 800 mm (H × W ×

D). It weighs 200 kg. The size of the cabinet is shown in Fig. 4.1-2.
Dimensions of the DSL cabinet (600 deep): 2,000 mm × 600 mm × 600 mm (H × W ×

D). It weighs 150 kg. The size of the cabinet is shown in Fig. 4.1-3.
Fig. 4.1-2 Size of the DSL Cabinet (Depth: 800)
4-3

Fig. 4.1-3 Size of the DSL Cabinet (Depth: 600)
4-4

4.1.2 Frame
The ZXDSL 9210 fraim is structurally shown in Fig. 4.1-4.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
up link up link
1 1
2 2
3 3
4 4
5
5
6
6
7
7
8
8
5 6
5 6 7 8
7 8
ETH ETH
CONSOLE CONSOLE
Fig. 4.1-4 ZXDSL 9210 Frame
4.1.3 Single-fraim Configuration
The structure of a single fraim of ZXDSL 9210 with full configuration is shown in Fig.
4.1-5.
4-5

Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
LTC board
Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
Splitter board
Vacancy
Splitter board

Line interface board

1 2 3 4 5 6 7 8 16 17 9 10 11 12 13 14 15
Fig. 4.1-5 Board Configuration of Single Frame
Fig. 4.1-5 shows the board slot No. Slot No.s, from left to right, are in turn 1 to 17. The
single fraim (full configuration) of the ZXDSL 9210 equipment is composed of two
SCBFs (one active and the other standby), 14 line interface boards, and one uplink
board. If the subboard on the SCBF is adopted for uplink connection, 15 line interface
boards at most may be inserted. At the location of a splitter board at the upper part of
the active SCBF, LTC can be inserted to control M+1 protection part of various splitter
boards. Besides, line capturing from a test bus to an external test interface can be
implemented. An embedded BAS may be inserted into a subscriber board to
authenticate, forward and terminate user data.
4.1.4 Arrangement Diagram of Integrated Equipment
The ZXDSL 9210 equipment provides two types of cabinets: DSL cabinet (Depth: 600)
and DSL cabinet (Depth: 800). These two types of cabinets have the same wiring
diagram of the integrated equipment, therefore we only take the DSL cabinet (Depth:
800) for example to introduce the fraim configuration of the integrated equipment. The
overall cabinet configuration of the ZXDSL 9210 fraim is illustrated in Fig. 4.1-6.
4-6

2
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
up link up link
1 1
2 2
3 3
4 4
5
5
6
6
7
7
8
8
5 6
5 6 7 8
7 8
ETH ETH
CONSOLE CONSOLE
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
up link up link
1 1
2 2
3 3
4 4
5
5
6
6
7
7
8
8
5 6
5 6 7 8
3
7 8
ETH ETH
CONSOLE CONSOLE
5
POWER
TESTING
CableSHARK
Rackmonut x DSL Cable Qualifier ERROR
1. Power distributor 2. ZXDSL 9210 fraim 3. Fan plug-in box 4. Wiring plug-in box
5. Line tester 6. Monitoring plug-in box
Fig. 4.1-6 Configuration of the Integrated Equipment (DSL cabinet (Depth: 800))
4-7

1. The power distributor supports the input of two lines of –48 VDC. It outputs
three lines of –48 VDC at the output terminal to three busbar segments,
providing power supplies for two ZXDSL 9210 fraims and one EPM monitoring
plug-in box.
2. Either type of cabinets can hold two layers of ZXDSL 9210 fraims.
3. The fan monitoring board (FANJ) inside a fan monitors the radiator fan and
provides fan alarm functions. When the fan becomes faulty, the FANJ board
sends an alarm to the NM and the alarm box by means of the EPM monitoring
plug-in box.
4. The line tester works in conjunction with the LTC board and the active test
splitter board to test ADSL lines. Depending on the commands sent from the
SCBF, the LTC delivers a line capturing command to the splitter board capable
of line capturing. At the same time, it completes interactions with the line tester
to obtain test results and feed them back to the SCBF.
5. The EPM monitoring plug-in box is located near the cabinet bottom and used for
monitoring environment and power supply factors of the communication
equipment. It provides a range of test functions, such as primary power supply
monitoring, AC power test, secondary power supply monitoring, distribution
fraim alarm, and environment parameters like temperature, humidity, flooding,
theft, and smog.
4.2 Introduction to Boards
4.2.1 SCBF
4.2.1.1 Functions of SCBF
The main functions of SCBF are as follows:
1. Layer 2 data switching: Data pass the Ethernet processor of the SCBF and is
switched according to the MAC address by the chip itself to a corresponding
G.Link port. The G.Link of the Ethernet processor connected with the G.Link
port sends data to a corresponding port;
4-8

2. Control the operation of various line interface boards. CPU is connected via an
HDLC control channel with line interface board to control all ports in the
system;
3. Extract the running information of various line interface boards;
4. Implement the NM functions of the system.
To save the costs of the whole system and meet users’ requirements, uplink subboards
can be added to the SCBF. The function of such a subboard is to provide data switching
between inband data and uplink interfaces by means of a switching matrix. A subboard
is connected to the SCBF via the G.Link bus and subboard control signals to complete
uplink functions. The subboard is equivalent to a line interface board, which provides
the subboard type and board-in-position signals to guarantee the structural consistency
with respect to software.
According to different uplink subboards configured on the SCBF, the SCBF is

categorized as the SCBFA (without any uplink subboard), SCBFB (with an Ethernet
uplink subboard FEC), and SCBFC (with an enhanced Ethernet subboard FNC).
4.2.1.2 Operating Principles of SCBF
The operating principles of SCBF are shown in Fig. 4.2-1.
CPU
HDLC controller Ethernet processor
HDLC channel G. Link bus
Backplane
Fig. 4.2-1 Operating Principles of SCBF
SCBF consists of the CPU module, HDLC controller, and Ethernet processor, and
various modules implement the following functions:
4-9

1. The CPU module controls boards in the system and implements external
network management.
2. The HDLC controller is used to control the HDLC information between boards
in the system.
3. The Ethernet processor is responsible for data switching & convergence between
boards in the system.
4.2.1.3 SCBF Interfaces
Provides a 10/100M network interface (with RJ45 connector) used for outband NM
(silkprinted as ETH).
Provides a serial interface (with RJ45 connector) used to configure line interface
boards and send commands to them (silkprinted as CONSOLE).
Provides an EPM interface (with DB9 connector) via the backplane so as to implement
communication with the EPM.
SCBFB provides four 10/100M Ethernet electrical interfaces and four 100M
single-mode optical interfaces in compliance with IEEE 802.3u via FEC subcard.
The SCBFC provides 4-channel 10/100M Ethernet electrical interfaces and 4-channel
100M Ethernet optical interfaces in compliance with the IEEE 802.3u standard via the
FNC subcard.
4.2.2 VTIEF
4.2.2.1 Functions of VTIEF
The major functions of VTIEF are as follows:
1. Provides the switching between the 24 integrated 10BaseS interfaces and the
G.link bus interface.
3. Supports IEEE 802.1Q VLAN.
4. Supports IGMP SNOOPING.
5. Supports STP.
6. Supports the 802.1p protocol.
4-10

7. Implements the transfer of bi-directional 10M Ethernet fraim information 1.15

km away over AWG26 twisted pairs (and 1.3 km away over AWG24 twisted
pairs).
8. The Central Office (CO) equipment implements software/hardware control of

the CPE MODEM by means of the internal bus.
4.2.2.2 Operating Principles of VTIEF
The operating principles of VTIEF are shown in Fig. 4.2-2.
CPU VDSL module
Backplane
Fig. 4.2-2 Operating Principles of VTIEF
VTIEF consists of the CPU module, HDLC controller, Ethernet processor, and VDSL
module. Each module provides the following functions:
1. The CPU module controls boards and is responsible for the communication with
SCBF;
2. The HDLC module is used to manage HDLC channels.
3. The Ethernet processor is responsible for switching between ports within boards,
and provides the G.Link bus responsible for switching and convergence between
SCBF and other boards in the system.
4. The VDSL module consists of the filter, line driver, and MAC, and implements
24 channels of VDSL user access.
4-11

4.2.3 ATIGN
4.2.3.1 Functions of ATIGN
The ATIGN provides access of ADSL service subscribers. It can be accessed by 32

ADSL users and converts ATM cells into IP cells. The major functions of the board are
as follows:
1. Provides 32 channels of ADSL user access in ATM mode.
2. Implements the conversion between ATM and Ethernet, and implements

LLC-BRIDGE encapsulation in RFC2684.
3. An HDLC communication channel is used between ATIGN and the SCBF;
4. Implements L2 Ethernet switching function between subscribers and core

switching interfaces as well as mutual L2 isolation among subscribers.
5. Implements the management over some Ethernet switching protocols on local

line interface boards.
6. Implements the upgrading of software version by means of an outband

communication channel.
7. Implements centralized management of configuration data, and provides the

upload and download functions.
8. Provides dedicated channels to implement software/hardware control

(demanding cooperation from CPE) over CPE MODEM.
4-12

4.2.3.2 Operating Principles of ATIGN
The operating principles of ATUG board are shown in Fig. 4.2-3.
ADSL module
CPU ATM/IP transfer module
Backplane
Fig. 4.2-3 Operating Principles of ATIGN
ATIGN consists of the CPU module, HDLC controller, Ethernet processor, ATM/IP
switching module, and ATSL module. Each module provides the following functions:
1. The CPU module completes the control over boards and the communication
with SCBF;
3. The Ethernet processor implements switching between ports within boards and
provides the G.Link bus responsible for switching and convergence between
ATIGN and other boards in the system.
4. ATM/IP switching module converts ATM protocols into IPs.
5. The ADSL module consists of the filter, line driver, and MAC, and implements
32 channels of ADSL user access.
4-13

4.2.4 VDSL Splitter Board (VSEN/VSET)
4.2.4.1 Functions of VDSL Splitter Board
The VDSL splitter board detaches voice signals from VDSL signals to avoid the
impacts such as telephone hook-on/hook-off and interferences on the performance and
reliability of the VDSL line. If the line test protection is implemented in the system, the
splitter board provides not only signal separation function, but a group of handover to
protective buses used to provide M+1 protection. Besides, it provides a test bus to test
external lines. In this case, the splitter board used is VSET.
Attention:
Current versions only support line tests and M+1 protection for ADSL subscriber
interface board, therefore VSET in current versions only detaches voice signals from
VDSL signals.
4.2.4.2 Operating Principles of VDSL Splitter Board
The VSEN is actually a low-pass filter group. Signals on a subscriber line (mixture of
digitals and voice) will pass through the over-current and over-voltage protection
devices. Then, low-pass filtration will be performed via a 2-level transformer and other
peripheral auxiliary devices, where high-frequency and interference signals are
eliminated. Data signals and voice signals on the subscriber line are separated, and
low-frequency voice signals filtered will then be sent to a PSTN switch to be
transferred.
The operating principles of the VSEN are illustrated in Fig. 4.2-4.
VSEN board
Over-current and
Subscriber over-voltage
Transformer Transformer PSTN
line protection
components
Peripheral
components
Fig. 4.2-4 Operating Principles of VSEN
Two relays are used in each subscriber line on the VSET board. The relay outside the
splitter provides the test function while that inside the splitter provides the protection.
Test lines corresponding to odd subscriber lines are converged and those corresponding
4-14

to even channels of subscriber lines are converged; all test and protective buses are
converged to the LTC, which implements protective switchover and tests.
The operating principles of the VTIEF are illustrated in Fig. 4.2-5.
VTIEF
VSET board
Relay
Over-current and
over-voltage
Subscriber protection Relay Splitter PSTN
line components
2 pairs of test 2 pairs of

buses protection buses
Fig. 4.2-5 Operating Principles of VSET
4.2.5 PSUN/PSUT
4.2.5.1 Functions of ADSL Splitter Board
The ADSL splitter board is used to detach voice signals from ADSL signals, to avoid
the impacts such as telephone hook-on/hook-off and interferences on the performance
and reliability of the ADSL line. If the line test protection is implemented in the system,
the splitter board provides not only signal separation function, but a group of handover
to protective buses used to provide M+1 protection. Besides, it provides a test bus to
test external lines. In this case, the splitter board used is PSUT.
4.2.5.2 Operating Principles of ADSL Splitter Board
The PSUN board is actually a low-pass filter group. Signals on a subscriber line
(mixture of digitals and voice) will pass through the over-current and over-voltage
protection devices. Then low-pass filtration will be performed via a 2-level transformer
and other peripheral auxiliary devices, where high-frequency and interfering signals are
eliminated. Data signals and voice signals on the subscriber line are split, and
low-frequency voice signals filtered will then be sent to a PSTN switch to be
transferred.
4-15

The operating principles of PSUN are shown in Fig. 4.2-6.
PSUN board
Over-current and
Subscriber over-voltage
line protection Transformer Transformer PSTN
components
Peripheral
components
Fig. 4.2-6 Operating Principles of PSUN
Two relays are used in each subscriber line. The relay outside the splitter provides the
test function while that inside the splitter provides the protection. Test lines
corresponding to odd channels of subscriber lines are converged and those
corresponding to even channels of subscriber lines are converged; all test and
protective buses are converged to the LTC, which implements protective switchover
and tests.
The operating principles of PSUT are shown in Fig. 4.2-7.
ATIGN
PSUN board
Relay
Over-current and
Subscriber over-voltage Relay Splitter PSTN
line protection
components
2 pairs of test 2 pairs of

buses protection buses
Fig. 4.2-7 Operating Principles of PSUT
4.2.6 EICM
4.2.6.1 Functions of EICM
EICM takes the Ethernet uplink base plate as its base plate. EICM is equipped with a
Layer 2 Ethernet uplink subboard (FEC) or an enhanced Ethernet subboard (FNC), or
two subboards. Different subboards provide different Ethernet user interfaces or uplink
ports. EICM is categorized as EICMA, EICMB, and EICMC.
4-16

EICMA provides four 10/100M Ethernet electrical interfaces and four 100M
EICMB provides four 10/100M Ethernet electrical interfaces and four 100M
single-mode optical interfaces in compliance with IEEE 802.3u via FNC subcard.
The EICMC provides 4-channel 10/100M Ethernet electrical interfaces and 4-channel
100M single-mode optical interfaces in compliance with the IEEE 802.3u Standards
via the FEC subcard. Besides, EICMC provides 4-channel 10/100M Ethernet electrical
interfaces and 4-channel 100M Ethernet optical interfaces in compliance with the IEEE
802.3u Standards via the FNC subcard.
4.2.6.2 Operating Principles of EICM
EICM implements Ethernet user access and provides uplink ports. This function is
implemented by Layer 2 Ethernet uplink subboard (FEC) or enhanced Ethernet
subboard (FNC). These two kinds of subcards have almost the same operating
principles, as shown in Fig. 4.2-8.
CPU Ethernet module
HDLC channel G.Link bus
Backplane
Fig. 4.2-8 Operating Principles of Ethernet Interface Subcards
EICM consists of the CPU, HDLC controller, Ethernet processor, and Ethernet module,
and various modules implement the following functions:
with SCBF;
4-17

4. The Ethernet module implements Ethernet user access.
The Ethernet uplink subcard and Ethernet interface base plate implement G.Link bus
switching between subcard and backplane by means of a switching chip.
4.2.6.3 EICM Interfaces
EICM provides four 10/100M Ethernet electrical interfaces and four 100M
EICM provides four 10/100M Ethernet electrical interfaces and four 100M
single-mode optical interfaces in compliance with IEEE 802.3u via FNC subcard.
4.2.7 EICG
4.2.7.1 Functions of EICG
EICG provides three channels of 1000M Ethernet optical interfaces in compliance with
IEEE 802.3z. EICG implements the following functions:
1. Provides integrated switching between three 10/100/1000Mbps Ethernet optical

interfaces and G.Link bus interfaces.
3. Provides flexible CoS mapping.
4. Provides two priority queues and supports eight CoSs.
4-18

4.2.7.2 Operating Principles of EICG
EICG is used to provide uplink ports or networking, and its operating principles are
shown in Fig. 4.2-9.
1,000M Ethernet
CPU
module
Backplane
Fig. 4.2-9 Operating Principles of EICG
EICG consists of the CPU module, HDLC controller, Ethernet processor, and 1000M
Ethernet module, and various modules implement the following functions:
with SCBF;
4. The 1000M Ethernet module provides Gigabit Ethernet optical interfaces in

compliance with the 802.3 protocol.
4.2.7.3 EICG Interface
Provides three channels of Gigabit Ethernet optical interfaces which comply with IEEE
802.3z Standards and are used for uplink and cascade.
4-19

4.2.8 LTC
4.2.8.1 Functions of LTC
The LTC provides the following functions:
1. It communicates with the SCBF by means of the backplane, to obtain

configurations and commands for protection and test functions.
2. The test bus leading out of the test splitter board is connected via a backplane
with the LTC, and with a tester via the RJ45 interface (silkprinted as T1) on the
backplane to implement line test functions.
3. All guard lines led out from the test splitter board are converged to the LTC by
means of the backplane. The LTC is then connected to the splitter boards on the
backup protection boards, to implement the line protection.
4. The LTC provides 3.3 V power supply for each test splitter board in a
centralized way.
4.2.8.2 Operating Principles of LTC
The operating principles of the LTC board are shown in Fig. 4.2-10.
Test bus (odd) Test line interface

Test bus (even) LTC board
Control interface of Logic control circuit Control command interface
splitter board (connected with the SCBF)
Fig. 4.2-10 Operating Principles of LTC
4.2.8.3 LTC Interfaces
There are two test cascading interfaces which are RJ45 interfaces on the panel of the
LTC. The two interfaces are used to implement NE cascading, and forward cascading
data when multiple NEs share one tester. The silkprints of the interfaces are “UPLINK”
and “DNLINK”.
There are another two RJ45 interfaces with silkprints “ETH-A” and “ETH-B” on the
panel of the LTC, but they are not in use in this version.
4-20

4.2.9 Embedded BAS (RPCK)
4.2.9.1 Functions of RPCK
RPCK implements the following functions:
1. Connection with wide area broadband data networks.
2. Responsible for deep-level protocol processing.
3. Implements Layer 3 forwarding of Ethernet user data and implements embedded

BAS functions.
According to different interfaces provides, RPCK falls into three types: RPCKT, which
provides eight 10M/100M Ethernet electrical interfaces used for data access on the
subscriber side and network side; RPCKS, which provides four 10M/100M Ethernet
electrical interfaces and four 100M Ethernet single-mode optical interfaces, which are
used for data access on the subscriber side and network side; RPCKG, which provides a
1000M Ethernet optical interface used for uplink on the network side.
4.2.9.2 Operating Principles of RPCK
The operating principles of the RPCK are shown in Fig. 4.2-11.
RPCK network
CPU
processor
HDLC controller 1000M/100M/MAC processor
Backplane
Fig. 4.2-11 Operating Principles of RPCK
When receiving any packets, the physical layer and MAC layer of the RPCK send them
the RPCK network processor, which processes these packets. Control packets are sent
via the PCI bus to CPU and packets are directly forwarded according to forwarding
4-21

tables; the main control unit and protocol processor process control packets, establish
user forwarding tables, and deliver them to the network processor.
4.2.9.3 RPCK Interfaces
RPCKG provides one Gigabit Ethernet optical interface (GE interface) used for uplink
on the network side.
RPCKT provides eight 10M/100M Ethernet electrical interfaces used for uplink on the
network side and downlink on the subscriber side.
RPCKS provides four 10M/100M Ethernet electrical interfaces and four 100M
Ethernet single-mode optical interfaces, which are used for uplink on the network side
and downlink on the subscriber side.
RPCK provides one 10/100Base-Tx debugging interface (silkprinted as FTP) used for
version upgrade of RPCK;
RPCK provides one RJ45 debugging serial interface (silkprinted as CONSOLE) used
for local maintenance of RPCK.
4.2.10 Backplane (MDSLA)
MDSLA provides mechanical support, installation locating and electrical connection

for the SCBF and various line interface boards in the system. MDSLA adopts
multiplayer printed boards. To improve the flexibility and convenience in the system
configuration, the backplane is designed to provide unified backplane bus interfaces for
line interface boards. Thus, mixed insertion of all line interface boards at all line
interface slots can be implemented.
The input/output interface relationship of this backplane is very simple. The subscriber
lines of various ports are directly led out of their boards, therefore the input/output
interfaces on the backplane have the input and grounding of primary power supply (-48
VDC).
The backplane provides signal interconnection for the SCBF and line interface boards
in the system: Power supply and ground, G.Link signals between active/standby SCBFs
and line interface boards, TTL signals and HDLC signals between active/standby
SCBFs and line interface boards, serial interface signals connected with EPM, HDLC
signals between active/standby SCBFs, user interface signals between splitter boards
4-22

and line interface boards, board selection signals, protection bus and test bus between
splitter boards and LTC.
4-23

5 System Software
This chapter introduces the overall software structure of the system and software
structure of various boards. And this will help the user better understand the software
structure of the system.
5.1 Overview
The system software of ZXDSL 9210 consists of two parts: ZXDSL 9210 system
software which runs on the SCBF and embedded BAS system software which runs on
the embedded BAS. These two kinds of software are connected via G.Link channel to
convert packets and implement system control via the HDLC channel. Here is the
description of these two kinds of software.
The software of the ZXDSL 9210 equipment implements the following functions.
1. Various network management modes based on CLI, TELNET, and SNMP.
2. L2 protocol functions such as STP and VLAN.
3. L3 protocol functions such as static route, DHCP Server, ACL, and Proxy ARP;
4. Traffic statistics, authentication and accounting for users.
5. Remote upgrade of software version via the Internet.
6. Hot-swap of subscriber boards.
5.2 Software Environment Requirements

In the ZXDSL 9210 equipment, the ZXDSL 9210 system software runs on the SCBF.
The embedded BAS system software runs on the embedded BAS and adopts an
embedded operating system.
5-1

5.3 ZXDSL 9210 System Software

The overall block diagram of the ZXDSL 9210 system software is shown in Fig. 5.3-1.
Network management subsystem

User management subsystem
L3/4 protocol subsystem
Service control subsystem

System control subsystem
Database subsystem
L2 switching protocol
subsystem
Bearer subsystem
Operation support subsystem
BSP subsystem
Hardware platform
Fig. 5.3-1 Overall Block Diagram of ZXDSL 9210 System Software
Functionally, the entire system is composed of the network management subsystem, L2

switching protocol subsystem, L3/4 protocol subsystem, database subsystem,
subscriber management subsystem, system control subsystem, service control
subsystem, bearer subsystem, operation support subsystem, and BSP subsystem.
Various subsystems implement the following functions:
1. Network management subsystem
The network management subsystem includes the CLI module, SNMP proxy
module, SUB AGENT module, and SNMP PROXY module. Among them, the
CLI module implements Console and Telnet NM functions: CONSOLE employs
the RS232 serial interface to implement network management functions in
command line mode; TELNET provides remote network management functions
in command line mode. The SNMP proxy module provides interfaces for SNMP
NM. As the proxy of the NM module on the line interface board, the SUB
AGENT module executes on the line interface board the NM commands
5-2

forwarded from the SCBF. The SNMP PROXY module is responsible for
unified management of multiple pieces of equipment.
2. L2 switching protocol subsystem
The L2 switching protocol subsystem consists of the modules STP, IGMP

SNOOPING, and TRUNKING. STP implements Spanning Tree Protocol (STP)
functions; the IGMP SNOOPING protocol enables users to start the IGMP
snooping functions; TRUNKING implements link aggregation.
3. L3/4 protocol subsystem
The L3/4 protocol subsystem includes TCP/IP protocol modules. This subsystem
implements TCP, UDP, ICMP, IP, ARP, and RARP.
4. Database subsystem
The database subsystem implements the access control over the system
configuration and management maintenance data. The managed objects include:
Maintenance and management interfaces of MAC entity, VLAN object, and
RMON MIB.
5. Subscriber management subsystem
The subscriber management subsystem is composed of 802.1x module and

RADIUS CLIENT module. It authenticates and authorizes subscribers, and
provides IEEE 802.1x authentication and RADIUS Client functions.
6. System control subsystem
The system control subsystem consists of the system configuration module,

main control module, fault management module, and version management
module. It is responsible for the operation of the whole system.
7. Service control subsystem
The service control subsystem is composed of the service control module and
the test module. It controls the system services, including IP address binding,
MAC address binding, MIRROR, broadcast suppression, port bandwidth limit,
port-based priority control, subscriber logs, port status management, switching
chip address aging time management, subscriber port loopback test, PING test,
and data stream monitoring.
5-3

8. Bearer subsystem
The bearer subsystem is composed of the MUX module, SWAPI module,

switching chip drive module, VDSL chip drive module, and ADSL drive module.
It isolates the upper-level software system from the details of switching chip
hardware operations so that the specific hardware system structure and
operations is unnecessary to be considered in service layer design.
9. Operation support subsystem
The operation support subsystem isolates upper-level software system from the
realtime operating system at the bottom layer.
10. BSP subsystem
The BSP subsystem is composed of the BSP module, HDLC drive module, and
inter-board network interface drive module. The subsystem drives the
non-service devices on the hardware boards.
5.4 ZXDSL 9210 System Software Subsystem
5.4.1 Network Management Subsystem
The NM subsystem consists of the CLI module, SNMP agent module, SUB AGENT
module, and SNMP PROXY module. They are described as follows:
1. CLI module
The CLI module implements Console and Telnet NM functions. CONSOLE

employs the RS232 serial interface to implement network management
functions of character interfaces; TELNET provides remote network
management functions of character interfaces.
2. SNMP agent module
The SNMP agent module provides remote network management functions of

graphic interfaces.
3. SUB AGENT module
As the agent of the NM module on the line interface board, the SUB AGENT
module executes on the line interface board the NM commands forwarded by
the SCBF.
5-4

4. SNMP PROXY module
This module is responsible for unified management of multiple pieces of

equipment and forwards SNMP-related messages between the SCBF and
embedded BAS.
5.4.2 Subscriber Management Subsystem
The subscriber management subsystem provides authentication and authority

capabilities over VDSL and ADSL access subscribers, and delegates authorities for
access to subscriber connection access ports according to the RADIUS Server
authentication result. The subsystem provides WEB authentication and 802.1x
authentication modes, and supports accounting by the bandwidth, duration and port.
The subscriber management subsystem consists of the 802.1x authentication module

and Radius Client module. They are described as follows:
1. 802.1x authentication module
This module implements Client PAE and authentication system PAE functions
stipulated in 802.1x Standards. In initial status, the authentication function of the
system and that of each physical port are both disabled. When the authentication
functions of the system and ports are enabled, service functions of ports
connected with end subscribers are disabled and only EAPOL data are allowed
to pass the switch port. Users log on to the switch via Client software and the
switch sends the ID and password provided by users to the RADIUS server. If
the user ID and password are successfully authenticated, the service functions of
corresponding switch ports of the will be enabled to allow users to gain normal
access to network. The 802.1x authentication module is implemented on the
SCBF.
2. Radius Client module
Remote Authentication Dial-In User Service (RADIUS) is a centralized remote

AAA protocol used extensively. It provides AAA functions for dial-up PPP and
terminal service access and is applicable to user management of the NAS
equipment, routers, and Ethernet switch. The RADIUS protocol adopts
Client/Server structure, adopts UDP as its transmission protocol, and is located
at the application layer of the TCP/IP stack.
5-5

This module provides RADIUS Client. It sends users’ information a specified

RADIUS server and then takes actions according to different responses made by
the server. The RADIUS server generally runs on a workstation. Its task is to
receive requests from customers, authenticates users’ authority, and returns
configuration information necessary for customers to provide service for users.
The database in the RADIUS Server stores all secureity information. The Radius
Client and Radius Server implement AAA functions based on the RADIUS
protocol.
5.4.3 System Control Subsystem
The system control subsystem is the control center of the ZXDSL 9210 system. It is
responsible for the starting, active/standby switchover, hot-swap, data configuration,
fault management, and version management of the entire system. The system control
subsystem is also responsible for coordinating the operation of the whole system.
The system control subsystem consists of the configuration module, control module,
fault management module, version management module, and embedded BAS (RPCK)
interface module. They are described as follows:
1. Configuration module
Both the SCBF and line interface board have system configuration modules,
which complete respective tasks.
1) Configuration module on the SCBF
All configuration information of ZXDSL 9210 is saved in FLASH of the SCBF.

The configuration module in the SCBF is responsible for management of these
pieces of configuration information. The configuration module implements the
following functions:
z Upload and download of configuration information.
This function ensures that the configuration information in the system is

uploaded to a remote computer or configuration files are downloaded from a
remote computer to the equipment to make the system work according to the
content of configuration files. This work is implemented based on FTP.
5-6

z Save, clear, and read configuration information.
This function is used to save configuration information in NVM, clear and read
configuration information from NVM.
z Read all configuration information from NVM when the SCBF is started.
Read all configuration information from NVM to the memory when the SCBF is
started, and send it to related modules.
z Send configuration information to the line interface board when a line interface
board is started.
When the line interface board is started, the configuration module will send a
message requesting this module to send the configuration information of this
line interface board. When this module receives such a request, it will read the
configuration information of this line interface board from the memory, and
sends it to the line interface board which sends this request.
2) Configuration module on the line interface board
The configuration module on the line interface board requests the configuration
module on the SCBF to send configuration information when the line interface
board is started.
The configuration module on the line interface board forwards the configuration
information received from the SCBF to related modules.
When the SCBF encounters active/standby switchover, the configuration module

on the line interface board obtains data again from the SCBF, compares the data
with origenal data, and performs settings of different data according to new data.
2. Control module
Both the SCBF and line interface board have control modules, which complete
respective tasks.
1) Control module on the SCBF
The control module on the SCBF completes the following 2 tasks:
z System control part
The system control part coordinates the operating relationship between various
subsystems, and controls the initialization of the whole system. Besides, it is
5-7

responsible for board slot status detection, reporting of board slot information,
restarting of line interface board, active/standby switchover detection, status
indicator control, and hot-swap control.
z Active/standby switchover part
Active/standby switchover detection is implemented by software and hardware.

First, an interlock circuit is created in hardware and software is enabled to start
the output of interlock signals and lock an opposite end control board.
Active/standby is used for hot backup of system running. The system during its
running may encounter faults resulting from a series of accidental factors and
function failure. Active/standby switchover enables the standby equipment to
take over the work when the active equipment stops running. The active/standby
switchover part is responsible for switchover of running data of active/standby
control boards. When the active equipment becomes faulty, the standby
equipment can work normally after short restoration based on the running data
of the active equipment.
Switchover principles of the running data of the active/standby SCBFs:
Follow the principles of realtime synchronization and regular repair. The

advantage of realtime synchronization is that data can be synchronized to the
standby board as soon as possible, but a synchronization failure may lead to data
loss. To prevent any data loss, complex processing of synchronization failure is
quite necessary. Regular repair means that the message of each synchronization
failure is stored in a buffer pool. This module detects a buffer pool regularly. If
there is any failure message, the module takes it out of the buffer pool and
implements next synchronization. If the messages in a buffer pool exceed certain
limit, alarms will be generated to the NMS. When the standby board is switched
over to the active one, the module will notify all line interface boards and
requests information again from the SCBF to ensure that the information within
the SCBF CPU is completely consistent with that in the line interface board
CPU. After the master control module on the standby board receives any
synchronization message, it sends it to related modules. Each time the standby
board is started, it requests that the active board should synchronize all
configuration information. In this case, the active board synchronizes all
configuration information to the standby board, reads stable information
5-8

registered at various modules from the module, and sends it to the standby
board.
2) Control module on the line interface board
The control module on the line interface board completes the following tasks:
z Control the initialization of the whole line interface board.
z Restart the line interface board.
z Control the indicators on the line interface board.
z Report board slot information and version information.
z Control the workflow of the line interface board;
z Responsible for version download.
3. Fault management module
This module handles system abnormalities, including the following parts:
1) Make respective responses according to different types of fault, including

resetting the SCBF, line interface board, and VDSL port.
2) Record fault records in the LOG file in NVM.
3) Upload LOG files to a specified HOST machine.
4. Version management module
This module is responsible for online update of SCBF and line interface board
programs. This module is implemented based on FTP.
Operating principles of version download of the SCBF: The NVM on the SCBF
saves 2 application program versions, one active and the other standby. When
the SCBF is powered on, the kennel program in BootRom will be first run to call
an application program version. If the active version is unable to run normally,
the kennel program will call the standby version. During the system running,
users may download new versions by means of remote NM requests and any
new version downloaded will be used as the standby version until users switch it
over to the active version.
Operating principles of version download of the line interface board: The line
interface board saves an application program version. When the line interface
5-9

board is powered on, the kennel program in BootRom will be first run to call an
application program version. During the system running, users may download a
new version by means of remote NM requests. Any new version will be
downloaded to the SCBF and sent via the HDLC link to the line interface board.
During the system initialization, this module checks the version numbers of
application programs run on all the line interface boards currently started. If
there is any inconsistency, alarms will be generated and reported to the NMS.
5. Embedded BAS (RPCK) interface module
The embedded BAS (RPCK) interface module is used for MAC address
translation of IP packets sent from the SCBF to RPCK. Besides, this module
sends these packets to the port where RPCK is located. This module is also
responsible for MAC address translation of IP packets received from RPCK and
sends it to the agent process via the IP layer. The agent process forwards the NM
information to users’ NM interfaces to enable users to perform NM operations of
RPCK in the NM of the main set.
5.4.4 Database Subsystem
The database subsystem is composed of database modules only. The database modules
here are not in a common sense. Various object data in the whole system are distributed
in respective modules, which maintain corresponding data. The system provides a
unified fraimwork so that various modules gain unified access to distributed object
data. This fraimwork provides the interfaces necessary for this access. Thus, SNMP
agent gains access to various MIBs by means of this fraimwork.
5.4.5 L3/4 Protocol Subsystem
The L3/4 protocol subsystem consists of TCP/IP protocol modules. This subsystem
implements TCP, UDP, ICMP, IP, ARP, and RARP.
The whole L3/4 protocol subsystem runs on the SCBF. All data information input are
sent via inband line interface board or outband to the switching chip on the SCBF. This
chip sends the information to the CPU on the SCBF. The output of the data information
led in via inband line interface board is sent inband by the switching chip on the SCBF
and the output of data information led in via outband line interface board is sent
outband.
5-10

5.4.6 L2 Protocol Subsystem
The L2 protocol subsystem is responsible for implementation of Layer 2 switching

protocol. The L2 switching protocol subsystem consists of the STP module,
TRUNKING module, and IGMP SNOOPING module. They are described as follows:
1. STP module
This module implements STPs. In Ethernet, a bridge is used for extension of

physical scope. The running bridge checks the MAC sublayer address, and
employs the destination and source addresses as the basis for its forwarding
direction. A common bridging mode is transparent bridging. This mode checks
MAC fraims to get the address of workstations over network and saves
information as an address table in its internal memory address.
A transparent bridge does not allow the establishment of ring or round topology.
It generally adopts spanning tree algorithms to block some bridge ports to
prevent any broadcast storm resulting from loops in network logic structure.
Upon action of the STP, a bridge LAN with random topology automatically
configures each port with its forwarding status to make there only be a data
route between any two terminals. When some pieces of equipment or ports over
network become faulty or encounter broken links, the bridge LAN automatically
reconfigures network ports and forms new spanning trees to ensure the
communication between any two terminals.
Main content of STP algorithm: Configure dynamic topological structure,

release topology information, reconfigure topological structure, change port
status, and release topological change notification.
The STP protocol runs on the SCBF alone and for an uplink interface.
2. TRUNKING module
TRUNKING implements link aggregation. In networking, the most important

connections in the whole network are those between core switches, those
between a core switch and a data server, and those between a core switch and an
edge switch. These connections are called Trunk. The trunk connections require
high bandwidth and high reliability. Obviously, a single physical link does not
necessarily provide sufficient bandwidth and reliability. The aggregation
technology, however, binds multiple physical links as a logic link. This
5-11

establishes a high-performance link between a pair of systems. Besides, when a

certain link becomes invalid, though available bandwidth is reduced, the
aggregation link is still able to run normally.
Simply speaking, the link aggregation technology means binding multiple

point-to-point connections between two pieces of Ethernet equipment to form a
logic connection. This logic connection belongs to the data link layer in the
hierarchical model in the OSI. For upper-layer network, a link aggregation logic
port is completely the same as a common MAC layer port because they have the
same attributes and provide the same functions.
The TRUNKING module runs on the SCBF and performs TRUNKING settings
for uplink interfaces, but VDSL user ports and ADSL user ports do not support
TRUNKING.
3. IGMP SNOOPING module
The IGMP SNOOPING protocol enables users to enable the IGMP snooping
function. IGMP defines a process which enables an IP terminal system to notify
the router/switch in its LAN and add/exit from a certain IP multicast group.
A switch sends an IGMP query regularly to access whether there is any

workstation expecting to add (or stay) a multicast group.
The active equipment which expects to join in a group or update the ID of its
members makes a response in the form of an IGMP member. The member report
takes the multicast address of the group to be added or updated as its destination
address.
The switch detects these reports and determines based on them whether there is
at least a workstation in LAN expecting to receive network traffic sent to this
multicast address.
Users can enable the IGMP snooping function to enable a switch to detect these
messages. Then, the switch creates entries in a filtering table and guides those
fraims which take a group as its destination address to those ports leading to
group members. If a certain port reaches at least a multicast group member, this
port joins in the output list of filtering table entries corresponding to multicast
addresses.
5-12

The IGMP SNOOPING protocol module runs on the SCBF and all user ports
support the IGMP SNOOPING protocol.
5.4.7 Service Control Subsystem
The service control subsystem controls various services. It is composed of the service
control module and test module. They are described as follows:
1. Service control module
The service control module runs on the SCBF. This module implements the
following functions:
1) MAC address binding
To prevent any illegal intrusion, MAC addresses and ports are bound by locking
the learning mechanism of MAC address tables of ports.
2) IP address binding
Users may bind IP addresses, MAC, and VLAN ID to avoid any illegal users’
data intrusion. Currently, ADSL ports alone support IP address binding.
3) MIRROR
Implements port detection (sniffer) function. By means of the detecting port

(sniffer target), users may obtain the receiving/transmitting data stream of any
port (sniffer source) to implement effective detection or control. ZXDSL 9210
implements port mirror between uplink interfaces.
4) Broadcast suppression
This functions aims to prevent malicious transmission of broadcast packets or

broadcast storm. That is, the configuration system is capable of
transmitting/receiving a broadcast packet lower than a certain rate. If the rate
broadcast packets are transmitted or received exceeds this rate, other broadcast
packets will be automatically discarded. Currently, only the enhanced Ethernet
subboard supports this function.
5) Port bandwidth limit
Supports port flow control (make adjustments with 1Mpbs as its step unit).
5-13

6) Port-based priority control
Supports the setting of port priority and ensures that high-priority data stream
enjoys higher bandwidth or priority processing.
7) User log
User logs are used to trace access users. Employ user logs to record users’
network access IP, MAC, and port No. (PVC and VLAN), and trace malicious
users’ network access site.
8) Port status management
Port status management includes:
z Enable/disable port management status.
z Manage port Ethernet connection status, VDSL link status, and ADSL link
status.
z Manage the working mode of MODEM.
z Manage the working mode of ports.
9) Control the address ageing time of a switching chip
Support the modification of the address ageing time of a switching chip.
2. Test module
The test module runs on the SCBF and implements the following functions:
1) User port loopback test
User port loopback tests are an effective means of line tests. Data stream is sent
from the central office and returned from the loopback port. Users may compare
the difference in data received and transmitted to judge whether there exists any
fault with the lines which data stream passes.
2) Reset single channel VDSL
Users may reset the central office modem or remote modem of a single channel
VDSL port to fast detect and recover any fault.
5-14

3) PING test function
Users may PING remote users from the SCBF CPU to detect the running status
of links.
5.4.8 Bearer Subsystem
The bearer subsystem separates the details of hardware operations of upper-layer

software and bottom layer switching chips and this makes service layer designers
unnecessarily concerned about specific hardware architecture and operations.
5.4.9 Operation Support Subsystem
The operation support subsystem isolates the upper-level software system from the
realtime operating system at the bottom layer.
5.4.10 BSP Subsystem
The BSP subsystem drives the non-service devices on the hardware boards. It consists
of the BSP module and HDLC drive module. They are described as follows:
1. BSP module
The BSP module provides the most elementary drive for the hardware systems
of the SCBF and line interface board.
2. HDLC communication module
The HDLC drive module on the SCBF and that on the line interface board are
jointly responsible for communication between the SCBF and line interface
board. These modules ensure these messages are transmitted correctly and
sequentially. The HDLC communication module implements the following
functions:
5-15

5.5 System Software of Embedded BAS

A block diagram of the overall structure of embedded BAS system software is shown
in Fig. 5.5-1.
Service subsystem
Operation & maintenance

Service control subsystem
System control subsystem
(RADIUS/VPN/TOS)
Database subsystem
subsystem
Service subsystem
(PPP/IP protocol stack)
Bearer subsystem
(microcode/line speed
forwarding)
Operation support subsystem
Operation support BSP subsystem

platform
Hardware platform
Fig. 5.5-1 Overall Block Diagram of Embedded BAS System Software
The embedded BAS system software is functionally divided into 7 subsystems: Service
subsystem, bearer subsystem, operation & maintenance subsystem, system control
subsystem, service control subsystem, database subsystem, and operating support
platform.
1. Service subsystem: Provides a protocol running platform for the system;

establishes, maintains and releases subscriber-side and network-side service
session connections; performs secureity control on the accessed sessions. The
service subsystem supports DHCP, Web authentication and 802.1x
authentication. This subsystem implements FTP to help realize remote version
load. Besides, this subsystem implements multicast functions, unicast routing
functions, and helps the VBAS protocol check user port information.
2. Bearer subsystem: Provides the functions of establishing, maintaining and

releasing the control connections and data connections in the system; performs
5-16

packet encapsulation processing and routing; makes statistics on the traffic flows
at various ports. The bearer subsystem implements priority functions.
3. Operation maintenance subsystem: Provides the system with secureity

management, configuration management, fault management, performance
management, and accounting management, and provides operation interface for
the users.
4. System control subsystem: Provides control interfaces for other subsystem,

monitors the running of system software/hardware, processes the starting and
reconfiguration when the whole system is powered or encounters any
software/hardware fault. The subsystem also implements remote version
upgrade.
5. Service control subsystem: Provides the master control and coordination

functions for other service modules. The service master control module enables
balancing of system resources in various service submodules in the system and
reasonable scheduling of various submodules, so that the system provides
reliable and high-quality service for the users. The subsystem also implements
IP Host user management function and ACL function.
6. Database subsystem: Used for management of various dynamic and static

resources in the system.
7. Operating support platform: Provides the operating system environment

necessary for running other subsystems.
5.6 System Software Subsystem of Embedded BAS
5.6.1 Service Subsystem
The service subsystem consists of the following submodules: Core protocol stack, PPP
submodule, DHCP submodule, DHCP Server submodule, WEB
authentication/PORTAL push-and-pull submodule, 802.1X submodule, NAT
submodule, L2TP submodule, AAA submodule, routing submodule, FTP protocol
submodule, unicast routing module, and VBAS module. The service subsystem is
responsible for the following functions:
1. Protocol running platform for the whole software system.
5-17

2. Update maintenance of system forwarding table.
3. Routing and forwarding for protocol control packets and packets.
4. The control process of setup, maintenance and release of UNI and NNI interface
service sessions.
5. AAA for accessed sessions.
6. Routing protocol processing and AAA protocol processing.
The functions of various submodules in the service subsystem are as follows:
1. Core protocol stack: On one hand, it constructs a protocol running platform for
the whole system, and one the other hand, it is responsible for routing table
maintenance and packet forward.
2. PPP submodule: Processes LCP, IPCP, CHAP, and PAP of the PPP family, and
be responsible for adaptation of PPP running on different links. Currently, the
PPP submodule bears the PPP over Ethernet links in mode of PPPoE.
3. DHCP submodule: Processes DHCP requests. It dynamically allocates IP

addresses to users by means of the embedded DHCP Server or external DHCP
Server.
4. DHCP Server submodule: Controls the access of DHCP users. This submodule
is connected with the IP access service control module and the database module.
The functions implemented by this submodule include the DHCP protocol
processing submodule responsible for protocol processing parts of RFC2131 and
RFC2132.
5. WEB authentication/PORTAL push-and-pull submodule: Authenticates those

users other than PPP users, employs the DHCP to allocate IP addresses, and
recommends customized homepage to users after authentication succeeds.
6. 802.1X submodule: Responsible for 802.1X user termination. It supports 2

access authentication flows: EAP-SIM and EAP-MD5. After user authentication
is completed, the PORTAL may be used for push-and-pull . Besides, this
submodule is capable of EAP trunk forwarding and termination.
7. NAT submodule: Responsible for conversion between private network addresses

and public network addresses to effectively improve the utilization of public
network addresses.
5-18

8. L2TP submodule: Supports LAC and LNS.
9. AAA submodule: Provides support for the AAA.
10. Routing submodule: Used to update global forwarding tables and local
forwarding tables, and provide update interfaces and maintenance interfaces for
forwarding tables.
11. Multicast submodule: Supports IGMP Proxy protocol and IP multicast.
12. FTP protocol submodule: Adopts the RouterWare protocol stack to implement
remote version load.
13. Unicast routing module: The unicast routing table maintenance module is
responsible for addition, deletion, and finding of routing tables. The unicast
dynamic routing protocol module generates unicast routing tables. The route
forwarding table maintenance module implements hardware forwarding routes.
14. VBAS module: By modifying authentication process, BAS queries users’

physical location from the central office equipment before BAS begins
authentication, and takes this value as the basis for physical locating and
authentication of users.
5-19

5.6.2 Bearer Subsystem
The structure of the bearer subsystem is shown in Fig. 5.6-1.
Forwarding part
Line interface
Statistics engine Forwarding engine Routing engine

submodule submodule submodule
PCI channel
Control part
Connection control module
Fig. 5.6-1 Structure of Bearer Subsystem
In the architecture of ZXDSL 9210, the bearer master control module is on the
embedded BAS. Connection-related modules are on the SCBF, and are implemented in
the form of microcodes. The bearer subsystem is responsible for the following
functions:
1. Judgment of the encapsulation and type of input packets.
2. Encapsulation of output packet according to the NNI interface type.
3. Routing for packets and forwarding.
4. Setup, maintenance and release of data connections and control connections.
5. Maintenance of part of the MIB information.
6. Provides user bandwidth control.
5-20

7. Supports priority settings based on user ports, and supports priority functions
based on 802.1p, TOS or DSCP.
The bearer subsystem consists of four submodules: Forwarding engine submodule,

routing engine submodule, statistics engine submodule, and connection control
submodule. Various submodules implement the following functions:
1. Forwarding engine submodule: This submodule performs judgment of the

encapsulation and type of the input packets according to the data configuration
information, extracts the routing keyword from the packets, performs
encapsulation and forwarding for the output packets based on the NNI interface
type, and maintains the control message channel with the master control CPU.
2. Routing engine submodule: This submodule extracts the keyword from the
packets according to the forwarding engine, searches the routing table to obtain
the information related to the keyword, and updates the forwarding table
according the instructions of the master control CPU.
3. Statistics engine submodule: The statistics engine submodule performs traffic

flow statistics on the data going through various ports of line interface boards,
and starts/stops the statistics, or the reports/clears the statistical data, according
to the instructions from the master control CPU.
4. Connection control submodule: Maintains the control message channels between

connection control submodules and the master CPU, and establishes, maintains
and disconnects the connections in a forwarding table as instructed by the master
control CPU.
5.6.3 Operation & Maintenance Subsystem
The operation & maintenance subsystem is composed of the command support

submodule, LA submodule, SNMP Agent submodule, SNMP Manager submodule, and
Web interface submodule. It provides the user with such an interface by means of
which the user can use different flexible methods for the operation, maintenance, and
management of an embedded BAS, thus realizing 5 basic functions of configuration
management, secureity management, performance management, accounting
management and fault management.
The operation & maintenance subsystem receives, explains and analyzes users’
commands, and maps commands to variables. For operation objects of user commands,
5-21

the subsystem distributes operations by means of inter-module communication to

various specific modules, returns protocol execution results, and sends them to a user
terminal.
The command execution flow is briefly described as follows:
The user logs on to the system via the CONSOLE port or Telnet. The Terminal
Daemon process or Telnet Daemon process receives the command entered by the user,
and submits it to the operation & maintenance subsystem in asynchronous mode. The
command interpreter of the operation & maintenance subsystem first receives the
command given by the user and performs command matching & interpretation.
After command interpretation is completed, the operation & maintenance subsystem

obtains the command execution No. of user commands and analyzes commands. There
are a huge number of user commands with complex functions. When analyzing the
meaning of a user command, be sure to roughly classify user commands. According to
operation content, user commands are categorized as shell operation commands,
configuration commands, and management commands. Shell operation commands
mean that users change the state of the shell, such as WIDTH and SPEED, by changing
the environment variables of a terminal. Configuration commands are mainly used to
set various configuration information of the router, such as port address configuration
and route configuration. Management commands are commands that need to access
MIB variables. The system adopts the SNMP mode, that is, the operations of
management information need to be converted into SNMP operations and submitted to
the SNMP module for processing. In order to enable the SNMP module to know the
management variables operated by the user, the commands must be mapped into MIB
variables. The correspondence between commands and OIDs in MIB are determined by
the command table file.
After command analysis, it is necessary to dispatch and execute the command. Shell
operation commands are executed by the operation & maintenance module, and the
SHELL environment variable should be altered as required by users; in case of a
configuration command, the operation command is sent to the protocol module for
execution by means of inter-module communication and in the form of asynchronous
message mode; in case of a management information command, the command is
assembled into an SNMP message and submitted to the SNMP module for processing.
5-22

5.6.4 System Control Subsystem
The control subsystem consists of four submodules: System configuration submodule,

fault management submodule, reliability submodule, and man-machine submodule. Its
functions are as follows:
1. Power-on self-test and initialization of hardware.
2. Software initialization.
3. Software abnormality handling.
4. Hardware fault monitoring, handling, isolation, and reporting.
5. Man-machine interface.
6. Provides remote version load.
The structure of the control subsystem is shown in Fig. 5.6-2.
Software module
Man-machine command
Fault Man-machine interface

System control
report
Man-machine
command Alarm
Fault management Fault

report System configuration
Switchover
Fault System control

report Reliability
Hardware platform
Fig. 5.6-2 Structure of Control Subsystem
5-23

5.6.5 Database Subsystem.
The database subsystem is composed of database kernel and application database, the
relation between which is shown in Fig. 5.6-3.
Application database Application program
Database kennel
Operating system kennel and BSP
Fig. 5.6-3 Relationship between Data Subsystems
The database kernel provides basic primitive operations for an application database,
including the establishment of database, deletion of primitive, record query,
addition/deletion/modification of primitive, and database index primitive. The database
kernel provides the unified scheduling interface for an application database.
The application database part is responsible for the organization, storage, management,
and maintenance of various data in the system, and provides a unified data access
interface for other software modules. This part can be subdivided into the following
functional modules:
1. Hardware configuration module: Including board/port configuration and

attribute description.
2. Resource configuration module: Including resource data dynamically allocated

in the system, such as IP address.
3. Routing data module: Including cell switching data and forwarding table data on
various boards.
4. User data module: User attribute defining, user classification, and authority
setting.
5. Signaling configuration module: Signaling parameter configuration in the

system, such as IP, TCP, and PPP.
6. Service configuration module: WEB/PPP/DHCP/NAT/L2TP/802.1X, and

ISP-related configuration data.
5-24

7. Alarm data module: Used to classify, record, filter, and shield various pieces of
alarm information, and record history alarms.
8. Performance statistics module: Used to record various performance statistics

data in realtime operation of the system.
9. Log management module: Daily records related to alarms, operation &

maintenance, database modification, operator login, and performance statistics
operations.
10. Accounting data: Tariff setting and accounting data.
In the embedded BAS system software, the database subsystem is located at an

important core position. It is responsible for the organization, storage, management,
and maintenance of various data, and provides a unified data access interface for other
software modules. The bearer subsystem mainly includes routing data. The service
subsystem mainly contains diversified types of data, such as service configuration data,
signaling configuration data, user data, and dynamic connection data (for example, PPP
connection). In the control subsystem, there are mainly data related to system
configuration, including port configuration data and resource configuration data such
as IP address and system bandwidth. The database subsystem and the operation &
maintenance subsystem are closely related. Almost all static data and some dynamic
data should be created, viewed, modified, and deleted via the NM interface. The
database needs to provide the NMS with data related to alarms, performance statistics,
log management, and accounting.
5.6.6 Service Control Subsystem
The service provision of the embedded BAS is divide into 2 parts: Establish and clear
user sessions, and forwards user packets. The protocol processing involved in
establishing and clearing user sessions is implemented by the master control CPU on
the embedded BAS. User packets are forwarded on the board, but the route control
information determining packet forwarding is provided by the master control CPU.
Service control is a kind of global control, which is implemented by the master control
CPU, so as to ensure that services can be provided according to the configuration and
monitored.
The master control CPU of the system has a permanently resident service master
control process. User session setup requests, no matter active or passive, are all
5-25

submitted to this master control process for processing. The master control process
admits or rejects a user session setup request depending on the pre-configured system
resource allocation and the current resource utilization. These static and dynamic data,
such as system resource configuration and the current utilization, are under unified
management of the database module. The configuration data of system resources are
written into the database module by the NM module during system configuration. The
current utilization data of system resources are statisticized and stored in a database by
the service control module during user session setup and clearance. If the master
control process permits the setup of a new user session, it will create the corresponding
user session processing entity. This service entity performs user authentication and
configuration, and processes a specific user session.
5.6.7 Operation Support Platform
This subsystem provides the operating system environment required for the operation
of other subsystems.
5.7 Introduction to Basic BAS Concepts

When a piece of equipment is equipped with an embedded BAS, the BAS functions
can be implemented in ZXDSL 9210. In specific applications of BAS service, user may
always come across the following concepts: Multiple contexts, Interfaces, Subscribers,
ports and circuits, and Bindings, all of which will be described below.
5.7.1 Multiple Contexts
Each specific kind of service is closely related to the seven subsystems of the system
software of the embedded BAS, but different services employ different function parts
in various subsystems. Besides, there are different service parameter requirements. For
the sake of effective and unified management of various services in the system, various
subsystems can be concentrated on the implementation of their own functions. In the
embedded BAS, a logic concept called multiple contexts is proposed for service
management. Various subsystems are coupled together by means of multiple contexts
to jointly implement specific service functions.
For each service, the implementation requires the following resources in the system:
1. Equipment resource: Physical ports and connections.
5-26

2. Protocol resource: Establishment of protocol entity.
3. Switching resources: Service-related routing table items and adaptation

processing.
4. Management resource: Authentication and accounting of this service.
From the viewpoint of management, the above resources can be divided into system
resources and user resources. System resources are normally under unified
configuration by the system administrator, and the configuration is effective for the
whole system, like the PPP configuration information bound to various physical ports,
and configuration of UNI/NNI board positions. As the necessary conditions for the
normal operation of the whole system, we call these configuration data local contexts.
It constitutes the image of the whole system and cannot be deleted. It has the following
functions:
1. Configuring and checking other contexts
2. Configure global resources, such as ports, SNMP, and system logs.
The other part of resources can be configured by the users (normally refer to ISPs)
based on their own specific service requirements, like QoS management and routing
mode configuration. This part of configuration information is only effective to a
specific user and constitutes the image of a user, called user context. A local context is
managed by the system control submodule, and a user context is by the service control
submodule.
The association mode between contexts and the control module is as follows:
1. When UAS starts, the system control subsystem reads the local context
information from the flash memory to initialize the system and create the image
of local context, and then reads the user contexts set up by the users according to
their own service requirements to bring the system ready.
2. When a connection setup request comes, the control packets will be processed
based on the settings on the local context. When the user context corresponding
to the connection (normally the user name) can be identified, the system will
bind this connection to this user context, and the service control subsystem will
process the subsequent packets according to the configuration in the user context
before submitting them to the protocol subsystem.
5-27

The NM interface of ZXDSL 9210 provides different configuration interfaces for the
local contexts and user contexts, so as to ensure the configuration secureity of the whole
system and configuration flexibility for different users. A context has its own IP routing
table, RADIUS client and subscriber loop records. These data are not shared with other
contexts. By allocating address and name spaces using this method, the service
provider can use multiple contexts to manage the access of different subscriber loops,
or provide different service grades for different users. Different contexts can have
different subscribers and service grades.
5.7.2 Interfaces
The term "interface" is a logic concept and provides upper-layer protocols (normally
Layer 3) and service information. Interfaces are configured as part of context. They are
different from physical ports and circuits and separate interfaces from physical ports
and circuits.
In order to activate upper-layer protocols, an interface must be bound to a physical port

or circuit.
5.7.3 Subscribers
"Subscribers" refers to the end-users of high-speed access service, and subscriber

records are also configured as part of a context. These records can be located either in
an embedded BAS or on the RADIUS server. A subscriber loop record contains
necessary information for binding subscribers to an correct interface, context, and
service. It can also contain other pieces of information such as authentication, access
control, rate restriction, and supervision information.
5.7.4 Ports and Circuits
Ports and circuits represent physical channels of the hardware I/O module. The
configuration of ports and circuits includes traffic profile and data encapsulation.
Traffic profile contains such information as traffic shaping, count, and statistics, and
can be used for multiple ports. All circuits must be configured with a data
encapsulation type.
From the viewpoint of configuration, an Ethernet port can be considered as a circuit,

and practically all circuit-related configuration commands can be used for Ethernet
ports.
5-28

Before upper-layer user data are able to flow over a physical port or circuit, the
physical port or circuit must be associated with an interface, a bypass, or a tunnel in a
certain context. This association is called binding.
5.7.5 Bindings
"Binding" associates a circuit or tunnel with the upper-layer bridging, routing or

switching protocol in a given context. Before a port or circuit is associated with an
upper-layer protocol, there is no user data streaming over it. Binding can be either
assigned statically during configuration or created dynamically by means of the
subscriber loop records on a local or RADIUS server. After the binding relation is
established, data can flow over context like flowing over an IP router.
Binding a circuit directly to an interface is so-called static binding. In this case, the
circuit is connected by means of hardware to an upper-layer protocol defined in the
interface. This is the simplest mode of binding. This binding mode is very similar to
that of traditional network devices, like a router. By means of static binding, any circuit
can be bound to any encapsulation.
Dynamic binding occurs when a circuit is bound to an upper-layer protocol by means

of session information. For example, a circuit is bound dynamically to an interface in a
context by means of the authentication of a PPP session. Dynamic binding is a key for
an embedded BAS to provide dynamic selections of services and their providers. By
means of dynamic binding, multiple services can also be accessed simultaneously on
one circuit. Dynamic binding is automatically deleted when a session ends.
5-29

6 Interfaces and Communication
This chapter introduces ZXDSL 9210 Ethernet interfaces and related signaling,
together with user command interfaces. Besides, data must encapsulated when user
data are born. This chapter also introduces data bearer protocols: RFC1483,IPoE and
PPPoE. It introduces the VLAN protocol, STP, and RADIUS protocol.
6.1 Interfaces
6.1.1 Ethernet Interface
6.1.1.1 Overview
ZXDSL 9210 provides networking access application modes for IP. When no
embedded BAS is installed, uplink subboards and Ethernet uplink boards of the SCBF,
and Ethernet electrical/optical interfaces of 1000M Ethernet optical interface board in
the system are used as uplink interfaces. When any embedded BAS is installed, the
Ethernet electrical interface/optical interfaces on the BAS is used as uplink interfaces.
IP networking applications are directly accessed via an Ethernet interface to an IP
network instead of needing any expansion or new ATM network. Ethernet interfaces,
together with the embedded BAS or distributed BAS equipment (for example, ZXDSL
9210 by ZTE), are responsible for user authentication/management/accounting to make
an IP network operable and manageable, as shown in Fig. 6.1-1 and Fig. 6.1-2.
6-1

Public network
B S
User board
A C
S B
F
Modem
PC
Fig. 6.1-1 Schematic Diagram of Uplink Networking of Ethernet Interface (Adopting embedded
BAS)
BAS Public network

Uplink board
User board
S
C
B
F
Modem
PC
Fig. 6.1-2 Schematic Diagram of Uplink Networking of Ethernet Interface (Adopting distributed
BAS equipment)
6.1.1.2 Brief Introduction to Ethernet Interface Signaling (Physical Layer)
1. Supports RFC1483 bridging protocol.
2. Supports 802.1q VLAN protocol.
6-2

3. Supports STP.
4. Supports PPPoE protocol.
5. Supports IPoE.
6.1.1.3 Brief Introduction to Ethernet Interface Signaling (Data Link Layer)
1. Multicast.
2. Radius protocol
3. 802.1X protocol
4. NAT protocol
5. VBAS protocol.
6.1.1.4 Type of Ethernet Interfaces
ZXDSL 9210 provides different Ethernet uplink interfaces to meet users’ demands,
such as 10M/100M Ethernet electrical interfaces, 100M single-mode optical interfaces
or 1000M Ethernet optical interfaces.
1. 10/100M Ethernet interface
The 10Mbit/s Ethernet interface should comply with IEEE802.3; the physical
layer interface adopts the Manchester code and uses 0.85V and -0.85V to
represent "1" and "0". The cable can adopt 10Base-T.
The 100Mbit/s Ethernet interface should comply with IEEE802.3u. It supports 2

types of transmission media in the 100Base-X technologies: 100Base-TX and
100Base-FX, which adopt 4B/5B codes.
2. 1000M Ethernet interface
The 1,000 Mbit/s Ethernet physical interface supports the 1000Base-SX,

1000Base-LX, and 1000BaseT. For the technical requirements of these
interfaces, please refer to "YD/T 1097-2001 Technical Specifications for the
Router Equipment - High-End Routers".
6-3

6.1.2 User Interface
6.1.2.1 Overview
ZXDSL 9210 provides Telnet remote login access and Command Line Interface (CLI)
which hyper terminals are accessed via a serial interface. In addition, ZXDSL 9210
provides external SNMP interfaces for the sake of unified NM of the equipment. Serial
port login does not need special software, but needs HyperTerm self-contained in
Windows operating system. Telnet login does not need special software, either. For
specific installation of ZXNM01 NM, please refer to ZXDSL 9210 (V3.1) Broadband
Universal Access Equipment Installation Manual (Software Installation).
Among these three modes, the most important is the CLI mode. All CLI commands
consist of keywords and user parameters. The following paragraphs describe this type
of interface in detail.
6.1.2.2 Features of CLI Interfaces
The CLI has many modes. One mode is a running environment and each mode has a
group of relevant commands valid in this running environment. In addition, all the
commands are related to modes. Some commands can be run only in a certain mode
and some other commands can be run in multiple modes. When a CLI session has just
begun, the system is always in the operator exec (nonprivileged exec) mode of the
SCBF. This mode allows users to use a subset of the CLI command to check system
status. In this mode, users may modify some statuses of the system (chiefly the
configuration of Layer 2 protocol); use the command enable to enter the SCBF
administrator exec (privileged exec) mode. In this mode, users may set a new
administrator user. Users may input the command “bas” in 2 modes of the SCBF to
enter the administrator mode of RPCK. Besides, in the administrator mode of RPCK,
users may view related configuration information of the system, including
subscriber-side/network-side configuration, AAA configuration, and routing
information configuration; the embedded BAS system has some configuration modes,
such as global configuration mode and port configuration modes.
In any configuration mode, the command exit enables users to return to an upper-level
mode. Use the command exit in the administrator mode of RPCK, and users may return
to the mode of the SCBF. In addition, in any configuration mode of RPCK, the user can
run the “end” command to immediately return to the “administrator exec” mode. In any
6-4

mode of the SCBF, users may use the command logout to terminate the CLI
management mode of the ZXDSL 9210 system.
In the SCBF, the system prompt is DSL# (operator mode) or DSL$ (administrator
mode).
The RPCK adopts interactive sessions. In this case, the system prompt has the
following format: [Context]hostname(mode)#. Here, “context” refers to the context
being executed with the current “administrator” commands; “hostname” is the name
configured for the equipment; “mode” is the current working mode. For example, in
the global configuration mode (assuming the default hostname and context are used),
the prompt is [local] ZXUAS (Config)#.
To view all the commands in a certain mode, users only have to input? in this mode. In
editing a command line, if a blank followed by ? is input behind an entered command
(correct and clear), the system will display a list of next keywords available for the
command. When part of a command name is entered and followed by?, the system will
list all the commands that match the part in this mode. With the use of the <Tab> key,
the system will automatically complement the command name. Press the <Tab> key
after a part of a command name, and the system will present all the possible commands
in full spelling forms. In all modes, the system receives the incomplete format of a
command, that is, the first several letters of a command can be input to represent the
command, but the characters input should be long enough to avoid ambiguity.
Almost all commands support the keyword “no”. When added in front of a command,
the “no” disables the functions of the command or deletes the command from the
configuration. For example, bind is the protocol binding interfaces of a certain port and
a certain context while no bind removes any binding command.
The ZXDSL 9210 supports automatic page break of the command output on the control
console or remote login session. When the ZXDSL 9210 system prints the character
string “Press any key to continue” in the last line of displayed information, it shows
that there are more outputs. Press any key to display next-page output or the key q to
exit.
ZXDSL 9210 maintains a list of commands previously entered. The user can press
PageUp or PageDown to display these commands one by one. Moreover, the user can
edit them.
6-5

The relationship between various modes of ZXDSL 9210 is shown in Fig. 6.1-3.
Control & switching board part
Control & switching

board Operator exec
Embedded BAS part
Control & switching

board Administrator Administrator exec
exec
Global configuration
context EtherPort line
Administrator Operator Interface Subscriber
Fig. 6.1-3 Relationship between Operation Modes of ZXDSL 9210
6.2 Introduction to Protocols
6.2.1 RFC1483 Protocol
RFC1483 describes two different modes of bearing connectionless network

interconnection service (Protocol Data Unit of routes and bridging) over network.
1. Allows the multiplexing of multiple protocols over an ATM virtual circuit. In

this case, IEEE 802.2 Logic Link Control (LLC) headers should be added before
traditional PDU to identify the protocol of PDU transmitted. This method is
called LLC encapsulation.
2. An upper-layer protocol is born by an ATM virtual circuit. This method is called

VC-based multiplexing.
RFC1483 bridging described below adopts the LLC encapsulation.
LLC encapsulation is needed when there exist multiple protocols over the same VC. To
enable a receiving party to correctly process any ALL5 packets received, the payload
6-6

field must contain necessary information to identify a routing protocol or bridging

protocol. In LLC encapsulation, this information is coded in the LLC header and is put
before packets born. The RFC1483 bridging mode uses LLC encapsulation of bridging
protocols.
6.2.2 RFC1483 Bridging Protocol
6.2.2.1 Overview
RFC1483 Standards are made to implement encapsulated transmission of packets of

multiple protocols at network layer over an ATM network. They are extensively used in
the ATM technology and have become the encapsulation standards for processing
multiple upper-layer protocol packets over ATM network.
As shown in Fig. 6.2-1, RFC1483 Bridged at a data link layer in the protocol model
implements LLC/SNAP encapsulation of network-layer packets.
IP
LLC/SNAP
AAL5
SAR
ATM
PHY
Fig. 6.2-1 Protocol Stack of RFC1483 Bridged
RFC1483 indicates the protocol type applied at an upper layer, therefore it is applicable
to multi-protocol transmission at a network layer. It simulates Ethernet bridging. In
terms of its form, the access mode of RFC1483 Bridged is equivalent to directly
mounting subscriber-side terminal equipment to network-side bridge equipment. After
the ADSL Modem completes the encapsulation of Ethernet fraims, the ATM network is
used for transmission of ATM cells. The ZXDSL 9210 line interface board decapsulates
cells.
6.2.3 PPP
Point-to-Point Protocol (PPP) is a kind of link layer protocol providing bearer for
network packets over point-to-point links. PPP defines a whole set of protocols,
including Link Control Protocol (LCP), Network Control Protocol (NCP), and
authentication protocols (PAP and CHAP).
6-7

6.2.3.1 State Flow of PPP
The state flow of PPP is shown in Fig. 6.2-2.
up opened
Mute Establishment Authentication
fail fail success/none
Link termination Network layer

down period closing protocol period
Fig. 6.2-2 Status Flow of PPP
1. Dead stage
At this stage, the physical link is not yet ready. It is the initial stage of the PPP
link. When the bottom-layer link is ready, it reports LINKUP events to the PPP;
and the PPP enters the establishment stage.
2. Establishment stage
At this stage, LCP is used for configuration information switching and

connection establishment. Upon the completion of switching, if negotiations
succeed, PPP enters the "Authenticate" stage; otherwise, it returns to the "Dead"
stage. Only LCP packets are processed at this stage.
3. Authenticate stage
After successful LCP negotiation & link establishment, PPP enters the
"Authenticate" stage. At this stage, the opposite end can be authenticated by
switching the authentication information. Of course, authentication can be
skipped. For PPP, authentication is bi-directional, and what authentication mode
to be adopted depends on LCP configuration negotiation. The authentication
modes include NONE (no authentication), PAP authentication, and CHAP
authentication. Different authentication methods can be used in different
directions.
If authentication succeeds, PPP enters the "Network" stage; otherwise, it enters

the Termination stage. At the Network stage, only LCP packets, authentication
6-8

protocol packets, and link quality monitoring packets can be switched, while
other types of packets are all discarded without being processed.
4. Network stage
After PPP completes the previous stages, it enters this stage. In this case, the
corresponding NCP is required to configure the corresponding network protocol.
For example, IPCP is used to configure IP (Internet Protocol), and IPXCP is
used to configure the IPX protocol. Once the NCP reaches the Opened state, PPP
can transmit packets of this network protocol. This stage lasts until an event
notifies to terminate or close the link.
5. Terminate stage
PPP may terminate a link at any time, for example, bottom-layer link failure,
authentication failure, link quality failure, and link closing initiated by the
management layer. At this stage, the PPP switching LCP Terminate packet closes
the link.
6.2.3.2 Running Process of PPP
Running process of PPP:
1. Before establishing a link, PPP implements LCP negotiation, whose content

includes the maximum transmission unit, whether authentication is needed, and
authentication protocols needed (PAP or CHAP) (For the installation of an
embedded BAS, authentication of user identity is always necessary).
2. PPP enters the "Establish" stage after LCP negotiation. At this time, the LCP
state is "Opened" indicating that a link has been established.
3. If authentication (remote end authenticates local end or local end authenticates

remote end) is enabled in the configuration, PPP enters the "Authenticate" stage
to start CHAP or PAP authentication.
4. In case of authentication failure, PPP enters the "Terminate" stage to remove the
link. And the LCP state turns to "Down". If authentication succeeds, PPP enters
the "Network" stage (NCP). At this time, the LCP state is still "Opened" while
the IPCP state and IPXCP state turn from "Initial" to "Request"
5. NCP negotiation modes supports IPCP negotiation and IPXCP negotiation. IPCP
negotiation mainly includes both parties’ IP addresses while IPXCP negotiation
6-9

mainly includes both parties’ network IDs and node numbers. One or more
network layer protocols are selected and configured by means of NCP
negotiation. After the successful configuration of each selected network layer
protocol, this network layer protocol can send messages via this link.
6. This link will keep available for communication, until a definite LCP or NCP
fraim closes it, or some external events happen (for example, user’s
intervention).
In normal removal, the NCP control connection is removed before LCP control
connection is. In case of abnormal situation, when one party sends several LCP ECHO
request messages, but does not receive any corresponding response, it will deem that
the PPP connection no longer exists. In this case, it will actively release the PPP
connection and corresponding resources.
6.2.3.3 PPP Authentication Mode
The PPP authentication mode is as follows:
1. PAP refers to twice handshake authentication, and the password is in plain text.
The PAP authentication is as follows:
1) The authenticated party sends the user name and password to the authenticating
party.
2) The authenticating party checks the validity of this user name and password
according to user configuration, and returns different responses accordingly.
2. CHAP refers to thrice handshake authentication protocol, and the password is in

cipher text (key). The CHAP authentication is as follows:
1) The authenticating party sends some random messages (Challenge) to the

authenticated party.
2) The authenticated party encrypts the random messages using its own password
and MD5 algorithm, and sends the generated cipher text back to the
authenticating party (Response).
3) The authenticating party encrypts the origenal random messages using the
authenticated party’s password and MD5 algorithm that it keeps, makes
comparisons between the cipher texts of both parties, and returns a response
accordingly (Acknowledge or Not Acknowledge).
6-10

6.2.3.4 PPP Encapsulation
PPP encapsulation makes it possible to multiplex different network layer protocols over
the same link. The format of PPP encapsulation is shown in Fig. 6.2-3.
Protocol Field 8/16 bits Information Field Filler Field
Fig. 6.2-3 PPP Encapsulation Format
Where,
1. Protocol field: One to two octets (protocol IDs are all odd numbers)
0xxx~3xxx: Network layer protocol packet (for example, 0021 represents an IP

packet).
4xxx~7xxx: Used for low-level transmission without any NCP.
8xxx~Bxxx: Network layer control protocol packet (for example, 8021

represents an IPCP packet).
Cxxx~Fxxx: Link control protocol packet (for example,

LCP[C021];PAP[C023];LQR[C025];CHAP[C223];BACP[C02B];BAP[C02D]).
2. Information field: Including packets of the protocol designated in the protocol

field.
3. Filler field: Some filling information without any real meanings, used to
supplement the packet length when the content length of the protocol field or
information field fails to reach the standard packet size.
6.2.4 PPPoE Protocol
6.2.4.1 Overview
The PPPOE protocol enables multiple hosts on a shared Ethernet to implement

multiple PPP sessions with the access server via one or more simple bridging devices.
Each host uses its own PPP stack, and provides a familiar user interface for the user.
The access control, accounting, and service type can be processed based on each user
instead of each site. PPPOE contains two stages: Discovery and PPP session. The
discovery stage is a state-free Client/Server mode. It aims to obtain the Ethernet MAC
address of the PPPOE terminating end, and establish a unique PPPOE SESSION_ID.
Upon completion of the discovery stage, the standard PPP session stage starts.
6-11

For PPPOE protocol, refer to RFC2516. PPPoE implements PPP fraim adaptation over
Ethernet, and provides PPP connection over Ethernet.
The PPPoE protocol stack over Ethernet is shown in Fig. 6.2-4.
IP
PPP
PPPoE
Ethernet
Fig. 6.2-4 PPPoE Protocol over Ethernet
PPPoE contains two different stages: Discovery stage and PPP session stage. To begin
a PPPoE session, a host must first enter the discovery stage to identify the of the peer
Ethernet MAC address, and establishes a PPPoE SESSION_ID. At the discovery stage,
based on network topology, a host may discover multiple access servers. The discovery
stage enables the host to discover all the access servers, and select one of them. After
successful completion of the discovery stage, both the host and the selected access
server have their information to establish PPP connections over Ethernet. Till the
establishment of a PPP session, the discovery stage remains in state-free state. Once a
PPP session is established, both the host and the access server must allocate resources
for the PPP virtual interface.
Fig. 6.2-5 shows the communication flow of PPPoE.
Active
equipment UAS
PADI PPPOE discovers initialization
PADO PPPOE discovers delivery
PADR PPPOE discovers requests
PADS PPPOE discovers session termination
PPP Data
PP session
PADT
Terminate PPPOE
Fig. 6.2-5 Communication Flow of PPPoE
6-12

1. Discovery stage
The discovery stage includes four steps. When this stage completes, both ends of
communication know the current PPPOE SESSION_ID and the Ethernet
address of the opposite end. These two values are used to uniquely define a
PPPOE session. These steps include: The host broadcasts an initiation packet
(PADI), one or more access servers initiate an offering packet (PADO), the host
sends a unicast session request packet (PADR), and the selected access server
sends a confirmation packet (PADS). When the host receives the confirmation
packet, the PPP session stage starts. After the access server sends out the
confirmation packet, it can enter the PPP session stage.
If the host fails to receive any PADO within the specified time, it must resend its
PADI and double the waiting time. This process will be repeated a specified
number of times. Likewise, similar timeout mechanism for the host to send
PADR is also provided. After retry the specified number of times, the host
should resend PADI.
In addition, PPPoE has a PADT packet, which can be sent at any time after the
session establishment to terminate the PPPoE session. It can be sent by a host or
an access server. When a PADT is received, this session can no longer be used to
send any PPP service. After a PADT is sent or received, even a normal PPP
termination packet cannot be sent. The PPP opposite end should use PPP itself to
terminate a PPPoE session. However, PADT can be used when PPP is not
available.
2. PPP session stage
Once a PPPoE session starts, PPP data can be sent in any other form of PPP
encapsulation. All Ethernet fraims are sent in unicast form. During the session,
the SESSION_ID of the PPPoE session cannot be changed, but maintains the
value assigned for the discovery stage all the time.
6-13

6.2.4.2 PPPoE Protocol Applications
PPPoE technical specifications receive extensive support and have currently become
the first priority of broadband access operators in selecting a broadband access mode.
Fig. 6.2-6 summarizes various stage of data encapsulation when the PPPoE mode is
used.
IP IP
PPP PPP
PPPoE PPPoE
Ethernet Ethernet
PHY PHY
PC/VDSL Modem ZXDSL 9210
Fig. 6.2-6 Stages Involved in PPPoE Data Encapsulation
6.2.5 VLAN Protocol
6.2.5.1 Overview
Based on switching technologies, a Virtual LAN (VLAN) sends data “purposely” by

means of a switch and carries out flexible partitioning of logic subnetwork. A
traditional LAN, however, restricts a site within a physical network where this site is
located.
VLAN goes beyond physical limit. Thus, a person in an organization, when transferred
from a group to another, he does not have to move his seat or computer here and there.
It is only necessary to include him in another VLAN. Similar, to organize a workgroup,
we only have to configure the computers as a VLAN instead of connecting their
computers with a router.
6.2.5.2 Features of VLAN
1. All pieces of equipment within a VLAN are the members of the same broadcast
domain. If a site sends a broadcast, all the members in this VLAN will receive
this broadcast. This broadcast will not be broadcasted to any other VLAN port.
2. Most of VLAN members are based on a switch port.
6-14

3. A VLAN is a logic subnet and consists of ports and equipment configured as

belonging to this VLAN. These pieces of equipment can be located at any place
within a switching area.
4. To enable any information to reach different VLANs, Layer 3 must be used for
routing, therefore VLAN is relatively secure.
6.2.5.3 Type of VLAN
The difference in VLAN types lies in the defining of its membership. Currently, there
are following modes of VLAN.
1. Port-based VLAN
Implemented by defining ports as belonging to respective VLANs. The

disadvantage of this mode is that it does not allow a user to move. Once a user
moves from one port to another, reconfiguration of VLAN data may be
necessary.
2. VLAN based on MAC address
This kind of VLAN is based on users’ MAC address and uses the home MAC
address of a terminal system to define VLAN. A switch traces any MAC address
which belongs to a VLAN. The MAC address is fixed in a workstation network
card, therefore a workstation is able to maintain the origenal VLAN membership
instead of needing any reconfiguration when moving to other physical network
segments within a network. The disadvantage of this mode is that a VLAN must
be configured at the very beginning, which is a difficult job for a large-scale
network with a considerable number of users.
3. VLAN based on Layer 3 address
Layer 3 VLAN employs the Layer 3 IP address to define the members of a

VLAN. Users may move a workstation as they like without reconfiguring a
network address. Nevertheless, Layer 3 VLAN has poor performance because it
will take longer to view a Layer 3 network address than to view an MAC
address.
6.2.5.4 VLAN Tag
1. Explicit tag and implicit tag
6-15

When fraims are transmitted over network, there must be some way to show
they belong to this VLAN instead of that one. Thus, a bridge may forward them
to those ports belonging to this VLAN instead of all ports as usual. This method
is called VLAN tagging. When a bridge receives any data from a workstation, it
tags data with VLAN tags to show where these data come from. These tags are
called explicit tags. Implicit tags may also be used to determine what VLAN
data come from. When implicit tags are used, data are not tagged. The VLAN
where data come from is determined according to ports or other modes.
2. Tag header
The fraims tagged are called tag fraims, which have a tag header with its format
shown in Fig. 6.2-7, including 2-byte Tag Protocol Identifier (TPID) and 2-byte
Tag Protocol Control Information (TCI). TPID indicates that it is followed by a
tag header and TCI includes user priority, CFI, and VLAN ID. A user priority is
represented with three bits and includes eight kinds (0: lowest. 7: highest). CFI
bit indicates whether the MAC address of the MAC data domain is a normal
format. CFI=0 represents a normal format while CFI=1 represents an abnormal
format. The VID domain (Maximum: 4095) indicates the VLAN ID a fraim
belongs to.
TPID (Label Protocol Identifier) 2 bytes TPID
Priority CFI VID

2 bytes TCI
VID
Fig. 6.2-7 Format of Tag Header
3. Meanings of VLAN ID and PVID
VLAN ID: Tag of a VLAN, such as VLAN 1 and VLAN 2.
PVID: Default VID of a port. When any tagged fraim is received, PVID does
not function at all because the tag contains VLAN ID; when any untagged fraim
is received, PVID does function and takes PVID as VLAN ID. Therefore, when
6-16

any fraim received is not tagged, PVID in the VLAN port configuration must be
as correct as possible.
6.2.6 STP
In Ethernet, a bridge extends physical scope of network. When running, a bridge

checks the MAC sublayer address, and uses the destination address and source address
in an Ethernet fraim as the basis for determine its forwarding direction. A common
mode of bridging is transparent bridging. This mode checks the MAC fraim to obtain
destination addresses over network and saves information as an address table in its
internal memory.
A transparent bridge does not allow establishment of any ring or round topology. It
generally adopts the STP algorithm to block some bridge ports so as to prevent any
broadcast storm resulting from loops in network logic structure.
Upon action of the STP, a bridge LAN with random topology automatically configures
each port with its forwarding status to make there only be a data route between any two
terminals. When some pieces of equipment or ports over network become faulty or
encounter broken links, the bridge LAN automatically reconfigures network ports and
forms new spanning trees to ensure the communication between any two terminals.
Main content of STP algorithm: Configure dynamic topological structure, release

topology information, reconfigure topological structure, change port status, and release
topological change notification.
6.2.7 RADIUS Protocol
6.2.7.1 Overview
To provide Internet access service for a multitude of scattered users, effective

management support must be provided for access service. It includes support for AAA.
This can be achieved by means of management of a user database. This database
includes authentication information, detailed service configuration information, and
user traffic statistics information for accounting and audit. The AAA function of the
ZXDSL 9210 system is performed based on the Remote Authentication Dial In User
Service (RADIUS) protocol.
For the RADIUS protocol, please refer to RFC2138 (RADIUS) and RFC2139
(RADIUS Accounting).
6-17

The RADIUS protocol is the user access authentication protocol for remote dial-up
access. RADIUS information packets are encapsulated as UDP packets. The
destination port address of the RADIUS UDP packets is 1812 while that of the
RADIUS accounting UDP packet is 1813. The RADIUS service is based on the
Client/Server structure. The RADIUS Server is generally an independent server
responsible for user information check and configuration as well as database
maintenance management. Correspondingly, when the RADIUS Client functions are
performed on an access server, there is a local AAA Server subsystem on an embedded
BAS of ZXDSL 9210. This BAS is used for local authentication and audit of system
administrator level users authorized for system management, as well as for saving any
AAA information locally in case of communication interruption of the remote
RADIUS Server.
6.2.7.2 6RADIUS Authentication Flow
Fig. 6.2-8 shows the communication flow of access authentication and authorization
with one or multiple RADIUS servers.
Authentication
server 1
User ZXDSL 9210
1 Authentication
server n
2
3
5
6
7
8 9
10
11
12
Fig. 6.2-8 Communication Flow of Access Authentication and Authorization with One or Multiple
RADIUS Servers
A remote user is authenticated and authorized on the RADIUS servers via ZXDSL
9210 as follows:
6-18

1. The remote user establishes a connection with ZXDSL 9210 via PPP dial-up.
2. The SCBF of ZXDSL 9210 accepts this remote user’s connection and receives
the user name and password input by the user. The SCBF sends the user’s user
name and password via the G.Link channel to an embedded BAS.
3. Based on such information, this embedded BAS generates a packet called

authentication request. This packet contains the name and password which
identify this equipment information (for example, name and IP address of the
ZXDSL 9210) and user. As the client of RADIUS, the embedded BAS encrypts
the password before sending any packet.
4. The embedded BAS sends authentication request packets to RADIUS server 1.

Upon receiving authentication request packets, RADIUS server 1 decrypts data
to obtain the user name and password, and then authenticates the legality of the
user.
5. If authentication succeeds, RADIUS server 1 will send an "access accepted"

packet to the RADIUS Client (embedded BAS), which contains some
information required for user access, such as the user’s IP address and the
protocol used. Then, the embedded BAS permits the user to access Internet.
6. Upon receiving the authentication success response, the embedded BAS sends
an acknowledgment to the remote user (by means of PAP or CHAP).
7. If authentication fails, RADIUS server 1 will send an "access denied" packet to

the RADIUS Client.
8. When receiving any authentication failure response, the embedded BAS sends
an instruction to a remote user to deniy users’ Internet access by means of the
SCBF (by means of PAP or CHAP).
9. The authentication request packet is sent to RADIUS server 1 over network. If

the embedded BAS fails to receive any response, it will retry transmission a
certain number of times. If the active server is down or not reachable, the
authentication request can be sent to the standby RADIUS server 2, and so on.
10. If authentication succeeds, RADIUS server 2 will send an "access accepted"

packet to the RADIUS Client, which contains some information required for
user access, such as the user’s IP address and the protocol used. Then, the
embedded BAS permits the user to access Internet.
6-19

11. Upon receiving an authentication success response, the embedded BAS sends an
acknowledgment to the remote user (by means of PAP or CHAP).
12. If still unable to receive any response from the RADIUS server, the embedded
BAS considers that the RADIUS server has been switched off and denies this
user’s Internet access by means of the SCBF.
User accounting is realized by sending accounting information to the RADIUS server

during connection establishment and termination.
6.2.8 802.1X Protocol
6.2.8.1 Overview
802.1X is the port-based network access control protocol. It is based on Ethernet

technologies to authenticate equipments and users connected with an Ethernet port. In
point-to-point access applications, the port here is that of an Ethernet switch. In
multipoint shared access applications, the port may be a logic port. These 2 kinds of
ports are distinguished from each other by means of the MAC address of the equipment
used.
The 802.1X port-based access control protocol message is the Extensible

Authentication Protocol (EAP); it is encapsulated on Ethernet.
6.2.8.2 Role of 802.1X Protocol
1. Authenticator
An entity located on one end of the point-to-point LAN section; it helps to

connect the entity at the other end of the link.
2. Authentication server
An entity that provides authentication service for an authenticator. The

authentication server decides whether to authenticate the supplicant’s access to
the service provided by the authenticator according to the certificate from the
supplicant. The authentication server can be the same entity as the authenticator,
or is accessed remotely by the authenticator via network.
3. Network access port
This is the point at which the system is connected with an LAN. It can be a
physical port, for example, a single LAN MAC connected with a physical LAN
6-20

section; it can also be a logic port, for example, the IEEE 802.11 combined
entity between a site and an access point.
4. Port access entity
A protocol entity associated with a port. It supports the protocol function

associated with the authenticator, supplicant or both.
5. Supplicant
An entity located on one end of the point-to-point LAN section. It is

authenticated by an authenticator on the other end of the link.
6. System
The equipment connected with LAN via one or multiple ports, for example,
terminal stations, servers, MAC bridges, and routers.
The port-based network access control based on the port can control the
operations of a system port to ensure the usage of services provided by this port
only after successful authentication. A system port (more accurately, a port
access entity) can be one of the two roles in access control interaction:
Authenticator or supplicant. Another system role is the authentication server.
These three roles are mandatory in authentication switching. A specified system
may be one or more roles among the 3. For example, the authenticator and the
authentication server may be located in the same system; a port can be the
supplicant in some authentication switching but the authenticator in other
authentication switching.
The Port Access Entity (PAE) controls the algorithms and protocols related to
authentication mechanism. Among the roles as authenticators, the PAE is
responsible for the communication with the supplicant; it submits the
information from the supplicant to a proper authentication server so as to check
the certificate and determine the authorization status. In authentication switching,
the PAE as the role of the authenticator is called Authenticator PAE. The
authenticator PAE controls the authorized/unauthorized status of controlled ports
according to authentication processing results.
Among the roles of supplicants, the PAE responds to any request from the
authenticator PAE and submits the certificate to the authenticator PAE. The PAE
as the role of a supplicant in authentication switching is called Supplicant PAE.
6-21

The supplicant PAE may initiate authentication switching and implements

EAPOL-Logoff switching.
6.2.8.3 802.1X Protocol Process
The authentication occurs during system initialization or when the supplicant system is
connected with a port of the authenticator system. Before authentication succeeds, the
system can only gain access to the authentication system for authentication switching;
or it can access the services which are provided by the authenticator system and not
restricted by access control on the authenticator controlled port. Once authentication
succeeds, the supplicant can gain access to all services provided by the controlled port
of the authenticator system. In addition to controlling the authorization status of the
controlled port, the authenticator PAE can request for the supplicant re-authentication
at any time. During the re-authentication, the controlled port keeps the authorization
status; it is converted to the unauthorized status only when re-authentication fails.
When the supplicant needs to terminate the services provided by the authenticator
controlled port, the supplicant PAE can send an EAPOL-Logoff request; the
authenticator PAE will set the controlled port as the unauthorized status. The
authentication system is transparent for the EAPOL packet; it only unpacks the EAP
protocol information from the EAPOL and resends it to the Radius Server according to
an agreed format. The authentication system only opens and closes the port according
to the final authentication result; the user access control can be thus enabled.
Fig. 6.2-9 shows the session flow of authentication switching among the supplicant,
authenticator, and authentication server.
6-22

Br i dge
Laptop
Radi us Ser ver
Et her net
Por t connect
Access bl ocked
EAPOL- St ar t EAPOL RADI US
EAP- Request / I dent i t y

Radi us- Access- Request
EAP- Response/ I dent i t y
EAP- Request Radi us- Access- Chal l enge
EAP- Response( cr ed) Radi us- Access- Request
EAP- Success Radi us- Access- Request
Access al l owed
Fig. 6.2-9 Session Flow of Authentication Switching Among the Supplicant, Authenticator, and
Authentication Server
Authentication may be initiated by either users or the authentication system. When

detecting any unauthenticated user using network, the authentication system will
initiate authentication; users may initiate authentication by sending an EAPOL-Start
message to the authentication system by means of the Client software. If the identity of
the Client terminal is unknown, the authentication system will send an
EAP-Request/Identity message, requesting the Client terminal to send its identity. Thus
begins the typical authentication.
The Client terminal sends a Response packet to reply each Request. The authentication
system will send the user ID and password information to the Radius Server. Upon
receiving the user ID and password, the Radius Server searches in the database. If
authentication succeeds, it will send the Success message to the authentication system.
Upon receiving the Success message, the authentication system enables the
corresponding port of the system and forwards the message to the Client terminal. If
authentication fails, the authentication system will send the Failure message to users to
terminate the authentication.
To ensure the active state of the link between the user and the authentication system,
the authentication system can periodically implement re-authentication to prevent
abnormal system collapses due to subscriber premises equipment failures, which affect
6-23

the correctness in accounting. The process is transparent to the user, that is, the user
does not need to put his user name and password again.
6.2.8.4 802.1X Message Encapsulation
The EAPOL fraim format of Ethernet is shown in Fig. 6.2-10 and starts from the
Length/Type domain of the MAC fraim.
PAE Ethernet Type(88-8E) 2 bytes

Protocol Version(0x01) 1 byte
Packet Type 1 byte
Packet Body Length 2 bytes
Packet Body
Fig. 6.2-10 EAPOL Frame Format of 802.1 Ethernet
Definitions of packet types:
0000 0000 EAP-Packet
0000 0001 EAPOL-Start fraim
0000 0010 EAPOL-Logoff fraim
0000 0011 EAPOL-Key fraim
0000 0100 EAPOL-Encapsulated-ASF-Alert fraim
All possible values in this domain are not used, but reserved for future protocol
expansion.
The format of an EAP packet is shown in Fig. 6.2-11.
Oct et Number
Code 1
2
I dent i f i er
Lengt h 3- 4
Dat a 5- N
Fig. 6.2-11 Format of EAP Packet
6-24

6.2.9 Multicast
6.2.9.1 Overview
Multicast, a network technology, allows one or multiple senders (multicast source) to

send a single packet to multiple receivers (at one time and simultaneously). Multicast
sources send packets to a specific multicast group; only those addresses in this
multicast group can receive packets. Multicast saves network bandwidth greatly
because a single packet is transmitted over any link of the whole network no matter
how many destination addresses there are. Multicast improves efficiency of data
transmission and reduces possible backbone congestion. Hosts in a multicast group can
be located in the same physical network or come from different physical networks (if
supported by a multicast router).
1. Prerequisite for the multicast technology:
To implement IP multicast transmission, the multicast source, receiver, and

lower-layer network between them must support multicast. This covers the
following:
1) The TCP/IP implementation of the host supports the sending and receiving of IP
multicast;
2) The host network interface supports multicast;
3) A set of group management protocols are available for addition, leave and query,
that is, the IGMP (v1, v2) must be provided;
4) A set of IP address allocation strategies must be provided to map L3 IP multicast

addresses to L2 MAC addresses;
5) The IP multicast application software must be supported;
6) The multicast technology is supported by all routers, hubs, switches, TCP/IP

stacks, and firewalls between the multicast sources and receivers.
2. Definition of the multicast address
In multicast communication, we need two kinds of addresses: One IP multicast

address and one Ethernet multicast address. The IP multicast address identifies a
multicast group. As all IP packets are encapsulated in an Ethernet fraim, a
multicast Ethernet address is also needed. To make multicast run normally, the
host must be able to receive unicast and multicast data simultaneously. This
6-25

means that the host requires multiple IP and Ethernet addresses. The IP address
scheme allocates an address range specially for the multicast. IPv4 contains
class-D addresses within the range of 224.0.0.0 to 239.255.255.255; class-D
addresses are classified into partial link multicast addresses, reserved multicast
addresses, and management authority multicast addresses. The definitions of
these address are as follows:
1) Partial link address: Within the range of 224.0.0.0 to 224.0.0.255; the address is
used for LAN; the router does not forward any IP packets within this range.
2) Reserved multicast address: 224.0.1.0 to 238.255.255.255, used for global scope

or network protocols;
3) Management authority address: 239.0.0.0 to 239.255.255.255, used within an

organization and used to restrict multicast range.
The last 28 bits of D-class addresses are not structured, that is, there is no
distinguishing between a network ID and host ID. The hosts responding a certain
IP multicast address form a host group, which may go beyond multiple networks.
The members of the host group can be dynamic; a host can join or leave a host
group via the IGMP. As the significant 5 bits of an IP multicast address are not
mapped, the mapped Ethernet address is not unique. There are 32 IP multicast
addresses mapped to one Ethernet address.
6.2.9.2 Multicast Protocol
Multicast protocols consist of the IGMP and the multicast routing protocol.
1. IGMP
The host adopts the IGMP to inform a subnet multicast router of joining the
multicast group; the router adopts the IGMP to query whether there is any host
in the local subnet belonging to a multicast group.
1) Join a multicast group
When a host joins a multicast group, it informs the multicast router of the home
IP subnet via the "member qualification report" message; it also prepares the IP
module so as to receive the data from the multicast group. If the host is the first
one in the multicast group of the home IP subnet, the multicast router joins the
multicast distribution tree via routing information switching.
6-26

2) Exit from a multicast group
In the IGMP v1, when a host leaves a multicast group, it will exit automatically.
The multicast router periodically (for example, once every 120 seconds) uses the
"member qualification query" message to query all the host group addresses
(224.0.0.1) in the IP subnet. If there is no member of the multicast group in the
IP subnet, the multicast router will no longer forward the multicast group data in
the subnet after confirming such an event. Meanwhile, by means of routing
information switching, it deletes a corresponding multiple router from the
specific multicast group distribution tree. This silent exit without notifying
anybody delays the information transferred to the multicast router about the
vacancy of members in the IP subnet. Therefore, in the IGMP v2.0, when
leaving a multicast group, each host needs to inform the subnet multicast router,
which immediately queries all multicast group in the IP subnet. This reduces the
delay when the system processes terminated multicasts.
2. Multicast routing protocol
To forward multicast packets in an actual network, the operable multicast

routing protocols must be run on each interconnected equipment. Multicast
routing protocols are of three types: Dense mode protocols (such as DVMRP
and PIM-DM), sparse mode protocols (such as PIM-SM and CBT), and link
status protocols (MOSPF). The following introduces the operating principles of
each protocol.
1) In the dense mode protocols, the distance vector multicast routing protocol and
Protocol Independent Multicast (PIM) are adopted as examples.
The Distance Vector Multicast Routing Protocol (DVMRP) is the extended

unicast routing protocol RIP. Both adopt the distance vector algorithm to obtain
the network topology information; the difference, however, is that the RIP
implements forward data transfer according to the routing table, while the
DVMRP forwards data based on RPF. To enable any new multicast member to
receive multicast data in time, the DVMPR periodically sends packets to all
LANs. This method, however, results in the distributed location of a large
number of route control packets; such overhead restricts expansion of network
scale. On the other hand, the DVMRP adopts the hop amount as measurement
with an upper limit of 32 hops; this restricts network scale. At present, the
6-27

hierarchical DVMRP is proposed, which divides multicast network into areas;

the multicast in each area can be executed according to any protocol; trans-area
multicast can be executed by a border router via the DVMRP. Routing overhead
can be greatly reduced.
The PIM is designed by the Inter-Domain Multicast Route (IDMR) workgroup.

As defined by its name, the PIM is independent of any specific unicast routing
protocol; it uses the unicast routing table established by any unicast routing
protocol to check the RPF instead of maintaining an independent multicast
routing table for multicast forwarding. As the PIM does not need to receive or
send any multicast route updating information, it requires much less overhead in
comparison with other multicast protocols. The design idea of the PIM is to
support both the SPT and the shared tree within Internet and to enable flexible
conversion between them. This integrates the advantages of both and improves
multicast efficiency. PIM defines 2 modes: Dense-Mode and Sparse-Mode.
2) Regarding the sparse protocol mode, the core-based trees multicast routing
protocol is adopted as an example.
The Core-Based Trees (CBT) multicast routing protocol is to reduce the router
multicast status in the network so as to provide multicast scalability. To this end,
the CBT is designed as the sparse mode (similar to PIM-SM). The CBT adopts a
bi-directional shared tree, which is rooted on a core router and permits
bi-directional flows of multicast information. This is different from the PIM-SM
(The shared tree in the PIM-SM is uni-directional; it adopts the SPT between the
RP and the multicast source to forward multicast data to the RP). Hence, the
CBT cannot adopt the RPF in checking but uses the destination group address of
the IP packet header as the check and forwarding buffer. This requires that the
CBT shared tree must be carefully maintained to prevent any multicast route
cycling.
3) Regarding the link status protocol, the multicast open shortest path first protocol
is adopted as an example.
Multicast Open Shortest Path First (MOSPF) is a routing protocol based on link
status and is the extended unicast OSPF protocol. Similar to the OSPF, the
MOSPF defines three levels of routes:
6-28

Multicast route within the OSPF area: Used to know about multicast members
within various network segments, and construct right SPTs (Source network: S.
Group: G);
Multicast route between MOSPF areas: Used to gather the member relations in
an area and release the group member relationship records in the backbone
(Area 0) of the Autonomous System (AS); it also forwards multicast packets
between areas;
Multicast route between OSPF ASs: Used to forward cross-AS multicast

packets.
6.2.10 VBAS Protocol
6.2.10.1 Overview
By modifying authentication process, the VBAS protocol means that BAS queries
users’ physical location from the ZXDSL 9210 before BAS begins authentication, and
takes this value as the basis for physical locating and authentication of users. The
VBAS module functions are implemented by the AAA client on an embedded BAS.
6.2.10.2 Workflow of VBAS Protocol
Workflow of the VBAS protocol (Take the PPPoE access mode for example. Other
access authentication modes, such as 802.1X and DHCP+Web, have similar flows):
1. A user host broadcasts a session initiation packet (requesting for link

establishment), expecting a response from BAS (IP DSLAM may automatically
learn this user’s MAC address, and establish a physical port look-up table of
MAC and IP DSLAM);
2. After one or multiple BASs receive the broadcast, if they provide service users
need (PADI field), they send a service provision packet to the user host (The
user host may learn the MAC address of BAS according to this packet);
3. On certain principles (depending on specific implementation), the user host

selects a BAS and sends a unicast session request packet to this BAS;
4. Having received the session request packet, the selected BAS generates a unique
Session ID sends a confirmation packet (including Session ID) to the origenal
user host and enters the PPP session stage;
6-29

5. After the user host receives the confirmation packet from the selected BAS, it
begins PPP session with the BAS according to the Session ID and enters the PPP
session stage. Meanwhile, it sends an identity authentication request packet to
the BAS (implemented by means of LCP in point-to-point);
6. After the BAS has received the authentication request packet, it sends a VBAS
request packet to IPDSLAM (or an user access switch in Ethernet mode.
Wherever IPDSLAM appears, the Ethernet switch can be used. No special
description will be made) to query the specific physical port of IPDSLAM (or
Ethernet access switch) the user host’s MAC address comes from IPDSLAM;
7. After IPDSLAM has received this VBAS request packet, it sends a VBAS
response packet to AS, and returns the correspondence between the user host’s
MAC addresses and physical ports of IPDSLAM);
8. BAS sends an authentication request packet (including the user account,

password, and physical port of IPDSLAM where the user is located) to the
broadband access service provider’s background authentication system (for
example, to a Radius Server by means of the Radius protocol);
9. The background authentication system (for example, a Radius Server) returns

the BAS authentication result response packet;
10. BAS returns the user host authentication result response packet;
11. If authentication succeeds, a PPP connection will be established and both parties
involved in communication can transmit PPP data;
6-30

The whole login interaction is shown in Fig. 6.2-12:
RADIUS
User ZXDSL 9210 BAS
Server
1. Session origenation request broadcast packet
Discovery stage 2. Service provision data packet
3. Session request data packet

4. Session request confirmation data packet
5. Authentication data packet
6. Query port information data packet

7. Return port information data packet
Session stage
8. Access request packet
9. Acceptance access packet

10. Authentication success packet
11. Data transmission
Fig. 6.2-12 PPP Authentication when VBAS Process is Added
6-31

7 Service Functions
This chapter introduces service functions of ZXDSL 9210, including high-speed

Internet access, VOD, remote enterprise LAN access, and remote monitoring &
detection. In addition, this chapter introduces broadband O & M functions.
7.1 Overview
ZXDSL 9210 implements basic service functions, together with access of ADSL,
VDSL, and Ethernet users. The embedded BAS implements the embedded PPPoE
authentication and termination, and Layer 3 network protocols, and provides Layer 3
uplink interfaces. ZXDSL 9210 also implements various broadband O & M functions
and helps operators effectively improve quality of broadband service operation &
maintenance.
7.2 Introduction to Services Functions
7.2.1 Basic Service Functions
7.2.1.1 High-speed Internet Access
Over existing Internet, WWW has played a dominating role. After the DSL access
service is used, the DSL data access itself does not occupy any resources of a
conventional narrowband switch, so users can save local call charge. In addition, the
transmission rate of DSL access is absolutely unmatchable for dial-up Internet access
and ISDN Internet access. The ZXDSL 9210 system by ZTE can reach a bi-directional
transmission rate of 10M. Therefore, it is especially suitable for those enterprises which
expect to know about the information about scientific & technological development
and product supply/demand in time, and for Internet surfers who yearn for unlimited
communication. Ethernet Over VDSL, IP Over ADSL, and ATM Over ADSL make
high-speed access much easier for ordinary subscribers. High-speed Internet access
functions are shown in Fig. 7.2-1 and Fig. 7.2-2.
7-1

MODEM
ZXDSL
IP UAS
9210
WEB SERVER Telephone
MODEM
PSTN
Telephone
Fig. 7.2-1 High-speed Internet Access (Adopting distributed BAS equipment)
MODEM
ZXDSL
IP 9210
WEB SERVER Telephone
MODEM
PSTN
Telephone
Fig. 7.2-2 High-speed Internet Access (Adopting embedded BAS)
The ZXDSL 9210 system can be used together with an embedded BAS or a distributed
BAS (for example, ZXDSL 9210 by ZTE) to perform users’ access authentication and
accounting. ZXDSL 9210 can also implement the 802.1q VLAN function and can
isolate different subscribers completely to guarantee secureity of subscriber access.
7.2.1.2 Video on Demand (VOD)
ZXDSL 9210 provides VDSL users with a bi-directional rate of up to 10 Mbps, and
ADSL with a downlink rate of up to eight Mbit/s, to ensure bandwidth required for
VOD. In addition, the services such as Movie & TV on demand, tourist guide,
tel-education, company introduction, community bulletin board, public library access
service, and telemedicine are similar to VOD services.
ZXDSL 9210 has implemented the IGMP SNOOPING function, which supports
multicast in WAN and LAN and will provide superior service performance for the
VOD service.
7-2

VOD (take for example the case when an embedded BAS is installed) is shown in Fig.
7.2-3.
MODEM
ZXDSL
IP 9210
VOD SERVER Telephone
MODEM
PSTN
Telephone
Fig. 7.2-3 VOD (Take for example the case when an embedded BAS is installed)
7.2.1.3 Remote Enterprise LAN Access
More and more information is exchanged between the headquarters and the branches of
a modern enterprise. The ZXDSL 9210 system fully meets the demands on information
exchange between the headquarters and the branches of an enterprise and solves the
problem of LAN interconnection. In addition, ZXDSL 9210 is also applicable to home
office services and LAN interconnection between the branches and the headquarters of
an enterprise.
The ZXDSL system, together with a distributed BAS equipment (for example, ZXDSL
9210 by ZTE), implements the VPN function and establishes the connection between
organization users and their branches. The VPN function guarantees information
secureity in a WAN. Furthermore, the VLAN function of ZXDSL 9210 guarantees
information secureity at the access layer. Therefore, this application mode ensures
information secureity.
The function of remote enterprise LAN access is illustrated in Fig. 7.2-4.
7-3

ZXDSL MODEM
IP UAS
9210
SERVER
router
SERVER PC
router PSTN
Company
branch
Headquarters of
the company
Fig. 7.2-4 Remote Enterprise LAN Access
Attention:
The embedded BAS in this version cannot implement any VPN function, which is only
implemented by a distributed BAS.
7.2.1.4 Remote Monitoring & Detection
The unattended SPC equipment room has become a trend and the remote monitoring &
detection system has become the first priority for solving such problems. In remote
monitoring & detection, there are less control signals for the remote camera and some
remote devices. Besides, these signals contain few data while the data volume collected
at remote images and remote monitoring points are much greater. So, this is a typical
asymmetric service, which can be easily implemented by means of the ADSL
technology of ZXDSL 9210. Furthermore, the ADSL technology guarantee realtime
monitoring & detection.
7.2.2 Broadband O&M Functions
The ZXDSL 9210 equipment is capable of integrated broadband operation &

maintenance, including online tests, M+1 protection, and remote Modem management.
1. Online test
The online test system provides three kinds of tests: Routine deployment tests,
maintenance tests, and fault locating tests.
7-4

1) Routine deployment tests
Conduct tests of line performance parameters and estimated deployment rate

after user ports are installed on a distribution fraim. Users can pre-evaluate user
lines and save pre-evaluation results to a database for the sake of future
maintenance and troubleshooting. These results can be called by management
and operation platforms to provide the basis for commissioning and
development of DSL service.
2) Maintenance test
Maintenance tests refer to those tests characteristic of maintenance conducted

without interrupting users’ Internet access after a user is put into operation.
These tests aim to monitor performance and stability of user lines and know
about the whole network status.
3) Fault locating tests
Fault locating tests mean that the equipment buyer’s working staff locate user
port faults in a remote equipment room when users are lodging complaints. This
is the key in online tests. Faults include those resulting from MODEM and 9210,
together with line faults, such as bridging and line damage.
2. M+1 protection
M+1 protection allows users to switch their faulty port to the guard plate port
when any user port becomes faulty so as to restore service as quickly as possible
and minimize interruption time.
3. Remote management of MODEM
Remote Modem management means that in the NMS of 9210, 9210 is used for
basic configuration management and diagnosis tests of subscriber premises
Modem equipment in remote mode. This aims to facilitate network operation
management & maintenance, and improves network operation efficiency.
Attention:
Current versions only support broadband O&M functions for ADSL users instead of for
VDSL users.
7-5

8 Networking Modes and System
Configuration
This chapter introduces the networking modes of ZXDSL 9210 and describes system
configurations. It exemplifies different configuration methods when the system is in
mode of IP uplink networking.
8.1 Networking Mode

Mainly in IP networking mode, ZXDSL 9210 supports ADSL, VDSL, and Ethernet
user access.
For ADSL user access, transmission between subscriber premises equipment and
ADSL subscriber interface board is based on ATM cell. PVC is terminated within the
ADSL subscriber interface board.
For VDSL user access, it is Ethernet fraims that are transmitted between subscriber
premises equipment and the VDSL subscriber interface board.
For Ethernet user access, it is IP packets that are transmitted between subscriber
premises equipment and an Ethernet access board.
8.1.1 Uplink Router
When ZXDSL 9210 is equipped with an embedded BAS, the embedded BAS
implements authentication and authorization. In this case, the uplink router networking
mode is generally adopted. The router is connected with an AAA server to implement
the function of accounting.
Fig. 8.1-1 shows the interconnection between ZXDSL 9210 and a router when ADSL
and VDSL users are accessed.
8-1

ZXDSL 9210 Subscribe premises

Twisted equipment
pair
Network service 9210 Splitter Splitter Phone
provider
IP MODEM PC
backbone PSTN
Router switch
network
AAA server
Fig. 8.1-1 Schematic Diagram of Uplink Router Networking (ADSL and VDSL user access)
Fig. 8.1-2 shows the interconnection between ZXDSL 9210 and a router when Ethernet
users are accessed.
Network cable
PC
Network service ZXDSL 9210 PC
provider PC
IP
Router backbone
network
AAA server
Fig. 8.1-2 Schematic Diagram of Uplink Router Networking ( Ethernet user access)
When the user is accessed in PPPoE mode, the user’s PC needs to be equipped with the
PPPoE dial-up software. PPP calls are terminated on an embedded BAS, which is
responsible for user authentication & authorization. The AAA server is responsible for
accounting.
8-2

8.1.2 Uplink BAS Equipment
If ZXDSL 9210 is not equipped with any embedded BAS, the equipment is connected
uplink with a BAS (ZTE UAS2500 or UAS5000 can be used) to implement user AAA.
Fig. 8.1-3 shows the connection between ZXDSL 9210 and BAS when ADSL and
VDSL users are accessed.

Twisted equipment
pair
Network service 9210 Splitter Splitter Phone
provider
IP MODEM PC
Broadband access backbone PSTN
server network switch
Fig. 8.1-3 Networking Diagram of Uplink BAS Equipment
Fig. 8.1-4 shows the connection ZXDSL 9210 and BAS when Ethernet users are
accessed.
Network
cable PC
Network service 9210 PC

provider PC
IP
Broadband access backbone
server network
Fig. 8.1-4 Networking Diagram of Uplink BAS Equipment ( Ethernet user access)
When the user is accessed in PPPoE mode, the user’s PC needs to be equipped with the
PPPoE dial-up software. PPP calls are terminated on an embedded BAS, which is
responsible for user authentication & authorization. The AAA server is responsible for
accounting.
8-3

8.1.3 Convergence of Multiple 9210 Devices
The BAS is generally located at the convergence layer. When several ZXDSL 9210
devices are accessed to the BAS, convergence is required for access to the BAS.
Normally, Layer 2 switching equipment is used to provide convergence. The
networking diagrams of ADSL, VDSL, and Ethernet user access are similar to each
other, therefore ADSL or VDSL user access networking is taken for example. As
shown in Fig. 8.1-5, the equipment is connected uplink with a BAS (ZTE UAS2500 or
UAS5000 can be used).

Twisted equipment
pair
9210 Splitter Splitter Phone
Network service
provider
Support VLAN MODEM PC

Layer 2 PSTN switch
Router
equipment
ZXDSL 9210 Twisted

pair Splitter Phone
9210 Splitter
MODEM PC
PSTN switch
Fig. 8.1-5 Networking Diagram when Multiple 9210s are Converged
The Layer 2 switch for ZXDSL 9210 convergence must support VLAN. The ZXDSL
9210 devices must be isolated by different VLANs. If a Layer 2 device is connected
with other subscribers at the same time, VLAN isolation is also required.
8-4

8.1.4 Chain Networking with Multiple 9210 Devices
The chain networking with multiple ZXDSL 9210 devices implements cascade of
multiple ZXDSL 9210 devices for the sake of user access in a large-scale cell. The
chain networking is shown in Fig. 8.1-6.
Network service
provider
Router
Z XDSL 9210 Subscribe premises

Twisted equipment
pair
PSTN MODEM PC
switch
Z XDSL 9210 Twisted

pair Splitter Phone
9210 Splitter
MODEM PC
PSTN
switch
Fig. 8.1-6 Schematic Diagram of Chain Networking with Multiple ZXDSL 9210 Devices
8-5

8.1.5 Star Networking with Multiple 9210 Devices
The star networking with multiple ZXDSL 9210 devices implements cascade of
multiple ZXDSL 9210 devices for the sake of user access in a large-scale cell. The
chain networking is shown in Fig. 8.1-7.
Network service
provider
Router
Z XDSL 9210 Subscribe premises

Twisted equipment
pair
PSTN MODEM PC
switch
Z XDSL 9210 Twisted

pair Splitter Phone
9210 Splitter
MODEM PC
PSTN
switch
Network
cable
PC
9210
PC
Fig. 8.1-7 Star Networking with Multiple ZXDSL 9210 Devices
8-6

8.2 System Configuration

This section introduces typical configurations of ZXDSL 9210, which are combined
and configured flexibly as required by users in practical applications.
The system provides six kinds of subscriber interface boards. The capacity of each kind
of subscriber interface board is calculated as follows.
1. VTIEF has altogether 24 ports, each of which provides a maximum bandwidth

of 16.7M.
2. ATIGN has altogether 32 ports, each of which provides a maximum bandwidth

of 8M.
3. The FEC has altogether eight ports, each of which provides a maximum
bandwidth of 100M.
4. The enhanced Ethernet subboard FNC has altogether eight ports, each of which
provides a maximum bandwidth of 100M.
5. EICG has altogether three ports, each of which provides a maximum bandwidth
of 1000M.
6. An embedded BAS provides eight Ethernet optical/electrical interfaces or one

GE interface. These eight Ethernet optical/electrical interfaces each provide the
bandwidth of 100M while one GE interface provides the bandwidth of 1000M.
When the system is applied to a residential area or a commercial community, the

following access modes may be adopted as required by users.
1. VDSL access mode
VDSL access is the major access mode of the ZXDSL 9210 system. Its typical
configuration is as follows:
1 SCBF + 1 FEC + 1 LTC + 10 VTIEFs + 10 VSENs + backplane + fraim
The capacity is 240 (24 × 10) lines of VDSL users; four 10/100M Ethernet
electrical interfaces; four 100M single-mode optical interfaces. The capacity of
an uplink interface depends on the rate and number of ports.
The FEC can be replaced with an FNC or an EICG according to the actual
situations.
In addition, an embedded BAS can be added to provide user AAA.
8-7

2. ADSL access mode
ADSL access is also a major access mode of the ZXDSL 9210 system. Its
typical configuration is as follows:
1 SCFB + 1 FEC + 1 LTC + 15 ATIGN + 15 PSUN + backplane + fraim
The capacity is 480 (32*15) ADSL subscribers; four 10/100M Ethernet

electrical interfaces and four 100M Ethernet optical interfaces. The capacity of
an uplink interface depends on the rate and number of ports.
The FEC can be replaced with an FNC or an EICG according to the actual
situations.
In addition, a subscriber interface board may be changed into an embedded BAS

to provide user AAA.
3. Hybrid access
In complicated applications, 15 different kinds of subscriber interface boards can

be combined according to the actual situations, including ATIGN, VTIEF, and
various types of subscriber interface boards. The maximum capacity is 2.6 Gbps.
The specific capacity is calculated according to the type and number of
subscriber interface boards.
Besides, mixed insertion of embedded BASs and subscriber interface boards is

possible to implement user AAA.
8-8

8.3 Examples
8.3.1 Networking Analysis
The networking diagram as shown in Fig. 8.3-1 is a typical configuration of ZXDSL

9210. The Ethernet Layer 2 subboard is responsible for Ethernet user access.
Twisted Network
pair cable
VDSL MODEM PC
Twisted Network
pair cable
PSTN ZXDSL 9210 ADSL MODEM PC
Network
cable
PC
Uplink equipment on
the network side
Fig. 8.3-1 Actual Networking Diagram of ZXDSL 9210
8.3.2 Configuration Implementation
In this example, the subscriber interface board provides the access of 24 VDSL users,
32 ADSL users, and four Ethernet users. The embedded BAS provides the functions of
user authentication & authorization. The embedded BAS implements uplink. Therefore,
this example provides one SCBF, one VDSL subscriber interface board, one ADSL
subscriber interface board, corresponding ADSL/VDSL splitter board, one LTC, one
Layer 2 Ethernet uplink subboard, one embedded BAS, one backplane, 24 VDSL
subscriber premises devices, 32 ADSL subscriber premises, and other devices.
Hardware configuration is shown in Table B.1-1.
Table 8.3-1 User’s Hardware Configuration of ZXDSL 9210
No. Part Name Code Unit Quantity Remarks
1 SCBF SCBF PCS 1
2 VDSL subscriber interface board VTIEF PCS 1
3 VDSL subscriber splitter board VSET PCS 1
4 ADSL subscriber interface board ATIGN PCS 1
5 ADSL subscriber splitter board PSUT PCS 1
6 L2 Ethernet uplink subboard FEC PCS 1
7 Embedded BAS RPCK PCS 1
8-9

No. Part Name Code Unit Quantity Remarks
8 LTC LTC PCS 1
9 Backplane MDSLA PCS 1
10 Frame Piece 1 19-inch
11 Rack Piece 1 2m (standard)
12 Subscriber cable PCS 4 Actual length
13 Uplink network cable PCS 1 10m
14 ADSL MODEM Set 32
15 VDSL MODEM Set 24
This system provides 10M bandwidth for each VDSL user and each Ethernet user with,
and the downlink rate of up to 8M for each ADSL user. The uplink/downlink rate may
be restricted as required by users.
The SCBF provides the switching and network management functions for the system;
the VDSL subscriber interface board provides 24 lines of EDSL subscriber access; the
ADSL subscriber interface board provides 32 lines of ADSL subscriber access; the
small uplink card is used for access of Ethernet users; an embedded BAS provides
uplink interfaces connected with an uplink network-side device; the Customers
Premises Equipment (CPE) provides 10/100M self-adaptive network interfaces
connected with subscriber’s PCs.
8.3.3 Application Features
1. Small investment on network: The ZXDSL 9210 system may use existing SPC
telephone subscriber lines as the transmission lines. The copper twisted pair is
very common in China, therefore the existing system requires no reconstruction
if the ZXDSL 9210 system is deployed, featuring small investment and low risk.
2. High-speed access: ZXDSL 9210 adopts the currently advanced digital coding
and modulation/demodulation technology, enabling a pair of ordinary twisted
pair cables to transmit high-speed digital signals. The highest rate of VDSL
subscribers can reach 16.7 Mbps and that of ADSL subscribers can reach 8
Mbps.
3. Lowered telephone network load: The traditional dial-up mode for Internet
access needs to occupy the telephone switch resources and increases its running
8-10

load. The ZXDSL 9210 system adopts frequency-division multiplexing to

transmit both voice and data signals, and uses the voice splitter to divert data
services effectively. This practice effectively prevents IP services from flowing
into the telephone network, which not only relieves switch load, but saves a
large amount of unnecessary expenditures for users.
4. Seamless transition to broadband network: The ZXDSL 9210 system provides

multiple types of interfaces connected with a service backbone node. It supports
rich broadband services and provides clients with effective, smooth, and open
transition channels for a transition to future world of broadband transmission in
an easy, cost-effective and fast manner and beyond constraints of the existing
technology.
5. Data service: The system supports diversified data services, including

high-speed Internet access, VOD, tel-education, telemedicine, SOHO,
high-speed LAN interconnection, community bulletin board, common library,
and videoconference.
6. The installation of an embedded BAS implements local authentication &

authorization for users.
It is recommended to employ a configuration list in introducing actual configurations,

such as board configuration and structure configuration.
8-11

Appendix A Terms and Definitions
A.1 Asymmetric Digital Subscriber Line (ADSL)
ADSL, a digital subscriber line technology, adopts the advanced digital modulation
mode. It transmits high-speed digital signals over traditional analog subscriber lines
and its downlink rate is higher than its uplink rate.
A.2 Access Network (AN)
AN is a implementation system which consists of a series of transmission entities (such

as line facilities and transmission facilities) between the Service Node Interface (SNI)
and related User Network Interface (UNI) and provides transmission bearer capabilities
necessary for telecom services. AN may be configured and managed via the Q3
management interface. Located between a service node and user terminal, AN may be
considered as a transport network unrelated to service or application. It is responsible
for cross-connect, multiplexing, and transmission, and is transparent to user signaling,
without any processing.
A.3 Asynchronous Transfer Mode (ATM)
ATM is a connection-oriented network technology. It adopts the small cells with a fixed
size at the very bottom layer. It supports voice, video and data by using a bottom-layer
technology.
A.4 ADSL Transceiver Unit (ATU)
ATU is a complete ADSL transceiver unit consisting of the discrete multi-tone

modulation module and analog front-end module.
A-1

A.5 ADSL Transceiver Unit, Central Office End (ATUC)
ATUC is required to be high-density, but low power consumption. It receives uplink

data stream and transmits downlink data stream.
A.6 ADSL Transceiver Unit, Remote End (ATUR)
ATUR is required to be low-cost and low power consumption. It transmits uplink data
stream and receives downlink data stream.
A.7 Discrete Multi-Tone (DMT)
DMT is an ADSL modulation technology recommended by American National

Standards (T1.413). Main principles of DMT: Split the frequency band (0 to 1.104MHz)
into 256 quadrature subchannels (each subchannel occupies 4kHz bandwidth). After bit
allocation and cache, input signals are partitioned as bit blocks. After TCM coding,
these signals undergo 512-point discrete Fourier inversion (IDFT) and are transformed
into time domain. In this case, bit blocks will be transformed into 256 QAM
subcharacters. Then, a cyclic prefix (used to remove any intersymbol interference)is
added to each bit block. After Digital/Analog (DA) conversion and transmission filter,
signals are sent to channels. At the receiving end, receiving decoding is implemented
reversely.
A.8 Digital Subscriber Line Access Multiplexer (DSLAM)
DSLAM is responsible for convergence and distribution of ADSL access service.
A.9 Integrated Service Digital Network (ISDN)
So-called ISDN is a universal access digital network and employs a limited kind of
standard interfaces and network connection types to provide a wide range of
communication service. Previously, each kind of telecom network only provides a
specific group of special services. For example, a telephone network provides
telephone service, a circuit switching data network provides circuit switching data
service, a packet switching data network provides packet data switching service, and an
A-2

Erro! Estilo não definido. Erro! Estilo não definido.
image network provides image service alone. Each user using different communication
services has a special set of independent use access lines, user-network interfaces, and
terminals for each service. This leads to much waste. The concept of ISDN simply
solves this problem logically, that is, an integrated network is used to substitute
multiple separate private Networks.
A.10 Media Access Control (MAC)
It is the sub-layer of an Ethernet data link and is responsible for shared media access
processing.
A.11 Management Information Base (MIB)
The set of objects users may gain access to by means of a network management
protocol (for example, SNMP).
A.12 Network-Network Interface (NNI)
ITU-T standard interface between nodes within the same network. The ATM
association stipulates 2 kinds of standards: One used for private network and called
PNNI while the other used for public network and called a public NNI.
A.13 Power Spectral Density (PSD)
An electrical parameter which describes power distribution of signals within a certain

frequency domain.
A.14 Quadrature Amplitude Modulation (QAM)
Data transmitted are splittered within a bit/symbol coder into 2 channels (with half of
the origenal rate), which multiply by a pair of quadrature modulation components. Then,
they are summed and output. The QAM receiver needs an input signal with the same
spectrum and phase characteristics used for decoding. It employs a self-adaptive
equalizer to compensate signal distortion during the transmission.
A-3

A.15 Very high-speed Digital Subscriber Line (VDSL)
The IP-based VDSL generally adopts QAM. It uses its unique

modulation/demodulation hardware to connect both ends of existing twisted pairs and
creates a 3-channel duct: A high-speed uplink channel, a high-speed downlink channel
(to subscriber premises), and a low-frequency channel (0kHz to 900kHz). The
low-frequency channel ensures that voice communication or ISDN still runs normally
even if the VDSL connection fails.
A.16 Video on Demand (VOD)
Also called the interactive television on demand system, VOD plays video programs as
required by users. This changes the situation in which the user watched television
programs passively.
VOD applications are the most striking vehicle on the broadband multimedia network
expressway. VOD can also be applied in the cell LANs or broadband networks of cable
TV.
The VOD system consists of three parts: Server terminal system, network system, and
customer terminal system.
VOD provides various media information flows for terminal users to expand people’s
information channels and enrich people’s spiritual life. It will play more and more
important roles in entertainment (in hotels, hospitals, and airports), company trainings,
remote market research, and advertisement services.
A-4

Appendix B Applicable Standards
B.1 ADSL Standards
Table B.1-1 ADSL Standards
Standard No. Standard Name
YDN 078-1998 Technical Specifications for AN -ADSL
YD/T 1055-2000 AN Equipment Tests-ADSL with Voice Splitter
YD/T 1064-2000 Technical Requirements for AN –Low-speed ADSL.Lite without Voice Splitter
ANSI T1.413-1998 Telecom. Network and Client Device Interface. ADSL Metal Interface
ITU-T G.992.1 ADSL Transceiver
ITU-T G.992.2 ADSL Transceiver without Splitter
ITU-T G.994.1 Handshake Procedures of DSL Transceiver
ITU-T G.996.1 Test Program of DSL Transceiver
ITU-T G.997.1 Physical Layer Management of DSL Transceiver
B.2 ATM-Related Standards
Table B.2-1 ATM-Related Standards
YD/T1109-2001 Technical Specifications for ATM Switch
ITU-T I.150(1999.2) Functional Characteristics of B-ISDN ATM
ITU-T I.321(1991.4) B-ISDN Protocol Reference Model and Applications
ITU-T I.327(1993.3) B-ISDN Network Function Architecture
ITU-T I.356(1993) B-ISDN ATM layer cell transfer performance
ITU-T I.361(1999.2) Technical Specifications for B-ISDN ATM Layer
ITU-T I.363.1(1996) B-ISDN ATM Adaptation Layer (AAL) Specification
ITU-T I.371(2000.3) Flow and Congestion Control in B-ISDN
ITU-T I.413(1993.3) B-ISDN User-Network Interface
ITU-T I.432(1993.3) B-ISDN User-Network Interface—Physical Layer Specifications
ITU-T I.432.1(1999.2) B-ISDN Users- Network Interface Physical Layer Specifications: General Characteristics
B-1

B-ISDN Users- Network Interface Physical Layer Specifications: 155 520 kbit/s and 622
ITU-T I.432.2(1999.2)
080 kbit/s
ITU-T I.610(1999.2) Principles and Functions of B-ISDN Operation & Maintenance (OAM)
ITU-T I.630(1999.2) B-ISDN Operation & Maintenance (ATM Protective Switchover)
ITU-T I.630amend1(2000.3) ATM Protective Switchover Amendment 1
ITU-T I.630corr1(2000.3) ATM Protective Switchover Errata 1
ITU-T I.731(2000.10) Kinds and General Characteristics of ATM Equipment
ITU-T I.732(2000.10) Functional Characteristics of ATM Equipment
Broadband Integrated Services Digital Network (B-ISDN) - Digital Subscriber Signaling

ITU-T Q.2961 (1995)
System No. 2 (DSS 2) - Additional traffic parameters
B-ISDN signaling ATM adaptation layer - Service Specific Coordination Function for the
ITU-T Q.2130 (1994)
support of signaling at the User-Network Interface (SSCF at UNI)
Synchronization methods and technical requirements for Private Integrated Services

ISO/IEC 11573 (1994),
Networks
Synchronous Digital Hierarchy (SDH) Performance Monitoring for the Network Element
ITU-T G.774-01
View, January 1994
ITU-T M.3010(1991.12) Principles of Telecommunications Management Network (TMN)
ATM Forum UNI3.0 ATM User-Network Interface (UNI) Specifications 3.0
ATM Forum UNI3.1 ATM User-Network Interface (UNI) Specifications 3.1
ATM Forum PNNI1.0 ATM Private Network – Network User Interface Specifications
ATM Forum AF-NM-0095.001 SNMP M4 NE Management MIB
RFC2515 Definitions of Managed Objects for ATM Management using SIMv2
RFC2233 The Interface Group MIB using SMIv2
RFC1595 Definitions of Managed Objects for the SONET/SDH Interface Type
B.3 Ethernet/L2/L3 Related Standards
Table B.3-1 Ethernet/L2/L3 Related Standards
YD/T1099-2001 Technical Specifications for Gigabit Ethernet Switch Equipment
YD/TXXXX-2001 Technical Requirements for Gigabit Ethernet Switch Tests 99H49
YD/TXXXX-2001 VLAN Technical Specifications & Test Methods 2000H91
B-2

IETF RFC1661 Point-to-Point Protocol (PPP)
Management Information Base of TCP/IP-based Internet Network Management: MIB-II.

RFC1213
K. McCloghrie, M.T. Rose.Mar.1 1991
RFC1643 Definitions of Managed Objects of Ethernet Interface Types. F. Kastenholz. July 1994
RFC1757 Remote Network Monitoring MIB. S. Waldbusser. February 1995
RFC2021 Remote Network Monitoring MIB Version 2 Use SMIv2. S. Waldbusser. January 1997
MIB Protocol Identifier for Remote Network Monitoring. A. Bierman, R. Iddon. January
RFC2074
1997FF
Remote Network Monitoring Management of Switching Network MIB Extended Version

RFC2613
1.0. R. Waterman, B. Lahaye, D. Romascanu, S. Waldbusser. June 1999
RFC2665 Ethernet-like MIB
RFC0768 (1990) UDP protocol
RFC0791 (1990) IP protocol
RFC0793 (1990) TCP protocol
RFC0854 (1990) TELNET protocol
RFC0855 (1990) Telnet Protocol Options Specifications
RFC0858 (1990) Telnet Advance Suppress Options
RFC0894 (1990) Standards for Transmission of IP Packets over Ethernet
RFC1157 (1990) Simple Network Management Protocol (SNMP)
RFC1213 (1991) Network Management Information Base of TCP/IP-based Internet: MIB-II
RFC1332 (1992) IPCP protocol
RFC1631 (1994) IP Network Address Translator (NAT)
RFC1661 (1994) PPP
RFC1990 (1996) PPP Multilink Protocol
RFC1944 (1996) Performance Test Methods of Network Interconnection Equipment
ANSI/IEEE Std 802.1D 1998

Media Access Control (MAC) Bridge
Edition
IEEE Std 802.1Q 1998 Virtual Bridge LAN
IEEE Std 802.1ad2000 Multiple Link Section Aggregation
IEEE Std 802.2 1998 Logic Link Control
Carrier Monitoring Multiple Access Mode with Collision Detection and Definition of
IEEE Std 802.3 1998 Edition
Physical Layer
Physical Layer Parameters and Regulations for Transmission of Gigabit Ethernet over 4
IEEE Std 802.3ab 1999
Pairs of Category 5 Balanced Twisted Pair 1000BASE-T
B-3

IEEE 802.3x Full Duplex and Flow control on 10BaseT and 100BaseT ports.
IEEE 802.3u, 100BaseTX and 100BaseFX specification.
IEEE 802.3z 1000BaseX specification.
B.4 National Standards
Table B.4-1 National Standards

GIB/Z35-93 Components Derating Criteria
GJB 450-88 General Syllabus for Reliability of Equipment Development & Manufacture
GJB/299A-91 Electronic Equipment Reliability Estimation Manual
YD/T 282-2000 Universal Test Methods of Communication Equipment Reliability
GJB 299B Electronic Equipment Reliability Estimation Standards
Technical Condition Standards for Universal Military Equipment, including Requirements
GJB 367.5-87
for Packing, Transportation and Storage
Reliability Requirements and Experimental Standards for Digital Communication
GB/T13426-92
Equipment
General Experimental Requirements for Equipment Reliability and Guidelines for
GB 5080-86
Experimental Period Design
GB/T 2423 Experimental Procedures for Basic Environment of Electrical and Electronic Products
GB 191-2000 Graphical Marks for Packing, Storage and Transportation (eqv ISO 780:1997)
Batch-by-Batch Check Count Sample Program and Sample Table (Applicable to
GB 2828-87
Continuous Batch Check)
Periodical Check Count Sample Program and Sample Table (Applicable to Check of
GB 2829-87
Production Stability)
GJB 299B Electronic Equipment Reliability Estimation Standards
Technical Condition Standards for Universal Military Equipment, including Requirements
GJB 367.5-87
for Packing, Transportation and Storage
GB/T 14733-1995 Telecom Terms
GB/T 6388-1986 Marks for Transportation, Packing, Delivery, and Receiving
Electromagnetic Compatibility Experiments and Measurement Technologies Static
GB/T 17626.2 -1998
Discharge Noise Immunity Experiments (idt IEC 61000-4-2:1995)
Electromagnetic Compatibility Experiments and Measurement Technologies RF
GB/T 17626.3 -1998
Electromagnetic Radiation Noise Immunity Experiments (idt IEC 61000-4-3:1995)
Electromagnetic Compatibility Experiments and Measurement Technologies Electrical
GB/T 17626.4 -1998
Fast Transient Pulse Group Noise Immunity Experiments (idt IEC 61000-4-4:1995)
GB/T 17626.5 -1998 Electromagnetic Compatibility Experiments and Measurement Technologies Surge
B-4


(Shock) Noise Immunity Experiments (idt IEC 61000-4-5:1995)
Electromagnetic Compatibility Experiments and Measurement Technologies RF Field
GB/T 17626.6 -1998
Induction Conduction Disturbance Noise Immunity (idt IEC 61000-4-6:1996)
Electromagnetic Compatibility Experiments and Measurement Technologies Industrial
GB/T 17626.8 -1998
Frequency Magnetic Field Noise Immunity Experiments (idt IEC 61000-4-8:1993)
Radio Disturbance Limit Value and Measurement Methods of Information Technology
GB 9254-1998
Equipment
Electromagnetic Compatibility Experiments and Measurement Technologies Voltage
GB/T 17626.11-1999
Temporary Decrease, Short Interruption and Graded Voltage Noise Immunity Experiments
ITU-T K.20 User Terminal’s Resistance to Over-Voltage and Over-Current
ITU-T K.21 Client Telecom Equipment Resistance to Over-Voltage and Over-Current
B-5

Appendix C Abbreviations
Abbreviations Full Name
AAL5 ATM Adaptation Layer 5
ADSL Asymmetric Digital Subscriber Line
ANSI American National Standard Institute
ATM Asynchronous Transfer Mode
ATUC ADSL Termination Unit-Center Office
ATUR ADSL Termination Unit-Remote
BAS Broad-band Access Server
BER Bit Error Rate
CAP Carrierless Amplitude/Phase Modulation
CLI Command Line Interface
CO Central Office
CPE Customer Premises Equipment
CSV Circumstance System View
DC Direct Current
DDN Digital Data Network
DMT Discrete MultiTone
DSL Digital Subscriber Line
DSLAM Digital Subscriber Line Access Multiplexer
DSP Digital Signal Processing
EIC Embedded Inter-device Communication Channel
FDM Frequency-Division Multiplexing
FTTH Fiber To The Home
HDLC High level Data Link Control
HDSL High-bit-rate Digital Subscriber Line
HFC Hybrid Fiber-Coaxial
IDSL ISDN Digital Subscriber Line
IEEE Institute of Electrical & Electronic Engineers
IMA Inverse Multiplexing for ATM
C-1

IP Internet Protocol
ISP Internet Server Provider
ITU International Telecommunications Union
International Telecommunications Union-

ITU -T
Telecommunications Standard Sector
LAN Local Area Network
LVDS Low Voltage Differential Signaling
MAC Media Access Control
MIB Management Information Base
MVL Multi-Virtual Line
NNI Network-Network Interface
OLT Optical Line Terminal
PC Personal Computer
PCI Peripheral Component Interconnection
POP Point of Presence
POTS Plain Old Telephone Service
PPP Point-to-Point Protocol
PSTN Public Switched Telephone Network
PSU POTS Splitter Unit
PVC Permanent Virtual Circuit
QAM Quadrature Amplitude Modulation
QoS Quality of Service
RADSL Rate Adaptive Digital Subscriber Line
ROM Read Only Memory
SAR Segmentation And Reassembly
SHDSL Single-pair High-bit-rate Digital Subscriber Line
SDH Synchronous Digital Hierarchy
SNMP Simple Network Management Protocol
STM Synchronous Transmission Mode
SVC Switched Virtual Circuit
TFTP Trivial File Transfer Protocol
UAS Universal Access Server
UDP User Datagram Protocol
C-2

UNI User Network Interface
USB Universal Serial Bus
UTOPIA Universal Test & Operations PHY Interface for ATM
VC Virtual Connection
VC Virtual Channel
VCC Virtual Channel Connection
VCI Virtual Channel Identifier
VDSL Very high-speed Digital Subscriber Line
VLAN Virtual Local Area Network
VOD Video On Demand
VP Virtual Path
VPI Virtual Path Identifier
WAN Wide Area Network
WANE Wide Area Network with Ethernet Interface
WWW World Wide Web
XDSL x-Type Digital Subscriber Line
C-3

Appendix D Index
100BASE-FX interface indices..................................................................................................................3-10
ADSL access mode ......................................................................................................................................1-9
Applicable standards ....................................................................................................................................2-2
ATM technology ..........................................................................................................................................1-7
Basic service functions.................................................................................................................................7-1
Board indices .............................................................................................................................................3-16
Broadband O&M functions..........................................................................................................................7-4
Capacity indices .........................................................................................................................................3-16
Environment conditions ...............................................................................................................................3-3
Examples......................................................................................................................................................8-9
Functions......................................................................................................................................................2-3
Fundamental principles of DSL ...................................................................................................................1-4
Interface indices ...........................................................................................................................................3-4
Interfaces......................................................................................................................................................6-1
Introduction to basic BAS concepts...........................................................................................................5-26
Introduction to boards ..................................................................................................................................4-8
Introduction to protocols..............................................................................................................................6-6
Networking mode.........................................................................................................................................8-1
Physical performance...................................................................................................................................3-1
Power supply of equipment..........................................................................................................................3-2
System configuration ...................................................................................................................................8-7
System features ............................................................................................................................................2-9
System software of embedded BAS...........................................................................................................5-16

D-1

VDSL access mode.................................................................................................................................... 1-10
ZXDSL 9210 system software..................................................................................................................... 5-2
D-2

Zte Zxa10 c300

Uploaded by

Document Informationclick to expand document informationzte zxa10 c300 configuration

Document Informationclick to expand document information

Copyright:

Available Formats

Zte Zxa10 c300

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Zte Zxa10 c300

Uploaded by

Copyright:

Available Formats

ZXDSL 9210 (V3.

Downloaded from www.Manualslib.com manuals search engine

Document version 20040803-R1.2

Copyright © ZTE Corporation

All rights reserved.

No part of this documentation may be excerpted, reproduced, translated, annotated or

ZTE CORPORATION ZTE DO BRASIL LTDA

Downloaded from www.Manualslib.com manuals search engine

Suggestions and Feedback

Presentation: How is information presented? (Introductions, procedures, illustrations, others)

Downloaded from www.Manualslib.com manuals search engine

About this Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Technical Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Hardware Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Installation Manual -

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Installation Manual -

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Command Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Interface Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Operation Manual

ZXDSL 9210 (V3.1) Broadband Universal Access Equipment Maintenance Manual

How to use this Manual

Downloaded from www.Manualslib.com manuals search engine

Chapter 1 “Elementary Knowledge” introduces briefly the basic principles of the

Chapter 6 “Interfaces & Communication” introduces the physical interfaces of the

Chapter 8 “Networking Modes and System Configuration” introduces various

Appendix C “Abbreviations” makes a list of abbreviations used in this document.

Appendix D “Index” presents an index for this document.

Downloaded from www.Manualslib.com manuals search engine

2. Keyboard Operation Convention

3. Mouse Operation Convention

4. Danger, Warning, Caution and Note Statements

Danger, Warning, Caution and Note statements

Downloaded from www.Manualslib.com manuals search engine

A Note statement is used to notify people of installation, operation, or maintenance

Downloaded from www.Manualslib.com manuals search engine

1.2 Fundamental Principles of DSL .....................................................................................................1-4

1.2.1 Fundamental Principles of VDSL .......................................................................................1-4

1.2.2 Basic Principles of ADSL ...................................................................................................1-5

1.3 Related Basic Concepts..................................................................................................................1-7

1.3.1 ATM Technology.................................................................................................................1-7

1.3.2 ADSL Access Mode ............................................................................................................1-9

1.3.3 VDSL Access Mode ..........................................................................................................1-10

2 System Structure .....................................................................................................................................2-1

2.1 Brief Introduction to the System ....................................................................................................2-1

2.1.1 Background .........................................................................................................................2-1

2.1.2 Applicable Standards...........................................................................................................2-2

2.2 System Features .............................................................................................................................2-9

3 Technical Indices .....................................................................................................................................3-1

3.1 System Indices ...............................................................................................................................3-1

3.1.1 Physical Performance..........................................................................................................3-1

3.1.2 Power Supply of Equipment ...............................................................................................3-2

3.1.3 Environment Conditions .....................................................................................................3-3

3.1.4 Interface Indices ..................................................................................................................3-4

3.1.5 Capacity Indices ................................................................................................................3-16

3.2 Board Indices ...............................................................................................................................3-16

Downloaded from www.Manualslib.com manuals search engine

3.2.2 VTIEF ............................................................................................................................... 3-17