1、 ETSI ES 202 391-10 V1.3.1 (2008-05)ETSI Standard Open Service Access (OSA); Parlay X Web Services;Part 10: Call Handling(Parlay X 2)floppy3 ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 2 Reference RES/TISPAN-01056-10-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-10 V1.3.1 (2008-05) 3 Contents Intellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 2.1 Normative references .5 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .
8、6 4 Detailed service description .6 5 Namespaces7 6 Sequence diagrams.7 6.1 Setup call handling, query and clear rules7 7 XML Schema data type definition .8 7.1 ConditionalForward structure.8 7.2 UnconditionalForward structure.8 7.3 InteractionContent enumeration .8 7.4 TextInteraction structure 8 7
9、.5 VoiceInteraction union.8 7.6 CallHandlingRules structure 9 7.7 SetRulesResult structure.9 8 Web Service interface definition9 8.1 Interface: CallHandling 9 8.1.1 Operation: setRules.9 8.1.1.1 Input message: setRulesRequest .9 8.1.1.2 Output message: setRulesResponse 9 8.1.1.3 Referenced faults.10
10、 8.1.2 Operation: setRulesForGroup .10 8.1.2.1 Input message: setRulesForGroupRequest10 8.1.2.2 Output message: setRulesForGroupResponse.10 8.1.2.3 Referenced faults.10 8.1.3 Operation: getRules 10 8.1.3.1 Input message: getRulesRequest.11 8.1.3.2 Output message: getRulesResponse11 8.1.3.3 Reference
11、d faults.11 8.1.4 Operation: clearRules .11 8.1.4.1 Input message: clearRulesRequest 11 8.1.4.2 Output message: clearRulesResponse.11 8.1.4.3 Referenced faults.11 9 Fault definitions12 10 Service policies 12 Annex A (normative): WSDL for Call Handling 13 Annex B (informative): Bibliography.14 Histor
12、y 15 ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 4 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
13、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 server (http:/webapp.etsi.org/IPR/home.asp). Pursuant t
14、o 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 server) which are, or may be, or may become, essential to the present document.
15、 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 10 of a multi-part deliverable covering Open Service Access (OSA); Parlay X Web Services, as
16、 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 Status“; Part 9: “Terminal Location“; Part 10: “Call Handling“; Part 11: “Audio
17、Call“; 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 d
18、ocument is equivalent to 3GPP TS 29.199-10 V6.5.0 (Release 6). ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 5 1 Scope The present document is part 10 of the Stage 3 Parlay X 2 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application
19、 developers to make use of network functionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Call Handling Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method des
20、criptions. 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 refer
21、ence 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 n
22、ot 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. Preferably, the primary source of the referenced document should be cited, in ord
23、er 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 network address, with the same punctuation and use of upper case and lower ca
24、se 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 for the application of the present document. For dated references, only t
25、he 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 http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 391-10 V
26、1.3.1 (2008-05) 6 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 purpose
27、s of the present document, the abbreviations given in ES 202 391-1 2 apply. 4 Detailed service description The Call Handling Web Service provides a mechanism for an application to specify how calls are to be handled for a specific number. Call handling includes commonly utilized actions: Call accept
28、ing - only accepting calls from a list of numbers. Call blocking - blocking calls if they are on a blocking list. Conditional call forwarding - changing the destination of a call to another number for a specific calling number. Unconditional call forwarding - changing the destination of a call to an
29、other number. Play audio - initiate audio with the caller (e.g. an announcement or menu). The set of rules are provided to the Web Service which is responsible for establishing the call handling function. Only one action is taken for a call, and once this action is started the rules will stop being
30、processed. There is a specific order in which these rules are processed, providing a predictable call handling expectation for rules provided. The processing is done as follows: 1) Call accepting determines if the call is accepted or rejected. If the caller is not on the accept list, the call is rej
31、ected and rule processing ends. 2) Call blocking determines if the call is rejected. If the caller is on the block list, the call is rejected and rule processing ends. 3) Conditional call forwarding - each calling number that has a specific forwarding instruction is checked, and the call is forwarde
32、d on a match, and rule processing ends. 4) Unconditional call forwarding - the called number is changed to the call forwarding number and rule processing ends. 5) Play audio - the call is handled by a voice system, which handles all further processing of the call. Rule processing ends when the call
33、is handed off. 6) Continue processing call, to complete call to the original called number. If no rules are specified in a particular area, then that step is skipped. If the rule processing ends without any action being indicated, then the call will continue to the called number. Call Handling provi
34、des its function without further interaction with the Application. This is in contrast to the Call Notification interfaces which provide notifications to the Application for processing. ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 7 5 Namespaces The Call Handling interface uses the namespace: http:/www.
35、csapi.org/wsdl/parlayx/call_handling/v2_4 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/call_handling/v2_3 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 semanticall
36、y significant. 6 Sequence diagrams 6.1 Setup call handling, query and clear rules Pattern: Request / Response. This sequence shows the application setting up Call Handling with rules to be processed, querying those rules and clearing them. : Application : Call HandlingProvision call handling for gro
37、upProcess groupsConfigure handlingResultsProvision handling for one addressConfigure handlingGet rules for addressRulesClear rules for addressesProcess groupsClear handlingFigure 1 ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 8 7 XML Schema data type definition 7.1 ConditionalForward structure Informati
38、on on handling of forwarding for specific calling numbers. Element name Element type Optional Description callingAddress xsd:anyURI No Address that call is placed from forwardingAddress xsd:anyURI No Address to forward call to onBusyAddress xsd:anyURI No If line is busy at forwarding address, forwar
39、d to this address onNoAnswerAddress xsd:anyURI No If no answer at forwarding address, forward to this address 7.2 UnconditionalForward structure Information for handling of forwarding unconditionally. Element name Element type Optional Description forwardingAddress xsd:anyURI No Address to forward c
40、all to onBusyAddress xsd:anyURI No If line is busy at forwarding address, forward to this address onNoAnswerAddress xsd:anyURI No If no answer at forwarding address, forward to this address 7.3 InteractionContent enumeration The following are the types of content that may be used for user interactio
41、n. Enumeration value Description TextInfo Text to be processed by a Text-To-Speech engine VoiceXml VoiceXML to be processed by a VoiceXML browser Audio Audio file to be played by an audio processor 7.4 TextInteraction structure Information for processing by a text to speech engine. Element name Elem
42、ent type Optional Description text xsd:string No Text to play through a Text-To-Speech engine language xsd:string No Language of text 7.5 VoiceInteraction union For a call that is to be handled by an interactive voice system, the information to provide to that system. Element name Element type Optio
43、nal Description UnionElement InteractionContent No Type of content provided (one of the following) TextInfo TextInteraction Yes Announcement to play through a Text-To-Speech engine VoiceXml xsd:anyURI Yes Location of VoiceXML to use in a VoiceXML browser Audio xsd:anyURI Yes Location of audio conten
44、t (WAV or MP3 file) ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 9 7.6 CallHandlingRules structure Structure containing set of rules that are applied when the call is handled. Element name Element type Optional Description acceptList xsd:anyURI 0unbounded Yes List of addresses to accept calls from block
45、List xsd:anyURI 0unbounded Yes List of addresses to block calls from forwardList ConditionalForward 0unbounded Yes List of conditional forwarding addresses and destinations forward UnconditionalForward Yes Unconditional call forwarding address voiceInteractionContent VoiceInteraction Yes Forward cal
46、l to a user interaction system with information on content 7.7 SetRulesResult structure Result of setRules operation for each address. Element name Element type Optional Description address xsd:anyURI No Address to be set successful xsd:boolean No Successfully set rules or not error common:ServiceEr
47、ror Yes Error message if unsuccessful 8 Web Service interface definition 8.1 Interface: CallHandling CallHandling provides a rule based processing capability that is accessible to Applications through a set of operations that allow definition of discrete rules. 8.1.1 Operation: setRules Set the call
48、 handling rules for an address (the destination for the call). If a set of rules is already in place for the address, then this operation will replace the old rules with the set provided in this operation. The address may not specify a group. If a group is specified, a PolicyException will be return
49、ed. 8.1.1.1 Input message: setRulesRequest Part name Part type Optional Description address xsd:anyURI No Address to handle calls for rules CallHandlingRules No Rules to apply for this address 8.1.1.2 Output message: setRulesResponse Part name Part type Optional Description None ETSI ETSI ES 202 391-10 V1.3.1 (2008-05) 108.1.1.3 Referenced faults ServiceException from ES 202 391-1 2: SVC0001: Service error. SVC0002: Invalid input value. PolicyException from ES 202 391-1 2: POL0001: Policy error. POL0006: Groups not
