IP RAN Network Design 2G & 3GMuhamad YopanCCIE#38903Ericsson IndonesiaCCIETalk session, May 12, 2013

Meet Challenges in Mobile Backhaul

2G/3G Network Architecture

IP RAN Solution What it meansIP RAN is a full IP connectivity solution to enable smooth and future-proof introduction and deployment of IP transport in RAN.IP RAN covers IP feature in GSM and IP in WCDMA.IP RAN is a tested and verified solution and is aligned with M-PBN.

ScopeDesigns maintaining RAN performanceCapacity & SynchronizationQoS & Traffic SeparationNetwork SecurityFuture proof designs based on verified IP-RAN solution Automated Design and Integration configuration transfer Competence to handle the complexity of Multi-vendor networks

Competencies requiredIPBasic- IP Addressing- VLAN- Static routing- Dynamic routing (OSPF, IS-IS)- STP (MSTP, PVST, RSTP)- VRRP, HSRP- QOS- BFDOptional:- IP MPLS - VPN L2/L3- MPLS TP- Tunneling- Metro E- IP SLA

Mobile broadband- 2G Architecture- 3G Architecture- Product Knowledge

Functionality

Transport ConnectivityNetwork SynchronizationQuality of ServiceSecurity

Transport Connectivity

Synchronization in IP RAN

In traditional GSM/WCDMA access networks, the distribution of a reference clock signal to the RBS is supported by the SDH and PDH technology

In Packet Transport Network the RBS cannot be synchronized by traditional PDH/SDH layer 1 interface

Network Synchronization over IP Transport transparent and independent (L2, L3, access, backhaul)Client/Server solution, integrated in the certain boardsProven in real networksNo need for GPS, ITU1588, Sync Over Ethernet solutionsUse protocols available today (NTP/PTP)

QoS requirements on IP RANTelecom Grade requirements on Transport NWDifferent requirements on voice and data Service Performance seen by users is degraded with increased delay or frame loss

QoS Priority Handling

Handletraffic according to Network, Userand ServicedimensionsCommon QoS rules for GSM/WCDMA/LTEA framework for resolving RAN congestion in a controlled and predictable way, when demand for resources exceeds supply.

Quality of Service

QoS traffic handlingTraffic classification for both GSM & WCDMAMarking: DSCP and/or p-bitQueuing

Queuing capabilities are hardware dependent. It is recommended to use three or four queues in the Transport Network.

QoS Supported in IP RAN

The use of DSCPApplication mapping to DiffServ is recommended to be the same within a network domain (dedicated RAN, Dedicated Core or Common multi-service).

The use of p-bitsMapping to Ethernet-QoS can be used differently due to queue-principles and congestion behavior.

Remarking/RemappingIf the transport network could handle QoS on both, L3 and L2, the Per hop-behavior (DiffServ value) is the one to act upon.

Network planning & design key for success

Adaptation of Class-of-Service to network conditions

SecurityRAN Security:Iub user plane frames are encrypted (3GPP standard) from RNC to UEAbis user plane is not encrypted from BSC to RBSControl plane is sent open for bothGSM & WCDMAO&M traffic is protected on application level for both GSM & WCDMAHighest priority is to protect BSC/RNC and OSS from external intrusion.

Consideration AspectNew network architecture between Access and Core networksNetwork topology logical and physicalChoice of backhaul network (L2 or L3 IP network)Network Security, Quality of Service and SynchronizationO&M networkExisting backhaul network and backhaul providersCore network IP infrastructureTraffic model and Node & Interface dimensioningMigration and Future expansion

Related ServicesThe IP-RAN Network Design has relationships with the following services:Network Strategy ConsultingMicrowave Network DesignOptical Network DesignCore Network DesignProduct Configuration & IntegrationSite Engineering & InstallationCustomer Training

IP RAN Network Design ApproachBuildRequirementSpecificationDetailed DesignSpecificationNetworkAcceptanceAddressingTraffic ModelingTopologySecurityL3 RoutingL2 SwitchingNode & InterfaceDimensioningProtection & RedundancyTraffic SeparationQuality of ServicesettingSolution DesignSpecificationTunneling &FirewallingStart-up & Info GatheringSolution DesignDetailed Design Conclusion

Integration

Build

Cases

2G Physical Topology

2G Logical Topology (Southbound)

2G Logical Topology (Northbound)

IuPs

IuPs

The service is divided in three major phases; Information Gathering collects the operators requirements and systemrequirements for the IP RAN Network Design and translates them into aproject specification and a requirement specification. Solution Design creates a network solution, where the requirements aretranslated into plans that consider network architecture, capacity, security,Service Level Agreements, etc.Detailed Design builds on the solution design and produces all necessarymaterial for a successful integration and implementation of the IP RANsolution.

--------------------Information GatheringThe main activity of this sub-process is to collect requirements andassumptions regarding how to introduce the LTE/WCDMA/GSM IP RANsolution. This sub-process involves the following activities: Creating a Responsibility Matrix, reflecting customer and Ericssonresponsibilities during the design project. This may be defined by theEricsson project manager for the overall IP RAN deployment project. Gathering customer requirements, assumptions, agreements, andguidelines from various other sources into a specification that will be thebasis for the design.Some examples of customer requirements: Selection of nodes and site infrastructure for IP RAN deployment anddetails of site survey Survey of northbound, to Core Network, IP site Infrastructure Survey of the operators access transport network (ATN), in case of selfbuiltIP-ATN for IP RAN Number of subscribers and distribution of subscribers, actual andforecastedIP RAN Network Design for GSM, WCDMA and LTE18/22103-FGC1010109 Rev H 2012-11-16 Ericsson AB 2009 - 2012 open 13 (16)Ericsson Internal Traffic model, actual and forecasted Network related requirements, e.g. SLAs, security policies, IP addressingand network expansion plansThe focus of the Information Gathering phase is the interaction between thecustomer and Ericsson, in order to ensure a mutual understanding of therequirements and assumptions to be used in the Solution Design and DetailedDesign.

Solution DesignThe main goals of the Solution Design phase are to translate technicalrequirements into an IP RAN Network Design, to identify the network elementsto be included in the IP introduction in RAN, and to describe the impact on theexisting network infrastructure.During Solution Design, the following activities are covered: Define the IP RAN network aspects suitable for the operators network Develop and apply network scenarios, traffic models, and subscriberprofiles, etc. Dimension the network with respect to the traffic model, QoSrequirements, security policies, geographical needs, topology, bandwidth,and redundancy Perform node dimensioning and link dimensioning, based on customerrequirements and other inputs Define security activities (traffic separation, VLAN, authentication,encryption) Manage the following based on Service Level Agreements;- Delay and variation- Synchronization- Packet drop probability- Availability- Prioritization Define type nodes in terms of HW and SW, based on product packages Perform high-level logical network design. The result will be a networkdrawing showing physical and logical network topology.

Detailed DesignIn the Detailed Design sub-process, the implementation and integration detailsare completed, starting from the high-level solution made in the SolutionDesign. Many of the activities will be the same as for the Solution Design subprocess,but on a more detailed level.During Detailed Design, the following activities are covered: Perform the complete logical network design, which enhances the highleveldesign with descriptions of all logical connections between theinvolved nodes. Complete address plans and routing plans are included,among others Perform physical network design, based on the logical network design.This results in descriptions that show all physical interfaces and theconnections between them Present detailed node HW dimensioning and link dimensioning based ondetailed traffic model information provided either by the customer or anetwork audit service Create node configuration, which specifies configuration information forimplementation of each node and interface (such as addresses, routing,protocols, security, and more) Create the documentation needed for presentation and understanding ofthe Detailed Design. The result includes detailed drawings for the logicaland physical views

Acceptance and conclusionThe outputs of the Detailed Design sub-process are handed over to theimplementation and integration phase of IP RAN deployment project.Acceptance of IP RAN Network Design for LTE/WCDMA/GSM is concluded bythe successful integration and implementation of Detailed Design.