Reach Us +44-175-271-2024
All submissions of the EM system will be redirected to Online Manuscript Submission System. Authors are requested to submit articles directly to Online Manuscript Submission System of respective journal.

New Methodology for Distributed Real-Time Implementation of Telecommunications Architecture Based on Linux

Equipe Architectures des Systèmes, ENSEM, Université Hassan II Ain Chock.
Postal Address: BP. 8118, Oasis Casablanca, Morocco

Equipe Architectures des Systèmes, ENSEM, Université Hassan II Ain Chock.
Postal Address: BP. 8118, Oasis Casablanca, Morocco

Equipe Architectures des Systèmes, ENSEM, Université Hassan II Ain Chock.
Postal Address: . 8118, Oasis Casablanca, Morocco

Mustafa RADOUI
Equipe Architectures des Systèmes, ENSEM, Université Hassan II Ain Chock.
Postal Address: . 8118, Oasis Casablanca, Morocco

Visit for more related articles at Journal of Internet Banking and Commerce


Our goal is to define an architecture to design a real-time distributed platform of network connection with an installation wizard and configuration of an ADSL modem, router and other telecommunication products under a GNU/Linux distribution, and an utility for managing ADSL connections. This architecture is based on the multi-agents. The design of this architecture is based on the concept of AUML


Distributed Architecture; Real Time; Multi-agent System; UML Agent; Linux; Kernel; Modem; Router; DSL modem


An agent is a physical or virtual entity able to act in an environment that can communicate directly with other agents, driven by a set of trends (autonomy), which has its own resources, able to perceive its environment, which has skills and offers services that can possibly happen again, whose behavior tends to meet its objectives, taking into account the resources and skills available, and depending on its perception, its representations and communications received [1].

An agent possesses some or all of these features.

A multi-agent system is a set of autonomous agents in interaction. It helps coordinate the behavior of this group of agents to collectively solve a problem in a complex and evolving environment.

A multi-agent system is a set of intelligent agents interacting.

Agent → Autonomy

Intelligent→ Goal, tasks

Interacting→ Consideration of other distributed systems consisting of a set of agents

A multi-agent system can be:

• Open: agents enter and exit freely.

For example: a cafe, an e-commerce application.

• Closed: the set of agents remains the same.

For example: a football game, a multi-expert system.

• Homogeneous: all agents are built on the same model.

For example: a meeting, a colony of ants.

• Heterogeneous: agents of different models of different granularities.

For example: an ecosystem

• Mixed (or not): 'human' agents are part of the system. It is open and heterogeneous.

For example: a working group mediated by assistant's agents.

The oriented-agent programming has been proposed by Yoav Shoham in 1993 as a new programming paradigm.

In this approach, agents are the central elements of language.

Oriented-agent programming assumes that we will develop programs in which multiple agents interact, which focuses on the social dimension of agents.


Figure.1 Differences between Object and Agent

Proposed Architecture

Our goal is to build a distributed architecture based on multi-agents, able to solve configuration problems of ADSL modems, routers and other telecommunications products under a GNU/Linux distribution.


Figure.2 Proposed architecture

Realization of the Platform

• Designing the Model

In this section we propose a new design methodology based on the AUML language.

Agent UML is an extension of UML to take into account the agent notions. Agent UML inherits representations proposed by UML [3]. It thus contains ten types of diagrams symbolizing many different views to represent particular concepts of information system. They fall into two main groups:

Diagrams behavioral or dynamic charts:

1. Sequence diagrams

2. Collaboration diagrams

3. Activity diagrams

4. Statechart

5. Use case diagrams

Structural diagrams or static diagrams:

6. Class diagrams

7. Object diagrams

8. Packages

9. Component diagrams

10. Deployment diagrams

These diagrams are not necessarily all used at modeling.

The design of the proposed architecture is described through the two diagrams of use cases and classes of agents to illustrate the static aspect of the distributed platform developed.

• Diagram of use case


Figure.3 Use case diagram

A representation in use case diagram is needed for the requirements specification. Several use cases were identified from the needs analysis:

• Class agents diagram

Initially, we look at the conceptual level that is high enough for the multi-agents system eliminating all surface information for understanding the structure of the system.

The class agents diagram in Figure 4 represents the conceptual level of the platform developed.


Figure.4 Class agents diagram (conceptual level)

Realization of the Model

We used the concepts explained in the previous sections to develop a demonstration application which implements this model.

We chose for our distributed development platform, open source solutions including:

• Fedora (GNU/Linux) as an Operating System

• GTK+ graphical library

• C and Bash Shell.

• RPM (Red Hat Package Manager) to package the application with its different components (programs, firmware,..) for an easy setup on the end-user OS.

• Supported products :

o ADSL Modem: Sagem Fast 800 (chipset 1 to 4)

o Router with a wired connection

In Figure 5 we can see the setup file (RPM package) and a running installation on Fedora (GNU/Linux).


Figure.5 Installing the application packaged in rpm

The installation is therefore without any user intervention, only a confirmation by pressing a button.

Then we will start our program from the menu that Fedora has been added automatically during the installation:


Figure.6 Launching the application through the menu

After the first screen, the application proposes to choose the type of device to install.


Figure.7 Choosing the type of device to install

If you chose to install a router, the application proposes the configuration of the network card via DHCP since most routers have a DHCP server by default, and then launch the browser to administer the router via its web integrated application.


Figure.8 Routers configuration

In the case of installation of an ADSL modem, the application detects and blocks the installation if the kernel version, GNU/Linux distribution or modems are not supported.


Figure.9 Checking kernel, OS and modem

If the modem is connected and supported, the following screen appears:


Figure.10 Entering DSL Connection Informations


Figure.11 Display performed tasks


Figure.12 ADSL Management

The final screen is dedicated to the program launched just after the wizard to manage an ADSL connection:


We have proposed a new distributed real-time architecture based on multi-agent systems that allow the installation and configuration of modem, routers and other telecommunications products on a GNU/Linux distribution and also the management of an ADSL connection. This new architecture designed to facilitate the installation tasks for an end user not familiar with shell commands.


Copyright © 2024 Research and Reviews, All Rights Reserved