SOA + Telecommunications = TelcoML! (An introduction to the TelcoML design standard)
-
Upload
roger-snook -
Category
Technology
-
view
908 -
download
2
Transcript of SOA + Telecommunications = TelcoML! (An introduction to the TelcoML design standard)
© 2012 IBM Corporation
Enabling Product and Service Innovation | Rational
Good 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 for Integrated Telecom
Guest Speaker: Irv Badr
Host: Roger Snook IBM Software, RationalWorldWide Enablement Leader, Offering, Strategy, Delivery (OSD) Team, +1.703.943.1170, [email protected] July 13
2
Agenda
Status: TelcoML is now an OMG standard
TelcoML Motivation and global overview
TelcoML marketing activities
Details of TelcoML
3
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
4
TelcoML Motivation
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
Telco2 APIs Modeling Tools (SoaML/UML)
5
Introduction to SoaML services 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.
6
SoaML Interfaces: example of BSS implementation
7
SoaML Service Data Models
Data oriented model
Message oriented services model
8
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
Good Design is Good Business Series (developerWorks)
Host: Roger Snook
9
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 complementarycomplementary and may be used independently from each other
10
TelcoML Enabler library
Goal: 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
11
Example : OneAPI/SMS reformulated in SoaML
SMS<<ServiceInterface>>
+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
DeliveryStatus<<datatype>>
+address: Address+status: String
Address<<datatype>>
Url<<datatype>>
DeliveryStatusResponse<<datatype>>
+statusResponse: StatusResponse+deliveryStatus: DeliveryStatus[*]
SMSDeliveryNotification<<ServiceInterface>>
+notifyDeliveryReceipt(correlator: String, deliveryStatus: DeliveryStatus)
SMSReceptionNotification<<ServiceInterface>>
+notifyReception(correlator: String)
StatusResponse<<datatype>>
+code: String+reason: String
SendResponse<<datatype>>
+statusResponse: StatusResponse+messageId: String
<<uses>>
<<uses>>
Send an SMS
Parameter Opt Description
address No List of addresses to which the SMS will be sent
message No The message to be sent
notifyURL Yes URL to notify the application for delivery receipts
correlator Yes Correlator for inclusion in a delivery receipt notification
senderName
Yes Name of the sender to appear on the terminal
Charging Yes Charge to apply to this message
12
More Examples : Generic Messaging and OneAPI/Location
Generic & Simplified Messaging Interface
Location
13
TM Forum SES/SMI Draft: Reformulation in TelcoML
Data Types (first level)
Interface
14
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).
15
TelcoML Service Composition Profile: Example
- Executablity is more prescriptivethan SoaML- Defined through State Machines (transition-centric presentation)
16
TelcoML and JOSIF Tooling
-Import of SoaML interfaces, in particular the TelcoML Library-Generate code to call the telco ‘s enabler implementations
1
-Import of TelcoML compositions and generate corresponding code to execute them
2
Our Expectations:
17
Executing a model
18
Expanding the scope of TelcoML
© 2012 IBM Corporation
Enabling Product and Service Innovation | Rational
Complete 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 implementationUse 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 | Rational
Service 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
Jane wants to schedule a meeting
Jane selects invitees
Buddy List
Mary S
Chris D
John D
Jim H
Jane schedules
the meeting
Subject:Starts at:Duration:
Meeting invites are
sent via SMS to invitees
within range
You are invited to attend a meeting…
Jane sees invite
confirmations
Invite Status
Mary S
Chris D
John D
Jim H
Application checks the location of
invitees
Enables a user to send an instant meeting notice to a group of people and/or individuals via customized messages based upon presence and location
Description – ‘Meet-me-now’
PIC
© 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
26
© 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 have the 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 IBM software. 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 capabilities referenced 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 feature availability 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 Machines Corporation, in the United States, other countries or both. Other company, product, or service names may be trademarks or service marks of others.
www.ibm.com/software/rational