Presentation is loading. Please wait.

Presentation is loading. Please wait.

Feature Interaction Handling in LESS Xiaotao Wu and Henning Schulzrinne Internet Real Time Laboratory.

Similar presentations

Presentation on theme: "Feature Interaction Handling in LESS Xiaotao Wu and Henning Schulzrinne Internet Real Time Laboratory."— Presentation transcript:

1 Feature Interaction Handling in LESS Xiaotao Wu and Henning Schulzrinne Internet Real Time Laboratory

2 2 Overview End system services CPL and LESS Feature interaction handling in CPL/LESS Action conflict table Tree merging More than call control services Open issues

3 3 Where to put services End devicesEnd serversNet UAsProxyB2BUA Number of users SingleSingle/trust ed users Multiple Call/dialog states Yes NoYes MediaYesYes/noYesNoYes/no Number of entities SingleMultipleSingleMultiple Direct interaction YesNo/yesNo Admin.End user Admin. Store services in the network, though they may get executed in end systems Keep the peer-to-peer architecture, avoid the master/slave architecture

4 4 CPL and LESS CPL: Call Processing Language LESS: Language for End System Services Simple Four kinds of elements: trigger, switch, action, modifier Tree-like structure, easy for feature interaction analysis Safe Type safety: XML-based, no user defined variables Control flow safety: tree-like structure without back-reference No direct memory access Default behavior for every tree branch Portability Handle user interactions and media operations Beyond call control presence, IM, Web, location IEEE ICC’03 RFC3880

5 5 Tree-like structure Using a tree-like structure to represent communication services Natural thinking of call decision making – a rule set For an incoming call, if I am in a conference, I will reject all the calls that are not from my boss. A decision tree to represent a rule set For an incoming call If I am in a conference If the call is from my boss Vibrate my device Reject the call YES NO CPL and LESS

6 6 Timer triggered outgoing call <less xmlns="urn:ietf:params:xml:ns:less “ xmlns:IM="urn:ietf:params:xml:ns:less:im “ xmlns:xsi= “… " xsi:schemaLocation= “… "> <status-switch uri="" status-name="presence"> Hi, please call me back. I am in office …………….

7 7 LESS elements Triggers incoming: incoming call handling timer: timer triggered actions UI:command: user interaction commands IM:message: incoming instant messaging Event:subscription: incoming subscription Event:notification: incoming notification

8 8 LESS elements (cont.) Switches time-switch: make decisions based on time address-switch: make decisions based on caller, callee priority-switch: make decisions based on call priority string-switch: make decisions based on subject, … language-switch: make decisions based on languages status-switch: make decisions based on users’ status (remote user or local user, status includes presence, activity, mood, …, as listed in RPID) Event:event-switch: check values in event notifications LOC:where-switch: check users’ physical location information (remote or local user) LOC:where-relation-switch: check relative physical locations between two people

9 9 LESS elements (Cont.) Actions accept: accept an incoming call reject: reject an incoming call redirect: redirect an incoming call authenticate: authenticate an incoming request call: make an outgoing call terminate: disconnect a call wait: wait for a certain time before next action mail: send email log: log request handling process Media:mediaupdate: update media attributes Midcall:transfer: transfer a call Midcall:merge: merge multiple calls UI:alert: alert user UI:getinput: get user input IM:sendmsg: send an instant message Event:approve: approve subscription Event:deny: deny event subscription Event:defer: defer the decision on event subscription Event:subscribe: send subscription out Event:notify: send notification out Queue:enqueue: put a call and its context into a queue Queue:dequeue: get a call and its context from a queue

10 10 LESS elements (Cont.) Two smaller concepts might be simpler and more flexible than one more powerful but complicated concept Modifiers location: to which a request to be directed lookup: lookup locations from a source remove-location: remove locations from location set Media:media: provide media attributes

11 11 Automatic Call Back (ACB) <less xmlns="urn:ietf:params:xml:ns:less“ xmlns:Event="urn:ietf:params:xml:ns:less:event“ xmlns:Queue="urn:ietf:params:xml:ns:less:queue“ xmlns:xsi=“….“ xsi:schemaLocation=“……"> <status-switch status-name=“activity”> <Queue:enqueue queue="callback"/> In ITU Q.1211 “This feature allows the called party to automatically call back the calling party of the last call directed to the called party.” Check my activity for an incoming call Use Event and Queue extension If I am on-the-phone Reject and enqueue

12 12 <Event:event package=“presence" name=“activity" is=“normal"> <Queue:dequeue queue="callback"> A event notification for myself I am available Dequeue and make a call Automatic Call Back (ACB) (cont.)

13 13

14 14

15 15

16 16 LESS script customization xsl:if LESS editor service.less (template) XSLT less.xsl configuration editor service.html translate.cgi service_foo.less address is=$var

17 17 accept Feature interaction analysis Tree merging + = If time is between 10:00AM and 11:00AM If address is hgs Forward to conf Incoming call If time is between 10:00AM and 11:00AM If address is hgs reject Forward to conf reject accept Take actions from both scripts. Simply setting precedence rules cannot work.

18 18 Feature interaction analysis FI handling between multiple CPL/LESS scripts Action conflict tables Tree merging algorithm Multi-component feature interactions e.g., parallel forking with all end systems automatically accept an incoming call

19 19 Related work of CPL FI handling Related work Syntax correct, semantic warnings e.g., parent switch and child switch mutually exclusive Translate to formal languages to check FI with other complex services

20 20 Pre-condition and expected results pre-conditionexpected results accept The call setup is pending. The audio device is available. The call setup is finalize. The communication session is setup. The audio device is occupied. reject The call setup is pending.The call setup is finalized. redirect The call setup is pending.The call setup is finalized on the current end system. call The audio device is available.If the callee side accepts the call, a communication session is setup and audio device is occupied.

21 21 Action conflict table acceptrejectredirectcall accept A(media)CCR reject CA(reason)C- redirect CCA(target)- call R--A(target) -: no interaction, A: attribute conflict, C: action conflict, (C): avoidable conflict, E: enabling, R: resource competition

22 22 Tree merging set base-rule-set empty foreach LESS-tree { convert the LESS-tree into a rule set foreach rule in the rule set { normalize the rule } merge the normalized rule set into base-rule-set } convert base-rule-set into a decision tree

23 23 Tree merging (cont.) if (two rules have different triggers) { no rule conflict except timer trigger } else if actions in two rules do not conflict { no rule conflict } else if no overlap between rule path in two rules { no rule conflict } else { two rules conflict with each other, return the rule path overlap and action conflict information prompt to the script owner to judge }

24 24 Rich signaling information can help to solve feature interactions Rich signaling information SIP headers Caller preference and callee capabilities MIME contents Event notification Other means Web calendar, Directory services

25 25 More than just call control services Interact with existing Internet services web email SLP SAP IM presence location networked appliance control directory service calendar service conferencing Not named services, but programmable services Programmable conferencing services

26 26 Open issues Can we use LESS for B2BUA? ‘lookup’ from database coordinate multiple sessions multi-user feature interaction handling Loop and user-defined variables needed? Based on our exercises, no But, what about unknown new services? Convert loop to a high-level abstraction? What’s the impact on feature interaction handling

27 27 Some links LESS: Service examples: repository/reports/reports-2004/cucs-048-04.pdf repository/reports/reports-2004/cucs-048-04.pdf Feature interaction handling: ~xiaotaow/rer/Research/Paper/fiw.pdf ~xiaotaow/rer/Research/Paper/fiw.pdf SIPc: CINEMA:

28 28 Acknowledgements Dr. Henning Schulzrinne This project is supported by the funding from SIPQuest Thank you!

Download ppt "Feature Interaction Handling in LESS Xiaotao Wu and Henning Schulzrinne Internet Real Time Laboratory."

Similar presentations

Ads by Google