AIRCC PUBLISHING CORPORATION
New Proposed Architecture For Q3 Interface To Manage IP-Based Networks
Department of Electrical Engineering and Information Technology,
Iranian Research Organization for Science and Technology (IROST), Tehran, Iran
This paper presents a new architecture of Q3 interface to combine OSI and Internet management protocols CMIP and SNMP with union management protocol in Telecommunication Management Network (TMN). To manage both OSI and IP-based networks, new proposed sub-layer is added between upper layers (SNMP and CMIP) and lower layers stack protocols such that with use of this sub-layer the TMN is able to communicate data between CMIP and SNMP with OSI and TCP/UDP/IP. Results of our simulation are shown that our new architecture named SUL (Sub-layer between Upper and Lower layers) has better performance than CMIP with 12.5% improvement in M-Get and M-Set services and 25% in M-Event Report service. Also SUL architecture performance will overcome to SNMP with 125% in M-Get and M-Set services and 66% in M-Event Report service. Usage of Q3 interface in telecommunication management network will improve the performance of instruction interchange approximately 26.6% in comparison to ordinary telecommunication.
Transmission Control Protocol, Internet Protocol, User Datagram Protocol, Simple Network Management Protocol, Common Management Information Protocol.
Nowadays usage of computer networks is growing up in different applications. Further, the network architectures are very complex and diverse. With this growth of computer networks, requirement for a high level of service and performance is necessary. It is important to capable to propose a union management architecture, which covers a range of services, protocols and geographical borders. Reference  examines such network management infrastructures and addresses key issues such as TCP/IP network management, as well as issues pertaining to TMN, Telecommunications Information Networking Architecture (TINA), Telco and Corporate networks also further examines state-of-the-art technologies such as: managed objects, SNMPv3, CMIP, Q3 interfaces, TMN (Telecommunications Network Management), TINA and policy-based management.
Management of networks has related to some activities like as design, presentation and control of network resources. Because of variety of network resources, management of them is complicated. As reference , internet is working based on Simple Network Management Protocol (SNMP) that is designed to manage the network simply, while management protocol named Common Management Information Protocol (CMIP) is designed for managing the OSI model. There are some advantages for SNMP like as simplicity and fast run time of it. Therefore usage of SNMP grows up rapidly. For implementation of CMIP and SNMP, always there are difficulties such as implementation of CMIP over TCP/UDP/IP (CMOT) and SNMP over OSI . Because of networks variety, there are different private interfaces in them, thus to manage each private network, different interfaces is required to operate the protocols in these networks. Usage of internet in the worldwide is grown up, therefore for information interchange, internet mode profile against connection oriented and connectionless mode profiles will use as a global method in the world, which it consists of TMN .
To clarify the duty scope of each part of TMN, management architecture with standard connection interface should be used. Therefore standard institute ITU-T declared first standard for TMN in 1985. TMN may be considered as a concept in the discrete network, which has some connections at different points. These connections are shown in figure 1 . According to figure 1, telecommunication network has connection points with TMN at switches and transmission systems. Table 1 shows the required recommendation of the protocols which implement internet profile in each layer .
Figure 1. Relation between TMN and telecommunication network.
Table 1. Internet profile protocols in each layer with their recommendations
Most producers of telecommunication equipment currently are substituting their profiles with internet mode profile, for compatibility with data transmission systems in the base of TCP/IP. SNMP has been designed for all-purpose management protocols. The main point in the SNMP design is simplification of management operations as much as possible, therefore usage of it on each inter-network system has been successful and its operation will not stop easily. Although this SNMP has an advantage of simplicity in network management, it has some weakness such as this protocol has not powerful functions. Figure 2 shows the management network model for TCP/UDP/IP networks [5, 7].
Figure 2. Manager-Agent model for TCP/UDP/IP networks.
The components of management model are Manger entity, Agent entity, Management Information Base (MIB) and Management Protocol between two entities (SNMP). Design of Management protocol for the simple network should be such that it contains application levels. For implementation of SNMP at fourth layer of network, User Datagram Protocol (UDP) will use. UDP is a connectionless protocol and SNMP will sit over UDP, hence SNMP is also connectionless. Manager entity may send three management messages towards the agent entity according to the conditions which these messages are Get Request, Get Next Request and Set Request. Agent entity will response to these messages with Get Response service. Figure 3 shows SNMP architecture .
Figure 3. SNMP architecture.
OSI management structure is similar to SNMP and its components are manager entity, agent (managed) entity, management connection protocol CMIP and Management information base [5, 8]. CMIP characteristic implicates a precise protocol that includes connect, disconnect and sending management messages.
Figure 4 shows network layers of CMIP with details of application layer which are System Management Application Service Element (SMASE), Common Management Information Service Element (CMISE), Association Control Service Element (ACSE) and Remote Operation Service Element (ROSE). User will use the ACSE element to connect and disconnect the link. At CMIP two condition of connection-oriented and connectionless have been considered.
SMASE element includes some System Management Functions (SMF) and its structure is different in comparison with other elements. SMASE element doesn’t have clear rules and standard. Some samples of these functions are: Alarm report, Alarm declaration, Alarm abstracting and etc.
ROSE functional element will use to send a request toward the remote system and receive its response. In spite of SMASE element, in Rose element there is a standard structure for sending request and receiving its response.
Figure 4. Management structure of network layers at CMIP.
CMISE element provides services and protocols to better clarify the request and its response structure in cooperation with ROSE element. With usage of the services and protocols of CMISE element, all management information will pass to the ROSE functional element and the result will send. Different models could implement on the IP network protocol [9, 10] but in this paper we focus on the increasing performance of IP-based networks.
In the recent years some improvement is carried out of the network architecture named Next Generation Network (NGN) architecture. In Reference  several end-to-end Quality of Service (QOS) for NGN (called NGN QOS) are proposed that are
Current network management technologies follow two approaches: ITU-T’s recommendations for TMN and IETF’s SNMP that favours IP networks. The applications based on these methods are specifically targeted at the variety of independent networks. These networks are Public Switched Telephone Network (PSTN), the Public Switched Data Network (PSDN), the Public Land Mobile Network (PLMN), the Wireless Local Area Network (WLAN), and etc. All of these networks will be integrated into an infrastructure with single IP that will refer as the NGN in the near future. In reference  some emerging methods towards management of network in NGN are proposed.
The simulation for telecommunication switches is implemented in Iranian Telecommunication Research Center (ITRC). With using other functionalities of telecommunication management network in association with Q3 interface program, we would be able to configure our network in the optimal condition .
2. Description of TMN
In TMN there are three different architectures. In this section these architectures will describe briefly.
2.1. Functional Architecture of TMN
In this architecture, five types of different functional architecture are defined which in implementation of TMN, all of them are not require. Figure 5 shows different types of functional blocks.
For description of the functional blocks in functional architecture of TMN, reference points will use. Therefore there are five sets of reference points. From these five reference points, three of them Q, F and X will define in TMN recommendation completely but two other reference points M and G are placed in the outside of TMN environment. In figure 6 reference points and their functional blocks are shown. At continuation of this subsection, functional blocks of TMN will describe briefly.
Figure 5. Functional Blocks of TMN.
OSF Operations Systems Function
MF Mediation Function
WSF WorkStation Function
NEF Network Element Function
QAF Q Adaptor Function
The TMN functional boundary
Figure 6. Different reference points in TMN.
2.2. Information Architecture of TMN
This architecture will discuss about interchange information structure between manager and agent. These information will use for management of information resources. Figure 7 shows the common schematic of relationship between two network management systems. Each management system includes manager, agent and information resources.
Figure 7. Common structure between manager, agent and information resources.
2.3. Physical Architecture of TMN
In physical architecture of TMN, the implementation platform of TMN functional block with physical equipment will describe. Structural blocks usually implement functional blocks of their names. Table 2 shows functional and structural blocks relation .
Table 2. Relation between functional and structural blocks
O*: May be exist if OSF and MF exist
3. Q3 Interface
In TMN, there are four different communication interfaces which are shown in table 3. As shown in table 3, Q3 interface includes different connections in TMN environment. Although Q3 interface uses to interact between different system functions but type of interchanged management information is different. The applications of Q3 interface in TMN are listed in front of Q3 in the table 3 which are between OS and NE, MD and NE, OS and OS in a TMN environment.
Table 3. Applications of different TMN interfaces
For Q3 interface, three different application classes are defined according to its requirements as below:
3.1 Upper Layers of Q3 Interface
In this section necessary concept of upper layers protocol requirements will introduce, then according to the functions which supported with these layers, different services have defined .
3.1.1 Functional Unit
Functional unit is a technique to group the services into the intended sets. Based on services type with use of functional unit, interchange of information will carry out.
3.1.2 Application Service Element (ASE)
In this element, specified function of application layer will carry out. ASEs may be utilized in different applications. When several ASEs are used at application layer, it is necessary to coordinate them which in this situation, coordination unit is necessary that includes functions to organize between ASEs.
Application Service Element consists of Remote Operation Service Element (ROSE), Association Control Service Element (ACSE), System Management Application Service Element (SMASE) and Common Management Information Service Element (CMISE).
184.108.40.206 ROSE Functional Unit
After connection establishment, with use of remote operation protocols, management information must be send to destination. Then destination with these protocols will send a response to the source. These requests and receiving related response will carry out with four services format in ROSE functional unit. These services are RO-INVOKE, RO-RESULT, RO-ERROR and RO-REJECT.
To send initial request, the RO-INVOKE service will use. To send positive response to request from side of receiver, RO-RESULT service will utilize. For sending negative response to the request from side of receiver, RO -ERROR service will employ. To reject each of three services RO-INVOKE, RO-RESULT and RO-ERROR, the service RO-REJECT will use.
220.127.116.11 ACSE Functional Unit
ACSE functional unit will employ for connection-oriented services. This functional unit uses to establish and release the connection. The ACSE has four services which these services are A-Associate, A-Release, A-Abort and A-P-Abort.
A-Associate service will use for connection establishment. A-Release service is for gracefully disconnection. A-Abort service uses for suddenly disconnection by user of ACSE and A-P-Abort will utilize to suddenly disconnection by the provider (ACSE). Abstractly, ACSE services have a task of connection establishment and disconnection. Data transmission will carry out with services of other entities.
18.104.22.168 SMASE Functional Unit
For SMASE there is not clear protocol and standard in the implementation. This functional unit has several system management functions. These functions will employ for more clearance and transparency of information and parameters of CMISE. Hence SMASE in cooperation with CMISE will deliver complete information to ROSE .
22.214.171.124 CMISE Functional Unit
CMISE will utilize for common management information transmission between OS and NE. With use of services and protocols of CMISE, all of the common management information will transfer to ROSE unit and this information will send as a request or response.
3.1.3 Q3 Interface with TCP Protocol
TCP is a connection-oriented protocol that has a few restrictions for lower layers for secure data stream transmission. Network layers schematic of TCP protocol is shown in Table 4.
Table 4. Network layers of TCP/IP protocol
As shown in table 4, TCP layer is seated on the IP. Because of the IP layer usage, TCP layer will able to send and receive information with fragments of different length . One of the main features of the Internet Protocol is fragmentation of the TCP packets in the source and adhesive the fragments together in the destination. Also IP uses to transmit data and deliver it to the destination in several networks and gateways based on priority and security.
To implement TCP over IP, some parameters such as reliability, data stream control, multiplexing, congestion control, type of service, data communication, priority and security must be considered .
3.1.4 TCP/ (Application or User) Interface
The application layer at Q3 interface could connect to the network via TCP. TCP performs ACSE functional unit instructions and return their answers. All implementation of TCP has a minimum set of services to implement such as Open, Send, Receive¸ Close, Status, and Abort. Task of necessary services is as table 5 .
Table 5. TCP services
3.2 OSI Model versus TCP/IP Model
Table 6 shows the network layers of OSI and TCP/IP reference models. At TCP model, session and presentation layers are not exist and their works will carry out by transport and application layers respectively. Although both reference models have the application layer, but their services are different.
Transport layer at TCP/IP model, provide two standard protocol which named TCP and UDP. Network layer in the OSI model like as other models provides both connection-oriented and connectionless services while internet layer at TCP/IP model has only connectionless service. Connectionless Network Protocol (CLNP) at OSI model is like as IP protocol in performance and only its difference is that CLNP protocol has a variable address length while IP has a fixed address length . Transport layer of TCP/IP doesn’t have any restriction on the lower layers of this protocol but host should be capable to connect to the network and send its data with use of IP packet protocols.
Table 6. Comparison between OSI and TCP/IP models
3.3 Comparison CMIP with SNMP
CMIP and SNMP, each of them has some advantages and weaknesses. Selection one of these protocols depends on the many parameters. Simplicity in the design is the main advantage of SNMP. Also when the communicated messages between manager and agent entities are low, SNMP will utilize. Low security is the main weakness of SNMP that recently is going to be better in the new versions. Because of using connectionless services in the transport layer, agent entity will not receive acknowledge, therefore it cannot sure that its alarm report reached to manager entity. Therefore when there is too much management information to communicate, the network traffic load rises and might be management information lost.
On the other hand, to compensate the lacks of SNMP, CMIP has designed and it can be used for lager networks. Object-oriented model will use to design and implement SNMP . The main advantage of CMIP is its ability to define the techniques to cover manual control, security and filtering of the management information. The main weakness of CMIP is resource occupation time which is more than SNMP. Table 7 summarize the list of the CMIP and SNMP services.
Table 7. CMIP and SNMP services
Regards to client-server property in TCP/IP protocol and using TCP/IP at lower layers of Q3 interface; implemented software has a client-server property. TCP/IP protocol is connection-oriented; therefore when one client connects to the server, a portion of server time will allocate to receive information from client, even if client sends its information with short time gap. Hence during the answering or listening of server to the client, other requests of clients to the server must be queued until connection between a client and server released and server able to answer another client request which is time-consuming. To overcome this problem, multithreading feature of programming is used in the software . Socket programming is proper feature of programming to create relation between application programs and TCP/IP protocol. In socket programming, input arguments will give to the each socket and socket will return one or more results which these results will utilize as an end point to establish connection in TCP/IP.
To implement and calculate simulation results, instead of telecommunication switches, client computers are used to simulate them, and server computer simulate control switch to make a required instructions for controlling telecommunication switches. Simulation of client-server network, functional test program for send/receive, connect/disconnect and other functions of TCP/IP protocol are programmed with visual C++ software . According to received information from application layer, connection conditions such as establishment and release will carry out. Also clean and unaccepted data sending and different states of TCP were implemented in the simulation software .
4.1 Proposed Architecture to Manage Network
As explained in subsection 3.3, each of the CMIP and SNMP might implement on the OSI and TCP/UDP/IP models separately. In the proposed architecture, the main advantage is the possibility of network management of both OSI model and TCP/UDP/IP networks simultaneously. As shown in figure 8, this new architecture could manage hybrid OSI and Internet-based networks . We named this new architecture SUL (Sub-layer between Upper and Lower layers). This model means:
To manage network, protocol selection is very important and depend on the different parameters such as size of network, network traffic, access to the resources and essential management functions. Table 8 compares the management functional areas of CMIP and SNMP. To implement SNMP on the OSI model, a “snmp” selector defines. This selector is used for management and “snmp trap” will utilize to declare alarm. SNMP entity of the manager or agent should listen to this selector for detection the type of message.
To put CMIP on the TCP/UDP/IP network in the OSI model, Low Presentation Protocol (LPP) is proposed for connection TCP/UDP/IP to the upper layers. The LPP in the sub-layer will provide necessary functions of CMIP on the stack protocol TCP/UDP/IP. Also LPP give the required function for SNMP on the OSI protocol stack.
Figure 8. Proposed architecture of network management.
Table 8. Functional management of SNMP and CMIP
4.2 Proposed Algorithm
Regarding to three different approaches for information transaction between threads named Semaphore, Deadlock and Critical Section, we have used Critical Section approach, it means if there is shared resource between threads and one thread use a shared resource, another thread doesn’t have an ability of using shared resource till first thread finish its work with shared resource Proposed implemented algorithm for lower layers of Q3 interface is shown in figure 9. The hardware specification of implementation for comparison of proposed algorithm with other algorithm is as Table 9.
Table 9. Hardware specification of simulation
In our implementation server simulate the control center and 20 clients simulate the users in the TMN. Each instruction for ordinary approach in ordinary switching telecommunication networks requires 86 bit in average for different protocols while with use of proposed algorithm in the Q3 interface each instruction needs only 64 bit. Our management network was implemented with RS232 network and maximum bit rate 11520 bps. As shown in figure 10, proposed method with Q3 interface implementation has overcome to ordinary method in approximately 300 points average with 26.6% performance improvement that performance was calculated as relative bit per second improvement for each number of instructions per second.
Figure 9. General proposed algorithm to transmit data between client and server
Figure 10. Comparison of the ordinary and proposed methods (Relative improvement for number of instructions per second)
Also to asset performance of the new proposed architecture, first the passing time for receiving response after sending a request is calculated. Calculation of time for three M-Get, M-Set and M-Event Report services is as table 10 .
Table 10. Time calculation for three service M-Get, M-Set and M-Event Report
Figure 11 shows the effectiveness of the proposed architecture (SUL) in comparison to CMIP and SNMP. In figure 11 numbers of operations per second have been calculated and proved that SUI architecture shown in figure 8 has a better performance than CMIP and SNMP. SUL has a 12.5% performance improvement in M-Get and M-Set services and 25% in M-Event Report service. For SNMP compare to CMIP, performance improvement is 125% in M-Get and M-Set services and 66% in M-Event Report service.
Figure 11. Performance Comparison of SUL (Proposed), CMIP and SNMP models
In this paper, the layers of Q3 interface was simulated and implemented on laboratory. For management of hybrid OSI and Internet network a new architecture was proposed. The proposed architecture named SUL which is based on the CMIP and SNMP protocols to manage networks. The SUL which is a new sub-layer, stayed between upper layer management protocols and lower layers protocol stacks OSI and TCP/UDP/IP. With use of this sub-layer, CMIP and SNMP protocols will provide required services for users independent of lower layers protocols in OSI and internet models.
This SUL architecture has been proposed to communicate between manager and agent entities fast with lower layers independency. SUL performance will overcome to each CMIP and SNMP performances. Simulation results show the performance improvement of SUL in comparison to CMIP and SNMP protocols in three services M-Get, M-Set and M-Event Report. Also proposed algorithm with Q3 interface has 26.6% performance improvement averagely in comparison to ordinary method in the TMN to manage all telecommunication switches.
 King A. & Hunt R., (2000), “Protocols and architecture for managing TCP/IP network infrastructures”, Computer Communications, Vol. 23, pp 1558–1572.
 Lakshmi, G. R., (1999), Fundamental of Telecommunication Network Management, IEEE press, New York.
 RFC 1189, ITU-T Recommendation X.711, (1990), Common Management Information Services and Protocols for the Internet (CMOT and CMIP).
 Sahin, V., Omidyar C.G., & Bauman T.M., (1988), “Telecommunications management network (TMN) architecture and interworking designs’, IEEE Journal on Selected Areas in Communications, Vol. 6, pp 685-696.
 ITU-T, M3010, (1996), Principles for a Telecommunications Management Network.
 ITU-T, M3020, (2000), TMN Interface Specification Methodology.
 Mark, A. & Miller, P. E., (1992), Trouble Shooting TCP/IP, Prentice Hall.
 Pouffer, Y., (1997), ISO Transport Service on top of TCP (ITOT), RFC2126, Network Working Group, Digital Equipment Corporation.
 RFC791, (1981), Internet Protocol, Information Sciences Institute University of southern California.
 Thomas S. A., (1996), Ipng and TCP/IP protocols, John Wiley & Sons Inc.
 M. Sailaja & Y. N. Kumar, (2015), “Design and Implementation of Next Generation Networks: A Future Communication System over IP Platform”, International Journal of Advanced Research in Electrical, Electronics and Instrumentation Engineering, Vol. 4, No. 11, pp 8634-8638.
 V. SURESH, (2016), “Network Management for Next Generation Networks”, International Research Journal of Computer Science (IRJCS), Vol. 3, No. 12, pp 45-47.
 ITU-T, M.3000, (1995), Maintenance Telecommunications Management Network: Overview of TMN Recommendations.
 ITU-T, Q.812, (1997), Upper Layer Protocol Profiles for the Q3 and X Interfaces.
 ITU-T, Q.811, (1997), Lower Layer Protocol Profiles for the Q3 and X Interfaces.
 Forouzan B., (2009), TCP/IP Protocol Suite, Mcgraw-Hill, 4th edition.
 Rose M. T. & McCloghrie K., (1995), How to Manage Your Network Using SNMP, Prentice Hall.
 Duffy J., (2008), Concurrent Programming on Windows, Addison-Wesley, ISBN : 9780321434821.
 Schildt H., (2004), The Art of C++, McGraw-Hill/Osborne.
 Petzold C., (1998), Programming Windows, Microsoft Press.
 Farahani G., (2012), “Design and Implementation of New Architecture to Improve Management Performance of IP-based Networks”, International Conference on Information and Computer Networks, Singapore.
 Farahani G., (2012), “Design and Implementation of Lower Layers of Q3 Interface in Telecommunication Management Network”, Proceedings of the International Network Conference, Port Elizabeth, South Africa.
Gholamreza Farahani received his BSc degree in electrical engineering from Sharif University of Technology, Tehran, Iran, in 1998 and MSc and PhD degrees in electrical engineering from Amirkabir University of Technology (Polytechnic), Tehran, Iran in 2000 and 2006 respectively. Currently, he is an assistant professor in the Institute of Electrical and Information Technology, Iranian Research Organization for Science and Technology (IROST), Iran. His research interest is signal processing and computer network especially architecture and protocols.