1、 ETSI TS 129 198-10 V9.0.0 (2010-01)Technical Specification Digital cellular telecommunications system (Phase 2+);Universal Mobile Telecommunications System (UMTS);LTE;Open Service Access (OSA)Application Programming Interface (API);Part 10: Connectivity manager Service Capability Feature (SCF) (3GP
2、P TS 29.198-10 version 9.0.0 Release 9)floppy3ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)13GPP TS 29.198-10 version 9.0.0 Release 9Reference RTS/TSGC-0029198-10v900 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
3、 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.etsi.org The present document may be made available in more than one electronic versi
4、on 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 Sec
5、retariat. 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 s
6、end 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
7、 Standards Institute 2010. 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
8、. LTE is a Trade Mark of ETSI 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 198-10 V9.0.0 (2010-01)23GPP TS 29.198-10 version 9.0.0 Release 9Intelle
9、ctual 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
10、 (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
11、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 Technical Specification (TS) has been pr
12、oduced by ETSI 3rd Generation 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
13、between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)33GPP TS 29.198-10 version 9.0.0 Release 9Contents Intellectual Property Rights 2g3Foreword . 2g3Foreword . 6g3Introduction 6g31 Scope 8g32 References 8g33
14、Definitions and abbreviations . 8g33.1 Definitions 8g33.2 Abbreviations . 9g34 Connectivity Manager SCF 9g35 Sequence Diagrams 13g35.1 Operator Selects Service Components and creates a new VPrP . 13g35.2 Operator Browses Virtual Provisioned Pipe . 13g35.3 Operator Browses SAPs and Sites 15g36 Class
15、Diagrams . 16g37 The Service Interface Specifications 22g37.1 Interface Specification Format . 22g37.1.1 Interface Class 22g37.1.2 Method descriptions 22g37.1.3 Parameter descriptions 23g37.1.4 State Model . 23g37.2 Base Interface . 23g37.2.1 Interface Class IpInterface 23g37.3 Service Interfaces .
16、23g37.3.1 Overview 23g37.4 Generic Service Interface . 23g37.4.1 Interface Class IpService 23g37.4.1.1 Method setCallback() 24g37.4.1.2 Method setCallbackWithSessionID() 24g38 Connectivity Manager Interface Classes 24g38.1 Interface Class IpConnectivityManager . 24g38.1.1 Method getQoSMenu() . 25g38
17、.1.2 Method getEnterpriseNetwork() . 25g38.2 Interface Class IpEnterpriseNetwork 25g38.2.1 Method getSiteList() . 26g38.2.2 Method getVPrN() 26g38.2.3 Method getSite() . 27g38.3 Interface Class IpEnterpriseNetworkSite . 27g38.3.1 Method getSAPList() 28g38.3.2 Method getSiteID() . 28g38.3.3 Method ge
18、tSiteLocation() . 29g38.3.4 Method getSiteDescription() . 29g38.3.5 Method getIPSubnet() . 29g38.3.6 Method getSAPIPSubnet() . 30g38.4 Interface Class IpQoSMenu . 30g38.4.1 Method getTemplate() 31g38.4.2 Method getTemplateList() 31g38.5 Interface Class IpQoSTemplate 32g38.5.1 Method getTemplateType(
19、) 32g38.5.2 Method getDescription() . 33g3ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)43GPP TS 29.198-10 version 9.0.0 Release 98.5.3 Method setSlaID() 33g38.5.4 Method getPipeQoSInfo() . 34g38.5.5 Method setPipeQoSInfo() . 34g38.5.6 Method getValidityInfo() 35g38.5.7 Method setValidityInfo() 35g38.5.8
20、Method setProvisionedQoSInfo() . 35g38.5.9 Method getProvisionedQoSInfo() . 36g38.5.10 Method getDsCodepoint() 37g38.6 Interface Class IpVPrN 37g38.6.1 Method getVPrPList(). 38g38.6.2 Method getVPrP() . 38g38.6.3 Method createVPrP() 39g38.6.4 Method deleteVPrP() 39g38.7 Interface Class IpVPrP . 40g3
21、8.7.1 Method getVPrPID(). 41g38.7.2 Method getSlaID() 41g38.7.3 Method getStatus() 42g38.7.4 Method getProvisionedQoSInfo() . 42g38.7.5 Method getValidityInfo() 43g38.7.6 Method getPipeQoSInfo() . 43g38.7.7 Method getDsCodepoint() 44g39 State Transition Diagrams 44g310 Data Definitions . 44g310.1 Co
22、nnectivity Manager Data Types . 45g310.1.1 TpIPSubnet . 45g310.1.2 TpIPv4AddType . 45g310.1.3 TpIPVersion 45g310.1.4 TpVprpStatus 46g310.1.5 TpDsCodepoint . 46g310.1.6 TpProvisionedQoSInfo . 46g310.1.7 TpDelayDescriptor 46g310.1.8 TpLossDescriptor . 47g310.1.9 TpJitterDescriptor . 47g310.1.10 TpName
23、DescrpTagInt 47g310.1.11 TpNameDescrpTagString . 47g310.1.12 TpTagValue 48g310.1.13 TpNameDescrpTagExcessLoadAction . 48g310.1.14 TpAction . 48g310.1.15 TpPipeQoSInfo . 48g310.1.16 TpNameDescrpTagDir 49g310.1.17 TpTrafficDirection 49g310.1.18 TpEndpoint . 49g310.1.19 TpSiteOrSap . 49g310.1.20 TpLoad
24、Descriptor . 49g310.1.21 TpValidityInfo 49g310.1.22 TpNameDescrpTagDateTime . 50g310.1.23 TpNameDescrpTagTimePeriod 50g310.1.24 TpNameDescrpTagTimeOfDay 50g310.1.25 TpNameDescrpTagDayOfWeek . 50g310.1.26 TpNameDescrpTagMonth 51g311 Exception Classes . 52g3Annex A (normative): OMG IDL Description of
25、Connectivity Manager SCF . 53g3Annex B (informative): W3C WSDL Description of Connectivity Manager SCF . 54g3Annex C (informative): Java API Description of the Connectivity Manager SCF 55g3Annex D (informative): Description of Connectivity Manager for 3GPP2 cdma2000 networks 56g3D.1 General Exceptio
26、ns. 56g3ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)53GPP TS 29.198-10 version 9.0.0 Release 9D.2 Specific Exceptions 56g3D.2.1 Clause 1: Scope 56g3D.2.2 Clause 2: References 56g3D.2.3 Clause 3: Definitions and abbreviations . 56g3D.2.4 Clause 4: Connectivity Manager SCF 56g3D.2.5 Clause 5: Sequence Dia
27、grams 56g3D.2.6 Clause 6: Class Diagrams . 57g3D.2.7 Clause 7: The Service Interface Specifications 57g3D.2.8 Clause 8: Connectivity Manager Interface Classes 57g3D.2.9 Clause 9: State Transition Diagrams 57g3D.2.10 Clause 10: Connectivity Manager Service Properties 57g3D.2.11 Clause 11: Data Defini
28、tions 57g3D.2.12 Clause 12: Exception Classes . 57g3D.2.13 Annex A (normative): OMG IDL Description of Connectivity Manager SCF 57g3D.2.14 Annex B (informative): W3C WSDL Description of Connectivity Manager SCF 57g3Annex E (informative): Change history . 58g3History 59g3ETSI ETSI TS 129 198-10 V9.0.
29、0 (2010-01)63GPP TS 29.198-10 version 9.0.0 Release 9Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TS
30、G modify the contents of the present document, it will be re-released by the TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicate
31、s TSG approved document under change control. y the second digit is incremented for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. Introduction The present document
32、 is part 10 of a multi-part TS covering the 3rdGeneration Partnership Project: Technical Specification Group Core Network; Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (3GPP TS 29.198) is structured in the following Parts: Part 1: “Ov
33、erview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control“; Sub-part 1: “Call Control Common Definitions“; Sub-part 2: “Generic Call Control SCF“; Sub-part 3: “Multi-Party Call Control SCF“; Sub-part 4: “Multi-Media Call Control SCF“; Sub-part 5: “Conference Call Control
34、 SCF“; Part 5: “User Interaction SCF“; Part 6: “Mobility SCF“; Part 7: “Terminal Capabilities SCF“; Part 8: “Data Session Control SCF“; Part 9: “Generic Messaging SCF“; (not part of 3GPP Release 8) Part 10: “Connectivity Manager SCF“; (new in 3GPP Release 8) Part 11: “Account Management SCF“; Part 1
35、2: “Charging SCF“. Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“; Part 15: “Multi Media Messaging SCF“; Part 16: “Service Broker SCF“. The Mapping specification of the OSA APIs and network protocols (3GPP TR 29.998) is also structured as above. A mapping to ne
36、twork protocols is however not applicable for all Parts, but the numbering of Parts is kept. Also in case a Part is not supported in a Release, the numbering of the parts is maintained. ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)73GPP TS 29.198-10 version 9.0.0 Release 9Table: Overview of the OSA APIs
37、Application Programming Interface; Part 1: Overview“. 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“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and d
38、efinitions given in TS 29.198-1 1 apply. ETSI ETSI TS 129 198-10 V9.0.0 (2010-01)93GPP TS 29.198-10 version 9.0.0 Release 93.2 Abbreviations For the purposes of the present document, the abbreviations given in TS 29.198-1 1 apply. 4 Connectivity Manager SCF Connectivity Manager includes the APIs bet
39、ween the enterprise operator and the provider network for the two parties to establish QoS parameters for enterprise network packets travelling through the provider network. The Connectivity Manager service provides tools for the enterprise operator to set up a Provisioned QoS service in the provide
40、r network. The QoS measures used in the enterprise network are outside the scope of the service. The API does not require any specific QoS method to be used in the enterprise network, nor in the provider network. However, in order for Provisioned QoS service to be applied to packets arriving from th
41、e enterprise network into the provider network, the packets have to be marked using DS Codepoint marking. Once the packets are so marked, they can enjoy the QoS service provisioned in the provider network. APIs provide the enterprise network operator on-line access to provision quality of service me
42、asures that control the enterprises own traffic passing through the provider network. Using APIs the operator can create Virtual Provisioned Pipes (VPrPs) in the provider network to carry the enterprise traffic and support it with pre-specified quality of service attributes. A VPrP can be thought of
43、 as a Virtual Leased Line (VLL) provisioned to deliver pre-specified QoS. The provider may offer to the enterprise operator a set of templates that are used by the operator to specify a VPrP. For instance, the provider may offer templates for video conferencing, audio conferencing, Gold Service, Sil
44、ver Service, etc. Using these templates the operator can select and provision a VPrP that specifies the quality of service attributes for this VPrP. Elements that can be specified for a VPrP include attributes such as packet delay and packet loss. Characteristics of traffic that enters the VPrP at i
45、ts access point to the provider network can be also specified with attributes such as maximum rate and burst rate. The following is an example of a possible scenario: The provider prepares a template with operator-specified attributes, provider-specified attributes, and unspecified attributes, one f
46、or each QoS level. The provider generates for the enterprise network a list of all the current sites and their access points to the provider network. Enterprise operator logs into connectivity manager after being authenticated and authorised by the Framework service. Operator gets the list of the si
47、tes and service access points of the enterprise Virtual Private Network (VPN) already provided to the enterprise by the provider. Enterprise operator retrieves the set of templates available to the enterprise (as supported by the SLA), selects one, and requests a template for constructing a new VPrP
48、 based upon the selected QoS. Enterprise operator completes the VPrP template: i.e. selects a value for delay, loss, jitter and excess traffic treatment action, enters the SLA ID against which the template could be validated, selects endpoints, load parameters and traffic flow direction, and selects
49、 the time requirements desired. The enterprise operator can choose or modify those attributes that are operator-specified attributes in the template. Provider-specified attributes cannot be modified and are inherently part of the service. Enterprise operator submits the completed VPrP template for validation by the CM service. Operator creates a new VPrP with pending-status that holds these selections. The provider responds after validating the requests, which may be an approval or a denial (e.g. the requested service is not available at this access
