I hspa rel-1_feature_description

I-HSPA Release 1 FeatureDescriptions

DN70500287Issue 1-1 en09/09/2008

# Nokia Siemens Networks 1 (329)

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (329) # Nokia Siemens Networks DN70500287Issue 1-1 en09/09/2008

I-HSPA Release 1 Feature Descriptions

Contents

Contents 3

Summary of changes 15

1 Introduction 17

2 General functionality 192.1 IHSW-101: Optimized Network Architecture for the PS Traffic 192.1.1 Introduction 192.1.2 Functional description 202.1.3 System impact 222.1.3.1 Interdependencies between features 222.1.3.2 Software dependencies 222.1.3.3 Software sales information 232.1.3.4 Management plane 232.2 IHSW-102: Support for Standard Compliant Terminals 232.2.1 Introduction 232.2.2 Functional description 242.2.3 System impact 242.2.3.1 Interdependencies between features 242.2.3.2 Software dependencies 242.2.3.3 Software sales information 242.2.3.4 Management plane 252.3 IHSW-105: Optimized Radio Interface in I-HSPA 252.3.1 Introduction 252.3.2 Functional description 252.3.3 System impact 292.3.3.1 Interdependencies between features 292.3.3.2 Software dependencies 292.3.3.3 Software sales information 302.3.3.4 Management plane 302.4 IHSW-103: Optimized User Plane and Round Trip Time (RTT) for PS 302.4.1 Introduction 302.4.2 Functional description 312.4.3 System impact 312.4.3.1 Interdependencies between features 312.4.3.2 Software dependencies: 312.4.3.3 Software sales information 322.4.3.4 Management plane 322.5 IHSW-104: Optimized Control Plane and Connection Set-up Time 322.5.1 Introduction 322.5.2 Functional description 332.5.3 System impact 332.5.3.1 Interdependencies between features 332.5.3.2 Software dependencies 332.5.3.3 Software sales information 342.5.3.4 Management plane 34

DN70500287Issue 1-1 en09/09/2008


Contents

3 Radio resource management and telecom 373.1 Mobility management 373.1.1 IHSW-26: I-HSPA Intra System Mobility Based on Hard Handover (No

Iur) 373.1.1.1 Introduction 373.1.1.2 Functional description 373.1.1.3 System impact 383.1.2 IHSW-9: Intra-System Handover 393.1.2.1 Introduction 393.1.2.2 Functional description 393.1.2.3 System impact 403.1.3 IHSW-14: 2G/3G Inter-System Handover 443.1.3.1 Introduction 443.1.3.2 Functional description 443.1.3.3 System impact 443.1.4 ARAN970: HSUPA Handover 513.1.4.1 Introduction 513.1.4.2 Functional description 513.1.4.3 System impact 513.2 Voice 543.2.1 IHSW-31: I-HSPA CS Service Enabling Handover 543.2.1.1 Introduction 543.2.1.2 Functional description 543.2.1.3 System impact 553.2.2 IHSW-50: VoIP 583.2.2.1 Introduction 583.2.2.2 Functional description 583.2.2.3 System impact 593.3 Quality of Service 603.3.1 IHSW-10: QoS for IP Transport 603.3.1.1 Introduction 603.3.1.2 Functional description 603.3.1.3 System impact 603.4 Capacity and efficiency 643.4.1 ARAN834: Flexible Iu 643.4.1.1 Introduction 643.4.1.2 Functional description 643.4.1.3 System impact 653.4.2 ARAN242: Flexible Upgrade of NRT DCH Data Rate 673.4.2.1 Introduction 673.4.2.2 Functional description 673.4.2.3 System impact 673.4.3 ARAN409: Throughput-based Optimization of the Packet Scheduler

Algorithm 713.4.3.1 Introduction 713.4.3.2 Functional description 713.4.3.3 System impact 723.4.4 ARAN146: Power Balancing 793.4.4.1 Introduction 793.4.4.2 Functional description 793.4.4.3 System impact 813.4.5 IHSW-8: RRC States and State Transitions 83



3.4.5.1 Introduction 833.4.5.2 Functional description 833.4.5.3 System impact 853.4.6 ARAN2.0107: RRC Connection Re-establishment 873.4.6.1 Functional description 873.4.6.2 System impact 873.5 Location services 883.5.1 ARAN2.0041: LCS - Cell Coverage-Based (RTT) with Geographical

Coordinates 883.5.1.1 Introduction 883.5.1.2 Functional description 893.5.1.3 System impact 903.5.2 ARAN223: UE-Based A-GPS Using External Reference Network 953.5.2.1 Introduction 953.5.2.2 Functional description 973.5.2.3 System impact 983.5.3 ARAN815: Point-to-Point Iu-PC Interface 1013.5.3.1 Introduction 1013.5.3.2 Functional description 1013.5.3.3 System impact 1023.5.4 ARAN1219: Latency Statistics for UE Positioning 1033.5.4.1 Introduction 1033.5.4.2 Functional description 1033.5.4.3 System impact 1033.6 Radio Access Bearer combinations 1063.6.1 ARAN1.010: DCH UL NRT PS Data Bearer Package for I-HSPA 1063.6.1.1 Functional description 1063.6.1.2 System impact 1073.7 HSDPA 1083.7.1 ARAN763: Basic HSDPA with QPSK and 5 Codes 1083.7.1.1 Introduction 1083.7.1.2 Functional description 1093.7.1.3 System impact 1103.7.2 ARAN233: HSDPA Associated Uplink DPCH Scheduling 1183.7.2.1 Introduction 1183.7.2.2 Functional description 1183.7.2.3 System impact 1213.7.3 RAN764: HSDPA 16QAM Support 1223.7.3.1 Introduction 1223.7.3.2 Functional description 1223.7.3.3 System impact 1233.7.4 ARAN839: HSDPA 16 Users per Cell 1243.7.4.1 Introduction 1243.7.4.2 Functional description 1243.7.4.3 System impact 1243.7.5 ARAN1033: HSDPA 48 Users per Cell 1253.7.5.1 Introduction 1253.7.5.2 Functional description 1263.7.5.3 System impact 1263.7.6 ARAN852: HSDPA 10 and 15 Codes 1273.7.6.1 Introduction 1273.7.6.2 Functional description 128

DN70500287Issue 1-1 en09/09/2008


Contents

3.7.6.3 System impact 1283.7.7 ARAN853: HSDPA Code Multiplexing 1313.7.7.1 Introduction 1313.7.7.2 Functional description 1313.7.7.3 System impact 1323.7.8 ARAN312: HSDPA Dynamic Resource Allocation 1333.7.8.1 Introduction 1333.7.8.2 Functional description 1343.7.8.3 System impact 1353.8 HSUPA 1363.8.1 ARAN826: Basic HSUPA 1363.8.1.1 Introduction 1363.8.1.2 Functional description 1373.8.1.3 System impact 1383.8.2 ARAN973: HSUPA Basic RRM 1473.8.2.1 Introduction 1473.8.2.2 Functional description 1503.8.2.3 System impact 1503.9 Supplementary RRM and telecom features 1513.9.1 ARAN1.020: Encryption and Integrity Protection 1513.9.1.1 Functional description 1513.9.1.2 System impact 1523.9.2 IHSW-150: I-HSPA Adapter Frequency Variants 1533.9.2.1 Introduction 1533.9.2.2 Functional description 1533.9.2.3 System impact 153

4 Transmission and transport 1554.1 IP transport 1554.1.1 IHSW-60: I-HSPA Transport Over IP 1554.1.1.1 Introduction 1554.1.1.2 Functional description 1554.1.1.3 System impact 1564.1.2 ARAN165: IP-based Control and User Planes at Iu-PS and Iur 1574.1.2.1 Introduction 1574.1.2.2 Functional description 1574.1.2.3 System impact 1574.1.3 IHSW-29: IP-based Control Plane for IuCS 1594.1.3.1 Introduction 1594.1.3.2 Functional description 1594.1.3.3 System impact 1594.2 IP transport security 1604.2.1 IHSW-25: Transport Security Ciphering and Integrity Protection 1604.2.1.1 Introduction 1604.2.1.2 Functional description 1604.2.1.3 System impact 1614.2.2 IHSW-24: Secured Iu User Plane Transport 1624.2.2.1 Introduction 1624.2.2.2 Functional description 1624.2.2.3 System impact 1624.2.3 IHSW-20: Secured Iu Control Plane Transport 1634.2.3.1 Introduction 163



4.2.3.2 Functional description 1644.2.3.3 System impact 1644.2.4 IHSW-32: Secured O&M Traffic Transport 1654.2.4.1 Introduction 1654.2.4.2 Functional description 1654.2.4.3 System impact 1654.2.5 IHSW-90: Support for Infrastructure for Certification Authority (CA) 1664.2.5.1 Introduction 1664.2.5.2 Functional description 1674.2.5.3 System impact 1674.3 BTS and I-HSPA Adapter transport interfaces 1684.3.1 ARAN940: E1 Interface for Flexi WCDMA BTS 1684.3.1.1 Functional description 1684.3.1.2 System impact 1694.3.2 IHSW-75: ATM Transmission Convergence for E1 1704.3.2.1 Introduction 1704.3.2.2 Functional description 1714.3.2.3 System impact 1714.3.3 ARAN941: JT1 Interface for Flexi WCDMA BTS 1724.3.3.1 Functional description 1724.3.3.2 System impact 1734.3.4 ARAN946: T1 Interface for Flexi WCDMA BTS 1744.3.4.1 Functional description 1744.3.4.2 System impact 1754.3.5 IHSW-76: ATM Transmission Convergence for T1, JT1 1764.3.5.1 Introduction 1764.3.5.2 Functional description 1764.3.5.3 System impact 1774.3.6 ARAN942: SDH STM-1 Interface for Flexi WCDMA BTS 1784.3.6.1 Introduction 1784.3.6.2 Functional description 1784.3.6.3 System impact 1794.3.7 IHSW-77: ATM Transmission Convergence for STM-1 1804.3.7.1 Introduction 1804.3.7.2 Functional description 1804.3.7.3 System impact 1804.3.8 ARAN939: BTS Flexbus Interface 1814.3.8.1 Functional description 1814.3.8.2 System impact 1824.3.9 RAN1062: IMA (Flexi WCDMA BTS) 1834.3.9.1 Introduction 1834.3.9.2 Functional description 1844.3.9.3 System impact 1844.3.10 IHSW-701: 2xFE + 1xGE + 4xE1/T1/JT1 (symm.) FlexiBTS Transport

Sub-module FTIA 1854.3.10.1 Introduction 1854.3.10.2 Functional description 1854.3.10.3 System impact 1854.4 Supplementary transport features 1864.4.1 ARAN944: Use of GSM Transmission (Flexi WCDMA BTS) 1864.4.1.1 Introduction 1864.4.1.2 Functional description 186

DN70500287Issue 1-1 en09/09/2008


Contents

4.4.1.3 System impact 1864.4.2 IHSW-33: Ethernet Transport 1874.4.2.1 Introduction 1874.4.2.2 Functional description 1884.4.2.3 System impact 1884.4.3 IHSW-70: I-HSPA Additional L1 and L2 Transport Options 1894.4.3.1 Introduction 1894.4.3.2 Functional description 1894.4.3.3 System impact 189

5 Operability 1915.1 Operability architecture 1915.1.1 IHSW-3712: I-HSPA Operability Solution 1915.1.1.1 Introduction 1915.1.1.2 Functional description 1915.1.1.3 System impact 1935.2 ARAN1.051: Alarm System 1955.2.1 Functional description 1955.2.2 System impact 1955.2.2.1 Interdependencies between features 1955.2.2.2 Software dependencies 1965.2.2.3 Software sales information 1965.2.2.4 Management plane 1965.3 Configuration management 1975.3.1 IHSW-3698: Configuration Management with NetAct 1975.3.1.1 Introduction 1975.3.1.2 Functional description 1975.3.1.3 System impact 1985.3.2 ARAN801: Radio Network Access Regulation Function 1995.3.2.1 Introduction 1995.3.2.2 Functional description 1995.3.2.3 System impact 2005.3.3 ARAN2.0058: RNW Configuration Event Management 2035.3.3.1 Functional description 2035.3.3.2 System impact 2035.4 DCN architecture for O&M 2045.4.1 ARAN1.040: DCN Architecture for O&M 2045.4.1.1 Functional description 2045.4.1.2 System impact 2065.4.2 ARAN2.0065: DHCP Server for BTS Site Devices 2075.4.2.1 Functional description 2075.4.2.2 System impact 2075.5 ARAN1.041: Graphical User Interface 2085.5.1 Functional description 2085.5.2 System impact 2095.5.2.1 Interdependencies between features 2095.5.2.2 Software dependencies 2095.5.2.3 Software sales information 2105.5.2.4 Management plane 2105.6 License and option management 2115.6.1 ARAN172: License Management with NetAct 2115.6.1.1 Functional description 211



5.6.1.2 System impact 2115.6.2 ARAN804: Centralized Pool License Management in NetAct 2125.6.2.1 Introduction 2125.6.2.2 Functional description 2135.6.2.3 System impact 2135.7 Maintenance and diagnostics 2145.7.1 ARAN1.048: Radio Network Recovery 2145.7.1.1 Functional description 2145.7.1.2 System impact 2155.7.2 ARAN1.049: Resets and Initializations 2165.7.2.1 Functional description 2165.7.2.2 System impact 2165.7.3 ARAN1.050: I-HSPA Adapter Computing Platform System

Maintenance 2185.7.3.1 Functional description 2185.7.3.2 System impact 2185.7.4 ARAN1161: Alarms for PM Measurement Data Transfer Failures 2205.7.4.1 Introduction 2205.7.4.2 Functional description 2205.7.4.3 System impact 2215.7.5 ARAN1.5053: BTS Testing Functions 2225.7.5.1 Functional description 2225.7.5.2 System impact 2235.7.6 ARAN2.0044: Intelligent BTS Shutdown with BBU Unit 2245.7.6.1 Functional description 2245.7.6.2 System impact 2255.8 O&M security 2265.8.1 ARAN812: Local User Authentication for BTS 2265.8.1.1 Introduction 2265.8.1.2 Functional description 2265.8.1.3 System impact 2265.8.2 ARAN618: Centralized User Information Management for BTS 2275.8.2.1 Introduction 2275.8.2.2 Functional description 2285.8.2.3 System impact 2295.8.3 ARAN1159: IP Address and Port-Based Filtering for BTS LMPs 2305.8.3.1 Introduction 2305.8.3.2 Functional description 2305.8.3.3 System impact 2315.8.4 ARAN33: IP Security for O&M Traffic Between OMS and NetAct 2325.8.4.1 Introduction 2325.8.4.2 Functional description 2335.8.4.3 System impact 2335.8.5 ARAN181: Remote User Information Management for I-HSPA

Adapter 2355.8.5.1 Introduction 2355.8.5.2 Functional description 2355.8.5.3 System impact 2355.8.6 ARAN895: Secure Port Configuration in NetAct Firewall 2365.8.6.1 Introduction 2365.8.6.2 Functional description 2375.8.6.3 System impact 237

DN70500287Issue 1-1 en09/09/2008


Contents

5.9 RNW integration 2385.9.1 ARAN1.043: Radio Network Integration 2385.9.1.1 Functional description 2385.9.1.2 System impact 2385.10 SW management 2405.10.1 IHSW-3695: SW Management with NetAct 2405.10.1.1 Functional description 2405.10.1.2 System impact 2405.11 Topology management 2415.11.1 IHSW-3696: Topology Management with NetAct 2415.11.1.1 Functional description 2415.11.1.2 System impact 2425.12 BTS related O&M features 2435.12.1 ARAN2.0048: Nokia Siemens Networks RealTilt 2435.12.1.1 Introduction 2435.12.1.2 Functional description 2435.12.1.3 System impact 2445.13 Supplementary operability features 2455.13.1 ARAN1.5028: Combined GSM and WCDMA Management 2455.13.1.1 Functional description 2455.13.1.2 System impact 246

6 Performance monitoring 2496.1 ARAN1.052: Radio Network Monitoring Statistics 2496.1.1 Introduction 2496.1.2 Functional description 2496.1.3 System impact 2506.1.3.1 Interdependencies between features 2506.1.3.2 Software dependencies 2506.1.3.3 Software sales information 2506.1.3.4 Management plane 2516.2 ARAN1163: Iu-PS Throughput Measurement for GTP Traffic 2516.2.1 Introduction 2516.2.2 Functional description 2516.2.3 System impact 2526.2.3.1 Interdependencies between features 2526.2.3.2 Software dependencies 2526.2.3.3 Software sales information 2526.2.3.4 Management plane 2526.3 ARAN234: I-HSPA Subscriber Trace 2556.3.1 Introduction 2556.3.2 Functional description 2556.3.3 System impact 2576.3.3.1 Interdependencies between features 2576.3.3.2 Software dependencies 2576.3.3.3 Software sales information 2586.3.3.4 Management plane 2586.4 ARAN2.0026: KPI Calculations in OMS for I-HSPA 2586.4.1 Introduction 2586.4.2 Functional description 2596.4.3 System impact 2596.4.3.1 Interdependencies between features 259



6.4.3.2 Software dependencies 2596.4.3.3 Software sales information 2596.4.3.4 Management plane 2606.5 ARAN2.0027: Threshold-based PM Notification Triggering 2606.5.1 Introduction 2606.5.2 Functional description 2606.5.3 System impact 2616.5.3.1 Interdependencies between features 2616.5.3.2 Software dependencies 2616.5.3.3 Software sales information 2616.5.3.4 Management plane 2626.6 ARAN189: Automatic Definition of Neighboring Cells 2626.6.1 Introduction 2626.6.2 Functional description 2636.6.3 System impact 2646.6.3.1 Software dependencies 2646.6.3.2 Software sales information 2656.6.3.3 Management plane 2656.7 IHSW-23: KPI Support in I-HSPA Adapter 2656.7.1 Introduction 2656.7.2 Functional description 2666.7.3 System impact 2666.7.3.1 Interdependencies between features 2666.7.3.2 Software dependencies 2666.7.3.3 Software sales information 2666.7.3.4 Management plane 2676.8 ARAN232: CPICH Ec/No Coverage Measurements and Optimization 2676.8.1 Introduction 2676.8.2 Functional description 2676.8.3 System impact 2696.8.3.1 Interdependencies between features 2696.8.3.2 Software dependencies 2696.8.3.3 Software sales information 2696.8.3.4 Management plane 269

7 Adapter solution 2717.1 IHSW-1: I-HSPA Rel. 1 Operational SW with Capacity Step 1 2717.1.1 Introduction 2717.1.2 Functional description 2717.1.3 System impact 2717.1.3.1 Interdependencies between features 2717.1.3.2 Software dependencies 2717.1.3.3 Software sales information 2727.1.3.4 Management plane 2727.2 IHSW-2: I-HSPA Capacity Step 2 2727.2.1 Introduction 2727.2.2 Functional description 2737.2.3 System impact 2737.2.3.1 Interdependencies between features 2737.2.3.2 Software dependencies 2737.2.3.3 Software sales information 2737.2.3.4 Management plane 274

DN70500287Issue 1-1 en09/09/2008


Contents

7.3 IHSW-3: I-HSPA Capacity Step 3 2747.3.1 Introduction 2747.3.2 Functional description 2747.3.3 System impact 2747.3.3.1 Interdependencies between features 2747.3.3.2 Software dependencies 2747.3.3.3 Software sales information 2757.3.3.4 Management plane 275

8 BTS solution 2778.1 Frequency variants 2778.1.1 ARAN999: Flexi WCDMA BTS 1700/2100 2778.1.1.1 Functional description 2778.1.1.2 System impact 2778.1.2 ARAN914: Flexi WCDMA BTS 1900 2798.1.2.1 Introduction 2798.1.2.2 Functional description 2798.1.2.3 System impact 2798.1.3 ARAN917: Flexi WCDMA BTS 850 2818.1.3.1 Introduction 2818.1.3.2 Functional description 2818.1.3.3 System impact 2818.1.4 ARAN916: Flexi WCDMA BTS 900 2838.1.4.1 Introduction 2838.1.4.2 Functional description 2838.1.4.3 System impact 2838.1.5 ARAN1221: Flexi WCDMA BTS 2000 2858.1.5.1 Introduction 2858.1.5.2 Functional description 2858.1.5.3 System impact 2858.2 Synchronization 2878.2.1 IHSW-7: External Synchronization Support 2878.2.1.1 Introduction 2878.2.1.2 Functional description 2878.2.1.3 System impact 2878.2.2 ARAN943: Synchronizing WCDMA RAN (Flexi WCDMA BTS) 2888.2.2.1 Functional description 2888.2.2.2 System impact 2898.2.3 ARAN1222: Support for External GPS Synchronization in Flexi BTS 2908.2.3.1 Functional description 2908.2.3.2 System impact 2918.3 BTS scheduler 2928.3.1 ARAN869: HSDPA BTS Packet Scheduler 2928.3.1.1 Introduction 2928.3.1.2 Functional description 2928.3.1.3 System impact 2938.3.2 RAN849: HSDPA Proportional Fair Resource Packet Scheduler 2948.3.2.1 Introduction 2948.3.2.2 Functional description 2948.3.2.3 System impact 2958.3.3 RAN1034: Shared HSDPA Scheduler for Baseband Efficiency 2968.3.3.1 Introduction 296



8.3.3.2 Functional description 2978.3.3.3 System impact 2988.3.4 ARAN968: HSUPA BTS Packet Scheduler 2998.3.4.1 Introduction 2998.3.4.2 Functional description 2998.3.4.3 System impact 3008.4 MHA and antenna 3018.4.1 ARAN908: Flexi WCDMA BTS AISG MHA Support 3018.4.1.1 Introduction 3018.4.1.2 Functional description 3018.4.1.3 System impact 3018.4.2 ARAN907: Antenna Line Supervision 3028.4.2.1 Introduction 3028.4.2.2 Functional description 3038.4.2.3 System impact 3038.4.3 RAN1046: Feederless Site Solution for Flexi WCDMA BTS 3048.4.3.1 Introduction 3048.4.3.2 Functional description 3048.4.3.3 System impact 3048.4.4 ARAN905: Flexi WCDMA BTS Nokia Siemens Networks MHA

Support 3058.4.4.1 Introduction 3058.4.4.2 Functional description 3068.4.4.3 System impact 3068.4.5 ARAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support 3078.4.5.1 Introduction 3078.4.5.2 Functional description 3078.4.5.3 System impact 3078.4.6 ARAN1223: Flexi WCDMA BTS Mast Head RF Module 2.1 20 W 3088.4.6.1 Functional description 3088.4.6.2 System impact 3098.4.7 ARAN1079: Sameband Combiner for Flexi WCDMA BTS 850 MHz (Tx

Carrier Combiner for Dual Duplex Support) 3108.4.7.1 Introduction 3108.4.7.2 Functional description 3108.4.7.3 System impact 3118.4.8 ARAN1139: Sameband Combiner for Flexi WCDMA BTS 900 MHz (Tx

Carrier Combiner for Dual Duplex Support) 3128.4.8.1 Introduction 3128.4.8.2 Functional description 3128.4.8.3 System impact 3128.4.9 ARAN1462: Sameband Combiner for Flexi WCDMA BTS 2100MHz (Tx

Carrier Combiner for Dual Duplex Support) 3138.4.9.1 Introduction 3138.4.9.2 Functional description 3148.4.9.3 System impact 3148.5 Supplementary BTS solution 3158.5.1 ARAN912: License-based BTS Channel Capacity 3158.5.1.1 Functional description 3158.5.1.2 System impact 3158.5.2 ARAN1000: Baseband Extension for Flexi WCDMA BTS 3168.5.2.1 Introduction 316

DN70500287Issue 1-1 en09/09/2008


Contents

8.5.2.2 Functional description 3178.5.2.3 System impact 3178.5.3 ARAN1002: Flexi WCDMA BTS 40 W Carrier Power Support 3188.5.3.1 Introduction 3188.5.3.2 Functional description 3188.5.3.3 System impact 3188.5.4 ARAN1144: Flexi WCDMA BTS 8 W RF Power Limitation 3198.5.4.1 Introduction 3198.5.4.2 Functional description 3198.5.4.3 System impact 3208.5.5 ARAN1145: Flexi WCDMA BTS RF Module with AC Input Power 3218.5.5.1 Introduction 3218.5.5.2 System impact 3218.5.6 ARAN1146: Flexi WCDMA BTS Horizontal Mounting Kit for GSM EDGE

BTS 3228.5.6.1 Introduction 3228.5.6.2 Functional description 3228.5.6.3 System impact 3228.5.7 RAN1093: HSDPA 16QAM SW License Support 3238.5.7.1 Introduction 3238.5.7.2 Functional description 3248.5.7.3 System impact 3248.5.8 ARAN1127: Extended Cell (180 km) 3258.5.8.1 Introduction 3258.5.8.2 Functional description 3258.5.8.3 System impact 3258.6 ARAN900: Flexi WCDMA BTS 3278.6.1 Functional description 3278.6.2 System impact 3278.6.2.1 Interdependencies between features 3278.6.2.2 Software dependencies 3288.6.2.3 Software sales information 3288.6.2.4 Management plane 328



Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes between issues 1-0 and 1-1

The Introduction has been updated with information on the required I-HSPA specific radio access and core network features.

The following features have been removed from Release 1, thereforethese sections have also been removed from the documentation:

. Feature IHSW-22 Handover Between Satellite System and I-HSPA

. Feature IHSW-21 Emergency VoIP

. Feature ARAN132 Robust Header Compression for the Air Interface

. Feature ARAN1176 Flexi WCDMA BTS Mast Head RF Module 1.7/2.1 20W

. Feature ARAN1282 Flexi WCDMA BTS Mast Head RF Module 40 WCarrier Power Support

Feature ARAN312 HSDPA Dynamic Resource Allocation has been movedto chapter HSDPA.

The section on feature IHSW-31 CS Service Enabling Handover has beenupdated with a link to the activation manual of this feature.

Changes for issue 1-0

This document replaces I-HSPA Features Under Development(DN70420035).

The following features have been removed from Release 1, thereforethese sections have also been removed from the documentation:

DN70500287Issue 1-1 en09/09/2008


Summary of changes

. Feature IHSW-11 Pre-emption

. Feature IHSW-13 RAB Modification

. Feature ARAN656 WCEL Lock and Unlock from NetAct

. Feature ARAN1047 Flexi WCDMA BTS 1700 and 1800

New sections have been added on the following features:

. Feature IHSW-701 2xFE + 1xGE + 4xE1/T1/JT1 (symm.) FlexiBTSTransport Sub-module FTIA

. Feature ARAN1145 Flexi WCDMA BTS RF Module with AC InputPower

. Feature ARAN1462 Sameband Combiner for Flexi WCDMA BTS2100MHz (Tx Carrier Combiner for Dual Duplex Support)



1 Introduction

This Feature Description documentation provides the list of features beingdeveloped for I-HSPA Release 1.

The documentation covers the radio access network features in detail. Themost essential I-HSPA specific radio access and core network features areas follows:

MSS (Minimum M13, M14.2 SW and HW recommended):

. Iu-CS interface (Required only for CS interworking)

. Feature 50035: SS7 MTP3-User Adaptation Layer (M3UA),SIGTRAN support over Ethernet

. Feature 1325: RANAP and BSSAP in MSC Server (SRNSRelocation)

. Feature 1260 Inter-system handover and UMTS changes in MSC

Combi SGSN (SG6 CD6):

. Feature SG01142: I-HSPA Enhancement

. Feature SG02017: Direct tunnel

. Feature SG01119: Iu over IP

. Feature SG01161: SRNS Relocation

. Feature SG01113: SG6 HSUPA Support 1M-1.5M

. Feature SG01113: SG6 HSUPA Support 1.5-2M

. Feature SG01113: SG6 HSUPA Support 2M-6M

. Feature SG01113: SG6 HSUPA Support 6M-8M

. Feature SG02104: SG6 HSDPA Support 2M-4M

. Feature SG02104: SG6 HSDPA Support 8M-12M

DN70500287Issue 1-1 en09/09/2008


Introduction

GGSN (FI3.2 PCD2.2):

To enable high user bit-rates (>2 Mbps) the following features are neededin the Flexi ISN:

. FISNFI30HSD - FI30 HSPA Support 2 to 8 Mbps: With the HSPAfeature support the Flexi ISN allows the use of bit rates above 2Mbps and up to 8 Mbps for downlink (HSDPA) and uplink (HSUPA).The basic GGSN feature includes HSPA support for bit rates up to 2Mbps.

. FISNFI30H16 - FI30 HSDPA Support for up to 16 Mbps: With theHSDPA feature support the Flexi ISN allows the use of bit rates up to16 Mbps for downlink (HSDPA). Data rates > 8 Mbps and up to 16Mbps are supported in the downlink only (HSDPA).

RNC (RN3.0 CD2.2)

. Feature RAN1596, HSPA Capability Based HO (For 3Ginterworking)

NodeB (WN4.0 CD1.2 [6.7-187])

The I-HSPA system is managed with the Operations Support System(OSS) and it interfaces with both circuit-switched (CS) and packet-switched (PS) core networks (CN). I-HSPA Release 1 specification baseline for radio interface is 3GPP Release 5/6 and for the architecture 3GPPRelease 7, called HSPA evolution. This document is NON-BINDING.



2 General functionality

2.1 IHSW-101: Optimized Network Architecture for thePS Traffic

2.1.1 Introduction

The introduction and evolution of 3GPP HSPA (HSDPA/HSUPA) radiostandard will grant mobile industry a historical opportunity to expand themobile voice dominating business to the new era of data dominatingservices. This will however only happen when the operator cost structuresupports the new business model.

This document introduces and provides a high level overview of NokiaSiemens Networks I-HSPA network solution proposal to satisfy theoperator's network requirements.

In formulating this proposed solution Nokia Siemens Networks has givencareful consideration to the operator's key technical requirements of 3GHSPA evolution, some of the main ones being:

. Fully compliant with 3GPP WCDMA radio standards, HSPA and itsevolution.

. Standard 3GPP Rel5 and Rel6 terminals (with HSDPA andoptionally HSUPA capability).

. Radio and core network optimized for broadband wireless access.

. Future proof carrier grade platforms.

. Architecture scalability that is independent of traffic growth createdby new services.

DN70500287Issue 1-1 en09/09/2008


General functionality

To address these and other operator key requirements, Nokia SiemensNetworks provides I-HSPA (Internet High Speed Packet Access) solution.The complete Nokia Siemens Networks solution offering consists of theWCDMA BTS enhanced to support I-HSPA, the Nokia Siemens NetworksPacket Core Network, and the Nokia Siemens Networks ManagementSolution.

Benefits for the operator

The I-HSPA base station provides more direct Internet access via the Gninterface by-passing the RNC and optionally SGSN in user plane. I-HSPAmakes a very fluent evolution for the existing 3G networks as well asprovides clear cost and performance optimization for new networks.

2.1.2 Functional description

I-HSPA is a 3GPP standards based simplified network architectureinnovation from Nokia Siemens Networks. From a technical perspective I-HSPA is a lean and streamlined architecture in which the subset offunctions of the RNC are implemented by the base station. The NokiaSiemens Networks I-HSPA RAN part consists of BTSs only. WCDMA BTSis adapted to support WCDMA, HSPA and I-HSPA technologies. I-HSPArelease 1 uses Flexi WCDMA BTS, which is a small, lightweight, modular,and versatile macro base station that provides a solution to address thechallenges faced by operators today rolling out and expanding theirnetworks.

I-HSPA implements the streamlined RNC functionality in I-HSPA Adapter,which is part of WCDMA BTS.

The I-HSPA Adapter main functionality includes:

. 3GPP defined protocols to handle terminals compliant to 3GPP

. Certain telecom and mobility signaling procedures

. Header compression as part of PDCP

. Authentication and authorization

. Adapter to Adapter interface and related Inter I-HSPA Handover,PDP context transfer and paging procedures

. Radio Resource Management

. Load control

. Admission control



. Power control

. HO control

. Packet scheduling

. WCDMA scrambling codes management

. RNTI management

. Subscriber and PDP context management

. Allocation and management

. Triggering PDP context re-establishment

For circuit-switched (CS) handovers, active CS users are moved to CSnetwork, either GSM/EGDE or 3G.

In other words, the base station provides more direct Internet access viathe Gn interface bypassing the RNC and optionally SGSN in user plane. I-HSPA makes a very fluent evolution for the existing 3G networks as wellas provides clear cost and performance optimization for new networks.

I-HSPA BTS can be connected to any standard compliant core network.Therefore, the operator can use existing Core Network Elements. NokiaSiemens Networks has introduced Direct Tunnel functionality, where theuser plane can also bypass SGSN. Direct Tunnel solution is now alsostandardized in 3GPP. All of the Nokia Siemens Networks core networkelements are implemented on highly available, highly scalable carriergrade platforms.

The complete solution is centrally managed and operated via the NokiaSiemens Networks NetAct framework which provides the operator with arich suite of tools to perform functions such as network monitoring,configuration, accounting, optimization, and fine tuning, to name just a few.

DN70500287Issue 1-1 en09/09/2008



Figure 1. I-HSPA in a cellular network

MSC Release: Not Applicable

2.1.3 System impact

2.1.3.1 Interdependencies between features

This feature has no interdependencies with other features.

2.1.3.2 Software dependencies

The following table presents software dependencies.

IMS

I-HSPA

I-HSPA

WCDMA BTS RNC

HSPAdevice

Content &Connectivity

Internet +Intranets

I-HSPA handover towardsRNC

I-HSPA Intrasystemhandover

GGSN

IM, Presence, PoC,Video sharing,VoIP, IP Centrex

SGSN

MSC



Table 1. Software dependencies for feature IHSW-101

I-HSPAAdapter

RAS BTSrelease(Flexi)

FTM NetAct OMS CombiSGSN

GGSN/FlexiISN

UE

Release I-HSPAAdapterRel1

N/A WBTS4.0 N/A OSS5.1 OMS1.0 N/A N/A 3GPPRel-5

2.1.3.3 Software sales information

The following table presents software sales information.

Table 2. Software sales information for feature IHSW-101

OSW/ASW SW component License control innetwork element

License controlattributes

OSW I-HSPA Always included 0.0

2.1.3.4 Management plane

Management data

The management data of this feature is listed in the following table.

Parameters Counters Alarms

No parameters related tothis feature

No counters related to thisfeature

No alarms related to thisfeature

2.2 IHSW-102: Support for Standard CompliantTerminals

2.2.1 Introduction

I-HSPA works with all the 3GPP standards based terminals. I-HSPAsystem serves terminals starting from 3GPP rel. 5 with HSDPA capabilitysupport. Other terminals will be directed to other networks.

DN70500287Issue 1-1 en09/09/2008




The operator can upgrade existing 2G/3G networks with I-HSPA and useoptimal network for each category of services.


I-HSPA system enables PS-optimized solution for the HSDPA andoptionally HSUPA capable terminals. 3GPP terminals rel. 4 and below andterminals without HSDPA capability will be directed to other networks.

Terminal and RAN interface (Uu interface) is fully 3GPP compliant anddoes not change at all.


2.2.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE






OSW/ASW SW component



Table 4. Software sales information for feature IHSW-102 (cont.)



License control innetwork element




Management data






2.3 IHSW-105: Optimized Radio Interface in I-HSPA

2.3.1 Introduction

I-HSPA works with standard based terminals. I-HSPA system servesterminals from 3GPP rel. 5 with HSDPA capability support.


I-HSPA system enables PS optimized solution for the HSDPA capableterminals. 3GPP rel. 4 and earlier terminals will be directed to othernetworks.


I-HSPA provides following transport channels for the user payload:

For downlink:

DN70500287Issue 1-1 en09/09/2008



. HS-DSCH High-speed downlink channel

. PCH Paging channel

. BCH Broadcast channel

. FACH Forward Access channel

For Uplink:

. DCH Dedicated Channel

. E-DCH with feature Enhanced Dedicated Channel

. RACH Random Access Channel

I-HSPA support the following six groups of physical channels:

. Dedicated Physical Channels (DPCH)

. Physical Random Access Channel (PRACH)

. Common Pilot Channel (CPICH)

. Primary Common Control Physical Channel (Primary CCPCH)

. Synchronization Channel (SCH)

. Secondary Common Control Physical Channel (Secondary CCPCH)

. Page Indicator Channel (PICH)

. Acquisition Indication Channel (AICH)

. High Speed Physical Downlink Shared Channel (HS-PDSCH)

. High Speed Dedicated Physical Control Channel (HS-DPCCH)

. High Speed Shared Control Channel (HS-SCCH)

. E-DCH Absolute Grant Channel (E-AGCH)

. E-DCH Relative Grant Channel (E-RGCH)

. E-DCH Hybrid ARQ Indicator Channel (E-HICH)

. E-DCH Dedicated Physical Control Channel (E-DPCCH)

. E-DCH Dedicated Physical Data Channel (E-DPDCH)



The DPCH is a user-dedicated channel between the UE and the BTS. TheDPCH is further divided into Dedicated Physical Data Channel (DPDCH)and Dedicated Physical Control Channel (DPCCH). The DPDCH is usedto carry dedicated user and control data generated by L2 and above. L1control information is transmitted on the DPCCH. Therefore, the radio linkmust always have a DPCCH in the uplink and downlink directions.

The PRACH is an uplink physical channel that is shared by several UEslocated in the same cell. The PRACH is always associated with the AICH,which is used to acknowledge preambles transmitted by the UEs in thePRACH.

The CPICH is used in downlink only. The CPICH is shared by all UEslocated in the cell and used to achieve and maintain synchronizationbetween the BTS and the UEs. Also, the UEs located in the adjacent cellsuse the CPICH for neighboring cell measurements. The CPICH transmitsonly L1 control information (predetermined pilot bits) and does not carryany user and control data generated by L2 and above.

The Primary CCPCH is used in downlink only. The Primary CCPCH isshared by all UEs located in the cell. The SCH is multiplexed with thePrimary CCPCH and used by the UEs to achieve synchronization to theBTS.

The Secondary CCPCHs are downlink physical channels that are sharedby several UEs located in the same cell.

The PICH is a downlink physical channel that is used for transmitting PageIndicators. Page Indicators inform the UEs about incoming pagingmessages.

Transport channels are services that Layer 1 offers to higher layers. Atransport channel is defined by how and with what characteristics the datais transmitted over the radio interface. The transport channel types can bedivided into the following two groups:

. Dedicated transport channels:. Dedicated Channel (DCH). Enhanced dedicated channel (E-DCH)

. Common transport channels:. Random Access Channel (RACH). Forward Access Channel (FACH). Paging Channel (PCH). Broadcast Channel (BCH). High-speed downlink shared channel (HS-DSCH)

DN70500287Issue 1-1 en09/09/2008



The DCH is used to carry user or control information between the RAN andthe UE. The DCH is mapped to the DPCH. Several DCHs per DPCH (perdirection) can be allocated within one radio link.

The RACH is an uplink transport channel used to carry control informationor user data. The RACH is mapped to the PRACH.

The FACH is a downlink transport channel used to carry controlinformation or user data to a UE when the RAN knows the location cell ofthe UE. The PCH is the downlink transport channel used to page the UE.Both the FACH and the PCH are mapped to the Secondary CCPCH. TheFACH and the PCH can be multiplexed into same Secondary CCPCHs.

The BCH is a downlink transport channel used to broadcast system or cell-specific information. The BCH is mapped to the Primary CCPCH.

E-DCH was introduced in 3GPP release 6. It exists in the uplink only, withpossibility to change rate each Transmission Time Interval. It is mapped toE-DPDCH.

HS-DSCH was introduced in 3GPP release 5. The downlink transportchannel is shared by several UEs. It is mapped to HS-PDSCH.

The mapping of the transport channels to the physical channels isdescribed in the figure Correlation of transport and physical channels.

A cell including the receiving and transmitting functionality normally hasallocation from each of the common transport channel types.



Figure 2. Correlation of transport and physical channels


2.3.3 System impact





Transport Channles Physical Channels

DCH Dedicated Physical Data Channel (DPDCH)

Dedicated Physical Control Channel (DPCCH)

E-DCH E-DCH Dedicated Physical Data Channel (E-DPDCH)

E-DCH Dedicated Physical Control Channel (E-DPCCH)

E-DCH Absolute Grant Channel (E-AGCH)

E-DCH Relative Grant Channel (E-RGCH)

E-DCH Hybrid ARQ Indicator Channel (E-HICH)

Physical Random Access Channel (PRACH)RACH

Common Pilot Channel (CPICH)

Primary Common Control Physical Channel (P-CCPCH)

Secondary Common Control Physical Channel (S-CCPCH)

BCH

FACH

PCHSynchronization Channel (SCH)

Acquisition Indicator Channel (AICH)

Paging Indicator Channel (PICH)

High Speed Physical Downlink Shared Channel (HS-PDSCH)HS-DSCH

HS-DSCH-related Shared Control Channel (HS-SCCH)

Dedicated Physical Control Channel (uplomk) for HS-DSCH (HS-DPCCH)

DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE










Management data






2.4 IHSW-103: Optimized User Plane and Round TripTime (RTT) for PS

2.4.1 Introduction

PS-optimized network architecture enables reduced RTT for the userplane.




. Enables new services, for example, some games requiring shortRTT.

. Enables better end-user experience for the services.

. Improves throughput.


End-to-end RTT delay including UE is shorter than RTT in traditional HSPAimplementation as the RNC is removed and optionally SGSN can also beremoved from the user plane. I-HSPA also removes the Iub interfacebetween BTS and RNC, when RNC functionality is moved to the BTS.

Figure 3. User plane from BTS to GGSN


2.4.3 System impact



2.4.3.2 Software dependencies:


SGSN

I-HSPA

ISN / GGSN

User plane directly fromBTS to GGSN

DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE


N/A WBTS4.0 N/A OSS5.1 OMS1.0 SGN6.0 N/A 3GPPRel-5








Management data






2.5 IHSW-104: Optimized Control Plane andConnection Set-up Time

2.5.1 Introduction

PS-optimized network architecture enables reduced connection set-uptimes.




This feature enables better end-user perception of packet services, forexample Web browsing requires fast connection set-up time to provideexcellent user experience.


I-HSPA moves part of the RNC functionality to the BTS, which means thatconnection set-up time is shorter than in traditional HSPA implementationbecause Iub is removed in I-HSPA architecture. Adapter also implementsadditional feature as Direct Resource Allocation for HSDPA set-up.

Figure 4. Control plane from BTS to GGSN


2.5.3 System impact






I-HSPAAdapter

RAS FTM NetAct OMS CombiSGSN

UE

SGSN

I-HSPA

ISN / GGSN

Control plane directly fromBTS to SGSN

DN70500287Issue 1-1 en09/09/2008



Table 9. Software dependencies for feature IHSW-104 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA Always included 0


Management data

Parameters:

Table 11. IHSW-104: Optimized Control Plane and Connection Set-up Timeimpact on parameters

Parameter Use

Usage of the direct resource allocationfor PS NRT RAB

This parameter enables/disables theuse of the direct resource allocationfeature.



No counters related to this feature No alarms related to this feature




Usage of the direct resourceallocation for PS NRT RAB

DN70500287Issue 1-1 en09/09/2008





3 Radio resource management andtelecom

3.1 Mobility management

3.1.1 IHSW-26: I-HSPA Intra System Mobility Based on Hard Handover (NoIur)

3.1.1.1 Introduction

This feature enables basic mobility between I-HSPA Adapters without Iurinterfaces and direct mobility from the HS-DSCH in one cell to the HS-DSCH in another cell.


The operator can provide mobility without Iur, which simplifies thetransmission network planning and parametrization.

3.1.1.2 Functional description

The HSDPA Serving Cell Change (SCC) is an HS-DSCH to HS-DSCHhandover (HO) that can happen either between cells that belong to thesame BTS (intra-BTS SCC), or between cells that belong to different BTSs(inter-I-HSPA Adapter SCC). Standard compliant Hard Handoverprocedure between I-HSPA Adapters is used.

The operator can control the sensitivity of the serving cell change. For allcases, the MAC-hs of the source cell is reset upon the serving cell changeand the RLC protocol takes care of the retransmission of the data to thetarget cell.

This feature ensures that the best available radio condition in the active setis used for HS-DSCH. Direct HSPA allocation is used in target Adapterduring handover, resulting in quicker handover and shorter traffic break.

DN70500287Issue 1-1 en09/09/2008


Radio resource management and telecom


3.1.1.3 System impact

Interdependencies between features


Software dependencies



I-HSPAAdapter



GGSN/FlexiISN

UE



Software sales information






Management plane

Management data

Parameters:



Table 14. IHSW-26: I-HSPA Intra System Mobility Based on Hard Handover(no Iur) impact on parameters

Parameter Use

Inter-Adapter HHO repetition timer Guard Timer to prevent repeated Inter-Adapter HHO during this time period.



Inter-Adapter HHO repetition timer No counters related to this feature No alarms related to this feature

3.1.2 IHSW-9: Intra-System Handover


The terminal sees the I-HSPA intra-system handover as normal handoverin the traditional 3GPP. I-HSPA system hides the changes towards theterminal and the core network. Intra-system handover is fast enough forseamless VoIP.


This feature ensures full coverage for HSDPA and allows macrodiversitygain in uplink and more reliable signaling over R99-DCH in case ofsignaling radio bearers.


I-HSPA uses HSDPA in the DL. This feature implements HSDPA soft/softer handover for associated DPCH.

Soft/softer HO for HSDPA users enables HSDPA usage in the whole cellcoverage area and between the cells. The following intra-frequency soft/softer HOs for associated DPCH are supported:

. Intra-BTS softer handover

. Inter-BTS inter-I-HSPA Adapter soft handover

DN70500287Issue 1-1 en09/09/2008



Implementation of these HOs ensures full coverage for HSDPA as well asit allows achieving macrodiversity gain in uplink and more reliablesignaling over R99-DCH in case of signaling radio bearers. Therefore, HS-DSCH is also supported for UEs with an active set size larger than one (tothe UEs in the soft handover (SHO) region).

To prevent the use of Serving I-HSPA Adapter anchoring for HS-DSCH incase of inter-BTS inter-I-HSPA Adapter SHO, Serving I-HSPA AdapterRelocation procedure combined with inter-I-HSPA Adapter HS-DSCHServing Cell Change is triggered when the branch(es) from Drifting I-HSPAAdapter become(s) more favorable.

HSPA data flow is not established over Iur interface but HSPA resourcesare reserved and allocated under Drift I-HSPA Adapter in conjunction withthe SRNS relocation. Associated DCH (signaling link) and uplink DCHreturn channel can be set-up over Iur-interface, whereas HS-DSCH and E-DCH are not allowed over Iur interface.

The operator can set this feature on or off for the whole network.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW/ASW RAS SW component License control innetwork element


OSW I-HSPA Always included -

Management plane

Management data

Parameters:

Table 17. IHSW-9: Intra-System Handover impact on parameters

Parameter Use

Averaging window of the CPICH Ec/Nomeasurement

This parameter determines theaveraging window for the periodicalCPICH Ec/No measurement reporting,which is used as a criterion for theserving HS-DSCH cell changeprocedure.

CPICH Ec/No threshold for serving HS-DSCH cell change

Parameter determines the absoluteCPICH Ec/No threshold for the servingHS-DSCH cell change procedure.

Reporting period of the CPICH Ec/Nomeasurement

This parameter determines the reportingperiod of the CPICH Ec/Nomeasurement, which is used as acriterion for the serving HS-DSCH cellchange procedure.

Minimum interval between serving HS-DSCH cell changes

Parameter determines the minimuminterval between serving HS-DSCH cellchanges due to CPICH Ec/No windowbetween the best cell and the servingHS-DSCH cell.

Window for max repetitive serving HS-DSCH cell changes

Parameter determines the time periodfor calculation of the maximum numberof repetitive serving HS-DSCH cellchanges.

Max number of repetitive serving HS-DSCH cell changes

Parameter determines the maximumnumber of repetitive serving HS-DSCHcell changes during a predefined timeperiod (see parameter relationships). Ifthe maximum number of serving HS-DSCH cell changes is exceeded, HS-DSCH is released.

DN70500287Issue 1-1 en09/09/2008



Table 17. IHSW-9: Intra-System Handover impact on parameters (cont.)

Parameter Use

Averaging window of the SIRerrormeasurement

Parameter determines the averagingwindow for the periodical UL SIRerrormeasurement, which is used as acriterion for serving HS-DSCH cellchange procedure.

Higher layer filtering coefficient forHSDPA SIRerror

Parameter determines the filteringcoefficient of the UL SIRerrormeasurement which is used as acriterion for serving HS-DSCH cellchange procedure.

Reporting period of the SIRerrormeasurement

Parameter determines the reportingperiod of the dedicated UL SIRerrormeasurement, which is used as acriterion for serving HS-DSCH cellchange procedure. If the value of theparameter is set to 0, SIRerrormeasurement is not used as a criterion.

SIRerror threshold for the serving HS-DSCH cell

The parameter determines the level ofthe UL SIRerror of the serving cell,which initiates serving HS-DSCH cellchange.

SIRerror threshold for the target cell The parameter determines the requiredlevel of the UL SIRerror in the targetcell in order to execute serving HS-DSCH cell change due to DL CPICHEc/No or UL SIRerror.

CPICH Ec/No window for serving HS-DSCH cell selection

The parameter determines themaximum allowed difference betweenthe best cell and the serving HS-DSCHcell. The window is relative to the bestcell in the active set.

DRNC Ec/No offset for HSPA Inter-Adapter Cell Change

This parameter defines an offsetdeducted from the CPICH Ec/Nomeasurement result of the Drift Adaptercell.

SIR error offset for HSPA Inter-RNC CellChange

This parameter defines an offsetdeducted from the UL SIR errormeasurement, which is applied in thecase of Inter-Adapter SCC/Role Switch.

Role Switch activation adjustment offset This parameter defines an offset thatcan be used to tune the activation offset(CFN offset) for role switch.

HSUPA Inter Adapter Serving CellChange

The parameter indicates whether anInter-Adapter serving cell change canbe initiated when HSUPA is allocated inthe Source Adapter.



Table 17. IHSW-9: Intra-System Handover impact on parameters (cont.)

Parameter Use

Neighbouring Radio Network Elementtype

The parameter indicates whether theneighbouring WCDMA Controller Nodeis an I-HSPA adapter or a 3G RNC.

List of Neighbouring PLMN identities List of Neighbouring PLMN identities.

Neighbouring PLMN identity Neighbouring PLMN identity is used toglobally identify the neighbouring RNCor I-HSPA Adapter.



Averaging window of the CPICHEc/No measurement

CPICH Ec/No threshold for servingHS-DSCH cell change

Reporting period of the CPICH Ec/No measurement

Minimum interval between servingHS-DSCH cell changes

Window for max repetitive servingHS-DSCH cell changes

Max number of repetitive servingHS-DSCH cell changes




SIRerror threshold for the servingHS-DSCH cell

SIRerror threshold for the targetcell

CPICH Ec/No window for servingHS-DSCH cell selection

DRNC Ec/No offset for HSPAInter-Adapter Cell Change

SIR error offset for HSPA Inter-RNC Cell Change


DN70500287Issue 1-1 en09/09/2008




Role Switch activation adjustmentoffset

HSUPA Inter Adapter Serving CellChange

Neighbouring Radio NetworkElement type

List of Neighbouring PLMNidentities

Neighbouring PLMN identity

3.1.3 IHSW-14: 2G/3G Inter-System Handover


This feature provides inter-system mobility for PS towards 2G/3G.


The feature enables seamless coverage. The operator can build the dataoptimized I-HSPA network to the areas of high HSPA capacity andimplement low HSPA capacity areas with other networks.


For 3G domain HOs, I-HSPA system uses standard interfaces towards theexisting RNCs via core network and the radio network will see thehandover as standard combined Hard handover and serving RNSrelocation. I-HSPA uses Iu interface in the inter-system HO. I-HSPA andthe traditional 3GPP can use same GGSN and IP addresses for the PDPcontext. In Cell_FACH, Cell_PCH or URA_PCH, due to no-Iur, RRCconnection release with directed signaling connection re-establishmentcause is used. In CELL_ DCH state Hard Handover is used.

For 2G domain HOs, UE will be forced to initiate new cell re-selection andexecute Routing Area Update procedure to target SGSN if access to newcell generates RAU.










I-HSPAAdapter



GGSN/FlexiISN

UE








ASW I-HSPA I-HSPA Adapter LK Long-term ON/OFFlicense

Management plane

Management data

Parameters:

Table 20. IHSW-14: 2G/3G Inter-System Handover impact on parameters

Parameter Use

Inter-system adjacency identifier Identification of inter-system adjacency(GSM) within a WCDMA cell. WhenWireless Priority Service feature isenabled, then value 0 is a special valuewhich indicates that cell is target cell ofblind handover.

Base Station Colour Code

DN70500287Issue 1-1 en09/09/2008



Table 20. IHSW-14: 2G/3G Inter-System Handover impact on parameters(cont.)

Parameter Use

Base Station Identity Code (BSIC) iscomposed of Network Colour Code(NCC) and Base Station Colour Code(BCC).

BCCH ARFCN Parameter contains the absolute RFchannel number of the BroadcastControl Channel (BCCH) of the GSMneighbour cell.

Band Indicator Indicates how to interpret the value ofthe parameter AdjgBCCH.

Cell Identifier Cell identifier of the GSM neighbourcell.

Location Area Code The PLMN Identifier and Location AreaCode (LAC) determine the LocationArea (LAI) to which the GSM neighbourcell belongs to.

Mobile Country Code Unique country identification of GSMneighbour cell.

Mobile Network Code A GSM neighbour cell is identified withthe Cell Global Identifier (CGI), which iscomposed of the PLMN Identifier (MCC+ MNC), Location Area Code and CellIdentifier.

Mobile Network Code Length Defines whether 2 or 3 digits are usedin Mobile Network Code.

Network Colour Code Base Station Identity Code (BSIC) iscomposed of Network Colour Code(NCC) and Base Station Colour Code(BCC).

Include in System Information The parameter indicates whether theGSM neighbour cell is included in thesystem information for the cell selectionand re-selection procedures. Theparameter does not affect GSMmeasurements in CELL_DCH state ofconnected mode.

Maximum UE TX Power on RACH Indicates the maximum transmissionpower level that an UE can use whenaccessing the GSM neighbour cell onthe RACH.

Maximum UE TX Power on TCH Parameter indicates the maximumtransmission power level that an UEmay use on a TCH in the GSMneighbour cell.




Parameter Use

NRT HOPG Identifier Parameter defines the parameter set(HOPG object) which controls the inter-RAT handover of a non-real time (NRT)radio bearer to the GSM neighbour cell.

FMCG identifier This parameter identifies the FMCGuniquely within I-HSPA Adapter.

GSM HO caused by CPICH Ec/No The parameter indicates whether ahandover to GSM caused by lowmeasured absolute CPICH Ec/No of theserving cell is enabled.

GSM HO caused by CPICH RSCP This parameter indicates whether ahandover to GSM caused by lowmeasured absolute CPICH RSCP of theserving cell is enabled.

GSM HO caused by UE TX Power The parameter indicates whether ahandover to GSM caused by high UETX power level is enabled.

GSM HO caused by UL DCH Quality The parameter indicates whether ahandover to GSM caused by bad uplinkDCH quality is enabled.

Maximum Measurement Period The maximum number of periodicalinter-RAT (GSM) measurement reportsdetermines the maximum allowedduration of the GSM measurement.

Measurement Averaging Window The parameter determines themaximum number of periodical inter-RAT (GSM) measurement reports(maximum size of the sliding averagingwindow) from which the I-HSPA adaptercalculates the averaged GSM RSSIvalues for the handover decisionalgorithm.

Measurement Reporting Interval This parameter determines themeasurement reporting interval forperiodical inter-RAT (GSM)measurements.

Minimum Interval Between HOs This parameter determines theminimum interval between a successfulinter-RAT handover from GSM toUTRAN and the following inter-RAThandover attempt back to GSM relatedto the same RRC connection.

Minimum Measurement Interval

DN70500287Issue 1-1 en09/09/2008




Parameter Use

This parameter determines theminimum interval between anunsuccessful inter-RAT (GSM)measurement or handover procedure,and the following GSM measurementprocedure related to the same RRCconnection.

GSM Neighbour Cell Search Period The parameter determines the numberof periodical inter-RAT (GSM)measurement reports, starting from thefirst report after the measurement setup,during which a handover to GSM is notpossible.

UE TX Power Filter Coefficient The parameter controls the higher layerfiltering of physical layer UE TX powermeasurements before the eventevaluation and measurement reportingis performed by the UE.

UE TX Power Threshold for NRT PS The parameter determines the UE TXpower threshold for a non-real time PSdata connection.

UE TX Power Time Hysteresis This parameter determines the timeperiod during which the UE TX powermust stay below the UE TX powerthreshold before the I-HSPA adaptercalls off the GSM measurementscaused by the high UE TX power.

Cell Re-selection HCS Priority Defines the prioriry level of the GSMneighbour cell in the hierarchical cell re-selection procedure.

Cell Re-selection HCS Threshold Defines the threshold which must beexceeded by the RSSI measurementresult of the GSM neighbour cell beforethe hierarchical cell re-selectionbecomes possible.

Cell Re-selection Penalty Time The parameter determines the timeperiod during which the TemporaryOffset 1 is applied in the cell re-selection procedure for the GSMneighbour cell in question.

Ncell Priority for Coverage HO The priority level of the GSM neighbourcell is controlled by this parameter. Therange of the parameter varies from zeroto 7. Zero is the lowest and 7 thehighest priority level.




Parameter Use

Cell Re-selection Quality Offset 1 The parameter is used in the cell re-selection and ranking between WCDMAand GSM cells.

Cell Re-selection Minimum RX Level The parameter determines the minimumrequired RSSI level which themeasurement result of the GSMneighbour cell must exceed before thecell re-selection is possible.

Minimum RX Level for Coverage HO This parameter determines theminimum required GSM RSSI levelwhich the averaged RSSI value of theGSM neighbour cell must exceedbefore the coverage (or quality) reasonhandover to GSM is possible.

Cell Re-selection Temporary Offset 1 Parameter is used in the cell rankingbetween GSM and WCDMA cells whenthe GSM neighbour cell has the sameHCS priority level as the serving cell.

HOPG Identifier This parameter identifies the HOPGuniquely within I-HSPA Adapter.

Blind GSM handover for NRT PS RAB The parameter indicates whether ablind inter-RAT cell change to 2G isallowed for NRT PS data services.

Blind GSM handover for RT PS RAB The parameter indicates whether ablind inter-RAT cell change to 2G isallowed for RT PS data services.

Blind Inter frequency handover for NRTPS RAB

The parameter indicates whether ablind inter-RAT cell change to 3G isallowed for NRT PS data services.

Blind Inter frequency handover for RTPS RAB

The parameter indicates whether ablind inter-RAT cell change to 3G isallowed for RT PS data services.

Handover of NRT PS Service to GSM This parameter indicates whether aninter-RAT handover (cell change) toGSM/GPRS is allowed for non-real timepacket switched (PS) data services inCELL_DCH state of connected mode.

UE in DCH X/Y state timer The parameter indicates the maximumtime during which UE is allowed to stayin DCH x/y state after failure of IF/IRmeasurements or handover.

BLHO failure inter-system cell penalty

DN70500287Issue 1-1 en09/09/2008




Parameter Use

The parameter indicates the penaltytime on an inter-system cell, on whichan inter-system blind handover (IRBLHO) was unsuccessful.

BLHO failure Inter-frequency cell penalty The parameter indicates the penaltytime on an inter-frequency cell, onwhich an inter-frequency blind handover(IF BLHO) was unsuccessful.

Transmision gap pattern length in caseof double frame: NRT PS service andGSM measurement

Parameter defines the length oftransmission gap pattern for GSM inter-RAT measurement in case ofcompressed mode with double framegap and UE using non-real time packetscheduled data service.

Transmision gap pattern length in caseof single frame: NRT PS service andGSM measurement

Parameter defines the length oftransmission gap pattern for GSM inter-RAT measurement in case ofcompressed mode with single framegap and UE using non-real time packetscheduled service.

Neighboring Radio Network Elementtype

The parameter indicates whether theneighboring WCDMA Controller Node isan I-HSPA Adapter or a 3G RNC.



Inter-system adjacency identifier

Base Station Colour Code

BCCH ARFCN

Band Indicator

Cell Identifier

Location Area Code

Mobile Country Code

Mobile Network Code

Mobile Network Code Length

Network Colour Code

Include in System Information

Maximum UE TX Power on RACH





Maximum UE TX Power on TCH

NRT HOPG Identifier

FMCG identifier

GSM HO caused by CPICH Ec/No

GSM HO caused by CPICH RSCP

GSM HO caused by UE TX Power

GSM HO caused by UL DCHQuality

Maximum Measurement Period

Measurement Averaging Window

Measurement Reporting Interval

Minimum Interval Between HOs

Minimum Measurement Interval

GSM Neighbour Cell SearchPeriod

UE TX Power Filter Coefficient

UE TX Power Threshold for NRTPS

UE TX Power Time Hysteresis

Cell Re-selection HCS Priority

Cell Re-selection HCS Threshold

Cell Re-selection Penalty Time

Ncell Priority for Coverage HO

Cell Re-selection Quality Offset 1

Cell Re-selection Minimum RXLevel

Minimum RX Level for CoverageHO

Cell Re-selection Temporary Offset1

HOPG Identifier

Blind GSM handover for NRT PSRAB

Blind GSM handover for RT PSRAB

Blind Inter frequency handover forNRT PS RAB

Blind Inter frequency handover forRT PS RAB

DN70500287Issue 1-1 en09/09/2008




Handover of NRT PS Service toGSM

UE in DCH X/Y state timer

BLHO failure inter-system cellpenalty

BLHO failure Inter-frequency cellpenalty

Neighboring Radio NetworkElement type

3.1.4 ARAN970: HSUPA Handover


This feature brings soft/softer handovers and serving cell changes forHSUPA users, allowing HSUPA in the whole cell coverage area andbetween the cells.


This feature enables full mobility for the HSUPA users and widens thecoverage area of a given bit rate. The gain is significant especially withhigh bit rates.


The following intra-frequency soft/softer handovers are supported for E-DCH:

. Intra-BTS intra-I-HSPA Adapter softer handover

. Inter-BTS soft handover for signaling radio bearer

The algorithms of HSDPA are followed. The HS-DSCH and E-DCH servingcell is always the same cell.









Table 21. Software dependencies for feature ARAN970

I-HSPAAdapter



GGSN/FlexiISN

UE





Table 22. Software sales information for feature ARAN970



OSW I-HSPA 0.0 -

Management plane

Management data




ONE CELL IN E-DCH ACTIVE SETDURATION

TWO CELLS IN E-DCH ACTIVE SETDURATION

THREE CELLS IN E-DCH ACTIVE SETDURATION

SOFTER HANDOVER DURATION ON THESRNC SIDE FOR HSUPA MOBILITY

CELL ADDITION ATTEMPT REQ BY UE TOE-DCH AS


DN70500287Issue 1-1 en09/09/2008




CELL ADDITION SUCCESS TO E-DCHACTIVE SET

CELL NOT ADDED TO E-DCH ACTIVE SETBUT ADDED TO DCH AS

CELL ADDITION ATTEMPT RETRY TO E-DCH AS

3.2 Voice

3.2.1 IHSW-31: I-HSPA CS Service Enabling Handover


This feature enables seamless provision of the CS Service for the end-user.

For instructions on how to activate this feature, see document FeatureIHSW-31: I-HSPA CS Service Enabling Hand Over Feature ActivationManual.


CAPEX and OPEX savings are achieved with the right architecture for theright purpose. The feature provides all services seamlessly with theexisting and future 3G terminals. In the future, services are moved to PSonly networks, for example voice calls are done using VoIP technologybecause of better spectral efficiency. To enable smooth evolution, theoperator can continue to use already invested machinery for CS servicesas long as it is feasible.


CS Service Enabling HO takes care of service differentiation between I-HSPA, WCDMA and GSM/GPRS systems.

CS Service Enabling Handover (HO) is a feature that enables movingsubscribers between I-HSPA and WCDMA networks or between I-HSPAand GSM networks. The feature is needed to ensure that all services areavailable for all subscribers. Based on operator definable end-user servicecategories, the CS voice calls can be moved either to the 3G or to the 2Gnetworks in order to provide the required service.



If UE was camped to 2G or 3G network:

. In case of the PS service request, 3G or 2G network movessubscriber back to the I-HSPA network;

. In the case of a CS only or CS + PS MultiRAB- or Dual TransferMode (DTM) call, the services are provided by 3G or 2G network.

I-HSPA offers IuCS signaling towards MSC/VLR. This enables fast andreliable HO to CS enabled network such as GSM/EDGE or hierarchicalWCDMA. The CS service enabling HO is implemented running combinedHard Handover with SRNC functionality in I-HSPA Adapter relocationduring call setup, therefore the delay for the call set-up is minimal.

Mobile terminated calls can be handled in similar way.

Operational aspects: The list below shows an example of service prioritydefinitions. Each service is given a preferred system/layer, which can beset by the operator.

. CS voice (including CS emergency call) → GSM or WCDMA

. HSPA traffic → I-HSPA

. Rel 99 data → WCDMA

. CS + PS MultiRAB → WCDMA

. CS Emergency call → GSM or WCDMA

MSC Release: M13.6







I-HSPAAdapter



GGSN/FlexiISN

UE

DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 25. IHSW-31: I-HSPA CS Service Enabling Handover impact onparameters

Parameter Use

BLHO failure inter-system cell penalty The parameter indicates the penaltytime on an inter-system cell, on whichan inter-system blind handover (IRBLHO) was unsuccessful.

BLHO failure Inter-frequency cell penalty The parameter indicates the penaltytime on an inter-frequency cell, onwhich an inter-frequency blind handover(IF BLHO) was unsuccessful.

ADJG Blind Handover to GSM/GPRS The parameter indicates whether the I-HSPA Adapter may perform an inter-RAT handover to the GSM neighbourcell as a blind handover.



Table 25. IHSW-31: I-HSPA CS Service Enabling Handover impact onparameters (cont.)

Parameter Use

ADJI Blind Inter-frequency Handover The parameter indicates whether the I-HSPA Adapter may perform a inter-frequency handover from the serving(source) cell to the neighbouring (target)cell as a blind handover.

Blind GSM handover for CS RAB The parameter indicates whether ablind inter-RAT cell change to 2G isallowed for CS data services.

Blind Inter frequency handover for CSRAB

The parameter indicates whether ablind inter-RAT cell change to 3G isallowed for CS data services.

CS Enabling handover solution with Iu-CS

This parameter defines the use of Iu-CSbased handover to 2G/3G for CS calls.

CPICH Ec/No Threshold Value For CUCUsage

The parameter defines the thresholdvalue that is checked to decide whetherto move the UE to Cell_DCH usingRRC:CELL UPDATE CONFIRM.

Cell/URA_PCH to Cell_DCH transitiondue to CS call

This parameter defines the use of Cell/URA_PCH to Cell_DCH transition incase of a CS call attempt in Cell/URA_PCH state.

I-HSPA Unsupported RAB CombinationHandling

This parameter defines the handling ofa PS RAB Request if its admissionresults unsupported RAB combination inI-HSPA.

Maximum Number of BLHO Attempts This parameter describes the maximumnumber of subsequent (unsuccessful)inter-frequency and inter-system blindhandover attempts.

Direct HSPA Handover The parameter indicates whether theneighboring RNC supports a directHSDPA or HSPA relocation or not.



BLHO failure inter-system cellpenalty

BLHO failure Inter-frequency cellpenalty

ADJG Blind Handover to GSM/GPRS

RRC CONN REJECT DUE TORRC CONNECTION SETUPREDIRECTION

ATTEMPTED INTERFREQUENCY HANDOVERSCAUSED BY CS CALL

No alarms related to this feature

DN70500287Issue 1-1 en09/09/2008




ADJI Blind Inter-frequencyHandover

Blind GSM handover for CS RAB

Blind Inter frequency handover forCS RAB

CS Enabling handover solutionwith Iu-CS

CPICH Ec/No Threshold Value ForCUC Usage

Cell/URA_PCH to Cell_DCHtransition due to CS call

I-HSPA Unsupported RABCombination Handling

Maximum Number of BLHOAttempts

Direct HSPA Handover

SUCCESSFUL INTERFREQUENCY HANDOVERCAUSED BY CS CALL

RRC CONNECTION DROPSDURING INTER FREQHANDOVER CAUSED BY CSCALL

UNSUCCESSFUL INTERFREQUENCY HANDOVERCAUSED BY CS CALL

ATTEMPTED INTER SYSTEMHANDOVERS CAUSED BY CSCALL

SUCCESSFUL INTER SYSTEMHANDOVER CAUSED BY CSCALL

RRC CONNECTION DROPSDURING INTER SYSTEMHANDOVER CAUSED BY CSCALL

UNSUCCESSFUL INTERSYSTEM HANDOVER CAUSEDBY CS CALL

3.2.2 IHSW-50: VoIP


I-HSPA enables efficient VoIP networks using optimized PS networkstructure.


The operator can provide VoIP using I-HSPA as a PS-only accessnetwork.


I-HSPA system provides efficient network for the VoIP service. Theoperator can integrate I-HSPA system to the different VoIP services, forexample towards IMS.

The operator can provide VoIP using I-HSPA as PS access network. Theoperator can also improve VoIP user experience using additional features,such as Direct Resource Allocation for HSDPA setup.










I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






DN70500287Issue 1-1 en09/09/2008



3.3 Quality of Service

3.3.1 IHSW-10: QoS for IP Transport


This feature enables I-HSPA system specific QoS support.


The feature provides a better end-user experience using QoSdifferentiation.


I-HSPA QoS support e-2-e requires support from several elements. I-HSPA Adapter maps 3GPP HSPA QoS parameters from the air interfacetowards IETF specified Differentiated Services (DiffServ) based QoSmappings. Transport supports DiffServ. Intelligent Service Node or ISN ofNokia Siemens Networks supports L4- 7 packet look-up enabling, forexample, the separation of VoIP traffic from the rest of the traffic. ISN mapsthe DiffServ code points to downlink and, for example, in the case of bi-directional VoIP traffic, I-HSPA Adapter uses the mapping for markinguplink in the same way.

1st Phase QoS on Adapter: the traffic class and THP; Admission Controlbased on Traffic Class and Allocation, and Retention Priority parametersand DiffServ marking for transport layer.








I-HSPAAdapter


UE




I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN









Management plane

Management data

Parameters:

Table 30. IHSW-10: QoS for IP Transport impact on parameters

Parameter Use

Background ARP1 To DSCP Mapping DSCP for the background traffic classwith ARP1.



Conversational ARP1 To DSCP Mapping DSCP for the conversational trafficclass with ARP1.

DN70500287Issue 1-1 en09/09/2008



Table 30. IHSW-10: QoS for IP Transport impact on parameters (cont.)

Parameter Use



Change origin The parameter defines the origin of thelast configuration action affecting theobject.

IP Qos Management Identifier Identifier for Quality of Service settingsfor Iu Interface.

Interactive THP1 ARP1 To DSCPMapping

DSCP for the interactive traffic classwith THP1 and ARP1.

















Streaming ARP1 To DSCP Mapping DSCP for the streaming traffic classwith ARP1.





Background ARP1 To DSCPMapping







Conversational ARP1 To DSCPMapping



Change origin

IP Qos Management Identifier










Streaming ARP1 To DSCPMapping



DN70500287Issue 1-1 en09/09/2008



3.4 Capacity and efficiency

3.4.1 ARAN834: Flexible Iu


Flexible Iu feature provides a standardized mechanism for connectingmultiple MSCs and SGSNs to an I-HSPA Adapter within a single operatorNW. Flexible Iu is also known as 'Iu Flex' and 3GPP uses the names 'IntraDomain Connection of RAN Nodes to Multiple CN Nodes' and 'MultipointIu/Gb/A'.


Flexible Iu provides CAPEX and OPEX savings resulting from efficientCNs resource utilization and load balancing. Increased service availabilityand better NW resilience improve the end-user experience.


This feature introduces the concept of Pool Areas. A UE may roam freelywithin a Pool Area (in either connected or idle mode) without the need tochange the CN serving node.

Pool Area configurations are done in the CN nodes. Pool Areasthemselves are not visible to the RAN but the I-HSPA Adapterconfiguration has to be done according to the CN Pool Area configurationsso that the Adapter is able to route signaling messages to any CN nodewithin a Pool Area.

The NAS Node Selector function (NNSF) is a mechanism used forselecting the CN node for the UE. The UE derives the value of theparameter NRI from the (P)-TMSI or IMSI and sends the NRI to the I-HSPAAdapter in the Initial Direct Transfer message. The Adapter selects the CNnode corresponding to the NRI value configured in its database.

The NNSF in the I-HSPA Adapter also contains the CN node recoveryfunctionality, which balances the load between the CN nodes of a pool indifferent cases, for example, with CN node failure, SW/HW update oradding/removing a CN node to/from the pool.










I-HSPAAdapter



GGSN/FlexiISN

UE


N/A WBTS4.0 N/A OSS5.1 OMS1.0 SGN6.0 N/A 3GPPRel-5






ASW I-HSPA Always included -

Management plane

Management data

Parameters

Table 33. ARAN834: Flexible Iu impact on parameters

Parameter Use

Default Core Network DefaultCN is a parameter used toidentify if considered CN is used as adefault CN.

DN70500287Issue 1-1 en09/09/2008



Table 33. ARAN834: Flexible Iu impact on parameters (cont.)

Parameter Use

Default Core Network DefaultCN is a parameter used toidentify if considered CN is used as adefault CN.

NRI length for CS Core Networks NRI length for CS Core networks.

NRI length for PS Core Networks NRI length for PS Core networks.

Null NRI value for CS Pool Null NRI value for CS Pool.

Null NRI value for PS Pool Null NRI value for PS Pool.

NRI list for CS Core routing NRI list for CS Core routing.

Maximum value of NRI range for CSCore routing

Maximum value of NRI range for CSCore routing.

Minimum value of NRI range for CSCore routing

Minimum value of NRI range for CSCore routing.

State of Iu interface State of Iu interface - WO-EX = workingnormally, default - BAL-US = barredfrom load balacing only - BAR-US =barred from all connections

State of Iu interface State of Iu interface - WO-EX = workingnormally, default - BAL-US = barredfrom load balancing only - BAR-US =barred from all connections

NRI list for PS Core routing NRI list for PS Core routing.

Maximum value of NRI range for PSCore routing

Maximum value of NRI range for PSCore routing.

Minimum value of NRI range for PSCore routing

Minimum value of NRI range for PSCore routing.



Default Core Network

Default Core Network

NRI length for CS Core Networks

NRI length for PS Core Networks

Null NRI value for CS Pool

Null NRI value for PS Pool

NRI list for CS Core routing

Maximum value of NRI range forCS Core routing





Minimum value of NRI range forCS Core routing

State of Iu interface

State of Iu interface

NRI list for PS Core routing

Maximum value of NRI range forPS Core routing

Minimum value of NRI range forPS Core routing

3.4.2 ARAN242: Flexible Upgrade of NRT DCH Data Rate


This feature enables the operator to control the upgrade of the UL DCHsallocated for the NRT RABs.


CAPEX and OPEX savings can be expected due to the better resourceutilization. Improved service availability and data rates also increase theend-user experience.


With this feature the operator can control the flexible data rate upgrades.

The UL DCH throughput is measured in UE (via TVM measurements).

All this enables the control of adapting to the fast changes in the ULDCHdata rates and radio conditions without causing unnecessary upgradesand downgrades of DCH data rate.





DN70500287Issue 1-1 en09/09/2008






I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 36. ARAN242: Flexible Upgrade of NRT DCH Data Rate impact onparameters

Parameter Use

Window size for the high throughputmeasurement

This parameter defines slidingmeasurement window size for the highthroughput measurement in uplink anddownlink NRT dedicated channels.

Threshold below the NRT DCH data rate



Table 36. ARAN242: Flexible Upgrade of NRT DCH Data Rate impact onparameters (cont.)

Parameter Use

This parameter defines threshold for thehigh throughput measurement. Thethreshold below the NRT DCH data rateis defined as percentage down from theNRT DCH data rate.

Time to trigger for the high throughputmeasurement

This parameter defines the period of thetime between timing of the throughputgoes below the high bit rate thresholdand the timing of sending highindication to PS.

Dynamic usage of UL NRT DCHHSDPA return Channel

This parameter switch "On" and "Off"The Flexible Upgrade of NRT DataRate and Throughput BasedOptimisation of the PS Algorithm –feature use to UL NRT DCH HSDPAreturn channel.

Usage of the Flexible Upgrade of theNRT DCH data rate

This parameter switch "On" and "Off",the functionality of the Flexible Upgradeof the NRT DCH Data Rate.

Traffic volume threshold for uplink NRTDCH bit rates

The parameter defines the threshold ofdata in RLC buffer of RB in bytes. Thisthreshold triggers the uplink trafficvolume measurement report when theUE is in a Cell_DCH state and DCH isallocated for the radio bearer.

Traffic volume threshold for UL NRTDCH of 128 kbps

The parameter defines the threshold ofdata in RLC buffer of RB in bytes. Thisthreshold triggers the uplink trafficvolume measurement report when theUE is in a Cell_DCH state and 128kbps DCH is allocated for the radiobearer.


The parameter defines the threshold ofdata in RLC buffer of RB in bytes. Thisthreshold triggers the uplink trafficvolume measurement report when theUE is in a Cell_DCH state and 16 kbpsDCH is allocated for the radio bearer.


The parameter defines the threshold ofdata in RLC buffer of RB in bytes. Thisthreshold triggers the uplink trafficvolume measurement report when theUE is in a Cell_DCH state and 256kbps DCH is allocated for the radiobearer.

DN70500287Issue 1-1 en09/09/2008



Table 36. ARAN242: Flexible Upgrade of NRT DCH Data Rate impact onparameters (cont.)

Parameter Use







Tx power of radio link averaging windowsize for DLO

This parameter defines the use oftransmitted code power of radio linkaveraging in I-HSPA adapter fordynamic link optimisation functionality.

Tx power of radio link averaging windowsize for PS

This parameter defines the use oftransmitted code power of radio linkaveraging in I-HSPA adapter for packetscheduling functionality.



Window size for the highthroughput measurement

Threshold below the NRT DCHdata rate

Time to trigger for the highthroughput measurement


Usage of the Flexible Upgrade ofthe NRT DCH data rate

Traffic volume threshold for uplinkNRT DCH bit rates





Traffic volume threshold for ULNRT DCH of 128 kbps






Tx power of radio link averagingwindow size for DLO

Tx power of radio link averagingwindow size for PS

3.4.3 ARAN409: Throughput-based Optimization of the Packet SchedulerAlgorithm


This feature enables the operator to control the utilization of the UL DCHsallocated for the NRT RABs.


OPEX and CAPEX savings can be achieved as the resources are usedmore efficiently. Increased end-user experience is also expected due toimproved service availability and data rates.


The throughput-based optimization algorithm adapts the DCH resourcereservation to meet the actual utilization of the DCH. The bit rate allocatedfor the DCH is downgraded when the utilization of the channel is low. TheDCH may even be released if the utilization is low enough. The UL DCHresource reservations are adapted independently but the CHs can bereleased only if the utilization of the channels in both directions is lowenough at the same time.

Upgrade of the allocated DCH bit rate is carried out according to theexisting upgrade procedures.

DN70500287Issue 1-1 en09/09/2008



The DCH resource adaptation is based on the throughput measurement ofthe channel. The throughput is measured on the MAC layer for eachtransport channel by monitoring the used bit rate.

In the figure Average throughput, the averaged throughput is shown inproportion to the maximum user bit rate of the currently allocated DCH.The upper and lower thresholds trigger the DCH downgrade when thethroughput decreases below the threshold. A longer averaging time isused with the upper threshold, which means that the lower threshold maytrigger before the upper threshold. If the throughput decreases below therelease threshold, the DCH is released. There are operator adjustableparameters for the thresholds and the decreased DCH bit rate allocationscorresponding to the upper and lower thresholds.

This feature significantly decreases the capacity loss caused by too highbit rate allocations in the NW. The optimization concerns mainly the BTSHW.

Figure 5. Average throughput





100%

ave_throughput

downgrade_threshold 1

downgrade_threshold 2

release_threshold

send downgrade request to PS send release request to PS






I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 39. ARAN409: Throughput-based Optimization of the Packet SchedulerAlgorithm impact on parameters

Parameter Use

Threshold below the downgrade bit rate This parameter defines withDCHUtilUpperDowngradeThrBitRateandDCHUtilLowerDowngradeThrBitRateRNP parameters the upper and lowerdowngrade thresholds for the upper andlower throughput measurements.

DN70500287Issue 1-1 en09/09/2008



Table 39. ARAN409: Throughput-based Optimization of the Packet SchedulerAlgorithm impact on parameters (cont.)

Parameter Use

Window size for the lower throughputmeasurement

This parameter defines lower slidingmeasurement window size for theallocated up- and down link NRT DCH.

Lower measurement window size forNRT DCH of 128 kbps

This parameter defines lower slidingmeasurement window size for the NRTDCH that allocated user plane data rateis 128 kbps.









Lower downgrade threshold Parameter defines maximum allowedallocation time for new or changed DCHof the NRT RB of the BackgroundTraffic Service.

Lower downgrade threshold for the NRTDCH of 128 kbps

Defines the minimum allowed bit rate inuplink that can be allocated by the PS









Time to trigger for the lower throughputmeasurement

This parameter defines the period of thetime between timing of the lowerthroughput goes below the lower bitrate threshold and the timing of sendinglower downgrade request.




Parameter Use

Lower time to trigger for the NRT DCHof 128 kbps

This parameter defines the period of thetime between timing of the lowerthroughput goes below the lower bitrate threshold and the timing of sendinglower downgrade request for the NRTDCH that allocated data rate is 128kbps.




This parameter defines the period of thetime between timing of the lowerthroughput goes below the lower bitrate threshold and the timing of sendinglower downgrade request for the NRTDCH that allocated data rate is 32 kbps.




This parameter defines the period of thetime between timing of the lowerthroughput goes below the lower bitrate threshold and the timing of sendinglower downgrade request for the NRTDCH that allocated data rate is 64 kbps.

Guard time for throughput measurement This parameter defines the period oftime during which downgrading theallocated DCH bit rate of the NRT RB isdenied due to throughputmeasurements.

Window size for the release throughputmeasurement

This parameter defines release slidingmeasurement window size for up- anddown link NRT dedicated channels.Release sliding measurement window isused in the release throughputmeasurement.

Time to trigger for the releasethroughput measurement

DN70500287Issue 1-1 en09/09/2008




Parameter Use

This parameter defines the period of thetime between timing of the releasethroughput goes below the release bitrate threshold and the timing of sendinglower downgrade request.

Window size for the upper throughputmeasurement

This parameter defines upper slidingmeasurement window size for theallocated up- and down link NRT DCH.

Upper measurement window size forNRT DCH of 128 kbps

This parameter defines upper slidingmeasurement window size for the NRTDCH that allocated user plane data rateis 128 kbps.









Upper downgrade threshold Parameter defines maximum allowedallocation time for new or changed DCHof the NRT RB of the BackgroundTraffic Service.

Upper downgrade threshold for the NRTDCH of 128 kbps

This parameter defines the target upperdowngrade data rate for the NRT DCHthat allocated user plane data rate is128 kbps.




This parameter defines the target upperdowngrade data rate for the NRT DCHthat allocated user plane data rate is 32kbps.




Parameter Use




This parameter defines the target upperdowngrade data rate for the NRT DCHthat allocated user plane data rate is 64kbps.

Time to trigger for the upper throughputmeasurement

This parameter defines the period of thetime between timing of the upperthroughput goes below the upper bitrate threshold and the timing of sendingupper downgrade request.

Upper time to trigger for the NRT DCHof 128 kbps

This parameter defines the period of thetime between timing of the upperthroughput goes below the upper bitrate threshold and the timing of sendingupper downgrade request for the NRTDCH that allocated data rate is 128kbps.




This parameter defines the period of thetime between timing of the upperthroughput goes below the upper bitrate threshold and the timing of sendingupper downgrade request for the NRTDCH that allocated data rate is 32 kbps.




This parameter defines the period of thetime between timing of the upperthroughput goes below the upper bitrate threshold and the timing of sendingupper downgrade request for the NRTDCH that allocated data rate is 64 kbps.

DN70500287Issue 1-1 en09/09/2008




Parameter Use


This parameter switches "On" and "Off"The Flexible Upgrade of NRT DataRate and Throughput BasedOptimization of the PS Algorithmfeature use to UL NRT DCH HSDPAreturn channel.

Throughput based optimization of thePS algorithm usage

This parameter activates Throughputbased optimization of the PS algorithmfeature. Activation and deactivation canbe done separately for interactive trafficclass within all traffic handling prioritiesand background traffic class traffics.



Threshold below the downgradebit rate

Window size for the lowerthroughput measurement

Lower measurement window sizefor NRT DCH of 128 kbps





Lower downgrade threshold

Lower downgrade threshold for theNRT DCH of 128 kbps





RB DOWNGRADE DUE TOTHROUGHPUT BASEDOPTIMIZATION

RB RELEASE DUE TOTHROUGHPUT BASEDOPTIMIZATION

RL RECONF PREP SYNCH FORDCH MOD DUE THROUGHPUTBASED OPTIMISATION

RL RECONF PREP SYNCH FORDCH DEL DUE THROUGHPUTBASED OPTIMISATION





Time to trigger for the lowerthroughput measurement

Lower time to trigger for the NRTDCH of 128 kbps





Guard time for throughputmeasurement

Window size for the releasethroughput measurement

Time to trigger for the releasethroughput measurement

Window size for the upperthroughput measurement

Upper measurement window sizefor NRT DCH of 128 kbps





Upper downgrade threshold

Upper downgrade threshold for theNRT DCH of 128 kbps





Time to trigger for the upperthroughput measurement

DN70500287Issue 1-1 en09/09/2008




Upper time to trigger for the NRTDCH of 128 kbps






Throughput based optimization ofthe PS algorithm usage

3.4.4 ARAN146: Power Balancing


The feature prevents power drifting and therefore power drifting capacitylosses during soft handovers (SHOs).


Power Balancing feature improves the radio capacity and quality in DL,and also end-user experience in the case of indoor – outdoor transitions.

The feature decreases Dynamic Link optimizations for PS trafficparticularly at cell edge areas.


The power-balancing algorithm for preventing the power drifting is basedon the Reference Transmission Power (Pref) calculated in the I-HSPAAdapter. The Pref corresponds to the average DL transmission power ofthe radio links needed in SHO. The I-HSPA Adapter periodically updatesthe Pref based on the transmitted code power measurements receivedfrom the BTSs. If a new Pref value differs from the previous value, the I-HSPA Adapter sends the updated Pref to the BTSs.



The power-drifting prevention algorithm in the BTS operates with the DLfast closed loop power control during a SHO. The algorithm calculates therequired power correction based on the Pref and the current transmissionpower. The closed loop power control adjusts the transmission poweraccording to the required power correction during a predefined adjustmentperiod.

Figure 6. Power-drifting prevention algorithm








I-HSPAAdapter



GGSN/FlexiISN

UE



MS

PC command PC command

Detection ofPC command

Adjustment ofdownlink power

Detection ofPC command

Adjustment ofdownlink power

DN70500287Issue 1-1 en09/09/2008








OSW I-HSPA I-HSPA Adapter LK Long-term ON/OFFlicense

Management plane

Management data

Parameters:

Table 42. ARAN146: Power Balancing impact on parameters

Parameter Use

Adjustment period time Adjustment period, time for DLtransmitted power to be corrected to thereference power.

Adjustment ratio Parameter defines the adjustment ratio,convergence rate to reference power.

Maximum adjustment step Maximum adjustment step, limitation formaximum TX power correction in onecorrection period.

Trigger for sending the updatedreference power to BTSs

Minimum reference power change. Thisparameter can be used to limit theamount of messaging traffic related toreference power updates.

Power Balancing on/off Parameter defines the usage of PowerBalancing

Reference power subtraction parameter Subtraction parameter for referencepower calculation.



Adjustment period time ALL IUR DL POWER CONTROLMESSAGES IN SRNC





Adjustment ratio

Maximum adjustment step

Trigger for sending the updatedreference power to BTSs

Power Balancing on/off

Reference power subtractionparameter

IUR DL POWER CONTROLMESSAGES FOR POWERUPDATE IN SRNC

ALL IUR DL POWER CONTROLMESSAGES IN DRNC

IUR DL POWER CONTROLMESSAGES FOR POWERUPDATE IN DRNC

ALL IUB DL POWER CONTROLMESSAGES IN SRNC

ALL IUB DL POWER CONTROLMESSAGES IN DRNC

IUB DL POWER CONTROLMESSAGES FOR POWERUPDATE IN SRNC

IUB DL POWER CONTROLMESSAGES FOR POWERUPDATE IN DRNC

3.4.5 IHSW-8: RRC States and State Transitions


I-HSPA Adapter supports the following RRC states: Cell_DCH,Cell_FACH, Cell_PCH, and URA_PCH.


In order to provide efficient radio resource usage, a full set of packet datatransfer states is needed for the management of NRT radio access bearerusers.


The location of the UE to which the RT radio access bearers have beenallocated is always known on the cell level. The location of the UE that hasonly NRT radio access bearers, however, is either known on the cell levelor the URA level, depending on which RRC state the UE is in. The UE isthen in UTRA RRC Connected Mode.

There are four different RRC states in the UTRA RRC Connected Mode:three states where the UE location is known on the cell level and one statewhere the UE location is known on the URA level. These states are'Cell_DCH', 'Cell_FACH', 'Cell_PCH' and 'URA_PCH'.

DN70500287Issue 1-1 en09/09/2008



The different RRC states can be characterized by the following mainaspects:

. In Cell_DCH state the UE has dedicated channel resources (adedicated physical channel). The dedicated resources are reservedfrom I-HSPA BTS for this UTRAN-UE connection.

The location of the UE is known on the cell level based on theexisting radio link(s) between the UE and the BTS(s).

When inactivity of the NRT radio bearer(s) (RBs) and signaling radiobearers (SRBs) is detected, there is no need to keep dedicatedresources reserved for the UE. Thus, the UE is transferred to theCell_FACH state.

. In Cell_FACH state the UE uses UTRAN common channelresources. There are no dedicated resources reserved in the BTSfor the UE. The UE can send uplink data and signaling messages viathe RACH after a random access procedure between UE and theBTS. The I-HSPA Adapter sends downlink data and signalingmessages on the FACH, which is continuously monitored by all theUEs in the Cell_FACH state.

When the amount of user data to be sent via the RACH exceeds apredefined limit, the UE requests dedicated channel resources bysending a capacity request to the I-HSPA Adapter. After this adedicated physical channel is allocated and the UE is transferred tothe Cell_DCH state.

The location of the UE is known on the cell level based on theindications (cell update) sent by the UE when a cell re-selectionoccurs.

When inactivity of the NRT RB(s) and SRB(s) is detected inCell_FACH state, the UE is ordered to transfer to the Cell_PCHstate. This is done in order to conserve the battery of the UE;keeping the UE continuously receiving on FACH wouldunnecessarily consume its battery.

Note that if a UE in Cell_PCH or URA_PCH state wishes to initiateany uplink activity for user plane data or signaling messages, it mustalways execute a random access procedure, perform a transition tothe Cell_FACH state and initiate a Cell Update procedure.



. In Cell_PCH state, the UE can use discontinuous reception (DRX)and must only monitor paging indications (and paging messages)sent by the I-HSPA Adapter. If the I-HSPA Adapter wishes to initiateany downlink activity (for user plane data or signaling messages), itmust first perform a paging procedure to transfer the UE to theCell_FACH state.

The location of the UE is known on the cell level based on the CellUpdate messages sent by the UE when it enters a new cell.

The inactivity detection in Cell_PCH state is based on Cell Updatemessages sent by the UE. When a predefined maximum timeallowed for user inactivity is exceeded, the RRC connection for thisUE is released and the UE transfers to the idle mode.

. In URA_PCH state, the UE can use DRX and must only monitorpaging indications and paging messages sent by the I-HSPAAdapter. If the I-HSPA Adapter wishes to initiate any downlinkactivity for user plane data or signaling messages, it must firstperform a paging procedure to transfer UE to the Cell_FACH state.

The location of the UE is known on the URA level based on the URAUpdate messages sent by the UE when a URA change occurs.

The inactivity detection in URA_PCH state is based on the URAUpdate messages sent by the UE. When a predefined maximumtime allowed for user inactivity is exceeded, the RRC connection forthis UE is released and the UE transfers to the idle mode.

HSDPA RRC State Handling feature provides efficient radio and hardware(DSP) resource usage in the RAN and conserves UE battery by enablingthe state transitions from Cell_DCH state to Cell_FACH or Cell_PCH statefor the HSDPA users. When inactivity or low utilization of the radio bearer(s) and signaling radio bearer(s) is detected for an HSDPA user, there is noneed to keep dedicated resources reserved for the UE, and thus the UE istransferred to the Cell_FACH ,Cell_PCH state or URA_PCH.







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 45. IHSW-8: RRC States and State Transitions impact on parameters

Parameter Use

Shared URA identities of theneighboring Adapter

List of shared URA identities of theneighboring Adapter.

I-HSPA neighboring Adapter sharedURA identity

This parameter defines the shared URAidentity of the neighboring Adapter.



Shared URA identities of theneighboring Adapter





I-HSPA neighboring Adaptershared URA identity

3.4.6 ARAN2.0107: RRC Connection Re-establishment


The purpose of this procedure is to re-establish a lost RRC connection.When a UE loses the radio connection due to radio link failure inCELL_DCH state, the UE may initiate a new cell selection by transiting toCELL_FACH state. UE initiates the procedure by sending the RRC: CellUpdate message with the proper cause value. When I-HSPA Adapterdiscovers that the RRC connection is lost, it releases internally all RT RBs.The NRT RBs can be kept up for a predefined time period.







Table 46. Software dependencies for feature ARAN2.0107

I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008



Table 47. Software sales information for feature ARAN2.0107




Management plane

Management data




RRC RE-ESTABLISHSUCCESS NRT

RRC RE-ESTABLISH FAILUE NRT

RRC RE-ESTABLISH FAILNO REPLY NRT


3.5 Location services

3.5.1 ARAN2.0041: LCS - Cell Coverage-Based (RTT) with GeographicalCoordinates


CI + RTT provides medium accuracy end-user location information foremergency calls or Location Based Services.


Low cost location solution for Location Based Services and a fall-backlocation method for emergency calls.




The cell coverage-based positioning method is based on the fact that theRAN knows which cell is the serving cell of the UE. Information about theserving cell is always available in RAN, because an RRC connection is setup before the positioning is started.

The cell coverage-based location information can be indicated either asthe Service Area that the UE is currently in (in the form of Service AreaIdentity) or as the geographical coordinates of the location in relation to theserving cell.

If the serving area of the UE is requested, the I-HSPA Adapter maps thecurrent serving cell to the service area ID (SAI) and returns the SAI to thecore network. The same service area ID may include several cells.

If the geographical coordinates are requested, the location informationincludes estimated geographical coordinates of the UE and an indicationof the achieved accuracy of the location estimate. When the geographicalcoordinates are used as location information, the estimated position of theUE can be determined as the location within the serving cell. Thegeographical location estimate is obtained by combining information onthe cell-specific geographical location of the BTS with signal Round TripTime (RTT) measurements between the BTS and the UE. If the UE is insoft(er) handover, the cell-specific information and the RTT measurementsare combined and used from all of the active set cells. If the RTTmeasurements fail, the cell-specific cell area information is used toformulate the UE position estimate.

Figure 7. Cell coverage-based location information


BTS

RTT MeasurementError Margins

Cell coverage area= "Service Area"

Round trip time

CI + RTT

DN70500287Issue 1-1 en09/09/2008







I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 50. ARAN2.0041: LCS - Cell Coverage-Based (RTT) with GeographicalCoordinates impact on parameters

Parameter Use

LCS functionality The operator can enable or disable theLCS functionality with this parameter. Ifthe parameter is enabled the cell id-based method is in use.

Antenna Bearing



Table 50. ARAN2.0041: LCS - Cell Coverage-Based (RTT) with GeographicalCoordinates impact on parameters (cont.)

Parameter Use

Antenna direction measuredcounterclockwise from North (indegrees).

Antenna HPBW (Half Power BeamWidth) for Cell

Half power beam width in degrees (3dBangle) of the antenna.

Antenna Coordinates Coordinates of the TX antenna of thecell in WGS-84 format.

Antenna Coordinates Altitude Coordinates of the TX antenna of thecell in WGS-84 format (altitude)

Antenna Coordinates Altitude Direction This parameter is used to identify thegeographical coordinates of theantenna. Altitude: direction (height,depth).

Antenna Coordinates Altitude of GroundLevel

Coordinates of the TX antenna of thecell in WGS-84 format (altitude ground).Altitude measured from the sea level tothe TX antenna: meters (0..10000).

Antenna Coordinate Latitude Latitude of the TX antenna of the cell.

Antenna Coordinates Latitude Degrees Latitude degrees of the TX antenna ofthe cell.

Antenna Coordinates Latitude Fractions Latitude fractions of the TX antenna ofthe cell.

Antenna Coordinates Latitude Minutes Latitude minutes of the TX antenna ofthe cell.

Antenna Coordinates Latitude Seconds Latitude seconds of the TX antenna ofthe cell.

Antenna Coordinates Latitude Sign Latitude sign of the TX antenna of thecell.

Antenna Coordinate Longitude Longitude of the TX antenna of the cell.

Antenna Coordinates Longitude Degrees Longitude degrees of the TX antenna ofthe cell.

Antenna Coordinates LongitudeFractions

Longitude fractions of the TX antennaof the cell.

Antenna Coordinates Longitude Minutes Longitude minutes of the TX antenna ofthe cell.

Antenna Coordinates LongitudeSeconds

Longitude seconds of the TX antennaof the cell.

Antenna Coordinates Longitude Sign Longitude sign of TX antenna of thecell.

Coverage Type Describes the type of coverage.

DN70500287Issue 1-1 en09/09/2008




Parameter Use

Environment characterisation This parameter defines environmentcharacterisation.

Maximum Cell back radius Gives maximum radius of antenna backradiation beam in meters.

Maximum cell radius Gives maximum radius of antenna mainradiation beam in meters.

Repeater exist Informs if repeater exists in the cell.

LCSE UTRAN Cell Id Parameter defines Utran Cellidentification. Structure includes PLMN-id, RNC-id and Cell id.

Cell Identifier The parameter identifies the cell withina I-HSPA adapter.

PLMN identity A Public Land Mobile Network isuniquely identified by its PLMN identity

Mobile Country Code Unique country identification.

Mobile Network Code Unique network identification withincountry.

Mobile Network Code Length This parameter defines whether 2 or 3digits are used in Mobile Network Code.

RNC Identifier A unique identification for an I-HSPAadapter node within the UTRAN.

WLCSE Id Parameter defines the WLCSEidentification.

CIRTT Shape Priority List forEmergency Calls

This list defines the priorities of theEmergency call CI+RTT locationcalculation shapes.

CIRTT Arc Priority for Emergency Calls This parameter defines the priority ofthe Ellipsoid Arc for emergencylocationing shape.

CIRTT Point Priority for EmergencyCalls

This parameter defines the priority ofthe Ellipsoid point for emergencylocationing shape.

CIRTT Point And Altitude Priority forEmergency Calls

This parameter defines the priority ofthe Ellipsoid point with altitude foremergency locationing shape.

CIRTT Point And Circle Priority ForEmergency Calls

This parameter defines the priority ofthe Ellipsoid point with uncertainty circlefor emergency locationing shape.

CIRTT 3D Point And Ellipse Priority ForEmergency Calls




Parameter Use

This parameter defines the priority ofthe Ellipsoid point with altitude anduncertainty Ellipsoid for emergencylocationing shape.

CIRTT Point And Ellipse Priority ForEmergency Calls

This parameter defines the priority ofthe Ellipsoid point with uncertaintyEllipse for emergency locationingshape.

CIRTT Polygon Priority for EmergencyCalls

This parameter defines the priority ofthe Polygon for emergency locationingshape.

CIRTT Shape Priority List for Non-Emergency Calls

The list defines the shape priorities forthe CI+RTT location calculation.

CIRTT Arc Priority This parameter defines the Ellipsoid Arcshape priority.

CIRTT Point Priority This parameter defines the Ellipsoidpoint shape priority.

CIRTT Point And Altitude Priority This parameter defines the priority ofthe Ellipsoid point with altitude shape.

CIRTT Point And Uncertainty CirclePriority

This parameter defines the priority ofthe Ellipsoid point with uncertainty circleshape.

CIRTT 3D Point And Ellipse Priority This parameter defines the priority ofthe Ellipsoid point with altitude anduncertainty Ellipsoid shape.

CIRTT Point And Uncertainty EllipsePriority

This parameter defines the priority ofthe Ellipsoid point with uncertaintyEllipse shape.

CIRTT Polygon Priority This parameter defines the priority ofthe Polygon shape.

Confidence Area Level Parameter informs how many percent ofrange difference measurement lieswithin the confidence area that isreported.

LCS Interface option This parameter indicates to SMLCwhich interface is used for enquiring A-GPS data.

Network indicator for SAS The network indicator defines thesignaling network to which the signalingpoint belongs. The network indicator forSAS is used for SCCP connections inthe Iupc interface.

DN70500287Issue 1-1 en09/09/2008




Parameter Use

Location Reporting Delay Tolerantresponse time

Parameter defines the exact maximumtime to process when CN hasrequested direct reporting with delaytolerant response time.

Location Reporting Low DelayResponse time

Parameter defines the exact maximumtime to process when CN hasrequested direct reporting with lowdelay response time.

Signalling Point Code of SAS The code that uniquely identifies thesignaling point in the signalling network.Signalling Point Code of SAS is usedfor SCCP connections in the Iupcinterface.

UE based A-GPS This parameter enables and disablesUE based A-GPS using the externalreference network feature. If LCSfunctionality is disabled, UE basedAGPS is also disabled

WSMLC Id Parameter defines SMLC identification.



LCS functionality

Antenna Bearing

Antenna HPBW (Half Power BeamWidth) for Cell

Antenna Coordinates

Antenna Coordinates Altitude

Antenna Coordinates AltitudeDirection

Antenna Coordinates Altitude ofGround Level

Antenna Coordinate Latitude

Antenna Coordinates LatitudeDegrees

Antenna Coordinates LatitudeFractions

Antenna Coordinates LatitudeMinutes

UE RXTX TIME DIFFERENCEPOSITIONING CAPABILITY TYPE2

MEAS REPORT MESSAGESWITH PERIODIC REPORTINGRESULTS

LCS REQUESTS

LCS REQUESTS FOREMERGENCY CALL

FAILED LCS REQUESTS

FAILED LCS REQUESTS FOREMERGENCY CALL

SUCCESSFUL HIGH PRIORITYLCS REQ: ACCURACY CODESFULLFILLED BY CELL ID/RTT

SUCCESSFUL NORMALPRIORITY LCS REQ: ACCURACYCODES FULLFILLED BY CELL ID/RTT





Antenna Coordinates LatitudeSeconds

Antenna Coordinates Latitude Sign

Antenna Coordinate Longitude

Antenna Coordinates LongitudeDegrees

Antenna Coordinates LongitudeFractions

Antenna Coordinates LongitudeMinutes

Antenna Coordinates LongitudeSeconds

Antenna Coordinates LongitudeSign

Coverage Type

Environment characterisation

Maximum Cell back radius

Maximum cell radius

Repeater exist

LCSE UTRAN Cell Id

Cell Identifier

PLMN identity

Mobile Country Code

Mobile Network Code

Mobile Network Code Length

RNC Identifier

WLCSE Id

CIRTT Shape Priority List forEmergency Calls

CIRTT Arc Priority for EmergencyCalls

CIRTT Point Priority forEmergency Calls

CIRTT Point And Altitude Priorityfor Emergency Calls

CIRTT Point And Circle PriorityFor Emergency Calls

CIRTT 3D Point And EllipsePriority For Emergency Calls

CIRTT Point And Ellipse PriorityFor Emergency Calls

SUCCESSFUL HIGH PRIORITYLCS REQ: ACCURACY NOTFULLFILLED BY CELL ID/RTT

SUCCESSFUL NORMALPRIORITY LCS REQ: ACCURACYNOT FULLFILLED BY CELL ID/RTT

SUCCESSFUL HIGH PRIORITYLCS REQ: HORIZONTALACCURACY NOT FULLFILLEDBY CELL ID/RTT

SUCCESSFUL NORMALPRIORITY LCS REQ:HORIZONTAL ACCURACY NOTFULLFILLED BY CELL ID/RTT

FAILED HIGH PRIORITY LCSREQ - CELL ID/RTT

FAILED NORMAL PRIORITY LCSREQ - CELL ID METHOD

FAILED LCS REQUESTS DUE TOANCHORING

REJECTED LCS REQUESTSDUE TO DUPLICATE REQUEST

SAI CHANGE REPORTING STOPREQUESTS FROM CN

DN70500287Issue 1-1 en09/09/2008




CIRTT Polygon Priority forEmergency Calls

CIRTT Shape Priority List for Non-Emergency Calls

CIRTT Arc Priority

CIRTT Point Priority

CIRTT Point And Altitude Priority

CIRTT Point And UncertaintyCircle Priority

CIRTT 3D Point And EllipsePriority

CIRTT Point And UncertaintyEllipse Priority

CIRTT Polygon Priority

Confidence Area Level

LCS Interface option

Network indicator for SAS

Location Reporting Delay Tolerantresponse time

Location Reporting Low DelayResponse time

Signalling Point Code of SAS

UE based A-GPS

3.5.2 ARAN223: UE-Based A-GPS Using External Reference Network


A-GPS location method utilizes the assistance data sent from MobileLocation Centre to a UE. With this assistance data, the UE's GPS receiveris able to calculate a position faster and in weaker GPS satellite signalconditions. The UE returns the position coordinates to the NW.


Increased end-user experience is achieved because of better positioningaccuracy, in comparison with the accuracy provided with the cell ID / RTT-based positioning method.




When the GPS is cooperating with UTRAN, the NW can assist the UE toimprove the stand-alone GPS receiver performance in several ways. TheA-GPS method can:

. Reduce the GPS receiver start-up and acquisition times: the searchwindow can be limited and the measurements speed up significantly.

. Increase the GPS sensitivity: time information and navigationmessages are obtained via UTRAN, so GPS can operate also inhigh noise rate situations, for example indoors and in buildingblockage.

. Consume less handset power than a stand-alone GPS receiverdoes: this is due to rapid start-up times as the GPS can be in idlemode when it is not needed.

After a locationing request has been received from the CN, the I-HSPAAdapter's integrated SMLC calculates the CI + RTT location estimate forthe target. If the locationing accuracy requested by the CN cannot befulfilled, the A-GPS method is selected.

In a UE-based A-GPS, all the above-mentioned improvements can beachieved with additional assistance data retrieved from the stand-aloneSMLC (SAS). The reference NW can be connected to the I-HSPA Adaptervia standard 3GPP Iu-PC interface. The I-HSPA Adapter is able toconstruct the GPS assistance information elements according to 3GPPstandards. At the request of an UE- or NW-based application, theassistance data is transmitted from the I-HSPA Adapter to the UE. The UEuses the assistance data and its own GPS measurements to locate itselfand sends the locationing results (location coordinates) back to the I-HSPA Adapter, from which the I-HSPA Adapter forwards the results to theCN.

DN70500287Issue 1-1 en09/09/2008



Figure 8. A-GPS using external reference network








I-HSPAAdapter


UE

A-GPS Assistance data2.

Flexi I-BTS(inc. SMLC)

HSPAdevice

Iupc

Externalreferencenetwork

SAS

ephemeris,almanac,clock etc.

A-GPS Assistance data request1.x, y, z4.

A-GPS Assistance data3.

GPSchip

ephemeris,almanac,clock etc.



Table 51. Software dependencies for feature ARAN223 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN









Management plane

Management data

Parameters:

Table 53. ARAN223: UE-Based A-GPS Using External Reference Networkimpact on parameters

Parameter Use

LCS Interface option This parameter indicates to SMLCwhich interface is used for enquiring A-GPS data.

Network indicator for SAS The network indicator defines thesignaling network to which the signalingpoint belongs. The network indicator forSAS is used for SCCP connections inthe Iupc interface.

DN70500287Issue 1-1 en09/09/2008



Table 53. ARAN223: UE-Based A-GPS Using External Reference Networkimpact on parameters (cont.)

Parameter Use

Signalling Point Code of SAS The code that uniquely identifies thesignaling point in the signalling network.Signalling Point Code of SAS is usedfor SCCP connections in the Iupcinterface.

UE based A-GPS This parameter enables and disablesUE based A-GPS using the externalreference network feature. If LCSfunctionality is disabled, UE basedAGPS is also disabled.



LCS Interface option

Network indicator for SAS

Signalling Point Code of SAS

UE based A-GPS

UE SUPPORT FOR NETWORKASSISTED GPS

RECEIVED LOCATION RELATEDDATA REQUEST

SENT LOCATION RELATED DATARESPONSE

SENT LOCATION RELATED DATAFAILURE

ASSISTANCE DATA DELIVERYMESSAGES

SUCCESSFUL HIGH PRIORITYLCS REQ: ACCURACY CODESFULFILLED BY AGPS

SUCCESSFUL NORMALPRIORITY LCS REQ: ACCURACYCODES FULFILLED BY AGPS

SUCCESSFUL HIGH PRIORITYLCS REQ: ACCURACY NOTFULFILLED BY AGPS

SUCCESSFUL NORMALPRIORITY LCS REQ: ACCURACYNOT FULFILLED BY AGPS

SUCCESSFUL HIGH PRIORITYLCS REQ: HORIZONTALACCURACY NOT FULFILLED BYAGPS

3303 NO A-GPS SERVICE

3304 DECREASED A-GPSSERVICE




SUCCESSFUL NORMALPRIORITY LCS REQ:HORIZONTAL ACCURACY NOTFULFILLED BY AGPS

FAILED HIGH PRIORITY LCSREQ AGPS

FAILED NORMAL PRIORITY LCSREQ AGPS

RRC MEASUREMENT REPORTWITH AGPS DATA REQUEST

3.5.3 ARAN815: Point-to-Point Iu-PC Interface


Iu-PC is a 3GPP specified interface between the RNC and a stand-aloneSMLC (Serving Mobile Location Center). It supports point-to-point GPSassistance data delivery between an SMLC and a UE. With this assistancedata, the UE's GPS receiver is able to calculate position faster and inweaker GPS satellite signal conditions.


CAPEX and OPEX savings are achieved due to possibility to usestandardized interface towards a stand-alone SMLC. This enables morefreedom in SMLC vendor selection. Point-to-point Iu-PC interface supportsUE-based and NW-based A-GPS location services.


This feature provides the support of the 3GPP Iu-pc interface in the I-HSPA Adapter. The Iu-pc interface is a logical interface for theinterconnection of the Stand-Alone SMLC (SAS) and I-HSPA Adapter viathe PCAP protocol. The SAS provides GPS assistance data to the Adapterand may perform the position calculation function for various positioningmethods.

The PCAP provides the signaling services between the I-HSPA Adapterand SAS. PCAP services are categorized as follows:

DN70500287Issue 1-1 en09/09/2008



. Position Calculation Services are related to a single UE and involvethe transfer of UE positioning measurement data and UE positionestimate data over the Iu-pc interface between the I-HSPA Adapterand SAS.

. Information Exchange Service involves the transfer of GPS relateddata over the Iu-pc interface between the I-HSPA Adapter and SAS.

This feature also includes the basic functionality (UE based A-GPS) overthe Iu-PC interface, and it enables the NW-based A-GPS.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data




ASSISTANCE DATA REQUESTS TOSAS

UNSUCCESSFUL ASSISTANCEDATA REQUESTS USING SAS

SUCCESSFUL ASSISTANCE DATADELIVERY FROM SAS

ASSISTANCE DATA DELIVERYFAILURE FROM SAS

ERROR INDICATIONS FROM SAS


3.5.4 ARAN1219: Latency Statistics for UE Positioning


Statistics of location system's latencies are collected for further analysis.


Better end-user experience can be achieved as the operator haspossibilities to monitor and verify improved location system's performance.


Latency statistics for UE Positioning present new statistical latencyinformation concerning the UE positioning. The latency statistics presentoverall locationing service latencies, and detailed latency statistics for cell-based and A-GPS positioning methods.





DN70500287Issue 1-1 en09/09/2008






I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data



No parameters related to thisfeature

SUM OF CIRTT LATENCY

DENOM CIRTT METHOD

CIRTT LATENCY LESS THAN 2SECONDS

CIRTT LATENCY BETWEEN 2 TO5 SECONDS

CIRTT LATENCY OVER 5SECONDS

SUM OF GPS LATENCY

DENOM GPS METHOD





GPS LATENCY LESS THAN 5SECONDS

GPS LATENCY BETWEEN 5 TO15 SECONDS

GPS LATENCY OVER 15SECONDS

SUM OF LCS TOTAL LATENCY

SQUARED SUM OF LCS TOTALLATENCY

DENOM LCS TOTAL LATENCY

SUM OF EMERGENCY CIRTTLATENCY

DENOM EMERGENCY CIRTTMETHOD

EMERGENCY CIRTT LATENCYLESS THAN 2 SEC

EMERGENCY CIRTT LATENCYBETWEEN 2 to 5 SEC

EMERGENCY CIRTT LATENCYOVER 5 SEC

SUM OF EMERGENCY GPSLATENCY

DENOM EMERGENCY GPSMETHOD

EMERGENCY GPS LATENCYLESS THAN 5 SECONDS

EMERGENCY GPS LATENCYBETWEEN 5 to 15 SECONDS

EMERGENCY GPS LATENCYOVER 15 SECONDS

SUM OF EMERGENCY LCSTOTAL LATENCY

SQUARED SUM OFEMERGENCY LCS TOTALLATENCY

DENOM EMERGENCY LCSTOTAL LATENCY

DN70500287Issue 1-1 en09/09/2008



3.6 Radio Access Bearer combinations

3.6.1 ARAN1.010: DCH UL NRT PS Data Bearer Package for I-HSPA


The Core Network (CN) service is negotiated with Call Control (CC)signaling, which uses the existing signaling link between the UserEquipment (UE) and Radio Access Network (RAN), and the signalingconnection between the RAN and CN. When the CN and UE havecompleted the service negotiation, the CN requests the radio accessbearer from the RAN.

If the radio access bearer parameters are admitted, the radio accessbearer is set up. The I-HSPA Adapter starts the activation procedures forthe required resources at the radio interface and establishes the userplane connections.

For NRT (non-real-time) services, the radio access bearer can beestablished without immediate reservation of radio resources. The radioresources will be allocated when requested, using the signaling linkbetween the UE and the I-HSPA Adapter.

Nokia Siemens Networks I-HSPA Release 1 supports 3GPP Rel. 5HSDPA and with following respective DCH uplinks. Supported bearersubclasses are PS interactive and background:

. 16 k

. 64 k

. 128 k

. 384 k

Radio Access Bearer Release:

After the UE and the CN have negotiated the release of the CN service,the CN commands the RAN to release the radio access bearer(s). The I-HSPA Adapter sends an indication of the radio access bearer release tothe UE and releases the radio resources and user plane connections onthe Iu and Iur interfaces.

If a radio access bearer release is required by the RAN (for example, if aradio connection to the UE is lost), the RAN may request the CN to releasethe radio access bearer(s).










I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

DN70500287Issue 1-1 en09/09/2008



Table 60. ARAN1.010: DCH UL NRT PS Data Bearer Package for I-HSPAimpact on parameters

Parameter Use

HSDPA 16 kbps UL DCH return channelon/off switch

This parameter defines whether theusage of the 16 kbps UL DCH returnchannel is allowed for HSDPA.

Initial bitrate for HSDPA associated ULDCH

The parameter determines the initial bitrate for scheduling of the HSDPAassociated UL DCH.

Minimum bitrate for HSDPA associatedUL DCH

The parameter determines the minimumallowed bit rate in the uplink that can beallocated by the PS to the HSDPAassociated UL DCH when downgradingthe bit rate.



HSDPA 16 kbps UL DCH returnchannel on/off switch

Initial bitrate for HSDPAassociated UL DCH

Minimum bitrate for HSDPAassociated UL DCH


3.7 HSDPA

3.7.1 ARAN763: Basic HSDPA with QPSK and 5 Codes


This feature provides the basic High Speed Downlink Packet Access(HSDPA) functionality. HSDPA is based on a technique where scheduling,link adaptation, and physical layer re-transmission handling are in theBTS, improving the downlink packet data performance with the achievedhigh throughput and peak rates and reduced delays.




HSDPA offers a lower cost per bit and potentially creates new applicationareas with higher data rates and lower delay variance. This feature bringsthe basic performance gain of HSDPA to the operator, that is, a cellthroughput gain of up to 60%, as well as higher peak data rates up to 1.8Mbps.


This feature allows a 1.8 Mbps air interface peak rate with QPSKmodulation. Only a single High Speed Shared Control Channel (HS-SCCH) taking care of the HSDPA downlink signaling needs is required, ascode multiplexing is not supported.

HS-DSCH is transmitted to only one cell at a time from the BTS, that is, it istime multiplexed between the different cells of the BTS.

The basic characteristics of the feature are listed below:

. Maximum number of HSDPA users per BTS is 16.

. Maximum HS-PDSCH codes per cell is 5.

. Maximum HS-SCCH codes per cell is 1.

. Maximum HS-PDSCH codes per UE is 5.

HSDPA channel encoding/decoding functionality includes HS-DSCH andHS-SCCH encoding in the downlink and HS-DPCCH decoding in theuplink.

. HSDPA ARQ handling in MAC-hs

. HS-DSCH link adaptation based on CQI from the UEs

. Up to 3 cells per BTS can be enabled for HSDPA

Even though the maximum number of the HS-PDSCH codes is 5 per UE,all the UE categories (1-12) are still supported. Other categories will betreated the same way as categories 11-12.

This feature also adjusts the High Speed Shared Control Channel(HSSCCH) transmitting power according to the required power level at theUE. It reduces the average power overhead required for the HS-SCCH,compared to using a fixed transmit power level. The HS-SCCH transmitpower is adjusted every TTI based on the CQIs and Ack/Nack/DTXs

DN70500287Issue 1-1 en09/09/2008



received from the UEs. It is estimated that the HSDPA cell throughput gainprovided by this feature is 5% - 20% (compared to using fixed HSSCCHpower), depending on the environment and the total power allocated toHSDPA.








I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:



Table 63. ARAN763: Basic HSDPA with QPSK and 5 Codes impact onparameters

Parameter Use

HSDPA HOPS identifier The parameter identifies the parameterset (HOPS object) controlling the intra-frequency handovers of a user havingHS-DSCH allocated.

AM RLC configuration for PS NRT withHS-DSCH

This parameter defines theretransmission parameters for the AMRLC of the PS interactive orbackground RAB that is using HS-DSCH in its data transfer direction.

AM RLC status reports count for PSNRT with HS-DSCH

This parameter defines the minimumnumber for the AM RLC status reportsthat will be received for the PSinteractive and background radiobearers in the duration of the RLCtransmission window when data istransferred over HS-DSCH.

AM RLC retransmission filter for PSNRT with HS-DSCH

This parameter defines the AMD PDUretransmission filtering period in relationto the RLC round trip time for the PSinteractive and background radiobearers when data is transferred overHS-DSCH.

AM RLC MaxDAT transmissions for PSNRT with HS-DSCH

This parameter defines the value of theRLC protocol parameter MaxDAT forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over HS-DSCH.

AM RLC MaxMRW transmissions for PSNRT with HS-DSCH

This parameter defines the value of theRLC protocol parameter MaxMRW forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over HS-DSCH.

AM RLC maxRST transmissions for PSNRT with HS-DSCH

This parameter defines the value of theRLC protocol parameter MaxRST forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over HS-DSCH.

AM RLC status period max for PS NRTwith HS-DSCH

This parameter defines the maximumstatus reporting period of the AM RLCin relation to the RLC round trip time forthe PS interactive and background radiobearers when the data is transferredover HS-DSCH.

AM RLC status period min for PS NRTwith HS-DSCH

DN70500287Issue 1-1 en09/09/2008



Table 63. ARAN763: Basic HSDPA with QPSK and 5 Codes impact onparameters (cont.)

Parameter Use

This parameter defines the minimumstatus reporting period of the AM RLCfor the PS interactive and backgroundradio bearers when data is transferredover HS-DSCH.

AM RLC period Poll_PDU for PS NRTwith HS-DSCH

This parameter defines the minimumvalue of the RLC protocol parameterPoll_PDU for the AM RLC entity of thePS interactive and background radiobearers when data is transferred overHS-DSCH.

AM RLC period Poll_SDU for PS NRTwith HS-DSCH

This parameter defines the value of theRLC protocol parameter Poll_SDU forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over HS-DSCH.

AM RLC period Poll_Window for PSNRT with HS-DSCH

This parameter defines the value of theRLC protocol parameter Poll_windowfor the AM RLC entity of the PSinteractive and background radiobearers when data is transferred overHS-DSCH.

AM RLC status report triggers for PSNRT with HS-DSCH

This parameter activates anddeactivates polling and status reportingtriggers and the RLC timers for the AMRLC entity of the PS interactive orbackground RAB that is using HS-DSCH in its data transfer direction.

AM RLC round trip times with HS-DSCH This parameter defines the AM RLCRound Trip Time (RTT) for the downlinkdata transfer when the radio bearer ismapped to the HS-DSCH.

AM RLC round trip time with HS-DSCH/DCH

This parameter defines the AM RLCRound Trip Time (RTT) for the downlinkdata transfer over HS-DSCH when theradio bearer is mapped to the DCH inUL.

AM RLC round trip time with HS-DSCH/E-DCH

This parameter defines the AM RLCRound Trip Time (RTT) for the downlinkdata transfer with HS-DSCH when theradio bearer is mapped to the E-DCH inUL.

Averaging window of the CPICH Ec/Nomeasurement




Parameter Use

This parameter determines theaveraging window for the periodicalCPICH Ec/No measurement reporting,which is used as a criterion for theserving HS-DSCH cell changeprocedure.

DCH to HS-DSCH switch CPICH Ec/Noreporting period

This parameter determines the reportingperiod of the CPICH Ec/Nomeasurement that is used as a criterionfor starting the DCH to HS-DSCHswitch.

CPICH Ec/No threshold for serving HS-DSCH cell change

Parameter determines the absoluteCPICH Ec/No threshold for the servingHS-DSCH cell change procedure.

Reporting period of the CPICH Ec/Nomeasurement

This parameter determines the reportingperiod of the CPICH Ec/Nomeasurement, which is used as acriterion for the serving HS-DSCH cellchange procedure.

Minimum interval between serving HS-DSCH cell changes

Parameter determines the minimuminterval between serving HS-DSCH cellchanges due to CPICH Ec/No windowbetween the best cell and the servingHS-DSCH cell.

Window for max repetitive serving HS-DSCH cell changes

Parameter determines the time periodfor calculation of the maximum numberof repetitive serving HS-DSCH cellchanges.

HSDPA channel type switching window This parameter determines themaximum allowed measured CPICH Ec/No difference between the best cell ofthe active set and the potential new HS-DSCH cell in case of DCH to HS-DSCHswitch.

Max number of repetitive serving HS-DSCH cell changes

Parameter determines the maximumnumber of repetitive serving HS-DSCHcell changes during a predefined timeperiod (see parameter relationships). Ifthe maximum number of serving HS-DSCH cell changes is exceeded, HS-DSCH is released.


Parameter determines the averagingwindow for the periodical UL SIRerrormeasurement, which is used as acriterion for serving HS-DSCH cellchange procedure.

DN70500287Issue 1-1 en09/09/2008




Parameter Use


Parameter determines the filteringcoefficient of the UL SIRerrormeasurement which is used as acriterion for serving HS-DSCH cellchange procedure.


Parameter determines the reportingperiod of the dedicated UL SIRerrormeasurement, which is used as acriterion for serving HS-DSCH cellchange procedure. If the value of theparameter is set to 0, SIRerrormeasurement is not used as a criterion.

SIRerror threshold for the serving HS-DSCH cell

The parameter determines the level ofthe UL SIRerror of the serving cell,which initiates serving HS-DSCH cellchange.

SIRerror threshold for the target cell The parameter determines the requiredlevel of the UL SIRerror in the targetcell in order to execute serving HS-DSCH cell change due to DL CPICHEc/No or UL SIRerror.

CPICH Ec/No window for serving HS-DSCH cell selection

The parameter determines themaximum allowed difference betweenthe best cell and the serving HS-DSCHcell. The window is relative to the bestcell in the active set.

Initial bitrate for HSDPA associated ULDCH

The parameter determines the initial bitrate for scheduling of the HSDPAassociated UL DCH.

Minimum bitrate for HSDPA associatedUL DCH

The parameter determines the minimumallowed bit rate in the uplink that can beallocated by the PS to the HSDPAassociated UL DCH when downgradingthe bit rate.

HS-DSCH channel type switch guardtimer

This parameter determines the time thatmust be waited after an HS-DSCH toDCH channel type switching before thechannel type can be switched back toHS-DSCH again.

HS-DSCH guard timer due to lowthroughput

HSDSCHGuardTimerLowThroughput isa UE-specific timer. It is started after arelease of the MAC-d flow, which wastriggered by low throughput. When thetimer is running HS-DSCH allocation isnot allowed to the UE.




Parameter Use

HS-DSCH QoS classes The parameter defines the trafficclasses (TC) and traffic handlingpriorities (THP), which can use HS-DSCH. Value 1 means that both DCHand HS-DSCH can be used and value0 means that only DCH can be used forthe specific TC and THP.

Window size of the MAC-d flowthroughput measurement

This parameter defines the averagingwindow size for the throughputmeasurement of the MAC-d flow. Thethroughput measurement measures thenumber of bits transmitted by MAC-dduring the sliding measurement window.

Low throughput threshold of the MAC-dflow

This parameter defines the lowthroughput threshold of the throughputmeasurement of the MAC-d flow.

Low throughput time to trigger of theMAC-d flow

This parameter defines the lowthroughput time to trigger the timer ofthe throughput measurement of theMAC-d flow.

Low utilisation threshold of the MAC-dflow

This parameter defines the lowutilisation threshold of the throughputmeasurement of the MAC-d flow.

Low utilization time to trigger of theMAC-d flow

This parameter defines the lowutilisation time to trigger the timer of thethroughput measurement of the MAC-dflow.

Retry time for u-plane resourceallocation in Cell_DCH

This timer defines the time periodduring which the user plane DCHresource allocation should succeed.

Weight of NRT DCH UE This parameter defines the weightvalues for HSDPA Dynamic ResourceAllocation and HSUPA.

Weight of NRT DCH UE BG RAB This parameter defines the weight valueof the background traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP1 RAB This parameter defines the weight valueof the Interactive THP1 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP2 RAB

DN70500287Issue 1-1 en09/09/2008




Parameter Use

This parameter defines the weight valueof the Interactive THP2 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP3 RAB This parameter defines the weight valueof the interactive THP3 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of HSPA UE This parameter defines weight valuesfor HSDPA Dynamic ResourceAllocation and HSUPA.

Weight of HSPA UE BG RAB This parameter defines the weight valueof the background traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of HSPA UE THP1 RAB This parameter defines the weight valueof the interactive THP1 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.



PtxnonHSPA averaging window size forLC

This parameter determines theaveraging window size of transmittedcarrier power of all codes not used forHS-PDSCH or HS-SCCH transmission(PtxnonHSDPA) measurement innumber of received PtxnonHSDPAmeasurement results.

HSDPA FMCG identifier The parameter identifies themeasurement control parameter set(FMCG object) controlling the inter-system measurements of a user havingHS-DSCH allocated.

HSDPA FMCI identifier The parameter identifies themeasurement control parameter set(FMCI object) controlling the inter-frequency measurements of a userhaving HS-DSCH allocated.




Parameter Use

HSDPA FMCS identifier The parameter identifies themeasurement control parameter set(FMCS object) controlling the intra-frequency measurements of a userhaving HS-DSCH allocated.

HS-PDSCH code set This parameter defines the HS-PDSCHcode set.

High threshold of PtxTotal for dynamicHSDPA pwr alloc

This parameter defines the threshold ofthe PtxTotal measurement that indicateshigh usage of HSDPA power in thecase of HSDPA dynamic resourceallocation.

DCH PS target adjust period for dynHSDPA pwr alloc

This parameter defines the adjustmentperiod of the target level for DCHpacket scheduling in case HSDPAdynamic resource allocation is used inthe cell.

Max DCH PS target for dynamic HSDPApwr allocation

This parameter defines the maximumallowed target level for DCH packetscheduling when HSDPA dynamicresource allocation is used in the cell.

Min DCH PS target for dynamic HSDPApwr allocation

This parameter defines the minimumallowed target level for DCH packetscheduling when HSDPA dynamicresource allocation is used in the cell.

DCH PS target step down for dynamicHSDPA pwr alloc

This parameter defines the fixed stepsize for decreasing target level for DCHpacket scheduling in the case ofHSDPA dynamic resource allocation.

DCH PS target step up for dynamicHSDPA pwr alloc

This parameter defines the fixed stepsize for increasing target level for DCHpacket scheduling in the case ofHSDPA dynamic resource allocation.



HSDPA HOPS identifier

AM RLC configuration for PS NRTwith HS-DSCH

AM RLC status reports count forPS NRT with HS-DSCH

No counters related to this feature 7772 HSDPA CONFIGURATIONFAILED

7776 HSDPA FAILURE IN WCEL

DN70500287Issue 1-1 en09/09/2008




AM RLC retransmission filter forPS NRT with HS-DSCH

AM RLC MaxDAT transmissionsfor PS NRT with HS-DSCH

AM RLC MaxMRW transmissionsfor PS NRT with HS-DSCH

AM RLC maxRST transmissionsfor PS NRT with HS-DSCH

AM RLC status period max for PSNRT with HS-DSCH

AM RLC status period min for PSNRT with HS-DSCH

AM RLC period Poll_PDU for PSNRT with HS-DSCH

AM RLC period Poll_SDU for PSNRT with HS-DSCH

AM RLC period Poll_Window forPS NRT with HS-DSCH

AM RLC status report triggers forPS NRT with HS-DSCH

AM RLC round trip times with HS-DSCH

AM RLC round trip time with HS-DSCH/DCH

AM RLC round trip time with HS-DSCH/E-DCH

Averaging window of the CPICHEc/No measurement

DCH to HS-DSCH switch CPICHEc/No reporting period

CPICH Ec/No threshold for servingHS-DSCH cell change

Reporting period of the CPICH Ec/No measurement

Minimum interval between servingHS-DSCH cell changes

Window for max repetitive servingHS-DSCH cell changes

HSDPA channel type switchingwindow

Max number of repetitive servingHS-DSCH cell changes







SIRerror threshold for the servingHS-DSCH cell

SIRerror threshold for the targetcell

CPICH Ec/No window for servingHS-DSCH cell selection

Initial bitrate for HSDPAassociated UL DCH

Minimum bitrate for HSDPAassociated UL DCH

HS-DSCH channel type switchguard timer

HS-DSCH guard timer due to lowthroughput

HS-DSCH QoS classes

Window size of the MAC-d flowthroughput measurement

Low throughput threshold of theMAC-d flow

Low throughput time to trigger ofthe MAC-d flow

Low utilisation threshold of theMAC-d flow

Low utilization time to trigger ofthe MAC-d flow

Retry time for u-plane resourceallocation in Cell_DCH

Weight of NRT DCH UE

Weight of NRT DCH UE BG RAB

Weight of NRT DCH UE THP1RAB



Weight of HSPA UE

Weight of HSPA UE BG RAB

Weight of HSPA UE THP1 RAB

DN70500287Issue 1-1 en09/09/2008






PtxnonHSPA averaging windowsize for LC

HSDPA FMCG identifier

HSDPA FMCI identifier

HSDPA FMCS identifier

HS-PDSCH code set

High threshold of PtxTotal fordynamic HSDPA pwr alloc

DCH PS target adjust period fordyn HSDPA pwr alloc

Max DCH PS target for dynamicHSDPA pwr allocation

Min DCH PS target for dynamicHSDPA pwr allocation

DCH PS target step down fordynamic HSDPA pwr alloc

DCH PS target step up fordynamic HSDPA pwr alloc

3.7.2 ARAN233: HSDPA Associated Uplink DPCH Scheduling


This feature selects the data rates that are used for the HSDPA associateduplink return channel.


This feature enables the HSDPA and allows the operator to select thepreferred bit rate to be used for HSDPA associated uplink DCH.


The resource scheduling for the HSDPA associated uplink return channelis based on two parameters: initial bit rate and minimum bit rate. Theseparameters are cell-specific configuration parameters. The bit rates usedin the scheduling are 0K, 16K, 64 kbps, 128 kbps, and 384 kbps.



The initial bit rate is allocated as an uplink return channel bit rate, whenHS-DSCH is selected as a DL transport channel. Once the DCH has beenconfigured, the UE may use the TFC selection to momentarily use a lowerdata rate, for example in the case of power limitations or lack of data to betransmitted. There is an exception to the usage of the initial bit rate: if HS-DSCH selection is performed due to UL capacity request indicating a highdata amount, the highest possible bit rate is allocated.

The minimum bit rate is the lowest bit rate allowed for the UL DCH for loadcontrol purposes. The UL DCH can be reconfigured down to this bit ratedue to the following functionalities:

. RAB Pre-emption (other call may override)

. Decrease of the Retried NRT DCH Bit Rate

. Enhanced Priority Based Scheduling for UL Rel99

. Upgrade of the NRT DCH Data Rate (from initial or lower bit rate)

These procedures will prevent the uplink resources being tied up forexample for only a few 384 kbps users in case of a resource shortage.

The upgrade of the UL DCH is controlled by traffic volume measurement.The traffic volume measurement is active when the allocated bit rate isequal to or lower than the initial bit rate.








I-HSPAAdapter



GGSN/FlexiISN

UE



DN70500287Issue 1-1 en09/09/2008








OSW I-HSPA - -

Management plane






3.7.3 RAN764: HSDPA 16QAM Support


This modulation enables higher HSDPA peak data rates and average cellthroughput.


Improved end-user experience due to increased HSDPA peak data rates.16QAM support increases the peak data rate with a factor of twocompared to a basic HSDPA solution.


This feature increases the HSDPA peak data rate from 1.8 Mbps (QPSKwith 5 codes) to 3.6 Mbps with the use of higher order modulation(16QAM).

The link adaptation algorithm in the BTS (MAC-hs) selects 16QAM whenthe channel quality is sufficient.



It also provides 5% - 20% higher average HSDPA cell throughput,depending on the environment.







Table 66. Software dependencies for feature RAN764

I-HSPAAdapter



GGSN/FlexiISN

UE





Table 67. Software sales information for feature RAN764



ASW I-HSPA BTS LK Long-term ON/OFFlicense

Management plane

Management data


DN70500287Issue 1-1 en09/09/2008







3.7.4 ARAN839: HSDPA 16 Users per Cell


This feature provides support for 16 HSDPA users per cell.


Increased revenue and increased end-user experience are achievedthanks to increased HSDPA capacity. The HSDPA capacity is increasedboth in terms of the number of users supported and cell throughput. Theincreased capacity improves the end-user performance with higheraverage bitrates.


The maximum number of HSDPA users per BTS is enhanced by allocatingdedicated schedulers for the selected cells of the BTS (maximum 3 cellsper BTS), instead of having one timeshared scheduler for the BTS.

This functionality enables up to 16 simultaneous HSDPA users per cell.High speed downlink shared channel (HS-DSCH) can then be transmittedto all cells of the BTS with 3.6 Mbps maximum throughput per cell, bringingthe HSDPA performance gains for each cell independently of the data ratein the other cells of the same BTS.










I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






3.7.5 ARAN1033: HSDPA 48 Users per Cell


The maximum number of simultaneous HSDPA users in a cell is increasedto 48.

DN70500287Issue 1-1 en09/09/2008




CAPEX and OPEX savings are achieved by the increased amount ofsimultaneous HSDPA end-users in a cell. Instant access to data servicesafter momentary inactivity periods improves the end-user experience.


This feature allows 48 simultaneous HSDPA users per cell. Thisconsumes one submodule in Flexi BTS per cell.

A higher number of users allows higher user volumes to be served. Theend-user experience is improved in any ON/OFF type of service, that is, aservice with momentary inactivity periods, since higher number of userscan be kept on cell_DCH state for longer periods. Such services are, forexample, web or WAP browsing and gaming.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data

Parameters:

Table 72. ARAN1033: HSDPA 48 Users per Cell impact on parameters

Parameter Use

HSDPA 48 users enabled This parameter defines whether thefeature HSDPA 48 Users per Cell is inuse.



HSDPA 48 users enabled No counters related to this feature No alarms related to this feature

3.7.6 ARAN852: HSDPA 10 and 15 Codes


HSDPA 15 Codes feature allows higher peak rates as well as largercapacity. The average cell throughput is increased by about 50% in amacro cell environment compared to having 5 codes. The peak bit rate forsingle user is 7.2 Mbps. Peak cell level total throughput is 10.8 Mbps (withcode multiplexing).


Higher data rates improve the end-user experience. HSDPA 15 codesprovides more cell capacity compared to HSDPA 10 codes solution. Newdata service availability results in increased revenue. Increased cellcapacity means savings in CAPEX and OPEX.

DN70500287Issue 1-1 en09/09/2008




HSDPA 15 codes feature is a further evolution of the features BasicHSDPA with QPSK and 5 codes and HSDPA 16QAM support, allowinghigher peak data rates and increased average cell throughput. The peakbit rate for single user is 7.2 Mbps. Peak cell level total throughput is 10.8Mbps (with code multiplexing).

Depending on the UE category, the RLC payload size of 640 bits may beused when the HSDPA 15 Codes is enabled.

HSDPA 15 Codes allows higher peak rates as well as larger capacity. Theaverage HSDPA cell throughput depends on the maximum number ofallocated HS-PDSCH codes. When allocating the maximum of 10HSPDSCH codes, the average cell throughput is increased by about 30%in a macro cell environment compared to having only 5 HS-PDSCH codes.

Allocating the maximum of 15 HS-PDSCH codes increases the averagecell throughput by about 50% compared to the same 5-code referencescenario. In a frequency layer dedicated for HSDPA, the gains aresignificantly higher, as well as in micro cells.

If HSDPA code multiplexing is used, the maximum cell level throughput forsimultaneously scheduled HSDPA users is 14.4 Mbps.

HSDPA category 9 UE is capable of 10 Mbps peak air interface bit ratewith 15 codes. With this feature a category 9 UE may receive data with itsmaximum bit rate when 15 codes for HSDPA are allocated in the cell.










I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 75. ARAN852: HSDPA 10 and 15 Codes impact on parameters

Parameter Use

HS-PDSCH code adjustment period This parameter defines the period foradjustment for the HS-PDSCH codes.

Maximum bit rate of NRT MAC-d flow The parameter defines the maximum bitrate of the NRT MAC-d flow. The bitrate used in the reservation of theresources for the MAC-d flow is theminimum value of the maximum bit ratebased on UE capability and the value ofthis parameter.

Bit rate threshold for RLC PDU size 656with HS-DSCH

This parameter defines the bit ratethreshold for the usage of RLC PDUsize 656 bits if the RB is mapped toHS-DSCH.

DN70500287Issue 1-1 en09/09/2008



Table 75. ARAN852: HSDPA 10 and 15 Codes impact on parameters (cont.)

Parameter Use

Number of HS-PDSCH codes for greaterRLC PDU size

This parameter defines the minimumnumber of allocated HS-PDSCH codesthat allows the usage of RLC PDU size656 bits when the RB is mapped to HS-DSCH.

SIR threshold for RLC PDU size 656with HS-DSCH

This parameter defines the HS-DSCHsignal to interference ratio threshold forthe usage of RLC PDU size 656 bits ifthe RB is mapped to HS-DSCH.

Usage of RLC PDU size 656 with HS-DSCH

This parameter defines whether the useof RLC PDU size 656 in DL datatransfer is allowed in the BTS if the RBis mapped to the HS-DSCH in the DL.

NRT DPCH over HS-PDSCH code offset This parameter defines the number ofallocated HS-PDSCH codes that arenot allowed to pre-empt by NRT DPCH.

HS-PDSCH code upgrade margin forSF128 codes

The parameter defines the requirednumber of free SF128 channelisationcodes left for DPCHs.

Maximum number of HS-SCCH codes This parameter defines the maximumnumber of HS-SCCH codes (SF 128)that can be reserved in one cell.



HS-PDSCH code adjustmentperiod

Maximum bit rate of NRT MAC-dflow

Bit rate threshold for RLC PDUsize 656 with HS-DSCH

Number of HS-PDSCH codes forgreater RLC PDU size

SIR threshold for RLC PDU size656 with HS-DSCH

Usage of RLC PDU size 656 withHS-DSCH

NRT DPCH over HS-PDSCH codeoffset

HS-PDSCH code upgrade marginfor SF128 codes





Maximum number of HS-SCCHcodes

3.7.7 ARAN853: HSDPA Code Multiplexing


HSDPA code multiplexing enables simultaneous transmission of (max)three HSDPA users within a single cell during a single Transmission TimeInterval (TTI).

Code multiplexing improves the code resource utilization andsubsequently, improves the cell throughput 30-50% and beyond.


Improved end-user experience is acquired thanks to better cell throughputin the case of simultaneous users supporting maximum 5 codes. CAPEXand OPEX savings result from increased cell capacity.


This feature allows sending data packets to more than one HSDPA usersimultaneously in each 2 ms TTI. Code multiplexing can be used when atleast two high-speed secondary control channel (HS-SCCH) codes areallocated by the I-HSPA Adapter. With this feature, 2-3 users can be codemultiplexed on HS-PDSCH, depending on HS-PDSCH and HS-SCCHallocation. The available code and power resources are evenly sharedbetween the scheduled users.

The decision on how many users are scheduled per cell is doneindependently on each TTI. The general rule is that when the UE categorywith the highest scheduling metric from proportional fair schedulingalgorithm is supporting less codes than the cell has available, thenpotentially (in case the first user cannot use all the available power) asecond UE is scheduled as well. The second UE to be scheduled is theone with the second highest scheduling metric. If the two scheduled UEsboth support max 5 codes each, then a third user is potentially scheduledas well.

DN70500287Issue 1-1 en09/09/2008



Note that code multiplexing does not provide any throughput gains in acase where the UEs support as many codes as the NW. In such ascenario, the optimal strategy from spectral efficiency point of view is toschedule a single user at a time. This decreases the power spent forcontrol channels (only one HS-SCCH needed instead of several) andincreases the gain from proportional scheduling.

With code multiplexing it is possible to use code space larger than fivecodes also with UEs that support only five codes. The NW capacity gainfrom code multiplexing is similar to gain from 15 codes in the case wheremost of the users are supporting maximum 5 codes.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data

Parameters:

Table 78. ARAN853: HSDPA Code Multiplexing impact on parameters

Parameter Use

Maximum number of HS-SCCH codes This parameter defines the maximumnumber of HS-SCCH codes (SF 128)that can be reserved in one cell.



Maximum number of HS-SCCHcodes


3.7.8 ARAN312: HSDPA Dynamic Resource Allocation


Dynamic HSDPA channelization codes allocation enables full cell resourceutilization, better end-user experience and increased NW capacity. Directswitch functionality provides additionally smoother PS service continuity.


Gain in cell throughput is achieved as the cell resources are better utilizedfor varying traffic mix. The operator control on resource division betweenNRT DCH and HSDPA allows flexible support of different pricing strategiesfor DCH and HSDPA data. Direct HSDPA - DCH switch provides smoothPS service continuity in channel type switches.

DN70500287Issue 1-1 en09/09/2008




Flexi WCDMA BTS will dynamically control the amount of power used forHSDPA. All the power left after DCH traffic, HSUPA control channels andcommon channels is used for HSDPA. This means that as long as there isHSDPA traffic in the cell, all the available PA power can be efficientlyutilized.

The I-HSPA Adapter will still schedule the NRT DCH bit rates. The higherbit rates the I-HSPA Adapter allocates for NRT DCHs, the less there is"spare" power that the Flexi WCDMA BTS can use for HSDPA. To avoidsituations where very unfair distribution of power is created betweenHSDPA and NRT DCH users, the RNC takes into account both the currentnumber of NRT DCH and HSDPA users in the cell when allocating NRTDCH bit rates. By default, the RNC will treat NRT DCH and HSDPA usersequal in the sense that NRT DCH bit rates are allocated in such a way thatroughly equal amount of tx power per user will be available to both NRTDCH users and HSDPA users. This does not mean that each user wouldhave equal bit rates. It simply means that if in a 20 W cell there happens tobe 8 W of RT and common channel load, then about 12 W is available forNRT traffic. This 12 W is then divided so, that in case of 2 NRT DCH usersand 10 HSDPA users, about 2 W would be given to DCH side and 10 W toHSDPA side. The I-HSPA Adapter does not directly guide the FlexiWCDMA BTS in allocating the power for HSDPA, but the I-HSPA Adapterdoes affect this implicitly by decision of NRT DCH bit rates.

On an operator choice, the priority between NRT DCH and HSDPA can beweighted so that power is aimed to be spent in relation p1 : p2, where p1represents the target tx power per user available for NRT DCH, and p2 -the target tx power per user available for HSDPA. In addition, users withhigher Traffic Handling Priority (THP) can be counted more importantwhen deciding the division between power for NRT DCH side and HSDPAside. THP is not taken into account in actual HSDPA scheduling, but allHSDPA users are given roughly equal resources according to proportionalfair scheduling principle.

The code allocation is dynamically following the power allocation. Inpractice this means that once the NRT DCH bit rates have been decided,based on equal power criterion, the code requirements for the DCH sidehave been fixed. All other codes are then given to the HSDPA (operatormay leave some margin to allow fast voice call allocation). In case of newDCH connections (for which the bit rate is again determined based onpower criteria), the required amount of HSDPA codes are given back to theDCH.

This feature also includes the direct switch from HS-DSCH to DCH otherthan zero kbit/s and vice versa.










I-HSPAAdapter



GGSN/FlexiISN

UE








ASW I-HSPA Always included 0.0

Management plane

Management data




MINIMUM PTXTARGETPS

MAXIMUM PTXTARGETPS

AVERAGE PTXTARGETPS


DN70500287Issue 1-1 en09/09/2008




PTXTARGETPS DENOM

MIN HSPA DL POWER

MAX HSPA DL POWER

AVE HSPA DL POWER

HSPA DL POWERSAMPLES

DURATION OF HSDPA 5CODES RESERVATION









HSDPA CH CODEDOWNGRADE DUE TORT

HSDPA CH CODEDOWNGRADE DUE TONRT DCH

3.8 HSUPA

3.8.1 ARAN826: Basic HSUPA


This feature provides the High Speed Uplink Packet Access (HSUPA)functionality, also known as Enhanced Uplink DCH (E-DCH). HSUPAfunctionality is based on the following techniques:



. BTS-controlled scheduling of the E-DCH within the limits set by the I-HSPA Adapter, and

. Physical layer retransmission handling in the BTS.


Increased UL average and peak data rates improve the end-userexperience. CAPEX and OPEX savings result from increased cell ULcapacity and BTS HW efficiency. New data service availability increasesrevenue.


The basic characteristics of the feature are listed below.

. HSUPA is supported only with co-existence of HSDPA.

. All cells in the BTS can be enabled for HSUPA.

. The maximum number of HSUPA users per BTS is 24. Themaximum number of HSUPA users in a cell is 20. One E-AGCH andone ERGCH/ E-HICH are configured to each serving E-DCH cell.

. The operator can choose to set a lower threshold to the maximumnumber of users (3 or 12) per cell and per BTS.

. TTI of 10 ms is used for maximizing the resulting UL range.

. HSUPA requires a static reservation of 12.5% of Flexi submodulecapacity. The rest of the HSUPA baseband capacity is fully pooledacross cells, and also dynamically shared with R'99 traffic. Up to twoFlexi submodules can be in HSUPA use, R'99 traffic allowing.

. The maximum peak data rate per user is 2.0 Mbps as coded L1 bitrate (error protection coding is not counted into bit rate but L1retransmissions are).

. One Flexi submodule supports up to 12 HSUPA users.

. The maximum total average HSUPA bit rate per one Flexisubmodule is 4 Mbps.

DN70500287Issue 1-1 en09/09/2008



. HSUPA channel coding functionality includes E-DCH Absolute GrantChannel (E-AGCH), E-DCH Relative Grant Channel (ERGCH), andE-DCH Hybrid Automatic Repeat Request (ARQ) Indicator Channel(E-HICH) encoding in DL and E-DCH Dedicated Physical DataChannel(s) (E-DPDCH) and E-DCH Dedicated Physical ControlChannel (E-DPCCH) decoding in UL.

. HSUPA Hybrid Automatic Repeat Request (H-ARQ) operationhandling per UE in E-DCH Medium Access Control (MAC-e) entitywithin a BTS.

The total cell data rate for HSUPA users is scheduled between the HSUPAcapable UEs in a cell. Scheduling is performed by the BTS in a fast cycleby using mainly relative grants. All UEs get as much bit rate as they cansend in non-congested case. In case of congestion, roughly equal noiserise contribution is allowed for each user.

For facilitating smooth mobility operations with non-HSUPA capable BTSs,Signaling Radio Bearer (SRB) is mapped on DCH.

HSUPA improves the UL packet data performance by providing higherdata rates over the whole cell area, increasing the peak data rate andreducing delay. HSUPA also increases the system capacity by improvingthe cell throughput and BTS hardware resources. HSUPA benefits areespecially significant for bursty high bit rate applications.

In a non-congested, single user case the maximum bit rates are greatlyimproved, since instead of practical maximum of 384 kbps with R'99, 2.0Mbps can be reached with HSUPA. In a loaded NW with congestion, thecapacity gain from HSUPA is expected to be on the order of 20% - 50%.








RAS FTM NetAct OMS UE




I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter

BTSrelease(Flexi)

CombiSGSN

GGSN/FlexiISN









Management plane

Management data

Parameters:

Table 83. ARAN826: Basic HSUPA impact on parameters

Parameter Use

Allow E-DCH usage EcNo offset CPICH EcNo offset needed for the E-DCH channel type selection for thecells which are in the DCH active setbut not in the E-DCH active set.

CPICH EcNo offset E-DCH usageremoval

The CPICH EcNo offset for the channeltype switch from the E-DCH to the DCHfor the cells which are in the DCHactive set but not in the E-DCH activeset.

DN70500287Issue 1-1 en09/09/2008



Table 83. ARAN826: Basic HSUPA impact on parameters (cont.)

Parameter Use

AM RLC maximum buffer allocation forUE

This parameter defines the maximumAM RLC buffer of the UE. The buffercan be used in the allocation of thetransmission and receiving windows.

AM RLC maximum buffer allocation forUE capability 100

This parameter defines the maximumAM RLC buffer of the UE which hasreported the value of 100 Kbytes for itsnominal Total RLC AM and MAC-hsbuffer size.







AM RLC configuration for PS NRT withE-DCH

This parameter defines theretransmission parameters for the AMRLC of the PS interactive orbackground RAB that is using E-DCH inits data transfer direction.

AM RLC status reports count for PSNRT with E-DCH

This parameter defines the minimumnumber for the AM RLC status reportsthat will be received for the PSinteractive and background radiobearers in the duration of the RLCtransmission window when data istransferred over E-DCH.

AM RLC MaxDAT transmissions for PSNRT with E-DCH

This parameter defines the value of theRLC protocol parameter MaxDAT forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over E-DCH.

AM RLC MaxMRW transmissions for PSNRT with E-DCH

This parameter defines the value of theRLC protocol parameter MaxMRW forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over E-DCH.




Parameter Use

AM RLC maxRST transmissions for PSNRT with E-DCH

This parameter defines the value of theRLC protocol parameter MaxRST forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over E-DCH.

AM RLC status period max for PS NRTwith E-DCH

This parameter defines the maximumstatus reporting period of the AM RLCin relation to the RLC round trip time forthe PS interactive and background radiobearers when data is transferred overE-DCH.

AM RLC status period min for PS NRTwith E-DCH

This parameter defines the minimumstatus reporting period of the AM RLCfor the PS interactive and backgroundradio bearers when data is transferredover E-DCH.

AM RLC period Poll_PDU for PS NRTwith E-DCH

This parameter defines the minimumvalue of the RLC protocol parameterPoll_PDU for the AM RLC entity of thePS interactive and background radiobearers when data is transferred overE-DCH.

AM RLC period Poll_SDU for PS NRTwith E-DCH

This parameter defines the value of theRLC protocol parameter Poll_SDU forthe AM RLC entity of the PS interactiveand background radio bearers whendata is transferred over E-DCH.

AM RLC period Poll_Window for PSNRT with E-DCH

This parameter defines the value of theRLC protocol parameter Poll_windowfor the AM RLC entity of the PSinteractive and background radiobearers when data is transferred overE-DCH.

AM RLC status report triggers for PSNRT with E-DCH

This parameter activates anddeactivates the polling and statusreporting triggers and the RLC timersfor the AM RLC entity of the PSinteractive or background RAB that isusing E-DCH in its data transferdirection.

AM RLC round trip time with E-DCH This parameter defines the AM RLCRound Trip Time (RTT) for the UL datatransfer when the radio bearer ismapped to the E-DCH and the reversetransport channel is the HS-DSCH.

DCH slope of the curve

DN70500287Issue 1-1 en09/09/2008




Parameter Use

Defines the slope of the curve, and inwhat extent the EDCH BLER differenceis taken into account during the DCHBLER target calculation.

E-DCH channel type switch guard timer This parameter determines the time thatmust be waited after an E-DCH to DCHchannel type switching before a DCH toE-DCH channel type switching can bedone.

Window size of E-DCH MAC-d flowthroughput measurement

This parameter defines the size of thesliding averaging window for thethroughput measurement of the E-DCHNRT MAC-d flow.

Low throughput threshold of the E-DCHMAC-d flow

This parameter defines the lowthroughput threshold for the throughputmeasurement of the E-DCH NRT MAC-d flow.

Low throughput time to trigger of the E-DCH MAC-d flow

This parameter defines the lowthroughput time to the trigger timer forthe throughput measurement of the E-DCH NRT MAC-d flow.

E-DCH maximum number of HARQretransmissions

This parameter determines themaximum number of HARQretransmissions for E-DCH.

EDCH slope of the curve This parameter defines the slope of thecurve, and the extent to which the DCHBLER difference is taken into accountduring the EDCH BLER targetcalculation.

Factor to calculate EDCH maximum bitrate

This parameter defines the factor forcalculating the E-DCH maximum bit ratefrom the maximum uplink user bit rateof the RAB.

Happy bit delay condition for E-DCH This parameter determines value forRRC: Happy bit delay conditioninformation element.

Maximum Reordering Wait Time forMAC-es

Parameter allows operators to adjustMAC-es reordering buffer wait time.

Periodicity for scheduling info This parameter defines periodicity forScheduling Info.

Power Offset for Scheduling Info This parameter defines the power offsetfor Scheduling Info.

Step Size for DCH BLER calculation Step Size for DCH BLER weighs theDCH BLER impact to the Delta SIR.




Parameter Use

Step Size for EDCH BLER calculation Step Size for EDCH BLER weighs theEDCH BLER impact to the Delta SIR.

Threshold to define maximum E-DPDCHSR

This parameter structure can be used torestrict the maximum total uplink symbolrate of E-DPDCH(s) based on themaximum uplink user bit rate of theRAB.

Threshold to define maximum EDPDCHSR 1920 kbps

This parameter can be used to restrictthe maximum total uplink symbol rate ofE-DPDCH(s) based on the maximumuplink user bit rate of the RAB.

Threshold to define maximum EDPDCHSR 960 kbps

This parameter can be used to restrictthe maximum total uplink symbol rate ofE-DPDCH(s) based on the maximumuplink user bit rate of the RAB.

HARQ RV Configuration This parameter defines the HARQmethod that is to be used in this BTS.

Maximum number of E-DCHs in thelocal cell group

This parameter determines themaximum number of E-DCH allocationsin the BTS specific local cell group.

PS target tune period in HSPA-DCHinterference sharing

The parameter defines the period forthe adjustment of the target thresholdfor the UL PS NRT DCH resourceallocation when one or more E-DCHMAC-d flows have been set up in thecell.

Non-EDPCH interference averagingwindow size for LC

This parameter defines the averagingwindow size in the number of thecommon measurement reportingperiods for the total receivedinterference power of the cell excludingthe received E-DPCH code powers.

E-DCH Capability This parameter defines the E-DCH(HSUPA) capability for a local cell.

E-DCH minimum set E-TFCI This parameter determines theminimum set E-TFCI for E-DCH.

Operational E-DCH state This parameter is used for reporting theHSUPA operational state of a cell.

HSPA FMCS identifier The parameter identifies themeasurement control parameter set(FMCS object) controlling the intra-frequency measurements of a userhaving HS-DSCH and E-DCH allocated.

HSUPA enabled

DN70500287Issue 1-1 en09/09/2008




Parameter Use

This parameter enables / disables theuse of HSUPA in the cell.

Maximum number of E-DCHs in the cell This parameter determines themaximum number of E-DCH allocationsin the cell.

Maximum total uplink symbol rate This parameter determines the plannedmaximum total uplink symbol rate of theE-DPDCH(s) of the UE in the cell.

Number of E-DCHs reserved for SHObranch additions

This parameter determines the numberof E-DCH allocations that is reservedonly for soft and softer handover branchadditions in the cell and for softhandover branch additions in the BTS-specific local cell group.

DCH time limit for UL NRT DCHoverload in E-DCH cell

This parameter defines the limit time forthe NRT DCH allocation after which theDCH is allowed to be downgraded byreconfiguring it in the overload of theUL NRT DCH resources when an E-DCH MAC-d flow is established in thecell.

Interference margin for the minimum E-DCH load

This parameter defines the minimumcapacity for the throughput based trafficload that is allowed for the E-DCHtraffic in the cell on top of the admittedor scheduled DCH traffic withoutconsidering the received wide bandinterference.

Maximum target received wide bandpower for BTS

The maximum target for received totalwide band power in the cell for BTSpacket scheduling.

Max PS target in HSPA-DCHinterference sharing

This parameter defines the maximumvalue for the dynamic interferencetarget of the UL PS NRT DCH resourceallocation when the HSDPA-DCHinterference sharing is applied.

Min PS target in HSPA-DCHinterference sharing

This parameter defines the minimumvalue for the dynamic interferencetarget of the UL PS NRT DCH resourceallocation when the HSDPA-DCHinterference sharing is applied.

PS target step down in HSPA-DCHinterference sharing




Parameter Use

This parameter defines the fixed stepsize in decreasing the targetinterference level for the UL PS NRTDCH resource allocation when theHSPA-DCH interference sharing isapplied.

PS target step up in HSPA-DCHinterference sharing

This parameter defines the fixed stepsize in increasing the target interferencelevel for the UL PS NRT DCH resourceallocation when HSPA-DCH interferencesharing is applied.

The Maximum transmission power E-HICH

This parameter defines the transmissionpower of the E-HICH in relation to thetransmission power of primary CPICH.

The transmission power offset of the E-AGCH

This parameter defines the transmissionpower of the E-AGCH in relation to thetransmission power of the primaryCPICH.

The transmission power offset of the E-RGCH

This parameter defines the transmissionpower of the E-RGCH in relation to thetransmission power of the primaryCPICH.

SIR target offset for DPCCH with E-DPCH

This parameter defines an offset valuethat the BTS adds to the result of themeasured DPCCH SIR when the radiolink has an E-DCH configured.

Target non-serving E-DCH to total E-DCH power ratio

This parameter defines the value for theNBAP: Target Non-serving E-DCH toTotal E-DCH Power Ratio informationelement.

E-DCH QoS classes This parameter defines the trafficclasses (TC) and traffic handlingpriorities (THP) that can use E-DCH.

Weight of NRT DCH UE This parameter defines the weightvalues for HSDPA Dynamic ResourceAllocation and HSUPA.

Weight of NRT DCH UE BG RAB This parameter defines the weight valueof the background traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP1 RAB This parameter defines the weight valueof the Interactive THP1 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP2 RAB

DN70500287Issue 1-1 en09/09/2008




Parameter Use

This parameter defines the weight valueof the Interactive THP2 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of NRT DCH UE THP3 RAB This parameter defines the weight valueof the interactive THP3 traffic class forHSDPA Dynamic Resource Allocationand HSUPA.

Weight of HSPA UE This parameter defines weight valuesfor HSDPA Dynamic ResourceAllocation and HSUPA.

Weight of HSPA UE BG RAB This parameter defines the weight valueof the background traffic class forHSDPA Dynamic Resource Allocationand HSUPA.






Allow E-DCH usage EcNo offset

CPICH EcNo offset E-DCH usageremoval

AM RLC maximum bufferallocation for UE

AM RLC maximum bufferallocation for UE capability 100



No counters related to this feature 7780 HSUPA DISABLED IN WCEL

7782 HSUPA CONFIGURATIONFAILED





AM RLC configuration for PS NRTwith E-DCH

AM RLC status reports count forPS NRT with E-DCH

AM RLC MaxDAT transmissionsfor PS NRT with E-DCH

AM RLC MaxMRW transmissionsfor PS NRT with E-DCH

AM RLC maxRST transmissionsfor PS NRT with E-DCH

AM RLC status period max for PSNRT with E-DCH

AM RLC status period min for PSNRT with E-DCH

AM RLC period Poll_PDU for PSNRT with E-DCH

AM RLC period Poll_SDU for PSNRT with E-DCH

AM RLC period Poll_Window forPS NRT with E-DCH

AM RLC status report triggers forPS NRT with E-DCH

AM RLC round trip time with E-DCH

DCH slope of the curve

E-DCH channel type switch guardtimer

Window size of E-DCH MAC-dflow throughput measurement

Low throughput threshold of the E-DCH MAC-d flow

Low throughput time to trigger ofthe E-DCH MAC-d flow

E-DCH maximum number ofHARQ retransmissions

EDCH slope of the curve

Factor to calculate EDCHmaximum bit rate

Happy bit delay condition for E-DCH

DN70500287Issue 1-1 en09/09/2008




Maximum Reordering Wait Timefor MAC-es

Periodicity for scheduling info

Power Offset for Scheduling Info

Step Size for DCH BLERcalculation

Step Size for EDCH BLERcalculation

Threshold to define maximum E-DPDCH SR

Threshold to define maximumEDPDCH SR 1920 kbps

Threshold to define maximumEDPDCH SR 960 kbps

HARQ RV Configuration

Maximum number of E-DCHs inthe local cell group

PS target tune period in HSPA-DCH interference sharing

Non-EDPCH interferenceaveraging window size for LC

E-DCH Capability

E-DCH minimum set E-TFCI

Operational E-DCH state

HSPA FMCS identifier

HSUPA enabled

Maximum number of E-DCHs inthe cell

Maximum total uplink symbol rate

Number of E-DCHs reserved forSHO branch additions

DCH time limit for UL NRT DCHoverload in E-DCH cell

Interference margin for theminimum E-DCH load

Maximum target received wideband power for BTS

Max PS target in HSPA-DCHinterference sharing

Min PS target in HSPA-DCHinterference sharing




PS target step down in HSPA-DCH interference sharing

PS target step up in HSPA-DCHinterference sharing

The Maximum transmission powerE-HICH

The transmission power offset ofthe E-AGCH

The transmission power offset ofthe E-RGCH

SIR target offset for DPCCH withE-DPCH

Target non-serving E-DCH to totalE-DCH power ratio

E-DCH QoS classes

Weight of NRT DCH UE

Weight of NRT DCH UE BG RAB




Weight of HSPA UE

Weight of HSPA UE BG RAB




3.8.2 ARAN973: HSUPA Basic RRM


This feature provides the essential Radio Resource Management (RRM)functionality for HSUPA operation.

DN70500287Issue 1-1 en09/09/2008




HSUPA RRM in the I-HSPA Adapter algorithm reserves the required codesand power for the E-AGCH, E-RGCH, and E-HICH physical channels inDL. In UL, a certain noise rise is reserved for the BTS packet scheduler.This allows admitting the NRT DCH users according to the normaladmission control procedure in the I-HSPA Adapter while the remainingnoise rise margin is efficiently utilized for the HSUPA.

HSUPA RRM algorithm in the I-HSPA Adapter also makes the E-DCHallocation decisions. The decision between UL DCH and E-DCH allocationfor a UE is based on the service (RAB parameters), resource availability,and UE capability. HSUPA is supported only with coexistence of HSDPAper UE.

HSUPA RRM algorithm in the I-HSPA Adapter configures also the RLClayer, radio bearer, transport channel, and physical channel configurationfor an E-DCH user based on RAB parameters. E-DCH is released basedon low throughput detection in both UL and DL.

Furthermore, HSUPA RRM algorithm in the I-HSPA Adapter performscombined power and throughput based (hybrid) admission decision andpacket scheduling for R99 NRT DCH and/or E-DCH users in the cell.HSUPA RRM algorithm in the I-HSPA Adapter performs HSUPA outer looppower control for E-DPCH, that is, in uplink.








I-HSPAAdapter



GGSN/FlexiISN

UE










OSW I-HSPA - -

Management plane

Management data






3.9 Supplementary RRM and telecom features

3.9.1 ARAN1.020: Encryption and Integrity Protection


In RAN two security mechanisms can be applied: ciphering and integrityprotection. Ciphering is a sufficient countermeasure againsteavesdropping and it plays a significant role in protecting connectionsagainst attackers with more advanced capabilities, but it is not sufficientalone. In addition to the mutual authentication performed between the UEand CN, integrity protection of signaling is needed in order to havesufficient security against active attackers.

The type of ciphering provided by RAN is based on XOR combining with amask obtained as an output of the ciphering algorithm. The inputparameters for the algorithm are a cipher key, time dependent input, theradio access bearer identity, the direction of the transmission and the

DN70500287Issue 1-1 en09/09/2008



length of the required key stream. Because of the separate mobilitymanagement for CS and PS services, the UE establishes cipher keysseparately to CS and PS core networks. As for the signaling links, the mostrecently established key (between the UE and either of the CNs) is used.

The UMTS Integrity Algorithm (UIA) is used to authenticate the dataintegrity of signaling messages. Input parameters for the algorithm are anintegrity key, time dependent input, a random value, a direction bit, andsignaling message data. Based on these input parameters the messageauthentication code for data integrity (MAC-I) is generated and appendedto the signaling messages sent over the signaling link. Also the receivercomputes the MAC-I and verifies the data integrity of the message bycomparing it to the received MAC-I. The integrity key is transferred to theRAN in conjunction with the cipher key. In RAN both ciphering and integrityprotection are always performed in the serving I-HSPA Adapter.








I-HSPAAdapter



GGSN/FlexiISN

UE






OSW/ASW RAS SW component



Table 87. Software sales information for feature ARAN1.020 (cont.)






Management plane

Management data






3.9.2 IHSW-150: I-HSPA Adapter Frequency Variants


I-HSPA Adapter supports the available Flexi BTS frequency variants.


I-HSPA Adapter supports the available Flexi BTS frequency variants. Seethe variants from the BTS solution features.







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

Management plane

Management data








4 Transmission and transport

4.1 IP transport

4.1.1 IHSW-60: I-HSPA Transport Over IP


The I-HSPA BTSs and I-HSPA Adapters are connected to the transportusing IP-based protocols.


The I-HSPA transport provides the following benefits:

. it is optimized for packet transport, and

. it enables to use the most cost-effective transport technologyavailable.


The I-HSPA BTSs and I-HSPA Adapters use IP-based protocols toconnect to the transport network. This enables easy connectivity betweendifferent BTS sites, even if different L1/L2 technologies are used (Ethernet,TDM/ATM).

I-HSPA site is connected using IP-based:

. IuPS for PS user plane and control plane.

. O&M for operability and management purposes.

Additional separate features enable:

DN70500287Issue 1-1 en09/09/2008


Transmission and transport

. Iur for PS user plane and PS & CS control plane

. IuPC for location services

. IuCS control plane for CS service enabling HO purposes

The operator can also use separate IPSec features to secure theconnections when needed.








I-HSPAAdapter



GGSN/FlexiISN

UE


N/A WBTS4.0 FTM3.0 OSS5.1 OMS1.0 N/A N/A 3GPPRel-5









Management plane

Management data






4.1.2 ARAN165: IP-based Control and User Planes at Iu-PS and Iur


This feature offers increased flexibility in operating WCDMA RAN. The IP-based control plane supports the mobile CN evolution towards an all-IPnetwork.


Increased flexibility in operating WCDMA RAN. IP-based control plane anduser plane support the Mobile Core Network evolution towards an all-IPnetwork.


IP-based Iu-PS and Iur support the evolution of the mobile CN towards anall-IP network.








DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data





General alarms related toSCTP failure:

3159 SCTP ASSOCIATIONLOST

3293 SCTP PRIMARYPATH NOT AVAILABLE



4.1.3 IHSW-29: IP-based Control Plane for IuCS


This feature provides Control plane connectivity towards CS core.


Easy integration towards MSC.


IuCS Control plane allows I-HSPA CS Service enabling Handover andalso Mobile terminated CS calls via MSC.

MSC Release: M13.6







I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008







Management plane

Management data






4.2 IP transport security

4.2.1 IHSW-25: Transport Security Ciphering and Integrity Protection


Security of control, user and management planes over last mile link withNDS/IP as per TS 33.210 standard. Default UMTS parameters for IPSeccan be used.


Secure IP Transport.


This feature lists default UMTS parameters for IPSec, which can be usedfor IPSec tunnels for control, user and management planes.

Services: Data integrity protection, origin authentication andanti-replay protection

Protocol: ESP ( RFC 2406)

Mode: Tunnel mode (only)



Confidentiality: Optional

Encryption: 3DES or AES-128

Modes: CBC, random chosen IV

Integrity: HMAC-MD5, SHA-1

Identification: IP addresses and Fully Qualified Domain Names(FQDN) shall be supported for identification

Authentication: Digital certificates (X.509)

Key exchange: IKE, RFC 2407 - 2409

Key management: ISAKMP

Diffie-Hellman key exchange: Group 2

Separate features are needed for separate interfaces such as secured Iuuser plane, secured Iu control plane and secured O&M transports, whichare needed to enable IPSec for the mentioned interfaces.








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008







Management plane

Management data






4.2.2 IHSW-24: Secured Iu User Plane Transport


Transport is secured with IPSec towards the Packet Core.


The operator can secure the Iu user plane access transport.


I-HSPA terminates ciphering in the Adapter, that is, at the BTS site, thetransport is secured with IPSec towards the ISN (GGSN) site or SGSN siteif direct tunnel is not used. 3GPP specified ciphering is supported over theair interface.










I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






4.2.3 IHSW-20: Secured Iu Control Plane Transport


This feature enables IPSec-protected Iu control plane over IP transport.

DN70500287Issue 1-1 en09/09/2008




The feature provides secure IP transport for control plane.


I-HSPA terminates ciphering in the Adapter. That is, at the BTS site, thetransport is secured with IPSec towards the SGSN site. 3GPP specifiedciphering is supported over the air interface.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data






4.2.4 IHSW-32: Secured O&M Traffic Transport


Enables IPSec protected O&M traffic over IP transport.


Secure IP transport for O&M traffic.


The most important part of the O&M traffic to be encrypted is naturally theuser management related information. IPSec configuration can be donebased on source and destination IP addresses and port numbers.

Typically, NetAct and OMS are co-sited. When NetAct and OMS are indifferent sites, additional feature ARAN33 IP Security for O&M trafficbetween OMS and NetAct is highly recommended.







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






4.2.5 IHSW-90: Support for Infrastructure for Certification Authority (CA)


Digital certificates with X.509v3 format can be used.




Digital certificates with X.509v3 format can be used in ASN.1 binaryformat. The infrastructure can be re-used for other non-I-HSPA productsusing certificates.

I-HSPA supports CA infrastructure with Certificate Management Protocol(CMP), IETF RFC 4210, for automated certificate enrollment; andPKCS#10, IETF RFC 2986, for manual certificate enrollment.

CA includes a secure (typically redundant) repository (HSM) for certificatesand public keys and Certificate Revocation Lists (CRL). I-HSPA usesLDAP protocol for accessing the repository.








I-HSPAAdapter



GGSN/FlexiISN

UE








DN70500287Issue 1-1 en09/09/2008







Management plane

Management data






4.3 BTS and I-HSPA Adapter transport interfaces

4.3.1 ARAN940: E1 Interface for Flexi WCDMA BTS


Flexi WCDMA BTS supports standard compliant E1 (UNI) interfaces, bothtwisted pair (symmetric, 120 ohm) and coaxial (asymmetric, 75 ohm).

The following transport sub-modules are available:

. FTPB, 8 x E1/T1/JT1 (symmetric, 120 ohm).

. FTEB, 8 x E1 (coaxial, 75 ohm).

. FTIA, 4xE1/T1/JT1 (symmetrical, 120 Ohm); 2xFast Ethernet,1xGigabit Ethernet. For more information, see feature 2xFE + 1xGE+ 4xE1/T1/JT1 (symm.) FlexiBTS Transport Sub-module FTIA.

Electrical specifications and frame structure:

The main characteristics of the physical layer of the interface are listedbelow.



. Bit rate 2.048 Mbit/s + 50 ppm

. Code HDB3

. Impedance 75 ohm: coaxial cable; 120 ohm: twisted pair cable

. Type Short-haul

. Connectors used: 75 ohm: SMB; 120 ohm: RJ-45

Jitter and wander are as defined in ITU-T G.823 and ITU-T I.431specifications.

The signal frame and multiframe structure complies with ITU-T G.704/706specifications.

Figure 9. E1 interfaces for Flexi WCDMA BTS







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA FTM LK Long-term capacitylicense

Management plane

Management data






4.3.2 IHSW-75: ATM Transmission Convergence for E1


ATM Transmission convergence for E1.




ATM transmission convergence functionality meets the requirements inITU-T I.432.3 specification. ATM cells are directly mapped into the framestructure according to ITU-T G.804. The cells are octet-aligned in theframe structure. Time Slot 0 (TS0) is used for OAM functions. TS16 is notused in this interface. TS1 to TS15 and TS17 to TS31 are used to transportthe ATM cells (30 octets / 125 us & 4528 cps).

The ATM Inverse Multiplexing functionality E1 (IMA) can optionally beused within interfaces residing on the same plug-in-unit. With IMA it ispossible to group a number of E1 connections together to form a single,larger logical pipe.








I-HSPAAdapter



GGSN/FlexiISN

UE








DN70500287Issue 1-1 en09/09/2008






OSW I-HSPA 0.0 0.0

Management plane

Management data






4.3.3 ARAN941: JT1 Interface for Flexi WCDMA BTS


Flexi WCDMA BTS supports standard compliant JT1 (UNI) interfaces.

The following transport sub-modules are available:


. FTIA, 4 x E1/T1/JT1 (symmetric, 120 ohm); 2 x Fast Ethernet, 1 xGigabit Ethernet. For more information, see feature 2xFE + 1xGE +4xE1/T1/JT1 (symm.) FlexiBTS Transport Sub-module FTIA.

BTS supports standard compliant JT1 (UNI) interfaces. JT1 leasedtransmission service is accessible for example via a Network TerminationUnit.

Electrical specifications and frame structure:

The JT1 interface complies with TTC JT-I431 and TTC JT-G703standards.

The main physical layer characteristics of the interface are:



. Bit rate 1.544 Mbit/s + 32 ppm

. Code B8ZS

. Impedance 100 ohm, twisted pair cable

. Type Short-haul

The control of jitter and wander is defined in the specification TTC JTI431.

The JT1 signal frame and multiframe structure complies with TTC JTG.704/706 specifications.

The connector used is RJ-45.

Figure 10. JT1 interface for Flexi WCDMA BTS





DN70500287Issue 1-1 en09/09/2008






I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






4.3.4 ARAN946: T1 Interface for Flexi WCDMA BTS


Flexi WCDMA BTS supports standard compliant T1 (UNI) interfaces.



The following transport submodules are available:


. FTIA, 4 x E1/T1/JT1 (symmetric, 120 ohm); 2 x Fast Ethernet, 1 xGigabit Ethernet. For more information, see feature 2xFE + 1xGE +4xE1/T1/JT1 (symm.) FlexiBTS Transport Sub-module FTIA.

This feature supports E1/T1/JT1 interfaces only.

Figure 11. T1 interfaces for Flexi WCDMA BTS







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






4.3.5 IHSW-76: ATM Transmission Convergence for T1, JT1


ATM transmission convergence for T1, JT1.


The transmission convergence functionality meets the TTC I.432.3specification.



A JT1 frame consists of 24 time slots, numbered from 1 to 24. The ATMcell is mapped into JT-G.704 frame time slots 1 to 24. The ATM cells aredirectly mapped into the frame structure according to ITU-T G.804. Thecells are octet-aligned in the frame structure.

The ATM Inverse Multiplexing functionality (IMA) can optionally be used.With IMA it is possible to group a number of T1/JT1 connections togetherto form a single, larger logical pipe.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

DN70500287Issue 1-1 en09/09/2008



Management plane

Management data






4.3.6 ARAN942: SDH STM-1 Interface for Flexi WCDMA BTS


FTOA offers 1 x STM-1/VC-4 interface with a tailored throughput for a tailsite.


Cost-efficient and compact STM-1/VC-4 interface integrated to the BTS.


Flexi WCDMA BTS supports standard compliant optical STM1 (VC4)interfaces.

Flexi WCDMA BTS transport submodule FTOA supports one STM-1/VC- 4interface with a throughput that is limited to the equivalent of 16 x E1. Thiscapacity might be enhanced by additional software development effort in alater release if there is a need.

Interface specifications and frame structure:

The interface characteristics of STM-1 are described in ITU-T I.432.2 withVC-4 mapping. The optical media type is Single Mode Fiber (SMF).

The control of jitter and wander complies with ITU-T G.825 and G.958specifications in ETSI.

For safety reasons, the parameters for IEC 825 Class 1 devices should notbe exceeded even under failure conditions.

The connector used is LC -type.



Figure 12. SDH STM-1 interface for Flexi WCDMA BTS








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008






OSW I-HSPA FTM LK Long-term ON/OFFlicense

Management plane

Management data






4.3.7 IHSW-77: ATM Transmission Convergence for STM-1


ATM Transmission convergence for STM-1.


The functionality of the transmission convergence layer is described in theSDH based option of the ITU-T I.432.2 specification. SDH overhead bytesare accessible according to ITU-T G.707 specification.

The ATM cell stream is first mapped into the C-4 and then in the VC-4container, along with the VC-4 path overhead. The ATM cell boundariesare aligned with the STM-1 octet boundaries. Since the C-4 capacity (2340octets) is not a multiple integer of the cell length (53 octets), a cell maycross a C-4 boundary.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

Management plane

Management data






4.3.8 ARAN939: BTS Flexbus Interface


Flexi WCDMA BTS supports Flexbus interfaces.

DN70500287Issue 1-1 en09/09/2008



The following transport submodule is available:

. FTFA, 2 x Flexbus

Each Flexbus interface enables a single-cable connection between theBTS and Nokia Siemens Networks FlexiHopper/MetroHopper microwaveradio outdoor units. No external transmission equipment is needed.

The coaxial Flexbus cable carries user plane data and O&M traffic, andalso supplies power (30 W) to the radio outdoor unit. The user planecapacity is 16 x 2 Mbps. ATM is mapped into E1, with support of IMA. Inaddition to that, TDM cross-connections are supported at the 2 Mbps level.

Figure 13. Flexbus interface (TNC-type female connectors)










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






4.3.9 RAN1062: IMA (Flexi WCDMA BTS)


IMA (Inverse Multiplexing for ATM) is supported for E1, T1, JT1 andFlexbus interfaces of Flexi WCDMA BTS.


IMA feature allows using any transmission medium for BTS access.

DN70500287Issue 1-1 en09/09/2008




IMA is a physical layer technology, which divides and transmits a high-speed stream of ATM cells across multiple (parallel) low speed links andthen reconstructs them back into the original ATM cell order at thedestination.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data






4.3.10 IHSW-701: 2xFE + 1xGE + 4xE1/T1/JT1 (symm.) FlexiBTS TransportSub-module FTIA


The FTIA transport sub-module provides two Fast Ethernet (FE), oneGigabit Ethernet (GE) and four E1/T1/JT1 (symmetrical) interfaces. TheGE interface is provided through an optional SFP module.


The FTIA transport sub-module supports both Ethernet and TDMinterfaces.


Physical interfaces: 1-2) FE 100Base-TX (electrical), RJ45 3) GE SFPreceptacle which can be optionally equipped with one of the followingtypes of SFP modules - 1000Base-SX/LX (optical) - 100/1000Base-T(electrical) 4-7) E1/T1/JT1 symmetrical, RJ48 The FE and E1/T1/JT1interfaces support overvoltage protection (OVP) with respect to "TelecomPorts". I-HSPA Rel.1 supports only the E1/T1/JT1 interfaces. The Ethernetinterface is provided through the Adapter.




Management plane

Management data


DN70500287Issue 1-1 en09/09/2008







4.4 Supplementary transport features

4.4.1 ARAN944: Use of GSM Transmission (Flexi WCDMA BTS)



Sharing transmission medium for WCDMA and GSM BTS access savescost.


Traffic from I-HSPA BTSs is carried in PDH/SDH layer time slots, frames orvirtual containers. The GSM transmission network, based on either PDH orSDH, delivers the bandwidth for the I-HSPA traffic. The I-HSPA appears asa capacity increase.

Existing physical transmission media, microwave radio (MWR), fiber,copper and leased lines, can all be used. WCDMA BTS sites integrate withexisting GSM sites and a common access link can be shared to act as Iu,Iur and Abis.












I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter

BTSrelease(Flexi)

CombiSGSN

GGSN/FlexiISN









Management plane

Management data






4.4.2 IHSW-33: Ethernet Transport


I-HSPA adapter supports Ethernet transport.

DN70500287Issue 1-1 en09/09/2008




Provides additional transport options for operators looking for higherbandwidth and lower backhaul costs than traditional TDM methods.


Three 10M, 100M and 1G electrical Ethernet ports are supported.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data






4.4.3 IHSW-70: I-HSPA Additional L1 and L2 Transport Options


I-HSPA Adapter provides direct connectivity to Ethernet-based transportnetworks. Other transport options are provided via FlexiTransport Modules(FTM).


This feature provides flexible transport options.


I-HSPA Adapter provides direct connectivity towards Ethernet-basedtransport. I-HSPA Adapter has one Ethernet interface reserved fortransport use. Interface provides 10M/100M/1G Electrical interface (RJ-45).

Other L1/L2 transport options are provided via FlexiTransport Modules(FTM).







DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data








5 Operability

5.1 Operability architecture

5.1.1 IHSW-3712: I-HSPA Operability Solution


Nokia Siemens Networks I-HSPA network management system has beendesigned to support operability in the flat network architecture

From the operating user point of view, I-HSPA network management isvery similar to that of Nokia Siemens Networks WCDMA.


Provides the same network management interface (NetAct) for I-HSPAthat is used in traditional WDMA networks. This allows seemlessintroduction of I-HSPA utilizing the same network management tools usedin existing 3G networks.


Nokia Siemens Networks I-HSPA network management system has beendesigned for scalability, supporting different network sizes. Selectedsolutions are inherited from Nokia Siemens Networks WCDMA (3G) anddeveloped further to also support operability of flat network architecture.

Management traffic to/from I-HSPA Adapter goes via Operation andMaintenance Server (OMS). Interface between I-HSPA Adapter and OMSis based on the BTSOM protocol. It carries all the necessary data andcommands (for example, alarms, measurements, configuration and newsoftware data) to control the network element behavior remotely.

DN70500287Issue 1-1 en09/09/2008


Operability

OMS acts as a mediator between I-HSPA Adapters and Nokia SiemensNetworks NetAct. It concentrates the operating and management trafficand performs management tasks towards NEs.

Interface between OMS and NetAct is based on the NWI3 protocol. Thisinterface gives NetAct full control over the whole network (via multipleOMSs). NetAct offers the open northbound interfaces for othermanagement systems.

NetAct provides advanced applications for multi technology and multivendor network and service management; for example, monitoring,reporting, configuring and optimizing.

NetAct provides seamless management of different network technologieswith integrated and interworking tools, which enables the operator tocontrol costs while redeploying competencies and resources from 2G to3G, HSDPA, HSUPA and I-HSPA. Further, as a pre-integrated andprocess-based management system, NetAct visualizes all networkelement failures, service quality indicators and entire traffic on a singlescreen. NetAct makes it possible for the operator to act more proactively,and reach for optimal network and service quality to the end-customer.

Examples of functionality provided in the NetAct for I-HSPA:

. Topology Management.

. Basic administration, Time Management and access to local node/element managers.

. Centralized Software Management.

. Alarm Data and Measurement Data Collection and Storing.

. Alarm Filtering and Reclassification, Modifiable Alarm Manual.

. Performance Management tools and Administration ofMeasurements.

. Network configuration visualization.

. The current radio network configuration as well as the plannedconfiguration of the radio network can be viewed, searched andmodified.

. Exporting actual configuration to an external tool and importing plansfrom external tools.

. Plan provisioning, plan and template management, operationsscheduling.



. Uploading radio network configuration from Adapter, MSC, SGSNand element management system into the Radio AccessConfigurator database.

. Plan actual compare - for reviewing changes what is expected whenplan is provisioned to the network or for verifying that plannedchanges were implemented correctly to the network.

. Site Configuration Tool - for providing an easy-to-access storage forWCDMA BTS site configuration files and other commissioning data.The application supports network rollout by enabling effectivecommissioning of BTSs.

Figure 14. Network management with NetAct





WBTS

ADA

MSC-S

SGSN

GGSN

3rd partyNMS

NetActOMSBTSOM

Iups-u

I ucs

I ups-c

Q3 Q3 NE3S

XML

Gi

NWI3

Iub

Flexi I-BTS

DN70500287Issue 1-1 en09/09/2008


Operability




I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

Management plane

Management data





3476 FAILURE IN BTSO&M CONNECTIONUSAGE



5.2 ARAN1.051: Alarm System


The RAN alarm system helps the user to monitor the network. A decreasein the service level is reported to the operator, including the cause of theservice loss. With the network monitoring tools the user gets information tostart required actions. The alarms themselves are supplemented with thealarm manual pages to describe the condition in more detail. The faultdetection also leads to automatic recovery actions, if needed.

In the I-HSPA Adapter, the Network Element Level Alarm system handlesthe alarms on the network element level. The I-HSPA Adapter alarmsystem gathers alarm reports from the application software in the I-HSPAAdapter, as well as from the BTSs in the radio network.

The alarms of OMS, all I-HSPA Adapters and BTSs are collected in theOMS and they can be viewed in the OMS user interface. The userinterface provides a view for active alarms and alarm history. The user canalso modify alarm parameters in the OMS user interface.

The alarm reports from the NEs are also sent to NetAct. The report givesdetails on how the fault affects the services of logical objects in thenetwork and, if available, the physical unit that caused the service loss.The report also contains the alarm number, which is an entry to the alarmreference manual, and an alarm text, which explains shortly the fault andgives information on the severity level and time.

The severity level classifies the alarms according to their priorities andeffects on services. Critical alarms require immediate actions from themaintenance personnel, major alarms require immediate actions duringworking hours, and minor ones do not require user actions at all.

The handling of the alarms is carried out at different levels of the alarmsystem to simplify the preprocessing of the fault observations and toreduce the load on the whole alarm system.


5.2.2 System impact



DN70500287Issue 1-1 en09/09/2008


Operability




I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -


Management data








5.3 Configuration management

5.3.1 IHSW-3698: Configuration Management with NetAct


Radio Network configuration management can be accomplished usingNetAct.


Efficient and flexible radio network parameter management functionalityoffered.


NetAct offers means to import the radio network plan from the planningtools and to modify it, if needed. NetAct also provides means to modify thecurrent radio network configuration and to send the changes to thenetwork.

Radio network plans in the NetAct can contain changes to multiple I-HSPAAdapters.

The radio network plan is first downloaded to OMS from NetAct. Onedelivered plan can contain objects from different plan types, for exampleradio network and transmission plan types. OMS is capable of splitting oneplan to network element and plan type specific plans. OMS delivers theplan to the I-HSPA Adapter where it is stored in the radio networkdatabase. The plan contains the planned objects in the network and theirconfiguration with corresponding parameters. Those parameters arerelated to handovers, power control, admission control and so on. Whenthe NetAct operator activates the plan made with the help of networkplanning tools, the BTSs and the I-HSPA Adapter are configured by thesystem.

The BTS checks whether the changed parameters require a restart. Ifrestarts are required, they are performed with minimum effect on traffic.The I-HSPA Adapter reports the status of the network to NetAct. Possibletraffic downtime caused by the configuration updating is kept to aminimum.

Other configuration parameters can also be modified from NetAct includingthe IP configuration in the I-HSPA Adapter and the transmissionconfiguration in FTM.

DN70500287Issue 1-1 en09/09/2008


Operability

Some operations (like locking the cell) can be done from OMS usingtopology GUI. Locally the BTS can initiate operational state informationchanges for some network object due to BTS faults and BTS recoveryactions.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

Management plane

Management data








5.3.2 ARAN801: Radio Network Access Regulation Function


This feature enables dividing the NW capacity according to user specificAccess Classes.


The feature makes it possible to control and restrict the user traffic inemergency situations.


An NW becomes congested when the number of user accesses goes farbeyond the maximum user access capacity at a certain location. It can belargely divided into two cases:

(A) Small area (such as a baseball park, a soccer stadium, a concert hall,or a shrine on New Year holidays).

Before the CN becomes congested, the maximum user access capacity ofthe cell is exceeded and the cell may be placed in a permanentlyinaccessible state.

(B) Considerably large area (city, town, or village level) in case ofemergency such as natural disaster like an earthquake.

Users try to access the NW in a vast amount at the same time (foremergency calls such as inquiring about the safety of their family). In thiscase, the core side may become congested because of overcrowdedlines.

The access right to the NW (allowed/restricted) is broadcast to all UEs inthe System Information message on Access Class basis. In a normalsituation, the NW access is allowed for all Access Classes. If the NWaccess needs to be limited due to above-mentioned reasons, the operatorcan activate the access control algorithm, which allows and restricts theNW access of Access Level 0 to 9 users in predefined intervals. AccessLevels 10 to 15 belonging to authority (for example, fireworks, police) arenot restricted.

DN70500287Issue 1-1 en09/09/2008


Operability

New restricted/allowed information is broadcasted in the SystemInformation message to all UEs in the cycle of the access control algorithminterval. The UEs at the restricted Access Class stop transmitting theconnection request messages until the status of the Access Class insystem Information changes to “allowed”.

The following figure gives an example where in a certain area AccessClasses 0 and 1 are prohibited from accessing the NW for the first 2minutes. Other Access Classes are allowed to access the NW. For thenext 2 minutes, Access Classes 2 and 3 are prohibited from accessing theNW. These steps are repeated sequentially.

Figure 15. Access regulation function







Accessclass

01

2

3

4

5

6

7

8

9

12

10

11

13

14

15

Time (minutes)

1 2 3 4 5 6 7 8 9 10 11

Access classes from 10 through 15 cannot be included in regulation.

x xx x

x

xx xx x

x xx x

x xx x

x xx x




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data

Parameters:

Table 138. ARAN801: Radio Network Access Regulation Function impact onparameters

Parameter Use

Access Class Barred list 'Access Class Barred list' informationdefines whether access is barred foreach of the 16 Access Classes (AC0,AC1,...AC15).

Access Class Barred List given bySystem

This parameter replaces the barringinformation for the access classes 0through 9 in the cells where the RadioNetwork Access Regulation Functionfeature is active.

Change origin The parameter defines the origin of thelast configuration action affecting theobject.

DN70500287Issue 1-1 en09/09/2008


Operability

Table 138. ARAN801: Radio Network Access Regulation Function impact onparameters (cont.)

Parameter Use

Congestion Management GroupIdentifier

This parameter uniquely identifies theCMOB (Congestion ManagementGroup) within the I-HSPA Adapter.Values 1...3 are reserved for systemusage.

Cell Access Restriction The Cell Access Restriction parameterdefines the percentage of the cell that isrestricted. The parameter defines thenumber of Access Classes (AC0, AC1,…AC9) that are restricted in a cell atthe same time.

Restriction group name User-defined name for the restrictiongroup.

Restriction group type Restriction group type.

Traffic Restriction The parameter is a switch to enable ordisable traffic restriction.

Restriction Interval Restriction Interval defines therestriction period length. Duringrestriction period same Access Classesare restricted.

Radio Network Access RegulationFunction Group Id

Identifies congestion managementobject (CMOB) which contains RadioNetwork Access Regulation Functioninformation of the cell.



Access Class Barred list

Access Class Barred List given bySystem

Change origin

Congestion Management GroupIdentifier

Cell Access Restriction

Restriction group name

Restriction group type

Traffic Restriction

Restriction Interval

No counters related to this feature 2868 LIMITED UE ACCESS TORADIO NETWORK




Radio Network Access RegulationFunction Group Id

5.3.3 ARAN2.0058: RNW Configuration Event Management


With this function the I-HSPA Adapter reports online to the NetAct via OMSchanges to the Radio Network configuration made locally. The changesare reported automatically as events to the NetAct, which then has an up-to-date documentation of the Radio Network configuration at all times. Thisfunction works even if there is a break in the connection between the I-HSPA Adapter and OMS. The upload of changes is automatically resumedonce the connection has been restored.








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008


Operability




OSW I-HSPA - -

Management plane

Management data





71057 NWI3NOTIFICATION MISSING

5.4 DCN architecture for O&M

5.4.1 ARAN1.040: DCN Architecture for O&M


The O&M connections are based on TCP/IP protocol suite. The datacommunications network provides Intranet connections for O&M. IPprovides a common transport solution for network management. IP iswidely used in Internet and its behavior is well known. The products usingIP are evolving favorably in respect to technology, availability and price.The O&M interface for network elements uses IP in I-HSPA radio accessnetwork.

Many of the management operations are initiated from NetAct. Themessages related to these operations are routed by the OMS to theappropriate Adapter and BTS. In some cases the OMS acts as an activecontroller of the operation and the interactions happen between NetAct-OMS and OMS-Adapter-BTS. The IP traffic directed to the BTS is routed inthe Adapter.



The DCN between OMS and the I-HSPA BTS is always IP-based, but itcan be built using either IP over Ethernet or IP over ATM. When the IP overATM option is chosen, the DCN network can also be used to manage thetransmission network and elements. If the transmission network is basedon PDH and/or SDH links, Q1 and Q3 interfaces are implemented intotransmission mediator devices (MD) and Q1 in FTMs.

Some PDH/SDH devices use IP-based DCN network. This gives thepossibility to manage PDH/SDH devices over the IP network. Note, thatPDH/SDH islands will use their own DCNs, which are currently not basedon the IP. The IP DCN is only used to reach those isolated PDH/SDHDCNs.

The interface from Mediator Device (MD) towards NetAct is handled withCORBA technology. All the mediator devices must be accessible via the IPnetwork. The transmission mediator devices also control the managementof the FTM and 3rd party network elements via SNMP.

Figure 16. DCN architecture for O&M

NetAct

OMS/Mediator

Adapter

BTS

I-HSPA BTS

O&M Connection TCP/IP

O&M Connection TCP/IP

TCP/IP CORBA

DN70500287Issue 1-1 en09/09/2008


Operability








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data





71058 BTS O&MCONNECTION FAILURE



5.4.2 ARAN2.0065: DHCP Server for BTS Site Devices


The DHCP Server can be used for IP address configuration for BTSexternal/site support devices. Along with the IP address, other networkparameters can also be given to the host. The meaningful parameters are:default gateway IP address, lease time and subnet mask.

DHCP functionality shall be supported according to [RFC2131] and[RFC2132]. Ports UDP/67,68 are reserved for DHCP.

The DHCP lease time shall be one week. DHCP lease must be renewedbefore lease time ends.








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008


Operability




OSW I-HSPA - -

Management plane

Management data






5.5 ARAN1.041: Graphical User Interface


The I-HSPA BTS, I-HSPA Adapter and I-HSPA OMS local element levelservices are managed by using a Graphical User Interface (GUI). Allremote configurations are done using GUI as well. GUI is also available inNetAct.

Element Manager is a GUI, which works on top of the NE O&Marchitecture that provides services for NE O&M. The graphical userinterface of EM allows illustrative presentations of configuration, fault andperformance management information on the network element.

The Element Manager is the client program (SW) that runs in the localmanagement tool (LMT), which is connected to NE. Local managementtool is typically connected to the LAN interface of NE for local (on site)element management purpose. Element Manager GUIs can be also usedremotely (as with local LMT) with O&M DCN connected NE, for examplelaunched from NetAct (OSS).

I-HSPA OMS GUI feature includes following graphical user interfaces:



. Application Launcher GUI: Application Launcher (AL) is used as aclient desktop to start up and manage other EM GUIs on the client.

. Fault Management (Alarm System) GUI: The OMS FaultManagement GUI contains a graphical user interface for alarmsystem to get a view of active alarms issued for the object (by NE).

. Topology Browser GUI: With topology browser the user is able tosee I-HSPA radio access network topology structure and attributechanges (such as state) in real time. Furthermore the user can seerelationships of managed objects and attributes and their values fora selected item in the GUI. The user is also able to executeprivileged O&M operations for managed NEs or RNW objects fromOMS.

. RNW Measurement Presentation GUI: With RNW MeasurementPresentation application it is possible to view the counter and KPIvalues of I-HSPA measurements collected and stored to OMS PMdatabase.

. Radio Network Measurement Management GUI: With the RNWMeasurement Management GUI the user can manage I-HSPA radionetwork measurements.

. OMS Parameter Management GUI: With OMS ParameterManagement GUI the user can manage OMS specific parametersstored into LDAP database.

. Network Element Threshold Management GUI: With NE ThresholdManagement GUI it is possible to define threshold rules for counters/KPIs and activate monitoring of them.


5.5.2 System impact







DN70500287Issue 1-1 en09/09/2008


Operability

Table 145. Software dependencies for feature ARAN1.041 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter

BTSrelease(Flexi)

CombiSGSN

GGSN/FlexiISN








OSW I-HSPA - -


Management data








5.6 License and option management

5.6.1 ARAN172: License Management with NetAct


With this feature the NetAct user is able to manage the licenses for theoptional features available for the BTS. The licenses are ordered fromNokia Siemens Networks and introduced to the NetAct licensemanagement application, from where the license files are distributed to thecorrect network elements.

The feature also introduces tools for tracking the state of the optionalfeatures in the network. When an optional feature is activated, an event isautomatically sent to the NetAct for updating the network wide view of theoptional features.








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008


Operability




OSW I-HSPA - -

Management plane

Management data





3269 LICENCEEXPIRATION WARNING

3270 LICENCE HASEXPIRED

3271 LICENCE IS NOTVALID

3272 LICENCE CHANGEIS NOT NOTIFIED

3294 LICENCE CAPACITYWARNING

3295 LICENCE CAPACITYEXCEEDED

7660 BASE STATIONLICENCE EXPIRED

7661 BASE STATIONLICENCE NOTIFICATION

5.6.2 ARAN804: Centralized Pool License Management in NetAct


A centralized license management application in NetAct that receiveslicense files from the License Generator (LG).




The proposed approach requires a centralized license managementapplication in NetAct that receives license files from License Generator.These license files will contain a huge amount of licenses (license pool)that can be distributed freely by the operator, that is, these licenses do notcontain site-specific information. This feature is applicable only for BTSlicenses.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

DN70500287Issue 1-1 en09/09/2008


Operability

Management plane

Management data






5.7 Maintenance and diagnostics

5.7.1 ARAN1.048: Radio Network Recovery


Radio network recovery ensures that the maximum performance level ismaintained in the network by restricting the effects of the fault or failureoccurrences.

In case of BTS faults, the BTS itself detects the hardware fault anddisables the corresponding logical object. It sends information about theoperation to the I-HSPA Adapter. The I-HSPA Adapter disables theresources by marking them as unavailable for traffic. It also marks theobject disabled in the radio network database. When the fault is correctedor the network element proves functional again, the automatic recoverytakes the resource back into use by enabling the logical resource.

The BTS can also request, for example, that the traffic in a particular cellbe cleared in failure situations, which do not demand immediate resourcedisabling.

The I-HSPA Adapter supervises Iub common channels. So the I-HSPAAdapter is able to detect possible sleeping cells because of droppedcommon channels.

In case the common channel connection on Iub is dropped, the I-HSPAAdapter has to get information about the situation to ensure the servicestate of the cell. The corrective action in I-HSPA Adapter is to initiate a newcommon channel setup procedure.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data





7761 RNW O&MSCENARIO FAILURE

7762 RNW DATABASEOPERATION FAILURE

DN70500287Issue 1-1 en09/09/2008


Operability


7771 WCDMA CELL OUTOF USE

7779 RECOVERYACTIONS ONGOING

5.7.2 ARAN1.049: Resets and Initializations


The BTS initialization procedure takes place in case of a spontaneousreset or when the operator triggers the reset remotely from OMS EM orNetAct. In BTS reset the BTS starts with the software saved in its non-volatile memory. The SW is installed either earlier in the factory, locally atsite, or downloaded from the SW file server.

The BTS System Module requests configuration data from the I-HSPAAdapter. The I-HSPA Adapter sends the configuration data to the BTSSystem Module. After the configuration, the BTS System Module takes theresources into use. If only BTS reset was requested and the I-HSPAAdapter computer unit is up and running, the BTS opens connection to I-HSPA Adapter and provides up-to-date information about BTSconfiguration, cell resources and so on to the I-HSPA Adapter. If the I-HSPA Adapter was reset, after the computer unit is up and running, the I-HSPA Adapter requests the information from BTS.

I-HSPA Adapter reset also starts with the software saved in its non-volatilememory. I-HSPA Adapter reads the configuration data that was last savedin the adapter's permanent storage and opens the connection to OMS.When operator triggers I-HSPA Adapter reset from OMS EM or NetAct,also BTS reset is always executed. Also spontaneous I-HSPA Adapterreset causes BTS to reset.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data







7778 WCDMA BTSDEDICATEDMEASUREMENT FAILURE

DN70500287Issue 1-1 en09/09/2008


Operability

5.7.3 ARAN1.050: I-HSPA Adapter Computing Platform SystemMaintenance


System maintenance is responsible for maintaining the fault-tolerantcomputing platform of the I-HSPA Adapter. It consists of three systems:supervision system, alarm system, and recovery system. The supervisionsystem performs continuous checking and testing in order to detectirregularities and informs the alarm system about them. The alarm systemidentifies the faulty unit or object and informs the recovery system and theoperator about the fault. The recovery system tries to eliminate the effectsand spreading of the fault.








I-HSPAAdapter



GGSN/FlexiISN

UE










Table 156. Software sales information for feature ARAN1.050 (cont.)



OSW I-HSPA - -

Management plane

Management data





2018 OVERFLOW INHANDLING ALARMEVENTS

2425 ALARM SYSTEMFILE ERROR

2450 SCHEDULEDALARM BLOCKINGFAILED

2451 ALARM NOT SAVEDTO DATABASE

2452 ALARM SYSTEMDATABASE READINGFAILED

2453 NETWORKELEMENT LEVEL ALARMSYSTEM FILE ERROR

2465 UNDEFINED ALARM

2723 OVERFLOW INBUFFERING BLOCKEDALARMS THAT SHOULDBE RESTORED

2724 ACTIVE ALARMSOVERFLOW

2842 ALARM PRINTOUTFAILED

3041 UNKNOWN ALARMOBJECT UNIT

DN70500287Issue 1-1 en09/09/2008


Operability

5.7.4 ARAN1161: Alarms for PM Measurement Data Transfer Failures


The feature introduces new alarms for noticing problems in PM datacollection.


OPEX savings result from faster discovery of problems in measurementcollection mechanism.


This feature introduces new alarms for ensuring correct information aboutthe problems in the PM data transfer.

New alarms are introduced for the following failure situations:

. OMS is not able to retrieve Measurement data from I-HSPA Adapteror BTS.

. NetAct is not able to retrieve Measurement data from OMS.

. There are problems in measurement data processing.

Alarms are canceled when the situation is resolved.

There are various in-built mechanisms for recovering from problems, sothe alarms are only generated for situations that:

. Result in loss of data

. Require explicit action for resolution

. Indicate a problem in performance of measurement data processingor transfer

The new PM alarms are only intended to cover the PM specific aspect ofthe data pipe. There are separate mechanisms to notice, for example,general problems with DCN or OMS - Adapter connections.

Compliance to standards: This feature has no references to standards.

Interaction with other features: There are no dependencies to other RANfeatures as such, but the basic FM and PM functionality has to beavailable.



Interaction with other features: There are no dependencies to other RANfeatures as such, but the basic FM and PM functionality has to beavailable.

Limitations and restrictions: This feature has no special limitations orrestrictions.

Using Alarms for PM Data Transfer Failures: The feature is usable via thenormal NetAct monitoring tools once the feature has been activated.

Feature management: There are no counters or parameters related to thisfeature.

Capacity: This feature has no special capacity requirements.








I-HSPAAdapter



GGSN/FlexiISN

UE






OSW/ASW RAS SW component

DN70500287Issue 1-1 en09/09/2008


Operability

Table 158. Software sales information for feature ARAN1161 (cont.)





OSW I-HSPA - -

Management plane

Management data





71000 PM FTPCONNECTION FAILED

71001 MEASUREMENTDATA NOTTRANSFERRED

71002 MEASUREMENTDATA ERROR

71003 OMSMEASUREMENT DATAPROCESSINGOVERLOAD

5.7.5 ARAN1.5053: BTS Testing Functions


This feature enables the operator to verify the BTS functionality in the fieldwhile the BTS is not connected to a live network or during the operationalstate. Typically, these tests are run at the end of the commissioning phase.There are three different types of tests that can be run by the BTSManager commands:



. BTS CDMA Loop Test: By this test, the BTS internal basebandpayload connections can be tested. Testing of the connections isbased on the HW, which must be detected automatically when theBTS is started. This test can be run either off-line or during theoperational state. While this test is active, the BTS capacity isreduced.

. BER measurement: A specific WTR Rx functionality can be testedby connecting a separate RF-generator to the BTS Rx input andactivating the BER measurement from the BTS Manager. This testcan be run in the off-line state.

. BTS Test model: Test models are used to simulate TX traffic from theBTS when it is off-line. Like the BER test, this test is run in adedicated test state (not connected to a live network). With testmodels 1-5 it is possible to test for example the following: basestation maximum output power, spectrum emission mask, frequencyerror, spurious emissions, ACLR, CPICH power accuracy, outputpower dynamics, peak code domain error and total power dynamicrange. Channel variations can be between 3- 64 DPCH channels. Inaddition to that, 2-4 control channels are represented in all testmodels.








I-HSPAAdapter



GGSN/FlexiISN

UE



DN70500287Issue 1-1 en09/09/2008


Operability






OSW I-HSPA - -

Management plane

Management data






5.7.6 ARAN2.0044: Intelligent BTS Shutdown with BBU Unit


Intelligent BTS shutdown provides BTS the capability to shut downresources in order to increase the time using battery power supply in theevent of main power failure.

The operator is allowed to configure battery backup timer via BTSManager/GUI. Battery backup timer is managed only when commissioningis ongoing.

A battery backup timer is defined as per cell basis. The timer defines thetime the cell is allowed to stay in service while working on batteries. Afterthe timers for all cells in BTS have expired, all other units excepttransmission functionality are also shut down to save the batteries.

Transmission functionality will stay active as long as possible using thebatteries. This is done to make sure that other BTSes in the BTS chain willnot be affected by the power failure.



BTS uses Common NBAP procedures to request I-HSPA Adapter to clearthe cells with Battery backup procedure after the battery backup timer hasexpired.

Additional BTS HW is required (that is, battery back-up unit).

Intelligent shutdown assures the performance of the network in powerfailure situations. The operator shall be able to tune the shutdown timers inBTS to ensure the maximum performance in failure situation for each BTSindividually to correspond to the most probable shutdown time.








I-HSPAAdapter



GGSN/FlexiISN

UE








ASW I-HSPA Trust based -

DN70500287Issue 1-1 en09/09/2008


Operability

Management plane

Management data






5.8 O&M security

5.8.1 ARAN812: Local User Authentication for BTS


The feature introduces local user account management for BTS.


Enhanced risk management is achieved because of improved RANsystem security.


With this feature, the Element Manager access to a BTS is protected witha configurable password. The user authentication is done locally in theBTS. The user can change the local BTS user password with the BTSelement manager.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






5.8.2 ARAN618: Centralized User Information Management for BTS


This feature enables entralized user account management for BTS fromNetAct. This feature is only available when NetAct is used.

DN70500287Issue 1-1 en09/09/2008


Operability


Both BTS element manager user and BTS host are identified to fulfill thesecurity requirements. Authentication is done in the centralizedauthentication server located in the NetAct.

With this feature the user is able to manage the access to the O&M NWseparately for each group or individual of the maintenance personnel on aBTS access level.

Compliance: This feature has no references to standards.

Limitations and restrictions:

. BTS users have only one type of authorization access profile in use.

. If illegal access attempt using wrong credentials is done to BTS, noalarm is generated.

Feature management: There are no alarms or counters related to thisfeature.

Parameters related to this feature are:

. LDAP server address (initialization parameter)

. LDAP server TCP port (initialization parameter)

. BaseDN (initialization parameter)

. peopleDN (initialization parameter)

. configDN (initialization parameter)

. NESpecificDN (initialization parameter)

. AuthenticationMethod (system defined)

. IdleTimeout (associated with nwi3-interface)

. NumberofUnsuccessfulLoginAttempts (associated with nwi3-interface)

. TimeToResetDelay (associated with nwi3-interface)

. AccountLength (system defined)

. PasswordLength (system defined)



Using Centralized User Information management for BTS: The feature canbe used by setting up the initialization parameters. Also the BTS mustreceive its own NE account. The BTS user accounts must be created withNetAct into centralized authentication server.

Activating Centralized User Information Management for BTS: The featureis a standard one, no licenses are needed.

Capacity: Authentication response time depends on different factors likethe overall authentication request density and connection speed.








I-HSPAAdapter



GGSN/FlexiISN

UE








ASW NetAct I-HSPA I-HSPA Adapter LK Long-term ON/OFFlicense

DN70500287Issue 1-1 en09/09/2008


Operability

Management plane

Management data






5.8.3 ARAN1159: IP Address and Port-Based Filtering for BTS LMPs


This feature enables the selective defining of the access to/from IP DCNfrom/to all entry points at a Flexi WCDMA BTS site. Filtering is based onsource and destination IP address and port information.

This feature improves protection of:

. IP DCN from harmful IP traffic originated from Flexi WCDMA BTS

. Flexi WCDMA BTS from harmful IP traffic arriving from IP DCN


Enhanced risk management is achieved because of improved RANsystem security.


Flexi BTS system module extends the supervision of IP traffic to all packetflows in Flexi WCDMA BTS, and it introduces a new mode to define moreselectively the access to/from IP DCN. Since system module offers also anLMP, this feature increases security with respect to all Flexi WCDMA BTSLMPs.

Compliance to standard: This feature has no references to standards.


Feature management: This feature is managed with the followingparameters:



. IP filter rule - parameter. Unique rule name. Source and destination IP address definitions. Ranges or wildcards can be used. Source and destination port definitions

Flexi BTS system module contains several rules as table.

There are no alarms or counters related to this feature.

. Using IP Address and Port based Filtering for BTS LMPs: Theoperator may select between the following modes, independently foreach packet flows:. In unrestricted mode, all IP traffic is allowed to pass through.. In restricted mode, no IP traffic is allowed to pass through.. In restricted mode with exceptions, the system module routing

function validates the source and destination information ofeach incoming IP packet against the configuration in therelated table. IP packets not matching the criteria arediscarded.

Whether only IP addresses, or ports as well, need to match, it is a matter ofconfiguration. The configuration can only be modified via remotemanagement session. Modification via local management session is notsupported because this would allow changing the access restrictions LMPwhile being connected to it and thus jeopardize the whole concept.

Feature activation: This is a standard feature, so no licenses are needed.The feature is activated by default as in unrestricted mode.

Capacity: This feature has no special capacity requirements.








DN70500287Issue 1-1 en09/09/2008


Operability


I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter



GGSN/FlexiISN

UE


N/A WBTS4.0 FTM3.0 OSS5.1 OMS1.0 N/A N/A N/A






OSW I-HSPA - -

Management plane

Management data






5.8.4 ARAN33: IP Security for O&M Traffic Between OMS and NetAct


This feature enables secure transmission of O&M traffic in the O&M DCNfor the connection between the OMS and NetAct.




Enhanced risk management is gained because of improved RAN systemsecurity. This feature strengthens the protection against both internal andexternal hostile attacks.


If NetAct and OMS are located in different sites, this feature is highlyapplicable and recommended.

Virtual Private Networks (VPN) are defined for the O&M traffic between theOMS and NetAct. IPSec is used to encrypt the data.

The most important part of the O&M traffic to be encrypted is naturally theuser management related information. IPSec configuration can be donebased on source and destination IP addresses and port numbers.

Interaction with other features: This feature has no special interaction withother features.


Feature management: The feature includes the OMS-specific IPSec-related parameters. For more information, see OMS customerdocumentation.

There are no alarms or counters related to this feature.

Using the IP security for O&M traffic between OMS and NetAct: Thefeature is managed via CLI. IPSec rules need to be configured to theelement.

Feature activation: The feature is optional. To activate the feature, therelated NetAct licenses have to be purchased.

Capacity: See OMS customer documentation.





DN70500287Issue 1-1 en09/09/2008


Operability




I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data








5.8.5 ARAN181: Remote User Information Management for I-HSPAAdapter


This feature enables a centralized user account management for I-HSPAAdapter from NetAct.


Enhanced risk management and OPEX savings are achieved because ofcentralized RAN system security.


With this feature, the system administrator is able to manage the access tothe NW and element manager with a centralized authentication andauthorization server in NetAct.

In the login phase, the NW entity checks the user access right from theauthentication and authorization server.

The access rights can be managed separately for each group or individualof the maintenance personnel. In the User Information Managementsystem, the operator is able to define different access classes for differentuser groups and NEs.








I-HSPAAdapter



GGSN/FlexiISN

UE

Release N/A WBTS4.0 N/A OSS5.1 OMS1.0 N/A N/A 3GPPRel-5

DN70500287Issue 1-1 en09/09/2008


Operability


I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapterRel1






ASW NetAct I-HSPA I-HSPA Adapter LK Long-term ON/OFFlicense

Management plane

Management data






5.8.6 ARAN895: Secure Port Configuration in NetAct Firewall



The firewall configuration for CORBA port can be changed so that only thefixed values that are used in the RAN O&M are allowed.




When fixed CORBA ports are used, the firewall can be configured to allowtraffic only for these ports. This improves the security in the network.

This implementation is done to the OMS.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

DN70500287Issue 1-1 en09/09/2008


Operability

Management plane

Management data






5.9 RNW integration

5.9.1 ARAN1.043: Radio Network Integration


RNW configuration is delivered automatically from NetAct or manuallyfrom OMS to the I-HSPA Adapter and BTS. The BTS' TRS configuration isdone either remotely or locally using EMs.

The radio network integration is divided into several areas: configuration oftransmission level, IP level, and, finally, setting up the radio network. Thefeature covers the whole integration from setting up a DCN andtransmission to activating radio network plans in network elements.

The aim of the radio network integration is to provide support for theautomated configuration of each of the integration areas. The automationimplementation of different areas is done in several steps, starting from themost time consuming operations.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data





3172 RNW DATABASEFILE COPY FAILED

3173 RNW PLANACTIVATION ORROLLBACK FAILED

3325 INCONSISTENCY INNOKIA SPECIFICCONFIGURATIONPARAMETERS



7775 INCONSISTENCY INWCEL CONFIGURATIONPARAMETERS

DN70500287Issue 1-1 en09/09/2008


Operability

5.10 SW management

5.10.1 IHSW-3695: SW Management with NetAct


Basic SW Management with NetAct consists of software managementfunctionalities focused to BTS or I-HSPA Adapter. Those functionalities aredownloading SW build, activating SW build and uploading SWconfiguration. Each of them can also be focused to multiple BTSs andAdapters (the amount is not limited). The SW build contains the filesrelated to one release of the network element. Change Deliveries (CD) arealso handled as builds, that is, there are no separate operations that couldbe used for CD management.

When a SW build is downloaded, it can be activated immediately, or laterwith a separate activation request. The activation of the SW build requiresa reset of the network element. Automatic return to the old SW package isprovided if a fatal error is detected during SW upgrade procedure. The SWconfiguration upload functionality is used to keep NetAct SW registers up-to-date.








I-HSPAAdapter



GGSN/FlexiISN

UE










OSW I-HSPA 0.0 0.0

Management plane

Management data






5.11 Topology management

5.11.1 IHSW-3696: Topology Management with NetAct


NetAct gathers the topology information automatically from the controllednetwork elements with the help of topology events and topology uploadoperations. The topology information is stored to its topology repository.OMS acts as a mediator for topology management related operationsbetween NetAct and network elements. The topology information is alwayskept up-to-date and available for the use by all the other NetAct based NElevel management operations.


DN70500287Issue 1-1 en09/09/2008


Operability







I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0

Management plane

Management data








5.12 BTS related O&M features

5.12.1 ARAN2.0048: Nokia Siemens Networks RealTilt



Nokia Siemens Networks RealTilt allows operators to:

. Simplify and speed up the network optimization process, allowingthe network to be optimized regularly, independent of engineeringresources, site access or weather conditions.

. Create the capability to react to changing load patterns and tune thenetwork, ensuring optimal network performance for all services.

. Eliminate the need for site visits to tilt antennas and hence the needto turn off sites. This leads to considerable savings in operationalcosts and avoids the loss of revenue due to site downtime.

. Reduce the overall antenna stock holding and improve logisticsbecause of a radical reduction of antenna variants, due to the use ofantennas with continuously variable down-tilt.


RealTilt is a fully integrated solution, which enables the optimization of I-HSPA networks by adjusting antenna tilt angle remotely with the BTSelement manager and in the future from the network management system,Nokia Siemens Networks NetAct.

A graphical user interface running in the BTS Element Manager allows theuser to tilt six antennas to the desired angle (0°-14°) and monitor the statusof the antenna.

Antenna tilt angle is controlled using the RealTilt control unit, RCU. Thisunit is sited within the BTS cabinet, BTS site support cabinet or outside theBTS in any 19-inch rack. RCU receives inputs from the BTS controlinterface and converts these inputs to a protocol that is compatible with thedown tilt control actuators, RTA. The RTA unit is mechanically mounted tothe antenna for electrical down-tilt adjustments.

DN70500287Issue 1-1 en09/09/2008


Operability

Because the BTS Element Manager can be launched within the NetActFramework, the user can simultaneously use the graphical analysis toolsin Optimizer, which is also within NetAct, to monitor the effect of theantenna tilt on the network performance by means of the dominance areamap and reports based on relevant Key Performance Indicators (KPIs).

The solution takes full advantage of the latest developments in antennatechnology, which enable tilt angle to be adjusted electrically usingvariable phase shifters. Using this technology the main beam energy of theantenna can be tilted, without the need to physically tilt the antennaradome.

RealTilt delivers savings because of the two following main facts:

1. Less effort on tilting. Less manual work needed in defining a reason for under-

performing cells. Less manual work needed to implement new antenna tilt. Less working hours. OPEX savings

2. Better radio RF performance. Less cells in queue waiting to be optimized. Fast reaction to changing load conditions. Less capacity upgrades. CAPEX savings








I-HSPAAdapter



GGSN/FlexiISN

UE



Table 181. Software dependencies for feature ARAN2.0048 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






5.13 Supplementary operability features

5.13.1 ARAN1.5028: Combined GSM and WCDMA Management


When this feature is used, it is possible to control both GSM and WCDMA(including I-HSPA) radio networks using one and the same logicalmanagement system, that is, NetAct.

DN70500287Issue 1-1 en09/09/2008


Operability

GSM BSS and WCDMA RAN are closely related: GSM and WCDMA basestations can be located at the same sites, even inside common cabinets,and they can share common transmission connections. Same sites andalso transmission can be used to I-HSPA NEs. NSS is common for bothGSM and 3G. Moreover, the 3G packet core network is a continuation fromGPRS. Hence, it is important to have a common management tool forcontrolling the GSM and 3G networks.

Combined GSM and WCDMA NetAct supports network monitoring, that is,all the configuration data is found in a common database and managedwith a single application. Combined NetAct also features commontransmission configuration management and radio network configurationmanagement, for example BTS sites and establishing neighboring cell listsfor the purpose of inter-system handovers.








I-HSPAAdapter



GGSN/FlexiISN

UE










OSW I-HSPA - -

Management plane

Management data






DN70500287Issue 1-1 en09/09/2008


Operability



6 Performance monitoring

6.1 ARAN1.052: Radio Network Monitoring Statistics

6.1.1 Introduction

The Radio Network Monitoring Statistics provides operators withcontinuous up-to-date information, enabling them to maintain a highstandard of network operability for their customers.


OPEX and CAPEX savings and enhanced end-user service quality areachieved with a continuous monitoring of the radio network.


This feature consists of the following operability aspects:

. Measurement management either via OMS Element Manager orusing NetAct Administration of Measurements application.

. Producing and collecting the statistics data in the I-HSPA Adapterand WBTS.

. Storing of the measurement data to OMS database for viewing thedata using OMS Element Manager.

. Forwarding the measurement data to NetAct.

The following measurement areas are supported:

. Resource availability (Cell availability, Iu availability, Iur availability)

. Quality of service (RRC and RAB connections)

DN70500287Issue 1-1 en09/09/2008


Performance monitoring

. HSPA accessibility and retainability

. HSPA radio interface quality

. Radio resource usage

. Traffic channel usage

. Layer-3 RANAP, RNSAP and NBAP signaling

. RRC protocol signaling

. Handovers

. Transmission statistics

. I-HSPA Adapter and WBTS hardware resource usage


6.1.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE










OSW I-HSPA 0.0 0.0


Management data






6.2 ARAN1163: Iu-PS Throughput Measurement forGTP Traffic

6.2.1 Introduction

This feature provides a new measurement for monitoring the Iu-PSinterface user plane throughput and performance. The information of PStraffic volumes can be used to dimension the Iu-PS interface transmissioncapacity, plan the I-HSPA Adapter capacity licensing, and to report the PSdomain traffic volumes for different business purposes.


CAPEX and OPEX savings are achieved because of optimized transportresources and capacity licensing for Iu- PS interface.

The new counters enable monitoring the Iu-PS resource usage anddimensioning the NW resources based on the actual traffic volumes.


This feature introduces Iu-PS throughput measurement that can be usedto monitor the amount of data transferred in the Iu-PS interface.

DN70500287Issue 1-1 en09/09/2008




6.2.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE


N/A N/A N/A OSS5.1 OMS1.0 N/A N/A N/A






ASW I-HSPA - -


Management data




SENT_GTP_USER_PAYLOAD No alarms related to this feature




RECEIVED_GTP_USER_PAYLOAD

SENT_GTP_U_PACKET

RECEIVED_GTP_U_PACKET

AVG_GTP_TUNNELS

MAX_GTP_TUNNELS

RECEIVED_GTP_ECHO_REQ

RECEIVED_GTP_ECHO_RESP

SENT_GTP_ECHO_REQ

SENT_GTP_ECHO_RESP

RECEIVED_GTP_ERR_INDICATION

SENT_GTP_ERR_INDICATION

MAX_UL_DATA_THROUGHPUT

AVG_UL_DATA_THROUGHPUT

MAX_DL_DATA_THROUGHPUT

AVG_DL_DATA_THROUGHPUT

SENT_GTP_PACKETS

RECEIVED_GTP_PACKETS

IUPS_DL_THRPUT_CLASS_0


















DN70500287Issue 1-1 en09/09/2008













IUPS_UL_THRPUT_CLASS_0





















THRPUT_LIMIT_DURATION



6.3 ARAN234: I-HSPA Subscriber Trace

6.3.1 Introduction

Tracing provides an efficient means to manage, collect and view data fromdifferent network elements related to a specific subscriber or mobile phonein wireless networks. Tracing plays a major role in such activities as thedetermination of the root cause of a malfunctioning mobile, advancedtroubleshooting, optimization of resource usage and quality, RF coveragecontrol and capacity improvement, dropped call analysis, and end-to-endnetwork procedure validation.

This feature enables HSPA reporting for Subscriber and Equipment Tracefunctionality.


. Finding right sites to be tested.

. Possibility to test "hard to access" cases.

. Fast testing response without special terminals and specialcompetence.

. Facilitating network quality testing, using. Field engineer's mobile. Employees on the way to/from work. Automated data gathering for post processing

. Reducing costly site visits.

. Analyzing problems before launch.

. Tracking individual problems.

. Speeding up customer complaint resolution through real-timetroubleshooting data and automated process.

. Making OPEX and CAPEX savings by using Subscriber traceinstead of drive testing.


I-HSPA Adapter provides Subscriber Trace data for NetAct TraceViewerapplication, which provides an efficient means to manage, collect and viewdata.

DN70500287Issue 1-1 en09/09/2008



The tracing can be activated with two different methods:

1. Directly from TraceViewer to I-HSPA Adapter; this is known asManagement Based Activation and does not require any tracesupport from the core network.

2. From core network via 3GPP compliant RANAP signaling; this isknown as Signaling Based Activation and requires support from thecore network.

Subscriber Trace provides information from, for example, the followingevents:

. Radio Access Bearer establishment and release

. UE capability information

. Radio Bearer establishment and release

. HS-DSCH and E-DCH allocations and releases

. UE state changes (Cell-DCH, Cell-FACH, Cell-PCH, URA-PCH)

. Cell Updates

. Soft and hard handovers

. HSPA serving cell change

. Uplink power control, including uplink BLER and HARQretransmissions information

. AM-RLC radio bearer throughput and error ratio



Figure 17. I-HSPA Trace Solution


6.3.3 System impact





I-HSPABTS

I-HSPABTS

NetAct

OMS

CoreNetworkCN_INVOKE_TRACE

Tu

Iu

Traceactivation

Tracerecord

TraceViewer

Report generation

Trace activation

HSDPA Trace data

- UE capability

- HS-DSCH HOs

- HS-DSCH <-> DCH

HSDPA Trace data

- UE capability

- E-DSCH HOs

- E-DSCH <-> DCH

DN70500287Issue 1-1 en09/09/2008




I-HSPAAdapter



GGSN/FlexiISN

UE


N/A N/A N/A OSS5.1 OMS1.0 N/A N/A 3GPPRel-5






ASW I-HSPA 0 Long-term ON/OFFlicense


Management data






6.4 ARAN2.0026: KPI Calculations in OMS for I-HSPA

6.4.1 Introduction

The operator is able to view KPI-values calculated from the performancemeasurements in the OMS Element Manager.




Network performance can be evaluated based on Key PerformanceIndicators (KPIs), which present some vital information regarding thenetwork. KPIs are either an individual counter or a combination of severalcounters, which are collected in the network. The idea behind the KPIconcept is that the information of one counter value rarely is verydescriptive as such, but combined with other counters it can providevaluable information on how well the network is functioning.

This feature enables I-HSPA OMS to calculate KPIs and show their resultsin Element Manager measurement presentation GUI. The operator canuse predefined KPIs or define own customized KPI formulas.


6.4.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE


N/A N/A N/A 0.0 OMS1.0 N/A N/A 3GPPRel-5



DN70500287Issue 1-1 en09/09/2008






ASW I-HSPA 0.0 0.0


Management data






6.5 ARAN2.0027: Threshold-based PM NotificationTriggering

6.5.1 Introduction

This feature makes it easier to detect faults, identify bottlenecks andoptimize the network.


The operator is able to set thresholds on performance management dataat I-HSPA OMS.


Using the OMS, the operator defines the appropriate performancethresholds for various important variables. If any of these thresholds areexceeded, it indicates a problem worth of attention, and OMS generatesan alarm that is shown in the Element Manager and NetAct. The variablescan be either single counters or Key Performance Indicators (KPIs); a KPI,in turn, can be a combination of several counters.



When performance data is gathered on variables of interest from themeasured objects in the network, their values are compared against anyactive threshold limits. When a performance threshold is exceeded, analert is generated and sent to the network management system. In additionto this, a threshold event log is saved in the network element for furtherstudy of the events that occurred in that NE during a certain period of time.

By doing threshold monitoring on the network element level, NetActcapacity can be saved for doing tasks related to the entire network. It maynot be in the interest of centralized network management to concentrateon individual faults, but the lowest level performance monitoring can bedone locally in the network elements.

This feature works also without NetAct connection because the generatedalarms can be seen in the OMS Element Manager.


6.5.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008






ASW I-HSPA Trust based Long-term ON/OFFlicense


Management data





71005 THRESHOLDMONITORING LIMITEXCEEDED

71006 WCELTHRESHOLDMONITORING LIMITEXCEEDED

71007 MEASUREMENTTHRESHOLDMONITORING LIMITEXCEEDED

6.6 ARAN189: Automatic Definition of NeighboringCells

6.6.1 Introduction

This feature introduces new measurements for HO statistics to verify theperformance of current adjacencies. These measurements can be usedfor neighbor cell list optimization.


OPEX savings result from faster and less resource consuming neighborlist optimization.



Increased revenue and improved end-user experience are acquiredthrough smaller number of dropped calls and better data throughput.Neighboring cell list optimization reduces the signaling load and ensuresfast and reliable HO process of Mobile Terminals.


The automatic definition of neighboring cells consists of operational andbasic RNW measurement aspects.

Operational aspect:

The operational aspect is the centralized performance analysis of currentadjacencies and automated optimization of the adjacency lists using theperformance statistics from I-HSPA RAN.

HO adjacency lists are initially defined with RNW planning based ongeographical locations and the estimated behavior of the cells. However,this is not the optimal case; unnecessary cells may be included ornecessary cells excluded.

In order to guarantee good NW performance immediately after launch, it isessential to be able to analyze the performance of current adjacency lists,and, if needed, to optimize the adjacencies according to the performancestatistics from operational cells. This process needs to be fast and reliableand therefore aided with appropriate tools. In Nokia Siemens Networksportfolio, NetAct Optimizer provides means to optimize the adjacency listsbased on measurements, while the other NetAct tools complement thesolution with centralized change management and performance datacollection and reporting tools.

Basic radio network performance measurement aspect:

In order to enable the NW management system to optimize the cellneighbor lists, counters are provided that measure the number ofattempted and successful handovers between source and target cell pairs.

In addition to using the measurement results in the optimizing procedure,the measurements can be activated and used as any other basicperformance measurements.

DN70500287Issue 1-1 en09/09/2008



Figure 18. HO lists creation


6.6.3 System impact




I-HSPAAdapter



GGSN/FlexiISN

UE



meas. activation

meas. reslts

new cand. list

meas. reslts

optimized adjacencylist

OSS I-HSPA

1 Cell # A2 Cell # B3 Cell # C4 Cell # D

1 Cell # A2 Cell # B3 Cell # C4 Cell # D5 Cell # E



1

2

3

1

2

3

HO measurements are collectedfor current adjacencies

Adjacency candidate lists are createdand performance is measured

Once all candidates are tested thefinal optimal lists are created








ASW NetAct I-HSPA NetAct Long-term ON/OFFlicense


Management data




NUMBER OF INTRAFREQUENCY SHO ATTEMPTS

NUMBER OF COMPLETEDINTRA FREQUENCY SHO

NUMBER OF INTERFREQUENCY HHO ATTEMPTS

NUMBER OF COMPLETEDINTER FREQUENCY HHO

NUMBER OF INTER SYSTEMHHO ATTEMPTS

NUMBER OF COMPLETEDINTER SYSTEM HHO


6.7 IHSW-23: KPI Support in I-HSPA Adapter

6.7.1 Introduction

I-HSPA Adapter collects the needed counters for the I-HSPA KPI values.

DN70500287Issue 1-1 en09/09/2008




I-HSPA KPIs help to identify network and I-HSPA network element status.

They include values such as cell availability, radio connection setup rates,radio connection drop rates, cell throughput, and lost packets on radiolayer. I-HSPA Adapter provides means to collect the I-HSPA counters forKPIs.


6.7.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE


N/A N/A N/A OSS5.1 OMS1.0 N/A N/A N/A






OSW I-HSPA - -




Management data






6.8 ARAN232: CPICH Ec/No Coverage Measurementsand Optimization

6.8.1 Introduction

The feature introduces new counters for measuring the pilot channel signalover noise ratio.

These counters can be used for interference and coverage optimization.


OPEX savings are achieved because of faster and less resourceconsuming coverage and interference optimization.

Improved cell coverage and capacity mean increased revenue.


After the 3G network launch, the operator can tune the CPICH power for:

. Increasing NW capacity and coverage

. Controlling interference

DN70500287Issue 1-1 en09/09/2008



The capacity gain in an interference limited case can be approximately 5%or higher, since all common channels are set up with respect to the CPICHpower. As a result, this feature provides essential information about thequality of the current CPICH power setting and guides to setting of theoptimal value. This feature also provides useful information for automatedantenna tilt and setting the baseline power levels for HO and loadbalancing optimization.

When the UE sends the 1A event triggered intra-frequency measurementreport to the Serving I-HSPA Adapter in the MEASUREMENT REPORT(RRC) message, the CPICH Ec/No measuring is done. The receivedmeasurement report contains the cellspecific information about the CPICHEc/No value mapped from the CPICH Ec/Io reporting range by the UE.The CPICH Ec/No measuring is done for the best Serving I-HSPA Adapterside cell, which can be either one of the current active set cells, or one ofthe event triggered cells.

To gather the data into a logical format, the CPICH Ec/No measurementcan be split into classes in relation to the reported CPICH Ec/No value.These classes represent the measured quantity value area in dB. TableClasses for CPICH Ec/No coverage measurements below shows how theclasses are linked with the reported CPICH Ec/No values.

Class 9: CPICH Ec/Io < -24

Class 8: -24 <= CPICH Ec/Io < -22








Class 0: -5 <= CPICH Ec/Io

When the I-HSPA Adapter receives the 1A report from the UE, aclassification counter corresponding to the reported CPICH Ec/No value isupdated.



The histogram is used in NetAct Optimizer for analyzing the cellinterference situation and for guiding to correct optimization actions.


6.8.3 System impact






I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA 0.0 0.0


Management data


DN70500287Issue 1-1 en09/09/2008





CELL SPECIFIC CPICH EC/NO- CLASS 0













7 Adapter solution

7.1 IHSW-1: I-HSPA Rel. 1 Operational SW withCapacity Step 1

7.1.1 Introduction

Basic I-HSPA adapter SW functions for Release 1 at the initial capacitylevel, 1.8/0.6 Mbps (DL/UL).


HSPA offers a lower cost per bit and potentially creates new applicationareas with higher data rates and lower delay variance. This feature bringsthe basic performance gain of HSPA to the operator.


This feature provides I-HSPA Rel-1 Operational SW with capacity step 1.Capacity step 1 is initial capacity level, 1.8/0.6 Mbps (DL/UL). Whencapacity limit is achieved, all new incoming service requests are rejected.


7.1.3 System impact





DN70500287Issue 1-1 en09/09/2008


Adapter solution


I-HSPAAdapter



GGSN/FlexiISN

UE










Management data






7.2 IHSW-2: I-HSPA Capacity Step 2

7.2.1 Introduction

This feature offers increased HSPA capacity to 3.6/1.2 Mbps (DL/UL).




The feature provides increased HSPA capacity.


This feature provides I-HSPA Rel-1 Operational SW with capacity step 2.Capacity step 2 is capacity level of 3.6/1.2 Mbps (DL/UL). When capacitylimit is achieved, all new incoming service requests are rejected.


7.2.3 System impact


Requires IHSW-1.




I-HSPAAdapter



GGSN/FlexiISN

UE









DN70500287Issue 1-1 en09/09/2008


Adapter solution


Management data






7.3 IHSW-3: I-HSPA Capacity Step 3

7.3.1 Introduction

This feature offers increased HSPA capacity to 7.2/2.4 Mbps (DL/UL).


The feature provides increased HSPA capacity.


This feature provides I-HSPA Rel-1 Operational SW with capacity step 3.Capacity step 3 is capacity level of 7.2/2.4 Mbps (DL/UL). When capacitylimit is achieved, all new incoming service requests are rejected.


7.3.3 System impact


Requires IHSW-1 and IHSW-2.






I-HSPAAdapter



GGSN/FlexiISN

UE










Management data






DN70500287Issue 1-1 en09/09/2008


Adapter solution



8 BTS solution

8.1 Frequency variants

8.1.1 ARAN999: Flexi WCDMA BTS 1700/2100


1700/2100 MHz (UL/DL) is a new frequency variant of Flexi WCDMA BTS.Two new radio modules are introduced:

. FRIA, 1700/2100 MHz with two Power Amplifiers supporting one ortwo carrier layers, and

. FRIB, 1700/2100 MHz with one Power Amplifier supporting onecarrier layer.








I-HSPAAdapter



GGSN/FlexiISN

UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data

Parameters

Table 209. ARAN999: Flexi WCDMA BTS 1700/2100 impact on parameters

Parameter Use

UTRA Absolute Radio FrequencyChannel Number

Downlink carrier frequency of theadjacent WCDMA RAN cell.


Defines the downlink carrier frequencyof the WCDMA RAN cell.



UTRA Absolute RadioFrequency ChannelNumber






UTRA Absolute RadioFrequency ChannelNumber

8.1.2 ARAN914: Flexi WCDMA BTS 1900


Flexi WCDMA BTS 1.9 GHz support.


Flexi WCDMA BTS 1.9 GHz RF Modules (HW & SW) and System ModuleSW support for 1.9 GHz band.

FRFA is Flexi WCDMA RF Module 1.9 GHz with 2 PA supporting one ortwo sectors.

FRFB is Flexi WCDMA RF Module 1.9 GHz with 1 PA supporting onesector.

This is band II in 3GPP spec rel-5:

. Uplink: 1850 - 1910 MHz

. Downlink: 1930 - 1990 MHz








I-HSPAAdapter


UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA - -

Management plane

Management data

Parameters:

Table 212. ARAN914: Flexi WCDMA BTS 1900 impact on parameters

Parameter Use















Flexi WCDMA BTS to support 850 MHz RF band with 850 MHz RF Modulevariants.


New 850 MHz units:

. FRCA - RF Module 850 MHz with 2 PA supporting one or twosectors

. FRCB - RF Module 850 MHz with 1 PA supporting one sector

This is band V in 3GPP rel-6:

. Uplink: 824 - 849 MHz









I-HSPAAdapter


UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA - -

Management plane

Management data

Parameters:


Parameter Use















Flexi WCDMA BTS to support 900 MHz band with new RF modules.


Flexi WCDMA BTS 900 MHz RF Modules (HW & SW) and System ModuleSW support for 900 MHz band.

FRDA is Flexi WCDMA RF Module 900 MHz with 2 PA supporting one ortwo sectors.

FRDB is Flexi WCDMA RF Module 900 GHz with 1 PA supporting onesector.

This is band VIII in 3GPP rel-7:

. Uplink: 880 - 915 MHz










DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE

I-HSPAAdapter

BTSrelease(Flexi)

CombiSGSN

GGSN/FlexiISN








OSW I-HSPA - -

Management plane

Management data

Parameters:


Parameter Use















Flexi WCDMA BTS to support 2000 MHz RF band with 2000 MHz RFModule variants.


I-HSPA implements one carrier 1+1+1 configuration with 2.0 GHz band forUS market. New frequency variant needs to fill extremely tight out of bandemissions requirements due to FCC regulations that in practice require theexternal filter as well. In addition to the external filter, the carrier will be setin the middle of the 10 MHz band so that 2.4 MHz guard band can beutilized and out of band requirements are fulfilled.

The whole allocated band:

. UL: 2000 - 2020 MHz

. DL: 2180 - 2200 MHz








I-HSPAAdapter


UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA - -

Management plane

Management data

Parameters:


Parameter Use













8.2 Synchronization

8.2.1 IHSW-7: External Synchronization Support


Flexi I-BTS synchronization can be derived from ATM/TDM or externalGPS.


Multiple methods available to provide Flexi I-BTS synchronization.


Synchronization can be derived from ATM/TDM signal via Flexi transportmodule and it can also be derived from another synchronized element onthe BTS site. Other synchronized elements on the BTS site include GPSreceivers and 2G or 3G BTSs receiving synchronization from TDM.

Synchronization signal is connected to Flexi System Modulesynchronization port except for inband synchronization via Flexi transportmodule.







DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






8.2.2 ARAN943: Synchronizing WCDMA RAN (Flexi WCDMA BTS)


For proper operation, all RAN elements need to be synchronized to acommon clock source. The synchronization needs to be considered whenthe RAN network is planned, so that a good quality clock is availableeverywhere in the RAN network.



Each element basically synchronizes its operation to one of its physicaltransmission line interfaces. This is the normal operating condition. If aconnection is broken, the synchronization is lost and the element startsusing the next predefined source (another line interface). Ultimately, if allsecondary sources fail, the element operates on its local clock, withtypically poorer frequency accuracy.

In a case of Ethernet transport, BTS can be synchronized using externalsynchronization source like GPS.

The BTSs require a highly accurate, stable clock for the air interface. Thebasic reference is typically still obtained via the transmission line interface,but the clock signal is first purified from jitter and wander.








I-HSPAAdapter



GGSN/FlexiISN

UE








DN70500287Issue 1-1 en09/09/2008


BTS solution




OSW I-HSPA - -

Management plane

Management data






8.2.3 ARAN1222: Support for External GPS Synchronization in Flexi BTS


The BTS will get the synchronization signal (1 pps) from an external GPSdevice. The GPS signal is needed together with the I-HSPA module orwhen the Ethernet transport is in use.

The GPS device is over voltage protected by mediator box that includes:

1. Power output (12 VDC) to the GPS receiver.

2. GPS signal transfer from GPS receiver to MDR26 connector inSystem Module.

3. Overvoltage protection (4K V) must be guaranteed according to thestandard for mast devices, which prevents System Module failures.

4. Min IP55 protection.



5. Three cables (GPS - BOX, BOX - MDR26, and BOX – 48 VDC) mustbe provided between GPS and Rel1 System Module.

6. HW support for GPS power reset. The power feeding towards GPSreceiver must be implemented via a relay contact. It must bepossible to shut down GPS power to cause a GPS reset (like in FSP/ FTM). The shutdown of the GPS power shall be doneindependently of a System Module reset, that is, System Modulereset does not cause the GPS reset to avoid the GPS satellitesurvey during a BTS reset.

The PPS output signal in SOUT (MDR14) must be phase locked to thePPS input in SIN (MDR26). In case there is no PPS input signal, the PPSoutput signal shall be disabled as well.








I-HSPAAdapter



GGSN/FlexiISN

UE





DN70500287Issue 1-1 en09/09/2008


BTS solution




OSW I-HSPA - -

Management plane

Management data






8.3 BTS scheduler

8.3.1 ARAN869: HSDPA BTS Packet Scheduler


The HSDPA BTS Packet Scheduler is a fast BTS-based schedulerdetermining the bit rates to be used for HSDPA services.


The HSDPA BTS Packet Scheduler with a round-robin principle is a robustscheduler for achieving good HSDPA cell throughput.


Round-robin scheduler is used for the MAC-hs packet-schedulingalgorithm serving users in sequential order. It is a robust schedulerachieving resource-fair HSDPA cell throughput. On the average, the UEsclose to the BTS get clearly higher bit rates than users on the cell edge.Those users with no data ready for transmission in the BTS buffer are notconsidered for scheduling.










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






DN70500287Issue 1-1 en09/09/2008


BTS solution

8.3.2 RAN849: HSDPA Proportional Fair Resource Packet Scheduler


The high-speed downlink packet access (HSDPA) Proportional FairPacket Scheduler feature provides a multi-user diversity gain of 30%-60%in terms of improved HSDPA cell throughput for low to medium UE speeds,depending on the environment.


Improved end-user experience is acquired by increased HSDPA cellthroughput.


The proportional fair resource (P-FR) algorithm is used for the MAC-hspacket scheduling in the BTS. This algorithm utilizes the radio channelstate information from the UEs in its scheduling decisions. The P-FRprinciple is to select one UE among those active users that have data intheir buffers and are not limited by their capabilities for selection, tomaximize the relative instantaneous channel quality (ratio ofinstantaneous throughput to average throughput) for scheduling in thefollowing 2 ms transmission time interval (TTI). The relative instantaneouschannel quality is calculated in every 2 ms TTI.



Figure 19. HSDPA proportional fair scheduling








I-HSPAAdapter


UE

HSDPA uses fast feedback from mobile

Terminal sends fast L1 feedback to Flexi WCDMA BTS

- Channel Quality Info (CQI)

- Transmission period typically every 4 ms

CQI is used by HSDPA packet scheduling

- Link adaptation

- Multiuser scheduling decisions

Propotional fair schedulingprinciple: allocate resources to

the best user leading tomultiuser diversity gain

L1 Feedback(CQI)

Data

TTI 1 TTI 2 TTI 3 TTI 4

User 1 CQI

User 2 CQI

Scheduled user

DN70500287Issue 1-1 en09/09/2008


BTS solution

Table 230. Software dependencies for feature RAN849 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN









Management plane

Management data






8.3.3 RAN1034: Shared HSDPA Scheduler for Baseband Efficiency


This feature enables simultaneous HSDPA transmission to a maximum ofthree HSDPA-capable cells by using one submodule in Flexi BTS.



Shared HSDPA Scheduler supports 48 HSDPA users per BTS. 10.8 Mbpsmaximum HSDPA throughput per BTS is provided. 15 codes per cell and45 codes per BTS are supported. The peak bit rate for single user is 7.2Mbps.


Statistical multiplexing gain and superior baseband efficiency result inCAPEX and OPEX savings. HSDPA throughput and users from up to threecells can be multiplexed in single Shared HSDPA Scheduler requiring.Superior performance is gained with a minimum number of CEs.

Increased HSDPA capacity means increased revenue and better end-userexperience. HSDPA capacity is increased both in terms of number of userssupported and cell throughput. The increased capacity improves end-userperformance with higher average bit rates.


The Shared HSDPA Scheduler for Baseband Efficiency allows a singlesubmodule to handle the processing of HSDPA for 1, 2 or 3 cellssimultaneously. The submodule supports 48 simultaneous HSDPA users.These users can be divided in any combination among the cells handledby the submodule.

It is possible to use all 15 HSDPA codes in all three cells simultaneouslywith the Shared HSDPA Scheduler for Baseband Efficiency scheduler.However, on each TTI the total bit rate over all cells has to be below 10.8Mbps. Therefore, even though there is no code limitation, the throughput islimited to 10.8 Mbps per submodule in Flexi. On those TTIs where the totalbit rate for all scheduled UEs would exceed 10.8 Mbps, the Flexi WCDMABTS will clip data from the highest bit rate user so that the maximum limitof 10.8 Mbps is not exceeded.

Note that using 15 codes simultaneously in each cell is beneficial evenwith the total bit rate limitation, since in optimal link adaptation the numberof codes is increased prior to increasing coding rate or modulation. Forexample, the 15th code should be taken into use already at 2.4 Mbpswhen codes are available, since spectrally this is more efficient than usingless codes but having higher order modulation or less robust errorprotection coding.

Therefore, all 45 codes of three cells can be taken to full use when the totalthroughput in the BTS is 3 x 2.4 Mbps = 7.2 Mbps. As a result, the ability touse all 15 codes in each cell simultaneously increases the practicalaverage cell throughputs significantly, even though the theoretical peakthroughputs are not affected.

DN70500287Issue 1-1 en09/09/2008


BTS solution

The benefit of the Shared HSDPA Scheduler for Baseband Efficiency ismore efficient utilization of baseband capacity. For 1+1+1 configuration,one submodule with Shared HSDPA Scheduler for Baseband Efficiencyoffers almost the same performance as three submodules. The loss inperformance is due to the fact that the total combined bit rate on each TTIhas to be below 10.8 Mbps. However, as the air interface limits theaverage cell throughput to around 2 Mbps in macro environment, there isno real difference in cell level throughput.

Note that code shared scheduler is offering clearly better performance onthe air interface compared to using 32 CE reservation. This is due to theface that with code shared scheduler each cell is capable of achieving thepeak bit rate of 10.8 Mbps when other cells are not loaded. Moreover,since code shared scheduler has no limitation on the number of codes, thelink adaptation algorithm is able to use spectrally more efficient method ofincreasing number of codes beyond five before going to more robustcoding rate and higher order modulation. This means that on given SINRconditions, 1+1+1 Flexi WCDMA BTS with code shared scheduler offerssignificantly better throughput than static allocation of 5 codes per sector.








I-HSPAAdapter



GGSN/FlexiISN

UE











Management plane

Management data






8.3.4 ARAN968: HSUPA BTS Packet Scheduler


HSUPA BTS Packet Scheduler is a fast BTS based scheduler determiningthe bit rates to be used on E-DCH.

This increases the efficiency at which especially bursty data can be treatedby the packet scheduler.


Increased UL data throughput improves the end-user experience. Inaddition, increased cell UL capacity results in CAPEX and OPEX savings.


HSUPA BTS Packet Scheduler (PS) is a cell-specific scheduler using 10ms scheduling periods with both Absolute Grants (AG) and RelativeGrants (RG). The scheduling decisions are based on the maximumallowed noise rise and the physical layer feedback from the UEs in a cell.The HSUPA BTS PS also takes into account the available basebandresources not needed for R'99 DCHs.

DN70500287Issue 1-1 en09/09/2008


BTS solution

In a case where air interface and NW resources do not limit the data rates,each UE is given as much bit rate as they request, up to maximum of 2.0Mbps. The scheduling grant determined by the PS is applicable to allHARQ processes of the UE.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data








8.4 MHA and antenna

8.4.1 ARAN908: Flexi WCDMA BTS AISG MHA Support


Flexi BTS has integrated Bias-T HW in Radio module to control NokiaSiemens Networks or 3rd party AISG 2.0 MHAs. This integrated HW-based SW functionality has to be enabled by a specific SW license.


Bias-T is integrated to the RF module of Flexi BTS. It feeds DC power tothe MHA and controls the MHA DC power current consumption. If thecurrent consumption is out of a specified window, an alarm is generated.AISG has specified additional control functionality for MHA. This control isdone over OOK modulation using the antenna feeder.

In Flexi BTS, this AISG (or later 3GPP) MHA power feeding and enhancedMHA alarm control must be enabled by a SW license because the HW isintegrated to all RF Modules.








I-HSPAAdapter


UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA BTS LK -

Management plane

Management data






8.4.2 ARAN907: Antenna Line Supervision


BTS has an integrated antenna line supervision in Radio module to controlantenna line condition by VSWR measurement. This integrated HW basedfunctionality has to be enabled by a specific SW license.




The antenna line supervision is integrated to the RF module of Flexi BTS.It measures the VSWR, that is, the reflected RF power of the BTS TXantenna branch.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA BTS LK -

Management plane

Management data


DN70500287Issue 1-1 en09/09/2008


BTS solution





8.4.3 RAN1046: Feederless Site Solution for Flexi WCDMA BTS


Feederless Site Solution up to 200 m for Flexi WCDMA BTS.


Feederless Site Solution for Flexi WCDMA BTS offers an alternative wayto provide WDCMA BTS site solutions, especially cost and performancedegradation resulting from the installation of long feeder cables can beavoided.


Feederless site is a site where the Radio Head (RH) is as close to theantenna as possible. The distance between the RH and the antenna isonly a few meters, so, in practice, the Feederless Site is a solution thatdoes not require any traditional thick feeder cables. SM can be freelylocated (by an optical interface) up to 200 m away from the RH, closer tothe transmission termination point and to the location with easier accessfor the operator. Both SM and RH apply to indoor and outdoor installations.








I-HSPAAdapter



GGSN/FlexiISN

UE



Table 240. Software dependencies for feature RAN1046 (cont.)

I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data






8.4.4 ARAN905: Flexi WCDMA BTS Nokia Siemens Networks MHASupport


Flexi BTS has integrated Bias-Ts in Radio module to control NokiaSiemens Networks MHA (for example, WMHC). This integrated HW has tobe enabled by a specific SW license.

DN70500287Issue 1-1 en09/09/2008


BTS solution


The Bias-T is integrated to the Flexi BTS RF module. The Bias-T feeds DCpower to the MHA and controls the MHA DC power current consumption. Ifcurrent consumption is out of a specified window range, an alarm isgenerated.

In Flexi BTS, the MHA power feeding and alarm control must be enabledby a SW License.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA BTS LK -



Management plane

Management data






8.4.5 ARAN906: Flexi WCDMA BTS 3GPP Antenna Tilt Support


Flexi BTS has an integrated Antenna Tilt control HW in Radio module tocontrol the 3GPP Tilt Antennas. This integrated Antenna tilt HW is enabledby a specific SW license.


Antenna Tilt is integrated to the RF module of Flexi BTS. It feeds DC powerto the antenna and controls the antenna tilting.

In Flexi BTS this 3GPP specified antenna tilting functionality must beenabled by a SW license.








I-HSPAAdapter



GGSN/FlexiISN

UE

DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA BTS LK -

Management plane

Management data






8.4.6 ARAN1223: Flexi WCDMA BTS Mast Head RF Module 2.1 20 W


. Fully outdoor/indoor capable Mast Head RF Head for Wide Areasolutions

. Optical link between Head and System Module

. Supports Obsai/RP3 -interface (interface similar to the one in FlexiWCDMA BTS RF Module)



. No fans

. Supports only DC-voltage

. Support for two carriers

. HW is 50 W Power amplifier (40 W in antenna connector)

. 20 W (in antenna connector) is default o/p power; 40 W carrier powersupport (I1002) and second carrier support (I1001) are silencedfeatures

. Operating temperature range -33º - +55ºC

. Antenna shape








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

DN70500287Issue 1-1 en09/09/2008


BTS solution

Management plane

Management data






8.4.7 ARAN1079: Sameband Combiner for Flexi WCDMA BTS 850 MHz (TxCarrier Combiner for Dual Duplex Support)


Sameband combiner for Flexi WCDMA BTS 850 MHz (Tx carrier combinerfor Dual duplex support).


Common feeders and antennas can be used for GSM and UMTS systemsoperating on the same system band. This solution will make it possible tobuild an antenna line-sharing site with minimum effect on the existingGSM/EDGE system performance and with maximized UMTSperformance:

. Only minor performance degradation in GSM DL power

. Only slight performance degradation in WCDMA DL power

. MHA will retain the UL performance. If BTS supports an adjustable front-end gain (Nokia Siemens

Networks Flexi WCDMA BTS feature), the original sensitivitycan be maintained, otherwise a slight degradation of sensitivityoccurs.

. No internal connections to/from BTSs needed

. Suitable for integrated BTSs

. No wasted spectrum for guard bands needed










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






DN70500287Issue 1-1 en09/09/2008


BTS solution

8.4.8 ARAN1139: Sameband Combiner for Flexi WCDMA BTS 900 MHz (TxCarrier Combiner for Dual Duplex Support)


Sameband combiner for Flexi WCDMA BTS 900 MHz (Tx carrier combinerfor Dual duplex support).


Common feeders and antennas can be used for GSM and UMTS systemsoperating on the same system band. The solution will make it possible tobuild an antenna line-sharing site with minimum effect on existing GSM/EDGE system performance and with maximized UMTS performance:

. Only minor performance degradation in GSM DL power

. Only slight performance degradation in WCDMA DL power

. MHA will retain the UL performance. If BTS supports an adjustable front-end gain (Nokia Siemens

Networks Flexi WCDMA BTS feature), the original sensitivitycan be maintained, otherwise a slight degradation of sensitivityoccurs.

. No internal connections to/from BTSs needed

. Suitable for integrated BTSs

. No wasted spectrum for guard bands needed










I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data






8.4.9 ARAN1462: Sameband Combiner for Flexi WCDMA BTS 2100MHz(Tx Carrier Combiner for Dual Duplex Support)


When building overlay with I-HSPA BTS on top of third party RAN, theantenna lines, elements and Mast Head Amplifiers can be shared.


Shared antenna lines, elements and MHAs reduce CAPEX and OPEX.

DN70500287Issue 1-1 en09/09/2008


BTS solution


Multiradio combiner (MRC) makes it possible to use common feeders andantennas for two WCDMA systems operating on the same frequencyband. This solution provides a cost efficient way to add a new WDCMABTS to an existing site by combining signals of the two BTSs into oneantenna system.

The use of MRC has minimal performance impact on WCDMA BTS. LowDL insertion loss of 0.5 dB means only minor performance degradation intransmit power. MRC losses in UL path are compensated with an MHA,and if the BTS supports an adjustable front end gain (Flexi WCDMA BTSand UltraSite), the degradation of original sensitivity is marginal.








I-HSPAAdapter



GGSN/FlexiISN

UE













OSW I-HSPA 0 0

Management plane

Management data






8.5 Supplementary BTS solution

8.5.1 ARAN912: License-based BTS Channel Capacity


In Flexi WCDMA BTS HW channel capacity is integrated to Flexi WCDMABTS System Module without any plug-in cards. The operator candynamically enable as many channel elements as needed to FlexiWCDMA BTS site by downloading a Capacity SW License key file. CostlyBTS site visits to install more HW channel plug-in cards are thus avoided.

Without any installed license file, 32 channel elements are available.







DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA BTS LK -

Management plane

Management data






8.5.2 ARAN1000: Baseband Extension for Flexi WCDMA BTS


Second System Module (FSMB) in extension mode brings additionalbaseband processing power and capacity to BTS site to handle largervariety of air interface services.




Second System Module is not equipped with transmission submodule. Forusing System Module as extension module will require Extension Kit(FSKA, that is, cables and dummy transmission submodule).








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data


DN70500287Issue 1-1 en09/09/2008


BTS solution





8.5.3 ARAN1002: Flexi WCDMA BTS 40 W Carrier Power Support


Flexi WCDMA BTS 40 W Carrier Power license will activate full 40 Wpower to Flexi WCDMA BTS Radio Module.


The output power min 40 W per carrier is available with Radio Module.

Dual Radio Module can support one or two sectors. For 1+1+1 (min 40 Wper carrier) or 2+2+2 (min 20 W per carrier) configurations only oneSystem Module and one Dual and one Single Radio Modules are requiredfor a complete WCDMA BTS system.

Up to 1+1+1 at 40 W are supported in I-HSPA release 1.0.








I-HSPAAdapter



GGSN/FlexiISN

UE










OSW I-HSPA BTS LK -

Management plane

Management data






8.5.4 ARAN1144: Flexi WCDMA BTS 8 W RF Power Limitation


This feature enables 8 W RF power operation with Flexi BTS.


Same Flexi BTS HW variant can be used on macro and micro sites.Logistics and spare part costs will be lower.


This feature makes it possible to limit the Flexi BTS RF power into 8 W withthe current 20/40 W RF module. It makes it possible to limit the maximumallowed RF exposure from the BTS especially on micro sites. The RFexposure limits depend on national or local legislation in each country.

The operator can select the 8 W mode in the commissioning phase of FlexiBTS. The Flexi BTS RF module will internally limit the output power into 8W with control cycle of less than 1 ms.

DN70500287Issue 1-1 en09/09/2008


BTS solution








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

Management plane

Management data








8.5.5 ARAN1145: Flexi WCDMA BTS RF Module with AC Input Power


Optional AC/DC module can be equipped to FlexiBTS 1-sector RF modulein the empty place of the second antenna filter.


The feature provides a more integrated feederless site (RF head) solutioncompared to the existing one.








I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -

DN70500287Issue 1-1 en09/09/2008


BTS solution

Management plane

Management data






8.5.6 ARAN1146: Flexi WCDMA BTS Horizontal Mounting Kit for GSMEDGE BTS


Mounting kit provides Flexi BTS modules (max 5 pcs) support for UltrasiteGSM EDGE in horizontal position.


The customer can "empty" the low part of the GSM EDGE BTS (6 TRX'srack) in the field and add this kit into the cabinets, which then gives roomfor Flexi BTS modules.

The same kit can be installed either to the indoor or the outdoor GSMEDGE BTS.








I-HSPAAdapter


UE




I-HSPAAdapter



GGSN/FlexiISN

UE

BTSrelease(Flexi)

GGSN/FlexiISN








OSW I-HSPA - -

Management plane

Management data






8.5.7 RAN1093: HSDPA 16QAM SW License Support


Enables SW licensing to HSDPA 16QAM feature (RAN764).

DN70500287Issue 1-1 en09/09/2008


BTS solution


The HSDPA 16QAM support is implemented.








I-HSPAAdapter



GGSN/FlexiISN

UE









Management plane

Management data








8.5.8 ARAN1127: Extended Cell (180 km)


With this feature, the cell radius is extended to up to 180 km.


This feature offers an economical method for building WCDMA coveragein rural areas.


The 3G extended cell feature can be used to efficiently provide coveragein coastal and rural areas, where big capacity or high data rates are notneeded. Furthermore, new lower WCDMA frequency bands 850 MHz and900 MHz make it possible to achieve larger cell sizes and utilize theexisting GSM cell raster.

The feature is also needed with optical repeater cases (train tunnels, FlexiBTS remote RF heads) to overcome the decreased cell radius caused bythe delay of optical cables. BTS has the main functionality of this feature.The feature is activated from the NetAct with the Cell Range parameter.The operator has the possibility to modify Cell Range Parameter to up to180 km. The shorter extended cell ranges are 35 km and 60 km.

In 3GPP, RACH/AICH detection and transmit power control delays definethe cell range. The cell range 180 km is available with 2-port receiverdiversity. The feature activation is based on SW licenses.







DN70500287Issue 1-1 en09/09/2008


BTS solution


I-HSPAAdapter



GGSN/FlexiISN

UE








ASW I-HSPA RNC LK Long-term ON/OFFlicense

Management plane

Management data

Parameters

Table 270. ARAN1127: Extended Cell (180 km) impact on parameters

Parameter Use

Cell range Defines the maximum range of the cell.



Cell range No counters related to this feature No alarms related to this feature



8.6 ARAN900: Flexi WCDMA BTS


Flexi WCDMA BTS consists of self-supporting BTS modules that are smalland light enough for one person to carry to the site:

. Radio Module

. System Module

. Optional Power Supply Module with battery backup

Optional outdoor and indoor cabinets with long-term battery backup is alsoavailable.

Flexi WCDMA BTS architecture and modules provide 12-carrier capacity:up to six sectors or four carriers per sector configurations are available inlater SW releases according to Nokia Siemens Networks RAN Roadmap.The output power min 20 W and min 40 W per carrier is available withRadio Module equipped with one or two 50 W Power Amplifiers.

Dual Radio Module can support one or two sectors. For 1+1+1 (min 40 Wper carrier) or 2+2+2 (min 20 W per carrier) configurations only oneSystem Module and one Dual and one Single Radio Modules are requiredfor a complete WCDMA BTS system.

Up to 1+1+1 at 20 W or 40 W are supported in I-HSPA release 1.0.

The baseband capacity of the System Module can be added remotely witha SW-license when needed.

Flexi WCDMA BTS is based on the OBSAI (Open Base StationArchitecture Initiative) architecture enabling the multiradio platform forfuture radio technologies.


8.6.2 System impact



DN70500287Issue 1-1 en09/09/2008


BTS solution




I-HSPAAdapter



GGSN/FlexiISN

UE








OSW I-HSPA - -


Management data

Parameters:

Table 273. ARAN900: Flexi WCDMA BTS impact on parameters

Parameter Use












DN70500287Issue 1-1 en09/09/2008


BTS solution

Date post:	07-Jan-2017
Category:	Documents
Upload:	emerson-eduardo-rodrigues-pmp
View:	252 times
Download:	2 times

I hspa rel-1_feature_description

Documents