|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |
See:
Description
Interface Summary | |
---|---|
ThirdPartyCall | This interface provides the ability to setup, end and determine the status of a call. |
ThirdPartyCall_RI | |
ThirdPartyCallHome | |
ThirdPartyCallService |
Class Summary | |
---|---|
CallInformation | Call information for this call. |
CallInformation_Deser | |
CallInformation_Helper | |
CallInformation_Ser | |
CallStatus | List of call status values. |
CallTerminationCause | List of call termination cause values. |
ThirdPartyCallBindingStub | |
ThirdPartyCallProxy | |
ThirdPartyCallServiceInformation | |
ThirdPartyCallServiceLocator |
Third Party Call.
The present document is part 2 of the Stage 3 Parlay X 2 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, for example, the OSA APIs.
The present document specifies the Third Party Call Web Service. The following are defined here:
* Name spaces.
* Sequence diagrams.
* Data definitions.
* Interface specification plus detailed method descriptions.
* Fault definitions.
* Service Policies.
* WSDL Description of the interfaces.
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
* References are either specific (identified by date of publication and/or edition number or version number) or nonspecific.
* For a specific reference, subsequent revisions do not apply.
* For a non-specific reference, the latest version applies.
Referenced documents which are not found to be publicly available in the expected location might be found at http://docbox.etsi.org/Reference.
[1] W3C Recommendation (2 May 2001): "XML Schema Part 2: Datatypes".
NOTE: Available at http://www.w3.org/TR/2001/REC-xmlschema-2-20010502/. [2] ETSI ES 202 391-1: "Open Service Access (OSA); Parlay X 2 Web Services;
Part 1: Common".
For the purposes of the present document, the terms and definitions given in ES 202 391-1 [2] apply.
For the purposes of the present document, the abbreviations defined in ES 202 391-1 [2] 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 to use Call Control OSA interfaces.
In this clause we describe a Parlay X 2 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 functions without detailed telecommunication knowledge.
Figure 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 2 Interface to initiate a third party call between a broker and his client.
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 method (4) using the Parlay/OSA SCS-CC (Call control) interface. This SCS handles the invocation and sends a message (5) to an MSC to set-up a call between user A and user B.
In an alternative scenario, the Parlay API interaction involving steps (4) and (5) could be replaced with a direct interaction between the Third Party Call Web Service and the Mobile network.
The ThirdPartyCall interface uses the namespace: http://www.csapi.org/wsdl/parlayx/third_party_call/v2_13
The data types are defined in the namespace: http://www.csapi.org/schema/parlayx/third_party_call/v2_13
The 'xsd' namespace is used in the present document to refer to the XML Schema data types defined in XML Schema [1]. The use of the name 'xsd' is not semantically significant.
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.
The following faults are defined for this service.
messageId
SVC0260
text
Call has already been connected, it cannot be cancelled
variables
None
messageId
SVC0261
text
Call has already been terminated
variables
None
These service policies are defined for the Third Party Call service.
ChargingAllowed
xsd:boolean
Is charging allowed for makeCall operation
StatusRetentionTime
xsd:int
Length of time, in seconds, to retain status after the termination of the call
|
||||||||||
PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES |