You are on page 1of 11

Daisy chaining

Daisy chaining for Flexi Zone Micro and Pico
• Raija Lilius
• 01-11-2015

1 © Nokia Solutions and Networks 2015
Nokia Internal Use

Daisy Chaining Introduction Internal Ethernet switch WAN or FZC FZP. Optional integrated Wi-Fi traffic can be chained as well . Chained FZP / FZM can be connected to the backhaul (WAN) or to Flexi Zone Controller using Z1 interface . Chained traffic can be also from a non-LTE device – for example Flexi Zone WCDMA Pico or Wi-Fi AP 2 .3G FZP / FZM FZP / FZM • Flexi Zone Micro (FZM) and Pico (FZP) for LTE can take traffic from the available Ethernet interface and aggregate towards backhaul . support is coming in WCDMAFZ17 © Nokia Solutions and Networks 2015 Nokia Internal Use . Flexi Zone WCDMA Pico does not support chaining.

FZM with one electrical and one optical interface with different SFP alternatives 2.Daisy Chaining with Flexi Zone Micro (FZM) • Flexi Zone Micro comes in two transport versions 1. SynchE or GNSS can be used for the root node. FZM with one electrical and two optical SFP interfaces (TDD LTE version) • Practical maximum number of chained nodes is limited by the expected traffic • The maximum chained backhaul throughput has been verified at 750Mbps measured at the root node (UL and DL) -. Rate-limiting is recommended and explained here • 1588v2. GNSS and 1588v2 frequency for chained nodes GNSS GNSS Flexi Zone Micro Wi-Fi (optional) 1000Base-T Optical Separate AC power required for the chained FZM 3 © Nokia Solutions and Networks 2015 Nokia Internal Use .

Daisy Chaining with Flexi Zone Pico (FZP) • Flexi Zone Pico has two electrical Ethernet interfaces • Practical maximum number of chained nodes is limited by the expected traffic • The maximum chained backhaul throughput has been verified at 750Mbps measured at the root node (UL and DL) . GNSS and 1588v2 for frequency synchronization for chained nodes Flexi Zone Pico 1000Base-T Wi-Fi 1000Base-T (optional) with PoE++ PoE injector or separate AC power required for the chained FZP 4 © Nokia Solutions and Networks 2015 Nokia Internal Use . SynchE or GNSS can be used for the root node. Rate-limiting/shaping and policing is recommended and explained here • 1588v2.

Synchronization support (RL15A) WAN or FZC PoE injector or separate AC power required for the chained FZP • 1588v2 frequency synchronization using unicast mode can be supported up to four hops • Egress limiting for aggregated traffic should be done to make sure that the traffic does not exceed the max backhaul capacity of the root node • 1588v2 phase synchronization (in multicast or unicast mode) is not supported in chained configuration . GNSS is needed for providing synchronization for chained configuration 5 © Nokia Solutions and Networks 2015 Nokia Internal Use . 1588v2 phase synchronization is needed for TDD LTE and LTE Advanced features for FDD LTE .

Daisy Chaining Example Root node 1 2 3 4 Total WCDMA 42 LTE 170 Mbps LTE 170 Mbps 742 Mbps Mbps Wi-Fi 180 Mbps Wi-Fi 180 Mbps LTE 170 Mbps LTE 170 Mbps LTE 170 Mbps LTE 170 Mbps 680 Mbps 6 © Nokia Solutions and Networks 2015 Nokia Internal Use .

SSH Tunnel management & Wi-Fi can also be SGW carried over control IPSec tunnelGNSS GNSS Security GW CA 1 GE Wi-Fi GW PoE injector or separate AC power required for the chained FZP Internet 7 © Nokia Solutions and Networks 2015 Nokia Internal Use .Daisy Chaining with Flexi Zone Pico with LTE and Wi-Fi Traffic LTE and Wi-Fi IPsec/TLS Tunnel management Example LTE traffic is carried in separate IPSec Tunnel user and control GMC tunnels and Wi-Fi configured GRE Tunnel user MME separately.

The total traffic is divided between chained nodes and a node needs to limit its traffic not to exceed ~750 Mbps at the root node .Ethernet Switching Functionality in RL70/55 Rate limiting for traffic originating from FZM/FZP (RL70/55) Non LTE traffic Root node • Integrated Ethernet switch supports Basic Ethernet switching without QoS • In case expected throughput is close to 750 Mbps. Overflow traffic may be dropped . rate-limiting is recommended . In case traffic towards the chain is likely to exceed 750 Mbps. the DL traffic need to be rate limited in 8 the backhaul equipment © Nokia Solutions and Networks 2015 Nokia Internal Use . Total traffic including integrated Wi-Fi and non-LTE traffic should be calculated as part of the total traffic .

Ethernet Switching Functionality Improvements in RL15A /16 • LTE649 – QoS Aware Ethernet Switching is brought in two phases Root node Non LTE traffic Ingress Rate limiting Egress rate limiting for aggregated traffic Egress Scheduling Ingress Rate limiting Egress rate limiting of VLAN aware switching aggregated traffic RL15A RL16 9 © Nokia Solutions and Networks 2015 <Change information classification in footer> .

Alternative Indoor Backhaul Solution Both LTE and WCDMA Flexi Zone Picos BC/TC Wi- Fi EPC PoE++ Aggregatio n switch Support for high QoS aware PoE power supply Configuration LTE + Wi-Fi switching in for FZP can be supports 1588v2 throughput per aggregation protected time/phase FZP synchronization Throughput QoS Power Synchronization 10 © Nokia Solutions and Networks 2015 Nokia Internal Use .