RAN2523 BTS Backhaul Over Physically Separated VLAN Interfaces

Slide 1

Network Engineering Info (NEI)Feature Deep Dive RAN2523 BTS Backhaul over Physically Separated VLAN InterfacesMicha MalcherNWS Network Engineeringhttps://sharenet-ims.inside.nokiasiemensnetworks.com/Overview/D438368687 R 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherChange HistoryIssue NumberDate of IssueReason for Update0.130.11.2011Draft version1.008.12.2011Approved version# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherOutlineRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesGeneral IntroductionInterdependenciesTechnical DetailsUser scenarios / Use CasesLicensing and Activation Aspects# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherAgendaHere is an example of what your agenda could look like.

General IntroductionRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherSummaryFeature enables to run Iub/IP over more than one VLAN interface on physically different ports in the BTS. This allows to have either different physical backhaul paths for specific traffic types, or to distribute traffic among them via load distribution.Benefits for the operatorLoad distribution provides the benefit for improved resiliency. Two or more VLAN interfaces on different physical paths with different quality can be used. Otherwise this would be only possible with additional costs of an external element (cost of HW, it's management and providing outdoor capability for example).RAN2523 is a combination of two features:RU20EP1 RAN1709 VLAN Traffic Differentiation (detailed presentation available here)RU30 RAN1769 QoS Aware Ethernet Switching (detailed presentation available here)

Brief Introduction & Benefits of RAN2523 (1/2)General Introduction# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherBrief Introduction & Benefits of RAN2523 (2/2)General IntroductionIntroduces IP Iub over more than one VLAN interface assigned to two ETH interfaces in BTSCombination of RAN1709 VLAN Traffic Differentiation (traffic mapping to VLAN interface) and RAN1769 QoS Aware Ethernet Switching (VLAN aware switching, using two ETH interfaces)ApplicationsUser Plane Traffic separation: each ETH port can be used for specific traffic types (e.g. one for low priority, one for high priority traffic), allowing to separate these to different Ethernet backhaul technologies (e.g. two xDSL variants or MWR/xDSL in parallel) User Plane Load distribution: Iub user plane traffic is evenly split among the two ETH interfaces and paths, allowing to benefit from higher transport capacities and providing better availability (for U-Plane)Control, Management and Synchronization plane can be configured to any of the two VLAN interfaces

Traffic separation example:VLAN1 = R99 voice&data, control & management planeVLAN2 = HSPAPacketPacket

BTS

RNC

ISP

BTS

RNC

CPE

IntegratedEthernetSwitch

IntegratedEthernetSwitchVLAN1VLAN1VLAN2VLAN2VLAN1VLAN1VLAN2VLAN2User Plane Load balancing example:VLAN1 = all user plane traffic types, control & management planeVLAN2 = all user plane traffic typesETH1ETH2ETH1ETH2# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherGeneral Release Information on RAN2523General IntroductionCommon O&M Platform FeatureNoBSW/ASWASWRAS SW Component RANLicense ControlON/OFFLicence Control in Network ElementTRS LKWCDMA ReleaseRU30EP1I-HSPA System-RNC ReleaseRU20EP1mcRNC Release-BTS (Flexi)BTS (Flexi 10)WBTS7.0 1.0WBTS7.0 2.0NetAct OSS5.3 CD Set3HW Requirements Flexi: FTIA, FTJA, FTIB, FTLB, FTFBFlexi 10: with/without FTIF, FIIF, FTLFRNC: NP2GEUE ReleaseSupplementary O&M InformationRelease Information# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherWith and Without RAN2523General IntroductionRAN2523 ActivatedRAN2523 Not activatedPacketPacket

BTS

RNC

IntegratedEthernetSwitchVLAN1VLAN1VLAN2VLAN2ETH

VLAN1ETH1VLAN2ETH2BTS siteExternal site equipment required in BTS site to separate WCDMA traffic to two physical paths (using ETH interfaces)External site equipment NOT required in BTS site to separate WCDMA traffic to two physical paths (using BTS integrated transport ETH interfaces)Separation based on VLAN IDsTraffic differentiation or Load distribution scenarios possiblePacketPacket

BTS

RNC

IntegratedEthernetSwitchVLAN1VLAN1VLAN2VLAN2ETH1ETH2BTS site# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherInterdependenciesRAN2523 BTS Backhaul over Physically Separated VLAN Interfaces

R 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherRequirements of RAN2523Interdependencies

Feature requirements:RU20EP1 RAN1709 VLAN Traffic Differentiation (traffic differentiation to different VLAN interfaces)RU30 RAN1769 QoS Aware Ethernet Switching (VLAN aware switching in integrated ETH switch)RAN1709 VLAN Traffic DifferentiationRAN1769 QoS Aware Ethernet Switching RAN2523BTS Backhaul over Physically Separated VLAN Interfaces# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherThis feature requires RAN1016/RAN1848: Flexi BTS Multimode System Module. In the RNC RAN1226: HSPA Peak Rate Upgrade for RNC196 and RNC450 is required.

FlexiBTS1.0FlexiBTS2.0FlexiBTS3.0Flexi HW2.1Flexi HW2.2

BTS_SW Release : WN5.0 CD2WN6.0WN6.0 EP1WN7.0

Optional features of RAN2523Interdependencies

Feature options:RU30EP1 RAN2440 Fast IP Rerouting (allows to monitor path connectivity, traffic can then be routed via BTS ETH interface connected to operational path)RAN2523BTS Backhaul over Physically Separated VLAN InterfacesRAN2440Fast IP Rerouting# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherThis feature requires RAN1016/RAN1848: Flexi BTS Multimode System Module. In the RNC RAN1226: HSPA Peak Rate Upgrade for RNC196 and RNC450 is required.

FlexiBTS1.0FlexiBTS2.0FlexiBTS3.0Flexi HW2.1Flexi HW2.2

BTS_SW Release : WN5.0 CD2WN6.0WN6.0 EP1WN7.0

Technical DetailsRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherRAN1709 VLAN Traffic Differentiation OverviewTechnical detailsRAN1709 (first key building block of RAN2523) introduces traffic separation in RNC & BTS according to the traffic type:U-Plane can be separated into high and low priority (e.g. R99 DCH vs HSPA)C-Plane, M-Plane and S-Plane can be separated individually (additionally separate CESoPSN and FPR O&M VLANs are available)Separation is provided by assigning applications to different VLAN interfaces. Each VLAN belongs to separate subnet.RAN1709 main applications:Traffic separation: utilization of different transport media for different trafficTraffic aggregation: different VLANs for different planes in the aggregation network (aggregation is done in transport network, not in the BTS)Load distribution: user plane distribution over two different VLANs (then separated to two paths in transport network) for capacity extension (or U-Plane protection)EthernetViolet = VLAN ID for DCH (rt & nrt)Blue = VLAN ID for HSPA Orange = VLAN ID for O&MDSLViolet = VLAN ID for DCH (rt & nrt), SignallingOrange = VLAN ID for HSPA, O&M

3G BTS

RNC

RNC

3G BTS# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherRAN1769 QoS Aware Ethernet Switching OverviewTechnical detailsRAN1769 (second key building block of RAN2523) introduces following functionalities to BTS (FTM):QoS aware Ethernet switching between Ethernet ports to aggregate Ethernet traffic in e.g. chaining or collocation scenariosVLAN awarenessEgress traffic classification based on either DSCP or 802.1p, QoS scheduling with 4 to 6 queues (depending on Transport Sub-Module) and optional shapingOptional rate limiting for ingress trafficPer ETH port functional blocks shown exemplarily for FTLB

to ETHswitchAggregated uplink trafficEthernet shaping level highpriority lowpriorityUplink traffic BTS #2 highpriority lowpriority highpriority lowpriorityUplink traffic BTS #1VLAN awarenes in Flexi intergated Ethernet switch

Internal EIFEIF1EIF2VLAN1VLAN2# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherThis feature is targeted mainly at scenarios, where two separate last mile links are available and mobile traffic has to be separated to two ETH interfaces towards backhaul (thus avoiding deployment of external L2 switch in BTS site)No new parameters/counters are introduced by the feature (RAN1709 and RAN1769 parameters/counters are valid)There will be no separate feature available for I-HSPA (relevant scenarios will be included in I-HSPA Rel5 RAN1769 feature)Limitations:No different MAC@ per ETH interface (the same BTS internal ETH MAC only available for traffic originated/terminated in BTS)Chaining scenario not supported by FTIB or Flexi 10 without optional transport module (only 2 active ETH available)Assigning both BTS backhaul ETH interfaces to the same VLAN should be avoided (to prevent potential L2 loops)

RAN2523 BTS Backhaul over Physically Separated VLAN Interfaces (1/x)Technical detailsL2L2

BTS

RNC

VLAN1VLAN1VLAN1VLAN1ETH1ETH2

VLAN1L2 loop!# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherRAN2523 BTS Backhaul over Physically Separated VLAN Interfaces (2/x) Technical details

L2Internal EIFEIF3EIF2

FSMFTMRNC

IP@1: UP1, CP, SPIP@2: MPIP@3: UP2VLAN1VLAN2VLAN3L2VLAN1VLAN2VLAN3VLAN3VLAN1VLAN2EIF1Flexi BTSIP@: UP1IP@: UP2IP@: CPIP@: SPToP Master

NetActTraffic separation to VLAN interfaces is applied by RAN1709. On exemplary figure below:VLAN1 carries U-Plane high (UP1: RT/NRT DCH, RT HSPA), C-Plane, S-PlaneVLAN2 carries M-PlaneVLAN3 carries U-Plane low (UP2: NRT HSPA)Traffic class allocation in RNC to VLAN is configurable by means of DSCP/PHB mapping and IP based route(s) parametersVLAN configuration to separate BTS ETH interfaces is applied by RAN1769. On exemplary figure below:VLAN1 and VLAN2 are assigned to EIF1VLAN3 is assigned to EIF2# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherNetwork Design Impact and Use CasesRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherMain application for RAN2523 is two separate last mile links to BTSFor optimum DL traffic control, two IP based routes are recommended per BTS (allowing for independent CAC and IFC configuration per each path)In UL traffic shaping in BTS should be set to Path (allowing for CIR/SIR configuration per VLAN) this is controlled by RAN1709For proper traffic separation between BTS ETH interfaces, it is mandatory to enable VLAN awareness in BTS integrated Ethernet switch this is controlled by RAN1769In case BTS chaining scenario is deployed, egress shaping in integrated FTM switch should be configured in UL, to prevent last mile link from congestion (only single aggregated shaping value is available, thus traffic mapping and scheduling should be aligned to prevent high priority traffic) this is controlled by RAN1769Exemplary (most common) use cases are presented in following slidesRAN2523 RAN Network Design PrinciplesUser scenarios / Use Cases

# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherTraffic differentiation scenarioUP1: RT/NRT DCH, RT HSPAUP2: NRT HSPAU-Plane bearers established via VLAN1 or VLAN3 (depending on traffic class)C-Plane, S-Planed carried over VLAN1Dedicated VLAN2 for M-PlaneVLAN1, VLAN2 are configured over high priority path (e.g. MWR link)VLAN3 is configured over low priority (low cost) path (e.g. xDSL link)No resilience:In case VLAN3 (lower) path is down NRT HSPA services not availableIn case VLAN1+VLAN2 (upper) path is down connection to BTS lost

RAN2523 Use Cases (1/6)User scenarios / Use Cases


FSMFTMRNC


NetAct# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherLoad distribution scenarioUP1, UP2: All U-Plane traffic classesU-Plane bearers established via VLAN1 or VLAN3 (round robin)C-Plane, S-Planed carried over VLAN1Dedicated VLAN2 for M-PlaneSLA requirements for second path dictated by highest U-Plane traffic class (usually RT DCH) requirementsSecond path can be used for U-Plane capacity expansion in backhaul (but no more than 1 Gbps which is available at BTS internal ETH inteface)Partial resilience to U-Plane:In case VLAN3 (lower) path is down all new U-Plane bearers established via VLAN1In case VLAN1+VLAN2 (upper) path is down connection to BTS lost



FSMFTMRNC


NetAct# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherBTS chaining scenario (dedicated VLANs per BTS)VLAN1, VLAN2 assigned to BTS1VLAN3, VLAN4 assigned to BTS2Both Traffic differentiation and Load distribution scenarios are valid for U-Plane (for details refer to previous slides)RAN1769 is not required in BTS2 (when single path between BTS1 and BTS2 is available)Chained BTS can also be deployed with basic functionality (no RAN1709: single VLAN) in that case all BTS2 traffic is switched to single ETH interface of BTS1Full logical (VLAN level) traffic separation between BTS nodes (requires high maintenance effort, possible IP addressing / VLAN scaling limitations)


L2Internal EIFEIF3

FSMFTMRNC

IP@1: UP1, CP, SPIP@2: UP2, MPVLAN1VLAN2L2VLAN1VLAN3VLAN2VLAN1VLAN3EIF1BTS1 (chaining)IP@: UP1IP@: UP2IP@: CPIP@: SPToP Master

NetActVLAN2VLAN4EIF2VLAN3VLAN4

VLAN3VLAN4VLAN4BTS2 (chained)IP@3: UP1, CP, SPIP@4: UP2, MP# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherBTS chaining scenario (shared VLANs)VLAN1, VLAN2 assigned to BTS1 and BTS2Both Traffic differentiation and Load distribution scenarios are valid for U-Plane (for details refer to previous slides)RAN1769 is not required in BTS2 (when single path between BTS1 and BTS2 is available)Chained BTS can also be deployed with basic functionality (no RAN1709: single VLAN) in that case all BTS2 traffic is switched to single ETH interface of BTS1No logical (VLAN level) traffic separation between BTS nodes (but requires lower maintenance effort, IP addressing / VLAN scaling limitations less severe)


L2Internal EIF

FSMFTMRNC

IP@1: UP1, CP, SPIP@2: UP2, MPVLAN1VLAN2L2VLAN1VLAN2VLAN1EIF1BTS1 (chaining)IP@: UP1IP@: UP2IP@: CPIP@: SPToP Master

NetAct

BTS2 (chained)IP@3: UP1, CP, SPIP@4: UP2, MPVLAN1EIF1VLAN2EIF2VLAN2VLAN1EIF3VLAN2# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherBFD protection introduced with RAN2440 Fast IP Rerouting (no U-Plane traffic separation scenario)BTS transport IP addresses: IP@3 (VLAN1), IP@4 (VLAN2)BTS virtual IP addresses:IP@1 for U-Plane, C-Plane, S-PlaneIP@2 for M-PlaneVLAN1 is assigned to BTS EIF1, VLAN2 is assigned to BTS EIF2Single-hop BFD session established via VLAN1 between BTS transport IP address and router interfaceRAN2523 Use Cases (5/6)User scenarios / Use Cases


FSMFTMRNC

IP@1: UP, CP, SPIP@2: MPVLAN1L2VLAN1VLAN3VLAN2VLAN1EIF1Flexi BTSIP@: UPIP@: CPIP@: SPToP Master

NetActIP@3IP@4

BFD sessionVLAN2Two paths (static route entries) are configured in BTS and in RNC site router (higher preference via VLAN1, associated with BFD session; lower preference via VLAN2)In normal conditions (both paths operational) all BTS traffic is forwarded via VLAN1 (upper L2 path)When BFD session goes down all BTS traffic is forwarded via VLAN2 (lower L2 path)

# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherBFD protection introduced with RAN2440 Fast IP Rerouting (U-Plane traffic separation scenario)BTS transport IP addresses: IP@3 (VLAN1), IP@4 (VLAN2)BTS virtual IP addresses:IP@1 for U-Plane high (RT/NRT DCH, RT HSPA), C-Plane, S-PlaneIP@2 for M-Plane, U-Plane low (NRT HSPA)VLAN1 is assigned to BTS EIF1, VLAN2 is assigned to BTS EIF2Two single-hop BFD sessions are established:(1) via VLAN1 between BTS transport IP@3 address and upper router interface(2) via VLAN2 between BTS transport IP@4 address and lower router interfaceRAN2523 Use Cases (6/6)User scenarios / Use Cases


FSMFTMRNC

IP@1: UP1,CP,SPIP@2: MP,UP2VLAN1L2VLAN1VLAN3VLAN2VLAN1EIF1Flexi BTSIP@: UPIP@: CPIP@: SPToP Master

NetActIP@3IP@4

BFD session 1VLAN2BFD session 2Two paths (static route entries) are configured in BTS and in RNC site router (for UP1, CP, SP higher preference via VLAN1 associated with BFD session 1; for UP2, MP higher preference via VLAN2 associated with BFD session 2)In normal conditions (both paths operational) BTS UP1, CP, SP traffic is forwarded via VLAN1 (upper L2 path), while UP2, MP traffic is forwarded via VLAN2 (lower L2 path)When any of two BFD sessions goes down, all BTS traffic is forwarded via remaining operational L2 path

# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherSummary of network design impact Transport ModuleTwo ETH interfaces can be used for backhaul connectivity (and optionally third ETH interface for chaining)IubIub traffic can be effectively split to two separate backhaul paths already in BTS (no external site equipment required)

Network Engineering dimensioning tools impact:ANT_3G_DimAdditional configuration options to be taken into account (traffic separation to two ETH interfaces)No impact on dimensioning methods (any changes already introduced by RAN1709 and RAN1769 are still valid)

# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherActivation parameters and Licensing AspectsRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherActivationParameters and configuration recommendations / procedures applicable to RAN1709 and RAN1769 are also valid for RAN2523Enabling RAN1769 VLAN awareness (on top of proper IP addressing, VLAN configuration and QoS traffic mapping/scheduling) is mandatoryLicensingThere is no dedicated license for RAN2523 (both RAN1769 and RAN1709 licenses are required)RAN1769 and RAN1709 are licensed with a long-term ON/OFF license, which are activated in the BTSRAN2523 BTS Backhaul over Physically Separated VLAN InterfacesActivation and Licensing

# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha MalcherThank you for your attentionR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:# Nokia Siemens Networks 2011For internal useNWS Network Engineering / Micha Malcher# Nokia Siemens Networks 2011For internal useR 255 G 204 B 0R 255 G 130 B 0R 110 G 6B 115R 163 G 166 B 173R 104G 113 B 122R 234 G 234 B 234R 170 G 15B 30R 0 G 0 B 0R 255 G 255 B 255Supporting colors:R 60 G 170 B 0Primary colors:NWS Network Engineering / Micha Malcher

Documents

RAN2523 BTS Backhaul Over Physically Separated VLAN Interfaces