Telecom Service Evolution Environment Feb 2008

1. Telecom Service Evolution EnvironmentFeb 2008 Shiri Kremer-Davidson (shiri@il.ibm.com) Mila Keren(keren@il.ibm.com) Dmitri Pikus(dpikus@il.ibm.com) Model Driven Engineering Technologies Group, Haifa Research Lab

2. Service Design Service Development Overview (1 of 3) Rapid Model Based Development of Quality IMS Services Problems being Addressed: • Developing a quality telecom service is time consuming and error prone • Developers need to be experts in low level protocols and architectures • Underlying technology is frequently changing • Service choreography is difficult • Developed services are hard to maintain Telecom and Modeling • Telecom domain professionals are familiar with modeling and its tooling • E.g. for capturing flow charts, sequence charts Target Audience: • Software professionals (modelers/developers) • May or may not be telecom experts • Are familiar with modeling notations Radical simplification of service development makes the process accessible to non-experts and cuts down time-to-market.

3. Service Design Service Development Overview (2 of 3) Rapid Model Based Development of Quality IMS Services Solution Benefits: • Radically simplifies new service development • Accessible to non-telecom experts • Reduces design time by an order of magnitude • Dramatically reduces time-to-market for new value-added services • Automatically generates executable service code • Supports service choreography in telecom domain • Invokes external services SIP Servlet code is generated from SCE UML Models Radical simplification of service development makes the process accessible to non-experts and cuts down time-to-market.

4. Service Design Service Development Overview (3 of 3) Rapid Model Based Development of Quality IMS Services Solution Highlights: • Telecom-specific modeling environment for developing IMS services • Telecom internals are hidden from users • Model transformation produces runnable code • Including service’s business logic • Service oriented development invokes external services from within the model • Using a service registry • Extensible reusable library of telecom specific elements

5. Objective: • Reduce the resources (time and money) needed to develop telecom services • Bring the benefits of end-to-end MDD to the Telecom Domain • Hide telecom internals from the developer by: • Providing a Telecom DSL abstracting over telecom protocols and IMS internals • Providing smart transformations, hiding the technical details • Providing an library of reusable telecom specific elements that can be extended by providers • Providing connectivity to a service registry (from multiple platforms) • Provide model creation, validation, debugging and testing tools Our Approach:

6. Telecom Services Scope • SCE enables creating TelecomServices (Server Side ) • SCE is typically used to define services of the following categories: • Medium complexity services that require logic fragments/structural parts in addition to service invocations • E.g. Meet-Me-Now, CallTunes • Services that require telecom specific characteristics (e.g. call management) and not only SOA related functionality • E.g. Free Calls with Advertisement Service • Services whose internals require maintenance or other telecom environment characteristics • E.g.: billing and authentication • Low-level atomic services that can be used in WEB2 mash-ups • E.g. media player • Need to be defined by IT Specialist

7. Current Status (Feb 2008) • Created a PoC Telecom Service Creation Environment • Over Rational Software Architect • Created two services using the tool (demos on our website): • Meet – Me – Now (emphasis on Service Choreography) Enables a user to send am SMS with a meeting invitation to a group of people from his buddy list who are nearby. • Free calls with Advertisement (emphasis on IMS Call Manipulation) Enables a client to place a free of charge calls that are interrupted from time to time by short advertisements • Defined Telecom Service Domain Specific Language • Defined a transformation from the model to runnable code • Structural parts include: Sipplet, sip.xml, modeled classes • Behavioral parts include: state machine and activity implementations

8. Plan for 2008 • Enhance Telecom IMS Service Creation Environment • Enlarge scope to include billing and authentication • Introduce model validation, including: • Model consistency/validation rules • Model quality rules • Introduce model debugging and test capturing tools • Ability to “run” the design model (using behavioral diagrams)

9. Thanks 