Iuh Parameter Guidelines for R3 - Cisco...Iuh Parameter Guidelines for R3.7

Iuh Parameter Guidelines for R3.7 30 May 2017

Version 2.5

Please refer to the important note on the following page. Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000 800 553-NETS (6387) Fax: 408 527-0883

Ref: UBS-44-53-006

http://www.cisco.com/

Iuh Parameter Guidelines for R3.7 ▄ UBS-44-57-004 ii

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

© 2015 Cisco Systems, Inc. All rights reserved.

▄ Iuh Parameter Guidelines for R3.7

iii

Contents

1 REFERENCES ........................................................................................................................................................... 7 1.1 STANDARDS ........................................................................................................................................................... 7 1.2 DOCUMENT REFERENCES ...................................................................................................................................... 7

2 DEFINITIONS AND ABBREVIATIONS ................................................................................................................ 8

3 OPERATION AND MAINTANANCE: TR-069 PROTOCOL .............................................................................. 9 3.1 INTRODUCTION ...................................................................................................................................................... 9 3.2 PARAMETERS ACCESS AND PROPERTY .................................................................................................................. 9 3.3 MANAGEMENT LEVEL ........................................................................................................................................... 9 3.4 SUPPORT OF TR-069 ............................................................................................................................................ 10

3.4.1 Parameters Requiring Reboot ..................................................................................................................... 10 3.4.1.1 List of Parameters Requiring Reboot ........................................................................................................................ 10

3.5 DEVIATIONS FROM TR196 PARAMETERS ............................................................................................................. 12

4 CORE NETWORK PARAMETERS ...................................................................................................................... 15 4.1 THE ROOT OBJECT: INTERNETGATEWAYDEVICE ................................................................................................ 16

4.1.1 Device Summary ......................................................................................................................................... 16 4.2 DEVICE INFORMATION ......................................................................................................................................... 17 4.3 TIME, IP-TIMING AND FREQUENCY DISCIPLINE ................................................................................................... 21

4.3.1 Validity of Digital Certificates .................................................................................................................... 25 4.3.2 Frequency Discipline .................................................................................................................................. 26

4.3.2.1 Parameters Related to IP Timing .............................................................................................................................. 27 4.3.3 Time and Timezones .................................................................................................................................... 28

4.3.3.1 Timezone Parameters ................................................................................................................................................ 29 4.4 CONFIGURATION OF MANAGEMENT SERVER ....................................................................................................... 29 4.5 WAN DEVICE ...................................................................................................................................................... 33

4.5.1 DHCP Settings ............................................................................................................................................ 36 FAP SERVICE .................................................................................................................................................................. 39 4.6 CAPABILITIES ...................................................................................................................................................... 43

4.6.1 UMTS Capabilities...................................................................................................................................... 44 4.6.2 UMTS Self-Configuration Capabilities ....................................................................................................... 47

4.7 FAP CONTROL ..................................................................................................................................................... 52 4.7.1 Enabling of UMTS Capabilities .................................................................................................................. 55 4.7.2 Gateways Configuration ............................................................................................................................. 55

4.7.2.1 Further HNB-GW Parameters ................................................................................................................................... 59 4.7.3 Software Upgrade Configuration ................................................................................................................ 60 4.7.4 Timers ......................................................................................................................................................... 63

4.8 CALL ADMISSION CONTROL ................................................................................................................................ 64 4.8.1 Access Management Parameters ................................................................................................................ 65 4.8.2 Redirection to LTE ...................................................................................................................................... 70 4.8.3 IMSI White List Filtering in Open Mode .................................................................................................... 71 4.8.4 Traffic Hot-spot Management ..................................................................................................................... 71 4.8.5 Rejection and Redirection ........................................................................................................................... 71 4.8.6 Emergency Calls ......................................................................................................................................... 74

4.8.6.1 Non Provisioned User Emergency Calls ................................................................................................................... 74 4.8.7 Cell Restriction ........................................................................................................................................... 78

4.8.7.1 Access-Class Barring ................................................................................................................................................ 79 4.9 CELL CONFIGURATION FOR UMTS...................................................................................................................... 83

4.9.1 CN Configurations ...................................................................................................................................... 84 4.9.1.1 CN Configuration Extensions ................................................................................................................................... 89

4.9.2 RAN Configuration ..................................................................................................................................... 90 4.9.2.1 Parameters used for Configuring the RAN ............................................................................................................... 90

4.9.3 Cell Level Configurations ........................................................................................................................... 93 4.9.3.1 SIB19 ........................................................................................................................................................................ 98 4.9.3.2 Extensions to Cell Level Configuration .................................................................................................................. 103

4.9.4 Cell Selection ............................................................................................................................................ 104

Iuh Parameter Guidelines for R3.7 ▄ UBS-44-57-004 iv

4.9.4.1 Category A: Co-channel Femtocell Deployment .................................................................................................... 104 4.9.4.1.1 Co-channel Rove-in ........................................................................................................................................... 104 4.9.4.1.2 Co-channel Sintrasearch based Rove Out .......................................................................................................... 105

4.9.4.2 Category B: Dedicated Channel Femtocell Deployment ......................................................................................... 105 4.9.4.2.1 Dedicated channel Rove-in ................................................................................................................................ 106 4.9.4.2.2 Dedicated channel Sintrasearch based Rove Out ............................................................................................... 106

4.9.4.3 Category C: HCS-Enabled Femtocell Deployment ................................................................................................. 106 4.9.4.3.1 HCS Rove-in ..................................................................................................................................................... 107 4.9.4.3.2 HCS Rove Out ................................................................................................................................................... 107

4.9.4.4 Overview of Intra/Inter Frequency Cell Reselection ............................................................................................... 107 4.9.4.5 Measurement Rules for Cell Re-selection when HCS is used ................................................................................. 108 4.9.4.6 RSCP Based Handover ........................................................................................................................................... 111 4.9.4.7 Cell Selection Parameters ....................................................................................................................................... 112

4.9.5 RRC Timers ............................................................................................................................................... 119 4.9.6 DRX ........................................................................................................................................................... 121 4.9.7 Power Control ........................................................................................................................................... 122

4.9.7.1 Power Control ......................................................................................................................................................... 123 4.9.8 Intra Frequency Masurements .................................................................................................................. 125

4.9.8.1 Parameters for Intra Frequency Measurements ....................................................................................................... 125 4.9.9 Inter Frequency Measurements ................................................................................................................ 134

4.9.9.1 Parameters for Inter Frequency Measurements ....................................................................................................... 134 4.9.9.2 Inter Frequency Handovers Extensions ................................................................................................................... 140

4.9.10 Inter RAT Measurements .......................................................................................................................... 141 4.9.11 UE Internal Measurements ....................................................................................................................... 145 4.9.12 State Transition Measurement .................................................................................................................. 147

4.9.12.1 State Transition Measurement Extensions .......................................................................................................... 147 4.9.13 RF and Power Management ..................................................................................................................... 148

4.9.13.1 Manual and Load Based Reselection .................................................................................................................. 148 4.9.13.2 Power Management Process ............................................................................................................................... 148 4.9.13.3 Initial DL Power Setting ..................................................................................................................................... 149 4.9.13.4 Initial UL Power Setting (Maximum Femto UE Transmit Power) ..................................................................... 149

4.9.13.4.1 Parameter Analysis: RRMProfile.ULNoiseMargin and RRMProfile.NodeBNoiseFloor ................................ 149 4.9.13.5 Dynamic DL and UL Power Adaptation ............................................................................................................ 150 4.9.13.6 DCH Power Reallocation ................................................................................................................................... 150 4.9.13.7 Dynamic HSDPA Power Allocation ................................................................................................................... 151 4.9.13.8 Dynamic Noise Rise Target Management for HSUPA/R99 Coexistence ........................................................... 151 4.9.13.9 RF Parameters .................................................................................................................................................... 151

4.9.13.9.1 RRM Profile .................................................................................................................................................... 161 4.9.13.9.2 RRM Profile: Frequency Configuration .......................................................................................................... 170 4.9.13.9.3 RRM Profile: Sniffing Functionality ............................................................................................................... 171 4.9.13.9.4 RRM Profile: RRM Status ............................................................................................................................... 171 4.9.13.9.5 RRM Profile: Poor RF QoS Alarm Configuration ........................................................................................... 172 4.9.13.9.6 Enhanced Poor RF QoS Alarms ...................................................................................................................... 173 4.9.13.9.7 RRM Profile: Load Based Coverage Tuning ................................................................................................... 173 4.9.13.9.8 RRM Profile: Discovery of Scrambling Codes ................................................................................................ 176 4.9.13.9.9 RRM Profile: LAIs .......................................................................................................................................... 177 4.9.13.9.10 RRM Profile: Unclassified Primary Scrambling Codes ................................................................................. 179 4.9.13.9.11 RLC Configuration ........................................................................................................................................ 179 4.9.13.9.12 Dynamic DL Power Allocation ..................................................................................................................... 179 4.9.13.9.13 Dynamic UL Power Allocation ..................................................................................................................... 183 4.9.13.9.14 Dynamic DL-DCH Power Allocation ............................................................................................................ 184

4.9.14 Neighboring Lists ...................................................................................................................................... 186 4.9.14.1.1 Neighbor List Extensions ................................................................................................................................ 188 4.9.14.1.2 Neighbor List Extensions ................................................................................................................................ 188

4.9.14.2 Intra-Frequency Neighboring List ...................................................................................................................... 189 4.9.14.3 Inter-Frequency Neighboring List ...................................................................................................................... 190 4.9.14.4 Inter RAT NeighbouringList .............................................................................................................................. 193 4.9.14.5 GSM NeighborList ............................................................................................................................................. 194 4.9.14.6 Neighbor List in Use........................................................................................................................................... 196

4.10 HOMEZONE NOTIFICATION ................................................................................................................................ 210 4.10.1 HomeZone Value Added Feature .............................................................................................................. 210

4.10.1.1 Scenario 1: Idle Mode Transition Options: ......................................................................................................... 210 4.10.1.1.1 Option 1: Equivalent PLMN ............................................................................................................................ 210 4.10.1.1.2 Option 2: Modified Network Name Using MM-INFORMATION ................................................................. 210

4.10.1.2 Scenario 2: Connected Mode Transition Options ............................................................................................... 211 4.10.1.2.1 Option 1: Handover tones: ............................................................................................................................... 211


v

4.10.1.3 Scenario 3: Idle to Connected Mode Options ..................................................................................................... 211 4.10.1.3.1 Option 1: Tone Insertion – CS initiation: ........................................................................................................ 211 4.10.1.3.2 Option 2: SMS Class 0 – PS Initiation: ........................................................................................................... 211

4.10.2 HomeZone Parameters ............................................................................................................................. 212 4.11 TRANSPORT ....................................................................................................................................................... 215

4.11.1 SCTP ......................................................................................................................................................... 215 4.11.2 Packet Transport ....................................................................................................................................... 220 4.11.3 Tunnelling ................................................................................................................................................. 221 4.11.4 Security ..................................................................................................................................................... 224

4.11.4.1 Security Extensions ............................................................................................................................................ 229 4.11.4.2 Security Extensions ............................................................................................................................................ 230

4.12 REM .................................................................................................................................................................. 231 4.12.1 WCDMA FDD ........................................................................................................................................... 231 4.12.2 GSM .......................................................................................................................................................... 237

4.13 GPS ................................................................................................................................................................... 243 4.14 GEO-COORDINATES ........................................................................................................................................... 246 4.15 FAULT MANAGEMENT ....................................................................................................................................... 248

4.15.1 Supported Alarms...................................................................................................................................... 249 4.15.1.1 Alarm List ........................................................................................................................................................... 250 4.15.1.2 Alarms Object ..................................................................................................................................................... 255

4.15.1.2.1 Further Alarms ................................................................................................................................................ 305 4.15.2 Current Alarms ......................................................................................................................................... 306 4.15.3 History Events ........................................................................................................................................... 308 4.15.4 Expedited Events ....................................................................................................................................... 311 4.15.5 Queued Events .......................................................................................................................................... 313

4.16 PERFORMANCE MANAGEMENT .......................................................................................................................... 317 4.16.1.1 Reference Documents ......................................................................................................................................... 317

4.16.2 Parameters used for Performance Management Reports ......................................................................... 317 4.16.3 Supported Counters .................................................................................................................................. 321

4.16.3.1 HNB Gateway Interface ..................................................................................................................................... 321 4.17 EVENT LOGS ...................................................................................................................................................... 322 4.18 DIAGNOSTICS .................................................................................................................................................... 324 4.19 USER GUI .......................................................................................................................................................... 327

4.19.1 Parameters Controlling the User GUI ...................................................................................................... 328 4.20 QOS ................................................................................................................................................................... 328

4.20.1 Service Mapping ....................................................................................................................................... 328 4.21 BACKHAUL QOS ................................................................................................................................................ 331 4.22 SMALL CELL METRICS ...................................................................................................................................... 332 4.23 VLAN ............................................................................................................................................................... 333 4.24 HOME GATEWAY ............................................................................................................................................... 339

4.24.1 Home Gateway Information ...................................................................................................................... 339 4.24.2 Home Gateway Change Detection ............................................................................................................ 340

4.25 LICENCING ......................................................................................................................................................... 341 4.25.1 Licencing Solution .................................................................................................................................... 341

4.26 UPLINK TRAFFIC SHAPING ................................................................................................................................. 346 4.27 SUPPORT FOR PEER-PEER IPC INTERFACE .......................................................................................................... 347 4.28 ACTIVE SON ..................................................................................................................................................... 349 4.29 IURH GRID OVERRIDE ........................................................................................................................................ 366

5 PROVISIONING PROCEDURES ........................................................................................................................ 369 5.1 HMS ADDRESS FOR: IPSEC OR TLS/SSL .......................................................................................................... 369 5.2 PROCEDURES LEADING TO HNB PROVIDING SERVICE ...................................................................................... 369

5.2.1.1 Typical Duration of Start-Up Times ....................................................................................................................... 371 5.2.1.2 Administrative and Operational States .................................................................................................................... 371

5.2.2 CloudBase System: Activation .................................................................................................................. 372 5.2.3 Initial Provisioning ................................................................................................................................... 372

5.2.3.1.1 Parameters to be configured by the HMS .......................................................................................................... 374 5.2.4 Full Provisioning ...................................................................................................................................... 376

5.2.4.1 Re-provisioning Following HNB Reboot ................................................................................................................ 378 5.2.5 HNB Registration ...................................................................................................................................... 380

5.2.5.1 HNB Registration Reject ........................................................................................................................................ 381 5.2.6 HNB Deregistration .................................................................................................................................. 381

Iuh Parameter Guidelines for R3.7 ▄ UBS-44-57-004 vi

5.2.6.1 HNB-GW Initiated HNB Deregistration ................................................................................................................. 381 5.2.6.2 HNB Initiated Deregistration .................................................................................................................................. 382

5.2.6.2.1 HNB Deregistration due to internal event ......................................................................................................... 382 5.2.6.2.2 HNB Deregistration triggered by HMS ............................................................................................................. 383

6 RRM ......................................................................................................................................................................... 385 6.1 INITIAL RRM ..................................................................................................................................................... 385 6.2 SUBSEQUENT RRM ........................................................................................................................................... 387

7 HANDOVERS ......................................................................................................................................................... 389 7.1 HANDOUT .......................................................................................................................................................... 389

7.1.1 RCSP Based Handover ............................................................................................................................. 390

8 LOCATION VERIFICATION .............................................................................................................................. 391 8.1 HNB LOCATION CHANGE DETECTION BASED ON CHANGES OF NEIGHBOURING CELLS .................................... 391

8.1.1 Algorithm Details ...................................................................................................................................... 392 8.2 HNB LOCATION CHANGE DETECTION BASED ON DETECTION OF NEIGHBOUR’S PLMNS ................................. 392

9 REVISION HISTORY ........................................................................................................................................... 394

▀ References


7 UBS-44-57-004

1 References 1.1 Standards

• [TR069] BroadBand Forum “TR-069 CPE WAN Management Protocol v1.1”, Technical Report, Issue 1, Amendment 4, Sept. 2005

• [TR098] BroadBand Forum “TR-098 Internet Gateway Device Data Model for TR-069”, Technical Report, Issue 1, Amendment 1, Sept. 2005

• [TR106] BroadBand Forum “TR-106 Data Model Template for TR-069-Enabled Devices”, Technical Report, Issue 1, Amendment 2, Nov. 2008

• [TR196] BroadBand Forum “TR-196 Femto Access Point Service Data Model”, Technical Report, Issue 1, Apr. 2009

• [TR21.905] 3GPP TR 21.905, "Vocabulary for 3GPP Specifications", Version 8.7.0

• [TS32.330] 3GPP TS 33.320, “Security of Home Node B (HNB) / Home evolved Node B (HeNB)”, Version 9.0.0

1.2 Document References • [UBS-44-41-002] “Configuration Data and Software Management”, USC-44-41-002

• [UBS-21-23-326] “CSCO HMS FAP Database Specification (Auto Generated)”, UBS-21-23-326

▀ Definitions and Abbreviations

Iuh Parameter Guidelines for R3.7 ▄ UBS-44-57-004 8

2 Definitions and Abbreviations For common terminology refer to [TR21.905]

APN Access Point Name

DLMM Down Link Monitor Mode

LIPA Local IP Access

SIPTO Selected IP Traffic Offload

USC Cisco Universal Small Cell (also referred to as FAP/HNB throughout this document)

▀ Operation and Maintanance: TR-069 Protocol


9 UBS-44-57-004

3 Operation and Maintanance: TR-069 Protocol 3.1 Introduction The Operation And Maintenance (OAM) system comprises of one or more HNB Management Servers (HMS) under control of the operator. These servers configure the HNBs for operation according to the network specific planning. The interface between HMS and HNB is based upon the TR-069 suite of protocols and specifications. The TR-069 suite is a generic interface designed for remote configuration of generic home appliances from a system OAM centre. The suite is extended to be specific to femtocell devices by adding the TR-196 data model definition on top of the generic data model defined in TR-098.

While TR-196 provides the majority of data model parameters needed by a femtocell with standard functionality, the parameter set does not cover more advanced features provided by the Cisco femtocell. Cisco and Partner Integrators have extended the data model further with proprietary parameters to allow support of these features. Proprietary extensions are to be kept to a minimum in order to maintain interoperability. The proprietary extensions shall be identifiable by the parameter/node names conforming to TR-106, section 3.3 (i.e. the string “X_OUI_COM_” is prepended to the name, where OUI can be “UBIQUISYS” or the name of the system integrator).

3.2 Parameters Access and Property The parameters described in this document can be used by the HMS to configure or monitor the HNB by employing standard TR-069 Remote Procedure Calls (RPC). Each parameter can be one of the following access methods from the HMS are used:

• RMS Access: READ/WRITE: These parameters can be set by the HMS. Otherwise the default value is used.

• RMS Access: READ: Parameters cannot be set by the HMS.

• RMS Access: WRITE: Parameters which can be set but are not readable from HMS, such as passwords or parameters triggering actions on the HNB.

The default value of each parameter used by the HNB can be:

• Default value: the default value hardcoded in the software; these can be modified by the HMS if the parameter has a write access.

• Value modified via activation server: the HNB will employ the value set by the activation server during factory provisioning. For example: product class, hardware model, URL of Operator servers.

• Value set at runtime: the HNB sets the parameters value during normal operation. For example, radio measurements or neighbour lists

The organisation of file system where the parameters are stored and the various data categories are described in [UBS-44-41-02].

An additional item defined as RMS Property defines the parameter name as seen on the RMS.

3.3 Management Level Each parameter is associated with a consideration of the Operator “management level” of the parameter - Solution: The parameter is set depending on the end-to-end use case and functionality requirements. - Customer: The parameter setting depends on Operator network and/or requirements. - Deployment: The parameter must be set and tuned depending on the deployment and/or use case of the device (e.g. Residential or Enterprise) - Deployment specific: The current RMS or FAP default value is recommended by Cisco, although it may require further optimization as per Operator's requirement. The RMS default value always takes precedence on the FAP default value. - Default: The parameter is left to Operator modification if deemed necessary. The RMS default value always takes precedence on the FAP default value.



- System: The parameter has been fine-tuned to deliver functions, services and/or performance. It shall not be modified by the Operator without appropriate checks and agreement with Cisco. - N/A: The parameter shall not / cannot be modified

3.4 Support of TR-069 The HNB supports the specification defined in TR-069 “CPE WAN Management Protocol”, Issue 1, Amendment 4, 2006.

RPC Methods supported and called by the HNB:

HNB Method name TR-069

requirement SetParameterValues Required GetParameterValues Required SetParameterAttributes Required AddObject Required DeleteObject Required Reboot Required Download Required FactoryReset Optional GetParameterNames Required GetRPCMethods Required

Table 1: methods supported by HNB

HMS Method name TR-069

requirements TransferComplete Required Inform Required

Table 2: methods called by HNB

3.4.1 Parameters Requiring Reboot A number of parameters require that the HNB reboots, in order for the software to apply their value. Those parameters requiring reboot are marked in the description of each parameter. It should be noted that the HNB will reboot as soon as the TR069 session terminated, withouth HMS intervention. as required by the TR069 protocol.

These parameter will trigger a reboot even if the value written by the HMS is the same as the value stored in memory

The reboot behaviour can be modfified by the parameter InternetGatewayDevice.Services.FAPService.1.FAPControl. X_UBIQUISYS_COM_RebootLock (in Section 4.7); which, when set, will prevent the HNB from rebooting until the HMS clears the parameter.

3.4.1.1 List of Parameters Requiring Reboot

Object List of parameter requiring reboot when included within a SetParameterValue RPC

InternetGatewayDevice.DeviceInfo ProvisioningCode InternetGatewayDevice.ManagementServer URL ConnectionRequestURL



11 UBS-44-57-004


InternetGatewayDevice.Time NTPServer1 NTPServer2 NTPServer3 InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.SelfConfig UARFCNSelfConfigEnable LACRACURASelfConfigEnable InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.Gateway SecGWServer1 SecGWServer2 FAPGWServer1 FAPGWPort SourcePortForFAPGWConnection X_UBIQUISYS_COM_Partner InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP X_UBIQUISYS_COM_CbsLevel1Scheduling X_UBIQUISYS_COM_CbsLevel2Scheduling InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_IntraFreqMeas1 MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_InterFreqMeas1 MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas X_UBIQUISYS_COM_MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_InterRATMeas1 MeasurementQuantity InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF UARFCNDL UARFCNDLToProtect X_UBIQUISYS_COM_UARFCNDLNormalCarriers PrimaryScramblingCode InternetGatewayDevice.Services.FAPService.1.Transport.Security X_UBIQUISYS_COM_TransmitFragmentMode InternetGatewayDevice.Services.FAPService.1.Transport.Security.CryptoProfile IKERekeyLifetime




IPsecRekeyLifetimeTime InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD REMBandList InternetGatewayDevice.Services.FAPService.1.REM.GSM REMBandList InternetGatewayDevice.Services.FAPService.1.GPS

X_UBIQUISYS_COM_FemtoPlusEmulation (only used for Development purposes)

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Diagnostics FactoryRecovery InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_PartnerQoS.ServiceMapping Conversational StreamingPS InteractivePS_Priority1 InteractivePS_Priority2 InteractivePS_Priority3 BackgroundPS Signalling OAMP IPT InteractivePSPriorityTHPIMSSignalling

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON ActiveSONReset InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.ProvisioningInfo EnterpriseID GroupID GroupSiteID

Table 3: Parameters requiring reboot following SetParameterValue from HMS

3.5 Deviations from TR196 Parameters The following table shows the deviation of parameter usage betweem the TR196 standard and the usage of the same parameters in the HMS.

Object Parameter Differences betwewen usage in the HNB and TR196 standard

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellSelection



13 UBS-44-57-004


QqualMinOffset

RMS Access: Read/Write Range defined in TR196: 1:16 Range used in HNB: 0:16 --- Remarks: Value of 0 is allowed for Ubiquisys HNBs. If used, this IE is omitted from SIB3

DeltaQRxLevMin

RMS Access: Read/Write Range defined in TR196: {-4, -2} Range used in HNB: {-4, -2, 0} --- Remarks: Value of 0 is allowed for Ubiquisys HNB. If used, this IE is omitted from SIB3

QRxLevMinOffset

RMS Access: Read/Write Range defined in TR196: {2,4,6,8,10,12,14,16} Range used in HNB: {0.2,4,6,8,10,12,14,16} --- Remarks: Value of 0 is allowed for Ubiquisys FAPs. If used, this IE is omitted from SIB3

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellSelection

MaxFAPTxPowerInUse

RMS Access: Read/Write Range defined in TR196: 0:200 Range used in HNB: -400:300 --- Remarks: Actual values of the maximum transmission power are -40.0dBm to 30.0 dBm in steps of 0.1 dB. The value of MaxFAPTxPowerInUse divided by 10 yields the actual value of the maximum transmission power.

PCPICHPowerInUse

RMS Access: Read Range defined in TR196: -100:200 Range used in HNB: -500:200 --- Remarks: Actual values of the maximum transmission power are -50.0 dBm to 20.0 dBm in steps of 0.1 dB. The value of PCPICHPowerInUse divided by 10 yields the actual value of the maximum transmission power.

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP

NumOfHSPDSCHs

RMS Access: Read/Write Range defined in TR196: 0:15 Range used in HNB: 0:14 --- Remarks: Only 14 HSPDSCH channels are supported




NumOfHSSCCHs

RMS Access: Read/Write Range defined in TR196: as defined in “3GPP-TS.32.642 Section 6.3.9” Range used in HNB: 2:2 --- Remarks: Note: the HNB restricts the range to single default value

InternetGatewayDevice.Services.FAPService.1.Transport.Security.CryptoProfile

MaxChildSA

RMS Access: Read/Write Range defined in TR196: {2,4,6,8,10} Range used in HNB: {2} --- Remarks: Only one tunnel is supported

InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt

PeriodicUploadInterval

RMS Access: Read/Write Range defined in TR196: 1: 4294967295 Range used in HNB: 1800: 4294967295 --- Remarks: The minimum upload interval is of 900sec

InternetGatewayDevice.Services.FAPService.1.Capabilities.UMTS

MaxHSSCCHsSupported

RMS Access: Read Range defined in TR196: 3GPP-TS.32.642 Section 6.3.9 Range used in HNB: {0:2}

InternetGatewayDevice.Services.FAPService.1.AccessMgmt

AccessControlList

RMS Access: Read/Write Range defined in TR196: 0:1024 Range used in HNB: 0:4000 --- Remarks: The list was extended up to 4000 entries

▀ Core Network Parameters


15 UBS-44-57-004

4 Core Network Parameters The HNB employs the data model specified for “TR-069 capable devices”, which is specified in [TR098], [TR106] and [TR196]. These specifications provide guidelines on the data hierarchy to be used by the data model.

In [TR106], it is specified how the data model can be extended by vendor-specific parameters (or objects); a vendor string (e.g. “X_UBIQUISYS_COM_”) is appended in front of the name of the element.

The top-most data model elements supported by the Cisco's HNB are shown in the figure below. The following subsections describe the parameters and features supported by these objects.

Figure 1: Root container of data model

Description of the elements in these objects is to be found in the following sections:

1. InternetGatewayDevice (root object): see section 4.1

2. InternetGatewayDevice.DeviceInfo: see section 4.2

3. InternetGatewayDevice.Time: see section Error! Reference source not found. 4. InternetGatewayDevice.ManagementServer: see section 4.4

5. InternetGatewayDevice.LANConfigSecurity: see section 4.19.1

6. InternetGatewayDevice.WANDevice: see section 4.5

7. InternetGatewayDevice.Services.FAPService: see section 0

8. InternetGatewayDevice.X_UBIQUISYS_COM_GatewayInfo: see section 4.24.1



4.1 The Root Object: InternetGatewayDevice The InternetGatewayDevice provides the root object of the data model; any supported object or parameters shall use this as its root object.

Object Parameter Description

InternetGatewayDevice The top-level object for an Internet Gateway Device.

DeviceSummary

As defined in TR-106 --- RMS Access: READ Type: String. (Length: 0 to 1024 characters). Notification: Forced FAP Default value: "InternetGatewayDevice:1.4[](Baseline:2,Time:2),FAPService:1.0[1](Baseline:1,LocalIPAccess:1,REMGSM:1,IPSecTunnel:1,UMTSSelfConfig:1,UMTSSelfConfigNLInUseIntraFreqCell:1,UMTSSelfConfigNLInUseInterFreqCell:1,UMTSSelfConfigNLInUseInterRATCell:1,UMTSSelfConfigNLIntraFreqCell:1,UMTSSelfConfigNLInterFreqCell:1,UMTSSelfConfigNLInterRATCell:1,FaultMgmtSupportedAlarms:1,FaultMgmtActive:1,FaultMgmtHistory:1,FaultMgmtExpedited:1,FaultMgmtQueued:1,PerfMgmt:1)" RMS Default value: N/A RMS Property:N/A Management level: N/A

LANDeviceNumberOfEntries

Number of instances of LANDevice. Ubiquisys HNB does not use this object --- RMS Access: READ Type: Integer. (Range: 0 to 0). Notification: None FAP Default value: 0 RMS Default value: N/A Management level: N/A

WANDeviceNumberOfEntries

Number of instances of WANDevice. --- RMS Access: READ Type: Integer. (Range: 1 to 1). Notification: None FAP Default value: 1 RMS Default value: N/A Management level: N/A

Table 4: Parameters for HNB’s root object: InternetGatewayDevice.

Note that the HNB will not support any LAN devices (the number of entries is zero); but will support a single instance of WAN devices (the number of entries is set to 1).

4.1.1 Device Summary The Device Summary a list that includes the Root Object followed by all Service Object instances (or support for a Service Object type if no instances are currently present), it is defined in [TR106]. For each of these objects, the DeviceSummary specifies the version of the object, the associated instance number used to identify the specific object instance, and a list of the supported profiles for that object. In release 3.x of the HNB, the following instances are used:



17 UBS-44-57-004

Root object Profile

Name Version [Instance] Name Version

InternetGatewayDevice 1.4[] Baseline 2 Time 2 FAPService 1.0[1] Baseline 1 LocalIPAccess 1 REMGSM 1 IPSecTunnel 1 UMTSSelfConfig 1 UMTSSelfConfigNLInUseIntraFreqCell 1 UMTSSelfConfigNLInUseInterFreqCell 1 UMTSSelfConfigNLInUseInterRATCell 1 UMTSSelfConfigNLIntraFreqCell 1 UMTSSelfConfigNLInterFreqCell 1 UMTSSelfConfigNLInterRATCell 1 FaultMgmtSupportedAlarms 1 FaultMgmtActive 1 FaultMgmtHistory 1 FaultMgmtExpedited 1 FaultMgmtQueued 1 PerfMgmt 1

Table 5: Profiles used in InternetGatewayDevice.DeviceSummary

4.2 Device Information The object “DeviceInfo” includes those parameters which can be used to identify the device manufacturer, type, hardware and software.


InternetGatewayDevice.DeviceInfo This object contains general device information.

Manufacturer

The manufacturer of the HNB (human readable string). --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Ubiquisys" RMS Default value: N/A RMS Property:N/A Management level: N/A

ManufacturerOUI

Organizationally unique identifier of the device manufacturer. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros. The value MUST be a valid OUI as defined in http://standards.ieee.org/faqs/OUI.html This value MUST remain fixed over the lifetime of the device, including across firmware updates. --- RMS Access: READ Type: String. (Length: 6 characters). Notification: None FAP Default value: "001B67" RMS Default value: N/A RMS Property:N/A Management level: N/A




ModelName

Model name of the HNB (human readable string). --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "ZoneGate Access Point" RMS Default value: N/A RMS Property:N/A Management level: N/A

Description

A full description of the HNB device (human readable string). --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "Provides local cellular service via ethernet connection to residential gateway router" RMS Default value: N/A RMS Property:N/A Management level: N/A

ProductClass

Identifier of the class of product for which the serial number applies. That is, for a given manufacturer, this parameter is used to identify the product or class of product over which the SerialNumber parameter is unique. This value MUST remain fixed over the lifetime of the device, including across firmware updates. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value: "ZM-000-05" RMS Default value: N/A RMS Property:N/A Management level: N/A

SerialNumber

Serial number of the HNB. This value MUST remain fixed over the lifetime of the device, including across firmware updates. For Ubiquisys femtocells this contains the IMEI of the unit --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value: N/A RMS Property:N/A Management level: N/A

HardwareVersion

A string identifying the particular HNB model and version. For Ubiquisys femtocells this contains the PCB version (e.g. G2.1.3) --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: Forced Parameter modified via activation server. FAP Default value "" RMS Default value: N/A RMS Property:N/A Management level: N/A



19 UBS-44-57-004


SoftwareVersion

A string identifying the software version currently installed in the HNB. To allow version comparisons, this element SHOULD be in the form of dot-delimited integers, where each successive integer represents a more minor category of variation. For example, 3.0.21 where the components mean: Major.Minor.Build. For Ubiquisys femtocells the version is prefixed with 'AV' or 'BV' --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: Forced FAP Default value: "" RMS Default value: N/A RMS Property:N/A Management level: N/A

ModemFirmwareVersion

A string identifying the version of the modem firmware currently installed in the HNB. This is applicable only when the modem firmware is separable from the overall HNB software. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime RMS Default value: N/A RMS Property:N/A Management level: N/A

ProvisioningCode

Identifier of the primary service provider and other provisioning information, which MAY be used by the Server to determine service provider-specific customization and provisioning parameters. If non-empty, this argument SHOULD be in the form of a hierarchical descriptor with one or more nodes specified. Each node in the hierarchy is represented as a 4-character sub-string, containing only numerals or upper-case letters. If there is more than one node indicated, each node is separated by a "." (dot). Examples: "TLCO" or "TLCO.GRP2". --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: Forced FAP Default value: "" RMS Default value: N/A RMS Property:N/A Management level: System

AdditionalHardwareVersion

A comma separated list of any additional versions. Represents any additional hardware version information the vendor may wish to supply. For Ubiquisys femtocells this contains the PCB tracking number --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value: N/A RMS Property:N/A



Object Parameter Description Management level: N/A

SpecVersion

Represents the version of the specification implemented by the device. Currently 1.0 is the only available version. The value of this parameter MUST equal "1.0". This parameter is DEPRECATED because its value is fixed and it therefore serves no purpose. However, it is a Forced Inform parameter and therefore cannot be OBSOLETED. --- RMS Access: READ Type: String. (Length: 0 to 16 characters). Notification: Forced FAP Default value: "1.0" RMS Default value: N/A RMS Property:N/A Management level: N/A

UpTime

Time in seconds since the HNB was last restarted. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value :0 RMS Default value: N/A RMS Property:N/A Management level: N/A

FirstUseDate

Date and time in UTC that the HNB first both successfully established an IP-layer network connection and acquired an absolute time reference using NTP or equivalent over that network connection. The HNB MAY reset this date after a factory reset. If NTP or equivalent is not available, this parameter, if present, SHOULD be set to the Unknown Time value. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value: N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_ChassisSN

Chassis Serial number at which the 3G module is located. This value MUST remain fixed over the lifetime of the device, including across firmware updates. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: Forced Parameter modified via activation server. FAP Default value "" RMS Default value: N/A RMS Property:N/A Management level: N/A

Table 6: Parameters in InternetGatewayDevice.DeviceInfo



21 UBS-44-57-004

4.3 Time, IP-Timing and Frequency Discipline The HNB acquires data and time information from time servers via the NTP protocol, in order to:

• Report its own local time, alarms, KPI counters, logs and events with the appropriate timestamp

• Verify digital certificates validity

• Employ packet network synchronisation for disciplining the frequency of the RF reference oscillator (IP Timing)

The three categories of NTP servers and how the HNB accesses them are shown in the diagram below.

Figure 1: NTP Architecture



NTP Server Category Use by HNB Parameters configuring NTP Servers

Public NTP server

Date/time for initial verification of digital certificates

Only accessed once prior to IPsec tunnel establishment.

Up to 3 servers:

.Time.NTPServer1

.Time.NTPServer2

.Time.NTPServer3

Operator NTP server

Date/time secure verification of digital certificates.

Accessed immediately after IPsec tunnel is established, periodically thereafter to maintain secure date/time

Up to 2 servers:

.Time.X_UBIQUISYS_COM_OperatorNTPServer1

.Time.X_UBIQUISYS_COM_OperatorNTPServer2

IP Timing server

IP timing source for RF frequency discipline.

Periodic polling.

Up to 4 highly stable servers:

.X_UBIQUISYS_COM_IPTiming.TimingServerInstance.{1}.ServerIP




It should be noted that the

• Operator NTP Servers are not mandatory to be set via Activation servers

• Operator NTP Servers are not used before to connect to the HMS

The following object contains parameters relating to configuration of NTP servers on the HNB


InternetGatewayDevice.Time This object contains parameters relating an NTP or SNTP time client in the CPE. Support for this object is Optional.

Status

Status of Time support on the HNB. Enumeration of: - "Disabled" - "Unsynchronized" - "Synchronized" - "Error_FailedToSynchronize" - "Error" (OPTIONAL) The "Unsynchronized" value indicates that the HNB's absolute time has not yet been set. The "Synchronized" value indicates that the HNB has acquired accurate absolute time; its current time is accurate. The "Error_FailedToSynchronize" value indicates that the HNB failed to acquire accurate absolute time; its current time is not accurate. The "Error" value MAY be used by the HNB to indicate a locally defined error condition. --- RMS Access: READ Type: Enumeration (0 to 4) Notification: None FAP Default value: “Unsynchronized” RMS Default value:N/A RMS Property:N/A Management level: N/A



23 UBS-44-57-004


NTPServer1

First public NTP timeserver. Either a host name or IP address. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value: "0.pool.ntp.org" RMS Default Value: Requires Operator Input RMS Property : FC-NTP-SERVER-1 Management level: Solution or Customer

NTPServer2

Second public NTP timeserver. Either a host name or IP address. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value: "1.pool.ntp.org" RMS Default Value: Requires Operator Input RMS Property : FC-NTP-SERVER-2 Management level: Solution or Customer

NTPServer3

Third public NTP timeserver. Either a host name or IP address. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value: "2.pool.ntp.org" RMS Default Value: Requires Operator Input RMS Property : FC-NTP-SERVER-3 Management level: Solution or Customer

CurrentLocalTime

The current date and time in the HNB's local time zone. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value :0 RMS Default value:N/A Management level:N/A

X_UBIQUISYS_COM_NTPServerStatus

Status of configured Time Servers. Enumeration of: - "Unknown": unknown server - "Fail": NTP server not responding - "Public": public (un-secured NTP server) - "Secure": secure NTP server --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value :”unknown” RMS Default value:N/A RMS Property:N/A Management level:N/A

X_UBIQUISYS_COM_OperatorNTPServer1

First operator NTP timeserver. Either a host name or IP address. A change to this param is picked up at the next PollPeriod (provided it is non-zero), otherwise a manual reboot is required --- RMS Access: READ/WRITE



Object Parameter Description Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default Value: Requires Operator Input RMS Property : OPERATOR-NTP-SERVER-1 Management level:Customer

X_UBIQUISYS_COM_OperatorNTPServer2

Second operator NTP timeserver. Either a host name or IP address. A change to this param is picked up at the next PollPeriod (provided it is non-zero), otherwise a manual reboot is required --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default Value: Requires Operator Input RMS Property : OPERATOR-NTP-SERVER-2 Management level:Customer

X_UBIQUISYS_COM_PollPeriod

Time in minutes between NTP time re-validations. If set to zero then the time is never re-validated after boot-up --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 2880). Notification: None FAP Default value: 2880 RMS Default value:2880 RMS Property : POLL-PERIOD-TIME Management level:Solution

X_UBIQUISYS_COM_OperatorServerBehaviour

The X_UBIQUISYS_COM_OperatorNTPServer1/2 params are a mandatoty configuration item to approve as part of the operator data. The operator choice to specify empty strings for both these params shall be used by the FAP to implicilty determine that the FAP shall continue to proceed with service without connecting to an operator NTP server. This param, X_UBIQUISYS_COM_OperatorServerBehaviour is therefore only used when the OperatorNTPServer1/2 strings ARE populated, to refine the behaviour as per the enumeration:- InhibitOnServerInitiallyUnreachable - (default) Suppress FAP service if no contact to Operator NTP Servers achieved when IPSec tunnel established. FAP Service may be subsequently provided if contact with Operator NTP server is successful following re-validation (occuring at intervals specified in minutes by InternetGatewayDevice.Time.X_UBIQUISYS_COM_PollPeriod) InhibitOnServerUnreachable -Suppress FAP service if no contact to Operator NTP Servers achieved when IPSec tunnel established. No attempt made to re-establish service, even if contact with Operator NTP server is successful NeverInhibitService - continue to provide FAP service, using timing from macro and/or public NTP servers even if contact with Operator NTP servers is not possible --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "InhibitOnServerInitiallyUnreachable" RMS Default value: "InhibitOnServerInitiallyUnreachable" RMS Property : OPERATOR-SERVER-BEHAVIOUR Management level: Solution or Customer

Table 7 configuration of NTP servers



25 UBS-44-57-004

4.3.1 Validity of Digital Certificates

Prior connecting to a SeGW, the HNB employs the timestamp from a “Public NTP Server” in order to verify the validity of the digital certificate of the SeGW.

Following the successful connection to a SeGW, the HNB attempts to verify the SeGW certificate with the timestamp from a secure “Operator NTP Server”:

• If the “Operator NTP Servers” are reachable and provide a timestamp:

o If the validity of the digital certificates provided by the SeGW is verified, the HNB will proceed with its configuration by contacting the HMS.

o If the validity of the digital certificate has expired, the connection to the SeGW is closed.

• If the “Operator NTP Servers” are set in the database but not reachable, the HNB behaviour is decided by the parameter .Time.X_UBIQUISYS_COM_OperatorServerBehaviour:

o InhibitOnServerInitiallyUnreachable: The HNB will not provide any WCDMA service until an “Operator NTP Servers” becomes available and the certificate verified. The HNB will retry to contact the servers at intervals specified by the parameter .Time.X_UBIQUISYS_COM_PollPeriod.

o InhibitOnServerUnreachable: The HNB will not provide any WCDMA service. No attempt is made to contact again the “Operator NTP Server”. The HNB will require a power cycle.

o NeverInhibitService: The HNB will proceed with configuration and activation even if it could not verify the digital certificate of the SeGW because none of the configured “Operator NTP server” was reachable.

As required by [TS32.330], the most recent sevure timestamps obtained from the “Operator NTP Servers” is periodically stored and signed in the database and upon subsequent rebbot this last secure timestamp is used as initial current time until next NTP update. The frequency is set by the parameter .Time.X_UBIQUISYS_COM_PollPeriod.

As an indication to the Operator of the date and time source, the .Time.X_UBIQUISYS_COM_NTPServerStatus parameter provides such information upon HMS query. The different responses mean:

• 0 = Unknown time state (NTP software not running)

• 1 = Both public and private NTP server communication failed

• 2 = Public NTP time is set

• 3 = Private/secure (over IPsec tunnel) NTP time is set (takes precedence over Public NTP time is set)

The typical operational sequence of how the HNB access NTP servers and updates the status parameter are shown in the figure below.



Figure 2: NTP server address configuration and Operations Flow

4.3.2 Frequency Discipline

The HNB meets [TS-25.104] the “local area NodeB” frequency requirement of +/- 0.1ppm with the following methods:

• Network Listen Mode: disciplines the frequncy against the signal from a 3G or 2G neighbouring cells at start-up

• Fast Sniff Mode: disciplines the frequency against the signal from 3G and 2G neighbouring cells, periodically

• IP Timing: disciplines the frequncy using a packet network time synchronisation protocol (NTP)

During Network Listen Mode and Fast Sniff Mode, the HNB disciplines its frequency to the configured downlink frequencies of the macro network and extract the frequency offset from neighbouring NodeBs.

In IP Timing Mode, the HNB discipline its frequency from highly stable Stratum 1 servers running NTP version 4 on the IP network. Up to 4 NTP Servers can be configured on the HNB.

The HNB disciplines its frequency from the following synchronisation sources (ordered by priority):

1. home PLMN 3G,

2. other PLMN 3G (if any configured)

3. 2G (home PLMN only)

4. Timing.

This frequency source used for synchronisation is reported to the HMS via the parameter .X_UBIQUISYS_COM_IPTiming.TimingReferenceSource.

Other parameters in the data model concerning IP Timing are:



27 UBS-44-57-004

• If all frequency discipline mechanisms are unavailable (i.e. no macro coverage and IP Timing servers unavailable) the oscillator’s frequency will slowly drift outside minimum requirements for UEs to be able to detect the femtocell carrier. It is expected that once synchronise, an undisciplined oscillator will maintain sufficient accuracy for up to 3-4 weeks. The parameter .X_UBIQUISYS_COM_IPTiming.PoorResolutionBehaviour controls the femtocell behaviour in case of loss of frequency discipline, the femtocell can be either be configured to turn off the transmitter (thus not providing 3GPP services) or provide service with a frequency outside specification (which some UE seems to cope anyway).

o It should be noted that the HNB will raise an alarm when the oscillator is not disciplined (see alarm “No Timing Source”).

• : When set, IP Timing is disabled when suitable synchronisation candidates are available for Fast Sniff. This can be used in order to reduce backhaul bandwidth requirements.

NOTE: .X_UBIQUISYS_COM_IPTiming.DisableIPTWhenInMacroCoverage parameter would always be set to TRUE which means that IPT will be disabled when the FAP is in MACRO coverage (2G or 3G coverage) to save the backhaul load

• “Fast Sniff Mode” is used to discipline the oscillator’s frequency every 100seconds based on the signal received from neighbouring macrocells. However, as the Fast Sniff procedure requires the transmitter to be switched off for a short period, the procedure is postponed if any traffic or signalling bearer is assigned to a call. In order to maintain frequency accuracy, the HNB will discipline its frequency via IP Timing after a period defined by the parameter IPTHandOffTimer (within the object .FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile). Note that:

o This behaviour will ignore the setting of the parameter .X_UBIQUISYS_COM_IPTiming.DisableIPTWhenInMacroCoverage, described above.

o IP Timining Servers needs to be configured and reachable

o In order to cope with a variety of oscillator devices, convergence time of the IP Timing algorithm and network jitter, it is recommended that the value of this parameter is set to 1 hour.

4.3.2.1 Parameters Related to IP Timing

The objects and parameters listed in the table below are used to monitor and configure IP Timing.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_IPTiming

Object name

TimingServerInstanceNumberOfEntries

Length of IP Timing list (for information only) --- RMS Access: READ Type: Integer. (Range: 0 to 4). Notification: None FAP Default value: 0 RMS Default value : N/A RMS Property:N/A Management level: N/A

PredictedResolution

Predicted resolution of frequency error: - "Greater than 250ppb" - "Between 250ppb and 100ppb" - "Less than 100ppb" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Greater than 250ppb" RMS Default value : N/A RMS Property:N/A Management level: N/A

TimingReferenceSource Source of the AP timing reference:



Object Parameter Description - "unsynchronised" - "IP timing" - "Operator 3G macro" - "Other 3G macro" - "2G macro" - "GPS" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "unsynchronised" RMS Default value : N/A RMS Property:N/A Management level: N/A

PoorResolutionBehaviour

Action to take if the predicted resolution exceeds 250ppb: - "Continue with service" - "Inhibit service" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Continue with service" RMS Default value : N/A RMS Property:N/A Management level: System

GpsRrmPreference

Defines relative priority of GPS and macro timing. Both are always higher priority than IP timing. 0 - Prefer GPS over macro timing 1 - Prefer macro timing over GPS 2- Treat GPS and macro timing equally --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Prefer macro timing over GPS" RMS Default value : "Prefer macro timing over GPS" RMS Property: FC-GPS-RRM-PREFERENCE Management level: N/A

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_IPTiming.TimingServerInstance List of IPTiming specific information

ServerIP

IP address or FQDN of timing server --- RMS Access: READ Type: String. (Length: 7 to 255 characters). Notification: None FAP Default value: "0.0.0.0" RMS Default value : "0.0.0.0" RMS Property: IP-TIMING-SERVER-IP IP-TIMING-SERVER-IP-1 IP-TIMING-SERVER-IP-2 Management level: Customer

Table 8 Parameters Related IP Timing

4.3.3 Time and Timezones Time and date are assumed to be relative to UTC (Coordinated Universal Time); note that, in this context, UTC can be considered equivalent to GMT (Greenwich Mean Time).

In order to provide local time for all time-stamped information, a local timezone parameter can be configured from the HMS. The timezone parameter is a time offset from UTC which is applied to the timestamp.



29 UBS-44-57-004

The standard data model provides a parameter (InternetGatewayDevice.Time.LocalTimeZoneName), configured by the HMS, which can be used to give a name the specific timezone.

Local time is used in the following procedures:

• The parameter InternetGatewayDevice.Time.CurrentLocalTime

• Timestamp of Current Alarm

• Timestamp of Alarm History entries

• Timestamp of Event Log entries

• Timestamp used in the filenames for Performance Monitoring files

• Timestamps used for Performance Monitoring measurement

• Start/End of Performance Monitoring reporting cycles

• Calculation of the Least Busy Hour

4.3.3.1 Timezone Parameters The following parameters shall be used for time stamping Event logs:


InternetGatewayDevice.Time This object contains parameters relating an NTP or SNTP time client in the CPE. Support for this object is Optional.

LocalTimeZoneName

Name of the local time zone. This must be a POSIX compliant string e.g. "EST+5EDT,M4.1.0/2,M10.5.0/2". --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Property : LOCAL-TIME-ZONE-NAME

Table 9 Timezone Parameters

4.4 Configuration of Management Server Configuration of the Management Server (the HMS) is configured in the following object.


InternetGatewayDevice.ManagementServer This object contains parameters relating to the HNB's association with an HMS.

URL

URL for the CPE to connect to the ACS using the CPE WAN Management Protocol. This parameter MUST be in the form of a valid HTTP or HTTPS URL. The "host" portion of this URL is used by the CPE for validating the ACS certificate when using SSL or TLS. Note that on a factory reset of the CPE, the value of this parameter might be reset to its factory value. If an ACS modifies the value of this parameter, it SHOULD be prepared to accommodate the situation that the original value is restored as the result of a factory reset. Initially set by FAP based on factory configuration data, but may be overridden by HMS --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value: Input CloudBase



Object Parameter Description RMS Property:Input CloudBase Management level: Customer

PeriodicInformEnable

Whether or not the CPE MUST periodically send CPE information to Server using the Inform method call. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: 1 RMS Default value: TRUE RMS Property:N/A Management level: N/A

PeriodicInformInterval

The duration in seconds of the interval for which the CPE MUST attempt to connect with the ACS and call the Inform method if PeriodicInformEnable is true. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 4294967295). Notification: None FAP Default value: 86400 RMS Default value: 86400/600 RMS Property: FC-PERIODIC-INFORM-INTERVAL Management level: Solution

PeriodicInformTime

An absolute time reference in UTC to determine when the HNB will initiate the periodic Inform method calls. Each Inform call MUST occur at this reference time plus or minus an integer multiple of the PeriodicInformInterval. PeriodicInformTime is used only to set the "phase" of the periodic Informs. The actual value of PeriodicInformTime can be arbitrarily far into the past or future. For example, if PeriodicInformInterval is 86400 (a day) and if PeriodicInformTime is set to UTC midnight on some day (in the past, present, or future) then periodic Informs will occur every day at UTC midnight. These MUST begin on the very next midnight, even if PeriodicInformTime refers to a day in the future. The Unknown Time value defined in TR-098 section 2.2 indicates that no particular time reference is specified. That is, the HNB MAY locally choose the time reference, and needs only to adhere to the specified PeriodicInformInterval. If absolute time is not available to the HNB, its periodic Inform behavior MUST be the same as if the PeriodicInformTime parameter was set to the Unknown Time value. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value: 2006-01-27T01:00:00Z + Random 10 or 1440 m RMS Property:N/A Management level: N/A

ParameterKey

ParameterKey provides the HMS a reliable and extensible means to track changes made by the HMS. The value of ParameterKey MUST be equal to the value of the ParameterKey argument from the most recent successful SetParameterValues, AddObject, or DeleteObject method call from the HMS. The HMS MUST set ParameterKey to the value specified in the corresponding method arguments if and only if the method completes successfully and no fault response is generated. If a method call does



31 UBS-44-57-004

Object Parameter Description not complete successfully (implying that the changes requested in the method did not take effect), the value of ParameterKey MUST NOT be modified. The HMS MUST only modify the value of ParameterKey as a result of SetParameterValues, AddObject, DeleteObject, or due to a factory reset. On factory reset, the value of ParameterKey MUST be set to empty. --- RMS Access: READ Type: String. (Length: 0 to 32 characters). Notification: Forced FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

ConnectionRequestURL

HTTP URL for an HMS to make a Connection Request notification to the HNB. In the form: http://host:port/path The "host" portion of the URL MAY be the IP address for the management interface of the HNB in lieu of a host name. Internally set to the IP address of the IPSEC tunnel endpoint and then converted to an URL by the HNB before sending to HMS --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Reboot triggered by SetParameterValue. Notification: Forced FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_BootReason

The reason for the AP rebooting: 0 - Unspecified. The AP has rebooted for an unspecified reason. This could also be due to a factory-reset or the user doing a manual power-off. 1 - Software Fault. A software fault occurred which required the AP to reboot. 2 - Parameter Update. A configuration parameter was updated which required the AP to reboot. 3 - Software Upgrade. The AP has completed a software upgrade. 4 - Controlled Reboot. The AP has rebooted for a controlled reason. This could also be due to a operator-initiated reboot or a restart at Least Busy Hour. 5 - Loss of Network Connectivity. The network connection was lost and has now been re-established. 6 - Loss of Secure Connection. The IPsec tunnel was lost and has now been re-established. 7 - SIM Card Re-inserted. The SIM card was removed and has now been re-inserted." --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Unspecified" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IPAddressAffinity

Determines how the AP chooses the HMS IP address from a list returned by DNS: FirstEntry - Uses first in list



Object Parameter Description Random- Makes a random selection every time Preferred - Once the selection has been made once, continues to use the selected server for future connections --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Preferred" RMS Default value:N/A RMS Property:N/A Management level: System

Table 10 Configuration of the Management Server



33 UBS-44-57-004

4.5 WAN Device The WANDevice contains WAN connections objects associated to the physical WAN interface. The HNB shall support one instance of the WANDevice object.

Figure 5: Container of WAN devices

Object Parameter Description InternetGatewayDevice.WANDevice Each instance contains all objects associated with a particular

physical WAN interface. InternetGatewayDevice.WANDevice.1 The one and only instance of the WANDevice object InternetGatewayDevice.WANDevice.1.WANCommonInterfaceConfig

This object models WAN interface properties common across all connection instances.

WANAccessType

Specifies the WAN access (modem) type. Enumeration of: "DSL" "Ethernet" "POTS" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Ethernet" RMS Default value:N/A RMS Property:N/A Management level: N/A

Layer1UpstreamMaxBitRate

Specifies the maximum upstream theoretical bit rate for the WAN device in bits per second. This describes the maximum possible rate given the type of interface assuming the best-case operating environment, regardless of the current operating rate. For example, if the physical interface is 100BaseT, this value would be 100000000, regardless of the current operating rate. ---



Object Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 100000000 RMS Default value:N/A RMS Property:N/A Management level: N/A

Layer1DownstreamMaxBitRate

Specifies the maximum downstream theoretical bit rate for the WAN device in bits per second. This describes the maximum possible rate given the type of interface assuming the best-case operating environment, regardless of the current operating rate. For example, if the physical interface is 100BaseT, this value would be 100000000, regardless of the current operating rate. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 100000000 RMS Default value:N/A RMS Property:N/A Management level: N/A

PhysicalLinkStatus

Indicates the state of the physical connection (link) from WANDevice to a connected entity. Enumeration of: "Up" "Down" "Initializing" "Unavailable" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Up" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 11 WAN Device


InternetGatewayDevice.WANDevice.1.WANCommonInterfaceConfig

This object models WAN interface properties common across all connection instances.

MaximumActiveConnections Indicates the maximum number of active connections the CPE can simultaneously support. --- RMS Access: READ Type: Integer. (Range: 1 to 1). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

NumberOfActiveConnections Number of WAN connection service instances currently active on this WAN interface. --- RMS Access: READ



35 UBS-44-57-004

Object Parameter Description Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.WANDevice.1.WANCommonInterfaceConfig.Connection.1

The one and only instance of the active connection table

ActiveConnectionDeviceContainer Specifies a WAN connection device object associated with this connection instance. The content is the full hierarchical parameter name of the WAN connection device. Example: "Internet-GatewayDevice.WANDevice.1.WANConnection-Device.2". --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1" RMS Default value:N/A RMS Property:N/A Management level: N/A

ActiveConnectionServiceID Specifies a WAN connection object associated with this connection instance. The content is the full hierarchical parameter name of the layer 3 connection object. Example: "InternetGateway-Device.WANDevice.1.WANConnectionDevice.2.-WANPPPConnection.1". --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 12 WAN Device

Object Parameter Description InternetGatewayDevice.WANDevice.1.WANEthernetInterfaceConfig

The one and only instance of the LANEthernetInterfaceConfig object

Status

Indicates the status of this interface. Enumeration of: - "Up" - "NoLink" - "Error" (OPTIONAL) - "Disabled" The "Error" value MAY be used by the CPE to indicate a locally defined error condition. --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime



Object Parameter Description FAP Default value:”Up” RMS Default value:N/A RMS Property:N/A Management level: N/A

MACAddress

The physical address of the interface. --- RMS Access: READ Type: String. (Length: 0 to 17 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 13 WAN Device

4.5.1 DHCP Settings The plug & play principle allowing zero-touch HNB deployments is primarily based on DHCP (Dynamic Hosting Configuration Protocol) in order to retrieve the basic IP parameters such as IP address and netmask, default gateway IP address, DNS IP addresses, and also to exchange vendor information between the home gateway and the AP through DHCP options.

Nevertheless, in some specific situations, the Operator may want to choose deactivating the DHCP function on the HNB and configure this information statically, either at factory or by any other mean (i.e. via the AP Management Server after first initialisation).

The following object enables the configuration of IP connections of the WAN.

Object Parameter Description InternetGatewayDevice.WANDevice.1.WANConnectionDevice

Each instance contains objects associated with a given WAN link. In the case of DSL, each instance corresponds to either a single ATM VC or a PTM Ethernet link. On creation of a WANConnection-Device instance, there are initially no connection objects contained within. In the case of Ethernet (interface or link), only one WANConnectionDevice instance is supported.

InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1

The one and only instance of the WANConnectionDevice table

WANIPConnectionNumberOfEntries

Number of instances of WANIPConnection in this WANConnectionDevice. --- RMS Access: READ Type: Integer. (Range: 1 to 1). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

WANPPPConnectionNumberOfEntries

Number of instances of WANPPPConnection in this WANConnectionDevice. --- RMS Access: READ Type: Integer. (Range: 0 to 0). Notification: None FAP Default value: 0 RMS Default value:N/A



37 UBS-44-57-004

Object Parameter Description RMS Property:N/A Management level: N/A

InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection

This object enables configuration of IP connections on the WAN interface of a CPE. If the Layer2Bridging object is implemented, the view that it provides of the CPE's underlying bridging configuration MUST be consistent with the view provided by any LANDevice and WAN**Conn-ection objects. The implications of this are explained in Annex A.6.

InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1

The one and only instance of the WANIPConnection

AddressingType

The method used to assign an address to the WAN side interface of the CPE for this connection. Enumeration of: "Static" = 0 "DHCP" = 1 --- RMS Access: READ Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

ExternalIPAddress

This is the external IP address used by NAT for this connection. This parameter is configurable only if the AddressingType is Static. Ubiquisys Note: This is the FAP IP address on the WAN side, not the tunnel IP address --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: Forced Parameter modified via activation server. FAP Default value "192.168.1.120" RMS Default value:N/A RMS Property:N/A Management level: N/A

SubnetMask

Subnet mask of the WAN interface. This parameter is configurable only if the AddressingType is Static. --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Parameter modified via activation server. FAP Default value "255.255.0.0" RMS Default value:N/A RMS Property:N/A Management level: N/A

DefaultGateway

The IP address of the default gateway for this connection. This parameter is configurable only if the AddressingType is Static. --- RMS Access: READ Type: String. (Length: 0 to 15 characters).



Object Parameter Description Notification: None Parameter modified via activation server. FAP Default value "192.168.1.1" RMS Default value:N/A RMS Property:N/A Management level: N/A

DNSServers

Comma-separated list of DNS server IP addresses for this connection. Support for two DNS Servers max. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

MACAddress

The physical address of the WANIPConnection if applicable. Configurable only if MACAddressOverride is present and True. --- RMS Access: READ Type: String. (Length: 0 to 17 characters). Notification: Forced Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 14 DHCP Settings



39 UBS-44-57-004

FAP Service The parameters to be used by the HNB are specified by the specifications in [TR196].

The objects used by the HNB are summarised in the following figure.

Figure 6: FAP Service container

Description of the elements in these objects is to be found in the following sections:



1. .Capabilities.: see section 4.6

2. .FAPControl.: see section 4.7

3. .AccessMgmt.: see section 4.8

4. .CellConfiguration.: see section 4.9

5. .Transport.: see section 4.10

6. .REM.: see section 4.12

7. .GPS.: see section 4.13

8. .FaultMgmt.: see section 4.14

9. .PerfMgmt.: see section 4.16

10. .X_UBIQUISYS_COM_EventLogs.: see section 4.17

11. .X_UBIQUISYS_COM_Diagnostics.: see section 4.18

12. .X_UBIQUISYS_COM_QoS.: see section 4.19

13. .X_UBIQUISYS_COM_IPTiming.: see section 4.3.1

14. .X_UBIQUISYS_COM_BackhaulQoS.: see section 4.21

15. .X_UBIQUISYS_COM_LocalGUI.: see section 4.19

16. .X_UBIQUISYS_COM_HomeGateway.: see section 4.23

17. .X_UBIQUISYS_COM_GeoCoordinates.: see section 4.14

18. .X_UBIQUISYS_COM_Licencing.: see section 4.25

19. .X_UBIQUISYS_COM_TrafficControl.: see section Error! Reference source not found.

One instance of the FAPService object is used by the HNB as defined by the following parameter:

Object Parameter Description InternetGatewayDevice.Services Object name

FAPServiceNumberOfEntries

The number of entries in the FAPService table --- RMS Access: READ Type: Integer. (Range: 1 to 1). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService The Femto Access Point (FAP) Service Object. We will have only one instance of this object with instance number 1. The FAPService object and all of its underlying objects (except multi-instance objects) shall be automatically created by the HNB. This avoids the need for invoking many AddObject methods on the interface from HMS to HNB.

InternetGatewayDevice.Services.FAPService.1 The HNB shall support one and only one instance of the FAPService

DeviceType

The type of FAP device. Enumeration of: - "Standalone" - "Integrated" --- RMS Access: READ Type: Enumeration.



41 UBS-44-57-004

Object Parameter Description Notification: None Parameter modified via activation server. FAP Default value "Standalone" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_ModelCode

Model code of the Ubiquisys product (e.g. ZM-000-05) --- RMS Access: READ Type: String. (Length: 0 to 9 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_ModelRevision

Revision of the model of the Ubiquisys product (e.g. 0001) --- RMS Access: READ Type: String. (Length: 0 to 4 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

DNPrefix

Specifies the Distinguished Name (DN) Prefix to be used when constructing full DNs which uniquely identify a FAP object, e.g. .FaultMgmt.CurrentAlarm.{i}.ManagedObjectInstance. Encodes the Managed Object Prefix representation in string format as defined in 3GPP-TS32.300. Examples: "DC=a1.companyNN.com,SubNetwork=1,IRPAgent=1" and "SubNetwork=1" --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default Value: Requires Operator Input RMS Property : FC-DN-PREFIX Management level: Solution or Customer

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_DeploymentProfile Definition of a Deployment Profile

Name

Short description associated with the deployment profile (as set by the RF System Engineer team). E.g. 20dm_Multicell --- RMS Access: READ/WRITE Type: String. (Length: 0 to 80 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property : DEPLOYMENT-PROFILE-NAME Management level: System

Version Version number, as set by the RF System Engineer team,



Object Parameter Description for each profile release --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:DEPLOYMENT-PROFILE-VERSION Management level: System

Table 15 the FAPService object



43 UBS-44-57-004

4.6 Capabilities This object contains parameters relating to the hardware capabilities of the FAP device.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Capabilities This object contains parameters relating to the hardware

capabilities of the FAP device.

GPSEquipped

Indicates whether the FAP is equipped with a GPS receiver or not. --- RMS Access: READ Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxTxPower

Indicates the maximum possible transmit power in dBm that the FAP hardware can support (Ubiquisys maximum currently support is 30dBm for G6 hardware) --- RMS Access: READ Type: Integer. (Range: 0 to 30). Notification: None Parameter modified via activation server. FAP Default value 30 RMS Default value:N/A RMS Property:N/A Management level: N/A

SupportedSystems

Comma-separated list of strings. Each entry is a type of system that the FAP supports. Each list item is an enumeration of: - "UMTS" Other values are "For Future Study" (FFS). --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "UMTS" RMS Default value:N/A Management level: N/A

MaxChildSAPerIKE

Indicates the maximum number of child SAs per IKE session that the device is capable of supporting. --- RMS Access: READ Type: Integer. (Range: 1 to 100). Notification: None FAP Default value: 2 RMS Default value:N/A Management level: N/A

MaxIKESessions

Indicates the maximum number of IKE sessions the device is capable of supporting at any given time. --- RMS Access: READ Type: Integer. (Range: 1 to 50).



Object Parameter Description Notification: None FAP Default value: 1 RMS Default value:N/A Management level: N/A

X_UBIQUISYS_COM_HardwareFlag

Indication to software whether development/trials/commercial software builds are permitted on the HNB. The Integer value is mapped to the following 0: Development unit (Ubiquisys internal use only) 1: Trials unit (Partner use - will run development builds, Trace tool and Web GUI access is licenced) 2: Consumer unit (Consumer use - will only run securely signed software builds. Trace tool and Web GUI access is licenced) --- RMS Access: READ Type: Integer. (Range: 0 to 2). Notification: None Parameter modified via activation server. FAP Default value 2 RMS Default value:N/A Management level: N/A

X_UBIQUISYS_COM_TamperDetectionSupported

This parameter shall be set to True if the HNB supports the detection of tampering of the device. Otherwise it is set to False. --- RMS Access: READ Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value FALSE RMS Default value:N/A Management level: N/A

Table 16 Capabilities

4.6.1 UMTS Capabilities This object contains parameters relating to the system and RF aspect of the FAP device that supports the UMTS system (i.e. 3G HNB).

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Capabilities.UMTS

This object contains parameters relating to the system and RF aspect of the FAP device that supports the UMTS system (i.e. 3G HNB).

DuplexMode

Indicates the mode supported by the FAP. Enumeration of: - "FDDMode" Other values are "For Future Study" (FFS). --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "FDDMode" RMS Default value:N/A RMS Property:N/A Management level: N/A

GSMRxSupported Indicates whether the FAP hardware supports the



45 UBS-44-57-004

Object Parameter Description receiving function of GSM or not. --- RMS Access: READ Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

HSDPASupported

Indicates whether the FAP hardware supports the HSDPA capability or not. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxHSDPADataRateSupported

If the FAP hardware supports HSDPA (HSDPASupported is true), this parameter indicates the maximum HSDPA data rate in Kbps that the device supports. --- RMS Access: READ Type: Integer. (Range: 0 to 21000). Notification: None FAP Default value: 11808 RMS Default value:N/A RMS Property:N/A Management level: N/A

HSUPASupported

Indicates whether the FAP hardware supports the HSUPA capability or not. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxHSUPADataRateSupported

If the FAP hardware supports HSUPA (HSUPASupported is true), this parameter indicates the maximum HSUPA data rate in Kbps that the device supports. --- RMS Access: READ Type: Integer. (Range: 0 to 5760). Notification: None FAP Default value: 5712 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxHSPDSCHsSupported

If the FAP hardware supports HSPA family (either HSDPASupported is true or HSUPASupported is true),



Object Parameter Description this parameter indicates the available number of codes at the defined spreading factor (SF=16), within the complete code tree. See 3GPP-TS32.642 section 6.3.9 for more details --- RMS Access: READ Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 14 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxHSSCCHsSupported

If the FAP hardware supports HSPA family (either HSDPASupported is true or HSUPASupported is true), this parameter indicates the available number of HS-SCCHs for one cell. See 3GPP-TS32.642 section 6.3.9 for more details --- RMS Access: READ Type: Integer. (Range: 0 to 2). Notification: None FAP Default value: 2 RMS Default value:N/A RMS Property:N/A Management level: N/A

FDDBandsSupported

Comma-separated list (maximum length 16) of strings. Indicates the UMTS bands that the FAP supports 3GPP-TS.25.104, Release 8. At least one band MUST be supported and multiple bands MAY be supported. 3GPP-TS.25.104 Version 8.3.0 defines 14 UMTS bands (I through XIV). Each individual band is identified by its upper case Roman numeral. The order of the band indicators in the string has no significance. In case a new band is defined in the 3GPP standard in a future release of 3GPP-TS.25.104, the corresponding new upper case Roman numeral will be included in the valid band indicators. The followings are examples of valid values: "I" (specifies only band-I is supported) "I,II,V" (specifies 3 bands are supported) "II,VII,I" (specifies 3 bands are supported) --- RMS Access: READ Type: String. (Length: 0 to 16 characters). Notification: None Parameter modified via activation server. FAP Default value "I" RMS Default value:N/A RMS Property:N/A Management level: N/A

GSMRxBandsSupported

Comma-separated list of strings. Indicates the GSM receive bands that the FAP supports 3GPP-TS.45.005. At least one band MUST be supported and multiple bands MAY be supported. 3GPP-TS.45.005 defines 14 GSM bands. Each list item



47 UBS-44-57-004

Object Parameter Description is an enumeration of: T-GSM380 T-GSM410 GSM450 GSM480 GSM710 GSM750 T-GSM810 GSM850 P-GSM900 E-GSM900 R-GSM900 T-GSM900 DCS1800 PCS1900 The order of the band indicators in the string has no significance. The following is an example of a valid value. "GSM850,PCS1900" --- RMS Access: READ Type: String. (Length: 0 to 112 characters). Notification: None Parameter modified via activation server. FAP Default value "P-GSM900,E-GSM900,DCS1800" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 17 UMTS Capabilities

4.6.2 UMTS Self-Configuration Capabilities This object contains parameters relating to the self-configuration capabilities of the FAP. Self-configuration is enabled in .FAPControl.UMTS.SelfConfig.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Capabilities.UMTS.SelfConfig

This object contains parameters relating to the self-configuration capabilities of the FAP. Self-configuration is enabled in .FAPControl.UMTS.SelfConfig.

UARFCNConfig

Indicates whether the FAP supports the self-configuration capability to determine the UTRA Absolute Radio Frequency Channel Number (UARFCN). If true multiple values MAY be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A




PrimaryScramblingCodeConfig

Indicates whether the FAP supports the self-configuration capability to determine the Primary Scrambling Code (PSC). If true multiple values or a range of values MAY be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.PrimaryScramblingCode for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.PrimaryScramblingCode. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxFAPTxPowerConfig

Indicates whether the FAP supports the self-configuration capability to determine the Maximum FAP Transmit Power. If true a range of values MAY be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPower for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.MaxFAPTxPower. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

PCPICHPowerConfig

Indicates whether the FAP supports the self-configuration capability to determine the P-CPICH power. If true a range of values MAY be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.PCPICHPower for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.PCPICHPower as an upper bound. Note that Ubiquisys FAPs do not support PCPICH config as defined in TR-196 - we define it as a percentage of the MaxDLTxPower - see .CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.PercentageTotalPowerForCPICH. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A



49 UBS-44-57-004


MaxULTxPowerConfig

Indicates whether the FAP supports the self-configuration capability to determine the Maximum UL Transmit Power. If true a range of values MAY be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.MaxULTxPower for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.RAN.FDDFAP.RF.MaxULTxPower. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

LACRACURAConfig

Indicates whether the FAP supports the self-configuration capability to determine the LAC, RAC, and URA. If true multiple values MAY be provided in .CellConfig.UMTS.CN.LACRAC and .CellConfig.UMTS.RAN.URAList for the FAP to select from. If false only a single value SHOULD be provided in .CellConfig.UMTS.CN.LACRAC and .CellConfig.UMTS.RAN.URAList. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

NeighborListConfig

Indicates whether the FAP supports the self-configuration capability to determine the neighbor list. If true the ACS uses the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell. tables to explicitly include or exclude entries and the FAP uses that information to determine the final configuration found in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell. tables. If false the ACS uses the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}., .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell. tables to only specify the included entries and the



Object Parameter Description FAP uses that list. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

CellReSelectionConfig

Indicates whether the FAP supports the self-configuration capability to determine cell-reselection values. If true .CellConfig.UMTS.RAN.FDDFAP.CellSelection. can be self-configured. If false .CellConfig.UMTS.RAN.FDDFAP.CellSelection. is provided by the ACS. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

IntraFreqMeasConfig

Indicates whether the FAP supports the self-configuration capability to determine intra-frequency measurement values. If true .CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas. can be self-configured. If false .CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas. is provided by the ACS. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

InterFreqMeasConfig

Indicates whether the FAP supports the self-configuration capability to determine inter-frequency measurement values. If true .CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas. can be self-configured. If false .CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas. is provided by the ACS. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

InterRATMeasConfig

Indicates whether the FAP supports the self-configuration capability to determine inter-RAT measurement values.



51 UBS-44-57-004

Object Parameter Description If true .CellConfig.UMTS.RAN.FDDFAP.InterRATMeas. can be self-configured. If false .CellConfig.UMTS.RAN.FDDFAP.InterRATMeas. is provided by the ACS. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

UEInternalMeasConfig

Indicates whether the FAP supports the self-configuration capability to determine UE internal measurement values. If true .CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas. can be self-configured. If false .CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas. is provided by the ACS. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 18 UMTS Self-Configuration Capabilities



4.7 FAP Control This object contains parameters relating to state management and provisioning aspects of the FAP. The HMS employs parameters in the FAPControl object in order to verify and change states of the HNB.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl This object contains parameters relating to state

management and provisioning aspects of the FAP.

OpState

Current operational state of the FAP as defined in ITU-X.731. If true the FAP is currently enabled. If false the FAP is currently disabled. FAP shall set operational state to enabled after successful registration with serving gateway unless any of the following gating conditions apply - IPTiming poor resolution (unless overridden by changing 'PoorResolutionBehaviour' to 'Continue with Service' - HomeGateway MAC Address change - Location change (unless overridden by asserting OverrideLocationChangeServiceInhibition) - Invalid Country (unless overridden by asserting OverrideInvalidCountryServiceInhibition) Note that OpState=true does not necessarily mean that the FAP is providing service since the RF may still be disabled due to actions such as cell barring, HNB-GW initiated deregister, or failure of the HNB-GW or SecGW connection. --- RMS Access: READ Type: Boolean. Notification: Forced Value set at runtime FAP Default value=0 RMS Default value:N/A RMS Property:N/A Management level: N/A

AdminState

Lock or unlock the FAP. This controls the administrative state of the FAP as defined in ITUX.731. If true Unlocked with permission to serve traffic (and enable RF transmitter(s)). If false Locked. Transition FAP to state where it is NOT permitted to serve traffic. RF transmitter is disabled. Given that this command controls the FAP's RF transmitter, the underlying expectation is that the unlock is done when all necessary conditions are met to allow the transmitter to key on and provide service, including aspects such as: - location verification (including meeting the governing regulatory requirements) - verifying the FAP configuration - if physical tampering is supported and no physical tampering is detected. The default value after power-on is false. --- RMS Access: READ/WRITE Type: Boolean. Notification: None



53 UBS-44-57-004

Object Parameter Description Value set at runtime FAP Default value=0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RFTxStatus

Current status of this RF transmitter. true indicates that the 3G Tx transmitter is on. false indicates that the 3G Tx transmitter is off. This state is tied to the Administrative state which is controlled by the ACS. When the ACS sets AdminState to true, then the FAP has permission to turn on the RF transmitter. When the ACS sets AdminState to false, then the FAP is not allowed to provide service and MUST turn off the RF transmitter. --- RMS Access: READ Type: Boolean. Notification: Forced Value set at runtime FAP Default value=0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_SecureConnectionStatus

Current state of the secure network connection - "OK" - "Cannot create secure connection" - "Unknown" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Unknown” RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_RebootLock

When this parameter is true, normal behaviour where a reboot is initiated due to change to any parameter that has it's "Reboot Required" flag set to "reboot", is suppressed. If the RebootLock flag is subsequently set false, a reboot will take place if it was previously suppressed. --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_NetworkConnectionStatus

Current state of the network connection - "OK" - "No physical network connection" - "Cannot get IP address"



Object Parameter Description - "Cannot resolve GW DNS address" - "Unknown" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”unknown” RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_HardwareStatus

Status of the hardware: 0 - OK 1 - Fault - hardware problem but can still operate 2 - OverTemperature - overrides Fault 3 - Fault - hardware problem can no longer operate --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "OK" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_InServiceForPSSessions

If set to TRUE then the 'In service' LED flashes for CELL DCH PS sessions as well as CS sessions. Otherwise the LED only flashes when a CS call is being made. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Default

EnclosureTamperingDetected

This parameter indicates whether or not physical tampering of the device enclosure occurred, such as illegal opening of the box. If true device tampering is detected. If false no sign of device tampering is detected. Tampering state must be persisted across reboots and the device MUST never reset it back from true to false even after a factory reset. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property:N/A Management level: N/A

Table 19 FAP Control



55 UBS-44-57-004

4.7.1 Enabling of UMTS Capabilities This object contains parameters relating to the UMTS system specific information.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS

This object contains parameters relating to the UMTS system specific information.

InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.SelfConfig

This object contains parameters relating to the controlling of self-configuration capabilities in the FAP.

UARFCNSelfConfigEnable

Indicates whether the self-configuration capability in the FAP is used or not to determine the values of .CellConfig.UMTS.RAN.CSG.UARFCNDLList. If true The FAP self-configures the value. If false The ACS must provide the specific value to be used. --- RMS Access: READ/WRITE Type: Boolean. Reboot triggered by SetParameterValue. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: ENABLE-UARFCN-SELF-CONFIG Management level: System

LACRACURASelfConfigEnable

Indicates whether the self-configuration capability in the FAP is used or not to determine the values of .CellConfig.UMTS.CN.LACRAC and .CellConfig.UMTS.RAN.URAList. If true The FAP self-configures the value. If false The ACS must provide the specific value to be used. --- RMS Access: READ/WRITE Type: Boolean. Reboot triggered by SetParameterValue. Notification: None FAP Default value: TRUE RMS Default value:True for Residential False for Enterprise RMS Property: ENABLE-LAC-RAC-URA-SELF-CONFIG Management level: Deployment

Table 20 Enabling of UMTS Capabilities

4.7.2 Gateways Configuration The Security Gateway is provisioned by two separate threads; one is included in the operator data delivered by the ZoneGate Activation Server (ZAS) and another one by the HMS. The HMS control of the Security Gateway can only be performed after HNB initialisation and typically would be used for online HNB transitions to a new SeGW, under HMS controlled redirections.

The provisioning Security Gateway is the operator data parameter provisioned from the ZAS and cannot be overwritten. Taking precedence over this parameter, the serving 'Network Gateway' range of FQDN, common to both RAN and CN GWs, can be used by the HMS to provide SeGW control to the operational team managing the femtocell solution via HMS.

Modifying this latter parameter will automatically force an HNB reboot.

The following parameters are used for configuration of the FGW.



Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.Gateway

This object contains parameters relating to the Gateways that FAP is connected to.

SecGWServer1

First serving SecGW the FAP attempts to establish connection with. Either hostname or IPaddress. This is a "platform-copy" parameter so that an initial SecGW may be obtained from operator data in order to make the initial connection, after which the parameter may be updated by the HMS. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value "" RMS Default Value: Requires Operator Input RMS Property: FC-IPSEC-SERVER-HOST Management level: Customer or Deployment

SecGWServer2

Second serving SecGW the FAP attempts to establish connection with. Either hostname or IPaddress. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default Value: "" RMS Property: FC-IPSEC-SERVER-HOST-2 Management level: Customer or Deployment

FAPGWServer1

First FAP-GW the FAP attempts to establish connection with. Either hostname or IPaddress. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default Value: Requires Operator Input RMS Property: HNB-GW-SERVER Management level: Customer or Deployment

FAPGWPort

Port number of HNB-GW used by FAP for initial Iuh SCTP contact. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 29169 RMS Default value:29169 RMS Property: HNB-GW-PORT Management level: System

X_UBIQUISYS_COM_Partner

--- RMS Access: READ Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value "default"



57 UBS-44-57-004


X_UBIQUISYS_COM_FAPGWLatencyAlarmWindow

The FAP monitors the round-trip time for procedures involving theFAP Gateway (HNB-GW) such as UE Registration/Deregistration and TNL Update Procedure. Excessive response time is flagged by an alarm based on a moving window average of the response latency. This param defines the size of the window in seconds --- RMS Access: READ/WRITE Type: Integer. (Range: 60 to 86400). Notification: None FAP Default value: 3600 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_FAPGWLatencyAlarmCount

The FAP monitors the round-trip time for procedures involving theFAP Gateway (HNB-GW) such as UE Registration/Deregistration and TNL Update Procedure. Excessive response time is flagged by an alarm based on a moving window average of the response latency. This param defines the threshold for the number of times the response latency is violated before the alarm is raised. A value of zero disables the alarm --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_FAPGWLatencyAlarmThreshold

The FAP monitors the round-trip time for procedures involving theFAP Gateway (HNB-GW) such as UE Registration/Deregistration and TNL Update Procedure. Excessive response time is flagged by an alarm based on a moving window average of the response latency. This param defines the threshold for the response latency, in mS, before pegging this slow response. The alarm is raised if the number of violations exceeds the AlarmCount in the given AlarmWindow --- RMS Access: READ/WRITE Type: Integer. (Range: 10 to 2000). Notification: None FAP Default value: 100 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_LongTermIPsecFailureAlarmThreshold

The parameter defines the maximum number of SecGW discoveries failure. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 300). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: System

SourcePortForFAPGWConnection Source Port number used by FAP for initial Iuh SCTP



Object Parameter Description contact with the HNB-GW. If 0, FAP will use random port .number on every connection other wise FAP will always use the port number specified --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 29169 RMS Default value:N/A RMS Property:N/A Management level: System

Table 21 Gateways Configuration



59 UBS-44-57-004

4.7.2.1 Further HNB-GW Parameters Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.Gateway

This object contains parameters relating to the Gateways that FAP is connected to.

X_UBIQUISYS_COM_RecoverableConnectionFirstTimeout

In case the HNB detects a loss of the connection, a FGW swap, or connection establishment failure (IPSEC tunnel/TR-069/SCTP) to the currently connected SecGW the HNB will first try to re-establish a connection to the same SeGW after FirstTimeout + delta1 expiry. The delta1 addition is a uniformly distributed random value in the range [0..100]second. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 100). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_RecoverableConnectionSecondTimeout

Upon unsuccessful SeGW retry after T1 + delta1 expiry, the HNB will try to establish a connection to the same SecGW after SecondTimeout + delta2 expiry. The delta2 addition is a uniformly distributed random value in the range [0..300]second. --- RMS Access: READ/WRITE Type: Integer. (Range: 5 to 300). Notification: None FAP Default value: 100 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_UnrecoverableConnectionTimeout

If HNB has retried all SecGWs in the iSeGW or sSeGW pool, it will wait for this timer before falling back to the iSeGW (units of minutes) --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 60). Notification: None FAP Default value: 5 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_Partner

--- RMS Access: READ Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None Parameter modified via activation server. FAP Default value "default" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 22 Further HNB-GW Parameters



4.7.3 Software Upgrade Configuration This object contains parameters relating to the software running on the FAP

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.X_UBIQUISYS_COM_Software

This object contains parameters relating to the software running on the FAP

UpgradeStatus

Current state of upgrade: - "NoUpgrade" - No upgrade in progress - "DownloadingFiles" - Waiting to download files - "WaitingForInit" - Waiting for the next initialization to complete upgrade - "Failed" - Upgrade failed. - "DBUpgradeFault" - Database Upgrade failed. - "SWTrial" - Software running in trial period --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "NoUpgrade" RMS Default value:N/A RMS Property:N/A Management level: N/A

UpgradeControl

When to perform upgrade: - "Immediately" - indicates immediately stop all current calls (including emergency calls) - "PDQ" - Wait until current calls have terminated, and then carry out the upgrade. New calls may be started if another call is already in progress - "LeastBusyHour" - Upgrade when there are no calls allowed - "NextInit" - During the next HNB next initialization. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Immediately" RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

PreviousSoftwareVersion

Version of software in the backup memory. If there is no pervious version then this will be NULL. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RevertToBackupVersion

If set to TRUE, the HNB reverts to the software stored in the backup memory. The HNB clears the flag once it has completed the operation. --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A



61 UBS-44-57-004

Object Parameter Description Management level: System

ClearPreviousVersion

If set to TRUE, the HNB will delete the version of software in backup memory and copy the current version into backup memory. At the same time the configuration information will be changed accordingly. The HNB will then clear the flag once it has completed the operation. --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: System

NetworkID

Identifies network that the HNB is deployed on - used by factory recovery and Download Controller to validate suitability of software for the network. There are 3 ways to authorise a load, 1) NetworkId value "0" allows all loads, 2) Match the NetworkId to a value specified in the "AuthorisedNetworks" list in the SCF, 3) Have no entries in the "AuthorisedNetworks" list, this will also allow all s/w loads. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Parameter modified via activation server. FAP Default value 0 RMS Default value:N/A RMS Property:N/A Management level: System

NetworkVersion

Version of the configuration information for the specified Network ID. Value 0 means no network version specified. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Parameter modified via activation server. FAP Default value 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

BootloaderVersion

Bootloader software version --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RecoveryKernelVersion

Version of the "factory recovery kernel". --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value ""



Object Parameter Description RMS Default value:N/A RMS Property:N/A Management level: N/A

BackupRecoveryKernelVersion

Backup factory recovery kernel version --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

StandardKernelVersion

Version of the kernel currently in use. --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

AltStandardKernelVersion

Main kernel version (alternative kernel currently not in use) --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RootfsVersion

Version of the "root file system" currently in use. --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

AltRootfsVersion

Root file system version (alternative system currently not in use) --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

UbiqfsVersion

Version of the Ubiquisys' file system currently in use. --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server.



63 UBS-44-57-004

Object Parameter Description FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

AltUbiqfsVersion

Ubiquisys file system version (alternative system currently not in use) --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 23 Software Upgrade Configuration

4.7.4 Timers

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.X_UBIQUISYS_COM_Timers

This object contains parameters relating to internal timers in the FAP

TEmergencyCallTail

Time after an emergency call made by an user is released that the AP will apply emergency status to any follow-on call, CS or PS, for that user. (seconds) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 600). Notification: None FAP Default value: 60 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 24 Timers



4.8 Call Admission Control The HNB supports 3 different access control modes for UE, which can be configured from the AP Management Server via .AccessMgmt.AccessMode:

Closed access mode: In this mode, the AP is configured by the HMS with the list of “allowed UEs” (see section on “Access Lists”). This list consists of IMSIs and always includes the IMSI of the Femtocell subscriber (i.e. the account holder) and optionally any other UEs that this subscriber has requested, up to the maximum allowed list size. The AP allows up to 250 UE in the list; however, the list size is operator configurable and maximum value of 10 or 20 is more typical for a consumer environment. In this mode, the AP will locally reject requests from any UE that is not on the AP’s allowed UE list. The AP performs this rejection without involving the core network in any signalling. The rejection cause can be operator selected via FinalRejectCauseForUENotAllowed and FinalRejectCauseForUEUnauthorised.

Open access mode: In this mode, the AP does not maintain a local list of authorised UEs. Instead all requests from UEs to attach to the AP are referred to the Iuh and core network, and the AP accepts or rejects UEs according to the response received from the Iuh or core network.

Semi-open access mode: This mode combines both previous modes by maintaining a local list of authorised UE and also by referring requests to attach from any unknown UEs to the core network before accepting/rejecting the UE. This mode permits preferential treatment for registered UEs above the open access UEs.

The access control and UE rejection method selection is summarised in the table below:

Access Control

Parameter Settings HNB Access Mode (rejection method for

closed access) NonCSGUE Access

Decision

Access Mode

AccessControlList X_UBIQUISYS_COM_ MemberReservedCalls

Local

Closed 1+ entry N/A Closed

(Immediate UE Reject) Hybrid1 1+ entry

N/A

N/A

Open N/A 0 Open

1+ entry 1+ Semi-Open

QueryFAP-GW

Closed 1+ entry N/A Closed

(Service Based UE Reject ) Hybrid 1+ entry N/A

N/A

Open N/A 0 Open


By Core

Closed N/A 0 Open


Hybrid N/A 0 Open


Open N/A 0 Open


Table 25 - Access control and UE rejection method selection 1 In R3.x Cisco do not recommend configuring Hybrid when NonCSGUEAccessDecision is Local or QueryFAP-GW, since this HNB actually operates in closed access mode.



65 UBS-44-57-004

Upon rejection of the unauthorised UE by the HNB-GW in a HNBAP: UE REGISTER REJECT message, the HNB performs NAS layer rejection towards that UE. The NAS layer reject cause used by the HNB is determined by the following combination of HNB parameters and the cause provided by HNB-GW in the UE REGISTER REJECT messages:

Rejection cause by HNB-GW in HNBAP: UE REGISTER REJECT

HNB uses reject cause as defined in the object InternetGatewayDevice.Services.FAPService.1.AccessMgmt. X_UBIQUISYS_COM_RejectionRedirection

‘UE not allowed on this HNB’ FinalRejectCauseForUENotAllowed

‘UE unauthorized” FinalRejectCauseForUEUnauthorised

Table 26 - NAS rejection cause selection parameters

The HNB behaviour as regards keeping any context or record for this UE is unchanged from the behaviour when immediate UE rejection is enabled and after local rejection by the HNB.

Alternatively, control of GoS and QoS can be enforced by basic Call Admission Control (CAC) defining the maximum number of concurrent CS calls .AccessMgmt.X_UBIQUISYS_COM_MaxCSUsers, the maximum number of concurrent PS calls .AccessMgmt.X_UBIQUISYS_COM_MaxPSUsers, the maximum number of concurrent UE signalling channels .AccessMgmt.X_UBIQUISYS_COM_MaxSRBUsers.

Moreover, the parameter .AccessMgmt.X_UBIQUISYS_COM_RejectionRedirection.CongestedCSCallBehaviour configures the AP behaviour when it is running at full CS call capacity and another CS call arrives or when the maximum number of simultaneous signalling resources are in use and another user attempts a new signalling procedure:

• Value = 0: Send RRCConnectionReject with redirection to another 3G frequency (if inter-freq macro neighbours are detected) else to the 2G network. This should allow the call to continue on the macro network as long as the UE can detect a macro neighbour.

• Value = 1: Send RRCConnectionReject without redirection. This will cause the call to fail but will ensure there is no billing ambiguity.

• Value = 2: Enable Service Redirection to a macrocell. This will cause the RAB ASSIGNMENT for CS call to be redirected to a suitable neighbouring macrocell

In open access mode, the AP does not maintain a list of authorised users. Instead, the AP is optionally configured with a “whitelist” of allowed IMSI masks.

• If no entries are configured in the whitelist, defined by the number of mask entries WhiteListNumberOfEntries (see .AccessMgmt.X_UBIQUISYS_COM_WhiteList.); then the AP refers all UE attach requests to the core network.

• If one or more entries are configured in the whitelist, then the AP compares the UE’s IMSI against each IMSImask value in the whitelist (see .AccessMgmt.X_UBIQUISYS_COM_WhiteList.). Failure for the UE’s IMSI to match an entry in the whitelist causes the AP to locally reject the UE. A successful match of the UE’s IMSI against any of the entries in the whitelist allows the AP to refer the attach request to the Core Network and the AP subsequently accepts or rejects the UE according to the response received from the Core Network.

4.8.1 Access Management Parameters The content of the .AccessMgmt. object is summarised in the figure below:



Figure 7: Access Management container

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.AccessMgmt

This object contains parameters relating to Access Management (ACL, CSG, LIA). Closed Subscriber Group (CSG) service behaviour is specified in 3GPP-TS.22.011. Note: Cell barring and 3GPP access class parameters are contained in .CellConfig.UMTS.RAN.FDDFAP.CellRestriction.

HomeZoneName

An operator-defined ASCII character string that is displayed on the UE when it is connected to the HNB. The home zone name may be used by the HNB to indicate its identity to a non-CSG capable UE. E.g. through Cell Broadcast or SMS. On Ubiquisys HNB, this parameter sent to UEs through the MMINFO message and is optional possible to override operator setting from owner GUI. If set to empty string then no MMINFO will be sent. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 160 characters).



67 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: "" RMS Default Value: Requires Operator Input RMS Property: HOME-ZONE-NAME Management level: Customer

X_UBIQUISYS_COM_HomeZoneIndicationControl

This parameter controls which method of HomeZone Indication is enabled including when and how the HNB manipulates core network initiated MM-INFO messages. The following enumerations (in quotes) define the HNB behaviour as follows: "HZDisplay Disabled" (Default) The HNB does: 1. not generate MM-INFO 2. not intercept CN-initiated MM-INFO "ePLMN Method" The HNB does: 1. not generate MM-INFO. 2. intercept CN-initiated MM-INFO messages and replace network name fields dependent on whether the UE is authorised for service or not as follows: a. UE authorised: do not modify network name fields b. UE not authorised: replace with spaces. "MMINFO Method" The FAP does: 1. generate MM-INFO towards UEs. 2. intercept and replace network name fields in CN-initiated MM-INFO messages. In both cases the HNB inserts/replaces network names fields in MM-INFO dependent on whether the UE is authorised for service or not as follows: a. UE authorised: use HomeZoneName b. UE not authorised: use spaces. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "HZDisplay Disabled" RMS Default value: "HZDisplay Disabled" RMS Property: HOME-ZONE-INDICATION-CONTROL Management level: Solution

X_UBIQUISYS_COM_HomeZoneCharacterEncoding

Defines the encoding scheme that will be used for the HomeZoneName string in the (G)MMINFO message - "UCS2" - "GSM7" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "GSM7" RMS Default value: "GSM7" RMS Property: HOME-ZONE-CHARACTER-ENCODING Management level: Customer

X_UBIQUISYS_COM_HomeZonePSNotification

The 'Home Zone PS Notification' message that is sent to the UE in a type 0 SMS when it starts a PS session. If set



Object Parameter Description to empty string then no PS notification will be sent to UEs. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 130 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property: N/A Management level: N/A

X_UBIQUISYS_COM_EnableHomeZoneTone

If enabled, a tone file is played during a voice-call set-up. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: ENABLE-HOMEZONE-TONE Management level: Customer

X_UBIQUISYS_COM_MaxConcurrentUsers

The maximum number of users (CSG and Non-CSG) that can be attached to the HNB concurrently (either from the AccessControlList or open access) --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 1000). Notification: None FAP Default value: 100 RMS Default value:100 RMS Property: ACCESS-MGMT-CONCURRENT-USERS Management level: Solution or Customer

X_UBIQUISYS_COM_MaxPchUsers

The maximum number of users that can be in CELL_PCH state. This value must always be less than MaxConcurrentUsers otherwise MaxConcurrentUsers will override this value. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 200). Notification: None Value is persistent FAP Default value: 24 RMS Default value:24 RMS Property: N/A Management level: Solution or Customer This feature is not supported in this version of Release

X_UBIQUISYS_COM_MaxCSUsers

Maximum number of concurrent CS calls --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16). Notification: None FAP Default value: 4 RMS Default value:4 RMS Property: ACCESS-MGMT-CONCURRENT-CS-CALLS Management level: Solution or Customer

X_UBIQUISYS_COM_MaxSRBUsers

Maximum number of concurrent UE signalling channels (SRBs) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 24). Notification: None FAP Default value: 12 RMS Default value:12 RMS Property: ACCESS-MGMT-MAX-SRBUSERS Management level: Solution or Customer



69 UBS-44-57-004


X_UBIQUISYS_COM_MaxSRBRegistrations

Maximum number of concurrent UE signalling channels (SRBs) used for connections with cause set to Registration. This includes registration, location and routing area updates. It does not include connections reconfigured as calls. It is set using the MedMobCap, HiMobCap licences --- RMS Access: READ Type: Integer. (Range: 0 to 24). Notification: None FAP Default value: 4 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_MaxDSUsers

Maximum number of concurrent Dedicated Channels to use --- RMS Access: READ Type: Integer. (Range: 1 to 16). Notification: None FAP Default value: 4 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CurrentAppliedMaxCSLimit

Maximum number of concurrent CS calls once all hardware and licensing limits are applied by SC --- RMS Access: READ Type: Integer. (Range: 0 to 16). Notification: None Value set at runtime RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CurrentAppliedMaxSRBLimit

Maximum number of concurrent UE signalling channels (SRBs) once all hardware and licensing limits are applied by SC --- RMS Access: READ Type: Integer. (Range: 0 to 24). Notification: None Value set at runtime RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CurrentAppliedMaxDSLimit

Maximum number of concurrent Dedicated Channels once all hardware and licensing limits are applied by SC --- RMS Access: READ Type: Integer. (Range: 1 to 16). Notification: None Value set at runtime RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_BackhaulLimitedMaxCSUsers

Maximum number of concurrent CS calls capable within measured backhaul performance limits. --- RMS Access: READ Type: Integer. (Range: 0 to 16). Notification: None FAP Default value: 16 RMS Default value:N/A RMS Property:N/A




X_UBIQUISYS_COM_CurrentAppliedBSLimit

Number of CS calls which can be sustained on the current backhaul based on BQoS limits. Note: Serving calls on anchor FAPs will count as two BS users. --- RMS Access: READ Type: Integer. (Range: 0 to 16). Notification: None FAP Default value: 4 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 27 Access Management Parameters

4.8.2 Redirection to LTE The below table indicates the configurable parameters for redirection to LTE if required.

InternetGatewayDevice.Services.FAPService.1.AccessMgmt.ReleaseRedirectionToLTE Object name

ReleaseAndRedirectToLTE

This flag enables or disables the functionality in this feature If set to true, then the FAP includes Redirection Info IE in the RRC CONNECTION RELEASE message as CSFB call is released. If set to false, then the FAP excludes Redirection Info IE in the RRC CONNECTION RELEASE message as CSFB call is released. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-RELEASE-REDIRECT-TO-LTE Management level: Deployment specific or Customer

PreferrdMethodOfRedirectionToLTE

This parameter is valid only when RedirectToLTE parameter is set to true. Enumerations: Colocated_LTE_Cell Any_suitable_LTE_cell --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Any_suitable_LTE_cell" RMS Default value: "Any_suitable_LTE_cell" RMS Property: FC-METHOD-REDIRECT-TO-LTE Management level: System

PreferrdMethodOfPSOnlyCallHandling

This parameter determines the PS-only call handling behaviour when the CSFB call ends. See section 3.2.3.3.3. Enumerations: Keep_in_3G Redirect_to_LTE --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Redirect_to_LTE"



71 UBS-44-57-004

InternetGatewayDevice.Services.FAPService.1.AccessMgmt.ReleaseRedirectionToLTE Object name

RMS Default value: "Redirect_to_LTE" RMS Property: FC-PSONLY-CALL-HANDLING Management level: Deployment specific or Customer

Table 28 Access Lists

4.8.3 IMSI White List Filtering in Open Mode White lists are used in open access mode.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.AccessMgmt.X_UBIQUISYS_COM_WhiteList WhiteList configuration

MaxMasksEntries

The maximum number of entries available in the .AccessMgmt.X_UBIQUISYS_COM_WhiteList.Masks.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 20). Notification: None FAP Default value: 20 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.AccessMgmt.X_UBIQUISYS_COM_WhiteList.Masks

List of whitelist masks to be applied to all unregistered user access attempts. Only used if NonCSGUEAccessDecision is not 'Local'

Table 29 IMSI White List Filtering in Open Mode

4.8.4 Traffic Hot-spot Management An HNB is deemed to be in “traffic hot-spots” if a large number of un-authorized UEs, (i.e. UEs not included in the access list) attempt to camp on the HNB. These UE’s will be rejected by the HNB with Location Update Rejection (cause #15 or #13).

Such scenario may easily arise where closed access residential HNBs are installed in houses near public locations where large number of people convey, such as a restaurant, bars, bus stops etc.

Currently the HNB is deployed in OpenAccess mode and hence the parameter DeploymentCategory of a residential HNB is set as “General”, i.e. the HNB assumes that it is not in a traffic hot-spot location.

4.8.5 Rejection and Redirection

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.AccessMgmt.X_UBIQUISYS_COM_RejectionRedirection Rejection and redirection configuration

EnableEmergencyCallRedirect

Set to TRUE to enable the emergency call redirect feature (all emergency calls are re-directed to the macro network rather than being serviced by the femtocell) --- RMS Access: READ/WRITE Type: Boolean. Notification: None



Object Parameter Description FAP Default value: FALSE RMS Default value:FALSE RMS Property: ENABLE-EMG-CALL-REDIRECT Management level: Deployment specific or Customer

EmergencyCallRedirectPreference

If emergency call redirect is enabled above then this field configures which type of macro cell the call is redirected to: - "UMTS" - UMTS if inter-freq neighbours detected, otherwise GSM - "GSM" - GSM only --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "UMTS" RMS Default value:UMTS RMS Property: EMG-CALL-REDIRECT-PREFERENCE Management level: Deployment specific or Customer

MaxRRCLayerRejections

Number of times an unauthorised UE will be rejected at the RRC layer before being allowed to establish a SRB and be rejected by NAS. The value "0" implies the feature is disabled; i.e. no RRC rejection is used for unauthorised UEs. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 3). Notification: None FAP Default value: 3 RMS Default value : N/A RMS Property:N/A Management level: N/A

FinalRejectCauseForUENotAllowed

Selects which reject cause is used by the AP when rejecting unauthorised UEs at the (G)MM layer for temporary rejection: - "Cause 13" [Roaming not allowed in this location area] - "Cause 15" [No suitable cells in location area] - "Cause 12" [Location Area not allowed] - "Cause 11" [PLMN not allowed] - "Cause 111" [Protocol error, unspecified] This is used if UE Registration to HNB-GW fails with a temporary reject cause (eg. 'UE not allowed on this HNB'). --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Cause15" RMS Default value: "Cause15" RMS Property: UE-NOTALLOWED-FINAL-REJECT-CAUSE Management level: Default

FinalRejectCauseForUEUnauthorised

Selects which reject cause is used by the AP when rejecting unauthorised UEs at the (G)MM layer for permanent rejection: - "Cause 13" [Roaming not allowed in this location area] - "Cause 15" [No suitable cells in location area] - "Cause 12" [Location Area not allowed] - "Cause 11" [PLMN not allowed] - "Cause 111" [Protocol error, unspecified] This is used if UE Registration to HNB-GW fails with a permanent reject cause (eg. 'UE unauthorised') or following HNB local access control decision to reject the UE without



73 UBS-44-57-004

Object Parameter Description involving HNB-GW --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Cause15" RMS Default value: "Cause15" RMS Property: UE-UNAUTHORISED-FINAL-REJECT-CAUSE Management level: Default

ExtendedEmergencyServiceSupportEnabled

Controls the use of the Simplified Extended Emergency Service feature. Set to TRUE, extended emergecy service will be applied to allow follow-on CS and PS calls to be treated as emergency calls for pre-emption and retention. Only SIMPLIFIED version supported in this version. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: N/A RMS Property:N/A Management level: N/A

CongestedCSCallBehaviour

Configures the AP behaviour when it is running at full CS call capacity and another CS call arrives or when the maximum number of simultaneous signalling resources are in use and another user attempts a new signalling procedure: 0 - Send RRCConnectionReject with redirection to another 3G frequency (if inter-freq macro neighbours are detected) else to the 2G network. This should allow the call to continue on the macro network as long as the UE can detect a macro neighbour. 1 - Send RRCConnectionReject without redirection. This will cause the call to fail but will ensure there is no billing ambiguity. 2 - Enable Service Redirection to suitable Macro. This will cause the rab assignment for CS call to be redirected to a suitable Macro (note, this option is not currently supported) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value: N/A RMS Property:N/A Management level: Customer

X_UBIQUISYS_COM_BlackList

Configure an IMSI blacklist - IMSI; comma separated full IMSI. UE will be rejected with LAU cause given by NAS cause for UE reject --- RMS Access: READ/WRITE Type: String ( 0 to 164 characters) Notification: None FAP Default value: “” RMS Default value: “” RMS Property: FC-BLACK-LIST Management level:Solution or Customer

Table 30 Rejection and Redirection



4.8.6 Emergency Calls

The handling and prioritisation of emergency call is described in [UBS-44-41-002].

This feature allows the operator to configure whether the HNB accepts emergency calls from unauthorised UEs not provisioned in the HNB database. There are two database parameters that control whether

• An unauthorised UE can make an emergency call on the HNB when macro coverage is present

• An unauthorised UE can make an emergency call on the HNB when no macro coverage is present

In addition, the feature allows the operator to configure the length of time that the unauthorised UE is kept registered on the HNB following the initial emergency call – this is called the emergency registration period. During this period location updates and routing area updates from the UE are accepted, but all MO activity other than further emergency calls, and any non-conversational MT calls will be rejected, conversation MT calls will be accepted which is designed to allow emergency call centre responses back to the user.

The emergency registration timeout can be configured as zero which will cause the UE to be de-registered from the core network the moment the initial emergency call is terminated.

The feature does not affect the congestion handling within the FAP, which remains the same as per emergency calls from authorised UEs.

The following flow chart illustrates the emergency call handling decisions taken by the FAP for unauthorised UEs in Closed access mode:

RRC connection Request from un-authorised UEwith establishment cause: Emergency

Y

Are Ecalls for non-authorised UEs allowed?

Y

Are Ecalls for non-authorised UEs under macro coverage allowed?

Send RRC CON REJECT (Cause= unspecified, Wait Time=0)

N

Macro coverage detected?

1-Handle like emergency RRC connection Request from authorised UE

N

N

Y

4.8.6.1 Non Provisioned User Emergency Calls

Although this feature is principally for Closed access mode, it changes the behaviour of emergency call handling for Open and Semi-Open access modes. In these modes the database parameters controlling whether emergency calls are handled by the FAP are now used to control whether emergency calls are accepted from open-access users.



75 UBS-44-57-004

The emergency registration timeout period does not apply for Open and Semi-Open modes however and once accepted for the initial emergency call in these modes they will be registered as normal open-access users in the HLR and will be removed from the HLR after the normal HLR expiry timeout period has elapsed.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.AccessMgmt.X_UBIQUISYS_COM_RejectionRedirection Rejection and redirection configuration

EnableEmergencyCallRedirect

Set to TRUE to enable the emergency call redirect feature (all emergency calls are re-directed to the macro network rather than being serviced by the femtocell) --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default Value :False RMS Property : ENABLE-EMG-CALL-REDIRECT Management Level : Deployment specific or Customer

EmergencyCallRedirectPreference

If emergency call redirect is enabled above then this field configures which type of macro cell the call is redirected to: - "UMTS" - UMTS if inter-freq neighbours detected, otherwise GSM - "GSM" - GSM only --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "UMTS" RMS Default Value :”UMTS” RMS Property : EMG-CALL-REDIRECT-PREFERENCE Management Level : Deployment specific or Customer

MaxRRCLayerRejections

Number of times an unauthorised UE will be rejected at the RRC layer before being allowed to establish a SRB and be rejected by NAS. The value "0" implies the feature is disabled; i.e. no RRC rejection is used for unauthorised UEs. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 3). Notification: None FAP Default value: 3 RMS Default value : N/A Management level: N/A

FinalRejectCauseForUENotAllowed

Selects which reject cause is used by the AP when rejecting unauthorised UEs at the (G)MM layer for temporary rejection: - "Cause 13" [Roaming not allowed in this location area] - "Cause 15" [No suitable cells in location area] - "Cause 12" [Location Area not allowed] - "Cause 11" [PLMN not allowed] - "Cause 111" [Protocol error, unspecified] This is used if UE Registration to HNB-GW fails with a temporary reject cause (eg. 'UE not allowed on this HNB'). --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Cause15"



Object Parameter Description RMS Property: UE-NOTALLOWED-FINAL-REJECT-CAUSE Management level: Default

FinalRejectCauseForUEUnauthorised

Selects which reject cause is used by the AP when rejecting unauthorised UEs at the (G)MM layer for permanent rejection: - "Cause 13" [Roaming not allowed in this location area] - "Cause 15" [No suitable cells in location area] - "Cause 12" [Location Area not allowed] - "Cause 11" [PLMN not allowed] - "Cause 111" [Protocol error, unspecified] This is used if UE Registration to HNB-GW fails with a permanent reject cause (eg. 'UE unauthorised') or following HNB local access control decision to reject the UE without involving HNB-GW --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Cause15" RMS Default value:”Cause 15” RMS Property: UE-UNAUTHORISED-FINAL-REJECT-CAUSE Management level: Default

CongestedCSCallBehaviour

Configures the AP behaviour when it is running at full CS call capacity and another CS call arrives or when the maximum number of simultaneous signalling resources are in use and another user attempts a new signalling procedure: 0 - Send RRCConnectionReject with redirection to another 3G frequency (if inter-freq macro neighbours are detected) else to the 2G network. This should allow the call to continue on the macro network as long as the UE can detect a macro neighbour. 1 - Send RRCConnectionReject without redirection. This will cause the call to fail but will ensure there is no billing ambiguity. 2 - Enable Service Redirection to suitable Macro. This will cause the rab assignment for CS call to be redirected to a suitable Macro (note, this option is not currently supported) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value: N/A Management level: Customer

Table 31 Non Provisioned User Emergency Calls

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FAPControl.X_UBIQUISYS_COM_Timers

This object contains parameters relating to internal timers in the FAP

TEmergencyRegistration

Time after first emergency call made by an unauthorised user is released that the AP will keep the UE 'emergency registered' to allow for further emergency calls and/or call back from PSAP (seconds) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 3600). Notification: None



77 UBS-44-57-004

Object Parameter Description FAP Default value: 60 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 32 Non Provisioned User Emergency Calls



4.8.7 Cell Restriction Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellRestriction

This object contains parameters related to cell access restriction.

CellBarred Indicates whether the FAP is barred from service or not. 3GPP-TS.25.331 Section 10.3.2 --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

IntraFreqCellReselectionIndicator When CellBarred is true, this indicates whether the intra-frequency cell re-selection is allowed or not. IntraFreqCellReselectionIndicator has no meaning if CellBarred is false and MUST be ignored in such cases. true means that intra-frequency cell re-selection is allowed. false means that intra-frequency cell re-selection is not allowed. 3GPP-TS.25.331 Section 10.3.2 --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

TBarred The time period in seconds during which the UE is barred from accessing the FAP. Values allowed are 10, 20, 40, 80, 160, 320, 640, 1280 3GPP-TS.25.331 Section 10.3.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 3 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

AccessClassBarredListCS Comma-separated list of unsigned integers (range 0 to 15). Each entry is an Access Class that is barred from CS service. The order of the list has no significance. 3GPP-TS.25.331 Section 10.3.2 Note that this will only be acted on by UEs compliant with R6 or later specifications --- RMS Access: READ/WRITE Type: String. (Length: 0 to 45 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

AccessClassBarredListPS Comma-separated list of unsigned integers (range 0 to 15). Each entry is an Access Class that is barred from PS service. The order of the list has no significance.



79 UBS-44-57-004

Object Parameter Description 3GPP-TS.25.331 Section 10.3.2 Note that this will only be acted on by UEs compliant with R6 or later specifications --- RMS Access: READ/WRITE Type: String. (Length: 0 to 45 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

CellReservedForOperatorUse Indicates whether the FAP is reserved for operator use or not. 3GPP-TS.25.331 Section 10.3.2 --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property:FC-RESERVED-MODE Management level: Default or Customer

X_UBIQUISYS_COM_RepetitionTimes

The number of times the restriction step is repeated. 0 means repeat forever. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1000). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

Table 33 Cell Restriction

4.8.7.1 Access-Class Barring Access Class Baring breaks into 3 components:

• Broadcast System Information Blocks (SIBs) and Master Information Block (MIB) extended to support the R6 25.331 v6c0 3GPP specification.

• Extend the database to permit static configuration of R99/R5 RNAR access class barring and R6 CS/PS DSAC access class barring.

• Support the Dynamic Access Class Barring schedule based on barring percentage and time as configured for R99/R5 Radio Network Access Restriction (RNAR) and R6 CS/PS Domain Specific Access Class (DSAC)

The R6 support for the SIBs results in extensions being configured for each required SIB. These will only be processed by UEs compliant with the necessary specification version. The following R6 (or R5 if specified) extensions have been added as part of this feature:

• SIB3 support for QrxLevMin values between -116 and -119dBm [R5 extension]

• SIB3 DSAC fields to control access class barring for the PLMN specified in the MIB

• SIB5 frequency band indicator (FDD 2100MHz)

• SIB5 HSDPA capability of the cell indicator (always TRUE)

• SIB11 support for QrxLevMin of each neighbour cell between -116 and -119dBm [R5 extension]

• SIB11 support for requesting Inter-Frequency measurements on RACH (for future AP use in selecting potential handout candidates)



The RNAR configuration operates in parallel with DSAC in order to maintain backwards compatibility. This means the RNAR and DSAC parameters will be enabled, but only RNAR will apply to 3GPP Release 99 and 3GPP Release 5 UEs, while DSAC will apply to 3GPP Release 6 UEs.

As defined in 3GPP 25.331, the UE will re-read SIB3 when it’s updated if the UE is in IDLE or Cell FACH. While in Cell FACH, the UE will only apply the change in barred state for the CS domain. This is standard operation as specified in the 3GPP specs as the barred block is only applied when a signalling connection is required for a given domain.

The HNB delivers Access Class Barring either by means of a statically implementation, for which defined classes are barred for a certain period, or dynamically, where the barring of classes fluctuates cyclically to allow for all users to be equally served by the AP.

Static Access Class Barring

Each access class can be individually barred by the operator from the APMS by tuningwith any of the configuration items referred in X_UBIQUISYS_COM_AccessClassBarredListPreR6 as (see .CellConfig.UMTS.RAN.FDDFAP.CellRestriction, section 4.8.7):

• AccessClassBarredListCS

• AccessClassBarredListPS

When set to True, these parameters activate the access class barring; while, False deactivates it (which is the default behaviour). There is no duration or expiration associated with this configuration; it must be cleared by the APMS.

Dynamic Access Class Barring

The Femto AP must be able to support a cyclic access class restriction when enabled from the APMS. This is configured from a percentage of restriction, restriction interval and repetition times. Each access classes will be cyclically barred by AP internal logical based on APMS configuration by playing with any of the configuration items referred as (see .CellConfig.UMTS.RAN.FDDFAP.CellRestriction, section 4.8.7):

• X_UBIQUISYS_COM_PreR6RestrictionPercentage

• X_UBIQUISYS_COM_CSRestrictionPercentage

• X_UBIQUISYS_COM_PSRestrictionPercentage

The restriction interval X_UBIQUISYS_COM_RestrictionInterval and repetition times X_UBIQUISYS_COM_RepetitionTimes define the delay between each step and how many steps to go through the sequence respectively. The algorithm can be configured to never end by setting the X_UBIQUISYS_COM_RepetitionTimes to 0. The restriction interval and repetition times are applied to all 3 restriction modes, therefore the sequence is always kept in sync between RNAR, DSAC-CS and DSAC-PS.

Once the dynamic access class barring schedule is complete for the configured number of steps, the Femto AP will restore the static configuration of access class barring. The Femto AP will also update the dynamic access class barring database parameters for percentage of restriction to 0%.

A description of the percentages is shown in the table here below where each bit represents an AC class (i.e. Bit1: AC0, Bit2: AC1 and respectively…), and a value of 1 infers restriction on the Access Class

0% 10% 20% 30% 40% 50% Step0 Step1 Step2 Step3 Step4 Step5 Step6 Step7 Step8

0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000 0000000000

1000000000 0100000000 0010000000 0001000000 0000100000 0000010000 0000001000 0000000100 0000000010

1000010000 0100001000 0010000100 0001000010 0000100001 1000010000 0100001000 0010000100 0001000010

1001001000 0100100100 0010010010 0001001001 1000100100 0100010010 0010001001 1001000100 0100100010

1010010010 0101001001 1010100100 0101010010 0010101001 1001010100 0100101010 0010010101 1001001010

1010101010 0101010101 1010101010 0101010101 1010101010 0101010101 1010101010 0101010101 1010101010



81 UBS-44-57-004

0% 10% 20% 30% 40% 50% Step9 0000000000 0000000001 0000100001 0010010001 0100100101 0101010101 60% 70% 80% 90% 100% Step0 Step1 Step2 Step3 Step4 Step5 Step6 Step7 Step8 Step9

0101101101 1010110110 0101011011 1010101101 1101010110 0110101011 1011010101 1101101010 0110110101 1011011010

0110110111 1011011011 1101101101 1110110110 0111011011 1011101101 1101110110 0110111011 1011011101 1101101110

0111101111 1011110111 1101111011 1110111101 1111011110 0111101111 1011110111 1101111011 1110111101 1111011110

0111111111 1011111111 1101111111 1110111111 1111011111 1111101111 1111110111 1111111011 1111111101 1111111110

1111111111 1111111111 1111111111 1111111111 1111111111 1111111111 1111111111 1111111111 1111111111 1111111111

Combination of Static and Dynamic Access Class Barring When configured, the dynamic access class barring pattern is merged with whatever configuration has been set for the static access class barring. Therefore, if AC2 is statically set as barred and a 10% dynamic restriction pattern is set; the actual sequence of restriction is as follows:

An example configuration is as follows:

RNAR: 50%, DSAC-CS: 20%, DSAC-PS: 30%, Restriction Interval: 2 minutes, Repetition Times: 2

RNARDSAC

CSDSAC

PS RNARDSAC

CSDSAC

PS RNARDSAC

CSDSAC

PS RNARDSAC

CSDSAC

PSAC0 - - - Restrict Restrict Restrict - - - - - -AC1 - - - - - - Restrict Restrict Restrict - - -AC2 - - - Restrict - - - - - - - -AC3 - - - - - Restrict Restrict - - - - -AC4 - - - Restrict - - - - Restrict - - -AC5 - - - - Restrict - Restrict - - - - -AC6 - - - Restrict - Restrict - Restrict - - - -AC7 - - - - - - Restrict - Restrict - - -AC8 - - - Restrict - - - - - - - -AC9 - - - - - - Restrict - - - - -

Before Restriction

2 minutes

After RestrictionStep 2Step 1

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellRestriction


X_UBIQUISYS_COM_AccessClassBarredLis Comma-separated list of unsigned integers (range 0 to 15).

(The Red 1 is the statically barred AC2)

Step0: 1010000000

Step1: 0110000000

Step2: 0010000000

Step3: 0011000000

Step4: 0010100000

Step5: 0010010000

etc



Object Parameter Description tPreR6 Each entry is an Access Class that is barred from both PS

and CS service. The order of the list has no significance. 3GPP-TS.25.331 Section 10.3.2 This is included to provide barring capability for R5/R99 UEs that will not read the DSAC fields configured above. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 45 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

X_UBIQUISYS_COM_PreR6RestrictionPercentage

Configures percentage of R5 or R99 UE access classes that will be barred for the dynamic access class restriction. (0=0%, 1=10%, 10=100%) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

X_UBIQUISYS_COM_CSRestrictionPercentage

Configures percentage of R6 or later UE access classes that will be barred on the CS domain for the dynamic access class restriction. (0=0%, 1=10%, 10=100%) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

X_UBIQUISYS_COM_PSRestrictionPercentage

Configures percentage of R6 or later UE access classes that will be barred on the PS domain for the dynamic access class restriction. (0=0%, 1=10%, 10=100%) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

X_UBIQUISYS_COM_RestrictionInterval

The duration of a restriction step in minutes --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 10). Notification: None FAP Default value: 2 RMS Default value:N/A RMS Property:N/A Management level: Default or Customer

Table 34 Access-Class Barring



83 UBS-44-57-004

4.9 Cell Configuration for UMTS The object .CellConfig. includes those parameters used for configuring UMTS specific information. The subobjects are shown in the figures below.

Figure 12: CN object



Figure 13: RAN object

The container objects for these parameters are:

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig This object contains parameters relating to configuring the

FAP. InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS

This object contains parameters relating to configuring UMTS system specific information.

Table 35 Cell Configuration for UMTS

4.9.1 CN Configurations

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN

This object contains parameters relating to configuring UMTS CN.

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. Note that the MNC is always maintained in the database as a fixed-length 3-digits - the 3rd digit is 'F' where only a 2-digit MNC is required. ---



85 UBS-44-57-004

Object Parameter Description RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: CELL-CONFIG-PLMNID Management level: Deployment specific

EquivPLMNID Comma-separated list (maximum length 64) of strings (maximum item length 6). Each item is a PLMNID. PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of the PLMNID is 5. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value: "" RMS Property: CELL-CONFIG-EQUIV-PLMNID Management level: Solution or Customer

SAC Service Area Code (SAC) 3GPP-TS.23.003. The concatenation of PLMN ID (MCC+MNC), LAC, and SAC uniquely identifies the Service Area ID (SAI). --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SAC-ID Management level: Deployment specific or Cutomer

X_UBIQUISYS_COM_BroadcastSAC Service Area Code (SAC) for broadcast. The format of this parameter is the same with SAC, and it uniquely identifies the Service Area ID (SAI) for Earthquake and Tsunami Warning Services (ETWS) [Section 9.1.3/3GPP-TS.25.469] --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SAC-ID Management level: System

LACRAC Comma-separated list (maximum length 256) of strings. Each item is a LAC/RAC combination expressed in the following format: <LAC or LACrange>':'<RAC or RACrange> Where LAC and RAC are single values, while LACrange and RACrange are inclusive and can be expressed in the following format: <Start-value>".."<End-value> Location Area Code (LAC) consists of up to 5 numerical characters. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section



Object Parameter Description 9.2.3.6. Routing Area Code (RAC) consists of up to 3 numerical characters. The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7. The FAP is to select one LAC and RAC from the combination(s) expressed in this parameter for use in LACInUse and RACInUse respectively. If a LAC occurs more than once in the list, this shall not increase the chance that it is selected over other LAC values in the list. The following are examples of the valid LACRAC combination formats: "64000:210" (one list item with single value for LAC and RAC) "64000..64100:210, 64101:211" (two list items, first item has a LAC range) "64000:210..214, 64001:215..219" (two list items, both items have a RAC range for a specific LAC value) "64000..64100:210..214" (one list item both have a LAC range and a RAC range) --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:4000..62000:10..200 RMS Property: FC-LAC-RAC-CL-CLOSE-MODE CELL-CONFIG-LAC-RAC-CL FC-LAC-RAC-CL-GRID Management level: Deployment specific or Customer or System or Solution

LACInUse The LAC being used by the FAP. Self-configuration for LAC is controlled by .Capabilities.UMTS.SelfConfig.LACRACURAConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the choices provided in LACRAC. If the self-configuration capability is not available or not enabled, then this parameter contains the first LAC value in LACRAC. LACInUse is made persistent so that on reboot, the previous LACInUse may be discounted from the selected choice of LAC --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: Active Value set at runtime FAP Default value:0 RMS Default value: N/A RMS Property:N/A Management level: N/A

RACInUse The RAC being used by the FAP. Self-configuration for RAC is controlled by .Capabilities.UMTS.SelfConfig.LACRACURAConfig



87 UBS-44-57-004

Object Parameter Description from an availability perspective and .FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the choices provided in LACRAC. If the self-configuration capability is not available or not enabled, then this parameter contains the first RAC value in LACRAC. --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default value: N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IuPLMNID Defines the PLMN ID reported on the Iu interface in place of the PLMNID used by the UE. Format is identical to PLMNID. Only used (and mandatory) if X_UBIQUISYS_COM_LAIRAISwapEnable is TRUE or if X_UBIQUISYS_COM_CBSSAItype is set to Iu --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: CELL-CONFIG-IU-PLMNID Management level: Deployment specific or Cutomer

X_UBIQUISYS_COM_IuRAC Defines the RAC reported on the Iu interface in place of the RAC used by the UE. Only used (and mandatory) if X_UBIQUISYS_COM_LAIRAISwapEnable is TRUE --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: CELL-CONFIG-IU-RAC Management level: Deployment specific or Cutomer

X_UBIQUISYS_COM_CBSLAC Defines the LAC to be used in CBS SAI if X_UBIQUISYS_COM_CBSSAItype is set to CBS. Only used (and mandatory) if X_UBIQUISYS_COM_CBSSAItype is set to CBS. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-LAC-ID Management level: System

X_UBIQUISYS_COM_CBSPLMNID Defines the PLMN ID to be used in CBS SAI if X_UBIQUISYS_COM_CBSSAItype is set to CBS. Format is identical to PLMNID. Only used (and mandatory) if X_UBIQUISYS_COM_CBSSAItype is set to CBS. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters).



Object Parameter Description Notification: None FAP Default value: "" RMS Default value:Input RMS Property: CBS-PLMNID Management level: System

X_UBIQUISYS_COM_CBSSAItype Parameter to specify which PLMN and LAC will be used in the SAI value used by HNB in SABP (BroadcastSAI). Enumeration of: - "Uu" - "Iu" - "CBS" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Uu" RMS Default value:CBS RMS Property: CBS-SAI-TYPE Management level: System

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.CSDomain

This object contains parameters relating to configuring the CS domain of the UMTS CN.

T3212 T3212 timeout value specified in seconds. 3GPP-TS.24.008 Note that the spec only allows the value to be specified to the nearest decihour so the FAP will round the value down if it is not divisible by 360 seconds. Value of 0 means that periodic updating is disabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 91800). Notification: None FAP Default value: 360 RMS Default value:360 RMS Property: CELL-CONFIG-T3212 Management level: Deployment specific or Cutomer

IMSIAttachDetachEnable Indicates the UE behavior regarding IMSI attach/detach procedure to the CN. 3GPP-TS.24.008 If true UE SHALL apply IMSI attach and detach procedure If false UE SHALL NOT apply IMSI attach and detach procedure --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A Management level: Solution

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.PSDomain

This object contains parameters relating to configuring the PS domain of the UMTS CN.

X_UBIQUISYS_COM_EnablePSHandoutTo3GMacro

For 3G macros that do not support SRNC relocation of PS services, this control provides the means to trigger Iu release of PS domain in order to suppress handout of PS RABs --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE/RF Profile v2.4 RMS Property: ENABLE-PSHANDOUT-3G-MACRO Management level: Deployment specific

X_UBIQUISYS_COM_CurrentFreqPSRelease Quality offset to be added to for 2D thresholds for the



89 UBS-44-57-004

Object Parameter Description OffsetEcNo current cell when a PS ONLY call when

EnablePSHandoutTo3GMacro is FALSE.. Units of dB. This parameter is for EcNo measurements only --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 24). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: CURRENT-FREQ-PS-REL-OFFSET-ECNO Management level: Deployment specific or Cutomer

X_UBIQUISYS_COM_CurrentFreqPSReleaseOffsetRSCP

Quality offset to be added to for 2D thresholds for the current cell when a PS ONLY call when EnablePSHandoutTo3GMacro is FALSE.. Units of dB. This parameter is for RSCP measurements only --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 95). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: CURRENT-FREQ-PS-REL-OFFSET-RSCP Management level: Deployment specific or Cutomer

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.X_UBIQUISYS_COM_MMGMMParams

This object contains parameters relating to configuring the MMGMM entity within the FAP

UEPeriodicRAUTimer Periodic Routing Area Update time interval (in minutes). Note in RANGW mode this parameter is not used to populate in NAS messages to the UE but it should be set to the same value as the SGSN otherwise the internal FAP timers that manage UE deregistration on inactivity would not work correctly. --- RMS Access: READ/WRITE Type: Integer. (Range: 3 to 186). Notification: None FAP Default value: 60 RMS Default value:60 RMS Property: CELL-CONFIG-RAU-TIMER Management level: Deployment specific or Cutomer

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.X_UBIQUISYS_COM_RANAPParams

This object contains parameters relating to configuring the RANAP entity within the FAP

PSTransitionToIdleReleaseCause RANAP cause value that will be sent to the core network when the FAP releases a PS RAB due to inactivity. User Inactivity is the recommended value by 3GPP (and hence the default) but other values may be used for inter-working with non-standards compliant networks. - "User Inactivity" (16) - "Network Optimisation" (116) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: User Inactivity RMS Default value:N/A RMS Property:N/A Management level: Default

Table 36 CN Configurations

4.9.1.1 CN Configuration Extensions



Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN

This object contains parameters relating to configuring UMTS CN.

X_UBIQUISYS_COM_LAIRAISwapEnable If configured and enabled (X_UBIQUISYS_COM_LAIRAISwapEnable = true), the following three valus replace those received from the UE in RANAP and NAS messages to the CN. RANAP and NAS message from the CN to the UE will have these values overwritten with the PLMNID, LACInUse and RACInUse values. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default vaue:TRUE RMS Property: CELL-CONFIG-LAI-RAI-SWAP-ENABLE Management level: System

X_UBIQUISYS_COM_IuLAC Defines the LAC reported on the Iu interface in place of the LAC used by the UE. Only used (and mandatory) if X_UBIQUISYS_COM_LAIRAISwapEnable is TRUE or if X_UBIQUISYS_COM_CBSSAItype is set to Iu --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-LAC-ID Management level:Deployement specific or Customer

Table 37 CN Configuration Extensions

4.9.2 RAN Configuration

4.9.2.1 Parameters used for Configuring the RAN

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN

This object contains parameters relating to the RAN level configuration.

URAInUse The URA being used by the FAP. Self-configuration for URA is controlled by .Capabilities.UMTS.SelfConfig.LACRACURAConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.LACRACURASelfConfigEnable from an enabled perspective. If the FAP's self-configuration capability for URA is available and enabled, this parameter indicates the value selected by the FAP among the choices provided in URAList. If the self-configuration capability is not available or not enabled, then this parameter contains the first URA value in URAList. Note: Ubiquisys FAPs do not support broadcast of URA



91 UBS-44-57-004

Object Parameter Description information (no SIB2) but this field is included in the data model to allow full support of the UMTSSelfConfig:1 profile --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RNCID RNC-ID allocated to the FAP. It uniquely identifies an RNC within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than 4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit need to have them separated. 3GPP-TS.25.413 Section 9.2.1.39. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Customer

CellID Cell Identity. 3GPP-TS.25.331 Section 10.3.2.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 268435455). Notification: None FAP Default value: 0 RMS Default value: 1 RMS Property: CELL-CONFIG-RAN-CELL-ID Management level: Deployement specific or Custmer or Solution

TRatC Guard period in seconds before sending a "RANAP:RESET ACKNOWLEDGE" message towards the Femto GW. 3GPP-TS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Default or Deployement specific

TRafC Maximum amount of time in seconds that the FAP SHOULD wait for receiving a "RANAP:RESET ACKNOWLEDGE" message from the Femto GW after sending a Reset to the Femto GW. 3GPPTS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 30 RMS Default value:N/A RMS Property:N/A



Object Parameter Description Management level: Default or Deployement specific

NRafC Maximum number for RESET procedure that can be repeated in FAP. 3GPP-TS.25.413 Section 8.26.3.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: Default

TigOR Amount of time in seconds used to determine when the additional level of traffic reduction in CN overload should take place. While this timer is running all OVERLOAD messages or signalling pointing to congested information received by the FAP are ignored. 3GPP-TS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 5 RMS Default value:N/A RMS Property:N/A Management level: N/A

TinTR Amount of time in seconds used to determine when the CN overload can be considered cleared. While this timer is running, the FAP is not allowed to increase traffic. 3GPP-TS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 15 RMS Default value:N/A RMS Property:N/A Management level: N/A

TRelocPrep Maximum amount of time in seconds for the Relocation Preparation procedure. Timer is started when a "RANAP:Relocation Required" message is sent. Timer is stopped when a "RANAP:Relocation Command" or a "RANAP:Relocation Preparation Failure" message is received. 3GPP-TS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 4 RMS Default value:N/A RMS Property:N/A Management level: Default

TRelocOverall Maximum amount of time in seconds for protection of the overall Relocation procedure. Timer is started when a "RANAP:Relocation Command" message is received. Timer is stopped when a "RANAP:Iu Release Command" is received or the relocation procedure is cancelled. 3GPP-TS.25.413 Section 9.5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 10 RMS Default value:N/A



93 UBS-44-57-004

Object Parameter Description RMS Property:N/A Management level: Default

X_UBIQUISYS_COM_RelocRetryTimer Time to wait before retrying handout if a temporary failure occurs (in seconds). --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 3 RMS Default value:N/A RMS Property:N/A Management level: Default

Table 38 Parameters used for Configuring the RAN

4.9.3 Cell Level Configurations

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP

This object contains parameters relating to the cell level configuration for FDD mode FAP.

HSFlag

Enables/disables the HSDPA function in the FAP. If true HSDPA is enabled (this is equivalent to a "1" in 3GPP-TS.32.642 Section 6.3.9) If false HSDPA is disabled (this is equivalent to a "0" in 3GPP TS.32.642 Section 6.3.9 --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Default

HSEnable Enables or disables HSDPA in the cell. If true HSDPA is enabled (this is equivalent to a "1" in 3GPP-TS.32.642 Section 6.3.9) If false HSDPA is not enabled (this is equivalent to a "0" in 3GPP-TS.32.642 Section 6.3.9) If HSFlag is false then this value MUST be false. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Default

NumOfHSPDSCHs The number of codes at the defined spreading factor (SF=16), within the complete code tree. 3GPP-TS.32.642 Section 6.3.9 Note: Ubiquisys FAPs will treat this as the maximum number of HSPDSCHs allowed but may decide to reduce the number actually used dependent on the R99 call load --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 14). Notification: None FAP Default value: 14



Object Parameter Description RMS Default value:N/A RMS Property:N/A Management level: System or Solution

NumOfHSSCCHs The number of HS-SCCHs for one cell. 3GPP-TS.32.642 Section 6.3.9 Note: Ubiquisys FAPs will treat this as the maximum number of HSSCCHs allowed but may decide to reduce the number actually used dependent on the R99 call load Note: presently does not support configuration to non-default value hence restrict range to single default value --- RMS Access: READ/WRITE Type: Integer. (Range: 2 to 2). Notification: None FAP Default value: 2 RMS Default value:N/A RMS Property:N/A Management level: Default or System or Solution

X_UBIQUISYS_COM_SRBConfiguration Configures the use of fast (13.6k) SRB: - "Disabled" - use slow (3.4k) SRB with all services. This will lead to slower call setup times. - "Enabled for all" - use fast (13.6k) SRB with all services. This gives the fastest possible call setup times but may cause IOT issues with older UEs. - "Enabled except AMR" - use fast (13.6k) SRB with all services except for standalone AMR which will be configured with 3.4k SRB. This is the default as some older UEs do not support the AMR + 13.6k SRB RAB combination defined in Release 7. - "Only when no RAB" - Fast (13.6k) SRB is only used when there are no other RABs present. As soon as any CS or PS RAB is added the FAP will revert to 3.4k SRB. This means the first call setup will be fast but multiRAB/multiPDP additions will be slow. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Enabled for all" RMS Default value:N/A RMS Property:N/A Management level: Default

X_UBIQUISYS_COM_CellPCHEnabled Enables or disables the CELL_PCH feature. This parameter is used in conjuction with the licence value: Cell_PCH_FD to determine if the CELL_PCH feature is enabled. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: CELL-PCH-ENABLED Management level: Default

X_UBIQUISYS_COM_DualSCCPCHEnabled Determines the S-CCPCH configuration used by the FAP. - If FALSE then it uses a single S-CCPCH according to 3GPP 34.108 6.10.2.4.3.3 - If TRUE then it uses two S-CCPCH channels according to 3GPP 34.108 6.10.2.4.3.1 and 6.10.2.4.3.2 --- RMS Access: READ/WRITE Type: Boolean.



95 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: Default or System or Solution

X_UBIQUISYS_COM_SRBOnEDCHEnabled Controls whether SRB is placed upon EDCH for PS only HSUPA calls. This is required to achieve max throughput (5.76Mbps) on the uplink for Cat 6 devices, but will be used for all HSUPA calls if set to free up UL SF resources. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-SRB-ON-EDCH-ENABLED Management level: Deployement

X_UBIQUISYS_COM_CurrentFreqCSVideoHandoverQualityOffset

Quality offset to be added to all of the handover trigger thresholds for the current cell when a CS video call is present (either standalone or MultiRAB). Units of dB. The PS value takes priority if a video call co-exists with a PS call. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 24). Notification: None FAP Default value: 0 RMS Default value: 0/RF Profile v2.3 RMS Property: CURRENT-FREQ-CS-HANDOVER-QUALITY Management level: Deployement

X_UBIQUISYS_COM_CurrentFreqPSHandoverQualityOffset

Quality offset to be added to all of the intra/inter handover trigger thresholds for the current cell when a PS call is present (either standalone or MultiRAB). Units of dB. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 24). Notification: None FAP Default value: 0 RMS Default value: 0/RF Profile v2.3 RMS Property: CURRENT-FREQ-PS-HANDOVER-QUALITY Management level: Deployement

X_UBIQUISYS_COM_CbsLevel1Scheduling Enables CBS Level 1 Scheduling 0: Disabled 1: Static 2: Dynamic --- RMS Access: READ/WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "Disabled" RMS Default value: "Disabled" RMS Property: CBS-LEVEL-1-SCHEDULING Management level: Deployement specific or Customer

X_UBIQUISYS_COM_FastDormancyRRCStateChangePreference

State change preference when a UE requests fast dormancy, a value of FAST_DORMANCY_DISABLED will disable the feature regardless of the licence. Valid states are: FAST_DORMANCY_DISABLED, IDLE, CELL_PCH, CELL_FACH, CELL_DCH ---



Object Parameter Description RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "FAST_DORMANCY_DISABLED" RMS Default value: "FAST_DORMANCY_DISABLED" RMS Property: FAST-DORMANCY-STATE-CHANGE-PREFERENCE Management level: N/A

X_UBIQUISYS_COM_CbsLevel2Scheduling Enables CBS Level 2 Scheduling 0: Disabled 1: Enabled --- RMS Access: READ/WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "Disabled" RMS Default value:N/A Management level: Deployement specific or Customer

X_UBIQUISYS_COM_IMSSignallingBearerTHP

Identifies a PS RAB of Interactive Traffic Class as being used to transport IMS traffic and so subject to be prioritised over other PS RABs of Interactive or Background Traffic Class --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 1 RMS Default value:1 RMS Property: FC-IMS-SIGNALLING-BEARER-THP Management level: Customer

X_UBIQUISYS_COM_IMSSignallingRABPrioritisation

If disabled then the concept of IMS Signalling PS RAB is not used and all PS RABs are treated with the same priority. If enabled then IMS Signalling PS RAB has more priority than common PS RAB. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE RMS Property: FC-IMS-SIGNALLING-RAB-PRIORITISATION Management level: Customer

X_UBIQUISYS_COM_PSRABPreemptionByIMSSignRAB

If disabled then the IMS Signalling PS RABs may not pre-empt common PS RABs during IMS Signalling PS RAB activation. If enabled then the IIMS Signalling PS RABs may pre-empt common PS RABs during IMS Signalling PS RAB activation --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE RMS Property: FC-PSRAB-PREEMPTION-BY-IMSSIGN-RAB Management level: Customer

X_UBIQUISYS_COM_CellFACHHandoverEnabled

Gating control for hand-in of UEs in Cell-FACH --- RMS Access: READ/WRITE Type: Boolean.



97 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: TRUE RMS Default value;N/A RMS Property:N/A Management level: Solution

Table 39 Cell Level Configurations

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellRestriction


X_UBIQUISYS_COM_R5_ACB_Status String showing bit mask for R99/R5 barred access classes, covering all forms of access class barring: static, dynamic and stepped. Left most character is AC0. --- RMS Access: READ Type: String. (Length: 0 to 11 characters). Notification: None Value set at runtime FAP Default value: "0000000000" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_R6_CS_ACB_Status String showing bit mask for R6 CS barred access classes, covering all forms of access class barring: static, dynamic and stepped. Left most character is AC0. --- RMS Access: READ Type: String. (Length: 0 to 11 characters). Notification: None Value set at runtime FAP Default value: "0000000000" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_R6_PS_ACB_Status String showing bit mask for R6 PS barred access classes, covering all forms of access class barring: static, dynamic and stepped. Left most character is AC0. --- RMS Access: READ Type: String. (Length: 0 to 11 characters). Notification: None Value set at runtime FAP Default value: "0000000000" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_SACB_Enable Enables Stepped Access Class Barring at AP reboot --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: 0 / RF Profile v. 2.3 Modify RMS Property: CELL-SACB-ENABLE Management level: Deployment



Table 40 Cell Level Configurations

4.9.3.1 SIB19

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19

SIB19 Control Parameters

SIB19Included

Flag to include SIB19 in the system broadcast info or not --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: SIB19-INCLUDE Management level: Deployment specific or Customer

SIB19ConfigMode

Auto(1) or Manual(0) configuration of SIB19. It is desired to have residential type devices to done automatically, but for outdoor small cell type products (e.g. G5, G6), they prefer to manually configure everything. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value: 0 / RF Prfoile Modify RMS Property: SIB19-CONFIG-MODE Management level: Deployment specific

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19.UTRA

SIB19 Parameters - Serving Cell and UTRAN FDD Frequencies

ThreshXHigh

RSCP value, Unit in dB by step of 2. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: SIB19-THRESH-HIGH Management level: Deployment specific

ThreshXLow

RSCP value, Unit in dB by step of 2. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: SIB19-THRESH-LOW Management level: Deployment specific

UTRANFDDFreqsNumberOfEntries

Number of entries in UTRANFDDFreqs list. --- RMS Access: READ Type: Integer. (Range: 0 to 8). Notification: None FAP Default value: 0 RMS Default value:N/A RMS property:N/A Management level: N/A

UTRANFDDFreqsDeleteAllInstances

When this parameter is set to true, all instances of the UTRANFDDFreqs Instance object will be deleted. The parameter is locally cleared to false by the HNB.



99 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:FALSE RMS Property: SIB19-UTRAN-FDD-FREQ-DELETE-ALL-INSTANCES Management level: N/A

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19.UTRA.UTRANFDDFreqs SIB19 Parameters - UTRAN FDD Frequencies Info

UARFCN

UARFCN of downlink Carrier frequency (FDD) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16383). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SIB19-ARFCN-i-DOWNLINK Management level: Deployment specific

Priority

Priority value of the UTRAN FDD Freq. 0 is the lowest priority and 7 is the highest. 8 indicates field is not configured by HMS --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 8). Notification: None FAP Default value: 8 RMS Default value:0 RMS Property: SIB19-ARFCN-i-DOWNLINK-PRIORITY Management level: Deployment specific

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19.UTRA.ServingCell SIB19 Parameters - Serving Cell Info

Priority

Priority value of the serving cell. 0 is the lowest priority and 7 is the highest. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SERVING-CELL-PRIORITY Management level: Deployment specific

SPrioritySearch1

Threshold to trigger search high priority UTRA/EUTRA cells in SIB19 (CPICH RSCP). Unit in dB, by step of 2. (CPICH RSCP) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 4 RMS Default value:6 RMS Property: SERVING-CELL-PRIORITY-SEARCH-1 Management level: Deployment

SPrioritySearch2

Threshold to trigger search high priority UTRA/EUTRA cells in SIB19 (CPICH Ec/No). Unit in dB. By step of 1.



Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 4 RMS Default value:6 RMS Property: SERVING-CELL-PRIORITY-SEARCH-2 Management level: Deployment

ThreshServingLow

RSCP value. Unit in dB by step of 2. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SERVING-CELL-PRIORITY-THRES-SERVING-LOW Management level: Deployment specific

ThreshServingLow2

Ec/N0 value. Unit in dB. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SERVING-CELL-PRIORITY-THRES-SERVING-LOW2 Management level: Deployment specific

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19.EUTRA SIB19 Parameters - EUTRA Frequencies

EUTRAFreqsNumberOfEntries

Number of entries in EUTRAFreqs list. --- RMS Access: READ Type: Integer. (Range: 0 to 8). Notification: None FAP Default value: 0 RMS Default value:N/A Management level: N/A

EUTRAFreqsDeleteAllInstances

When this parameter is set to true, all instances of the EUTRAFreqs Instance object will be deleted. The parameter is locally cleared to false by the HNB. --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value: FALSE RMS Default value:FALSE RMS Property: SIB19-EUTRA-FREQS-DELETE-ALLINSTANCES Management level: N/A

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_SIB19.EUTRA.EUTRAFreqs SIB19 Parameters - EUTRA Frequencies Info

EARFCN

EARFCN of the downlink carrier frequency. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0



101 UBS-44-57-004

Object Parameter Description RMS Property: SIB19-EUTRA-FREQ-i-EARFCN-DOWNLINK Management level: Deployment specific

Priority

0 is the lowest priority and 7 is the highest. 8 indicates that value is not configured by HMS --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 8). Notification: None FAP Default value: 8 RMS Default value:0 RMS Property: SIB19-EUTRA-FREQ-i-EARFCN-DOWNLINK-PRIORITY Management level: Deployment specific

QRxLevMinEUTRA

RSRP value. Unit in dBm by step of 2. -21 indicates value not specifically configured from HMS --- RMS Access: READ/WRITE Type: Integer. (Range: -70 to -21). Notification: None FAP Default value: -21 RMS Default value:-60 RMS Property: SIB19-EUTRA-FREQ-i-QRX-LEVEL Management level: Deployment specific

ThreshXHigh

RSRP value. Unit in dB by step of 2. 32 indicates that value is not configured by HMS. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 32 RMS Default value:0 RMS Property: SIB19-EUTRA-FREQ-i-THRESH-HIGH Management level: Deployment specific

ThreshXLow

RSRP value. Unit in dB by step of 2. 32 indicates that value is not configured by HMS. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 32 RMS Default value:0 RMS Property: SIB19-EUTRA-FREQ-i-THRESH-LOW Management level: Deployment specific

MeasurementBandwidth

Measurement bandwidth information common for all neighbouring cells on the carrier frequency. It is defined by the parameter Transmission Bandwidth Configuration, NRB in TS 36.104. The values indicate the number of resource blocks over which the UE could measure. Default value is 6. Enumerated value [6, 15, 25, 50, 75, 100, invalid].6 indicates that value is not configured by HMS --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 6). Notification: None FAP Default value: 6 RMS Default value:0 RMS Property: SIB19-EUTRA-FREQ-i-MEASUREMENT-BANDWIDTH Management level: Deployment specific

EUTRADetection

TRUE means that the UE may detect the presence of a E-UTRA cell and report to NAS.2 indicates that the value is not configured by HMS ---



Object Parameter Description RMS Access: READ/WRITE Type: Integer. (Range: 0 to 2). Notification: None FAP Default value: 2 RMS Default value:FALSE RMS Property: SIB19-EUTRA-FREQUENCY-i-DETECTION Management level: Deployment specific

BlacklistedCellsPCI

Comma-separated list of strings. Each entry is a PCI of LTE cell for which access is prohibited (blacklisted) expressed in the value between 0 and 503. There can be a minimum of 0 entry to maximum of 16 entries. Empty string indicates 0 entry. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value:empty RMS Property: SIB19-EUTRA-FREQ-i-BLACKLISTED-CELL-PCI Management level: Deployment specific

MultipleFrequencyBandIndicator

Comma-separated list of strings. Each entry is a frequency band which the E-UTRA cells belong to, expressed in the value between 1 and 64. There can be a minimum of 0 entry to maximum of 8 entries. Empty string indicates 0 entry and there are no Multiple Bands for the particular EARFCN. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 24 characters). Notification: None FAP Default value: "" RMS Default value:empty RMS Property: SIB19-MULTIPLE-FREQ-i-BAND-INDICATOR Management level: Deployment specific

QqualMinEUTRA

RSRQ value. Unit in dB. -35 indicates that value is not configured by HMS --- RMS Access: READ/WRITE Type: Integer. (Range: -35 to -3). Notification: None FAP Default value: -35 RMS Default value: -35 RMS Property: SIB19-EUTRA-FREQ-i-QQUAL-MIN Management level: Deployment specific

ThreshXHigh2

RSRQ value. Unit in dB. 32 indicates that value is not configured by HMS. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 32 RMS Default value: 32 RMS Property: SIB19-EUTRA-FREQ-i-THRESH-HIGH-2 Management level: Deployment specific

ThreshXLow2

RSRQ value. Unit in dB. 32 indicates that value is not configured by HMS. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 32



103 UBS-44-57-004

Object Parameter Description RMS Default value: 32 RMS Property: SIB19-EUTRA-FREQ-i-THRESH-LOW-2 Management level: Deployment specific

Table 41 SIB19

4.9.3.2 Extensions to Cell Level Configuration

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP

This object contains parameters relating to the cell level configuration for FDD mode FAP.

X_UBIQUISYS_COM_HSUPAEnable

Enables or disables HSUPA in the cell Works in the same way as HSEnable but this applies to HSUPA --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value: N/A Management level : Default

X_UBIQUISYS_COM_TargetRNCRelease

This controls the maximum 3GPP specification version which can be used for the construction of srncRelocation Source-to-Target RNC container. Note: If a RAB Combination requires a higher release version than this parameter allows, then the handout will be blocked. - REL_99 - REL_4 - REL_5 - REL_6 - REL_7 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "REL_6" RMS Defalut value: “REL_6” RMS Property: RNC-TARGET-RELEASE-NUMBER Management level : Deployement specific or Customer

Table 42 Extensions to Cell Level Configuration



4.9.4 Cell Selection

As Mobile Network Operators have different deployment strategies2 it is not possible to engineer one set of cell selection and reselection parameter values that fits all deployments. For the purpose of this analysis the deployment of femtocells can generally be classified under 3 broad categories:

• Category A: Co-channel femtocell deployment – femtocells deployed on same carrier a macro network, relying on intra frequency cell reselection to rove between femto layer and macro layer.

• Category B: Dedicated Channel femtocell deployment – femtocells deployed on separate carrier to macro network, relying on inter frequency cell reselection to rove between the femto layer and macro layer.

• Category C: HCS-enabled deployment – femtocells rely on having a higher priority than the macro layer to enable UEs to rove in and rove out reliably.

The sections that follow highlight the key points to take into consideration while setting up the cell selection and reselection parameters for macro network and HNBs for each of the 3 categories introduced above.

Release note on QualityMeasureCPICH: As of R3.x only CPICH Ec/No is supported for QualityMEasureCPICH. CPICH RSCP will be supported in a later release. Consequently the guidelines below assume CPICH Ec/No reselection criteria.

4.9.4.1 Category A: Co-channel Femtocell Deployment

In a co-channel deployment, the HNB’s DL power management feature will aim to limit the coverage of the HNB to within the residence it is deployed in. This is achieved by ensuring that the HNB’s coverage is dominant over the co-channel macro coverage inside the residence while at the same time minimising leakage outside the residence.

The co-channel DL power management will set the HNB power such that the HNB CPICH RSCP will be equal to the macro network CPICH RSCP at the periphery of the residence containing the HNB. As CPICH Ec/No = CPICH RSCP/RSSI and RSSI will be the same on a given carrier, it follows that the CPICH Ec/No of the macro and femto layer should also be identical at the femtocell periphery. This, as well as the existing mobility settings in the macro network can be used to guide the settings of the rove in and rove out mobility settings on the femto layer as outlined in the next 2 sections.

4.9.4.1.1 Co-channel Rove-in

As the macro network is already in place it is expected that only the Qoffsets,n3 mobility parameter associated with the femtocell scrambling codes will be added on the macro network side.

As a guide to setting the Qoffsets,n parameter consider the following analysis. The UE will continuously rank its current serving cell against measured cells (as long as they fulfil the ranking criteria). Assuming that the macro network Sintrasearch threshold and Qqualmin have been set to an appropriate level such that UE measurements are already in progress when the UE enters the HNB coverage area, as the UE moves closer to the femto and experiences a stronger femto signal it will get to a point where just before reselection the macro and the femto will have an equal ranking. For example, given a typical value of Qhyst-macro of 2dB on the macro this implies that Qoffset-

femto for the femtocells should be set at -2dB4 or more.

Objective:

( ) dBQQRR macromeasfemtomeaswhen

macrofemto 0.. ≥− →>

2 e.g. which frequencies support Rel 99 and/or HSPA, which frequencies support femtocells and which frequencies just support the macro layer, which frequencies the UEs camps on by default, is HCS supported? etc. 3 This is a 3GPP IE that is entered in SIB 11 against the primary scrambling code of each neighbour UMTS Base Station in SIB 11 4 Note this parameters in units of 2dBs therefore odd values are not possible



105 UBS-44-57-004

Which is equivalent to:

( ) ( )( ) ( )

( )femtooffsetmacrohyst

femtooffsetmacrohystmacromeasfemtomeas

macrohystmacromeasfemtooffsetfemtomeas

QQQQQQQQQQ

_.

_...

.._.

0 +>+>−+>−

Therefore we need to set Qoffset-femto such that:

( )macrohystfemtooffeset QQ ._ −<

Equation 1: Co-channel rove-in from macro to femto

4.9.4.1.2 Co-channel Sintrasearch based Rove Out

To avoid ping ponging between the macro and femto, the femtocell rove out settings should take into account the femtocell rove in settings on the macro network. The key points to take into account include

The HNB has a default cell boundary of CPICH Ec/No of -16dB, hence It is desirable to make the femtocell sticky up to (but no more) femtocell CPICH signal quality levels of around Ec/No of -16dB otherwise the UE will likely be out of range of the femto common control channels. The rove out region from Femto to macro should be beyond the rove in region as an overlap in rove in/rove out regions could cause the Femto UE to ping pong between the macro and Femto layer.

Table 43 provides guidelines for cell resection parameters when femtocells are deployed co-channel without HCS.

Table 43: Femtocell reselection parameters in co-channel deployment without HCS

4.9.4.2 Category B: Dedicated Channel Femtocell Deployment

In a dedicated channel deployment the macro layer pilot signal quality (CPICH Ec/No) levels could still be very high within the femtocell coverage area and likewise the femtocell pilot signal quality (CPCIH Ec/No) could also be very good also in areas outside the residence. Therefore in this case the limit of performance of the UE with respect to the femtocells’ pilot signal quality (CPICH Ec/No) as well as the existing mobility settings in the macro network should be used to guide settings the rove in and rove out parameters on the femto layer. In addition, as



the macro signal may still be good within the femto coverage area, it implies that the macro layer SinterSearch threshold should be set such that the UE is making measurements even when the macro signal quality is good. However, to minimise any impacts to UE battery life it is recommended the Sintersearch threshold should be set such that the UE is making measurements when the serving macro cell CPICH Ec/No is no more than -6dBs.

In the dedicated channel deployment, the HNB DL power management will limit the coverage of the femtocell to within the residence it is deployed in, ensuring that the femto coverage is dominant over the noise floor of the UE while at the same time minimising leakage outside the residence.

Typically the co-channel DL power management will set the femtocell’s power such that the minimum femto cell pilot signal strength CPICH RSCP is greater than -105dBm and the CPICH Ec/No is greater than -10dB within the home. Though the CPICH Ec/No would be expected to drop below this value as a user exits the home, the roll-off in CPICH Ec/No has in general been found to be more gradual when there is no surrounding macro layer or femto cell interference.

This, as well as the existing mobility settings in the macro network can be used to guide the settings of the rove in and rove out mobility settings on the femto layer as shown in the next 2 sections.

4.9.4.2.1 Dedicated channel Rove-in

It is expected that only the mobility parameters Qoffset s,n associated with the femtocell scrambling codes can be influenced on the macro network side, and all other mobility parameters are given. As a guide to setting the Qoffset s,n parameter consider the following analysis. The UE will continuously rank its current serving cell against measured cells (as long as they fulfil the ranking criteria). Assuming that the macro network Sintersearch threshold and Qqualmin have been set to an appropriate level such that UE measurements are taking place as the UE enters the coverage area of the femtocell, then it is recommended that the Qoffset value of the femtocells on the macro be set to at least 8dB below the macro Qhyst value:

8._ −≤ macrohystfemtooffset QQ

Equation 2: Co-channel rove in from macro to femto

4.9.4.2.2 Dedicated channel Sintrasearch based Rove Out

In a similar fashion to the co-channel rove out, the femtocell rove out settings should be made taking into account the femtocell rove in settings on the macro network. The key points to take into account when setting the rove out parameters of the Femto cell are:

The HNB has a default cell boundary of CPICH Ec/No of -16dB, hence it is desirable to make the femtocell sticky up to (but no more) femtocell signal quality (CPICH Ec/No) levels of around -16dB otherwise the UE will likely be out of range of the femto common control channels. The rove out region from Femto to macro should be beyond the rove in region as an overlap in rove in/rove out regions could cause the femto UE to ping pong between the macro and femto layer.

Table 44 highlights the deviation from the guidelines provided in Table 43 for cell reselection parameters applicable when femtocells are deployed co-channel without HCS.

Table 44: Femtocell reselection parameters in co-channel deployment without HCS

4.9.4.3 Category C: HCS-Enabled Femtocell Deployment



107 UBS-44-57-004

HCS has the advantage of being able to prioritise the femtocell population over the macro network firstly by ensuring that when inter-cell measurements take place they always measure the scrambling codes of the femtocell population irrespective of the cell quality of the serving cell and secondly placing a higher priority on the femtocell population when ranking the femto cells. 4.9.4.3.1 HCS Rove-in

From macro layer perspective, integrating femtocells into a HCS network will require entries to be made for the femtocell scrambling codes with at least the following properties:

Femto HCS priority level must be greater than macro HCS priority level Qhcs,n for the femto should be such that H criterion (Qmeas,n - Qhcs,n > 0 ) is always passed when the UE enters the coverage area of the femto and the femto signal quality can support connected mode services. However, the rove in region should be further in than the rove out region to avoid ping ponging between the macro and Femto. 4.9.4.3.2 HCS Rove Out

The femtocell rove out settings should be made taking into account the femtocell rove in settings on the macro network. The key points to take into account when setting the rove out parameters of the femtocell:

Macro HCS priority level must be less than femto HCS priority level. It is desirable to make the femto cell sticky up to femto cell signal quality (CPICH Ec/No) levels of around -16dB, hence around this point the femto cell should fail the H criterion (Qmeas,n - Qhcs,n > 0 ) and no longer consider the femto for reselection. The rove out region from femto to macro should be beyond the rove in region as an overlap in rove in/rove out regions could cause the Femto UE to ping pong between the macro and femto layer

In addition to parameters in Table 43 and Table 44 (depending on whether the femtocell deployment is on a shared or dedicated channel), the parameters listed in section 4.9.4.6 provide default guidelines for parameters associated with HCS. In the event that HCS should be enabled then the value of UseOfHCS should be changed from the default value of 0 (HCS disabled) to 1 (HCS enabled).

4.9.4.4 Overview of Intra/Inter Frequency Cell Reselection

The algorithm for cell reselection to be used by a UE in a UTRAN cell is defined in section 5.2.6.1 of 3GPP TS 25.304. The serving cell broadcasts neighbour cell lists (System Information Block (SIB) 11 for idle mode and SIB 12 for connected mode). The lists may include UTRAN intra-frequency neighbours, UTRAN inter-frequency neighbours, and GSM neighbours. Only these cells are considered by the UE for the purpose of the cell reselection procedure.

The basic principle behind cell reselection is as follows:

The decision to start cell reselection is triggered by a measurement. This is dependant on the absolute signal quality (e.g. CPICH Ec/No and/or CPICH RSCP) quality AND absolute signal level. The relative CPICH Ec/No quality of the femtocell versus the macro layer. This determines the relative ranking of the femtocell versus the macro layer.

For FDD the cell selection criterion S used for cell reselection is fulfilled when the following two criteria are met:

Where:

• Squal is typically the measurement of signal quality of the serving cell (either RSCP or CPICH Ec/No) and details of this criteria is provided in the following paragraphs

• Srxlev is essentially a measure of signal level of the serving cell and is there to ensure that it meets a minimum criteria. Typically Qrxlevmin is chosen so that this cell reselection criteria is always met.

Srxlev > 0

AND

Squal > 0



Where:

Squal Cell Selection quality value (dB)

Srxlev Cell Selection RX level value (dB)

Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) for FDD cells.

Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) and the averaged received signal level for GSM cells (dBm).

Qqualmin Minimum required quality level in the cell (dB).

Qrxlevmin Minimum required RX level in the cell (dBm)

Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB) UE_TXPWR_MAX_RACH

Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm)

P_MAX Maximum RF output power of the UE (dBm)

Table 45: Definition of cell reselection parameters

The UE continuously makes a measurement of the serving cell’s quality. This is defined as the parameter Squal = Qqualmeas – Qqualmin where:

• Qqualmeas is the measured received quality in terms of the serving cell’s CPICH Ec/No • Qqualmin is the minimum received signal quality defined for the cell. This quantity is broadcast by the

serving cell in a broadcast information massage. For example, if this value is -15dB, then this is the minimum acceptable signal quality for that cell.

A neighbour cell measurement is triggered if any of the following conditions are met:

• If Squal≤ Sintrasearch: The UE will perform an intra-frequency measurement based on the neighbour cell list received from the serving cell.

• If Squal≤ Sintersearch The UE will perform an inter-frequency measurement based on the neighbour cell list received from the serving cell.

• if Squal≤ SsearchRATm: The UE will perform a measurement on the list of cells of RAT type m that the UE received from the serving cell.

Sintrasearch, Sintersearch, and SsearchRATm are all communicated by the serving cell in SIB3/4 broadcast messages.

4.9.4.5 Measurement Rules for Cell Re-selection when HCS is used

The measurement rules below apply in Idle, URA_PCH, CELL_PCH states. In Idle, URA_PCH, CELL_PCH and CELL_FACH states the UE shall only consider those cells the UE is mandated to measure according to the measurement rules below as measured cells in the cell reselection criteria.

For FDD the cell selection criterion S used for cell reselection is fulfilled when the following two criteria are met:

Where:

• Squal is typically the measurement of signal quality of the serving cell (either RSCP or CPICH Ec/No) and details of this criteria is provided in the following paragraphs

• Srxlev is a measure of signal level of the serving cell and is there to ensure that it meets a minimum criteria. Typically Qrxlevmin

Srxlev,s > 0 AND Squal > 0

Srxlev = Qrxlevmeas – Qrxlevmin - Pcompensation



109 UBS-44-57-004

Where:

Squal Cell Selection quality value (dB)

Srxlev Cell Selection RX level value (dB)

Qqualmeas Measured cell quality value. The quality of the received signal expressed in CPICH Ec/N0 (dB) for FDD cells.

Qrxlevmeas Measured cell RX level value. This is received signal, CPICH RSCP for FDD cells (dBm) and the averaged received signal level for GSM cells (dBm).

Qqualmin Minimum required quality level in the cell (dB).

Qrxlevmin Minimum required RX level in the cell (dBm)

Pcompensation max(UE_TXPWR_MAX_RACH – P_MAX, 0) (dB)

UE_TXPWR_MAX_RACH Maximum TX power level an UE may use when accessing the cell on RACH (read in system information) (dBm)

P_MAX Maximum RF output power of the UE (dBm)

Table 46: Definition of cell reselection parameters

The UE continuously makes a measurement of the serving cell’s quality. This is defined as the parameter Squal= Qqualmeas – Qqualmin where:

• Qqualmeas is the measured received quality in terms of the serving cell’s CPICH Ec/No • Qqualmin is the minimum received signal quality defined for the cell. This quantity is broadcast by the

serving cell in a broadcast information massage. For example, if this value is -15dB, then this is the minimum acceptable signal quality for that cell.

A neighbour cell measurement is triggered if any of the following conditions are met:

• if Squal≤ Sintrasearch : The UE will perform an intra-frequency measurement based on the neighbour cell list received from the serving cell.

• if Squal≤ Sintersearch : The UE will perform an inter-frequency measurement based on the neighbour cell list received from the serving cell.

• if Squal≤ SsearchRATm: The UE will perform a measurement on the list of cells of RAT type m that the UE received from the serving cell.

If the system information broadcast in the serving cell indicates that HCS is used, then for intra-frequency and inter-frequency measurements, the UE would perform the following measurement process5:

• Calculate Squal and Srxlev and apply the following rules:

5 The following is a cut down version of the cell measurement procedure to reflect the UbiquiSys implementation (no high mobility or MBBS)

Srxlev,s = Qrxlevmeas – Qrxlevmin - Pcompensation



IF (Srxlevs <= SsearchHCS) or (if FDD and Squal <= Sintersearch) THEN

measure on all intra-frequency and inter-frequency cells.

ELSE

IF (Squal > Sintrasearch) THEN

measure on all intra-frequency and inter-frequency cells, which have higher HCS priority level than the serving cell

ELSE

measure on all intra-frequency and inter-frequency cells, which have equal or higher HCS priority level than the serving cell

ENDIF

ENDIF



111 UBS-44-57-004

When serving cell belongs to a hierarchical cell structure, the UE follows these rules for Inter-RAT measurements:

Following the triggering of the measurements the cell reselection criteria apply. The following cell re-selection criteria are used for intra-frequency cells, inter-frequency cells and inter-RAT cells.

The quality level threshold criterion H for hierarchical cell structures is used to determine whether prioritised ranking according to hierarchical cell re-selection rules apply and for the Cisco product the following applies:

The cell-ranking criterion R is defined by:

If HCS is not used in the serving cell the UE performs ranking of all cells that fulfil the Squal criterion among all the measured cells. However, if HCS is used in the serving cell the UE performs ranking of all cells that fulfil the Squal criterion on all measured cells, that have the highest HCS priority among those cells that fulfil the criterion H >= 0 and all measured cells, not considering HCS priority levels, if no cell fulfil the criterion H >= 0. The cell with the highest ranking is selected.

4.9.4.6 RSCP Based Handover The feature is covered in the following document:

• UBS-44-20-030 RSCP Based Handover

IF (Srxlevs <= SHCS,RATm) or (Squal <= SSearchRATm) THEN

UE measures on all inter-RATm cells.

ELSE

IF (Squal > Slimit,SearchRATm) THEN

UE may choose to not measure neighbouring cells in RAT "m".

ELSE

UE shall measure on all neighbouring cells in RAT "m", which have equal or higher HCS priority level than the serving cell

ENDIF

ENDIF

Hs = Qmeas,s – Qhcss Hn = Qmeas, n - Qhcsn

Rs = Q meas,s + Qhysts

Rn = Q meas,n – Qoffsets,n



4.9.4.7 Cell Selection Parameters

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.CellSelection

This object contains parameters related to cell selection and reselection.

QualityMeasureCPICH Which mechanism to use when doing CPICH quality measurements. 3GPP-TS.25.331 Section 10.3.7.47 Enumeration of: - "Ec/No" - "RSCP" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Ec/No" RMS Default value;N/A RMS Property:N/A Management level: Default

QqualMin Minimum required quality measure, specified in dB. 3GPP-TS.25.331 Section 10.3.2.3 and Section 10.3.2.4 This value is only meaningful if QualityMeasureCPICH has the value Ec/No and it MUST otherwise be ignored. --- RMS Access: READ/WRITE Type: Integer. (Range: -24 to 0). Notification: None FAP Default value: -18 RMS Default value: -18 RMS Property: FC-CELL-SELECTION-Q-QUAL-MIN Management level: Default

QqualMinOffset Offset for QqualMin specified in dB. 3GPP-TS.25.331 Section 10.3.2.3 This value is only meaningful if QualityMeasureCPICH has the value Ec/No and it MUST otherwise be ignored. Value of 0 is allowed for Ubiquisys FAPs and means that this IE is omitted from SIB3 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16). Notification: None FAP Default value: 0 RMS Default value;N/A RMS Property:N/A Management level: Default

X_UBIQUISYS_COM_QqualMinMacroBias Reselection QqualMin bias to apply for all UMTS macro neighbours (dB). UMTS Macro Qqualmin (advertised by FAP on SIB 11) = Femto QqualMin + QqualMinMacroBias --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: FC-CELL-SELECTION-Q-QUAL-MIN-MACRO-BIAS Management level: Default

QRxLevMin Minimum required RX level in the cell, specified in dBm. 3GPP-TS.25.331 Section 10.3.2.3 Only odd values are valid, use of an even value MUST be rejected by the CPE.



113 UBS-44-57-004

This value is only meaningful if QualityMeasureCPICH has the value RSCP and it MUST otherwise be ignored. --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to -25). Notification: None FAP Default value: -111 RMS Default value: -111/RF Profile v2.3 RMS Property: FC-CELL-SELECTION-Q-RX-LEV-MIN Management level: Deployement specific

DeltaQRxLevMin Delta for the minimum required RX level in the cell, specified in dB. 3GPP-TS.25.331 Section 10.3.2.3 and Section 10.3.2.4 The actual value of QRxLevMin = QRxLevMin + DeltaQRxLevMin This value is only meaningful if QualityMeasureCPICH has the value RSCP and it MUST otherwise be ignored. Value of 0 is allowed for Ubiquisys FAPs and means that this IE is omitted from SIB3 Only even values are valid --- RMS Access: READ/WRITE Type: Integer. (Range: -4 to 0). Notification: None FAP Default value: 0 RMS Default value;N/A RMS Property:N/A Management level: Default

QRxLevMinOffset Offset for QRxLevMin, specified in dB. 3GPPTS.25.331 Section 10.3.2.3 This value is only meaningful if QualityMeasureCPICH has the value RSCP and it MUST otherwise be ignored. Value of 0 is allowed for Ubiquisys FAPs and means that this IE is omitted from SIB3 Only even values are valid --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16). Notification: None FAP Default value: 0 RMS Default value: 0/RF Profile v2.3 RMS Property:N/A Management level: Default

X_UBIQUISYS_COM_QRxLevMinUMTSMacroBias

Reselection QrxLevMin bias to apply for all UMTS macro neighbours (dB). UMTS Macro Qrxlevmin (advertised by FAP on SIB 11) = Femto QrxLevmin + QrxLevMinUMTSMacroBias. --- RMS Access: READ/WRITE Type: Integer. (Range: -90 to 90). Notification: None FAP Default value: 0 RMS Default value: 0/RF Profile v2.3 RMS Property: UMTS-QRX-MIN-MACRO-BIAS Management level: Deployment specific or Customer

X_UBIQUISYS_COM_QRxLevMinGSMMacroBias

Reselection QrxLevMin bias to apply for all GSM macro neighbours (dB). UMTS Macro Qrxlevmin (advertised by FAP on SIB 11) = Femto QrxLevmin + QrxLevMinGSMMacroBias. --- RMS Access: READ/WRITE Type: Integer. (Range: -90 to 90). Notification: None FAP Default value: 10



RMS Default value: 10/RF Profile v2.3 RMS Property : GSM-QRX-MIN-MACRO-BIAS Management level: Deployment specific or Customer

QHyst1s GSM and FDD Cell reselection hysteresis 1. 3GPPTS.25.331 Section 10.3.2.3 Only even values are valid, use of an odd value MUST be rejected by the CPE. This value is only meaningful if QualityMeasureCPICH has the value RSCP and it MUST otherwise be ignored. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 40). Notification: None FAP Default value: 2 RMS Default value: 2/RF Profile v2.3 RMS Property : FC-CELL-SELECTION-Q-HYST-1S Management level: Deployment specific or Customer

QHyst2s FDD Cell reselection hysteresis 2. 3GPP-TS.25.331 Section 10.3.2.3 Only even values are valid, use of an odd value MUST be rejected by the CPE. This value is only meaningful if QualityMeasureCPICH has the value CPICH Ec/N0 and it MUST otherwise be ignored. By default when QHyst1s is set and QHyst2s is not, then the value for QHyst2s should match the value of QHyst1s. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 40). Notification: None FAP Default value: 2 RMS Default value: 2/RF Profile v2.3 RMS Property : FDD-CELL-RESELECTION-HYSTERESIS Management level: Deployment specific or Customer

X_UBIQUISYS_COM_Qoffset1UMTSMacro Reselection Qoffset1 parameter to apply for all UMTS macro neighbours (dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 50). Notification: None FAP Default value: 4 RMS Default value: 2/RF Profile v2.3 RMS Property: Q-OFFSET1-UMTS-MACRO Management level: Deployment specific or Customer

X_UBIQUISYS_COM_Qoffset2UMTSMacro Reselection Qoffset2 parameter to apply for all UMTS macro neighbours (dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 50). Notification: None FAP Default value: 4 RMS Default value: 2/RF Profile v2.3 RMS Property: FC-MACRO-QOFFSET2-IDLE Management level: Deployment specific or Customer

X_UBIQUISYS_COM_Qoffset1GSMMacro Reselection Qoffset1 parameter to apply for all GSM macro neighbours (dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 50). Notification: None FAP Default value: 6 RMS Default value: 6/RF Profile v2.3 RMS Property: FC-CELL-SELECTION-Q-OFFSET1-GSM-MACRO



115 UBS-44-57-004

Management level: Deployment specific or Customer TReselections A member of the set of parameters used for cell

reselection functionality. A UE triggers the reselection of a new cell if the cell reselection criteria are fulfilled during the time interval in seconds. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 31). Notification: None FAP Default value: 2 RMS Default value: 2/RF Profile v2.4 Modify RMS Property: CELL-SELECTION-TRESELECTIONS Management level: Deployment specific

SIntrasearch A member of the set of parameters used for cell reselection functionality. Defines the threshold for intra-frequency measurements, and for the HCS measurement rules. Only even values are valid, use of an odd value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -32 to 20). Notification: None FAP Default value: 8 RMS Default value: 8/RF Profile v2.3 Modify RMS Property: FC-IDLE-SINTRASEARCH Management level: Deployment specific or Customer

SIntersearch A member of the set of parameters used for cell reselection functionality. Defines the threshold for inter-frequency measurements, and for the HCS measurement rules. Only even values are valid, use of an odd value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -32 to 20). Notification: None FAP Default value: 4 RMS Default value: 8/RF Profile v2.3 Modify RMS Property: FC-IDLE-SINTERSEARCH Management level: Deployment specific or Customer

SSearchHCS A member of the set of parameters used for cell reselection functionality. Defines the threshold for intrafrequency and interfrequency measurement rules in HCS. Below this limit in the serving cell, the UE initiates measurements of all intrafrequency and interfrequency neighbouring cells of the serving cell. Only odd values are valid, use of an even value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -105 to 91). Notification: None



FAP Default value: -85 RMS Default value:-85 RMS Property: CELL-SELECTION-SEARCH-HCS Management level: Solution or Customer

SSearchRAT A member of the set of parameters used for cell reselection functionality. Defines the RAT (GSM) specific threshold for inter-RAT measurement rules. Only even values are valid, use of an odd value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -32 to 20). Notification: None FAP Default value: 4 RMS Default value: 4/RF Profile v2.4 RMS Property: CELL-SELECTION-SSEARCHRAT Management level: Deployment specific or Customer

SHCSRAT A member of the set of parameters used for cell reselection functionality. Defines the RAT (GSM) specific threshold for inter-RAT measurement rules in HCS. Only odd values are valid, use of an even value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -105 to 91). Notification: None FAP Default value: 1 RMS Default value: 1/RF Profile v2.3 RMS Property: FC-CELL-SELECTION-SHCS-RAT Management level: Deployment specific or Customer

SLimitSearchRAT A member of the set of parameters used for cell reselection functionality. Defines the threshold for skipping inter-RAT measurement rules in HCS. Above this RAT (GSM) specific threshold in the serving UTRA cell, the UE does not need to perform any inter-RAT measurements. Only even values are valid, use of an odd value MUST be rejected by the CPE. Parameter defined in SIB3 3GPP-TS.25.331 Section 10.3.2.3. --- RMS Access: READ/WRITE Type: Integer. (Range: -32 to 20). Notification: None FAP Default value: 4 RMS Default value: 4/RF Profile v2.3 RMS Property: FC-CELL-SELECTION-SLIMIT-SEARCH-RAT Management level: Deployment specific or Customer

QHCS A member of the set of parameters used for cell reselection functionality. Defines the quality threshold levels for applying prioritised hierarchical cell reselection. 3GPP-TS.25.331 Section 10.3.7.12 and Section 10.3.7.54a Note: For Ubiquisys FAPs this is only used for the current cell (i.e. in SIB3) ---



117 UBS-44-57-004

RMS Access: READ/WRITE Type: Integer. (Range: 0 to 99). Notification: None FAP Default value: 20 RMS Default value:20 RMS Property: FC-CELL-SELECTION-QHCS Management level: Solution or Customer

X_UBIQUISYS_COM_UMTSMacroQHCS Quality threshold for applying prioritised HCS for all UMTS macro neighbours. Qhcs is mapped from CPICH Ec/No or CPICH RSCP - see 25.331 10.3.7.54a --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 99). Notification: None FAP Default value: 12 RMS Default value:12 RMS Property: FC-CELL-SELECTION-UMTS-MACRO-QHCS Management level: Solution or Customer

X_UBIQUISYS_COM_GSMMacroQHCS Quality threshold for applying prioritised HCS for all GSM neighbours. Qhcs is mapped from CPICH Ec/No or CPICH RSCP - see 25.331 10.3.7.54a --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 99). Notification: None FAP Default value: 12 RMS Default value:12 RMS Property: FC-CELL-SELECTION-GSM-MACRO-QHCS Management level: Solution or Customer

UseOfHCS A member of the set of parameters used for cell reselection functionality. Indicate whether HCS is used in this cell or not. 3GPP-TS.25.331 Section 10.3.7.47 --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: FC-CELL-SELECTION-USE-HCS Management level: Default

HCSPrio A member of the set of parameters used for cell reselection functionality. Defines the HCS priority of this cell. 3GPP-TS.25.331 Section 10.3.7.12 Note: For Ubiquisys FAPs this is only used for the current cell (i.e. in SIB3) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 2 RMS Default value:2 RMS Property: FC-CELL-SELECTION-HCS-PRIO Management level: Solution or Customer

X_UBIQUISYS_COM_UMTSMacroHCSPrio HCS priority of all UMTS macro neighbours. 0 is lowest priority --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 1 RMS Default value:1 RMS Property: FC-CELL-SELECTION-UMTS-MACRO-HCS-



Table 47 Cell Selection Parameters

PRIO Management level: Solution or Customer

X_UBIQUISYS_COM_GSMMacroHCSPrio HCS priority of all GSM macro neighbours. 0 is lowest priority --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-CELL-SELECTION-GSM-MACRO-HCS-PRIO Management level: Solution or Customer

UETxPwrMaxRACH A member of the set of parameters used for cell reselection functionality. Defines the maximum transmit power level, specified in dBm, that an UE may use when accessing the cell on RACH. Used to calculate Pcompensation, which is: max(UE_TXPWR_MAX_RACH - P_MAX, 0), where UE_TXPWR_MAX_RACH is UETxPwrMaxRACH and P_MAX is the max transmit power for a UE. 3GPP-TS.25.331 Section 10.3.2.3, 3GPPTS.25.304 Section 5.2.3 Note that Ubiquisys FAPs will automatically set this variable if Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig is enabled --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 33). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: UETX-PWR-MAX-RACH Management level: Default

X_UBIQUISYS_COM_Qoffset1UMTSFemto Reselection Qoffset1 parameter to apply for all UMTS femto neighbours (dB) [Enterprise mode only] --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 50). Notification: None FAP Default value: 2 RMS Default value:0 RMS Property: FC-CELL-SELECTION-Q-OFFSET1-UMTS-FEMTO Management level: Deployment specific or Customer

X_UBIQUISYS_COM_Qoffset2UMTSFemto Reselection Qoffset2 parameter to apply for all UMTS femto neighbours (dB) [Enterprise mode only] --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 50). Notification: None FAP Default value: 2 RMS Default value:0 RMS Property: FC-CELL-SELECTION-Q-OFFSET2-UMTS-FEMTO Management level: Deployment specific or Customer



119 UBS-44-57-004

4.9.5 RRC Timers

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RRCTimers

This object contains parameters related to miscellaneous RRC timers and constants.

T312 Timer measured in seconds. Defined in SIB1 3GPPTS.25.331 Section 13.1 and Section 10.3.3.43. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 1 RMS Default value:1 RMS Property: RRCTIMERS-T312 Management level: Solution or Customer

T313 Timer measured in seconds. Defined in SIB1 3GPPTS.25.331 Section 13.1 and Section 10.3.3.43. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 3 RMS Default value:3 RMS Property: RRCTIMERS-T313 Management level: Solution or Customer

T317 Timer measured in seconds. Defined in SIB1 3GPPTS.25.331 Section 13.1 and Section 10.3.3.43. Not used by Ubiquisys Enumerations of: - "0" - "10" - "30" - "60" - "180" - "600" - "1200" - "1800" --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 7

T323 Timer measured in seconds. Defined in SIB1 3GPPTS.25.331 Section 13.1 and Section 10.3.3.43. Enumerations of: - "0" - "5" - "10" - "20" - "30" - "60" - "90" - "120" --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A



Object Parameter Description Management level: Default

N302 Counter. Defined in SIB1 3GPP-TS.25.331 Section 13.1 and Section 10.3.3.43. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 3 RMS Default value:3 RMS Property: RRCTIMERS-N302 Management level: Solution or Customer

X_UBIQUISYS_COM_N308 Number of times to restransmit RRC Connection Release Complete. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 8). Notification: None FAP Default value: 3 RMS Default value:N/A RMS Property:N/A Management level: Default

N313 Counter. Defined in SIB1 3GPP-TS.25.331 Section 13.1 and Section 10.3.3.43. Enumerations of: - "1" - "2" - "4" - "10" - "20" - "50" - "100" - "200" --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 4 RMS Default value:20 (Corresponds to Enum 4) RMS Property: RRCTIMERS-N313 Management level: Solution or Customer

WaitTime Time period defined in seconds that the UE has to wait before repeating the rejected procedure. This is an IE used when sending RRC connection reject, redirecting the requesting UE to another frequency. 0 indicates that repetition is not allowed. 3GPP-TS.25.331 Section 10.3.3.50. For Ubiquisys FAPs this parameter is only used when rejecting an unauthorised UE --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 15 RMS Default value:15 RMS Property: RRCTIMERS-WAIT-TIME Management level: Solution or Customer

X_UBIQUISYS_COM_CTCHReleaseTriggerDelay

Time in ms between sending last CTCH mesaage and releasing the CTCH --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10000). Notification: None FAP Default value: 3000



121 UBS-44-57-004

Object Parameter Description RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

X_UBIQUISYS_COM_CTCHSIBUpdateDelay

Time in ms to allow UEs to read updated SIBs before FAP starts sending ctch data --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10000). Notification: None FAP Default value: 2000 RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

Table 48 RRC Timers

4.9.6 DRX

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.DRX

This object contains parameters related to DRX parameters.

DRXCycleLengthCoefficientCS Defines the DRX cycle length coefficient for CS domain to optimize paging in idle mode. Defined in SIB1 3GPP-TS.25.331 Section 10.3.3.6. DRXCycleLengthCoefficientCS refers to 'k' in the formula as specified in 3GPP-TS.25.304, Discontinuous reception. Used by the CN CS domain to count paging occasions for discontinuous reception in Idle Mode. The duration of the DRX cycle is 2^k frames, where 'k' is the used DRX cycle length coefficient for CN. --- RMS Access: READ/WRITE Type: Integer. (Range: 6 to 9). Notification: None FAP Default value: 7 RMS Default value: 7 / RF Profile v. 2.4 Modify RMS Property: DRX-CYCLE-LENGTH-CO-EFFICIENT-CS Management level: Deployment

DRXCycleLengthCoefficientPS Defines the DRX cycle length coefficient for PS domain to optimize paging in idle mode. Defined in SIB1 3GPP-TS.25.331 Section 10.3.3.6. DRXCycleLengthCoefficientPS refers to 'k' in the formula as specified in 3GPP-TS.25.304, Discontinuous reception. Used by the CN PS domain to count paging occasions for discontinuous reception in Idle Mode. The duration of the DRX cycle is 2^k frames, where 'k' is the used DRX cycle length coefficient for CN. --- RMS Access: READ/WRITE Type: Integer. (Range: 6 to 9). Notification: None FAP Default value: 7 RMS Default value: 7 / RF Profile v. 2.4 Modify RMS Property: DRX-CYCLE-LENGTH-CO-EFFICIENT-PS Management level: Deployment

UTRANDRXCycleLengthCoefficient Defines the DRX cycle length used by UTRAN to count paging occasions for discontinuous reception in Connected Mode. The duration of the DRX cycle is 2^k frames, where 'k' is the used DRX cycle length coefficient for UTRAN. UTRANDRXCycleLengthCoefficient SHOULD be used



Object Parameter Description by the UTRAN/FAP for UEs in Cell_PCH/Cell_FACH state. 3GPP-TS.25.331 Section 10.3.3.49 --- RMS Access: READ/WRITE Type: Integer. (Range: 3 to 9). Notification: None FAP Default value: 7 RMS Default value:7 RMS Property: UTRAN-DRX-CYCLE-LENGTH-CO-EFFICIENT Management level: Solution or Customer

Table 49 DRX

4.9.7 Power Control

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.PowerControl

This object contains parameters related to power control and RACH.

ConstantValue Used by the UE to calculate the initial output power, specified in dB, on PRACH according to the open loop power control procedure. Parameter in SIB5. 3GPP-TS.25.331 ection 10.3.6.11 --- RMS Access: READ/WRITE Type: Integer. (Range: -35 to -10). Notification: None FAP Default value: -18 RMS Default value:-18 RMS Property: FC-POWER-CONTROL-CONSTANT-VALUE Management level: Solution or Customer

PreambleRetransMax Used for the Uplink Common Channel. Defines the maximum number of preambles allowed in one preamble ramping cycle. PRACH Preamble Retrans Max is part of "PRACH power offset" which is part of "PRACH system information list". Parameter in SIB5. 3GPP-TS.25.331 Section 10.3.6.54 --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 64). Notification: None FAP Default value: 30 RMS Default value:30 RMS Property: FC-POWER-CONTROL-PREAMBLE-RE-TX-MAX Management level: Solution or Customer

MMax Maximum number of RACH preamble cycles. Defines how many times the PRACH preamble ramping procedure can be repeated before UE MAC reports a failure on RACH transmission to higher layers. Maximum number of RACH preamble cycles is part of "RACH transmission parameters" which is part of "PRACH system information list" which is part of SIB5. 3GPP-TS.25.331 Section 10.3.6.67 --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 32). Notification: None



123 UBS-44-57-004

Object Parameter Description FAP Default value: 10 RMS Default value:10 RMS Property: FC-POWER-CONTROL-MMAX Management level: Solution or Customer

NB01Min RACH random back-off lower bound. NB01Min is the lower bound of the waiting time in 10 millisecond increments (i.e. 1 corresponds to 10 ms and 50 corresponds to 500 ms). NB01Min is part of "RACH transmission parameters" which is part of "PRACH system information list" which is part of SIB5. 3GPP-TS.25.331 Section 10.3.6.67 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 50). Notification: None FAP Default value: 3 RMS Default value:3 RMS Property: FC-POWER-CONTROL-NB01MIN Management level: Solution or Customer

NB01Max RACH random back-off upper bound. NB01Max is the Upper bound of the waiting time in 10 millisecond increments (i.e. 1 corresponds to 10 ms and 50 corresponds to 500 ms). NB01Max is part of "RACH transmission parameters" which is part of "PRACH system information list" which is part of SIB5. 3GPP-TS.25.331 Section 10.3.6.67 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 50). Notification: None FAP Default value: 10 RMS Default value:10 RMS Property: FC-POWER-CONTROL-NB01MAX Management level: Solution or Customer

Table 50 Power Control

4.9.7.1 Power Control

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.PowerControl

This object contains parameters related to power control and RACH.

PowerRampStep Used for the Uplink Common Channel. Defines the Power ramp setup, specified in dB, on PRACH preamble when no acquisition indicator (AI) is detected by the UE. Parameter in SIB5. 3GPP-TS.25.331 Section 10.3.6.54 --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 8). Notification: None FAP Default value: 3 RMS Default value: 3 / RF Profile v. 2.4 Modify RMS Property: FC-POWER-RAMP-STEP Management level: Deployment

Table 51 Power Control





125 UBS-44-57-004

4.9.8 Intra Frequency Masurements 4.9.8.1 Parameters for Intra Frequency

Measurements

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas

This object contains parameters relating to the intra-freq HO control parameters.

MeasurementQuantity Defines the measurement quantity for intra-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: CPICH Ec/No CPICH RSCP Pathloss 3GPP-TS.25.331 Section 10.3.7.38 FAP does not support "pathloss" measurement quantitiy in this version. --- RMS Access: READ/WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "CPICH Ec/No" RMS Default value: CPICH Ec/No / RF Profile v. 2.3 RMS Property: CELL-CONFIG-INTRA-FREQ-MEAS-QUANTITY Management level: Deployment specific or Customer

IntraFrequencyEventIdentity Comma-separated list (maximum length 32) of strings. Each entry is an Event ID from the list of: 1a, 1b, 1c, 1d, 1e, 1f,1g, 1h, 1i Defines the identity of the event used to trigger UE reporting (in case of event-triggered reporting). 3GPP TS.25.331 Section 10.3.7.34 Since the FAP can determine this on its own, it might not be necessary to configure it. Note: Ubiquisys FAPs currently only support 1e and 1f for intra frequency macro handout and 1b,1c,1e and 1f for intra frequency HNB handout. If 1b,1c is added to this list then 1e, 1f must also be defined. Supported options: 1e,1f [default] 1b,1c,1e,1f All other string values will be treated as 1e,1f only If InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.MeasurementQuantity Is set to RSCP then the only supported value will be 1e,1f --- RMS Access: READ/WRITE Type: String. (Length: 0 to 32 characters). Notification: None FAP Default value: "1e,1f" RMS Default value: 1e / RF Profile Modify RMS Property: ALPHA-INTRA-FREQ-EVENT-IDENTITY Management level: Deployment

FilterCoefficient Defines the equivalent time constant of the low pass filter applied to the CPICH quality measurements. 3GPP-TS.25.331 Section 8.6.7.2 and Section 10.3.7.9 Enumerations of: - "0" - "1"



Object Parameter Description - "2" - "3" - "4" - "5" - "6" - "7" - "8" - "9" - "11" - "13" - "15" - "17" - "19" --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 14). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: System

TriggeringCondition2Event1e Comma-separated list of strings. Indicates which cells can trigger Event 1e. Each list item is an enumeration of: - "Active" - "Monitored" - "Active and Monitored" - "Detected" - "Detected and Monitored" 3GPP-TS.25.331 Section 14.1.2 and Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Active and Monitored" RMS Default value:N/A RMS Property:N/A Management level: System

TriggeringCondition1Event1f Comma-separated list of strings. Indicates which cells can trigger Event 1f. Each list item is an enumeration of: - "Active" - "Monitored" - "Active and Monitored" 3GPP-TS.25.331 Section 14.1.2 and Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Active and Monitored" RMS Default value:N/A RMS Property:N/A Management level: System

ReportingRangeEvent1b Defines a constant in the inequality criterion that needs to be satisfied for an Event 1b to occur. Actual values of the range are 0.0 to 14.5 dB in steps of 0.5 dB. The value of ReportingRangeEvent1b divided by 2 yields the actual value of the range. 3GPP-TS.25.331 Section 14.1.2 and Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4



127 UBS-44-57-004

Object Parameter Description RMS Default value:4 RMS Property: CELL-CONFIG-INTRA-FREQ-REPORTING-EVENT-1B Management level: System

TimeToTriggerEvent1b Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11(Corresponds to actual value 320) RMS Default value: 320 RMS Property: CELL-CONFIG-INTRA-FREQ-TIME-TRIGGER-EVENT-1B Management level: Default Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent1c Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 12 (Corresponds to actual value 640) RMS Default value: 640 RMS Property: CELL-CONFIG-INTRA-FREQ-TIME-TRIGGER-EVENT-1C Management level: Default Note: 0=0,1=10,2=20,3=40,etc.

WeightingFactorEvent1b Defines the weighting factor for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the weighting factor are 0.0 to 2.0 in steps of 0.1. The value of WeightingFactorEvent1b divided by 10 yields the actual value of the weighting factor. 3GPP-TS.25.331 Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 20). Notification: None FAP Default value: 10 RMS Default value:10 RMS Property: CELL-CONFIG-INTRA-FREQ-WEIGHTING-EVENT-1B Management level: Default

HysteresisEvent1e Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1e divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2



Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-HYSTERESIS-EVENT-1E Management level: Deployment specific or Customer

HysteresisEvent1f Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1f divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-HYSTERESIS-EVENT-1F Management level: Deployment specific or Customer

HysteresisEvent1b

Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1b divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 4 RMS Default value: 4 RMS Property: CELL-CONIFG-INTRA-FREQ-HYSTERESIS-EVENT-1B Management level: Default

HysteresisEvent1c

Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1c divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 8 RMS Default value: 8 RMS Property: CELL-CONIFG-INTRA-FREQ-HYSTERESIS-EVENT-1C Management level: Default

TimeToTriggerEvent1e Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64



129 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONFIG-INTRA-FREQ-TTT-EVENT-1E Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent1f Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 9 (Corresponds to actual value 200) RMS Default value: 200 / RF Profile v. 2.3 RMS Property: CELL-CONFIG-INTRA-FREQ-TTT-EVENT-1F Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

ThresholdUsedFrequencyEvent1e Defines the reporting threshold for intra-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.39. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB Pathloss has a range of 30 dB to 165 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 165). Notification: None FAP Default value: -9 RMS Default value: -9 / RF Profile v. 2.3 Modify RMS Property: CELL-CONFIG-INTRA-FREQ-1-THRESHOLD-EVENT-1E Management level: Deployment

ThresholdUsedFrequencyEvent1f Defines the reporting threshold for intra-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.39. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB Pathloss has a range of 30 dB to 165 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 165). Notification: None FAP Default value: -13 RMS Default value: -13 / RF Profile v. 2.3 Modify RMS Property: CELL-CONFIG-INTRA-FREQ-1-THRESHOLD-EVENT-1F



Object Parameter Description Management level: Deployment

X_UBIQUISYS_COM_MacroOffset Cell Individual Offset to apply to all Macro neighbours that are to be considered for the 1E/1F handout measurements. This allows the quality of a good/bad Macro to be varied relative to a good/bad Femto. (-10 .. +10 in steps of 0.5dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 0 RMS Default value: 0 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-MACRO-OFFSET Management level: Deployment specific or Customer

X_UBIQUISYS_COM_HandoutMargin1c The pilot quality of the target that triggers the 1c event has to be better than the 1e ThresholdUsedFrequencyEvent1e + HysteresisEvent1e by this margin before a handout will be triggered to this target because of event 1c. --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 4 RMS Default value:4 RMS Property: CELL-CONIFG-INTRA-FREQ-HANDOUT-MARGIN-1C Management level: System

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_IntraFreqMeas1

This object contains parameters relating to the optional second set of intra-freq HO control parameters.

Enable Enable the optional second set of intra-freq HO control parameters. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-ENABLE Management level: Deployment specific or Customer

HysteresisEvent1e Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1e divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 8 RMS Default value: 8 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-HYSTERESIS-EVENT-1E Management level: Deployment specific or Customer

HysteresisEvent1f Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1f divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2



131 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 8 RMS Default value: 8 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-HYSTERESIS-EVENT-1F Management level: Deployment specific or Customer

MeasurementQuantity Defines the measurement quantity for intra-freq HO measurement when the UE is in Cell-DCH state. When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.MeasurementQuantity is set to "CPICH Ec/No", this parameter is automatically set to "CPICH RSCP" When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.IntraFreqMeas.MeasurementQuantity is set to "CPICH RSCP", this parameter is automatically set to "CPICH Ec/No" FAP does not support "pathloss" measurement quantitiy in this version. --- RMS Access: READ Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "CPICH RSCP" Management level: N/A

ThresholdUsedFrequencyEvent1e Defines the reporting threshold for intra-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.39. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB Pathloss has a range of 30 dB to 165 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 165). Notification: None FAP Default value: -100 RMS Default value: -98 RMS Property: CELL-CONIFG-INTRA-FREQ-1-THRESHOLD-EVENT-1E Management level: Deployment

ThresholdUsedFrequencyEvent1f Defines the reporting threshold for intra-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.39. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB Pathloss has a range of 30 dB to 165 dB --- RMS Access: READ/WRITE



Object Parameter Description Type: Integer. (Range: -120 to 165). Notification: None FAP Default value: -100 RMS Default value: -97 RMS Property: CELL-CONIFG-INTRA-FREQ-1-THRESHOLD-EVENT-1F Management level: Deployment

TimeToTriggerEvent1e Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-TTT-EVENT-1E Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent1f Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 9 (Corresponds to actual value 200) RMS Default value:200/RF Profile v2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-TTT-EVENT-1F Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TriggeringCondition1Event1f Comma-separated list of strings. Indicates which cells can trigger Event 1f. Each list item is an enumeration of: - "Active" - "Monitored" - "Active and Monitored" 3GPP-TS.25.331 Section 14.1.2 and Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Active and Monitored" RMS Default value: Active and Monitored / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-TRIGGERING-EVENT-1F Management level: Deployment specific or Customer

TriggeringCondition2Event1e Comma-separated list of strings. Indicates which cells can trigger Event 1e. Each list item is an enumeration of: - "Active" - "Monitored"



133 UBS-44-57-004

Object Parameter Description - "Active and Monitored" - "Detected" - "Detected and Monitored" 3GPP-TS.25.331 Section 14.1.2 and Section 10.3.7.39 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Active and Monitored" RMS Default value: Active and Monitored / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTRA-FREQ-1-TRIGGERING-EVENT-1E Management level: Deployment specific or Customer

TimeToTriggerEvent1b Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 RMS Default value:320 RMS Property: CELL-CONIFG-INTRA-FREQ-TIME-TRIGGER-EVENT-1B Management level:Default

TimeToTriggerEvent1c Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 12 RMS Default value:320 RMS Property: CELL-CONIFG-INTRA-FREQ-TIME-TRIGGER-EVENT-1C Management level:Default

X_UBIQUISYS_COM_HandoutMargin1c The pilot quality of the target that triggers the 1c event has to be better than the 1e ThresholdUsedFrequencyEvent1e + HysteresisEvent1e by this margin before a handout will be triggered to this target because of event 1c. --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 4 RMS Default value:4 RMS Property: CELL-CONIFG-INTRA-FREQ1-HANDOUT-MARGIN-1C Management level: System

MacroOffset Cell Individual Offset to apply to all Macro neighbours



Object Parameter Description that are to be considered for the 1E/1F handout measurements. This allows the quality of a good/bad Macro to be varied relative to a good/bad Femto. (-10 .. +10 in steps of 0.5dB). --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-MACRO-QOFFSET-INTRAFREQ1 Management level: System

Table 52 Parameters for Intra Frequency Measurements

4.9.9 Inter Frequency Measurements 4.9.9.1 Parameters for Inter Frequency

Measurements

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas

This object contains parameters relating to the inter-freq HO control parameters.

MeasurementQuantity Defines the measurement quantity for inter-freq HO measurement when the UE is in Cell-DCH state. Enumeration of: CPICH Ec/No CPICH RSCP 3GPP-TS.25.331 Section 10.3.7.18 --- RMS Access: READ/WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "CPICH Ec/No" RMS Default value: CPICH Ec/No / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-MEAS-QUANTITY Management level: Deployment specific or Customer

HysteresisEvent2b Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5. The value of HysteresisEvent2b divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-HYSTERESIS-EVENT-2B Management level: Deployment specific or Customer

HysteresisEvent2d Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5. The value of HysteresisEvent2d divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 ---



135 UBS-44-57-004

Object Parameter Description RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-HYSTERESIS-EVENT-2D Management level: Deployment specific or Customer

HysteresisEvent2f Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5. The value of HysteresisEvent2f divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 RMS Property: CELL-CONIFG-INTER-FREQ-HYSTERESIS-EVENT-2F Management level: Deployment

TimeToTriggerEvent2b Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value: 100 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-TTT-EVENT-2B Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent2d Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-TTT-EVENT-2D Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent2f Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid:



Object Parameter Description 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-TTT-EVENT-2F Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

ThresholdUsedFrequencyEvent2b Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -10 RMS Default value: -11 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-THRESHOLD-EVENT-2B Management level: Deployment

ThresholdUsedFrequencyEvent2d Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -8 RMS Default value: -11 / RF Profile v. 2.3 Modify RMS Property: CELL-CONIFG-INTER-FREQ-THRESHOLD-EVENT-2D Management level: Deployment

ThresholdUsedFrequencyEvent2f Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -8 RMS Default value: -11 / RF Profile v. 2.3 Modify



137 UBS-44-57-004

Object Parameter Description RMS Property: CELL-CONIFG-INTER-FREQ-THRESHOLD-EVENT-2F Management level: Deployment

X_UBIQUISYS_COM_MacroOffset Cell Individual Offset to apply to all Macro neighbours that are to be considered for the 2B other frequency handout measurements. This allows the quality of a good/bad Macro to be varied relative to a good/bad Femto. (-10 .. +10 in steps of 0.5dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: FC-MACRO-QOFFSET-INTERFREQ Management level: Deployment specific or Customer

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_InterFreqMeas1

This object contains parameters relating to the optional second set of inter-freq HO control parameters.

Enable Enable the optional second set of inter-freq HO control parameters. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE/RF Profile v2.4 RMS Property: CELL-CONIFG-INTER-FREQ-1-ENABLE Management level: Deployment

HysteresisEvent2b Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5. The value of HysteresisEvent2b divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-HYSTERESIS-EVENT-2B Management level: Deployment specific or Customer

HysteresisEvent2d Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5. The value of HysteresisEvent2d divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-HYSTERESIS-EVENT-2D Management level: Deployment specific or Customer

HysteresisEvent2f Defines the hysteresis for inter-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 14.5 in steps of 0.5.



Object Parameter Description The value of HysteresisEvent2f divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.19 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 29). Notification: None FAP Default value: 4 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-HYSTERESIS-EVENT-2F Management level: Deployment specific or Customer

MeasurementQuantity Defines the measurement quantity for intra-freq HO measurement when the UE is in Cell-DCH state. When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas.MeasurementQuantity is set to "CPICH Ec/No", this parameter is automatically set to "CPICH RSCP" When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas.MeasurementQuantity is set to "CPICH RSCP", this parameter is automatically set to "CPICH Ec/No" --- RMS Access: READ Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "CPICH RSCP" Management level: N/A

ThresholdNonUsedFrequencyEvent2b Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold non used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -110 RMS Default value: -97 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-THRESHOLD-NON-USED-2B Management level: Deployment

ThresholdUsedFrequencyEvent2b Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0).



139 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: -95 RMS Default value: -97 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-THRESHOLD-EVENT-2B Management level: Deployment

ThresholdUsedFrequencyEvent2d Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -95 RMS Default value: -95 / RF Profile v. 2.4 Modify RMS Property: CELL-CONIFG-INTER-FREQ-1-THRESHOLD-EVENT-2D Management level: Deployment

ThresholdUsedFrequencyEvent2f Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19. Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -90 RMS Default value: -90 / RF Profile v. 2.4 Modify RMS Property: CELL-CONIFG-INTER-FREQ-1-THRESHOLD-EVENT-2F Management level: Deployment

TimeToTriggerEvent2b Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value: 100 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-TTT-EVENT-2B Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent2d Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640,



Object Parameter Description 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-TTT-EVENT-2D Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTriggerEvent2f Defines the time-to-trigger in milliseconds for inter-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.19 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 11 (Corresponds to actual value 320) RMS Default value: 320 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-FREQ-1-TTT-EVENT-2F Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

MacroOffset Cell Individual Offset to apply to all Macro neighbours that are to be considered for the 2B other frequency handout measurements. This allows the quality of a good/bad Macro to be varied relative to a good/bad Femto. (-10 .. +10 in steps of 0.5dB) --- RMS Access: READ/WRITE Type: Integer. (Range: -20 to 20). Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: FC-MACRO-QOFFSET-INTERFREQMEAS1 Management level: Deployment specific or Customer

Table 53 Parameters for Inter Frequency Measurements

4.9.9.2 Inter Frequency Handovers Extensions

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterFreqMeas

This object contains parameters relating to the inter-freq HO control parameters.

X_UBIQUISYS_COM_ThresholdNonUsedFrequencyEvent2b

Defines the reporting threshold for inter-freq HO measurement when the UE is in Cell-DCH state. This is the "Threshold non used frequency" as defined in 3GPP-TS.25.331 Section 10.3.7.19.



141 UBS-44-57-004

Object Parameter Description Each valid value of MeasurementQuantity has a different valid range. CPICH RSCP has a range of -120 dBm to -25 dBm CPICH Ec/No has a range of -24 dB to 0 dB --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to 0). Notification: None FAP Default value: -10 RMS Default value: -10 RMS Property: CELL-CONIFG-INTER-FREQ-THRESHOLD-NON-USED-2B Management level: Deployment

Table 54 Inter Frequency Handovers Extensions

4.9.10 Inter RAT Measurements

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas

This object contains parameters relating to the inter-RAT HO related control parameters. This is specifically for GERAN system.

X_UBIQUISYS_COM_MeasurementQuantity

Defines the UTRAN measurement quantity for inter-RAT HO measurement when the UE is in Cell-DCH state. Enumeration of: CPICH Ec/No CPICH RSCP 3GPP-TS.25.331 Section 10.3.7.38 --- RMS Access: READ/WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "CPICH Ec/No" RMS Default value: CPICH Ec/No / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-MEAS-QUANTITY Management level: Deployment specific or Customer

Hysteresis Defines the hysteresis for inter-RAT HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of Hysteresis divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.30 Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 0 RMS Default value: 4 RMS Property: CELL-CONIFG-INTER-RAT-HYSTERESIS Management level: Deployment

X_UBIQUISYS_COM_Hysteresis3b Defines the hysteresis for inter-RAT HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of X_UBIQUISYS_COM_Hysteresis3b divided by 2 yields the actual value of the hysteresis.



Object Parameter Description 3GPP-TS.25.331 Section 10.3.7.30 Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 0 RMS Default value:0 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-HYSTERESIS-3B Management level: Deployment specific or Customer

TimeToTrigger Defines the time-to-trigger in milliseconds for inter-RAT HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.30 and Section 10.3.7.64 Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value: 100/ RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-TTT Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

X_UBIQUISYS_COM_TimeToTrigger3b Defines the time-to-trigger in milliseconds for inter-RAT HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.30 and Section 10.3.7.64 Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value:100 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-TTT-3B Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

ThresholdOwnSystem Defines the reporting threshold for inter-RAT HO measurement when the UE is in Cell-DCH state. This is the "Threshold own system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Note: Applies to 3A measurements only --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -10 RMS Default value: -11 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-THRESHOLD-OWN-SYSTEM Management level: Deployment



143 UBS-44-57-004

Object Parameter Description ThresholdOtherSystem Defines the reporting threshold for inter-RAT HO

measurement when the UE is in Cell-DCH state. This is the "Threshold other system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -92 RMS Default value: -98 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-THRESHOLD-OTHER-SYSTEM Management level: Deployment

X_UBIQUISYS_COM_ThresholdOtherSystem3b

Defines the reporting threshold for inter-RAT HO measurement when the UE is in Cell-DCH state. This is the "Threshold other system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -102 RMS Default value: -102 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-THRESHOLD-OTHER-SYSTEM-3B Management level: Deployment specific or Customer

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_InterRATMeas1

This object contains parameters relating to the optional second set of inter-RAT HO control parameters.

Enable Enable the optional second set of inter-RAT HO control parameters. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE / RF Profile v2.4 RMS Property: CELL-CONIFG-INTER-RAT-1-ENABLE Management level: Deployment

MeasurementQuantity Defines the UTRAN measurement quantity for inter-RAT HO measurement when the UE is in Cell-DCH state. When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas.MeasurementQuantity is set to "CPICH Ec/No", this parameter is automatically set to "CPICH RSCP" When InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.InterRATMeas.MeasurementQuantity is set to "CPICH RSCP", this parameter is automatically set to "CPICH Ec/No" --- RMS Access: READ Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None



Object Parameter Description FAP Default value: "CPICH RSCP" RMS Default value:N/A RMS Property:N/A Management level: N/A

Hysteresis Defines the hysteresis for inter-RAT HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of Hysteresis divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.30 Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 0 RMS Default value: 4 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-HYSTRESIS Management level: Deployment

Hysteresis3b Defines the hysteresis for inter-RAT HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of X_UBIQUISYS_COM_Hysteresis3b divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.30 Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 0 RMS Default value: 0 / RF Profile v. 2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-HYSTRESIS-3B Management level: Deployment specific or Customer

ThresholdOtherSystem Defines the reporting threshold for inter-RAT HO measurement when the UE is in Cell-DCH state. This is the "Threshold other system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -92 RMS Default value: -98 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-THRESHOLD-OTHER-SYSTEM Management level: Deployment

ThresholdOtherSystem3b Defines the reporting threshold for inter-RAT HO measurement when the UE is in Cell-DCH state. This is the "Threshold other system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -102 RMS Default value: -102 / RF Profile v2.3



145 UBS-44-57-004

Object Parameter Description RMS Property: CELL-CONIFG-INTER-RAT-1-THRESHOLD-OTHER-SYSTEM-3B Management level: Deployment specific or Customer

ThresholdOwnSystem Defines the reporting threshold for inter-RAT HO measurement when the UE is in Cell-DCH state. This is the "Threshold own system" as defined in 3GPP-TS.25.331 Section 10.3.7.30. Note: Applies to 3A measurements only --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to 0). Notification: None FAP Default value: -100 RMS Default value: -97 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-THRESHOLD-OWN-SYSTEM Management level: Deployment

TimeToTrigger Defines the time-to-trigger in milliseconds for inter-RAT HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.30 and Section 10.3.7.64 Used by Ubiquisys FAPs for 3A [and 3C with Handover Prioritisation feature] measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value:100 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-TTT Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

TimeToTrigger3b Defines the time-to-trigger in milliseconds for inter-RAT HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.30 and Section 10.3.7.64 Used by Ubiquisys FAPs for 3B measurements --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 6 (Corresponds to actual value 100) RMS Default value:100 / RF Profile v2.3 RMS Property: CELL-CONIFG-INTER-RAT-1-TTT-3B Management level: Deployment specific or Customer Note: 0=0,1=10,2=20,3=40,etc.

Table 55 Inter RAT Measurements

4.9.11 UE Internal Measurements



Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.UEInternalMeas

This object contains parameters relating to the UE internal measurement control parameters.

FilterCoefficient Defines the filter coefficient for UE internal measurement. 3GPP-TS.25.331 Section 10.3.7.9 and Section 10.3.7.79. Enumerations of 0,1,2,3,4,5,6,7,8,9,11,13,15,17,19 --- RMS Access: READ Type: Integer. (Range: 0 to 14). Notification: None FAP Default value: 11 RMS Default value:N/A RMS Property:N/A Management level: N/A

TimeToTriggerEvent6a Defines the period in milliseconds between detection of Event 6a and sending of Measurement Report. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.80 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 2 RMS Default value:N/A RMS Property:N/A Management level: Default

TimeToTriggerEvent6b Defines the period in milliseconds between detection of Event 6b and sending of Measurement Report. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.80 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 15 (Corresponds to actual value 5000) RMS Default value:5000 RMS Property: FC-TTT-EVENT-6B Management level: Default Note: 0=0,1=10,2=20,3=40,etc.

Table 56 UE Internal Measurements



147 UBS-44-57-004

4.9.12 State Transition Measurement 4.9.12.1 State Transition Measurement

Extensions

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.X_UBIQUISYS_COM_StateChangeMeas

This object contains parameters to configure the measurements and configuration relating to RRC state changes (DCH<->FACH, FACH<->PCH, PCH<->IDLE and FACH->IDLE)

DCHtoFACHTimeToTrigger

Time to trigger for transition from CELL DCH to CELL FACH when inactivity has been detected in both UL and DL in milliseconds The value is the index (starting at zero) into the following list of valid values: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000, 10000, 15000, 30000, 60000, 120000, 300000. Any value other than those and the CPE MUST reject the request. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 21). Notification: None FAP Default value: 17 (Corresponds to Actual value 15000) RMS Default value: 15000 / RF Profile v. 2.3 RMS Property: DCH-FACH-TIME-TRIGGER Management level: Deployment Note: 0=0, 1=10, 2=20, 3=40, etc.

FACHtoPCHTimeToTrigger

Time to trigger for transition from CELL FACH to CELL PCH when inactivity has been detected in both UL and DL in milliseconds The value is the index (starting at zero) into the following list of valid values: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000, 10000, 15000, 30000, 60000, 120000, 300000. Any value other than those and the CPE MUST reject the request. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 21). Notification: None FAP Default value: 17 (Corresponds to Actual value 15000) RMS Default value: 15000 RMS Property: FACH-PCH-TIME-TRIGGER Management level: Deployment Note: 0=0, 1=10, 2=20, 3=40, etc.

PCHtoIDLETimeToTrigger

Time to trigger transition from CELL_PCH to IDLE in minutes. The value is the index (starting at zero) into the following list of valid values: 0, 1, 2, 5, 10, 20 and 30 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 6). Notification: None FAP Default value: 5 (Corresponds to Actual Value 20) RMS Default value: 20 RMS Property: PCH-IDLE-TIME-TRIGGER



Object Parameter Description Management level: Deployment Note: 0=0, 1=1, 2=2, 3=5, etc.

FACHtoIDLETimeToTrigger

Time to trigger for transition from CELL FACH to CELL IDLE when inactivity has been detected in both UL and DL in milliseconds The value is the index (starting at zero) into the following list of valid values: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000, 10000, 15000, 30000, 60000, 120000, 300000 . Any value other than those and the CPE MUST reject the request. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 21). Notification: None FAP Default value: 20 (Corresponds to Actual value 120000) RMS Default value: 120000 / RF Profile v. 2.3 RMS Property: FACH-IDLE-TIME-TRIGGER Management level: Deployment Note: 0=0, 1=10, 2=20, 3=40, etc.

Table 57 State Transition Measurement Extensions

4.9.13 RF and Power Management Section 6 outlines the RF configuration process during power-up. The following subsections cover the power management process and associated parameter guidelines in more detail.

4.9.13.1 Manual and Load Based Reselection

For details on this feature, refer to:

[UBS-44-20-046] Coverage Tuning

4.9.13.2 Power Management Process The HNB DL and UL power management process has two main stages: • Stage 1: setting of the initial total DL and UL transmit power levels based on the HNB measurement of the

macro operating environment and the HMS provisioned parameters.

• Stage 2: post power-up optimisation which includes:Optimisation of the DL and UL powers based on the femto UE measurement reports. The optimisation aims to minimise leakage/dead zones outside the intended HNB coverage area and to avoid an UL noise rise to the surrounding ML Node B’s.

o Dynamic HSDPA power allocation for active HS sessions which aims to allocate as much power to HSDPA sessions depending on current cell loading hence ensuring optimal use of total available power.

o Dynamic DCH power management for DCHs which aims to ensure that total DCH power available is available to all DCHs on a need to basis while also ensuring fair distribution of resources across DCHs.

o DL/UL RAB rate adaption for R99 PS sessions that will reconfigure RABs to a lower data rate e.g. when experiencing interference and restore the RAB to a higher data rate at an appropriate time e.g. when no longer experiencing interference.

o Dynamic management of noise rise target for HSUPA which aims to limit the HSUPA power whenever HSUPA sessions could impact R99 services in the uplink.

o Monitoring of the RF environment for changes (referred to as Significant Event Checking) using the Fast Sniff Mode (FSM) of the Network Listen Mode function which could indicate that that the initial



149 UBS-44-57-004

RF parameters selected are no longer optimal leading to a rerun of the auto configuration process of the parameters in question.

In the sections that follow, more detail descriptions of the various HNB features mentioned above are provided with specific reference to the relevant parameters associated with these features.

4.9.13.3 Initial DL Power Setting Using the maximum/minimum allowed DL power provided by the HMS as the operating bounds (MaxFAPTxPower.min .. MaxFAPTxPower.max), the HNB will set its DL power such that its CPICH Ec/No is of sufficient quality to provide adequate coverage/performance for the femto UEs cell within the expected femto coverage area as well as causing minimal impact to macro layer coverage. As such the AP will set its CPICH power depending on the measurements made by the Network Listen as follows:

1. If the Network Listen Mode has measured WCDMA macro signals on its operating carrier then the HNB CPICH power will be set based on the strongest measured macro RSCP such that the HNB CPICH RSCP at the HNB edge of coverage is not excessively dominant over the macro RSCP levels hence minimising impact to macro layer coverage outside the HNB intended coverage area. The femto edge of coverage is represented by an indoor pathloss parameter (FAPCoverageTarget) set to 95dB.

2. If the Network Listen Mode has measured nearby HNB within a certain pathloss (SlavingZAPRange) of it on its operating carrier, the HNB will extract from the SIBs the CPICH Tx power of the strongest HNB within this pathloss and set its own CPICH power to this value. If the detected HNBs are outside this pathloss radius, the HNB will set its power based on measured WCDMA macro signals (as described in the previous paragraph) or to an initial level provided by the AP MS. This approach gives collocated AP equal priority and hence equal QoS. The pathloss radius within which HNBs copy each other powers is represented by a configurable HNB parameter (SlavingZAPRange).

3. If the Network Listen Mode has not measured WCDMA/GSM macro signals and has not measured any HNBs on its operating carrier, it will set its CPICH power to achieve a configurable minimum CPICH RSCP target (inRSCP) at the cell edge at a nominal indoor pathloss (FAPCoverageTarget) relative to the HNB.

4.9.13.4 Initial UL Power Setting (Maximum Femto UE Transmit Power)

Given an UL operating power range by the HMS (MaxULTxPower.min .. MaxULTxPower.max) and pathloss to macro cells measurements provided by Network Listen Mode, the HNB sets a maximum allowed UE transmit power such that if its UEs were transmitting at this maximum power level they will not cause a significant UL noise rise to macro Node B.

The aim is to ensure that the interference at the macro cell from a femto UE is always below the macro noise floor (NodeBNoiseFloor). The maximum allowed UE power is calculated by summing the pathloss to the nearest macro cell, a typical macro noise floor value and a back off margin (ULNoiseRiseMargin), which caters for multiple femto UEs transmitting simultaneously. The WCDMA basestation path loss is calculated by subtracting the measured RSCP of the basestation from the CPICH Tx Power of the basestation extracted from its SIBs by the Network Listen Mode function whereas the typical noise floor and back off margins are parameters provided by the HMS. This approach keeps the noise rise caused by the Femto AP UE well below the up link noise caused by the macro cell traffic.

4.9.13.4.1 Parameter Analysis: RRMProfile.ULNoiseMargin and RRMProfile.NodeBNoiseFloor

When a HNB is operating on a carrier used by the macro layer it will set its power based on the path loss to the nearest macro Node B and a typical Node B noise floor value. The typical noise floor value is defined by the parameter NodeBNoiseFloor. The link budget in Table 58 shows the calculation for the typical noise floor of a macro node B. A back-ff margin defined by parameter ULNoiseMargin is also applied to limit the additional UL noise rise (referenced at the antenna connector) caused by the femto UEs to the macro Node Bs. Table 59 shows an example of how to calculate of the ULNoiseMargin parameter. This margin is based on the assumption that all



the femto UEs are transmitting at the allowed maximum power set the by HNB, hence it could be relaxed if need be as it unlikely all femto UEs will be transmitting at maximum allowed power.

ML Node B Noise Floor Node B Bandwidth B 3.84 MHz Thermal Noise Density Pnd -174 dBm/Hz Receiver Noise Figure NF 4.5 dB Receiver Noise Density Prd -169.5 dBm/Hz Receiver Noise Power Pr -103.7 dBm =Prd+10log(B) Loading L 20 % Planned Orthogonality Factor Ofp Interference Margin (Noise Rise) IM 1.0 dB =-10*LOG(1-(load/100)) Receiver Interference Power Pi -109.7 dBm =10*log(10^((Pr+IM)/10)-10^(Pr/10)

Noise Floor at antenna connector Pt -102.7 dBm =10*log(10^((Pr)/10)+[10^(Pi/10)*(1-Ofp)]

Table 58: Noise Rise from Access Point UE

Likely number of Femto UE simultaneously transmitting in UL per macro Node B femton 20

Acceptable noise rise from all Femto UEs femtoNR 0.5dB6 Number of dBs below macro noise floor total power from all Femto UE has to be to cause noise rise of femtoNR

[ ]110log10 1010 −∗−=∆ femtoNR

femto 9dB

Back off margin

∗−=

∆−

femtoninULNoiseM

femto 10

1010log10arg 22dB

Table 59: Example calculation of ULNoiseMargin Parameter

4.9.13.5 Dynamic DL and UL Power Adaptation

As part of the ongoing RRM process the HNB optimises the maximum DL and UL powers through the use of femto UE measurement reports collected during active femto call sessions. The UE reports contain CPICH RSCP and Ec/No measurement for the AP and its WCDMA intra frequency neighbours which the HNB collects into histograms. The power adaptation algorithms rely on the mobility of Femto users as they make calls to create a ‘picture’ of the surrounding coverage area.

The HNB uses the histograms to optimise the femto AP maximum DL transmit power to achieve a HNB RSCP dominance within 90% of the expected coverage area and ensure the UL power would not cause an uplink noise rise to surrounding macro cells. Any measurements above UpperIndoorPathlossLimit and below 65dB will be excluded from the histograms used for power adaptation. This ensures that the HNB power will not shrink and or expand beyond reasonable limits.

4.9.13.6 DCH Power Reallocation The HNB has a dynamic DCH power allocation feature which aims to maximise the use of available DL power. By default the algorithm allocates the maximum available total DCH code power to each individual user (e.g. Up to 60% of total cell power). The HNB hen sums the DCH code powers being used by all users. If the sum exceeds the reduction threshold then the maximum available DCH code is reduced by a fixed amount. If the sum falls

6 A noise rise of 0.5 dB in this example is equivalent of taking a loading of 20% on the Node B up to 30% which is considered acceptable especially when you consider that extra UL capacity is being freed up on the macro Node B when traffic is offloaded onto the Access Point



151 UBS-44-57-004

below the increase threshold the maximum is re-established. DCH has priority over HSDPA. Power hungry users on the cell boundary are impacted first. The .X_UBIQUISYS_COM_DynamicDLDCHPowerAllocation object includes the parameters that control the feature including how to enable the feature. This feature can be used in conjunction with the dynamic HSDPA power allocation feature (see below).

4.9.13.7 Dynamic HSDPA Power Allocation

The HNB has a dynamic HSDPA power allocation feature which aims to maximise the use of available DL power. The feature monitors the instantaneous power in use by all DL DCHs and allocates near 100% of the remaining power to HSDPA. This helps to improve HSDPA performance in lightly loaded cells as unused power is diverted to HSDPA. However, under heavily loaded conditions HSDPA throughput could be slightly impacted as priority is given to the Release 99 DCH. The feature is switched off by default. The .X_UBIQUISYS_COM_DynamicDLPowerAllocation object includes the parameters that control the feature including how to enable the feature.

Total Power in use by all DL dedicated user physical channels is monitored by the HNB when a HS session is active. Periodically RRC will analyse the total DPDCH power at that instance and up to a certain amount of time prior to that instance. Based on the analysis RRC performs a look up in the Dynamic Power Allocation table and selects the appropriate HS Profile:

• If the total power over a certain period exceeds a certain percentage of total power for a certain period, then the total power allocated to HSDPA is reduced.

• If the total DPDCH Power over a certain period falls below a certain percentage of total available power for a certain period of time, then the total power allocated to HSDPA is increased.

When a new HS Profile is selected RRC uses Physical Channel Reconfiguration procedure to signal the new Measurement Power Offset (MPO) value.

4.9.13.8 Dynamic Noise Rise Target Management for HSUPA/R99 Coexistence

For HSUPA, the shared resource in the uplink is the tolerable UL noise rise at the base station, which depends on the decentralized power resource in each UE. The fraction of tolerable UL noise rise resource a UE is using depends on the data rate used by the UE. Generally, the higher the data rate, the larger the required transmission power and the higher the tolerable RTWP resource consumption.

Under normal conditions adding an R.99 UL service to the AP will have an insignificant impact to ULcoverage (as the additional UL noise rise will be negligible). However, UEs in a HSUPA session could transmit by up to 15dBs+ more than an R99 session from the same physical location, as a result R99 UEs will then be forced to power up to overcome the additional UL interference at the AP from the HSUPA session which could reduce the uplink coverage of R99 UEs.

To mitigate the possibility of HSUPA sessions further shrinking UL coverage for R99 users the default HSUPA scheduler tolerable noise rise is temporarily clawed back relative to the instantaneous noise floor of the AP whenever a HSUPA session is active and a UE with an R99 service is approaching the limit of its uplink coverage. The default HSUPA scheduler tolerable noise rise is only restored when all UEs with an R99 service running are not near the limit of their uplink coverage. The proximity of UEs to the limit of their UL coverage is monitored via event triggered measurements of type 6A & 6B.

The .X_UBIQUISYS_COM_DynamicULPowerAllocation object includes the parameters that control the feature including.

4.9.13.9 RF Parameters

Parameter Description InternetGatewayDevice.Services.FAPService.1. This object contains parameters relating to the RF



Parameter Description CellConfig.UMTS.RAN.FDDFAP.RF configuration. UARFCNDL Comma-separated list (maximum length 64) (minimum 1

items) of strings. Each item is a DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell. 3GPP-TS.25.433 Section 9.2.1.65 Self-configuration for UARFCN is controlled by .Capabilities.UMTS.SelfConfig.UARFCNConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.UARFCNSelfConfigEnable from an enabled perspective. If the FAP's self-configuration capability for UARFCN is available and enabled, this parameter MAY contain more than one item and the FAP is expected to select one from the list for UARFCNDLInUse. If the self-configuration capability is not available or not enabled, then this parameter SHOULD contain only a single item. The UARFCN values supplied to the list are derived based on the formula defined in 3GPP-TS.25.104 Section 5.4.3 The order of the UARFCN entries has no significance. The carrier spacing in FDD mode is fixed as defined in 3GPP-TS.25.104. Therefore, the FAP can unambiguously derive the UL UARFCN value based on the selected DL UARFCN. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 385 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default vaule:Input RMS Property: CELL-CONFIG-RF-UARFCNDL FC-UARFCN-SINGLE FC-UARFCN-CL FC-UARFCN-ENTERPRISE-ENTRY Management level: Deployment specific or Customer

UARFCNDLInUse The DL UARFCN being used by the FAP. Self-configuration for UARFCN is controlled by .Capabilities.UMTS.SelfConfig.UARFCNConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.UARFCNSelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the choices provided in UARFCNDL. If the self-configuration capability is not available or not enabled, then this parameter contains the first value in UARFCNDL. --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: Active Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNULInUse The UL UARFCN being used by the FAP. The UL UARFCN that corresponds to UARFCNDLInUse. ---



153 UBS-44-57-004

Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNDLToProtect Comma-separated list (maximum length 64) of strings. Each item is a DL UARFCNs to be protected from adjacent channel interference. "Adjacent channel" in this context means offset from the FAP's UARFCN by 5MHz. 3GPP-TS.25.104 Section 6.4.6 If any of the items in the list are adjacent to the FAP's own DL channel, the FAP MUST take the Primary CPICH code power measured on these channels into account as part of its maximum transmit power self-configuration. The UARFCNs in the list can belong to any operator, allowing for protection of the FAP operator's own macro layer as well as that of other operators (only the latter is mandated by the 3GPP-TS.25.104 requirements). The list should take into account the ability of the FAP to self-configure its own DL UARFCN and so SHOULD include any channels (requiring protection) which can potentially be adjacent to the UARFCN selected by the FAP. For example, if only adjacent operator protection is required and the FAP has the ability to self-configure to any channel owned by its operator, this list would be populated with the UARFCNs immediately above and below the range of channels owned by the FAP operator. Adjacent channel protection can cause the FAP transmit power to be reduced down to as low as 8dBm. If an empty string then it indicates that there are no channels adjacent to the FAP that require protection, or that self-configuration of the FAP transmit power is not enabled. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_UARFCNDLNormalCarriers

Comma-separated list (maximum length 64) of strings. Each item is a DL UARFCN of the surrounding Normal (non-Straddled) carriers that the HNB must consider when performing Straddled Carrier selection. The normal carriers may belong to the serving Network Operator or may be a neighbouring carrier in use by another operator. If an empty string then the Straddled Carrier feature is disabled. This field is mandatory if any CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.FrequencyConfig entries have CarrierDeploymentType marked as "Straddled carrier" Note, the HNB does not use this list when choosing a UARFCN for transmission, this list is only used to



Parameter Description differentiate between Normal and Straddled Carriers during REM scanning and automatic TX power selection. (The UARFCNs available for transmission, either normal or Straddled, are configured in parameter UARFCNDL.) --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

PrimaryScramblingCode Comma-separated list (maximum length 32) (minimum 1 items) of strings. Each item is a Primary DL Scrambling Code used by the FDD mode cell with a numeric range between 0 and 511 inclusive. 3GPP-TS.25.433 Section 9.2.2.34 Self-configuration for PSC is controlled by .Capabilities.UMTS.SelfConfig.PrimaryScramblingCodeConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.PrimaryScramblingCodeSelfConfigEnable from an enabled perspective. If the FAP's self-configuration capability for PrimaryScramblingCode is available and enabled, this parameter MAY contain more than one item and the FAP is expected to select one from the list for PrimaryScramblingCodeInUse. If the self-configuration capability is not available or not enabled, then this parameter SHOULD contain only a single item. The multiplicity of the PSC values can also be expressed by defining a range using ".." (two periods) between two values. In this case, the combination of two values defines the lower-bound and upper-bound of the range inclusive. The following are examples of valid PSC string: "20" (explicitly specifies a single PSC value) "20,30,40" (specifies 3 possible PSC values to select from) "20..40" (specifies 21 possible values between 20 and 40, inclusive) "20..40,50" (specifies 22 possible values between 20 and 40 inclusive and a single value 50) The order of the items has no significance. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value:1..10 RMS Property: CELL-CONFIG-RF-PSC FC-PSC-CL-ENTRY FC-PSC-CL-INNER Management level: Deployment specific or Customer

PrimaryScramblingCodeInUse The PSC being used by the FAP. Self-configuration for PSC is controlled by .Capabilities.UMTS.SelfConfig.PrimaryScramblingCodeC



155 UBS-44-57-004

Parameter Description onfig from an availability perspective and .FAPControl.UMTS.SelfConfig.PrimaryScramblingCodeSelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the choices provided in PrimaryScramblingCode. If the self-configuration capability is not available or not enabled, then this parameter contains the first value in PrimaryScramblingCode. 512 is treated as invalid value and defines that the PSC selction is not yet completed. FAP will write the valid value after the PSC selection is completed during boot up. This is too ensure that FAP reports the PSC in the inform if active notification is set for this parameter. --- RMS Access: READ Type: Integer. (Range: 0 to 512). Notification: None Value set at runtime FAP Default value:512 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxFAPTxPower Defines the maximum transmission power allowed on the FAP, maximum value for the linear sum of the power of all downlink physical channels, that is allowed to be used in a cell. MaxFAPTxPower is expressed as a range of allowed maximum power levels with ".." (two periods) between the upper and lower values, i.e. "<Pmax_low>..<Pmax_high>". MaxFAPTxPower identifies the limits between which the FAP can self-configure its maximum transmit power. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxFAPTxPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.MaxFAPTxPowerSelfConfigEnable from an enabled perspective. <Pmax_low> and <Pmax_high> are measured in dBm and have a range of -40.0 to 30.0 incremented by 0.1dB. 3GPP-TS.32.642 Section 6.3.9, 3GPP-TS.25.104 Section 6.2.1 Note: Ranges adjusted from standard to align with Ubiquisys FAP capabilities Updates to this parameter will only take affect after the following full radio scan (either due to reboot or periodic scan). --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "-14.0..5.0" RMS Default value: Runtime Provisioning / RF Profile v. 2.3 Modify RMS Property: MAX-FAP-TX-POWER Management level: Deployment or Deployment specific or Customer

MaxFAPTxPowerInUse The maximum transmission power measured in dBm



Parameter Description currently used by the FAP. Actual values of the maximum transmission power are -40.0dBm to 30.0 dBm in steps of 0.1 dB. The value of MaxFAPTxPowerInUse divided by 10 yields the actual value of the maximum transmission power. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxFAPTxPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.MaxFAPTxPowerSelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the range provided in MaxFAPTxPower. If the self-configuration capability is not available or not enabled, then this parameter contains a value selected by the ACS. --- RMS Access: READ Type: Integer. (Range: -400 to 300). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxULTxPower Defines the maximum transmission power level a UE can use on PRACH. MaxULTxPower is expressed as a range of allowed maximum power levels with ".." (two periods) between the upper and lower values, i.e. "<Pmax_low>..<Pmax_high>". MaxULTxPower identifies the limits between which the FAP can self-configure its maximum transmit power. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.MaxULTxPowerSelfConfigEnable from an enabled perspective. <Pmax_low> and <Pmax_high> are measured in dBm and have a range of -50 to 33 incremented by 1. 3GPP-TS.25.331 Section 10.3.6.39. Ubiquisys comment: This parameter is also used within RRM for the calculation of the max and min tx power used for the initial DL DCH power calculation. update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "5..5" RMS Defaut value: "5..5" RMS Property: MAX-UL-TX-POWER Management level: Deployment

MaxULTxPowerInUse The maximum transmission power level a UE can use on PRACH. Self-configuration for maximum transmission power is controlled by .Capabilities.UMTS.SelfConfig.MaxULTxPowerConfig from an availability perspective and



157 UBS-44-57-004

Parameter Description .FAPControl.UMTS.SelfConfig.MaxULTxPowerSelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the range provided in MaxULTxPower. If the self-configuration capability is not available or not enabled, then this parameter contains a value selected by the ACS. --- RMS Access: READ Type: Integer. (Range: -50 to 33). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PCPICHPowerInUse The P-CPICH power measured in dBm currently used by the FAP. Actual values of the maximum transmission power are -50.0 dBm to 20.0 dBm in steps of 0.1 dB. The value of PCPICHPowerInUse divided by 10 yields the actual value of the maximum transmission power. Self-configuration for transmission power is controlled by .Capabilities.UMTS.SelfConfig.PCPICHPowerConfig from an availability perspective and .FAPControl.UMTS.SelfConfig.PCPICHPowerSelfConfigEnable from an enabled perspective. If the self-configuration capability is available and enabled, this parameter indicates the value selected by the FAP among the range provided in PCPICHPower. If the self-configuration capability is not available or not enabled, then this parameter contains a value selected by the ACS. --- RMS Access: READ Type: Integer. (Range: -500 to 200). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SSCHPower Defines the transmission power offset measured in dB of the Secondary SCH relative to the Primary CPICH power. Actual values of the transmission power offset are -35.0 dB to 15.0 dB in steps of 0.1 dB. The value of SSCHPower divided by 10 yields the actual value of the transmission power offset. 3GPP-TS.32.642 Section 6.3.11, 3GPP-TS.25.433 Section 9.1.24 and Section 9.2.1.21 --- RMS Access: READ/WRITE Type: Integer. (Range: -350 to 150). Notification: None FAP Default value: -40 RMS Default value:-40 RMS Property: FC-SSCH-POWER Management level: Solution or Customer

PICHPower Defines the maximum transmission power offset measured in dB of the PICH channel relative to the Primary CPICH transmission power.



Parameter Description 3GPP-TS.32.642 Section 6.3.9, 3GPP-TS.25.433 Section 9.2.1.49A 3GPP-TS.25.331 Section 10.3.6.50 --- RMS Access: READ/WRITE Type: Integer. (Range: -10 to 5). Notification: None FAP Default value: -6 RMS Default value:-6 RMS Property: FC-PICH-POWER Management level: Solution or Customer

PCHPower Defines the transmission power offset measured in dB of the PCH relative to the Primary CPICH power. Actual values of the transmission power offset are -35.0 dB to 15.0 dB in steps of 0.1 dB. The value of PCHPower divided by 10 yields the actual value of the transmission power offset. 3GPP-TS.32.642 Section 6.3.9, 3GPP-TS.25.433 Section 9.1.3.1 and Section 9.2.1.21 --- RMS Access: READ/WRITE Type: Integer. (Range: -350 to 150). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-PCH-POWER Management level: Solution or Customer

FACHPower Defines the transmission power offset measured in dB of the FACH relative to the Primary CPICH power. Actual values of the transmission power offset are -35.0 dB to 15.0 dB in steps of 0.1 dB. The value of FACHPower divided by 10 yields the actual value of the transmission power offset. 3GPP-TS.32.642 Section 6.3.9, 3GPP-TS.25.433 Section 9.1.6.1 and Section 9.2.1.21 --- RMS Access: READ/WRITE Type: Integer. (Range: -350 to 150). Notification: None FAP Default value: 30 RMS Default value:30 RMS Property: FC-FACH-POWER Management level: Solution or Customer

BCHPower Defines the transmission power offset measured in dB of the BCH relative to the Primary CPICH power. Actual values of the transmission power offset are -35.0 dB to 15.0 dB in steps of 0.1 dB. The value of BCHPower divided by 10 yields the actual value of the transmission power offset. 3GPP-TS.32.642 Section 9.3.11, 3GPPTS.25.433 Section 9.1.24 and Section 9.2.1.21 --- RMS Access: READ/WRITE Type: Integer. (Range: -350 to 150). Notification: None FAP Default value: -30 RMS Default value:-30 RMS Property: FC-BCH-POWER Management level: Solution or Customer

AICHPower Defines the transmission power offset measured in dB of one AICH relative to the Primary CPICH power. Parameter defined in SIB5 3GPP-TS.25.331 Section 10.3.6.3.



159 UBS-44-57-004

Parameter Description Transmission power level of AICH, AP-AICH and CD/CA-ICH channels compared to CPICH. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 9.2.2.D --- RMS Access: READ/WRITE Type: Integer. (Range: -22 to 5). Notification: None FAP Default value: -6 RMS Default value:-6 RMS Property: FC-AICH-POWER Management level: Solution or Customer

X_UBIQUISYS_COM_HSSCCH_CellPowerOffset

Cell wide HS-SCCH power offset relative to P-CPICH: 0-28 (0=-14dB, 28=0dB) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 28). Notification: None FAP Default value: 8 RMS Default value:8 RMS Property: FC-HSS-CCH-CELL-POWER-OFFSET Management level: Solution or Customer

CBSFrameOffset Value of CBS frame offset (CTCH) on DL FACH. Parameter in SIB5 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: CBS-FRAME-OFFSET Management level: Default

CTCHAllocationPeriod The value defines 'N' multiples of M(TTI) for CBS DRX calculations at the UE side. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 255). Notification: None FAP Default value: 242 RMS Default value:242 RMS Property:CBS-CTH-ALLOCATION-PERIOD Management level: Default

X_UBIQUISYS_COM_CbsSchedulePeriod Period of BMC Scheduling Message with following enumerations -8 -16 -32 -64 -128 -256 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "32" RMS Default value:N/A RMS Property: N/A Management level: Default

X_UBIQUISYS_COM_ProvisionedOtherHNBPrimaryScramblingCodesNumberOfEntries

Number of entries in the InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_ProvisionedOtherHNBPrimaryScramblingCodes table ---



Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 4). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property: N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_ProvisionedOtherHNBPrimaryScramblingCodes

A supplementary list of UARFCN PSC pairs used to provide the HNB with visibility of the PSC allocated for use by any HNBs in the locality (in addition to those used by the HNB to select a PSC for its own use) The HNB appends these tuples with the UARFCN PSC pairs defined in InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDPFAP.RF.UARFCNDL and PrimaryScramblingCode and if enabled the auto doscovered UARFCN.PSC tuples populated in InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDPFAP.RF.X_UBIQUISYS_COM_RRMProfile.AutoDiscoveredOtherHNBPrimaryScramblingCode table in its consideration of HNB neighbours

UARFCNDL

Central downlink channel frequency: 412-10838. --- RMS Access: READ/WRITE Type: Integer. (Range: 412 to 10838). Notification: None FAP Default value: 412 RMS Default value: 512 RMS Property: FC-OTHER-HNB-PSC-i-DLUARFCN Management level: Deployment specific or Customer

PrimaryScramblingCodes

Comma-separated list (maximum length 32) of strings. Each item is a Primary DL Scrambling Code used by the FDD mode cell with a numeric range between 0 and 511 inclusive. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:empty RMS Property: FC-OTHER-HNB-PSC-i-PSC Management level: Deployment specific or Customer

Table 60 RF Parameters



161 UBS-44-57-004

4.9.13.9.1 RRM Profile

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile

This object contains parameters relating to the Ubiquisys proprietary RRM algorithms

MinWidebandInterferenceLevel If the wideband interference (RSSI) on a carrier is below this level (dBm) it is concluded that the carrier is not being used. update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: -150 to -20). Notification: None FAP Default value: -85 RMS Default value:N/A RMS Property:N/A Management level: Default or System or N/A

MaxTotalWidebandInterferenceLevel Maximum allowed wideband interferance for straddled carrier (dBm) above which an alarm is triggered update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to -15). Notification: None FAP Default value: -65 RMS Default value:N/A RMS Property:N/A Management level: Default or System or N/A

MaxTotalMacroPilotInterferenceLevel Maximum allowed Macro Layer pilot Interference level per carrier (dBm) above which an alarm is triggered. update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to -15). Notification: None FAP Default value: -65 RMS Default value:-65 RMS Property: FC-MAX-MACRO-PILOT-INTERFERENCE Management level: Solution or Customer

MaxZAP_RSCP_Level Maximum allowed level of interference (dBm) on a particular scrambling code, above which alarm is triggered. update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: -150 to -50). Notification: None FAP Default value: -90 RMS Default:-65 RMS Property: MAX-ZAP-RSCP-LEVEL Management level: Default

NodeBNoiseFloor Noise floor for a typical Node B on the macro network (units of 0.1dBm) update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: -1700 to -500). Notification: None FAP Default value: -1027 RMS Default value:-1027/ RF Profile v2.3 RMS Property: NODE-B-NOISE-FLOOR Management level: Deployment specific



Object Parameter Description ULNoiseRiseMargin Margin to ensure that the noise rise caused by multiple

Home-UEs is within acceptable limits (units of 0.1dB) update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 300). Notification: None FAP Default value: 150 RMS Default value: 150 /RF Profile v 2.3 RMS Property: UL-NOISE-RISE-MARGIN Management level: Deployment specific

StraddledUplinkNoiseRiseMargin Margin to ensure that the noise rise caused by multiple Home-UEs is within acceptable limits (units of 0.1dB). This parameter is used for straddled carriers. update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 300). Notification: None FAP Default value: 150 RMS Default value:N/A RMS Property:N/A Management level: N/A

SlavingZAPRange Minimum path-loss to a ZAP for it to be considered for slaving power levels (dBm) update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Integer. (Range: 10 to 150). Notification: None FAP Default value: 75 RMS Default value:10 RMS Property: FC-SLAVING-ZAP-RANGE Management level: Default

SignificantChangeEventsEnable Enables or disables RRM significant change algorithms that will trigger immediate re-run of full Downlink Monitor Mode if a significant RF environment change is detected --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value: TRUE / RF Profile v. 2.3 RMS Property: SIGNIFICANT-CHANGE-EVENTS-ENABLE Management level: Deployment specific or Default

CarrierChangeThreshold Difference in current DL interference on a carrier to indicate a significant increase in DL interference level (units of 0.1dB) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 300). Notification: None FAP Default value: 150 RMS Default value:N/A RMS Property:N/A Management level: Default

ClearCarrierULTxPower UL Tx power that the RRM algorithm will initially set if it detects a clear carrier (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 33). Notification: None



163 UBS-44-57-004

Object Parameter Description FAP Default value: 10 RMS Default value:10 /RF Profile v 2.3 RMS Property: CLEAR-CARRIER-ULTX-POWER Management level: Deployment

SafeDLPower DL power that the RRM algorithm initially sets on a carrier with poor QoS (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: -40 to 30). Notification: None FAP Default value: -14 RMS Default value:N/A RMS Property:N/A Management level: Default

SafeULTxPower UL Tx power that the RRM algorithm initially sets on a carrier with poor QoS (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 33). Notification: None FAP Default value: -30 RMS Default value:N/A RMS Property:N/A Management level: Default

MinRSCP The absolute minimum RSCP value the HNB aims to achieve (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to -50). Notification: None FAP Default value: -100 RMS Default value:N/A RMS Property:N/A Management level: Default

AdaptOnVoiceOnly InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE/ RF Profile v. 2.3 Modify RMS Property: ADAPT-ON-VOICE Management level: Deployment

StationaryThreshold InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 20). Notification: None FAP Default value: 6 RMS Default value:N/A RMS Property:N/A Management level: N/A

LocationChangeThreshold Percentage of neighbour cells that need to change in order to trigger the LocationChange alarm. Value of 0 disables the alarm. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 100




LocationChangeBehaviour Action to take after raising the LocationChange alarm: - "Continue with service" - "Inhibit service" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Continue with service" RMS Default value:N/A RMS Property:N/A Management level: N/A

OverrideLocationChangeServiceInhibition If the HMS asserts this parameter then any detected location change processing shall be ignored, which may result in the cell becoming operational - the OpState shall be updated accordingly --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InvalidCountryBehaviour Action to take after raising the InvalidCountry alarm: - "Continue with service" - "Inhibit service" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Continue with service" RMS Default value:N/A RMS Property:N/A Management level: N/A

OverrideInvalidCountryServiceInhibition If the HMS asserts this parameter then the invalid country detection processing shall be ignored which may result in the cell becoming operational - the OpState shall be updated accordingly --- RMS Access: READ/WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

IPTHandoffTimer Time in seconds that RRM waits before handing over timing to IPT during long calls. Set to zero to disable handoff during calls. Values below 15 minutes (900s) are not recommended. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 86400). Notification: None FAP Default value: 3600 RMS Default value:N/A RMS Property:N/A Management level: Default



165 UBS-44-57-004

Object Parameter Description ScramblingCodeSelectionMethod Type of scrambling code selection algorithm used by the

AP: - "Least Interference" : Select code with least interference from the AllowedCodesList - "Highest Prob Undetected Code" : Select highest probability undetected code from macro neighbour lists. If no macro cells detected, AP reverts to algorithm 0 update to this parameter will trigger a full radio scan. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Least Interference" RMS Default value:N/A RMS Property:N/A Management level: N/A

MinSignificantChangeRSCP The minimum RSCP level that will trigger a significant change event when detected by Fast Sniff as the new strongest cell (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: -120 to -50). Notification: None FAP Default value: -105 RMS Default value:N/A RMS Property:N/A Management level: Default

RSCPRSSIChangeHysteresis Configures the amount of change in RSCP (or RSSI for GSM cells) that Fast Sniff must detect before the RSCP/RSSI is updated in the database and decisions about the new strongest cell for registration purposes updated. Setting to a very large value effectively disables neighbour list RSCP/RSSI updates from Fast Sniff unless a cell disappears completely --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 3 RMS Default value:N/A RMS Property:N/A Management level: Default

RSCPRSSIMeasurementAveragingCoefficient RSCP/RSSI measurement averaging coefficient, used for calculation of exponential moving average value for fast sniff measurements of neighbour cells. Value is expressed in units of 0.1, with 1 representing 0.1 and 10 representing 1.0. Value of 1.0 disables the averaging of fast sniff measurements. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 10). Notification: None FAP Default value: 1 RMS Default value: 1/ RF Profile v. 2.3 RMS Property: RSCPRSSI-MSMT-AVG-COEFT Management level: Deployment

GSMNeighbourListType Optional configuration for use of GSM neighbours: - "Reselection and handout" - "Reselection only" - "Handout only" - "Ignore" (i.e. use for timing and power adaptation only) ---



Object Parameter Description RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Reselection and handout" RMS Default value: Reselection and handout / RF Profile v. 2.3 RMS Property: GSM-NEIGHBOUR-LIST-TYPE Management level: Deployment specific or Customer

GSMHandoverPriority Optional configuration to specify the relative handover priority for femto to GSM handover relative to femto to UMTS macro handover on the configured UMTS frequencies. 1 is the highest priority and 12 the lowest priority. The default value of 0 means that this field should be ignored and the 'Service Handover' IE received from the core network should be used to determine the relative priority of GSM vs UMTS handover. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 12). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxFrequencyConfigEntries The maximum number of entries in the .CellConfig.UMTS.RAN.RF.X_UBIQUISYS_RRMProfile.FrequencyConfig.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 12). Notification: None FAP Default value: 12 RMS Default value:N/A RMS Property:N/A Management level: N/A

FrequencyConfigNumberOfEntries The number of entries in the .CellConfig.UMTS.RAN.RF.X_UBIQUISYS_RRMProfile.FrequencyConfig.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 12). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UpperIndoorPathlossLimit Measurement reports with a path-loss above this value will be excluded from the power adaptation histograms (dBm) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 170). Notification: None FAP Default value: 100 RMS Default Value: 100 RMS Property: FC-UPPER-INDOOR-PATHLOSS-LIMIT Management level: Solution or Customer

ManualCPICHOffset CPICH Offset in dB applied to the initial value of PCPICHPowerInUse generated by RRMto generate the final value of PCPICHPowerInUse used to configure CPICH coverage --- RMS Access: READ/WRITE Type: Integer. (Range: -9 to 9). Notification: None FAP Default value: 0



167 UBS-44-57-004

Object Parameter Description RMS Default value:N/A RMS Property:N/A Management level: Default or System or N/A

PercentageTotalPowerForCPICH The percentage of the total downlink power that has been allocated to the CPICH channel, according to the following enumeration: 0: 2.5%; -16dB: 25 1: 3.2%; -15dB: 32 2: 4.0%; -14dB: 40 3: 5.0%; -13dB: 50 4: 6.3%; -12dB: 63 5: 7.9%; -11dB: 79 6: 10.0%; -10dB: 100 7: 12.6%; -9dB: 126 8: 15.8%; -8dB: 158 9: 20.0%; -7dB: 200 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 9). Notification: None FAP Default value: 6 RMS Default value:N/A RMS Property:N/A Management level: Default or System

AutoDiscoveredOtherHNBPrimaryScramblingCodesNumberOfEntries

Number of entries in the AutoDiscoveredOtherHNBPrimaryScramblingCodes table --- RMS Access: READ Type: Integer. (Range: 0 to 12). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property: N/A Management level:N/A

BlackListedLAIsNumberOfEntries Number of entries in the BlacklistedLAIs table --- RMS Access: READ Type: Integer. (Range: 0 to 4). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property: N/A Management level:N/A

DetSet_EcNoThreshold Minimum EcNo reported by UEs for a detected set neighbour, for the neighbour to be considered a valid neighbour candidate. --- RMS Access: READ/WRITE Type: Integer. (Range: -24 to 0). Notification: None FAP Default value: -11 RMS Default value:-11 RMS Property: FC-DET-SET-EC-NO-THRESHOLD Management level: Default

DetSet_Hysteresis1E Defines the hysteresis for intra-freq HO measurement when the UE is in Cell-DCH state. Actual values of the range are 0.0 to 7.5 in steps of 0.5. The value of HysteresisEvent1e divided by 2 yields the actual value of the hysteresis. 3GPP-TS.25.331 Section 10.3.7.39 and Section 14.1.2 --- RMS Access: READ/WRITE



Object Parameter Description Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 4 RMS Default value:4 RMS Property: FC-DET-SET-HYSTERESIS-1E Management level: Default

DetSet_RSCPThreshold Minimum RSCP reported by UEs for a detected set neighbour, for the neighbour to be considered a valid neighbour candidate. --- RMS Access: READ/WRITE Type: Integer. (Range: -115 to -25). Notification: None FAP Default value: -105 RMS Default value:-105 RMS Property: FC-DET-SET-RSCP-THRESHOLD Management level: Default

DetSet_TimeToTrigger1E Defines the time-to-trigger in milliseconds for intra-freq HO measurement when the UE is in Cell-DCH state. Only the following values are considered valid: 0, 10, 20, 40, 60, 80, 100, 120, 160, 200, 240, 320, 640, 1280, 2560, 5000 Any value other than those and the CPE MUST reject the request. 3GPP-TS.25.331 Section 10.3.7.39 and Section 10.3.7.64 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 15). Notification: None FAP Default value: 14 RMS Default value:14 RMS Property: FC-DET-SET-TIME-TO-TRIGGER-1E Management level: Default

OtherHNBAutoDiscovery Enables or disables auto classification of other HNBs based on set classification policy (OTA LAI or P-CPICH Tx Power criteria). Possible enumerations are: Disabled UseOtherHNBOTALAIs UseOtherHNBCPICHTxPowerThreshold When Disabled, the table AutoDiscoveredOtherHNBPrimaryScramblingCodes will be populated with auto discovered HNB cells that are not part of the ProvisionedOtherHNBPSC's OR in the provisioned NeighbourList OR in the Allowed UARFCN, PSC combination. This is currently limited to Cisco HNB's that are transmitting the SIB proprietary extension. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "UseOtherHNBCPICHTxPowerThreshold" RMS Default value:UseOtherHNBOTALAIs RMS Property: FC-OTHER-HNB-AUTO-DISCOVERY Management level: Default

OtherHNBOTALAIsNumberOfEntries Number of entries in the OtherHNBOTALAIs table --- RMS Access: READ Type: Integer. (Range: 0 to 4). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OtherHNBPCPICHTxPowerThreshold The AP will classify any neighbours with P-CPICH Tx



169 UBS-44-57-004

Object Parameter Description Power in dBm equal or below this threshold as HNBs. --- RMS Access: READ/WRITE Type: Integer. (Range: -10 to 50). Notification: None FAP Default value: 14 RMS Default value:14 RMS Property: FC-OTHER-HNB-TX-POWER-THRESHOLD Management level: Default

StaleIntraNeighbourGraceWindow Time to live value for intra frequency neighbours which are considered as stale. The AP waits for this many Intra frequency periodic measurement reports before declaring a neighbour redundant, once the neighbour is flagged as stale by network listen. A neighbour is declared redundant if none of the Intra frequency measurement reports during this period include measurements for this neighbour. A stale neighbour is promoted back to online state, by any of the following: - an Intra frequency measurement report including measurements for this neighbour, - network listen --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 460800). Notification: None FAP Default value: 57600 RMS Default value:57600 RMS Property: FC-INTRA-NEIGHBOUR-GRACE-WINDOW Management level: Default

StaleNonIntraNeighbourGraceWindow Time to live value for inter-frequency and inter-RAT neighbours which are considered as stale. The AP waits for this many Inter frequency periodic measurement reports before declaring a neighbour redundant, once the neighbour is flagged as stale by network listen. A neighbour is declared redundant if none of the Inter frequency periodic measurement reports during this period include measurements for this neighbour. Note Inter frequency measurement reports are activated only after FAP enables compressed mode on UE. A stale neighbour is promoted back to online state, by any of the following: - an Inter frequency measurement report including measurements for Inter frequency neighbour and an Inter RAT measurement report including measurements for Inter RAT neighbour, - network listen --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 460800). Notification: None FAP Default value: 5760 RMS Default value:57600 RMS Property: FC-NON-INTRA-NEIGHBOUR-GRACE-WINDOW Management level: Default

UnclassifiedPrimaryScramblingCodesNumberOfEntries

Number of entries in the UnclassifiedPrimaryScramblingCodes table --- RMS Access: READ Type: Integer. (Range: 0 to 12). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A




PathLossForCongestedTargetPSIuReleaseRequest

Path loss in dB estimated by the AP based on UE measurement reports for neighbour cells (SON.Peers) below which the AP will initiate a PS Iu release request if an attempted PS or MutiRAB relocation preparation procedure fails due to congestion at target. A value of 30dB will disable this feature. --- RMS Access: READ/WRITE Type: Integer. (Range: 30 to 100). Notification: None FAP Default value: 70 Management level: Deployment specific

Table 61 RRM Profile

4.9.13.9.2 RRM Profile: Frequency Configuration

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.FrequencyConfig

Table containing optional configuration for each DL frequency specified in CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL. If an entry does not exist in this table for a given entry in the CellConfig.UMTS.RAN.FDDFAP.RF.UARFCNDL parameter then the defaults specified below will apply

UARFCNDL Central downlink channel frequency: 412-10838. --- RMS Access: READ/WRITE Type: Integer. (Range: 412 to 10838). Notification: None FAP Default value: 412 RMS Default value: 412/ RF Profile v. 2.3 RMS Property: RRM-ARFCN-i-DOWNLINK Management level: Deployment specific

NeighbourListType Optional configuration for use of neighbours on this frequency: - "Reselection and handout" - "Reselection only" - "Handout only" - "Ignore" (i.e. use for timing and power adaptation only) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Reselection and handout" RMS Default value: Reselection and handout/ RF Profile v. 2.3 RMS Property: RRM-NEIGHBOUR-i-LIST-TYPE Management level: Deployment specific or Customer

CarrierDeploymentType Non standard carrier deployment type. Enumeration of: - GSM overlap carrier - Straddled carrier - Normal carrier --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Normal carrier" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 62 RRM Profile: Frequency Configuration



171 UBS-44-57-004

4.9.13.9.3 RRM Profile: Sniffing Functionality

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.SNIFFProfile

Object name

OPLMNSearchEnable Enable or disable the search for alternate WCDMA carriers during sniff mode in order to find a macro cell to use as a timing reference --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value: TRUE/ RF Profile v. 2.3 RMS Property: ENABLE-SNIFF-OPLMN-SEARCH Management level: Deployment specific

OPLMNAllowedBandList Comma-separated list of strings (maximum item length 64). Each item is a UMTS Band to consider for the OPLMN search Each band is identified in by a roman numeral 3GPP-TS.25.104. If an empty string then no specific UMTS band is provided, meaning that the FAP is allowed to consider all available bands. The order of the band indicator has no significance. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value: N/A RMS Property: SNIFF-OPLMN-BAND-LIST Management level: Deployment specific

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.GSMSniffProfile

Object name

OPLMNSearchEnable Enable or disable the search for alternate GSM carriers during sniff mode in order to find a macro cell to use as a timing reference --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value: TRUE/ RF Profile v. 2.3 RMS Property: ENABLE-GSM-SNIFF-OPLMN-SEARCH Management level: Deployment specific or Customer

Table 63 RRM Profile: Sniffing Functionality

4.9.13.9.4 RRM Profile: RRM Status

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMStatus

Object name

MaxDLPowerWarning When set, this indicates that the RRM algorithm is using a DL power equal to the max value in the RRM profile --- RMS Access: READ Type: Boolean.



Object Parameter Description Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxULTxPowerWarning When set, this indicates that the RRM algorithm is using a UL Tx power equal to the max value in the RRM profile --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MinDLPowerWarning When set, this indicates that the RRM algorithm is using a DL power equal to the min value in the RRM profile --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MinULTxPowerWarning When set, this indicates that the RRM algorithm is using a UL Tx power equal to the min value in the RRM profile --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 64 RRM Profile: RRM Status

4.9.13.9.5 RRM Profile: Poor RF QoS Alarm Configuration

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.PoorRFQoSAlarmConfig

Object name

HNBInterference

Alarm Configuration: 0 - Disable alarm 1 - Enable alarm safe mode 2 - Enable alarm no safe mode --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Enable alarm safe mode" RMS Default value: Enable alarm no safe mode / RF Profile v. 2.3 RMS Property: HNB-INTERFERENCE Management level: Deployment

MacroInterference Alarm Configuration:



173 UBS-44-57-004

Object Parameter Description 0 - Disable alarm 1 - Enable alarm safe mode 2 - Enable alarm no safe mode --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Enable alarm safe mode" RMS Default value: Enable alarm no safe mode / RF Profile v. 2.3 RMS Property: MACRO-INTERFERENCE Management level: Deployment

UnknownWidebandRFInterference

Alarm Configuration: 0 - Disable alarm 1 - Enable alarm safe mode 2 - Enable alarm no safe mode --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Enable alarm safe mode" RMS Default value: Enable alarm no safe mode / RF Profile v. 2.3 RMS Property:UNKNOWN-WIDEBAND-RF-INTERFERENCE Management level: Deployment

MacroSIBDecodeFailure

Alarm Configuration: 0 - Disable alarm 1 - Enable alarm safe mode 2 - Enable alarm no safe mode --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Enable alarm safe mode" RMS Default value: Enable alarm no safe mode / RF Profile v. 2.3 RMS Property: MACRO-SIB-DECODE-FAILURE Management level: Deployment

Table 65 RRM Profile: Poor RF QoS Alarm Configuration

4.9.13.9.6 Enhanced Poor RF QoS Alarms

The feature is covered in the following document: [UBS-44-12-012] UBS-44-12-012 Safe Mode and Poor RF QoS 4.9.13.9.7 RRM Profile: Load Based Coverage Tuning

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.LoadBasedCoverageTuning

This object controls the Ubiquisys proprietary load based coverage algorithms

CongestionMonitoringRecoveryPeriod

Accumulation period for RRC Connection Reject count to trigger coverage recovery (hours) --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 672). Notification: None FAP Default value: 168 RMS Default value:N/A



Object Parameter Description RMS Property:N/A Management level: Default

CongestionMonitoringRecoveryPeriodCount

Time elapsed since the last CongestionMonitoringRecoveryPeriod was started, in units of 15minutes --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default

CongestionMonitoringReductionPeriod

Accumulation period for RRC Connection Reject count to trigger coverage reduction (hours) --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 168). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: Default

CongestionMonitoringReductionPeriodCount

Time elapsed since the last CongestionMonitoringReductionPeriod was started, in units of 15minutes --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default

EnableCPICHBoosting

If true, CPICH power is set to 7dB below max allowed transmit power, rather than default 10dB. Only settable on unit restricted to 4 calls. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE/ RF Profile v. 2.3 RMS Property: ENABLE-CPICH-BOOSTING Management level: Deployment specific

EnableLoadBasedCoverageTuning

If true, enables load based coverage auto-tuning. Only settable if not in Enterprise mode. Enabling or disabling of this parameter would trigger cell restart. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE/ RF Profile v. 2.3 RMS Property: ENABLE-LOAD-BASED-COVERAGE-TUNING Management level: Deployment

MaxLoadBasedTxPowerContraction

Maximum Tx power contraction due to load, relative to the minimum allowed



175 UBS-44-57-004

Object Parameter Description DL power (dB) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default

MinCPICHOffset

Minimum CPICH offset relative to MaxTXPowerInUse (dB): 0: -10dB 1: -11dB 2: -12dB 3: -13dB 4: -14dB 5: -15dB 6: -16dB --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 6). Notification: None FAP Default value: 4 RMS Default value:N/A RMS Property:N/A Management level: Default

RRCRejectThreshold

If the number of Rejects in the reduction accumulation period is greater than this, reduction is triggered. If the number of Rejects in the recovery accumulation period is smaller than this, recovery is triggered. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 7200). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: Default

RRCRejectionsRecoveryCount

Number of RRC rejections registered since the last CongestionMonitoringRecoveryPeriod was started. --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Default

RRCRejectionsReductionCount

Number of RRC rejections registered since the last CongestionMonitoringReductionPeriod was started. --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A



Object Parameter Description Management level: Default

TargetMaxFAPTxPowerInUse

The TargetMaxFapTxPowerInUse that RRM should apply after a CELL RESTART This value should be initialised to MaxFapTxPowerInUse. The actual value set for MaxFapTxPowerInUse will be different to that set here if targetPCPICHOffset increases or decreases until the next DLMM cycle. The definition is identical to MaxFAPTxPowerInUse --- RMS Access: READ/WRITE Type: Integer. (Range: -400 to 300). Notification: None FAP Default value: 100 RMS Default value:N/A RMS Property:N/A Management level: Default

Table 66 RRM Profile: Load Based Coverage Tuning

4.9.13.9.8 RRM Profile: Discovery of Scrambling Codes

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.AutoDiscoveredOtherHNBPrimaryScramblingCodes

A list of UARFCN:PSC pairs which the HNB has detected to be in use by other HNBs in the locality. If OtherHNBAutoDsicovery is enabled, the HNB appends these tuples with the UARFCN:PSC pairs defined in InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF: .UARFCNDL and .PrimaryScramblingCode and InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_ProvisionedOtherHNBPrimaryScramblingCodes: .DLUARFCN .PrimaryScramblingCodes in its consideration of HNB neighbours. The HNB will append to the list of primary scrambling codes in the order of discovery.

UARFCNDL

Central downlink channel frequency: 412-10838. --- RMS Access: READ Type: Integer. (Range: 412 to 10838). Notification: None FAP Default value: 412 RMS Default value:N/A RMS Property:N/A Management level: N/A


Comma-separated list (maximum length 32) of strings. Each item is a Primary DL Scrambling Code used by the FDD mode cell with a numeric range



177 UBS-44-57-004

Object Parameter Description between 0 and 511 inclusive. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

4.9.13.9.9 RRM Profile: LAIs


InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.BlackListedLAIs

The AP will exclude any neighbours operating on these PLMNID LAI combination from the InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse

PLMNID

PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: Deployment specific

LACs

Comma-separated list of strings representing Location Area Codes (LACs). Each item is a LAC or LAC range. LAC ranges are inclusive and expressed in the following format: <Start-value>".."<End-value> Each LAC consists of up to 5 numerical characters. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6. The following are examples of the valid LAC formats: "64000" (one list item with single value for LAC) "64000..64100, 64101" (two list items, first item has a LAC range) "64000, 64001" (two list items, both items have a specific LAC value) "64000..64100" (one list item both have a LAC range) --- RMS Access: READ/WRITE Type: String. (Length: 0 to 4098 characters). Notification: None



Object Parameter Description FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: Deployment specific

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.OtherHNBOTALAIs

The AP will classify any neighbours operating on these LAIs as HNBs. Both PLMNID and LAC need to be matched in order for the discovered cell to be considered as a HNB. A valid match will mean the HNB is added to the AutoDiscoveredOtherHNBPrimaryScramblingCodesTable

PLMNID

PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value: RMS Property: FC-OTHER-HNB-OTA-i-PLMNID Management level: Deployment specific

LACs

Comma-separated list of strings representing Location Area Codes (LACs). Each item is a LAC or LAC range. LAC ranges are inclusive and expressed in the following format: <Start-value>".."<End-value> Each LAC consists of up to 5 numerical characters. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6. The following are examples of the valid LAC formats: "64000" (one list item with single value for LAC) "64000..64100, 64101" (two list items, first item has a LAC range) "64000, 64001" (two list items, both items have a specific LAC value) "64000..64100" (one list item both have a LAC range) --- RMS Access: READ/WRITE Type: String. (Length: 0 to 4098 characters). Notification: None FAP Default value: "" RMS Default value: RMS Property: FC-OTHER-HNB-OTA-i-LAC Management level: Deployment specific



179 UBS-44-57-004

4.9.13.9.10 RRM Profile: Unclassified Primary Scrambling Codes


InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.UnclassifiedPrimaryScramblingCodes

A list of UARFCN:PSC pairs which the HNB has been unable to classify (relevant SIBs cannot be decoded). The neighbouring cells operating on these PSCs are not valid for over-the-air scynchronisation.


Comma-separated list (maximum length 32) of strings. Each item is a Primary DL Scrambling Code used by the FDD mode cell with a numeric range between 0 and 511 inclusive. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A

UARFCNDL

Central downlink channel frequency: 412-10838. --- RMS Access: READ Type: Integer. (Range: 412 to 10838). Notification: None FAP Default value: 412 RMS Default value:N/A RMS Property:N/A

4.9.13.9.11 RLC Configuration

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_HSUPAConfig

This object contains HSDPA specific parameters

enable_ue_edch_rate_control

Enable FEAT-1232 - Individual rate control for UE's based on path loss to source or path loss to neighbouring HNB --- RMS Access: READ/WRITE Type: Boolean Notification: None FAP Default value: False RMS Default value: FALSE / RF Profile v.2.4 RMS Property: FC-ENABLE-UE-EDCH-RATE-CONTROL Management level: Deployment

4.9.13.9.12 Dynamic DL Power Allocation

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLPowerAllocation

Control parameters for the DL Power allocation algorithms which dynamically adjust the power allocated to DCH and HS channels.

UpdatePeriod Period between running dynamic DL power algorithms. This time should take into account processing delay between RRM algorithm running in the host processor, the modem responding to RRM results, signalling new



Object Parameter Description settings over the air and any delays in the UE. To a lesser extent this parameter should factor in a margin of at least 2 TTIs to cater for the 2 HS-SCCHs that could be running. (it could take a UE 2 TTI slots before it receives new information when 4 HS sessions are active). --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 50). Notification: None FAP Default value: 50 RMS Default value:N/A RMS Property:N/A Management level: System

HDLPAEnabled Enables or disables the HSDPA dynamic DL power algorithm --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE RMS Property: DYNAMIC-DL-PA-HDLPA-ENABLED Management level: Default

PowerIncreaseTimeToTrigger #Iterations of Dynamic Power update algorithm. When moving to a higher HS profile, Total DPDCH power has to be within the higher HS power profile range for at least this duration before a decision is made to move to such an HS profile. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 50). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Default

PowerDecreaseTimeToTrigger #Iterations of Dynamic Power update algorithm. When moving to a lower HS profile, Total DPDCH power has to be within the lower HS profile power range for at least this duration before a decision is made to move to such an HS profile. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 50). Notification: None FAP Default value: 3 RMS Default value:3 RMS Property: FC-POWER-DECREASE-TTT Management level: Default

MaxHSProfileEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLPowerAllocation.HSProfile.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 10). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A



181 UBS-44-57-004


HSProfileNumberOfEntries The number of entries in the .CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLPowerAllocation.HSProfile.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 5 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLPowerAllocation.HSProfile

List of HS profiles. This should be populated as an ordered list based upon the TotalDPCHPowerMax (smallest to largest)

TotalDPCHPowerMax Upper limit for Total DPDCH power percentage usage range for which this HS profile is valid. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 100 RMS Default value:N/A RMS Property:N/A Management level: System

HSPower Total HS power (HS-PDSCHs + HS-SCCHs) as a percentage of total power --- RMS Access: READ/WRITE Type: Integer. (Range: 10 to 80). Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: System

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLPowerAllocation.HSProfile.1

Object name







Object name




Object name




Object name

TotalDPCHPowerMax Upper limit for Total DPDCH power percentage usage range for which this HS profile is valid. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 60 RMS Default value:N/A RMS Property:N/A



183 UBS-44-57-004




Object name



Table 67 Dynamic DL Power Allocation

4.9.13.9.13 Dynamic UL Power Allocation

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicULPowerAllocation

Parameters for control of dynamic UL power allocation

RTWPAveragingWindow Number of RTWP samples to be used in averaging. 0 disables algorithm --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 20). Notification: None FAP Default value: 3 RMS Default value: 3 / RF Profile v. 2.4 Modify RMS Property: ALPHA-IN-RTWP-AVERAGE-WINDOW Management level: Deployment

DefaultMaxTargetRTWP The Default target RTWP value Range 0..621 in units of 0.1dBm where 0=-112dBm, 621 =-50dBm



Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 621). Notification: None FAP Default value: 580 RMS Default value: 580 / RF Profile v. 2.4 Modify RMS Property: FC-DEFAULT-MAX-TARGET-RTWP Management level: Deployment

WeightingTriggerThreshold1

The weighting trigger threshold as a percentage of maximum to apply weighting backoff margin 1 to the RTWP value. --- RMS Access: READ/WRITE Type: Integer (range: 0 to 100) Notification: None FAP Default value: 60 RMS Default value: 60 RMS Property: FC-WEIGHTING-TRIGGER-THRESHOLD-1 Management level: Deployment





UL_RSSI_EDCH_RateControl

Enabled EDCH Rate control by RSSI aswell as by RAB weight. FEAT-1231 --- RMS Access: READ/WRITE Type: Boolean Notification: None FAP Default value: FALSE RMS Default value: FALSE/ RF Profile v. 2.4 Modify RMS Property: FC-UL-RSSI-EDCH-RATECONTROL Management level: Deployment

Table 68 Dynamic UL Power Allocation

4.9.13.9.14 Dynamic DL-DCH Power Allocation

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_DynamicDLDCHPowerAllocation

Control parameters for the DL Power allocation algorithm which dynamically adjusts the power allocated to the DL DCH channels.

DDLPAEnabled Enables or disables the DCH DL Power Allocation Algorithm. --- RMS Access: READ/WRITE



185 UBS-44-57-004

Object Parameter Description Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: ENABLE-DCH-DL-PAA Management level: Default

DCHPowerDecreaseThreshold Percentage of total power in use by all DCHs which will trigger a decrease in the max DL DCH power. (Units: %) --- RMS Access: READ/WRITE Type: Integer. (Range: 20 to 100). Notification: None FAP Default value: 45 RMS Default value: 45/ RF Profile v. 2.3 Modify RMS Property: DCH-POWER-DECREASE-THRESHOLD Management level: Deployment

DCHPowerIncreaseThreshold Percentage of total power in use by all DCHs which will trigger an increase of the max DL DCH power towards its initial default value. (Units: %) --- RMS Access: READ/WRITE Type: Integer. (Range: 20 to 100). Notification: None FAP Default value: 35 RMS Default value: 35/ RF Profile v. 2.3 RMS Property: DCH-POWER-INCREASE-THRESHOLD Management level: Deployment specific

DCHPowerLimitReductionStep The Max DCH power will be decreased by a fixed step anytime a request to lower Max DCH power is triggered (Units: dB) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 6). Notification: None FAP Default value: 2 RMS Default value: 2 / RF Profile v. 2.3 RMS Property: DCH-POWER-LIMIT-REDUCTION-STEP Management level: Deployment specific

DCHPowerLimitIncreaseStep The Max DCH power will be increased by a fixed step anytime a request to increase Max DCH power is triggered. (Units: dB) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 6). Notification: None FAP Default value: 3 RMS Default value: 3 / RF Profile v. 2.3 RMS Property: DCH-POWER-LIMIT-INCREASE-STEP Management level: Deployment specific

DCHPowerDecreaseSamplesToTrigger The total DCH power has to be above the reduction threshold for a number of samples before a reduction is triggered --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 50). Notification: None FAP Default value: 5 RMS Default value: 5 / RF Profile v. 2.3



Object Parameter Description RMS Property: DCH-POWER-DECREASE-SAMPLE-TO-TRIGGER Management level: Deployment specific

DCHPowerIncreaseSamplesToTrigger The total DCH power has to be below the increase threshold for a number of samples before an increase is triggered --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 50). Notification: None FAP Default value: 10 RMS Default value: 10 / RF Profile v. 2.3 RMS Property: DCH-POWER-INCREASE-SAMPLE-TO-TRIGGER Management level: Deployment specific

LowestMaxDCHPowerAllocation This is the lowest possible value Max DCH Power allocation. Specified as dBs relative to CPICH. --- RMS Access: READ/WRITE Type: Integer. (Range: -35 to 9). Notification: None FAP Default value: -6 RMS Default value: -6 / RF Profile v. 2.3 RMS Property: LOWEST-MAX-DCH-POWER-ALLOCATION Management level: Deployment specific

Table 69 Dynamic DL-DCH Power Allocation

4.9.14 Neighboring Lists Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList

This object contains parameters relating to the neighbor list.

MaxIntraFreqCellEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 200). Notification: None FAP Default value: 200 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxInterFreqCellEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 200). Notification: None FAP Default value: 200 RMS Default value:N/A RMS Property:N/A Management level: N/A

IntraFreqCellNumberOfEntries The number of entries in the



187 UBS-44-57-004

Object Parameter Description .CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 200). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InterFreqCellNumberOfEntries The number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 200). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 70 Neighboring Lists



4.9.14.1.1 Neighbor List Extensions

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList


X_UBIQUISYS_COM_TRNCBaselineReleaseInfo

Layout to be used for "Source RNC To Target RNC Transparent Container" in RELOCATION REQUIRED message depends on release supported by target RNC. "TRNC Baseline Release Info" indicates which release will be used by the FAP in RELOCATION REQUIRED message. The Operator could give the value of the majority RNC release operated on. This parameter could be global or custmized to each HNB and Possible values: Release_99; Release_4; Release_5; Release_6; Release_7 --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Release_99" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 71 Neighbor List Extensions

4.9.14.1.2 Neighbor List Extensions

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList


X_UBIQUISYS_COM_FemtoNeighbourFilteringEnable

Enables Automatic Femto Neighbour Filtering mode. When this is set TRUE, Sniffed femtos are not added to the NeighbourListInUse unless they are manually provisioned as MustInclude by the HMS --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FEMTO-NEIGHBORING-FILTERING-ENABLE Management level : System

X_UBIQUISYS_COM_StaticNeighbourFilteringEnable

Enables Classification of Static Neighbours mode. When this is set TRUE, entries in the NeighbourList.InterFreq may be IntraFreq and are copied to the appropriate NeighbourListInUse based on their UARFCN --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: STATIC-NEIGHBORING-FILTERING-



189 UBS-44-57-004

Object Parameter Description ENABLE Management level : System

Table 72 Neighbor List Extensions

4.9.14.2 Intra-Frequency Neighboring List

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell

Table containing the intra-frequency cell list provided by the ACS. The table contents may be added/deleted/modified during operation, in which case these changes shall be reflected in the broadcast information as soon as possible. At most one enabled entry in this table can exist with a given value for PCPICHScramblingCode.

Table 73 Intra-Frequency Neighboring List



4.9.14.3 Inter-Frequency Neighboring List

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell

Table containing the inter-frequency cell list provided by the ACS. The table contents may be added/deleted/modified during operation, in which case these changes shall be reflected in the broadcast information as soon as possible. At most one enabled entry in this table can exist with the same values for PCPICHScramblingCode and UARFCNDL.

Enable Enables or disables this entry. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-SC-INTER-FREQ-i-ENABLE Management level: Deployment specific or Customer

MustInclude Indicates whether this instance of the neighbor shall be included or excluded in the FAP's NL configuration. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-SC-INTER-FREQ-i-MUST-INCLUDE Management level: Deployment specific or Customer

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:11121 RMS Property: FC-SC-INTER-FREQ-i-PLMNID Management level: Deployment specific or Customer

RNCID RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than 4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit need to have them separated. 3GPP-TS.25.413 Section 9.2.1.39 ---



191 UBS-44-57-004

Object Parameter Description RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-FREQ-i-RNCID Management level: Deployment specific or Customer

CID Cell Identifier (C-id) that identifies a cell within an RNS. This Cell Identifier together with the controlling RNC (RNC-ID) constitutes the UTRAN Cell ID (UCID) and is used to identify a cell uniquely within UTRAN. C-ID is either 12-bit or 16-bit value. 3GPPTS.25.401 Section 6.1.5. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-FREQ-i-CID Management level: Deployment specific or Customer

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:1 RMS Property: FC-SC-INTER-FREQ-i-LAC Management level: Deployment specific or Customer

RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:1 RMS Property: FC-SC-INTER-FREQ-i-RAC Management level: Deployment specific or Customer

URA UTRAN Registration Area (URA) 3GPP-TS.23.401. Indicates to the UE which URA it shall use in case of overlapping URAs. 3GPP-TS.25.331 Section 10.3.2.6 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SC-INTER-FREQ-i-URA Management level: Deployment specific or Customer




UARFCNUL The UL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell. 3GPPTS.25.433 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16383). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SC-INTER-FREQ-i-UARFCNUL Management level: Deployment specific or Customer

UARFCNDL The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell. 3GPPTS.25.433 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16383). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-FREQ-i-UARFCDL Management level: Deployment specific or Customer

PCPICHScramblingCode Primary CPICH scrambling code. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 511). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-FREQ-i-SCRAMBLING-CODE Management level: Deployment specific or Customer

PCPICHTxPower Primary CPICH Tx power in dBm. Actual values of the power are -10.0 dBm to 50.0 dBm in steps of 0.1 dB. The value of PCPICHTxPower divided by 10 yields the actual value of the power. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 2.2.33 --- RMS Access: READ/WRITE Type: Integer. (Range: -100 to 500). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-FREQ-i-PCPICH-TX-POWER Management level: Deployment specific or Customer

X_UBIQUISYS_COM_TxDiversityInd Indicates whether the cell is using transmit diversity --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: SC-INTER-FREQ-i-TX-DIVERSITY-INDICATOR Management level: Deployment specific or Customer

X_UBIQUISYS_COM_MaxUlTxPower Max permitted UE Tx power: -50-33 (dBm) as broadcast in SIB 3 3GPP-TS.25.331 10.3.6.39



193 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 33). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: SC-INTER-FREQ-i-MAX-UL-TX-POWER Management level: Deployment specific or Customer

Layer QSS: Type of neighbour cell: - Macro: This neighbour is valid for OTA synchronisation. Macro mobility offsets will be applied against this neighbour - Other: This neighbour is not valid for OTA synchronisation. Macro mobility offsets will NOT be applied against this neighbour. - Unknown: The AP will use FEAT-1124 to locally classify the neighbour as Macro or Other --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Unknown" RMS Default value:”Unknown” RMS Property: FC-SC-INTER-FREQ-i-LAYER Management level: Deployment specific or Customer

Table 74 Inter-Frequency Neighboring List

4.9.14.4 Inter RAT NeighbouringList

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell

The inter-RAT cell lists separated by technology. 3GPP-TS.25.331 Section 10.3.7.23

MaxGSMEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 64). Notification: None FAP Default value: 64 RMS Default value:N/A RMS Property:N/A Management level: N/A

GSMNumberOfEntries Number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 64). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 75 Inter RAT NeighburingList



4.9.14.5 GSM NeighborList

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterRATCell.GSM

Table containing the inter-RAT cell list for GSM provided by the ACS. The table contents may be added/deleted/modified during operation, in which case these changes shall be reflected in the broadcast information as soon as possible. At most one enabled entry in this table can exist with a given value for BCCHARFCN.

Enable Enables or disables this entry. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-SC-INTER-RAT-i-ENABLE Management level: Deployment specific or Customer

MustInclude Indicates whether this instance of the neighbor shall be included or excluded in the FAP's NL configuration. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: FC-SC-INTER-RAT-i-MUST-INCLUDE Management level: Deployment specific or Customer

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:11111 RMS Property: FC-SC-INTER-RAT-i-PLMNID Management level: Deployment specific or Customer

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:1 RMS Property: FC-SC-INTER-RAT-i-LAC Management level: Deployment specific or Customer

RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section



195 UBS-44-57-004

Object Parameter Description 9.2.3.7 --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-RAT-i-RAC Management level: Deployment specific or Customer

BSIC BSIC of the cell per 3GPP-TS.23.003 [8], consisting of: Bit 7:6 - not used ("00") Bit 5:3 - NCC (PLMN Color Code) Bit 2:0 - BCC (BS color code) For example, if NCC is 7 and BCC is 2 you would have 00111010 (binary) or 0x3A (hex), and the value of this parameter would be 58. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-RAT-i-BSIC Management level: Deployment specific or Customer

CI Cell ID of the cell per 3GPP-TS.23.003 Section 4.3.1. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-RAT-i-CI Management level: Deployment specific or Customer

BandIndicator Indicates how to interpret the BCCH ARFCN. Enumeration of: - "GSM 850" - "GSM 900" - "DCS 1800" - "PCS 1900" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "DCS 1800" RMS Default value:GSM 900 RMS Property: FC-SC-INTER-RAT-i-BAND Management level: Deployment specific or Customer

BCCHARFCN ARFCN of this cell. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1023). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-SC-INTER-RAT-i-BCCH-ARFCN Management level: Deployment specific or Customer

X_UBIQUISYS_COM_MaxUlTxPower Max permitted UE Tx power: -50-33 (dBm) as broadcast in SIB 3 3GPP-TS.25.331 10.3.6.39 --- RMS Access: READ/WRITE Type: Integer. (Range: -50 to 33). Notification: None FAP Default value: 0



Object Parameter Description RMS Default value:0 RMS Property: SC-INTER-RAT-i-MAX-TX-POWER Management level: Deployment specific or Customer

Table 76 GSM NeighborList

4.9.14.6 Neighbor List in Use

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse

This object contains parameters relating to the neighbor list used by the FAP based on its self-configuration capability and .CellConfig.UMTS.RAN.FDDFAP.NeighborList. configuration of adding and excluding cells.

MaxIntraFreqCellEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 32). Notification: None FAP Default value: 32 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxInterFreqCellEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 32). Notification: None FAP Default value: 32 RMS Default value:N/A RMS Property:N/A Management level: N/A

IntraFreqCellNumberOfEntries The number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InterFreqCellNumberOfEntries The number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_InterFreqMacroCellNumberOfEntries

The number of macro cell entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.InterFreqCell.{i}. table. ---



197 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 200). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IntraFreqMacroCellNumberOfEntries

The number of macro cell entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborList.IntraFreqCell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 200). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_DominantNeighbourMacroIndex

Index into the NeighborListInUse.IntraFreqCell or NeighborListInUse.InterFreqCell list for the strongest neighbour (to allow LAC/RAC/PLMN etc to be read) Value -1 means that no macros have been detected. 0-31 corresponds to entries in the IntraFreqCell list 32-63 corresponds to entries in the InterFreqCell list --- RMS Access: READ Type: Integer. (Range: -1 to 63). Notification: None Value set at runtime FAP Default value:-1 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_DominantNeighbourMacroInterFreqIndex

Index into the NeighborListInUse.InterFreqCell list for the strongest macro inter-freq neighbour (to support emergency redirection) Value -1 means that no inter-freq cells have been detected. 10-19 corresponds to entries in the InterFreqCell list --- RMS Access: READ Type: Integer. (Range: -1 to 19). Notification: None Value set at runtime FAP Default value:-1 RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.IntraFreqCell

Table containing the intra-frequency cell list. At most one entry in this table can exist with a given value for PCPICHScramblingCode.

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ



Object Parameter Description Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RNCID RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than 4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit need to have them separated. 3GPP-TS.25.413 Section 9.2.1.39 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CID C-ID of the intra-freq neighbour cell 3GPP-TS.25.401 Section 6.1.5. If RNCID is larger than 4095, then CID will be 12 bits (i.e. a range of [0:4095]), else CID is 16 bits long (i.e. range of [4096:65535]). This is needed to facilitate Femto to Macro handover. Used in 3GPP-TS.25.413 Section 9.2.1.28 as part of Target Cell ID. --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None



199 UBS-44-57-004


URA UTRAN Registration Area (URA) 3GPP-TS.23.401. Indicates to the UE which URA it shall use in case of overlapping URAs. 3GPP-TS.25.331 Section 10.3.2.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PCPICHScramblingCode Primary CPICH scrambling code. --- RMS Access: READ Type: Integer. (Range: 0 to 511). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CPICHEcNo

Measured EcNo. (energy per chip to interference power density) in dB received in the downlink pilot channel. Actual values of the range are -24.0 dB to 0.0 dB in steps of 0.5 dB. The value of CPICHEcNo divided by 2 yields the actual value of the range. 3G --- RMS Access: READ Type: Integer. (Range: -48 to 0). Notification: None FAP Default value: -48 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CPICHRSCP

Received signal level in dBm of the CPICH channel. (Ref. 3GPP-TS 25.133) --- RMS Access: READ Type: Integer. (Range: -120 to -25). Notification: None FAP Default value: -120 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellType

The classification of the cell, enumerations as follows:- DETECTED_MACRO DERIVED_MACRO INFERRED_MACRO DETECTED_HNB RECIPROCATED_HNB DERIVED_HNB INFERRED_HNB DERIVED_GSM DETECTED_GSM UNKNOWN UNKNOWN_OTHER UNKNOWN_MACRO UE_REPORTED_HNB



Object Parameter Description UE_REPORTED_MACRO Note: RRM sets this parameter when the RRM scan has been performed on this cell. If the cellType is "UNKNOWN", this indicates a cell that is present in this list because it was provisioned by the HMS in the HMSList and was not scanned. RRC uses this information to suppress the check of the cell Ec/No against the X_UBIQUISYS_COM_ThresholdUMTSMacro since HMS provisioned cells are always candidates for relocation --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "UNKNOWN" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IsProvisioned

Deprecated functionality. CellType set to INFERRED indicates that cell is provisioned. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IsOnGrid

Indicates if the neighbour has been located on the grid. (if this AP has detected this AP then this flag will be set true) --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_RemainingCountToLive

Remaining count to live value for a neighbour which registered as stale (NeighbourState = 1:Stale). This value is set to StaleIntraNeighbourGraceWindow (in RRM profile) value when the neighbour state transits from online to stale (NeighbourState:: 0:Online -) 1:Stale). The count will be decremented for every periodic intra-frequency measurement report received where the cell psc is not measured. --- RMS Access: READ Type: Integer. (Range: 0 to 460800). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_NeighbourState

A neighbour classified as stale if it is no longer detected by network listen. A stale neighbour is promoted back to online state by any of the following: - a UE measurement report including measurements for this neighbour's UARFCN:PSC, - network listen



201 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "0_Online" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellMobilityCriterion

Configuration for this cell as to what it should be used for - "Reselection and handout" - "Reselection only" - "Handout only" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Reselection and handout" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellAddedAtTime

Timestamp when this cell was added. In the case of a full NL, a new cell is defined as when the cid / rnc_id is modified. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellLastModifiedTime

Timestamp when this cell was last modified in any way e.g RemainingTimeToLive --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_PCPICHTxPower

Primary CPICH Tx power in dBm. Actual values of the power are -50.0 dBm to 50.0 dBm in steps of 0.1 dB. The value of PCPICHTxPower divided by 10 yields the actual value of the power. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 2.2.33. Used by RRC to determine path loss --- RMS Access: READ Type: Integer. (Range: -500 to 500). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterFreqCell

Table containing the inter-frequency cell list. At most one entry in this table can exist with the same values for PCPICHScramblingCode and UARFCNDL.



Object Parameter Description PLMNID PLMN ID consists of Mobile Country Code (MCC) and

Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RNCID RNC-ID of an intra-freq neighbor cell. It uniquely identifies an RNC within a PLMN. Normally, RNC-ID consists of 12 bits (i.e. a range of [0:4095]). However, if the value is larger than 4095, then Extended RNC-ID (range of [4096:65535]) is used in RANAP. The RNC-ID and Extended RNC-ID are combined into a single parameter here as there is no explicit need to have them separated. 3GPP-TS.25.413 Section 9.2.1.39 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CID C-ID of the intra-freq neighbour cell 3GPP-TS.25.401 Section 6.1.5. If RNCID is larger than 4095, then CID will be 12 bits (i.e. a range of [0:4095]), else CID is 16 bits long (i.e. range of [4096:65535]). This is needed to facilitate Femto to Macro handover. Used in 3GPP-TS.25.413 Section 9.2.1.28 as part of Target Cell ID. --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A



203 UBS-44-57-004


RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

URA UTRAN Registration Area (URA) 3GPP-TS.23.401. Indicates to the UE which URA it shall use in case of overlapping URAs. 3GPP-TS.25.331 Section 10.3.2.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNUL The UL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell. 3GPPTS.25.433 --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNDL The DL UTRA Absolute Radio Frequency Channel Number (UARFCN) in an FDD mode cell. 3GPPTS.25.433 --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PCPICHScramblingCode Primary CPICH scrambling code. --- RMS Access: READ Type: Integer. (Range: 0 to 511). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CPICHEcNo

Measured EcNo. (energy per chip to interference power density) in dB received in the downlink pilot channel. Actual values of the range are -24.0 dB to 0.0 dB in steps of 0.5 dB. The value of CPICHEcNo divided by 2 yields the actual value of the range. 3G ---



Object Parameter Description RMS Access: READ Type: Integer. (Range: -48 to 0). Notification: None FAP Default value: -48 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CPICHRSCP

Received signal level in dBm of the CPICH channel. (Ref. 3GPP-TS 25.133) --- RMS Access: READ Type: Integer. (Range: -120 to -25). Notification: None FAP Default value: -120 RMS Default value:N/A RMS Property:N/A Management level: N/A


The classification of the cell, enumerations as follows:- DETECTED_MACRO DERIVED_MACRO INFERRED_MACRO DETECTED_HNB RECIPROCATED_HNB DERIVED_HNB INFERRED_HNB DERIVED_GSM DETECTED_GSM UNKNOWN UNKNOWN_OTHER UNKNOWN_MACRO UE_REPORTED_HNB UE_REPORTED_MACRO Note: RRM sets this parameter when the RRM scan has been performed on this cell. If the cellType is "UNKNOWN", this indicates a cell that is present in this list because it was provisioned by the HMS in the HMSList. RRC uses this information to suppress the check of the cell Ec/No against the X_UBIQUISYS_COM_ThresholdUMTSMacro since HMS provisioned cells are always candidates for relocation --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "UNKNOWN" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_IsProvisioned

Deprecated functionality. CellType set to INFERRED indicates that cell is provisioned. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A


Remaining count to live value for a neighbour which registered as stale (NeighbourState = 1:Stale). This value



205 UBS-44-57-004

Object Parameter Description is set to StaleNonIntraNeighbourGraceWindow (in RRM profile) value when the neighbour state transits from online to stale (NeighbourState:: 0:Online -> 1:Stale). It is decremented for every inter frequency periodic measurement report received from a UE where the PSC is not received. --- RMS Access: READ Type: Integer. (Range: 0 to 460800). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A


A neighbour classified as stale if it is no longer detected by network listen. A stale neighbour is promoted back to online state by any of the following: - a UE measurement report including measurements for this neighbour's UARFCN:PSC, - network listen --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "0_Online" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellMobilityCriterion

Configuration for this cell as to what it should be used for - "Reselection and handout" - "Reselection only" - "Handout only" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Reselection and handout" RMS Default value:N/A RMS Property:N/A Management level: N/A


Timestamp when this cell was added. In the case of a full NL, a new cell is defined as when the cid / rnc_id is modified. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A


Timestamp when this cell was last modified in any way e.g RemainingTimeToLive --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A



Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell

The inter-RAT cell lists separated by technology. 3GPP-TS.25.331 Section 10.3.7.23

MaxGSMEntries The maximum number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell.GSM.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 32). Notification: None FAP Default value: 32 RMS Default value:N/A RMS Property:N/A Management level: N/A

GSMNumberOfEntries Number of entries in the .CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell.GSM.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 32). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_DominantNeighbourMacroIndex

Index into the NeighborListInUse.InterRATCell.GSMl list for the strongest neighbour (to allow LAC/RAC/PLMN etc to be read) Value -1 means that no macros have been detected. --- RMS Access: READ Type: Integer. (Range: -1 to 9). Notification: None Value set at runtime FAP Default value:-1 RMS Default value:N/A RMS Property:N/A Management level: N/A



207 UBS-44-57-004

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.NeighborListInUse.InterRATCell.GSM

Table containing the inter-RAT cell list for GSM. At most one entry in this table can exist with a given value for BCCHARFCN.

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None FAP Default value: "" Management level: N/A

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 Management level: N/A

RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 Management level: N/A

BSIC BSIC of the cell per 3GPP-TS.23.003 [8], consisting of: Bit 7:6 - not used ("00") Bit 5:3 - NCC (PLMN Color Code) Bit 2:0 - BCC (BS color code) For example, if NCC is 7 and BCC is 2 you would have 00111010 (binary) or 0x3A (hex), and the value of this parameter would be 58. --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 Management level: N/A

CI Cell ID of the cell per 3GPP-TS.23.003 Section 4.3.1. --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None FAP Default value: 0 Management level: N/A

BandIndicator Indicates how to interpret the BCCH ARFCN. Enumeration of:



Object Parameter Description - "GSM 850" - "GSM 900" - "DCS 1800" - "PCS 1900" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "DCS 1800" Management level: N/A

BCCHARFCN ARFCN of this cell. --- RMS Access: READ Type: Integer. (Range: 0 to 1023). Notification: None FAP Default value: 0 Management level: N/A

X_UBIQUISYS_COM_RSSI

Received signal level in dBm of the BCCH carrier. --- RMS Access: READ Type: Integer. (Range: -110 to 48). Notification: None FAP Default value: -110 Management level: N/A


Remaining count to live value for a neighbour which registered as stale (NeighbourState = 1:Stale). This value is set to StaleNonIntraNeighbourGraceWindow (in RRM profile) value when the neighbour state transits from online to stale (NeighbourState:: 0:Online -> 1:Stale). The count value will be decremented for every inter-frequency periodic measurement report received where this inter-rat cell is not detected. --- RMS Access: READ Type: Integer. (Range: 0 to 460800). Notification: None FAP Default value: 0 Management level: N/A


A neighbour classified as stale if it is no longer detected by network listen. A stale neighbour is promoted back to online state by any of the following: - a UE measurement report including measurements for this neighbour's UARFCN:PSC, - network listen --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "0_Online" Management level: N/A


Timestamp when this cell was added. In the case of a full NL, a new cell is defined as when the cid / rnc_id is modified. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 Management level: N/A


Timestamp when this cell was last modified in any way e.g RemainingTimeToLive



209 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 Management level: N/A

Table 77 Neighbor List in Use



4.10 HomeZone Notification

4.10.1 HomeZone Value Added Feature There are actually 3 general scenarios to consider when providing indications to the user to indicate they are being served by the macro or Femto network:

• Scenario 1: UE transition between Femto and macro network in idle mode (see Section 4.10.1.1)

• Scenario 2: UE transition between Femto and macro network in connected mode (see Section 4.10.1.2)

• Scenario 3: Idle mode UE on Femto network activates connected mode (CS or PS) (see Section 4.10.1.3)

The Femto solution has options for each of these scenarios (.AccessMgmt.X_UBIQUISYS_COM_HomeZoneIndicationControl), and these are discussed below.

4.10.1.1 Scenario 1: Idle Mode Transition Options:

For idle mode reselection, the following 2 visual indication options are currently available. One or both options can be activated via configuration from the HMS. In each case, the UE’s display is updated with Femto/macro network specific text following successful Location Update procedure with the Femto/macro layers. This text persists for the duration that the UE is served in idle mode by the Femto network/macro layer.

4.10.1.1.1 Option 1: Equivalent PLMN

This option is achieved independently of any AP configuration by:

• Allocation of an alternative PLMN identifier for use by the Femto network – typically this will be via a second Mobile Network Code (MNC) available to the Operator.

• Configuration of both Femto and macro networks to communicate the list of equivalent PLMN to UEs during existing signalling procedures.

• UEs use the existing, built-in mechanism to display the network name text associated with the Femto PLMN, whenever they are served on the Femto network. In case the UE does not yet have the registered network name text for this PLMN in its memory, the UE will instead display the digits of the PLMN code, which can be recognised as the Femto network.

The significant benefits of this method are that it:

• Uses existing procedures and principles

• Requires no UE modification

• Provides real-time and persistent indication

• Works with SIM or USIMs

4.10.1.1.2 Option 2: Modified Network Name Using MM-INFORMATION

This option is achieved by:

• Configuring both the macro and Femto networks to trigger an MM-INFORMATION procedure towards the UE immediately after the UE performs a successful Location Update procedure. On the HNB this is configured using .AccessMgmt.HomeZoneName and is enabled as soon as the field is not an empty string.

• The MM-INFORMATION message contains an appropriate “network name” field, configured in .AccessMgmt.HomeZoneName, to distinguish whether the UE is served by the Femto network (e.g. “Operator-HomeZone”) or the macro network (e.g. “Operator”). With MM-INFO option activated, it is possible to have a customised, subscriber specific homezone text configured on a per AP basis in .AccessMgmt.X_UBIQUISYS_COM.HomeZoneNameCustomisation. With this, it is possible for the user to



211 UBS-44-57-004

distinguish which AP they are being served by, for example on their home AP (indication “John’s AP”) or a visited AP on which they are authorised (e.g. indication “Company ABC”).

• The UE uses this text, configured in .AccessMgmt.HomeZoneName, to overwrite the network name field on its display (as this takes preference over the name derived from the registered PLMN).

The significant benefits of this method are that it:

• Provides real-time and persistent indication

• Allows a customised network name text to be configured on a per AP basis -this could be meaningful and representative of the customer, and offered– allowing user specific text (“Jane’s AP”, “Bob’s Home”) to be configured by AP management system (perhaps as a value added service to subscribers).

The full algorithm is as follows:

• When the parameter .AccessMgmt.HomeZoneName IS NOT null, then the HNB shall: o Intercept all G/MM-INFO messages sent by CN towards UEs. o Replace or insert the long/short network name IEs such that these contain the

.AccessMgmt.HomeZoneName string o Relay the modified G/MM-INFO message towards the UEs.

• On the other hand, if the parameter .AccessMgmt.HomeZoneName IS null, then the HNB shall relay

G/MM-INFO messages towards UE without modification. This option does have a drawback in that UE support for MM-INFORMATION message is optional. As such, this method is more appropriate when a significant proportion of the Operator’s UE population supports this message and contents. This method also requires MM-INFORMATION support on the macro network to clear the MM-INFORMATION displayed by the UE when this one roves out of femtocell coverage.

4.10.1.2 Scenario 2: Connected Mode Transition Options

4.10.1.2.1 Option 1: Handover tones:

Following successful hand-in from macro to Femto or immediately prior to hand-out from Femto to macro, a single brief tone is inserted into the audio path idle mode to the user to inform them that they are transitioning out of their ‘home zone’ Femto connection, and may be subject to a different tariff.

For the handover out audio tone, the parameter .AccessMgmt.EnableHandoutTone must be enabled. Similarly, for handover in audio tone, the parameter EnableHandinTone must be enabled. The .AccessMgmt.EnableHandoutTone parameter is by default enabled.

4.10.1.3 Scenario 3: Idle to Connected Mode Options

4.10.1.3.1 Option 1: Tone Insertion – CS initiation:

When establishing a CS call on the Femto, if .AccessMgmt.EnableHomeZoneTone is enabled, the AP injects an AMR recording into the audio path prior to establishment of the end to end speech path. This gives the user confidence that they will be subject to Femto specific tariffs. This function is by default enabled.

4.10.1.3.2 Option 2: SMS Class 0 – PS Initiation:

When establishing a PS session on the AP, if .AccessMgmt.HomeZonePSNotification is not empty, the AP sends an SMS class 0 to the UE – this is displayed immediately on the UE screen without requiring user intervention to see the message contents.

However, once in connected mode on the Femto layer, there is no ongoing indication to the user.

The Cisco HNB supports activation of multiple options in combination; this is the most likely deployment scenario.



With either or both the ePLMN and MM-INFO options activated, the visual indication can be configured to be distinct from the macro network. This feature will permit CS to insert (play) a predefined set of AMR frames towards the UE when requested from an indication message.

The AMR frames to be inserted will be from files specified within the Cisco file system. Initially they could be the actual files, ultimately they will form part of the operator data and as such can be customised for each Operator. If the Operator were to be willing to create their own tone, the file format used is:

• AMR-NB file format

o (http://wiki.forum.nokia.com/index.php?title=Special:PdfPrint&page=AMR_format)

• Encoded using 12.2k Frames (No SID frames)

• The indication of when to play the handout tone or the CS call tone will be sent from RRC for handout and CC for homezone.

4.10.2 HomeZone Parameters

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.AccessMgmt

This object contains parameters relating to Access Management (ACL, CSG, LIA). Closed Subscriber Group (CSG) service behaviour is specified in 3GPP-TS.22.011. Note: Cell barring and 3GPP access class parameters are contained in .CellConfig.UMTS.RAN.FDDFAP.CellRestriction.

HomeZoneName

An operator-defined ASCII character string that is displayed on the UE when it is connected to the HNB. The home zone name may be used by the HNB to indicate its identity to a non-CSG capable UE. E.g. through Cell Broadcast or SMS. On Ubiquisys HNB, this parameter sent to UEs through the MMINFO message and is optional possible to override operator setting from owner GUI. If set to empty string then no MMINFO will be sent. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 160 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:HOME-ZONE-NAME Management level: Customer

X_UBIQUISYS_COM_HomeZoneIndicationControl

This parameter controls which method of HomeZone Indication is enabled including when and how the HNB manipulates core network initiated MM-INFO messages. The following enumerations define the HNB behaviour as follows: 0: Disabled (Default) The HNB does: 1. not generate MM-INFO 2. not intercept CN-initiated MM-INFO 1: ePLMN method enabled The HNB does: 1. not generate MM-INFO. 2. intercept CN-initiated MM-INFO messages and replace network name fields dependent on whether the UE



213 UBS-44-57-004

Object Parameter Description is authorised for service or not as follows: a. UE authorised: do not modify network name fields b. UE not authorised: replace with spaces. 2: MM-INFO method enabled The FAP does: 1. generate MM-INFO towards UEs. 2. intercept and replace network name fields in CN-initiated MM-INFO messages. In both cases the HNB inserts/replaces network names fields in MM-INFO dependent on whether the UE is authorised for service or not as follows: a. UE authorised: use HomeZoneName b. UE not authorised: use spaces. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "HZDisplay Disabled" RMS Default value: "HZDisplay Disabled" RMS Property: HOME-ZONE-INDICATION-CONTROL Management level: Solution

X_UBIQUISYS_COM_HomeZoneCharacterEncoding

Defines the encoding scheme that will be used for the HomeZoneName string in the (G)MMINFO message - "UCS2" - "GSM7" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "GSM7" RMS Default value: "GSM7" RMS Property: HOME-ZONE-CHARACTER-ENCODING Management level: Customer

X_UBIQUISYS_COM_HomeZonePSNotification

The 'Home Zone PS Notification' message that is sent to the UE in a type 0 SMS when it starts a PS session. If set to empty string then no PS notification will be sent to UEs. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 130 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_EnableHomeZoneTone

If enabled, a tone file is played during a voice-call set-up. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: ENABLE-HOMEZONE-TONE Management level: Customer

X_UBIQUISYS_COM_MaxConcurrentUsers

The maximum number of users (CSG and Non-CSG) that can be attached to the HNB concurrently (either from the AccessControlList or open access) ---



Object Parameter Description RMS Access: READ/WRITE Type: Integer. (Range: 1 to 200). Notification: None FAP Default value: 100 RMS Default value:100 RMS Property: ACCESS-MGMT-CONCURRENT-USERS Management level: Customer or Solution

Table 78 HomeZone Parameters



215 UBS-44-57-004

4.11 Transport This object contains parameters relating to HNB’s transport layer. The following objects are collectected under the Transport object:

the .AccessMgmt. object is shown in the figure below:

Figure 14: FAP Transport container

4.11.1 SCTP

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport This object contains parameters relating to the transport InternetGatewayDevice.Services.FAPService.1.Transport.SCTP

This object contains parameters relating to SCTP as defined in RFC4960 and RFC3873.

Enable

Enables or disables the whole SCTP object and allows the setup or release of SCTP associations and their related streams. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: System

HBInterval

Heartbeat interval in seconds. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 4294967295). Notification: None FAP Default value: 30 RMS Default value:N/A RMS Property:N/A Management level: System

MaxAssociationRetransmits

Maximum number of consecutive retransmissions to a peer before an endpoint considers that the peer is unreachable and closes the association. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 4 RMS Default value:N/A



Object Parameter Description RMS Property:N/A Management level: System

MaxInitRetransmits

Number of retransmission per connection-attempt. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 8 RMS Default value:N/A RMS Property:N/A Management level: System

MaxPathRetransmits

Maximum retransmission per destination address. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 5 RMS Default value:N/A RMS Property:N/A Management level: System

RTOInitial

Initial value for Retransmit timeout in milliseconds. A retransmission time value of zero means immediate retransmission. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 3000 RMS Default value:N/A RMS Property:N/A Management level: System

RTOMax

Maximum value for Retransmit timeout in milliseconds. A retransmission time value of zero means immediate retransmission. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 60000 RMS Default value:N/A RMS Property:N/A Management level: System

RTOMin

Minimum value for Retransmit timeout in milliseconds. A retransmission time value of zero means immediate retransmission. The value of this parameter MUST be lower than or equal toRTOMax. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 1000 RMS Default value:N/A RMS Property:N/A Management level: System

ValCookieLife

Valid cookie life in the 4-way start-up handshake procedure in milliseconds --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 60000 RMS Default value:N/A RMS Property:N/A Management level: System



217 UBS-44-57-004


MaxMTUSize

Maximum Fragment Size used during SCTP Fragmentation. Minimum of MaxMTUSize and PMTU discovered shall be used during SCTP Fragmentation. --- RMS Access: READ/WRITE Type: Integer. (Range: 500 to1500). Notification: None FAP Default value: 1344 RMS Default value:1344 RMS Property: FC-SCTP-MAX-MTU-SIZE Management level: System

OutOfBlues

The number of correctly formed SCTP packets, including the proper checksum, but for which the receiver was unable to identify an appropriate association. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ChecksumErrors

The number of SCTP packets received with an invalid checksum. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OutCtrlChunks

The number of SCTP control chunks sent (retransmissions are not included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OutOrderChunks

The number of SCTP ordered data chunks sent (retransmissions are not included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OutUnorderChunks

The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) sent (retransmissions are not included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime



Object Parameter Description FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InCtrlChunks

The number of SCTP control chunks received (no duplicate chunks included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InOrderChunks

The number of SCTP ordered data chunks received (no duplicate chunks included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InUnorderChunks

The number of SCTP unordered chunks (data chunks in which the U bit is set to 1) received (no duplicate chunks included). --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

FragUsrMsgs

The number of user messages that have been sent fragmented. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ReasmUsrMsgs

The number of user messages that have been received fragmented and submitted to the reassembly process. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OutSCTPPacks

The number of SCTP packets sent. Retransmitted DATA chunks are included. --- RMS Access: READ



219 UBS-44-57-004

Object Parameter Description Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InSCTPPacks

The number of SCTP packets received. Duplicates are included. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Discontinuity

The time of the last discontinuity. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

AssocNumberOfEntries

The number of entries in the .Transport.SCTP.Assoc.{i}. Table --- RMS Access: READ Type: Integer. (Range: 0 to 1). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.Transport.SCTP.Assoc

SCTP Association Table At most one entry in this table can exist with the same values for PrimaryPeerAddress and LocalPort.

Status

The status of this SCTP association entry. Enumeration of: - "Disabled" - "Active" (The Association is active.) - "Progressing" (The Association establishment is in progress.) - "ShuttingDown" (The Association graceful shutdown is in progress.) - "Error" (Indicates a locally defined error condition., OPTIONAL) --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Disabled” RMS Default value:N/A RMS Property:N/A Management level: N/A

PrimaryPeerAddress

The primary IP address of the peer SCTP association entity.



Object Parameter Description --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

LocalPort

The local SCTP port number used for this SCTP association. --- RMS Access: READ Type: Integer. (Range: 0 to 63999). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InStreams

The number of Inbound Streams according to the negotiation at association start-up. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

OutStreams

The number of Outbound Streams according to the negotiation at association start-up. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime Management level: N/A

StartTime

The start Time for the present SCTP association. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Deafult value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 79 SCTP

4.11.2 Packet Transport This object contains parameters relating to Packet Transport using GTP-U.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Packet

This object contains parameters relating to Packet Transport using GTP-U.

EchoInterval

Echo interval in seconds. An Echo interval value of zero means echo is disabled. ---



221 UBS-44-57-004

Object Parameter Description RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_MSS

Configures the MSS (Maximum Segment Size) for DL FTP PS data that is sent through the GTP tunnel. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 1500). Notification: None FAP Default value: 1344 RMS Default value:N/A RMS Property:N/A Management level: System

Table 80 Packet Transport

4.11.3 Tunnelling This object contains parameters relating to Tunnelling. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Tunnel This object contains parameters relating to Tunneling.

IKESANumberOfEntries

The number of entries in the .Transport.Tunnel.IKESA.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 2). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ChildSANumberOfEntries

The number of entries in the .Transport.Tunnel.ChildSA.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 4). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxVirtualInterfaces

The maximum number of virtual interfaces. --- RMS Access: READ Type: Integer. (Range: 1 to 1). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

VirtualInterfaceNumberOfEntries

The number of entries in the .Transport.Tunnel.VirtualInterface.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 1). Notification: None




InternetGatewayDevice.Services.FAPService.1.Transport.Tunnel.IKESA

IKE IPsec Security Association Table. This Table is a member of the IPsec Security Association Database (SAD). RFC4301. At most one entry in this table can exist with the same values for IPAddress and SubnetMask.

Status

The status of this IKE SA entry. Enumeration of: - "Disabled" - "Active" - "Completed" - "Progressing" - "Error" (This value MAY be used by the CPE to indicate a locally defined error condition.,OPTIONAL) --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Disabled” RMS Default value:N/A RMS Property:N/A Management level: N/A

PeerAddress

The IP address of the peer SecGW. --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

CreationTime

The time that the current IKE SA was set up. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

IPAddress

The current IP address assigned to this interface by IKEv2. --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

SubnetMask

The current subnet mask assigned to this interface by IKEv2. --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Value set at runtime FAP Default value:””



223 UBS-44-57-004


DNSServers

Comma-separated list (maximum length 256) of IPAddresses. Each item is an IP Address of a DNS server for this interface assigned to this interface by IKEv2. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.Transport.Tunnel.ChildSA

Child IPsec Security Association Table. This Table is a member of the IPsec Security Association Database (SAD). RFC4301. At most one entry in this table can exist with a given value for SPI.

ParentID

The value MUST be the instance number of a row in the .Transport.Tunnel.IKESA table, or else be 0 if no row is currently referenced. If the referenced row is deleted, the parameter value MUST be set to 0. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime Management level: N/A

SPI

SPI value of the Child SA. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

DirectionOutbound

Traffic Direction. If true this Child SA refers to outbound traffic. If false this Child SA refers to inbound traffic. --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CreationTime

The time that the current Child SA was set up. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 81 Tunnelling



4.11.4 Security These objects contain parameters relating to Security. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security This object contains parameters relating to Security.

SecretNumberOfEntries

The number of entries in the .Transport.Security.Secret.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PkeyNumberOfEntries

The number of entries in the .Transport.Security.Pkey.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CryptoProfileNumberOfEntries

The number of entries in the .Transport.Security.CryptoProfile.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 82 Security

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security.Secret

Shared Secret Table. This table gathers information about all types of shared secret-based credentials (UICC). At most one entry in this table can exist with a given value for UICCCardID.

Enable

Enable or disable this Shared Secret entry --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: System

Type

The type of this Shared Secret entry. Enumeration of: - "SIM" - "USIM" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "SIM" RMS Default value:N/A



225 UBS-44-57-004


Status

The status of this Shared Secret entry. Enumeration of: - "Present" - "Not_present" - "Error" (This value MAY be used by the CPE to indicate a locally defined error condition.) --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Not_present" RMS Default value:N/A RMS Property:N/A Management level: N/A

UICCCardID

The UICC Card Identifier (UICCID), only numeric values are allowed. ITU-E.118 --- RMS Access: READ Type: String. (Length: 0 to 19 characters). Notification: Forced FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 83 Security

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security.Pkey

Public Key Table. This table gathers information about all types of public key-based credentials, such as X.509 certificates. RFC3280. At most one entry in this table can exist with a given value for SerialNumber.

Enable

Enables or disables this Public Key entry. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

LastModif

The last modification time of this Public Key entry. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SerialNumber

The Serial Number field in an X.509 certificate --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Issuer The Issuer field in an X.509 certificate; i.e. the



Object Parameter Description Distinguished Name (DN) of the entity who has signed the certificate. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

NotBefore

The beginning of the certificate validity period; i.e. the Not Before field in an X.509 certificate. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

NotAfter

The end of the certificate validity period; i.e., the Not After field in an X.509 certificate. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Subject

The X.501 Distinguished Name (DN) of the entity associated with the Public Key; i.e., the Subject field in an X.509 certificate. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" Management level: N/A

SubjectAlt

Comma-separated list (maximum length 256) of strings. Each item is a DNS Name. The Subject Alternative Names extension field in an X.509 certificate. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 84 Security

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security.CryptoProfile

This object contains parameters relating to IKEv2 and IPsec crypto profiles, which are essentially a subset of the typical IPsec SPD. RFC4301. At most one enabled entry in this table can exist with all the same values for AuthMethod, IKEEncrypt, IKEPRF, IKEIntegrity, IKEDH, ESPEncrypt and ESPIntegrity.

Enable Enables and disables this entry.



227 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: FALSE RMS Property: CRYPTO-PROFILE-ENABLE Management level: N/A

AuthMethod

Specifies the Security mechanism and set of credentials used by the FAP to authenticate itself. The value MUST be the full path name of a row in the .Transport.Security.Pkey or .Transport.Security.Secret tables. If the referenced object is deleted, the parameter value MUST be set to an empty string. If an empty string, the FAP chooses the authentication method based on local policy. In order to configure the FAP for both FAP and hosting-party authentication, the object is populated with an enabled instance of the Pkey object. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default vaule: Input Cloudbase RMS Property: CRYPTO-PROFILE-AUTH-METHOD Management level: N/A

MaxChildSA

Controls the maximum number of child SAs that can be negotiated by a single IKE session. --- RMS Access: READ/WRITE Type: Integer. (Range: 2 to 2). Notification: None FAP Default value: 2 RMS Default value:2 RMS Property: CRYPTO-PROFILE-MAX-CHILD-SA Management level: N/A

IKEEncrypt

Comma-separated list of strings. IKEv2 encryption algorithm. RFC4307 Each list item is an enumeration of: - "3DES-CBC" - "AES-CBC" Ubiquisys currently support only the default algorithm --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "AES-CBC" RMS Default value: AES-CBC RMS Property: CRYPTO-PROFILE-IKE-ENCRYPT Management level: System

IKEPRF

Comma-separated list of strings. IKEv2 pseudorandom function. RFC4307 Each list item is an enumeration of: - "HMAC-SHA1" - "AES-XCBC-PRF-128" Ubiquisys currently support only the default algorithm --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "HMAC-SHA1" RMS Default value: HMAC-SHA1



Object Parameter Description RMS Property: CRYPTO-PROFILE-IKE-PRF Management level: System

IKEIntegrity

Comma-separated list of strings. IKEv2 integrity function. RFC4307 Each list item is an enumeration of: - "HMAC-SHA1-96" - "AES-XCBC-MAC-96" Ubiquisys currently support only the default algorithm --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "HMAC-SHA1-96" RMS Default value: HMAC-SHA1-96 RMS Property: CRYPTO-PROFILE-IKE-INTEGRITY Management level: System

IKEDH

Comma-separated list of strings. IKEv2 pseudorandom function. RFC4307 Each list item is an enumeration of: - "1024" - "2048" --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "2048" RMS Default value: 2048 RMS Property: CRYPTO-PROFILE-IKE-DH Management level: System

ESPEncrypt

Comma-separated list of strings. IPsec encryption algorithm. RFC4307 Each list item is an enumeration of: - "3DES-CBC" - "AES-CBC" - "Null" Ubiquisys currently support only the default algorithm --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "AES-CBC" RMS Default value: AES-CBC RMS Property: CRYPTO-PROFILE-ESP-ENCRYPT Management level: System

ESPIntegrity

Comma-separated list of strings. IPsec integrity function. RFC4307 Each list item is an enumeration of: - "HMAC-SHA1-96" - "AES-XCBC-MAC-96" Ubiquisys currently support only the default algorithm --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "HMAC-SHA1-96" RMS Default value: HMAC-SHA1-96 RMS Property: CRYPTO-PROFILE-ESP-INTEGRITY Management level: System

IKERekeyLifetime

IKEv2 SA rekey timeout in seconds. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 432000).



229 UBS-44-57-004

Object Parameter Description Reboot triggered by SetParameterValue. Notification: None FAP Default value: 0 RMS Default value: 0 RMS Property: CRYPTO-PROFILE-IKE-RE-KEY-LIFETIME Management level: System

IPsecRekeyLifetimeTime

IPsec SA rekey timeout in seconds. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 432000). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: CRYPTO-PROFILE-IPSEC-LIFETIME-TIME Management level: System

DPDTimer

DPD timeout in seconds. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 72000). Notification: None FAP Default value: 300 RMS Default value: 300 RMS Property: CRYPTO-PROFILE-DPD-TIMER Management level: System

NATTKeepaliveTimer

NAT-T keepalive timeout in seconds. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 72000). Notification: None FAP Default value: 180 RMS Default value: 180 RMS Property: CRYPTO-PROFILE-NATT-KEEP-ALIVE-TIMER Management level: System

Table 85 Security

4.11.4.1 Security Extensions

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security This object contains parameters relating to Security.

X_UBIQUISYS_COM_SendCertReq

Request GW certificate --- RMS Access: READ/WRITE Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value TRUE RMS Default value: N/A RMS Property:N/A Management level: System

X_UBIQUISYS_COM_VerifyCert

Enable checking of the GW Certificate --- RMS Access: READ/WRITE Type: Boolean. Notification: None Parameter modified via activation server. FAP Default value TRUE RMS Default value: N/A RMS Property:N/A




X_UBIQUISYS_COM_TransmitFragmentMode

Defines the behaviour of setting the Don't Fragment (DF) flag in the IP header of the ESP tunnel mode packet (outer). See RFC 4301 Sec 8.1 for detail. 0 - Propagate from inner to outer 1 - Always set DF 2- Always clear DF (Original default mode for G2) --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 2). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 2 RMS Default value:2 RMS Property: SECURITY-TRANSMIT-FRAGMENT-MODE Management level: System

Table 86 Security Extensions

4.11.4.2 Security Extensions Object Parameter Description InternetGatewayDevice.Services.FAPService.1.Transport.Security.CryptoProfile

This object contains parameters relating to IKEv2 and IPsec crypto profiles, which are essentially a subset of the typical IPsec SPD. RFC4301. At most one enabled entry in this table can exist with all the same values for AuthMethod, IKEEncrypt, IKEPRF, IKEIntegrity, IKEDH, ESPEncrypt and ESPIntegrity.

X_UBIQUISYS_COM_RetransmitTimeout

Time in seconds between retransmission of IKE messages --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 300). Notification: None FAP Default value: 5 RMS Default value:5 RMS Property: CRYPTO-PROFILE-RE-TRANSMIT-TIMEOUT Management level: System

X_UBIQUISYS_COM_RetransmitTries

Max number of re-transmission attempts for IKE messages --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 10). Notification: None FAP Default value: 5 RMS Default value:5 RMS Property: CRYPTO-PROFILE-RE-TRANSMIT-TRIES Management level: System

Table 87 Security Extensions



231 UBS-44-57-004

4.12 REM The duration of the REM scan dependson a numbe of factors, follows is an example for calculating the duration of the DLMM REM scan:

• Assuming: o 20 GSM ARFCNs searched per band (typical 3G BA size) o 2 GSM bands & one BCH per GSM band o Home PLMN only o 2 UMTS carriers (7 neighbours each)

• Total duration = o WCDAM = 10 + (2 * (5 + (7 * 10))) = 160s o GSM = 2 * (10 + (20 * 1) + 10) = 80s o 160 + 80 = 240s

4.12.1 WCDMA FDD Object Parameter Description InternetGatewayDevice.Services.FAPService.1.REM This object contains parameters relating to REM

(Radio Environment Measurement). InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD

This object contains parameters relating to radio environment measurement capabilities for the UMTS system.

InServiceHandling FAP REM behavior with respect to ongoing active connections. Enumeration of: - "Immediate" (Immediately perform REM, even if have active connections or idle camping UE that may be disrupted.) - "Delayed" (Wait to initiate REM until no CS bearers or PS bearers of streaming or higher QoS class are assigned.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Delayed" RMS Default value:N/A RMS Property:N/A Management level: Solution

ScanOnBoot Enables or disables Radio Environment Measurement during the FAP start up. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: FC-REM-3G-SCAN-ON-BOOT Management level: System

ScanPeriodically Enable Periodic Radio Environment Measurement on all enabled RAT. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE RMS Property: FC-REM-3G-SCAN-PERIODICALLY Management level: System

PeriodicInterval When ScanPeriodically is true, this value indicates the interval in seconds which REM is performed



Object Parameter Description while the FAP service is enabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 86400 RMS Default value;86400 RMS Property: FC-REM-PERIODIC-INTERVAL Management level: Solution

PeriodicTime An absolute time reference in UTC to determine when the CPE will initiate the periodic REM. Each REM MUST occur at (or as soon as possible after) this reference time plus or minus an integer multiple of the PeriodicInterval. PeriodicTime is used only to set the "phase" of the REM. The actual value of PeriodicTime can be arbitrarily far into the past or future. For example, if PeriodicInterval is 86400 (a day) and if PeriodicTime is set to UTC midnight on some day (in the past, present, or future) then periodic REMs will occur every day at UTC midnight. These MUST begin on the very next midnight, even if PeriodicTime refers to a day in the future. The Unknown Time value defined in [TR-106a2] Section 3.2 indicates that no particular time reference is specified. That is, the CPE MAY locally choose the time reference, and needs only to adhere to the specified PeriodicInformInterval. If absolute time is not available to the CPE, its periodic REM behavior MUST be the same as if PeriodicTime parameter was set to the Unknown Time value. Ubiquisys FAPs will run the periodic scan in the Least Busy Hour when an Unknown Time value is set --- RMS Access: READ/WRITE Type: dateTime . (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value: Random RMS Property: PERIODIC-SCAN-RANDOM-TIME Management level: Solution

REMPLMNList Comma-separated list (maximum length 32) of strings. Each item is a PLMN ID to measure. PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. If an empty string, then no specific PLMN ID is provided, meaning that the FAP is required to scan all available PLMN IDs. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 224 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: REM-3G-PLMN-LIST Management level: Deployment specific

REMBandList Comma-separated list of strings. Each item is a UMTS Band to measure. Each band is identified in



233 UBS-44-57-004

Object Parameter Description by a roman numeral 3GPP-TS.25.104. If an empty string then no specific UMTS band is provided, meaning that the FAP is required to scan all available bands. The order of the band indicator has no significance. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 90 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value: Input RMS Property: REM-3G-BAND-LIST Management level: Deployment specific

UARFCNDLList Comma-separated list (maximum length 64) of strings. Each entry is a UARFCN in the DL direction to measure. If an empty string, then no specific UARFCN is provided, meaning that the FAP is required to scan all UARFCNs that it is aware of. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 385 characters). Notification: None FAP Default value: "" RMS Default value: Input RMS Property: REM-3G-ARFCN-LIST Management level: Deployment specific

ScanTimeout Specifies the time-out value in seconds, measured from the start of the REM scan, before the REM scan will time out. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 600 RMS Default value:N/A RMS Property:N/A Management level: System

ScanStatus Indicates the current status of this scan. Enumeration of: - "Indeterminate" (The scan has not been executed and there are no valid scan results available) - "InProgress" - "Success" (scan has finished and results have changed compared to last scan) - "Error" - "Error_TIMEOUT" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Intermediate” RMS Default value:N/A RMS Property:N/A Management level: N/A

ErrorDetails Provides more detail when the ScanStatus is either Error or Error_TIMEOUT. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None



Object Parameter Description Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

LastScanTime The time of the last UMTS system radio environment measurement. Note that Ubiquisys FAPs will only update this after a full REM scan, not during the 'Continuous' scan mode --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: Active Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxCellEntries The maximum number of entries available in the .REM.WCDMAFDD.Cell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 100). Notification: None FAP Default value: 100 RMS Default value:N/A RMS Property:N/A Management level: N/A

CellNumberOfEntries The number entries in the .REM.WCDMAFDD.Cell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD.Cell

Table indicating the components of the discovered cells.

InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD.Cell.0.RF

Table indicating the RF aspect of the discovered cells.

UARFCNDL The UTRA Absolute Radio Frequency Channel Number (UARFCN) in the DL direction of an FDD mode cell. 3GPP-TS.25.433 --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CPICHRSCP Received signal level in dBm of the CPICH channel. (Ref. 3GPP-TS 25.133) --- RMS Access: READ Type: Integer. (Range: -120 to -25). Notification: None Value set at runtime



235 UBS-44-57-004

Object Parameter Description FAP default value:-120 RMS Default value:N/A RMS Property:N/A Management level: N/A

CPICHEcNo Measured EcNo. (energy per chip to interference power density) in dB received in the downlink pilot channel. Actual values of the range are -24.0 dB to 0.0 dB in steps of 0.5 dB. The value of CPICHEcNo divided by 2 yields the actual value of the range. 3GPP-TS.25.133 Section 9.1.2.3 --- RMS Access: READ Type: Integer. (Range: -48 to 0). Notification: None Value set at runtime FAP default value:-48 RMS Default value:N/A RMS Property:N/A Management level: N/A

RSSI This measurement is for Inter-frequency handover evaluation, measured in total dBm in the band. 3GPP-TS.25.133 Section9.1.3 --- RMS Access: READ Type: Integer. (Range: -100 to -25). Notification: None Value set at runtime FAP default value:-100 RMS Default value:N/A RMS Property:N/A Management level: N/A

PrimaryScramblingCode Primary scrambling code. --- RMS Access: READ Type: Integer. (Range: 0 to 511). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD.Cell.0.BCCH

Table containing the system information broadcast in the BCCH logical channel.

PLMNType Type of Public Land Mobile Network (PLMN). Enumeration of: - "GSM-MAP" - "ANSI-41" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP default value:”GSM-MAP” RMS Default value:N/A RMS Property:N/A Management level: N/A

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber.



Object Parameter Description Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Value set at runtime FAP default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

LAC Location Area Code (LAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the LAI (Location Area ID) 3GPP-TS.23.003 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RAC Routing Area Code (RAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the RAI (Routing Area ID) 3GPP-TS.23.003. --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CellID Cell Identity as defined in SIB3 3GPP-TS.25.331 Section10.3.2.2. 3GPP-TS.24.008 --- RMS Access: READ Type: Integer. (Range: 0 to 268435455). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PCPICHTxPower Primary Common Pilot Channel (CPICH) power level on SIB 5/6 3GPP-TS.25.331 Section10.3.6.55 --- RMS Access: READ Type: Integer. (Range: -10 to 50). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_TxDiversityInd Indicates whether the cell is using transmit diversity ---



237 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_MaxUlTxPower Max permitted UE Tx power: -50-33 (dBm) as broadcast in SIB 3 3GPP-TS.25.331 10.3.6.39 --- RMS Access: READ Type: Integer. (Range: -50 to 33). Notification: None Value set at runtime FAP default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 88 WCDMA FDD

4.12.2 GSM Object Parameter Description InternetGatewayDevice.Services.FAPService.1.REM This object contains parameters relating to REM

(Radio Environment Measurement). InternetGatewayDevice.Services.FAPService.1.REM.GSM This object contains parameters relating to GSM

REM capabilities. InServiceHandling FAP REM behavior with respect to ongoing active

connections. Enumeration of: - "Immediate" (Immediately perform REM, even if have active connections or idle camping UE that may be disrupted.) - "Delayed" (Wait to initiate REM until no CS bearers or PS bearers of streaming or higher QoS class are assigned.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Delayed" RMS Default value:N/A RMS Property:N/A Management level: Solution

ScanOnBoot Enables or disables Radio Environment Measurement during the FAP start up. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: FC-REM-2G-SCAN-ON-BOOT Management level: System

ScanPeriodically Enable Periodic Radio Environment Measurement on all enabled RAT. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE



Object Parameter Description RMS Default value:TRUE RMS Property: FC-REM-2G-SCAN-PERIODICALLY Management level: System

PeriodicInterval When ScanPeriodically is true, this value indicates the interval in seconds which REM is performed while the FAP service is enabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 86400 RMS Default value: 86400 RMS Property: FC-REM-PERIODIC-INTERVAL Management level: Solution

PeriodicTime An absolute time reference in UTC to determine when the CPE will initiate the periodic REM. Each REM MUST occur at (or as soon as possible after) this reference time plus or minus an integer multiple of the PeriodicInterval. PeriodicTime is used only to set the "phase" of the REM. The actual value of PeriodicTime can be arbitrarily far into the past or future. For example, if PeriodicInterval is 86400 (a day) and if PeriodicTime is set to UTC midnight on some day (in the past, present, or future) then periodic REMs will occur every day at UTC midnight. These MUST begin on the very next midnight, even if PeriodicTime refers to a day in the future. The Unknown Time value defined in [TR-106a2] Section 3.2 indicates that no particular time reference is specified. That is, the CPE MAY locally choose the time reference, and needs only to adhere to the specified PeriodicInformInterval. If absolute time is not available to the CPE, its periodic REM behavior MUST be the same as if PeriodicTime parameter was set to the Unknown Time value. Ubiquisys FAPs will run the periodic scan in the Least Busy Hour when an Unknown Time value is set --- RMS Access: READ/WRITE Type: dateTime. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value: Random RMS Property: PERIODIC-SCAN-RANDOM-TIME Management level: Solution

REMPLMNList Comma-separated list of strings (maximum item length 6). Each item is a PLMNID. PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of the PLMNID is 5. If an empty string no specific PLMN ID is provided,



239 UBS-44-57-004

Object Parameter Description meaning that the FAP is required to report all available PLMN IDs. If a list is provided, the FAP is expected to limit the REM measurement to the PLMN(s) specified in this list only and ignore others even if they are detected. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 37 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: REM-2G-PLMN-LIST Management level: Deployment specific

REMBandList Comma-separated list of strings. Each item is a GSM Band to measure. Each list item is an enumeration of: - "T-GSM380" - "T-GSM410" - "GSM450" - "GSM480" - "GSM710" - "GSM750" - "T-GSM810" - "GSM850" - "P-GSM900" - "E-GSM900" - "R-GSM900" - "T-GSM900" - "DCS1800" - "PCS1900" If an empty string then no specific GSM band is provided, meaning that the FAP MUST scan all bands. If a list is provided, the FAP is expected to limit the REM measurement to the band(s) specified in this list only and ignore others even if they are detected. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 120 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value: Input RMS Property: REM-2G-BAND-LIST Management level: Deployment specific

ARFCNList Comma-separated list (maximum length 64) of strings. Each item is a GSM ARFCN to measure. If an empty string then no specific ARFCN is provided, meaning that the FAP is required to scan all ARFCNs. If a list is provided, the FAP is expected to limit the REM measurement to the ARFCN(s) specified in this list only and ignore others even if they are detected. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 385 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: REM-2G-ARFCN-LIST Management level: Deployment specific



Object Parameter Description ScanTimeout Specifies the time-out value in seconds, measured

from the start of the REM scan, before the REM scan will time out. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 600 RMS Default va;ue:N/A RMS Property:N/A Management level: System

ScanStatus Indicates the current status of this scan. Enumeration of: - "Indeterminate" (The scan has not been executed and there are no valid scan results available) - "InProgress" - "Success" (scan has finished and results have changed compared to last scan) - "Error" - "Error_TIMEOUT" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value: “Indeterminate” RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

ErrorDetails Provides more detail when the ScanStatus is either Error or Error_TIMEOUT. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None Value set at runtime Management level: N/A

LastScanTime The time of the last UMTS system radio environment measurement. Note that Ubiquisys FAPs will only update this after a full REM scan, not during the 'Continuous' scan mode --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: Active Value set at runtime FAP Default value: “” RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

MaxCellEntries The maximum number of entries available in the .REM.GSM.Cell.{i}. table. --- RMS Access: READ Type: Integer. (Range: 1 to 100). Notification: None FAP Default value: 100 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

CellNumberOfEntries The number entries in the .REM.GSM.Cell.{i}. table. ---



241 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime FAP Default value: 0 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.REM.GSM.Cell

Table indicating the components of the discovered cells. At most one entry in this table can exist with the same values for ARFCN and BSIC.

BandIndicator Indicates how to interpret the BCCH ARFCN. Enumeration of: - "GSM 850" - "GSM 900" - "DCS 1800" - "PCS 1900" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”DSC 1800” RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

ARFCN Absolute Radio Frequency Channel Number (ARFCN) 3GPP-TS.05.05 --- RMS Access: READ Type: Integer. (Range: 0 to 1023). Notification: None Value set at runtime FAP Default value:0 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

BSIC Base Station Identity Code 3GPP-TS.03.03 --- RMS Access: READ Type: Integer. (Range: 0 to 63). Notification: None Value set at runtime FAP Default value:0 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

PLMNID PLMN ID consists of Mobile Country Code (MCC) and Mobile Network Code (MNC) 3GPP-TS.23.003, 3GPP-TS.24.008. Mobile Country Code consists of three digits and uniquely identifies the country of domicile of the subscriber. Mobile Network Code consists of two or three digits and identifies the Home PLMN within a country. For a 2-digit MNC the total string length of PLMNID is 5. --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Value set at runtime



Object Parameter Description FAP Default value:”” RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

LAC Location Area Code (LAC) as defined in SIB 1 3GPP-TS.25.331. The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the LAI (Location Area ID) 3GPP-TS.23.003 --- RMS Access: READ Type: Integer. (Range: 1 to 65535). Notification: None Value set at runtime FAP Default value:1 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

RAC Routing Area Code (RAC) consists of up to 3 numerical characters. The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

CI Cell Identity. 3GPP-TS.25.331 Section 10.3.2.2 --- RMS Access: READ Type: Integer. (Range: 0 to 63999). Notification: None Value set at runtime FAP Default value:0 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

RSSI Received signal level in dBm of the BCCH carrier. --- RMS Access: READ Type: Integer. (Range: -110 to 48). Notification: None Value set at runtime FAP Default value:-110 RMS Default va;ue:N/A RMS Property:N/A Management level: N/A

Table 89 GSM



243 UBS-44-57-004

4.13 GPS The following parameters are used to enable, control and enquire the GPS receiver.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.GPS This object contains the parameters relating to the

GPS scan.

ScanOnBoot

Enables or disables GPS scans during the FAP start up. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: GPS-SCAN-ON-BOOT Management level: N/A

ScanPeriodically

Enables or disables Periodic GPS scans. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:TRUE RMS Property: GPS-SCAN-PERIODICALLY Management level: N/A

PeriodicInterval

When ScanPeriodically is true, this value indicates the interval in seconds which GPS scan is performed while the FAP service is enabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:86400 RMS Property: GPS-PERIODIC-INTERVAL Management level: N/A

PeriodicTime

An absolute time reference in UTC to determine when the CPE will initiate the periodic GPS scan. Each GPS scan MUST occur at (or as soon as possible after) this reference time plus or minus an integer multiple of the PeriodicInterval. PeriodicTime is used only to set the "phase" of the G{S scan. The actual value of PeriodicTime can be arbitrarily far into the past or future. For example, if PeriodicInterval is 86400 (a day) and if PeriodicTime is set to UTC midnight on some day (in the past, present, or future) then periodic GPS scans will occur every day at UTC midnight. These MUST begin on the very next midnight, even if PeriodicTime refers to a day in the future. The Unknown Time value defined in [TR-106a2] Section 3.2 indicates that no particular time reference is specified. That is, the CPE MAY locally choose the time reference, and needs only to adhere to the specified PeriodicInformInterval. If absolute time is not available to the CPE, its periodic GPS scan behavior MUST be the same as if PeriodicTime parameter was set to the Unknown Time value. --- RMS Access: READ/WRITE Type: dateTime. (Range: 0 to 4294967295).



Object Parameter Description Notification: None FAP Default value: 0 RMS Default value: 2013-01-01T00:00:00Z RMS Property: GPS-PERIODIC-TIME Management level: N/A

ContinuousGPS

Whether or not the FAP SHOULD maintain a continuous GPS lock (e.g. as a frequency stability source). --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property: GPS-CONTINUOUS-SCAN Management level: N/A

ScanTimeout

Specifies the time-out value in seconds since the test started after which the test will time out. A timed out test is to be reported as Error_TIMEOUT with ErrorDetails indicating "Timed out". --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 600 RMS Default value:600 RMS Property: FC-GPS-TIME-OUT Management level: N/A

ScanStatus

Indicates the current status of this scan. Enumeration of: 0 - "Indeterminate" (The scan has not been executed and there are no valid scan results available) 1 - "InProgress" 2 - "Success" 3 - "Error" 4 - "Error_TIMEOUT" 5 - "Not fixed" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Indetermine” RMS Default value:N/A RMS Property:N/A Management level: N/A

ErrorDetails

Provides more detail when the ScanStatus is set to "Error" --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

LastScanTime

The time of the last GPS scan. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: Active Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A



245 UBS-44-57-004


LastSuccessfulScanTime

Specifies the date and time, when the GPS scan last completed successfully. This value is retained across reboot. The values for LockedLatitude, LockedLongitute and NumberOfSattelites correspond to this time. If a scan has never succeeded before, the value will be the Unknown Time value, as defined in [TR-106a2] Section 3.2. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LockedLatitude

This parameter specifies the actual location of the FAP, returned by the GPS Diagnostics Test. This parameter specifies the latitude of the device's position in degrees, multiplied by 1 million. The positive value signifies the direction, north of the equator. The negative value signifies the direction, south of the equator. Range is from: 90deg00.00' South (-90,000,000) to 90deg00.00' North (90,000,000). Example: A latitude of 13deg19.43' N would be represented as 13,323,833, derived as (13*1,000,000)+((19.43*1,000,000)/60). Latitude of 50deg0.00' S would be represented as value -50,000,000. This value is retained across reboots and is only reset after another scan completes successfully. If a scan has never succeeded before, the value 0 is reported. --- RMS Access: READ Type: Integer. (Range: -90000000 to 90000000). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LockedLongitude

This parameter specifies the actual location of the FAP, returned by the GPS Diagnostics Test. This parameter specifies the longitude of the device's position in degrees, multiplied by 1 million. The positive value signifies the direction, east of the prime meridian. The negative value signifies the direction, west of the prime meridian. Range is from: 180deg00.00' West (-180,000,000) to 180deg00.00' East (180,000,000). Example: A longitude of 13deg19.43' E would be represented as 13,323,833, derived as (13*1,000,000)+((19.43*1,000,000)/60). A longitude of 50deg0'0'' W would be represented as value -50,000,000. This value is retained across reboots and is only reset after another scan completes successfully. If a scan has never succeeded before, the value 0 is reported. --- RMS Access: READ Type: Integer. (Range: -180000000 to 180000000). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A




NumberOfSatellites

The number of satellites that were locked during the test execution. The greater the number of satellites the better the precision of the results. This value is retained across reboots and is only reset after another scan completes successfully. If a scan has never succeeded before, the value 0 is reported. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_BackoffLowerThreshold This parameter specifies the lower threshold (i.e., number of active UE's) at which point GPS will become re-enabled, if it was temporarily disabled via the 'backoff' mechanism. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_BackoffUpperThreshold This parameter specifies the upper threshold (i.e., number of active UE's) at which point GPS will become temporarily disabled via the 'backoff' mechanism. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Notification: None FAP Default value: 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 90 GPS

4.14 Geo-Coordinates The following object contains parameters relating to the location of the HNB as calculated by the HMS. These parameters are set by one HMS and can be read by subsequent HMSs for location verification. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_GeoCoordinatesAndAltitude Object name

Latitude

This parameter provisions the actual location of the FAP in situations where GPS is not available. The FAP will use this value if GPS hardware is not present or a GPS lock cannot be obtained. This parameter specifies the latitude of the device's position in degrees, multiplied by 1 million. The positive value signifies the direction, north of the equator. The negative value signifies the direction, south of the equator. Range is from: 90deg00.00' South (-90,000,000) to 90deg00.00' North (90,000,000).



247 UBS-44-57-004

Object Parameter Description Example: A latitude of 13deg19.43' N would be represented as 13,323,833, derived as (13*1,000,000)+((19.43*1,000,000)/60). Latitude of 50deg0.00' S would be represented as value -50,000,000. --- RMS Access: READ/WRITE Type: Integer. (Range: -90000000 to 90000000). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-GPS-LAT FC-CIG-GPS-LAT FC-EXP-LAT Management level: Solution or Customer

Longitude

This parameter provisions the actual location of the FAP in situations where GPS is not available. The FAP will use this value if GPS hardware is not present or a GPS lock cannot be obtained. This parameter specifies the longitude of the device's position in degrees, multiplied by 1 million. The positive value signifies the direction, east of the prime meridian. The negative value signifies the direction, west of the prime meridian. Range is from: 180deg00.00' West (-180,000,000) to 180deg00.00' East (180,000,000). Example: A longitude of 13deg19.43' E would be represented as 13,323,833, derived as (13*1,000,000)+((19.43*1,000,000)/60). A longitude of 50deg0'0'' W would be represented as value -50,000,000. --- RMS Access: READ/WRITE Type: Integer. (Range: -180000000 to 180000000). Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-GPS-LONG FC-CIG-GPS-LONG FC-EXP-LONG Management level: Solution or Customer

Altitude

This parameter provisions the actual altitude of the FAP in situations where GPS is not available. The FAP will use this value if GPS hardware is not present or a GPS lock cannot be obtained. The value gives the height in metres above sea level (negative values indicate below sea level) --- RMS Access: READ/WRITE Type: Integer. (Range: -500 to 10000). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Propery:N/A Management level: Solution or Customer

Table 91 Geo-Coordinates



4.15 Fault Management The objects in this section relate to configuration, report and handling of Fault and Alarms.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt This object contains parameters relating to

Fault/Alarm Management.

SupportedAlarmNumberOfEntries

The number of entries in the .FaultMgmt.SupportedAlarm.{i}. table. --- RMS Access: READ Type: Integer. (Range: 42 to 42). Notification: None FAP Default value: 42 RMS Default value:N/A RMS Property:N/A Management level: N/A

MaxCurrentAlarmEntries

The maximum number of entries allowed in the .FaultMgmt.CurrentAlarm.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 42). Notification: None FAP Default value: 42 RMS Default value:N/A RMS Property:N/A Management level: N/A

CurrentAlarmNumberOfEntries

The number of entries in the .FaultMgmt.CurrentAlarm.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 42). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

HistoryEventNumberOfEntries

The number of entries in the .FaultMgmt.HistoryEvent.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ExpeditedEventNumberOfEntries

The number of entries in the .FaultMgmt.ExpeditedEvent.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

QueuedEventNumberOfEntries

The number of entries in the .FaultMgmt.QueuedEvent.{i}. table. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None Value set at runtime



249 UBS-44-57-004


X_UBIQUISYS_COM_ReportingMechanismOverride

Global override for reporting mechanism for all alarm supported. When an individual alarm is reported (i.e. expedited, logged or queued) this override will be applied. The override does not apply when the setting of an alarm is "3 Disabled". When "OverrideOff" is selected, the parameter does not have any effect on the report mechanism of each alarm. Enumeration of: 0 Expedited 1 Queued 2 Logged 3 Disabled OverrideOff --- RMS Access: READ/WRITE Type: Enumeration Notification: None Value set is persistent FAP Default value: "OverrideOff" RMS Default value: “OverrideOff” RMS Property: REPORTING-MECHANISM-OVERRIDE-ENT,REPORTING-MECHANISM-OVERRIDE-RES Management level: N/A

Table 92 Fault Management

4.15.1 Supported Alarms The following parameters are the supported alarm entries which can be raised by the FAP. The following paramters are reported with each alarm:

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.SupportedAlarm

Supported Alarm Entries which can be raised by the FAP. The instance numbers for this table SHOULD be maintained across firmware upgrades of the device. At most one entry in this table can exist with all the same values for EventType, ProbableCause, SpecificProblem and PerceivedSeverity.

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" FAP Default value: 0 RMS Default value:N/A




SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "" FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Indeterminate" RMS Default value:N/A RMS Property:N/A Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "2 Logged" RMS Default value:N/A RMS Property: FC-REPORTING-MECHANISM-i Management level: N/A

Table 93 Supported Alarms

4.15.1.1 Alarm List



251 UBS-44-57-004

The instance numbers for this table SHOULD be maintained across firmware upgrades of the device. At most one entry in this table can exist with all the same values for EventType, ProbableCause, SpecificProblem and PerceivedSeverity.

Instance number

Event Type Probable Causes Perceived severity

Specific Problem

1

Processing Error Alarm

Cannot Select RF Profile

Critical

"The HNB is unable to select a valid set of RF parameters due to invalid configuration or adverse radio conditions"

2


Software Error

Major

"The HNB detected a software problem which requires it to re-initialise in order to provide service."

3


PM Report Failure

Minor

"The HNB is unable to upload the PM files."

4

Operation Violation

Location Changed

Minor

"The HNB has detected that it has potentially changed location."

5

Quality Of Service Alarm

Poor RF Qos

Major

"The HNB has measured that the QoS on the RF uplink and/or downlink have has diminished below a preset threshold."

6


Poor Backhaul QoS

Major

"The HNB has measured that the QoS on the backhaul connection have has diminished below a preset threshold."

7

Environmental Alarm

High Temperature

Major

"The HNB shutdown because of over temperature."

8

Communication Alarm

Upgrade Failure

Minor

"The HNB could not complete its upgrade successfully."

9

Communications Alarm

Filesystem Failure

Minor

"The HNB secondary file system has failed. (will be escalated to a System Failure if the fault cannot be cleared)."

10


Hot Spot Indication

Warning

"The HNB has detected an excessive number of attach rejects which indicates it is in a hotspot."

11


No NTP Server

Minor

"The HNB cannot connect to an NTP server to set its internal date/time clock."

12 Operational Violation "Potential change location into a different country. HNB home PLMN MCC has not been detected on



Instance number


Specific Problem

Invalid Country

Minor

any macro cells."

13


Gateway Changed

Warning

"The HNB has detected that it has potentially change location as the Home Gateway MAC address has changed"

14


Loss Of All Timing Server Connectivity

Minor

"The HNB has detected that all the configured timing servers are no longer contactable."

15


No Timing Source

Major

"No macro coverage, no timing servers, or LossOfAllTimingServerConnectivity alarm raised. HNB drift until timing restored"

16


Enterprise LAC Reuse Detected

Warning

"The HNB has detected that the LAC assigned to the enterprise is being used by a cell that is not part of the enterprise group"

17


Service Affecting Backhaul QoS

Major

"Backhaul Qos below threshold with only one CS call in progress. CS service will be affected."

18


Capacity Limiting Backhaul QoS

Major

“Backhaul Qos below threshold with several CS calls in progress. HNB may limit CS call capacity to maintain acceptable service level."

19

CommunicationAlarm

No SON Traffic Received from Small Cells peers

Warning

Inter-Small Cell P2P interface is enabled but no traffic received, check OAM and LAN config. The alarm clears when P2P traffic is received.

20

Environmental Alarm

Hardware Fault

Critical

The HNB has a detected a major hardware fault, refer to event log.

21 Not used

22


Congestion

Major

The AP has experienced signalling overload when already at minimum possible coverage

23

"Communications Alarm"

"Transmission Error"

Major

Communication Failure: CBC



253 UBS-44-57-004

Instance number


Specific Problem

24

"Communications Alarm"

"Application Subsystem Failure"

Major

Communication Failure: CBC

25 “Load/Congestion Alarm” "High Traffic Load" Warning

The HNB is consistently reaching its Erlang capacity

26

“Quality Of Service Alarm” "HNB PSC used by a tier 1 neighbour" Major

The HNB has detected that the PSC it is using is also in use on the same UARFCN by a tier 1 neighbour.

27

“Quality Of Service Alarm” "HNB PSC reused on same UARFCN" Major

The HNB has detected that the PSC it is using is also in use on the same UARFCN by a tier 1 neighbour.

28 “Quality Of Service Alarm” “PSC confusion detected” Major

The HNB has detected that the same PSC is in use by more than one neighbour on the same UARFCN

29 “Quality Of Service Alarm” “Cannot select PSC” Major

The HNB cannot use any of the provisioned PSC

30 “Quality Of Service Alarm” “ActiveSON timeout” Warning

AciveSON has timed out despite Inter-HNB SON connection established

31

“Quality Of Service Alarm” “Inconsistent UARFCNs detected” Warning

AciveSON has detected that the same UARFCN is not used throughout the grid

32

"Communications Alarm" "Application Subsystem Failure" Major

The HNB failed to register to the HNB-GW (HNB-GW rejection) or the HNB de-registered

33 "Communications Alarm" "IPSec connectivity failure" Major

The HNB has failed to establish or dropped the connection to the IPSec tunnel

34

"Communications Alarm" “HNBGW connectivity or SCTP association failure” Major

Service cannot be provided due to HNBGW service failure

35 "Communications Alarm" Operation State change Major

HNB’s RF radio transmitter has been disabled. The cell is no longer providing service

36

“Operation Violation” “Enclosure tampering detected” Critical

Physical tampering of the device enclosure has been detected

37 “Communications Alarm” ”Operation State change” Major

The eNB has failed to connect to any of the provisioned Security Gateways; multiple attempts have been made to each gateway

38

“Communications Alarm” “SON server coordination failed” Warning

The HNB is provisioned with a different set of servers than the other SON peers.

39 “Operation Violation” The HNB is operating beyond its maximum



Instance number


Specific Problem

“SON group size limit exceeded” Warning

supported number of SON secure peer connections. The HNB may become overloaded.

40

“Communications Alarm” “SON coordinated HNBGW Registration failed” Warning

The HNB failed to register to the same HNBGW as its peers (prevents Iurh handover).

41

"Quality Of Service Alarm" "Persistent HNB-GW Latency" Major

Persistent over-threshold HNB-GW response latency

Implemented after R3.4

Table 94: Supported alarm definition



255 UBS-44-57-004

4.15.1.2 Alarms Object The following table includes the alarms object stored in the database

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.SupportedAlarm

Supported Alarm Entries which can be raised by the FAP. The instance numbers for this table SHOULD be maintained across firmware upgrades of the device. At most one entry in this table can exist with all the same values for EventType, ProbableCause, SpecificProblem and PerceivedSeverity.

InternetGatewayDevice.Services.FAPService.1.FaultMgmt.SupportedAlarm.1 Fixed entry in the SupportedAlarm table

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Processing Error Alarm" RMS Default value:N/A RMS Property:N/A Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Critical" RMS Default value:N/A RMS Property:N/A Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Cannot Select RF Profile" RMS Default value:N/A RMS Property:N/A Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1



Object Parameter Description QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-1 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB is unable to select a valid set of RF parameters because of excessive interference." RMS Default value:N/A RMS Property:N/A Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" RMS Default value:N/A



257 UBS-44-57-004


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Software Error" RMS Default value:N/A RMS Property:N/A Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-2 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB detected a software problem which requires it to re-initialise in order to provide service." RMS Default value:N/A RMS Property:N/A Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared"



Object Parameter Description - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Minor" RMS Default value:N/A RMS Property:N/A Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "PM Report Failure" RMS Default value:N/A RMS Property:N/A Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-3 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB is unable to upload the PM files." RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService Fixed entry in the SupportedAlarm table



259 UBS-44-57-004

Object Parameter Description .1.FaultMgmt.SupportedAlarm.4

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Operational Violation" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Minor" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Location Changed" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-4 Management level: Solution or Customer

SpecificProblem Provides further qualification on the alarm beyond EventType and



Object Parameter Description ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that it has potentially changed location." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Quality Of Service Alarm" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Poor RF Qos" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.)



261 UBS-44-57-004

Object Parameter Description - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-5 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has measured that the QoS on the RF uplink and/or downlink have has diminished below a preset threshold." Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType.



Object Parameter Description See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Poor BackHaul QoS" RMS Property: FC-REPORTING-MECHANISM-6 Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-6Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has measured that the QoS on the backhaul connection have has diminished below a preset threshold." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Environmental Alarm" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL)



263 UBS-44-57-004

Object Parameter Description Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "High Temperature" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB shutdown because of over temperature." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None



Object Parameter Description FAP Default value: "Communications Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Upgrade Failure" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged”RMS Property: FC-REPORTING-MECHANISM-8 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ



265 UBS-44-57-004

Object Parameter Description Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB could not complete its upgrade successfully." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Communications Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Filesystem Failure" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued"



Object Parameter Description RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-9 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB secondary file system has failed. (will be escalated to a System Failure if the fault cannot be cleared)." Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Warning" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Hot Spot Indication" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of:



267 UBS-44-57-004

Object Parameter Description - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "2 Logged" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-10 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected an excessive number of attach rejects which indicates it is in a hotspot." Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration.



Object Parameter Description Notification: None FAP Default value: "Minor" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "No Ntp Server" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB cannot connect to an NTP server to set its internal date/time clock." Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical"



269 UBS-44-57-004

Object Parameter Description - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Minor" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Invalid Country" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Potential change location into a different country. HNB home PLMN MCC has not been detected on any macro cells." Management level: N/A


EventType Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm



Object Parameter Description types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Communications Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Gateway Changed" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "2 Logged" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-13 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the



271 UBS-44-57-004

Object Parameter Description table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that it has potentially change location as the Home Gateway MAC address has changed" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Loss Of All Timing-Server Connectivity" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.)



Object Parameter Description - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged”RMS Property: FC-REPORTING-MECHANISM-14 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that all the configured timing servers are no longer contactable." Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes.



273 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "No Timing Source" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "No macro coverage, no timing servers, or LossOfAllTimingServerConnectivity alarm raised. HNB drift until timing restored" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Processing Error Alarm" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity.



Object Parameter Description This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Warning" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Enterprise LAC Reuse Detected" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that the LAC assigned to the enterprise is being used by a cell that is not part of the enterprise group" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Quality Of Service Alarm"



275 UBS-44-57-004


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Service Affecting Backhaul QoS" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ



Object Parameter Description Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Backhaul QoS below threshold with only one CS call in progress. CS service will be affected" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Capacity Limiting Backhaul QoS" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None



277 UBS-44-57-004

Object Parameter Description FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-18 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Backhaul QoS below threshold with several CS calls in progress. HNB may limit CS capacity to maintain acceptable service level" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Environmental Alarm" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Critical" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Hardware Fault" Management level: N/A

ReportingMechanism Indicates the reporting mechanism setting of the alarm.



Object Parameter Description Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-20 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The AP has a detected a major hardware fault, refer to event log." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Equipment Alarm" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration.



279 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Hardware or Network Timing Problem" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Oscillator Stability Problem" Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major"



Object Parameter Description - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Congestion" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The AP has experienced signalling overload when already at minimum possible coverage" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types.



281 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Communications Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Transmission Error" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem.



Object Parameter Description The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Communication Failure: CBC" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Application Subsystem Failure" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.)



283 UBS-44-57-004

Object Parameter Description --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "2 Logged" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-24 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Communication Failure: CBC" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Load/Congestion Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None



Object Parameter Description FAP Default value: "High Traffic Load" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The FemtoEngine is consistently reaching its Erlang capacity" Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table.



285 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "HNB PSC in use on the same UARFCN by a tier 1 neighbour" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that the PSC it is using is also in use on the same UARFCN by a tier 1 neighbour." Management level: N/A


EventType


PerceivedSeverity Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of:



Object Parameter Description - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "HNB PSC is reused on the same UARFCN" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that the PSC, it is using is also in use on the same UARFCN." Management level: N/A



287 UBS-44-57-004

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.SupportedAlarm.28 Fixed entry in the SupportedAlarm table

EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "PSC confusion detected" Management level: N/A

ReportingMechanism


SpecificProblem Provides further qualification on the alarm beyond EventType and



Object Parameter Description ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has detected that the same PSC is in use by more than one neighbour on the same UARFCN" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Cannot select PSC" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.)



289 UBS-44-57-004

Object Parameter Description - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-29 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB cannot use any of the provisioned PSCs" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable



Object Parameter Description causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "ActiveSON timeout" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "AciveSON has timed out despite Inter-HNB SON connection established" Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity.



291 UBS-44-57-004

Object Parameter Description This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Warning" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Inconsistent UARFCNs detected" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "AciveSON has detected that the same UARFCN is not used throughout the grid" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Communications Alarm"




PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "HNB Registration Reject or Deregistered" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters).



293 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: "Service cannot be provided due to Iuh registration reject or deregistration" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "IPSec connectivity failure" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited"




SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB has failed to establish or dropped the connection to the IPSec tunnel" Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "HNBGW connectivity or SCTP association failure" Management level: N/A

ReportingMechanism Indicates the reporting mechanism setting of the alarm. Enumeration of:



295 UBS-44-57-004

Object Parameter Description - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-34 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Service cannot be provided due to HNBGW service failure" Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Major"




ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Operation State change" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "HNB's RF radio transmitter has been disabled and the cell is not providing service" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Operation Violation" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor"



297 UBS-44-57-004

Object Parameter Description - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Critical" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Enclosure tampering detected" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Physical tampering of the device enclosure has been detected" Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. ---



Object Parameter Description RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Operational Violation" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Long Term IPsec Failure" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "0 Expedited" RMS Property: FC-REPORTING-MECHANISM-37 RMS Default value: “2 Logged” Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a



299 UBS-44-57-004

Object Parameter Description subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The eNB has failed to connect to any of the provisioned Security Gateways; multiple attempts have been made to each gateway." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Communication Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "SON server coordination failed" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.)



Object Parameter Description --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued" RMS Default value: “2 Logged” RMS Property: FC-REPORTING-MECHANISM-38 Management level: Solution or Customer

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB is provisioned with a different set of servers than the other SON peers." Management level: N/A


EventType


PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters).



301 UBS-44-57-004

Object Parameter Description Notification: None FAP Default value: "SON group size limit exceeded" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB is operating beyond its maximum supported number of SON secure peer connections. The HNB may become overloaded." Management level: N/A


EventType


PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity.



Object Parameter Description The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Warning" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "SON Coordinated HNBGW Registration failed" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The HNB failed to register to the same HNB-GW as its peers (prevents Iurh handover)." Management level: N/A


EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Quality of Service" Management level: N/A

PerceivedSeverity Indicates the relative level of urgency for operator attention, see



303 UBS-44-57-004

Object Parameter Description ITU-X.733. Enumeration of: - "" (an empty string) - "*" - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity. This will be an empty string if the FAP doesn't support unique indexing of the table using PerceivedSeverity. The string can be set to "*" to indicate the default case if only a subset of PerceivedSeverity are to be contained within the table. --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Warning" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "Persistent HNB-GW Latency" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Persistent over-threshold HNB-GW response latency" Management level: N/A




EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 [24] for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: " Communication Alarm" Management level: N/A

PerceivedSeverity


ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: " IPC Communication Lost" Management level: N/A

ReportingMechanism

Indicates the reporting mechanism setting of the alarm. Enumeration of: - "0 Expedited" (The FAP inserts the alarm into the .FaultMgmt.0 ExpeditedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "1 Queued" (The FAP inserts the alarm into the .FaultMgmt.1 QueuedEvent.{i}. table and the .FaultMgmt.HistoryEvent.{i}. table.) - "2 Logged" (The FAP inserts the alarm into the .FaultMgmt.HistoryEvent.{i}. table.) - "3 Disabled" (The FAP ignores the alarm.) --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "1 Queued"



305 UBS-44-57-004


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "The IPC communication has been lost with the co-located module" Management level: N/A

Table 95 Alarms Object

4.15.1.2.1 Further Alarms


EventType


PerceivedSeverity





ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 [24] for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "No SON Traffic Received from Small Cell peers" Management level: N/A

ReportingMechanism


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support unique indexing of the table using SpecificProblem. The string can be set to "*" to indicate the default case if only a subset of SpecificProblem are to be contained within the table. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "Inter-Small Cell P2P interface is enabled but no traffic received, check OAM and LAN config." Management level: N/A

Table 96 Further Alarms

4.15.2 Current Alarms Contains all currently active alarms (whose .FaultMgmt.SupportedAlarm.{i}.PerceivedSeverity is not Cleared).

New raised alarms result in a new entry in this table being added, any changes to the alarm as a result of an update event are updated in the existing table entry, and a clear event raised against an alarm results in the alarm being removed from this table.

Active alarms at the time of a power failure or reboot are removed from this table.At most one entry in this table can exist with a given value for AlarmIdentifier, or with all the same values for EventType, ProbableCause and SpecificProblem.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.CurrentAlarm

Contains all currently active alarms (whose .FaultMgmt.SupportedAlarm.{i}.PerceivedSeverity is not Cleared). New raised alarms result in a new entry in this table being added, any changes to the alarm as a result of an update event are updated in the existing table entry, and a clear event raised against an alarm



307 UBS-44-57-004

Object Parameter Description results in the alarm being removed from this table. Active alarms at the time of a power failure or reboot are removed from this table. At most one entry in this table can exist with a given value for AlarmIdentifier, or with all the same values for EventType, ProbableCause and SpecificProblem.

AlarmIdentifier

Identifies one Alarm Entry in the Alarm List. This value MUST be uniquely allocated by the FAP to the alarm instance during the lifetime of the individual alarm. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime Management level: N/A

AlarmRaisedTime

Indicates the date and time when the alarm was first raised by the FAP. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime Management level: N/A

AlarmChangedTime

Indicates the date and time when the alarm was last changed by the FAP. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime Management level: N/A

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType. See 3GPP-TS.32.111-5 for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime Management level: N/A

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Value set at runtime




PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime Management level: N/A

AdditionalText

This provides a textual string which is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None Value set at runtime Management level: N/A

AdditionalInformation

This contains additional information about the alarm and is vendor defined. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None Value set at runtime Management level: N/A

ManagedObjectInstance

Specifies the instance of the Informational Object Class in which the FAP alarm occurred by carrying the Distinguished Name (DN) of this object instance. This object may or may not be identical to the object instance actually emitting the notification to the ACS. The .DNPrefix should be pre-pended to the local DN to create the ManagedObjectInstance. Encode the Managed Objects representation in string format as defined in 3GPP-TS.32.300 --- RMS Access: READ Type: String. (Length: 0 to 512 characters). Notification: None Value set at runtime Management level: N/A

Table 97 Current Alarms

4.15.3 History Events Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table. This table also contains alarm clearing events.

Active alarms at the time of a power failure or reboot may not get an alarm clearing event. If maximum instance number .FaultMgmt.HistoryEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers.



309 UBS-44-57-004

This logic provides for automatic "rolling" of records.

The data in this table is maintained across reboots.

At most one entry in this table can exist with the same values for EventTime and AlarmIdentifier.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.HistoryEvent

Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table. This table also contains alarm clearing events. Active alarms at the time of a power failure or reboot may not get an alarm clearing event. If maximum instance number .FaultMgmt.HistoryEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers. This logic provides for automatic "rolling" of records. The data in this table is maintained across reboots. At most one entry in this table can exist with the same values for EventTime and AlarmIdentifier.

EventTime

Indicates the date and time when the alarm event occurs. --- RMS Access: READ Type: dateTime. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 Management level: N/A

AlarmIdentifier

Identifies one Alarm Entry in the Alarm List. This value MUST be uniquely allocated by the FAP to the alarm instance during the lifetime of the individual alarm. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" Management level: N/A

NotificationType

Indicates the reason for the specific alarm notification event. Enumeration of: - "NewAlarm" - "ChangedAlarm" - "ClearedAlarm" --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "NewAlarm" Management level: N/A

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" Management level: N/A

ProbableCause

Qualifies the alarm and provides further information than EventType.



Object Parameter Description See 3GPP-TS.32.111-5 for information on predefined probable causes. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None FAP Default value: "" Management level: N/A

SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None FAP Default value: "" Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Indeterminate" Management level: N/A

AdditionalText

This provides a textual string which is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" Management level: N/A


This contains additional information about the alarm and is vendor defined. --- RMS Access: READ Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" Management level: N/A


Specifies the instance of the Informational Object Class in which the FAP alarm occurred by carrying the Distinguished Name (DN) of this object instance. This object may or may not be identical to the object instance actually emitting the notification to the ACS. The .DNPrefix should be pre-pended to the local DN to create the ManagedObjectInstance.



311 UBS-44-57-004

Object Parameter Description Encode the Managed Objects representation in string format as defined in 3GPP-TS.32.300 --- RMS Access: READ Type: String. (Length: 0 to 512 characters). Notification: None FAP Default value: "" Management level: N/A

Table 98 History Events

4.15.4 Expedited Events Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table if their corresponding entry in .FaultMgmt.SupportedAlarm.{i}. has .FaultMgmt.SupportedAlarm.{i}.ReportingMechanism set to 0 Expedited. This table also contains alarm clearing events.

This object has a fixed number of entries with instance numbers from 1 to .FaultMgmt.HistoryEventNumberOfEntries.

Initially the table starts with all instances having EventTime set to the Unknown Time value, as defined in [TR-106a2]. If maximum instance number .FaultMgmt.ExpeditedEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers.


When a new alarm replaces an existing alarm, then all parameter values for that instance are considered as changed for the purposes of value change notifications to the ACS (even if their new values are identical to those of the prior alarm).

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.ExpeditedEvent

Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table if their corresponding entry in .FaultMgmt.SupportedAlarm.{i}. has .FaultMgmt.SupportedAlarm.{i}.ReportingMechanism set to 0 Expedited. This table also contains alarm clearing events. This object has a fixed number of entries with instance numbers from 1 to .FaultMgmt.HistoryEventNumberOfEntries. Initially the table starts with all instances having EventTime set to the Unknown Time value, as defined in [TR-106a2]. If maximum instance number .FaultMgmt.ExpeditedEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers. This logic provides for automatic "rolling" of records. When a new alarm replaces an existing alarm, then all parameter values for that instance are considered as changed for the purposes of value change notifications to the ACS (even if their new values are identical to those of the prior alarm).

EventTime

Indicates the date and time when the alarm event occurs. --- RMS Access: READ Type: dateTime. (Range: 0 to 4294967295). Notification: Active Value set at runtime Management level: N/A




AlarmIdentifier


NotificationType

Indicates the reason for the specific alarm notification event. Enumeration of: - "NewAlarm" - "ChangedAlarm" - "ClearedAlarm" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime Management level: N/A

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 for information on predefined alarm types. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime Management level: N/A

ProbableCause


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Value set at runtime Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a



313 UBS-44-57-004

Object Parameter Description PerceivedSeverity --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime Management level: N/A

AdditionalText






Table 99 Expedited Events

4.15.5 Queued Events Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table if their corresponding entry in .FaultMgmt.SupportedAlarm.{i}. has .FaultMgmt.SupportedAlarm.{i}.ReportingMechanism set to 1 Queued. This table also contains alarm clearing events.

This object has a fixed number of entries with instance numbers from 1 to .FaultMgmt.HistoryEventNumberOfEntries.

Initially the table starts with all instances having EventTime set to the Unknown Time value, as defined in [TR-106a2].

If maximum instance number .FaultMgmt.QueuedEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers.




When a new alarm replaces an existing alarm, then all parameter values for that instance are considered as changed for the purposes of value change notifications to the ACS (even if their new values are identical to those of the prior alarm).

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.FaultMgmt.QueuedEvent

Alarm events added or updated in .FaultMgmt.CurrentAlarm.{i}. are simultaneously entered into the this table if their corresponding entry in .FaultMgmt.SupportedAlarm.{i}. has .FaultMgmt.SupportedAlarm.{i}.ReportingMechanism set to Queued. This table also contains alarm clearing events. This object has a fixed number of entries with instance numbers from 1 to .FaultMgmt.HistoryEventNumberOfEntries. Initially the table starts with all instances having EventTime set to the Unknown Time value, as defined in [TR-106a2]. If maximum instance number .FaultMgmt.QueuedEventNumberOfEntries is reached, the next event overrides the object with instance number 1. Subsequent entries override objects at sequentially increasing instance numbers. This logic provides for automatic "rolling" of records. When a new alarm replaces an existing alarm, then all parameter values for that instance are considered as changed for the purposes of value change notifications to the ACS (even if their new values are identical to those of the prior alarm).

EventTime

Indicates the date and time when the alarm event occurs. --- RMS Access: READ Type: dateTime. (Range: 0 to 4294967295). Notification: Passive Value set at runtime Management level: N/A

AlarmIdentifier


NotificationType

Indicates the reason for the specific alarm notification event. Enumeration of: - "NewAlarm" - "ChangedAlarm" - "ClearedAlarm" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime Management level: N/A

EventType

Indicates the type of FAP event. See 3GPP-TS.32.111-5 for information on predefined alarm types. ---



315 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime Management level: N/A

ProbableCause


SpecificProblem

Provides further qualification on the alarm beyond EventType and ProbableCause. This is not 3GPP standards based and is vendor defined. This will be an empty string if the FAP doesn't support inclusion of this information. --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Value set at runtime Management level: N/A

PerceivedSeverity

Indicates the relative level of urgency for operator attention, see ITU-X.733. Enumeration of: - "Cleared" - "Critical" - "Major" - "Minor" - "Warning" - "Indeterminate" (OPTIONAL) Although Indeterminate is defined in ITU-X.733 it SHOULD NOT be used by the FAP as a PerceivedSeverity --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime Management level: N/A

AdditionalText









Table 100 Queued Events



317 UBS-44-57-004

4.16 Performance Management The HNB collects measurements and reports them in a performance management report which will be uploaded to the Performance Management System (PMS). The PMS can then use these measurements to calculate the relevant Key Performance Indicators (KPIs).

4.16.1.1 Reference Documents Full details can be found:

• USC-44-12-002 Definition, Configuration and Reporting of PM Counters for Iuh

4.16.2 Parameters used for Performance Management Reports

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.PerfMgmt This object contains parameters relating to

Performance Management. InternetGatewayDevice.Services.FAPService.1.PerfMgmt.FileMgmt

This object contains parameters relating to File Management for uploading of Performance Files to a designated File Server.

PeriodicUploadEnable

Enables or disables the ability to send FAP information periodically to a designated File Server. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value: TRUE RMS Property: FC-LOG-PERIODIC-UPLOAD-ENABLE Management level: Solution or Customer

URL

URL specifying the destination file location. HTTP and HTTPS transports MUST be supported. Other optional transports MAY be supported. This argument specifies only the destination file location, and does not indicate in any way the name or location of the local file to be uploaded. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:Input RMS Property: FC-LOG-PERIODIC-UPLOAD-URL Management level: Solution or Customer

PeriodicUploadInterval

The duration in seconds of the interval for which the FAP MUST create an Performance File and attempt to upload the file to URL if PeriodicUploadEnable is true. --- RMS Access: READ/WRITE Type: Integer. (Range: 900 to 4294967295). Notification: None FAP Default value: 900 RMS Default Value: 86400/900 RMS Property:FC-LOG-PERIODIC-UPLOAD-INTERVAL/ FC-LOG-PERIODIC-UPLOAD-INTERVAL-ENT Management level: Solution or Customer

PeriodicUploadTime

An absolute time reference in UTC to determine when the FAP will initiate the periodic file upload. Each file upload MUST occur at this reference time plus or minus an integer multiple of the PeriodicUploadInterval. PeriodicUploadTime is used only to set the "phase" of the



Object Parameter Description periodic uploads. The actual value of PeriodicUploadTime can be arbitrarily far into the past or future. For example, if PeriodicUploadInterval is 86400 (a day) and if PeriodicUploadTime is set to UTC midnight on some day (in the past, present, or future) then periodic file uploads will occur every day at UTC midnight. These MUST begin on the very next midnight, even if PeriodicUploadTime refers to a day in the future. The Unknown Time value as defined in [TR-106a2] indicates that no particular time reference is specified. That is, the FAP MAY locally choose the time reference, and is required only to adhere to the specified PeriodicUploadInterval. If absolute time is not available to the FAP, its periodic file upload behavior MUST be the same as if the PeriodicUploadTime parameter was set to the Unknown Time value. Ubiquisys FAPs will perform the upload in the Least Busy Hour when an Unknown Time value is set --- RMS Access: READ/WRITE Type: dateTime. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Default value: Random Value RMS Property: N/A Management level: N/A

X_UBIQUISYS_COM_ForceFileSend

When set to TRUE it will force an immediate upload of the PM file. Flag is automatically reset to FALSE when the action is complete. --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

X_UBIQUISYS_COM_AddCurrentlAlarmInformation

When set to TRUE it will force the ALARM indication block to be output to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

X_UBIQUISYS_COM_AddNeighbourListMetrics

When set to TRUE it will force the NeigbourList metrics to be output to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

X_UBIQUISYS_COM_AddOperationalParameters

When set to TRUE it will force the Cell Operational Parameters to be output to the PM file ---



319 UBS-44-57-004

Object Parameter Description RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

X_UBIQUISYS_COM_AddGPSLocation

When set to TRUE it will force the GPS location parameters to be output to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_AddHandoutStatsByNeighbour

When set to TRUE it will force the handout state by neighbour metrics to be output to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

X_UBIQUISYS_COM_AddREMScan

When set to TRUE it will force the REM scan results to be output to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

X_UBIQUISYS_COM_AddQualifiedCandidates

When set to TRUE it will force the UE detected cells to be reported to the PM file --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:TRUE RMS Property: FC-QUALIFIED-CANDIDATES Management level: Deployment specific or Customer

X_UBIQUISYS_COM_JobId

JobID to be used as a part of the PM file name. If it is configured, then the 3G SC appends JobID as a part of the PM file name. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 50 characters). Notification: None FAP Default value: "" RMS Default value: "" RMS Property: FC-JOB-ID Management level: Solution or Customer

X_UBIQUISYS_COM_UseGzipForCompression

Enables or disables PM file compression before uploading using gzip. When enabled the PM file suffix is replaced with .xml.gz in place of .xml. --- RMS Access: READ/WRITE



Object Parameter Description Type: Boolean. Notification: None FAP Default value: True RMS Default value:N/A RMS Property:N/A Management level: Default

X_UBIQUISYS_COM_PeriodicUploadMaxDelay

Random delay in mInutes to be applied to the PeriodicUploadTime to avoid all HNBs trying to upload at the same time if the PeriodicUploadTime is same for all HNBs. HNB will conver this to seconds before chosing the random time delay. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 20). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_AddHandoverLatencyDistributions

--- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Deployment specific or Customer

InternetGatewayDevice.Services.FAPService.1.PerfMgmt.X_UBIQUISYS_COM_LBH

This object contains parameters relating to Least Busy Hour tracking and control

LeastBusyHour

The least busy hour of the ZAP. The least busy hour is calculated as the middle of the longest period of least number of active RABs. --- RMS Access: READ Type: Integer. (Range: 0 to 23). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LeastBusyHourAccumulationPeriod

Number of days worth of LBH info that has been stored in the LHBHistory. Max is 7 days - once it has reached this point, further days' history is averaged with existing data --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

NextLeastBusyHourExpiryTime

The time when the least busy hour is next due to occur --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A



321 UBS-44-57-004

Table 101 Parameters used for Performance Management Reports

4.16.3 Supported Counters 4.16.3.1 HNB Gateway Interface

The following counters are supported by the Cisco platform. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.PerfMgmt.X_UBIQUISYS_COM_Reports This object contains control of individual PM reports OverridePeggingPeriod

Global override for counter pegging parameters. When an individual pegging parameter has been enabled this override will be applied. The override does not apply for individual pegging parameter is off. --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "OverrideOff" RMS Default value:OverrideOff RMS Property: For residential use FC-PEGGING-PERIOD-OVERRIDE For Enterprise use FC-PEGGING-PERIOD-OVERRIDE Management level: Solution



4.17 Event Logs This object contains parameters relating to event logging feature. The feature is detailed in the following document:

• USC-44-54-010 USC Alarms Summary R3_5

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_EventLog This object contains the event log for the FAP

MaxLength

Max number of events in the event list. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 50 RMS Deafult value:50 RMS Property : EVENT-LOG-MAX-LENGTH Management level: Solution or Customer

EventListNumberOfEntries

Number of events in the event list. --- RMS Access: READ Type: Integer. (Range: 0 to 100). Notification: None FAP Default value: 0 RMS Deafult value:N/A RMS Property:N/A Management level: N/A

WriteIndex

Index of the oldest entry in the event list --- RMS Access: READ Type: Integer. (Range: 0 to 99). Notification: None FAP Default value: 0 RMS Deafult value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_EventLog.EventList List of events the FAP has previously logged.

EventDescription

Description of the event --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None FAP Default value: "" RMS Deafult value:N/A RMS Property:N/A Management level: N/A

EventDateTime

Time and date that the event occurred --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None FAP Default value: 0 RMS Deafult value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_EventLog.Suppression

This object provides support to suppress event codes from the EventLog. This can be used to prevent swamping of the finite length EventLog by frequently occuring events



323 UBS-44-57-004


EventCode46

Set true to suppress EventCode 46 from the EventLog --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Deafult value:N/A RMS Property:N/A Management level: System

Congestion

Set true to suppress Congestion event from the EventLog --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Deafult value:N/A RMS Property:N/A Management level: System

Table 102 Event Logs



4.18 Diagnostics This object contains parameters relating to fault diagnostics. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Diagnostics Object name

FactoryRecovery

If set to non-zero then the HNB will reboot and enter Factory Recovery mode as indicated below. The HNB will automatically clear this field once it has completed the operation. 0 - No Recovery 1 - Immediate Recovery 2 - Recovery In Least Busy Hour 3 - Recovery On Next Power Up --- RMS Access: WRITE Type: Enumeration. Reboot triggered by SetParameterValue. Notification: None FAP Default value: "No Recovery" RMS Deafult value:N/A RMS Property:N/A Management level: Solution or Customer

TraceFileSize

Limits the size of the circular local trace buffer to the last n Mb of trace. The value is in Mb. A value of 0 indicates that local trace should be disabled --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 5). Notification: None FAP Default value: 2 RMS Deafult value:N/A RMS Property:N/A Management level: System

PostEventPeriod

Indicates how long after the event that local trace should be allowed to continue before the local-trace buffer is copied and prepared for uploading. The value is in seconds. A value of 0 indicates no post-event delay. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 300). Notification: None FAP Default value: 1 RMS Deafult value:N/A RMS Property:N/A Management level: System

PostEventUploadURL

The FQDN or IP address of the server where the Post Event Diagnostics tarballs should be uploaded to. An empty string will indicate that uploading (as opposed to collection and packaging) is disabled. --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Notification: None FAP Default value: "" RMS Default value:empty RMS Property: FC-LOG-PERIODIC-UPLOAD-URL Management level: System

PostEventMaxFiles

Maximum number of Post Event Diagnostics tarballs that should be queued for uploading. --- RMS Access: READ/WRITE



325 UBS-44-57-004

Object Parameter Description Type: Integer. (Range: 1 to 10). Notification: None FAP Default value: 3 RMS Deafult value:N/A RMS Property:N/A Management level: System

TriggerImmediatePostEventUpload

Trigger an immediate creation and upload of a Post Event Diagnostics (PED) file to the FTP server configured above --- RMS Access: WRITE Type: Boolean. Notification: None Value set at runtime FAP Default value: 0 RMS Deafult value:N/A RMS Property:N/A Management level: System

TraceProfile0

An encoded string containing the trace level setting for all relevant modules and interfaces for a trace profile with the lowest overhead --- RMS Access: READ/WRITE Type: String. (Length: 0 to 2048 characters). Notification: None FAP Default value: "" RMS Default value:”” RMS Property: FC-TRACE-PROFILE-0 Management level: System

TraceProfile1

An encoded string containing the trace level setting for all relevant modules and interfaces for a trace profile with a medium overhead --- RMS Access: READ/WRITE Type: String. (Length: 0 to 2048 characters). Notification: None FAP Default value: "" RMS Default value: “” RMS Property: FC-TRACE-PROFILE-1 Management level: System

TraceProfile2

An encoded string containing the trace level setting for all relevant modules and interfaces for a trace profile with the maximum overhead --- RMS Access: READ/WRITE Type: String. (Length: 0 to 2048 characters). Notification: None FAP Default value: "" RMS Default value:”” RMS Property: FC-TRACE-PROFILE-2 Management level: System

SetCurrentTraceProfile

Allows the default behaviour of choosing a different trace profile to be overridden until the next reboot. -1 means that the FAP is allowed to choose its own local trace levels. 0 means that the FAP must use trace profile 0 (low levels of trace) 1 mean --- RMS Access: READ/WRITE Type: Integer. (Range: -1 to 2). Notification: None Value set at runtime



Object Parameter Description FAP Default value:-1 RMS Default value:-1 RMS Property: FC-CURRENT-TRACE-PROFILE Management level: System

InServiceChecking

Controls periodic In-Service checks: 0 - Disabled. 1 - Enable periodic PED upload when not In-Service. 2 - Enable PED upload when not In-Service and then reboot when FAP has not been In-Service for two consecutive checks. 3 - Enable reboot wen FAP has not been In-Service for two consecutive checkes (No PED upload). Warning: Many PED files may be generated when configured with options 1 and 2, when taking FAPs out of service for routine maintenance. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 3). Notification: None FAP Default value: 0 RMS Default value: 0 / RF Profile v. 2.3 Modify RMS Property: ALPHA-INSERVICE-CHECK Management level: Deployment

AutomaticRebootDelay

Sets the automatic reboot delay period in days (0=off). When this period elapses a reboot will occur in the next Least Busy Hour on a PDQ basis --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 365). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: System

CPUResourceMismatchActions

Action to take when connection rejected due to CPU overload but no resources taken in RRC: TRUE: None, FALSE: Reboot --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: System

EnterpriseMonitorServerURL

The FQDN or IP address of the realtime server to which the FAP is sending database AVPs. These are used for FAP debug in the field and/or monitoring of FAPs in an enterprise grid --- RMS Access: READ/WRITE Type: String. (Length: 0 to 256 characters). Reboot triggered by SetParameterValue. Notification: None FAP Default value: "" RMS Default value:empty RMS Property: FC-ENT-MONITOR-SERVER-URL Management level: N/A

CDRReportingMode

Enables reporting mode for call drop records 0 - Off 1 - Trace Only



327 UBS-44-57-004

Object Parameter Description 2 - PM only 3 - Trace and PM File --- RMS Access: READ/WRITE Type: Enumeration. Notification: None FAP Default value: "Trace Only" RMS Default value: Off / RF Profile Modify RMS Property: ALPHA-IN-CDR-REPORT-MODE Management level: System

Table 103 Diagnostics

4.19 User GUI

The HNB provides access of a number of parameters via a local GUI, accessed from a Web browser on a local network. A Java Application is used to discover Cisco’s devices on the same LAN via IP multicasting.

The feature is enabled by the HMS. The web page allows to view and modify the following parameters:

Object Parameter RMS Access Local GUI Access InternetGatewayDevice InternetGatewayDevice.DeviceInfo SerialNumber Yes READ SoftwareVersion Yes READ X_UBIQUISYS_COM_ChassisSN Yes READ InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1

ExternalIPAddress Yes READ SubnetMask Yes READ DefaultGateway Yes READ DNSServers Yes READ X_UBIQUISYS_COM_VLANEnabled None READ/WRITE X_UBIQUISYS_COM_VLANID None READ/WRITE MACAddress Yes READ InternetGatewayDevice.Services.FAPService.1.FAPControl RFTxStatus Yes READ X_UBIQUISYS_COM_RFStatus None READ X_UBIQUISYS_COM_LEDStatus None READ InternetGatewayDevice.Services.FAPService.1 X_UBIQUISYS_COM_ModelCode Yes READ InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.ProvisioningInfo

EnterpriseID Yes READ GroupID Yes READ GroupSiteID Yes READ InternetGatewayDevice.Services.FAPService.1.AccessMgmt

HomeZoneName Yes READ InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_PartnerQoS.ServiceMapping8021P

Conversational None READ/WRITE StreamingPS None READ/WRITE InteractivePS_Priority1 None READ/WRITE InteractivePS_Priority2 None READ/WRITE



Object Parameter RMS Access Local GUI Access InteractivePS_Priority3 None READ/WRITE BackgroundPS None READ/WRITE Signalling None READ/WRITE OAMP None READ/WRITE IPT None READ/WRITE

Table 104: Parameters access from the Local GUI

NOTE that parameters with “None” HMS READ Access, are only readable from the Local GUI. For this parameter it is assumed that no control or visibility from HMS is required.

4.19.1 Parameters Controlling the User GUI Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_LocalGUI Security configuration

GUIName

Friendly display name for the unit to be displayed on the local owner GUI in preference to MAC address or IP address --- RMS Access: READ Type: String. (Length: 0 to 1024 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

4.20 QoS In the case of the standalone (non-integrated to a gateway router) HNB, the uplink bandwidth (Ethernet) and packet forwarding capability of the HNB is generally considered to be such that only a simple treatment of each packet with respect to classification, queuing and prioritization is required (egress bandwidth is always greater than the aggregate ingress bandwidth in the uplink direction). Therefore, a simple priority-based algorithm is used to ensure that high-priority (e.g. CS) traffic is not blocked by large numbers of lower priority (e.g. data) packets at the egress of the AP in either direction.

Additionally, the HNB marks each traffic type based on “service mapping” as described below for appropriate QoS treatment at the home gateway router.

4.20.1 Service Mapping Service mapping directly associates the traffic type to a DSCP value.

The different traffic classes being considered for service mapping are somewhat similar to the PHB mapping and are defined in the object .X_UBIQUISYS_COM_PartnerQoS.ServiceMapping as Conversational, StreamingPS, InteractivePS_Priority1, InteractivePS_Priority2, InteractivePS_Priority3, BackgroundPS, Signalling, OAMP and IPT. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_PartnerQoS Values used in Service mapping scheme



329 UBS-44-57-004

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_PartnerQoS.ServiceMapping Values used in Service mapping scheme

Conversational

DSCP used for conversational traffic (speech, video, conversational PS calls). Default is Expedited Forwarding. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 46 RMS Default value:N/A RMS Property:N/A Management level: Solution

StreamingPS

DSCP used for streaming PS. Default is Assured Forwarding Class 4. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 34 RMS Default value:N/A RMS Property:N/A Management level: Solution

InteractivePS_Priority1

DSCP used for Interactive PS with a traffic handling priority of 1 (Highest). Default is Assured Forwarding Class 3. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 26 RMS Default value:N/A RMS Property:N/A Management level: Solution


DSCP used for Interactive PS with a traffic handling priority of 2. Default is Assured Forwarding Class 2. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 18 RMS Default value:N/A RMS Property:N/A Management level: Solution


DSCP used for Interactive PS with a traffic handling priority of 3. Default is Assured Forwarding Class 1. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Solution

InteractivePSPriorityTHPIMSSignalling

DSCP to be used for Interactive PS RABs with the Traffic Handling Priority value defined for IMS signalling PS RAB --- RMS Access: READ/WRITE



Object Parameter Description Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 26 RMS Default value:26 RMS Property: FC-INTERACTIVE-PSPRIORITY-THP-IMS-SIGNALLING Management level: Solution

BackgroundPS

DSCP used for background PS. Default is Assured Forwarding Class 1. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Solution

Signalling

DSCP used for signalling connections in to an IMS or RANGW core network. Default is Assured Forwarding Class 3. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 26 Management level: Solution

OAMP

DSCP used for OAMP/TR069 connections. Default is Assured Forwarding Class 1. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Solution

IPT

DSCP used for IP timing server connections. Default is Assured Forwarding Class 1. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 63). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 10 RMS Default value:N/A RMS Property:N/A Management level: Solution

Table 105 Service Mapping



331 UBS-44-57-004

4.21 Backhaul QoS Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_BackhaulQoS Backhaul QoS RTCPAllocatedBandwidth This parameter defines the proportion of each

estimated overall bandwidth session to be used for RTCP. It configures the RTCP packets frequency, or more practically, the inter-RTCP time. A value of zero disables RTCP and the dynamic BQoS feature. As the estimated bandwidth for a session depends on the type and number of streams and IP network conditions, the theoretical value is accompanied by a range of time difference which may occur (+- 5 seconds) If RTCPAllocatedBandwitdh value is set to n %, FAP transmits RTCP each approximately t +/-5 seconds, where t seconds = 96 bytes / (BW_S * n %). BW_S is about 113.5 bytes/s for CS calls and 192 bytes/s for video calls --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 20). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

StaticMeasurementStatus Status of static measurements: - Unknown - Service Affecting - Capacity Affecting - Good --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”unknown” RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 106 Backhaul QoS



4.22 Small Cell Metrics

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SmallCellMetrics SmallCellMetrics configuration Enable The FemtoEngine shall support a new Operator

configurable parameter that enables/disables the Small Cell Metrics feature. This feature shall be enabled/disabled through the use of an on/off switch. 1: Enable 0: Disable --- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: TRUE RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer

ErlangThreshold The FemtoEngine shall support a new Operator configurable data model parameter that specifies the percentage of the Erlang capacity that is used for thresholding purposes. --- RMS Access: READ/WRITE Type: Integer. (Range: 10 to 100). Notification: None FAP Default value: 90 RMS Default value:N/A RMS Property:N/A Management level: Solution or Customer



333 UBS-44-57-004

4.23 VLAN

Operators envisage the deployment of HNBs within Organisation where the underlined physical network is subdivided in logical networks by employing VLAN tagging. The benefit of data separation between other traffic offers a level of security; moreover, the standard offers the possibility of applying prioritisation marking to different classes of traffic. Cisco HNB supports the IEEE 802.1Q standard

The HNB shall activate VLAN tagging from either:

• DHCP Server Vendor Specific Information Options 43

• “Customer GUI” (only in case of static IP address).

The HNB shall use the following VLAN tags:

• TDIP (as per standard)

• VID as set by DHCP server (using Vendor Specific Information) or by the “Customer GUI” (in case of static IP address).

• PCP: configuration and mapping to HNB traffic types

• CFI = 0. Always.

If the HNB is configured with VID other than 0 (and VLAN tagging is used), the HNB shall ignore: all packets with different VID tagging AND those packets without VLAN tagging.

If the HNB is configured with VID equal to 0 (and VLAN tagging is used), the HNB shall only ignore all packets with VID not equal to 0. Note that packet without VLAN tagging will not be ignored (this is due to the fact that a value of 0 is defined as a frame which does not belong to any VLAN).

If the HNB is configured not to use VLAN tagging, the HNB shall ignore all VLAN packets.

Configuration of the “Priority Code Points” for different services shall only be configurable in the following ways:

• Via DCHP with Option 43 (using the “Vendor Specific Infos”)

• Via “Customer GUI”, when static IP addressing is used.

The HNB shall map the following traffic types to the PCP with the following default settings:

HNB traffic types 802.1Q Traffic Priority values

As defined in [1], Sect. G4

Default PCP value Acronyms Traffic Type

Conversational 5 VO “Voice,” < 10 ms latency and jitter

StreamingPS 4 VI “Video,” < 100 ms latency and jitter

InteractivePS_Priority1 3 CA Critical Applications

InteractivePS_Priority2 2 EE Excellent Effort

InteractivePS_Priority3 0 BE Best Effort

BackgroundPS 1 BK Background



Signalling 3 CA Critical Applications

OAMP 0 BE Bests Effort

IPT 2 EE Excellent Effort

Note that all others traffic types will be regarded as being erroneous and ignored. (these are: QoSMappingType, ExpeditedForwarding, AssuredForwardingClass4, AssuredForwardingClass3, AssuredForwardingClass2, AssuredForwardingClass1).

All other traffic types shall be given a default PCP value provided by the DHCP Option 43, or 0 (Best Effort) if not specified.

The HNB shall activate the VLAN tagging protocol in the following methods:

• DHCP Server Vendor Specific Information Options 43

• Via “Customer GUI” when static IP address is used.

Note that VLAN tagging will not be activated or deactivated from HMS or APMS; as this may leave the HNB in a state where a hardware reset is required.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Network Object name InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Network.IP Object name State Defines the state of the network interface: 0 -

disconnected, do not use 1 - connected but with no IP address assigned, use only for multicast 2 - connected with an IP address assigned. --- RMS Access: READ Type: Integer. (Range: 0 to 2). Notification: None Parameter modified via activation server. FAP Default value :0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Interface Primary Ethernet interface: e.g. eth0 for no VLAN and eth0.0 for VLAN 0 --- RMS Access: READ Type: String. (Length: 2 to 10 characters). Notification: None Parameter modified via activation server. FAP Default value :"eth0" RMS Default value:N/A RMS Property:N/A Management level: N/A

Address Ethernet interface IP address as a dotted-quad string --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A



335 UBS-44-57-004

Object Parameter Description Netmask Ethernet IP address netmask as a dotted-quad string

--- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Parameter modified via activation server. FAP Default value :"" RMS Default value:N/A RMS Property:N/A Management level: N/A

Broadcast Ethernet broadcast IP address as a dotted-quad string --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None Parameter modified via activation server. FAP Default value :"" RMS Default value:N/A RMS Property:N/A Management level: N/A

Gateways One or more space-separated gateway addresses as a dotted-quad strings --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

StaticRoutes Zero or more static routes in format: destinationIP gateway destinationIP gateway .. --- RMS Access: READ Type: String. (Length: 0 to 1024 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Domain Default search domain (e.g. ubiquisys.local) --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

DNS One or more space-separated DNS server addresses as a dotted-quad strings --- RMS Access: READ Type: String. (Length: 0 to 128 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A



Object Parameter Description ManufacturerOUI Gateway organizationally unique identifier of the

device manufacturer. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros, as returned in DHCP option 125 --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

ProductClass Gateway product class as returned in DHCP option 125 --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

SerialNumber Gateway serial number as returned in DHCP option 125 --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Parameter modified via activation server. FAP Default value "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Conversational Class of service for conversational data (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 5 RMS Default value:N/A RMS Property:N/A Management level: N/A

StreamingPS Class of service for streaming PS data (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 4 RMS Default value:N/A RMS Property:N/A Management level: N/A

InteractivePS_Priority1 Class of service for interactive PS data, priority 1 (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None



337 UBS-44-57-004

Object Parameter Description Parameter modified via activation server. FAP Default value 3 RMS Default value:N/A RMS Property:N/A Management level: N/A

InteractivePS_Priority2 Class of service for interactive PS data, priority 2 (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 2 RMS Default value:N/A RMS Property:N/A Management level: N/A

InteractivePS_Priority3 Class of service for interactive PS data, priority 3 (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 0 Management level: N/A

BackgroundPS Class of service for background PS data (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 1 RMS Default value:N/A RMS Property:N/A Management level: N/A

Signalling Class of service for signalling data to the core network(Only used VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 3 RMS Default value:N/A RMS Property:N/A Management level: N/A

OAMP Class of service for OAMP/TR069 data (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None Parameter modified via activation server. FAP Default value 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

IPT Class of service for IP timing data (Only used if VLAN is enabled) --- RMS Access: READ Type: Integer. (Range: 0 to 7). Notification: None



Object Parameter Description Parameter modified via activation server. FAP Default value 2 RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 107 VLAN



339 UBS-44-57-004

4.24 Home Gateway

4.24.1 Home Gateway Information This object contains the parameters relating to the home gateway, these are acquired the Vendor-Specific Information DHCP Option as specified in [TR-111].

Object Parameter Description InternetGatewayDevice.X_UBIQUISYS_COM_GatewayInfo Object name

ManufacturerOUI

Organizationally unique identifier of the device manufacturer. Represented as a six hexadecimal-digit value using all upper-case letters and including any leading zeros. The value MUST be a valid OUI --- RMS Access: READ Type: String. (Length: 6 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

ProductClass

Identifier of the class of product for which the serial number applies. That is, for a given manufacturer, this parameter is used to identify the product or class of product over which the SerialNumber parameter is unique. --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

SerialNumber

Serial number of the Gateway --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 108 Home Gateway Information



4.24.2 Home Gateway Change Detection The following parameters can be used to report the Gateway MAC address; other parameters are used to support the HNB Location Verification feauture described in section 8.

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_HomeGateway Home Gateway security

GatewayMACAddress

Gateway MAC address. String format: xx:xx:xx:xx:xx:xx --- RMS Access: READ Type: String. (Length: 0 to 17 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

Table 109 Home Gateway Change Detection



341 UBS-44-57-004

4.25 Licencing The following object contains the Licencing parameters for the features of the HNB.

4.25.1 Licencing Solution The parameters in the object .X_UBIQUISYS_COM_Licencing.Features. are set by the Activation Server and cannot be modified by the HMS. Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Licencing Object name InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Licencing.Features Object name

Base

Shows whether the base licence is present. If this is not present then the FAP will not provide service. This licence cannot be overridden (but the OpState flag can be used from the HMS for a similar effect) --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HSUPACAT4_29

Shows whether HSUPA Cat 4 (2.9Mbps) data rates are licenced --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HSUPACAT6_574

Shows whether HSUPA Cat 6 (5.74Mbps) data rates are licenced --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HSDPA14Codes

Shows whether HSDPA is licenced to use up to 14 codes when R99 call volume allows --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HSDPA_plus

Shows whether EvolvedHSDPA (aka HSDPA+) is licenced for Cat 13/14 data rates --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE




Calls8

Shows whether up to 8 DCHs are licenced to be used simultaneously (hardware permitting) On PRC6000 hardware 8 DCHs are possible with Single SCCPCH but this falls to 7 if Dual SCCPCH is enabled On PRC6500 hardware 8 DCHs are possible regardless of whether Dual SCCPCH is enabled or not --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

Calls16

Shows whether up to 16 DCHs are licenced to be used simultaneously (hardware permitting) On PRC6000 hardware only 8 DCHs are possible (or 7 if Dual SCCPCH is enabled) On PRC6500 hardware the full 16 DCHs are available (or 15 if Dual SCCPCH is enabled) Note that the Calls8 licence is not required in addition to this licence --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

ExtendedRange

Shows whether extended range functionality is licenced for use. This allows the FAP to respond to RACH attempts from UEs up to 27 chips (~2km) away from the FAP. With the feature disabled the max UE distance is 3 chips (~225m). --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

LocalLANTrace

Shows whether tracing using the ZoneGate Trace Tool via the local LAN is licenced for use Note that this is a security vunerability if enabled in an uncontrolled manner on commercial units. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

RTPMultiplexing

Shows whether RTP multiplexing is licenced for use on voice calls.



343 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HandInRelocation

Shows whether the FAP supports CS and/or PS Hand-In --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

StraddledCarrier

Shows whether straddled carrier functionality is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

LoadBasedCoverageTuning

Shows whether the Load Based Coverage Tuning feature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

MedMobCap

Shows whether the medium User Mobilityfeature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

HiMobCap

Shows whether the high User Mobilityfeature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE Management level: N/A

HiData

Shows whether the high level Aggregate Data Throughput feature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A




OperatorGUI

Shows whether the operator GUI is licenced for use. This controls the ACS simulator access in commercial mode. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

OpenAccessMode

Shows whether Open Access Mode is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

SemiOpenAccessMode

Shows whether Semi Open Access Mode is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

Cell_PCH_FD

Shows whether CELL_PCH and fast dormancy is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

CellBroadCast

Shows whether Cell Broadcast is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

LTE_Mob

Shows whether LTE Mobility features including SIB19 and CSMT is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

LIPA

Shows whether LIPA feature is licenced for use. ---



345 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

ActiveSON

Shows whether Active SON is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

QSS_HSCO_HANR_Support

Shows whether support for Cisco QSS HSCO and HANR is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

UL_Traffic_Shaping

Shows whether UL Traffic Shaping feature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

Sniff_900MHz

Shows whether 900 MHz G3 sniff is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:FALSE RMS Property:N/A Management level: N/A

IurhHandover

Shows whether Iurh based hadover is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A Management level: N/A

WB_AMR

Shows whether the WB-AMR feature is licenced for use. --- RMS Access: READ Type: Boolean. Notification: None FAP Default value: FALSE RMS Default value:N/A RMS Property:N/A




Table 110 Licencing Solution

4.26 Uplink Traffic Shaping

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_UplinkTrafficShaping Object name Enabled Enables or disables Uplink Traffic Shaping feature.

--- RMS Access: READ/WRITE Type: Boolean. Notification: None FAP Default value: FALSE RMS default value:FALSE RMS Property: FC-UPLINK-TRAFFICSHAPING-ENABLE Management level: Customer

BackhaulAllocation It specifies the uplink backhaul allocation in terms of Kbps, for UL Traffic Shaping. --- RMS Access: READ/WRITE Type: Integer. (Range: 500 to 10000). Notification: None FAP Default value: 2000 RMS Default value:2000 RMS Property: FC-UPLINK-TRAFFICSHAPING-BACKHAULALLOCATION Management level: Customer

MinHSUPARate it specifies the minimum aggregate HSUPA rate in terms of Kbps that shall be supported if UL Traffic Shaping is enabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 1000). Notification: None FAP Default value: 100 RMS Deafult value:100 RMS Property: FC-UPLINK-TRAFFICSHAPING-MINHSUPARAT Management level: Customer



347 UBS-44-57-004

4.27 Support for peer-peer IPC Interface Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_IPC Object name

ChassisModuleNumberOfEntries

The number of entries in the ChassisModule.{i} table. Non-zero indicates that the IPC discovery procedures will take place --- RMS Access: READ Type: Integer. (Range: 0 to 3). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_IPC.ChassisModule Object name MACAddress MACAddress of the specific chassis module

--- RMS Access: READ Type: String. (Length: 0 to 17 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

DeviceId DeviceId of the specific chassis module --- RMS Access: READ Type: String. (Length: 0 to 30 characters). Notification: None FAP Default value: "" RMS Default value:N/A RMS Property:N/A Management level: N/A

RfTxStatus Indicates whether the peer module RF is enabled --- RMS Access: READ Type: Boolean Notification: None FAP Default value: False RMS Default value:N/A Value set at runtime RMS Property:N/A Management level: N/A

OpState Indicates whether this peer module is operationally enabled --- RMS Access: READ Type: Boolean Notification: None FAP Default value: False RMS Default value:N/A Value set at runtime RMS Property:N/A Management level: N/A

Status

Status of this ChassisModule. Enumerations of:- Not Established Connected No Peer Cannot Authenticate Cannot Connect Restart



Object Parameter Description Unknown --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "Unknown" RMS Default value:N/A RMS Property:N/A Management level: N/A

RAT

The RAT to which this module belongs. Enumerations of:- UMTS LTE --- RMS Access: READ Type: Enumeration. Notification: None FAP Default value: "UMTS" RMS Default value:N/A RMS Property:N/A Management level: N/A

IPAddress

IPAddress of the chassis module, represented as a dotted-quad string --- RMS Access: READ Type: String. (Length: 0 to 15 characters). Notification: None FAP Default value: "0.0.0.0" RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_GeoRedundancy Object name

LastUsedSecGWServer

Indication of which SecGW the HNB last connected to. Enumerations of:- SecGWServer1 SecGWServer2 SecGWServer3 Unknown --- RMS Access: READ Type: Enumeration. (Range: 0 to 3). Notification: None FAP Default value: unknown RMS Default value:N/A RMS Property:N/A

RedundancyFailoverTimeout

Timer interval in minutes to determine when the HNB should trigger a failover to the backup security gateway. A value of zero disables the feature --- RMS Access: READ/WRITE Type:Integer. (Range: 0 to 30). Notification: None FAP Default value: 30 RMS Default value:30 RMS Property: FC-RED-FAILOVER-TIMEOUT



349 UBS-44-57-004

4.28 Active SON

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON General SON Management details

SONNeighboursNumberOfEntries

Length of the Other Small Cells list (for information only) --- RMS Access: READ Type: Integer. (Range: 0 to 200). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PeersNumberOfEntries


PeerNeighboursNumberOfEntries


ActiveSONReset

If this is set to TRUE the AP will reset the contents of all the parameters of the Device.X_UBIQUISYS_COM_ZAP.Services.Enterprise.MRT InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.Peers multi object (including persistent class) to their default values and then trigger a reboot. The flag will be automatically cleared as part of the reboot. --- RMS Access: WRITE Type: Boolean. Reboot triggered by SetParameterValue. Notification: None Value set at runtime FAP Default value:FALSE RMS Default value:FALSE RMS Property: FC-ACTIVESON-RESET Management level: N/A




LocalSecurePortLow

Transport mode IPSec local port range low for SON applications --- RMS Access: READ Type: Integer. (Range: 48000 to 65535). Notification: None Value set at runtime FAP Default value:48000 RMS Default value:N/A RMS Property:N/A Management level: N/A

LocalSecurePortHigh

Transport mode IPSec local base high for SON applications --- RMS Access: READ Type: Integer. (Range: 48000 to 65535). Notification: None Value set at runtime FAP Default value:48000 RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.ProvisioningInfo SON provisioning details

EnterpriseID

Unique global enterprise ID. Also used to enable enterprise functionality within the AP. Default value of 0 means enterprise feature set is disabled. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16777215). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 0 RMS Default value:0 RMS Property: FC-ENTERPRISE-ID Management level: Solution

GroupID

Unique group identifier for a collection of APs within an enterprise. Mandatory if enterprise ID is non-zero. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 255). Reboot triggered by SetParameterValue. Notification: None FAP Default value: 0 RMS Default value:0 RMS Property:FC-GROUP-ID Management level: Solution

GroupSiteID

Unique site id within the enterprise. All APs within a specific group must be located on the same site. Mandatory if enterprise ID is non-zero. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 16777215). Reboot triggered by SetParameterValue. Notification: None



351 UBS-44-57-004

Object Parameter Description FAP Default value: 0 RMS Default value:0 RMS Property: FC-SITE-ID Management level: Solution

P2PSONRefreshPeriod

Period (in seconds) for FAP to send periodic SONDataIndications to other FAPs. 0 inhibits these periodic updates. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 86400). Notification: None FAP Default value: 30 RMS Default value:60 RMS Property: FC-P2PSON-REFRESH-PERIOD Management level: System

P2PStaleTimeoutMultiplier

Multiplier of the SONRefreshPeriod to determine the number of seconds after which another FAP shall be considered as stale. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 1000). Notification: None FAP Default value: 8 RMS Default value:4 RMS Property: FC-P2P-STALE-TIMEOUT-MULTIPLIER Management level: System

P2PKeepAliveTimeoutMultiplier

Multiplier of the SONRefreshPeriod to determine the number of seconds after which another FAP shall be considered as offline it has not been heard from. The FAP may initiate a DiscoveryRequest to the suspect FAP to determine if is still online or not. --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 10). Notification: None FAP Default value: 2 RMS Default value:2 RMS Property: FC-P2P-KEEPALIVE-TIMEOUT-MULTIPLIER Management level: System

P2PDiscoveryPort

UDP Discovery port used for Peer-to-peer traffic --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 65536). Notification: None FAP Default value: 30369 RMS Default value:30369 RMS Property: FC-P2P-DISCOVERY-PORT Management level: System

P2PMulticastGroup

Multicast group to be used for Peer-to-peer traffic (the lower 28 bits of the IP address where the top 4 bits are set to 0xE). If set to 0 then broadcast is used instead of multicast. Note that multicast groups 1-255 and 251658240-268435455 are reserved for special use and hence are not recommended to be used for Enterprise peer-to-peer traffic. --- RMS Access: READ/WRITE Type: Integer. (Range: 0 to 268435455). Notification: None FAP Default value: 0 RMS Default value:0



Object Parameter Description RMS Property: FC-P2P-MULTICAST-GROUP Management level: System

P2PTTL

IP Packet Time to Live --- RMS Access: READ/WRITE Type: Integer. (Range: 1 to 255). Notification: None FAP Default value: 5 RMS Default value:1 RMS Property: FC-P2P-TTL Management level: System

EdgeDiscoveryProvisioning

Provisioning for Edge Discovery. CSV list of IPv4 addresses. --- RMS Access: READ/WRITE Type: String. Notification: None FAP Default value: “” RMS Default value: “” RMS Property; FC-EDGE-DISCOVERY-PROVISIONING Management level: Solution or Customer

EnableP2PCommunicationViaSecGW

Enables Provisioning for P2P Connection via Security Gateway. --- RMS Access: READ/WRITE Type: Boolean Notification: None FAP Default value: False RMS Default value:False RMS Property; FC-ENABLE-P2PCOMMUNICATION Management level: Solution or Customer

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.CurrentInUseSettings

The current SON settings, used by EPP to inform other peers of the current configuration.

SONOnline

Indicates if the AP is on-line or not. If an AP is online this means that it active and can support peer to peer communications. If an AP is off line then it will not be used for load balancing or hand out. --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SONOnlineSince

Timestamp when the inter-HNB SON communication link was last (re-)established. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A




353 UBS-44-57-004

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.PeerNeighbours

Master Relationship Table (MRT) containing Tier1 information of non-grid neighbours that other Aps have discovered. One entry in this table for each other neighbour on a given site. Populated by EPP

CellID UMTS Cell ID assigned to the AP --- RMS Access: READ Type: Integer. (Range: 0 to 268435455). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PLMNID PLMN ID assigned to the AP --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

RAT RAT type for this peer Enumerations of "UTRAN", "GSM" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”UTRAN” RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNDL DL UARFCN chosen by the Peer Macro device --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNUL UL UARFCN chosen by the Peer Macro device --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

BCCHARFCN ARFCN for GSM only --- RMS Access: READ Type: Integer. (Range: 0 to 1023). Notification: None Value set at runtime FAP Default value:0




Code PSC for WCDMA (range 0..511), BSIC for GSM (range 0..255) --- RMS Access: READ Type: Integer. (Range: 0 to 511). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CPICHTxPower Primary CPICH Tx power in dBm. Actual values of the power are -10.0 dBm to 50.0 dBm in steps of 0.1 dB. The value of PCPICHTxPower divided by 10 yields the actual value of the power. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 2.2.33. --- RMS Access: READ Type: Integer. (Range: -500 to 500). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LAC Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RAC Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Tier1NeighbourAPList String containing the list of all peer AP's that have detected this non grid neighbour. ["AAAAAAA,-CCC,D"] CellId = AAAAAAA in hexadecimal format. -CCC = decimal representation of measured RSCP for UTRAN OR -CCC represents the decimal



355 UBS-44-57-004

Object Parameter Description representation of the measured RSSI of the neighbour cell D = 0 or 1, 0 = only used by this AP for cell reselection (no decode), 1 = cell is considered suitable for handout by this AP --- RMS Access: READ Type: String. (Length: 0 to 2786 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

X_UBIQUISYS_COM_CellType The classification of the cell, enumerations as follows:- DETECTED_MACRO DERIVED_MACRO INFERRED_MACRO DETECTED_HNB RECIPROCATED_HNB DERIVED_HNB INFERRED_HNB DERIVED_GSM DETECTED_GSM UNKNOWN UNKNOWN_OTHER UNKNOWN_MACRO UE_REPORTED_HNB UE_REPORTED_MACRO Note: RRM sets this parameter when the RRM scan has been performed on this cell. If the cellType is "UNKNOWN", this indicates a cell that is present in this list because it was provisioned by the HMS in the HMSList and was not scanned. RRC uses this information to suppress the check of the cell Ec/No against the X_UBIQUISYS_COM_ThresholdUMTSMacro since HMS provisioned cells are always candidates for relocation --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”UNKNOWN” RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.Peers

Runtime multiobject table, populated by EPP, containing information on peer HNBs. One entry in this table for each HNB in the grid. The table is divided into parameters that are common to the SON functionality, followed by parameters that are specific to applications that make use of the SON functionality. At this time, the applications are Iurh and Active SON Lite (ASL)

VersionTag Incremented each time the HNB changes any other



Object Parameter Description parameters associated with this object. Used by other Aps when receiving the object to determine if there are any changes from the previous version or not. 0 - special value, set at boot and implies that the AP has not yet completed auto-configuration and, therefore has no valid parameters. As soon as the AP completes initial auto-configuration, this value will be incremented to 1 and the AP is then able to share its SON information with its peers. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PLMNID

PLMN ID assigned to the HNB --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

CellID

UMTS Cell ID assigned to the HNB --- RMS Access: READ Type: Integer. (Range: 0 to 268435455). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

DeviceID

Unique Identifier assigned to the HNB, comprising the Manufacturer OUI and Serial Number in the form:- <OUI>-<IMEI> e.g ABCDEF-357539010392542 --- RMS Access: READ Type: String. (Length: 0 to 22 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

FAPID

Unique Identifier assigned to the HNB --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

GroupID

Group ID assigned to the HNB --- RMS Access: READ Type: Integer. (Range: 0 to 255).



357 UBS-44-57-004


OpState

Indicates whether this AP is operationally enabled. Note this may be true even though the HNB is performing a REM scan --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RfTxStatus

Indicates whether the peer HNB RF is enabled --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RemoteLANIPAddress

LAN IP address of the AP derived from the UDP packets received from it --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

LocalSecureAddress

Transport mode IPSec local tunnel endpoint address - this is written by the HNB when the tunnel is established to the peer. The expectation is that this would be the same for all IPSec links, but the parameter is included to be future-proof --- RMS Access: READ Type: String. (Length: 7 to 15 characters). Notification: None Value set at runtime FAP Default value:”0.0.0.0” RMS Default value:N/A RMS Property:N/A Management level: N/A

RemoteSecureAddress

Transport mode IPSec remote tunnel endpoint address - this is written by the HNB when the tunnel is established to the peer. --- RMS Access: READ Type: String. (Length: 7 to 15 characters). Notification: None Value set at runtime FAP Default value:”0.0.0.0” RMS Default value:N/A




SecureTunnelStatus

Status of the secure IPSec tunnel with the peer. Enumerations of "Unknown", "Connected" and "Disconnected" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Unknown” RMS Default value:N/A RMS Property:N/A Management level: N/A

SecurePortLow

This, together with SecurePortHigh defines the ephemeral port range supported by transport mode IPSec. Iurh requires a single port for RNA SCTP, a single port for PS GTP forwarding (PS sessions are multiplexed using the GTP TEID) and multiple ports for CS-RTP forwarding. EPP SON requires a single port. By default we therefore define a range of 32 ports. Note that this param is RO. The port range is determined by the HNB. It is visible in the DB for use by other HNB processes and by the HMS, but may not be provisioned --- RMS Access: READ Type: Integer. (Range: 55296 to 65535). Notification: None Value set at runtime FAP Default value:55296 RMS Default value:N/A RMS Property:N/A Management level: N/A

SecurePortHigh

This, together with SecurePortHigh defines the ephemeral port range supported by transport mode IPSec. Iurh requires a single port for RNA SCTP, a single port for PS GTP forwarding (PS sessions are multiplexed using the GTP TEID) and multiple ports for CS-RTP forwarding. EPP SON requires a single port. By default we therefore define a range of 32 ports. Note that this param is RO. The port range is determined by the HNB. It is visible in the DB for use by other HNB processes and by the HMS, but may not be provisioned --- RMS Access: READ Type: Integer. (Range: 55296 to 65535). Notification: None Value set at runtime FAP Default value:55328 RMS Default value:N/A RMS Property:N/A Management level: N/A

SONTimestamp

Timestamp when the last communication was received from this peer HNB, either "Discovery" or application "Announce" message --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime



359 UBS-44-57-004

Object Parameter Description FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SONOnline

Indicates if the peer HNB has an active SON communications channel. If this field is false then the peer HNB will not be considered by any SON applications --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SONOnlineSince

Timestamp when the inter-HNB SON communication link was last (re-)established. --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

SONStale

SONStale is false if SONOnline is true, If SONOnline becomes false, a guard timer is started (period P2PSONRefreshPeriod X P2PStaleTimeoutMultiplier) and SONStale is set true upon this timer expiry If a HNB is stale then it is considered to be out of service and so its RF profile can be used by other HNBs --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ProvisionedSeGWServer

Provisioned SeGW Server IP Address --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

SeGWServerIPAddressInUse

SeGW Server IP Address already in use --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A




ProvisionedHMSServer

Provisioned HMS Server IP Address --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

HMSIPAddressInUse

HMS Server IP Address already in use --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

ProvisionedHNBGWServer

Provisioned HNBGW Server IP Address --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

HNBGWIPAddressInUse

HNBGW Server IP Address already in use --- RMS Access: READ Type: String. (Length: 0 to 64 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNDL

DL UARFCN chosen by the Peer HNB --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

UARFCNUL

UL UARFCN chosen by the Peer HNB --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PrimaryScramblingCodeInUse

Primary Scrambling code chosen by the Peer HNB --- RMS Access: READ Type: Integer. (Range: 0 to 511).



361 UBS-44-57-004


PrimaryScramblingCodeInUseOwnedSince

Timestamp (UTC Date and Time) when the AP made the SelectedPrimaryScramblingCode selection. Value = 0 represents: no selection exercised so far. Value = 1 represents: only single PSC was provisioned (i.e. selection was enforced) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967295). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LAC

Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

RAC

Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

CPICHTxPower

Primary CPICH Tx power in dBm. Actual values of the power are -10.0 dBm to 50.0 dBm in steps of 0.1 dB. The value of PCPICHTxPower divided by 10 yields the actual value of the power. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 2.2.33. --- RMS Access: READ Type: Integer. (Range: -500 to 500). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A




MVTRange

MIB value tag range chosen by the AP. MVT_ALL MVT_1_2 MVT_3_4 MVT_5_6 MVT_7_8 MVT_1_4 MVT_5_8 --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”MVT_ALL” RMS Default value:N/A RMS Property:N/A Management level: N/A

Tier1NeighbourAPList

String containing the list of all peer HNBs that this peer has detected as a tier1 neighbour. ["AAAAAAA,-CCC"] CellId = AAAAAAA in hexadecimal format. -CCC = decimal representation of measured RSCP for UTRAN OR -CCC represents the decimal representation of the measured RSSI of the neighbour cell --- RMS Access: READ Type: String. (Length: 0 to 2786 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

IurhAvailable

Indicates whether this peer HNB has Iurh capability,based on the reception of an Iurh SON Announce --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

ASLAvailable

Indicates whether this peer HNB has Active SON Lite capability,based on the reception of an ASL Announce --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_SON.SONNeighbours

Contains information on neighbours measured by RRM. This maybe a superset of the data contained within neighbourListInUse



363 UBS-44-57-004


EntryIsHNB

Indicates whether this Peer is an AP --- RMS Access: READ Type: Boolean. Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

CellID

UMTS Cell ID assigned to the AP - uniquie identifier --- RMS Access: READ Type: Integer. (Range: 0 to 268435455). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

MeasuredRSCP

The absolute measured RSCP --- RMS Access: READ Type: Integer. (Range: -120 to -50). Notification: None Value set at runtime FAP Default value:-100 RMS Default value:N/A RMS Property value:N/A Management level: N/A

CPICHTxPower

Primary CPICH Tx power in dBm. Actual values of the power are -10.0 dBm to 50.0 dBm in steps of 0.1 dB. The value of PCPICHTxPower divided by 10 yields the actual value of the power. 3GPP-TS.32.642 Section 6.3.11, 3GPPTS.25.433 Section 2.2.33. -101 is considered to be an invalid value --- RMS Access: READ Type: Integer. (Range: -500 to 500). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

PLMNID

PLMN ID assigned to the AP --- RMS Access: READ Type: String. (Length: 0 to 6 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property value:N/A Management level: N/A

RAT

RAT type for this peer Enumerations of "UTRAN", "GSM" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”UTRAN”



Object Parameter Description RMS Default value:N/A RMS Property value:N/A Management level: N/A

LAC

Location Area Code (LAC). The concatenation of PLMN ID (MCC+MNC) and LAC uniquely identifies the Location Area ID (LAI). 3GPP-TS.23.003 Section 4.1 3GPP-TS.25.413 Section 9.2.3.6 --- RMS Access: READ Type: Integer. (Range: 0 to 65535). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

RAC

Routing Area Code (RAC). The concatenation of PLMN ID (MCC+MNC), LAC, and RAC uniquely identifies the Routing Area ID (RAI). 3GPP-TS.23.003 Section 4.2 3GPP-TS.25.413 Section 9.2.3.7 --- RMS Access: READ Type: Integer. (Range: 0 to 255). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

UARFCNDL

DL UARFCN chosen by the Peer Macro device --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

UARFCNUL

UL UARFCN chosen by the Peer Macro device --- RMS Access: READ Type: Integer. (Range: 0 to 16383). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

BCCHARFCN

ARFCN for GSM only --- RMS Access: READ Type: Integer. (Range: 0 to 1023). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

Code

PSC for WCDMA (range 0..511), BSIC for GSM (range 0..255) ---



365 UBS-44-57-004

Object Parameter Description RMS Access: READ Type: Integer. (Range: 0 to 511). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property value:N/A Management level: N/A

RSSI

Received signal level in dBm of the BCCH carrier for GSM only --- RMS Access: READ Type: Integer. (Range: -110 to 48). Notification: None Value set at runtime FAP Default value:-110 RMS Default value:N/A RMS Property value:N/A Management level: N/A


The classification of the cell, enumerations as follows:- DETECTED_MACRO DERIVED_MACRO INFERRED_MACRO DETECTED_HNB RECIPROCATED_HNB DERIVED_HNB INFERRED_HNB DERIVED_GSM DETECTED_GSM UNKNOWN UNKNOWN_OTHER UNKNOWN_MACRO UE_REPORTED_HNB UE_REPORTED_MACRO Note: RRM sets this parameter when the RRM scan has been performed on this cell. If the cellType is "UNKNOWN", this indicates a cell that is present in this list because it was provisioned by the HMS in the HMSList and was not scanned. RRC uses this information to suppress the check of the cell Ec/No against the X_UBIQUISYS_COM_ ThresholdUMTSMacro since HMS provisioned cells are always candidates for relocation --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”UNKNOWN” RMS Default value:N/A RMS Property value:N/A Management level: N/A



4.29 Iurh Grid Override

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Iurh.GridOverride Iurh params to support gateway alignment

SeGWFQDN

Fully Qualified Domain Name of the current Security Gateway this FAP has negotiated for use by the grid. --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

SeGWIPAddress

IP Address that is in use associated with the seGWFQDN (32bit representation of IPv4 address) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

HNBGWFQDN

Fully Qualified Domain Name of the current HNB Gateway this FAP has negotiated for use by the grid --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

HNBGWIPAddress

IP Address that is in use associated with the HNBGWFQDN (32bit representation of IPv4 address) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

HMSFQDN

Fully Qualified Domain Name of the HMS that this FAP is using from the Grid --- RMS Access: READ Type: String. (Length: 0 to 255 characters). Notification: None Value set at runtime FAP Default value:”” RMS Default value:N/A RMS Property:N/A Management level: N/A

HMSIPAddress

IP address that is in use associated with the HMSFQDN (32bit representation of IPv4 address)



367 UBS-44-57-004

Object Parameter Description --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PrevSeGWIPAddress

The last IP address in use for the Security Gateway used by this FAP (value retained over restart of FAP) (32bit representation of IPv4 address) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A Management level: N/A

PrevHNBGWIPAddress

The last IP address in use for the HNB Gateway used by this FAP (value retained over restart of FAP) (32bit representation of IPv4 address) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None FAP Default value: 0 RMS Default value:N/A RMS Property:N/A

PrevHMSIPAddress

The last IP address in use for the HMS used by this FAP (value retained over restart of FAP) (32bit representation of IPv4 address) --- RMS Access: READ Type: Integer. (Range: 0 to 4294967294). Notification: None FAP Default value: 0 Management level: N/A

Object Parameter Description InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Iurh Iurh Cells

LinkTableNumberOfEntries

umber of entries in the LinkTable multiobject (for information only) --- RMS Access: READ Type: Integer. (Range: 0 to 50). Notification: None Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

InternetGatewayDevice.Services.FAPService.1.X_UBIQUISYS_COM_Iurh.LinkTable Object name

CellID

UMTS Cell ID assigned to the AP --- RMS Access: READ Type: Integer. (Range: 0 to 268435455). Notification: None



Value set at runtime FAP Default value:0 RMS Default value:N/A RMS Property:N/A Management level: N/A

LinkStatus

Indicates the Iurh Link status - "Connected" - "Disconnected" -"FailedToConnect" --- RMS Access: READ Type: Enumeration. Notification: None Value set at runtime FAP Default value:”Disconnected” RMS Default value:N/A RMS Property:N/A Management level: N/A

▀ Provisioning Procedures


369 UBS-44-57-004

5 Provisioning Procedures

5.1 HMS Address for: IPSec or TLS/SSL The HNB always initiates OAM procedures with the HMS at the address configured with in the TR-098 parameter: InternetGatewayDevice.ManagementServer.URL. The parameter may contain an IP address or FQDN/URL.

The Standards allows secure connection to the HMS either using TLS/SSL or via a SeGW through an established IPSec tunnel. The connection method choice depends on the address type, a URL beginning ‘https://’ implies TLS/SSL, otherwise a FQDN or IP address implies IPSec connection.

If the DNS query returns more than one IP addresses for an FQDN/URL address, the HNB tries the different addresses, if the HMS does not respond.

An HMS can direct a managed HNB to a different HMS. This is done by writing a new address into the parameter .ManagementServer.URL. This parameter forces the HNB to reboot and contact the new HMS. It should be noted that this method is used for moving a HNB from an initial HMS (which provides common parameters to all HNBs) to a serving HMS which can provides the full set of configuration parameter for the HNB to provide service; however, note the HNB does not differentiate the functionality of serving or initial HMSs. The next section provides further details of the configuration procedure.

5.2 Procedures Leading to HNB Providing Service In order to start providing WCDMA services, an HNB needs to successfully complete four initialisation stages:

• The HNB is activated by Cisco’s CloudBase System (see Section 5.2.2)

• The HNB is provisioned by the initial HMS (see Section 5.2.3)

• The HNB is fully provisioned by a serving HMS (see Section 5.2.4)

• The HNB registers with a HNB-GW (see Section 5.2.5)

The process is summarised in Figure 3.



HNB iSeGW

1. Initial provisioning

iHMS SeGW HNB-GW

Database partly provisioned

HMS

2. Full provisioning (or re-provisioning after reboot)

3. HNB Registration

Database fully provisioned

Cell Enabled

CloudBase

0. Activation

Database not provisioned

Figure 3: Activation, Initialisation and Registration high level view

The HMS uses the initial and full provisioning procedures in order to acquire information and set given parameters such that the HNB is provided with values for the following mandatory parameters:

Object Mandatory parameter Comments InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.Gateway.

SecGWServer1 See section 4.7.2

FAPGWServer1 See section 4.7.2

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.

CELLID See section 4.9.2

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.

UARFCNDL See Section 4.9.13.9

PrimaryScramblingCode See Section 4.9.13.9

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.

LACRAC See Section 4.9.1

PLMNID See Section 4.9.1

Table 111: Mandatory parameters



371 UBS-44-57-004

Unless the parameter listed above is set differently from default, the HNB will not attempt registration to the HNB-GW. The HNB will hang until these parameters are set.

5.2.1.1 Typical Duration of Start-Up Times

Start-up time duration is non-deterministic, mostly affected by duration of the NWL scan of diverse macro environment conditions and configuration of various parameters under operator control.

Start-up duration also depends if the procedure is a first activation (or Factory Recovery) boot or a normal cold/warm reboot.

Typical start-up duration for the HNB to:

• Factory recovery (depends on backhaul, software and certificates) 150–270s

• The OS start-up and AP bootloader (ZAP INIT) 15-20s

• The Core AP application start, including NETC (DHCP + DNS + NTP queries) 15-20s

• Upper layer applications, including:

o IPsec application and IPsec tunnel connection setup 05-10s

o TR69 application and HMS connectivity 15-30s

o SW download/upgrade 30-60s

o DLMM (DownLink Monitor Mode), or full scan of the environment

WCDMA: Make RSSI measurement on all carrier in band: 10s

WCDMA: Detect all Primary Scrambling Codes on Carrier: 5s

WCDMA: Decode all SIBs on single Primary Scrambling Code: 10s

GSM: Make RSSI measurement on all carriers in band: 10s

GSM: Detect FCCH/SCH on carrier: 1s

GSM: Decode all SIs on carrier: 10s

5.2.1.2 Administrative and Operational States

The HNB offers 3 parameters which are used for administration of the various states of the HNB (These parameters are within the object: InternetGatewayDevice.Services.FAPService.1.FAPControl.):

• AdminState: set by the HMS

• OpState: set by the HNB

• RFTxStatus: set by the HNB following registration with HNB-GW

The AdminState always defaults to “locked” upon each boot and must be explicitly unlocked by the HMS during each initialisation sequence.

The HNB will attempt to register to the HNB-GW only once the AdminState is unlocked and OpState is enabled.

See the following summary of states:

AdminState OpState RFTxStatus HNB-GW Registration Typical condition



AdminState OpState RFTxStatus HNB-GW Registration Typical condition

Locked Disabled False Not registered Initialisation or provisioning incomplete

Locked Enabled False Not registered Device provisioned but the HMS has taken the HNB out of service

Unlocked Disabled False Not registered Provisioning incomplete. The HMS considers HNB to be configured but HNB awaits further configuration.

Unlocked Enabled False Not registered

Device provisioned and allowed for service. HNB attempts registration to HNB-GW or setup in progress (e.g. REM scan)

Unlocked Enabled True Registered

Device provisioned, allowed for service and registered with HNB-GW. Cell setup = IN SERVICE The HNB is providing WCDMA service.

5.2.2 CloudBase System: Activation Cisco femtocells & modules for Integrated Access Device (IADs) are manufactured as generic products (in terms of software/data). As femtocells are shipped from the production site, the hardware information and calibration data is loaded onto the CloudBase System.

At first boot-up the device needs to contact the CloudBase System and acquire the Activation Profile, which includes:

• Factory default software load (as specified by the Operator)

• A set of Operator defined parameters, including the address of the initial SeGW and HMS

• Calibration data unique to each femtocell

• Initialisation of the database (femtocell becomes un-provisioned)

Following acquisition of the Activation Profile, the HNB connects to the initial HMS, via the SeGW.

Note that Cisco’s CloudBase System and its procedures are not relevant in this document and are presented on other Cisco’s’ documents.

5.2.3 Initial Provisioning Initial provisioning assumes that the database has been initialised, during activation by the Cisco’s CloudBase System, caused by:

• First power up

• Factory recovery initiated by the OAM

• Auto-recovery from SW fault leading to 3 reboots in 5 minutes

• Reset button (held pressed for 5 sec) by user intervention

When in this state, the HNB contacts the HMS defined by the operator in the activation setting acquired from the CloudBase System.

The HMS needs to configures an initial ‘core set’ of database parameters that are needed for the unit to proceed to be fully configured. The following Figure shows a typical transaction.



373 UBS-44-57-004

HNB SeGW

3. Establish Secure Connection

1. Database not provisioned

HMS Operator DNS

public DNS

6. Reboot and perform REM scan

8. opt: Release Secure Connection

2. Opt: DNS resolve iSeGW address

4. DNS resolve iHMS address

DB part provisioned

5a. Inform (BOOTSTRAP, BOOT, VALUE CHANGE)

7a. INFORM(REM Status); GET(REM Results)

5e. Provision REM scanning parameters

7b. Provision sHMS and sSeGW / HNB-GW sets

5b. opt: Perform SW Download

5c. opt. Create objects

5d. opt: Change Attributes

Figure 4: Initial HMS contact using IPSec, normal flow

1. The HNB database is considered not-provisioned until a number of parameters, including serving SeGW/HMS and a number of RF parameters are configured (these are marked as requiring provisioning in the data model). The .FAPControl.AdminState defaults to ‘locked’. The HNB has been provided with the URL or FQDN of an initial SeGW and the URL of the HMS by Cisco’s CloudBase System.

2. If the SeGW has been configured by FQDN, the HNB performs a DNS lookup to a public DNS server to resolve the FQDN to a list of one or more IP addresses. This step is not necessary if the SeGW has been configured directly as an IP address.

3. The HNB establishes a secure connection to the SeGW using IPSec. This procedure modifies the HNB destination for DNS queries to be made towards the Operators’ private DNS server.

4. If configured by URL or FQDN, the HNB resolves a list of one or more IP addresses for the HMS from the operator’s private DNS server.

5a. The HNB opens a TCP connection to the HMS and sends an Inform message to the HMS. This contains the following parameters/objects:

• Device Id: manufacturer, OUI, product class, serial number

• Event Codes: “0 BOOTSTRAP, 1 BOOT, 4 VALUE CHANGE”

• Parameter list:

o InternetGatewayDevice.DeviceSummary



o InternetGatewayDevice.DeviceInfo.HardwareVersion

o InternetGatewayDevice.DeviceInfo.SoftwareVersion

o InternetGatewayDevice.DeviceInfo.SpecVersion

o InternetGatewayDevice.DeviceInfo.ProvisioningCode

o InternetGatewayDevice.ManagementServer.ConnectionRequestURL

o InternetGatewayDevice.ManagementServer.ParameterKey

o InternetGatewayDevice.Services.FAPService.1.FAPControl.OpState

o InternetGatewayDevice.Services.FAPService.1.FAPControl.RFTxStatus

o InternetGatewayDevice.Services.FAPService.1.Transport.Security.Secret.1.UICCCardID

o InternetGatewayDevice.Services.FAPService.1.Transport.Tunnel.IKESA.1.IPAddress

o InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1.ExternalIPAddress

o InternetGatewayDevice.WANDevice.1.WANConnectionDevice.1.WANIPConnection.1.MACAddress

5b. The HMS may initiate a SW Download rather than continuing the initialisation procedure. If this occurs the HNB shall reboot upon download of the new software (and restart initial provisioning from point 1)

5c. The HMS may create and extend object instances as required by the data model. For example the HMS should ensure one .FAPService.{1}.Transport.Security.CryptoProfile object instance exists and is fully populated during the initial provisioning phase.

5d. The HMS should modify the notification attribute of parameters using the appropriate TR-069 RPC. The parameters will depend on the Integrator OAM strategy.

For example, the parameter InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.LACInUse is set to notification active, such that the HNB can be recognised by the HNB-GW.

5e. The HMS can configure parameters depending on service requirements; typical parameters are listed in section 5.2.3.1.1. The TCP connection may be closed by the HMS once this transaction completes.

6. Configuration of REM scan parameters will trigger the HNB to reboot and perform a REM scan. Possible neighbouring cells are discovered

7a. Upon REM scan completion, if any REM parameters have the Active notification attribute, the HNB opens a new TCP connection to the HMS and sends an Inform message using the event code ‘4 VALUE CHANGE’ and which includes those REM parameters which are set to Active notification. This notification can be used by the HMS as a trigger for it to retrieve (using TR-069 call: “GetParameterValue”) the REM results.

7b. The HMS may now verify the location of the HNB (the procedure is outside the scope of this document and is decided by the HMS vendor). Following this, the HMS may provide the HNB with different addresses for more localised serving HMS, SeGW and HNB-GW to use as future OAM and Iuh transactions. The initial SeGW and HMS (i.e. those from the factory/operator provisioned data) are not used again unless the configured HMS becomes unavailable (eg. if the HNB performs factory recovery for some reason which clears its database settings).

8. The HMS may release the connection. The HNB will reboot if a different SeGW/HMS pair were configured by the HMS.

The HNB has a partially configured database, it has enough information to attempt to connect to the configured serving HMS. The HNB selects the first ‘GW pair’ to contact (SeGW HNB-GW) and compares the SeGW FQDN/IP address to the one it is currently connected to. If this check shows the serving SeGW to be the same as the initial SeGW then the HNB shall maintain the IPSec tunnel for the following transaction to the sHMS. Otherwise, the HNB releases the IPSec tunnel.

5.2.3.1.1 Parameters to be configured by the HMS

The HMS can configure parameters , the list is not nor complete nor a mandatory list, as it will depend on architecture and how the HNB is employed:



375 UBS-44-57-004

Object Name Parameters

InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.Gateway.

SecGWServer1 and FAPGWServer1

SecGWServer2

FAPGWPort

InternetGatewayDevice.Services.FAPService.1.FAPControl.UMTS.SelfConfig.

UARFCNSelfConfigEnable

LACRACURASelfConfigEnable

InternetGatewayDevice.Services.FAPService.1.REM.WCDMAFDD.

ScanOnBoot

ScanPeriodically

UARFCNDLList

REMBandList

ScanTimeout

InternetGatewayDevice.Services.FAPService.1.REM.GSM.

ScanOnBoot

ScanPeriodically

ARFCNList

REMBandList

ScanTimeout

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.FDDFAP.RF.

MaxFAPTxPower

MaxULTxPower

UARFCNDL

PrimaryScramblingCode

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.CN.



Object Name Parameters

EquivPLMNID

LACRAC

SAC

PLMNID

X_UBIQUISYS_COM_LAIRAISwapEnable

X_UBIQUISYS_COM_IuPLMNID

X_UBIQUISYS_COM_IuLAC

X_UBIQUISYS_COM_IuRAC

InternetGatewayDevice.Services.FAPService.1.CellConfig.UMTS.RAN.

URAList

CellID

InternetGatewayDevice.ManagementServer.

URL

InternetGatewayDevice.Services.FAPService.1.Transport.Security.CryptoProfile.1.

Enable AuthMethod IKERekeyLifetime IPsecRekeyLifetimeTime

Table 112: Minimum parameter set required from HMS

5.2.4 Full Provisioning This procedure described in this section is invoked either:

• Following the initial provisioning procedure for a factory fresh or factory recovered HNB (as discussed in Section 5.2.3)

• Following a power cycle

• If the parameter InternetGatewayDevice.ManagementServer.URL is updated by an HMS.

This is the most common start-up sequence as a HNB should rarely revert back to an un-provisioned state which would require initial provisioning.

During full provisioning, the HNB expects to be provided with working parameters for it to register and provide service. The HMS providing the full configuration may be the same as the HMS used for the initial provisioning.

Once the mandatory database parameters (listed in section 5.2) provisioned, the HNB sets the OpState to enabled and expect that the HMS sets the AdminState to true (i.e. unlocked).



377 UBS-44-57-004

HNB SeGW

4. Opt: Establish Secure Connection

1. Database partly provisioned

HMS operator DNS

public DNS

11. Release TCP Connection

7. Opt: Reboot

3. Opt: DNS resolve SeGW address

5. DNS resolve sHMS address

DB fully provisioned

8a. INFORM (opt: RF selections, opt: REM Status)

6a. INFORM (REM Status); GET (REM Results)

6b. Main HNB database provisioning

2. opt: Perform REM scan

8b. Opt: provision HNB NeighbourList

9. Select Neighbours In Use

10. AdminState is ‘unlocked’ if HNB allowed to register

8. opt

Figure 5: Full configuration

1. At this stage of provisioning the database of the HNB is considered part provisioned:

• SeGW and HNB-GW where configured.

• Some RF configuration was carried out, but it may need to be updated ta take into consideration the actual location and use of the HNB.

• Other static parameters may be in an unknown state. They have either default values (if this is the first connection to a HMS) or may have been set by other HMSs.

The aim of this procedure is to fully provision all necessary parameters into a known state.

2. If the procedure is being run directly after reboot or power up, the HNB shall perform an initial REM scan using the parameters configured by the last HMS.



3. If the SeGW has been configured by FQDN, the HNB performs a DNS lookup to a public DNS server to resolve the FQDN to a list of one or more IP addresses. This step is not necessary if the SeGW has been configured directly as an IP address. Also, this step is not performed if an existing IPSec tunnel is to be reused.

4. HNB establishes a new IPSec tunnel to the SeGW only if it determines that the address of the SeGW was modified by the HMS; otherwise, the HNB will use the same IPSec tunnel.

5. If configured by URL or FQDN, the HNB resolves a list of one or more IP addresses for the HMS from the Operators’ private DNS server.

6a – 6b. The HNB opens a TCP connection to the HMS and send an Inform message with Event Code:

• If the HMS address is the same as the last HMS contacted, the HNB uses ‘1 BOOT’

• Otherwise, if the HNB is contacting a new HMS, ‘0 BOOTSTRAP’ is used.

The Inform Message also includes the REM status parameters (ScanStatus and/or LastScanTime) if a new REM Scan was performed (step 2) and if these status parameters are set with Active notification. If the REM status is included then the HMS could use this as a trigger to retrieve the latest REM results from the HNB.

The HMS can configure the rest of the database parameters, for example:

• Access control ‘whitelist’

• Fault Management, eg. notification levels (.FAPService.{i}.FaultMgmt)

• Parameters controlling Performance Management (.FAPService.{i}.PerfMgmt)

• Licences

• Enabling/Disabling Local GUI

Note that the exact combination and sequence of TR-069 RPC methods used in this provisioning is determined by HMS implementation, Operator’s requirements and femtocell expected usage.

Optionally, if HNB has been provisioned to use its self-configuration capabilities (self-selection of UARFCN, Primary Scrambling Code and Neighbour List) and the UARFCNDL list has been provisioned with only one UARFCN, then the HMS may also provision the NeighbourList (WCDMA and/or GSM lists)

The HMS should also set the AdminState to ‘unlocked’; thus allowing the HNB to register with the HNB-GW.

7. Optionally, if RF parameters (UARFCN or PrimayScramblingCode) were updated during step 6b, the HNB would reboot.

8a. Optionally, if HNB has been provisioned to self-configure its RF parameters (selection of Primary Scrambling Code and UARFCN), then the HNB sends an Inform message with Event Code ‘VALUE CHANGE’ to report the RF parameters selected. Note that selection is restricted within the ranges defined by the HMS.

8b. The HMS should be able to provision the list of neighbour cells as soon as the UARFCN selected by the HNB is known. If the UARFCN was selected from a list, the HMS should wait for the UARFCNDLInUse to be updated by the HNB before it can modify the NeighbourList.

9. Once the NeighborList has been provisioned, the HNB shall create the object NeighborListInUse object using the configured NeighborList and the results of the REM scan as inputs.

10. If the HMS deems the HNB is authorised for service (eg. after relevant owner subscription checks and location checks) and the parameter AdminState is ‘unlocked’, the HNB can proceed with registration.

11. The HNB shall close the TCP connection. The HNB uses the same IPSec tunnel for subsequent communication with the HNB-GW.

5.2.4.1 Re-provisioning Following HNB Reboot

This procedure is invoked each subsequent reboot following a full configuration (described in section 5.2.4).



379 UBS-44-57-004

HNB SeGW

4. Establish Secure Connection

1. Database fully provisioned

HMS operator DNS

public DNS

9. Release TCP Connection

3. Opt: DNS resolve sSeGW address

5. DNS resolve sHMS address

6a. Inform (BOOT, REM Results)

2. Perform REM scan

7. Select Neighbours In Use

8. Provision HNB Admin-State to ‘unlocked’

6b. Carryout any queued provisioning requests

Figure 6: Serving HMS contact after reboot using IPSec, normal flow

1. The HNB database is considered fully provisioned if:

• Serving SeGW and HNB-GW are configured

• The RF parameters necessary to the HNB are configured.

2. The HNB perform a REM scan using the RF parameters previously provisioning.

3. If the SeGW has been configured with a FQDN, the HNB performs a DNS lookup to a public DNS server to resolve to IP addresses.

4. The HNB establishes an IPSec tunnel to the SeGW.

5. The HNB resolves the FQDN of the HMS to IP addresses via the operator’s private DNS server.

6a – 6b. The HNB opens a TCP connection to the HMS and sends and Inform Message with Event Code: ‘1 BOOT’. Together with the result of the REM scan

The HMS should verify that the HNB has not changed its location.

• If the HNB has changed location then the HMS could carry out a TR-069 factory reset. This will have the effect of clearing the HNB database and cause it to reconnect to the initial HMS for provisioning.

• If the HNB has not changed location the HMS can complete any queued provisioning requests for the HNB

7. The HMS provides the current NeighborList to the HNB. The HNB can configure the NeighborListInUse object with this and the updated REM measurements.

8. The HMS allows the HNB to proceed with HNB Registration by setting the AdminState to ‘unlocked’.

9. The HNB shall close the TCP connection. The HNB uses the same IPSec tunnel for subsequent communication with the HNB-GW.



5.2.5 HNB Registration

HNB

1b. Opt: Establish Secure Connection

SeGW operator DNS

2. Opt: DNS resolve HNB-GW address

HNB-GW

4. HNBAP: HNB Register Request

5. HNBAP: HNB Register Accept

1a. Opt: DNS resolve sSeGW dd

public DNS

3. SCTP establishment

De-registered

Registered

6b. Inform (VALUE CHANGE, RF Status)

HMS

6a. Enable Cell

Figure 7: HNB Registration, normal flow

1. If the HMS connection was made via IPSec (as in 5.2.4), the HNB would use the IPSec tunnel already established; otherwise, the HNB runs through steps 1a and 1b (DNS discover and IPSec establishment).

2. The HNB uses SeGW/HNB-GWs in pair, as configured by the HMS. Only if these are configured by using FQDN addressing, the HNB resolves them from the operators’ DNS server.

3. The HNB initiates a SCTP connection to the HNB-GW. As defined by IANA:

• HNBAP protocol messages shall be marked with PPI value 20

• RUA protocol messages shall be marked with PPI value 19.

4. The HNB sends a HNB Register Request to the HNB-GW over the HNBAP SCTP stream. The message contains the following:

• HNB Identity (Device ID)

• HNB Location Information:

o Macro Coverage Indicator: a single macro cell identifier (PLMN, LAC, RAC, Cell-ID) for either a UTRAN or GERAN cell. The HNB Location Information is an optional Information Element (IE) and is not included when the HNB is unable to detect any neighbouring macro cells. When included it indicates the strongest detected neighbour cell (measured by RSCP for UTRAN or RSSI for GERAN).

o Geo-Location: is either determined by GPS reading (if supported) or the latitude, longitude, altitude and direction information is provisioned from the HMS. Whenever available, the HNB includes the content of the Geo-Location within the Location Information IE. If both GPS reading and HMS provisioned location are present, the HNB defaults to the GPS reading. If neither location type is available, the Geo-Location is omitted from the HNB Location Information IE.

o It should be noted that the HNB does not include the optional “Public IP Address” IE in the HNB Location Information.



381 UBS-44-57-004

• PLMN-ID (as provisioned from sHMS; to be broadcast in SIBs)

• Cell-ID (provisioned from HMS; to be broadcast in SIBs)

• LAC (as selected by HNB from LACRAC range provisioned by HMS; to be broadcast in SIBs)

• RAC (as selected by HNB from LACRAC range provisioned by HMS; to be broadcast in SIBs)

• SAC (as provisioned from HMS)

5. Provided that the HNB is allowed access, the HNB-GW should return a HNB Register Accept. The message contains an RNC-ID IE which shall be stored in the database for use in SIBs, URNTI assignment, etc. If present, the Mux Port ID is used to configure the end-point of RTP Multiplexing of UL CS traffic to the specified port.

6a – 6b. The HNB proceeds to configure the cell and enables RF transmission. The RFTxStatus database parameter is updated to reflect this and the serving HMS is also informed of the change.

5.2.5.1 HNB Registration Reject The HNB-GW may reject the registration attempt with a HNBAP: HNB REGISTER REJECT. This message contains a Cause value and optionally a Backoff timer IE (presence of which is dependent on the Cause value). The Cause values supported by the HNB are the following:

• RNL: Overload: The HNB shall release the SCTP association and start a backoff timeout. If the optional Backoff Timer IE is present in the reject message the HNB shall use its value for the timeout period. Otherwise the HNB shall use a default timeout period of 60 seconds. When the timeout expires the HNB shall establish a new SCTP association and retry the HNB Registration procedure. If the HNB is rejected 3 times in a row with cause Overload then it shall release the IPSec tunnel, select a different SeGW / HNB-GW pair and attempt HNB Registration to the new GW pair. If all attempts fail to all available GW pairs then the HNB shall backoff for a period of 25 minutes plus a 0 to 10 minute random offset.

• Misc: Transport Resource Unavailable: the HNB shall release the SCTP connection with the serving HNB-GW as well as the IPSec tunnel with the serving SeGW. HNB shall then establish an IPSec tunnel with the next SeGW of the pool and connect to the next serving HMS in order to retrieve the IP address of the next serving HNB-GW to register with.

• RNL: Unauthorised HNB

• Misc: Unspecified

5.2.6 HNB Deregistration 5.2.6.1 HNB-GW Initiated HNB

Deregistration



HNB

5. Release Secure Connection

SeGW HNB-GW

1. HNBAP: HNB Deregister

4. Close SCTP

UE(s)

Optional

3. Cell shutdown

2a. Release UE connections

Registered

De-registered

6. Attempt new initialisation and registration

HMS

Figure 8: HNB-GW initiated Deregistration

1. The HNB-GW sends a HNBAP HNB Deregister message to a registered HNB. 2. If the HNB has any UEs registered with the HNB-GW, the HNB shall locally release any currently active radio

resources and internal resources for these UEs. 3. The HNB is now considered Deregistered; it therefore cannot provide service for UEs. 4. The HNB releases all SCTP streams and the overall SCTP association to the HNB-GW. 5. The HNB closes the IPSec tunnel to the SeGW. 6. The HNB shall attempt a new initialisation and registration procedure.

5.2.6.2 HNB Initiated Deregistration 5.2.6.2.1 HNB Deregistration due to internal event



383 UBS-44-57-004

HNB


SeGW HMS


5. close SCTP

UE(s)

2b. HNBAP: UE Deregister

Optional

3. Shutdown Cell


Registered

De-registered

7. Opt: attempt new initialisation and registration

HNB-GW

1. Internal event trigger

Figure 9, HNB initiated Deregistration, triggered by internal event

1. Events which may trigger deregistration are: • USIM status change; (U)SIM that was present is removed or unreadable • Temperature status change; the HNB temperature increases above a critical threshold • IP timing status change; the detected timing error increases above a critical threshold • Cell status change; the cell has been shut-down, either for operational reasons (eg. to perform a new

REM scan) or due to unexpected modem fault. • Change of:

o LACInUse o RACInUse o PLMN-ID

2. The HNB releases any currently active radio resources and send a HNBAP UE Deregister message to the

HNB-GW for each released UE. 3. The cell is disabled to prevent any new UE initiated procedures. 4. The HNB sends a HNBAP HNB Deregister message to the HNB-GW. 5. The HNB releases all SCTP streams and the overall SCTP association to the HNB-GW. 6. The HNB closes the IPSec tunnel to the SeGW. 7. The follow up action for the HNB is determined by the triggering event in step 1:

• USIM status change; the LED pattern ‘No SIM Card Detected’ shall be invoked, the HNB shall poll the (U)SIM status and only perform the full installation procedure(described in sections 5.2.4 or 5.2.4.1) upon the (U)SIM becoming accessible again.

• Temperature status change; the LED pattern ‘Over Temperature’ is invoked; the HNB polls its temperature and perform a new initialisation upon it dropping below a given threshold.

• IP timing status change; the LED pattern ‘Temporarily Out of Service’ is invoked, the HNB maintains IP timing and only perform initialisation upon the timing error dropping below the threshold.

• Cell status change; initialisation is attempted once the HNB is ready to be re-enabled (e.g. the modem has been reloaded for a modem failure event, or after a REM scan has completed).

5.2.6.2.2 HNB Deregistration triggered by HMS



HNB


SeGW


5. close SCTP

UE(s)

2b. HNBAP: UE Deregister

opt

3. Shutdown Cell


Registered

De-registered

7. Attempt new initialisation and registration

HNB-GW

1b. HMS sets param(s) triggering cell shutdown

1a. HTTP GPV “ConnectionRequestURL”

1c. HMS sends REBOOT to HNB

HMS

Figure 10, HNB initiated Deregistration, triggered by HMS

HMS sets HNB to admin state Locked HMS triggers reboot while HNB Registered with HNB-GW 1. The HMS contacts the HNB (1a) and updates parameters requiring reboot (1b) or the HMS triggers a TR-06

REBOOT method (1c). 2. If the HNB has any UEs registered with the HNB-GW, the HNB releases any currently active radio resources

and send a HNBAP UE Deregister message to the HNB-GW for each released UE. 3. The cell is disabled to prevent any new UE initiated procedures. 4. The HNB sends a HNBAP HNB Deregister message to the HNB-GW. 5. The HNB releases all SCTP streams and the overall SCTP association to the HNB-GW. 6. The HNB closes the IPSec tunnel to the SeGW. 7. The follow up action for the HNB is determined by the triggering event in step 1:

o administrative state to ‘Locked’; the LED pattern ‘Not Provisioned’ shall be invoked, the HNB shall wait pending further updates from HMS and only perform initialisation upon the administrative state being set back to ‘Unlocked’.

o parameters changed with attribute ‘reboot required’, or HMS invoked REBOOT method; upon completion of the HMS transaction and HNB Deregistration the HNB performs a controlled shutdown and reboot. Upon restart the HNB performs a new initialisation.

▀ RRM


385 UBS-44-57-004

6 RRM

6.1 Initial RRM During initialisation the HNB will notify the HMS of the following database parameters to indicate which of its RF parameters are self-configurable:

.FAPService.1.FAPCapabilities. UMTS.SelfConfig.

Residential Stage 1 Configuration

UARFCNConfig TRUE PrimaryScramblingCodeConfig TRUE MaxFAPTxPowerConfig TRUE PCPICHPowerConfig FALSE MaxULTxPowerConfig TRUE LACRACURAConfig TRUE NeighborListConfig TRUE CellReSelectionConfig FALSE IntraFreqMeasConfig FALSE InterFreqMeasConfig FALSE InterRATMeasConfig FALSE UEInternalMeasConfig FALSE

Table 113: Residential Iuh Initialisation RRM and Cell Config parameters.

▀ RRM


Stage 1: HNB runs DLMM and collects all the SIB information from surrounding Macro network based on

iHMS parameter range. WCDMA and GSM REM results communicated to iHMS. Note: Detected HNB scrambling

codes should also be reported in REM results.

Stage 1: HNB receives from the iHMS the WCDMA and GSM band, PLMN and UARFCN lists of information

Stage 2: (a) Receive from sHMS the RF parameter range and Neighbour List Configuration options and RF

Configuration Options.

Stage 2: Run Scrambling Code Selection Algorithm

Stage 2: populate the NeighborCellList

Stage 2: Set initial DL and UL Powers

Stage 2: Run Carrier Selection Algorithm

Stage 2: Apply sHMS Admin State filter to decide which RF parameters need to be configured from

sHMS parameters.

Stage 2: Overwrite HNB autoconfigured parameters

from sHMS RF parameters as a function of Admin State filter

End Stage 2: Inform sHMS of HNB RF parameters.

Do the sHMS RF parameters

include new UARFCNS?

NO

Rerun the REM scan for the additional UARFCNs

YES

Stage 1: HNB powers up and communicates its RF self configuration capability to iHMS

Figure 11: Residential Iuh RRM initialisation process

With respect to the Residential Iuh RRM initialisation showed in Figure 11, the following comments are relevant:

• During initialisation the HNB reports its RF auto-configuration parameters through the data object defined as FAPService.{i}.FAPCapabilities.UMTS.SelfConfig.

• After receiving the UMTS and GSM UARFCN information from the initial HMS (through the .FAPService.{i}.REM. data object) the HNB then runs a REM scan for those particular UMTS and GSM UARFCNs and reports the demodulated information (e.g. PSCs, neighbours etc.) in the FAPService.{i}.REM.WCDMAFDD.Cell.{i} and FAPService.{i}.REM.WCDMAFDD.Cell.{i} data object. Note that the UARFCNDLList is the set of UARFCNs that the HNB should scan. These are not necessarily the UARFCN’s that the HNB can select from.

▀ RRM


387 UBS-44-57-004

• In Stage 2, the sHMS through the .FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.RF. and FAPService.{i}.FAPControl.UMTS data objects define both the ranges of RF parameters (UARFCN, PSCs, DL/UL powers etc.) and which of these parameters are auto-configurable for the HNB. Note that the UARFCNDL parameters are those down link UARFCN’s that the HNB can select from if the correct autoconfiguration is applied.

• If any additional UARFCNs (i.e. see UARFCNDL in FAPService.{i}.CellConfig.UMTS.RAN. FDDFAP .RF) were added by the sHMS in stage 2, the HNB may need to re-run the REM/RRM procedure.

• The HNB then runs the Carrier selection, PSC selection and Neighbour Cell List creation algorithms (irrespective of the configuration settings in .FAPService.{i}.FAPControl.UMTS.). Following this, selectively per parameter type. If auto configuration is allowed for that parameter according to .FAPService.{i}.FAPControl.UMTS. the value created by the algorithm is applied. If auto configuration is not allowed then the value is set as configured from the sHMS.

• In the final step of stage 2, the HNB then reports back to the sHMS the cell configuration parameters that it has configured itself to using the .FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.RF data object. For example UARFCNDLInUse would contain the DL carrier frequency UARFCN selected by the HNB.

• There are a range of RF error conditions that can be triggered (e.g. high RSSI, no PSC available etc.) that can be triggered as part of the RRM algorithm processing. These error conditions generally result in the HNB going into a particular ‘error state’ (i.e. safe RF power state). These error conditions shall generate an alarm or log event as appropriate.

6.2 Subsequent RRM After initialization is complete, through subsequent RF scans the HNB may detect a RF ‘significant event’ which could result in the HNB (if the HMS settings are correct) bringing the cell down and reconfiguring its UARFCN and PSC parameters. This occurs for the following events:

• It is assumed that the following parameters will be configured in .FAPService.{i}.REM. to cause a periodic DLMM7.

o ScanPeriodically

o PeriodicInterval

o PeriodicTime

• The Sniff Mode is always operational irrespective of the HMS database parameter settings as the HNB frequency reference is derived from this measurement of the surrounding UMTS/GSM Macro Layer. Consequently, after each Fast Sniff Mode the HNB will carry out detection of a RF ‘significant event’, namely:

o The HNB selected a code already in use by another HNB due to a lack of free codes and a previously used scrambling code is no longer being detected i.e. it appears to be free.

o Latest sniff mode results of the allowed HNB carriers indicate that carrier selection will lead to the choice of a different carrier allowing for a margin of ‘CarrierChangeThreshold‘ in the macro layer interference calculation. ‘CarrierChangeThreshold‘ is a parameter supplied by the HMS.

o A macro cell with an RSCP larger than any previously measured RSCPs is detected which implies a network re-plan.

o A neighbour HNB which the HNB slaved its powers from disappears and the HNB now has to reconfigure its DL and UL transmit powers.

• If any of the above ‘significant events’ occur then the HNB cell is brought down and DLMM rerun. After a ‘filter stage’ this could result in the selection of a new UARFCN, PSC, creation of a new NCL and/or DL/UL transmit powers within the ranges defined from the HMS. The filtering stage applies only those parameters with auto configuration enabled to be applied.

7 DLMM and Sniff mode are almost equivalent except DLMM will detect both new 2G and 3G cells while Sniff Mode will currently only detect new 3G cells.

▀ RRM


• Finally the HNB would then report back to the sHMS the cell configuration parameters that it has configured itself to using the .FAPService.{i}.CellConfig.UMTS.RAN.FDDFAP.RF data object. For example UARFCNDLInUse would contain the DL carrier frequency UARFCN selected by the HNB.

▀ Handovers


389 UBS-44-57-004

7 Handovers 7.1 Handout This section provides a summary of the Intra-freq, Inter-freq and Inter-RAT handout triggers that are supported by the HNB. The following sections summarise the various HO processes. The relevant parameters are covered in sections 4.9.8 to 4.9.10.

The following hand-out (HO) triggering events are implemented:

Intra-freq HO:

• Event 1E: CPICH of cell becomes better than threshold. The objective for this measurement report is to inform the Femto Cell when a specific cell rises above some absolute threshold. For this, the trigger is that a primary CPICH becomes better than some absolute threshold for the quantity being measured. The monitored set are those cells derived through the Down Link Monitor Mode (DLMM).

• Event 1F: CPICH of cell becomes worse than threshold. This event is the reverse of event 1E. The event is triggered when the primary CPICH for a cell falls below some absolute threshold for a defined time period (time-to-trigger). The time to trigger value is currently a parameter set at the Femto Cell database and not available at the HMS.

Inter-freq HO:

• Event 2D: start of compressed mode. If the used frequency CPICH Ec/No falls below a specified level for a specified time period (time-to-trigger) then the event is triggered and a measurement report sent to the femtocell.

• Event 2F: stop compressed mode. If the used frequency CPICH Ec/No goes above a specified level for a specified time period (time-to-trigger) then the event is triggered and a measurement report sent to the femtocell.

• Event 2B: Quality of current frequency below threshold and quality of target frequency is above another threshold. This inter-frequency measurement event is intended to indicate to the femtocell that the used frequency has fallen below some threshold and that the non-used frequency is currently above the threshold. The frequency quality is based on the contents of the virtual active set. If the criteria are meet for a period (defined by a time-to-trigger) a measurement report is sent.

Use 3G Listen Mode to generate dedicated mode: • Intra-Freq neighbour list • Inter-Freq neighbour list

RRC connection establishment

RRC: MEASUREMENT CONTROLIntra-Frequency Dedicated Mode Neighbour List

Event 1E configurationEvent 1F configuration

RRC: MEASUREMENT CONTROLEvent 2D configuration (for inter-freq meas)Event 2F configuration (for inter-freq meas)

RRC: MEASUREMENT REPORTEvent 2D

RRC: MEASUREMENT CONTROLActivate Compressed Mode

Inter-Frequency Dedicated Mode Neighbour ListEvent 2B configuration

RRC: PHYSICAL CHANNEL RECONFIGCM Pattern

RRC: PHYSICAL CHANNEL RECONFIG COMPL

If UE needs CM for inter-freq

measurements

Figure 12: Intra/Inter frequency HO RRC messaging sequence

▀ Handovers


Inter-RAT HO:

• Event 2D: start of compressed mode. If the used frequency CPICH Ec/No falls below a specified level for a specified time period (time-to-trigger) then the event is triggered and a measurement report sent to the femtocell.

• Event 2F: stop of compressed mode. If the used frequency CPICH Ec/No goes above a specified level for a specified time period (time-to-trigger) then the event is triggered and a measurement report sent to the femtocell.

• Event 3A: Quality of UTRAN frequency is below a threshold and quality of GSM is above another threshold. The event is designed to notify the femtocell that when the current cell falls below a certain threshold at the same time as one or more GSM cells rise above a defined threshold.

• Event 3B: quality of GSM is below threshold. This event is triggered if the current cell falls below the threshold for a period of time (time to trigger) after which a measurement report is sent.

Obtain dedicated mode Inter-RAT neighbour list via 2G Listen Mode

RRC connection establishment

RRC: MEASUREMENT CONTROLEvent 2D configuration (for 2G measurements)Event 2F configuration (for 2G measurements)

RRC: MEASUREMENT REPORTEvent 2D (for 2G measurements)

RRC: MEASUREMENT CONTROLActivate CM Pattern

Inter-RAT Dedicated Mode Neighbour ListEvent 3A configuration

RRC: PHYSICAL CHANNEL RECONFIGCM Pattern

RRC: PHYSICAL CHANNEL RECONFIG COMPL

If UE needs CM for 2G

measurements

RRC: MEASUREMENT REPORTEvent 3A2G reported measurements Handover

Decision

Figure 13: Inter RAT HO RRC messaging sequence

7.1.1 RCSP Based Handover For RSCP based see reference:

• [UBS-21-30-244] RSCP Based Handover Feature Analysis

▀ Location Verification


391 UBS-44-57-004

8 Location Verification As required in [TS25.467], Location Verification is performed by the HMS/HNB-GW; Cisco's HNB complies with [TS33.320], Section 8.1.1, by supporting the following Location Verification methods:

• “Information of macro-cells surrounding the H(e)NB provided by the H(e)NB”

• The HNB will report the surrounding macrocells to the HMS as part of the Network Listen procedure. See section 4.12 for details on the standard parameters and vendor extension supported

• “Geo-coordinates provided by a GNSS receiver embedded into the H(e)NB” (subject to GPS capable hardware):

o The HNB can be provided with a GPS receiver. Parameters to manage and monitor the GPS receiver are described in section 4.13.

Note that, 3GPP defines the “public IP” address of the HNB to also be an optional input into Location Verification. Cisco defer determination of the public IP address to the HMS as there is no secure method of determining it locally at the HNB.

However, Cisco's HNBs can provide further location detection techniques and alarms, as follow:

• Changes of neighbouring cells (section 8.1); which may trigger a “Location Change” alarm

• Detection of neighbour’s PLMNs (see section 8.2); which may trigger a “Invalid Country” alarm

• Changes of HomeGateway device (see section Error! Reference source not found.); which may trigger a “MAC Address change” alarm

Operators have full control on these from the HMS.

Finally, the location coordinates of the femtocell can be written and stored on the HNB by the HMS (using the parameters defined in section 4.25). The location coordinates can be read by other HMSs which do need to repeat the location verification procedure.

It should be noted that the algorithms for Location Verification are only run during DownLink Monitor Mode (DLMM). The “Fast Sniff” feature detected 2G and 3G cells; however, no location checking is carried out with this data.

If during Fast Sniff a cell (previously detected) is not found, it is removed from the DB. 3G cells may be re-established if come back on line, while 2G are removed till next DLMM. A threshold of 4 Fast Sniffs is used before removing cells.

8.1 HNB Location Change Detection Based on Changes of Neighbouring Cells

At power-up, the HNB scans all the frequencies in the bands and RATs (e.g. UTRA and GSM) it has been configured for.

The newly detected list of neighbour is compared against the previous list stored in the database. If the list of detected cells has changed considerably from the stored list (as configured by the threshold describe in section 8.1.1), new macro cells are reported back to the HMS and the alarm LocationChanged (see list of alarms in section 4.15.1) is raised.

Depending on configuration information provided by the HMS in LocationChangeBehaviour (see .CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile), the HNB will raise the alarm LocationChanged and either:

• Continue the initialisation procedure, giving to the HMS the responsibility of inhibiting HNB service, if required.

• Stops the initialisation sequence (and hence not provides any service). The HNB will not provide service until, following a reboot, it can verify its correct location. The HMS can allow service to resume by clearing the contents of the UMTS/GSM macro neighbour list and rebooting the HNB.



The parameter OverrideLocationChangeServiceInhibition can be used to switch off any action taken following a detection of location change .

8.1.1 Algorithm Details The HNB monitors 3G and 2G frequencies at power up through its DLMM (DownLink Monitor Mode). Once the list of neighbouring cell has been provisioned by the HMS the list is written in non-volatile memory. Following DLMM scans, new list of detected cells are compared with the list stored on the HNB. The possible outputs from the analysis of the detected cells changes, these are globally:

• The HNB considers there is No Location Change if less than N% (LocationChangeThreshold in .CellConfig.UMTS.RAN.FDDFAP.RF X_UBIQUISYS_COM_RRMProfile) of the UMTS/GSM macro neighbour cells on the AP allowed frequencies have changed.

o The new list of cells will substitute the one stored on the HNB

• Whenever N% or more (as defined by the parameter LocationChangeThreshold) of the UMTS/GSM macro neighbour cells on the HNB allowed frequencies have changed: the HNB considers it has been moved and a LocationChanged alarm is raised8.

o The original list of neighbouring cells will be maintained

However, in order to better understand the percentage N calculation and exceptions, it is necessary to understand the full algorithm criteria used to determine if a location change has occurred.

• If LocationChangeThreshold == 0 the LocationChange alarm is disabled

• If there are 2, or less, known cells (n_known_cells), location checking is disabled.

• Otherwise the HNB calculates the Cell Change Metric and compares it to the threshold: cell_chg_metric = ((n_added_cells + n_deleted_cells) *100) / n_known_cells

o if (cell_chg_metric >= LocationChangeThreshold) then a location change has been detected.

Ultimately, if both the UMTS or GSM Macro lists were initially empty, i.e. this is the first initialisation after a factory or database reset, the location change alarm will not be raised

Note:

• n_known_cells is the number of previously stored 3G and 2G HPLMN neighbour cells.

• n_added_cells is incremented if:

o no previous cell with that frequency/ scrambling code could be found i.e. the cell has moved from being Derived from the neighbour list of a cell, to actually being detected.

• n_deleted_cells is incremented if:

o cell is to be deleted (it cannot be seen anymore)

o or can no longer be detected, but it is still present in the neighbour list of a macro cell.

8.2 HNB Location Change Detection Based on Detection of Neighbour’s PLMNs

At power-up, the HNB attempts to decode the PLMNs of all the detected cell in the frequency bands and RATs (e.g. UTRA and GSM) it was configured for.

The following cases are considered:

8 This is likely to be the case if the HNB is physically moved to another location, but it may also occur when there has been some RF re-engineering on the macro around the AP location.



393 UBS-44-57-004

• If none of the neighbouring cells have the same MCC as the one configured in the HNB (both HPLMN and PLMNs), the HNB assumes to be sited in a wrong country

• If one or more neighbouring cells have the same PLMS as the one configured in the HNB, the HNB assumes that it is sited in the correct country.

Depending on configuration information provided by the HMS for the parameter InvalidCountryBehaviour (in .CellConfig.UMTS.RAN.FDDFAP.RF.X_UBIQUISYS_COM_RRMProfile.), the HNB will raise the alarm InvalidCountry (see supported alarms in 4.15.1) and either continue as normal, or stop the initialisation sequence (and hence not provide any service). The HNB will not provide service until, following a reboot, it can verify its correct location. The HMS can override this behaviour by setting the parameter OverrideInvalidCountryServiceInhibition.

▀ Revision History


9 Revision History Version Date Author Comment

0.1 13 Nov 14 Simon Hughes Baseline R3.5 document using R3.5.9.22

1.0 08 Dec 14 Simon Hughes Version 1 for R3.5.10.3

2.0 20 April 15 Simon Hughes V2.0 updated to 3.5 MR R3.5.11.11

2.1 27 Jan 16 Manbir Kaur Updated the description in section 4.9.13.9 RF Parameters for parameter MaxFAPTxPower, MaxULTxPower

Updated the description in 4.9.13.9.1 RRM Profile for the following parameters:

• MinWidebandInterferenceLevel,

• MaxTotalWidebandInterferenceLevel,

• MaxTotalMacroPilotInterferenceLevel,

• MaxZAP_RSCP_Level,

• NodeBNoiseFloor,

• ULNoiseRiseMargin,

• StraddledUplinkNoiseRiseMargin,

• SlavingZAPRange,

• ScramblingCodeSelectionMethod

2.2 15 Feb 16 Manbir Kaur Updated the description for EnableLoadBasedCoverageTuning parameter

2.3 15 June 16 Manbir Kaur Aligned the document with R3.7 changes

2.4 09 March 17 Monika Goyal Corrected RMS property of many parameters

2.5 26 May 17 Monika Goyal Default Value and RMS property of parameters is aligned with Configurable_parameter_guide_RMS52