TMN Architecture

1
TMN Architecture

• Telecommunications Management Network (TMN)
  provides an architecture that allows exchange of
  management information using standard interfaces
• Management network that interfaces with
  telecommunications equipment to control its
  operations
• Standardization of OSI layer management

2
TMN
Operations System
Operations System
Data Communication Network
WorkStation
Switch
Switch
Transmission System
Telecommunications Network
3
Management Functional Areas

• Fault Management
• Alarm Surveillance (Q.821)
• Based on SMFs X.733 (Alarm Reporting), X.734
• (Event Report Management) and Xgt735 (Log Control
  Function)
• Alarm Reporting, Alarm Logging, Alarm Retrieval,
  Alarm Acknowledgment
• Fault Localization
• Fault Correction

4
Management Functional Areas

• Testing (X.745)
• Routine Test
• Test Scheduling
• Trouble Administration
• Create Problem Report
• Review Problem Report
• Configuration Management
• Service Order Management (Provisioning)
• Identify and control provisioning of new
  resources through service orders

5
Management Functional Areas

• Resource Configuration (Reconfiguration)
• Resource Information (Inventory)
• Performance Management
• Traffic Measurement Reporting
• Traffic measurement reports constructed from
  Performance measurement information
• Performance Monitoring
• Obtain, evaluate, and report on network
  performance parameters
• Real-time Performance monitoring, Real-time
  Performance criteria, Request performance
  information, Performance data logging, Retrieve
  Performance log
• Based on X.721 (DMI), X.738 (Summarization
  Function), and X.739 (Metric Objects
  Attribute) SMFs

6
Management Functional Areas

• Accounting Management
• Billing
• Tariffing
• Security Management
• Access Security (Access to Management
  capabilities)
• Managing Access Security (Privileged user defines
  access capabilities of other users)
• Audit Trails
• Security Alarms

7
TMN Reference Architecture
NEF
Q3
X
F
OSF
WSF
g
Q3
F
Q3
MF
Qx
m
QAF
Qx
NEF
OSF Operations System Function MF Mediation
Function NEF Network Element Function QAF Q
Adapter Function
8
TMN Functional Blocks

• Operations Systems Function
• Processes management information in order to
  monitor, control, coordinate telecommunications
  functions
• Network Element Function
• Communicates with TMN in order to be monitored
  and controlled
• Provides telecommunications functions
• Mediation Function
• Builds conforming information to attached
  functional blocks
• May store, adapt, filter, condense information

9
TMN Functional Blocks

• Workstation Function
• Interprets and presents TMN information to
  end-user
• Q Adapter Function
• Connects NEF-like and OSF-like Non-TMN entities
  to TMN

10
TMN Reference Points

• Q Reference Point
• Q3
• Full OSI and CMIS capability
• Connects OSF-NEF, OSF-QAF, OSF-MF, OSF-OSF
• Qx
• Limited OSI capability (e.g CMOT)
• Connects MF-NEF, MF-QAF, MF-MF
• F Reference Point
• Connects WSF-OSF, WSF-MF
• M.3300 defines only capabilities not an interface
• X Reference Point

11
TMN Reference Points

• Connects two TMNs or a TMN with another
  management network that has a TMN-like interface
• M.3400 describes only general capabilities
• M Reference Point
• located outside TMN between QAF and non-TMN
  entities
• G Reference Point
• located outside TMN between WSF and human users

12
Systems Management Functions

• Systems Management Functions (SMFs) define models
  for generic
• aspects of object behavior which serve as
  building blocks for more complex
• services. X. 721 (Definition of Management
  Information) contains data
• referred to by the SMFs
• X.730 Object Management Function Defines a set
  of pass-through
• services for object management that
• are mapped to CMISE. The objective is to define
  an independent layer of
• service that can be mapped to an underlying
  protocol (e.g. CMISE)
• X.731 State Management Function Defines state
  and status attributes that are generic to object
  classes
• X.732 Attributes for representing relationships
  Describes a model for
• representing relationship among objects
• X.733 Alarm Reporting Function Defines the
  basic Alarm reporting model to allow reporting
  of network events. Defines the following alarms
• Communications alarm

13
Systems Management Functions

• Quality of service alarm
• Processing error alarm (processing fault)
• Equipment alarm (equipment fault)
• Environmental alarm
• X.734 Event Report Management Function Defines
  the model for
• Event Reporting based on on a Event Forwarding
  mechanism known as
• Event Forwarding Discriminator (EFD)
• X.735 Log Control Function Describes the
  Logging Model to store information based on a
  filtering or selection criteria
• X.736 Security Alarm Reporting Function
  Defines the structure of Security Alarms

14
Abstract Syntax Notation One

• An abstract syntax notation enables definition of
  types (datatypes) and the specification of values
  for them. It is independent of the encoding
  technique used to represent types.
• ISO 8824 Specification of Abstract Syntax
  Notation One (ASN.1) describes a general
  notation and a set of datatypes
• A transfer syntax describes the encoding method
  applied to represent abstract data types
• ISO 8825 Specification of Basic Encoding Rules
  for Abstract Syntax Notation One describes a set
  of encoding rules to represent ASN.1 data types

15
Abstract Syntax Transfer Syntax in OSI
Communications

• Presentation Applications (e.g. ACSE, CMIS)
  sharing information in an open OSI environment
  must identify through an Abstract Syntax
  Identifier the constituent data types that they
  intend to exchange
• Each Abstract Syntax Identifier proposed by an
  Application must have a corresponding Transfer
  Syntax Identifier to indicate how that data is
  represented and transferred in a machine
  independent manner
• For each Abstract Syntax Identifier proposed by
  an Application, the Presentation Layer associates
  a Transfer Syntax it can support.
• This agreement is made during Presentation Layer
  Connection establishment

16
Abstract Syntax Transfer Syntax in OSI
Communications
ACSE Layer Abstract Syntax 2 2 1 0 1 Transfer
Syntax 2 1 1
CMISE Layer Abstract Syntax 2 9 1 1 4 Transfer
Syntax 2 1 1
Presentation Layer
OSI Stack
17
ASN.1 Modules

• A Module consists of a group of definitions
• Module structure
• ModuleIdentifier DEFINITIONS TagDefault
• BEGIN
• ModuleBody
• END
• ModuleIdentifier
• modulereference
• AssignedIdentifier
• AssignedIdentifier
• ObjectIdentifierValue
• empty
• TagDefault
• EXPLICIT TAGS
• IMPLICIT TAGS empty
• ModuleBody

18
ASN.1 MODULES

• Exports
• EXPORTS SymbolsExported empty
• Imports
• IMPORTS SymbolsImported empty
• Example
• TestModule DEFINITIONS BEGIN
• END
• Export Import clauses can be used to indicate
  definitions that are exported
• by a module and imported from other modules
• Tag option affects how tags are encoded for the
  entire module

19
ASN.1 Types

• Defines several built-in Types
• INTEGER, BOOLEAN, BIT STRING..
• Type Definition
• ltDefinedTypegt lttypereferencegt
• Volume INTEGER
• Users may define new types based on built-in
  (simple)
• Types
• Names of all DefinedTypes must begin with an
  upper-case letter
• Type names may contain digits, letters, and
  hyphens

20
ASN.1 TAGS

• Tags identify a Type
• Tags have two components Class Number
• Tag Class ClassNumber
• ClassNumber
• number Defined Value
• Class
• UNIVERSAL APPLICATIONPRIVATEempty
• Class
• Universal Class assigned to Tags defined for
  ASN.1 types
• Application Used to identify types in an
  Application. OSI
• Application Layer protocols (e.g. ACSE,
  FTAM) use Application
• Tags
• Private Used on an enterprise-specific basis
• Empty Context-specific Tag Identify types in
  a specific context
• ClassNumber or IDcode identifies a particular
  type within a class

21
ASN.1 TAGS

• BOOLEAN UNIVERSAL 1
• INTEGER UNIVERSAL 2
• BIT STRING UNIVERSAL 3
• OCTET STRING UNIVERSAL 4
• NULL UNIVERSAL 5
• OBJECT IDENTIFIER UNIVERSAL 6
• EXTERNAL UNIVERSAL 8
• SEQUENCE UNIVERSAL 16
• SET UNIVERSAL 17
• CHOICE

22
ASN.1 Tagged Types

• Tags assigned by user to a defined type
• Examples
• NumberRange PRIVATE 1 INTEGER
• NameList 21 IMPLICIT OCTET STRING
• Original Universal Tag associated with an ASN.1
  Type not included
• if IMPLICIT Keyword present

23
ASN.1 TYPES Sequence

• A group contruct consisting of built-in and
  defined ASN.1 types
• Order of vlaues is maintained
• SequenceType
• SEQUENCE ElementTypeList
• SEQUENCE
• ElementTypeList
• ELementType ElementTypeList, ElementType
• ElementType
• NamedType NamedType OPTIONAL
• NamedType Default Value
• COMPONENTS OF Type
• NamedType Optional indicates an optional element
• NamedType Deafult indicates a n element with a
  default value
• Default value not carried
• COMPONENTS OF Type includes alll the elements of
  the sequence
• Type referred to

24
ASN.1 TYPES Examples
Designation INTEGER Designation INTEGER
mts(0), sup(1), depthead(2) AccountRecord
SEQUENCE name OCTET STRING, accountType 0
INTEGER DEFAULT 0, balance INTEGER, transaction
s1 INTEGER OPTIONAL AccountHistory
SEQUENCE historyId INTEGER, COMPONENTS OF
AccountRecord AccountLog SEQUENCE OF
AccountRecord
25
ASN.1 Value Notation

• Notation for specifying values of types
• A type that will only carry the specified value
• Used only when the value(s) a type takes is
  known at specification time
• General Format
• ltvaluereference gt lttype gt ltvaluegt
• Examples
• status INTEGER 1
• Salary INTEGER
• averageSalary Salary 1000
• myaccount AccountRecord name xyz,
  account_type 1, balance 0

26
ASN.1 OBJECT IDENTIFIER

• Information in distributed environments (e.g. a
  TMN Object Class) requires unique names
• for universal identification
• ASN.1 Object Identifier Type facilitates
  identification of information elements in
  distributed
• open environments
• Object Identifier values are defined by an Object
  Identifier Tree maintained by
• CCITT and ISO
• Examples
• Cmip_abstract_Syntax OBJECT IDENTIFIER
• cmip_asn1_syntax_val Cmip_abstract_Syntax 2
  9 1 1 4

27
ASN.1 Object Identifier Tree
joint-iso-ccitt (2)
ccitt (0)
iso (1)
ms (9)
cmip (1)
cmip-pci (1)
abstractSyntax (4)
28
ASN.1 ANY TYPE

• For specifications where the data type is not
  known, ASN.1 ANY is generally used. The
• actual type is application-specific and the
  application specifies its type
• All CMISE application-specific data (e.g.
  EventInfo, ActionInfo, Attributes) is specified
• is specified as ANY by CMISE
• The clause ANY DEFINED BY ltnamegt provides more
  information about the
• actual type of the ANY in an instance of
  communication
• In a Sequence and a Set, the ANY DEFINED BY
  construct can refer to a non-optional
• element (eitheran Object Identifier or an
  Integer ) in the containing type
• Application-specific data is encoded/decoded by
  Application building tools (e.g.
• HP OVDM tools)
• Example
• Traffic SEQUENCE
• data_type OBJECT IDENTIFIER,
• traffic_data ANY DEFINED BY data_type

29
ASN.1 EXTERNAL

• Type used for exchanging OSI Presentation Layer
  Data
• When Presentation Layer negotiation of encoding
  rules is not in use, the
• Direct Reference points to the Abstract syntax
  (there is prior agreement on the transfer
• syntax) of the data in the EXTERNAL. The
  Indirect Reference is absent.
• When Presentation Layer negotiation of
  encoding rules is in use and the Presentation
• Layer negotiation has been completed,
  Indirect Reference points to the Presentation
• Context Identifier (PCI) which identifies the
  Presentation Context (Abstract syntax and
• Transfer syntax) to which the data belongs.
  The direct reference is absent.
• When Presentation Layer negotiation of encoding
  rules is in use and the Presentation
• Layer negotiation has not been completed, the
  Direct Reference is required to identify
• the Transfer syntax of the data. The Indirect
  Reference points to the Abstract syntax.
• However, as the transfer syntax has not been
  determined at his point, the Direct Reference
• points to the transfer syntax of the data in
  the EXTERNAL

30
ASN.1 EXTERNAL
EXTERNAL UNIVERSAL 8 IMPLICIT SEQUENCE
direct_ref OBJECT IDENTIFIER
OPTIONAL indirect_ref INTEGER OPTIONAL data_valu
e_descriptor ObjectDescriptor OPTIONAL, encoding
CHOICE single_ASN1_type 0
ANY, octet_aligned 1 IMPLICIT OCTET
STRING, arbitrary 2 IMPLICIT BIT
STRING ObjectDescriptor UNIVERSAL 7
IMPLICIT GraphicString
31
ASN.1 Macro Notation

• Macros provide a formal mechanism to tie a
  variety of diverse elements together
• The diverse elements are usually components of a
  protocol (e.g. ROSE).
• The macro is a convenient method of specifying a
  protocol like ROSE
• Defines a new type and value notation

32
Instance of ROSE Operation Macro CMIP Operations
m-Action OPERATION ARGUMENT ActionArgument
lovalValue 6
33
Basic Encoding Rules for ASN.1

• ISO 8825 defines the BER encoding rules for
  ASN.1
• The encoding convention is known as
  type-length-value (TLV)
• Type is known as the identifier and encodes the
  Tag (class
• number)
• Length indicates the number of octets in the
  contents octets
• Value contains the contents octets

34
Basic Encoding Format
Identifier Octets
Contents Octets
Length Octets
Definite Form Encoding
End of Contents Octets
Length Octets
Identifier Octets
Contents Octets
Indefinite Form Encoding
35
Basic Encoding Format
BITS 8 7 6 5 4 3 2 1
Class
P/C
Number of TAG
0 Primitive 1 Constructed

• Primitive Encoding A data value encoding in
  which the contents octets directly represent
• the value
• Constructed Encoding A data value encoding in
  which the contents octets are the complete
• encoding of one or more other data values

36
Basic Encoding Format
Encoding of class of tag
37
BER Examples Encoding a Boolean

• Encoding is primitive
• Contents will consist of a single octet
• If the Boolean is FALSE, the contents octet will
  be zero
• If the Boolean is TRUE, the contents octet will
  be any non-zero value
• Boolean with value TRUE will be encoded
• Boolean Length Contents
• 01 01 FF

38
BER Examples Encoding a Sequence

• Encoding is constructed
• Contents octets will consist of complete encoding
  of a data values in the order
• of their appearance in the type definition
• myseq SEQUENCE name IA5String, ok BOOLEAN
• name Smith, ok TRUE
• Sequence Length Contents
• 30 0A
  IA5String Length Contents
• 16 05 Smith
• Boolean Length Contents
• 01 01 FF

39
ASN.1 Lab

• Create a directory lab1
• Copy files from Opey in your directory
• Execute make asn1 to run asn1 compiler (asn1cc)
  on your input
• Examine how the construct COMPONENTS OF is
  interpreted by the compiler
• Initialize an instance of AccountRecord in file
  test.c and build your application
• by executing make compile
• Run your application and examine BER trace

40
Association Control Service Element (ACSE)

• ACSE provides services for establishing and
  releasing Application Associations
• ISO 8649 contains ACSE service definition
• ISO 8650 contains ACSE protocol definition
• Services Overview
• Reference model represents communication between
  a pair of Application
• Processes (APs) in terms of communication
  between their Application
• Entities (AEs). The functionality of an AE
  is factored into a number of
• Application Service Elements (ASEs)
• An application context is an explicitly
  identified set of Application Service
• Elements for the interworking of
  Application entities on an association
• X.701 defines an application context for Systems
  Management Applications that include the
  following Application Service Elements
• ACSE, ROSE, CMISE, SMASE
• Application Context 2 9 0 0 2

41
Association Control Service Element (ACSE)

• SMASE (Systems Management Application Service
  Element
• Data used during association establishment to
  indicate the set of Systems
• Management Functional Units (SMFUs) agreed
  between Manager
• Agent Systems
• Refer to X.701 A.3.4

42
Association Control Service Element

• A_ASSOCIATE (confirmed service) initiates the
  establishment of an association
• A_ASSOCIATE parameters
• Application Context Manager and Agent roles can
  be switched between
• each interaction
• Calling Application Process Title (AP Title) ANY
• Calling AE (Application Entity) Qualifier ANY
• Calling AE Title Composite of AP Title AE
  Qualifier HP OVDM
• supports as an OBJECT IDENTIFIER
• Calling AP Invocation Identifier Integer
• Calling AE Invocation Identifier Integer
• Called AP Title
• Called AE Qualifier
• Called AP Invocation Identifier
• Called AE Invocation Identifier

43
Association Control Service Element (ACSE)

• A_RELEASE is a confirmed service that gracefully
  (without loss of data
• an existing application association
• A_ABORT is a non-confirmed service that results
  in the termination of an
• association
• A_P_ABORT is used by ACSE layer to signal to the
  application the release
• of association due to problems in the underlying
  presentation-service

44
Guidelines for the definition of managed Objects
(GDMO)

• GDMO is a specification and notation standard
  (ISO 10165-4/X.722) for
• managed objects
• GDMO definitions consist of templates that
  contain information about
• some aspect of a managed object
• ASN.1 notation is used to describe the data
  elements associated with
• managed objects
• Managed Object Provides abstract view of
  managed entities
• Attributes Represents elements within an entity
  that are of interest from
• a management point-of-view
• Attribute Group Defines a group of Attributes
  that can be conveniently
• referred from a Package
• Package Defines a group of related Behaviors,
  Attributes, Attribute Groups,
• Actions, and Notifications that can be shared by
  Managed Objects
• Behavior (text description) How the object is
  expected to behave under
• 
  specific conditions (Implementation
  specifications)
• Notification Asynchronous Evnts or Notifications
  emitted by Objects

45
Guidelines for the definition of managed Objects
(GDMO)

• Action Specific operation requests (CMISE
  M_ACTION) that can be
• made on a Managed Object
• Name Binding Describes how Managed Object
  instances are to be named
• base on a containment relationship
• Parameter Information that may be carried in
  Action, Notifications, and
• Processing Errors

46
Guidelines for the definition of managed Objects
(GDMO)

• Registration Tree
• A hierarchical scheme maintained by iso and ccitt
  that uniquely identifies
• information including Managed Object Classes
  and their constituent elements (e.g Attributes,
• Notifications, Actions, Packages, and Name
  Bindings) in a distributed
• environment
• Uses ASN.1 type Object Identifier
• Inheritance Tree
• An Object-oriented construct (with a hierarchical
  scheme) that shows how object claasses,
• can inherit attributes, properties, and
  behavior from parent object classes by
  sub-classing
• sub-classing supported by GDMO Managed Objects
• Naming Tree
• A Hierarchical scheme base on a containment
  relationship that shows hows instances of
• Managed Objects are named

47
GDMO Example from X.722

• Refer to example from X.722 Annex A

Registration Hierarchy for MO exampleObjectClass
joint_iso_ccitt (2)
ms (9)
smi (3)
part4 (4)
managedObjectClass (3)
exampleclass (0)
48
GDMO Example from X.722
Inheritance Hierarchy for exampleObjctClass
X.721 Top topPackage, packagesPackage allomorphic
Package
exampleObjectClass examplepackage1, examplepackag
e2
49
GDMO Example from X.722
Naming Tree for X.722 exampleObjectClass
x.721 System Instance SystemId Lucent
X.722 exampleObjectClass Instance InstanceId o
bjecname obj1

• objectname ltvaluegt is called an Attribute
  Value Assertion (AVA)
• Distinguished Name (DN) is a list of RDNs from
  the root of the Naming Tree
• Relative Distinguished Name (RDN) is a single AVA
  identifying an Object instnace
• contained in a specific Superior Object Instance
  (e.g. objectname obj1)
• Local Distinguished Name (LDN) is a list of AVAs
  from any pre-agreed node in the
• Naming Tree other than the root (e.g. System in
  the above example)

50
MANAGED OBJECT CLASS Template

• class-label class Name
• DERIVED FROM Specifies Inheritance from
  superclasses
• All classes are subclasses of top
• MO top conatins attributes that are generic
• ObjectClass, nameBinding,
• packages (list of instantiated pkgs)
• Allomorphism (list of MO classes to which it is
  allomorphic)
• CHARACTERIZED BY Specifies the mandatory
  packages
• CONDITIONAL PACKAGES Conditional packages that
  may br included in
• the class
• REGISTERED AS Object Identifier of a Managed
  Object Class carried in CMISE
• Create, Delete, Set, Action, Get requests

51
PACKAGE Template

• ltpackage-labelgt Name of the package
• BEHAVIOUR describes complete behavior that is
  included in the package
• Effect of Opeartions upon a MO
• Specification Initial Value Mamaged Object (IVMO)
  selection criteria, if any
• ATTRIBUTES propertylist Operations permitted on
  an Attribute
• REPLACE WITH DEFAULT If the attribute has a
  default value that may be set by
• means of a Replace with default value operation
• DEFAULT VALUE ltvaluegt A default value that may
  be used when the Mo containing
• the package is instantiated or to be specified in
  REPLACE WITH DEFAULT operation
• INITIAL VALUE ltvaluegt A mandatory initial value
  to used for the attribute at create
• PERMITTED VALUES Range of possible values for
  the attribute
• REQUIRED VALUE Value(s) that the attribute is
  required to take (e.g for conformance)
• GET (CMISE GET) operation on the attribute
• REPLACE (CMISE SET) operation on the attribute
• GET-REPLACE Both CMISE GET SET operations
• ADD Add attribute member
• REMOVE Remove attribute member
• ADD-REMOVE ADD REMOVE

52
PACKAGE Template

• ATTRIBUTE ltparamter-labelgt Identify MO class
  specific error parameters associated
• 
  with management operations on the attribute
• ATTRIBUTE GROUPS ltgroup-labelgt Attribute Group
  templates in the package
• ATTRIBUTE GROUPS ,group-labelgt ltattribute-labelgt
  Group may be extended by
• ltattribute-labelgt
• ACTIONS ltaction-labelgt Action templates included
  in the package
• ACTIONS ltaction-label ltparameter labelgt MO
  class specific action information, or
• error parameters associated with the
  action
• NOTIFICATIONS ltnotification_labelgt Notification
  templates included in the package
• NTIFICATIONS ltparametr-labelgt MO class specific
  Notification information or error
• parameters associated with the
  notification

53
PARAMETER Template

• ltparameter-labelgt name of the PARAMETER template
• CONTEXT conext-type the context(s) (ACTION-INFO,
  ACTION-REPLY, EVENT-INFO,
• EVENT-REPLY, SPECIFIC-ERROR) in which the
  parameter is applicable
• synatx-or-attribute ASN.1 type of the parameter
  or an ATTRIBUTE template whose syntax is
• to be used
• REGISTERED AS Object Identifier of a parameter

54
NAME BINDING Template

• ltname-binding-labelgt Name of the template
• SUBORDINATE OBJECT CLASS ltclass-labelgt Managed
  object class whose instances may be named by
  instances of the object class defined by the
• NAMED BY SUPERIOR OBJECT CLASS construct
• NAMED BY SUPERIOR OBJECT CLASS ltclass-labelgt A
  MO classs whose instances may
• name instances of MO classes defined by
  SUBORDINATE OBJECT CLASS construct
• WITH ATTRIBUTE ltattribute-labelgt Attribute
  (Naming attribute) that shall be used to
• construct an RDN for a MO instance defined by
  SUBORDINATE OBJECT CLASS
• construct

• CREATE ltcreate-modifiergt Permission to create
  new instances of MO class referred by
• by SUBORDINATE OBJECT CLASS. Upon creation
  following options available
• WITH-REFERENCE-OBJECT If present, a reference
  managed object in CMISE
• CREATE request may be specified as the source of
  default values and choice of
• conditional packages
• WITH_AUTOMATIC_INSTANCE-NAMING If present, the
  Create request may omit to
• to specify the instance name of the new managed
  object

55
NAME BINDING Template

• DELETE ltdelete-modifiergt Present if it is
  permitted to delete MO class instances
• of SUBORDINATE OBJECT CLASS with the following
  options
• ONLY-IF-NO_CONTAINED-OBJECTS Operation
  successful only if there
• are no contained MO object instances
• DELETE-CONTAINED-OBJECTS Deletes contained
  objects
• CREATE, DELETE ltparameter-labelgt Specific error
  parameters associated with Create
• and Delete operations reported as CMISE
  processing failure
• REGISTERED AS Object Id of a Name Binding

56
ATTRIBUTE Template

• ltattribute-labelgt Name of the Attribute template
• DERIVED FROM ltattribute-labelgt definition
  derived from an existing attribute def.
• WITH ATTRIBUTE SYNTAX Present only if DERIVED
  FROM is absent. Identifies
• the ASN.1 data type of the attribute
• MATCHES FORDefines the type of test that may be
  applied to a attribute value as part
• of a CMISE filter construct. Options are
  EQUALITY, ORDERING,
• SUB_STRINGS, SET-COMPARISON, SET-INTERSECTION
• PARAMETER ltparameter-labelgt Allows parameters
  to be associated with attributes for
• the definition of processing failures
• REGISTERED AS Object id of anattribute

57
ATTRIBUTE GROUP Template

• group-label Name of a attribute group template
• GROUP ELEMENTS ltattribute-labelgt Attributes
  (each defined by an ATTRIBUTE
• template) that are members of the group
• FIXED indicates that the attribute is of fixed
  membership
• DESCRIPTION text explaining the semantics of the
  grouping

58
BEHAVIOUR Template

• ltbehaviour-definition-labelgt Name of a behavior
  template
• DEFINED AS text explaining the behavior of a MO
  or associated name bindings
• parameters, attributes, actions or notifications

59
ACTION Template

• action-label Name of am action template
• MODE CONFIRMED action shall operate only in
  confirmed mode
• PARAMETERS ltparameter-labelgt identifies action
  information, action reply
• parameters, or processing failures associated
  with Action Type

• WITH INFORMATION SYNTAX lttype referencegt ASN.1
  data type that is
• carried in Action Information parameter in CMISE
  Action request
• WITH REPLY SYNTAX lttype-referencegt ASNB.1 data
  type that is carried
• in Action Reply parameter in Action response

• REGISTERED AS Action Type id passed in CMISE
  Action request

60
NOTIFICATION Template

• ltnotification-labelgt Name of a Notification
  template
• PARAMETERS ltparameter labelgt Identifies event
  information or event reply
• parameters, or processing failures associated
  with the template
• WITH INFORMATION SYNTAX lttype-refgt ASN.1 data
  type carried in Event-info
• in CMISE Event-report
• AND ATTRIBUTE IDS ltfield-namegt
  ltattribute-labelgt field-name is a label defined
• within the lttype-refgt abstract syntax. The
  ltfiled-namegt data type carries the
• values of ltattribute-labelgt
• WITH REPLY SYNTAX lttype-refgt ASN.1 data type
  that carries Event reply
• information
• REGISTERED AS Event Type Id carried in CMISE
  Event report and reply

61
Common Management Information Service Element
(CMISE)

• Protocol for systems management in distributed
  environments
• Applicable to management of OSI resources
• Applicable to management of Telecommunications
  Network resources
• ITU X.710 (ISO 9595) specifies Common Management
  Information Service Definition
• ITU X,711 (ISO 9596) defines Common Management
  Information Protocol Definition

62
CMISE Manager-Agent Paradigm
Service Request
Agent
Manager
Service Response
Notifications
63
CMISE Services

• M_EVENT_REPORT confirmed/non-confirmed
• M_GET confirmed
• M-CANCEL-GET confirmed
• M_SET confirmed/non-confirmed
• M-ACTION confirmed/non-confirmed
• M-CREATE confirmed
• M-DELETE confirmed

64
CMISE Services and ROSE

• Remote Operations Service Element (ROSE) defines
  the following services and the
• associated APDUs (Application Protocol Data
  Units)
• RO-INVOKE service carried by ROIVapdu Invoke an
  Operation
• RO-RESULT service carried by RORSapdu Return a
  result in response to RO-INVKE
• RO-ERROR service carried by ROERapdu Return an
  error (unsuccessful operation
• to a RO-INVOKE
• RO-REJECT-U service carried by RORJapdu ROSE
  user rejects RO-INVOKE due to
• problem
• RO-REJECT-P Service used by ROSE only to
  signal protocol problems (e.g. bad pdu)
• CMISE services are mapped to the above ROSE APDUs
  with appropriate macro expansion
• totie together Arguments, results, Errors and
  linked operations

65
CMISE M-EVENT-REPORT Service

• M_EVENT-REPORT reports an asynchronous event from
  Agent toManager
• M-EVENT-REPORT request mapped to ROSE
• Request mapped to RO-INVOKE
• Response mapped to RO-RESULT
• Operation Errors discovered by Manager mapped to
  RO-ERROR
• Errors discovered by CMISE mapped to RO-REJECT-U
• M-EVENT-REPORT parameters
• Invoke id Distinguishes this operation from
  other operations that may be in progress
• Mode Confirmed/non-confirmed
• Managed Object class MO class that generated the
  event
• Managed object instance the MO instance that
  generated the event
• Event type Type of event
• Event time Optional Time of generation of the
  event
• Event information Optional Event Information
  whose type is sepcified by Event Type
• current Time Time when the response was
  generated coneyed via M_EVENT Response
• Event Reply Event Reply information conveyed by
  M-EVENT Response
• Errors Errors found by CMISE Manager conveyed in
  M_EVENT Response via RO-ERROR
• In the confirmed mode M_EVENT_REPORT response
  primitive mapped to
• RO-RESULT service

66
CMISE M_CREATE Service

• Service used to create a new managed obbject
  instance from Manager to Agent
• M_CREATE service mapped to ROSE services
• M_CREATE parameters
• Invoke Id To distinguish this operation from
  other operations
• Managed object class Object class whose instance
  has to be created
• Managed Object instance Optional Instance name
  (DN) that needs to be created in the MIB
• Superior Object Instance Optional Name of the
  Superior Object Instance in the MIB
• none as specified in the NAME BINDING Template
  with the construct
• WITH-AUTOMATIC-INSTANCE-NAMING The Agent
  assigns a name (DN) to
• the new object in the MIB
• Access Control Optional Information of
  unspecified form to determine access permissions
• for this request only. The default access
  permissions for all exchanges are
• specified at association establishment time as
  part of CMIP user info
• Reference object instance Optional an existing
  Object instance of the same class whose
• attribute values become the default values for
  those not specified in the attribute list
• the construct WITH-REFERENCE-OBJECT must be
  present in the associated
• NAME BINDING template for the Managed Object
  class

67
CMISE M_CREATE Service

• Attribute list Optional List of attributes and
  values to be assigned to the new
• object instance. These values override values
  from other sources
• Current time Response Generation time conveyed
  M_CREATE RESPONSE
• via RO-RESULT
• Errors Errors (e.g. no such reference object
  instance) found by service
• performer (CMISE Agent ). Returned by M_CREATE
  Response
• via RO-ERROR service
• CREATE RESPONSE returns a postive response via
  RO-RESULT

68
CMISE Managed Object Selection

• Instances of managed objects are hierarchically
  arranged as a tree in the MIB
• Managed object selection involves two components
  scoping and filtering
• Scoping identifies managed objects (MOs) to
  which a filter is to be applied with the
  folllowing
• constructs
• Base Managed Object Instance Indicates the root
  of the sub-tree in the MIB
• Scope Tree Traversal depth (Scope levels)
• Scope Levels
• Base Object alone (Default)
• first level only
• Individual levelN-th level subordinates of the
  base object (integer value)
• Base to Nth Level the base object and alll its
  subordinates down to and including the
• the nth level
• whole Sub-tree the base object and all its
  subordinates
• Filtering is a set of assertions about scoped
  objects
• Assertions can be grouped together with logical
  operators
• If the filter is successfule for a scoped object
  instance, the MO instance is selected for the
• associated operation
• Discuss an example

69
CMISE Linked Operations

• Specific CMISE operations (M_GET, M-SET,
  M-ACTION, and M-DELETE) can have
• multiple respnses. The responses are sent as
  linked replies

Manager M-GET Request Invoke Id 1 Linked Id
Nort Present
Agent
M-GET Response Invoke id 3 Link Id 1 MO data
M-GET Response Invoke id 4 Link Id 1 MO
data
M-GET Response Invoke id 1 LinkId NotPresent No
MO Data
70
CMISE M-GET Service

• Service Request from Manager to Agent to get
  infromation about a set of MO from the Agents
• MIB
• M-GET Service Parameters
• Invoe id To distiguish this operation from other
  opeartions
• Linked Id Used for Multiple responses
• Base Object Class Class of the Base Object for
  scoping
• Base Object Instance Instance of the Base Object
  to be used for scoping
• Scope Optional the scope level
• Filter Optional Filter construct
• Access Control Optional Access control
  Information only for this operation
• Synchronization Optional How to synchronize the
  operation across the selected object
• instances
• Atomic All selected Objects are checked to
  ascertain if they can perform the
• operation successfully. If not, then the
  operation is not performed at all
• Best Effort Operation performed on all
  lselected objects
• Attribute Identifier List Optional Set of
  attribute identifiers for which the attribute
  values
• are to returned. If omitted, all attribute Ids
  are assumed
• Managed Objct Class Optional Class of the
  Object whose attribute values are being
• returned in M_GET Response. Not specified if
  onlty the base object alone was

71
CMISE M-GET Service

• Managed Object Instance Optional Instance of
  the managed object whose values are
• being returned via M_GET Response. Not required
  if base object alone was specified
• Current time Time when the response was
  generated via M_GET Response
• Attribute List Set of Attribute Ids and Values
  returned via M_GET Response
• Errors Any errors found by the Agent conveyed by
  M_GET Response vi a RO-ERROR

72
CMISE M-CANCEL-GET Service

• Service requested to cancel a previously
  requested M-GET
• Service Parameters
• Invoke Id To distinguish this operation from
  other operations
• Get Invoke Id Invoke id of a previously issued
  M-GET
• Errors Any Error conditions to be returned by
  M-CANCEL-GET Response
• via RO-ERROR
• If successful, the Aent sends a negative M-GET
  Response containing
• Error operationCancelled via RO-ERROR
• Followed by M-CANCEL-GET Response

73
M_DELETE Service

• Service request to delete a set of MO instances
  from Manager to Agent
• Service Parameters same as M-GET with the
  semantics for M-DELETE

74
M-SET Service

• Service to request the modification of attribute
  values of a set of Managed Object Instances
• Service Parameters
• Modification List A set of modification
  specifications
• Attribute Id Id of the Attribute whose value is
  to be modified
• Attribute Value Value to be used in the
  modification of the attribute
• Modify Operator (Replace, Add, Remove., Set to
  Default)
• Other Parameters same as M-GET with the
  associated semantics for M-SET operation

75
M-ACTON Service

• Service request from Manager to Agent to perform
  a specific Action identified by Action Type
• Parameters
• Action Type Type of the Action identified by the
  Id of the Action Template
• Action Information Action Information
  specified by the WITH INFORMATION
• SYNTAX construct of the Action template
• Action Reply Action Reply information returned
  in the M-ACTION-RESPONSE
• identified by the WITH REPLY SYNTAX construct of
  the Action template
• Other Parameters same as M_GET with the
  appropriate semantics for M-ACTION

76
CMISE Functional Units

• CMISE Functional Units specify CMISE feature
  sets
• Kernel Functional Unit includes CMISE except
  those listed under Additional Functional units
• Additional Functional Units
• Multiple Object Selection FU (Scope
  Synchronization)
• Filter FU
• Multiple Reply FU (Linked-Reply feature)
• Extended service FU Presentation services other
  than P-DATA
• Cancel Get FU
• CMISE FUs indicated during ACSE Association
  establishment

77
CMISE Lab

• X/Open Management Protocol (XMP) is an X/Open
  interface for CMISE services
• implemented by HP OVDM product
• Run HP OVDM GUI utility ovdmref to look at the
  following XMP routines and their
• parameters
• mp_create_request
• mp-get-request
• mp-get-request