1、 ETSI ES 202 915-10 V1.4.1 (2006-12)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 10: Connectivity Manager SCF(Parlay 4)floppy3 ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 2 Reference RES/TISPAN-01028-10-OSA Keywords API, IDL, OSA, UML ETSI 650 Route des Lucioles
2、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:/www
3、.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 printin
4、g 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:/por
5、tal.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
6、foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2006. The Parlay Group 2006. All rights reserved. DECTTM, PLUGTESTSTM and UMTSTM are Trade Marks of ETSI registered for the benefit of its Members. TIPHONTMand the TIPHON logo are Trade Marks c
7、urrently being registered by ETSI 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. ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 3 Contents Intellectual Property Rights6 Foreword.6 1 Scope 7 2 References 7 3
8、Definitions and abbreviations.7 3.1 Definitions7 3.2 Abbreviations .8 4 Connectivity Manager SCF9 5 Sequence Diagrams 12 5.1 Operator Selects Service Components and creates a new VPrP.12 5.2 Operator Browses Virtual Provisioned Pipe.13 5.3 Operator Browses SAPs and Sites14 6 Class Diagrams.15 7 The
9、Service Interface Specifications21 7.1 Interface Specification Format .21 7.1.1 Interface Class 21 7.1.2 Method descriptions21 7.1.3 Parameter descriptions22 7.1.4 State Model.22 7.2 Base Interface.22 7.2.1 Interface Class IpInterface 22 7.3 Service Interfaces .22 7.3.1 Overview 22 7.4 Generic Servi
10、ce Interface .22 7.4.1 Interface Class IpService 22 7.4.1.1 Method setCallback()23 7.4.1.2 Method setCallbackWithSessionID()23 8 Connectivity Manager Interface Classes23 8.1 Interface Class IpConnectivityManager .23 8.1.1 Method getQoSMenu().24 8.1.2 Method getEnterpriseNetwork() .24 8.2 Interface C
11、lass IpEnterpriseNetwork24 8.2.1 Method getSiteList().25 8.2.2 Method getVPrN() 25 8.2.3 Method getSite() .25 8.3 Interface Class IpEnterpriseNetworkSite .26 8.3.1 Method getSAPList()26 8.3.2 Method getSiteID().26 8.3.3 Method getSiteLocation() .27 8.3.4 Method getSiteDescription().27 8.3.5 Method g
12、etIPSubnet().27 8.3.6 Method getSAPIPSubnet() .28 8.4 Interface Class IpQoSMenu .28 8.4.1 Method getTemplate() 28 8.4.2 Method getTemplateList() 29 8.5 Interface Class IpQoSTemplate29 8.5.1 Method getTemplateType() 30 8.5.2 Method getDescription().30 8.5.3 Method setSlaID() 31 8.5.4 Method getPipeQo
13、SInfo().31 8.5.5 Method setPipeQoSInfo() .31 ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 4 8.5.6 Method getValidityInfo()32 8.5.7 Method setValidityInfo() 32 8.5.8 Method setProvisionedQoSInfo() .33 8.5.9 Method getProvisionedQoSInfo().33 8.5.10 Method getDsCodepoint() 34 8.6 Interface Class IpVPrN 34
14、8.6.1 Method getVPrPList().35 8.6.2 Method getVPrP().35 8.6.3 Method createVPrP() 36 8.6.4 Method deleteVPrP() 36 8.7 Interface Class IpVPrP .37 8.7.1 Method getVPrPID().37 8.7.2 Method getSlaID() 38 8.7.3 Method getStatus()38 8.7.4 Method getProvisionedQoSInfo().38 8.7.5 Method getValidityInfo()39
15、8.7.6 Method getPipeQoSInfo().39 8.7.7 Method getDsCodepoint() 40 9 State Transition Diagrams40 10 Data Definitions .40 10.1 Connectivity Manager Data Types.41 10.1.1 TpIPSubnet .41 10.1.2 TpIPv4AddType .41 10.1.3 TpIPVersion41 10.1.4 TpVprpStatus42 10.1.5 TpDsCodepoint.42 10.1.6 TpProvisionedQoSInf
16、o .42 10.1.7 TpDelayDescriptor42 10.1.8 TpLossDescriptor .43 10.1.9 TpJitterDescriptor.43 10.1.10 TpNameDescrpTagInt 43 10.1.11 TpNameDescrpTagString .43 10.1.12 TpTagValue 44 10.1.13 TpNameDescrpTagExcessLoadAction.44 10.1.14 TpAction.44 10.1.15 TpPipeQoSInfo.44 10.1.16 TpNameDescrpTagDir45 10.1.17
17、 TpTrafficDirection45 10.1.18 TpEndpoint .45 10.1.19 TpSiteOrSap .45 10.1.20 TpLoadDescriptor.45 10.1.21 TpValidityInfo 45 10.1.22 TpNameDescrpTagDateTime .46 10.1.23 TpNameDescrpTagTimePeriod 46 10.1.24 TpNameDescrpTagTimeOfDay46 10.1.25 TpNameDescrpTagDayOfWeek.46 10.1.26 TpNameDescrpTagMonth 47 1
18、1 Exception Classes.48 Annex A (normative): OMG IDL Description of Connectivity Manager SCF.49 Annex B (informative): W3C WSDL Description of Connectivity Manager SCF.50 Annex C (informative): Java API Description of the Connectivity Management SCF51 Annex D (informative): Record of changes 52 D.1 I
19、nterfaces 52 D.1.1 New 52 D.1.2 Deprecated52 D.1.3 Removed.52 ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 5 D.2 Methods53 D.2.1 New 53 D.2.2 Deprecated53 D.2.3 Modified.53 D.2.4 Removed.53 D.3 Data Definitions .54 D.3.1 New 54 D.3.2 Modified.54 D.3.3 Removed.54 D.4 Service Properties.55 D.4.1 New 55 D.
20、4.2 Deprecated55 D.4.3 Modified.55 D.4.4 Removed.55 D.5 Exceptions 56 D.5.1 New 56 D.5.2 Modified.56 D.5.3 Removed.56 D.6 Others .56 History 57 ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 6 Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declar
21、ed 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 i
22、s 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 re
23、ferenced 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 Net
24、working (TISPAN). The present document is part 10 of a multi-part deliverable covering Open Service Access (OSA); Application Programming Interface (API), as identified below. The API specification (ES 202 915) is structured in the following parts: Part 1: “Overview“; Part 2: “Common Data Definition
25、s“; Part 3: “Framework“; Part 4: “Call Control“; 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“; Part 10: “Connectivity Manager SCF“; Part 11: “Account Management SCF“; Part 12: “Chargin
26、g SCF“; Part 13: “Policy Management SCF“; Part 14: “Presence and Availability Management SCF“. The present document has been defined jointly between ETSI, The Parlay Group (http:/www.parlay.org) and the 3GPP, in co-operation with a number of JAIN Community (http:/ member companies. The present docum
27、ent forms part of the Parlay 4.3 set of specifications. ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 7 1 Scope The present document is part 10 of the Stage 3 specification for an Application Programming Interface (API) for Open Service Access (OSA). The OSA specifications define an architecture that ena
28、bles application developers to make use of network functionality through an open standardised interface, i.e. the OSA APIs. The present document specifies the Connectivity Manager Service Capability Feature (SCF) aspects of the interface. All aspects of the Connectivity Manager SCF are defined here,
29、 these being: Sequence Diagrams. Class Diagrams. Interface specification plus detailed method descriptions. State Transition diagrams. Data Definitions. IDL Description of the interfaces. The process by which this task is accomplished is through the use of object modelling techniques described by th
30、e Unified Modelling Language (UML). 2 References The references listed in clause 2 of ES 202 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 202 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1:
31、Overview (Parlay 4)“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 202 915-1 and the following apply: best effort traffic: traffic that is not carried by a VPrN established for the enterprise network by the provider d
32、ifferentiated services: effort in the Internet Engineering Task Force (IETF) to provide quality of service in networks employing small well defined building blocks from which variety of service may be built DS codepoint: marking associated with a specific VPrP enterprise operator: administrator of t
33、he enterprise network/user of APIs NOTE: Also referred to as operator. operator: enterprise operator provider network: provides a VPN and VPrP service to the enterprise network, and offers APIs for connectivity manager to the enterprise operator NOTE: Also referred to as network service provider. pr
34、ovider: entity that offers the VPN and VPrP services, and implements the APIs in the provider network ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 8 Quality of Service (QoS): collection of service levels delivered by a provider network to an enterprise network NOTE: QoS can be characterised by various p
35、erformance attributes such as: packet loss, packet delay; traffic policing measures such as maximum bandwidth and burst rate for traffic entering the providers network. Service Access Point (SAP): enterprise network is connected to the provider network through the enterprise network service access p
36、oints NOTE: A SAP is typically the egress router from the enterprise network that connects to the provider network. TOS bits: value held in the TOS field NOTE: IETF defined the use the TOS field in the IPv4 packet header as a signalling mechanism aimed at providing definitions of aggregation of flow
37、s, where each aggregate is supported by the same level of QoS. Virtual Private Network (VPN): network that uses a provider network infrastructure to connect geographically separated sites of an enterprise NOTE: Such a network looks like a private network to the enterprise as the sites are connected
38、using tunnelling and security technologies. With no QoS measures, VPN passes all packets among the sites with a best effort approach. Virtual Leased Line (VLL): network that uses a provider network infrastructure to connect two geographically separated sites of an enterprise Virtual Provisioned Netw
39、ork (VPrN): collection of VPrP delivered as a service to a single enterprise network Virtual Provisioned Pipe (VPrP): service provided by the provider network to the enterprise network, which is a type of virtual leased line (VLL) provisioned with QoS levels NOTE: VPrP carries enterprise network tra
40、ffic whose packets are marked with the specific DS Codepoint that is associated with this VPrP. The enterprise operator using APIs can create on-line a VPrP. 3.2 Abbreviations For the purposes of the present document, the abbreviations defined in ES 202 915-1 and the following apply: CIM Common Info
41、rmation Model CM Connectivity Manager DiffServ Differentiated ServicesDMTF Distributed Management Task Force DS Differentiated Services QoS Quality of Service SAP Service Access Point SLA Service Level Agreement terms TOS Type Of Service VLL Virtual Leased Line VPN Virtual Private Network VPrN Virtu
42、al Provisioned Network VPrP Virtual Provisioned Pipe ETSI ETSI ES 202 915-10 V1.4.1 (2006-12) 9 4 Connectivity Manager SCF Connectivity Manager includes the APIs between the enterprise operator and the provider network for the two parties to establish QoS parameters for enterprise network packets tr
43、avelling through the provider network. The Connectivity Manager service provides tools for the enterprise operator to set up a Provisioned QoS service in the provider network. The QoS measures used in the enterprise network are outside the scope of the service. The API does not require any specific
44、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 the enterprise network into the provider network, the packets have to be marked using DS Codepoint marking. Once the packets are so marke
45、d, 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 measures that control the enterprises own traffic passing through the provider network. Using APIs the operator can create virtual provis
46、ioned 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 as a Virtual Leased Line (VLL) provisioned to deliver pre-specified QoS. The provider may offer to the enterprise operator a set of te
47、mplates that are used by the operator to specify a VPrP. For instance, the provider may offer templates for video conferencing, audio conferencing, Gold Service, Silver Service, etc. Using these templates the operator can select and provision a VPrP that specifies the quality of service attributes f
48、or 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 its access point to the provider network can be also specified with attributes such as maximum rate and burst rate. The following is an
49、example of a possible scenario: The provider prepares a template with operator-specified attributes, provider-specified attributes, and unspecified attributes, one for 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 sites and service access points of the enterprise virtual privat
