SOA + Telecommunications = TelcoML! (An introduction to the TelcoML design standard)

Enabling Product and Service Innovation | RationalGood Design is Good Business Series (developerWorks)Good Design is Good Business Video (5:50 time mark)Brings ( you:SOA + Telecommunications = TelcoML!An introduction to the TelcoML design standard, an UML Profile forIntegrated TelecomGuest Speaker: Irv Badr Host: Roger Snook IBM Software, Rational WorldWide Enablement Leader, Offering, Strategy, Delivery (OSD) Team, +1.703.943.1170, RCSnook@us.ibm.com 2012 July 13 © 2012 IBM Corporation

Agenda Status: TelcoML is now an OMG standard TelcoML Motivation and global overview TelcoML marketing activities Details of TelcoML 2

Time-line for TelcoML standard Past – Jan 2008 : Start of specification process – March 2011: First presentation to the the OMG Architecture Board – Use cases presented by IBM and France Telecom – March-June 2011: Intensive work to fix AB reported problems – December 2011: TelcoML became a Global standard SPECIFICATION AVAILABLE at: http://www.omg.org/spec/TelcoML/ To Come – September 2012: End of finalization period - correction of bugs reported by implementers - Integration of TM Forum’s SES/SMI and possible updates to align with GSMA/OneAPI evolution – 2013 : TelcoML v2 with library 3

TelcoML Motivation Modeling Tools Telco2 APIs (SoaML/UML) Customization of SoaML to the telecom domain SoaML == modeling of SOA with UML TelcoML reuses <<ServiceInterface>> from SoaML Content of this specification – Telecom Enabler library expressed in UML (SoaML) – Service Composition Profile : Specify composite services (Telco+IT components) using UML, executable/technology agnostic 4

Introduction to SoaMLservices are defined through these set of basic information The name of the service, suggesting its purpose. The provided and required interfaces, thereby defining the functional capabilities that are provided by the service and those that it requires of its users. – Not how the service is implemented, but rather the interaction between the consumers and providers of this service. Any protocol that specifies rules for how the functional capabilities are used or in what order. Constraints that reflect what successful use of the service is intended to accomplish and how it will be evaluated. Qualities that service consumers should expect and that providers are expected to provide, such as cost, availability, performance, footprint, suitability to the task, competitive information, and so forth. Policies for using the service, such as security and transaction scopes for maintaining security and integrity or for recovering from the inability to successfully perform the service or any required service. 5

SoaML Interfaces: example of BSS implementation6

SoaML Service Data Models Data oriented model Message oriented services model7

Good Design is Good Business Series (developerWorks) www.ibm.com/software/rational SOA + Telecommunications = TelcoML!An introduction to the TelcoML design standard, an UML Profile for Integrated Telecom Guest Speaker: Irv Badr Host: Roger Snook8

TelcoML Details Two parts in TelcoML – Enabler Library: Representing in UML, popular Telco API’s – Composition Profile: means to model in UML executable service compositions. These two parts are complementary and may be used independently from each other 9

TelcoML Enabler libraryGoal: reformulate in SoaML, interfaces relevant to Telco API facilities Typical Usage: Code generation from UML Tools (such as IBM RSA) to execution frameworks (such as JOSIF) Relation with SDOs: GSMA, TMF Main interfaces: – Messaging: SMS & MMS (from GSMA/OneAPI) + generic (simpified) Messaging Interface – Click to call – Location (from GSMA/OneAPI) – Synchronization – Voice recognition and TTS Annex: – SES SMI (from TMF) – Waiting finalization for being incorporated 10

Example : OneAPI/SMS reformulated in SoaML <<ServiceInterface>> SMS +send(address: Address[1..*], message: String, notifyUrl: Url[0..1], correlator: String, senderName: String[0..1], charging: String[0..1]): SendResponse +getDeliveryStatus(messageId: String): DeliveryStatusResponse +startDeliveryReceipt(notifyUrl: Url, correlator: String, filterCriteria: String): StatusResponse +stopDeliveryReceipt(correlator: String): StatusResponse +receivedSms(registrationId: String) +startSmsNotification(notifyUrl: Url, correlator: String, destination: String, criteria: String): StatusResponse +stopSmsNotification(correlator: String): StatusResponse <<uses>> <<datatype>> <<datatype>> Address Url <<ServiceInterface>> SMSDeliveryNotification <<datatype>> DeliveryStatus <<uses>> +notifyDeliveryReceipt(correlator: String, deliveryStatus: DeliveryStatus) +address: Address +status: String <<ServiceInterface>> SMSReceptionNotification Send an SMS +notifyReception(correlator: String) P a ra me t Opt D e s c r ip t io n er a ddre s s No L is t o f a d d r e s s e s t o w h ic h t h e S M S w ill b e s e n t <<datatype>> <<datatype>> me s s a g <<datatype>> N o Th e m e s s a g e to b e s e n t DeliveryStatusResponse SendResponse e StatusResponse n o t if y U R Ye s U R L t o n o t if y t h e a p p lic a t io n f o r +statusResponse: StatusResponse +statusResponse: StatusResponse +code: String +deliveryStatus: DeliveryStatus[*] L d e liv e r y r e c e ip t s +messageId: String c o r r e la t +reason: String Y e s C o r r e la t o r f o r in c lu s io n in a or d e liv e r y r e c e ip t n o t if ic a t io n s e nde rN Ye s N a me o f the s e nd e r to a p p e a r o n a me t h e t e r m in a l C h a r g in Ye s C h a r g e t o a p p ly t o t h is m e s s a g e g11

More Examples : Generic Messagingand OneAPI/Location Generic & Simplified Messaging Interface Location12

TM Forum SES/SMI Draft: Reformulation in TelcoML Interface Data Types (first level)13

TelcoML Service Composition Profile Customize Service Composition from SoaML Service logic in SoaML can be specified using any kind of behavioral formalism TelcoML: – Selects a behavior paradigm suitable for expressing executable complex behavior (like voice-based interaction) => State Machines – Select notation conventions in line with ITU-T SDL experience => Transition centric notation. – Adds few specific icons: service call distinguished from computations done locally – Adds triggers and actions for voice interaction (Play, PlayAll, Inactivity Event, Reject Event, and so on). 14

TelcoML Service Composition Profile: Example - Executablity is more prescriptive than SoaML - Defined through State Machines (transition-centric presentation)15

TelcoML and JOSIF ToolingOur Expectations: 1 -Import of SoaML interfaces, in particular the TelcoML Library -Generate code to call the telco ‘s enabler implementations 2 -Import of TelcoML compositions and generate corresponding code to16 execute them

Executing a model17

Expanding the scope of TelcoML18

Enabling Product and Service Innovation | RationalComplete Scope of this Profile –Add SMI as Service Manager to TelcoML –Model Centric Business Process Framework • BPMN • eTOM –CSP Core Operations Management •OSS •BSS –Services Management (Creation/Execution/Measurement) •SDP Use Case based on Parlay X implementation Use Case based on Session-oriented messaging via SIP © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational CSP Services– Operational Services – SOA based • Performance Management • Event/Fault Management • Network Management & Monitoring • Asset Management • Trouble Ticketing/Service Desk • SLA Management– Data/Call Services • SoaML Based © 2012 IBM Corporation

Enabling Product and Service Innovation | RationalService Creation – Web Services through Parlay XHas been replaced with OneAPI  Parlay X 2.1 specification has been defined jointly between the European Telecommunications Standards Institute (ETSI), Parlay, and the Third Generation Partnership Program (3GPP) – http://portal.etsi.org/docbox/TISPAN/Open/OSA/ParlayX21.html  Parlay X is set of Web service APIs for the Communications Industry – Parlay X web services give users access to underlying network capabilities – interfaces are defined using WSDL 1.1 – conform with Web Services Interoperability (WS-I Basic Profile). © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational Simple Web Service: Use Case for Acknowledged SMS Multicast Enables a user to send an instant meeting notice to a group of Description – people and/or individuals via customized messages based upon ‘Meet-me-now’ presence and location Buddy List Invite Status Subject: You are Mary S Starts at: invited to Mary S Chris D Duration: attend a Chris D John D meeting John D Jim H … Jim H PI C Application Meeting invites Jane wants Jane Jane sees Jane selects checks the are sent via to schedule schedules SMS to invitees invite invitees location of a meeting the meeting within range confirmations invitees © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational Parlay X: Possible implementation roadmap A UML model of the Parlay X 2.1 Specification – UML to WSDL transformation generates semantically correct WSDL – Includes the basic behavioral diagrams found in the specifications – Includes the 2.1 specification documents and WSDL represented by the model © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational Multi-media sessions and SIP: Implementation Examples Call Flow modeling – Common domain-relevant way to express an expected scenario © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational SIP base messaging: Modeling and Implementation Call Flow reporting – A report or trace template showing the call flow – Servlet modeling – Design SIP and converged servlet applications that integrate in the context of user applications. Test case integration – Generate SIP test cases from modeled call flow diagrams. © 2012 IBM Corporation

Enabling Product and Service Innovation | Rational www.ibm.com/software/rational© Copyright IBM Corporation 2011. All rights reserved. The information contained in these materials is provided for informational purposes only, and is provided AS IS without warranty of any kind,express or implied. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, these materials. Nothing contained in these materials is intended to, nor shall havethe effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBMsoftware. References in these materials to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilitiesreferenced in these materials may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or featureavailability in any way. IBM, the IBM logo, Rational, the Rational logo, Telelogic, the Telelogic logo, and other IBM products and services are trademarks of the International Business MachinesCorporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others. 26 © 2012 IBM Corporation

SOA + Telecommunications = TelcoML! (An introduction to the TelcoML design standard)

by Roger Snook on Jul 13, 2012

Accessibility

Categories

Upload Details

Usage Rights

Statistics

SOA + Telecommunications = TelcoML! (An introduction to the TelcoML design standard) Presentation Transcript