ETSI TS 129 199-18-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services .pdf

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

1、 ETSI TS 129 199-18 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA);Parlay X web services;Part 18: Device capabilities and configuration (3GPP TS 29.199-18 version 9.0.0 Rele

2、ase 9)floppy3ETSI ETSI TS 129 199-18 V9.0.0 (2010-01)13GPP TS 29.199-18 version 9.0.0 Release 9Reference RTS/TSGC-0029199-18v900 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 199-18 V9.0.0 (2010-01)23GPP TS 29.199-18 version 9.0.0 Release 9Intellectual Property Rights IPRs essent

9、ial 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 potentiall

10、y 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 Par

12、tnership 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

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

14、g33.1 Definitions 7g33.2 Abbreviations . 7g34 Detailed service description . 7g34.1 Device Capabilities. 7g34.2 Device Configuration . 7g34.3 Application scenarios . 8g35 Namespaces 9g36 Sequence diagrams . 10g36.1 Device Capability . 10g36.2 Device Configuration . 11g37 XML Schema data type definit

15、ion . 12g37.1 ConfigurationDescription Structure . 12g37.2 ConfigurationHistory Structure 12g37.3 DeviceCapabilities Structure 12g38 Web Service interface definition 13g38.1 Interface: DeviceCapabilities . 13g38.1.1 Operation: getCapabilities 13g38.1.1.1 Input message: getCapabilitiesRequest . 13g38

16、.1.1.2 Output message: getCapabilitiesResponse 13g38.1.1.3 Referenced faults . 13g38.1.2 Operation: getDeviceId . 14g38.1.2.1 Input message: getDeviceIdRequest . 14g38.1.2.2 Output message: getDeviceIdResponse 14g38.1.2.3 Referenced faults . 14g38.2 Interface: DeviceCapabilitiesNotificationManager 1

17、5g38.2.1 Operation: startNotification 15g38.2.1.1 Input message: startNotificationRequest . 15g38.2.1.2 Output message: startNotificationResponse 15g38.2.1.3 Referenced faults . 15g38.2.2 Operation: endNotification . 16g38.2.2.1 Input message: endNotificationRequest 16g38.2.2.2 Output message: endNo

18、tificationResponse . 16g38.2.2.3 Referenced faults. 16g38.3 Interface: DeviceCapabilitiesNotification 17g38.3.1 Operation: deviceNotification . 17g38.3.1.1 Input message: deviceNotificationRequest . 17g38.3.1.2 Output message: deviceNotificationResponse 17g38.3.2 Operation: deviceError . 18g38.3.2.1

19、 Input message: deviceErrorRequest 18g38.3.2.2 Output message: deviceErrorResponse . 18g38.3.3 Operation: deviceEnd . 18g38.3.3.1 Input message: deviceEndRequest 18g38.3.3.2 Output message: deviceEndResponse. 18g3ETSI ETSI TS 129 199-18 V9.0.0 (2010-01)43GPP TS 29.199-18 version 9.0.0 Release 98.4 I

20、nterface: DeviceConfiguration 19g38.4.1 Operation: pushConfiguration 19g38.4.1.1 Input message: pushConfigurationRequest . 19g38.4.1.2 Output message: pushConfigurationResponse 19g38.4.1.3 Referenced faults. 19g38.4.2 Operation getConfigurationList 20g38.4.2.1 Input message: getConfigurationListRequ

21、est 20g38.4.2.2 Output message: getConfigurationListResponse 20g38.4.2.3 Referenced faults. 20g38.4.3 Operation: getConfigurationHistory . 20g38.4.3.1 Input message: getConfigurationHistoryRequest 20g38.4.3.2 Output message: getConfigurationHistoryResponse. 20g38.4.3.3 Referenced faults . 20g39 Faul

22、t definitions 21g310 Service policies 21g3Annex A (normative): WSDL for Device Capabilities and Configuration . 22g3Annex B (informative): Description of Parlay X Web Services Part 18: Device Capabilities and Configuration for 3GPP2 cdma2000 networks 23g3B.1 General Exceptions. 23g3B.2 Specific Exce

23、ptions 23g3B.2.1 Clause 1: Scope 23g3B.2.2 Clause 2: References 23g3B.2.3 Clause 3: Definitions and abbreviations . 23g3B.2.4 Clause 4: Detailed service description 23g3B.2.5 Clause 5: Namespaces 23g3B.2.6 Clause 6: Sequence diagrams . 24g3B.2.7 Clause 7: XML Schema data type definition 24g3B.2.8 Cl

24、ause 8: Web Service interface definition 24g3B.2.9 Clause 9: Fault definitions 24g3B.2.10 Clause 10: Service policies . 24g3B.2.11 Annex A (normative): WSDL for Device Capabilities and Configuration 24g3Annex C (informative): Change history . 25g3History 26g3ETSI ETSI TS 129 199-18 V9.0.0 (2010-01)5

25、3GPP TS 29.199-18 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). 3GPP acknowledges the contribution of the Parlay X Web Services specifications from The Parlay Group. The Parlay Group is pleased to see 3GPP acknowledge

26、and publish the present document, and the Parlay Group looks forward to working with the 3GPP community to improve future versions of the present document. The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG

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

28、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 The present document i

29、s part 18 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specification Group Core Network and Terminals; Open Service Access (OSA); Parlay X Web Services, as identified below: Part 1: “Common“ Part 2: “Third party call“ Part 3: “Call Notification“ Part 4: “Shor

30、t Messaging“ Part 5: “Multimedia Messaging“ Part 6: “Payment“ Part 7: “Account management“ Part 8: “Terminal Status“ Part 9: “Terminal location“ Part 10: “Call handling“ Part 11: “Audio call“ Part 12: “Multimedia conference“ Part 13: “Address list management“ Part 14: “Presence“ Part 15: “Message Br

31、oadcast“ Part 16: “Geocoding“ Part 17: “Application driven Quality of Service (QoS)“ Part 18: “Device Capabilities and Configuration“ Part 19: “Multimedia streaming control“ Part 20: “Multimedia multicast session management“ Part 21: “Content management“ Part 22: “Policy“ ETSI ETSI TS 129 199-18 V9.

32、0.0 (2010-01)63GPP TS 29.199-18 version 9.0.0 Release 91 Scope The present document is Part 18 of the Stage 3 Parlay X Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to make use of network functionality thro

33、ugh an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture for the OSA are contained in 3GPP TS 23.198 3. The requirements for OSA are contained in 3GPP TS 22.127 2. The present document specifies the Device Capabilities and Configuration Web Service aspects

34、of the interface. All aspects of the Device Capabilities and Configuration Web Service are defined here, these being: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service policies. WSDL description of the interfaces.

35、The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. 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 t

36、his 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

37、 the 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 TR 21.905: “Vocabulary for 3GPP Specifications“. 2 3GPP TS 22.127: “Service Requirement for th

38、e Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3GPP TS 22.101: “Service aspects; Service principles“. 5 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS

39、 29.199-1: “Open Service Access (OSA); Parlay X web services; Part 1: Common“. 7 OMA Client Provisioning. See http:/www.wapforum.org/DTD/prov.dtd ETSI ETSI TS 129 199-18 V9.0.0 (2010-01)73GPP TS 29.199-18 version 9.0.0 Release 93 Definitions and abbreviations 3.1 Definitions For the purposes of the

40、present document, the terms and definitions given in 3GPP TS 29.199-1 6 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6 apply. 4 Detailed service description The Parlay X Device Capabilities and Configuration Web Service will allow app

41、lications to get information about device capabilities and push device configuration to a device. 4.1 Device Capabilities and 4.2 Device Configuration gives a description of each of these two possibilities. 4.1 Device Capabilities An application retrieves the device capabilities of a user“s device b

42、y providing their phone number. The device capabilities are described by a user profile XML file, which URL is stored in the DeviceCapability structure returned when the capabilities are requested. In addition there is an operation to get the equipment identifier of the device. (The operation to get

43、 the device identifier is in a separate call, in case there is a wish to restrict this information more than the device capabilities.) In addition it is possible to set up notification for device identifier changes and receive the notifications when the device identifier changes. 4.2 Device Configur

44、ation The application pushes the device configuration to a user“s device by providing their phone number and the configuration (chosen from a list of available configurations.) The application can get the list of available configurations for a given device and the history of the configurations previ

45、ously pushed to the user“s device. ETSI ETSI TS 129 199-18 V9.0.0 (2010-01)83GPP TS 29.199-18 version 9.0.0 Release 94.3 Application scenarios The Parlay X Device Capabilities and Configuration web service relies on the Parlay/OSA Terminal Capabilities SCF and one of the Parlay/OSA or Parlay X Messa

46、ging interfaces. In addition storage for configuration files is provided. . These files should respect the OMA Client Provisioning standard 7. Usually sent to the subscriber device by SMS messages these files may configure settings such as WAP, MMS, Emails, etc. The following figure gives two exampl

47、es of applications that can utilize the Device Capabilities and Configuration web service. One is a Customer Relationship Management Application used by an operator, the other is a Self Care Application used by the subscribers. Parlay X Device Capabilitiesand ConfigurationParlay/OSA TerminalCapabili

48、ties SCFConfigurationstorageParlay (X)MessagingCustomerRelationshipManagementApplicationSelf CareApplicationOperatorSubscriberETSI ETSI TS 129 199-18 V9.0.0 (2010-01)93GPP TS 29.199-18 version 9.0.0 Release 95 Namespaces The DeviceCapabilities interface uses the namespace: http:/www.csapi.org/wsdl/p

49、arlayx/device_capabilities/v4_0 The DeviceCapabilitiesNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/notification_manager/v4_0 The DeviceCapabilitiesNotification interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/notification/v4_0 The DeviceConfiguration interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/device_configuration/v4_0 The data types are defined in the namespace: http:/www.csapi.org/schema/parlay