Manage Telecommunication equipment using Web Services

Agenda 1

Project objectivesSide issuesMain issues

MileGate ?Embedded HTTP serverHTML GenerationClient tools

Frameworks functionalitiesEvaluated frameworks

WS-Description

Agenda 2Interoperability

WS►I ProfilesWS►I Tools

TestsTests definitionsTests validations

ConclusionDisadvantage of the projectBenefit of the projectWhat needs to be improved in the future…

Questions

Project objectives

Side issues….….

Main issues…..…....…

IP-based multi-service next-generation access platformCombines broadband access, telephony and data interfacesMigrate your telecommunications network to the NGNhigh quality Triple Play, broadband business services and traditional telephony and data services at the same time

core unit & 20 other units

example: 960 xDSL or 456 COMBO

Introduction on MileGate

Embedded systemVxWorks, C++PowerPC ~400MHz256MB RAM, 128MB flash memory

Introduction on MileGate

Embedded HTTP Servers

Embedded HTTP Servers 2

Embedded HTTP Servers 3

Embedded HTTP Servers 4

We performed a feasibility study and suggested a manner for the implementation.

The suggestion contains:functional design sequential interactionsdiscovery/requesting mechanismGUI prototypegeneration of the filesreaction on modifications

HTML Generation

No client

installation

needed !

Client tools Frameworks functionalities

Client tools 2

Client tools 3

Client tools 4

Evaluated frameworks

General features → ………………………………..

Data binding → ……………………………………

Encoding table → ……………………………..

Transport → Data transfer protocol

WS-Concepts → Web services concepts supported

Client tools 5

Evaluated frameworks Unavoidable frameworks

PrinciplePerformed workFurther development / Suggestions

Web Service

W3C definitionpublic interfaces and bindings are defined and described using XMLinteract with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols

Basic components of Web Service ArchitectureCommunicationService DescriptionDirectory Service

Web Service - Principle

SOAP WSDL optional, not

used

The new parts added to the WSDL file are:new fault typeheader & fault messagesIntegration of fault into operation’sWS-Transfer “soapAction” for operation’sautomatic binding of the headers into the SOAP messageswsdl:service element with the Endpoint References

Web Service – Performed work XSLT

New discover message just for MO’sUse of relationships for operationsAdaptation of notification mechanismMeta constraints for invocation of operations

Many other possibilities as advertisement of new endpointsoperational status of resourcecustomized requests and more

..need to be analyzed carefully!

Web Service – Further development

Web services interoperability

Web services interoperability 2 WS►I Tools

Interoperability testing tools 1.1

Tests

Test definition

Use WS-I tools for testing interoperability

Send a SetLabel and Receive a GetLabel

Verify the usage of WS-Management

Test of the xFer module (WS-transfer)

Generate java classes from WSDL file

Convert WSDL 1.1 to 2.0 with WSO2 tools

Tests 2

……….…..

……

Conclusion

….

Questions

?