Académique Documents
Professionnel Documents
Culture Documents
RAN Sharing
Feature Parameter Description Copyright Huawei Technologies Co., Ltd. 2010. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Technologies Co., Ltd.
Notice
The purchased products, services and features are stipulated by the commercial contract made between Huawei and the customer. All or partial products, services and features described in this document may not be within the purchased scope or the usage scope. Unless otherwise agreed by the contract, all statements, information, and recommendations in this document are provided AS IS without warranties, guarantees or representations of any kind, either express or implied. The information in this document is subject to change without notice. Every effort has been made in the preparation of this document to ensure accuracy of the contents, but all statements, information, and recommendations in this document do not constitute the warranty of any kind, express or implied.
Contents
Contents
1 Introduction ................................................................................................................................1-1
1.1 Scope ............................................................................................................................................ 1-1 1.2 Intended Audience ........................................................................................................................ 1-1 1.3 Change History.............................................................................................................................. 1-1
4 Engineering Guidelines...........................................................................................................4-1
4.1 RAN Sharing Function Switch....................................................................................................... 4-1 4.2 Mobility Control Switch.................................................................................................................. 4-1 4.3 Typical Networking Modes of RAN Sharing .................................................................................. 4-2 4.3.1 Coexistence of RNCs Under Full Coverage......................................................................... 4-2 4.3.2 Coexistence of Shared RNC and 2G Network ..................................................................... 4-2 4.3.3 Coexistence of Full and Partial Coverage for Different Operators ....................................... 4-3 4.3.4 Coexistence of Iu Flex and RAN Sharing............................................................................. 4-4 4.3.5 Coexistence of Multiple Operators ....................................................................................... 4-4 4.4 Hardware Configurations for RAN Sharing ................................................................................... 4-5 4.4.1 BTS3812E/BTS3812AE Configurations for RAN Sharing.................................................... 4-5 4.4.2 DBS3800 Configurations for RAN Sharing........................................................................... 4-6 4.4.3 BTS3900/BTS3900A Configurations for RAN Sharing......................................................... 4-8 4.4.4 DBS3900 Configurations for RAN Sharing........................................................................... 4-9
5 Parameters .................................................................................................................................5-1
Issue 01 (2010-03-30)
iii
Contents
iv
Issue 01 (2010-03-30)
1 Introduction
1 Introduction
1.1 Scope
This document describes the RAN Sharing feature. It covers the overview, technical description, engineering guidelines, and parameters related to the feature.
Document Issues
The document issues are as follows: 01 (2010-03-30) Draft (2009-12-05)
01 (2010-03-30)
This is the document for the first commercial release of RAN12.0. Compared with issue Draft (2009-12-05) of RAN12.0, this issue optimizes the description.
Draft (2009-12-05)
This is the draft of the document for RAN12.0. Compared with issue 02 (2009-06-30) of RAN11.0, this issue optimizes the description.
Issue 01 (2010-03-30)
1-1
RAN Sharing enables mobile operators to economize network deployment and raise network resource usage. This feature brings benefits for all parties involved in the Universal Mobile Telecommunications System (UMTS). Cost saving The driving force for operators to share networks is the substantial saving of CAPEX (capital expenditure) and OPEX (operating expenditure). Fast deployment RAN Sharing enables a fast deployment of the UMTS network through speeding up the network rollout and expanding the coverage area. Hardware complement
Issue 01 (2010-03-30)
2-1
RAN Sharing is an effective way to overcome such problems as shortage of sites or antennas, especially in areas of poor environmental conditions. Better service RAN Sharing frees operators from heavy workload of rolling out and operating networks. Therefore, operators can focus on end user services. RAN Sharing, however, also has some limitations. Reduced independence may lead to closer cooperation between operators and may impose some restrictions during capacity expansion.
2-2
Issue 01 (2010-03-30)
3 Technical Description
3 Technical Description
The following covers the following topics: RAN Sharing Functionality Flexible RNC Interfaces RAN Sharing License Management RAN Sharing OM Architecture
Issue 01 (2010-03-30)
3-1
3 Technical Description
The CBS information content is broadcast with a set of CBS SAs, and each CBS SA is composed of a set of cells. In the dedicated carrier shared RAN, the CBS SA is also operator dedicated, that is, the CBS SA of each operator can be composed of its own cells only. Therefore, the CBS is isolated between operators in the shared RAN. Furthermore, since each operator can deploy stand-alone CBS equipment, differentiated and independent service provision is also achievable.
3-2
Issue 01 (2010-03-30)
3 Technical Description
Optional Feature Intra-System Direct Retry Inter-System Direct Retry Inter-System Redirect Cell Broadcast Service AGPS Based LCS OTDOA Based LCS Hierarchical Cell Structure (HCS) Queuing and Pre-emption Inter-RAT Handover Based on Service Inter-RAT Handover Based on Load RAB Quality of Service Renegotiation over Iu LCS Classified Zones Iu Flex Iu Flex Load Distribution Management MBMS Function Adaptive Multi Rate Wide Band (AMR-WB) High Speed Downlink Packet Access High Speed Uplink Packet Access IP Transportation on Iub Interface Satellite Communication on Iub Interface IMS Signaling over HSPA HSDPA 13.976 Mbps per User HS-DPCCH Preamble support HSDPA over Iur SRB over HSDPA 2ms/10ms TTI Handover HSUPA 5.74 Mbps per User HSUPA over Iur SRB over HSUPA MBMS P2P over HSDPA PDCP Header Compression (RoHC)
Parameter Level Both RNC and cell Both RNC and cell RNC Both RNC and cell Both RNC and cell Both RNC and cell Both RNC and cell RNC Both RNC and cell Both RNC and cell RNC Operator Operator Operator Both RNC and cell Both RNC and cell Both RNC and cell Both RNC and cell NodeB NodeB RNC RNC RNC RNC RNC RNC RNC RNC RNC RNC RNC
Issue 01 (2010-03-30)
3-3
3 Technical Description
Optional Feature Active Queue Management (AQM) Inter Frequency Hard Handover Based on DL QoS 3G/2G Common Load Management Inter-RAT Handover Based on DL QoS Multi Frequency Band Networking Management 60 HSUPA Users per Cell MBMS Admission Enhancement MBMS 16 Channels per Cell MBMS Enhanced Broadcast Mode MBMS over Iur Separation of Transmission Resources for the Iub user plane Traffic Priority Mapping on Transport FP MUX BFD/ARP IP Re-route Overbooking on IP Transmission Dynamic Bandwidth Control of Iub IP CS voice over HSPA 96 HSDPA Users per Cell HSPA+ Downlink 21 Mbit/s Per User HSPA+ Downlink 28 Mbit/s Per User 96 HSUPA Users per Cell Enhanced CELL_FACH CPC-HS-SCCH Less Operation CPC-DTX/DRX Domain Specific Access Control (DSAC) Service Steering in RRC Connection Setup MOCN Introduction Package MSCH Scheduling
Parameter Level RNC RNC RNC RNC RNC Both RNC and cell Both RNC and cell Both RNC and cell RNC RNC RNC RNC RNC RNC RNC RNC RNC Both RNC and Cell RNC RNC Both RNC and Cell Cell RNC RNC Both RNC and Cell RNC RNC RNC
3-4
Issue 01 (2010-03-30)
3 Technical Description
3.2.1 Iu Interface
Typically, unchannelized STM-1/OC-3c optical ports on the UOIa board are used on the Iu interface. Because an operator can only use the operator's own CN nodes, each operator can use one or more optical ports to connect its own CN nodes. The physical bandwidth related to the physical ports is operator dedicated. In the shared RNC, a global CN identity is added to each CN node. The global CN identity consists of the PLMN-ID and the CN-ID. Figure 3-1 shows an example where the RNC is shared by operator A and operator B. Operator A uses Iu Flex, whereas operator B does not. Figure 3-1 Operator A and operator B share an RNC with operator A using Iu Flex
The switch to enable or disable Iu Flex is configurable for each operator, that is, the operator can individually enable or disable Iu Flex. The configuration of Iu Flex in the shared RNC is similar to that in the non-shared RNC. In the shared RNC, the configuration for the initial NAS message routing should be performed separately by each operator. The configuration is as follows: NRI length for the CS or PS domain. Mapping between NRI and global CN identity. Mapping between IMSI route value and global CN identity.
IMSI route value = (IMSI div 10) mod 1000. The value range is 0-999.
Issue 01 (2010-03-30)
3-5
3 Technical Description
3-6
Issue 01 (2010-03-30)
3 Technical Description
Transmission for the Iub User Plane The transmission resources for the Iub user plane can be shared or dedicated by operators, as shown in Figure 3-4. Figure 3-4 Separation of transmission resources for the Iub user plane
The parameter RscMngMode is used to control whether the transmission resources for the Iub user plane are separated or not. When separation of the transmission resources for the Iub user plane is enabled, the transmission resources for the Iub user plane can be configured into different Virtual Ports (VPs) or Logical Ports (LPs), as shown in Figure 3-5. The VP is for ATM and the LP is for IP. Each VP or LP is specified for an individual operator only. The VP and LP traffic shaping is supported. The admission control is based on a VP or an LP. RNC detects and resolves the transmission congestion through an individual operator. Otherwise, the transmission resources for the Iub user plane are totally shared by operators.
Issue 01 (2010-03-30)
3-7
3 Technical Description
When ATM/IP dual stack is adopted, there are two cases, as shown in Table 3-2. Table 3-2 Cases when ATM/IP dual stack is adopted Case Two operators engage two stacks respectively. Method
As shown in Figure 3-7, the Iur user plane is also shared. In ATM transport, all AAL2 paths are common resources of all operators and each AAL2 path can carry the traffic of all operators.
3-8
Issue 01 (2010-03-30)
3 Technical Description
Figure 3-7 Iur user plane of two RNCs shared by operators A and B
Issue 01 (2010-03-30)
3-9
3 Technical Description
Examples
Operators A and B use different frequencies. They share Channel Elements (CEs), which are jointly purchased by the two operators. In this case, the NodeB license has three groups: private group A, private group B, and common group. Private group A contains operator A's own frequency information. Similarly, private group B contains operator B's own frequency information. The common group defines the number of CEs.
3-10
Issue 01 (2010-03-30)
3 Technical Description
Operators A and B use different frequencies. Each operator purchases the CEs. The total number of CEs must not exceed the supported hardware capacity. In this case, the NodeB license defines two groups: private groups A and B. Each private group defines the operator's frequency information and number of CEs.
The shared master OSS is in charge of network management and OM functions. One of the operators or a third party is expected to operate the shared master OSS, which is up to the commercial agreement among operators. The shared master OSS provides the northbound interface for each operator's NMS and independent access to cell-level Fault Management (FM), PM, and CM for each operator. RAN Sharing Itf-N FM&PM&CM RAN Sharing enables different operators to access and perform operations on their dedicated or shared data through Itf-N. Itf-N refers to the northbound interface. The FM part of Itf-N is Common Object Request Broker Architecture (CORBA) interface. The PM and CM part of Ift-N is file interface. Itf-N is redesigned for RAN Sharing, as shown in Figure 3-9.
Issue 01 (2010-03-30)
3-11
3 Technical Description
Instance Set
Each operator has multiple managers, and all the managers of the different operators are connected to the M2000 on Itf-N. On Itf-N, all the managers of one operator have the same identity and the M2000 recognizes which operator the manager belongs to through the identity. The M2000 generates a specific type of IRP Agent instance for each manager, for example PMIRP Agent for a PM manager. All IRP instances with the same identity form an instance set. As shown in Figure 3-9, PMIRP, FMIRP, and CMIRP Agent instances of operator A constitute Instance set 1.
Authentication
The M2000 creates an account to authorize managers to connect with the shared master OSS through Itf-N. The account can be added, modified, deleted, or queried on the M2000. For detailed information, see the M2000 Online Help. When creating the account, an FTP account is automatically generated in order to transfer files on Itf-N PM&CM.
3-12
Issue 01 (2010-03-30)
3 Technical Description
Issue 01 (2010-03-30)
3-13
4 Engineering Guidelines
4 Engineering Guidelines
The following describes RAN Sharing function switch, mobile control switch, typical networking modes, and hardware configurations.
Issue 01 (2010-03-30)
4-1
4 Engineering Guidelines
The intra-frequency and inter-frequency neighboring cell relations between different operators can be configured only when the switch of InterPlmnHoAllowedIntraRat is set to YES. . The intra-frequency and inter-frequency neighboring cell relations between different operators can be configured only when the switch of InterPlmnHoAllowedInterRat is set to YES. .
4-2
Issue 01 (2010-03-30)
4 Engineering Guidelines
Issue 01 (2010-03-30)
4-3
4 Engineering Guidelines
4-4
Issue 01 (2010-03-30)
4 Engineering Guidelines
Issue 01 (2010-03-30)
4-5
4 Engineering Guidelines
RF Subrack Baseband Subrack MTRU: 6 MAFU: 6 HBBI: 2 HULP: 2 HDLP: 1 NMPT: 1 NUTI: 1 to 3
Remarks One sector uses two PAs. A pair of frequencies in the same PA must be two consecutive frequencies within 10 MHz. The frequencies in different PAs can be inconsecutive.
Maximum configuration
MTRU: 6 MAFU: 6
NOTE: The 3 x 4 configuration is available for macro NodeBs from RAN 6.0. Baseband capacity increases with the baseband board expansion. The total number of CE licenses cannot exceed the baseband capacity.
Table 4-2 describes the configurations in a single cabinet available for operator A and operator B in RAN Sharing solution. The number of baseband boards is configured to meet the requirements of operators that share the RAN. Table 4-2 Single cabinet configurations available for operator A and operator B Configuration 3x2 MTRU: 3 MAFU: 3 MTRU: 6 MAFU: 6 3x4 MTRU: 6 MAFU: 6 3x1 3x2 3x3 3x3 3x2 3x1 One sector uses two PAs. A pair of frequencies in the same PA must be two consecutive frequencies within 10 MHz. The frequencies in different PAs can be inconsecutive. 3x1 3x1 Operator A 3x1 Operator B 3x1 Remarks A pair of frequencies in the same sector must be two consecutive frequencies within 10 MHz.
4-6
Issue 01 (2010-03-30)
4 Engineering Guidelines
Table 4-3 DBS3800 configurations Configuration 3x2 Modules RRU: 3 BBU: 2 Diagram Capacity UL: 384 CE DL: 512 CE Remarks The pair f1, f2 must be two consecutive frequencies within 10 MHz.
RRU: 6 BBU: 2
3x4
RRU: 6 BBU: 2
UL:768 CE
The pair f1, f2 must DL:1024 CE be two consecutive frequencies within 10 MHz. The pair f3, f4 must be two consecutive frequencies within 10 MHz. There is no limit to the continuity of the pair f1, f2 and the pair f3, f4.
Table 4-4 describes the configurations available for operator A and operator B when RAN Sharing is applied. Table 4-4 Single cabinet configurations available for operator A and operator B Configuration 3x2 RRU: 3 BBU: 2 RRU: 6 BBU: 2 3x4 RRU: 6 BBU: 2 3x1 3x2 3x3 3x3 3x2 3x1 The pair f1, f2 must be two consecutive frequencies within 10 MHz. The pair f3, f4 must be two consecutive frequencies within 10 MHz. There is no limit to the continuity of the pair f1, f2 and the pair f3, f4. 3x1 3x1 Operator A 3x1 Operator B 3x1 Remarks The pair f1, f2 must be two consecutive frequencies within 10 MHz.
Issue 01 (2010-03-30)
4-7
4 Engineering Guidelines
Remarks -
Table 4-6 describes the configurations in a single cabinet available for operator A and operator B in RAN Sharing solution. The number of baseband boards is configured to meet the requirements of operators that share the RAN. Table 4-6 Single cabinet configurations available for operator A and operator B Configuration 3x2 WRFU-40W2C: 3 WRFU-80W4C: 6 3x4 WRFU-80W4C: 3 Operator A 3x1 3x1 3x1 3x2 3x3 WRFU-80W4C: 6 3x1 3x2 3x3 Operator B 3x1 3x1 3x3 3x2 3x1 3x3 3x2 3x1 Remarks -
4-8
Issue 01 (2010-03-30)
4 Engineering Guidelines
Maximum configuration
RRU3804: 6
3x4
Minimum configuration
RRU3804: 3
Maximum configuration
RRU3804: 6
NOTE:
Baseband capacity increases with the baseband board expansion. The total number of CE licenses cannot exceed the baseband capacity. The BBU and the RRU support ring topology. When a link is faulty, the service on the link is automatically switched over to another link.
Table 4-8 describes the configurations in a single cabinet available for operator A and operator B in RAN Sharing solution. The number of baseband boards is configured to meet the requirements of operators that share the RAN.
Issue 01 (2010-03-30)
4-9
4 Engineering Guidelines
Table 4-8 Single cabinet configurations available for operator A and operator B Configuration 3x2 RRU3804: 3 RRU3804: 6 3x4 RRU3804: 3 Operator A 3x1 3x1 3x1 3x2 3x3 RRU3804: 6 3x1 3x2 3x3 Operator B 3x1 3x1 3x3 3x2 3x1 3x3 3x2 3x1 Remarks -
4-10
Issue 01 (2010-03-30)
5 Parameters
5 Parameters
Table 5-1 Parameter description Parameter ID NE MML Description
SET Meaning: This parameter specifies whether UOPERATORSHARIN inter-RAT handover of the UE among different GMODE(Optional) operators is allowed. GUI Value Range: NO, YES Actual Value Range: NO, YES Unit: None Default Value: YES
SET Meaning: This parameter specifies whether UOPERATORSHARIN intra-RAT handover of the UE among different GMODE(Optional) operators is allowed. GUI Value Range: NO, YES Actual Value Range: NO, YES Unit: None Default Value: YES
OperatorType
BSC6900
ADD Meaning: Identity Operator Type,as follows: UCNOPERATOR(Man Primary operator: Each RAN system has only one datory) primary operator. The primary operator owns all MOD or part of the resources of the RAN system. The UCNOPERATOR(Man license of the primary operator controls the datory) features and functions supported by the RAN system. Secondary operator: Each RAN system can have a maximum of three secondary operators. A secondary operator owns part of the resources of the RAN system. The license of the secondary operator controls the functions and features supported by the secondary operator. Outer Operator: In order to support mobility between two RNCs, we define the operator switched over to the target RNC as an outer operator. The outer operator is not a primary or secondary operator of the source RNC. Common operator: PLMN-id indicated in the system broadcast information as defined for conventional networks, which non-supporting UEs understand as the serving operator. If there are multiple operators in the operator group to which the cell belongs, you are advised to configure the operators as common operators. GUI Value Range: PRIM(Primary Operator), SEC(Secondary Operator), OUTER(Outer Operator), COMM(Common Operator) Actual Value Range: PRIM, SEC, OUTER, COMM Unit: None
Issue 01 (2010-03-30)
5-1
5 Parameters
Default Value: None RANSharingSup BSC6900 port SET Meaning: When RAN Sharing Supported, RNC UOPERATORSHARIN can configure multi-plmn. GMODE(Optional) GUI Value Range: NO, YES Actual Value Range: NO, YES Unit: None Default Value: NO ADD UNODEB(Optional) MOD UNODEB(Optional) Meaning: Indicating the resource management mode GUI Value Range: SHARE(Share), EXCLUSIVE(Exclusive) Actual Value Range: SHARE, EXCLUSIVE Unit: None Default Value: SHARE
RscMngMode
BSC6900
5-2
Issue 01 (2010-03-30)
6 Counters
6 Counters
For details, see the BSC6900 UMTS Performance Counter Reference.
Issue 01 (2010-03-30)
6-1
7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see the Glossary.
Issue 01 (2010-03-30)
7-1
8 Reference Documents
8 Reference Documents
[1] 3GPP TS 23.251: Network Sharing Architecture and Functional Description [2] 3GPP TR 23.851: Network Sharing Architecture and Functional Description [3] 3GPP TS 23.236: Intra-domain Connection of RAN Nodes to Multiple CN Nodes [4] 3GPP TR 22.951: Service Aspects and Requirements for Network Sharing [5] BSC6900 UMTS Performance Counter Reference
Issue 01 (2010-03-30)
8-1