SIST ES 202 504-17 V1.1.1:2008

• Abstract:

  New ParlayX specification to cover Application driven QoS, based on requirements in ES 201 988-4, corresponding to 3GPP TS 29.199-17 Rel-7. 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 functionality 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 descriptions.; • Fault definitions.; • Service Policies.; • WSDL Description of the interfaces.

• Status: Published
• Publication Date: 14-Jul-2008
• ICS: 35.100.01 - Open systems interconnection in general
• Technical Committee: SPN - Services and Protocols for Networks
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 18-Jun-2008
• Due Date: 23-Aug-2008
• Completion Date: 15-Jul-2008
• Ref Project: ETSI ES 202 504-17 V1.1.1 (2008-05) - Open Service Access (OSA); Parlay X Web Services; Part 17: Application-driven Quality of Service (QoS); (Parlay X 3)

SIST ES 202 504-17 V1.1.1:2008 is the SIST reference for an ETSI Standard on Open Service Access (OSA) Parlay X Web Services, Part 17: Application-driven Quality of Service (QoS). It specifies the Application-driven QoS Web Service, including the interfaces, XML data types, faults, service policies, notifications, and WSDL used to request default or temporary QoS changes on end-user connections. It is written for application providers, service providers, and implementers of OSA APIs who need a standardized web service interface for QoS control.

What does SIST ES 202 504-17 V1.1.1:2008 specify?

SIST ES 202 504-17 V1.1.1:2008 specifies the Parlay X 3 Web Service for Application-driven Quality of Service (QoS) within Open Service Access (OSA). In practice, it describes how applications can ask a network to apply, change, remove, monitor, and report QoS features on end-user connections.

The document is organized around the service description, namespaces, sequence diagrams, XML schema data types, interface definitions, fault handling, service policies, and a normative WSDL annex. The sequence diagrams show the request-response and notification flow, so readers can see how the service behaves in use.

Annex	What it covers
Annex A	Normative WSDL for Application-driven QoS
Annex B	Informative bibliography

What are the key requirements of SIST ES 202 504-17 V1.1.1:2008?

Service model and operation flow

Clause 4 states that the service supports two kinds of QoS control: default QoS Feature and temporary QoS Feature. That matters because a provider must decide whether a change is a lasting profile on the connection or a time-limited upgrade.

Clause 6 says the methods are synchronous and notifications are unsolicited. For implementers, that means an application gets an immediate response for a request, and it does not need polling to learn the result.

Clause 4 also says the Service Provider defines the QoS features and shares them with application providers, including which features may be used temporarily and which may be used as default. In practice, this sets the boundary between what the application may request and what the service provider must preconfigure.

Core application operations

Clause 8.1.1 defines applyQoSFeature, which can apply a QoS feature either as the default on the connection or as a temporary change. The request uses defaultQoSFeature to choose the mode, modifyExistingSession when a default change is to be applied to an ongoing connection or the next one, and qosFeatureProperties for temporary-feature settings such as duration and rates.

Clause 8.1.1 also makes clear that default QoS Features have no configurable parameters. For a reader, that means a permanent profile is selected by identifier, while temporary profiles can carry property values.

Clause 8.1.2 defines modifyQoSFeature, which changes the configurable service attributes of an active temporary QoS feature instance using a requestID. Clause 8.1.3 defines removeQoSFeature, which releases a temporary QoS feature by requestID and returns a boolean result.

Status, history, and monitoring

Clause 8.1.4 defines getQoSStatus as a self-care operation for retrieving the status of an end user connection. Its response includes whether the user is connected, the current default QoS feature, supported traffic classes, and the temporary QoS features that are active.

Clause 8.1.5 defines getQoSHistory, which returns the historical list of QoS transactions for an end user connection. It can be filtered by qosFeatureIdentifier, date, maxEntries, and additionalCriteria, so operators can narrow the history to the events they need for support or audit work.

Clause 8.2.1 and Clause 8.2.2 define notification registration and cancellation through startQoSNotification and stopQoSNotification. The application supplies a notification reference, end user identities, and the events to monitor, which means a service can track selected users and selected event types rather than all traffic.

Clause 8.3.1 defines notifyQoSEvent, which reports network events affecting active QoS features. Clause 7.7 limits the event set to AbnormalConnectionTermination, NormalConnectionTermination, and TemporaryQoSFeatureReleased, so implementers know the event vocabulary used by the service.

Data model, faults, and policy controls

Clause 7 defines the data structures used by the service. QoSFeatureProperties carries duration, upstream speed rate, downstream speed rate, and other provider-defined properties; QoSStatus groups the online state, default feature, traffic classes, and active temporary feature data; QoSFeatureData identifies one active temporary feature instance and its current properties.

Clause 9 defines the service faults. The main cases are insufficient connection resources, unknown QoS feature identifier, end user not online, conflict between specified and existing temporary QoS features, and a QoS feature that cannot be applied as default. In practical terms, these faults tell an application why a request failed and whether it needs to retry, choose another feature, or wait for the user to reconnect.

Clause 10 defines service policies for default history timing and the maximum number of historical transactions returned by getQoSHistory. That matters because the service can enforce consistent history windows and result limits even when the application does not provide those values.

What terms does SIST ES 202 504-17 V1.1.1:2008 define?

• Application-Driven Quality of Service (ADQ) - The service that lets applications request QoS changes on end-user connections.
• Quality of Service (QoS) - The service quality level applied to the connection, including features such as bandwidth.
• QoSFeatureProperties - The set of configurable values attached to a temporary QoS feature, such as duration and speed rates.
• QoSFeatureData - The record that identifies one active temporary QoS feature instance and its current values.
• QoSStatus - The status snapshot of an end user connection, including online state, default feature, traffic classes, and active temporary features.
• QoSEvent - The event type reported or monitored for QoS impact, including connection termination and temporary feature release.
• correlator - The identifier used to link a notification registration with the notifications it generates.

Who uses SIST ES 202 504-17 V1.1.1:2008?

Application developers and application providers use this standard when they need to request QoS changes, query status, collect transaction history, or subscribe to notifications through a web service. It is aimed at systems that already talk to network services through OSA APIs.

Service providers and network operators use it to define QoS features, decide which features are temporary or default, and control the policy rules around history and notifications. In practice, that is where the network-side behavior is configured.

It is also relevant to telecom and broadband implementers building OSA or Parlay X 3 platforms, including services such as DSL upgrades and video streaming support. The examples in the document show how an application can raise bandwidth for a connection either permanently or for a limited time.

What changed in SIST ES 202 504-17 V1.1.1:2008 from the previous edition?

SIST ES 202 504-17 V1.1.1:2008 is equivalent to 3GPP TS 29.199-17 V7.0.2 (Release 7).

Which standards are used with SIST ES 202 504-17 V1.1.1:2008?

• W3C Recommendation, XML Schema Part 2: Datatypes - supplies the XML Schema datatypes used throughout the service, such as xsd:string, xsd:boolean, xsd:int, and xsd:dateTime.
• ETSI ES 202 504-1, Open Service Access (OSA); Parlay X Web Services; Part 1: Common (Parlay X 3) - provides the common Parlay X 3 framework, including the shared definitions and terminology that this part relies on.

What does the SIST ES 202 504-17 V1.1.1:2008 document contain?

The document contains a service description, namespace declarations, sequence diagrams, XML schema type definitions, web service interface definitions, fault definitions, and service policies. It also includes a normative WSDL annex for the Application-driven QoS interface.

Clause 7 gives the data structures used in requests, responses, and notifications. Clause 8 describes the operations for applying, modifying, removing, checking, and monitoring QoS features.

Clause 9 lists the service exceptions that an implementation can return, and Clause 10 defines the policy values used by history queries. Annex A provides the WSDL representation used for implementation work, testing, and integration.

Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 17: Application-driven Quality of Service (QoS);
(Parlay X 3)
�
2 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)

Reference
DES/TISPAN-01034-17-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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.
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 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 Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
5 Namespaces.10
6 Sequence diagrams.10
6.1 Interface Flow overview.10
7 XML Schema data type definition .12
7.1 QoSFeatureProperties structure.12
7.2 Property structure.13
7.3 QoSFeatureData structure.13
7.4 QoSStatus structure.13
7.5 TrafficClass structure.13
7.6 QoSHistory structure.14
7.7 QoSEvent enumeration.14
8 Web Service interface definition.14
8.1 Interface: ApplicationQoS.14
8.1.1 Operation: applyQoSFeature.14
8.1.1.1 Input message: applyQoSFeatureRequest.15
8.1.1.2 Output message: applyQoSFeatureResponse.15
8.1.1.3 Referenced faults.15
8.1.2 Operation: modifyQoSFeature.15
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: removeQoSFeatureRequest.16
8.1.3.2 Output message: removeQoSFeatureResponse.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 Faults.17
8.1.5 Operation: getQoSHistory.17
8.1.5.1 Input message: getQoSHistoryRequest.18
8.1.5.2 Output message: getQoSHistoryResponse.18
8.1.5.3 Referenced Faults.18
8.2 Interface: ApplicationQoSNotificationManager .18
8.2.1 Operation: startQoSNotification.18
8.2.1.1 Input message: startQoSNotificationRequest.18
8.2.1.2 Output message: startQoSNotificationResponse.19
8.2.1.3 Referenced faults.19
8.2.2 Operation: stopQoSNotification.19
8.2.2.1 Input message: stopQoSNotificationRequest.19
8.2.2.2 Output message: stopQoSNotificationResponse.19
8.2.2.3 Referenced faults.19
ETSI
4 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
8.3 Interface: ApplicationQoSNotification.19
8.3.1 Operation: notifyQoSEvent.19
8.3.1.1 Input message: notifyQoSEventRequest.20
8.3.1.2 Output message: notifyQoSEventResponse.20
8.3.1.3 Referenced faults.20
9 Fault definitions.20
9.1 ServiceException.20
9.1.1 SVC0340: Insufficient Connection Resources.20
9.1.2 SVC0341: Unknown QoS Feature Identifier .20
9.1.3 SVC0342: End User Is Not 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 QoS.22
Annex B (informative): Bibliography.23
History .24

ETSI
5 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
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: "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 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 ETSI Standard (ES) has been produced by ETSI Technical Committee Telecommunications and Internet
converged Services and Protocols for Advanced Networking (TISPAN), and is now submitted for the ETSI standards
Membership Approval Procedure.
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: "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 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: "Multimedia Multicast Session Management".
ETSI
6 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
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.199-17 V7.0.2 (Release 7).
ETSI
7 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
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 functionality
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 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 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 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, 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 lower 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, 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
8 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
[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 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.
bandwidth) 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 user by requesting that pre-defined QoS Feature
profiles are applied on the end user's 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 temporary 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 WS
EU wishes to Upgrade to “Broadband Gold” product
upgrade to
defaul tQ oSFeature = T rue
faster ISP
QoSFeature = DSL_8192
applyQoSFeature()
Service
offering E.g.
DSL 2048
kbps to 8192
kbps
EU QoS Profile will be
applied on a permanent
basis. I.e. each time EU
terminal attaches to
network .
Figure 4.1: 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 bandwidth 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 user's terminal equipment attaches to
their DSL service, the default QoS (in this case DSL_8192) will be applied.
ETSI
9 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
Video Server App
End User ADQ WS
EU wishes to Stream Video
stream a video
defaultQ oSFeature = F alse
lasting 3
applyQoSFeature() QoSFeature = Download_QoS
hours, but
requires
qosFeatureProperties:
tempor ar y
bandwidth
Duration = 180 mins
upgrade to
UpStreamSpeedRate = 256kbps
support
DownStreamSpeedRate = 4096kbps
streaming.
E.g. EU may
only have
contracted a
1Mbps DSL
service from
EU QoS Profile will be
ISP.
applied in network on a
temporary basis only (i.e.
for 3 hrs, or until user
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 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 'Download_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 user's bandwidth will be increased to the rate requested by the
application for the specified duration. Once the requested duration has expired, the end user's service will resume to
their original (in this example 1024 kbps bandwidth) QoS.

Figure 4.3: ADQ Web Service
ETSI
10 Final draft ETSI ES 202 504-17 V1.1.1 (2008-02)
The ADQ service is enabled as a Web Service 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 user's connection,
• Requests to change the quality of service available
...

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 17: Application-driven Quality of Service (QoS);
(Parlay X 3)
�
2 ETSI ES 202 504-17 V1.1.1 (2008-05)

Reference
DES/TISPAN-01034-17-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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.
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 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 Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 504-17 V1.1.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
5 Namespaces.10
6 Sequence diagrams.10
6.1 Interface Flow overview.10
7 XML Schema data type definition .12
7.1 QoSFeatureProperties structure.12
7.2 Property structure.13
7.3 QoSFeatureData structure.13
7.4 QoSStatus structure.13
7.5 TrafficClass structure.13
7.6 QoSHistory structure.14
7.7 QoSEvent enumeration.14
8 Web Service interface definition.14
8.1 Interface: ApplicationQoS.14
8.1.1 Operation: applyQoSFeature.14
8.1.1.1 Input message: applyQoSFeatureRequest.15
8.1.1.2 Output message: applyQoSFeatureResponse.15
8.1.1.3 Referenced faults.15
8.1.2 Operation: modifyQoSFeature.15
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: removeQoSFeatureRequest.16
8.1.3.2 Output message: removeQoSFeatureResponse.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 Faults.17
8.1.5 Operation: getQoSHistory.17
8.1.5.1 Input message: getQoSHistoryRequest.18
8.1.5.2 Output message: getQoSHistoryResponse.18
8.1.5.3 Referenced Faults.18
8.2 Interface: ApplicationQoSNotificationManager .18
8.2.1 Operation: startQoSNotification.18
8.2.1.1 Input message: startQoSNotificationRequest.18
8.2.1.2 Output message: startQoSNotificationResponse.19
8.2.1.3 Referenced faults.19
8.2.2 Operation: stopQoSNotification.19
8.2.2.1 Input message: stopQoSNotificationRequest.19
8.2.2.2 Output message: stopQoSNotificationResponse.19
8.2.2.3 Referenced faults.19
ETSI
4 ETSI ES 202 504-17 V1.1.1 (2008-05)
8.3 Interface: ApplicationQoSNotification.19
8.3.1 Operation: notifyQoSEvent.19
8.3.1.1 Input message: notifyQoSEventRequest.20
8.3.1.2 Output message: notifyQoSEventResponse.20
8.3.1.3 Referenced faults.20
9 Fault definitions.20
9.1 ServiceException.20
9.1.1 SVC0340: Insufficient Connection Resources.20
9.1.2 SVC0341: Unknown QoS Feature Identifier .20
9.1.3 SVC0342: End User Is Not 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 QoS.22
Annex B (informative): Bibliography.23
History .24

ETSI
5 ETSI ES 202 504-17 V1.1.1 (2008-05)
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: "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 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 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 17 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web
Services, as identified 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 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: "Multimedia Multicast Session Management".
ETSI
6 ETSI ES 202 504-17 V1.1.1 (2008-05)
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.199-17 V7.0.2 (Release 7).
ETSI
7 ETSI ES 202 504-17 V1.1.1 (2008-05)
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 functionality
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 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 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 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, 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 lower 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, 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
8 ETSI ES 202 504-17 V1.1.1 (2008-05)
[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 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.
bandwidth) 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 user by requesting that pre-defined QoS Feature
profiles are applied on the end user's 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 temporary 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 WS
EU wishes to Upgrade to “Broadband Gold” product
upgrade to
defaul tQ oSFeature = T rue
faster ISP
QoSFeature = DSL_8192
applyQoSFeature()
Service
offering E.g.
DSL 2048
kbps to 8192
kbps
EU QoS Profile will be
applied on a permanent
basis. I.e. each time EU
terminal attaches to
network .
Figure 4.1: 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 bandwidth 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 user's terminal equipment attaches to
their DSL service, the default QoS (in this case DSL_8192) will be applied.
ETSI
9 ETSI ES 202 504-17 V1.1.1 (2008-05)
Video Server App
End User ADQ WS
EU wishes to Stream Video
stream a video
defaultQ oSFeature = F alse
lasting 3
applyQoSFeature() QoSFeature = Download_QoS
hours, but
requires
qosFeatureProperties:
tempor ar y
bandwidth
Duration = 180 mins
upgrade to
UpStreamSpeedRate = 256kbps
support
DownStreamSpeedRate = 4096kbps
streaming.
E.g. EU may
only have
contracted a
1Mbps DSL
service from
EU QoS Profile will be
ISP.
applied in network on a
temporary basis only (i.e.
for 3 hrs, or until user
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 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 'Download_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 user's bandwidth will be increased to the rate requested by the
application for the specified duration. Once the requested duration has expired, the end user's service will resume to
their original (in this example 1024 kbps bandwidth) QoS.

Figure 4.3: ADQ Web Service
ETSI
10 ETSI ES 202 504-17 V1.1.1 (2008-05)
The ADQ service is enabled as a Web Service 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 user's connection,
• Requests to change the quality of service available on the end user's connection
...

SLOVENSKI STANDARD
01-september-2008
Odprti dostop do storitve (OSA) - Spletne storitve Parlay X - 17. del: Aplikacijsko
gnana kakovost storitve - (Parlay X 3)
Open Service Access (OSA) - Parlay X Web Services - Part 17: Application-driven
Quality of Service (QoS) - (Parlay X 3)
Ta slovenski standard je istoveten z: ES 202 504-17 Version 1.1.1
ICS:
35.100.01 Medsebojno povezovanje Open systems
odprtih sistemov na splošno interconnection in general
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

ETSI Standard
Open Service Access (OSA);
Parlay X Web Services;
Part 17: Application-driven Quality of Service (QoS);
(Parlay X 3)
�
2 ETSI ES 202 504-17 V1.1.1 (2008-05)

Reference
DES/TISPAN-01034-17-OSA
Keywords
API, OSA, service
ETSI
650 Route des Lucioles
F-06921 Sophia Antipolis Cedex - FRANCE

Tel.: [phone]  Fax: [phone]

Siret N° 348 623 562 00017 - NAF 742 C
Association à but non lucratif enregistrée à la
Sous-Préfecture 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 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.
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 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 Standards Institute 2008.
© The Parlay Group 2008.
All rights reserved.
TM TM TM TM
DECT , PLUGTESTS , UMTS , TIPHON , the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered
for the benefit of its Members.
TM
3GPP is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners.
ETSI
3 ETSI ES 202 504-17 V1.1.1 (2008-05)
Contents
Intellectual Property Rights.5
Foreword.5
1 Scope.7
2 References.7
2.1 Normative references.7
3 Definitions and abbreviations.8
3.1 Definitions.8
3.2 Abbreviations.8
4 Detailed service description .8
5 Namespaces.10
6 Sequence diagrams.10
6.1 Interface Flow overview.10
7 XML Schema data type definition .12
7.1 QoSFeatureProperties structure.12
7.2 Property structure.13
7.3 QoSFeatureData structure.13
7.4 QoSStatus structure.13
7.5 TrafficClass structure.13
7.6 QoSHistory structure.14
7.7 QoSEvent enumeration.14
8 Web Service interface definition.14
8.1 Interface: ApplicationQoS.14
8.1.1 Operation: applyQoSFeature.14
8.1.1.1 Input message: applyQoSFeatureRequest.15
8.1.1.2 Output message: applyQoSFeatureResponse.15
8.1.1.3 Referenced faults.15
8.1.2 Operation: modifyQoSFeature.15
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: removeQoSFeatureRequest.16
8.1.3.2 Output message: removeQoSFeatureResponse.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 Faults.17
8.1.5 Operation: getQoSHistory.17
8.1.5.1 Input message: getQoSHistoryRequest.18
8.1.5.2 Output message: getQoSHistoryResponse.18
8.1.5.3 Referenced Faults.18
8.2 Interface: ApplicationQoSNotificationManager .18
8.2.1 Operation: startQoSNotification.18
8.2.1.1 Input message: startQoSNotificationRequest.18
8.2.1.2 Output message: startQoSNotificationResponse.19
8.2.1.3 Referenced faults.19
8.2.2 Operation: stopQoSNotification.19
8.2.2.1 Input message: stopQoSNotificationRequest.19
8.2.2.2 Output message: stopQoSNotificationResponse.19
8.2.2.3 Referenced faults.19
ETSI
4 ETSI ES 202 504-17 V1.1.1 (2008-05)
8.3 Interface: ApplicationQoSNotification.19
8.3.1 Operation: notifyQoSEvent.19
8.3.1.1 Input message: notifyQoSEventRequest.20
8.3.1.2 Output message: notifyQoSEventResponse.20
8.3.1.3 Referenced faults.20
9 Fault definitions.20
9.1 ServiceException.20
9.1.1 SVC0340: Insufficient Connection Resources.20
9.1.2 SVC0341: Unknown QoS Feature Identifier .20
9.1.3 SVC0342: End User Is Not 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 QoS.22
Annex B (informative): Bibliography.23
History .24

ETSI
5 ETSI ES 202 504-17 V1.1.1 (2008-05)
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: "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 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 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 17 of a multi-part deliverable covering Open Service Access (OSA); Parlay X 3 Web
Services, as identified 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 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: "Multimedia Multicast Session Management".
ETSI
6 ETSI ES 202 504-17 V1.1.1 (2008-05)
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.199-17 V7.0.2 (Release 7).
ETSI
7 ETSI ES 202 504-17 V1.1.1 (2008-05)
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 functionality
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 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 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 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, 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 lower 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, 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
8 ETSI ES 202 504-17 V1.1.1 (2008-05)
[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 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.
bandwidth) 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 user by requesting that pre-defined QoS Feature
profiles are applied on the end user's 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 temporary 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 WS
EU wishes to Upgrade to “Broadband Gold” product
upgrade to
defaul tQ oSFeature = T rue
faster ISP
QoSFeature = DSL_8192
applyQoSFeature()
Service
offering E.g.
DSL 2048
kbps to 8192
kbps
EU QoS Profile will be
applied on a permanent
basis. I.e. each time EU
terminal attaches to
network .
Figure 4.1: 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 bandwidth 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 user's terminal equipment attaches to
their DSL service, the default QoS (in this case DSL_8192) will be applied.
ETSI
9 ETSI ES 202 504-17 V1.1.1 (2008-05)
Video Server App
End User ADQ WS
EU wishes to Stream Video
stream a video
defaultQ oSFeature = F alse
lasting 3
applyQoSFeature() QoSFeature = Download_QoS
hours, but
requires
qosFeatureProperties:
tempor ar y
bandwidth
Duration = 180 mins
upgrade to
UpStreamSpeedRate = 256kbps
support
DownStreamSpeedRate = 4096kbps
streaming.
E.g. EU may
only have
contracted a
1Mbps DSL
service from
EU QoS Profile will be
ISP.
applied in network on a
temporary basis only (i.e.
for 3 hrs, or until user
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 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 'Download_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 user's bandwidth will be increased to the rate requested by the
application for the specified duration. Once the requested duration has expired, the end user's service will resume to
their original (in this example 1024 kbps bandwidth) QoS.

Figure 4.3: ADQ Web Service
ETSI
10 ETSI ES 202 504-17 V1.1.1 (2008-05)
The ADQ service i
...