09772LAAAe01

8/13/2019 09772LAAAe01

1/27

NMC/A1353 RA Q3 Interface: Q3 Protocol Conformance Statements

ED 01 RELEASED

Evolium9772l1re.doc28/09/2007 3BK 09772 LAAA PBZZA 1/1

Allrightsreserved.

Passingonandc

opyingofthis

document,useandcommunicationo

fitscontents

NMC/A1353 RA Q3 Interface:

Q3 Protocol Conformance Statements

(B10 onwards)

8/13/2019 09772LAAAe01

2/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

SYSTEM FUNCTIONAL BLOCKS

TABLE OF CONTENTS

1. INTRODUCTION...............................................................................................8 1.1 Scope of the document ......................................................................... 81.2 Notations and conventions...................................................................8

2. OVERVIEW OF THE Q3 PROCOCOL STACK................................................82.1 General description............................................................................... 82.2 Detailed description ............................................................................ 10

2.2.1 Lower layer infrastructure ............................................................102.2.1.1 CONS1............................................................................................................10

2.2.1.1.1 Physical and Data Link layers..................................................................... 102.2.1.1.2 Network layer.............................................................................................. 102.2.1.1.3 Transport layer............................................................................................ 10

2.2.1.2 CLNS1 ...................................... .............................................. ........................102.2.1.2.1 Physical and Data Link layers..................................................................... 102.2.1.2.2 Network layer.............................................................................................. 112.2.1.2.3 Transport layer............................................................................................ 11

2.2.1.3 RFC10006/TCP/IP..........................................................................................11 2.2.1.3.1 Physical and Data Link layers..................................................................... 112.2.1.3.2 Network layer.............................................................................................. 112.2.1.3.3 Transport layer............................................................................................ 11

2.2.2 Upper layer infrastructure ............................................................122.2.2.1 Session layer ............................................. ............................................. .........122.2.2.2 Presentation layer............................................................................................122.2.2.3 Application layer.............................................................................................12

2.2.2.3.1 ACSE .......................................................................................................... 12

2.2.2.3.2 ROSE .......................................................................................................... 122.2.2.3.3 CMISE........................................................................................................ 132.2.2.3.4 NMC/A1353 RA Q3 Interface-related Applications .................................. 13

2.3 Addressing........................................................................................... 132.3.1 Introduction..................................................................................13 2.3.2 AE-title values (AET) ...................................................................142.3.3 Presentation Service Access Point (PSAP) values......................14

2.3.3.1 Introduction.....................................................................................................14 2.3.3.2 PSEL, SSEL and TSEL values ........................................ ...............................142.3.3.3 NSAP addresses ........................................ ............................................. .........142.3.3.4 SNPA addresses ........................................ ............................................. .........15

3. FURTHER CUSTOMIZATION OF ACSE SERVICES .................................... 163.1 A-ASSOCIATE service.........................................................................163.1.1 A-ASSOCIATE parameters .........................................................163.1.2 Corresponding functional issues..................................................17

3.2 A-RELEASE service.............................................................................173.2.1 A-RELEASE parameters .............................................................173.2.2 Corresponding functional issues..................................................17

3.3 A-ABORT and A-P-ABORT services...................................................17

8/13/2019 09772LAAAe01

3/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

3.3.1 A-ABORT parameters..................................................................173.3.2 A-P-ABORT parameters ..............................................................183.3.3 Corresponding functional issues..................................................18

3.4 Common Conformance statements ................................................... 183.4.1 Application-context-name values.................................................183.4.2 AP-title values..............................................................................18

3.4.3 AE-qualifier values.......................................................................183.4.4 Parameters associated with the authentication FU......................18

4. FURTHER CUSTOMIZATION OF THE CMIS SERVICES............................. 194.1 M-CREATE service...............................................................................194.2 M-DELETE service............................................................................... 194.3 M-GET service......................................................................................204.4 M-CANCEL-GET service......................................................................204.5 M-SET service ......................................................................................214.6 M-ACTION service ............................................................................... 224.7 M-EVENT-REPORT service .................................................................23

4.8 Common Conformance Statements...................................................234.8.1 The accessControl parameter .....................................................234.8.2 The currentTime parameter ......................................................... 234.8.3 The scope and filter parameters ..................................................234.8.4 The synchronization parameter ...................................................24

5. SAFEGUARDING MECHANISMS..................................................................255.1 Event request sequence......................................................................255.2 Lock of an EFD.....................................................................................255.3 Deletion of an EFD...............................................................................255.4 Association survey..............................................................................255.5 Resynchronization...............................................................................25

6. GLOSSARY....................................................................................................26

01 070924 First issue O&M System TD/MRC/OMD Spec

ED DATE CHANGE NOTE APPRAISAL AUTHORITY ORIGINATOR

8/13/2019 09772LAAAe01

4/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

LIST OF FIGURES AND TABLES

Figure 1: The supported Q3 Protocol Stack ............................................................................9Figure 2: Structure of a PSAP value......................................................................................14

Table 1: Conventions used in tables .......................................................................................8Table 2: Addressing the A1353 RA instance: PSEL, SSEL and TSEL values......................14Table 3: Addressing the A1353 RA instance: NSAP addresses ...........................................15Table 4: A-ASSOCIATE parameters .....................................................................................16Table 5: A-RELEASE parameters .........................................................................................17Table 6: A-ABORT parameters .............................................................................................18Table 7: A-P-ABORT parameters..........................................................................................18Table 8: M-CREATE parameters...........................................................................................19Table 9: M-DELETE parameters ...........................................................................................20Table 10: M-GET parameters................................................................................................20Table 11: M-CANCEL-GET parameters ................................................................................20Table 12: M-SET parameters ................................................................................................21Table 13: M-ACTION parameters..........................................................................................22Table 14: M-EVENT-REPORT parameters ...........................................................................23

HISTORY

Ed. 01

05/09/2007: Creation from 3BK 09772 JAAA PBZZA Ed.01 Released

General changes

B9 is replaced by B10

The RELATED DOCUMENTS part is updated for B10

24/09/2007: No technical changes.

REFERENCED DOCUMENTS

Alcatel documents

[ANOIprofile] Profile for the NMC/A1353 RA Q3 Interface3BK 09654 LAAA PBZZA

[ANOIgdmo] NMC/A1353 RA Q3 Interface Information Model: GDMO FormalSpecification3BK 09707 LAAA PBZZA

[ANOIcs-gene] NMC/A1353 RA Q3 Interface: Overview and Conformance Statements3BK 09709 LAAA PBZZA

Standards

[STD0005] Internet ProtocolRecommendation Internet Architecture Board STD0005, September1981.

[STD0007] Transmission Control ProtocolRecommendation Internet Architecture Board STD0007, September1981.

8/13/2019 09772LAAAe01

5/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

[STD0035] ISO Transport Service on top of the TCPRecommendation Internet Architecture Board STD0035 Version 3, May1987.

[ISO/IEC 7776] Information technology - Telecommunications and informationexchange between systems - High-level data link control procedures

Description of the X.25 LAPB-compatible DTE data link proceduresRecommendation ISO/IEC 1776, 1995

[ISO/IEC 8073] Information technology - Telecommunications and informationexchange between systems - Open Systems InterconnectionProtocol for providing the connection-mode transport serviceRecommendation ISO/IEC 8073, 1992

[ISO/IEC 8208] Information Technology - Data Communications - X.25 Packet layerProtocol for Data Terminal EquipmentRecommendation ISO/IEC 8208, 1995

[ISO/IEC 8348-A2] Information technology - Open Systems Interconnection - Network

Service DefinitionRecommendation ISO/IEC 8348, Addendum 2, Covering NetworkLayer Addressing

[ISO/IEC 8473-2] Information Technology - Protocol for providing the connectionless-mode network service, Part 2: Provision of the underlying service by anISO/IEC 8802 subnetwork.Recommendation ISO/IEC 8473-2, 1996

[ISO/IEC 8802-2] Information technology - Telecommunications and informationexchange between systems - Local and metropolitan area networks -Specific requirements - Part 2: Logical Link ControlRecommendation ISO/IEC 8802-2, 1994

[ISO/IEC 8802-3] Information technology - Telecommunications and informationexchange between systems - Local and metropolitan area networks -Specific requirements - Part 3: Carrier sense multiple access withcollision detection (CSMA/CD) - Access method and physical layerspecificationsRecommendation ISO/IEC 8802-3, 1996

[X.121] Data Networks and Open System Communication - Public Datanetworks - Network Aspects - International numbering plan for publicdata networksITU-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 NotationSpecification of Basic Encoding Rules for Abstract Syntax NotationOne (ASN.1)ITU-T Recommendation X.209 (ISO/IEC 8825), 1988

8/13/2019 09772LAAAe01

6/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

[X.213] Information Technology- Open Systems Interconnection (OSI)Network Service DefinitionITU-T Recommendation X.213 (ISO/IEC 8348), November 1995

[X.214] Information Technology- Open Systems Interconnection (OSI)Transport Service Definition

ITU-T Recommendation X.214 (ISO/IEC 8072), November 1995

[X.215] Information Technology- Open Systems Interconnection (OSI)Session Service DefinitionITU-T Recommendation X.215 (ISO/IEC 8326), November 1995

[X.216] Information Technology- Open Systems Interconnection (OSI)Presentation Service DefinitionITU-T Recommendation X.216 (ISO/IEC 8822), 1994

[X.217] Information Technology- Open Systems Interconnection (OSI)Service Definition for the Association Control Service ElementCCITT Recommendation X.217 (ISO/IEC 8649), 1996

[X.219] Data Communication Networks- Open Systems Interconnection (OSI)Remote operations: Model, notation and service definitionCCITT Recommendation X.219 (ISO/IEC 9072-1), 1988

[X.223] Information Technology- Open Systems Interconnection (OSI)Use of X.25 to provide the OSI Connection Mode Network Service forITU-T ApplicationsITU-T Recommendation X.223 (ISO/IEC 8878), November 1993

[X.224] Information Technology- Open Systems Interconnection (OSI)Protocol for providing the Connection-mode Transport ServiceITU-T Recommendation X.224 (ISO/IEC 8072), November 1995

[X.225] Information Technology- Open Systems Interconnection (OSI)Connection-oriented Session Protocol: Protocol SpecificationITU-T Recommendation X.225 (ISO/IEC 8327-1), November 1995

[X.226] Information Technology- Open Systems Interconnection (OSI)Connection-oriented Presentation Protocol: Protocol SpecificationITU-T Recommendation X.226 (ISO/IEC 8823-1), 1994

[X.227] Information Technology- Open Systems Interconnection (OSI)Connection-oriented Protocol for the Association Control ServiceElement: Protocol specificationCCITT Recommendation X.217 (ISO/IEC 8650-1), 1996

[X.229] Data Communication Networks- Open Systems Interconnection (OSI)Remote operations: Protocol specificationCCITT Recommendation X.229 (ISO/IEC 9072-2), 1988

[X.25] Data Networks and Open System Communication - Public DataNetworks - InterfacesInterface between Data Terminal Equipment (DTE) and Data Circuit-

8/13/2019 09772LAAAe01

7/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

terminating Equipment (DCE) for terminals operating in the packetmode and connected to public data networks by dedicated circuit

[X.233] Information Technology- Open Systems Interconnection (OSI)Protocol for providing the connectionless-mode network service:Protocol specificationITU-T Recommendation X.233 (ISO/IEC 8473-1), 1994

[X.410] Information Technology- Data Networks and Open SystemCommunication - Message Handling Systems (MHS)Remote Operations and Reliable Transfer ServerCCITT Recommendation X.410, 1984

[X.650] Information Technology- Open Systems InterconnectionBasic reference Model: Naming and AddressingITU-T Recommendation X.650 (ISO/IEC 7498-3), 1996

[X.710] Data Communication Networks- Open Systems Interconnection (OSI)-ManagementCommon Management Information Service Definition

CCITT Recommendation X.710 (ISO/IEC 9595), 1997

[X.711] Data Communication Networks- Open Systems Interconnection (OSI)-ManagementCommon Management Information Protocol SpecificationCCITT Recommendation X.711 (ISO/IEC 9596), March 1991

[Q.811] Specifications of Signalling System No. 7 - Q3 interfaceLower layer protocol profiles for the Q3 and X interfacesITU-T Recommendation Q.811, June 1997

[Q.812] Specifications of Signalling System No. 7 - Q3 interfaceUpper Layer protocol profiles for the Q3 and X interfaces

ITU-T Recommendation Q.812, June 1997

Sun MicrosystemsDocumentsN.B.: 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 werefully compliant with the corresponding standard(s) with no noticeable options. Thereader shall contact directly SUN with respect to related Conformance Statements.

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

[PICS_CONS1_3] Protocol Implementation Conformance Statement Proforma for PacketLayer (ISO 8208)US GOSIP Version 2, March 1992

[PICS_CLNS1_3] Protocol Implementation Conformance Statement Proforma forConnectionless Network Layer Protocol (ISO 8473) - CLNS1 part

8/13/2019 09772LAAAe01

8/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

US GOSIP, March 1992

[CS_IP] Protocol Implementation Conformance Statement Proforma forConnectionless Network Layer Protocol (ISO 8473) - IP partUK GOSIP PICS for ISO 8473, 1991

[PICS_CONS1_4] Information processing systems - Open Systems Interconnection -

Connection-oriented transport protocol specificationAmendment 3: PICS proforma (ISO 8073)Concerned Product: Solstice OSI version 9.0N.B.: Only the part dealing with the Transport class 2 shall be

considered in this document.

[PICS_CLNS1_4] Protocol Implementation Conformance Statement Proforma forTransport Class 0 and 4 Protocols (ISO 8073)US/UK GOSIP, March 1992

[PICS_CO_5] Information technology - Open Systems Interconnection - Basicconnection-oriented session protocol specificationPart 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 forthe Basic Connection-oriented Presentation protocol (ISO/IEC DIS8823-2)Concerned Product: Solstice OSI version 9.0.Date of statement: 07/09/1993.

[PICS_CO_ACSE] Information technology - Open Systems Interconnection - ProtocolSpecification for the Association Control Service ElementPart 2: Protocol Implementation Conformance Statements (PICS)(ISO/IEC DIS 8650-2)

Concerned Product: Solstice OSI version 9.0.

[PICS_CO_ROSE] Remote Operations Service ElementProtocol Implementation Conformance Statements (PICS) proformaConcerned Product: Solstice CMIP version 9.0

[PICS_CO_CMIP] Information technology - Open Systems Interconnection - CommonManagement Information ProtocolProtocol Implementation Conformance Statements (PICS) proformaConcerned Product: Solstice CMIP version 9.0

Alcatel COMET Documents

[EPIM-Guide] COMET 6.5 Event Processing IM User Guide3BP 21673 0012 TCZZA, Ed.01

RELATED DOCUMENTS

None.

8/13/2019 09772LAAAe01

9/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

1. INTRODUCTION

1.1 Scope of the document

This document defines the Conformance Statements for the Q3 Protocol used by theNMC/A1353 RA Q3 interface.In particular, it defines:

The structure of the Q3 Protocol Stack

Peculiarities with respect to standards and implementation options for the differentlayers of the Q3 Protocol StackN.B.: Given that, for the NMC/A1353 RA Q3 Interface, the different layers of the

Q3 Protocol Stack actually rely on third party products, this part islimited to important noticeable issues. For a complete specification ofthe corresponding Conformance Statements, the reader is referred torelated documents (PICS Proforma and administration documents) ofthese third party productswhich 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 SEMANTICS

M The associated item is mandatory.

(=) The value of the associated item is equal to the value of the one in thecolumn to the left.For example, it can be used to indicate that the value of a CMISparameter in a R/C primitive is equal to the one in the R/I primitive.

U The use of the associated item is a service-user option.

- The associated item is not present in the interaction described by theprimitive concerned.

C The associated item is conditional.

bold characters When used in a table, bold characters highlight noticeable peculiaritieswith respect to the corresponding standard(s).

name In the first column of a table whose entry corresponds to an item thatis a list, 'name' denotes a sub-field of this item. This is used todescribe, 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:

8/13/2019 09772LAAAe01

10/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

NMC/A1353 RA Q3 Interface-related Applications

(7) Application CMISE([X.710],[X.711])

UpperLayers

ACSE([X.217],[X.227])

ROSE([X.219],[X.229])

([Q.812])

(6) PresentationOSI Presentation Layer([X.209],[X.216],[X.226])

(5) Session

OSI Session Layer([X.215],[X.225])

(4) TransportTransport over

CONSTransport over

CLNSRFC1006([STD0035])

([ISO/IEC 8073],[X.214],[X.224])

([ISO/IEC 8073],[X.214],[X.224])

TCP([STD0007])

Lowerlayers (3) Network

X.25 PLPCLNP/CLNS

([X.213],[X.233])IP

([Q.811]) ([ISO/IEC 8208],[X.213],[X.223])

[ISO/IEC 8473-2]([STD0005])

(2) Data LinkX.25 LAPB

[ISO/IEC 8802-2]LLC (Type 1)

Notspecified

([ISO/IEC 7776],[X.25])

[ISO/IEC 8802-3]MAC CSMA/CD

(1) Physical See [Q.811] Not specified Notspecified

Lower layer protocol profiles: CONS1 CLNS1RFC1006/

TCP/IP

Legend:The corresponding layer/service element is supported through the following thirdparty 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.

8/13/2019 09772LAAAe01

11/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

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 partyproduct: Solstice X.25 version 9.2.For these layers,

This product complies with the CONS1 profile of [Q.811]. In particular, the Data LinkLayer 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 PacketLayer 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 partyproduct: Sun Solaris operation version 5.8.For these layers,

This product complies with the CLNS1 profile of [Q.811]. In particular, the Data LinkLayer conforms to [ISO/IEC 8802-2] LLC and [ISO/IEC 8802-3] MAC CSMA/CD.

8/13/2019 09772LAAAe01

12/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

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


For the CLNS1 profile, the Network layer is supported by the following third party product:Solstice OSI version 9.0.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:Solstice OSI version 9.0.For this layer,

This product conforms to Rec. [Q.811], [X.214], [X.224] and [ISO/IEC 8073]. Inparticular, 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 thirdparty product: Sun Solaris operation version 5.8.


For the RFC10006/TCP/IP profile, the Network layer is supported by the following third partyproduct: 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 theREFERENCED DOCUMENTS part.


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,

This product conforms to Rec. [Q.811] and [STD0007]. Concerning the applicable Conformance Statements, see the N.B. of the

REFERENCED DOCUMENTS part.

The link with the OSI session layer (RFC10006) supported by the following third partyproduct: Solstice OSI version 9.0.For this link, This product conforms to Rec. [Q.811] and [STD0035].

8/13/2019 09772LAAAe01

13/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

Concerning the applicable Conformance Statements, see the N.B. of theREFERENCED DOCUMENTS part.

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

2.2.2 Upper layer infrastructure

Only the upper layer protocol profile for Interactive Class services defined in [Q.812] isrelevant for the NMC/A1353 RA Q3 Interface.

2.2.2.1 Session layer

The session layer is supported by the following third party product: Solstice OSI version9.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 theSession connection-oriented protocol is supported.

2.2.2.2 Presentation layer

The presentation layer is supported by the following third party product: Solstice OSI version9.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 transfersyntax is defined by the Basic Encoding Rules (BER) defined in Rec. [X.209] andidentified 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 thePresentation 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 theconnection-oriented ACSE protocol is supported.For this service element,

This product conforms to Rec. [Q.812], [X.217] and [X.227]. In particular, the ACSEabstract 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/A1353 RAQ3 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.

8/13/2019 09772LAAAe01

14/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

For this service element,

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.For this service element,

This product conforms to Rec. [Q.812], [X.710] and [X.711]. In particular, the CMISEabstract 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 arethe 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/A1353 RA Q3 Interface-related Applications

The NMC/A1353 RA Q3 Interface is supported:

For the "ANOI":anoiPlmnNetwork MOI and all MOIs named under it, via a dedicatedMediation Device developped by Alcatel.

For the "X.721":system MOI and all the MOIs named under it, via the EFD and Logfacilities 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/A1353 RA Q3 interface, the following application entities can be addressed: The A1353 RA instance

For a given Q.811 profile, the corresponding address (actually the NSAP part of it) isonly dependent on the address (for that profile) of the workstation on which the A1353RA 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 withthe associated type of NMC (i.e. primary or secondary) are defined at the installation ofthe A1353 RA instance (from a NMC viewpoint).

What follows only deals with noticeable addressing aspect. For more information, refer tothe Administration Guide of Solstice CMIP version 9.0.

8/13/2019 09772LAAAe01

15/27

8/13/2019 09772LAAAe01

16/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

[Q.811] profile NSAP address

CONS1 The X.25 address of the workstation on which the A1353 RAinstance is installed

CLNS1 The MAC layer address of the workstation on which theA1353 RA instance is installed

RFC1006/TCP/IP 0x540072872203 followed by the IP address of the

workstation on which the A1353 RA instance is installed.For example, if this IP address is 15.5.25.225, the NSAPaddress will be 0x540072872203015005025225.

Table 3: Addressing the A1353 RA 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 CONS1profile. In that case, the SNPA address needs to be supplied when configuring Solstice X.25version 9.2 (see section 2.2.1.1.1). This address is the [X.121] address (in hexadecimal) of

the workstation on which the A1353 RA instance is installed (up to 15 digits).

8/13/2019 09772LAAAe01

17/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

3. FURTHER CUSTOMIZATION OF ACSE SERVICES

3.1 A-ASSOCIATE service

3.1.1 A-ASSOCIATE parameters

PARAMETER NAME Req Ind Rsp Cnf COMMENT

application-context-name

M M(=) M C See section 3.4.1.

called-AP-title U C(=) - - See section 3.4.2.

called-AE-qualifier U C(=) - - See section 3.4.3.

called-AP-invocation-identifier

- - - - It is recommended not to includethis parameter in the request.

called-AE-invocation-identifier


calling-AP-title U C(=) - - See section 3.4.2.calling-AE-qualifier U C(=) - - See section 3.4.3.

calling-AP-invocation-identifier


calling-AE-invocation-identifier


result - - M M

result-source-diagnostic - - - M

responding-AP-title - - U C(=) See section 3.4.2.responding-AE-qualifier - - U C(=) See section 3.4.3.responding-AP-invocation-identifier

- - - - This parameter is not included inthe response.

responding-AE-invocation-identifier - - - - This parameter is not included inthe response.

sender-acse-requirements

U C - -

responder-acse-requirements

- - C C(=)

mechanism-name - - - - See section 3.4.4.calling-authentication-value

- - - - See section 3.4.4.

responding-authentication-value

- - - - See section 3.4.4.

application-context-name-list

U C C C

implementation-information

- - - -

user-information U C(=) U C(=) This parameter is always includedin the response.

Table 4: A-ASSOCIATE parameters

8/13/2019 09772LAAAe01

18/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

3.1.2 Corresponding functional issues

An association between the A1353 RA and a NMC is created:

By the A1353 RA when it needs to forward a notification to that NMC and noassociation with that NMC has yet been opened.

The A1353 RA does not open two associations with the same called AET at the sametime.After the A1353 RA has forwarded an association request in connection-oriented modetowards a NMC, the association will not be established in case:

It receives a negative acknowledgement (A-ASSOCIATE-cnf with a resultparameter 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 associationwith the A1353 RA has yet been opened.

The A1353 RA may use an association created by a NMC to forward its notifications to that

NMC. A NMC may use an association created by the A1353 RA with that NMC to send itsCMISE operation requests and to wait for the potentially associated confirmations.

3.2 A-RELEASE service

3.2.1 A-RELEASE parameters

PARAMETER NAME Req Ind Rsp Cnf COMMENT

reason U C(=) U C=

user-information U C(=) - - This parameter is not included inthe response.

Table 5: A-RELEASE parameters


An association created by the A1353 RA is normally released by the A1353 RA 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 torelease this association. The A1353 RA confirms positively the corresponding A-RELEASEindication 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 Req Ind COMMENT

abort-source - Mabort-diagnostic U C(=)

user-information U C(=)

8/13/2019 09772LAAAe01

19/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

Table 6: A-ABORT parameters

3.3.2 A-P-ABORT parameters

PARAMETER NAME Ind COMMENT

provider-reason C

Table 7: A-P-ABORT parameters


Violations of the rules of the protocols used are intercepted by the A1353 RA and result inthe 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 definedas:

{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-form2defined 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 unitis not supported (see section 2.2.2.3.1).

8/13/2019 09772LAAAe01

20/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

4. FURTHER CUSTOMIZATION OF THE CMIS SERVICES

4.1 M-CREATE service

PARAMETER NAME R/I R/C COMMENTSinvokeID M M(=)

managedObjectClass M U

managedObjectInstance U C

superiorObjectInstance U -

accessControl U - See section 4.8.1.

referenceObjectInstance U - If this parameter is specified, the attributevalues are copied from the supplied instance,then possibly replaced by the ones specified inthe Attribute List parameter.

attributeList U C In a R/I primitive, this list includes one item perattribute of the MOI that shall be assigned agiven value.The set of attributes that shall or may have acorresponding item in this list is defined in[ANOIcs-gene].See, in addition (a) below.In a R/C primitive, this list shall include one itemper attribute of the MOI that is either GET orGET-REPLACE, except in a negativeconfirmation, in which case each of these itemsmay or not be present.

attributeId M M

attributeValue M M

currentTime - U See section 4.8.2.

Create Error - C

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

If no naming attribute is specified for an object that doesn't support automaticinstance naming and if no managedObjectInstance parameter is specified, then a'missingAttributeValue' error response is returned.

4.2 M-DELETE service

PARAMETER NAME R/I R/C COMMENTS

invokeID M M

linked-ID - C

baseManagedObjectClass M -

baseManagedObjectInstan M -

8/13/2019 09772LAAAe01

21/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents


ce

accessControl U - See section 4.8.1.

synchronization U - See section 4.8.4.

scope U - See section 4.8.3.filter U - See section 4.8.3.

managedObjectClass - CmanagedObjectInstance - CcurrentTime - U See section 4.8.2.Delete Error - C

Table 9: M-DELETE parameters

4.3 M-GET service


invokeID M M

linked-ID - C

baseManagedObjectClass M -baseManagedObjectInstance

M -

accessControl U - See section 4.8.1.synchronization U - See section 4.8.4.scope U - See section 4.8.3.filter U - See section 4.8.3.attributeIdList U - See [ANOIcs-gene].

managedObjectClass - C

managedObjectInstance - CcurrentTime - U See section 4.8.2.attributeList - C This list includes one item:

per attribute identified in the attributeIdListparameter when the latter is not empty;

per attribute of the MOI that is either GETor GET-REPLACE otherwise.

See [ANOIcs-gene].

attributeId - M

attributeValue - M

Get Errors - C

Table 10: M-GET parameters

4.4 M-CANCEL-GET service


invokeID M M(=)

get-invoke-ID M -

CancelGet Errors - C

Table 11: M-CANCEL-GET parameters

8/13/2019 09772LAAAe01

22/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

4.5 M-SET service

A NMC is free to decide how it will send its modifications, i.e. either through one or severalM-SET requests on the same managed object instance).


invokeID M Mlinked-ID - C

mode M - The value of this parameter is ignored. Ifthis value is not equal to 'confirmed', therequest is treated similarly to the samerequest but with 'confirmed' as the value ofthe mode parameter.

baseManagedObjectClass M -

baseManagedObjectInstance

M -

accessControl U - See section 4.8.1.synchronization U - See section 4.8.4.

scope U -See section 4.8.3.filter U - See section 4.8.3.

modificationList M - This parameter contains one item perrequested attribute value modification (a).

modifyOperator C This sub-field must be present exceptwhen the modify operator is intended to be'replace', in which case it may be omitted.This is because 'replace' is defined as thedefault value for this sub-field.

attributeId M This sub-field must always be present.

attributeValue C This sub-field must be present exceptwhen the modify operator is 'setToDefault'and the attribute has the REPLACE WITH

DEFAULT property (i.e. implicit support ofa default value).

See [ANOIcs-gene].

managedObjectClass - C

managedObjectInstance - C

currentTime - U See section 4.8.2.attributeList - U There is one item in this list per attribute that is

identified in the modificationList parameter ofthe request.

attributeId M

attributeValue M

Set Errors - C

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 sameattribute,

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.

8/13/2019 09772LAAAe01

23/27

8/13/2019 09772LAAAe01

24/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

4.7 M-EVENT-REPORT service


invokeID M M(=)

mode M - This parameter always contains 'non-confirmed'.

managedObjectClass M UmanagedObjectInstance M U

eventTime U - For an A1353 RA internal event, thisparameter contains the A1353 RA time.

For an event caused by a BSS-NE, it shallcontain the BSS-NE time if available.Otherwise, it shall contain the A1353 RAtime.The format 'UTCTime' is used.

eventType M C(=) This parameter identifies the notification.

eventInfo U - This parameter is supported (and mandatory)whenever the WITH INFORMATION SYNTAXclause appears for the correspondingNOTIFICATION template in [ANOIgdmo].See [ANOIcs-gene].

currentTime - U See section 4.8.2.eventReply - C This parameter is supported (and mandatory)

whenever the WITH REPLY SYNTAX clauseappears for the corresponding NOTIFICATIONtemplate in [ANOIgdmo].See [ANOIcs-gene].

EventReport Errors - C

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 theNMC/A1353 RA 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].

8/13/2019 09772LAAAe01

25/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

4.8.4 The synchronization parameter

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

8/13/2019 09772LAAAe01

26/27


ED 01 RELEASED


Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

5. SAFEGUARDING MECHANISMS

5.1 Event request sequence

A flow control mechanism is offered by Solstice CMIP version 9.0. More precisely, if a floodof notifications is to be sent to a NMC and if the traffic is too heavy, Solstice CMIP version9.0 will block the sending of events by the agent when the maximum number ofsimultaneous 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 thecorresponding "X.721":eventForwardingDiscriminator MOI to 'locked', has no consequenceon 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 EFDdeletion 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] formore information.

5.5 Resynchronization

See [ANOIprofile].

8/13/2019 09772LAAAe01

27/27


ED 01 RELEASED

Allrightsreserved.

Passingonandc

opyingofthis


fitscontents

6. GLOSSARY

ACSE Association Control Service ElementAE Application EntityAET AE-title valueAPDU Application Protocol Data UnitASN1 Abstract Syntax Notation OneBOC baseManagedObjectClassCLNP Connectionless Network Layer ProtocolCLNS Connectionless Network Layer ServiceCMIP Common Management Information ProtocolCMISE Common Management Information Service ElementCSMA/CD Carrier Sense Multiple Access with Collision DetectionCONS Connection-mode Network Layer ServiceEPIM Event Processing IMFU Functional UnitGDMO Guidelines for the Definition of Managed ObjectsHP Hewlett-Packard

HPOV DM Hewlett-Packard OpenView Distributed ManagementIEC International Electrotechnical CommissionIP Inter-networking ProtocolISO International Organization for StandardizationITU-T International Telecommunication Union -

Telecommunication Standardization SectorLAN Local Area NetworkLAPB Link Access Procedure BalancedLLC Logical Link ControlMAC Media Access ControlMOC Managed Object ClassMOI Managed Object InstanceNMC Network Management Centre

NSAP Network Service Access PointO&M Operation and MaintenanceOID OBJECT IDENTIFIEROSI Open Systems InterconnectionPICS Protocol Implementation Conformance StatementsPLP Packet Layer ProtocolPDU Protocol Data UnitPSAP Presentation Service Access PointPSEL Presentation SelectorRec. RecommendationROSE Remote Operations Service ElementSNPA Subnetwork Point of AttachementSSAP Session Service Access Point

SSEL Session SelectorTCP Transmission Control ProtocolTSAP Transport Service Access PointTSEL Transport Selector

END OF DOCUMENT