Sie sind auf Seite 1von 90

3GPP

OSS

INTERFACE

DEVELOPER

GUIDE

3GPP OSS INTERFACE DEVELOPER GUIDE Alcatel-Lucent 5620 SERVICE AWARE MANAGER | RELEASE 10.0 R5 3GPP OSS

Alcatel-Lucent 5620

SERVICE AWARE MANAGER | RELEASE 10.0 R5

3GPP

OSS

INTERFACE

DEVELOPER

GUIDE

3HE 06977 AAAE TQZZA Edition 01

Alcatel-Lucent Proprietary This document contains proprietary information of Alcatel-Lucent and is not to be disclosed or used except in accordance with applicable agreements. Copyright 2012 © Alcatel-Lucent. All rights reserved.

or used except in accordance with applicable agreements. Copyright 2012 © Alcatel-Lucent. All rights reserved.

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice.

Alcatel, Lucent, Alcatel-Lucent, the Alcatel-Lucent logo, lightRadio, and TiMetra are registered trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

Copyright 2012 Alcatel-Lucent. All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

When printed by Alcatel-Lucent, this document is printed on recycled paper.

Alcatel-Lucent License Agreement

SAMPLE END USER LICENSE AGREEMENT

1. LICENSE

1.1 Subject to the terms and conditions of this Agreement, Alcatel-Lucent grants to Customer and Customer accepts a nonexclusive, nontransferable license to use any software and related documentation provided by Alcatel-Lucent pursuant to this Agreement ("Licensed Program") for Customer's own internal use, solely in conjunction with hardware supplied or approved by Alcatel-Lucent. In case of equipment failure, Customer may use the Licensed Program on a backup system, but only for such limited time as is required to rectify the failure.

1.2 Customer acknowledges that Alcatel-Lucent may have encoded within the Licensed Program optional functionality and capacity (including, but not limited to, the number of equivalent nodes, delegate workstations, paths and partitions), which may be increased upon the purchase of the applicable license extensions.

1.3 Use of the Licensed Program may be subject to the issuance of an application key, which shall be conveyed to the Customer in the form of a Supplement to this End User License Agreement. The purchase of a license extension may require the issuance of a new application key.

2. PROTECTION AND SECURITY OF LICENSED PROGRAMS

2.1 Customer acknowledges and agrees that the Licensed Program contains proprietary and confidential information of Alcatel-Lucent and its third party suppliers, and agrees to keep such information confidential. Customer shall not disclose the Licensed Program except to its employees having a need to know, and only after they have been advised of its confidential and proprietary nature and have agreed to protect same.

2.2 All rights, title and interest in and to the Licensed Program, other than those expressly granted to Customer herein, shall remain vested in Alcatel-Lucent or its third party suppliers. Customer shall not, and shall prevent others from copying, translating, modifying, creating derivative works, reverse engineering, decompiling, encumbering or otherwise using the Licensed Program except as specifically authorized under this Agreement. Notwithstanding the foregoing, Customer is authorized to make one copy for its archival purposes only. All appropriate copyright and other proprietary notices and legends shall be placed on all Licensed Programs supplied by Alcatel-Lucent, and Customer shall maintain and reproduce such notices on any full or partial copies made by it.

3. TERM

3.1 This Agreement shall become effective for each Licensed Program upon delivery of the Licensed Program to Customer.

3.2 Alcatel-Lucent may terminate this Agreement: (a) upon notice to Customer if any amount payable to Alcatel-Lucent is not paid within thirty (30) days of the date on which payment is due; (b) if Customer becomes bankrupt, makes an assignment for the benefit of its creditors, or if its assets vest or become subject to the rights of any trustee, receiver or other administrator; (c) if bankruptcy, reorganization or insolvency proceedings are instituted against Customer and not dismissed within 15 days; or (d) if Customer breaches a material provision of this Agreement and such breach is not rectified within 15 days of receipt of notice of the breach from Alcatel-Lucent.

3.3 Upon termination of this Agreement, Customer shall return or destroy all copies of the Licensed Program. All obligations of Customer arising prior to termination, and those obligations relating to confidentiality and nonuse, shall survive termination.

4. CHARGES

4.1 Upon shipment of the Licensed Program, Alcatel-Lucent will invoice Customer for all fees, and any taxes, duties and other charges. Customer will be invoiced for any license extensions upon delivery of the new software application key or, if a new application key is not required, upon delivery of the extension. All amounts shall be due and payable within thirty (30) days of receipt of invoice, and interest will be charged on any overdue amounts at the rate of 1 1/2% per month (19.6% per annum).

5. SUPPORT AND UPGRADES

5.1 Customer shall receive software support and upgrades for the Licensed Program only to the extent provided for in the applicable Alcatel-Lucent software support policy in effect from time to time, and upon payment of any applicable fees. Unless expressly excluded, this Agreement shall be deemed to apply to all updates, upgrades, revisions, enhancements and other software which may be supplied by Alcatel-Lucent to Customer from time to time.

6. WARRANTIES AND INDEMNIFICATION

6.1 Alcatel-Lucent warrants that the Licensed Program as originally delivered to Customer will function substantially in accordance with the functional description set out in the associated user documentation for a period of 90 days from the date of shipment, when used in accordance with the user documentation. Alcatel-Lucent's sole liability and Customer's sole remedy for a breach of this warranty shall be Alcatel-Lucent's good faith efforts to rectify the nonconformity or, if after repeated efforts Alcatel-Lucent is unable to rectify the nonconformity, Alcatel-Lucent shall accept return of the Licensed Program and shall refund to Customer all amounts paid in respect thereof. This warranty is available only once in respect of each Licensed Program, and is not renewed by the payment of an extension charge or upgrade fee.

6.2 ALCATEL-LUCENT EXPRESSLY DISCLAIMS ALL OTHER WARRANTIES, REPRESENTATIONS, COVENANTS OR CONDITIONS OF ANY KIND, WHETHER EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION, WARRANTIES OR REPRESENTATIONS OF WORKMANSHIP, MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, DURABILITY, OR THAT THE OPERATION OF THE LICENSED PROGRAM WILL BE ERROR FREE OR THAT THE LICENSED PROGRAMS WILL NOT INFRINGE UPON ANY THIRD PARTY RIGHTS.

6.3 Alcatel-Lucent shall defend and indemnify Customer in any action to the extent that it is based on a claim that the Licensed Program furnished by Alcatel-Lucent infringes any patent, copyright, trade secret or other intellectual property right, provided that Customer notifies Alcatel-Lucent within ten (10) days of the existence of the claim, gives Alcatel-Lucent sole control of the litigation or settlement of the claim, and provides all such assistance as Alcatel-Lucent may reasonably require. Notwithstanding the foregoing, Alcatel-Lucent shall have no liability if the claim results from any modification or unauthorized use of the Licensed Program by Customer, and Customer shall defend and indemnify Alcatel-Lucent against any such claim.

6.4 Alcatel-Lucent Products are intended for standard commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The Customer hereby agrees that the use, sale, license or other distribution of the Products for any such application without the prior written consent of Alcatel-Lucent, shall be at the Customer's sole risk. The Customer also agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the Products in such applications.

7. LIMITATION OF LIABILITY

7.1 IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF ALCATEL-LUCENT, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ANY CLAIM, REGARDLESS OF VALUE OR NATURE, EXCEED THE AMOUNT PAID UNDER THIS AGREEMENT FOR THE LICENSED PROGRAM THAT IS THE SUBJECT MATTER OF THE CLAIM. IN NO EVENT SHALL THE TOTAL COLLECTIVE LIABILITY OF ALCATEL-LUCENT, ITS EMPLOYEES, DIRECTORS, OFFICERS OR AGENTS FOR ALL CLAIMS EXCEED THE TOTAL AMOUNT PAID BY CUSTOMER TO ALCATEL-LUCENT HEREUNDER. NO PARTY SHALL BE LIABLE FOR ANY INDIRECT, SPECIAL OR CONSEQUENTIAL DAMAGES, WHETHER OR NOT SUCH DAMAGES ARE FORESEEABLE, AND/OR THE PARTY HAD BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7.2 The foregoing provision limiting the liability of Alcatel-Lucent's employees, agents, officers and directors shall be deemed to be a trust provision, and shall be enforceable by such employees, agents, officers and directors as trust beneficiaries.

8. GENERAL

8.1 Under no circumstances shall either party be liable to the other for any failure to perform its obligations (other than the payment of any monies owing) where such failure results from causes beyond that party's reasonable control.

8.2 This Agreement constitutes the entire agreement between Alcatel-Lucent and Customer and supersedes all prior oral and written communications. All amendments shall be in writing and signed by authorized representatives of both parties.

8.3 If any provision of this Agreement is held to be invalid, illegal or unenforceable, it shall be severed and the remaining provisions shall continue in full force and effect.

8.4 The Licensed Program may contain freeware or shareware obtained by Alcatel-Lucent from a third party source. No license fee has been paid by Alcatel-Lucent for the inclusion of any such freeware or shareware, and no license fee is charged to Customer for its use. The Customer agrees to be bound by any license agreement for such freeware or shareware. CUSTOMER ACKNOWLEDGES AND AGREES THAT THE THIRD PARTY SOURCE PROVIDES NO WARRANTIES AND SHALL HAVE NO LIABILITY WHATSOEVER IN RESPECT OF CUSTOMER'S POSSESSION AND/OR USE OF THE FREEWARE OR SHAREWARE.

8.5 Alcatel-Lucent shall have the right, at its own expense and upon reasonable written notice to Customer, to periodically inspect Customer's premises and such documents as it may reasonably require, for the exclusive purpose of verifying Customer's compliance with its obligations under this Agreement.

8.6 All notices shall be sent to the parties at the addresses listed above, or to any such address as may be specified from time to time. Notices shall be deemed to have been received five days after deposit with a post office when sent by registered or certified mail, postage prepaid and receipt requested.

8.7 If the Licensed Program is being acquired by or on behalf of any unit or agency of the United States Government, the following provision shall apply: If the Licensed Program is supplied to the Department of Defense, it shall be classified as "Commercial Computer Software" and the United States Government is acquiring only "restricted rights" in the Licensed Program as defined in DFARS 227-7202-1(a) and 227.7202-3(a), or equivalent. If the Licensed Program is supplied to any other unit or agency of the United States Government, rights will be defined in Clause 52.227-19 or 52.227-14 of the FAR, or if acquired by NASA, Clause 18-52.227-86(d) of the NASA Supplement to the FAR, or equivalent. If the software was acquired under a contract subject to the October 1988 Rights in Technical Data and Computer Software regulations, use, duplication and disclosure by the Government is subject to the restrictions set forth in DFARS 252-227.7013(c)(1)(ii) 1988, or equivalent.

8.8 Customer shall comply with all export regulations pertaining to the Licensed Program in effect from time to time. Without limiting the generality of the foregoing, Customer expressly warrants that it will not directly or indirectly export, reexport, or transship the Licensed Program in violation of any export laws, rules or regulations of Canada, the United States or the United Kingdom.

8.9 No term or provision of this Agreement shall be deemed waived and no breach excused unless such waiver or consent is in writing and signed by the party claimed to have waived or consented. The waiver by either party of any right hereunder, or of the failure to perform or of a breach by the other party, shall not be deemed to be a waiver of any other right hereunder or of any other breach or failure by such other party, whether of a similar nature or otherwise.

8.10 This Agreement shall be governed by and construed in accordance with the laws of the Province of Ontario. The application of the United Nations Convention on Contracts for the International Sale of Goods is hereby expressly excluded.

Preface

The Preface provides general information about the 5620 Service Aware Manager documentation suite, including this guide.

Prerequisites

Readers of the 5620 SAM documentation suite are assumed to be familiar with the following:

5620 SAM software structure and components

5620 SAM GUI operations and tools

typical 5620 SAM management tasks and procedures

device and network management concepts

5620 SAM documentation suite

The 5620 SAM documentation suite describes the 5620 SAM and the associated network management of its supported devices. Contact your Alcatel-Lucent support representative for information about specific network or facility considerations.

Table 1 lists the documents in the 5620 SAM customer documentation suite.

Table 1 5620 SAM customer documentation suite

Guide

Description

5620 SAM core documentation

5620 SAM Release Description

The 5620 SAM Release Description provides information about the new features associated with a 5620 SAM software release.

(1 of 4)

Preface

Guide

 

Description

5620

SAM Planning Guide

The 5620 SAM Planning Guide provides information about 5620 SAM scalability and recommended hardware configurations.

5620

SAM System

The 5620 SAM System Architecture Guide is intended for technology officers and network planners to increase their knowledge of the 5620 SAM software structure and components. It describes the system structure, software components, and interfaces of the 5620 SAM. In addition, 5620 SAM fault tolerance, security, and network management capabilities are discussed from an architectural perspective.

Architecture Guide

5620

SAM | 5650 CPAM

The 5620 SAM | 5650 CPAM Installation and Upgrade Guide provides OS considerations, configuration information, and procedures for the following:

Installation and Upgrade

Guide

installing, upgrading, and uninstalling 5620 SAM and 5650 CPAM software in standalone and redundant deployments

5620 SAM system migration to a different system

conversion from a standalone to a redundant 5620 SAM system

5620

SAM User Guide

The 5620 SAM User Guide provides information about using the 5620 SAM to manage the service-aware IP/MPLS network, including GUI basics, commissioning, service configuration, and policy management.

 

The 5620 SAM User Guide uses a task-based format. Each chapter contains:

a workflow that describes the steps for configuring and using the functions

detailed procedures that list the configurable parameters on the associated forms

5620

SAM management information specific to LTE network elements is covered in the

5620 SAM LTE ePC User Guide and 5620 SAM LTE RAN User Guide.

5620

SAM management information specific to 1830 PSS network elements is covered in

the 5620 SAM Optical User Guide.

5620

SAM Integration

The 5620 SAM Integration Guide provides procedures to allow the 5620 SAM to integrate with additional components.

Guide

5620

SAM Supervision

The 5620 SAM Supervision Module User Guide provides information about how to configure and use the web-based 5620 SAM Supervision Module for fault management and at-a-glance network element monitoring.

Module User Guide

5620

SAM Scripts and

The 5620 SAM Scripts and Templates Developer Guide provides information that allows users to develop, manage, and execute CLI-based or XML-based scripts or templates.

Templates Developer

Guide

The guide is intended for developers, skilled administrators, and operators who are expected to be familiar with the following:

CLI scripting, XML, and the Velocity engine

basic scripting or programming

5620 SAM functions

5620

SAM Parameter

The 5620 SAM Parameter Guide provides:

Guide

parameter descriptions that include value ranges and default values

parameter options and option descriptions

parameter and option dependencies

parameter mappings to the 5620 SAM-O XML equivalent property names

There are dynamic links between the procedures in the 5620 SAM User Guide and the parameter descriptions in the 5620 SAM Parameter Guide.

Parameters specific to LTE network elements are covered in the 5620 SAM LTE Parameter Reference.

Parameters specific to 1830 PSS network elements are covered in the 5620 SAM Optical Parameter Reference.

5620

SAM Statistics

The 5620 SAM Statistics Management Guide provides information about how to configure performance and accounting statistics collection and how to view counters using the 5620 SAM. Network examples are included.

Management Guide

(2 of 4)

Preface

Guide

Description

5620

SAM Maintenance

The 5620 SAM Maintenance Guide provides procedures for:

Guide

generating baseline information for 5620 SAM applications

performing daily, weekly, monthly, and as-required maintenance activities for 5620 SAM-managed networks

5620

SAM Troubleshooting

The 5620 SAM Troubleshooting Guide provides task-based procedures and user documentation to:

Guide

help resolve issues in the managed and management networks

identify the root cause and plan corrective action for:

alarm conditions on a network object or customer service

problems on customer services with no associated alarms

list problem scenarios, possible solutions, and tools to help check:

network management LANs

network management platforms and operating systems

5620 SAM client GUIs and client OSS applications

5620 SAM servers

5620 SAM databases

5620

SAM Alarm Reference

The 5620 SAM Alarm Reference provides a description of all alarms supported on the 5620 SAM, including LTE and optical alarms, the raising and clearing conditions of each alarm, and the remedial action to fix the problem. The reference is organized by network element type.

5620

SAM Glossary

The 5620 SAM Glossary defines terms and acronyms used in all of the 5620 SAM documentation, including 5620 SAM LTE documentation.

5620

SAM Network

The 5620 SAM Network Element Compatibility Guide provides release-specific information about the compatibility of managed devices in 5620 SAM releases. This document is updated regularly; always consult the latest version on OLCS as described in Documentation on the web.

Element Compatibility Guide

5620

SAM LTE documentation

5620

SAM LTE Release

The 5620 SAM LTE Release Description provides information about the LTE features associated with the release.

Description

5620

SAM LTE ePC User

The 5620 SAM LTE ePC User Guide describes how to discover, configure, and manage LTE ePC devices using the 5620 SAM. The guide is intended for LTE ePC network planners, administrators, and operators and is to be used in conjunction with other guides in the 5620 SAM documentation suite where management of ePC devices does not differ from other network elements.

Alcatel-Lucent recommends that you review the entire 5620 SAM LTE ePC User Guide before you attempt to use the 5620 SAM in your LTE network.

Guide

5620

SAM LTE RAN User

The 5620 SAM LTE RAN User Guide describes how to discover, configure, and manage the Evolved NodeB, or eNodeB, using the 5620 SAM. The guide is intended for LTE RAN network planners, administrators, and operators and is to be used in conjunction with other guides in the 5620 SAM documentation suite where management of RAN devices does not differ from other network elements.

Alcatel-Lucent recommends that you review the entire 5620 SAM LTE RAN User Guide before you attempt to use the 5620 SAM in your LTE network.

Guide

5620

SAM LTE Parameter

The 5620 SAM LTE Parameter Reference provides a list of all LTE ePC and LTE RAN parameters supported in the 5620 SAM.

Reference

5620

SAM-O documentation

5620

SAM XML OSS

The 5620 SAM XML OSS Interface Developer Guide provides information that allows you to:

Interface Developer Guide

use the 5620 SAM XML OSS interface to access network management information

learn about the information model associated with the managed network

develop OSS applications using the packaged methods, classes, data types, and objects necessary to manage 5620 SAM functions

(3 of 4)

Preface

Guide

Description

5620

SAM 3GPP OSS

The 5620 SAM 3GPP OSS Interface Developer Guide describes the components and architecture of the 3GPP OSS interface to the 5620 SAM. It includes procedures and samples to assist OSS application developers to use the 3GPP interface to manage LTE devices.

Interface Developer Guide

5620

SAM 3GPP OSS

The 5620 SAM 3GPP OSS Interface Compliance Statements document describes the compliance of the 5620 SAM 3GPP OSS interface with the 3GPP standard.

Interface Compliance

Statements

 

5620

SAM optical documentation

5620

SAM Optical User

The 5620 SAM Optical User Guide describes how to discover, configure, and manage optical devices using the 5620 SAM. The guide is intended for optical network planners, administrators, and operators and is to be used in conjunction with other guides in the 5620 SAM documentation suite where management of optical devices does not differ from other network elements.

Alcatel-Lucent recommends that you review the entire 5620 SAM Optical User Guide before you attempt to use the 5620 SAM in your network.

Guide

5620

SAM Optical

The 5620 SAM Optical Parameter Reference provides a list of all optical device parameters supported in the 5620 SAM.

Parameter Reference

5650

CPAM documentation

5650

CPAM User Guide

The 5650 CPAM User Guide describes how to capture, inspect, visualize, and troubleshoot IGP and BGP topologies using the 5650 CPAM.

7701

CPAA Hardware

The 7701 CPAA Hardware Revision 2 Setup and Software Installation Instructions describes the hardware setup and software installation for the 7701 CPAA Hardware Revision 1, the route analyzer component of the 5650 CPAM.

Revision 1 Setup and Software Installation Instructions

7701

CPAA Hardware

The 7701 CPAA Hardware Revision 2 Setup and Software Installation Instructions describes the hardware setup and software installation for the 7701 CPAA Hardware Revision 2, the route analyzer component of the 5650 CPAM.

Revision 2 Setup and Software Installation Instructions

(4 of 4)

Obtaining customer documentation

You can obtain 5620 SAM customer documentation:

from the product

on the web

On-product documentation

The 5620 SAM on-product customer documentation is delivered in HTML and PDF. Choose HelpUser Documentation from the 5620 SAM client GUI to open the help system in a web browser.

The help system opens to the User Documentation Index, which provides a summary of and links to all 5620 SAM customer documents.

Click on the Using the help system tab on the User Documentation Index page to find usage tips for navigating and searching within the on-product customer documentation.

You can return to the User Documentation Index at any time by clicking on the Home icon, shown in Figure 1.

Preface

Figure 1 Home icon

Preface Figure 1 Home icon Documentation on the web The 5620 SAM customer documentation is available

Documentation on the web

The 5620 SAM customer documentation is available for download in PDF format from the Alcatel-Lucent Customer Support Center:

http://www.alcatel-lucent.com/myaccess. If you are a new user and require access to this service, please contact your Alcatel-Lucent support representative.

In addition to the guides listed in Table 1, Release Notices and other documents not delivered on-product are posted to this site.

Working with PDFs

You can download PDFs of individual guides from the Alcatel-Lucent Customer Support Center, or you can choose to download a zip of all PDFs for a particular release.

You can use the Search function of Acrobat Reader (FileSearch) to find a term in a PDF of any 5620 SAM document. To refine your search, use appropriate search options (for example, search for whole words only or enable case-sensitive searching). You can also search for a term in multiple PDFs at once, provided that they are located in the same directory. For more information, see the Help for Acrobat Reader.

Cross-book hotlinks, for example, from a parameter name in the 5620 SAM User Guide to a description of that parameter in the 5620 SAM Parameter Guide, work only if both PDF files are in the same directory.

, work only if both PDF files are in the same directory. Note ó Users of

Note ó Users of Mozilla browsers may receive an error message when opening the PDF files in the 5620 SAM documentation suite. The offline storage and default cache values used by the browsers are the cause of the error message.

Alcatel-Lucent recommends changing the Mozilla Firefox offline storage or Mozilla 1.7 cache value to 100 Mbytes to eliminate the error message.

Documentation conventions

Table 2 lists the conventions that are used throughout the documentation.

Table 2 Documentation conventions

Convention

Description

Example

Key name

Press a keyboard key

Delete

Italics

Identifies a variable

hostname

Key+Key

Type the appropriate consecutive keystroke sequence

CTRL+G

(1 of 2)

Preface

Convention

Description

Example

KeyñKey

Type the appropriate simultaneous keystroke sequence

CTRLñG

*

An asterisk is a wildcard character, which means ìany characterî in a search argument.

log_file*.txt

Press the Return key

ó

An em dash indicates there is no information.

ó

Indicates that a cascading submenu results from selecting a menu item

PoliciesAlarm

Policies

(2 of 2)

Procedures with options or substeps

When there are options in a procedure, they are identified by letters. When there are substeps in a procedure, they are identified by Roman numerals.

Example of options in a procedure

At step 1, you can choose option a or b. At step 2, you must do what the step indicates.

1 This step offers two options. You must choose one of the following.

a This is one option.

b This is another option.

2 You must perform this step.

Example of substeps in a procedure

At step 1, you must perform a series of substeps within a step. At step 2, you must do what the step indicates.

1 This step has a series of substeps that you must perform to complete the step. You must perform the following substeps.

i This is the first substep.

ii This is the second substep.

iii This is the third substep.

2 You must perform this step.

Measurement conventions

Measurements in this document are expressed in metric units and follow the Système international d’unités (SI) standard for abbreviation of metric units. If imperial measurements are included, they appear in brackets following the metric unit.

Table 3 lists the measurement symbols used in this document.

Preface

Table 3 Bits and bytes conventions

Measurement

Symbol

bit

b

byte

byte

kilobits per second

kb/s

Important information

The following conventions are used to indicate important information:

Warning ó Warning indicates that the described activity or situation Warning ó Warning indicates that the desc may, or will, cause equipment damage or serious performance may, or will, cause equipment damage or serious performance problems.

Caution ó Caution indicates that the described activity or situation Caution ó Caution indicates that the de may, or will, cause service interruption. may, or will, cause service interruption.

Note ó Notes provide information that is, or may be, of special Note ó interest. interest.

Preface

Contents

Preface

ix

Prerequisites

ix

5620 SAM documentation suite

ix

Obtaining customer documentation

xii

On-product documentation

xii

Documentation on the web

xiii

Documentation conventions

xiii

Procedures with options or substeps

xiv

Measurement conventions

xiv

Important information

xv

5620 SAM 3GPP OSS interface

1 5620 SAM 3GPP OSS features and functions

ó

1-1

1.1

5620 SAM 3GPP OSS Release 10.0

1-2

2 Introduction

ó

2-1

2.1 5620 SAM 3GPP OSS interface overview

2-2

Before you begin

2-2

2.2 3GPP overview

2-3

2.3 About this guide

2-3

2.4 Supported devices and technologies

2-4

2.5 Open interfaces professional support

2-4

Contents

3 IRPs

ó

3-1

3.1 IRP overview

3-2

3.2 IRP framework and concepts

3-2

3.3 IRP components

3-3

3.4 5620 SAM 3GPP OSS interface solutions sets

3-3

3.5 3GPP OSS interface compliance statements overview

3-4

3.6 5620 SAM 3GPP OSS interface IRPS

3-5

Entry Point IRP

3-6

Fault Management/Alarm IRP

3-9

Basic CM IRP 3-13

Notification IRP

3-17

Communication Surveillance IRP 3-22

Kernel IRP

3-23

Generic IRP 3-24

4 Communicating with OSS clients

ó

4-1

4.1 Initial access

4-2

4.2 Event monitoring

4-2

Notification IRP initialization

4-2

Subscribing to event notifications

4-3

Procedure 4-1 To subscribe to and unsubscribe from event notifications for a CORBA 3GPP OSS client

4-3

Procedure 4-2 To subscribe to and unsubscribe from event notifications for a SOAP/XML 3GPP OSS client

4-4

Filtering

4-6

Connection monitoring

4-6

Error recovery

4-7

4.3 Security

4-7

User security

4-7

SSL security

4-8

Firewall support

4-8

Procedure 4-3 To configure a 3GPP OSS interface to operate through a firewall for a CORBA OSS client

4-9

4.4 Redundancy

4-10

4.5 3GPP OSS Interface administration 4-10

5 5620 SAM 3GPP OSS domains

ó

5-1

5.1 Fault management

5-2

5.2 Workflow to obtain an alarm list

5-2

5.3 Workflow to acknowledge an alarm list

5-2

5.4 Inventory management

5-3

Basic inventory

5-3

3GPP compliant inventory file generation and description

5-3

Automatic generation of inventory file

5-3

3GPP inventory file properties description

5-4

Inventory file attributes

5-4

Sample 3GPP inventory file

5-5

5.5 Workflow to obtain a list of NEs

5-8

Contents

Appendices

A. 5620 SAM-O 3GPP code samples

A-1

A.1

Code samples

A-2

Fault management code samples

A-2

Basic inventory management code samples

A-2

B. Standards compliance

B-1

B.1

Standards compliance

B-2

C. Troubleshooting

C-1

C.1

3GPP OSS troubleshooting overview

C-2

C.2

Diagnosing typical 3GPP installation problems on the 5620 SAM server

C-2

Typical installation problem

C-2

Procedure C-1 To update the cnbi.properties file in the 5620 SAM

C-2

Troubleshooting 3GPP OSS SSL communication problems

C-3

Procedure C-2 To verify the JMS status of the 3GPP OSS Interface

C-3

Verifying that messages are being received by the 3GPP OSS interface from the 5620 SAM

C-4

Firewall preventing OSS client access to the 3GPP OSS Interface using the CORBA solution set

C-4

Problems referencing the Entry Point IOR

C-4

Incorrect configuration of the System DN

C-4

Problems receiving alarms and events when SPAN is configured

C-5

C.3

Useful logs

C-5

Contents

5620 SAM 3GPP OSS interface

1 ó 5620 SAM 3GPP OSS features and functions

2 ó Introduction

3 ó IRPs

4 ó Communicating with OSS clients

5 ó 5620 SAM 3GPP OSS domains

1 ó

5620 SAM 3GPP OSS features and functions

1.1 5620 SAM 3GPP OSS Release 10.0

1-2

1 ó 5620 SAM 3GPP OSS features and functions

1.1 5620 SAM 3GPP OSS Release 10.0

Table 1-1 lists the features and functions added in 5620 SAM 3GPP OSS Release

10.0.

Table 1-1 5620 SAM 3GPP OSS Release 10.0 functionality

Feature or function

Description

Reference for more information

Release 6.0 R1 features

SOAP/XML solution set

The 5620 SAM 3GPP OSS now supports the SOAP/XML solution set.

See the

5620

SAM 3GPP OSS

Interface Developer

Guide and

5620

SAM 3GPP OSS

Interface

Compliance

Statements.

2 ó

Introduction

2.1 5620 SAM 3GPP OSS interface overview

2-2

2.2 3GPP overview

2.3 About this guide

2-3

2-3

2.4 Supported devices and technologies

2.5 Open interfaces professional support

2-4

2-4

2 ó Introduction

2.1 5620 SAM 3GPP OSS interface overview

The 3GPP OSS Interface is an API that provides a 3GPP-compliant layer of communication with a 5620 SAM-managed LTE network. See the 5620 SAM LTE ePC User Guide and 5620 SAM LTE RAN User Guide for more information about

5620 SAM-managed LTE network components.

OSS client applications that integrate with the 3GPP OSS interface can perform network management functions as defined by supported 3GPP specifications called IRPs. See Chapter 3 for more information about IRPs.

The supported 3GPP OSS interface network management functions include the following:

Inventory Management (IM) - retrieve 5620 SAM network management information specific to LTE managed devices.

Fault Management (FM) - retrieve event and alarm notifications from the 5620 SAM server primarily for LTE managed devices.

The 3GPP OSS interface provides two different 3GPP solutions sets (APIs) that implement the following transport protocols for communicating with OSS clients:

3GPP CORBA API

3GPP SOAP/XML API

The 3GPP OSS interface is included in the overall architecture of the 5620 SAM server as the 3GPP component of the 5620 SAM-O. Integration between the

5620

SAM and the 3GPP OSS interface happens at the 5620 SAM-O interface. The

5620

SAM-O is a 5620 SAM module that provides an XML interface to the

5620

SAM. See the 5620 SAM System Architecture Guide for more information

about 5620 SAM architecture.

Guide for more information about 5620 SAM architecture. Note 1 ó The 5620 SAM license key

Note 1 ó The 5620 SAM license key has to include the 5620 SAM-O module before an OSS can integrate with the 3GPP OSS interface. See the 5620 SAM User Guide for more information about 5620 SAM licensing.

Note 2 ó The 3GPP OSS interface has to be enabled during the 5620 SAM server installation before an OSS can communicate with the 5620 SAM. See the 5620 SAM | 5650 CPAM Installation and Upgrade Guide for more information.

Note 3 ó An OSS can communicate with the 5620 SAM using either the 5620 SAM XML OSS interface or the 3GPP OSS interface. See the 5620 SAM XML OSS Interface Developer Guide for more information about developing OSS applications using the SOAP XML/JMS API.

Before you begin

Developers who create OSS applications for the 3GPP OSS interface are expected to be familiar with the following:

CORBA architecture and framework or SOAP/XML and WSDL

3GPP specifications, IRP layers and components

2 ó Introduction

OSS interfaces

LTE managed devices

5620 SAM functionality

Alcatel-Lucent recommends that developers perform the following tasks prior to working in an OSS development environment:

Review the requirements for license key configuration and platform size considerations. See the 5620 SAM Planning Guide for more information.

Pre-configure the device that you want the 5620 SAM to manage. See the device documentation for more information.

Back up the 5620 SAM database. A database backup utility is available in the 5620 SAM client GUI and through a CLI. See the 5620 SAM User Guide for more information.

2.2 3GPP overview

The 3rd Generation Partnership Project (3GPP) is a collaboration between groups of telecommunications associations to provide their members with a stable environment to produce Technical Specifications and Technical Reports for a 3G Mobile System based on evolved GSM core networks and the radio access technologies that they support (such as UTRA, FDD, and TDD), as well as evolved radio access technologies (such as GPRS, EDGE, W-CDMA, and both LTE and LTE-Advanced).

The Technical Specification development work within 3GPP is accomplished by different Technical Specification Groups that report into the larger 3GPP Project Coordination Group. This work is stored in the 3GPP Specification Status database located on the 3GPP project’s website at http:\\www.3gpp.org.

The 3GPP OSS interface complies with the 3GPP specifications developed and maintained by the TSG SA WG5, which is the Telecom Management Working group that specifies the requirements, architecture, and solutions for the provisioning and management of the network (e.g. RAN, CN, IMS) and its services. See the 5620 SAM 3GPP OSS Interface Compliance Statements for more information on the standards compliance of this interface.

2.3 About this guide

The 5620 SAM 3GPP OSS Interface Developer Guide provides information to help OSS developers create applications that perform 5620 SAM-specific functions on an LTE network. It is part of the 5620 SAM LTE documentation set, which also includes the 5620 SAM 3GPP OSS Interface Compliance Statements.

This guide contains and overviews of the 3GPP OSS interface and IRPs, information about OSS domains and communicating with OSS clients, and 3GPP OSS code samples for both solution sets.

2 ó Introduction

2.4 Supported devices and technologies

The 5620 SAM 3GPP OSS interface supports the retrieval of data including receiving notifications for the following LTE NE types:

eNode B

9471 WMM

Caution ó When a device introduces a maintenance release, you Caution ó must ensure that your 5620 SAM software supports the new release before upgrading the must ensure that your 5620 SAM software supports the new release before upgrading the device. You may need to upgrade the 5620 SAM to support the new device release. See the 5620 SAM Network Element Compatibility Guide for more information

Note 1 ó The SOAP/XML variant of the 3GPP OSS interface does Note 1 ó not support receiving alarm notifications from LTE devices in the 5620 SAM network. not support receiving alarm notifications from LTE devices in the 5620 SAM network. See the Fault Management/Alarm IRP subsection for more information.

Note 2 ó The 5620 SAM functions and features vary for the supported devices. See the 5620 SAM LTE ePC User Guide or the 5620 SAM LTE RAN User Guide for variations in support or device-specific procedures for specific implementations. See the 5620 SAM Parameter Guide or the 5620 SAM LTE Parameter Reference for device-specific parameters, default parameter values, and parameter ranges.

The 5620 SAM 3GPP OSS interface uses the following technologies:

XML

SOAP

HTTP(S)

WSDL

Java

CORBA

JBoss

3GPP

See the 5620 SAM System Architecture Guide for more information about the standards compliance and versions of these technologies.

2.5 Open interfaces professional support

Alcatel-Lucent provides developer support for third-party application integration with the 5620 SAM 3GPP OSS interface. The Alcatel-Lucent OIPS portfolio provides OSS developers with network management integration solutions for the 5620 SAM and 5650 CPAM. OSS integration initiatives include project review, design consultation, development support, and training for integration projects.

2 ó Introduction

Key elements of each service offering:

Design consultation and high-level project reviews. Extensive software design consultation provides architectural review of a proposed design and guidance on whether the design methodology is suited to the proposed application given Alcatel-Lucent experience with the platform and interface.

Software development support and technical guidance.

Sample code that provide examples of configuration and management concepts, to facilitate rapid OSS intergration.

OSS product training that minimizes project down time and optimizes development efficiency.

OSS Product Certification support to ISVs identified as Connected Partners, involving extensive interoperability testing of OSS applications with the 5620 SAM and 5650 CPAM.

Alcatel-Lucent OIPS can customize the support content and contract length to meet the unique development requirements of service providers.

2 ó Introduction

3 ó

IRPs

3.1 IRP overview

3-2

3.2 IRP framework and concepts

3.3 IRP components

3-3

3-2

3.4 5620 SAM 3GPP OSS interface solutions sets

3-3

3.5 3GPP OSS interface compliance statements overview

3.6 5620 SAM 3GPP OSS interface IRPS

3-5

3-4

3 ó

IRPs

3.1 IRP overview

The 3GPP management interface concept called Integration Reference Point, or IRP, promotes the adoption of standardized management interfaces in telecommunication networks. The IRP concept and associated methodology use protocol- and technology-neutral modeling methods, and protocol-specific solution sets.

The 3GPP publishes IRP specifications for operations and notifications for telecommunication domains such as alarm, configuration, and performance management. Detailed IRP specifications are available on the 3GPP website at http:\\www.3gpp.org\specifications under the TSG SA WG5 for Telecom Management.

3.2 IRP framework and concepts

3GPP IRP specifications consist of the following three levels:

Requirements level—provides a conceptual and use-cases definition for a specific management interface aspect, and defines subsequent requirements for an IRP

Information Service level—provides the detailed IRP description that identifies the technology specification of an IRP

Solution Sets level—describes the low-level interoperability mechanisms of the APIs that the elements managers and network managers must confirm to, and defines the mapping of the IS definitions into one or more technology-specific solution set

There are also three categories of IRP specifications: Interface, NRM, and Data Definitions. These categories are partitioned into the three specification levels described above.

Figure 3-1 illustrates the approach for the level specifications combined with the categories.

3 ó

IRPs

Figure 3-1 IRP

Requirements/Use Cases Interface IRP’s NRM IRP’s Data Definition IRP’s Information Service Definitions (UML)
Requirements/Use Cases
Interface IRP’s
NRM IRP’s
Data Definition IRP’s
Information Service Definitions (UML)
Notification IRP
Generic NRM
Alarm IRP
CoreNW NRM
State Mgmt IRP
etc
BulkCM IRP
UMTS NRM’s
KernelCM IRP
CDMA NRM’s
BasicCM IRP
Inventory NRM
etc
etc
Solution Set Defenitions (CORBA, SOAP, XML, CMIP)
Solution Set Defenitions (other/future e.g. JAVA, SNMP)

3.3 IRP components

Relative stable over long period of time(other/future e.g. JAVA, SNMP) 3.3 IRP components Changes only with respect to addition and extentions

Changes only with respect to addition and extentions and extentions

Technologiestime Changes only with respect to addition and extentions Changes with new better 22884 The IRP

Changes with

new better

22884

The IRP specification describes the following main components:

IRP agent—encapsulates a well-defined subset of network or NE functions; it interacts with IRP managers using one or more IRPs

IRP manager—models a user of IRP agents and interacts with IRP agents through IRPS

The 5620 SAM server contains the IRP agent (which is the 3GPP OSS interface), and an OSS application is considered the IRP manager.

3.4 5620 SAM 3GPP OSS interface solutions sets

The 3GPP OSS interface includes both a CORBA and SOAP/XML solution set.

The CORBA solution set includes an ORB implementation (JacORB) and a Notification Service implementation (TAO). CORBA Interface Definition Language (IDL) provides a language-neutral way of specifying the classes, or interfaces, of the objects within the application. An interface consists of a set of named operations and operation parameters. The 3GPP CORBA IDLs are based on the 3GPP standards defined by the compliance statement for the supported IRPs.

The SOAP/XML solution set is implemented as a web service and deployed in JBoss. It uses a callback mechanism for sending and receiving SOAP/XML formatted messages. Web Services Description Language (WSDL), in combination with SOAP and XML Schema, provides web services in a standard format. The 3GPP OSS interface WSDL file is based on the 3GPP standards defined by the compliance statements for the supported IRPs.

The IDL and WSDL files that define the solution sets for the 3GPP OSS interface are located in the following directory on a 5620 SAM main server:

3 ó

IRPs

path/nms/integration/SAM_O/3GPP

where path is the 5620 SAM main server installation directory, typically

/opt/5620sam/server

Note ó A series of modifications were applied in order to make the Note ó schemas included in the SOAP/X ML solution set usable. See the 5620 SAM 3GPP schemas included in the SOAP/XML solution set usable. See the 5620 SAM 3GPP OSS Interface Compliance Statements for more information. The WSDL file shipped with the 5620 SAM would have these modifications applied.

3.5 3GPP OSS interface compliance statements overview

The 5620 SAM 3GPP OSS interface Compliance Statements include information about all the supported IRPs. Each IRP supported by an IRP agent includes a set of operations and notifications. The Compliance Statements define whether an interface’s operation and notification is mandatory or optional. It also includes the compliant versions for each of the 3GPP solution sets.

Note ó The Basic CM and Generic IRPs do not have notification Note ó interface definitions. interface definitions.

For example, Table 3-1 lists the interfaces that are defined for the Communication Surveillance, or CS, IRP.

Table 3-1 CS IRP compliance with 3GPP R8

Interface name

Method name

Support

CORBA R8

SOAP/XML R8

Qualifier

Compliant

Compliant

CSIRPOperations_1

getHeartbeatPeriod

Mandatory

Y

Y

triggerHeartbeat

Mandatory

N

N

CSIRPOperations_2

setHeartbeatPeriod

Optional

N

N

CSIRPNotifications

notifyHeartbeat

Mandatory

Y

N

The compliance statements also include the following details for each supported IRP:

References—provides the list of 3GPP Technical Specifications numbers for the IRPs requirements, Information Service, CORBA solution set, and SOAP/XML solution set

General—provides high-level general information on the IRP if required

3 ó

IRPs

Operations—provides the name of all the supported methods, including definitions, parameters, and exceptions for both the CORBA and SOAP/XML solution sets

Notifications—provides the name of all the supported notifications, including definitions, parameters, and exceptions for both the CORBA and SOAP/XML solution sets

See the 5620 SAM 3GPP OSS Interface Compliance Statements for more information.

3.6 5620 SAM 3GPP OSS interface IRPS

The 3GPP has defined a number of IRPs that map to telecommunications management domains in an LTE network. The 5620 SAM 3GPP OSS interface supports a subset of these IRPs that includes the following:

Entry Point IRP—allows OSS applications to discover the management system and IRPs

Notification IRP—allows OSS applications to subscribe to notifications and manage subscriptions

Fault Management/Alarm IRP—allows OSS applications to detect and manage alarms and faults

Communication Surveillance IRP—provides a communication heartbeat for monitoring OSS application communication with the network manager

Basic CM IRP—allows OSS applications to control and monitor NE configurations and network resources

Kernel IRP—provides OSS applications with a list of the version of all IRPs in the network and also defines notification on NEs for object creation, deletion, attribute value changes, state changes, and synchronization information

Generic IRP—provides OSS applications with IRP version, method and notification profile information for a specific IRP

Inventory Management IRP—provides OSS applications with a 3GPP compliant XML inventory file

By default, once the 5620 SAM server is started the IRPs will be initialized by the 3GPP OSS Interface and made available for OSS clients to access the SAM LTE network. See section 4.5 for more information about starting, stopping, and getting the status of the 3GPP OSS interface processes.

and getting the status of the 3GPP OSS interface processes. Note 1 ó Although the 3GPP

Note 1 ó Although the 3GPP OSS interface supports the IRPs described above, it may not support all interfaces and methods defined in the 3GPP standard specifications. See Appendix B for more information.

Note 2 ó The Alarm IRP is not supported for the SOAP/XML solution set.

3 ó

IRPs

Entry Point IRP

In order for OSS applications to connect to the 3GPP OSS interface, the OSS must have access to the list of supported IRPs. The Entry Point IRP provides a mechanism for the OSS clients to discover the managed systems and associated IRPs.

The Entry Point IRP allows an OSS application to do the following:

Discover IRP information that includes the DN, supported IRP versions, management scope, and the set of network resources in the managed system to which it has access.

Obtain the references of the IRPs for a specific IRP version using the DN of the IRP that supports the required IRP version. The OSS application can use the Entry Point IRP to tell the 3GPP OSS interface which references it does not use. The managed system may release the references, if it is designed to do so.

CORBA Entry Point IRP

OSS applications using the CORBA solution set are required to retrieve the IOR of the Entry Point IRP. The CORBA IOR provides the “contact detail” that the OSS application uses to communicate with a CORBA object in order to provide initial access to the IRPs of the 3GPP OSS interface. During initialization, the 3GPP OSS interface generates an IOR for the Entry Point IRP and stores it in the following file on a 5620 SAM main server:

$CNBI_HOME/ior/EPIRP.ior

where $CNBI_HOME is the location of the 3GPP OSS interface, typically

/opt/5620sam/server/nms/cnbi/home

This IOR file does not change and remains the same after system restarts.

Code 3-1 shows an example of IRP reference retrieval using the CORBA Entry Point IRP.

Code 3-1: CORBA Entry Point IRP reference retrieval example String iorDir = “$CNBI_HOME/ior directory”; String iorFile = iorDir + File.separator + "EPIRP.ior";

FileInputStream fis = new FileInputStream(iorFile); BufferedReader reader = new BufferedReader(new InputStreamReader(fis)); String ior = reader.readLine(); reader.close();

try

{

org.omg.CORBA.Object entryPointObj = orb.string_to_object(ior); entryPointIRP = EPIRPHelper.narrow(entryPointObj);

}

catch (Exception e)

{

e.printStackTrace();

}

3 ó

IRPs

SOAP/XML Entry Point IRP

OSS applications using the SOAP/XML solution set are required to retrieve the URL of the Entry Point IRP. During intialization, the 3GPP OSS interface deploys the Entry Point WSDL, generating an associated URL. This URL does not change after system re-starts.This URL should be distributed. The format of this URL is:

http://IP address:port/cnbi-3gppWS/EntryPointIRPImpl?wsdl

where

IP address is the IP address of the server where the 5620 SAM is installed

port is the port number of the Jboss web server, typically 8980

See the 5620 SAM Planning Guide for more information about setting ports.

Once an OSS client is provided with this URL, it can start interacting with the 3GPP OSS interface without further security enforcements.

Code 3-2 shows an example of IRP reference retrieval using the SOAP/XML Entry Point IRP.

Code 3-2: SOAP/XML Entry Point IRP reference retrieval example String samServerIpAddress = “<SAM IP address>”; int JBOSS_ADMIN_PORT = 8980; String CNBI_3GPPWS = “cnbi-3gppWS String irpName; String serviceName;

public static EntryPointIRPPortType getEntryPointProxy(String samServerIpAddress) throws Exception {

URL url = new URL(“http://” + samServerIpAddress + ‘:’ + JBOSS_ADMIN_PORT + ‘/’ + CNBI_3GPPWS + “/EntryPointIRPImpl?WSDL”);

EntryPointIRPService entryPointService = new EntryPointIRPService(url, new QName(

“http://www.3gpp.org/ftp/Specs/archive/32_series/32.367/EntryPointIR

PSystem”,

“EntryPointIRPService”));

return entryPointService.getEntryPointIRPPort();

getIRPOutline method

The Entry Point IRP includes the getIRPOutline method, which is used to obtain information about all supported IRPs.

Code 3-3 shows an example of CORBA getIRPOutline method invocation.

3 ó

IRPs

Code 3-3: CORBA getIRPOutline method invocation example

try

{

String irp_version = ""; SupportedIRPListHolder supported_irp_list = new SupportedIRPListHolder();

Result result = entryPointIRP.get_irp_outline(irp_version,supported_irp_list); SupportedIRP supportedIRP = supported_irp_list.value[0];

}

catch (Exception e)

{

e.printStackTrace();

}

Code 3-4 shows an example of SOAP/XML getIRPOutline method invocation.

Code 3-4: SOAP/XML getIRPOutline method invocation example

try { Holder<OperationStatusTwo> status = new Holder<OperationStatusTwo>(); Holder<SupportedIRPList> supportedIRPList = new

Holder(SupportedIRPList.(); getEntryPointProxy(getSamServerIpAddress()).getIRPOutline(version,su pportedIRPList, status); SupportedIRP supportedIRP =

supportedIRPList.value.getSupportedIRP().get(0);

for (IRPElement irpElement:

supportedIRP.getIRPList().getIRPElement()){ writer.printIn(irpElement.getRDN() + ‘\t’ + irpElement.getIRPVersionSet().getVersionNumber());

}

writer.printIn(“Operation Status:” + status.value.value());

} catch (GetIRPOutlineFault getIRPOutlineFault) { writer.printIn(“GetIRPOutlineFault caught: “ + getIRPOutlineFault.getFaultInfo());

}

Table 3-2 describes the supported IRP version information that should be returned when the getIRPOutline method is used for each 3GPP OSS solution set.

Table 3-2 Supported IRP version information returned by getIRPOutline method

rDN (R8)

CORBA R8

SOAP/XML R8

ERIRP = 1

{ ì32.363 V8.2î }

{ì32.367 V8.0î}

NotificationIRP = 1

{ ì32.303 V8.0î }

{ì32.307 V8.0î}

CSIRP = 1

{ ì32.353 V8.0î }

{ì32.357 V9.0î}

BasicCMIRP = 1

{ ì32.603 V8.1î }

{ì32.607 V8.1î}

KernalIRP = 1

{ ì32.663 V8.1î }

{ì32.667 V8.0î}

AlarmIRP = 1

{ ì32.111-3 V8.0î }

N/A

3 ó

IRPs

getIRPReference method

The Entry Point IRP includes the getIRPReference method, which is used to request a reference for a specific IRP.

Code 3-5 shows a generic example of method invocation for retrieving the reference for any IRP supported by the CORBA solution set.

Code 3-5: CORBA getIRPReference method invocation example

try

{

entryPointIRP.get_irp_reference(manager_identifier, system_dn, <IRP>Impl.NAME_TO_BIND, irp_reference); org.omg.CORBA.Object <IRP>Obj = orb.string_to_object(irp_reference.value);

<IRP> = <IRP_operation>Helper.narrow(<IRP>Obj);

}

catch (Exception e)

{

e.printStackTrace();

}

where

<IRP> is KernelIRP, HeartBeatIRP, NotificationIRP, BasicCM, or AlarmIRP

<IRP_operation> is _KernelCMIrpOperations, CSIRP, NotificationIRP, _BasicCmIrpOperations, or AlarmIRP

Code 3-6 shows a generic example of method invocation for retrieving the reference for any IRP supported by the SOAP/XML solution set.

Code 3-6: SOAP/XML getIRPReference method invocation example

try { getEntryPointProxy)getSamSeverIpAddress()).getIRPReference(managerId entifier, systemDN, rdn, iRPReference, status); writer.printIn(iRPReference.value + ‘/t’ +status.value.value()); } catch (GetIRPReferenceFault getIRPReferenceFault) { writer.printIn(“getIRPReferenceFault caught:

“ + getIRPReferenceFault.getFaultInfo());

}

where rdn is a SOAP/XML R8 value from Table 3-2.

Fault Management/Alarm IRP

An evaluation of NE and network health requires the detection of faults in the network and the subsequent forwarding of associated alarms to the element manager or network manager. Depending on the nature of a fault, there may be a change in the operational state of the affected logical or physical resources.

3 ó

IRPs

Alarm and state-change detection and notification are essential. A list of the current network alarms, operational state information, and the associated history data are required for further fault analysis. Additionally, test procedures can be used to obtain more detailed information, if required, and to verify an alarm or operational state to ensure correct NE operation and the proper use of resources.

See Code 3-5 for a generic code sample that can be used to gain access to the Fault Management/Alarm IRP for the CORBA solution set.

acknowledgeAlarms method

The Fault Management/Alarm IRP includes the acknowledgeAlarms method. The method updates the specified alarm in the following ways:

sets the Acknowledgement State to Acknowledged

adds the ackUserId and ackSystemId values as comments to the alarm

sets the Acknowledgement Time of the alarm to the current time

the Acknowledgement Time of the alarm to the current time Note 1 ó The method performs

Note 1 ó The method performs no verification of the provided ackUserId and ackSystemId values.

Note 2 ó A perceivedSeverity value in the request is ignored; an alarm is acknowledged based on the alarm ID only.

Code 3-7 shows an example of acknowledgeAlarms method invocation.

Code 3-7: acknowledgeAlarms method invocation example BadAcknowledgeAlarmInfoSeqHolder badackalarmholder = new BadAcknowledgeAlarmInfoSeqHolder(); StringOpt opt = new StringOpt(); opt.value("system_id"); AlarmInformationIdAndSev alarm = new AlarmInformationIdAndSev(); AlarmInformationIdAndSev alarm2 = new AlarmInformationIdAndSev();

ShortOpt op = new ShortOpt(); op.value((short) 1); alarm.alarm_id = "1"; alarm.perceived_severity = op; alarm2.alarm_id = "2"; alarm2.perceived_severity = op; try

{

alarmIRP.acknowledge_alarms(new AlarmInformationIdAndSev[] { alarm, alarm2 }, "user_id", opt, badackalarmholder); BadAcknowledgeAlarmInfo[] info = badackalarmholder.value;

}

catch (Exception e)

{

Log.error(this, "ERROR", e); fail(e.getMessage());

}

3 ó

IRPs

If an acknowledgeAlarms operation fails, the list of errors, which includes the alarm identifiers and error codes, is stored in the bad alarm information object. This object is defined as a CORBA holder, and has to be created and passed by reference to the method.

clearAlarms method

The Fault Management/Alarm IRP includes the clearAlarms method, which clears one or more alarm instances in an alarm list.

Note ó The method performs no verification of the provided Note ó clearUserId and clearSystemId values. clearUserId and clearSystemId values.

Code 3-8 shows an example of clearAlarms method invocation.

Code 3-8: clearAlarms method invocation example

BadAlarmInformationIdSeqHolder badclearalarmholder = new BadAlarmInformationIdSeqHolder(); StringOpt opt = new StringOpt(); opt.value("system_id"); ShortOpt op = new ShortOpt(); op.value((short) 1); try

{

alarmIRP.clear_alarms(new String[]{"1", "2"}, "user_id", opt, badclearalarmholder); BadAlarmInformationId[] info = badclearalarmholder.value;

}

catch (Exception e)

{

e.printStackTrace();

fail();

}

If a clearAlarms operation fails, the list of errors, which includes the alarm identifiers and error codes, is stored in the bad alarm information object. This object is defined as a CORBA holder, and has to be created and passed by reference to the method.

commentAlarms method

The Fault Management/Alarm IRP includes the commentAlarms method, which records one or more alarm information instances in an alarm list.

Note ó The method performs no verification of the provided Note ó commentUserId and comme ntSystemId values. commentUserId and commentSystemId values.

Code 3-9 shows an example of commentAlarms method invocation.

Code 3-9: comment_alarms method invocation example BadAlarmInformationIdSeqHolder badcommentalarmholder = new BadAlarmInformationIdSeqHolder();

3 ó

IRPs

StringOpt opt = new StringOpt(); opt.value("system_id"); ShortOpt op = new ShortOpt(); op.value((short) 1); try

{

alarmIRP.comment_alarms(new String[]{"1", "2"}, "user_id", opt, "alarm comment", badcommentalarmholder); BadAlarmInformationId[] info = badcommentalarmholder.value;

}

catch (Exception e)

{

e.printStackTrace();

fail();

}

If a commentAlarms operation fails, the list of errors, which includes the alarm identifiers and error codes, is stored in the bad alarm information object. This object is defined as a CORBA holder, and has to be created and passed by reference to the method.

getAlarmList method

The Fault Management/Alarm IRP includes the getAlarmList method, which returns the set of current alarms. The returned alarm list contains all alarms in the current alarm list. Depending on the network manager fault management configuration, this may include the following:

alarms that have a perceivedSeverity other than Cleared, and alarms that have a perceivedSeverity of Cleared but are not acknowledged

only alarms that have a perceivedSeverity other than Cleared

The alarm life cycle reported by the interface is provided by the network manager.

by the interfa ce is provided by the network manager. Note ó This operation is only

Note ó This operation is only supported in synchronous mode, which means that the data is returned using an iterator and not using a notification.

Code 3-10 shows an example of getAlarmList method invocation.

Code 3-10: getAlarmList method invocation example StringOpt filter = new StringOpt(); filter.value("$.filterable_data(h) == 1"); DNOpt base_object = new DNOpt(); base_object.value(base); BooleanHolder flag = new BooleanHolder(); AlarmInformationIteratorHolder iter = new AlarmInformationIteratorHolder(); alarmIRP.get_alarm_list(filter, base_object, flag, iter); AlarmInformationIterator iterator = iter.value; List<StructuredEvent> resultList = new ArrayList<StructuredEvent>(); EventBatchHolder alarm_informations = new EventBatchHolder(); while (iterator.next_alarm_informations((short) 10, alarm_informations))

3 ó

IRPs

{

resultList.addAll(Arrays.asList(alarm_informations.value));

}

resultList.addAll(Arrays.asList(alarm_informations.value));

An iterator object is created and passed as a parameter to the getAlarmList method. Alarm batches are retrieved using iterator calls to the next_alarm_informations method, which returns a Boolean value. If the value is true, batches are pending.

When the 5620 SAM main server becomes available after being unavailable for a time, the 3GPP OSS interface re-establishes a connection to the server. If the interface detects missed events, it sends a notifyAlarmListRebuilt notification to the OSS clients to inform them that the alarm list is again reliable. See chapter 4 for information about connection monitoring and redundancy.

getAlarmCount method

The Fault Management/Alarm IRP includes the getAlarmCount method, which retrieves a list of alarm counts, organized by severity, for alarms in raised, cleared, and acknowledged states.

Code 3-11 shows an example of getAlarmCount method invocation.

Code 3-11: getAlarmCount method invocation example StringOpt filter = new StringOpt(); IntHolder critical_count = new IntHolder(); IntHolder major_count = new IntHolder(); IntHolder minor_count = new IntHolder(); IntHolder warning_count = new IntHolder(); IntHolder indeterminate_count = new IntHolder(); IntHolder cleared_count = new IntHolder(); try

{

filter.value(""); alarmIRP.get_alarm_count(filter, critical_count, major_count, minor_count, warning_count, indeterminate_count, cleared_count);

}

catch (Exception e)

{

e.printStackTrace();

}

The counters are defined as CORBA holders, and are created and passed by reference. The counter values are retrievable after the method invocation.

Basic CM IRP

Configuration Management, or CM, provides the ability to ensure correct and effective network operation. Basic CM actions control and monitor the NE and network resource configurations, and can be initiated by an operator or by functions in an NE operations system.

The Basic CM IRP allows OSS clients to invoke methods that retrieve basic data about the 3GPP NEs in the network. This data can be associated with data from other functions, for example, alarm management.

3 ó

IRPs

The Basic CM IRP supports the following NE attributes:

Managed Element ID

User Label

Type

Managed By

User Defined State

Software Version

Location Name

Vendor Name

Supported NE Types

The 5620 SAM 3GPP device OSS interface supports the retrieval of data for the

following LTE devices:

eNodeB

9471 WMM

See

Code 3-5 for a generic code sample that can be used to gain access to the Basic

CM

IRP for the CORBA solution set.

See

Code 3-6 for a generic code sample that can be used to gain access to the Basic

CM

IRP for the SOAP/XML solution set.

getMOAttributes method

The

Basic CM IRP includes the goMOAttributes method, which returns the list of

NEs

and option supported attributes, or specific NE and optional attributes.

Code 3-12 shows an example of CORBA getMOAttributes and getContainment methods invocation.

Code 3-12: CORBA getMOAttributes and getContainment methods invocation example String base_object = ""; BasicCmInformationIterator cmIterator = null; ResultSetHolder batchHolder = new ResultSetHolder(); ResultContents result_contents = ResultContents.NAMES_AND_ATTRIBUTES; // remaining SearchControl fields are not supported SearchControl search_control = new SearchControl(ScopeType.BASE_ONLY, 0, "useless filter", result_contents); try

{

// empty base_object, NAMES_AND_ATTRS cmIterator = basicCMIRP.find_managed_objects(base_object, search_control, new String[]{}); boolean isDataPending = cmIterator.next_basic_cm_informations((short)10, batchHolder); Result[] result = batchHolder.value;

// given base_object, NAMES_AND_ATTRS base_object =

"SubNetwork=IPSubNetwork,ManagedElement=network:192.168.1.1";

cmIterator = basicCMIRP.find_managed_objects(base_object, search_control, new String[]{}); isDataPending = cmIterator.next_basic_cm_informations((short)1, batchHolder);

3 ó

IRPs

result = batchHolder.value;

// empty base_object, NAMES only base_object = ""; result_contents = ResultContents.NAMES; search_control = new SearchControl(ScopeType.BASE_ONLY, 0, "useless filter", result_contents); cmIterator = basicCMIRP.find_managed_objects(base_object, search_control, new String[]{}); isDataPending = cmIterator.next_basic_cm_informations((short)10, batchHolder); result = batchHolder.value; // multiple batches cmIterator = basicCMIRP.find_managed_objects(base_object, search_control, new String[]{}); isDataPending = cmIterator.next_basic_cm_informations((short)1, batchHolder); result = batchHolder.value; isDataPending = cmIterator.next_basic_cm_informations((short)1, batchHolder); result = batchHolder.value;

}

catch (Exception e)

{

Log.error(this, "testFindManagedObjects", "sw error during test execution", e);

}

Code 3-13 shows an example of SOAP/XML getMOAttributes method invocation.

Code 3-13: SOAP/XML getMOAttributes method invocation example private static final String BASE_OBJECT = “base_object”; List<String> mandatoryPropertiesNames = Arrays.asList(BASE_OBJECT); String MANAGED_ELEMENT_ID_ATTRIBUTE = “managedElementType”; String USERLABEL_ATTRIBUTE = “userLabel”; String MANAGED_ELEMENT_TYPE_ATTRIBUTE = “managedElementType”; String SW_VERSION_ATTRIBUTE = “swVersion”; String LOCATION_NAME_ATTRIBUTE = “locationName”; List<String> ATTRIBUTES_NAMES= Arrays.asList(MANAGED_ELEMENT_ID_ATTRIBUTE, USERLABEL_ATTRIBUTE, MANAGED_ELEMENT_TYPE_ATTRIBUTE, SW_VERSION_ATTRIBUTE, LOCATION_NAME_ATTRIBUTE);

-

-

-

-

for (Iterator<String> iterator = ATTRIBUTES_NAMES.iterator(); iterator.hasNext();) { writer.print(iterator.next()); if (iterator.hasNext()) { writer.print(‘\t’); } else { writer.print(‘\n’);

3 ó

IRPs

}

}

BasicCMIRP basicCmPort = getBasicCMIRPPort(properties,writer); Holder<MOSequenceType> moiListOut = new Holder<MOSequenceType>(); basicCmPort.getMOAttributes(““, baseObject, new Holder<String>()), moiListOut;

MOSequenceType getMOAttributesResult = moiListOut.value; Map<String, String> attributesMap; for (AnyMOType type : getMOAttributesResult.getMO()) { attributesmap = new HashMap<String, String>(); for (AttributeNameValueType attr :

type.getAttributeList().getAttributeList()) { String attName = attr.getName(); String attValue = ((JAXBElement) attr.getValue().getAny()).getValue().toString(); attributesMap.put(attName, attValue);

}

for (Iterator<String> iterator = ATTRIBUTES_NAMES.iterator(); iterator.hasNext();) {

String attValue = attributesMap.get(iterator.next()); writer.print(attValue); if (iterator.hasNext()) { writer.print(‘\t’); } else { writer.print(‘\n\);

}

}

}

}

getContainment method

The Basic CM IRP includes the getContainment method, which returns the list of NEs or a specific NE.

See Code 3-12 for a code sample that can be used to invoke the getContainment method for the CORBA solution set.

Code 3-14 shows an example of SOAP/XML getContainment method invocation.

Code 3-14: SOAP/XML getContainment method invocation example String BASE_OBJECT = ‘base_object”; List<String> mandatoryPropertiesNames = Arrays.asList(BASE_OBJECT);

public GetContainmentWSOnlineClient() { super(“GetContainmentIRP”, mandatoryPropertiesNames);

}

public void launchSpecificTest(Properties properties, PrintWriter writer) throws Exception {

String baseObject = properties.getProperty(BASE_OBJECT); GetContainment parameter = new GetContainment(); writer.printIn(“NE MO”); parameter.setQueryXpathExp(baseObject);

3 ó

IRPs

BasicCMIRP basicCmPort = getBasicCMIRPPort(properties, writer); GetContainmentResponse getContainmentResponse = basicCmPort.getContainment(parameter); List<String> results = getContainmentResponse.getTopContainerLoc();

for (String result : results) {

}

}

Notification IRP

NEs generate notifications about network events. Different kinds of events carry different kinds of information such as the following:

a new alarm, as specified in Alarm IRP: Information Service

an object creation, as specified in Basic CM IRP: Information Service

The Notification IRP defines an interface through which an IRP manager (OSS application) can subscribe to an IRP agent (3GPP OSS interface) for receiving a notification.

The 5620 SAM 3GPP OSS interface supports the following notification types:

alarm—forwarded when alarm events are received from the alarm feeder (specified in the Alarm IRP)

heartbeat—sent by the 3GPP OSS interface to each attached client (specified in the CS IRP)

kernel—sent when the 3GPP OSS interface host system notifies the interface about NE creation, deletion or modification (specified in the Kernel IRP)

See Code 3-5 for a generic code sample that can be used to gain access to the Notification IRP for the CORBA solution set.

See Code 3-6 for a generic code sample that can be used to gain access to the Notification IRP for the SOAP/XML solution set.

This Notification IRP includes the following methods:

Subscribe—creates a subscription for receiving notifications

Unsubscribe—cancels a subscription

getSubscriptionStatus—obtains the subscription status and informs the IRP agent about whether a subscription is required

changeSubscriptionFilter—replaces the current subscription filter

getSubscriptionIds—obtains the ID assigned by the Notification IRP to each valid subscription; a valid subscription is a subscription that is not unsubscribed or removed by the IRP agent

getNotificationCategories—obtains a list of the notification categories that the IRP agent supports

Subscribe method

The Notification IRP includes the Subscribe method, which creates a subscription for receiving notifications.

3 ó

IRPs

Code 3-15 shows an example of the CORBA Subscribe method invocation.

Code 3-15: CORBA Subscribe method invocation example

public static class SubscriberTest extends SequencePushConsumerPOA

{

}

UnsignedLongOpt time_tick = new UnsignedLongOpt();

time_tick.value(1440);

NotificationCategorySetOpt notification_categories = new NotificationCategorySetOpt(); notification_categories.value(new String[] {}); StringOpt filter = new StringOpt(); filter.value(""); SubscriberTest subscriber = new SubscriberTest(); org.omg.CORBA.Object subscriberReference = null; String subscriptionId = null; org.omg.PortableServer.POA rootpoa = org.omg.PortableServer.POAHelper.narrow(orb.resolve_initial_referenc es("RootPOA")); rootpoa.the_POAManager().activate(); subscriberReference = rootpoa.servant_to_reference(subscriber);

subscriptionId = orb.object_to_string(subscriberReference); notificationIRP.attach_push(manager_reference, time_tick, notification_categories, filter);

Code 3-15 shows an example of the SOAP/XML Subscribe method invocation.

Code 3-16: SOAP/XML Subscribe method invocation example public class EventSubscriber {

-

-

}

public void subscribe() throws Exception { writer.printIn(“Subscribing to notification category “ + notificationCategory + “ with filter -” + filter +

“- during “ + subscriptionDurationInt + “ minutes.”); endpoint = deployNotificationListenerWebService(managerReferenceId); subscriptionId = subscribeListenerToNotificationIrp(); String managerReferenceOutput = “ManagerReference: “ + managerReference; System.out.printIn(managerReferenceOutput); writer.printIn(managerReferenceOutput); String subscriptionIdOutput = “SubscriptionId: “ + subscriptionId; System.out.printIn(subscritpionsIdOutput); writer.printIn(subscriptionIdOutput); writer.flush();

}

3 ó

IRPs

UnSubscribe method

The Notification IRP includes the UnSubscribe method, which cancels a subscription.

Code 3-17 shows an example of the CORBA UnSubscribe method invocation. The input parameters are the CORBA reference of the subscription and the subscription ID, which are obtained by the subscription operator in the Subscribe method.

Code 3-17: CORBA UnSubscribe method invocation example SubscriptionIdOpt sub_id = new SubscriptionIdOpt(); sub_id.value(subscriptionId); notificationIRP.detach(manager_reference, sub_id);

Code 3-18 shows an example of the SOAP/XML UnSubscribe method invocation.

Code 3-18: SOAP/XML UnSubscribe method invocation example public void unsubscribe() throws Exception { Unsubscribe unsubscribeParameter = new Unsubscribe();

unsubscribeParameter.setManagerReference(managerReference);

unsubscribeParameter.setSubscriptionId(subscriptionId);

getNotificationIrpProxy().unsubscribe(unsubscribeParameter);

endpoint.stop();

System.out.printIn(“Disconnected.”);

getSubscriptionStatus method

The Notification IRP includes the getSubscriptionStatus method, which obtains subscription status and informs the IRP agent about whether a subscription is required.

the IRP agent about whether a subscription is required. Note ó An IRP manager must perfo

Note ó An IRP manager must perform a getSubscriptionStatus operation within the specified timeTick period. Otherwise, the IRP agent removes the subscription.

Code 3-19 shows an example of the CORBA getSubscriptionStatus method invocation. The input parameters are the CORBA reference of the subscription and the subscription ID, which are obtained by the subscription operator in the Subscribe method.

Code 3-19: CORBA getSubscriptionStatus method invocation example StringOptHolder filter_in_effect = new StringOptHolder(); SubscriptionStateOptHolder subscription_state = new SubscriptionStateOptHolder(); UnsignedLongOptHolder time_tick_holder = new UnsignedLongOptHolder();

String[] cats = notificationIRP.get_subscription_status(subscriptionId, filter_in_effect, subscription_state, time_tick_holder);

Code 3-20 shows an example of the SOAP/XML getSubscriptionStatus method invocation.

3 ó

IRPs

Code 3-20: SOAP/XML getSubscriptionStatus method invocation example public class GetSubscriptionStatus extends NotificationIrpTools {

}

public void launchSpecificTest(Properties properties, PrintWriter writer) throws Exception { Holder<NotificationCategorySetType> notificationCategories = new Holder<NotificationCategorySetType>(); Holder<String> filterInEffect = new Holder<String>(); HOlder<SubscriptionStateType> subscriptionState = new Holder<SubscriptionStateType>(); Holder<Long> timeTick = new Holder<Long>(); try { String subscriptionId = properties.getProperty(SUBSCRIPTION_ID); getNotificationIRPPort(properties, writer).getSubscriptionStatus(subscriptionId, notificationCategories, filterInEffect, subscriptionState, timeTick);

changeSubsciptionFilter method

The Notification IRP includes the changeSubscriptionFilter method, which replaces the current subscription filter.

Code 3-21 shows an example of the CORBA changeSubsciptionFilter method invocation. The input parameters are the CORBA reference of the subscription and the subscription ID, which are obtained by the subscription operator in the Subscribe method.

Code 3-21: CORBA changeSubsciptionFilter method invocation example String newFilter = "$.filterable_data(n) == 1"; notificationIRP.change_subscription_filter(subscriptionId, newFilter);

newFilter); Note ó Since the SOAP/XML solution set does not support

Note ó Since the SOAP/XML solution set does not support filtering, this method is not useful for that solution set.

getSubscriptionIds method

The Notification IRP includes the getSubscriptionIds method, which obtains the ID assigned by the Notification IRP to each valid subscription. A valid subscription is a subscription that is not unsubscribed or removed by the IRP agent.

Code 3-22 shows an example of the CORBA getSubscriptionIds method invocation. The input parameters are the CORBA reference of the subscription and the subscription ID, which are obtained by the subscription operator in the Subscribe method.

3 ó

IRPs

Code 3-22: CORBA getSubscriptionIds method invocation example String[] subscriptions = notificationIRP.get_subscription_ids(manager_reference);

Code 3-23 shows an example of the SOAP/XML getSubscriptionIds method invocation.

Code 3-23: SOAP/XML getSubscriptionIds method invocation example

try { GetSubscriptionIdsResponse.SubscriptionIdSet subscriptionIdSet =

getNotificationIRPPort(properties, writer).getSubscriptionIds(properties.getProperty(MANAGER_ REFERENCE)); for(String subscriptionId:

subscriptionIdSet.getSubscriptionId()) { writer.printIn(subscriptionId);

}

getNotificationCategories method

The Notification IRP includes the getNotificationCategories method, which obtains a list of the notification categories that the IRP agent supports (alarm, heartbeat, or kernel).