Orchestration in Web Services and Real-Time Communications

Authors:
Lin Lin;P. Lin
Affiliations:
Univ. of Toronto's M.Eng, Toronto;-
Venue:
IEEE Communications Magazine
Year:
2007

Citing 0
Cited 6

A choreography approach for value-added services creation

WiCOM'09 Proceedings of the 5th International Conference on Wireless communications, networking and mobile computing
Applying recommender system based mashup to web-telecom hybrid service creation

GLOBECOM'09 Proceedings of the 28th IEEE conference on Global telecommunications
An open carrier controlled service environment for user generated mobile multimedia services

Proceedings of the 7th International Conference on Advances in Mobile Computing and Multimedia
Development of Web-Telecom based hybrid services orchestration and execution middleware over convergence networks

Journal of Network and Computer Applications
Service oriented testbed infrastructures: a cross-layer approach for NGNs

Mobile Networks and Applications
A platform for user generated multimedia communication services

Journal of Mobile Multimedia

Quantified Score

Hi-index	0.25

Visualization

Abstract

Web services orchestration is now being adopted for the coordination of real-time communications services, including telephony, video and multimedia communications. But do these communications services integrate into workflows in the same way as Web services in the data environment, and are orchestration mechanisms for Web services sufficient for the needs of workflows that involve real-time communications? In this article we explore these questions by taking a look at three approaches to orchestrating workflows: Business Process Execution Language (BPEL), Call Control extensible Markup Language (CCXML), and State Chart extensible Markup Language (SCXML). Through an analysis of these languages, we find that although there are similarities between BPEL as a Web services orchestration language and CCXML/SCXML as orchestration languages for telecom applications, certain key differences, namely procedural vs. event-based representation and coarse vs. fine task granularity, make it more suitable to use these two types of languages together rather than having one replace the other in converged voice-data applications.