Policies: Giving Users Control over Calls

Reiff-Marganiec, Stephan

doi:10.1007/978-3-540-25930-5_12

Cited by 7 publications

(5 citation statements)

References 11 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…We have used the language of [GRM06c] for its simplicity, expressive power and our familiarity with it Policies have generally been used as an administration technique in system management (e.g. access control [Mos05] or Internet Telephony [RM03]). Policies are descriptive and essentially provide information that is used to adapt the behaviour of a system.…”

Section: Related Workmentioning

confidence: 99%

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

Abstract. Service Oriented Computing is a paradigm for developing software systems as the composition of a number of services. Services are loosely coupled entities, that can be dynamically published, discovered and invoked over a network. The engineering of such systems presents novel challenges, mostly due to the dynamicity and distributed nature of service-based applications. In this paper, we focus on the modelling of service orchestrations. We discuss the relationship between two languages developed under the SENSORIA project: SRML as a high level modelling language for Service Oriented Architectures, and STPOWLA as a process-oriented orchestration approach that separates core business processes from system variability at the end-user's level, where the focus is towards achieving business goals. A fundamental challenge of software engineering is to correctly align business goals with IT strategy, and as such we present an encoding of STPOWLA to SRML. This provides a formal framework for STPOWLA and also a separated view of policies representing system variability that is not present in SRML.

show abstract

Section: Related Workmentioning

confidence: 99%

From StPowla processes to SRML models

Bocchi

Gorton²,

Reiff-Marganiec

2010

Form. Asp. Comput.

Self Cite

View full text Add to dashboard Cite

show abstract

“…stir.ac.uk/accent. The approach to policies for call control is discussed in [26,27,37]. In fact, a broad view was taken of what a 'call' might be.…”

Section: Call Controlmentioning

confidence: 99%

Policies and conflicts in call control

Turner

Blair

2007

Computer Networks

View full text Add to dashboard Cite

Policy-based management is introduced and related to the specific needs of call control. It is explained how policies differ in important ways from features. Related work on policy-based management is reviewed, leading to the conclusion that a different approach is required for call control. A general architecture is presented for a policy system. This includes an overview of the major policy components, relating them to the system under control and to the context system that provides additional information.As a framework for explaining how policy conflicts are handled, the policy language for call control is briefly presented along with some sample policies. The paper then focuses on how policy conflicts are defined and resolved, using sample resolutions to illustrate the approach. Pointers are given to future enhancements to policy support, including new applications of policies to novel domains.

show abstract

“…The need for policies in call control is explained in [12]. The specialisation of APPEL for call control is fully defined in [17].…”

Section: Policies For Call Controlmentioning

confidence: 99%

Policy support for call control

Turner

Reiff-Marganiec

Blair

et al. 2006

Computer Standards & Interfaces

Self Cite

View full text Add to dashboard Cite

The need for policies to control calls is justified by the changing face of communications. It is argued that call control requires distinctive capabilities in a policy system. A specialised policy language called APPEL (ACCENT Project Policy Environment/Language) has therefore been developed for this purpose. However the policy language is cleanly separated into a core plus specialisations for various application domains. The paper describes both the foundation and the call control ontologies. Sample policy examples are provided to illustrate use for call control. The paper also presents the policy system architecture in which the policy language is interpreted. The components of the policy system are described, particularly the policy server and the policy wizard.

show abstract

Policies: Giving Users Control over Calls

Cited by 7 publications

References 11 publications

From StPowla processes to SRML models

From StPowla processes to SRML models

Policies and conflicts in call control

Policy support for call control

Contact Info

Product

Resources

About