ETSI TR 129 998-6-2004 Universal Mobile Telecommunications System (UMTS) Open Service Access (OSA) Application Programming Interface (API) Mapping for Open Service Access Part 6 Uso.pdf

《ETSI TR 129 998-6-2004 Universal Mobile Telecommunications System (UMTS) Open Service Access (OSA) Application Programming Interface (API) Mapping for Open Service Access Part 6 Uso.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 129 998-6-2004 Universal Mobile Telecommunications System (UMTS) Open Service Access (OSA) Application Programming Interface (API) Mapping for Open Service Access Part 6 Uso.pdf（21页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 129 998-6 V6.0.0 (2004-12)Technical Report Universal Mobile Telecommunications System (UMTS);Open Service Access (OSA)Application Programming Interface (API)Mapping for Open Service Access;Part 6: User Location and User StatusService Mapping to MAP(3GPP TR 29.998-06 version 6.0.0 Release 6)

2、ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 1 3GPP TR 29.998-06 version 6.0.0 Release 6 Reference RTR/TSGN-0529998-06v600 Keywords UMTS 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

3、 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 available in more than one electronic version or in print. In any case of existing or perceived d

4、ifference 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 specific network drive within ETSI Secretariat. Users of the present document should be awar

5、e 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 errors in the present document, please send your comment to one of the following services: htt

6、p:/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 all media. European Telecommunications Standards Institute 2004. All rights reserved. DECTTM

7、, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the 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 Organiza

8、tional Partners. ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 2 3GPP TR 29.998-06 version 6.0.0 Release 6 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 av

9、ailable 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 se

10、rver (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

11、be, or may become, essential to the present document. Foreword This 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 s

12、hould be interpreted as being references to the corresponding ETSI 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-6 V6.0.0 (2004-12) 3 3GPP TR 29.998-06 version 6.0.0 Release 6 Contents I

13、ntellectual Property Rights2 Foreword.2 Foreword.4 Introduction 4 1 Scope 5 2 References 5 3 Definitions and abbreviations.5 3.1 Definitions5 3.2 Abbreviations .6 4 User Status Service CAMEL Flows.6 4.1 triggeredStatusReportingStartReq6 4.2 triggeredStatusReportingStop.7 4.3 statusReportReq .7 4.4 s

14、tatusReportRes8 4.5 triggeredStatusReport.9 5 User Status Service core-MAP Flows9 5.1 statusReportReq .9 5.2 statusReportRes10 6 Network User Location Call Flows11 6.1 locationReportReq11 6.2 locationReportRes 11 6.3 locationReportErr .12 6.4 periodicLocationReportingStartReq.13 6.5 periodicLocation

15、ReportingStop .14 6.6 periodicLocationReport14 6.7 periodicLocationReportErr.15 6.8 triggeredLocationReportingStartReq16 6.9 triggeredLocationReportingStop 16 6.10 triggeredLocationReport 17 6.11 triggeredLocationReportErr .18 Annex A: Change history 19 History 20 ETSI ETSI TR 129 998-6 V6.0.0 (2004

16、-12) 4 3GPP TR 29.998-06 version 6.0.0 Release 6 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 th

17、e contents of the present document, it will 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 appro

18、ved document under change control. y the 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 Mappin

19、g (3GPP TR 29.998) The present document is part 6 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specification Group Core Network; Open Service Access (OSA); Application Programming Interface (API) Mapping for OSA. Table: Overview of the OSA APIs Application Pr

20、ogramming Interface (API); Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (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-6: “Open Service Access (OSA); Applicati

21、on Programming Interface (API); Part 6: Mobility“. 6 3GPP TS 29.002: “Mobile Application Part (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 Principle

22、s“. 9 ITU-T Recommendation Q.850: “Usage of cause and location in the Digital Subscriber 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 Ma

23、pping“. 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. ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 6 3GPP TR 29.998-06 version 6.0.0 Release 6 3.2 Abbreviations For the purposes of the present document, th

24、e abbreviations given in TS 29.198-1 1 apply. 4 User Status Service CAMEL Flows The User Status (US) interface class allows applications to obtain the status of mobile telephony users. 4.1 triggeredStatusReportingStartReq TriggeredStatusReportingStartReq is a method that is used to subscribe to trig

25、gered user status notifications so that events can be sent to the application. HLR gsmSCFSCS ApplicationtriggeredStatusReportingStartReqAnyTimeModificationFigure 4-1: Call Flow for triggeredStatusReportingStartReq Table 4-1: Normal Operation Pre-conditions An agreement is established between the net

26、work operator and the service provider for the event notification to be enabled 1 The application invokes the triggeredStatusReportingStartReq method 2 The gsmSCF sends a MAP AnyTimeModification to the HLR in order to activate the CAMEL Subscription Information (M-CSI) In case the Status Report is r

27、equested for multiple users, multiple ATM requests are sent to the HLR Table 4-2: Parameter Mapping From: triggeredStatusReportingStartReq To: MAP AnyTimeModification appStatus users subscriberIdentity modificationInstruction in modificationRequestFor-CSI has value activate, for M-CSI (Mobility CAME

28、L Subscription Information) assignmentID gsmSCF-Address ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 7 3GPP TR 29.998-06 version 6.0.0 Release 6 4.2 triggeredStatusReportingStop triggeredStatusReportingStop is a method that is used by the application to disable triggered user status notifications. HLR gs

29、mSCFSCS ApplicationtriggeredStatusReportingStopAnyTimeModificationFigure 4-2: Call Flow for triggeredStatusReportingStop Table 4-3: Normal Operation Pre-conditions An agreement is established between the network operator and the service provider for the status notification to be disabled 1 The appli

30、cation invokes the triggeredStatusReportingStop method 2 The gsmSCF sends a MAP AnyTimeModificaitonRequest to the HLR in order to de-activate the CAMEL Subscription Information (M-CSI). In case stopping Status Reporting is requested for multiple users, multiple ATM requests are sent to the HLR. Tabl

31、e 4-4: Parameter Mapping From: triggeredStatusReportingStop To: MAP AnyTimeModification stopRequest assignmentID stopScope users subscriberIdentity (either extracted from assignmentID, or mapped from users) modificationInstruction in modificationRequestFor-CSI has value deactivate, for M-CSI (Mobili

32、ty CAMEL Subscription Information) gsmSCF-Address 4.3 statusReportReq statusReportReq is a method that is used by the application to request a user status report. Note that this can be requested for multiple users at the same time. HLR gsmSCFSCS ApplicationstatusReportReqAnyTimeInterrogationFigure 4

33、-3: Call Flow for statusReportReq Table 4-5: Normal Operation Pre-conditions 1 The application invokes the statusReportReq method 2 The gsmSCF sends a MAP AnyTimeInterrogateRequest to the HLR in order to request the subscriber status In case the Status Report is requested for multiple users, multipl

34、e ATI requests are sent to the HLR. ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 8 3GPP TR 29.998-06 version 6.0.0 Release 6 Table 4-6: Parameter Mapping From: statusReportReq To: MAP AnyTimeInterrogation Invoke id appStatus users subscriberIdentity requestedInfo (sequence of optional indicators, of whic

35、h only subscriberState is present) gsmSCF-Address assignmentID 4.4 statusReportRes statusReportRes is a method that is used by the HLR/SCS towards the application, in response to an earlier request for a user status report. Note that this can be requested for multiple users at the same time. HLR gsm

36、SCFSCS ApplicationAnyTimeInterrogationAckStatusReportResFigure 4-4: Call Flow for statusReportRes Table 4-7: Normal Operation Pre-conditions The application has invoked a statusReportReq method and this request has been forwarded to the HLR 1 The HLR sends a MAP AnyTimeInterrogationAck to the HLR/SC

37、S in response to the earlier request. 2 The gsmSCF/SCS respond to the application via StatusReportRes. In case the Status Report was requested for multiple users, multiple ATI acknowledgements are collected in the gsmSCF/SCS before a response is sent back to the Application. Table 4-8: Parameter Map

38、ping To: statusReportRes From: MAP AnyTimeInterrogationAck Invoke id assignmentID statususerID statusCode subscriberInfo (sequence of optional parameters, of which only subscriberState present) status subscriberState ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 9 3GPP TR 29.998-06 version 6.0.0 Release 6

39、 4.5 triggeredStatusReport triggeredStatusReport is a method that is used to notify the application of the arrival of a requested user status report event. VLR gsmSCFSCS ApplicationnoteMMEventtriggeredStatusReportFigure 4-5: Call Flow for triggeredStatusReport Table 4-9: Normal Operation Pre-conditi

40、ons The Application has requested triggeredStatusReporting 1 The VLR sends a MAP noteMM-Event message to the CSE/SCS 2 The SCS sends a triggeredStatusReport to the Application Table 4-10: Parameter Mapping To triggeredStatusReport From: MAP noteMM-Event status userID msisdn statusCode status event-M

41、et serviceKeyimsiassignmentID 5 User Status Service core-MAP Flows The User Status (US) interface class allows applications to obtain the status of mobile telephony users. 5.1 statusReportReq statusReportReq is a method that is used by the application to request a user status report. Note that this

42、can be requested for multiple users at the same time. VLR HLR SCS ApplicationstatusReportReqProvideSubscriberInfoReqFigure 5-1: Call Flow for statusReportReq ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 103GPP TR 29.998-06 version 6.0.0 Release 6 Table 5-1: Normal Operation Pre-conditions 1 The applicati

43、on invokes the statusReportReq method 2 The HLR sends a MAP ProvideSubscriberInfoRequest to the VLR in order to request the subscriber status In case the Status Report is requested for multiple users, multiple PSI requests are sent to the VLR Table 5-2: Parameter Mapping From: statusReportReq To: MA

44、P ProvideSubscriberInfo Invoke id appStatus users imsi (deduced from information in users) requestedInfo (sequence of optional indicators, of which only subscriberState is present) assignmentID 5.2 statusReportRes statusReportRes is a method that is used by the HLR/SCS towards the application, in re

45、sponse to an earlier request for a user status report. Note that this can be requested for multiple users at the same time. VLR HLR SCS ApplicationProvideSubscriberInfoAckStatusReportResFigure 5-2: Call Flow for statusReportRes Table 5-3: Normal Operation Pre-conditions The application has invoked a

46、 statusReportReq method and this request has been forwarded to the VLR 1 The VLR sends a MAP ProvideSubscriberInfoAck to the HLR/SCS in response to the earlier request 2 The HLR/SCS respond to the application via StatusReportRes In case the Status Report was requested for multiple users, multiple PS

47、I acknowledgements are collected in the HLR/SCS before a response is sent back to the Application Table 5-4: Parameter Mapping To: statusReportRes From: MAP ProvideSubscriberInfoAck Invoke id assignmentID statususerID statusCode subscriberInfo (sequence of optional parameters, of which only subscrib

48、erState present) status subscriberState ETSI ETSI TR 129 998-6 V6.0.0 (2004-12) 113GPP TR 29.998-06 version 6.0.0 Release 6 6 Network User Location Call Flows The Network User Location (NUL) provides location information, based on network-related information. Using the NUL functions, an application

49、programmer can request the VLR number, the Location Area Identifier, geodetic Location Information and the Cell Global Identification and other mobile telephony specific location information, if the network is able to support the corresponding capability. 6.1 locationReportReq locationReportReq is a method used by the application to request for mobile-related location information on one or several users. A request of location information for several users shall mapped to several MAP-operation-requests. HLR gsmSCF SCS ApplicationlocationReportReqAny