ASSIGNMENT 1

Ques1. TELECOMMUNICATION ARCHITECTURE

The telecommunication process requires interaction between a number of different functions, which can be
allocated to various networks - the physical transmission network - the logical transport network - the
intelligent services network (IN) - the telecommunications management network (TMN)

The architecture of the transmission and transport networks The Transmission Network contains the
physical means for transfer of information, i.e. telecommunications equipment and connecting transmission
media; typically switching matrices of switches and cross-connect systems, modems, muldexes and line
systems. The signal generating and signal using functions of terminal equipment can be considered to be
part of the transmission network. Fig. 1 a shows an example of a transmission network with digital
exchanges (DE), digital cross-connect systems (DXC) and connecting line systems (LS). The transmission
network connects the interfaces in the user terminals.

The Transport Network performs logical functions, such as network configuration and routing, and ensures
reliable transfer of information between service users, regardless of the information content. Routing or
configuration of the bit streams are initiated either by the TMN - in case of failures - or by the service
network if the traffic demands different bit rates. The transport network also connects the user terminals. In
fig. 1 b, a logical end-to-end connection is established between terminals over Access Nodes (AN) and
Transit Nodes (TN).

The purpose of the Service Network is to offer users a particular service. In the example in fig. 1 c, the user
initiates a service via a Service Switching Point (SSP) using signaling system No. 7 or D-channels of the
ISDN system. The service also needs data from a Feature Node (FN). The process is controlled by the
database of the Service Control Point (SCP). SCP is updated - when new services are introduced or existing
services changed - through the Service Management System (SMS) located in the network operator's
administrative Centre. The Telecommunications Management Network (TMN) connects the network
operators and administrators - via workstations (WS), operation systems (OS) and standardized Q-interfaces
- to the managed telecommunication equipment, as shown in fig. 1 d. System management covers
maintenance, performance monitoring, configuration, security and accounting. TMN serves as an overlay
network using the facilities of the transmission network or the signaling channels provided by the service
network. The relationship between TMN and IN is being studied by the CCITT and other standardization
bodies. Among the driving forces behind the continuing evolution of telecommunications networks are the
development of various technologies - miniaturization and the speeding up of processes at lower costs - and,
last but not least, customer demands for new services and their quality. The concepts underlying the rapid
evolution of the transmission and transport networks are - the definition of the Synchronous Digital
Hierarchy (SDH) by the CCITT, which is accepted worldwide, making an efficient transmission standard
available1 - the introduction of new transmission equipment, such as synchronous digital cross-connects
(SDXC), synchronous multiplexers (SMUX), fiber-optic synchronous line systems and flexible
multiplexers, permitting new network configurations and flexibility2 - the application of
Telecommunications
Management Networks (TMN), leading to standardized and centralized management of telecommunications
networks34 - the advent of Asynchronous Transfer Mode (ATM), which will be essential for flexible
broadband switching and transmission. Through synergistic effects, a combination of these concepts leads to
the transmission and transport mechanisms that will be used in the intelligent networks of the future.
QUES2.TELECOMMUNICATION MANAGEMENT LAYERS
 BML

SML

NML Network
OS

EML MD for EML

EML OS Network OS OS
MD
MD
NEL QA for
Network OS

Q-Adapter
Network Element

Assignment 2
Ques1. Management Information model.
1. Basic Concepts

Managed objects are abstractions of data processing and data communications resources for the
purposes of management... The design of systems management requires that an approach be adopted
that will allow the specifications to be standardized in a modular fashion and provide the extensibility
of the protocol and procedures. The information model makes use of object-oriented design principles
because they provide the above capabilities and provide for reuse of pieces of specification.

Managed objects are defined for the purpose of managing systems. Each managed system may contain
a Management Information Base (MIB). In the MIB, managed objects are used to represent the
resources that may be managed within the system. A MIB is the conceptual repository of the
management information with in an open system. It represents the resources in managed system that
has been externalized for communication with a managing system. They are externalized in the sense
that a managing system has knowledge of the MIB, not of the actual data structures of the managed
system's internal database; and the two may be vastly different. Resources that are not managed do not
need managed object representations. By managing this MIB, a managing system can control the
managed system's actual resources. This control includes the ability to retrieve information about the
resources and to provision, reconfigure, or inhibit the capabilities of the resources with in a managed
system.

2. Objects

A managed object is an abstraction of a physical or logical entity for the purpose of management. It
contains the specific information associated with the management of that physical or logical entity.

A managed object class defines the characteristics of a type of physical or logical resource. Instances
of a managed object class exist to represent specific instances of a resource. Therefore, a managed
object is an instance of a managed object class. The terms "object" and "object instance" are
synonymous.

Operations

Operations may be directed to manage objects and notifications maybe emitted from managed objects.
Operations and notifications apply across a managed object boundary and map onto underlying
communications services, which for the purposes of systems management are the CMIS services
defined in [ISO/IEC 9595].

All operations performed on a managed object are visible at the managed object boundary and can
succeed only if consistency constraints of the managed object are not violated. An operation definition
includes the direct effect of the operation on the managed object. In addition to the direct effects of an
operation on a managed object, which are defined by the operation, indirect effects may also occur as a
result of the relationships in the underlying resource.
There are two types of operations that may be directed to a managed object: attribute-oriented
operations and object-oriented operations . Notifications are information emitted from managed
objects upon an occurrence of an event.

Attribute-oriented operations are applied to the attributes of an object, and their impact is generally
confined to the modification of attribute values. The possible attribute-oriented operations are retrieve
(get) an attribute value, set an attribute value, replace an attribute value with the default value and, for
set-valued attributes, add and remove attribute values.

The operations that are valid for a particular attribute in a managed object are part of the package
definition that references that attribute .Operations to retrieve attribute values map onto the CMIS M-
GET service, while operations to set, replace with default, add and remove attribute values use the
CMIS M-SET service.

Object-oriented operations are applied to the object as a whole. The possible object-oriented
operations are create, delete, and action. The create and delete operations are used to create and delete
specific instances of a managed object class; however, managed objects also may be created or deleted
as side-effects of other normal resource operations. The create and delete operations use the CMIS M-
CREATE and M-DELETE services, respectively.

An action is defined to elicit a specific response that is not obtainable through the use of the other
operations. Action operations use the CMISM-ACTION service. An action defines an operation that
may be directed to a managed object to perform a specific operation. An action definition includes its
behavior (optional), whether it is always confirmed or not, the syntax of any information (if any) in the
action request or response, and any specific errors.

A notification defines information that may be sent when a managed object emits a notification as a
result of an event. A notification definition includes its behavior (optional), the syntax of any
information (if any)in the report or response, and any specific errors. Whether a notification is
confirmed or unconfirmed is implementation dependent but also may be configurable by a manager
(i.e., Event Forwarding Discriminator object class provides a mechanism [ISO/IEC 10164-5]).
Notifications use the CMISM-EVENT-REPORT service.

The syntax of the information in the request or response of action sand notifications is defined using
ASN.1 notation [CCITT X.208, ASN.1].It is possible to leave the syntax of these data fields as an open
type, such that the syntax is specified using parameters when defining a managed object class
containing the action or notification.

...An operation performed on a managed object can succeed only if the invoking managing system has
the access rights necessary to perform this operation, and consistency constraints are not violated.
...Consistency constraints are specified as a part of the behavior definition of the attribute or managed
object class definition. When performance of an operation, e.g. ,replacing an attribute value, would
violate a defined constraint, the operation is not performed and a "failure in processing" indication is
returned.
Ques 2. Management servicing and functions.

TMN Management Services

TMN-MSs are groups of specific TMN management functions to provide the management of
telecommunication equipment. They may be grouped into Operation Systems (OSs) in order to best
match the organizational requirements of the administration operating the TMN. A given TMN-MS
may be distributed over several OSs or one and more OSs may perform several TMN-MSs.

There are a number of specific areas covered by different TMN management services. Several areas
are chosen to be discussed.
A. Customer administration
B. Traffic management
C. Management of customer access
D. Common channel signaling system management
E. Staff work scheduling

A. Customer administration

This management activity requires the network operator to exchange management data and functions
required by the customers to offer a telecommunication service and to exchange with the network all
the customer-related management data and functions that the network needs to provide that service.
This could involve interactions which related to provisioning management, configuration
administration, fault administration, charging (billing) administration, complaints administration,
quality of service administration, traffic measurement administration, etc.

B. Traffic management

This deals with the management of traffic associated with circuit switched networks, for example,
Integrated Services Digital Network (ISDN) and Public Switched Telephone Network (PSTN), and
transmission networks.

The objective of traffic management is to enable as many calls as possible to be successfully

completed. This is done by maximizing the use of all available equipment and facilities in the traffic
situation. It is also responsible to supervise the performance of a network, and has to take action to
control the flow of the traffic and to optimize the utilization of the network capacity.

It will initially concern itself with the Network Element (NE), a digital exchange network element, to
ensure the specification of this service. It then collect traffic information from and send commands to
the NE so as to modify its operation or reconfigure the network. The NE may send information
periodically or on threshold triggering. The TMN-MS may change the threshold at which the NE sends
the traffic data or the periodic reports. Those data may be processed within the TMN-MS via OSs.
Thus the Digital exchange NE has to perform several functions so as to achieve the above tasks. It has
to collect traffic management information using an internal measurement sub-system, processes the
information and converts it to a recognized set of traffic management indicators, then transfer it to the
OSs. From the indicators, the OS should be able to obtain an overall view of the status of the Network.
The NE will later receive control information from the OS and executes appropriate controls to change
the traffic flow.

It is usual to take into account aspects of common channel signaling and traffic measurement during
the specification and processing of the traffic management information.

C. Management of customer access

This includes all the equipment which associated with the customer access involving multiplex
equipment, network terminating units etc, regardless of its bandwidth (narrow-band or broadband),
analogue or digital.

Management describes quite a number of tasks, configuration, failure monitoring, security and
network performance of any part or piece of equipment associated with the access. Separate
requirements resulting from circuit-switched or packet-switched environments must also be taken into
account.

Needs of management control facilities upon the customer access arises due to the complexity.
Customer access may be regarded as consisting of copper wires or optical fibers with complex
electronic equipment whose functions may need updating or altering by the network provider, instead
of merely consisted of copper wires and network terminating equipment.

D. Common channel signaling system (CCSS) management

This covers all the aspects concerned with the management of CCSSs. During the process of managing
a CCSS, several things outside of the sphere of the MS has to be considered as well. They are the
events and information outside the MS, also planning is needed.

It is necessary to have a network wide view of the availability of the signaling network and the
signaling traffic loading. The network wide view should at least contain a number of relevant
information such as, the configuration on the signaling network, the availability of each signaling link
set and its capacity, current loading of each link set, and indication of the initiation of internal flow
control procedures.

Those information will be used as a statistical measurements. They will be gathered from both inside
and outside of the signaling system concerned.

CCSS management also make use of the computer based tools which could contain information such
as a map of the network with all signaling points and Signaling Transfer Points (STPs), signaling
routes and their capacities, detection of the signaling link sets which requires additional capacity. Also
they could contain interconnection with transmission planning information to ensure the required
diversity of the transmission paths.
The management system should be able to manipulate signaling resources through a Human-Machine
Interface (HMI). Some types of information could be accessed and changed, these include changing
and adding routes, collecting statistics, controlling the signaling link states and reporting of failures.

E. Staff Work Scheduling

This management service has no direct influence on NEs. However the quality of telecommunication
services depends very much on the network operator's staff, and that effective staff work scheduling
helps to maintain the economic level of the staff effort. This is a management activity of the network
operator which aims at getting the right staff member to carry out the work. This is valid for OAM of
the NEs, maintenance and installation work to be done at the customers' premises, and also installation
and repair work to be done in the field, such as installing cables.

TMN MANAGEMENT FUNCTION

The TMN management function is associated with management functionality in a managed system. It
may be triggered by internal events of the managed system (for example, report alarm) or invoke by
the managing system. They are usually grouped into five functional areas:

1. Performance management

2. Fault (Maintenance) management

3. Configuration management

4. Accounting management

5. Security management

Performance management includes all activities necessary to maintain the short term customer view
of quality of service. It gathers statistical data for monitoring and controlling the effectiveness and
behaviors of the network, NE or equipment.

1. Performance monitoring (PM)

PM involves the collection of data relating the performance of the NE. It is designed to
measure the overall quality using monitored parameters and also to detect characteristic pattern
before the quality of signal drops below an acceptable level.

1. The Common function

NE sends current PM data to TMN on its request. It may be generated periodically by
the NE and sent to TMN whenever it demands or by parameter threshold triggering.
TMN directs the NE to start/stop the collection and to reset storage registers for PM
data.

2. Performance controlling (PC)

 1. The Common function
TMN makes NE to set up a schedule for reporting of PM data, to send the PM data
report schedule and to assign designated values to PM attributes. NE sends current PM
attributes to TMN on its request. In addition, TMN directs NE to change or to set the
PM parameter threshold, also to set up a schedule for the execution of QoS test calls
and sends the current QoS call schedule to TMN. NE reports the result of QoS test calls
to TMN whenever it demands or on a schedule basis. Besides that, TMN asks NE to
change or to set the attributes of QoS test calls, to start/stop sending test calls and sends
the current QoS test call attributes.

Fault (Maintenance) Management include all procedure necessary to handle

system alarm, correct and test falling equipment, and respond intelligently to customers complaints.

1. Alarm
TMN is able to monitor NE failures in near real time. Indication is made by the NE when a
failure occurs. TMN determines the nature and severity of the fault basing on the indication. It
may determine the effect of the fault on the services supported by the fault equipment in two
ways. The first one is that a data base within a TMN may interpret binary alarm indication
from the NE, which requires little of the NE beyond self-monitoring capability. The second is
that it may transmit self- explanatory messages to a TMN if the NE has sufficient intelligence,
but requires additional support of message syntax for the description of fault condition from
both NE and TMN.

2. Correction
Automatic restoration report from NE to TMN indicates a specific line, service, equipment or
system that has been switched as part of NE's protection procedures.

TMN requests NE to start/stop hot-standby procedures for system or service so as to let a

redundant unit to take over with minimum disruption to traffic.

Reload procedure involves a request from TMN to NE for reconstruction of a service or a

system from a particular dump record. A reload report is the reporting of a reloaded service or
system from a dump, from NE to TMN.

3. Testing
It can be done in two ways. The first way is that a TMN orders a NE to carry out analysis of
circuit or equipment characteristics, which is done entirely within the NE. Results are reported
to the TMN automatically and immediately or on a delayed basis. Another way is that the
analysis is done within the TMN. It asks the NE to provide access to the circuit or equipment
concerned and no more messages are exchanged with the NE.

Configuration Management covers activities such as installing equipment,

provisioning equipment, behaviors of network and modifying parameter.
It provides functions for control over, identify, collect data from and provide data to NEs.
 1. Provisioning
It consists of procedures need to bring an equipment into service, excluding installation. When
the unit is in service, supporting programs will be initialized with the TMN. Status of the unit,
for example, whether in service or not, may be controlled by provisioning functions.

Use of provisioning functions differs in different NEs. Frequent use of these functions is
required in digital switching and cross-connect equipment as circuits are put up and dropped.
While only one usage is usually required in small transmission elements.

2. Status and control of NE

TMN provides monitoring and controlling over the NE on request. A status check is usually
provided in conjunction with each control function so as to check that the resulting action has
taken place. These functions are corrective when dealing with faulty conditions.

Status and control functions form part of routine maintenance which is done on a periodic or
automatic basis. TMN will stop the operation of a faulty equipment and may rearrange
equipment or re-route traffic. It can also enable entering of proposed configuration to analyse
the feasibility of the design before its implementation.

Accounting Management includes the measurement and control of costs and customers billing.
It provides a function set which enable the use of the network service to be measured and determine
the cost of it. It also collects the accounting record and

1. Billing
Some NEs is used to determine charges to customer accounts and it will send to the OS within
TMN if it requires these data. To enable the maintaining of the record of billing, this type of
function needs highly efficient and redundant data transport. Processing must be carried out in
near real time for large number of customers.

Security Management is responsible for controlling access to customers, network data and
resources.
It is concerned not with the provision and use of encryption or authentication techniques
themselves but rather with their management, including reports concerning attempts to breach
system security. There are two important functions, first one is managing the security and
maintaining security audits. The other one is performing the network management task in a
secure way.
 ASSIGNMENT 3
Ques1.TMN INFORMATION MODEL
Much of the information presented in the models of M.3100 are based on concepts defined in G.803.
Through this recommendation, standard forms are provided for the definition of virtual objects within
the telecommunications system. The ever-popular Client/Server model is used as a paradigm for
describing the relationship between the layers of synchronous networks, with the client layer traffic
being carried over transport services provided by the Server Layer.

Two important types of transport entities, trails and connections, are used to transfer information
within the framework of the client and server layers. A trail consists of trail termination functions that
interact via a network connection. Connections, on the other hand, are used to transfer information
between connection points; multiple connections can be used to support a single trail within a layer.

There are several other components in the general framework defined by G.803. the objects include:

CP - connection point, this is the point at which the end of a single trail is bound to either
another trail or another connection.

TCP - Termination Connection Point (not Transmission Control Protocol). This is a special
case of a connection point where a trail termination and an adaptation function are bound.

Adaptation - provides a point of access between the client and server layers. This function
"defines the "server/client" association between the connection point and access points.

Bi-directional reference point - refers to a point in the network in which a pair of unidirectional
connections or trails are combined to provide full-duplex connections.
 Network connection - defined by G.803 as a "transport entity" formed by a series of
"connections between "termination connection points". This network connection can be used to
transfer client trail information.

AP - access point. Defined as a "reference point" where the output of an "adaptation" source
function is bound to an input of a "trail termination source" or the output of a "trail termination
sink" is bound to the input of an adaptation sink function." In simpler terms, each layer's access
point is the point at which a server layer terminates the supporting trail service.

MC - matrix connection. Models the connection within a subnetwork that consists of a

connection that is transferred through a matrix function. This matrix can either be a fixed
matrix (for example, a permanent circuit through some switching function, or dynamically, as
in the case of an automatically switched circuit.

M.3100 Objects

M.3100 takes the information developed to support the SDH models (in G.803), and adds several
additional managed object classes that provide a baseline for developing application specific models.
By using the M.3100 classes, integration of information models into the larger scale enterprise vision
is possible. As a "Generic Information Model," M.3100 provides generally useful object classes that
can be applied to support the TMN architecture. If, for example, you are developing a mega-switch
gizmo with proprietary gizmo circuits, plan on using M.3100 as a model for breaking down your
proprietary gizmo into the appropriate components. Through the classes defined in M.3100 uniform
mechanisms are provided to support fault, configuration, performance, security and accounting
management.

The M.3100 specification is organized into 6 "fragments" that combine to form the Generic
information model. There are both direct containment relationships between the fragments along with
associative peer relationships. The 6 fragments defined within M.3100 are:

Network Fragment: defines the relationship between a managed network and its related
trails, connections, and managed elements. In this case, a network fragment is shown to contain
all elements.

Managed Element: defines the components and relationships contained in a single

managed element. In this case, a managed element is shown to contain equipment (including
software), along with trail termination points.

Termination Point: The termination point fragment contains the types of terminations that a
single piece of managed equipment may contain. Both trail and connection termination points
are included in this fragment.

Transmission Fragment: Provides a different, non-equipment oriented view of

communications through a network. In this case, two forms of transmission entities are
defined, trails and connections. The relationships between these entities and references to their
relative termination points are included in this fragment. Termination points include
termination point sources, sinks and bi-directional termination points.

Cross Connection Fragment: helps in managing cross connect fabric topologies. In this
case, the cross connection fragment contains multipoint cross connections, cross connections,
generic termination points, and a pool of termination points.

Functional Area Fragment: defines the classes of objects contained within a managed
element to provide additional management services. Object classes contained in the functional
area fragment include: Management Operations Schedule, Logs (e.g., alarms, attribute value
changes, object creation and deletion records, state change records), alarm assignment profiles,
event forwarding discriminators and the current alarm summary control. Of these object
classes, with the exception of the Alarm Severity Assignment Profile, all are defined either in
X.721 or Q.821.

M.3100 provides a set of objects to identify network topologies from several perspectives, and
to provide the standard management functions. Figure 2 shows the inheritance relationship of
many of the main objects required to support the M.3100 functional fragments.
 The majority of the objects defined within M.3100 are self-evident in the context of the SDH
system architecture definitions.There are some interesting issues in developing systems that
implement these objects. For example, the termination point objects can be automatically
instantiated by the managed element, or on the direction of the element management layer.
Similarly, the establishment of associations between the termination points and their parent
connections and trails is a matter requiring distributed knowledge.

Ques2. Structure of Management Information(SMI)

The Structure of Management Information (SMI), described in detail in RFC 1155, is a framework that
describes the basic types of information that can be manipulated by SNMP. It provides a skeleton that
specifies the basic format and hierarchy of management data but does not describe the objects that can
be managed. Rather, it describes the building blocks from which managed objects are constructed.

A fundamental concept of SNMP is the notion of object identifiers. An object identifier (OID) is a tag
that allows a management entity to refer unambiguously to a particular object. Object identifiers are
allocated in a tree fashion. The value of the object identifier is a sequence of integers that refer to a
particular traversal of the object tree. ``Object identifier hierarchy'', shows a portion of the object
identifier hierarchy.

The root of the OID tree has no label. Currently, there are three children of the root, ccitt(0), iso(1),
and joint-iso-ccitt(2). The ISO node has many children, one of which is org(3), which is allocated for
international organizations. Under org(3) is the U.S. Department of Defense, dod(6), which has the
child internet(1).

The name { iso org dod internet } is a symbolic representation for the integer series 1.3.6.1. Both refer
to the object identifier of the Internet subtree. In practice, 1.3.6.1 can simply be referred to as
``internet''. The terms { iso org dod internet }, 1.3.6.1, and internet are all different ways of identifying
the same object. In SNMP PDUs, only the numeric sequences are used.

Object identifier hierarchy

To ensure that object identifiers are unique, each organization is responsible for a particular section of
the OID tree. Just as ISO and CCITT have responsibility for their portions, the Internet Activities
Board (IAB) has responsibility for the internet portion.

To allow vendors to support objects that may not be defined in the standard MIB, the IAB reserves a
portion of the OID tree for enterprises MIBs. This provides vendors with the flexibility they need.

The SMI defines basic data types that make it convenient to describe managed objects. These types
are: Integer, Octet_String, Object_Identifier, ipAddress, Counter, Gauge, TimeTicks, NetworkA
ddress, and Opaque.