1、 ETSI TR 129 998-5-1 V9.0.0 (2010-01)Technical Report Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Application Programming Interface (API)Mapping for Open Service Access;Part 5: User Interaction Service Mapping;
2、Subpart 1: API to CAP Mapping (3GPP TR 29.998-05-1 version 9.0.0 Release 9)ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 13GPP TR 29.998-05-1 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-05-1v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33
3、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 document may be made availab
4、le 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 PDF version kept on a sp
5、ecific 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/status.asp If you find erro
6、rs 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 extend to reproduction in al
7、l media. European Telecommunications Standards Institute 2010. 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 registered for the benefit of its Members and
8、 of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 23GPP TR 29
9、.998-05-1 version 9.0.0 Release 9 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 in ETSI
10、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 ETSI IPR
11、 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 This
12、 Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI
13、deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 33GPP TR 29.998-05-1 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introd
14、uction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Generic Message Transfer Service CAMEL Call Flows . 6g34.1 User Interaction 6g34.1.1 createUI 6g34.1.2 createUICall 7g34.1.3 enableUINotification 7g34.1.4 disableUINotification 8g34.
15、1.5 userInteractionEventNotify . 8g34.1.6 userInteractionAborted . 9g34.1.7 userInteractionNotificationInterrupted 10g34.1.8 userInteractionNotificationContinued . 10g34.1.9 userInteractionFaultDetected 11g34.1.10 sendInfoReq 12g34.1.11 sendInfoRes 14g34.1.12 sendInfoErr . 16g34.1.13 sendInfoAndColl
16、ectReq 17g34.1.14 sendInfoAndCollectRes 20g34.1.15 sendInfoAndCollectErr . 21g34.1.16 release . 22g34.1.17 abortActionReq . 23g34.1.18 abortActionRes . 23g34.1.19 abortActionErr 24g3Annex A: Change history 25g3History 26g3ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 43GPP TR 29.998-05-1 version 9.0.0 R
17、elease 9 Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it w
18、ill be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the
19、 second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction Structure of the OSA API Mapping (3GPP TR 29.998) The present document
20、is part 5 subpart 1 of a multi-part deliverable covering the Open Service Access (OSA); Application Programming Interface (API) Mapping for OSA. Table: Overview of the OSA APIs Application Programming Interface (API); Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Ac
21、cess (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 5 3GPP TS 29.198-5: “Open Service Access (OSA); Application Programming Interface (API); Part 5: Generic user interaction“. 6 3GPP TS 29.002: “Mobile Application Part
22、 (MAP) specification“. 7 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification“. 8 3GPP TS 22.101: “Service Aspects; Service Principles“. 9 ITU-T Recommendation Q.850: “Usage of cause and location in the Digital Subscriber Sign
23、alling System No. 1 and the Signalling System No. 7 ISDN User Part“. 10 3GPP TR 29.998-1: “Open Service Access (OSA); Application Programming Interface (API) Mapping for OSA; Part 1: General Issues on API Mapping“. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 63GPP TR 29.998-05-1 version 9.0.0 Release
24、9 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TS 29.198-1 1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Generic Message Transfer Service CAMEL Cal
25、l Flows 4.1 User Interaction The User Interaction interface is used by applications to interact with end users. The API only supports Call User Interaction. 4.1.1 createUI createUI is a method that is used to create a new (non call related) user interaction object. gsmSSF gsmSCF SCS Application crea
26、teUI NOTE: There are no associated CAP call flows. Figure 4-1: Call Flow for createUI Table 4-1: Normal Operation Pre-conditions The application has been instructed to initiate a non call related User Interaction 1 The application invokes the createUI method 2 The SCS creates a new UI object Paramet
27、er Mapping None. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 73GPP TR 29.998-05-1 version 9.0.0 Release 9 4.1.2 createUICall createUICal is a method that is used to create a new call related user interaction object. gsmSSF gsmSCF SCS Application createUICall NOTE: There are no associated CAP call flow
28、s. Figure 4-2: Call Flow for createUICall Table 4-2: Normal Operation Pre-conditions The application has been requested to initiate a call related User Interaction 1 The application invokes the createUICall method 2 The SCS creates a new UICall object Parameter Mapping None. 4.1.3 enableUINotificati
29、on enableUINotification is a method that enables the reception of a user initiated user interaction. HLR gsmSCF SCS ApplicationenableUInotificationFigure 4-3: Call Flow for enableUINotification Table 4-3: Normal Operation Pre-conditions An agreement is established between the network operator and th
30、e service provider for the event notification to be enabled 1 The application invokes the enableUINotification method 2 The SCS stores the request Parameter Mapping None. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 83GPP TR 29.998-05-1 version 9.0.0 Release 9 4.1.4 disableUINotification disableUINotif
31、ication is a method that allows the application to remove notification for UI related actions previously set. HLR gsmSCF SCS ApplicationdisableUINotificationFigure 4-4: Call Flow for disableUINotification Table 4-4: Normal Operation Pre-conditions An agreement is established between the network oper
32、ator and the service provider for the event notification to be disabled 1 The application invokes the disableUINotification method 2 The request is disabled in the SCS. Parameter Mapping None. 4.1.5 userInteractionEventNotify userInteractionEventNotify is a method that notifies the application of a
33、user initiated request for user interaction. HLR gsmSCF SCS ApplicationMAP processUnstructuredSS-RequestuserInteractionEventNotifyMAP BeginSubscriberActivityFigure 4-5: Call Flow for userInteractionEventNotify Table 4-4: Normal Operation Pre-conditions 1 The gsmSCF receives a MAP processUnstructured
34、SS-Request message from the HLR. This operation may be preceded by MAP beginSubscriberActivity (see note) 2 The gsmSCF sends an equivalent internal message to the SCS 3 The SCS identified the correct application that enable the notification request from the subscriber and invokes the userInteraction
35、EventNotify method NOTE: The MAP beginSubscriberActivity is sent in case of MAP version 1. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 93GPP TR 29.998-05-1 version 9.0.0 Release 9 Table 4-5: Parameter Mapping From: processUnstructuredSS-Request To: userInteractionEventNotify uieventInfo (TpCallEventIn
36、fo):msisdn OriginatingAddressDestinationAddressServiceCodeDataTypeIndication ussd-DataCodingScheme ussd-String DataString assignmentIDappInterface (output)4.1.6 userInteractionAborted userInteractionAborted is a method that indicates to the application that the User Interaction service instance has
37、terminated or closed abnormally. No further communication will be possible between the User Interaction service instance and the application. HLRgsmSCFSCS ApplicationDialogue Abort (if appropriate)userInteractionAbortedFigure 4-6: Call Flow for userInteractionAborted (scenario 1) gsmSRFgsmSSFgsmSCFS
38、CS ApplicationDialogue Abort (if approppriate)userInteractionAbortedgsmSRFDialogue Abort (if appropriate)Figure 4-7: Call Flow for userInteractionAborted (scenario 2) Parameter Mapping None. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 103GPP TR 29.998-05-1 version 9.0.0 Release 9 4.1.7 userInteraction
39、NotificationInterrupted userInteractionNotificationInterrupted is a method that indicates to the application that all user interaction event notifications have been temporarily interrupted. HLR gsmSCF SCS ApplicationNo appropriate MAP messageuserInteractionNotificationInterruptedFigure 4-8: Call Flo
40、w for userInteractionNotificationInterrupted Table 4-6: Normal Operation Pre-conditions User interaction event notifications have been enabled using the enableUINotification method on the UIManager interface 1 The SCS has detected, or has been informed of, a fault which prevents further user interac
41、tion events from being notified 2 The SCS invokes the userInteractionNotificationInterrupted method Parameter Mapping None. 4.1.8 userInteractionNotificationContinued userInteractionNotificationContinued is a method that indicates to the application that user interaction event notifications will aga
42、in be possible. HLR gsmSCF SCS ApplicationNo appropriate MAP messageuserInteractionNotificationContinuedFigure 4-9: Call Flow for userInteractionNotificationContinued Table 4-7: Normal Operation Pre-conditions User interaction event notifications have been interrupted and userInteractionNotification
43、Interrupted method has been invoked 1 The SCS detects that user interaction event notifications are again possible 2 The SCS invokes the userInteractionNotificationContinued method Parameter Mapping None. ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 113GPP TR 29.998-05-1 version 9.0.0 Release 9 4.1.9 u
44、serInteractionFaultDetected userInteractionFaultDetected is a method that indicates to the application that a fault has been detected in the user interaction. This method is invoked e.g. if the call has been deassigned. HLR gsmSCFSCS ApplicationDialogue Error (if appropraite)userInteractionFaultDete
45、ctedFigure 4-10: Call Flow for userInteractionFaultDetected (scenario 1) gsmSRFgsmSSFgsmSCFSCS ApplicationDialogue Error (if appropriate)userInteractionFaultDetectedgsmSRFDialogue Error (if appropriate)Figure 4-11: Call Flow for userInteractionFaultDetected (scenario 2) Three Alternatives have been
46、identified: 1. USSD based interaction between the MS and the gsmSCF (see table 4-8). 2. Interaction between a gsmSRF internal to the gsmSSF and the gsmSCF (see table 4-9). 3. Interaction between a gsmSRF and the gsmSCF (see table 4-10). Table 4-8: Normal Operation Pre-conditions USSD interaction is
47、in progress and a dialogue is running between the HLR and gsmSCF 1 The gsmSCF detects or receives an indication that the there is an error in the user interaction 2 The gsmSCF sends an equivalent internal message to the SCS 3 The SCS invokes the userInteractionFaultDetected method to the appropriate
48、 application Table 4-9 Pre-conditions User interaction is in progress between the gsmSRF and the gsmSCF 1 The gsmSCF detects or receives an indication that there is an error in the user interaction 2 The gsmSCF sends an equivalent internal message to the SCS 3 The SCS invokes the userInteractionFaul
49、tDetected method to the appropriate application ETSI ETSI TR 129 998-5-1 V9.0.0 (2010-01) 123GPP TR 29.998-05-1 version 9.0.0 Release 9 Table 4-10 Pre-conditions User interaction is in progress between the gsmSRF and the gsmSCF 1 The gsmSCF detects or receives an indication that the there is an error in the user interaction 2 The gsmSCF sends an equivalent internal message to the SCS 3 The SCS invokes the userInteractionFaultDetected method to the appropriate application Table 4-11: Parameter Mapping From: Dialogue Error To: userInteractionFaultDetected
