1、 ETSI ES 202 504-18 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 18: Device Capabilities and Configuration(Parlay X 3)floppy3 ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-18-OSA Keywords API, OSA, service ETSI 650 Route des Lucioles F-06
2、921 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 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.ets
3、i.org The present 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
4、 ETSI printers 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.
5、etsi.org/tb/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 fore
6、going restriction extend to reproduction in all media. European Telecommunications Standards Institute 2008. The Parlay Group 2008. 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
7、is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 7 2 References 7 2.1 Normative references .7 3 Definitions and abbreviations.8 3.1 Definitio
8、ns8 3.2 Abbreviations .8 4 Detailed service description .8 4.1 Device capabilities .8 4.2 Device configuration 8 4.3 Application scenarios .8 5 Namespaces9 6 Sequence diagrams.9 6.1 Device capability9 6.2 Device configuration 10 7 XML Schema data type definition .11 7.1 ConfigurationDescription Stru
9、cture .11 7.2 ConfigurationHistory Structure11 7.3 DeviceCapabilities Structure11 8 Web Service interface definition12 8.1 Interface: DeviceCapabilities .12 8.1.1 Operation: getCapabilities 12 8.1.1.1 Input message: getCapabilitiesRequest .12 8.1.1.2 Output message: getCapabilitiesResponse12 8.1.1.3
10、 Referenced faults.12 8.1.2 Operation: getDeviceId.12 8.1.2.1 Input message: getDeviceIdRequest .12 8.1.2.2 Output message: getDeviceIdResponse 12 8.1.2.3 Referenced faults.13 8.2 Interface: DeviceCapabilitiesNotificationManager 13 8.2.1 Operation: startNotification 13 8.2.1.1 Input message: startNo
11、tificationRequest.13 8.2.1.2 Output message: startNotificationResponse13 8.2.1.3 Referenced faults.13 8.2.2 Operation: endNotification .14 8.2.2.1 Input message: endNotificationRequest14 8.2.2.2 Output message: endNotificationResponse.14 8.2.2.3 Referenced faults.14 8.3 Interface: DeviceCapabilities
12、Notification 14 8.3.1 Operation: deviceNotification.14 8.3.1.1 Input message: deviceNotificationRequest .14 8.3.1.2 Output message: deviceNotificationResponse 15 8.3.2 Operation: deviceError .15 8.3.2.1 Input message: deviceErrorRequest 15 8.3.2.2 Output message: deviceErrorResponse .15 8.3.3 Operat
13、ion: deviceEnd .15 8.3.3.1 Input message: deviceEndRequest 15 8.3.3.2 Output message: deviceEndResponse.15 8.4 Interface: DeviceConfiguration15 8.4.1 Operation: pushConfiguration 15 ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 4 8.4.1.1 Input message: pushConfigurationRequest .16 8.4.1.2 Output message:
14、 pushConfigurationResponse16 8.4.1.3 Referenced faults.16 8.4.2 Operation getConfigurationList16 8.4.2.1 Input message: getConfigurationListRequest16 8.4.2.2 Output message: getConfigurationListResponse 16 8.4.2.3 Referenced faults.16 8.4.3 Operation: getConfigurationHistory .16 8.4.3.1 Input messag
15、e: getConfigurationHistoryRequest17 8.4.3.2 Output message: getConfigurationHistoryResponse.17 8.4.3.3 Referenced faults.17 9 Fault definitions17 10 Service policies 17 Annex A (normative): WSDL for Device Capabilities and Configuration .18 Annex B (informative): Bibliography.19 History 20 ETSI ETSI
16、 ES 202 504-18 V1.1.1 (2008-05) 5 Intellectual Property 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
17、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 available on the ETSI Web server (http:/webapp.etsi.org/IPR/home.asp). Pursuant to the ETSI IPR
18、 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 Web server) which are, or may be, or may become, essential to the present document. Foreword This
19、 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 18 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web Services, as identified
20、below: Part 1: “Common“; Part 2: “Third Party Call“; Part 3: “Call Notification“; Part 4: “Short 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
21、12: “Multimedia Conference“; Part 13: “Address List Management“; Part 14: “Presence“; Part 15: “Message Broadcast“; Part 16: “Geocoding“; Part 17: “Application-driven Quality of Service (QoS)“; Part 18: “Device Capabilities and Configuration“; Part 19: “Multimedia Streaming Control“; Part 20: “Multi
22、media Multicast Session Management“. ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 6 The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP. The present document forms part of the Parlay X 3.0 set of specifications. The present document is equival
23、ent to 3GPP TS 29.199-18 V7.0.0 (Release 7). ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 7 1 Scope The present document is part 18 of the Stage 3 Parlay X 3 Web Services specification for Open Service Access (OSA). The OSA specifications define an architecture that enables application developers to mak
24、e use of network functionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Device Capabilities and Configuration Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed meth
25、od descriptions. Fault definitions. Service Policies. WSDL Description of the interfaces. 2 References References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For a specific reference, subsequent revisions do not apply. Non-specific
26、 reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accepted that it will be possible to use all future changes of the referenced document for the purposes of the referring document; - for informative references. Referenced documents which
27、 are not found to be publicly available in the expected location might be found at http:/docbox.etsi.org/Reference. For online referenced documents, information sufficient to identify and locate the source shall be provided. Preferably, the primary source of the referenced document should be cited,
28、in order to ensure traceability. Furthermore, the reference should, as far as possible, remain valid for the expected life of the document. The reference shall include the method of access to the referenced document and the full network address, with the same punctuation and use of upper case and lo
29、wer case letters. NOTE: While any hyperlinks included in this clause were valid at the time of publication ETSI cannot guarantee their long term validity. 2.1 Normative references The following referenced documents are indispensable for the application of the present document. For dated references,
30、only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. 1 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. NOTE: Available at http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. ETSI ETSI ES 202 50
31、4-18 V1.1.1 (2008-05) 8 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 OMA Client Provisioning. NOTE: Available at http:/www.wapforum.org/DTD/prov.dtd. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, t
32、he terms and definitions given in ES 202 504-1 2 apply. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 202 504-1 2 apply. 4 Detailed service description The Parlay X Device Capabilities and Configuration Web Service will allow applications to get informat
33、ion about device capabilities and push device configuration to a device. 4.1 Device capabilities An application retrieves the device capabilities of a users device by providing their phone number. The device capabilities are described by a user profile XML file, which URL is stored in the DeviceCapa
34、bility 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 the device identifier is in a separate call, in case there is a wish to restrict this information more than the device capabilities.)
35、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 configuration The application pushes the device configuration to a users device by providing their phone number and the configuration (chosen f
36、rom a list of available configurations.) The application can get the list of available configurations for a given device and the history of the configurations previously pushed to the users device. 4.3 Application scenarios The Parlay X Device Capabilities and Configuration web service relies on the
37、 Parlay/OSA Terminal Capabilities SCF and one of the Parlay/OSA or Parlay X Messaging interfaces. In addition storage for configuration files is provided. These files should respect the OMA Client Provisioning standard 3. Usually sent to the subscriber device by SMS messages these files may configur
38、e settings such as WAP, MMS, Emails, etc. The following figure gives two examples 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 subscr
39、ibers. ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 9 Parlay X Device Capabilitiesand ConfigurationParlay/OSA TerminalCapabilities SCFConfigurationstorageParlay (X)MessagingCustomerRelationshipManagementApplicationSelf CareApplicationOperator SubscriberFigure 1 5 Namespaces The DeviceCapabilities interf
40、ace uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/v3_0 The DeviceCapabilitiesNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/notification_manager/v3_0 The DeviceCapabilitiesNotification interface uses the namespace: ht
41、tp:/www.csapi.org/wsdl/parlayx/device_capabilities/notification/v3_0 The DeviceConfiguration interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/device_capabilities/device_configuration/v3_0 The data types are defined in the namespace: http:/www.csapi.org/schema/parlayx/device_capabilitie
42、s/v3_0 The xsd namespace is used in the present document to refer to the XML Schema data types defined in XML Schema 1. The use of the name xsd is not semantically significant. 6 Sequence diagrams 6.1 Device capability The application gets the device capabilities of a device. With the device capabil
43、ities the application can chose the right version of another service to make available for the user (not shown in the diagram). ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 10Parlay X DeviceCapabilities andConfigurationWeb ServiceParlay XApplicationgetCapabilities (user phone number)Device CapabilitiesR
44、etrieveSubscribershandsetscapabilitiesFigure 2 6.2 Device configuration The first device configuration sequence diagram shows how an application for a customer service operator can utilize the configuration history when a customer calls in with configuration problems. The application first gets the
45、configuration history, and then the customer service operator chooses to push the previous configuration to the device. Parlay X DeviceCapabilities andConfigurationWeb ServiceParlay XApplicationgetConfigurationHistory(user phone number)Configuration History RetrieveSubscribersconfigurationhistorypus
46、hConfiguration(user phone number, configuration)Operator updatessubscribersconfigurationwith previousconfigurationFigure 3 Another possibility is for the customer service operator to check available configurations for the customers device when the customer calls. Then the operator chooses a configur
47、ation to push to the device. ETSI ETSI ES 202 504-18 V1.1.1 (2008-05) 11Parlay X DeviceCapabilities andConfigurationWeb ServiceParlay XApplicationgetConfigurationListuser phone number)Configuration pushConfiguration(user phone number, configuration)Retrieveconfigurations available forsubscribersdevi
48、ceOperatorupdaessubscribersconfigurationFigure 4 7 XML Schema data type definition 7.1 ConfigurationDescription Structure Data structure containing the configuration ID, name, description and a link to the URL where the configuration XML file can be found. Element Name Element Type Optional Descript
49、ion configurationId xsd:string No A unique identifier for the Configuration name xsd:string No The name of the configuration. description xsd:string No The description of the configuration configurationReference xsd:anyURI No The URL where the configuration XML file can be found 7.2 ConfigurationHistory Structure Data structure containing configuration (ConfigurationDescription) and a timestamp for when this configuration was sent to a device address. Element Name Element Type Optional Description configuration Configura
