1 / 26

Manage Telecommunication equipment using Web Services

Manage Telecommunication equipment using Web Services. Agenda 1. Project objectives Side issues Main issues MileGate ? Embedded HTTP server HTML Generation Client tools Frameworks functionalities Evaluated frameworks WS-Description. Agenda 2. Interoperability WS►I Profiles

cosmo
Download Presentation

Manage Telecommunication equipment using Web Services

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Manage Telecommunicationequipmentusing Web Services

  2. Agenda 1 • Project objectives • Side issues • Main issues • MileGate ? • Embedded HTTP server • HTML Generation • Client tools • Frameworksfunctionalities • Evaluatedframeworks • WS-Description

  3. Agenda 2 • Interoperability • WS►I Profiles • WS►I Tools • Tests • Tests definitions • Tests validations • Conclusion • Disadvantage of the project • Benefit of the project • Whatneeds to beimproved in the future… • Questions

  4. Project objectives • Side issues • …. • …. • Main issues • ….. • ….. • ..…

  5. Introduction on MileGate IP-based multi-service next-generation access platform Combines broadbandaccess, telephony and data interfaces Migrate your telecommunications network to the NGN high quality Triple Play, broadband business services and traditional telephony and data services at the same time core unit & 20 otherunits example: 960 xDSL or 456 COMBO

  6. Introduction on MileGate Embedded system VxWorks, C++ PowerPC ~400MHz 256MB RAM, 128MB flash memory

  7. Embedded HTTP Servers

  8. Embedded HTTP Servers 2

  9. Embedded HTTP Servers 3

  10. Embedded HTTP Servers 4

  11. HTML Generation We performed a feasibility study and suggested a manner for the implementation. The suggestion contains: functional design sequential interactions discovery/requesting mechanism GUI prototype generation of the files reaction on modifications No client installation needed !

  12. Client tools • Frameworksfunctionalities

  13. Client tools 2

  14. Client tools 3

  15. Client tools 4 • Evaluatedframeworks • WS-Concepts → Web services concepts supported • Transport → Data transferprotocol • Encoding table → …………………………….. • Data binding → …………………………………… • General features→ ………………………………..

  16. Client tools 5 • Evaluatedframeworks • Unavoidableframeworks

  17. Web Service Principle Performed work Further development / Suggestions

  18. Web Service - Principle W3C definition public interfaces and bindings are defined and described using XML interact with the Web service in a manner prescribed by its definition, using XML based messages conveyed by Internet protocols Basic components of Web Service Architecture Communication Service Description Directory Service • SOAP • WSDL • optional, not used

  19. Web Service – Performedwork The new parts added to the WSDL file are: new fault type header & fault messages Integration of fault into operation’s WS-Transfer “soapAction” for operation’s automatic binding of the headers into the SOAP messages wsdl:service element with the Endpoint References • XSLT

  20. Web Service – Furtherdevelopment New discover message just for MO’s Use of relationships for operations Adaptation of notification mechanism Meta constraints for invocation of operations Many other possibilities as advertisement of new endpoints operational status of resource customized requests and more ..need to be analyzed carefully!

  21. Web services interoperability

  22. Web services interoperability 2 • WS►I Tools Interoperabilitytestingtools 1.1

  23. Tests • Test definition • Generate java classes from WSDL file • Test of the xFer module (WS-transfer) • Verify the usage of WS-Management • Send a SetLabel and Receive a GetLabel • Use WS-I tools for testinginteroperability • Convert WSDL 1.1 to 2.0 with WSO2 tools

  24. Tests 2

  25. Conclusion • … • … • …. • ….. • … • … • ….

  26. Questions ?

More Related