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

1、 ETSI TR 129 998-6-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 6: User location - user status

2、 service mapping; Subpart 1: Mapping to Mobile Application Part (MAP) (3GPP TR 29.998-06-1 version 9.0.0 Release 9) ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 13GPP TR 29.998-06-1 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-06-1v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-06921 S

3、ophia 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 present document can be downloaded from: http:/www.etsi.org

4、 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 case of dispute, the reference shall be the printing on ETSI

5、 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 and other ETSI documents is available at http:/portal.etsi.

6、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 authorized by written permission. The copyright and the foregoing

7、 restriction extend to reproduction in all 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 regi

8、stered for the benefit of its Members and 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

9、 129 998-6-1 V9.0.0 (2010-01) 23GPP TR 29.998-06-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 a

10、nd 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 server (http:/webapp.etsi.or

11、g/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 be, or may become, essenti

12、al 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 should be interpreted as be

13、ing 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-1 V9.0.0 (2010-01) 33GPP TR 29.998-06-1 version 9.0.0 Release 9 Contents Intellectual Property Rig

14、hts 2g3Foreword . 2g3Foreword . 4g3Introduction 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 User Status Service CAMEL Flows . 6g34.1 triggeredStatusReportingStartReq 6g34.2 triggeredStatusReportingStop. 7g34.3 statusReportReq . 8g34.

15、4 statusReportRes 9g34.5 triggeredStatusReport . 10g35 User Status Service core-MAP Flows 11g35.1 statusReportReq . 11g35.2 statusReportRes 12g36 Network User Location Call Flows 13g36.1 locationReportReq 13g36.2 locationReportRes 14g36.3 locationReportErr . 15g36.4 periodicLocationReportingStartReq

16、 . 16g36.5 periodicLocationReportingStop . 17g36.6 periodicLocationReport 18g36.7 periodicLocationReportErr . 19g36.8 triggeredLocationReportingStartReq 20g36.9 triggeredLocationReportingStop 21g36.10 triggeredLocationReport 22g36.11 triggeredLocationReportErr . 23g3Annex A: Change history 24g3Histo

17、ry 25g3ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 43GPP TR 29.998-06-1 version 9.0.0 Release 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

18、formal TSG approval. Should the TSG modify the 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 f

19、or approval; 3 or greater indicates TSG approved 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.

20、 Introduction Structure of the OSA API Mapping (3GPP TR 29.998) The present document is part 6 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:

21、 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); Application Programming Interface (API); Pa

22、rt 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 Principles“. 9 ITU-T Recommendation Q.850:

23、“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 Mapping“. ETSI ETSI TR 129 998-6-1 V

24、9.0.0 (2010-01) 63GPP TR 29.998-06-1 version 9.0.0 Release 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.

25、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 triggered user status notifications

26、 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 network operator and the service p

27、rovider 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 requested for multiple users, mu

28、ltiple 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 CAMEL Subscription Information) ass

29、ignmentID gsmSCF-AddressETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 73GPP TR 29.998-06-1 version 9.0.0 Release 9 4.2 triggeredStatusReportingStop triggeredStatusReportingStop is a method that is used by the application to disable triggered user status notifications. HLR gsmSCFSCS ApplicationtriggeredS

30、tatusReportingStopAnyTimeModificationFigure 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 application invokes the triggeredS

31、tatusReportingStop 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. Table 4-4: Parameter Mapping From

32、: 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 (Mobility CAMEL Subscription Informa

33、tion) gsmSCF-AddressETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 83GPP TR 29.998-06-1 version 9.0.0 Release 9 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 gsmSCFS

34、CS ApplicationstatusReportReqAnyTimeInterrogationFigure 4-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 t

35、he Status Report is requested for multiple users, multiple ATI requests are sent to the HLR. Table 4-6: Parameter Mapping From: statusReportReq To: MAP AnyTimeInterrogation Invoke id appStatus users subscriberIdentity requestedInfo (sequence of optional indicators, of which only subscriberState is p

36、resent) gsmSCF-AddressassignmentID ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 93GPP TR 29.998-06-1 version 9.0.0 Release 9 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 ca

37、n be requested for multiple users at the same time. HLR gsmSCFSCS 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

38、1 The HLR sends a MAP AnyTimeInterrogationAck to the HLR/SCS 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 respons

39、e is sent back to the Application. Table 4-8: Parameter Mapping 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-1

40、V9.0.0 (2010-01) 103GPP TR 29.998-06-1 version 9.0.0 Release 9 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

41、 triggeredStatusReport Table 4-9: Normal Operation Pre-conditions 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: M

42、AP noteMM-Event status userID msisdn statusCode status event-Met serviceKeyimsiassignmentID ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 113GPP TR 29.998-06-1 version 9.0.0 Release 9 5 User Status Service core-MAP Flows The User Status (US) interface class allows applications to obtain the status of mo

43、bile telephony users. 5.1 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. VLR HLR SCS ApplicationstatusReportReqProvideSubscriberInfoReqFigure 5-1: Call Flow for statusRe

44、portReq Table 5-1: Normal Operation Pre-conditions 1 The application 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

45、 the VLR Table 5-2: Parameter Mapping From: statusReportReq To: MAP ProvideSubscriberInfo Invoke id appStatus users imsi (deduced from information in users) requestedInfo(sequence of optional indicators, of which only subscriberState is present) assignmentID ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01)

46、 123GPP TR 29.998-06-1 version 9.0.0 Release 9 5.2 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. VLR HLR SCS Application

47、ProvideSubscriberInfoAckStatusReportResFigure 5-2: Call Flow for statusReportRes Table 5-3: Normal Operation Pre-conditions The application has invoked a 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

48、 the earlier request 2 The HLR/SCS respond to the application via StatusReportRes In case the Status Report was requested for multiple users, multiple PSI acknowledgements are collected in the HLR/SCS before a response is sent back to the Application Table 5-4: Parameter Mapping To: statusReportRes

49、From: MAP ProvideSubscriberInfoAck Invoke id assignmentID statususerID statusCode subscriberInfo(sequence of optional parameters, of which only subscriberState present) status subscriberState ETSI ETSI TR 129 998-6-1 V9.0.0 (2010-01) 133GPP TR 29.998-06-1 version 9.0.0 Release 9 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 programmer can request the VLR number, the Location Area Identifier, geodetic Location Informati