1、 ETSI ES 201 915-6 V1.5.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 6: Mobility SCF(Parlay 3)floppy3 ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 2 Reference RES/TISPAN-01027-06-OSA Keywords API, OSA, IDL, UML ETSI 650 Route des Lucioles F-06921 Sophia
2、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 The p
3、resent 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 print
4、ers 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.org/tb
5、/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 restr
6、iction extend to reproduction in all media. European Telecommunications Standards Institute 2006. The Parlay Group 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks currently being
7、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 Organizational Partners. ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 3 Contents Intellectual Property Rights7 Foreword.7 1 Scope 8 2 References 8 3 Definitions and
8、abbreviations.8 3.1 Definitions8 3.2 Abbreviations .8 4 Mobility SCF9 4.1 General requirements on support of methods.9 5 Sequence Diagrams 9 5.1 User Location Sequence Diagrams.9 5.1.1 User Location Interrogation - Triggered Request .9 5.1.2 User Location Interrogation - Periodic Request11 5.1.3 Use
9、r Location Interrogation - Parameter Error .12 5.1.4 User Location Interrogation - Network Error .12 5.1.5 User Location Interrogation - Interactive Request13 5.2 User Location Camel Sequence Diagrams .14 5.2.1 User Location Camel Interrogation - Triggered Request14 5.2.2 User Location Camel Interro
10、gation - Periodic Request 15 5.2.3 User Location Camel Interrogation - Parameter Error15 5.2.4 User Location Camel Interrogation - Network Error16 5.2.5 User Location Camel Interrogation - Interactive Request 17 5.3 User Location Emergency Sequence Diagrams .18 5.3.1 Subscription and Network Induced
11、 Location Reports 18 5.3.2 Network Induced Location Reports 19 5.3.3 Interactive Request Parameter Error.19 5.3.4 Interactive Request Network Error .20 5.3.5 Interactive Location Request 20 5.4 User Status Sequence Diagrams.21 5.4.1 Triggered Reporting21 5.4.2 Interactive Request Parameter Error.22
12、5.4.3 Interactive Request Network Error .22 5.4.4 Interactive Request .23 6 Class Diagrams.24 6.1 User Location Class Diagrams .24 6.2 User Location Camel Class Diagrams25 6.3 User Location Emergency Class Diagrams 26 6.4 User Status Class Diagrams27 7 The Service Interface Specifications27 7.1 Inte
13、rface Specification Format .27 7.1.1 Interface Class 27 7.1.2 Method descriptions28 7.1.3 Parameter descriptions28 7.1.4 State Model.28 7.2 Base Interface.28 7.2.1 Interface Class IpInterface 28 7.3 Service Interfaces .28 7.3.1 Overview 28 7.4 Generic Service Interface .28 7.4.1 Interface Class IpSe
14、rvice 28 8 Mobility Interface Classes29 ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 4 8.1 User Location Interface Classes .29 8.1.1 Interface Class IpUserLocation.30 8.1.2 Interface Class IpAppUserLocation33 8.1.3 Interface Class IpTriggeredUserLocation.35 8.1.4 Interface Class IpAppTriggeredUserLocatio
15、n 37 8.2 User Location Camel Interface Classes38 8.2.1 Interface Class IpUserLocationCamel 38 8.2.2 Interface Class IpAppUserLocationCamel .41 8.3 User Location Emergency Interface Classes 44 8.3.1 Interface Class IpUserLocationEmergency 44 8.3.2 Interface Class IpAppUserLocationEmergency46 8.4 User
16、 Status Interface Classes47 8.4.1 Interface Class IpAppUserStatus 47 8.4.2 Interface Class IpUserStatus.48 9 State Transition Diagrams50 9.1 User Location .50 9.2 User Location Camel50 9.2.1 State Transition Diagrams for IpUserLocationCamel.50 9.2.1.1 Active State.51 9.3 User Location Emergency 51 9
17、.4 User Status52 9.4.1 State Transition Diagrams for IpUserStatus .52 9.4.1.1 Active State.52 10 Service Properties.52 10.1 Mobility Properties.52 10.1.1 Emergency Application Subtypes.52 10.1.2 Value Added Application Subtypes53 10.1.3 PLMN Operator Application Subtypes.53 10.1.4 Lawful Intercept A
18、pplication Subtypes 53 10.1.5 Altitude Obtainable.53 10.1.6 Location Methods .53 10.1.7 Priorities54 10.1.8 Max Interactive Requests54 10.1.9 Max Triggered Users 54 10.1.10 Max Periodic Users.54 10.1.11 Min Periodic Interval Duration.54 10.1.12 Initial Report.54 10.2 User Location Service Properties
19、 .54 10.3 User Location Camel Service Properties55 10.4 User Location Emergency Service Properties 56 10.5 User Status Service Properties56 11 Data Definitions .56 11.1 Common Mobility Data Definitions.56 11.1.1 TpGeographicalPosition .56 11.1.2 TpLocationPriority58 11.1.3 TpLocationRequest.58 11.1.
20、4 TpLocationResponseIndicator 58 11.1.5 TpLocationResponseTime 58 11.1.6 TpLocationType .58 11.1.7 TpLocationUncertaintyShape .59 11.1.8 TpMobilityDiagnostic.59 11.1.9 TpMobilityError .59 11.1.10 TpMobilityStopAssignmentData 60 11.1.11 TpMobilityStopScope.60 11.1.12 TpTerminalType .60 11.2 User Loca
21、tion Data Definitions60 11.2.1 IpUserLocation .60 11.2.2 IpUserLocationRef60 11.2.3 IpAppUserLocation 60 11.2.4 IpAppUserLocationRef.60 ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 5 11.2.5 IpTriggeredUserLocation60 11.2.6 IpTriggeredUserLocationRef61 11.2.7 IpAppTriggeredUserLocation.61 11.2.8 IpAppTrig
22、geredUserLocationRef .61 11.2.9 TpUlExtendedData .61 11.2.10 TpUlExtendedDataSet 61 11.2.11 TpUserLocationExtended .61 11.2.12 TpUserLocationExtendedSet 61 11.2.13 TpLocationTrigger62 11.2.14 TpLocationTriggerSet.62 11.2.15 TpLocationTriggerCriteria62 11.2.16 TpUserLocation 62 11.2.17 TpUserLocation
23、Set .62 11.3 User Location Camel Data Definitions 62 11.3.1 IpUserLocationCamel.62 11.3.2 IpUserLocationCamelRef .62 11.3.3 IpAppUserLocationCamel 63 11.3.4 IpAppUserLocationCamelRef 63 11.3.5 TpLocationCellIDOrLAI 63 11.3.6 TpLocationTriggerCamel .63 11.3.7 TpUserLocationCamel63 11.3.8 TpUserLocati
24、onCamelSet.64 11.4 User Location Emergency Data Definitions.64 11.4.1 IpUserLocationEmergency .64 11.4.2 IpUserLocationEmergencyRef .64 11.4.3 IpAppUserLocationEmergency 64 11.4.4 IpAppUserLocationEmergencyRef.64 11.4.5 TpIMEI .64 11.4.6 TpNaESRD.64 11.4.7 TpNaESRK.65 11.4.8 TpUserLocationEmergencyR
25、equest .65 11.4.9 TpUserLocationEmergency 65 11.4.10 TpUserLocationEmergencyTrigger 66 11.5 User Status Data Definitions 66 11.5.1 IpUserStatus66 11.5.2 IpUserStatusRef66 11.5.3 IpAppUserStatus.66 11.5.4 IpAppUserStatusRef .66 11.5.5 TpUserStatus.66 11.5.6 TpUserStatusSet .66 11.5.7 TpUserStatusIndi
26、cator 66 11.6 Units and Validations of Parameters 67 12 Exception Classes.68 Annex A (normative): OMG IDL Description of Mobility SCF 69 Annex B (informative): Contents of 3GPP OSA R4 Mobility 70 Annex C (informative): Record of changes 71 C.1 Interfaces 71 C.1.1 New 71 C.1.2 Deprecated71 C.1.3 Remo
27、ved.71 C.2 Methods71 C.2.1 New 71 C.2.2 Deprecated72 C.2.3 Modified.72 C.2.4 Removed.72 C.3 Data Definitions .72 ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 6 C.3.1 New 72 C.3.2 Modified.72 C.3.3 Removed.73 C.4 Service Properties.73 C.4.1 New 73 C.4.2 Deprecated73 C.4.3 Modified.73 C.4.4 Removed.73 C.5
28、Exceptions 74 C.5.1 New 74 C.5.2 Modified.74 C.5.3 Removed.74 C.6 Others .74 History 75 ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 7 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential
29、 IPRs, if any, is publicly available 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
30、 available on the ETSI Web server (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 W
31、eb server) which are, or may be, or may become, essential to the present document. Foreword This ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 6 of a mul
32、ti-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 201 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control SCF“; Part
33、5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Charging SCF“. The present document has been defined jointly
34、between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-operation with a number of JAIN Community (http:/ member companies. The present document forms part of the Parlay 3.5 set of specifications. A subset of the present document is in 3GPP TS 29.198-6 V4.6.0 (Release 4). ETSI ETSI
35、 ES 201 915-6 V1.5.1 (2006-12) 8 1 Scope The present document is part 6 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functionality th
36、rough an open standardised interface, i.e. the OSA APIs. The present document specifies the Mobility Service Capability Feature (SCF) aspects of the interface. All aspects of the Mobility SCF are defined here, these being: Sequence Diagrams. Class Diagrams. Interface specification plus detailed meth
37、od descriptions. State Transition diagrams. Data Definitions. IDL Description of the interfaces. The process by which this task is accomplished is through the use of object modelling techniques described by the Unified Modelling Language (UML). 2 References The references listed in clause 2 of ES 20
38、1 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 201 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 3)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of t
39、he present document, the terms and definitions given in ES 201 915-1 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 201 915-1 apply. ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 9 4 Mobility SCF The following clauses describe each aspect of the Mobility
40、 Service Capability Feature (SCF). The order is as follows: The Sequence diagrams give the reader a practical idea of how each of the SCFs is implemented. The Class relationships clause show how each of the interfaces applicable to the SCF, relate to one another. The Interface specification clause d
41、escribes in detail each of the interfaces shown within the Class diagram part. The State Transition Diagrams (STD) show the transition between states in the SCF. The states and transitions are well-defined; either methods specified in the Interface specification or events occurring in the underlying
42、 networks cause state transitions. The Data Definitions clause show a detailed expansion of each of the data types associated with the methods within the classes. Note that some data types are used in other methods and classes and are therefore defined within the Common Data types part of the presen
43、t document. 4.1 General requirements on support of methods An implementation of this API which supports or implements a method described in the present document, shall support or implement the functionality described for that method, for at least one valid set of values for the parameters of that me
44、thod. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED shall be returned to any call of that method. Where a method is not supported by an implementation of an Application interface, a call to that method shall be possible, and no exce
45、ption shall be returned. 5 Sequence Diagrams 5.1 User Location Sequence Diagrams 5.1.1 User Location Interrogation - Triggered Request The following sequence diagram shows how an application requests triggered location reports from the User Location service. When users location changes, the service
46、reports this to the application. ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 10: IpAppTriggeredUserLocation : IpTriggeredUserLocation1: triggeredLocationReportingStartReq( )4: triggeredLocationReportingStop( )2: triggeredLocationReport( )3: triggeredLocationReport( )New reports are sent until the trigge
47、red reporting is stopped1: This message is used to start triggered location reporting for one or several users. 2: When the trigger condition is fulfilled then this message passes the location of the affected user to its callback object. 3: This is repeated until the application stops triggered loca
48、tion reporting (see next message). 4: This message is used to stop triggered location reporting. ETSI ETSI ES 201 915-6 V1.5.1 (2006-12) 115.1.2 User Location Interrogation - Periodic Request The following sequence diagram shows how an application requests periodic location reports from the User Loc
49、ation service. : IpAppUserLocation : IpUserLocation1: periodicLocationReportingStartReq( )2: periodicLocationReport( )3: periodicLocationReport( )New reports are sent until the periodic reporting is stopped4: periodicLocationReportingStop( )1: This message is used to start periodic location reporting for one or several users. 2: This message passes the location of one or several users to its callback object. 3: This message passes the location of one or several users to its callback object. This is repeated at regular
