1、 ETSI ES 201 915-10 V1.4.1 (2003-07)ETSI Standard Open Service Access (OSA);Application Programming Interface (API);Part 10: Connectivity Manager SCF(Parlay 3)floppy3 ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 2 Reference RES/SPAN-120095-10 Keywords API, OSA, IDL, UML ETSI 650 Route des Lucioles F-069
2、21 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.etsi
3、.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
4、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.e
5、tsi.org/tb/status/status.asp If you find errors in the present document, send your comment to: editoretsi.org 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 Telecom
6、munications Standards Institute 2003. The Parlay Group 2003. 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 currently being registered by ETSI for the benefit of its Members. 3GPPTM is
7、 a Trade Mark of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 3 Contents Intellectual Property Rights5 Foreword.5 1 Scope 6 2 References 6 3 Definitions and abbreviations.6 3.1 Definitions6 3.2 Abbreviations .7 4 Con
8、nectivity Manager SCF8 5 Sequence Diagrams 11 5.1 Operator Selects Service Components and creates a new VPrP.11 5.2 Operator Browses Virtual Provisioned Pipe.12 5.3 Operator Browses SAPs and Sites13 6 Class Diagrams.14 7 The Service Interface Specifications20 7.1 Interface Specification Format .20 7
9、.1.1 Interface Class 20 7.1.2 Method descriptions20 7.1.3 Parameter descriptions21 7.1.4 State Model.21 7.2 Base Interface.21 7.2.1 Interface Class IpInterface 21 7.3 Service Interfaces .21 7.3.1 Overview 21 7.4 Generic Service Interface .21 7.4.1 Interface Class IpService 21 8 Connectivity Manager
10、Interface Classes22 8.1 Interface Class IpConnectivityManager .22 8.2 Interface Class IpEnterpriseNetwork24 8.3 Interface Class IpEnterpriseNetworkSite .26 8.4 Interface Class IpQoSMenu .28 8.5 Interface Class IpQoSTemplate30 8.6 Interface Class IpVPrN 35 8.7 Interface Class IpVPrP .38 9 State Trans
11、ition Diagrams42 10 Data Definitions .42 10.1 Connectivity Manager Data Types.43 10.1.1 TpStringList43 10.1.2 TpIPSubnet .43 10.1.3 TpIPv4AddType .43 10.1.4 TpIPVersion43 10.1.5 TpVprpStatus44 10.1.6 TpDsCodepoint.44 10.1.7 TpProvisionedQoSInfo .44 10.1.8 TpDelayDescriptor44 10.1.9 TpLossDescriptor
12、.45 10.1.10 TpJitterDescriptor.45 10.1.11 TpNameDescrpTagInt 45 10.1.12 TpNameDescrpTagString .45 10.1.13 TpTagValue 46 10.1.14 TpNameDescrpTagExcessLoadAction.46 ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 4 10.1.15 TpAction.46 10.1.16 TpPipeQoSInfo.46 10.1.17 TpNameDescrpTagDir47 10.1.18 TpTrafficDir
13、ection47 10.1.19 TpEndpoint .47 10.1.20 TpSiteOrSap .47 10.1.21 TpLoadDescriptor.47 10.1.22 TpValidityInfo 48 10.1.23 TpNameDescrpTagDateTime .48 10.1.24 TpNameDescrpTagTimePeriod 48 10.1.25 TpNameDescrpTagTimeOfDay48 10.1.26 TpNameDescrpTagDayOfWeek.49 10.1.27 TpNameDescrpTagMonth 49 11 Exception C
14、lasses.51 Annex A (normative): OMG IDL Description of Connectivity Manager SCF.52 Annex B (informative): Record of changes 53 B.1 Interfaces 53 B.1.1 New 53 B.1.2 Deprecated53 B.1.3 Removed.53 B.2 Methods53 B.2.1 New 53 B.2.2 Deprecated53 B.2.3 Modified.54 B.2.4 Removed.54 B.3 Data Definitions .54 B
15、.3.1 New 54 B.3.2 Modified.54 B.3.3 Removed.54 B.4 Service Properties.54 B.4.1 New 54 B.4.2 Deprecated55 B.4.3 Modified.55 B.4.4 Removed.55 B.5 Exceptions 55 B.5.1 New 55 B.5.2 Modified.55 B.5.3 Removed.55 B.6 Others .55 History 56 ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 5 Intellectual Property Rig
16、hts 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
17、, 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
18、 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 Com
19、mittee Services and Protocols for Advanced Networks (SPAN). 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 201 915) is structured in the following parts: Part 1: “
20、Overview“; Part 2: “Common Data Definitions“; Part 3: “Framework“; Part 4: “Call Control 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“; Part 10: “Connectivity Manager SCF“; Part 1
21、1: “Account Management SCF“; Part 12: “Charging 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 document forms part of the Parlay 3.3 set of s
22、pecifications. ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 6 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 enables application developers to make use o
23、f 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, these being: Sequence Diagrams Class Dia
24、grams 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 the Unified Modelling Language (UML). 2 Reference
25、s The references listed in clause 2 of ES 201 915-1 contain provisions which, through reference in this text, constitute provisions of the present document. ETSI ES 201 915-1: “Open Service Access (OSA); Application Programming Interface (API); Part 1: Overview (Parlay 3)“. 3 Definitions and abbrevi
26、ations 3.1 Definitions For the purposes of the present document, the terms and definitions given in ES 201 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 differentiated services: effort in the Internet
27、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 the enterprise network/user of APIs also referre
28、d 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 also referred to as network service provider provider: entity that offers the VPN and VPrP services, and imp
29、lements the APIs in the provider network ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 7 Quality of Service (QoS): collection of service levels delivered by a provider network to an enterprise network NOTE: QoS can be characterised by various performance attributes such as: packet loss, packet delay; tra
30、ffic 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 points NOTE: A SAP is typically the egress router from the ent
31、erprise 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 flows, where each aggregate is supported by the same level of QoS
32、. 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 using tunnelling and security technologies. With no QoS measu
33、res, 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 Network (VPrN): collection of VPrP delivered as a service to a si
34、ngle 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 traffic whose packets are marked with the specific DS Codepoint
35、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 201 915-1 and the following apply: CIM Common Information Model CM Connectivity Manager DiffServ Differentiated
36、 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 Virtual Provisioned Network VPrP Virtual Provisioned Pipe ETSI ETS
37、I ES 201 915-10 V1.4.1 (2003-07) 8 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 travelling through the provider network. The Connectivity Manag
38、er 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 QoS method to be used in the enterprise network, nor in the p
39、rovider 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 marked, they can enjoy the QoS service provisioned in the provider
40、 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 provisioned pipes (VPrPs) in the provider network to carry the ente
41、rprise 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 templates that are used by the operator to specify a VPrP. For
42、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 for this VPrP. Elements that can be specified for a VPrP inclu
43、de 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 example of a possible scenario: The provider prepares a templ
44、ate 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 man
45、ager after being authenticated and authorised by the Framework service. Operator gets the list of the sites 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 th
46、e enterprise (as supported by the SLA), selects one, and requests a template for constructing a new VPrP 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
47、 template could be validated, selects endpoints, load parameters and traffic flow direction, and selects 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 modifi
48、ed 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
49、(e.g. the requested service is not available at this access point, or at the specified time). If the provider approves service, the operator may send packets marked with the templates DiffServ Codepoint, which identifies together with the endpoints the VPrP that carries these packets. ETSI ETSI ES 201 915-10 V1.4.1 (2003-07) 9 Some additional clarification points: A VPrN is associated with a single network provider. A VPrP defines QoS parameters for traffic flowing through this provider network, between two s
copyright@ 2008-2019 麦多课文库（www.mydoc123.com）网站版权所有
备案/许可证编号：苏ICP备17064731号-1