3GPP CORBA Bulk CM Northbound

Nokia Siemens Networks NetAct OSS5.4 CD Set 2

3GPP CORBA Bulk CM Northbound Interface Principles

DN03317891

Issue 10-1

Nokia Siemens Networks is continually striving to reduce the adverse environmental effects of its products and services. We would like to encourage you as our customers and users to join us in working towards a cleaner, safer environment. Please recycle product packaging and follow the recommendations for power use and proper disposal of our products and their compo-nents.

If you should have questions regarding our Environmental Policy or any of the environmental services we offer, please contact us at Nokia Siemens Networks for any additional information.

2 DN03317891Issue 10-1

3GPP CORBA Bulk CM Northbound Interface Princi-ples

Id:0900d80580942544

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

The information or statements given in this documentation concerning the suitability, capacity, or performance of the mentioned hardware or software products are given "as is" and all liability arising in connection with such hardware or software products shall be defined conclusively and finally in a separate agreement between Nokia Siemens Networks and the customer. However, Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT.

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

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

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

Copyright © Nokia Siemens Networks 2012/9/28. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product.

The safety information is provided in the Safety Information section in the “Legal, Safety and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-satzes.

DN03317891Issue 10-1

3


Id:0900d80580942544

Table of ContentsThis document has 136 pages.

1 About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.1 NetAct compatibility and capacity information . . . . . . . . . . . . . . . . . . . . . 81.2 Terms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 Introduction to 3GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 3GPP CORBA Bulk CM Northbound Interface . . . . . . . . . . . . . . . . . . . 123.1 IDL files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1.1 3GPP IDL files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.1.2 Object Management Group IDL files . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.2 Supported network resource models . . . . . . . . . . . . . . . . . . . . . . . . . . . 123.3 Used XML schemas. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4 Functionality overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4.1 System roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133.4.2 IRP-related functionality. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.5 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.6 Supported operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.6.1 startSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.6.2 endSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.6.3 upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.6.4 download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.6.5 preactivate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.6.6 activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.6.7 fallback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.6.8 abortSessionOperation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.6.9 getSessionIds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.6.10 getSessionStatus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.6.11 getSessionLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.6.12 getBulkCmIRPVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.7 Supported notifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.7.1 Push and Pull style . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.7.2 notifySessionStateChanged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.7.3 notifyGetSessionLogEnded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 NetAct Object Model RAN data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.1 Naming conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2 Associations between object models . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2.1 Associations for management node. . . . . . . . . . . . . . . . . . . . . . . . . . . . 304.2.2 Associations for NetAct and external managed objects. . . . . . . . . . . . . 304.2.3 Associations for NetAct WCDMA managed objects . . . . . . . . . . . . . . . 324.2.4 Associations for NetAct WBTS managed objects . . . . . . . . . . . . . . . . . 354.2.5 Associations for WCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 364.2.6 Associations for ANTE managed objects. . . . . . . . . . . . . . . . . . . . . . . . 374.2.7 Associations for OMS managed objects . . . . . . . . . . . . . . . . . . . . . . . . 38

4 DN03317891Issue 10-1


Id:0900d80580942544

4.2.8 Associations for NetAct MRBTS (LTE eNB) managed objects in RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

4.2.8.1 Associations for MRBTS managed objects. . . . . . . . . . . . . . . . . . . . . . . 384.2.8.2 Associations for LNBTS managed objects . . . . . . . . . . . . . . . . . . . . . . . 394.2.8.3 Associations for FTM managed objects . . . . . . . . . . . . . . . . . . . . . . . . . 404.2.8.4 Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 414.2.8.5 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 424.2.9 Associations for NetAct MRBTS (LTE eNB) managed objects in

RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 434.2.9.1 Associations for MRBTS managed objects. . . . . . . . . . . . . . . . . . . . . . . 434.2.9.2 Associations for LNBTS managed objects . . . . . . . . . . . . . . . . . . . . . . . 444.2.9.3 Associations for FTM managed objects . . . . . . . . . . . . . . . . . . . . . . . . . 454.2.9.4 Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 464.2.9.5 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 474.2.10 Associations for NetAct MRBTS (LTE eNB) managed objects in RL40 . 484.2.10.1 Associations for MRBTS managed objects. . . . . . . . . . . . . . . . . . . . . . . 494.2.10.2 Associations for LNBTS managed objects . . . . . . . . . . . . . . . . . . . . . . . 494.2.10.3 Associations for FTM managed objects . . . . . . . . . . . . . . . . . . . . . . . . . 504.2.10.4 Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 524.2.10.5 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 524.3 Data amounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5 OSS5.x - 3GPP R6 object model mapping for WCDMA. . . . . . . . . . . . . 565.1 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.1.1 Considerations in CM data upload (NetAct model → 3GPP model) . . . . 605.1.2 Considerations in CM data download (3GPP model → NetAct model) . 605.2 Vendor-specific objects and parameters. . . . . . . . . . . . . . . . . . . . . . . . . 625.3 Interface-N XML file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6 OSS5.x - 3GPP R8 object model mapping for LTE RL15/RL20 . . . . . . . 726.1 Instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726.1.1 Considerations in CM data upload (NetAct model → 3GPP model) . . . . 776.1.2 Considerations in CM data download (3GPP model → NetAct model) . 77

7 OSS5.x - 3GPP R8 object model mapping for LTE RL25/RL30 . . . . . . . 787.1 Instance mappings for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 787.1.1 Considerations in CM data upload (NetAct model → 3GPP model) . . . . 847.1.2 Considerations in CM data download (3GPP model → NetAct model) . 85

8 OSS5.x - 3GPP R8 object model mapping for LTE RL40. . . . . . . . . . . . 868.1 Instance mappings for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 868.2 Considerations in CM data upload (NetAct model → 3GPP model) . . . . 938.3 Considerations in CM data download (3GPP model → NetAct model) . 93

9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

10 Where to find more information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

11 Appendix A: BulkCmIRPConstDefs.idl . . . . . . . . . . . . . . . . . . . . . . . . . . 96

12 Appendix B: BulkCMIRPSystem.idl . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

13 Appendix C: BulkCMIRPNotifications.idl. . . . . . . . . . . . . . . . . . . . . . . . 112

DN03317891Issue 10-1

5


Id:0900d80580942544

14 Appendix D: LTE RL40 3GPP XML file example . . . . . . . . . . . . . . . . . 114

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

6 DN03317891Issue 10-1


Id:0900d80580942544

List of FiguresFigure 1 Overview of the global Network Manager . . . . . . . . . . . . . . . . . . . . . . . . 11Figure 2 OMC management node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 3 RNC external managed objects association . . . . . . . . . . . . . . . . . . . . . . 31Figure 4 GSM external managed objects association. . . . . . . . . . . . . . . . . . . . . . 31Figure 5 Utran external managed objects association . . . . . . . . . . . . . . . . . . . . . 32Figure 6 LTE external managed objects association . . . . . . . . . . . . . . . . . . . . . . 32Figure 7 WCDMA associations (1/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 8 WCDMA associations (2/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 9 WCDMA associations (3/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Figure 10 WBTS associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 11 WCEL associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 12 ANTE associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 13 OMS associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 14 MRBTS associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 15 LNBTS associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 16 FTM associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Figure 17 IPNO associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 18 LNCEL associations for RL15/20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 19 MRBTS associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 20 LNBTS for RL25/RL30 associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 21 FTM associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 22 IPNO associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Figure 23 LNCEL associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 24 MRBTS associations for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 25 LNBTS for RL40 associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 26 FTM associations for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Figure 27 IPNO associations for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 28 LNCEL associations for RL40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 29 Data amount example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 30 NOM vendor-specific objects and vendor-specific data . . . . . . . . . . . . . 62Figure 31 Containment for Frequency Measurement Control Objects . . . . . . . . . . 63Figure 32 Containment for Handover path objects . . . . . . . . . . . . . . . . . . . . . . . . . 63Figure 33 Containment for Location Services -related objects . . . . . . . . . . . . . . . . 64Figure 34 Containment for IMSI based HO -related objects . . . . . . . . . . . . . . . . . . 64

DN03317891Issue 10-1

7


Id:0900d80580942544

List of TablesTable 1 Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Table 2 Used XML Schamas and the modifications . . . . . . . . . . . . . . . . . . . . . 13Table 3 The Bulk Configuration Management IRP-related functionality . . . . . . 14Table 4 subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 5 unsubscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Table 6 startSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 7 endSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 8 upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 9 download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 10 activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Table 11 fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 12 abortSessionOperation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Table 13 getSessionIds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 14 getSessionStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 15 getSessionLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 16 getBulkCmIRPVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 17 notifySessionStateChanged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Table 18 notifyGetSessionLogEnded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Table 19 Data amount example for LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Table 20 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Table 21 NetAct UTRAN vendor specific object/data mappings . . . . . . . . . . . . . 65Table 22 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Table 23 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Table 24 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

8 DN03317891Issue 10-1


Id:0900d80580942542

About this document

1 About this document3GPP CORBA Bulk CM Northbound Interface Principles document describes the Nokia Siemens Networks NetAct implementation of the 3GPP CORBA Bulk CM Northbound Interface as well as object model mapping between the NetAct object model and the 3GPP R6 UTRAN/ 3GPP R8 EUTRAN object model.

This document is intended for personnel integrating the NetAct 3GPP CORBA Bulk CM Northbound Interface.

1.1 NetAct compatibility and capacity informationFor information on the NetAct system and capacity, and the compatibility between NetAct and network element releases, see the NetAct Compatibility and Capacity Infor-mation document.

1.2 TermsFor general information on terms, see Glossary, DN9763965.

Term Explanation

3GPP Third Generation Partnership Project

Common The term refers to 3GPP R6 specifications. For instance, “common parameters” equals parameters defined in 3GPP R6 bulk CM specifi-cations.

DN Distinguished name, a name of a managed object which consists of a sequence of the relative distinguished names of its superiors in the naming tree, starting at the root and working to the managed object to be identified.

FBTS Foreign BTS

Interface-N An interface between a global Network Management System and a regional Element Management System.

IOR Interoperable Object Reference

Main object, related object

Two 3GPP objects that refer to the same NetAct object can be called a main object and a related object. The parent 3GPP object is the main object and the child object is the related object. For example, Managed Element: RNC is a main object and its child, RncFunction, is a related object, because they both refer to the same RNC.

MO Managed Object

NM Network Manager

NEM Network Element Manager

NRM Network Resource Model

NOM NetAct Object Model

Non-network parameters

Parameters visible only in the NEM level, not in the network interface.

OMG Object Management Group

Table 1 Terms

DN03317891Issue 10-1

9


About this document

Id:0900d80580942542

R6 Release 6 (of the 3GPP specifications)

R6OM 3GPP R6 Object Model

R8OM 3GPP R8 Object Model

RC Regional Configurator

VSD Vendor-Specific Data

IRP Integration Reference Point, a collection of related integration inter-faces that form a connection point between subsystems.

IRPAgent A subset of network (element) functions in a region. For instance, Regional Configurator (RC).

IRPManager A system that can act as a global-level network management system.

Term Explanation

Table 1 Terms (Cont.)

10 DN03317891Issue 10-1


Id:0900d80580942542

Introduction to 3GPP

2 Introduction to 3GPPThe 3rd Generation Partnership Project (3GPP) is a collaboration agreement that brings together a number of telecommunications standard bodies. 3GPP has specified the Interface-N which can be used to transfer network configuration data between:

• one global network management system and • several regional network element managers (by different network vendors).

Parameters specified in the 3GPP specifications are the same for all vendors. In other words, all vendors have to support them to allow centralised base network configuration management.

3GPP CORBA Bulk CM Northbound Interface provides a network management inter-face for integration of the Configurator regional cluster into a 3GPP-compliant network-wide configuration management system. The interface is provided for all networks (how-ever, the current release supports only UTRAN, E-UTRAN and CORE) and it covers 3GPP common objects and parameters as well as NetAct-specific objects and parame-ters. For the data exchange standard, 3GPP Bulk CM file format is used including vendor-specific data extensions to cover NetAct-specific objects and parameters.

Starting from OSS5.2 CD Set 1 SFTP can be used as protocol for transferring data between NetAct and external systems. For information on how to configure SFTP, see Enabling the SFTP file transfer between NetAct and 3GPP manager in Managing NetAct System Security

2.1 OverviewThe following graphic illustrates the basic idea in global NM and the position of the 3GPP CORBA Bulk CM Northbound Interface.

DN03317891Issue 10-1

11


Introduction to 3GPP

Id:0900d80580942542

Figure 1 Overview of the global Network Manager

Interface-N

Global Network Manager

eNodeBRNC RNC RNC RNC RNC RNC

Interface

CM Northbound

3GPP CORBA Bulk

interfaceNetwork

RegionalConfigurator

VendorX

VendorY

eNodeBeNodeB

12 DN03317891Issue 10-1


Id:0900d80580942542

3GPP CORBA Bulk CM Northbound Interface

3 3GPP CORBA Bulk CM Northbound InterfaceThis section describes the 3GPP CORBA Bulk CM Northbound Interface.

3.1 IDL filesThis section lists all IDL files that are required for 3GPP Bulk Configuration Management Northbound interfaces.

3.1.1 3GPP IDL filesThese files are included in this document as appendixes:

• Appendix BulkCmIRPConstDefs.idl • Appendix BulkCMIRPSystem.idl • Appendix BulkCMIRPNotifications.idl

3.1.2 Object Management Group IDL filesThese IDL files can be downloaded from the Object Management Group Website at http://www.omg.org.

• TimeBase.idl

• CosNotifyFilter.idl • CosNotifyComm.idl

• CosNotifyChannelAdmin.idl

• CosNotification.idl • CosEventComm.idl

• CosEventChannelAdmin.idl

3.2 Supported network resource modelsThe NetAct 3GPP CORBA Bulk CM interface supports the 3GPP network resource model specified in the following 3GPP specifications:

• TS 32.622-6.4.0 (2005-03) • TS 32.623-6.4.0 (2005-03) • TS 32.642-6.4.0 (2005-03) • TS 32643-6.4.0 (2005-03) • TS 32.652-6.4.0 (2005-03) • TS 32.653-6.4.0 (2005-03) • TS 32.762-8.2.0 (2009-09) • TS 32.763-8.2.0 (2009-09) • TS 32.752-8.2.0 (2009-09) • TS 32.753-8.2.0 (2009-09)

For these specifications, refer to 3GPP web pages in http://www.3gpp.org/.

The implementation supports UTRAN and E-UTRAN. Only GsmRelation and ExternalGsmCell are supported for GERAN.

DN03317891Issue 10-1

13



Id:0900d80580942542

3.3 Used XML schemasXML schemas should be used by the Global Network Manager system to validate the contents of configuration files before downloading them and after uploading them.

For the XML file format used in the Interface-N, see http://www.3gpp.org/ftp/specs/archive/32_series.

The names of the vendor specific schemas are formed from the following parts:

• Subsystem name • Network element release

For example, the vendor specific schema file for RNC RN4.0 is cmdrnc_rn4.0.xsd.

XML schemas provided by Nokia Siemens Networks for generic and vendor-specific data are installed in CS to direc-tory/etc/opt/nokia/oss/rac/conf/metadata/<subsystem_name>/3gpp/.

g For LTE E-UTRAN, the subsystem_name is cmdlte.

3.4 Functionality overviewThis section gives an overview of the 3GPP CORBA Bulk CM Northbound interface functionality.

For operations between the global NM and the RC, as well as operations between the RC and the network, see NetAct Configurator Principles.

3.4.1 System rolesThe system roles in the Interface-N CORBA communication are:

• The Regional Configurator system acts as a 3GPP CORBA IRPAgent. • The global NM system acts as a 3GPP CORBA IRPManager.

3GPP schema version modification to standard 3GPP schemas

configData.xsd Rel 32.615-630 No

genericNrm.xsd Rel 32.625-630 No

utranNrm.xsd Rel 32.645-690 No

geranNrm.xsd Rel 32.655-620 add schemaLocation="untranNrm.xsd" during importing untranNrm.

stateManagementIRP.xsd Rel 32.675-620

replace operationalStateType "disbled" with "disabled".

epcNrm.xsd Rel 32.755-820 Commented out the line xn:linkListType

eutranNrm.xsd Rel 32.765-820 • replace PLMNId "mNc" with "mnc" • add

schemaLocation="stateManagementIRP.xsd" during importing stateManagementIRP namespace

Table 2 Used XML Schamas and the modifications

14 DN03317891Issue 10-1


Id:0900d80580942542


3.4.2 IRP-related functionalityThis section describes the IRP-related functionality of the 3GPP CORBA Bulk CM Northbound Interface.

The Bulk Configuration Management IRP-related functionality

1 The validate operation is not supported in NetAct.2 The activate and fallback operations cannot be aborted.3 The get_bulk_CM_IRP_notification_profile and get_bulk_CM_IRP_operation_profile operations are optional and not supported in NetAct.

3.5 Getting startedA 3GPP IRPManager that needs to communicate with the IRPAgent through the 3GPP CORBA Bulk Configuration Management Interface will first have to discover the agent, that is, get the object reference for the NetAct CORBA servers implementing that inter-face.

Entry Point IRPTo get these object references, the 3GPP IRPManager has to connect to Entry Point IRP (EPIRP). The CORBA Naming Service Context of EPIRP can be uploaded via HTTP.

Information Service operation / noti-fication in 3GPP TS 32.612 Solution Set method in TS 32.613

startSession start_session

endSession end_session

upload upload

download download

validate1 validate

preactivate preactivate

activate2 activate

fallback2 fallback

abortSessionOperation abort_session_operation

getSessionIds get_session_ids

getSessionStatus get_session_status

getSessionLog get_session_log

getIRPVersion get_bulk_CM_IRP_versions

getNotificationProfile3 get_bulk_CM_IRP_notification_profile

getOperationProfile3 get_bulk_CM_IRP_operation_profile

Table 3 The Bulk Configuration Management IRP-related functionality

DN03317891Issue 10-1

15



Id:0900d80580942542

This can be achieved by opening a Telnet session to the NetAct osscore2 package on port 10115, or by opening a socket connection to the NetAct osscore2 package on port 10115 and then sending the following request:

GET /cgi-bin/get_nbif_ior

The 3GPP IRPManager retrieves and reads the IOR using methods described above. It then uses this IOR string to construct an object of type EPIRP by resolving naming context rel_6.EPIRP and then narrowing the object reference returned by resolver.

CM Bulk Data IRPAfter the EPIRP object is constructed, the get_IRP_reference() method of EPIRP object is used to retrieve the IOR of desired interface. This method requires an irpId parameter which is the naming context of the interface. The naming context for CM Bulk Data is BulkCmIRP. Parameter managerIdentifier in method get_IRP_reference is an identifier of the IRPManager. Any string can be used for this parameter. Parameter systemDN is the systemDN of the IRPAgent. An empty string can be used as the systemDN.

The returned IOR is placed in an inout parameter of the method call. This stringified IOR can then be converted to a CORBA object using the string_to_object() method of the ORB. Then this CORBA object is narrowed to the BulkCmIRP object.

The BulkCmIRP uses port 10200.

Notification IRPCM Bulk Data IRP uses Notification IRP to notify the IRPManager about events such as session state changes.

Notification IRP is retrieved through EPIRP in a similar fashion. The Naming Context is NotificationIRP.

After retrieving NotificationIRP, IRPManager can subscribe to notifications. This is done by calling attach_push() method on the Notification IRP interface. This method requires following parameters:

Information Service oper-ation parameter Solution Set method parameter

managerReference input parameter manager_reference, type string

timeTick input parameter time_tick, type long

notification Categories

input parameter notification_category_set, type NotificationIRPConstDefs::NotificationCategorySet

filter input parameter filter, type string

subscriptionId NotificationIRPConstDefs::SubscriptionId

Table 4 subscribe

16 DN03317891Issue 10-1


Id:0900d80580942542


The parameter notification_categories defines which category notifications are subscribed. The category for CM Bulk Data notifications is BulkCmIRP.

Method call will return a reference value, which needs to be used when notifications are unsubscribed. This is done by calling method detach_push() on the Notification IRP interface.

3.6 Supported operationsThe following operations are supported by NetAct Northbound Interface:

• start_session • upload • download • preactivate • activate • fallback • abort_session_operation • end_session • get_session_ids • get_session_status • get_session_log • get_bulk_CM_IRP_versions

For more information on the operations, refer to the 3GPP specification TS 32.612 in 3GPP web pages at http://www.3gpp.org/.

exceptions:

Attach

ParameterNotSupported

InvalidParameter

AlreadySubscribed

AtLeastOneNotificationCategoryNotSupported


managerReference input parameter manager_reference, type string

subscriptionId input parameter subscription_id, type NotificationIRPConstDefs::SubscriptionId

exceptions:

Detach

InvalidParameter

Table 5 unsubscribe


Table 4 subscribe (Cont.)

DN03317891Issue 10-1

17



Id:0900d80580942542

All operations listed in the following tables are supported by NetAct, unless otherwise stated in a footnote.

3.6.1 startSession

g This operation must be done before any of the other operations can be performed.

3.6.2 endSession

endSession operation descriptionOnce the session is closed, the information related to the session is removed from the regional database. If a download operation was performed during the session, and the plan is removed from the database, the local copy of the session log is deleted.

3.6.3 upload


sessionId BulkCmIRPConstDefs::SessionId session_id

exceptions:

StartSessionException

SessionIdInUseException

MaxSessionReachedException

InvalidParameter

Table 6 startSession



exceptions:

EndSessionException

UnknownSessionIdException

NotValidInCurrentStateException

InvalidParameter

Table 7 endSession

Information Service operation parameter Solution Set method parameter


uploadDataFileReference BulkCmIRPConstDefs::FileDestination sink

baseObjectInstance BulkCmIRPConstDefs::DistinguishedName base_object

Table 8 upload

18 DN03317891Issue 10-1


Id:0900d80580942542


Upload operation descriptionThe upload operation consists of the following phases:

1. The global NM user initiates an upload operation.2. The Regional Configurator (RC) receives the upload operation request and reads

the parameter settings in the upload operation request.3. The RC reads the actual configuration from the regional database and converts it

from NetAct object model to 3GPP NRM and writes the data to an XML file to a local working directory.

4. The generated XML file is transferred via FTP/SFTP to the location specified by the IRPManager. After the transfer is completed, the local copy of the 3GPP XML file is deleted.For instructions on how to configure SFTP, see Enabling the SFTP file transfer between NetAct and 3GPP manager in Managing NetAct System Security docu-ment.

5. The RC sends a notification, notifySessionStateChanged, about a new session state.

Upload operation scope determinationStarting from the baseObjectInstance, the scope (that is, scopeType and level) is applied.

If you require more detailed control over the object classes included in the upload file, you can use a filter. The filter is a list of 3GPP object classes (separated with spaces) that should be included in the upload.

The filter overrides the ScopeType and level parameters; only the object classes spec-ified in the filter are included in the upload. If you do not need a filter, you should give an empty filter string.

Examples:

• Uploading the whole Subnetwork:

scope, filter BulkCmIRPConstDefs::SearchControl search_control

exceptions:

UploadException




ConcurrencyException

IllegalDNFormatException

IllegalFilterFormatException

IllegalScopeTypeException

IllegalScopeLevelException

IllegalURLFormatException

InvalidParameter

Information Service operation parameter Solution Set method parameter

Table 8 upload (Cont.)

DN03317891Issue 10-1

19



Id:0900d80580942542

baseObjectInstance="SubNetwork=Nokia-1"scope=ScopeType.BaseAll, level=5filter=""

g You only need to set value for the level of ScopeTye.BaseAll, and the system will set a default value for the level of other scopes.

• Uploading only UtranCells, ExternalUtranCells and ExternalGsmCells:baseObjectInstance="SubNetwork=Nokia-1"filter="UtranCell, ExternalUtranCell, ExternalGsmCell"

g When you want to upload multiple class filter once, separate the class filters by comma.

Error situations in the upload operation

• The following errors cause the upload to fail: • An unrecoverable error happened when reading from the database. • An OMC object is missing from the database.

• In the following situations, some parameters are written to the XML file as empty: • If a target cell of an adjacency is not found from the database: parameter adja-

centCell is left empty (for UtranRelation and GsmRelation). • If there is no COCO object connected to a WBTS, the following parameters are

left empty: • NodeBFunction: nodeBFunction-iubLink • IubLink: iubLink-NodeBFunction • UtranCell: utranCell-IubLink

• If there is no Site object attached to a NetAct managed object, the parameter locationName (for Managed Element) is left empty.

• If there is no Site object attached to the OMC object, the parameter locationName (for ManagementNode) is left empty.

g Additionally, if the parameters of some object cannot be read from the database, but that does not prevent any other objects from being uploaded, the upload is not aborted. The parameters of the object in question are simply skipped, and its child objects can still be uploaded.

3.6.4 download



downloadDataFileReference

BulkCmIRPConstDefs::FileDestination sink

Table 9 download

20 DN03317891Issue 10-1


Id:0900d80580942542


Download operation descriptionTo ensure data correctness and consistency and avoid problems with file handling in a region, the global NM tool (IRPManager) has to validate the XML files against the generic 3GPP and the vendor specific data schemas provided by Nokia Siemens Networks before performing a download operation.

g If a plan with the same name already exists in the regional data repository when starting a download operation, the previous plan is deleted and a new plan is created.

The download operation consists of the following phases:

1. The global NM user initiates a download operation for plan file(s) validated against XML schemas.

2. The RC receives the download operation request and reads the parameter settings from the operation request.

3. The RC transfers the given 3GPP XML file to the region via FTP/SFTP.For instructions on how to configure SFTP, see Enabling the SFTP file transfer between NetAct and 3GPP manager in Managing NetAct System Security docu-ment.

4. The RC converts the configuration data defined in the file from the 3GPP network resource model to the NetAct object model, and saves it as a plan in the regional database.

5. Possible errors in the file are written to the session log. Only fatal errors (for instance, database not available) cause the session state to be set to DOWNLOAD_FAILED.We recommend that you check the session log before proceeding with the activa-tion, even if the state was DOWNLOAD_COMPLETED, to see that there were no problems when creating the plan in the regional database.

6. The name of the plan is written to the session log. The name is of the following format: GLOBAL _ <session ID>. For example, if the session ID is 1234, the plan name will be GLOBAL_1234.

7. After the file transfer, mapping and data storing are completed, the system sends a notification, notifySessionStateChanged, about a new session state.

After the operation is completed, the plan can be edited in the region with CM Editor, if changes are needed before activating the plan in the network. For more information on CM Editor, see CM Editor Help.

exceptions:

DownloadException





InvalidParameter


Table 9 download (Cont.)

DN03317891Issue 10-1

21



Id:0900d80580942542

Error situations in the download operationAll error situations described below are written to the session log. The log also contains information on:

• The new plan name. • The objects that are successfully saved to the plan.

Error situations:

• Reading the XML file is stopped and the status of the download operation is set to DOWNLOAD_FAILED in the following situations: • The file contains some non-relevant, excess information that cannot be read by

the XML reader. • The structure of the file is erroneous. For instance, endConfig data is called

before all objects have been closed with endManagedObject/endVSD. • An unrecoverable error occurred when reading/writing into the database. • The file format version in the file header is invalid. • The vendor specific data format version in any of the VsDataContainers is

invalid. • Invalid type of root object (not SubNetwork). • Site reading, creation or attachment failed when creating a WBTS. • Reading templates failed when saving a creation operation. • Inconsistent modifiers with the main objects and related objects. • Inconsistent referenced objects with the main objects and related objects. • Create operation for OMC (ManagementNode) or RNC. They can only be

updated via the Interface-N. • The object ID is not in the right form or it is out of range. • The controller object is not found in the regional data repository (controller object

holds the network element version information needed in creating a plan object). • In creation, the object ID already exists in the NetAct SubNetwork.

• Reading the XML file continues and the status of the download operation is set to DOWNLOAD_COMPLETED in the following situations. The erroneous object and its children are skipped. That is, they are not written in to the regional plan. • The object is in a wrong place. For instance, UtranCell is under SubNetwork. • Unknown object type. • Unknown modifier.

• In the following situations, only the object is skipped, but its children are handled nor-mally: • An unknown parameter name. • Wrong type of a parameter value. • A parameter value out of range. • A dependant parameter could not be checked. • An attempt to update read-only common parameters is made. • There is more than one operation to the same 3GPP object in the download file.

22 DN03317891Issue 10-1


Id:0900d80580942542


3.6.5 preactivate

Preactivate operation descriptionThe system performs the following steps during the preactivation:

1. The global NM user initiates the preactivation operation.2. The Regional Configurator (RC) receives the preactivation operation and reads the

parameter settings in the operation (fallbackEnabled) and saves them.3. The RC starts provisioning (NWI3 download) to the mediators in the network if pre-

activation operation was not performed before activation. All network elements included in the plan are preactivated in parallel.

4. After each network element has received a plan and completion information is received, the system automatically requests NWI3 preactivation.

5. When the preactivation is completed, the mediators send a notification to the RC about completing the preactivation operation.

6. Regional RC sends a notification, notifySessionStateChanged, to the global NM (IRPManager) about a new session state.

3.6.6 activate

Information Service operation parameter

Solution Set method parameter

sessionId

verificationMode

activationMode

fallbackEnabled

BulkCmIRPConstDefs::SessionId session_id

BulkCmIRPConstDefs::VerificationModeTypeOpt verification_mode

BulkCmIRPConstDefs::ActivationModeTypeOpt activation_mode

boolean fallback

exceptions:

PreactivateException




IllegalActivationModeException

IllegalVerificationModeException


InvalidParameter

OperationNotSupported



fallbackEnabled boolean fallback

Table 10 activate

DN03317891Issue 10-1

23



Id:0900d80580942542

Activate operation descriptionThe system performs the following steps during the activation:

1. The global NM user initiates the activation operation.2. The Regional Configurator (RC) receives the activation operation and reads the

parameter settings in the operation (saveFallback) and saves them.3. The RC starts provisioning (NWI3 download) to the mediators in the network. All

network elements included in the plan are activated in parallel.4. After each network element has received a plan and completion information is

received, the system automatically requests NWI3 activation.5. When the mediators receive the NWI3 activation operation, they first take a backup

copy of the original network configuration, and then start the plan activation in the network.

6. Non-network parameters from the plan are merged to the actual configuration in the RC database.

7. When the activation is completed, the mediators send a notification to the RC about completing the activation operation.

8. Events from network element take care of updating NetAct database so there is no need for network upload.

9. Regional RC sends a notification, notifySessionStateChanged, to the global NM (IRPManager) about a new session state.

3.6.7 fallback

exceptions:

ActivateException




IllegalActivationModeException


InvalidParameter


Table 10 activate (Cont.)



Table 11 fallback

24 DN03317891Issue 10-1


Id:0900d80580942542


Fallback operation descriptionAs with the activate operation, the Regional Configurator automatically performs a network upload to update the RC actual data configuration according to the current network situation after the fallback in WCDMA.

In WCDMA, events from RNC take care of updating NetAct database so there is no need for an automatic network upload.

The RNC supports only one fallback area, which implies that the fallback operation only applies to the latest activation operation performed on a given RNC. If another activation operation is performed after your activation, either from the global NM tool or from the region, it overrides your activation operation and you cannot perform fallback any more.

g Fallback is not supported for non-network parameters, LTE or external GSM cells. For more information on non-network parameters, see Interface-N: WCDMA (3G) Parame-ter Mapping, DN03373371.

3.6.8 abortSessionOperation

The following operations can be aborted:

• upload • download

The abort operation is not supported with Bulk CM operations activate and fallback. This is due to constraints from the network element side.

exceptions:

FallbackException


NoFallbackException



InvalidParameter


Table 11 fallback (Cont.)



exceptions:

AbortSessionOperationException



InvalidParameter

Table 12 abortSessionOperation

DN03317891Issue 10-1

25



Id:0900d80580942542

3.6.9 getSessionIds

3.6.10 getSessionStatus

3.6.11 getSessionLog

1 Not supported by NetAct.


sessionIdList BulkCmIRPConstDefs::SessionIdList

No error condition identified.

Table 13 getSessionIds



sessionState BulkCmIRPConstDefs::SessionState

status BulkCmIRPConstDefs::ErrorInformation error_information

Exceptions:

GetSessionStatusException


InvalidParameter

Table 14 getSessionStatus



logFileReference BulkCmIRPConstDefs::FileDestination sink

contentType boolean only_error_info1

exceptions:

GetSessionLogException



InvalidParameter

Table 15 getSessionLog

26 DN03317891Issue 10-1


Id:0900d80580942542


3.6.12 getBulkCmIRPVersion

3.7 Supported notifications

3.7.1 Push and Pull styleObject Management Group (OMG) Notification Service defines two styles of interaction:

• push style • pull style

NetAct only supports the push style.

3.7.2 notifySessionStateChanged


versionNumberList ManagedGenericIRPConstDefs::VersionNumberSet

No error condition identified.

Table 16 getBulkCmIRPVersion

Solution Set Attribute

OMG CORBA Structured Event Attribute

Supported by NetAct Comment

There is no correspond-ing Information Service attribute.

domain_name Yes Carries the IRP document version number string. Indi-cates the syntax and semantics of the Structured Event as defined by this document.

notificationType type_name Yes Carries the string NOTIFY_SESSION_STATE_CHANGED. In the Information Service, this is defined as a Header attribute.

Table 17 notifySessionStateChanged

DN03317891Issue 10-1

27



Id:0900d80580942542

sessionState event_name Yes Carries one of the following:

UPLOAD_FAILED

UPLOAD_COMPLETED

DOWNLOAD_FAILED

DOWNLOAD_COMPLETED

PREACTIVATION_FAILED

PREACTIVATION_PARTLY_REALISED

PREACTIVATION_COMPLETED

ACTIVATION_FAILED

ACTIVATION_PARTLY_REALISED

ACTIVATION_COMPLETED

FALLBACK_FAILED

FALLBACK_PARTLY_REALISED

FALLBACK_COMPLETED

In the case of XXX_FAILED and XXX_PARTLY_REALISED, the name-value pair indicat-ing ERROR_INFORMATIONmay be present


Variable Header

managedObjectClass, managedObjectInstance

One name-value pair of filterable_body_fields

No The order of the name-value pairs is not significant. The name and the value of a name-value pair are of the type string.

The name of a name-value pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.

See encoding of this string in [5]. These are attributes of Header defined in the Information Service.

notificationId One name-value pair of filterable_body_fields

No The name of the name-value pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.

The value of a name-value pair is of the type long. In the Information Service, this is defined as a Header attribute.

eventTime One name-value pair of filterable_body_fields

Yes The name of the name-value pair is the EVENT_TIME of interface AttributeNameValue of module NotificationIRPConstDefs.

The value of the name-value pair is IRPTime. In the Information Service, this is defined as a Header attribute.




Table 17 notifySessionStateChanged (Cont.)

28 DN03317891Issue 10-1


Id:0900d80580942542


3.7.3 notifyGetSessionLogEnded

systemDN One name-value pair of filterable_body_fields

No The name of the name-value pair is the SYSTEM_DN of interface AttributeNameValue of module NotificationIRPConstDefs.

The value of the name-value pair is a string. In the Infor-mation Service, this is defined as a Header attribute.

sessionId One name-value pair of filterable_body_fields

Yes The name of the name-value pair is the SESSION_ID of interface AttributeNameValue of module BulkCMIRPConstDefs.

The name and the value of a name-value pair are of the type string.

sourceIndicator One name-value pair of filterable_body_fields

No The name of the name-value pair is the SOURCE_INDICATOR of interface AttributeNameValue of module BulkCMIRPConstDefs.




The name of the name-value pair is the ERROR_INFORMATION of interface AttributeNameValue of module BulkCMIRPConstDefs.





Table 17 notifySessionStateChanged (Cont.)

Solution Set Attri-bute



There is no corre-sponding Informa-tion Service attribute.

domain_name Yes Carries the IRP document version number string. Indicates the syntax and semantics of the Structured Event as defined by this document.

notificationType

type_name Yes Carries the string NOTIFY_GET_SESSION_LOG_ENDED.

sessionLogStatus

event_name Yes Carries either the string GET_SESSION_LOG_COMPLETED_SUCCESSFULLY or GET_SESSION_LOG_COMPLETED_UNSUCCESSFULLY.

In the case of the latter, the name-value pair indicating ERROR_INFORMATION may be present.

There is no corre-sponding Informa-tion Service attribute

Variable Header

Table 18 notifyGetSessionLogEnded

DN03317891Issue 10-1

29



Id:0900d80580942542

managedObjectClass, managedObjectInstance


No The order of the name-value pairs is not significant. The name and the value of a name-value pair are of the type string.

The name of an name-value pair is the MANAGED_OBJECT_INSTANCE of interface AttributeNameValue of module NotificationIRPConstDefs.

See encoding of this string in [5]. These are attributes of Header defined in the Information Service.

notificationId One name-value pair of filterable_body_fields

No The name of the name-value pair is the NOTIFICATION_ID of interface AttributeNameValue of module NotificationIRPConstDefs.

The value of a name-value pair is of the type long. In the Infor-mation Service, this is defined as a Header attribute.

eventTime One name-value pair of filterable_body_fields

Yes The name of the name-value pair is the EVENT_TIME of inter-face AttributeNameValue of module NotificationIRPConstDefs.

The value of the name-value pair is IRPTime. In the Informa-tion Service, this is defined as a Header attribute.

systemDN One name-value pair of filterable_body_fields

No The name of the name-value pair is the SYSTEM_DN of inter-face AttributeNameValue of module NotificationIRPConstDefs.

The value of the name-value pair is a string. In the Information Service, this is defined as a Header attribute.

sessionId One name-value pair of filterable_body_fields

Yes The name of the name-value pair is the SESSION_ID of inter-face AttributeNameValue of module BulkCMIRPConstDefs.

The value of the name-value pair is a string.

sourceIndicator


No The name of the name-value pair is the SOURCE_INDICATOR of interface AttributeNameValue of module BulkCMIRPConstDefs.


There is no corre-sponding Informa-tion Service attribute


The name of the name-value pair is the ERROR_INFORMATION of interface AttributeNameValue of module BulkCMIRPConstDefs.


Solution Set Attri-bute



Table 18 notifyGetSessionLogEnded (Cont.)

30 DN03317891Issue 10-1


Id:0900d80580942542

NetAct Object Model RAN data

4 NetAct Object Model RAN dataThis section describes some basic information on Object Model data.

For information on the allowed object identifiers, see Managed Object Reference.

4.1 Naming conventionsThe regional Interface-N adaptation supports the naming conventions defined in the 3GPP specification 3GPP: 3GPP TS 32.300 v6.3.1 (06/2001), Name Convention for Managed Objects and 3GPP TS 32.300 v8.0.0 (12/2008) (this version is for EUTRAN NRM Part).

In the Interface-N, a distinguished name (DN) is used to identify objects.

NetAct specific object names and parameter names for common parameters are used in Regional Configurator GUI. The conversion between R6OM/ R8OM and NOM is per-formed in the Interface-N adaptation.

4.2 Associations between object modelsThe graphics in this section present the associations between the 3GPP object model and the NetAct object model.

4.2.1 Associations for management nodeThe figure below describes the associations for management node.

Figure 2 OMC management node

4.2.2 Associations for NetAct and external managed objectsThe figure below describes the associations for NetAct and external managed objects.

NetAct 3GPP

ManagementNodeOMC

SubNetworkPLMN1:1

n 1:1

= contains

1:1

0...n, n = the number of possible child objects

= one NOM object instancecorresponds to one 3GPP object instance

DN03317891Issue 10-1

31



Id:0900d80580942542

Figure 3 RNC external managed objects association

Figure 4 GSM external managed objects association

NetAct 3GPP

SubNetworkPLMN

ExternalRncFunction1:1

EXRNCF0...n

NetAct 3GPP

SubNetwork

ExternalGsmCell

PLMN

0...n1:1

BSC-0

BCF-0

BTS

(FBTS)

VsDataContainervsDataType:EGCE

1:1

32 DN03317891Issue 10-1


Id:0900d80580942542


Figure 5 Utran external managed objects association

Figure 6 LTE external managed objects association

4.2.3 Associations for NetAct WCDMA managed objectsThe figure below describes the associations for NetAct RNC managed objects.

NetAct 3GPP

SubNetwork

External UtranCell

EXCC

PLMN1:1

0...n1:1

VsDataContainervsDataType:EWCE

EWCE

1:1

PLMN SubNetwork

ExternalENBFunction

ExternalEUtranCellFDDExternalEUtranCellTDD

NetAct 3GPP

EXCENBF

EXEUCE

1:1

0...n

1:1

EXENBF

DN03317891Issue 10-1

33



Id:0900d80580942542

Figure 7 WCDMA associations (1/3)

NetAct 3GPP

0...n

0...100

1:1 1

1

SubNetwork

1:1

1:1

1:1

1:1

1:1

1:1FMCS

RNC

RncFunction

ManagedElement

ManagedElement Type: RNC

1:1

1:1

1:1

1:1

VsDataContainer

vsDataType: HOPG

VsDataContainer

vsDataType: HOPI

VsDataContainer

vsDataType: HOPS

VsDataContainer

vsDataType: FMCG

VsDataContainer

vsDataType: FMCI

VsDataContainer

vsDataType: FMCS

vsDataType: RNC

VsDataContainer

VsDataContainer

vsDataType: WSMLC

VsDataContainer

vsDataType:WLCSE

VsDataContainer

vsDataType: WANE

VsDataContainer

vsDataType: WGS

PLMN

0...1

0...4352

0...10

0...128

FMCI

FMCG

HOPS

HOPI

HOPG

WSMLC

1:1 VsDataContainer0...300IUR

vsDataType: IUR

WLCSE

WANE

WSG

34 DN03317891Issue 10-1


Id:0900d80580942542



1:1

1:1

1:1

1:1

1:10...13

0...4

0...8

0...255

0...5

NetAct

VsDataContainer

vsDataType: IUCS

VsDataContainer

vsDataType: WRAB

VsDataContainer

vsDataType: IPQM

VsDataContainer

vsDataType: TQM

VsDataContainer

vsDataType: CMOB

3GPP

1:10 ... 5 VsDataContainer

vsDataType: IUCSIP

1:10...1 VsDataContainer

vsDataType: RNMOBI


vsDataType: RNHSPA


vsDataType: RNRLC


vsDataType: RNAC

1:1

RNFC0...1 VsDataContainer

vsDataType: RNFC

RNAC

RNRLC

RNHSPA

RNMOBI

CMOB

TQM

IPQM

WRAB

IUCS

IUCSIP


vsDataType: IUPS


vsDataType: IUPSIP

IUPS

IUPSIP

DN03317891Issue 10-1

35



Id:0900d80580942542


4.2.4 Associations for NetAct WBTS managed objectsThe figure below describes the associations for NetAct WBTS managed objects.

1:1

1:10...4

0...n

NetAct

VsDataContainer

vsDataType: ADJL

VsDataContainer

vsDataType: IUO

3GPP


vsDataType: RNTRM


vsDataType: RNPS


vsDataType: CBCI

1:10...n VsDataContainer

vsDataType: HOPL

1:1

PFL0...50 VsDataContainer

vsDataType: PFL

HOPL

CBCI

RNPS

RNTRM

IUO

ADJL


vsDataType: VBTS


vsDataType: VCEL

VBTS

VCEL

36 DN03317891Issue 10-1


Id:0900d80580942542


Figure 10 WBTS associations

g The total number of NetAct child managed objects per one RNC are defined in figure Data amount example, column "Objects total".

4.2.5 Associations for WCEL managed objectsThe figure below describes the associations for WCEL managed objects.

NetAct 3GPP

RNC

0...n

0...400

0...384 1:1

1:1

ManagedElement

managedElementType: RNC

1

RncFunction

1

SubNetwork

IubLink

VsDataContainer

vsDataType: COCO

COCO

VsDataContainer

vsDataType: WBTS

1

1

ManagedElement

managedElementType: NodeB

WBTS NodeBFunction

1...65535IPNB

1

IubLink

VsDataContainer

vsDataType: IPNB

11:1

DN03317891Issue 10-1

37



Id:0900d80580942542

Figure 11 WCEL associations

4.2.6 Associations for ANTE managed objectsThe figure below describes the associations for ANTE managed objects.

NetAct 3GPP

RncFunction

0...384

1

WBTS

VsDataContainer

vsDataType: WCEL

0...32

0...48

0...3

0...31

UtranCell1:1

1:1

1:1

1

1

1

UtranRelation

VsDataContainer

vsDataType: ADJS

WCEL

GsmRelation

VsDataContainer

vsDataType: ADJG

UtranRelation

VsDataContainer

vsDataType: ADJI

1:1

ADJG

ADJI

ADJS

1:11

UtranRelation

VsDataContainer

vsDataType: ADJD

ADJD0...31

0...n 1:1 VsDataContainer

vsDataType: ADJL

ADJL

38 DN03317891Issue 10-1


Id:0900d80580942542


Figure 12 ANTE associations

4.2.7 Associations for OMS managed objects The figure below describes the associations for OMS managed objects.

Figure 13 OMS associations

4.2.8 Associations for NetAct MRBTS (LTE eNB) managed objects in RL15/RL20

4.2.8.1 Associations for MRBTS managed objects The figure below describes the associations for MRBTS managed objects.

NetAct 3GPP

0...n

0...n

1:1

1

SubNetwork

1:1

1:1

ANTE

ManagedElement

managedElementType: ANTE

GCAL

PLMN

0...n

ANTC

1

WCAL

vsDataType: ANTE

VsDataContainer

VsDataContainer

vsDataType: GCAL

Antenna

VsDataContainer

vsDataType: WCAL

1:10...nEUCAL VsDataContainer

vsDataType: EUCAL

PLMN SubNetwork

ManagedNode

VsDataContainerVsDataType: PREBTS

1:1

NetAct 3GPP

OMS

VsDataContainerVsDataType: OMS

PREBTS1:1

0...n

DN03317891Issue 10-1

39



Id:0900d80580942542

Figure 14 MRBTS associations for RL15/RL20

4.2.8.2 Associations for LNBTS managed objects The figure below describes the associations for LNBTS managed objects.

PLMN

MRBTS

SubNetwork

ManagedElementType:MRBTSManagedElement

VsDataContainerVsDataType: MRBTS

VsDataContainerVsDataType: MHA

VsDataContainerVsDataType: LNBTS

VsDataContainerVsDataType: LCELL

VsDataContainerVsDataType: BTSSCL

VsDataContainerVsDataType: ANTL

ANTL

BTSSCL

LCELL

LNBTS*

MHA

0...n

1...1

0...12

1...1

0...255 1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: RET

VsDataContainerVsDataType: RMODRMOD

RET0...255

1:1

1:1

VsDataContainerVsDataType: SMOD

1...18

1...3

SMOD1:11...2

ENBFunction

1:1

40 DN03317891Issue 10-1


Id:0900d80580942542


Figure 15 LNBTS associations for RL15/RL20

g The object which has “*” behind its name in the figure means this object has child objects, but these child objects are not drawn in this figure.

4.2.8.3 Associations for FTM managed objects The figure below describes the associations for FTM managed objects.

PLMN

MRBTS*

LNBTS

SubNetwork

ENBFunction




VsDataContainerVsDataType: LNADJL

VsDataContainerVsDataType: LNADJ

VsDataContainerVsDataType: GTPU

VsDataContainerVsDataType: FTM

VsDataContainerVsDataType: MTRACE

VsDataContainerVsDataType: CTRLTS

VsDataContainerVsDataType: ADIPNO

ADIPNO

CTRLTS

MTRACE

FTM*

GTPU

LNADJ

LNADJL

0...n

0...1

0...6

1...1

0...1

0...64

0...6

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: LNADLP

VsDataContainerVsDataType: LNCEL

VsDataContainerVsDataType: LNMME

VsDataContainerVsDataType: ITRACE

ITRACE

LNMME

LNADLP0...16

1:1

1:1

1:1

1:1

VsDataContainerVsDataType: SCTPSCTP

0...1 1:1

1...1

1...1

0...32

0...32

LNCEL*1:11...6 EUtranCellFDD/

EUtranCellTDD

EUtranRelation

DN03317891Issue 10-1

41



Id:0900d80580942542

Figure 16 FTM associations for RL15/RL20

g The object which has “*” behind its name in the figure means this object has child objects, but these child objects are not drawn in this figure.

4.2.8.4 Associations for IPNO managed objects The figure below describes the associations for IPNO managed objects.

PLMN

MRBTS*

LNBTS*

SubNetwork

ENBFunction




VsDataContainerVsDataType: AMGR


FTM

AMGR

1...1

1...1

1:1

1:1

NetAct 3GPP

1...1

1...1

VsDataContainerVsDataType: CERTH

CERTH1...1 1:1

VsDataContainerVsDataType: ETHLK

ETHLK1...4 1:1

VsDataContainerVsDataType: IPNO

IPNO*1:1

VsDataContainerVsDataType: IPSECC

IPSECC1:1

VsDataContainerVsDataType: L2SWI

L2SWI1:1

VsDataContainer

VsDataType: OAMMDOAMMD

1:1

VsDataContainerVsDataType: OAMMA

OAMMA

0...151:1

VsDataContainerVsDataType: OAMMEP

OAMMEP0...1 1:1

VsDataContainerVsDataType: OAMPRF

OAMPRF0...5 1:1

VsDataContainerVsDataType: PMTNL

PMTNL1...1 1:1

VsDataContainerVsDataType: PPTT

PPTT1...4 1:1

VsDataContainerVsDataType: SYNC

SYNC1...1 1:1

VsDataContainerVsDataType:UNITUNIT

1...1 1:1

STPG1:1 VsDataContainer

VsDataType: STPG

1...1

1...1

1...1

1...1

1...10

42 DN03317891Issue 10-1


Id:0900d80580942542


Figure 17 IPNO associations for RL15/RL20

4.2.8.5 Associations for LNCEL managed objects The figure below describes the associations for LNCEL managed objects.

PLMN

MRBTS*

LNBTS*

FTM*

SubNetwork

ENBFunction





VsDataContainer

VsDataContainerVsDataType: QOS

VsDataContainerVsDataType: IPRT

VsDataContainerVsDataType: IPRM

VsDataContainerVsDataType: INTP

VsDataContainerVsDataType: IHCP

VsDataContainerVsDataType: IVIF

VsDataContainerIEIF

IVIF

IHCP

INTP

IPRM

IPRT

QOS

TOPIK

0...n

1...1

1...1

1...1

0...5

1...1

1...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

IPNO

1...1VsDataContainer

VsDataType: IPNO1:1

1...1

1...1

1...1

1...1

VsDataType: IEIF

VsDataType: TOPIK

DN03317891Issue 10-1

43



Id:0900d80580942542

Figure 18 LNCEL associations for RL15/20

4.2.9 Associations for NetAct MRBTS (LTE eNB) managed objects in RL25/RL30The graphics in this section present the associations between the 3GPP object model and the NetAct object model in RL25/RL30.

g The object which has “*” behind its name in the figure means this object has child objects, but these child objects are not drawn in the figure.


PLMN

MRBTS*

LNBTS*

LNCEL

SubNetwork

ENBFunction






VsDataContainerVsDataType: UFFIM

VsDataContainerVsDataType: REDRT

VsDataContainerVsDataType: LNHOIF

VsDataContainerVsDataType: IRFIM

VsDataContainerVsDataType: IAFIM

VsDataContainerVsDataType: GNFL

VsDataContainerVsDataType: GFIM

VsDataContainerVsDataType: CDFIM

CDFIM

GFIM

GNFL

IAFIM

IRFIM

LNHOIF

REDRT

UFFIM

0...n

1...1

1...6

0...1

0...1

0...16

0...1

0...5

0...16

0...6

0...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

EUtranCellFDD

EUtranCellTDD

44 DN03317891Issue 10-1


Id:0900d80580942542


Figure 19 MRBTS associations for RL25/RL30


PLMN

MRBTS

SubNetwork








ANTL

BTSSCL

LCELL

LNBTS*

MHA

0...n

1...1

0...13

1...1

0...255 1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: CREL


VsDataContainerVsDataType: RMOD

VsDataContainerVsDataType: ECREL

ECREL

RMOD

RET

CREL

0...255

1:1

1:1

1:1

1:1


1...18

1...3

SMOD1:11...3

0...255

ENBFunction

0...255

1:1

DN03317891Issue 10-1

45



Id:0900d80580942542

Figure 20 LNBTS for RL25/RL30 associations


PLMN

MRBTS*

LNBTS

SubNetwork

ENBFunction









ADIPNO

CTRLTS

MTRACE

FTM*

GTPU

0...n

0...1

0...6

1...1

0...1 1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: MODRED

VsDataContainerVsDataType: MODPR


VsDataContainerVsDataType: LNADJW

VsDataContainerVsDataType: LNADJG

LNADJG

LNADJW

LNMME

MODPR

MODRED

MOPR

0...16

0...1

0...8

1:1

1:1

1:1

1:1

1:1

1:1

VsDataContainerVsDataType: SCTP

VsDataContainerVsDataType: PMRNL

VsDataContainerVsDataType: MORED

VsDataContainerVsDataType: MOPR

MORED

PMRNL

SCTP

0...6

0...1

0...1

1:1

1:1

1:1

1...1

1...1

0...32

0...32

0...6



LNADJ

LNADJL

0...64

0...6

1:1

1:1


1:1


EUtranCellTDD

EUtranRelation

46 DN03317891Issue 10-1


Id:0900d80580942542


Figure 21 FTM associations for RL25/RL30

g OAMMD, OAMMA, OAMMEP, OAMPRF, PMTNL, TAC and LTAC are not supported in LNT2.0.


PLMN

MRBTS*

LNBTS*

SubNetwork

ENBFunction






FTM

AMGR

1...1

1...1

1:1

1:1

NetAct 3GPP

1...1

1...1


CERTH1...1 1:1


ETHLK1...4 1:1


IPNO*1:1


IPSECC1:1


L2SWI1:1

VsDataContainer


1:1

VsDataContainerVsDataType: OAMMA

OAMMA

0...151:1

VsDataContainerVsDataType: OAMMEP

OAMMEP0...1 1:1

VsDataContainerVsDataType: OAMPRF

OAMPRF0...5 1:1

VsDataContainerVsDataType: PMTNL

PMTNL1...1 1:1

VsDataContainerVsDataType: PPTT

PPTT1...4 1:1


SYNC1...1 1:1


1...1 1:1


VsDataType: STPG

1...1

VsDataContainerVsDataType: TAC

TAC1...1 1:1

LTAC1:1 VsDataContainer

VsDataType: LTAC

1...1

1...1

1...1

1...1

1...10

DN03317891Issue 10-1

47



Id:0900d80580942542

Figure 22 IPNO associations for RL25/RL30

g BFD, BFDGRP and TWAMP are not supported in LNT2.0.

TOPIK is not supported in LNT2.0 and LN4.0.


PLMN

MRBTS*

LNBTS*

FTM*

SubNetwork

ENBFunction





VsDataContainerVsDataType: TWAMP

VsDataContainer






VsDataContainerVsDataType: IDNS

VsDataContainerVsDataType: BFDGRP


VsDataContainer

VsDataContainerVsDataType: BFD

BFD

IEIF

IVIF

BFDGRP

IDNS

IHCP

INTP

IPRM

IPRT

QOS

TOPIK

TWAMP

0...n

1...1

1...1

0...2

1...1

0...5

8...8

1...1

1...1

1...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

IPNO


VsDataType: IPNO1:1

1...1

1...1

1...1

1...1

0...10

VsDataType: IEIF

VsDataType: TOPIK

48 DN03317891Issue 10-1


Id:0900d80580942542


Figure 23 LNCEL associations for RL25/RL30

g CDFIM is not supported in TDD.

4.2.10 Associations for NetAct MRBTS (LTE eNB) managed objects in RL40The graphics in this section present the associations between the 3GPP object model and the NetAct object model in RL40.

g The object which has “*” behind its name in the figure means this object has child objects, but these child objects are not drawn in the figure.

PLMN

MRBTS*

LNBTS*

LNCEL

SubNetwork

ENBFunction








VsDataContainerVsDataType: LNRELW

VsDataContainerVsDataType: LNRELG

VsDataContainerVsDataType: LNREL

VsDataContainerVsDataType: LNHOW


VsDataContainerVsDataType: LNHOG






CDFIM

GFIM

GNFL

IAFIM

IRFIM

LNHOG

LNHOIF

LNHOW

LNREL

LNRELG

LNRELW

REDRT

UFFIM

0...n

1...1

1...6

0...1

0...1

0...16

0...1

0...5

0...6

0...16

0...16

0...389

0...256

0...256

0...6

0...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:11:1

1:1

1:1

NetAct 3GPP

EUtranCellFDD

EUtranCellTDD

DN03317891Issue 10-1

49



Id:0900d80580942542


Figure 24 MRBTS associations for RL40


PLMN

MRBTS

SubNetwork








ANTL

BTSSCL

LCELL

LNBTS*

MHA

0...n

1...1

0...12

1...1

0...255 1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: CREL


VsDataContainerVsDataType: RMOD

VsDataContainerVsDataType: ECREL

ECREL

RMOD

RET

CREL

0...255

1:1

1:1

1:1

1:1


1...18

1...3

SMOD1:11...2

0...255

ENBFunction

0...255

1:1

50 DN03317891Issue 10-1


Id:0900d80580942542


Figure 25 LNBTS for RL40 associations


PLMN

MRBTS*

LNBTS

SubNetwork

ENBFunction









ADIPNO

CTRLTS

MTRACE

FTM*

GTPU

0...n

0...1

0...6

1...1

0...1 1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

VsDataContainerVsDataType: MODRED

VsDataContainerVsDataType: MODPR


VsDataContainerVsDataType: LNADJW

VsDataContainerVsDataType: LNADJG

LNADJG

LNADJW

LNMME

MODPR

MODRED

MOPR

0...16

0...1

0...8

1:1

1:1

1:1

1:1

1:1

1:1

VsDataContainerVsDataType: SCTP

VsDataContainerVsDataType: PMRNL

VsDataContainerVsDataType: MORED

VsDataContainerVsDataType: MOPR

MORED

PMRNL

SCTP

0...6

0...1

0...1

1:1

1:1

1:1

1...1

1...1

0...32

0...32

0...6



LNADJ

LNADJL

0...64

0...6

1:1

1:1


1:1


EUtranCellTDD

EUtranRelation

DN03317891Issue 10-1

51



Id:0900d80580942542

Figure 26 FTM associations for RL40

g OAMMD, OAMMA, OAMMEP, OAMPRF, PMTNL, TAC and LTAC are not supported in LNT2.0.

TOPB, TOPF and TOPP are only supported in LN4.0.

PLMN

MRBTS*

LNBTS*

SubNetwork

ENBFunction






FTM

AMGR

1...1

1...1

1:1

1:1

NetAct 3GPP

1...1

1...1


CERTH1...1 1:1


ETHLK1...4 1:1


IPNO*1:1


IPSECC1:1


L2SWI1:1

VsDataContainer


1:1

VsDataContainerVsDataType: OAMMAOAMMA

0...151:1

VsDataContainerVsDataType: OAMMEPOAMMEP0...1 1:1

VsDataContainerVsDataType: OAMPRFOAMPRF

0...5 1:1

VsDataContainerVsDataType: PMTNLPMTNL

1...1 1:1

VsDataContainerVsDataType: PPTTPPTT

1...4 1:1


SYNC1...1 1:1


1...1 1:1


VsDataType: STPG

1...1

VsDataContainerVsDataType: TAC

TAC1...1 1:1

LTAC1:1 VsDataContainer

VsDataType: LTAC

1...1

VsDataContainerVsDataType: TOPB

TOPB1...1 1:1

TOPF1:1 VsDataContainer

VsDataType: TOPF

1...1

TOPP1:1 VsDataContainer

VsDataTYpe: TOPP

1...1

1...1

1...1

1...1

1...10

52 DN03317891Issue 10-1


Id:0900d80580942542



Figure 27 IPNO associations for RL40

g BFD, BFDGRP and TWAMP are not supported in LNT2.0.

TOPIK is not supported in LNT2.0 and LN4.0.


PLMN

MRBTS*

LNBTS*

FTM*

SubNetwork

ENBFunction





VsDataContainerVsDataType: TWAMP

VsDataContainer






VsDataContainerVsDataType: IDNS

VsDataContainerVsDataType: BFDGRP


VsDataContainer

VsDataContainerVsDataType: BFD

BFD

IEIF

IVIF

BFDGRP

IDNS

IHCP

INTP

IPRM

IPRT

QOS

TOPIK

TWAMP

0...n

1...1

1...1

0...2

1...1

0...5

8...8

1...1

1...1

1...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

IPNO


VsDataType: IPNO1:1

1...1

1...1

1...1

1...1

0...10

VsDataType: IEIF

VsDataType: TOPIK

DN03317891Issue 10-1

53



Id:0900d80580942542

Figure 28 LNCEL associations for RL40

g CDFIM is not supported in TDD.

LNHOT and LNRELT are not supported in FDD.

4.3 Data amountsThe example case below describes data amounts for one RNC and the maximum number of child objects below it.

PLMN

MRBTS*

LNBTS*

LNCEL

SubNetwork

ENBFunction








VsDataContainerVsDataType: LNRELW

VsDataContainerVsDataType: LNRELT

VsDataContainerVsDataType: LNRELG

VsDataContainerVsDataType: LNREL

VsDataContainerVsDataType: LNHOW

VsDataContainerVsDataType: LNHOT


VsDataContainerVsDataType: LNHOG






CDFIM

GFIM

GNFL

IAFIM

IRFIM

LNHOG

LNHOIF

LNHOT

LNHOW

LNREL

LNRELG

LNRELT

LNRELW

REDRT

UFFIM

0...n

1...1

1...6

0...1

0...1

0...16

0...1

0...5

0...6

0...16

0...16

0...389

0...256

0...256

0...6

0...1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

1:1

NetAct 3GPP

EUtranCellFDD

EUtranCellTDD

0...16

0...256

54 DN03317891Issue 10-1


Id:0900d80580942542


g External cells and other non-network objects are not included in this table.

Figure 29 Data amount example

Below is another example describes data amounts for one LTE and the maximum number of objects.

Object Number of object/ parent object

parameters/object

MRBTS 1 7

LNBTS 1 119

LNCEL 3 263

Table 19 Data amount example for LTE

RNC

WBTS

WCEL

ADJS

ADJI

ADJG

FMCS

FMCI

FMCG

HOPS

HOPI

HOPG

COCO

Object

Lines in an XML file (one line per parameter):Characters per line (average):Bytes per line:

25640854040

File size in megabytes 103

Total XML file size 102563400

1

384

3

31

48

32

100

100

100

400

1

4352

10

128

Number of objects/ parent object

Objectstotal

Parameters/ object

Parameterstotal

518

18816

198144

607104

995328

552960

2300

1800

1000

30400

5

147968

90

1152

1700

Objects total: 134900

PARAMETERS TOTAL: 2564085

WSMLC

WLCSE

WANE

WSG

100

100

100

1

384

1152

35712

55296

36864

100

100

100

400

1

4352

10

128

100

100

100

518

49

172

17

18

15

23

24

24

18

17

10

76

5

34

9

9

2400

2400

DN03317891Issue 10-1

55



Id:0900d80580942542

LNADJ 32 11

LNADJL 3 16

Object Number of object/ parent object

parameters/object

Table 19 Data amount example for LTE (Cont.)

56 DN03317891Issue 10-1


Id:0900d80580942542

OSS5.x - 3GPP R6 object model mapping for WCDMA

5 OSS5.x - 3GPP R6 object model mapping for WCDMAThis section describes the instance mappings between NetAct Object Model (NOM) and 3GPP R6 Object Model (R6OM).

5.1 Examples of instance mappingsThis section describes examples of instance mappings.

In the column titled "Mapping" of the following table, different fonts are used for the attri-butes of the 3GPP model and the attributes of the NetAct model.

Object class Mapping NetAct DN 3GPP DN Notes

OMC subNetworkId="Nokia"+ clusterId (NmsId)

PLMN-PLMN/OMC-1

SubNetwork=Nokia-1

dnPrefix can be set to NULL, since in this case the SubNetwork is not the "root of the local MIB" (PLMN is the "root of the local MIB").

OMC managementNodeId=omcRDN

PLMN-PLMN/OMC-1

SubNetwork=Nokia-1, Management-Node=OMC-1

RNC managedElementId=rncFunctionId=rncRDN

PLMN-PLMN/RNC-3

SubNetwork=Nokia-1, ManagedEle-ment=RNC-3

Attribute rncId shall be set to rncRDN.

WBTS managedElementId=nodeBFunctionId=rncRDN + "I" + wbtsRDN

PLMN-PLMN/RNC-3/WBTS-4

SubNetwork=Nokia-1, ManagedEle-ment=RNC-3/WBTS-4, NodeB-Function=RNC-3/WBTS-4

NodeBFunctionId must be unique sub-network wide as it is not under RNC in the 3GPP model.

The RNC identity needs to be carried in nodeB and nodeBFunction RDN, otherwise the reverse mapping is not possible.

WCEL utranCellId=wbtsRDN + "I" + wcelRDN

PLMN-PLMN/RNC-3/WBTS-4/WCEL-5

SubNetwork=Nokia-1, ManagedEle-ment=RNC-3, Rnc-Function=RNC-3, UtranCell=WBTS-4/WCEL-5

The WBTS identity needs to be carried in UtranCell RDN, otherwise the reverse mapping is not possible.

wcelRDN=WCEL-"LcrId"

(LcrId=localCellId)

Table 20 Examples of instance mappings

DN03317891Issue 10-1

57



Id:0900d80580942542

ADJS utranCellId=wbtsRDN + "I" + wcelRDN, utranRelationId=adjsRDN

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJS-1

SubNetwork=Nokia-1, ManagedEle-ment=RNC-1,

RncFunction=RNC-1, UtranCell=WBTS-1/WCEL-1, UtranRe-lation=ADJS-1

utranCellId must also carry the infor-mation of the parent WBTS as it is not under NodeBFunc-tion in the 3GPP model.

Object class name prefixes used in UtranRelation and GsmRelation identifiers in R6OM to separate the relation type in NOM.

ADJI utranCellId=wbtsRDN +"I" + wcelRDN, utranRelationId=adjiRDN

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJI-1

SubNetwork=Nokia-1, ManagedEle-ment=RNC-1, Rnc-Function=RNC-1, UtranCell=WBTS-1/WCEL-1, UtranRe-lation=ADJI-1

utranCellId must also carry the infor-mation of the parent WBTS as it is not under NodeBFunction in the 3GPP model.


ADJG utranCellId=wbtsRDN + "I" + wcelRDN, gsmRelationId=adjgRDN

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJG-1

SubNetwork=Nokia-1, ManagedEle-ment=RNC-1, Rnc-Function=RNC-1, UtranCell=WBTS-1/WCEL-1, GsmRe-lation=ADJG-1

utranCellId must also carry the infor-mation of the parent WBTS as it is not under NodeBFunction in 3GPP model.


COCO IubLinkId=cocoRDN PLMN-PLMN/RNC-1/COCO-1

SubNetwork=Nokia-1,

ManagedEle-ment=RNC-1, Rnc-Function=RNC-1, IubLink=COCO-1

COCO is only existed in RNC.


Table 20 Examples of instance mappings (Cont.)

58 DN03317891Issue 10-1


Id:0900d80580942542


IPNB IubLinkId=IPNBRDN PLMN-PLMN/RNC-1/IPNB-1

SubNetwork=Nokia-1,

ManagedEle-ment=RNC-1, Rnc-Function=RNC-1, IubLink=IPNB-1

EXCC PLMN-PLMN/EXCC-1

No mapping, con-ceptual object only

EWCE externalUtranCellId=ewceRDN

PLMN-PLMN/EXCC-1/EWCE-1234

SubNetwork=Nokia-1, ExternalUtran-Cell=EWCE-1234

It is not necessary to carry ExccId in the 3GPP DN.

Operators can define the EWCE instance number but the requirement is that the identification has to be unique in the subNetwork. The maximum character number is 10.

BTS (FBTS)

externalGsmCellId=egceRDN

PLMN-PLMN/BSC-0/BCF-0/BTS-123 321

SubNetwork=Nokia-1, ExternalGsm-Cell=EGCE-123 321


Note: currently FBTS (foreign BTS) is used but it will be replaced with EGCE in the future NetAct/Con-figurator releases.

The EGCE/BTS identification has to include real cell LAC (5 digits) and Cell ID (5 digits) information, that is, the first 5 digits are reserved for LAC and the next 5 digits for cell ID. (Empty spaces left after the LAC digits if all 5 digits are not used, for instance, EGCE-123 321)

ANTE managementElementId=AnteFunctionId=anteRDN

PLMN-PLMN/ANTC-1/ANTE-1

SubNetwork=Nokia-1, ManagedEle-ment=ANTC-1/ ANTE -1, Antenna=ANTE-1, vsDataCon-tainer=ANTE-1

In IOC (32.642-3) 3GPP specifications the name is Anten-naFunction, but in Schema (32.645) the name is Antenna.



DN03317891Issue 10-1

59



Id:0900d80580942542

Notes about the mappings

• Embedding objects NetAct distinguished names (DNs) into the object instances used in 3GPP DN: some operations like object creation require that knowledge of NetAct internal hierarchy is present in 3GPP DNs, otherwise the object's place in the NetAct hierarchy cannot be determined.

• PLMN is only a conceptual root object in the NetAct model and therefore has no mapping.

• In all mappings involving ManagedElement, its dnPrefix can be set to NULL. • Objects like MeContext in R6OM is not taken into account in the mapping. It is not

used in the NetAct model.

Notes about the attribute value formats (attributes that are affected by the map-pings):

• The ManagementNode attribute manages is set to the 3GPP DN of the managed ManagedElement(s). The content of 3GPP DN must include the NetAct topology.SubNetwork=Nokia-1,ManagedElement=RNC-3SubNetwork=Nokia-1,ManagedElement=RNC-3/WBTS-4

• The ManagedElement attribute managedBy is set to the 3GPP DN of the control-ling OMC.

• The NodeBFunction attribute nodeBFunctionIubLink is set to the 3GPP DN of the relating IubLink.

• The IubLink attribute IubLinkUtranCell is set to the 3GPP DN of the relating UtranCell(s). The content of the 3GPP DN has to include the NetAct topology.SubNetwork=Nokia-1,ManagedElement=RNC-3,RncFunction=RNC-1,UtranCell=WBTS-1/WCEL-1

• The IubLink attribute IubLinkNodeBFunction is set to the 3GPP DN of the relating nodeBFunction. The content of the 3GPP DN must include the NetAct topology.SubNetwork=Nokia-1,ManagedElement=RNC-3/WBTS-4

• The UtranCell attribute UtranCellIubLink is set to the 3GPP DN of the relating IubLink.

-- irpAgentId= systemId of OMC

-- SubNetwork=Nokia-1, Management-Node=OMC-1, IRPAgent=Nokia-1

NetAct does not have a correspond-ing object.

ADJD utranCellId=wbtsRDN +"I" + wcelRDN, utranRelationId=adjdRDN

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJD-1

SubNetwork=Nokia-1,ManagedEle-ment=RNC-1,Rnc-Function=RNC-1,UtranCell=WBTS-1/WCEL-1,UtranRe-lation=ADJD-1



60 DN03317891Issue 10-1


Id:0900d80580942542


• The UtranRelation attribute adjacentCell is set to the 3GPP DN of the target cell. The content of the 3GPP DN must include the NetAct topology.SubNetwork=Nokia-1,ManagedElement=RNC-2,RncFunction=RNC-2,UtranCell=WBTS-3/WCEL-4SubNetwork=Nokia-1,ExternalUtranCell=EWCE-2

• The GsmRelation attribute adjacentCell must be set to the 3GPP DN of the target cell.

5.1.1 Considerations in CM data upload (NetAct model → 3GPP model)During the upload of a NOM object:

• OMC: mapped to two common R6OM objects: ManagementNode and Subnetwork. The same NOM, OMCId (NmsId), is used in RDN for both R6OM objects.

• RNC: divided to two different common R6OM objects: Managed element: Rnc and RncFunction. The same NOM, rncId, is used in RDN for both R6OM objects.

• WBTS: divided to two different common R6OM objects: Managed element: nodeB and nodeBFunction. The same NOM, WBTSId, is used in RDN for both R6OM objects.

• ANTE: divided to two different common R6OM objects: Managed element: ANTE and Antenna(Function). The same NOM, ANTEId, is used in RDN for both R6OM objects.

All of R6OM objects can be separately requested to upload: upload is done based on the upload scope. The relevant attributes have to be uploaded for each R6OM object:

• Common attributes specified in the 3GPP R6 specifications for each object. • The NOM vendor-specific attributes for common objects are provided in

vsDataContainer.

The following parameters can have wrong values due to range differences between NetAct and 3GPP:

• UtranCell/WCEL: • Parameter Name: maximumTransmissionPower/ PtxDLabsMax

3GPP range: 0..50; NetAct range: -10..50 • Antenna/ANTE:

• Parameter name: MechanicalOffset/tilt 3GPP range: 0..360; NetAct range: -90 to 90

• Parameter name: Height/height 3GPP range: 0.. 36000000; NetAct range: -1000..1000 m

5.1.2 Considerations in CM data download (3GPP model → NetAct model)During the download of R6OM objects:

• ManagementNode and Subnetwork combined in one NOM object: OMC, which holds all ManagementNode and Subnetwork attributes in the NOM.

• Managed element: ANTE and antenna(Function) combined in one NOM object: ANTE. That is, all R6OM ManagedElement:ANTE and antenna(Function) attributes are mapped to be attributes of ANTE in NOM.

DN03317891Issue 10-1

61



Id:0900d80580942542

• ManagedElement: Rnc and RncFunction combined in one NOM object: RNC. That is, all R6OM Rnc and RncFunction attributes are mapped to be attributes of RNC in NOM.

• Managed element: nodeB and nodeBFunction combined in one NOM object: WBTS. That is, all R6OM NodeB and nodeBFunction attributes are mapped to be attributes of WBTS in NOM.

• The NOM vendor-specific attributes for common objects are provided in vsDataContainer.

g All the rules above have to be taken into account when operating over the Interface-N. Otherwise the download process fails.

Special requirements for the NOM RNC creation:

• A NOM RNC cannot be created via Interface-N: it is always created via the network, that is, uploaded from the network to the regional network element manager.

Special requirements for the NOM WBTS creation:

• ManagedElementNodeB and nodeBFunction creation: the same ID (in NOM: <WBTSId>) must be used for both objects (1:1 relation).

• The content of the R6OM nodeBFunction ID in the Interface-N DN must include the identity of the RNCFunction to which the NodeBFunction is connected via its associated IubLink. It also has to be of the following format: RNC-<rncFunctionId>/WBTS-<nodeBFunctionId>.

Special requirements for the NOM WCEL creation:

• The ID (in NOM: <LcrId>) has to be unique under the associated NodeBFunction (NOM: WBTS) or, rather, under the network.

• The content of the R6OM utranCell ID in the Interface-N DN must include the identity of the nodeBFunction to which the utranCell is connected via its associ-ated IubLink. It also has to be of the following format: WBTS-<nodeBFunctionId>/WCEL-<utranCellId>.

• Parameters that are mandatory in an object creation in the Regional Configurator database, are introduced in Mandatory WCDMA Parameters in Creating BTS Sites.

g The object creation via the Interface-N has to be done in the NOM order: parent object first - then child objects. That is: WBTS - WCEL - adjacencies.

Special requirements for the object rehosting:

• When a NOM WBTS is rehosted under another RNC, its identity will not remain the same in the Interface-N, because its ID contains the parent RNC’s ID, for instance, RNC-<RncFunctionId>/WBTS-<nodeBFunctionId>.

• Therefore, the WBTS rehosting requires a delete-create scenario. • The same applies also to NOM WCEL (UtranCell). • Since the ExternalGsmCell ID contains ExternalGsmCell LAC parameter, the

ID changes in rehosting, if the ExternalGsmCell LAC parameter is changed. • Therefore, the ExternalGsmCell rehosting requires a delete-create scenario.

Special requirements for the object deletion:

• When the main object deletion is included in a plan, the deletion for all related objects has to be included in the same plan in order to keep the NOM consistent.

62 DN03317891Issue 10-1


Id:0900d80580942542


For instance, if a nodeB is deleted, also the related nodeBFunction has to be deleted from the same plan.

• Related objects cannot be deleted separately (in NOM or over the Interface-N). For instance, nodeBFunction cannot be deleted separately.

• If an UtranCell, ExternalUtranCell or ExternalGsmCell is deleted, all incoming UtranRelations and GsmRelations are automatically deleted as well.

• The object deletion via the Interface-N has to be done in the NOM order: child objects first - then the parent object. That is, adjacencies - WCEL - WBTS.

g R6OM object VsDataContainer as well can include creation, update or deletion commands for vendor-specific objects.

5.2 Vendor-specific objects and parametersVendor-specific data is specific for bulk configuration management.

NOM vendor-specific objects and vendor-specific data of the common objects are pre-sented in R6OM (in the Interface-N) by using VsDataContainers as shown in the figure below.

Figure 30 NOM vendor-specific objects and vendor-specific data

Nestings of VsDataContainers are not used in the NOM (in UMTS).

NetAct Object Model (NOM) has the following vendor-specific objects in UMTS:

• FMCG • FMCI • FMCS • HOPG • HOPI • HOPS • WSMLC • WLCSE • WANE • WSG • WCAL • GCAL • EUCAL

MOC

0...n

VsDataContainer(from the generic model)

= contains

0...n, 0...1 = the number of possible child objects

DN03317891Issue 10-1

63



Id:0900d80580942542

In the NOM, there are also some transmission objects, such as AXC, IMAG and PORT that are not related to bulk CM in the Interface-N and are not supported. The object NEMU is not supported due to restrictions in 3GPP specifications.

The following graphic presents the containment for Frequency Measurement Control (FMCx) objects in the Interface-N, as well as the maximum instance numbers.

Figure 31 Containment for Frequency Measurement Control Objects

The following graphic presents the containment for Handover path (HOPx) objects in the Interface-N, as well as the maximum instance numbers.

Figure 32 Containment for Handover path objects

The following graphic presents the containment for Location Services -related objects in the Interface-N, as well as the maximum instance numbers.

RncFunction

FMCS

1

FMCG

0...100 0...100 0...100

11

FMCI

= contains

1, 0...x = the number of possible child objects

RncFunction

HOPS

1

HOPG

0...100 0...100 0...100

11

= contains


HOPI

64 DN03317891Issue 10-1


Id:0900d80580942542


Figure 33 Containment for Location Services -related objects

The following graphic presents the containment for IMSI based HO -related objects in the Interface-N, as well as the maximum instance numbers.

Figure 34 Containment for IMSI based HO -related objects

The following common NOM objects, which have a corresponding object in R6OM, have a vendor-specific extension in R6OM:

• ADJG • ADJI • ADJS • COCO • RNC • WBTS • WCEL • ANTE

In addition, the following NOM objects have a NetAct-specific vsDataContainer exten-sion in R6OM in order to support mandatory adjacency parameters (the extension is not specified in the 3GPP specifications):

• BTS (FBTS) • EWCE

RncFunction

1

1

WSMLC

= contains


1

WLCSE

0...4352

RncFunction

1

0...10

WANE

= contains


1

WSG

0...128

DN03317891Issue 10-1

65



Id:0900d80580942542

All of the NOM objects mentioned above always have one vsDataContainer instance per corresponding R6OM object in the Interface-N.

Special case: ExternalRncFunction - which maps to NOM RNC parameter IurItem - always has one VsDataContainer instance.

The identification of the vendor-specific objects and vendor-specific data of the common objects is performed by using vsDataContainerId in the R6OM (in the Interface-N XML files). The vsDataContainerId is formulated by using a combination of the NOM object name and the NOM identifier, for instance:

• NOM HOPSId="1" (vendor-specific object) corresponds to vsDataContainerId="HOPS-1" (in R6OM / in the Interface-N)

• NOM WCELId="12345" (vendor-specific part of a common object UtranCell) corre-sponds to vsDataContainerId="WCEL-12345" (in R6OM / in the Interface-N).

NetAct UTRAN vendor-specific object/data mappings


ADJG 1 vsDataContainerId=adjgRDN, vsDataType=ADJG

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJG-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RncFunc-tion=RNC-1, UtranCell=WBTS-1/WCEL-1, VsDataCon-tainer=ADJG-1

The NetAct-specific param-eters cannot be carried in 3GPP's GsmRelation object, but a separate vendor-specific object is needed.

ADJI 1 vsDataContainerId=adjiRDN, vsDataType=ADJI

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJI-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RncFunc-tion=RNC-1, UtranCell=WBTS-1/WCEL-1, VsDataCon-tainer=ADJI-1

The NetAct-specific param-eters cannot be carried in 3GPP's UtranRelation object, but a separate vendor-specific object is needed.

ADJL vsDataContainerId=adjlRDNvsDataType=ADJL

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJL-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RncFunc-tion=RNC-1, UtranCell=WBTS-1/WCEL-1, VsDataCon-tainer=ADJL-1


ADJS 1 vsDataContainerId=adjsRDN, vsDataType=ADJS

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJS-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1,

RncFunction=RNC-1, Utran-Cell=WBTS-1/WCEL-1, VsData-Container=ADJS-1


ADJD vsDataContain-erId=adjdRDN, vsDataType=ADJD

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1/ADJD-1


RncFunction=RNC-1, Utran-Cell=WBTS-1/WCEL-1, VsData-Container=ADJD-1

Table 21 NetAct UTRAN vendor specific object/data mappings

66 DN03317891Issue 10-1


Id:0900d80580942542


COCO vsDataContainerId=cocoRDN, vsDataType=COCO

PLMN-PLMN/RNC-1/COCO-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=COCO-1

The NetAct-specific param-eters cannot be carried in 3GPP's IubLink object but a separate vendor specific object is needed under IubLink.

IPNB vsDataContainerId=ipnbRDN, vsDataType=IPNB

PLMN-PLMN/RNC-1/IPNB-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=IPNB-1

BTS (FBTS)

vsDataContainerId=egceRDN, vsDataType=EGCE

PLMN-PLMN/BSC-0/BCF-0/BTS-123 321

SubNetwork=Nokia-1, Extern-alGsmCell=EGCE-123 321, VsDataContainer=EGCE-123 321


Note: currently FBTS (foreign BTS) is used but it will be replaced with EGCE in the future NetAct/Config-urator releases. For more information, see examples of instance mappings on Table 18.

EWCE vsDataContainerId=ewceRDN, vsDataType=EWCE

PLMN-PLMN/EXCC-1/EWCE-1234

SubNetwork=Nokia-1, External-UtranCell=EWCE-1234, VsDataContainer=EWCE-1234


Operators can define the EWCE instance number but the requirement is that the identification has to be unique in the subNetwork. The maximum character amount is 10.

FMCG vsDataContainerId=fmcgRDN, vsDataType=FMCG

PLMN-PLMN/RNC-1/FMCG-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=FMCG-1

WCEL MOs have refer-ences to FMCx MOs: FMCx MO instance has to exist (at least in the same plan) before it can be referred to.

FMCI vsDataContainerId=fmciRDN, vsDataType=FMCI

PLMN-PLMN/RNC-1/FMCI-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=FMCI-1


FMCS vsDataContainerId=fmcsRDN, vsDataType=FMCS

PLMN-PLMN/RNC-1/FMCS-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=FMCS-1


IUR vsDataContainerId=iurRDN, vsDataType=IUR

PLMN-PLMN/RNC-1/IUR-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=IUR-1


Table 21 NetAct UTRAN vendor specific object/data mappings (Cont.)

DN03317891Issue 10-1

67



Id:0900d80580942542

HOPS vsDataContainerId=hopsRDN, vsDataType=HOPS

PLMN-PLMN/RNC-1/HOPS-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=HOPS-1

ADJx MOs have references to HOPx MOs: HOPx MO instance has to exist (at least in the same plan) before it can be referred to.

HOPI vsDataContainerId=hopiRDN, vsDataType=HOPI

PLMN-PLMN/RNC-1/HOPI-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=HOPI-1


HOPG vsDataContainerId=hopgRDN, vsDataType=HOPG

PLMN-PLMN/RNC-1/HOPG-1


RcnFunction=RNC-1, VsData-Container=HOPG-1


WSMLC vsDataContainerId=wsmlcRDN, vsDataType=WSMLC

PLMN-PLMN/RNC-1/WSMLC-1

SubNetwork=Nokia-1,

ManagedElement=RNC-1, Rcn-Function=RNC-1, VsDataCon-tainer=WSMLC-1

There is one WSMLC per each RNC.

WLCSE vsDataContainerId=wlcseRDN, vsDataType=WLCSE

PLMN-PLMN/RNC-1/WLCSE-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=WLCSE-1

WLCSE MOs have refer-ences to WCEL MOs: WCEL instance has to exist (at least in the same plan) before it can be referred to.

WANE vsDataContainerId=waneRDN, vsDataType=WANE

PLMN-PLMN/RNC-1/WANE-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=WANE-1

WSG vsDataContainerId=wsgRDN, vsDataType=WSG

PLMN-PLMN/RNC-1/WSG-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=WSG-1

WSG MOs have references to WANE MOs: WANE instance has to exist (at least in the same plan) before it can be referred to.

RNC 1 vsDataContainerId=rncRDN, vsDataType=RNC

PLMN-PLMN/RNC-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RcnFunc-tion=RNC-1, VsDataContainer=RNC-1

The NetAct-specific param-eters cannot be carried in 3GPP's RncFunction object, but a separate vendor specific object is needed.

RNC/IurItem

VsDataContainerId=NRncId (ID of the neighbouring RNC), vsDataType=RNC

no correspond-ing NetAct DN

SubNetwork=Nokia-1, External-RncFunction=RNC-1, VsData-Container=RNC-1

This is a special mapping. Check Figure 4.



68 DN03317891Issue 10-1


Id:0900d80580942542


WBTS 1 vsDataContainerId=wbtsRDN, vsDataType=WBTS

PLMN-PLMN/RNC-1/WBTS-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1/WBTS-1, NodeBFunction=RNC-1/WBTS-1, VsDataContainer=WBTS-1

The NetAct-specific param-eters cannot be carried in 3GPP's NodeBFunction object, but a separate vendor specific object is needed.

WCEL 1 vsDataContainerId=wcelRDN, vsDataType=WCEL

PLMN-PLMN/RNC-1/WBTS-1/WCEL-1

SubNetwork=Nokia-1, Manage-dElement=RNC-1, RncFunc-tion=RNC-1, UtranCell=WBTS-1/WCEL-1, VsDataCon-tainer=WCEL-1

The NetAct-specific param-eters cannot be carried in 3GPP's UtranCell object, but a separate vendor specific object is needed.

ANTE vsDataContainerId=rRDN, vsDataType=ANTE

PLMN-PLMN/ANTC-1/ANTE-1/

SubNetwork=Nokia-1, Manage-dElement=ANTC-1/ ANTE-1, Antenna=ANTE-1, vsDataCon-tainer=ANTE-1

The NetAct-specific param-eters cannot be carried in 3GPP's AnteFunction object, but a separate vendor specific object is needed. VSD shall not appear as a child of RNC

WCAL vsDataContainerId=rRDN, vsDataType=WCAL

PLMN-PLMN/ANTC-1/ANTE-1/WCAL-1

SubNetwork=Nokia-1, Manage-dElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataCon-tainer=WCAL-1

GCAL vsDataContainerId=rRDN, vsDataType=GCAL

PLMN-PLMN/ANTC-1/ANTE-1/GCAL-1

SubNetwork=Nokia-1, Manage-dElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataCon-tainer=GCAL-1

EUCAL vsDataContainerId=rRDN, vsDataType=EUCAL

PLMN-PLMN/ANTC-1/ANTE-1/EUCAL-1

SubNetwork=Nokia-1, Manage-dElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataCon-tainer=EUCAL-1

IUPS vsDataContainerId=iupsRDN, vsDataType=IUPS

PLMN-PLMN/RNC-1/IUPS-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IUPS-1

IUPSIP vsDataContainerId=iupsRDN/iupsipDN, vsDataType=IUPSIP

PLMN-PLMN/RNC-1/IUPS-1/IUPSIP-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IUPS-1/IUPSIP-1

IUCS vsDataContainerId=iucsRDN, vsDataType=IUCS

PLMN-PLMN/RNC-1/IUCS-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IUCS-1

IUCSIP vsDataContainerId=iucsRDN/iucsipDN, vsDataType=IUCSIP

PLMN-PLMN/RNC-1/IUCS-1/IUCSIP-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IUCS-1/IUCSIP-1



DN03317891Issue 10-1

69



Id:0900d80580942542

VBTS vsDataContainerId=vbtsRDN, vsDataType=VBTS

PLMN-PLMN/RNC-1/VBTS-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=VBTS-1

VCEL vsDataContainerId=vbtsRDN/vcelDN, vsDataTyep=VCEL

PLMN-PLMN/RNC-1/VBTS-1/VCEL-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=VBTS-1/VCEL-1

CMOB vsDataContainerId=cmobRDN, vsDataType=CMOB

PLMN-PLMN/RNC-1/CMOB-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=CMOB-1

IUO vsDataContainerId=iuoRDN, vsDataType=IUO

PLMN-PLMN/RNC-1/IUO-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IUO-1

RNPS vsDataContainerId=rnpsRDN, vs-DataType=RNPS

PLMN-PLMN/RNC-1/RNPS-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNPS-1

RNAC vsDataContainerId=rnacRDN, vs-DataType=RNAC

PLMN-PLMN/RNC-1/RNAC-1

SubNetwork=Nokia-1,

ManagedElement=RNC-1,

RcnFunction=RNC-1, Vs-

DataContainer=RNAC-2

RNRLC vsDataContainerId=rnrlcRDN,vsDataType=RNRLC

PLMN-PLMN/RNC-1/RNRLC-2

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNRLC-1

RNHSPA vsDataContainerId=rnhspaRDN, vs-DataType=RNHSPA

PLMN-PLMN/RNC-1/RNHSPA-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNHSPA-1

RNMOBI vsDataContainerId=rnmobiRDN, vs-DataType=RNMOBI

PLMN-PLMN/RNC-1/RNMOBI-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNMOBI-1

RNTRM vsDataContainerId=rntrmRDN, vs-DataType=RNTRM

PLMN-PLMN/RNC-1/RNTRM-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNTRM-1

RNFC vsDataContainerId=rnfcRDN,vsDataType=RNFC

PLMN-PLMN/RNC-1/RNFC-2

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=RNFC-2



70 DN03317891Issue 10-1


Id:0900d80580942542


1 Note that in this context, this denotes the NetAct-specific part of the object.

g The set of vendor-specific parameters is different per adjacency/relation. It depends on the adjacency type in the NetAct Object Model.

5.3 Interface-N XML file example<?xml version="1.0" encoding="UTF-8"?><bulkCmConfigDataFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.615#configData" xmlns:gn="http://www.3gpp.org/ftp/specs/archive/32_series/32.655#geranNrm" xmlns:sm="http://www.3gpp.org/ftp/specs/archive/32_series/32.675#stateManagementIRP" xmlns:un="http://www.3gpp.org/ftp/specs/archive/32_series/32.645#utranNrm" xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm"> <fileHeader fileFormatVersion="32.615 V6.2" vendorName="Nokia Siemens Networks"/> <configData dnPrefix="DC:nokia.com"> <xn:SubNetwork id="Nokia-51140"> <xn:ManagedElement id="RNC-184"> <xn:attributes> <xn:userLabel>Ahonen</xn:userLabel> <xn:vendorName>Nokia Siemens Networks</xn:vendorName> <xn:swVersion>RN4.0</xn:swVersion> <xn:managedElementType>RNC</xn:managedElementType> </xn:attributes> <un:RncFunction id="RNC-184"> <un:attributes> <un:userLabel>Ahonen</un:userLabel>

CBCI vsDataContainerId=cbciRDN,vsDataType=CBCI

PLMN-PLMN/RNC-1/CBCI-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=CBCI-1

TQM vsDataContainerId=tqmRDN,vsDataType=TQM

PLMN-PLMN/RNC-1/TQM-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=TQM-1

IPQM vsDataContainerId=ipqmRDN,vsDataType=IPQM

PLMN-PLMN/RNC-1/IPQM-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=IPQM-1

WRAB vsDataContainerId=wrabRDN,vsDataType=WRAB

PLMN-PLMN/RNC-1/WRAB-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=WRAB-1

HOPL vsDataContainerId=hoplRDN,vsDataType=HOPL

PLMN-PLMN/RNC-1/HOPL-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=HOPL-1

PFL vsDataContainerId=pflRDN,vsDataType=PFL

PLMN-PLMN/RNC-1/PFL-1

SubNetwork=Nokia-1,Manage-dElement=RNC-1,RncFunc-tion=RNC-1,VsDataContainer=PFL-1



DN03317891Issue 10-1

71



Id:0900d80580942542

<un:rncId>184</un:rncId> </un:attributes> <xn:VsDataContainer id="RNC-184"> <xn:attributes> <xn:vsDataType>RNC</xn:vsDataType> <xn:vsDataFormatVersion>RN4.0</xn:vsDataFormatVersion> <RNC xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKRNC/RN4.0"> <AMRLCOnDCHOfNRTPSCount>10</AMRLCOnDCHOfNRTPSCount> <AMRLCOnDCHOfNRTPSFilterReTX>80</AMRLCOnDCHOfNRTPSFilterReTX> <AMRLCOnDCHOfNRTPSMaxDAT>15</AMRLCOnDCHOfNRTPSMaxDAT> [...] </RNC> </xn:attributes> </xn:VsDataContainer> <un:UtranCell id="WBTS-176/WCEL-1"> <un:attributes> <un:userLabel></un:userLabel> <un:cId>1</un:cId> <un:localCellId>1</un:localCellId> <un:uarfcnDl>10808</un:uarfcnDl> <un:primaryScramblingCode>11</un:primaryScramblingCode> <un:primaryCpichTxPower>330</un:primaryCpichTxPower> <un:maximumTransmissionPower>370</un:maximumTransmissionPower> <un:primarySchPower>-30</un:primarySchPower> <un:secondarySchPower>-30</un:secondarySchPower> <un:bchPower>-50</un:bchPower> <un:cellMode>FDDMode</un:cellMode> <un:lac>4459</un:lac> <un:rac>14</un:rac> <un:sac>15125</un:sac> <un:uraList> <un:ura>1</un:ura> </un:uraList> <un:utranCellIubLink>SubNetwork=Nokia-511410,ManagedElement=RNC-184,RncFunction=RNC-184,IubLink=COCO-2</un:utranCellIubLink> <un:operationalState>enabled</un:operationalState> </un:attributes> <xn:VsDataContainer id="WBTS-176/WCEL-1"> <xn:attributes> <xn:vsDataType>WCEL</xn:vsDataType> <xn:vsDataFormatVersion>RN4.0</xn:vsDataFormatVersion> <WCEL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKRNC/RN4.0"> <WCELCSCNId>1</WCELCSCNId> <WCELMCC>358</WCELMCC> <WCELMNC>03</WCELMNC> [...] </WCEL> </xn:attributes> </xn:VsDataContainer> </un:UtranCell> </un:RncFunction> </xn:ManagedElement> </xn:SubNetwork> </configData> <fileFooter dateTime="2008-10-10T10:48:57+03:00"/></bulkCmConfigDataFile>

72 DN03317891Issue 10-1


Id:0900d80580942542

OSS5.x - 3GPP R8 object model mapping for LTE RL15/RL20

6 OSS5.x - 3GPP R8 object model mapping for LTE RL15/RL20This chapter describes the instance mappings between NetAct Object Model (NOM) and 3GPP R8 Object Model (R8OM).

6.1 Instance mappings This section describes examples of instance mappings.

Object class Mapping NetAct DN 3GPP DN

MRBTS id=MRBTS RDN PLMN-PLMN/ MRBTS-100 SubNetwork=Nokia-1,Manage-dElement=MRBTS-100

ANTL id=MRBTS RDN +”/” +ANTL RDN PLMN-PLMN/ MRBTS-100/ ANTL-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=ANTL-1

BTSSCL id=MRBTS RDN +”/” + BTSSCL RDN

PLMN-PLMN/ MRBTS-100/ BTSSCL-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=BTSSCL-1

LNBTS id=MRBTS RDN+”/” +LNBTS RDN

PLMN-PLMN/ MRBTS-100/ LNBTS-100

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100

MHA id=MRBTS RDN+”/” +MHA RDN PLMN-PLMN/ MRBTS-100/MHA-0

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=MHA-0

RET id=MRBTS RDN+”/”+RET RDN PLMN-PLMN/ MRBTS-100/RET-0

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=RET-0,

RMOD id=MRBTS RDN+”/”+RMOD RDN PLMN-PLMN/ MRBTS-100/ RMOD-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=RMOD-1

SMOD id=MRBTS RDN+”/”+SMOD RDN PLMN-PLMN/ MRBTS-100/ SMOD-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsDataContainer=SMOD-1

LCELL id=MRBTS RDN+”/”+BTSSCL RDN+”/”+LCELL RDN

PLMN-PLMN/MRBTS-100/BTSSCL-1/LECLL-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-1, VsDataContainer=LCELL-1

ADIPNO id=MRBTS RDN+”/”+LNBTS RDN+”/”+ADIPNO RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/ADIPNO-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-1, VsDataContainer=ADIPNO-1

CTRLTS id=MRBTS RDN+”/”+LNBTS RDN+”/”+CTRLTS RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/CTRLTS-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-1, VsDataContainer=CTRLTS-1


DN03317891Issue 10-1

73


OSS5.x - 3GPP R8 object model mapping for LTERL15/RL20

Id:0900d80580942542

FTM id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1

GTPU id=MRBTS RDN+”/”+LNBTS RDN+”/”+GTPU RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/GTPU-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=GTPU-1

ITRACE id=MRBTS RDN+”/”+LNBTS RDN+”/”+ITRACE RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/ITRACE-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=ITRACE-1

LNADJ id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJ RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNADJ-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADJ-0

LNADLP id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADLP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNADLP-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADLP-0

LNCEL id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, EUtranCellFDD/EUtran-CellTDD=LNEL-0

LNMME id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNMME RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNMME-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNMME-0

SCTP id=MRBTS RDN+”/”+LNBTS RDN+”/”+SCTP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/SCTP-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=SCTP-1

MTRACE id=MRBTS RDN+”/”+LNBTS RDN+”/”+CTRLTS+”/”+MTRACE RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/CTRLTS-0/MTRACE-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=CTRLS-0/MTRACE-1

AMGR id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+AMGR RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/AMGR-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/AMGR-1

CERTH id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+CERTH RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/CERTH-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/CERTH-1



74 DN03317891Issue 10-1


Id:0900d80580942542


ETHLK id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+ETHLK RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/ETHLK-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/ETHLK-1

IPNO id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1

IPSECC id=MRBTS RDN+”/”+LNBTSRDN+”/”+FTMRDN+”/”+IPSECC RDN

PLMNPLMN/MRBTS-100/LNBTS-100/FTM-1/IPSECC-0

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100,VsDataContainer=FTM -1/IPSECC-0

L2SWI iid=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+L2SWI RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/L2SWI-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/L2SWI-1

OAMMD id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAMMD RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/OAMMD-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0

OAMPRF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAM-PRF RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/OAMPRF-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/OAMPRF-0

SYNC id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+SYNC RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/SYNC-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/SYNC-0,

PPTT id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+PPTT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/PPTT-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/PPTT-0

UNIT id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+UNIT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/UNIT-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/UNIT-1

LNADJL id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJ RDN+”/”+LNADJL RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNADJ-0/LNADJL-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, EUtranCellTDD/EUtran-CellFDD=LNCEL-100, EUtran-Relation=LNADJ-0/LNADJL-1



DN03317891Issue 10-1

75



Id:0900d80580942542

GFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+GFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/GFIM-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0

IAFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+IAFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/IAFIM-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/IAFIM-0

IRFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+IRFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/IRFIM-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/IRFIM-0

LNHOIF id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNHOIF RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0//LNHOIF-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/LNHOIF-0

REDRT id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+REDRT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/REDRT-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/REDRT-0

UFFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+UFFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/UFFIM-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/UFFIM-0

GNFL id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+GFIM RDN+”/”+GNFL RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/GFIM-0/GNFL-0

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0/GNFL-0

IEIF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+IEIF RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/IEIF-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1

IHCP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+IHCP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/IHCP-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IHCP-1

INTP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+INTP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/INTP-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/INTP-1



76 DN03317891Issue 10-1


Id:0900d80580942542


Notes about the mappings:

• Embedding objects NetAct distinguished names (DNs) into the object instances used in 3GPP DN: some operations like object creation require that knowledge of NetAct internal hierarchy is present in 3GPP DNs, otherwise the object's place in the NetAct hierarchy cannot be determined.

• PLMN is only a conceptual root object in the NetAct model and therefore has no mapping.

• In all mappings involving ManagedElement, its dnPrefix can be set to NULL.

IPRM id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+IPRM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/IPRM-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRM-1

IPRT id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+IPRT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/IPRT-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRT-1

QOS id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+QOS RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/QOS-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/QOS-1

TOPIK id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+TOPIK RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/TOPIK-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/TOPIK-1

OAMMA id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAMMD RDN+”/”+OAMMA RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/OAMMD-0/OAMMA-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1

STPG id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+SYNC RDN+”/”+STPG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/SYNC-0/STPG-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/SYNC-0/STPG-1

IVIF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+IEIF RDN+”/”+IVIF RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/IEIF-1/IVIF-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1/IVIF-1

OAMMEP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAMMD RDN+”/”+OAMMA RDN+”/”+OAMMEP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/OAMMD-0/OAMMA-1/OAMMEP-1

SubNetwork=Nokia-1, Man-agedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1/OAMMEP-1



DN03317891Issue 10-1

77



Id:0900d80580942542

Notes about the attribute value formats (attributes that are affected by the mappings):

• The ManagementNode attribute manages is set to the 3GPP DN of the Manage-dElement(s). The content of 3GPP DN must include the NetAct topology SubNetwork=Nokia-1, ManagedElement=MRBTS-3.

• The ManagedElement attribute managedBy is set to the 3GPP DN of the control-ling OMC.


• OMC: mapped to two common R8OM objects: ManagementNode and Subnet-work.The same NOM, OMCId(NmsId), is used in RDN for both R8OM objects.

• MRBTS: mapped to common R8OM object: ManagedElement. The NOM, mrbtsId, is used in RDN.

• LNBTS: mapped to R8OM object: ENBFunction. The NOM, lnBtsId, is used in RDN.

• LNCEL: mapped to R8OM object: EUtranCellFDD or EUtranCellTDD. The NOM, lnCelId, is used in RDN.

• LNADJL: mapped to R8OM object: EUtranRelation. The NOM, lnAdjlId, is used in RDN.


• Common attributes specified in the 3GPP R8 specifications for each object. • The NOM vendor-specific attributes for common objects are provided in vsDataCon-

tainer.



• ManagedElement: MRBTS NOM object: MRBTS. • ENBFunction; NOM object: LNBTS. That is, all R8OM ENBFunction attributes are

mapped to be attributes of LNBTS in NOM. • EUtranCellFDD; NOM object: LNCEL. That is, all R8OM EUtranCellFDD attributes

are mapped to be attributes of LNCEL in NOM. • EUtranRelation; NOM object: LNADJL. That is, all R8OM EUtranRelation attributes

are mapped to be attributes of LNADJL in NOM. • EUtranCellTDD; NOM object: LNCEL. That is, all R8OM EUtranCellTDD attributes

are mapped to be attributes of LNCEL in NOM. • The NOM vendor-specific attributes for common objects are provided in vsDataCon-

tainer.

78 DN03317891Issue 10-1


Id:0900d80580942542


7 OSS5.x - 3GPP R8 object model mapping for LTE RL25/RL30This chapter describes the instance mappings between NetAct Object Model (NOM) and 3GPP R8 Object Model (R8OM).

7.1 Instance mappings for RL25/RL30This section describes examples of instance mappings.


MRBTS id=MRBTS RDN PLMN-PLMN/ MRBTS-100 SubNetwork=Nokia-1,Manage-dElement=MRBTS-100

ANTL id=MRBTS RDN +”/” +ANTL RDN

PLMN-PLMN/ MRBTS-100/ ANTL-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=ANTL-1


PLMN-PLMN/ MRBTS-100/ BTSSCL-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=BTSSCL-1


PLMN-PLMN/ MRBTS-100/ LNBTS-100

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100

MHA id=MHA RDN PLMN-PLMN/MHA-0 SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=MHA-0

RET id=MRBTS RDN+”/”+RET RDN

PLMN-PLMN/ MRBTS-100/RET-0

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=RET-0,

RMOD id=MRBTS RDN+”/”+RMOD RDN

PLMN-PLMN/ MRBTS-100/ RMOD-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=RMOD-1

SMOD id=MRBTS RDN+”/”+SMOD RDN

PLMN-PLMN/ MRBTS-100/ SMOD-1

SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, VsData-Container=SMOD-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-1, VsDataContainer=LCELL-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-1, VsDataContainer=ADIPNO-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-1, VsDataContainer=CTRLTS-1


DN03317891Issue 10-1

79



Id:0900d80580942542



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=GTPU-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNADJ-0

LNADJG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNADJG-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNADJG-0

LNADJW id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJW RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNADJW-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100,

EUtranCellFDD/EUtran-CellTDD=LNCEL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, EUtranCellFDD/EUtran-CellTDD=LNCEL-0

MODPR id=MRBTS RDN+”/”+LNBTS RDN+”/”+MODPR RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=MODPR-0

MOPR id=MRBTS RDN+”/”+LNBTS RDN+”/”+MOPR RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=MOPR-0

PMRNL id=MRBTS RDN+”/”+LNBTS RDN+”/”+PMRNL RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=PMRNL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=SCTP-1



80 DN03317891Issue 10-1


Id:0900d80580942542




SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=CTRLS-0/MTRACE-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/AMGR-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/CERTH-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/ETHLK-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1



SubNetwork=Nokia-1,Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100,VsDataContainer=FTM -1/IPSECC-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/L2SWI-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0

OAMPRF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAMPRF RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/OAMPRF-0

PMTNL id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+PMTNL RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/PMTNL-0



DN03317891Issue 10-1

81



Id:0900d80580942542



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/SYNC-0,



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/PPTT-0

TAC id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TAC-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/TAC-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/UNIT-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, EUtranCellTDD/EUtran-CellFDD=LNCEL-100, EUtran-Relation=LNADJ-0/LNADJL-1

LNRELG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNRELG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNRELG-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNRELG-0

LNRELW id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNRELW RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNRELW-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNRELW-0

CDFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+CDFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/CDFIM-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/CDFIM-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/IAFIM-0



82 DN03317891Issue 10-1


Id:0900d80580942542


LNHOG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNHOG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOG-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNHOG-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/IRFIM-0


PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOIF-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNHOIF-0

LNHOW id=MRBTS RDN+”/”+LNBTS RND+”/”+LNCEL RDN+”/”+LNHOW RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOW-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNHOW-0

LNREL id=MRBTS RDN+”/”+LNBTS RND+”/”+LNCEL RDN+”/”+LNREL RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNREL-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/LNREL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/REDRT-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/UFFIM-0

MODRED id=MRBTS RDN+”/”+LNBTS RDN+”/”+MODPR RDN+”/”+MODRED RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/MODPR-0/MODRED-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=MODPR-0/MODRED-0

MORED id=MRBTS RDN+”/”+LNBTS RDN+”/”+MOPR RDN+”/”+MORED RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/MOPR-0/MORED-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=MOPR-0/MORED-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0/GNFL-0



DN03317891Issue 10-1

83



Id:0900d80580942542

BFD id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+BFD RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/BFD-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/BFD-1

BFDGRP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+BFDGRP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/BFDGRP-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/BFDGRP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IHCP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/INTP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRM-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRT-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/QOS-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/TOPIK-1

TWAMP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+TWAMP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/TWAMP-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/TWAMP-1



84 DN03317891Issue 10-1


Id:0900d80580942542



• OMC: mapped to two common R8OM objects: ManagementNode and Subnet-work.The same NOM, OMCId(NmsId), is used in RDN for both R8OM objects.

• MRBTS: mapped to common R8OM object: ManagedElement. The NOM, mrbtsId, is used in RDN.

• LNBTS: mapped to R8OM object: ENBFunction. The NOM, lnBtsId, is used in RDN.

• LNCEL: mapped to R8OM object: EUtranCellFDD or EUtranCellTDD. The NOM, lnCelId, is used in RDN.

• LNADJL: mapped to R8OM object: EUtranRelation. The NOM, lnAdjlId, is used in RDN.


• Common attributes specified in the 3GPP R8 specifications for each object. • The NOM vendor-specific attributes for common objects are provided in vsDataCon-

tainer.



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/SYNC-0/STPG-1

LTAC id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN+”/”+LTAC RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TAC-0/LTAC-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/TAC-0/LTAC-1

IVIF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN+”/”+IEIF RDN+”/”+IVIF RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1/IVIF-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENB-Function=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1/OAMMEP-1



DN03317891Issue 10-1

85



Id:0900d80580942542



• ManagedElement: MRBTS NOM object: MRBTS. • ENBFunction; NOM object: LNBTS. That is, all R8OM ENBFunction attributes are

mapped to be attributes of LNBTS in NOM. • EUtranCellFDD; NOM object: LNCEL. That is, all R8OM EUtranCellFDD attributes

are mapped to be attributes of LNCEL in NOM. • EUtranRelation; NOM object: LNADJL. That is, all R8OM EUtranRelation attributes

are mapped to be attributes of LNADJL in NOM. • EUtranCellTDD; NOM object: LNCEL. That is, all R8OM EUtranCellTDD attributes

are mapped to be attributes of LNCEL in NOM. • The NOM vendor-specific attributes for common objects are provided in vsDataCon-

tainer.

86 DN03317891Issue 10-1


Id:0900d80580942542

OSS5.x - 3GPP R8 object model mapping for LTE RL40

8 OSS5.x - 3GPP R8 object model mapping for LTE RL40This chapter describes the instance mappings between NetAct Object Model (NOM) and 3GPP R8 Object Model (R8OM).

8.1 Instance mappings for RL40This section describes examples of instance mappings.


MRBTS id=MRBTS RDN PLMN-PLMN/MRBTS-100 SubNetwork=Nokia-1, Manage-dElement=MRBTS-100

ANTL id=MRBTS RDN +”/” +ANTL RDN

PLMN-PLMN/MRBTS-100/ANTL-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=ANTL-1


PLMN-PLMN/MRBTS-100/BTSSCL-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=BTSSCL-1


PLMN-PLMN/MRBTS-100/LNBTS-100

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100

MHA id=MHA RDN PLMN-PLMN/MHA-0 SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=MHA-0

RET id=MRBTS RDN+”/”+RET RDN

PLMN-PLMN/MRBTS-100/ RET-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=RET-0

RMOD id=MRBTS RDN+”/”+RMOD RDN

PLMN-PLMN/MRBTS-100/RMOD-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=RMOD-1

SMOD id=MRBTS RDN+”/”+SMOD RDN

PLMN-PLMN/MRBTS-100/SMOD-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, VsData-Container=SMOD-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-1, VsDataContainer=LCELL-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-1, VsDataContainer=ADIPNO-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-1, VsDataContainer=CTRLTS-1


DN03317891Issue 10-1

87


OSS5.x - 3GPP R8 object model mapping for LTERL40

Id:0900d80580942542



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=GTPU-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNADJ-0

LNADJG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJG RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNADJG-0

LNADJW id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNADJW RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNADJW-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, EUtranCellFDD/EUtran-CellTDD=LNCEL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNMME-0

MODPR id=MRBTS RDN+”/”+LNBTS RDN+”/”+MODPR RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=MODPR-0

MOPR id=MRBTS RDN+”/”+LNBTS RDN+”/”+MOPR RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=MOPR-0

PMRNL id=MRBTS RDN+”/”+LNBTS RDN+”/”+PMRNL RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=PMRNL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=SCTP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=CTRLS-0/MTRACE-1



88 DN03317891Issue 10-1


Id:0900d80580942542




SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/AMGR-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/CERTH-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/ETHLK-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPSECC-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/L2SWI-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0

OAMPRF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+OAMPRF RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/OAMPRF-0

PMTNL id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+PMTNL RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/PMTNL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/SYNC-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/PPTT-0



DN03317891Issue 10-1

89



Id:0900d80580942542

TAC id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TAC-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/TAC-0

TOPB id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TOPB RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TOPB-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/TOPB-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/UNIT-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, EUtranCellTDD/EUtran-CellFDD=LNCEL-100, EUtranRela-tion=LNADJ-0/LNADJL-1

LNRELG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNRELG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNRELG-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNRELG-0

LNRELT id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNRELT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNRELT-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNRELT-0

LNRELW id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNRELW RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNRELW-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNRELW-0

CDFIM id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+CDFIM RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/CDFIM-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/CDFIM-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/IAFIM-0



90 DN03317891Issue 10-1


Id:0900d80580942542


LNHOG id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNHOG RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOG-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNHOG-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/IRFIM-0


PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOIF-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNHOIF-0

LNHOT id=MRBTS RDN+”/”+LNBTS RDN+”/”+LNCEL RDN+”/”+LNHOT RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOT-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNHOT-0

LNHOW id=MRBTS RDN+”/”+LNBTS RND+”/”+LNCEL RDN+”/”+LNHOW RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNHOW-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNHOW-0

LNREL id=MRBTS RDN+”/”+LNBTS RND+”/”+LNCEL RDN+”/”+LNREL RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/LNCEL-0/LNREL-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/LNREL-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/REDRT-0



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/UFFIM-0

MODRED id=MRBTS RDN+”/”+LNBTS RDN+”/”+MODPR RDN+”/”+MODRED RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/MODPR-0/MODRED-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=MODPR-0/MODRED-0

MORED id=MRBTS RDN+”/”+LNBTS RDN+”/”+MOPR RDN+”/”+MORED RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/MOPR-0/MORED-0

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=MOPR-0/MORED-0



DN03317891Issue 10-1

91



Id:0900d80580942542



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=LNCEL-0/GFIM-0/GNFL-0

BFD id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+BFD RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/BFD-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/BFD-1

BFDGRP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+BFDGRP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/BFDGRP-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/BFDGRP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IHCP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/INTP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRM-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IPRT-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/QOS-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/TOPIK-1



92 DN03317891Issue 10-1


Id:0900d80580942542


TWAMP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+IPNO RDN+”/”+TWAMP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/IPNO-1/TWAMP-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/TWAMP-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/SYNC-0/STPG-1

LTAC id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN+”/”+LTAC RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TAC-0/LTAC-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/TAC-0/LTAC-1

TOPF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TOPB RDN+”/”+TOPF RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TOPB-0/TOPF-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/TOPB-0/TOPF-1

TOPP id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TOPB RDN+”/”+TOPP RDN

PLMN-PLMN/MRBTS-100/LNBTS-100/FTM-1/TOPB-0/TOPP-1

SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/TOPB-0/TOPP-1

IVIF id=MRBTS RDN+”/”+LNBTS RDN+”/”+FTM RDN+”/”+TAC RDN+”/”+IEIF RDN+”/”+IVIF RDN


SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/IPNO-1/IEIF-1/IVIF-1



SubNetwork=Nokia-1, Manage-dElement=MRBTS-100, ENBFunc-tion=LNBTS-100, VsDataContainer=FTM -1/OAMMD-0/OAMMA-1/OAMMEP-1

EXENBF id=EXENBF RND PLMN-PLMN/EXCENBF-1/EXENBF-1

SubNetWork=Nokia-1,ExternalEN-BFunction=EXCENBF-1/EXENBF-1

EXEUCE id=EXENBF RND+”/”+EXEUCE RDN

PLMN-PLMN/EXCENBF-1/EXENBF-1/EXEUCE-1

SubNetwork=Nokia-1, ExternalEN-BFunction=EXCENBF-1/EXENBF-1, ExternalEUtranCellFDD/Exernal-EUtranCellTDD=EXEUCE-1



DN03317891Issue 10-1

93



Id:0900d80580942542

8.2 Considerations in CM data upload (NetAct model → 3GPP model)During the upload of a NRM object:

• OMC is mapped to two common 3GPP R8 NRM objects ManagementNode and Subnetwork.

• MRBTS is mapped to common 3GPP R8 NRM object ManagedElement. • LNBTS is mapped to 3GPP R8 NRM object ENBFunction. • LNCEL is mapped to 3GPP R8 NRM object EUtranCellFDD or EUtranCellTDD. • LNADJL is mapped to 3GPP R8 NRM object EUtranRelation.

All of the 3GPP R8 NRM objects can be separately requested to upload and upload is done based on the upload scope. The relevant attributes have to be uploaded for each 3GPP R8 NRM object:

• Common attributes specified in the 3GPP R8 specifications for each object. • The NSN internal NRM vendor-specific attributes for common objects are provided

in VsData-Container.

8.3 Considerations in CM data download (3GPP model → NetAct model)During the download of R8OM objects:

• ManagementNode and Subnetwork are combined in one NSN internal NRM object OMC, which holds all ManagementNode and Subnetwork attributes in the NSN internal NRM.

• ManagedElement is mapped to NSN internal NRM object MRBTS. • ENBFunction is mapped to NSN internal NRM object LNBTS. • EUtranCellFDD is mapped to NSN internal NRM object LNCEL. • EUtranRelation is mapped to NSN internal NRM object LNADJL. • EUtranCellTDD is mapped to NSN internal NRM object LNCEL. • The NSN internal NRM vendor-specific attributes for common objects are provided

in VsData-Container.

94 DN03317891Issue 10-1


Id:0900d80580942542

Troubleshooting

9 TroubleshootingThe following steps describe how to troubleshoot the 3GPP CORBA Bulk CM North-bound Interface.

To restart the 3GPP CORBA Bulk CM Northbound Interface

1. Find PID of the rac3gpmx process with command:

ls -l /var/opt/nokia/oss/local/common/ref/*rac3gp*

It returns a reference file of the format

/var/opt/nokia/oss/local/common/ref/<host>.rac3gpmx.<PID>

2. Terminate rac3gpmx process with command:

kill -TERM <PID>

3. Find PID of the wpmanamx process supervising rac3gpmx process with command:

ls -l /var/opt/nokia/oss/local/common/ref/*rac*wpmana*

It returns a reference file of the format

/var/opt/nokia/oss/local/common/ref/<rac_package>.wpmanamx..<PID>

Send HUP signal to wpmanamx process:

kill -HUP <PID>

4. The CM NBIF restarts automatically in couple of minutes.

Command for manually starting rac3gpmx process should be changed from/opt/nokia/oss/configurator/rac/rac3gp/bin/rac3gpmx.sh& to /opt/nokia/oss/bin/rac3gpmx.sh

To stop the 3GPP CORBA Bulk CM Northbound Interface process

1. Stop the process with:

kill -TERM <PID>

The process will be shutdown and removed from WPMANA control.

2. Start the process manually with:

/opt/nokia/oss/configurator/rac/rac3gp/bin/rac3gpmx.sh&

to

/opt/nokia/oss/bin/rac3gpmx.sh

DN03317891Issue 10-1

95


Where to find more information

Id:0900d80580942542

10 Where to find more informationFor more information on NetAct Configurator, see NetAct Configurator Principles, DN03317888.

For more information on technical aspects of NetAct Configurator, see NetAct Configu-rator Technical Reference Guide, DN03317864.

For the allowed object identifiers, see Managed Object Reference, DN00126336.

For detailed information about RNC parameters supported by NetAct Configurator, see Adaptation Information Browser.

For WCDMA parameter mapping, see Interface-N: WCDMA (3G) Parameter Mapping, DN03373371.

For instructions on how to configure SFTP, see Enabling the SFTP file transfer between NetAct and 3GPP manager in Managing NetAct System Security document.

For more information about the 3GPP CORBA Northbound Interface, see the following documents in NED and in the NOLS documentation set:

• Configuring NetAct for 3GPP CORBA Northbound Interface, DN05171594 • 3GPP CORBA Northbound Interface Technical Reference Guide, DN05171613 • 3GPP CORBA Northbound Interface Principles, DN05171637

See the 3rd Generation Partnership Project (3GPP) web pages at http://www.3gpp.org/ftp/Specs/ for the following specifications:

For 3GPP R6 object models (termed Network Resource Models):

• TS 32.622-6.4.0 Generic Network Resources IRP: Network Resource Model (2005-03)

• 3GPP TS 32.642-6.4.0 UTRAN Network Resources IRP: Network Resource Model (2005-03)

• 3GPP TS 32.652-6.4.0 GERAN Network Resources IRP: Network Resource Model (2005-03)

• 3GPP TS 32.300-6.4.0 Name Convention for Managed Objects (2005-03)

For 3GPP R8 UTRAN object models (termed Network Resource Models):

• 3GPP TS 32.762 V8.2.0 Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Network Resource Model (NRM) Integration Reference Point (IRP)

• 3GPP TS 32.300 v8.0.0 Name Convention for Managed Objects (12/2008)

96 DN03317891Issue 10-1


Id:0900d80580942542

Appendix A: BulkCmIRPConstDefs.idl

11 Appendix A: BulkCmIRPConstDefs.idl // File: BulkCmIRPConstDefs.idl

#ifndef _BULKCMIRPCONSTDEFS_IDL_#define _BULKCMIRPCONSTDEFS_IDL_

// This statement must appear after all include statements#pragma prefix "3gppsa5.org"

/* ## Module: BulkCmIRPConstDefsThis module contains type definitions for the Bulk CM IRP================================================================*/module BulkCmIRPConstDefs{

/*This block identifies the notification types defined bythis Bulk CM IRP version.This string is used in the second field of the StructuredEvent.*/interface NotificationType{

const string NOTIFY_SESSION_STATE_CHANGED = "x1";const string NOTIFY_GET_SESSION_LOG_ENDED = "x2";

};

/*This block assigns value for the name of the NV of the Structured Event.*/interface AttributeNameValue{

const string SESSION_ID = "k";const string SOURCE_INDICATOR = "m";const string ERROR_INFORMATION = "n";

};

/*This block defines all possible values for sessionState.One of these strings appear in the event_name of theStructured Event of notifySessionStateChanged notification.*/interface SessionStateChangeNotification{

const string UPLOAD_FAILED = "x1";const string UPLOAD_COMPLETED = "x2";const string DOWNLOAD_FAILED = "x3";const string DOWNLOAD_COMPLETED = "x4";const string ACTIVATION_FAILED = "x5";

DN03317891Issue 10-1

97



Id:0900d80580942542

const string ACTIVATION_PARTLY_REALISED = "x6";const string ACTIVATION_COMPLETED = "x7";const string FALLBACK_FAILED = "x8";const string FALLBACK_PARTLY_REALISED = "x9";const string FALLBACK_COMPLETED = "x10";const string VALIDATION_FAILED = "x11";const string VALIDATION_COMPLETED = "x12";const string PREACTIVATION_FAILED = "x13";const string PREACTIVATION_PARTLY_REALISED = "x14";const string PREACTIVATION_COMPLETED = "x15";

};

/*This block defines all possible values for sessionLogStatusOne of these strings appear in the event_name of the StructuredEvent of notifyGetSessionLogEnded notification.*/interface LogStateNotification{

const string GET_SESSION_LOG_COMPLETED_SUCCESSFULLY = "x1";const string GET_SESSION_LOG_COMPLETED_UNSUCESSFULLY = "x2";

};

/*For each started configuration session a unique identifier is generatedby the IRPManager. An sessionId can not be used for an upload if it isalready in use of a download configuration and vice versa.*/typedef string SessionId;

/*This string field is used in order to provide additional error informationif an operation has failed.*/typedef string ErrorInformation;

/*Defines the different subphases of a configuration sessione.g. thus it is easy to implement a detection of an uploador a download/activate session.*/enum SubPhase {IdlePhase, DownloadPhase, UploadPhase, ActivationPhase,

FallbackPhase, PreactivationPhase, ValidationPhase};

/*Defines the different substates of a configuration session. This includesthe transition state as well.*/enum SubState {Completed, Failed, PartlyRealised, InProgress};

/*

98 DN03317891Issue 10-1


Id:0900d80580942542


Defines state of a configuration session with the phase and the substateof the configuration.*/struct SessionState{

SubPhase sub_phase;SubState sub_state;

};

/*Contains the list of all current sessionIds*/typedef sequence <SessionId> SessionIdList;

/*Specifies a complete destination path (including filename).*/typedef string FileDestination;

/*The format of Distinguished Name is specified inthe Naming Conventions for Managed Objects; TS 32.300.e.g. "SubNetwork=10001,ManagedElement=400001" identifies aManagedElement instance of the object model.*/typedef string DistinguishedName;

/*Used within the upload method to give filter critera*/typedef string FilterType;

/*Defines the kind of scope to use in a search together withSearchControl.level, in a SearchControl value.SearchControl.level is always >= 0. If a level is bigger than thedepth of the tree there will be no exceptions thrown.*/enum ScopeType {BaseOnly, BaseNthLevel, BaseSubtree, BaseAll};

/*Controls the searching for MOs during upload, and contains:the type of scope ("type" field),the level of scope ("level" field),the filter ("filter" field),The type and level fields are mandatory.The filter field is mandatory (The filter will have to beset to an empty string if it has no other value).*/struct SearchControl{

DN03317891Issue 10-1

99



Id:0900d80580942542

ScopeType type;unsigned long level;FilterType filter;

};

/*This indicates how the activation is executed, either with least serviceimpact or least elapsed time.*/ enum ActivationMode {LeastServiceImpact, LeastElapsedTime};

/*This indicates the level of verification of bulk configuration data done,either full or limited checking.*/ enum VerificationMode {FullChecking, LimitedChecking};

/* ActivationModeTypeOpt is a type carrying an optional parameter.If the boolean is TRUE, the value is present.Otherwise, the value is absent.

*/union ActivationModeTypeOpt switch(boolean)

{case TRUE: ActivationMode activation_mode;

};

/* VerificationModeTypeOpt is a type carrying an optional parameter.If the boolean is TRUE, the value is present.Otherwise, the value is absent.

*/union VerificationModeTypeOpt switch(boolean){

case TRUE: VerificationMode verification_mode;};

};

#endif // _BULKCMIRPCONSTDEFS_IDL_

100 DN03317891Issue 10-1


Id:0900d80580942542

Appendix B: BulkCMIRPSystem.idl

12 Appendix B: BulkCMIRPSystem.idl// File: BulkCMIRPSystem.idl

#ifndef _BULKCMIRPSYSTEM_IDL_#define _BULKCMIRPSYSTEM_IDL_

#include "BulkCmIRPConstDefs.idl"#include "ManagedGenericIRPConstDefs.idl"#include "ManagedGenericIRPSystem.idl"


/* ## Module: BulkCmIRPSystemThis module implements capabilities of Bulk CM IRP.================================================================*/module BulkCmIRPSystem{

/*The request cannot be processed due to a situation of concurrency.E.g. two concurrent activation requests involving the same ManagedElementinstance. The semantics carried in reason is outside the scope of this IRP.*/exception ConcurrencyException { string reason; };

/*The provided filter is malformed or invalid. The semantics carried in reasonis outside the scope of this IRP.*/exception IllegalFilterFormatException { string reason; };

/*The provided Distinguished Name is malformed or invalid. The semanticscarried in reason is outside the scope of this IRP.*/exception IllegalDNFormatException { string reason; };

/*The provided scope type is illegal. The semantics carried in reason isoutside the scope of this IRP.*/exception IllegalScopeTypeException { string reason; };

/*The provided scope level is illegal. The semantics carried in reason isoutside the scope of this IRP.*/exception IllegalScopeLevelException { string reason; };

DN03317891Issue 10-1

101



Id:0900d80580942542

/*The request cannot be processed because no fallback data is available, that isfallback capability was previously not asked for.*/exception NoFallbackException {};

/*The provided sessionId value is already used for another configurationsession. The semantics carried in reason is outside the scope of this IRP.*/exception SessionIdInUseException { string reason; };

/*The provided URL is malformed or invalid. The semantics carried in reason isoutside the scope of this IRP.*/exception IllegalURLFormatException{ string reason; };

/*The provided sessionId value does not identify any existing configurationsession.*/exception UnknownSessionIdException {};

/*The request cannot be processed because it is not valid in the current stateof the configuration session.*/exception NotValidInCurrentStateException{

BulkCmIRPConstDefs::SessionState current_state;};

/*The request cannot be processed because the maximum number of simultaneouslyrunning configuration sessions has been reached. The semantics carried inreason is outside the scope of this IRP.*/exception MaxSessionReachedException { string reason; };

/*The provided ActivationMode type is illegal. The semantics carried in reasonis outside the scope of this IRP.*/exception IllegalActivationModeException { string reason; };

/*The provided VerificationMode type is illegal. The semantics carried inreason is outside the scope of this IRP.*/exception IllegalVerificationModeException { string reason; };

102 DN03317891Issue 10-1


Id:0900d80580942542


/*System otherwise fails to complete the operation. System can provide reasonto qualify the exception. The semantics carried in reasonis outside the scope of this IRP.*/exception GetBulkCmIRPVersionsException { string reason; };exception UploadException { string reason; };exception DownloadException { string reason; };exception ActivateException { string reason; };exception ValidateException { string reason; };exception PreactivateException { string reason; };exception GetBulkCMIRPOperationProfileException { string reason; };exception GetBulkCMIRPNotificationProfileException { string reason; };exception GetSessionLogException { string reason; };exception StartSessionException { string reason; };exception GetSessionStatusException { string reason; };exception FallbackException { string reason; };exception EndSessionException { string reason; };exception AbortSessionOperationException { string reason; };exception GetSessionIdsException { string reason; };

/*Defines the System interface of a EM. It defines all methods which arenecessary to control a configuration session from a IRPManager.*/interface BulkCmIRP{

/*Return the list of all supported Bulk CM IRP versions.*/ManagedGenericIRPConstDefs::VersionNumberSet get_bulk_CM_IRP_versions ()raises (GetBulkCmIRPVersionsException);

/*Return the list of all supported operations and their supportedparameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList get_bulk_CM_IRP_operation_profile (

in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version)raises (GetBulkCMIRPOperationProfileException,

ManagedGenericIRPSystem::OperationNotSupported,ManagedGenericIRPSystem::InvalidParameter);

/*Return the list of all supported notifications and their supportedparameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList

DN03317891Issue 10-1

103



Id:0900d80580942542

get_bulk_CM_IRP_notification_profile(

in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version)raises (GetBulkCMIRPNotificationProfileException,


/*Uploads a configuration from the subnetwork. The result is put in aconfiguration data file in an area specified by the IRPManager.The MIB of the subnetwork is iterated by means of containment search,using a SearchControl to control the search and the returned results.All MOs in the scope constitutes a set that the filter works on.In case of a concurrent running session the function willreturn an exception. If the value of the given baseObject or FilterTypedoes not exist then this asynchronous error condition will be notified.*/void upload (

in BulkCmIRPConstDefs::SessionId session_id,in BulkCmIRPConstDefs::FileDestination sink,in BulkCmIRPConstDefs::DistinguishedName base_object,in BulkCmIRPConstDefs::SearchControl search_control

)raises (UploadException, UnknownSessionIdException,

MaxSessionReachedException, NotValidInCurrentStateException,ConcurrencyException,IllegalDNFormatException, IllegalFilterFormatException,IllegalScopeTypeException, IllegalScopeLevelException,IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

/*Indicates the EM that it can download a configuration data file froma given configuration data file storage area. The EM will check theconsistence of the configuration data and the software compatibility.*/void download (

in BulkCmIRPConstDefs::SessionId session_id,in BulkCmIRPConstDefs::FileDestination source

)raises (DownloadException, UnknownSessionIdException,

MaxSessionReachedException, NotValidInCurrentStateException,IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

/*Activates a previously downloaded and successfully parsed configurationinside a session. This means that the configuration will be introducedin the live sub-network. In case of a concurrent running sessionthe function will return an exception.

104 DN03317891Issue 10-1


Id:0900d80580942542


*/void activate (

in BulkCmIRPConstDefs::SessionId session_id,in BulkCmIRPConstDefs::ActivationModeTypeOpt activation_mode,in boolean fallback

)raises (ActivateException, UnknownSessionIdException,

NotValidInCurrentStateException, ConcurrencyException,IllegalActivationModeException,ManagedGenericIRPSystem::ParameterNotSupported,ManagedGenericIRPSystem::InvalidParameter);

/*Uploads a log from the subnetwork which is usually used for erroranalysis. The log is put in a logfile in the filesystem which canbe accessed by the EM. If there are no log entries an empty log fileis uploaded.*/void get_session_log (

in BulkCmIRPConstDefs::FileDestination sink,in BulkCmIRPConstDefs::SessionId session_id,in boolean only_error_info

)raises (GetSessionLogException, UnknownSessionIdException,

IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

/*Creates an instance of the configuration session state machine. TheIDLE_PHASE & COMPLETED is notified*/void start_session (

in BulkCmIRPConstDefs::SessionId session_id)raises (StartSessionException, SessionIdInUseException,

MaxSessionReachedException,ManagedGenericIRPSystem::InvalidParameter);

/*Returns the state of a configuration session.*/BulkCmIRPConstDefs::SessionState get_session_status (

in BulkCmIRPConstDefs::SessionId session_id,out BulkCmIRPConstDefs::ErrorInformation error_information

)raises (GetSessionStatusException, UnknownSessionIdException,

ManagedGenericIRPSystem::InvalidParameter);

/*Actives a fallback area. Each time a configuration is activated afallback area can be created, s. activate parameter.

DN03317891Issue 10-1

105



Id:0900d80580942542

This area is backup of the complete configuration which can berestored by this method. The process is as follows:1. When the method activate(...,..., TRUE) is used,

a copy of the valid area is taken before the activationof the new planned data has started. Only one fallback area canexists at a time for a specific scope of the subnetwork.

2. When a fallback area is available and triggered by this method, theprevious valid area is replaced with the data stored inthe fall back area.

If the EM detects that the former configuration has never beenchanged it returns an exception because it does not trigger anactivation of the former data.*/void fallback (

in BulkCmIRPConstDefs::SessionId session_id)raises (FallbackException, UnknownSessionIdException, NoFallbackException,

NotValidInCurrentStateException, ConcurrencyException,ManagedGenericIRPSystem::InvalidParameter);

/*The IRPManager invokes this operation to delete all its temporaryentities and the related sessionId which belong to the scope ofa configuration session. This includes the related error and loginformation too.*/void end_session (

in BulkCmIRPConstDefs::SessionId session_id)raises (EndSessionException, UnknownSessionIdException,

NotValidInCurrentStateException,ManagedGenericIRPSystem::InvalidParameter);

/*The IRPManager invokes this operation to abort an active operationduring a configuration session. It is only effectinga configuration session in state IN_PROGRESS. In this case thecurrent session task is interrupted, e.g. the activating in progress,using best effort strategy, and a state change is notified*/void abort_session_operation (

in BulkCmIRPConstDefs::SessionId session_id)raises (AbortSessionOperationException, UnknownSessionIdException,

NotValidInCurrentStateException,ManagedGenericIRPSystem::InvalidParameter);

/*Returns a list all sessionIds of current running configuration sessions.*/BulkCmIRPConstDefs::SessionIdList get_session_ids (

106 DN03317891Issue 10-1


Id:0900d80580942542


)raises (GetSessionIdsException);

/*Validates previously downloaded bulk configuration data inside a session.Detects errors in the data prior to requesting preactivation oractivation.*/void validate (

in BulkCmIRPConstDefs::SessionId session_id,in BulkCmIRPConstDefs::ActivationModeTypeOpt activation_mode

)raises (ValidateException, UnknownSessionIdException,

NotValidInCurrentStateException, ConcurrencyException,IllegalActivationModeException,ManagedGenericIRPSystem::ParameterNotSupported,ManagedGenericIRPSystem::InvalidParameter,ManagedGenericIRPSystem::OperationNotSupported);

/*Preactivates previously downloaded bulk configuration data inside asession. This operation validates configuration data changes in thecontext of the current data and pre-processes the configuration datachanges.*/void preactivate (

in BulkCmIRPConstDefs::SessionId session_id,in BulkCmIRPConstDefs::VerificationModeTypeOpt verification_mode,in BulkCmIRPConstDefs::ActivationModeTypeOpt activation_mode,in boolean fallback

)raises (PreactivateException, UnknownSessionIdException,

NotValidInCurrentStateException, ConcurrencyException,IllegalActivationModeException, IllegalVerificationModeException,ManagedGenericIRPSystem::ParameterNotSupported,ManagedGenericIRPSystem::InvalidParameter,ManagedGenericIRPSystem::OperationNotSupported);

};};

module SimpleUploadBulkCMIRPSystem{

exception GetSimpleUploadBulkCmIRPVersionsException { string reason; };exception GetSimpleUploadBulkCMIRPOperationProfileException

{ string reason; };exception GetSimpleUploadBulkCMIRPNotificationProfileException

{ string reason; };

DN03317891Issue 10-1

107



Id:0900d80580942542

interface SimpleUploadBulkCMIRP{

/*Return the list of all supported Bulk CM IRP versions.*/ManagedGenericIRPConstDefs::VersionNumberSet

get_simple_upload_bulk_CM_IRP_versions ()raises (GetSimpleUploadBulkCmIRPVersionsException);

/*Return the list of all supported operations and their supportedparameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList

get_simple_upload_bulk_CM_IRP_operation_profile (in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version

)raises (GetSimpleUploadBulkCMIRPOperationProfileException,


/*Return the list of all supported notifications and their supportedparameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList

get_simple_upload_bulk_CM_IRP_notification_profile(

in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version)raises (GetSimpleUploadBulkCMIRPNotificationProfileException,




108 DN03317891Issue 10-1


Id:0900d80580942542


)raises (

BulkCmIRPSystem::UploadException,BulkCmIRPSystem::UnknownSessionIdException,BulkCmIRPSystem::MaxSessionReachedException,BulkCmIRPSystem::NotValidInCurrentStateException,BulkCmIRPSystem::ConcurrencyException,BulkCmIRPSystem::IllegalDNFormatException,BulkCmIRPSystem::IllegalFilterFormatException,BulkCmIRPSystem::IllegalScopeTypeException,BulkCmIRPSystem::IllegalScopeLevelException,BulkCmIRPSystem::IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

};

}; // end of module SimpleUploadBulkCMIRPSystem

module ControlledUploadBulkCMIRPSystem{

exception GetControlledUploadBulkCmIRPVersionsException { string reason; };exception GetControlledUploadBulkCMIRPOperationProfileException

{ string reason; };exception GetControlledUploadBulkCMIRPNotificationProfileException

{ string reason; };

interface ControlledUploadBulkCMIRP{

/*Return the list of all supported Bulk CM IRP versions.*/ManagedGenericIRPConstDefs::VersionNumberSet

get_controlled_upload_bulk_CM_IRP_versions ()raises (GetControlledUploadBulkCmIRPVersionsException);

/*Return the list of all supported operations and their supportedparameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList

get_controlled_upload_bulk_CM_IRP_operation_profile (in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version

)raises (GetControlledUploadBulkCMIRPOperationProfileException,


/*Return the list of all supported notifications and their supported

DN03317891Issue 10-1

109



Id:0900d80580942542

parameters for a specific BulkCM IRP version.*/ManagedGenericIRPConstDefs::MethodList

get_controlled_upload_bulk_CM_IRP_notification_profile (in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version

)raises (GetControlledUploadBulkCMIRPNotificationProfileException,




)raises (

BulkCmIRPSystem::UploadException,BulkCmIRPSystem::UnknownSessionIdException,BulkCmIRPSystem::MaxSessionReachedException,BulkCmIRPSystem::NotValidInCurrentStateException,BulkCmIRPSystem::ConcurrencyException,BulkCmIRPSystem::IllegalDNFormatException,BulkCmIRPSystem::IllegalFilterFormatException,BulkCmIRPSystem::IllegalScopeTypeException,BulkCmIRPSystem::IllegalScopeLevelException,BulkCmIRPSystem::IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

/*Uploads a log from the subnetwork which is usually used for erroranalysis. The log is put in a logfile in the filesystem which canbe accessed by the EM. If there are no log entries an empty log fileis uploaded.*/void get_session_log (

in BulkCmIRPConstDefs::FileDestination sink,in BulkCmIRPConstDefs::SessionId session_id,in boolean only_error_info

110 DN03317891Issue 10-1


Id:0900d80580942542


)raises (

BulkCmIRPSystem::GetSessionLogException,BulkCmIRPSystem::UnknownSessionIdException,BulkCmIRPSystem::IllegalURLFormatException,ManagedGenericIRPSystem::InvalidParameter);

/*Creates an instance of the configuration session state machine. TheIDLE_PHASE & COMPLETED is notified*/void start_session (

in BulkCmIRPConstDefs::SessionId session_id)raises (

BulkCmIRPSystem::StartSessionException,BulkCmIRPSystem::SessionIdInUseException,BulkCmIRPSystem::MaxSessionReachedException,ManagedGenericIRPSystem::InvalidParameter);

/*Returns the state of a configuration session.*/BulkCmIRPConstDefs::SessionState get_session_status (

in BulkCmIRPConstDefs::SessionId session_id,out BulkCmIRPConstDefs::ErrorInformation error_information

)raises (

BulkCmIRPSystem::GetSessionStatusException,BulkCmIRPSystem::UnknownSessionIdException,ManagedGenericIRPSystem::InvalidParameter);

/*The IRPManager invokes this operation to delete all its temporaryentities and the related sessionId which belong to the scope ofa configuration session. This includes the related error and loginformation too.*/void end_session (


BulkCmIRPSystem::EndSessionException,BulkCmIRPSystem::UnknownSessionIdException,BulkCmIRPSystem::NotValidInCurrentStateException,ManagedGenericIRPSystem::InvalidParameter);

/*The IRPManager invokes this operation to abort an active operationduring a configuration session. It is only effecting

DN03317891Issue 10-1

111



Id:0900d80580942542

a configuration session in state IN_PROGRESS. In this case thecurrent session task is interrupted, e.g. the activating in progress,using best effort strategy, and a state change is notified*/void abort_session_operation (


BulkCmIRPSystem::AbortSessionOperationException,BulkCmIRPSystem::UnknownSessionIdException,BulkCmIRPSystem::NotValidInCurrentStateException,ManagedGenericIRPSystem::InvalidParameter);

/*Returns a list all sessionIds of current running configuration sessions.*/BulkCmIRPConstDefs::SessionIdList get_session_ids ()raises (

BulkCmIRPSystem::GetSessionIdsException);

};

}; // end of module ControlledUploadBulkCMIRPSystem

#endif // _BULKCMIRPSYSTEM_IDL_

112 DN03317891Issue 10-1


Id:0900d80580942542

Appendix C: BulkCMIRPNotifications.idl

13 Appendix C: BulkCMIRPNotifications.idl// File: BulkCMNotifications.idl

#ifndef _BULKCMIRPNOTIFICATIONS_IDL_#define _BULKCMIRPNOTIFICATIONS_IDL_

#include <NotificationIRPNotifications.idl>#include <BulkCmIRPConstDefs.idl>


module BulkCMIRPNotifications{

interface NotifySessionStateChange: NotificationIRPNotifications::Notify{

// This is the type_name (2nd field) of the fixed header.const string EVENT_TYPE =

BulkCmIRPConstDefs::NotificationType::NOTIFY_SESSION_STATE_CHANGED;

// -----------------------------// One of the strings here is the event_name (3rd field) of the// fixed header.// The first 2 are relevant for IS-defined packages Simple// Upload and Controlled Upload.// All are relevant for IS-defined package// Controlled Upload & Provisioning.

const string UPLOAD_FAILED = BulkCmIRPConstDefs::SessionStateChangeNotification::UPLOAD_FAILED;

const string UPLOAD_COMPLETED = BulkCmIRPConstDefs::SessionStateChangeNotification::UPLOAD_COMPLETED;

const string DOWNLOAD_FAILED = BulkCmIRPConstDefs::SessionStateChangeNotification::DOWNLOAD_FAILED;

const string DOWNLOAD_COMPLETED = BulkCmIRPConstDefs::SessionStateChangeNotification::DOWNLOAD_COMPLETED;

const string ACTIVATION_FAILED = BulkCmIRPConstDefs::SessionStateChangeNotification::ACTIVATION_FAILED;

const string ACTIVATION_PARTLY_REALISED = BulkCmIRPConstDefs::SessionStateChangeNotification::ACTIVATION_PARTLY_REALISED;

const string ACTIVATION_COMPLETED = BulkCmIRPConstDefs::SessionStateChangeNotification::ACTIVATION_COMPLETED;

const string FALLBACK_FAILED = BulkCmIRPConstDefs::SessionStateChangeNotification::FALLBACK_FAILED;

const string FALLBACK_PARTLY_REALISED = BulkCmIRPConstDefs::SessionStateChangeNotification::FALLBACK_PARTLY_REALISED;

const string FALLBACK_COMPLETED = BulkCmIRPConstDefs::SessionStateChangeNotification::FALLBACK_COMPLETED;

const string VALIDATION_FAILED = BulkCmIRPConstDefs::

DN03317891Issue 10-1

113


Appendix C: BulkCMIRPNotifications.idl

Id:0900d80580942542

SessionStateChangeNotification::VALIDATION_FAILED;const string VALIDATION_COMPLETED = BulkCmIRPConstDefs::

SessionStateChangeNotification::VALIDATION_COMPLETED;const string PREACTIVATION_FAILED = BulkCmIRPConstDefs::

SessionStateChangeNotification::PREACTIVATION_FAILED;const string PREACTIVATION_PARTLY_REALISED = BulkCmIRPConstDefs::

SessionStateChangeNotification::PREACTIVATION_PARTLY_REALISED;const string PREACTIVATION_COMPLETED = BulkCmIRPConstDefs::

SessionStateChangeNotification::PREACTIVATION_COMPLETED;// ------------------------------

const string SESSION_ID =BulkCmIRPConstDefs::AttributeNameValue::SESSION_ID;

const string SOURCE_INDICATOR =BulkCmIRPConstDefs::AttributeNameValue::SOURCE_INDICATOR;

};

interface NotifyGetSessionLogEnded: NotificationIRPNotifications::Notify{

// This is the type_name (2nd field) of the fixed header.const string EVENT_TYPE =

BulkCmIRPConstDefs::NotificationType::NOTIFY_GET_SESSION_LOG_ENDED;

// -----------------// One of the 2 strings here is the event_name (3rd field) of the// fixed header.const string GET_SESSION_LOG_COMPLETED_SUCCESSFULLY =

BulkCmIRPConstDefs::LogStateNotification::GET_SESSION_LOG_COMPLETED_SUCCESSFULLY;

const string GET_SESSION_LOG_COMPLETED_UNSUCESSFULLY =BulkCmIRPConstDefs::LogStateNotification::

GET_SESSION_LOG_COMPLETED_UNSUCESSFULLY;// ----------------------

const string SESSION_ID =BulkCmIRPConstDefs::AttributeNameValue::SESSION_ID;

const string SOURCE_INDICATOR =BulkCmIRPConstDefs::AttributeNameValue::SOURCE_INDICATOR;

};

};

#endif // _BULKCMIRPNOTIFICATIONS_IDL_

114 DN03317891Issue 10-1


Id:0900d80580942542

Appendix D: LTE RL40 3GPP XML file example

14 Appendix D: LTE RL40 3GPP XML file example

<?xml version="1.0" encoding="UTF-8"?><bulkCmConfigDataFile xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"xmlns="http://www.3gpp.org/ftp/specs/archive/32_series/32.615#configData"xmlns:gn="http://www.3gpp.org/ftp/specs/archive/32_series/32.655#geranNrm"xmlns:sm="http://www.3gpp.org/ftp/specs/archive/32_series/32.675#stateManagementIRP"xmlns:un="http://www.3gpp.org/ftp/specs/archive/32_series/32.645#utranNrm"xmlns:xn="http://www.3gpp.org/ftp/specs/archive/32_series/32.625#genericNrm"xmlns:cn="http://www.3gpp.org/ftp/specs/archive/32_series/32.635#coreNrm"xmlns:stn="http://www.3gpp.org/ftp/specs/archive/32_series/32.745#stnNrm"xmlns:en="http://www.3gpp.org/ftp/specs/archive/32_series/32.765#eutranNrm"xmlns:epc="http://www.3gpp.org/ftp/specs/archive/32_series/32.755#epcNrm"><fileHeader fileFormatVersion="32.615 V6.2" vendorName="Nokia Siemens Networks"/><configData dnPrefix="DC=com.nsn"><xn:SubNetwork id="Nokia-511115"><xn:ManagedElement id="MRBTS-20050"><xn:attributes><xn:userLabel></xn:userLabel><xn:vendorName>Nokia Siemens Networks</xn:vendorName><xn:locationName></xn:locationName><xn:managedBy>SubNetwork=Nokia-511115,ManagementNode=OMC-511115</xn:managedBy><xn:swVersion>LN3.0</xn:swVersion><xn:managedElementType><xn:strItem>MRBTS</xn:strItem></xn:managedElementType></xn:attributes><xn:VsDataContainer id="MRBTS-20050"><xn:attributes><xn:vsDataType>MRBTS</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><MRBTSxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><AutoConnHWID></AutoConnHWID><AutoConnSiteID></AutoConnSiteID><autoConfMode>0</autoConfMode><autoConfPlanName>LD_mrbts_pronto</autoConfPlanName><autoConfPlanReady>0</autoConfPlanReady><autoConfSWPackage></autoConfSWPackage><autoConfStatus>0</autoConfStatus><siteTemplateDescription></siteTemplateDescription><siteTemplateName></siteTemplateName><actEthernetSec>0</actEthernetSec><altitude></altitude><autoConHWId></autoConHWId><autoConSiteId></autoConSiteId><autoConfBlocked>0</autoConfBlocked><commissioningRequired>0</commissioningRequired><latitude></latitude>

DN03317891Issue 10-1

115



Id:0900d80580942542

<longitude></longitude><passUnitList></passUnitList><resetToTestDedicated>0</resetToTestDedicated><timeZone>323</timeZone><unitList><Item><primaryConnection>1</primaryConnection><prodCode>471894A</prodCode><unitName>FR</unitName><unitNumber>1</unitNumber><variant>HA</variant></Item><Item><primaryConnection>0</primaryConnection><prodCode>471469A</prodCode><unitName>FSM</unitName><unitNumber>1</unitNumber><variant>E</variant></Item></unitList></MRBTS></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="BTSSCL-1/LCELL-1"><xn:attributes><xn:vsDataType>LCELL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LCELLxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><resourceList><Item><antlId>1</antlId><txRxUsage>0</txRxUsage></Item><Item><antlId>2</antlId><txRxUsage>2</txRxUsage></Item></resourceList></LCELL></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>LCELL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LCELLxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><resourceList><Item><antlId>5</antlId><txRxUsage>0</txRxUsage></Item></resourceList>

116 DN03317891Issue 10-1


Id:0900d80580942542


</LCELL></xn:attributes></xn:VsDataContainer><en:ENBFunction id="LNBTS-20050"><en:attributes><en:x2IpAddressList>10.46.156.50</en:x2IpAddressList></en:attributes><xn:VsDataContainer id="LNBTS-20050"><xn:attributes><xn:vsDataType>LNBTS</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNBTSxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><mcc>555</mcc><mnc>10</mnc><name></name><division></division><glbNbEnbIdX2LinkBlacklist></glbNbEnbIdX2LinkBlacklist><imsEmerPlmnConfig></imsEmerPlmnConfig><pciIpAdrMap></pciIpAdrMap><actCSFBRedir>0</actCSFBRedir><actCellTrace>0</actCellTrace><actCiphering>1</actCiphering><actConvVoice>0</actConvVoice><actDistributedSite>0</actDistributedSite><actEmerCallRedir>0</actEmerCallRedir><actFlexBbUsage>0</actFlexBbUsage><actHOtoWcdma>0</actHOtoWcdma><actIMSEmerSessR9>0</actIMSEmerSessR9><actIfHo>0</actIfHo><actImmHRPD>0</actImmHRPD><actImmXrtt>0</actImmXrtt><actLTES1Ho>0</actLTES1Ho><actLocRep>0</actLocRep><actMultBearers>1</actMultBearers><actNonGbrServiceDiff>1</actNonGbrServiceDiff><actOperatorQCI>0</actOperatorQCI><actPdcpRohc>0</actPdcpRohc><actPeriodicIntraUeMeas>0</actPeriodicIntraUeMeas><actRedirect>0</actRedirect><actRfChaining>0</actRfChaining><actS1Flex>1</actS1Flex><actSelMobPrf>0</actSelMobPrf><actSubscriberTrace>0</actSubscriberTrace><actUeBasedAnrIntraFreqLte>1</actUeBasedAnrIntraFreqLte><acteNACCtoGSM>0</acteNACCtoGSM><amRlcPBTab1dlPollByte>0</amRlcPBTab1dlPollByte><amRlcPBTab1ueCategory>1</amRlcPBTab1ueCategory><amRlcPBTab1ulPollByte>1</amRlcPBTab1ulPollByte><amRlcPBTab2dlPollByte>4</amRlcPBTab2dlPollByte><amRlcPBTab2ueCategory>2</amRlcPBTab2ueCategory><amRlcPBTab2ulPollByte>5</amRlcPBTab2ulPollByte>

DN03317891Issue 10-1

117



Id:0900d80580942542

<amRlcPBTab3dlPollByte>5</amRlcPBTab3dlPollByte<amRlcPBTab3ueCategory>3</amRlcPBTab3ueCategory><amRlcPBTab3ulPollByte>7</amRlcPBTab3ulPollByte><amRlcPBTab4dlPollByte>5</amRlcPBTab4dlPollByte><amRlcPBTab4ueCategory>4</amRlcPBTab4ueCategory><amRlcPBTab4ulPollByte>8</amRlcPBTab4ulPollByte><amRlcPBTab5dlPollByte>6</amRlcPBTab5dlPollByte><amRlcPBTab5ueCategory>5</amRlcPBTab5ueCategory><amRlcPBTab5ulPollByte>9</amRlcPBTab5ulPollByte><anrOmExtEnable>0</anrOmExtEnable><btsResetRequest></btsResetRequest><eea0>1</eea0><eea1>9</eea1><eea2>1</eea2><enableAutoLock>1</enableAutoLock><enableGrflShdn>1</enableGrflShdn><enbName></enbName><eia0>1</eia0><eia1>9</eia1><eia2>1</eia2><keyRefrMarg>50000</keyRefrMarg><nullFallback>1</nullFallback><operationalState>5</operationalState><pbrNonGbr>2</pbrNonGbr><pdcpProf1pdcpProfileId>1</pdcpProf1pdcpProfileId><pdcpProf1statusRepReq>3</pdcpProf1statusRepReq><pdcpProf1tDiscard>2</pdcpProf1tDiscard><pdcpProf101pdcpProfileId>101</pdcpProf101pdcpProfileId><pdcpProf101rohcMaxCid>4</pdcpProf101rohcMaxCid><pdcpProf101snSize>0</pdcpProf101snSize><pdcpProf101tDiscard>0</pdcpProf101tDiscard><pdcpProf102pdcpProfileId>102</pdcpProf102pdcpProfileId><pdcpProf102snSize>0</pdcpProf102snSize><pdcpProf102tDiscard>1</pdcpProf102tDiscard><pdcpProf2pdcpProfileId>2</pdcpProf2pdcpProfileId><pdcpProf2statusRepReq>3</pdcpProf2statusRepReq><pdcpProf2tDiscard>2</pdcpProf2tDiscard><pdcpProf3pdcpProfileId>3</pdcpProf3pdcpProfileId><pdcpProf3statusRepReq>3</pdcpProf3statusRepReq><pdcpProf3tDiscard>2</pdcpProf3tDiscard><pdcpProf4pdcpProfileId>4</pdcpProf4pdcpProfileId><pdcpProf4statusRepReq>3</pdcpProf4statusRepReq><pdcpProf4tDiscard>2</pdcpProf4tDiscard><pdcpProf5pdcpProfileId>5</pdcpProf5pdcpProfileId><pdcpProf5statusRepReq>3</pdcpProf5statusRepReq><pdcpProf5tDiscard>2</pdcpProf5tDiscard><prioTopoHO>0</prioTopoHO><qciTab1delayTarget>3</qciTab1delayTarget><qciTab1drxProfileIndex>2</qciTab1drxProfileIndex<qciTab1dscp>46</qciTab1dscp><qciTab1lcgid>1</qciTab1lcgid>

118 DN03317891Issue 10-1


Id:0900d80580942542


<qciTab1pdcpProfIdx>101</qciTab1pdcpProfIdx><qciTab1prio>2</qciTab1prio><qciTab1qci>1</qciTab1qci><qciTab1qciSupp>1</qciTab1qciSupp><qciTab1resType>0</qciTab1resType><qciTab1rlcMode>0</qciTab1rlcMode><qciTab1rlcProfIdx>101</qciTab1rlcProfIdx><qciTab1schedulBSD>1</qciTab1schedulBSD><qciTab1schedulPrio>5</qciTab1schedulPrio><qciTab2drxProfileIndex>2</qciTab2drxProfileIndex><qciTab2dscp>26</qciTab2dscp><qciTab2lcgid>2</qciTab2lcgid><qciTab2pdcpProfIdx>102</qciTab2pdcpProfIdx><qciTab2prio>4</qciTab2prio><qciTab2qci>2</qciTab2qci><qciTab2qciSupp>0</qciTab2qciSupp><qciTab2resType>0</qciTab2resType><qciTab2rlcMode>0</qciTab2rlcMode><qciTab2rlcProfIdx>102</qciTab2rlcProfIdx><qciTab2schedulBSD>1</qciTab2schedulBSD><qciTab2schedulPrio>7</qciTab2schedulPrio><qciTab3drxProfileIndex>2</qciTab3drxProfileIndex><qciTab3dscp>46</qciTab3dscp><qciTab3lcgid>2</qciTab3lcgid><qciTab3pdcpProfIdx>102</qciTab3pdcpProfIdx><qciTab3prio>3</qciTab3prio><qciTab3qci>3</qciTab3qci><qciTab3qciSupp>0</qciTab3qciSupp><qciTab3resType>0</qciTab3resType><qciTab3rlcMode>0</qciTab3rlcMode><qciTab3rlcProfIdx>102</qciTab3rlcProfIdx><qciTab3schedulBSD>1</qciTab3schedulBSD><qciTab3schedulPrio>6</qciTab3schedulPrio><qciTab4drxProfileIndex>2</qciTab4drxProfileIndex><qciTab4dscp>28</qciTab4dscp><qciTab4lcgid>2</qciTab4lcgid><qciTab4pdcpProfIdx>2</qciTab4pdcpProfIdx><qciTab4prio>4</qciTab4prio><qciTab4qci>4</qciTab4qci><qciTab4qciSupp>0</qciTab4qciSupp><qciTab4resType>0</qciTab4resType><qciTab4rlcMode>0</qciTab4rlcMode><qciTab4rlcProfIdx>2</qciTab4rlcProfIdx><qciTab4schedulBSD>3</qciTab4schedulBSD><qciTab4schedulPrio>8</qciTab4schedulPrio><qciTab5drxProfileIndex>3</qciTab5drxProfileIndex><qciTab5dscp>34</qciTab5dscp><qciTab5lcgid>2</qciTab5lcgid><qciTab5pdcpProfIdx>1</qciTab5pdcpProfIdx><qciTab5prio>1</qciTab5prio><qciTab5qci>5</qciTab5qci>

DN03317891Issue 10-1

119



Id:0900d80580942542

<qciTab5qciSupp>1</qciTab5qciSupp><qciTab5resType>1</qciTab5resType><qciTab5rlcMode>0</qciTab5rlcMode><qciTab5rlcProfIdx>1</qciTab5rlcProfIdx><qciTab5schedulBSD>1</qciTab5schedulBSD><qciTab5schedulPrio>9</qciTab5schedulPrio><qciTab5schedulType>1</qciTab5schedulType><qciTab5schedulWeight>40</qciTab5schedulWeight><qciTab6drxProfileIndex>3</qciTab6drxProfileIndex><qciTab6dscp>18</qciTab6dscp><qciTab6lcgid>3</qciTab6lcgid><qciTab6pdcpProfIdx>1</qciTab6pdcpProfIdx><qciTab6prio>6</qciTab6prio><qciTab6qci>6</qciTab6qci><qciTab6qciSupp>1</qciTab6qciSupp><qciTab6resType>1</qciTab6resType><qciTab6rlcMode>0</qciTab6rlcMode><qciTab6rlcProfIdx>1</qciTab6rlcProfIdx><qciTab6schedulBSD>3</qciTab6schedulBSD><qciTab6schedulPrio>9</qciTab6schedulPrio><qciTab6schedulWeight>20</qciTab6schedulWeight><qciTab7drxProfileIndex>3</qciTab7drxProfileIndex><qciTab7dscp>28</qciTab7dscp><qciTab7lcgid>2</qciTab7lcgid><qciTab7pdcpProfIdx>1</qciTab7pdcpProfIdx><qciTab7prio>7</qciTab7prio><qciTab7qci>7</qciTab7qci><qciTab7qciSupp>1</qciTab7qciSupp><qciTab7resType>1</qciTab7resType><qciTab7rlcMode>0</qciTab7rlcMode><qciTab7rlcProfIdx>1</qciTab7rlcProfIdx><qciTab7schedulBSD>1</qciTab7schedulBSD><qciTab7schedulPrio>10</qciTab7schedulPrio><qciTab7schedulWeight>10</qciTab7schedulWeight><qciTab8drxProfileIndex>3</qciTab8drxProfileIndex><qciTab8dscp>10</qciTab8dscp><qciTab8lcgid>3</qciTab8lcgid><qciTab8pdcpProfIdx>1</qciTab8pdcpProfIdx><qciTab8prio>8</qciTab8prio><qciTab8qci>8</qciTab8qci><qciTab8qciSupp>1</qciTab8qciSupp><qciTab8resType>1</qciTab8resType><qciTab8rlcMode>0</qciTab8rlcMode><qciTab8rlcProfIdx>1</qciTab8rlcProfIdx><qciTab8schedulBSD>3</qciTab8schedulBSD><qciTab8schedulPrio>11</qciTab8schedulPrio><qciTab8schedulWeight>5</qciTab8schedulWeight><qciTab9drxProfileIndex>3</qciTab9drxProfileIndex><qciTab9dscp>0</qciTab9dscp><qciTab9lcgid>3</qciTab9lcgid><qciTab9pdcpProfIdx>1</qciTab9pdcpProfIdx>

120 DN03317891Issue 10-1


Id:0900d80580942542


<qciTab9prio>9</qciTab9prio><qciTab9qci>9</qciTab9qci><qciTab9qciSupp>1</qciTab9qciSupp><qciTab9resType>1</qciTab9resType><qciTab9rlcMode>0</qciTab9rlcMode><qciTab9rlcProfIdx>1</qciTab9rlcProfIdx><qciTab9schedulBSD>3</qciTab9schedulBSD><qciTab9schedulPrio>12</qciTab9schedulPrio><qciTab9schedulWeight>1</qciTab9schedulWeight><qciTabOperator></qciTabOperator><rlcProf1pollPdu>2</rlcProf1pollPdu><rlcProf1rlcProfileId>1</rlcProf1rlcProfileId><rlcProf1tPollRetr>49</rlcProf1tPollRetr><rlcProf1tProhib>10</rlcProf1tProhib><rlcProf1tReord>10</rlcProf1tReord><rlcProf101rlcProfileId>101</rlcProf101rlcProfileId><rlcProf101snFieldLengthDL>0</rlcProf101snFieldLengthDL><rlcProf101snFieldLengthUL>0</rlcProf101snFieldLengthUL><rlcProf101tReord>10</rlcProf101tReord><rlcProf102rlcProfileId>102</rlcProf102rlcProfileId><rlcProf102snFieldLengthDL>0</rlcProf102snFieldLengthDL><rlcProf102snFieldLengthUL>0</rlcProf102snFieldLengthUL><rlcProf102tReord>10</rlcProf102tReord><rlcProf2pollPdu>0</rlcProf2pollPdu><rlcProf2rlcProfileId>2</rlcProf2rlcProfileId><rlcProf2tPollRetr>23</rlcProf2tPollRetr><rlcProf2tProhib>10</rlcProf2tProhib><rlcProf2tReord>10</rlcProf2tReord><rlcProf3pollPdu>0</rlcProf3pollPdu><rlcProf3rlcProfileId>3</rlcProf3rlcProfileId><rlcProf3tPollRetr>23</rlcProf3tPollRetr><rlcProf3tProhib>10</rlcProf3tProhib><rlcProf3tReord>10</rlcProf3tReord><rlcProf4pollPdu>4</rlcProf4pollPdu><rlcProf4rlcProfileId>4</rlcProf4rlcProfileId><rlcProf4tPollRetr>23</rlcProf4tPollRetr><rlcProf4tProhib>10</rlcProf4tProhib><rlcProf4tReord>10</rlcProf4tReord><rlcProf5pollPdu>4</rlcProf5pollPdu><rlcProf5rlcProfileId>5</rlcProf5rlcProfileId><rlcProf5tPollRetr>23</rlcProf5tPollRetr><rlcProf5tProhib>10</rlcProf5tProhib><rlcProf5tReord>10</rlcProf5tReord><shutdownStepAmount>6</shutdownStepAmount><shutdownWindow>60</shutdownWindow><systemInformationListWCDMA></systemInformationListWCDMA><tS1RelPrepL>150</tS1RelPrepL><tS1RelPrepU>500</tS1RelPrepU><tagMaxAM>10</tagMaxAM><tagMaxUM>10</tagMaxUM></LNBTS>

DN03317891Issue 10-1

121



Id:0900d80580942542

</xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/SYNC-1/STPG-1"><xn:attributes><xn:vsDataType>STPG</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><STPGxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><synchroSourceList></synchroSourceList></STPG></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/TAC-1/LTAC-1"><xn:attributes><xn:vsDataType>LTAC</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LTAC xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><tacActivityFactor>1</tacActivityFactor><tacExludeL2Overhead>0</tacExludeL2Overhead><tacLimitGbrEmergency>1000000</tacLimitGbrEmergency><tacLimitGbrHandover>1000000</tacLimitGbrHandover><tacLimitGbrNormal>1000000</tacLimitGbrNormal></LTAC></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/QOS-1"><xn:attributes><xn:vsDataType>QOS</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><QOSxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><dscpMap><Item><dscp>46</dscp><pHB>0</pHB><vlanPrio>6</vlanPrio></Item></dscpMap><enablePhbCounters>0</enablePhbCounters><assuredForwardingClass1>10</assuredForwardingClass1><assuredForwardingClass2>100</assuredForwardingClass2><assuredForwardingClass3>1000</assuredForwardingClass3><assuredForwardingClass4>10000</assuredForwardingClass4><bestEffort>1</bestEffort><sseDscpOverwrite>0</sseDscpOverwrite><trafficTypesMap><Item><dscp>46</dscp><trafficType>CPLANE</trafficType></Item><Item><dscp>34</dscp>

122 DN03317891Issue 10-1


Id:0900d80580942542


<trafficType>MPLANE</trafficType></Item></trafficTypesMap></QOS></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/IPRM-1"><xn:attributes><xn:vsDataType>IPRM</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IPRM xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><RmExceptions></RmExceptions></IPRM></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/IEIF-1"><xn:attributes><xn:vsDataType>IEIF</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IEIF xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><localIpAddr>10.46.156.50</localIpAddr><mtu>1500</mtu><netmask>255.255.255.0</netmask><qosEnabled>1</qosEnabled><sbs>1522</sbs><sbsTotal>1522</sbsTotal><sir>1000000</sir><sirTotal>1000000</sirTotal><trafficPathShapingEnable>2</trafficPathShapingEnable><upperLayerShaping>0</upperLayerShaping><wfqSchedQueueWeight>1</wfqSchedQueueWeight></IEIF></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>BFDGRP</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><BFDGRP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"/></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/BFDGRP-1"><xn:attributes><xn:vsDataType>BFDGRP</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><BFDGRP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"/></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>BFDGRP</xn:vsDataType>

DN03317891Issue 10-1

123



Id:0900d80580942542

<xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><BFDGRP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"/></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/TOPIK-1"><xn:attributes><xn:vsDataType>TOPIK</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><TOPIK xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><administrativeState>0</administrativeState><logMeanSyncValue>-3</logMeanSyncValue><masterIpAddr>10.44.34.45</masterIpAddr></TOPIK></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/IHCP-1"><xn:attributes><xn:vsDataType>IHCP</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IHCP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><client_identifier></client_identifier><hardware_identifier></hardware_identifier><dhcpRangeEnd></dhcpRangeEnd><dhcpRangeStart></dhcpRangeStart></IHCP></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/INTP-1"><xn:attributes><xn:vsDataType>INTP</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><INTP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><ntpServers><Item>10.46.151.43</Item></ntpServers></INTP></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/IPRT-1"><xn:attributes><xn:vsDataType>IPRT</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IPRT xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><staticRoutes><Item><bfdId>0</bfdId><destIpAddr>0.0.0.0</destIpAddr><gateway>10.46.156.254</gateway><netmask>0.0.0.0</netmask><preference>1</preference>

124 DN03317891Issue 10-1


Id:0900d80580942542


</Item></staticRoutes></IPRT></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/IPNO-1/IDNS-1"><xn:attributes><xn:vsDataType>IDNS</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IDNS xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><serverIpAddress>10.44.35.81</serverIpAddress><serverIpAddress2>0.0.0.0</serverIpAddress2></IDNS></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>ETHLK</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><ETHLK xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><administrativeState>0</administrativeState><discardUntagged>0</discardUntagged><l2BurstSize>0</l2BurstSize><l2IngressRate>0</l2IngressRate><l2ShaperRate>0</l2ShaperRate><l2SwitchingMode>0</l2SwitchingMode><l2VlanIdList></l2VlanIdList><linkOAMEnabled>0</linkOAMEnabled><linkOAMProfile></linkOAMProfile><macAddr>00:40:43:6c:4b:ae</macAddr><speedAndDuplex>0</speedAndDuplex></ETHLK></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="FTM-1/ETHLK-1-1"><xn:attributes><xn:vsDataType>ETHLK</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><ETHLK xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><administrativeState>0</administrativeState><discardUntagged>0</discardUntagged><l2BurstSize>0</l2BurstSize><l2IngressRate>0</l2IngressRate><l2ShaperRate>0</l2ShaperRate><l2SwitchingMode>0</l2SwitchingMode><l2VlanIdList></l2VlanIdList><linkOAMEnabled>0</linkOAMEnabled><linkOAMProfile></linkOAMProfile><macAddr>00:40:43:6c:4b:ae</macAddr><speedAndDuplex>0</speedAndDuplex></ETHLK></xn:attributes>

DN03317891Issue 10-1

125



Id:0900d80580942542

</xn:VsDataContainer><xn:attributes><xn:vsDataType>IRFIM</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IRFIM xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><dlCarFrqEut>25000</dlCarFrqEut><eutCelResPrio></eutCelResPrio><intFrBCList></intFrBCList><intFrNCList></intFrNCList><interFrqThrH>34</interFrqThrH><interFrqThrL>2</interFrqThrL><interPresAntP>0</interPresAntP><interTResEut>4</interTResEut><measBdw>3</measBdw><pMaxInterF></pMaxInterF><qOffFrq>15</qOffFrq><qRxLevMinInterF>-68</qRxLevMinInterF><eutResTiFHM></eutResTiFHM><eutResTiFMM></eutResTiFMM></IRFIM></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="LNCEL-2/IAFIM-1"><xn:attributes><xn:vsDataType>IAFIM</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IAFIM xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><intrFrBCList><Item><startIntraPci>0</startIntraPci></Item></intrFrBCList><intrFrNCList><Item><physCellIdNcl>151</physCellIdNcl><qOffsetCell>15</qOffsetCell></Item></intrFrNCList></IAFIM></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>PPTT</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><PPTT xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><administrativeState>0</administrativeState><pdhLbo>1</pdhLbo><pdhLineType>2</pdhLineType></PPTT></xn:attributes></xn:VsDataContainer>

126 DN03317891Issue 10-1


Id:0900d80580942542


<xn:VsDataContainer id="FTM-1/CERTH-1"><xn:attributes><xn:vsDataType>CERTH</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><CERTH xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><btsCertificateUpdateTime>30</btsCertificateUpdateTime><caCertificateUpdateTime>30</caCertificateUpdateTime><caSubjectName>C=FI, O=NSN, CN=MRTAmpereNewRootCA</caSubjectName><cmpServerIpAddress>10.8.207.54</cmpServerIpAddress><cmpServerPort>8080</cmpServerPort><crlUpdatePeriod>24</crlUpdatePeriod></CERTH></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>L2SWI</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><L2SWI xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><dscpMap><Item><dscp>0</dscp><priorityQueue>6</priorityQueue></Item><Item><dscp>1</dscp><priorityQueue>6</priorityQueue></Item></dscpMap><enableLayer2Switching>0</enableLayer2Switching><l2PriorityQueueWeight2>8</l2PriorityQueueWeight2><priorityQueueNonIP>1</priorityQueueNonIP><priorityQueuePcp0>6</priorityQueuePcp0><priorityQueuePcp7>1</priorityQueuePcp7><priorityQueueUntagged>1</priorityQueueUntagged><qosClassification>0</qosClassification></L2SWI></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>IRFIM</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><IRFIM xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><dlCarFrqEut>25000</dlCarFrqEut><eutCelResPrio></eutCelResPrio><intFrBCList></intFrBCList><intFrNCList></intFrNCList><interFrqThrH>34</interFrqThrH><interFrqThrL>2</interFrqThrL><interPresAntP>0</interPresAntP><interTResEut>4</interTResEut><measBdw>3</measBdw>

DN03317891Issue 10-1

127



Id:0900d80580942542

<pMaxInterF></pMaxInterF><qOffFrq>15</qOffFrq><qRxLevMinInterF>-68</qRxLevMinInterF><eutResTiFHM></eutResTiFHM><eutResTiFMM></eutResTiFMM></IRFIM></xn:attributes></xn:VsDataContainer><en:EUtranCellFDD id="LNCEL-3"><en:attributes><en:cellIdentity></en:cellIdentity><en:cellType>Macro</en:cellType><en:cellSize>large</en:cellSize><en:tac>123</en:tac><en:pci>152</en:pci><en:maximumTransmissionPower>5</en:maximumTransmissionPower><en:earfcnDl>3050</en:earfcnDl><en:earfcnUl>21050</en:earfcnUl><en:referenceSignalPower>-15</en:referenceSignalPower><en:pLMNIdList><en:pLMNId><en:mcc>555</en:mcc><en:mnc>10</en:mnc></en:pLMNId></en:pLMNIdList><en:operationalState>Enabled</en:operationalState><en:administrativeState>Unlocked</en:administrativeState></en:attributes><xn:VsDataContainer id="LNCEL-3"><xn:attributes><xn:vsDataType>LNCEL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNCEL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><angle></angle><furtherPlmnIdL></furtherPlmnIdL><name></name><expectedCellRange></expectedCellRange><rachDensity></rachDensity><a1TimeToTriggerDeactInterMeas>16</a1TimeToTriggerDeactInterMeas><a2TimeToTriggerActGERANMeas></a2TimeToTriggerActGERANMeas><ulsMinTbs>104</ulsMinTbs><ulsSchedMethod>0</ulsSchedMethod><useId></useId></LNCEL></xn:attributes></xn:VsDataContainer><en:EUtranRelation id="LNADJ-62/LNADJL-2"><en:attributes><en:tCI>55510144</en:tCI><en:isRemoveAllowed>false</en:isRemoveAllowed><en:adjacentCell>SubNetwork=Nokia-511115,ManagedElement=MRBTS-

128 DN03317891Issue 10-1


Id:0900d80580942542


20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1</en:adjacentCell><en:isHOAllowed>yes</en:isHOAllowed></en:attributes><xn:VsDataContainer id="LNADJ-62/LNADJL-2"><xn:attributes><xn:vsDataType>LNADJL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNADJL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><bcPlmnIdList><Item><mcc>555</mcc><mnc>10</mnc></Item></bcPlmnIdList><mcc>555</mcc><mnc>10</mnc><dlTrmBw>3</dlTrmBw><ecgiAdjEnbId>48</ecgiAdjEnbId><ecgiLcrId>1</ecgiLcrId><fDlEarfcn>3050</fDlEarfcn><fUlEarfcn>21050</fUlEarfcn><phyCellId>144</phyCellId><sourceOfData>0</sourceOfData><tac>123</tac><ulTrmBw>3</ulTrmBw><validityOfData>1</validityOfData></LNADJL></xn:attributes></xn:VsDataContainer></en:EUtranRelation></en:EUtranCellFDD><en:EUtranCellFDD id="LNCEL-2"><en:attributes><en:cellIdentity></en:cellIdentity><en:cellType>Macro</en:cellType><en:cellSize>large</en:cellSize><en:tac>123</en:tac><en:pci>151</en:pci><en:maximumTransmissionPower>5</en:maximumTransmissionPower><en:earfcnDl>3050</en:earfcnDl><en:earfcnUl>21050</en:earfcnUl><en:referenceSignalPower>-15</en:referenceSignalPower><en:pLMNIdList><en:pLMNId><en:mcc>555</en:mcc><en:mnc>10</en:mnc></en:pLMNId></en:pLMNIdList><en:operationalState>Enabled</en:operationalState><en:administrativeState>Unlocked</en:administrativeState></en:attributes>

DN03317891Issue 10-1

129



Id:0900d80580942542

<xn:VsDataContainer id="LNCEL-2"><xn:attributes><xn:vsDataType>LNCEL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNCEL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><angle></angle><furtherPlmnIdL></furtherPlmnIdL><name></name><expectedCellRange></expectedCellRange><rachDensity></rachDensity><a1TimeToTriggerDeactInterMeas>16</a1TimeToTriggerDeactInterMeas><a2TimeToTriggerActGERANMeas></a2TimeToTriggerActGERANMeas></LNCEL></xn:attributes></xn:VsDataContainer><en:EUtranRelation id="LNADJ-62/LNADJL-2"><en:attributes><en:tCI>55510144</en:tCI><en:isRemoveAllowed>false</en:isRemoveAllowed><en:adjacentCell>SubNetwork=Nokia-511115,ManagedElement=MRBTS-20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1</en:adjacentCell><en:isHOAllowed>yes</en:isHOAllowed></en:attributes><xn:VsDataContainer id="LNADJ-62/LNADJL-2"><xn:attributes><xn:vsDataType>LNADJL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNADJLxmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><bcPlmnIdList><Item><mcc>555</mcc><mnc>10</mnc></Item></bcPlmnIdList><mcc>555</mcc><mnc>10</mnc><dlTrmBw>3</dlTrmBw><ecgiAdjEnbId>48</ecgiAdjEnbId><ecgiLcrId>1</ecgiLcrId><fDlEarfcn>3050</fDlEarfcn><fUlEarfcn>21050</fUlEarfcn><phyCellId>144</phyCellId><sourceOfData>0</sourceOfData><tac>123</tac><ulTrmBw>3</ulTrmBw><validityOfData>1</validityOfData></LNADJL></xn:attributes></xn:VsDataContainer></en:EUtranRelation></en:EUtranCellFDD>

130 DN03317891Issue 10-1


Id:0900d80580942542


<xn:VsDataContainer id="FTM-1"><xn:attributes><xn:vsDataType>FTM</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><FTM xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><name></name><locationName>SyVe_Ulm</locationName><softwareReleaseVersion>FTM_L30_196.00</softwareReleaseVersion><systemTitle>LTE50</systemTitle><userLabel></userLabel></FTM></xn:attributes></xn:VsDataContainer><en:EUtranCellFDD id="LNCEL-1"><en:attributes><en:cellIdentity></en:cellIdentity><en:cellType>Macro</en:cellType><en:cellSize>large</en:cellSize><en:tac>123</en:tac><en:pci>150</en:pci><en:maximumTransmissionPower>5</en:maximumTransmissionPower><en:earfcnDl>3050</en:earfcnDl><en:earfcnUl>21050</en:earfcnUl><en:referenceSignalPower>-15</en:referenceSignalPower><en:pLMNIdList><en:pLMNId><en:mcc>555</en:mcc><en:mnc>10</en:mnc></en:pLMNId></en:pLMNIdList><en:operationalState>Enabled</en:operationalState><en:administrativeState>Unlocked</en:administrativeState></en:attributes><xn:VsDataContainer id="LNCEL-1"><xn:attributes><xn:vsDataType>LNCEL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNCEL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><angle></angle><furtherPlmnIdL></furtherPlmnIdL><name></name><expectedCellRange></expectedCellRange><rachDensity></rachDensity><a1TimeToTriggerDeactInterMeas>16</a1TimeToTriggerDeactInterMeas><a2TimeToTriggerActGERANMeas></a2TimeToTriggerActGERANMeas><useId></useId></LNCEL></xn:attributes></xn:VsDataContainer><en:EUtranRelation id="LNADJ-62/LNADJL-2"><en:attributes>

DN03317891Issue 10-1

131



Id:0900d80580942542

<en:tCI>55510144</en:tCI><en:isRemoveAllowed>false</en:isRemoveAllowed><en:adjacentCell>SubNetwork=Nokia-511115,ManagedElement=MRBTS-20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1</en:adjacentCell><en:isHOAllowed>yes</en:isHOAllowed></en:attributes><xn:VsDataContainer id="LNADJ-62/LNADJL-2"><xn:attributes><xn:vsDataType>LNADJL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNADJL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><bcPlmnIdList><Item><mcc>555</mcc><mnc>10</mnc></Item></bcPlmnIdList><mcc>555</mcc><mnc>10</mnc><dlTrmBw>3</dlTrmBw><ecgiAdjEnbId>48</ecgiAdjEnbId><ecgiLcrId>1</ecgiLcrId><fDlEarfcn>3050</fDlEarfcn><fUlEarfcn>21050</fUlEarfcn><phyCellId>144</phyCellId><sourceOfData>0</sourceOfData><tac>123</tac><ulTrmBw>3</ulTrmBw><validityOfData>1</validityOfData></LNADJL></xn:attributes></xn:VsDataContainer></en:EUtranRelation></en:EUtranCellFDD><xn:VsDataContainer id="LNMME-0"><xn:attributes><xn:vsDataType>LNMME</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNMME xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><accMmePlmnsList><Item><mcc>555</mcc><mnc>10</mnc></Item></accMmePlmnsList><mcc>555</mcc><mnc>10</mnc><mmeCode>1</mmeCode><mmeGroupId>65531</mmeGroupId><mmeName>01</mmeName><relMmeCap>3</relMmeCap>

132 DN03317891Issue 10-1


Id:0900d80580942542


</LNMME></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="SCTP-1"><xn:attributes><xn:vsDataType>SCTP</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><SCTP xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><assocMaxRetrans>5</assocMaxRetrans><maxTimeSctpSetup>130</maxTimeSctpSetup><pathMaxRetrans>5</pathMaxRetrans><rtoMax>60</rtoMax><rtoMin>1</rtoMin><sctpHeartbeatInterval>30</sctpHeartbeatInterval></SCTP></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>LNADJ</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><LNADJ xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"/></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>ANTL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><ANTL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><UserDefinedState></UserDefinedState><bearing></bearing><latitude></latitude><longitude></longitude><additionalRxGain>0</additionalRxGain><alDcVoltageEnabled>1</alDcVoltageEnabled><antId>5</antId><antennaRoundTripDelay>80</antennaRoundTripDelay><antennaTotalLoss>-30</antennaTotalLoss><communication3gppEnabled>0</communication3gppEnabled><feederVoltage>-1</feederVoltage><mrcProdCode></mrcProdCode><rModId>1</rModId><ulDelay>0</ulDelay><vswrMajorAlarm></vswrMajorAlarm><vswrMinorAlarm></vswrMinorAlarm></ANTL></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="ANTL-1"><xn:attributes><xn:vsDataType>ANTL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><ANTL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0">

DN03317891Issue 10-1

133



Id:0900d80580942542

<UserDefinedState></UserDefinedState><bearing></bearing><latitude></latitude><longitude></longitude><additionalRxGain>0</additionalRxGain><alDcVoltageEnabled>1</alDcVoltageEnabled><antId>0</antId><antennaRoundTripDelay>80</antennaRoundTripDelay><antennaTotalLoss>-30</antennaTotalLoss><communication3gppEnabled>1</communication3gppEnabled><feederVoltage>-1</feederVoltage><mrcProdCode></mrcProdCode><rModId>1</rModId><ulDelay>0</ulDelay><vswrMajorAlarm></vswrMajorAlarm><vswrMinorAlarm></vswrMinorAlarm></ANTL></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>ANTL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><ANTL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><UserDefinedState></UserDefinedState><bearing></bearing><latitude></latitude><longitude></longitude><additionalRxGain>0</additionalRxGain><alDcVoltageEnabled>1</alDcVoltageEnabled><antId>3</antId><antennaRoundTripDelay>80</antennaRoundTripDelay><antennaTotalLoss>-30</antennaTotalLoss><communication3gppEnabled>0</communication3gppEnabled><feederVoltage>-1</feederVoltage><mrcProdCode></mrcProdCode><rModId>1</rModId><ulDelay>0</ulDelay><vswrMajorAlarm></vswrMajorAlarm><vswrMinorAlarm></vswrMinorAlarm></ANTL></xn:attributes></xn:VsDataContainer><xn:VsDataContainer id="BTSSCL-1"><xn:attributes><xn:vsDataType>BTSSCL</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><BTSSCL xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><alToggSuppList><Item><alToggAmount>2</alToggAmount><alToggClearenceTime>120</alToggClearenceTime>

134 DN03317891Issue 10-1


Id:0900d80580942542


<alToggConditonTime>120</alToggConditonTime><faultName>4</faultName><inUse>1</inUse></Item><Item><alToggAmount>2</alToggAmount><alToggClearenceTime>120</alToggClearenceTime><alToggConditonTime>120</alToggConditonTime><faultName>5</faultName><inUse>1</inUse></Item></alToggSuppList><btsId>20050</btsId><btsName>LTE20050</btsName><btsSyncMode>0</btsSyncMode><ext2M048ClkInUse>0</ext2M048ClkInUse><gpsCableLength>2</gpsCableLength><gpsInUse>1</gpsInUse><gpsTotalAntennaLineDelay>0</gpsTotalAntennaLineDelay><ppsTimingOffset>0</ppsTimingOffset><rfSharingEnabled></rfSharingEnabled><tdmSyncInUse>0</tdmSyncInUse></BTSSCL></xn:attributes></xn:VsDataContainer><xn:attributes><xn:vsDataType>RMOD</xn:vsDataType><xn:vsDataFormatVersion>LN3.0</xn:vsDataFormatVersion><RMOD xmlns="http://www.nsn.com/schemas/public/cm/adaptation/3gpp/NOKLTE/LN3.0"><connectionList><Item><linkId>1</linkId><positionInChain>1</positionInChain><sModId>1</sModId></Item></connectionList><extAlList></extAlList><extCtrlList></extCtrlList><moduleLocation>SyVe_Ulm</moduleLocation><prodCode>471894A</prodCode><radioSiteId>0</radioSiteId><serNum>_EMPTY_</serNum></RMOD></xn:attributes></xn:VsDataContainer></en:ENBFunction></xn:ManagedElement></xn:SubNetwork></configData><fileFooter dateTime="2011-08-22T12:37:08+03:00"/>

DN03317891Issue 10-1

135



Id:0900d80580942542

</bulkCmConfigDataFile>

136 DN03317891Issue 10-1


Id:0900d80580942544

Index

Aactivate 24

BBulk Configuration Management IRP 14BulkCmIRPConstDefs.idl 96BulkCMIRPSystem.idl 100

CCM data download 60CM data upload 60

Ddata amounts 53

EEntry Point IRP 14

Ffallback 24file size 54

IIDL files

3GPP 12CosEventChannelAdmin.idl 12CosEventComm.idl 12CosNotification.idl 12CosNotifyChannelAdmin.idl 12CosNotifyComm.idl 12CosNotifyFilter.idl 12Object Management Group 12TimeBase.idl 12

IRPBulk Configuration Management IRP 14CM Bulk Data 15Entry Point 14Notification 15related functionality 14

IRPAgent 9, 13IRPManager 9, 13, 14

MMCCM 10, 13, 24

user 18, 20, 23Mobile Common Configuration Management 10

Nnon -network parameters 8notifications

notifyGetSessionLogEnded 28notifySessionStateChanged 26pull style 26push style 26

notifyGetSessionLogEnded 28notifySessionStateChanged 26NRM 8, 18

Oobject deletion 61object model 56object models

associations 30, 37object rehosting 61

Ppull style 26push style 26

RRAN data 30RNC creation 61roles 13

SstartSession 14supported

network resource models 12notifications 26operations 16

Vvendor specific data 10, 62, 64, 65

schemas 20VSD 9

WWBTS creation 61WCEL creation 61

XXML file example 70

3GPP CORBA Bulk CM Northbound

Documents

Transcript of 3GPP CORBA Bulk CM Northbound