ETSI ETS 300 483 ed.1 (1996-04)

SLOVENSKI STANDARD
01-december-2003
7HUPLQDOVNDRSUHPD7(±'LJLWDOQRRPUHåMH]LQWHJULUDQLPLVWRULWYDPL,6'1±
9HþWRþNRYQHNRPXQLNDFLMH]DDYGLRYL]XDOQHVWRULWYH±*ODYQHIXQNFLRQDOQRVWLLQ
RVQRYQH]DKWHYH]DYHþWRþNRYQHNUPLOQHHQRWH0&8
Terminal Equipment (TE); Integrated Services Digital Network (ISDN); Multipoint
communications for audiovisual services; Main functionalities and basic requirements for
Multipoint Control Units (MCUs)
Ta slovenski standard je istoveten z: ETS 300 483 Edition 1
ICS:
33.080 Digitalno omrežje z Integrated Services Digital
integriranimi storitvami Network (ISDN)
(ISDN)
35.180 Terminalska in druga IT Terminal and other
periferna oprema IT peripheral equipment
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 483
TELECOMMUNICATION April 1996
STANDARD
Source: ETSI TC-TE Reference: DE/TE-04032
ICS: 33.020
ISDN, audiovisual, multipoint
Key words:
Terminal Equipment (TE);
Integrated Services Digital Network (ISDN);
Multipoint communications for audiovisual services;
Main functionalities and basic requirements
for Multipoint Control Units (MCUs)
ETSI
European Telecommunications Standards Institute
ETSI Secretariat
F-06921 Sophia Antipolis CEDEX - FRANCE
Postal address:
650 Route des Lucioles - Sophia Antipolis - Valbonne - FRANCE
Office address:
c=fr, a=atlas, p=etsi, s=secretariat - secretariat@etsi.fr
X.400: Internet:
Tel.: +33 92 94 42 00 - Fax: +33 93 65 47 16
*
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 1996. All rights reserved.

Page 2
ETS 300 483: April 1996
Whilst every care has been taken in the preparation and publication of this document, errors in content,
typographical or otherwise, may occur. If you have comments concerning its accuracy, please write to
"ETSI Editing and Committee Support Dept." at the address shown on the title page.

Page 3
ETS 300 483: April 1996
Contents
Foreword .5
1 Scope .7
2 Normative references.8
3 Definitions.9
4 Abbreviations.9
5 Functional requirements for a MCU .10
5.1 Basic functions.10
5.1.1 Network Interface Unit (NIU) .10
5.1.2 Multiplexer/Demultiplexer Unit (MDU).10
5.1.3 Audio Processor Unit (APU).11
5.1.4 Video Processor Unit (VPU).11
5.1.5 Control Processor Unit (CPU) .11
5.2 Optional functions .13
5.2.1 Additional audio processing .13
5.2.2 Additional video processing.13
5.2.3 Additional call processing.13
5.2.4 Management of the SCM .14
5.2.5 Alternative conference management modes.14
5.2.6 Identification of connected terminals.14
5.2.7 Data transmission and/or broadcast functions.14
5.2.8 Identification of token assignment.15
5.2.9 Transmission of additional information.15
5.2.10 Multiple MCU configurations .15
5.2.11 Off-line or on-line conference administration .17
5.2.12 Security measures.17
5.2.13 Maintenance.17
5.2.14 Operation Administration and Maintenance Terminal (OA&MT).17
5.3 Various types of MCU - minimum functional requirements .17
5.3.1 Different classes of MCU .17
5.3.2 Minimum functional requirements for every class of MCU.18
5.4 Technical requirements .19
5.4.1 General requirements.19
5.4.2 Requirements applicable to individual functions .19
6 Special procedures for multipoint communications.20
6.1 Basic procedures .20
6.1.1 Initialisation procedures.20
6.1.2 Further capability exchanges .23
6.1.3 BAS sequencing.23
6.1.4 Mode switching procedures.23
6.1.5 Video bit-rate changing procedure .23
6.1.6 Video switching procedures .24
6.1.6.1 Automatic switching.24
6.1.6.2 Controlled switching.24
6.2 Videoconference with multiple MCUs .25
6.2.1 Designation of master MCU .25
6.2.2 Initialisation.25
6.2.3 Common operating mode.25
6.3 Special maintenance procedures .26
6.3.1 Loop control.26
6.3.2 Loop detection.26

Page 4
ETS 300 483: April 1996
7 Basic in-band signalling requirements for MCUs. 27
Annex A (informative): Requirements applicable to audiovisual terminals. 30
A.1 Functional requirements . 30
A.1.1 Basic multipoint operation . 30
A.1.2 Enhanced multipoint operation. 30
A.1.2.1 In-band signalling procedures. 30
A.1.2.2 Additional keyboard and display . 30
A.2 In-band signalling requirements. 32
Annex B (informative): Bibliography . 34
History. 35

Page 5
ETS 300 483: April 1996
Foreword
This European Telecommunication Standard has been prepared by the Terminal Equipment (TE)
Technical Committee of the European Telecommunications Standards Institute (ETSI).
Transposition dates
Date of adoption of this ETS: 15 March 1996
Date of latest announcement of this ETS (doa): 31 July 1996
Date of latest publication of new National Standard
or endorsement of this ETS (dop/e): 31 January 1997
Date of withdrawal of any conflicting National Standard (dow): 31 January 1997

Page 6
ETS 300 483: April 1996
Blank page
Page 7
ETS 300 483: April 1996
1 Scope
This ETS specifies the functional requirements applicable to a Multipoint Control Unit (MCU), or a set of
interconnected MCUs, which allows several audiovisual terminals to communicate simultaneously using
single or multiple digital channels up to 1 920 kbit/s when interconnected through the pan-European
Integrated Services Digital Network (ISDN).
This ETS specifies the basic in-band signalling procedures to be supported to control the operation of
MCU and audiovisual terminals involved in a simple multipoint communication or a basic video/
audiographic conference as specified in other standards.
This ETS includes an overall description of the basic and optional functionalities of a MCU, and lists the
related requirements.
Annex A (informative) describes the various requirements which apply to audiovisual terminals in order to
ensure their capability to take part in multipoint communications.
A MCU with any interface connected to the ISDN via a Channel Aggregation Unit (CAU) and/or special
interface adapters may be used for multipoint communication when the composite equipment complies
with all requirements specified in this ETS. However, the various related pieces of equipment are outside
the scope of this ETS.
A MCU may establish conferences which include not only audiovisual terminals connected through an
ISDN, but also some audiovisual terminals directly linked through digital leased lines.
A MCU may set up a conference where the connected terminals include not only videoconference and
videotelephony terminals but also Audiographic conference, 7 kHz telephony or 3,1 kHz telephony
terminals. The description of protocols and requirements is limited to the basic multipoint communication
established between various terminals supporting 3,1 kHz telephony, 7 kHz telephony, or the
Videotelephony teleservice. The protocols and requirements necessary to support more sophisticated
services, such as Videoconference, Audiographic conference, or applications based on data transmission
are not considered here.
NOTE 1: The T.120 series of ITU-T Recommendations presently developed by ITU-T SG 8
should be used to support such enhanced functionalities.
Use of the protocol specified in ITU-T Recommendation H.243 to support these
functionalities should be precluded since it would result in incompatibilities between
MCUs and/or terminals.
NOTE 2: In the case of interworking with Public Switched Telephone Network (PSTN) or mobile
telephony terminals, echoes and/or transmission delays can degrade the audio
communication quality to an unacceptable level.
A MCU may be owned either by a public service provider or by a private customer. In the latter case the
equipment is part of a Private Telephone Network.
The D-channel signalling protocol used to set up, modify and clear a multipoint communication is outside
the scope of this ETS.
On line procedure and/or protocol to be used by an end user to require, modify or cancel a conference
reservation is outside the scope of this ETS.
Implementation of the T.120 series of ITU-T Recommendations for the support of the enhanced functions
associated to various options of the videoconference service (e.g. Conference control, multipoint data
communication service) is outside the scope of this ETS.
Conformance to this ETS will be demonstrated by checking that all mandatory functional requirements are
supported during execution of a test suite which is specified in other ETSs.

Page 8
ETS 300 483: April 1996
2 Normative references
This ETS incorporates by dated or undated reference, provisions from other publications. These
normative references are cited at the appropriate places in the text and the publications listed hereafter.
For dated references, subsequent amendments to, or revisions of any of these publications apply to this
ETS only when incorporated in it by amendment or revision. For undated references the latest edition of
the publication referred to applies.
[1] ETS 300 144: "Integrated Services Digital Network (ISDN); Audiovisual services;
Frame structure for a 64 kbit/s to 1 920 kbit/s channel and associated syntax for
inband signalling".
[2] ITU-T Recommendation G. 728 (1993): "Coding of speech at 16 kbit/s using
low-delay code excited linear prediction".
[3] CCITT Recommendation G. 711 (1988): "Pulse code modulation (PCM) of voice
frequencies".
[4] CCITT Recommendation G. 722 (1988): "7 kHz audio-coding within 64 kbit/s".
[5] ETS 300 012: "Integrated Services Digital Network (ISDN); Basic user-network
interface; Layer 1 specification and test principles".
[6] ETS 300 011: "Integrated Services Digital Network (ISDN); Primary rate
user-network interface; Layer 1 specification and test principles".
[7] ETS 300 290: "Business TeleCommunications (BTC); 64 kbit/s digital
unrestricted leased line with octet integrity (D64U); Terminal equipment
interface".
[8] ETS 300 248: "Business Telecommunications (BT); Open Network Provision
(ONP) technical requirements; 2 048 kbit/s unstructured leased line (D2048U);
Terminal equipment interface".
[9] ETS 300 420: "Business TeleCommunications (BTC); 2 048 kbit/s structured
leased line (D2048S); Terminal equipment interface".
[10] ETS 300 102-1: "Integrated Services Digital Network (ISDN); User-network
interface layer 3; Specifications for basic call control".
[11] ETS 300 267: "Integrated Services Digital Network (ISDN); Telephony 7 kHz
and videotelephony teleservices; Digital Subscriber Signalling System No. one
(DSS1) protocol".
[12] ETS 300 164: "Integrated Services Digital Network (ISDN); Meet-Me
Conference (MMC) supplementary service; Service description".
[13] ETS 300 185: "Integrated Services Digital Network (ISDN); Conference call add-
on (CONF) supplementary service; Digital Subscriber Signalling System No. one
(DSS1) protocol".
[14] ETS 300 143: "Integrated Services Digital Network (ISDN); Audiovisual services;
Inband signalling procedures for audiovisual terminals using digital channels up
to 2 048 kbit/s".
[15] ETS 300 145: "Integrated Services Digital Network (ISDN); Audiovisual services;
Videotelephone systems and terminal equipment operating on one or two
64 kbit/s channels".
[16] ITU-T Recommendation H. 261: "Video codec for audiovisual services at
p x 64 kbit/s".
Page 9
ETS 300 483: April 1996
3 Definitions
For the purposes of this ETS, the following definitions apply:
Conference control: The capability conferred to one terminal to control operation of the MCU. This
function requires a specially designed terminal. The terminal user may be the actual chairman of the
meeting or the conference controller.
Directly connected terminal or Local terminal: A terminal connected to a given MCU (this wording
should be used only in case of multiple MCU configuration).
Master MCU: The MCU selected to control the system operation in case of multiple MCU configuration.
Multipoint Control Unit (MCU): A functional entity which is used to establish a multipoint communication
between several audiovisual (or audio only) terminals. A MCU may be owned by the customer (and
located in its premises) or may be offered by a service provider/network operator.
MCU Port: The bi-directional access point of the digital link established between a terminal (or another
MCU) and a MCU. It is a logical entity; a port may eventually require several MCU-Network physical
interfaces, but several ports may also share a MCU-Network physical interface.
Primary Port: A MCU Port where the connected terminal can support the SCM.
Secondary Port: A MCU Port where the connected terminal has a lower capability than the SCM.
Selected Communication Mode (SCM): Common operating mode of most terminals during the
conference. It defines symmetrical rates for audio, video and any data path.
token: A virtual token which may be allocated by a controlling entity (MCU or Conference-control terminal)
to confer, to a requesting terminal, authorisation to initiate a special activity (e.g. video broadcast, data
transmission) which otherwise would be in conflict with normal or similar activities of other terminals. Such
a token may be allocated or "passed" successively from one terminal to another.
4 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
APU Audio Processor Unit
BAS Bit-rate Allocation Signal
C&I Control and Indication
cap-set capability set
CAU Channel Aggregation Unit
CLIP Calling Line Identification Presentation
CPU Control Processor Unit
DPU Data Processor Unit
ECS Encryption Control Signal
FAS Frame Alignment Signal
ISDN Integrated Services Digital Network
MBE Multiple Byte Extension (BAS codes)
MCS Multipoint Communication Service
MCU Multipoint Control Unit
MDU Multiplexer/Demultiplexer Unit
MLP Logical data sub-channel which may contain various data protocols (also
referred to as Multi-Layer Protocol in ETS 300 144 [1])
NIU Network Interface Unit
OA&MT Operation, Administration and Maintenance Terminal
ONP Open Network Provision
PIN Personal Identification Number
PSTN Public Switched (analogue) Telephone Network
SBE Single Byte Extension (BAS codes)
SCM Selected Communication Mode
SCM-cap SCM capability set
Page 10
ETS 300 483: April 1996
VPU Video Processor Unit
NOTE: A complementary list of abbreviations used for C&I (typed in bold characters) can be
found in tables 5 and A.2.
5 Functional requirements for a MCU
5.1 Basic functions
A MCU includes several types of functional entities. An overall description is given by the schematic of
figure 1 (see subclause 5.1.5). The various functional entities are listed and briefly described below. The
two first types shall be provided for every individual port, while the others are common to all ports involved
in a multipoint communication (conference).
NOTE: There is no particular limit set to the maximum number of ports involved in a
conference, however it is practically limited, taking into account cost, set-up difficulty
and audio performance degradation (noise).
A same piece of equipment called a MCU, may simultaneously handle several
independent videoconferences.
5.1.1 Network Interface Unit (NIU)
The Network Interface Unit (NIU), supported by a local call control facility, has two basic tasks:
- the establishment and release of the digital link related to the port;
- the adaptation of the composite signal (audio + video + signalling + etc.) to the ISDN interface.
NOTE: The network access may use an external standard interface adapter.
5.1.2 Multiplexer/Demultiplexer Unit (MDU)
The Multiplexer/Demultiplexer Unit (MDU) performs the following tasks:
- the generation/recovery of in-band frame and multiframe synchronisation signals;
- the buffering and ordering of audio, video, data and in-band signalling signals;
- the transmission/reception of Bit-rate Allocation Signal (BAS) codes;
- the transmission/reception of optional data sub-channel(s).
This unit is also used to split/aggregate several "64 kbit/s channels" which may be necessary for a given
port, when this is required by the selected transfer rate capability.
NOTE: Splitting/aggregation may be achieved in an external piece of equipment.

Page 11
ETS 300 483: April 1996
5.1.3 Audio Processor Unit (APU)
The Audio Processor Unit (APU) receives audio inputs from all demultiplexers and generates the same
number of audio outputs sent to the multiplexers. The generation of output signals may use one of several
techniques:
a) audio mixing - the signal sent to each terminal is the linear sum of the audio signals delivered by the
other terminals;
b) audio switching - the signal sent to a conferee is either the largest audio input signal or is directly
selected according to the controlled operating mode. In any case no signal is returned to the
speaker; the switching shall be performed smoothly and without additional noise.
NOTE: In both cases audio signals with a level lower than an adjustable threshold may be
suppressed in order to avoid the addition of useless noises/echoes.
A small time delay (Θ ) may be incorporated into the automatic switching to prevent its
a
excessively frequent activation by inadvertent noises (coughing, knocking a
microphone, etc.).
5.1.4 Video Processor Unit (VPU)
The Video Processor Unit (VPU) receives video signals from all demultiplexers and generates video
signals sent to the multiplexers. The generation of output signals is generally based on switching
techniques:
a) the signal broadcast to conferees is the picture of the current speaker (largest audio input signal). In
this case the signal sent to the current speaker is the signal received from the previous speaker;
b) the signal sent to the conferees is selected according to a special operating mode:
- a terminal requires broadcasting its video to all other conferees (one at a time);
- the MCU itself chooses which video shall be broadcast (cf. subclause 6.1.6.2).
NOTE: In case of automatic video switching, another time constant (Θ ) may be used to
v
prevent useless activation resulting from a short voice burst.
The MCU should be designed in order to preserve the audio/video alignment as
provided by terminals.
5.1.5 Control Processor Unit (CPU)
The Control Processor Unit (CPU) controls set up and release of the various digital links. In the case of
ports connected to an ISDN, it provides for co-ordinated set-up and release of the initial and additional
"channels".
The CPU exchanges information with connected terminals by sending and receiving the BAS codes
transmitted through the in-band signalling procedures.
After an initial capability exchange sequence, the CPU defines the SCM and controls the various entities
(NIU, MDU, APU, VPU and DPU) according to:
- capabilities declared by the audiovisual terminals;
- MCU configuration and management data.
After exchange of Controls and Indications (C&I), the CPU routes the various internal signals.

Page 12
ETS 300 483: April 1996
Ar1
Ar1
Vr1
Demultiplexer Ar2
Dr1
Network Ar
Br1
AUDIO PROCESSOR
ArN
Interface
At1
( NIU ) Vt1 ( APU )
Multiplexer
Dt1
At1
Bt1
At2
At
AtN
Call Control
Ar1
Vr1
Vr1
Demultiplexer Vr2
Dr1
Network Vr
Br1 VIDEO PROCESSOR
VrN
Interface
At1
( NIU ) Vt1 ( VPU )
Multiplexer
Dt1
Vt1
Bt1
Vt2
Vt
VtN
Call Control
" Dr1
Dr2
"
Dr
DATA PROCESSOR
" DrN
( DPU )
( repeted N times )
Dt1
Dt2
Dt
"
DtN
"
"
ArN
Br1
VrN
Demultiplexer Br2
DrN CONTROL
Network Br
BrN
BrN PROCESSOR
Interface
AtN
( NIU ) VtN ( CPU )
Multiplexer
DtN
Bt1
BtN
Bt2
Bt
BtN
Call Control
to Call Control
from Call Control
A : audio signal    D : data signal
V : video signal    B : BAS codes (or equivalent)
r : receive        t : transmit
Figure 1: Schematic of a Multipoint Control Unit

Page 13
ETS 300 483: April 1996
5.2 Optional functions
A wide variety of MCUs may be developed according to the various options which could be provided. In
order to identify, in subclause 5.3, the minimum requirements applicable to a "basic" MCU, a
non-exhaustive list of optional functions is presented below.
Some optional functions require related enhanced functions of connected terminals (e.g. terminal used for
Conference control), however terminals having no such enhancements may take part in a
videoconference without misoperation (cf. annex A).
Some optional functions are not independent since one shall be supported to allow implementation of
another one (see "bound options" in table 1, subclause 5.3.2).
When an option described in this ETS is declared by a manufacturer or service provider, the related
protocol procedures shall conform to the requirements specified in clause 6.
5.2.1 Additional audio processing
Additional functions could be:
a) provision of tones and/or announcements during conference set-up;
b) total control of individual audio source and destination.
5.2.2 Additional video processing
In addition to the basic switching functions listed in subclause 5.1.4, a MCU may provide:
a) video mixing: the signal sent to all conferees results from spatially multiplexing the images sent by
the other terminals into a single composite image in a "split screen" format;
b) total control of individual video source and destination;
c) provision of visual information on call and/or terminal states.
5.2.3 Additional call processing
To be able to interwork with audiovisual terminals, which may offer various interfaces and/or transfer rate
capabilities, a MCU may provide:
a) internal splitting/aggregation of the various "64 kbit/s channels" involved in a MCU-terminal link;
b) compatibility with multiple channel terminals;
c) compatibility with mixed single and multiple channel terminals (SM comp capability);
d) compatibility with remote terminals connected to restricted networks;
e) compatibility with 3 kHz, 4 kHz and/or 7 kHz telephony terminals.
Conference set-up mode results from permanent, reserved and on-demand connections. In the latter case
the MCU may offer several alternative procedures:
f) "Meet-me conference" using a MCU ISDN destination number;
g) "Meet-me conference" using a conference ISDN destination number;
h) "Dial out conference" with previous registration of conferee ISDN numbers;
i) "Mixed mode (Dial out and Meet-me) conference".
During the conference, a MCU may also offer additional facilities related to call control such as:
j) addition of a new conferee (add on conference requiring new dialling);
k) exclusion of a terminal (connection is released).

Page 14
ETS 300 483: April 1996
5.2.4 Management of the SCM
At least one of the following solutions shall be available to determine the Communication Mode and shall
be clearly indicated to user by manufacturer and/or service provider:
a) the SCM is fixed, it results from the MCU definition and manufacture;
b) the SCM is fixed, it results from a previous arrangement with the service provider at the time of
conference booking;
c) the SCM is set up according to a Multi-Layer Protocol (MLP) based procedure;
d) the SCM is selected automatically according to an identified algorithm (e.g.):
- highest common mode of audiovisual terminals;
- based on capabilities of the chair-control terminal;
- based on an adjustable threshold;
- etc.
NOTE: When the SCM is fixed, any terminal with a lower capability may be rejected;
otherwise, it is considered as a secondary terminal (subclause 6.1.1).
5.2.5 Alternative conference management modes
A MCU shall at least provide the unconducted mode, where switching functions are performed
automatically, and result in selection and transmission of the current speaker image (subclause 5.1.4).
In addition, it may also provide conference control procedures.
When the conference control facility is declared, the following functions shall be provided:
a) claim, assignment of chair-control token;
b) withdrawal of chair-control token (return to voice activation mode);
c) indication of connected terminals;
d) indication of selected terminal for video broadcast;
e) indication of terminals asking the floor;
f) selection of a terminal for video broadcast;
g) addition/drop of a terminal;
h) withdrawal of data token (cf. subclause 5.2.7);
i) release of the complete conference;
however, further possible options may be offered:
j) selection of video signal sent to the terminal having the Chair-control;
k) separate interconnection of two terminals for private consultation.
5.2.6 Identification of connected terminals
Identification of connected terminals by numbering procedures, though optional, should be required for
most of the functions available under the conference control provisions. Terminal identification may also
be used in order to associate incoming calls (for additional channels) to originating terminals. This is
specially useful in case of "Meet-me conference" (cf. subclause 5.2.3) using the same ISDN destination
number (allocated either to the MCU or to the conference).
5.2.7 Data transmission and/or broadcast functions
A Data Processor Unit (DPU), as shown in figure 1, shall support data transmission. The data shall be
transmitted/broadcast according to the capability of the connected terminals.
When a terminal has not declared the related capability, it does not receive the data and, in addition, does
not receive video, since it cannot support the multiplexed rates effective between the MCU and those
terminals exchanging data (it is reduced to "secondary" status).

Page 15
ETS 300 483: April 1996
NOTE: An option could be to continue video exchange between secondary terminals; but a
better solution is the implementation by terminals of the "Dummy data" capability (cf.
annex A).
When the Data transmission/broadcast option is declared, the following functions shall be provided
independently for any data sub-channel:
a) claim, assignment of Data token;
b) withdrawal of Data token;
c) opening/closing of a data sub-channel;
d) changing rate of a data channel;
e) closing of data channel on time out (no token claim).
5.2.8 Identification of token assignment
A MCU may be able to identify, by their allocated number, terminals to which either the Conference
control, or Data tokens have been assigned; then, it shall send this information to any requesting terminal.
5.2.9 Transmission of additional information
Additional information may be transmitted between the MCU and terminals in order to make the
Conference control terminal user friendly. It can consist of supplementary identity information (e.g.
user/company names, location/country) or be oriented to a better conference management (e.g.
conference end-time reminder).
5.2.10 Multiple MCU configurations
The use of several MCUs for a videoconference may be considered when special requirements result
from:
- the number of terminals;
- the location of terminals;
- the digital links availability (leased lines and public ISDN accesses).
The resulting configurations include:
- MCU star: two or more MCUs, connected to a central one, define a second order
hierarchy (cf. figure 2, a);
- Dumb-bell: two interconnected MCUs gathering terminals at both ends (cf. figure 2, b)
but may extend to higher order configurations.

Page 16
ETS 300 483: April 1996
MULTIPOINT
MULTIPOINT
CONTROL CONTROL
UNIT
UNIT
MULTIPOINT
MULTIPOINT MULTIPOINT
CONTROL CONTROL
CONTROL
UNIT UNIT
UNIT
MULTIPOINT
MULTIPOINT
CONTROL
CONTROL
UNIT
UNIT
a) "Star" configuration
Terminal Terminal
MULTIPOINT MULTIPOINT
Terminal CONTROL CONTROL Terminal
UNIT UNIT
Terminal Terminal
b) "Dumb bell" configuration
NOTE: In most cases, a user cannot choose the video sent to his terminal when the source is not
connected to the local MCU.
Figure 2: Multiple MCU configurations
In the case of a multiple MCU configuration, the following functions may be provided:
a) master/slave designation before the conference;
b) automatic choice of a master in case of Dumb-bell configuration.

Page 17
ETS 300 483: April 1996
5.2.11 Off-line or on-line conference administration
The MCU may offer additional functions related to videoconference booking and scheduling. They are
outside the scope of this ETS but have an impact on the way a MCU reacts to some stimulation during its
test. They could include, for example, registration of various parameters which are used later to set up a
videoconference:
a) user data such as name, site, ISDN number, password;
b) terminal characteristics: capabilities and special facilities;
c) day, time and duration;
d) conference modes (initial mode and allowed changes);
e) Conference control (initial and alternative possibilities);
f) Data token allocation (initial and further allowed assignments).
5.2.12 Security measures
A MCU may combine D-Channel and in-band procedures to identify end points and, when possible, to
authenticate conferees by exchanging passwords or Personal Identification Numbers (PINs).
5.2.13 Maintenance
A MCU may offer many different maintenance functions including self tests and fault diagnostics; they are
outside the scope of this ETS, however when these functions rely on local or remote loop backs (in the
connected terminals) performed at different points, they shall conform to related standardized protocol
procedures.
Care should be taken to avoid automatic testing that disturbs the normal MCU operation.
5.2.14 Operation Administration and Maintenance Terminal (OA&MT)
Definition, functions and interface of the OA&MT are outside the scope of this ETS.
5.3 Various types of MCU - minimum functional requirements
5.3.1 Different classes of MCU
Given the wide range of possible capabilities and options, it is appropriate, for convenience and clarity, to
identify several classes of MCU which can be referred to.
A definition of seven MCU classes is given below.
Class 1 addresses equipment especially designed to establish an audiovisual
conference where participants use 1B videotelephony terminals (with audio
coding according to ITU-T Recommendation G.728 [2]) and 3,1 kHz telephony
terminals.
Class 2 includes MCU which can establish conferences between participants using 2B
videotelephony terminals and 3,1 kHz or 7 kHz telephony terminals.
Class 2d this MCU has the same definition as above but, in addition, supports data
transmission/broadcast and/or data applications.
Class 3 addresses MCUs which aim at multipoint meetings where every site has
terminals offering an enhanced picture quality resulting from a higher transfer
rate (3B to 6B).
Class 3d same as above with the data functionalities.

Page 18
ETS 300 483: April 1996
Class 4 includes MCU which can be used to established videoconferences with high
quality pictures established between specially equipped rooms, and where
additional facilities such as Conference-control, though optional, are
recommended.
Class 4d same as above with the data functionalities.
5.3.2 Minimum functional requirements for every class of MCU
Table 1 lists the various attributes which are used to characterize a MCU.
The minimum requirements are listed as mandatory attributes (M).
The support of some functional attributes identified (R) are recommended.
The attributes marked ( ) identify options which may be supported independently.
*
Some attributes marked (n) relate to "bound" options, which cannot be reasonably provided separately;
they are defining an option package.
When several attributes are marked (C), this means that at least one of these functionalities shall be
chosen and supported by a MCU.
When there is no entry for one attribute in a Class column, this means that it is inopportune or useless.
NOTE: Manufacturers may include, in one product, one or more of these "classes". They may
also provide additional options which then conform to related definitions and
standardized protocol implementation, but the behaviour when used with other
equipment might be less predictable or lead to man-machine interface problems.

Page 19
ETS 300 483: April 1996
Table 1: MCU classes and related requirements
Requirements
N° Attributes Values Reference vs MCU class
1 2 2d33d 4 4d
1 Minimum number of ports 4 to 8 5.3.1, 5.3 2 44444 44
2 Type of network interface ISDN - Basic Access C C C
ISDN - Primary Rate C C C M M
* *
Leased line G.703
* * * * * * *
Leased line V.35
* * * * * * *
3 Minimum transfer rate capability at 64 kbit/s or 1B M
M M
every port 128 kbit/s or 2 B
*
384 kbit/s or 6 B M M
* *
> 384 kbit/s MM
* *
4 Audio processor mode audio mixing 5.1.3 a C M M M M M M
automatic switching 5.1.3 b C
* * * * * *
controlled switching 5.1.3 b
* * * *
tones/announcements 5.2.1 a R R
* *
total control 5.2.1 b
* * * * * *
5 Audio coding algorithm G.711 [3]+ G.728 [2] M
G.711 [3] + G.722 [4] M M M M MM
G.711 [3] + G.722 [4] +
* * * * *
G.728 [2]
6 Video processor mode automatic switching 5.1.4 a MMM M M M M
controlled switching 5.1.4 b
* * * * *
mixed video (split screen) 5.2.2 a
* * * *
total control 5.2.2 b
* *
7 Channel aggregation (more than 2 B- Internal aggregation 5.2.3 a RRR R R R
channels) "SM comp" capability 5.2.3 b/c R R R R
Use of terminal identity 5.2.6 (1) (1) (1) (1)
* * * *
8 Set up mode/Call control Meet-me conference 5.2.3 e/f C C C C
* * *
Dial out conference 5.2.3 g C C C C
New conferee addition 5.2.3 h
* * * *
Exclusion of conferee 5.2.3 i
* * * *
Restricted network comp. 5.2.3 d
* * * * * * *
9 Selected communication mode Fixed by manufacturer 5.2.4 a C C C C
Programmable 5.2.4 b/c C C C C C C C
Automatic selection 5.2.4 d C C C C C C C
Telephony terminals 6.1.1 M
* * * * * *
accepted secondary
terminals)
10 Support of loop backs Local loops (in MCU) 6.3
* * * *
Remote (in terminals) 6.3
* * * *
11 Support of Multiple MCUs Master/Slave pre-set 5.2.10 a MMM M M M
configuration Auto selection (for 2) 5.2.10 b R R
* *
12 Conference control facility Facility support R R RR
**
* *
13 Data transmission/broadcast Support of data facilities 5.2.7 M M M
* * *
capability
14 Management of various additional Support of various 5.2.5
information concerning: user, call, individual facility to R R
* * * *
token 5.2.9
* * * * * *
15 Terminal identification (1) (1) M M
* *
16 MBE capability
*** **
5.4 Technical requirements
5.4.1 General requirements
A MCU, which belongs to a given class, shall support the mandatory attributes listed in table 1 and include
the basic functional entities described in subclause 5.1. When an option is declared, it shall be required to
offer the various facilities considered as mandatory in the description of subclause 5.2.
5.4.2 Requirements applicable to individual functions
Network interface: when a MCU has an ISDN interface, it shall conform either to ETS 300 012 [5] (basic
access) or 300 011 [6] (primary rate).

Page 20
ETS 300 483: April 1996
NOTE: If the ISDN access is provided by separate piece of equipment (e.g. adapter, CAU, it is
still considered as part of the MCU, it provides the same functions and conforms to the
same call control requirements. The interface between the two pieces of equipment is
outside the scope of this ETS.
When a MCU is designed to use several ports with more than two B-channels, an ISDN primary rate
interface is recommended.
When a MCU provides access to Open Network Provision (ONP) digital leased lines, the interface shall
conform to ETS 300 290 [7] (64 kbit/s) or ETS 300 248 [8] or ETS 300 420 [9] (2 048 kbit/s). Other
interfaces which may be provided are outside the scope of this ETS.
Audio mixing/switching: audio mixing/switching shall not lead to a noticeable degradation of speech
transmission characteristics (signal/noise ratio) compared to those resulting from the successive codings
and decodings necessary to achieve the linear addition of voice signals. Speech encoding, when used,
shall conform to related CCITT Recommendations G.711 [3] and G.722 [4], or ITU-T Recommendation
G.728 [2]. Switching shall be performed smoothly in order to avoid addition of any spurious noise.
In the case of interworking with networks and/or terminals which may cause a higher echo level (e.g.
PSTN analogue telephones) and/or longer echo delay (e.g. GSM terminals), care should be taken to keep
the audio transmission to an acceptable level of quality. This may require implementation in the MCU of
an echo cancelling device.
Video switching: care shall be taken to avoid that switching between different video sources occurs too
frequently.
Call control: call set up and/or release procedures, and D-channel signalling messages shall conform to
ETS 300 102-1 [10], and ETS 300 267 [11]. The support of fall back procedures and several teleservices
shall be in accordance with the optional support of secondary terminals. When the MCU supports
supplementary services, it shall use relevant adapted standard procedures and protocols (e.g.
ETS 300 164 [12] or ETS 300 185 [13]).
Signal Multiplexing and Framing: audio, video and optional data signals shall be multiplexed with Frame
Alignment Signal (FAS) and BAS in a frame structure according to ETS 300 144 [1].
In-band signalling: in-band signalling procedures shall conform to the various requirements of
ETS 300 143 [14] and of clauses 6 and 7 of this ETS. Frame synchronous Control and Indication (C&I)
codes shall conform to the description and requirements of ETS 300 144 [1]. Protocols necessary to
support enhanced functionalities are not included in this ETS.
Data broadcast: between the times a data sub-channel is opened and the data channel is activated, the
MCU shall fill idle bits with binary "1s".
6 Special procedures for multipoint communications
In addition to in-band signalling procedures specified in ETS 300 143 [14], MCUs and terminals supporting
basic multipoint communications, shall conform to the requirements specified below.
6.1 Basic procedures
6.1.1 Initialisation procedures
Initialisation procedures allow the communication to be established between the terminals according to the
appropriate SCM.
Page 21
ETS 300 483: April 1996
NOTE 1: The SCM is either fixed or results from encountered terminal capabilities as described
in subclause 5.2.4.
A MCU may successively declare different capabilities according to those declared by
newly connected terminals. It may, for instance, initially declare 6 B-channel and CIF
capability and later accept 2 B-channel and QCIF for final SCM capability, as this one
is supported by the majority of connected terminals.
During
...