Basic model of network management

Network administration requires the ability to monitor, check, probe, configure

and control the hardware and software components of a network. Likewise, the network administrator
must master the aspects that define a network, so that it is:

Scalable: the ability to extend the operating margin without losing quality.
Transparent: ability of a protocol to transmit data over the network in such a way that
transparent sea for those who are using the protocol.
Efficient: rational use of the devices available to achieve the objectives and
scheduled goals, with the minimum available resources and time.
Reliable: to ensure that each section of data sent from the source reaches the destination.

Main tasks of an administrator

1. Network availability monitoring: thanks to this, it is possible to detect failures in the network and thus
work immediately on its solution allowing for greater efficiency in the network.

2. Improve automation: optimize processes by ensuring they are carried out in a way
automatically through programming, increasing the quality of the results.

3. Monitor the response time: monitor the time taken to perform the processes with which
the administrator will be able to notice which processes are taking the most time, thus being able to do
necessary corrections in these to make them more efficient.

4. Security: indicates that a certain system is free from all danger, harm, or risk, and that it is,
certain way, infallible.

5. Redirect traffic: configure protocols according to the needs of the network,

so that packages travel by the best route.

6. Having the ability to reset: in case the network fails, the administrator must
configure it to recover from failures and resolve errors in the shortest time
possible.

7. Register users: the administrator is the only person who can register, deregister or
proporcionarle más accesos o menos a los usuarios de la red, esto de acuerdo con las tareas
performed by each employee of the company.
Network management considers

a. Control corporate resources to ensure they provide proper performance.

b. Control of complexity, controlling both the components and the number of users,
interfaces, protocols, providers, to keep track of the network.

c. Improve the service, users expect better services even as the network grows.

d. Balancing different needs, users must have various applications for a

specific support level.

e. Reduction of downtime, it is important to consider high availability of resources,

thanks to the redundant design itself.

f. Cost control, monitor and control the use of resources so that users are without
the need to increase costs.

Network management is subdivided into computer network management and management of

telecommunications networks (see Figure 3.1).
 Figure 3.1 Division of network administration.

The Administration of Computer Networks is a set of actions whose primary objective is

keep the network operational, efficient, and secure.

On the other hand, telecommunications network management provides management functions and
communications for the operation of the administration and maintenance of the networks
telecommunications and its services in a multi-vendor environment. The reason why it
develop the architecture TMN.

Network management architecture

Network management requires the ability to monitor, check, probe, configure

and control the hardware and software components of a network. For this, a requires.
architecture of network management systems consisting of the following elements (see
table 3.1):

Table 3.1 Elements and description of network management system architecture.

This infrastructure is the basis for the implementation of different network management models.
(see Figure 3.2)
 Figure 3.2 Network management infrastructure.

The OSI (International Organization for Standardization)

Normalization) created a committee to generate a model for the management of a network, this one
it consists of four sub-modules, with the purpose of having a structured work environment, as
is shown in Figure 3.3.

Figure 3.3 Network Management Model, proposed by OSI.

a. Organization model: is responsible for the description of the components of the

network management, that is: the administrator, the agent, etc., along with their relationships.

[Link] model: it is responsible for the structure and storage of information

network object management, which is stored in a database called MIB
(Management Information Base - Management Information Base).
 c. Communication model: is responsible for verifying the way data is communicated
administration between the agent and the administrator process.

[Link] model: it is who directs the network management applications, which

find in the NMS (Network Management System).

It is responsible for enabling interoperability between different network platforms and standards.
of network management.

3.2 TMN Model

A TMN (Telecommunications Management Network - Network Management)

Telecommunications is conceptually a separate network that interfaces with a network of
telecommunications at various different points" There were two basic motivations for the
development of TMN architecture:

One is the increasing heterogeneity in technology for network construction.

telecommunications and the coexistence of analog-digital networks.

Another offshoot of the greatest demands:

Possibility of introducing new services.

High quality of services.
Possibility of reorganizing networks.
Efficient work methods for operation.
Networks and competition among private companies.

Background

The study of the TMN concept began in 1985 by the ITU (International Telecommunications)
Union - International Telecommunication Union), through the study to develop a
a more comprehensive and standardized way to improve the elements of a network through a system
of network management. As a formal result of this process, Recommendation M.30 was obtained, which
was published in 1988.

M.30 summarizes the fundamental principles of TMN. Later, several versions were introduced and the
Recommendation M.30 has been replaced by recommendation M.3010.

Objectives

TMN primarily pursues two main objectives:

 Provide management and communication functions for operation, administration and
maintenance of a telecommunications network and provisioning of its services in a
multivendor environment.

Provide an organized network structure to achieve interconnection using a

standard architecture and standardized interfaces.

3.2.1 Functions and Architecture of a TMN

The functions and architecture of a TMN can be considered in various dimensions. Each
dimension is defined by existing or in-development standards. The recommendations M.3010 of
the ITU-T deals with:

Functions associated with TMN.

Aspect of TMN architectures.
Layered logical architecture of TMN.

The functions associated with a TMN are classified in terms of OSI management;
accordingly, five functional areas are defined, which are: systems function block
operations (Operations System Function: OSF), network element function block (Network
Element Function: NEF), workstation function block (Workstation Function: WSF),
mediation function block (Mediation Function: MF) and Q adapter function block (Q
Adaptor Function: QAF)

Regarding the general architecture of TMN, three basic aspects are considered in ITU-T.
M.3010:

1. Functional architecture of TMN: functional blocks and reference points between them. Each
one of which encompasses a subset of the functionalities necessary for TMN to be able to
fulfill the management objectives for which it was conceived.

2. Information architecture of TMN: definition of the information transmitted between the

functional blocks.

3. Physical architecture of TMN: structure and entities (elements and interfaces) of the TMN.
Show how the functional blocks of the Functional Architecture can be implemented in
various physical devices interconnected through interfaces.

The TMN defines the relationship between the basic functional blocks constituting the network through
standard interfaces. Introduces the concept of subnet control and is treated as a single entity
through the management application. (see Figure 3.4)
 Figure 3.4 Relationship between functional blocks.

The model is composed of:

a) Functional architecture

The functional architecture of TMN is based on a number of TMN function blocks. These
they represent the appropriate functions required by TMN to fulfill its general management function
of the network. These are actually executed by elements of the physical architecture of TMN.

Recommendation M.3010 defines five function blocks (see Figure 3.5):

1. Operations System Function Block (Operations System Function: OSF).

2. Network Element Function Block (Network Element Function: NEF).
3. Workstation Function Block (Workstation Function: WSF).
4. Mediation Function Block (Mediation Function: MF).
5. Q Adaptor Function Block (QAF).

Figure 3.5 TMN elements.

The data communication requirements of these function blocks are satisfied by the
data communication function (Data Communication Function: DCF) (see table 3.2)
 Table 3.2 Function of the blocks of the TMN functional architecture.

b) Physical architecture

Define how management functions can be implemented in physical teams. The physical architecture
from TMN describes the physical building blocks (physical elements) of a management system
red TMN and contains exact rules for its relationships. The related standard is the recommendation
CCITT/ITU-T M.3010.

The M.3010 defines the physical elements of TMN as follows:

Operations System (OS): It is responsible for managing the network.

controlling the operation of its elements. As for its implementation, the OS is
basically consisting of one or more processing centers, performing the task of gathering
information from the network elements and processing it according to the system functions
network management.
Q Adapter (Q Adapter: QA): They perform Q Adapter functions (QAFs). They achieve the
information exchange between the OS or the DCN, applying standard protocols, and the
potential non-standard NEs located in the network.
Workstation (Workstation: WS): It refers to the physical representation of interfaces.
man-machine interfaces through which operators can communicate with the
TMN.
Network Element (NE): They are basically telecommunications devices.
manageable located in the nodes of the network to be managed. They provide the functions
adequate in network operation, and can usually be identified by a simple address
by the operations system of the TMN.
Data Communication Network (DCN): The DCN is a network that
execute the data communication function (DCF). It transmits required messages for
execute management functions between the OS and the NEs. The information is exchanged through
the DCN, using standard protocols as established by the standard interfaces.
 Mediation Device (MD): They perform mediation functions (MFs).
They can adapt the information transferred between the OS or the DCN and those TMN elements.
compatible located on the network, which still requires appropriate operations (storage,
adaptation, filtering, etc.) to be executed on the exchanged data.
Q Adapter (Q Adapter: QA): They execute Q adapter functions (QAFs). They achieve the
information exchange between the OS or the DCN, applying standard protocols, and the
potential non-standard NEs located in the network.

c) Information architecture

The general characteristics of the TMN information model are discussed by the
Recommendations M.3010 and M.3100 of CCITT/ITU-T. The network management information model
TMN is largely supported by the OSI/CMIP network management model, the architecture of
transaction-oriented information, and uses the so-called agent/manager principle
(agent/manager).

The basic concepts used in the definition of TMN's information architecture are similar.
to those applied in SNMP and OSI/CMIP, they are:

Managed Object (Management Object: MO): MOs are abstractions of resources

physical or logical to be managed in order to monitor the operation of the network and to prevent
disorders in the operation of the network.
Agent: It is a system element towards which management commands are directed for
purposes of control, coordination, and monitoring. The agents carry out operations on the
objetos gestionados y retransmiten mensajes emitidos por los objetos gestionados hacia el gestor.
Manager: It is a system element whose task is to send management requirements.
towards the agents for control, coordination, and monitoring purposes, executing operations
about the agents with the help of those requirements and the reception of messages issued by
the objects managed and transmitted by the manager's agents.
Management Information Base (MIB): It is a base of
data that contains data belonging to the managed objects of the system.

d) TMN Logical Architecture by Levels

Includes one of TMN's best ideas: a model that shows how it can be structured
management according to different responsibilities.

According to TMN terminology, network management OSFs are divided into four layers.
Hierarchical. Each layer of the given hierarchy defines an appropriate group of management operations.
These layers are built one on top of the other; they and their appropriate operations are very
interrelated. (see Figure 3.6)
 Figure 3.6 Logical Architecture of TMN.

3.3 TOM Model

The Telecommunications Operations Map, abbreviated in English as Telecomunication

Operations Map was developed between 1995 and 1998 by the TMF (Telemanagement) organization.
Forum). In order to help telecommunications service providers automate their
business processes in an efficient manner, which is why a consortium of international companies was created
of communications, among whose objectives are included:

Establish an operational guide for the business processes.

Determine the type of information that should flow between processes.
Identify a realistic environment that supports the interconnection of support systems.
To promote the development of a market and products to integrate and automate processes of
telecommunications.

Thus, the TOM model was developed with the purpose of replacing the Telecommunications model.
Management Network (TMN) to meet the aforementioned objectives.

Structure

In the TOM model, the management functions of a telecommunications operator are grouped into
boxes, which represent groupings of related activities. (Figure 3.7)
 Figure 3.7 Diagram of the TOM model

3.4 eTOM Model

The Enhanced Telecom Operations Map, eTOM, for its acronym in English,
Enhanced Telecommunication Operations Map is a model that serves as a framework for reference.
business processes oriented towards the telecommunications sector. Describe and analyze all of the
processes empresariales necessary for the functioning of one company.

It aims to analyze the existing processes in an organization and also to develop

new processes.

The need to identify, control, and maintain all components of technologies is raised.
from the information.
Structure

The model starts at the business level, defining business processes and presenting them in areas.
At a conceptual level, it presents three main areas of processes: (see Figure 3.8)

Figure 3.8 Diagram of the eTOM model.

1. Strategy, Infrastructure, and Product: covers the management of planning and life cycles.
The objective is the processes related to planning.

2. Operations: focuses on the core of operations management.

3. Corporate administration: it deals with business support. Here the processes are concentrated.
that every company must have for its normal operation.

The following describes in detail each of the areas of the eTOM model:

The vertical sections of the area of Strategy, Infrastructure, and Product generally take care of
to direct and support the provision of products to customers. Its mission is compliance with the
expectations del client.

Each of its vertical sections is described in Table 3.3:

 Table 3.3 Description of the vertical sections of the Strategy, Infrastructure, and Product area of the eTOM model.

The four sections of functional support processes are represented at horizontal levels within.
from the area of Strategy, Infrastructure, and Product, which are described in table 3.4:

Table 3.4 Description of the horizontal sections of the Strategy, Infrastructure and Product area of the eTOM model.

The Operations area contains the vertical sections of the direct operations processes.
Compliance, Assurance and Billing, along with the section of Support processes and
Preparation. (Table 3.5)
 Table 3.5 Description of the vertical sections of the Operations area of the eTOM model.

The Operations area encompasses four horizontal sections: relationship management with the
client, service and operations management, resource management and management of the
relationships with suppliers and allies. (Table 3.6)

Tabla 3.6 Descripción de las secciones horizontales del área de Operaciones del modelo eTOM.

The Corporate Administration section involves knowledge of actions and

needs at the company level, unlike with the sections on Strategy, Infrastructure,
Product and Operations, which focus more on the needs of the customers.

The processes that constitute it become necessary for any company, as they are required for
to run the business and are critical to support customer processes. It also establishes strategies
and corporate directions, and provides guidelines and goals for the rest of the business.

It is composed of seven sections, which are described in table 3.7:

 Tabla 3.7 Descripción de las secciones del área de Administración corporativa del modelo eTOM.

Advantages of implementing the model in Network Management

It allows the establishment of a common business framework for telecommunications companies.

Provide common definitions to describe the processes of a service provider.
telecommunications operator.
Agreements on the basic information required to carry out each process.
Provide a process framework that allows identifying which processes and interfaces are more
feasible to integrate, automate, and standardize.

Disadvantage of implementing the model in Network Management

It is a method that requires a lot of preparation to implement it, as it goes

through various levels.
 3.5 Definition of network management protocols

A network protocol is a set of conventions and rules for sending and receiving information.
through a network. Such conventions regulate the content, the format of the data, the speed of
sending and receiving and error management over the network.

The following defines three of the most used and important protocols in management
networks.

a) SNMP (Simple Network Management Protocol).

The first protocol that was used was SNMP [RFC 1157]. It was developed in the early days of the Internet.
for the administration of TCP/IP networks and originally as a short-term solution for the
problems of network monitoring.

In the 1980s, the new SNMP protocol emerged, which incorporated many of the functions of
original (which is still in use) and included new features that improved its shortcomings.

It is an application layer protocol that is part of the TCP/IP protocol suite.

Internet. Figure 3.9 summarizes the evolution of SNMP:

Figure 3.9
Evolution of SNMP over time.

Characteristics

It is a highly flexible protocol that allows for great extensibility to all types of networks.

The manager periodically asks the agent for information about the resources we manage, it is
the manager is responsible for monitoring the resources.

Being a protocol based on UDP/IP, it does not guarantee the arrival of messages.

The client program (called the network manager) creates virtual connections to a server program.
(called the SNMP agent).

Port 161 is used to send and receive messages, the trap messages sent by the agents.
are received at the port 162.
SNMP Architecture

Implicit in the architecture model of SNMP is a collection of network management stations.

and network elements. The stations run management applications that monitor and
they control the network elements. Network elements are devices such as hosts, gateways,
terminal servers, and similar ones, that have management agents to perform the functions of
network management requested by the network management stations.

SNMP is used to transmit management information between the management stations and the
agents in the network elements.

SNMP Requests (see Figure 3.10)

Figure 3.10 SNMP Requests

Advantages

The main advantage is its simplicity, which greatly reduces development costs and time.
applications, as well as their subsequent updates.
SNMP has the support of several commercial multi-vendor network management platforms.
like HP's OpenView, Sun Microsystems' SunNet, or IBM's NetView.
It is a market standard.
Useful model for accessing network management data.
Efficient access and organization of managed data.
Independence of the communication environment.

Disadvantages
 Consumes more bandwidth than CMIP in extended network environments.
In its original version, it does not allow for the efficient transfer of large amounts of data.
It has a very high vulnerability to various security issues, for example, modification of
information and alteration of the message sequence.
Limitations in the information retrieval mechanism.
Limitations of data modeling capabilities: static MIB, difficult data correlation,
Modeling of complex systems.

b) CMIP (Common Management Information Protocol - Management Protocol)

common information

Alternatively, the CMIP was also developed as part of the work of the OSI and the Committee
Advisory International of Telephony y Telecommunications (CCITT).

CMIP [RFC 1189] was designed with SNMP in mind, addressing the errors and faults that
it had SNMP and became a larger and more detailed network manager. Its design is similar to SNMP for
PDUs (Protocol Data Units) are used as variables to monitor the network.

The CMIP series consists of six protocols, CMISE ISO 9595/9596, ACSE ISO 8649/8650,
ROSE ISO DIS 9072-1/2, ISO Presentation, ISO Session and ISO Transport.

Characteristics of CMIP

It is a network management protocol implemented over the Network Interconnection model.

Open OSI that has been standardized by ISO. Working on layer seven (Application).
It has a network management architecture that provides a way for control information and
maintenance can be exchanged between a manager and a remote element of
red.
Define a peer-to-peer relationship between the manager and the agent including what refers to the
establishment and closure of connection, and to the management information address.
Requires a large amount of memory and CPU capacity.
Generate long headers in the messages.
Difficult specifications to carry out and tedious to implement in applications.
Communication with agents oriented to connection.
Distributed operating structure.
Allows hierarchy of operating systems.
Ensure that messages reach their destination.
The agent is responsible for monitoring the resources.

Architecture CMIP

Specifically, CMIP offers a transport mechanism in the form of a question-answer service.

(see Figure 3.11) for the seven layers of the OSI model.
 Figure 3.11 Operation of CMIP.

CMIP is essentially composed of the following two components:

1. Systems Management Application Entity (SMAE–Systems Management Application

Entity):

Application level entity responsible for information exchange management with SMEs
from other nodes, especially with the system that acts as the network control center.

A standardized protocol (CMIP) is used for this function:

Level Management Entity (LME): provides functions

specific management of each layer of the OSI tower.
Management Information Base (MIB).

At the same time, the system management application entity, SMAE, presents the following division:

General purpose (designed to be useful in many applications):

oACSE (Association Control Service Element)

Association): is responsible for carrying out the initial negotiation in order to decide whether to
can establish a data connection and make it available for communication.
functional unit supports information exchange by supporting authentication
during the establishment of the association. The second functional unit supports the
negotiation of the context of application during the establishment of the partnership.

oROSE (Remote Operations Service Element–Service Operation Element)

Remote): controls and supervises the interactions between remote entities of a
 application, where those interactions can be modeled and supported as
remote operations.

Specific for system management:

oSMASE (System Management Application Service Element - Service Element)

of System Management Application): implements basic management functions in the
areas of fault management, costs, configuration, performance, and security. Provides
services to the network manager and management applications.

oCMISE (Common Management Information Service Element - Common Element)

Management Information Service): is responsible for the generation of
basic standard requirements and message processing of
response according to lo defined for the CMIS.

Through CMISE (Common Management Information Service Element - Information

Common Management Information Protocol (CMIP) provides three types of service:
. Data management: used by the manager to request and alter information from the
agent resources.
. Incident report: used by the agent to inform the manager about various
events of interest.
. Direct control: used by the manager to request the execution of various
actions on the agent.

FTAM (File Transfer Access and Management)

Files): is responsible for organizing and managing access to files for application processes.
Offers file transfer services between the client and the server.

2. CMIS (Common Management Information Services)

Administration): refers to the set of services provided by the architecture of
OSI management which define its implementation in the CMIP protocol and are invoked
through a set of instructions related to one or more objects of the MIB as
see in table 3.8:
 Table 3.8 CMIS Instructions.

Once each of the elements of CMIP has been explained, the following diagram can be obtained that
shows the different elements that make up the CMIP protocol (Figure 3.12):
 Figure 3.12 Protocols that integrate CMIP

The seventh layer protocol (application) used by OSI management is the common protocol of
management information (Common Management Information Protocol: CMIP). In an environment of
management based on the OSI/CMIP model, the user application process (whose operation is
based on the manager/agent principle) is provided with the common management information service
(Common Management Information Service: CMIS) based on a program interface of
application (API) by the so-called application entity for systems management (Systems
Management Application Entity: SMAE), which is implemented in the seventh layer (Application)
delete model of seven layers OSI.

The OSI management model defines managed systems and management systems.
these have the following characteristics:

Each communication node must have a management information base (MIB).

An Application Process of the Administration System (SMAP - systems management)

application process) provides the interface with the information shared by the MIB. The
SMAPs communicate with other SMAPs through the network.
 An Application Entity of the Administration System (SMAE) supports communication of
The SMAP and SMAEs use CMIP to exchange data between nodes.

CMIP defines the methodology for designing the network management system and the
interface specifications are indicated in CMIS (Content Management Interoperability Services)
Common Administration.

Advantages

Not only can management information be sent to or from a terminal, but it is also possible
develop tasks that would be impossible under SNMP.

CMIP solves several issues of SNMP. For example, it includes devices of

security management that supports authorizations, access control, passwords, among others.

CMIP, by operating in connected mode, offers greater security than SNMP.

Disadvantages

There are so many variables in CMIP that only the most skilled programmers are capable of
to bring out all their potential. Their variables are too complex.

For the user of the management tools, CMIP has as its main disadvantage requiring
about ten times more network resources than SNMP.

The implementation of OSI protocols on routers and management platforms is very expensive.

c) CORBA (Common Object Request Broker Architecture - Common Architecture of Intermediaries)

in Requests a Objects)

CORBA was introduced in 1991 and standardized by the OMG (Object Management Group–Group
of Object Management), the largest consortium in the software industry and defines the IDL Interface
Definition Language - Interface Description Language and APIs (Application Programming)
Interfaces - Application Programming Interfaces that enable interaction between objects
following a model client/server.

CORBA is basically a distributed programming architecture designed to support objects.

regardless of its location within a network machine. o
Characteristics

Communication with agents is oriented towards connection.

The protocol ensures that messages reach their destination.
The fact that it is an event-driven management means that:
The agent notifies the event manager of the information regarding the resources.
managed.
The agent is responsible for monitoring resources.
There is less traffic management.
Present more complex agents.
Define:
The interface of objects (IDL).
How they communicate with each other (IIOP, Internet Inter ORB Protocol–Interoperability between
ORB).
Object services.
CORBA deals with Interfaces, not with the implementation of the objects.
Interoperability between distributed heterogeneous objects. (Distributed applications)
Objects are classified according to their nature, being grouped within an ORB (Object Request)
Broker–Request Intermediary for Objects.

Architecture

CORBA is made up of several main elements, which are explained in

continuation:

1. ORB (Object Request Brokers - Object Request Intermediary): it is the core of

Any CORBA implementation transmits the messages exchanged between client and server.
(Figure 3.13), therefore they deal with:

Channel communications between local and remote objects.

Package the parameters that the client passes to the remote method and the result that the method
returns to the client.
Locate the remote object based on a reference.
 Figure 3.13 Object Request Middleware.

The ORB, Object Request Broker, provides various services, which are used
due to the implementations of the objects. Since the ORB does not know the details of the
fundamental implementations of objects. An 'object adapter' (The object adapter is responsible for
to convert one interface into another interface that the client expects, which allows for it to be dealt with even though it is about
different interfaces can work together, which otherwise could not be done due to their
incompatible interfaces) maps generic models to implementations, thus achieving that the
implementations of the objects access the services provided by it.

Table 3.9 mentions and describes each of the services provided by the ORB:
 Table 3.9 Services provided by the ORB

2. IDL (Interface Definition Language): is a language for interface description.

programming designed exclusively to specify the interfaces that clients will use.

The task of an IDL is to harmonize different languages in the format and size of their
specifications, establishing a contract between client and server indicating which services are going to
be accessible to the client from the server, (see Figure 3.14).

Figure 3.14 Function of an IDL.

3. IIOP (Internet Inter ORB Protocol - Interoperability between ORBs): CORBA is neutral
regarding the network protocol used to communicate the client with the server. For this, it specifies
the GIOP (General Inter ORB Protocol) that defines communication
between different ORBs. For TCP/IP networks, an instance of GIOP known as
IIOP. Thanks to the IIOP, it is possible for objects that use ORBs from different manufacturers to
interoperate on networks like the Internet. (see Figure 3.15)

Figure 3.15 Function of the IIOP.

Once the elements of CORBA have been explained one by one, the following functional diagram is generated.
with each of these elements, thus allowing for a better understanding of the process that is carried out (see
Figure 3.16)

Figure 3.16 Conceptual diagram of CORBA.

The following shows the previous diagram broken down (Figure 3.17):
 Figure 3.17 Extended conceptual diagram of CORBA.

Where:

Skeleton: It is the element responsible for communication with the client.

Client stub: refers to the local representative of the remote object and is responsible for the
communication with the remote object.

As observed in figure 3.17, there is an interface between client and server applications. A
Interface Definition Language (IDL) has been specifically defined for CORBA. Any
An object can be a client, a server, or both. For descriptive purposes, CORBA uses the model
Client/Server.

What CORBA specifically does is specify the middleware services that will be used by
the applications (objects).

The architecture of CORBA has some characteristics, which are listed below:

CORBA defines an architecture for distributed objects.

The basic paradigm of CORBA is a request for services from distributed objects.
The services that an object provides are given by its interface. Interfaces are defined in the
Object Management Group (OMG) Interface Definition Language (IDL).
Distributed objects are identified by object references, which are defined by
IDL interfaces.
A client has a reference to a distributed object. The reference to the object is given by a
interface.
The ORB (Object Request Broker) sends the request to the object and returns any of the results.
to the client.
Advantages

Standardized, multiple implementations (not dependent on the manufacturer).

The specifications are adopted by consensus.
Good infrastructure for building distributed applications.
It allows applications to communicate with each other, no matter where they are located and how.
have been developed.
Application layering separates interface and implementation, and also creates transparency of
localization through the ORB :
Of objects: the invocation is always done locally.
Of the network: the ORB manages it.
Activation: the servers activate automatically.
It is independent of the language: client and server objects are implemented in any
language (of the supported ones).
Server replication.
Distribution of computational load.
Code reuse.
CORBA is more powerful than SNMP and less complex than CMIP. Additionally, this adds the advantage that
It assumes its proximity to C++ and Java, two widely used languages.

Disadvantages

It's not the simplest technology to use.

Specifications take time to develop, and consequently, implementations take time to
go to market.
More complex and heavier technology.
New challenges: management of concurrent access and security.
The greatest difficulty that the integration of CORBA presents with traditional systems
management is the object model.