148 pages
English

Networking and internetworking 2

-

Obtenez un accès à la bibliothèque pour le consulter en ligne
En savoir plus

Description

Information technology and telecommunications

Sujets

Informations

Publié par
Nombre de lectures 8
Langue English
Poids de l'ouvrage 3 Mo

mm
RACE
COMMON
FUNCTIONAL
SPECIFICATIONS
Document 3.
Networking
and internetworking 2
CFS
D120-D530
ISSUE A
DECEMBER 1990 Commission of the European Communities
information technologies
and sciences
RACE COMMON FUNCTIONAL
SPECIFICATIONS
Document 3
Networking and internetworking 2
Commission of the European Communities
RACE Consensus Management
RACE Industrial Consortium
61 rue de Trêves
B-1040 Brussels
Project No R1045
Directorate-General
Telecommunications, Information Industries and lnïtov|tic&:RCP UUk
N.CpUR 13846/3 EN 1991 Published by the
COMMISSION OF THE EUROPEAN COMMUNITIES
Directorate-General
Telecommunications, Information Industries and Innovation
L-2920 Luxembourg
LEGAL NOTICE
Neither the Commission of the European Communities nor any person acting on
behalf of the Commission is responsible for the use which might be made of the following information
ISBN 92-826-3030-7 (Volumes 1-8)
Cataloguing data can be found at the end of this publication
Luxembourg: Office for Official Publications of the European Communities, 1991
ISBN 92-826-3008-0 Catalogue number: CD-NC-13846-EN-C
© ECSC-EEC-EAEC, Brussels • Luxembourg, 1991
Printed in Germany IBC Common Functional Specification Issue A
RACE COMMON FUNCTIONAL SPECIFICATIONS
ISSUE A DECEMBER 1990
DOCUMENT 3
NETWORKING AND INTERNETWORKING 2
Reference Configurations, Quality of Service, Signalling.
PREEFACE
The Common Functional Specifications (CFS) are to be the concise, coherent and
customized framework of the synthesis results of RACE Part I : IBC Developments and
Implementations Strategies.
This is the first issue of the RACE CFS. They are not yet complete nor are they
rigorous in their treatment of the various issues. They have been prepared by the system
sections of the RACE Projects via their participation in the RACE STG (Sub Technical Groups).
The specifications represent the first attempt by many participants in RACE at preparing
CFS. In some instances they have been prepared by a single project and are written as project
reports. Such CFS have been included as written because of the lack of opportunity to do
otherwise. It must be recognised however that they are the only set of documents describing the
system level output from the RACE programme and entering the public domain.
The work of enhancing the CFS, extending them, reconciling inconsistencies, improving
the presentation, etc. are ongoing tasks for the technical groups of RACE. They will continue
meeting throughout 1991 and 1992 with the above objectives. At the same time they will be
selecting appropriate parts of their work for contribution to the standardisation bodies of Europe
(ETSI, CEN/CENELEC, etc.) to assist in their work and to bring the results of the RACE
Programme to the attention of the other actors in the telecommunications sector of Europe.
Copyright (c) 1991 RIC Association Internationale
December 1990 Document 3 IBC Common Functional Specification Issue A
RACE
RACE (Research and Development in Advanced Communications Technologies in
Europe) is a Community Programme to prepare for the 'Introduction of Integrated Broadband
Communication (IBC) taking into account the evolving ISDN and national introduction strategies,
progressing to community-wide services by 1995'.
RACE covers major aspects of terrestrial networks, satellites and mobile
telecommunications, including considerations on narrowband and broadband networks as well as
distribution networks. RACE is also concerned with telecommunications services, their
definition and exploitation by end-users.
Document 3 December 1990 IBC Common Functional Specification Issue A
CONTENT LIST FOR ALL DOCUMENTS
Document 1 - General Aspects of IBC and IBC Services
B210 The Concept of IBC and its Relationship to ISDN
B220 Reference Models of IBC
B311 Methods for the Characteristics of the Operational Requirements of IBC
B410 Protocol Conformance Testing
C110s for the Specification of IBC Services
C301 Description of an IBC Service : Video-telephony
C302 General Purpose Multi-media Bearer
C303 Connectionless Bearer Service Description/Stage-1
C304n of aa Conference Service
Document 2 - Networking and Internetworking 1
- FRM
DUO IBC Functional Reference Model (IBC FRM)
Document 3 - Networking and Internetworking 2
- Reference Configurations
- Quality of Service
- Signalling
D120 Specification of Overall B-ISDN Connection Types
D200 Methods for Specifying a Reference Configuration
D210 IBC Reference Configurations
D410 Signalling Protocols
DS10 General Aspects of Quality of Service and Network Performance in IBC
D530 Network Performance Objectives
Document 4 - Networking and Internetworking 3
- Subsystems
D710 Switching Systems
D720 Principles for the Introduction of Intelligent Network Subsystems
D730 Mobile Network Subsystems
D740 Optical Transmission Systems in the Customer Access Networks
D7S0 Satellites in B-ISDN
December 1990 Document 3 IBC Common Functional Specification Issue A
Document 5 - IBC Access
£211 Interface at the T Reference Point - Physical Layer
E212e at the Tet - ATM Layer
£216e at the T Reference Point - Meta-signalling Protocol
£330 Optical Interfaces for the Customer Access Network
E333l User Network Interface for High Speed Digital (HD)TV using TDM and
WDM
E334l User Network Interface for (HD)TV using HDWDM
E335 Optical Userk Interface for (HD)TV using Coherent Multichannel (CMC)
Systems
E500 Metropolitan Area Networks - MAN
Document 6 - Network Management
HUO Networkt Terminology and Definitions
H200 An Architecture for the Telecommunications Management Network
H400 Telecommunications Management Functional Areas
H404 The Provisioning Activity Functional Area
H40Se Maintenance Functional Area
H406e Performance Management Functional Area
H408 The Accountingtl Area
H409e Customer Query and Control Functional Area
H531 Network Performance Monitoring
HSSO Telecommunications Management Objects
Document 7 - Network Evolution, Terminals and CPN
J100 General Aspects of Audio-visual Services within IBC
LI00 CPN Reference Configurations and Functional Models
M100 Network Evolution
M200 TMNn
Document 8 - General Terminology
A150 Vocabulary of Terms for IBC
Document 3 December 1990 IBC Common Functional Specification Issue A
Specification RACE D120
TITLE : SPECIFICATION OF OVERALL B-ISDN CONNECTION TYPES
PREFACE :
This draft is based on work carried out by RACE 1044 RCD.
HISTORY :
Status Comments Date
Issue A Discussed at the RACE Concertation Technical Workshop 23 Nov 90
STG 2.1 on 8-9 November 1990
CONTENT :
1 Introduction
2 Basic Concept of B-ISDN Connection Types
3 Relationship between Services and Connection Types
4 * Attributes and Possible Values Already Identified for B-ISDN Connection Types
5 * Examples of Overall B-ISDN Connection Types
* These sections are in outline form with headings only. It is intended to include text in
a future edition of the CFS.
1 INTRODUCTION
In this CFS a method for the specification of B-ISDN network capabilities is derived by using
connection types as a basis in a manner similar to that used in CCITT 1.340 (Blue Book,
Melbourne 1988) for the N-ISDN network capabilities. In the N-ISDN the specification of
network capabilities is mainly derived by:
the definition of a set of ISDN connection types, associated with a set of attributes with
certain values (CCITT 1.340),
other requirements described in CCITT Recommendations 1.310, 1.410, 1.411 of the Blue
Book.
The method of specifying ISDN connection types can be described as a four step process (a
precursor of this process involves some knowledge of the services to be supported; see section
3.1 below):
Step 1: Select a set of attributes, useful to describe ISDN connections,
e.g. Information Transfer Mode, Establishment of Connection,
Symmetry, Channel Rate, ... (cf. 1.140: "Attribute Technique ... ").
Step 2: Identify the possible attribute values (or value classes) for
these attributes, e.g. "Switched, semi-permanent, permanent" fo
"Establishment of Connection".
Step 3: Select a combination of specific attribute values to describe a
connection type.
Step 4:t a limited set of the combinations, if possible; these form
the Connection Types (in 1.340, this selection of combinations is
mainly based on a selection of 5 "dominant" attributes).
December 1990 Document 3 - DI20 Issue A IBC Common Functional Specification
A connection type obtained by this method is therefore associated with a set of attributes with
certain values (they are still under study and will provided in section 4 of this CFS in 1991).
Step 4 is necessary, because not all of the combinations of attribute values of step 3 are of
practical use; some combinations will be impractical or may even be contradictory.
For the B-ISDN, the method used to get N-ISDN connection types has to be enlarged, taking
into account
user requirements,
new network performance requirements,
the impact of multi-media, multi-point services.
This CFS only describes the specification of overall connection types; a breakdown into
connection elements and basic connection components (together with the corresponding
association laws) is derived in CFS D230. Material for D230 is still under study and subject to a
later CFS edition.
Teleservices HLF
Bearer
LLF
Services
ISDN capabiIities ISDN services
Figure la. Relationship between Telecommunications Services and Network Capabilities.
(Source: CCITT Rec. 1.310, Figure 2)
Overall connection types can be regarded as a description of the basic lower laver functions
(LLFs, see Figure la, taken from CCITT Rec. 1.310) of the ISDN. In addition to describing
network capabilities of the ISDN, the identification of ISDN connection types facilitates the
specification of network-to-network interfaces. It will also assist in the allocation of network
performance parameters.
Based on ISDN connection types, telecommunication services can be offered to a user (see Figure
lb)). It should be noted that users only specify the (tele-) service required while the network
allocates resources to set up a connection of the specific type as necessary to support the
requested service. It is further noted that for certain services additional functions (e.g. additional
lower layer functions and/or higher layer functions) may be required as depicted in Figure lb).
Document 3 - D120 December 1990