ETSI TS 129 199-17-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-17-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-17-2010 Digital cellular telecommunications system (Phase 2+) Universal Mobile Telecommunications System (UMTS) LTE Open Service Access (OSA) Parlay X web services .pdf（30页珍藏版）》请在麦多课文档分享上搜索。

1、 ETSI TS 129 199-17 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 17: Application-driven Quality of Service (QoS) (3GPP TS 29.199-17 version 9.0.

2、0 Release 9)floppy3ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)13GPP TS 29.199-17 version 9.0.0 Release 9Reference RTS/TSGC-0029199-17v900 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

3、- NAF 742 C Association but non lucratif enregistre la Sous-Prfecture de Grasse (06) N 7803/88 Important notice Individual copies of the present document can be downloaded from: http:/www.etsi.org The present document may be made available in more than one electronic version or in print. In any case

4、 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 pres

5、ent 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

6、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 2010.

7、All rights reserved. DECTTM, PLUGTESTSTM, UMTSTM, TIPHONTM, the TIPHON logo and the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM is a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. LTE is a Trade Mark of ET

8、SI currently being registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)23GPP TS 29.199-17 version 9.0.0 Release 9Intellectual Property Rights IPRs

9、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 pote

10、ntially 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

11、out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present document. Foreword This Technical Specification (TS) has been produced by ETSI 3rd Generati

12、on Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the corresponding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and

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

14、ns . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 Detailed service description . 7g35 Namespaces 10g36 Sequence diagrams . 10g36.1 Interface Flow overview . 10g37 XML Schema data type definition . 13g37.1 QoSFeatureProperties structure 13g37.2 Void 13g37.3 QoSFeatureData structure 13g37.4 QoSStatu

15、s structure 13g37.5 TrafficClass structure . 14g37.6 QoSHistory structure 14g37.7 QoSEvent enumeration . 14g38 Web Service interface definition 15g38.1 Interface: ApplicationQoS 15g38.1.1 Operation: applyQoSFeature 15g38.1.1.1 Input message: applyQoSFeatureRequest . 16g38.1.1.2 Output message : appl

16、yQoSFeatureResponse . 16g38.1.1.3 Referenced faults . 16g38.1.2 Operation: modifyQoSFeature 17g38.1.3.1 Output message: modifyQoSFeatureResponse . 17g38.1.3.3 Referenced faults . 17g38.1.4 Operation: removeQoSFeature . 18g38.1.4.1 Input message: removeQoSFeatureRequest 18g38.1.4.2 Output message: re

17、moveQoSFeatureResponse. 18g38.1.4.3 Referenced faults . 18g38.1.5 Operation: getQoSStatus . 19g38.1.5.1 Input message: getQoSStatusRequest . 19g38.1.5.2 Output message: getQoSStatusResponse 19g38.1.5.3 Referenced Faults 19g38.1.6 Operation: getQoSHistory 20g38.1.6.1 Input message: getQoSHistoryReque

18、st . 20g38.1.6.2 Output message: getQoSHistoryResponse 20g38.1.6.3 Referenced Faults 20g38.2 Interface: ApplicationQoSNotificationManager 21g38.2.1 Operation: startQoSNotification . 21g38.2.1.1 Input message: startQoSNotificationRequest 21g38.2.1.2 Output message : startQoSNotificationResponse 21g38

19、.2.1.3 Referenced faults . 21g38.2.2 Operation: stopQoSNotification . 22g38.2.2.1 Input message: stopQoSNotificationRequest 22g38.2.2.1 Output message: stopQoSNotificationResponse. 22g3ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)43GPP TS 29.199-17 version 9.0.0 Release 98.2.2.3 Referenced faults . 22g38

20、.3 Interface: ApplicationQoSNotification. 23g38.3.1 Operation: notifyQoSEvent 23g38.3.1.1 Input message: notifyQoSEventRequest . 23g38.3.1.2 Output message : notifyQoSEventResponse . 23g38.3.1.3 Referenced faults . 23g39 Fault definitions 24g39.1 ServiceException 24g39.1.1 SVC0340: InsufficientConne

21、ctionResources . 24g39.1.2 SVC0341: UnknownQoSFeatureIdentifier . 24g39.1.3 SVC0342: EndUserIsNotOnline . 24g39.1.4 SVC0343: SpecifiedAndTemporaryQoSFeaturesConflict . 24g39.1.5 SVC0344: SpecifiedQoSFeatureNotPermittableAsDefault 24g310 Service policies 24g3Annex A (normative): WSDL of Application-d

22、riven QoS API 25g3Annex B (informative): Description of Parlay X Web Services Part 17: Application-driven Quality of Service (QoS) for 3GPP2 cdma2000 networks 26g3B.1 General Exceptions. 26g3B.2 Specific Exceptions 26g3B.2.1 Clause 1: Scope 26g3B.2.2 Clause 2: References 26g3B.2.3 Clause 3: Definiti

23、ons and abbreviations . 26g3B.2.4 Clause 4: Detailed service description 26g3B.2.5 Clause 5: Namespaces 26g3B.2.6 Clause 6: Sequence diagrams . 27g3B.2.7 Clause 7: XML Schema data type definition 27g3B.2.8 Clause 8: Web Service interface definition 27g3B.2.9 Clause 9: Fault definitions 27g3B.2.10 Cl

24、ause 10: Service policies . 27g3B.2.11 Annex A (normative): WSDL of Application-driven QoS API . 27g3Annex C (informative): Change history . 28g3History 29g3ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)53GPP TS 29.199-17 version 9.0.0 Release 9Foreword This Technical Specification has been produced by th

25、e 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 and publish the present document, and the Parlay Group looks forward to working with the 3GPP communit

26、y 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 modify the contents of the present document, it will be re-released by the TSG with an identifying cha

27、nge 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 TSG approved document under change control. y the second digit is incremented for all changes of subst

28、ance, 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 is part 17 of a multi-part deliverable covering the 3rdGeneration Partnership Project; Technical Specif

29、ication 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: “Short Messaging“ Part 5: “Multimedia Messaging“ Part 6: “Payment“ Part 7: “Account management“ Part 8: “Te

30、rminal 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

31、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-17 V9.0.0 (2010-01)63GPP TS 29.199-17 version 9.0.0 Release 91 Scope The present document is Part 17 of the

32、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 through an open standardized interface, i.e. the OSA APIs. The concepts and the functional architecture fo

33、r 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 Application-driven Quality of Service (QoS) Web Service aspects of the interface. All aspects of the Application-driven QoS Web Service are defined here, these

34、being: Name spaces. Sequence diagrams. Data definitions. Interface specification plus detailed method descriptions. Fault definitions. Service policies. WSDL Description of the interfaces. The present document has been defined jointly between 3GPP TSG CT WG5, ETSI TISPAN and The Parlay Group. Mainte

35、nance 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 this text, constitute provisions of the present document. I. References are either specific (identified by date

36、of publication, edition number, version number, etc.) or non-specific. II. For a specific reference, subsequent revisions do not apply. III. For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference im

37、plicitly 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 the Open Services Access (OSA); Stage 1“. 3 3GPP TS 23.198: “Open Service Access (OSA); Stage 2“. 4 3

38、GPP TS 22.101: “Service aspects; Service principles“. 5 W3C Recommendation (2 May 2001): “XML Schema Part 2: Datatypes“. http:/www.w3.org/TR/2001/REC-xmlschema-2-20010502/. 6 3GPP TS 29.199-1: “Open Service Access (OSA); Parlay X Web Services; Part 1: Common“. 3 Definitions and abbreviations 3.1 Def

39、initions For the purposes of the present document, the terms and definitions given in 3GPP TS 29.199-1 6 apply. ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)73GPP TS 29.199-17 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the abbreviations given in 3GPP TS 29.199-1 6

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

41、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 a

42、re 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 defau

43、lt 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 WSEU wishes to upgrade to faster ISP Service offering E.g

44、. DSL 2048 kbps to 8192 kbpsUpgrade to “Broadband Gold” productapplyQoSFeature()defaultQoSFeature = TrueQoSFeature = DSL_8192EU 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 exa

45、mple 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 mak

46、es 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

47、 DSL_8192) will be applied. ETSI ETSI TS 129 199-17 V9.0.0 (2010-01)83GPP TS 29.199-17 version 9.0.0 Release 9End UserVideo Server AppADQ WSEU wishes to stream a video lasting 3 hours, but requires temporary bandwidth upgrade to support streaming. E.g. EU may only have contracted a 1Mbps DSL service

48、 from ISP.Stream VideoapplyQoSFeature()defaultQoSFeature = FalseQoSFeature = Download_QoSqosFeatureProperties:Duration = 180 minsUpStreamSpeedRate = 256kbpsDownStreamSpeedRate = 4096kbpsEU QoS Profile will be applied in network on a temporary basis only (i.e. for 3 hrs, or until user terminates conn

49、ection).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