Beruflich Dokumente
Kultur Dokumente
INTRODUCTION
Automation of the operation and maintenance of mobile networks is a need for mobile
operators due to several forces driving costs up: increased traffic volume, variety of services,
number of subscribers, demand for quality of service (QoS), and competitiveness among
operators. Modern networks produce large volumes of operation and maintenance data, which
contain the information needed for the self-healing functions that operators need. In fact, the
volume of this data, along with the variety and time restrictions, calls for the use of the big data
paradigm. Big data is a set of new techniques that exploit the ever increasing processing power
of computer networks. Several use cases have been displayed as examples where data processing
algorithms can extract information contained in big-data-compliant data sources. In order for
these algorithms to work properly, small modifications have been proposed in order to run the
algorithm in parallel processes that do not interfere with each other. Parallelization reduces the
processing time (or increases the processing capability) of these algorithms, so Self-organizing
networking (SON) functions can be applied in a manner that is transparent for the users of the
network. The proposals can be extended to any self-organizing networking algorithm that can be
extended in a way which guarantees that the results of the parallelized version are the same as
the original. In order to further test the proposed solutions of the use cases, they can be
implemented using the commercially available big data processing solutions.
2. PROJECT DESCRIPTION
When data largely increase, traditional processing techniques have very poor
performance. The big data paradigm deals with this type of dataset by applying new techniques
that exploit the latest hardware and software innovations. In particular, in this article, self-healing
is reframed as a big data problem, and some specific requirements for the development of big-
data-compliant self-healing functions are proposed. Self-healing algorithms are usually
implemented during knowledge-based systems (KBSs) that imitate the process of human experts
in order to accomplish a task.
3. COMPUTATIONAL ENVIRONMENT
● Processor : Intel I5
● RAM : 1GB
● Storage Disk : 300 GB
3.3 SOFTWARE ENVIRONMENT:
Java Technology
The Java programming language is a high-level language that can be characterized by all
of the following buzzwords:
● Simple
● Architecture neutral
● Object oriented
● Portable
● Distributed
● High performance
● Interpreted
● Multithreaded
● Robust
● Dynamic
● Secure
The following figure depicts a program that’s running on the Java platform. As the figure
shows, the Java API and the virtual machine insulate the program from the hardware.
Java Technology
The most common types of programs written in the Java programming language are
applets and applications. If you’ve surfed the Web, you’re probably already familiar with applets.
An applet is a program that adheres to certain conventions that allow it to run within a Java-
enabled browser.
However, the Java programming language is not just for writing short, entertaining
applets for the Web. The general-purpose, high-level Java programming language is also a
powerful software platform. Using the generous API, you can write many types of programs.
An application is a standalone program that runs directly on the Java platform. A special
kind of application known as a server serves and supports clients on a network. Examples of
servers are
Web servers, proxy servers, mail servers, and print servers. Another specialized program is a
servlet. A servlet can almost be thought of as an applet that runs on the server side. Java Servlets
are a popular choice for building interactive web applications, replacing the use of CGI scripts.
Servlets are similar to applets in that they are runtime extensions of applications. Instead of
working in browsers, though, servlets run within Java Web servers, configuring or tailoring the
server.
● Software components: Known as Java BeansTM, can plug into existing component
architectures.
● Object serialization: Allows lightweight persistence and communication via Remote
Method Invocation (RMI).
● Java Database Connectivity (JDBCTM): Provides uniform access to a wide range of
relational databases.
The Java platform also has APIs for 2D and 3D graphics, accessibility, servers,
collaboration, telephony, speech, animation, and more. The following figure depicts what
is included in the Java 2 SDK.
Java programming language is still likely to make our programs better and requires less
effort than other languages. We believe that Java technology will help us do the following:
● Get started quickly: Although the Java programming language is a powerful object-
oriented language, it’s easy to learn, especially for programmers already familiar with C
or C++.
● Write less code: Comparisons of program metrics (class counts, method counts, and so
on) suggest that a program written in the Java programming language can be four times
smaller than the same program in C++.
● Write better code: The Java programming language encourages good coding practices,
and its garbage collection helps you avoid memory leaks. Its object orientation, its
● JavaBeans component architecture, and its wide-ranging, easily extendible API let you
reuse other people’s tested code and introduce fewer bugs.
● Develop programs more quickly: Your development time may be as much as twice as
fast versus writing the same program in C++. Why? You write fewer lines of code and it
is a simpler programming language than C++.
● Avoid platform dependencies with 100% Pure Java: You can keep your program
portable by avoiding the use of libraries written in other languages. The 100% Pure
JavaTM Product Certification Program has a repository of historical process manuals,
white papers, brochures, and similar materials online.
● Write once, run anywhere: Because 100% Pure Java programs are compiled into
machine-independent byte codes, they run consistently on any Java platform.
● Distribute software more easily: You can upgrade applets easily from a central server.
Applets take advantage of the feature of allowing new classes to be loaded “on the fly,”
without recompiling the entire program.
JDBC
In an effort to set an independent database standard API for Java; Sun Microsystems
developed Java Database Connectivity, or JDBC. JDBC offers a generic SQL database access
mechanism that provides a consistent interface to a variety of RDBMS. This consistent interface
is achieved through the use of “plug-in” database connectivity modules, or drivers. If a database
vendor wishes to have JDBC support, he or she must provide the driver for each platform that the
database and Java run on.
To gain a wider acceptance of JDBC, Sun based JDBC’s framework on ODBC. As you
discovered earlier in this chapter, ODBC has widespread support on a variety of platforms.
Basing
JDBC on ODBC will allow vendors to bring JDBC drivers to market much faster than
developing a completely new connectivity solution.
JDBC was announced in March of 1996. It was released for a 90 day public review that
ended June 8, 1996. Because of user input, the final JDBC v1.0 specification was released soon
after.
Few software packages are designed without goals in mind. JDBC is one that, because of
its many goals, drove the development of the API. These goals, in conjunction with early
reviewer feedback, have finalized the JDBC class library into a solid framework for building
database applications in Java.
The goals that were set for JDBC are important. They will give you some insight as to
why certain classes and functionalities behave the way they do. The eight design goals for JDBC
are as follows:
1. SQL Level API
The designers felt that their main goal was to define a SQL interface for Java. Although
not the lowest database interface level possible, it is at a low enough level for higher-level tools
and APIs to be created. Conversely, it is at a high enough level for application programmers to
use it confidently. Attaining this goal allows for future tool vendors to “generate” JDBC code and
to hide many of JDBC’s complexities from the end user.
2. SQL Conformance
SQL syntax varies as you move from database vendor to database vendor. In an effort to
support a wide variety of vendors, JDBC will allow any query statement to be passed through it
to the underlying database driver. This allows the connectivity module to handle non-standard
functionality in a manner that is suitable for its users.
1. JDBC must be implemental on top of common database interfaces
2. Provide a Java interface that is consistent with the rest of the Java system
3. Keep it simple
4. Use strong, static typing wherever possible
5. Keep the common cases simple
Finally we decided to proceed the implementation using Java Networking. And for
dynamically updating the cache table we go for MS Access database.
Compilation happens just once; interpretation occurs each time the program is
executed. The figure illustrates how this works.
Java Program
Fig 3.5 Working of Java Program
You can think of Java byte codes as the machine code instructions for the Java
Virtual Machine (Java VM). Every Java interpreter, whether it’s a Java development
tool or a Web browser that can run Java applets, is an implementation of the Java VM.
The Java VM can also be implemented in hardware.
Java byte codes help make “write once, run anywhere” possible. You can
compile your Java program into byte codes on my platform that has a Java compiler.
The byte codes can then be run any implementation of the Java VM. For example, the
same Java program can run Windows NT, Solaris, and Macintosh.
4. FEASIBILITY STUDY
The feasibility of the project is analyzed in this phase and business proposal is put forth
with a very general plan for the project and some cost estimates. During system analysis the
feasibility study of the proposed system is to be carried out. This is to ensure that the proposed
With each new generation of communication technologies, the control data and network
performance measurements in the operation and maintenance (O&M) subsystem grow in both
volume and speed. A larger number of users and quantity of transferred data means a larger
amount of measurements. In addition, the higher demand for quality and larger bandwidths
pushes for a faster rate of generation and consumption of these data. Downtimes due to problems
that are not solved quickly or incorrect optimization cause a high opportunity cost and increased
overall operation and maintenance costs.
Troubleshooting Procedure
The manual troubleshooting workflow has four main subtasks.
● Detection: The process of determining that there is a problem in the network, and
pinpointing the element or elements that are affected. To do this, troubleshooting
engineers will usually monitor a much reduced set of a problem.
● Diagnosis: Once the problematic elements have been determined, troubleshooting
engineers must find out the root cause (i.e., why they are failing). The study of low-level
indicators, as well as logs or event records may help in the determination of the root
cause. In some cases, active measurements are taken, such as drive tests.
● Compensation: The troubleshooting process may take anywhere between minutes to
several days. Therefore, it is important to redirect the resources of the network
temporarily to give service to the users in the affected area.
● Recovery: Once the root cause is known, the required actions to fix it are taken. These
actions range from simple resets or configuration changes that can be ordered remotely,
to hardware fixes or replacements that need on-site repairs. The recovery action may or
may not solve a problem, so the results of the action are taken into account on subsequent
repetitions of the diagnosis subtask.
System Design is the most crucial phase in the development of a project. The purpose of
the system design is to define the required architecture, necessary components, needed modules,
suitable interfaces and the essential data for a system to satisfy the requirements that are in the
specification. Sometimes it can be viewed as the application of systems theory to development of
the product. There is an overlap with the various disciplines of the system analysis such as
systems architecture and systems engineering. Systems design is consequently the process of
defining and developing the systems that must satisfy all the requirements that are specified by
the user
6.1 ARCHITECTURAL DESIGN
Fig.6.1.Architecture
The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application.
The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling of object
oriented systems because they are the only UML diagrams which can be mapped directly with
object oriented languages.
Purpose:
The purpose of the class diagram is to model the static view of an application. The class
diagrams are the only diagrams which can be directly mapped with object oriented languages and
thus widely used at the time of construction.
The UML diagrams like activity diagram, sequence diagram can only give the sequence
flow of the application but class diagram is a bit different. So it is the most popular UML
diagram in the coder community.
To model a system the most important aspect is to capture the dynamic behaviour. To
clarify a bit in details, dynamic behaviour means the behaviour of the system when it is running
or operating.
These internal and external agents are known as actors. So use case diagrams are consists
of actors, use cases and their relationships. The diagram is used to model the system/subsystem
of an application. A single use case diagram captures a particular functionality of a system.
So to model the entire system numbers of use case diagrams are used.
Purpose:
The purpose of use case diagram is to capture the dynamic aspect of a system. But this
definition is too generic to describe the purpose.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. So when a system is
analyzed to gather its functionalities use cases are prepared and actors are identified.
Now when the initial task is complete use case diagrams are modelled to present the
outside view.
Overview:
Purpose:
The purposes of interaction diagrams are to visualize the interactive behaviour of the
system. Now visualizing interaction is a difficult task. So the solution is to use different types of
models to capture the different aspects of the interaction.
Activity diagram explained in next chapter, is a special kind of a State chart diagram. As
State chart diagram defines states it is used to model lifetime of an object.
Purpose:
State chart diagram is one of the five UML diagrams used to model dynamic nature of a
system. They define different states of an object during its lifetime. And these states are changed
by events. So State chart diagrams are useful to model reactive systems. Reactive systems can be
defined as a system that responds to external or internal events.
State chart diagram describes the flow of control from one state to another state. States
are defined as a condition in which an object exists and it changes when some event is triggered.
So the most important purpose of State chart diagram is to model life time of an object from
creation to termination.
State chart diagrams are also used for forward and reverse engineering of a system. But
the main purpose is to model reactive system.
Activity diagram is basically a flow chart to represent the flow form one activity to
another activity. The activity can be described as an operation of the system.So the control flow
is drawn from one operation to another. This flow can be sequential, branched or concurrent.
Purpose:
The basic purposes of activity diagrams are similar to other four diagrams. It captures the
dynamic behaviour of the system. Other four diagrams are used to show the message flow from
one object to another but activity diagram is used to show message flow from one activity to
another.
Activity is a particular operation of the system. Activity diagrams are not only used for
visualizing dynamic nature of a system but they are also used to construct the executable system
by using forward and reverse engineering techniques. The only missing thing in activity diagram
is the message part.
It does not show any message flow from one activity to another. Activity diagram is some
time considered as the flow chart. Although the diagrams looks like a flow chart but it is not. It
shows different flow like parallel, branched, concurrent and single.
Purpose:
Component diagram is a special kind of diagram in UML. The purpose is also different
from all other diagrams discussed so far. It does not describe the functionality of the system but it
describes the components used to make those functionalities.
So from that point component diagrams are used to visualize the physical components in
a system. These components are libraries, packages, files etc.
A single component diagram cannot represent the entire system but a collection of
diagrams are used to represent the whole.
Deployment diagrams are used to visualize the topology of the physical components of a
system where the software components are deployed.
So deployment diagrams are used to describe the static deployment view of a system.
Deployment diagrams consist of nodes and their relationships.
The name Deployment itself describes the purpose of the diagram. Deployment diagrams
are used for describing the hardware components where software components are deployed.
Component diagrams and deployment diagrams are closely related.
Component diagrams are used to describe the components and deployment diagrams
shows how they are deployed in hardware.
UML is mainly designed to focus on software artifacts of a system. But these two
diagrams are special diagrams used to focus on software components and hardware components.
So most of the UML diagrams are used to handle logical components but deployment
diagrams are made to focus on hardware topology of a system. Deployment diagrams are used by
the system engineers.
7. SYSTEM IMPLEMENTATION
7.1.2 MODULES
1. Performance Management Metrics
2. Fault Management Alarms
8. TESTING
The purpose of testing is to discover errors. Testing is the process of trying to discover
every conceivable fault or weakness in a work product. It provides a way to check the
functionality of components, sub-assemblies, assemblies and/or a finished product .It is the
process of exercising software with the intent of ensuring that the software system meets its
LOGIN:
<style type="text/css">
input {
width: 125px;
font-family: Verdana;
font-size: 8pt;
}
</style>
</head>
<body bgcolor="#F4FFE4">
<table width="100%" border="0" cellspacing="0" cellpadding="0">
<tr bgcolor="#D5EDB3">
<td height="51" style="text-align:center;" colspan="2" bgcolor="#0D4961"><img
src="images/Legal Management System11.jpg" alt="s" width="1000" height="139" /></td>
</tr>
<tr>
<td colspan="2" bgcolor="#5C743D"><img src="images/mm_spacer.gif" alt="" width="1"
height="2" border="0" /></td>
</tr>
<tr>
<td height="10" colspan="2" bgcolor="#000000"> </td>
</tr>
<tr>
<td width="100%" height="30px;" style="padding:10px;font-size:30px;" align="center"
valign="top" bgcolor="#DCDCDC">Login
<table width="100%" border="0" cellpadding="0" cellspacing="0" bgcolor="#DCDCDC">
</table>
LOGIN HANDLER:
<html><head>
<meta name="GENERATOR" content="Microsoft FrontPage 5.0">
CONCLUSION
Automation of the operation and maintenance of mobile networks is a need for mobile
operators due to several forces driving costs up: increased traffic volume, variety of services,
number of subscribers, demand for Quality of Service, and competitiveness among operators.
FUTURE ENHANCEMENT
In future work, in order to further test the proposed solutions of the use cases, they can be
implemented using the commercially available big data processing solutions.
12. BIBLIOGRAPHY
REFERENCES
● NGMN, Use Cases Related to Self-Organizing Network, Overall Description, Apr. 2007.
● 3GPP, “Telecommunication Management; Self-Organizing Networks (SON); Self-
Healing Concepts and Requirements,” Rel. 11, TS 32.541.
● R. Barco, P. Lázaro, and P. Muñoz, “A Unified Framework for Self-Healing in Wireless
Networks,” IEEE Commun. Mag., vol. 50, no. 12, Dec. 2012,pp. 134–42.
● E. J. Khatib et al., “Data Mining for Fuzzy Diagnosis Systems in LTE Networks, ”Expert
Systems with Applications, vol. 42, no. 21, 2015, pp. 7549–59.