UMTS Network RAN Sharing SolutionRAN Sharing Solution Overview of RAN Sharing Key Techniques in RAN Sharing ZTE RAN Sharing Solution Drivers of Network Sharing • Operators are facing challenges of cutting cost when ARPU decreases continuously Cost Driver • Network sharing can save the rental and number of sites dramatically • Coverage in rural areas is unprofitable • Hard to acquire site Market Driver • Fast deployment in the initial stage • Win additional revenue to provide network sharing • Green and environmental concerns • Government encourage network sharing to save resources and protect environment, provided that competition is not weakened • Government encourage operators to share their infrastructure to expand coverage and foster the market in early 3G deployment • Operators share one 3G license in some countries Regulation Driver 3 Cost Analysis of Network Construct and Operating Incumbent network cost structure New entrant network cost structure 2% 5% 24% Core Network RAN 36% Billing System Service Platform NMS Rollout Cost 30% 46% 14% 2% 5% 29% 1% 0% 4% 2% Transimission Source: Coleago Consulting Typical European 3G site cost breakdown (FY07/08e) Capex Backhaul (microwave) RAN equipment Civil work 37% 27% 36% Opex Rentals/ leases Maintenance Source: Vodafone 41% 22% 16% Backhaul (leased lines) 21% Other (inc energy) 4 3GPP specification TS 23. Node B.VAS) GW CORE (MSC/SGSN/MME) Shared RAN Shared RNC Shared carrier Shared NodeB Shared carrier f1 f2 f1 f1 f2 f1 Shared NodeB Shared RAN Shared RNC 6 .GGSN. RNC and Core network elements Network Architecture MOCN Carrier Configuration Carrier dedicated Carrier shared GWCN Carrier dedicated Carrier shared 5 Network Architecture in RAN Sharing RAN Sharing GWCN RAN Sharing MOCN Common sharing of RAN equipment and carrier Gateway core network is shared UE select operator based on PLMN ID GW core routes message to the right operator Common sharing of RAN equipment and carrier 。 Independent core network UE select operator based on PLMN ID RNC routes message to the right operator Core of operator A Core of operator B Core of operator A (HLR. and defines the specification of UE.Standardization of Network Sharing RAN sharing is standardized in 3GPP release 6 Only shared carrier RAN sharing need to be standardized. Other forms of network sharing has no impact on 3GPP standard.VAS) Core of operator B (HLR.GGSN.251 gives the technology specification of common carrier RAN sharing. they are fully compliant with pre-R6 standard. Carriers Strategies in RAN Sharing Dedicated Carrier RAN sharing Shared Carrier RAN sharing Further sharing of RNC and NodeB Logical independent access network with each operator has its own frequency Further sharing of RNC and NodeB Logical independent access network with each operator has its own frequency Balance between cost saving and network independence Balance between cost saving and network independence CN Shared RAN Shared RNC F1 of operator A Shared NodeB F1 of operator A and B Shared RAN CN Shared RNC f1 f2 F2 of operator B f1 f2 f1 f1 Shared NodeB 7 Operators Cooperation in RAN Sharing Geography Sharing MVNO separated network that have different geography coverage Provide service to each other through network sharing agreements MVNO has no radio access network. It has its own VAS platform MVNO rent MNO’s network to provide service. but it has its own brand and channel Used to provide national coverage for small operators or in underserved areas Core of operator A Core of operator B Core of operator A MVNO VAS GW Core of operator A RNC sharing agreement RAN of operator A RNC RAN of operator A RAN of operator B NodeB f1 f1 8 . It may or may not have its own core network. Operators Cooperation ScenariosBoth Operators own frequency resources When operators have their own frequency resources Dedicated Carrier MOCN RAN sharing is the most applicable solution Dedicated Carrier GWCN RAN sharing is also a possible solution CN A CN B CN A CN B GW CORE (MSC/SGSN) RAN of A RAN of B RAN of A Shared RAN Shared RAN RAN of B A and B share RAN in some areas. A provides shared RAN to B. 9 Operators Cooperation ScenariosOnly One Operator has frequency resources When one operator have not their own frequency resources Shared Carrier MOCN RAN sharing is the most applicable solution Shared Carrier GWCN RAN sharing has the least possibility. CN B CN A CN A CN B RAN A Shared RAN by B Shared RAN by A RAN B RAN A Shared RAN by B RAN B A and B provide shared RAN in different geographical areas. 10 . A and B share RAN and part of CN in some areas. Vodafone and Orange announced their network sharing plan. Telenor and Tele2 setup joint venture Net4Mobility to build their shared GSM and LTE network. 30% of the coverage must be provided by their own network and the other 70% can be provided by shared network Network sharing Teliasonera and Tele2 setup their joint venture Svenska UMTS Nät AB to build and operate their shared UMTS network Telenor and H3G setup their joint venture 3GIS to build and operate their shared UMTS network. and replace their own GSM outdated network All shared network in Sweden are common carrier RAN sharing 12 Svenska UMTS Nät 3G Infrastructure Services AB Net4Mobility . Orange. Tele2. Vodafone. to improve coverage. aiming at build the largest HSPA network in Europe 11 Network Sharing in Europe – Sweden Summary of the market Adequate competition market with four operators: Teliasonera. quality and lower cost National roaming Site sharing In Dec. T-Mobile Full sharing Operators hope to strengthen their market position through network sharing Regulation UK Government encourage network infrastructure sharing to improve coverage and service quality. 2007. T-Mobile and H3G announced their 3G network sharing plan.Network Sharing in Europe – UK Summary of the market Adequate competition market with five mobile operators: O2. which covers 70% of the population In April 2009. 2007. but network sharing should not threaten competition Full sharing Network sharing T-Mobile and O2 began site sharing and H3G uses O2’s network for national roaming from 2003 In June. HI3G Teliasonera and Tele2 are competitors share one 3G license and jointly build the 3G network Regulation Operators are obliged by regulators to provide 100% 3G coverage nationwide. Telenor. having a long term object of consolidate current network and jointly build out new network. H3G. Network Sharing in Asia Regulation Encourage and requires passive & active RAN sharing. Network sharing mode Main Features required by Operators Flexible dynamic resource sharing between operators. non continuous segment for example. Operator specific resource and license control and management. Flexible carrier configuration. Some operators’ require priority of resource utilization by dedicated resource allocation. MOCN/GWCN with dedicated carrier. Renting mode is the main required operation mode. 13 Overview of Network Sharing Key Techniques in RAN Sharing ZTE Success Stories . Spectrum sharing is not permitted in some countries. 16 . And ZTE consider the UE mode as pre-R6 mode and R6 mode when they stay in idle or connected status. UE could selects the network which it can attach.3GPP Consideration on RAN Sharing Deploying RAN sharing in the network. Key Technologies: Message Routing & Network Logo display 15 3G Message Routing – GWCN with Support UE (R6) GWCN: ―The system broadcasting information includes network sharing status. the network should solve the issues on all UE mode. PLMN ID display and mobility management Regarding the various UE type and compatibility. ―SGSN send back the accept or reject information. ―Then UE send the request to the SGSN and the SGSN could determine if the UE belong to the any one of it’s shared operators. should face some key issues: message router. choose the common information and send to CN ―Then UE send the request to the SGSN and the SGSN could determine if the UE belong to the any one of it’s shared operators. choose the correct CN ―Then RNC send the request to the correct SGSN depends on the sharing information decoded by the UE and the SGSN could determine if the UE belong to the any one of it’s shared operators. ―SGSN send back the accept or reject information. ―SGSN send back the accept or reject information.3G Message Routing – GWCN with Non Support UE GWCN: ―The system broadcasting information includes network sharing status. 17 3G Message Routing – MOCN with Support UE MOCN: ―The system broadcasting information includes network sharing status. UE decode the network sharing information. UE cannot decode the network sharing information. 18 . Reroute command may repeat some times and increase the network load and time delay. 20 . and SIM Card customization can be auxiliary method. - 19 PLMN ID/Name Display Overview The PLMN Name or Operator Name is mapped from the PLMN ID(MCC+MNC). RAN Updating and NITZ can be major methods for Name Display. How UE display the correct PLMN ID is a key issue because pre-R6 UE can only read primary PLMN ID from the broadcasting information.3G Message Routing – MOCN with Non Support UE ––Network Protocol Updating Common frequency Sharing In MOCN: Network update to support R6 signaling protocol with reroute command. e. Then the UE perhaps could not judge the correct operator’s name. And UE could display the correct operator name by the common ID.PLMN ID/Name Display – SIM Card Updating The UE could store at least 10 PLMN ID and the corresponding operator name. The pre-R6 UE could not read the list while only read one PLMN ID. normally this ID will be the common ID which is one of the sharing operators’ ID. Common ID = 460 08 Then Operator A SIM store: 460 01 = 460 08 = “Operator A Name” And Operator B store: 460 03 = 460 08 = “Operator B Name” The Operator Name could display 21 Operator A Operator B 460 01 460 08 Name A Name A Name B Name B 460 03 460 08 Common ID 460 08 Operator A & Operator B Sharing Operator A 460 01 Operator B 460 03 PLMN ID/Name Display – RAN Updating to R6 Add a PLMN ID list in the broadcasting information in MIB field which need RAN Updating R6 UE could read the whole list and find out the correct PLMN ID and display the operator name. The operators write the sharing network PLMN ID which is a common ID into the SIM card. That means the UE could be allowed register but could not display the correct operator name Operator A Operator A 460 01 460 03 460 01 460 01 Sharing Operator B 22 . Operator A PLMN ID = 460 01 i. i. Operator B PLMN ID = 460 03 If Operator A and Operator B have a sharing network and make a common ID for that.e. the mapping among the SNA and TMSI is send to RNC and stored in RNC. when RNC initiation. 23 ① Register Requirement ③ Display the Operator Name ② NITZ include Operator ID After Register CMCC Sharing China Unicom Mobility – Sharing Network Mobility Management SNA ( Shared Network Area ) Area consisting of one or more LA’s to which access can be controlled. • After UE attachment. use the default content. which includes the local time . • CN sends SNA and LA mapping table to RNC. When UE dose not support NITZ. • • Handover based on SNA During the connected status – CELL_DCH. date and the operator name. Location Area Update Cell Update Based on SNA • Location area update and cell update are supported based on the SNA when UE is idle status or no connected status – Update procedure between the shared network and the non shared network.PLMN ID/Name Display –NITZ Network Supports NITZ. The NITZ information will include the correct PLMN ID and operator name after the UE register success. – Update procedure inside the shared network 24 . also synchronizing the time and date. Network Identity Time Zone. UE decode the NITZ information and display the operator name. handover is supported – Handover between the shared network and the non shared network. . – Handover inside the shared network. Overview of Network Sharing Key Techniques in RAN Sharing ZTE RAN Sharing Solution ZTE RAN Sharing Solution Overview Main Investment Base Station Sharing Base Station BP resource and RU sharing Static/Dynamic Power Control Large capacity and flexible configuration Radio network controller Radio Network Controller Sharing Resource distribution and management Transmission interface resource sharing O&M Sharing Operation & maintenance mode Access authorization control and management Features launching and license Operation & Maintenance 26 . DL 43. BSC/RNC Operators can share one RRU based on cell level. DL 192CE/BP UL 15Mbps. 28 . SE:0/1 1/2 1/1 Some boards can be dedicated for multi-PLMN Base Station-RRU Sharing Sector Cell-1 Cell-2 Cell-3 Cell-4 RRU sharing: Dedicated carrier: Operators distinguished by PLMN2 ID Sector PLMN-1 PLMN-2 PLMN-3 PLMN1 ID PLMN3 ID PLMN4 ID frequency point. Shared carrier: operators distinguished by PLMN-id in cell broadcasted information.2Mbps/BP Module Name CC Board FS Board UBPG/BPC Board SA/SE PM Module FAM Shared Y Y Y Y Y Y Dedicated N Y Y Y N N 27 Min/Max Configuration 1/2 1/2 1/5 SA: 1/1. Operators can share one RRU based on cell level.Base Station-BBU Sharing UMTS BP Board UL 192CE. RRU Support Multi PLMN Configuration (3G) RRU Unit 20MHz RF Bandwidth 4 Carriers Supported 5MHz Multi-PLMN 4 carriers configured to 4 operators Operator B Operator A 20MHz RSU Module Multi-PLMN configuration Operator A Operator B Operator C Operator D R S U R R R S S S U U U 20 MHz 1 RU to 3 RU 3 RU to 6 RU R RR R R R S SS S S S U UU U U U BBU BBU S1+S1+S1+S1 BBU BBU S111+S111+S111+S111 29 BBU BBU S222+S222+S222+S222 BP Resource Sharing Methods BP Board BP Board Three types of BP resources sharing for different scenarios Operator A Operator A BP Pool Operator B Operator B Dynamic Operator A Operator C Operator B BP Dynamic Sharing available BP resources dynamic shared by operators BP Flexible Allocation 09Q4 BP resources static reserved by operators BP Hybrid Allocation 09Q4 Dynamic shared + Reserved shared 30 . PA Output Power Sharing.Static Configuration Multi operators have same TOC. Average power allocation Un-equivalent power allocation PA Output power 80W time 31 RNC Sharing and Dedication RNC BGSN Operator 2 BGSN BGSN Operator 1 Dedicated Shelf Control plane sharing User plane dedicated and sharing management Shared Shelf BCTC Interface dedicated and sharing management BPSN 32 . Static output power configuration Multi operators have un-equivalent TOC. will be sent to corresponding CN. For the Non-initial access. and RNC will extract the PLMN-id from IMSI. avoid CN upgrade and reiterate message procedure For initial access.ZTE innovative solution for Message Routing RAN support NRI analysis. then the attach message is directly routed to the correct CN. RNC will reiterate all CN supported by the carrier. If the NRI is valid. such as roaming subscriber’s H-PLMN is not matched in NRI codes. and RNC will get NRI through TMSI. the NRI will be analyzed. 33 IMSI PLMN ID TMSI NRI NRI Valid Find correct CN NRI Invalid reiterate all CN CN A CN C RNC Interface Resource Sharing & Dedication ll Ce 3 1 Cell 1 TRX MSC MSC Iu-CS SGSN SGSN Iu-PS 2 Ce ll 2 TR X Iu-b Node B RNC Iu-r All the interface Resources Pool: dynamic sharing Dedicated interface: Static reservation (09’Q4) 34 . MS will send IMSI to RNC. MS will send TMSI to RNC. If the NRI is invalid or can not be correctly decoded. the services priority could be defined separately. 128K 64K When the limitation occur . for the transmission or the code resource. Flexible partitioning: Convenience to separate.Iub Transmission Resource Dedication —Shared bandwidth —Operator A bandwidth —Operator B bandwidth BSC/RNC ATM/IP(3G) TDM/IP(2G) BTS/NodeB Realized 10’Q4 10’Q4 Dynamic pooling Flexible partitioning Hybrid mode Dynamic pooling: high usage efficiency. the system resource will be distributed to the high priority operator first Services Priority – For each operator. the lower level UE will be handed over to lower speed or other cells 36 . The hybrid one : CAC bandwidth assignment and congestion avoidance. 35 QoS Level for operators by PLMN in RNC Operators Priority ZTE BSC/RNC could provides the access control. call control and load balance by the operators’ QoS level – Operators could be set with different priorities. ) RNC/BSC/Site level software upgrade and status query. RNC capacity.2 UTRAN RAN resource for A Reserved resource for B available resource: BP CE. •LMT /EMS will not be distinguished according to different operators. 38 . mainly including: RNC/BSC/Cell level configuration (Hardware.ZXWR UTRAN Sharing Solution Roadmap 2010Q4 Operator B Operator B (Joint Venture) (Joint Venture) Read/Write UTRAN Operator N Operator N (Renting) (Renting) Read Sharing Phase3: Operator QoS Priority Operator Specific Iub/Iur Transmission Operator Specific Feature Control Only U10. RNC/BSC/Site level FM and PM. Backhaul bandwidth Sharing Phase2: Specific FM/PM/CM Resource dynamically shared Sharing with Shared Carrier Operator 2008 Operator A CN Operator A V408 UTRAN Multi Sharing Phase1: PLMN Support RAN Sharing Support Networks Access Control Sharing with Dedicated Carrier Basic RAN Shared Operator B Operator N Operator N CN Released Released Planned Planned Planning Planning 37 Unified EMS System. •Support independent NMS interface.1 Operator A Operator A (Host) (Host) Reserved & SW Setting for A QoS & SW Setting for N OMC OMC Total QoS 2009Q4 U9. Transmission.Multiple North Bound Interface Operator A Operator A NMS NMS Ift-N In Ift-N Inte terface rface Shared EMS Shared EMS ace rffac e Intte r In e Ifftt--N I N Operator B Operator B NMS NMS Operator A Operator A Operator B Operator B Shared Shared RAN RAN •A shared NETNUMEN™M31 manages all O&M functions. All three methods can be used in conjunction with each other. Example: Operator A Capacity Feature 2010-8-4 Operator B 50K TRX FR、HR Implement Date 2008Q4 2010Q4 EMS Level Cell Level 100K TRX FR、HR、AMR 40 . BSC or RNC can be authorized with different function. Capacity authorization: Restrict authorized network hardware capacity based on TRX or Cell. Feature authorization: Different cell. Support capacity reconfiguration without reactivation.North-bound Interface The maximum number of concurrent connections to NMS is 4 Cell-level FM/PM/CM can be distinguished on NBI for different operators Operator A Operator B Operator C EMS CM/PM FM/IM CM/PM/FM/IM CM/PM FM/IM Host Operator A Partner Operator B Partner Operator C Host Operator A’s cells Partner Operator B’s cells Partner Operator C’s cells R/W R/W R/W 39 --R --- ----R Resources & Features Control between Operators License control type License control principle Date authorization: Network operation is valid until a defined date. 41 .Summary for Network Sharing Architecture: GWCN and MOCN Carrier: Dedicated or Shared Network Sharing Specification detailed in R6 Options for Network Name Display in Pre-R6 Terminal ZTE RAN Network can be fully shared. and Resources flexibly controlled. ZTE Innovative solution to avoid CN upgrade for pre-R6 terminals in RAN Sharing Solution.