NMC/9153 OMC-R Q3 Interface: Q3 Protocol Conformance Statements

All rights reserved.
Passing on and copying of this

document, use and communication of its contents
not permitted without written authorization from Alcatel.
NMC/9153 OMC-R Q3 Interface:

Q3 Protocol Conformance Statements
Release B11
ED
01
NMC/9153 OMC-R Q3 Interface: Q3 Protocol Conformance Statements

RELEASED
9772m1re.doc
15/05/2009
3BK 09772 MAAA PBZZA
1/1
All rights reserved. Passing on and copying of this

SYSTEM FUNCTIONAL BLOCKS
TABLE OF CONTENTS
1.
2.
1.1
1.2
2.1
2.2
INTRODUCTION...............................................................................................8
Scope of the document .........................................................................8
Notations and conventions...................................................................8
OVERVIEW OF THE Q3 PROCOCOL STACK ................................................8
General description ...............................................................................8
Detailed description ............................................................................10
2.2.1
Lower layer infrastructure ............................................................10
2.2.1.1
2.2.1.2
2.2.1.3
2.2.2
2.3
3.
ED
2.3.1
2.3.2
2.3.3
2.2.2.1
2.2.2.2
2.2.2.3
CONS1 ............................................................................................................10
2.2.1.1.1
2.2.1.1.2
2.2.1.1.3
Physical and Data Link layers..................................................................... 10

Network layer.............................................................................................. 10
Transport layer ............................................................................................ 10
2.2.1.2.1
2.2.1.2.2
2.2.1.2.3

Network layer.............................................................................................. 11
Transport layer ............................................................................................ 11
2.2.1.3.1
2.2.1.3.2
2.2.1.3.3

Network layer.............................................................................................. 11
Transport layer ............................................................................................ 11
CLNS1 ............................................................................................................10
RFC10006/TCP/IP ..........................................................................................11
Upper layer infrastructure ............................................................12

Session layer ...................................................................................................12
Presentation layer............................................................................................12
Application layer.............................................................................................12
2.2.2.3.1
2.2.2.3.2
2.2.2.3.3
2.2.2.3.4
ACSE .......................................................................................................... 12
ROSE .......................................................................................................... 12
CMISE ........................................................................................................ 13
NMC/9153 OMC-R Q3 Interface-related Applications.............................. 13
Addressing ...........................................................................................13
Introduction..................................................................................13
AE-title values (AET) ...................................................................14
Presentation Service Access Point (PSAP) values......................14
2.3.3.1
2.3.3.2
2.3.3.3
2.3.3.4
Introduction.....................................................................................................14
PSEL, SSEL and TSEL values .......................................................................14
NSAP addresses ..............................................................................................14
SNPA addresses ..............................................................................................15
FURTHER CUSTOMIZATION OF ACSE SERVICES ....................................16

3.1
A-ASSOCIATE service.........................................................................16
3.1.1
A-ASSOCIATE parameters .........................................................16
3.1.2
Corresponding functional issues..................................................17
3.2
A-RELEASE service.............................................................................17
3.2.1
A-RELEASE parameters .............................................................17
3.2.2
3.3
A-ABORT and A-P-ABORT services...................................................17
01

RELEASED
9772m1re.doc
15/05/2009
1/26

3.4
4.
4.1
4.2
4.3
4.4
4.5
4.6
4.7
4.8
3.3.1
3.3.2
3.3.3
3.4.1
3.4.2
3.4.3
3.4.4
A-ABORT parameters..................................................................17
A-P-ABORT parameters ..............................................................18
Common Conformance statements ...................................................18
Application-context-name values .................................................18
AP-title values..............................................................................18
AE-qualifier values.......................................................................18
Parameters associated with the authentication FU......................18
FURTHER CUSTOMIZATION OF THE CMIS SERVICES .............................19

M-CREATE service...............................................................................19
M-DELETE service ...............................................................................19
M-GET service......................................................................................20
M-CANCEL-GET service......................................................................20
M-SET service ......................................................................................21
M-ACTION service ...............................................................................22
M-EVENT-REPORT service .................................................................23
Common Conformance Statements ...................................................23
4.8.1
The accessControl parameter .....................................................23
4.8.2
The currentTime parameter .........................................................23
4.8.3
The scope and filter parameters ..................................................23
4.8.4
The synchronization parameter ...................................................24
5.
SAFEGUARDING MECHANISMS..................................................................25
5.1
Event request sequence......................................................................25
5.2
Lock of an EFD.....................................................................................25
5.3
Deletion of an EFD ...............................................................................25
5.4
Association survey ..............................................................................25
5.5
Resynchronization...............................................................................25
6.
GLOSSARY....................................................................................................26
01
ED
ED
090515
DATE
01
First issue
CHANGE NOTE
O&M System
APPRAISAL AUTHORITY
TD/MRC/OMD Spec
ORIGINATOR

RELEASED
9772m1re.doc
15/05/2009
2/26

LIST OF FIGURES AND TABLES

Figure 1: The supported Q3 Protocol Stack ............................................................................9
Figure 2: Structure of a PSAP value......................................................................................14
Table 1: Conventions used in tables .......................................................................................8
Table 2: Addressing the 9153 OMC-R instance: PSEL, SSEL and TSEL values .................14
Table 3: Addressing the 9153 OMC-R instance: NSAP addresses.......................................15
Table 4: A-ASSOCIATE parameters .....................................................................................16
Table 5: A-RELEASE parameters .........................................................................................17
Table 6: A-ABORT parameters .............................................................................................18
Table 7: A-P-ABORT parameters ..........................................................................................18
Table 8: M-CREATE parameters...........................................................................................19
Table 9: M-DELETE parameters ...........................................................................................20
Table 10: M-GET parameters ................................................................................................20
Table 11: M-CANCEL-GET parameters ................................................................................20
Table 12: M-SET parameters ................................................................................................21
Table 13: M-ACTION parameters..........................................................................................22
Table 14: M-EVENT-REPORT parameters ...........................................................................23
HISTORY
Ed. 01
29/04/2009: Creation from 3BK 09772 LAAA PBZZA Ed.02 Released
General changes
B10 is replaced by B11
The RELATED DOCUMENTS part is updated for B11

15/05/2009: No technical changes.
REFERENCED DOCUMENTS
Alcatel-Lucent documents
[ANOIprofile]
Profile for the NMC/9153 OMC-R Q3 Interface

[ANOIgdmo]
NMC/9153 OMC-R Q3 Interface Information Model: GDMO Formal

Specification
[ANOIcs-gene]
NMC/9153 OMC-R Q3 Interface:

Statements
Overview
and
Conformance
Standards
[STD0005]
Internet Protocol
Recommendation Internet Architecture Board STD0005, September
1981.
[STD0007]
Transmission Control Protocol

Recommendation Internet Architecture Board STD0007, September
1981.
ED
01

RELEASED
9772m1re.doc
15/05/2009
3/26

[STD0035]
ISO Transport Service on top of the TCP

Recommendation Internet Architecture Board STD0035 Version 3, May
1987.
[ISO/IEC 7776]
Information technology - Telecommunications and information

exchange between systems - High-level data link control procedures
Description of the X.25 LAPB-compatible DTE data link procedures
Recommendation ISO/IEC 1776, 1995
[ISO/IEC 8073]

exchange between systems - Open Systems Interconnection
Protocol for providing the connection-mode transport service
[ISO/IEC 8208]
Information Technology - Data Communications - X.25 Packet layer

Protocol for Data Terminal Equipment
[ISO/IEC 8348-A2] Information technology - Open Systems Interconnection - Network

Service Definition
Recommendation ISO/IEC 8348, Addendum 2, Covering Network
Layer Addressing
[ISO/IEC 8473-2]
Information Technology - Protocol for providing the connectionlessmode network service, Part 2: Provision of the underlying service by an
ISO/IEC 8802 subnetwork.
Recommendation ISO/IEC 8473-2, 1996
[ISO/IEC 8802-2]

exchange between systems - Local and metropolitan area networks Specific requirements - Part 2: Logical Link Control
[ISO/IEC 8802-3]

exchange between systems - Local and metropolitan area networks Specific requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) - Access method and physical layer
specifications
[X.121]
Data Networks and Open System Communication - Public Data

networks - Network Aspects - International numbering plan for public
data networks
ITU-T Recommendation X.121, 1996
[X.208]
Information Processing Systems - Open Systems Interconnection Specification of Abstract Syntax Notation One (ASN.1)
CCITT Rec. X.208 (1988) | ISO/IEC 8824
[X.209]
Open System Interconnection - Model and Notation

Specification of Basic Encoding Rules for Abstract Syntax Notation
One (ASN.1)
ITU-T Recommendation X.209 (ISO/IEC 8825), 1988
ED
01

RELEASED
9772m1re.doc
15/05/2009
4/26

[X.213]
Information Technology- Open Systems Interconnection (OSI)

Network Service Definition
ITU-T Recommendation X.213 (ISO/IEC 8348), November 1995
[X.214]

Transport Service Definition
[X.215]

Session Service Definition
[X.216]

Presentation Service Definition
ITU-T Recommendation X.216 (ISO/IEC 8822), 1994
[X.217]

Service Definition for the Association Control Service Element
CCITT Recommendation X.217 (ISO/IEC 8649), 1996
[X.219]
Data Communication Networks- Open Systems Interconnection (OSI)

Remote operations: Model, notation and service definition
CCITT Recommendation X.219 (ISO/IEC 9072-1), 1988
[X.223]

Use of X.25 to provide the OSI Connection Mode Network Service for
ITU-T Applications
[X.224]

Protocol for providing the Connection-mode Transport Service
[X.225]

Connection-oriented Session Protocol: Protocol Specification
ITU-T Recommendation X.225 (ISO/IEC 8327-1), November 1995
[X.226]

Connection-oriented Presentation Protocol: Protocol Specification
ITU-T Recommendation X.226 (ISO/IEC 8823-1), 1994
[X.227]

Connection-oriented Protocol for the Association Control Service
Element: Protocol specification
[X.229]
Data Communication Networks- Open Systems Interconnection (OSI)

Remote operations: Protocol specification
[X.25]
Data Networks and Open System Communication - Public Data

Networks - Interfaces
Interface between Data Terminal Equipment (DTE) and Data Circuit-
ED
01

RELEASED
9772m1re.doc
15/05/2009
5/26

terminating Equipment (DCE) for terminals operating in the packet

mode and connected to public data networks by dedicated circuit
[X.233]

Protocol for providing the connectionless-mode network service:
Protocol specification
[X.410]
Information Technology- Data Networks and

Communication - Message Handling Systems (MHS)
Remote Operations and Reliable Transfer Server
CCITT Recommendation X.410, 1984
[X.650]
Information Technology- Open Systems Interconnection

Basic reference Model: Naming and Addressing
[X.710]
Data Communication Networks- Open Systems Interconnection (OSI)Management

Common Management Information Service Definition
CCITT Recommendation X.710 (ISO/IEC 9595), 1997
[X.711]
Data Communication Networks- Open Systems Interconnection (OSI)Management

Common Management Information Protocol Specification
CCITT Recommendation X.711 (ISO/IEC 9596), March 1991
[Q.811]
Specifications of Signalling System No. 7 - Q3 interface

Lower layer protocol profiles for the Q3 and X interfaces
ITU-T Recommendation Q.811, June 1997
[Q.812]
Specifications of Signalling System No. 7 - Q3 interface

Upper Layer protocol profiles for the Q3 and X interfaces
ITU-T Recommendation Q.812, June 1997
Open
System
Sun Microsystems Documents

The following documents, although requested of SUN, have not been obtained at
the date of this writing:
Conformance Statements for the RFC1006/TCP/IP profile and
PICS Proforma document for the Data Link layer of the CLNS1 profile (LLC1)
In what follows, these parts of the Q3 Protocol Stack are treated as if they were
fully compliant with the corresponding standard(s) with no noticeable options. The
reader shall contact directly SUN with respect to related Conformance Statements.
N.B.:
[PICS_CONS1_2]
Protocol Implementation Conformance Statement Proforma for Data

Link Layer (ISO 7776)
US GOSIP Version 2, March 1992
[PICS_CONS1_3]
Protocol Implementation Conformance Statement Proforma for Packet

Layer (ISO 8208)
US GOSIP Version 2, March 1992
[PICS_CLNS1_3]
Protocol Implementation Conformance Statement Proforma

Connectionless Network Layer Protocol (ISO 8473) - CLNS1 part
ED
01
for

RELEASED
9772m1re.doc
15/05/2009
6/26

US GOSIP, March 1992

[CS_IP]
Protocol Implementation Conformance Statement Proforma

Connectionless Network Layer Protocol (ISO 8473) - IP part
UK GOSIP PICS for ISO 8473, 1991
[PICS_CONS1_4]
Information processing systems - Open Systems Interconnection Connection-oriented transport protocol specification
Amendment 3: PICS proforma (ISO 8073)
Concerned Product: Solstice OSI version 9.0
N.B.:
Only the part dealing with the Transport class 2 shall be
considered in this document.
[PICS_CLNS1_4]
Protocol Implementation Conformance Statement

Transport Class 0 and 4 Protocols (ISO 8073)
US/UK GOSIP, March 1992
[PICS_CO_5]
Information technology - Open Systems Interconnection - Basic

connection-oriented session protocol specification
Part 2: Protocol Implementation Conformance Statements (PICS)
Proforma (ISO/IEC DIS 8327-2)
Concerned Product: Solstice OSI version 9.0.
[PICS_CO_6]
Protocol Implementation Conformance Statement (PICS) Proforma for

the Basic Connection-oriented Presentation protocol (ISO/IEC DIS
8823-2)
Date of statement: 07/09/1993.
Proforma
for
for
[PICS_CO_ACSE] Information technology - Open Systems Interconnection - Protocol

Specification for the Association Control Service Element
Part 2: Protocol Implementation Conformance Statements (PICS)
(ISO/IEC DIS 8650-2)
[PICS_CO_ROSE] Remote Operations Service Element
Protocol Implementation Conformance Statements (PICS) proforma
Concerned Product: Solstice CMIP version 9.0
[PICS_CO_CMIP]
Information technology - Open Systems Interconnection - Common

Management Information Protocol
Protocol Implementation Conformance Statements (PICS) proforma
Concerned Product: Solstice CMIP version 9.0
Alcatel COMET Documents
[EPIM-Guide]
COMET 6.5 Event Processing IM User Guide

3BP 21673 0012 TCZZA, Ed.01
RELATED DOCUMENTS
None.
ED
01

RELEASED
9772m1re.doc
15/05/2009
7/26

1. INTRODUCTION
1.1 Scope of the document
This document defines the Conformance Statements for the Q3 Protocol used by the
NMC/9153 OMC-R Q3 interface.
In particular, it defines:
The structure of the Q3 Protocol Stack
Peculiarities with respect to standards and implementation options for the different
layers of the Q3 Protocol Stack
N.B.:
Given that, for the NMC/9153 OMC-R Q3 Interface, the different layers of
the Q3 Protocol Stack actually rely on third party products, this part is
limited to important noticeable issues. For a complete specification of
the corresponding Conformance Statements, the reader is referred to
related documents (PICS Proforma and administration documents) of
these third party products which are to be considered as the reference.
Additional related functional issues.
1.2 Notations and conventions

The following conventions are used in the tables below:
CONVENTION
M
(=)
U
C
bold characters
name
SEMANTICS
The associated item is mandatory.
The value of the associated item is equal to the value of the one in the
column to the left.
For example, it can be used to indicate that the value of a CMIS
parameter in a R/C primitive is equal to the one in the R/I primitive.
The use of the associated item is a service-user option.
The associated item is not present in the interaction described by the
primitive concerned.
The associated item is conditional.
When used in a table, bold characters highlight noticeable peculiarities
with respect to the corresponding standard(s).
In the first column of a table whose entry corresponds to an item that
is a list, 'name' denotes a sub-field of this item. This is used to
describe, when the item is present, whether the sub-field 'name'
may/should be present.
Light grey is used to highlight items that are conditionally present.
Dark grey is used to highlight items that are never present.
Table 1: Conventions used in tables
2. OVERVIEW OF THE Q3 PROCOCOL STACK

2.1 General description
The supported Q3 protocol stack is as follows:
ED
01

RELEASED
9772m1re.doc
15/05/2009
8/26

NMC/9153 OMC-R Q3 Interface-related Applications

(7)
Application
CMISE
([X.710],[X.711])
ACSE
([X.217],[X.227])
Upper
Layers
ROSE
([X.219],[X.229])
([Q.812])
Lower
layers
([Q.811])
(6)
Presentation
OSI Presentation Layer

([X.209],[X.216],[X.226])
(5)
Session
OSI Session Layer

([X.215],[X.225])
(4)
Transport
(3)
(2)
(1)
Network
Data Link
Physical
Lower layer protocol profiles:
Transport over
CONS
([ISO/IEC 8073],
[X.214],[X.224])
Transport over
CLNS
([ISO/IEC 8073],
[X.214],[X.224])
RFC1006
X.25 PLP
CLNP/CLNS
([X.213],[X.233])
([ISO/IEC 8208],
[X.213],[X.223])
[ISO/IEC 8473-2]
X.25 LAPB
[ISO/IEC 8802-2]
LLC (Type 1)
([ISO/IEC 7776],
[X.25])
[ISO/IEC 8802-3]
MAC CSMA/CD
See [Q.811]
Not specified
Not
specified
CONS1
CLNS1
RFC1006/
TCP/IP
([STD0035])
TCP
([STD0007])
IP
([STD0005])
Not
specified
Legend:
The corresponding layer/service element is supported through the following third
party product:
Sun Microsystems products:

Solstice X.25 version 9.2
Solstice OSI version 9.0

Sun Solaris operation version 5.8
Solstice CMIP version 9.0
Figure 1: The supported Q3 Protocol Stack
The different layers are detailed in the following sub-sections.
ED
01

RELEASED
9772m1re.doc
15/05/2009
9/26

2.2 Detailed description

2.2.1 Lower layer infrastructure
The following lower layer protocol profiles defined in [Q.811] are supported:
CONS1:
A connection-mode packet interface using X.25
CLNS1:
A connectionless-mode interface using [ISO/IEC 8802-2] type LANs
using Carrier Sense Multiple Access with Collision Detection
(CSMA/CD)
RFC1006/TCP/IP: OSI Transport class 0 over Internet TCP.
2.2.1.1 CONS1
2.2.1.1.1 Physical and Data Link layers
For the CONS1 profile, the two lower layers are supported by the following third party
product: Solstice X.25 version 9.2.
For these layers,
This product complies with the CONS1 profile of [Q.811]. In particular, the Data Link
Layer conforms to X.25 LAPB as defined in Rec. [X.25] and [ISO/IEC 7776].
The applicable PICS Proforma document is [PICS_CONS1_2].
2.2.1.1.2 Network layer

For the CONS1 profile, the Network layer is supported by the following third party product:
Solstice X.25 version 9.2.
For this layer,
This product complies with the CONS1 profile of [Q.811]. It conforms to X25 Packet
Layer Protocol (PLP) as defined in Rec. [X.25] and [ISO/IEC 8208].
2.2.1.1.3 Transport layer

For the CONS1 profile, the Transport layer is supported by the following third party product:
Solstice OSI version 9.0.
For this layer,
This product complies with Rec. [Q.811], [X.214], [X.224] and [ISO/IEC 8073].
2.2.1.2 CLNS1
For the CLNS1 profile, the two lower layers are supported by the following third party
product: Sun Solaris operation version 5.8.
For these layers,
This product complies with the CLNS1 profile of [Q.811]. In particular, the Data Link
Layer conforms to [ISO/IEC 8802-2] LLC and [ISO/IEC 8802-3] MAC CSMA/CD.
ED
01

RELEASED
9772m1re.doc
15/05/2009
10/26

Concerning the applicable PICS Proforma document, see the N.B. of the
REFERENCED DOCUMENTS part.

For the CLNS1 profile, the Network layer is supported by the following third party product:
For this layer,
This product complies with the CLNS1 profile of [Q.811]. It notably conforms Rec.
[X.213], [X.233] and [ISO/IEC 8473-2].
The applicable PICS Proforma document is [PICS_CLNS1_3].

For the CLNS1 profile, the Transport layer is supported by the following third party product:
For this layer,
This product conforms to Rec. [Q.811], [X.214], [X.224] and [ISO/IEC 8073]. In
particular, the transport class is class 4.
The applicable PICS Proforma document is [PICS_CLNS1_4].
2.2.1.3 RFC10006/TCP/IP
For the RFC10006/TCP/IP profile, the two lower layers are supported by the following third
party product: Sun Solaris operation version 5.8.

For the RFC10006/TCP/IP profile, the Network layer is supported by the following third party
product: Sun Solaris operation version 5.8.
For this layer,
This product conforms to Rec. [Q.811] and [STD0005].
Concerning the applicable Conformance Statements, see the N.B. of the


For the RFC10006/TCP/IP profile, the Transport layer is splitted into:
The link with the IP network layer (TCP) supported by the following third party product:
Sun Solaris operation version 5.8.
For this link,

The link with the OSI session layer (RFC10006) supported by the following third party
product: Solstice OSI version 9.0.
For this link,
ED
01

RELEASED
9772m1re.doc
15/05/2009
11/26


The (implied) transport class is the transport class 0 (see [Q.811]).
N.B.:
2.2.2 Upper layer infrastructure

Only the upper layer protocol profile for Interactive Class services defined in [Q.812] is
relevant for the NMC/9153 OMC-R Q3 Interface.
2.2.2.1 Session layer

The session layer is supported by the following third party product: Solstice OSI version
9.0.Only the connection-oriented session protocol is supported.
For this layer,
This product conforms to Rec. [Q.812], [X.215] and [X.225].
The applicable PICS Proforma document is [PICS_CO_5]. In particular, Version 2 of the

Session connection-oriented protocol is supported.
2.2.2.2 Presentation layer

The presentation layer is supported by the following third party product: Solstice OSI version
9.0. Only the connection-oriented presentation protocol is supported.
For this layer,
This product conforms to Rec. [Q.812], [X.216] and [X.226]. In particular, the transfer
syntax is defined by the Basic Encoding Rules (BER) defined in Rec. [X.209] and
identified by the OBJECT IDENTIFIER value defined as:
{ joint-iso-itu-t(2) asn1(1) basic-encoding(1) }
N.B.:
This is the only transfer syntax used (i.e. it applies also to ACSE and CMIP).
The applicable PICS Proforma document is [PICS_CO_6]. In particular, Version 1 of the

Presentation connection-oriented protocol is supported.
2.2.2.3 Application layer

2.2.2.3.1 ACSE
ACSE is supported by the following third party product: Solstice OSI version 9.0. Only the
connection-oriented ACSE protocol is supported.
For this service element,
This product conforms to Rec. [Q.812], [X.217] and [X.227]. In particular, the ACSE
abstract syntax name is identified by the OBJECT IDENTIFIER value defined as:
{ joint-iso-itu-t(2) association-control(2) abstract-syntax(1) apdus(0) version1(1) }
The applicable PICS Proforma document is [PICS_CO_ACSE]. In particular,
version1 of the ACSE connection-oriented protocol is supported;
the normal and [X.410] modes of operation for the ACSE connection-oriented
protocol are supported by the third party product. However, for the NMC/9153
OMC-R Q3 interface, it is recommended to use only the normal mode.
See also chapter 2.3.1.
2.2.2.3.2 ROSE
ROSE is supported by the following third party product: Solstice CMIP version 9.0.
ED
01

RELEASED
9772m1re.doc
15/05/2009
12/26

This product conforms to Rec. [Q.812], [X.219] and [X.229].
The applicable PICS Proforma document is [PICS_CO_ROSE].
2.2.2.3.3 CMISE
CMISE is supported by the following third party product: Solstice CMIP version 9.0.
This product conforms to Rec. [Q.812], [X.710] and [X.711]. In particular, the CMISE
abstract syntax name is identified by the OBJECT IDENTIFIER value defined as:
{ joint-iso-ccitt(2) ms(9) cmip(1) abstract-syntax(4) }
The applicable PICS Proforma document is [PICS_CO_CMIP]. In particular:
Version 2 of the CMIP protocol is supported.
The functional units that are supported in addition to the kernel functional unit are
the following:
Multiple object selection
Filter
Multiple reply
Cancel get
In other words, the Extended service functional unit is not supported.
See also chapter 4.
2.2.2.3.4 NMC/9153 OMC-R Q3 Interface-related Applications

The NMC/9153 OMC-R Q3 Interface is supported:
For the "ANOI":anoiPlmnNetwork MOI and all MOIs named under it, via a dedicated
Mediation Device developped by Alcatel.
For the "X.721":system MOI and all the MOIs named under it, via the EFD and Log
facilities offered by COMET 6.5 Event Processing IM (EPIM).
The Conformance Statements specific to this layer are specified in [ANOIcs-gene].
2.3 Addressing
2.3.1 Introduction
For the NMC/9153 OMC-R Q3 interface, the following application entities can be addressed:
The 9153 OMC-R instance

For a given Q.811 profile, the corresponding address (actually the NSAP part of it) is
only dependent on the address (for that profile) of the workstation on which the 9153
OMC-R instance is installed (see section 2.3.3.3).
NMCs among which:
One primary NMC (mandatory)
A number (possibly equal to 0) of secondary NMCs.

The corresponding addresses are customer dependent. These addresses together with
the associated type of NMC (i.e. primary or secondary) are defined at the installation of
the 9153 OMC-R instance (from a NMC viewpoint).
What follows only deals with noticeable addressing aspect. For more information, refer to
the Administration Guide of Solstice CMIP version 9.0.
ED
01

RELEASED
9772m1re.doc
15/05/2009
13/26

2.3.2 AE-title values (AET)

For the Application layer, addressing information is supplied through AE-title values. In
accordance with [X.650], these AE-title values are constructed from AP-title and AE-qualifier
values.
Conformance Statements for these values are specified in sections 3.4.2 and 3.4.3
respectively.
2.3.3 Presentation Service Access Point (PSAP) values

2.3.3.1 Introduction
In accordance with [X.650], each AE-title value is bound to a single presentation address
that identifies the associated set of PSAPs.
A PSAP value can be divided into the following parts:
NSAP
TSEL
SSEL
PSEL
TSAP
SSAP
PSAP
Figure 2: Structure of a PSAP value
2.3.3.2 PSEL, SSEL and TSEL values

The maximum length that can be configured on Solstice OSI version 9.0 for the
Presentation, Session and Transport selector values is:
4 octets for PSEL
16 octets for SSEL
32 octets for TSEL.

The values of these selectors for addressing the 9153 OMC-R instance are as follows:
Selector
PSEL
SSEL
TSEL
Value
q3
Prs
CMIP
Table 2: Addressing the 9153 OMC-R instance: PSEL, SSEL and TSEL values
2.3.3.3 NSAP addresses

The NSAP addresses used by Solstice OSI version 9.0 conform to [ISO/IEC 8348-A2] and
Annex A of [X.213]. A NSAP address can be a maximum of 20 bytes in length.
The value of the NSAP addresses for addressing the 9153 OMC-R instance are as follows:
ED
01

RELEASED
9772m1re.doc
15/05/2009
14/26

[Q.811] profile
CONS1
NSAP address
The X.25 address of the workstation on which the 9153
OMC-R instance is installed
The MAC layer address of the workstation on which the
9153 OMC-R instance is installed
0x540072872203 followed by the IP address of the
workstation on which the 9153 OMC-R instance is installed.
For example, if this IP address is 15.5.25.225, the NSAP
address will be 0x540072872203015005025225.
CLNS1
RFC1006/TCP/IP
Table 3: Addressing the 9153 OMC-R instance: NSAP addresses
2.3.3.4 SNPA addresses

Solstice OSI version 9.0 also requires to supply a Subnetwork Point of Attachment (SNPA)
to identify a unique point at which the subnetwork is connected to the NSAP.
Actually, this information can be deduced from the NSAP address, except for the CONS1
profile. In that case, the SNPA address needs to be supplied when configuring Solstice X.25
version 9.2 (see section 2.2.1.1.1). This address is the [X.121] address (in hexadecimal) of
the workstation on which the 9153 OMC-R instance is installed (up to 15 digits).
ED
01

RELEASED
9772m1re.doc
15/05/2009
15/26

3. FURTHER CUSTOMIZATION OF ACSE SERVICES

3.1 A-ASSOCIATE service
3.1.1 A-ASSOCIATE parameters
PARAMETER NAME
application-contextname
called-AP-title
called-AE-qualifier
called-AP-invocationidentifier
called-AE-invocationidentifier
calling-AP-title
calling-AE-qualifier
calling-AP-invocationidentifier
calling-AE-invocationidentifier
result
result-source-diagnostic
responding-AP-title
responding-AE-qualifier
responding-APinvocation-identifier
responding-AEinvocation-identifier
sender-acserequirements
responder-acserequirements
mechanism-name
calling-authenticationvalue
respondingauthentication-value
application-contextname-list
implementationinformation
user-information
COMMENT
See section 3.4.1.
Req
Ind
Rsp
Cnf
M(=)
U
U
-
C(=)
C(=)
-
U
U
-
C(=)
C(=)
-
M
U
U
-
M
M
C(=)
C(=)
-
C(=)
See section 3.4.4.

See section 3.4.4.
See section 3.4.4.
C(=)
C(=)
See section 3.4.2.

See section 3.4.3.
It is recommended not to include
this parameter in the request.
See section 3.4.2.
See section 3.4.3.
See section 3.4.2.
See section 3.4.3.
This parameter is not included in
the response.
the response.
This parameter is always included

in the response.
Table 4: A-ASSOCIATE parameters
ED
01

RELEASED
9772m1re.doc
15/05/2009
16/26

3.1.2 Corresponding functional issues

An association between the 9153 OMC-R and a NMC is created:
By the 9153 OMC-R when it needs to forward a notification to that NMC and no
association with that NMC has yet been opened.
The 9153 OMC-R does not open two associations with the same called AET at the
same time.
After the 9153 OMC-R has forwarded an association request in connection-oriented
mode towards a NMC, the association will not be established in case:
It receives a negative acknowledgement (A-ASSOCIATE-cnf with a result

parameter indicating 'rejected (transient)' or 'rejected (permanent)',
Or it receives an abort indication (A-ABORT-ind or A-P-BORT-ind),
Or in case of an absence of acknowledgement.
By a NMC when it needs to forward commands (CMIS operations) and no association

with the 9153 OMC-R has yet been opened.
The 9153 OMC-R may use an association created by a NMC to forward its notifications to
that NMC. A NMC may use an association created by the 9153 OMC-R with that NMC to
send its CMISE operation requests and to wait for the potentially associated confirmations.
3.2 A-RELEASE service

3.2.1 A-RELEASE parameters
PARAMETER NAME
reason
user-information
Req
Ind
Rsp
Cnf
U
U
C(=)
C(=)
U
-
C=
-
COMMENT
the response.
Table 5: A-RELEASE parameters

An association created by the 9153 OMC-R is normally released by the 9153 OMC-R when,
during a predetermined time, no traffic occurs on it.
On the other hand, for an association created by a NMC, it is that NMC's responsibility to
release this association. The 9153 OMC-R confirms positively the corresponding ARELEASE indication primitive if no confirmed operation is being processed.
3.3 A-ABORT and A-P-ABORT services

3.3.1 A-ABORT parameters
PARAMETER NAME
abort-source
abort-diagnostic
user-information
ED
01
Req
Ind
U
U
M
C(=)
C(=)
COMMENT

RELEASED
9772m1re.doc
15/05/2009
17/26

Table 6: A-ABORT parameters
3.3.2 A-P-ABORT parameters

PARAMETER NAME
provider-reason
Ind
COMMENT
C
Table 7: A-P-ABORT parameters

Violations of the rules of the protocols used are intercepted by the 9153 OMC-R and result
in the association being aborted or not being created.
3.4 Common Conformance statements

3.4.1 Application-context-name values
The value of the application-context-name parameter in a response is the OID value defined
as:
{joint-iso-ccitt(2) ms(9) smo(0) applicationContext(0) systems-management(2)}
3.4.2 AP-title values

The alternative of AP-title (see [X.217]) that is recommended is AP-title-form2 defined as:
AP-title-form2 ::= OBJECT IDENTIFIER
If, in a request, AP-title-form1 is used, the request might be rejected.
3.4.3 AE-qualifier values

The alternative of AE-qualifier (see [X.217]) that is recommended is AE-qualifier-form2
defined as:
AE-qualifier-form2 ::= INTEGER
3.4.4 Parameters associated with the authentication FU

Such parameters shall not be present in the request since the authentication functional unit
is not supported (see section 2.2.2.3.1).
ED
01

RELEASED
9772m1re.doc
15/05/2009
18/26

4. FURTHER CUSTOMIZATION OF THE CMIS SERVICES

4.1 M-CREATE service
PARAMETER NAME
invokeID
managedObjectClass
managedObjectInstance
superiorObjectInstance
accessControl
referenceObjectInstance
R/I
M
M
U
U
U
U
R/C
M(=)
U
C
-
attributeList
attributeId
attributeValue
currentTime
Create Error
M
M
-
M
M
U
C
COMMENTS
See section 4.8.1.

If this parameter is specified, the attribute
values are copied from the supplied instance,
then possibly replaced by the ones specified in
the Attribute List parameter.
In a R/I primitive, this list includes one item per
attribute of the MOI that shall be assigned a
given value.
The set of attributes that shall or may have a
corresponding item in this list is defined in
[ANOIcs-gene].
See, in addition (a) below.
In a R/C primitive, this list shall include one item
per attribute of the MOI that is either GET or
GET-REPLACE, except in a negative
confirmation, in which case each of these items
may or not be present.
See section 4.8.2.
Table 8: M-CREATE parameters

(a) The following holds concerning the Attribute List parameter:
If a non modifiable attribute is specified (e.g., operationalState)
if the specified value is the default one, this is accepted,
otherwise an 'invalidAttributeValue' error is returned.
If a non applicable nameBinding is specified, an 'invalidAttributeValue' error is

returned.
If no naming attribute is specified for an object that doesn't support automatic

instance naming and if no managedObjectInstance parameter is specified, then a
'missingAttributeValue' error response is returned.
4.2 M-DELETE service

PARAMETER NAME
invokeID
linked-ID
baseManagedObjectClass
baseManagedObjectInstan
ED
01
R/I
M
M
M
R/C
M
C
-
COMMENTS

RELEASED
9772m1re.doc
15/05/2009
19/26

PARAMETER NAME
ce
accessControl
synchronization
scope
filter
managedObjectClass
currentTime
Delete Error
R/I
R/C
COMMENTS
U
U
U
U
-
C
C
U
C
See section 4.8.1.

See section 4.8.4.
See section 4.8.3.
See section 4.8.3.
See section 4.8.2.
Table 9: M-DELETE parameters
4.3 M-GET service

PARAMETER NAME
invokeID
linked-ID
ce
accessControl
synchronization
scope
filter
attributeIdList
managedObjectClass
currentTime
attributeList
attributeId
attributeValue
Get Errors
R/I
M
M
M
R/C
M
C
-
U
U
U
U
U
-
C
C
U
C
M
M
C
COMMENTS
See section 4.8.1.

See section 4.8.4.
See section 4.8.3.
See section 4.8.3.
See [ANOIcs-gene].
See section 4.8.2.
This list includes one item:
per attribute identified in the attributeIdList

parameter when the latter is not empty;
per attribute of the MOI that is either GET

or GET-REPLACE otherwise.
See [ANOIcs-gene].
Table 10: M-GET parameters
4.4 M-CANCEL-GET service

PARAMETER NAME
invokeID
get-invoke-ID
CancelGet Errors
R/I
M
M
-
R/C
M(=)
C
COMMENTS
Table 11: M-CANCEL-GET parameters
ED
01

RELEASED
9772m1re.doc
15/05/2009
20/26

4.5 M-SET service

A NMC is free to decide how it will send its modifications, i.e. either through one or several
M-SET requests on the same managed object instance).
PARAMETER NAME
invokeID
linked-ID
mode
R/I
M
M
R/C
M
C
-
ce
accessControl
synchronization
scope
filter
modificationList
M
M
U
U
U
U
M
modifyOperator
attributeId
attributeValue
M
C
managedObjectClass
currentTime
attributeList
attributeId
attributeValue
Set Errors
C
C
U
U
M
M
C
COMMENTS
The value of this parameter is ignored. If

this value is not equal to 'confirmed', the
request is treated similarly to the same
request but with 'confirmed' as the value of
the mode parameter.
See section 4.8.1.

See section 4.8.4.
See section 4.8.3.
See section 4.8.3.
This parameter contains one item per
requested attribute value modification (a).
This sub-field must be present except

when the modify operator is intended to be
'replace', in which case it may be omitted.
This is because 'replace' is defined as the
default value for this sub-field.
This sub-field must always be present.
This sub-field must be present except

when the modify operator is 'setToDefault'
and the attribute has the REPLACE WITH
DEFAULT property (i.e. implicit support of
a default value).
See [ANOIcs-gene].
See section 4.8.2.
There is one item in this list per attribute that is
identified in the modificationList parameter of
the request.
Table 12: M-SET parameters

(a) The following holds concerning the 'Modification List' parameter:
If a 'replace' and/or 'setToDefault' is specified more than once for the same
attribute,
only the last value of this attribute in the list is taken into account;
in the response, the attribute is present only once, with the last value.
ED
01

RELEASED
9772m1re.doc
15/05/2009
21/26

If a 'setToDefault' operator is specified for an attribute that has no default value, an

'invalidOperation' error is returned.
If an 'addValues' operator is specified more than once for the same attribute,
all the addValues specifications are taken into account: the new attribute value
is the union of its old one and all the added ones;
in the response, the attribute is present only once, with its new value.
If an 'addValues' operator is used on a single-valued attribute, an 'invalidOperation'
error is returned
If an 'addValues' operator is used on a size-limited set and the result exceeds the
maximum size, an 'invalidAttributeValue' error is returned.
If a non 'replaceable' attribute with 'replace' as modify operator is specified, a
setListError error is returned with an 'invalidOperation' attribute error.
If a non-existing value with 'removeValues' as modify operator is specified, this part
of the request is accepted and does not cause any change.
If an existing value with 'addValues' as modify operator is specified, this part of the
request is accepted and does not cause any change.
4.6 M-ACTION service

PARAMETER NAME
invokeID
linked-ID
mode
R/I
M
M
R/C
M
C
-
ce
accessControl
synchronization
scope
filter
actionInfo
M
M
U
U
U
U
U
managedObjectClass
currentTime
actionReply
C
C
U
C
Action Errors
COMMENTS
This parameter must always contain
'confirmed' since all actions defined at the
NMC/9153 OMC-R Q3 interface are defined
to operate in confirmed mode (see
[ANOIgdmo]).
See section 4.8.1.

See section 4.8.4.
See section 4.8.3.
See section 4.8.3.
This parameter is supported (and mandatory)
whenever the WITH INFORMATION SYNTAX
clause appears for the corresponding ACTION
template in [ANOIgdmo].
See [ANOIcs-gene].
See section 4.8.2.
whenever the WITH REPLY SYNTAX clause
appears for the corresponding ACTION
See [ANOIcs-gene].
Table 13: M-ACTION parameters
ED
01

RELEASED
9772m1re.doc
15/05/2009
22/26

4.7 M-EVENT-REPORT service

PARAMETER NAME
invokeID
mode
R/I
M
M
R/C
M(=)
-
managedObjectClass
eventTime
M
M
U
U
U
-
eventType
eventInfo
M
U
C(=)
-
currentTime
eventReply
U
C
EventReport Errors
COMMENTS
This parameter
confirmed'.
always
contains
'non-
For an 9153 OMC-R internal event, this

parameter contains the 9153 OMC-R time.
For an event caused by a BSS-NE, it shall
contain the BSS-NE time if available.
Otherwise, it shall contain the 9153 OMC-R
time.
The format 'UTCTime' is used.
This parameter identifies the notification.
whenever the WITH INFORMATION SYNTAX
clause appears for the corresponding
NOTIFICATION template in [ANOIgdmo].
See [ANOIcs-gene].
See section 4.8.2.
whenever the WITH REPLY SYNTAX clause
appears for the corresponding NOTIFICATION
See [ANOIcs-gene].
Table 14: M-EVENT-REPORT parameters
4.8 Common Conformance Statements

4.8.1 The accessControl parameter
If a value is supplied for the accessControl parameter, this value is ignored by the
NMC/9153 OMC-R Q3 Interface Mediation Device.
4.8.2 The currentTime parameter

For the currentTime parameter, the UTC time form of GeneralizedTime is used (second form
mentioned in [X.208]). For example, 20003003161520.5Z.
4.8.3 The scope and filter parameters

The scope and/or filter parameters that are allowed are defined in [ANOIcs-gene].
ED
01

RELEASED
9772m1re.doc
15/05/2009
23/26

4.8.4 The synchronization parameter

If present, the synchronization parameter must always contain 'bestEffort'. Otherwise, the
error 'syncNotSupported' is returned.
ED
01

RELEASED
9772m1re.doc
15/05/2009
24/26

5. SAFEGUARDING MECHANISMS
5.1 Event request sequence
A flow control mechanism is offered by Solstice CMIP version 9.0. More precisely, if a flood
of notifications is to be sent to a NMC and if the traffic is too heavy, Solstice CMIP version
9.0 will block the sending of events by the agent when the maximum number of
simultaneous interactions is exceeded. This maximum number is configurable.
5.2 Lock of an EFD

Locking an EFD, i.e. setting the "X.721":administrativeState attribute value of the
corresponding "X.721":eventForwardingDiscriminator MOI to 'locked', has no consequence
on the sending of the notifications that passed this EFD before it was locked.
5.3 Deletion of an EFD

When an EFD is deleted, the notifications that passed the EFD but are not sent at EFD
deletion time, are processed normally.
5.4 Association survey

The "ANOI":anoiPlmnNetwork MOI sends periodically a specific notification to the NMCs,
namely the "ANOI":associationSurvey notification. See [ANOIprofile] and [ANOIgdmo] for
more information.
5.5 Resynchronization
See [ANOIprofile].
ED
01

RELEASED
9772m1re.doc
15/05/2009
25/26

6. GLOSSARY
ACSE
AE
AET
APDU
ASN1
BOC
CLNP
CLNS
CMIP
CMISE
CSMA/CD
CONS
EPIM
FU
GDMO
HP
HPOV DM
IEC
IP
ISO
ITU-T
LAN
LAPB
LLC
MAC
MOC
MOI
NMC
NSAP
O&M
OID
OSI
PICS
PLP
PDU
PSAP
PSEL
Rec.
ROSE
SNPA
SSAP
SSEL
TCP
TSAP
TSEL
Association Control Service Element

Application Entity
AE-title value
Application Protocol Data Unit
Abstract Syntax Notation One
Connectionless Network Layer Protocol
Connectionless Network Layer Service
Common Management Information Protocol
Common Management Information Service Element
Carrier Sense Multiple Access with Collision Detection
Connection-mode Network Layer Service
Event Processing IM
Functional Unit
Guidelines for the Definition of Managed Objects
Hewlett-Packard
Hewlett-Packard OpenView Distributed Management
International Electrotechnical Commission
Inter-networking Protocol
International Organization for Standardization
International Telecommunication Union Telecommunication Standardization Sector
Local Area Network
Link Access Procedure Balanced
Logical Link Control
Media Access Control
Managed Object Class
Managed Object Instance
Network Management Centre
Network Service Access Point
Operation and Maintenance
OBJECT IDENTIFIER
Open Systems Interconnection
Protocol Implementation Conformance Statements
Packet Layer Protocol
Protocol Data Unit
Presentation Service Access Point
Presentation Selector
Recommendation
Remote Operations Service Element
Subnetwork Point of Attachement
Session Service Access Point
Session Selector
Transmission Control Protocol
Transport Service Access Point
Transport Selector
END OF DOCUMENT
ED
01

RELEASED
9772m1re.doc
15/05/2009
26/26

NMC/9153 OMC-R Q3 Interface: Q3 Protocol Conformance Statements

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NMC/9153 OMC-R Q3 Interface: Q3 Protocol Conformance Statements

Uploaded by

Copyright:

Available Formats

All rights reserved.

Passing on and copying of this