1、 ETSI ES 202 504-17 V1.1.1 (2008-05)ETSI Standard Open Service Access (OSA);Parlay X Web Services;Part 17: Application-driven Quality of Service (QoS);(Parlay X 3)floppy3 ETSI ETSI ES 202 504-17 V1.1.1 (2008-05) 2 Reference DES/TISPAN-01034-17-OSA Keywords API, OSA, service ETSI 650 Route des Luciol
2、es 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 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:/
3、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 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 prin
4、ting on 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:/
5、portal.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 t
6、he foregoing 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.
7、3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 202 504-17 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 De
8、finitions8 3.2 Abbreviations .8 4 Detailed service description .8 5 Namespaces10 6 Sequence diagrams.10 6.1 Interface Flow overview.10 7 XML Schema data type definition .12 7.1 QoSFeatureProperties structure12 7.2 Property structure .13 7.3 QoSFeatureData structure 13 7.4 QoSStatus structure 13 7.5
9、TrafficClass structure .13 7.6 QoSHistory structure14 7.7 QoSEvent enumeration.14 8 Web Service interface definition14 8.1 Interface: ApplicationQoS14 8.1.1 Operation: applyQoSFeature 14 8.1.1.1 Input message: applyQoSFeatureRequest .15 8.1.1.2 Output message: applyQoSFeatureResponse15 8.1.1.3 Refer
10、enced faults.15 8.1.2 Operation: modifyQoSFeature15 8.1.2.1 Input message: modifyQoSFeatureRequest 16 8.1.2.2 Output message: modifyQoSFeatureResponse .16 8.1.2.3 Referenced faults.16 8.1.3 Operation: removeQoSFeature .16 8.1.3.1 Input message: removeQoSFeatureRequest16 8.1.3.2 Output message: remov
11、eQoSFeatureResponse.16 8.1.3.3 Referenced faults.17 8.1.4 Operation: getQoSStatus.17 8.1.4.1 Input message: getQoSStatusRequest .17 8.1.4.2 Output message: getQoSStatusResponse 17 8.1.4.3 Referenced Faults17 8.1.5 Operation: getQoSHistory 17 8.1.5.1 Input message: getQoSHistoryRequest .18 8.1.5.2 Ou
12、tput message: getQoSHistoryResponse18 8.1.5.3 Referenced Faults18 8.2 Interface: ApplicationQoSNotificationManager 18 8.2.1 Operation: startQoSNotification .18 8.2.1.1 Input message: startQoSNotificationRequest18 8.2.1.2 Output message: startQoSNotificationResponse.19 8.2.1.3 Referenced faults.19 8.
13、2.2 Operation: stopQoSNotification .19 8.2.2.1 Input message: stopQoSNotificationRequest19 8.2.2.2 Output message: stopQoSNotificationResponse.19 8.2.2.3 Referenced faults.19 ETSI ETSI ES 202 504-17 V1.1.1 (2008-05) 4 8.3 Interface: ApplicationQoSNotification.19 8.3.1 Operation: notifyQoSEvent 19 8.
14、3.1.1 Input message: notifyQoSEventRequest .20 8.3.1.2 Output message: notifyQoSEventResponse20 8.3.1.3 Referenced faults.20 9 Fault definitions20 9.1 ServiceException20 9.1.1 SVC0340: Insufficient Connection Resources20 9.1.2 SVC0341: Unknown QoS Feature Identifier 20 9.1.3 SVC0342: End User Is Not
15、 Online.20 9.1.4 SVC0343: Specified And Existing Temporary QoS Features Conflict 20 9.1.5 SVC0344: QoS Feature Cannot Be Applied As Default.21 10 Service policies 21 Annex A (normative): WSDL for Application-driven QoS22 Annex B (informative): Bibliography.23 History 24 ETSI ETSI ES 202 504-17 V1.1.
16、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 SR 000 314: “Intelle
17、ctual 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 Policy, no investig
18、ation, 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 ETSI Standard (ES)
19、has been produced by ETSI Technical Committee Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN). The present document is part 17 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web Services, as identified below: Part 1: “Comm
20、on“; 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 12: “Multimedia Conf
21、erence“; 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: “Multimedia Multicast Sess
22、ion Management“. ETSI ETSI ES 202 504-17 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 equivalent to 3GPP TS 29.19
23、9-17 V7.0.2 (Release 7). ETSI ETSI ES 202 504-17 V1.1.1 (2008-05) 7 1 Scope The present document is part 17 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 make use of network fun
24、ctionality through an open standardized interface, i.e. the OSA APIs. The present document specifies the Application-driven Quality of Service (QoS) Web Service. The following are defined here: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method description
25、s. 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 reference may
26、 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 are not found
27、 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, in order to en
28、sure 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 lower case lette
29、rs. 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, only the editi
30、on 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 504-17 V1.1.1 (2
31、008-05) 8 2 ETSI ES 202 504-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 504-1 2 apply. 3.2 Abbreviations For the purposes of the
32、 present document, the abbreviations given in ES 202 504-1 2 and the following apply: ADQ Application-Driven Quality of Service QoS Quality of Service 4 Detailed service description Application Driven QoS is a service which enables applications to dynamically change the quality of service (e.g. band
33、width) available on end user network connections. Changes in QoS may be applied on either a temporary basis (i.e. for a defined period of time), or as the default QoS to be applied for a user each time they connect to the network. Applications will govern the quality of service available to the end
34、user by requesting that pre-defined QoS Feature profiles are applied on the end users connection. It is the responsibility of the Service Provider to define these QoS Features and share them beforehand with application providers, along with a clear indication as to which of these can be used as temp
35、orary QoS Features and which can be used to set the default QoS on an end user connection. The following scenarios provide example business use-cases to further illustrate the difference between default and temporary QoS Features and when they may be applied by the application. End User ISP App ADQ
36、WSEU wishes to upgrade to faster ISP Servi ce offering E.g. DSL 2048 kbps to 8192 kbpsUpgrade to “Broadband Gold” productapplyQoSFeature()defa ul tQ oS Featu re = T rueQoSFeature = DSL_8192EU QoS Profile will be applied on a permanent basis. I.e. each time EU terminal attaches to network .Figure 4.1
37、: Example Default QoS Feature Use-Case Figure 4.1 provides an example of where a default QoS Feature could be applied to an end user connection. The scenario given shows the end user of a DSL service requesting a permanent upgrade from their existing service offering (e.g. 2048 kbps) to a higher ban
38、dwidth service (e.g. 8192 kbps). The application subsequently makes a request to the ADQ web service to apply the pre-defined DSL_8192 QoS Feature to the end user connection on a permanent, or default, basis. Following successful completion of this use-case, each time the end users terminal equipmen
39、t attaches to their DSL service, the default QoS (in this case DSL_8192) will be applied. ETSI ETSI ES 202 504-17 V1.1.1 (2008-05) 9 End UserVideo Server AppADQ WSEU wishes to stream a video lasting 3 hours, but requires t em p or ar y bandwidth upgrade to support streami ng. E.g. EU may on l y h av
40、 e contracted a 1Mbps DSL service from ISP.Stream VideoapplyQoSFeature()defaul tQ oS Feature = F al seQoSFeature = Download_QoSqosFeatureProperties:Durati on = 180 m i nsUpStreamSpeedRate = 256kbpsDownS treamS peedRate = 4096kbpsEU QoS Profile will be applied in network on a temporary basis only (i.
41、e. f or 3 hr s, or u nt il us er terminates connection).Figure 4.2: Example Temporary QoS Feature Use-Case Figure 4.2 provides an example of where a temporary QoS Feature could be applied to an end user connection. The scenario given shows an end user of a DSL service who wishes to stream a piece of
42、 video content. Their current service offering (e.g. 1024 kbps DSL) however will not support video streaming and hence they require a temporary bandwidth upgrade for the duration of the video stream. The streaming application then makes a request to the ADQ web service to apply the pre-defined Downl
43、oad_QoS QoS Feature to the end user connection, specifying the upstream and downstream bandwidth rate and the duration for which the temporary QoS Feature should be applied. Assuming that the network supports the requested bandwidth rate, the end users bandwidth will be increased to the rate request
44、ed by the application for the specified duration. Once the requested duration has expired, the end users service will resume to their original (in this example 1024 kbps bandwidth) QoS. Figure 4.3: ADQ Web Service ETSI ETSI ES 202 504-17 V1.1.1 (2008-05) 10The ADQ service is enabled as a Web Service
45、 interface, as depicted in figure 4.3, and will accept four logical kinds of requests from the Applications viz.: Requests to change the default quality of service available on the end users connection, Requests to change the quality of service available on the end users connection on a temporary ba
46、sis, Requests to manage event registrations and Self-care requests. Applications can register with the service for notifications about network events that affect the quality of service temporarily configured on the end users connection. Whenever such events occur, the Service generates notifications
47、 to inform Applications about the impact that these events had on the temporary QoS features set up on the end users connection. Self-care requests enable Applications to view transaction history and current quality of service status. 5 Namespaces The ApplicationQoS interface uses the namespace: htt
48、p:/www.csapi.org/wsdl/parlayx/adq/v3_0 The ApplicationQoSImpactNotificationManager interface uses the namespace: http:/www.csapi.org/wsdl/parlayx/adq/notification_manager/v3_0 The ApplicationQoSImpactNotification uses the namespace: http:/www.csapi.org/wsdl/parlayx/adq/notification/v3_0 The data typ
49、es are defined in the namespace: http:/www.csapi.org/schema/parlayx/adq/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 Interface Flow overview The sequence diagrams show the interaction where the Application Provider has a Web Service compliant Application capable of sending requests to the service and receiving notifications from the service. Every method defined in
