Open Service Access (OSA); Application Programming Interface (API); Part 10: Connectivity Manager SCF (Parlay 4)

Maintenance update of ES 202 915-10 V1.1.1 to produce ES 202 915-10 V1.2.1 Updated document will also be known as PARLAY 4.1. Only those parts requiring modification will be updated ( most parts require maintenance fixes )

Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) – 10. del: Upravljalnik povezljivosti SCF

General Information

Status
Published
Publication Date
31-Dec-2004
Current Stage
6060 - National Implementation/Publication (Adopted Project)
Start Date
01-Jan-2005
Due Date
01-Jan-2005
Completion Date
01-Jan-2005

Buy Standard

Standardization document
ES 202 915-10 V1.2.1:2005
English language
57 pages
sale 10% off
Preview
sale 10% off
Preview
e-Library read for
1 day

Standards Content (Sample)

SLOVENSKI STANDARD
SIST ES 202 915-10 V1.2.1:2005
01-januar-2005
Odprti dostop do storitve (OSA) – Vmesnik za aplikacijsko programiranje (API) –
10. del: Upravljalnik povezljivosti SCF
Open Service Access (OSA); Application Programming Interface (API); Part 10:
Connectivity Manager SCF (Parlay 4)
Ta slovenski standard je istoveten z: ES 202 915-10 Version 1.2.1
ICS:
33.040.01 Telekomunikacijski sistemi Telecommunication systems
na splošno in general
SIST ES 202 915-10 V1.2.1:2005 en
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

---------------------- Page: 1 ----------------------

SIST ES 202 915-10 V1.2.1:2005

---------------------- Page: 2 ----------------------

SIST ES 202 915-10 V1.2.1:2005

ETSI ES 202 915-10 V1.2.1 (2003-08)
ETSI Standard


Open Service Access (OSA);
Application Programming Interface (API);
Part 10: Connectivity Manager SCF
(Parlay 4)





---------------------- Page: 3 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 2 ETSI ES 202 915-10 V1.2.1 (2003-08)



Reference
RES/SPAN-120096-10
Keywords
API, IDL, OSA, UML
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 - 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, send your comment to:
editor@etsi.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 Telecommunications Standards Institute 2003.
© The Parlay Group 2003.
All rights reserved.

TM TM TM
DECT , PLUGTESTS and UMTS are Trade Marks of ETSI registered for the benefit of its Members.
TM
TIPHON and the TIPHON logo are Trade Marks currently being registered by ETSI 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

---------------------- Page: 4 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 3 ETSI ES 202 915-10 V1.2.1 (2003-08)
Contents
Intellectual Property Rights.6
Foreword.6
1 Scope.7
2 References.7
3 Definitions and abbreviations.7
3.1 Definitions.7
3.2 Abbreviations.8
4 Connectivity Manager SCF.9
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 Sites.14
6 Class Diagrams.15
7 The Service Interface Specifications.21
7.1 Interface Specification Format .21
7.1.1 Interface Class.21
7.1.2 Method descriptions.21
7.1.3 Parameter descriptions.21
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 Service 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 Classes.23
8.1 Interface Class IpConnectivityManager .23
8.1.1 Method getQoSMenu().24
8.1.2 Method getEnterpriseNetwork().24
8.2 Interface Class IpEnterpriseNetwork.25
8.2.1 Method getSiteList().25
8.2.2 Method getVPrN().25
8.2.3 Method getSite().26
8.3 Interface Class IpEnterpriseNetworkSite .26
8.3.1 Method getSAPList().27
8.3.2 Method getSiteID().27
8.3.3 Method getSiteLocation().27
8.3.4 Method getSiteDescription().28
8.3.5 Method getIPSubnet().28
8.3.6 Method getSAPIPSubnet().28
8.4 Interface Class IpQoSMenu .29
8.4.1 Method getTemplate().29
8.4.2 Method getTemplateList().29
8.5 Interface Class IpQoSTemplate.30
8.5.1 Method getTemplateType().31
8.5.2 Method getDescription().31
8.5.3 Method setSlaID().32
8.5.4 Method getPipeQoSInfo().32
8.5.5 Method setPipeQoSInfo().32
ETSI

---------------------- Page: 5 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 4 ETSI ES 202 915-10 V1.2.1 (2003-08)
8.5.6 Method getValidityInfo().33
8.5.7 Method setValidityInfo().33
8.5.8 Method setProvisionedQoSInfo().34
8.5.9 Method getProvisionedQoSInfo().35
8.5.10 Method getDsCodepoint().35
8.6 Interface Class IpVPrN .36
8.6.1 Method getVPrPList().36
8.6.2 Method getVPrP().37
8.6.3 Method createVPrP().37
8.6.4 Method deleteVPrP().38
8.7 Interface Class IpVPrP .38
8.7.1 Method getVPrPID().39
8.7.2 Method getSlaID().39
8.7.3 Method getStatus().40
8.7.4 Method getProvisionedQoSInfo().40
8.7.5 Method getValidityInfo().41
8.7.6 Method getPipeQoSInfo().41
8.7.7 Method getDsCodepoint().41
9 State Transition Diagrams.42
10 Data Definitions.42
10.1 Connectivity Manager Data Types.43
10.1.1 TpIPSubnet.43
10.1.2 TpIPv4AddType.43
10.1.3 TpIPVersion.43
10.1.4 TpVprpStatus.43
10.1.5 TpDsCodepoint.44
10.1.6 TpProvisionedQoSInfo.44
10.1.7 TpDelayDescriptor.44
10.1.8 TpLossDescriptor.44
10.1.9 TpJitterDescriptor.44
10.1.10 TpNameDescrpTagInt.45
10.1.11 TpNameDescrpTagString.45
10.1.12 TpTagValue.45
10.1.13 TpNameDescrpTagExcessLoadAction.45
10.1.14 TpAction.46
10.1.15 TpPipeQoSInfo.46
10.1.16 TpNameDescrpTagDir.46
10.1.17 TpTrafficDirection.46
10.1.18 TpEndpoint.46
10.1.19 TpSiteOrSap.47
10.1.20 TpLoadDescriptor.47
10.1.21 TpValidityInfo.47
10.1.22 TpNameDescrpTagDateTime.47
10.1.23 TpNameDescrpTagTimePeriod.47
10.1.24 TpNameDescrpTagTimeOfDay.48
10.1.25 TpNameDescrpTagDayOfWeek.48
10.1.26 TpNameDescrpTagMonth.49
11 Exception Classes.50
Annex A (normative): OMG IDL Description of Connectivity Manager SCF.51
Annex B (informative): W3C WSDL Description of Connectivity Manager SCF.52
Annex C (informative): Record of changes .53
C.1 Interfaces.53
C.1.1 New.53
C.1.2 Deprecated.53
C.1.3 Removed.53
C.2 Methods.53
ETSI

---------------------- Page: 6 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 5 ETSI ES 202 915-10 V1.2.1 (2003-08)
C.2.1 New.53
C.2.2 Deprecated.54
C.2.3 Modified.54
C.2.4 Removed.54
C.3 Data Definitions.54
C.3.1 New.54
C.3.2 Modified.54
C.3.3 Removed.55
C.4 Service Properties.55
C.4.1 New.55
C.4.2 Deprecated.55
C.4.3 Modified.55
C.4.4 Removed.55
C.5 Exceptions.56
C.5.1 New.56
C.5.2 Modified.56
C.5.3 Removed.56
C.6 Others.56
History .57

ETSI

---------------------- Page: 7 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 6 ETSI ES 202 915-10 V1.2.1 (2003-08)
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 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 202 915) is structured in the following
parts:
Part 1: "Overview";
Part 2: "Common Data Definitions";
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: "Charging 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://www.java.sun.com/products/jain) member companies.
The present document forms part of the Parlay 4.1 set of specifications.
ETSI

---------------------- Page: 8 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 7 ETSI ES 202 915-10 V1.2.1 (2003-08)
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 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, 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 the
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: Overview
(Parlay 4)".
ETSI ES 202 915-2: "Open Service Access (OSA); Application Programming Interface (API); Part 2: Common Data
Definitions (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
differentiated 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 the enterprise network/user of APIs
NOTE: Also referred to as operator.
operator: enterprise operator
ETSI

---------------------- Page: 9 ----------------------

SIST ES 202 915-10 V1.2.1:2005
 8 ETSI ES 202 915-10 V1.2.1 (2003-08)
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.
provider: entity that offers the VPN and VPrP services, and implements the APIs in the provider network
Quality of Service: 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; traffic
policing measures such as maximum bandwidth and burst rate for traffic entering the providers' network.
Service Access Point: 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 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 flows, where each aggregate is supported by the same level of
QoS.
Virtual Private Network: 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 measures, VPN passes all packets among the sites with a best
effort approach.
Virtual Leased Line: network that uses a provider network infrastructure to connect two geographically separated sites
of an enterprise
Virtual Provisioned Network: collection of VPrP delivered as a service to a single enterprise network
Virtual Provisioned Pipe: 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 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 Information Model
CM Connect
...

Questions, Comments and Discussion

Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.