The service is divided in three major phases; • Information Gathering collects the operator’s requirements and system requirements for the IP RAN Network Design and translates them into a project specification and a requirement specification. • Solution Design creates a network solution, where the requirements are translated into plans that consider network architecture, capacity, security, Service Level Agreements, etc. Detailed Design builds on the solution design and produces all necessary material for a successful integration and implementation of the IP RAN solution. -------------------- Information Gathering The main activity of this sub-process is to collect requirements and assumptions regarding how to introduce the LTE/WCDMA/GSM IP RAN solution. This sub-process involves the following activities: • Creating a Responsibility Matrix, reflecting customer and Ericsson responsibilities during the design project. This may be defined by the Ericsson project manager for the overall IP RAN deployment project. • Gathering customer requirements, assumptions, agreements, and guidelines from various other sources into a specification that will be the basis for the design. Some examples of customer requirements: • Selection of nodes and site infrastructure for IP RAN deployment and details of site survey • Survey of northbound, to Core Network, IP site Infrastructure • Survey of the operator’s access transport network (ATN), in case of selfbuilt IP-ATN for IP RAN • Number of subscribers and distribution of subscribers, actual and forecasted IP RAN Network Design for GSM, WCDMA and LTE 18/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 addressing and network expansion plans The focus of the Information Gathering phase is the interaction between the customer and Ericsson, in order to ensure a mutual understanding of the requirements and assumptions to be used in the Solution Design and Detailed Design. Solution Design The main goals of the Solution Design phase are to translate technical requirements into an IP RAN Network Design, to identify the network elements to be included in the IP introduction in RAN, and to describe the impact on the existing network infrastructure. During Solution Design, the following activities are covered: • Define the IP RAN network aspects suitable for the operator’s network • Develop and apply network scenarios, traffic models, and subscriber profiles, etc. • Dimension the network with respect to the traffic model, QoS requirements, security policies, geographical needs, topology, bandwidth, and redundancy • Perform node dimensioning and link dimensioning, based on customer requirements 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 network drawing showing physical and logical network topology. Detailed Design In the Detailed Design sub-process, the implementation and integration details are completed, starting from the high-level solution made in the Solution Design. 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 highlevel design with descriptions of all logical connections between the involved 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 the connections between them • Present detailed node HW dimensioning and link dimensioning based on detailed traffic model information provided either by the customer or a network audit service • Create node configuration, which specifies configuration information for implementation of each node and interface (such as addresses, routing, protocols, security, and more) • Create the documentation needed for presentation and understanding of the Detailed Design. The result includes detailed drawings for the logical and physical views Acceptance and conclusion The outputs of the Detailed Design sub-process are handed over to the implementation and integration phase of IP RAN deployment project. Acceptance of IP RAN Network Design for LTE/WCDMA/GSM is concluded by the successful integration and implementation of Detailed Design.
IP RAN is a reference solution2G3GLTEBSCRNCcell site– Physical and logical connectivity– HW recommendations– Redundancy– 2G/3G/LTE/Wifi co-location– Quality of Service– Synchronization– Security– IP Addressing– ManagementA reference for how to connect cell site and switch site:switch siteMBH MPBNSIU/TCUMPBNCPG / MMEIP RAN IP RANSwitch siterouterOSS-RCSynchsrvIPSecMBHcell sitecell site
IP RAN Design Goals The IP RAN solution abstracts away the diverse transport networks-Multiple technologies and providers but one network view for the RAN applications Provides a unified set of services to the RAN applications-Synch, QoS handling, SLA monitoring, security, ...Utilizes simple, cost efficient transport servicesEnables multiple transports to cell site- Different transports for different traffic types with different requirements (QoS vs. Availability)Dual transport redundancy
IP RAN solution is aligned with mbhand Mpbn2G3GLTEBSCRNCCGWMSSMMECGWIP RAN MBHLRAN, AccessMPBNHRAN, METROIP RANMPBNFor Mobile CoreIP siteInfrastructureMultivendorMBHMultivendor
• The IP RAN solution is fully aligned with theMobile Backhaul and the MPBN solutionsTogether they form “Mobile Transport”, and provides end-to-endtransport services.Mobile Transport
IP RAN recommends the SoIP solution• SoIP is independent on what transport network isused as long as it provides IP connectivity and theright characteristics• Based on standard NTP and/or 1588v2– Same transport network requirements, same syncalgorithm• SoIP server integrated in the RNC boards– SoIP over NTP only supported• Standalone SoIP server required for 1588v2• SoIP client in SIU, TCU 02 and RBSes– 1588v2 currently only supported by the SIU/TCU 02• Proven in live customer networks
RAN security challenges• User plane traffic:– GSM: Abis is not encrypted from BSC to RBS– WCDMA: Iub frames are encrypted (3GPP standard) from RNC to UE– LTE: Can be natively protected using IPSec• Control plane traffic:Is un-encrypted for GSM, WCDMA and LTE.– Can be protected using IPSec for GSM and LTE– Can be protected using external IPSec equipment for WCDMA• O&M traffic:– Is protected on application level using SSL for both GSM, WCDMA and LTE(Ericsson solution)– IPsec is supported for LTE O&M and can be activated if needed, to get an extralevel of security• Highest priority is to protect BSC/RNC site and OSS from external intrusion.
IPSec in LTE• eNodeB supports IPSec (currently for IPv4 only) to protect traffic– Tunnel mode– Encryption and integrity (ESP) according to 3GPP• Anti-replay protection• 3DES and AES encryption• MD5 and SHA-1 integrity– Certificates based IKEv2 key handling• Separate tunnels for UP/CP/Synch and O&M.– One IPsec tunnel for UP/CP and Synch, and one for O&M. (O&M is alsoSSL-protected inside the IPsec tunnel).– Redundant tunnels monitored using Dead Peer Detection• Auto integration also supports IPSec– Using IKEv2 Configuration Payload
QOS PRIORITY HANDLING• IP RAN solution providesrecommendations for:– Traffic classification– Prioritization– Scheduling– Link dimensioning (including foradaptive modulation)•The solution resolves RANcongestion in a controlled andpredictable way• Common QoS recommendationsapply forGSM/CDMA/WCDMA/LTE