1、 ETSI ES 202 391-3 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 3: Call Notification(Parlay X 2)floppy3 ETSI ETSI ES 202 391-3 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-03-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Ce
2、dex - 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 docum
3、ent 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 P
4、DF 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/stat
5、us.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 exten
6、d 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 391-3 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 2.1 Normative references .6 3 Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .7
8、 4 Detailed service description .7 5 Namespaces7 6 Sequence diagrams.8 6.1 SMS notification of a missed call.8 7 XML Schema data type definition .8 7.1 ActionValues enumeration .8 7.2 Action structure 9 7.3 CallEvents enumeration .9 8 Web Service interface definition9 8.1 Interface: CallDirection9 8
9、.1.1 Operation: handleBusy .10 8.1.1.1 Input message: handleBusyRequest 10 8.1.1.2 Output message: handleBusyResponse .10 8.1.1.3 Referenced faults.10 8.1.2 Operation: handleNotReachable .10 8.1.2.1 Input message: handleNotReachableRequest10 8.1.2.2 Output message: handleNotReachableResponse.11 8.1.
10、2.3 Referenced faults.11 8.1.3 Operation: handleNoAnswer 11 8.1.3.1 Input message: handleNoAnswerRequest .11 8.1.3.2 Output message: handleNoAnswerResponse11 8.1.3.3 Referenced faults.11 8.1.4 Operation: handleCalledNumber 11 8.1.4.1 Input message: handleCalledNumberRequest.12 8.1.4.2 Output message
11、: handleCalledNumberResponse12 8.1.4.3 Referenced faults.12 8.2 Interface: CallNotification12 8.2.1 Operation: notifyBusy.12 8.2.1.1 Input message: notifyBusyRequest .12 8.2.1.2 Output message: notifyBusyResponse 12 8.2.1.3 Referenced faults.12 8.2.2 Operation: notifyNotReachable 12 8.2.2.1 Input me
12、ssage: notifyNotReachableRequest.13 8.2.2.2 Output message: notifyNotReachableResponse13 8.2.2.3 Referenced faults.13 8.2.3 Operation: notifyNoAnswer13 8.2.3.1 Input message: notifyNoAnswerRequest 13 8.2.3.2 Output message: notifyNoAnswerResponse .13 8.2.3.3 Referenced faults.13 8.2.4 Operation: not
13、ifyCalledNumber .13 8.2.4.1 Input message: notifyCalledNumberRequest13 8.2.4.2 Output message: notifyCalledNumberResponse.14 8.2.4.3 Referenced faults.14 ETSI ETSI ES 202 391-3 V1.3.1 (2008-05) 4 8.3 Interface: CallDirectionManager14 8.3.1 Operation: startCallDirectionNotification.14 8.3.1.1 Input m
14、essage: startCallDirectionNotificationRequest .14 8.3.1.2 Output message: startCallDirectionNotificationResponse 14 8.3.1.3 Referenced Faults14 8.3.2 Operation: stopCallDirectionNotification.15 8.3.2.1 Input message: stopCallDirectionNotificationRequest .15 8.3.2.2 Output message: stopCallDirectionN
15、otificationResponse 15 8.3.2.3 Referenced Faults15 8.4 Interface: CallNotificationManager15 8.4.1 Operation: StartCallNotification.15 8.4.1.1 Input message: startCallNotificationRequest 15 8.4.1.2 Output message: startCallNotificationResponse .15 8.4.1.3 Referenced Faults16 8.4.2 Operation: stopCall
16、Notification16 8.4.2.1 Input message: stopCallNotificationRequest 16 8.4.2.2 Output message: stopCallNotificationResponse .16 8.4.2.3 Referenced Faults16 9 Fault definitions16 10 Service policies 16 Annex A (normative): WSDL for Call Notification 17 Annex B (informative): Bibliography.18 History 19
17、ETSI ETSI ES 202 391-3 V1.3.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 IPRs, if any, is publicly available for ETSI members and non-members, and can be found
18、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 server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the
19、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 server) which are, or may be, or may become, essential to the present document. Forew
20、ord 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-part deliverable covering Open Service Access (OSA); Parlay X Web Services, as identi
21、fied 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 Status“; Part 9: “Terminal Location“; Part 10: “Call Handling“; Part 11: “Audio Call“;
22、Part 12: “Multimedia Conference“; Part 13: “Address List Management“; Part 14: “Presence“. 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 2.2 set of specifications. The present document
23、 is equivalent to 3GPP TS 29.199-03 V6.6.0 (Release 6). ETSI ETSI ES 202 391-3 V1.3.1 (2008-05) 6 1 Scope The present document is part 3 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application develope
24、rs 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 diagrams. Data definitions. Interface specification plus detailed method descript
25、ions. 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 specific reference, subsequent revisions do not apply. Non-specific reference
26、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 document; - for informative references. Referenced documents which are not fo
27、und 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. Preferably, the primary source of the referenced document should be cited, in order to
28、 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 network address, with the same punctuation and use of upper case and lower case le
29、tters. 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 for the application of the present document. For dated references, only the ed
30、ition 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: http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 391-3 V1.3.1
31、 (2008-05) 7 2 ETSI ES 202 391-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 2)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 391-1 2 apply. 3.2 Abbreviations For the purposes of
32、the present document, the abbreviations given in ES 202 391-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 write applications using specific protocols to access Call Control functions pro
33、vided 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 are usually perceived to be quite complex by application IT developers. Devel
34、opers must have advanced telecommunication skills to use Call Control OSA interfaces. In this clause we will describe a Parlay X 2 Web Service, Call Notification, for handling calls initiated by a subscriber in the network. A (third party) application determines how the call should be treated. The o
35、verall scope of this Web Service is to provide simple functions to application developers to determine how a call should be treated. Using the Web Services, application developers can perform simple handling of network-initiated calls without specific Telco knowledge. Examples of usage include the f
36、ollowing: 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 applicati
37、on provides the subscriber with a list of choices on how to handle the call (e.g. route the call to voicemail, 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-routed or released depending on
38、 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 maintenance personnel. The appl
39、ication 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 SMS whenever he misses a call.
40、 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. 5 Namespaces The CallDirection
41、 interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_direction/v2_3 The CallDirectionNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_direction/notification_manager/v2_5 ETSI ETSI ES 202 391-3 V1.3.1 (2008-05) 8 The CallNotification interface us
42、es the namespace: http:/www.csapi.org/wsdl/parlayx/call_notification/v2_3 The CallNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/call_notification/notification_manager/v2_5 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/call_notifi
43、cation/v2_2 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. 6 Sequence diagrams 6.1 SMS notification of a missed call Showing the use of the CallNotification and Short Messag
44、ing Web Services, an SMS is sent to a person who misses a call (no answer). This sequence assumes that the provisioning of the “no answer“ call notification has occurred independently. Application Call NotificationWeb ServiceShort MessagingWeb Service(ref. Part 4)notifyNoAnswerResponsenotifyNoAnswer
45、Request“A does not answer”event report (call monitor mode)sendSmsResponsesendSmsRequestSends an SMS “missed call”notification to AFigure 1 7 XML Schema data type definition 7.1 ActionValues enumeration The ActionValues data type is an enumeration with the following values. ETSI ETSI ES 202 391-3 V1.
46、3.1 (2008-05) 9 Enumeration value Description Route Request to (re-)route the call to the address indicated with routingAddress. Continue Request to continue the call without any changes. This will result in normal handling of the event in the network. EndCall Request to end the call. This will resu
47、lt in termination of the call. The callingParty will receive a tone or announcement. 7.2 Action structure The Action data type is a structure containing the following parameters. Element name Element type Optional Description actionToPerform ActionValues No Indicates the action as described below ro
48、utingAddress xsd:anyURI Yes The address to be used in case the action indicates “Route“ charging common:ChargingInformation Yes Charge to apply to this call 7.3 CallEvents enumeration The CallEvents data type is an enumeration with the following values. Enumeration value Description Busy Called part
49、y is busy. NotReachable Called party is not reachable. NoAnswer Called party does not answer. CalledNumber A call between two parties is being attempted. 8 Web Service interface definition 8.1 Interface: CallDirection This clause describes an initial set of capabilities in terms of message invocations, parameters and data types. The message-based invocations are: handleBusy. handleNotReachable. handleNoAnswer. handleCalledNumber. These messages are initiated by the Call Notification Web Service (running in a Parlay X 2 Gateway) and i
