1、 ETSI TR 102 397-10-2 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 2: Mapping to Multi-Party Call Control and User InteractionETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01
2、021-10-02-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 Indivi
3、dual 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
4、 Format (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 curr
5、ent 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 reproduc
6、ed except 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
7、benefit 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-2 V1.1.1 (2005-08) 3 Conten
8、ts Intellectual 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 dest
9、ination8 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 E
10、TSI 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. Forewo
11、rd This 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 2 of a multi-part deliverable covering Open Service Access (OSA); Mapping of Parlay
12、 X Web 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
13、 8: “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 Confer
14、ence 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
15、Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 5 1 Scope The present document specifies the mapping of the Parlay X Call Handling Web Service to the Multi-Party Call Control and User Interaction Service Capability Features (SCFs). The Parlay X Web Servic
16、es provide 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
17、 application 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); Vocabular
18、y for 3GPP 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
19、Mapping“. 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
20、of the present document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Call Handling capability can be implemented with Parlay/OSA Multi-Party 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. ET
21、SI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 6 5 Sequence diagrams 5.1 Enabling call notifications Application Call Handling IpAppMPCC Manager IpMPCC Manager createNotification i.e. INTERRUPT mode, P_CALL_EVENT_ADDRESS_ANALYSED“new“ setRulesForGroupRequest createNotification i.e. INTERRUPT mode, P_CALL_
22、EVENT_ADDRESS_ANALYSED createNotification i.e. INTERRUPT mode, P_CALL_EVENT_ADDRESS_ANALYSED setRulesForGroupResponse getRulesRequest getRulesResponse Figure 1 ETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 7 5.2 Disabling call notifications Application Call Handling IpAppMPCCManager IpMPCC Manager dest
23、royNotification clearRulesRequestdestroyNotification destroyNotificationclearRulesResponse Figure 2 ETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 8 5.3 Processing a call: Route to original destination Call Notification IpApp CallLeg: A IpApp MPCC Manager Ip MPCC Manager IpApp MPCall Ip MPCall Ip CallLe
24、g: A “A attempting to call B“ “new“ “new: Active“ reportNotification: P_CALL_EVENT_ADDRESS_ANALYSED“forward event“ “new“ “new“ OPTIONAL: setChargePlan continue Processing deassignCall “destroy“ “destroy“ Appl Evaluate rules for calls from A to B Figure 3 ETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 9
25、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 through 6.1.10. 6.1.1 setRules and setRulesForGroup These operations set up (or replace as applicable) the set of rules associat
26、ed with a destination address or addresses. Call notification is established with the Multi-Party Call Control service for the termination address for the receipt of a call attempt notification. The sequence diagram in clause 5.1 illustrates the flow for these operations. They are mapped to the Parl
27、ay/OSA method: IpMultiPartyCallControlManager.createNotification. 6.1.1.1 Mapping to IpMultiPartyCallControlManager.createNotification The IpMultiPartyCallControlManager.createNotification method is invoked with the following parameters. Name Type Comment appCallControl Manager IpAppMultiPartyCall C
28、ontrolManagerRef Specifies the interface for receiving call-related event notifications associated with the criteria contained in the notificationRequest. notification Request TpCallNotification Request Specifies event-related data, which is mapped from the parts of the setRulesForGroupRequest messa
29、ge as described in clause 6.1.1.2. The result from IpMultiPartyCallControlManager.createNotification is of type TpAssignmentID. It is used internally by the Call Handling web service to correlate the Parlay/OSA callbacks, e.g. IpAppMultiPartyCallControlManager.reportNotification, when a call-related
30、 event, which is associated with the criteria contained in the notificationRequest, is triggered in the network. Parlay exceptions thrown by IpMultiPartyCallControlManager.createNotification are mapped to Parlay X exceptions as defined in clause 6.1.4. 6.1.1.2 Mapping from setRulesForGroupRequest to
31、 notificationRequest The elements of the notificationRequest data type are derived from the parts of the setRulesForGroupRequest message as follows. Name Type Comment CallNotification Scope TpCallNotification Scope Specifies the destination address of the call, which is derived from the URI in the a
32、ddresses part of setRulesForGroupRequest, as described in TR 102 397-1 3. CallEvents Requested TpCallEventRequest Set Defines a SINGLE element of a set, as follows: CallEventType = P_CALL_EVENT_ADDRESS_ANALYSED AdditionalCallEventCriteria = Null CallMonitorMode = P_CALL_MONITOR_MODE_INTERRUPT. ETSI
33、ETSI TR 102 397-10-2 V1.1.1 (2005-08) 126.1.2 getRules This operation 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 notificatio
34、n from the Multi-Party Call Control service, and clears the related rules information 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: IpMultiPartyCallControlManager.destroyNotification. 6.1.3.1 Mapping to
35、IpMultiPartyCallControlManager.destroyNotification The IpMultiPartyCallControlManager.destroyNotification method is invoked with the following parameters. Name Type Comment assignmentID TpAssignmentID Specifies the assignment id returned after an earlier invocation of IpMultiPartyCallControlManager.
36、createNotification method. Parlay exceptions thrown by IpMultiPartyCallControlManager.destroyNotification are mapped to Parlay X exceptions as defined in clause 6.1.4. 6.1.4 CallHandlingRules.AcceptList Rule Processing Call accepting determines if the call is accepted or rejected. If the accept list
37、 associated with the called party (B) is null, then CallHandlingRules.AcceptList rule processing ends: processing 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 claus
38、e 6.1.10 CallHandlingRules: Reject Call Attempt. Otherwise the calling party (A) is a member of Bs accept list, the call attempt by A is not rejected: processing continues with CallHandlingRules.ForwardList Rule Processing. Rule processing is invoked by the Parlay/OSA method: IpAppCallControlManager
39、. reportNotification, as illustrated in clauses 5.3 to 5.5. 6.1.4.1 Mapping from IpAppMultiPartyCallControlManager.reportNotification The IpAppMultiPartyCallControlManager.reportNotification method is invoked with the following parameters. Name Type Comment callReference TpMultiParty CallIdentifier
40、Specifies the reference to the call interface to which the notification relates. callLegReferenceSet TpCallLegIdentifierSet Specifies the set of all call leg references associated with the call. Contains a single reference to the calling party (A) leg. notificationInfo TpCallNotificationInfo Specifi
41、es event-related data, which is mapped 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 IpMultiPartyCallControlManager.createNotification method, when the criteria associated with this c
42、all-related event were activated in the 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. ETSI ETSI TR 102 397-10-2 V1.1.1 (2005-08) 13The result from IpAppMultiPartyCallControlManager.reportNotification is of t
43、ype TpAppMultiPartyCallBack (element=AppMultiPartyCallAndCallLeg), which specifies references to the application interfaces which implement the callback interfaces for the call and the calling party (A) leg. 6.1.4.2 Mapping from TpCallNotificationInfo to Call Handling Rule Database The elements of t
44、he TpCallNotificationInfo data type are mapped to the Call Handling rule database as follows. Name Type Comment CallNotification ReportScope TpCallNotification ReportScope Specifies the called party address (B) and calling party address (A) of the call. Bs address is used as an index into the rule d
45、atabase 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. As address is mapped to a URI provided in the CallHandlingRules structure for B, as described in TR 102 397-1 3. Matched against
46、the contents of one or more of the following lists: CallHandlingRules.AcceptList CallHandlingRules.BlockList CallHandlingRules.ForwardList.CallingAddress. CallAppInfo TpCallAppInfoSet Not mapped. CallEventInfo TpCallEventInfo Contains the event which is reported, which is mapped as described in the
47、following table. The elements of the TpCallEventInfo data type are mapped as follows. Name Type Comment CallEventType TpCallEventType Not mapped. This element has a value of P_EVENT_GCCS_ADDRESS_ANALYSED_EVENT. AdditionalCallEvent Info TpCallAdditionalEvent Info For P_CALL_EVENT_ADDRESS_ANALYSED thi
48、s element contains Bs address, which is redundant here and ignored. CallMonitorMode TpCallMonitorMode Not mapped. This element has a value of “P_CALL_MONITOR_MODE_INTERRUPT“. CallEventTime TpDateAndTime Not mapped. 6.1.5 CallHandlingRules.BlockList Rule Processing Call blocking determines if the cal
49、l 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 Rule 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 continues with clause 6.1.10 CallHandlingRules
