Mumbai University > Electronics and Telecommunication > Sem8 > Wireless Networks

Marks: 10M

Network services management middleware framework model

The framework supports the secondary development, through integrated environment development, services to meet the SOA specification, deployment of services in the form of plug-ins to the framework, assembly existing service components suitable for the business services through process planning, which will be published to the ESB business services, through the thin terminal access thin service management system to complete the network service management and monitoring.

• Network element layer :

  i. The underlying framework is the network element (NE) layer that contain the network physical layer devices and various interfaces, and systems and applications. The equipment composed of IaaS platform including servers, routers, switches, hosts, etc.

  ii. The applications deployed on the platform include operating system, database, virtual machine, which are called soft-NE.

  iii. Because these devices and applications from different manufacturers with different technical standards of production and development and different communication protocols.

• Data acquisition and processing :

  i. IT service quality management and monitoring system use layer data management in data management, as shown in Figure 2.

  ii. First of all, the managed object model is needed to build, of which interface and attributes are called the master data.

  iii. A variety of data collected by monitoring agent is called resource data, also known as real-time data, which is the source data used by analyzing and processing in the system, .

  iv. By Calculating and processing real-time data, we can get business data. System get analysis of data by analyzing monitoring data, which can be showed to user in the way of graphics, animation, alarm, etc. the data is referred to as user data.

Fig2: Hierarchical data processing

• JBI implementation environment monitoring network services :

  i. The aim of network services management is to provide stable, reliable, high-quality services for users.

  ii. To achieve this goal, managers must fully understand the operational status of network service resources, which requires the monitoring of network resources to provide services together, as shown in Figure 3.

  iii. Monitoring agent will introduce monitored node information into JBI container through different protocol binding components where data can be process through the engine.

  iv. Data processing focus on monitoring data contained in the information and knowledge using of data mining, business intelligence (BI) analysis techniques.

  v. Engine can schedule the service consumer and services, can provide simple services, the service engine can constructer new services by aggregating other services. JBI automatically create monitor resource directory through the directory automatic discovery engine.

  vi. The monitoring engine inspect the data that returned by monitoring agency and compare alert alarm conditions set in the alarm engine to determine whether the alarm is triggered. Resource control engine communicate with monitoring agency, and control resources monitored by monitoring agent.

  vii. Data processing engine can obtain the corresponding business data and analytical data by calculating, extracting and other processing of the data collected. viii. The safety control engine is for user authentication and access control.

  ix. Event management engine manage various events within the system, and log. XSLT engine complete the convert between a text file, SQL statements, HTTP message, a certain sequence of data calls, etc. and XML documents.

  x. BPEL engine complete weaving business process by deploying BPEL service unit the deployment.

  xi. POJO engine will put the basic service's POJO class into the JBI. SQL engine complete the operation of database. RULE engine is for processing the alarm occurred. All functions of JBI provide service in the form of web service externally.

Fig3: Implementation of the JBI environment monitoring network services

xii. Java Management Extension (JMX) binding components achieve management control of JBI environment, SMTP binding components implementation mail forwarding , JMS binding components achieve distributed management of network services, HTTP Binding Component achieve Web service access, SNMP Binding Component achieve monitoring resources management control and data acquisition.

xiii. The nodes outside the JBI system is external service consumers and service providers, on behalf of external entity that JBI need to integrate.

• Business services :

  i. The business service get by the framework model are ultimately up to enterprise service bus, the administrator call these services through the management terminal to implement network management.

  ii. ESB is a product of combinations traditional middleware technology with XML, Web services technologies etc. which can eliminate technical difference between different applications, make different application servers do well and achieve communication between the different services.

  iii. We publish the business services to ESB, which make these services available to the network services in the form of web service.

  iv. Manager Server fined Service Broker by looking for various types of IT and get these resources management information, analysis the management information, percept and call the functional modules to achieve the purpose of reuse modules.

  v. The open standards XML, WSDL, SOAP and UDDI are used to describe a web application integrating standardized methods. WSDL describes the availability of services, XML is used to package the data, and SOAP is used to transmit data, UDDI lists which services are available. Figure 4 describes the basic model of web services.