DOCSLIB.ORG

ZXCTN 9004 Product Description

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ZXCTN 9004 Product Description Operator Logo ZXCTN 9004 Product Description ZXCTN 9004 Product Description ZXCTN 9004 Product Description Version Date Author Approved By Remarks R0 2009-08-21 Wang Ning He Ping Not open to the Third Party © 2010 ZTE Corporation. All rights reserved. ZTE CONFIDENTIAL: This document contains proprietary information of ZTE and is not to be disclosed or used without the prior written permission of ZTE. Due to update and improvement of ZTE products and technologies, information in this document is subjected to change without notice. ZTE Confidential Proprietary © 2009 ZTE Corporation. All rights reserved. I Content TABLE OF CONTENTS 1 Overview ..................................................................................................................... 1 2 Highlights .................................................................................................................... 3 3 Functions and Features ............................................................................................. 5 3.1.1 Service processing capability ...................................................................................... 5 3.1.2 Interface type and quantity .......................................................................................... 6 3.2 Multi-service bearing capability.................................................................................... 7 3.2.1 TDM emulation ............................................................................................................ 7 3.2.2 ATM Emulation ............................................................................................................ 7 3.2.3 Ethernet Service .......................................................................................................... 8 3.3 L2 functions.................................................................................................................. 9 3.3.1 Basic Ethernet Features .............................................................................................. 9 3.3.2 VLAN and Expanded VLAN Features ....................................................................... 11 3.3.3 LACP .......................................................................................................................... 14 3.3.4 ACL ............................................................................................................................ 14 3.3.5 STP ............................................................................................................................ 15 3.3.6 L2 Multicast ................................................................................................................ 17 3.4 L3 Functions .............................................................................................................. 18 3.4.1 IPv4 ............................................................................................................................ 18 3.4.2 L3 Multicast ................................................................................................................ 18 3.5 MPLS L2/L3 VPN ....................................................................................................... 20 3.6 QoS ............................................................................................................................ 23 3.6.1 Basic QoS Features ................................................................................................... 23 3.6.2 Ethernet QoS ............................................................................................................. 24 3.6.3 MPLS QoS ................................................................................................................. 24 3.6.4 H-QoS ........................................................................................................................ 25 3.7 OAM ........................................................................................................................... 26 3.7.1 MPLS OAM ................................................................................................................ 26 3.7.2 T-MPLS OAM ............................................................................................................ 26 3.7.3 Ethernet OAM ............................................................................................................ 27 3.7.4 OAM Mapping ............................................................................................................ 27 3.8 Synchronization ......................................................................................................... 27 3.8.1 Clock Synchronization and Protection ....................................................................... 27 3.9 Protection ................................................................................................................... 28 3.9.1 Equipment-level Protection ........................................................................................ 28 3.9.2 Network-level Protection ............................................................................................ 29 3.10 Security ...................................................................................................................... 36 3.10.1 Equipment Security .................................................................................................... 36 3.10.2 Network Security ........................................................................................................ 37 4 System Architecture ................................................................................................ 41 4.1 System Hardware Architecture .................................................................................. 41 4.1.1 Overall Hardware Architecture................................................................................... 41 4.1.2 Working Principles for Hardware System .................................................................. 44 4.2 Introduction to Hardware Modules ............................................................................. 45 4.2.1 Overview .................................................................................................................... 45 4.2.2 MSC ........................................................................................................................... 46 4.2.3 Power Suply Module .................................................................................................. 48 4.2.4 Line Processing Card (LPC) ...................................................................................... 49 4.3 Software Architecture ................................................................................................ 52 4.4 Software Platform ...................................................................................................... 53 II © 2009 ZTE Corporation. All rights reserved. ZTE Confidential Proprietary ZXCTN 9004 Product Description 5 Technical Indexes and Specifications ................................................................... 63 5.1 Physical Indexes ........................................................................................................ 63 5.2 Interface indexes ....................................................................................................... 63 5.3 System Performance Indexes.................................................................................... 64 5.4 System Functions ...................................................................................................... 65 5.4.1 L2 Features ................................................................................................................ 65 5.4.2 L3 Features ................................................................................................................ 66 5.4.3 MPLS Features .......................................................................................................... 67 5.4.4 QoS Features ............................................................................................................ 68 5.4.5 Service Management ................................................................................................. 68 5.4.6 Reliability.................................................................................................................... 69 5.4.7 Clock Synchronization ............................................................................................... 69 5.4.8 Tunnel Features ......................................................................................................... 70 5.4.9 Security Features ....................................................................................................... 70 5.4.10 Operation and Maintenance ...................................................................................... 71 6 Operation and Maintenance .................................................................................... 73 6.1 Network Management Platform ................................................................................. 73 6.2 Maintenance and Management ................................................................................. 73 6.2.1 Monitoring and Maintenance ..................................................................................... 73 6.2.2 Diagnosis and Debugging .......................................................................................... 74 6.2.3 Software
Load more

Recommended publications
  • INTRODUCTION Client
    1 INTRODUCTION Client Server Network Fig. 1-1. A network with two clients and one server. Client machine Server machine Request Network Reply Client process Server process Fig. 1-2. The client-server model involves requests and replies. Fig. 1-3. In a peer-to-peer system there are no fixed clients and servers. 2222222222222222222222222222222222222222222222222222222222222222222222222222222 21 222222222222222222222222222222222222222222222222222222222222222222222222222222Tag1 Full name1 Example 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222B2C1 Business-to-consumer1 Ordering books on-line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222B2B1 Business-to-business1 Car manufacturer ordering tires from supplier 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222G2C1 Government-to-consumer1 Government distributing tax forms electronically 1 1 1 1 1 12222222222222222222222222222222222222222222222222222222222222222222222222222222C2C1 Consumer-to-consumer1 Auctioning second-hand products on line 1 21 222222222222222222222222222222222222222222222222222222222222222222222222222222P2P1 Peer-to-peer1 File sharing 1 Fig. 1-4. Some forms of e-commerce. 22222222222222222222222222222222222222222222222222222222222222 222222222222222222222222222222222222222222222222222222222222221 Wireless1 Mobile1 Applications 1 1 1 1 1 122222222222222222222222222222222222222222222222222222222222222No1 No1 Desktop computers in offices 1 222222222222222222222222222222222222222222222222222222222222221
    [Show full text]
  • Network Reliability and Fault Tolerance
    Network Reliability and Fault Tolerance Muriel Medard´ [email protected] Laboratory for Information and Decision Systems Room 35-212 Massachusetts Institute of Technology 77 Massachusetts Avenue, Cambridge, MA 02139 Steven S. Lumetta [email protected] Coordinated Science Laboratory University of Illinois Urbana-Champaign 1308 W. Main Street, Urbana, IL 61801 1 Introduction The majority of communications applications, from cellular telephone conversations to credit card transactions, assume the availability of a reliable network. At this level, data are expected to tra- verse the network and to arrive intact at their destination. The physical systems that compose a network, on the other hand, are subjected to a wide range of problems, ranging from signal distor- tion to component failures. Similarly, the software that supports the high-level semantic interface 1 often contains unknown bugs and other latent reliability problems. Redundancy underlies all ap- proaches to fault tolerance. Definitive definitions for all concepts and terms related to reliability, and, more broadly, dependability, can be found in [AAC+92]. Designing any system to tolerate faults first requires the selection of a fault model, a set of possible failure scenarios along with an understanding of the frequency, duration, and impact of each scenario. A simple fault model merely lists the set of faults to be considered; inclusion in the set is decided based on a combination of expected frequency, impact on the system, and feasibility or cost of providing protection. Most reliable network designs address the failure of any single component, and some designs tolerate multiple failures. In contrast, few attempt to handle the adversarial conditions that might occur in a terrorist attack, and cataclysmic events are almost never addressed at any scale larger than a city.
    [Show full text]
  • The Role of Emerging Broadband Technologies on the Converged
    The Role of Emerging Broadband Technologies on the Converged Packet-Based Network Introduction The vision of network convergence toward a consolidated packet-based network has been discussed for years, though it is still not a reality. Currently, there are numerous overlay networks such as IP, ATM, FR, Ethernet, SONET, DWDM and wireless for different services. The evolution pace toward convergence has been slow due to economic, technical and regulatory issues. However, the fact is that data traffic volume is now surpassing voice traffic volume. Traditional TDM voice traffic is moving to IP packets and TDM private line is moving to Ethernet private line. The wave of broadband applications such as Internet access, VOD, and IPTV create high bandwidth requirements for the network. These applications are packet-based, but have a much lower margin of profit for the service providers when compared to traditional voice service. Today’s overlay and traditional circuit-based infrastructure will become less optimal for the new packet-based services as the profit margin decreases. Most of the wireless networks in North America today are still circuit-based because most of the current wireless service is still voice-based. However, with emerging wireless access technologies such as WiMAX and Wi-Fi, more broadband wireless data and video services can be deployed. As a result, the wireless core network evolves toward a packet-based network. Service offerings drive network evolution. As more packet-based broadband services are launched and bundled together in service offerings, service providers start to add more packet-aware features into their current network components.
    [Show full text]
  • Congestion Control in Resilient Packet Ring Networks
    New Jersey Institute of Technology Digital Commons @ NJIT Dissertations Electronic Theses and Dissertations Fall 1-31-2005 Congestion control in resilient packet ring networks Alharbi Fahd New Jersey Institute of Technology Follow this and additional works at: https://digitalcommons.njit.edu/dissertations Part of the Electrical and Electronics Commons Recommended Citation Fahd, Alharbi, "Congestion control in resilient packet ring networks" (2005). Dissertations. 670. https://digitalcommons.njit.edu/dissertations/670 This Dissertation is brought to you for free and open access by the Electronic Theses and Dissertations at Digital Commons @ NJIT. It has been accepted for inclusion in Dissertations by an authorized administrator of Digital Commons @ NJIT. For more information, please contact [email protected]. Copyright Warning & Restrictions The copyright law of the United States (Title 17, United States Code) governs the making of photocopies or other reproductions of copyrighted material. Under certain conditions specified in the law, libraries and archives are authorized to furnish a photocopy or other reproduction. One of these specified conditions is that the photocopy or reproduction is not to be “used for any purpose other than private study, scholarship, or research.” If a, user makes a request for, or later uses, a photocopy or reproduction for purposes in excess of “fair use” that user may be liable for copyright infringement, This institution reserves the right to refuse to accept a copying order if, in its judgment, fulfillment
    [Show full text]
  • Getting Physical with Ethernet
    ETHERNET GETTING PHYSICAL STANDARDS • The Importance of Standards • Standards are necessary in almost every business and public service entity. For example, before 1904, fire hose couplings in the United States were not standard, which meant a fire department in one community could not help in another community. The transmission of electric current was not standardized until the end of the nineteenth century, so customers had to choose between Thomas Edison’s direct current (DC) and George Westinghouse’s alternating current (AC). IEEE 802 STANDARD • IEEE 802 is a family of IEEE standards dealing with local area networks and metropolitan area networks. • More specifically, the IEEE 802 standards are restricted to networks carrying variable-size packets. By contrast, in cell relay networks data is transmitted in short, uniformly sized units called cells. Isochronous , where data is transmitted as a steady stream of octets, or groups of octets, at regular time intervals, are also out of the scope of this standard. The number 802 was simply the next free number IEEE could assign,[1] though “802” is sometimes associated with the date the first meeting was held — February 1980. • The IEEE 802 family of standards is maintained by the IEEE 802 LAN/MAN Standards Committee (LMSC). The most widely used standards are for the Ethernet family, Token Ring, Wireless LAN, Bridging and Virtual Bridged LANs. An individual working group provides the focus for each area. Name Description Note IEEE 802.1 Higher Layer LAN Protocols (Bridging) active IEEE 802.2
    [Show full text]
  • IEEE Plenary - Lajolla, CA RPRSG Meeting Minutes July 11-13 2000
    IEEE Plenary - LaJolla, CA RPRSG Meeting Minutes July 11-13 2000 7/11/2000 8:43AM 30 attendees Presentations may be found at: http://www.ieee802.org/rprsg/public/july_plenary/index.html ACTION items in text Motion#1- The RPRSG voting rules amended to require: 1) 75% approval vote for technical issues 2) 50% +1 approval vote for procedural issues Motion: Harry Peng Second:Raj Sharma Yes:20 No:0 Minutes will be approved 8/12/2000 Presentation - Performance Metrics IEEE 802 RPRSG Khaled Amer Discussion - Ring Restoration performance metric will be added Ring performance stability with traffic flow changes Define Ingress/Egress access connection Bit Rate and Traffic characteristics Can Egress rate be below ring rate? Which mechanism? Simulation scenarios should be included ingress=egress traffic ports Change Bit rate to data rate in presentation Define L2/L1 mapping for consistency (mapping delay, etc.) Define L1 data rate - SONET vs. GigE Define L1 model ( packetization delay) metrics Sharing of model source code discussion Presentation - IPR(Intellectual Property Rights) issues Gary Robinson Presentation - Assessment of Scalable Coherent Interface Jason Fan Presentation - Resilient Packet Ring 5 Criteria (Compatibility) BJ Lee Discussion - Ethernet (SNAP encapsulation) and LLC over MAC sublayer correction Page 5- SRP TTL field 8 bits 802.1D compatibility (transparent bridging) and jumbo frame support Compatibility discussion tabled until PAR discussion Decision not to preclude 802.1D bridging Presentation - IEEE 802 Compatibility Considerations
    [Show full text]
  • Cisco Next Generation Routing
    A B NGR Brochure Cisco Next Generation Routing Section 1 Issues for networking in the Broadband Era Section 2 Next Generation WAN Services using MPLS Section 3 Cisco's Next Generation IP Network Solution Section 4 Cisco’s Next Generation Optical Ring Solution Section 5 Service differentiation and Quality of Service Section 6 Service with Security Section 7 Cisco Next Generation Routers – Core and Edge Section 8 Cisco Next Generation Routers – Access W NGR Brochure 12400 series 3700 series 12416 7600 series 12410 7300 series 2600XM/2691 series 10000 series 7609 7613 12406 7304 12404 1700/1760 series 7301 7606 7400 series 7603 10700 series SOHO and 800 series Larg SoH SM e Bra o B / Enterprise nch CPE Cisco Next Generation Routing (NGR) Solution Next Generation Internet in the Broadband Era Broadband networking is rapidly expanding in usage; consequently, routers Innovative Next Generation metro IP solution must support an ever growing range of features and service capabilities to RPR (Resilient Packet Ring), represents a key technology for the meet the unique needs of this high growth area. As the world's leading router deployment of advanced IP ring technology. RPR is used by a large manufacturer, Cisco’s routers are in widespread use, helping to support and number of customers in the metro access arena, for providing an expand the development and usage of the Internet and its rich service base. It advanced, industry-first, IP-based metro Ethernet access solution. This is Cisco's charter to continue this focused development, building upon the ensures an optimum linkage between the router and the Ethernet base, a success of Cisco deployments to date.
    [Show full text]
  • CPE 426 Computer Networks: Term 1-56 Homework 1 Wk 3 Solutions
    ภาคเรียนที่ 1/2556 วิชา CPE426 Computer Networks: HW Wk3; Review 3+TCP/IP Concept 1 ชื่อ______________________________________รหัส_____________________Section________ CPE 426 Computer Networks: Term 1-56 Homework 1 Wk 3 Solutions Review III: LAN Technologies and Chapter 20: TCP/IP Concept ใหนกศั ึกษาแสดงคําตอบโดยเขียนลงในชองว างที่ใหไว สงตนชั่วโมงสัปดาหถัดไป 1. ใหนักศึกษาเขา Web Site ของ IEEE หรือ Search จาก IEEE802 Standard จากนั้นใหหาวามาตรฐาน IEEE802 ตอไปนี้เปน มาตรฐานของอะไร ตอไปนี้เปนขอมูลจาก http://en.wikipedia.org/wiki/IEEE_802 IEEE 802 Working Groups Name Description Note IEEE 802.1 Bridging (networking) and Network Management IEEE 802.2 LLC inactive IEEE 802.3 Ethernet IEEE 802.4 Token bus disbanded IEEE 802.5 Defines the MAC layer for a Token Ring inactive IEEE 802.6 MANs (DQDB) disbanded IEEE 802.7 Broadband LAN using Coaxial Cable disbanded IEEE 802.8 Fiber Optic TAG disbanded IEEE 802.9 Integrated Services LAN (ISLAN or isoEthernet) disbanded IEEE 802.10 Interoperable LAN Security disbanded IEEE 802.11 a/b/g/n Wireless LAN (WLAN) & Mesh (Wi-Fi certification) IEEE 802.12 100BaseVG disbanded IEEE 802.13 Unused[2] IEEE 802.14 Cable modems disbanded IEEE 802.15 Wireless PAN IEEE 802.15.1 Bluetooth certification IEEE 802.15.2 IEEE 802.15 and IEEE 802.11 coexistence IEEE 802.15.3 High-Rate wireless PAN Low-Rate wireless PAN (e.g., ZigBee, WirelessHART, IEEE 802.15.4 MiWi, etc.) IEEE 802.15.5 Mesh networking for WPAN IEEE 802.15.6 Body area network ภาควิชาวิศวกรรมคอมพิวเตอร วิทยาลัยวิศวกรรมศาสตร มหาวิทยาลัยรังสิต ภาคเรียนที่ 1/2556
    [Show full text]
  • Pocket Guideguide Industrial ETHERNET
    Hirschmann Automation and Control GmbH PocketPocket GuideGuide Industrial ETHERNET Hirschmann Competence Center Edition 2006 Copyright © 2006 Hirschmann Automation and Control GmbH All Rights Reserved Permission is not given for the circulation or reproduction of this document, its use or the passing on of its contents unless granted expressly. Contravention renders the perpetrator liable for compensation for damages. All rights reserved, in particular in the case of patent grant or registration of a utility or design. The information/details in this publication merely contain general descriptions or performance factors which, when applied in an actual situation, do not always correspond with the described form, and may be amended by way of the further development of products. The desired performance factors shall only be deemed binding if these are expressly agreed on conclusion of the contract. In 1984 Hirschmann created the first fiber optic ETHERNET network at the University of Stuttgart. In 1990 Hirschmann also invented the ”Redundant ETHERNET Ring“ and finally in 1998 we brought out the HIPER-Ring (Hirsch- mann Performance Redundancy Ring) in switched ETHERNET. Hirschmann is the only manufacturer worldwide offer a universal product range for setting up high-performance, high-availablity industrial networks. From the networking of production lines via the control room using SCADA applications to the enterprise environment - vertical integration - everything from a single source. 1 Contents Contents Page 1 Know-How for the World of
    [Show full text]
  • Ciena Acronyms Guide.Pdf
    The Acronyms Guide edited by Erin Malone Chris Janson 1st edition Publisher Acknowledgement: This is the first edition of this book. Please notify us of any acronyms we may have missed by submitting them via the form at www.ciena.com/acronymsguide. We will be happy to include them in further editions of “The Acronyms Guide”. For additional information on Ciena’s Carrier Ethernet or Optical Communications Certification programs please contact [email protected]. Table of Contents Numerics ..........................1 A .......................................1 B .......................................2 C .......................................3 D .......................................5 E .......................................7 F........................................9 G .....................................10 H .....................................11 I .......................................12 J ......................................14 K .....................................14 L ......................................14 M ....................................15 N .....................................17 O.....................................18 P .....................................20 Q.....................................22 R .....................................22 S......................................23 T .....................................26 U .....................................28 V .....................................29 W ....................................29 X .....................................30 Z......................................30
    [Show full text]
  • Martin Reisslein School of Electrical, Computer, and Energy Engineering Ira A
    Martin Reisslein School of Electrical, Computer, and Energy Engineering Ira A. Fulton Schools of Engineering Arizona State University P.O. Box 875706, Tempe, AZ 85287-5706 Phone: (480)965-8593, Fax: (480)965-8325 [email protected], http://mre.faculty.asu.edu EDUCATION University of Pennsylvania Ph. D. in Systems Engineering, August 1998 Thesis: Managing Prerecorded Traffic in Packet{Switched Networks Advisor: Dr. Keith W. Ross M. S. E. in Electrical Engineering, August 1996 Fachhochschule Dieburg, Germany Diplom{Ingenieur(FH) in Electrical Engineering, 1994 ACADEMIC EXPERIENCE Ira A. Fulton Schools of Engineering, Arizona State University Program Chair, Computer Engineering, January 2018 { present School of Electrical, Computer, and Energy Engineering, Arizona State University Professor, August 2011 { present Department of Electrical Engineering, Arizona State University Associate Professor, August 2005 { August 2011 Department of Electrical Engineering, Arizona State University Assistant Professor, October 2000 { August 2005 German National Research Center for Information Technology (GMD FOKUS) and Technical University Berlin Post{doctoral Researcher and Lecturer, August 1998 { October 2000 PRINCIPAL AREAS of TEACHING AND RESEARCH Teaching • Communication Networks and Multimedia Networking • Electrical Networks and Digital Design Fundamentals • Performance Evaluation of Computer Networks Research • Characterization and Network Transport of Multimedia Traffic Martin Reisslein 2 • Optical-Wireless Access and Metropolitan Area Networks • 5G Wireless Network Systems • Software Defined Networking • Ultra-low Latency Networking • Engineering Education and K-12 Outreach MAJOR AWARDS AND PROFESSIONAL RECOGNITIONS Career Award from United States National Science Foundation, 2002 Best Tutorial Paper Award from IEEE Communications Society, 2008 Elevation to IEEE Fellow, 2014 Friedrich Wilhelm Bessel Research Award from Alexander von Humboldt Foundation, 2015 DRESDEN Senior Fellow, Technical University Dresden, Germany, 2016, 2019 IEEE Transactions on Education Theodore E.
    [Show full text]
  • Chapter 2 Data-Link Layer
    Chapter 2 Data-link layer Problem Statement To transmit data over physical links from one node to another or more nodes effectively and efficiently, there is much more to do than simply modulating bit stream into signal. Transmission impairments, such as crosstalk between two adjacent pairs, can unexpectedly change transmission signal and hence result in errors. The transmitter may transmit faster than the receiver can afford. If there are multiple stations that share common transmission media, an arbitration mechanism is required to determine who can transmit its own data. The transmitter has to somehow indicate the destination, and usually needs to name itself so that the receiver knows where the source is. These problems need to be addressed by a set of functions above the physical layer. In the Open Systems Interconnection (OSI) seven-layer model, a specific layer, named data-link layer, provides the service of controlling data communications over a physical link. This layer provides solutions to the above problems. In addition, upper layers are therefore exempt from the duty of controlling parameters in a physical network. These services greatly alleviate upper-layer protocol design and make it virtually independent of physical transmission characteristics. Throughout this chapter, we intend to equip readers with fundamental background about (1) services and functions provided in the data-link layer, (2) real-world examples of popular data-link protocols, and (3) open source implementation in Linux. Frankly, there are too many real-world examples to choose. Some are legacy or much less popular nowadays. Some are in the mainstream and still some others are under development.
    [Show full text]