Technical Specification
2.Technical requirements
2.1 Service functions
2.1.1 Common requirements
All the equipment must support fast Ethernet and Ethernet LAN protocols. The bidder should specify the protocols the equipment supports.
All the equipment must support VLAN routes and VLAN trunking.
All the equipment must support multicast. Please specify the protocols supported and the amount.
2.1.2 Routers
Routers must support various encapsulation protocols such as PPP, HDLC, X.25, FR, ATM etc.
Please specify if the routers support VPN, and the VPN types and features the routers support.
Router 1 configuration enables access by private lines, etc.
Router 2 configuration enables access by private lines, VoIP and dial-up functions. The VoIP implementation should be further specified.
Router 3 configuration enables access by private lines, dial-up access, VPN, etc. The protocols supported by dial-up access should be specified.
2.1.3 Route switches
Route switches must support GE protocols
Route switches must support VLAN. The bidder should specify the policy for VLAN division.
Route switches must support QoS. The bidder should specify the QoS policy and performance parameters of the equipment.
2.2 Interface requirements
The interfaces provided by the equipment should have good interworking with the existing network equipment.
2.2.1 Router 1
Must support diversified WAN interfaces, such as DDN, ISDN, PSTN, X.25, ATM, Frame Relay, SDH, POS, DS3 (45M). The bidder should specify the bit rates, media types of the above mentioned interfaces. Must support fast Ethernet and Ethernet interfaces. Please specify if bundling of multiple fast Ethernet is supported, the maximum amount, the relevant technologies employed for implementation and compatibility with technologies employed by other manufacturers. Other types of interfaces that the equipment can provide should be listed.
2.2.2 Router 2
Must support diversified WAN interfaces, such as DDN, ISDN, PSTN, X.25, ATM, Frame Relay, etc. Must support fast Ethernet and Ethernet interfaces. Must support VoIP interfaces. Other types of interfaces that the equipment can provide should be listed.
2.2.3 Router 3
Must support diversified WAN interfaces, such as DDN, ISDN, PSTN, X.25, ATM, Frame Relay, etc. Must support fast Ethernet and Ethernet interfaces. Other types of interfaces that the equipment can provide should be listed.
2.2.4 Route switches
2.2.4.1 Fast Ethernet ports
The bidder should specify interface types, optical interface modes, transmission ranges, module configuration, type numbers of the Ethernet and fast Ethernet modules that the equipment supports and the maximum amount of the ports the equipment supports and the ways for implementation. The bidder should specify the amount of MAC addresses that each port supports. The bidder should specify if the bundling of multiple 100M Ethernet is supported and the maximum amount for bundling and the relevant technologies employed for implementation and the compatibility between this technology and technologies used by other manufacturers.
2.2.4.2 GE ports
The bidder should specify interface types, optical interface modes, transmission ranges, module configuration, type numbers of the GE modules that the equipment supports and the maximum amount of the ports the equipment supports and the ways for implementation. The bidder should specify the amount of MAC addresses that each port supports.
The bidder should specify the maximum transmission ranges the GE optical ports support. The backbone and edge switching equipment are required to contain modules with transmission ranges longer than 70km, and other ways for implementation.
The bidder should specify if the bundling of multiple GE is supported and the maximum amount for bundling and the relevant technologies employed for implementation and the compatibility between this technology and technologies used by other manufacturers.
2.2.4.3 The bidder should specify if the interfaces of POS, ATM, etc. are supported, as well as the interface types, optical interface modes, transmission ranges, maximum amount of paths, module configuration, type numbers and the maximum amount of the ports the equipment supports and the ways for implementation.
2.3 Routing protocols
2.3.1 All the equipment must support CIDR
2.3.2 Route 1 must support routing protocols such as RIP, RIP2, OSPF, BGP4, etc. Please specify the performance parameters for route processing (such as routing table length, route processing capability, etc.). Other routers and route switches must support protocols like RIP, RIP2, OSPF, etc. Please specify if Router 2 and Route 3 support NAT protocol. The bidder should specify other routing protocols that the equipment supports.
2.4 Key performance parameters
2.4.1 All the equipment should be stable in performance, ensuring 7X24 proper operation. The bidder should provide the annual fault rate and the MTBF for each board and the complete system.
2.4.2 Route 1 packet forward capability should be greater than 200Kbps. The backboard bandwidth of over 800M should be available.
Router 2 packet forward capability should be greater than 50Kbps,
Router 3 packet forward capability should be greater than 25Kbps.
Route switches should have the backboard bandwidth of over 80G.
The bidder should specify the processing structure, bus structure and the maximum throughput capacity, maximum load (maximum amount of modules and ports accommodated and port rates) of Router 1 and the route switch.
2.4.3 The bidder should specify the following IP packet processing performance criteria for routers: loss rates of IP packet lightly loaded and heavily loaded, IP packet error rate, throughput, IP packet transfer delay, and the specific conditions these criteria are based on (packet length, bandwidth, etc.).
2.4.4 The bidder should describe the maximum utilization rates of various interfaces for Router 1 and the route switches.
2.5 Manageability
2.5.1 All the equipment should provide standard management interfaces, supporting SNMP protocols and management capabilities required by the network management system for management of configuration, fault, performance and security.
2.5.2 Should support router management/security protocols: SNMPv1 & v2 (the latest and stable versions), SNMP MIB II, RMON/RMON II, Telnet Remote Access, Username/Password for Remote Access Security Control, Access Lists (Routing), Ping Commands, Syslog, Event Logging, etc.
2.6 Security
2.6.1 Routers
2.6.1.1 The bidder should specify if the routers provide core software and hardware redundancy for its own. The bidder should specify the redundancy modes and the main-standby switch mode and switch time in case of failure. The bidder should specify if the routers allow hot insertion.
2.6.1.2 The bidder should specify if the routers provide redundancy for junction lines and subscriber lines, and support VRRP (or may be compatible with HSRP, FSRP used in the existing nodes).
2.6.1.3 The bidder should specify the ways for software upgrade, if online upgrade is supported and the interruption of normal communications due to online upgrade.
2.6.2 Switches
2.6.2.1 The equipment must provide core software and hardware redundancy for its own. The bidder should specify the redundant modules the equipment has and the redundancy mode (1:1 or N:1 etc). The bidder should specify main-standby module switch mode and time.
2.6.2.2 The bidder should specify if the equipment modules allow hot insertion and online insertion.
2.6.2.3 The equipment must provide redundancy for junction lines and subscriber lines, and allow compatibility with VRRP (or may be compatible with HSRP, FSRP used in the existing nodes).
2.6.2.4 The bidder should specify the ways for software upgrade, if online upgrade is supported and the interruption of normal communications due to online upgrade.
1.12 Y2K
The equipment supplied by the bidder should meet the following principle requirements for "Y2K solution":
All the functions should work after the year 2000, the date and time will not affect the operation and maintenance of the system;
Should make a sound judgement that the year 2000 is a leap year;
Should meet the ISO8601 standard to represent a year with 4 decimal digits.
1.13 Interoperability
The bidder should specify the capability of interconnection and interworking with routers, LAN switches, WAN switches supplied by other manufacturers. The interworking with the existing equipment in the network is a must.
1.14 The bidder should specify the AC/DC power supplies, voltage range, power plug types, power consumption and grounding protection, etc for equipment running.
1.15 The bidder should specify the environment requirements for equipment running, including temperature, humidity and dust-proof, etc.
VI. Package 5- IDC customer support network equipment
1. Introduction
1.1 System description
To meet the requirements for an information society in 21st century, a comprehensive study on information sources, optical cable networks, information processing and transmission, user access means, etc. is necessary. The rapid development of information technology, especially the unexpected development in the field of information processing and transmission, calls for sophisticated, practical and feasible technical solutions. The functions and services delivered to the customers should be part of a long-term plan and implemented step by step in phases.
Integrated information networks should meet the requirements for both traditional leased line services and various IP-based services. Network bearer capabilities, data transport, user access, etc. are key considerations while deploying networks.
1.2 General requirements
1.2.1 Support of network scale
The equipment supplied by the manufacturer should enable deployment of large-scale networks and meet the requirements in terms of capacity, network management capabilities, connectivity, the amount of virtual connections supported, and support of relevant technologies employed for IP-based services.
1.2.2 Standard compatibility
The equipment should conform to the relevant standards (international standards formulated by ITU-T, ATM Forum, IETF, FR Forum, etc). The bidder should specify the support of international standards by classes. The bidder should specify the technical standards and versions the equipment conforms to. For those that do not conform to the standards, the bidder should give a schedule to indicate when the standards will be supported.
1.3 Equipment configuration
The bidder should specify the proprietary control protocols or management protocols, it there are any.
This bid, in accordance with the technical requirements and service requirements of the Long Distance Communication Business Unit of Shanghai Telecommunication Corporation, requires two multi-service ATM switching nodes and network management systems. Each switching node is equipped with a set of backbone switch (ATM/FR/DDN hybrid device), three sets of edge switches (DDN access devices). The network management system consists of a mainframe for network management and network management software. See the details in Table 1.3 Equipment configuration.
Table 1.3 Equipment configuration
Sequence No. Equipment Interface rates and types Number of interfaces Remarks
ATM/FR/DDN DC, redundancy
hybrid device
Long range
Ultra long range
Channelized FR
Channelized DDN
DDN access device DC, redundancy
Channelized DDN
1.4 Capacity requirements
The capacity of the backbone switch supplied by the bidder should be higher than 5Gbps. The capacity of the edge switch should be specified.
1.5 Equipment reliability
The common modules of the equipment supplied by the bidder, such as control modules, switching modules, and power supply modules should be redundant. The bidder should specify the redundancy of ports and board cards. All the hardware boards allow hot insertion, with no service affected. The bidder should provide the specific data for switching time in case of failure. The bidder should provide complete, advanced and matured system software and hardware. It should be ensured that all the technologies are open, transportable, compatible and scalable.
1.6 Network reliability
The equipment should have self-healing functions, enabling automatic re-routing to restore communication in case of network faults. The bidder should provide the maximum for re-routing by each switching system in a given period of time.
1.7 Principles for Y2K solutions
The equipment supplied by the bidder should meet the following principle requirements for "Y2K solution":
All the functions should work after the year 2000, the date and time will not affect the operation and maintenance of the system;
Should make a sound judgement that the year 2000 is a leap year;
Should meet the ISO8601 standard to represent a year with 4 decimal digits.
1.8 System availability
The bidder should provide the annual availability for stand-alone systems and the MTBF for each board and the complete system.
1.9 Scalability
The bidder should specify the ways for equipment capacity expansion and online upgrade. The bidder should specify the test results for interconnection and interworking of the equipment with the products by other manufacturers.
2. Technical requirements for equipment
*2.1 Interface requirements
The bidder should specify if the following interfaces are supported and the port density in the stand-alone cabinet, and the ways for implementation.
2.1.1 ATM interfaces
The bidder should specify the types, transmission media, transmission rates, and transmission ranges of ATM interfaces for the backbone switch. The bidder should specify if the ATM optical interfaces of the backbone switch are directly connected with optic fibers or via the relevant transmission devices.
2.1.2 FR Interfaces
The bidder should specify the types of FR interface the backbone switch supports: G.703 (channlization and non-channelization), V.35, X.21. The bidder should specify the maximum amount of the FR virtual connections that each port supports. The bidder should specify the maximum rates for the non-channelized FR interfaces. Recommendations G.703 and G.704 should be supported.
2.1.3 Circuit emulation interfaces
The bidder should specify if all the equipment support circuit emulation interfaces.
2.2 Interfaces for other services
The bidder should specify if the interfaces for other services are supported and the port density in the stand-alone cabinet, and the ways for implementation.
2.3 Service functions and requirements
2.3.1 The backbone switch should support functions for bi-directional point-to-point FR/ATM connection (PVC and SVC).
2.3.2 The backbone switch should support symmetric and asymmetric bandwidth allocation on the point-to-point VC connection (PVC and SVC).
2.3.3 The backbone switch should support symmetric and asymmetric bandwidth allocation on the point-to-point VP connection.
2.3.4 The backbone switch should support ATM multicast for point-to-multipoint connection (PVC and SVC).
2.3.5 The backbone switch should support service types of CBR, VBR, ABR and UBR.
2.3.6 The backbone switch should differentiate the real-time services from non-real-time services and ensure the transport priority for the real-time services.
2.3.7 The backbone switch should differentiate the loss-sensitive services from non-loss-sensitive services and ensure the transport quality for the loss-sensitive services.
2.3.8 Please specify if the backbone switch supports MPLS and the ways for implementation.
2.3.9 The bidder should specify the ways for the equipment to implement point-to-multipoint connection.
2.3.10 The bidder should specify the other services functions that can be provided.
*2.4 Signaling, numbering, address formats and addressing modes
2.4.1 The bidder should specify the UNI and NNI signaling standards that the equipment supplied supports.
The equipment should allow setup of point-to-point and point-to-multipoint connection via relevant signaling, and have enhanced routing functions, such as dynamic alternating routes, load sharing for standby routes, etc.
2.5 Traffic management
2.5.1 The bidder should specify the technologies employed for congestion control.
2.5.3 The backbone switch should provide the prioritized FR services and ensure the QoS of all the services. The implementation mechanism for FR QoS should be specified.
2.5.3.1 Connection admission control (CAC)
The bidder should specify which CAC algorithm is supported;
The bidder should specify if over-subscription is supported.
2.5.3.2 User parameter control (UPC) and network parameter control (NPC)
The bidder should specify the ways to implement UPC/NPC and if UPC functions is available to each virtual connection.
2.5.3.3 Network resource management
Network resource management is for control of network resource allocation. The bidder should specify how to implement network resource management.
2.5.3.4 Priority control
*2.5.3.5 Traffic shaping
2.5.4 The bidder should specify the implementation mechanism and assurance mechanism for ATM QoS.
2.5.5 Please specify how the backbone switch ensures the consistency of FR QoS and ATM QoS for FR/ATM service interworking.
2.5.6 The equipment should provide effective buffering function. The bidder should specify the cell-buffering scheme, location, scheduling algorithm and buffering size, etc for the equipment.
2.6 OAM functions
The equipment should have at least the following functions. The bidder should specify the ways to implement all the functions.
(1) Performance supervision
(2) Defect and fault supervision
(3) System protection
(4) Fault and performance information
(5) Fault location
2.7 Network management and billing requirements
2.7.1 Introduction
2.7.1.1 The bidder should specify the network management protocols the equipment adopts and supports.
2.7.1.2 The bidder should ensure the network management software can be upgraded and the different versions are compatible with each other.
2.7.1.3 Transmission of network management information allows in-band and out-of-band transmission.
2.7.1.4 The bidder should specify the software and hardware configuration for the network management.
2.7.1.5 The bidder should specify the part of network bandwidth resources used by in-band network management information.
2.7.1.6 The bidder should specify the network management system architecture and if any WEB-based technologies are available.
2.7.1.7 The bidder should specify the workflow of the network management system.
2.7.1.8 The bidder should specify the maximum amount of the manageable nodes by the network management system.
2.7.1.9 Please specify if the GUI-based management interfaces are available to the network management system.
2.7.1.10 The network management system should meet all the principle requirements for Y2K solution specified in Article 1.7.
2.7.2 Network management functions
Network management should include the following functions:
Configuration management
Performance management
Security management
Fault management
2.7.3 Configuration management
Configuration management includes network resource configuration and service configuration. The bidder should specify all the configuration functions.
2.7.4 Performance management
Performance management:
2.7.4.1 Collection of performance information
(1) The network management center should record the following information in phases or in a real-time mode and modify them as the networks change;
a. Information on network user, including the relevant information about the number of users and distribution, characteristics of user services, etc;
b. Information on network nodes and junction line resources, including the numbers of ports (used or unused), the use of bandwidth, the use of junction lines, etc;
c. Make records, statistics and reports on network resource utilization and generate performance management logs.
(2) The network management center should be able to collect performance data about network operation, including at least the following:
a. The amount of VP/VC connection in current use
b. For each port, the following data about VPC/VCC:
Amount of cells transported
Amount of cells received or transited
Amount of discarded cells as being out of the parameter range committed by UPC/NPC
Amount of cells transported though being out of the parameter range committed by UPC/NPC
Cell error rate
Discard cell rate, including lost cells due to header errors
Duration for severe congestion
Duration for moderate congestion
Duration for slight congestion
Times for congestion alarming
(3) The network should collect, store and display the above-mentioned data and generate historical data in a given period of time. Reports can be generated based on the collected data while printing and network analysis are allowed.
For information collected in phases, the network management center should be able to set the intervals for information collection.
2.7.4.2 Alarming and filtering
(1) The network management center should enable threshold setup for congestion supervision and alarming;
(2) The network management center should enable network supervision. For those nodes with network congestion, equipment faults or the performance degraded to the thresholds, graphic display is possible.
2.7.4.3 Statistic reports
The network management system should provide graphic reports for historical data about network performance, such as network utilization, as the basis for the network optimization and planning.
2.7.5 Security management
The network management system should enable assignment of user identifier, password, access control grade and scope. Configuration and modification of the passwords for network node access are possible. It also has security management functions to verify the users' rights, block unauthorized access, record all the login process and operation process, provide security logs, provide timeout management, security cancellation, etc.
2.7.6 Fault management
The bidder should specify what is for fault management and the ways for implementation.
2.8 Synchronization requirements
2.8.1 The equipment should enable searching for clocks from external timing systems and line signals simultaneously. When the external clock is lost, the network will activate its own clock and switch back automatically after the normal conditions of external clocks detected.
2.8.2 The bidder should provide the recommended external timing system
2.8.3 The bidder should specify the characteristics of the internal clocks for the equipment.
2.9 Equipment performance requirements
The bidder should provide the specific values and satisfaction for the following performance parameters:
1. Non-blocking switching capability of the equipment
2. Modular structure for switching adopted should be specified
3. Call handling capability of the equipment (calculation methods for call handling capability should be provided)
4. Cell loss rate of the equipment
5. Cell error rate of the equipment
6. Cell transfer delay and cell delay variation
7. Call setup time and disconnection time
8. Domain in which equipment VPI/VCI can be used
9. Size, location and allocation of cell buffering areas
10. NIC ports support self-defined service features (e.g. UNI, NNI, etc.)
11. Amount of virtual connection simultaneously supported by ports/cards
12. Amount of virtual connection simultaneously supported by the complete system
2.10 Requirements for temperature, humidity and power supplies
The temperature range for proper operation of the equipment: 5oC-40oC
The relative humidity range for proper operation of the equipment: 20%-80%
The equipment will work properly in the range of -40V—57V or 205V-235V. The power supply module of the equipment should have complete main-standby and switching functions.
2.11 Software structure
2.11.1 Software requirements
The software design should be of layered modules. The communication between modules should take the interfaces specified by international standards. The maintenance and upgrade of each software module will not affect other software modules.
The software supplied by the bidder should be complete and allow online upgrade. The interruption caused by software upgrade will be no longer than 5 seconds. The network management can specify the time for upgrade. If the upgrade is not successful, the system should enable switching back to the previous version of software for continued operation.
All the software must be original and the bidder should have the copyrights or the authorized certificates awarded by the copyright dealers.
2.11.2 Hardware requirements
The racks of the equipment supplies should adopt the structure that meets both the international standards and buyer's requirements. The bidder should provide the maximum capacity of the equipment and the maximum amount of the equipment supervised by the network management system and the total capacity for easy capacity expansion at the buyer's side.
The bidder should provide the equipment electromagnetic field intensity of outgoing radiation and electromagnetic compatibility to bear external electromagnetic interference.
VII. Package 6- Equipment in IDC service management system
1. System introduction
1.1 Project outline
In this stage of the network management project, a centralized NOC will be deployed at the newly built IDC in Pudong. Among other IDCs, there will be one selected for a sub-NOC. The centralized NOC will perform global control for unified management and support. The sub-NOC is in charge of the network management for co-located sub-IDCs and works together with the centralized NOC. The bidder should examine the situation with the characteristics and current status of Shanghai Telecom and presents more practical deployment proposals.
1.2 System configuration
The network management system consists of a set of network management software, network management hardware platform and the expansion of the existing systems. The additional components for reconfiguration should be fully compatible with the existing equipment. See Table 1.2-1 for the specific configuration for expansion of the billing part of the existing systems.
Table 1.2-1 Equipment as expansion of the existing systems
Sequence No. Equipment Quantity Remarks
Mainframe mainframe dual redundancy, with disc array
Workstation mainframe
Mainframe
Mainframe
Database software a set of dual HA and a stand-alone HA
Mainframe
2 Key requirements for IDC network management system
The network management system for Shanghai Telecom's IDC should meet the following key requirements:
2.1 RAS (reliability, availability and scalability) assurance
The products recommended by the bidder should be matured open products, meeting the industry standards in terms of quality. The bidder should, in its scheme, describe successful cases in IDC deployment home and abroad.
The network management system is required to enable creation of reliability rules as design guidance for equipment redundancy plan in configuration management and other relevant functions. They are mainly:
Definition of RAS objectives for the entire network. For instance, in configuration management, it is possible to define network's alarming frequency in a given period of time and the control targets of alarming duration in a quantitative way.
Definition of service availability objectives. For instance, in configuration management, it is possible to define network's alarming frequency in a given period of time and the control targets of alarming duration in a quantitative way.
RAS assessment. Examine the reports on network reliability, availability and scalability, and make comparisons with the defined RAS objectives.
The network management scheme submitted by the bidder should provide the performance criteria required by operation and maintenance, with relevant analysis. The network management system should enable effective management and supervision for the equipment in the existing network, and support the equipment by leading manufacturers (like Cisco, Juniper, Lucent, Nortel, Foundry, etc.). The network management system should be effectively connected with the existing network management system.
2.2 Network configuration management
It enables automatic detection of network topology and network configuration, real-time supervision of operation status of the network and equipment. It also allows records and statistics for network node equipment, ports and configuration process. The network configuration management should perform the management of in-network resources, such as resources of bandwidth and IP address, etc.
2.3 Performance management
The network management system can continually collect the relevant data about network operation in a real-time manner, provide statistics of network and equipment performance, and display the levels of network events in a graphic way. The commands will be sent to all the nodes (equipment) for network control, if necessary.
The network management system can collect and process traffic data, listed below, on network nodes and generate daily or monthly reports for network operation analysis.
Utilization and availability of node equipment and various ports
Utilization of CPU, hard disk and RAM
Statistics of network traffic and various traffic
Statistics of network delay
Duration of slight, moderate and severe congestion
Times of congestion alarming
Times and duration of equipment fault
Times of severe alarming and slight alarming
Examine the trend relationships between network and equipment availability and performance in different service models, work out a proper arrangement for network load, as a decision-making basis for the further capacity expansion planning.
2.4 Fault management
The network management system should enable real-time collection of fault supervision information in the network, process them promptly and store them effectively. The relative severe alarming will be displayed and the network equipment under control as required. That is to say, the network platform for fault management should instantly display network fault information with sound and light.
The network management system can generate statistic reports on the alarm creation, specific information and clearance of the alarms for network nodes and junction lines. The function set of fault management enables detection, isolation and correction of faults in the network or the environment. Fault management includes the following function sets: RAS (reliability, availability, scalability) assurance; alarming supervision; fault location; fault correction; fault management.
Fault management sends the fault reports that the customer generates or the fault spot by the fault detection, provide operations for fault analysis and clearance and detect the status of fault clearance process and services. Fault management provides the following functions:
Fault report rules. Provide confirmation and testing rules and rules for report distribution to the corresponding management modules.
Fault reports. Receive fault reports from customers and determine if it is a new fault and write the reports into the database.
Fault status change announcement. Send announcement to the customers in case of fault status change.
Fault information inquiry. Check fault status and inquire fault history and fault report formats.
Fault slip management. Provide access to fault reports and fault slips. They can be generated by customers or in the network, or the abnormal conditions detected by alarm analysis and performance supervision. Follow-up reports come from the processes of fault correction and fault report and slip clearance.
Fault effects. Information about physical faults can be combined with IDC service management. It can provide individual windows for fault management to IDC customers.
Fault processing capability. Automatic classification of faults, fault compression and relevant processing are possible. At least 200 pieces of fault information can be processed per second.
2.5 Security management
Security management may block unauthorized access to the network management system and control the access levels and domains for various users. The network management system can configure users' identifiers and passwords, record operation commands by operators and assign management rights for the administrators.
Network management is performed in a manner of rights separation. It provides security management mechanism for fixed console and Web pages (respectively for internal and external users).
2.6 Internet services
The products recommended should enable effective supervision over the following 18 key Internet services, including SNMP, Transx, DHCP, Dial, NTP, RPING, DNS, FTP, HTTP, HTTPS, IMAP4, LDAP, NNTP, PING/ICMP, POP3, PORT, RADIUS and SMTP.
2.7 SLA management
Provide various IDC customers diversified SLA service reports with Web interfaces. With the relevant service parameter supervision and reports while providing different SLA services to customers, e.g. provide customers data traffic, use of bandwidth and system resources, Internet services, firewall log processing, together with analysis of fault logs, find the roots of causes. System administrators are allowed to create SLA reports to ensure quality of customer services.
It also provides interfaces with the leading databases by Oracle, Sybase, Informix, etc.
2.8 Network management system hardware platform
The operating system is a standard Unix platform, supporting multithreaded kernel.
3. Engineering implementation and others
3.1 Requirements for system integration
(1) The bidder should complete system integration, implement the scheme it proposes and complete the installation and commissioning of all the equipment and software involved in the scheme. The bidder should be responsible for the interworking between the equipment integrated, and work with the buyer to ensure interworking with other equipment and a full availability of all the functions specified in the scheme.
(2) The bidder should provide its credit conditions, including business size, capital, technical strength, credit certificate by banks and capital sponsorship.
(3) Project management capability
The project management capability is a key factor for the project implementation. Therefore, the bidder is required to enjoy a wealth of project management experiences for large or complicated computer systems in the telecom sector to ensure the smooth implementation of the whole project.
(4) Experiences of system integration
The bidder should have the experiences of seamless system integration for the equipment specified in the scheme recommended and the existing equipment at the buyer's side. Typical cases should be given.
3.2 Technical service requirements
(1) In accordance with the types and uses of the software and hardware the bidder should integrate and the buyer's requirements, the bidder should provide the buyer comprehensive, effective and prompt technical support and services. The bidder should specify the scope and extent for technical guidance and technical support.
(2) The bidder should provide the engineering design materials required by equipment installation and debugging. The bidder should provide technical services, including technical consulting, to ensure security and quality.
(3) During the system installation, the buyer has the rights to send technical people to the sites. The bidder has the obligations to give instructions.
(4) The bidder should send the installation and debugging materials separately to the sites in advance, as required by the contract.
(5) The system should be ease of installation and use, allowing integration with the existing network management system.
(6) The bidder should provide prompt technical support for the equipment that the buyer puts into operation. When the equipment fails, the bidder should provide the following technical services promptly, i.e. the bidder should provide telephone services within half an hour, on-site support by dispatched technicians within 2 hours, restoration from failure within 4 hours.
3.3 Factory check for equipment
The bidder should supply the detailed steps of factory check for the equipment to be integrated.
3.4 Training
The bidder should provide specific proposals and schedules for training in accordance with this project. The requirements are:
Technical training is of two types: advanced training (for high-level professionals or managers) and maintenance and operation training. The bidder should propose the courses, place and hours for training and list the costs for each course. The details (like persons to be trained) will be determined during the technical or engineering negotiations.
3.5 System acceptance
(1) Test for verification can be performed after the equipment installation and debugging meet the criteria specified by this technical specification and services launched. The bidder should submit the verification specification (including items, criteria, modes and instrument, etc) to the buyer one month ahead. The buyer can make modifications in accordance with the contract, technical specification and relevant specifications by China Telecom. After confirmation by both parties, verification documents are generated as basis for verification. After going through the test for cut-over verification, both parties will sign the verification agreement and the equipment will work in the network for a trial operation.
(2) When the equipment, through the trial operation, meets all the performance criteria specified by the technical specification, the final verification can be performed.
(3) Warranty
The time period of one year after the final verification is the warranty term, during which the bidder should warrant all the equipment except consumables. During the period, if the system fails, the bidder should find out the reasons and accomplish troubleshooting until the performance criteria specified by the final verification are met, or the materials or software with defect should be partially or totally replaced. All these should be free of charge.
3.6 Others
(1) The bidder should make commitment that when the system capacity is expanded, the costs for products of the same kinds should be no higher than those actual costs for this contract.
(2) The bidder should ensure the feasibility of its technical proposals. The application software and hardware equipment should be complete for proper operation. If there are any software or hardware supplied by the bidder that could not meet the requirements or the system functions could not be performed or not performed completely due to the insufficient technical support and services provided by the bidder, the bidder should be liable for all these.
(3) The bidder should make compensations for the losses incurred through project delay caused by the bidder.
(4) The bidder should ensure that the equipment (software and hardware) of the same kinds provided in different periods of time should be compatible.
(5) The bidder should ensure a complete Y2K solution for this project
VIII. Package 7- IDC private line equipment
1. Introduction
1.1 The supplier should have the ability to design and manufacture ATM or IP switches, and the experiences (with proofs) for successful operation of the systems similar to those involved in this project. The bidder should provide valid qualification certificate (including ISO9000 series quality assurance certificates), and briefly reviews the sales results related to this kind of equipment.
*1.2 The IDC private line equipment involved in this bid is an expansion of the existing private line system. The equipment supplied by the bidder, as the additional components for reconfiguration, should be compatible with the existing equipment in the systems.
2. Equipment configuration
See Table 1 for the specific equipment configuration
Table 1
Sequence No. Equipment Quantity
Core switch
Switching matrix
Software
Single mode, medium range
Multi-mode, medium range
Single mode, medium range
Edge switch
Multi-mode
DC power supply (redundancy)
3. System description
3.1 Network service classes
3.1.1 Broadband connection-oriented bearer services
Broadband connection-oriented bearer services mainly include the following sub-classes
Services with fixed bandwidth
Services with real-time variable bandwidth
Services with non-real-time variable bandwidth
Others: support CBR, rt-VBR, nrt-VBR, UBR services specified by ATM Forum, and support ABR services that conforms to ATM TM 4.0, and provide UBR+ service
(UBR+=UBR+MCR, simple, but the throughput for UBR connection assured).
3.2 Requirements for system functions
The switch supplied for this bid is the node equipment for broadband data networks in this project. Its system functions should include two parts of lower network functions and service functions.
3.2.1 Lower network functions
3.2.1.1 Service adaptation functions
Complete adaptation to multi-services of voice, data, video, etc. provided. ATM interfaces support the relevant specifications by ITU-T Recommendations I.362, I.363.1, I.363.4, I.363.5, I.366.1, I.366.2, and FR-SSCF functions conforming to ITU Recommendation I.365.1.
3.2.1.2 Connection and control functions
The equipment should support point-to-point and point-to-multipoint permanent virtual connection (PVC) and switched virtual connection (SVC).
The control functions should include three parts of addressing, call connection handling and signaling. Call connection handling functions consist of two parts of decoding and routing handling. Decoding functions are used for switched virtual connection (SVC), while routing handling functions are used for switched virtual connection (SVC), as well as permanent virtual connection (PVC).
The bidder should specify the methods for the control systems of the equipment to complete networking routing, alternate protection, SVC handling, etc. and the maximum amount of the SVC set up by the system in a given period of time.
3.2.1.3 QoS grade functions
The equipment supplied by the bidder should provide a number of QoS grades to ensure that different services can enjoy their corresponding QoS grades. The assignment of QoS grades should be done separately in accordance of the specific user ports or service types. The bidder should specify the implementation mechanism and assurance mechanism for QoS.
3.2.1.4 Traffic control and congestion control functions
The equipment supplied by the bidder should adopt two technologies of traffic control and congestion control simultaneously to avoid or alleviate network congestion. In addition, for proper and effective use of the networks, the equipment supplied by the bidder should provide functions like network resource management (NRM), priority control (PC), traffic shaping, fast resource management and packet discard, etc, for traffic control and congestion control.
And the traffic management should enable two modes of user/network parameter control (UPC/NPC) and connection admission control (CAC). The bidder should specify the CAC algorithm and the parameters used and if UPC functions are available to each virtual connection. The bidder should specify the specific implementation mechanism of the control system for its closed ring.
3.2.2 Service functions
Please specify if the equipment supports circuit emulation services, IP-based services bearer functions and FR service interworking functions. The interworking of the equipment supplied by the bidder and FR should conform to the requirements by the relevant ITU-T Recommendations.
3.3 Requirements for equipment capacity
The capacity of the edge switch supplied by the bidder should be higher than 1G; the capacity of the backbone switch should be higher than 20G.
3.4 Equipment reliability
The equipment supplied by the bidder should have the security measurement by redundancy and fault tolerance, etc. The common modules of the system, such as control modules, switching modules, and power supply modules should be redundant. The equipment should be maintainable. All the hardware boards allow hot insertion, with no service affected. The parts that fail in a switch can be isolated from other parts.
3.5 Network reliability
The equipment should have self-healing functions, enabling automatic re-routing to restore communication in case of network faults. The bidder should provide the maximum for re-routing by each system in a given period of time.
3.6 The requirements for interconnection and interworking
The bidder should have consistency and interoperability tests in accordance with the relevant ITU-T Recommendations and provide the relevant testing reports.
The bidder should specify the interconnection and interworking with the products by other manufacturers.
3.7 Requirements for equipment scalability
The bidder should specify the capacity expansion scheme for the equipment and the ways for upgrade and implement.
3.8 Statement of proprietary protocols
The bidder should specify, if there are any, the proprietary control protocols or management protocols.
3.9 Other requirements for the equipment
3.10 Power supplies
The power supply for the equipment should be DC (-48V).
The bidder should specify the power consumption for each station and equipment and the total power consumption.
3.11 Environment conditions
The bidder should specify the environment in which the equipment will work, including temperature, humidity and dust-proof, etc.
4. Technical criteria and requirements for equipment
4.1 Interfaces
The core equipment should provide ATM interfaces at 155M and 622M. The edge equipment should provide ATM interfaces at 155M and 34M, and FR interfaces at 2M.
4.2 The bidder should specify the non-blocking switching capability of the equipment supplied and the switching module architecture adopted and the maximum load.
4.3 Signaling requirements
4.3.1 Signaling support
The bidder should specify the signaling protocols supported and to what extent.
4.3.2 Signaling functions
The equipment supplied by the bidder should enable point-to-point and point-to-multipoint connection through relevant signaling protocols and have enhanced routing functions, such as dynamic alternating route, standby route load sharing, etc.
4.4 Equipment reliability requirements
The annual fault rate for the equipment <0.001&. The bidder should specify the MTBF for each board and the complete system.
4.5 Network management system
The bidder should specify the network management functions.
- 作者： zhangliping 访问统计： 2005年02月11日, 星期五 07:59 加入博采
你可以使用这个链接引用该篇文章 http://publishblog.blogchina.com/blog/tb.b?diaryID=701130