1、 ETSI TR 102 397-10-1 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 10: Call Handling Mapping;Sub-part 1: Mapping to Generic Call Control and User InteractionETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-
2、10-01-OSA Keywords API, OSA, service 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 enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual
3、 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 For
4、mat (PDF). In case of dispute, the reference shall be the printing on ETSI printers of the PDF 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
5、status of this and other ETSI documents is available at http:/portal.etsi.org/tb/status/status.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 e
6、xcept as authorized by written permission. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2005. The Parlay Group 2005. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the bene
7、fit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being registered by ETSI for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 3 Contents I
8、ntellectual Property Rights4 Foreword.4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .5 4 Mapping description.5 5 Sequence diagrams.6 5.1 Enabling call notifications6 5.2 Disabling call notifications.7 5.3 Processing a call: Route to original destinat
9、ion8 5.4 Processing a call: Perform user interaction 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 ETSI
10、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. Foreword T
11、his Technical Report (TR) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 10, sub-part 1 of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay X W
12、eb Services to Parlay/OSA APIs, as identified below: Part 1: “Common Mapping“; Part 2: “Third Party Call Mapping“; Part 3: “Call Notification Mapping“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8:
13、“Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Sub-part 1: “Mapping to Generic Call Control and User Interaction“; Sub-part 2: “Mapping to Multi-Party Call Control and User Interaction“; Part 11: “Audio Call Mapping“; Part 12: “Multimedia Conference
14、 Mapping“; Part 14: “Presence Mapping“. NOTE: Part 13 has not been provided as there is currently no defined mapping between ES 202 391-13 4 and the Parlay/OSA APIs. If a mapping is developed, it will become part 13 of this series. The present document has been defined jointly between ETSI, The Parl
15、ay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 5 1 Scope The present document specifies the mapping of the Parlay X Call Handling Web Service to the Generic Call Control and User Interaction Service Capability Features (SCFs). The Parlay X Web Services provi
16、de powerful yet simple, highly abstracted, imaginative, telecommunications functions that application developers and the IT community can both quickly comprehend and use to generate new, innovative applications. The Open Service Access (OSA) specifications define an architecture that enables applica
17、tion developers to make use of network functionality through an open standardized interface, i.e. the Parlay/OSA APIs. 2 References For the purposes of this Technical Report (TR), the following references apply: 1 ETSI TR 121 905: “Universal Mobile Telecommunications System (UMTS); Vocabulary for 3G
18、PP Specifications (3GPP TR 21.905)“. 2 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 3 ETSI TR 102 397-1: “Open Service Access (OSA); Mapping of Parlay X Web Services to Parlay/OSA APIs; Part 1: Common Mapping“
19、. 4 ETSI ES 202 391-13: “Open Service Access (OSA); Parlay X Web Services; Part 13: Address List Management“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 102 397-1 3 apply. 3.2 Abbreviations For the purposes of the p
20、resent document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Call Handling capability can be implemented with Parlay/OSA Generic Call Control and User Interaction. It is applicable to ETSI OSA 1.x/2.x/3.x, Parlay/OSA 3.x/4.x/5.x and 3GPP Releases 4 to 6. ETSI ETSI TR 1
21、02 397-10-1 V1.1.1 (2005-08) 6 5 Sequence diagrams 5.1 Enabling call notifications Application Call Handling IpAppCall Control Manager Control Manager enableCallNotification i.e. INTERRUPT mode, P EVENT GCCS ADDRESS ANALYSED EVENT “new“ setRulesForGroupRequest enableCallNotification i.e. INTERRUPT m
22、ode, P EVENT GCCS ADDRESS ANALYSED EVENT enableCallNotification i.e. INTERRUPT mode, P EVENT GCCS ADDRESS ANALYSED EVENT setRulesForGroupResponse getRulesRequest getRulesResponse IpCall Figure 1 ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 7 5.2 Disabling call notifications Application Call Handling I
23、pAppCall Control Manager IpCall Control Manager disableCallNotification clearRulesRequest disableCallNotification disableCallNotification clearRulesResponse Figure 2 ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 8 5.3 Processing a call: Route to original destination Call Notification IpAppCall Control
24、Manager IpCall Control Manager IpApp Call IpCall “A attempting to call B“ “new“ callEventNotify: P_EVENT_GCCS_ADDRESS_ANALYSED_EVENT“forward event“ “new“ OPTIONAL: setChargePlan deassignCall “destroy“ Appl Evaluate rules for calls from A to B Action= Route to B EITHER routeReq() with no address modi
25、fication OR continue Processing() - Parlay 3.4/4.2/5.0 later versions) Figure 3 ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 9 5.4 Processing a call: Perform user interaction sequential rule-based processing of originating call attempts, which is discussed (in order of precedence) in clauses 6.1.4 thr
26、ough 6.1.10. 6.1.1 setRules and setRulesForGroup These operations set up (or replace as applicable) the set of rules associated with a destination address or addresses. Call notification is established with the Call Control service for the termination address for the receipt of a call attempt notifi
27、cation. The sequence diagram in clause 5.1 illustrates the flow for these operations. They are mapped to the Parlay/OSA method: IpCallControlManager.enableCallNotification. 6.1.1.1 Mapping to IpCallControlManager.enableCallNotification The IpCallControlManager.enableCallNotification method is invoke
28、d with the following parameters. Name Type Comment appCallControl Manager IpAppCallControl ManagerRef Specifies the interface for receiving call-related event notifications associated with the criteria contained in the eventCriteria. eventCriteria TpCallEventCriteria Specifies event-related data, wh
29、ich is mapped from the parts of the setRulesForGroupRequest message as described in clause 6.1.1.2. The result from IpCallControlManager.enableCallNotification is of type TpAssignmentID. It is used internally by the Call Handling web service to correlate the Parlay/OSA callbacks, e.g. IpAppCallContr
30、olManager.callEventNotify, when a call-related event, which is associated with the criteria contained in the eventCriteria element, is triggered in the network. Parlay exceptions thrown by IpCallControlManager.enableCallNotification are mapped to Parlay X exceptions as defined in clause 6.2. 6.1.1.2
31、 Mapping from setRulesForGroupRequest to eventCriteria The elements of the eventCriteria data type are derived from the parts of the setRulesForGroupRequest message as follows. Name Type Comment DestinationAddress TpAddressRange Specifies the destination address of the call, which is derived from th
32、e URI in the addresses part of setRulesForGroupRequest, as described in TR 102 397-1 3. OriginatingAddress TpAddressRange Not mapped. Specifies the origination address of the call: i.e. null CallEventName TpCallEventName Name of the event: i.e. P_EVENT_GCCS_ADDRESS_ANALYSED_EVENT. CallNotificationTy
33、pe TpCallNotificationType Specifies that the notification is related to the call destination. MonitorMode TpCallMonitorMode Defines the mode that the call is in following the notification: i.e. P_CALL_MONITOR_MODE_INTERRUPT. ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 126.1.2 getRules This operation
34、does not interact with any network elements, it returns the configured rules for an address. The sequence diagram in clause 5.1 illustrates the flow for this operation. 6.1.3 clearRules This operation disables the call notification from the Call Control service, and clears the related rules informat
35、ion stored by the service. The sequence diagram in clause 5.2 illustrates the flow for these operations. They are mapped to the Parlay/OSA method: IpCallControlManager.disableCallNotification. 6.1.3.1 Mapping to IpCallControlManager.disableCallNotification The IpCallControlManager.disableCallNotific
36、ation method is invoked with the following parameters. Name Type Comment assignmentID TpAssignmentID Specifies the assignment ID returned after an earlier invocation of IpCallControlManager.enableCallNotification method. Parlay exceptions thrown by IpCallControlManager.disableCallNotification are ma
37、pped to Parlay X exceptions as defined in clause 6.2. 6.1.4 CallHandlingRules.AcceptList Rule Processing Call accepting determines if the call is accepted or rejected. If the accept list associated with the called party (B) is null, then CallHandlingRules.AcceptList rule processing ends: processing
38、continues with CallHandlingRules.BlockList Rule Processing. If the calling party (A) is not a member of Bs accept list, the call attempt by A is rejected: processing continues with clause 6.1.10 CallHandlingRules: Reject Call Attempt. Otherwise the calling party (A) is a member of Bs accept list, th
39、e call attempt by A is not rejected: processing continues with CallHandlingRules.ForwardList Rule Processing. Rule processing is invoked by the Parlay/OSA method: IpAppCallControlManager. callEventNotify, as illustrated in clauses 5.3, 5.4 and 5.5. 6.1.4.1 Mapping from IpAppCallControlManager.callEv
40、entNotify The IpAppCallControlManager.callEventNotify method is invoked with the following parameters. Name Type Comment callReference TpCallIdentifier Specifies the reference to the call interface to which the notification relates. eventInfo TpCallEventInfo Specifies event-related data, which is ma
41、pped to the Call Handling rule database as described in clause 6.1.4.2. assignmentID TpAssignmentID Specifies the assignment id returned after an earlier invocation of IpCallControlManager.enableCallNotification method, when the criteria associated with this call-related event were activated in the
42、network, as described in clause 6.1.1.1. It is used internally by the Call Notification web service to correlate the Parlay/OSA callbacks. The result from IpAppCallControlManager.callEventNotify is of type IpAppCallRef, which specifies a reference to the application interface which implements the ca
43、llback interface for the new call. ETSI ETSI TR 102 397-10-1 V1.1.1 (2005-08) 136.1.4.2 Mapping from TpCallEventInfo to Call Handling Rule Database The elements of the TpCallEventInfo data type are mapped to the Call Handling rule database as follows. Name Type Comment DestinationAddress TpAddress T
44、he called party B. Used as an index into the rule database to locate the CallHandlingRules structure for B. Mapped to the URI in the address(es) part of a setRules(ForGroup)Request message, as described in TR 102 397-1 3. OriginatingAddress TpAddress The calling party A. Mapped to a URI provided in
45、the CallHandlingRules structure for B, as described in TR 102 397-1 3. Matched against the contents of one or more of the following lists: CallHandlingRules.AcceptList CallHandlingRules.BlockList CallHandlingRules.ForwardList.CallingAddress. OriginalDestination Address TpAddress Not mapped. Redirect
46、ingAddress TpAddress Not mapped. CallAppInfo TpCallAppInfoSet Not mapped. CallEventName TpCallEventName Not mapped. This element has a value of P_EVENT_GCCS_ADDRESS_ANALYSED_EVENT. CallNotificationType TpCallNotificationType Not mapped. MonitorMode TpCallMonitorMode Not mapped. This element has a va
47、lue of “P_CALL_MONITOR_MODE_INTERRUPT“. 6.1.5 CallHandlingRules.BlockList Rule Processing Call blocking determines if the call is rejected. If the block list associated with the called party (B) is null, the call attempt by A is not rejected: processing continues with CallHandlingRules.ForwardList R
48、ule Processing. If the calling party (A) is not a member of Bs block list, the call attempt by A is not rejected: processing continues with CallHandlingRules.ForwardList Rule Processing. Otherwise the calling party (A) is a member of Bs block list, the call attempt by A is rejected: processing conti
49、nues with clause 6.1.10 CallHandlingRules: Reject Call Attempt. Rule processing is invoked by the Parlay/OSA method: IpAppCallControlManager. callEventNotify as described in clauses 6.1.4.1 and 6.1.4.2, and as illustrated in clauses 5.3 to 5.5. 6.1.6 CallHandlingRules.ForwardList Rule Processing Conditional call forwarding determines how the call attempt is forwarded, and possibly re-forwarded if the forwarded call does not complete. If the (conditional) forward list associated with the called party (B) is null, the call
