´³ó ²ÜÐ-Ç í»ñ³µ»ñÛ³É ·ÝÙ³Ý
÷³ëï³ÃÕûñ
20 ÑáõÉÇëÇ, 2011
гí»Éí³Í 3/Annex 3
1.1. Modules Specification
1.1.1.
TCP optimization
The solution should provide mobile optimized TCP behavior towards devices on the
radio access network, and standard TCP/IP behavior towards the internet. The bidder shall
specify the impact of the major effects of the solution.
1.1.2.
Clientless
The solution should not require any additional software to be installed in the client
device.
1.1.3.
Protocol Independent
The solution should accelerate TCP connections regardless of the application
protocol or TCP port number.
1.1.4.
Non TCP transparency
The solution should be able to transparently handle all IP protocols, not just TCP by
passing them transparently.
1.1.5.
Selective Optimization
The solution should allow fine-grained configuration of which TCP connections
should be accelerated/not accelerated based on connection properties such as (but not
limited to) destination port or source network.
1.1.6.
Layer 3 IP integration
The solution should integrate into the packet network using standard Ethernet / IP
protocols. The solution should be capable of acting as a Layer 3 router with a minimum of
1
´³ó ²ÜÐ-Ç í»ñ³µ»ñÛ³É ·ÝÙ³Ý
÷³ëï³ÃÕûñ
20 ÑáõÉÇëÇ, 2011
support for Address Resolution Protocol (ARP), and identification of the next hop address
and outgoing interface for each packet based on mobile device IP address range(s).
1.1.7.
Failure detection and re-routing
The solution shall integrate with the standard Bidirectional Forwarding Detection
(BFD) and ICMP ping based failure detection mechanisms of its attached router(s). In the
case where inbound and outbound traffic does not traverse the same physical interface to
the same connected router the system must ensure that a failure detected on one interface
is indicated to the router connected to the other interfaces.
1.1.8.
Performance
Each box must deliver at least 10Gb/s performance of optimized traffic with no less
than 1 million optimized sockets.
1.1.9.
Overload Protection
The solution shall provide overload protection that ensures that traffic is not disturbed
if the system detects it is overloaded. SNMP traps should be generated by the system to
indicate an overload condition. Describe the mechanism for ensuring that traffic is not
disturbed.
1.1.10.
VLAN Tag management
The solution shall provide a mode where packets outgoing on an interface are tagged
with a per interface configurable VLAN tag.
1.1.11.
Data Transparency
The solution shall not change the data content of the TCP/IP traffic traversing the
network.
1.1.12.
Protocol Transparency
The solution shall not change the source or destination IP addresses or TCP
sequence numbering of optimized TCP sessions.
2
´³ó ²ÜÐ-Ç í»ñ³µ»ñÛ³É ·ÝÙ³Ý
÷³ëï³ÃÕûñ
20 ÑáõÉÇëÇ, 2011
1.1.13.
Physical Connectivity
The solution should support at least 4* 1Gb/s or 2* 10Gb/s traffic handling Ethernet
interfaces in addition to one 1Gb/s management interface per box.
1.1.14.
Integration
The solution must integrate with existing NMS systems via SNMP V2c for monitoring
and statistics
1.1.15.
Reporting
Reporting details:


Generate counters for significant internal and external events such as
packets/bytes received and sent. The counters should be viewable from the
system CLI and accessible from SNMP
The report generation system shall be able to give comparative reports on
the performance level of the live optimized and un-optimized traffic, over a
period of at least the last 24 hours.
1.1.16.
Security hierarchy
Multiple security profiles should be supported including as a minimum Read only and
Update account types.
1.1.17.






Technical Requirements
CLI-based operational interface using SSH v1/v2
Fast, easy and secure access to the application
Minimal administration
Operating system: Linux preferred
Required traffic throughput is 1 Gbps
Additional upgrade fees to be quoted separately
1.1.18.
Hardware Footprint
The solution should occupy no more than 2U of rack space per 10Gb/s of optimized
traffic (or 4 U for a fully redundant system).
3
´³ó ²ÜÐ-Ç í»ñ³µ»ñÛ³É ·ÝÙ³Ý
÷³ëï³ÃÕûñ
20 ÑáõÉÇëÇ, 2011
1.1.19.
Hardware Requirements
The solution should specify the minimum and recommended hardware configuration.
The hardware fee should be quoted separately.
The bidder should provide evidence that the proposed hardware will guarantee
performance.
1.1.20.
Training
The solution should include training to the users and administrators. The trainings
should be conducted onsite.
The training should include basic and advanced trainings.
1.1.21.
Manuals and documentation
The solution should include user guides, operation manuals and deployment guides
in electronic format. Printed manuals are optional.
1.1.22.
Project Management
The solution should include project management and professional services to
implement the project.
1.1.23.
Technical support and maintenance
The proposed solution should include the staffing details for normal operations of the
system. In addition to define roles based on best practices and standards.
The solution should include technical support and maintenance with 24x7 hot line
and online ticketing system. The first 3 year technical support will need to be part of the
solution or the commercial proposal.
4