3GPP_CORBA_Bulk_CM_Northbound.pdf

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 w ould like to encourage you as our customer s 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 components. If you should have questions regarding our Environment al Policy or any of the environm ental services we offer, please contact us at Nokia Siemens Networks for any additional information.

3GPP CORBA Bulk CM Northbound Interface Principles

The information in this document i s subject to change without notice and descri bes only the product defined in the introduction of this documentation. This documentation is in tended for the use of Nokia Siemens Networks c ustomers 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 pr ofessional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes customer comments as part of the pr ocess 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 so ftware 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 m aterial errors and omissions. N okia Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whi ch 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 DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING B UT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, 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 DOCUM ENT OR THE INFORMATION IN IT. This documentation and the product it desc ribes 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 Safety This product may present safety risks due to laser, electricity, heat, and other sources of danger. Only trained and qualified personnel may i nstall, operate, maintain or otherwise handle this product and only after having carefully read the safety information applicable to this product. The safety information is pr ovided 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 Produktsicherheit Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder andere Gefahrenquellen ausgehen. Installation, Betrieb, Wartung und sonstige Handhabung des Pr oduktes darf nur durch geschultes und qualifiziertes Personal unter Be achtung der anwendbaren Sicherheitsanforderungen erfolgen. Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal, Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.

2

Id:0900d80580942544

DN03317891 Issue 10-1


Table of Contents This document has 136 pages.

DN03317891 Issue 10-1

1 1.1 1. 1

Abo bou ut this do doc cument . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 NettAc Ne Actt co comp mpat atib ibiili litty and and ca capa paci city ty in inffor orma mati tion on . . . . . . . . . . . . . . . . . . . . . 8

1.2 1. 2

Term rms. s. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

2 2.1 2. 1

Introduction to 3GPP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 Ove verv rviiew . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 3.1 3. 1 3.1 3. 1.1

3GPP CORBA Bulk CM Northbound Inter erfface . . . . . . . . . . . . . . . . . . . 12 IDL fifiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3GPP 3G PP ID IDL L fil files es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

3.1.2 3.1. 2 3.2 3. 2 3.3 3. 3

Objec Obje ct Man Manag agem emen entt Gr Grou oup p IDL IDL fi file les s . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Sup upp port rte ed ne nettwor ork k re resourc rce e model els s . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 Used XML schem ema as. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

3.4 3.4 3.4 3. 4.1 3.4. 3. 4.2 2

Fun unct ctiion onal aliity ove verv rvie iew w . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Sys yste tem m rol roles es . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 IRPIR P-re rela late ted d fun funct ctio iona nali lity. ty. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

3.5 3.5 3.6 3. 6 3.6. 3. 6.1 1

Gett ttin ing g sta start rte ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Sup upp porte ted d op ope era rattio ion ns . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 sta tart rtSe Ses ssi sion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

3.6.2 3.6. 2 3.6. 3. 6.3 3 3.6 3. 6.4

endSes endS essi sion on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 uplo up load ad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 dow do wnl nloa oad d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

3.6.5 3.6. 5 3.6 3. 6.6 3.6. 3. 6.7 7

preact prea ctiv ivat ate e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 acttiv ac ivat ate e . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 fall fa llba back. ck. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3.6.8 3.6. 8 3.6. 3. 6.9 9 3.6. 3. 6.10 10

abortS abor tSes essi sion onOp Oper erat atio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 getS ge tSes essi sion onId Ids s . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 getS ge tSes essi sion onSt Stat atus. us. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

3.6.11 3.6. 11 3.6. 3. 6.12 12 3.7 3. 7

getSes getS essi sion onLo Log g . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 getB ge tBul ulkC kCmI mIRP RPVe Vers rsio ion n . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 Sup upp porte ted d no nottif ifiicati tio ons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

3.7.1 3.7 3.7. 3. 7.2 2 3.7. 3. 7.3 3

Pus ush h an and Pul Pulll sty style le . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 noti no tify fySe Sess ssio ionS nSta tate teCh Chan ange ged d . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 noti no tify fyGe GetS tSes essi sion onLo LogE gEnd nded ed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

4 4.1 4. 1 4.2 4. 2

NetAct Object Model RAN data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Nami min ng co conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Ass ssoc ocia iati tion ons s be betw twee een n ob obje ject ct mod odel els. s. . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4.2.1 4.2. 1 4.2. 4. 2.2 2 4.2. 4. 2.3 3

Associ Asso ciat atio ions ns fo forr ma mana nage geme ment nt no node de.. . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 Asso As soci ciat atio ions ns fo forr Ne NetA tAct ct an and d ext exter erna nall ma mana nage ged d obj objec ects ts.. . . . . . . . . . . . . 30 Ass sso oci ciat atiion ons s for for Net etAc Actt WCD WCDMA MA ma mana nage ged d ob objjec ects ts . . . . . . . . . . . . . . . 32

4.2.4 4.2. 4 4.2. 4. 2.5 5 4.2. 4. 2.6 6

Associ Asso ciat atio ions ns fo forr Ne NetA tAct ct WB WBTS TS ma mana nage ged d obj objec ects ts . . . . . . . . . . . . . . . . . 35 Asso As soci ciat atio ions ns fo forr WC WCEL EL ma mana nage ged d ob obje ject cts s . . . . . . . . . . . . . . . . . . . . . . . 36 Asso As soci ciat atio ions ns fo forr AN ANTE TE ma mana nage ged d obj objec ects ts.. . . . . . . . . . . . . . . . . . . . . . . . 37

4.2. 4. 2.7 7

Asso As soci ciat atio ions ns fo forr OM OMS S man manag aged ed ob obje jec cts . . . . . . . . . . . . . . . . . . . . . . . . 38

Id:0900d80580942544

3


4

4.2.8

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

4.2.8.1 4.2.8.2 4.2.8.3

Associations for MRBTS managed objects. . . . . . . . . . . . . . . . . . . . . . . 38 Associations for LNBTS managed objects . . . . . . . . . . . . . . . . . . . . . . . 39 Associations for FTM managed objects . . . . . . . . . . . . . . . . . . . . . . . . . 40

4.2.8.4 4.2.8.5 4.2.9

Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 41 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 42 Associations for NetAct MRBTS (LTE eNB) managed objects in RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

4.2.9.1 4.2.9.2 4.2.9.3


4.2.9.4 4.2.9.5 4.2.10

Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 46 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 47 Associations for NetAct MRBTS (LTE eNB) managed objects in RL40 . 48

4.2.10.1 4.2.10.2 4.2.10.3


4.2.10.4 4.2.10.5 4.3

Associations for IPNO managed objects . . . . . . . . . . . . . . . . . . . . . . . . 52 Associations for LNCEL managed objects . . . . . . . . . . . . . . . . . . . . . . . 52 Data amounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

5 5.1 5.1.1

OSS5.x - 3GPP R6 object model mapping for WCDMA . . . . . . . . . . . . . 56 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 Considerations in CM data upload (NetAct model → 3GPP model). . . . 60

5.1.2 5.2 5.3

Considerations in CM data download (3GPP model → NetAct model) . 60 Vendor-specific objects and parameters. . . . . . . . . . . . . . . . . . . . . . . . . 62 Interface-N XML file example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6 6.1 6.1.1

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

6.1.2

Considerations in CM data download (3GPP model

7 7.1

OSS5.x - 3GPP R8 object model mapping for LTE RL25/RL30 . . . . . . . 78 Instance mappings for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

7.1.1 7.1.2

Considerations in CM data upload (NetAct model → 3GPP model). . . . 84 Considerations in CM data download (3GPP model → NetAct model) . 85

8

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

8.1 8.2 8.3

Instance mappings for RL40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86 Considerations in CM data upload (NetAct model → 3GPP model). . . . 93 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

Id:0900d80580942544

→ NetAct

model) . 77

DN03317891 Issue 10-1


14

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

DN03317891 Issue 10-1

Id:0900d80580942544

5


List of Figures

6

Figure 1

Overview of the global Network Manager. . . . . . . . . . . . . . . . . . . . . . . . 11

Figure 2 Figure 3 Figure 4

OMC management node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30 RNC external managed objects association . . . . . . . . . . . . . . . . . . . . . . 31 GSM external managed objects association. . . . . . . . . . . . . . . . . . . . . . 31


Utran external managed objects association . . . . . . . . . . . . . . . . . . . . . 32 LTE external managed objects association . . . . . . . . . . . . . . . . . . . . . . 32 WCDMA associations (1/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33


WCDMA associations (2/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 WCDMA associations (3/3). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 WBTS associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36


WCEL associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 ANTE associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 OMS associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38


MRBTS associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 LNBTS associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40 FTM associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41


IPNO associations for RL15/RL20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42 LNCEL associations for RL15/20 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43 MRBTS associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . 44


LNBTS for RL25/RL30 associations . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45 FTM associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46 IPNO associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47


LNCEL associations for RL25/RL30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48 MRBTS associations for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49 LNBTS for RL40 associations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50


FTM associations for RL40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51 IPNO associations for RL40 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52 LNCEL associations for RL40. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53


Data amount example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54 NOM vendor-specific objects and vendor-specific data . . . . . . . . . . . . . 62 Containment for Frequency Measurement Control Objects . . . . . . . . . . 63


Containment for Handover path objects . . . . . . . . . . . . . . . . . . . . . . . . . 63 Containment for Location Services -related objects . . . . . . . . . . . . . . . . 64 Containment for IMSI based HO -related objects . . . . . . . . . . . . . . . . . . 64

Id:0900d80580942544

DN03317891 Issue 10-1


List of Tables

DN03317891 Issue 10-1

Table 1

Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Table 2 Table 3 Table 4

Used XML Schamas and the modifications . . . . . . . . . . . . . . . . . . . . . 13 The Bulk Configuration Management IRP-related functionality . . . . . . 14 subscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


unsubscribe . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 startSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 endSession . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17


upload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 activate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22


fallback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 abortSessionOperation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 getSessionIds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


getSessionStatus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 getSessionLog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 getBulkCmIRPVersion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26


notifySessionStateChanged . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 notifyGetSessionLogEnded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28 Data amount example for LTE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54


Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56 NetAct UTRAN vendor specific object/data mappings . . . . . . . . . . . . . 65 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Table 23 Table 24

Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78 Examples of instance mappings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Id:0900d80580942544

7

About this document


1 About this document 3GPP 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 3G PP CORBA Bulk CM Northbound Interface.

1.1

NetAct compatibility and capacity information For 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

Terms For 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 speci fications.

DN

Distinguished name, a name of a managed object which consists of a sequence of the relative distinguished names of its superiors in t he 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 3GP P object is the main object and the child object is the related object. For example, Managed Element: RNC is a main object and it s 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

8

Terms

Id:0900d80580942542

DN03317891 Issue 10-1


Term

Explanation

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 interfaces 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.

Table 1

DN03317891 Issue 10-1

About this document

Terms (Cont.)

Id:0900d80580942542

9

Introduction to 3GPP


2 Introduction to 3GPP The 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 interface for integration of the Configurator regional cluster into a 3GPP-compliant networkwide configuration management system. The interface is provided for all networks (however, 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 parameters. 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

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

10

Id:0900d80580942542

DN03317891 Issue 10-1


Introduction to 3GPP

Global Network Manager Interface-N

3GPP CORBA Bulk CM Northbound Interface Regional Configurator

Vendor X

Vendor Y

Network interface

RNC

Figure 1

DN03317891 Issue 10-1

eNodeB

RNC

RNC

eNodeB

RNC

RNC

eNodeB

RNC

Overview of the global Network Manager

Id:0900d80580942542

11

3GPP CORBA Bulk CM Northbound Interface


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

3.1

IDL files This section lists all IDL files that are required for 3GPP B ulk Configuration Management Northbound interfaces.

3.1.1

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

3.1.2

•

Appendix BulkCmIRPConstDefs.idl

•

Appendix BulkCMIRPSystem.idl

•

Appendix BulkCMIRPNotifications.idl

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

3.2

•

TimeBase.idl

•

CosNotifyFilter.idl

•

CosNotifyComm.idl

•

CosNotifyChannelAdmin.idl

•

CosNotification.idl

•

CosEventComm.idl

•

CosEventChannelAdmin.idl

Supported network resource models The 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.

12

Id:0900d80580942542

DN03317891 Issue 10-1


3.3


Used XML schemas XML 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. 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.675620

replace operationalStateType "disbled" with "disabled".

epcNrm.xsd

Commented out the line xn:linkListType

Rel 32.755-820

eutranNrm.xsd Rel 32.765-820

Table 2

•

replace PLMNId "mNc" with "mnc"

•

add schemaLocation="stateManagementIR P.xsd" during importing stateManagementIRP namespace

Used XML Schamas and the modifications

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 directory/etc/opt/nokia/oss/rac/conf/metadata//3gpp/ .

g

For LTE E-UTRAN, the subsystem_name is cmdlte.

3.4

Functionality overview This 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 roles The system roles in the Interface-N CORBA communication are:

DN03317891 Issue 10-1

•

The Regional Configurator system acts as a 3GPP CORBA IRPAgent.

•

The global NM system acts as a 3GPP CORBA IRPManager.

Id:0900d80580942542

13


3.4.2


IRP-related functionality This section describes the IRP-related functionality of the 3GPP CORBA Bulk CM Northbound Interface. The Bulk Configuration Management IRP-related functionality

Information Service operation / notification 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 getOperationProfile3

Table 3

get_bulk_CM_IRP_notification_profile get_bulk_CM_IRP_operation_profile

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 started A 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 interface. Entry Point IRP

To 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.

14

Id:0900d80580942542

DN03317891 Issue 10-1



This can be achieved by opening a Telnet session to t he 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 IRP

After 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 IRP

CM Bulk Data IRP uses Notification IRP to notify the IRPManage r about events such as session state changes. Notification IRP is retrieved through E PIRP 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 operation 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::NotificationCate gorySet

filter

input parameter filter, type string

subscriptionId

NotificationIRPConstDefs::SubscriptionId

Table 4

DN03317891 Issue 10-1

subscribe

Id:0900d80580942542

15



Information Service operation parameter Solution Set method parameter exceptions: Attach ParameterNotSupported InvalidParameter AlreadySubscribed AtLeastOneNotificationCategoryNotSupported

Table 4

subscribe (Cont.)

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, w hich needs to be used when notifications are unsubscribed. This is done by calling method detach_push() on the Notification IRP interface. Information Service operation parameter Solution Set method parameter

managerReference

input parameter manager_reference, type string

subscriptionId

input parameter subscription_id, type NotificationIRPConstDefs::SubscriptionId exceptions: Detach InvalidParameter

Table 5

3.6

unsubscribe

Supported operations The 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/ .

16

Id:0900d80580942542

DN03317891 Issue 10-1



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

3.6.1

g

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

Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionId session_id

sessionId

exceptions: StartSessionException SessionIdInUseException MaxSessionReachedException InvalidParameter

Table 6

3.6.2

startSession

endSession Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionId session_id

sessionId

exceptions: EndSessionException UnknownSessionIdException NotValidInCurrentStateException InvalidParameter

Table 7

endSession

endSession operation description

Once 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 Information Service operation parameter

Solution Set method parameter

sessionId

BulkCmIRPConstDefs::SessionId session_id

uploadDataFileReference

BulkCmIRPConstDefs::FileDestination sink

baseObjectInstance

BulkCmIRPConstDefs::DistinguishedName base_object

Table 8

DN03317891 Issue 10-1

upload

Id:0900d80580942542

17



Information Service operation parameter


scope, filter

BulkCmIRPConstDefs::SearchControl search_control exceptions: UploadException UnknownSessionIdException MaxSessionReachedException NotValidInCurrentStateException ConcurrencyException IllegalDNFormatException IllegalFilterFormatException IllegalScopeTypeException IllegalScopeLevelException IllegalURLFormatException InvalidParameter

Table 8

upload (Cont.)

Upload operation description

The 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 XM L file to a local working directory.

4.

The generated XML file is transferred via FTP/SFTP to the location specified by th e 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 document.

5.

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

Upload operation scope determination

Starting 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 specified in the filter are included in the upload. If you do not need a filter, you should give an empty filter string. Examples: •

18

Uploading the whole Subnetwork:

Id:0900d80580942542

DN03317891 Issue 10-1



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

g

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

g

Uploading only UtranCells, ExternalUtranCells and ExternalGsmCells: baseObjectInstance="SubNetwork=Nokia-1" filter="UtranCell, ExternalUtranCell, ExternalGsmCell" When you want to upload multiple class filter once, separate the class filters by comma.

Error situations in the upload operation •

•

g

3.6.4

The following errors cause the upload to fail: •

An unrecoverable error happened when reading from th e 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 adjacentCell is left empty (for UtranRelation and GsmRelation).

•

If there is no COCO object connected to a WB TS, 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.

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

download Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionId session_id

sessionId

downloadDataFileRefe BulkCmIRPConstDefs::FileDestination sink rence

Table 9

DN03317891 Issue 10-1

download

Id:0900d80580942542

19



Information Service operation parameter Solution Set method parameter exceptions: DownloadException UnknownSessionIdException MaxSessionReachedException NotValidInCurrentStateException IllegalURLFormatException InvalidParameter

Table 9

download (Cont.)

Download operation description

To 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 ag ainst 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 document.

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 activation, 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 _ . 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.

20

Id:0900d80580942542

DN03317891 Issue 10-1



Error situations in the download operation

All 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: •

•

•

•

•

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 normally: • •

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.

•

DN03317891 Issue 10-1

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 .

There is more than one operation to the same 3GPP object in the download file.

Id:0900d80580942542

21


3.6.5


preactivate Information Service operation parameter


sessionId


verificationMode

BulkCmIRPConstDefs::VerificationModeTypeOpt verification_mode

activationMode

BulkCmIRPConstDefs::ActivationModeTypeOpt activation_mode

fallbackEnabled

boolean fallback exceptions: PreactivateException UnknownSessionIdException NotValidInCurrentStateException ConcurrencyException IllegalActivationModeException IllegalVerificationModeException ParameterNotSupported InvalidParameter OperationNotSupported

Preactivate operation description

The 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 preactivation operation was not performed before activation. All network elements included in the plan are preactivated in parallel.

4.

3.6.6

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.

activate Information Service operation parameter Solution Set method parameter

sessionId


fallbackEnabled

boolean fallback

Table 10

22

activate

Id:0900d80580942542

DN03317891 Issue 10-1



Information Service operation parameter Solution Set method parameter exceptions: ActivateException UnknownSessionIdException NotValidInCurrentStateException ConcurrencyException IllegalActivationModeException ParameterNotSupported InvalidParameter

Table 10

activate (Cont.)

Activate operation description

The 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.

3.6.7

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.

fallback Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionId session_id

sessionId

Table 11

DN03317891 Issue 10-1

fallback

Id:0900d80580942542

23



Information Service operation parameter Solution Set method parameter exceptions: FallbackException UnknownSessionIdException NoFallbackException NotValidInCurrentStateException ConcurrencyException InvalidParameter

Table 11

fallback (Cont.)

Fallback operation description

As 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 i mplies that the fallback operation only applies to the latest activation operation p erformed 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

3.6.8

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) Parameter Mapping , DN03373371.

abortSessionOperation Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionId session_id

sessionId

exceptions: AbortSessionOperationException UnknownSessionIdException NotValidInCurrentStateException InvalidParameter

Table 12

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.

24

Id:0900d80580942542

DN03317891 Issue 10-1


3.6.9


getSessionIds Information Service operation parameter Solution Set method parameter BulkCmIRPConstDefs::SessionIdList

sessionIdList

No error condition identified.

Table 13

3.6.10

getSessionIds

getSessionStatus Information Service operation parameter Solution Set method parameter

sessionId


sessionState

BulkCmIRPConstDefs::SessionState

status

BulkCmIRPConstDefs::ErrorInformation error_information Exceptions: GetSessionStatusException UnknownSessionIdException InvalidParameter

Table 14

3.6.11

getSessionStatus

getSessionLog Information Service operation parameter Solution Set method parameter

sessionId


logFileReference

BulkCmIRPConstDefs::FileDestination sink

contentType

boolean only_error_info1 exceptions: GetSessionLogException UnknownSessionIdException IllegalURLFormatException InvalidParameter

Table 15 1 Not

DN03317891 Issue 10-1

getSessionLog

supported by NetAct.

Id:0900d80580942542

25


3.6.12


getBulkCmIRPVersion Information Service operation parameter Solution Set method parameter

versionNumberList

ManagedGenericIRPConstDefs::VersionNumberSet No error condition identified.

Table 16

3.7 3.7.1

getBulkCmIRPVersion

Supported notifications Push and Pull style Object Management Group (OMG) Notification Service defines two styles of interaction: •

push style

•

pull style

NetAct only supports the push style.

3.7.2

notifySessionStateChanged OMG CORBA Structured Event Attribute

Supported by NetAct

There is no corresponding Information 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_SESSION_STATE_CHANGED. In the Information Service, this is defined as a Header attribute.

Solution Set Attribute

Table 17

26

Comment

notifySessionStateChanged

Id:0900d80580942542

DN03317891 Issue 10-1




OMG CORBA Structured Event Attribute

Supported by NetAct

Comment

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 indicating ERROR_INFORMATIONmay be present There is no corresponding Information Service attribute.

Variable Header

managedObjectClas s, managedObjectInst ance

One name-value pair of filterable_bod y_fields

No

The order of the name-value pairs is not significant. The name and the value of a name-value pair are of t he 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


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

Table 17

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.

notifySessionStateChanged (Cont.)

DN03317891 Issue 10-1

Id:0900d80580942542

27



systemDN

sessionId

sourceIndicator


Supported by NetAct


No


Yes


No


Comment 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 Information Service, this is defined as a Header attribute. 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. The name of the name-value pair is the SOURCE_INDICATOR of interface AttributeNameValue of module BulkCMIRPConstDefs. The name and the value of a name-value pair are of the type string.



The name of the name-value pair is the ERROR_INFORMATION of interface AttributeNameValue of module BulkCMIRPConstDefs. The name and the value of a name-value pair are of the type string.

Table 17

notifySessionStateChanged (Cont.)

3.7.3

notifyGetSessionLogEnded


Supported by NetAct


domain_name

Yes

Carries the IRP document version number stri ng. Indicates the syntax and semantics of the S tructured Event as defined by this document.

notificationTy pe

type_name

Yes

Carries the string NOTIFY_GET_SESSION_LOG_ENDED.

sessionLogStat us

event_name

Yes

Carries either the string GET_SESSION_LOG_COMPLETED_SUCCESSFULLY or GET_SESSION_LOG_COMPLETED_UNSUCCESSFULLY.


Comment

In the case of the latter, the name-value pair indicating ERROR_INFORMATION may be present. There is no corresponding Information Service attribute

Table 18

28

Variable Header

notifyGetSessionLogEnded

Id:0900d80580942542

DN03317891 Issue 10-1




managedObjectC lass , managedObjectI nstance


Supported by NetAct No


Comment 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 ar e attributes of Header defined in the Information Service.

notificationId

eventTime

systemDN

sessionId

sourceIndicato r

There is no corresponding Information Service attribute

Table 18


No


Yes


No


Yes


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. 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. 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 Information Service, this is defined as a Header attribute. The name of the name-value pair is the SESSION_ID of interface AttributeNameValue of module BulkCMIRPConstDefs. The value of the name-value pair is a string.


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

notifyGetSessionLogEnded (Cont.)

DN03317891 Issue 10-1

Id:0900d80580942542

29

NetAct Object Model RAN data


4 NetAct Object Model RAN data This section describes some basic information on Object Model data. For information on the allowed object identifiers, see Managed Object Reference.

4.1

Naming conventions The 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 3 GPP 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 bet ween R6OM/ R8OM and NOM is performed in the Interface-N adaptation.

4.2

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

4.2.1

Associations for management node The figure below describes the associations for management node.

NetAct

3GPP 1:1

PLMN

n

OMC

1:1

SubNetwork

ManagementNode

= contains 1:1 = one NOM object instance corresponds to one 3GPP object instance 0...n, n = the number of possible child objects Figure 2

4.2.2

OMC management node

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

30

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

3GPP

PLMN

SubNetwork

0...n

Figure 3

EXRNCF

1:1

ExternalRncFunction

RNC external managed objects association

NetAct

3GPP

PLMN

SubNetwork

BSC-0

BCF-0

0...n

BTS (FBTS)

1:1

1:1

Figure 4

DN03317891 Issue 10-1

ExternalGsmCell

VsDataContainer vsDataType:EGCE

GSM external managed objects association

Id:0900d80580942542

31



NetAct

3GPP

1:1

PLMN

SubNetwork

EXCC

0...n

1:1

EWCE

1:1

Figure 5

External UtranCell

VsDataContainer vsDataType:EWCE

Utran external managed objects association

NetAct

1:1

3GPP

PLMN

SubNetwork

0...n

ExternalENBFunction

EXCENBF 1:1 EXENBF EXEUCE

Figure 6

4.2.3

ExternalEUtranCellFDD ExternalEUtranCellTDD

LTE external managed objects association

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

32

Id:0900d80580942542

DN03317891 Issue 10-1


NetAct


3GPP SubNetwork

PLMN

ManagedElement ManagedElement Type: RNC 1

RncFunction 0...n

1:1

VsDataContainer vsDataType: RNC

RNC FMCS FMCI

FMCG 0...100

HOPS HOPI

HOPG 0...300

0...1

WSMLC

0...4352

1:1

VsDataContainer vsDataType: FMCI

1:1

VsDataContainer vsDataType: FMCG

1:1

VsDataContainer vsDataType: HOPS

1:1

VsDataContainer vsDataType: HOPI

1:1

VsDataContainer vsDataType: HOPG

1:1

VsDataContainer vsDataType: IUR

1:1

VsDataContainer vsDataType: WSMLC

1:1

VsDataContainer vsDataType:WLCSE VsDataContainer vsDataType: WANE

WANE

0...128

DN03317891 Issue 10-1

WLCSE

VsDataContainer vsDataType: FMCS

1:1

0...10

Figure 7

IUR

1:1

1

WSG

1:1

VsDataContainer vsDataType: WGS

WCDMA associations (1/3)

Id:0900d80580942542

33



NetAct 0...1 0...1 0...1 0...1 0...1 0...13 0...4 0...8 0...5 0...255

1:1 RNFC 1:1 RNAC 1:1 RNRLC 1:1 RNHSPA 1:1 RNMOBI 1:1 CMOB 1:1 TQM 1:1 IPQM 1:1 WRAB 1:1 IUCS 0...5

0...255

34

IUCSIP

1:1

1:1 IUPS 0...5

Figure 8

3GPP

IUPSIP

1:1

VsDataContainer vsDataType: RNFC VsDataContainer vsDataType: RNAC VsDataContainer vsDataType: RNRLC VsDataContainer vsDataType: RNHSPA VsDataContainer vsDataType: RNMOBI VsDataContainer vsDataType: CMOB VsDataContainer vsDataType: TQM VsDataContainer vsDataType: IPQM VsDataContainer vsDataType: WRAB VsDataContainer vsDataType: IUCS VsDataContainer vsDataType: IUCSIP VsDataContainer vsDataType: IUPS VsDataContainer vsDataType: IUPSIP


Id:0900d80580942542

DN03317891 Issue 10-1



NetAct 0...50 0...n 0...4 0...1 0...1 0...4 0...n 0...255

1:1 PFL 1:1 HOPL 1:1 CBCI 1:1 RNPS 1:1 RNTRM 1:1 IUO 1:1 ADJL 1:1 VBTS 0...5

Figure 9

4.2.4

3GPP

VCEL

1:1

VsDataContainer vsDataType: PFL VsDataContainer vsDataType: HOPL VsDataContainer vsDataType: CBCI VsDataContainer vsDataType: RNPS VsDataContainer vsDataType: RNTRM VsDataContainer vsDataType: IUO VsDataContainer vsDataType: ADJL VsDataContainer vsDataType: VBTS VsDataContainer vsDataType: VCEL


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

DN03317891 Issue 10-1

Id:0900d80580942542

35



NetAct

3GPP

0...n

SubNetwork

RNC

ManagedElement managedElement Type: RNC 1

RncFunction

0...400

COCO

1:1

IubLink 1

VsDataContainer vsDataType: COCO 1...65535

IPNB

1:1

IubLink 1

VsDataContainer vsDataType: IPNB

1

ManagedElement managedElement Type: NodeB 1

0...384

WBTS

1:1

NodeBFunction 1

VsDataContainer vsDataType: WBTS

Figure 10

g 4.2.5

WBTS associations

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

Associations for WCEL managed objects The figure below describes the associations for WCEL managed objects.

36

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

3GPP

0...384 WBTS

RncFunction

0...3

1:1

WCEL

UtranCell 1

VsDataContainer vsDataType: WCEL UtranRelation 0...31

ADJS

1:1

1

VsDataContainer vsDataType: ADJS UtranRelation 0...48

ADJI

1:1

1

VsDataContainer vsDataType: ADJI UtranRelation 0...31

ADJD

1:1

1

VsDataContainer vsDataType: ADJD GsmRelation 0...32

ADJG

1:1

1

VsDataContainer vsDataType: ADJG 0...n

Figure 11

4.2.6

ADJL

1:1

VsDataContainer vsDataType: ADJL

WCEL associations

Associations for ANTE managed objects The figure below describes the associations for ANTE managed objects.

DN03317891 Issue 10-1

Id:0900d80580942542

37



NetAct

3GPP

SubNetwork

PLMN

ManagedElement managedElement Type: ANTE

1 ANTC

1 Antenna

0...n 1:1

VsDataContainer vsDataType: ANTE

1:1

VsDataContainer vsDataType: WCAL

1:1

VsDataContainer vsDataType: GCAL

1:1

VsDataContainer vsDataType: EUCAL

ANTE 0...n 0...n

0...n

WCAL GCAL EUCAL

Figure 12 ANTE associations

4.2.7

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

PLMN

3GPP

SubNetwork ManagedNode

OMS 1:1

VsDataContainer VsDataType: OMS

1:1

VsDataContainer VsDataType: PREBTS

0...n PREBTS

Figure 13

4.2.8

4.2.8.1

OMS associations

Associations for NetAct MRBTS (LTE eNB) managed objects in RL15/RL20 Associations for MRBTS managed objects The figure below describes the associations for MRBTS managed objects.

38

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

SubNetwork

0...n MRBTS

ManagedElement ManagedElementType:MRBTS VsDataContainer VsDataType: MRBTS

1...18 1...1 0...12 1...1

0...255 0...255 1...3 1...2

Figure 14

4.2.8.2

ANTL BTSSCL LCELL LNBTS*

MHA RET RMOD SMOD

1:1

VsDataContainer VsDataType: ANTL

1:1

VsDataContainer VsDataType: BTSSCL

1:1

VsDataContainer VsDataType: LCELL

1:1

ENBFunction

1:1

VsDataContainer VsDataType: LNBTS

1:1

VsDataContainer VsDataType: MHA

1:1

VsDataContainer VsDataType: RET

1:1

VsDataContainer VsDataType: RMOD

1:1

VsDataContainer VsDataType: SMOD

MRBTS associations for RL15/RL20

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

DN03317891 Issue 10-1

Id:0900d80580942542

39



NetAct

PLMN

3GPP

0...n MRBTS*

SubNetwork ManagedElement ManagedElementType:MRBTS VsDataContainer VsDataType: MRBTS

1...1

ENBFunction

LNBTS

VsDataContainer VsDataType: LNBTS 1...1 0...1 0...6 1...1 0...1 1...6

ADIPNO CTRLTS MTRACE FTM* GTPU LNCEL*

1:1

VsDataContainer VsDataType: ADIPNO

1:1

VsDataContainer VsDataType: CTRLTS

1:1

VsDataContainer VsDataType: MTRACE

1:1

VsDataContainer VsDataType: FTM

1:1

VsDataContainer VsDataType: GTPU

1:1

EUtranCellFDD/ EUtranCellTDD

1:1 0...64 0...6

LNADJ LNADJL

1:1

VsDataContainer VsDataType: LNCEL VsDataContainer VsDataType: LNADJ

1:1

EUtranRelation VsDataContainer VsDataType: LNADJL

0...32 0...32 0...16 0...1

Figure 15

g 4.2.8.3

ITRACE LNMME LNADLP SCTP

1:1

VsDataContainer VsDataType: ITRACE

1:1

VsDataContainer VsDataType: LNMME

1:1

VsDataContainer VsDataType: LNADLP

1:1

VsDataContainer VsDataType: SCTP

LNBTS associations for RL15/RL20

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.

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

40

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

1...1 MRBTS*


1...1 LNBTS*

ENBFunction VsDataContainer VsDataType: LNBTS

1...1

1:1

FTM

1...1 1...1 1...4 1...1 1...1 1...1 1...10

AMGR CERTH ETHLK IPNO* IPSECC L2SWI OAMMD 0...15 OAMMA 0...1

0...5 1...1 1...4 1...1 1...1 1...1

Figure 16

g 4.2.8.4

OAMMEP

OAMPRF PMTNL PPTT SYNC STPG UNIT

1:1 1:1

VsDataContainer VsDataType: FTM VsDataContainer VsDataType: AMGR VsDataContainer VsDataType: CERTH

1:1

VsDataContainer VsDataType: ETHLK

1:1

VsDataContainer VsDataType: IPNO

1:1

VsDataContainer VsDataType: IPSECC VsDataContainer VsDataType: L2SWI

1:1 1:1

VsDataContainer VsDataType: OAMMD

1:1

VsDataContainer VsDataType: OAMMA

1:1

VsDataContainer VsDataType: OAMMEP

1:1

VsDataContainer VsDataType: OAMPRF VsDataContainer VsDataType: PMTNL VsDataContainer VsDataType: PPTT VsDataContainer VsDataType: SYNC VsDataContainer VsDataType: STPG

1:1 1:1 1:1 1:1 1:1

VsDataContainer VsDataType:UNIT

FTM associations for RL15/RL20

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.

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

DN03317891 Issue 10-1

Id:0900d80580942542

41



NetAct

PLMN

3GPP

SubNetwork

0...n MRBTS*

ManagedElement ManagedElementType:MRBTS 1:1

VsDataContainer VsDataType: MRBTS

1...1 LNBTS*

ENBFunction 1:1

1...1 FTM*

1:1


1...1 IPNO

1:1


1:1

VsDataContainer VsDataType: IEIF

1:1

VsDataContainer VsDataType: IVIF

1:1

VsDataContainer VsDataType: IHCP

1:1

VsDataContainer VsDataType: INTP

1:1

VsDataContainer VsDataType: IPRM

1:1

VsDataContainer VsDataType: IPRT

1:1

VsDataContainer VsDataType: QOS

1:1

VsDataContainer VsDataType: TOPIK

1...1 0...5 1...1 1...1 1...1 1...1 1...1 1...1

Figure 17

4.2.8.5


IEIF IVIF IHCP INTP IPRM IPRT QOS TOPIK

IPNO associations for RL15/RL20

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

42

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

SubNetwork

0...n MRBTS*



1...1 LNBTS*

ENBFunction 1:1

VsDataContainer VsDataType: LNBTS EUtranCellFDD

1...6 LNCEL

1:1

VsDataContainer VsDataType: LNCEL

1:1

VsDataContainer VsDataType: LNCEL EUtranCellTDD

0...1 0...1 0...16 0...1 0...5 0...16 0...6 0...1

Figure 18

4.2.9

CDFIM GFIM GNFL IAFIM IRFIM LNHOIF REDRT UFFIM

1:1

VsDataContainer VsDataType: CDFIM

1:1

VsDataContainer VsDataType: GFIM

1:1

VsDataContainer VsDataType: GNFL

1:1

VsDataContainer VsDataType: IAFIM

1:1

VsDataContainer VsDataType: IRFIM

1:1

VsDataContainer VsDataType: LNHOIF

1:1

VsDataContainer VsDataType: REDRT

1:1

VsDataContainer VsDataType: UFFIM

LNCEL associations for RL15/20

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

g 4.2.9.1

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.

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

DN03317891 Issue 10-1

Id:0900d80580942542

43



NetAct

PLMN

3GPP

SubNetwork

0...n MRBTS


1...18 1...1 0...13 1...1

0...255 0...255


MHA RET 0...255 CREL 0...255 ECREL

1...3 1...3

Figure 19

4.2.9.2

RMOD SMOD

1:1


1:1


1:1


1:1

ENBFunction

1:1


1:1


1:1


1:1

VsDataContainer VsDataType: CREL

1:1

VsDataContainer VsDataType: ECREL

1:1


1:1


MRBTS associations for RL25/RL30


44

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

0...n MRBTS*


1...1

ENBFunction

LNBTS



1:1


1:1


1:1


1:1


1:1


1:1

EUtranCellFDD/ EUtranCellTDD

1:1 0...64 0...6

LNADJ LNADJL

1:1

VsDataContainer VsDataType: LNCEL VsDataContainer VsDataType: LNADJ

1:1


0...32 0...32 0...16 0...1 0...6 0...8 0...6 0...1 0...1

Figure 20

4.2.9.3

LNADJG LNADJW LNMME MODPR MODRED MOPR MORED PMRNL SCTP

1:1

VsDataContainer VsDataType: LNADJG

1:1

VsDataContainer VsDataType: LNADJW

1:1


1:1

VsDataContainer VsDataType: MODPR

1:1

VsDataContainer VsDataType: MODRED

1:1

VsDataContainer VsDataType: MOPR

1:1

VsDataContainer VsDataType: MORED

1:1

VsDataContainer VsDataType: PMRNL

1:1


LNBTS for RL25/RL30 associations


DN03317891 Issue 10-1

Id:0900d80580942542

45



NetAct

PLMN

3GPP

1...1 MRBTS*


1...1 LNBTS*

ENBFunction VsDataContainer VsDataType: LNBTS

1...1

1:1

FTM 1...1 1...1 1...4 1...1 1...1 1...1 1...10

AMGR CERTH ETHLK IPNO* IPSECC L2SWI OAMMD 0...15 OAMMA 0...1

0...5 1...1 1...4 1...1 1...1 1...1 1...1 1...1

Figure 21

g 4.2.9.4

OAMMEP

OAMPRF PMTNL PPTT SYNC STPG TAC LTAC UNIT

VsDataContainer VsDataType: FTM VsDataContainer VsDataType: AMGR VsDataContainer VsDataType: CERTH

1:1 1:1 1:1


1:1


1:1

VsDataContainer VsDataType: IPSECC VsDataContainer VsDataType: L2SWI

1:1 1:1


1:1


1:1

VsDataContainer VsDataType: OAMMEP

1:1

VsDataContainer VsDataType: OAMPRF VsDataContainer VsDataType: PMTNL VsDataContainer VsDataType: PPTT VsDataContainer VsDataType: SYNC VsDataContainer VsDataType: STPG VsDataContainer VsDataType: TAC VsDataContainer VsDataType: LTAC

1:1 1:1 1:1 1:1 1:1 1:1 1:1

VsDataContainer VsDataType:UNIT

FTM associations for RL25/RL30

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

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

46

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

SubNetwork

0...n MRBTS*



1...1 LNBTS*

ENBFunction 1:1

1...1 FTM*

1:1


1...1 IPNO

1:1


1:1

VsDataContainer VsDataType: BFD

1:1

VsDataContainer VsDataType: BFDGRP

1:1

VsDataContainer VsDataType: IDNS

1:1


1:1


1:1


1:1


1:1


1:1


1:1


1:1


1:1

VsDataContainer VsDataType: TWAMP

0...2 8...8 1...1 1...1 0...5 1...1 1...1 1...1 1...1 1...1 1...1 0...10

Figure 22

g


BFD BFDGRP IDNS IEIF IVIF IHCP INTP IPRM IPRT QOS TOPIK TWAMP

IPNO associations for RL25/RL30

BFD, BFDGRP and TWAMP are not supported in LNT2.0. TOPIK is not supported in LNT2.0 and LN4.0.

4.2.9.5


DN03317891 Issue 10-1

Id:0900d80580942542

47



NetAct

PLMN

3GPP

0...n MRBTS*

SubNetwork ManagedElement ManagedElementType:MRBTS

1:1


1...1 LNBTS*

ENBFunction 1:1


1...6 LNCEL

1:1


1:1


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

Figure 23

g 4.2.10

CDFIM GFIM GNFL IAFIM IRFIM LNHOG LNHOIF LNHOW LNREL LNRELG LNRELW REDRT UFFIM

1:1


1:1


1:1


1:1


1:1


1:1

VsDataContainer VsDataType: LNHOG

1:1


1:1

VsDataContainer VsDataType: LNHOW

1:1

VsDataContainer VsDataType: LNREL

1:1

VsDataContainer VsDataType: LNRELG

1:1

VsDataContainer VsDataType: LNRELW

1:1


1:1


LNCEL associations for RL25/RL30

CDFIM is not supported in TDD.

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

g

48

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.

Id:0900d80580942542

DN03317891 Issue 10-1


4.2.10.1


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

PLMN

3GPP

SubNetwork

0...n MRBTS


1...18 1...1 0...12 1...1

0...255 0...255


MHA RET 0...255 CREL 0...255 ECREL

1...3 1...2

Figure 24

4.2.10.2

RMOD SMOD

1:1


1:1


1:1


1:1

ENBFunction

1:1


1:1


1:1


1:1

VsDataContainer VsDataType: CREL

1:1

VsDataContainer VsDataType: ECREL

1:1


1:1


MRBTS associations for RL40


DN03317891 Issue 10-1

Id:0900d80580942542

49



NetAct

PLMN

3GPP

0...n MRBTS*


1...1

ENBFunction

LNBTS



1:1 1:1


1:1


1:1


1:1


1:1 1:1

0...64 0...6

LNADJ LNADJL


1:1

EUtranCellFDD/ EUtranCellTDD VsDataContainer VsDataType: LNCEL VsDataContainer VsDataType: LNADJ

1:1


0...32 0...32 0...16 0...1 0...6 0...8 0...6 0...1 0...1

Figure 25

4.2.10.3

LNADJG LNADJW LNMME MODPR MODRED MOPR MORED PMRNL SCTP

1:1

VsDataContainer VsDataType: LNADJG

1:1

VsDataContainer VsDataType: LNADJW

1:1


1:1

VsDataContainer VsDataType: MODPR

1:1

VsDataContainer VsDataType: MODRED

1:1

VsDataContainer VsDataType: MOPR

1:1

VsDataContainer VsDataType: MORED

1:1

VsDataContainer VsDataType: PMRNL

1:1


LNBTS for RL40 associations


50

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

1...1 MRBTS*


1...1

ENBFunction

LNBTS*

VsDataContainer VsDataType: LNBTS 1...1 FTM

1...1 1...1 1...4 1...1 1...1 1...1 1...10

0...5 1...1 1...4 1...1 1...1 1...1 1...1 1...1 1...1

AMGR CERTH

g

1:1

VsDataContainer VsDataType: AMGR VsDataContainer VsDataType: CERTH

1:1


1:1


1:1

VsDataContainer VsDataType: IPSECC

1:1

VsDataContainer VsDataType: L2SWI

1:1

0...15 OAMMA


1:1


0...1

1:1

VsDataContainer VsDataType: OAMMEP VsDataContainer VsDataType: OAMPRF

IPNO* IPSECC L2SWI OAMMD

OAMMEP

OAMPRF PMTNL PPTT SYNC STPG TAC LTAC TOPB TOPF TOPP

Figure 26


1:1

ETHLK

1...1 1...1

1:1

UNIT

1:1

VsDataContainer VsDataType: PMTNL VsDataContainer VsDataType: PPTT

1:1 1:1 1:1

VsDataContainer VsDataType: SYNC VsDataContainer VsDataType: STPG VsDataContainer VsDataType: TAC

1:1 1:1 1:1

VsDataContainer VsDataType: LTAC VsDataContainer VsDataType: TOPB

1:1 1:1 1:1

1:1

VsDataContainer VsDataType: TOPF VsDataContainer VsDataTYpe: TOPP VsDataContainer VsDataType:UNIT

FTM associations for RL40

OAMMD, OAMMA, OAMMEP, OAMPRF, PMTNL, TAC and LTAC are not supported in LNT2.0. TOPB, TOPF and TOPP are only supported in LN4.0.

DN03317891 Issue 10-1

Id:0900d80580942542

51


4.2.10.4


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

PLMN

3GPP

SubNetwork

0...n MRBTS*



1...1 LNBTS*

ENBFunction 1:1

1...1 FTM*

1:1


1...1 IPNO

1:1


1:1

VsDataContainer VsDataType: BFD

1:1

VsDataContainer VsDataType: BFDGRP

1:1

VsDataContainer VsDataType: IDNS

1:1


1:1


1:1


1:1


1:1


1:1


1:1


1:1


1:1

VsDataContainer VsDataType: TWAMP

0...2 8...8 1...1 1...1 0...5 1...1 1...1 1...1 1...1 1...1 1...1 0...10

Figure 27

g


BFD BFDGRP IDNS IEIF IVIF IHCP INTP IPRM IPRT QOS TOPIK TWAMP

IPNO associations for RL40

BFD, BFDGRP and TWAMP are not supported in LNT2.0. TOPIK is not supported in LNT2.0 and LN4.0.

4.2.10.5


52

Id:0900d80580942542

DN03317891 Issue 10-1



NetAct

PLMN

3GPP

0...n MRBTS*

SubNetwork ManagedElement ManagedElementType:MRBTS

1:1


1...1 LNBTS*

ENBFunction 1:1


1...6 LNCEL

1:1


1:1


0...1

CDFIM

0...1

GFIM

0...16

GNFL

0...1

IAFIM

0...5 0...6 0...16 0...16 0...16

IRFIM LNHOG LNHOIF LNHOT LNHOW

0...389 0...256 0...256 0...256 0...6

LNREL LNRELG LNRELT LNRELW REDRT

0...1

Figure 28

g

UFFIM

1:1


1:1


1:1


1:1


1:1


1:1

VsDataContainer VsDataType: LNHOG

1:1


1:1

VsDataContainer VsDataType: LNHOT

1:1

VsDataContainer VsDataType: LNHOW

1:1

VsDataContainer VsDataType: LNREL

1:1

VsDataContainer VsDataType: LNRELG

1:1

VsDataContainer VsDataType: LNRELT

1:1

VsDataContainer VsDataType: LNRELW

1:1


1:1


LNCEL associations for RL40

CDFIM is not supported in TDD. LNHOT and LNRELT are not supported in FDD.

4.3

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

DN03317891 Issue 10-1

Id:0900d80580942542

53


g


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

Number of objects / parent object

Objects total

Parameters / object

Parameters total

1

1

518

518

WBTS

384

384

49

18816

WCEL

3

1152

172

198144

ADJS

31

35712

17

607104

ADJI

48

55296

18

995328

ADJG

32

36864

15

552960

FMCS

100

100

23

2300

FMCI

100

100

24

2400

FMCG

100

100

24

2400

HOPS

100

100

18

1800

HOPI

100

100

17

1700

HOPG

100

100

10

1000

COCO

400

400

76

30400

WSMLC

1

1

5

5

WLCSE

4352

4352

34

147968

10

10

9

90

128

128

9

1152

Object RNC

WANE WSG Objects total:

134900

PARAMETERS TOTAL:

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

2564085 40 40 102563400

File size in megabytes Figure 29

2564085

103

Data amount example

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

parameters/object

MRBTS

1

7

LNBTS

1

119

LNCEL

3

263

Table 19

54

Number of object/ parent object

Data amount example for LTE

Id:0900d80580942542

DN03317891 Issue 10-1


Object

Number of object/ parent object

parameters/object

LNADJ

32

11

LNADJL

3

16

Table 19

DN03317891 Issue 10-1


Data amount example for LTE (Cont.)

Id:0900d80580942542

55

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


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

5.1

Examples of instance mappings This section describes examples of instance mappings. In the column titled "Mapping" of the f ollowing table, different fonts are used for the attributes of the 3GPP model and the attributes of the NetAct model .

Object class

Mapping

NetAct DN

3GPP DN

Notes

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

subNetworkId= "Nokia"+ clusterId (NmsId)

PLMNPLMN/OMC-1

SubNetwork=Nokia1

OMC

managementNodeId= omcRD N

PLMNPLMN/OMC-1

SubNetwork=Nokia1, ManagementNode=OMC-1

RNC

managedElementId=rncFun PLMNctionId=rncRDN PLMN/RNC-3

WBTS managedElementId=nodeBF PLMNunctionId=rncRDN + "I " + PLMN/RNCwbtsRDN 3/WBTS-4

WCEL utranCellId=wbtsRDN + "I " + wcelRDN

PLMNPLMN/RNC3/WBTS4/WCEL-5

SubNetwork=Nokia- Attribute rncId shall 1, ManagedElebe set to rncRDN . ment=RNC-3 SubNetwork=Nokia1, ManagedElement=RNC3/WBTS-4, NodeBFunction=RNC3/WBTS-4

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

SubNetwork=Nokia1, ManagedElement=RNC-3, RncFunction=RNC-3, UtranCell=WBTS4/WCEL-5

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

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

wcelRDN =WCEL"LcrId " (LcrId =localCellI d)

Table 20

56

Examples of instance mappings

Id:0900d80580942542

DN03317891 Issue 10-1


Object class

Mapping

NetAct DN


3GPP DN

ADJS utranCellId=wbtsRDN + "I " PLMN+ wcelRDN , PLMN/RNCutranRelationId=adjsRDN 1/WBTS1/WCEL1/ADJS-1

SubNetwork=Nokia1, ManagedElement=RNC-1,

ADJI

SubNetwork=Nokia1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, UtranRelation=ADJI-1

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

PLMNPLMN/RNC1/WBTS1/WCEL-1/ADJI1

Notes

utranCellId must also carry the information of the parent RncFunction=RNC- WBTS as it is not 1, UtranCell=WBTS- under NodeBFunc1/WCEL-1, UtranRe- tion in the 3GPP model. lation=ADJS-1 Object class name prefixes used in UtranRelation and GsmRelation identifiers in R6OM to separate the relation type in NOM. utranCellId must also carry the information of the parent WBTS as it is not under NodeBFunction in the 3GPP model. Object class name prefixes used in UtranRelation and GsmRelation identifiers in R6OM to separate the relation type in NOM.

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

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJG-1

SubNetwork=Nokia1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, GsmRelation=ADJG-1

utranCellId must also carry the information of the parent WBTS as it is not under NodeBFunction in 3GPP model. Object class name prefixes used in UtranRelation and GsmRelation identifiers in R6OM to separate the relation type in NOM.

COCO IubLinkId=cocoRDN

Table 20

PLMNPLMN/RNC1/COCO-1

SubNetwork=Nokia1,

COCO is only existed in RNC.

ManagedElement=RNC-1, RncFunction=RNC-1, IubLink=COCO-1

Examples of instance mappings (Cont.)

DN03317891 Issue 10-1

Id:0900d80580942542

57


Object class IPNB

EXCC


Mapping

NetAct DN

3GPP DN

IubLinkId=IPNBRDN

PLMNPLMN/RNC1/IPNB-1

SubNetwork=Nokia1, ManagedElement=RNC-1, RncFunction=RNC-1, IubLink=IPNB-1

PLMNPLMN/EXCC-1

EWCE externalUtranCellId=ewc PLMNeRDN PLMN/EXCC1/EWCE-1234

Notes

No mapping, conceptual object only SubNetwork=Nokia1, ExternalUtranCell=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=egceR PLMNDN PLMN/BSC0/BCF-0/BTS123 321

SubNetwork=Nokia1, ExternalGsmCell=EGCE-123 321

It is not necessary to carry ExccId in the 3GPP DN. Note: currently FBTS (foreign BTS) is used but it will be replaced with EGCE in the future NetAct/Configurator 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= Ant PLMNeFunctionId=anteRDN PLMN/ANTC1/ANTE-1

Table 20

58

SubNetwork=Nokia1, ManagedElement=ANTC-1/ ANTE -1, Antenna=ANTE-1, vsDataContainer=ANTE-1

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


Id:0900d80580942542

DN03317891 Issue 10-1


Object class --

Mapping

NetAct DN

3GPP DN

Notes

irpAgentId= systemId of OMC

--

SubNetwork=Nokia1, ManagementNode=OMC-1, IRPAgent=Nokia-1

NetAct does not have a corresponding object.

ADJD utranCellId=wbtsRDN +"I +"I " PLMN+ wcelRDN , PLMN/RNCutranRelationId=adjdRDN 1/WBTS1/WCEL1/ADJD-1

Table 20


SubNetwork=Nokia1,ManagedElement=RNC-1,RncFunction=RNC1,UtranCell=WBTS1/WCEL-1,UtranRelation=ADJD-1

Examples of instance mappings (Cont.) 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.

•

MeContext in R6OM is not taken into account in the mapping. It is not Objects like MeContext in used in the NetAct model.

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

DN03317891 Issue 10-1

•

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

•

managedBy is set to the 3GPP DN of the controlThe ManagedElement attribute managedBy is ling OMC.

•

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

•

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

•

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

•

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

Id:0900d80580942542

59


5.1.1 5.1.1


•

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=RNC2,UtranCell=WBTS-3/WCEL-4 SubNetwork=Nokia-1,ExternalUtranCell=EWCE-2

•

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

Consid Consider erati ations ons in CM CM data data uploa upload d (NetA (NetAct ct model model

3GPP model)

During the upload of a NOM object: •

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

•

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

•

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

•

ANTE: divided to two different common R6OM objects: Managed element: ANTE ANTEId , is used in RDN for both and Antenna(Function). The same NOM, ANTEId, bo th 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: •

•

5.1.2 5.1.2

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

Consid Consider erati ations ons in CM CM data data downlo download ad (3GPP (3GPP model model

NetAct model)

During the download of R6OM objects: •

•

60

ManagementNode and ManagementNode and Subnetwork combined Subnetwork combined in one NOM object: obj ect: OMC, which holds all ManagementNode and Subnetwork attributes in the NOM. ANTE and antenna(Function) combined in one NOM object: Managed element: ANTE and ANTE. That is, all R6OM ManagedElement:ANTE and antenna(Function) attributes are mapped to be attributes of ANTE in NOM.

Id:0900d80580942542

DN03317891 Issue 10-1


g


•

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.

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: ) 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/WBTS- .

Special requirements for the NOM WCEL creation: •

The ID (in NOM: ) 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 associated IubLink. It also has to be of the following format: WBTS/WCEL- .

•

g

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

The object creation via the Interface-N has to be done in the NOM order: pare nt object first - then child objects. That is: WBTS - WCEL - adjacencies. Special requirements for the object rehosting: •

When a NOM WBTS is rehosted und er 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-/WBTS- .

•

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: •

DN03317891 Issue 10-1

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.

Id:0900d80580942542

61



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 parameters Vendor-specific data is specific for bulk configuration management. NOM vendor-specific objects and vendor-specific data of the common objects are presented in R6OM (in the Interface-N) by using VsDataContainers as shown in the figure below.

MOC

0...n

VsDataContainer (from the generic model)

= contains 0...n, 0...1 = the number of possible child objects 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:

62

•

FMCG

•

FMCI

•

FMCS

•

HOPG

•

HOPI

•

HOPS

•

WSMLC

•

WLCSE

•

WANE

•

WSG

•

WCAL

•

GCAL

•

EUCAL

Id:0900d80580942542

DN03317891 Issue 10-1



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 o bject 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.

RncFunction 1

0...100

1

1

0...100

0...100

FMCI

FMCS

FMCG

= contains 1, 0...x = the number of possible child objects 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.

RncFunction 1

0...100

1

0...100

HOPS

HOPI

1

0...100 HOPG

= contains

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

Containment for Handover path objects

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

DN03317891 Issue 10-1

Id:0900d80580942542

63



RncFunction 1

1

1

0...4352

WSMLC

WLCSE


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.

RncFunction 1

1

0...10

0...128

WANE

WSG


Containment for IMSI based HO -related objects

The following common NOM objects, which have a corresponding obj ect 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 extension in R6OM in order to support mandatory adjacency parameters (the extension is not specified in the 3GPP specifications):

64

•

BTS (FBTS)

•

EWCE

Id:0900d80580942542

DN03317891 Issue 10-1



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 combin ation 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) corresponds to vsDataContainerId="WCEL-12345 " (in R6OM / in the Interface-N).

NetAct UTRAN v endor-specific object/data mappings

Object class

Mapping

NetAct DN

3GPP DN

Notes

ADJG 1 vsDataContainer Id=adjgRDN, vsDataType=ADJG

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJG-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, VsDataContainer=ADJG-1

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

ADJI 1

vsDataContainer Id=adjiRDN, vsDataType=ADJI

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJI-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, VsDataContainer=ADJI-1

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

ADJL

vsDataContainer Id=adjlRDNvsDat aType=ADJL

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJL-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, VsDataContainer=ADJL-1

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

ADJS 1 vsDataContainer Id=adjsRDN, vsDataType=ADJS

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJS-1

SubNetwork=Nokia-1, ManagedElement=RNC-1,

ADJD

PLMNPLMN/RNC1/WBTS1/WCEL1/ADJD-1

SubNetwork=Nokia-1, ManagedElement=RNC-1,

Table 21

vsDataContainerId=adjdRDN, vsDataType=ADJD

The NetAct-specific parameters cannot be carried in 3GPP's UtranRelation RncFunction=RNC-1, UtranCell=WBTS-1/WCEL-1, VsData- object, but a separate vendor-specific object is Container=ADJS-1 needed.

RncFunction=RNC-1, UtranCell=WBTS-1/WCEL-1, VsDataContainer=ADJD-1

NetAct UTRAN vendor specific object/data mappings

DN03317891 Issue 10-1

Id:0900d80580942542

65


Object class COCO

IPNB

BTS (FBTS)

EWCE


Mapping

NetAct DN

3GPP DN

Notes

vsDataContainer Id=cocoRDN, vsDataType=COCO

PLMNPLMN/RNC1/COCO-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=COCO-1

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

vsDataContainer Id=ipnbRDN, vsDataType=IPNB

PLMNPLMN/RNC1/IPNB-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=IPNB-1

vsDataContainer Id=egceRDN, vsDataType=EGCE

PLMNPLMN/BSC0/BCF-0/BTS123 321

SubNetwork=Nokia-1, ExternalGsmCell=EGCE-123 321, VsDataContainer=EGCE123 321

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

vsDataContainer Id=ewceRDN, vsDataType=EWCE

PLMNPLMN/EXCC1/EWCE-1234

SubNetwork=Nokia-1, ExternalUtranCell=EWCE-1234, VsDataContainer=EWCE-1234

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

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

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

vsDataContainer Id=fmcgRDN, vsDataType=FMCG

PLMNPLMN/RNC1/FMCG-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=FMCG-1

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

FMCI

vsDataContainer Id=fmciRDN, vsDataType=FMCI

PLMNPLMN/RNC1/FMCI-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=FMCI-1


FMCS

vsDataContainer Id=fmcsRDN, vsDataType=FMCS

PLMNPLMN/RNC1/FMCS-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=FMCS-1


vsDataContainer Id=iurRDN, vsDataType=IUR

PLMNPLMN/RNC1/IUR-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=IUR-1

IUR

Table 21

66

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

Id:0900d80580942542

DN03317891 Issue 10-1


Object class


Mapping

NetAct DN

3GPP DN

Notes

HOPS

vsDataContainer Id=hopsRDN, vsDataType=HOPS

PLMNPLMN/RNC1/HOPS-1

SubNetwork=Nokia-1, Manage- ADJx MOs have references dElement=RNC-1, RcnFuncto HOPx MOs: HOPx MO tion=RNC-1, instance has to exist (at VsDataContainer=HOPS-1 least in the same plan) before it can be referred to.

HOPI

vsDataContainer Id=hopiRDN, vsDataType=HOPI

PLMNPLMN/RNC1/HOPI-1

SubNetwork=Nokia-1, Manage- ADJx MOs have references dElement=RNC-1, RcnFuncto HOPx MOs: HOPx MO tion=RNC-1, instance has to exist (at VsDataContainer=HOPI-1 least in the same plan) before it can be referred to.

HOPG

vsDataContainer Id=hopgRDN, vsDataType=HOPG

PLMNPLMN/RNC1/HOPG-1

SubNetwork=Nokia-1, Manage- ADJx MOs have references dElement=RNC-1, to HOPx MOs: HOPx MO instance has to exist (at RcnFunction=RNC-1, VsDataleast in the same plan) Container=HOPG-1 before it can be referred to.

WSMLC vsDataContainer Id=wsmlcRDN, vsDataType=WSML C

PLMNPLMN/RNC1/WSMLC-1

SubNetwork=Nokia-1,

WLCSE vsDataContainer Id=wlcseRDN, vsDataType=WLCS E

PLMNPLMN/RNC1/WLCSE-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=WLCSE-1

WANE

vsDataContainer Id=waneRDN, vsDataType=WANE

PLMNPLMN/RNC1/WANE-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=WANE-1

ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=WSMLC-1

There is one WSMLC per each RNC.

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

WSG

vsDataContainer Id=wsgRDN, vsDataType=WSG

PLMNPLMN/RNC1/WSG-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=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

vsDataContainer Id=rncRDN, vsDataType=RNC

PLMNPLMN/RNC-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=RNC-1

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

no corresponding NetAct DN

SubNetwork=Nokia-1, ExternalRncFunction=RNC-1, VsDataContainer=RNC-1

This is a special mapping. Check Figure 4.

RNC/IurIte VsDataContainer Id=NRncId (ID of m the neighbouring RNC), vsDataType=RNC

Table 21


DN03317891 Issue 10-1

Id:0900d80580942542

67


Object class

Mapping


NetAct DN

3GPP DN

Notes

WBTS 1 vsDataContainer Id=wbtsRDN, vsDataType=WBTS

PLMNPLMN/RNC1/WBTS-1

SubNetwork=Nokia-1, ManagedElement=RNC-1/WBTS-1, NodeBFunction=RNC-1/WBTS1, VsDataContainer=WBTS-1

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

WCEL 1 vsDataContainer Id=wcelRDN, vsDataType=WCEL

PLMNPLMN/RNC1/WBTS1/WCEL-1

SubNetwork=Nokia-1, ManagedElement=RNC-1, RncFunction=RNC-1, UtranCell=WBTS1/WCEL-1, VsDataContainer=WCEL-1

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

ANTE

vsDataContainer Id=rRDN, vsDataType=ANTE

PLMNPLMN/ANTC1/ANTE-1/

SubNetwork=Nokia-1, ManagedElement=ANTC-1/ ANTE-1, Antenna=ANTE-1, vsDataContainer=ANTE-1

The NetAct-specific parameters 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

vsDataContainer Id=rRDN, vsDataType=WCAL

PLMNPLMN/ANTC1/ANTE1/WCAL-1

SubNetwork=Nokia-1, ManagedElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataContainer=WCAL-1

GCAL

vsDataContainer Id=rRDN, vsDataType=GCAL

PLMNPLMN/ANTC1/ANTE1/GCAL-1

SubNetwork=Nokia-1, ManagedElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataContainer=GCAL-1

EUCAL vsDataContainer Id=rRDN, vsDataType=EUCA L

PLMNPLMN/ANTC1/ANTE1/EUCAL-1

SubNetwork=Nokia-1, ManagedElement=ANTC-1, ANTE-1, Antenna=ANTE-1, VsDataContainer=EUCAL-1

IUPS

vsDataContainer Id=iupsRDN, vsDataType=IUPS

PLMNPLMN/RNC1/IUPS-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IUPS-1

IUPSIP vsDataContainer Id=iupsRDN/iups ipDN, vsDataType=IUPS IP

PLMNPLMN/RNC1/IUPS1/IUPSIP-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IUPS1/IUPSIP-1

IUCS

vsDataContainer Id=iucsRDN, vsDataType=IUCS

PLMNPLMN/RNC1/IUCS-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IUCS-1

IUCSIP vsDataContainer Id=iucsRDN/iucs ipDN, vsDataType=IUCS IP

PLMNPLMN/RNC1/IUCS1/IUCSIP-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IUCS1/IUCSIP-1

Table 21

68


Id:0900d80580942542

DN03317891 Issue 10-1


Object class


Mapping

NetAct DN

3GPP DN

VBTS

vsDataContainer Id=vbtsRDN, vsDataType=VBTS

PLMNPLMN/RNC1/VBTS-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=VBTS-1

VCEL

vsDataContainer Id=vbtsRDN/vcel DN, vsDataTyep=VCEL

PLMNPLMN/RNC1/VBTS1/VCEL-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=VBTS1/VCEL-1

CMOB

vsDataContainer Id=cmobRDN, vsDataType=CMOB

PLMNPLMN/RNC1/CMOB-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=CMOB-1

vsDataContainer Id=iuoRDN, vsDataType=IUO

PLMNPLMN/RNC1/IUO-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IUO-1

IUO

RNPS

vsDataContainer Id=rnpsRDN, vsDataType=RNPS

PLMNPLMN/RNC1/RNPS-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNPS-1

RNAC

vsDataContainer Id=rnacRDN, vsDataType=RNAC

PLMNPLMN/RNC1/RNAC-1

SubNetwork=Nokia-1,

Notes

ManagedElement=RNC-1, RcnFunction=RNC-1, VsDataContainer=RNAC-2

RNRLC vsDataContainer Id=rnrlcRDN,vsD ataType=RNRLC

PLMNPLMN/RNC1/RNRLC-2

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNRLC-1

RNHSPA vsDataContainer Id=rnhspaRDN, vsDataType=RNHSPA

PLMNPLMN/RNC1/RNHSPA-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNHSPA-1

RNMOBI vsDataContainer Id=rnmobiRDN, vsDataType=RNMOBI

PLMNPLMN/RNC1/RNMOBI-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNMOBI-1

RNTRM vsDataContainer Id=rntrmRDN, vsDataType=RNTRM

PLMNPLMN/RNC1/RNTRM-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNTRM-1

RNFC

PLMNPLMN/RNC1/RNFC-2

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=RNFC-2

Table 21

vsDataContainer Id=rnfcRDN,vsDa taType=RNFC


DN03317891 Issue 10-1

Id:0900d80580942542

69


Object class

Mapping

NetAct DN

3GPP DN


CBCI

vsDataContainer Id=cbciRDN,vsDa taType=CBCI

PLMNPLMN/RNC1/CBCI-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=CBCI-1

TQM

vsDataContainer Id=tqmRDN,vsDat aType=TQM

PLMNPLMN/RNC1/TQM-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=TQM-1

IPQM

vsDataContainer Id=ipqmRDN,vsDa taType=IPQM

PLMNPLMN/RNC1/IPQM-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=IPQM-1

WRAB

vsDataContainer Id=wrabRDN,vsDa taType=WRAB

PLMNPLMN/RNC1/WRAB-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=WRAB-1

HOPL

vsDataContainer Id=hoplRDN,vsDa taType=HOPL

PLMNPLMN/RNC1/HOPL-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=HOPL-1

vsDataContainer Id=pflRDN,vsDat aType=PFL

PLMNPLMN/RNC1/PFL-1

SubNetwork=Nokia-1,ManagedElement=RNC-1,RncFunction=RNC1,VsDataContainer=PFL-1

PFL

Table 21

Notes

NetAct UTRAN vendor specific object/data mappings (Cont.) 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

Ahonen Nokia Siemens Networks RN4.0 RNC Ahonen

70

Id:0900d80580942542

DN03317891 Issue 10-1



184 RNC RN4.0 10 80 15 [...] 1 1 10808 11 330 370 -30 -30 -50 FDDMode 4459 14 15125 1 SubNetwork=Nokia-511410,ManagedElement=RNC-184,RncFunction=RNC184,IubLink=COCO-2 enabled WCEL RN4.0 1 358 03 [...]

DN03317891 Issue 10-1

Id:0900d80580942542

71

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


6 OSS5.x - 3GPP R8 object model mapping for LTE RL15/RL20 This 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,ManagedElement=MRBTS-100

ANTL

id=MRBTS RDN +”/” +ANTL RDN

PLMN-PLMN/ MRBTS-100/ ANTL-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=ANTL-1

BTSSCL

id=MRBTS RDN +”/” + BTSSCL RDN

PLMN-PLMN/ MRBTS-100/ BTSSCL-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=BTSSCL-1

LNBTS

id=MRBTS RDN+”/” +LNBTS RDN

PLMN-PLMN/ MRBTS-100/ LNBTS-100

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, ENBFunction=LNBTS-100

MHA

id=MRBTS RDN+”/” +MHA RDN

PLMN-PLMN/ MRBTS100/MHA-0

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=MHA-0

RET

id=MRBTS RDN+”/”+RET RDN

PLMN-PLMN/ MRBTS100/RET-0

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=RET-0,

RMOD

id=MRBTS RDN+”/”+RMOD RDN

PLMN-PLMN/ MRBTS-100/ RMOD-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=RMOD-1

SMOD

id=MRBTS RDN+”/”+SMOD RDN

PLMN-PLMN/ MRBTS-100/ SMOD-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=SMOD-1

LCELL

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

PLMN-PLMN/MRBTS100/BTSSCL-1/LECLL-0

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

ADIPNO

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

PLMN-PLMN/MRBTS100/LNBTS-100/ADIPNO-1

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

CTRLTS

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

PLMN-PLMN/MRBTS100/LNBTS-100/CTRLTS-1

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

Table 22

72


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

FTM

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1

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

GTPU

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

PLMN-PLMN/MRBTS100/LNBTS-100/GTPU-1

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

ITRACE

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

PLMN-PLMN/MRBTS100/LNBTS-100/ITRACE-1

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

LNADJ

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJ-0

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

LNADLP

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADLP-0

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

LNCEL

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, EUtranCellFDD/EUtranCellTDD=LNEL-0

LNMME

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNMME-0

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

SCTP

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

PLMN-PLMN/MRBTS100/LNBTS-100/SCTP-1

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

MTRACE

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

PLMN-PLMN/MRBTS100/LNBTS-100/CTRLTS0/MTRACE-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=CTRLS0/MTRACE-1

AMGR

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/AMGR-1

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

CERTH

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/CERTH-1

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

Table 22


DN03317891 Issue 10-1

Id:0900d80580942542

73



Object class

Mapping

NetAct DN

3GPP DN

ETHLK

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/ETHLK-1

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

IPNO

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1

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

IPSECC

id=MRBTS RDN+”/”+LNBTSRDN+”/”+FTMR DN+”/”+IPSECC RDN

PLMNPLMN/MRBTS100/LNBTS-100/FTM1/IPSECC-0

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, ENBFunction=LNBTS100,VsDataContainer=FTM 1/IPSECC-0

L2SWI

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/L2SWI-1

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

OAMMD

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/OAMMD-0

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

OAMPRF

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/OAMPRF-0

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

SYNC

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/SYNC-0

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

PPTT

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/PPTT-0

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

UNIT

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/UNIT-1

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

LNADJL

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJ0/LNADJL-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, EUtranCellTDD/EUtranCellFDD=LNCEL-100, EUtranRelation=LNADJ-0/LNADJL-1

Table 22


74

Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

GFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/GFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/GFIM-0

IAFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/IAFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/IAFIM-0

IRFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/IRFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/IRFIM-0

LNHOIF

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0//LNHOIF-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOIF-0

REDRT

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/REDRT-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/REDRT-0

UFFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/UFFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/UFFIM-0

GNFL

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/GFIM-0/GNFL-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/GFIM-0/GNFL-0

IEIF

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IEIF-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/IHCP-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/INTP-1

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

Table 22


DN03317891 Issue 10-1

Id:0900d80580942542

75



Object class

Mapping

NetAct DN

3GPP DN

IPRM

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IPRM-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/IPRT-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/QOS-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/TOPIK-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/OAMMD-0/OAMMA-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/SYNC-0/STPG-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/IPNO-1/IEIF-1/IVIF-1

SubNetwork=Nokia-1, ManagedElement=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/MRBTS100/LNBTS-100/FTM1/OAMMD-0/OAMMA1/OAMMEP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM 1/OAMMD-0/OAMMA1/OAMMEP-1

Table 22

Examples of instance mappings (Cont.) 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.

•

76

Id:0900d80580942542

DN03317891 Issue 10-1



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

6.1.1 6.1.1

•

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

•

managedBy is set to the 3GPP DN of the controlThe ManagedElement attribute managedBy is ling OMC.

Conside Considerat ration ions s in CM data data uploa upload d (NetA (NetAct ct mode modell

3GPP model)


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

•

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

•

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

•

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

•

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

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

6.1.2 6.1.2

•


•

The NOM vendor-specific attributes for common o bjects are provided in vsDataContainer.

Consid Considera eratio tions ns in CM CM data data downlo download ad (3GPP (3GPP model model

NetAct model)

During the download of R8OM objects:

DN03317891 Issue 10-1

•

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

•

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.

•


Id:0900d80580942542

77



7 OSS5. OSS5.x x - 3GPP 3GPP R8 R8 obje object ct mode modell map mappin ping g for for LTE RL25/RL30 This chapter describes the instance mappings between NetAct Object Model (NOM) and 3GPP R8 Object Model (R8OM).

7.1 7.1

Inst Instan ance ce mappi mapping ngs s for for RL25 RL25/R /RL3 L30 0 This section describes examples of instance mappings.

Object class

Mapping

NetAct DN

3G PP DN

MRBTS

id=MRBTS RDN

PLMN-PLMN/ MRBTS-100

SubNetwork=Nokia-1,ManagedElement=MRBTS-100

ANTL


PLMN-PLMN/ MRBTS-100/ ANTL-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=ANTL-1

BTSSCL


PLMN-PLMN/ MRBTS-100/ BTSSCL-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=BTSSCL-1

LNBTS


PLMN-PLMN/ MRBTS-100/ LNBTS-100

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, ENBFunction=LNBTS-100

MHA

id=MHA RDN

PLMN-PLMN/MHA-0

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=MHA-0

RET


PLMN-PLMN/ MRBTS100/RET-0

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=RET-0,

RMOD


PLMN-PLMN/ MRBTS-100/ RMOD-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=RMOD-1

SMOD

id=MRBTS RDN+”/”+SM OD RDN

PLMN-PLMN/ MRBTS-100/ SMOD-1

SubNetwork=Nokia-1,ManagedElement=MRBTS-100, VsDataContainer=SMOD-1

LCELL




ADIPNO


PLMN-PLMN/MRBTS100/LNBTS-100/ADIPNO-1


CTRLTS


PLMN-PLMN/MRBTS100/LNBTS-100/CTRLTS-1


Table 23

78


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

FTM




GTPU




LN AD J




LN AD JG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADJG-0

LN AD JW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADJW-0

LN CEL



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, EUtranCellFDD/EUtranCellTDD=LNCEL-0

LN MME




MODPR

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MODPR-0

MOPR

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MOPR-0

PMRNL

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=PMRNL-0

SCTP




Table 23


DN03317891 Issue 10-1

Id:0900d80580942542

79



Object class

Mapping

NetAct DN

3GPP DN

MTRACE

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



AMGR



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

CERTH



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

ETHLK



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

IPNO


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1

IPSECC

id=MRBTS RDN+”/”+LNBTSRDN+”/”+FT MRDN+”/”+IPSECC RDN


SubNetwork=Nokia-1,ManagedElement=MRBTS-100, ENBFunction=LNBTS100,VsDataContainer=FTM 1/IPSECC-0

L2SWI



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

OAMMD




OAMPRF




PMTNL

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM 1/PMTNL-0

Table 23

80


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

SYNC



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

PPTT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/PPTT0

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

TAC

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

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

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TAC0

UNIT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/UNIT1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/UNIT1

LNADJL




LNRELG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNRELG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNRELG-0

LNRELW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNRELW-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNRELW-0

CDFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/CDFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/CDFIM-0

GFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/GFIM-0

IAFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/IAFIM-0

Table 23


DN03317891 Issue 10-1

Id:0900d80580942542

81



Object class

Mapping

NetAct DN

3GPP DN

LNHOG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOG-0

IRFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/IRFIM-0

LNHOIF


PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOIF-0


LNHOW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOW-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOW-0

LNREL

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNREL-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNREL-0

REDRT




UFFIM




MODRED

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

PLMN-PLMN/MRBTS100/LNBTS-100/MODPR0/MODRED-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MODPR0/MODRED-0

MORED

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

PLMN-PLMN/MRBTS100/LNBTS-100/MOPR0/MORED-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MOPR0/MORED-0

GNFL



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/GFIM-0/GNFL-0

Table 23

82


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

BFD

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/BFD-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/BFD-1

BFDGRP

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/BFDGRP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/BFDGRP-1

IEIF


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/IEIF-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IEIF-1

IHCP


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/IHCP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IHCP-1

INTP


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/INTP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/INTP-1

IPRM


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/IPRM-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IPRM-1

IPRT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/IPRT-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IPRT-1

QOS


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/QOS-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/QOS-1

TOPIK


PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/TOPIK-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/TOPIK-1

TWAMP

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/TWAMP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/TWAMP-1

Table 23


DN03317891 Issue 10-1

Id:0900d80580942542

83



Object class

Mapping

NetAct DN

3GPP DN

OAMMA




STPG



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

LTAC

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/TAC0/LTAC-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TAC0/LTAC-1

IVIF

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM-1/IPNO1/IEIF-1/IVIF-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IEIF-1/IVIF-1

OAMMEP



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM 1/OAMMD-0/OAMMA1/OAMMEP-1

Table 23


7.1.1

Considerations in CM data upload (NetAct model

3GPP model)


OMC: mapped to two common R8OM objects: ManagementNode and Subnetwork.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.

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

84

•


•


Id:0900d80580942542

DN03317891 Issue 10-1


7.1.2


Considerations in CM data download (3GPP model

NetAct model)

During the download of R8OM objects:

DN03317891 Issue 10-1

•

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

•

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.

•


Id:0900d80580942542

85

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


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

8.1

Instance mappings for RL40 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, ManagedElement=MRBTS-100

ANTL


PLMN-PLMN/MRBTS100/ANTL-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=ANTL-1

BTSSCL


PLMN-PLMN/MRBTS100/BTSSCL-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=BTSSCL-1

LNBTS


PLMN-PLMN/MRBTS100/LNBTS-100

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100

MHA

id=MHA RDN

PLMN-PLMN/MHA-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=MHA-0

RET


PLMN-PLMN/MRBTS100/ RET-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=RET-0

RMOD


PLMN-PLMN/MRBTS100/RMOD-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=RMOD-1

SMOD

id=MRBTS RDN+”/”+SMOD RDN

PLMN-PLMN/MRBTS100/SMOD-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, VsDataContainer=SMOD-1

LCELL




ADIPNO


PLMN-PLMN/MRBTS100/LNBTS-100/ADIPNO1


CTRLTS


PLMN-PLMN/MRBTS100/LNBTS-100/CTRLTS1


Table 24

86


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

FTM




GTPU




LNADJ




LNADJG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJG0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADJG-0

LNADJW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNADJG0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNADJW-0

LNCEL




LNMME


PLMN-PLMN/MRBTS100/LNBTS-100/LNMME0

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

MODPR

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MODPR-0

MOPR

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MOPR-0

PMRNL

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=PMRNL-0

SCTP




MTRACE

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



Table 24


DN03317891 Issue 10-1

Id:0900d80580942542

87



Object class

Mapping

NetAct DN

3GPP DN

AMGR



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

CERTH



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/CERTH1

ETHLK



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/ETHLK1

IPNO


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1

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

IPSECC

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM 1/IPSECC-0

L2SWI



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

OAMMD




OAMPRF




PMTNL

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


SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/PMTNL0

SYNC



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

PPTT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/PPTT-0

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

Table 24

88


Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

TAC

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/TAC-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TAC-0

TOPB

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/TOPB-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TOPB-0

UNIT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/UNIT-1

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

LNADJL




LNRELG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNRELG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNRELG-0

LNRELT

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNRELT-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNRELT-0

LNRELW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNRELW-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNRELW-0

CDFIM

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/CDFIM-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/CDFIM-0

GFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/GFIM0

IAFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/IAFIM0

Table 24


DN03317891 Issue 10-1

Id:0900d80580942542

89



Object class

Mapping

NetAct DN

3GPP DN

LNHOG

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOG-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOG-0

IRFIM



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/IRFIM0

LNHOIF


PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOIF-0


LNHOT

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOT-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOT-0

LNHOW

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNHOW-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNHOW-0

LNREL

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

PLMN-PLMN/MRBTS100/LNBTS-100/LNCEL0/LNREL-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL0/LNREL-0

REDRT




UFFIM




MODRED

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

PLMN-PLMN/MRBTS100/LNBTS-100/MODPR0/MODRED-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MODPR0/MODRED-0

MORED

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

PLMN-PLMN/MRBTS100/LNBTS-100/MOPR0/MORED-0

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=MOPR0/MORED-0

Table 24


90

Id:0900d80580942542

DN03317891 Issue 10-1



Object class

Mapping

NetAct DN

3GPP DN

GNFL



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=LNCEL-0/GFIM0/GNFL-0

BFD

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/BFD-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/BFD-1

BFDGRP

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/BFDGRP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/BFDGRP-1

IEIF


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IEIF-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IEIF-1

IHCP


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IHCP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IHCP-1

INTP


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/INTP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/INTP-1

IPRM


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IPRM-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IPRM-1

IPRT


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IPRT-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IPRT-1

QOS


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/QOS-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/QOS-1

TOPIK


PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/TOPIK-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/TOPIK-1

Table 24


DN03317891 Issue 10-1

Id:0900d80580942542

91



Object class

Mapping

NetAct DN

3GPP DN

TWAMP

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/TWAMP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/TWAMP-1

OAMMA




STPG



SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/SYNC0/STPG-1

LTAC

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/TAC-0/LTAC-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TAC0/LTAC-1

TOPF

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/TOPB-0/TOPF-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TOPB0/TOPF-1

TOPP

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/TOPB-0/TOPP-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/TOPB0/TOPP-1

IVIF

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

PLMN-PLMN/MRBTS100/LNBTS-100/FTM1/IPNO-1/IEIF-1/IVIF-1

SubNetwork=Nokia-1, ManagedElement=MRBTS-100, ENBFunction=LNBTS-100, VsDataContainer=FTM -1/IPNO1/IEIF-1/IVIF-1

OAMMEP



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

EXENBF

id=EXENBF RND

PLMN-PLMN/EXCENBF1/EXENBF-1

SubNetWork=Nokia-1,ExternalENBFunction=EXCENBF-1/EXENBF1

EXEUCE

id=EXENBF RND+”/”+EXEUCE RDN

PLMN-PLMN/EXCENBF1/EXENBF-1/EXEUCE-1

SubNetwork=Nokia-1, ExternalENBFunction=EXCENBF-1/EXENBF1, ExternalEUtranCellFDD/ExernalEUtranCellTDD=EXEUCE-1

Table 24

92


Id:0900d80580942542

DN03317891 Issue 10-1


8.2


Considerations in CM data upload (NetAct model model)

3GPP

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:

8.3

•


•

The NSN internal NRM vendor-specific attributes for common obje cts are provided in VsData-Container .

Considerations in CM data download (3GPP model NetAct model) During the download of R8OM objects: •

•

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.

•

DN03317891 Issue 10-1

ManagementNode and Subnetwork are combined in one NSN internal NRM object OMC, which holds all ManagementNode and Subnetwork attributes in the NSN internal NRM.

The NSN internal NRM vendor-specific attributes for common objects are provided in VsData-Container .

Id:0900d80580942542

93

Troubleshooting


9 Troubleshooting The following steps describe how to troubleshoot the 3GPP CORBA Bulk CM Northbound Interface. To restart the 3GPP CORBA Bulk CM Northbound Interface

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/.rac3gpmx. Terminate rac3gpmx process with command: kill -TERM 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/.wpmanamx..< PID> Send HUP signal to wpmanamx process: kill -HUP 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 3 GPP CORBA Bulk CM N orthbound Interface process

Stop the process with: kill -TERM The process will be shutdown and removed from WPMANA control. Start the process manually with: /opt/nokia/oss/configurator/rac/rac3gp/bin/rac3gpmx.sh& to /opt/nokia/oss/bin/rac3gpmx.sh

94

Id:0900d80580942542

DN03317891 Issue 10-1


Where to find more information

10 Where to find more information For more information on NetAct Configurator, see NetAct Configurator Principles, DN03317888. For more information on technical aspects of NetAct Configurator, see NetAct Configurator 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 (200503)

•

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):

DN03317891 Issue 10-1

•

3GPP TS 32.762 V8.2.0 Evolved Universal Terrestrial Radio Access Network (EUTRAN) Network Resource Model (NRM) Integration Reference Point (IRP)

•

3GPP TS 32.300 v8.0.0 Name Convention for Managed Objects (12/2008)

Id:0900d80580942542

95

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: BulkCmIRPConstDefs This module contains type definitions for the Bulk CM IRP ================================================================ */ module BulkCmIRPConstDefs { /* This block identifies the notification types defined by this Bulk CM IRP version. This string is used in the second field of the Structured Event. */ 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 the Structured 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";

96

Id:0900d80580942542

DN03317891 Issue 10-1


const const const const const const const const const const

string string string string string string string string string string


ACTIVATION_PARTLY_REALISED = "x6"; ACTIVATION_COMPLETED = "x7"; FALLBACK_FAILED = "x8"; FALLBACK_PARTLY_REALISED = "x9"; FALLBACK_COMPLETED = "x10"; VALIDATION_FAILED = "x11"; VALIDATION_COMPLETED = "x12"; PREACTIVATION_FAILED = "x13"; PREACTIVATION_PARTLY_REALISED = "x14"; PREACTIVATION_COMPLETED = "x15";

}; /* This block defines all possible values for sessionLogStatus One of these strings appear in the event_name of the Structured Event 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 generated by the IRPManager. An sessionId can not be used for an upload if it is already in use of a download configuration and vice versa. */ typedef string SessionId; /* This string field is used in order to provide additional error information if an operation has failed. */ typedef string ErrorInformation; /* Defines the different subphases of a configuration session e.g. thus it is easy to implement a detection of an upload or a download/activate session. */ enum SubPhase {IdlePhase, DownloadPhase, UploadPhase, ActivationPhase, FallbackPhase, PreactivationPhase, ValidationPhase}; /* Defines the different substates of a configuration session. This includes the transition state as well. */ enum SubState {Completed, Failed, PartlyRealised, InProgress}; /*

DN03317891 Issue 10-1

Id:0900d80580942542

97



Defines state of a configuration session with the phase and the substate of the configuration. */ struct SessionState { SubPhase sub_phase; SubState sub_state; }; /* Contains the list of all current sessionIds */ typedef sequence SessionIdList; /* Specifies a complete destination path (including filename). */ typedef string FileDestination; /* The format of Distinguished Name is specified in the Naming Conventions for Managed Objects; TS 32.300. e.g. "SubNetwork=10001,ManagedElement=400001" identifies a ManagedElement 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 with SearchControl.level, in a SearchControl value. SearchControl.level is always >= 0. If a level is bigger than the depth 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 be set to an empty string if it has no other value). */ struct SearchControl {

98

Id:0900d80580942542

DN03317891 Issue 10-1



ScopeType type; unsigned long level; FilterType filter; }; /* This indicates how the activation is executed, either with least service impact 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_

DN03317891 Issue 10-1

Id:0900d80580942542

99

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" // This statement must appear after all include statements #pragma prefix "3gppsa5.org" /* ## Module: BulkCmIRPSystem This 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 ManagedElement instance. 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 reason is outside the scope of this IRP. */ exception IllegalFilterFormatException { string reason; }; /* The provided Distinguished Name is malformed or invalid. The semantics carried in reason is outside the scope of this IRP. */ exception IllegalDNFormatException { string reason; }; /* The provided scope type is illegal. The semantics carried in reason is outside the scope of this IRP. */ exception IllegalScopeTypeException { string reason; }; /* The provided scope level is illegal. The semantics carried in reason is outside the scope of this IRP. */ exception IllegalScopeLevelException { string reason; };

100

Id:0900d80580942542

DN03317891 Issue 10-1



/* The request cannot be processed because no fallback data is available, that is fallback capability was previously not asked for. */ exception NoFallbackException {}; /* The provided sessionId value is already used for another configuration session. 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 is outside the scope of this IRP. */ exception IllegalURLFormatException{ string reason; }; /* The provided sessionId value does not identify any existing configuration session. */ exception UnknownSessionIdException {}; /* The request cannot be processed because it is not valid in the current state of the configuration session. */ exception NotValidInCurrentStateException { BulkCmIRPConstDefs::SessionState current_state; }; /* The request cannot be processed because the maximum number of simultaneously running configuration sessions has been reached. The semantics carried in reason is outside the scope of this IRP. */ exception MaxSessionReachedException { string reason; }; /* The provided ActivationMode type is illegal. The semantics carried in reason is outside the scope of this IRP. */ exception IllegalActivationModeException { string reason; }; /* The provided VerificationMode type is illegal. The semantics carried in reason is outside the scope of this IRP. */ exception IllegalVerificationModeException { string reason; };

DN03317891 Issue 10-1

Id:0900d80580942542

101



/* System otherwise fails to complete the operation. System can provide reason to qualify the exception. The semantics carried in reason is 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 are necessary 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 supported parameters 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 supported parameters for a specific BulkCM IRP version. */ ManagedGenericIRPConstDefs::MethodList

102

Id:0900d80580942542

DN03317891 Issue 10-1



get_bulk_CM_IRP_notification_profile ( in ManagedGenericIRPConstDefs::VersionNumber bulk_CM_IRP_version ) raises (GetBulkCMIRPNotificationProfileException, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter); /* Uploads a configuration from the subnetwork. The result is put in a configuration 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 will return an exception. If the value of the given baseObject or FilterType does 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 from a given configuration data file storage area. The EM will check the consistence 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 configuration inside a session. This means that the configuration will be introduced in the live sub-network. In case of a concurrent running session the function will return an exception.

DN03317891 Issue 10-1

Id:0900d80580942542

103



*/ 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 error analysis. The log is put in a logfile in the filesystem which can be accessed by the EM. If there are no log entries an empty log file is 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. The IDLE_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 a fallback area can be created, s. activate parameter.

104

Id:0900d80580942542

DN03317891 Issue 10-1



This area is backup of the complete configuration which can be restored 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 activation of the new planned data has started. Only one fallback area can exists at a time for a specific scope of the subnetwork. 2. When a fallback area is available and triggered by this method, the previous valid area is replaced with the data stored in the fall back area. If the EM detects that the former configuration has never been changed it returns an exception because it does not trigger an activation 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 temporary entities and the related sessionId which belong to the scope of a configuration session. This includes the related error and log information too. */ void end_session ( in BulkCmIRPConstDefs::SessionId session_id ) raises (EndSessionException, UnknownSessionIdException, NotValidInCurrentStateException, ManagedGenericIRPSystem::InvalidParameter); /* The IRPManager invokes this operation to abort an active operation during a configuration session. It is only effecting a configuration session in state IN_PROGRESS. In this case the current 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 (

DN03317891 Issue 10-1

Id:0900d80580942542

105



) raises (GetSessionIdsException); /* Validates previously downloaded bulk configuration data inside a session. Detects errors in the data prior to requesting preactivation or activation. */ 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 a session. This operation validates configuration data changes in the context of the current data and pre-processes the configuration data changes. */ 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; };

106

Id:0900d80580942542

DN03317891 Issue 10-1



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 supported parameters 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, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter); /* Return the list of all supported notifications and their supported parameters 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, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter);

/* Uploads a configuration from the subnetwork. The result is put in a configuration 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 will return an exception. If the value of the given baseObject or FilterType does 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

DN03317891 Issue 10-1

Id:0900d80580942542

107



) 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 supported parameters 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, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter); /* Return the list of all supported notifications and their supported

108

Id:0900d80580942542

DN03317891 Issue 10-1



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, ManagedGenericIRPSystem::OperationNotSupported, ManagedGenericIRPSystem::InvalidParameter);

/* Uploads a configuration from the subnetwork. The result is put in a configuration 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 will return an exception. If the value of the given baseObject or FilterType does 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 ( 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 error analysis. The log is put in a logfile in the filesystem which can be accessed by the EM. If there are no log entries an empty log file is uploaded. */ void get_session_log ( in BulkCmIRPConstDefs::FileDestination sink, in BulkCmIRPConstDefs::SessionId session_id, in boolean only_error_info

DN03317891 Issue 10-1

Id:0900d80580942542

109



) raises ( BulkCmIRPSystem::GetSessionLogException, BulkCmIRPSystem::UnknownSessionIdException, BulkCmIRPSystem::IllegalURLFormatException, ManagedGenericIRPSystem::InvalidParameter); /* Creates an instance of the configuration session state machine. The IDLE_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 temporary entities and the related sessionId which belong to the scope of a configuration session. This includes the related error and log information too. */ void end_session ( in BulkCmIRPConstDefs::SessionId session_id ) raises ( BulkCmIRPSystem::EndSessionException, BulkCmIRPSystem::UnknownSessionIdException, BulkCmIRPSystem::NotValidInCurrentStateException, ManagedGenericIRPSystem::InvalidParameter);

/* The IRPManager invokes this operation to abort an active operation during a configuration session. It is only effecting

110

Id:0900d80580942542

DN03317891 Issue 10-1



a configuration session in state IN_PROGRESS. In this case the current 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 ( 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_

DN03317891 Issue 10-1

Id:0900d80580942542

111

Appendix C: BulkCMIRPNotifications.idl


13 Appendix C: BulkCMIRPNotifications.idl // File: BulkCMNotifications.idl #ifndef _BULKCMIRPNOTIFICATIONS_IDL_ #define _BULKCMIRPNOTIFICATIONS_IDL_ #include #include // This statement must appear after all include statements #pragma prefix "3gppsa5.org" 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::

112

Id:0900d80580942542

DN03317891 Issue 10-1


Appendix C: BulkCMIRPNotifications.idl

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_

DN03317891 Issue 10-1

Id:0900d80580942542

113

Appendix D: LTE RL40 3GPP XML file example


14 Appendix D: LTE RL40 3GPP XML file example Nokia Siemens Networks SubNetwork=Nokia-511115,ManagementNode=OMC-511115 LN3.0 MRBTS MRBTS LN3.0 0 LD_mrbts_pronto 0 0 0 0 0

114

Id:0900d80580942542

DN03317891 Issue 10-1



0 323 1 471894A FR 1 HA 0 471469A FSM 1 E LCELL LN3.0 1 0 2 2 LCELL LN3.0 5 0

DN03317891 Issue 10-1

Id:0900d80580942542

115



10.46.156.50 LNBTS LN3.0 555 10 0 0 1 0 0 0 0 0 0 0 0 0 0 0 1 1 0 0 0 0 0 1 0 0 1 0 0 1 1 4 2 5

116

Id:0900d80580942542

DN03317891 Issue 10-1



53 7 5 4 8 6 5 9 0 1 9 1 1 1 1 9 1 50000 1 5 2 1 3 2 101 4 0 0 102 0 1 2 3 2 3 3 2 4 3 2 5 3 2 0 3 246 1

DN03317891 Issue 10-1

Id:0900d80580942542

117



101 2 1 1 0 0 101 1 5 2 26 2 102 4 2 0 0 0 102 1 7 2 46 2 102 3 3 0 0 0 102 1 6 2 28 2 2 4 4 0 0 0 2 3 8 3 34 2 1 1 5

118

Id:0900d80580942542

DN03317891 Issue 10-1



1 1 0 1 1 9 1 40 3 18 3 1 6 6 1 1 0 1 3 9 20 3 28 2 1 7 7 1 1 0 1 1 10 10 3 10 3 1 8 8 1 1 0 1 3 11 5 3 0 3 1

DN03317891 Issue 10-1

Id:0900d80580942542

119



9 9 1 1 0 1 3 12 1 2 1 49 10 10 101 0 0 10 102 0 0 10 0 2 23 10 10 0 3 23 10 10 4 4 23 10 10 4 5 23 10 10 6 60 150 500 10 10

120

Id:0900d80580942542

DN03317891 Issue 10-1



STPG LN3.0 LTAC LN3.0 1 0 1000000 1000000 1000000 QOS LN3.0 46 0 6 0 10 100 1000 10000 1 0 46 CPLANE 34

DN03317891 Issue 10-1

Id:0900d80580942542

121



MPLANE IPRM LN3.0 IEIF LN3.0 10.46.156.50 1500 255.255.255.0 1 1522 1522 1000000 1000000 2 0 1 BFDGRP LN3.0 BFDGRP LN3.0 BFDGRP

122

Id:0900d80580942542

DN03317891 Issue 10-1



LN3.0 TOPIK LN3.0 0 -3 10.44.34.45 IHCP LN3.0 INTP LN3.0 10.46.151.43 IPRT LN3.0 0 0.0.0.0 10.46.156.254 0.0.0.0 1

DN03317891 Issue 10-1

Id:0900d80580942542

123



IDNS LN3.0 10.44.35.81 0.0.0.0 ETHLK LN3.0 0 0 0 0 0 0 0 00:40:43:6c:4b:ae 0 ETHLK LN3.0 0 0 0 0 0 0 0 00:40:43:6c:4b:ae 0

124

Id:0900d80580942542

DN03317891 Issue 10-1



IRFIM LN3.0 25000 34 2 0 4 3 15 -68 IAFIM LN3.0 0 151 15 PPTT LN3.0 0 1 2

DN03317891 Issue 10-1

Id:0900d80580942542

125



CERTH LN3.0 30 30 C=FI, O=NSN, CN=MRTAmpereNewRootCA 10.8.207.54 8080 24 L2SWI LN3.0 0 6 1 6 0 8 1 6 1 1 0 IRFIM LN3.0 25000 34 2 0 4 3

126

Id:0900d80580942542

DN03317891 Issue 10-1



15 -68 Macro large 123 152 5 3050 21050 -15 555 10 Enabled Unlocked LNCEL LN3.0 16 104 0 55510144 false SubNetwork=Nokia-511115,ManagedElement=MRBTS-

DN03317891 Issue 10-1

Id:0900d80580942542

127



20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1 yes LNADJL LN3.0 555 10 555 10 3 48 1 3050 21050 144 0 123 3 1 Macro large 123 151 5 3050 21050 -15 555 10 Enabled Unlocked

128

Id:0900d80580942542

DN03317891 Issue 10-1



LNCEL LN3.0 16 55510144 false SubNetwork=Nokia-511115,ManagedElement=MRBTS20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1 yes LNADJL LN3.0 555 10 555 10 3 48 1 3050 21050 144 0 123 3 1

DN03317891 Issue 10-1

Id:0900d80580942542

129



FTM LN3.0 SyVe_Ulm FTM_L30_196.00 LTE50 Macro large 123 150 5 3050 21050 -15 555 10 Enabled Unlocked LNCEL LN3.0 16

130

Id:0900d80580942542

DN03317891 Issue 10-1



55510144 false SubNetwork=Nokia-511115,ManagedElement=MRBTS20050,ENBFunction=LNBTS-20050,EUtranCellFDD=LNCEL-1 yes LNADJL LN3.0 555 10 555 10 3 48 1 3050 21050 144 0 123 3 1 LNMME LN3.0 555 10 555 10 1 65531 01 3

DN03317891 Issue 10-1

Id:0900d80580942542

131



SCTP LN3.0 5 130 5 60 1 30 LNADJ LN3.0 ANTL LN3.0 0 1 5 80 -30 0 -1 1 0 ANTL LN3.0

132

Id:0900d80580942542

DN03317891 Issue 10-1



0 1 0 80 -30 1 -1 1 0 ANTL LN3.0 0 1 3 80 -30 0 -1 1 0 BTSSCL LN3.0 2 120

DN03317891 Issue 10-1

Id:0900d80580942542

133



120 4 1 2 120 120 5 1 20050 LTE20050 0 0 2 1 0 0 0 RMOD LN3.0 1 1 1 SyVe_Ulm 471894A 0 _EMPTY_

134

Id:0900d80580942542

DN03317891 Issue 10-1



DN03317891 Issue 10-1

Id:0900d80580942542

135

3GPP_CORBA_Bulk_CM_Northbound.pdf

Recommend Documents