ETSI TR 129 998-5-4-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf

1、 ETSI TR 129 998-5-4 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 4: API to SMS Mapping (3GPP TR 29.998-05-4 version 9.0.0 Release 9)ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 13GPP TR 29.998-05-4 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-05-4v900 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-4 V9.0.0 (2010-01) 23GPP TR 29

9、.998-05-4 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-4 V9.0.0 (2010-01) 33GPP TR 29.998-05-4 version 9.0.0 Release 9 Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 4g3Introd

14、uction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 5g33.1 Definitions 5g33.2 Abbreviations . 6g34 Generic Message Transfer Service SMS Call Flows . 6g34.1 User Interaction 6g34.1.1 createUI 6g34.1.2 createUICall 6g34.1.3 enableUINotification 6g34.1.4 disableUINotification 7g34.1.

15、5 userInteractionEventNotify . 8g34.1.6 userInteractionAborted . 9g34.1.7 userInteractionNotificationInterrupted 9g34.1.8 userInteractionNotificationContinued . 10g34.1.9 userInteractionFaultDetected 11g34.1.10 sendInfoReq 11g34.1.11 sendInfoRes 15g34.1.12 sendInfoErr . 16g34.1.13 sendInfoAndCollect

16、Req 19g34.1.14 sendInfoAndCollectRes 22g34.1.15 sendInfoAndCollectErr . 24g34.1.16 release . 26g34.1.17 abortActionReq . 27g34.1.18 abortActionRes . 27g34.1.19 abortActionErr 27g3Annex A: Change history 28g3History 29g3ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 43GPP TR 29.998-05-4 version 9.0.0 Rele

17、ase 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 will

18、 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 se

19、cond 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 is

20、part 5 subpart 4 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 Acces

21、s (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 (M

22、AP) specification“. 7 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL) Phase 3; 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

23、 Signalling 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“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present

24、document, the terms and definitions given in TS 29.198-1 1 apply. ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 63GPP TR 29.998-05-4 version 9.0.0 Release 9 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 SMS

25、Call Flows 4.1 User Interaction The User Interaction interface is used by applications to interact with end users. The API supports call and non-call related User Interaction. In mapping the User Interaction interface to SMS call flows, only non-call related User Interaction is applicable. 4.1.1 cre

26、ateUI createUI is a method that is used to create a new (non call related) user interaction object. gsmSSF gsmSCF SCS Application createUI SMS-G/IWMSC SCS HLR MSC createUI NOTE: There are no associated CAP or MAP, SMS call flows. Figure 4-1: Call Flow for createUI Table 4-1: Normal Operation Pre-con

27、ditions 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 Parameter Mapping None. 4.1.2 createUICall createUICall is a method that does not map to SMS delivery. 4.1.3 enableUINotificatio

28、n enableUINotification is a method that enables the reception of a user initiated user interaction. The user initiates this interaction by means of a CAMEL Phase 3 enabled MO SMS. ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 73GPP TR 29.998-05-4 version 9.0.0 Release 9 HLRgsmSCFSCS ApplicationenableUIN

29、otificationMAP AnyTimeModificationFigure 4-2: Call Flow for enableUINotification Two alternatives have been identified: 1. The application requests notifications to be enabled (see table 4-2). 2. HLR rejects CSI updates (see table 4-3). Table 4-2: Normal Operation Pre-conditions An agreement is esta

30、blished between the network operator and the service provider for the event notification to be enabled 1 The application invokes the enableUINotification method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to Activate the necessary CAMEL Subscription Information (SMS-CSI) (see no

31、te) NOTE: CAMEL phase 3 only allows for activation/deactivation of the CSI and not modification of the contents of the CSIs. As the SMS-CSI relates only to MO messaging, only originating addresses are considered. For SMS-CSI only DP SMS_Collected_Info is supported. Table 4-3: Error condition Pre-con

32、ditions gsmSCF had previously sent a MAP AnyTimeModification message to the HLR as a result of an enableUINotification request from the application 1 HLR rejects the request to update the CSI 2 The gsmSCF sends an internal message to the SCS to indicate the up date failure 3 The SCS invokes the exce

33、ption on enableUINotification Table 4-4: Parameter Mapping From: enableUINotification To: MAP AnyTimeModification appInterface gsmSCFAddress eventCriteria (TpUIEventCriteria): OriginatingAddress subscriberIdentity (see note) DestinationAddress ServiceCode assignmentID modificationRequestFor-CallForw

34、ardingSS-Data ficationRequestFor-CallBarringSS-DatamodificationRequestFor-CSI Requested CSI = SMS-CSI ModifyNotificationFlag Modify CSI State = Activate NOTE: In case an address range is used, a separate MAP AnyTimeModificationRequest shall be sent for every address in the range. 4.1.4 disableUINoti

35、fication disableUINotification is a method that allows the application to remove notification for UI related actions previously set. ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 83GPP TR 29.998-05-4 version 9.0.0 Release 9 HLRgsmSCFSCS ApplicationdisableUINotificationMAP AnyTimeModificationFigure 4-3:

36、Call Flow for disableUINotification Table 4-5: Normal Operation Pre-conditions An agreement is established between the network operator and the service provider for the event notification to be disabled 1 The application invokes the disableUINotification method 2 The gsmSCF sends a MAP AnyTimeModifi

37、cation to the HLR in order to de-activate the CAMEL subscription Information (SMS-CSI). Note that CAMEL Phase 3 only allows the capability to activate/deactivate CSI and not to modify the triggering information Table 4-6: Parameter Mapping From: disableUINotification To: MAP AnyTimeModification assi

38、gnmentID gsmSCFAddress subscriberIdentity (see note) modificationRequestFor-CallForwardingSS-DataficationRequestFor-CallBarringSS-Data modificationRequestFor-CSI- Requested CSI = SMS-CSI - ModifyNotificationFlag - Modify CSI State = Deactivate NOTE: A separate MAP AnyTimeModificationRequest shall be

39、 sent for every originating address in the prior enableUINotification and known to the IpUIManager. 4.1.5 userInteractionEventNotify userInteractionEventNotify is a method that notifies the application of a user initiated request for user interaction. gsmSSF gsmSCF SCS ApplicationInitialDPSMSuserInt

40、eractionEventNotifyFigure 4-4: Call Flow for userInteractionEventNotify Table 4-7 Pre-conditions CAMEL MO SMS interaction between gsmSSF and gsmSCF 1 The gsmSCF has previously enabled the SMS-CSI DP triggers using the MAP AnyTimeModification for the origination mobile subscriber address 2 The gsmSCF

41、 receives the CAP InitialDPSMS from the gsmSSF 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 userInteractionEventNotify method ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01

42、) 93GPP TR 29.998-05-4 version 9.0.0 Release 9 Table 4-8: Parameter Mapping From: initialDPSMS To: userInteractionEventNotify uieventInfo (TpUIEventInfo) : CallingPartyNumber OriginatingAddressDestinationSubscriberNumber DestinationAddressServiceKey ServiceCodeDataTypeIndication (= TP-DataCodingSche

43、me) EventType DataStringassignmentIDappInterface (output)IMSILocationInfo in MSC ( C ) LocationInfor in SGSN ( C ) Time DataCoding Scheme,UserDataLength Enable an event if a sendInfoRes is needed assignmentIDTable 4-19 From: sendInfoReq To: FurnishChargingInfoSMS userInteractionSessionID info (choic

44、e) infoID infoData infoAddress variableInfoSet variablePartInteger variablePartAddress variablePartTime variablePartDate variablePartPrice FCI Billing Charging Characteristics repeatIndicator responseRequestedassignmentIDETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 153GPP TR 29.998-05-4 version 9.0.0 R

45、elease 9 Table 4-20 From: sendInfoReq To: ConnectSMS userInteractionSessionID CallingPartysNumberinfo (choice) infoID infoData infoAddress variableInfoSet variablePartInteger variablePartAddress DestinationSubscriberNumber variablePartTime variablePartDate variablePartPrice repeatIndicator responseR

46、equestedassignmentIDSMSCAddress No mapping exists between sendInfoReq and continueSMS. 4.1.11 sendInfoRes sendInfoRes is an asynchronous method that informs the application about the start or the completion of a sendInfoReq(). This response is called only if the application has requested a response.

47、 MSC SMS-GMSCSCS ApplicationsendInfoResMAP MTForwardSMConfFigure 4-11: Call Flow for sendInfoRes (scenario 1) gsmSSF gsmSCF SCS ApplicationEventReportSMSsendInfoResFigure 4-12: Call Flow for sendInfoRes (scenario 2) Two alternatives have been identified: 1. SMS based interaction between the MS and t

48、he SMS-GMSC (see table 4-21). 2. Notification from gsmSSF to gsmSCF of an event previously requested by a RequestReportSMSEvent (see table 4-22). ETSI ETSI TR 129 998-5-4 V9.0.0 (2010-01) 163GPP TR 29.998-05-4 version 9.0.0 Release 9 Table 4-21: Normal Operation Pre-conditions The application has pr

49、eviously invoked the sendInfoReq method and has requested a notification 1 The SMS-GMSC receives a MAP MT-ForwardShortMessage confirmation message from the MSC 2 The SMS-GMSC sends an equivalent internal message to the SCS 3 The SCS identifies the correct application and invokes the sendInfoRes method Table 4-22 Pre-conditions 1 The gsmSCF has previously requested the gsmSSF to monitor for a particular SMS related event (e.g. SMS_Submitted, SMS_Failure) using the CAP RequestReportSMSEvent method. 2 The gsmSSF detects the SMS event and forwards the CAP Ev