2005
DOI: 10.1109/jcn.2005.6389819
|View full text |Cite
|
Sign up to set email alerts
|

Interactive conflict detection and resolution for personalized features

Abstract: In future telecommunications systems, behaviour will be defined by inexperienced users for many different purposes, often by specifying requirements in the form of policies. The call processing language (CPL) was developed by the IETF in order to make it possible to define telephony policies in an Internet telephony environment. However, user-defined policies can hide inconsistencies or feature interactions. In this paper, a method and a tool are proposed to flag inconsistencies in a set of policies and to ass… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
10
0

Year Published

2005
2005
2013
2013

Publication Types

Select...
5

Relationship

2
3

Authors

Journals

citations
Cited by 7 publications
(10 citation statements)
references
References 13 publications
0
10
0
Order By: Relevance
“…Xu et al proposed to translate CPL into a formal language to check feature interactions [12]. Amyot et al developed a tool called FIAT for filtering inconsistencies among features, then implemented a translator to convert CPL to the FIAT input language [13]. FIAT has a user-friendly web-based user interface for handling conflicts detected among CPL scripts.…”
Section: Related Workmentioning
confidence: 99%
See 1 more Smart Citation
“…Xu et al proposed to translate CPL into a formal language to check feature interactions [12]. Amyot et al developed a tool called FIAT for filtering inconsistencies among features, then implemented a translator to convert CPL to the FIAT input language [13]. FIAT has a user-friendly web-based user interface for handling conflicts detected among CPL scripts.…”
Section: Related Workmentioning
confidence: 99%
“…Users can also manually change the order of services by clicking the Move up or Move down button. This is similar to the method defined in FIAT [13], but we do not explicitly ask users to set priority among or disable features. If all the branches of a feature are redundant or shadowed [13] by features having higher priority, the feature will be automatically disabled.…”
Section: Feature Interactions Caused By Multiple Triggersmentioning
confidence: 99%
“…As shown in the secretary example above, users should be given the means to relate the expected operation of their policies to situations which they currently understand. Static detection tools to help users in this direction are being developed [3] [25]. To accomplish this, policy systems for both professional and naïve feature designers must be informed by knowledge of the human world.…”
Section: Formalisms For Naïve Usersmentioning
confidence: 99%
“…One of the characteristics of Internet telephony will be the capability for users to program their own features. Obviously, users will need interactive help to catch common pitfalls in this process, and our method promises such help [9].…”
mentioning
confidence: 99%
“…However, the method doesn't depend on any specific telephony model and has been used by the authors in order to detect feature interaction in Internetbased telephony systems [9].…”
mentioning
confidence: 99%