Design patterns - ICIN 2010

Session 7b Future Ideas Analysis of Design Patterns for Composite Telco Services Corrado Moiso - Strategy & Innovation, Telecom Italia R. Minerva, A. Manzalini - Strategy & Innovation, Telecom Italia P. Baglietto, M. Maresca, M. Stecca - CIPI University of Genoa and Padua All rights reserved

The issue ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Composite services a reference model Composite Service Component Service Component Service Component Service Telco Capability Telco Capability Telco Capability Heterogeneous protocols (e.g., capability specific) Interfaces based on basic interaction primitives Command Assist Event Basic interaction primitives

Basic interaction primitives ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Request-Response interaction pattern ,[object Object],Composite Service Component Service Command Commands processed by the Component Service CommandRes The Composite Service waits for the result Command CommandRes

Notification interaction pattern ,[object Object],Command (Subscribe: EventDescr, CBref ) CommandRes (SubscribeRes: SubID ) Subscription to a specific event class to start notifications Composite Service Component Service Command (UnSubscribe: SubID ) CommandRes (UnSubscribeRes: SubID ) Unsubscription to stop notifications Event1 Event (Notify: Event1, SubID ) Processing of events performed by Composite Service according to the logic of CBref Eventn Events of the Component Service (notified to all the subscribed application) Event (Notify: Eventn, SubID )

Request-started transaction interaction pattern ,[object Object],The Component Service starts of a new “activity” Command (StartActivity: Descr, CBref ) CommandRes (StartRes: SessID ) Composite Service Component Service Event (ChangeStatus, SessID ) Command (ModifyExecution, SessID ) Monitoring and control (in pull and/or push mode via CBref ) of the activity Execution of the activity performed by the Component Service Assist (InstructionRequest, SessID )

Solicit-started transaction interaction pattern ,[object Object],Command (Subscribe: ActivityDescr,CBref) CommandRes (SubscribeRes: SubID ) Subscription to a specific class of activities that the application has to monitor/control Composite Service Component Service Notification of an activity to be controlled by the subscribed application Assist (Activity, SubID , SessID ) AssistRes(Instruction) Monitoring and control (in pull and/or push mode) of the activity Execution of the activity performed by the Component Service Event (ChangeStatus, SessID ) Command (ModifyExecution, SessID ) Assist (InstructionRequest, SessID )

Interaction Patterns and existing interfaces – some examples Interaction Pattern Examples from OSA Examples from Parlay X Examples from Ribbit Examples from Ringful Request-Response User Location (pull mode) Short Messaging - Receive (pull mode) API – Messages (send and retrieval) SMS API - SendSms (without response) Notification User Location (periodic/ triggered events) Terminal Loc. (periodic/ triggered events) API - Messages (reception of events) Request-started trans. Multi-Party Call (appl. initiated) API - Calls Conference Call API Request-started trans. (only pull) Charging Session Third Party Call Solicit-started transaction Multi-Party Call (network initiated) Call Direction

Request-started transaction in Parlay X 3rd Party Call ,[object Object],[object Object],MakeCallSessionReq(Leg1, Leg2) MakeCallSessionRes( CallSessionIdentifier ) Composite Service Third Party Call Service The Component Service starts of a new call EndCallSessionReq( CallSessionIdentifier ) EndCallSessionRes() The thread periodically polls the state of the call GetCallSessionInformationRes(CallInfo) GetCallSessionInformationReq( CallSessionIdentifier ) GetCallSessionInformationRes(CallInfo) GetCallSessionInformationReq( CallSessionIdentifier )

Request-started transaction in Ribbit Call Control ,[object Object],[object Object],Composite Service Call API Application API PUT /apps/mydomain:myapp/ { "notificationUrl" : Ref } 200 OK {Appl-Info} POST /rest/1.0/calls/… { "legs":[Leg1, Leg2]} 201 CREATED LOCATION Call-Id POST Json={Call-Event} Event processed by Ref Events on call evolution POST Json={Call-Event} PUT /rest/1.0/calls/ Call-Id { "active":false } 200 OK { Call-Info}

Design Patterns ,[object Object],[object Object],[object Object],[object Object],[object Object]

Request-started transaction Design Pattern ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Design Patterns mapping ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Some open issues: Composite Service Session ID ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Parental Control Service – a use case ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

BPEL for Parental Control Service Notification Design Pattern Request Started Transaction Design Pattern

Parental Control Service : the role of csSessionID s ,[object Object],[object Object],[object Object],[object Object],[object Object],APIs without extraInfo parameter are not suitable to be combined by means of widely used BPEL language

The role of csSessionID s in Java ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]

Lessons learnt (1/2) ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],The definition of APIs for Telco Capabilities must carefully identify the interaction patterns (instead of the protocols to adopt)

Lessons learnt (2/2) ,[object Object],[object Object],[object Object],Signatures of APIs for Telco Capabilities should be extended with a new parameter to pass “CS Session ID” between Composite Service and Service Components

Design patterns - ICIN 2010

Recommandé

Recommandé

Contenu connexe

En vedette

En vedette (10)

Similaire à Design patterns - ICIN 2010

Similaire à Design patterns - ICIN 2010 (20)

Plus de steccami

Plus de steccami (20)

Dernier

Dernier (20)

Design patterns - ICIN 2010