ETSI TS 129 199-2 V8.0.0 (2009-02)

ETSI TS 129 199-2 V8.0.0 (2009-02)
Technical Specification
Universal Mobile Telecommunications System (UMTS);
LTE;
Open Service Access (OSA);
Parlay X web services;
Part 2: Third party call
(3GPP TS 29.199-02 version 8.0.0 Release 8)
---------------------- Page: 1 ----------------------
3GPP TS 29.199-02 version 8.0.0 Release 8 1 ETSI TS 129 199-2 V8.0.0 (2009-02)
Reference
RTS/TSGC-0029199-02v800
Keywords
LTE, UMTS
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE
Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16
Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture de Grasse (06) N° 7803/88
Important notice
Individual copies of the present document can be downloaded from:
http://www.etsi.org

The present document may be made available in more than one electronic version or in print. In any case of existing or

perceived difference in contents between such versions, the reference version is the Portable Document Format (PDF).

In case of dispute, the reference shall be the printing on ETSI printers of the PDF version kept on a specific network drive

Users of the present document should be aware that the document may be subject to revision or change of status.

Information on the current status of this and other ETSI documents is available at

If you find errors in the present document, please send your comment to one of the following services:

DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered

3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.

GSM® and the GSM logo are Trade Marks registered and owned by the GSM Association.

IPRs essential or potentially essential to the present document may have been declared to ETSI. The information

pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-members, and can be found

in ETSI SR 000 314: "Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in

respect of ETSI standards", which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web

Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee

can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web

This Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project (3GPP).

The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or

GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables.

The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under

Intellectual Property Rights................................................................................................................................2

Foreword.............................................................................................................................................................2

Foreword.............................................................................................................................................................5

Introduction ........................................................................................................................................................5

1 Scope........................................................................................................................................................6

2 References................................................................................................................................................6

3 Definitions and abbreviations...................................................................................................................6

3.1 Definitions..........................................................................................................................................................6

3.2 Abbreviations.....................................................................................................................................................7

4 Detailed service description .....................................................................................................................7

5 Namespaces..............................................................................................................................................9

6 Sequence diagrams...................................................................................................................................9

6.1 'Click to Dial' call setup......................................................................................................................................9

6.2 Third party call with announcement between broker and customer.................................................................10

7 XML Schema data type definition .........................................................................................................10

8 Web Service interface definition............................................................................................................11

8.1 Interface: ThirdPartyCall..................................................................................................................................11

8.1.1 Operation: MakeCallSession......................................................................................................................11

8.1.1.1 Input message: MakeCallSessionRequest.............................................................................................11

8.1.1.2 Output message : MakeCallSessionResponse.......................................................................................12

8.1.1.3 Referenced faults...................................................................................................................................12

8.1.1a Operation: AddCallParticipant....................................................................................................................12

8.1.1a.1 Input Message : AddCallParticipantRequest.........................................................................................12

8.1.1a.2 Output message : AddCallParticipantResponse ....................................................................................12

8.1.1a.3 Referenced faults...................................................................................................................................12

8.1.1b Operation: TransferCallParticipant.............................................................................................................13

8.1.1b.1 Input Message : TransferCallParticipantRequest ..................................................................................13

8.1.1b.2 Output message : TransferCallParticipantResponse .............................................................................13

8.1.1b.3 Referenced faults...................................................................................................................................13

8.1.2 Operation: GetCallParticipantInformation..................................................................................................14

8.1.2.1 Input message: GetCallParticipantInformationRequest........................................................................14

8.1.2.2 Output message : GetCallParticipantInformationResponse ..................................................................14

8.1.2.3 Referenced faults...................................................................................................................................14

8.1.3 Void............................................................................................................................................................14

8.1.4 Void............................................................................................................................................................14

8.1.5 Operation: GetCallSessionInformation.......................................................................................................14

8.1.5.1 Input message: GetCallSessionInformationRequest.............................................................................14

8.1.5.2 Output message : GetCallSessionInformationResponse .......................................................................15

8.1.5.3 Referenced faults...................................................................................................................................15

8.1.6 Operation: DeleteCallParticipant................................................................................................................15

8.1.6.1 Input message: DeleteCallParticipantRequest.......................................................................................15

8.1.6.2 Output message: DeleteCallParticipantResponse..................................................................................15

8.1.6.3 Referenced faults...................................................................................................................................15

8.1.7 Operation: EndCallSession.........................................................................................................................16

8.1.7.1 Input message: EndCallSessionRequest................................................................................................16

8.1.7.2 Output message: EndCallSessionResponse...........................................................................................16

8.1.7.3 Referenced faults...................................................................................................................................16

9 Fault definitions......................................................................................................................................17

9.1 ServiceException..............................................................................................................................................17

9.1.1 SVC0260: Void ..........................................................................................................................................17

9.1.2 SVC0261: Call Session already terminated ................................................................................................17

10 Service policies ......................................................................................................................................17

Annex A (normative): WSDL for Third Party Call..........................................................................18

Annex B (informative): Description of Parlay X Web Services Part 2: Third party call for

3GPP2 cdma2000 networks ..........................................................................19

B.1 General Exceptions.................................................................................................................................19

B.2 Specific Exceptions................................................................................................................................19

B.2.1 Clause 1: Scope ................................................................................................................................................19

B.2.2 Clause 2: References ........................................................................................................................................19

B.2.3 Clause 3: Definitions and abbreviations...........................................................................................................19

B.2.4 Clause 4: Detailed service description..............................................................................................................19

B.2.5 Clause 5: Namespaces ......................................................................................................................................19

B.2.6 Clause 6: Sequence diagrams ...........................................................................................................................20

B.2.7 Clause 7: XML Schema data type definition....................................................................................................20

B.2.8 Clause 8: Web Service interface definition ......................................................................................................20

B.2.9 Clause 9: Fault definitions................................................................................................................................20

B.2.10 Clause 10: Service policies...............................................................................................................................20

B.2.11 Annex A (normative): WSDL for Third Party Call..........................................................................................20

Annex C (informative): Change history ...............................................................................................21

History ..............................................................................................................................................................22

This Technical Specification has been produced by the 3 Generation Partnership Project (3GPP).

3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay

Group is pleased to see 3GPP acknowledge and publish the present document, and the Parlay Group looks forward to

working with the 3GPP community to improve future versions of the present document.

The contents of the present document are subject to continuing work within the TSG and may change following formal

TSG approval. Should the TSG modify the contents of the present document, it will be re-released by the TSG with an

y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections,

z the third digit is incremented when editorial only changes have been incorporated in the document.

The present document is part 2 of a multi-part deliverable covering the 3 Generation Partnership Project; Technical

Specification Group Core Network and Terminals; Open Service Access (OSA); Parlay X Web Services, as identified

The present document is Part 2 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA).

The OSA specifications define an architecture that enables application developers to make use of network functionality

through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are

contained in 3GPP TS 23.127 [3]. The requirements for OSA are contained in 3GPP TS 22.127 [2].

The present document specifies the Third Party Call Web Service aspects of the interface. All aspects of the Third Party

The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group.

The following documents contain provisions which, through reference in this text, constitute provisions of the present

• References are either specific (identified by date of publication, edition number, version number, etc.) or

• For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including

a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same

[2] 3GPP TS 22.127: "Service Requirement for the Open Services Access (OSA); Stage 1".

[3] 3GPP TS 23.127: "Virtual Home Environment (VHE) / Open Service Access (OSA); Stage 2".

[6] 3GPP TS 29.199-1: "Open Service Access (OSA); Parlay X Web Services; Part 1: Common".

[7] 3GPP TS 29.199-12: "Open Service Access (OSA); Parlay X Web Services; Part 12: Multimedia

For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 [6] apply.

For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 [6] apply.

Currently, in order to perform a third party call in telecommunication networks we have to write applications using

specific protocols to access Call Control functions provided by network elements (specifically operations to initiate a

call from applications). This approach requires a high degree of network expertise. We can also use the OSA gateway

approach, invoking standard interfaces to gain access to call control capabilities, but these interfaces are usually

perceived to be quite complex by application IT developers. Developers must have advanced telecommunication skills

In this subclause we describe a Parlay X Web Service, Third Party Call, for creating and managing a call initiated by an

application (third party call). The overall scope of this Web Service is to provide functions to application developers to

create a call in a simple way. Using the Third Party Call Web Service, application developers can invoke call handling

• Call Session: a call (uniquely identified) to which participants can be added/removed.

• Call Participant: each of the call parties (uniquely identified) involved in the call session.

• Media: the call can utilize multiple media types to support the participants' communication. In particular both

audio and video streams are available, including the specific stream direction (i.e. incoming, outgoing,

NOTE 1: Call participants in a Call Session are anticipated to be uniquely identifiable using their URI address.

An application setting up a call session must initially invoke the makeCallSession. The result of such invocation is the

creation of a "context" that represents a call session with usually two participants, or at a minimum one participant

connected, a unique identifier is assigned to the just-created call session. Subsequently the application may wish to add,

remove, park or transfer call participants. In order to do so the operations addCallParticipant,

transferCallParticipant, deleteCallParticipant can be used. Furthermore the call session or call participant status

including the media details can be read. In order to do so the operations getCallParticipantInformation, and

getCallSessionInformation can be used. It is also possible to retrieve the media details on its own using the

getMediaForParticipant or getMediaForCall operations of the Audio Call web service.

The application can also force the call session and all its participants to be terminated with the operation

NOTE 2: A call session allows the application to avail of other web service features that can add value to the

created call session. For example the Audio Call web service can provide multimedia message delivery to

call participants in the call session (playXXXMessage operation) and furthermore control of the media

types for the call participants thus enabling conversational multimedia communication including voice,

Figure 4.1 shows a scenario using the Third Party Call Web Service to handle third party call functions. The application

invokes a Web Service to retrieve stock quotes and a Parlay X Interface to initiate a third party call between a broker

In the scenario, whenever a particular stock quote reaches a threshold value (1) and (2), the client application invokes a

third party call between one or more brokers and their corresponding customers to decide actions to be taken. After

invocation (3) by the application, the Third Party Call Web Service invokes a Parlay API operation (4) using the

Parlay/OSA SCS-CC (Call control) interface. This SCS handles the invocation and sends a message (5) to an MSC to

In an alternative scenario, the Parlay API interaction involving steps (4) and (5) could be replaced with a direct

The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in XML Schema

A common convergence application is Click to Dial, where a self service portal provides a web page that can initiate a

call between two phones. This sequence shows a basic call setup, and ending the call through the portal.

This sequence shows the third party call with announcement between broker and customer in addition to basic flow of

figure 4.1. It could be realized through invoking TPC and AC web services with same session identifier. If the broker

gets the announcement of information related to this call, he can get more information before talking to his customer.

This interface provides the ability to setup a call session, add and delete a call participant, transfer a call participant

from one call session into another call session, determine the status of an individual call participant or a complete call

The invocation of MakeCallSession requests to set-up a call session between two addresses, a first CallParticipant

('A-Party') and a second CallParticipant ('B-Party'), provided that the invoking application is allowed to connect them.

Optionally, the caller"s ('A-Party"s') name is provided. Optionally a call session with only a single CallParticipant ('A-

party') can be set-up, for example to play media to the call participant using mediaCall capabilities (e.g.

playMedia).Optionally the application can also indicate the charging information (Charging). Optionally, the media

type(s) to be used for the participants in the call session can be requested (MediaInfo). A service policy details if

multimedia application control is supported. If the parameter MediaInfo is omitted, the media type(s) shall be

negotiated by the underlying network. A CallSessionIdentifier is returned on invocation of the MakeCallSession. This

CallSessionIdentifier may be used to retrieve the call session status for all the call participants including their media

type information with the operation getCallSessionInformation. With the operation getCallParticipantInformation

During call set-up, the first CallParticipant ('A-Party') might wait for the second CallParticipant ('B-Party') to answer

the call hearing ringback tone. MakeCallSession creates a call session with one or two call participants and generates a

new CallSessionIdentifier which is identified by the string returned in the MakeCallSessionResponse operation. The

invocation returns as soon as the request is received by the system, i.e. the actual call session is established

In order to receive the information on call status the application has to explicitly invoke the

CallParticipants xsd:anyURI[1..2] No It contains the address of the first participant,