OBJECT-ORIENTED METHOD ANDARCHITECTURE FOR VIRTUAL PRIVATE NETWORK by jlhd32

VIEWS: 25 PAGES: 14

More Info
									   OBJECT-ORIENTED METHOD ANDARCHITECTURE
FOR VIRTUAL PRIVATE NETWORK SERVICE MANAGEMENT




                        THÈSE No 1446 (1995)

           PRÉSENTÉEÀ LA SECTION DE SYSTÈMESDE COMMUNICATION



        ÉCOLE POLYTECHNIQUE FÉDÉRALE DE LAUSANNE

        POUR L'OBTENTION DU GRADE DE DOCTEUR Ès SCIENCES TECHNIQUES




                                       PAR


                        Jean-Paul GASPOZ
                         Ingénieur électricien diplômé EPF
                            originaire de St-Martin (VS)




                         acceptée sur proposition du jury:

                       Prof. J.-P. Hubaux, directeur de thèse
                                B. Liver, corapporteur
                         Prof. C. Petitpiene, corapporteur
                          Prof. T. Saydam, corapporteur




                                 Lausanne, EPFL
                                       1996
                                  ABSTRACT
One of the major trends in the evolution of current corporate networking is an increasing need
for high performance long distance communications. Provided as an aitemative to leased lines
networks, virtuai private networks (VPNs) are gaining increasing acceptance among customers
and network providers by providing corporate networking between geographically dispersed
customer premises based on a shared public switched network infrastructure.

As a contribution towards this evolution, the present thesis proposes a generic object-oriented
architecture for open distributed VPN services integrating service and management issues al   l
dong the modeling process. The aim of this VPN architecture is not only to provide a
descriptive model of VPNs but aiso to illustrate possible ways of operating on that model to
solve VPN related service or management issues. The architecture proposed is generic in the
sense that, firstly, it is network technology independent and, secondly, that it captures the
fundamental charactenstics common to ail VPNs. This latter aspect is very important as, due to
the lack of standardization in this area, current VPNs are more marketable products than well-
defined telecommunications services.

The notion of distribution is aiso very important as telecommunications systerns in generai, and
VPNs in particular, are intrinsicaily distributed. Indeed, a VPN can be seen as a distributed
application mnning on the multiple nodes of telecommunications networks. To effectively deal
with this de facto distribution and to exploit at best the benefits it can provide the VPN service
and management services have been conceived from the very beginning as distributed
applications. For this purpose, and due to the lack of satisfactory existing solutions in this area,
an object-oriented method for the specification and design of open distributed
telecommunications and management services has been developed. The proposed method
combines the ODP (Open Distributecl Processing) concepts and stmcturing rules with the
systematic development process advocated by an object-onented software engineering method
cailed Fusion. This method provides an architectural framework and a seamless thread from
problem defuiition to the realization of the distributed telecommunications system, based on
hierarchically related abstraction levels. Mapping rules, guidelines and notations are proposed
on how and when enterprise, information and computational models should be built, in
particular based on models performed at a higher abstraction level.

The method has then been applied to the specification of the generic VPN architecture itself. In
the enterprise viewpoint the scope of the VPN service has been refmed and lirnited to the
provision, within the public domain boundary, of internetworking services between customer
premises networks. The m i actors involved in using, providing and managing the VPN
                            an
service have been descnbed as well as interactions between them. Based on their requirements,
fundamentai VPN characteristics have been identified, among which the notions of virtud
resource and of closed user group are the most relevant. In the information viewpoint, a generic
object-oriented network information model has been developed based on standard network
resources. This model has been recursively applied to specify the object models pertaining to
the different layers of the VPN architecture. Based on this architecture, a management service
allowing customers to dynamicaily configure the logicai comectivity of their VPN has been
specified down to the network elements level. The realization of this functionality in terms of
application components suitable for distribution and interactions between them has been the
purpose of the computational viewpoint.

Finally, the generic VPN architecture has been refined and applied to the particular context of
ATM-based VPNs. In addition to describing how VPNs can be built on ATM networks tius
case study addresses a very important issue in such an environment, narnely bandwidth
management. In this respect, an open distributed VPN bandwidth management service has been
specified that aliows VPN customers to dynamically modify the bandwidth ailocated to the
virtual path connections connecting the different sites of their organization. The final outcome
of this specification process is the definition of a computational architecture for VPN bandwidth
management extending from VPN level down to the physical network elements.

This work has been canied out in the frame of the RACE (Research and Development in
Advanced Communications Technologies in Europe) project R2041 PRISM (Pan-European
Reference Configuration for IBC Services Management).
                                  RESUME
Une des principales tendances dans l'évolution actuelle des réseaux d'entreprise est un
besoin croissant pour des communications à longue distance performantes. Créés comme
une alternative aux réseaux privés à base de lignes louées, les réseaux privés virtuels
(Virtual Private Network - VPN) connaissent un succès croissant auprès des opérateurs et
des compagnies disposant d'un réseau d'entreprise car ils permettent d'interconnecter les
différents sites d'une même société en utilisant uniquement l'infrastructure publique
commutée.

Dans le but de contribuer à cette évolution, ce travail de thèse propose une architecture de
réseau privé virtuel orientée-objet et générique, intégrant les aspects service et gestion de
ces services tout au long du processus de modélisation. Cette architecture vise non
seulement à fournir un modèle descriptif de réseau privé virtuel mais également à montrer
comment opérer sur ce modèle pour gérer le service VPN. L'architecture proposée est
générique car, d'une part, elle est indépendante d'une technologie réseau particulière et,
d'autre part, elle couvre les caractéristiques fondamentales communes à tout service VPN.
Ce dernier aspect est d'ailleurs très important car, en raison d'un manque de standardisation
dans le domaine, les réseaux privés virtuels actuels sont d'avantage des produits
commerciaux que des services de télécommunication bien définis.

La notion & distribution est également très importante car les systèmes de
télécommunications en général et les réseaux privés virtuels en particulier sont
intrinsèquement distribués. En effet, un VPN peut être considéré comme une application
distribuée s'exécutant sur les différents noeuds d'un réseau de télécommunications. A h de
prendre en compte au mieux cette distribution de fait et d'en exploiter les bénéfices, le
service VPN, ainsi que les services de gestion qui lui sont associés, ont été spécifiés et
conçus comme des applications distribuées. A cet effet, et vu le manque de solutions
satisfaisantes dans le domaine, une méthode orientée-objet pour la spécification et la
conception de services de télécommunications et de gestion a été développée dans le cadre
de cette thèse. La méthode proposée combine les concepts et les règles de structuration des
systèmes répartis ouverts (Open Distributed Processing - ODP) et l'approche systématique
définie dans le cadre de la méthode de génie logiciel orientée-objet appelée Fusion. La
méthode développée founiit un cadre architectural ainsi qu'un fil conducteur de la définition
du problème à la réalisation du système de télécommunications distribué. Des lignes
directrices, des règles de correspondance ainsi que des notations ont été proposées afin de
faciliter le développement des points de vue d'entreprise, d'information et de calcul du
modèle de référence ODP.

La méthode a ensuite été appliquée à la spécification de l'architecture générique de réseau
privé virtuel elle-même. Dans le cadre du modèle d'entreprise, le service VPN a été défini
plus précisément comme un service permettant l'interconnexion de réseaux privés locaux
mais construit sur des ressources publiques uniquement. Les différents acteurs intéressés à
utiliser, founiir ou souscrire à un service VPN ont été identifiés. Sur la base de leurs
attentes envers le service, les caractéristiquesfondamentales communes à tout service VPN
ont été isolées, parmi lesquelles les notions de ressources virtuelles et de groupe fermé
d'usager sont les plus significatives. Le principal objet du point de vue d'information a été
le développement d'un modèle informationnel de réseau, orienté-objet et générique.
L'application récursive de ce modèle à différents niveaux d'abstraction a permis
l'élaboration d'une architecture informationnelle de réseau privé virtuel. Sur la base de cette
architecture, un service de gestion permettant aux clients du service VPN de configurer
dynamiquement la connectivité de leur réseau privé virtuel a été spécifié à tous les niveaux
de l'architecture. La réalisation de ce service de gestion en termes de composants applicatifs
susceptibles d'être distribués et conçus comme tel, et d'interaction entre ces derniers, a
constitué l'objectif principal du point de vue de calcul.

Finalement, l'architecture générique de réseau privé virtuel a été appliquée au contexte
particulier des réseaux privés virtuels construits sur une infrastructure ATM (Mode de
Tranfert Asynchrone - Asynchronous Transfer Mode). Dans un premier temps, différentes
manières de construire un réseau privé virtuel sur ATM ont été proposées. Dans un
deuxième temps, un aspect très important, inhérent à une telle infrastructure, a été considéré
à savoir la gestion de la largeur de bande. A cet égards, une application distribuée
permettant de gérer la largeur de bande dans un contexte VPN a été conçue. Le service de
gestion offert par cette application permet aux clients du service VPN de modifier
dynamiquement la largeur de bande ailouée aux chemins virtuels (Virtual Path) connectant
les différents sites de leur organisation. Au terme de cette étude, une architecture de gestion
de la largeur de bande pour réseaux privés virtuels a pu être proposée.

Ce travail a été réalisé dans le cadre du projet de recherche européen pour des technologies
de communications avancées (Research and Development in Advanced Communications
Technologies in Europe - RACE) numéro R2041 et intitulé 'configuration de référence pour
la gestion de services dans un contexte de communications intégrées à large bande (Pan-
European Reference Configurationfor IBC Services Management - PRISM).
1 INTRODUCTION                                                                                                                        1


  1.1 MOTIVATIONS ......................................................................................................... 1
  1.2 VIRTUAL PRIVATE     NETWORKS DISTRIBUTEDAS                           APPLICATIONS              .......................2
  1.3 BROADBAND  VPNS.................................................................................................      3
  1.4 STRUCTURE OF THE DOCUMENT                 ............................................................................3
2 SCOPE AND OBJECTIVES                                                                                                                5


  2.1 PROBLEM
            STATEMENT           ............................................................................................5
  2.2 OBJECTIVES............................................................................................................6
  2.3 TECHNICALAPPROACH           ..........................................................................................6
  2.4 RELATED WOR K .....................................................................................................
                     .                                                                                                      7
     2.4.1 ~ O D O L O G I C A L     .................................................................................7
                               ASPECTS
         2.4.1.1 PRISM..................................................................................................... 7
         2.4.1.2 TTNA-C ...................................................................................................... 9
     2.4.2 VPN MODELING     ............................................................................... 1 1
                      ASPECTS
         2.4.2.1 PREPARE Approach to VPN Modeling .................................................... 1 1


3 NETWORKING CONCEPTS                                                                                                               13


  3.1 TMN       ...................................................................................................................... 13
                     ................................................................................................
      3.1.1 INTRODUC~ON                                                                                                           1 3
      3.1.2 PRINCIPLES A TEUKOMMUNICA~ONS
                     FOR              MANAGEMENT     ...................... 1 3
                                               NEIWORK
         3.1.2.1 TMN Functional Architecture................................................................. 1 4
         3.1.2.2 TMN Information Architecture................................................................. 15
         3.1.2.3 TMN Physical Architecture..................................................................... 1 7


Table of Contents                                                                                                                         i
Object-Oriented Method and Architecturefor VPN Service Management


       3.1.3 (JTHER TMN STANDARDS .................................................................................. 18
     3.2 VIRTUAL PRIVATE
                       NETWORKS: STATE OF THE ART                                        .....................................19
       3.2.1 I.ODUCïiûN ..................................................................................................19
       3.2.2 BRIEFHISTORY VPNs ...................................................................................19
                        OF

                         ~ THE          ........................................................... 2 O
       3.2.3 C H A R A ~ OFC SVPN SERVICE
                    ARGUMENTS VPNS......................................................................2 1
       3.2.4 BUSINESS      FOR

           3.2.4.1 Customer Point of View ............................................................................             21
          3.2.4.2 Network Provider Point of View ................................................................22
                             ....................................................................................2 2
       3.2.5 VPN STANDARDIZATION


4 MODELING BACKGROUND                                                                                                              25


     4.1 PRINCIPLES OF OBJECT-ORIENTED MODELING                                    .................................................
                                                                                                                                   25
                            AND ?kpES......................................................................... 5
       4.1.1 OBJECrS. CLASSES                                                                                2
       4.1.2 Ass'ïk4CI'ïo~             ..................................................................2 6
                          AND ENCAPSULA~ON

       4.1.3 BEHAVIOR STATE
                    AND    ........................................................................................2 6
                                            .......................................................26
       4.1.4 ~NHERITANCE,SUBQSSSING SUBTYPING
                                  AM)

                         mo~           ...................................................................2 7
       4.1.5 C o ~ ~ o s AND DECOMPOSITION
     4.2 FUSION      ..................................................................................................................
                                                                                                                                      27
                       .............................................................................................2 8
                   PHASE
       4.2.1 ANALYSIS
          4.2.1.1 Object Mode1............................................................................................28
          4.2.1.2 Interface Mode1.......................................................................................2 8
       4.2.2 DESIGN   ..................................................................................................
                  PHASE                                                                                                           29
                               ....................................................................................2 9
       4.2.3 IMPLEMENTATIONPHASE
       4.2.4 LWKING THE MODELS ........................................................................................29
          4.2.4.1 Object Mode1 - Life-cycle Mode1.............................................................. 30
          4.2.4.2 Object Mode1 - Operation Mode1..............................................................30
          4.2.4.3 Life-cycle Mode1 - Operation Mode1 .......................................................- 3O
          4.2.4.4 Operation Mode1 - Object Interaction Graphs ........................................... 3 1
     4.3 OPENDISTRIBUTED PROCESSING                           ....................................................................... 1
                                                                                                                                    3
       4.3.1 blTRODUCI'ION .................................................................................................. 1
                                                                                                                            3
       4.3.2 E ~ R I S E V E W P O .....................................................................................32
                                        INT
       4.3.3 INFORMATION  VIEWPOINT .................................................................................3 2
       4.3.4 COMPUTATIONAL w r .............................................................................3 2
                              V m
                       V      .................................................................................. 3 3
       4.3.5 ENGINEERING ~ I N T


ii                                                                                                              Table of Contents
                                        Object-OrientedMetbd and Architecture for VPN Service Management




5 METHODOLOGY                                                                                                                  35


  5.1 INTRODUCTION  .....................................................................................................35
  5.2 MOTIVATIONS .......................................................................................................36
  5.3 FUSION PHASES WITH RESPECT ODP VIEWPOINTS ......................................
                                               TO                                                                        38
      5.3.1 COMPAIUSON SIMILAR
                     WITH          ................................................................ 3 9
                             MAPPING
  5.4 PROPOSED
             METHOD                  ..............................................................................................
                                                                                                                                  40
                             .................................................................................. 4 3
      5.4.1 E ~ R I SVIEWPOINT
                      E
         5.4.1 .1 Introduction .............................................................................................43
         5.4.1.2 Scope and Objectives ................................................................................         44
         5.4.1.3 Requirements............................................................................................
                                                                                                                        44
         5.4.1.4 Organizational Mode1............................................................................... 45
         5.4.1.5 Policies .................................................................................................... 4 5
            5.4.1.5.1 Refmement of the Policy Concept..................................................... -46
            5.4.1.5.2 Policy Specification Template...................................................... 4                       7
         5.4.1.6 Life-cycle Mode1......................................................................................         48
      5.4.2 N'FORMATION       ................................................................................. 4 9
                      VIEWPOINT
         5.4.2.1 Object Mode1............................................................................................       49
             5.4.2.1.1 Relationship Modeling .......................................................................50
             5.4.2.1.2 Graphical Object Mode1 Notation ...................................................... 51
         5.4.2.2 Operation Mode1 ..................................................................................... 3
                                                                                                                     5
             5.4.2.2.1 Extensions to Fusion's Operation Mode1 Notations............................ 53
         5.4.2.3 Relationships with ODP Schemata ............................................................. 55
             5.4.2.3.1 Static Schema .................................................................................... 55
             5.4.2.3.2 Invariant Schema .......................................................................... 5              6
             5.4.2.3.3 Dynamic Schema ....................................................................... 5                   7
             5.4.2.3.4 Conclusion ..................................................................................            57
         5.4.2.4 Forma1 Notation .......................................................................................        57
          5.4.2.5 Behavior of Individual Information Objects ........................................59
          5.4.2.6 Alternative Notations ............................................................................... 6 2
             5.4.2.6.1 GDMO 1 GRM ................................................................................              62


..
 ..              -



Table of Contents
Object-OrientedMethod and Architecturefor VPN Service Management


              5.4.2.6.2 FUS".................................................................................................63
             5.4.2.6.3 Formal Description Techniques ........................................................ 6 3
       5.4.3 COMPUTA~ONAL     VDWPOINT         .............................................................................6 4
          5.4.3.1 Introduction .............................................................................................64
          5.4.3.2 Computational Concepts .........................................................................                 6 4
              5.4.3.2.1 Objects and Interfaces........................................................................ 64
              5.4.3.2.2 Binding and Trading .........................................................................65
          5.4.3.3 Computational Specification .................................................................... 5
                                                                                                                 6
              5.4.3.3.1 Reusing Information Specification.................................................... 6 5
              5.4.3.3.2 Computational Object Interaction Graphs ..........................................67
              5.4.3.3.3 Computational Object Type Diagrams .............................................. 6 7
              5.4.3.3.4 Notations for Computational Object Types ........................................68
          5.4.3.4 Overall Computational Modeling Process.................................................
                                                                                                        -69
      5.4.4   ENGINEERING ........................................................................................7 0
                       ISSUES
     5.5 CONCLUSION         .........................................................................................................
                                                                                                                                    72


6 GENERIC VPN MODEL                                                                                                                    75


     6.1 ENTERPRISEVIEWPOINT                  ......................................................................................   75
      6.1.1 PURPOSEOF A G m c VPN MODEL.................................................................7 5
                            .....................................................................................7 5
      6.1.2 VPN TERMs ANALYSIS
      6.1.3 VPN SCOPE......................................................................................................76
          6.1.3.1 CTN Definition........................................................................................               76
          6.1.3.2 VPN Definition in a             CTN Context............................................................. 77
          6.1.3.3 Scope of the Generic VPN ....................................................................... 7 7
          6.1.3.4 Possible CTN Configurations and Outsourcing .........................................78
      6.1.4 ORGANIZATIONAL  ..................................................................................
                        MODEL                                                                                                          8 1
          6.1.4.1 Actors and Interactions .............................................................................8 1
          6.1.4.2 Actors and Roles......................................................................................-83
                          ....................................................................................83
      6.1.5 GEN~~CREQVIREMENT~
          6.1.5.1 Customers Requirements..........................................................................                     85
              6.1.5.1.1 Functional Requirements .................................................................. 5
                                                                                                                 8
              6.1.5.1.2 Non-functional Requirements ..........................................................8 5
              6.1.5.1.3 Management Requirements ................................................................85
              6.1.5.1.4 Security Requirements ......................................................................8 6


iv                                                                                                                Table of Contents
                                        Object-OrientedMethod and Architecture for VPN Service Management


           6.1.5.1.5 QoS Requirements ...........................................................................8 6
           6.1.5.1.6 Billing Requirements ....................................................................... 8
                                                                                                                8
       6.1.5.2 VASP Requirements ................................................................................. 88
       6.1 .5.3 Network Provider Requirements................................................................ 89
    6.1.6 GENERIC            .............................................................................. 9 0
                CHARACTERISTICS
                                 ............................................................... 9 4
                         MANAGEMENT
    6.1.7 VPN CONFIGURATION
       6.1.7.1 Ovewiew ...................................................................................................    94
       6.1.7.2 Organizational Mode1......................................................................... 9                   4
       6.1.7.3 Policies ..................................................................................................... 95
       6.1.7.4 Life-cycle Mode1...................................................................................... 96
 6.2 LNFORMATIONVIEWPOINT                      ...................................................................................
                                                                                                                                 97
                 ........................................................................................................
    6.2.1 OVERVIEW                                                                                                             97
                            ............................................................................................ 98
                       LEVELS
    6.2.2 V I S I B I L ~
    6.2.3 RELATED INFORMATION    ........................................................................ 9 8
                            MODELS
       6.2.3.1 Prelirninary Work .................................................................................... 9 8
       6.2.3.2 Related Standards ..................................................................................... 99
           6.2.3.2.1 M.3100 .............................................................................................      99
           6.2.3.2.2 G.803 ................................................................................................ 99
    6.2.4 GENERIC
                INFORMATION                   ....................................................................           10 1
    6.2.5 G m c NEIWORK       INFORMATION .........................................................
                                             MODEL                                                                           102
       6.2.5.1 Topology Fragment ................................................................................            104
        6.2.5.2 Connectivity Fragment......................................................................... 1              0 5
        6.2.5.3 Object-oriented Modeling of the Layering Principle ...............................                           106
        6.2.5.4 inheritance Hierarchy of the Generic Mode1...........................................107
    6.2.6 VPN ~NFORMATIONARC HI TE^ .................................................................. 107
        6.2.6.1 Service Level Object Mode1 ....................................................................109
        6.2.6.2 CTN Level Object Mode1........................................................................ 111
        6.2.6.3 VPN Level Object Mode1.......................................................................                 112
        6.2.6.4 Public Network Level Object Mode1........................................................113
        6.2.6.5 Switching Element Level Object Mode1.................................................. 114
        6.2.6.6 Inheritance Hierarchy of the Overall VPN Information Architecture ....... 115
                     ~WENTANCE.............................................................................116
     6.2.7 RELATIONSHIP
     6.2.8 MODEL                   .......................................................... 118
               ASSESSMENT APPLICABIL~
                        AND

     6.2.9 OPERATION   ..........................................................................................
                   MODEL                                                                                                      121

-



Table o Contents
       f
Object-Oriented Method and Architecture for VPN Service Management


     6.3 VPN CONFIGURATION
                         MANAGEMENT
                                  SUB-SYSTEMS
                                            SPECIFICATION                                                              ............123
       6.3.1 ENTERF~ISE     ..................................................................................
                    VIEWPOINT                                                                                                    1 23
          6.3.1.1 Organizational Mode1............................................................................. 123
          6.3.1.2 Policies ...................................................................................................   125
          6.3.1.3 Life-cycle Mode1...................................................................................1 2 5
       6.3.2 INFORMATION ~ I N ................................................................................
                        V         T                                                                                              127
          6.3.2.1 Object Mode1..........................................................................................         127
          6.3.2.2 Operation Mode1 .................................................................................... 128
             6.3.2.2.1 Route Selection................................................................................           129
             6.3.2.2.2 QoS Parameters Cascading............................................................... 129
             6.3.2.2.3 Route Segments Sequencing ............................................................ 130
             6.3.2.2.4 Identification of Objects Representing the Same Comection............130
          6.3.2.3 Forma1 Information Specification........................................................... 130
       6.3.3 COMPUTA~ONAL
                       VDWFOINT............................................................................131
     6.4 COMPUTATIONAL
                    VIEWPOINT                           ............................................................................136
      6.4.1 COMPV~A~ONALAR-      ......................................................................136
                           MANAGEMENT A TMN AC
      6.4.2 VPN CONFIGURATION          IN              R-                     ......................... 137
     6.5 CONCLUSION          .......................................................................................................138
7 OPEN DISTRIBUTED BANDWIDTH MANAGEMENT SERVICE FOR ATM-
BASED VPNS                                                                                                                       141


     7.1 ATM-BASED
                 VPNS                  .............................................................................................141
      7.1.1 INTRODUCTION................................................................................................ 141
      7.1.2 PHYSICAL
                  ARCHITE=                                        VPNS............................................. 142
                                                    FOR A'ï"M-BASED

                                               VPNS ............................................. 144
      7.1.3 LAYERED ARCHl'IEClWU2 FOR A'ïM-BASED
     7.2 ENTERPRISE VIEWPOINT                   ....................................................................................145
      7.2.1 SYSTD~
                 SCOPE O-
                     AND B                      ....................................................................... 146
         7.2.1.1 System Environment...............................................................................146
         7.2.1.2 Requirements.........................................................................................1 46
         7.2.1.3 Purpose and Scope of the System ...........................................................147
      7.2.2 ORGANIZATIONAL .................................................................................147
                             MODEL
      7.2.3 POLICIES.........................................................................................................148
      7.2.4 LIFE-CYCLE   .........................................................................................149
                     MODEL
     7.3 INFORMATION VIEWPOINT                     ........................................................................... 150
vi                                                                                                               Table of Contents
                                        Object-Otiented Method and Architecturefor VPN Service Manugernent


     7.3.1 INFORMATION
                    A-
                     R                                           BVPNS ....................................150
                                                     FOR ATM-BASED
                    ...............................................................................................
     7.3.2 OBJEC~MODEL                                                                                                      151
                     .......................................................................................... 152
     7.3.3 OPERA~ONMODEL
  7.4 BVPN BANDWIDTH MANAGEMENT
                             SUB-SYSTEMS SPECIFICATION                                                     .................153
     7.4.1 ENTERPRISE      ................................................................................... 153
                   VIEWPOINT
        7.4.1 .1 Organizational Mode1........................................................................... 153
        7.4.1.2 Policies ................................................................................................... 154
        7.4.1.3 Life-cycle Mode1.................................................................................... 154
                             ............................................................................... 157
     7.4.2 INFORMATIONVIEWP~INT
        7.4.2.1 Object Mode1.......................................................................................... 157
        7.4.2.2 Operation Mode1 ....................................................................................        158
     7.4.3 COMPUTA~ONAL I N ............................................................................ 159
                    V ~        T
  7.5 COMPUTATIONAL
                 VIEWPOINT               ............................................................................161
              .......................................................................................................163
  7.6 CONCLUSION


8 CONCLUSIONS                                                                                                               165


  8.1 VPN MODELING             ..................................................................................................
                                                                                                                                165
     8.1.1 AREASOFFURTHER ............................................................................. 166
                       WORK
  8.2 METHODOLOGICAL K.
                  WOR                          .................................................................................
                                                                                                                               167
                          ...............................................................................168
     8.2.1 AREASOFFURTHERWORK


9 BIBLIOGRAPHY                                                                                                              169



10 ABBREVIATIONS                                                                                                            175



APPENDM A ASN.l TEMPLATES                                                                                                   A -1


  A.l OBJECTCLASSTEMPLATE                       ................................................................................A- 1
  A.2 ATTRIBUTE TEMPLAT
                      E
                      .   ..................................................A- 1
  A.3 RELATIONSHIP
                 TEMPLATE      ................................................................................A.1
  A.4 ACTION       ............................................................................................A-2
            TEMPLATE
  A S SUPPORTING
               DEFINITIONS     ................................................................................ 3
                                                                                                               -


Table of Contents                                                                                                             vii
Object-OrientedMethod and Architecture for VPN Service Management


APPENDIX B TYPES DEFINITIONS                                                                                                     B-1



APPENDM C MODELS FOR VPN CONFIGURATION MANAGEMENT                                                                                C-1


   C.1 LIFE-CYCLE
                MODELS                    .........................................................................................
                                                                                                                                  C-1
       C.1.1 LIFE-CYCLE
                      MODEL THE 'VPL-CGMSS' Sm-SYSTEM
                          FOR                              .................................C- 1
       C.1.2 LIFE-CYCLE MODEL FOR THE 'SUBNW-CXMSS'Sm-SYSl'EM............................C-2
       C.1.3 LIFE-CYCLE MODEL THE 'SWELT-CXMSS'Sm-SYSTEM
                              FOR                              .............................C-2
   C.2 OPERATION
               SCHEMATA                       .....................................................................................
                                                                                                                                  C-3
       c.2.1 OPERATION SCHFMATA FOR THE 'VPL-CGMSS' Sm-SYSTEM............................. c - 3
       C.2.2 OPERATION
                     SCHEMATA THE 'SUBNW-CXMSS'SUB-SYSIEM
                            FOR                          .......................C-5
       C.2.3 OPERATION SCHEMATA FOR THE 'SWELT-CXMSS' SUB-SYSTEM ........................ - 8
                                                                                        c
   C.3 COMPUTATIONAL
                  MODELS                           ................................................................................C-9
                                    (VPLM) ...................................................... c - 9
                   FWVATE LINEMANAGER
       C.3.1 VIRTUAL
         C.3.1.1 Computationd Object interaction Graph (COIG) for the 'rese~eVPL'
         Operation ...........................................................................................................   C-9
         C.3.1.2 COIG for the 'removeVPL' operation..................................................C- 10
         C.3.1.3 Computational Object Type Diagram for the VPLM.............................C-10
       C.3.2 Sm-NEIWORKO N CO
                      C N EI N                         MANAGER S N 0............................................C- 11
                                                             (
         C.3.2.1 COIG for the 'setupSNC' Operation ....................................................C- 11
         C.3.2.2 COIG for the 'releaseSNC' Operation .................................................. C- 12
         C.3.2.3 Computationd Object Type Diagram for the SNCM............................. C-12
                     ELD~ENTN EI N
       C.3.3 SWITCHING      O O
                           C NC                                       (SECM) ....................................C- 13
                                                                MANAGER
         C.3.3.1 COIG for the 'setupSNC' Operation ...................................................C-13
         C.3.3.2 COIG for the 'releaseSNC' Operation ..................................................C-13
         C.3.3.3 Computational Object Type Diagram for the SECM ............................. C- 14


APPENDM D MODELS FOR VPN BANDWIDTH MANAGEMENT                                                                                    D-1


   D.l LIFE-CYCLE
                MODELS                    .........................................................................................D-1
       D.1.1 Lm-CYCLE                             ...................................D- 1
                    MODEL THE ‘VPL-BMSS' SUB-SYSTEM
                        FOR

       D.1.2 Lm-CYCLE MODEL THE 'VPATH-BMSS'Sm-SYSTEM
                          FOR                                                            ...............................D-2
       D.1.3 Lm-CYCLE MODEL THE 'VPCC-BMSS'
                          FOR                                                           ................................D-2
                                                                               SUB.SYSTEM
   D.2 OPERATION
               SCHEMATA                       .....................................................................................
                                                                                                                                  D.3


viii                                                                                                            Table of Contents
                                        Object-Oriented Method and Architecture for VPN Service Management


                                                         ..............................D-3
     D.2.1 OPERATIONSCHEMATA FOR THE 'VPL-BMSS' SUB-SYSTEM
     D.2.2 OPERATION                                   .......................... D-4
                    SCHEMATA THE 'VPATH-BMSS'SUB-SYS'IEM
                           FOR

     D.2.3 OPERATIONSCHEMATA FOR THE 'VPCC-BMSS' SUB-SYSTEM ........................... D-5
  D.3 COMPUTATIONAL
                 MODELS                         ................................................................................D-7
     D.3.1 VIRTUAL      LINE
                  PRIVATE BANDWIDTH    (VLBM) ................................... D-7
                                 MANAGER
        D.3.1.1 Computational Object Interaction Graph (COIG) for the 'incVplBw'
        Operation ........................................................................................................... D-7
        D.3.1.2 COIG for the 'decVplBw' operation ......................................................D-7
        D.3.1.3 Computational Object Type Diagram for the VLBM .............................. D-7
     D.3.2 VIRTUAL
                 PATHBAND=                               (VPBM) ................................................ D- 8
                                                   MANAGER
        D.3.2.1 COIG for the 'incBwReq' Operation...................................................... D-8
        D.3.2.2 COIG for the 'decBwReq' Operation ..................................................... D-9
        D.3.2.3 COIG for the 'discardBwInc' Operation ................................................ D-9
        D.3.2.4 Computational Object Type Diagram for the VPBM ............................D- 10
                 PATH
     D.3.3 VIRTUAL                                  (CCBM)................ D- 10
                                              MANAGER
                     CROSS-CONNECIION BANDWIDTH
        D.3.3.1 COIG for the 'incBwReq' Operation.................................................... D- 10
        D.3.3.2 COIG for the 'decBwReq' Operation ................................................... D- 11
        D.3.3.3 COIG for the 'discarcBwInc' Operation............................................... D- 1
        D.3.3.4 Computational Object Type Diagram for the CCBM ............................ D-11


APPENDM E OVERVIEW OF PRISM                                                                                                  E-1


  E.l THEPRISM CONSORTIUM             ................................................................................. E-2
  E.2 PROJECT OBJECTIVES        .......................................................................................E-2
  E.3 TECHNICALAPPROACH           .....................................................................................E-2
  E.4 DOCUMENTS ....................................................................................................... E-3




Table of Contents                                                                                                              ix

								
To top