ETSI TS 129 198-7-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Application Programming.pdf

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

1、 ETSI TS 129 198-7 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 7: Terminal capabilities Service Capability Feature (SCF) (3GPP

2、 TS 29.198-07 version 9.0.0 Release 9)ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)13GPP TS 29.198-07 version 9.0.0 Release 9Reference RTS/TSGC-0029198-07v900 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

3、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 present document may be made available in more than one electronic version or in

4、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 printers of the PDF version kept on a specific network drive within ETSI Secretariat.

5、 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/status/status.asp If you find errors in the present document, please send your

6、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 restriction extend to reproduction in all media. European Telecommunications Standard

7、s 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 registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is

8、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 TS 129 198-7 V9.0.0 (2010-01)23GPP TS 29.198-07 version 9.0.0 Release 9Intellectual Prop

9、erty 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 and non-members, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); E

10、ssential, 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.org/IPR/home.asp). Pursuant to the ETSI IPR Policy, no investigation, including IPR searches,

11、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, essential to the present document. Foreword This Technical Specification (TS) has been produced by

12、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 being references to the corresponding ETSI deliverables. The cross reference between GS

13、M, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)33GPP TS 29.198-07 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 5g3Introduction 5g31 Scope 7g32 References 7g33 Definitions

14、 and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 8g34 Terminal Capabilities SCF . 8g34.1 General requirements on support of methods . 8g35 Sequence Diagrams 9g35.1 Terminal capabilities triggered example 9g35.2 Terminal capabilities interactive request 10g36 Class Diagrams . 11g37 The

15、Service Interface Specifications 12g37.1 Interface Specification Format . 12g37.1.1 Interface Class 12g37.1.2 Method descriptions 12g37.1.3 Parameter descriptions 12g37.1.4 State Model . 12g37.2 Base Interface . 13g37.2.1 Interface Class IpInterface 13g37.3 Service Interfaces . 13g37.3.1 Overview 13

16、g37.4 Generic Service Interface . 14g37.4.1 Interface Class IpService 14g37.4.1.1 Method setCallback() 14g37.4.1.2 Method setCallbackWithSessionID() 14g38 Terminal Capabilities Interface Classes . 15g38.1 Interface Class IpTerminalCapabilities 16g38.1.1 Method getTerminalCapabilities() 16g38.2 Inter

17、face Class IpExtendedTerminalCapabilities . 17g38.2.0a Method terminalCapabilitiesReportReq() . 18g38.2.1 Method triggeredTerminalCapabilityStartReq() . 19g38.2.2 Method triggeredTerminalCapabilityStop() . 20g38.3 Interface Class IpAppExtendedTerminalCapabilities 21g38.3.0a Method terminalCapabiliti

18、esReportErr() 21g38.3.0b Method terminalCapabilitiesReportRes() . 21g38.3.1 Method triggeredTerminalCapabilityReport() 22g38.3.2 Method triggeredTerminalCapabilityReportErr() . 22g39 State Transition Diagrams 23g310 Service Properties . 23g311 Terminal Capabilities Data Definitions 24g311.1 terminal

19、Identity 24g311.2 TpTerminalCapabilities 24g311.3 TpTerminalCapabilitiesError . 24g311.3a TpTerminalCapabilitiesReport . 24g3ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)43GPP TS 29.198-07 version 9.0.0 Release 911.3b TpTerminalCapabilitiesReportSet 25g311.4 TpTerminalCapabilityChangeCriteria 25g311.5 TpT

20、erminalCapabilityScopeType 25g311.6 TpTerminalCapabilityScope. 25g312 Exception Classes . 26g3Annex A (normative): OMG IDL Description of Terminal Capabilities SCF . 27g3Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF 28g3Annex C (informative): Java API Description of the Te

21、rminal Capabilities SCF 29g3Annex D (informative): Description of Terminal Capabilities SCF for 3GPP2 cdma2000 networks 30g3D.1 General Exceptions. 30g3D.2 Specific Exceptions 30g3D.2.1 Clause 1: Scope 30g3D.2.2 Clause 2: References 30g3D.2.3 Clause 3: Definitions and abbreviations . 30g3D.2.4 Claus

22、e 4: Terminal Capabilities SCF . 30g3D.2.5 Clause 5: Sequence Diagrams 30g3D.2.6 Clause 6: Class Diagrams . 31g3D.2.7 Clause 7: The Service Interface Specifications 31g3D.2.8 Clause 8: Terminal Capabilities Interface Classes . 31g3D.2.9 Clause 9: State Transition Diagrams 31g3D.2.10 Clause 10: Servi

23、ce Properties . 31g3D.2.11 Clause 11: Terminal Capabilities Data Definitions 31g3D.2.12 Clause 12: Exception Classes . 31g3D.2.13 Annex A (normative): OMG IDL Description of Terminal Capabilities SCF . 31g3D.2.14 Annex B (informative): W3C WSDL Description of Terminal Capabilities SCF . 31g3D.2.15 A

24、nnex C (informative): Java API Description of Terminal Capabilities SCF 31g3Annex E (informative): Change history . 32g3History 33g3ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)53GPP TS 29.198-07 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnershi

25、p 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 of release date and an increase

26、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, i.e. technical enhancements, c

27、orrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document is part 7 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; Open Service Acces

28、s (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-part 1: “Call Control Common Definitions“; Sub-p

29、art 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 SCF“; Part 8: “Data Session Control SCF“; Part

30、9: “Generic Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (not part of 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 Messagin

31、g 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. Also in case a Part is not supported in a R

32、elease, the numbering of the parts is maintained. ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)63GPP TS 29.198-07 version 9.0.0 Release 9Table: Overview of the OSA APIs Application Programming Interface; Part 1: Overview“. 2 3GPP TS 22.127: “Service Requirement for the Open Services Access (OSA); Stage 1“

33、. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 World Wide Web Consortium “Composite Capability/Preference Profiles (CC/PP): A user side framework for content negotiation“ (http:/www.w3.org/TR/NOTE-CCPP/). 5 Wireless Application Protocol (WAP), Version 2.0: “User Agent Profiling Specific

34、ation“ (WAP-248) (http:/www.wapforum.org/what/technical.htm). ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)83GPP TS 29.198-07 version 9.0.0 Release 93 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 Abbrevi

35、ations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Terminal Capabilities SCF The following clauses describe each aspect of the Terminal Capability Feature (SCF). The order is as follows: The Sequence diagrams give the reader a practical idea of how eac

36、h of the SCF is implemented. The Class relationships clause shows how each of the interfaces applicable to the SCF, relate to one another. The Interface specification clause describes in detail each of the interfaces shown within the Class diagram part. The State Transition Diagrams (STD) show the t

37、he 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 networks cause state transitions. The Data definitions section shows a detailed expansion of each of the data types asso

38、ciated 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 this specification. 4.1 General requirements on support of methods An implementation of this API which supports or implements a m

39、ethod 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 method. Where a method is not supported by an implementation of a Service interface, the exception P_METHOD_NOT_SUPPORTED s

40、hall 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 exception shall be returned. ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)93GPP TS 29.198-07 version 9.0.0 Release 95 Sequence Diag

41、rams 5.1 Terminal capabilities triggered example The following example sequence diagram illustrates how the terminal capabilities can be retrieved and their changes monitored. Application: IpAppExtendedTerminalCapabilities: IpTer minalCapabilities: IpExtendedTerminalCapabilities1: getTerminalCapabil

42、itiesy( )2: new( )3: triggeredTerminalCapabilityStartReq( )4: triggeredTerminalCapabilityReport( )6: triggeredTerminalCapabilityReport( )5: forward notification7: forward notification8: triggeredTerminalCapabilityReportErr( )9: forward error10: triggeredTerminalCapabilityReport( )11: forward notific

43、ation12: triggeredTerminalCapabilityStop( )1: The application retrieves the terminal capability of a terminal using the synchronous mechanism. The terminalCapabilitiesReportReq method can also be used here, and allows the application to set the scope of capabilities and allows retrieval of terminal

44、capabilities for one or several users. 2: The application creates an object to implement IpAppExtendedTerminalCapabilities. 3: The terminal capabilities changes are started to be monitored. 4: The terminal capabilities have changed and they are reported as requested. 5: The report is forwarded inter

45、nally to the application. 6: The terminal capabilities have changed and they are reported as requested. 7: The report is forwarded internally to the application. ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)103GPP TS 29.198-07 version 9.0.0 Release 98: An error has happened in the monitoring and it is rep

46、orted. 9: The error report is forwarded internally to the application. 10: The terminal capabilities have changed and they are reported as requested. 11: The report is forwarded internally to the application. 12: The terminal capability monitoring is stopped. 5.2 Terminal capabilities interactive re

47、quest The following example sequence diagram illustrates how the terminal capabilities can be retrieved. Application : IpAppExtendedTerminalCapabilities : IpTerminalCapabilities : IpExtendedTerminalCapabilities 1: new( ) 2: terminalCapabilitiesReportReq( ) 3: terminalCapabilitiesReportRes( ) 4: forw

48、ard 1: The application creates an object to implement IpAppExtendedTerminalCapabilities. 2: The terminal capabilities for one or several users are requested. The scope of capabilities can be set for the request. 3: The terminal capabilities are reported. 4: The report is forwarded internally to the

49、application. ETSI ETSI TS 129 198-7 V9.0.0 (2010-01)113GPP TS 29.198-07 version 9.0.0 Release 96 Class Diagrams Terminal Capabilities Class Diagram: IpTerminalCapabilities getTerminalCapabilities() (from termcap) IpService setCallback() setCallbackWithSessionID() (from csapi) IpExtendedTerminalCapabilities terminalCapabilitiesReportReq() triggeredTerminalCapabilityStartReq() (from termcap) IpAppExtendedTerminalCapabilities terminalCapabilitiesReportErr() terminalCapabilitiesReportRes() (from termcap) IpInterface (from csapi) triggeredTerminalC