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

《ETSI TR 129 998-6-2-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf》由会员分享，可在线阅读，更多相关《ETSI TR 129 998-6-2-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programmi_1.pdf（15页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TR 129 998-6-2 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 2: Mapping to Session Initiation Protocol (SIP) (3GPP TR 29.998-06-2 version 9.0.0 Release 9) ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 13GPP TR 29.998-06-2 version 9.0.0 Release 9 Reference RTR/TSGC-0029998-06-2v900 Keywords GSM, LTE, UMTS ETSI 650 Route des Lucioles F-069

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

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

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

6、tsi.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 foreg

7、oing 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

8、registered 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 ETS

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

10、rs 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 server (http:/webapp.ets

11、i.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 be, or may become, ess

12、ential 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 a

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

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

15、4.4 statusReportRes 9g34.5 triggeredStatusReport . 10g35 User Location Service Flows . 11g35.1 locationReportReq 11g35.2 locationReportRes 11g35.3 locationReportErr . 11g35.4 periodicLocationReportingStartReq . 11g35.5 periodicLocationReportingStop . 11g35.6 periodicLocationReport 11g35.7 periodicLo

16、cationReportErr . 11g35.8 triggeredLocationReportingStartReq 11g35.9 triggeredLocationReportingStop 11g35.10 triggeredLocationReport 11g35.11 triggeredLocationReportErr . 11g36 Detailed parameter mappings . 12g36.1 TpAddress 12g3Annex A: Change history . 13g3History 14g3ETSI ETSI TR 129 998-6-2 V9.0

17、.0 (2010-01) 43GPP TR 29.998-06-2 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 formal TSG approval. Should the TSG

18、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 for approval; 3 or greater indicates

19、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. Introduction Structure of the OSA A

20、PI 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: Overview“. 2 3GPP TS 22.127: “Servi

21、ce Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 29.198-2: “Open Service Access (OSA) Application Programming Interface (API); Part 2: Common data definitions“. 4 3GPP TR 21.905: “Vocabulary for 3GPP Specifications“. 5 3GPP TS 29.198-6: “Open Service Access (OSA); Application P

22、rogramming Interface (API); Part 6: Mobility“. 6 3GPP TS 24.229 : “IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP);“, 7 3GPP TS 23.218 : “IP Multimedia (IM) session handling; IM call model; Stage 2“ 8 3GPP TS 22.101: “Service Aspe

23、cts; Service Principles“. 9 IETF RFC 3261: “SIP:Session Initiation Protocol“ 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-2 V9.0.0 (2010-01) 63GPP TR 29.998-06-2 version 9.0.0

24、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.198-1 1 apply. 4 User Status Service SIP Flows The

25、User Status (US) interface class allows applications to obtain the status of mobile telephony users. 4.1 triggeredStatusReportingStartReq TriggeredStatusReportingStartReq is a method that request for triggered status reports when one or several users is registrered/re-registrerd from the IMS core ne

26、twork. The user status service will only send a report when the status changes (registred to de-registred and vice-versa). Application triggeredStatusReportingStartReq OSA SCS SIP server SCS Figure 4-1: Call Flow for triggeredStatusReportingStartReq Table 4-1: Normal Operation Pre-conditions An agre

27、ement is established between the network operator and the service provider for the status notification to be enabled 1 The application invokes the triggeredStatusReportingStartReq method for one or several users 2 The SCS requests the controlled SIP server to observe for 3rd Party SIP REGISTER to be

28、 notified to the application. The SCS reports the current available status to the application using triggeredStatusReport() (see section 4.5 ) ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 73GPP TR 29.998-06-2 version 9.0.0 Release 9 Table 4-2: Parameter Mapping From: triggeredStatusReportingStartReq To

29、: SIP Remarks appStatus (IpAppUserStatusRef) N/A Users (TpAddressSet) See table 6-1 TpAddress (Set) for mapping to SIP TpAssignmentID N/A Returns assignmentID to application, which specifies the ID assigned by the User Status manager interface for this newly trigger notification. 4.2 triggeredStatus

30、ReportingStop triggeredStatusReportingStop is a method that is used by the application to disable triggered user status notifications. Application triggeredStatusReportingStop OSA SCS SIP server SCS Figure 4-2: Call Flow for triggeredStatusReportingStop Table 4-3: Normal Operation Pre-condition The

31、application has invoked triggeredStatusReportingReq() 1 The application invokes the triggeredStatusReportingStop() method for one, several or all users within an assignment (i.e. requested with the corresponding triggeredStatusReportingStartReq() 2 The trigger setting on the appropriate subscriber s

32、tatus is disabled. Table 4-4: Parameter Mapping From: triggeredStatusReportingStop To: SIP Remarks stopRequest : (TpMobilityStopAssignmentData) - stopScope (TpMobilityStopScope) - users (TpAddressSet) - assignmentID (TpAssignmentID) stopScope not mapped to SIP See table 6-1 TpAddress (Set) for mappi

33、ng to SIP TpAssignmentID not mapped to SIP ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 83GPP TR 29.998-06-2 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 (registered/unregistred in IMS core network). Note that th

34、is can be requested for multiple users at the same time. Application statusReportReq OSA SCS SIP server SCS Figure 4-3: Call Flow for statusReportReq Table 4-5: Normal Operation Pre-conditions 1 The application invokes the statusReportReq() method 2 The SCS checks the subscriber status and the curre

35、nt status is returned to the application via statusReportRes(). See section 4.4. Table 4-6: Parameter Mapping From: statusReportReq To: SIP appStatus (IpAppUserStatusRef) N/A Users (TpAddressSet) See table 6-1 TpAddress (Set) for mapping to SIP TpAssignmentID N/A ETSI ETSI TR 129 998-6-2 V9.0.0 (201

36、0-01) 93GPP TR 29.998-06-2 version 9.0.0 Release 9 4.4 statusReportRes statusReportRes delivers a report indicating if a user has been registred or unregistred. Note that this can be requested for multiple users at the same time. User/Core network Application StatusReportRes REGISTER OSA SCS SIP ser

37、ver SCS 200 OK StatusReportReq Figure 4-4: Call Flow for statusReportRes Table 4-7: Normal Operation Pre-condition The application has invoked a statusReportReq 1 The OSA SCS has collected subscriber status based on REGISTER notifications received/or not received from the network. Note that several

38、contact addresses can be registered for a subscriber Address-of-Record. 2 The current subscriber status is returned to the application using statusReportRes(). A subscriber is reachable if at least one valid SIP or TEL contact address is registered. Table 4-8: Parameter Mapping To: statusReportRes F

39、rom: SIP Register Remarks Status (TpUserStatus) userID (TpAddress) SIP URL in the TO header See table 6-1 TpAddress for mapping to SIP statusCode (TpMobilityError) Not mapped to SIP Status (TpUserStatusIndicator) Not mapped to SIP A subscriber is reachable if at least one valid SIP or TEL contact ad

40、dress is registered. TerminalType (TpTerminalType) Not mapped to SIP AssignmentID (TpAssignmentID) N/A ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 103GPP TR 29.998-06-2 version 9.0.0 Release 9 4.5 triggeredStatusReport triggeredStatusReport is a method that is used to notify the application of the the

41、 change of the subscriber(s) status from Registred to Unregistred and vice-versa. User/Core network Application triggeredStatusReport REGISTER OSA SCS SIP server SCS 200 OK Figure 4-5: Call Flow for triggeredStatusReport, triggered by SIP REGISTER Table 4-9: Normal Operation Pre-conditions Status re

42、poting has been enabled by triggerStatusReportingStartReq 1 A third party REGISTER arrives from IMS core network. This request is detected by the SIP Server which determines if an overall status change has occurred for the subscriber 2 If the subscriber status has changed the OSA SCS identifies the

43、application that requested these users status changes (from registred to un-registered and vice-versa) and invokes the triggeredStatusReport method appropriately. Table 4-10: Parameter Mapping To triggeredStatusReport From: SIP Register Remarks Status (TpUserStatus) userID (TpAddress) SIP URL in the

44、 TO header See table 6-1 TpAddress for mapping to SIP statusCode (TpMobilityError) Not mapped to SIP Status (TpUserStatusIndicator) Not mapped to SIP directly. Only a change in the overall subscriber status is reported. A REGISTER could be an initial registration (status change to reachable), refres

45、h an existing contact, add an additional contact or remove one, several or all contacts (removing the last contact would result in a status change to unreachable). Also the registration timer expiring for the last remaining contact would result in a status change to unreachable. TerminalType (TpTerm

46、inalType) Not mapped to SIP AssignmentID (TpAssignmentID) N/A ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 113GPP TR 29.998-06-2 version 9.0.0 Release 9 5 User Location Service Flows 5.1 locationReportReq 5.2 locationReportRes 5.3 locationReportErr 5.4 periodicLocationReportingStartReq 5.5 periodicLoca

47、tionReportingStop 5.6 periodicLocationReport 5.7 periodicLocationReportErr 5.8 triggeredLocationReportingStartReq 5.9 triggeredLocationReportingStop 5.10 triggeredLocationReport 5.11 triggeredLocationReportErr ETSI ETSI TR 129 998-6-2 V9.0.0 (2010-01) 123GPP TR 29.998-06-2 version 9.0.0 Release 9 6

48、Detailed parameter mappings 6.1 TpAddress Table 6-1: TpAddress Table mapping From: TpAddress To: SIP Remark Plan (TpAddressPlan) SIP Specifies the address plan in force. Here only all the address schemes which are allowed in SIP are applicable. AddrString (TpString) Any URL schemes allowed by RFC 32

49、61 Contains a valid SIP address string. A few examples of SIP URLs: - A user of an online service: “sip:userxxx.org“ “sip:alice10.1.1.1“ - A PSTN phone number at a gateway service: “sip:“, “sip: +1-212-555-1212:; user =phone“ An example of tel URL: tel: +1-212-555-1212 Presentation (TpAddressPresentation) N/A Screening (TpAddressScreeing) N/A Name (TpString) N/A SubAddressString (TpString) N/A NOTE: The AddrString defines the actual address information and the structure of the string depends on the Plan. Further inf