SRS-FBSR-OAM Alcatel-Lucent -Confidential Version: 2.

2 (Approved)

/BSR SRS Documents

SRS-FBSR-OAM

OAM requirements of Femto BSR

Version: 2.2 (Approved)

Printed by: lfreiber
Printed on: 10 July 2014

10 July 2014 Alcatel-Lucent - Confidential - This Document is Uncontrolled if Copied or Printed i

SRS-FBSR-OAM Version: 2.2 (Approved)

Contents

3 System Description and Requirements 1

3.1 Configuration Management 1
3.1.9 Spare Parameter Handlings 1

Contents Alcatel-Lucent - Confidential - This Document is Uncontrolled if Copied or Printed ii

SRS-FBSR-OAM Version: 2.2 (Approved)

OAM requirements of Femto BSR Attributes

3 System Description and Requirements Object ID:SRS-FBSR-OAM-149

3.1 Configuration Management Object ID:SRS-FBSR-OAM-505

3.1.9 Spare Parameter Handlings Object ID:SRS-FBSR-OAM-2109

There are spare parameters defined in the MIM. They are used when late adder features and functions are introduced after MIM Object ID:SRS-FBSR-OAM-2110
freeze. All the spare parameters are string type with maximum length either 50 or 80 chars. They are all defined in BSR MO,
with name like sparePara<X>, where X is an integer starting from 1.

There are certain rules and conventions when provisioning the spare parameters. This is needed to facilitate the contents
processing to be used by the Small Cell applications.

If a spare parameter includes multiple variables, the ";" shall be used as a delimiter between different variables. For example, Object ID:SRS-FBSR-OAM-2111
sparePara1="name1=<value1>;name2=<value2>" Object Type:SRS Requirement
Feature Number:b174378
Review Status:Approved

If there are multiple instances of the same parameter defined in a spare attribute then the behaviour shall be defined by the first Object ID:SRS-FBSR-OAM-2112
instance of that parameter in the string. Object Type:SRS Requirement
Feature Number:b174378
Review Status:Approved

The values in the spare parameter shall not be case sensitive. For example, if a Boolean type is included, the preferred values Object ID:SRS-FBSR-OAM-2113
should be true or false, but other cases are also allowed, e.g. "TRUE". Object Type:SRS Requirement
Feature Number:b174378
The parameter name encoded in the spare shall also not be case sensitive. Review Status:Approved

It is also suggested that the Small Cell should also support the rules validation by implementing centralised functions to process Object ID:SRS-FBSR-OAM-2114
the spares, e.g. a common library for decoding, etc.

10 July 2014 Alcatel-Lucent - Confidential - This Document is Uncontrolled if Copied or Printed Page 1 of 2
SRS-FBSR-OAM Version: 2.2 (Approved)

OAM requirements of Femto BSR Attributes

The Small Cell Access Point shall log a warning message whenever a failure occurs in parsing a spare parameter. Object ID:SRS-FBSR-OAM-2179
Object Type:SRS Requirement
Notes: Feature Number:b174378
The centralised function provided for parsing spare parameters shall provide a set of informative warning messages supporting Review Status:Ready for Review
a wide range of parsing errors.
Along with allocating Spara Parameters and documenting the Spare Parameter definition, the SRS-FBSR-DATA shall provide
guidelines that recommend that the centralised function is always used for parsing Spare Parameters.

10 July 2014 Alcatel-Lucent - Confidential - This Document is Uncontrolled if Copied or Printed Page 2 of 2