SIST ETS 300 273 E1:2003

• Abstract:

  DE/NA-053129

• Status: Published
• Publication Date: 30-Nov-2003
• ICS: 35.110 - Networking
• Technical Committee: SS EIT - Technical Board for the electrotechnical, information technology and telecommunications fields
• Current Stage: 6060 - National Implementation/Publication (Adopted Project)
• Start Date: 01-Dec-2003
• Due Date: 01-Dec-2003
• Completion Date: 01-Dec-2003
• Ref Project: ETSI ETS 300 273 ed.1 (1994-03) - Network Aspects (NA); Metropolitan Area Network (MAN); Medium Access Control (MAC) layer management

SIST ETS 300 273 E1:2003 is the Slovenian adoption of ETS 300 273 Edition 1, published by SIST. It specifies Medium Access Control (MAC) layer management for European Metropolitan Area Network (MAN) systems, including the management architecture, services, protocols and managed objects used to supervise DQDB-based MAN MAC functions. It is aimed at engineers and operators who design, implement or manage MAN nodes, MAN Switching Systems and network management systems.

What does SIST ETS 300 273 E1:2003 specify?

SIST ETS 300 273 E1:2003 covers MAC layer management for the European standard MAN. It defines how MAC resources are controlled and supervised, how management information is exchanged, and which managed objects represent the MAC layer resources.

The document is organized into five clauses and two annexes:

Part	What it covers
Clause 1	Scope
Clause 2	Normative references
Clause 3	Definitions and abbreviations
Clause 4	MAC layer management architecture, protocols and addressing
Clause 5	Information model for systems management of the MAC layer
Annex A	Optional packages for the MAC layer information model
Annex B	Bibliography

Clause 4 describes two management paths - special purpose layer management within the MAC layer and systems management through management interfaces. Clause 5 defines the managed object model, including names, attributes, actions, notifications and ASN.1 syntax. The managed object classes for Connection Oriented (CO) and Constant Bit Rate (CBR) services are outside the object model in this standard.

What are the key requirements of SIST ETS 300 273 E1:2003?

MAC layer management is split into two management mechanisms

SIST ETS 300 273 E1:2003 says that MAC layer management is carried out either by a special purpose MLM protocol inside the MAC layer or by systems management protocols. In practice, this means the same MAN MAC resources can be managed locally between peer entities or remotely through a manager/agent arrangement.

The architecture in Clause 4.1 is based on the OSI management model and managed-object principles. For implementers, that means the management software must expose MAC resources in a form that systems management can read, set and monitor.

The special purpose MLM protocol is defined for AF1 and AF2

Clause 4.2 defines the Layer Management Protocol Entity (LMPE) and the MLM interface and protocol for Access Facility 1 (AF1) and Access Facility 2 (AF2). The standard ties this mechanism to IEEE Standard 802.6 as referenced by ETS 300 212.

This matters when two MAC entities need to exchange management information directly. The standard also notes that configuration control applies only in a looped multipoint configuration, so implementers only need that part when their topology uses it.

The systems management path uses the Q interface and a short stack

Clause 4.3 defines the systems management path using manager/agent relationships. The standard specifies the Q interface for MAN systems management and states that the short stack protocol suite is mandatory when the Q interface is placed on MAN Nodes (MNs).

The short stack uses the MAN physical and data link layers, an acknowledged connectionless-mode LLC service, a connectionless-mode network service, and the application-layer mapping described in G.773. In practice, this gives a complete management path without requiring a full seven-layer stack in the standard itself.

The data link and network layer rules are tied to MAN and OSI service definitions

Clause 4.3.2.2 says the data link layer uses DQDB access and acknowledged connectionless-mode service. The MAC sublayer address length is fixed by the standard, and the LLC service and protocol follow ISO 8802-2 and its addendum for acknowledged connectionless-mode operation.

The network layer uses the connectionless-mode network service and ISO 8473, with address formats following ISO 8348 addendum 2. The standard also requires the network layer to provide the N-UNITDATA service. For users of the standard, this means management traffic has a specific service model and cannot be implemented as an arbitrary packet format.

Addressing rules identify management traffic and management entities

Clause 4.3.2.3 sets the addressing principles for MAN systems management. Management communications use connectionless MAC service, E.164-based numbering for management entities, a specific protocol identifier in the IMPDU, and one LLC Service Access Point (LSAP) address for MAN management.

This is important for interoperability. Equipment from different vendors must recognize management frames, address management entities consistently, and use the same logical link access point for MAN management traffic.

Clause 5 defines the managed object model for MAC layer resources

Clause 5 is the core of the standard. It defines managed object classes such as midPageAllocation, dqdbConfiguration, distributedQueueProcess, bandwidthBalancingProcess, manDQDBsap, manCLsap, segmentHeaderProcessing, impduReassemblyProcess, impduTransmissionProcess and physicalLayerFacilities.

For implementers, this is the model that a manager reads and writes. It covers configuration, operational state, counters, thresholds, alarms and control actions for DQDB MAC resources, including connectionless service access points and reassembly or transmission processes.

Annex A adds optional monitoring and control packages

Annex A adds optional packages for counters, thresholds and alarms. These include page counters, queue counters, bandwidth balancing, discarded IMPDU monitoring, segment header error monitoring, IMPDU reassembly monitoring and bus selection information.

In practice, Annex A is what you use when you need deeper operational visibility or optional control functions. It also includes optional notifications and optional ASN.1 attribute definitions for those functions.

What terms does SIST ETS 300 273 E1:2003 define?

• Distributed Queue Dual Bus (DQDB) - The MAN access method and management context used by the standard for MAC-layer operation.
• Medium Access Control Layer Management (MLM) - The management function that controls and monitors MAC-layer resources.
• Layer Management Protocol Entity (LMPE) - The entity that carries special purpose layer management information between MAC entities.
• Initial MAC Protocol Data Unit (IMPDU) - The MAC PDU used in the management and transmission model described by the standard.
• MAC Convergence Functions (MCF) - The functions that map higher-layer traffic into the MAC layer and use items such as header extensions and VCI lists.
• Reassembly State Machine (RSM) - The state machine that reassembles received data units during IMPDU reassembly.
• MAN Switching System (MSS) - The MAN node type referenced by the standard for interface and management behavior.

Who uses SIST ETS 300 273 E1:2003?

SIST ETS 300 273 E1:2003 is used by vendors building MAN nodes, MAN Switching Systems and management agents for DQDB-based networks. It is also used by network management system developers who need to expose MAC resources through the Q interface or other systems management interfaces.

Operators and maintenance teams use it to monitor counters, thresholds and alarms for IMPDU flow, header errors, reassembly errors and service access points. Test and conformance teams use it to check whether a device implements the specified managed objects, actions, notifications and ASN.1 structures.

Which standards are used with SIST ETS 300 273 E1:2003?

• ETS 300 211 and ETS 300 212 define MAN principles, architecture, and the MAC layer and physical layer behavior that this management standard controls.
• ETS 300 213, ETS 300 214, ETS 300 215, ETS 300 216 and ETS 300 276 provide the physical-layer convergence procedures for the supported MAN transmission options.
• IEEE Standard 802.6 supplies the DQDB functions, counters, flags and operational concepts used throughout the management model.
• CCITT Recommendation X.700, X.701, X.720, X.721 and X.722 provide the OSI management framework and information-model rules used for managed objects.
• CCITT Recommendation X.200, ISO 8802-2, ISO 8348 addendum 1, ISO 8348 addendum 2 and ISO 8473 define the service and protocol structure used for the short stack protocol suite.
• CCITT Recommendation M.3010 and CCITT Recommendation G.773 provide TMN principles and the Q-interface protocol suite guidance referenced by the standard.

What does the SIST ETS 300 273 E1:2003 document contain?

The document contains the MAC layer management architecture, the MLM interface and protocol, and the systems management model for MAN MAC resources. It also contains the definition of managed object classes, object names, attributes, actions and notifications, together with ASN.1 syntax for the information model.

Figures 1 to 4 show the layer management protocol entity, the manager-agent exchange model, and the inheritance and naming trees for the MAC layer managed objects. Clause 5.6 provides the ASN.1 modules for attributes, actions and notifications, while Annex A adds optional packages for operational counters, thresholds and alarms used in design, implementation, testing and network operation.

SLOVENSKI STANDARD
01-december-2003
Omrežni vidiki (NA) – Velemestno omrežje (MAN) – Upravljanje plasti za krmiljenje
dostopa do medijev (MAC)
Network Aspects (NA); Metropolitan Area Network (MAN); Medium Access Control
(MAC) layer management
Ta slovenski standard je istoveten z: ETS 300 273 Edition 1
ICS:
35.110 Omreževanje Networking
2003-01.Slovenski inštitut za standardizacijo. Razmnoževanje celote ali delov tega standarda ni dovoljeno.

EUROPEAN ETS 300 273
TELECOMMUNICATION March 1994
STANDARD
Source: ETSI TC-NA Reference: DE/NA-053129
ICS: 33.080
MAN, management
Key words:
Network Aspects (NA);
Metropolitan Area Network (MAN)
Medium Access Control (MAC) layer management
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 - [e-mail]
X.400: Internet:
Tel.: [phone] - Fax: [phone]
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 1994. All rights reserved.
New presentation - see History box

Page 2
ETS 300 273: March 1994
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 273: March 1994
Contents
Foreword .5
1 Scope .7
2 Normative references.7
3 Definitions and abbreviations .9
3.1 Definitions .9
3.2 Abbreviations .9
4 MAC layer management.10
4.1 MAC layer management architecture .10
4.2 MLM through special purpose layer management protocols within the MAC layer .11
4.2.1 MLM interface.11
4.2.2 MLM protocol.11
4.3 MLM through systems management .12
4.3.1 Interface .14
4.3.2 Protocols .14
4.3.2.1 Introduction.14
4.3.2.2 Short stack protocol suite .14
4.3.2.2.1 Physical layer.14
4.3.2.2.2 Data link layer .15
4.3.2.2.3 Network layer.15
4.3.2.2.4 Mapping functions.15
4.3.2.2.5 Application layer.15
4.3.2.3 Addressing principles for MAN systems management.15
4.3.2.3.1 MAC layer addresses.16
4.3.2.3.2 Logical link addresses .16
4.3.2.3.3 Addressing at higher layers .16
5 Information model for systems management of the MAC layer.16
5.1 Object classes and packages definitions.16
5.1.1 Message identifier page allocation .16
5.1.2 DQDB configuration .17
5.1.3 Distributed queue process.18
5.1.4 Bandwidth balancing process.18
5.1.5 MAN DQDB service access point.19
5.1.6 MAN CL service access point .20
5.1.7 Segment header processing .20
5.1.8 IMPDU reassembly process.21
5.1.9 IMPDU transmission process.22
5.1.10 Physical layer facilities.24
5.2 Name bindings for object classes.24
5.3 Attributes.29
5.4 Actions .40
5.5 Notifications .41
5.6 ASN.1 syntax .42
5.6.1 ASN.1 attributes definitions .42
5.6.2 Action module definitions .44
5.6.3 ASN.1 notification definitions.45
Annex A (informative): Optional packages for the MAC layer information model.46
A.1 MID page allocation.46
A.2 Distributed queue process.47

Page 4
ETS 300 273: March 1994
A.3 Bandwidth balancing process. 50
A.4 Connectionless service access points. 51
A.5 Segment header processing. 53
A.6 IMPDU reassembly process . 55
A.7 IMPDU transmission process . 59
A.8 ASN.1 syntax . 60
A.8.1 ASN.1 optional attributes definitions . 60
A.8.2 ASN.1 optional notification definitions. 61
Annex B (informative): Bibliography . 62
History. 63

Page 5
ETS 300 273: March 1994
Foreword
This European Telecommunication Standard (ETS) describes the layer management for the Medium
Access Control (MAC) layer of European Metropolitan Area Networks (MANs) to the ETSs on MANs.
This ETS has been produced by the Network Aspects (NA) Technical Committee of the European
Telecommunications Standards Institute (ETSI) taking into account the guide-lines given in CCITT
Recommendation X.700 [11] and the protocol specification given in ETS 300 212 [2].
Introduction
All the resources of a telecommunication network need to be managed in order to cost effectively provide
the Quality Of Service (QOS) required by customers.
A subset of these resources is constituted by the protocol stack supporting communications between
remote systems.
The structure and process of controlling and/or monitoring activities of different facilities in different
communication layers is the layer management.

Page 6
ETS 300 273: March 1994
Blank page
Page 7
ETS 300 273: March 1994
1 Scope
This European Telecommunication Standard (ETS) describes the Medium Access Control (MAC) layer
management which applies to the European standard Metropolitan Area Network (MAN).
To this end it:
a) defines the reference architecture for MAC Layer Management (MLM);
b) defines services and protocols for MLM;
c) includes the specification of managed objects which permit the operation of the protocol elements
to be remotely managed. The definition of the managed object classes for the Connection Oriented
(CO) and Constant Bit Rate (CBR) services is not contained in this ETS.
Management information within the network is exchanged through systems management protocols and
special purpose layer management protocols.
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 are listed below.
For dated references, subsequent amendments to or revisions 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 211: "Network Aspects (NA); Metropolitan Area Network (MAN)
Principles and architecture".
[2] ETS 300 212: "Network Aspects (NA); Metropolitan Area Network (MAN) Media
access control layer and physical layer specification".
[3] ETS 300 213: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 2,048 Mbit/s".
[4] ETS 300 214: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 34,368 Mbit/s".
[5] ETS 300 215: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 139,264 Mbit/s".
[6] ETS 300 216: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 155,520 Mbit/s".
[7] IEEE Standard 802.1b, Draft D.19 (1991): "Local Area Networks and
Metropolitan Area Networks - Management".
[8] IEEE Standard 802.1f, Draft D7 (1991): "Guide-lines for the Development of
Layer Management Standard".
[9] IEEE Standard 802.6g, Draft D0 (1991): "Distributed Queue Dual Bus (DQDB)
Subnetwork of a Metroplolitan Area Network (MAN) - Layer Management".
[10] CCITT Recommendation X.208 (1988): "Specification of Abstract syntax
notation one (ASN.1)".
[11] CCITT Recommendation X.700: "OSI Management Framework".
[12] CCITT Recommendation X.701: "Information technology - Open systems
interconnection - Systems management overview".

Page 8
ETS 300 273: March 1994
[13] CCITT Recommendation X.711 (1991): "OSI Common management information
protocol specification for CCITT applications".
[14] CCITT Draft Recommendation X.720: "Information technology - Open systems
interconnection - Structure of management informations: management
information model".
[15] CCITT Draft Recommendation X.721: "Information technology - Open systems
interconnection - Structure of management informations: definition of
management information".
[16] CCITT Recommendation X.722: "Information technology - Open systems
interconnection - Structure of management informations: Guide-lines for the
Definition of Managed Objects".
[17] CCITT Recommendation X.200 (1988): "Reference model of open system
interconnection for CCITT applications".
[18] IEEE Standard 802.6 (1991): "Distributed Queue Dual Bus (DQDB) Subnetwork
of a Metropolitan Area Network (MAN)".
[19] CCITT Recommendation M.3010 (1992): "Principles for a Telecommunication
Management Network".
[20] CCITT Recommendation G.773 (1988): "Protocol suites for Q-interfaces for
management of transmission systems".
[21] ETS 300 276: "Network Aspects (NA); Metropolitan Area Network (MAN)
Physical layer convergence procedure for 622,080 Mbit/s CCITT
Recommendations G.707, G.708, and G.709 SDH based systems".
[22] ISO 8802-2 (1988): "Information processing systems - Local area networks -
Part 2: Logical link control".
[23] ISO 8802-2 addendum 2: "Information Processing Systems - Local Area
Networks. Logical Link Control - Addendum 2: Acknowledged connectionless-
mode services and protocol, Type 3 operation".
[24] ISO 8348 addendum 1 (1987): "Information processing systems - Data
communication - Network service definition Addendum 1: Connectionless-mode
transmission".
[25] ISO 8348 addendum 2 (1988): "Information processing systems - Data
communication - Network service definition - Addendum 2: Network layer
addressing".
[26] ISO 8473 (1988): "Information processing systems - Data communications -
Protocol for providing the connectionless-mode network service".
[27] CCITT Recommendation M.3100 (1992): "Generic Network Information Model".
[28] CCITT Draft Recommendation X.738 (1991): "Summarisation Function".

Page 9
ETS 300 273: March 1994
3 Definitions and abbreviations
3.1 Definitions
This ETS uses the MAN terminology defined in ETS 300 211 [1], specifically:
a) Access Facility 1 (AF1);
b) Access Facility 2 (AF2);
c) Distributed Queue Dual Bus (DQDB);
d) MAN Switching System (MSS);
e) Metropolitan Area Network (MAN);
f) User MAN Interface (UMI).
This ETS also uses the MAN terminology defined in ETS 300 212 [2], specifically:
a) Bus Identification Field (BIF);
b) Default Slot Generator Subfield (DSGS);
c) External Timing Source Subfield (ETSS);
d) Head Of Bus Subfield (HOBS);
e) Medium Access Control (MAC);
f) Message Identifier (MID);
g) Physical Layer Convergence Procedure (PLCP);
h) slot.
This ETS uses some of the terminology defined in the CCITT Draft Recommendation X.738 [28],
specifically:
- granularity period.
3.2 Abbreviations
For the purposes of this ETS, the following abbreviations apply:
AF1 Access Facility 1
AF2 Access Facility 2
AFI Authority and Format Identifier
ASN.1 Abstract Syntax Notation 1
BCD Binary Coded Decimal
BIF Bus Identification Field
BWB Bandwidth Balancing
CBR Constant Bit Rate
CC Configuration Control
CL Connectionless
CO Connection Oriented
CRC Cyclic Redundancy Check
DCN Data Communication Network
DMPDU Derived MAC Protocol Data Unit
DQDB Distributed Queue Dual Bus
DSGS Default Slot Generator Subfield
ETSI MAN European MAN conforming to ETSI ETSs on MANs
ETSS External Timing Source Subfield

Page 10
ETS 300 273: March 1994
HOB Head Of Bus
HOBS Head Of Bus Subfield
IDI Initial Domain Identifier
IMPDU Initial MAC Protocol Data Unit
LLC Logical Link Control
LMPE Layer Management Protocol Entity
LSAP LLC Service Access Point
MAC Medium Access Control
MAN Metropolitan Area Network
MCF MAC Convergence Functions
MID Message Identifier
MLM MAC Layer Management
MN MAN Node
MSS MAN Switching System
NE Network Element
PDH Plesiochronous Digital Hierarchy
PDU Protocol Data Unit
PLCP Physical Layer Convergence Procedure
PLCSM Physical Layer Connection State Machine
PR Page Request
QA Queued Arbitrated
Q Q interface for specific MAN systems and service management
MAN
QOS Quality Of Service
RDN Relative Distinguished Name
RIT Reassembly IMPDU Timer
RSM Reassembly State Machine
SAP Service Access Point
SDH Synchronous Digital Hierarchy
TMN Telecommunication Management Network
UMI User MAN Interface
VCI Virtual Channel Identifier
4 MAC layer management
The MAC layer of the European MAN conforming to ETSI ETSs on MANs (ETSI MAN) uses IEEE
Standard 802.6 [18] Distributed Queue Dual Bus (DQDB) functions. Management of these functions is
performed in two specific categories: peer-to-peer management of DQDB entities is performed over a
special purpose layer management protocol, and remote management is performed over a systems
management interface. These are described below.
4.1 MAC layer management architecture
This subclause describes the general architecture for MLM.
There are two main aspects of the management function. One is the layer management related
information and operations and the second is the communication services and protocols required to
exchange management information between different open systems.
The information model used in this ETS is based on the definition given in CCITT Draft Recommendation
X.720 [14]. Managed objects for MLM are defined according to guide-lines given in CCITT
Recommendation X.722 [16].
Management communication is effected through the following mechanisms:
a) the use of the special purpose management protocols within the layer;
b) the use of systems management protocols.

Page 11
ETS 300 273: March 1994
4.2 MLM through special purpose layer management protocols within the MAC layer
The mechanism for the exchange of layer management information between two MAC layer entities is
indicated in IEEE Standard 802.6 [18], sections 9 and 10, as indicated in ETS 300 212 [2]. Figure 1 shows
a schematic representation of this mechanism.
The MAC layer entities communicate with one another via the MLM protocol to support management
control of the layer.
Higher
Higher
layers
layers
Special purpose
MLM protocol
MAC MAC
LMPE LMPE
layer
layer
(via octets M1/M2)
Physical
Physical
layer
layer
Figure 1: Layer Management Protocol Entity (LMPE)
4.2.1 MLM interface
This subclause is based on IEEE Standard 802.6 [18], section 9 (as indicated in ETS 300 212 [2]) and
applies for Access Facility 1 (AF1) and Access Facility 2 (AF2). Section 9.2.4 of IEEE Standard 802.6 [18]
describes functions required for the connection oriented convergence function and is, therefore, for further
study within ETSI. Section 9.7 of IEEE Standard 802.6 [18] describes functions related to configuration
control that are required only for a looped multipoint configuration.
4.2.2 MLM protocol
This subclause is based on IEEE Standard 802.6 [18], section 10 (as indicated in ETS 300 212 [2]) and
applies for AF1 and AF2. Section 10.2 of IEEE Standard 802.6 [18] describes the configuration control
protocol, which is required only for a looped multipoint configuration. In any other case the node on the
MAN Switching System (MSS) side of the interface shall set the MAC layer information octet type 0 to
00111011 (TYPE=0, Bus Identification Field (BIF)=01, Default Slot Generator Subfield (DSGS)=11, Head
of Bus Subfield (HOBS)=01, External Timing Source Subfield (ETSS)=1).
Section 10.3 of IEEE Standard 802.6 [18] describes the Message Identifier (MID) page allocation protocol.
This section applies only where dynamic distributed MID page allocation is implemented.

Page 12
ETS 300 273: March 1994
4.3 MLM through systems management
The communication structure for the exchange of management information through systems management
protocols is based on manager/agent relationships as indicated in CCITT Recommendation X.701 [12].
Figure 2 shows the communication between the manager and the agent entities, between agent and
managed objects, as well as the protocols and services used for this purpose.
The MAC layer resources are part of the whole MAN resources. Therefore, they are subject to control and
supervision by the MAN systems management.
The interface to the MAN management system is the systems management interface, and the definition of
this interface implies the definition of the management information (the information model) as well as of
the protocols that carry this information.
The DQDB MAC sublayer is implemented both in MSSs and MAN Nodes (MNs). Depending on the type of
managed element, different interfaces can be used for the management of the sublayer resources
through system management.
MSSs can use either DQDB based networks or other networks as access part to the public
Telecommunication Management Network (TMN) Data Communication Network (DCN).
The protocol suite which shall be used is either the Q (described in subclause 4.3.2), the Q (defined in
MAN
CCITT Recommendation G.773 [20]) or the Q3 (defined in CCITT Recommendation Q.961 and CCITT
Recommendation Q.962).
The Q short stack (see subclause 4.3.2.2) management interface shall be provided in the MN.
MAN
Additional interfaces may be provided.
This ETS specifies only the short stack Q protocol suite.
MAN
Page 13
ETS 300 273: March 1994
MANAGER
OPEN SYSTEM
MANAGER
Request Confirmation
management service
management
protocol
management service
Indication Response
MANAGED
OPEN SYSTEM
AGENT
Managed
Operations Results
object
boundary
MANAGED
OBJECTS
2a:  Operations
MANAGER
OPEN SYSTEM
MANAGER
Response Indication
management service
management
protocol
management service
Confirmation Request
MANAGED
OPEN SYSTEM
AGENT
Managed
Notifications
object
boundary
MANAGED
OBJECTS
2b:  Notifications
Figure 2: MAN management information exchanges

Page 14
ETS 300 273: March 1994
4.3.1 Interface
The Q interface is considered for specific MAN systems (and service) management. This interface
MAN
shall be used for systems (and service) management communications among managers and agents
(indicated in subclause 4.2) when they take place via a DQDB based MAN. The protocols for the Q
MAN
interface are specified in subclause 4.3.2. The exchanged information (as far as the MLM is concerned) is
specified in Clause 5, where the MLM information model is defined.
NOTE: The MAC layer information model as defined in this ETS can also be used with system
management interfaces different from the Q .
MAN
4.3.2 Protocols
4.3.2.1 Introduction
In the following, the protocol suites for the Q interface are described.
MAN
The defined communication services and protocols are in accordance with the CCITT Recommendation
X.200 [17]. The protocols for the non-MAC layers are based on CCITT Recommendations and/or ISO
standards, while the MAC layer is defined in relevant IEEE Standard and ETSI standards, IEEE Standard
802.6 [18] and ETS 300 212 [2].
Two protocol suites are considered:
a) short stack protocol suite;
b) full 7 layers stack protocol suite.
A short stack protocol suite is mandatory when the Q interface is placed on MAN Nodes (MNs) and
MAN
shall be implemented as described in subclause 4.3.2.2.
The full 7 layers protocol suite for the Q is not specified in this ETS. However, it should be aligned, for
MAN
the layers above the MAC layer, to the CCITT Draft Recommendations Q.961 (§ 5.3.2.2 and § 5.3.3) and
CCITT Recommendation Q.962 (§ 3.2, § 3.3, § 3.4, § 3.5, § 4.1 and § 4.2).
4.3.2.2 Short stack protocol suite
4.3.2.2.1 Physical layer
The short stack protocol suite employs MAN technology for the physical and data link layers. Therefore,
the following alternatives are considered for the physical layer:
- 2,048 Mbit/s: CCITT Recommendations G.702, G.703, and G.704 Plesiochronous
Digital Hierarchy (PDH);
- 34,368 Mbit/s: CCITT Recommendations G.702, G.703, and G.751 PDH;
- 139,264 Mbit/s: CCITT Recommendations G.702, G.703, and G.751 PDH;
- 155,520 Mbit/s: CCITT Recommendations G.707, G.708, and G.709 Synchronous
Digital Hierarchy (SDH);
- 622,080 Mbit/s: CCITT Recommendations G.707, G.708, and G.709 SDH.
The relevant Physical Layer Convergence Procedures (PLCPs) are indicated respectively in the following
documents: ETS 300 213 [3], ETS 300 214 [4], ETS 300 215 [5], ETS 300 216 [6] and in
ETS 300 276 [21].
Page 15
ETS 300 273: March 1994
4.3.2.2.2 Data link layer
The data link layer provides the acknowledged connectionless-mode service. The access method
employed is the DQDB in accordance with IEEE Standard 802.6 [18].
The services and protocol of the DQDB access method shall comply with those specified in
ETS 300 211 [1]. The address length used at the MAC sublayer shall be 60 bits.
The definition of the acknowledged connectionless-mode Logical Link Control (LLC) service and protocol
shall comply with that specified in ISO 8802-2 [22] and ISO 8802-2 addendum 2 [23].
4.3.2.2.3 Network layer
The definition of the connectionless-mode network service shall comply with that specified in ISO 8348
addendum 1 [24]. Address formats supported shall conform to ISO 8348 addendum 2 [25].
The network layer requires the normal data transfer service from the data link layer. The network layer
shall provide the N-UNITDATA service as listed in table 8 of CCITT Recommendation G.773 [20]
(equivalent to table 15 of ISO 8348, addendum 1 [24]).
The network protocol is specified in ISO 8473 [26]. The Authority and Format Identifier (AFI) and the Initial
Domain Identifier (IDI) shall be set according to ISO 8348 addendum 2 [25].
The full network layer protocol and its two subsets permit the use of known sub-network characteristics
and are therefore not sub-network independent. Depending on the required usage and the sub-network
architecture, the full network layer protocol, or one or both subsets, shall be supported by the short stack
protocol suite:
- the inactive network layer protocol shall be in accordance with the inactive subset of the protocol as
defined in ISO 8473 [26];
- the non-segmenting network layer protocol shall be in accordance with "Type 1" functions of the
non-segmenting subset of the protocol as defined in ISO 8473 [26]. From the optional functions
("Type 3") defined in the non-segmenting subset only the "priority functions" shall be supported as
defined in ISO 8473 [26];
- the full network layer protocol subset of category "Type 1" functions shall be in accordance with ISO
8473 [26]. An implementation of such a protocol shall not transmit PDUs encoded using the inactive
subset. Received Protocol Data Units (PDUs) encoded using the inactive subset shall be discarded.
An implementation shall not generate data PDUs without a segmentation part, i.e. the segmentation
permitted flag (SP) shall be set to 1 and the segmentation part shall be included. However, an
implementation shall be capable of receiving and correctly processing PDUs which do not contain
the segmentation part.
4.3.2.2.4 Mapping functions
No transport layer, session layer and presentation layer is specified for the short stack protocol suite. To
provide the required service to the application layer and using the provided service of the network layer, a
mapping function is defined. The mapping function for the short stack protocol suite is specified in the
CCITT Recommendation G.773 [20], § 3.4.
4.3.2.2.5 Application layer
The application layer services and protocol for the short stack protocol suite are specified in CCITT
Recommendation G.773 [20], § 3.5.
4.3.2.3 Addressing principles for MAN systems management
System management communications between local and remote managers require communication
facilities (i.e. DCN). A specific protocol suite and interface (i.e. Q ), to be used when the DCN is a
MAN
DQDB-based MAN, have been specified. In the following subclauses a generic scheme for addressing of
management communications is outlined.

Page 16
ETS 300 273: March 1994
4.3.2.3.1 MAC layer addresses
Management communications shall make use of the Connectionless (CL) service functionalities provided
by the MAN MAC layer. Numbers structured according to CCITT Recommendation E.164 shall be
assigned to address management entities.
The management PDUs that run over the MAC shall be uniquely identified as containing management
information by using the value '000010' binary (to be confirmed by the IEEE) of the protocol identifier field
in the Initial MAC Protocol Data Unit (IMPDU), see ETS 300 212 [2].
4.3.2.3.2 Logical link addresses
Management communications will use the LLC type 3 service. A single LLC (LLC Service Access Point
(LSAP)) address shall be allocated for MAN management, similarly to what is expected for IEEE
LAN/MAN management.
The value of the LLC address to be used is '01000000' binary.
4.3.2.3.3 Addressing at higher layers
The addressing schemes and principles used for the higher layers of the protocol stack are outside the
scope of this ETS.
5 Information model for systems management of the MAC layer
The definition of the information model is based on the guide-lines given in CCITT Draft
Recommendations X.720 [14] and X.721 [15] and deals with managed objects. In this context managed
objects are the management view of resources within the MAC Layer that are subject to management.
Figures 3 and 4 show the MAC layer managed objects inheritance and naming trees respectively.
In the following the MAC layer managed objects for the MAC CL service are described.
NOTE: The definition of the managed object classes for the Connection Oriented (CO) and
Constant Bit Rate (CBR) services is not contained in this ETS and is for further study.
5.1 Object classes and packages definitions
5.1.1 Message identifier page allocation
midPageAllocation MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY midPageAllocationPackage;
REGISTERED AS {managedObjectClass 0};
midPageAllocationPackage PACKAGE
BEHAVIOUR midPageAllocationPackageBehaviour;
ATTRIBUTES
midPageAllocationId GET,
reservedMIDPages DEFAULT VALUE 0
GET-REPLACE
REPLACE-WITH-DEFAULT,
midPagesInUse GET
ADD-REMOVE,
maxMIDPages DEFAULT VALUE 1
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 0};
Page 17
ETS 300 273: March 1994
midPageAllocationPackageBehaviour BEHAVIOUR
DEFINED AS '
This is the managed object class which represents the MID allocation process. The reservedMIDPages
attribute is equal to the DQDB single value RESERVED_MID_PAGES attribute defined in IEEE Standard
802.6 [18], section 7.3.4, as indicated in ETS 300 212 [2]. The midPagesInUse attribute specifies the
MIDs used by the node. It contains a table with the following fields: MCF_ID; Message_ID; Time_Stamp.
The maxMIDPages attribute is equal to the DQDB single value MAX_MID_PAGES attribute defined in
IEEE Standard 802.6 [18], section 7.3.5, as indicated in ETS 300 212 [2].
NOTE: The implementation of this object class is conditional. It is mandatory if the dynamic
centralised MID page allocation mechanism is implemented. This is reflected in
ETS 300 274. The centralised MID page allocation is performed via the ADD-
REMOVE operation on the midPagesInUse attribute.
';
5.1.2 DQDB configuration
dqdbConfiguration MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY dqdbConfigurationPackage;
CONDITIONAL PACKAGES
configurationControlPackage PRESENT IF
"an instance supports it";
REGISTERED AS {managedObjectClass 1};
dqdbConfigurationPackage PACKAGE
BEHAVIOUR dqdbConfigurationPackageBehaviour;
ATTRIBUTES
dqdbConfigurationId GET,
hobOperationIndicators GET,
linkStatusIndicator GET,
externalTimingSourceStatus GET,
lmInfoOctetsType0 GET;
REGISTERED AS {package 1};
dqdbConfigurationPackageBehaviour BEHAVIOUR
DEFINED AS '
The dqdbConfiguration managed object class represents the subnetwork (re)configuration functions in the
DQDB layer. The hobOperationIndicators attribute is equal to the DQDB attribute HOB_OPERATION
defined in IEEE Standard 802.6 [18], section 7.5.2, as indicated in ETS 300 212 [2]. The
linkStatusIndicators attribute equals the DQDB single value attribute LINK_STATUS defined in IEEE
Standard 802.6 [18], section 7.5.3, as indicated in ETS 300 212 [2]. The externalTimingSourceStatus
attribute is equal to the DQDB single value attribute ETS_STATUS defined in IEEE Standard 802.6 [18],
section 7.5.4, as indicated in ETS 300 212 [2]. The lmInfoOctetsType0 attribute represents the information
carried in the two Type 0 octets, as defined in IEEE Standard 802.6 [18], received at the Ph-SAPs and
supporting communication between different DQDB layer management entities.
NOTE: The information concerning the dqdb single value attribute CC_STATUS defined in
IEEE 802.6 Standard [18], section 7.5.1, as indicated in ETS 300 212 [2], can be
derived from the hobOperationIndicators attribute.
';
configurationControlPackage PACKAGE

Page 18
ETS 300 273: March 1994
BEHAVIOUR configurationControlPackageBehaviour;
ATTRIBUTES
hobArbitrationTimerPeriod DEFAULT VALUE 5000
GET-REPLACE
REPLACE-WITH-DEFAULT,
nodeType GET-REPLACE,
configurationControlFlag DEFAULT VALUE disabled
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 2};
configurationControlPackageBehaviour BEHAVIOUR
DEFINED AS '
The hobArbitrationTimerPeriod attribute is equal to the dqdb single value attribute Timer_H_PERIOD
defined in IEEE Standard 802.6 [18], section 7.3.2, as indicated in ETS 300 212 [2] (its default value is
5 000 ms). The nodeType attribute identifies the distinction between a normal node and the default slot
generator node. The configurationControlFlag attribute equals the DQDB single value attribute
CC_12_CONTROL, defined in IEEE Standard 802.6 [18], section 7.4.1, as indicated in ETS 300 212 [2].
';
5.1.3 Distributed queue process
distributedQueueProcess MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY distributedQueueProcessPackage;
REGISTERED AS {managedObjectClass 2};
distributedQueueProcessPackage PACKAGE
BEHAVIOUR distributedQueueProcessPackageBehaviour;
ATTRIBUTES
distributedQueueProcessId GET,
priority GET;
REGISTERED AS {package 3};
distributedQueueProcessPackageBehaviour BEHAVIOUR
DEFINED AS '
The distributedQueueProcess managed object class represents the DQDB distributed queue resources.
';
5.1.4 Bandwidth balancing process
bandwidthBalancingProcess MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY bandwidthBalancingProcessPackage;
REGISTERED AS {managedObjectClass 3};
bandwidthBalancingProcessPackage PACKAGE

Page 19
ETS 300 273: March 1994
BEHAVIOUR bwbProcessPackageBehaviour;
ATTRIBUTES
bandwidthBalancingId GET,
bwbBusIdentifier GET,
bwbModulus DEFAULT VALUE 8
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 4};
bwbProcessPackageBehaviour BEHAVIOUR
DEFINED AS '
The bandwidthBalancingProcess managed object class represents the resources of the DQDB bandwidth
balancing mechanism. The bwbBusIdentifier attribute specifies the bus on which the process is operating.
The bwbModulus attribute is equal to the single value attribute BWB_MOD defined in IEEE Standard
802.6 [18], section 7.3.6, as indicated in ETS 300 212 [2].
NOTE: This object class is optional if the multipoint configuration is implemented, and not
applicable if the point-to-point configuration is implemented.
';
5.1.5 MAN DQDB service access point
manDQDBsap MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY manDQDBsapPackage;
REGISTERED AS {managedObjectClass 4};
manDQDBsapPackage PACKAGE
BEHAVIOUR manDQDBsapPackageBehaviour;
ATTRIBUTES
manDQDBsapId GET,
manDQDBsapNumber GET-REPLACE,
manDQDBsapStatus GET-REPLACE;
REGISTERED AS {package 5};
manDQDBsapPackageBehaviour BEHAVIOUR
DEFINED AS '
manDQDBsap is the managed object class representing the point at which the service is provided. The
manDQDBsapId attribute can be used to build the relative distinguished name of the instances of the
class. The manDQDBsapNumber attribute represents the CCITT Recommendation E.164 number
associated with the point at which the DQDB layer services (CL, CO or CBR) are provided. The
manDQDBsapStatus attribute represents the logical status of the service access point.
';
NOTE: The manDQDBsapStatus attribute is under discussion. The need for representing the
status of the sap is clear, but this might be done by deriving the object class from a
superior class. While this would also be useful for other object classes, a suitable
superior object class has not yet been identified and the manDQDBsapStatus attribute
has been retained in the description.

Page 20
ETS 300 273: March 1994
5.1.6 MAN CL service access point
manCLsap MANAGED OBJECT CLASS
DERIVED FROM manDQDBsap;
CHARACTERIZED BY manCLsapPackage;
REGISTERED AS {managedObjectClass 5};
manCLsapPackage PACKAGE
BEHAVIOUR manCLsapPackageBehaviour;
ATTRIBUTES
manCLsapAddress GET-REPLACE,
discardedIMPDUsThreshold DEFAULT VALUE
ASN1AttributeModule.discardedIMPDUsThresholdDefVal
GET-REPLACE
REPLACE-WITH-DEFAULT;
ACTIONS
manCLsapAddressSet;
NOTIFICATIONS
discardedIMPDUsThresholdAlarm;
REGISTERED AS {package 6};
manCLsapPackageBehaviour BEHAVIOUR
DEFINED AS '
manCLsap is the managed object class representing the point at which the connectionless service is
provided. This object inherits the attributes from the manDQDBsap managed object class. The
manCLsapAddress attribute represents the DQDB MAC address. The structure of the address includes a
4-bit field and a 60-bit field, as defined in IEEE Standard 802.6 [18]. The CCITT Recommendation E.164
numbers associated with the DQDB Service Access Point (SAP) and represented by the
manDQDBsapNumber attribute are mapped into the coding defined for the CL service purposes, which is
fully described in subclause 5.6. The mapping includes Binary Coded Decimal (BCD) coding of the 15
digits of the CCITT Recommendation E.164 number and their placing in the 60-bit field of the CL SAP
address. An alarm is emitted when the threshold represented by the discardedIMPDUsThreshold attribute
is reached.
';
NOTE: The discardedIMPDUsCounter attribute can be found in Annex A, Clause A.4.
5.1.7 Segment header processing
segmentHeaderProcessing MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY segmentHeaderProcessingPackage;
REGISTERED AS {managedObjectClass 6};
segmentHeaderProcessingPackage PACKAGE
BEHAVIOUR segmentHeaderProcessingPackageBehaviour;
ATTRIBUTES
segmentHeaderProcessingId GET,
clVCIList DEFAULT VALUE {1,'FFFFF' hex}
GET
Page 21
ETS 300 273: March 1994
ADD-REMOVE
REPLACE-WITH-DEFAULT;
ACTIONS
clVCIListSet;
REGISTERED AS {package 7};
segmentHeaderProcessingPackageBehaviour BEHAVIOUR
DEFINED AS '
The segmentHeaderProcessing managed object class represents the resources related to virtual channel
identifiers. The clVCIList attribute contains the list of connectionless VCIs associated with the MAC
convergence function in a MAN node. The default list includes the number of Virtual Channel Identifiers
(VCIs), i.e. 1 and the single value 'FFFFF' hex (or '11111111111111111111' binary), as specified in IEEE
Standard 802.6 [18], section 6.3.1.1.1.1, as indicated in ETS 300 212 [2].
';
5.1.8 IMPDU reassembly process
impduReassemblyProcess MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY impduReassemblyProcessPackage;
CONDITIONAL PACKAGES
reassemblyErrorCounterThresholdPackage PRESENT IF
"an instance supports it",
crc32CheckControlPackage PRESENT IF
"an instance supports it";
REGISTERED AS {managedObjectClass 7};
impduReassemblyProcessPackage PACKAGE
BEHAVIOUR impduReassemblyProcessPackageBehaviour;
ATTRIBUTES
impduReassemblyProcessId GET,
ritPeriod DEFAULT VALUE 700
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 8};
impduReassemblyProcessPackageBehaviour BEHAVIOUR
DEFINED AS '
The impduReassemblyProcess managed object class represents the resources of the DQDB reassembly
procedure. The ritPeriod (its default value is 700 ms) attribute is equal to the single value attribute
RIT_PERIOD defined in IEEE Standard 802.6 [18], section 7.3.1, as indicated in ETS 300 212 [2].
';
reassemblyErrorCounterThresholdPackage PACKAGE
BEHAVIOUR reassemblyErrorCounterThresholdPackageBehaviour;
ATTRIBUTES
reassemblyErrorCounterThreshold DEFAULT VALUE
ASN1AttributeModule.reassemblyErrorCounterThresholdDefVal
GET-REPLACE
REPLACE-WITH-DEFAULT;
NOTIFICATIONS
Page 22
ETS 300 273: March 1994
reassemblyErrorCounterThresholdAlarm;
REGISTERED AS {package 9};
reassemblyErrorCounterThresholdPackageBehaviour BEHAVIOUR
DEFINED AS '
This package supports the emission of an appropriate notification in case the number of errors occurring
during the IMPDU reassembly process reach a specific threshold value within a certain granularity period.
It also supports the control over this threshold value.
';
NOTE: The reassemblyErrorCounter attribute can be found in Annex A, Clause A.6.
crc32CheckControlPackage PACKAGE
BEHAVIOUR crc32CheckControlPackageBehaviour;
ATTRIBUTES
crc32CheckControl DEFAULT VALUE off
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 10};
crc32CheckControlPackageBehaviour BEHAVIOUR
DEFINED AS '
The crc32CheckControlPackage package defines the information related to the operation of the CRC32
checking mechanism. It is an optional feature. The crc32CheckControl attribute is equal to the single
value attribute CRC32_CHECK_CONTROL defined in IEEE Standard 802.6 [18], section 7.4.4, as
indicated in ETS 300 212 [2]. The default value for this attribute is "off".
';
5.1.9 IMPDU transmission process
impduTransmissionProcess MANAGED OBJECT CLASS
DERIVED FROM "CCITT Recommendation X.721 [15]":top;
CHARACTERIZED BY impduTransmissionProcessPackage;
CONDITIONAL PACKAGES
crc32GenerationControlPackage PRESENT IF
"an instance supports it",
headerExtensionPackage PRESENT IF
"an instance supports it";
REGISTERED AS {managedObjectClass 8};
impduTransmissionProcessPackage PACKAGE
BEHAVIOUR impduTransmissionProcessBehaviour;
ATTRIBUTES
impduTransmissionProcessId GET,
qosMap DEFAULT VALUE {0,0,0,0,0,0,0,0}
GET-REPLACE
REPLACE-WITH-DEFAULT;
REGISTERED AS {package 11};
Page 23
ETS 300 273: March 1994
impduTransmissionProcessBehaviour BEHAVIOUR
DEFINED AS '
The impduTransmissionProcess is the managed object class which represents the resources of the
IMPDU transmission procedure. The qosMap attribute is equal to the single value attribute QOS_MAP
attribute defined in IEEE Standard 802.6 [18], section 7.3.3, as indicated in ETS 300 212 [2].
NOTE: The default value of the qosMap attribute is {0,0,0,0,0,0,0,0}, indicating that all the
eight levels of QOS (from QOS level 0 to QOS level 7) for incomi
...