1、 ETSI TS 129 198-2 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 2: Common data definitions (3GPP TS 29.198-02 version 9.0.0 Rel
2、ease 9)floppy3ETSI ETSI TS 129 198-2 V9.0.0 (2010-01)13GPP TS 29.198-02 version 9.0.0 Release 9Reference RTS/TSGC-0029198-02v900 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
3、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 present document may be made available in more than one electronic version or in print. In any case of ex
4、isting 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 printers of the PDF version kept on a specific network drive within ETSI Secretariat. Users of the present do
5、cument 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/status/status.asp If you find errors in the present document, please send your comment to one of the fo
6、llowing 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 restriction extend to reproduction in all media. European Telecommunications Standards Institute 2010. All ri
7、ghts 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 registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ETSI cur
8、rently 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 TS 129 198-2 V9.0.0 (2010-01)23GPP TS 29.198-02 version 9.0.0 Release 9Intellectual Property Rights IPRs essenti
9、al 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 and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially
10、 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.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by
11、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, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generation Part
12、nership 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 being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI i
13、dentities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-2 V9.0.0 (2010-01)33GPP TS 29.198-02 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions and abbreviations . 8g3
14、3.1 Definitions 8g33.2 Abbreviations . 8g34 Common Data definitions 8g35 Common System Data definitions 8g35.1 Standard Data types 8g35.1.1 TpBoolean. 8g35.1.2 TpInt32 . 8g35.1.3 TpFloat 8g35.1.4 TpLongString 8g35.1.5 TpOctet . 9g35.1.6 TpOctetSet 9g35.1.7 TpString 9g35.1.8 TpAssignmentID . 9g35.1.9
15、 TpSessionID . 9g35.1.10 TpSessionIDSet 9g35.1.11 TpAny . 9g35.1.12 TpAttribute . 9g35.1.13 TpAttributeValue 10g35.1.14 TpAttributeList . 10g35.1.15 TpAttributeSet 10g35.1.16 TpInt64 . 10g35.1.17 TpVersion . 10g35.1.18 TpStringSet . 10g35.1.19 TpStringList 11g35.1.20 TpAttributeTagInfo . 11g35.1.21
16、TpSimpleAttributeValue . 11g35.1.22 TpSimpleAttributeTypeInfo . 11g35.1.23 TpStructuredAttributeType . 12g35.1.24 TpStructuredAttributeValue . 12g35.1.25 TpChar 12g35.1.26 TpWChar 12g35.1.27 TpWString 12g35.1.28 TpInt16 . 12g35.1.29 TpUnsignedInt16 13g35.1.30 TpUnsignedInt32 13g35.1.31 TpUnsignedInt
17、64 13g35.1.32 TpDouble 13g35.1.33 TpXMLString . 13g35.1.34 TpUnorderedOctetSet . 13g35.2 Other Data sorts 13g35.2.1 Sequence of Data Elements 13g35.2.2 Tagged Choice of Data Elements . 13g35.2.3 Numbered Set of Data Elements . 14g35.2.4 Reference 14g35.2.5 Numbered List of Data Elements 14g3ETSI ETS
18、I TS 129 198-2 V9.0.0 (2010-01)43GPP TS 29.198-02 version 9.0.0 Release 95.3 Interface Related Data definitions 14g35.3.1 IpInterface . 14g35.3.2 IpInterfaceRef . 14g35.4 Exception Classes . 15g35.4.1 Underlying Technology Exceptions . 15g35.4.2 TpCommonExceptions . 15g35.4.3 Constants associated wi
19、th TpCommonExceptions . 15g35.4.4 Exceptions available to all methods on all interfaces . 16g35.5 Date- and Time-related Data definitions 16g35.5.1 TpDate 16g35.5.2 TpTime . 17g35.5.3 TpDateAndTime . 17g35.5.4 TpDuration 18g35.5.5 TpTimeInterval . 18g35.6 Address-related Data definitions 18g35.6.1 T
20、pAddress . 18g35.6.2 TpAddressSet 19g35.6.3 TpAddressPresentation . 19g35.6.4 TpAddressScreening . 20g35.6.5 TpAddressPlan 20g35.6.6 TpAddressError 21g35.6.7 TpAddressRange . 21g35.6.8 TpURL 22g35.6.9 TpURN . 22g35.7 Price-related Data definitions . 22g35.7.1 TpPrice 22g35.7.2 TpAoCInfo 23g35.7.3 Tp
21、AoCOrder. 23g35.7.4 TpCallAoCOrderCategory 23g35.7.5 TpChargeAdviceInfo 23g35.7.6 TpCAIElements 24g35.7.7 TpChargePerTime. 24g35.7.8 TpLanguage 24g35.8 Data Types Common Across Call Control and Data Session Control 24g35.8.1 TpDataSessionQosClass . 24g3Annex A (normative): OMG IDL Description of the
22、 Common Data definitions . 25g3Annex B (informative): W3C WSDL Description of the Common Data definitions 26g3Annex C (informative): Java API Description of the Common Data definitions 27g3Annex D (normative): Exception Hierarchy 28g3Annex E (informative): Description of the Common Data definitions
23、for 3GPP2 cdma2000 networks 37g3E.1 General Exceptions. 37g3E.2 Specific Exceptions 37g3E.2.1 Clause 1: Scope 37g3E.2.2 Clause 2: References 37g3E.2.3 Clause 3: Definitions and abbreviations . 37g3E.2.4 Clause 4: Common Data definitions . 37g3E.2.5 Clause 5: Common System Data definitions 37g3E.2.6
24、Annex A (normative): OMG IDL Description of the Common Data definitions . 38g3E.2.7 Annex B (informative): W3C WSDL Description of the Common Data definitions . 38g3E.2.8 Annex C (informative): Java API Description of the Common Data definitions . 38g3E.2.9 Annex D (normative): Exception Hierarchy.
25、38g3Annex F (informative): Change history . 39g3History 40g3ETSI ETSI TS 129 198-2 V9.0.0 (2010-01)53GPP TS 29.198-02 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to co
26、ntinuing 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 of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1
27、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, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editoria
28、l only changes have been incorporated in the document. Introduction The present document is part 2 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network and Terminals; Open Service Access (OSA); Application Programming Interface (API), as ident
29、ified 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-part 1: “Call Control Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub-part 3: “Multi-Part
30、y 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 SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 8) P
31、art 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 Management SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“ The Mapping specification
32、 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. Also in case a Part is not supported in a Release, the numbering of the parts is maintained. ETSI ETSI TS 1
33、29 198-2 V9.0.0 (2010-01)63GPP TS 29.198-02 version 9.0.0 Release 9Table: Overview of the OSA APIs - IDL Description of the data types; - WSDL Description of the data types; - Reference to the Java API description of the data types. This specification has been defined jointly between 3GPP TSG CT WG5
34、, ETSI TISPAN and The Parlay Group, in co-operation with a number of JAIN Community member companies. Maintenance of up to 3GPP Rel-8 and new OSA Stage 1, 2 and 3 work beyond Rel-9 was moved to OMA in June 2008. 2 References The following documents contain provisions which, through reference in this
35、 text, constitute provisions of the present document. References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. For a specific reference, subsequent revisions do not apply. For a non-specific reference, the latest version applies. In th
36、e case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP TS 29.198-1: “Open Service Access; Application Programming Interface; Part 1: Overview“. 2 3GPP T
37、S 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 ISO 8601: “Data elements and interchange formats - Information interchange - Representation of dates and times“. 5 3GPP TS 22.024: “Description of Charge Advice Info
38、rmation (CAI)“. 6 IETF RFC 1738: “Uniform Resource Locators (URL)“. 7 IETF RFC 0822: “Standard for the format of ARPA Internet text messages“. 8 ISO 4217: “Codes for the representation of currencies and funds“. 9 ITU-T Recommendation E.164: “The international public telecommunication numbering plan“
39、. 10 ITU-T Recommendation X.400: “Message handling system and service overview“. 11 ISO 639: “Code for the representation of names of languages“. ETSI ETSI TS 129 198-2 V9.0.0 (2010-01)83GPP TS 29.198-02 version 9.0.0 Release 912 IEEE Std 1003.2 (POSIX 1003.2): “IEEE Standard for Information Technol
40、ogy-Portable Operating System Interface (POSIX)-Part 2“. 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-
41、1 1 apply. 4 Common Data definitions The following clauses describe each aspect of the Common Data definitions. The order is as follows: - The Data definitions clause shows a detailed expansion of each of the data types associated with the methods within the classes. - IDL description of the data ty
42、pes (normative Annex); - WSDL description of the data types (informative Annex); - Reference to the Java API description of the data types (informative Annex). 5 Common System Data definitions These data definitions are assumed to be provided by the client operating system. 5.1 Standard Data types T
43、he APIs assume that the following Data types can be supported. 5.1.1 TpBoolean Defines a Boolean data type. 5.1.2 TpInt32 Defines a signed 32-bit integer. 5.1.3 TpFloat Defines a single precision real number. 5.1.4 TpLongString Defines a Byte string, comprising length and data. The length shall be a
44、t least a 32-bit integer. ETSI ETSI TS 129 198-2 V9.0.0 (2010-01)93GPP TS 29.198-02 version 9.0.0 Release 95.1.5 TpOctet Defines an 8-bit quantity that is not translated during transmission. 5.1.6 TpOctetSet Defines a Numbered List of Data elements of TpOctet. Note that this is an ordered list. 5.1.
45、7 TpString Defines a Byte string, comprising length and data. The length shall be at least a 16-bit integer. 5.1.8 TpAssignmentID Defines an assignment ID with a value that is unique to an instance of an implementation of a given interface (i.e. an object), irrespective of the method invoked on it.
46、This ID may be used, for example, to identify single or multiple event notifications enabled by an object; or by a requesting object to modify or stop functionality ( e.g. event notifications, call load control) associated with a previously supplied assignment ID. The assignment ID is identical to a
47、 TpInt32 type. 5.1.9 TpSessionID Defines a session ID with a value that is at least unique within the context of a specific instance of an SCF. An instance of an SCF is a single service manager instance plus the associated subordinate instances. For example, a single MultiPartyCallControlManager ins
48、tance plus all associated MultiPartyCall and MultiPartyCallLeg instances. The session ID is used to identify different sessions (e.g. different call or call leg sessions) of an interface capable of handling multiple sessions. Example 1, myCallObject may implement the IpCall interface. If so, myCallO
49、bject may handle multiple call sessions, and each call session will be identified by a call session ID value (e.g. 1, 2, 3) that is unique within the context of the SCF instance. Example 2, myCallAndCallLegObject may implement the IpCall and IpCallLeg interfaces. If so, myCallAndCallLegObject may handle multiple call sessions and multiple call leg sessions. Each call session will be identified by a call session ID value (e.g. 1, 2, 3) that is unique within the context of the SCF instance. Similarly, each call leg session will be identif
