1、 ETSI ES 202 504-3 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 3: Call Notification(Parlay X 3)floppy3 ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-3-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ced
2、ex - 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present docume
3、nt 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 PD
4、F version kept on a specific network drive within ETSI Secretariat. 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 http:/portal.etsi.org/tb/status/statu
5、s.asp If you find errors in the present document, please send your comment to one of the following services: http:/portal.etsi.org/chaircor/ETSI_support.asp Copyright Notification No part may be reproduced except as authorized by written permission. The copyright and the foregoing restriction extend
6、 to reproduction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI
7、registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 7 2 References 7 2.1 Normative references .7 3 Definitions and abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8
8、4 Detailed service description .8 5 Namespaces9 6 Sequence diagrams.9 6.1 SMS notification of a missed call.9 6.2 Media interaction Collection of digits from end user10 6.3 Notification of media interaction11 7 XML Schema data type definition .11 7.1 ActionValues enumeration .11 7.2 Action structure
9、 11 7.3 CallEvents enumeration .12 8 Web Service interface definition12 8.1 Interface: CallDirection12 8.1.1 Operation: handleBusy .12 8.1.1.1 Input message: handleBusyRequest 13 8.1.1.2 Output message: handleBusyResponse .13 8.1.1.3 Referenced faults.13 8.1.2 Operation: handleNotReachable .13 8.1.2
10、.1 Input message: handleNotReachableRequest13 8.1.2.2 Output message: handleNotReachableResponse.13 8.1.2.3 Referenced faults.14 8.1.3 Operation: handleNoAnswer 14 8.1.3.1 Input message: handleNoAnswerRequest .14 8.1.3.2 Output message: handleNoAnswerResponse14 8.1.3.3 Referenced faults.14 8.1.4 Ope
11、ration: handleCalledNumber 14 8.1.4.1 Input message: handleCalledNumberRequest.15 8.1.4.2 Output message: handleCalledNumberResponse15 8.1.4.3 Referenced faults.15 8.2 Interface: CallNotification15 8.2.1 Operation: notifyBusy.15 8.2.1.1 Input message: notifyBusyRequest .15 8.2.1.2 Output message: no
12、tifyBusyResponse 15 8.2.1.3 Referenced faults.16 8.2.2 Operation: notifyNotReachable 16 8.2.2.1 Input message: notifyNotReachableRequest.16 8.2.2.2 Output message: notifyNotReachableResponse16 8.2.2.3 Referenced faults.16 8.2.3 Operation: notifyNoAnswer16 8.2.3.1 Input message: notifyNoAnswerRequest
13、 16 8.2.3.2 Output message: notifyNoAnswerResponse .16 8.2.3.3 Referenced faults.17 8.2.4 Operation: notifyCalledNumber .17 8.2.4.1 Input message: notifyCalledNumberRequest17 ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 4 8.2.4.2 Output message: notifyCalledNumberResponse.17 8.2.4.3 Referenced faults.17
14、8.2.5 Operation: notifyAnswer 17 8.2.5.1 Input message: notifyAnswerRequest .17 8.2.5.2 Output message: notifyAnswerResponse17 8.2.5.3 Referenced faults.17 8.2.6 Operation: notifyPlayAndCollectEvent 18 8.2.6.1 Input message: notifyPlayAndCollectEventRequest.18 8.2.6.2 Output message: notifyPlayAndCo
15、llectEventResponse18 8.2.6.3 Referenced faults.18 8.2.7 Operation: notifyPlayAndRecordEvent 18 8.2.7.1 Input message: notifyPlayAndRecordEventRequest.18 8.2.7.2 Output message: notifyPlayAndRecordEventResponse18 8.2.7.3 Referenced faults.18 8.3 Interface: CallDirectionManager18 8.3.1 Operation: star
16、tCallDirectionNotification.19 8.3.1.1 Input message: startCallDirectionNotificationRequest .19 8.3.1.2 Output message: startCallDirectionNotificationResponse 19 8.3.1.3 Referenced Faults19 8.3.2 Operation: stopCallDirectionNotification.19 8.3.2.1 Input message: stopCallDirectionNotificationRequest .
17、19 8.3.2.2 Output message: stopCallDirectionNotificationResponse 19 8.3.2.3 Referenced Faults20 8.3.3 Operation: startPlayAndCollectNotification.20 8.3.3.1 Input message: startPlayAndCollectNotificationRequest .20 8.3.3.2 Output message: startPlayAndCollectNotificationResponse 20 8.3.3.3 Referenced
18、Faults20 8.3.4 Operation: startPlayAndRecordNotification.20 8.3.4.1 Input message: startPlayAndRecordNotificationRequest .20 8.3.4.2 Output message: startPlayAndRecordNotificationResponse 21 8.3.4.3 Referenced Faults21 8.3.5 Operation: stopMediaInteractionNotification .21 8.3.5.1 Input Message: stop
19、MediaInteractionNotificationRequest .21 8.3.5.2 Output Message: stopMediaInteractionNotificationResponse 21 8.3.5.3 Referenced Faults21 8.4 Interface: CallNotificationManager21 8.4.1 Operation: StartCallNotification.21 8.4.1.1 Input message: startCallNotificationRequest 22 8.4.1.2 Output message: st
20、artCallNotificationResponse .22 8.4.1.3 Referenced Faults22 8.4.2 Operation: stopCallNotification22 8.4.2.1 Input message: stopCallNotificationRequest 22 8.4.2.2 Output message: stopCallNotificationResponse .22 8.4.2.3 Referenced Faults22 9 Fault definitions23 10 Service policies 23 Annex A (normati
21、ve): WSDL for Call Notification 24 Annex B (informative): Bibliography.25 History 26 ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 5 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IP
22、Rs, 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 av
23、ailable on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). 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
24、server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 3 of a multi-
25、part deliverable covering Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“; Part 2: “Third Party Call“; Part 3: “Call Notification“; Part 4: “Short Messaging“; Part 5: “Multimedia Messaging“; Part 6: “Payment“; Part 7: “Account Management“; Part 8: “Terminal St
26、atus“; Part 9: “Terminal Location“; Part 10: “Call Handling“; Part 11: “Audio Call“; Part 12: “Multimedia Conference“; Part 13: “Address List Management“; Part 14: “Presence“; Part 15: “Message Broadcast“; Part 16: “Geocoding“; Part 17: “Application-driven Quality of Service (QoS)“; Part 18: “Device
27、 Capabilities and Configuration“; Part 19: “Multimedia Streaming Control“; Part 20: “Multimedia Multicast Session Management“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay X 3.0 set of
28、specifications. ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 6 The present document is equivalent to 3GPP TS 29.199-03 V7.2.0 (Release 7). ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 7 1 Scope The present document is part 3 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA). T
29、he 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 present document specifies the Call Notification Web Service. The following are defined here: Name spaces. Sequence dia
30、grams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service Policies. WSDL Description of the interfaces. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a
31、specific reference, subsequent revisions do not apply. Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring
32、 document; - for informative references. Referenced documents which are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferab
33、ly, the primary source of the referenced document should be cited, in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full netw
34、ork address, with the same punctuation and use of upper case and lower case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable
35、for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at: htt
36、p:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 504-3 V1.1.1 (2008-05) 8 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and def
37、initions given in ES 202 504-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in ES 202 504-1 2 apply. 4 Detailed service description Currently, in order to determine the handling of a subscriber initiated call in telecommunication networks we have to wr
38、ite applications using specific protocols to access Call Control functions provided by network elements. 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
39、 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 will describe a Parlay X Web Service, Call Notification, for handling calls initiated by a subscriber in the network.
40、A (third party) application determines how the call should be treated. The overall scope of this Web Service is to provide simple functions to application developers to determine how a call should be treated. It is possible to request to end the call, continue the call or re-route the call. Optional
41、ly, it is also possible to request the media type(s) when the action is to re-route the call. It provides, for example, the capability to route a call to an IVR in order to play a video stream to the calling subscriber. A service policy determines if multimedia application control is supported. The
42、media types used in the call can be retrieved using the getMediaForParticipant or getMediaForCall operations of the Audio Call web service. Using the Web Services, application developers can perform simple handling of network-initiated calls without specific Telco knowledge. Examples of usage includ
43、e the following: Incoming call handling: A subscriber receives a call while he is logged-on to the Internet. Since this occupies his telephone connection, he is regarded as busy by the network. The subscriber has an application that is invoked when somebody tries to call him while he is busy. The ap
44、plication provides the subscriber with a list of choices on how to handle the call (e.g. route the call to voicemail or other media server, redirect the call to a secretary, reject the call). Based on the response of the subscriber the call is handled in the network. Alternatively, the call is re-ro
45、uted or released depending on the preferences of the subscriber and some context information (e.g. based on the status or location of the subscriber). Service numbers: An application is triggered whenever a certain service number is dialled. This number is used to connect the caller to one of the ma
46、intenance personnel. The application redirects the call to the appropriate maintenance person based on, e.g. calling party number, time, location and availability of the maintenance personnel. SMS notification of missed calls: An application offers the subscriber the possibility to be notified via S
47、MS whenever he misses a call. The application registers to be notified when calls to its subscribers encounter busy, no-answer or not-reachable. The application does not influence the call treatment, but sends an SMS containing the calling party number, the time and reason why the call was missed. E
48、TSI ETSI ES 202 504-3 V1.1.1 (2008-05) 9 MediaInteraction: An application is provided information regarding the start of a media stream to an end user, the termination of a media stream that the end user is watching, and other media events, e.g. the end-user pausing playback of a media stream. For e
49、xample, starting to stream a video to an end user, the end user pausing the ongoing video stream and the ending of the video stream. 5 Namespaces The CallDirection interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_direction/v3_2 The CallDirectionNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_direction/notification_manager/v3_1 The CallNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_notification/v3_2 The CallNotificationManager interface uses the namesp
