ETSI TR 102 397-3-2-2005 Open Service Access (OSA) Mapping of Parlay X Web Services to Parlay OSA APIs Part 3 Call Notification Mapping Sub-part 2 Mapping to Multi-Party Call Contr_1.pdf

1、 ETSI TR 102 397-3-2 V1.1.1 (2005-08)Technical Report Open Service Access (OSA);Mapping of Parlay X Web Services to Parlay/OSA APIs;Part 3: Call Notification Mapping;Sub-part 2: Mapping to Multi-Party Call ControlETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 2 Reference DTR/TISPAN-01021-03-02-OSA Keywor

2、ds 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 copies of the p

3、resent 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 Format (PDF). In ca

4、se 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 status of this a

5、nd 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 except as authori

6、zed 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 benefit of its Membe

7、rs. 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-3-2 V1.1.1 (2005-08) 3 Contents Intellectual Prope

8、rty 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 Notification of a network-related Call Event .6 5.2 Handling a network-related call event - Action: Continue .7 5.3 Handling a net

9、work-related call event - Action: Route 8 5.4 Handling a network-related call event - Action: End Call9 6 Detailed mapping information10 6.1 Operations 10 6.1.1 notifyXXX 10 6.1.1.1 Mapping from IpAppMultiPartyCallControlManager.reportNotification.10 6.1.1.2 Mapping from TpCallNotificationInfo to no

10、tifyXXXRequest 10 6.1.2 handleXXX.11 6.1.2.1 Mapping to IpMultiPartyCall.createAndRouteCallLegReq .12 6.1.2.2 Mapping to IpMultiPartyCall.setCallChargePlan12 6.1.2.3 Mapping to IpCallLeg.continueProcessing 12 6.1.2.4 Mapping to IpMultiPartyCall.deassignCall13 6.1.2.5 Mapping to IpMultiPartyCall.rele

11、ase13 6.2 Exceptions 13 7 Additional notes .13 History 14 ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 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 a

12、vailable 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 available on the ETSI Web s

13、erver (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 server) which are, or may

14、 be, or may become, essential to the present document. Foreword 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 3, sub-part 2 of a multi-part deliv

15、erable covering Open Service Access (OSA); Mapping of Parlay 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“; Sub-part 1: “Mapping to Generic Call Control“; Sub-part 2: “Mapping to Multi-Party C

16、all Control“; Part 4: “Short Messaging Mapping“; Part 5: “Multimedia Messaging Mapping“; Part 6: “Payment Mapping“; Part 7: “Account Management Mapping“; Part 8: “Terminal Status Mapping“; Part 9: “Terminal Location Mapping“; Part 10: “Call Handling Mapping“; Part 11: “Audio Call Mapping“; Part 12:

17、“Multimedia Conference 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

18、between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 5 1 Scope The present document specifies the mapping of the Parlay X Call Notification Web Service to the Parlay/OSA Multi-Party Call Control Service Capability Feature (SCF). The Parlay X W

19、eb Services 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 tha

20、t enables 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);

21、Vocabulary 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

22、1: Common 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

23、 purposes of the present document, the abbreviations given in TR 102 397-1 3 apply. 4 Mapping description The Call Notification capability can be implemented with the Parlay/OSA Multi-Party Call Control SCF. 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. E

24、TSI ETSI TR 102 397-3-2 V1.1.1 (2005-08)6 5 Sequence diagrams 5.1 Notification of a network-related Call Event reportNotification: P_CALL_EVENT_ADDRESS_ANALYSED reportNotifi cation: P_BUSY reportNotification: P_UNREACHABLE reportNotification: P_NO_ANSWER ApplicationCall Notification IpAppMPCC Manage

25、r IpMPCC Manager createNotification i.e. NOTIFY mode “new“ notifyCalledNumberResponsecreateNotification i.e. NOTIFY mode createNotification i.e. NOTIFY mode “forward event“ notifyCalledNumberRequestnotifyBusyResponse “forward event“ notifyBusyRequestnotifyNotReachableResponse“forward event“ notifyNo

26、tReachableRequestnotifyNoAnswerResponse “forward event“ notifyNoAnswerRequestFigure 1 ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08)7 5.2 Handling a network-related call event - Action: Continue Call Notification IpApp CallLeg: A IpApp MPCC Ip MPCC Manager IpApp MPCall Ip MPCall createNotification: P_CAL

27、L_EVENT_ADDRESS_ANALYSED : i.e. INTERRUPT mode “new“ “A attempting to call B“ “new“ “new: Active“ reportNotification: P_CALL_EVENT_ADDRESS_ANALYSED“forward event“ “new“ “new“ handleCalledNumberResponse: CONTINUE handleCalledNumberRequest OPTIONAL: setChargePlan continueProcessing deassignCall “destr

28、oy“ “destroy“ Appl Ip CallLeg: A Figure 2 ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08)8 5.3 Handling a network-related call event - Action: Route Appl Call Notification IpApp MPCC IpApp MPCall createNotification: P_BUSY : i.e. INTERRUPT mode “new“ “A calls B, but B is Busy“ “new“ “new: Active“ “new: Re

29、leasing“ reportNotification: P_BUSY “forward event“ “new“ “new“ handleBusyResponse: ROUTE handleBusyRequest “new“ OPTIONAL: setChargePlan createAndRouteCallLegReq “new: Idle“ deassign deassignCall “destroy“ “destroy“ “destroy“ Ip MPCall Ip CallLeg: A IpApp CallLeg: A IpApp CallLeg: C Ip CallLeg: C I

30、p MPCC Manager Ip CallLeg: B Figure 3 ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08)9 5.4 Handling a network-related call event - Action: End Call Appl Call Notification IpApp CallLeg: A createNotification: P NO ANSWER : i.e. INTERRUPT mode “new“ “A calls B, but B is not answering“ “new“ “new: Active“ “n

31、ew: Releasing“ reportNotification: P NO ANSWER “forward event“ “new“ “new“ handleNoAnswerResponse: END CALL handleNoAnswerRequest release “destroy“ “destroy“ IpApp MPCC IpApp MPCall Ip MPCC Manager Ip MPCall Ip CallLeg: A Ip CallLeg: A Figure 4 ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 106 Detailed

32、mapping information 6.1 Operations 6.1.1 notifyXXX The sequence diagram in clause 5.1 illustrates the flow for any of the notifyXXX operations, namely: notifyCalledNumber; notifyBusy; notifyNotReachable; notifyNoAnswer. Each notifyXXX operation is mapped from the Parlay/OSA method: IpAppMultiPartyCa

33、llControlManager.reportNotification. 6.1.1.1 Mapping from IpAppMultiPartyCallControlManager.reportNotification The IpAppMultiPartyCallControlManager.reportNotification method is invoked with the following parameters. Name Type Comment callReference TpMultiPartyCallIdentifier Specifies the reference

34、to the call interface to which the notification relates. Since the notification is in NOTIFY mode, this parameter should be ignored by the Call Notification web service; and is is not mapped to the notifyXXXRequest message. callLegReferenceSet TpCallLegIdentifierSet Specifies the set of all call leg

35、 references associated with the call. Since the notification is in NOTIFY mode, this parameter should be ignored by the Call Notification web service; and is is not mapped to the notifyXXXRequest message. notificationInfo TpCallNotificationInfo Specifies event-related data, which is mapped to the no

36、tifyXXXRequest message as described in clause 6.1.1.2. assignmentID TpAssignmentID Specifies the assignment id returned after an earlier invocation of IpMultiPartyCallControlManager.createNotification method, when the criteria associated with this call-related event were activated in the network. It

37、 is used internally by the Call Notification web service to correlate the Parlay/OSA callbacks. The result from IpAppMultiPartyCallControlManager.reportNotification is of type TpAppMultiPartyCallBack, but is null (P_APP_CALLBACK_UNDEFINED) for event notifications in NOTIFY mode. 6.1.1.2 Mapping from

38、 TpCallNotificationInfo to notifyXXXRequest The elements of the TpCallNotificationInfo data type are mapped to the parts of the notifyXXXRequest message as follows. Name Type Comment CallNotification ReportScope TpCallNotification ReportScope Specifies the destination address and originating address

39、 of the call, which are mapped to the URIs provided in the CalledParty part and CallingParty part,respectively, of notifyXXXRequest, as described in TR 102 397-1 3. CallAppInfo TpCallAppInfoSet Not mapped. CallEventInfo TpCallEventInfo Contains the event which is reported, which is mapped to the not

40、ifyXXXRequest message as described in the following table. ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 11The elements of the TpCallEventInfo data type are mapped to the parts of the notifyXXXRequest message as follows. Name Type Comment CallEventType TpCallEventType Defines the specific notifyXXXReque

41、st message to send, i.e.: XXX= CalledNumber for P_CALL_EVENT_ADDRESS_ANALYSED; XXX= Busy, NotReachable or NoAnswer for P_CALL_EVENT_TERMINATING_RELEASE. AdditionalCallEvent Info TpCallAdditionalEvent Info For P_CALL_EVENT_ADDRESS_ANALYSED this element contains the called address, which is redundant

42、her and ignored. For P_CALL_EVENT_TERMINATING_RELEASE, this element contains the terminating release cause, P_BUSY, P_NO_ANSWER, or P_NOT_REACHABLE, and identifies the specific notifyXXXRequest message to send. CallMonitorMode TpCallMonitorMode Not mapped. This element has a value of “P_CALL_MONITOR

43、_MODE_NOTIFY“. CallEventTime TpDateAndTime Not mapped. 6.1.2 handleXXX The sequence diagrams in clauses 5.2 through 5.4 illustrates the flow for any of the handleXXX operations. A handleXXX operation is synchronous from the Call Notification Web Service“s point of view. As defined for the notifyXXXr

44、equest message in clause 6.1.1, each handleXXXrequest message is mapped from the Parlay/OSA method: IpAppMultiPartyCallControlManager.reportNotification. However in this case the notificationInfo.CallEventInfo.CallMonitorMode element has a value of “P_CALL_MONITOR_MODE_INTERRUPT“. The handleXXXrespo

45、nse message is mapped to one or more of the following Parlay/OSA methods, depending on the value of the Action part: IpMultiPartyCall.createAndRouteCallLegReq, if the ActionToPerform parameter of the Action part = Route. IpMultiPartyCall.setChargePlan, if: - the optional Charging parameter of the Ac

46、tion part is present; and - the ActionToPerform parameter of the Action part = Route or Continue. IpCallLeg.continueProcessing, if the ActionToPerform parameter of the Action part = Continue. IpMultiPartyCall.deassignCall, if the ActionToPerform parameter of the Action part = Route or Continue. IpMu

47、ltiPartyCall.release, if the ActionToPerform parameter of the Action part = EndCall. ETSI ETSI TR 102 397-3-2 V1.1.1 (2005-08) 126.1.2.1 Mapping to IpMultiPartyCall.createAndRouteCallLegReq The IpMultiPartyCall.createAndRouteCallLegReq method is invoked with the following parameters. Name Type Comme

48、nt callSessionID TpSessionID Not mapped: derived from the callReference parameter of IpAppMultiPartyCallControlManager.reportNotification. eventsRequested TpCallEventRequest Set Not mapped. Requests NO call-related event reports. targetAddress TpAddress Specifies the destination leg to which the cal

49、l should be routed. It is constructed based on the URI provided in the RoutingAddress parameter of the Action part of the handleXXXResponse message, mapped as described in TR 102 397-1 3. originatingAddress TpAddress Not mapped: derived from the notificationInfo parameter of IpAppMultiPartyCallControlManager.reportNotification. appInfo TpCallAppInfoSet Not mapped: derived from the notificationInfo parameter of IpAppMultiPartyCallControlManager.reportNotification. appLegInterface IpAppCallLegRef Not mapped. The result from IpMultiPartyCal