DOC

deliverable_D2_MOVE

By Nicholas Bryant,2014-05-16 01:34
7 views 0
IT

Project Number: AC343

Project Title: MOVE

Deliverable Type: (P/R/L/I)* P

CEC Deliverable Number: AC343/ Siemens / WP2 / DS / P / 02 / a1

Contractual Date of Delivery to the CEC: November 1998

Actual Date of Delivery to the CEC: November 1998

Title of Deliverable: Design of V/D-API and Architecture of the

    VE-MASE

     W2D2 / D2

Workpackage contributing to the Deliverable: WP2

Nature of the Deliverable: (P/R/S/T/O)** R

Author(s): Dominique Carrega, Emmanuel Fournier,

     Hervé Muyal (Tecsi), Michael Krautgärtner,

     Hendrik Decker (Siemens), Michael

     Wallbaum, Jens Meggers (RWTH Aachen),

     Casey Ong (KRDL).

Abstract:

    This document defines the VE-MASE Architecture and the Voice/Data API (V/D-API).

    The first part is the functional, high level specification of the voice-enabled middleware architecture (VE-MASE). A set of VE-MASE Managers offering the voice/data services is defined. These managers are responsible for the functionality of the VE-MASE.

    The second part of the document includes a detailed specification of the V/D-API through which mobile voice enabled services can access the managers’ functionality of the middleware. It takes the requirements from WP1 into account. This part is an important input for WP1 in order to enable WP1 to develop the application.

Keyword list: MOVE, VE-MASE, V/D-API, Services.

    *Type: P-public, R-restricted, L-limited, I-internal

    **Nature: P-Prototype, R-Report, S-Specification, R-Tool, O-Other

HISTORY OF THIS DOCUMENT

    Date Version Status

    July 07, 1998 D2_01.DOC creation of the document.

    August 18 D2_02.DOC second draft

    September 4 D2_03.DOC third draft

    September 23 D2_04.DOC fourth draft

    October 2 D2_05.DOC fifth draft

    October 5 D2_06.DOC sixth draft

    October 7 D2_07.DOC seventh draft

    November 16 D2_08.DOC eighth draft

    November 30 D2_09.DOC ninth draft

ACKNOWLEDGEMENTS

    The VE-MASE and Voice/Data API specification document is the outcome of an effort which started

    in May 98. Many people from the MOVE consortium have invested time in contributing to the VE-MASE and the V/D-API maturation in co-operative spirit. Let them and their companies (here below

    listed) all be acknowledged for the part they played in the set up of this specification.

KENT RIDGE DIGITAL LABS

     ORANGE PCSL

     RHEINISCH WESTFALISCHE TECHNISCHE HOCHSCHULE

     SIEMENS AG

     TECSI

Page 2 Design of V/D-API and Architecture of the VE-MASE AC343 MOVE Deliverable D2 AC343 / Sie / WP2 / R / P / 02 / a1

Table of Content

    1 EXECUTIVE SUMMARY ........................................................................................................ 6 2 INTRODUCTION ...................................................................................................................... 8

    2.1 OBJECTIVES OF THE MOVE PROJECT ........................................................................................ 8 PART I: THE ARCHITECTURE ...................................................................................................... 9 3 THE VE-MASE OVERALL ARCHITECTURE...................................................................... 9 3.1 PHYSICAL VIEW ....................................................................................................................... 9

    3.1.1 The Mobile Client (MC) .................................................................................................. 11

    3.1.2 The Mobility Gateway (MG) ........................................................................................... 11

    3.1.3 The Information Server (IS) ............................................................................................ 11

    3.1.4 The Voice/Data Application Server (V/D-AS) .................................................................. 11

    3.1.5 The Voice/Data Application Client (V/D-AC) .................................................................. 11 3.2 FUNCTIONAL VIEW ................................................................................................................ 12 4 AUDIO GATEWAY ................................................................................................................. 14

    4.1 FUNCTIONAL SPECIFICATION .................................................................................................. 15

    4.1.1 The Gateway Architecture............................................................................................... 16

    4.1.1.1 Media and Channel Selection....................................................................................... 16

    4.1.1.2 Transcoding and Codecs .............................................................................................. 17

    4.1.1.3 Mixing ......................................................................................................................... 17

    4.1.1.4 Application Level Framing .......................................................................................... 17

    4.1.1.5 Network Adaptation .................................................................................................... 17

    4.1.2 The Gateway Client ........................................................................................................ 18

    4.1.3 Signalling Issues ............................................................................................................. 18

    4.1.3.1 End-to-End Signalling Using H.323 ............................................................................. 18

    4.1.3.2 Lightweight Signalling For The Wireless Network ...................................................... 20

     4.1.3.3 Discussion of the Signalling ........................................................................................ 21

    4.2 EXTERNAL INTERFACES.......................................................................................................... 21 4.3 INTERNAL INTERFACES ........................................................................................................... 21 5 SCHEDULER ........................................................................................................................... 23

    5.1 FUNCTIONAL SPECIFICATION .................................................................................................. 24

    5.1.1 The VE-MASE Scheduler ................................................................................................ 25

    5.1.1.1 Service classes ............................................................................................................. 25

    5.1.1.2 QoS parameters ........................................................................................................... 25

    5.2 EXTERNAL INTERFACES.......................................................................................................... 25 5.3 INTERNAL INTERFACES ........................................................................................................... 26 6 CALL MANAGER .................................................................................................................. 27

    6.1 FUNCTIONAL SPECIFICATION (SERVICES) ................................................................................ 27

    6.1.1 Requirements .................................................................................................................. 27

    6.1.2 Presumption ................................................................................................................... 28

    6.1.3 Call Manager in VE-MASE Distributed Architecture ...................................................... 28

    6.1.4 Implementation of Call Manager and Call Manager Proxy ............................................. 29

    6.1.5 Operation ....................................................................................................................... 31

    6.1.6 Session Termination ........................................................................................................ 32

    6.2 EXTERNAL INTERFACES .......................................................................................................... 33 AC343 MOVE Deliverable D2 Design of V/D-API and Architecture of the VE-MASE Page 3 AC343 / Sie / WP2 / R / P / 02 / a1

    NTERNAL INTERFACES ........................................................................................................... 33 6.3 I

    7 COLLABORATION MANAGER ........................................................................................... 34 7.1 FUNCTIONAL SPECIFICATION (SERVICES) ................................................................................ 34

    7.1.1 HTTP dispatching ........................................................................................................... 34

    7.1.2 Notification ..................................................................................................................... 35

    7.1.3 Two implementation options ........................................................................................... 35

    7.2 A PLUG-IN APPROACH TO DECENTRALISED COLLABORATION MANAGEMENT ............................. 36

    7.2.1 Message sequence chart for decentralised collaboration management ............................ 38 7.3 A CENTRALISED APPROACH .................................................................................................... 40

    7.3.1 Message sequence chart for centralised collaboration management................................ 40

    7.3.2 Architecture of a centralised Collaboration Manager ..................................................... 42 7.4 INTERNAL INTERFACES ........................................................................................................... 47 7.5 EXTERNAL INTERFACES .......................................................................................................... 47 8 SYSTEM ADAPTABILITY MANAGER (SAM) ................................................................... 48 8.1 FUNCTIONAL SPECIFICATION .................................................................................................. 48 8.2 QOS CLASSIFICATION ............................................................................................................ 49 8.3 EVENTS ................................................................................................................................. 51

    8.3.1 Network events................................................................................................................ 52

    8.3.2 Transport events ............................................................................................................. 53

    8.3.3 Session events ................................................................................................................. 53

    8.3.4 Application events ........................................................................................................... 53

    8.4 SAM ARCHITECTURE ............................................................................................................. 54 8.5 EXTERNAL INTERFACES.......................................................................................................... 55 8.6 INTERNAL INTERFACES ........................................................................................................... 55 9 ONTHEMOVE MANAGERS ................................................................................................. 56 PART II: THE API ........................................................................................................................... 57

    10 OVERVIEW OF THE V/D-API .............................................................................................. 57 10.1 GENERAL CONCEPTS .............................................................................................................. 57 10.2 FUNCTIONAL DECOMPOSITION OF THE V/D-API ..................................................................... 57

    10.3 DISTRIBUTION OF THE V/D API .............................................................................................. 57 10.4 NOTATIONS AND CONVENTIONS ............................................................................................. 57 10.5 SUMMARY OF THE METHODS................................................................................................... 59 11 AUDIO GATEWAY API ......................................................................................................... 62

    11.1 OVERVIEW OF THE API .......................................................................................................... 62 11.2 SPECIFICATION OF THE API .................................................................................................... 62

    11.2.1 Textual Definition ........................................................................................................... 62

    11.2.2 State Tables .................................................................................................................... 63

    11.2.3 IDL Definition ................................................................................................................ 64

    12 SCHEDULER API ................................................................................................................... 65

    12.1 OVERVIEW OF THE API .......................................................................................................... 65 12.2 SPECIFICATION OF THE API .................................................................................................... 65

    12.2.1 Textual Definition ........................................................................................................... 65

    12.2.2 State Tables .................................................................................................................... 65

    12.2.3 IDL Definition ................................................................................................................ 66

    13 CALL MANAGER API ........................................................................................................... 67

    Page 4 Design of V/D-API and Architecture of the VE-MASE AC343 MOVE Deliverable D2 AC343 / Sie / WP2 / R / P / 02 / a1

    VERVIEW OF THE API (EXTERNAL INTERFACES) ................................................................... 67 13.1 O

    13.2 SPECIFICATION OF THE API (EXTERNAL INTERFACES) ............................................................. 68

    13.3 OVERVIEW OF THE API (INTERNAL INTERFACES) .................................................................... 80

    13.4 SPECIFICATION OF THE API .................................................................................................... 82

     13.4.1 Use of VE-MASE classes by the Call Manager ................................................................ 8314 COLLABORATION MANAGER API ................................................................................... 84 14.1 OVERVIEW OF THE API .......................................................................................................... 84 14.2 SPECIFICATION OF THE API .................................................................................................... 84

    14.2.1 API for the Call Manager Proxy ..................................................................................... 84

    14.2.2 API for the Collaboration Manager ................................................................................ 84

    14.2.3 API for driving the collaboration Manager ..................................................................... 85 15 SYSTEM ADAPTABILITY MANAGER (SAM) API............................................................ 87 15.1 OVERVIEW OF THE API .......................................................................................................... 87 15.2 SPECIFICATION OF THE API .................................................................................................... 87 16 HOW TO USE THE V/D API FOR VOICE/DATA INTEGRATION SERVICES .............. 89

    16.1 PRINCIPLES OF USING VOICE/DATA INTEGRATION FOR EXTENDED SERVICES.............................. 89

    16.2 A GENERIC PROCESS SCENARIO FOR USING EXTENDED VOICE/DATA SERVICES .......................... 89

    16.3 A POSSIBLE TECHNIQUE TO USE THE VOICE/DATA API ............................................................ 92

    17 REFERENCES ......................................................................................................................... 94

    18 ABBREVIATIONS .................................................................................................................. 96

AC343 MOVE Deliverable D2 Design of V/D-API and Architecture of the VE-MASE Page 5 AC343 / Sie / WP2 / R / P / 02 / a1

    XECUTIVE SUMMARY 1 E

    The Deliverable D2 „Design of V/D-API and Architecture of the VE-MASE‟, prepared by

    Workpackage 2 (Voice Enabled Multimedia Application Support Environment, VE-MASE), describes

    the architecture of the VE-MASE (Part I) and the Voice/Data Application Programming Interface (V/D-API) (Part II) for integrated voice and data services. The external V/D-API is specified explicitly whereas the internal APIs between different functional entities of the VE-MASE are described informally. The design including an explicit specification of internal interfaces and the description of their implementation will be given in the Deliverable D5 „Design and Implementation of the VE-

    MASE Prototype‟. The supported voice/data services use the V/D-API and its underlying functionality as offered by the VE-MASE. The V/D-API allows application programs to start voice and data connections and service providers to offer voice enabled mobile services. The Deliverable D2 serves as a basis for the development of the mobile multimedia demonstration service (Workpackage 1, Demonstration Service) which demonstrates the feasibility and market potential of integrated voice and data services. Furthermore, the Deliverable D2 makes use of the Mobile-API developed by the ACTS project 034 OnTheMove [OTM].

    The V/D-API allows applications to signal their quality of service requirements to employed computing and communication subsystems. Application programs are enabled to use voice and data connections without the necessity to explicitly select the underlying transport mechanism. Mobile devices need a mobility gateway that provides an intelligent gateway to the wired infrastructure. By means of a user-supplied profile, the mobility gateway acts as a proxy agent for mobile devices, which cannot always be fully connected, to a network. The mobility gateway knows about the current quality of available wireless links and intelligently schedules communication with the mobile device based on user-supplied profiles.

    The MOVE project has investigated network requirements in terms of quality of service limitations of voice over packet-switched networks like the Internet and over different mobile networks, for example Wireless LANs and GSM. Within the scope of the MOVE project, the actual prototype will

    only be implemented for voice services running on top of data services. The VE-MASE architecture supports integrated voice and data applications. The VE-MASE adapts to the specific transport capabilities of the underlying networks and supplies a set of mobility, voice, and data related management functions:

     The Mobility Gateway (MG) approach supports Voice over IP (VoIP) over mobile networks.

    Examples for its functionality are the harmonisation of new voice sessions and ongoing data

    sessions as well as bandwidth adaptation on the narrowband wireless link.

     The Audio Gateway on the Mobility Gateway provides for real-time audio conferencing

    between peers in a wireless access network and peers located in a fixed network environment.

     The Audio Gateway Client is an application for VoIP running on the Mobile Client, e.g., a

    notebook or a PDA.

     The Scheduler ensures that real-time streams (e.g., audio) are not delayed by non real-time data

    (e.g., collaborative web browsing). Incoming packets are classified according to their service

    class. Quality of Service (QoS) parameters are measured for each stream and signalled to the

    System Adaptability Manager (SAM).

Page 6 Design of V/D-API and Architecture of the VE-MASE AC343 MOVE Deliverable D2 AC343 / Sie / WP2 / R / P / 02 / a1

     The Call Manager is part of the distributed VE-MASE architecture and is responsible for the

    set-up and the termination of a voice/data conference between a mobile client and another client

    with voice/data capability. It controls the audio session (i.e., VoIP) and the collaborative web

    browsing session. The call set-up is based on an existing IP connection; either a call is placed

    from the client terminal or call set-up information is delivered to the proxy gateway where the

    connection is set up to a Voice over IP based terminal, e.g., a call-centre. Depending on real-

    time changes of QoS parameters, the voice/data conference is possibly terminated or only the

    audio session is terminated. The corresponding V/D-API enhances Sun‟s Java-based telephony

    API JTAPI [JTAPI].

     The Collaboration Manager on the Mobility Gateway enables the members of a conference to

    exchange HTML pages and to perform collaborative web browsing. Thus, a kind of push

    mechanism for the forced download of an HTML page in a browser is proposed (HTTP

    dispatch). A notification informs the Collaboration Manager that the corresponding member

    (e.g., Mobile Client) has received the HTML page. A notification is sent to all members of the

    conference after successful completion of the download.

     The MOVE extension of the System Adaptability Manager (SAM) collects events and

    measurements from the Audio Gateway, the Scheduler, and in principle also from the

    Collaboration Manager and the HTTP proxy. The quality of service (QoS) parameters are

    analysed in real-time for real-time audio and non real-time data and the result (e.g., QoS class

    cannot be guaranteed) is delivered to the Call Manager. The function of the SAM extension is to

    perform QoS trading for the complete transmission medium (e.g., voice and data), i.e. by co-

    ordinating per-stream QoS trading.

     The Profile Management (OnTheMove) will give the service provider access to user-specific

    context information (e.g., to a history of HTML downloads preceding a particular information

    access).

     Multi-sensitivity adaptations (OnTheMove): A Location Manager will support applications

    handling location-dependent information and a System Adaptability Manager (SAM) will

    provide information about device capabilities, user preferences and/or network capabilities.

AC343 MOVE Deliverable D2 Design of V/D-API and Architecture of the VE-MASE Page 7 AC343 / Sie / WP2 / R / P / 02 / a1

2 INTRODUCTION

    This Deliverable provides a high level specification of the architecture of the VE-MASE and the V/D-API. This document will be used by WP1 to design and implement the Demonstration Service. The MOVE project will investigate, develop and demonstrate the integration of voice and data services into a middleware for mobile multimedia applications. MOVE will integrate mobile technologies and

    voice services into the European approach for ?information superhighways“. Proper support and adaptations must be given to people who are on the move and need information using mobile network access to their voice/data services.

    2.1 Objectives of the MOVE Project

    The overall objective of the MOVE project is:

    To define and prototype a voice-enabled mobile middleware architecture that integrates voice

    and data services for small user terminals and to derive a common interface for voice-enabled

    mobility support as an enhancement of today‟s networks and part of the UMTS service.

    The main project objectives are consequently derived from this overall objective:

     To design an architecture that supports strong integration of voice and data over UMTS for interactive mobile multimedia services and applications.

To evaluate emerging mobile multimedia protocols integrating voice and data communication

    and architectural approaches well suited for interactive wireless multimedia communication.

To offer an open voice enabled application programming interface (Voice/Data V/D-API) to

    content and service providers for rapid and flexible deployment and operation of voice/data services, supporting on-line user contextual assistance.

To specify and prototype a demonstration service that demonstrates the benefits of the V/D-API.

     To define a demonstration on advanced personal digital assistants or laptops to demonstrate the V/D-API and middleware architecture, and to show the value of the approach for service providers.

To promote the adoption of the V/D-API by the computer industry, application and service

    developers, and standardisation bodies.

To increase commercial and public interest for mobile multimedia information services through

    publications and demonstrations.

By achieving these objectives, MOVE will accelerate the use of voice enabled multimedia

    information services and assist the development of new applications and network embedded mobility support.

Page 8 Design of V/D-API and Architecture of the VE-MASE AC343 MOVE Deliverable D2 AC343 / Sie / WP2 / R / P / 02 / a1

PART I: THE ARCHITECTURE

3 THE VE-MASE OVERALL ARCHITECTURE

    3.1 Physical View

The following diagram panoramically shows the physical architecture of the MOVE demonstrator.

    Some hardware components could, of course, be merged on the same machine, but, as they are

    functionally independent, they will be designed so that they can be distributed on separate computers.

    Mobility Gateway (MG)Information Server (IS)

    Mobile Client (MC)

    Voice/DataApplication Client (V/D-AC)

    Voice/Data Application Server(V/D-AS)

    Voice/DataApplication Client (V/D-AC)

    Figure 3.1: VE-MASE Hardware architecture

AC343 MOVE Deliverable D2 Design of V/D-API and Architecture of the VE-MASE Page 9 AC343 / Sie / WP2 / R / P / 02 / a1

    The following figure shows the software architecture of the MOVE architecture.

    Mobility Gateway (MG) Information Server (V/D AS)

    with HTTP Server Mobile Client (MC) V/D API

    V/D API Voice Over IP V/D Scheduler

    Audio Gateway Web Site MASE Client

     System Call Manager Adaptability

    Manager

    MASE Gateway

    Collaboration

    Manager

    Call Mgr Proxy

    Voice/Data Application

    Client (V/D AC)

    Voice/Data Application

    Server (V/D AS)

    V/D API

    Voice/Data Application

    Client (V/D AC) Call Manager

    Voice Over IP

    Figure 3.2: VE-MASE Software architecture

    Page 10 Design of V/D-API and Architecture of the VE-MASE AC343 MOVE Deliverable D2 AC343 / Sie / WP2 / R / P / 02 / a1

Report this document

For any questions or suggestions please email
cust-service@docsford.com