V5 - 10th May 2001 OAM Solutions

1. UMTS V1 iBTS and iRNC OAM AnalysisThis presentation analyses the strengths and weaknesses of the Access Network Element OAM functionality in the V1 timeframe. It is intended as a basis for discussion and an input into future iBTS and iRNC releases V5 - 10th May 2001 OAM Solutions

2. History • V3 • First wide distribution and review with URAN PLM • V4 • No iRNC control node alarms at all in V1 • V5 • Add iBTS feedback. • «False » class 2 management for RRM parameters.

3. iBTS - Configuration Management • Positive Points • Configuration Management available from V1.0 via FTP of a file to the iBTS • Negative Points • Activation of new configuration, even for one parameter update (e.g set administrativeState !) is done using a "build" of the iBTS MIB. • This resets the BTS, with loss of service. No improvement before V2. In V2, there is a plan to have a full SEPE management. • No "class 3" commands planned (parameters which can be modified without service impact) • The BTS resets when it lose it the Iub interface with the Interface Node • No way to modify I&C parameters remotely (no way to modify the IP @ of the NodeB or the IP @ of the OMC that the NodeB communicates with and the flag activating / disactivating the DHCP mechanism). A solution is under study by the iBTS team to have a solution in V1.2

4. iBTS - Fault Management • Positive Points • Real-time alarms as from V1.0 • Note: no information yet available on the quantity and quality of iBTS alarms in V1 - to be monitored carefully • Negative Points • Some alarms are never cleared by the BTS. • No state management (state changes). It will be introduced with SEPE management.

5. iBTS - Performance Management • Positive Points • Debug trace planned for v1.2 (tbc) which allows to tune the BTS. CDMA experience has shown this was a useful tool to build a working network • Observation counters available in V1.0 for debug, consultation possible remotely using a BTS tool running on OMC-B or TIL. • Negative Points • No "physical" counters available in V1 - TBC • No clear understanding of the iBTS counters added value for the end-user (is it only platform counters for diagnostic activity ?) • No clear estimation of the involved IP traffic & CPU load (all the iBTS must be permanently monitored) • No observation configuration for iBTS • No real time performance management

6. iBTS - Upgrades • Positive Points • Background downloading of software while the iBTS is in service • Remote, parallel downloading available from V1.0 with automatic activation of the new software • Activation can be decorrelated from the downloading phase by the end of V1 • Negative Points • Downtime is estimated at 20 minutes (to be checked soon during integration testing), target needs to be less than 1 minute • This situation will certainly not improve up until the V2 to V3 upgrade (no committment on this) • Upgrade duration impacted by the OAM network (limitation of a 1.2 Mb/s throughput due to RNC interface node limitation) • Network bandwidth limited to 200 Kb/s for one iBTS. This limitation is due to the FFS management inside the iBTS

7. iBTS - Plug & Play • Positive Points • Shelf Level Display on the OAM is updated automatically with the cards installed physically in the BTS (upon BTS reset only) • Partial inventory data provided by Node B in V1.2 • Negative Points • No dynamic update of cards on the Shelf Level Display if cards are inserted or extracted. A workaround is possible in V1.2 to manage the special case of the TRM board.

8. iBTS - Auto Discovery • Positive Points • DHCP should work for auto IP address allocation in V1 (to be tested) • iBTS connects automatically to the OAM when the transmission link is established • iBTSs which are not yet configured on the OAM appear in a special window with all their details • Negative Points • Process to enter iBTS serial number into OAM system not clear, must be validated during VO Phase

9. iRNC - Configuration Management • Positive Points • iRNC Configuration Management available from V1.0 • Negative Points • Limited set of on-line commands (lock / unlock on FddCell, controlPort and on some attributes of RRM objects) • No class 3 attribute management. • iRNC-CNode build sequence resets the iRNC and all its sub-tending iBTSs, with loss of service. • Two different OAM interfaces for the INode and Cnode; different level of services between the two systems. • RRM parameters are not managed are « standard » class 2 parameters. To modify a class 2 RRM parameter, it is mandatory to lock all cells hosted by the iRNC-CNode.

10. iRNC - Fault Management • Positive Points • iRNC real-time Fault Management available as from V1.0 • Note: no information yet available on the quantity and quality of iRNC alarms in V1.0 - to be monitored carefully • Negative Points • No RNC Control Node alarms at all in V1 • No faults on logical objects (only some state changes) • No filtering mechanism at EMS level between INode alarms and CNode alarms

11. iRNC - Performance Management • Positive Points • Debug Call Trace available from V1.1b • UMTS INode counters collected and aggregated by CNode. • Negative Points • No real time performance management

12. iRNC - Upgrades • Positive Points • Negative Points • No remote downloading feature available in V1. • Upgrades are done using the TML. Note: possibility of launching the TML remotely from the OMC is being investigated • This situation may not change for V2 • Downtime target is 6 minutes (TBC) by the end of V1. Customers will certainly expect a hitless RNC upgrade once in commercial service • Bandwidth for Node B upgrades is limited to 1.2Mbit/s (until V1.2??)

13. iRNC - Plug & Play • Positive Points • Shelf Level Display on the OAM is updated automatically with the cards installed physically in the iRNC (upon RNC reset only) • Negative Points • No dynamic update of cards on the Shelf Level Display if cards are inserted or extracted • No real hardware snapshot in V1. Hardware description will be entered into CNode during I&C phase using TML. No plan for the H/W snapshot step 3 integration • No inventory information • No unified SLD for iRNC nodes (CNode, INode, ANode)