1、 ETSI TS 129 198-1 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA)Application Programming Interface (API);Part 1: Overview (3GPP TS 29.198-01 version 9.0.0 Release 9)floppy3E
2、TSI ETSI TS 129 198-1 V9.0.0 (2010-01)13GPP TS 29.198-01 version 9.0.0 Release 9Reference RTS/TSGC-0029198-01v900 Keywords GSM, LTE, 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 Associati
3、on 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 available in more than one electronic version or in print. In any case of existing or perce
4、ived 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 specific network drive within ETSI Secretariat. Users of the present document should b
5、e 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 errors in the present document, please send your comment to one of the following service
6、s: 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 all media. European Telecommunications Standards Institute 2010. All rights reserved.
7、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 of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI currently being re
8、gistered 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 TS 129 198-1 V9.0.0 (2010-01)23GPP TS 29.198-01 version 9.0.0 Release 9Intellectual Property Rights IPRs essential or potential
9、ly 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 SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPR
10、s 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 Policy, no investigation, including IPR searches, has been carried out by ETSI. No guaran
11、tee 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 Technical Specification (TS) has been produced by ETSI 3rd Generation Partnership Project
12、 (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 deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can b
13、e found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)33GPP TS 29.198-01 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3Introduction 6g31 Scope 9g32 References 9g33 Definitions and abbreviations . 9g33.1 Definitions
14、 9g33.2 Abbreviations . 10g34 Open Service Access APIs . 11g35 Structure of the OSA API (29.198) and Mapping (29.998) documents . 12g36 Methodology 14g36.1 Tools and Languages 14g36.2 Packaging . 14g36.3 Colours . 14g36.4 Naming scheme 14g36.5 State Transition Diagram text and text symbols . 15g36.6
15、 Exception handling and passing results 15g36.7 References 15g36.8 Strings and Collections . 15g36.9 Prefixes . 15g37. Introduction to OSA APIs 16g37.1 Interface Types . 16g37.2 Service Factory . 16g37.3 Use of Sessions . 16g37.4 Interfaces and Sessions . 16g37.5 Callback Interfaces . 16g37.6 Settin
16、g Callbacks 17g37.7 Synchronous versus Asynchronous Methods . 17g37.8 Out Parameters . 17g37.9 Exception Hierarchy . 17g37.10 Common Exceptions 18g37.11 Use of NULL 18g37.12 Notification Handling . 18g38 Backwards Compatibility Considerations 19g38.1 Guidelines to enable backwards compatibility in i
17、mplementations . 19g38.2 Rule summary 19g38.2.1 Server side permitted changes 19g38.2.2 Client side permitted changes . 20g38.2.3 Data type permitted changes . 20g38.3 Implementation Guidelines for Server Programmers . 20g38.4 Implementation Guidelines for Client Programmers 20g38.5 Tracking the cha
18、nges in the specifications . 20g38.5.1 New Tag . 20g38.5.2 Deprecated Tag . 21g38.6 Technology realization rules 21g38.6.1 Corba IDL Rules . 21g38.6.2 Java rules 21g38.7 Rules for removal of deprecated items from the specifications 21g3ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)43GPP TS 29.198-01 versio
19、n 9.0.0 Release 9Annex A (normative): OMG IDL . 22g3A.1 Tools and Languages 22g3A.2 Namespace . 22g3A.3 Object References. 22g3A.4 Mapping of Datatypes 22g3A.4.1 Basic Datatypes 22g3A.4.2 Constants 22g3A.4.3 Collections 22g3A.4.4 Sequences . 23g3A.4.5 Enumerations 23g3A.4.6 Choices . 23g3A.5 Use of
20、NULL 24g3A.6 Exceptions 24g3A.7 Naming space across CORBA modules . 24g3Annex B (informative): W3C WSDL 25g3B.1 Tools and Languages 25g3B.2 Proposed Namespaces for the OSA WSDL . 25g3B.3 Object References. 26g3B.4 Mapping UML Data Types to XML Schema . 26g3B.4.1 Data Types 26g3B.4.1.2 . 26g3B.4.1.3
21、27g3B.4.1.4 27g3B.4.1.5 . 27g3B.4.1.6 . 28g3B.4.1.7 28g3B.5 Mapping of UML Interfaces to WSDL 28g3B.5.1 Mapping of UML Operations to WSDL message element. 28g3B.5.2 Mapping of Exception to WSDL message element 29g3B.5.4 Mapping of Interface Class to WSDL portType and binding elements 29g3B.5.5 Mappi
22、ng of UML Interfaces to WSDL service element. 30g3Annex C (informative): Java Realisation API . 31g3C.1 Java Realisation Overview . 31g3C.1.1 J2SE API 31g3C.1.2 J2EE API 31g3C 1.3 Javadoc . 31g3C.2 Tools and languages . 32g3C.3 Generic mappings (Elements common to J2SE and J2EE) 32g3C.3.1 Namespace
23、. 32g3C.3.2 Package Naming Conventions 32g3C.3.3 Object References. 32g3C.3.4 Element Naming . 33g3C.3.5 Element Naming Collisions 33g3C.3.6 Data Type Definitions 33g3C.3.6.1 Basic Data Types 33g3C.3.6.2 Constants 33g3C.3.6.3 NumberedSetsOfDataElements (Collections) . 34g3C.3.6.4 SequenceOfDataEleme
24、nts (Structures) . 34g3C.3.6.5 NameValuePair (Enumerations) . 35g3C.3.6.6 TaggedChoiceOfDataElements (Unions) . 36g3C.3.6.7 Exceptions. 38g3ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)53GPP TS 29.198-01 version 9.0.0 Release 9C.3.6.7.1 PlatformException 38g3C.3.6.7.2 P_XXX_XXX Exceptions 39g3C.3.6.7.3 Tp
25、CommonExceptions 39g3C.3.6.7.4 TpCommonExceptions associated exceptions 40g3C.3.6.7.5 Additional abstract exceptions 40g3C.3.6.7.6 InvalidUnionAccessorException . 41g3C.3.6.7.7 InvalidEnumValueException 41g3C.3.6.8 Deprecation . 41g3C.4 J2SE Specific Conventions. 42g3C.4.1 Removal of “Tp“ Prefix 42g
26、3C.4.2 Constants 42g3C.4.3 Removal of “Ip“ prefix . 43g3C.4.4 Mapping of IpInterface . 43g3C.4.5 Mapping of IpService . 43g3C.4.6 Mapping of UML Operations . 43g3C.4.7 Mapping of TpSessionID . 44g3C.4.8 Mapping of TpAssignmentID to the creation of an Activity object . 44g3C.4.9 Callback Rule . 47g3C
27、.4.10 Factory Rule . 48g3C.4.11 J2SE Specific Exceptions . 50g3C.4.11.1 PeerUnavailableException 50g3C.4.11.2 IllegalStateException 50g3C.4.12 User Interaction Specific Rules 51g3C.4.12.1 Interfaces representing UML IpUI and IpUICall Rule . 51g3C.4.12.2 Naming Collisions of IpUI and IpUICall Rule .
28、51g3C.4.12.3 Naming Collisions of IpUICall and IpUIAdminManager Rule 51g3C.5 J2EE Specific Conventions 51g3C.5.1 Void 51g3C.5.2 Remote Interface Definitions . 51g3C.5.2.1 IpInterface . 51g3C.5.2.2 Methods for Remote Interfaces . 51g3C.5.3 Local Interface Definitions . 52g3C.5.3.1 Methods for Local I
29、nterfaces 52g3C.5.4 Multi Party Call Control Specific Rules . 52g3C.5.4.1 IpCallLeg and IpAppCallLeg method name conflicts 52g3Annex D (informative): Description of Overview for 3GPP2 cdma2000 networks 53g3D.1 General Exceptions. 53g3D.2 Specific Exceptions 53g3D.2.1 Clause 1: Scope 53g3D2.2 Clause
30、2: References 53g3D2.3 Clause 3: Definitions and abbreviations . 53g3D2.4 Clause 4: Open Service Access APIs . 53g3D2.5 Clause 5: Structure of the OSA API (29.198) and Mapping (29.998) documents . 53g3D.2.6 Clause 6: Methodology 54g3D.2.7 Clause 7: Introduction to OSA APIs 54g3D.2.8 Annex A (normati
31、ve): OMG IDL . 54g3D.2.9 Annex B (informative): W3C WSDL . 54g3D.2.10 Annex C (informative): Java API . 54g3Annex E (informative): Change history . 55g3History 56g3ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)63GPP TS 29.198-01 version 9.0.0 Release 9Foreword This Technical Specification has been produced
32、 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 be re-released by the TSG with an identifying change
33、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 second digit is incremented for all changes of substance
34、, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 1 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group
35、Core Network and Terminals; Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts: Part 1: “Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-pa
36、rt 1: “Call Control Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control SCF“; Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities S
37、CF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (new in 3GPP Release 8) Part 11: “Account Management SCF“; Part 12: “Charging SCF“. Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Manage
38、ment SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to network protocols is however not applicable for all Parts, but the numbering of Parts is kept. Al
39、so in case a Part is not supported in a Release, the numbering of the parts is maintained. ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)73GPP TS 29.198-01 version 9.0.0 Release 9Table: Overview of the OSA APIs Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 Void. 5 3GPP TS 22.101: “Ser
40、vice Aspects; Service Principles“. 6 Void. 7 3GPP TS 29.002: “Mobile Application Part (MAP) specification“. 8 3GPP TS 29.078: “Customised Applications for Mobile network Enhanced Logic (CAMEL); CAMEL Application Part (CAP) specification“. 3 Definitions and abbreviations 3.1 Definitions For the purpo
41、ses of the present document, the terms and definitions given in 3GPP TS 22.101 5 and the following apply. Applications: Services, which are designed using Service Capability Features (SCFs). Gateway: Synonym for Service Capability Server (SCS). From the viewpoint of applications, an SCS can be seen
42、as a gateway to the core network. ETSI ETSI TS 129 198-1 V9.0.0 (2010-01)103GPP TS 29.198-01 version 9.0.0 Release 9HE-VASP: Home Environment Value Added Service Provider. This is a VASP that has an agreement with the Home Environment to provide services. Home Environment: responsible for overall pr
43、ovision of services to users. Local Service: A service, which can be exclusively provided in the current serving network by a Value Added Service Provider. OSA Interface: Standardised Interface used by application to access service capability features. Personal Service Environment (PSE): contains pe
44、rsonalised information defining how subscribed services are provided and presented towards the user. The Personal Service Environment is defined in terms of one or more User Profiles. Service Capabilities: Bearers defined by parameters, and/or mechanisms needed to realise services. These are within
45、networks and under network control. Service Capability Feature (SCF): Functionality offered by service capabilities that are accessible via the standardised OSA interface. Service Capability Server (SCS): Functional Entity providing OSA interfaces towards an application. Service: term used as an alt
46、ernative for Service Capability Feature in this specification. User Interface Profile: Contains information to present the personalised user interface within the capabilities of the terminal and serving network. User Profile: This is a label identifying a combination of one user interface profile, a
47、nd one user services profile. User Services Profile: Contains identification of subscriber services, their status and reference to service preferences. Value Added Service Provider: provides services other than basic telecommunications service for which additional charges may be incurred. Virtual Ho
48、me Environment: A concept for personal service environment portability across network boundaries and between terminals. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TR 21.905 1 and the following apply. API Application Programming Interface CAMEL Customi
49、sed Application for Mobile network Enhanced Logic CAP CAMEL Application Part CSE CAMEL Service Environment FW Framework HE Home Environment HE-VASP Home Environment - Value Added Service Provider HLR Home Location Register INAP Intelligent Networks Application Part IDL Interface Description Language JSR Java Specification Request MAP Mobile Application Part ME Mobile Equipment MExE Mobile Station (Application) Execution Environment MS Mobile Station MSC Mobile Switching Centre OSA Open Service AccessPLMN Public Land Mobile Network PSE Personal S
