Bezeq Service Implementations with RAD Products Danny Ben Simhon Head of Business Services Planning Dept. Engineering and Network Division

Agenda נושאים Deployed solutions Ethernet over PDH Ethernet over SDH FR emulation over DSL IP VPN and SDH integrated redundant services Products under evaluation FCD-622 G.SHDSL for TDM services Cellular backhauling

Ethernet Direct Service Upgrade existing PDH customers to ETH services Fast deployment Easy to install Over 1000 units deployed Eth RIC E1 PDH Network Termination Access PDH SDH Access PDH PDH Network Termination E1 Eth RIC

Ethernet Direct Service Enhancement RICi-E1 CA Unicenter ADSL Modem for Remote Management 1xE1 over DSL 1xE1 1 ISP / Customer’s HQ XDM / Syncom RICi-E1 4xE1 over PDH SDH STM-1 1xE1 Egate-100 Point-to-multipoint Configuration Manage all components Separates branches by VLAN’s Easy service monitoring Very popular at ISPs RICi-E1 1xE1 STM-1 63

L2 VPN Ethernet Service over SDH SDH CPE for ETH services (VCAT), E1 Voice and Leased Line services over SDH ETH on point-to-multipoint topology HQ up-to 8 remote Sites Voice and ETH over the same fiber DCC Management integration with ECI Up to 8 Branches Branch #1 FCD-155E PABX STM-1 E1 PRI ETH 10/100BT Customer HQ XDM Branch #2 FCD-155E XDM XDM GBE ETH FCD-155E PABX ECI SDH STM-1 E1 PRI 2xSTM-1 STM-1 Ethernet Switch/ Router XDM Up to 8/21E1’s ETH 10/100BT Here we are using an In-band management approach between customer HQ and branches and thus avoiding the need to use more VC-12s for managing the branches in a protected SDH network. A single protected VC-12 is allocated for management at the carrier CO and is connecting between the CO to the customer’s HQ site. At the HQ the management traffic is transported together with the LAN traffic on the same bundle of VC-12s (thus creating a layer 2 customer network). As opposed to the previous slide where we saw that a separate VC-12 is allocated for management, here the management is running In-band together with the LAN traffic. In case there is a need to separate between the management traffic and user LAN traffic (I.e, for security reasons), the separation can be in either of the following methods: GFP-Mux – This methodology enables muxing two VCGs over the same bundle of VC-12s. GFP Mux functionality allowing to Mux together 2 VCGs over the same bundle. The user can define the bandwidth allocated for management in steps of 12.5% (i.e, 12.5% is dedicated for management and 84% for user traffic) and management bandwidth is allocated dynamically and only allocated when management data is being sent (thus, in regular operation the user has 100% of the bandwidth). This method provides a complete separation between management traffic to user traffic but can only be utilized when there are available VCGs (each FCD-155 unit can support up to 4 VCGs). For example, in the above example, this method can not be used since the FCD at the customer;s HQ requires 5 different VCGs and only 4 are available. Port based VLAN – This functionality enables separating user LAN traffic from management traffic according to a separate VLAN identification (based on the data source port in the built-in switch). This function should be used only when there are not enough VCGs to use the GFP-Mux functionality or when the encapsulation method is either LAPS or LAPF. The main limitation is the fact that broadcasts from the management station in the CO will not stop at the management Agent in the FCD-155 which is at customer HQ, and will reach also the customer’s LAN. The third and probably most efficient method is to use standard VLAN tugs (according to 802.1Q) in order to separate between management and LAN traffic. This functionality combines the best of both GFP-Mux and Port based VLAN methods and is guarantying full separation of traffic, dynamic bandwidth allocation between management and LAN traffic, ability to limit the maximum bandwidth used for management (at the expense of user LAN) and also utilize the same VCG as the LAN traffic (and thus enable connectivity of more remote sites). This feature is planed for December this year (part of phase 3). 2 x STM-1 Branch #8 Leased Line for Cellular PABX BTS FCD-155 BSC FCD-155 1 E1 FCD-155 E1’s STM-1 E1’s STM-1 Street Cabinet ETH 10/100BT BTS 8 E1

Integrated PDH & ETH over SDH “Large Scale” Consolidates up to full GbE traffic Fully remote management and monitoring Easy to upgrade from NOC FCD-155 1 STM-1 FCD-155 STM-1 FCD-155 STM-1 8 SDH XDM Bezeq POP STM-1 XDM Bezeq POP HQ EIS FCD-155 FCD-155 1 STM-1 Bezeq POP GbE FCD-155 GbE FCD-155 STM-1 STM-1 GbE RING XDM Bezeq POP FCD-155 STM-1 FCD-155 GbE 8 E1 PBX Over 2000 units installed for major business customers

FR Emulation over ATM Network LA-110 emulates Frame Relay service Directly connected to DSLAM and ATM network FR DLCI to ATM VP/VC inter-working Fully compatible with major FR routers (Cisco, Motorola, Nortel, 3Com, etc.) Fully remote management and monitoring “Future proof”: integrated ETH user port DSLAM LA-110 G.SHDSL FR V.35 STM-1 ATM Network ETH 2-4 copper pairs Over 500 units installed for business customers

Dual Network Solution HQ SDH Network IP VPN Network Branch Branch GbE GbE SDH Network IP VPN Network L3-VPN FCD-155 LA-110 FCD-155 LA-110 FCD-155 LA-110 LA-110 FCD-155 Branch Branch Branch Branch

Agenda Products under evaluation FCD-622 G.SHDSL for TDM services Cellular backhauling

Ethernet over SDH Up to 32 Remote Sites Branch #1 FCD-155 PABX E1 PRI STM-1 XDM ETH 10/100BT Customer HQ Up to 32 Branches Branch #2 ETH 2xGBE (Option) FCD-622 2xSTM-1 XDM FCD-155 PABX E1 PRI ECI SDH STM-1 Ethernet Switch/ Router XDM XDM Up to 8/21E1’s ETH 10/100BT Here we are using an In-band management approach between customer HQ and branches and thus avoiding the need to use more VC-12s for managing the branches in a protected SDH network. A single protected VC-12 is allocated for management at the carrier CO and is connecting between the CO to the customer’s HQ site. At the HQ the management traffic is transported together with the LAN traffic on the same bundle of VC-12s (thus creating a layer 2 customer network). As opposed to the previous slide where we saw that a separate VC-12 is allocated for management, here the management is running In-band together with the LAN traffic. In case there is a need to separate between the management traffic and user LAN traffic (I.e, for security reasons), the separation can be in either of the following methods: GFP-Mux – This methodology enables muxing two VCGs over the same bundle of VC-12s. GFP Mux functionality allowing to Mux together 2 VCGs over the same bundle. The user can define the bandwidth allocated for management in steps of 12.5% (i.e, 12.5% is dedicated for management and 84% for user traffic) and management bandwidth is allocated dynamically and only allocated when management data is being sent (thus, in regular operation the user has 100% of the bandwidth). This method provides a complete separation between management traffic to user traffic but can only be utilized when there are available VCGs (each FCD-155 unit can support up to 4 VCGs). For example, in the above example, this method can not be used since the FCD at the customer;s HQ requires 5 different VCGs and only 4 are available. Port based VLAN – This functionality enables separating user LAN traffic from management traffic according to a separate VLAN identification (based on the data source port in the built-in switch). This function should be used only when there are not enough VCGs to use the GFP-Mux functionality or when the encapsulation method is either LAPS or LAPF. The main limitation is the fact that broadcasts from the management station in the CO will not stop at the management Agent in the FCD-155 which is at customer HQ, and will reach also the customer’s LAN. The third and probably most efficient method is to use standard VLAN tugs (according to 802.1Q) in order to separate between management and LAN traffic. This functionality combines the best of both GFP-Mux and Port based VLAN methods and is guarantying full separation of traffic, dynamic bandwidth allocation between management and LAN traffic, ability to limit the maximum bandwidth used for management (at the expense of user LAN) and also utilize the same VCG as the LAN traffic (and thus enable connectivity of more remote sites). This feature is planed for December this year (part of phase 3). Branch #32 ETH 10/100BT FCD-155 PABX STM-1

Integration of L2 VPN for ETH Direct Service Remote Branch RICi-E1 Enterprise/ ISP Headquarters F.Ethernet 1xE1 Egate-100 Enterprise PSN Ethernet STM-1 SDH Remote Branch 1xE1 GbE RICi-E1 F.Ethernet CO/POP LRS-24 Modem Rack Remote Branch NxE1 ASMi-52/E1 2w/4w ASMi-52/ETH F.Ethernet NMS Headquarters and remote branches: L2 VPN connection – as on the same LAN E1 connections with Egate-100 + RICi-E1, copper access with ASMi-52 Egate is located at enterprise headquarters, managed out-of band All Remote units are End-to-End managed in-band via the Egate Forwards according to VLAN priority Transparent to number of MAC addresses Starting with E1/T1 rate; in the right hand side of the slide we see end users using stand alone RIC-E1/T1 converters. The RIC-E1/T1 with an Integrated IP router enables standard interfacing to service providers IP routers, and enables communicating with the router via Telnet in order to configure the router or diagnostics. When equipped with a 10/100BaseT bridge, the RIC-E1/T1 bridges Fast Ethernet networks supporting VPN settings configured using VLANs. Interfacing to Frame relay services is done using serial interfaces such as V.35. In the CO the ASM-MN-214 rack can hold up to 14 RIC-E1R cards saving the cost of E1 interfaces on the CO/POP router.

Cellular Backhauling: Network TDMoIP Tunneling Cellular Site Cellular C.O. TDMA BTS (196 x E1 or 2 x STM-1/OC-3) E1 TDM Gmux 2G BSC Metro ETH Edge E1 TDM IPmux-24/14 Metro Ethernet GbE GbE GbE GSM BTS 3G RNC Ethernet Ethernet GbE UMTS Node B